N65236-16-R-0026-0001.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

See page 2, further details in Section A.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 94

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

16C. DATE SIGNED

BY 29-Nov-2017

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 N65236-16-R-0026

X 9B. DATED (SEE ITEM 11)

08-Nov-2017

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 is extended, X 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 1 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

28-Nov-2017

CODE

US NAVY SPAWARSYSCEN ATLANTIC CHARLESTON

PO BOX 190022 2.0 CONTRACTS

843-218-3578

ELIZABETH.NORRIS@NAVY.MIL

NORTH CHARLESTON SC 29419-9022

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N65236-16-R-0026

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

AMENDMENT 01

The purpose of this modification is to update and make changes to : 1D, Attachments 2, 3, 4 5, 6, and Sections B, C, I, J, L, and M.

Changes to the RFP in Amendment 0001:

1. PWS Section 3.14.1 updated to state EMW and Cyber Exploitation. This also impacted Section L/M to match for Factor B4.

From: Electromagnetic Maneuver Warfare (EMW) or Cyber Exploitation T0: Electromagnetic Maneuver Warfare (EMW) and Cyber Exploitation

2. PWS Section 5.3.1.3 for eCMRA was updated with the correct web address - http://www.ecrma.mil.

3. Section J: WD for Charleston SC was added as Attachment 7.

4. L-317 Chart for Proposal Format was updated to show GA1 files are to be submitted separately - GateA1 A and GateA1 B.

5. L-317 Note was added after the chart - "Unless otherwise noted, the Government will exclude the title page, table of contents, list of acronyms and indexes from the page count of the aforementioned sections."

6. L-317 Factor D1/D2 changes made in accordance with Technical Feedback from Ms. Carel Peacock dated 11/20/2017.

7. Updating Factor E Section L-317 Removed VOSB and HBCU/MI in accordance with SBA.

8. Section L 317 Factor F: Past Performance, updated to correct POC for this effort, elizabeth.norris@navy.mil and lacey.flint@navy.mil.

9. L-335 was added as full text. "Estimated Effective Award Date"

10. Section M-307 Factor B B4 was updated for the and/or issue discussed above.

From: Electromagnetic Maneuver Warfare (EMW) or Cyber Exploitation T0: Electromagnetic Maneuver Warfare (EMW) and Cyber Exploitation

11. Section M-307 Factor E SMALL BUSINESS MUST MATCH SECTION L - Removed VOSB and HBCU/MI in accordance withSBA.

12. Section M 307 - Factor G COST/PRICE –

FROM: "A Cost/Price Proposal shall be submitted in accordance with Section B as set forth in the solicitation."

mailto:elizabeth.norris@navy.mil mailto:lacey.flint@navy.mil

TO: A Cost/Price Proposal shall be submitted in accordance with Attachment 5. Section B only profit and fee should be filled in.

13. Section I full text - 52.204-8 - removed 52.222-57

14. Section L 317 Factor B B4 was updated to:

From: Electromagnetic Maneuver Warfare (EMW) or Cyber Exploitation T0: Electromagnetic Maneuver Warfare (EMW) and Cyber Exploitation

Attachment Changes:

1. 1D Team Summary: Correct typo of two B3, to read correctly now at B1, B2, B3, B4 and B5.

2: Attachment 2 Capability Matrix, correcting Program Manager to have 15 cells instead of 20 to match the RFP.

3. Attachment 3 Small Business Participation removed VOSB, MIs, and HBCU.

4. Attachment 4 Past Performance Questionnaire - Revised point of contract to Elizabeth Norris.

5. Attachment 5 - Included missing professional labor categories "Safety Specialist 1 and 2" this increased the overall hours proposed from 318,720 to 322,560

6. Attachment 6 - Correction of formula in Cell R7 to include the Option 1 and 2 years.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 2003

The CLIN extended description has changed from:

Option in accordance with 52.217-8 for six months. *This CLIN is cost-only and the specific requirements will be priced at the task order level.

To:

Option in accordance with 52.217-8 for six months. *This CLIN is cost-only and the specific requirements will be priced at the task order level. Cost CLIN for travel, and other ODCs in accordance with Section C, Performance

Work Statement and L-329.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PWS

PERFORMANCE WORK STATEMENT (MISSION ENGINEERING CONTRACT 5.6)

1.0 PURPOSE

1.1 BACKGROUND

Space and Naval Warfare Systems Center Atlantic (SPAWARSYSCEN Atlantic) is a Department of the

Navy organization with a mission to rapidly deliver and support solutions that enable Information Warfare

(IW) for our Naval, Joint, National and Coalition Warfighters. SPAWARSYSCEN Atlantic meets our nation's demands for uninterrupted vigilance, fail-safe cyber security, adaptive response and engineering excellence by delivering secure, integrated and innovative solutions to many naval, joint and national agencies. SPAWARSYSCEN Atlantic serves naval, joint and national warfighters' unified efforts to best cope with the dangers of the 21st century and beyond by enabling them to respond to any situation, anywhere, at any time. SPAWARSYSCEN Atlantic conducts research, designs, acquires, engineers and sustains the systems, sensor connections, cyber network infrastructures and knowledge management services to ensure reliable information is available to only those who need it, where and when it is needed.

1.2 SCOPE

The scope of this contract covers the entire spectrum of non-inherently Governmental services and solutions

(equipment and services) associated with the full system lifecycle support including research, development, test, evaluation, production and fielding of sustainable, secure, survivable, and interoperable Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, Reconnaissance

(C5ISR), Information Operations (IO), Identity Operations (IdOps), Enterprise Information Services (EIS) and Space capabilities. Although not limited beyond the description above, this contract has a primary focus on mission capabilities within the SPAWARSYSCEN Atlantic Intelligence, Surveillance, Reconnaissance/ Information Operations (ISR/IO) 5.6 Competency and includes engineering and technical services for all of the warfighting domains which include land, sea, air, space, cyber, and electromagnetic warfare.

NOTE: Work may be performed at locations worldwide including Afghanistan.

1.2.1 Mission Engineering Description

Mission Engineering focuses on bridging the gap between operational requirements and technology solutions by leveraging a deep understanding of the context, characteristics, and constraints of a mission domain.

The oversight of this work is by the SPAWARSYSCEN Atlantic 5.6 Competency which focuses on the rapid acquisition, development, and delivery of effective and affordable capabilities to meet the mission requirements of our Navy, Marine Corps, Department of Defense (DoD), and Federal sponsors. Mission

Engineering execution specifically focuses on engineering activities, including but not limited to:

architecture, design, development, integration, testing, security, and support services. Mission

Engineering execution also focuses on the deliberate planning, analyzing, organizing, and integrating of current and emerging operational and system capabilities to achieve desired warfighting mission effects, which includes mission analysis, designing or adapting systems and architectures to meet mission outcomes, and analysis and assessments.

Mission Engineering fully encompasses the range of technical, engineering, and systems acquisition requirements for Command, Control, Communications, Computers, and Combat Systems (C5), Intelligence, Surveillance, Reconnaissance (ISR); Information Operations (IO); Domain Focused

Intelligence (SIGINT, IMINT, Identity Intelligence; Meteorology and Oceanography (METOC);

Cyberspace Operations (Offensive, Defensive, Exploitation); Electronic Warfare (EW); Enterprise

Information Services (EIS); and Space. Technologies include but are not limited to: multi-spectral/modal sensing, sensitive and tactical site exploitation (SSE/TSE); networked and distributed sensors, big data and advanced analytics, machine learning, artificial intelligence, decoys, and autonomous and unmanned systems.

Most of the SPAWARSYSCEN Atlantic 5.6 efforts concentrate on the delivery of Information Warfare capabilities, delivering effects through sea, air, land, space, electromagnetic (EM), and cyber domains through the full range of military operations and levels of war. These capabilities provide a strategic and operational advantage to our sponsors gained from fully integrating information assets, systems, and resources to optimize decision making and maximize warfighting kinetic and non-kinetic effects. These capabilities allow our warfighters to understand their own abilities while penetrating the designs of their adversaries; discern an adversary’s capabilities and vulnerabilities; and influence, disrupt, or deny an adversary’s ability to maneuver within any operational environment and domain. Within the Navy these capabilities are focused around Battlespace Awareness, Assured Command and Control (C2), and

Integrated Fires covering areas from Electromagnetic Maneuver Warfare (EMW) to Cryptologic Warfare.

Representative projects within the SPAWARSYSCEN Atlantic 5.6 Competency include:

Navy Projects:

o Ships Signals Exploitation Equipment (SSEE) Increments E/F o Cryptologic Carry-On Program (CCOP) o Automated Identification System (AIS) In-Service Engineering Activity o EP-3 Special Collection Add-On System (SCAS) o Distributed Common Ground System – Navy (DCGS-N) o Tactical Cloud Reference Implementation (TCRI) o Integrated Communications & Data System (ICADS) o Identity Operations Systems (IOS)

Marine Corps Projects:

o Identification and Detection Systems (IDS) o Identity Operations Systems (IOS) o Team Portable Collection System – Multi System Platform Capable (TPCS-MPC) o Communication and Emitter Sensing and Attack Systems (CESAS II) o Tactical SIGINT Collection System (TSCS) o Counter Radio Improvised Explosive Device - Electronic Warfare (CREW) o Counter Intelligence HUMINT Equipment Program (CIHEP) o Tactical Remote Sensor System (TRSS) o Intelligence Analysis System Family of Systems (IAS FoS) o Distributed Common Ground/Surface System – Marine Corps (DCGS-MC) o Tactical Exploitation Group – Remote Workstation (TEG-RWS) o Technical Control and Analysis Center (TCAC)

Joint Projects:

o Joint Threat Warning System (JTWS) o Distributed Common Ground System - Special Operations Forces (DCGS-SOF) o Combatant Craft Medium ISR o Near Real Time Identity Operations Systems

Current and future sponsors supported within the ISR/IO Competency include, but are not limited to:

PEO-C4I (PMW-120/740), PEO-LCS, PEO IEW&S, PEO-U&W NAVSEA, NAVAIR, NRO, NSA, DIA, DTRA, OSD, ODNI, OPNAV N2/N6, DARPA, ONR/NRL, USMC Intelligence, MARCORSYSCOM, SOCOM, CENTCOM, Joint Staff Extension (formerly JFCOM), PACOM, EUCOM, FLTCYBERCOM/10th Fleet, NIOC Suitland, U.S. Air Force, and U.S. Army.

2.0 PLACE(S) OF PERFORMANCE

2.1 GOVERNMENT FACILITIES

The Government will provide facilities (i.e., office space, computer hardware/software, or lab space) to those labor categories that would otherwise adversely affect the work performance if they were not available on-site. The location of contractor personnel with supplied Government facilities will be identified at the task order level.

2.1.1 Training Requirements

Contractor personnel working full-time or partially at a Government facility shall complete all applicable mandatory training requirements as specified under Security Training, PWS Para 8.2.3.

2.2 CONTRACTOR FACILITIES

The contractor shall have a facilities (i.e., office space, laboratory space, staging and storage areas, with or without classified storage) in order to accomplish task order objectives. Depending on the type of support required at the task order level, contractor shall be required to possess or establish facilities at specific locations. Any necessary contractor facilities requirements will be determined by the Government prior to task order award.

3.0 PERFORMANCE REQUIREMENTS

The following performance requirements describe the various non-personal services tasks that require resources to successfully fulfill responsibilities related to this contract. Contractors shall perform requirements in accordance with Federal Acquisition Regulation (FAR) and/or Defense Federal

Acquisition Regulation Supplement (DFARS) which does not include performance of inherently

Governmental functions. The contractor shall provide the necessary timely support to meet current and emergent requirements as requested by the program manager, technical point of contact, or other properly designated authority. Performance requirements may encompass more than one task area listed below.

The contractor shall furnish all work, management, supervision, labor, and materials necessary to ensure the effective and efficient performance of functions identified throughout this PWS which make up this requirement. The contractor shall be flexible, responsive, and capable of providing high quality services and support. As specified at the task order level, the contractor shall conduct travel and perform reviews that are necessary to ensure the effective and efficient performance of functions identified throughout this PWS.

The contractor shall be responsible for supporting and meeting the requirements of the following tasks:

Note: In compliance with SPAWARINST 4720.1A – SPAWAR Modernization and Installation Policy, all contract installation work performed aboard Navy ships and Navy shore sites is under Installation

Management Office (IMO) supervision; otherwise, a formal exemption request has been approved. In accordance with the Fleet Readiness Directorate Standard Operating Procedure (FRD SOP), COMSPAWARSYSCOM letter Ser FRD/235 dated 24 Apr 12, the contractor shall ensure proper notification and status updates of installation work performed outside of SPAWARSYSCEN Atlantic respective Areas of Responsibilities (AORs) are provided to the SPAWAR Officer in Charge (OIC) of the

AOR where the work is performed or applicable Geographic Lead.

3.1 TECHNICAL AND PROGRAM MANAGEMENT SUPPORT

The contractor shall support the execution of acquisition programs, projects, and Integrated Product Team

(IPT) actions as required by applicable task orders. The contractor shall have the capability to manage projects applying the Project Management Institute best practices (e.g., Project Management Body of

Knowledge, PMBOK). The contractor shall apply current industry lean and/or agile development best practices to technical efforts that include iterative and incremental project management techniques.

Emphasis is on placing capable and supportable systems in the hands of the warfighter when and where needed and at an affordable price. This support will be required through all phases of the acquisition lifecycle.

The contractor shall facilitate and participate in IPTs, special advisory boards, off sites, working groups, audit teams, etc. The contractor shall coordinate and monitor meetings, appointments, schedules, and facilities as requested, as well as provide direct support for presentations, conferences, events, and other meetings as requested. The contractor shall provide effective oral and written communications in order to interface with commands and other activities across the Government, DoD, and the Navy. The contractor shall analyze, evaluate and prepare briefs, reports and correspondence, editing for spelling, punctuation and grammar, as well as ensuring formats are in compliance with Government, DoD, and Navy procedures. As required by task order, the contractor shall develop various deliverable program management reports

(CDRL A001) in support of the multiple tasks listed below.

The contractor shall be able to provide significant coordination and interface with various DoD and non-

DoD activities located in and out of the contiguous United States (CONUS).

3.1.1 Acquisition Management

The contractor shall support drafting, analyzing, integrating, reviewing, and providing documentation and reports to programmatic leadership in accordance with Government, DOD and Navy regulations. This includes supporting the process of implementing and managing acquisition procurements/documentation to ensure that documents are properly executed providing proper controls and regulations. The contractor shall support the development, review and updating of charters, Memorandum of Agreement (MOA), Memorandum of Understanding (MOU), and organizational charts to enable more effective communications and organizations for the program and stakeholders.

3.1.2 Business, Cost Estimating, and Financial Management

The contractor shall assist the Government in the implementation of fiscal practices and controls at the program/project level. This includes the process of implementing and managing financial control systems, collecting financial data, analyzing financial reports, and making sound financial decisions based on the analyses. The contractor shall support programming, planning, and budgeting management including budget preparation and justification, funds execution, program planning and analysis, and the presentation of this data in various formats. The contractor shall analyze, evaluate, and provide recommendations for

Total Ownership Cost (TOC), Cost as an Independent Variable (CAIV), and Life Cycle Cost (LCC). The contractor shall analyze obligations and expenditures, maintain forecasts, prepare reports on the status/recommendations and availability of funds, justify and prioritize unfunded requirements, and assist with development, review and recommendation of execution year funding efforts.

3.1.3 Technical Management

The contractor shall provide programmatic leadership technical guidance, methodologies in managing, evaluating, providing recommendations, reports, and resolutions. The contractor shall work with

Government stakeholders and technology professionals to properly understand business requirements and develop an industry best practice approach to technology solutions. The contract shall provide support which includes the following:

Evaluating issues and providing recommendations related to system cost, schedule, and performance

Providing support for requirement generation, allocation, verification, and validation

Developing and maintain work breakdown structure

Performing and providing reviews, analyses, studies, documentation, and recommendations for system design including technical expertise in system engineering, software engineering, logistics, test and evaluation and training. Provide recommendations for planning, organizing, and managing critical aspects of the development, production, and/or deployment of capabilities

3.1.4 Agile Environment

As required by the task order, the contractor will work in a team-based Agile environment (e.g., Scrum, Kanban). The Government will create and maintain system roadmaps, project plans, and product and release backlogs that will be the basis for the contractor’s work. The Government Product Owner will specify high-level requirements to the Agile team. As in typical Scrum-based Agile processes, the

Government Product Owner will work together with the team to develop and estimate user stories and establish acceptance criteria. These acceptance criteria will specify expected functionality for a user story, as well as any non-functional requirements that must be met in the development of the story. The

Government Product Owner, supported by subject matter experts (SMEs) and business analysts, will determine whether or not acceptance criteria have been satisfied.

3.1.5 Lean Environment

As required by the task order, the contractor shall work in, establish, and support a Lean product development (e.g., Lean Production, Lean Systems Engineering) environment, applying lean thinking to

Information Technology, Systems Engineering, and Project Management. The contractor shall assist the

Government in any goals to deliver the best life-cycle value for technically complex systems with minimal waste.

3.2 SYSTEMS ENGINEERING SUPPORT

The contractor shall provide Navy, Marine Corps and Joint ISR/IO specific systems engineering support for the analysis, design, integration, installation, testing, and life-cycle support of new and upgraded systems associated with delivery of capabilities as defined by this contract. The contractor shall employ disciplined systems engineering processes in accomplishing contract tasking, using commercial best practices for systems engineering processes in planning, architecting, requirements development and management, design, technical management and control, technical reviews, technical measurements, integrated risk management, configuration management, data management, interface management, decision analysis, systems management, inspections and maintenance, sources of supply maintenance and repair, and test and evaluation, verification and validation. The contractor shall provide customer-friendly solutions that provide ease of use for non-technical Government users.

The Navy, Marine Corps and Joint ISR/IO systems engineering solutions shall follow industry standard engineering processes and may include but not be limited to: Technical assessments of all user requirements, integration of all Government Furnished Equipment (GFE) and Contractor

Acquired/Furnished Equipment (CAE/CFE) as proposed, hardware and software information, network applications, system design, initial and recurring training (Commercial Off The Shelf (COTS) or customized), maintenance and support, system interface studies and control documents, network integration and test plans, cost analysis/trade-off studies, engineering change proposals, and engineering support to Government engineers.

The contractor shall design, develop, test and package Navy, Marine Corps and Joint ISR/IO systems changes as well as provide problem resolutions for existing systems according to the task order. The contractor shall maintain the current system baselines and provide change and problem fixes to these baselines as required. The contractor shall provide to the Government all developed, modified, or converted software, processes, programs, scripts, operating instructions, data models, databases, system files, documentation, test files, and test conditions used to develop each approved systems change request.

As required by task order, the contractor shall develop various deliverable engineering/technical reports

(CDRL A002) in support of the multiple tasks listed below.

Task orders may further refine specific technical approaches and the Navy, Marine Corps and Joint

ISR/IO systems engineering processes according to Government, DoD, or Navy policies and practices.

The contractor shall employ the principles of Open Systems Architecture (OSA), and systems engineering activities used in developing contractor solutions shall adhere to open architecture designs and employ a modular OSA approach. Task orders may require adherence to other Governmental standards.

3.2.1 Systems Engineering Plan (SEP)

The contractor shall follow and refer to SPAWAR SEP guidance for common plans, procedures, checklists, forms, and templates that support system life cycle management and systems engineering processes, or be able to demonstrate comparable processes and artifacts. This includes managing and supporting program or system requirements (statutory, regulatory, derived, certification), technical staffing and organization planning, technical baseline management, technical review planning, event-based technical reviews, and integration with the overall management of the IPT, project or program, as required by applicable task orders. These findings may be utilized by the Government to develop acquisition strategies, test planning, sustainment planning, configuration management, risk management, and life cycle management. Task orders may tailor the overarching process requirements and artifacts.

3.2.2 Architecture and Design

The contractor shall support the design and development of Navy, Marine Corps and Joint ISR/IO systems and applications and their integration into the overarching enterprise architecture. The contractor shall assist the Government in developing system architecture documentation, design and planning of current and future systems by depicting technical, systems, and functional architecture views as required. The contractor shall facilitate and develop plans which will enable information sharing, integration, and interoperability while considering service-oriented architecture best practices by aligning architectures with overarching Government, DoD, and Navy architectures, and other related architecture activities as required by task orders.

The architecture support provided to the Government shall consider the full life cycle, inclusive of initial planning through systems decommissioning. The contractor shall provide all required design and development documents, and supporting architectural documentation, for any frameworks as identified in applicable task orders. The contractor shall develop systems in such a manner as to leverage maximum re-use and sharing across the platform by other Government, DoD, or Navy agencies.

3.2.3 Technology Insertion and Best Practices

The contractor shall integrate new equipment technologies into existing Navy, Marine Corps and Joint

ISR/IO system architectures as required by applicable task orders. The contractor shall apply a systems engineering approach to ensure that mission objectives and system criteria requirements are fulfilled.

Emphasis shall be on the demonstration of clear and definable improvements in the performance, logistics supportability, reliability and maintainability of the item. All efforts shall employ the latest technology in consonance with economic considerations.

The Government is interested in remaining current and knowledgeable in the latest industry trends that affect the technology provided to their customers. As specified by task order, the contractor shall provide white papers and briefings to agency management that includes the following information:

The latest industry trends in the functional areas supported under the applicable task order. The contractor shall provide suggestions for change to the operation and configuration of the infrastructure environment, as appropriate and as required, that will ensure that the agency remains current, efficient, and effective and so that the users continue to receive a high level of quality support. The white paper should include a cost benefit analysis of the suggested change.

Research and identification of system requirements and recommendations of technology solutions to project and technical leadership

Research and investigation of new technologies and their possible use by systems covered under applicable task orders. Services shall include ongoing evaluation of current technology, platforms, and operations to seek improvement and optimal business processes. The contractor shall identify and recommend best practices and best technology for the Government needs and responsibilities.

Where functional or performance problems appear (or approximately twice a year), the contractor shall provide program and technical leadership on applicable task orders with technology evaluations regarding specific issues such as areas of possible cost savings or state of art technology approaches that would improve performance or reduce costs. The contractor shall evaluate system performance in conjunction with communications and application performance. The contractor shall work with system administrators to analyze the performance of the deployed and developed applications, to include determining effects on server and network capacity as applications are deployed.

3.2.4 Cloud Expertise

The contractor shall provide expertise in cloud solutions as required by applicable task orders. As IT service models (e.g., “cloud”) continue to evolve and are embraced by the DoD, their use in mission-critical operations will become more prevalent. Cost savings, agility, innovation, and the strategic use of cloud for IT modernization and digital transformation will be realized through the implementation and use of resilient infrastructure, platform, and software services. Cloud solutions will have an impact in orchestrating software services, big data, and multiple sensors/devices that are connected to the cloud

(a.k.a. “Internet of Things”).

The contractor shall provide Navy, Marine Corps and Joint ISR/IO engineering support in the development and integration of cloud-based systems into -as-a-Service models, as specified by applicable task orders. This includes core services such as: security, data management and transport, storage, hosting, networking, and system health and status monitoring.

The contractor shall provide subject matter expertise as required by applicable task orders in popular software tools/capabilities such as VMWare/Virtustream, Amazon Web Services, Spinnaker, OpenStack, Microsoft Azure, and/or Google App Engine.

3.2.5 Technical Development Reviews

The contractor shall conduct formal and informal technical reviews as well as periodic technical development reviews for major capability upgrades. The purpose of these reviews is to observe that the design and other documentation is complete, complies with the established design and testing approach, is technically sound and will satisfy the functional requirements as defined in the approved functional design specification documents. The Government will establish entry/exit criteria and acceptance/rejection criteria for each formal review and will document these criteria in a Technical Instruction (TI).

Technical Review Objectives:

Assess the development maturity based on technical development goals, systems engineering events and accomplishments, and empirical test data supporting progress to date.

Ensure operational, functional, performance, information assurance, cost, schedule requirements and objectives, designs, implementations, technical performance measurements, and technical plans are being tracked, are on schedule, and are achievable within existing programmatic constraints.

Assess the system requirements and allocations to ensure that requirements are unambiguous, traceable to top-level requirements.

Demonstrate that the relationships, interactions, interdependencies, and interfaces between required items and externally interfacing items, system functions, subsystems, and system elements (including operators and maintainers), as appropriate, have been addressed.

Assess the degree of openness of the emerging system, its degree of DoD or Service-level Enterprise reuse, and critique any tradeoff decisions made.

3.2.6 System Supportability and Readiness

The contractor shall participate in the systems engineering process to impact the design from inception throughout the life cycle, facilitating supportability to maximize the availability, effectiveness, and capability of the system at the lowest lifecycle cost. Readiness and support resource requirements and design parameters include the following:

Reliability, availability, maintainability (RAM)

Human factors

User/machine/software/interface/usability

System safety

Survivability and vulnerability

Hazardous material management

Environmental quality factors such as assessment of air, water, and noise pollution.

Standardization and interoperability

Energy management

Corrosion

Nondestructive inspection

Transportability

3.3 SOFTWARE ENGINEERING SUPPORT

Software engineering includes the design, development, and documentation of software to support Navy, Marine Corps and Joint ISR/IO specific system requirements. The contractor shall utilize certified software and computer personnel as needed.

The contractor shall provide software engineering support for the analysis, design, integration, installation, testing, and life-cycle support of new and upgraded Navy, Marine Corps and Joint ISR/IO systems associated with delivery of capabilities as defined by this Contract. The contractor shall support technical reviews (e.g., design reviews, code walkthroughs), configuration management, test plan evaluation, field exercise support, and documentation review. During the lifecycle process, software engineering support will include, but not be limited to, software system reliability assessment, earned value, probability of success and other ROI analysis, software re-use (e.g., COTS, Government off the Shelf (GOTS)) strategy analysis, interoperability assessment, using software applications/tools, software metric reviews, and

Secure Software Engineering that develops and writes/codes new (or modifies existing) computer applications, software, or specialized utility programs following software assurance best practices. The contractor shall provide customer-friendly solutions that provide ease of use for non-technical

Government users. As required at the task order, the contractor shall develop various deliverable engineering/technical reports (CDRL A002) in support of the multiple tasks listed below.

Task orders may further refine specific technical approaches and the systems engineering processes according to Government, DoD, or Navy policies and practices. The contractor shall employ the principles of OSA, and software engineering activities used in developing contractor solutions shall adhere to open architecture designs and employ a modular OSA approach. Task orders may require adherence to other

Governmental standards.

3.3.1 Software Quality Assurance

If a contractor is required to develop a significant portion of any mission critical software product on a task order under this contract, the contractor shall be required to demonstrate they, or the sub-contractor that will be performing the task, are operating at a Software Engineering Institute (SEI) Capability

Maturity Model Integration (CMMI) Level 3 (or higher) software processes capability (or equivalent). If the SEI CMMI Level 3 (or higher) software processes capability (or equivalent rating) is required on a task order, the Government reserves the right to validate the software developers' process assertions and representations by conducting an evaluation or appraisals of the contractor's organization and sub-contractors using commonly accepted Industry/Government validation practices.

3.3.2 Software Development Plan (SDP)

The contractor (prime and/or subcontractor) that is responsible for leading software development efforts shall define a software development approach appropriate for the computer software effort to be performed under each task. The contractor shall document the approach in a Software Development Plan

(SDP) (CDRL A003). The contractor shall follow this SDP for all computer software to be developed or maintained under this effort. The contractor shall develop one SDP to support the unique software requirements for each task order/project. The Government will identify specific SDP project requirements at the task order level. At a minimum, the contractor shall ensure the SDP meets the criteria specified in the CDRL DD1423 using IEEE Std 12207-2008 and the task order PWS.

3.3.3 Software Code Walkthroughs

The contractor shall conduct periodic code walkthroughs during the development Phase, as specified by the task order. Senior technical personnel from the development team will review the code and unit test plans that have been developed for a technical design specification (TDS). 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 TDS, and that the unit test plan for the code under review is documented in accordance with Quality Assurance (QA)/Test standards as defined. The Government reserves the right to have one or more representatives, on a not-to-interfere basis, observe any and all code walkthroughs and create a detailed report.

3.4 DATA ENGINEERING SUPPORT

The contractor shall provide data engineering support for the analysis, design, integration, installation, testing, and life-cycle support of new and upgraded Navy, Marine Corps and Joint ISR/IO systems associated with delivery of capabilities as defined by this contract. Data engineering covers the architecture, design, development, integration, and testing of systems that access, collect, ingest, clean, analyze, store, visualize, and share data. This includes software development and system administration support to task order specific technologies, e.g. Hadoop, Accumulo, etc. The contractor shall employ commercial best practices as required by applicable task orders. The contractor shall provide customer-friendly solutions that provide ease of use for non-technical Government users.

Task orders may further refine specific technical approaches and the data engineering processes according to Government, DoD, or Navy policies and practices. The contractor shall employ the principles of OSA, and data engineering activities used in developing contractor solutions shall adhere to open architecture designs and employ a modular OSA approach. Task orders may require adherence to other Governmental standards. As required by task order, the contractor shall develop various deliverable engineering/technical reports (CDRL A002) in support of the multiple tasks listed below.

3.4.1 Ontology Development

Contractor shall support the development of data ontologies that enable semantic interoperability among heterogeneous data sources and systems. These ontologies shall be developed to serves as common models for all of the data sources within complex information ecosystems. The contractor shall ensure ontologies serve as a proxy for some portion of the world, employing as far as possible consensus expressions (from natural language, including scientific vocabularies). The contractor shall ensure ontologies are analogous not to a data model, but rather to a reality model of entities which make up the information domain.

3.4.2 Data Ingest and Integration

Contractor shall support data ingest and integration activities including data understanding, modeling, preparation, integration, and analysis for both structured and unstructured data from social, business, financial, health, biometrics, intelligence, including Imagery Intelligence (IMINT) and Multi-Intelligence

(Multi-Int), telemetry, and cyber data sources. The contractor shall support cognitive processing of intelligence products, open source info, social networks and media, and other data sources to support knowledge discovery and turn data into information to support decision making, provide situational awareness, promote understanding of the operational environment, and to lead to new or improved products and procedures.

The contractor shall use well-defined, standards-based, and published interfaces, e.g. Application Program

Interface (API). The contractor shall provide secure mechanisms to allow data exchange and interaction with external systems. The contractor shall provide comprehensive documentation and information necessary to analyze processes, procedures, and/or policies that were implemented in the creation of the data ingest or data integration systems.

3.4.3 Big Data Expertise

The contractor shall provide subject matter expertise for big data areas such as: data federation, data ingest, data streaming, data storage, complex adaptive systems, and distributed systems.

3.4.4 Analytics Expertise

The contractor shall provide subject matter expertise for analytics areas such as: data visualization, data mining (including visual, text, and natural language), speech recognition, signal recognition, predictive analytics, machine learning, deep learning, artificial intelligence, decision support, automation, and cognitive systems.

3.5 GENERAL ENGINEERING SUPPORT

3.5.1 System Acquisition and Mission Documentation

The contractor shall identify, refine, and document operational and functional requirements; translate operational and functional requirements to Concepts of Operations (CONOPS), Functional Requirements, Functional Descriptions and Operational Requirements Documentation such as Capability Development

Document (CDD), Capability Production Document (CPD), etc.; develop system, subsystem and component level design specifications and documents; and develop system performance documents, specifications, and interface requirements documents specifically for Navy, Marine Corps and Joint

ISR/IO systems. For any documentation (CDRL A002) required, the contractor shall develop and submit as specified by the task order.

3.5.2 Research and Experimentation

The contractor shall conduct fundamental research, scientific study, and experimentation directed toward advancing the state-of-the-art or increasing knowledge or understanding as required by applicable task orders. The contractor shall evaluate unproven technology applications and identify potential risks. Task orders may require manning, operating, and maintaining experimental platforms to support testing or demonstrations. The contractor shall document results (CDRL A002) and submitted as required by applicable task orders.

3.5.3 Study and Analysis

The contractor shall perform studies and analyses as required by applicable task orders. Such studies/analyses may include engineering, scientific, financial, operational, etc. considerations for acquisition efforts. The contractor shall perform non-recurring engineering studies and analyses to evaluate the viability of potential solutions to solve various technical problems or meet system requirements. These studies and analysis include the assessment of system and subsystem requirements;

development, analysis and evaluation of concepts, technologies, systems and subsystems; and development and examination of operational concepts and tactics. The contractor shall document results

(CDRL A002) and submitted as required by applicable task orders.

3.5.4 Prototypes

The contractor shall develop, operate, and maintain prototype, model, and mock-up systems, software applications, data models, and tools to determine optimal solutions to operational and functional requirements. The contractor shall support the building, production, fabrication, testing, evaluation, and operation of reduced and full-scale models, mock-ups, prototypes, production units, and research and development (R&D) test tools. The contractor shall develop schedules and implementation plans, including operational capability milestones, identification of technical approaches, and a description of anticipated prototype results. For any documentation (CDRL A002) required, the contractor shall develop and submit as specified by the task order.

3.5.5 Modeling and Simulation

The contractor shall provide the necessary personnel, equipment, and facilities to design, install, operate, maintain and support Modeling and Simulation (M&S) efforts. For any documentation (CDRL A002) required, the contractor shall develop and submit as specified by the task order.

3.5.6 Fabrication

The contractor shall support the fabrication and manufacturing of replacement parts and equipment for

Navy, Marine Corps and Joint ISR/IO fielded systems or platforms.

3.5.7 Installation

The contractor shall install hardware and software as required by applicable task orders. Installation may involve fabrication of mounts, brackets, and/or installation kits to include cabling, connections, and interconnecting devices. This includes the installation in accordance with PWS Para 6.2.2 for shipboard work and SPAWAR Shore Installation Process Handbook for shore work, and delivery of systems, including the development of installation and integration plans (CDRL A002), drawings (CDRL A004), technical change documentation and notices and procedures in support of these efforts.

When required, the contractor shall assist the Government in identifying all equipment and utilities required for installation at the installation site, including Government Furnished Equipment/Material

(GFE/GFM). The contractor shall assist the Government with determining the required equipment, utilities, and resources are available at the installation site. The contractor shall identify, plan, resource, and acquire Packaging, Handling, Storage and Transportation (PHS&T) requirements to maximize availability and usability of materiel and equipment to include support items when needed for training or other aspects of the mission.

3.5.8 Training

The contractor shall plan, resource, and implement a cohesive integrated strategy to train military and civilian personnel to maximize the effectiveness of the doctrine, manpower and personnel, to fight, operate, and maintain systems, software, and equipment throughout the life cycle. As part of the strategy, the contractor shall plan, resource, and implement management actions to identify, develop, and acquire

Training Aids, Devices, Simulations, and Simulators (TADSS) to maximize the effectiveness of the manpower and personnel to fight, operate, and sustain systems, software, and equipment at the lowest lifecycle cost.

The contractor shall support the development of training policy, processes, procedures, techniques, training devices, and equipment used to train civilian and military personnel to acquire, operate and support a system. This support includes individual and crew training, new equipment training, initial, formal, and on-the-job training, train-the-trainer, as well as training during system development to support the system test and evaluation. For any training documentation (CDRL A002) required, the contractor shall develop and submit as specified by the task order.

3.5.9 Test and Evaluation

The contractor shall define and develop test programs, plans, and procedures, conduct testing, and evaluate and document results. The contractor shall support testing requirements that may include:

Hardware and software component testing

Subsystem and system level development testing

System compatibility testing

Acceptance testing

Functional testing

Integration testing

Full qualification testing

Field-testing and evaluation

Environmental tests and stress screening

Electromagnetic interference testing, electromagnetic compatibility testing and TEMPEST

Regression Testing

Operational Assessments (OA)

Initial Operational Test and Evaluation (IOT&E)

Limited User Testing (LUT)

Human Systems Integration Testing

Production Verification Testing

Cyber Test & Evaluation

The contractor shall conduct testing in total or shall support Government test personnel as specified by applicable task orders. The contractor shall ensure that all hardware, software, test equipment, instrumentation, supplies, facilities, and personnel are available and in place to conduct or support each scheduled test.

The contractor shall review and evaluate Test Evaluation Master Plans, test plans, test procedures and test results as required by applicable task orders.

The contractor shall perform and/or apply engineering, scientific analytical disciplines and the development of all necessary test documentation, plans, change requests, specifications and reports to ensure that developed platforms, C5ISR and IT systems, and war-fighting capabilities have been properly tested and that joint interoperability requirements have been fully met at…