A015_Att_1_Encl_1_CDEX.pdf

Enclosure 1

JEDMICS Compact Disc Engineering Data Exchange (CDEX)

1.0 INTRODUCTION

The main purpose of the JEDMICS Compact Disk Engineering Data Exchange (CDEX) document is to define the format for the exchange of data between JEDMICS repositories utilizing compact disc media. The business processes are totally controlled by the individual organizations. This document contains requirements for data exchange utilizing CDs in and out of JEDMICS, the only mandatory requirements are for Image files and Index structure. The INDEX.DLF file will follow the format as required in the current version of the JEDMICS data File Index Structure (DFIS). These requirements must apply to all contractor data or when ordering CDs. Additionally the CDEX document contains some guidelines for CDs which will vary according to the business process.

1.1 JEDMICS PROCESS

The JEDMICS process for the exchange of data on CDs will be in accordance with JEDMICS operations manuals. The target CD will contain a hierarchical directory structure in accordance with ISO-9660. The CD shall contain all directories and files necessary to support the producing activities business process, and the intended use of the Disk. A sample structure (Figure 1) is described herein to assist in the CD development process.

1.1.1. Non-JEDMICS Data. The user may assemble additional files from sources outside JEDMICS (e.g. software, contracting documents, security instructions, special handling, general information, other engineering data from non-JEDMICS systems, configuration data, etc.) and add these files to the dataset prior to mastering the CD.

1.1.2. Data Use Software. The appropriate software application(s) from a library may be included with the dataset. Since the JEDMICS system is managing a variety of data types, the software application(s) required are dependent on the data type. For example, a viewer software program may be included with raster images. It is anticipated that the file type codes will be examined to determine the required software applications. Inclusion of all possible software applications is not practical and consumes disk space needed for data.

2.0 INDEX. DLF

All CDs created for any of the purposes below shall contain an INDEX.DLF file in the Root Directory. The INDEX. DLF file will follow the format as required in the current version f the

JEDMICS (DFIS):

a. Delivery of data from a contractor to JEDMICS repository.

b. Transfer of data between JEDMICS sites.

c. CDs developed for an activity’s business process that may also be used by another JEDMICS site.

ROOT

|-- INDEX.DLF (2.0 JEDMICS USE ONLY)

|-- VOLUMEID.TXT (3.1 Volume Identification File) |-- README.TXT (3.2 General Information) |-- INSTALL.BAT (3.3 Installation Script)

|-- SYSTEM

|-- VIEWERS (3.4 Viewer (s) SoftwareDir.)

| |-- VIEWERX

| | |-- xxxxxxxx.EXE | | |-- yyyyyyy.DLL | | |-- zzzzzzzz

| |-- VIEWERZ

| -- request1 (3.5 Job Directory) | |-- JOBDATA (3.6 Job Summary Data) | |-- RFQ (3.7 Solicitation Doc) | |-- TDPLS (3.8 TDP Directory) | | |-- TDP0001 (3.8.1 TDPL Document) | | |-- TDP00002.DAT (3.8.2 TDP Identification)

| | |-- TDP00003

| |-- INDEX.DAT (3.9 Index Document List File) | |-- IMAGES (3.10 Image Directory) | | |-- 0001 (3.11 Repository Data Files) | | |-- 0002 | | |-- so forth | | |- so forth

| | |-- ZZZZ

| | |--IMAGES02

| | |--IMAGES03

| |-- NORS (3.12 NOR Directory) | |--MODELS (3.13 Models and Engr. Data) | |-- filenames (3.13.1 Models Directory & Files) | |--directory names |-- request2 (3.5 Job Directory)

Figure 1. Sample CD Directory Structure d . Advanced Technical Information System (ATIS) CDs produced from JEDMICS.

INDEX.DLF in the root directory of the ATIS CD will not be used for ATIS, however the file will provide the index information if ATIS data is entered into JEDMICS.

The INDEX.DLF file shall contain an index record for each image file contained on the CD as described in the JEDMICS DFIS.

2.1. One CD with Separate Technical Data Packages (TDP) Directories. The user may elect to include multiple TDPs on the CD in separate directories. This scenario occurs frequently when multiple reprocurement TDPs are being prepared for a restricted source or qualified bidders list, or when multiple TDPs are being transferred to another organization’s repository system. The INDEX.DLF shall contain an index record for each image file on the CD as described in the JEDMICS DFIS and located in the Root Directory.

2.2. Multi-disk TDP. In cases of a very large dataset that may not fit on one CD, the dataset may be divided across multiple CDs. One CD will typically hold approximately 4000 images. Each CD will have its own INDEX.DLF. This INDEX.DLF shall contain all the images on that CD.

2.3 Disk Marking/Labeling. Information from the JEDMICS job and/or user supplied information will be used to prepare disc marking and labeling. As a minimum, each compact disk will be labeled with job identification, security classification, and distribution rights according to MIL-STD-1806 (Digital Data Marking).

3.0 COMPACT DISK DATA STRUCTURE

The CD shall contain all directories and files necessary to support the producing activities business process. Depending on the business process these files may be included on the CDs in this recommended format.

3.1 Volume Identification File

FILENAME: VOLUMEID.TXT

FORMAT: ASCII Text In “keyword:data tuple” format.

DESCRIPTION: Flat file in ASCII text format that identifies the volume.

Information is provided in a keyword and data field tuple to allow for both human interpretation and computer processing.

SEPARATOR: Each tuple is separated by a CR/LF.

RULES: File is Required for each volume. However, specific data elements may be omitted if not used by the organization.

Data elements contained in this file include:

3.1.1 VOL_TITLE: 50-character data field. Name by which the disk is known

3.1.2 Volume_ID: 11 characters.

The VID is a unique disc identification serial number. The VID is a concatenation of a 5 character organization Unique Contractor and Government Entity (CAGE) Code and unique 7 character sequential number. The CAGE code shall identify the organization creating the original CD/R. Any duplicates or CD-ROMS made form the CD/R shall not change the CAGE portion of the VID.

3.1.3 PWD: 25 characters.

Procurement Work Directive or Contact Number if appropriate from the DD-1095.

3.1.4 Volume_Created Date: mm/dd/yy

Computer generated date the volume was created.

3.1.5 Volume_Number: 2-characters

Which volume of the set is this one. Default of 01 unless a TDP is split across multiple disks.

3.1.6 Volumes_in_Set: 2-characters

Number of volumes in a set. Field will be used if a TDP is split across multiple disks.

3.1.7 Sender_Activity: 50 characters

The activity/site that sent the package out. The Sender_Activity is site defined.

3.1.8 Sender_POC_Name: 50 characters

Sender point of contact name. Sender_POC_Name is site defined.

3.1.9 Sender_POC_Address: 50 characters

Address of sender.Sender_POC_Address is site defined.

3.1.10 Sender_POC_Phone: (xxx)xxx-xxxx

Phone number of sender. Sender_POC_Phone is site defined.

3.1.11 Sender_POC_Fax: (xxx)xxx-xxxx

Fax number for sender. Sender_POC_Fax is site defined.

3.1.12 Sender_POC_EMAIL: 50 characters

EMAIL address for sender. Sender_POC_EMAIL is site defined.

3.1.13 FEES: 50 characters

Optional field defining charges/fee associated with providing this information.

3.1.14. Security_Classification: 1-character

Rule=inherents highest classification of documents contained within disk.

3.1.15 Classification_Authority: 50 characters

Activity who assigned classification. Classification_Authority is site defined.

3.1.16 Security_Handling: 50 characters

Special instructions related to security and handling. Security_Handling is site defined.

3.1.17 Declassification_Date: mm/dd/yy

Rule= optional for classified data future use.

3.1.18 Distribution_Restrictions: 50 characters

Rule= inherence highest restriction of documents contained on disk.

3.1.19 Jobs_Contained: 12345678

Rule= one key-word/data-field tuple for each jobid contained on volume.

Value must match Job Directory Name (see 1.7) Maximum of 8 character directory name.

Example File:

TITLE :MQM-107 Target System

PWD :P02CD014024D A

Volume_Identifier (VID) :88786000001 Volume_Created Date :10/12/95 Volume_Number :01 Volumes_in_Set :01 Sender_Activity :US Army Missile Command Redstone Arsenal AL Sender_POC_Name :John Doe Sender_POC_Address :ATTN.AMSMI-CIC-ED-MI Sender_POC_Phone :(205) 876-8251 Sender_POC_Fax :(205) 842-7360 Sender_POC_EMAIL :monty@redstone-emh2.army.mil FEES :this media provided at no cost to perspective bidders Security_Classification :Unclassified Classification_Authority :US Army Missile Command Redstone Arsenal AL Security_Handling :For Official Use Only Declassification Date :12/30/99 Distribution_Restrictions :unrestricted Jobs_Contained :12134545 Jobs_Contained :13324355

3.2 General Information

FILENAME:README.TXT

FORMAT: ASCII Text DESCRIPTION: General explanation, information, instructions on how to use the volume including any comments that describe the organization of the information. The file may include comments needed to install provided software, comments for executing provided software, and any comments that allow the user to effectively use the volume of information.

RULES: Optional file. Contents of file is site selectable.

Insert CR/LF separator after each 70 characters.

SOURCE: default template. README.TXT is site defined.

3.3 Installation Script

FILENAME: INSTALL.xxx FORMAT: File suffix may be .BAT or .COM or .EXE depending on software requirement.

DESCRIPTION: Script file may be used to simplify the processing of the volume. The script file may be used to set system variables, initiate software applications for presenting the data, or used for installing or executing provided software.

RULES: Optional file. Contents of file is site selectable.

SOURCE: default template

3.4 Viewer(s) Software Directory

DESCRIPTION: An optional directory for storage of application software.

DIRECTORY NAME: VIEWERS

1. Optional sub-directories used to provide software applications.

2. Each application provided will reside in a separate sub-directory.

3. Names of sub-directories are site selectable.

4. The specific software to be provided is dependent upon the file type code of the data included in the IMAGES directory.

SOURCE: default template. Software applications provided are site defined.

3.5 Job Directory

DIRECTORY NAME: 8 character unique name DESCRIPTION: A unique directory for storage of a request.

RULES:

1. One unique directory for each job.

2. Directory name is site selectable and represents the request identifier. The directory name may be one of the following: JEDMICS JOBID, PWD, PRON, USERID, TPN, NSN.

3. Directory name must match an entry in the Jobs_Contained: data field used in the VOLUMEID. TXT file.

4. Multiple jobs/requests may be placed on a compact disk. The hierarchical data structure below the Job Directory will be repeated for each job/request.

5. If multiple jobs/requests are placed on a compact disk, then a job/request can not be split across multiple compact disks.

3.6 Job Summary Data

FILE NAME: JOBDATA

DESCRIPTION:Create Identifier - the activity/site that generated the data (originator) Creator POC - the name, address, phone, fax, EMAIL of the creator Number of documents in volume (consistency check) Short description for each job Time Period of Content: Time period for which the data on the disk is valid See page 7 of MIL-STD-1806 for guidance.

3.7 Solicitation Document

FILE NAME : RFQ

DESCRIPTION: Optional directory for inclusion of contractual documents such as a Request for Quote (RFQ), Request for Proposal (RFP), Synopsis, ETC. Specific file to be included in this directory are site selectable.

3.8 TDP Directory

FILE NAME: TDPLS

DESCRIPTION: Optional directory for inclusion of Technical Data Package Lists (TDPLs).

3.8.1 Technical Data Package Listing (TDPL) Document

FILENAME: TDPxxxxx.

FORMAT: ASCII Only Text DESCRIPTION: An optional report listing all documents of the Technical Data Package (TDP).

3.8.2 Technical Data Package Identification

FILENAME: TDPID.TXT

FORMAT: ASCII Only Text DESCRIPTION: This is an optional file which contains information that uniquely identifies a technical data package. Information is provided in a keyword and data field tuple to allow for both human interpretation and computer processing. Each tuple is separated by CR/LF character separator.

Information in this file is provided by procurement and configuration management systems and provides an association between the TDP and originating sources.

RULES: Require file for each package of technical data.

TUPLES:

Top_Part_Number: aaaaaaaaaaaaaaa Top_NSN: bbbbbbbbbb PRON: cccccccccccc Nomenclature: dddddddddd End_Item_Spec (EIS): eeeeeeeeeee TDPL_Date: mm/dd/yy Weapon_System_Code: fffffffffffffff Preparer: ggggggggg

3.9 Index Elements File

FILENAME: INDEX. DAT

FORMAT: ASCII Only Text DESCRIPTION: This file includes one record for each repository data file contained in the data package sub-directory. In cases where data files are contained on multiple compact disks, the INDEX.DAT file will contain a record for each data file in the complete set of disks.

One data record will exist for each data file.

Data Elements will be follow the same structure as the INDEX.DLF.

Each data element will be character delimited using a pipe bar “|” character, hexadecimal 7C Each record will be delimited by CR/LF characters.

3.10 Image Directory

DIRECTORY NAME: IMAGES

DESCRIPTION: Repository data files will be placed in a directory named IMAGES. A maximum of 500 data files will be placed in the top level directory. If more than 500 data files exist, then a sub-directory named IMAGES02 will be created and an additional 500 images placed in the sub-directory.

Additional sub-directories will be added until the maximum disk capacity is reached. Considering that a compact disk will hold approximately 5000 data files, the above structure should be sufficient.

3.11 Repository Data Files

DESCRIPTION: Due to the 8 character filename limitations imposed by the ISO-9660 format, the filename for repository data files can not exceed 8 characters and can not be associated with Index data elements. Repository data files will be assigned a unique filename that matches the name used in the index data record. Data file names will begin with 00000001 thru zzzzzzzz.

3.12 NOR Directory

DIRECTORY NAME: NORS

RULES: optional directory. May be utilized by individual sites to include unincorporated changes.

3.13 Models and Engineering Data Directory

DIRECTORY NAME: MODELS

DESCRIPTION: This is an optional directory. This directory may be utilized by individual sites to include engineering models. As engineering data is loaded to the JEDMICS system utilizing the file type code to define the type of data, this directory will not be required.

3.13.1 Models Directory & Files

DESCRIPTION:

The directories and files included are at the discretion of the individual sites provided naming convention complies with ISO-9660.

4.0 COMPACT DISK MASTERING

After Pre-master Processing are completed, the dataset is transformed into a virtual image of the compact disc ready for delivery to a compact disk recordable mastering unit. The compact disk virtual image will contain a hierarchical directory structure and file naming conventions consistent with ISO-9660 conventions. Compact discs produced by this process will be compliant with ISO 10149 Mode 1 (Yellow Book) physical format.