Data_Item-Descriptions.pdf

DATA ITEM DESCRIPTION

Title: REPAIR/MODIFICATION/OVERHAUL STATUS REPORT

Number: DI-MGMT-80933A Approval Date: 20170531

AMSC Number: 9812 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: MI Project Number: MGMT-2017-024

Applicable Forms: N/A

Use/relationship: This Data Item Description (DID) provides information on contractual maintenance programs applicable to military equipment.

a. This 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 supersedes DI-MGMT-80933.

Requirements:

1. Reference documents. None.

2. Format. The Repair/Modification/Overhaul Status Report shall be in a contractor selected format.

3. Content. The Repair/Modification/Overhaul Status Report content shall be as follows:

a. Contract Number.

b. National Stock Number for each item prior to work.

c. Program quantity for each National Stock Number item.

d. Quantity completed to date on each National Stock Number item.

e. Work in process quantity on each National Stock Number item.

f. Unserviceable on hand quantity to date on each National Stock Number item.

g. Identification and explanation of delays, accelerations, and problems.

h. Consumption data.

i. Charges billed to date.

End of DI-MGMT-80933A.

Source: http://assist.dla.mil -- Downloaded: 2020-03-24T15:26Z Check the source to verify that this is the current version before use.

Title: ANALYTICAL CONDITION INSPECTION (ACI) REPORT

Number: DI-MISC-81391A Approval Date: 20180326 AMSC Number: F9914 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFLCMC/EZFS) Project Number: MISC-2018-008 Applicable Forms: N/A Use/Relationship: The Analytical Condition Inspection (ACI) Report will be used to reveal damage (flaw, defect, crack, corrosion, disbond, delamination, discontinuity, or other type that degrades or has the potential to degrade the performance of the affected component) that may not otherwise be detected through normal technical order (TO) and programmed depot maintenance (PDM) inspections and to provide data for engineering and technical evaluations of the relative condition of the mission, design and series (MDS) aircraft. Data generated through ACI Reports is used to refine mandatory aircraft inspection programs (field and depot).

This DID contains the format, content and intended use information for the data deliverable resulting from the technical requirements described in Task V of MIL-STD-1530, Aircraft Structural Integrity Program (ASIP), and Subtask 3 of MIL-STD-1798, Mechanical Equipment and Subsystems Integrity Program.

(Copies of these documents are available online at http://quicksearch.dla.mil.)

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 ACI Report shall be in the contractor’s format.

3. Content. The ACI Report shall include the following information:

3.1 ACI Work Instructions - for each inspection/inspection location:

a. Identification number.

b. Part name/description of article to be inspected.

c. Part number(s).

d. Part criticality – safety or fracture critical, durability or maintenance (Mx) critical, normal controls, etc.

e. Area/location of inspection.

f. Reason for inspection.

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

Source: http://assist.dla.mil -- Downloaded: 2020-03-25T18:15Z http://quicksearch.dla.mil/

DI-MISC-81391A

g. Frequency of inspection.

h. Type of inspection.

i. Instructions for accessing article to be inspected.

j. Inspection procedures and potential/anticipated damage.

3.2 ACI Inspection Results:

a. Pertinent aircraft identifying information:

(1) Aircraft mission design series (MDS).

(2) Aircraft serial number (SN).

(3) Base assignment history.

(4) Planned ACI start and end date.

(5) Actual ACI start and end date.

(6) Actual flight hours.

(7) Equivalent flight hours.

(8) Last programmed depot Mx date.

b. Information for each inspection location:

(1) ACI work instruction identification number.

(2) Date of inspection.

(3) Description of inspected article condition.

(4) If damage found, damage classification (minor, major, or critical):

(a) Detailed description, sketches, drawings, and photographs documenting damage, for damage types, sizes, locations, and orientations.

(b) Part number and criticality classification.

(c) Work Unit Code for item with defect.

(d) How malfunction codes/root cause determination.

(e) Engineering and nondestructive inspection records.

(f) Action taken code/damage disposition (no action required, repair, replace, etc.)

with documentation.

(5) Record of inspection:

(a) Date and time of inspection.

(b) Name and organization of inspector.

(c) Location of inspection (e.g., RAFB (Robins Air Force Base), HAFB (Hill Air Force Base), TAFB (Tinker Air Force Base), location of contractor facility, etc.).

c. Summary of results and recommendations.

(1) Summary of inspection findings.

DI-MISC-81391A

(2) Prioritized list of critical and major findings.

(3) Recommendations for revisions to maintenance requirements at the depot and/or field levels.

End of DI-MISC-81391A.

Source: http://assist.dla.mil -- Downloaded: 2020-03-25T18:19Z

Source: http://assist.dla.mil -- Downloaded: 2020-03-25T18:21Z

Source: http://assist.dla.mil -- Downloaded: 2020-03-25T18:21Z

DATA ITEM DESCRIPTION I Form Approved OMB No.0704.0188

1.nTLE 2.IOENTIFICATIONNUMBER

TEST/ INSPECTION REPORT DI-NM’I-80809B

L OESCRIPTlOtVPURPOSE

3.1 The testl inspection report is used to document testl inspection results, findings, and analyses that will enable the government or contracting agency to evaluate compliance with system requirements, performance objectives, specifications, and test linspection plans.

1.APPROVALDATE 5.OFFICEOFPRIMARYRESPONSIBILITY(OPB) Ea.DTICAPPLICABLE 6b.CWIEP AppliCable

(YVMMOD)

F/AFMC-DCJP

970124

,.APPLlCAT\0NflNTER7iElAT10NSH1P

7.1 This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement

I as delineated in the contract.

I

7.2 This DID is applicable to engineering (developmental ), preliminary qualification, qualification, and acceptance testing.

7.3 This DID supersedes DI-NDTI-80809A and DI-MISC-80653

1.APPROVALLIMITATION 9a.APPLICABLEFORMS 9b.AMSCNUMBER

F7231

10,PREPARATIONlNSTRUCnONS

10.1 Format. Contractor format is acceptable.

paragraph 10.2 and its subparagraphs in a manner understanding

10.2 CQnL!aL. The test/inspection report shall

applicable.

Organize the information required by that facilitates presentation and contain the following information, as

10. 2.1 Cove. and tile uaae. The following information shall appear on the outside front :over and title page:

a. Report date.

b. Report number (contractor or government)

Contractor’ s name, address, and commercia 1 and government entity code.

Contract number and contract line item number or sequence number (if applicable)

e. ‘fvpe of test/inspection (for example. first article acceptance test, aualitv con formanc-e-inspection, d-evelopmental test-, qualification test, f Identification of item tested/inspected.

9. Date or period of test/inspection.

h. Name and address of requiring government activity.

i. Security classification, downgrading and declassifying environmental Lest) .“ information, if applicable.

(Continued on page 2 )

1.DIS77UBUTIONSTATEMEW

DISTRIBUTION STATEMRNT A : APPROVED FOR PUBLIC RELBASE; DISTRIBUTION IS UNLIMITED.

ID Form 1664,APR 89 PreviOLIsedtliomwe obsdem. Page 1 of & Pages 39123

Source: http://assist.dla.mil -- Downloaded: 2020-03-25T18:26Z

DI-NDTI-80809B

Block 10, Preparation Instructions (continued)

10.2.2 ~. The table of contents shall identify the following:

a. The title and starting page of each major section, paragraph, and apPendix of the report.

b. The page, identifying number, and title of each illustration (for example; figure, table, photograph, chart, and drawing)

10 .2.3 -ductim. The introduction shall include the following information:

10.2 .3.1 obyectlve W. The specific test/ inspection objective (s) as specified in the contract tasking document.

10. 2.3.2 L.temls) tes~. Complete identification of the item(s) testedl inspected including the following:

a. Nomenclature.

b. National stock number.

Model number, part number t and serial number :: Type of item (for example, prototype, production item, laboratory model )

e. Serial or lot number.

f. Applicable engineering changes

9. Production item specification, if applicable.

h. Date of manufacture.

10.2 .3.3 Complete inspection requirements correlated to contractual following:

Required testl inspection parameters :: Performance requirements, acceptance or environmental criteria.

10.2.4 ~. Complete test/inspection report following:

identification of the testl requirements including the compliance limits, and summary including the

a. A brief discussion of the significant test/inspection results, ObSerVati Qns, conclusions, and recommendations covered in greater detail elsewhere in the report.

b. Proposed corrective actions and schedules for failures or problems encountered.

c. Identification of deviations, departures, or limitations encountered, referenced to the contract requirements.

d. Tables, graphs, illustrations, or charts as appropriate to simplify the summary data.

10.2.5 ~. Complete identification of all documents referenced in the test finspection report including the following, as applicable:

a. Prior testf inspection reports on the same item.

b. Test /inspection plans and procedure documents

c. Prior certifications of compliance.

d. Contractor’ s file designation where test/ inspection records are maintained.

e. Input parameters used.

The applicable issue of the documents cited therein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

Page 2 of 4 Pages Source: http://assist.dla.mil -- Downloaded: 2020-03-25T18:26Z

10.2.6 ~. The body of the testlinspection report shall be as follows :

10 .2.6.1 KzZL_ + de.tlflca~.

Complete identification of each item of test equipment used in the testlinspection including the following:

a.

b.

c.

d.

e.

f.

9.

10. 2.6.2

Nomenclature.

Model number.

Serial number.

Manufacturer.

Calibration status.

Accuracy data.

Comments, if applicable.

Testlinmection kuhtv mstd.b&mn and set–w. Complete description of the physical set-up used in conducting the test/inspection to include the following:

a. Location or orientation of the item.

b. Location. orientation, or settinm of test equipment and instrumentation.

c. Location, orientation, or settings of sensors and probes

d. Location or orientation of interconnections, cables, and hoop-ups.

e. Electrical power, pneumatic, fluidic, and hydraulic requirements.

Drawings, illustrations, and photographs maY be used for clarification.

10 .2.6.3 wrocedur~. Complete description of the procedures used in conducting the test/inspection to include the following:

a. Item selection and inspection that verified suitability for test/ inspection.

b. Summarized sequence of testing/inspection steps, including a description of how the item was operated during the test/inspection, and any control conditions imposed.

10 .2.6.4 A copy of all testlinspection results and analysis to include the following:

10.2.6 .4.1 ~. The actual recorded data (for example, log book entries, oscillographs, instrument readings, plotter graphs) If the recorded data is extensive, provide it in an appendix.

10. 2.6.4.2 Test/ insQec!iion resu. Identification of all testlinspection results to include the following:

a. Matrices comparing results achieved against test/inspection objectives or requirements

b. A discussion of these matrices as to their significance, and how they compare to any prior testlinspections.

Calculation examples.

;; Discussion of anomalies, deviations, discrepancies, or failures, including their impact, causes, and proposed corrective actions The discussion shall address discrepancies between design requirements and the tested/inspected Configuration.

10. 2.6.5 Conclusicxls Test/ inspection conclusions distinguished between objective and subjective to include the following:

a. The effectiveness of the testlinspection procedures in measuring item performance.

Page 3 of 4 PagesSource: http://assist.dla.mil -- Downloaded: 2020-03-25T18:26Z

b. The success or failure of the item to meet required test/inspection objectives.

c. The need for repeat, additional, or alternative tests linspections.

d. The need for item redesign or further development.

e. The need for improved test/inspection procedures, techniques, or facilities.

f. The adequacy and completeness of the test/inspection requirements.

10.2 .6.6 Recommendations appropriate to the test/inspection results and conclusions including the following:

a b.

c.

d.

e.

f.

9.

h.

Acceptability of the item tested/inspected (pass or fail) Additional testing/inspection required. ,.

Redesign required.

Problem resolution.

Test/inspection procedure or facility improvements Disposition of items tested/inspected.

Documentation changes required.

Testing/ inspection improvements

10.2.7 The following certifications shall be included, .as

applicable:

10.2 .7.1 A statement that the testlinspection was performed in accordance with applicable testlinspection plans and procedures, and that the results are true and accurate. The authentication shall include the signature of the contractor personnel that performed the test(s) /inspection(s) , a contractor representative authorized to make such certification, and any government witnesses

10.2 .7.2 A statement identifying those requirements not tested/inspected or measured that were previously validated.

Include identification of the data and method employed for such validation (for example, prior test/inspection, analytical verification, equivalent item, and so on) The authentication shall include the signature of a contractor representative authorized to make such authentication and any government witness.

10.2 .7.3 A statement that the item tested/ inspected either passed or failed item acceptability requirements This authentication shall include the signature of a contractor representative authorized to make such authentication and any government witness

10.2.8 Appendices shall be used to append detailed

test/inspection daia, drawings, photographs , or other documentation too voluminous to include in the main body of the report This includes referenced documentation not previously provided by the government, and test/ inspection reports from any associated test/inspection activity that may have performed some of the testing/inspecting requirements.

Page 4 of 4 Pages Source: http://assist.dla.mil -- Downloaded: 2020-03-25T18:26Z

Source: http://assist.dla.mil -- Downloaded: 2020-10-22T15:51Z

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:46Z

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:46Z

Data Item Description

Title: Scanning/Digitizing Data Approval Date: 01 June 01 Number: DI-ALSS-81610 AMSC Number: G7440 DTIC: N/A GIDEP Applicable: No Office of Primary Responsibility: G/DA12-TDM

Description/Purpose Provides minimum scanning recommendations for responsible conversion and to achieve an acceptable level of image quality. The document addresses these formats: text, photographs, and graphic materials. As a rule, the key to quality scanning is to scan at the resolution that matches the information content of the original, not necessarily at the highest resolution possible. The scanning shall be provided to ensure a consistent and high quality image and decrease the likelihood of re-scanning.

Application/Interrelationship This Data Item Description (DID) contains the format and preparation instructions for scanning documentation.

Requirements:

1. Format.

1.1 Use the original or first generation be used to achieve the best quality image.

1.2 Types of Scanning:

1.2.1 Bitonal - One pixel representing black and white. Bitonal scanning is best suited to high-contrast documents such as printed text.

1.2.2 Grayscale - Multiple bits per pixel representing shades of gray. Grayscale is suited to continuous tone documents such as black and white photographs.

1.2.3 Color - Multiple bits per pixel representing color. Color scanning is suited to documents with color information.

1.3 These three modes of scanning require some subjective decisions. Documents, including black and white test with color makes manuscripts, older printer matter, might be scanned in color to bring out special meaning or information identified through the color notation and markings. Although bitonal scanning is often used for type scanning as continuous tone in grayscale or color to being out the shade and conditions of the paper and the marks inscribed on it.

2. Material formats. The following defines the minimum standards based on the following format types, text, photographs, maps, graphic material and three-dimensional material represented in two-dimensional format.

2.1 Tonal depth: Bitonal

Format: TIFF Compression: Uncompressed Spatial Resolution: 600dpi

2.2 For handwritten or manuscripts that are difficult to read, consider providing a transcript of text using an Optical Character Reader (OCR). Consideration must be give to the cost of keying the transcription.

2.3 Portable Document Format (PDF) shall be used as the format for creating and displaying text-based files on the web. The Adobe Acrobat viewer can be downloaded at no charge to view the documents.

2.4 Since many digitization projects are undertaken to increase access, the digital image as a preservation copy is a natural by product.

Page 1 of 2 Pages

Source: http://assist.dla.mil -- Downloaded: 2020-10-22T15:56Z

DI-ALSS-81610

2.5 Consider current and future user needs, as well as the unique requirements of specific types of materials and collections.

2.6 Scan at the highest resolution appropriate to the content of the original.

2.7 Scan at a resolution level to avoid re-scanning in the future.

2.8 Create and store master image, allowing for production of derivative images for current and future use.

2.9 Create appropriate backup files and store media in an appropriate environment.

2.10 Consider grayscale over bitonal, color over grayscale.

2.11 Use objective measurements to determine scanner settings. Do NOT attempt to make the image look good on a particular monitor or use image processing to correct color.

2.12 Do not compress digital masters, unless a lossless compression is used.

3. Quality Control. A quality control program shall be conducted throughout all phases of the digital conversion process. Inspections of final digital image files should be incorporated into the project workflow. Typically, master image files are inspected via CD batch or online for a variety of defects. Depending on the project, the project can inspect 100% of the master images, or inspect a random selection of the files. A 10% sample is generally used. It is recommended that quality control procedures be implemented and documented and that specific defects found unacceptable in the image be defined. Images should be inspected while viewing at 1:1 pixel ratio or at 100% magnification or higher.

3.1 Quality is evaluated both subjectively by project staff through visual inspection and objectively in the imaging software. The viewing environment for visual inspection of images is also important. Evaluation criteria for the visual inspection may include:

3.1.1 Image is not the correct size

3.1.2 Image is not the correct resolution

3.1.3 File name is incorrect

3.1.4 File format is incorrect

3.1.5 Image is in incorrect mode, i.e. color image has been scaled as grayscale

3.1.6 Loss of detail in highlights or shadows

3.1.7 Excessive noise especially in dark areas of shadows

3.1.8 Overall too light or too dark

3.1.9 Uneven tonal values or flare

3.1.10 Lack of sharpness/Excessive sharpening

3.1.11 Pixalated

3.1.12 Presence of digital artifacts, such as very regular, straight lines across picture

3.1.13 Moiré patterns (wavy lines or swirls, usually found in areas where there are repeated patterns)

3.1.14 Image not cropped

3.1.15 Image not rotated or backward

3.1.16 Image skewed or not centered

3.1.17 Incorrect color balance

3.1.18 Image dull or not tonal variation

3.1.19 Negative curve in the Look-up table

3.1.20 Clipping black and white values (in histogram)

3.1.21 CD recording and Verification

3.1.22 File naming

4. End of DI-ALSS-81610. Page 2 of 2 Pages

Source: http://assist.dla.mil -- Downloaded: 2020-10-22T15:56Z

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:09Z

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:09Z

DI-MGMT-81804A

DATA ITEM DESCRIPTION

Title: Item Unique Identification (IUID) Marking Activity, Validation and Verification Report

Number: DI-MGMT-81804A Approval Date: 20130212

AMSC Number: F9335 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Office of Primary Responsibility: 70 (OO-ALC) Applicable Forms: N/A

Use/relationship: The Item Unique Identification (IUID) Marking Activity, Validation and

Verification Report is a tabular list providing IUID marking activity, validation and verification data such as: physical asset marking, registration, inventory audits, quality audits, and verification/validation results.

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

This DID may be applied in any contract which contains a requirement for marking parts and equipment with IUID encoded in data matrix symbols.

1. Reference document: MIL-STD-130. The applicable issue of MIL-STD-130 shall be the latest version cited online at Acquisition Streamlining and Standardization Information System

(ASSIST) Update, at the time of the solicitation. Other documents referenced in MIL-STD-130 shall also be applied.

2. The Contractor’s format is acceptable. Recommend electronic transfer of information.

3. A representative sample of IUID-related data matrix marks on items in each delivered

Contract Line Item Number/Sub-Contract Line Item Number/Exhibit Line Item Number

(CLIN/SLIN/ELIN) shall be validated and verified. Verification and validation results shall be provided using this report format. Marks failing verification or validation must be replaced with compliant marks prior to government acceptance of the items.

4. The tabular report shall include the following alphanumeric fields:

4.1 Unique Item Identifier (UII).

4.2 UII Type (Construct).

4.3 Enterprise Identifier (EID).

4.4 EID Type (CAGE/NCAGE, DUNS, etc).

4.5 Original Equipment Manufacturer (OEM) Part Number.

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:11Z

DI-MGMT-81804A

4.6 Service Assigned Serial Number (if assigned).

4.7 Original Equipment Manufacturer (OEM) serial number.

4.8 Equipment Nomenclature (name and type).

4.9 National Stock Number (NSN).

4.10 Validation Date.

4.11 Validation Result (Pass/Fail).

4.12 Verification Date.

4.13 Verification Result (Pass/Fail).

4.14 Other Event/Activity Date* (optional).

4.15 Other Event/Activity* (optional).

4.16 For items marked that “Fail” IUID validation or verification, identify corrective action

(whether the item has been re-marked or scrapped).

*Other Event/Activity will be defined in the Contract Data Requirements Lists (CDRLS) if required.

5. The Key attributes for the report are the validation and verification columns which each indicate (Pass/Fail). (NOTE: Most verification apparatus provide electronic records with pass/fail summaries for both verification and validation.)

A “Pass” validation value shall be assigned to records whose data matrix symbol(s) properly encode Item Unique Identification data as prescribed in MIL-STD-130 DoD Standard Practice

Identification Marking of U.S. Military Property requirements for machine readable information

(MRI) marking.

A “Pass” verification value shall be assigned to records whose data matrix symbol(s) meet or exceed MIL-STD-130 DoD Standard Practice Identification Marking of U.S. Military Property requirements for data matrix symbol quality.

6. The Contractor shall ensure machine-readable IUID marks required under this contract are permanently placed on the items subjected to contractually-required performance testing prior to that testing; and further shall include all mark serviceability problems in the item’s test report(s).

7. End of DI-MGMT-81804A.

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:11Z

Title: Quality Program Plan (QPP)

Number: DI-QCIC-81722 Approval Date: 29 NOV 2006 AMSC Number: 7676 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/I5223 Applicable Forms: N/A

Use/Relationship:

The Quality Program Plan (QPP) describes the methodology that will be used to meet the quality requirements needed for the specific program. The object of the plan is to define and document what, where, and how to procure, fabricate, assemble, inspect, test and deliver only units and other end products that conform to quality standards. The QPP should start with the contractor’s standard quality system and detail changes to that. The QPP shall be used to verify attainability of contract objectives in the area of producing reliable, quality products. This DID is applicable to development, low rate initial production and full rate production efforts.

a. This DID contains the format and content preparation instructions for the data product generated by the specific requirement delineated in the contract and International Organization for Standardization (ISO) 9001, Quality Management Systems – Requirements (Entire Document).

b. The prime contractor is required to include information from significant suppliers (eg, PWAs) or teammates regarding their standard quality system requirements and any deviations specific to this program.

1. Reference Documents: The applicable issue of the documents herein, including, their approval dates and the dates of any applicable amendments, notices, and revisions, shall be as cited in the current issue of the DODISS at the time of the solicitation; or, for non DODISS-listed documents, as stated herein. International Organization for Standardization (ISO) 9001 Quality Management Systems – Requirements, current edition, is available at International Organization for Standardization website http://www.iso.org/iso/en/ISOOnline.frontpage.

2. Format: Contractor format is acceptable using 8 ½ x 11 in. paper.

3. Content:

3.1 The data item shall have a Title page containing the following information as a minimum:

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:12Z

DI-QCIC-81722

3.1.1 Title

3.1.2 CDRL exhibit number

3.1.3 Revision level

3.1.4 Approval/submission

3.1.5 Date

3.1.6 Program name

3.1.7 Contract number

3.1.8 Contractor’s name and address

3.1.9 Data item author

3.1.10 Signature

3.1.11 Approval record

3.2 The data item shall have a table of contents if the length of the document warrants.

3.3 The data item shall have a revision status log page which includes the various revision levels, dates, and summary description of the changes made.

3.4 The QPP shall reference any Industry standard for which the contractor has a current certification. The plan shall reference the contractor’s current Quality Manual, number or identification, and date. The plan shall then detail any changes, deletions or additions to the contractor’s standard requirements, and shall delineate the specific Industry workmanship standards and levels for soldering, printed wiring assembly, etc, that are to be applied to the program. The government shall concur in use of any standard repair procedures and conditions for use on the program.

3.5 The QPP shall include an organizational chart identifying the Product Assurance (PA) organization, names and titles of key PA personnel assigned to the program, and how the PA organization relates to the corporate structure.

3.6 The QPP shall include a proposed end item product flow including test & inspection points. The plan shall briefly address the following topics if different from or not included in the quality manual: quality audit frequency, depth, and independence; process certification and control of automated processes; “cannot duplicate” (CND) and nonconforming material processes; incoming inspection/test, certified supplier program and parts control; and any unique requirements for the program.

4. END OF DI-QCIC-81722

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:12Z

Title: FAILURE SUMMARY AND ANALYSIS REPORT

Number: DI-SESS-80255B Approval Date: 20191015

AMSC Number: N10166 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-063

Use/relationship: The Failure Summary and Analysis Report presents a summary of the individual failures that occur prior to and during the reporting period and describes the analysis and corrective actions performed. This report is used to evaluate the contractor’s failure reporting, analysis, and corrective action efforts in accordance with the solicitation.

This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract.

This DID supersedes DI-SESS-80255A.

1. Reference Documents. None

2. Format. The Failure Summary and Analysis Report shall be in contractor’s format.

3. Content. The report shall summarize the results of the contractor’s Failure Reporting, Analysis, and Corrective Action System (FRACAS) implementation required by the statement of work, and shall include a cumulative tabulation of failure data. Failures that occurred during the latest report period shall be identified by suitable notation. The report shall include the following elements at a minimum:

3.1 Failure number

3.2 Failure analysis number

3.3 Failure date

3.4 Name of engineer responsible for failure analysis

3.5 Failed part name

3.6 Failed part number (e.g. national stock number (NSN), logistics control number, work unit code)

3.7 Manufacturer of failed part

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:13Z Check the source to verify that this is the current version before use.

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

DI-SESS-80255B

3.8 Subassembly name and number

3.9 Major assembly name and number

3.10 Equipment name and serial number

3.11 Failed part’s accumulated test or field operational life data

3.12 Test or mission being performed when the failure occurred

3.13 Test or mission mode of operation and environmental and use conditions when the failure occurred

3.14 Failure symptoms and description of detection or diagnosis methods (e.g. Built In Test)

3.15 Failure effects (e.g. none, degradation, abort)

3.16 Repair action (e.g. remove/replace)

3.17 Failure mode description

3.18 Description of engineering analysis method employed in failure analysis

3.19 Failure mechanism/cause of failure

3.20 Contributing factors, including multiple factor interactions, or secondary effects of the failure

3.21 Categorization of failure (e.g. equipment design, equipment manufacturing workmanship, part design, part manufacturing workmanship, software errors, unverified, intermittent, non-relevant)

3.22 Information on previous corrective actions for the same part or failure mode.

Corrective action required to mitigate the failure mode, including:

3.22.1 Identification of the failure mode

3.22.2 The recommended process or process control changes, when the failure cause was due to workmanship defects

3.22.3 Proposals for retrofit of all equipment already delivered or assembled, including recommended effectivity, in accordance with the contract

DI-SESS-80255B

3.22.4 Disposition of all defective material and material rendered obsolete because of any necessary redesign, to assure their exclusion from production items

3.22.5 Identification of previous functional and environmental qualification tests, if any, invalidated by the corrective action changes and a recommendation of those tests that should be repeated, in accordance with the terms of the contract, to demonstrate the corrective action’s effectiveness

3.22.6 Effect on operational and diagnostic software programs and plan for changes, if necessary

3.23 Corrective action status

3.24 The recommended fix effectiveness factor (FEF) to be applied to the failure mode based on the proposed corrective action

3.25 Rationale for any open failure analyses past the contract-specified closeout time

3.26 Severity criticality ranking of the failure modes. The severity classification categories are:

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

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

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

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

End of DI-SESS-80255B

Title: RELIABILITY AND MAINTAINABILITY PREDICTIONS REPORT

Number: DI-SESS-81497B Approval Date: 20191008

AMSC Number: N10110 Limitation: No

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-061

Use/relationship: The Reliability and Maintainability (R&M) Predictions Report documents contractor quantitative predictions of reliability, maintainability, and Built-In-Test (BIT). The report is intended as support for feasibility evaluations, comparison of alternative configurations, identification of potential problems, logistics support planning, life cycle cost studies, determination of data deficiencies, tradeoff decisions, allocation (apportionment) of performance requirements, and criteria for growth testing and demonstration. The R&M predictions report will assist in eliminating or managing high-risk elements, improving readiness, reducing life cycle cost, and assessing whether the design is capable of meeting specification requirements.

This DID supersedes DI-RELI-81497A.

2. Format. The Reliability and Maintainability (R&M) Predictions Report shall be in contractor’s

3. Content. The report shall include:

3.1 System configuration identification.

3.2 Assumptions used in the prediction process.

3.3 Documentation or cross-reference to the data used in performing R&M predictions, including the following:

3.3.1 Hardware parts description, including manufacturer part number and manufacturer

CAGE if applicable

3.3.2 Software Configuration Items description

Source: http://assist.dla.mil -- Downloaded: 2020-11-03T14:40Z Check the source to verify that this is the current version before use.

DI-SESS-81497B

3.3.3 Failure rate data source and assumed operational loads

3.3.4 Failure distributions

3.3.5 Constraints

3.3.6 Item definition, including assembly indenture

3.3.7 Service use profile

3.3.8 R&M block diagrams and mathematical models

3.3.9 Failure Modes, Effects, and Criticality Analysis (FMECA)

3.3.10 Environmental data, including life cycle loads (e.g. engineering mechanical, electrical, and thermal analysis)

3.3.11 Environmental and operating Stress data, including physics of failure analyses

3.4 Description of system BIT, maintenance and support concepts.

3.5 Description of data developed to support system age-reliability relationships (particularly for the identification of life limits) for Reliability-Centered Maintenance (RCM) analysis to develop appropriate life limits or maintenance tasks.

3.6 Description of the R&M prediction procedures used, including methodology, models and tools.

3.7 Results of the analysis performed for field reliability (mission and logistics), maintainability and BIT performance of similar and analogous items operating in the same expected environment.

3.8 Applicable failure rates, failure distributions, failure rate adjustment factors, and reliability variables used in the calculation of each configuration item.

3.9 The source(s) of the data and the evaluated validity of data used in the reliability predictions.

3.10 The operating and environmental stress factors and ratios, along with other factors used in determining part failure rates shall be specified in in the report and shall be individually identified as estimated (i.e. documented subject matter expert (SME) engineering opinion), calculated (i.e. reliability analysis from comparable systems), and measured (i.e. historical reliability from predecessor systems and shall include test and field data).

3.11 How the accumulated operating hours were determined when using field experience data for similar items in a like environment.

3.12 The reliability prediction for each subdivision of the system breakdown structure for each mission, mode of operation, and periods of non-operation and storage from an items final factory acceptance through its terminal expenditure including removal from inventory.

3.13 Maintainability predictions shall be identified for each associated level of maintenance, including both unscheduled and scheduled maintenance, and shall also include repair time source data for the prescribed level of maintenance.

3.14 BIT predictions of the overall system level BIT fault detection, and fault isolation for the overall system.

3.15 Risk assessment and mitigation plans for each configuration item’s reliability, maintainability, and BIT value based upon the data source and maturity of design.

3.16 Conclusions and recommendations based upon the R&M predictions that coincide with the phase of item development and shall specify any indication of the system’s reliability and maintainability status. All R&M deficiencies identified shall be included and shall also contain the course of action to be taken to resolve each deficiency.

End of DI-SESS-81497B

Title: Failure Modes, Effects, and Criticality Analysis Report

Number: DI-SESS-82018 Approval Date: 20160106

AMSC Number: N9616 Limitation: No

DTIC Applicable: Yes GIDEP Applicable: Yes

Defense Technical Information Center GIDEP Operations Center

ATTN: DTIC- Naval Warfare Assessment Center

8725 John J. Kingman Road, Suite 0944 P. O. Box 8000

Fort Belvoir VA 22060-6218 Corona, CA 91718-8000

Preparing Activity: AS Project Number: SESS-2015-007

Use/relationship:

The Failure Modes, Effects, and Criticality Analysis (FMECA) Report provides an analysis of independent single item failures and the resulting potential impact on mission success, performance, safety, and maintainability. This analysis is intended to promote design 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.

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.

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

2. Content. This report shall document the results of the FMECA, as required by the contract statement of work, and shall include:

a. Identification of the system overview, 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.

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

DI-SESS-82018

c. Identification of those failure modes which are detectable by Built-In-Test (BIT) and to what level they will be isolated. If 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.

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

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

f. 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 interpretations 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.

g. 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 - A serial number 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 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 most probable causes for each indenture level analyzed shall be identified and described.

H - A concise statement of the mission phase and operational mode in which the failure occurs.

I - Local 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 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 effect a failure has on the operation, function, or status of the uppermost system or end item and the surrounding environment.

L - A description of the methods by which occurrence of the failure mode is detected by the operator and by the maintainer at the unit level and to what indenture level they will be isolated. 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.

M - Describe the most direct procedure that allows an operator to isolate the malfunction or failure.

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

-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 system definition.

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-82018

Title: RELIABILITY AND MAINTAINABILITY PREDICTIONS REPORT

Number: DI-SESS-81497B Approval Date: 20191008

AMSC Number: N10110 Limitation: No

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-061

Use/relationship: The Reliability and Maintainability (R&M) Predictions Report documents contractor quantitative predictions of reliability, maintainability, and Built-In-Test (BIT). The report is intended as support for feasibility evaluations, comparison of alternative configurations, identification of potential problems, logistics support planning, life cycle cost studies, determination of data deficiencies, tradeoff decisions, allocation (apportionment) of performance requirements, and criteria for growth testing and demonstration. The R&M predictions report will assist in eliminating or managing high-risk elements, improving readiness, reducing life cycle cost, and assessing whether the design is capable of meeting specification requirements.

This DID supersedes DI-RELI-81497A.

2. Format. The Reliability and Maintainability (R&M) Predictions Report shall be in contractor’s

3. Content. The report shall include:

3.1 System configuration identification.

3.2 Assumptions used in the prediction process.

3.3 Documentation or cross-reference to the data used in performing R&M predictions, including the following:

3.3.1 Hardware parts description, including manufacturer part number and manufacturer

CAGE if applicable

3.3.2 Software Configuration Items description

Source: http://assist.dla.mil -- Downloaded: 2020-10-21T20:18Z Check the source to verify that this is the current version before use.

3.3.3 Failure rate data…