PWS_Draft.docx

DRAFT

PERFORMANCE WORK STATEMENT

FOR

MISSION MODULE ENGINEERING AND TECHNICAL SUPPORT

SCOPE

This Performance Work Statement (PWS) supports the Naval Surface Warfare Center Panama City Division (NSWC PCD) Modular Integration Division as the lead for engineering, analysis, and planning support for the modularization of off-board systems in support of the littoral warfare mission area. The requirements will include systems engineering, packaging and handling of off-board system hardware, system integration of legacy and emerging littoral mission systems, seaframe integration of mission modules, development of mission system common computing environments (e.g. Mission Package Computing Environment (MPCE)) and integrated communications networks (e.g. Multiple Vehicle Communication System(MVCS)), distributed engineering testing, and validation and verification. Specifically, these requirements include the general program, engineering, technical, and integrated logistics support requirements for the Littoral Combat Ship (LCS)Mission Modules (MM) program at NSWC PCD.

The LCS is a modular, reconfigurable ship with three types of Mission Packages: Surface Warfare (SUW) Mission Package (MP), Mine Countermeasures (MCM) MP, and Anti-Submarine Warfare (ASW) MP. The LCS MCM MP supports MCM operations through the employment of aviation assets and unmanned surface, semi-submersible, and submersible vehicles that are equipped with an array of sensors and systems to detect, localize, and neutralize surface, near surface, in-volume, and bottom mines. The LCS MCM MP is deployable on LCS and other vessels of opportunity (VOOs). The Contractor shall provide the level of effort necessary to support the technical areas identified in the following paragraphs.

Acronym List

Following is a list of acronyms used in this PWS.

1.0 APPLICABLE DOCUMENTS

The following documents, of the exact issue shown, form a part of this Performance Work Statement (PWS) to the extent specified herein. In the event of conflict between the documents referenced and the contents of this PWS, the PWS shall take precedence. Second tier and lower references, (i.e., those referenced in the primary references) shall be used for guidance only.

Military Specifications: None

Military Standards:

a) MIL-STD-882E, System Safety, dated 11 May 12

b) MIL-STD-31000B, Technical Data Packages, dated 31 Oct 18

c) MIL-STD-130N, Identification Marking of U.S. Military Property, 26 Aug 19

d) MIL-STD-3034A, Reliability Centered Maintenance (RCM) Program, 15 Apr 19 Other Documents:

a) Interface Control Document (ICD) for the Littoral Combat Ship (LCS) Flight Zero Reconfigurable Mission Packages, Baseline

b) 1.2, Rev A., dated 22 Jan 10

c) Capability Development Document (CDD) for Littoral Combat Ship Flight 0+ (Post RCR 554 - revision 5), dated 15 Apr 20

d) Littoral Combat Ship Platform Wholeness Concept of Operations Revision E, dated 26 Jan 16

e) D) PMS 420-PLN-08-0001 Rev B, Configuration Management Plan (CM Plan) for the Littoral Combat Ship (LCS) Mission Modules (MMs) Program, dated Aug 16

f) PEO LCS MM Class I Configuration Management Workflow User’s Guide, dated 06 Jul 17

g) NAVSEAINST 4423.5, Provisioning Policy, dated 07 May 19

h) NAVSEA M-4423.1, Provisioning and Allowance Procedures Manual, dated May 19

i) NAVSEA Interactive Computer Aided Provisioning System (ICAPS) Training Guide, dated 05 Jun 17

j) Aerospace and Defense Industries Association of Europe (ASD) Standard S1000D, International Specification for Technical Publications Utilizing a Common Source Data Base, dated 2019

k) ANSI/EIA-632-2013, Process for Engineering a System, dated 01 Sep 03

l) COMOPTEVFORINST 3980.2I, Operational Test Director's Manual, dated 03 May 19

m) Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) (see NOTE below)

n) DoD Directive 8140.01 with Change 1, Cyberspace Workforce Management, dated 31 Jul 17

o) DoD Directive 5144.02 with Change 1, DoD Chief Information Officer (DoD CIO), dated 19 Sep 17

p) DoD 8570.01-M with Change 4, Information Assurance Workforce Improvement Program, dated 10 Nov 15

q) DoD Instruction 8500.01 with Change 1, Cybersecurity, dated 07 Oct 19

r) DoDI 8510.01 with Change 2, Risk Management Framework (RMF) for DoD Information Technology (IT), dated 28 Jul 17

s) Federal Information Security Management Act of 2002

t) IEEE 12207:2017, Systems and software engineering — Software life cycle processes, dated Nov 17

u) ISO 9001:2015, Quality Management System, dated Jan 15

v) MIL-HDBK-1390, Level of Repair Analysis, dated 29 Jan 15

w) National Institute of Standards and Technology (NIST) Special Publication 800-37 Rev 2, Guide for Applying the Risk Management Framework to Federal Information Systems a Security Life Cycle Approach, dated Dec 18

x) NIST Special Publication 800-34 Rev. 1 Contingency Planning Guide for Federal Information Systems, dated 11 Nov 10

y) OPNAV 5239.1D, U.S. Navy Cybersecurity Program, dated 18 Jul 18

z) SECNAVINST 5239.3B, Department of the Navy Information Assurance Policy, dated 17 Jun 09

aa) SECNAV M-5239.2, Department Of The Navy Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification Manual, dated 27 Jun 16

ab) SAE EIA-649-1, Configuration Management Requirements for Defense Contractors, dated 04 Mar 15

ac) SEA EIA-649C, Configuration Management Standard, dated 10 Sep 19

ad) U.S. Government Printing Office, Style Manual, dated 12 Jan 17

ae) NSWCPCDINST 3110.2B, Pre-sail Dispatching Operating and Reporting Procedures for Naval Surface Warfare Center Panama City Division Support Craft, dated 18 Aug 20

NOTE: DISA STIGS are available at https://public. cyber.mil/ stigs/. DISA STIGS are frequently updated and relevant STIGs must be selected for use during performance and are not specifically cited herein. Military Standards and Specifications are available at https://assist.dla.mil/online/start/. DoD Directives and Instructions are available at http://www.dtic. mil/whs/directives/corres/ins1.html. Secretary of the Navy (SECNAV) instructions are available at https://www.secnav. navy.mil/doni/default.aspx. NIST Publications are available at http://csrc.nist.gov/ publications/PubsSPs.html. ERP desk guide(s) are available from: https://www.erp.navy.mil/. LCS and PMS 420 specific documents will be provided with the solicitation.

2.0 REQUIREMENTS

(a) The Contractor shall assume responsibility for this task order within 45 calendar days after award to include assuming responsibility for any Government Furnished Property (GFP) and hiring personnel. Within ten days of contract award, the Contractor shall provide a transition plan annotating the time line for acquiring the GFP and hiring personnel that are certified in accordance with this PWS. (CDRL A001).

(b) The Contractor shall ensure that employees shall communicate in and understand the English language and shall be United States (U.S.) citizens prior to being admitted to a Government facility. Contractor employees shall conduct themselves in a proper, efficient, courteous and businesslike manner. The Contractor shall remove from the site any individual whose continued employment is deemed by the Government to be contrary to the public interest or inconsistent with the best interests of National Security.

(c) The Contractor shall ensure all new employees are fully trained and certified to meet functional position requirements. For Government mandatory training (i.e. Safety, Personally Identifiable Information (PII), etc.) the Contractor shall ensure all Contractor personnel working onsite in a Government facility are registered in the U.S. Navy Total Workforce Management Services (TWMS) website at https://twms.navy.mil/selfservice/login.asp. The Government will identify mandatory training through this website and the Contractor shall monitor and ensure that Contractor employees complete required mandatory training requirements by the required completion dates. The Contractor shall provide the following information for each employee that will be working onsite at a Government facility in the Transition Plan (CDRL A001): Employees Last Name, First Name (No nicknames); Reporting Date, Contract Number, Job Title and the Government Contracting Officers Representative (COR) Organization Code. The Contractor shall document changes to this list (additions or departures) and training completion tracking information in the task order Contract Status Report.

Any additional onsite training in the support of NSWC PCD specific application problems will be provided by the Government as required. When additional training is required or specifically requested by the Government, the costs associated with attending this training shall be approved by the Procuring Contracting Officer (PCO) via a Technical Instruction (TI) and purchased under the Other Direct Cost (ODC) line items for the task order.

(d) Cyber Information Technology (IT) /Cybersecurity Workforce (CSWF) – the Contractor shall identify any personnel assigned to work on the contract that are considered part of the CSWF as defined in DoD Directive 8140.01 in the Transition Plan (CDRL A001) by providing the information required by paragraph (c) above. The Contractor shall ensure all CSWF personnel are registered in the U.S. Navy Waypoints website at https://don.csod.com/LMS/catalog/Welcome.aspx. The Government will identify mandatory CSWF training through this website and the Contractor shall monitor and ensure that Contractor employees complete required mandatory training requirements by the required completion dates.

CSWF personnel may be required to complete additional training outside of Waypoints. The Contractor shall document changes to the CSWF list (additions or departures) and provide CSWF training and certification tracking information in the task order Contract Status Report.

(1) Cyberspace Qualifications Per “DFARS 252.239-7001, Information Assurance Contracting Training and Certification” all personnel performing cyber functions must be trained and qualified. In addition, personnel shall maintain the appropriate security clearance per SECNAV M-5510.30C to perform the tasks associated with their assigned positions.

Note: DFARS uses Information Assurance (lA) which is the old title and acronym; it has been replaced by Cyberspace Workforce (CWF).

All positions with cyber functions, whether primary or as additional/embedded duties, shall have an Information Assurance category and level identified on each TI or applicable matrix in the PWS.

The contractor is required to:

1. Earn and maintain appropriate baseline certification as identified in DOD 8570.01-M for the position and tasking being performed prior to the period of performance.

2. If privileged access is required, the contractor shall complete a privileged access agreement, SECNAV 5239/1, and submit it to the COR. Contractors must obtain the applicable operating system/computing environment training within six months of the CWF(Program Manager) PM’s signature on the privileged agreement or the account(s) will be suspended. A copy of the certificate of completion shall be provided to the COR.

Unless expressly provided for in the TI, all responsibility for training that is required for the contractor to maintain a specific expertise, commercial certification, or continuous learning is the sole responsibility of the contractor employee and or the contractor’s employer.

(2) Cyberspace Reporting The contractor shall provide a list of all personnel assigned to the TI performing cyber functions as a part of the monthly CWF Report. The report shall include employee name, TI#, the applicable Information Assurance category/specialty and level (see PWS or TI), required certifications and fulfillment status.

New hire information for tasking requiring cyber functions shall be submitted to the COR at least 7 days prior to employee beginning performance of any cyber functions. New hire information shall include name, TI#, list of applicable cyber functions category, level, required certifications and fulfillment status to include a copy of the baseline certification documentation. Per DFARS 252.239-7001(c), “Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.” and therefore may not be allowed to charge to the Task Order.

(3) CWF Report (CDRL A002) The contractor shall provide a list of all CWF personnel assigned to PWS, TIs with a CWF functions as a part of the Monthly CWF Report. The monthly report of the contractor CWF personnel shall be provided to the COR and CWF PM to include, at a minimum:

Person’s name, Contract Number, TI/TO#, Person’s assigned labor category, if applicable, Information Assurance Technical (lAT)/ Information Assurance Management (IAM)/ Information Assurance Support Environment (IASE) category and level CWF Specialty Area Code (SAC) - optional CWF Work Role Code (WRC) - optional Status of person’s individual baseline certification(s)/fulfillment, and renewal date.

Updates for new OS/CE, if applicable.

Continuous Learning/Continuous Education (CL/CE) Status

(e) NSWC PCD will not provide space onboard NSWC PCD or the Naval Support Activity Panama City (NSA PC) during performance of this task order.

(f) This requirement shall be principally performed at the Contractor's facility located at:

Naval Surface Warfare Center Panama City Division 110 Vernon Avenue Panama City, FL 32407-7001

The Government will provide space for up to 12 Contractor personnel in office or working spaces each with a phone and Navy and Marine Corps Intranet (NMCI) computer with network connection. The Government will also supply the consumables for the stated equipment such as paper, toner cartridges, etc. The specific workspace location(s) will be provided at the time of award. The Contractor shall provide a list of employees who require access to these areas, including standard security clearance information for each person to the COR no later than thirty business days after the date of award. The workspace provided to the Contractor personnel shall be identified by the awardee, with appropriate signage listing the company name and individual Contractor employee name. Contractor management is responsible for establishing work hours for Contractor staff that meets the Government’s requirements for coverage.

When a Government facility is closed or early dismissal of Federal employees is directed due to severe weather, a security threat, or a facility-related problem that prevents personnel from working, on-site Contractor personnel regularly assigned to work at that facility should follow the same reporting or departure directions given to Government personnel. The Contractor shall not direct charge to the contract for time off, but shall follow parent company policies regarding taking leave (administrative or other). Non-essential Contractor personnel, who are not required to remain at or report to the facility, shall follow their parent company reporting policy. Subsequent to an early dismissal and during periods of inclement weather, on-site Contractors should monitor radio and television announcements before departing for work to determine if the facility is closed or operating on a delayed arrival basis.

When Federal employees are excused from work due to a holiday or a special event (that is unrelated to severe weather, a security threat, or a facility-related problem), on-site Contractors may continue working established work hours off-site or take leave in accordance with parent company policy. Those Contractors who take leave shall not direct charge the non-working hours to the Task Order.

Contractors are responsible for predetermining and disclosing their charging practices for early dismissal, delayed openings, or closings in accordance with the Federal Acquisition Regulation (FAR), applicable cost accounting standards, and company policy. Contractors shall follow their disclosed charging practices during the Task Order period of performance, and shall not follow any verbal directions to the contrary. The Contracting Officer will make the determination of cost allowability for time lost due to facility closure in accordance with FAR, applicable Cost Accounting Standards, and the Contractor’s established accounting policy.

(g) Contractor-operated vehicles shall meet the following criteria:

The company name shall be displayed on each of the Contractor's vehicles in a manner and size that is clearly visible. All vehicles shall display a valid state license plate that complies with State Vehicle Code. Vehicles shall meet all other requirement of the State Vehicle Code, such as safety standards, and shall carry proof of insurance and state registration.

The Contractor shall mark all Government Furnished Vehicles “Contractor operated” in one and one-half inch (1 ½”) lettering. The color of the marking shall be distinguishable from the base vehicle color and match other vehicle markings, and in close proximity to the USN number.

Contractor personnel shall not utilize cellular telephones or personal devices while operating Contractor- furnished equipment or vehicles or personal owned vehicles on Government property.

(h) Contract Management

The Contractor shall provide management for administration and technical supervision of Contractor employees in the performance of Task Orders issued under this contract. The management team shall be the Contractor’s primary representative(s) and have the Contractor’s full authority to act on matters pertaining to the performance of services under this Contract. Contractor management shall:

(a) Be responsible for the overall performance of all services required by this Contract.

(b) Have the authority to act and make binding decisions for the Contractor.

(c) Meet with Government personnel designated by the PCO or the COR to discuss immediate problem areas.

(d) Be available during normal working hours

(e) To counter circumstances inferring personal services and to preserve the non-personal nature of the contract, the Contractor shall adhere to the following guidelines in the performance of efforts under the contract:

a. Directly supervise all contract employees assigned to tasks.

b. Refrain from discussing the issues such as skill levels and hours, salaries, cost and funding data, or administrative and personnel matters affecting Contractor employees with NSWC PCD personnel.

c. Ensure close communication and coordination with the COR, reporting problems to the COR as they occur (not waiting for a monthly meeting).

d. Ensure potential Contractor employees are not interviewed by Government officials, that Contractor employee's individual performance is not discussed with Government officials, other than the COR or PCO, that Contractor employees do not allow Government employees to approve their leave or work scheduling, that Government officials do not terminate Contractor employees, and that Contractor employee's do not receive assistance from Government officials in doing their jobs or assist the Government for areas not covered by this PWS.

e. Do not assign Contractor personnel to work under direct Government supervision.

f. Ensure Contractor employees obtain Common Access Cards (CAC), if appropriate, identifying them as contractors.

g. Use work orders to document and manage the work and to define the details of the assignment and its deliverables; the Government has the right to reject the finished product or result, and this does not constitute personal services.

h. When travel is required for the performance on a task, the Contractor personnel are only to travel as directed by their contract management (such as their Program Manager or equivalent point of contact).

i. The Contractor shall document their processes for ensuring services remain non-personal in nature during Contract performance in the Transition Plan (CDRL A001)

(f) Contractor-operated vehicles shall meet the following criteria:

a. The Contractor may be required to operate mobile equipment such as Government owned pickup.

(g) During performance in the task areas defined in this PWS, the Contractor may require access to information that is proprietary to the Original Equipment Manufacturers (OEMs) of Multiple Vehicle Communication System (MVCS) systems, subsystems, and components, some of which may or may not have already been delivered to the Government. The Contractor shall negotiate in good faith and enter into appropriate agreements (e.g., subcontract, Associate Contractor Agreement (ACA), or Non-Disclosure Agreement (NDA)) with pertinent OEMs to gain access to such information as required to perform the tasks defined in this PWS before the contractor may have access to proprietary information of the OEMs. It is anticipated that, as a minimum, the Prime Contractor may be required to negotiate appropriate agreements with the following OEMs of MVCS subsystems and components not readily available on the open market:

a. A & J Manufacturing Company

b. Ballard Technology

c. Crystal Group Inc.

d. Direct Beam Incorporated

e. Harris Corporation

f. Mid-Eastern Industries Division Technology Dynamics

g. North Star Scientific Corporation

h. Nova Electric Inc.

i. Parvus Corporation

j. Reliable System Services Corporation

k. ViaSat

The Contractor shall, using the guidance of PWS paragraph 2.3 and Government Furnished Information (GFI), provide all labor and materials required to support the following task areas:

Task Area # 1 – Program, Business, Financial, and Documentation Support

The Contractor shall support Government program management effort by performing functions such as:

a) The Contractor shall attend, as requested, NSWC PCD and program/project meetings. The Contractor shall report on the status of ongoing tasking. The Contractor shall provide verbal input at meetings. The Contractor shall support program and project personnel by developing draft meeting minutes and action items. The Contractor shall support program and project personnel in the development of Status Reports (i.e. weekly, bi-weekly). In the event that back-up Contractor support is required for additional meetings, a notice of 24 hours will be given. The Contractor shall provide support to program reviews at NSWC PCD, the Program Office, and/or Contractor Facilities. The Contractor, as requested, shall draft meeting minutes and/or trip reports from meetings. As requested, the Contractor shall support the Division and Branches in scheduling meetings, coordinating resources, tracking action items, and other administrative actions. (CDRL A002)

b) The Contractor shall support NSWC PCD in the preparation, tracking, and upkeep of selected program and project documentation and financial information. This will include developing, editing, formatting, and copying programmatic documents for selected program distribution. Distribution will be by e-mail, fax, local guard mail, commercial carrier, and/or hand delivery. Documents will include, but are not limited to 1) Weekly Accomplishments, 2) Team Member Communication Listing, 3) Task Reference Tables, and 4) Master Action Item Lists. (CDRL A003)

c) The Contractor shall develop briefing materials and presentations from information gathered by the Contractor in the course of performing engineering, analytical, and programmatic support and on information provided as GFI. Documents developed shall cover emerging operational concepts, processes, and strategies and include graphic formulations and depictions. Presentations are in support of NSWC PCD, Naval Sea Systems Command (NAVSEA), and Chief of Naval Operations (OPNAV) tasking and will include, but is not limited to, Initial Baseline Reviews, Tri-Annual Execution Reviews, and visitor tours. (CDRL A004)

d) The Contractor shall provide financial accounting support by performing downloads from both Navy Enterprise Resource Planning (NERP) and local NSWC PCD databases. Historical data extracted from these financial support systems will be used to develop monthly progress reports and support both NSWC PCD internal management reviews and periodic project reviews with sponsors. The Contractor shall support requirements for specific cost data calls. The Contractor shall prepare the monthly financial report by the 10th of each month with the prior month’s data. The Contractor shall deliver an updated Master Phasing Plan with current execution plans and milestone/ deliverable/task information obtained from the task Project Engineer at least once per week. The Contractor shall provide Task Summary Actuals with hours worked per task by employee at least twice per month. (CDRL A005, A006, A007)

e) The Contractor shall provide monthly Value Metrics reporting in accordance with NSWC PCD template and guidance. The Contractor shall utilize Value Metrics and project financial data to develop financial reports to support sponsor and NSWC PCD briefings. (CDRL A008)

f) The Contractor shall support development of Integrated Master Schedules (IMSs) and support the overall management needs of the Division’s projects. The Contractor will ensure that the cost, schedule, and technical aspects of the projects are integrated into an IMS that provides an accurate depiction of project status, the basis for course correction, and helps to bring the projects in on schedule. (CDRL A009)

g) The Contractor shall provide conference rooms for classified or unclassified meetings and phone lines or computer links to support phone or web-based conferences, as required.

Engineering Support

The following paragraphs specify the engineering efforts required to support acquisition, engineering development, testing efforts, and sustainment associated with the Mission Modules aboard both LCS and VOOs, which include, but are not limited to, other US Navy ships, foreign military ships, and commercial vessels. The following paragraphs also specify the engineering support necessary to support the MP In-Service Engineering Agent (ISEA) in such functions as installing systems on ships, certifying that the systems perform as designed, and developing improvements to the systems resulting from feedback gained during test and evaluation, exercises, and fleet operations.

2.1.1 Systems Engineering

a) The Contractor shall support system engineering activities associated with NSWC PCD tasking from the LCS Mission Modules program office (PMS 420) and other NAVSEA offices. The Contractor will use best industry practices in developing system engineering documentation. System Engineering support includes activities such as, but not limited to, requirements management and analysis, concepts of operation, safety, and risk management and analysis. The Contractor shall develop requested deliverables such as subsystem specifications and requirements traceability verification matrices.

b) The Contractor shall provide systems engineering support for shipboard operations, manning, MCM systems design and employment, MCM tactics, and the MCM MP (to include systems, support containers, and vessel specific support equipment). The Contractor’s support shall include both the LCS and VOOs. The Contractor shall investigate requirements for operational employment, manning, and tactics of MCM systems to be deployed on LCS or VOOs as part of the spiral development of the MCM MP. Using this knowledge, the Contractor shall support the system and subsystem requirements formulation by preparing MCM MM load outs, watch station analyses, operational sequence diagrams, and tactics inputs to be documented in various Concepts of Employment (COEs). In accordance with documents such as the ICD for the LCS Flight Zero Reconfigurable Mission Packages, the CDD for LCS Flight 0+, LCS Platform Wholeness CONOPS, MCM mission system program of record testing, and MCM mission analysis studies, the Contractor shall assist in the preparation of system development and operational recommendations for MCM integration in to future Fleet operations. The development of COEs requires continuous interface with a number of programs and activities. The Contractor shall support liaison efforts with Naval Mine and Anti-Submarine Warfare Command (NMAWC), Commander Naval Surface Forces Atlantic (COMNAVSURFLANT), Commander Naval Surface Forces Pacific (COMNAVSURFPAC), OPNAV, Commander Operational Test and Evaluation Force (COMOPTEVFOR), Naval Undersea Warfare Center (NUWC), Naval Air Systems Command (NAVAIR), PMS 420, PMS 406, PMS 495, PMS 505, and PMS 501 and other such activities. The Contractor shall develop and support COE briefs, receive and incorporate comments, engage Fleet in operational issues, expand detail of COE documents with operational timelines, examine new concepts for the MCM MP utilization in future spirals, and coordinate Fleet review of MCM MP requirements, human-machine interface demonstrations, and MCM MP developmental and operational testing.

c) The Contractor shall develop an MCM Operational Guidelines Manual (OGM) that provides direction on MP employment and operation from a command, supervisory, and operator perspective. The OGM shall include tactical and environmental considerations, system descriptions and specifications, system-handling descriptions, watch station instructions, and display and control descriptions. The OGM shall be developed by utilizing the CONOPS and user documentation developed as part of the MCM MP and with various Mission System's OGMs for guidance.

d) The Contractor shall provide systems engineering support in evaluating system problem reports for the performance of the MCM mission systems and mission modules against the requirements of the LCS ICD, CDD, and CONOPS, while being mindful of the MCM MP development strategy. This includes technical and operational evaluation of the minehunting, mine sweeping, and mine neutralization systems, such as the AN/AQS-20C Minehunting Sonar, Airborne Laser Mine Detection System (ALMDS), Airborne Mine Neutralization System (AMNS), Explosive Ordnance Disposal (EOD) systems, Unmanned Surface Vehicle (USV), Unmanned Influence Sweep System (UISS), Unmanned Vehicle Common Control (UVCC), Coastal Battlefield Reconnaissance and Analysis (COBRA) System, MQ-8B Vertical Takeoff Unmanned Aerial Vehicle (VTUAV), Surface Mine Countermeasure Unmanned Underwater Vehicle (SMCM UUV), Barracuda, the MCM Toolset, Organic Post Mission Analysis (OPMA), and the Organic Airborne and Surface Influence Sweep (OASIS). These technical performance measure evaluations shall be documented and reported monthly, as required.

e) The Contractor shall update and maintain the required MCM MP safety log, prepare and implement schedules, conduct briefs, submit applicable Systems Safety milestone documents and reports, attend and actively participate in meetings and training, track data exchanges of Systems Safety information, and provide administrative support. The MCM MP System Safety Plan (SSP) describes the management framework, documents requirements, and assigns functional responsibility in accordance with MIL-STD-882E and the MP Systems Safety Management Plan (SSMP). The Contractor shall maintain continuous interface with all mission systems, mission modules, and MP sub-elements and functional area representatives including Human Factors Integration (HFI) branch, facilities, Command and Control, tactics, and associated sub-systems and component developers, as necessary, to ensure proper integration and application of the SSP. The Contractor shall provide direct assistance to the MCM MP Systems Engineering Project Engineer and Lead Systems Engineer (NSWC PCD agents) in the MCM MP Environment, Safety, and Occupational Health (ESOH) Integration effort. Specifically, the Contractor shall assist the MCM MP Systems Engineering Project Engineer in developing and integrating MCM MP Programmatic Environment, Safety and Occupational Health Evaluation into the overarching scope of the program. The Contractor shall assist and support external LCS/VOO activities including Seaframe developers, other Navy labs, NAVAIR Ship Integration, Weapon System Explosives Safety Review Board (WSESRB), PMS 420, PMS 406, PMS 495, PMS 505, and PMS 501 and other such activities, as necessary.

2.1.2 Hardware Engineering (CDRL A011, A012, A013, A014, A015, A016, A017)

The Contractor shall provide technical support in the design, fabrication, and testing of modular and off-board systems hardware. The Contractor shall support the entire engineering development phase including requirements definition, design, modeling, drawings, analysis, fabrication of peculiar support equipment, testing, and installation. In addition, the Contractor shall support implementation of Engineering Change Proposals (ECPs). The Contractor shall ensure all specifications are sufficiently detailed to permit design, eventual production, and evaluation of the end item. The Contractor shall provide mathematical and computer-modeling support services of three-dimensional solids to support design concept development. The Contractor shall provide fabrication support for one-off or very small quantity (typically no more than two) prototypes or Engineering Development Models (EDMs), test articles, test assets, and/or test instrumentation for Government assessment and testing in support of the Government developing ECPs for the MCM MP. The Contractor shall integrate prototypes, EDM, test articles, test assets, and test instrumentation developed and maintain it in a functional state. The Contractor shall keep all specifications current for the duration of the task order. The Contractor shall support Government development of Advanced Change Study Notices (ACSNs) in support of ECP development. The Contractor shall maintain a positive documentation management process for all project tasks to ensure all aspects of design, including analysis, models, drawings, fabrication objective quality evidence, and prototype hardware are traceable and meet project requirements. A suitable data and Configuration Management (CM) system shall be in place at the Contractor’s facility. The Contractor shall use ANSI/EIA-632-2003 as a guide to implement engineering analysis, design and fabrication efforts. Engineering drawings and support documentation shall be prepared using MIL-STD-31000B as guidance. Markings shall be in accordance with MIL-STD-130N, as applicable.

The Contractor shall support the hardware installations and retrofit of Mission Package Computing Environment (MPCE) servers, switches, Keyboard Video Mouse (KVM), network switches, and firewalls on Navy Platforms as part of the ISEA Permanently Installed Equipment (PIE) process.

2.1.2.1 Drafting Support

The Contractor shall provide technical expertise in drafting support. The Contractor shall provide design review for manufacturability including, but not limited to, fit, finish, geometric dimensioning and tolerancing as required to meet design intent. When required, the Contractor will provide drafting support to create, check, and edit mechanical and electrical drawings. All drawings shall be created in accordance with and include appropriate requirements as detailed in MIL-STD-31000B. All drawings shall be provided in appropriate print formats and sizes, hard copies to be on ANSI B (11in. X 17in.) sheet, and digital copies to be included. Drawings shall be prepared using the Government provided templates, in AutoCAD 2013 to 2017 (or latest approved for NMCI) or SolidWorks 2018 or 2019 (or latest approved for NMCI).

2.1.3 Software Engineering (CDRL A018)

The Contractor shall provide technical support in the requirements definition, design, development, integration, and testing of Mission Modules program command, control, communications systems, and associated simulators and stimulators. The Contractor shall support the software life cycle including requirements definition, design, development, testing, integration, configuration management, and supportability in accordance with IEEE 12207:2017.

The Contractor shall support software engineering tasks for the continued design, computer programming and coding, development, testing, and sustainment of MCM MP Software and its future builds; i.e. the Mission Package Application Software (MPAS), MPCE software in accordance with Government furnished Software Development Plans (SDP). Performance of this support will require proficiency in the following areas:

· Programming Languages such as C, C++, Java

· Scripting Languages such as Bash, Python

· Operating Systems such as Linux, Windows 7/10, ESXi (VMware)

· Development tools such as Eclipse, Qt, Subversion, Git

· Middleware/communication protocols/application serving such as CORBA, SNMP, Tomcat, SOAP

The Contractor shall, using IEEE 12207:2017 and Capability Maturity Model Integration (CMMI) level 3 processes for guidance, provide engineering, coding and programming, integration, testing and documentation support for Command and Control (C2) software development. Efforts shall include supporting requirements, design, and implementation analysis; providing programming and network support; developing and maintaining an Integration Notebook that contains the installation, setup, and configuration parameters for each of the software packages; running prescribed test scripts for software test events; installing computer software configuration items; reviewing and commenting on C2 software design documentation; developing and maintaining a C2 Technical Operators Manual; and developing and maintaining software user guides. The Contractor shall participate in and develop documentation for technical meetings, briefings, presentations, and reviews.

2.1.3.1 System Software Development and Configuration Management Support (CDRL A019, A020, A021, A0022, A023, A024, A025)

The Contractor shall provide engineering, integration, testing and documentation support to LCS Mission Modules programs based on GFI SDPs. Anticipated tasking includes, but is not limited to, supporting mission requirements, design, and implementation analysis; providing programming and network support; developing and maintaining an integration notebook that contains the installation, setup, and configuration parameters for each of the software packages; running prescribed test scripts for software test events; installing computer software configuration items (CSCIs); reviewing and commenting on system software design documentation; and developing and maintaining software user guidelines. The Contractor shall conduct periodic code walkthroughs during the software development phase.

Senior technical personnel (NSWC PCD agents) from the development team shall review the code and unit test plans that have been developed for a specification. The purpose of the review is to identify that the code adheres to the program’s development standards, is technically sound, meets the design articulated in the related specification, and that the unit test plan for the code under review is documented. The Navy reserves the right to have one or more representatives, on a not-to-interfere basis, observe all code walkthroughs and create a detailed report. Code walkthroughs will not be conducted until the code has appropriate markings with respect to intellectual property rights. These walkthroughs help support the open architecture principle of design disclosure.

2.1.3.2 Software testing and Support (CDRL A026, A027)

The Contractor shall, as required, perform checkout functions, debugging, and software integration. The Contractor shall provide test integration of individual modules, subroutines, subsystems, and systems. Levels of testing shall include Software Unit (SU) testing, CSCI testing, Build Testing, and Factory Acceptance Testing (FAT). The Contractor shall generate and submit test procedures for each Build. The Government will review and approve FAT test procedures prior to FAT events. A Government representative shall be on-site to witness the FAT events. Following FAT, the Contractor shall prepare and deliver a Software Test Report (STR) documenting the results of software testing. The Contractor shall support software integration, configuration management, and logistics as required that will meet Government acceptable standards such as ISO 12207 and CMMI Level 3 requirements.

2.1.4 Mission Package Technical Direction Agent (TDA) Support (CDRL A028)

The Contractor shall support NSWC PCD in their role as Mission Package Integrator (MPI) Technical Direction Agent (TDA) for management, technical execution, and support for the MCM MP. The Contractor shall provide the appropriate level of Subject Matter Experts (SMEs) (based on thorough knowledge and experience of the systems) to support the MPI by reviewing all MP and technical drawing packages in a timely, efficient and technically sound manner. The Contractor shall review drawings to verify technical accuracy and ensure the drawings meet technical standards. The Contractor shall validate thru observation, simulation and test that required functionality is present and that requirements are met in the MP and technical drawings. The Contractor shall also support task, such as, receive, archive, route, and follow-up on actions, ship equipment, and conduct quality assurance checks. Work includes preparation of schedule development and monitoring, establishment of value management metrics, analysis/verification of program control data, and collection, distribution, review and reporting of program deliverables.

2.1.5 Test and Evaluation (T&E) Support (CDRL A029)

The Contractor shall provide support for T&E efforts for LCS MM systems that are developed by the Government or are third party vendor products under evaluation by the Government. Contractor support does not include performing as a Test Director. The MM systems tested may consist of the full operational package and any combination of the package components. This support includes testing and integration aboard LCS and other VOOs. The Contractor shall review requirements, specifications and other documents related to the project to evaluate the technical adequacy of the documentation, identify alternatives, and technically support the evaluation of MM systems during system experimentation and testing. The Contractor shall provide technical and engineering input during the development of specifications and requirements documents for procurement of MM systems. The Contractor shall interface closely with the Modular Integration design teams to provide technical input to and review of integration and test documents such as plans, procedures, schedules and reports. The Contractor shall participate in test and evaluation working group meetings and technically support the activities of the working groups. The Contractor shall participate in Test Readiness Review (TRR) and Test Safety Review Committee (TSRC) meetings on the MM systems plans and procedures. The Contractor shall operate Government owned vehicles and equipment to include trucks, golf carts, forklifts, and small boats. The Contractor shall participate in T&E events. The Contractor may ride and berth aboard vessels of various size during testing in support of fulfilling such roles as safety observer, data collector, and boat liaison.

In instances where the requirement for Communication Security (COMSEC) information is invoked, the Contractor shall ensure all COMSEC equipment and information is handled, stored and protected in accordance with National Security Agency (NSA) requirements.

2.1.6 Experimentation Process (CDRL A030)

Mission Modules experimentation requires support in the coordination and execution…