HQ0858-20-R-0002 Atch J-01 TEAMS-Next QMA SOW_050620.pdf

HQ0858-20-R-0002

Attachment J-01 Quality and Mission Assurance (QMA) SOW

Approved for Public Release 20-MDA-10459 (15 Apr 20)

TEAMS-Next Statement of Work

Quality and Mission Assurance

(QMA) 06 May 2020

Approved for Public Release 20-MDA-10459 (15 Apr 20)

Revision History

Author Date MR Number P00000 Reason For Change(s) SOW Version

1.0 Top Level Overview

1.1 Purpose

This Statement of Work (SOW) supports the Missile Defense Agency's (MDA) mission to develop, test, and field an integrated, layered, Missile Defense System (MDS) to defend the United States (U.S.), its deployed forces, allies, and friends against all ranges of enemy ballistic missiles in all phases of flight. The types of support required includes: 1) engineering and technical support; 2) studies, analyses, and evaluations, and

3) management and professional services.

1.2 Organizational Description and General Requirements

1.2.1 Organizational Description

1.2.1.1 Mission

The Missile Defense Agency’s mission goal is “to develop and deploy a layered Missile Defense System to defend the United States, its deployed forces, allies, and friends from missile attacks in all phases of flight.”

1.2.1.2 Overview

The Missile Defense Agency established the Quality, Safety and Mission

Assurance (QS) organization to perform a continuous assessment of the engineering, technology, processes, production, and programmatic practices used to develop and operate the MDS such that high risk attributes can be identified and addressed to increase confidence in achieving mission success while ensuring personnel safety. Mission assurance is the disciplined application of general system engineering, risk management, quality, and management principles to achieve mission success. A disciplined mission assurance process has independent technical assessment as a cornerstone throughout the entire planning, design, development, fabrication, test, deployment, and support processes.

The QS Directorate plans, executes, analyzes, and reports technical results for all MDA operations and MDS design, development, production, testing and operations. The QS Directorate functions as an independent, unfettered and unrestricted, non-advocate technical organization for the MDA with a specific focus on mission success and personnel safety. It provides executive guidance and policy direction on all Quality, Safety and Mission Assurance

(QSMA) matters throughout the MDA and assures compliance with QSMA strategies, policies, agreements, and standard practices to advance capabilities and assures that effective and efficient functional management is in place to enhance the success of the agency. It also assesses compliance with applicable governing MDA guidance and reports results to MDA Leadership.

1.2.1.3 Organizational Structure

The QS Leadership consists of the QS Director, a Deputy Director, a Chief

Engineer, a Deputy Chief Engineer, a Financial Manager and a Business

Operations Manager. The QS MDS Division Chiefs for Safety (QSS), including Safety &Occupational Health; Operations Safety (QSO); Mission

Assurance (QSI), Quality (QSQ), including Test Assurance; Parts, Materials and Processes (QSP); Radiation Parts, Materials and Processes (QSR);

Verification (QSX); and Field Assurance (QSF) manage the overall execution of the MDA MDS in achieving mission success while ensuring personnel safety. The QS Program Functional Leads consists of THAAD (THQ), Ground Sensors (SNQ), C2BMC (BCQ), Targets & Countermeasures (TCQ), Ground-based Midcourse Defense (GMQ), Sea-Based Weapon Systems

(ABQ), Advanced Technology (DVQ), U.S.-Israeli Cooperative Program

Office (IPQ) and Advanced Technology, Sensors & Directed Energy

(DVDQ). QS Program Functional Leads manage the QSMA program within the Program Elements and serve as technical advisors to the QS Director and assigned organizations to help enable mission success by providing oversight and insight to acquisition, development, fielding, integration, and operations.

The Functional Leads are responsible for coordinating the daily tasking of assigned functional personnel and providing working level interface between

MDA functions, programs, and QS Directorate.

The QS governing document is the MDA Assurance Provisions (MAP). This document is a standardized set of 14 QSMA provisions, requirements, and processes that apply to mission and safety critical items. The MAP gives

MDA the methodology to measure, verify, and validate mission success through collection and analysis of metrics, risk assessment, technical evaluations, independent assessment, reviews, conducting tests, and promoting continuous process improvement to reduce cost, improve productivity, and institute QSMA.

The QS organization is shown in Figure 1.2.1.3.1.

Figure 1.2.1.3.1 – QS Directorate Organization Chart

1.2.2 General Requirements

1.2.2.1 Organizational Conflict of Interest (OCI)

The QMA Contractor shall manage potential/emergent OCI as set forth in the

H-09 clause; specifically, throughout performance, the QMA Contractor shall promptly request Procuring Contracting Officer (PCO) consent (pursuant to the process set forth in H-09(f)(2)) prior to adding any new Subcontractors

(at any tier regardless of Subcontractor dollar threshold or business arrangement) to properly ensure enforcement of OCI.

The Contractor shall require all employees, and all Subcontractor employees at all tiers, to sign the Missile Defense Agency Non-Disclosure Agreement

(MDA NDA) set forth in Section J Attachment 06 within 10 days of employment. The signed forms shall be submitted to the PCO and the primary Contracting Officer’s Representative (COR) within 10 days of employee signature.

The Contractor shall continuously enforce the OCI requirements throughout

Subcontractor period of performance and report any Subcontractor (at any tier regardless of subcontractor dollar threshold or business arrangement) that violates the OCI requirements of this contract to the PCO and primary COR immediately.

1.2.2.2 Non-Personal Services

The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required work within the hours invoiced for each employee. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are personal services in nature, or give the perception of personal services as defined in

Federal Acquisition Regulations (FAR) 37.104. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor’s responsibility to notify the PCO and primary COR immediately.

1.2.2.3 Business Relations

The Contractor shall successfully integrate and coordinate all activities needed to execute the requirement. The Contractor shall manage the timeliness, completeness, quality of problem identification, and fraud prevention/reporting (i.e., obligation to ensure expenses charged to the contract are properly accounted for before submitting invoices to MDA). The

Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of Subcontractors. The

Contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all Contractor personnel in support of the United States

Government.

1.2.2.4 Technology Assistance Agreement

The Contractor shall obtain and maintain a Technology Assistance

Agreement (TAA) as defined by the International Traffic Arms Regulation

(ITAR) with the Government of Israel (GOI) in order to allow technical discussions between representatives of the Contractor and representatives of

GOI and Israeli industry (GOI contractors). The Contractor shall develop, implement and maintain a strategy that will cover its direct employees and any sub-contract employees.

1.2.2.5 Contractor Flight and Ground Operations involving Air Force

The contractor shall comply with non-crewmember requirements set forth in

DCMA Instruction 8210.1C Change 1 dated April 5, 2017 (Air Force

Instruction 10-220), “Contractor’s Flight and Ground Operations” as applicable.

1.3 Applicable Documents

The following documents are applicable to this SOW:

1.3.1 MDA Instruction 8360.01 INS, “Test Event Certification (TEC) Instruction”

1.3.2 MDA Instruction 3058.01-INS, “Risk Management”

1.3.3 MDA PMAP (REV A)

1.3.4 MDA PMAP (REV B)

1.3.5 MDA PMAP (REV C)

1.3.6 MDA MAP (REV A)

1.3.7 MDA MAP (REV B)

1.3.8 MDA MAP (REV C)

1.3.9 MDA Policy Memorandum #22, “Additional Requirements for Plastic

Encapsulated Microcircuits with Copper Wire Bonds.”

1.3.10 MDA Policy Memorandum #86, “Parts, Materials, and Processes Requirements

Verification.”

1.3.11 MDA Policy Memorandum #50, “MDA Policy on Purchasing Electronic Parts”

1.3.12 QS-INST-03, “QS End of Week (EOW) Report Development Operating

Instruction.”

1.3.13 QS-INST-07, “QSMA Contracting Handbook and Guide”

1.3.14 QS-SOP-01, “QS Concept of Operations (CONOPS)”

1.3.15 QS-SOP-06, “MDA Quality Safety, and Mission Assurance Audit Program

Standard Operating Procedure”

1.3.16 QS-SOP-10, “MDS Program Flight Test Support”

1.3.17 QS-SOP-13, “MDA QS Ground Test Support”

1.3.18 QS-SOP-16, “Pedigree Review Standard Operating Procedure”

1.3.19 SAE AS9100D

1.3.20 SAE AS9102, Aerospace First Article Inspection Requirement

1.3.21 Joint Travel Regulation (JTR), at https://www.defensetravel.dod.mil/

1.3.22 Synchronized Pre-deployment and Operational Tracker (SPOT), at https://www.acq.osd.mil/log/PS/.spot.html

1.3.23 DCMA Instruction 8210.1C Change 1 dated April 5, 2017 (Air Force Instruction

10-220), “Contractor’s Flight and Ground Operations” at https://www.dcma.mil/Portals/31/Documents/Policy/DCMA-INST-8210-1C-

C1.pdf?ver=2019-08-14-070818-860

Note: If any document referenced in Section 2 is replaced or superseded, the replacement or superseding document shall be applicable to this SOW unless MDA provides other guidance.

https://www.defensetravel.dod.mil/ https://www.acq.osd.mil/log/PS/.spot.html https://www.dcma.mil/Portals/31/Documents/Policy/DCMA-INST-8210-1C-C1.pdf?ver=2019-08-14-070818-860 https://www.dcma.mil/Portals/31/Documents/Policy/DCMA-INST-8210-1C-C1.pdf?ver=2019-08-14-070818-860

2.0 Data Rights and Government Information Protections

2.1 Data Rights

The Contractor shall comply with government data rights In Accordance With (IAW) the Defense Federal Acquisition Regulations Supplement (DFARS), as identified below:

All data (including but not limited to technical data, computer software, algorithms and related models, and documentation) produced or developed under this contract shall be delivered to the Government with unlimited data rights; source code shall be delivered for all computer software produced or developed under this contract. During contract performance, data shall be delivered to the contracting officer in its entirety upon written request. Absent such a request, all data produced or developed under this contract shall be delivered by the end of contract performance. Data shall be produced or developed with only Government funds. Open source computer software shall not be incorporated into any deliverable absent prior written approval from the PCO.

2.2 Government and Proprietary Information

In the performance of this contract, the Contractor may be provided access to privileged government information. Government information may include items such as plans, policies, reports, studies, financial plans, or data which has not been released or otherwise made available to the public. The Contractor shall ensure that all such information is protected in accordance with any restrictions imposed on such information. The contractor agrees that that without the prior written approval of the

Contracting Officer, it shall not:

1) Use such information for any private purpose unless the information has been released or otherwise made available to the public.

2) Compete for work based on such information after the completion of this contract, or until such information is released or otherwise made available to the public, whichever occurs first.

3) Submit an unsolicited proposal to the Government which is based on such information after such information is released or otherwise made available to the public, whichever occurs first.

4) Submit information unless such information has previously been released or otherwise made available to the public by the Government.

The Contractor agrees that, to the extent it receives or is given access to proprietary data, trade secrets, or other confidential or privileged technical, business, or financial information (hereinafter referred to as "proprietary data") under this contract, it shall treat such information in accordance with any restrictions imposed on such information.

The Contractor further agrees to enter into a written agreement for the protection of the proprietary data of others and to exercise diligent effort to protect such proprietary data from unauthorized use or disclosure.

2.3 Non-Disclosure Agreements

The Contractor shall obtain from each employee under this contract, a written MDA

NDA (Section J Attachment 06) which shall provide that the employee shall not, during his/her employment by the Contractor or thereafter, disclose to others or use for their benefit, privileged government information or proprietary data received in connection with the work under this contract. The Contractor shall educate its employees regarding the philosophy of FAR Part 9.505-4 so that they will not use or disclose government information or proprietary data acquired in the performance of this contract.

The MDA NDA is required of all Contractor employees and Subcontractors supporting under this effort as provided in SOW 1.2.2.1 above; however, there may be additional

NDAs required (i.e., H-16, Planning, Programming, Budgeting and Execution (PPBE)) dependent upon the support required at any given time throughout period of performance of the contract. The Contractor shall certify completion of the MDA NDA requirement and others applicable NDAs for each employee via the Monthly Manpower Report

(Contract Data Requirements List (CDRL) A004).

3.0 Scope of Work

3.1 Specific Requirements/Tasks

3.1.1 Contract Program Management

a) Manage and execute all activities under this contract, including those of subcontractors, suppliers, and any and all sub-tier vendors.

b) Serve as the focal point to the Government Contracting Office Point of

Contact (POC).

c) Conduct and integrate all aspects of the contract such as schedule, cost, risk and opportunity management.

d) Provide the necessary administration required to support the contract.

e) Schedule monthly meetings, and discussions with Stakeholders on programmatic and technical topics related to:

Contractor performance

Hiring status

Travel and other direct cost projections and funding status

Identify, estimate and report to Government contacts expected increases to budget prior to cost being incurred

Develop alternative approaches to accomplishing increases in tasks without increases to budget

3.1.2 Technical Writing

a) Utilize MS Office software to prepare comprehensive weekly activity report/s with status of issues IAW QS-INST-03, “QS End of Week (EOW) Report

Development Operating Instruction.

b) Develop and disseminate reports encompassing QS Core and

Program/Element events/efforts.

c) Coordinate with stakeholders to resolve any communication and reporting shortfalls.

d) Coordinate between weekly status report authors to provide one input with all relevant details to subject.

e) Provide status updates through technical discussions, technical reports, trip reports, and presentation materials.

f) Leverage a basic understanding of quality (AS9100 or equivalent), program management, systems thinking, and risk analysis during technical writing activities.

3.1.3 Technical Assurance Implementation

The Contractor shall support the implementation of MDA quality and mission assurance requirements by (1) participating in the development and compliance verification of processes used for the design, development, test, and evaluation of mission critical hardware and software and (2) providing technical evaluations of

Developer designs for subcomponents, assemblies, and integrated systems associated with MDA programs. In support of QS activities the Contractor shall provide the following functions:

a) Prepare draft documents, briefs, presentations, and actions items responses, which may include information papers.

b) Assist with developing and/or maintaining QS Directorate directives, policies, and Standard Operating Procedures (SOPs).

c) Retain and retrieve QS documentation, including maintaining and verifying

QS security files and classified inventory.

d) Facilitate meetings involving QS personnel. Serve as liaison between QS organizations and non-MDA communities. Provide situational awareness and status of changes from meetings.

e) Assist with planning the development and refinement of QS directives, policies, memorandums, advisories, and instructions.

f) Assist with implementing QS command media in support of all MDA elements and all phases of the MDS life-cycle.

g) Assist with evaluating QS-related outcomes across the all MDA elements and all phases of the MDS life-cycle.

h) Assist with reporting both successful and unsuccessful outcomes resulting from the implementation of QS command media across all MDA elements and all phases of the MDS life-cycle.

i) Assist with coordinating the integration of quality assurance processes within and between both all QS core and all QS matrixed organizations.

j) Assist with developing QS annual accomplishment report.

3.1.4 Ground and Flight Test Configuration Verification

The QS role is to ensure Flight and Ground Testing is performed in a safe and successful manner, in accordance with Missile Defense Agency (MDA) policies and practices. QS establishes a QS Flight Test Team (FTT) and Ground Test

Team (GTT) for the development and implementation of quality and mission assurance plans to support Flight and Ground Test events.

assurance requirements by (1) collecting and documenting hardware and software configuration management records for flight and ground operational tests and (2) recording, reporting, and tracking test observations/findings to closure. In support of QS activities the Contractor shall provide the following functions:

a) Track, record and confirm configuration of system test participants.

b) Identifies test configuration items, monitors change control, implements configuration status tracking and accounting, and conducts configuration verification in support of system tests.

c) Works with test teams to create and maintain software, hardware, and documentation configuration baselines in support of system tests.

d) Develops, reviews, or modifies instructions, plans, policies, and procedures governing the configuration management, test event certification, test configuration lockdown, and recording, tracking and monitoring of test observations/deviations.

e) Monitors test execution activities and identifies/records test observations/deviations.

f) Implement quality processes throughout the system test preparation, execution, and reporting process.

g) Monitors and reports on the test change processes and change boards to determine if only approved and validated changes are incorporated.

h) Reviews and reports on problems and changes to the system test documents, standard operating procedures, and current test configurations for completeness, accuracy, and correctness.

i) Develops and coordinates system test event certification checklist, collects required checklist documentation, and verifies test participant configuration as required.

3.1.5 Mission Assurance Implementation

Mission Assurance is the disciplined application of general system engineering, risk management, quality, and management principles to achieve mission success.

A disciplined mission assurance process has independent technical assessment as a cornerstone throughout the entire planning, design, development, fabrication, test, deployment, and support processes.

assurance requirements by (1) providing technical evaluations of Developer designs for subcomponents, assemblies, and integrated systems associated with

MDA programs and (2) providing subject matter expertise for the identification, evaluation, and mitigation of risks associated with various aspects of the design, development, manufacturing, fielding and operation of MDA systems. In support of QS activities the Contractor shall provide the following functions:

MDS Policies and Requirements Development and Execution

a) Provide insight into implementation and execution of MDA MAP and PMAP requirements on MDA development efforts.

b) Support the review, coordination, and response to agency internal taskers from a mission assurance perspective.

c) Participate in first article inspection processes on manufactured or purchased mission critical items (per SAE AS9102, Aerospace First Article Inspection

Requirement).

d) Assist in preparation, presentation, and action item tracking and resolution related to program reviews and meetings addressing development, operations, and testing of the MDS.

e) Assist with the development, dissemination, and implementation of emerging

MDA mission assurance policies and requirements including but not limited to, directives, policies, memorandums, standard operating procedures, operating instructions, and advisories.

f) Provide technical support or present government opinions at senior level meetings as a mission assurance representative.

g) Support mission assurance assessments and audits (per MAP, PMAP, and the

QS Directorate standard operating procedures (SOP), QS-SOP-06, “MDA

Quality Safety, and Mission Assurance Technical Assessment Program

Standard Operating Procedure”). Activities include (1) planning assessments, conducting assessments, reporting findings, and correcting findings and (2) providing on-site verification and auditing at Developer facilities to ensure that robust controls are in place for quality assurance practices including foreign object debris, electrostatic discharge, and contamination.

h) Provide strategic recommendations related to identifying and addressing mission assurance trends and patterns affecting missile defense systems, elements, and components.

i) Provide weekly status reports on activities and issues of concern.

MDS Technical Risk Assessment

Evaluate the current risk level of baseline system designs, as well as the impact of baseline changes to the overall system risk profile. Assist in communicating issues and risks. Prepare risk notification reports.

j) Engage in the MDS-level risk management meetings and assist in developing and communicating independent QS Directorate comments, positions, and recommended changes through the MDA risk management process (per MDA

Instruction 3058.01-INS, "Risk Management"). Report results.

k) Assist with developing, implementing, and executing System-Level Pedigree

Reviews (per QS-SOP-16, "QS Pedigree Review Standard Operating

Procedure" and in compliance with the MAP.

l) Review, research, and report information related to the US Department of

Treasury Committee on Foreign Investment in the United States (CFIUS).

Efforts shall encompass MDS safety and mission critical components affected by the transactions with foreign entities.

m) Provide weekly status reports on activities and issues of concern.

MDS Demonstration Activities

n) Participate in mission assurance activities for flight test integration and execution efforts (per QS-SOP-10, "BMDS & Program Flight Test Support

Standard Operating Procedure”).

o) Participate in mission assurance activities for ground test integration and execution efforts (per QS-SOP-13, "MDA/QS Ground Test Support Standard

Operating Procedure”).

p) Witness hardware test activities for mission critical MDS items to identify, address, and report on flaws in test procedures, test set-up, and test configurations.

q) Support the evaluation of broker procured parts used in MDS ground test and flight test hardware and software to determine inherent risk prior to tests.

Brokers are unauthorized suppliers (typically independent distributors) who buy and sell parts or materials without maintaining stock and without Original

Component Manufacturer authorization.

r) Participate and provide technical inputs in readiness reviews (examples but not limited to: Mission Analysis Reviews, Mission Readiness Reviews, Execution Readiness Reviews, and Pre-Ship Readiness Reviews).

s) Review and analyze test documentation issues to assess and address concerns.

t) Assist with developing, implementing, and executing Flight Ready/Fielded

End Item Pedigree Reviews (per QS-SOP-16, "QS Pedigree Review Standard

Operating Procedure" and in compliance with the MAP).

u) Assist in the flight and ground test process to include a daily report of flight hardware and software status after fielding prior to flight.

v) Review and analyze data from test planning and verification and validation activities and prepare assessment reports.

w) Provide weekly status reports on activities and issues of concern.

x) Support design and technical reviews IAW specific program requirements including but not limited to System Requirements Reviews (SRRs), Preliminary Design Reviews (PDRs), Critical Design Reviews (CDRs), Mission System Requirements Reviews (MSRRs), Mission Design Reviews

(MDRs), and Pre-Ship Readiness Reviews (PSRRs).

y) Support product reviews, acceptance, and verifications of hardware and software to (include but not limited to) Pedigree Reviews, Product Acceptance

Reviews (PARs), Pre-Ship Reviews (PSRs), Hardware and Software

Acceptance Reviews, First Article Inspections (FAIs), and Hardware and software developmental and qualification testing.

z) The contractor shall support flight test integration, execution, and mission assurance activities on-site and at deployed locations. Activities include providing on-site verification and auditing at Developer facilities to ensure that robust controls are in place for quality assurance practices including foreign object debris, electrostatic discharge, and contamination.

aa) Observe and witness assembly processes in production, integration, or testing of MDA assets and identify/report issues.

bb) Provide support to design, development, integration, acceptance and operations of Air Launch missile assets, to include on-board aircraft mission support as required.

3.1.6 Software Quality Assurance Implementation

Software Quality Assurance (SQA) reviews and assesses the adequacy of software products and processes to provide assurance that the software processes are appropriate and produce software products of suitable quality for their intended purposes.

assurance requirements by (1) providing software quality support to MDA’s software system acquisition process, (2) providing technical evaluations of

Developer designs for subcomponents, assemblies, and integrated systems associated with MDA programs, and (3) providing subject matter expertise for the identification, evaluation, and mitigation of risks associated with various aspects of the design, development, manufacturing, fielding and operation of MDA systems. In support of QS activities the Contractor shall provide the following functions:

a) Provide technical expertise in software quality assurance to the government for the assigned programs.

b) Provide weekly status reports on software activities and issues of concern.

c) Participate in cross-functional teams conducting software quality evaluations, audits and assessments, for existing and developmental missile defense programs. Activities include providing on-site verification and auditing at

Developer facilities to ensure that robust controls are in place for quality assurance practices including foreign object debris, electrostatic discharge, and contamination.

d) Review, support and assess software development activities based on software development processes and models, as defined in the approved Software

Development Plan, to include all phases of development (examples, but not limited to: requirements, design, code, development, testing(unit and formal), qualification, ground test, flight test, and operational testing and deployment activities).

e) Support Program milestone technical reviews.

f) Participate and provide input for Software Review Boards, failure investigations and failure review boards. Activities include determining root cause of failures of MDA hardware and software.

g) Draft and submit status reports and papers identifying and explaining conditions, issues of concern, status and corrective actions currently open in assigned program. Activities include (1) determining appropriate corrective actions for failures of MDA hardware appropriate corrective actions and software and (2) evaluating effectiveness of corrective actions following implementation.

h) Participate in assessments, tests, or technical interchange meetings to assess processes and practices for compliance with software quality assurance strategies, policies, and standards. Report results. Activities include providing on-site verification and auditing at Developer facilities to ensure that robust controls are in place for quality assurance practices including foreign object debris, electrostatic discharge, and contamination.

i) Review software and firmware developer’s processes and products to assess compliance with applicable government and developer’s documented processes and procedures.

j) Participate in technical meetings and independent software code reviews for software (including but not limited to agile/iterative) development efforts to assess compliance with industry-wide and MDA software quality assurance standards and best practices. Report results.

k) Provide oversight by assessing software products (including but not limited to agile/iterative practices) by participating in meetings, interacting with product owners and team members to integrate quality assurance in software development.

l) Assess software (including but not limited to agile/iterative software development model) quality assurance to include requirements, design, development, testing, and deployment activities.

m) Provide technical expertise, and recommendations to assigned program personnel on any issues or observations.

n) Collect, compile, track, review and assess available software quality assurance metrics for assigned programs.

o) Assess the developer’s Software Quality Plan to confirm software processes and products conform to requirements throughout the life cycle.

p) Support SQA reviews, providing detailed analysis, recommendations for improvement, and accurate reporting.

3.1.7 Manufacturing, Production and Quality Assessments

Manufacturing, Production and Quality assessments and activities ensure the control of systems for operations associated with fabrication and quality, including any related measurement and analysis, which support the fabrication process and ensure specification requirements are achieved, verified, and maintained. Established techniques for monitoring fabrication processes are needed to ensure process capabilities remain adequate to produce required product characteristics and ensure product conformance can be verified using quality verification techniques.

designs for subcomponents, assemblies, and integrated systems associated with

MDA programs and (2) providing subject matter expertise for the identification, evaluation, and mitigation of risks associated with various aspects of the design, of QS the Contractor shall provide the following functions:

a) Provide technical expertise across the program acquisition life cycle in quality, mission assurance and manufacturing to the government for the assigned MDA programs.

b) Apply QMA manufacturing principles and industry best practices to program activities.

c) Participate in cross-functional teams conducting quality, mission assurance and manufacturing evaluations and assessments, for existing and developmental missile defense components. Activities include providing on-site verification and auditing at Developer facilities to ensure that robust controls are in place for quality assurance practices including foreign object debris, electrostatic discharge, and contamination.

d) Support engineering technical and management reviews, to include (but not limited to) System Requirements Reviews (SRRs), Preliminary Design

Reviews (PDRs), and Critical Design Reviews (CDRs), qualification testing and Program Management Reviews (PMRs) and Incremental Engineering

Technical Reviews (IETRs).

e) Provide technical expertise for failure investigations and failure review boards. Activities include determining root cause of failures of MDA hardware and software.

f) Draft and submit status reports and papers identifying and explaining conditions, issues, status and corrective actions present in the programs.

Activities include (1) determining appropriate corrective actions for failures of

MDA hardware appropriate corrective actions and software and (2) evaluating effectiveness of corrective actions following implementation.

g) Participate in assessments, tests, or technical interchange meetings to assess processes and practices for compliance with industry standard and MDA accepted quality, mission assurance and manufacturing strategies, policies, and standards. Report results. Activities include providing on-site verification and auditing at Developer facilities to ensure that robust controls are in place for quality assurance practices including foreign object debris, electrostatic discharge, and contamination.

h) Support manufacturing and test readiness activities, to include (but not limited

to) production readiness reviews (PRRs), pedigree reviews, first article inspections (FAIs), manufacturing assistance activities, Test Readiness

Reviews (TRRs), Risk Working Group, and the MDA four phase test process.

i) Review data from developer’s and track available manufacturing metrics for

MDA programs.

j) Provide weekly status reports on activities and issues of concern.

k) Provide manufacturing on the job training sessions (OJTs), Joint Source

Inspections (JSIs).

l) Provide production/manufacturing expertise to assigned program Technical

Cell.

3.1.8 Configuration and Data Management Functions

Configuration and Data Management applies proven Department of Defense and industry standards and practices in managing configuration and technical data.

Configuration management is a systems engineering process for establishing and maintaining consistency of a product’s performance, functional, and physical attributes with its requirements, design, and operational information throughout the life of the product. Data management is a system of disciplines by which data is generated or acquired to accomplish contractual development, operation and support tasks as required by the contract.

assurance requirements by providing subject matter expertise for the identification, evaluation, and mitigation of risks associated with various aspects of the design, development, manufacturing, fielding and operation of MDA systems. In support of QS the Contractor shall provide the following functions:

a) Provide assessments of developer hardware and/or software configuration and data management support on system, system elements, interfacing systems, components, devices and/or processes.

b) Assist and Support the program office in controlling and monitoring the established Configuration Management Baselines.

c) Collect and gather configuration information to support ground test configurations for hardware and software.

d) Coordinate and/or assist in the preparation for and conduct of the program

Configuration Control Board. Prepares associated summary reports as needed.

e) Support and provide technical recommendation on all Contract Data Items which may pertain to program software/hardware quality.

f) Support the Government program office by assisting in the implementation, use, and oversight of the software change processes used by prime and subordinate contractors for program quality/production.

g) Prepare, coordinate, and occasionally present software/hardware configuration and data management briefings for internal and external leadership.

h) Assist the program office in the development of effective hardware and/or software configuration management requirements for Statements of Work and

Task Orders.

i) Assist the program office in the development, coordination, and implementation of an effective software/hardware change processes and associated documentation.

j) Assist the program office in the effective interface with the appropriate program office functional and product personnel to effectively educate, manage, and implement the program configuration and data management processes.

k) Participate in configuration audits and assessments at the prime/developer contractor, subcontractors, and suppliers, ensuring the effective implementation of the program configuration and data management requirements.

l) Provide weekly status reports on activities and issues of concern.

3.1.9 Parts, Obsolescence

Parts Obsolescence management ensures that obsolescence is managed as an integral part of design, development, production and in-service support in order to minimize cost and its detrimental impact to MDA programs throughout the product life cycle.

designs for subcomponents, assemblies, and integrated systems associated with

MDA programs and (2) providing subject matter expertise for the identification, evaluation, and mitigation of risks associated with various aspects of the design, of QS, the Contractor shall provide the following functions:

a) Assist the program office in the development of effective mitigation plans to reduce or eliminate the program impact of known or potential part/material obsolescence.

b) Participate as an Obsolescence Team Member to monitor original equipment manufacturer (OEM) progress reports and alerts for assigned program obsolescence surveillance and mitigation activities.

c) Participate in scheduled program Obsolescence Working Group (OWG) weekly teleconferences.

d) Participate in Quarterly program OWG meetings and prepare United States

Government (USG) presentation information as required by the OWG chairman.

e) Assist in the preparation of obsolescence input information for USG Program

Management Reviews, Obsolescence "Deep Dives", etc.

f) Monitor Government and Industry obsolescence material alerts to determine if assigned program equipment is impacted. Report information to the OEM via the OWG.

g) Provide obsolescence expertise to OEM/USG technical reviews to include

System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), Incremental

Engineering Technical Review (IETR), etc.

h) Work as a member of program and obsolescence team and assist with solving complex problems.

i) Perform and apply obsolescence management practices and principles to system elements, interfacing systems, components, devices and/or processes.

j) Actively participate in the technical review of developer contractor obsolescence mitigation proposals and associated basis of estimates, and formulate proposed counter positions for use by the USG in negotiations.

k) Participate in task order and contract negotiations as an obsolescence representative.

l) Enter pertinent obsolescence events into the assigned program obsolescence database for the end item effected.

m) Provide weekly status reports on activities and issues of concern.

3.1.10 Materials Corrosion Control

Materials Corrosion Control is the prevention of deterioration by mitigating the chemical reactions that cause corrosion by using design and manufacturing practices that address selection of materials, coating and surface treatments, production processes, system geometry, and by repairs, overhaul, spare parts requirements, and preventive and scheduled maintenance.

In support of QS, the Contractor shall provide the following functions:

a) Work as a member of team, coordinates with the appropriate functional and programmatic personnel) to identify and solve complex corrosion related problems and issues.

b) Perform on-site inspections, training, and assessments of fielded hardware, providing feedback, training, and mitigation to assist the unit in effective preventive and corrective maintenance of the system.

c) Coordinate and schedule inspections, training, and assessments with MDA personnel and with the fielded system units.

d) Work with subject matter experts to develop new and improved techniques for corrosion prevention and mitigation.

e) Review and analyze programmatic corrosion prevention and mitigation requirements, training materials, inspection methods, maintenance techniques, etc. specifications, and test methods.

f) Document findings and assist with the preparation of briefings, technical risk analyses and assessments, and document findings.

g) Provide weekly status reports on activities and issues of concern.

3.1.11 Quality Implementation

The QS governing document is the MDA Assurance Provisions (MAP). This document is a standardized set of 14 QSMA provisions, requirements, and processes that apply to mission and safety critical items. The MAP gives MDA the methodology to measure, confirm, and validate mission success through collection and analysis of metrics, risk assessment, technical evaluations, independent assessment, reviews, conducting tests, and promoting continuous process improvement to reduce cost, improve productivity, and institute QSMA.

assurance requirements by providing subject matter expertise for the identification, evaluation, and mitigation of risks associated with various aspects of the design, development, manufacturing, fielding and operation of MDA systems. In support of QS the Contractor shall provide the following functions:

a) Provide independent quality and related mission assurance engineering expertise in support of assigned MDA program and Foreign Military Sales

(FMS) hardware and software at all levels of the architecture across the entire product life cycle.

b) Assist with review and assessment of hardware and software compliance with quality and related mission assurance requirements, including support of failure investigations, failure review boards, evaluations, audits, and assessments. Activities include determining root cause of failures of MDA

c) Provide technical and data management expertise for quality and mission assurance boards, working groups, and reviews to include (but not limited to) the Parts, Materials, and Processes Control Board, technical and mission reviews, pedigree reviews, first article inspections, and risk working groups.

Activities include managing the MDA’s Parts, Materials and Processes (PMP)

Program.

d) Collect/track available quality and mission assurance metrics for the assigned program.

e) Report on the status of quality and related mission assurance efforts – weekly and periodically consistent with the battle rhythm – to communicate evolving risks, issues, and best practices associated the program.

f) Update and maintain the MDA Supplier Road Map.

g) Assess MDA Assurance Provisions (MAP) core metrics.

h) Review and provide comments on MDA Advisories and Lessons Learned.

i) Prepare draft documents, briefs, presentations, and actions items responses, which may include information papers.

j) Attend Industry Standards meetings. Provide report about changes that have an impact on MDS capabilities/assets and report changes and issues.

k) Assist with developing and/or maintaining QS Directorate directives, policies, and Standard Operating Procedures (SOPs).

l) Retain and retrieve QS documentation, including maintaining and verifying

QS security files and classified inventory.

m) Facilitate meetings involving QS personnel. Serve as liaison between QS organizations and non-MDA communities. Provide situational awareness and status of changes from meetings.

n) Assist with planning the development and refinement of QS directives, policies, memorandums, advisories, and instructions.

3.1.12 Mission Assurance Field Representation (MAR)

MARs provide MDA with a deployed Mission Assurance resource with direct and unfettered supplier insight, with the leverage to affect value added change and mitigate risk in a timely fashion. The MAR’s primary duties are to minimize escapes, drive continuous improvement throughout the supply chain, and provide independent technical assessments. MARs are located across the country in company manufacturing plants and launch sites that MDA has deemed of vital importance.

assurance requirements by (1) providing on-site verification and auditing at

Developer facilities to ensure that robust controls are in place for quality assurance practices including foreign object debris, electrostatic discharge, and contamination and (2) providing subject matter expertise for the identification, evaluation, and mitigation of risks associated with various aspects of the design, of QS the Contractor shall provide the following functions:

a) Serve as a Mission Assurance field site representative at an assigned supplier, launch site, or MDA center providing oversight into all Mission Assurance functions performed at that specific location and associated sub-tier suppliers.

b) Develop a weekly report of significant Mission Assurance issues occurring at the assigned location and associated sub-tier suppliers. The report shall capture significant risks associated with hardware and software items and includes the representative’s risk posture/rationale of these items.

c) Team with MDA Program Offices and DCMA to establish and formalize

Government Requirements for MDA product processed at the location and associated sub-tier suppliers.

d) Participate in Hardware Acceptance Reviews at the assigned location and associated sub-tier suppliers to assess completed MDA product meets all requirements and will perform design intent when fielded.

e) Perform walk-throughs of all manufacturing/ test areas at the location and assess build /test practices to industry standard ESD, FOD and tool control practices. Assess critical lift practices to MDA MAP and industry standard requirements.

f) Participate in program milestone reviews associated with the MDA product processed at the assigned location. Examples include but are not limited to these reviews: Requirements Reviews, Design Reviews, Test Reviews, Program Reviews, Failure Review Boards, and Ship Readiness Reviews.

Activities include (1) providing technical evaluations of Developer designs for subcomponents, assemblies, and integrated systems associated with MDA programs and (2) determining root cause of failures of MDA hardware and software.

g) Travel to other companies/ sites and perform MDA product assessments MAR

Regional Plan (MRP) visits, and complete and submit Supplier Assessments

Reports to the QSI Team Mailbox. (These companies/sites differ from the company/sites where the MAR is physically assigned.)

h) Assess MDA hardware/ software related design, manufacturing and test practices at the assigned location and associated sub-tier suppliers. Ensure these practices meet MDA MAP and industry standard requirements and ensure end items are consistent in characteristics and performance. Activities include providing technical evaluations of Developer designs for subcomponents, assemblies, and integrated systems associated with MDA programs.

i) Assess first article builds, first article tests and major tests at the assigned location and associated sub-tier suppliers to ensure items meet requirements and industry best practices. Perform inspections of MDA product to ensure they meet design requirements and industry best practices.

j) Assess all hardware / software non-conformances associated with MDA product at the assigned location and associated sub-tier suppliers to ensure root cause is accurately identified and determine if associated corrective action is robust. Activities include determining root cause of failures of MDA

k) Assess all repeat anomalies associated with MDA product build/ test to determine why previous root cause was not robust and ensure new corrective action is robust to prevent additional reoccurrences of issue. Activities include determining root cause of failures of MDA hardware and software.

l) Perform MAR duties temporarily for other QSI MARs while they are unavailable.

m) Provide technical/ logistics assistance to QSI Management.

n) Travel to other companies/sites and participate in MDA Audits. Lead the evaluation/closure of associated MDA Audit findings by assessing the root cause/corrective action and validating the company/ site improved policies/practices. Activities include (1) determining root cause of failures of

MDA hardware and software, (2) determining appropriate corrective actions for failures of MDA hardware appropriate corrective actions and software, and (3) evaluating effectiveness of corrective actions following implementation.

3.1.13 Audits and Audit Management Execution

The MDA Verification Organization performs independent assessment & evaluation of MDA field activities, critical contractors and program offices. The assessments focus on: a) the program’s adherence to mission assurance policies,

b) the contractor’s adherence to MDA mission assurance, quality, and reliability requirements, and c) the contractor’s adherence to their own internal policies and procedures. This assessment include an in-depth evaluation of the MDA critical product and assesses its design, quality processes, manufacturing processes, inspections and tests, with the goal of identifying risks and mitigating them.

assurance requirements by (1) providing on-site verification and auditing at

Developer facilities to ensure that robust controls are in place for quality assurance practices including foreign object debris, electrostatic discharge, and contamination, (2) providing technical evaluations of Developer designs for subcomponents, assemblies, and integrated systems associated with MDA programs, (3) providing subject…