WIFT_Solicitation_N68335-16-R-0166.docx

N68335-16-R-0166

Section B - Supplies or Services and Prices

Performance Acceptance Test (PAT) Units

FFP

Design, Develop,Fabricate, and Test Wiring Intermittent Fault Testor in accordance with (IAW) Statement of Work, Section C herein, and and the System Performance Specification, Contract Attachment 1.

FOB: Destination

NET AMT

Technical Data Package

In Accordance With (IAW) Statement of Work (SOW) and CDRLs C001, C002, C003 and C004

NET AMT

Adminisrating & Engineering Data

IAW SOW and CDRLs A001-A022

NSP

NET AMT

Training Curriculum

Operator & Mantenance IAW SOW and CDRL L001

NET AMT

Training Instructions

Computer Based IAW SOW and CDRL M001

NET AMT

Manual

Operation & Maintenance IAW SOW and CDRL N001.

NET AMT

WIFT Production Units

IAW Government approved technical data package and Performance Specification Contract Attachment 1.

MAX

NET AMT

CDRL P001

Design Change Notice (DCN)

NET AMT

CDRL Q001

Request For Variance

NET AMT

CDRL R001

Quality Deficiency Report Response/Corrective Action Report

NET AMT

WIFT Production Units

MAX

CDRL P001

Design Change Notice

NET AMT

CDRL Q001

Request For Variance.

NET AMT

CDRL R001

Quality Deficiency Report Response/Corrective Action Report

NET AMT

WIFT Production Units

MAX

CDRL P001

Design Change Notice

NET AMT

CDRL Q001

Request for Variance.

NET AMT

CDRL R001

Quality Deficiency Report Response/Corrective Action Report

NET AMT

WIFT Production Units

MAX

CDRL P001

Design Change Notice

NET AMT

CDRL Q001

Request For Variance.

NET AMT

CDRL R001

Quality Deficiency Report Response/Corrective Action Report

NET AMT

SUPPLIES OR SERVICES AND PRICE

The maximum quantities identified herein for the production units CLINs 0101, 0201, 0301, and 0401 represent the Government's best estimate of the maximum quantities of anticipated order(s) during that specified ordering period. The CLIN quantities maximums do not impose absolute quantity limits for each ordering period. The maximum quantities for the WIFT production units are not defined on an annual ordering period basis, but rather are defined by the sum of the quantities across all four annual ordering periods.

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF WORK

FOR

V-22 SERD 3809: WIRE INTERMITTENT FAULT TESTER (WIFT)

For all CLINS that may be ordered, The contractor shall provide supplies and/or services in accordance with the Contract N68335-16-R-0166 Statement of Work for V-22 Organizational, Intermediate, and Depot Level Peculiar Support Equipment included herein and any Appendices referenced therein.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

Prepared by: Benjamin Yearwood Naval Air Systems Command Code 4.8.6.7 Lakehurst, NJ

1. SCOPE

0. Purpose This Statement of Work (SOW) defines the specific tasks required to design, develop, test, and produce the V-22 Wire Intermittent Fault Tester (WIFT), along with the logistics support products required to deploy and sustain the WIFT. The WIFT capability need is established in V-22 Support Equipment Recommendation Data (SERD) 3809, and its performance characteristics and design requirements are established in the V-22 WIFT System Performance Specification (SPS).

1. APPLICABLE DOCUMENTS, GUIDANCE DOCUMENTS & INFORMATION

2.1 Government Documents

2.2 Non-Government Documents

2.3 Government Furnished Information

2.3.1 WIFT System Performance Specification (SPS)

The contractor shall design/develop a WIFT that meets all the performance requirements identified in the WIFT SPS, PRF-SPEC-PMA275-WIFT-0001, dated 24 July 2014. The contractor WIFT designs shall be the focal point of the SETR meetings.

2.4 Order of Precedence

In the event of a conflict between the text of this SOW and the references cited within, the text of this SOW shall take precedence. Nothing in this document, however, shall supersede applicable laws and regulations unless exemption has been obtained.

1. PROGRAM REQUIREMENTS

2. Performance Acceptance Test Units (CLIN 0001) Upon issuance of the first delivery order, the contractor shall design, develop, fabricate, test, and deliver V-22 Wire Intermittent Fault Testers (WIFT) that meet the performance requirements specified in the WIFT SPS PRF-SPEC-PMA275-WIFT-0001, dated 24 July 2014. The contractor shall organize, coordinate, and control program activities to ensure compliance with the contract requirements and the timely delivery of the required products.

2. Technical Data Package (CLIN 0002)

3.2.1. System Hardware Product Drawings (Contract Data Requirements List (CDRL) C001) The Contractor shall document the necessary design, engineering, manufacturing, testing and quality assurance requirements information (to include identification of Critical Safety Items, and Critical Application Items) for the WIFT. The contractor shall deliver complete design data IAW CDRL C001. The product drawings shall be fully dimensioned manufacturing drawings that will enable the procurement or manufacture of interchangeable WIFT components that duplicates the physical and performance characteristics of the original WIFT components without any additional design engineering effort. The drawings shall be fully dimensioned manufacturing drawings with electronic attachments including specifications, catalog pages, and other supporting data IAW with best commercial practices.

3.2.2. Software Data Package

3.2.2.1. System Software Specification (CDRL C002)

The contractor shall develop a WIFT System Software Specification (SSS) in accordance with the CDRL. The SSS shall be created based on the WIFT System Performance Specification, the WIFT system hardware utilized in the WIFT design, and the other WIFT design elements and reports. The WIFT SSS shall detail all salient software (SW) performance requirements that shall serve as the SW performance targets that will guide the WIFT SW design and development.

3.2.2.2. System Software Design Detailed Description (CDRL C003) The contractor shall develop a System Software Detailed Design Description (SSDDD) in accordance with the CDRL. The SSDDD shall consist of the complete SW functional flow diagram, ranging from the first WIFT input screen or function (when the WIFT is turned-on or enabled) and branching off to every SW function that makes-up the WIFT SW package. The relationship between each WIFT operating state or mode, and the SW that supports these states and modes, shall be presented. The SSDDD shall show all human input options and the resulting post a priori functional options – this shall be presented in functional flow format. The various optional functional flows for each WIFT test mode shall be presented. The SSDDD shall also describe all software (and SW versions) utilized to create each part of the total WIFT SW package. The SSDDD shall also detail all internal SW tables and databases. The SSDDD shall fully present the functional WIFT SW design and define the specific SW solutions used to achieve each function. Note that the SSDDD shall not present the bulk code that makes-up the WIFT SW – some code may be presented for purposes of clarity. All proprietary SW used in the WIFT SW package shall be clearly identified in the SSDDD. The SSDDD shall show the relationship of each SW function to its associated requirement detailed in the WIFT SSS.

3.2.2.3. Requirements Traceability Matrix (RTM) (CDRL C004)

The contractor shall develop a Requirements Traceability Matrix in accordance with the CDRL. The RTM shall cross reference every requirement in the WIFT System Performance Specification to its corresponding WIFT functional, performance, operating or design feature, or component. The WIFT functionality shall be broken down such that every requirement detailed in the WIFT SPS can be associated with a corresponding WIFT feature or component. A preliminary RTM shall be developed and presented at the Preliminary Design Review (PDR). This RTM shall be limited to the WIFT functional blocks, performance parameters and operating states and modes. The final RTM shall be developed and presented at the Critical Design Review (CDR) and shall also include requirements traceability to aggregate components (aggregate components includes circuit boards, displays, wire harnesses, meters, power supplies, etc; they do not include piece parts such as individual wires, resistors, chips, etc.)

3.2.3. Technical Data Rights

The Contractor shall submit any additional data rights assertions at PDR and CDR that were not previously asserted at time of proposal submission. All data rights assertions shall be in accordance with the clauses at DFARS 252.227 contained in section I of the solicitation.

2. Data and Administration (CLIN 0003)(NSP)

3.3.1 System Engineering Technical Reviews

The contractor shall coordinate and conduct System Engineering Technical Reviews (SETRs), which shall be conducted at the contractor’s facility. SETRs will be co-chaired by Government and Contractor representatives. The contractor shall prepare Meeting/Conference Agendas and Meeting Minutes for all SETRs.

During the SETRs the contractor shall explain the reasoning, assumptions, and methodologies for reaching particular conclusions, making recommendations, or choosing alternatives or design approaches to accomplish the tasks required by the contract. The contractor shall have key personnel available to make all technical presentations and generally execute the conference. Subcontractors shall be present whenever necessary to address key matters related to their involvement.

Except where noted herein, conferences and reviews shall be considered fulfilled when all of the following items are completed:

· A formal conference or meeting has been conducted and material has been formally presented to the Government

· All action items requiring Contractor response have been resolved

· All exit criteria are satisfied.

3.3.1.1 Post Award Review

Post Award Review The contractor shall host the government at a post award review between 30 and 45 days after contract award (DACA). The contractor shall inform the government of the dates and location of the Post Award Review not later than (NLT) 10 DACA. For planning purposes, the contractor shall assume the Post Award Review shall be three working days in duration. The purpose of the Post Award Review is first to ensure that all parties to this contract share a mutual understanding of all of the requirements of this contract development effort. The second purpose is to kick-off and baseline the technical and ILS development effort for the WIFT.

3.3.1.1.1 Post Award Review Entry Criteria

A) Contract Award B) Notification by the contractor and concurrence by the government of the location and dates for the review C) Submittal of the meeting agenda by the contractor and concurrence by the government D) Contractor submittal of the following contract data deliverables NLT 15 working days prior to the start of the Post Award Review:

a) Meeting Agenda (CDRL A001)

b) SETR PowerPoint Presentation (CDRL A003)

3.3.1.1.2 Post Award Review Proceedings

A) Achieve clear and mutual understanding of all contract requirements, and identify and resolve potential problems.

B) The contractor shall facilitate discussion utilizing the SETR Review PowerPoint Presentation (A003)

C) Converse with contractor on their methodology for contractor developed Program Management Plan (CDRL A004) including the Integrated Master Schedule (CDRL A005) to ensure that the plan is rational, efficient, integrated and executable.

D) Converse with contractor on their methodology for the contractor developed Risk Management Plan (A008) to evaluate the accuracy of the program risk assessments and to determine the effectiveness of the proposed risk mitigation management approached.

E) Consign action items to the contractor or government as required.

3.3.1.1.3 Post Award Review Exit (Pass) Criteria

A) Basic agreement between the contractor and the government regarding the contract and program plans.

B) Adjudication of all contractor action items.

C) Submittal by the contractor and approval by the government of the Post Award Review Minutes.

3.3.1.2 Preliminary Design Review (PDR)

The contractor shall host a PDR no later than 90 days after successful completion of the Post Award Review. The contractor shall notify the Government of the date and location of PDR NLT 30 days before the scheduled start of PDR. The PDR is planned to be three days in duration.

3.3.1.2.1 Preliminary Design Review Entry Criteria

A) The Post Award Review has been successfully completed (Passed)

B) The PDR agenda has been submitted and approved

C) All contractor action items with resolution dates preceding PDR have been resolved

D) Program and engineering CDRL items with due dates prior to PDR have been delivered, including:

a) Meeting Agenda (CDRL A001)

b) SETR Review PowerPoint Presentation for PDR (CDRL A003)

c) Program Management Plan (CDRL A004) & Integrated Master Schedule CDRL A005)

d) System Engineering Plan & Design Engineering Plan (SEP & DEP) (CDRL A006)

e) Preliminary Test & Evaluation Master Plan (TEMP – To include Acceptance Test Plan) (CDRL A007)

f) Program Risk Management Plan (CDRL A008)

g) WIFT Preliminary Hardware & Software Design Reports including:

1) System Design Theory & Concept of Operation Report (CDRL A009)

2) Preliminary Human – System Interface Design Report (CDRL A010)

3) Preliminary System Hardware Product Drawings (CDRL C001)

4) Preliminary System Software Development Plan (CDRL A011)

5) Preliminary System Software Specification (CDRL C002)

6) Preliminary System Software Design Detailed Description (CDRL C003)

7) Preliminary Failure Modes, Effects and Criticality Analysis (CDRL A012)

8) Preliminary Source Data for Instrument Calibration Procedures (CDRL A014)

9) Preliminary Reliability & Maintainability Analysis & Prediction (CDRL A015)

10) Requirements Traceability Matrix (RTM) (CDRL C004))

11) NAVAIR Cyber Security Implementation Plan (CDRL A016)

12) Calibration Measurement Requirements Summary (CMRS) (CDRL A013)

13) Diminishing Manufacturing Sources & Material Shortages (DMSMS) Plan (CDRL A022)

E) Logistics CDRL including:

1) Preliminary Operator Training Course & Curriculum Outline (CDRL L001)

2) Preliminary WIFT Operations & Maintenance Source Data (CDRL L002)

3.3.1.2.2 Preliminary Design Review Proceedings

At a minimum, the PDR shall address the following discussion topics:

A) Program Management

B) Systems Engineering

C) Program Risk Assessments, Mitigation and Management

D) Hardware and software design approaches

E) Hardware and software design details

F) Technical problems and their proposed solutions

G) Design for Electromagnetic Environmental Effects (E3) and Environmental compatibility

H) Reliability and Maintainability (R&M) predictions and design considerations

I) Discussion of Test and Evaluation Master Plan

J) Review and discuss all CDRLs

K) ILS Program Milestones

3.3.1.2.3 Preliminary Design Review Exit (Pass) Criteria

A) A formal PDR meeting has been conducted and material has been formally presented to the Government

B) The contractor has prepared and submitted and the government has approved comprehensive meeting minutes (CDRL A002)

C) All preliminary and interim CDRL submitted for PDR are accepted by the government

D) All action items requiring contractor response have been resolved

E) All PDR exit criteria are satisfied.

3.3.1.3 Critical Design Review (CDR)

The contractor shall host a CDR no later than 90 days after successful completion of the PDR. The contractor shall notify the Government of the date and location of the CDR NLT 30 days before the scheduled start of CDR. The CDR is planned to be three days in duration.

3.3.1.3.1 Critical Design Review Entry Criteria

A) The PDR has been successfully completed (Passed)

B) The CDR agenda has been submitted by the contractor and approved by the government

C) All contractor action items with resolution dates preceding CDR have been resolved

D) Program and engineering CDRL items with due dates prior to CDR have been delivered, including:

a) Meeting Agenda (CDRL A001)

b) SETR Review PowerPoint Presentation for CDR (CDRL A003)

c) Program Management Plan (CDRL A004) & Integrated Master Schedule (CDRL A005)

d) System Engineering Plan & Design Engineering Plan (SEP & DEP) (CDRL A006)

e) Draft Final Test & Evaluation Master Plan (TEMP) - To include Acceptance Test Plan) (CDRL A007)

f) Program Risk Management Plan (CDRL A008)

g) WIFT Preliminary Hardware & Software Design Reports including:

1) System Design Theory & Concept of Operation Report (CDRL A009)

2) Draft Final Human – System Interface Design Report (CDRL A010)

3) Draft Final System Hardware Product Drawings (CDRL C001)

4) Draft Final System Software Development Plan (CDRL A011)

5) Draft Final System Software Specification (CDRL C002)

6) Draft Final System Software Design Detailed Specification (CDRL C003)

7) Draft Final Failure Modes, Effects and Criticality Analysis (FMECA) (CDRL A012)

8) Traceable Calibration Certifications (TCC) (CDRL A014)

9) Draft Final Reliability & Maintainability Analysis and Prediction (CDRL A015)

10) Final Requirements Traceability Matrix (CDRL C004)

11) NAVAIR Cyber Security Implementation Plan (CDRL A016)

12) Draft Final Calibration Measurement Requirements Summary (CMRS) (CDRL A013)

13) Draft Final Diminishing Manufacturing Sources & Material Shortages (DMSMS) Plan (CDRL A022)

E) Logistics CDRL including:

1) Draft Final Operator Training Course & Curriculum Outline (CDRL L001)

2) Draft Final WIFT Commercial Operations & Maintenance Manual (CDRL L002)

3) Computer Based Training (CBT) Instructions (CDRL L003)

3.3.1.3.2 Critical Design Review Proceedings

At a minimum, the CDR shall address the following discussion topics:

A) Program Management

B) Systems Engineering

C) Program Risk Assessments, Mitigation and Management

D) ILS Development

E) Hardware and software design approaches

F) Hardware and software design details

G) Technical problems and their proposed solutions

H) Design for Electromagnetic Environmental Effects (E3) and Environmental compatibility

I) Reliability and Maintainability (R&M) predictions and design considerations

J) Discussion of Test and Evaluation Master Plan

K) Review and discuss all CDRLs

L) Conduct a review and assess test readiness of the plans to perform WIFT component level, sub-system level and system level testing prior to delivery of the six PAT units to the government (this testing shall be performed by the contractor)

3.3.1.3.3 Critical Design Review Exit (Pass) Criteria

A) A formal CDR meeting has been conducted and material has been formally presented to the Government

B) The contractor has prepared and submitted, and the government has approved, comprehensive meeting minutes (CDRL A002)

C) All Final Draft and interim CDRLs submitted for CDR are accepted by the government. Once these CDRLs are approved, they will become the baseline documentation for the design and fabrication of the Performance Acceptance Test (PAT) Units that will be utilized for Test and Evaluation.

D) All action items requiring contractor response have been resolved

E) All CDR exit criteria are satisfied.

3.3.1.4 Pre-Production WIFT Fabrication

After successful completion of CDR, the contractor shall fabricate six PAT units that will be utilized for Test and Evaluation. The fabrication of the six PAT testers shall be completed NLT 120 days after successful completion of CDR.

3.3.1.5 WIFT Test Readiness Review (TRR)

The contractor shall host the government for a Test Readiness Review NLT 60 days prior to the commencement of PAT, including: Qualification (performance and environmental) Testing, Technical Evaluation (TECHEVAL) (Verification), FLEET Suitability Evaluation (SUITEVAL) (Validation) and logistics (Operator Manual and training materials) validation. The purpose of the TRR is to ensure that all required equipment, materials, personnel, assets (such as operational aircraft), resources (funding, personnel or other) and all schedules for the WIFT test program are in place and ready. During the TRR the contractor and the government shall also conduct the 100% review of the WIFT draft final Operators Manual and training materials. The TRR is planned for a two day meeting duration. The TRR is planned to be conducted approximately 60 days after successful completion of CDR.

3.3.1.5.1 Test Readiness Review Entry Criteria

A) Successful completion of CDR (PASS) B) Government acceptance of all required CDRLsC) Successful WIFT component, subsystem and system testing, and ongoing low risk fabrication of the six PAT units.

D) Planning, organizing and programming for the WIFT test and evaluation events E) Program and engineering CDRL items with due dates prior to Final TRR have been delivered, including:

a) Meeting Agenda (CDRL A001)

b) SETR Review PowerPoint Presentation for TRR (CDRL A003)

c) Program Management Plan (CDRL A004) & Integrated Master Schedule CDRL A005)

d) System Engineering Plan & Design Engineering Plan (SEP & DEP) (CDRL A006)

e) Final Test & Evaluation Master Plan (TEMP – To include Acceptance Test Plans) (CDRL A007)

f) Risk Management Plan (CDRL A008)

g) NAVAIR Cyber Security Implementation Plan (CDRL A016)

3.3.1.5.2 Test Readiness Review Proceedings

A) Invite fleet personnel and representatives from testing activities that will be involved in the WIFT DT / OT B) Review TEMP testing events, schedules and resource requirements C) Create (Review) TEMP Team Action Item Listing D) Assess Test Readiness

3.3.1.5.3 Test Readiness Review Exit (Pass) Criteria

The successful completion of the TRR represents the successful start of WIFT Test and Evaluation. TRR pass criteria are:

A) Contractor disseminate TRR minutes and remaining action item listing B) Government acceptance of TRR minutes and remaining action item listing C) Completion of all contractor and government action items required to initiate WIFT DT/OT D) Government approval to begin WIFT Test and Evaluation

3.3.1.6 Performance Acceptance Testing (PAT)

The six WIFT PAT units shall be utilized to accomplish Performance Acceptance Testing. PAT shall consist of both contractor verification testing and government validation testing. The contractor shall plan to complete all contractor PAT and submit test reports within a 180 day period. The contractor shall strive to employ a concurrent testing approach when feasible. Two of the six PAT units are planned to support contractor testing, two are planned to support government testing, and two shall be held by the government should a contingency occur during the contractor PAT that would negatively impact the program schedule (such as the destruction of one of the WIFT PAT units). Should a contingency occur, any additional units given to the contractor shall be used for non-destructive testing only. This option serves to mitigate schedule risk for the WIFT program.

The government reserves the right to attend any contractor PAT event. The contractor shall be prepared to host the government at any PAT event. The contractor shall notify the government of each contractor test event not later than (NLT) 30 days prior to the scheduled start of the test event. This notification shall include the testing location, anticipated start and end date and times and any special requirements to attend the testing (such as safety glasses, ear protection, safety toe boots, security / visit request, etc.). A summary of the major PAT events is presented below. The expanded, detailed PAT schedule shall be included in the TEMP.

3.3.1.6.1 Initial PAT

The contractor shall plan to begin PAT NLT 60 days after TRR approval, and shall be completed within 14 days. The following Initial PAT shall be performed on each of the six WIFT PAT units:

a) Physical Inspection Verification : This will consist of an inspection of the WIFT physical configuration against the approved baseline drawing package.

b) Physical Configuration Specification Requirements Verification: This will consist of a comprehensive check of the WIFT physical configuration, features, properties, layouts and functions against the requirements in the WIFT Specification PRF-SPEC-PMA275-WIFT-0001.

c) Functional Specification Requirements Verification: This will consist of a comprehensive verification of WIFT functional design against the WIFT specification requirements in PRF-SPEC-PMA275-WIFT-0001. This will include WIFT controls, functional flow, displays and software functionality.

Upon conclusion of the above Initial PAT, four of the PAT units shall be shipped to the government to begin government PAT (validation testing). The four PAT units shipped to the government shall be sent to the following address: NAVAIR, Joint Base McGuire-Dix-Lakehurst, SE Bonded Warehouse, Hangar 6, Route 547, Lakehurst, NJ 08733; Marked for V-22 Program SE Account, Phone: 732-323-1042.

The other two PAT units shall remain in the custody of the contractor in order to perform contractor PAT (verification testing).

3.3.1.6.2 Contractor PAT

Contractor PAT shall consist of the following:

a) Performance Verification: This will consist of verification of all WIFT performance requirements called-out in PRF-SPEC-PMA275-WIFT-0001. As part of this testing the government will provide test harnesses and fixtures (as government furnished property (GFP) as specified in PRF-SPEC-PMA275-WIFT-0001 including:

b) Upon completion of the testing outlined above the contractor shall perform WIFT Qualification testing as follows:

c) The contractor shall prepare test reports for each test event and submit for government acceptance IAW CDRL A017. The contractor shall plan to complete all testing and submittal of reports within 180 days (including initial PAT of 3.3.1.6.1). The contractor shall plan to use one WIFT for acceptance and performance testing and the other one for qualification testing.

3.3.1.6.3 Test Failure and Deficiency Reporting (DR)

Each Deficiency shall be classified by relative importance and its impact upon the overall mission performance and capability of the WIFT. A Part 1* (safety/critical), Part I (critical), Part II (major), or Part III (minor) DR classification shall be assigned to each deficiency. Assignment shall be based upon a decision path starting at the Part I* DR definition and working down in severity to the lowest appropriate level, as determined at the sole discretion of the government. Collectively contractor and Government technical knowledge, relevant technical data and experience will be applied properly assess the severity of the deficiency in relation to the impact on the support equipment’s (SE) equipment’s ability to perform its mission safely and correctly, with supporting data presented in the “Test Conditions and Results” section. Deficiency class definitions are as follows

Part I* (safety/critical). Jeopardizes safety. Deficiency results in safety hazard(s) to personnel and/or equipment. Testing shall not proceed until the safety hazard is satisfactorily resolved, as determined by the government.

Part I (critical). Prevents the accomplishment of an operational or mission essential WIFT system capability, or jeopardizes security, life cycle support, or other critical requirements, as determined by the government. Deficiency results in significant degradation in mission accomplishment, technical performance, or supportability. Acceptable workarounds may not be available or may have negative consequences, as determined by the government.

Part II (major). Adversely affects the accomplishment of an operational or mission essential WIFT system capability, life cycle support, or other critical requirements, as determined by the government. Deficiency results in significant degradation in mission accomplishment, technical performance or reliability and maintainability, but a work-around solution is available and potentially acceptable, as determined by the government.

Part III (minor). Minor reduction in technical performance or supportability, but can be tolerated with little or no impact on mission accomplishment.

The contractor shall be required to correct all Part I* and Part I deficiencies. The contractor shall correct all Part II and Part III as directed by the government.

3.3.1.6.4 Government Independent PAT

Government Independent PAT, hereafter referred to as TECHEVAL (Technical Evaluation), is planned for 180 days total duration (including initial PAT of 3.3.1.6.1) and shall consist of the following:

a) Laboratory TECHEVAL: Shall consist of the government re-performing the test performed by the contractor and detailed in 3.1.1.A.B(A) Performance Verification. The government shall have its own set of test harnesses to perform these tests.

b) Electromagnetic Vulnerability (EMV) Testing: This validation testing shall be performed to ensure the ability of the WIFT to withstand the aircraft carrier flight deck environment during operation.

c) On-Aircraft TECHEVAL and Fleet User Suitability Evaluation (TECHEVAL / SUITEVAL): This series of tests and evaluations shall determine the operational effectiveness and suitability of the WIFT to detect and isolate wiring faults on the aircraft in the operational environment. This testing shall include USMC fleet maintainers.

d) The contractor shall be prepared to support the TECHEVAL by providing on demand technical assistance to government test engineers either by utilizing the WIFT PAT units in their possession or by travel to a government test site (the contractor shall plan at least one visit to MCAS New River, NC, by two of their technical personnel with a total travel time of four days). The contractor shall also provide timely answers to government technical inquiries submitted via telephone or e-mail.

3.3.1.6.5 Final Government Acceptance of PERFORMANCE ACCEPTANCE TEST (PAT) Units: The government shall formally accept by completion of form DD-250, the six PAT units after all testing is successfully completed. Acceptance of the PAT units shall be at Destination in accordance with the contract line items (CLINS).

3.3.1.7 Project Management Reviews (PMR)

Project Management Reviews shall be conducted between the contractor and the government as part of each SETR review. Also, at least one PMR shall be conducted between each SETR review, ideally concurrent with a Technical Interchange Meeting (these interim meetings shall be conducted via telephone conference, video teleconference or WEB meeting). The purpose of the PMR is to ensure management oversight and control of all aspects of the WIFT development and production program. Each PMR shall have a prepared agenda and is passed when the government approves the PMR minutes. The contractor shall ensure that adequate personnel are available to support the PMR. Subcontractors may also attend / participate as required. The PMR shall focus on the continuous review and assessment of particular CDRL deliverables including the:

A) Program Management Plan (CDRL A004) & Integrated Program Schedule (CDRL A005) B) System Engineering Plan & Design Engineering Plan (SEP & DEP) (CDRL A006) C) Test & Evaluation Master Plan (TEMP – To include Acceptance Test Plan) (CDRL A007) D) Program Risk Management Plan (CDRL A008)

3.3.1.8 Technical Interchange Meeting (TIM)

Technical Interchange Meetings shall be conducted between the contractor and the government, at least once between each SETR at a minimum, and whenever a test event, technical problem, decision point or requirement for a technical briefing arises between the contractor and the government regarding the WIFT development and production program. TIMs shall be conducted via telephone conference, video teleconference or WEB meeting. Agendas and minutes (to be approved by the government) are required for each TIM. TIM discussions shall cover any technical topic related to the WIFT development and production program. The contractor shall ensure that their required personnel are in attendance to participate in the TIM proceedings and to make technical decisions.

3.3.1.9 Production Readiness Review (PRR)

The PRR is the final SETR review of the WIFT development. The purpose of the PRR is to review and assess the WIFT test reports, in relation to WIFT specification performance requirements, to ensure that the WIFT meets or exceeds all those requirements. This shall also include an assessment of the suitability of the WIFT for use in the military aviation environment. The PRR is planned for a three day meeting duration.

3.3.1.9.1 PRR Entry Criteria

A) Completion of all test events called out in the Test & Evaluation Master Plan B) Generation and approval of test reports for all test events called out in the Test & Evaluation Master Plan C) Development and submittal to the government of any contractor recommended Design Change Notices (optional) D) Completion of all contractor action items with due dates prior to PRR E) Compilation of all deficiency reports generated during the WIFT testing along with the status of actions to resolve the reported deficiencies F) Program and engineering CDRL items with due dates prior to PRR have been delivered, including:

a) Meeting Agenda (CDRL A001)

b) SETR PowerPoint Presentation for TRR (CDRL A003)

c) Program Management Plan (CDRL A004) & Integrated Master Schedule CDRL A005)

d) Program Risk Management Plan (CDRL A006)

e) System Hardware Product Drawings (CDRL C001)

f) System Software Design Detailed Description (CDRL C003)

g) Reliability and Maintainability Analysis (CDRL A015)

h) Test Reports (CDRL A017)

i) Design Change Notices DCN (CDRL A018)

j) Request for Variance (CDRL A020)

k) NAVAIR Cyber Security Implementation Plan (CDRL A016)

l) Diminishing Manufacturing Sources and Material Shortages Plan (CDRL A022)

m) WIFT Operation and Maintenance Source Data (CDRL L002)

3.3.1.9.2 PRR Proceedings

A) Review each distinct test event performed, including deficiency reports and corrective actions taken, and declare the event passed of failed B) Review, and approve or disapprove, all Design Change Notices, Request for Deviation and Request for Waiver C) Account for and develop a plan to reclaim all government furnished equipment utilized during WIFT testing D) Assess the risk associated with going forward with WIFT production E) Review the planned WIFT production schedule F) Approve or disapprove the decision to enter into WIFT production G) Develop project plans and update the Integrated Master Schedule for WIFT Production; include any plans to incorporate design changes, deviations or waivers H) If the decision to enter into WIFT production is disapproved, discuss (and possibly develop) plans to correct deficiencies to allow approval of the WIFT production decision

3.3.1.9.3 PRR Exit Criteria

A) The decision to enter into WIFT production is approved or disapproved B) If the WIFT production decision is disapproved, the decision is made to either 1) end the WIFT project or; 2) undertake actions to correct deficiencies in order to approve the WIFT production decision C) PRR minutes are prepared by the contractor and approved (and possibly amended) by the government D) Communication of the PRR WIFT production decision (either to go forward with WIFT production or to not go forward) to the Contracting Officer for further action

2. Duplication of Data Data previously developed by or available to the contractor shall be used whenever possible to satisfy the requirements of this SOW or the SPS. The contractor shall identify to the Government all redundant data requirements within this SOW and combine any documents, drawings, and databases as is appropriate and cost effective.

3.3.3. – Engineering Data

3.3.3.1. Meeting Agenda and Meeting Minutes (CDRLs A001 and A002) The contractor shall prepare and submit to the government meeting agendas prior to all major program meetings and meeting minutes after all such meetings in accordance with the CDRL and this SOW.

3.3.3.2. SETR Review PowerPoint Presentation (CDRL A003)

The contractor shall develop, submit and present to the government SETR & ILS PowerPoint Presentations in accordance with the CDRL. This CDRL shall be submitted for the following SETR and ILS reviews: Post Award Review, PDR, CDR; TRR, PRR. Tailored PowerPoint Presentations shall be prepared for special PMRs and TIMs if required. The CDRL shall be utilized during each SETR to guide discussions and proceedings. The CDRL shall address every topic necessary to the contractor to “pass” the SETR. The purpose of the CDRL is to facilitate effective communication, between the contractor and the government, of the technical concepts, approaches, problems and solutions, the scientific and engineering principles, and the management prerogatives, problem areas and solutions, that must be addressed to successfully perform the contractual WIFT development and production effort. The CDRL shall contain detailed and summary information, as appropriate, for each topic discussed at each review. Slides containing proprietary information shall be prominently identified. The government shall have the right to utilize any slides, that do not contain contractor proprietary information, in other WIFT project related briefings and documents.

3.3.3.3. Program Management Plan (PMP) (CDRL A004) & Integrated Master Schedule (IMS) (CDRL A005) The PMP&IMS shall be the contractors consolidated plan of action and milestones for the successful accomplishment of the WIFT engineering development, production and ILS effort The contractor shall develop an event based Program Management Plan (CDRL A004). The PMP shall be expanded to a time-based Integrated Master Schedule (CDRL A005) to produce a networked and multi-layered schedule showing all detailed tasks required to accomplish the work effort. The PMP and IMP shall be a living document, within the limits of the contract, and shall be briefed at each major SETR. The “Plan” portion of the PMP&IMS shall consist of the project Integrated Master Schedule consisting of the work breakdown structure (WBS), schedule and task relationships (a priori and post a priori relationships). This plan shall be approved by the government at the post award review and shall be the contractor – government agreed upon plan of action and milestones for the remainder of the project. The “Report” portion of the PMP shall be the reports presented by the contractor, to the government, at each SETR, reporting The contractor’s progress in accomplishing the PMP tasks, reporting and expounding explanations for delayed tasks, reporting the tasks that are to be worked during the next (future) reporting period and reporting management problem areas with recommendations for resolution. The PMP&IMS shall be a project management tool and shall be included as a section in each SETR PowerPoint Presentation.

3.3.3.4 System Engineering & Design Engineering Plan (SEDEP) (CDRL A006) The contractor shall develop a Systems Engineering and Design Engineering Plan in accordance with the CDRL. The SEDEP shall be developed to meet the requirements of the contract, contract Statement of Work and the Systems Performance Specification (SPS). The SEDEP shall be the contractor’s detailed technical plan and approach to develop, through disciplined scientific, systems engineering and design engineering processes, a physical configuration item to meet or exceed the performance requirements detailed in the WIFT SPS. The initial SEDEP shall be presented to the government for approval at the Post Award Review (PAR). Any changes to the SEDEP after the PAR must be mutually agreed upon by the government and the contractor. The SEDEP shall trace design requirements to engineering tasks, WIFT components and subsystems. This shall include the performance requirements, allocated and functional baseline designs and the engineering design analysis to develop the end article components and sub systems. Note that the Requirements Traceability Matrix (CDRL C004) shall also be a product of this effort. The SEDEP shall also address hazardous materials (HAZMAT) utilization, minimization and management plan.

3.3.3.5 Test & Evaluation Master Plan (TEMP – To include Acceptance Test Plan) (CDRL A007) The contractor shall develop a Test and Evaluation Master Plan in accordance with the CDRL. The TEMP shall be developed utilizing the System Performance Specification and shall detail all of the testing and inspections that will be employed to qualify, verify and validate the WIFT end article design and performance through each phase of engineering development. The TEMP shall comprehensively detail the following testing for the WIFT: 1) Development Testing (DT) including critical component testing and subsystem testing; 2) Performance Acceptance Test Units (and Physical Configuration Audit – PCA); 3) Technical and Suitability evaluation (TECHEVAL / SUITEVAL); 4) Production Unit Acceptance Testing. The initial TEMP shall be presented to the government for approval at the PDR. Any changes to the TEMP after the PDR must be mutually agreed upon by the government and the contractor. The TEMP shall contain required entry criteria for each testing event. The TEMP shall also contain the pass / fail criteria for each test. The TEMP shall trace each test event and pass / fail criterion to a performance specification requirement in the SPS and shall also ensure that every performance requirement called out in the SPS is verified and validated through testing, inspection or certification. The TEMP shall include verification and validation of the Instrument Calibration Procedures for the WIFT. The TEMP shall not include verification and validation of technical publications and training documentation, this shall be included as part of the WIFT ILS development program. The TEMP shall address component and/or subsystem level testing for which the government may require test reports.

3.3.3.6 Program Risk Management Plan (CDRL A008)

The contractor shall develop and maintain a Program Risk Management Plan (RMP) in accordance with the CDRL. The contractor shall utilize the RMP to identify, manage, and mitigate all schedule and technical risks associated with the WIFT contractual development effort. All risks shall be identified and evaluated for probability of occurrence and severity of consequences. The RMP shall establish a plan of action to eliminate, mitigate or manage the program risk. All risk identified shall be traced to a requirement in the SPS or to a clause in the Statement of Work (SOW) or contract. The RMP shall establish and maintain an overall risk assessment for the entire WIFT development project, and for the major subtasks associated with the project, using the RED-YELLOW-GREEN standard systems engineering convention. The initial RMP shall be presented to the government at the Post Award Review. The RMP shall be a living document and shall be presented for discussion at each SETR.

3.3.3.7 System Design Theory & Concept of Operation Report (DTCO) (CDRL A009) The contractor shall develop and maintain a System Design Theory & Concept of Operation Report in accordance with the CDRL. This report shall be the authoritative synopsis describing the WIFT operational requirement, concept of operation, concept of employment, enabling technologies, system design and end article operation. This report shall be the primary document used by the WIFT development government-contractor team to communicate all aspects the WIFT program to individuals and organizations outside of the WIFT development team including future fleet users, other project and platform program offices, other US and allied military services, Naval Air System Command, HQ Marine Corps, Commander Naval Air Forces and USAF Special Operations Command. This report shall also serve as a quick reference for technical and management personnel that are a part of the WIFT development government-contractor team. This report shall be published as a PowerPoint presentation and as a narrative document. The initial System Design Theory & Concept of Operation Report shall be presented to the government at the Preliminary Design Review. Any changes to this report shall be presented for discussion at SETR reviews.

3.3.3.8 Human – System Interface Design Report (CDRL A010)

The contractor shall develop a Human – System Interface Design Report (H-SIDR) in accordance with the CDRL. The H-SIDR shall be utilized to identify, specify and design the detailed WIFT Human-System interface. The H-SIDR shall detail WIFT handling requirements and design (i.e. size, weight, handles, hand-holds, carrying straps, provisions to lay the WIFT on various surfaces, etc.), WIFT Input-Output screen requirements and design (i.e. screen size, brightness, contrast and image quality, Sun readability, touch screen, input stylus (yes/no), output information format (graphical, digital, combination), ergonomics, etc.), Manual input and keypad provision requirements and design (Functions included, use wearing cold weather or NBC (Nuclear, Biological, Chemical) gloves / gear, indicator lights, NVG (night vision goggle) readability (yes/no), etc.). The initial H-SIDR shall be submitted at PDR.

3.3.3.9 System Software Development Plan (A011)

The contractor shall develop a System Software Development Plan (SSDP) in accordance with the CDRL. The SSDP shall detail the technical tasks, schedule and milestones related to the development of the software (SW) for the WIFT. The SSDP shall describe the major software development project type such as Total SW Development; Modify COTS (Commercial Off-The Shelf) software; Integrate Existing COTS SW with WIFT Hardware (HDW); Integrate Multiple Existing SW Packages into a single functioning SW Package; etc. The contractor shall then develop an appropriate Work Breakdown Structure (WBS), schedule and milestones based on the WIFT SW development project type, contract, SOW and System Performance Specification requirements. The SSDP shall be utilized throughout the design phase of the WIFT development project (PDR & CDR).

3.3.3.10. Failure Modes, Effects and Criticality Analysis (FMECA) (CDRL A012) The contractor shall develop a FMECA in accordance with the CDRL as follows:

- Develop a FMECA based on the functional block diagram of the WIFT design. Also perform a criticality analysis identifying WIFT failure modes that create a hazard to personnel or to the aircraft component being tested. Present this FMECA at the PDR.

- Further refine and expand the functional Failure Modes and Effects Analysis (FMEA) to include the actual components utilized in the WIFT design. Also, in like manner, refine and expand the criticality analysis based on the actual WIFT components. Present this FMECA at the CDR.

Note that the FMECA shall also be utilized by the contractor in the reliability and maintainability analysis. Cancelled MIL-STD-1629A shall be consulted for guidance purposes regarding the procedures and document formats for the FMECA.

3.3.3.11 Calibration Measurement Requirements Summary (CDRL A013) The Contractor shall prepare a CMRS, in accordance with the CDRL, which identifies the system calibration and measurement requirements, the measuring and test equipment, calibration equipment, and calibration standards required to maintain a proper calibration system for the WIFT. The CMRS shall be developed using MIL-STD-1839D and DI-QCIC-80278A as guidance. The purpose of the CMRS is to establish the requirements baseline from which calibration procedures for the WIFT shall be developed.