DD 1423 and Data Item Descriptions (DIDs).pdf

DD FORM 1423-1, FEB 2001

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this 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 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 OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

A(FY 24) x

Torque Multiplier Calibration System & Ki

A001 Commercial-Off-The-Shelf (COTS) Manual

DI-TMSS-80527D PD 24M-232A-TQ Atch AFLCMC/WNMM

N/A

N/A A

ASREQ

ASREQ

See BLK 16

See BLK 16

1. AFMETCAL

Attn: Tom Carson 2 813 Irving-Wick Drive W Horton Bldg

Heath, Ohio 43056

0 5 0

Blk 12: No later than 90 day after contract award 2 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 electronically, the file or web link may be sent thomas.carson.2@us.af.mil. Reference contract number in all correspondence.

Blk 13: No later than 120 days after contract award, concurrent with delivery of first production unit, the contractor shall furnish and pack 1 set of manuals with each of the first production unit. Manuals shall be on CD/DVD in Indexed Portable Document Format (iPDF). Ship with unit.

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

4/4/2024

1 6

MORETTI.MEGAN

.ANN.1623937085

Digitally signed by

MORETTI.MEGAN.ANN.1623937

Date: 2024.04.09 08:45:33 -04'00'

POPSON.SHAN

E.P.1534986587

Digitally signed by

POPSON.SHANE.P.1534986587

Date: 2024.04.09 09:21:35 -04'00'

Attachment 2

DD FORM 1423-2, AUG 96

(2 Data Items)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 220 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this 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 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 OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

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

TDP ________ TM _______ OTHER _________________________

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page ____ of ____ Pages

A (FY 24) ✘

Torque Multiplier Calibration System & Ki

A002 Calibration Certificate

DI-QCIC-80798C PD 24M-232A-TQ Atch AFLCMC/WNMM

N/A

N/A A

ASREQ

ASREQ See BLK 16

See BLK 16

Ship with unit 3

0 3 0

BLK 12: Concurrent with delivery of production unit, the contractor shall furnish and pack one (1) calibration certificate. Ship with unit.

A003 FAILURE SUMMARY AND ANALYSIS REPORT

DI-SESS-80255B PD 24M-232A-TQ Atch AFLCMC/WNMM

N/A

N/A A

ASREQ

ASREQ

See BLK 16

See BLK 16

Ship with unit 1

0 1 0

BLK 12: A complete Failure Summary and Analysis Report shall be provided once at the end of every Fiscal Year (once/if warranty repairs begin).

4/4/2024

2 6

MORETTI.MEGAN

.ANN.1623937085

Digitally signed by

MORETTI.MEGAN.ANN.1623937

Date: 2024.04.09 08:48:02 -04'00'

POPSON.SHAN

E.P.1534986587

Digitally signed by

POPSON.SHANE.P.1534986587

Date: 2024.04.09 09:22:43 -04'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this 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 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 OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

A(FY24) x

Digital Theodolite

A004 Software User Manual

DI-IPSC-81443A PD 24M-232A-TQAtch AFLCMC/WNMM

N/A

N/A A

ASREQ

ASREQ

See BLK 16

See BLK 16 Ship with unit 3

0 3 0

BLK 12: Concurrent with delivery of production unit, the contractor shall furnish and pack one (1) software user manual with each unit. Ship with unit.

4/4/2024

3 6

MORETTI.MEGAN

.ANN.1623937085

Digitally signed by

MORETTI.MEGAN.ANN.1623937

Date: 2024.04.09 08:46:45 -04'00'

POPSON.SHAN

E.P.1534986587

Digitally signed by

POPSON.SHANE.P.1534986587

Date: 2024.04.09 09:23:07 -04'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this 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 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 OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

B(FY 25-28) x

Torque Multiplier Calibration System & Ki

B001 Commercial-Off-The-Shelf (COTS) Manual

DI-TMSS-80527D PD 24M-232A-TQ Atch AFLCMC/WNMM

N/A

N/A A

ASREQ

ASREQ

See BLK 16

See BLK 16

Ship with unit 10

0 10 0

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

The listed number of copies is the maximum amount for the acquisition. Specific quantities will be identified by issuance of a modification to exercise option quantities.

4/4/2024

4 6

MORETTI.MEGAN

.ANN.1623937085

Digitally signed by

MORETTI.MEGAN.ANN.1623937

Date: 2024.04.09 08:45:54 -04'00'

POPSON.SHAN

E.P.1534986587

Digitally signed by

POPSON.SHANE.P.1534986587

Date: 2024.04.09 09:22:35 -04'00'

DD FORM 1423-2, AUG 96

(2 Data Items)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 220 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this 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 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 OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

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

TDP ________ TM _______ OTHER _________________________

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page ____ of ____ Pages

B (FY 25-28) ✘

Torque Multiplier Calibration System &

B002 Calibration Certificate

DI-QCIC-80798C PD 24M-232A-TQ Atch AFLCMC/WNMM

N/A

N/A A

ASREQ

ASREQ See BLK 16

See BLK 16

Ship with unit 10

0 10 0

BLK 12: Concurrent with delivery of production units, the contractor shall furnish and pack one (1) calibration certificate. Ship with unit.

The listed number of copies is the maximum amount for the acquisition. Specific quantities will be identified by issuance of a modification to exercise option quantities.

B003 FAILURE SUMMARY AND ANALYSIS REPORT

DI-SESS-80255B PD 24M-232A-TQ Atch AFLCMC/WNMM

N/A

N/A A

ASREQ

ASREQ

See BLK 16

See BLK 16

Ship with unit 1

0 1 0

BLK 12: A complete Failure Summary and Analysis Report shall be provided once at the end of every Fiscal Year (once/if warranty repairs begin).

The listed number of copies is the maximum amount for the acquisition. Specific quantities will be identified by issuance of a modification to exercise option quantities.

4/4/2024

5 6

MORETTI.MEGAN

.ANN.1623937085

Digitally signed by

MORETTI.MEGAN.ANN.1623937

Date: 2024.04.09 08:46:32 -04'00'

POPSON.SHAN

E.P.1534986587

Digitally signed by

POPSON.SHANE.P.1534986587

Date: 2024.04.09 09:22:51 -04'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this 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 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 OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

B(FY25-28) x

Torque Multiplier Calibration System & Ki

B004 Software User Manual

DI-IPSC-81443A PD 24M-232A-TQAtch AFLCMC/WNMM

N/A

N/A A

ASREQ

ASREQ

See BLK 16

See BLK 16 Ship with unit 10

0 10 0

BLK 12: Concurrent with delivery of production unit, the contractor shall furnish and pack one (1) software user manual with each unit. Ship with unit.

The listed number of copies is the maximum amount for the acquisition. Specific quantities will be identified by issuance of a modification to exercise option quantities.

4/4/2024

6 6

MORETTI.MEGAN

.ANN.1623937085

Digitally signed by

MORETTI.MEGAN.ANN.1623937

Date: 2024.04.09 08:47:06 -04'00'

POPSON.SHAN

E.P.1534986587

Digitally signed by

POPSON.SHANE.P.1534986587

Date: 2024.04.09 09:22:59 -04'00'

DATA ITEM DESCRIPTION

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

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.

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.

Title: FAILURE MODES, EFFECTS, AND CRITICALITY ANALYSIS

Number: DI-SESS-81495B Approval Date: 20190516

AMSC Number: N10028 Limitation: N/A

DTIC Applicable: Yes GIDEP Applicable: Yes http://www.dtic.mil/dtic/submit http://www.gidep.org/data/submit.htm

Preparing Activity: AS Project Number: SESS-2019-016

Applicable Forms: N/A

Use/relationship:

The Failure Modes, Effects, and Criticality Analysis (FMECA) identifies independent single item failures and the resulting potential impact on mission success, performance, safety, and maintainability. The FMECA promotes corrective actions by identifying potential failure risk and maintainability issues in order that appropriate corrective actions may be taken early to eliminate or control high risk items to improve operational readiness and reduce life cycle cost. The FMECA also establishes the baseline engineering information to identify and eliminate or control all failure modes throughout the systems life cycle. The FMECA analytics establish the basis for fault detection, fault isolation, operator and maintainer failure recognition, depot test parameters and lay-in repair parts.

This Data Item Description (DID) contains the format, intended use information, and content preparation instructions for the data product generated by the specific and discrete task described in the solicitation, and should be tailored appropriately.

This DID supersedes DI-ILSS-81495A.

Requirements:

1. Format. The Failure Modes, Effects, and Criticality Analysis (FMECA) shall be in contractor’s format.

2. Content. These data shall explicitly show and document the relationship of the FMECA to the systems architecture and engineering artifacts and analysis, as required by the contract statement of work, and shall include:

a. Identification of how the FMECA aligns to the digital systems engineering environment.

b. Identification of the system overview, operational profile, scope, level of analysis, assumptions, summary of results, documentation of the data sources and techniques used in performing the analysis, and worksheets used during the analysis. The worksheets shall be organized to first display the highest indenture levels of the system. Sample worksheets for

Failure Modes Effect Analysis (FMEA) and Criticality Analysis (CA) are shown in Figures 1 and 2, respectively not all inclusive.

Attachment 2 http://www.dtic.mil/dtic/submit http://www.gidep.org/data/submit.htm

DI-SESS-81495B

c. Analysis performed for all mission profile(s), under worst-case conditions, which shall document and relate all associated failure modes from the piece part (or lowest indenture level specified) through all indenture levels through the subsystem and system levels, as well as identifying severity levels (categories I through IV) for each indenture level. All single-point failure modes shall be identified, evaluated and design mitigation documented.

d. Identification of those failure modes which are detectable by Built-In-Test (BIT) and to what level they will be isolated. When failures are identified as undetectable but the failure has no effect on the mission, the consequences of a second, separate item failure shall be analyzed. For those cases in which the mission would be jeopardized by the second failure, it shall be determined whether or not a failure indication would now be evident to the operator, maintainer, or detectable by BIT. The report shall also identify failure modes that result in an out-of-tolerance condition or loss of functionality rather than a “hard” failure. The report shall identify the extent to which system monitoring and warning features will provide warning of impending failure, to facilitate corrective action during a preventive maintenance period.

e. Identification of both the preventive maintenance provisions which would minimize the probability of occurrence and the corrective maintenance features which would minimize downtime in the event of occurrence, and a description of the methodology and controls used to ensure the preventive and corrective actions are adequate.

f. Identification and description of the hardware and software design provisions for maintenance by modular replacement, indication probable adjustment requirements following repair, and identification of the first point at which the post-repair checkout can be made to verify that the maintenance action is complete.

g. A description of the impact of the FMECA analysis on design, maintenance planning/supportability, and diagnostics. Major problems detected by the analysis shall be detailed, including how the problems were resolved (e.g. design changes, etc), including impacts on safety, supportability, and diagnostics. Contractor rationale and comments concerning the analysis and identification of the critical items list and initiated or recommended actions for control of failure risk shall be included.

h. A description of how the FMECA is used in and aligned to the Fault Tree Analysis (FTA), Reliability Centered Maintenance (RCM) analysis, Maintenance Task Analysis (MTA), and

Level of Repair Analysis (LORA).

i. Identification of information necessary for investigating root cause is identified and documented in FMECA to include

The root cause(s) is identified

Failure compensation based on appropriate technical or statistical analyses that fully address the root cause(s) mitigation

j. A summary which shall include contractor conclusions and recommendations based on the analysis results and problem information included in the report.

Figure 1 – Sample FMEA Worksheet

A – Serial number, Logistics Control Number (LCN) or other reference designation identification number is assigned for traceability purposes.

B - The name or nomenclature of the item or system function being analyzed for failure mode and effects.

C – The first function shall be numbered 01, the second 02, and so on.

D - A concise statement of the performance required by the function performed by the item including any performance standards.

E – The first functional failure shall be numbered A, the second B, and so on.

F – Ways an item can either partially (with upper and/or lower performance limits) or totally fail to perform its functions.

G - All predictable failure modes along with their root cause(s) for each indenture level analyzed shall be identified and described.

H - A concise statement of the mission phase descriptions, operational mode and system Con-Ops requirements in which the failure occurs.

I - Local performance effects identify the impact a failure mode has on the operation and function of the item in listed in block A.

J - Next higher level performance effects identify the impact an assumed failure has on the operation and function of the items in the next higher indenture level above the indenture level under consideration.

K - End effects evaluate and identify the total performance effect a failure has on the mission and the surrounding environment.

L - A description of the methods by which occurrence of the failure mode is detected by the operator at the system level.

M - Describe the most direct procedure that allows a maintainer to isolate the malfunction or failure.

Describe the method by which ambiguities are resolved when more than one failure mode causes the same failure indication. Identify to what indenture level failures can be isolated by the use of BIT features and indicate when ancillary test equipment will be required for fault isolation.

N - The compensating provisions, either design provisions or operator actions, which circumvent or mitigate the effect of the failure.

O - Severity classification categories (I-IV) assigned to each failure mode, without considering compensating provisions, according to the failure effect at the uppermost system. The severity classification categories are:

Category I - Catastrophic - A failure which may cause death or system loss (i.e., aircraft, tank, missile, ship)

Category II - Critical -A failure which may cause severe injury, major property damage, or major system damage which will result in mission loss.

Category III - Marginal -A failure which may cause minor injury, minor property damage, or minor system damage which will result in delay or loss of availability or mission degradation.

Category IV - Minor - A failure not serious enough to cause injury, property, or system damage, but which results in unscheduled maintenance or repair.

P - Describe the basic actions taken by the maintainer to correct the failure.

Q - Any pertinent remarks or Contractors Rationale pertaining to and clarifying any other columns or recommendations for design improvements.

Figure 2 – Sample Criticality Analysis Worksheet

Columns A, B, D, G, H, O, & Q on the Criticality Analysis worksheet are copied from the FMEA worksheet.

R – Failure probability or Failure rate data source - When failure modes are assessed in terms of probability of occurrence (Levels A-E):

Level A – Frequent: High probability of occurrence that may be defined as a single failure mode probability greater than or equal to 10-1 of the overall probability of failure during the operating time interval.

Level B – Reasonably probable: Reasonable probability of occurrence that may be defined as a single failure mode probability of occurrence which is more than 10-2 but less than 10-1 of the overall probability of failure during the item operating time.

Level C – Occasional: Occasional probability of occurrence that may be defined as a single failure mode probability of occurrence which is more than 10-3 but less than 10-2 of the overall probability of failure during the item operating time.

Level D – Remote: Remote probability of occurrence that may be defined as a single failure mode probability of occurrence which is more than 10-6 but less than 10-3 of the overall probability of failure during the item operating time.

Level E – Extremely unlikely: Extremely unlikely may be defined as a single failure mode probability of occurrence which is less than 10-6 of the overall probability of failure during the item operating time.

When failure rate data are to be used in the calculation of criticality numbers (column W), the data source of the failure rates used in each calculation shall be listed. When a failure probability is listed, the remaining columns S-V are not required.

S - The conditional probability that the failure effect will result in the identified criticality classification, given that the failure mode occurs. The values represent the analyst's judgment as to the conditional probability the loss will occur and should be quantified in general accordance with the following:

Actual loss 1.0

Probable Loss > 0.10 to <1.0

Possible Loss >0 to = 0.10

No Effect = 0

T - The fraction of the part failure rate related to the particular failure mode under consideration.

U - The failure rate from the appropriate reliability prediction.

V - The operating time of the item per mission shall be derived from the government approved operational concept or System Requirements Specifications.

W – A relative measure of consequence of a failure mode and its frequency of occurrence.

X – A relative measure of consequence of an item failure and its frequency of occurrence.

End of DI-SESS-81495B

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 CSCl'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-8 l 444A).

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 pref erred over including the description itself.

D1-IPSC-81443A

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

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:

I) 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.

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-81443A

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.

DID Failure