recurring equipment events - umoja...2017/08/10  · number and/or techidentno., functional...

1
Scenario: is covers the Equipment Maintenance & Physical Verification processes for a vehicle, i.e. a serialized equipment, while in use. Note: e Physical Verification process described below is the interim process until a Mobile Solution is implemented in 2018. Physical Verification Recurring Equipment Events Equipment Maintenance (Ad-Hoc) GENERATE LIST FOR PHYSICAL VERIFICATION MAINTENANCE REQUESTED PLAN MAINTENANCE UPDATE EQUIPMENT STATUS REVIEW & TECHNICALLY COMPLETE ORDER SERVICE ORDER APPROVAL/RELEASE UPDATE EQUIPMENT STATUS CONDUCT PHYSICAL VERIFICATION LOAD VERIFICATION RESULTS TO UMOJA RESOLVE ANY DISCREPANCIES BI REPORTS & ANALYSIS A Umoja report is generated for equipment that requires Physical Verification. Information includes: the serial number and/or TechIdentNo., Functional Location, equipment status, and person responsible. A Notification is created by the requesting section for maintenance on their vehicle. e Notification is approved by the Section Chief. Planners from the Transport Section receive the Notification, analyze the requirement, and create a Service Order. e Service Order specifies any spare parts that are needed, assigns tasks and estimated time for completion, as well as maintenance scheduling. Once services have been provided, the service order will be marked as Technically Completed. e Notification should be updated and closed. e Service Order must be approved and released by the Section Chief (or designate) before work can begin. e release of the Service Order creates reservations for spare parts in inventory, and also creates shopping carts for spare parts not available in inventory. e Master Data Maintainer updates the equipment status in the equipment record that the repair is under way. e Master Data Maintainer updates the equipment status to show that it is currently in use. e information from the list is manually verified and entered into a spreadsheet. Details entered also include: the date, user performing the verification, and discrepancy type. Discrepancies are reviewed and resolved. Any changes in discrepancy type will be logged in Umoja for reporting purposes. e spreadsheet with the Physical Verification results are migrated into Umoja using a Mass Upload Tool. Physical Verification Key Performance Indicators (KPI’s) can be produced using standard BI reports. Physical Verification for all serialized equipment with the serialization profile, UN-01, must be performed annually. e Umoja material master also has a separate serialization profile, UN-05, that generates serial numbers and equipment master records for operational tracking, but Physical Verification is not required. e Notification specifies the Planner Group, which determines the Technical Section planner who receives the Notification. For Cost Recovery scenarios, the Service Order must be approved by the Certifying Officer of the paying entity. 1 2 2 3 3 4 4 5 5 1 6 is is an example of an ad-hoc (unscheduled) maintenance process; it is also applicable for entities not using Preventative Maintenance functionalities in Umoja.

Upload: others

Post on 02-Mar-2021

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Recurring Equipment Events - UMOJA...2017/08/10  · number and/or TechIdentNo., Functional Location, equipment status, and person responsible. A Notification is created by the requesting

Scenario: This covers the Equipment Maintenance & Physical Verification processes for a vehicle, i.e. a serialized equipment, while in use.Note: The Physical Verification process described below is the interim process until a Mobile Solution is implemented in 2018.

Physical Verification

Recurring Equipment Events

Equipment Maintenance (Ad-Hoc)

GENERATE LIST FOR PHYSICAL VERIFICATION

MAINTENANCEREQUESTED

PLAN MAINTENANCE

UPDATE EQUIPMENT STATUS

REVIEW & TECHNICALLY COMPLETE ORDER

SERVICE ORDERAPPROVAL/RELEASE

UPDATEEQUIPMENT STATUS

CONDUCT PHYSICAL VERIFICATION

LOAD VERIFICATIONRESULTS TO UMOJA

RESOLVE ANY DISCREPANCIES

BI REPORTS &ANALYSIS

A Umoja report is generated for equipment that requires Physical Verification. Information includes: the serial number and/or TechIdentNo., Functional Location, equipment status, and person responsible.

A Notification is created by the requesting section for maintenance on their vehicle. The Notification is approved by the Section Chief.

Planners from the Transport Section receive the Notification, analyze the requirement, and create a Service Order. The Service Order specifies any spare parts that are needed, assigns tasks and estimated time for completion, as well as maintenance scheduling.

Once services have been provided, the service order will be marked as Technically Completed. The Notification should be updated and closed.

The Service Order must be approved and released by the Section Chief (or designate) before work can begin. The release of the Service Order creates reservations for spare parts in inventory, and also creates shopping carts for spare parts not available in inventory.

The Master Data Maintainer updates the equipment status in the equipment record that the repair is under way.

The Master Data Maintainer updates the equipment status to show that it is currently in use.

The information from the list is manually verified and entered into a spreadsheet. Details entered also include: the date, user performing the verification, and discrepancy type.

Discrepancies are reviewed and resolved. Any changes in discrepancy type will be logged in Umoja for reporting purposes.

The spreadsheet with the Physical Verification results are migrated into Umoja using a Mass Upload Tool.

Physical Verification Key Performance Indicators (KPI’s) can be produced using standard BI reports.

Physical Verification for all serialized equipment with the serialization profile, UN-01, must be performed annually. The Umoja material master also has a separate serialization profile, UN-05, that generates serial numbers and equipment master records for operational tracking, but Physical Verification is not required.

The Notification specifies the Planner Group, which determines the Technical Section planner who receives the Notification.

For Cost Recovery scenarios, the Service Order must be approved by the Certifying Officer of the paying entity.

1 2

2

3

3

4

4

5

51 6

This is an example of an ad-hoc (unscheduled) maintenance process; it is also applicable for entities not using Preventative Maintenance functionalities in Umoja.