CDRLS and DIDs.pdf

Source: http://assist.dla.mil -- Downloaded: 2022-03-08T20:02Z Check the source to verify that this is the current version before use.

DATA ITEM DESCRIPTION

Title: SOFTWARE SUSTAINABILITY PACKAGE

Number: DI-IPSC-82134 Approval Date: 20170615

AMSC Number: N9821 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: AS Project Number: IPSC-2017-003

Applicable Forms: N/A

Use/relationship: The Software Sustainability Package (SSP) contains the superset of source code, design details, models, algorithms, processes, flow charts, formulae and related materials that would allow the software to be reproduced, recreated or recompiled, as needed for sustainment by non-developer(s) or the original equipment manufacturer (OEM). This includes all executable software, des ign model s , source files, and software sustainment information, including "as built" design information and compilation, build, and modification procedures, for each Computer Software Configuration Item (CSCI).

The SSP is to be used in conjunction with a Contract Line Item Numbers (CLINs) or CLIN

Options to procure the executable software and source files for a CSCI and is the primary software sustainment document for each CSCI which could be maintained by non-OEM(s). The

SSP is the line item description of the data and products that are to be procured through the

CLINs.

Note: Different organizations have different policies for ordering delivery of software. These policies should be determined before applying this Data Item Description (DID).

This DID is used when the developer is tasked, either by CLIN, Statement of Work (SOW) or Statement of Objectives (SOO), to prepare executable software, source files, "as built"

CSCI design, hardware and related sustainment information for delivery.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract SOW.

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 specified in the contract.

2. Format. The SSP shall be in contractor format. The SSP shall adhere to the format described under Content.

3. Content. The specification shall contain the following items:

Source: http://assist.dla.mil -- Downloaded: 2022-04-06T20:10Z

DI-IPSC-82134

3.1 Scope

a. A detailed and complete 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).

b. 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 sustainment agencies; identify current and planned operating sites.

c. Describe the relationship to other project management plans.

3.2 Provide a detailed listing of source files, including source code in its original language, batch files, build scripts, data files, and libraries necessary to successfully regenerate the software product from scratch and to be able to successfully execute the regenerated software product on the target hardware without any involvement from the software product’s OEM.

3.3 Identify and describe in detail the hardware and associated documentation needed to sustain the deliverable software. This hardware may include computers, peripherals, hardware simulators, stimulators, emulators, diagnostic equipment, programming equipment (e.g. erasure of software from, loading software onto, and verification of software on a hardware device), firmware devices, and non-computer equipment. The following shall be included in the description:

a. Specific models, versions and configurations.

b. Operator manuals or instructions for each item, as applicable.

c. Whether the item is furnished by the developer, by the OEM, as GFE/GFI, etc. and whether the item is still supported by that particular organization. If the item is no longer supported or manufactured, a plan for procuring replacements (e.g. new source of supply) should be identified.

d. Information about licensing, data rights, etc.

e. Security and privacy considerations, limitations, or any other items of interest.

f. Information about the operational and environmental limits to which the item may be subjected and maintain satisfactory operation.

3.4 Provide a detailed description of the complete software development environment (SDE) and software test environment. The following shall be included in the description:

a. All software tools (Cybersecurity, compilers, linkers, loaders, debuggers, scripts, etc).

b. Procedural documentation.

c. Operational data and settings, such as compiler flags and environmental variables required to regenerate and maintain the software product.

3.5 Provide a detailed listing and description of automated test tools associated with the software product.

DI-IPSC-82134

3.6 As an appendix to this document or as a standalone document, identify, detail and list all unit, component and CSCI level test procedures and all test scripts.

3.7 As an appendix to this document or as a standalone document, identify, detail and list all

CSCI, CSC, CSU and system integration procedures; hardware/software integration procedures; and instructions for use of integration procedures.

3.8 As an appendix to this document or as a standalone document, identify, detail and list all system development testing suites such as System Integration Lab (SIL) subsystems, and data acquisition, data reduction, and data analysis tools, along with all custom test equipment.

3.9 Provide a detailed description of problem tracking, software configuration management, and data management tools and licenses.

3.10 Provide a detailed description of requirements, design, source code and processes for devices and software which load software into the subsystems.

3.11 Provide a detailed description of licenses, including commercial and open source, which are utilized at the SDE, software test environment, and SIL.

3.12 As an appendix to this document identify and detail all software architecture artifacts, including Unified Modeling Language (UML) diagrams, UML modeling and executable code, and data models.

3.13 As an appendix to this document identify and detail training materials to teach the sustainers the complexities of the systems and the interfaces with other systems.

3.14 Identify and detail other items required for software development and sustainment that are not previously requested or identified in the previous sections.

4. 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.

5. Appendixes. Appendixes 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 DI-IPSC-82134

Title: SYLLABUS Number: DI-MISC-81459B Approval Date: 20200422 AMSC Number: F10169 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFLCMC/WNSE) Project Number: MISC-2018-012 Applicable Forms: N/A Use/Relationship: The syllabus is the standardized plan for conducting training in a given course of instruction. It establishes a course configuration baseline and is used as a course control document.

a. This Data Item Description (DID) is applicable to all contracts requiring training course development.

b. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

c. This DID supersedes DI-MISC-81459A.

Requirements:

1. Reference documents. None.

2. Format. Contractor format is acceptable.

3. Content. The Syllabus shall include the following sections:

3.1 Course accounting. This section shall include the following information:

a. Course title

b. Course number

c. Course purpose

d. Course description

e. Course prerequisites

f. Course approval information

g. Course phase of training

h. Grading procedures

i. Status upon graduation from the course

j. Training strategy

k. Academic training, aircrew training devices, ground crew training devices, maintenance training devices, and flying inventory required for the course

l. Class start date

m. Quota control

Source: http://assist.dla.mil -- Downloaded: 2022-03-08T21:02Z

DI-MISC-81459B

3.2 Course training standards. This section shall include the following information:

a. Training elements to be accomplished

b. Standards of accomplishment for each training element

c. Course map

d. Course sequence

e. Training schedule matrix

3.3 Academic media. This section shall include the following information:

a. Lectures and description

b. Workbook and description

c. Sound and course slides and description

d. Interactive courseware (ICW) lessons and description

e. Required instructional manuals

3.4 Aircrew, ground crew, and maintenance training devices. This section shall include the following information:

a. Training device requirements

b. Mission statement and objective for each training device

c. Explanation of sortie elements to be accomplished

3.5 Criterion-referenced objectives. This section shall include the terminal objectives.

3.6 Course data. This section shall include the following information:

a. Course length

b. Breakdown of classroom and simulator hours

c. Class start date

d. Instructor contact hours

e. Class size

f. Specialty

g. Individual student training plan

h. Class frequency

i. Task list

3.7 Facilities and resources. This section shall include the following information:

a. Location of training

b. Student reporting instructions

c. Instructor staffing requirements

d. Requirements for multiple instruction, if applicable

e. Classroom and simulator layout

f. Student library of reference materials

DI-MISC-81459B

g. Instructor accessibility

h. Facility usage requirements per student

3.8 Explanation of terms. This section shall include explanation of terms unique to the training command or training system.

3.9 Curriculum outline of instruction. The curriculum outline shall provide detailed training data for each aircrew, ground crew, and maintenance position. The outline shall provide the sequence in which the courses are to be presented for each aircrew, ground crew, and maintenance position. The curriculum outline shall contain the following:

a. Curriculum title and scope

b. Academic hours

c. Training tasks

d. Terminal objectives

e. Enabling objectives

f. Method of instruction

g. Training support equipment and materials

h. Student library

End of DI-MISC-81459B

Data Item Description

Title: Software/Firmware Change Request Approval Date: 20100420 Number: DI-MISC-81807 Limitation: N/A AMSC Number: N9130 GIDEP Applicable: N/A DTIC Applicable: N/A Office of Primary Responsibility: SH/PMS-408 Applicable Forms: N/A

Use/relationship: The Software/ Firmware Change Request will be used to alert or inform the government about changes to software and firmware and also to provide detailed information to the government about the changes and the estimated cost of the software/firmware changes.

This DID contains the format, content and preparation instructions for the data product generated by the specific and discrete work task requirement as delineated in the contract.

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 specified in the contract.

2. Format. The Software/Firmware Change Request shall be presented in the Contractor’s format.

3. Content. The Software/Firmware Change Request shall contain all the information identified in Figures 1-7.

4. End of DI-MISC-81807.

Page 1 of 8 Pages

Source: http://assist.dla.mil -- Downloaded: 2022-03-08T20:10Z

DI-MISC-81807

SOFTWARE CHANGE REQUEST (SCR), PAGE 1

2. DATE

3. JUSTIFICATION CODE

1. ORIGINATOR NAME AND ADDRESS (include e-mail address and telephone number)

Name:

Organization:

Street 1:

Street 2:

City, State, Zip Code:

Telephone Number: ( ) ext:: E-mail address:

4. TYPE OF SCR

Class I Class II

5. PRIORITY

Emergency Urgent Routine

6. SCR DESIGNATION 7. BASELINE AFFECTED

a. CI/CSCI AFFECTED

b. CAGE CODE

c. SYSTEM DESIGNATION

FUNCTIONAL ALLOCATED PRODUCT

d. SCR No.

e. REVISION

f. TYPE Preliminary Final

8. OTHER SYS/CONFIG ITEMS AFFECTED

YES NO

9. IN PRODUCTIO N

YES NO

10. DOCUMENTS AFFECTED

CAGE CODE SPEC/DOC NO. REVISION SCN/NOR/ECN/ECO NO.

11. TITLE OF CHANGE

12. CONTRACT NO. & LINE ITEM

13. CONFIGURATION ITEM NOMENCLATURE

14. PROCURING CONTRACTING OFFICER

15. LOWEST ASSEMBLY AFFECTED

a. NOMENCLATURE

b. PART NO.

16. DESCRIPTION OF CHANGE

17. NEED FOR CHANGE

18. PRODUCTION EFFECTIVITY BY SERIAL NUMBER

19. EFFECT ON PRODUCTION DELIVERY

SCHEDULE

20. RETROFIT

a. RECOMMENDED ITEM EFFECTIVITY

b. ESTIMATED KIT DELIVERY SCHEDULE

c. PLATFORMS AFFECTED

21. ESTIMATED COST or (SAVINGS) UNDER CONTRACT

No Additional Cost/Savings – In Scope of the Contract

22. SUBMITTING ACTIVITY AUTHORIZING SIGNATURE

22a. TITLE

23. APPROVAL/DISAPPROVAL

a. LCCB CHAIRMAN

DATE :

RECOMMEND APPROVAL

RECOMMNED DISAPPROVAL

b. CCB CHAIRMAN

DATE :

APPROVED

DISAPPROVED

Figure 1 Page 2 of 8 Pages

SOFTWARE CHANGE REQUEST (SCR), Figure 2

SCR NUMBER & REV:

EFFECT ON FUNCTIONAL/ALLOCATED CONFIGURATION IDENTIFICATION

24. OTHER SYSTEMS AFFECTED

25. OTHER CONTRACTORS/ACTIVITIES AFFECTED

26. CONFIGURATION ITEMS AFFECTED

27. EFFECTS ON PERFORMANCE ALLOCATIONS AND INTERFACES IN SYSTEM SPECIFICATION

28. EFFECTS ON EMPLOYMENT, INTEGRATED LOGISTICS SUPPORT, TRAINING, OPERATIONAL, EFFECTIVENESS, OR SOFTWARE

29. EFFECTS ON CONFIGURATION ITEM SPECIFICATIONS

30. DEVELOPMENTAL REQUIREMENTS AND STATUS

31. TRADE-OFFS AND ALTERNATIVE SOLUTIONS

32. DATE BY WHICH CONTRACTUAL AUTHORITY IS NEEDED

Figure 2 Page 3 of 8 Pages

SOFTWARE CHANGE REQUEST (SCR), Figure 3

SCR NUMBER & REV:

EFFECTS ON PRODUCT CONFIGURATION IDENTIFICATION, LOGISTICS, AND OPERATIONS

(X) FACTOR ENCL. PAR. (X) FACTOR ENCL. PAR.

33. EFFECT ON PRODUCT CONFIGURATION

IDENTIFICATION OR CONTRACT

35. EFFECT ON OPERATIONAL

EMPLOYMENT

a. PERFORMANCE a. SAFETY

b. WEIGHT-BALANCE STABILITY (Aircraft) N/A N/A b. SURVIVABILITY

c. WEIGHT-MOMENT (Other equipment) N/A N/A c. RELIABILITY

d. CDRL, TECHNICAL DATA d. MAINTAINABILITY

e. NOMENCLATURE e. SERVICE LIFE

f. OPERATING PROCEDURES

g. ELECTROMAGNETIC INTERFERENCE 34. EFFECT ON INTEGRATED LOGISTICS

SUPPORT (ILS) ELEMENTS

h. ACTIVATION SCHEDULE

a. ILS PLANS i. CRITICAL SINGLE POINT FAILURE ITEMS

b. MAINTENANCE CONCEPT, PLANS, PROCEDURES j. INTEROPERABILITY c LOGISTICS SUPPORT ANALYSIS

d. INTERIM SUPPORT PROGRAMS 36. OTHER CONSIDERATIONS

e. SPARES AND REPAIR PARTS N/A N/A a. INTERFACE

f. TECH MANUALS/PROGRAMMING TAPES b. OTHER AFFECTED EQUIPMENT/GFE/GFP N/A N/A

g. FACILITIES N/A N/A c. PHYSICAL CONSTRAINTS N/A N/A P h. SUPPORT EQUIPMENT N/A N/A d. COMPUTER PROGRAMS AND RESOURCES

i. OPERATOR TRAINING e. REWORK OF OTHER EQUIPMENT N/A N/A

j. OPERATING TRAINING EQUIPMENT f. SYSTEM TEST PROCEDURES

k. MAINTENANCE TRAINING g. WARRANTY/GUARANTEE

l. MAINTENANCE TRAINING EQUIPMENT h. PARTS CONTROL N/A N/A

m. CONTRACT MAINTENANCE i. ENVIRONMENTAL

n. PACKAGING , HANDLING, STORAGE, AND

TRANSPORTABILITY

N/A N/A j. FMS RELEASE

37. ALTERNATE SOLUTIONS

38. DEVELOPMENTAL STATUS

39. RECOMMENDATIONS FOR RETROFIT

40. WORK-HOURS PER UNIT TO INSTALL RETROFIT KITS

a. ORGANIZATION

b. INTERMEDIATE

c. DEPOT

d. OTHER

41. WORK-HOURS TO CONDUCT SYSTEM TESTS AFTER RETROFIT

42. THIS CHANGE MUST BE ACCOMPLISHED

BEFORE WITH AFTER THE FOLLOWING CHANGES:

43. IS CONTRACTOR FIELD

SERVICE ENGINEERING

REQUIRED?

YES NO

44. OUT-OF-SERVICE TIME

45. EFFECT OF THIS SCR AND PREVIOUSLY APPROVED SCRs

46. DATE CONTRACTUAL AUTHORITY NEEDED

FOR PRODUCTION:

FOR RETROFIT:

Figure 3 Page 4 of 8 Pages

Figure 4 Page 5 of 8 Pages

SOFTWARE CHANGE REQUEST (SCR), Figure 5 SCR NUMBER and REV:

48. ESTIMATED COSTS SAVINGS/SUMMARY, RELATED SCRs (Use parentheses for savings)

FACTOR

CAGE CODE

(a)

SCR NUMBER

(b)

COSTS/SAVINGS

UNDER CONTRACT

(c)

OTHER COSTS/

SAVINGS

(d)

a. PRODUCTION COST/SAVING (Subtotal of Costs/Savings Elements from block 51a applicable to aircraft, ship, tank, vehicle, missile, or its subsystem)

SUBTOTAL PRODUCTION COSTS/SAVINGS

b. RETROFIT COSTS (Applicable to aircraft, ship, tank, vehicle, missile, or its subsystem)

SUBTOTAL RETROFIT COSTS

c. INTEGRATED LOGISTICS SUPPORT COSTS/SAVING REVISED

REQUIREMENTS

(1) ITEM RETROFIT (If not covered under “b”) (Applicable to aircraft, ship tank, vehicle, missile, or its subsystem)

(2) ILS SUBTOTAL (Applicable to aircraft, ship, tank, vehicle, missile or its subsystem)

(3) OPERATOR TRAINER (Net total cost/saving from each SCR covering operator trainer)

(4) MAINTENANCE TRAINER (Net total cost/saving from each SCR covering maintenance trainer)

(5) OTHER TRAINING EQUIPMENT

(6) SUPPORT EQUIPMENT (Net total cost/saving from each SCR on support equipment)

(7) ILS PLANS

(8) MAINTENANCE CONCEPT, PLANS, SYSTEM DOCUMENTS

(9) INTERIM SUPPORT PLAN

RECURRING COSTS

NEW REQUIREMENTS

PROCURIN

G

ACTIVITY

CODE

NON-

RECURRING

COSTS UNIT QTY TOTAL

(10) PROVISIONING DOCUMENTATION

(11) OPER TRNR/TRNG DEVICES/EQUIP

(12) MANUALS/PROGRAMMING TAPES, SPARES,

REPAIR PARTS (For 11)

(13) MAINTENANCE TRNR/TRNG DEVICES/

EQUIPMENT

(14) MANUALS/PROGRAMMING TAPES, SPARES,

REPAIR PARTS (For 13)

(15) SUPPORT EQUIPMENT

(16) MANUALS/PROGRAMMING TAPES (For 15)

(17) PROVISIONING DOCUMENTATION (For 15)

(18) REPAIR PARTS (For 15) N/A N/A N/A N/A N/A N/A N/A

(19) SUBTOTAL ILS COSTS/SAVINGS (Sum of c. 1 through c. 18)

CAGE CODE SCR NUMBER

d. OTHER COSTS/SAVINGS (Total from block 48d of related SCRs)

TOTAL OTHER COSTS/SAVINGS

SUBTOTALS OF COLUMNS

SUBTOTAL UNDER CONTRACT

Figure 5 Pages 6 of 8 Pages

SOFTWARE CHANGE REQUEST (SCR), Figure 6

SCR NUMBER and REV:

49. TITLE OF CHANGE

50. DATE AUTHORIZATION TO PROCEED

RECEIVED BY CONTRACTOR (YYMMDD)

S START DELIVERY C COMPLETED DELIVERY PROGRESS POINT

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

Figure 6 Page 7 of 8 Pages a.

C O

(1) Software Engineering

N F I

(2) Software Documentation

G U R

(3) Software Engineering Test

A T

(4) Update TDP b.

S

(1) Software Engineering Environment Upgrade

P

(2) Software Test Environment Upgrade

E Q

M c.

(1) Operator

A

(2) Maintenance

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 2

26 27 28 29 30 31 32 33 34 35 36

SOFTWARE CHANGE REQUEST (SCR), Continuation Sheet, Figure 7

TITLE OF CHANGE

SCR NUMBER and REV:

PARAGRAPH# BLOCK/LINE NO. BLOCK TITLE AND SUPPLEMENTARY INFORMATION

Figure 7 Page 8 of 8 Pages

Title: SOFTWARE LICENSE REQUIREMENTS LIST

Number: DI-PSSS-82046 Approval Date: 20160628

AMSC Number: N9672 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: AS Project Number: PSSS-2016-014

Applicable Forms: N/A

Use/relationship: The Software License Requirements List provides information that sustainment activities require to procure software licenses required to operate and maintain software intensive systems as part of the Department of Defense Program Manager’s total life cycle management responsibilities.

This Data Item Description (DID) contains the format, content, and intended use of information for the data product resulting from the work task described by the solicitation.

The data may be obtained during any program life cycle phase.

Requirements:

1. Format. Contractor’s format is acceptable. The Software License Requirements List shall be in a format similar to that of Table 1 and shall be provided in an electronic format compatible with current spreadsheet applications (ex. Microsoft Excel)

2. Content. The Software License Requirements List shall contain all of the information specified in Table 1. All fields shall be included. Fields that do not require data shall be left blank. The information shall be included for all software licenses required to operate the system specified in the contract.

Source: http://assist.dla.mil -- Downloaded: 2022-04-05T19:07Z

DI-PSSS-82046

Table 1: Field Definitions and Instructions

Field Name Definition Notes and Instructions

Software Licensed Name of the software being licensed Required

Software Version

Licensed

Version number of the software being licensed Required

Software Description Brief description of the software being licensed including whether or not it is commercial software

Required

Licenses Required Number of licenses required, per aircraft, to operate the system Required

License Requirement

Notes

Narrative description of the software license requirement. Include a description of the type of license required if it differs from one software license per aircraft

Required if Licenses Required field is not “one”

License Term Length of time the software license is valid Required. If license does not expire, include that information here

License Expiry Date Date current software license will expire Required if licenses are currently in place to operate the software

License Price Price of the software license Required (If no-cost, indicate no-cost license)

Maintenance Agreement Information regarding whether or not software maintenance or updates are included in the software license

Required

Company Name Name of the company licensing the software Required

Company CAGE Commercial and Government Entity (CAGE) code of the company licensing the software

Required if the company has a

CAGE assigned

Procurement Information Information describing where the Government can procure the license described

Required

End of DI-PSSS-82046

Source: http://assist.dla.mil -- Downloaded: 2022-04-05T19:07Z

Title: CALIBRATION CERTIFICATE/REPORT Number: DI-QCIC-80798C Approved Date: 20170123 AMSC Number: F9766 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 36 Project Number: QCIC-2017-003 Applicable Forms: N/A Use/Relationship: The Calibration Certificate/Report documents calibration certificates or reports accompanying the calibrations performed on Department of Defense (DoD) test, measurement, and diagnostic equipment.

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

b. This DID is applicable to contracts requiring calibration of test equipment prior to delivery.

This DID is consistent with ISO/IEC 17025, General requirements for the competence of testing and calibration laboratories, requirements for calibration reports or certificates.

(Copies of this document are available online at http://www.iso.org.)

c. This DID supersedes DI-QCIC-80798B.

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 specified in the contract.

2. Format. Contractor format is acceptable.

3. Content. The calibration certificate or report shall include:

a. Title (e.g., calibration certificate or calibration report);

b. The name and address of the laboratory and the location where the calibrations were carried out, if different from the address of the laboratory;

c. Unique identification of the calibration certificate or test report (such as the serial number), and on each page an identification in order to ensure that the page is recognized as a part of the test report or calibration certificate, and a clear identification of the end of the calibration certificate or test report;

d. The name and address of the client or customer;

e. Identification of the method used;

f. A description of, the condition of, and the unambiguous identification of the item(s) tested or calibrated;

g. The date of receipt of the test or calibration item(s) where this is critical to the validity and application of the results, and the date(s) of performance of the test or calibration;

DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.

Source: http://assist.dla.mil -- Downloaded: 2022-03-08T18:53Z

DI-QCIC-80798C

h. Reference to the sampling plan and procedures used by the laboratory or other bodies where these are relevant to the validity or application of the results;

i. The test or calibration results with, where appropriate, the units of measurement;

j. The name(s), function(s) and signature(s) or equivalent identification of person(s) authorizing the calibration certificate or test report;

k. Where relevant, a statement to the effect that the results relate only to the items tested or calibrated;

l. The conditions (e.g., environmental) under which the calibrations were made that have an influence on the measurement results;

m. The uncertainty of measurement or a statement of compliance with an identified metrological specification or clauses thereof;

n. Evidence that the measurements are traceable.

End of DI-QCIC-80798C.

Source: http://assist.dla.mil -- Downloaded: 2022-03-08T18:53Z

Source: http://assist.dla.mil -- Downloaded: 2022-03-08T19:56Z

Source: http://assist.dla.mil -- Downloaded: 2022-03-08T19:56Z

Title: COMMERCIAL OFF-THE-SHELF (COTS) MANUALS AND ASSOCIATED

SUPPLEMENTAL DATA

Approval Date: 20211203 Limitation: No GIDEP Applicable: No

Number: DI-TMSS-80527D AMSC Number: 10283 DTIC Applicable: No Office of Primary Responsibility: TM

Applicable Forms: None

Use/relationship: Commercial Off-the-Shelf Manuals may be used as-is or with supplementation to support COTS equipment used by DOD. This DID is used to:

a. Acquire sample COTS manuals for evaluation.

b. Acquire COTS manuals that have been evaluated and found to be acceptable.

c. Acquire associated supplemental data, if required.

This DID contains format, content, and intended use information for the data deliverable(s) resulting from the work described in MIL-PRF-32216.

This DID supersedes DI-TMSS-80527C, dated 12 Aug 2011.

Requirements:

1. Content. The manual shall contain all technical information on the assembly, installation, operation, parts, and maintenance of commercial equipment.

2. Evaluation. The manual shall be evaluated using the criteria found in MIL-PRF-32216.

3. Supplementation. The manual may be supplemented with additional data to comply with contract.

Supplemental data shall be prepared in accordance with MIL-PRF-32216.

4. Format. The basic manual shall be presented in the contractor's format. Supplemental data shall be presented in the format specified by the acquiring activity.

5. Digital files. Interactive Electronic Technical Manuals (IETMs) or PDFs are preferred for electronic COTS manuals.

6. PDF Files. PDF files shall be searchable, capable of having links added, and have fonts embedded.

7. IETMs. IETMs shall meet the general style and format and user interface requirements in MIL- STD-40051-1 (Army only) or MIL-STD-3031 (Army only).

8. Paper manuals. If paper manuals are acquired, the data shall be clearly legible and on paper of sufficient quality for long term use.

9. Quick Reference Guides (QRGs). QRGs shall meet the requirements of MIL-PRF-32614.

End of DI-TMSS-80527D

Source: http://assist.dla.mil -- Downloaded: 2022-03-08T19:03Z

NOT MEASUREMENT SENSITIVE

MIL-STD-1839D

12 MAY 2010

SUPERSEDING

MIL-STD-1839C

27 NOVEMBER 2000

DEPARTMENT OF DEFENSE

STANDARD PRACTICE

CALIBRATION AND

MEASUREMENT REQUIREMENTS

AMSC 9117 AREA QCIC

DISTRIBUTION STATEMENT A. Approved for public release, distribution is unlimited.

Source: http://assist.dla.mil -- Downloaded: 2022-03-30T20:27Z

FOREWORD

1. This military standard is approved for use by all Departments and Agencies of the Department of Defense.

2. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to 588th CBSS/GBNA, 813 Irving-Wick Dr W, Heath OH 43056-1199, or by letter emailed to MIL-PRF@AFMETCAL.AF.MIL since contact information can change; you may want to verify the currency of this address information using the ASSIST Online database at https://assist.daps.dla.mil.

ii https://assist.daps.dla.mil/ iii

CONTENTS

PARAGRAPH PAGE

1 SCOPE

1.1 Purpose

1.2 Applicability

1.2.1 Application guidance

2 APPLICABLE DOCUMENTS

2.1 General

2.2 Government documents

2.2.1 Specifications, standards and handbooks

2.2.2 Other government documents, drawings, and publications

2.3 Order of precedence

3 DEFINITIONS

3.1 Definitions

3.1.1 Accuracy

3.1.2 Built-in-Test (BIT)

3.1.3 Built-in-Test Equipment (BITE)

3.1.4 Calibration

3.1.5 Calibration Interval

3.1.6 Calibration and Measurement Requirements Summary (CMRS)

3.1.7 Design Activity

3.1.8 Interface Test Adapter

3.1.9 Logistics Support Analysis (LSA)

3.1.10 Measurement Traceability

3.1.11 Support Equipment (SE)

3.1.12 Support Equipment Recommendation Data (SERD)

3.1.13 Test Accuracy Ratio (TAR)

3.1.14 Test, Measurement, and Diagnostic Equipment (TMDE)

3.1.15 Test Program Set (TPS)

3.1.16 Test Uncertainty Ratio (TUR)

3.1.17 Uncertainty

4 GENERAL REQUIREMENTS

4.1 General measurement requirements

iv

CONTENTS

PARAGRAPH PAGE

5 DETAILED REQUIREMENTS

5.1 System Measurement Parameters

5.1.1 Description of Items

5.1.2 Identification of Parameters

5.1.3 Sequence of Relationship

5.1.4 Selecting TMDE

5.1.5 Firmware of System

5.2 Built-In Test and Built-In Test Equipment

5.3 System Test Points

5.4 Test, Measurement, And Diagnostic Equipment

5.4.1 Recommended TMDE

5.4.2 TMDE in support of TMDE

5.4.3 Test Uncertainty Ratio

5.4.4 Automatic Test Equipment

5.4.4.1 ATE Design

5.4.4.2 ATE Technical Description

5.4.4.3 ATE Calibration

6 NOTES

6.1 Intended Use

6.2 Associated Data Item Descriptions (DIDs)

6.3 Subject Term (keyword) Listing

6.4 Changes from previous issue

CONCLUDING MATERIAL

1. SCOPE

1.1 Purpose. This standard describes the requirement to provide a means for calibration and measurement traceability of all system, subsystem, and equipment. From this point on in this document, the word system will refer to system, subsystem, and equipment. This ensures system operational integrity and accuracy. It defines the requirement for establishing measurement traceability from actual system level measurements to the National Institute of Standards and Technology (NIST) or other approved measurement sources.

1.2 Applicability. The requirements of this standard apply to all systems that require measurements of any type to ensure proper operation.

1.2.1 Application guidance.

When Logistics Support Analysis (LSA) is required on an acquisition program, the requirements of this standard should be an integral part of the LSA effort. Data developed as a result of this standard should be documented in and become part of the LSA documentation.

When LSA is exempted or the LSA is tailored to exempt development of the data requirements, this standard can become an independent compliance document of the acquisition program and tailored in accordance with the contract.

2. APPLICABLE DOCUMENTS

2.1 General. The documents listed in this section are specified in sections 3, 4, and 5 of this standard.

This section does not include documents cited in other sections of this standard or recommended for additional information or as examples. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements documents cited in sections 3, 4, and 5 of this standard, whether or not they are listed.

2.2 Government documents.

2.2.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified herein.

HANDBOOK

DEPARTMENT OF DEFENSE

MIL-HDBK-300 Military Handbook, Technical Information File of Support Equipment.

MIL-HDBK-1839 Military Handbook, Calibration and Measurement Requirements

(Unless otherwise indicated, copies of the above military handbooks are available through the Acquisition Streamlining and Standardization Information System. Located on the internet at https://assist.daps.dla.mil/online/start/ .)

http://assist.daps.dla.mil/online/start/

2.2.2 Other government documents, drawings, and publications. The following other Government documents, drawings, and publications form a part of this document to the extent specified herein.

Unless otherwise specified, the issues are those cited in the solicitation.

NAVAIR 17-35MTL-1 Metrology Requirements List (METRL) NAVAIR 17-35NCE-1 Navy Calibration Equipment List (NCE)

TB 43-180 Calibration and Repair Requirements for the Maintenance of

Army Material TM-10510-14/1 U.S. Marine Corps Electronics Test Equipment Listing

TO 33K-1-100-1 Calibration Procedure for Maintenance Data Collection Codes, and Calibration Measurement Summaries.

TO 33K-1-100-2 TMDE Calibration Notes , Calibration Interval, Technical Order, And Work Unit Code Reference Guide

(Copies of Air Force TO 33K-1-100-1, 33K-1-100-2, Army TB 43-180, NAVAIR 17-35MTL-1, or NAVAIR 17-35NCE-1 should be obtained as directed by the contracting officer. The Marine Corps Technical Manual is available from HQMC, Technical Manual Sec, Washington, DC 20380-0001.)

2.3 Order of Precedence. In the event of a conflict between the text of this standard and the references cited herein, the text of this standard will take precedence. Nothing in this standard, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. DEFINITIONS

3.1 Definitions

3.1.1 Accuracy. Closeness of agreement between a measured quantity value and a true quantity value of the measured.

3.1.2 Built-in-Test (BIT). A test approach using built-in test equipment or self-test hardware and software that is internally designed into the supported system, subsystem, or equipment to test all or a part of that system, subsystem, or equipment.

3.1.3 Built-in-Test Equipment (BITE). Any device which is a part of a system, subsystem, or equipment and is used for the express purpose of testing the system, subsystem or equipment. BITE is an identifiable unit of the system, subsystem, or equipment.

3.1.4 Calibration. The set of operations that establish, under specified conditions, the relationship between values of quantities indicated by a measuring instrument or measuring system, or values represented by a material measure or a reference material, and the corresponding values realized by standards.

3.1.5 Calibration Interval. The maximum time an item of TMDE, may go between calibrations and still achieve its target measurement reliability.

3.1.6 Calibration and Measurement Requirements Summary (CMRS). A report which details the measurement requirements of a system, subsystem, or equipment; the TMDE, and the calibration standards and equipment required to assure traceability of all measurements through the applicable individual military service's metrology and calibration program.

3.1.7 Design Activity. A design activity is an activity that has responsibility for the design or modification of an item. The activity may be a U.S. Government, commercial, or nonprofit organization.

3.1.8 Interface Test Adapter. The point located on the ATE where all input and output signals are accessible for connection to an external UUT or calibration standard.

3.1.9 Logistics Support Analysis (LSA). The selective application of scientific and engineering efforts undertaken during the acquisition process, as part of the system engineering and design process, to assist in complying with supportability and other Integrated Logistics Support (ILS) objectives. The LSA process is a planned series of tasks performed to examine all elements of a proposed system to determine the logistics support required to keep that system useable for its intended purpose; and to influence the design so both the system and support can be provided at an affordable cost.

3.1.10 Measurement Traceability. The property of the result of a measurement or the value of a standard whereby it can be related to stated references, usually national or international standards, through an unbroken chain of comparisons all having stated uncertainties. Traceability, as used in this standard, applies to measurements/calibrations made from the prime system or subsystem through an unbroken chain of comparisons to the national reference standards.

3.1.11 Support Equipment (SE). All equipment used in calibration and maintenance support of mission and operational equipment.

3.1.12 Support Equipment Recommendation Data (SERD). The document, usually prepared by an equipment manufacturer, which describes the support requirement for an item of equipment and recommends an item of support equipment to satisfy the requirement.

3.1.13 Test Accuracy Ratio (TAR). A simple comparison between the accuracy of the Unit Under Test (UUT) and the accuracy of the calibration standard. However, this ratio does not consider other potential sources of error in the calibration process. For example, if it is required that an equipment output parameter’s accuracy is +/-8% and the accuracy of the single measuring device used to measure the output parameter is +/-2%, then the TAR is 8 to 2 or 4 to 1.

3.1.14 Test, Measurement, and Diagnostic Equipment (TMDE). Any system or device used to test, measure, evaluate, inspect, or otherwise examine materials, supplies, equipment, or a system to identify and/or isolate any actual or potential malfunction, or to determine compliance with specifications established in technical documents (e.g. research, development, test, and evaluation documents;

specifications; engineering drawings; technical orders). TMDE is SE that provides for measurement traceability.

3.1.15 Test Program Set (TPS). The ensemble of input-desired response data used to verify the performance of the system under test.

3.1.16 Test Uncertainty Ratio (TUR). The comparison between the accuracy of the Unit Under Test and the estimated calibration uncertainty is known as a Test Uncertainty Ratio (TUR). This ratio is more reliable because it accounts for possible sources of error in the calibration process that the TAR does not.

This value also takes into account issues such as temperature, humidity, Type A (statistical analysis including actual and random measurement results), and Type B (anything not a Type A) uncertainties.

3.1.17 Uncertainty. The word “uncertainty” means doubt, and thus in its broadest sense “uncertainty of measurement” means doubt about the validity of the result of a measurement. Because of the lack of different words for this general concept of uncertainty and the specific quantities that provide quantitative measures of the concept, for example, the standard deviation, it is necessary to use the word “uncertainty” in these two different senses.

4. GENERAL REQUIREMENTS

4.1 General Measurement Requirements. The design activity shall ensure the following actions are accomplished for the affected systems and equipment throughout their life cycle.

a. All parameters that require measurement to ensure proper and accurate operation of the system are identified and documented.

b. Calibration and measurement actions are conducted as required to maintain accurate operation.

Such actions are to be accomplished at all applicable system and subsystem levels and are appropriately integrated into the total system requirements.

c. All parameters are readily accessible and measurable in a manner that minimizes the number and duration of the tests required.

d. Measurement traceability of all system and subsystem parameters is documented.

5. DETAILED REQUIREMENTS

5.1 System Measurement Parameters.

5.1.1 Description of Items. The system, subsystem, or equipment, which has parameters that require measurement, shall be identified by nomenclature, manufacturer and manufacturer's code, part or model number, and type designation. If an item does not have an approved part number, but does have an approved or proposed end item specification number or system number, that number shall be referenced.

Each requirement shall identify:

a. Function: The function (specific input, output, or other characteristic which has units of measurement such as volts, frequency, power, current, length, force, etc.) which will be measured, tested, checked, or adjusted.

b. Operational range or specific value: The range of values or actual value that shall be measured to satisfy operational requirements.

c. Operational Tolerance: The tolerance of the range or specific value within which the equipment is required to perform to meet operational specifications.

d. Calibration Interval: The design activity shall recommend a maximum time lapse between tests.

5.1.2 Identification of Parameters. The design activity shall identify all system, subsystem, and equipment parameters that require measurement or testing to ensure proper system or equipment accuracy, and to ensure intended mission goals are met.

5.1.3 Sequence of Relationship. This assessment of parameters shall portray the logical sequence of relationship between the systems, and identify the parameters requiring measurement and verification.

5.1.4 Selecting TMDE. This assessment of parameters shall be used by the design activity during the evaluation process for recommending or selecting TMDE and developing support documentation.

5.1.5 Firmware of System. The design activity shall ensure that all firmware equipment that is required for measurement or testing is annotated by version, revision number and revision date. Any changes to the firmware that affects measurement or testing is documented as to the extent the change affect the measurement accuracy of the equipment should be noted.

5.2 Built-In Test and Built-In Test Equipment. For parameters of BIT and BITE, or other internal measurements which are part of the operational equipment requiring test or measurement, the nomenclature, manufacturer or code, part number or model number, range and accuracy of the operational equipment shall be identified, as well as the parameters being monitored or generated.

When built-in references are employed, a method of test or measurement shall be identified or, if not required, a narrative justification shall be documented.

5.3 System Test Points. The design activity shall ensure measurements can be accomplished; test points are identified in technical data, and are accessible with minimum disturbance to configuration of the system and/or equipment.

5.4 Test, Measurement, and Diagnostic Equipment.

5.4.1 Recommended TMDE. The design activity shall ensure that TMDE is recommended to satisfy all measurement requirements identified in accordance with sections 5.1 and 5.2 of this standard.

a. The TMDE recommended shall be capable of functioning in the system operational measurement environment and satisfy all parameters of each measurement (see 5.4.3).

b. Where several items of TMDE are used in combination, the overall test configuration specification and uncertainty shall be documented.

5.4.2 TMDE in support of TMDE.

a. The design activity shall identify calibration equipment and standards required to support TMDE recommendations which are not currently supportable (i.e. not listed with calibration procedures and intervals) by the applicable military department metrology and calibration program.

b. Refer to Air Force TO 33K-1-100-1, -2, Army TB 43-180, Navy NAVAIR 17-35MTL-1, or Marine Corps TM-10510-14/1 to determine TMDE supportability. Refer to Air Force TO AFCAV, Army TB 43-180 or Navy NAVAIR 17-35NCE-1 and MIL-HDBK-300 to identify existing military department calibration equipment and standards.

c. If existing applicable military department calibration equipment and/or standards will not meet the requirements, the design activity shall recommend equipment and/or standards and a narrative justification shall be documented.

d. The design activity shall assess specifications of the calibration equipment and standards used in support of other TMDE. The calibration equipment and standards identified shall satisfy all parameters of each measurement and comply with the requirements set forth in this standard (see 5.4.3).

5.4.3 Test Uncertainty Ratio (TUR). The recommended TMDE shall be capable of measuring or generating to a higher accuracy than the measurement parameters being supported. Unless otherwise specified, a minimum TUR of 4 to 1 is desired. The actual TUR shall be documented. If a TUR of 4 to 1, or the specified TUR, cannot be achieved, the design activity shall analyze the measurement requirements and provide documented justification for the lesser TUR. A TUR of 4 to 1 is not required when the TMDE only provides input stimuli which are not used to characterize performance of the operational equipment or other TMDE. In this case, a minimum TUR of 1 to 1 is acceptable.

5.4.4 Automatic Test Equipment.

5.4.4.1 ATE Design. The ATE performance specifications shall be more accurate than the system or equipment operational requirements (see 5.4.3).

5.4.4.2 ATE Technical Description.

a. The design activity shall determine the ATE capabilities actually used for UUT testing.

b. TMDE recommended for test, measurement, and calibration of ATE shall be selected to support

ATE capabilities actually being used for UUT testing and ATE self testing.

5.4.4.3 ATE Calibration. The design activity shall assess all functions and parameters required for UUT testing, ATE self test, and calibration of the ATE. ATE calibration is implemented as a test program set (TPS) with the program running on the ATE host computer.

a. The ATE/UUT parameters shall be documented to the ATE/UUT interface utilizing a CMRS.

b. The ATE calibration TPS shall be structured to provide traceability of every calibrated function and parameter to approved national or international standards. External standards and calibrated ATE components shall be used.

c. The ATE calibration TPS shall calibrate the ATE to a TUR of 4 to 1 when possible (see 5.4.3).

This includes, but is not limited to, the most stringent support requirements of the UUT.

d. In the case of ATE that uses built-in calibration standards, these standards shall be identified with their full measurement and stimuli capabilities (see 4.1c) in the CMRS.

e. Calibration standards or calibration procedures used to support built-in standards shall be recommended in the CMRS.

6. NOTES

6.1 Intended Use. This document provides a means for calibration and measurement traceability to ensure system operational integrity and accuracy.

6.2 Associated Data Item Descriptions (DIDs). When it is necessary to obtain the data, the applicable DID must be listed on the Contract Data Requirements List (DD Form 1423), except where the DoD Federal Acquisition Regulation Supplement exempts the requirement for a DD Form 1423. DIDs can be obtained by going through the ASSIST database located at https://assist.daps.dla.mil .

DID Number DID Title

DI-QCIC-80278 Calibration and Measurement Requirements Summary (CMRS)

The ASSIST Online database at https://assist.daps.dla.mil. must be researched to ensure that only current and approved DIDs are cited on the DD Form 1423.

6.3 Subject Term (keyword) Listing.

Metrology Parameters Specifications Standards Test Accuracy Ratio Test uncertainty ratio Tests Traceability Uncertainty

6.4 Changes from previous issue. Marginal notations are not used in this revision to identify changes with respect to the previous issue due to the extent of the changes.

CONCLUDING MATERIAL

Custodians: Preparing Activity:

Army - MI Air Force – 36 Navy - OS Air Force – 84 Agent:

Air Force – 99

(Project QCIC-2010-003)

Review Activities:

Army - AR, AT, AV, CR, TM Navy - AS, EC, MC, NM, SH, TD Air Force - 11, 13, 19

NOTE: The activities listed above were interested in this document as of the date of this document. Since organizations and responsibilities can change, you should verify the currency of the information above using the ASSIST Online database at https://assist.daps.dla.mil.