20RWM28_0001_sol.pdf

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

This amendment is hereby issued to include the follow ing:

1.) Updated version of the Statement of Work (SOW) 2.) Updated version of CDRLs A006 through A008 3.) Original CDRLs A020 through A022 deleted 4.) CDRLs re-numbered due to Item 3 update above (Original CDRL A023 became A020 and so forth) 5.) Section L Paragraph 4.1.2 has been marked as "Reserved" 6.) The proposal due date has been extended from 17 August 2020 to 31 August 2020

1. CONTRACT ID CODE PAGE OF PAGES

U 1 27

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

16C. DATE SIGNED

BY 05-Aug-2020

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 N0016420RWM28

X 9B. DATED (SEE ITEM 11)

17-Jun-2020

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

05-Aug-2020

CODE

NAVAL SURFACE WARFARE CENTER CRANE DIV

T. STOLL (812-854-1342)

BLDG 121

300 HWY 361

CRANE IN 47522-5001

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0016420RWM28

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

STATEMENT OF WORK (SOW)

FOR

ENGINEERING DEVELOPMENT MODEL (EDM) AND LOW-RATE INITIAL PRODUCTION (LRIP)

SURFACE ELECTRONIC WARFARE IMPROVEMENT PROGRAM (SEWIP) BLOCK 3 ELECTRONIC

ATTACK (EA) SUBSYSTEM OF THE AN/SLQ-32(V)7 INTEGRATION TEST SUPPORT, INSTALLATION

SUPPORT,

AND SUSTAINMENT

August 2020

1.0 Scope.

This SOW covers spares and repairs, and other related sustainment activities from Northrop Grumman Systems Corporation (NGSC) for the one (1) EDM and two (2) LRIP SEWIP Block 3 EA subsystems previously delivered under contract N00024-15-C-5319. This SOW also covers engineering and technical services from NGSC to support NSWC Crane Division with the integration of SEWIP Block 3 LRIP EA subsystems into AN/SLQ-32(V)7 systems.

1.1 Objective.

The objectives for this SOW are to obtain EDM and LRIP SEWIP Block 3 EA subsystem equipment and Lowest Replaceable Unit (LRU) repairs, and spare LRU provisioning. Engineering and technical support for integration of the of the SEWIP Block 3 equipment with the AN/SLQ-32(V)6 forming the AN/SLQ-32(V)7 Electronic Countermeasures System will consist of several focus areas.

Technical support includes pre-integration planning and setup for the Production Integration and Test (PIT) facility at both Northrop Grumman facilities in Baltimore, MD, and NSWC Crane Division, Crane, IN. Additionally, the contractor will support equipment installation (new installations include PIT facility, ships and shore sites); system assembly; system functional test; system hardware and software troubleshooting; issue root cause analysis and resolution recommendation; and training of integration personnel, operators and maintainers.

The contractor will provide knowledge transfer/tutoring to Navy technical personnel to enable the Government to assume independent responsibility for the operation, modification, integration, test and support of SEWIP Block 3 EA subsystems as integrated into the AN/SLQ-32(V)7 system.

2.0 Applicable Documents.

The following documents form a basis for this contract. Wherever MILSPECS and MIL Standards are cited, it shall be understood that they are for guidance only.

2.1 Department of Defense Specifications.

FY18 NAVSEA STANDARD ITEMS (NSI)

NSI 009-07 24 July 2019 Confined Space Entry, Certification, Fire Prevention and Housekeeping; accomplish

NSI 009-24 01 October 2018 Authorization, Control, Isolation, Blanking, and Tagging Requirements; accomplish

NSI 009-73 01 October 2018 Shipboard Electrical/Electronic/Fiber Optic Cable;

remove, relocate, repair, and install

NSI 009-74 01 October 2018 Occupational, Safety and Health Requirements;

Accomplish

DOD 5200.02 3 April 2017 Procedures for the DoD Personnel Security Program

(PSP)

DoDD 5220.22-M 28 March 2013 National Industrial Security Program Operating Manual

DoD 8570.01-M Change 4

10 November 2015 Information Assurance Workforce Improvement Program

DOD SD-22 29 January 2016 SD-22 Diminishing Manufacturing Sources & Material Shortages (DMSMS) Guidebook

DoDD 8510.01 12 Mar 2014 Risk Management Framework (RMF) for DoD Information Technology (IT)

DoDI 8140.01 Change 1

31 July 2017 Cybersecurity Workforce Management

MIL-HDBK-61A 07 February 2001 Configuration Management Guidance

MIL-HDBK-1785

Notice 2

11 February 2019 System Security Engineering Program Management Requirements

MIL-HDBK-2155

Notice 2

19 July 2019 Failure Reporting, Analysis and Corrective Action Taken

MIL-HDBK-29612/2A

Notice 3

31 March 2016 Instructional Systems Development/Systems Approach to Training and Education

MIL-STD-2042B 25 July 2002 Fiber Optic Cable Topology Installation Standard Methods For Naval Ships

MIL-STD-1678-1 28 May 2010 Fiber Optic Cabling System Requirements And Measurements

SER 96315/067 31 October 2003 Navy Guidance Document, Methods To Measure Ferrule End-Faced Fiber Optic Connectors And Termini

OPNAVINST 5100.23G CH-

21 July 2011 Navy Safety And Occupational Health Program Manual

COMUSFLTFORCOMINST

4790.3

25 November 2013 Joint Fleet Maintenance Manual (JFMM)

OPNAVINST 5530.14 20 November 2017 Navy Physical Security Manual NAVMC 1553.1A 15 September 2016 Marine Corps Instructional Systems Design/Systems

Approach to Training and Education Handbook

NSWCCRANEINST

12792.2

08 December 2016 Drug-Free Workplace Program

NSWCCRANEINST 5100.2 24 March 2014 Contractor Safety And Health Program

NAVSEA S0400-AD-URM-

010/TUM Revision 07

21 November 2013 Tag-Out User’s Manual (TUM)

SECNAV M-5239.1 Nov 2005 Information Assurance Manual

SECNAVINST 1543.2

SECNAV M-5239.2 27 June 2016 DON Cyberspace IT and Cybersecurity Workforce

Management and Qualification

SECNAVINST 5239.3C 02 May 2016 Department of the Navy Cybersecurity Policy SECNAVINST 5239.20A 10 February 2016 DON Cyberspace Information Technology and

Cybersecurity Workforce Management and Qualification SECNAV M-5510.36 June 2006 Department of the Navy Information Security Program

SEVNAVINST 5510.30C 24 January 2020 Department of the Navy Personnel Security Program

2.2 Other Government Documents.

OSHA 1910.1200 8 February 2013 Toxic and Hazardous Substances OSHA 1915.14 3 July 2002 Hot Work OSHA 1915.15 3 July 2002 Maintenance of Safe Conditions OSHA 1915.16 25 July 1994 Warning Signs and Labels OSHA 1915.502 15 September 2004 Fire Protection in Shipyard Employment

2.3 Industry Documents.

ANSI/EIA-649C 07 February 2019 National Consensus Standard for Configuration Management

ISO 9001:2015 23 September 2015 Quality Management Systems - Requirements EIA-455-171 (FOTP-171) 01 June 2001 Attenuation By Substitution Measurement For Short-

Length Multimode Graded-Index And Single Mode Optical Fiber Cable Assemblies

2.4 Program Documents

The contractor shall use existing approved SEWIP Block 3 EA plans, policies and procedures (as appropriate), unless otherwise defined in statement of work to perform this effort and in response to the Contract Data Requirements List (CDRL) deliverable requirements. These existing approved SEWIP Block 3 EA plans, policies and procedures will be provided as Government Furnished Information (GFI) as listed in Attachment C.

3.0 Performance Requirements

3.1 General Requirements

The contractor shall provide the engineering and technical services, labor, and resources required to support the Government’s installation of SEWIP Block 3 EA subsystems into AN/SLQ-32(V)7 systems. Activities include equipment assembly, test, troubleshooting, repair, depot activities and installations. Services are required for short-term and long-term support in the Continental United States (CONUS), and short-term support Outside the Continental United States (OCONUS).

Primary pre-ship integration and related activities shall be conducted either at the Production Integration and Test (PIT) facility at NSWC Crane Division, Crane, IN, or at the System Integration Laboratory at Northrop Grumman Corporation, Baltimore, MD as directed by the Navy SEWIP Contracting Officer (PEO IWS2.0). Shipboard installation and at-port integration and testing will be conducted at San Diego, CA for LRIP1 and LRIP2. Repairs shall be conducted at the contractor’s Baltimore area facilities or vendor locations as necessary.. EMD support and investigations may be conducted in Baltimore, MD or Wallops Island, VA. At-sea support may emanate from any of the following locations: Rota, Spain; Yokosuka and Sasebo, Japan; Bahrain, UAE; Souda Bay, Crete; San Diego and Port Hueneme, CA.; Norfolk, Newport News and Dahlgren, VA.; Pearl Harbor, HI.; Pascagoula, MS.; Mayport and Pensacola, FL.; Bath, ME.; and Everett, WA. Tasking consists of integration, test, installation and deployed support of two LRIP systems. All tasking for this contract will be authorized via COR and Contracting Officer approved Technical Instructions.

All tasking under this contract will be authorized solely via contract modifications that authorize CLINs or SLINs.

When possible, to minimize administrative burden, existing CLINs and SLINs shall be amended to increase funding and the period of performance, in lieu of establishing additional CLINs or SLINs.

3.1.1 Engineering and Technical Services.

The contractor shall furnish the services of qualified personnel to support the Government assembly, installation, testing, checkout, and operation of SEWIP Block 3 EA subsystems within AN/SLQ-32(V)7 during initial set-up and operation at the PIT facility, integration, depot, Pre-System Operational Verification Tests (Pre-SOVT), SOVT tasking, On-board Technical Assistance, shipboard test events and software support. These services shall occur at the Production Integration and Test (PIT) facility at NSWC Crane Division, or the System Integration Laboratory at Northrop Grumman, and Government sites. Shipboard services are anticipated to occur at CONUS shipyard locations as identified in X attachment.

The contractor shall provide reach back technical support, during standard weekday business hours (9AM though 5PM EST), for the field engineering team to resolve installation, integration, test, and operational issues.

For PIT, System Integration Laboratory at Northrop Grumman, and at-ship support, the contractor shall have at least one trained and certified person to service the R134a refrigerant equipment during installation and integration activities. Servicing of the R134a at-sea will be the responsibility of the customer.

Field Engineering facility space: Each person at the PIT will be provided a personal workspace for engineering and administrative duties. A secure/lockable storage area will be provided for storing program assets and engineering support equipment/materials.

3.1.2 System Security Program

Upon receipt of applicable guidance from the contracting agency and using MIL-HDBK-1785 (DOD SYSTEM SECURITY ENGINEERING PROGRAM MANAGEMENT REQUIREMENTS) and DoDD 5220.22-M, "National Industrial Security Program Operating Manual", (NISPOM) the Contractor shall maintain the existing GFI system security-engineering program.

3.1.2.1 Operations Security (OPSEC)

The contractor is required to protect critical information associated with this contract to prevent unauthorized disclosure and will observe OPSEC requirements.

The Contractor shall maintain the GFI provided an internal Operational Security (OPSEC) plan to reduce security risks on the program. Contractor personnel should be aware at all times of any unusual persons or packages in their work area and immediately report those to the building security staff. If Contractor personnel become aware of any person seeking unauthorized access to information or program materials, they should immediately report this to the

COR.

3.1.3 Website Security

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

3.1.4 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. Because project data and information associated with Mission Module (MM) and Mission Package (MP) architecture, design and interfaces directly affects the Government, and because this data will be stored on Contractor networks as part of program execution, it is imperative that the Contractor take all necessary actions to safeguard the data, information systems and networks that contain, transport, process or store program data.

IA Certification & Accreditation (C&A) requirements apply to all DoD and Contractor's Information Systems (IS)/networks that receive, process, display, store, or transmit DoD information. Contractor IS/networks that are involved in the development or operation of systems shall be configured and operated in accordance with (IAW) controlling laws, regulations, and DoD policy.

3.1.4.1 General Security Requirements

The Contractor shall establish appropriate administrative, technical, and physical safeguards to protect any and all Government systems and data, to ensure the confidentiality, integrity, availability, authentication, and non-repudiation of Government data. As a minimum, this shall include provisions for personnel security, electronic security and physical security.

3.1.4.2 Password Management

“Administrative” accounts, for use by the system administrator for System software upgrades and maintenance, shall be password protected. Administrative passwords shall be a minimum length of 15 characters and consists of a mix of upper case letters, lower case letters, numbers, and special characters, including at least one of each.

The Contractor shall ensure that all factory-set or default firmware passwords are changed before delivery of the System. Each password shall be a minimum length of 15 characters and consists of a mix of upper case letters, lower case letters, numbers, and special characters, including at least one of each. Each password shall be protected such that they are not embedded in access scripts or stored on function keys.

3.1.4.3 Government Furnished Information (GFI)/Government Furnished Property (GFP) The Government will provide all applicable program technical documentation, information property as defined in Section J herein as GFI/GFP. This includes technical manuals, training materials and information, drawings, specifications, procedures, processes, and quality system documents required for the performance of engineering, logistics, and technical support. Additional GFI will be provided as required or at the request of the contractor or as specified by the contract. The contractor shall generate and deliver a monthly Government Furnished Property Report. (CDRL A029) The Contractor shall submit a GFP Deficiency Report (CDRL A001) covering both GFI and GFP IAW the following guidelines:

a. If GFI is not received within fourteen (14) days after the date it is scheduled to be delivered.

b. Within twenty (20) calendar days after contractor receipt of the GFI and inspection for patent defects such as quantity, identification, description, and readability, or if it differs in some other significant respect from that expected to be delivered.

c. Within fourteen (14) calendar days after contractor determination that GFI has latent defects such as technical, engineering, or design deficiencies that existed at the time of

GFI delivery, but which were not discovered until actual attempted use of the GFI.

3.2 Program Management.

The contractor shall manage all contract resources, and coordinate and direct the efforts of all contract functional areas to fulfill the requirements of the SOW.

The contractor shall use a proactive approach to resolve Government requirements and concerns. The goal is to ensure that corrections and improvements are with the focus on, but not be limited to, cost savings or avoidances, improved business practices and enhanced system capabilities and availability. The contractor shall utilize a disciplined management approach to develop, integrate and manage all areas of this contract. All contract areas shall demonstrate continuing progress in achieving cost, schedule, and contract requirements.

3.2.1 Contractor's Progress, Status and Management Report.

The contractor shall prepare progress, status, program risk and management reports and deliver them monthly.

(CDRL A002)

3.2.2 Contractor Cost Data Reporting (if applicable)

The contractor shall systematically collect and report actual contract costs for each system installation support effort as part of one report IAW (CDRL A003).

3.2.3 Quality of Data and Deliverables

The contractor shall ensure submittal of all data IAW the CDRL attachment as required by CLIN 0006. The contractor shall ensure data is; timely, complete, valid, accurate, and consistent.

3.2.4 Licenses, Certifications, and Training

The contractor is required to receive training and hold a valid license or certification for the operation of forklifts and other handling equipment (hoists, cranes, etc.); receive training and certification in the handling of hazardous materials; and receive training and certification for any other specialized operations as required in support of the tasking set forth in this SOW. Training may be Government sponsored and conducted on-center, contractor sponsored and conducted at vendor facilities.

3.3 Sponson Shelter Commissioning

The contractor shall provide engineering and technical services to support the Government to complete assembly of the Sponson shelters.

3.4 AN/SLQ-32(V)7 Integration Support

The contractor shall provide the engineering and technical services to support the Government to incorporate SEWIP Block 3 EA subsystem into the AN/SLQ-32(V)7 system. This task shall include support to the Government by conducting system and cable connectorization and continuity checks to ensure all subsystems are physically connected IAW GFI provided Installation Control Drawings.

3.5 System Operational Support

The contractor shall provide the engineering and technical labor to support the Government to load software components from source code to executables and ensure the system is ready for functional testing. The contractor shall support the Government during the ISEA with system operation, and participate in resolving issues identified during start-up and operation.

At-sea support services is defined as up to six trips per LRIP system, with each trip defined as a continuous duration up to 10 days.

3.6 Knowledge Transfer

In conjunction with the technical support tasks in this statement of work, the Contractor shall provide informal on-the-job knowledge transfer in the operation and troubleshooting of the SEWIP Block 3 EA subsystem of the AN/SLQ-32(V)7 system to Navy engineers /technicians and/or other contractor engineers/technicians as designated by the Government, who work alongside Contractor personnel. Refer to Section 4.2 for formal training requirements.

3.7 Engineering Investigations and Troubleshooting

The contractor shall conduct system troubleshooting; engineering investigation and root cause analyses for malfunctions and anomalous behavior of the SEWIP Block 3 EA subsystem equipment installed as part of the AN/SLQ-32(V)7 system. This includes investigations into hardware, software and firmware. The contractor shall provide results, recommendations and proposed solutions for all analyses undertaken to resolve SEWIP Block 3 EA subsystem issues. (CDRL A004) The contractor shall develop and deliver troubleshooting procedures to logically isolate and resolve system problems and failures. Isolation procedure shall be addressed for the SEWIP Block 3 EA subsystem’s LRUs, CSCIs, MSIs and RCM items. (CDRL A005)

3.8 System Repair

The contractor shall provide the labor, materials, equipment and resources required to repair or replace any SEWIP Block 3 EA LRU hardware that malfunctions or fails during integration, installation, SOVT and shipping. The contractor shall lay-in repair material required to execute equipment repairs. The contractor shall propose the lay-in material list for Government disposition and approval. The Government shall order these items at contract award as part of CLIN 0001.

The contractor shall provide depot-level repair test procedures.

3.8.1 Test Teardown & Evaluation (TT&E) and Re-Test OK (RETOK) When an item is returned for repair, the Contractor shall perform a test tear down and evaluation of the unit to determine the cause for the failure in accordance with CDRL (A011). If the TT&E results in a RETOK, the unit will be shipped back to Crane. Crane shall provide contractor with authorization to use USG provided Transportation Account Code (TAC) for shipment of all RETOK units back to Crane. Units undergoing repair or being returned to receive confirmation testing will require the contractor to execute or have executed a Factory Acceptance Test verifying the unit meets the same manufacturer’s specifications, standards and performance criteria as a newly manufactured unit, unless specifically directed by Crane. The contractor will provide data sheets reflecting the tests performed, the specification limits of the tests, the measured values of the unit under test and a Certificate of Conformance will be provided to Crane accompanying the returned unit.

3.8.2 Repair Proposal & Implementation

The Contractor may repair and perform Factory Acceptance Test on a failed non-consumable part without prior Government approval, up to a limit of $30,000.00 or 40% of the replacement cost of the failed item (total of labor and material), whichever is less.

If the cost of a repair is expected to exceed $30,000.00 or 40% of the replacement cost, the Contractor shall provide an estimate of required time and schedule to complete the repair and subsequent factory Acceptance Test. Within thirty (30) days, the Government shall either authorize and fund the repair of the unit or disposition of the unit. The Contractor is neither authorized nor obligated to perform a repair or Factory Acceptance Test beyond $30,000.00 or 40% of the item replacement cost. The Contractor shall be authorized to complete the repair and Factory Acceptance test upon approval from the Contracting Officer and COR.

A unit shall be considered Beyond Economical Repair (BER) if the cost to repair the unit is equal to or greater than 40% of the cost to acquire a new spare of that item. In the event the Contractor determines that a unit is BER, the Contractor shall notify the Government and provide an estimated price and schedule for repair. Within thirty (30) calendar days, the Government shall either authorize the scrapping of the unit or the repair of the unit.

A repair is considered complete when the unit is shown to be restored to Condition “A” by performance of a Factory Acceptance Test on the repaired unit.

3.9 Government Furnished Property

The contractor shall use government furnished property during performance of this contract.

3.9.1 Government Furnished Material and Equipment

The contractor shall utilize Government Furnished Property and Government Furnished Equipment defined in Attachments A and B, respectively in the performance of this contract.

4.0 Integrated Product Support

4.1 IPS Planning and Management Conferences

The Contractor shall plan, host, attend, coordinate, support and conduct semi-annual ILS Program Reviews, logistics planning meetings, IPTs, formal reviews, conferences, and audits in conjunction with the Government. The Contractor shall prepare agendas for Government approval. The Contractor shall prepare conference presentation materials, and provide minutes and reports following each review. Action item documentation, assignment of responsibility for completion and due dates shall be determined prior to adjournment of all reviews. A summary of all action items, responsible parties, and estimated completion dates shall be included with the minutes. (CDRL A006)

4.2 Training Support

4.2.1 Training Curriculum Development

The Contractor shall deliver training curriculum in several CDRLs, as described below.

4.2.1.1 Training Job Task Analysis

The Contractor shall review and update the GFI Job Task List (JTL). The Contractor shall then use the updated JTL to review and update the GFI Job Task Analysis (JTA) and deliver the updated JTA as CDRL A007.

4.2.1.2 Training Curriculum Development

The Contractor shall update the GFI training curriculum with SEWIP Block 3 EA subsystem Operator and Maintenance content prior to providing a training. The Contractor shall deliver the updated curriculum as CDRL A008.

4.2.1.3 Training Specification Compliance

The Government shall provide the Contractor with GFI training curriculum that is already compliant with the tailored requirements of MIL-HDBK-29612/2A Instructional Systems Development/Systems Approach to Training and Education, and NAVMC 1553.1 Systems Approach to Training Users Guide within 5 days of contract award.

The contractor shall incorporate AN/SLQ-32(V)7 system configuration changes resultant from integration of the SEWIP Block 3 EA subsystem, as part of the ECP, while maintaining compliance with MIL-HDBK-29612/2A, NAVMC 1553.1, and/or other specified guidance mutually agreed to by the Government and the Contractor. Each CDRL will specify the appropriate Data Item Description (DID) and shall specify how the DID is to be tailored for each deliverable. All GFI and Contractor deliverables shall be capable of being read with MS Office 2016 or newer.

4.2.1.4 Training Changes Resulting from System Changes

The Contractor shall update the training curriculum with changes that result from System Problem Reports (SPRs) that are derived from comments collected during testing or training events, as adjudicated by the Government and the Contractor.

4.2.1.5 Training Changes Resulting from ECPs

The Contractor shall review and assess the impact of Engineering Change Proposals (ECPs) on the training curriculum. The cost of review, assessment, and incorporation of ECPs will be funded separately by each ECP.

4.2.2 Training Conduct

4.2.2.1 Training Courses Required

The Contractor shall conduct SEWIP Block 3 EA subsystem training for Government operators and maintainers once near the end of the first year of the contract (CLIN 2000), and twice during each of the subsequent four years

(CLIN 2100, 2200, 2300, 2400).

4.2.2.2 Training Class Size

The Contractor shall provide two (2) instructors to conduct classroom and hands-on training, with hands-on training comprising at least fifty percent (50%) of each training conduct. Class size shall be limited to a maximum of eight

(8) students. Hands-on training may require groups of two (2) or four (4) students, which will lengthen the time required to provide hands-on training to all students. The Contractor shall print and provide one (1) hardcopy Student Guide/materials for each student.

4.2.2.3 Training Days and Hours

Training will be conducted on weekdays (Monday through Friday) only, unless otherwise required and mutually agreed between the Government and the Contractor. Additional training time or days will be funded separately. The length of each training day shall not exceed 8 hours of instruction. The Government will ensure that students are available for instruction forty (40) hours per week between the hours of 0800 and 1700, with one hour reserved for lunch or other required activities. Instructors shall ordinarily provide ten (10) minutes of break time after each fifty

(50) minutes of instruction, unless circumstances warrant doing otherwise.

4.2.2.4 Training Venue

All training will be conducted within the continental United States (CONUS). Whether training is conducted at the Contractor or Government facility, the host facility will provide a classroom suitably sized for the number of students and instructors, equipped with video projector(s), white board, internet access, printer/scanner access, and any common tools and test, measurement and diagnostic equipment (TMDE) that may be required for training. The Government will notify the Contractor at least 30 days in advance for CONUS training, and shall include dates, locations, and instructions for facility access.

4.2.2.5 Training Critiques and Comments

The Contractor shall issue instructional rating forms at the conclusion of each lesson and a Government-approved end-of-course critique at the conclusion of each course to collect student feedback. The Contractor shall provide to the Government all end-of-course critique documentation and a consolidated list of all student comments for adjudication by the Contractor and Government. The Contractor shall then incorporate the adjudicated comments into the training curriculum.

4.2.3 Training Personnel

4.2.3.1 Training Lead

The Contractor shall assign a Training Lead who will be the single Point of Contact (POC) throughout the period of performance for all training matters addressed by this SOW. The Training Lead shall have a background in the development and presentation of military training programs and shall ensure that deliverables are compliant with

Instructional Systems Development principles. The Training Lead shall be responsible for coordination, scheduling, development, revision, and update of all training deliverables, and for all Contractor-conducted training courses.

4.2.3.2 Training Developers/Instructors

The Contractor shall assign Curriculum Developers/Instructors who are able to read, write, speak, and comprehend the English language, including technical language and terms associated with the operation and maintenance of the system. They shall understand all training tasks and shall be proficient with the system operation and maintenance tasks to be trained. To the extent possible, Instructors who conduct training shall have participated in curriculum development.

4.2.4 Training Meetings

The Contractor shall host a Training Guidance Conference and semiannual training Technical Interchange Meetings (TIMs), as described below. The Contractor shall coordinate with the Government to plan and schedule meetings.

The Contractor shall provide the meeting agenda and any read-ahead materials for Government IAW (CDRL A009).

The Contractor shall provide meeting minutes IAW (CDRL A006).

4.2.4.1 Training Guidance Conference (TGC)

The Contractor shall host a Training Guidance Conference at the Contractor's facility within sixty (60) calendar days of option exercise. The Contractor shall invite all training Government and Contractor stakeholders to attend the conference to ensure a mutual understanding of training requirements and the Contractor’s approach to training execution.

4.2.4.2 Training Technical Interchange Meetings (TIM)

The Contractor shall host two (2) training TIMs per year at the Contractor's facility. The Contractor shall present training status and work-in-progress at each TIM. The Contractor and Government shall adjudicate any comments regarding presented material.

The Contractor shall work closely with members of the Government AN/SLQ-32(V)7 Curriculum Development Team to ensure seamless transition of training deliverables to Government-managed operations and maintenance training products (e.g., MDEMO Team, Integration Team, and Schoolhouse).

4.3 Sustainment.

When a failure occurs to a SEWIP Block 3 EA subsystem in contractor’s possession, the contractor shall conduct root cause analysis and provide resolution recommendations. Implementation of a resolution recommendation may include a proposal for additional scope and funding. No software modification shall occur prior to execution of a bilateral contract modification explicitly identifying the software modification scope.

4.3.1 Failure Reporting, Analysis, and Corrective Action System (FRACAS) and Reliability Growth Program.

The contractor shall utilize the existing Navy approved GFI SEWIP Block 3 EA subsystem Failure Reporting, Analysis and Corrective Action System (FRACAS) process to determine and document failures, root cause and, as funded, corrective actions taken for failures. For failures that occur to items in the contractor’s possession, the contractor shall report the information in FRACAS. For failures that occur to items not in the contractor’s possession, the contractor shall support the Government by inputting Government furnished information into FRACAS. FRACAS efforts shall cover failures during System integration, test, installation, pre-System Operational Verification Test (SOVT), SOVT, and initial operational deployment of the SEWIP Block 3 EA subsystem. Failure reporting categories shall include primary, multiple, or pattern (trend) failures. The FRACAS program shall use MIL-HDBK-2155, “Failure Reporting, Analysis and Corrective Action Taken,” as a guide.

The Contractor shall support the Government by reporting Government information on failures in fielded systems for trends. Trends are defined as three failures with the same failure mode cause. The Contractor shall assess the failure data for the identification of trends and identify those trends in the Failure Summary and Analysis Report (CDRL A010). In each Failure Summary and Analysis Report, the Contractor shall ensure that the root cause is identified and, as funded, the remedial actions taken (including parts replaced) are addressed.

The Contractor shall utilize a Failure Review Board (FRB) to review failure trends, corrective action status, and, for items in the contractor’s possession, to ensure adequate corrective actions are taken. The FRB shall assess failure scoring for impacts such as Mission Ending, Degraded Capability (work around exists or can fix later), Minor Failure, Discrepancy No Mission Impact Root cause analysis, recommend corrective action, or implementation strategy. The personnel appointed by the Contractor to act on the FRB shall be identified in the FRACAS procedures and the scope of their authority shall be identified. The FRB shall require failure investigations and analyses and, when funded and authorized ensure implementation of corrective actions. Failure fixes and FRB results shall be utilized as inputs to update Reliability Growth Curves.

Reliability growth will be assessed for items in contractor’s possession IAW GFI document number B06400h001647, Reliability Development Growth Test Procedures, revision A dated 16 December 2019. Reliability growth will be assessed based on equipment operational time and those failures assessed during the FRACAS program categorized as relevant and chargeable failures. Scoring conferences will be held to include both Contractor and Government, and both will be a voting member at the scoring conferences throughout the contracted period of performance. The Government may appoint a representative to the FRB as an observer.

Use of Failure Analysis and Corrective Action Records (FACAR) shall be IAW GFI document number B06500h001647, EDM Failure Analysis and Corrective Action Report (FACAR), revision K dated 29 January 2020.

Reporting of Software Problem Reports shall be IAW GFI document DI-WXM-029_REV_D_PROCEDURE FOR PROGRAM TROUBLE REPORT (PTRS) PROCESSING. The Contractor shall notify the Government within 24 working hours of any critical failure (i.e., one that prevents the system from performing its mission) for items in contractor’s possession. The Contractor shall notify the Government of all non-critical failures within 10 working days of the occurrence for items in contractor’s possession. For items not in contractor’s possession, the Government shall furnish the contractor with sufficient information to populate the necessary reports. The Contractor shall notify the Government by submission of a separate Failure Analysis and Corrective Action Report (FACAR) (CDRL A011) for each failure event. The Contractor shall also prepare and deliver a quarterly Failure Summary and Analysis Report (CDRL A010) to the Government identifying any failure affecting cost, schedule, producibility, and cost of ownership or interface/performance. This report is a summary of all FACARs submitted since the last summary report.

The Contractor shall identify system operational hours for each failure occurrence and include it in the FRACAS data structure. System operation hours shall be 1) estimated by the contractor’s integration and test team for events occurring prior to delivery and 2) Government provided information for operating time post-delivery.

The Contractor shall maintain a FRACAS database that shall include all applicable failure scoring and hours of testing completed at time of failure to support the FRB and reliability growth assessment and reporting. Reliability growth assessments shall be completed and provided as part of the Failure Summary and Analysis Report (CDRL A010).

4.4 Configuration Management

The contractor shall support the Government’s maintenance of a Configuration Management (CM) program according to the approved GFI SEWIP BLOCK 3 CM Plan using MIL-HDBK-61 and ANSI/EIA-649 as guides.

The program shall address all configurations of hardware, firmware, software and documentation, including common parts for the SEWIP Block 3 EA Subsystem. The contractor shall support the Government’s maintenance of form, fit and function compatibility with the requirements herein and between each system. The configuration shall support interchangeability and interoperability at the replaceable part level. Replacement parts are defined as those parts installed by Government personnel.

4.4.1 Baseline Identification/Configuration Control.

The SEWIP Block 3 EA Subsystem EMD and LRIP Product Baselines will be provided for this contract as GFI.

Any change or deviation from the product baseline, including any change in software, shall be documented by a GFI Government approved Engineering Change Proposal (ECP) and Notice of Revisions (NOR), for Class I changes, or Request for Variance (RFV). (CDRLs A012 [ECP I], A013 [ECP II], A014 [ECP Test Data and Records])

4.4.2 Data Management and Integrated Digital Data Environment (Contractor IDE) The Contractor shall maintain a data management program, as well as a secure Integrated Digital Data Environment (IDDE) for hosting and transmitting all unclassified technical data and computer software used on or produced in the performance of this contract.

The contractor will require use of the Defense Courier Service for the transfer of classified material.

The purpose of the IDDE is to create a seamless, collaborative data environment for the Contractor and Government team that contains all pertinent data about the project throughout its development and delivery. This data management program, including IDE structure, format, processes, and procedures, shall be documented as part of the GFI contract Program Management Plan.

In order to use the current contract specifications and applicable documentation, the contractor is required to use the Defense Technical Information Center (DTIC).

The Contractor shall provide the Government team access to and the ability to download all data listed in the SEWIP Block 3 EA subsystem Data Accession List (DAL) by actively using the IDDE. All items posted to the IDE, including drafts of deliverables that are not final versions, shall be considered delivered for purposes of the DFARS data rights clauses 252.227-7013, 7014, and 7017 (and subject to the same rights asserted for final deliveries).

However, these non-final versions shall not constitute acceptance for purposes of Inspection and Acceptance requirements or the DFARS data rights clauses 252.227-7013, 7014, and 7017. The DAL shall contain the list of all data generated in support of this contract. Deliveries of data, in addition to the IDE, shall be as indicated in CDRL A002 (Contractor’s Management Report). The DAL shall be updated via a delivered data item each month, provided as an attachment and concurrently with the Monthly Status and Progress Report, which shows the data added each month (incremental reporting), which shall be provided as a separate data item showing the current and comprehensive listing. The procedures shall provide for the identification of any portions of the data provided with restrictive legends, when appropriate.

Data (technical data and computer software) shall be protected IAW the appropriate GFI Program Protection Plans and Information Assurance guidelines. The Government may witness all Contractor efforts to accomplish the SOW requirements and maintains the right to comment on processes.

All computer software and technical data developed under this Contract and posted to the IDE shall be as defined in DFARS clauses 252.227.7013, -7014, and -7017 and appropriately marked as defined in DFARS clauses 252.227- 7013, -7014, and -7017, and asserted to in the contract. A scan report verifying the appropriate markings, including distribution statement, copyright statements, open source software, security classification and data rights shall be delivered with the data.

The Contractor shall comply with the requirements of the DD 254 for implementation of the IDDE and to ensure proper safeguarding of classified materials, events and processes, including documentation developed by the Contractor or received in support of working groups and IPTs.

The IDDE shall support access to unclassified and classified data and models, and provide services for virtual/distributed meetings (classified and unclassified, voice and data), configuration management of baselines and deliverables, and management support tools for program execution.

The Contractor shall provide and maintain accounts for up to 30 Government-designated users of the unclassified IDE including commercial product licenses and network capacity for up to 25 simultaneous users in addition to the Contractor’s designated users. Accounts shall be maintained through the CLIN’s period of performance.

4.4.3 Integrated Digital Data Environment

The Contractor shall use the Government furnished Integrated Digital Data Environment (IDDE) to transmit unclassified CDRLs and documents including the system design, integration and test engineering efforts, the Contractor's system engineering efforts, integrated logistics support efforts, and the Contractor's program management effort. The Contractor will have its own private section within the IDDE that only Government personnel may access. These personnel will be allowed access for program execution, CDRL and other document handling duties. All Contractor source data published in the IDDE shall be in native format unless otherwise specified. All products and data developed under this Contract shall be delivered with at least Government Purpose Rights, as defined in Section H, DFARS clause 252.227.7013, 7014, and 7017.

The Contractor shall use the Government established and maintained Wide Area Network (WAN) to support classified processing through to GENSER SECRET and for connecting the Contractor’s site with the Contractor’s major subcontractor(s) and the following six (6) Government-designated sites: Naval Sea Systems Command (NAVSEA), Washington Navy Yard, DC; Naval Surface Warfare Center (NSWC), Dahlgren Division, Dahlgren, VA; NSWC Crane, Crane, IN; Naval Research Laboratory, Washington, DC; Johns Hopkins University Applied Physics Laboratory, Laurel, MD. The Contractor shall use the WAN to transmit classified CDRLs and documents including the system design, integration and test engineering efforts, the Contractor's system engineering efforts;

integrated logistics support efforts; and the Contractor's program management effort. The contractor will be required to store and access GFE COMSEC at their facility to include Taclane, key material, key loading device and STE equipment.

Site Requirements for Contractor connection to the WAN:

1. An approved SECRET area for workstation placement.

2. An approved area for COMSEC equipment (Taclane enclosed in a padlocked Hoffman box).

This area may/may not be the same area as the workstation area identified in 1. above.

3. Copper cabling can be provided between workstation, printer, firewall, also between firewall and Taclane if Taclane is in same area as workstation. If Taclane resides in a different area than workstation, site will provide cabling from Taclane to firewall. Site shall provide cabling to Taclane from site’s network.

4. Power outlets for workstation, printer, firewall, Taclane and Hoffman box fan.

5. Unclassified connection for the Taclane (multimode fiber or copper).

6. Unclassified IP address, subnet mask & Default Gateways for Taclane use.

7. Site-Managed firewall changes required to permit the remote site Taclane to communicate with NRL’s Taclane.

8. Points of Contact (POC’s) for the Site-Managed firewall for troubleshooting the initial connection.

9. Site’s COMSEC POC information to give to NRL’s COMSEC POC to enable Taclane & Keys to be sent.

10. Drawing of remote site workstation and Taclane area(s) showing location of workstation and

Taclane in the area as well as any other IT equipment in the area. (Required for NRL’s DIACAP paperwork).

4.5 Engineering Change Proposals.

The contractor shall generate and deliver Engineering Change Proposals (ECPs) for the SEWIP Block 3 EA Subsystem to correct issues or problems identified during system installation, test and operation, and to support Government system improvement plans. (CDRL A012, A013, A014) ECPs shall be prepared by the Contractor and submitted to the Government IAW MIL-HDBK-61A(SE). The Government and the Contractor coordinate the content of ECP’s in advance of formal submittal. MIL-HDBK-61A(SE) Table 6-2 provides guidance concerning the classification of ECPs. All ECP packages will be submitted IAW the DI-WXM-040 ECP Instruction, provided as GFI, for further action. Other ECP Formats, including the Contractor’s shall not be used unless approved by the

PMO.

ECP proposal preparation costs are within scope of this contract. The parties shall mutually agree to implementation of new scope pursuant to approved ECPs.

4.6 Diminishing Manufacturing Sources and Material Shortages (DMSMS) The Contractor shall monitor DMSMS and obsolescence – exclusive of GFE – use in the SEWIP Block 3 EA Subsystem at all indenture levels over the entire period of the contract. The contractor shall develop a DMSMS/Obsolescence Management Plan and deliver it to the Government for review and approval (CDRL A015).

The DMSMS/Obsolescence Management Plan shall include strategies for managing the loss, or impending loss, of manufacturers or suppliers of components, assemblies, or materials used in the system as well as document the responsibilities for the Government relative to the costs associated with locating part replacement, vendor interface, Last Time Buy Procurements, and non-recurring engineering redesign efforts.

Any costs for drop in replacements, last time buy procurements, and redesign efforts are outside the scope of this effort. DMS resolution shall be separately proposed and funded. Last time buy procurements will be quoted as Firm Fixed Price and redesign or drop in replacement testing efforts will be quoted as Cost-Plus Fixed Fee.

The contractor shall perform the activities necessary to identify, monitor, and study DMS/Obsolescence concerns for the SEWIP B3 EA subsystem.