J-0200000-07 Work Order Information.xlsx
XLSX spreadsheet 39 KB Posted
- Attached to
- Multi-Function Support Services (MFSS) for Naval Air Station (NAS) Jacksonville, Florida Federal contract opportunity
- Solicitation number
- N6945024R0018
About this file
This document appears to be an interface specification for the submission of work order information from a service provider to the NAVFAC MAXIMO system. It provides detailed field definitions and formatting requirements for a pipe-delimited data file, including fields such as work type, customer reference number, location, status, priority, labor and material costs, and target/scheduled start and completion dates.
The related federal contract opportunity is a solicitation for Multi-Function Support Services at Naval Air Station (NAS) Jacksonville, Florida, including custodial, pest control, solid waste management, and grounds maintenance services. The contract will be a single award Facilities Support Indefinite-Quantity contract, with a base period of one year and four one-year option periods. The procurement is a competitive 8(a) set-aside, with award to be made to the offeror providing the best value to the government based on technical, past performance, and price factors. A site visit is scheduled for April 30, 2024, and the Government Pre-Award Inquiry deadline is May 7, 2024.
View the file
Other files for this federal contract opportunity
Show all 45
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
1-Service Provider Info
ATTACHMENT J-0200000-07
WORK ORDER INFORMATION
| Interface: Service Provider | |
| VERSION #: | v3 |
| Current as of: | 3 December 2015 |
| Version History |
| v1 - Updated to reflect current interface in MAXIMO |
| v2 - Update to reflect addition of Utility Outage Reporting information & Support GL Account Import |
| v3 - Update to reflect addition of additional remarks field.[In sync with NITC R2 Interface Document] |
| TABS | |
| 1-Service Provider Info | This Sheet |
| 2-Service Provider Field List | Service Provider Template Data Format Information |
| 3-Service Provider - Template | Sample Excel Format |
2-Service Provider Field List
ATTACHMENT J-0200000-07
WORK ORDER INFORMATION
| Interface: Service Provider | ||||
| VERSION #: v3 | ||||
| Current as of: 3 December 2015 | ||||
| Service Provider (BOSC1) is a pipe delimited file. | ||||
| Position | Name | Required | Length | |
| Limit | Data Format Note | Field Definition | Content Notes | |
| <<Note to Spec Writer: Only the "Content Notes" field should be modified on this TAB, Delete this text box prior to publising, no other changes to this document should be made.>> | NAVFAC |
MAXIMO_FIELD
(WORKORDER.)
| 1 | Approved Date | N | 10 | MM/DD/YYYY hh:mm:ss | The Date on which the Work Order was last approved. If the file contains an Approved Date, then this date will be pulled over to the record. | |
| If the Approved Date in the file is null, then the Reported Date plus one minute will be displayed in the record. | APPROVEDDATE | |||||
| 2 | Work Type | Y | 15 |
Must match Value List in Maximo.
| (Cross-walked field.). Must match Crosswalk | Identifies the work order's type. |
| Example types are: preventive maintenance, corrective maintenance, emergency maintenance, capital project, and event report. | Value list in REFERENCE SPREADSHEET -or- |
For this contract the following are valid work types:
| CLIN XXXXXX use "XXXX" | WORKTYPE | |||||||
| 3 | Customer Reference Number | Y | 10 | Contractors internal work order tracking number. Will update Record if Value is found in Maximo otherwise new record (Work order) will be created. | SERVPRVREFCODE | |||
| 4 | Description | Y | 150 | Describes the work order. | ||||
| If the Description is null, in the inbound file, then this field is defaulted to CROSSWALK value. | DESCRIPTION | |||||||
| 5 | Location | Y | 30 | Must match Value List in Maximo | Identifies the work order's location. This is not necessarily the asset's location, however, if an asset is entered, its location will default here. | |||
| - If the Location is null, in the inbound file, then this field is defaulted to the site's base location. | Value list in REFERENCE SPREADSHEET | LOCATION | ||||||
| 6 | Reported By | N | 62 | Must match Value List in Maximo | Identifies the person reporting the work order. | Value list in REFERENCE SPREADSHEET -or- |
For this contract:
| - use the following identifier "XXXX" | REPORTEDBY | |||||
| 7 | Master System | N | N/A | Not used | N/A | |
| 8 | Status | Y | 16 | (Cross-walked field.) | ||
| Must match Crosswalk | Status of the work order, for example, in progress, waiting on material, waiting for approval, completed, or closed. | Value list in REFERENCE SPREADSHEET -or- |
For this contract:
| - use the following identifier "XXXX" | STATUS | ||||||
| 9 | Status Date | Y | 10 | MM/DD/YYYY hh:mm:ss | STATUSDATE | ||
| 10 | Priority | Y | 12 | (Cross-walked field.) | |||
| Must match Crosswalk | Identifies the importance of the work order, from 0-999, where 0 is the lowest priority and 999 is the highest. If the Priority is null, in the inbound file, then this field is defaulted. | Value list in REFERENCE SPREADSHEET | WOPRIORITY | ||||
| 11 | Actual Start | N | 10 | MM/DD/YYYY hh:mm:ss | ACTSTART | ||
| 12 | Actual Finish | N | 10 | MM/DD/YYYY hh:mm:ss | ACTFINISH | ||
| 13 | Supervisor | N | 30 | Must match Value List in Maximo | Value list in REFERENCE SPREADSHEET -or- |
For this contract:
| - use the following identifier "XXXX" | SUPERVISOR | |||||
| 14 | Labor Hours(Actual) | Y | 8 | Number (2 decimal places) | ACTLABHRS |
15 Labor Cost(Actual) Y 10 Number (2 decimal places) ACTLABCOST
16 Material Cost(Actual) Y 10 Number (2 decimal places) ACTMATCOST
| 17 | Duration | N | 8 | Number (2 decimal places) | Estimated remaining number of hours needed to complete the work. | ESTDUR | |
| 18 | Asset | N | 25 | Must match an existing ASSETNUM in Maximo | The asset number used must exist in NAVFAC MAXIMO prior to submission, or the record will be rejected. | Value list in REFERENCE SPREADSHEET |
| ASSETNUM | |||||
| 19 | Target Finish | N | 10 | MM/DD/YYYY hh:mm:ss | For contractor scheduled work Target Finish is calculated using the Frequency of Service in J-0200000-xx. |
For IMP system breakdowns the Target Finish is 2 days from the date the work was reported to the Contractor
| For E/U/R the Target Finish date is calculated from the date the work was reported to the Contractor. | TARGCOMPDATE | |||||
| 20 | Target Start | N | 10 | MM/DD/YYYY hh:mm:ss | For contractor scheduled work Target Start is calculated using the Frequency of Service in J-0200000-xx. |
For IMP system breakdowns the Target Start is the date the work was reported to the Contractor
| For E/U/R the Target Start date is calculated from the date the work was reported to the Contractor. | TARGSTARTDATE | |||||||
| 21 | Reported Date | Y | 10 | MM/DD/YYYY hh:mm:ss | REPORTDATE | |||
| 22 | Lead | N | 30 | Must match Value List in Maximo | Lead person responsible for the work. | Value list in REFERENCE SPREADSHEET | LEAD | |
| 23 | Scheduled Start | N | 10 | MM/DD/YYYY hh:mm:ss | Scheduled start should be between the target start and target completion date | SCHEDSTART | ||
| 24 | Scheduled Finish | N | 10 | MM/DD/YYYY hh:mm:ss | Scheduled finish should be between the target start and target completion date | SCHEDFINISH | ||
| 25 | Modified Date | Y | 10 | LEAVE BLANK | Leave blank/Do Not Use | Leave blank/Do Not Use | CHANGEDATE | |
| 26 | Modified By | Y | 30 | LEAVE BLANK | Leave blank/Do Not Use | Leave blank/Do Not Use | CHANGEBY | |
| 27 | N/A | N | 4 | MM/DD/YYYY hh:mm:ss | N a should be between the target start and target completion date | Placeholder for WORKORDER.PMNEXTDUEDATE. Value is not presently imported. | PMNEXTDUEDATE | |
| 28 | N/A | N | 1 | Yes or No | ISTASK | |||
| 29 | N/A | N | 10 | Length Limit: 250 | Must exist in NAVFAC MAXIMO prior to submission or the record will be rejected. | Must exist in NAVFAC MAXIMO prior to submission or the record will be rejected. | PARENT | |
| 30 | Work Order | N | 10 | Must match Value List in Maximo | Used in updating record status on existing records. | WONUM | ||
| 31 | Detail Location | N | 250 | Detail location should be between the target start and target completion date | DETAILLOC | |||
| 32 | CLIN | N | 30 | Contract Line Item Number | CLIN | |||
| 33 | Customer Ref Code | N | 8 | Must match Value List in Maximo | Customer code should be between the target start and target completion date | Value list in REFERENCE SPREADSHEET | CUSTOMERCODE | |
| 34 | Sub Work Type | N | 15 | (Cross-walked field). | ||||
| Must match Crosswalk | Defaulted field based on the value of worktype | SUBWORKTYPE | ||||||
| 35 | Work Center | N | 8 | Must match Value List in Maximo | Work center should be between the target start and target completion date | Value list in REFERENCE SPREADSHEET -or- |
For this contract:
| - use the following identifier "XXXX" | PERSONGROUP | |||||||
| 36 | GL Account | Y | 27 | Must be a complete GL account or will imported as NULL | Only full GL Account, including delimiters, values can be imported. | Format is “X.XXXXXXXX.XX.XXXXXXXXXXXX” (Example: T.N4425500.ZZ.ZZZZBOSCACCT). Only full GL Account, including delimiters, values can be imported. | GLACCOUNT | |
| 37 | Outage Type | N | 50 | ALN | Type of utility outage | The “Outage Type” value must be a valid value available in the “OUTTYPE” domain. | OUTAGETYPE | |
| 38 | Outage Cause | N | 50 | ALN | Cause of utility outage | The “Outage Cause” value must be a valid value available in the “OUTCAUSE” domain. | OUTAGEREASON | |
| 39 | Num of Bldgs Affected | N | 12 | Integer | Number of Building affected (whole number) | NUMBLDSAFFECTED | ||
| 40 | Outage Start Date | N | 10 | MM/DD/YYYY hh:mm:ss | Outage Start (Date/Time) | OUTAGESTARTDATE | ||
| 41 | Outage End Date | N | 10 | MM/DD/YYYY hh:mm:ss | Outage End (Date/Time) | OUTAGEENDDATE | ||
| 42 | Remarks | N | 150 | ALN | Additional remarks. At each submission the remarks are appended to the END of previous remarks. /// Use and Style is a CONTRACT SPECIFIC USE /// | Each remark submission is restricted to 150 characters, and the DATE will be appended in Maximo prior saving. This can be used (local/contract specific guidance) to provide a chronology to the work order. Resulting format would be: DATE1 - Remark1; DATE2 - Remark2; etc. |
The total field length is restricted to <2000 characters - or a maximum of 11-12 remarks on a single Work Order.
The following information shall be provided if it is relevant:
1. Name and phone number of all Government personnel with whom the work was coordinated or provided clarificaiton to the technician, and date KO was notified of any problems scheduling the work or accessing the location.
2. A narrative of work performed and technicians observations.
3. The estimated cost and date notification of work exceeding LOL was submitted to the KO. LONGDESCRIPTION
3-Service Provider-Template
| ATTACHMENT J-0200000-07 | ||
| WORK ORDER INFORMATION | ATTACHMENT J-0200000-XX |
SERVICE PROVIDER INFORMATION
| Interface: Service Provider |
| VERSION #: v3 |
| Current as of: 3 December 2015 |
| Position | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | |
| Name | Approved Date | Work Type | Customer Reference Number | Description | Location | Reported By | Master System | Status | Status Date | Priority | Actual Start | Actual Finish | Supervisor | Labor Hours | |||||||||||||||||||||||||||||
| (Actual) | Labor Cost | ||||||||||||||||||||||||||||||||||||||||||
| (Actual) | Material Cost | ||||||||||||||||||||||||||||||||||||||||||
| (Actual) | Duration | Asset | Target Finish | Target Start | Reported Date | Lead | Scheduled Start | Scheduled Finish | Modified Date | Modified By | PMNEXTDUEDATE | Is Task? | Parent WO | Work Order | Detail Location | CLIN | Customer Ref Code | Sub Work Type | Work Center | GL Account | Outage Type | Outage Cause | Num of Bldgs Affected | Outage Start Date | Outage End Date | Remarks | |||||||||||||||||
| Validation tool | Y | Y | Y | Y | Y | ||||||||||||||||||||||||||||||||||||||
| will default when upload | *Use PM for scheduled maint and PROJECT for IMP repairs | *Will delete if left blank | will create a default entry if left blank on update |
"Entered by SP FlatFile BOSC interface. No description provided."
Include contractor job plan number in the description * Location is not required if you have an asset # will default when upload will pull from asset will default on upload format #.## will not show in front end of MAXIMO but does show in TABLEAU use 0.00 for fixed price work will not show in front end of MAXIMO but does show in TABLEAU format #.##
| will not show in front end of MAXIMO but does show in TABLEAU | must be included with all records or will reject at validaton. | will default when upload | *req if status inprog or approv | * req if status inprog or approv | will default when upload | will default when upload | Use N | if bogus work order is provided, the record will pass validation and error during upload. | *use FACILITY or UTILITY for planned maintenance and FPCT for repairs under the LOL | will assign to CHR_CTR if blank | *work notes | ||||||||||||||||||||||||||||||||
| REQUIRED TO CREATE WO | N | Y* | Y | Y | Y* | N | N | Y | N | N | N | N | N | N | N | N | N | Y | Y | Y | N | N | N | N | N | N | N | N | N | N | N | Y | N | Y* | Y | Y | N | N | N | N | N | N* | |
| REQUIRED TO UPDATE WO | N | N | Y* | Y | N | N | N | N | N | N | N | N | N | N | N | N | N | Y | N | N | N | N | Y* | Y* | N | N | N | N | N | N | N | N | N | N | Y | N | N | N | N | N | N | N* | |
| REQUIRED TO COMP WO | N | N | Y* | Y | N | N | N | Y | N | N | Y | Y | N | Y* | Y* | Y* | N | Y | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | Y | N | N | N | N | N | N | Y* |
NOTES:
• ONLY POSITION/COLUMN 1-42, and rows containing data should be be included in the FLAT-FILE SUBMISSION;
• Pipe Delimited (.txt) - | (Pipe is at the end of the column. Must have 42 PIPEs per row.)
• If the column to the right of the last column is selected (the "43rd" column) this will provide the 42nd PIPE
File details come from the government source that posted it. Updated .