J-0200000-09 Service Provider Information (JAX).xlsx
XLSX spreadsheet 37 KB Posted
- Attached to
- Base Operations Support (BOS) Services at Naval Air Station (NAS) Jacksonville, FL and Outlying Areas
- Solicitation number
- N6945026R0007
About this file
This file is a Service Provider Information Interface document (Version 3) for the Naval Facilities Engineering Command (NAVFAC) MAXIMO work order system, detailing specific data field requirements for contractors submitting maintenance and work order information. The document provides a comprehensive 42-column template specifying mandatory and optional fields for work order submissions, including critical data points such as work type, description, location, asset number, target dates, labor hours, costs, status, and utility outage reporting. Key technical requirements include precise formatting (pipe-delimited .txt file), mandatory crosswalked field values, specific date formats, and contract-specific guidelines for populating fields like work center (JAX_CTR1), GL account, and remarks documentation.
The interface is specifically designed for the Base Operations Support (BOS) Services contract at Naval Air Station Jacksonville (Solicitation N6945026R0007), which covers facility management, utilities management, transportation, and environmental services. Contractors must adhere to strict data entry protocols, with fields like Service Provider Reference Code, Asset Number, and Work Order Number being critically important for system integration. The document emphasizes that asset numbers must exist in NAVFAC MAXIMO before submission, and provides detailed instructions on populating fields for different work types (preventive maintenance, project repairs, emergency maintenance) with specific requirements for status changes, cost tracking, and comprehensive work order documentation.
View the file
Other files
Show 40 more
50 files listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- 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-XX
SERVICE PROVIDER 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-XX
SERVICE PROVIDER INFORMATION
| Interface: Service Provider | |||
| VERSION #: v3 | |||
| Current as of: 3 December 2015 | |||
| Service Provider (BOSC1) is a pipe delimited file. | |||
| Position | Name | Length | |
| Limit | Data Format Note | Field Definition | Content Notes |
| NAVFAC |
MAXIMO_FIELD
(WORKORDER.)
| 1 | Approved Date | 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. | will default when upload if left blank | APPROVEDDATE | |||
| 2 | Work Type | 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. | PM is used for all scheduled work | |||||
| PROJECT for IMP repairs | WORKTYPE | |||||
| 3 | Service Provider Reference Code | 10 | Contractors internal work order tracking number. Will update Record if Value is found in Maximo otherwise new record (Work order) will be created. | * will delete if left blank when a work order is updated or completed. | SERVPRVREFCODE | |
| 4 | Description | 150 | Describes the work order. | |||
| If the Description is null, in the inbound file, then this field is defaulted to CROSSWALK value. | 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 descriptionInclude PM job plan and frequency.
| ie QUARTERLY PM JOB PLAN 1234. Or describe work performed ie Replace AHU fan motor and belt. | DESCRIPTION | ||||||
| 5 | Location | 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. | * Location is not required if the record has an asset #. Most records originating from the contractor system would be for maintenance on an asset # so this field can be left blank. If populated, the location must exist in NAVFAC MAXIMO or the record will be rejected. | LOCATION | |||||
| 6 | Reported By | 62 | Must match Value List in Maximo | Identifies the person reporting the work order. | Leave blank on flat file; auto-populates by direct entry. | REPORTEDBY | |
| 7 | Master System | N/A | Not used | Will pull from asset number. | N/A | ||
| 8 | Status | 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 | STATUS | ||||
| 9 | Status Date | 10 | MM/DD/YYYY hh:mm:ss | Leave blank on flat file; auto-populates by direct entry. | STATUSDATE | ||
| 10 | Priority | 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. | Leave blank on flat file unless local direction is provided | WOPRIORITY | ||||
| 11 | Actual Start | 10 | MM/DD/YYYY hh:mm:ss | Format is important | ACTSTART | ||
| 12 | Actual Finish | 10 | MM/DD/YYYY hh:mm:ss | Format is important | ACTFINISH | ||
| 13 | Supervisor | 30 | Must match Value List in Maximo | Leave blank; if used, must match a MAXIMO user | SUPERVISOR | ||
| 14 | Labor Hours(Actual) | 8 | Number (2 decimal places) | required to change status to COMP | ACTLABHRS |
15 Labor Cost(Actual) 10 Number (2 decimal places) required to change status to COMP ACTLABCOST
16 Material Cost(Actual) 10 Number (2 decimal places) required to change status to COMP ACTMATCOST
| 17 | Duration | 8 | Number (2 decimal places) | Estimated remaining number of hours needed to complete the work. | May be left blank | ESTDUR |
| 18 | Asset | 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. | The asset number used must exist in NAVFAC MAXIMO prior to submission, or the record will be rejected. | ASSETNUM |
| 19 | Target Finish | 10 | MM/DD/YYYY hh:mm:ss | For contractor scheduled work Target Finish is calculated using the Frequency of Service in J-0200000-01. |
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. | Required to create the work order | TARGCOMPDATE | |||
| 20 | Target Start | 10 | MM/DD/YYYY hh:mm:ss | For contractor scheduled work Target Start is calculated using the Frequency of Service in J-0200000-01. |
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. | Required to create the work order. | TARGSTARTDATE | |||||
| 21 | Reported Date | 10 | MM/DD/YYYY hh:mm:ss | Leave blank on flat file; auto-populates by direct entry. | REPORTDATE | ||
| 22 | Lead | 30 | Must match Value List in Maximo | Lead person responsible for the work. | Leave blank; if used, must match a MAXIMO user | LEAD | |
| 23 | Scheduled Start | 10 | MM/DD/YYYY hh:mm:ss | Scheduled start should be between the target start and target completion date | Required if status change to inprogress or approved | SCHEDSTART | |
| 24 | Scheduled Finish | 10 | MM/DD/YYYY hh:mm:ss | Scheduled finish should be between the target start and target completion date | Required if status change to inprogress or approved | SCHEDFINISH | |
| 25 | Modified Date | 10 | LEAVE BLANK | Leave blank/Do Not Use | Leave blank/Do Not Use | CHANGEDATE | |
| 26 | Modified By | 30 | LEAVE BLANK | Leave blank/Do Not Use | Leave blank/Do Not Use | CHANGEBY | |
| 27 | N/A | 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 | 1 | Yes or No | Use "N" or leave blank | ISTASK | ||
| 29 | N/A | 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 | 10 | Must match Value List in Maximo | Used in updating record status on existing records. | Not required if the record has a Service Provider Reference Code, otherwise must match the MAXIMO work order | WONUM | |
| 31 | Detail Location | 250 | Detail location should be between the target start and target completion date | leave blank; will pull from asset number | DETAILLOC | ||
| 32 | CLIN | 30 | Contract Line Item Number | Value list in ELINs Tab | CLIN | ||
| 33 | Customer Ref Code | 8 | Must match Value List in Maximo | Leave blank unless Requirements provides reference list. | May be blank; if used, must match a code in MAXIMO | CUSTOMERCODE | |
| 34 | Sub Work Type | 15 | (Cross-walked field). | ||||
| Must match Crosswalk | Defaulted field based on the value of worktype | FACILITIES for scheduled work in Annex 1502000 |
UTILITIES for scheduled work in any Annex 16 sub-annex
| FPCT for IMP repairs under the limit of liability | SUBWORKTYPE | |||||
| 35 | Work Center | 8 | Must match Value List in Maximo | Work center should be between the target start and target completion date | For this contract use JAX_CTR1 |
| Do not leave blank or will assign to CHR_CTR. | PERSONGROUP | ||||||
| 36 | GL Account | 27 | Must be a complete GL account or will imported as NULL | Only full GL Account, including delimiters, values can be imported. | Use "S.N69450.NX.TRACKNSTXXXXXXXX" for all work orders. changes every FY | GLACCOUNT | |
| 37 | Outage Type | 50 | ALN | Type of utility outage | May be blank. The “Outage Type” value must be a valid value available in the “OUTTYPE” domain. | OUTAGETYPE | |
| 38 | Outage Cause | 50 | ALN | Cause of utility outage | May be blank. The “Outage Cause” value must be a valid value available in the “OUTCAUSE” domain. | OUTAGEREASON | |
| 39 | Num of Bldgs Affected | 12 | Integer | Number of Building affected (whole number) | May be blank | NUMBLDSAFFECTED | |
| 40 | Outage Start Date | 10 | MM/DD/YYYY hh:mm:ss | Outage Start (Date/Time) | May be blank. The “Outage Start Date” value must be m valid value available in the “OUTDATE” domain. | OUTAGESTARTDATE | |
| 41 | Outage End Date | 10 | MM/DD/YYYY hh:mm:ss | Outage End (Date/Time) | May be blank. The “Outage End Date” value must be m valid value available in the “OUTDATE” domain. | OUTAGEENDDATE | |
| 42 | Remarks | 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 long descrption is limited to 1,000 characters.
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-XX | ||
| SERVICE PROVIDER 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 | Service Provider Reference Code | 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 | ||||||||||||||||||||||||||||||||||||||
| 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:
• File naming convention: boscextract_JAX1_YYYYMMDD.txt
• 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 41 PIPEs per row resulting in 42 columns.)
• If the column to the right of the last column is selected (the "42nd" column) this will provide the 42nd PIPE Actual Completion dates – Both Actual Start and Actual Finish completion dates are required when changing status to COMP workorder
• Asset number is required for work type PM and PROJECT. Asset number is not required for work type EMERGENCY, URGENT, ROUTINE
• Target dates – When one is provided, both Target Start and Target Finish must be entered.
File details come from the government source that posted it. Updated .