Configuration Items (Nuc)
A configuration item (CI) is any component that is under configuration control. This may be an asset, location, item or service, but it might also be a document. A CI can have a classification whose attributes can be used to define the configuration. A CI can be related to other CIs but an asset or location can only have one related CI record. Most often CIs are associated with technology infrastructure.
Used to create a relationship type that describes a dependency or connectivity point between multiple assets or configuration items. A relationship can be unidirectional or bidirectional.
A collection is any set of configuration items, asset or locations. Most often used to control access to these records through an object data restriction defined in the Security Groups application. Can add records to a service request or work order by selecting them from a collection. Can be easily added to the advanced search of applications to find the records associated to the asset, locations or CIs in a collection.
Clearances are used by operations to tag and/or isolate plant equipment prior to work or surveillance tests. It controls the process through the application of the tags, handover to the work supervisors, then after maintenance releases the clearance back to operations the restoration of the plant equipment to the required positions and the removal of the tags.
Clearances Kiosk (Nuc)
Clearances Kiosk is used by plant operators on the floor during the application and restoration of clearance tags and component positions. The application can be used by multiple users as part of the same Maximo session, for example, one operator may apply the tag, and another operator provides independent verification of this action.
Lineup Plans (Nuc)
A lineup plan specifies the approved operational configuration details of plant equipment components and component positions that are required for particular operating or test procedures and maintenance activities. Lineup groups provide an execution plan and sequence for complex lineups. A lineup plan is a template for a lineup.
Lineups provide the tracking of component positioning as part of operator walk-downs and clearance and tagging operations, it is an instance of a particular lineup plan. The lineup controls the sequencing of the changes to the component positions and of their independent verification as part of plant validation activities.
Reading Frequencies (Nuc)
Reading Frequencies define when readings are taken for each point in a Duty Station’s Rounds or on-demand processes. You specify the active days and dates in a specified number of cycle weeks.
Lineups Kiosk (Nuc)
Lineups Kiosk is used by operators on the floor who need to record the positions they have configured or independently verify component positions that have been configured by other operators. The application can be used by multiple users as part of the same Maximo session.
Impact Plans (Nuc)
An impact plan defines the impact on operations and maintenance as a result of performing a job plan on a location or asset. An impact plan is related to a PM or applied to a work order. It might, for example, indicate the permits that are required or the retest work that needs to be performed.
LCO Tracking (Nuc)
Limiting Conditions for Operations (LCOs) may be planned as part of maintenance or unplanned when there are equipment issues. When an LCO occurs, you link the event to appropriate tech specs, and manage the regulated actions defined by the technical specifications including retest work.
Duty Station Plans (Nuc)
A duty station is a role-based function performed on a unit across multiple shifts. It is specific to plant modes of operation. The duty station plan identifies the configuration for a duty station, for example, it identifies the meter, measurements and observations to be recorded as part of a duty station round.
Duty Stations (Nuc)
A duty station can be considered a log book and is based on the configuration defined for it by the duty station plan. It is where the meter readings and measurements of rounds are recorded, a narrative log is maintained, unit status updated, etc. There is a turnover process from one shift to the next.
A notification is a message that must be communicated to, and acknowledged by, a set of recipients. A notification might comprise new information that must be reviewed by duty station shift personnel or an action that must be taken and confirmed by designated staff members.
An objective is an order or requirement that needs to be completed during a shift operation, for example change plant mode or complete physical tests.
Tech Specs (Nuc)
A technical specification is a regulated document that defines the requirements for safe operation of a nuclear plant. A tech spec record details a part of the technical specification and the actions to be performed and the surveillance requirements to be followed when there is Limiting Condition for Operation (LCO).
Surveillance Requirements (Nuc)
Surveillance requirements are tests, observations, or activities that prove that the requirements of an internal or external regulation are being satisfied. Surveillance requirements are associated with tech spec records.
An event record identifies plant events and the response to take when the event occurs. For example, an alarm, an equipment trip, or other control room indicators. Events can be related to impact plans and work orders.
Clearance Groups (Nuc)
Clearance groups can be used to better facilitate tag sharing on clearances by linking a clearance to a clearance group. The clearance group might identify clearances associated with a particular operating cycle or used in a refueling outage.
Work permits are used for plant operations, engineering activities as well as maintenance, and they can exist stand-alone or be related to a work order. Work permits can be generated automatically when a preventive maintenance record with a related impact plan generates a work order. A permit can create a clearance request and be involved in clearance processes similar to that for a work order.
Quick Permits (Nuc)
Quick Permits has a subset of the functionalities in the Permits application. Quick Permits have a focus on the tasks and requirements of the permit, rather than the planning of the permit and there is no ability to create a clearance request from this application.
Job Plans (Nuc)
A job plan is a template for a work order. The application allows you to define the tasks and labor, material, service and tool requirements needed to fulfil the job plan and its tasks. A job task can have a classification and can reference another job plan thereby creating a multi-level hierarchy when applied to a work order.
A route is a set of locations and assets that are used in inspections and maintenance. Often the inspection or work to be performed at each route stop is the same, but a route stop can also reference a job plan.
Asset List (Nuc)
An asset list is a group of locations and assets which is applied to a commitment in the Commitment Tracking application. The work to be performed as part of the commitment is defined with a job plan.
Data Sheet Template
A data sheet template is used in instrument calibration. It defines the asset functions, input ranges, expected output ranges and tolerances that determine limits of adjustment or failure when calibrating instruments or instrument loops as part of a calibration work order.
Equipment Groups (Nuc)
An equipment group is any grouping of locations for functional, operational, scheduling or other purposes. Boundary equipment groups are used to identify the components involved in various clearance scenarios depending on plant modes.
The Hazards application can be used to define a hazard and the precautions needed to mitigate the hazard or a hazardous material. The application also shows associated tag outs for locations and assets.
Used to create a library of precautions which are associated with hazards or added to safety plans. Additional precautions can be added to a work order to mitigate a hazard.
Lock Out / Tag Out
This application provides the ability to define the lock out operations on assets and locations and the sequence required in order to safely isolate (tag out) another asset or location.
The safety plan collects together the hazard and their precautions, hazardous material and lock out / tag out operations to safely service a set of work assets and locations. A safety plan can be associated with a job plan and the work assets so that it is automatically applied when the job plan is applied to a work order for the referenced asset or location.
Preventive Maintenance (Nuc)
The Preventive Maintenance (PM) application is used to create a template for routine maintenance or inspection of an asset, location or a set of assets defined with a route. The frequency in which the work orders are generated can be time or meter based or a mix of each whichever comes first. When the work order is generated a job plan is applied, but a different job plan can be applied depending on the sequence of work order generation, for example a different job plan is used for the yearly maintenance to that used each quarter. PM records are also used as a template for surveillance testing.
A master PM is a template for a PM record. It defines the frequencies, seasons and job plan sequences and the defaults for the work orders. A master PM is linked to a rotating item and then a PM can be generated for all the locations and assets (including tool assets) which are linked to that item. If the master PM is updated the associated PMs can also be updated.
PM Frequencies (Nuc)
A PM Frequency record is a template for time-based frequencies used on preventive maintenance records. They represent the standardized frequencies defined in technical specifications for surveillance testing.