Cmms Implementation Guide

I. System

a. Oracle 10g Installation

b. Maximo Installation

c. Actuate Installation

d. Client-Server (Network)

II. Database Configuration (see attached Excel spreadsheet - MAXIMO DB Mapping.xls)

a. Provide DZSP with v.6.2 ERD and data dictionary

b. v.5.2 was provided to DZSP preconfigured with no ERD nor data dictionary

c. We will provide you with the current major database objects that we currently use

d. Recommend strategy of adding the "missing" columns in v.6.2 with the same naming convention

e. Data mapping Ð'- what is your timeframe?

f. Data migration Ð'- what is your timeframe?

III. Accounts and groups (see attached MAXIMO Usergroups.xls)

a. Setting up User Groups

i. v.5.2 currently has three main types of user groups Read Only, Insert/Update, Update

ii. There are three major group access

1. Access to Work Order tracking, Equipment, PM

2. Access to Transportation modules

3. Access to all

b. Setting up Users Ð'- recommend we migrate current "active" users (w/ passwords) to v.6.2

IV. Domain Values/ Valuelist (see attached MAXIMO Value List.xls)

a. Priority (workorder.wopriority)

b. Work Center (workorder.supervisor)

c. Work Type (workorder.worktype, pm.worktype)

d. GL Account (workorder.glaccount)

e. Customer Survey Rate (workorder.aischeckbox)

f. Work Subtype (workorder.wopm5)

g. Equipment (workorder.eqnum)

h. Location (workorder.location)

i. Failure Class (workorder.failurecode)

j. Material Info (workorder.wopm2)

k. Severe Hazard (workorder.hazseverity)

l. Category (workorder.category)

m. Pool (equipment.io_number)

n. Category (equipment.transmission)

o. Assignment Status (equipment.assignstatus)

p. Alpha code (equipment.alphacode)

q. Status (workorder.status)

r. Status (equipment.status)

s. Equipment type (equipment.eq23, pm.pmeq2, workorder.woeq13)

t. Fuel category code (equipment.fuel_cat_code)

u. Fuel type (equipment.fuel_type)

v. Wo priority (pm.priority)

w. Work sub type (pm.pm10)

x. Work order status (pm.wostatus)

V. Configuring the Layout

a. See screen shots provided (Maximo 5_2 Screen Shots.ppt)

b. Labor

i. These are not managed manually in Maximo

The values of the labor is mapped to our Financial employees table which is managed by our HR department

ii. A daily procedure, executed through an Oracle job queue, updates the entries in the labor table

c. Crafts

i. Currently, crafts are incorporated into the maximo.labor table, where labor.iscraft='Y'

ii. These are not managed manually in Maximo

The values of the labor is mapped to our Financial labor category table which is managed by our HR department

iii. An annual procedure updates the entries in the labor table based on a spreadsheet provided by the Comptroller

d. GL Components

i. Currently there are four GL components defined in v.5.2, but DZSP only utilizes one component which is six characters

e. GL Account and update procedure

i. Currently, GL Accounts are not managed manually in Maximo

ii. The values of the GL Account is mapped to our Financial projects table which is managed by our Finance department

iii. A daily procedure, executed through an Oracle job queue, updates the entries in chartofaccounts

iv. The procedure primarily links into the Financial database table, uploads all new records, and updates existing ones (active to inactive, etcÐ'...)

v. The procedure is executed manually if the need arises during business hours

f. Locations

i. The list of locations is provided by the Government for mass upload

ii. Locations naming convention is based on the Governments locations template

g. Equipment

i. The list of equipment is provided by the Government through the Engineering department

ii. Equipment numbers follow a prefix template

1. Facilities equipment follow a pattern of 2 letters + 3 occupant identifying numbers + 4 digit sequence (example MA5200001)

a. Two letter prefix: MA

b. Three numbers identify occupant

i. 180 Ð'- Naval Hospital

ii. 510 Ð'- Branch Dental Clinic

iii. 520 Ð'- ComNamMar

iv. 530 Ð'- DODEA

v. 540 Ð'- NCTS

vi. 550 Ð'- NavFacMar

vii. 560