The file's text, extracted by GovTribe without its formatting.
Sheet1
| | | | Mandatory | |
| | | Data | For Input | |
| Seq | DATA ELEMENT | Purpose | Size /Type | to JEDMICS | Notes |
| 1 | JMX_DocNumber | Document Number | 32 bytes / char | x | (13) | |
| 2 | JMX_DocCage | Commercial and Govn't Entries Reference | 5 bytes / char | x | (13) | |
| 3 | JMX_DocType | Document Type | 2 bytes / char | x | (4) (13) | |
| 4 | JMX_DocumentSize | Size of drawing (May Be A Through K and R except I) | 2 bytes / char | x | | |
| 5 | JMX_DocRevision | Document Revision | 2 bytes / char | x | (4) (6) (11) (13) | |
| 6 | JMX_DocumentRevDate | Document Revision Date | 18 bytes / char | | (7) (12) | |
| 7 | JMX_DocumentTitle | Document Title | 40 bytes / char | | | |
| 8 | JMX_SheetNumber | Sheet Number of Document | 12 bytes / char | x | | |
| 9 | JMX_NumberOfSheets | Number of Sheets for Document | 4 bytes / char | | (15) | |
| 10 | JMX_DocSheetRevision | Sheet Revision | 2 bytes / char | x | (4) (11) (13) | |
| 11 | JMX_FrameNumber | Frame Number | 4 bytes / char | x | | |
| 12 | JMX_NumberOfFrames | Number of Frames for Sheet | 4 bytes / char | x | | |
| 13 | JMX_FileType | Designator for the Data Format Type of File | 5 bytes / char | x | | |
| 14 | JMX_FileTypeFormat | Description of the Format of the File Type | 20 bytes / char | | (3) (10) | |
| 15 | JMX_FileTypeSrcFlavor | Description of the File Type Source Flavor | 20 bytes / char | | (3) (10) | |
| 16 | JMX_FileTypeDestFlavor | Description of the File Type Destination Flavor | 20 bytes / char | | (3) (10) | |
| 17 | JMX_FileTypeContent | Description of the File Type Content | 20 bytes / char | | (3) (10) | |
| 18 | JMX_FileTypeVersion | Description of the File Type Version | 14 bytes / char | x | (3) (10) | NEEDS TO BE MANDATORY |
| 19 | IDX_DfisSourceCage | CAGE Code of The Originator of The DFIS Data Set | 5 bytes / char | x | (3) | |
| 20 | IDX_FileName | File Name of Image File (without extension) | 8 bytes / char | x | (8) | |
| 21 | IDX_FileExtension | File Extension of Image File | 3 bytes / char | x | (8) | |
| 22 | IDX_FilePath | File Path Where Image File is Located | 242 bytes / char | x | (8) (9) | |
| 23 | IDX_MediaVolumeID | Media Volume ID of Media Where File is Located | 11 bytes / char | x | (8) | |
| 24 | IDX_MajorGroup | Major Group Designation Within Index | 20 bytes / char | | | |
| 25 | IDX_MinorGroup | Minor Group Designation Within Index | 8 bytes / char | | | |
| 26 | JMX_SecurityLevel | Security Level | 1 byte / char | x | | |
| 27 | JMX_Rights | Viewing Rights | 1 byte / char | x | "U" or "L" | |
| 28 | JMX_ForeignSecure | Indicates if Foreign Personnel May View the Drawing | 1 byte / char | x | "N" or "Y" | |
| 29 | JMX_Nuclear | Indicates if Drawing Contains Nuclear Equipment | 1 byte / char | x | "N" or "Y" | |
| 30 | JMX_Subsafe | Indicates if Critical Safety | 1 byte / char | x | "N" or "Y" | |
| 31 | JMX_AirType | Model/Device | 6 bytes / char | | | |
| 32 | JMX_Apl | Allowance Parts List | 35 bytes / char | | | |
| 33 | JMX_CadInfo | Computer Aided Design Reference | 2 bytes / char | | | |
| 34 | JMX_ControlCode | Activity Code Furnished by Procuring Activity | 2 btyes / char | | | |
| 35 | JMX_Hsc | Hierarchical Structure Code | 12 bytes / char | | | |
| 36 | JMX_Nsn | National Stock Number | 13 bytes / char | | | |
| 37 | JMX_Uic | Unit Identification Code | 5 bytes / char | | | |
| 38 | JMX_System | Associated Equipment/System Group | 32 bytes / char | | |
| 39 | JMX_Nomenclature | Name of Equipment Described in the Drawing | 20 bytes / char | | |
| 40 | JMX_ShipClass | Ship Classification | 4 bytes / char | | |
| 41 | JMX_ShipTypeHullNum | Ship Type/Hull Number Classification | 9 bytes / char | | |
| 42 | JMX_MasterLocation | Engineering Drawing Master Location | 30 bytes / char | | |
| 43 | JMX_OfflineLocation | Engineering Drawing Off-line Location | 80 bytes / char | | |
| 44 | JMX_ParentCage | CAGE of Parent Drawing | 5 bytes / char | | |
| 45 | JMX_ParentDocNumber | Drawing Number of Parent Drawing | 32 bytes / char | | |
| 46 | JMX_PartNumber | Identifies Associated Part Number With CAGE | 32 bytes / char | | |
| 47 | JMX_SubSheet | Further Identifies Sheet | 3 bytes / char | | |
| 48 | JMX_Succeeding | Drawing Number and CAGE of Superseding Drawing | 20 bytes / char | | |
| 49 | JMX_DistStmt | Distribution Statement | 2 bytes / char | | |
| 50 | JMX_AccDocType | Accompanying Document - Document Type | 2 bytes / char | x | (5) (13) |
| 51 | JMX_AccDocNumber | Accompanying Document - Document Number | 32 bytes / char | x | (5) (13) |
| 52 | JMX_AccDocCage | Accompanying Document - CAGE Code | 5 bytes / char | x | (5) (13) |
| 53 | JMX_AccDocRevision | Accompanying Document - Document Revision | 2 bytes / char | x | (4) (5) (13) |
| 54 | [Blank] | [This Field Reserved For Future Use] | 0 bytes / char | | (13) |
| 55 | [Blank] | [This Field Reserved For Future Use] | 0 bytes / char | | (13) |
| 56 | JMX_WeaponsSystemCode | Weapon System Code | 15 bytes / char | | |
| 57 | IDX_DfisVersion | Version of the DFIS Structure Implemented | 4 bytes / char | x | (14) |
| 58 | Record End | Indicate end of record CR/LF (Hex 0D0A) | 2 bytes | | |
| NOTES: |
| 1. The Data File Index Structure (DFIS) is a character delimited ASCII text file with one Image |
| Row Entry (Record) per image referencing a data file in a hierarchical directory structure. The |
| file and hierarchical directory structure naming convention is not pre-defined. Each Image Row |
| Entry contains a sequenced series of pre-defined standard Data Elements (Fields) separated by the |
| pipe bar character "|". Image Row Entries are separated by a Carriage Return/Line Feed (CR/LF). |
| There should be no blank lines, or lines that do not conform to an Image Row Entry description as |
| defined in the DFIS. |
| 2. The DFIS file format does not pre-define the size (width) of the Data Elements. Data Element |
| sizes defined indicate the maximum size allowed. Padding of Data Elements is not required (i.e. |
| Sheet 1 can be entered as "|1|" and does not require an entry of "|000000000001|". All entries in |
| Data Elements should be uppercase. Leading and trailing spaces within the Data Element are ignored |
| (i.e. "| 1 |" will be interpreted the same as "|1|". Null entries may represented by "||". |
| (3) DFIS Usage Only. These Data Elements are informational within the DFIS and are not used as |
| part of the input to a JEDMICS. |
| (4) Mandatory Data Element where "blank" is a valid entry. Null is not a valid entry (i.e. "| |" |
| is valid, "||" is invalid). "Blank" is not a valid entry for other Mandatory Data Elements. |
(5) Mandatory Data Element when Image Row Entry is an Accompanying Document.
| (6) The Document Revision (Data Element 5) for multiple sheet documents will be the same as the |
| Sheet Revision (Data Element 10) for Sheet 1 of the document for the other sheets of the document. |
| (7) Enter the date of the original drawing when drawing is the original release (i.e. Data Element |
| 10 (Sheet Revision) is blank). |
| (8) If media is an ISO-9660 Compact Disk, Data Elements 20, 21, 22, and 23 (Filename, File |
| Extension, File Path, and Media Volume ID) entries must contain only d-characters (i.e., the |
| letters A through Z (upper case), the numbers 0 through 9, and the underscore symbol "_"). |
| Corresponding file names of the data files on the media should also conform to being only |
| d-characters. |
| (9) If media is an ISO-9660 Compact Disk, Data Element 22 (File Path) should not exceed 66 |
| characters (including any drive designator, colon, directory names, and forward slashes), and |
| should include no more then eight (8) levels in a directory hierarchy. Individual directory names |
| within the File Path may contain no more than eight (8) d-characters (i.e., the letters A through Z |
| (upper case), the numbers 0 through 9, and the underscore symbol "_"). Corresponding file paths on |
| the media to the data files should also conform to the aforementioned. |
| (10) Data Element 13 (File Type) is the JEDMICS five character File Type code which indicates the |
| file format of the image file (e.g. CALS Type I raster, Autocad 13 Vector, etc.). A listing of |
| current JEDMICS values must be obtained to properly fill out this Data Element. Data Elements 14 |
| through 19 are descriptors of Data Element 13. |
| (11) JEDMICS 2.5 stores only one revision value for an Individual Sheet of a document, Sheet |
| Revision. This value is stored in both the Document Revision and Sheet Revision database fields |
| within JEDMICS 2.5. The Drawing Revision is calculated by JEDMICS 2.5 during execution, using the |
| drawing book algorithm. For this reason, both the Document Revision and Sheet Revision database |
| fields within JEDMICS 2.5 will be populated with the same DFIS Data Element, Sheet Revision (Data |
Element 10).
| (12) Dates will be expressed in the following format: DD-MON-YY:HH24:MI:SS were DD is the Day, MON |
| is the Month, YY is the Year, HH24 is the 24 hour representation of the Hour (i.e. 15 for 3:00PM), |
| MI is the Minutes, and SS is the Seconds. Examples include "27-JUN-96:15:50:59" and |
| 28-JAN-92:00:00:00. |
(13) ACCOMPANYING DOCUMENT NOTES:
| (13 A1.) Data Elements 1, 2, 3, 5, & 10 (Document Number, CAGE Code, Document Type, Document Revision, |
| and Sheet Revision) pertain to the Parent Document when the identified image is an Accompanying |
| Document. Only the aforementioned Data Elements should contain entries pertaining to the Parent |
| Document for an Image Row Entry describing an Accompanying Document; all other Data Elements |
| pertain to the Accompanying Document. Within JEDMICS 2.5, an Accompanying Document |
| is associated with a Parent Document's Document Revision (Sheet Revision of Sheet 1 of the |
| Parent Document). Therefore, during upload of an Accompanying Document to a JEDMICS 2.5 system, |
| the Parent Document Revision for an Accompanying Document within JEDMICS 2.5 will be populated |
| with the DFIS Data Element 5 (Parent Document Revision). Data Element 10 (Parent Document Sheet |
| Revision) is ignored during the upload of an Accompanying Document to a JEDMICS 2.5 system. |
| (13 A2.) Data Elements 54 and 55 are not defined in current implementation of the index but are retained |
| as place holders for future use. These Data Elements should be null. |
| (13 A3.) If Data Element 51 (Accompanying Document Number) is non-null and contains entries other than |
| blanks, then the Image Row Entry is assumed to be an Accompanying Document. |
| (13 A4.) Data Element 52, (Accompanying Document CAGE Code) is included in the Index but is not |
| currently used in populating the JEDMICS 2.5 database during a JEDMICS import. The Accompanying |
| Document CAGE Code in JEDMICS 2.5 is assumed to be the same as the Base Document CAGE Code (Data |
| Element 2, JMX_cage). Data Element 52 is included only to provide the ability to accurately |
| capture the data for potential future use. Data Element 2 (Base Document CAGE Code) SHOULD NOT BE |
| USED to reflect the actual Accompanying Document CAGE code if it is different from the Base |
| Document CAGE Code. Doing some will cause the relationship between the Accompanying Document and |
| the Base Document to not be established within the JEDMICS 2.5 database. |
| (14) IDX.DFIS Version "CD's" using this structure shall enter 1.0. |
| (15) Although this is not a mandatory item in JEDMICS, when invoking the CDEX Structure in contractual |
| documents this item should be considered a mandatory requirement. |
&"Arial,Bold"&14JEDMICS DATA FILE INDEX STRUCTURE (DFIS)&10 &12Version 1.0&"Arial,Regular"&10
Enclosure (1) &P &F
