W911SR-17-R-0002.pdf

DRAFT

CODE

(Hour)

PAGE(S)

until 04:00 PM local time 02 Dec 2016

X

A X B X C X D

EX

X

G F 100 - 109

110 - 128 X H 129 - 137

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-C9 1 137

(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.

W911SR 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 0 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 fbo.gov conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 17

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

18 - 45

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

47 - 48 49 - 50

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 51 - 53 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 54 - 63 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 - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

64 - 98

PART II - CONTRACT CLAUSES

USA CONTRACTING CMD-APG. - W911SR

EDGEWOOD CONTRACTING DIVISION

E4215 AUSTIN ROAD

ABERDEEN PROVING GROUND MD 21010-5401

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

02 Nov 2016

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

W911SR-17-R-0002

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 UNDEFINED Job RDT&E Work for Months 1-12

CPAF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance with Section C, paragraphs C.3.1 through C.3.1.8, C.3.2 through C.3.2.5 and C.4 through C.8 FOB: Destination

MAX COST

BASE FEE

SUBTOTAL MAX COST + BASE

MAX AWARD FEE

TOTAL MAX COST + FEE

UNIT UNIT PRICE MAX AMOUNT

0002 UNDEFINED Job O&M Work for Months 1-12

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance with Section C, paragraphs C.3.2, C.3.2.6, C.3.2.7 and C.4 through C.8

FIXED FEE

UNIT UNIT PRICE MAX AMOUNT

0003 UNDEFINED Job PROC Work for Months 1-12

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance with Section C, paragraphs C.3.2, C.3.2.8 and C.4 through C.8

UNIT UNIT PRICE MAX AMOUNT

0004 UNDEFINED Job FMS Work for Months 1-12

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance with Section C, parapgraphs C.3.2, C.3.2.10 and C.4 through C.8

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Accounting for Contract Services-NSP

The contractor shall perform manpower reporting required for performance of this contract (including all subcontracted manpower) required for performance of this contract as stated in Local Clause ACC-APG 5152.237-4900 ACCOUNTING FOR

CONTRACT SERVICES REQUIREMENT – ENTERPRISE-WIDE

CONTRACTOR MANPOWER REPORTING APPLICATION (June 2013).

Included in Section C. Not Separately Priced.

NET AMT

Contract Data Requirements-NSP

The contractor shall provide all data in accordance with the Contract Data Requirements List Section J attachment, DD Form 1423. Not Separately Priced.

UNIT UNIT PRICE MAX AMOUNT

1001 UNDEFINED Job RDT&E Work for Months 13-24

CPAF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance with Section C, paragraphs C.3.1 through C.3.1.8, C.3.2 through C.3.2.5 and C.4

UNIT UNIT PRICE MAX AMOUNT

1002 UNDEFINED Job O&M Work for Months 13-24

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance

UNIT UNIT PRICE MAX AMOUNT

1003 UNDEFINED Job PROC Work for Months 13-24

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance

UNIT UNIT PRICE MAX AMOUNT

1004 UNDEFINED Job FMS Work for Months 13-24

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance contract as stated in Local Clause ACC-APG 5152.237-4900 ACCOUNTING FOR

CONTRACT SERVICES REQUIREMENT – ENTERPRISE-WIDE

CONTRACTOR MANPOWER REPORTING APPLICATION (June 2013).

UNIT UNIT PRICE MAX AMOUNT

2001 UNDEFINED Job RDT&E Work for Months 25-36

CPAF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance with Section C, paragraphs C.3.1 through C.3.1.8, C.3.2 through C.3.2.5 and C.4

UNIT UNIT PRICE MAX AMOUNT

2002 UNDEFINED Job O&M Work for Months 25-36

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance

UNIT UNIT PRICE MAX AMOUNT

2003 UNDEFINED Job PROC Work for Months 25-36

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance

UNIT UNIT PRICE MAX AMOUNT

2004 UNDEFINED Job FMS Work for Months 25-36

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance contract as stated in Local Clause ACC-APG 5152.237-4900 ACCOUNTING FOR

CONTRACT SERVICES REQUIREMENT – ENTERPRISE-WIDE

CONTRACTOR MANPOWER REPORTING APPLICATION (June 2013).

UNIT UNIT PRICE MAX AMOUNT

3001 UNDEFINED Job RDT&E Work for Months 37-48

CPAF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance with Section C, paragraphs C.3.1 through C.3.1.8, C.3.2 through C.3.2.5 and C.4

UNIT UNIT PRICE MAX AMOUNT

3002 UNDEFINED Job O&M Work for Months 37-48

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance

UNIT UNIT PRICE MAX AMOUNT

3003 UNDEFINED Job PROC Work for Months 37-48

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance

UNIT UNIT PRICE MAX AMOUNT

3004 UNDEFINED Job FMS Work for Months 37-48

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance contract as stated in Local Clause ACC-APG 5152.237-4900 ACCOUNTING FOR

CONTRACT SERVICES REQUIREMENT – ENTERPRISE-WIDE

CONTRACTOR MANPOWER REPORTING APPLICATION (June 2013).

UNIT UNIT PRICE MAX AMOUNT

4001 UNDEFINED Job RDT&E Work for Months 49-60

CPAF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance with Section C, paragraphs C.3.1 through C.3.1.8, C.3.2 through C.3.2.5 and C.4

UNIT UNIT PRICE MAX AMOUNT

4002 UNDEFINED Job O&M Work for Months 49-60

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance

UNIT UNIT PRICE MAX AMOUNT

4003 UNDEFINED Job PROC Work for Months 49-60

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance

UNIT UNIT PRICE MAX AMOUNT

4004 UNDEFINED Job FMS Work for Months 49-60

CPFF

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish the work outlined in the Performance Work Statement (PWS) specifically in accordance contract as stated in Local Clause ACC-APG 5152.237-4900 ACCOUNTING FOR

CONTRACT SERVICES REQUIREMENT – ENTERPRISE-WIDE

CONTRACTOR MANPOWER REPORTING APPLICATION (June 2013).

NOTE

B.1 Reserved for direct rate ceilings per order period

B.2 MINIMUM AND MAXIMUM QUANTITIES FOR SINGLE AWARD CONTRACTS

As referred to in paragraph (b) of FAR Clause 52.216-22, “Indefinite Quantity” of this contract, the contract minimum quantity is a total of $2,500.00 to the awardee. The award of Task Order 0001 will satisfy the guaranteed minimum. The maximum quantity is the total “not to exceed” amount of $45,000,000.00 for the cumulative sum of all orders to be issued under this IDIQ contracting vehicle, including all option ordering periods. The maximum quantity may only be exceeded with prior written approval of the Procuring Contracting Officer.

MINIMUM MINIMUM MAXIMUM MAXIMUM

QUANTITY AMOUNT QUANTITY AMOUNT

$2,500.00 $45,000,000.00

Section C - Descriptions and Specifications

C.1.0 SCOPE

The scope of this effort includes development and integration of new capability as well as upgrade, modernization and sustainment of existing capability for the Joint Effects Model (JEM). The Contractor shall also provide support to JEM events including but not limited to ongoing JEM Government Developmental Testing and Evaluation (DT&E) and Operational Test and Evaluation (OT&E). Operational Assessments (OAs), Integrated Tests, User Feedback Events (UFEs), Technical Reviews and Exchanges will also be part of this effort.

C.1.1 Background The current JEM capability is developed and fielded in two increments, which will be managed under one JEM contract as two separate baselines with a significant amount of common code.

C.1.1.1 JEM Increment 1 (Incr 1) JEM Increment 1 (Incr 1) is based on requirements contained in the JEM Operational Requirements Document (ORD) approved in May 2004 by the Joint Requirements Oversight Council (JROC). The JEM acquisition began under the Requirements Generation System and was switched to the Joint Capabilities Integration Development System (JCIDS). The JEM ORD describes the JEM incremental development strategy and contains the requirements for all three planned JEM increments. The JEM Incr 1 Capability Production Document (CPD) was approved in January 2007. The JEM Incr 1 Standalone variant attained Full Rate Production (FRP) in May 2008.

The JEM Incr 1 Command and Control (C2) variant received its Full Deployment Decision (FDD) in June 2010.

JEM Incr 1 fielding, which began in 2008, includes Foreign Military Sales (FMS) to allied Government militaries.

C.1.1.2 JEM Increment 2 (Incr 2) JEM Incr 2 is fielded under the JCIDS Information Technology Box (IT-Box) Construct. The Information Systems Initial Capability Document (IS ICD) Performance Specification (PSPEC) was approved by the JROC in June 2014.

The JEM Incr 2 program achieved approval for Build Decision 1 in September 2014 and began limited fielding of the standalone product in the 2QFY16. Under the JEM IT-Box, requirements documents have been divided into five Requirements Definition Packages (RDPs). JEM Incr 2 may include up to five (5) RDPs. JEM RDP 1 and JEM RDP 2 are currently under development. [For reference only: JEM RDP 1 - Baseline Capabilities (document approved by Protection Functional Capability Board). JEM RDP 2 – Command and Control (C2) Integration. JEM RDP 3 - Analytical Support. JEM RDP 4 – Emerging Science and Technology Capabilities. JEM RDP 5 - Modernization and Sustainment.]

C.1.2 Objective The objective of this contract is the development and integration of new capability as well as the upgrade, modernization and sustainment of JEM software, leveraging reusable code across the multiple baselines. This contract will merge two separate software versions that are being modernized and developed.

C.2.0 APPLICABLE DOCUMENTS (Table 1) The Government will use Project Forge https://project.forge.mil/sf/projects/jem-follow-on to host documents listed in C.9.0 that don’t have a URL and are not available on the web. For the purposes of this Performance Work Statement (PWS), “Required”, as it applies to this paragraph, means that the requirements contained in the directly cited document are contractually applicable to the extent specified. If a document reference does not indicate the specific paragraph as being applicable, then the document is applicable in its entirety. The term “For guidance only” means the document is not contractually applicable and is provided for guidance and information only. The documents cited in Table 1 are “required” unless specifically identified as “for guidance only”. In the event of a conflict between the documents referenced herein and the contents of this PWS, the PWS shall take precedence.

C.3.0 REQUIREMENTS

The Contractor, as an independent Contractor and not as an agent of the Government, shall furnish the necessary resources (except those specifically designated as Government-furnished) to perform the following work.

C.3.1 Software Engineering

C.3.1.1 Software Development and Technical Documentation Research Development Test and Evaluation

(RDT&E)

C.3.1.1.1 JEM Common System Allocated Baseline Software Requirements.

Acceptable JEM software shall meet the following requirements:

a. The Contractor shall develop, adapt and modernize software that meets the requirements as defined in the JEM

Performance Specification (PSPEC), PRF JPM-IS-001.

b. The Contractor shall develop, adapt and modernize the JEM application modeling framework to:

i. Allow multiple components to collaborate on the execution of a Chemical, Biological, Radiological, and Nuclear (CBRN) scenario and generate applicable output products.

ii. Provide a scalable modeling architecture suitable for a single user as well as cloud based multi-user support.

iii. Provide efficient integration of new or updated components.

c. The Contractor shall maximize reuse of software source code across allocated baselines.

d. The Contractor shall develop, adapt and modernize a scalable web application, in which the software:

i. Allows for a user to be authenticated.

ii. Allows for concurrent multi-user functionality.

iii. Provides for efficient integration of new or updated components.

iv. Supports Ozone Widget Framework (OWF) and inter-widget communication with Joint Warning and

Reporting Network (JWARN), Command and Control (C2), and other CBRN Community of Interests (COI) widgets.

e. The Contractor shall develop, adapt and modernize a stand-alone local client installed application with similar capabilities as the web application that:

i. Provides users continued access to JEM2 functionality that does not rely on internet/network connectivity.

ii. Allows for single user concurrent modeling functionality.

iii. Provides for efficient integration of new or updated components.

iv. Supports Ozone Widget Framework (OWF) and inter-widget communication with Joint Warning and

Reporting. Network (JWARN), Command and Control (C2), and other CBRN Community of Interests (COI) widgets.

f. The Contractor shall develop, adapt and modernize JEM CBRN modeling web services that:

i. Support information sharing among the CBRN communities.

ii. Represent the interests of the COI to other domains and COIs.

iii. Support backward compatibility with fielded versions of JWARN.

g. The Contractor shall develop, adapt and modernize CBRN hazard plots and legends that can be shared with

Command and Control (C2) systems and exported to other formats such as ArcGIS Desktop, and Google mapping tools as defined in the JEM PSPEC.

h. The Contractor shall develop, adapt and modernize software that can operate on multiple hardware and operating systems as required; currently, JEM can be run on Windows, Solaris and Linux operating systems.

i. The Contractor shall develop, adapt and modernize software that complies with the Net-Ready Key Performance Parameter (NR-KPP) as defined in the Net-Ready Key Performance Parameter (NR-KPP) per the Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6212.01F.

j. The Contractor shall develop, adapt and modernize software that complies with communication and software standards, as defined in the Version Description Document for The DoD Architecture Framework (DoDAF) and DoDAF Meta Model (DM2) Version 2.02and the DoD Directive 8100.02 Use of

Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid.

C.3.1.1.2 JEM 2.0 System Allocated Baseline Software Requirements Acceptable JEM 2.0 software shall meet the following additional requirements:

a. The Contractor shall develop, adapt and modernize the modeling related software components to ensure that they are Common CBRN Model Interface (CCMI) compliant and compatible with the CCMI guidance and related blueprints as described in JEM Common Chemical, Biological, Radiological, and Nuclear (CBRN) Model Interface (CCMI) Guidance Documentation.

b. The Contractor shall develop, adapt and modernize the modeling software components to ensure they can run within the CCMI Auto-generated Test Toolkit (CATT).

c. The Contractor shall ensure sufficient modeling software component test coverage as described in the CCMI guidance in accordance with (IAW) ELIN A021.

d. The Contractor shall execute and document verification and validation tests and the results thereof and must provide the tests both as CATT runnable scenarios and, wherever possible, as JEM 2.0 problem set exports IAW ELIN A022 - Verification and Validation Report (V&V Report).

C.3.1.2 JEM Incremental Capability Requirements (RDT&E) As part of JEM modernization, the Contractor shall conduct development support on the following integration efforts IAW the PWS.

C.3.1.2.1 CBRN IS Integration CBRN IS is an emerging enterprise framework that provides JPEO CBD capabilities in a cloud environment. The Contractor shall support the development, integration, test, and modernization of CBRN IS capabilities through implementation and adherence to a common architecture that produces interoperable components. The Contractor shall develop capabilities that adhere to the CBRN IS framework such as a web application that allows individual capabilities to communicate through documented, pre-defined interfaces. The Contractor shall adhere to development processes and procedures that produce capabilities that are compatible with other CBRN IS components and utilize Single Sign On (SSO), a shared database, an Extensible Messaging and Presence Protocol (XMPP) server, and other enterprise features.

C.3.1.2.2 JWARN Integration In support of JEM interoperability and the CBRN IS enterprise implementation, the Contractor shall support the development, integration, test, and modernization of JWARN capabilities through implementation and adherence to a common architecture that produces interoperable components. The Contractor shall adhere to development processes and procedures that produce capabilities that are compatible with JWARN components that utilize Single Sign On (SSO), a shared database, an Extensible Messaging and Presence Protocol (XMPP) server, and other enterprise features.

C.3.1.2.3 Bio-Surveillance Portal Integration In support of JEM interoperability and the CBRN IS enterprise implementation, the Contractor shall support the development, integration, test, and modernization of the Bio-Surveillance Portal (BSP) capabilities through implementation and adherence to a common architecture that produces interoperable components. The Contractor shall adhere to development processes and procedures that produce capabilities that are compatible with BSP components that utilize Single Sign On (SSO), a shared database, an Extensible Messaging and Presence Protocol (XMPP) server, and other enterprise features.

C.3.1.2.4 Science and Technology Transition and Integration The Joint Science and Technology Office (JSTO) and the Defense Threat Reduction Agency (DTRA) provide the majority of the mature technology that transitions into JEM. The Contractor shall support the development, prototyping, integration, test, and transition of science and technology capabilities into JEM through implementation and adherence to the JEM software architecture. The Contractor shall modify science and technology, prototype, and test components to produce mature capability that adheres to the CCMI and integrates into the baseline JEM product with a minimum of development. The Contractor shall perform and document model verification and validation to ensure that the transitioned technologies are scientifically valid and produce results that can be accredited for use in an operational environment.

C.3.1.3 Fielded System Upgrade and Modernization (RDT&E)

C.3.1.3.1 Fielded System Upgrade Support The Contractor shall upgrade and modernize the fielded JEM software product. Software upgrades shall be performed in accordance with the most recent product baseline established by and approved by the Government.

C.3.1.3.2 Government Configuration Management System Support The Contractor shall follow all procedures in JPM IS SOPs listed in paragraph C.9.0 Applicable Documents. The Contractor shall participate in a weekly Configuration Control Board (CCB) SOP 12 teleconference facilitated by the Government.

C.3.1.4 Program Change Report (PCR) Process Support (RDT&E)

In adherence with the overarching JPM IS Configuration Management effort, the Contractor shall support the Program Change Report (PCR) Change Control Process, per the JPM IS Program Change Report (PCR) Change Control Process, SOP 10.

C.3.1.5 Software Delivery (RDT&E)

In delivering the software, the Contractor shall adhere to the JPM IS Software Deliveries Process, SOP 31 (20 May 2015).

C.3.1.5.1 Formal In-Cycle Deliveries The Contractor shall make Formal In-Cycle Deliveries to include delivery of Software Items and Technical Documentation. In-cycle deliveries are tied to Government milestone events such as formal Testing and Evaluation leading to Fielding Decisions.

C.3.1.5.1.1 Formal in-cycle deliveries shall include all components of the software, even if no changes have been made to specific components.

C.3.1.5.1.2 As part of a Formal In-Cycle Delivery, the Contractor shall create and deliver the following software and technical documentation:

C.3.1.5.1.2.1 The Contractor shall prepare Software Product Specification (SPS), IAW ELIN A008.

C.3.1.5.1.2.2 The Contractor shall prepare Software Version Description (SVD), IAW ELIN A011.

C.3.1.5.1.2.3 The Contractor shall prepare Software Test Description (STD), IAW ELIN A016.

C.3.1.5.1.2.4 The Contractor shall prepare Software Test Report (STR) as a record of the testing performed on a Computer Software Configuration Item (CSCI), a software system or subsystem, or other software-related item, IAW ELIN A018.

C.3.1.5.1.2.5 The Contractor shall prepare System Administrator Manual (SAM) IAW ELIN A014.

C.3.1.5.1.2.6 The Contractor shall prepare Software User Manual (SUM) IAW ELIN A015.

C.3.1.5.1.2.7 The Contractor shall prepare Software Resources Data Reporting (SRDR) IAW ELIN A006.

C.3.1.5.2 Technical Document Changes The Contractor shall provide updates to the following JEM technical documentation due to changes in the software to maintain the accuracy of the document as set forth below:

C.3.1.5.2.1 The Contractor shall prepare Interface Design Document (IDD) IAW ELIN A012.

C.3.1.5.2.2 The Contractor shall prepare Software Programmer’s Guide (SPG) IAW ELIN A013.

C.3.1.5.2.3 The Contractor shall prepare Engineering Notebooks (ENs) IAW ELIN A020.

C.3.1.5.3 Baseline Management The Contractor shall maintain the currency and accuracy of the allocated and product baselines. The Contractor shall establish and follow definitive processes that identify how the baseline will be managed or maintained.

C.3.1.5.3.1 Baseline Traceability

The Contractor shall maintain documented traceability between the functional, allocated, and product baselines for all software items. Traceability shall include all derived component-level requirements, including those typically included in a separate Software Requirements Specification (SRS), and shall provide forward and backward traceability between all requirements, system components, and associated design documentation (e.g. IDD, SDD, Detail Specs). Traceability shall also include rationale and heritage information via inclusion of Requirement ID, Rationale, Traced From and Owner metadata as detailed in MIL-HDBK-520A Table I, as well as documentation of (or direct links to documentation of) all historical approved changes to the Contractor-managed requirements.

C.3.1.5.3.2 The Contractor shall prepare Software Requirements Specification (SRS) IAW ELIN A009.

C.3.1.5.3.3 Software Allocation The Contractor shall categorize all software as application software and support software categories. Each category shall comprise a Computer Software Configuration Items (CSCI) and may further be subdivided into smaller CSCIs if the CSCI is complex, e.g., functional, allocated and product baselines. The product baseline items could be further broken down into developmental, test and production software baselines. The CSCIs shall be documented in detail in the Software Design Description (SDD). The Contractor shall deliver a SDD for JEM that details the design descriptions of the computer software configuration items, database design descriptions, interfaces among the software units/segments, etc. CSCIs shall be uniquely named and/or numbered and identify the functional characteristics (for example, its purpose and use) and physical characteristics. CSCIs shall include the JEM, and products that are used in the development of JEM, which should be controlled. The Contractor shall prepare and submit the SDD IAW ELIN A010.

C.3.1.5.4 Formal Out-of-Cycle Deliveries The Contractor shall provide a software upgrade to fix each designated high priority 1 and 2 PCR(s) and also correct the corresponding technical documentation. Typically, a patch will include only those files that have been changed and can be installed over the top of an existing program, but this will depend on the nature of the patch and the detailed instructions as provided by the Government.

C.3.1.5.4.1 As part of a Formal Out-of-Cycle Delivery, the Contractor shall prepare and deliver the following software and technical documentation. In addition, during contract performance, the Contractor shall perform updates for the same software and technical documentation:

C.3.1.5.4.1.1 The Contractor shall prepare Software Product Specification (SPS), IAW ELIN A008.

C.3.1.5.4.1.2 The Contractor shall prepare Software Version Description (SVD), IAW ELIN A011.

C.3.1.5.4.1.3 The Contractor shall prepare Software Test Description (STD), IAW ELIN A016.

C.3.1.5.4.1.4 The Contractor shall prepare Software Test Report (STR) IAW ELIN A018.

C.3.1.5.5 Technical Document Changes - Software The Contractor shall provide updates to the following JEM technical documentation due to changes in the software to maintain the accuracy of the document:

C.3.1.5.5.1 The Contractor shall prepare Engineering Notebooks (ENs) IAW ELIN A020.

C.3.1.5.5.2 The Contractor shall prepare System Administrator Manual (SAM) IAW ELIN A014.

C.3.1.5.5.3 The Contractor shall prepare Software User Manual (SUM) IAW ELIN A015.

C.3.1.5.5.4 The Contractor shall prepare Interface Design Document (IDD) IAW ELIN A012.

C.3.1.5.6 Engineering Delivery The Contractor shall provide Engineering Deliveries at the request of the Government at a regular or irregular cycle to support testing, review and in-progress Government feedback. These deliveries will be requested to support the program development effort to meet emerging requirements, and integration efforts. In general, Engineering Deliveries are not fielded.

C.3.1.5.6.1 Engineering Delivery Documentation

As part of an Engineering Delivery, the Contractor shall prepare and deliver the following software and technical documentation. In addition, during contract performance, the Contractor shall perform updates for the same software and technical documentation:

C.3.1.5.6.1.1 The Contractor shall prepare Software Version Description (SVD), IAW ELIN A011.

C.3.1.5.6.2 Software Change Documentation The Contractor shall prepare the following JEM technical documentation when software changes make document updates necessary to maintain the accuracy of the documents:

C.3.1.5.6.2.1 The Contractor shall prepare System Administrator Manual (SAM) IAW ELIN A014.

C.3.1.5.6.2.2 The Contractor shall prepare Software User Manual (SUM) IAW ELIN A015.

C.3.1.5.6.2.3 The Contractor shall prepare Interface Design Document (IDD) IAW ELIN A012.

C.3.1.5.7 Informal Engineering Delivery The Contractor shall provide Informal Engineering Deliveries at the request of the Government for prototyping of new capability, and early integration and interoperability testing. Informal feedback will include emails, meetings, and discussions to reduce risk in the development process. Informal Engineering Deliveries will not be tracked in the Government configuration management system. All documentation delivered with an Informal Engineering Delivery will be considered to be drafts. At all Informal Engineering Deliveries, the Contractor shall coordinate documents upon the request of the Government when scheduling the delivery.

C.3.1.6 Cybersecurity (RDT&E) The Contractor shall deliver software that is secure and able to be accredited for use on service and joint networks.

The Contractor shall ensure that security requirements are addressed in software design and development. The Contractor shall conduct security scans, monitor emerging DISA Information Assurance Vulnerability Management (IAVM) notifications, document vulnerabilities, correct vulnerabilities, and document the resolution or mitigation of vulnerabilities in conjunction with JPM IS Information Assurance Vulnerability Management (IAVM) Support Process, SOP 37 and IAW JPM IS Program Change Report (PCR) Change Control Process, SOP 10. The Contractor shall support the Government’s effort to accomplish JEM cybersecurity accreditation by assessing the validity of vulnerabilities identified during formal Government accreditation testing, recommending corrective actions to resolve or mitigate vulnerabilities, and estimating the level of effort and time required to resolve valid vulnerabilities IAW JPM IS SOP 10.

C.3.1.6.1 Maintain Cybersecurity Baseline Integrity The Contractor shall demonstrate compliance with Department of Defense Instruction (DoDI) 8500.01 (Cybersecurity) and Department of Defense Instruction (DoDI) 8510.01 (Risk Management Framework (RMF) for DoD Information Technology (IT), the Contractor shall ensure that the addition of software developed under this PWS does not compromise the security posture of the JEM software. Any Category 1 and Category 2 findings shall be considered a compromise of the security posture of the JEM software. Category definitions shall be governed by DoDI 8510.01, the DISA Information Assurance Vulnerability Management process, and DISA benchmarks for the JEM software, and DISA Security Technical Implementation Guides (STIGs) and Security Requirements Guides (SRGs).

C.3.1.6.2 Cybersecurity Implementation Plan The Contractor shall implement Government IA strategies and a Government validation plan consistent with JEM’s DoD Information Assurance Certification and Accreditation Process (DIACAP) Implementation Plan (DIP).

C.3.1.6.3 Cybersecurity Control Testing and Validation The Contractor shall demonstrate compliance with the applicable Cybersecurity controls through performance of a Contractor Cybersecurity Self-Assessment. The Contractor shall evaluate each software end-item against the applicable Security Technical Implementation Guides (STIGs) or checklists as provided in the DIP. Additionally, for STIGs or checklists that are supported by DISA approved software automated test tools, the Contractor shall deliver the test reports generated by the test tools. The Contractor shall deliver test reports for STIGs or checklists supported by automated test tools IAW ELIN A019, Information Assurance Test Tool Reports (IATTRs).

C.3.1.7 System Test and Evaluation (RDT&E) The Contractor shall conduct or support system test and evaluation as defined below.

C.3.1.7.1 On-Going Developmental Test and Evaluation Support The Contractor shall support the Government with any on-going Developmental Testing (DT) consistent with JEM’s Integrated Master Schedule (IMS). On-going DT events shall include a comprehensive evaluation to ensure the system meets all specifications and operational requirements as defined in the current JEM Test and Evaluation Master Plan (TEMP). Upon Government request, the Contractor’s on-going DT support may also include technical Subject Matter Expert (SME) support during test events, resolution of SPR deficiencies, and systems operation and sustainment during DT&E events in order to achieve Government acceptance of the Contractor’s delivered product.

The Contractor shall provide on-site technical support for DT. Any deficiencies identified by the Government during on-going DT shall be resolved by the Contractor in accordance with the JPM IS Program Change Report (PCR) Change Control Process, SOP 10.

C.3.1.7.2 Independent Operational Test and Evaluation Support The Contractor shall support the Government with Independent Operational Test & Evaluation (IOT&E). IOT&E support shall include Contractor technical subject matter expert (SME) support, resolution of SPR deficiencies, and on-site IOT&E support at a Government system site location.

C.3.1.7.3 Follow-on Operational Test and Evaluation Support The Contractor shall support the Government with Follow-on Operational Test & Evaluation (FOT&E). FOT&E support shall include Contractor technical subject matter expert (SME) support, resolution of SPR deficiencies, and on-site FOT&E support at a Government system site location.

C.3.1.8 Materials and Equipment (RDT&E)

As required and as approved by the Government, the Contractor shall purchase materials and equipment under the performance of this Contract.

C.3.2 Program Management (RDT&E, O&M, PROC, FMS)

The Contractor shall provide program management support to plan and execute all work required under this PWS and Contract Data Requirement List (CDRLs). The Contractor shall ensure all work conducted under this PWS is planned and executed in a manner that will achieve cost, schedule, and performance objectives. The Contractor shall provide the Government with Conference Agendas, Reports and Record of Meeting / Minutes IAW ELIN A023.The Contractor shall use the COR as the initial Point of Contact (POC). However, only the Contracting Officer has the authority to make changes to this contract.

C.3.2.1 Contract Work Breakdown Structure The Contractor’s cost and performance management approach shall be documented in a Contract Work Breakdown Structure (CWBS). The CWBS shall be created in accordance with MIL-HDBK-881 and shall contain detail commensurate with the work to be performed under this PWS. The CWBS shall be revised post award, if required by the Government. The Contractor shall prepare and deliver to the Government a Contract Work Breakdown Structure (CWBS) IAW ELIN A002.

C.3.2.2 New Development (RDT&E)

C.3.2.2.1 Systems Engineering The Contractor shall establish and maintain a Systems Engineering (SE) program IAW the Government Systems Engineering Plan (SEP). The Contractor shall prepare and deliver to the Government a Systems Engineering Management Plan (SEMP) that shall be approved by the Government IAW ELIN A003. The Contractor shall also consider software and network-ready requirements when developing the SEMP. The approved SEMP shall serve as the baseline for all Contractor systems engineering activities.

C.3.2.2.2 Software Development Approach The Contractor shall define and document an Agile software development approach, including tools used to facilitate a development process, which is appropriate for the work to be performed under this PWS and the IT Box construct, and delivers an incrementally developed field-able product. The Contractor shall document this approach in a Software Development Plan (SDP) consistent with the terms of this PWS and IAW ELIN A004, and in an Agile Software Metrics Report (ASMR) IAW ELIN A024. The Contractor shall perform all applicable work in accordance with the Contractor’s Government-approved SDP. The Contractor shall ensure that the components developed do not contain any US-only information that cannot be shared with partner nations as part of an FMS case.

C.3.2.2.3 Software Test Plan The Contractor shall prepare and deliver a Software Test Plan (STP) that describes the plans for testing of Computer Software Configuration Items (CSCIs), software system or subsystem, or other software-related items, IAW ELIN A017.

C.3.2.3 Exercise and Demonstration Support (RDT&E)

The Contractor shall provide technical and engineering expertise to demonstrate the JEM system.

C.3.2.4 Meetings and Reviews (RDT&E)

C.3.2.4.1 Start of Work Meeting The Contractor shall attend a Post Award Meeting with the Government Program Office and contracting representatives. The Post Award Meeting will be scheduled by the Procurement Contracting Officer (PCO) in conjunction with the Program Office within 30 days after contract award. The Post Award Meeting will be held at SPAWAR San Diego, CA.

C.3.2.4.2 Periodic Work Planning and Scheduling Meetings The Contractor shall participate in Periodic Work Planning and Scheduling Meetings with the Government Program Office and Government Contracting Representatives. The first Periodic Work Planning and Scheduling Meeting will be scheduled by the Program Office within 30 days of contract award. Periodic Work Planning and Scheduling Meetings may be held in conjunction with other meetings and reviews or scheduled independently no less than six

(6) months apart. Depending on the content to be discussed and resolved, the Work Planning and Scheduling Meeting may be held at SPAWAR San Diego (CA), the Contractor's facility, or via teleconference. The understanding and commitments agreed upon during the Periodic Work Planning and Scheduling Meetings, or specific clarification initiated by the Government to the Contractor, will be detailed in a Technical Instruction (TI) provided to the Contractor by the Government. A TI template is provided by reference in Other Government Documents, C.9.7

C.3.2.4.3 In Process Review (IPR) The Contractor shall attend program status updates at annual In Process Reviews (IPRs) in or around San Diego, CA at a Government facility. Upon the Government’s request, additional IPRs may be scheduled if critical issues arise or significant events or changes occur. In preparation of any IPR, the Contractor shall provide briefing material and presentation slides IAW ELIN A001.

C.3.2.4.4 Technical Interchange Meeting (TIM) The Contractor shall conduct a TIM via teleconference on a weekly basis to discuss technical questions/concerns with the Government. In accordance with CDRL A023 the Contractor shall provide meeting minutes that describes the items discussed as well as any resultant Government or Contractor actions from the TIM.

C.3.2.5 Reporting (RDT&E)

C.3.2.5.1 Monthly Status Report On a monthly basis, the Contractor shall deliver a Monthly Status Report (MSR) that briefly discusses upcoming meetings, deliveries, travel, activities accomplished, plan for the next month, new issues, and current issues. The Contractor shall provide all monthly status reports IAW ELIN A005.

C.3.2.5.2 Integrated Master Schedule Report Within the IMS, the Contractor shall describe the planned events and milestones, activities, and exit criteria, which shall directly relate to specific accomplishments. The Contractor shall provide traceability of all critical or high risk tasks.

C.3.2.5.3 Integrated Master Plan / Integrated Master Schedule (IMP/IMS) The Contractor shall develop and deliver the IMP and IMS, IAW the DoD IMP and IMS Preparation and User Guide. The IMP shall show the sequence of the Contractor’s planned effort to complete all items listed in this PWS.

The IMP shall provide a hierarchical, event-based plan that contains the following: events, significant accomplishments, and entry and exit criteria. The IMP shall not include any dates or durations. Both the IMP and IMS shall be delivered IAW ELIN A007. The Contractor’s IMS shall be based on major dates and timeframes included in the solicitation.

C.3.2.6 Performance Requirements (Operations & Maintenance O&M)

C.3.2.6.1 Program Management – Sustainment Support The Contractor shall manage sustainment support efforts to ensure life cycle support for all fielded JEM systems.

C.3.2.6.1.1 Periodic Work Planning and Scheduling Meetings The Contractor shall participate in Periodic Work Planning and Scheduling Meetings with the Government Program Office and Government Contracting Representatives. The first Periodic Work Planning and Scheduling Meeting will be scheduled by the Program Office within 30 days of contract award. Periodic Work Planning and Scheduling Meetings may be held in conjunction with other meetings and reviews or scheduled independently no less than six

(6) months apart. Depending on the content to be discussed and resolved, the Work Planning and Scheduling Meeting may be held at SPAWAR San Diego (CA), the Contractor's facility, or via teleconference. The understanding and commitments agreed upon during the Periodic Work Planning and Scheduling Meetings, or specific clarification initiated by the Government to the Contractor, will be detailed in a Technical Instruction (TI) provided to the Contractor by the Government. A TI template is provided by reference in Other Government Documents, C.9.7

C.3.2.6.1.2 Monthly Status Report The Contractor shall provide all monthly status reports IAW ELIN A005.

C.3.2.6.1.3 Integrated Master Schedule Report The Contractor shall provide all monthly status reports IAW ELIN A007.

C.3.2.6.2 Configuration Management The Contractor shall document their CM processes and procedures in a Configuration Management Plan (CMP) that shall maintain the integrity of the configuration items, Standard Operating Procedures and shall be delivered IAW ELIN A025. The CMP shall serve as the baseline for all configuration management activities, including all changes to technical data. The Contractor shall implement and maintain the Government-approved CMP and provide revisions IAW ELIN A025.

C.3.2.6.3 Fielded System Sustainment Support The Contractor shall provide the fielded product sustainment support of the JEM software. Software updates shall be performed in accordance with the most recent product baseline established by and approved by the Government.

In accordance with JPM IS SOP 10 the Contractor shall use the JPM IS database to:

1) Review and provide input to Government-developed Change Requests.

2) Develop Change Requests.

3) Review and provide input to system configuration.

4) Review and provide input to software load procedures.

5) Review and provide input to production and installation drawings and documentation.

6) Review and provide input to System problem resolution.

7) Review and provide input to pre-installation check out procedure.

8) Provide input to version configuration required for proper system operation, production testing and configuration management.

C.3.2.6.4 Software Delivery In delivering the software, the Contractor shall adhere to the JPM IS Software Deliveries Process, SOP 31 (20 May 2015).

C.3.2.6.4.1 Formal In-Cycle Deliveries The Contractor shall make Formal In-Cycle Deliveries to include delivery of Software Items and Technical Documentation. In-cycle deliveries are tied to Government milestone events such as formal Testing and Evaluation leading to Fielding Decisions.

C.3.2.6.4.1.1 Formal in-cycle deliveries shall include all components of the software, even if no changes have been made to specific components.

C.3.2.6.4.1.2 As a part of a Formal In-Cycle Delivery, the Contractor shall create and deliver the following software and technical documentation:

C.3.2.6.4.1.2.1 The Contractor shall update Software Product Specification (SPS), IAW ELIN A008.

C.3.2.6.4.1.2.2 The Contractor shall update Software Version Description (SVD), IAW ELIN A011.

C.3.2.6.4.1.2.3 The Contractor shall update and Software Test Description (STD), IAW ELIN A016.

C.3.2.6.4.1.2.4 The Contractor shall update and deliver a Software Test Report (STR) as a record of the testing performed on a CSCI, a software system or subsystem, or other software-related item, IAW ELIN A018.

C.3.2.6.4.1.2.5 The Contractor shall update System Administrator Manual (SAM) IAW ELIN A014.

C.3.2.6.4.1.2.6 The Contractor shall update Software User Manual (SUM) IAW ELIN A015.

C.3.2.6.4.1.3 The Contractor shall when required provide updates to the following JEM technical documentation due to changes in the software to maintain the accuracy of the document as set forth below:

C.3.2.6.4.1.3.1 The Contractor shall update Interface Design Document (IDD)

IAW ELIN A012.

C.3.2.6.4.1.3.2 The Contractor shall update Software Programmer’s Guide (SPG) IAW ELIN A013.

C.3.2.6.4.1.3.3 The Contractor shall update Engineering Notebooks (EN) IAW ELIN A020.

C.3.2.6.4.1.3.4 The Contractor shall update Software Resources Data Reporting (SRDR) IAW

ELIN A006.

C.3.2.6.4.1.4 Baseline Management

The Contractor shall maintain the currency and accuracy of the allocated and product baselines. The Contractor shall establish and follow definitive processes that identify how the baseline will be managed or maintained.

C.3.2.6.4.1.4.1 Baseline Traceability The Contractor shall maintain documented traceability between the functional, allocated, and product baselines for all software items. Traceability shall include all derived component-level requirements, including those typically included in a separate Software Requirements Specification (SRS), and shall provide forward and backward traceability between all requirements, system components, and associated design documentation (e.g. IDD, SDD, Detail Specs). Traceability shall also include rationale and heritage information via inclusion of Requirement ID, Rationale, Traced From and Owner metadata as detailed in MIL-HDBK-520A Table I, as well as documentation of (or direct links to documentation of) all historical approved changes to the Contractor-managed requirements.

C.3.2.6.4.1.4.2 The Contractor…