A Tivoli Field Guide Maximo for the Nuclear Power Industry Duty Stations (Nuc) Release 7.51

Transcription

1 A Tivoli Field Guide Maximo for the Nuclear Power Industry Duty Stations (Nuc) Release 7.51 By Jean Bellefeuille Version 1.0

2 Copyright Notice Copyright IBM Corporation All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Trademarks IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Enterprise Console, Tivoli Ready, and TME are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both. Lotus is a registered trademark of Lotus Development Corporation. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both. PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. For a complete list of Intel trademarks, see SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For further information, see Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York , U.S.A. iii

3

4 About the Tivoli Field Guides Sponsor Tivoli Customer Support sponsors the Tivoli Field Guide program. Authors Those who write field guides belong to one of these three groups: Tivoli Support and Services Engineers who work directly with customers Tivoli Customers and Business Partners who have experience using Tivoli software in a production environment Tivoli developers, testers, and architects Audience The field guides are written for all customers, both new and existing. They are applicable to external audiences including executives, project leads, technical leads, team members, and to internal audiences as well. Types of Field Guides Two types of Tivoli Field Guides describe how Tivoli products work and how they are used in real life situations: Field Guides for technical issues are designed to address specific technical scenarios or concepts that are often complex to implement or difficult to understand, for example: endpoint mobility, migration, and heartbeat monitoring. Field Guides for business issues are designed to address specific business practices that have a high impact on the success or failure of an ESM project, for example: change management, asset Management, and deployment phases. Purposes The Field Guide program has two major purposes: To empower customers & business partners to succeed with Tivoli software by documenting and sharing product information that provides accurate and timely information on Tivoli products and the business issues that impact an enterprise systems management project To leverage the internal knowledge within Tivoli Customer Support and Services and the external knowledge of Tivoli customers and Business Partners Availability All completed field guides are available free to registered customers and internal IBM employees at the following Web site: Authors can submit proposals and access papers by mailto:tivoli_esupport_feedback@us.ibm.com v

5 Table of Contents Sponsor... v Authors... v Audience... v Types of Field Guides... v Purposes... v Availability... v OVERVIEW... 8 INTRODUCTION... 8 DUTY STATIONS... 9 DUTY STATION PLANS... 9 SHIFT RECORDS... 9 SHIFT CYCLES SHIFT OWNERS AND SHIFT EDITORS Shift Owners Additional Roles Shift Editors Shift Teams PLANNING DUTY STATION REQUIREMENTS IDENTIFYING FUNCTIONS PLANNING DUTY STATIONS PLANNING SHIFT TEAM COMPOSITION DEFINING SECURITY GROUPS FOR SHIFT EDITORS PLANNING SHIFT ROUNDS DEVELOPING DUTY STATION PLANS CONFIGURATION RULES FOR ON-DEMAND PROCESS PLANS CONFIGURATION RULES FOR COMMON LOG PLANS SPECIFYING READINGS FOR SHIFT ROUNDS AND TURNOVER Defining reading frequency Defining readings ACTIVATING DUTY STATION PLANS

6 DUTY STATION PLAN REVISIONS EQUIPMENT MONITORING PROCESSES READINGS FOR SHIFT ROUNDS AND TURNOVER READINGS FOR ON-DEMAND PROCESSES READING HISTORIES NARRATIVE LOG ENTRIES AND OPERATIONAL HISTORY UPDATES MANAGING SHIFT CYCLES AND ON-DEMAND PROCESSES STARTING A DUTY STATION DIRECTING SHIFT OPERATIONS Site and unit objectives Notifications for individual users CONDITION REPORTING SHIFT RECORD ROUTINE, ON-DEMAND, OR TURNOVER READING NARRATIVE LOG ENTRY SHIFT EXECUTION STARTING THE SHIFT REVIEWING AND RESPONDING TO NOTIFICATIONS CONDUCTING SHIFT ROUNDS Rules for conducting shift rounds MAINTAINING THE NARRATIVE LOG Rules for maintaining the narrative log REPORTING ON UNIT STATUS AND OBJECTIVES Unit status Objectives COMPLETING SHIFT TEAM REVIEWS STARTING AND COMPLETING SHIFT TURNOVER CHANGING THE DUTY STATION PLAN CLOSING SHIFT RECORDS

7 Overview Maintaining records of facility activities is both mandated by law and a good practice. In normal operations at Nuclear plants there may be as many as 8-10 logs being maintained. The logs typically are either a position name or a physical portion of the facility e.g. Shift Manager, Control Room Supervisor, Balance of Plant, Nuclear Side, Water Factory, Condensate Polisher, Watch HP, Watch Maintenance, Watch I&C. In addition, occasionally logs are created for unique needs, some being one time use, while others may be for special plant modes or operations. While the principle users are expected to be Operational Positions and functions, other departments and generic functions can also make use of Duty Station functionality. During outages there may be many other logs established to support outage positions and roles. Logs can be required to be reviewed by superiors and also are used in the turn-over process to document the information exchange and transfer of responsibility to the new individual. Logs are valuable source of information and viewed by many. Frequently logs are viewed thru facility web portals The shift / log process is driven by the routine administrative requirements and as such the manual recording and analysis of plant equipment data is contained in this process as well. In addition to posted plant schedules and work process facility management can formally communicate via written directives to the shift personnel In addition to becoming qualified before assuming a duty station, incumbents must maintain awareness of changes to plant processes, design and management directives. A review of Notifications and Objectives is how those expectations are communicated and acknowledged With the above capabilities Maximo can create and manage the logs for a facility and mimic the control processes established by the facilities log keeping process. Introduction Maximo Nuclear uses Duty Station Plans (Nuc) and Duty Stations (Nuc) to manage these functions. Notifications (Nuc) and Objectives (Nuc) provide administrative support. Reading Frequencies (Nuc), Meters, and Condition Monitoring are also used to plan and execute Readings as part of the Duty Station process. You use duty station plans to define the functions that are required for shift operations at a nuclear power plant. You use shift records to execute the functions as planned and to document duty station status and activity. 8

8 While shift operations are in progress, you use objectives and notifications to communicate orders and other types of information to shift teams and individual shift owners. Duty Stations A duty station is the configuration of function, site, and unit that is used to manage the execution of a function at a specific site or unit. A function is a role, process, or activity with a specific purpose that must be accomplished for shift operations. Field operator and shift manager are examples of role-based functions. Unit log is an example of a process-based function. A function can be required for shift operations in some or all modes of plant operation, such as starting up, power production, and shutdown. For example, the shift manager function is required in all modes of plant operation. The outage engineer function is required only in outage periods. Depending on the associated function, a duty station can be active for some or all modes of plant operation. Duty Station Plans A duty station plan defines the requirements for a function when that function is executed at a specific site or unit. In each duty station plan, the duty station is defined by the configuration of function, site, and unit. If the requirements vary for different modes of plant operation, you can define more than one duty station plan for the same duty station. Duty station plans for the same duty station have the same configuration of function, site, and unit. A standard duty station plan defines the requirements for a role-based function. However, you can create specialized duty station plans to define the requirements for process-based functions such as common log and on-demand equipment monitoring. You use duty station plan to generate shift records. If multiple duty station plans exist for the same duty station, you can use only one of these plans at a time to generate shift records. Shift Records As a shift owner, you use the shift record to execute the duty station function in accordance with requirements. The following shift record content and authorizations are derived from the underlying duty station plan: Shift team data and authorization to review the shift records of other team members A narrative log for the duty station where you can create entries and follow up on or correct existing entries Readings that are required for equipment monitoring processes, including shift rounds and turnover Authorization to add on-demand readings to the duty station Authorization to report on unit status and objectives Access to information about key components for the duty station Access to information about LCO actions and condition reports for the site 9

9 Authorization for other users to edit the current shift record You create duty station plans in the Duty Station Plans application. You generate shift records in the Duty Stations application. Shift Cycles To activate a function at a particular site or unit, you start the corresponding duty station and select the appropriate duty station plan. The appropriate duty station plan is the one that specifies the requirements for the current mode of plant operations. The start action initiates the first shift in the cycle and generates a shift record that is based on the selected duty station plan. Successive shifts in the same cycle are linked by the turnover process. During turnover, the outgoing shift owner transfers duty station responsibility to the incoming shift owner. When the outgoing shift owner completes turnover, a new shift record is generated for the incoming shift owner. All shifts records in the cycle are based on the same duty station plan. The duty station must be stopped temporarily if a change in procedures or plant conditions requires a different duty station plan. For example, you might need to adopt a new revision of the same duty station plan or a duty station plan that applies to a different mode of plant operation. When the duty station is restarted, a new shift cycle is initiated based on the new duty station plan. You stop the duty station when the function is no longer required for current shift operations. From the current Duty Station plan, the View Duty Station History action looks at the records current Function, Site, and Unit and displays all Starts and Stops which also encompasses changes in the plan or the plan s revision. Shift Owners and Shift Editors Shift records are used by shift owners and shift editors. These roles are associated with different levels of authorization in the context of the duty station process. Shift Owners A shift owner is responsible for a duty station in a shift period and owns the corresponding shift record. The shift owner executes the duty station function in accordance with requirements. The requirements are defined in the duty station plan from which the shift record is derived. The shift owner uses the shift record to document duty station status and activity, and to communicate with other members of the shift team. During the turnover process, the outgoing shift owner specifies the owner of the next shift in the cycle and formally transfers responsibility for the duty station to that user. In a duty station plan, you can specify the qualifications that users must have to take ownership of the associated shifts. During the turnover process, the qualifications of incoming shift owners are checked against the requirements that are specified in the underlying station plan. An incoming shift owner who does not have the required qualifications is warned but not prohibited from starting the shift. You must use external 10

10 administrative controls to define the procedure for shift personnel whose qualifications do not meet the requirements. Additional Roles A shift owner can assume an additional role such as fire brigade leader that is independent of the duty station function. You define each additional role as a qualification in the Qualifications application. During the turnover process, the outgoing shift owner can specify an additional role for the incoming shift owner. Alternatively, the current shift owner can specify an additional role while the shift is in progress. In either case, if a qualification is specified for the duty station then the assignment of an additional role triggers a qualification check. A shift owner who does not have the required qualification is warned but not prohibited from assuming the role. Shift Editors A shift editor is a user with authorization to edit a shift record that is owned by another user. For example, a staff member who is assigned to assist at a duty station must have shift editor authorization for the corresponding shift record to create entries in the narrative log. The name, function, and shift ownership status of the shift editor are captured in the narrative log entry details. A shift editor cannot take ownership of a shift record that belongs to another user. However, if the shift owner is unavailable, the shift editor can perform actions, such as shift turnover, that are required to complete the shift. You grant shift editor authorization by specifying a security group in the duty station plan. Members of the specified security group have shift editor authorization for shift records that are based on the duty station plan. If a duty station plan does not require a functionspecific shift editor group, it is recommended that you specify a generic shift editor group such as MAXADMIN to prevent record locks during shift operations. Shift Teams A shift team is the set of functions that is required for shift operations at a specific unit. The composition of the shift team can vary depending on the mode of plant operation and other factors that affect plant conditions. For each function in a shift team, you typically define a duty station and one or more duty station plans. In each duty station plan, in the Shift Team table, you specify the other functions that comprise the shift team. You can also specify the requirement for owners of the current function to review the work of other team functions. The following rules apply: The other functions that comprise the shift team must belong to the same site as the current function. For each team function, you must specify a unit, except when the function applies to the site. The configuration of function, site, and, where necessary, unit identifies the relevant duty station. You cannot define a two-way team review. If the owners of the current function review the work of another team function, the owners of that function cannot review the work of the current function. 11

11 When you add a team function to a duty station plan, the action is not reciprocated in the duty station plans for that team function. If required, the current function must be added as a team function to the relevant duty station plans. The shift team that you define in a duty station plan determines the composition of the narrative log team view in the associated shift records. The team view includes only entries from the narrative logs of shift team defined in that duty station s plan. The shift team details that you define in the duty station plan are copied to the Shift Team table in the associated shift records. As a shift owner, you use the Shift Team table in your shift record to communicate with other members of the shift team: For each team function, you can view current shift owner and shift record details. In an active shift record, the shift team details are dynamically updated so that the information remains current. When the status of the shift record is changed to Completed, the shift team details are no longer updated. You complete the required team reviews by using the links in the Shift Team table to navigate to the relevant shift records. You enter review comments in your own shift record. If your function is a team function in the reviewed shift record, your comments are also displayed there. If your shift record includes a narrative log, you can view open and completed entries from the narrative logs of the shift team duty stations. Planning Duty Station Requirements Staff members who are responsible for plant procedures define the functions and duty stations that are required for shift operations. For each duty station, one or more duty station plans is defined. Duty station plans are activated when they are ready for use as shift record templates. The duty station plan acts a template for shift records. You use the configuration options to provide shift owners with the content and authorizations they need to execute the duty station function. You can also create specialized duty station plans for on-demand and common log processes. Identifying functions You identify the functions that are required for different modes of plant operation. In the Domains application, for each function, you define a value in the PLUSDUTYPOSITION domain. You must define different values for functions that are executed by the same staff member but require separate shift records. For example, you must define different functions for the shift manager role and the emergency director role for which shift managers might be responsible. If the functions that you identify require specific qualifications, you can define these qualifications in the Qualifications application. You associate qualifications with functions when you develop the duty station plans. 12

12 Planning duty stations For each function, you define one or more duty stations. A duty station is required for each site or unit where the function is executed. Typically, you manage shift operations for each unit in the nuclear power plant separately. As a result, most duty stations are unit-specific. However, for a function with site-level responsibility, you can define a duty station that applies to the site and all constituent units. For example, in a multiunit power plant, where the shift manager is responsible for all units, you can define a duty station at the site level for the shift manager function. You can define duty stations at the unit level for unit-specific functions in the same shift team. Planning shift team composition You define the composition of shift teams by considering the requirement for various functions in different modes of plant operation. For example, the shift manager function is required for shift teams that operate in all modes of plant operation. The outage engineer function is required only for shift teams that operate in outage periods. Defining security groups for shift editors By default, only shift owners can modify shift records. However, in a duty station plan, you can specify a security group to grant authorization to edit the associated shift records. In the Security Groups application, you can define security groups that are function-specific or generic. For example, you can define a security group for operators who require access to the narrative log for the field support supervisor function. For duty stations that do not require function-specific shift editors, you can define a generic security group. You specify this security group in duty station plans to avoid record locks during shift operations. Planning shift rounds In duty stations where shift owners must monitor equipment, you plan the readings that are taken during shift rounds and turnover. At a minimum, for each reading, you must define the measurement point or meter and the meter component. You define measurement points in the Condition Monitoring application, and you define meters in the Meters application. For routine or on-demand readings that are taken during shift rounds, you must also define a reading frequency in the Reading Frequencies application. You specify these readings in the duty station plan or plans for the relevant duty stations. Developing Duty Station Plans In the Duty Station Plans application, for each duty station, you develop one or more duty station plans. For example, if the requirements for the same duty station vary for different modes of plant operation, you can create multiple duty station plans that are differentiated by mode. In each duty station plan, you specify the duty station to which the duty station plan applies. 13

13 In a standard duty station plan, you use the configuration options to specify the processes that are implemented by shift owners and to grant the required authorizations. The following table outlines the configuration options that apply to standard duty station plans. Configuration Option Description Impact on Shift Records Duty Station Processes Has Rounds Has Narrative Logs Shift Team Required Qualifications Authorizations Reports on Unit Status Indicates whether shift owners take readings during shift rounds or turnover. Indicates whether shift owners maintain a narrative log. If the narrative log is intended for multiple users, you must specify a shift editor group that includes all potential users. The team functions that are specified in the Shift Team table determine the composition of the narrative log team view. Identifies the other functions that comprise the shift team, and specifies the requirement for shift owners to review the work of other team functions. Defines the qualifications that users must have to take ownership of shifts that are based on the duty station plan. Indicates whether shift owners are authorized to report on the status of the duty station unit. Shift records include a Rounds tab and a table for readings on the Turnover tab. If you do not select this option, shift records cannot be used to manage readings for shift rounds or turnover. Shift owners cannot add ondemand processes. Shift records include a Narrative Log tab and a Narrative Log - Team View tab. Shift records include current shift owner and shift record details for team functions. Shift owners can review the work of other team functions and see the reviews that are provided by other team functions. Shift owner qualifications are checked before the start of each shift. Shift owners who do not have the required qualifications are warned but not prohibited from starting the new shift. Unit status updates are shown in all active shift records for the unit. If you do not select this option, shift owners can view unit status details but cannot provide updates. 14

14 Reports on Objectives Secondary Unit Shift Editors Indicates whether shift owners are authorized to report on the status of objectives for the duty station unit. A unit or facility, other than the main unit, that is related to the duty station. A security group whose members can edit shift records that are based on the duty station plan. Access to data from related processes Key Components Identifies components that are key indicators of the general status of the duty station. LCO Actions Condition Reports Indicates whether shift records include information about LCO (limiting condition for operation) actions that are due for the site. Indicates whether shift records include information about condition reports for the site that require an operations shift review. Information about the status of unit objectives is shown in all active shift records for the unit. If you do not select this option, shift owners can view this information but cannot provide updates. Shift records by default include information about the secondary unit, including unit status and objectives. Shift records can be edited by users other than the shift owner. For example, shift editors can create entries in the narrative log. Shift records provide information about the status and condition of key components. This information is taken from the operational history in the component record. Shift records include an All LCO Actions Due tab. This information is read only and is taken from LCO records for the parent site that have a status of Active. Shift records include a Condition Reports for Review tab. This information is read only and is taken from condition reports for the parent site that have a status of Draft or Waiting for Approval. Configuration rules for on-demand process plans An on-demand process is a set of readings that is used to fulfill a temporary or periodic requirement at a specific duty station. For example, you can define an on-demand process to monitor a temporary air compressor that is used only during outages. You use a specially configured duty station plan to define the readings that are required in an on-demand process. The following rules apply: 15

15 The on-demand process plan must have the same function, site, and unit as the duty station to which the on-demand process applies. The On-Demand Process check box must be selected. You can add one or more on-demand processes to an active shift record. The duty station plan on which the shift record is based must be configured to include rounds. On-demand readings supplement the routine readings that are taken during shift rounds. Configuration rules for common log plans The narrative log in a standard shift record is duty station-specific and recognizes only the current duty station function. A common log is a shift record with a shared narrative log that is configured to recognize the duty station function and shift ownership status of all entry owners. A common log is typically used by members of the same shift team in place of duty station-specific narrative logs. Each entry in the common log specifies the function and shift ownership status of the entry owner. Shift team members continue to use their own shift records to document other shift activities, including shift rounds and team reviews. You use a specially configured duty station plan to generate common log shift records. The following rules apply: The common log plan must belong to the same site as the duty stations that are documented in the common log. If the common log plan is unit-specific, the function must be different from unit-specific team functions that use the common log. Two duty station plans with the same function, site, and unit cannot be used simultaneously to generate shift records. A shift editor group must be defined in the common log plan. The specified group must include all potential users of the common log, including shift owners and shift editors for the relevant duty stations. The Common Log check box must be selected. If required, you can exclude the narrative log from standard shift records by configuring the underlying duty station plans. In addition, to facilitate navigation to and from the common log shift record, you can add the common log as a team function in these duty station plans. Specifying Readings for Shift Rounds and Turnover In the duty station plan, you specify the readings that are required to monitor equipment performance and condition. Readings must be correctly specified to ensure compliance with plant and industry regulations, efficient organization of shift rounds, and proper assessment of new readings that are taken in the field. A measurement point or meter must be available for each reading. The action values or limits that are specified in the measurement points must be appropriate for the mode or modes of plant operation to which the duty station plan applies. The monitored component for each reading must be identified if the monitored component is different from the meter component. A reading frequency must be available for each routine or on-demand reading. In a standard duty station plan, you specify routine readings for shift rounds and readings for turnover. In an on-demand process plan, you specify on-demand readings. 16

16 During shift operations, routine and on-demand readings are integrated in the shift rounds process. Therefore, you must specify the frequency with which these reading types are taken. Readings for turnover are not subject to frequency rules. All readings require a meter component. The meter component can represent the measurement device or the monitored component. If the meter component represents the measurement device, you can specify the monitored component in a separate field. If you specify the monitored component, you can also specify conditions in which the component is exempt from reading requirements. Defining reading frequency Reading frequency records define the frequency with which the readings for shift rounds and on-demand processes must be taken. During shift operations, the due date and target time period for new readings are based on the associated reading frequency. You control reading frequency and due date calculations by defining active days and dates. You limit the timeframe for taking readings by defining a target time period. The target time period is an extension of the due date that is defined by the lead and lag hour values. The following restrictions apply when you create a reading frequency: You cannot use active dates unless the calendar period is fully defined. A fully defined calendar period includes a start date, start month, end date, and end month. You cannot specify the same active day for calendar periods that match or overlap. You must use the same entry to specify all target time periods for a specific day and calendar period. You cannot specify overlapping target time periods for the same or adjacent active days. Target time periods must be discrete. Specify frequencies as follows: 1. In the Reading Frequencies (Nuc) application, create a record. 2. Specify a record identifier and type a description. 3. In the Active Days and Dates table, define the reading frequency: a. Specify the week days on which the reading is taken. To specify a daily frequency within a calendar period, you must select all days of the week. b. If the specified week days are not active throughout the year, specify the active dates. 4. In the Target Time Period table, define one or more target time periods for the specified active days and dates. Defining readings 1. On the Duty Station Plan tab, configure the duty station plan for the type of readings that you want to define: Type of Reading Routine readings Readings for turnover On-demand readings Required Configuration Select Has Rounds. Select Has Rounds and Has Readings for Turnover. Select On-Demand Process. 17

17 2. On the Rounds and Bases tab, add a table row for each reading and specify the following details: a. If the reading applies to the turnover process, select For Turnover (aka Start of Watch). b. Specify a sequence number to define the order in which the reading is displayed relative to other readings in the list (normally the recommended physical route). c. Specify a measurement point or meter. If you specify a measurement point, the associated meter is automatically added. If the meter type is gauge, the warning and action limits are copied from the measurement point record. If the meter type is characteristic, the action values are copied. d. Specify the meter component. e. If the reading applies to the shift rounds process, specify the reading frequency. f. Optional: Specify the monitored component. g. Optional: Specify the conditions in which the monitored component qualifies for a reading exemption. h. If the reading satisfies a surveillance requirement, specify the relevant surveillance requirement record. Activating duty station plans To make a duty station plan available in the Duty Stations application for the creation of shift records, you must change the status of the duty station plan to Active. Duty station plan revisions If an active duty station plan requires changes, you create a duty station plan revision. Typically, you revise a duty station plan to reflect changes in the requirements for the duty station function. You create a revision by using the Revise Duty Station Plan action. This action is available only if the duty station plan has Active status. The new revision has the same record identifier and description as the existing revision, a different revision number, and a status of Pending Revision. The existing revision continues to function as an active duty station plan that can generate shift records. In the new revision, you can change the configuration settings and modify required readings. You activate the new revision by changing the status to Active. This status change is prohibited if the existing revision is associated with a shift record that has a status of In Progress or Turnover. You must complete the active shift record by stopping the duty station. After you stop the duty station, you can activate the new duty station plan revision. When you restart the duty station, the new revision is available for generating shift records. When the new revision is activated, the status of the existing revision changes to Revised. This revision of the duty station plan is retained as a history record that cannot be modified. You can view information about the current and previous revisions of a duty station plan by selecting the View Revision and Status History action. 18

18 If necessary, you can cancel a duty station plan that has Pending Revision status by selecting the Delete Duty Station Plan action. This action removes the new revision from the system, but has no effect on the existing revision. Equipment Monitoring Processes During shift operations, different processes are used to monitor equipment. These processes are defined in the duty station plan and implemented by shift owners in the associated shift records. Process data is added to the meter reading histories and to the operational histories for the relevant components. Readings for shift rounds and turnover In the duty station plan, you define the readings that are required for the shift rounds and turnover processes. For each reading, you specify the following information: Whether the reading applies to the shift rounds or turnover process (aka Start of Watch). If the reading applies to the shift rounds process, the frequency with which the reading is taken. Reading frequencies are defined in the Reading Frequencies application. A sequence number that defines the order in which the reading is displayed relative to other readings in the list (normally the recommended physical route). In the associated shift records, readings are sorted first by next due date and then by sequence number. Sequence numbers do not have to be unique. The meter or measurement point that is used to take the reading. Meters are defined in the Meters application, and measurement points are defined in the Condition Monitoring application. The component that is associated with the meter or measurement point. The associated component can be the measuring device or the monitored component. If the meter component is the measuring device, you can specify the monitored component separately. The association between a component and a meter is defined in the component record. The association between a component and a measurement point is defined in the measurement point record. If the reading is not required when the monitored component is in certain conditions, you can define reading exemptions. For example, you can define reading exemptions for periods when the monitored component is in standby mode or unavailable. During duty station shifts, the readings for shift rounds and turnover are subject to different rules. The following rules apply to the readings for shift rounds: The due date and target time period for each reading are automatically calculated based on information from the associated reading frequency. The target time period is an extension of the due date that is defined by the lead and lag hour values. All readings must be taken within the target time period or omitted. Reading omission is a distinct process action that is tracked. Shift turnover cannot be completed unless all readings that are due are taken or omitted. Readings for turnover are not subject to frequency rules and do not 19

19 affect turnover processing. Depending on local plant practice, turnover readings can be taken at the start or finish of the duty station shift. New readings must be committed before they are added to the shift record and meter reading histories. Readings that are saved but not committed are not processed or fully stored and they can be deleted from the shift record. Readings for on-demand processes You define the readings for an on-demand process in a specially configured duty station plan. During shift operations, these readings are integrated in the shift rounds process. Therefore, you must specify the frequency with which these readings are taken. You add on-demand readings to a duty station by adding the required on-demand process plan to the active shift record. The routine readings for the shift rounds process and the additional on-demand readings are tracked on separate subtabs in the shift record. However, on-demand readings are subject to the same frequency and tracking rules as routine readings. For example, an on-demand reading must be taken within the target time period that is defined in the associated reading frequency record. The shift owner cannot start the turnover process unless overdue on-demand readings are taken or omitted. Reading histories New readings that are committed, and any reading omissions, are tracked in the history that is maintained in the shift record for each reading. New readings that are committed are also added to the meter reading history for the meter component. You can access the meter reading history from the component or meter record. Reading omissions are not added to the meter reading history. Narrative log entries and operational history updates You can use the narrative log in a shift record to track events that result in a change of component position or condition. In each narrative log entry, you can add new position or condition details for one or more components. When the shift record is saved, the new position and condition details are automatically added to the operational histories for the relevant components. You use the PLUSOPCOND domain to define the condition values that are available for selection in shift records. The condition values in this domain apply to all components. You use the PLUSTAGPOS domain to define the position values that are available for selection in component records. In the component record, you must specify the position values that are allowable for the component. Only allowable positions can be used in clearance, lineup, and duty station processes. Managing Shift Cycles and On-demand Processes A shift cycle is a series of consecutive shifts that are based on the same duty station plan. You manage shift cycles by starting and stopping the duty stations for the required functions. When additional readings are required at an active duty station, you can add an on-demand process. 20

20 Starting a duty station As the owner of the first shift for a specific function, you select the required duty station plan to start the duty station. The start action initiates the first in a cycle of shifts that are based on the content of the selected duty station plan. The duty station plan for the new shift cycle must have a status of Active and you must be the incoming owner of the first shift in the cycle. The duty station plan that you select when you start the duty station specifies the requirements for the current mode of plant operations. The first and subsequent shift records in the shift cycle are all based on the same duty station plan. If the selected duty station plan specifies the requirement for prospective shift owners to hold one or more qualifications, the qualifications in your labor record must match. Similarly, if an additional role, such as fire brigade leader, is assigned to you for the shift period, the qualifications in your labor record must include the associated qualification. If your labor record does not include the required qualifications, you receive a warning. However, you are not prohibited from starting the duty station. You start a Duty Station as follows: 1. In the Duty Stations application, click Start Duty Station in the application toolbar. 2. In the Start Duty Station window, provide a summary of the duty station start event. 3. If an additional role is assigned to you for the shift period, specify the additional role. 4. Select an active duty station plan for the new shift cycle. The first shift record in the shift cycle is generated and is shown on the Duty Station Shift tab. The default status for new shift records is In Progress. Directing Shift Operations While shift operations are in progress, you can direct and communicate with shift personnel by creating objectives and notifications. In their shift records, shift owners can view and change the status of objectives, and acknowledge receipt of notifications. Site and unit objectives You define operating goals for shift owners in sites or units by creating objectives. Shift owners can view and change the status of approved objectives in their shift records. You create objectives only in the Objectives application. In each objective, you specify the details of an operating goal and the target timeframe for execution. For example, you can define an objective to communicate the need to change the mode of plant operation by a specific date. You can create an objective at the level of site or unit. The values for site and unit determine where the objective is displayed when it is approved: An objective that applies at the unit level is displayed in active shift records that have a matching unit or secondary unit, or shift records for the parent site that have no unit. 21

21 An objective that applies at the site level is displayed in all active shift records that have a matching site. All shift owners can view objectives in their shift records. However, only authorized shift owners can provide status updates. You can grant authorization by selecting the Reports on Objectives check box in the relevant duty station plans. You can also change the status of an objective in the Objectives application The following status change rules apply: When a shift owner changes the status of an objective to Active, the actual start date for implementation of the objective is defined. When a shift owner changes the status of an active objective to Completed, the actual finish date for implementation of the objective is defined. Notifications for individual users You can communicate requirements and information to individual shift owners by creating notifications and assigning them to the appropriate users. Shift owners receive and acknowledge notifications in their shift records. The assignment and completion data for all assigned users is tracked in the notification. You create notifications in the Notifications application to communicate different types of information to one or more users. For example, you can create a notification to communicate orders to all members of a shift team, or to communicate function-specific information to an individual shift owner. You can create a notification at the level of site or unit. The values for site and unit determine where the notification is displayed when the notification has a status of Approved or In Progress, and the current date is earlier than the expiration date: A notification that applies at the unit level is displayed in active shift records that belong to the assigned users and have a matching unit or secondary unit. A notification that applies at the site level is displayed in active shift records that belong to the assigned users and have a matching site. A shift owner must acknowledge a notification by entering a completion date in the shift record that contains the notification. After the completion date is specified, the notification is removed from the shift record unless the current date is earlier than the expiration date. If the current date is earlier than the expiration date, the completed notification is displayed until the expiration date is reached. Completion data for all assigned users is tracked in the Notifications application. Users with authorization to access the Notifications application can also review and acknowledge their notifications in this application. For example, authorization of this kind might be required by shift owners post-vacation who need to review all outstanding notifications before they go on shift duty. Condition Reporting You report component or process issues for the duty station by creating condition reports. You can also view existing condition reports for the site or unit that require an operations shift review. 22

22 You can create a condition report from the shift record, an equipment reading, or a narrative log entry. Shift record Use the Create Condition Report action. The new condition report includes information about the originating shift record. Routine, on-demand, or turnover reading Before you commit the reading, select the Condition Report check box in the reading details. Alternatively, if the new reading value matches the action values or exceeds the limits that are specified in a measurement point, you are automatically prompted to create a condition report. In both cases, the condition report is created after you commit the reading. The new condition report includes information about the originating shift record and the reading. Narrative log entry Click the Create/Relate Condition Report icon in a new or existing entry to associate the entry with a new or existing condition report. New condition reports include information about the originating shift record and narrative log entry. In the shift record, you can view a list of condition reports for the site that require an operations shift review. This list is available in the shift record only if the Show Condition Reports check box is selected in the underlying duty station plan. Shift Execution A shift worker is regularly assigned to work shifts at the duty station for his or her function. The shift worker executes each shift by fulfilling the requirements that are specified in the shift record. At the end of the shift, the shift worker turns the duty station over to the next shift owner. Starting the shift If the duty station for your function is inactive, you initiate a shift cycle in the Duty Stations application by selecting the required duty station plan. If multiple duty station plans exist for your duty station, the required duty station plan is the one that is appropriate for the current mode of plant operation. A shift record for the first shift in the cycle is generated from the selected duty station plan. If the duty station is active, the shift record for your shift is generated when the turnover process is completed by the previous shift owner. In the Duty Stations application, on the List tab, you filter by function, site, and unit to locate and open this shift record. On the shift record, you are identified as the shift owner. 23

23 Reviewing and responding to notifications If the shift record includes any notifications that are assigned to you, you review the content of the notifications and take the required action. You enter a completion date for each notification in the shift record. The completion dates that you enter in the shift record are automatically added to the relevant records in the Notifications application. Conducting shift rounds If the shift record includes a shift rounds process, you take the required readings when they are due. If additional readings are required to supplement the routine readings that are taken during shift rounds, you can add an on-demand process to the duty station. The process remains active for the current shift and subsequent shifts until it is manually removed by a shift owner or until the duty station is stopped. While the process is active, you must take the required on demand readings when they are due. The subtabs in the Rounds tab show the routine and on-demand readings that are due to be taken next at the duty station. By default, readings are sorted first by due date and then by sequence number. If multiple readings have the same due date, these readings are sorted by sequence number. The lists on both subtabs can include readings that are optional because of current reading exemptions. These optional readings have no due date and they are listed after the readings that are due. If the new reading value matches a characteristic action value or exceeds the acceptable limits for gauge meter readings, you are automatically prompted to generate a condition report. You can also initiate this process manually. In both cases, the condition report that you create is identified in the shift record reading history, and includes a reference to the originating reading, shift record, and duty station function. You must commit new readings individually to complete the condition report process for the relevant readings, and to save the reading details to the shift record and meter reading histories. Uncommitted readings can be manually deleted from the shift record. The process is as follows: 1. In the Duty Stations application, select a shift record and go to the Rounds tab. 2. Enter the details for each new reading: a. Select the appropriate row and specify the time when the reading was taken. If you do not specify a time, the current time is automatically specified. b. Enter the new reading value. c. If you are prompted to generate a condition report, click Yes or No. d. Optional: Enter remarks about the reading. The remarks that you enter are added to the shift record and meter reading histories and, where applicable, to the associated condition report. e. Optional: To request a condition report, expand the row and select Condition Report. f. Click the Commit icon to confirm the new reading details. g. If you requested or confirmed the requirement for a condition report, review and supplement the information in the Create Condition Report window and then click OK. 24

24 3. To omit readings that are overdue or cannot be taken, select Omit Readings from the Select Action menu. Select the readings that you want to omit and click OK. When you commit a new reading, a new entry is added to the reading histories that are maintained in the shift record, the meter component record, and, where applicable, the measurement point record. In the reading histories, you are identified as the reading inspector. This rule applies whether you are the owner of the current shift record or a shift editor who is acting on behalf of the shift owner. Reading omissions are tracked only in the reading history that is maintained in the shift record. Rules for conducting shift rounds During shift rounds, you take the routine and on-demand readings that are specified in the Rounds tab and enter new reading details in the shift record. You must observe the rules that apply to both tasks. The following rules apply to routine and on-demand readings: Each reading must be taken unless a reading exemption applies. Each reading must be taken within the target time period. A reading that is not taken within the target time period must be omitted. Reading omission is a separate process that is tracked in the shift record. A reading can be omitted before, during, or after the target time period. A reading that is subject to a reading exemption is optional and can be skipped or taken as a supplemental reading. An exemption applies only if the monitored component is in a condition that is designated for exemption. Exempt conditions are defined in the duty station plan. When you enter new reading details, you must specify the time when the reading was taken. You can specify a time that is current or in the past. To fulfill the reading requirement, the specified time must be within the target time period. If you specify a time that is earlier or later than the target time period, the new reading is classed as supplemental data that does not fulfill the requirement. You must enter another new reading for the target time period or omit the reading. You cannot start or complete shift turnover if the shift record includes readings that are overdue. Before you proceed with shift turnover, you must omit or retrospectively enter details for any readings that are overdue. Maintaining the narrative log If the shift record includes a narrative log, you use it to maintain a record of the events and actions that occur during the shift period. To maintain an accurate account of duty station events, actions, and status, you create entries in the narrative log. You can also use the narrative log to update the operational history of duty station components and to start the condition report process for nonstandard conditions. The shift record must have a status of In Progress or Turnover. You must own or have shift editor access to the shift record. 25

25 In an active shift record, you can create stand-alone entries or entries that relate to existing entries. You create related entries to follow up on, complete, or correct existing entries. The follow-up and correction statuses of the existing entry determine which related entries you can create. Use the following procedure: 1. In the Duty Stations application, select a shift record and go to the Narrative Log tab. 2. Create an entry: 3. In the Event Details field, enter the required narrative. 4. Specify an event time. If you do not specify an event time, the current time is automatically specified. 5. To designate an entry for follow-up action, change the follow-up status to Required. This designation is a prerequisite for the creation of follow-up or completion entries. 6. Optional: Specify the entry type. 7. To add component information to the entry, select the required assets and locations. For each component, specify a new condition, a new position, or both. 8. To associate the entry with a new or existing condition report, click the Create/Relate Condition Report icon. When prompted, click Yes to create a condition report or No to select an existing condition report. The associated condition report is identified and linked in the entry details. 9. Save the entry. If the new entry includes component information, the operational history of the relevant components is updated with new condition and position details. If the new entry is designated for follow-up action, it is displayed in both the All Entries table and the Entries that Require Follow-Up or Completion table. In Entries that Require Follow-Up or Completion table, define the priority of the new entry relative to other open items. Rules for maintaining the narrative log The narrative log is a series of entries that is created by successive shift owners and other authorized users to describe events and actions at a duty station. To use the narrative log effectively, you must be familiar with the rules for creating entries. A shift record that has narrative log capability includes a narrative log for the duty station and a narrative log team view. The team view is a composite view of the narrative logs 26