86
SC23-8876-00 Version 6.3 Maximo User’s Guide Addendum IBM Maximo for Nuclear Power

Maximo User’s Guide Addendum - IBMpublib.boulder.ibm.com/tividd/td/ITMfNPw/SC23-8876-00/en... · 2008-02-05 · SC23-8876-00 Version 6.3 Maximo User’s Guide Addendum IBM Maximo

  • Upload
    phamtu

  • View
    220

  • Download
    0

Embed Size (px)

Citation preview

SC23-8876-00

Version 6.3

Maximo User’s Guide Addendum

IBM Maximo for Nuclear Power

This edition applies to version 6, release 2, modification 1 of IBM Maximo for Nuclear Power and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces any previous edition of this document.

Portions © 1996-2005, i-net software GmbH

Portions © 2007 Intrinsyc Software Inc. and its licensors

Portions © 2001-2003 PowerTeam, Inc.

Portions © 1996-2003 Visual Mining, Inc. Visual Mining NetCharts Server provided by Visual Mining, Inc.

Sentry Spelling-Checker Engine Copyright © 2000 Wintertree Software Inc.

© Copyright International Business Machines Corporation 2007. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

NoteBefore using this information and the product it supports, read the information in “Notices” on page 73

© Copyright IBM Corp. 2007 iii

About This Publication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiAudience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiIBM Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1: Introducing Maximo for Nuclear Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2: Administration Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Organizations (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Organizations (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 3: Contracts Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Terms and Conditions (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Terms and Conditions (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 4: Inventory Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Inventory (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Inventory Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Inventory (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Item Master (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Item Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Qualifications Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Item Master (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 5: Operational Management (Nuc) Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Clearances (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Clearance Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Related Records Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Application Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Restoration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Sign On/Off Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Clearances (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Impact Plans (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Operational Impacts Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Maintenance Impacts Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Associations Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Impact Plans (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Tech Specs (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Tech Specs Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Tech Specs (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Surveillance Requirements (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Contents

iv IBM Maximo for Nuclear Power: User’s Guide Addendum

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Surveillance Requirements (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Events (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Events (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 6: Plans Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Asset List (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Asset List Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Asset List (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 7: Preventive Maintenance Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Preventive Maintenance (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22PM Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Frequency Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Seasonal Dates Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Job Plan Sequence Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23PM Hierarchy Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Surveillance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23References Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Preventive Maintenance (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Frequency (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Frequency Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Seasonal Dates Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 8: Purchasing Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Purchase Requisitions (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25PR Lines Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Terms and Conditions Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Purchase Requisition (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Purchase Orders (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27PO Lines Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Terms and Conditions Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Purchase Orders (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Request for Quotation (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28RFQ Lines Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Vendors Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Request for Quotation (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Terms and Conditions (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Terms and Conditions (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Companies (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Qualifications Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Items Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Companies (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 9: Work Orders Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Quick Reporting (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Quick Reporting Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Quick Reporting (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Commitment Tracking (Nuc) Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Contents v

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Review Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Work Package Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Work Order Tracking (Nuc) Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Work Order Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Plans Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Clearance Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Related Records Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Actuals Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Safety Plan Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Impact Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Failure Reporting Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38SNPM Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Work Order Tracking (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Sign On/Off (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Sign On/Off (Nuc) Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 10: Assets Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Assets (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41SNPM Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Positions Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Locations (Nuc) Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

SNPM Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Positions Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 11: Nuclear Database Tables and Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Nuclear-Specific Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

PLUSASSETPOS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45PLUSASSETRC Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45PLUSCLEARANCE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45PLUSCLHIER Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47PLUSCLLOG Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47PLUSCLSTATUS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47PLUSCLTAGLINK Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47PLUSCOMPAUDIT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48PLUSCOMPITEM Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48PLUSCOMPSTATUS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48PLUSCOMPTERM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49PLUSCRAFTAPPR Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49PLUSCTREVIEW Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49PLUSDRILLDOWN Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49PLUSEVENT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50PLUSIMPACT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50PLUSIPASSOC Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50PLUSIPCOORDINATE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51PLUSIPEVENT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51PLUSIPLOG Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51PLUSIPMTSTATUS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52PLUSIPOPSTATUS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52PLUSIPPERMIT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52PLUSIPRETEST Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52PLUSIPTS Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53PLUSIPUNVASSET Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

vi IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSIPUNVTASK Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53PLUSITEMTERM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53PLUSLOCPOS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53PLUSLOCRC Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54PLUSMTIMPACT Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54PLUSPMREF Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54PLUSPMSR Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54PLUSRESTPOS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55PLUSSIGNONOFF Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55PLUSSR Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55PLUSTAG Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56PLUSTAGSTATUS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57PLUSTERMSTATUS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57PLUSTS Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57PLUSTSSR Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58PLUSWOASSET Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58PLUSWOCLLINK Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58PLUSWOTAGLINK Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Modified Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60ASSETS Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60COMPANIES Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60EQUIPMENT Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60INVENTORY Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60ITEM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60LOCATION Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60LOCATIONS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61PM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61PMSEQUENCE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62POTERM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62PRTERM Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62RFQTERM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62RFQVENDORTERM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62TERM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63WOGEN Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63WORKORDER Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 12: Standard Nuclear-Process Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Generating Site Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Setting up Person Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Validate, Enable, and Activate the Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Workflows Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Single Point of Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Plant SSC Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Work Order Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Facilities Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Item Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

How it Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Start Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Key Performance Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

© Copyright IBM Corp. 2007 vii

About This Publication

This section explains how this guide can help you to use IBM® Maximo® for Nuclear Power. It also provides information about other IBM Corporation resources available to you, such as additional documentation and support.

Audience

If you are a Nuclear Power customer, read this guide for information on how to use Nuclear.

Related Documentation

For more information about Nuclear and Maximo, refer to the following documentation:

Document Description

IBM Maximo for Nuclear Power Installation Guide

Is a separate document delivered in Adobe® Acrobat® Portable Document Format (PDF) with the product software. The guide is used to install Nuclear.

IBM Maximo for Nuclear Power Online Help

Is the primary source of information for using the Nuclear application.

IBM Maximo Finance Manager’s Guide Describes how IBM Maximo completes financial transactions and how to set up general ledger accounts.

IBM Maximo Installation Guide Describes how to install and configure the following software:

Application serverIBM MaximoActuate®

IBM Maximo Multisite Administrator’s Guide

Describes how to configure IBM Maximo for a Multisite implementation.

IBM Maximo Online Help Provides step-by-step procedures for IBM Maximo applications.

IBM Support

viii Cover Product Name: Deliverable Type/Document Title

IBM Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. For information about the types of maintenance contracts available, see "Enhanced Support," in the Software Support Handbook at techsupport.services.ibm.com/guides/services.html.

Complete the following steps to contact IBM Software Support with a problem:

1 Define the problem, gather background information, and determine the severity of the problem. For help, see "Contacting IBM" in the Software Support Handbook at techsupport.services.ibm.com/guides/beforecontacting.html.

2 Gather diagnostic information.

3 Submit your problem to IBM Software Support in one of the following ways:

a Online: Click the Report problems tab on the IBM Software Support site: www.ibm.com/software/support/probsub.html.

b By telephone: For the telephone number to call in your country, go to the Contacts page of the Software Support Handbook: techsupport.services.ibm.com/guides/contacts.html.

IBM Maximo Reconciliation Module Implementation Guide

Describes how to use the IBM Maximo Reconciliation module to reconcile the two types of information that IBM Maximo maintains about information technology (IT) assets: IT asset data and deployed asset data.

IBM Maximo Report Administration and Development Guide

Describes how to use Actuate to design and administer IBM Maximo reports.

IBM Maximo System Administrator’s Guide

Describes database configuration, security, and other administrative level applications and tasks.

IBM Maximo User’s Guide Provides an overview of the Maximo end user applications. It also describes how the IBM Maximo applications interact with each other.

IBM Maximo Workflow Implementation Guide

Provides information about how to use IBM Maximo to plan, design, build, test, implement, and manage Workflow processes.

IBM Maximo Enterprise Adapter (MEA) System Administrator's Guide

Describes how to configure and use the IBM MEA.

Document Description

IBM Support

ix Cover Product Name: Deliverable Type/Document Title

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support web site daily, so that other users who experience the same problem can benefit from the same resolution.

IBM Support

x Cover Product Name: Deliverable Type/Document Title

© Copyright IBM Corp. 2007 1

Purpose You use Maximo for Nuclear Power to meet Nuclear Regulatory Commission (NRC) requirements, including surveillances, commitment tracking, and clearances.

Nuclear provides the necessary tools to meet all NRC requirements and additionally, to implement the Standard Nuclear Performance Model (SNPM) as defined by the Nuclear Energy Institute (NEI) and the Institute for Nuclear Power Operations (INPO) as they exist as of June 2004. This product will be improved as required to support changes to SNPM.

Nuclear has many enhancements incorporated into the base Maximo product. These enhancements let you incorporate nuclear-related features such as the following into your daily use of Maximo:

create surveillancesvalidate the suitability of a vendortrack commitmentsestablish clearancesimplement impact plans

This release includes several new applications developed specifically for operational management of nuclear facilities. The new applications are:

Clearances (Nuc)Events (Nuc)Impact Plans (Nuc)Sign On/Off (Nuc)Surveillance Requirements (Nuc)Tech Specs (Nuc)

Several other nuclear-specific applications are cloned, or copied, from standard Maximo applications in order to add nuclear-specific options to these applications. These applications are available only to users of Nuclear. (The base applications remain in the product. The Nuclear-specific clone or base application can be made available to different users in your organization depending upon their needs.)

Complete List of Nuclear-Specific Applications

Assets (Nuc) Asset List (Nuc) Clearances (Nuc)Commitment Tracking (Nuc) Companies (Nuc) Events (Nuc)Frequency (Nuc) Impact Plans (Nuc) Inventory(Nuc)

Introducing Maximo for Nuclear Power 1

2 IBM Maximo for Nuclear Power: User’s Guide Addendum

Item Master (Nuc) Locations (Nuc) Organizations (Nuc) Preventive Maintenance (Nuc) Purchase Orders (Nuc) Purchase Requisitions (Nuc) Quick Reporting (Nuc) Request for Quotations (Nuc) Sign On/Off (Nuc) Surveillance Requirements (Nuc) Tech Specs (Nuc) Terms and Conditions (Nuc) Work Order Tracking (Nuc)

© Copyright IBM Corp. 2007 3

Overview The Administration module has one cloned application. This chapter provides an overview of the actions added to the Organizations (Nuc) application. For more information, refer to the application’s help. You also can refer to the IBM Maximo User’s Guide for more information about any standard Maximo application.

The Administration module contains the following Nuclear-specific application:

Organizations (Nuc) Application

Purpose You use the Organizations (Nuc) application to set up the organizations and sites to use with Maximo. You must define at least one organization and one site.

For each organization, you specify a number of properties including the following:

Base currencyItem and company setsGL clearing accountAddress codes for organizational units, including sites, that you can use on Maximo records

By configuring Maximo with multiple organizations and sites, your company can run Maximo in multiple facilities all from the same database. Each site can access its own site-specific data and leverage data that is common across sites. Rather than installing multiple instances of Maximo, each with its own database, a company can install Maximo once, with different sites all accessing the same database via a Web browser.

Maximo's architecture enables different organizations and sites to keep some parts of their operations separate, while sharing others. For example, different facilities can share purchase agreements and vendors, and share and transfer items, while keeping work order and job plan data separate.

Organizations and sites are logical divisions of a company determined by what types of operations are performed at different locations, and what data can be shared among them.

Organization An organization is a major division of a company that contains one or more sites. Sites belonging to the same organization must use the same currency and share the same options for work orders, assets, labor, and certain other types of data.

Administration Module 2Application Nuclear Function

Organizations (Nuc) Set the nuclear MAXVARS.

Organizations (Nuc) Application

4 IBM Maximo for Nuclear Power: User’s Guide Addendum

Site A site is a subdivision of an organization that can track inventory and other data separately from other sites. Certain types of information are unique to a site and not visible to other sites within the organization.

Application Options Using the Organizations (Nuc) application you set defaults for nuclear system level options relating to Maximo purchasing. You access these options from the Select Action menu. The How Do I topics in the Organizations (Nuc) help cover these options. You can also access the help from the associated dialog box. For information about a particular action, refer to the corresponding Help topic .

Nuclear options let you perform the following tasks:

Specify what action Maximo takes when a part is ordered from a non-qualified vendorSpecify whether or not to automatically re-order quality items

Organizations (Nuc) Actions

The Organizations (Nuc) application has the following Nuclear-specific action:

Nuclear System Options

For information about this action, refer to the Organizations (Nuc) help.

© Copyright IBM Corp. 2007 5

Overview The Contracts module has one cloned application. This chapter describes the cloned application. For more information about any application, refer to the application’s help. You also can refer to the IBM Maximo User’s Guide for more information about any standard Maximo application.

The Terms and Conditions module contains the following Nuclear-specific application:

Terms and Conditions (Nuc) Application

Purpose You use the Terms and Conditions (Nuc) application to enter and maintain a library of terms and conditions. These terms can contain information such as liability concerns, shipping and handling details, or delivery time expectations.

The application uses three types of terms:

Commercial terms that can be added to a purchasing document or a contractQuality terms that can be associated with a companyTechnical terms that can be associated with an item

The Commercial terms entered in the Terms and Conditions (Nuc) application are available from the Terms and Conditions tabs in purchasing, contract, companies and item master applications. Quality terms are available only in Companies, and Technical terms are available only in Item Master.

The Terms and Conditions (Nuc) application has the following new fields:

Vendor Qual TypeRevision #StatusStatus DateChange ByMemo

For information about fields, place the cursor in the field and press Alt + F1.

Contracts Module 3Application Nuclear Function

Terms and Conditions (Nuc) Used to enter and maintain a library of terms and conditions.

Terms and Conditions (Nuc) Application

6 IBM Maximo for Nuclear Power: User’s Guide Addendum

Terms and Conditions (Nuc) Actions

Terms and Conditions (Nuc) has no Nuclear-specific actions.

© Copyright IBM Corp. 2007 7

Overview The Inventory module has two cloned applications. This chapter describes the cloned applications. For more information about any application, refer to the application’s help. You also can refer to the IBM Maximo User’s Guide for more information about any standard Maximo application.

The Inventory module contains the following Nuclear-specific applications:

Inventory (Nuc) Application

Purpose You use the Inventory (Nuc) application to enter, display, and update information on each inventory item. The addition of Procurement Class at the item level, in addition to the asset level, permits you to easily and quickly identify the quality level of all replacement parts. The new Auto-buy? field permits the use of Workflow to bypass the procurement engineering group (PEG) process for items previously identified by procurement engineering that no longer require PEG review prior to procurement. Special order and nonstocked items as well as stocked items can be tracked. You can view information both for master inventory items and for items at a specific storeroom location. You can track vendors that supply an item, and item balances down to the bin and lot level for each storeroom. The ability to capture the vendor's catalog number aids in the ability of PEG to readily identify like-kind replacements.

Most of the fields on the Inventory tab refer to item/location records. Current Balance, for example, means the current balance of the item at the storeroom in the Storeroom field. Like Current Balance, the fields listed under Balance Summary, Issue History, and Balances all apply to the item in a specific storeroom.

If an item is stored in more than one storeroom location you can select View Availability from the Select Action menu to view balances for all storeroom locations on one screen.

You can also use ABC Analysis to prioritize an item's usefulness and the financial benefit from investing in the item.

Inventory Module 4Application Nuclear Function

Inventory (Nuc) To enter, display, and update information on each inventory item.

Item Master (Nuc) To define items that will be stocked in your storerooms.

Item Master (Nuc) Application

8 IBM Maximo for Nuclear Power: User’s Guide Addendum

Tabs

The Inventory (Nuc) application has the following new or enhanced tab:

Inventory

Inventory Tab

Use the Inventory (Nuc) application to enter, view, or modify item balances, costs, balances, bins and lots, and to view storeroom locations where the item is stocked.

You can also track items (stocked, nonstocked, and special order items) by checking storeroom balances. When stock falls below a specified reorder point, the balances let you know when and what quantities to reorder.

Using ABC Analysis lets you prioritize an item's usefulness and the financial benefit from investing in the item.

Inventory (Nuc) Actions

The Inventory (Nuc) application has no Nuclear-specific actions.

Item Master (Nuc) Application

Purpose You use this application to define items that will be stocked in your storerooms. When you create an item record you can define the type of stock the item is, whether it is lotted or non-lotted, associate Hazards and Material Safety Data Sheets (MSDS) with the item, define the item as rotating assets, and identify alternate items that can be used as substitutes for the item.

The Auto-buy field may be set at the Item Master level, but can be overridden at the Item level. This accommodates mixed fleets (fossil and nuclear) and the support of a common Item list for several nuclear plants which might be of mixed types (BWR and PWR) and for fleets that resulted from mergers and acquisitions.

You can also define other information related to items, such as the storeroom locations that stock the item, Item Specification, Item Assembly Structures, and documents outside of Maximo that relate to the item record.

Tabs

The Item Master (Nuc) application has the following new or enhanced tabs:

ItemQualifications

Item Tab

You use the Item tab to add records for items that your organizations use and that you stock in storerooms. Examples of items include materials, supplies, assets,

Item Master (Nuc) Application

Inventory Module 9

software, and hardware. After you create an item record on this tab, you can refer to it on a work order or in an Item Assembly Structure (IAS). The same principle applies to purchase requisitions, purchase orders, request for quotes, and job plans.

Examples of attributes that you can associate to an item include commodity codes and groups, meters and meter groups, lot type, material safety data sheets (MSDS), and the issue and order unit. You can also specify whether the item is outside, capitalized, rotating, condition-enabled, part of a kit, used as a spare part, is to be inspected on receipt, and is to be attached to parent asset when issued.

In the Alternate Items table window, you can add, view, modify, or delete a list of other items that you can use interchangeably with this one. Items can have one or more alternate items. The table window displays the item number and description of interchangeable items.

In the Condition Codes table window, you can add, view, modify, or delete a list of condition codes for this item, if the item is condition-enabled.

The Item tab has the following new field:

Qualified Vendor

For information about a field, place the cursor in the field and press Alt + F1.

Qualifications Tab

Use the Qualification tab to add or modify technical terms to an item.

The Qualifications tab has the following new fields:

TermDescriptionRevision #

For information about a field, place the cursor in the field and press Alt + F1.

Item Master (Nuc) Actions

The Item Master (Nuc) application has no Nuclear-specific actions.

Item Master (Nuc) Application

10 IBM Maximo for Nuclear Power: User’s Guide Addendum

© Copyright IBM Corp. 2007 11

Overview The Operational Management module has five applications specific to Nuclear. This chapter provides an overview of these applications. For more information on any application, refer to the application help. You also can refer to the IBM Maximo User’s Guide for more information about any standard Maximo application.

The Operational Management module contains the following applications:

Clearances (Nuc) Application

Purpose Clearances provide for personnel and equipment safety, plant configuration control, and full management and accountability for all personnel associated with Clearance protection. You use the Clearances (Nuc) application to:

Establish a safe boundary for plant maintenance and testing personnel to perform assigned tasks.Control plant configuration. Clearances may remove systems from availability which affect the operational status of a plant.

Tabs

The Clearances (Nuc) application has the following tabs:

ClearanceRelated RecordsApplication

Operational Management (Nuc) Module 5

Application Nuclear Function

Clearances (Nuc) To establish safe working zones.

Impact Plans (Nuc) To define the operational and maintenance impacts related to planned maintenance work.

Tech Specs (Nuc) To create and maintain tech specs and their associated data.

Surveillance Requirements (Nuc)

To identify actions that must take place to ensure compliance with a technical specification.

Events (Nuc) To identify expected plant events and the appropriate responses to perform when the events occur.

Clearances (Nuc) Application

12 IBM Maximo for Nuclear Power: User’s Guide Addendum

RestorationSign On/OffLog

Clearance Tab

You use the Clearance tab to view or edit information related to the clearance. It lists who created the clearance and when, as well as scheduling information on the clearance.

Approval information, for both the application and restoration is also listed.

Related Records Tab

You use the Related Records Tab of Clearances (Nuc) to view or edit information on any related work orders or PMs and any child clearances.

Application Tab

You use the Application Tab of Clearances (Nuc) to view or edit tag application information for tags on the clearance. This tab includes any relevant information on the tag such as:

Indicates the sequence in which the tag is applied.The unique ID of the tag.The component being tagged.The application position of the component when tagged.The tag status.The tag type.Notes essential to tag application.

Restoration Tab

You use the Restoration Tab of Clearances (Nuc) to view or edit tag restoration information for each tag on the clearance. This tab includes any relevant information on the tag such as:

Indicates the sequence in which the tag is restored.The unique ID of the tag.The component being tagged.The restoration position of the component after the tag is removed.Notes essential to tag restoration.

Sign On/Off Tab

You use the Sign On/Off tab of Clearances (Nuc) to view who is currently signed on to the clearance protection provided by the current clearance.

Log Tab

You use the Log tab of Clearances (Nuc) to view and create entries about the current record.

The Log tab has the following subtabs:

Clearances Log: to add clearance log entries for the current record, and to view clearance log entries for all originating and follow-up records for the current record.

Impact Plans (Nuc) Application

Operational Management (Nuc) Module 13

Communications Log: to view inbound and outbound communications for the current record; to view any attachments that are associated with a communication. The Communication Log is read-only..

Clearances (Nuc) Actions

Clearances (Nuc) has the following nuclear-specific actions:

Change Clearance Status > Cancel ClearanceChange Clearance Status > Make Clearance ReadyChange Clearance Status > Change Status to WSHAREChange Clearance Status > Close ClearanceTO Approvals > Application ApprovalTO Approvals > Revision ApprovalTO Approvals > Release ApprovalSRO Approvals > Application ApprovalSRO Approvals > Revision ApprovalSRO Approvals > Restoration ApprovalTag Data > Add/Modify Application DataTag Data > Add/Modify Application Verification DataTag Data > Add/Modify Restoration DataTag Data > Add/Modify Restoration Verification DataClearance Revisions > Revise ClearanceClearance Revisions > View/Modify Revision SequenceClearance Revisions > Issue Revised ClearanceShift Supervisor UndoTag Share > Share TagsTag Share > Un-Share TagsConflict CheckingCreate Working ClearanceGenerate RestorationBlock/Unblock Work OrdersWork Orders > AddWork Orders > Approve AdditionWork Orders > RemoveWork Orders > Approve RemovalWork Orders > Undo RemovalView Child Clearance Work OrdersView Tag Related InformationView History > View Clearance HistoryView History > View Clearance Revision HistoryModify/Delete Clearance LogsCreate CommunicationDuplicate Clearance

For information on these actions, see the Clearances (Nuc) help.

Impact Plans (Nuc) Application

Purpose Use the Impact Plans (Nuc) application to define the operational and maintenance impacts related to work activities at your facility. By addressing these areas, impact plans provide the information that ensures proper scheduling and execution in a complex work management environment.

Impact Plans (Nuc) Application

14 IBM Maximo for Nuclear Power: User’s Guide Addendum

Impact plans cannot be used with Is Task work orders, but those kinds of tasks are covered by the Unavailability subtab of the Operational Impacts tab.

An impact plan is related to both a work activity (a job plan) and a piece of equipment (a location or asset).

There are two types of impact plans:

A template impact plan is a plan that can be associated with a PM. It defines what the impacts will be, based on the work activity and component. When associated with a PM's job plan and a location or asset, the template is copied onto the PM work order as a working impact plan.A working impact plan is an impact plan that is associated to a work order. It can be created during PM work order generation if there is a template impact plan associated to the same job plan and location or asset as the PM. A working impact plan cannot exist separate from a work order. Although working impact plans can be viewed in the Impact Plans (Nuc) application, they must be edited in the Work Order Tracking (Nuc) application.

Within an impact plan, the impacts are grouped into operational impacts and maintenance impacts. These two groups of impacts can be modeled and managed independently.

Tabs

The Impact Plans (Nuc) application has the following tabs:

Operational ImpactsMaintenance ImpactsAssociationsLog

Operational Impacts Tab

Use the Operational impacts tab to define the effects of planned maintenance at the component, system, and plant levels. The impacts are grouped into three categories, each on a separate subtab:

Tech Specs and Retest: to enter any applicable technical specifications, to identify the need for retesting, and to specify any PM-based testing requirements to verify the ability of components to perform their function after maintenance.Unavailability: to specify whether any components or systems will not be able to perform their function during the planned maintenance. This information is independently related to each specific job plan and component set from the Associations tab.Plant Response: to define any other operational-related events that are needed to initiate or will result from the maintenance and to indicate the actions to be taken in each case.

For information about a field, place the cursor in the field and press Alt + F1.

Impact Plans (Nuc) Application

Operational Management (Nuc) Module 15

Maintenance Impacts Tab

Use the Maintenance Impacts tab to summarize required notifications and interdepartmental support and permits that are necessary to support maintenance-related activities.

For information about a field, place the cursor in the field and press Alt + F1.

Associations Tab

Use the Associations tab to associate, or link, the pre-identified impacts with a job plan / component pair.

For an impact plan to be invoked during work order generation from the Preventive Maintenance (Nuc) application, the association data must identify both a job plan number and either a location or an asset.

For information about a field, place the cursor in the field and press Alt + F1.

Log Tab

Use the Log tab to keep a record of information about the impact plan and to create communications. The Log tab has two subtabs:

Impact Plan Log: to keep a record of information about the template impact plan.Communication Log: to create a log of communications.

For information about a field, place the cursor in the field and press Alt + F1.

Impact Plans (Nuc) Actions

The actions you can select from the Select Action menu depend on the type of impact plan.

For working impact plans:

View Operations Status HistoryView Maintenance Status HistoryCreate Template from Current Impact Plan

For template impact plans:

Change Operations StatusChange Maintenance StatusView Operations Status HistoryView Maintenance Status HistoryCreate CommunicationDelete Impact PlanDuplicate Impact PlanModify/Delete Impact Plan Logs

For information on these actions, see the Impact Plans (Nuc) help.

Tech Specs (Nuc) Application

16 IBM Maximo for Nuclear Power: User’s Guide Addendum

Tech Specs (Nuc) Application

Purpose You use the Tech Specs (Nuc) application to to create and maintain tech specs and their associated data.

A tech spec can be used for multiple source specifications, such as a specification from a Technical Requirements Manual or the Offsite Dose Calculation Manual, as well as a technical specification from the national regulatory body.

Maintenance activities that are part of an impact plan might challenge a tech spec, and you can identify these tech specs in the Impact Plans (Nuc) application. You also associate the surveillance requirements with a tech spec. To be associated, he surveillance requirement must match the tech spec's site, unit, and type.

Due to the importance of tech specs in nuclear power operations, fields are provided to help in managing changes. The Changed Date field is updated whenever a tech spec is saved, which permits tracking of updates.

Usage of a tech spec is flagged by the Used on Work Order? and Used on Impact Plan? indicators to identify the associations that have been established.

Tabs

The Tech Specs (Nuc) application has the following tabs:

ListTech Specs

List Tab

Use the List tab to search the database for a tech spec using any combination of available fields.

Tech Specs Tab

Use the Tech Specs tab to create or edit details of a tech spec and to associate its surveillance requirements.

For information about fields, place the cursor in the field and press Alt + F1.

Tech Specs (Nuc) Actions

The Tech Specs (Nuc) application has the following actions:

DeleteDuplicate Tech Spec

For information about these actions, see the Tech Spec (Nuc) help.

Surveillance Requirements (Nuc) Application

Operational Management (Nuc) Module 17

Surveillance Requirements (Nuc) Application

Purpose You use the Surveillance Requirements (Nuc) application to identify actions that must take place. Typically, a surveillance requirement action is mandated by and associated to the tech spec for which it checks compliance.

The surveillance requirements include details of the actions that must take place and their frequency.

Multiple surveillance requirements can be associated with a technical specification or with a PM. The system ensures that every surveillance requirement is identified by type, site, and unit.

Due to the importance of surveillance requirements in nuclear power operations, fields are provided to help in managing changes. The Changed Date field is updated whenever a surveillance requirement is saved, which permits tracking of updates.

Usage of a surveillance requirement is flagged by the Used on TS? and Used on PM? indicators to identify the associations that have been established..

Tabs

The Surveillance Requirements (Nuc) application has no tabs.

Surveillance Requirements (Nuc) Actions

The Surveillance Requirements (Nuc) application has the following action:

Duplicate Surveillance Requirement

For information about this action, see the Surveillance Requirements (Nuc) help.

Events (Nuc) Application

Purpose You use the Events (Nuc) application to identify expected plant events and the appropriate responses to perform when the events occur. Examples of events are:

alarmstripsother special conditions.

You can associate multiple events with an impact plan. The system ensures that every event is identified by type, site, and unit.

Due to the importance of event information in nuclear power operations, fields are provided to help in managing changes. The Changed Date field is updated whenever an event is saved, which permits tracking of updates.

Usage of an event is flagged by the Used on Work Order? and Used on Impact Plans? indicators to identify the associations that have been established.

Events (Nuc) Application

18 IBM Maximo for Nuclear Power: User’s Guide Addendum

Tabs

The Events (Nuc) application has no tabs.

Events (Nuc) Actions

The Events (Nuc) application has the following action:

Duplicate Event

For information about this action, see the Events (Nuc) help.

© Copyright IBM Corp. 2007 19

Overview The Plans module has one application. This chapter describes the application. For more information on any application, refer to the application help. You also can refer to the IBM Maximo User’s Guide for more information about any standard Maximo application.

The Plans module contains the following Nuclear-specific application:

Asset List (Nuc) Application

Purpose You use the Asset List (Nuc) application to create lists of assets that can be applied to a commitment. You can apply the asset list to the commitment via the Select Asset List button on the Work Package tab of the Commitment Tracking (Nuc) application. You can query Maximo to search for assets by asset number or location.

An asset list is a list of related work assets. The asset list contains assets, locations, or a combination of both. The list of work assets can be related by location, such as all pumps and motors in a room, or by type of asset, such as all fire extinguishers located throughout the site. Asset lists simplify building hierarchies of work orders for inspections. You can use an asset list in the following ways:

Apply the asset list to a preventive maintenance record to generate inspection-type work orders for all work assets listed.

Apply the asset list to a work order and generate child work orders for each work asset listed.

The Asset List (Nuc) application lets you add multiple locations to an asset list via the Add Multiple Locations action and add multiple items to an asset list via the Add Multiple Assets action.

Tabs

The Plans (Nuc) application has the following tab:

Asset List

Plans Module 6Application Nuclear Function

Asset List (Nuc) To create asset lists which may then be used on a commitment and on Work Orders.

Asset List (Nuc) Application

20 IBM Maximo for Nuclear Power: User’s Guide Addendum

Asset List Tab

Use the Asset List tab in the Asset List (Nuc) application to create, modify, and delete asset list records. Asset lists are lists of related work assets. You can apply an asset list to a commitment to create child work orders for each location or asset identifier listed on the asset list. You can also associate an asset list with a PM record. When you generate a work order for the PM, you also generate child work orders for each location or asset listed on the asset list.

You can associate a job plan with each asset or location in the asset list. Maximo copies the job plan to the child work orders that Maximo has generated for each work asset. If a default safety plan is associated with the job plan when used on the selected work asset. Maximo also copies that information to the work order.

Asset List (Nuc) Actions

The Asset List (Nuc) application has the following Nuclear-specific actions:

Duplicate Asset ListDelete Asset List

© Copyright IBM Corp. 2007 21

Overview The Preventive Maintenance module has one cloned application and one other application. This chapter describes these applications. For more information on any application, refer to the application help. You also can refer to the IBM Maximo User’s Guide for more information about any standard Maximo application.

The Preventive Maintenance module contains the following Nuclear-specific applications:

Preventive Maintenance (Nuc) Application

Purpose You use the Preventive Maintenance (Nuc) application to create, modify, and view preventive maintenance plans for work assets and locations. PM records are templates for work orders.

On a PM record, you schedule job plans to be performed for preventive maintenance work. Maximo then generates work orders from the PM.

You can also group PMs into hierarchies that model your asset hierarchies and generate sequenced work order hierarchies.

About Clearances and PMs

Clearances created with the type set to TEMPLATE can be associated with PMs. These template clearances are related to job plans that make up a job plan sequence for a PM. You can assign the same clearance to multiple job plans on the same PM or assign it to multiple PMs. However, Clearances are not mandatory for every PM job plan.

You can enter a single template clearance number for each job plan on a PM.

When you generate work orders from PMs with associated clearances, the template clearances are used to create working clearances. This working clearance is associated with the PM work order. When multiple PMs, or multiple work orders generated from the same PM, are associated with the same Template Clearance and these PMs are invoked during the same Work Order generation

Preventive Maintenance Module 7

Application Nuclear Function

Preventive Maintenance (Nuc) To schedule Preventive Maintenance records (PMs) and to schedule surveillances according to a prescribed schedule.

Frequency (Nuc) To create, modify, and view schedule frequencies that can be used on multiple surveillances.

Preventive Maintenance (Nuc) Application

22 IBM Maximo for Nuclear Power: User’s Guide Addendum

process, then a single Working Clearance related to the group of PM Work Orders is generated.

The new working clearance has a status of DRAFT and a new clearance number. All tags associated with the clearance are used to create working tags.

About Impact Plans and PMs

PMs can make use of template impact plans during work order generation. If the location or asset and the job plan for the PM are the same as those of an association row for an impact plan, and if the impact plan has a status of APPR, then when the work order is generated, an impact plan is generated too.

The impact plan for the work order initially has a status of DRAFT and a new impact plan number.

Tabs

The Preventive Maintenance (Nuc) application has the following tabs:

PMFrequencySeasonal DatesJob Plan SequencePM HierarchySurveillanceReferences

PM Tab

On the PM tab, you can create and view PM records. PM records are templates for maintenance work that contain scheduling and job plan information for an asset. Information associated with a PM record becomes part of the work order records you generate from the PM. You can create parent-child relationships between similar PMs to build a PM hierarchy. This feature lets you generate hierarchies of related work orders. You can also schedule PM work for assets on a route.

You might work with records that are templates for other PMs. These templates are Master PMs. Master PMs maintain and update the scheduling information for their associated PMs.

This tab contains the following new fields:

Scheduling CommentsDetailsMilestone Code

For information about these fields, place the cursor in the field and press Alt + F1.

Frequency Tab

On the Frequency tab, you specify a frequency schedule for a PM (Preventive Maintenance) record. A PM's frequency schedule determines how often you generate work orders from the PM.

You can create a PM schedule to generate work orders based on elapsed time between work orders or meter units used, or both. Usually, a PM schedule for asset measures both elapsed time between work orders and changes to meter

Preventive Maintenance (Nuc) Application

Preventive Maintenance Module 23

readings. A typical PM schedule for a location measures only elapsed time between work orders.

You can also specify a PM's active months or seasons, and enter an extension date that can override a usual next due date without interrupting the PM's established frequency schedule.

For information about these fields, place the cursor in the field and press Alt + F1.

Seasonal Dates Tab

You use the Seasonal Dates tab to specify a PM's active days, months, or seasons.

You can have multiple active seasons for a single PM. You can also specify on which days of the week you want Maximo to generate work orders for a PM.

Job Plan Sequence Tab

You use the Job Plan Sequence tab to assign a sequential list of job plans to a PM (Preventive Maintenance) record. This allows you to schedule different levels of maintenance work at specified intervals.

By assigning a sequence number to each job plan, you specify which job plan Maximo selects each time a work order is generated from the PM record.

You can also optionally assign a template clearance to the job plan sequence.

PM Hierarchy Tab

You use the PM Hierarchy tab to build PM hierarchies. A PM hierarchy is a group of PM (Preventive Maintenance) records with "parent-child" relationships.

PM hierarchies generate an organized group of work orders for an asset or location hierarchy. Work is often organized this way for inspections and large projects.

Surveillance Tab

The Surveillance tab is used to:

Enter equipment reliability informationSelect a surveillance requirementCreate a PM sequence

You use this tab while creating a surveillance or a PM sequence.

References Tab

On the References tab, you can view references associated with a nuclear PM or add references to a nuclear PM. A reference is the source of the agreement. The agreement source can be a document. It also can refer to a telephonic or verbal agreement.

Frequency (Nuc) Application

24 IBM Maximo for Nuclear Power: User’s Guide Addendum

Preventive Maintenance (Nuc) Actions

The Preventive Maintenance (Nuc) application has the following Nuclear-specific actions:

Add/Modify Tech SpecsView/Modify PM Sequence Dates

For information about these actions, refer to Preventive Maintenance (Nuc) help.

Frequency (Nuc) Application

Purpose Use this application to create standardized frequencies for the performance or recurring maintenance work in the Preventative Maintenance (Nuc) application.

These frequencies, such as those found in Technical Specifications—Surveillance Requirements, aid in defining the 'regulatory frequency' as compared to a convenient scheduling based time interval. You can apply a given frequency to multiple PM instances.

Tabs

The Frequency (Nuc) application has the following tabs:

FrequencySeasonal Dates

Frequency Tab

On the Frequency tab, you specify a frequency schedule for a surveillance.

Seasonal Dates Tab

You use the Seasonal Dates tab to specify a PM's active days, months, or seasons.

You can have multiple active seasons for a single PM. You can also specify on which days of the week you want Maximo to generate work orders for a PM.

© Copyright IBM Corp. 2007 25

Overview The Purchasing module has five cloned applications. This chapter provides an overview of these applications. For more information about any application, refer to the application help. You also can refer to the IBM Maximo User’s Guide for more information on any standard Maximo application.

The Purchasing module contains the following Nuclear-specific applications:

Purchase Requisitions (Nuc) Application

Purpose You use the Purchase Requisitions (Nuc) application to create purchase requisitions for items, supplies, and services. A purchase requisition (PR) is a written request issued internally to a purchasing department to order items or services.

Maximo allows you to create two types of PRs:

Internal PRs: requesting the transfer of materials from another company storeroom.External PRs: requesting the purchase of the necessary materials from an outside vendor. You can specify the vendor, if known.

Tabs

The Purchase Requisitions (Nuc) application has the following enhanced tabs:

Purchasing Module 8Application Nuclear Function

Purchase Requisitions (Nuc) To create purchase requisitions for items, supplies, and services.

Purchase Orders (Nuc) To create purchase orders.

Request for Quotation (Nuc) To create requests for quotations and store the quotations so you can assess which vendor best meets your needs.

Terms and Conditions (Nuc) To enter and maintain a library of terms and conditions that can be added to a purchasing document or contract, and that are required to be associated with either companies or items.

Companies (Nuc) To maintain detailed information about vendors, manufacturers, and other companies.

Purchase Requisitions (Nuc) Application

26 IBM Maximo for Nuclear Power: User’s Guide Addendum

PR Lines Terms and Conditions

PR Lines Tab

You use the PR Lines tab to enter items, services, or supplies for a purchase requisition. The Total Cost field reflects the total cost of all the items listed in the table window. If you are entering a series of items, you may want to fill in some of the Default Table Data fields for fields with consistent entries to speed up data entry.

The Technical Terms and Conditions table window lists any technical terms associated with the currently selected item, if there are any, and is read-only.

The PR Lines Tab has the following new fields:

Vendor?SequenceTermDescriptionRevision #

For information about fields, place the cursor in the field and press Alt + F1.

Terms and Conditions Tab

You use the Terms and Conditions tab to view existing Commercial terms and Quality terms associated with a purchase requisition. The Quality terms come from the vendor listed on the purchase requisition.

You can enter new (Commercial) Terms and Conditions on this tab, or you can choose from a library of existing terms from the Terms and Conditions (Nuc) application. The list of Quality Terms and Conditions is read only.

The Terms and Conditions tab has the following new fields:

SequenceTermDescriptionRevision #

For information about fields, place the cursor in the field and press Alt + F1.

Purchase Requisition (Nuc) Actions

The Purchase Requisitions (Nuc) application has the following Nuclear-specific action:

Add/Delete Technical Terms

For information about this action, refer to the Purchase Requisition (Nuc) help.

Purchase Orders (Nuc) Application

Purchasing Module 27

Purchase Orders (Nuc) Application

Purpose You use the Purchase Orders (Nuc) application to create purchase orders. A purchase order (PO) is an authorized order from a purchasing agent or department to an internal supplier or external vendor.

You can create POs in three ways:

Directly from the Purchase Orders applicationFrom purchase requisitions (PRs)From requests for quotations (RFQs)

You also use this application to create change orders.

Tabs

The Purchase Orders (Nuc) application has the following enhanced tabs:

PO LinesTerms and Conditions

PO Lines Tab

You use the PO Lines tab to enter line items on a purchase order. You can enter line items manually, copy them from a PR, or create them from an RFQ.

You can also view summary information from the Receiving application.

The Technical Terms and Conditions table window lists any technical terms associated with the currently selected item if there are any, and is read-only.

The PO Lines tab has the following new fields:

Vendor?SequenceTermDescriptionRevision #

For information about fields, place the cursor in the field and press Alt + F1.

Terms and Conditions Tab

You use the Terms and Conditions tab to view existing Commercial terms and Quality terms associated with a purchase requisition. The Quality terms come from the vendor listed on the purchase requisition.

You can enter new (Commercial) Terms and Conditions on this tab, or you can choose from a library of existing terms from the Terms and Conditions (Nuc) application. The list of Quality Terms and Conditions is read only.

The Terms and Conditions tab has the following new fields:

SequenceTerm

Request for Quotation (Nuc) Application

28 IBM Maximo for Nuclear Power: User’s Guide Addendum

DescriptionRevision #

For information about fields, place the cursor in the field and press Alt + F1.

Purchase Orders (Nuc) Actions

The Purchase Orders (Nuc) application has the following Nuclear-specific action:

Add/Delete Technical Terms

For information about this action, refer to the Purchase Orders (Nuc) help.

Request for Quotation (Nuc) Application

Purpose You use the Request for Quotations (Nuc) application to create requests for quotations and store the quotations so you can assess which vendor best meets your needs.

A request for quotation (RFQ) is a request that you send out to one or more potential suppliers. To list a vendor on the RFQ, the vendor must have a record in the Companies application. In the RFQ application, you can specify line items, required delivery dates, and other conditions you want the vendor to meet for the delivery of an item or service.

You can create an RFQ for any of the following circumstances:

The stock count of a stocked item drops below a certain level and you must place another bulk order.

A requisition is received for an item or service that requires a quotation each time due to item price or other requirements.

Someone at your site requests a quote for an item or service. It can be for a normally stocked item or for an item not normally ordered, such as a special order or non-stocked item.

You need to do commodity bulk buying for a certain period of time. This is typically for many items with common commodity codes. The quotation might not be copied to a PO immediately, but the pricing is set.

When you receive the quotations from the vendors, you enter them into the Request for Quotations (Nuc) application one at a time. At the end of the process, you review the quotations and award one quotation for each RFQ line. The quotations are then converted to one or more purchase orders or contracts, depending on the procurement flow within your organization.

Tabs

The Request for Quotations (Nuc) application has the following enhanced tabs:

RFQ LinesVendors

Request for Quotation (Nuc) Application

Purchasing Module 29

RFQ Lines Tab

You use the RFQ Lines tab to enter the line items or services that require quotations from one or more vendors. You can enter the information manually, or you can copy PR lines and convert them to RFQ lines. When you copy PR lines, copied information includes the item identifiers, quantities desired, and other item-specific information.

The Technical Terms and Conditions table window lists any technical terms associated with the currently selected item if there are any, and is read-only.

You should provide as much detail as possible for RFQ lines, so that vendors can provide accurate quotes based on your specified information.

The RFQ Lines tab has the following new fields:

SequenceTermDescriptionRevision #

For information about fields, place the cursor in the field and press Alt + F1.

Vendors Tab

You use the Vendors tab of Request for Quotations (Nuc) to enter the vendors to whom the request for quotation is to be sent, as well as terms and conditions received from each vendor. You can copy the vendor information over from the Companies application, or fill it in manually. You should provide such data as the vendor name, contact, phone number, and other vendor-specific information.

The quality terms and conditions for the currently selected vendor, if any, are displayed in the lower table window. These fields are read-only.

Rows on the Vendors tab can also be filled in by copying PR lines to the RFQ. If there is a vendor associated with the copied PR line, that vendor is added to the RFQ Vendors list. Thus a different vendor could possibly be added to the RFQ Vendors list for each new PR line added. If a specific vendor appears in more than one PR line, the vendor appears only once on the RFQ Vendors tab.

The Vendors tab has the following new fields:

SequenceTermDescriptionRevision #

For information about fields, place the cursor in the field and press Alt + F1.

Request for Quotation (Nuc) Actions

The Request for Quotation (Nuc) application has the following Nuclear-specific action:

Add/Delete Technical Terms

Terms and Conditions (Nuc) Application

30 IBM Maximo for Nuclear Power: User’s Guide Addendum

For information about this action, refer to the Purchase Orders (Nuc) help.

Terms and Conditions (Nuc) Application

Purpose You use the Terms and Conditions (Nuc) application to enter and maintain a library of terms and conditions. These terms can contain information such as liability concerns, shipping and handling details, or delivery time expectations.

There are three types of terms used:

Commercial terms that can be added to a purchasing document or a contractQuality terms that can be associated with a companyTechnical terms that can be associated with an item

The Commercial terms entered in the Terms and Conditions (Nuc) application are available from the Terms and Conditions tabs in purchasing, contract, companies and item master applications. From those tabs, you can select a term from the library to associate with a purchasing or contract record. Quality terms are used for companies and Technical terms are used for items.

Terms are now statusable. Only approved Quality terms can be applied to companies. Only approved Technical terms can be applied to items.

The Terms and Conditions (Nuc) application has the following new fields:

Vendor Qual TypeRevision #StatusStatus Date

For information about fields, place the cursor in the field and press Alt + F1.

Terms and Conditions (Nuc) Actions

Terms and Conditions (Nuc) has no Nuclear-specific actions.

Companies (Nuc) Application

Purpose The Companies (Nuc) application maintains detailed information about vendors, manufacturers, and other companies.

Vendors can have parent companies or multiple vendor locations for a single company. Using reports, you can determine total year-to-date expenditures with a single organization, regardless of its location.

Company information must be entered in the Companies application before other modules, such as Inventory and Purchasing, can access it.

Companies (Nuc) Application

Purchasing Module 31

Tabs

The Companies (Nuc) application has the following new tabs:

QualificationsItems

Qualifications Tab

The Qualifications tab is used to associate Quality terms to a company and to record Scope of Approval data. On this tab you can enter scheduled dates for company audits, add Quality Terms and Conditions, and enter Scope of Approval Data.

The Qualifications tab has the following new fields:

Quality StatusLast Audit DateNext Audit DateAudit ResultTermDescriptionRevision #Last History Evaluation DateNext History Evaluation DateLegacy CodeNUPIC Vendor CodeApproval ScopeDetails

Items Tab

Use the Items tab of Companies (Nuc) to associate items with a company. These items will generally be the items that the company normally supplies to the nuclear provider. The list of items for a company is referenced when purchasing items from that company. When ordering items, if an item is not listed for that company, the user is warned of this fact but allowed to continue if required.

The Items tab has the following new fields:

ItemDescription

Companies (Nuc) Actions

The Companies (Nuc) application has the following Nuclear-specific actions:

Add/modify Company Audit DataChange Quality Status

For information about these actions, refer to the Companies (Nuc) help.

Companies (Nuc) Application

32 IBM Maximo for Nuclear Power: User’s Guide Addendum

© Copyright IBM Corp. 2007 33

Overview The Work Orders module has one new application in this release (Sign On/Off) and three other cloned applications. For more information on any application, refer to the application help. You also can refer to the IBM Maximo User’s Guide for more information about any standard Maximo application.

The Work Orders module contains the following Nuclear-specific applications:

Quick Reporting (Nuc) Application

Purpose You use the Quick Reporting (Nuc) application to create or report on open work orders or small jobs. You can enter actual labor and material usage information, or report events such as asset failures or downtime that do not involve maintenance department work.

This application contains a subset of fields available in Work Order Tracking, and has probably been configured to meet the needs of your site.

Quick Reporting (Nuc) supports Commitment Tracking, Surveillances, and Asset Reliability.

Tabs

The Quick Reporting (Nuc) application has the following enhanced tab:

Quick Reporting

Quick Reporting Tab

You use the Quick Reporting tab to duplicate work orders, or to report on any open work order. Insert and modify information about asset, tasks, labor and material usage, tool information, and Failure reporting.

Work Orders Module 9Application Nuclear Function

Quick Reporting (Nuc) To create or report on open work orders or small jobs.

Commitment Tracking (Nuc) To effectively manage critical processes.

Work Order Tracking (Nuc) To plan, review, and approve work orders for asset and locations.

Sign On/Off (Nuc) To rapidly and securely sign on and off of clearance protection

Commitment Tracking (Nuc) Application

34 IBM Maximo for Nuclear Power: User’s Guide Addendum

When reporting on an open work order, you can copy information from an existing work plan to enter actual labor and material usage. Planners may want to use the Work Order Tracking application to plan and schedule recurring or complex work, but maintenance and shop floor personnel may find the Quick Reporting application more convenient to use.

This application contains a subset of fields available in Work Order Tracking, and has probably been configured to meet the needs of your site.

The Quick Reporting tab has the following enhanced sub-tab:

Materials

The materials sub-tab has been enhanced to include Procurement Class.

Quick Reporting (Nuc) Actions

Quick Reporting (Nuc) has no industry-specific actions.

Commitment Tracking (Nuc) Application

Purpose Commitments are agreements made between two organizations. One of the organizations performs the work, and reports the status of the work performed to an external organization ( for example, the Nuclear Regulatory Commission).

You use this application to maintain work records and report the status of work performed to accomplish tasks identified as a commitment to various external agencies, for example, NRC, OSHA, EPA. The following is a representative list of nuclear industry work you can track:

CommitmentsNRC BulletinsNRC Generic Letters (GL)Institute of Nuclear Power Operations INPOLicensee Event Reports (LER)Responses of NRC Notices of Violations (NOV)Federal Regulatory Guides (RG)Industry Codes and StandardsChanges in the utility's Practices and/or procedures

Maximo lets you perform the following tasks via the Commitment Tracking (Nuc) application:

Identify assets affected by the commitment.Determine the work that needs to be accomplished to meet the commitment.Track the work required to meet the commitment.

Commitment Tracking (Nuc) Application

Work Orders Module 35

Tabs

The Commitment Tracking (Nuc) application has the following new or enhanced tabs:

ReviewWork Package

Review Tab

You use the Review tab to add departments, groups, and people who are required to be part of the review process for a commitment. This enables the Commitment Tracking administrator to track who is part of the review process and when their review is due for completion along with other data.

This tab contains the following new fields:

Responsible DeptDept NameResponsible PersonNameReview Due DateExt Review DateReview ReceivedNotesSummaryEmail

For information about a field, place the cursor in the field and press Alt + F1.

Work Package Tab

You use the Work Package tab to perform the following tasks:

Display one or more assets attached to the commitment.Select one or more asset lists to attach to the commitment via Select Asset List. Generate work orders or PMs for the identified assets via Generate Work. Display all work orders associated with the commitment via Display Work Order Hierarchy.View a Status Summary of the work orders attached to this Commitment.

This tab contains the following new fields:

Work Order StatusNumber of Work OrdersPercentage of Total

For information about a field, place the cursor in the field and press Alt + F1.

Work Order Tracking (Nuc) Application

36 IBM Maximo for Nuclear Power: User’s Guide Addendum

Work Order Tracking (Nuc) Application

Purpose You use the Work Order Tracking (Nuc) application to plan, review, and approve work orders for assets and locations, and to identify what parts of a WO require a clearance.

When you create a work order, you initiate the maintenance process and create a historical record of work being performed. You can create work orders in several applications.

Tabs

The Work Order Tracking (Nuc) application has the following tabs:

Work OrderPlansClearanceRelated RecordsActualsSafety PlansImpact PlansLogFailure ReportingSNPM Data

Work Order Tab

You use the Work Order tab of Work Order Tracking (Nuc) to create, plan, review, and approve work orders. On this tab, you process work orders created with the Work Order Tracking (Nuc) application as well as those created or generated by other applications.

You can view and modify work order details such as the work assets, work type and priority, safety plan, job plan, GL account, problem code, scheduling information, ownership, and follow-up work on this tab.

You also indicate the need for a clearance on this tab. After the work order is associated to a clearance, the clearance number and revision number are displayed. The clearance number and revision number reflect the clearance that the work order is currently associated with.

For information about fields, place the cursor in the field and press Alt + F1.

Plans Tab

You use the Plans tab of Work Order Tracking (Nuc) to view, enter, and modify several types of work plan data on a work order. A work plan describes the tasks, labor, materials, services, and tools needed to complete the work.

An easy way to add a work plan to a work order is to associate a job plan with the work order. When you insert an identifier in the Job Plan field or, from another application, generate a work order that already has a job plan. The job plan gets copied as a work plan to the work order. Safety plans will also be copied to the work order, if the job plan and its assets or locations have a safety plan. Changes

Work Order Tracking (Nuc) Application

Work Orders Module 37

you make to the work plan or work order's safety plan do not affect the original job plan or safety plan.

On the Plans tab, you also can add child work orders and create tasks for the work order. You enter information about estimated labor, materials, services, and tools needed to carry out a work plan on the Plan's Labor, Material, Services, and Tools subtabs.

Clearance Tab

The Clearance tab of Work Order Tracking (Nuc) is used to display the tags added to the work order through the craft approval process. In addition, maintenance personnel can sign on or off of the work order clearance protection.

Craft Approval is done after the tags have been hung and verified. The craft approver must concur that work can safely be performed under the current clearance protection that has been related to the work order.

Depending on how your application is configured, the tags may:

All be brought over form the clearance at once.Be selected by the craft approver and brought over individually.

Related Records Tab

You use the Related Records tab of Work Order Tracking (Nuc) to link the selected work order to other work orders and tickets, and to view work orders and tickets already related to the selected work order. You also can delete the relationship between a work order and a related record if the relationship type is Related.

When you manually relate a work order or ticket to the current work order on the Related Records tab, the relationship type between the two records is Related.

When you create a work order or ticket using the Select Action menu from within a work order or ticket, the relationship type for the newly created record is Follow Up. The current record's relationship to the new record is Originator.

Actuals Tab

You use the Actuals tab of Work Order Tracking (Nuc) to enter, view and modify the actual job tasks, labor, materials, and tools used on the work order. If there is a work plan, Maximo copies data from the Tasks table window of the Plans tab to the Tasks table window of the Actuals tab. The work order must be approved before you can report actuals.

To report actual labor, material, and tool use, click on the appropriate subtab. You can then use dialog boxes available from the subtabs to copy plan data, or insert different or additional information on use. When you report actuals, you can modify fields until you save the record. Only approved labor is used in calculating actuals for labor hours and costs. On this tab, you can also view services that were recorded against the work order. The Services subtab is read-only.

Work Order Tracking (Nuc) Application

38 IBM Maximo for Nuclear Power: User’s Guide Addendum

Safety Plan Tab

You use the Safety Plan tab of Work Order Tracking (Nuc) to add, view or modify safety information on a work order. Changes you make here do not affect the safety information maintained in the safety plans applications. Use the Safety Plan field on the Work Order tab to insert a new safety plan from the Safety Plans application. A work order only can have one safety plan associated with it.

Impact Plans

You use the Impact Plans tab of Work Order Tracking (Nuc) to access the two main parts of an impact plan: Operational Impacts and Maintenance Impacts.

The Operational Impacts sub-tab lists the effects of maintenance work at the component, system, and plant levels. You use this sub-tab to:

Associate tech specs to a work order.Associate retest PMs as necessary.List unavailable components, and identify the work order tasks when they become available.Indicate the anticipated plant response to maintenance activities.

The Maintenance Impacts sub-tab lists the required notifications, interdepartmental support, and permits that are necessary to support the maintenance related activities. You use the Maintenance Impacts tab of Work Order Tracking (Nuc) to:

Enter notification and support comments.List the persons or groups that with whom you will coordinate on this work order.List any permits required for the work order.Enter any comments for planned permits.

Log Tab

You use the Log tab of Work Order Tracking (Nuc) to view and create entries about the current record.

Failure Reporting Tab

You use the Failure Reporting tab of Work Order Tracking (Nuc) to record and view asset and location problems, causes, and remedies. This data enables you to identify trends and isolate probable causes of breakdowns.

SNPM Data Tab

The SNPM (Standard Nuclear Performance Model) Data tab of Work Order Tracking (Nuc) is used to view nuclear program data for the location or asset on the work order. This includes equipment reliability, procurement engineering, and materials and services information.

Work Order Tracking (Nuc) Actions

The Work Order Tracking (Nuc) application has the following Nuclear-specific actions:

Sign On/Off (Nuc) Application

Work Orders Module 39

Craft ApprovalSupervisor Override > Add/Modify Sign On/OffSupervisor Override > Release Work Order from ClearanceSupervisor Override > Undo Work Order Release from ClearanceView/Accept Clearance RevisionImpact Plan Status > Change Operational StatusImpact Plan Status > Change Maintenance StatusImpact Plan Status > View Operational HistoryImpact Plan Status > View Maintenance HistoryImpact Plan Content > Add/Select Impact PlanImpact Plan Content > Add/Select Operational ImpactsImpact Plan Content > Add/Select Maintenance ImpactsImpact Plan Content > Remove Operational ImpactsImpact Plan Content > Remove Maintenance ImpactsDelete Impact PlanCreate Template from Current Impact Plan

Sign On/Off (Nuc) Application

Purpose You use the Sign On/Off (Nuc) application to rapidly and securely sign on and off of clearance protection.

After tags are brought over from the clearance to the work order as part of Craft Approval of the clearance, individual maintenance resources can sign on to the clearance and begin work under clearance protection. After maintenance resources sign on to the clearance, control of Clearance and Tag status is maintained as appropriate.

Resources sign off the clearance when they have finished work for their shift or other period as determined by plant practice, then may sign on again when they are ready to resume work. When signed off, the condition is that although a resource has begun work on a task protected by the clearance, the resource is temporarily not relying on clearance protection. The condition of signed off is recorded and supports potential decisions based on this state, such as whether it is safe for Operations to modify the clearance boundary.

While a maintenance resource can sign onto a single work order clearance protection in the Work Order Tracking (Nuc) application, the Sign On/Off (Nuc) application allows a maintenance resource to sign on/off multiple work orders in the same screen. The sign on/off functionality in the Work Order Tracking (Nuc) application is work order based while the Sign On/Off application is user based.

Work orders may be temporarily placed into a Blocked condition by Operations, where new sign-ons are not permitted.

Tabs

The Sign On/Off (Nuc) application has no tabs.

Sign On/Off (Nuc) Actions

The Sign On/Off (Nuc) application has no actions.

Sign On/Off (Nuc) Application

40 IBM Maximo for Nuclear Power: User’s Guide Addendum

© Copyright IBM Corp. 2007 41

Overview The Assets module has two cloned applications. This chapter provides an overview of the applications. For more information about any application, refer to the application’s help. You also can refer to the IBM Maximo User’s Guide for more information about any standard Maximo application.

The Assets module contains the following Nuclear-specific applications:

Assets (Nuc) Application

Purpose You use the Assets (Nuc) application to create and store asset numbers and corresponding information, such as parent, location, vendor, up/down status, and maintenance costs for each asset.

Tabs in the Assets (Nuc) application let you build the asset hierarchy: an arrangement of buildings, departments, assets, and subassemblies. The asset hierarchy provides a convenient way to roll up maintenance costs so that you can check accumulated costs at any level, at any time. It also makes it easy to find a particular asset number.

Tabs

The Assets (Nuc) application has the following nuclear-specific tabs:

SNPM DataPositions

SNPM Data Tab

The SNPM (Standard Nuclear Performance Model) Data tab is used to view, modify, add, or delete SNPM asset related data.

These best practices, benchmarks, and KPIs are established by the Nuclear Energy Institute (NEI) in conjunctions with the Institute of Nuclear Power Operations (INPO).

In order to support this, Maximo focuses on three areas of critical importance.

Assets Module 10Application Nuclear Function

Assets (Nuc) Used to add and store nuclear specific data.

Locations (Nuc) Used to add and store nuclear specific data.

Locations (Nuc) Application

42 IBM Maximo for Nuclear Power: User’s Guide Addendum

equipment reliabilitymaterials and servicesprocurement engineering.

Positions Tab

You use the Positions tab of Assets (Nuc) to enter information on the allowable positions for an asset.

You also indicate whether or not each position requires application or restoration independent verification. When you mark an asset as requiring application or restoration independent verification, then it must be independently verified by a user other than the user that applied or restored the tag in the Clearances (Nuc) application.

Locations (Nuc) Application

Purpose The Locations (Nuc) application lets you enter and track locations for assets and organize these locations into logical hierarchical systems or network systems. Using hierarchies or systems of locations and specifying the location for assets on the asset record provides the groundwork for gathering and tracking valuable information on the history of an asset, including its performance at specific sites, as it is moved from location to location. With locations organized into systems, you can quickly find a location on the Drilldown page, and identify the asset at that location.

Tabs

The Locations (Nuc) application has the following nuclear-specific tabs:

SNPM DataPositions

For information about fields, place the cursor in the field and press Alt + F1.

SNPM Data Tab

The SNPM (Standard Nuclear Performance Model) Data tab is used to store SNPM related data.

The SNPM (Standard Nuclear Performance Model) is used to identify the set of best practices, benchmarks, and Key Performance Indicators (KPIs) applicable to the task. The SNPM is used to measure your performance and compare it against other facilities.

These best practices, benchmarks, and KPIs are established by the Nuclear Energy Institute (NEI) in conjunctions with the Institute of Nuclear Power Operations (INPO).

In order to support this, Maximo focuses on three areas of critical importance:

equipment reliabilitymaterials and servicesprocurement engineering

Locations (Nuc) Application

Assets Module 43

Positions Tab

You use the Positions tab of Locations (Nuc) to enter information on the allowable positions for a location.

You also indicate whether or not each position requires application or restoration independent verification. When you mark a location as requiring independent verification, application or restoration, then it must be independently verified by a user other than the user that applied or restored the tag in the Clearances (Nuc) application.

Locations (Nuc) Application

44 IBM Maximo for Nuclear Power: User’s Guide Addendum

© Copyright IBM Corp. 2007 45

This chapter lists all the Nuclear-specific database tables and their columns. It also lists Nuclear-specific columns in Maximo database tables.

Nuclear-Specific Tables

PLUSASSETPOS Table

PLUSASSETRC Table

PLUSCLEARANCE Table

Nuclear Database Tables and Columns 11

COLUMN NULLS DATA TYPE LENGTH

APPIVREQ N YORN 1

ASSET Same as ASSETS.ASSETNUM

MEMO Y ALN 50

POSITION N UPPER 12

RESIVREQ N YORN 1

RESTCOND Y UPPER 12

COLUMN NULLS DATA TYPE LENGTH

ASSET Same as ASSETS.ASSETNUM

MEMO Y ALN 50

POSITION Same as PLUSASSETPOS.POSITION

RESTCOND N UPER 12

COLUMN NULLS DATA TYPE LENGTH

ACTAPPFIN Y DATETIME N/A

ACTAPPSTART Y DATETIME N/A

ACTIVE N YORN N/A

ACTRESTFIN Y DATETIME N/A

Nuclear-Specific Tables

46 IBM Maximo for Nuclear Power: User’s Guide Addendum

ACTRESTSTART Y DATETIME N/A

APPDURATION Y INTEGER 4

ASSETNUM Same as ASSET.ASSETNUM

CHANGEBY Same as PERSON.PERSONID

CHANGEDATE Y DATETIME N/A

CLEARNUM N UPPER 12

CLEARTEMPLATE Same as PLUSCLEARANCE.CLEARNUM

CREATEBY Same as PERSON.PERSONID

CREATEDATE Y DATETIME N/A

DESCRIPTION Y ALN 100

HISTORY N YORN 1

ISSUECOMMENTS Y ALN 100

ISSUEDATE Y DATETIME N/A

ISSUEDBY Same as PERSON.PERSONID

LOCATION Same as LOCATIONS.LOCATION

PLANTSYSTEM Y UPPER 12

RESDURATION Y INTEGER 4

RESTCOND N UPPER 12

REVBY Same as PERSON.PERSONID

REVCOMMENTS Y ALN 100

REVDATE Y DATETIME N/A

REVISIONNUM N INTEGER N/A

SCHAPPFIN Y DATETIME N/A

SCHAPPSTART Y DATETIME N/A

SCHEDULECODE Y UPPER 12

SCHRESTFIN Y DATETIME N/A

SCHRESTSTART Y DATETIME N/A

STATUS N UPPER 16

STATUSDATE N DATETIME N/A

TAGSHAREDATE Y DATETIME N/A

TAGSHARERUN N YORN 1

TYPE N UPPER 12

COLUMN NULLS DATA TYPE LENGTH

Nuclear-Specific Tables

Nuclear Database Tables and Columns 47

PLUSCLHIER Table

PLUSCLLOG Table

PLUSCLSTATUS Table

PLUSCLTAGLINK Table

COLUMN NULLS DATA TYPE LENGTH

CLEARNUM Same as PLUSCLEARANCE.CLEARNUM

PARENT Same as PLUSCLEARANCE.CLEARNUM

PARENTREVNUM Same as PLUSCLEARANCE.REVISIONNUM

REVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

COLUMN NULLS DATA TYPE LENGTH

CLEARNUM Same as PLUSCLEARANCE.CLEARNUM

CREATEBY Same as PERSON.PERSONID

CREATEDATE Y DATETIME N/A

DESCRIPTION Y ALN 100

LOGID N INTEGER 12

LOGTYPE N UPPER 12

MODIFYBY Same as PERSON.PERSONID

MODIFYDATE Y DATETIME N/A

REVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

COLUMN NULLS DATA TYPE LENGTH

CHANGEBY Same as PERSON.PERSONID

CHANGEDATE Y DATETIME N/A

CLEARNUM Same as PLUSCLEARANCE.CLEARNUM

MEMO Y ALN 50

REVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

STATUS Same as PLUSCLEARANCE.STATUS

COLUMN NULLS DATA TYPE LENGTH

APPSEQNUM Y INTEGER 12

CLEARNUM Same as PLUSCLEARANCE.CLEARNUM

Nuclear-Specific Tables

48 IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSCOMPAUDIT Table

PLUSCOMPITEM Table

PLUSCOMPSTATUS Table

RELEASED N YORN 1

RESSEQNUM N INTEGER 12

REVAPPSEQ Y INTEGER 12

REVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

REVRESSEQ Y INTEGER 12

SUPERSEDED Same as PLUSTAG.TAGNUM

TAGNUM Same as PLUSTAG.TAGNUM

COLUMN NULLS DATA TYPE LENGTH

COLUMN NULLS DATA TYPE LENGTH

AUDITORG N ALN 25

AUDITRESULT N UPPER 12

COMMENTS Y ALN 50

COMPANY N UPPER 12

COMPAUDITID N INTEGER 12

LASTAUDITDATE N DATE N/A

NEXTAUDITDATE N DATE N/A

COLUMN NULLS DATA TYPE LENGTH

COMPANY N UPPER 12

ITEMNUM N UPPER 30

COLUMN NULLS DATA TYPE LENGTH

CHANGEBY N UPPER 30

CHANGEDATE N DATE/TIME N/A

COMPANY N UPPER 12

FINCNTRLID Y UPPER N/A

GLACCOUNT Y GL 23

MEMO Y ALN 50

STATUS N UPPER 16

Nuclear-Specific Tables

Nuclear Database Tables and Columns 49

PLUSCOMPTERM Table

PLUSCRAFTAPPR Table

PLUSCTREVIEW Table

PLUSDRILLDOWN Table

COLUMN NULLS DATA TYPE LENGTH

COMPANY N UPPER 12

TERMID N UPPER 25

COLUMN NULLS DATA TYPE LENGTH

APPRDATE Y DATETIME N/A

APPRUSER Same as PERSON.PERSONID

CLEARNUM Same as PLUSCLEARANCE.CLEARNUM

COMMENTS Y ALN 50

REVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

WONUM Same as WORKORDER.WONUM

COLUMN NULLS DATA TYPE LENGTH

COMMITID N UPPER N/A

EXTRAVDATE Y DATE N/A

NOTES Y ALN N/A

RESPDEPT N INTEGER 12

RESPPERSON Y UPPER 30

REVDUEDATE Y DATE N/A

REVREC Y DATE N/A

COLUMN NULLS DATA TYPE LENGTH

INHIERARCHY N YORN 1

INITVALUE N UPPER 14

ISQBE N YORN 1

RTRATRIBUTE N UPPER 18

TBNAME N UPPER 18

Nuclear-Specific Tables

50 IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSEVENT Table

PLUSIMPACT Table

PLUSIPASSOC Table

COLUMN NULLS DATA TYPE LENGTH

CHANGEDATE N DATETIME N/A

DESCRIPTION Y ALN 100

EVENTNUM N UPPER 12

EVENTNOTE Y ALN 256

RESPONSE Y ALN 256

TYPE N UPPER 12

UNIT Same as LOCATIONS.PLUSUNIT

COLUMN NULLS DATA TYPE LENGTH

ACTIONS Y ALN 256

DESCRIPTION Y ALN 100

IMPACTNUM N UPPER 12

MODES Same as PM.PLUSPMOD

PARALLEL Y ALN 256

PRECAUTIONS Y ALN 256

RETEST N YORN 1

RETESTCOMMENT Y ALN 256

SCHCODE Y ALN 12

STATUS N UPPER 16

STATUSDATE Y DATETIME N/A

TECHSPEC N YORN 1

TSCOMMENT Y ALN 256

TYPE N UPPER 12

UNIT Same as LOCATIONS.PLUSUNIT

COLUMN NULLS DATA TYPE LENGTH

ASSETNUM Same as ASSET.ASSETNUM

ASSOCID N INTEGER 12

Nuclear-Specific Tables

51 IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSIPCOORDINATE Table

PLUSIPEVENT Table

PLUSIPLOG Table

IMPACTNUM Same as PLUSIMPACT.IMPACTNUM

JPNUM Same as JOBPLAN.JPNUM

LOCATION Same as LOCATIONS.LOCATION

NOTE Y ALN 50

WONUM Same as WORKORDER.WONUM

COLUMN NULLS DATA TYPE LENGTH

COLUMN NULLS DATA TYPE LENGTH

COORDGROUP Same as PERSONGROUP.PERSONGROUP

DESCRIPTION Y ALN 100

IMPACTNUM Same as PLUSIMPACT.IMPACTNUM

NOTE Y ALN 100

NOTIFICATION N YORN 1

PERSON Same as PERSON.PERSONID

SUPPORT N YORN 1

COLUMN NULLS DATA TYPE LENGTH

EVENTNUM Same as PLUSEVENT.EVENTNUM

IMPACTNUM Same as PLUSEVENT.IMPACTNUM

TYPE Same as PLUSEVENT.TYPE

COLUMN NULLS DATA TYPE LENGTH

CREATEBY Same as PERSON.PERSONID

CREATEDATE N DATETIME N/A

DESCRIPTION N ALN 100

IMPACTNUM Same as PLUSIMPACT.IMPACTNUM

LOGTYPE N UPPER 12

MODIFYBY Same as PERSON.PERSONID

MODIFYDATE N DATETIME N/A

Nuclear-Specific Tables

52 IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSIPMTSTATUS Table

PLUSIPOPSTATUS Table

PLUSIPPERMIT Table

PLUSIPRETEST Table

COLUMN NULLS DATA TYPE LENGTH

CHANGEBY Same as PERSON.PERSONID

CHANGEDATE Y DATETIME N/A

IMPACTNUM Same as PLUSIMPACT.IMPACTNUM

MEMO Y ALN 100

STATUS Same as PLUSIMPACT.STATUS

COLUMN NULLS DATA TYPE LENGTH

CHANGEBY Same as PERSON.PERSONID

CHANGEDATE Y DATETIME N/A

IMPACTNUM Same as PLUSIMPACT.IMPACTNUM

MEMO Y ALN 100

STATUS Same as PLUSIMPACT.STATUS

COLUMN NULLS DATA TYPE LENGTH

DESCRIPTION Y ALN 100

IMPACTNUM N/A N/A N/A

IPPERMITID N INTEGER 12

NOTE Y ALN 50

PERMITNUM Y ALN 12

TYPE N UPPER 12

COLUMN NULLS DATA TYPE LENGTH

IMPACTNUM Same as PLUSIMPACT.IMPACTNUM

PLUSIPRETESTID N INTEGER 12

RETEST Same as PM.PMNUM

Nuclear-Specific Tables

Nuclear Database Tables and Columns 53

PLUSIPTS Table

PLUSIPUNVASSET Table

PLUSIPUNVTASK Table

PLUSITEMTERM Table

PLUSLOCPOS Table

COLUMN NULLS DATA TYPE LENGTH

IMPACTNUM Same as PLUSIMPACT.IMPACTNUM

TSID Same as PLUSTS.TSID

TSUNIT Same as LOCATIONS.PLUSUNIT

TYPE Same as PLUSTS.TYPE

COLUMN NULLS DATA TYPE LENGTH

ASSETNUM Same as ASSETS.ASSETNUM

ASSOCID Same as PLUSIPASSOC.ASSOCID

LOCATION Same as LOCATIONS.LOCATION

UNAVAILASSETID N INTEGER 12

COLUMN NULLS DATA TYPE LENGTH

CAUSESUNAVAIL N YORN 1

SEQUENCE Same as JOBTASK.TASKSEQUENCE

TASKID Same as WORKORDER.TASKID

UNAVAILASSETID Same as PLUSIPUNVASSET.UNAVAILASSETID

UNAVAILTASKID N INTEGER 12

COLUMN NULLS DATA TYPE LENGTH

ITEMNUM N UPPER 30

TERMID N UPPER 25

COLUMN NULLS DATA TYPE LENGTH

APPIVREQ N YORN 1

LOCATION Same as LOCATIONS.LOCATION

Nuclear-Specific Tables

54 IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSLOCRC Table

PLUSMTIMPACT Table

PLUSPMREF Table

PLUSPMSR Table

MEMO Y ALN 50

POSITION N UPPER 12

RESIVREQ N YORN 1

RESTCOND Y UPPER 12

COLUMN NULLS DATA TYPE LENGTH

COLUMN NULLS DATA TYPE LENGTH

LOCATION Same as LOCATIONS.LOCATION

MEMO Y ALN 50

POSITION Same as PLUSLOCPOS.POSITION

RESTCOND N UPPER 12

COLUMN NULLS DATA TYPE LENGTH

IMPACTNUM Same as PLUSIMPACT.IMPACTNUM

NOTIFCOMM Y ALN 256

PERMCOMM Y ALN 256

STATUS N UPPER 16

STATUSDATE Y DATETIME N/A

SUPPCOMM Y ALN 256

COLUMN NULLS DATA TYPE LENGTH

PMNUM N VARCHAR2 8

REF N VARCHAR2 50

COLUMN NULLS DATA TYPE LENGTH

PMNUM Same as PM.PMNUM

SRID Same as PLUSSR.SRID

SRTYPE Same as PLUSSR.TYPE

Nuclear-Specific Tables

Nuclear Database Tables and Columns 55

PLUSRESTPOS Table

PLUSSIGNONOFF Table

PLUSSR Table

SRUNIT Same as LOCATIONS.PLUSUNIT

COLUMN NULLS DATA TYPE LENGTH

COLUMN NULLS DATA TYPE LENGTH

ASSETNUM Same as ASSET.ASSETNUM

LOCATION Same as LOCATIONS.LOCATION

RESTCONDITION N UPPER 12

RESTPOSITION N UPPER 12

COLUMN NULLS DATA TYPE LENGTH

CLEARNUM Same as PLUSCLEARANCE.CLEARNUM

COMMENTS Y ALN 250

DATETIME Y DATETIME N/A

LABOR Same as PERSON.PERSONID

SIGNON N YORN 1

WONUM Same as WORKORDER.WONUM

WORKCOMPLETE N YORN 1

COLUMN NULLS DATA TYPE LENGTH

CHANGEDATE N DATETIME N/A

DESCRIPTION Y ALN 256

FREQUENCY Y ALN 256

NOTE Y ALN 256

SRID N UPPER 25

TYPE N UPPER N/A

UNIT Same as LOCATIONS.PLUSUNIT

Nuclear-Specific Tables

56 IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSTAG Table

COLUMN NULLS DATA TYPE LENGTH

APPCLEARNUM Same as PLUSCLEARANCE.CLEARNUM

APPCOMMENT Y ALN 250

APPIVREQ N/A YORN 1

APPLIER Same as PERSON.PERSONID

APPLIERDATE Y DATETIME N/A

APPNOTES Y ALN 250

APPPOSITION N UPPER 12

APPREVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

APPVERCOMMENT Y ALN 250

APPVERIFDATE Y DATETIME N/A

APPVERIFIER Same as PERSON.PERSONID

ASSETNUM Same as ASSET.ASSETNUM

LOCATION Same as LOCATIONS.LOCATION

LOCNOTES Same as LOCATIONS.PLUSLOCNOTES

PARTCOMMENT Y ALN 250

PARTDATE Y DATETIME N/A

PARTUSER Same as PERSON.PERSONID

RELEASED N YORN 1

RESCLEARNUM Same as PLUSCLEARANCE.CLEARNUM

RESCOMMENT Y ALN 250

RESIVREQ N/A YORN 1

RESNOTES Y ALN 250

RESPOSITION N UPPER 12

RESREVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

RESTORER Same as PERSON.PERSONID

RESTORERDATE Y DATETIME N/A

RESVERCOMMENT Y ALN 250

RESVERIFDATE Y DATETIME N/A

RESVERIFIER Same as PERSON.PERSONID

SHARETAG N YORN 1

STATUS N UPPER 12

Nuclear-Specific Tables

Nuclear Database Tables and Columns 57

PLUSTAGSTATUS Table

PLUSTERMSTATUS Table

PLUSTS Table

STATUSDATE N DATETIME N/A

TAGNUM N UPPER 12

TAGTYPE N UPPER 12

COLUMN NULLS DATA TYPE LENGTH

COLUMN NULLS DATA TYPE LENGTH

CHANGEBY Same as PERSON.PERSONID

CHANGEDATE Y DATETIME N/A

MEMO Y ALN 50

STATUS Same as PLUSTAG.STATUS

TAGNUM Same as PLUSTAG.TAGNUM

COLUMN NULLS DATA TYPE LENGTH

CHANGEBY N UPPER N/A

CHANGEDATE N DATE N/A

MEMO Y ALN 50

STATUS N UPPER 20

TERMID N UPPER 25

COLUMN NULLS DATA TYPE LENGTH

CHANGEDATE Y DATETIME N/A

DESCRIPTION Y ALN 256

MODEAPP Y ALN 256

MODENOTE Y ALN 256

NOTE Y ALN 256

UNIT N N/A 256

TSID N UPPER 25

TYPE N UPPER 12

Nuclear-Specific Tables

58 IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSTSSR Table

PLUSWOASSET Table

PLUSWOCLLINK Table

COLUMN NULLS DATA TYPE LENGTH

SRID Same as PLUSSR.SRID

TSID Same as PLUSTS.TSID

TYPE Same as PLUSTS.TYPE

UNIT Same as LOCATIONS.PLUSUNIT

COLUMN NULLS DATA TYPE LENGTH

CHILDPMNUM Y VARCHAR2 8

CHILDWONUM Y VARCHAR2 10

DESCRIPTION Y VARCHAR2 80

EQNUM Y VARCHAR2 8

JPNUM Y VARCHAR2 10

LDKEY Y INT 4

LOCATION VARCHAR2 8

OTHER Y VARCHAR2 15

PMNUM Y VARCHAR2 8

WONUM N VARCHAR2 10

COLUMN NULLS DATA TYPE LENGTH

APPDATE Y DATETIME N/A

APPRCOMMENT Y ALN 250

APPROVER Same as PERSON.PERSONID

BLOCKED N YORN 1

CAREQ N YORN 1

CLEARNUM Same as PLUSCLEARANCE.CLEARNUM

FIRSTADDCOMM Y ALN 250

FIRSTADDDATE Y DATETIME N/A

FIRSTADDNAME Same as PERSON.PERSONID

FIRSTREMCOMM Y ALN 250

Nuclear-Specific Tables

Nuclear Database Tables and Columns 59

PLUSWOTAGLINK Table

FIRSTREMDATE Y DATETIME N/A

FIRSTREMNAME Same as PERSON.PERSONID

RELEASED N YORN 1

REMOVED N YORN 1

REVISIONNUM Same as PUSCLEARANCE.REVISIONNUM

SECADDCOMM Y ALN 250

SECADDDATE Y DATETIME N/A

SECADDNAME Same as PERSON.PERSONID

SECREMCOMM Y ALN 250

SECREMDATE Y DATETIME N/A

SECREMNAME Same as PERSON.PERSONID

WONUM Same as WORKORDER.WONUM

COLUMN NULLS DATA TYPE LENGTH

COLUMN NULLS DATA TYPE LENGTH

COMMENTS Y ALN 250

DATETIME Y DATETIME N/A

LABOR Same as PERSON.PERSONID

RELCOMMENT Y ALN 250

RELDATE Y DATETIME N/A

RELEASER Same as PERSON.PERSONID

RELEASED N YORN 1

REMOVED N YORN 1

TAGNUM Same as PLUSTAG.TAGNUM

WONUM Same as WORKORDER.WONUM

Modified Tables

60 IBM Maximo for Nuclear Power: User’s Guide Addendum

Modified Tables

The following are Maximo tables modified with the listed Nuclear-specific information.

ASSETS Table

COMPANIES Table

EQUIPMENT Table

INVENTORY Table

ITEM Table

LOCATION Table

COLUMN NULLS DATA TYPE LENGTH

PLUSLOCNOTES Same as LOCATIONS.PLUSLOCNOTES

PLUSPRINTTYPE Same as LOCATIONS.PLUSPRINTTYPE

COLUMN NULLS DATA TYPE LENGTH

PLUSQSTDATE N DATE N/A

PLUSQUALSTAT Y UPPER 12

COLUMN NULLS DATA TYPE LENGTH

PLUSPROC Y VARCHAR2

COLUMN NULLS DATA TYPE LENGTH

PLUSABUY Y YORN 1

COLUMN NULLS DATA TYPE LENGTH

PLUSAUTOBUY Y YORN 1

PLUSPROC Y VARCHAR2 8

PLUSQVEND N YORN 1

COLUMN NULLS DATA TYPE LENGTH

PLUSGRA N YORN 1

Modified Tables

Nuclear Database Tables and Columns 61

LOCATIONS Table

PM Table

PLUSPRA N YORN 1

COLUMN NULLS DATA TYPE LENGTH

COLUMN NULLS DATA TYPE LENGTH

PLUSCRITICAL Y VARCHAR2 8

PLUSGRA Y NUMERIC 8,4

PLUSLOCNOTES Y ALN 256

PLUSMRULE Y YORN 1

PLUSPLSYSTEM Y UPPER 12

PLUSPRA Y NUMERIC 8,4

PLUSPRINTTYPE Same as LOCATIONS.PLUSPRINTTYPE

PLUSQUAL Y VARCHAR2 8

PLUSTECHSPEC Y YORN 8

PLUSUNIT Y UPPER 12

COLUMN NULLS DATA TYPE LENGTH

PLUSENAB N YORN 1

PLUSFREQNAME N VARCHAR2 8

PLUSGRACE N VARCHAR2 3

PLUSGRACE325 N YORN 1

PLUSISFREQ N YORN 1

PLUSMER N VARCHAR2 2

PLUSMILESTONE Y UPPER 6

PLUSONDMD N YORN 1

PLUSPLCY N VARCHAR2 3

PLUSPMOD N VARCHAR2 3

PLUSPMTYPE N VARCHAR2 3

PLUSSCHED Y ALN 256

PLUSSEQ Y UPPER 8

PLUSSEQDATE Y DATE/TIME N/A

PLUSSTARTTIME N DATE

Modified Tables

62 IBM Maximo for Nuclear Power: User’s Guide Addendum

PMSEQUENCE Table

POTERM Table

PRTERM Table

RFQTERM Table

RFQVENDORTERM Table

PLUSTSFREQ N NUMBER

COLUMN NULLS DATA TYPE LENGTH

COLUMN NULLS DATA TYPE LENGTH

PLUSCLEARNUM Same as PLUSCLEARANCE.CLEARNUM

PLUSREVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

COLUMN NULLS DATA TYPE LENGTH

PLUSITEMNUM Y UPPER 30

PLUSREV Y UPPER 10

PLUSTYPE Y UPPER 15

COLUMN NULLS DATA TYPE LENGTH

PLUSITEMNUM Y UPPER 30

PLUSREV Y UPPER 10

PLUSTYPE Y UPPER 15

COLUMN NULLS DATA TYPE LENGTH

PLUSITEMNUM Y UPPER 30

PLUSREV Y UPPER 10

PLUSTYPE Y UPPER 15

COLUMN NULLS DATA TYPE LENGTH

PLUSREV Y UPPER 10

PLUSTYPE Y UPPER 15

Modified Tables

Nuclear Database Tables and Columns 63

TERM Table

WOGEN Table

WORKORDER Table

COLUMN NULLS DATA TYPE LENGTH

PLUSREV Y UPPER 10

PLUSSTATUS N UPPER 20

PLUSSTATUSDATE N DATE N/A

PLUSTYPE Y UPPER 15

COLUMN NULL DATA TYPE LENGTH

PLUSGRACE N VARCHAR2 3

PLUSGRACE325 N YORN 1

PLUSGRACEDAYS N VARCHAR2 40

PLUSMOD N VARCHAR2 3

COLUMN NULLS DATA TYPE LENGTH

PLUS325DEADDATE N DATE N/A

PLUSASFOUND Y VARCHAR2 8

PLUSCLEARNUM Same as PLUSCLEARANCE.CLEARNUM

PLUSCLEARREQ N YORN 1

PLUSCMTNUM Y VARCHAR2 10

PLUSCRITICAL Y UPPER 8

PLUSGRA Same as LOCATIONS.PLUSGRA

PLUSGRACE N VARCHAR2 3

PLUSGRACE325 N YORN 1

PLUSGRACEDAYS N VARCHAR2 40

PLUSIMPCTRQD Y YORN 1

PLUSLOCK N YORN 1

PLUSMOD N VARCHAR2 3

PLUSMRULE Y YORN 1

PLUSPRA Same as LOCATIONS.PLUSPRA

PLUSPRA Y DECIMAL 8

Modified Tables

64 IBM Maximo for Nuclear Power: User’s Guide Addendum

PLUSQUAL Y UPPER 1

PLUSREFERENCE Y VARCHAR2 50

PLUSREFIMPCTNUM Y UPPER N/A

PLUSREGDUEDATE N DATE N/A

PLUSREVISIONNUM Same as PLUSCLEARANCE.REVISIONNUM

PLUSSCHED Y ALN 256

PLUSTCHSPEC Y YORN 1

COLUMN NULLS DATA TYPE LENGTH

© Copyright IBM Corp. 2007 65

Overview Maximo for Nuclear Power comes pre-configured with standard nuclear-process support. Workflows are used to direct process performance, and pre-established KPIs display the effectiveness of the process.

There is ready-made workflow support for the Standard Nuclear Performance Model (SNPM). The workflows are organized into a Single Point of Entry workflow, and adheres to industry guidance in the areas of Work Management, Equipment Reliability, Materials and Services, and Performance Improvement. They also provide a basis for further configuration to meet your unique site requirements.

Industry-standard KPIs organize process results and data into relevant groups that are used for objective feedback and benchmarking.

For more information about workflows, see the help for the Workflow Configuration application.

Set Up

Before you can use the provided workflows correctly, you must perform the following configuration procedures.

Generating Site Unit

Data must be segregate at the Unit level as well as at the Site level. You must incorporate this into the associated workflows. To accomplish this, perform the following:

Add a PLUSUNIT attribute to the PERSONGROUPTEAM table.

Add a Unit (PLUSUNIT attribute) data field to the Person Group application.

Identify the Person records in the Person Groups that have the appropriate Unit ID.

Revise the database relationships to use the data field, for example. PERSONGROUP = 'PLUSUNCD' and USEFORSITE = :ASSETSITEID and PLUSUNIT = :PLUSUNIT

Standard Nuclear-Process Support 12

Workflows Provided

66 IBM Maximo for Nuclear Power: User’s Guide Addendum

Setting up Person Groups

Each group contains a place holder person record: PLUSPERSON. Replace this record with records of individuals who will receive workflow assignments as part of each specific group.

The following person groups are provided:

Validate, Enable, and Activate the Workflows

Validate, enable and activate the PLUSSPOE and PLUSWO workflows.

The PLUSITEM and PLUSFACLTY workflows are sub processes that are installed, validated, and enabled.

Workflows Provided

You use the workflows provided with Nuclear Power in a Multiple Organization or Multiple Site environment. The workflow process selects the correct individuals for assignments based on the Organization and Site affiliation of the record. The workflows included cover the following processes:

AP-928 Work Management—This workflow addresses emergency, minor, and planned maintenance.

AP-913 Equipment Reliability—This workflow addresses corrective action and continuous improvement requirements.

AP-908 Materials and Services—This workflow brings the Procurement Engineer into the process. It also addresses item creation, revision, and retirement.

AP-903 Performance Improvement—This workflow focuses on plant performance.

PLUSFACD Facilities Coordinators. Assigned to each Plant to manage service requests for Buildings and Grounds.

PLUSMATS SCM Material Supervisors. Manages the Supply Chain Materials function at a site. Assigns work to Material Analysts.

PLUSPESP Procurement Engineering Supervisors.

PLUSUNCD Unit Work Coordinators. Assigned to each Plant Unit to manage new work requests for the Work Coordination Team.

PLUSOPSR Operations Reviewers. Senior Reactor Operators assigned on each shift to review new plant related service requests and perform other work management related functions.

PLUSPLNS Maintenance Planning Supervisors. Assigned to each Site, manages new work orders requiring planning.

Workflows Provided

67 IBM Maximo for Nuclear Power: User’s Guide Addendum

Single Point of Entry

Each workflow starts with the single point of entry. This is where the workflow is evaluated by the system to see which other workflow it belongs in.

Single Point of Entry Workflow

See the Single Point of Entry Workflow diagram while reading this description of the workflow.

The service request starts the process. Each request must have a classification before it can proceed. When entering a service request, the user selects one of three Classifications from the Nuclear Classification (PLUSNUC):

PLUSPLNT—Plant Related IssuePLUSITEM—Supply Chain materials issuePLUSFAC—Facilities request.

The clasification of the request is then checked by the system and is routed into the proper workflow. See the following explanations of the workflow as it flows out at points A, B, and C.

Plant SSC Issue

The following roles use the Plant SSC Issue workflow:

Unit Work CoordinatorOPS Reviewer

See the Plant SSC Workflow diagram while reading this description of the workflow.

Service requests that are plant SSC issues are assigned to Operations for review. The OPS review determines if the classification is correct and also if priority maintenance is required.

For priority maintenance, a work order is created and is passed to the OPS Reviewer to review. The work order is inserted into the workflow where it is passed to the Unit Work Coordinator.

Non-priority maintenance requests are passed directly to the Unit Work Coordinator. When the request involves critical plant equipment, a Problem Record is created for Equipment Corrective Action reviews.

Workflows Provided

68 IBM Maximo for Nuclear Power: User’s Guide Addendum

The Unit Work Coordinator presents all requests to the Work Coordination Team and acts upon the team recommendations. Team review has the following outcomes:

The required work is classifed as tool pouch maintenance and a work order is not required.

The required work is classified as Minor Maintenance. A work order is created and entered into the work order workflow.

The required work is classified as Planned Maintenance. A work order is created and entered into the work order workflow.

The request is closed and the reason is documented.

Plant SSC Workflow

Work Order Workflow

The following roles use the Work Order workflow:

Maintenance SupervisorOPS ReviewerPlanning SupervisorPlanner

Workflows Provided

69 IBM Maximo for Nuclear Power: User’s Guide Addendum

Maintenance

Work Order Workflow

See the Work Order Workflow diagram while reading this description of the workflow.

The work order is checked to see if it is minor maintenance, part of a PM, or neither. The results are:

If it is minor maintenance, it is passed to the Maintenance Supervisor. The work is compledted and documented and the workflow ends.

PM work orders bypass planning and go to Maintenance and Operations for review.

If the workorder is Planned Maintenance, which follows the main path of the flowchart.

The Maintenance Supervisor passes the workorder to Operations for review and release of work.. It is then passed to Maintenance to complete the work. At any time in this stage, or during testing of the work, the workorder can be passed back to the Planner for editing.

After maintenance testing is completed, the workorder is passed to Operations for operability testing. After operability testing, the work order can be returned to maintenance for re-work or close-out.

How it Works

70 IBM Maximo for Nuclear Power: User’s Guide Addendum

Completed PM work orders on critical plant equipment that have an As Found Code that indicates a failure or unanticipated repair are sent for review by the equipment owner, using the Location Custodian to make the assignment.

Facilities Workflow

Service requests that apply to facilities are assigned to the site Facilities Work Coordinator. This person assigns the work to the proper person or group and this workflow stops.

The following role uses the Facilities workflow:

Facilities Work Coordinator

Facilities Workflow

Item Workflow

Service requests that apply to materials are assigned to the site Supply Chain Materials Supervisor. This person assigns the work to the proper person or group. The Materials Analyst completes the task then changes the SR owner to the appropriate Procurement Engineer

The following roles use the Item Workflow:

Supply Chain Materials SupervisorMaterials AnalystProcurement Engineer

Item Workflow.

How it Works

Using Person Groups and Database Relationships, the workflow process selects the appropriate person record to assign to the workflow task.

The Person records in a Person Group are identified to the Organization and Site where they work. A database relationship for each Person Group is used to select the records affiliated with the Organization and Site on the record for the workflow.

How it Works

Standard Nuclear-Process Support 71

Example:

You have a Person Group named PLUSUNCD. This group consists of the Unit Work Coordinators. The Organization and Site they are assigned to is indicated when you select the applicable Site.

You also have a Database Relationship named PLUSUNITCOORD. This relationship is used to select the person from the named Person Group associated with the Site on the Service Request.

Child Object: PERSONGROUPTEAM

Where clause: PERSONGROUP = 'PLUSUNCD' and USEFORSITE = :ASSETSITEID

Roles

You access ach workflow through the Start Center. Since each Start Center is unique to each role, what you see and are allowed to do is determined by your role. Not all roles are used for all workflows. The following representative nuclear power roles were defined:

Unit Work Coordinator—The person group that manages new work requests for the work coordination team.

OPS Reviewer—The person group that the SRO assigned on each shift to review new plant-related service requests.

Facilities Coordinator—The person group that manages facilities service requests for buildings and grounds.

SCM Material Supervisor—The person group that manages the Supply Chain Materials function at a site level. It also assigns work to the Material Analysts.

Material Analysts—The person group that reviews, acts on, and approves all item related requests.

Procurement Engineer—The person group that reviews, acts on, and approves all item related requests.

Procurement Engineering Supervisor—The person group that manages the procurement engineering function at a site. This group also assigns work to Procurement Engineers.

Planning Supervisor—The person group that manages new work orders that require planning.

OPS Reviewer—The SRO assigned, on each shift, to review work orders. The Person Group with Site designation for each entry.

Planner—The person group that is responsible for all aspects of work order planning activities.

Maintenance Supervisor—The person group that is responsible for implementing the planned work.

Start Centers

72 IBM Maximo for Nuclear Power: User’s Guide Addendum

Equipment Custodian—The person group that is responsible for reliability of the specified equipment.

You start by entering a Service Request (SR). The type of SR you enter determines which workflow is used.

Start Centers

A Start Center is also provided for each role identified in the workflows. These Start Centers have basic portlets configured for a few applications. You can further configure these Start Centers to meet your requirements.

Key Performance Indicators

The Key Performance Indicators are provided and created as standard indicators to use for all Sites, Units and Systems within the Nuclear Organization. To do this, placeholders in the form of a '%' sign are used for Site, Unit and System in the Where Clauses as applicable.

You must duplicate each indicator and revise the Where Clause with the appropriate Site ID, Unit ID, and System ID.

Target, Caution, and Alert values are mandatory and are set to '0'. Enter appropriate values for these variables.

These KPIs are defined as Public. You must assign them to the appropriate Start Center after you duplicate and revise them.

© Copyright IBM Corp. 2007 73

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

74 IBM Maximo for Nuclear Power: User’s Guide Addendum

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

IBMDB2MaximoTivoliWebSphere

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other contries, or both.

75

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Other company, product or service names may be trademarks or service marks of others.

76 IBM Maximo for Nuclear Power: User’s Guide Addendum