A07_W91CRB18R0002_Attachment_J-4_CDRLs_E001-E005.pdf

0001 - 0008, 0023 EEE Sys Eng / Quality Assurance

STORM II

E001 Test Procedures

DI-SESS-82045/DI-NDTI-80603A SOW 3.2.2, 3.2.5, Cont'd below Product Manager SPTD

See Remarks Below

See Remarks

See Blk 16

See Blk 16

SFAE-SDR-SSL-SPTD 1 1 1

1 1 1

SOW Contract Reference Continued: 3.3.6.1, 3.3.6.1.2, 3.3.6.1.3, 3.4.5, 3.4.7, 3.7, 3.13.4, 3.13.7.2, 4.14

Block 4. Firmware Development Plan DI-SESS-82045, 26 May 16. Quality Assurance testing DI-NDTI-80603 dated 14 Nov 06.

The test procedure identifies the step-by-step testing operations to be preformed on items under going developmental, qualification, or acceptance testing (includes PQT, PVT, and LAT)). It identifies items to be tested, the test equipment and support required, the test conditions to be imposed, the parameters to be measured, and the pass/fail criteria against which the test results will be measured. Submission of all system procedures shall occur no later than 30 days after the Design Review.

Government review/comments will be provided within 45 days. Final Test Procedures are due 21 days after receipt of Government comments. Final approval of the Test Procedures shall occur prior to commencement of testing.

Redlined test procedures are due no later than 30 days after successful completion of PQT.

Government review and comments will be provided within 30 days. Final test procedures are due 10 days after receipt of Government comments.

Any modifications to the agreed-upon procedures shall require concurrence in writing by the Government prior to being implemented.

Format -Contractor format is acceptable. Include DISTRIBUTION STATEMENT F:

Further dissemination only as directed by Product Manager Soldier Precision Targeting Devices, SFAE-SDR-SSL-SPTD, 10160 Beach Road, Bldg 325T, Fort Belvoir, VA 22060-5800. Date of determination is date product is generated.

Content – Must include the following, but is not limited to only the content below

• Purpose of test

• System, subsystem, or equipment to be tested. The following identification shall be provided.

see page 2

1 2 Adobe Professional 8.0

0001 - 0008, 0023 EEE Sys Eng / Quality Assurance

(DI E001 (Test Procedures) continued) o Nomenclature o Model or part number o Type of test item(prototype, production item, laboratory model, etc) o Applicable specification

• Test requirements. Included the following, each related to the prescribing contract requirement paragraph(specification, standard, plan, or work statement) o Required tests, and parameters to be measured o Performance requirements, acceptance of compliance limits, and Environmental criteria

• Referenced documents. A list by title, number, date, and source of those documents cited in the test procedure

• Required test equipment. Includes the following for each piece of test equipment required to perform the procedure:

o Nomenclature o Use of test equipment o Model number(if applicable) o Manufacturer(if mandatory) o Accuracy and calibration requirements o Range or spectrum of measurements required

• Table of tests. This table lists each test performed under the procedure in the sequence it is to be performed., identified to the procedure paragraph and the related specification/contract requirement.

• Step-by-step procedure. The following shall be included for each step of the test procedure:

o Test set-up diagrams, including test equipment connections o Input and output instrumentation points o Test item operating limits and test conditions to be imposed o Performance parameters to be measured o Step-by-step operations to obtain the required data o Caution and safety warnings as appropriate

• Data sheets. Data sheets shall be included with the procedure, or be separately attached at the end of all procedures. They shall provide for:

o Identification of item tested, including model and serial numbers o Recording of test measurements o Identification of required or objective performance values, with Tolerances o Identification of applicable procedure paragraphs o Date of test o Signature of technician or inspector performing the tests

• Support requirements. Any special support requirement would be included in this section, such as:

o Use of special facilities or test ranges o Personnel requirements (numbers, types, qualifications) o Unusual electrical, hydraulic, pneumatic, etc, requirements o Support equipment requirements

2 2

0001 - 0008, 0023 EEE Quality Assurance

E002 Test Plans

DI-SESS-82045/DI-NDTI-80603 SOW 3.2.4.2, 3.2.4.4, 3.4, 3.4.8 Product Manager SPTD

See Remarks Below

See Remarks

See Remarks

See Remarks

SFAE-SDR-SSL-SPTD 1 1 1

1 1 1

Firmware Development Plan DI-SESS-82045, 26 May 16. Quality Assurance testing DI-NDTI-80603 dated 14 Nov 06.

The Test Plan outlines the plans and performance objectives at every level of testing on systems or equipment. It provides the procuring activity with the test concept, objectives and requirements to be satisfied, test methods, elements, responsible activities associated with the testing, measures required and recording procedures to be used.

Format -Contractor format is acceptable. Include DISTRIBUTION STATEMENT F:

Further dissemination only as directed by Product Manager Soldier Precision Targeting Devices, SFAE-SDR-SSL-SPTD, 10160 Beach Road, Bldg 325T, Fort Belvoir, VA 22060-5800. Date of determination is date product is generated.

Content – Must include the following, but is not limited to only the content below

• Title page. The title page shall include the following:

o Title of the test to be conducted o Identification of system being tested o Contractor’s name o Contractor’s number o Security classification o Distribution statement

• Introduction. Consists of an overview of the objectives of the test plan, including flow diagrams, milestones, personnel participation, locations, schedules, and security measures to be observed. The plan shall include the following:

o Flow diagrams. The flow diagrams will reflect a functional description of the test program using a block diagram portrayal of the functions that must be met to satisfy the total test program. Functions shall be numbered 1.0, 2.0, 3.0, etc.

o Milestones. Identifies the start and expected completion dates of each test to be performed.

o Participation. Identifies the government and contractor participation roles and responsibilties.

o Location. Identifies the facilities where the testing will be performed.

o Schedule. States when testing will be performed, whether testing is on schedule, and if not, what procedures will be taken to meet the schedule.

o Security. Identify and state briefly any security measures of guidelines to be observed.

see page 2

(DI E002 (Test Plans) continued) o Master test list. Lists all tests to be accomplished in the order they are to be performed. A separate listing for each location shall be provided. Each listing shall include the following:

Test description. Name and brief description of test to be performed.

Applicable specification (s). The specifications shall be identified as follows:

(A.) Title and identification number (B). Paragraph number associated with the tests (C.) Title of test (D.) Functional category of test o Parameters. The number of cycles the test will be performed and selected parameters to be observed.

o Special tests. Provides a list of special or unusual tests and examination necessary to verify satisfactory equipment performance to specifications.

o Test classification category. State the functional area of each test performed.

o Test objectives. Describes the objectives of each test performed, including the criteria, baseline, duration, and number of times each test should be performed.

Success/failure criteria Baseline Duration Quantity of test o Test equipment. List all equipment to be used in the test and identify as follows:

o Description o Nomenclature o Serial number o Support equipment. List all support equipment that will be used to perform the tests and identify as follows:

Description Nomenclature Serial number Calibration constants Calibration procedures Operating instructions o Special test equipment. List all special test equipment required to be designed or fabricated for use on the program as follows:

Description Nomenclature

Data required o Approach. Describe the steps used to perform each test.

o Instrumentation. Indicates the type and recording devices that will be used and the number and types of parameters to be recorded.

o Data reduction and analysis. Describes data to be recorded and the data reduction and analysis techniques that will be used to interpret the data.

o Government test facilities. Identifies applicable facility and includes a reference to the appropriate facility requirements documents.

o Validation procedure. An overview of the procedures that the contractor will use to validate the test results.

The contractor shall prepare and submit a test plan for each delta-PQT, PVT, and LAT. All test plans shall be prepared in accordance with DI-SESS-881704. The contractor shall prepare and electronically submit the Test Plans no later than fifteen (15) days prior to TRR.

Government review/comments will be provided with in 10 days after receipt. The contractor shall submit final Test Plans five (5) business days after receipt of Government comments.

The document shall be compatible with Windows and Microsoft Office 2013 products (i.e., Word, Excel, PowerPoint, etc.) and MS Project 2013.

E003 Test Report

See Blk 16 SOW 3.2.4.1 - 4, 3.2.5, 3.3.6.1.3 Product Manager SPTD

See Remarks Below

See Remarks

See Blk 16

See Blk 16

SFAE-SDR-SSL-SPTD 1 1 1

1 1 1

SOW 3.8

Block 4. DI-SESS-82045, DI-NDTI-80603DI-ATTS-80283 Rev. B.

Upon completion of Contractor Qualification Test (CQT) and any delta CDT the contractor shall prepare and submit a Test Report. The report shall include the test logs, test results, to include A-test data, raw data, compiled and calculated data (to include mathematical equations/models used), address all failures encountered, and all and Sub-contractor Corrective Action Reports (SCARs).

All conclusions shall be clearly identified as such and shall be appropriately segregated from the objective results. The report shall be submitted within 21 days after test completion. Government review/comments will be provided within 30 days.

The Contractor shall incorporate corrections and resubmit a final report within 10 days of receipt of Government comments.

The contractor shall report test results IAW SOW. The report shall not be submitted until all FIARs are approved.

The document shall be compatible with Windows and Microsoft Office 2013 products (i.e., Word, Excel, PowerPoint, etc.) and MS Project 2013. DISTRIBUTION STATEMENT E:

Distribution authorized to DoD Components only per the STORM II Security Classification Guide. Date of determination is date product is generated. Further dissemination only as directed by Product Manager Soldier Precision Targeting Devices, SFAE-SDR-SSL-SPTD , 10170 Beach Road, Bldg. 325T, Fort Belvoir, VA 22060-5800. Date of determination is date product is generated.

The following content will be in the Test Report

• Contractor facility point of contact information.

• Subcontractor’s testing facility point of contact information.

• Test plan.

• Traceability matrix of tests performed to specifications.

• Test equipment used.

• Test software and algorithms used when conducting the test.

• Results of each test performed.

• Appendix of all FIARs, their status, root cause and corrective action taken.

See page 2

(DI E003 (Test Procedures) continued)

• Narrative of any material or supplies changed resulting from test results.

• Narrative of future planned material or supply changes resulting from testing.

Duration.

iv. Quantity of test.

o Test equipment. List all equipment to be used in the test and identify as follows:

o Description.

o Nomenclature.

o Serial number.

o Support equipment. List all support equipment that will be used to perform the tests and identify as follows:

Description.

Nomenclature.

Serial number.

Calibration constants.

Calibration procedures.

Operating instructions.

o Special test equipment. List all special test equipment required to be designed or fabricated for use on the program as follows:

Description.

Nomenclature.

Data required.

o Approach. Describe the steps used to perform each test.

o Instrumentation. Indicates the type and recording devices that will be used and the number and types of parameters to be recorded.

o Data reduction and analysis. Describes data to be recorded and the data reduction and analysis techniques that will be used to interpret the data.

o Government test facilities. Identifies applicable facility and includes a reference to the appropriate facility requirements documents.

o Validation procedure. An overview of the procedures that the contractor will use to validate the test results.

The FIAR shall include, but is not limited to:

• Subsystem or component failed, to include part number, serial number, and manufacturer

• Design code or process revision for the failed subsystem

• Description of test failure

• Failure date/time

• Test (or sub-test) failed to include reference to particular section of the test procedure under exection at the time of failure

• Operating hours and/or cycles at the time of failure

• Unit(s) affected

• Lot Number(s) affected and Lot size

• Sample size for the test failed

• A summary of the analysis, including o Identification and verification of failure mode. If measurements are made during the failure investigation the FIAR shall include results of all measurements made and expected/required values for each measurement o Failure root cause, to include why the defect was not detected during normal production, and impact to similar product or processes o Action taken to elimate root cause(s) and to prevent recurrence o Proposed corrective action for all materiel affected, including items delivered to the Government; include process controls in place or planned to prevent the problem from recurring o Test results showing validation/verification of corrective action is effective o History of the failure mode in all CI as well as in production testing and ESS. If the failure mode/root cause has been experienced during production acceptance testing and ESS the history shall also include a description of the corrective action implemented by the contractor to address the failure mode/root cause.

o Containment of the failure, including end items in plant and already delivered to the Government as well as material work in process, at receiving, or in transit o Recommended disposition of failed item(s) and lot and Sub-contractor Action Report if applicable.

0015 EEE Quality Assurance

E004 Failed Item Analysis Reports (FIARs)

DI-SESS-80255A SOW 3.3.4.1, 3.4.5, 3.9, 3.11 Product Manager SPTD

See Remarks Below

See Remarks

See Blk 16

See Blk 16

SFAE-SDR-SSL-SPTD 1 1 1

1 1 1

The FIAR documents test failures that occur during system, TMDE and major component-level CDT, PQT, FAT, CI testing, reliability testing, and Government DT/OT.

The FIAR shall include identification and verification of the failure mode, a summary of the failure analysis and identification of the root cause(s), disposition of the failed item(s), action taken to eliminate the root cause(s) and to prevent recurrence, corrective action for all materiel affected including items that may have been delivered to the Government, validation/ verification that the corrective action was effective, history of the failure, containment of the failure, recommended disposition of the lot, and applicable Sub-contractor Corrective Action Report.

The contractor shall submit a FIAR for each failure that occurs during CQT, reliability testing, Government DT. Within 10 business days of failure occurrence, including those occurring during Government DT, the contractor shall prepare and submit for concurrence the final FIAR with a final Sub-contractor Corrective Action Report (SCAR), if necessary.

Government review/comments will be provided within 5 business days.

The Contractor shall incorporate corrections and resubmit a final report within 5 business days of receipt of Government comments or as stated in the Government e-mail or letter.

The Government may extend FIAR deadlines on a case-by-case basis should the need arise.

The contractor shall prepare a separate FIAR for each failure mode experienced by a system. The FIAR shall not be considered closed until the IPPT has concurred with the report. Concurrence by the IPPT is required prior to shipment of any potentially affected production units.

The contractor shall submit to the IPT for concurrence, within time limits a final FIAR. The final FIAR, shall include, if necessary, a Sub-contractor Corrective Action Report (SCAR).

E-mail is the preferred method of FIAR submittal. The contractor shall prepare a separate FIAR for each failure. The contractor may prepare a combined FIAR for multiple failures of the same root cause if agreed to by the IPT.

Contractor format is acceptable; however, the IPT at the Post Award Conference shall concur with the complete template proposed content of the FIAR, and a list of personnel to be notified of failures. All subsequent FIARs shall adhere to the IPT-concurred format. The FIAR shall not be considered closed until the Government has concurred with the report.

Government approval is required prior to shipment of any potentially affected production units.

See page 2

0015 EEE Quality Assurance

(DI E004 (FIARs) continued)

Security marking shall contain DISTRIBUTION STATEMENT E: Distribution authorized to DoD Components only per the STORM II Security Classification Guide. Date of determination is date product is generated. Further dissemination only as directed by Product Manager Soldier Soldier Precision Targeting Devices, SFAE-SDR-SSL-SPTD , 10170 Beach Road, Bldg. 325T, Fort Belvoir, VA 22060-5800. Date of determination is date product is generated.

The FIAR shall include, but is not limited to:

• Subsystem or component failed, to include part number, serial number, and manufacturer.

• Design code or process revision for the failed subsystem.

• Description of test failure.

• Failure date/time.

• Test (or sub-test) failed to include reference to particular section of the test procedure under execution at the time of failure.

• Operating hours and/or cycles at the time of failure.

• Unit(s) affected.

• Lot Number(s) affected and Lot size.

• Sample size for the test failed.

• A summary of the analysis, including o Identification and verification of failure mode. If measurements are made during the failure investigation the FIAR shall include results of all measurements made and expected/required values for each measurement.

o Failure root cause, to include why the defect was not detected during normal production, and impact to similar product or processes.

o Action taken to eliminate root cause(s) and to prevent recurrence.

o Proposed corrective action for all materiel affected, including items delivered to the Government.

Include process controls in place or planned to prevent the problem from recurring.

o Test results showing validation/verification of corrective action is effective.

History of the failure mode/root cause in all CI testing, production acceptance testing, ESS, and qualification testing. If the failure mode/root cause has been experienced during production acceptance testing and ESS the history shall also include a description of the corrective action implemented by the contractor to address the failure mode/root cause.

o Containment of the failure, including end items in plant and already delivered to the Government as well as material work in process, at receiving, or in transit.

o Recommended disposition of failed item(s) and lot o Sub-contractor Corrective Action Report (SCAR), if applicable

0001 - 0008, 0017 -0020, 0023 EEE Quality Assurance

E005 Reliability Program Plan (RPP)

SOW 3.5.2 Product Manager SPTD

See Remarks Below

See Remarks

See Blk 16

See Blk 16

SFAE-SDR-SSL-SPTD 1 1 1

1 1 1

The contractor shall prepare and submit to the IPT, for concurrence, a Reliability Program Plan for the system.

• Modification/Revision only upon written concurrence of IPT Chairpersons.

The contractor shall prepare and submit the RPP as part of the contractor’s proposal.

Following contract award the contractor shall prepare and submit an updated RPP 30 days after contract award.

Government review/comments will be provided within 30 days.

Final submittal of the RPP is due 10 days after receipt and incorporation of Government comments.

Subsequent submissions/revisions shall include updated information to include, but not limited to, tests completed, changes in design, or suppliers and shall be submitted every 90 days or as agreed upon by the IPT.

Contractor format is acceptable. Security marking shall contain DISTRIBUTION STATEMENT E: Distribution authorized to DoD Components only per the STORM II Security Classification Guide. Date of determination is date product is generated. Further dissemination only as directed by Product Manager Soldier Precision Targeting Devices, SFAE-SDR-SSL-SPTD , 10170 Beach Road, Bldg. 325T, Fort Belvoir, VA 22060- 5800.

Date of determination is date product is generated.

The Reliability Program Plan (RPP) shall include, but is not limited to, the following:

• The Reliability Requirements. The report shall include all reliability requirements and the source of the requirements. Any derived requirements shall include all assumptions related to the derivation of the reliability metric.

• System Reliability Model (SRM). This report shall address the methods and tools that will be used for developing and refining the SRM. The report shall document how the SRM will be updated as the design evolves and new information about failure modes is identified. The SRM is a graphical depiction of the system with an underlying analysis such as Reliability Block Diagram, Fault Tree, or Event Tree.

See page 2

0001 - 0008, 0017 -0020, 0023 EEE Quality Assurance

(DI E005 (RPP) continued)

• Critical Elements. The report shall identify how critical elements will be identified. Critical elements are defined as those elements (subsystems/assemblies/subassemblies) whose failure impacts mission completion, essential functions, or safety; or elements whose failure rates contribute significantly to the overall system.

• Reliability Management and Organization. The report shall include an organizational chart that provides visibility into the management and organizational structure of those responsible and accountable for the conduct of reliability activities. The organization structure shall clearly define how those responsible for reliability activities interact with the design, systems engineering, test and evaluation, cost, and supportability teams. The organization structure shall also depict the interface between the Government and all subcontractors/suppliers (when applicable). The report shall define all responsibilities for the reliability team.

• Design for Reliability (DfR) Activities. The report shall document all planned DfR activities and the resources required to conduct the associated activities. DfR encompasses the management and reliability engineering activities executed during the design stage that identify and characterize failure modes at the lowest indenture levels possible before system-level prototyping.