Section_J_Attachment__1_SOW_2JUN15.rtf

M67854-15-R-6007 Section J – Attachment 1

STATEMENT OF WORK

FOR

Projectile, 120 Millimeter:

Precision Extended Range Munition (PERM), XM1109

Date: 25 March, 2015

Milestone C

ACAT IV(M)

Prepared By

Product Manager Fire Support Systems Marine Corps Systems Command M67854-15-R-6007 Section J – Attachment 1

STATEMENT OF WORK

STATEMENT OF WORK (SOW)

for Projectile, 120 Millimeter: Precision Extended Range Munition (PERM), XM1109

1 SCOPE. This Statement of Work (SOW) sets forth the work efforts required by the Contractor to design, develop, integrate, conduct component and system testing, and deliver production of the Projectile, 120MM: Precision Extended Range Munition, XM1109 (hereinafter called PERM) and the associated program management, system engineering, manufacturing, configuration management, quality assurance, logistic support, and development of technical publications and manuals associated with the production and delivery of the PERM. The Product Manager, Fire Support Systems (PdM FSS) will conduct the PERM Qualification utilizing the rounds supplied by the Contractors. The Contractor shall provide all material and necessary support documentation needed to complete the tasks identified in this SOW.

2 APPLICABLE DOCUMENTS. The following documents specified form a part of this SOW to the extent specified herein. The most recent revision of the referenced document at the time of contract shall be used unless otherwise specified. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence. All second tier and below references cited in mandatory compliance documents shall be considered as guidance only. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

2.1 Standards and Specifications

GEIA-STD-0007-B Logistics Product Data

MIL-STD-882E Standard Practice for System Safety

MIL-STD-1168C Ammunition Lot Numbering and Ammunition Data Card

N/A Lifecycle Environmental Profile (LCEP) for the Future Expeditionary Fire Support System (EFSS), April 2013

PRF-PMM141.1/PERM Performance Specification for the Precision Extended Range Munition (PERM)

2.2 Drawings.

N/A.

2.3 Handbooks - Guidance Only.

MIL-HDBK-61A Configuration Management Guidance

MIL-HDBK-338B Electronic Reliability Design

MIL-HDBK-502A Acquisition Logistics

N/A Joint Software Systems Safety Engineering Handbook

2.4 Other Government Documents. Unless otherwise stated, the following documents may be obtained from http://www.documentservices.dla.mil/ or DLA Document Services, 5450 Carlisle Pike Bldg. 09, PO Box 2020, Mechanicsburg, PA 17055-0788.

AOP-52 Allied Ordnance Publication (AOP), Guidance on Software Safety Design and Assessment of Munition-Related Computing Systems – ED 1

ASME Y14.100 Engineering Drawing Practices

ASME Y14.34 Associated Lists

CNSS 1253 Security Categorization and Control Selection for National Security Systems

DoDI 8500.01 Cybersecurity

DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT)

EIA-649 National Consensus Standard for Configuration Management

EPA 17 List of Targeted Chemicals

ETAP 3.5.2 NAVSEA Hazardous Material (HM) Avoidance Engineering Technical Authority Process

GPU-09-105 Security Approval Review Process Requirements For Selective Availability Anti Spoofing Module (SAASM) Host Application Equipment (HAE)

MARCORSYSCOMO 8020.1 Ammunition Demilitarization and Disposition Plan

NAVSEAINST 9310.1B Naval Lithium Battery Safety Program

NIST 800-53 Security and Privacy Controls for Federal Information Systems and Organizations

NIST 800-53A Guide for Assessing the Security Controls in Federal Information Systems and Organizations: Building Effective Security Assessment Plans

SAE JA1011 Evaluation Criteria for Reliability-Centered Maintenance (RCM) Processes

SAE JA1012 A Guide to the Reliability-Centered Maintenance (RCM) Standard

TM S9310-AQ-SAF-010 Technical Manual for Batteries, Navy Lithium Safety Program Responsibilities and Procedures, dated 15 July 2010

(Copies of TM S9310-AQ-SAF-010, dated 15 July 2010 are available from http://www.public.navy.mil/comnavsafecen/Documents/afloat/Surface/CS/Lithium%20Batteries%20Info/LithBatt_NAVSEA_TMS9310.pdf or Naval Weapons Support Center, Code 3057, Building 36, Crane, IN 47522-5060)

3 REQUIREMENTS. The Contractor shall perform all tasks required and delineated in this SOW to design, develop, integrate, conduct component and system test, deliver and prepare associated documentation, and deliver production of the PERM in the quantity specified in the contract. Once a Product Baseline has been established, the Contractor shall provide all materials, equipment, tooling, personnel, and facilities necessary to manufacture, test and deliver the types and quantities of deliverables specified by the contract.

The major required activities are listed below:

The Contractor shall design, develop, implement, and test any modifications proposed in their proposal submission, prior to delivering rounds that will be used for the Government qualification testing.

The Contractor shall deliver 162 PERM rounds in accordance with (CLIN 1000), that meet the specification and criteria of the PERM Performance specification, WS-35766 Attachment 2 – Section J, and that will successfully pass the test events outlined in Section 4 of the PERM performance specification. Failure to deliver 162 rounds that successfully pass PERM qualification tests will require the Contractor to deliver new PERM test articles that will be expended to support Government qualification testing.

The Contractor shall conduct multiple reviews as specified herein and provide supporting documentation to substantiate the PERM system ability to meet the Government contract requirements.

The Contractor shall fabricate systems/All-Up Rounds (AURs)/components which will be used for the Government led PERM Production Verification Test (PVT), Tabular Firing Tables (TFT), and Lot Acceptance Test (LAT). The Contractor shall also deliver final inspection records with the delivery of all rounds associated with each Lot delivered under the PERM production delivery CLINs.

The Contractor shall deliver the PERM quantities specified in this contract and as ordered under individual orders awarded under this contract.

3.1 Program and Data Management.

3.1.1 Program Management. The contractor shall prepare and submit a progress, status and management report. The Contractor shall establish and maintain program management practices capable of monitoring, cost, schedule and performance during the execution of the contract and throughout the period of performance. Program management practices shall provide visibility into the Contractors’ organization and techniques used in managing the program, specifically subcontractor and data management.

CDRL A001: DI-MGMT-80227, Contractor’s Progress, Status and Management Report

3.1.1.1 Integrated Program Management Report. The Contractor shall provide Integrated Program Management Report (IPMR) to the Government. The Contractor shall prepare an IPMR per CDRL A002 that includes at a minimum, cost reporting showing actuals and a top level schedule showing delivery dates of end products.

3.1.1.3 Subcontractor Management. The Contractor shall institute appropriate management actions relative to subcontractor performance. Requirements that are contractually specified shall apply to subcontractor performance; however, the Contractor shall be accountable for subcontractor compliance and is responsible for ensuring all deliverable products comply with the contract requirements.

3.1.2 Data Management. The Contractor shall establish a single, centralized system for management of all data required under this contract. The Government reserves the right to review all data associated with and developed for the PERM. Documentation shall be readily available to Government representative(s).

3.1.3 Security Requirements. All PERM systems will require a Selective Availability Anti-Spoofing Module (SAASM) Global Positioning System (GPS). The Contractor’s facilities and personnel shall have the appropriate clearances and approval to store and use GPS data and equipment required to operate the system. The Contractor shall provide evidence that their host application equipment has been approved per GPU-09-105. The Contractor and/or their subcontractor shall possess a valid COMSEC account number and adhere to all requirements as identified in the Security Classification Guide associated with this contract Attachment 4.

3.2 Government Furnished Property.

3.2.1 Government Furnished Equipment. The Government will notify the Contractor of the availability of Government Furnished Equipment (GFE). Items will be provided to the Contractor within 90 days of receipt of Contractor's written request to the Marine Corps Systems Command Fire Support Systems program office. The Contractor shall provide for accountability, security and storage for the GFP provided. The Contractor shall inspect and inventory all GFP received and identify and report any discrepancies/deficiencies to include associated costs (materials, labor and test (if applicable)) for repair of the GFP to like new conditions. Upon approval by the Government, the Contractor shall conduct the necessary repair actions.

CDRL A003: DI-MGMT-80389B, Receipt of Government Materiel Report

3.2.2 Government Furnished Information. The Government will furnish the Government Furnished Information (GFI) identified in the contract upon written request from the Contractor to the Marine Corps Systems Command Fire Support Systems program office. The Contractor shall notify the Government of any deficiencies in the GFI received.

CDRL A004: DI-MGMT-80596, Government Furnished Information Deficiency Report

3.3 Meetings, Formal Reviews, Conferences, and Audits.

3.3.1 Contractor Responsibilities. The Contractor shall plan, host, attend, coordinate, support and conduct meetings, formal reviews, conferences, and audits (hereinafter called "reviews"). The reviews shall be conducted at Government and Contractor facilities. All such reviews shall be included in the program schedule and may be held concurrently with the Government’s approval. The Contractor shall prepare agendas and conference presentation materials, and provide minutes and reports following each review. The Government reserves the right to cancel any review or to require any review. Action item documentation, assignment of responsibility for completion and due dates shall be determined prior to adjournment of all reviews. A summary of all action items, responsible parties, and estimated completion dates shall be included with the minutes.

3.3.3 In-Process Review. In-Process Reviews (IPR) will be held quarterly at a date and location mutually agreed upon. The Government reserves the right to cancel any review or to require any review to be scheduled during the period of performance. The Contractor’s progress, management, technical support services (if any), integrated logistics support, administrative, assurance of compliance with contract requirements, program status, funding, problem identification and resolutions shall be agenda items. Actual versus expected performance of each area shall be addressed. The Contractor shall prepare presentation materials providing an overview of all agenda items. The Contractor shall ensure that appropriate personnel are available for reviews to address and resolve agenda items.

3.3.4 Test Readiness Reviews. The Contractor shall host the Test Readiness Reviews (TRRs) prior to the start of testing that will evaluate the modification made to the Contractors rounds prior to delivery of the Government PERM Type Qualification Test (TQT) rounds and Production Verification Test (PVT) rounds. The Contractor shall also participate in the TRRs supporting the PERM Government qualification test and evaluation approximately 60 days prior to start.

3.3.5 Physical Configuration Audit. The Physical Configuration Audit (PCA) shall be performed to verify the PERM and its Configuration Items (CIs) and Software Configuration Items (SCIs) are accurate, complete, compatible, and have achieved the performance and functional characteristics defined in the functional configuration baseline. The Government and the Contractor shall conduct the PCA jointly, at a time and place mutually agreed to, with the Government chairing the audit. The PCA shall verify the drawings reflect the "as-built" configuration of all newly developed or modified portions of the system; accurate form, fit or function information is provided on control drawings for non-developmental/ commercial off-the-shelf items; and confirm the drawings accurately represent the "as-built" production configuration. Whenever possible, the PCA shall be conducted incrementally, concurrent with hardware fabrication and assembly of the first production system. The Contractor shall develop a configuration audit plan and provide the system to be audited, facilities, personnel, documentation (including drawings) and other support as may be required. The Contractor shall participate and assist the Government in the development of the PCA, using the guidelines contained in Section 8 of MIL-HDBK-61A, Configuration Management Guidance. The Contractor shall document the results of the PCA after each audit and shall correct all audit discrepancies documented in the configuration audit summary reports. In the event the Government finds evidence the drawings and/or documents do not adequately represent the equipment, production shall cease until all discrepancies are corrected and the Government approves the configuration audit summary report. The product baseline will be established upon completion of the PCA and resolution of audit discrepancies.

Form, fit or function changes to the Product Baseline during the course of this contract requires written Government approval prior to changes. The PERM shall be re-tested; or re-tested and re-qualified by the Contractor in accordance with the requirements of Performance Specification WS-35766, Attachment 2 – Section J, to the extent required by the Government.

3.3.6 Production Readiness Review. The Contractor shall host a Production Readiness Review (PRR) on a mutually agreed upon date to be determined at the PAC. The PRR shall be held no later than 60 days after completion of Type Qualification and Tabular Firing Table tests. The PRR shall address each hardware and software configuration item and related maintenance and logistics support. The Contractor shall show and/or demonstrate that evaluations of materials, lead times, tooling, fabrication techniques, assembly methods, test equipment, skills, processes and inspection techniques have been accomplished for each equipment, hardware and software configuration item and related support equipment; show and/or demonstrate that producibility objectives have been achieved; and shall identify all single source, sole source and diminishing source(s). This review will evaluate the progress, technical adequacy and risks of the system and will assess the technical risk associated with the selected assembly processes. During this review the Contractor shall present their plan to meet the production schedule.

3.4 Systems Engineering. The Contractor shall establish and maintain an effective systems engineering program throughout the testing and production processes. The systems engineering program shall be documented in a System Engineering Management Plan (SEMP) to be provided to the Government.

CDRL A00A: DI-SESS-81785, System Engineering Management Plan (SEMP)

3.4.1 Configuration Management. The Contractor shall perform configuration management on PERM to ensure form, fit, function and interface requirements are maintained throughout the contract period. The principles contained in EIA-649, National Consensus Standard for Configuration Management (CM), and MIL-HDBK-61A, Configuration Management Guidance, should be used for guidance as well as related MARCORSYSCOM acquisition and engineering policy. The Contractor's CM process shall consist of CM planning, configuration identification, configuration control, configuration status accounting, and configuration verification and audits and data management including tools. Processes and tools for interfacing with other acquisition requirements such as design review, assurance, and other program related disciplines shall be addressed. The Contractor shall notify the Government of any changes at the Contractor's facility, which affect the execution of the Contractor's CM Plan. The government shall review and approve the Contractor's CM plan.

CDRL A00B: DI-CMAN-80858B, Contractor's Configuration Management Plan (CMP)

3.4.1.1 Control/Accountability. The Contractor shall maintain control and accountability of the product baseline throughout the life of this contract. The Contractor shall notify the Government at the onset of their planning, which shall be at a minimum of 40 working days in advance, of all changes to established baselines that affect form, fit, function, cost or product delivery schedule throughout performance of this contract. The notification shall include a change impact analysis that assesses alternate solutions to determine what action is in the best interest of the Government. Additionally, notification information shall include enclosures and figures that identify and define the effect on Technical Manuals (TMs) including draft TM page changes, packaging data, testing supportability, interoperability/interchangeability, lifecycle costs, maintainability, reliability, environmental (to include identification of all ozone depleting substances) safety and health (ESH) and retrofit information. Sufficient supporting data to evaluate the proposed or requested change, such as engineering drawings, sketches, specifications, or manufacturing data sheets, shall also be submitted as supplemental information. All changes to the baseline shall be approved by the Government using the Engineering Change Proposal (ECP) accompanied, where appropriate, with a Notice of Revision (NOR) or the Request for Variance (RFV) Process.

3.4.1.1.1 Engineering Change Proposals. ECPs shall be submitted by the Contractor, and shall be limited to those, which are necessary or offer significant benefit to the Government. MIL-HDBK-61A provides guidance concerning the classification of ECPs. Class I ECPs shall be submitted when changes are required to: (a) Correct deficiencies; (b) Add or modify interface or interoperability requirements; (c) Make a significant and measurable effectiveness change in the operational capabilities or logistics supportability of the system; (d) Effect substantial life cycle costs/savings; and (e) Prevent slippage in an approved production schedule. Class II ECPs shall be submitted by the Contractor to the Administrative Contracting Officer (ACO) for approval for those engineering changes, which impacts none of the factors listed above. As a minimum, Class I ECPs shall contain the following information: (a) Date prepared; (b) Originator; (c) ECP Classification; (d) ECP Number; (e) Reason/need for change; (f) System designation (nomenclature, model, P/N); (g) Name of part (or lowest assembly) affected to include part numbers; (h) Baselines affected (to include drawings, specifications, CAGE, revision level, etc.); (i) Title of change; (j) Description of change; (k) Effect on interfaces (Interchangeability and Interoperability); (l) Total costs/savings w/ breakout; (m) Retrofit information; (n) Ozone Depleting Substances; (o) Impact on any engineering disciplines (such as quality, environmental, safety, health, reliability, maintainability, etc.); (p) Justification for change; (q) Priority of change; (r) Impacts to any logistics support elements (such as software, manuals, spares, tools, etc.) being utilized by Government personnel in support of the product; and (s) Alternatives evaluated or considered. The Contractor shall generate and submit Notices of Revision (NORs) concurrently with ECPs when technical documentation controlled by another Contractor or Government agency requires changes following approval of an ECP.

3.4.1.1.2 Technology Insertion. At any time during the course of this contract, the Government may require, at its option, the insertion of state-of-the-art, advanced or alternate technology into the items called for under the contract. Technology insertion may be initiated through Engineering Change Proposals and incorporated into the contract via contract modification. If any Engineering Change Proposal would result in the contract price being changed, it may be negotiated as any in scope change under change order modification, and any equitable adjustment shall be incorporated into the contract in the form of a modification.

3.4.1.1.3 Requests for Variance. The Contractor shall process RFVs from current approved configuration documentation. Authorized variances are a temporary departure from the requirements and do not constitute a change in an approved baseline. Submission of recurring variances is discouraged and shall be minimized. Where it is determined that a change should be permanent, the Contractor shall process an ECP. As a minimum, the RFVs shall contain the following information: (a) Date prepared; (b) Originator; (c) Request for Deviation (RFD) Classification (critical, major or minor); (d) Designation for variance (model/type, CAGE code, system designation, and deviation number); (e) Class of deviation; (f) Part Number affected; (g) Cost/Price data; (h) Effectivity; (i) Description of deviation; (j) Need for deviation; (k) Effect on delivery schedule; (l) Recommended corrective action; and (m) Alternatives evaluated.

3.4.1.1.4 Notification of Changes to Commercial Equipment/Software. The Contractor shall submit notification to the Government when changes occur to commercial equipment or software, which is being procured or fabricated by the Contractor off-the-shelf, and the Government does not control the developer’s design. The Contractor shall submit a change notice to the Government implementing any Class II ECPs and the Government will concur in the classification designation of the ECP.

CDRL A00F: DI-MISC-80508B, Technical Report - Study/Services (Change Notification), Subtitle: Notification of Changes to Commercial Equipment/Software

3.4.2 Engineering Design and Drawings.

3.4.2.1 System/Subsystem Design. The Contractor shall provide a System/Subsystem Design Description (SSDD) and a System/Subsystem Specification(s) (SSS(S)). The SSDD shall describe the system- or subsystem-wide design and the architectural design of a system or design of a system or subsystem. The SSS(s) shall specify the requirements for a system or subsystem and the verification methods used to ensure that each requirement has been met. The SSS(s) shall be used as the basis for the design of a system or subsystem.

3.4.2.2 Commercial Drawings/Models. The Contractor shall provide, in English, commercial drawings/models to the Government for commercial item(s) approved for use in the design and not covered by Government or nationally recognized industry association specifications and standards. The Contractor shall provide evidence that the part complies with the requirements of the applicable part documentation. Existing test data (such as supplier originated objective evidence of compliance or Government/Industry Data Exchange Program (GIDEP) reports) shall be used to the maximum extent practicable.

CDRL A00N: DI-SESS-81003E, Commercial Drawings/Models and Associated Lists

3.4.2.4 Ammunition Data Cards. The Contractor shall prepare, and provide with deliverable hardware, Ammunition Data Cards in accordance with MIL-STD-1168C. Ammunition Lot Numbering in accordance with MIL-STD-1168C is also required. In addition, copies of end item and lower level (including any energetic material) component ammunition data cards or Acceptance Test Certificates will be provided to Headquarters, Joint Munitions Command, 1 Rock Island Arsenal, Attn: FSJM-QAP, Rock Island, IL 61299 and Marine Corps Systems Command, Program Manager for Ammunition (PMM 116). The Contractor shall enter the ammunition data into the World-Wide Ammunition Repository Program (WARP) database located on the Munitions History Program (MHP) data logistics portal, Redstone Army Arsenal.

CDRL A00Q: DI-MISC-80043B, Ammunition Data Cards (ADC)

3.4.2.5 Failure Modes, Effects and Criticality Analysis. The Contractor shall prepare a Failure Modes, Effects and Criticality Analysis (FMECA) to identify all system failure modes. Failure modes resolved by inherent Built-in Test (BIT) capabilities shall be identified in the analysis. For all failure modes not resolved by BIT, this analysis shall identify the Single Point of Failure (SPOF) or fault group of maintenance-worthy items applicable to the mode based upon the system architecture. The failure effects to the system shall be identified in addition to the criticality level of each failure (inoperable or degraded). In the event of a degraded effect, the Contractor shall identify the operational/inoperable functional capabilities. Failure indications/symptoms to the operator/maintainer shall be detailed within the report. FMECA findings shall be applied during the conduct of Maintenance Task Analysis. The Contractor shall prepare a FMECA report in accordance with SAE JA1011 and SAE JA1012 and using best commercial practices.

CDRL A00R: DI-MISC-80508B, Technical Report - Study/Services (FMECA)

3.4.2.6 Reliability Predictions. The Contractor shall provide reliability predictions based on their design baseline. Reliability data shall be predicted and/or adjusted based on the Expeditionary Fire Support System (EFSS) Lifecycle Environmental Profile (LCEP) and shall account for end-user environmental conditions. System environmental parameters presented in the performance specification shall apply. De-rating criteria applied to calculations shall be detailed within the reliability report. Where relevant actual/historical reliability data exists, this data shall take precedence over predicted data and be adjusted appropriately to account for differences between the environments for the historical data and the specified PERM environment. The reliability predictions shall be decomposed down to the lowest appropriate design indenture level and updated as needed to reflect design or mission profile changes. In the event that the system architecture provides redundant functional/physical capabilities, the reliability report shall explain how this redundancy was taken into account in the reliability predictions and on mission reliability. The Contractor shall provide reliability prediction reporting for the AUR.

CDRL A00S: DI-RELI-81497, Reliability Prediction and Documentation of Supporting Data

3.4.3 Demilitarization and Disposition Plan. The Contractor shall provide information for the government in accordance with the MARCORSYSCOMO 8020.1, Ammunition Demilitarization and Disposition Plan to update the PERM Demilitarization and Disposition Plan. This information shall be presented in the form of a draft plan for government use and shall be updated as required to accommodate any approved changes to the rounds. The Ammunition and Demilitarization plan shall include Contractor support for the Government development of explosive ordnance disposal procedures and documentation.

CDRL A00T: DI-SAFT-81640, Ammunition Demilitarization and Disposition Plan

3.5 Quality Management System. The Contractor's quality management system shall ensure product conformation to contractual requirements. The Contractor shall have implemented, documented, and have previously demonstrated the ability to maintain the quality management system to be used on the contract. The Contractor shall make available all quality management documentation for the Government to review upon request. The Contractor's plan for the quality management system shall address the following elements:

In addition the following plans and lists shall be submitted and kept current:

a) Quality Assurance Plan.

b) Critical Characteristics Control Plan

c) Automated Acceptance Inspection Equipment Design, Design Testing and Approval, of shall meet MIL-A-70625A and 70625A Notice 2. The Acceptance Inspection Equipment List shall be kept current with appropriate certifications.

d) Statistical Process Control Plan

3.5.1 Management of Critical Characteristics Control Plan. The following Critical Characteristics Control requirements shall apply:

a. The Contractor’s processes shall be designed with the objective of preventing the creation and occurrence of nonconforming critical characteristics (see section “d” & “e” below). The Contractor shall establish, document and maintain a product specific Critical Characteristics Control (CCC) plan that shall be submitted to and approved by the Government. The CCC plan shall include or reference all procedures, work and handling instructions and process controls relating to all critical characteristics. Mistake Proofing techniques of the material handling and inspection systems shall be a part of the CCC Plan. Guidance for developing this plan and submitting Critical Plans of Action (CPOA) (see section “g” below) can be found at http://www.pica.army.mil/PicatinnyPublic/organizations/ardec/orgchart/quality.html.

b. The Contractor shall assure its critical processes are robust in design, capable and under control, with the objective of not generating critical non-conformances. The Contractor shall calculate, document, clearly identify, and have a schedule that routinely assess the reliability and effectiveness of its critical processes to prevent generating critical non-conformances as identified in the CCC Plan.

c. An inspection and verification system shall be employed that shall verify the robustness of all critical processes. The Contractor shall calculate, document, clearly identify, and have a schedule that routinely assess the reliability and effectiveness of its inspection and verification system to detect and prevent critical non-conformance escapes as identified in the CCC Plan. The Government expects that a Contractor shall allow zero critical escapes. To demonstrate its critical escape risk the Contractor shall utilize the non-conformance escape risk goal provided below.

(1) The calculated critical non-conformance escape risk is 1 in a million (.000001) items delivered. Unless otherwise approved by the Government, the non-conformance escape risk is the sum of the individual characteristic escape rates. The probability of escape for a single characteristic shall be calculated by multiplying the non-conformance rate(s) entering the inspection system(s) by the error rate of the inspection system(s). These escape rates are then summed and shall not exceed the tolerable critical non-conformance escape risk.

(2) Within 45 days after award, the Contractor shall either demonstrate compliance to the non-conformance escape risk in paragraph “c” above or submit a phased-in approach on how the nonconformance escape risk shall be achieved over a period of time not to exceed 180 days from the date of first article approval, or from initiation of production when first article is not required. Submission shall require approval by the Government and is subject to a technical review and analysis. Allowance for a phased-in approach will then become a part of the contract. Disapproval of the Contractor’s submission does not relieve the Contractor of its obligation to comply with the terms of this clause.

(3) Based on the maximum error rate defined for the inspection system, the Contractor shall develop a test procedure to demonstrate the error rate. As part of the test plan the Contractor shall include sufficient test quantities to assure 90% statistical confidence in the resultant rates unless otherwise approved by the Government. Once established, the Contractor shall have a documented schedule to routinely monitor the non-conformance and inspection system error rates to assure they do not exceed the maximum rates allotted.

d. As a result of previous practices, the government’s technical data may refer to “Critical I”, “Critical II”, and “Special” characteristics. The use of the term "critical characteristics" within this clause includes Critical I, Critical II and Special characteristics and the use of the term "critical non-conformances" includes those non-conformances pertaining to Critical I, Critical II and Special characteristics. Unless otherwise stated in paragraph “c” of this clause, these characteristics shall be subject to all requirements of this clause.

e. In addition to critical characteristics defined in the government’s technical data, the Contractor shall also identify and document in their contractor developed technical data all known material, component, subassembly and assembly characteristics whose non-conformances would likely result in hazardous or unsafe conditions for individuals using, maintaining or depending upon the product. All additional critical characteristics identified by the Contractor shall comply with the critical characteristic requirements of the technical data package, supplemented herein. The Critical Item Characteristic List (CICL) review process shall be included in the CCC Plan. The Contractor's additional critical characteristics shall be classified in accordance with guidance located at http://www.pica.army.mil/PicatinnyPublic/organizations/ardec/orgchart/quality.html and shall be submitted to and approved by the Government prior to production (DI-SAFT-80970A).

f. In the event that a critical non-conformance is found in the production process, the Contractor, as part of its CCC Plan, shall have procedures in place to ensure:

(1) The non-conformance is positively identified and segregated to ensure that non-conforming product does not inadvertently remain in or re-enter the production process. This control shall be accomplished without affecting or impairing subsequent non-conformance analysis. Final disposition of non-conforming product shall be documented and audited for traceability.

(2) The operation that produced the non-conforming component or assembly and other operations incorporating suspect components or assemblies are immediately stopped. (See paragraph “h” of this clause for exceptions)

(3) The government is immediately notified of the critical non-conformance (electronic mail) (DI-SAFT-80970A).

(4) Suspect material is identified, segregated and suspended from further processing and shipment.

(5) An investigation is conducted to determine the root cause of the non-conformance and the required corrective actions. An evaluation shall also be conducted with regard to suspect material to ensure that no additional critical non-conformances are present. A report of this investigation shall be submitted to the government (DI-SAFT-80970A). The use of the Data Item Description (DID) report shall not delay notification to the government per paragraph “f (3)” above.

(6) A request to restart manufacturing or to use suspect material associated with the critical nonconformance is submitted to the government (DI-SAFT-80970A). Restart of production shall not occur without written authorization from the Government, unless previously addressed in the approved CCC Plan. The Government will respond to a restart request within 3 working days. All objective evidence of the investigations to date shall be available for review at the time of restart. Suspect material shall not be used without written Government approval.

(7) The procuring activity reserves the right to refuse acceptance of suspect material until the root cause or reasonably likely cause of the critical non-conformance has been identified, corrective action has been fully implemented and sufficient evidence has been provided to exclude non-conforming material from the conforming population.

g. The Contractor may develop alternative plans and provisions, collectively referred to as a CPOA, relative to government and Contractor identified critical characteristics. All CPOAs are independent and shall be evaluated by the government for this contract. The CPOA and all subsequent revisions require written Government approval prior to implementation. Unless otherwise specified by the Government at time of CPOA approval, the Contractor shall review and evaluate CPOAs for currency and process improvements on an annual basis and submit results to the Government. Unless otherwise approved by the Government, each critical characteristic shall require a separate CPOA. If the CPOA includes other documents by reference, they shall be submitted upon request. Guidance for the development of a CPOA can be found in the referenced guidance located at paragraph “a” above.

h. The Contractor may continue production with an approved CPOA provided that the critical non-conformance is consistent with the failure mode(s) and rates established in the CPOA. Failure to meet all CPOA requirements shall require the Contractor to revert back to paragraph “f” requirements.

i. If a critical non-conformance is discovered beyond its designated inspection point and prior to Government acceptance the Contractor shall take actions specified in paragraph “f”. If a critical non-conformance is discovered after Government acceptance the Government has the right to invoke the requirements of paragraph “f” with respect to the Contractor’s remaining production under this contract.

3.5.2 Restriction on Use of Energetics Over Five Years Old. Unless a shorter time period is required elsewhere in this contract or in the specifications associated with this contract, all energetic materials used in components or end items produced under this contract shall be no more than five years old from the date of energetic component manufacture. The Government will entertain requests to use energetic materials more than five years old; however, such requests shall be submitted to the Government. Approval may involve cost consideration and may require independent testing at Contractor’s expense. The Government makes no commitment to approve such requests regardless of cost consideration offered or test results obtained. Energetic materials provided by the Government for use on this contract are excluded from the provisions of this clause. The Contractor will not be held responsible for Government Furnished Material (GFM) energetics.

3.6 Software.

3.6.1 Software Requirements Specification. The Contractor shall provide a Software Requirements Specification (SRS). The SRS shall specify the requirements for the SCIs and the verification methods to be used to ensure that each requirement has been met.

CDRL A00Z: DI-IPSC-81433A, Software Requirements Specification (SRS)

3.6.2 Software Architecture Description. The Contractor shall provide a Software Architecture Description (SAD). The SAD shall provide architectural views to show the software architecture achieves all of the specified quality attribute requirements. The SAD shall provide a complete packet of information for each view, which includes: a primary graphical presentation; an element catalog that explains the elements and relations in the primary presentation; a variability/options guide that describes points in the architecture that can change across versions, can be reconfigured or simply are not defined yet; rationale for non-obvious design decisions or decisions that are the source of questions, are critical, or have a widespread effect; relevant constraints, rejected alternatives, ramifications of the decision, and evidence that the…