J-0200000-13 - MAXIMO DIRECT ENTRY PROCEDURES.docx

SOUTHEAST

MAXIMO 7.6

NAVFAC MAXIMO DIRECT ENTRY PROCEDURES

NAVFAC SOUTHEAST TRAINING MANUAL

N69450-XX-X-XXXX

MID-SOUTH BOS

Table of Content

1. THE PURPOSE OF SERVICE REQUEST/WORK ODRER…………………………….………page 3

2. QUERYING A SERVICE A REQUEST……………………….…………………………………page 4 - 5

3. HOW TO CREATE SERVICE REQUEST.………………………………………………….…page 6 – 10

4. THE WORK ORDER……………………………………………..…………………..……………page 11 – 19

5. APPROVING THE WORK ORDER…………………………………………………….…………….page 20

6. ENTERING LABOR AND MATERIAL…………………………………………………………page 21– 30

7. COMPLETING THE WORK ORDER…………………………………………….……………………page 31-32

8. HOW TO CREATE AN ASSET……………………………………………………………………page 33-36

9. HOW TO DCR AN ASSET………………………………………………………………………..Page 37-39 10.

The Purpose of Service Request/Workorder This document will cover the fields necessary for a person to create and managing Service Requests and Workorders in Maximo. It gives an overview of NAVFAC SE data requirement for Service Requests/Workorders. Although the Regional Call Center enter all Emergency, Urgent, and Service tickets; there will be ocassions when an indivdual will need to enter Planned work in Maximo, (examples: Projects both Minor and Specific and PMs).

Service Requests Application The Service Requests application is used to manage requests for services that involve an asset or location at your site. For example, a request to repair an outlet or fix a piece of equipment.

Service requests include requests that are communicated to you directly from a user, for example from a phone call, e-mail message, direct contact or from an automated workflow process. The owner of a service request is responsible for managing the ticket to completion. The ownership of a service request can be assigned to another individual or a workgroup. The assigned person is responsible for the request from creation to completion.

The ticket identifies who the service affects and what priority it has; it specifies why the service request might be escalated. If an issue arises the status can be changed as the request moves toward completion. All communication that pertains to the service request can be stored in the log of the service request to provide a clear history of its lifecycle. A service request record captures information about a request, including the type of service, who needs it, where, when, and why. The Service Request is used to manage requests for services that involve an asset or location in your enterprise.

Work Order Tracking Application The Work Order Tracking application is used to plan, review, and approve work orders for assets and locations. When you generate a work order, you initiate the maintenance process and create a historical record of work being performed. This Module tracks past and present work and helps you plan for future work.

QUERYING A SERVICE REQUEST

From the Start Center go to: 1. Favorite Applications, 2. My Recent Application, or 3. Go to Applications. After you selected the ‘Service Requests’ applications, the SR module will display.

Then click on the advance search.

Advance search has a major over haul in the SR module; after the major field, all other fields have been arranged in Alphabetical order.

QUERYING A SERVICE REQUEST

If you are looking for a specific Service Request (SR), you can enter the number:

Once you click on the Service Request it will be displayed.

Then you will see a detailed report.

HOW TO CREATE SERVICE REQUEST

To get to the Service Request or the Work order Tracking Module from the Start Center you can get there three ways:

1. Favorite Applications

2. My Recent Applications

3. Go To Applications

Click ‘New Service Request’ button

HOW TO CREATE SERVICE REQUEST

Service Request: – number is auto-populated by Maximo.

1. Status: – When creating a new Service Request the status will be ‘NEW’.

2. Lead: – Blank, if the Lead is known it can be populated.

3. Site: – Auto-populate with 10701 for Southeast.

4. The section in yellow is a dummy GL account number because FY GL account number is not in Maximo test site. The right GL account number is S.2024ST1H.XX.N25GSW000001

DESCRIPTION

5. Project Title: – Brief description of the work needed. (Replace condenser)

6. Details (Long Description) – Provide detailed information regarding the ticket.

7. GL Account – The Job Order number (Customer’s JON paying for the Job. The GL account number:). S.2024STP2.XX.N25GSW000001 THIS NUMBER CHANGES EVERY FISCAL YEAR. (VALUE LIST)

8. Work Center – Work Center that will perform the Work (MIL_CTR1). (VALUE LIST)

9. Craft – The Craft assign to this type of work. (VALUE LIST)

10. Crew – The Crew assign to this type of work. (VALUE LIST)

11. CLIN – This is for BOSC Bases, the ELIN (MIL-17D2123-C005BH) is an example. (VALUE LIST)

12. Service Provider Ref Code – The BOSC Work order number.

HOW TO CREATE SERVICE REQUEST

LOCATION INFO

13. Location – Site where is the work going to be performed. Locations are identified by the Base Area name and the facility number (example: MEMPHI-1775), this location is in Memphis and the facility number is 1775).

NOTE: If a new location needs to be enter in Maximo, a STS ticket needs to be submitted.

14. Location Description – Name of the location, auto-populate from the Location application. (VALUE LIST)

15. Location Detail – Any addition specify detail to describe the locations.

16. Location POC – Person at the location that should be contacted.

17. Location POC Phone – The location POC phone number.

18. Asset – The Asset number, if work is to be performed on an Asset. (VALUE LIST)

19. Customer Ref Code – Customer identification assigned to each customer. (VALUE LIST)

20. Zone – Auto-populate from the Location. (VALUE LIST)

21. PWD – Auto-populate from the Location. (VALUE LIST)

INFO

22. Work Type – The classification of the work assigned to the Service Request (SR) (example ROUTINE). (VALUE LIST)

23. Sub Work Type – The second level of work associated to the SR that is derived from the Work order (example FACILITIES). (VALUE LIST)

24. Information Section

Routine Urgent Emergency

Routine Emergency

Routine Urgent Emergency

Routine Emergency

25. Activity – A Navy Installation within a Facilities Engineering Command (FEC). This field auto-populates when a valid GL Account is applied to the Service Request (example RBOSCNTR). (VALUE LIST)

CATEGORY

26. Business Line, P/S Code / NAVFAC Work Category – For Emergency, Urgent, and Routine Work types BL/PS Code/Work Category will be auto-populated for you. (Any auto-populated field can be changed) (example; Business Line: PW, P/S Code H1, NAVFAC Work Category: 4)

27. Submit Action – Tell the status of the created Work order.

28.

RESPONSIBILITY – This section is auto-populated by Maximo.

29. Component – Component Command responsible for the SR. (NAVFAC Southeast)

30. Target System – Denote the system that the Work order will be managed according on the entries on the Business Line, P/S Code, NAVFAC Work Category (either Maximo or eProjects).

31. Execution Team – Auto-populate from Location.

32. Responsible Team – Auto-populate from Location. HOW TO CREATE A SERVICE REQUEST

USER INFORMATION

33. Reported Date/By/Name/Phone/E-Mail – Auto populates with the current date and the user’s information of the person entering the ticket (information can be modified).

34. Customer ID Name/Phone/E-Mail/Customer Reference # – This is the building manager responsible for the building. Use the Detail Menu to select the caller’s name. If the caller name exists in the PEOPLE table their information will auto-populate after you enter the ‘Customer ID’. If name does not exist, enter an STS ticket to have information added to Maximo.

35. Affected Date – Date when user was affected by issue. Auto-populated

36. Entered By – Login/user name of the person entering the SR. Auto-populated

37. Entered Date – Actual date of the SR was entered into the system. Auto-populated

38. Modified By – The last person to change the SR. Auto-populated

39. Modified Date – The date on which the SR was changed. Auto-populated

REQUIREMENT INFORMATION – NOT REQUIRED FOR CMMB PROJECTS

40. Requirement Priority – The urgency of the work needed.

41. Requirement Cost – The cost of the work needed.

42. Requirement Category – CIMU, RPIE, or BOTH

43. Requirement Type – Type of work needed to fulfil the requirement

44. Requirement Year – The year the requirement need to be fixed.

45. Requirement Facility ID – The build number that needs the work performed.

IPL INFORMATION - NOT REQUIRED FOR CMMB PROJECTS

46. IPL Type – Integrated Product List Type associated to the SR. (VALUE LIST)

47. Project# – IPL Project Number associated to the SR.

48. Program Year – Indicates the IPL Program Year of the SR if applicable. (VALUE LIST)

49. Quarter – IPL Quarter associated with the SR if applicable. (VALUE LIST)

50. Command Sponsor – The Command Sponsor code is defined as a sub-designator indicating the Command Sponsor for the identified special project requirement. (VALUE LIST)

51. Preponderant User – The significant user UIC.

52. Users UIC – Identifies the users UIC.

53. IPL Priority – Integrated Product List Priority associated to the Service Request. (VALUE LIST)

54. Priority Score – Integrated Product List Priority Score associated to the Service Request.

55. Work Class – The Work Class code is defined as a sub-designator indicating the work class for the identified requirement. A Work Class shall be chosen from the drop-down list in Maximo and used in conjunction with IPL Type and Funding Type. (VALUE LIST)

56. SIC – The SIC code is defined as a sub-designator indicating the SIC for the identified special project requirement. A SIC shall be chosen from the drop-down list in Maximo and used in conjunction with the IPL Type, Funding Type, and Work Class codes. (VALUE LIST)

HOW TO CREATE A SERVICE REQUEST

57. Funding Type – Identifies the Funding Type of the Service Request. (VALUE LIST)

58. Expected Cost – The Expected Cost of the Service Request.

SERVICE REQUEST DETAILS - NOT REQUIRED FOR CMMB PROJECTS

59. UNIFORMAT Master System – Identifies the UNIFORMAT Master System to the Service Request if applicable. (VALUE LIST)

60. Classification – When you specify a classification for an object, you can organize related parent and child objects in a hierarchical structure, similar to a file directory. You can then drill up and down through the hierarchy to view associated items. Create and manage classifications in the Classifications application. (VALUE LIST)

61. Class Description – Description of the classification specified for this record. (VALUE LIST)

62. Reported Priority – Priority of Service Request as determined by person making the request. (VALUE LIST)

63. Internal Priority – Priority of the Service Request as determined by the Service desk agent. (VALUE LIST)

DATES

64. Target Start – The Target Start Date for the Service Request.

65. Target Finish – The Target Finish Date for the Service Request.

66. Actual Start – Actual Start Date. Enter a date or click the Select Date button and select a date.

67. Actual Finish – Actual finish date. Enter a date or click the Select Date button and select a date.

GLOBAL ISSUES

68. Is Global Issue – Flag used to determine if a Ticket/Service Request is a Global issue.

69. Global Ticket – If it is a Global issue the number of the ticket. (VALUE LIST)

70. Global Ticket Class – Identifies the Class of the global ticket.

MULTIPLE ASSETS, LOCATIONS

71. Asset/Location/Target Description/Sequence/Mark Progress?/Site –If more than one Asset is assigned to this Service Request; you can add by clicking ‘New Row’.

After entering and checking all pertinent data; SAVE THE RECORD.

THE WORKORDER

Submit the ‘Service Request’ to convert the Service Request into a Work order; on the ‘Common Actions’ menu, select the ‘Submit Request’ icon.

SYSTEM MESSAGE: The message you will receive is: ‘BMXZZ0007E - Are you sure you want to submit this Service Request? More information. Click ‘Yes’.

The next message is: BMXZZ0006E - Work Order XXXXXX is created successfully in the Submit Request Process. Click ‘OK’.

The Status will change from ‘NEW’ to ‘REQUESTED’.

THE WORKORDER

Go to the Related Records tab and the Work order number will be displayed under ‘Related Records Detail Click on the double arrow next to the Work order, then ‘Go To’, and then ‘Work Order Tracking’.

Maximo will take you to the Work order application; this will allow you to modify the Work order, if data needs to changed or add data as needed, before you approve the Work order.

THE WORK ORDER

WORKORDER DETAIL TAB

1. Work Order – Identifies the Work order auto-populated by Maximo.

2. Location – Identifies the work orders Location. This is not necessarily the asset’s location; however, if an Asset is entered its location will default to the Asset Location. (VALUE LIST)

3. Asset – Identifies the Asset associated with the Work order. (VALUE LIST)

4. Parent WO – Parent of the Work order shown in the Work order field. If the field is blank, the Work order in the Work order field is a top-level Work order. To assign a Work order to a parent, Select Assign to New Parent from the Select Action menu.

5. Work Center – Identifies the person group responsible for the work. (VALUE LIST)

6. Lead – Lead person responsible for the work. (VALUE LIST)

7. Classification – When you specify a classification for an object, you can organize related parent and child objects in a hierarchical structure, similar to a file directory. (VALUE LIST)

8. Launch Entry Name – Description of the classification specified for this record.

9. Failure Class – Failure class of the defined work asset. The failure class is the top level of the failure hierarchy. (VALUE LIST)

10. Problem Code – The Problem being reported based on the defined Failure Class. This is usually the code in the second level of the failure reporting hierarchy. (VALUE LIST)

11. Project Number – IPL Project Number.

12. CLIN – Contract Line Item Number. (VALUE LIST)

13. Type Service – Service Item Number. (VALUE LIST)

14. SIC – The special project requirement. A SIC shall be chosen from the drop-down list in Maximo and used in conjunction with the IPL Type, Funding Type, and Work Class codes. (VALUE LIST)

15. Command Sponsor – The command sponsor code is defined as a sub-designator indicating the Command Sponsor for the identified special project requirement. (VALUE LIST)

16. Supported Command Program – (NOT USED IN SE)

17. Reimbursable – Work order reimbursable?

18. Description (work order) – Describes the Work order, to enter additional information, click the Long Description button.

19. Description (location) – Description of the locations. To enter or view additional information, click the Long Description button.

20. Description (asset) – Description of the Asset.

21. Work Type – The classification of the work assigned to the Service Request (SR). (VALUE LIST)

22. Sub Work Type – The second level of work associated to the SR that is derived from the Workorder. (VALUE LIST)

23. Activity – A Navy Installation within a Facilities Engineering Command (FEC). This field auto-populates when a valid GL Account is applied to the Service Request. (VALUE LIST)

24. GL Account – The Job Order number (customer JON paying for the Job). The GL account number is S.2024STP2.XX.N25GSW000001. THIS CHANGES EVERY FISCAL YEAR. (VALUE LIST)

THE WORKORDER

25. Master System – UNIFORMAT classification for Buildings and Assets. (VALUE LIST)

26. System – UNIFORMAT classification for Buildings and Assets. (VALUE LIST)

27. Sub-System – UNIFORMAT classification for Buildings and Assets. (VALUE LIST)

28. Business Line – Business Line associated with the Work order (for PWD use PW). (VALUE LIST)

29. PS Code – The Product and Service code of the Work order. (VALUE LIST)

30. Category of Work – NAVFAC Work Category Associated to the Work order derived from the Business Line / PS Deliverable fields. (VALUE LIST)

31. Component – Component Command responsible for the Work order. (NAVFAC Southeast)

32. Expected Cost – The expected cost for the Work order.

33. Funding Type – The type of funding associated with the Work order. (VALUE LIST)

34. IPL Priority – Integrated Product List Priority associated to the Service Request.

35. Work Class – The Work Class code is defined as a sub-designator indicating the work class for the identified requirement. A Work Class shall be chosen from the drop-down list in Maximo and used in conjunction with IPL Type and Funding Type. (VALUE LIST)

36. Program Year – Indicates the IPL Program Year of the SR if applicable. (VALUE LIST)

37. Quarter – IPL Quarter associated with the SR if applicable. (VALUE LIST)

38. Service Code – Link to Failure Code. (VALUE LIST)

39. Link – (NOT USED)

40. Site – Identifies the site (10701).

41. Class – Identifies the Work order class.

42. Status – Status of the Work order, for example, in progress, waiting on material, waiting for approval, completed, or closed.

43. Status Date – Date the Work order status was last changed.

44. Approved Date – The Date on which the Work order was last approved.

45. Inherit Status Changes? – Specifies whether the Work order’s status will change when its parent Work order status changes. If the check box is selected (the default), the work order's status will change when the parent work order's status changes. If the check box is cleared, the work order's status will not change when the parent work order's status changes.

46. Accepts Charges - Check box specifies whether or not the work order accepts charges. If the check box is selected (the default), the work order accepts charges. If the check box is cleared, the work order does not accept charges, and you cannot enter charges on the work order.

47. Is Task - Specifies whether the work order is a task. If the check box is selected, the work order is a task. If the check box is cleared, the work order is not a task.

48. Record Type - Used to segregate between Facilities and Transportation Work Orders Auto-populate.

49. Generated From – Used to denote how the Work order was generated.

50. Modified By – Person who modified or changed the Work order last Auto-populate.

51. Modified Date – Date the Work order was last modified.

52. Entered Date – The actual date of when the SR/Work order was entered into the system.

THE WORK ORDER

53. Preponderant User – The significant user (N69450) SE UIC Auto-populate.

54. Description – Name and/or description of the company. Click the long description of the Description button to enter or view a long description Auto-populate from the UIC.

55. User UIC – Users UIC

56. Description – Name and/or description of the company. Click the long description button to enter to view a long description Auto-populate from the IIC.

SCHEDULE TAB:

Scheduling Information:

1. Target Start – Date the Work order is targeted to begin. If the Work order is generated from a PM, the date is supplied by the PM Work order generation process.

2. Target Finish – Date the Work order is targeted to be completed.

3. Scheduled Start – Date and time the work is scheduled to begin.

4. Scheduled Finish – Date and time the work is scheduled to complete.

5. Predecessors – A non-persistent field to display the Work orders predecessor Work orders.

6. Actual Start – Date and time the actual work began.

7. Actual Finish – Date and time the actual work was completed.

8. Duration – Estimated remaining number of hours needed to complete the work.

9. Time Remaining – Indicates the number of remaining hours needed to complete the work. Field can modify until Work order is closed.

10. Next Due Date – For PM Work order, the next date the PM is due Auto-populate from the PM.

11. Originating Record – Identifies the source record that was used to create this record.

12. Originating Record Class – Originating record’s class, for example: change, release, incident, problem, or Work order.

13. Has Follow-up Work? – Specifies whether the work order has follow up work. If the check box is selected, there is follow up work. If the check box is cleared (the default), there is no follow up work.

14. Interruptible - Specifies whether the work order is allowed to be stopped once the work has begun and then restarted. If the check box is selected, the work can be stopped. If the check box is cleared, the work cannot be stopped and restarted.

Address Information:

15. Service Address – The address code identifies a service address. It must be unique by site for each service address.

16. Formatted Address – This address is formatted according to the map provider's requirements and is updated when a location is found on the map tab. You can use the formatted address to search for addresses on the map tab.

THE WORK ORDER

17. Street Address – The street address details of the service address, such as the house number, the street direction prefix, and the name of the street. Additional details can include the type of street, the street direction suffix, and whether the address is an apartment, a unit, or a suite.

18. Description – The description of the service address.

19. City – The city of the service address.

20. State/Province – The state or the province of the service address.

21. Description – State/Province description.

Multiple Assets, Locations

RESPONSIBILITY TAB:

Responsibility Information:

1. Reported By – Identifies the person reporting the Work order.

2. Reported Date – The date and time the Work order was reported.

3. On Behalf Of – Identifies for whom this work order has been created. For example, if someone did not have access to a computer, another user could create the work order on behalf of that person.

4. Phone – The phone number associated with the Work order. It the reported by person has a phone number associated with it, the phone number is the default for this field.

5. Craft – The Craft Code associated to the Work order if applicable. (VALUE LIST)

6. Customer ID –The Point of Contact associated to the Work order.

7. Customer Name – The Customer Name associated to the Work order.

8. Customer Phone – The Point of Contact’s Phone Number.

9. Customer Email ID – The Point of Contact’s E-mail address.

10. Customer Ref Number – Customer identification assigned to each customer. (VALUE LIST)

11. Lead – Lead person responsible for the Work. (VALUE LIST)

12. Supervisor – Supervisor of the work. Maximo copies this information from the job plan, if there is one. You also can select a supervisor. (VALUE LIST)

13. Crew – ID for a given crew within a craft associated to the Work order if applicable. (VALUE LIST)

14. Service – Defines the service for the work order, for example: customer support, painting, print, telecommunications, and welding.

15. Service Group – Defines the service group for the Work order, for example IT, production, facility, or fleet.

16. Vendor – Identifies the vendor responsible for the work.

17. Execution Team – The Execution Team responsible for the work auto-populate from location table.

THE WORK ORDER

18. Responsible Team – The Responsible Team responsible for the work auto-populate from location table.

JOB DETAILS TAB:

Job Details:

1. Job Plan – Identifies the Work order Job Plan from the PM. When you assign a Job Plan to a Work order, Maximo copies the Job Plan operations, material, labor, and tool information to the Work order’s work plan.

2. PM – Identifies the Preventive Maintenance record from which the Work order was generated. It auto-populate from the auto-gen program.

3. Safety Plan – Identifies the Safety Plan applied to the Work order.

4. Contract – Identifies the warranty contract for the asset on the Work order if applicable.

Asset Details:

5. Asset Up? – Asset Status (Running-Not Running)

6. Warranties Exist? – Specifies whether any warranties exist for the Asset on the Work order. If the check box is selected, warranties exist. If the check box is cleared (the default), there are not warranties for the asset.

7. Charge to Store? – Check box that indicates whether charges on the Work order should be added to the Asset record.

8. Service Provider Ref Code – BOSC Work order number.

Priority:

9. Asset/Location Priority – Identifies the Priority level copied from the Asset or location record and used the schedule the Work order. (VALUE LIST)

10. Priority – Identifies the importance of the Work order from 0-999, where 0 is the lowest priority and 999 is the highest. (VALUE LIST)

11. Priority Justification – Describes why the Work order received the priority it has been assigned.

12. Risk Assessment – Defines the risk level of the Work order. Risk may be a numeric value or a term such as High, Medium, Low, or some other value based upon your business definitions.

OUTAGE LOG TAB:

UEM Work Order Information:

1. Outage Type – Identifies the type of outage. (VALUE LIST)

2. Outage Cause – Identifies the reason for the outage. (VALUE LIST)

THE WORK ORDER

3. Num of Bldgs. Affected – Identifies the number of Building affected by the outage.

4. Outage Start Date – Identifies the date and time the outage started.

5. Outage End Date – Identifies the date and time the outage ended.

DETAIL LOCATION TAB:

Detail Location Information:

1. Custodian – Identifier of the person.

2. Names – A nick name or a friendly name that this person can be identified with. This field is automatically populated when values are entered in the First Name and/or Last Name fields.

3. Primary Phone – The primary phone number that is used to contact this person.

4. Zone – Auto-populate from the Location. (VALUE LIST)

5. Customer Ref Code – Customer identification assigned to each customer. (VALUE LIST)

6. Location POC – Person at the location that should be contacted.

7. Detail Location – Additional Location Information associated to the Workorder.

8. Additional Location Information – Other information related to the Location.

PLANS TAB:

This tab is used for Child of Work Order, Tasks for Work Orders, Labor, Material, Services, and Tools in the planning stage of a Planned Work order.

ASSIGNMENTS TAB:

This tab is used to assign skill craft to the Work Order.

RELATED RECORDS TAB:

This tab is used to view are Service Request and Work orders that are related to this particular Work order.

ACTUALS TAB:

This tab is used to view Actual cost related to this Work order. It displays actuals Child (ren), Task(s), Labor, Materials, Service, and Tools.

SAFETY PLAN TAB:

This tab is used to view all Safety Plans related to this Work order, whether there are Hazard or Precautions. You can also view Lock Out/Tag Out related issues.

THE WORK ORDER

LOG TAB:

This tab is used to view the Work and Communication Logs.

FAILURE REPORTING TAB:

This tab is used to view Failure Details and Failure Codes.

SPECIFICATIONS TAB:

This tab is used to view classification for an object, you can organize related parent and child objects in a hierarchical structure, similar to a file directory. You can then drill up and down through the hierarchy to view associated items. Create and manage classifications in the Classifications application.

eCONTRACT TAB:

This tab contain all the eContract information, Contract#, Delivery Order#, Modification#, Contractor, Phone, E-mail, Award Amount, Contract Official, Planned Award Date, Actual Award Date, Planned Completion Date, Cumulative Cost Amount, Legal CCD, and BOD. You can also link into eContract via this tab.

FUND TAB:

This tab is used to view the status of the GL Account.

SERVICE ADDRESS TAB:

This tab is used to view the Service Address of the Work order.

MAP TAB:

(NOT ACTIVE) This tab is used to view locations on a map.

APPROVING THE WORKORDER

Before you start working on a Work order, it should be ‘Approve’. To approve a Work order go to the ‘Common Actions’ then ‘Approve Work Order’.

The ‘Change Status’ box appears and in the ‘New Status’ box the work ‘Approved’, click ‘OK’, your Work order status changes from ‘WAPPR’ to ‘APPR’.

The Work order can be assigned to a ‘Lead’ and work can be started.

ENTERING LABOR AND MATERIAL

Labor and Material for in-house workforce will be imported on the Work order; material will be pulled from the Purchase Order module and Labor from the SLACADA interface.

After approving the Work order, you can add labor and/or material to the work order. Once Labor and/or Material is added to a work order it cannot be cancelled.

This step is for CONTRACTORS ONLY:

Go to the ‘Actuals’ tab.

Enter ‘Labor’: Click on the Labor tab; then click on ‘New Row’.

Enter all the required fields in Red.

1. Labor – The employee labor code or the contract labor record. MIL_CTR1 (mandatory)

2. Rate – The per hour rate of the employee performing the work. $0 (mandatory)

3. Craft – The craft of the employee performing the work. (mandatory)

4. Regular Hours – Number of hours to complete job. (mandatory)

5. Start Date – The date of the work. (System defaults to current date – this can be modified). (mandatory)

6. Everything else is automatically entered by Maximo. Once you save the record, you cannot make any changes. (Check for accuracy before saving.) Save the record.

To enter ‘Material’: Click on the Material tab and then click new row button Click on the ‘New Row’ button. (ASTERISKS ARE MANDATORY FIELDS)

Click on the ‘New Row’ button. (ASTERISKS ARE MANDATORY FIELDS)

a. Change the ‘Line type’ to ‘Material’

b. Type the work ‘MATERIAL’ in the open space next to ‘Item’.

c. Quantity leave as ‘1’

d. Unit Cost, enter the total cost of the material.

Once you save the record, you cannot make any changes. (Check for accuracy before saving.) Save the record.

COMPLETING THE WORK ORDER

When completing WORK ORDER, click LOG tab.

Then click NEW ROW.

From the NEW ROW tab, information can be added to the WORK ORDRER in the details section.

When the work has been finish, time has been charged to the Workorder, and it’s time to complete the workorder; you need to go to ‘Common Actions’, ‘Completed Work Order’

The ‘Change Status’ box pops up and the ‘New Status’ box has ‘Completed’. Click ‘OK’.

Process Completed.

How to create an asset The easiest way is to duplicate an existing asset. Type in a known asset that is the same category that you want to create then click enter. Then when asset show up, click on the asset

Then click on duplicate asset.

This is the screen you will see next. This is where you name the asset, give its location and installation date. When using MAXIMO, always use CAP’s. When naming assets in GTMO, it always starts with CUB-BUILDING NUMBER-ASSET TYPE- ASSET NUMBER. This is where you give a description of the asset. This box lets you put in additional comments also. An installation date is also required, if a date isn’t entered, it won’t let you save.

Scroll down father and this is where you add manufacture/ model and serial number. A replacement cost should be added also. You also need to change the PM program to P-KT.

Next you need to click location and scroll down on the right side of drop menu and click select value.

Then in the location box, type building number and click enter

Then click GUABAY-M207

It will now add the facility number

Now you need to save your new asset and the top of the screen will say the asset was saved.

Then you’ll want to change status and make sure it’s listed as operating

Then click the arrow and put it in operating status.

This was created using the MAXIMO TEST SITE! This asset will not show up in regular MAXIMO and was only used to show how to create an asset.

How to grade an asset. Start by clicking asset

Under the asset section, type in the asset number and click enter

Then click enter on asset number Then click on the enter meter reading tab on the left side of the screen

Then under new reading, click the magnifying glass

This is where you select the grade of the asset, click the value of the asset I selected A for the asset grade for demonstration as shown under new reading. Then click ok, your asset will have its new grade.

PROPERTY OF NAVFAC SE Page 39 of 39 image3.png image4.png image5.png image6.png image7.png image8.png image9.png image10.png image11.png image12.png image13.png image14.png image15.png image16.png image17.png image18.png image19.png image20.png image21.png image22.png image23.png image24.png image25.png image26.png image27.png image28.png image29.png image30.png image31.png image32.png image33.png image34.png image35.png image36.png image37.png image38.png image39.png image40.png image41.png image42.png image43.png image44.png image45.png image46.png image47.png image48.png image49.png image50.png image51.png image1.jpeg image2.png