MNMAINTPROGRAMMED - Programmed maintenance import
This import template allows inserting:
- Programmed maintenance data.
For the insertion of each one of these items, the standard documented below must be followed.
Insert
| Column | Required | Type | Precision | Description |
|---|---|---|---|---|
| OIDINTERFACE | X | TEXT | 32 | Sequential code - Identifies an item to be imported into SoftExpert Suite. |
| FGIMPORT | X | NUMERIC | 2 | Import status: 1 - New; 2 - In progress; 3 - Finished; 4 - Error. |
| CDISOSYSTEM | X | NUMERIC | 10 | Code of the system for which the integration will be performed: 126 - Code of the SoftExpert Maintenance component. |
| FGOPTION | X | NUMERIC | 2 | Code of the operation to be performed: 4 - Create programmed maintenance. |
| NMFIELD01 | TEXT | 255 | Activity ID # (generated automatically if not entered). | |
| NMFIELD02 | X | TEXT | 255 | Standard activity ID # |
| NMFIELD03 | X | TEXT | 255 | Asset ID #. Note: For multiple assets, insert the identifiers separated by ';'. (E.g.: ASSET1;ASSET2) |
| NMFIELD04 | TEXT | 255 | Activity step: 1 - Planning; 2 - Execution; Note: Considered as 1 by default | |
| NMFIELD05 | X¹ | TEXT | 255 | Planned start date. The expected format must be YYYY-MM-DD (Year-Month-Day).If this is an import via spreadsheet, format the cell as text; otherwise, the import will not be successful. |
| NMFIELD06 | X¹ | TEXT | 255 | Planned start time |
| NMFIELD07 | X¹ | TEXT | 255 | Planned end date. The expected format must be YYYY-MM-DD (Year-Month-Day).If this is an import via spreadsheet, format the cell as text; otherwise, the import will not be successful. |
| NMFIELD08 | X¹ | TEXT | 255 | Planned end time |
| NMFIELD09 | X² | TEXT | 255 | Execution start date. The expected format must be YYYY-MM-DD (Year-Month-Day).If this is an import via spreadsheet, format the cell as text; otherwise, the import will not be successful. |
| NMFIELD10 | X² | TEXT | 255 | Execution start time |
| NMFIELD11 | X² | TEXT | 255 | Actual percentage (%) |
| NMFIELD12 | X³ | TEXT | 255 | Service center ID # |
| NMFIELD13 | X³ | TEXT | 255 | Technician ID # |
| NMFIELD14 | X⁵ | TEXT | 255 | Evaluation method ID # |
| NMFIELD15 | TEXT | 255 | ID # of the process to be associated with the activity. For workflow only. | |
| NMFIELD16 | TEXT | 255 | Process automation type: 1 - Workflow. | |
| DSFIELD01 | X⁴ | TEXT | 4000 | Example:identifier_of_attribute1=value_of_attribute1; identifier_of_attribute2=value_of_attribute2; identifier_of_attribute3=value_of_attribute3.Example with a multivalued attribute: identifier_of_attribute1=value1_of_attribute1, value2_of_attribute1, value3_of_attibute1Note: For attributes with a numeric value, the decimal place separator must be ".". For date fields, the value must have the “Y-M-D” (Year-Month-Day) format. |
| DSFIELD02 | X⁶ | TEXT | 4000 | For quantitative method: ▪ For list of values: [criterion 1 id]=[result 1 id]; [criterion 2 id]=[result 2 id]▪ For indeterminate value: [criterion 1 id]=[value 1]; [criterion 2 id]=[value2] ▪ Mixing: [criterion 1 id]=[result 1 id]; [criterion 2 id]=[value 2]▪ For simple listing method: ▪ [result id] |
info
Note:
- X¹ - Required if the “Activity step” field is 1
- X² - Required if the “Activity step” step is 2
- X² - Required if it has not been entered in the standard activity.
- X⁴ - Required if the standard activity has mandatory attribute
- X² - Required if the DSFIELD02 field is completed.
- X² - Required if the NMFIELD14 field is completed.