Convert the MP2 tasks.
MP2 tasks are a unique combination of the 15 character site field and the 20 character task field. Contrastingly,in HxGN EAM there is one 20-character PM schedule or standard work order field that does not use the HxGN EAM organization as part of the primary key. All MP2 tasks that have equipment will become PM schedules and all MP2 tasks that do not have equipment will become standard work orders. For example:
MP2 example
|
MP2 Site=GREENVILLE MP2 Task=3M-OILCHANGE |
AND |
MP2 Site=ATLANTA MP2 Task=3M-OILCHANGE |
In HxGN EAM you may only have one field that can have the same PM schedule value when converting the Task IDs from MP2. Here is an example:
GRE-3M-OILCHANGE
ATL-3M-OILCHANGE
The characters are both less than the 20 character maximum of HxGN EAM. In this example, the values of both fields were merged and separated by a '-'. If in your tasks list there are not any tasks and site combinations exceeding the 20 character maximum, you may still separate the values by a '-' and enter the full length of tasks IDs. Here is an example:
|
Prefix |
Field |
Start Position |
Length |
Suffix |
|---|---|---|---|---|
|
<blank> |
MP2 Site |
1 |
3 |
- |
|
<blank> |
MP2 Task |
1 |
16 |
This would guarantee field lengths covered at least the largest site/task combination and was still less than 30 characters. The system will cut off all data at the maximum length specified.
You may also select to only convert MP2 Tasks if you are certain no duplicate task ID exists in another site. If a duplicate Task exists, the second record will process as an error in the conversion process. This error can be corrected and reprocessed. Here is an example of converting Tasks only:
|
Prefix |
Field |
Start Position |
Length |
Suffix |
|---|---|---|---|---|
|
<blank> |
MP2 Task |
1 |
20 |