Data_Requirements.pdf

CONTRACT DATA REQUIREMENTS LIST Form Approved (1 Data Item) 0MB No. 0704-0188

Th• public reporting burden for this collK:tion of information is estimated to av•rag• 110 hours per response , including the time for reviewing instructions, searching existing data !iources, gathering and maintaining the data nNded, and completing and reviewing the collection of tnformation. Send comments regarding this burden estimate or any other aspect of this eoftection of information, including suggestions for reducing the burden, to th• Department of Defense. Executive Services and Communications Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid 0MB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Offk:er for the Contract/PR No, listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

tJutJt A(FY 18) TOP TM X OTHER --- - -

D. SYSTEM/ITEM IE. CONTRACT/PR NO. F.CONTRACTOR

Automated High Vacuum Gauge System

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3 . SUBTITLE

AOOl Technical Manual Contract Requirements (TMCR) and associated suoolemental data

4. AUTHORITY (Data Acquisition Document No.J 15. CONTRACT REFERENCE 6 . REQUIRING OFFICE

TM 86-0lQ PD 18M-888A-VA Atch AFLCMC/WNMEM 7 . DO 250 REQ 9 . DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

NIA

REQUIRED ASREQ SeeBLK 16 b. COPIES

8. APP CODE 11 . AS OF DATE 13. DATE OF SUBSEQUENT a. ADDRESSEE Finel

NIA D

ASREQ

SUBMISSION Draft See BLK 16 Reg Aepro

18. REMARKS

BLK 9: BLK: 8: 90 days after contract award a copy of the Draft Manual is due. l.AFMETCAL

The Government has 30 calendar days to review the preliminary draft. The Attn: Mike Hickey contractor has IO calendar days after receipt of Government comments to prepare I 3 Irving-Wick Drive W and deliver revised data. Criteria for approval shall meet the Government Horton Building comments. Reference the contract number in all correspondence. Final approval Heath, Ohio 43056 I after first production acceptance.

Blk 12: No later than 180 days after contract award, I copy(ies) of the final manual is(are) required on CD/DVD in indexed Portable Document Format (iPDF). Ship to addressee #1 listed in BLK 14a. If manuals are available

Ship with Unit 1 electronically, the file or web link may be sent to michael.hickey.2@us.af.mi1.

Reference contract number in all correspondence.

I

15. TOTAL I I 0

G. PREPARED BY H. DATE I. APPROVED BY J . DATE

CAPUANO.FRAN ·OigitaUy signed by SKINNER.KEVIN ~~=t~~u, 102,22122 1125118 CAPUANO.FRANK.R.140320965 l/24/18 K.R.1403209658 • .L.11.1024227223 L., 201 , nm •?·«·M .ns•nn• Date: 2018.01.2410:11:l:<46..05'00'

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 1 of 3 Pages

I i

I I I

I I I

I

I I

I I

I

I

I

I

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

CONTRACT DATA REQUIREMENTS LIST Form Approved (2 Data Items} 0MB No. 0704-0188

The public r-s,orting burden for th is collection of inform ation is estimate d to average 220 hours per response, including the t ime for reviewing instructions, searching existing data sources, gathering and mainta ining the data needed, and completing and reviewing the collection of information. Send comments regard ing th is burden estimate or any other aspect of this collection of Information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communica~ions Directorate (0 704·0188). Respondent s should be aware that notwithst anding any other provision of law, no person shall be subject to any penatty for failing to comply with a collection of ihformation if i1 does not display a currently valid 0MB control number. Plaasa do not return your form to the above organization. Send completed form to the Government l•tuing Contracting Officer for the Contract/PR No. listed in Block J:.

A. CONTRACT LINE ITEM NO. 8 . EXHIBIT C. CATEGORY:

/J11t1l A(FYl8) TOP TM ~ OTHER

D. SYSTEM/ITEM l E. CONTRACT/PR NO. F. CONTRACTOR

Automated High Vacuum Gauge System

1. DATA ITEM NO. 2 . TITLE OF DATA ITEM 3 . SUBTITLE

A002 Software User Manual (SUM)

4 . AUTHORITY (Data Acquisition Document No.) f 6 . CONTRACT REFERENCE 6. REQUIRING OFFICE

DI-IPSC-81443A PD I 8M-888A-V A Atch AFLCMC/WNMEM

7. DD 250 REQ 9 . DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISffllBUTION

NIA REQUIRED ASREQ See BLK 16 b . COPIES

8 . APP CODE D 11 . AS OF DATE 13. DATE OF SUBSEQUENT a. ADDRESSEE Final

NIA ASREQ sueTeb~LK 16 Draft Reg Repro

16. REMARKS

Blk 13: Concurrent with delivery of production unit contractor shall furnish and Shi11 with_ unit l pack I set of the manuals with each unit. Manual shall be on CD/DVD in indexed Portable Document Format (iPDF). Ship with unit.

15. TOTAL 0 I 0

1. DATA ITEM NO. 2 . TITLE OF DATA ITEM J . SUBTITLE

A003 Product Drawings

4 . AUTHORtTY (Data Acquisition Document No. ) , 5 . CONTRACT REFERENCE 6 . REQUIRING OFFI CE

DI-SESS-81000E PD 18M-888A-VA Atch AFLCMC/WNMEM

7. DD 250 REQ 9 . DIST STATEMENT 10 . FREQUENCY 12. DATE OF FIRST SUBMISSION 14 . DISTRIBUTION

NIA

REQUIRED

ASREQ See BLK 16 b . COPIES

8 . APP CODE D 11 . AS OF DATE 13. DATE OF SUBSEQUENT a. ADDRESSEE Final

NIA

SUBMISSION Draft

ASREQ See BLK 16 Reg Repro

16 . REMARKS

Blk 13: Concurrent with delivery of production unit contractor shall furnish and Ship with unit I tpack I set of the Drawings with each unit. Manual shall be on CD/DVD in indexed Portable Document Format (iPDF). Ship with unit.

16 . TOTA L - 0 I 0

G. PREPARED BY Oq,1a11y . by H. DATE I. APPROVED BY J. DATE

CAPUANO.FRAN _CA;,,, ... ~~K.R.140320965 SKINNER.KEVIN ~=~'~'\" 102,22122

K. R .1403209658 • 1/2412018 1/25/18 Date· 20 18.01 .2'4 10:23.50-05"00' .L.1 1.1024227223 ~"2!l18D1.2509:56:12-05'00'

DD FORM 1423-2, AUG 96 PREVIOUS EDITION MAY BE USED. Page L of _i Pages

I I

I i

I

I

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

17. PRICE GROUP

CONTRACT DAT A REQUIREMENTS LIST Form Approved (2 Data Items} 0MB No. 0704-0188

Th• public reporting burden for this collection of information is estimated to average 220 hours per response, inc luding the time for reviewing instructions, searching existing

~::, s~~;~~~· ::1~~"!0T,~t::;~j~:1?~7~,!:ti:~~a ;~~~~~g ':U~~~~~"?o:~!r:'t~;i~~. t~d~~~c!~" ~ j~:::r:!:~t :,eo~fe°n~:°~!~;~~~:di~:!~!:u;:" c4::!:~~c~,::

Directorate (0704-0188). Raspondents should be aware that notwithstanding any other provision of law , no person :s.hall b• sub;rtct to any penalty for failing to comply with• collection of information if it does not d;splay a currently valid 0MB control number. Pie ... do not retum your form to th• above organiz.ation. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No . Hated in Block E.

A. CONTRACT LINE ITEM NO. 8. EXHIBIT C. CATEGORY:

tJtJtJZ, A(FY18) TCP --- TM~ OTHER

D. SYSTEM/ITEM IE. CONTRACT/PR NO. F. CONTRACTOR

Automated High Vacuum Gauge System

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3 . SUBTITLE

A004 Software Test Plan

4 . AUTHORITY {Data Acquisition Document No.) , 6. CONTRACT REFERENCE 6. REQUIRING OFFICE

D1-IPSC-8 l 438A PD l 8M-888A-V A Atch AFLCMC/WNMEM

7. DD 250 REQ 9 . DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

NIA REQUIRED

ASREQ See BLK 16 b . COPIES

8. APP CODE D 11 . AS OF DATE 13. DATE OF SUBSEQI./ENT a. ADDRESSEE Final

NIA ASREQ SUB~J~

0fkK 16 Draft

~"'1' ~

16. REMARKS

Blk 13: Concurrent with delivery of production unit contractor shall furnish and Ship with unit I pack I set of Test Plans with each unit. Test Plans shall be on CD/DVD in indexed Portable Document Format (iPDF) . Ship with unit.

15. TOTAL 0 1 0

1. DATA ITEM NO. 2 . TITLE OF DATA ITEM 3 . SUBTITLE

A005 Software Test Report

4 . AUTHORITY (Data Acqu;sition Document No.) 15. CONTRACT REFERENCE 6 . REQUIRING OFFICE

DI-IPSC-8 I 440A PD 18M-888A-VA Atch AFLCMC/WNMEM

7. DD 250 REQ 9 . DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

REQUIRED

NIA ASREQ See BLK 16 b. COPIES

8 , APP CODE D 11. AS OF DATE 13. OATE OF SUBSEQUENT a. ADDRESSEE Final SUBMISSION Draft NIA ASREQ See BLK 16 Reg Repro

16. REMARKS

Blk 13: Concurrent with delivery of production unit contractor shall furnish and Ship with unit I pack I set of the Software Test Reports with each unit. Software Test Reports shall be on CD/DVD in indexed Portable Document Format (iPDF). Ship with unit.

15. TOTAL 0 I 0

G. PREPARED BY H. DATE

I. 'Mt~V~~~ 0 ,., . -, by

J . DATE

CAPUANO.FRAN =~-';"'~K.R.140320965 K N • EVIN . ~ ~ ~EVIN L.l/102'22722

K.R.1403209658 ' . 112412018 .L.11 .1024227223 ;3,.,.,2016 01.2509:so·:ie-<>S'Da 1/25118 Data: 2018 01 24 10;26-25-0!'00'

DD FORM 1423-2, AUG 96 PREVIOUS EDITION MAY BE USED. Page L of ___3_ Pages

I

I

I

I

I

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

17. PRICE GROUP

TM-86-0lQ 27 Oct 2017 1-01: AF TMSS Linear TMs

Air Force Technical Manual Contract Requirements (TMCR) for

AIR FORCE CALIBRATION AND METROLOGY (AFMETCAL) PROGRAM

AFPSL-Automated High Vacuum Gauge System

ATTACHMENT DD FORM 1423, TO CORL SEQUENCE NUMBER 001, EXHIBIT A REQUEST FOR

PROPOSAUCONTRACT:

Date: 30 May 2018

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS

1. TMCR Tailoring. This TMCR has been tailored by the program office, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). The Contractor may propose and submit, in writing, additional tailoring to the Technical Order Manager Agency/ Agent (TOMA), Government Program Manager (PM), and Procuring Contracting Officer (PCO) for consideration. The tailored TMCR shall be attached to the Contract Data Requirements List (CDRL) for Technical Order (TO) delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal Statement Of Work (SOW). Air Force (AF) TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3 , AF Technical Order Life Cycle Management, located at http://www.tinker.af.mil/Home/TechnicalOrders.aspx. A copy may also be obtained from the Program TO Manager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope. The Contractor shall develop and deliver technical manuals in accordance with (IA W) this TMCR that supports the AFMETCAL requirements for technically usable manuals. The technical manuals will include Operation and Maintenance Instructions, Illustrated Parts Breakdown, and Calibration Process/Procedure in a Portable Document Format (PDF). PDF TO Publications may be produced and distributed as physical media (Paper/CD) or electronically via Enhanced Technical Information Management System (ETIMS) electronic TO Viewer ( eTOV).

3. Commercial Manuals. Contractors shall recommend the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. All proposed commercial manuals are subject to Government review and approval. Contractors shall use Data Item Description (DID) DI-TMSS-80067C, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CF AEICFE) Notices, to provide recommendation data. A copy is available through ASSIST at http://quicksearch.dla.mil/gsSearch.aspx.

3 .1. The AF requests the ability to electronically store, print, distribute, update and decollate the commercial manual to allow for printing. Commercial manuals shall be delivered as Portable Document Format (PDF) unless otherwise specified.

3.2. Approved Commercial-Off-The-Shelf (COTS) Manuals shall be delivered with an Identifying TO Publication Sheet (ITPS), IA W MIL-PRF-32216, Performance Specification: Evaluation Of Commercial Off-The-Shelf (COTS) Manuals And Preparation Of Supplemental Data. All PDF files of commercial data shall be non-password protected to allow the AF to decollate the manual for printing.

3.3. If the proposed COTS data is found to be insufficient after review by the Government, the Contractor shall prepare supplemental data for the COTS manual as required IA W Military Standard (MIL-STD)-38784. If the COTS data cannot be supplemented sufficiently the Contractor may be tasked to develop new TM data IA W the applicable TMSS listed in Section 2, Table 1.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. The contractor shall develop all TMs IA W most current version of applicable TMSS for the type manual being developed and comply with the Specification/Standard Interface Records (SIRS) provided within Section 3.

5. Subsequent TO/Data Requirements. (Deleted)

6. TO Development. TOs shall be written to a scope and depth of coverage to support the AFMETCAL operations and maintenance concepts.

6.1. Standard Generalized Markup Language (SGML) tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. All delivered graphics shall conform to the approved graphic creation and format guidelines listed in Attachment 1, Graphics Format Guidelines. For assistance with illustration requirements contact AF TMSS via (e-mail: SGMLSupport@us.af.mil).

6.2. (Deleted)

7. TO Numbering. (Deleted)

8. Data Rights. Contractors shall comply with 10 U.S.C. 2320 and cognizant Defense Federal Acquisition Regulation Supplement (DFARS) provisions and clauses in providing Unlimited Rights for all source data, TO publications, and TO updates prepared specifically for the contract. Government rights in data are specified in the DFARS, 252.227-7013, Rights in Technical Data, Noncommercial Items, 252.227- 7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, and 252.227-7015, Technical Data-Commercial Items. The Government shall be given Unlimited Rights for all Government-funded business rules (tailoring and application methods and procedures) and documented business processes developed under the contract for the purpose of TO development. For all data delivered to the Government with other than Unlimited Rights, the Contractor shall assert their data rights IAW DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions. The Contractor shall pass through and enforce all requirements in this TMCR to all sub-Contractors.

9. Classification, Distribution, Destruction, Disclosure, Export Control Notices, and Cyber Security.

Contractors shall recommend the correct markings and controls for classified and restricted distribution data and TOs IAW the program's Security Classification Guide (SCG) and Department of Defense Manual (DODM) 5200.01 , Department of Defense Instruction (DODI) 5230.24, Department of Defense Directive (DODD) 5230.25, Air Force Instruction (AFI) 16-1404, and MIL-STD-38784 (available at http://www. e-publishing. af. mil/ or https :// assist.dla.mil/ online/ start/index.cfm). The markings and notices shall be reviewed during In-Process Reviews (IPR). The Contractor shall also apply policy and procedures for Cyber Security Protection IA W AFI 33-200, Information Assurance (IA) Management, AFMAN 17-1301, Computer Security (COMPUSEC), and MPTO 00-33B-5008, Remanence Security/or Information Systems. NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.

10. TO Quality. Contractor proposals shall describe how the Government will be allowed to interact with the Contractor's TO development team. The Contractors shall ensure prepared TOs are: a) technically accurate and safe; b) written to a scope and depth of coverage to support the operations and maintenance concepts; c) properly classified and marked with export control and distribution limitation statements.

11 . TO Delivery. TO file delivery requirements are located in Section 2, Table 3 of this document.

11 .1. MIL-SPEC (SGML) Tagged Files. The Contractor shall parse all SGML files required for the TOs prior to Government delivery and shall verify the SGML is compliant with the appropriate DTD.

NOTE: The Government will parse the files prior to acceptance using the public domain SGML parser (http://www.jclark.com/sp/) .

12. Source Data Maintenance. (Deleted)

13. TO Maintenance. (Deleted)

14. Schedules. (Deleted)

15. Time Compliance Technical Orders (TCTOs). (Deleted)

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

• Mark the TM Type Selection Tables indicating the applicable TO types and related specifications.

(NEW DEVELOPMENT) LINEAR TM TYPE (PUBLICATION) SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE AFMETCAL

(AFPSL - Automated High Vacuum Gauge System)

Title or Type of Manuals

1. Inspection TOs

a. Inspection and Maintenance Requirements (-6) Manual

b. Acceptance and Functional Check Flight (FCF) Procedures (-6CF) Manual

c. Acceptance and Functional Check Flight (-6CL) Checklist

d. Inspection Workcards (-6WC)

e. Maintenance/Operations Checklists

2. Cargo Aircraft Loading and Offloading TOs

a. Loading Instructions Manual

b. Nuclear Weapon Cargo Loading Manual

c. Checklists

3. Weight and Balance (Aircraft)

a. Loading Data Manual

b. Sample Basic Weight Checklists

4. Flight Manuals

a. Flight Manual

b. Performance Data Manual

c. Mission Crew Manual

d. Supplemental Manual

e. Abbreviated Flight Crew Checklist

5. List of Applicable Publications

6. Structural Repair Manuals (for Aircraft)

7. Munitions/Weapons Loading Procedures, Non- nuclear and Nuclear TOs

a. Nuclear Weapons Basic Information and Loading Procedures

b. Nuclear Weapons Loading Procedures

c. Non-nuclear Munitions Basic Information

d. Non-nuclear Loading Procedures

e. Non-nuclear Munitions Loading Standard Data Packages (SDPs)

f. Loading Procedures Checklist

g. Single Loading Procedures Checklist

h. Integrated Loading Procedures Checklists

i. Family Group Loading Procedures Checklist j . Nuclear Weapons Loading Procedure Checklists

k. Functional Check Procedures Checklist I. NATO Stage B Cross-Servicing Checklists

m. End of Runway (EOR) Procedures Checklist

8. Space Operations and Support Documentation TOs

Specification

MIL-DTL-5096

MIL-DTL-5288

MIL-DTL-5920

MIL-DTL-7700

MIL-DTL-8031

MIL-DTL-9854

MIL-DTL-9977

Required

D

D

D D D

D D D

D D

D D D D D D D

D D D D D D D D D D D D

TABLE 1

TMSS REQUIREMENTS FOR THE AFMETCAL

(AFPSL - Automated High Vacuum Gauge System)

Title or Type of Manuals

-- MIL-SPEC (Intercontinental Ballistic Missiles) -- MIL-SPEC (Space)

a. Operations Manual

b. Operations Checklists

c. Technical Manuals and Related Checklists

9. Nuclear and Non-nuclear Weapon Delivery and Aircrew Procedures Manuals and Checklists

a. Non-nuclear Weapon Delivery Manual

b. Aircrew Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)

Specification

MIL-PRF-38311

MIL-PRF-38314

MIL-DTL-38384

c. Aircrew Nuclear Missile Delivery Manual (Strategic Bomber Aircraft)

d. Aircrew Nuclear Bomb Delivery Manual (Tactical Aircraft)

e. Non-nuclear Weapon Delivery Checklist

f. Nuclear Weapon Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew Nuclear Bomb Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

10. Work Unit Code Manual MIL-DTL-38769

Required

D D D D D

D D D D D D D D

a. Standard WUC Manual D

b. Two Chapter Manual D

____ c._T_hr_ ee_ C_h ... ap __ t_er_M_ an_u_a_l _________________________ --::D

11. Calibration Procedures MIL-DTL-38793 rz:I

12. Time Compliance Technical Orders (TCTOs) MIL-DTL-38804

a. TCTO D

b. TCTO Supplement D

13. Aircraft Battle Damage Assessment and Repair TOs MIL-DTL-87158 D--

14. Illustrated Parts Breakdown MIL-DTL-38807 rz:I

15. On-Equipment Organizational Maintenance Manual Set MIL-DTL-83495

a. General Equipment (GE) Manual

b. General System (GS) Manuals

c. Combined GE & GS Manual

d. Job Guide (JG) Manuals

e. Fault Reporting (FR) Manual

f. Fault Isolation (FI) Manual

g. Wiring Data (WD) Manual

h. Schematic Diagram (SD) Manual

D D D D D D

T ABLE 1

TMSS REQUIREMENTS FOR THE AFMETCAL

(AFPSL- Automated High Vacuum Gauge System)

Title or Type of Manuals Specification Required

16. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929

a. Maintenance Manuals

( l) Organizational Maintenance ~

(2) Intermediate Maintenance D

(3) Depot Maintenance D

(4) Combined (l&D) Maintenance D

(5) On Condition Maintenance D

b. Operation & Maintenance Instruction Manuals ~ C. Special Manuals

(1) Aircraft Engine Testing and Trending Procedures D

(2) Aircraft Power Package Testing Procedures D

(3) Static Firing of Missile Motors D

(4) System Peculiar Corrosion Control D

(5) Nondestructive Inspection (NDI) D

(6) Aircraft Structural Integrity Program (ASIP) D

(7) ATE Operator Test Procedures D

(8) Special Requirements for Storage and Maintenance Procedures; D AUR Munitions/Launchers and Associated Support Equipment, Conventional Components and CMBR Agents

(9) Parachute Packing Procedures D

(10) Operators Instructions (Hand-Held Flight Computers) D

(11) Installation-Engineering Facility (Ground C-E Equipment) D

d. Checklists (IA W MIL-DTL-5096) D

e. With Illustrated Parts Breakdown D

17. Commercial Manuals (Evaluate according to MIL-PRF-32216) ~

18. Aircraft Cross-servicing Guide MIL-DTL-22202 D

NOTES:

TABLE 3 - LINEAR TM DELIVERY REQUIREMENTS

FOR THE AFMETCAL

AFPSL - Automated High Vacuum Gauge System

• For Paper media delivery indicate required quantity

DELIVERY SCHEDULE

Event ¢Number of days data required prior Technical First Administrative to event¢ Review(s) Article/First (Logistics)

(90 DACA) Production ( Unit DAFAOK)

(180 DACA)

.JJ. Enter physical mailing address, electronic Legend: DACA-After Contract Award

Final TO Distribution (Ship With Prod Units)

DAFAOK)

delivery location or web access point .JJ. DAF AOK - Days after First Article accepted (passes Acceptance testing)

Engineering (Draft) Copy

TPDF I 1 IPDF I IPDF I !PDF I

AFLCMCIWNMRP/ AFMETCAL Division ATTN: Mike Hickey michael.hickey.2@us.af.mil 813 Irving Wick Drive West, Bldg 2 Heath, Ohio 43056 First Production Copies (ship w/1 st Prod.) !PDF I IPDF I 1 !PDF / IPDF I Bionetics Transportation ATNN: Carol Cooperrider 813 Irving Wick Drive West, Bldg 4, Door 15 Heath, Ohio 43056 Administrative (Logistics) Copies IPDF I IPDF / IPDF I IPDF I AFLCMC/WNMRP/AFMETCAL Division ATTN: Mike Hickey michael.hickey.2@us.af.mil 813 Irving Wick Drive West, Bldg 2 Heath, Ohio 43056 Final (Production) Copies (ship w/ unit) IPDF I !PDF I IPDF I IPDF I Bionetics Transportation ATNN: Carol Cooperrider 813 Irving Wick Drive West, Bldg 4, Door 15 Heath, Ohio 43056

Total Paper Copies Required: 1 1

SECTION 3. DELETED

DATA ITEM DESCRIPTION

Title: SOFTWARE USER MANUAL (SUM)

Number: DI-IPSC-81443A AMSC Number: N7378 DTIC Applicable: No Office of Primary Responsibility: N/SPAW AR Applicable Forms: NIA Use, Relationships:

Approval Date: 20000111 Limitation: N/ A GIDEP Applicable: No

The Software User Manual (SUM) tells a hands-on software user how to install and use a Computer Software Configuration Item (CSCI), a group of related CSCI's, or a software system or subsystem. It may also cover a particular aspect of software operation, such as instructions for a particular position or task.

The SUM is developed for software that is run by the user and has a user interface requiring on line user input or interpretation of displayed output. If the software is embedded in a hardware software system, user manuals or operating procedures for that system may make separate SUMs unnecessary.

This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.

This DID is used when the developer is tasked to identify and record information needed by hands-on users of software.

The SUM is an alternative to the Software Input/Output Manual (SIOM) (DI-IPSC-81445A) and Software Center Operator Manual (SCOM) (DI-IPSC-81444A).

This DID supersedes DI-IPSC-81443 .

Requirements:

1. Reference documents. None.

2. General instructions.

a. Automated techniques. Use of automated techniques is encouraged. The term "document" in this DID means a collection of data regardless of its medium.

b. Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.

DI-IPSC-81443A

3. Format. Following are the format requirements.

The specification shall be in contractor format unless otherwise specified on the Contract Data Requirements List (CDRL)(DD 1423). The CORL should specify whether deliverable data are to be delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatible with a specified word processor or other support software); may be delivered in developer format rather than in the format specified herein; and may reside in a computer-aided software engineering (CASE) or other automated tool rather than in the form of a traditional document.

4. Content. The specification shall contain the following :

a. Title page or identifier. The document shall include a title page containing, as applicable: document number; volume number; version/revision indicator; security markings or other restrictions on the handling of the document; date; document title; name, abbreviation, and any other identifier for the system, subsystem, or item to which the document applies; contract number; CDRL item number; organization for which the document has been prepared; name and address of the preparing organization; and distribution statement. For data in a database or other alternative form, this information shall be included on external and internal labels or by equivalent identification methods.

b. Table of contents and index. The document shall contain a table of contents providing the number, title, and page number of each titled paragraph, figure, table, and appendix, and an index providing an alphabetic listing of key terms and concepts covered in the document and the pages or paragraphs in which the terms or concepts are covered. For data in a database or other alternative form, this information shall consist of an internal or external table of contents containing pointers to, or instructions for accessing, each paragraph, figure, table, and appendix or their equivalents.

c. Page numbering/labeling. Each page shall contain a unique page number and display the document number, including version, volume, and date, as applicable. For data in a database or other alternative form, files, screens, or other entities shall be assigned names or numbers in such a way that desired data can be indexed and accessed.

d. Response to tailoring instructions . If a paragraph is tailored out of this DID, the resulting document shall contain the corresponding paragraph number and title, followed by "This paragraph has been tailored out." For data in a database or other alternative form, this representation need occur only in the table of contents or equivalent.

e. Multiple paragraphs and subparagraphs. Any section, paragraph, or subparagraph in this DID may be written as multiple paragraphs or subparagraphs to enhance readability.

f. Standard data descriptions . If a data description required by this DID has been published in a standard data element dictionary specified in the contract, reference to an entry in that dictionary is preferred over including the description itself.

g. Substitution of existing documents . Commercial or other existing documents may be substituted for all or part of the document if they contain the required data.

The numbers shown designate the paragraph numbers to be used in the document.

1. Scope. This section shall be divided into the following paragraphs.

1.1 Identification. This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

1.2 System overview. This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents .

1.3 Document overview. This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.

2. Referenced documents. This section shall list the number, title, revision, and date of all documents referenced in this document. This section shall also identify the source for all documents not available through normal Government stocking activities.

3. Software summary. This section shall be divided into the following paragraphs.

3.1 Software application. This paragraph shall provide a brief description of the intended uses of the software. Capabilities, operating improvements, and benefits expected from its use shall be described.

3 .2 Software inventory. This paragraph shall identify all software files, including databases and data files, that must be installed for the software to operate. The identification shall include security and privacy considerations for each file and identification of the software necessary to continue or resume operation in case of an emergency.

3.3 Software environment. This paragraph shall identify the hardware, software, manual operations, and other resources needed for a user to install and run the software. Included, as applicable, shall be identification of:

a. Computer equipment that must be present, including amount of memory needed, amount of auxiliary storage needed, and peripheral equipment such as printers and other input/output devices

b. Communications equipment that must be present

Dl-IPSC-81443A

c. Other software that must be present, such as operating systems, databases, data files, utilities, and other supporting systems

d. Forms, procedures, or other manual operations that must be present

e. Other facilities, equipment, or resources that must be present

3.4 Software organization and overview of operation. This paragraph shall provide a brief description of the organization and operation of the software from the user's point of view.

The description shall include, as applicable:

a. Logical components of the software, from the user's point of view, and an overview of the purpose/operation of each component

b. Performance characteristics that can be expected by the user, such as :

1) Types, volumes, rate of inputs accepted

2) Types, volume, accuracy, rate of outputs that the software can produce

3) Typical response time and factors that affect it

4) Typical processing time and factors that affect it

5) Limitations, such as number of events that can be tracked

6) Error rate that can be expected

7) Reliability that can be expected

c. Relationship of the functions performed by the software with interfacing systems, organizations, or positions

d. Supervisory controls that can be implemented (such as passwords) to manage the software

3. 5 Contingencies and alternate states and modes of operation. This paragraph shall explain differences in what the user will be able to do with the software at times of emergency and in various states and modes of operation, if applicable.

3.6 Security and privacy. This paragraph shall contain an overview of the security and privacy considerations associated with the software. A warning shall be included regarding making unauthorized copies of software or documents, if applicable.

3.7 Assistance and problem reporting. This paragraph shall identify points of contact and procedures to be followed to obtain assistance and report problems encountered in using the software.

4. Access to the software. This section shall contain step-by-step procedures oriented to the first time/occasional user. Enough detail shall be presented so that the user can reliably access the software before learning the details of its functional capabilities. Safety precautions, marked by WARNING or. CAUTION, shall be included where applicable.

4.1 First-time user of the software. This paragraph shall be divided into the following subparagraphs.

4. 1.1 Equipment familiarization . This paragraph shall describe the following as appropriate:

a. Procedures for turning on power and making adjustments

b. Dimensions and capabilities of the visual display screen

c. Appearance of the cursor, how to identify an active cursor if more than one cursor can appear, how to position a cursor, and how to use a cursor

d. Keyboard layout and role of different types of keys and pointing devices

e. Procedures for turning power off if special sequencing of operations is needed

4.1.2 Access control. This paragraph shall present an overview of the access and security features of the software that are visible to the user. The following items shall be included, as applicable:

a. How and from whom to obtain a password

b. How to add, delete, or change passwords under user control

c. Security and privacy considerations pertaining to the storage and marking of output reports and other media that the user will generate

4.1.3 Installation and setup. This paragraph shall describe any procedures that the user must perform to be identified or authorized to access or install software on the equipment, to perform the installation, to configure the software, to delete or overwrite former files or data, and to enter parameters for software operation.

4.2 Initiating a session. This paragraph shall provide step-by-step procedures for beginning work, including any options available. A checklist for problem determination shall be included in case difficulties are encountered.

DI-1PSC-8 l 443A

4.3 Stopping and suspending work. This paragraph shall describe how the user can cease or interrupt use of the software and how to determine whether normal termination or cessation has occurred.

5. Processing reference guide. This section shall provide the user with procedures for using the software. If procedures are complicated or extensive, additional Sections 6, 7, .. . may be added in the same paragraph structure as this section and with titles meaningful to the sections selected. The organization of the document will depend on the characteristics of the software being documented. For example, one approach is to base the sections on the organizations in which users work, their assigned positions, their work sites, or the tasks they must perform. For other software, it may be more appropriate to have Section 5 be a guide to menus, Section 6 be a guide to the command language used, and Section 7 be a guide to functions . Detailed procedures are intended to be presented in subparagraphs of paragraph 5 .3. Depending on the design of the software, the subparagraphs might be organized on a function-by-function, menu-by-menu, transaction-by-transaction, or other basis. Safety precautions, marked by WARNING or CAUTION, shall be included where applicable.

5.1 Capabilities. This paragraph shall briefly describe the interrelationships of the transactions, menus, functions, or other processes in order to provide an overview of the use of the software.

5.2 Conventions. This paragraph shall describe any conventions used by the software, such as the use of colors in displays, the use of audible alarms, the use of abbreviated vocabulary, and the use of rules for assigning names or codes.

5.3 Processing procedures. This paragraph shall explain the organization of subsequent paragraphs, e.g., by function, by menu, by screen. Any necessary order in which procedures must be accomplished shall be described.

5 .3 .x (Aspect of software use) . The title of this paragraph shall identify the function, menu, transaction, or other process being described. This paragraph shall describe and give options and examples, as applicable, of menus, graphical icons, data entry forms, user inputs, inputs from other software or hardware that may affect the software's interface with the user, outputs, diagnostic or error messages or alarms, and help facilities that can provide on-line descriptive or tutorial information. The format for presenting this information can be adapted to the particular characteristics of the software, but a consistent style of presentation shall be used, i.e., the descriptions of menus shall be consistent, the descriptions of transactions shall be consistent among themselves .

5.4 Related processing. This paragraph shall identify and describe any related batch, offline, or background processing performed by the software that is not invoked directly by the user and is not described in paragraph 5.3. Any user responsibilities to support this processing shall be specified.

D1-IPSC-8 l 443A

5.5 Data backup. This paragraph shall describe procedures for creating and retaining backup data that can be used to replace primary copies of data in event of errors, defects, malfunctions, or accidents .

5.6 Recovery from errors, malfunctions, and emergencies . This paragraph shall present detailed procedures for restart or recovery from errors or malfunctions occurring during processing and for ensuring continuity of operations in the event of emergencies.

5. 7 Messages. This paragraph shall list, or refer to an appendix that lists, all error messages, diagnostic messages, and information messages that can occur while accomplishing any of the user' s functions . The meaning of each message and the action that should be taken after each such message shall be identified and described.

5.8 Quick-reference guide. If appropriate to the software, this paragraph shall provide or reference a quick-reference card or page for using the software. This quick-reference guide shall summarize, as applicable, frequently used function keys, control sequences, formats , commands, or other aspects of software use.

6. Notes. This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document. If Section 5 has been expanded into section(s )6, .. . , this section shall be numbered as the next section following section n.

A Appendices. Appendices may be used to provide information published separately for convenience in document maintenance (e.g., charts classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling.

Appendixes shall be lettered alphabetically (A, B, etc.).

END OF D1-IPSC-81443A.

Title: PRODUCT DRAWINGS/MODELS AND ASSOC IA TED LISTS

Number: DI-SESS-81000E AMSC Number: A9342 DTIC Applicable:

Office of Primary Responsibility: AR Applicable Forms:

Approval Date: 26 February 2013 Limitation:

GIDEP Applicable:

Use/relationship: Product Drawings/Models and Associated Lists provide engineering data to support competitive procurement and maintenance for items interchangeable with the original items. This data represents the highest level of design disclosure.

a. This Data Item Description (DID) contains the format and content preparation instructions for Product Drawings/Models and Associated Lists resulting from the work task described in 5.3.3.3 of

MIL-STD-31000.

b. This DID is applicable to acquisitions of military systems, equipment, and components. It is intended for acquiring drawings/models and Associated Lists at the end of the System Development and Demonstration Phase and during subsequent phases of the DoD materiel life cycle.

c. It is not intended that all the requirements contained herein should be applied to every program. This DID should be tailored to the minimum data requirements of the applicable contract or purchase order.

d. This DID is related to DI-SESS-81001E, DI-SESS-81002F, and DI-SESS-81003E. This DID supersedes DI-SESS-81 OOOD.

e. A purchased item, as defined by ASME Y14.24, an item which is sold or traded in the course of conducting normal business operations, is used by commercial industry, or is a specialized version of a supplier's general product line which he routinely customizes. Purchased items as used herein have also been referred to as vendor items or vendor-developed items.

Requirements:

1. Reference Documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as cited in the ASSIST database, http://assist.daps.dla.mil, at the time of the solicitation; or, for documents not included in ASSIST, as stated herein.

2. General. Product Drawings/Models and Associated Lists shall meet the requirements of MIL-STD- 31000. Product Drawings/Models and Associated Lists shall provide the design disclosure information necessary to enable a manufacturer of similar products at the same or similar state of the art to produce and maintain quality control of item( s) so that the resulting physical and functional characteristics duplicate those of the specified item. These drawings shall:

a. Reflect the end product at its current level of design maturity.

DI-SESS-81 OOOE

b. Provide the engineering data for Logistics Support products.

c. Provide the necessary data to permit competitive acquisition of the original item(s).

3. Format. Product Drawings/Models and Associated Lists shall be in either the contractor's format or the Government's format as specified on the TDP Option Selection Worksheet incorporated into the contract or purchase order.

4. Content. Product Drawings/Models and Associated Lists shall conform to the requirements of ASME YI 4.100, or, if applicable, ASME YI 4.100 and Appendices B through E, as required, ASME YI4.34 and ASME YI4.41 . They shall document directly or by reference the following, as applicable:

a. Details of unique processes, i.e., not published or generally available to industry, when essential to design and manufacture.

b. Performance ratings.

c. Dimensional and tolerance data

d. Critical manufacturing processes and assembly sequences. e.

Toleranced input and output characteristics.

f. Diagrams.

g. Mechanical and electrical connections.

h. Physical characteristics, including form, finishes, and protective coatings.

i. Details of material identification, including material condition, and mandatory treatments and coatings.

j . Inspection, test and evaluation criteria. k.

Equipment calibration requirements.

1. Quality assurance requirements.

m. Hardware marking requirements.

n. Requirements for reliability, maintainability, environmental conditioning, shock and vibration testing and other operational or functional tests.

o. Vendor substantiation data when required by the contract or purchase order.

p. Requirements for programming software into devices or assemblies including a description of the input media and the procedures for validating that the software has been installed correctly.

DI-SESS-81 OOOE

q. Special consideration items and processes.

5. Item definition. All parameters required to define each unit, assembly, subassembly, part or material shall be presented on the applicable drawing/model. This includes data such as:

a. All necessary mechanical dimensions to fully define fabrication, acceptance, interface or installation of the item depicted.

b. All necessary electrical parameters to fully define fabrication, acceptance, interface or installation of the item depicted.

c. All other necessary physical parameters to fully define fabrication, acceptance, interface or installation of the item depicted, i.e. , weight, pressure, viscosity, etc.

d. All necessary environmental conditions which units, assemblies, subassemblies, parts and materials must meet to perform effectively in the end item, such that the end item will meet its specification requirements.

6. CAGE code and document numbers. Product Drawings/Models and Associated Lists shall be identified with the contractor's CAGE code and contractor document numbers or with a Government CAGE code and document numbers as specified in the TDP Option Selection Worksheet incorporated in the contract or purchase order.

7. Selection of drawings. The types of drawings required will vary according to the complexity of the contract end item. The TDP Option Selection Worksheet incorporated in the contract or purchase order will specify whether the contractor or the Government is responsible for selecting the types of drawings/models and Associated Lists.

7 .1 . Vendor Item Control Drawings. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements).

7.2. Source Control Drawings. Source Control Drawings shall be used to specify the requirements for purchased items only when such items have been approved for use in the design and:

a. the item is for a critical application and

b. the requirements can be met by an item from one or more sources and

c. the application required source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements).

7.3 . Standard Microcircuit Drawings. Standard Microcircuit Drawings (MIL-HD BK-780) shall be used to specify the requirements of microcircuits.

8. End ofDI-SESS-81000E.

Title: SOFTWARE TEST PLAN (STP)

Number: DI-1PSC-81438A AMSC Number: N7363 DTIC Applicable:

Office of Primary Responsibility: NA VY/EC Applicable Forms:

Use, Relationships:

Approval Date: 19991215 Limitation:

GIDEP Applicable:

The Software Test Plan (STP) describes plans for qualification testing of Computer Software Configuration Items (CSCis) and software systems. It describes the software test environment to be used for the testing, identifies the tests to be performed, and provides schedules for test activities.

There is usually a single STP for a project. The STP enables the acquirer to assess the adequacy of planning for CSCI and, if applicable, software system qualification testing.

This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.

This DID is used when the developer is tasked to develop and record plans for conducting qualification testing and/or system qualification testing of a software system.

This DID supersedes DI-IPSC-81438.

Requirements:

1. Reference documents. None.

2. General instructions.

a. Automated techniques . Use of automated techniques is encouraged. The term "document" in this DID means a collection of data regardless of its medium.

b. Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.

3. Format. Following are the format requirements.

The plan shall be in contractor format unless otherwise specified on the Contract Data Requirements List (CDRL)(DD 1423). The CDRL should specify whether deliverable data are to be delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, D1-IPSC-81438A

CALS, or compatible with a specified word processor or other support software); may be delivered in developer format rather than in the format specified herein; and may reside in a computer-aided software engineering (CASE) or other automated tool rather than in the form of a traditional document.

4. Content. The plan shall contain the following:

a. Title page or identifier. The document shall include a title page containing, as applicable: document number; volume number; version/revision indicator; security markings or other restrictions on the handling of the document; date; document title; name, abbreviation, and any other identifier for the system, subsystem, or item to which the document applies; contract number; CDRL item number; organization for which the document has been prepared; name and address of the preparing organization; and distribution statement. For data in a database or other alternative form, this information shall be included on external and internal labels or by equivalent identification methods.

b. Table of contents. The document shall contain a table of contents providing the number, title, and page number of each titled paragraph, figure, table, and appendix. For data in a database or other alternative form, this information shall consist of an internal or external table of contents containing pointers to, or instructions for accessing, each paragraph, figure, table, and appendix or their equivalents.

c. Page numbering/labeling. Each page shall contain a unique page number and display the document number, including version, volume, and date, as applicable. For data in a database or other alternative form, files, screens, or other entities shall be assigned names or numbers in such a way that desired data can be indexed and accessed.

d. Response to tailoring instructions . If a paragraph is tailored out of this DID, the resulting document shall contain the corresponding paragraph number and title, followed by "This paragraph has been tailored out." For data in a database or other alternative form, this representation need occur only in the table of contents or equivalent.

e. Multiple paragraphs and subparagraphs. Any section, paragraph, or subparagraph in this DID may be written as multiple paragraphs or subparagraphs to enhance readability.

f. Standard data descriptions. If a data description required by this DID has been published in a standard data element dictionary specified in the contract, reference to an entry in that dictionary is preferred over…