N65236-16-R-0026.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local t ime 12 Dec 2017

X

A X B X C

D

EX

X G F 169 - 182

183 - 201 X H 202 - 210 jessica.stogner@navy .mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

DO-A7 1 210

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N65236 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and see L-349 conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

JESSICA STOGNER 843-218-2136

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 2 3 - 9

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

10 - 92 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

94 - 95 X K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 96 - 99 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 100 - 113 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

114 - 167

PART II - CO NTRACT CLAUSES

US NAVY SPAWARSYSCEN ATLANTIC CHARLESTON

PO BOX 190022 2.0 CONTRACTS

843-218-6142

LACEY.FLINT@NAVY.MIL

NORTH CHARLESTON SC 29419-9022

843-218-6142

843-218-4918FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

08 Nov 2017

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N65236-16-R-0026

Section A - Solicitation/Contract Form

CEILING

The total contract ceiling under this solicitation is $898,000,000.00. This does not include the value for any extensions that may be issued in accordance with FAR Clause 52.217-8.

Note: Due to system limitations, the page count on the SF 33 is incorrect. The SF 33 should read that it is 1 of 208 pages.

Section B - Supplies or Services and Prices

ITEM

NO

SUPPLIES/SERVICES

Cyber Mission Engineering - CPFF

CPFF

Technical support services for Cyber Mission Engineering tasks in accordance with the Section C, Performance Work Statement (PWS).

Completion and LOE orders are allowed.

Fixed Fee %__________*

*Offeror insert proposed fixed fee percentage to be utilized in pricing task orders. The fixed fee for task orders shall not exceed this percentage. Offeror shall also indicate the fee application base (e.g., Total Cost less FCCM, etc.)

ESTIMATED COST

FIXED FEE

TOTAL ESTIMATED COST

PLUS FIXED FEE

EST

QUANTITY

UNIT

UNIT PRICE TOTAL AMOUNT

0002 1 Lot Cyber Mission Engineering - FFP Technical support services for Cyber Mission Engineering tasks in accordance with the Section C, Performance Work Statement (PWS).

Completion orders are allowed.

Profit _____%* *Offeror insert proposed profit percentage to be utilized in pricing task orders. The profit for task orders shall not exceed this percentage and shall be applied to labor costs only.

FFP

ITEM NO SUPPLIES/SERVICES MAX

UNIT UNIT PRICE MAX AMOUNT

0003 UNDEFINED

Cyber Mission Engineering – COST COST

Cost CLIN for travel and other ODCs in accordance with Section C, Performance Work Statement and L-329. *This CLIN is cost-only and the specific requirements will be priced at the task order level.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

MAX COST

0004 UNDEFINED

CDRLS -

Contract Data Requirements List (CDRLS), as identified in Section C, Performance Work Statement.

OPTION Option One - Cyber Mission Engineering -

CPFF

Technical support services for Cyber Mission Engineering tasks in accordance with the Section C, Performance Work Statement (PWS).

Completion and LOE orders are allowed.

Fixed Fee %__________*

*Offeror insert proposed fixed fee percentage to be utilized in pricing task orders. The fixed fee for task orders shall not exceed this

SUPPLIES/SERVICES

1002 1 Lot Option One - Cyber Mission Engineering - OPTION Technical support services for Cyber Mission Engineering tasks in accordance with the Section C, Performance Work Statement (PWS).

Completion orders are allowed.

Profit _____%* *Offeror insert proposed profit percentage to be utilized in pricing task

UNIT UNIT PRICE MAX AMOUNT

1003 UNDEFINED

OPTION Option One - Cyber Mission Engineering -COST

Cost CLIN for travel, and other ODCs in accordance with Section C, Performance Work Statement and L-329. *This CLIN is cost-only and the specific requirements will be priced at the task order level.

1004 UNDEFINED

Option One CDRLS - OPTION Contract Data Requirements List (CDRLS) CDRLS, as identified in

Section C, Performance Work Statement.

OPTION Cyber Mission Engineering - Six Mth Opt

CPFF

Option in accordance with 52.217-8 for six months.

Fixed Fee %__________*

*Offeror insert proposed fixed fee percentage to be utilized in pricing task orders. The fixed fee for task orders shall not exceed this

2002 1 Lot Cyber Mission Engineering - Six Mth Opt OPTION Option in accordance with 52.217-8 for six months.

Profit _____%* *Offeror insert proposed profit percentage to be utilized in pricing task

UNIT UNIT PRICE MAX AMOUNT

2003 UNDEFINED

OPTION Cyber Mission Engineering - Six Mth Opt COST

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.

2004 UNDEFINED

Cyber Mission Engineering - Six Mth Opt OPTION Option in accordance with 52.217-8 for six months.

CLAUSES INCORPORATED BY FULL TEXT

5252.211-9201 COMPLIANCE WITH SPECIFICATION (DEC 1999)

The effort required hereunder shall be in accordance with the specifications set forth herein and the offeror’s technical proposal _____*_____ which is incorporated herein by reference and made a part hereof. In the event any discrepancy between the Government’s specification and the Contractor’s proposal, the Government’s specification shall control unless otherwise noted herein.

*To be completed at time of award.

(End of clause)

5252.216-9200 PAYMENT OF FIXED FEE (COMPLETION TYPE) (JAN 1989)

FIXED FEE: $ ____*____ The Government shall make payment to the Contractor when requested as work progresses, but no more frequently than biweekly, on account of the fixed fee, equal to ____**____ percent of the amounts invoiced by the Contractor under the “Allowable Cost and Payment” clause hereof for the related period, subject to the withholding provisions of paragraph (b) of the “Fixed Fee” clause. In the event of discontinuance of the work in accordance with clause of this contract entitled “Limitation of ___***___,” the fixed fee shall be redetermined by mutual agreement equitably to reflect the diminution of the work performed; the amount by which such fixed fee is less than, or exceeds payments previously made on account of fee, shall be paid, or repaid by, the Contractor, as the case may be.

* To be determined at the task order level.

** Percentage rate of fee established in the task order.

*** “Cost” or “Funds” as appropriate; will be determined at the task order level.

5252.216-9205 FEE DETERMINATION AND PAYMENT (INDEFINITE DELIVERY TYPE

CONTRACTS) (APR 2000) (VARIATION)

(a) Types of Delivery or Task Orders.

Both level-of-effort and completion type orders may be issued under this contract. The Request for Quotation issued for each delivery or task order will set forth the type of order deemed appropriate by the Government. If the Contractor disagrees with the Government’s assessment, the Ordering Officer and the contractor shall attempt to resolve the matter through the negotiation process. Failing this, the matter will be referred to the Contracting Officer. If necessary, a final decision shall be made in accordance with the FAR 52.233-1 “Disputes” clause. The Contracting Officer’s determination will govern the type of order, pending an appeal pursuant to the “Disputes” clause. The contractor will use his best efforts to work on the order until the dispute is resolved.

(b) Fixed Fee Pool.

The fixed fee pool consists of the total fixed fee of the contract AND includes the total fee to be paid to the prime contractor and all subcontractors. SUBCONTRACTOR FEE WILL NOT BE BILLED AS A SEPARATE DIRECT

COST ON THE VOUCHER SUBMITTED BY THE CONTRACTOR TO THE GOVERNMENT, BUT WILL BE

PAID TO THE SUBCONTRACTOR BY THE PRIME CONTRACTOR FROM THE FEE BILLED FROM THE

FIXED FEE POOL.

(c) Computation of Fee.

The percentage of the fee applicable to orders will be the same as the percentage of the fee established in the contract. However the total fee paid under the contract for a year of performance will not exceed the total fixed fee amount for the current year of performance.

(d) Fee on Modifications to Term Type (Level-of-Effort) Delivery or Task Orders.

If the hours for a particular delivery or task order are insufficient to complete performance under the order, the government may elect to increase the hours by written modification. This increase in cost associated with the increase in hours will be fee bearing at the same percentage of fee established in the basic contract. If the hours prove to be in excess of that necessary to complete performance under this order, the government shall decrease the hours by written modification. The fee associated with the decrease in hours will be reduced by the percentage of fee established in the basic contract. Estimated cost will be increased/decreased as applicable.

(e) Fee on Modifications to Completion Type Delivery or Task Orders.

If the task(s) required under a particular delivery or task order cannot be completed within the negotiated estimated cost (an overrun situation), the government may elect to increase the estimated cost to complete the effort with no additional fee allocation.

If the task(s) required under the order is completed and the cost is less than that negotiated (underrun), the contractor shall be entitled to full payment of the fixed fee specified in the order. Excess costs shall be deobligated by modification to the delivery order prior to contract closeout.

(f) Modifications to the Basic Contract.

If the contracting officer determines, for any reason, to adjust the contract amount or the estimated total hours, such adjustments shall be made by contract modification. Any increase will be fee bearing, except cost overruns on completion type orders, at the percentage of fee established in the basic contract.

The estimated cost of the contract may be increased by written modification, if required, due to cost overruns. This increase in cost is not fee bearing and no additional hours will be added to the total estimated hours under the contract.

(g) Payment of Fee.

The Government shall pay fixed fee to the contractor on each delivery order at the percentage rate of fee established in the basic contract subject to the contract’s “Fixed Fee” clause, provided that the total of all such payments shall not exceed eighty-five percent (85%) of the fixed fee specified under each applicable delivery order, unless waived.

In accordance with the provisions of paragraphs (d) and (e) of this clause, any balance of fixed fee shall be paid to the contractor, or any overpayment of fixed fee shall be repaid by the contractor, at the time of final payment.

(h) Closeout.

Delivery or task orders will be closed out on an individual basis, upon agreement of final indirect rates for the period of performance of the applicable delivery or task order. The contractor shall forward the final voucher directly to the cognizant DCAA for final audit. DCAA will forward the voucher and the final audit to the cognizant ACO (see block 6 of the basic contract), who will process it for final payment and submit it to the paying office.

Section C - Descriptions and Specifications

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…