Amendment_0002_-_N00024-14-R-5210.pdf

N0002413NR5210

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of Amendment 0002 to solicitation N00024-14-R-5210 is to update Sections C (including paragraph 3.2.7.3), H, L, and RFP Attachments 11 and 13.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 40

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 01-Aug-2014

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00024-14-R-5210

X 9B. DATED (SEE ITEM 11)

29-Apr-2014

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

01-Aug-2014

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2040

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00024-14-R-5210

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 08-Aug-2014 03:00 PM to 22-Aug-2014 11:00 AM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

SECTION C

C-1 DELIVERABLES:

CLINs 0001-0004 and 0009-0020, 1001-1004 and 1009-1020, 2001-2004 and 2009-2020, 3001-3004 and 3009- 3020, 4001-4004 and 4009-4020 – The Contractor shall manufacture, test and deliver the Common Display System, including Configuration Options. The CDS Variants, configurations and configuration options shall be identified in each Delivery Order.

CLINs 0005, 0007, 1005, 1007, 2005, 2007, 3005, 3007, 4005 and 4007 – The Contractor shall manufacture, integrate, test, and deliver CLINs 0005, 0007, 1005, 1007, 2005, 2007, 3005, 3007, 4005, and 4007 installed in CLINs 0006, 0008, 1008, 1008, 2006, 2008, 3006, 3008, 4006 and 4008. The supplies or services shall be identified in each Delivery Order.

CLINs 0006, 0008, 1006, 1008, 2006, 2008, 3006, 3008, 4006, and 4008 – The Data Processing Cabinet and ACE Remote CEM (CLINs 0006, 0008, 1006, 1008, 2006, 2008, 3006, 3008, 4006, and 4008) shall be populated with the respective Remote CEM Kits (CLINS 0005, 0007, 0026, 0027, 1005, 1007, 1026, 1027, 2005, 2007, 2026, 2027, 3005, 3007, 3026, 3027, 4005, 4007, 4026, and 4027) prior to Government acceptance testing. The configuration of CLINs 0006, 0008, 1006, 1008, 2006, 2008, 3006, 3008, 4006, and 4008 shall be specified in the Delivery Order.

CLINs 0021 – The Contractor shall test and deliver new or repaired spare parts. The spares shall be identified in each Delivery Order.

CLINs 0022, 1022, 2022, 3022, 4022, 0023, 1023, 2023, 3023, and 4023 – The Contractor shall provide the necessary labor, incidental materials and other direct costs to support the engineering studies. The specific tasks shall be defined in each Delivery Order.

CLINs 0024AA, 0025AA, 00026AA, 0027AA, 1024AA, 1025AA, 1026AA, 1027AA, 2024AA, 2025AA, 2026AA, 2027AA, 3024AA, 3025AA, 3026AA, 3027AA, 4024AA, 4025AA, 4026AA, and 4027AA – The Contractor shall provide the equipment necessary for incorporation in to the above SLINs. The Government will not be providing the equipment as called out in Section H, 5252.245-9109 GOVERNMENT-FURNISHED PROPERTY.

CLINs 0024AB, 0025AB, 00026AB, 0027AB, 1024AB, 1025AB, 1026AB, 1027AB, 2024AB, 2025AB, 2026AB, 2027AB, 3024AB, 3025AB, 3026AB, 3027AB, 4024AB, 4025AB, 4026AB, and 4027AB – The Contractor shall include material for CEM (v)3.0 in lieu of CEM (v) 2.1 on the above SLINs. Refer to Section B, Notes Q and R, as applicable.

CLIN 5001 – Orders shall be placed in accordance with Section C-2, Paragraph 3.14 PROVISIONED ITEMS ORDERS. The supplies or services shall be identified in each Delivery Order.

CLIN 5002 – The Contractor shall manufacture, test, and deliver the Acceptance Test Equipment in accordance with Document Number 1010526 of the Technical Data Package. The test set shall include all necessary cabling, connectors and ancillary required to perform PAT testing of the Console Only CDS configurations. The supplies or services shall be identified in each Delivery Order.

CLINs 6001-6004 – The Contractor shall support first article requirements as defined in Section C-2 of this Statement of Work. The supplies or services shall be identified in each Delivery Order.

C-2 STATEMENT OF WORK:

This Statement of Work (SOW) defines the efforts required for the fabrication, assembly and test of the Common Display System (CDS) Family of Display Consoles. The Contractor shall manufacture CDS Equipment (Variant A and B consoles both with and without Common Electronics Modules (CEM), Remote CEM (Display Processor Cabinets both with MCE and ACE versions, and Display Converter Units) in accordance with the relevant Technical Data Packages (TDPs). The Contractor’s facilities must be cleared at the secret level in accordance with the attached DD 254 (Attachment 1).

1.0 BACKGROUND

CDS is a family of common display systems, compliant with Open Architecture Computing Environment (OACE) requirements and implementing Human Systems Integration (HSI) design principals. As defined herein, CDS includes the Variant A and B consoles, both with and without CEM, Display Processor Cabinets both with MCE and ACE versions, and Display Converter Units (CDUs). CDS will be integrated across multiple platforms on Navy surface ships, submarines, and aircraft, and shall be designed using commercially available hardware and software wherever possible. Through its multi-mission functionality design, CDS will allow operators access to its mission applications at any platform Display Console. CDS supports the following program objectives:

Integrated platform mission critical and mission essential Display Console system requirements.

Navy Open Architecture (OA) compliance to enable integration into a platform OACE infrastructure.

Incorporation of HSI concepts required to optimize human performance and support the Navy’s manpower reduction initiatives.

Operator access to multiple applications on any Display Console.

Modular Open Systems Approach (MOSA) to support efficient technology insertion and refresh.

2.0 APPLICABLE DOCUMENTS

The following documents, of the exact issue shown, form a part of the SOW to the extent specified herein. In the event of a conflict between the documents referenced herein and the contents of this SOW, the contents of this SOW shall be considered a superseding requirement.

2.1 Government Documents

1010201 (CLINs 0001, 1001, 2001, 3001, and 4001)

Technical Data Package (TDP) for the Variant A Display Console with Common Electronics Module (CEM), dated 25 April 2013 and Variant A TDP delta disk dated 16 June 2014

1010203 (CLINs 0002, 1002, 2002, 3002, and 4002)

Technical Data Package (TDP) for the Variant A Console Only of the Common Display System (CDS), dated 14 September 2012

1010211 (CLINs 0003, 1003, 2003, 3003, and 4003)

Technical Data Package (TDP) for the Variant B Common Electronics Module (CEM), dated 31 July 2013

13253000 (CLINs 0004, 1004, 2004, 3004, and 4004)

Technical Data Package (TDP) for the Variant B Console, dated 31 July 2013 and Variant B TDP delta disk dated 16 June 2014

13253494 Technical Data Package (TDP) for the Variant B Display Console without Common Electronics Module (CEM), dated 31 July 2013

ARC-14-0001 (CLINs 0007, 1007, 2007, 3007, and 4007)

Advanced COTS Enclosure (ACE) Remote Commons Electronics Module (CEM) (ARC) Technical Data Package (TDP), dated 15 January 2014 and ACE RCEM TDP delta disk dated 13 June 2014

CDS-13-0034 (CLINs 0005, 1005, 2005, 3005, and 4005)

Common Display System (CDS) Remote Common Electronics Module (CEM) Technical Data Package (TDP), dated 04 October 2013

CID 3063350 Common Display System (CDS) Remote Common Electronics Module (CEM) Marking Plans (MPs), dated 04 October 2013 and RCEM TDP delta disk dated 16 June 2014

CID 3063352 Marking Plan (MP) for the Computer Group, Tactical OL-794/U, Rev 7, dated 15 January 2014

CID 3064149 Draft Marking Plan for the Converter, Digital to Digital CV-4443/U, dated 04 October 2013

4000232 System Safety Program Plan (SSPP) for the Common Display System (CDS) Family of Display Consoles, dated 31 August 2010

4000231 Environmental Health and Safety Plan (EHSP) for the Common Display System (CDS) Family of Display Consoles, dated 04 November 2011

4000246 System Safety Hazard Assessment (SSHA) Report for the Common Display System (CDS) Family of Display Consoles, Rev D, dated 24 April 2012

400260 Deliverable Marking Plan (DMP) For The Common Display System (CDS) Family of Display Consoles, dated 27 September 2012

PRF-CEDS-2005 System Requirements Document for the Common Display System (CDS), Rev E, dated 24 June 2011

PEO IWS Instruction 3058.1, Risk Management Plan, Rev 3.0 dated 2 August 2004 PEO IWS Program Plan Diminishing Manufacturing Sources and Material Shortages (DMSMS) Plan, dated June 2005 PEO IWS Program Plan Configuration Management Plan for PEO IWS, dated 21 July 2004 CDS SW File Descriptions Version 1.0.3.2, dated 27 October 2012 CDS Image Loader v1.0.3.4 CDS HCV FibCop v1.0.3.4 CDS HCV CopFib v1.0.3.4

2.2 Military Standards (MIL-STD)

MIL-STD-129P DoD Standard Practice, Military marking for Shipment and Storage, 19

September 2007 MIL-STD 130N Department of Defense Standard Practice Identification Marking of U.S.

Military Property, 15 June 2007 MIL-STD-2073-1E DoD Standard Practice for Military Packing, 7 January 2011

2.3 Joint Chiefs of Staff, Department of Defense and DoD Services Documents

Defense Acquisition Guidebook 4.3.3.4.7, https://dag.dau.mil

Production Readiness Reviews (PRR)

DoD 5220.22M Defense Security Service (DSS) National Industrial Security Program Operating manual (NISPOM), 28 February 2006

OPNAVINST 1500-76B Naval Training Systems Requirements, Acquisition, and Management DoDI 1322.26 Development, Management, and Delivery of Distributed Learning MIL-PRF-29612B Performance Specification Training Data Products NAVEDTRA 130A Task Based Curriculum Development Manual NAVEDTRA 131A Personnel Performance Profile Based Curriculum Development Manual

2.4 Handbooks

MIL-HDBK 61A Configuration Management Guidance, 7 February 2001

2.5 Non-Government and Commercial Standards, Specifications and other applicable publications

ANSI/ASQC Q9001-2008 Quality Systems - Model for Quality Assurance in Design, Development, Production, Installation and Servicing

3.0 REQUIREMENTS

3.1 GENERAL. Program information, deliveries and data shall be handled in accordance with the Contract Security Specification, DD Form 254, Attachment 1 of the Contract.

3.2 PROGRAM MANAGEMENT AND CONTROL (Applicable to all CLINs). The Contractor shall provide program management oversight to ensure all work conducted within this contract is planned and executed in a manner that will achieve all management, technical, logistics, budget and schedule objectives. The Contractor shall establish these objectives for every facet of the production, and post-production/delivery support tasks under the contract. The Contractor shall ensure coordination and integration of all production functional areas. The Contractor shall establish and perform business management functions to ensure contracting related actions, such as development and submission of proposals, negotiation of proposals, responses to requests for cost estimates and production orders meet established need dates of the Government.

3.2.1 Program Management Office. The Contractor shall establish a Program Management Office that is responsible for the management and control of the Program Management Plan (CDRL A001) elements in order to support the successful on-time delivery of the contract requirements. The Program Management Plan shall incorporate detailed production planning, milestones and metrics capable of supporting the execution of all tasks required by the contract and this SOW.

Deliverable Data Item (See DD-1423):

CDRL A001: “Program Management Plan”

The Contractor shall develop an Integrated Program Management Report (CDRL A002) by logically networking detailed program activities including and not limited to: Fabrication and Assembly Schedule, Testing Schedule, planned events and milestones, accomplishments, and activities from contract award to the completion of Production Readiness Review. The report shall consist of an Integrated Master Schedule (IMS) that includes the efforts of all activities, including Contractor or supplier and subcontractor and present a current, integrated view of the contract or agreement that is consistent with resource plans and other approved documentation. The IMS shall include all major reviews, (e.g., management and program reviews), technical and working group meetings, test events, ILS meetings, verifications, audits, and program data deliverables. Furthermore, the IMS shall reflect those risks identified and documented in the Contractor’s Risk Management Plan. The Contractor shall notify the Government in writing within 24 hours of any anticipated or projected work stoppages or delays that will impact schedules. The IMS shall be consistent with the Contract Work Breakdown Structure (CDRL A003) and must be detailed sufficiently that critical and high-risk efforts are identified and planned realistically to assure execution of program requirements.

Deliverable Data Item (See DD-1423):

CDRL A002: “Integrated Program Management Report” CDRL A003: “Contract Work Breakdown Structure”

3.2.2 Program Manager. The Contractor shall designate a Program Manager who shall ensure all work conducted within this contract is planned and executed in a manner that will achieve all management, technical, logistics, budget and schedule objectives.

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

3.2.4 Monthly Progress, Status and Management Reports. The Contractor shall deliver a monthly Contractor’s Progress, Status and Management Report (CDRL A004). CDRL requirements shall include:

Status of significant program events (e.g. Post Award Conference, Interchange Meetings, Program Reviews);

Status of significant/major production, test, and logistics efforts and/or issue resolution;

Program management metrics;

Risk assessment;

Environmental Safety and Occupational Health (ESOH) hazard status;

Schedules for individual tasks and delivery orders Tracking Report for equipment production/deliveries;

Configuration Status Accounting (CSA) database activities;

Action item status;

Invoices submitted to Wide Area Work Flow (WAWF).

Deliverable Data Item (See DD-1423):

CDRL A004: “Contractor’s Progress, Status and Management Report”

3.2.5 Meetings. The Contractor shall coordinate, schedule, prepare, conduct, facilitate and participate in reviews, meetings and conferences as specified herein. The Government reserves the right to attend meetings between the prime and subcontractors on a non-interference basis. The Contractor shall provide the Government notice of any meeting in writing fourteen (14) days in advance, or as soon as is reasonably possible. The Contractor shall provide Conference Agenda (CDRL A005), Presentation Material (CDRL A006), and Conference Minutes (CDRL A007) for each meeting. At a minimum, the Contractor shall support meetings identified within the following paragraphs.

Teleconferencing shall be used whenever possible, otherwise meetings shall be held at the Contractor’s facility.

Deliverable Data Item (See DD-1423):

CDRL A005: “Conference Agenda” CDRL A006: “Presentation Material” CDRL A007: “Conference Minutes”

3.2.5.1 Monthly Program Management Reviews (PMR). Monthly PMRs shall be conducted in person or via teleconferencing with the Contractor providing a summary of its current program status to include their Contractor’s Progress, Status and Management Report (CDRL A004). The current program status report shall contain the following main sections: Summary, Accomplishments, Current Status, Problem Areas, Risks and Mitigation, Cost and Schedule Data, and Future Plans. The reporting period shall be for the duration of the contract.

3.2.5.2 Quarterly Program Reviews. The Contractor shall conduct quarterly program reviews, beginning four (4) months after award of contract, to assess the Contractor’s progress and status. Quarterly program reviews will be conducted at the Contractor's facility. The Contractor shall provide, at a minimum, an overview of production status, review of program DMSMS status, including disclosure of any and all known DMSMS items, the planned action to mitigate its engineering and Integrated Logistic Support (ILS) impacts, and a report on the small business utilization. The status of the Contractor’s efforts to achieve the requirements set forth in the contract will be emphasized. Vendor/subcontractor status and problems shall also be addressed; as such, vendors/subcontractors may support the review as required. In addition, a separate review may be conducted to cover a special set of circumstances or troublesome area(s), but the reviews shall be considered part of and conducted with the quarterly production review. An Action Item List shall be prepared and maintained by the Contractor during the life of this contract to enable tracing the closure of generated action items.

3.2.5.3 Integrated Product Teams (IPTs) and Working Groups. The Contractor shall plan to participate in and support at least one (1) quarterly IPT or working group to ensure integrated and coordinated work across all elements of the CDS program.

3.2.5.4 Post Award Kickoff Meeting. The Contractor shall provide a detailed briefing on its management and contract execution strategy at the Post Award Kickoff Meeting to be held within 30 days after contract award at the Contractor’s facility. The Contractor shall plan for a one day Post Award Kickoff Meeting.

3.2.6 Data Management. The Contractor shall post contract data and applicable deliverables to a Government specified website, unless otherwise specified on the applicable CDRL DD Form 1423-1. The Contractor shall provide electronic-mail (e-mail) notification to the Contracting Officer's Representative (COR) and other Government personnel identified on the CDRL Addressee List within 24 hours of CDRL delivery (posting new/revised information and CDRL deliverable(s) on the website (VIEWNET) or delivering as specified on the associated CDRL DD Form 1423-1).

3.2.7 Program Security. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. Contractor must be able to handle and store classified material up to the SECRET Level.

3.2.7.1 International Traffic in Arms Regulations (ITAR). The Contractor shall be solely responsible for obtaining any State Department approvals, licenses, Technical Assistance Agreements (TAA), etc. required by the International Traffic in Arms Regulations. The Contractor shall notify the COR of all actions that require any approvals due to ITAR.

3.2.7.2 Contractor Security. The Contractor shall implement security procedures in concert with Defense Security Service (DSS) National Industrial Security Program Operating Manual (NISPOM) per DoD 5220.22M.

3.2.7.3 Security Clearance Levels. The Contractor shall possess a SECRET Facility Security Clearance in accordance with the NAVSEA Facility Security Clearance Clause (FEB 2012) in Section L of this solicitation.

3.2.7.4 Public Release of Information. All public releases of information concerning this project must receive written approval of the contracting officer two weeks prior to release.

3.2.7.5 Website Security. The Contractor shall ensure that its publicly-accessible web-sites are free of For Official Use Only (FOUO) or other sensitive information, and/or indicators that could tip-off adversaries about impeding program activity. The Government will provide additional Operational Security (OPSEC) guidance as necessary.

3.2.7.6 Contractor’s Internal Network and Data Security. The Contractor shall ensure that its internal networks and data have sufficient protection to prevent intrusion from sources outside its facilities.

3.3 FABRICATION AND ASSEMBLY. (Applicable to CLINs 0001-0021, 0024-0027, 1001-1021, 1024-1027, 2001-2021, 2024-2027, 3001-3021, 3024-3027, 4001-4021, 4024-4027). The Contractor shall build and deliver the CDS, including any configuration options ordered under CLINs 0009-0020, 1009-1020, 2009-2020, 3009-3020, and 4009-4020 in accordance with the Government provided Technical Data Package (TDP). Any changes to or deviations from the TDPs shall be submitted for approval via the Configuration Management process as described in paragraph 3.8 of this SOW.

The Contractor shall furnish all material, labor, and incidentals to accomplish the efforts required by the contract and this SOW, other than those provided by the Government as GFI and the GFP/GFE listed in Section H, 5252.245- 9109 GOVERNMENT-FURNISHED PROPERTY (INCORPORATION) and 5252.245-9115 RENT-FREE USE

OF GOVERNMENT PROPERTY.

The Data Processing Cabinet and ACE Remote CEM (CLINs 0006 and 0008) shall be populated with the respective Remote CEM Kits (CLINS 0005, 0007, 0026 and 0027) prior to Government acceptance testing. The configuration of CLINs 0006 and 0008 shall be specified in the Delivery Order. There are configurations that require integration and testing of Remote CEM kits (CLINs 0005, 0007, 0026 and 0027) from multiple orders into those cabinets prior to Government acceptance test. All costs for integrating and testing of Remote CEM and ACE Remote CEM kits into DPCs will be included CLINs 0005, 0007, 0026, 0027, 1005, 1007, 1026, 1027, 2005, 2007, 2026, 2027, 3005, 3007, 3026, 3027, 4005, 4007, 4026, and 4027.

3.3.1 TECHNICAL DATA PACKAGE (TDP). (Applicable to CLINs 0001-0020, 0024AB-0027AB, 1001-1020, 1024AB-1027AB, 2001-2020, 2024AB-2027AB, 3001-3020, 3024AB-3027AB, 4001-4020, and 4024AB-4027AB).

The Contractor shall maintain/update the TDP and deliver a quarterly TDP in accordance with CDRL B001. The TDP shall contain all data and information necessary to manufacture the CDS Equipment ( Display Consoles (Variants A and B), Remote CEM and ACE Remote CEM); including Proposed Critical Manufacturing Process Description (PCMPD) (CDRL B002) and Interface Control Documents (CDRL B003). The Contractor shall use Technical Interchange Meetings (TIM) to resolve ambiguities and deficiencies found in the TDPs. At the end of this contract, the Contractor shall deliver final versions of all the TDPs.

Deliverable Data Item (See DD-1423):

CDRL B001: “Technical Data Package” CDRL B002: “Proposed Critical Manufacturing Process Description” CDRL B003: “Interface Control Documents” CDRL B004: “Products Drawings/Models and Associated Lists” CDRL B005: “Commercial Drawings/Models and Associated Lists”

3.3.2 Production Acceptance Testing (Applicable to 0001-0005, 0007, 0024-0027, 1001-1001, 1007, 1024-1027, 2001-2005, 2007, 2024-2027, 3001-3005, 3007, 3024-3027, 4001-4005, 4007, 4024-4027 and 6001-6004).

Production Acceptance Test procedures (CDRL A008) shall be tailored and delivered using the Government provided Production Acceptance Test procedures as guidance. The Production Acceptance Test shall be conducted at the Contractor’s facility, utilizing Contractor and Government furnished test equipment in accordance with the Production Acceptance Test (PAT) procedures. The Contractor shall provide Test/Inspection Reports (CDRL A009) for all acceptance tests.

The Contractor shall conduct a System Burn-in Test (SBT) and PAT on each CDS configuration. The SBT and PAT for Remote CEM and ACE Remote CEM kits shall occur in the populated DPCs (0006, 0008, 1006, 1008, 2006, 2008, 3006, 3008, 4006, and 4008) All costs for testing of Remote CEM and ACE Remote CEM kits in DPCs shall be included CLINs 0005, 0007, 0026, 0027, 1005, 1007, 1026, 1027, 2005, 2007, 2026, 2027, 3005, 3007, 3026, 3027, 4005, 4007, 4026, and 4027. The SBT shall operate 72 hours error-free. PAT includes the functional, electrical, mechanical and visual tests performed to verify that the CDS equipment is operational. The Government reserves the right to witness Production Acceptance Test. The Contractor shall provide fourteen (14) calendar days’ notice prior to any test event.

In the event of a production test failure, the Test/Inspection Reports (CDRL A009) shall include the circumstances of the failure, identification of the CDS equipment under test, the testing step conducted when the failure occurred, physical observations, and meter readings (as applicable). The report shall include an analysis of the test failure and corrective measures to be taken to prevent further test failures.

Deliverable Data Item (See DD-1423):

CDRL A008: “Test Plan/Test Procedures: Production Acceptance Test Procedures” CDRL A009: “Test /Inspection Reports”

3.4 QUALITY ASSURANCE (Applicable to all Line Items). The Contractor shall adhere to a Quality Assurance (QA) system that, at a minimum, meets the requirements of ANSI/ASQ 9001-2008, and ensures that the products delivered meet the minimum functional and environmental requirement specified. The Contractor shall be responsible for performance of all quality requirements for the items delivered under this contract. The quality system shall include provisions conforming to all production requirements cited in this SOW including calibration, subcontractor control, failure diagnosis and corrective action, statistical process control, component and environmental screening, testing, and inspection. The Contractor shall provide and maintain a quality management system that, as a minimum, adheres to the requirements of ANSI/ISO/ASQ 9001-2008 Quality Management Systems and supplemental requirements imposed by this contract. The Contractor shall notify the Government of all production testing failures. The Contractor shall have established manufacturing processes that ensure all CDS equipment produced under this contract is delivered without defects. The Contractor shall screen material used for the production of CDS equipment in accordance with the Government Materials Screening Plan for the CDS Family of Display Consoles.

3.4.1 Quality Management Plan. The Contractor shall develop and update a Quality Management Plan (QMP) (CDRL A010) that includes a Quality Assurance Surveillance Plan (QASP). The QMP shall detail the processes, procedures, and metrics for assuring quality, such as; (1) Identification of roles, responsibilities and process owners,

(2) Implementation of an effective root cause analysis and corrective action process, (3) Continuous process improvement to reduce costs and timelines, (4) Incorporating Lessons Learned, After Action Reports and customer satisfaction surveys into process improvement, and (5) Documentation of all outstanding deficiencies related to all phases of design, fielding, and logistics support. The Contractor shall flow all quality system requirements down to all suppliers and subcontractors.

Deliverable Data Item (See DD-1423):

CDRL A010: “Quality Assurance Program Plan: Quality Management Plan”

3.4.2 Reliability, Maintainability, and Availability.

3.4.2.1 Reliability and Maintainability (R&M) Program. The Contractor shall provide the necessary personnel, equipment, supplies and services required to plan, implement, and maintain an R&M program for TI-12 Common Display System (CDS) Production.

The R&M characteristics of the CDS equipment, as defined in System Requirements Document, shall not be degraded during manufacturing and test.

3.4.2.2 Reliability and Maintainability Program Plan. The Contractor shall develop a Production R&M Program Plan that documents and details the processes and procedures utilized in the conduct and management of the Production R&M Program. The plan shall be updated annually or as conditions warrant. The Common Display System (CDS) Reliability and Maintainability( R&M) Program Plan shall be approved by the Government. (CDRL A011).

Deliverable Data Item (See DD-1423):

CDRL A011: “Common Display System (CDS) Reliability and Maintainability (R&M) Program Plan”

3.4.2.3 Failure Reporting, Analysis, and Corrective Action System (FRACAS). The Contractor shall track R&M of the CDS equipment, investigate trends and develop corrective action for the CDS equipment, as follows:

The Contractor shall conduct an internal failure review board as defined in the approved Production R&M Program Plan to review all production and test failure data collected under the Contractor's FRACAS program. All failure data shall be analyzed to identify failure trends. A failure trend for production failures is two or more failures of the same LRU in one cabinet (free standing unit) or two or more failures of the same LRU in the last four cabinets (free standing units) built, or as dictated in the latest approved CDS Production R&M Program Plan (criteria in program plan shall take precedence). All failure trends shall be investigated using best commercial practices until the failure mechanism has been satisfactorily identified and corrective action implemented to preclude recurrence of the failures. When corrective action results in the development of an ECP, the total impact of the ECP on R&M shall be assessed and documented in the ECP submitted to the Government.

FRACAS shall include all field failure data including data from land based test sites, production test centers, shipboard integration and testing prior to deployment and deployed system data (3M/PBL). All data shall be analyzed to identify field failure trends:

a. For insufficient data to establish confident Mean Time Between Failure (MTBF) values, a trend shall be identified whenever two or more of the same LRU has failed in one cabinet (free standing unit) or two or more failures of the same LRU in the last four cabinets (free standing units) at that site .

b. LRUs whose actual reliability is less than 90% of that initially predicted/ allocated shall be identified, assessed for impact, and reported to the Reliability and Maintainability Working Group (RMWG).

c. LRUs whose actual reliability is less than 80% of that initially predicted/ allocated shall be identified and assessed for impact. The Contractor shall recommend options to resolve these reliability issues. When developing recommendations the Contractor shall evaluate working with the LRU OEM to identify the root cause(s) of the LRU failure and redesigning the LRU to improve reliability.

The Contractor shall assess the effectiveness of corrective actions per the procedure contained in the Production R&M Plan.

The Contractor shall provide a Failure Summary and Analysis Report (CDRL A012) to document the failure mechanism (root cause) and corrective action of each failure trend identified. The Contractor shall maintain problem descriptions, investigations and corrective actions on each problem to reference and recall for same or similar problems that may recur in the future.

A Corrective Action Summary Report (CDRL A013) shall be provided biannually summarizing all failures, failure trends, corrective actions, and effectiveness of corrective actions.

CDRL A012: “Failure Summary and Analysis Report” CDRL A013: “Technical Report-Study /Services: Corrective Action Summary”

3.4.2.4 Meetings. The Contractor shall conduct, participate in and prepare for R&M program reviews on an annual basis. The agenda shall be provided five calendar days in advance of each review to provide adequate coverage of topics and participant preparation . Contractor R&M personnel shall also support all formal and informal meetings, program reviews, design reviews, integrated products teams, working groups, technical interface meetings and other meetings to the extent necessary to conduct the R&M program in accordance with the contractual milestones and R&M requirements. The Contractor shall participate, as required, in a Government R&M Working Group

(RMWG).

3.5 RISK ASSESSMENT AND MANAGEMENT. The Contractor shall establish and maintain a Contractor’s Risk Management Plan (CDRL A014) in accordance with the principles and processes of PEO IWS Risk Management Plan, to include risk identification, risk assessment, risk ranking, risk trends, risk mitigation and risk monitoring.

Risk metrics shall be generated in accordance with PEO IWS Instruction 3058.1, Risk Management, and reported as part of the Contractor’s Progress, Status and Management Report (CDRL A004) and during program reviews. The Contractor’s risk report shall include, as a minimum, the following:

• Identification of the risk areas;

• Assessment of identified risks, including a relative ranking by program impact;

• Definition of methods or alternatives to mitigate each risk, including the identification of criteria upon; which to base programmatic decisions;

• Human, hardware, and software performance;

• Analysis and tradeoffs impacted/considered during risk analysis;

• Status of resolving/mitigating identified risks.

CDRL A014: “Contractor’s Risk Management Plan”

3.6 MANAGEMENT AND ACCOUNTABILITY FOR GOVERNMENT FURNISHED MATERIAL (GFM) . The Contractor shall deliver a plan for the management and accountability of all GFM, GFP, and GFI as part of the

Program Management Plan (CDRL A001). The plan shall ensure that items and information furnished by the Government are properly managed and accounted for.

3.7 END OF CONTRACT TRANSITION PLANNING The Contractor shall develop an End of Contract Transition Plan (CDRL A015) that addresses the long-term support requirements of all CDS equipment procured under this contract, as support agent responsibility transitions from the Contractor. This plan shall describe how the Contractor would transition the follow-on support of CDS equipment to a third party. The plan shall identify all hardware and software (including firmware) information and equipment required to support CDS equipment. The transition plans shall address the turnover of all CDS databases (e.g. Environmental Safety and Occupational Health (ESOH) database and test hardware. Additionally, the end of contract transition plan shall address the supply support topics specified in this SOW.

CDRL A015: “Technical Report-Study/Services: End of Contract Transition Plan”

3.8 CONFIGURATION MANAGEMENT (CM) The Contractor shall establish and implement a CM Program based on NAVSEAINST 4130.12B Configuration Management Policy and Guidance and MIL-HDBK-61B. The Contractor’s CM efforts shall include configuration identification, configuration change control, hardware and software CSA, configuration verification and audits, and configuration data management. The Contractor shall establish a CM process capable of processing required configuration changes in a time frame that enables identification, evaluation, and implementation of proposed changes without impact to production schedules. The Contractor shall develop a CM Plan and deliver it to the Government for review and approval. (CDRL A016)

The Contractor shall control the configuration of the configuration baseline documentation until submitted to, and approved by, the Government. Configuration documentation baselines are established at the time of Government approval; subsequent changes shall be processed in accordance with this SOW and the associated CDRLs.

Deliverable Data Item (See DD-1423):

CDRL A016: “Contractor’s Configuration Management Plan”

3.8.1 Configuration Identification. The Contractor shall establish a configuration identification process that includes:

a. Selecting Configuration Items (CI) at appropriate levels of the product structure to facilitate the documentation, control and support of the items and their documentation;

b. Determining the types of configuration documentation required for each CI to define its performance, functional and physical attributes, including internal and external interfaces. Configuration documentation shall include the documentation the Contractor uses to develop and procure software/parts/material, fabricate and assemble parts, inspect and test items, and maintain systems;

c. Determining the appropriate configuration control authority for each configuration document consistent with logistic support planning for the associated CI;

d. Issuing identifiers for the CIs and document the identifiers within the configuration documentation;

e. Maintaining the configuration identification of CIs to facilitate effective logistics support of items in service;

f. Releasing configuration documentation; and

g. Establishing configuration baselines for the configuration control of CIs.

3.8.2 Configuration Baselines. The TDP shall establish the configuration baseline. The final production design approved at the Production Readiness Review (PRR) establishes the approved product baseline.

The Contractor shall update and maintain changes to the TDP as a result of configuration changes. The baselines shall include the hardware, firmware, and software (including Operating Environment (OE)) baselines established as a result of a successful PRR.

3.8.3 Configuration Change Control. Any requested change(s) to or Requests for Deviation (RFD) from the Government controlled baseline shall be submitted to the Government Configuration Control Board (CCB) in accordance with the Government approved Contractor’s CM Plan.

3.8.3.1 Local Configuration Control Board. The LCCB is responsible for the evaluation and disposition of all proposed configuration changes. The Government will chair the LCCB. The LCCB Secretariat will manage the documentation review process.

The Contractor shall provide membership and information as requested by the Government to support CCB review and decision meetings. The LCCB will review and disposition (approve or disapprove) Preliminary Engineering Change Proposals, Engineering Change Proposals (ECPs), Specification Change Notices (SCNs), and Requests for Deviation (RFDs). The Contractor shall obtain Procuring Contracting Officer (PCO) or duly authorized Government representative concurrence with the classification of all Class II ECPs and Minor RFDs prior to execution. Class I ECPs and Major RFDs shall not be executed without specific Contracting Officer approval. The Contractor is encouraged to participate in the LCCB process for all changes.

3.8.3.2 Engineering Change Proposals. The Contractor shall prepare and submit preliminary ECPs for all proposed configuration changes including changes generated by vendors. The purpose of the preliminary ECP is to provide advance notification of a proposed change, assign a recommended ECP classification (Class I or II), and obtain Government concurrence to expend resources to fully document the proposed change. If a Class I ECP is proposed, the Contractor shall include rationale explaining why the proposed change cannot be accomplished by a Class II ECP. The Contractor shall include Life Cycle Cost (LCC) impact estimates as part of the preliminary Class I ECP.

The Contractor shall generate ECPs when directed by the Government and/or following Government approval of a preliminary ECP. DD Forms 1692 and 1693 shall be used for Class I and II ECPs, respectively. An ECP shall contain the data necessary for the Government to render final CCB disposition. (CDRL A018)

Deliverable Data Item (See DD-1423):

CDRL A018: “Engineering Change Proposal”

3.8.3.3 Affordability Based Change Management. The Contractor shall support the Government in the evaluation of proposed cost reduction system changes.

3.8.3.4 Specification Change Notices. The Contractor shall generate Specification Change Notices (SCNs) to propose, transmit, and record changes to baseline specifications or requirements documents. (CDRL A019)

Deliverable Data Item (See DD-1423):

CDRL A019: “Specification Change Notice”

Request for Deviation (RFD). The Contractor shall generate a Request for Deviation (RFD) to request approval for a temporary departure from a specific requirement(s) of the approved CDS baseline. . DD Form 1694 shall be used for RFDs. (CDRL A020)

Deliverable Data Item (See DD-1423):

CDRL A020: “Request for Deviation”

3.8.3.6 As-Built Configuration List (ABCL). The Contractor shall deliver an As-Built Configuration List (ABCL) with each equipment delivery. The ABCL shall extend down to the Lowest Replaceable Unit/System Replaceable Assembly level (LRU). The list of LRUs is provided as GFI in the TDP. (CDRL A021)

Deliverable Data Item (See DD-1423):

CDRL A021: “As Built Configuration List”

3.8.3.7 Configuration Status Accounting (CSA). The Contractor shall establish a CSA database to record and track status of CDS hardware and software, which shall be established and functional prior to the PRR. The Contractor shall provide the Government electronic access to this database throughout the term of the contract. The Contractor shall record the CSA data for each CDS system, including FAUs, in this database when each system is delivered.

The CSA data shall be identified to the LRU level as defined in the TDP. (CDRL A022)

Deliverable Data Item (See DD-1423):

CDRL A022: “Configuration Status Accounting Information”

The Contractor shall include a report of CSA database activities in the monthly Contractor’s Progress, Status and Management Report (CDRL A004).

3.9 SYSTEM SAFETY (Applicable to all CLINs). The Contractor shall adhere to the existing System Safety Program Plan (SSPP), Environmental Health and Safety Plan (EHSP), and System Safety Hazard Analysis (SSHA) Report. The Contractor shall prepare a Safety Assessment Report (CDRL A023) that certifies the Contractor's compliance with the SSPP, EHSP and SSHA, and identifies and provides a plan of action and milestones for resolving any safety or health issues associated with CDS production, test and use. The Contractor shall implement the SSPP, EHSP, SSHA and Safety Assessment Report including providing its employees with necessary safety training.

Deliverable Data Item (See DD-1423):

CDRL A023: “Safety Assessment Report”

3.10 OBSOLESCENCE MANAGEMENT. (Applicable to CLINs 0001-0020, 0024-0027, 1001-1020, 1024-1027, 2001-2020, 2024-2027, 3001-3020, 3024-3027, 4001-4020, 4024-4027, and 5002).

The Contractor shall develop and deliver a Diminishing Manufacturing Sources and Material Shortages (DMSMS) Implementation Plan using the ASN (RD&A) Memorandum, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Guidance, dated 27 Jan 2005 as guidance.(CDRL A024)

CDRL A024: “Diminishing Manufacturing Sources and Material Shortages (DMSDS) Implementation Plan”

3.10.1 Obsolescence Identification

The Contractor shall be responsible for identifying all changes that are required to avoid and/or resolve hardware, software and firmware obsolescence issues which may affect production and sustainment of CDS equipment. The Contractor shall identify the occurrence of DMSMS or obsolescence issues to the Government as early as possible and provide a proposed resolution plan. (CDRL A025)

Actions to resolve obsolescence management issues shall be initiated with sufficient lead-time to preclude impact to Government delivery requirements (including production and Fleet requisitions) while meeting the other requirements of this SOW. Associated configuration changes to the TI 12 CDS variants shall be processed in accordance with the Government approved Contractor’s CM Plan (CDRL A016).

When developing recommendations to resolve obsolescence issues, the Contractor shall, at a minimum, evaluate the following: drop-in replacements with similar or improved reliability, Life Time Buys (LTB) from the OEM or third party source, redesign to meet the requirements of the contract or technology refresh through product migration to a new product (with either the same or increased functionality or capability). Recommended solutions shall include unlimited data rights.

The Contractor shall track the obsolescence status and technology trends of CDS equipment and components and shall provide quarterly DMSMS Health Charts indicating product life cycle and proposed DMSMS resolution

(CDRL A026).

CDRL A025: “Technical Report-Study/Services: Product Recall, DMSMS, Obsolescence Identification and Vendor Change Notices” CDRL A026: “Diminishing Manufacturing Sources and Material Shortages (DMSMS) Health Analysis Report”

3.10.2 Product Recall and Emergent Changes by Vendors

The Contractor shall have an established process to notify the Government of any recall notices from suppliers of materials, components or products in the CDS equipment (CDRL A025). Such notices shall be provided to the Government within two (2) business days after the Contractor receives notification. Changes implemented by vendors without the prior knowledge of the Contractor shall be managed in accordance with the Contractor’s approved DMSMS Implementation Plan (CDRL A024) and Contractor’s CM Plan, once they are discovered.

3.11 PACKAGING HANDLING, STORAGE AND TRANSPORTATION (PHS&T) (Applicable to CLINs 0001- 0021, 0024-0027, 1001-1021, 1024-1027, 2001-2021, 2024-2027, 3001-3021, 3024-3027, 4001-4021, 4024-4027, and 5002). The Contractor shall submit a Packaging Plan that addresses the packing, packaging, handling, storage, and transportation of items delivered under this contract to the Government for approval (CDRL A027).

CDRL A027: “Packaging Plan: Packaging, Handling, Storage and Transportation (PHS&T) Plan”

3.11.1 Unique Identification Marking. The Contractor shall apply DoD Item Unique Identification (IUID) markings to the CDS units at the unit level assemblies and associated Lowest Replaceable Units (LRUs) in accordance with DFARS 252.211-7003. The Contractor shall tag, label, or mark GFP in accordance with DFARS 252.245-7001 and MIL-STD-130. Embedded subassemblies shall be marked in accordance with DFARS 252.211-7003. The Contractor shall submit the required data defined in DFARS 252.211-7007 to the IUID Registry. IUID pedigree data for LRUs embedded in unit level assemblies shall be entered into the IUID Registry as children to the Parent Unit. The Contractor shall maintain marking and verification records for all IUID qualifying items manufactured on this contract. These records shall be available for inspection by the Government at all times. The Contractor shall deliver the final IUID Marking Activity and Verification Report at the end of the contract. The Contractor shall provide the information required by DFARS 252.211-7003 on the DD Form 250, Material Inspection and Receiving Report (CDRL A028). The Contractor shall develop and maintain a marking plan using the approved plans referenced in Section 2.1, Government Documents, provided as GFI.

CDRL A028: “Item Unique Identification (IUID) Marking Activity and Verification Report”

3.12 INTEGRATED LOGISTICS SUPPORT (ILS) (Applicable to CLINs 0001-0008, 0024-0027, 1001-1008, 1024-1027, 2001-2008, 2024-2027, 3001-3008, 3024-3027, 4001-4008, and 4024-4027) The Contractor shall establish and implement an ILS program to ensure operational availability requirements are achieved, within given program constraints, through maintenance planning and the consequent development of all ILS elements. The Contractor shall team with the Government in developing performance-based support for ILS elements.