A015_Att_1_LEP_TDP_Option_Selection_Worksheet-15Nov2016.pdf

TDP OPTION SELECTION WORKSHEET

SYSTEM: DATE PREPARED:

A. CONTRACT NO. B. EXHIBIT / ATTACHMENT NO. C. CLIN D. CDRL DATA

ITEM NO(s)

1. TDP LIFECYCLE LEVEL (CHOOSE ONLY ONE PER WORKSHEET) Note: The level selected must coincide with the requirements of the elements selected in Block 5.

A. CONCEPTUAL LEVEL B. REMARKS:

DEVELOPMENTAL LEVEL

PRODUCTION LEVEL

2. DELIVERABLE DATA PRODUCTS (X ALL THAT APPLY AND COMPLETE AS APPLICABLE)

TYPE FORMAT

2D DRAWINGS NATIVE CAD ISO 32000 PDF HARD COPY A.

OTHER FORMAT (SPECIFY) _________________________________________

B. 3D MODELS:

3D Digital MODELS ONLY NATIVE CAD (Specify level of annotation) _______________________________________

3D Digital MODELS W/ MODEL ORGANIZATION SCHEMA (Specify Appendix B or other) _______________

ASSOCIATED 2D NEUTRAL FORMAT (SPECIFY, e.g., ISO 10303 APxxx) ___________________________

DRAWINGS OTHER FORMAT (SPECIFY, E.G.,3D PDF, JT)__________________________________

C. METADATA ASCII TEXT- PIPE DELIMITED ISO 10303 (SPECIFY, e.g., APxxx & DEX) _______

(Specify in Section 9) JEDMICS (DLF) OTHER FORMAT (SPECIFY) __________________

D. ASSOCIATED NATIVE FORMAT ISO 32000 PDF HARDCOPY

LISTS (See Sect 7) OTHER FORMAT (SPECIFY) _____________________________________________

E. SUPPLEMENTAL NATIVE _______________________________________

TECHNICAL DATA NEUTRAL (SPECIFY e.g., STEP AP238, 240, DEX, Other)___________________________

(Specify in Section 9) OTHER (SPECIFY e.g., PDF) _____________________________________________________

3. CAGE CODE & DOCUMENT A. CONTRACTOR CAGE & DOCUMENT NUMBERS

NUMBERS GOVERNMENT CAGE (COMPLETE 3B, 3C and 3D)

B. USE CAGE CODE: C. USE DOCUMENT NUMBERS: D. TO BE ASSIGNED BY:

4. DRAWING FORMATS (X ONE AND COMPLETE AS APPLICABLE)

CONTRACTOR FORMAT GOVERNMENT FORMAT

REMARKS: ___________________________________________________________________________________________

5. TDP ELEMENTS AND ASSOCIATED DATA REQUIRED (X ALL THAT APPLY)

CONCEPTUAL DESIGN DRAWINGS / MODELS

DEVELOPMENTAL DESIGN DRAWINGS / MODELS AND ASSOCIATED LISTS

PRODUCT DRAWINGS / MODELS AND ASSOCIATED LISTS

SPECIAL INSPECTION EQUIPMENT (SIE) DRAWINGS, MODELS AND ASSOCIATED LISTS

SPECIAL TOOLING (ST) DRAWINGS, MODELS AND ASSOCIATED LISTS

SPECIAL PACKAGING INSTRUCTIONS (SPI) DRAWINGS, MODELS AND ASSOCIATED LISTS

SPECIFICATIONS AND/OR STANDARDS (SPECIFY) _______________________________________________________

SOFTWARE DOCUMENTATION (SPECIFY) _______________________________________________________________

QUALITY ASSURANCE PROVISIONS (QAP) (SPECIFY) _____________________________________________________

METADATA (SPECIFY) _________________________________________________________________________________

SUPPLEMENTARY TECHNICAL DATA (SPECIFY) _________________________________________________________

6. TDP DATA MANAGEMENT PRODUCTS

SOURCE CONTROL DRAWING (SOCD) APPROVAL REQUEST

DRAWING NUMBER ASSIGNMENT REPORT

PROPOSED CRITICAL MANUFACTURING PROCESS DESCRIPTION

7. ASSOCIATED LISTS (X AND COMPLETE AS APPLICABLE)

A. PARTS LISTS (X ONE)

(1) INTEGRAL

(2) SEPARATE (3) CONTRACTOR SELECT

B. DATA LISTS

REQUIRED (Specify Levels of Assy)_____________________________________

C. INDEX LISTS

D. WIRING LISTS

E. APPLICATION LISTS

(1) INTEGRAL

(2) SEPARATE

(3) CONTRACTOR SELECT

F. OTHER

REQUIRED (Specify)_________________________________________________

8. APPLICABILITY OF STANDARDS. THE FOLLOWING STANDARDS APPLY: (X AS APPLICABLE)

ASME Y14.100

ENGINEERING DRAWING

PRACTICES

WITH APPENDICES:

B C D E

ASME Y14.24 TYPES AND APPLICATIONS OF

ENGINEERING DRAWINGS

ASME Y14.34 ASSOCIATED LIST

ASME Y14.35M REVISION OF ENGINEERING

DRAWINGS AND ASSOCIATED LIST

ASME Y14.41 DIGITAL PRODUCT DEFINITION DATA

PRACTICES

ASME Y14.5 DIMENSIONING AND TOLERANCING

OTHER STANDARDS

APPLY AS DESCRIBED:

COMPANY STANDARDS

PERMITTED

YES NO

9. OTHER TAILORING (ATTACH ADDITIONAL SHEETS AS NECESSARY)

Sheet: Sheet1

Mandatory

Data

For Input

Seq

DATA ELEMENT

Purpose

Size /Type to JEDMICS

Notes

1.0

JMX_DocNumber

Document Number

32 bytes / char x

(13)

2.0

JMX_DocCage

Commercial and Govn't Entries Reference

5 bytes / char x

(13)

3.0

JMX_DocType

Document Type

2 bytes / char x

(4) (13)

4.0

JMX_DocumentSize

Size of drawing (May Be A Through K and R except I)

2 bytes / char x

5.0

JMX_DocRevision

Document Revision

2 bytes / char x

(4) (6) (11) (13)

6.0

JMX_DocumentRevDate

Document Revision Date

18 bytes / char

(7) (12)

7.0

JMX_DocumentTitle

Document Title

40 bytes / char

8.0

JMX_SheetNumber

Sheet Number of Document

12 bytes / char x

9.0

JMX_NumberOfSheets

Number of Sheets for Document

4 bytes / char

(15)

10.0

JMX_DocSheetRevision

Sheet Revision

2 bytes / char x

(4) (11) (13)

11.0

JMX_FrameNumber

Frame Number

4 bytes / char x

12.0

JMX_NumberOfFrames

Number of Frames for Sheet

4 bytes / char x

13.0

JMX_FileType

Designator for the Data Format Type of File

5 bytes / char x

14.0

JMX_FileTypeFormat

Description of the Format of the File Type

20 bytes / char

(3) (10)

15.0

JMX_FileTypeSrcFlavor

Description of the File Type Source Flavor

16.0

JMX_FileTypeDestFlavor

Description of the File Type Destination Flavor

17.0

JMX_FileTypeContent

Description of the File Type Content

18.0

JMX_FileTypeVersion

Description of the File Type Version

14 bytes / char x

(3) (10)

NEEDS TO BE MANDATORY

19.0

IDX_DfisSourceCage

CAGE Code of The Originator of The DFIS Data Set

5 bytes / char x

(3)

20.0

IDX_FileName

File Name of Image File (without extension)

8 bytes / char x

(8)

21.0

IDX_FileExtension

File Extension of Image File

3 bytes / char x

(8)

22.0

IDX_FilePath

File Path Where Image File is Located

242 bytes / char x

(8) (9)

23.0

IDX_MediaVolumeID

Media Volume ID of Media Where File is Located

11 bytes / char x

(8)

24.0

IDX_MajorGroup

Major Group Designation Within Index

20 bytes / char

25.0

IDX_MinorGroup

Minor Group Designation Within Index

8 bytes / char

26.0

JMX_SecurityLevel

Security Level

1 byte / char x

27.0

JMX_Rights

Viewing Rights

1 byte / char x

"U" or "L"

28.0

JMX_ForeignSecure

Indicates if Foreign Personnel May View the Drawing

1 byte / char x

"N" or "Y"

29.0

JMX_Nuclear

Indicates if Drawing Contains Nuclear Equipment

1 byte / char x

"N" or "Y"

30.0

JMX_Subsafe

Indicates if Critical Safety

1 byte / char x

"N" or "Y"

31.0

JMX_AirType

Model/Device

6 bytes / char

32.0

JMX_Apl

Allowance Parts List

35 bytes / char

33.0

JMX_CadInfo

Computer Aided Design Reference

2 bytes / char

34.0

JMX_ControlCode

Activity Code Furnished by Procuring Activity

2 btyes / char

35.0

JMX_Hsc

Hierarchical Structure Code

12 bytes / char

36.0

JMX_Nsn

National Stock Number

13 bytes / char

37.0

JMX_Uic

Unit Identification Code

5 bytes / char

38.0

JMX_System

Associated Equipment/System Group

32 bytes / char

39.0

JMX_Nomenclature

Name of Equipment Described in the Drawing

20 bytes / char

40.0

JMX_ShipClass

Ship Classification

4 bytes / char

41.0

JMX_ShipTypeHullNum

Ship Type/Hull Number Classification

9 bytes / char

42.0

JMX_MasterLocation

Engineering Drawing Master Location

30 bytes / char

43.0

JMX_OfflineLocation

Engineering Drawing Off-line Location

80 bytes / char

44.0

JMX_ParentCage

CAGE of Parent Drawing

5 bytes / char

45.0

JMX_ParentDocNumber

Drawing Number of Parent Drawing

32 bytes / char

46.0

JMX_PartNumber

Identifies Associated Part Number With CAGE

32 bytes / char

47.0

JMX_SubSheet

Further Identifies Sheet

3 bytes / char

48.0

JMX_Succeeding

Drawing Number and CAGE of Superseding Drawing

20 bytes / char

49.0

JMX_DistStmt

Distribution Statement

2 bytes / char

50.0

JMX_AccDocType

Accompanying Document - Document Type

2 bytes / char x

(5) (13)

51.0

JMX_AccDocNumber

Accompanying Document - Document Number

32 bytes / char x

(5) (13)

52.0

JMX_AccDocCage

Accompanying Document - CAGE Code

5 bytes / char x

(5) (13)

53.0

JMX_AccDocRevision

Accompanying Document - Document Revision

2 bytes / char x

(4) (5) (13)

54.0

[Blank]

[This Field Reserved For Future Use]

0 bytes / char

(13)

55.0

[Blank]

[This Field Reserved For Future Use]

0 bytes / char

(13)

56.0

JMX_WeaponsSystemCode

Weapon System Code

15 bytes / char

57.0

IDX_DfisVersion

Version of the DFIS Structure Implemented

4 bytes / char x

(14)

58.0

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.

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.

Block 5 — Block 5 - TDP deliverables will include interface constraints for the Rx lens as identified by the contractor, and will also explicitly describe the following values:

A Measurement B Measurement Diagonal Measurement Circumference Value