CDRL Package for D-TACAN 12-10-09.pdf
PDF 2 MB Posted
- Attached to
- Communication, Detection, and Coherent Radiation Equipment Federal contract opportunity
- Solicitation number
- FA8102-09-R-0007
About this file
Page 1 of the attachment package to CDRL A024 was missing at the official posting. This package includes that missing page. No other information has been changed.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| FA810209R0007_______0002.RTF | RTF text file | |
| FA810209R0007_______0001.RTF | RTF text file | |
| DTACAN QUESTIONS 3rd Installment.doc | DOC document | |
| DTACAN QUESTIONS 17Dec09.doc | DOC document | |
| D TACAN RFP Questions Answers.docx | DOCX document | |
| D-TACAN Frist Article Test | — | |
| D-TACAN Purchase Item Description Version 2.pdf | ||
| CDRL Package for D-TACAN.pdf | ||
| D-TACAN PWS - 3 Nov 09.pdf | ||
| CDRL Package for D-TACAN 9-3-09.pdf | ||
| D-TACAN Commercial Item Description Version 1.pdf | ||
| DRAFT RFP.pdf | ||
| D-TACAN Frist Article Test | — | |
| D-TACAN PWS - 3 Sept 09.pdf | ||
| Draft CID.pdf | ||
| Draft PWS.pdf |
Show all 16
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
FA8102-10-C-0001
DRCN PS-09-08-060
26 October 2009
The requirements specified in this CDRL are identified in accordance with procedures in DOD 5010.12M. Data Item Descriptions, DD Forms 1664, specified on the CDRL are those listed in the Acquisition Management Systems and Data Requirements Control List, DOD 5010.12L.
CONTRACT DATA REQUIREMENTS LIST (CDRL)
Air Force Deployable Tactical Air Navigation (D-TACAN) System Replacement Program
Data Request Control Number
PS-09-08-060
Contract Reference
1. METHOD OF TRANSMITTAL
a. Unless otherwise noted on the CDRL Form (DD Form 1423) in Block 16, all data shall be delivered electronically via email or CD/DVD, and shall be in a software file format that is compatible with Government systems. If the required data cannot be delivered electronically, the Contractor shall distribute per Block 14 of the CDRL.
b. All data submitted by a letter of transmittal or DD Form 250 shall be delivered to the attention of the Requiring Office (Block 6) and will identify the contract number, Data Item Description number, CDRL sequence number, document number and title.
c. Unless otherwise specified in Block 16 of the CDRL, the data submittal date is interpreted as the date the Government (Block 14) receives the data or the date it is submitted electronically.
d. For each data item in the CDRL, the Contractor shall clearly state in the final transmittal letter that this is the last submittal being made and that all contractual requirements concerning the data item have been fulfilled.
2. MODIFICATION OF DATA REQUIREMENTS
a. The Data Manager (DM) is a member of the D-TACAN Replacement Program Integrated Product Team (IPT). No changes to the data requirements of this contract shall be made without coordination of the DM and specific approval of the Procurement Contracting Officer (PCO).
b. Changes to Requiring Office (Block 6) and Distribution (Block 14) may be authorized and directed by a PCO letter to be incorporated by subsequent contract modification.
3. DATA APPROVAL:
Unless otherwise specified in the Remarks (Block 16) of the appropriate data item, the following definition applies to Block 8 of the CDRL:
a. The use of an “A” in Block 8 means the document identified is critical and requires written Government approval. The review cycle for data will begin on the date the last addressee receives the data, or upon submittal if delivered electronically. The Office of Primary Responsibility (OPR) designated in Block 6 of the DD Form 1423 will consolidate the evaluations performed by the data recipients with his own and respond through the PCO to the Contractor within thirty (30) working days after receipt of the data submittal, unless otherwise specified.
b. The absence of an “A” in Block 8 does not relieve the Contractor of the obligation to comply with the Data Item Description (DID) requirements.
c. Data submittal requirements shall not be considered to have been met until the CO has determined that all contractual requirements have been met regarding the identified data.
4. REVISIONS TO DATA SUBMITTALS AND RESUBMITTALS OF DATA:
Unless otherwise specified, data submittals that are disapproved by the Government shall be revised and resubmitted by the Contractor within thirty (30) days from the date of the PCO letter unless otherwise noted on the CDRL.
5. TAILORED DATA ITEMS
A slash (/) and the letter “T” (i.e. DI-E-3103A/T) added to the DID number in Block 4 of the CDRL denotes the DID has been tailored to comply with specific program requirements. If data preparation instructions contained in Block 10 of the DID conflict with those of the CDRL, the CDRL instructions will govern.
6. ACRONYMS:
ACO Administrative Contracting Officer ASREQ As Required CO Contracting Officer DAC Days After Contract Award IAW In Accordance With MTHLY Monthly ONE/R One time with revisions LT Letter of Transmittal
1. MARKING TECHNICAL DOCUMENTATION
a. Distribution Marking System:
i. In accordance with Section 1.30 of Title 10, “United States Code” a DoD distribution marking system for technical data has been established by DoD Directive 5230.24, “Distribution Statements on Technical Documents,” 18 March 1987. The intent of the system is to stem the flow of military-related technical data to our adversaries, without inhibiting technological growth or blocking the exchange of technical data that is vital to progress and innovation. All DoD components responsible for technical data are required to determine the distribution availability and arrange to mark the data appropriately before primary distribution. Distribution statements and export-control statements, supplemental to any security markings, shall be marked on all technical data to denote the extent of its availability for secondary distribution, release, and disclosure without need for additional approvals and authorizations from the controlling DoD office.
ii. Based on the technical content of the data, one of seven distribution statements defined in DoD Directive 5230.24 is to be applied to indicate the extent of secondary distribution. The seven authorized distribution statements provide options ranging from unlimited distribution to no secondary distribution without specific authority of the controlling DoD office. Distribution statements should be selected to denote the audience for which the data is intended. The statement selected shall not restrict the data any further than is actually required to protect the interests of the Government. The authority to withhold unclassified technical data from the public is found in Section 130 of Title 10, “United States Code” as implemented by DoD Directive 5230.25 “Withholding of Unclassified Technical Data from Public Disclosure,” 6 November 1984.
iii. It is the responsibility of the program office to select the correct distribution statement, to ensure that the corresponding code letter (“A”, “B”, “C”, “D”, “E”, “F”, or “X”) is in Block 9 of the DD Form 1423 or that Block 16 of the DD Form 1423 contains instructions on application of the correct distribution statement before initial distribution of the technical data. If the Contractor feels that a different statement is required, he may formally notify the contracting officer in a letter, make it a subject of discussion during negotiations or at one of the scheduled program audits or reviews.
b. Marking technical data:
i. All new or requested unmarked production, engineering, logistics, and scientific and technical information, regardless of its medium, physical form, or characteristics, including preliminary drafts and working papers, shall be marked with a distribution statement. This includes technical reports, blueprints, drawings, technical orders, technical manuals, plans, instructions, computer software, viewgraphs, film, technical papers, photographs, etc. If the document contains export-controlled technical data, it also must be marked with an export control warning statement. Distribution statements can be applied to technical data that contain or reveal proprietary information used.
(Location suggestions for placing the statements on the data may be obtained from MIL-STD-1806.)
ii. Technical data categorized as cryptographic/communications security, communications/electronic intelligence, and similar categories as may be designated by the Director, National Security Agency, whose distribution is limited through alternate methods, are exempt from these marking provisions.
iii. Certain types of technical data preclude placing the entire notice on the document. To accommodate this problem, each distribution statement contains an authorized abbreviation form. Abbreviated distribution statements are to be used only when space precludes placing the entire notice on the document. The use and wording of these statements are described in the following paragraphs.
c. Distribution Statements: The following statements regarding distribution must appear on the cover and title page of each document submitted, including the first sheet of each drawing.
The abbreviated form is: “Statement B, U.S. Government Agencies, 747 ACSG/PKB.”
d. Controlling Office: The following address shall be used for the “controlling office” for the program: 747 ACSG/PKB, 3001 Staff Dr. Ste 2AC-81A, Tinker AFB, OK 73145
e. Export-Controlled Warning Statement: Besides a distribution statement, the marking system also requires the use of a warning notice on all documents that contain export-controlled technical data. That notice may be used in conjunction with any of the six limited distribution statements (“B”, “C”, “D”, “E”, “F” and “X”.) Statement “A”, which denotes public release, cannot be used in conjunction with the export-control warning notice.
f. Destruction Notice: All unclassified technical data marked with distribution statements “B”, “C”, “D”, “E”, “F” or “X” shall be handled and destroyed as “For Official Use Only” (FOUO) documents, as described in DoD 5400.7-R. Classified data and classified limited technical data shall be handled and destroyed in accordance with the procedures in Chapter IX of DoD 5200.1-R “Information Security Program Regulation” or follow the procedures in DoD 5220.22-M “Industrial Security Manual”.
2. ELECTRONIC DATA TRANSMISSION
a. Electronic Data Transmission Statement for the CDRL:
i. The recipients will be notified by email of each submission of CDRL data. All submissions will be via email or CD/ DVD, unless other arrangements are approved by the Government. The versions of this software shall remain compatible with current program office software. The Contractor shall inform 747 ACSG/PKB if any of their data deliverables cannot comply with the above electronic formats. In such cases the Contractor shall recommend, for program office approval, alternative delivery format(s).
ii. The Government review cycle for data will begin on the date the last addressee listed in Block 14 receives the data or the date it is submitted electronically.
"WARNING - THIS DOCUMENT CONTAINS TECHNICAL DATA WHOSE EXPORT IS
RESTRICTED BY THE ARMS EXPORT CONTROL ACT (TITLE 22, U.S.C., SEC 2751 ET
SEQ.) OR THE EXPORT ADMINISTRATION ACT OF 1979, AS AMENDED, TITLE 50,
U.S.C.. APP. 2401, ET SEQ. VIOLATIONS OF THESE EXPORT LAWS ARE SUBJECT TO
SEVERE CRIMINAL PENALTIES. DISSEMINATE IN ACCORDANCE WITH THE
PROVISIONS OF DOD DIRECTIVE 5230.25.
DISTRIBUTION STATEMENT B
“Distribution authorized to U.S. Government Agencies only; proprietary information; September 2009. Other requests for this document shall be referred to the AF D-TACAN Replacement Program Contracting Officer, 747 ACSG/PKB, 3001 Staff Dr. Ste 2AC-81A, Tinker AFB, OK 73145.”
3. MAILING LISTS:
OFFICE SYMBOL/MAIL ADDRESS E-MAIL ADDRESS
747 ACSG/PKB
3001 Staff Drive, Suite 2AC-81A Tinker AFB, OK 73145 Attn: Mr. David Hancock
David.Hancock@tinker .af.mil
558 ACSS/GFLA
3001 Staff Drive, Suite 2AC4-100B Tinker AFB, OK 73145 Attn: Mr. Julius Logan
OC-ALC/ENSDAA
3001 Staff Drive, Suite 1AA82A Tinker AFB, OK 73145
Julius.Logan@tinker.af.mil
CONTRACT DATA REQUIREMENTS LIST
TABLE OF CONTENTS
CDRL
No.
Authority CDRL Title - Subtitle
A001 DI-MCCR-80700 Computer Software Product End Items A002 DI-IPSC-81442A Software Version Description (SVD) A003 DI-MGMT-81650 Integrated Master Schedule (IMS) A004 DI-MGMT-80227 Contractor's Progress, Status And Management Report A005 DI-ADMN-81249A Meeting Agenda A006 DI-ADMN-81250A Meeting Minutes A007 DI-MGMT-81024 System Engineering Management Plan (SEMP) A008 DI-CMAN-80858B Contractor’s Configuration Management Plan A009 DI-CMAN-80639C Engineering Change Proposals A010 DI-CMAN-80640C Request for Deviation (RFD) A011 DI-CMAN-81022C Configuration Audit Summary Report A012 DI-NDTI-80603A Test Procedures - Production Acceptance Test Procedures A013 DI-NDTI-80809B Test/Inspection Report - Production Acceptance Test Report A014 DI-SAFT-80101B System Safety Hazard Analysis Report A015 DI-ENVR-81375 Environmental Health and Safety Plan (HSP) A016 DI-ILSS-80095 Integrated Logistics Support Plan A017 DI-SESS-81705 Depot Level Repair Instructions A018 DI-ALSS-81557 Supplemental Data for Provisioning - Provisioning Parts List (PPL) A019 DI-ILSS-80134A Proposed Spare Parts List A020 DI-TMSS-80527B Commercial Off-The-Shelf (COTS) Manuals and Associated Supplemental Data A021 DI-IPSC-81443 Software User Manual A022 DI-ILSS-80872 Training Material A023 DI-SESS-80294B Maintenance Test and Support Equipment List - Support Equipment
Requirements Document (SERD) A024 DI-SESS-81000C Product Drawings/Models and Associated Lists
Attachment 1 Continuation of DD Form 1423-1, Block 16
1. Blk 4:
a. The CDRL to DID DI-SESS-81000C is tailored as follows: Para 4. Add ASME Y14.24M after ASME Y14.100 and Appendices B through E, as required, and before ASME Y14.34M. Add ASME Y14.35M after ASME Y14.34M.
b. See DD Form 2554-1, TDP Option Selection Worksheet, Tailoring for Product Drawings and Associated Lists/Specifications/Standards for specific tailoring requirements.
2. Blk 7:
a. "SD" for the final delivery of TDP compact disk.
b. "SD" for the final delivery of printed wiring board magnetic media.
c. "LT" for the delivery of a sample compact disk for government verification testing.
d. "LT" for pre-delivery lists.
3. Blk 9:
a. For unlimited rights data, Distribution Statement C in accordance with DODD 5230.24 shall be applied within the border, to the first page of each TDP document prior to delivery of documents to OC-ALC/ENSDAA.
Distribution statements on existing drawings and associated lists requiring delivery under this contract need not be changed unless otherwise specified in the contract or order.
b. The reason, date of determination, and controlling DOD office shall be "Critical Technology", the award date of the contract, and 747 ACSG/PKB (Controlling DoD office).
c. For limited rights data, Distribution Statement B in accordance with
DODD 5230.24 shall be affixed within the border to the first page of each TDP document prior to delivery to OC-ALC/ENSDAA. Distribution statements on existing drawings and associated lists requiring delivery under this contract need not be changed unless otherwise specified in the contract. The reason, date of determination, and controlling office shall be
“Proprietary Information”, award date of the contract, and 747 ACSG/PKB (Controlling DoD office).
d. The following export control notice, in accordance with DOD 5230.24, shall be affixed to the engineering drawings and associated lists as an added paragraph below the distribution statement.
"WARNING. This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22 U.S.C. Sec 2751, et seq.)
or the Export Administration Act of 1979, as amended (Title 50 U.S.C. App 2401, et seq.). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with the provisions of DOD Directive 5230.25."
4. Blk 10:
a. Copies of TDP’s shall be provided to support reviews and audits. Digital TDP documentation shall be submitted in lieu of paper copy. Re-submittals to OC-ALC/ENSDAA shall be required for each deficient document until deficiencies identified are corrected to the satisfaction of
OC-ALC/ENSDAA
b. Pre-delivery lists shall be submitted 60 days before initial delivery of the TDP. Supplemental lists shall be provided to reflect changes, additions or deletions to the initial submission.
c. Shipping list(s) are required for each shipment.
d. Printed wiring board magnetic media as required.
e. Deliver TDP documentation NOT LATER THAN 60 calendar days after Government approval for final delivery of the engineering data.
f. Re-submission is required for deficient, improperly formatted, illegible data and missing data. All data re-submittals shall include an Index.dlf file along with the corrected data. Correct and resubmit NOT LATER THAN 30 calendar days after Government notification to the contractor of deficiencies.
5. Blk 11, 12, AND 13:
a. TDP documentation is required for each IPR, audit or review. The contractor shall resubmit corrected TDP documents for government review NOT LATER THAN 30 calendar days after each government review.
b. Deliver TDP documentation NOT LATER THAN 60 calendar days after Government approval for final delivery of the engineering data.
Resubmission is required for deficient, improperly formatted, or illegible data as determined by OC-ALC/ENSDAA. Correct and resubmit corrected data NOT LATER THAN 30 calendar days after Government notification to the contractor of the deficient delivery.
c. Deliver the Pre-delivery list NOT LATER THAN 60 days prior to the initial delivery of TDP documentation.
d. Deliver shipping list(s) with each TDP shipment.
f. Deliver TDP updates/revisions 30 days prior to last hardware delivery.
g. Deliver formatted sample compact disk NOT LATER THAN 90 calendar days before test readiness review.
6. Blk 14
TDP DOCUMENTATION
CD Delivery Copies
OC-ALC/ENSDAA 558ACSS/GFLA
REVIEW/AUDIT 1 1
PRE-DELIVERY LIST 1 1
SHIPPING LIST(S) 1 1
SAMPLE COMPACT DISK 1 1
COMPACT DISK 1 1
Totals
A copy of all SD or LT shall also be sent to 747 ACSG/PKB.
TDP OPTION SELETION WORKSHEET
PRODUCT DRAWINGS AND ASSOCIATED LISTS
A. CONTRACT NO.
FD2030-09-90076
B. EXHIBIT/ATTACHMENT NO. C. CLIN
D. CDRL DATA ITEM NO.
A024
1. DELIVERABLE PRODUCT (X and complete as applicable.)
a. ORIGINALS (Specify current design activity’s full size reproducible drawing or digital data files(s) on which is kept the revision record recognized as official) (Identify specification, type, grade, and class, etc.)
X b. REPRODUCTIONS (Identify specifications, type, grade and class, etc., and quantity of each.)
(See block 9) X c. DIGITAL DATA (Identify specification, exchange media, etc. and specify original (master) or copy)
(See block 9)
2. CAGE CODE AND DOCUMENT NUMBERS (X One)
X a. CONTRACTOR
b. GOVERNMENT Complete (1) and (2) or (3)
(1) Use CAGE Code (2) Use Document Numbers (3) To be assigned by:
3. DRAWING FORMATS AND DRAWING FORMS (X one and complete as applicable)
X a. CONTRACTOR FORMATS Forms to be provided by contractor.
b. GOVERNMENT FORMATS. Forms to be provided by contractor.
c. GOVERNMENT FORMATS. Forms to be supplied as Government Furnished Material by (Specify)
4. TYPES OF DRAWINGS SELECTION (X one)
X a. CONTRACTOR SELECTS b. GOVERNMENT SELECTS (Specify item 9)
5. ASSOCIATED LISTS (X and complete as applicable)
a. PARTS LISTS (X one) (1) Integral (2) Separate X (3) Integral or separate
b. DATA LISTS (X one) X (1) Not required (2) Required (Specify levels of assembly)
c. INDEX LISTS (X one) X (1) Not required (2) Required (Specify levels of assembly)
d. WIRING LISTS (X one) 1) Not required X (2) Required (Specify levels of assembly)
e. INDENTURED DATA LISTS (X one)
X 1) Not required (2) Required (Specify levels of assembly)
f. APPLICATION LISTS (X one) X 1) Not required (2) Required (Specify levels of assembly)
6. DETAILS (X one)
X a. MULTIDETAIL DRAWINGS PERMITTED b. MONODETAIL DRAWINGS MANDATORY
7. VENDOR SUBSTANTIATION (X one)
X a. NOT REQUIRED b. REQUIRED
8. APPLICABILTY OF STANDARDS. The following standards apply: (X as applicable)
X a. ASME Y14.100, ENGINEERING
DRAWING PRACTICES
(COMMERCIAL)
B.x
C.x
D.x
E.x
b. ASME Y14.100 Appendices B.C.D.E
X c. ASME Y14.34M
ASSOCIATED LISTS
d. EXISTING STANDARDS DO
NOT APPLY
9. OTHER TAILORING (Attach additional sheets as necessary)
See attachments 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 to DD Form 2554-1
DD Form 2554-1, DEC 89 (ef)
ATTACHMENT 1
CONTINUATION OF DD FORM 2554-1, BLOCK 9
ADDITIONAL MATERIAL REQUIREMENTS/INSTRUCTIONS
1. Copies of the Technical Data Package (TDP) to support reviews and audits shall be the least costly media that meets the stated requirements. Alternate proposals that would satisfy this requirement may be submitted for consideration/approval to OC-ALC/ENSDAA. Paper media review requirements shall be satisfied when TDP documents are provided in digitized format through remote and/or local access terminals from contractor files. Training and assistance shall be provided to government personnel accessing digital TDP documents. TDP documents prepared by automated equipment, i.e., Computer Aided Design (CAD), may contain printed names in the title block in lieu of signatures, providing the signatures of the approving officials are recorded on an engineering document release record. Approval indicators may also be used if applied by a Digital Approval System which shall satisfy the contracting activity requirements for uniqueness, verifiability and sole control.
2. Each TDP document delivered shall be identified with Weapons System Code 404L. This code shall be entered in each TDP document, the shipping list, and the DD Form 250 accompanying each digital TDP delivery.
3. 3D Solid Models and 2D data based on 3D Models shall be delivered in accordance with MIL-DTL-31000C, Air Force Drawing 9835015, Rev E, and ISO 10303 (STEP).
4. Classified Data shall be delivered digitally on ISO-10149 compliant Compact Disk (CD).
CD's bearing classified information must be marked with the highest level of classification stored on it as well as any special control notices that apply to the information using one of the labels specified in DODD 5200.1. The label may be affixed to the sleeve or container in which the CD is stored.
5. Acceptance test procedures shall be provided to verify proper performance of separately procurable circuit cards, wiring harnesses and cable assemblies, modules, and other items which perform an electronic or electromechanical function. Whenever economically feasible with respect to the government's life cycle use of the item and requirement to compete spare parts, the procedures will test the unit independently of its next higher assembly. When possible, standard test equipment and methods shall be specified.
6. Acceptance test procedures that require special test fixtures will provide sufficient description in company format to fabricate the test fixtures.
7. Other TDP documentation requirements imposed by the following specifications, standards or work tasks by the contract or order shall be applied to or referenced on the applicable TDP documents.
8. MIL-STD-130. TDP elements for materiel subject to MIL-STD-130 marking shall specify the marking method, location, and content in accordance with the specific item marking requirements based on criteria provided in the current edition of MIL-STD-130. For materiel subject to the marking requirements of other specifications or standards, the TDP elements shall specify the marking method, location, and content of those requirements.
9. When Portable Document Files PDF files are required, they shall be in accordance with AF Drawing 9835015 Rev E.
10. Selected item drawings are required for all items and assemblies that require the application of Environmental Stress Screening (ESS) selection criteria to meet system requirements. The TDP element shall define, directly or by reference, the ESS selection criteria applied to the item or assembly identified.
11. Incoming ESS inspection procedures used on materiel/items which do not require selected item drawing delineation shall be required directly or by reference on the TDP element identifying that materiel/item.
12. Any ESS utilized during manufacturing/production in addition to the selected item ESS or incoming inspection criteria, shall be required either directly or by reference on applicable TDP documents.
13. Existing multi-detail drawings and associated lists developed using contractors standard drawing practices may be acceptable when the contractors drawing practice provides traceability of part number designations to the drawing on which it is defined. The CAGE Code, TDP Document Number, and Part Number for an item depicted on a new or existing document shall meet the requirements of ASME Y14.100, Chapter 6 and Appendix D. Parts Lists are required for each assembled item. Drawings, associated lists, and other engineering data shall be such that their intent and interpretation are clear and unambiguous.
14. Government and Industry Association (ANSI, ASME ISO, etc) documents shall not be submitted.
15. Except as stated herein, use of drawing types and lists not specified in ASME Y14.100 and ASME Y14.24 require government approval prior to selection. When required to document the item design, the drawing types in ASME Y14.100 and ASME Y14.24, as applicable shall be incorporated in the TDPs.
16. Modification Drawing. Modification drawings shall be used only for their intended purpose, which is to show how to modify delivered items, assemblies, installations, or systems.
Modification drawing information shall be incorporated into TDP design documentation by means of revision.
17. Control Drawings. Unlimited rights control drawings (vendor item control or source control) or unlimited rights company standards meeting the form, fit, function, and performance requirements for control drawings shall be provided for commercial items whenever the vendor items are non-reparable or determined non-reparable by government provisioning. (See MIL- DTL-31000C for definition of “commercial item”). Control drawings are not required for the commercial item when government provisioning has determined the item to be reparable. In the latter case, the vendor drawings are required for delivery to the government.
18. Vendor Item Control Drawings. Vendor Item Control Drawings, when selected in lieu of or in addition to control drawings for repairable commercial items, shall provide sufficient information to permit Government maintenance and modification of the items.
19. Tube Bend Drawings. Tube bend drawings shall contain the elements of data required by ASME Y14.24 using the X, Y, Z coordinate system for the establishment of the endpoints and centerline intersections. The columnar systems of MIL-D-9898C and ASME Y14.24 shall not be used, but may be used as supplementary reference information.
20. Altered item drawings additionally require that data be provided for the items which are to be altered.
21. Interchangeability Control Part Numbers shall be established to control, under a single control number, interchangeable source control part numbers under the following conditions.
This number is used to select from source control part number candidates those items which have been qualified for use in specific applications. The number is cited in parts lists in lieu of the source control part numbers. It does not re-identify source control part numbers. When this system is used, each source control part number has but one approved vendor and vendor design.
22. Repairable Source Control Part Numbers. An Interchangeability Control Part Number shall be used to identify, under a single control number, two or more repairable source control part numbers used interchangeably in a specific application. The Interchangeability Control part number will be cited in parts lists.
23. Source Control Part Numbers on Aerospace Propulsion Systems. On Aerospace Propulsion System applications, an Interchangeability Control Part Number shall be used to select and identify, from two or more possible candidates, specific source control part numbers which are approved for the application cited by the Interchangeability Control Drawing.
24. Company standards and specifications selected in accordance with the cancelled MIL- STD-970 may be acceptable but shall not be prepared in lieu of control drawings required in accordance with ASME Y14.24.
25. Standardized Microcircuit Drawings (SMDs) to the extent specified by the Parts Control Program and as directed by the Military Parts Control Advisory Group (MPCAG) (see MIL- HDBK-780) are required for microcircuits.
26. Product drawings (non-modification and non-installation) are required to define end items.
27. Impacted production installation drawings shall be revised to contain ECP traceability notes and prior ECPs.
28. Impacted production detail and assembly drawings shall be revised to include prior changes to reflect delivered item configuration.
29. Duplicate data should not be submitted when a current issue of a TDP document, meeting the requirements herein, has been previously submitted as the result of a government contract to the repository at Tinker AFB, unless requested by OC-ALC/ENSDAA. When a document of current issue indicates limited rights and the previous issue indicated unlimited rights, both issues shall be submitted.
30. Engineering data covered by this CDRL must be, or have been, delivered to the Air Force engineering data repository (OC-ALC/ENSDAA) at Tinker AFB, OK. Engineering data delivered to any other destination does not satisfy the requirement for delivery to a repository under this CDRL. For example, copies of drawings sent to engineering offices or placed in Time Compliance Technical Order (TCTO) hardware kits and sent to a government destination do not satisfy the repository delivery requirements of this CDRL. Conversely, unless otherwise specified, delivery of engineering data to an Air Force repository would not satisfy a required task of placing drawing copies in the TCTO kit or delivery to another location.
31. Unless otherwise specified in the contract, all engineering data shall be prepared in the English language in accordance with FAR 52.214-34
33. Sequencing. Regardless of media, delivered engineering data documents shall be in numerical drawing or document sequence and all images for each drawing or document shall be in drawing sheet sequence. The contractor shall sequence complete drawings as well as their accompanying documents and associated lists together on a single disk in alphanumeric sequence. The leading edge of the documents shall start with sheet 1 in sequentially numbered sheets or pages with the title block being the first frame of each document. Engineering drawing sheets requiring multiple image representation shall have the image that contains the title block appear first with successive images appearing in order until the opposite end of the drawing sheet is represented. Multi frame sheets shall be prepared with all frames the same size. There shall be a 4” minimum overlap. This same sequencing requirement applies for multiple CD delivery on the same shipment from the first CD to the last CD.
34. Multi-sheet documents shall be prepared with all sheets the same size.
35. For newly prepared documents, only one document number shall appear in the document number block.
36. Sheet Numbering: The first sheet shall state the total number of sheets in accordance with ASME Y14.1, Figure 10 (Sheet 1 of 3, for documents having 3 total sheets). "Pages of sheets" or "sheets of pages" are not permitted for newly developed data.
37. Zone Numbers: Formats, except for A and B size drawings, shall include zones for reference purposes. For A and B size drawings, zoning shall be optional. Zones shall be indicated by alphabetical and numerical entries in format margins as well as by sub-divisions or multiples thereof.
a. Zones shall be sequentially numbered with each sheet, i.e., sht 1 zones 1-8, sht 2 zones 9-16, sht 3 zones 17-24, etc.
b. Zone sizes shall be equal, and no less than 1 inch and no more than 5.5 inches.
38. Engineering data delivered to the government repositories as final delivery shall have all outstanding changes incorporated into the data.
39. Each engineering data document shall be marked with its Department Of Defense (DOD) Distribution Statement and, when applicable, appropriate documents shall also be marked with the DOD Rights in Data information or other legends/information such as contract numbers that are applicable to the document. If not preprinted, these statements and legends can be machine printed, hand stamped or applied by the overlay method. The words shall be placed in an open area of each document or each segment for documents that require multi-frame filming.
40. Application Data: Application data with “Next Assembly” and “Used On” columns are required for drawings whose detail part or assembly depicted thereon is for an element of a larger item. The Next Assembly (“NEXT ASSY”) column shall show the drawing numbers(s) of the next higher assembly to which the drawing applies. The Used On (“USED ON”) column shall show the model number or equivalent designator of the assembled unit(s) of which the part is an element. Application Data is not required for source control drawings, specification control drawings, vendor item control drawings, company standards, and commercial products (as defined by MIL-DTL-31000). The Application Data shall be located near the Title Block on sheet 1, or placed on a separate reference document, or provided on a separate parts list. When the application data appears on a separate referenced document, a cross reference note shall be included on each parent drawing to indicate that a separate referenced document is available.
When application data is included on a separate Parts List, the note required by ASME Y14.34M shall be expanded to read “SEE SEPARATE PARTS LIST FOR PARTS AND APPLICATION
DATA”.
41. Interconnection diagrams are required for wiring harnesses and cable assemblies, except for coaxial cable assemblies
42. Section lining for cut surfaces is required and shall be in accordance with ASME Y14.2.
43. Drawings which contain statements for items such as “Government Furnished Property” or “Government Furnished Equipment” must also include the contract which provided the property or equipment to the contractor, such as “Government Furnished Property under F34601-99-x-xxxx.”
44. Warranty Statements. When required by the contract or purchase order, warranty statements shall be affixed to or entered on each drawing. The statement shall not obliterate nor obscure information on the field of the drawing. The warranty statement shall specify the warranty period and include the contractor or agency that shall correct or repair the deficiency.
Warranty statements entered on TDP documents shall contain, as a minimum, the following information:
a. Warranted item until (Enter warranty expiration date YYMMDD format).
b. Contract number. (Enter the contract number that invokes warranty of TDP documents).
c. Deficiencies in this TDP document shall be corrected by (Enter the contractor and address of the agency that shall correct the deficiency)
45. When required by the contract or purchase order, legends or statements shall be affixed to or entered on each applicable TDP document. Legends shall not obliterate nor obscure information on the field of the drawing.
a General Marking Instructions: The contractor, its subcontractors or suppliers, shall conspicuously and legibly mark the appropriate legend on all technical data that qualify for such markings. The authorized legends shall be placed on the transmittal document or storage container and, for printed material, each page of the printed material containing technical data for which restrictions are asserted. When only portions of a page of printed material are subject to the asserted restrictions, such portions shall be identified by circling, underscoring, with a note or other appropriate identifier. Technical data transmitted directly from one computer or computer terminal to another shall contain a notice of asserted restrictions. Reproductions of technical data or any portions thereof subject to asserted restrictions shall also reproduce the asserted restrictions.
b. The following legends are authorized under this contract:
1. Government Purpose Rights legend
2. Limited Rights legend
3. Special License Rights legend
4. Notice of Copyright as prescribed by 17 USC 401 or 402
Attachment 2 Continuation of DD Form 2554-1, Block 9
MIL-DTL-31000C
TECHNICAL DATA PACKAGES
Each section of MIL-DTL-31000C is applicable and as tailored by the following:
1. Para 3.1. Delete 2nd sentence in its entirety.
2. Para 3.2.1. Insert "United States" before "Government" and "United States Industrial Association" before "non-Government" in the title.
3. Para 3.2.2.1. Add "United States Industrial Association" before "non-Government" in the title and 2nd line.
4. Delete Para 3.2.3.h (1) in it’s entirety and add new Para 3.2.3.h.(1) “When an existing TDP document at the same revision level has been provided to the specified United States Government repository on the CDRL in response to an earlier contract, it should not be resubmitted.”
5. Delete Para 3.2.3.h (2) in its entirety and add new Para 3.2.3.h (2) "When existing TDP elements require revision to include information applicable to the contract end item, and otherwise meets the requirements of this specification, changes to the existing TDP documents may be made utilizing the same guidelines in effect when the TDP document was originally prepared."
6. Add new Para 3.2.3.i. "When an existing TDP document is redrawn to meet the requirements of the contract, it shall be redrawn to meet the current requirements for preparation."
7. Delete Para 3.2.3.2 in its entirety. Add new Para 3.2.3.2. "Other Contractual Tasks. When other specifications or contract tasks in the contract or purchase order require development or entry of information on TDP documents, the contractor shall incorporate such information on TDP documents."
8. Para 3.5. Add “contractors Cage Code “ between “contractor” and “and contract number”.
9. Para 3.6.2.3. Delete last sentence and replace with "Product Drawings/Models and Associated Lists shall reflect the end product baseline configuration approved by the United States Government."
10. Add new Para 3.12. "Clarity and Unambiguity. Drawing practices and symbols used (including the use of legends/explanations for non-standard symbols) are such that their intent and interpretation are clear and unambiguous."
11. Add new Para 3.13. "Test and Acceptance Information. TDP documents shall provide the information required to test, accept and verify quality assurance requirements to the level specified in the contract or order."
12. Para 6.4.3. Re-write Para 6.4.3 to say “Basic engineering drawing practices for commercial applications are invoked through reference to ASME Y14.100. For other than commercial applications such as DoD design activities, reference must be made to ASME Y14.100 and associated Appendices B through E as applicable”.
13. Delete Appendix A.
ATTACHMENT 3
ASME Y14.100-2004 & Appendices B,C,D,E
Engineering Drawing Practices
Each section of ASME Y14.100 and Appendices B, C, D, E is applicable and as tailored by the following:
1. SCOPE. Para 1.1 Change paragraph to read “This standard and Appendices B, C, D and E establish the essential requirements and reference documents applicable to the preparation and revision of engineering drawings and associated lists. Past versions of MIL/DOD-STD-100 and previous editions of ASME Y14.100, which were contractually invoked for the delivery of drawings shall continue to apply.”
2. Paragraph 4.5.1 Add “if required.” after ASME Y14.1M. Add as new sentence, “Metric dimensioning is applicable only when interfacing with existing items that were dimensioned in metric.
When metric dimensioning is required, the drawings shall define the interface in metric accompanied by a parenthetical decimal inch dimension.”
3. Paragraph 4.19 Graphic Symbols, Designations, Letter Symbols, and Abbreviations. Add as new sentence after sentence one, “When applicable, Section Line representation shall be depicted on drawings.”
4. Non-Mandatory Appendix A. Delete Non-mandatory Appendix A “Tailoring”.
5. Appendix B, Paragraph B5.2, Digital Data. Add new sentence, “All pertinent drawing information required shall be inside the drawing border. Lettering less than 5/32 inches or metric equivalent is not allowed. Use of lettering less than 5/32 inches or metric equivalent requires approval by the government acquiring activity”.
6. Appendix B, Paragraph B5.2, Digital Data. Add new sub-paragraph B5.2.1, “Documents extracted from Computer Aided Design (CAD) platforms or scanned into raster images, shall meet thick and thin line convention density criteria recommended in Figure 1, ANSI Y14.2 (Thick line - 0.032 inches: Thin line - 0.016 inches).”
7. Appendix B, Change existing paragraph B5.2.1 Plotters to “B5.2.2 Plotters”.
8. Appendix B, Paragraph B7, Printed Board Assemblies. After last sentence add, “Printed wiring assembly drawings shall contain a note that specifies the item shall be manufactured in accordance with MIL-PRF-31032.”
9. Appendix B, Add new Paragraph B9, “Zoning. Except for A, A4, B, C or D size Drawings, zoning references shall be used and shall be reflected in the revision block.”
10. Appendix B, Change existing paragraph B9, Types and Applications of Engineering Drawings to “B10, Types and Applications of Engineering Drawings”.
11. Appendix B, Change existing paragraph B9.1 Standardized Microcircuit Drawing (SMD) to “B10.1 Standardized Microcircuit Drawing (SMD)”.
Attachment 4
REV E E D E E D E E D D C C C E C E E E
SHEET 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Added 5 pages of text to include additional
DATE
3/16/1998
3/29/2000
Air Force Drawing 9835015 Rev E
A
B
DESCRIPTION
Added text & tables for clarification per ECO
98C0039
Application
USED ON
REVISIONS
APPROVED
SCALE
None
AF CODE INDENT NO.
98748
REV
E
SIZE
A
DRAWING NO.
9835015
SHEET
U. S. AIR FORCE
TINKER AFB, Oklahoma
TITLE
DIGITAL DATA DELIVERY
Requirements Guideline
Distribution Statement A. Approved for public release; distribution is unlimited
CHECKER
Frank Maschino 12/13/05
REV
SHEETS
REV
SHEETS
REV STATUS
OF SHEETS
UNLESS OTHERWISE SPECIFIED
DIMENSIONS ARE IN INCHES
TOLERANCES ON
FRACTIONS DECIMALS ANGLES
PROJECT AUTHORITY
William Buchanan 12/13/05
RELEASE AUTHROITY
Barry Monroe 12/13/05
SIGNATURES ARE ON FILE IN 448 MSUG/GBMUEM
APPROVALS DATE
TREATMENT
None
FINISH
None
NEXT ASSY LTR
DRAFTSMAN
Leonard Davis 12/13/05
CHECKER
Bruce Schmitt 12/13/05 information per ECO 2000A0008
Reformatted & changed text for clarification
Changed/added text for clarification and information per ECO 2004A0003
Updated drawing to includeupdated technical language & processes per ECO 2005A0045
C D
E
5/9/2002
1/13/2004
12/13/2005
SCALE
None
REV E SHEET
1.0 Introduction
1.1 Purpose
The purpose of this document is to identify the delivery package requirements necessary to acquire compatibly formatted digital engineering data to JEDMCS repositories which use software release 3.5
1.2 Scope
This document addresses the mandatory requirements for a delivery package of engineering data that will ensure successful loading, indexing, access and retrieval of data with the initial operational and accepted JEDMICS issued suite of hardware and software for the Air Force. This document does not address the acquisition of data formats outside of the capabilities inherent to this version of JEDMICS hardware and software; nor is this document all-inclusive in its instruction for delivering data to JEDMICS.
The contractor must refer to the contract and the referenced documents for complete requirements.
1.3 Background
1.3.1 JEDMICS 3.5 Capabilities
JEDMICS release 3.5 is the operating version of JEDMICS for the Air Force. It supports the delivery of digital images in multiple formats. The standard JEDMICS viewers and output devices support the C4 format. All other formats rely on separate software resident on the user’s personal computer or workstation for viewing or printing.
2.0 References
2.1 General.
The documents listed in this section are needed to meet the requirements defined in this specification.
While every effort has been made to ensure the completeness of this list, document users are cautioned that they shall meet all requirements specified in this specification, whether or not they are listed in this paragraph.
2.2 Specifications.
The following specifications form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those listed in the issue of the Department of Defense Index of Specifications and Standards (DODISS) and supplement thereto, cited in the solicitation.
- International Standards Organization Publication (ISO-9660) Information Processing - Volume and File Structure of CD-ROM for Information Interchange, September 1988;
- International Standards Organization Publication (ISO 10149) Information Technology - Data Interchange on Read-Only 120 mm Optical Data Disks (CD-ROM), 1989 Office of the Secretary of Defense.
- MIL-HDBK-59, Department of Defense Continuous Acquisition and Life-Cycle Support (CALS) Program Implementation Guide, September 1991.
- DOD MIL-PRF-28002C, Military Specification, Requirements for Raster Graphics Representation in Binary Format,
- Department of Defense Directive 5230.24, Distribution Statements on Technical Documents dated 18 March 1987.
- MIL-HDBK-331 - Directory of DOD Engineering Data Repositories
SIZE
A
AF CODE IDENT NO.
98748
DRAWING NO.
9835015
Rev
D
SHEET
ANSI Y14.1 - Drawing Sheet Size and Format
ANSI Y14.2 - Line Conventions and Lettering
ANSI Y14.5 - Dimensioning and Tolerancing
(Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from the Defense Printing Service, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094).
2.3 Order of Precedence.
In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained and approved by the contractor, contracting officer, and repository POC.
3.0 Media.
3.1. Compact Disk Physical Media.
The data transmitted shall be on compact disk (CD). The compact disk media shall be compliant with ISO- 10149, ISO-9660, directory naming, file naming and data structure requirements provided herein. The contractor, contracting officer, and repository POC shall agree to the location, arrangement, or other structuring of transfer packages on the medium in writing prior to any delivery of data.
3.2 Compact disk directory and file structure.
3.2.1 Directory and file names.
The CD media file naming, file types, and file structure shall be implemented IAW ISO-9660 and data requirements contained herein. Constraints imposed by ISO-9660 include:
a. A directory name shall not exceed 8 characters.
b. File names shall not exceed 8 characters with a 3-character suffix.
c. The number of nested sub-directories shall not exceed 8.
d. The compact disk media shall contain only one directory structure session.
3.2.2. Volume Identifier File.
Each compact disk media shall contain a Volume Identifier File named VOLUMEID.TXT located at the root level of the file structure. The file shall contain, as a minimum, the Sender_Activity, sender Point of Contact (POC) fields, Security Classification and Distribution_Restrictions field. The Security_Classification and Distribution_Restrictions fields shall contain the highest restriction of the data contained on the CD media.
This file shall contain basic identification information in the sample format shown in APPENDIX A. Volume Identifier File (VOLUMEID.TXT) Sample.
3.2.3. Optional Summary Report File.
A typical exchange of engineering data includes a summary report that provides general information concerning the data delivered. At the option of the data provider, this information may be included in digital format on the compact disk media. If provided in digital format, the summary report shall be provided as an ASCI Text file named SUMMARY.TXT located in the root directory of the media.
SIZE
A
AF CODE IDENT NO.
98748
Rev
E
SHEET
3.3. Alternative Media.
Other physical media, which support a hierarchical data file structure, may be used by mutual written agreement between the contractor, contracting officer, and repository Point of Contact (POC). Other alternative mechanisms for automated data exchange, such as Electronic Data Interchange (EDI), may be used by mutual written agreement between the contractor, contracting officer, and repository POC.
Contractor deliveries shall be validated as to their ability to deliver said media. The Contractor is responsible for the performance of all inspection requirements as specified herein.
4.0 Metadata / Index Data
4.1. General Information.
For purposes of this document, the term metadata is used to describe the set of identification information (i.e. index data), which identifies a binary data file. In previous media used for the exchange of engineering drawings, index data was provided on aperture cards as hollerith punch codes, or was provided as a character string in the raster image header block of magnetic tape files. These methods are outdated technology for exchange of many types of engineering data. Therefore the requirements that follow provide for the exchange of metadata in a delimited text file suitable for all binary data types.
4.2. Metadata File.
Each compact disk media shall contain a metadata file with filename of INDEX.DLF. The metadata file shall be located at the root level of the file structure. The metadata file shall contain one metadata record entry for each binary data file contained on the media. Each file, except PDF and C4 Raster, shall be placed in its own folder and each folder shall have its own .DLF file.
4.3. Metadata Record.
The values of the data fields in the metadata record are used to populate the government’s JEDMICS system database. The Metadata Record format shall be provided as described in APPENDIX B, JEDMICS Data Format Interface Specification (DFIS). All data fields marked with an “X” in the column labeled “Required/Notes” are required input data and shall be provided.
4.3.1 Usage of Special Characters.
The single quote "'", percent "%", underbar "_", dollar sign "$", pound sign “#”, asterisk “*” pipe “|”, and exclamation "!" characters shall not be used in any Data Element fields except for Data Elements 20 (Filename), 21 (File Extension), 22 (File Path), and 23 (Media Volume ID) where underbar “_” is a valid character. The pipe character “|” is used as a field delimiter and shall not be used for a value in any field.
4.3.2 Binary data file names.
Each binary data file shall be identified by a unique file name.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .