J-1601000-04 Utility Map Attributes.xlsx
XLSX spreadsheet 59 KB Posted
- Solicitation number
- N6247025R0020
About this file
This document is a detailed technical specification file for a utility map attributes data interface, specifically focused on file transfer and data mapping processes for inserting or updating Facilities/UEM Assets records. The file describes a complex inbound data transfer process involving pipe-delimited text files, with specific protocols for file handling, conversion, and error management across multiple server directories. Key technical details include automatic file placement in specific interface folders, conversion processes managed by cron tasks, and a precise data mapping specification that defines required fields such as Asset Number, Site ID, Class Structure ID, and various attribute specifications with validation rules.
The interface is designed to process inserts and updates into an ASSETSPEC table, with strict validation requirements for data fields including domain value checks and specific rules for numeric and alphanumeric value population. Error handling is comprehensive, with provisions for creating .processed, .error, and .log files to track successful and failed record transfers. The specification includes sample data demonstrating the expected file format, with guidelines specifying that pipe-delimited files should not start with a pipe character and must end with a final pipe delimiter. While the file appears to be a technical specification for a data transfer interface, it is not directly related to the referenced federal contract opportunity for Base Operations Support Services at Naval Air Station Sigonella in Sicily, Italy.
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
File Transfer
| J-1601000-04_Utlity Map Attributes | |
| Interface: | Specification File |
| File Transfer | |
| Current as of April 4, 2012 |
Purpose: Insert or update Facilities/UEM Assets records with specifications
Type: Inbound
| Arctic OEM Job: TBD |
| Frequency: TBD |
Cron Task: ConvertFileImport
Cron Task Instance: SpecificationFile_<SITEID>
| File Format: Pipe Delimited (.txt) |
| File Transfer Process: |
1. File is received from FEC and automatically placed in the site-specific SpecificationFile interface folder (<server> /wsbin01/app/integration/assetfile/<SITEID>) with a Permission Mode value of 640. Note: When manually copying an interface file to its corresponding site-specific folder, the Permission Mode value needs to be set to 644.
2. When picked up by the SpecificationFile_<SITEID> Cron it is converted into a pipe delimited (.txt) file. The new .txt file is placed in the server's /wsbin01/app/integration/Global/PipedFiles/ folder.
3. Once the .txt file is created the string ".processed" is appended to the original file located in the server's /wsbin01/app/integration/assetfile/<SITEID> folder.
4. The Cron Task Instance Specification Interface (under Cron Task "ConvertFileImport") will process the newly created .txt file. The .processed file is placed in the server's /wsbin01/app/integration/global/PipeFiles/backup folder when done.
| Error Handling: | Yes - error log and log file both created when a bad record is found |
| Any other kind of error handling (such as Message Reprocessing, other file mentioned in the Business Logic tab, et al? |
J-1601000-05_Utility Map Attributes N62470-17-D-4012 &KFF0000A0051 19-Nov-2021
Data Mapping
| Interface: Asset File |
| Data Mapping |
| Current as of February 28, 2012 |
| Design ID: |
| Requirement ID: |
| Site Specific: Yes |
| Cron Task: ConvertFileForImport |
| Cron Task Instance: assetspecfile_<SITEID> |
| Type: Inbound |
| Source File Format: Pipe Delimited (.txt) |
| Converted File Format: N/A |
Note: All other TABLE.COLUMN contents and/or field values not listed below are NULL on insert.
| Source File and Source Code | |||||||||||||||||||
| Name | Position | Length | Start | Stop | Req'd | Notes | Maximo 7 | ||||||||||||
| Application | Title - Field Name | Tab | Table | Column | Type | Value | Validated against DOMAIN | Insert | Update | Populated By | Notes | Rqmt ID | HPQC | ||||||
| Asset | 1 | 25 | N/A | N/A | YES | Asset | Asset | Specification | ASSET | ASSETNUM | VARCHAR2(25) | NO | NO | ||||||
| siteid | 2 | 8 | N/A | N/A | YES | Asset | Asset | Specification | ASSET | SITEID | VARCHAR2(8) | NO | NO | ||||||
| CLASSSTRUCTUREID | 3 | 20 | N/A | N/A | YES | not shown on front end | N/A | N/A | N/A | ASSETSPEC | CLASSSTRUCTUREID | VARCHAR2(20) | NO | NO | |||||
| Attribute | 4 | 300 | N/A | N/A | YES | Asset | Attribute | Specification | ASSETSPEC | ASSETATTRID | VARCHAR2(300) | NO | NO | ||||||
| Numeric Value | 5 | 40 | N/A | N/A | NO | only one value can be pased Numeric or AlphaNumeric | Asset | Numeric Value | Specification | ASSETSPEC | NUMVALUE | NUMBER(30,10) | possibly | NO | YES | Interface | |||
| Alphanumeric | 6 | 254 | N/A | N/A | NO | only one value can be pased Numeric or AlphaNumeric | Asset | Alphanumeric | Specification | ASSETSPEC | ALNVALUE | VARCHAR2(254) | possibly | NO | YES | Interface | |||
| Unit of Measure | 7 | 8 | N/A | N/A | NO | must match domain | Asset | Unit of Measure | Specification | ASSETSPEC | MEASUREUNITID | VARCHAR2(8) | yes | NO | YES | Interface | |||
| Display Sequence | 8 | 10 | N/A | YES | Integer value | Asset Spec | N/A | N/A | ASSETSPEC | DISPLAYSEQUENCE | SMALLINT(10) | no | YES | YES | Interface | 8099 | |||
| Linear Asset Spec ID | 9 | 12 | N/A | YES | Integer value | Asset Spec | N/A | N/A | ASSETSPEC | LINEARASSETSPECID | INTEGER(12) | no | YES | YES | Interface | Should always be 0 unless client is using Linear | 8099 |
| Asset | Changed by | Asset | ASSET | CHANGEBY | Varchar(30) | userinterface | Interface |
| Asset | change date | ASSET | CHANGEDATE | Date | server date | Interface |
J-1601000-05_Utility Map Attributes N62470-17-D-4012 &KFF0000A0051
Business Logic
| Business Logic | ||
| Logic | Description | Additional Notes |
| Interface processes | Inserts and Updates into ASSETSPEC table (no modification of CLASSSPEC, i.e., don't touch templates) | |
| SITEID | Included in Source File | |
| Required Fields | ASSETNUM | Required fields not provided in the source file will be rejected via .error/.log ConvertFileForImport process |
| SITEID | ||
| CLASSSTRUCTUREID | ||
| ASSETATTRID | ||
| Validation | ASSETNUM + SITEID | |
| CLASSSTRUCTUREID | ||
| If the AssetNum + SiteID + Classification doesn't exist, then the interface will create the associated specification record. | Note: There must be an asset and classification populated before a specification is created. | |
| ALN and/or NUMERIC value depending on what is populated in the source file. These fields can be null individually; however, not both null. Not all attributes have domain lists for the Alphanumeric and Numeric Values; the MIF will validate the individual ALN or NUMERIC domain values and throw the rejects to MRP. | ||
| The value in ASSETATTRIBUTE.DATATYPE specifies if attribute can be updated with Alphanumeric value or Numeric value | ||
| VALUE UOM | ||
| ASSET.CHANGEBY populated by INTERFACE (not in the source) | ||
| ASSET.CHANGEDATE populated by server date (not in the source) | ||
| On UPDATE, data will be validated against domain lists when one exists for that data field; if data is not valid, record will not be updated and will be written to the error logs | ||
| If multiple attributes are to be updated on the same asset then a new record should be created for each attribute update | ||
| DISPLAYSEQUENCE will be created only for inserted records. It will grab the next sequence #. Updates will not affect this field. | ||
| Error Handling | If Successful, source file will be named .processed in the SOURCEDIRECTORY |
If Failed, .processed, .error and .log files will be created.
1) The .processed will contain all records that were successfully processed. Processed files shall be named with .datetime .processed extension.
2) The .error will contain the original transaction with the error.
3) The .log will contain the error message.
| Message Reprocessing | If the MBO cannot validate a value that comes in from the source (e.g. Invalid GL, Location etc.,) it will throw this error in Message Reprocessing. This is separate from the error handling that addresses issues with the original source file above. |
| Additional Requirements | Ignore Status and Change Date. Let the MIF construct these. |
| Business Logic | |
| Current as of Februrary 28, 2012 |
| Rqmt ID | Description | Comments - | Matt's comments |
| TBD | Flat file named Specification_FECID_DATETIME.txt shall be provided by the FEC in /assetfile/FECID on the Arctic server | ||
| TBD | File will be picked up and moved over to the Maximo Server (Adria) by OEM job created by NITC | ||
| TBD | Data should be in a pipe delimited file in the format specified in the Specification(F12)DataMapping tab (required fields, order, type, length) | See "Data Mapping" tab for list of required values. | |
| TBD | Any record missing a required data field shall be written to the error log named SpecificationFile_FECID_ErrorLog.txt | Shouldn't this really be just written to the .error and .log files we create in preprocessing with the ConvertFileForImport cron task? | |
| TBD | AssetNum, SiteId and Classstructureid must match for a record to be updated; on failure record should be written to error logs | So just to be clear, if this combination doesn't already exist in Maximo, we are not to create the Asset Specification record? We are just associating existing Asset Specifications with Asset records, right? | If the AssetNum + SiteID + Classification doesn't already exist, I create it. |
| TBD | Not all attributes have domain lists for the Alphanumeric and Numeric Values; must verify if domain list exists for that attribute; if one exists the data must be validated against the domain list | ||
| TBD | On update data will be validated against domain lists when one exists for that data field; if data is not valid, record will not be updated and will be written to the error logs | ||
| TBD | Any record failing domain validation shall be written to the error log named SpecificationFile_FECID_LogFile.txt | ||
| TBD | Any record written to the error log shall have a corresponding error message written in the log file with an explanation as to why the record failed validation | ||
| TBD | The error log file & log file shall be placed in xxxx directory on xxxx server for FEC review | ||
| TBD | Interface will create SpecificatoinFile_FECID_DateTime.txt file inserting additional required data fields updated by the system without frontend input. Those fields from the asset table are defined in the data mapping document under the Maximo 7 application portion | ||
| TBD | Innterface shall update the ASSETSPECHIST table shall be updated with data added to asset record | Mbo handles this | |
| TBD | The value in ASSETATTRIBUTE.DATATYPE specifies if attribute can be updated with Alphanumeric value or Numeric value | ||
| If multiple attributes are to be updated on the same asset then a new record should be created for each attribute update | |||
| TBD | Only one of the two values can be populated Alphanumeric or Numeric | ||
| TBD | If both are left blank should any exsitsing data be blanked out or should the record be rejected and written to error log? | Question for users | I am rejecting the record in this scenario and creating the .log/.error files |
| TBD | Processed files shall be named with .datetime .processed extension. |
J-1601000-05_Utility Map Attributes N62470-17-D-4012 &KFF0000A0051
Sample Data
| Sample Data |
| Current as of February 22, 2012 |
*Please do not include a | as the first character in the source and end the record with a final |
| 3-440-EPN-007|11001|1616|UAMETERDEVICEID||A1234|| |
| 3-440-EPN-007|11001|1616|AMRINDICATOR||No|| |
| 3-440-EPN-007|11001|1616|PTRATIO|36||BA| |
| INTTEST1|10401|1014|HP|250||CC| |
J-1601000-05_Utility Map Attributes N62470-17-D-4012 &KFF0000A0051
File details come from the government source that posted it. Updated .