HC104719R0007_C2SE_RFP09042019.pdf

CODE

(Hour)

PAGE(S)

until 10:00 AM local t ime 07 Oct 2019

X

A X B X C

D

EX

X G F 47 - 50

51 - 65 X H 66 - 73

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)

1 73

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

HC1047 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 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 - 4

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

5 - 23 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

25 X K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 26 - 30 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 31 - 37 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

38 - 45

PART II - CO NTRACT CLAUSES

DEFENSE INFORMATION SYSTEMS AGENCY

P.O. BOX 549

FT. MEADE MD 20755

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

04 Sep 2019

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

HC104719R0007

Section B - Supplies or Services and Prices

B1

B.1. MAXIMUM CONTRACT CEILING AND MINIMUM CONTRACT GUARANTEE

(a) Maximum. The maximum Contract ceiling value of all task orders issued against this single award procurement is established at $75,000,000.00 dollars.

(b) Minimum. The minimum guaranteed award amount for this Indefinite-Delivery, Indefinite-Quantity (ID/IQ) Contract is $10,000.00 dollars for the full term of the Contract. The minimum guarantee only applies if the awardee does not receive a task order within the ordering period. The minimum guarantee of this ID/IQ contract is anticipated to be fulfilled/obligated with the issuance of Task Order 1.

(c) The Government has no obligation to issue Task Orders to the Contractor beyond the amount specified in paragraph (b).

(End of Text)

B2

B.2. TASK ORDER CONTRACT TYPES

This is a single award indefinite delivery/indefinite quantity (ID/IQ) contract that allows for the use of task orders.

Task order contract types permitted include those under FAR 16.2 Fixed-Price and FAR 16.3 Cost-Reimbursement.

(End of Text)

B3

B.3. FIXED PRICE (FP) LABOR RATES

The Fixed Price Labor Rate Table, [Attachment Number To Be Completed At Time Of Award], represents the Offeror’s proposed fully-burdened fixed price hourly labor rates for each skill classification for work performed at Government sites and work performed at Contractor sites. The rates will be used as ceiling labor rates for pricing of all labor proposed under future fixed priced task orders or task orders with fixed price line items issued under this ID/IQ contract. The labor rates correspond to the labor categories and descriptions contained in Attachment C1.

(End of Text)

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 UNDEFINED

C2 Portfolio SE Support Services - Fixed

FFP

Labor - Fixed Price (FP) All Variations - This CLIN applies to all variations of contract types under fixed price. See Schedule B labor rate tables.

FOB: Destination

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0002 UNDEFINED

C2 Portfolio SE Support Services - Cost

COST

Labor - Cost Reimbursable (CR) All Variations - This CLIN applies to all variations of contract types under cost reimbursable.

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0003 UNDEFINED

ODCs in Support of CLINs 0001 and 0002

COST

Cost Reimbursable (CR) Other Direct Costs (ODCs) in support of Labor CLINs 0001 and 0002. ODCs may consist of software, materials, and task order-related items that are incidental to the services being performed. The cost of general-purpose items required for the conduct of the Contractor’s normal business operations will not be considered an allowable ODC in the performance of this contract. Profit is not allowed on ODCs for any task order; however, applicable burdens are allowed in accordance with Contractor’s accounting practices.

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0004 UNDEFINED

Travel in Support of CLINs 0001 and 0002

COST

Cost Reimbursable (CR) Travel funding in support of Labor CLINs 0001 and 0002. Travel must be incidental to the work being performed under this contract.

All travel must be pre-approved in writing by the COR prior to the Contractor incurring the cost. Travel shall be in accordance with FAR Subpart 31.205-46.

Profit is not allowed on Travel for any task order; however, applicable burdens are allowed in accordance with Contractor’s accounting practices.

MAX COST

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

as of 12 August 2019

Contract Number: TBD at time of award Contractor Name TBD at time of award Solicitation Number: HC1047-19-R-0007 Follow-on to Previous Contract and Task Order Number:

HC1047-15-C-4012

HC1028-08-D-2025-VC22

C.1. Contracting Officer’s Representative (COR).

C.1.1. Primary COR.

Identified at the individual Task Order level.

C.1.2. Alternate COR.

Identified in Section G, Points of Contact.

C.2. Contract or Task Order Title. Command and Control (C2) Portfolio Systems Engineering (SE) Services

C.3. Background.

The C2 Portfolio Systems Engineering order will be an overarching approach for fulfilling requirements to provide systems engineering technical and management support for the planning, implementing, and executing of current and future enterprise Information Technology (IT) capabilities and computing services. The four (4) major programs comprising the C2 Portfolio are known today as the Global Command and Control System-Joint (GCCS- J), the Global Combat Support System-Joint (GCSS-J), the Joint Planning and Execution Services (JPES), and the Global Command and Control System-Joint Enterprise (GCCS-JE). Each of the programs develop and sustain systems for use by the joint communities and as such each has requirements to independently plan, implement, and execute capabilities associated with these systems. The operational systems were developed independently of each other and, as a result, some of the foundational services that support each system are duplicative. The C2 Portfolio will evolve over time to have common modernized foundational services eliminating existing duplicative services.

Additionally, the core mission applications that will interface with the common foundational services will also be modernized resulting in the sunset of specific legacy components. As a result, the C2 capabilities that are supported by this PWS will transition over time.

Each of the major C2 systems is described below:

• GCCS-J is the Department of Defense (DoD) joint C2 System of Record for achieving full spectrum dominance. GCCS-J is a suite of mission applications that provides critical joint war-fighting C2 capabilities and is the principal foundation for dominant battlespace awareness, providing an integrated, near real-time picture of the battlespace necessary to conduct joint and multinational operations. GCCS-J provides a robust and seamless C2 capability to the Commander-in-Chief (CINC), Secretary of Defense (SECDEF), National Military Command Center (NMCC), Combatant Commanders (CCDRs), Joint Force Commanders, and Service Component Commanders. GCCS-J offers vital interoperability to the systems the joint warfighter uses to plan, execute, and manage military operations. Key capabilities of GCCS-J include two specific Global baselines, v4.3 and v6.x. GCCS-J Global 4.3 has a planned sunset in mid Fiscal Year (FY) 2020 and GCCS-J Global 6.x has a planned sunset by early FY23. The modernized system to replace GCCS-J is referred to as GCCS-J Enterprise (GCCS-JE). Rather than a local installation of the release at each site, the Initial Operational Capability (IOC) of GCCS-JE will be provided regionally.

• The GCSS-J system is the Joint Staff (JS/J4) Logistics System of Record providing an enterprise logistics Common Operational Picture (LogCOP) for the Combatant Command (CCMD) and Joint Task Force (JTF) commanders. The system integrates data from CCMD and JS/J4 identified authoritative data sources to provide a fused, integrated, near real-time, multi-dimensional view of combat support and combat service support across joint capability areas, providing situational awareness of the battlespace and logistics pipeline (e.g., Supply, Deployment and Distribution, Engineering, etc.) and optimizing joint logistics processes. Utilizing a strategic server concept, GCSS-J capabilities are accessible to users from any Government approved equipment, anywhere, as long as they have access to a web browser, a GCSS-J account and valid credentials (Secret Internet Protocol (IP) Router Network (SIPRNet): DoD SIPRNet hard token, Non-Secure IP Router Network (NIPRNet): Common Access Card (CAC)). Current GCSS-J initiatives provide solutions that improve collaboration across the CCMDs and facilitate the integration of GCSS-J services with each CCMD developed and maintained LogCOP.

• Joint Planning and Execution Services (JPES) is a portfolio of capabilities that support the policies, processes, procedures, and reporting structures needed to plan, execute, mobilize, deploy, employ, sustain, redeploy, and demobilize activities associated with Joint Operations. JPES capabilities support the deliberate planning, crisis action planning and global force management processes. Key legacy capabilities within JPES include the Joint Operation Planning and Execution System (JOPES), JPES Framework (JFW), Joint Capabilities Requirements Manager (JCRM) and Preferred Force Generation (PFG). JOPES is being modernized in two phases. Phase One consists of JPES which will replace the existing functionality of JOPES, concluding with the sunset of JOPES anticipated by the end of FY19. Phase Two consists of enhancing JPES to replace the functionality provided by JCRM. Phase Two is anticipated to start in planned FY21 and will result in the sunset of JCRM.

• The Global Command and Control System – Joint Enterprise (GCCS-JE) will be the DoD Joint Command and Control (C2) system of record for achieving full battlespace dominance. It will provide critical joint warfighting C2 capabilities, providing an integrated, near real-time picture of the battlespace necessary to conduct joint and multinational operations. GCCS-JE will provide a robust and seamless C2 capability to the Commander-in-Chief (CINC), Secretary of Defense (SECDEF), National Military Command Center (NMCC), Combatant Commanders (CCDRs), Joint Force Commanders, and Service Component Commanders. GCCS-JE will offer vital access to the fused information from systems and sources that the Joint warfighter uses to plan, execute, and manage military operations.

C.4. Objectives.

The objective of this PWS is to provide systems engineering technical and management support across the C2 Portfolio in the planning, implementing, and executing of current and future enterprise Information Technology (IT) capabilities and computing services. Core C2 task objectives include the performance of systems engineering processes and procedures, requirements management and analysis, functional analysis and design synthesis, configuration management, cybersecurity compliance and assessment, laboratory support and management, deployment and operational support, and sustainment and maintenance engineering support.

To accomplish these objectives, the intent is to support current and emerging technologies, processes, frameworks, architectures, methodologies, software and applications, hardware, and research to enable solutions for efficiencies and effectiveness across optimized end-to-end system delivery lifecycles. Emerging technical areas include digital technology platforms, cloud and networks, analytics, big data, adaptive security, mobility, virtualization and displays, machine learning and intelligent automation. Emerging processes and frameworks include agile development, enterprise agile, secure DevOps, and other best practices in software and system engineering.

C.5. Scope.

This PWS provides systems engineering support to the current C2 Portfolio of systems. This consists of GCCS-J, JOPES, JPES, JFW, JCRM, PFG, GCSS-J, and GCCS-JE. Follow-on modernization activities that employ emergent technologies, processes, frameworks, architectures, methodologies, software and applications, hardware, and research are included. Systems engineering programmatic support services, system administration, Database Administration (DBA) & Cyber Engineering support services apply to this effort. C2 Portfolio capabilities operate under Disconnected, Intermittent, and Limited (DIL) conditions and include custom baselines configured to support specific Foreign Military Sales (FMS) cases.

Section 5, Scope, and Section 6, Performance Requirements, of the PWS convey the span of the requirements the Contractor shall provide under this contract. However, specific details of task assignments, deliverables, delivery locations, documentation, training, applicable Government/DoD/Customer/Industry standards will be provided within individual Task Orders. An individual Task Order may relate to a single performance area or involve functions from multiple performance areas.

10 task areas constitute the technical scope of this contract:

Task Area 1: Contract and/or Task Order Management Task Area 2: Systems Engineering Support Task Area 3: Architecture and Design Task Area 4: Configuration Management Task Area 5: Cybersecurity Task Area 6: C2 Laboratory and System Administration Support Task Area 7: Research, Development, and Sustainment Technical Experiments and Investigation Task Area 8: Systems Engineering Process Improvement/Automation Task Area 9: Capability Deployment Planning and Review Task Area 10: Training and Technical Exchange

The Government may require surge support during the base or any option period of the individual Task Orders.

Surge modifications will be within the scope of the Task Orders and provide increased support for the defined task areas of the individual Task Order PWS. The not-to-exceed surge amount will be provided within individual Task Order if applicable to the order.

C.6. Performance Requirements.

C.6.1. Task Area 1 – Contract and/or Task Order Management

C.6.1.1. Subtask 1 – Contract Management.

The contractor is responsible for ensuring all awarded Task Orders are successfully executed per the Task Order, to include providing leadership and controls necessary to meet timely deliverable requirements. The contractor shall identify one Contractor Manager for all Task Orders that interfaces with the Government regarding contractual issues. The Contractor Manager shall provide contract status reports on an annual basis broken down to a Task Order Level. The status report should include, at a minimum, the financial status of each Task Order, the current staffing of each Task Order, the status of deliverables for each Task Order, confirmation of compliance with FAR 52.219-14, Limitations on Subcontracting, and any issues, concerns or problems. See Section G.4. Program Management Support Costs.

Deliverables:

Title Format Due Date Distribution/Copies Frequency and

Remarks Contract Status Report

Contractor Format, Government Approved.

Compatible with Microsoft Office 2010 or current version identified by the Government.

The first business day after a year of the ordering period has passed.

The final CSR shall be submitted on the last day of the five-year ordering period.

One (1) copy of the transmittal letter with the deliverable to the Contracting Officer (KO) and each Task Order COR.

Annually

C.6.1.2. Subtask 2 – Task Order Management.

The contractor shall ensure all tasks are completed according to the agreed upon schedule and quality for each task order. The contractor shall prepare and provide a Task Order Management Plan (TOMP) describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements for the PWS execution. The contractor shall provide technical and functional activities required for integration of all tasks specified within the PWS. The contractor shall integrate and coordinate all activities needed to execute the requirements within the PWS. The contractor shall ensure customer satisfaction and professional and ethical behavior of all contract personnel. The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirements. The contractor shall have quality assurance processes and plans in place throughout the life of this contract.

Deliverables: The Government will specify deliverables at the task order level.

C.6.1.3. Subtask 3 - Control Progress and Status Reporting.

The contractor shall prepare and provide a Monthly Status Report (MSR) at the task order level to communicate the status of tasks performed during the month and/or successful completion of tasks, as applicable to the phase of the contract. The MSR content requirements will be specified at the task order level. Examples of MSR contents include problem identification and recommendations for problem resolutions, personnel reassignments, or a break out of labor categories and hours per month.

The contractor shall conduct a monthly status review meeting at the task order level. The meeting may be facilitated via Defense Collaboration Services (DCS), teleconference, or onsite at the Government’s discretion. The contractor shall generate meeting minutes based on the monthly status review meeting. The minutes shall summarize the discussion of the monthly status review meeting and capture actions to be resolved.

C.6.1.4. Subtask 4 – Kick-Off Meeting (KOM).

The contractor shall prepare for and participate in a KOM with the Government to establish a baseline of understanding after the issuance of a task order at a location to be determined by the COR not later than (NLT) ten

(10) business days after the issuance of a task order. Participants will include the Product Leads and Deputy Product Leads, C2 Portfolio Program Managers (PMs), KO, COR, key contractor personnel and other Government staff. At the KOM, the contractor shall present the details of its intended approach for review. The KOM will serve to resolve strategic questions, refine goals, define success, and explore the biggest challenges and breakthrough opportunities for the Government. This will be the beginning of a dialogue between the Government and the contractor to ensure successful execution of this contract. The contractor shall coordinate the agenda for the KOM and include, as a minimum, the following:

• Introduction of management and technical teams

• Establishment of common understanding of the contract

• Details of contractor’s technical/management approach

• Other relevant items may be introduced at the discretion of the contractor and/or the Government

C.6.1.5. Subtask 5 – Task Order Transition.

In the event of a contractual change or turnover, the Government will provide written notification to the contractor.

Upon receipt of the notification, the contractor shall provide, at a minimum, all materials and support necessary to accomplish a seamless and expeditious transition of the tasks identified in the task order PWS to the incoming contractor or Government. The transition shall include the following: all in-progress working files for the deliverables of the task order PWS; final files for all tasks and final phase out meetings with Government, incumbent, and the new contractor. The incumbent contractor shall transition activities to the incoming contractor or Government with minimal disruption of services to the Government.

C.6.2. Task Area 2 - Systems Engineering Support The contractor shall provide systems engineering support to the Joint C2 capabilities for the C2 Portfolio.

C.6.2.1. Subtask 1 - Developmental Engineering Support

Developmental engineering support throughout this PWS shall refer to C2 programs, projects, and initiatives that are under development or being modernized. Developmental engineering support shall encompass support across the scope of systems engineering activities to include risk management, requirements management and analysis, functional analysis and design synthesis, data mediation, and optimization of systems, processes and procedures (exclusive of software coding). Developmental engineering support shall also include conducting meetings, answering questions from vendors, supporting cybersecurity activities, and deployment support. The contractor shall provide documentation for each of the above developmental engineering activities.

C.6.2.2. Subtask 2 – Non-developmental Engineering Support Non-developmental engineering support throughout this PWS shall refer to those C2 programs, projects, and initiatives in maintenance, sustainment, operations and support.

The contractor shall provide engineering support for Joint C2 capability developers and C2 Portfolio leadership.

Non-developmental engineering support spans the entire scope of systems engineering activities for maintenance, sustainment, operations, and support to include risk management, requirements management and analysis, functional analysis and design synthesis. Support includes sustainment engineering such as conducting meetings, answering questions of vendors and providing other maintenance support. Non-development engineering support also includes supporting cybersecurity activities, test and evaluation such as providing guidance/answering questions (exclusive of actual test planning/test execution) and deployment support, and providing documentation for each of these systems engineering activities.

The contractor shall support the C2 Portfolio leadership with advisory services to include recommendations during acquisition and strategic planning of the organization and Subject Matter Expertise of C2 warfare with warfighting knowledge of the C2 domain and Programs of Record in support of C2 missions (e.g. currently fielded GCCS Family of Systems, weapons systems, Deployable Joint C2 (DJC2) systems).

C.6.2.3. Subtask 3 – Joint C2 Systems Engineering Process The contractor shall provide support for the Joint C2 Systems Engineering (SE) processes utilizing Government- Furnished Information (GFI) provided after contract award. The contractor shall support the development, including the updates, refinement, and implementation, of the SE processes, workflows, illustrations, narratives, and templates. Using the existing Joint C2 SE process artifacts, the contractor shall prepare new and/or updated Systems Engineering Plans (SEP), Information Support Plans, Program Protection Plans, Test & Evaluation Master Plan (TEMP), System Requirement Reviews, and Business Case Analyses (BCA) for programs under the C2 Portfolio as needed in accordance with the DOD/DISA Systems Engineering process. The contractor shall provide advice and technical guidance to those individual functional projects/programs of Joint C2 attempting to utilize and adapt them for project usage.

The contractor shall support the development, including the updates, refinement, and implementation, of the C2 Agile development process for its programs. The contractor shall support agile development / engineering activities including release and sprint planning, developing requirements, refining user stories, developing and modifying query specifications, and assigning story points, as needed.

The contractor shall maintain, update and refine the repository for organizing Joint C2 content on platforms, such as SharePoint and Forge.mil, and provide administrator support to ensure that portal features are effectively utilized in support of C2 Portfolio goals and objectives. The contractor shall maintain and update content and ensure that portal access controls for users and content are properly maintained.

The contractor shall investigate the relative merits of a range of iterative and incremental agile process frameworks, including but not limited to Scrum, Dynamic Systems Development Method (DSDM), Crystal, Extreme Programming (XP), Rational Unified Process (RUP), Lean, Kanban, and Scaled Agile Framework (SAFe). The contractor shall also provide recommendations for use by the C2 Portfolio in the systems engineering process workflow illustration and narrative that justify their selected process framework(s).

C.6.3. Task Area 3 – Architecture and Design The contractor shall provide technical and management support to current and emerging C2 Portfolio architectures and designs. With guidance and approval from the Government, the contractor shall develop architecture and design plans/models based on stakeholder requirements by assessing the intended use of the architecture and the required data. The contractor shall analyze, collect, organize, correlate, document, and store architecture data in accordance with DOD policy and JC2 reference architectures. The contractor shall update, modify, or generate Information Support Plan (ISP) documentation and relevant DoD Architecture Framework (DoDAF) views. The Contractor shall ensure that the architectures and designs meet requirements for deployment to the global enterprise, virtualized instances, and DIL environments.

C.6.4. Task Area 4 – Configuration Management (CM) The contractor shall provide support for configuration management policies and procedures. The contractor shall maintain, update and refine the CM-relevant artifacts to include CM Plan(s) and Configuration Control Board (CCB) Charter(s).

C.6.4.1. Subtask 1 - Developmental Configuration Management The contractor shall support implementing CM activities and processes for those individual functional C2 Portfolio programs, projects, and initiatives that are in development or being modernized. The contractor shall provide technical (CM Secretariat) support for the Configuration Control Boards (CCBs) and Engineering Review Boards (ERBs). The contractor shall maintain, update and refine the CM trackers and CM-oriented Web page listings in the designated repository (e.g., Forge.mil) for development/modernization projects.

C.6.4.2. Subtask 2 – Non-Developmental Configuration Management The contractor shall support implementing CM activities and processes for those individual functional C2 Portfolio programs, projects, and initiatives that are in maintenance, sustainment, or operations and support. The contractor shall provide technical (CM Secretariat) support for the CCBs and ERBs as needed. The contractor shall track Change Control Requests (CCRs) as specified in the Joint C2 Systems Engineering and Integration (SE&I) CM Plan provided by the Government. The contractor shall maintain, update and refine the CM trackers and CM-oriented Web page listings in the designated repository (e.g., Forge.mil) for non-developmental projects.

C.6.5. Task Area 5 – Cybersecurity Contractor personnel supporting Task Area 5 shall comply with training and certification requirements at Information Assurance Technical (IAT) Level II in accordance with DoD 8570.01-M.

C.6.5.1. Subtask 1 - Cybersecurity Guidance The contractor shall maintain, update and refine the overarching capstone cybersecurity documentation that could be utilized for any C2 Portfolio program, project, or initiative being developed in accordance with systems engineering processes and other cybersecurity guidance for system administrators and cybersecurity personnel.

The contractor’s vulnerability management shall be conducted in accordance with the DISA Vulnerability Management Policy memo. The contractor shall deliver a Vulnerability Management Plan (VMP) to the Government which shall be compliant with the DISA Vulnerability Management Policy memo. Open source software monitoring shall be included in the VMP. The contractor shall conduct open source software update monitoring on a monthly basis.

The contractor shall update and revise the Continuity of Operations (COOP) Plan to be an overarching capstone document that could be utilized for any C2 Portfolio initiative being developed in accordance with this SE process.

The COOP Plan shall identify COOP processes and procedures, essential functions, alternate facilities, and test, training and exercise activities to ensure continuous performance of essential functions. The COOP Plan shall be accompanied by a Disaster Recovery Plan.

C.6.5.2. Subtask 2 - Developmental Cybersecurity Engineering The contractor shall provide cybersecurity engineering (cybersecurity process management, documentation, support and assistance) support for the individual functional programs, projects, and initiatives of C2 Portfolio capabilities under development or modernization.

The contractor shall provide support to the Government Information System Security Officers (ISSOs) activities, including Information System Security Engineer (ISSE) Manager (ISSE) and Information System Security Manager (ISSM) activities, for the individual functional programs/projects/initiatives of C2 Portfolio capabilities under development and modernization. The ISSO shall coordinate and lead Risk Management Framework (RMF)/Cybersecurity meetings on a weekly basis, support transitions to RMF for assigned systems and maintain authorizations as required, maintain close communications with the functional teams and report status to the designated ISSM. The contractor shall update and maintain RMF artifacts and submit RMF/DIACAP packages using Enterprise Mission Assurance Support Service (eMASS) or other assigned tools. The contractor shall interact with the developer, ISSM, ISSE and Validator to resolve technical and non-technical Security Technical Implementation Guide (STIG) and cybersecurity control findings and update the POA&M in eMASS; and, monitor and evaluate all related information Assurance Vulnerability Alerts (IAVA) through identification to closeout.

The contractor shall provide cybersecurity assessment support for the individual functional programs/projects/ initiatives of C2 Portfolio capabilities under development or modernization. The contractor shall coordinate and execute cybersecurity assessments and interact with the ISSM, ISSO, ISSE and Security Controls Assessor (SCA) regarding interpretation of technical and non-technical STIG requirements and applicability of IA controls and required documentation/artifacts needed prior to a validation event. The contractor shall develop security assessment plans (SAP) and reports (SAR) in accordance with RMF requirements and work with the developer to complete and hold an Information Assurance Validation Readiness Review (IAVRR) prior to validation. In support of cybersecurity assessments, the contractor shall conduct the assessment kick-off meeting, perform STIG validation, use current vulnerability scanning tools for testing, discuss vulnerability findings, review architectures and designs to provide security recommendations and enter validation data into the proper repository. The contractor shall upload test results into eMASS or other repository; assist ISSM/ISSO to update the POA&M, schedule post-validation meetings with developers and Government personnel as necessary, conduct risk assessment and document residual risks. The contractor shall ensure that developers and the government team have awareness of activities through submitting actions to the ISSO/ISSM for incorporation into the Integrated Master Schedule (IMS). The contractor shall participate in Assessment & Authorization efforts. The contractor will assist with necessary research and implementation of a continuous Authorization to Operate (ATO). The contractor shall apply the above cybersecurity processes and procedures in an agile development, scaled agile enterprise framework, and secure DevOps environment, as appropriate.

C.6.5.3. Subtask 3 – Non-Developmental Cybersecurity Engineering The contractor shall provide cybersecurity engineering (cybersecurity process management, documentation, support and assistance) support for those individual functional programs, projects, and initiatives of C2 Portfolio capabilities that are in maintenance, sustainment or operations & support.

The ISSO shall coordinate and lead RMF/Cybersecurity meetings on a weekly basis, support transitions to RMF for assigned systems and maintain authorizations as required, maintain close communications with the functional teams and report status to the designated ISSM. The contractor shall update and maintain RMF artifacts and submit RMF/DIACAP packages using eMASS or other assigned tools; interact with the developer, ISSM, ISSE, and Validator to resolve technical and non-technical STIG and cybersecurity control findings and update the POA&M in eMASS; and, monitor and evaluate all related IAVA’s through identification to closeout.

The contractor shall provide cybersecurity assessment support for the individual functional programs, projects, and initiatives of C2 Portfolio capabilities that are in maintenance, sustainment or operations & support. The contractor shall coordinate and execute cybersecurity assessments and interact with the ISSM, ISSO, ISSE and SCA regarding interpretation of technical and non-technical STIG requirements and applicability of cybersecurity controls and required documentation/artifacts needed prior to a validation event. The contractor shall develop SAP and SAR in accordance with RMF requirements and work with the developer to complete and hold IAVRR prior to validation.

In support of cybersecurity assessments, the contractor shall conduct the assessment kick-off meeting, perform STIG validation, use current vulnerability scanning tools for testing, discuss vulnerability findings, review architectures and designs to provide security recommendations and enter validation data into the proper repository. The contractor shall upload test results into eMASS or other repository; assist ISSM/ISSO to update the POA&M, schedule post-validation meetings with developers and Government personnel as necessary, conduct risk assessment and document residual risks. The contractor shall ensure developers and the Government team have awareness of activities through submitting actions to the ISSO/ISSM for incorporation into the IMS. The contractor shall participate in assessment & authorization activities.

C.6.6. Task Area 6 - C2 Laboratory and Systems Administration Support The contractor shall provide support for capability integration, maintenance, and sustainment in DISA Headquarters Laboratory spaces, cloud, and virtualized environments as appropriate, to include all of their supported environments, such as staging and integration/test.

C.6.6.1. Subtask 1 - Developmental Capabilities Integration The contractor shall provide integration support for developer-delivered capabilities in the DISA Headquarters Laboratory spaces, cloud, and virtualized environments as appropriate, to include all of their supported environments. Following a successful delivery of software and documentation artifacts to the Government-controlled CM Repository and upon receipt of cybersecurity approval, the contractor shall install the checked-in software. The contractor shall also verify the accuracy of delivered documentation (red-lining as necessary), ensure that all required external data source interfaces are connected and operational and perform a software smoke-check to provide assurance that the installed software capability is “ready for test”. The contractor shall establish/administer data management and database user accounts, including consolidated permissions for data access. The contractor shall audit database activity to ensure operational capability.

C.6.6.2. Subtask 2 - Non-Developmental Capabilities Integration The contractor shall provide integration support for delivered maintenance fixes/releases in DISA Headquarters Laboratory spaces, cloud, and virtualized environments as appropriate, to include all of their supported environments. Following a successful delivery of software and documentation artifacts to the Government-controlled CM Repository and upon receipt of cybersecurity approval, the contractor shall install the checked-in software. The contractor shall also verify the accuracy of delivered documentation (red-lining as necessary), ensure that all required external data source interfaces are connected and operational and perform a software smoke-check to provide assurance that the installed maintenance fix is “ready for test.” The contractor shall establish/administer data management and database user accounts, including consolidated permissions for data access. The contractor shall audit database activity to ensure operational capability.

C.6.6.3. Subtask 3 – DISA Headquarters Laboratory Spaces, Cloud, and Virtualized Environment Maintenance and Sustainment

The contractor shall provide support for maintaining and sustaining the DISA Headquarters Laboratory spaces, cloud, and virtualized environments to include all of their other supported environments. The contractor shall provide system administration-level support on an 8x5 basis. The contractor shall provide sustainment of installed components, e.g., the Common Infrastructure, Performance Tools, and Capability Components in both UNCLASSIFIED and SECRET environments.

The contractor shall provide maintenance of the DISA Headquarters laboratory spaces, cloud, and virtualized environment components and all of their other supported environment components, to include installation of new version releases, system software updates, software patches, daily status reporting on all suites. The contractor shall perform troubleshooting, back-ups, account creation, request IP addresses, coordinate Approvals to Connect (ATCs), and inventorying laboratory equipment and assets for supported programs.

The Government will provide the hardware, COTS software, lab space and network connectivity required for the DISA Headquarters laboratory spaces, cloud, and virtualized environments, and all of their other supported environments.

C.6.6.4. Subtask 4 – Software Services The contractor shall develop, maintain, and sustain software and source code in support of DISA C2 programs, to include development of the DevOps environment and configuration of automated test tools in accordance with cybersecurity guidance provided in previous sections of this document within DISA HQ laboratories. The contractor will provide maintenance and sustainment of developed software and code as instructed in the previous section of this document.

C.6.7. Task Area 7 – Research, Development, and Sustainment Technical Experiments and Investigation

The contractor shall provide support for modeling and simulation (M&S) efforts to include: technical experiments, investigations, data reduction, analysis and reporting. The contractor shall investigate new technologies for possible adoption; experiments and prototypes to assess architectural concepts and other engineering issues.

The contractor shall conduct technical studies, data collection, identification, analysis and evaluation of technology prototypes and for acquisition research purposes. The contractor shall prepare evaluation criteria to assess and evaluate prototypes during technology identification, planning, design, engineering, and implementation. The contractor shall coordinate detailed performance evaluations of technology prototypes documented in a Prototype Performance Evaluation Plan, to include capacity, timeliness, and scalability, Central Processing Unit (CPU) and network utilization, memory, and Input/output (I/O) functions, metrics findings and analysis shall be documented in a Prototype Performance Evaluation Report.

The contractor shall provide experiment and investigation support for sustainment and operations and support problems. The contractor shall investigate experiments to assess architectural issues; functional performance of Joint C2 capabilities; network issues; DIL bandwidth issues; Reliability, Availability and Maintainability (RAM);

and other engineering issues.

The contractor shall provide user feedback data analysis that provides metric-based insight to aid future systems engineering activities and acquisition decisions. The contractor shall establish system feedback metrics as an infrastructure component layer and implement candidate system feedback solutions.

C.6.8. Task Area 8 – Systems Engineering Process Improvement/Automation The contractor shall review and continually evaluate the overall C2 Portfolio systems engineering processes, methods and tools currently being used. Propose and upon COR approval, develop improvements to these systems engineering processes, methods, and tools that better fit the needs of the C2 Portfolio. The contractor shall monitor latest industry market capability trends and continually recommend areas of capability and functionality optimization.

The contractor shall observe and coordinate with developmental test and evaluation toward integrating automation tools/programs/scripts to enhance capability performance and redundancy. The contractor shall investigate, evaluate, and incorporate automated software tools and associated processes to facilitate systems engineering activities in DISA Headquarters laboratory spaces, cloud, and virtualized environments where appropriate.

The contractor shall replace repetitive manual activities with automated activities that can be run repeatedly. The contractor shall assist in improving the C2 Portfolio systems engineering processes by generating, executing, and reporting on automation. The selection of automated tools shall enable systems engineers to quickly set up and build complex scenarios that can be easily customized. The contractor shall develop a plan indicating how and when the tool or process is to be integrated into the laboratory, cloud, or virtualized environment. The contractor shall be proficient in executing systems engineering processes against client, server, virtual and enterprise C2 Portfolio of systems.

The approach and cost to automate shall be coordinated with and approved by the COR, prior to implementation.

The Government will purchase all third party automated tools for implementation and provide them to the contractor as Government Furnished Equipment (GFE).

C.6.8.1. Subtask 1 – Secure DevOps for Continuous Delivery Using Secure DevOps best practices, the contractor shall merge software development and IT operations into a seamless process for reduced time to fielding of capabilities. The contractor shall work in close collaboration with software development and IT operations representatives at meetings and working groups to promote standard tool usage and script delivery.

To automate processes across the DevOps lifecycle, the contractor shall leverage, build, and maintain contractor recommended, Government approved commercial/open source tools for builds, delivery, configuration management, testing, and provisioning. In addition, for Secure DevOps the contractor shall automate penetration detection and remediation, and continuous IA monitoring. The contractor shall recommend automated workflows where applicable and value is added.

C.6.8.2. Subtask 2 – Mobility Enterprise Capabilities and Services The contractor shall investigate the convergence of cloud computing, mobile applications, and data center networking techniques. This shall include combining resource-constrained mobile computing devices with the cloud computing services hosted by virtualized data center resources for data storage and data processing. Further, the contractor shall investigate security issues in mobile cloud computing for a secure mobile enterprise service.

C.6.8.3. Subtask 3 – Scaled Agile Framework The contractor shall investigate the scalability of agile teams for the enterprise based on scaled agile framework guidance, principles, and practices. The contractor shall formulate recommendations to align tools, processes, standards, metrics, and terminology across teams in order to minimize impediments to deliver capabilities. The use of automated tools shall enable cross-team collaboration, tracking and planning, reporting, and artifact change by co-located and geographically dispersed teams.

The contractor shall provide Scaled Agile Framework (SAFe) support in alignment with the SAFe construct. SAFe support includes fulfilling SAFe roles (e.g. Scrum master (s), Release Train Engineer(s), Solution Train Engineer(s), and Lean UX) and executing framework activities as requested by the Government.

C.6.9. Task Area 9 – Capability Deployment Planning and Review The contractor shall support the development of deployment strategies and approaches. The contractor shall conduct pre-deployment meetings and participate in Fielding Decision Reviews (FDRs), towards assessing deployment execution readiness.

C.6.10. Task Area 10 – Training and Technical Exchange

C.6.10.1. Subtask 1 – Contractor Training of Government Personnel The contractor shall train its Government counterparts in the concepts, processes and procedures used to perform the Systems Engineering activities required under this contract. Training shall be performed on request of the Government, in the form of individual (i.e., one-on-one) and group sessions. Training shall be presented in the form of presentation slides, video presentations, desk-top process guides, or similar materials. Systems Engineering training topic areas will be selected by the Government, as needed for ongoing knowledge transfer.

A preliminary and final Training Plan shall be submitted to the Government for review and approval at the task order level. The Training Plan shall describe the training requirements, concepts, processes, procedures and materials that the Contractor shall develop to train Government personnel on selected Systems Engineering topics.

The Training Plan shall include the training schedule, including the expected duration of each type of training, expected number of trainees, and location of the training.

The Training Plan shall have an executive summary providing an overview of the plan’s management and technical approach. Summary schedules of project phases, activities, and tasks, and the corresponding training shall be provided. The extent of the training plan shall be summarized in terms of overall effort, time, impact, expected results, and products. Training materials shall be submitted ten (10) calendar days prior to a scheduled training session.

C.6.10.2. Subtask 2 – Technical Exchange Meetings (TEMs) The contractor shall participate in a technical exchange meeting for government personnel on a quarterly basis to address new trends, concepts, technologies, and updates in support of the Government’s systems engineering mission. Systems engineering technical exchange meeting topic areas will be selected by the Government, as needed for ongoing knowledge transfer. A TEM shall consist of a series of contractor presentations and discussions in which the contractor shall respond to questions posed by the Government in the selected topic areas. Draft agenda and meeting slides shall be submitted by the contractor ten (10) calendar days prior to a scheduled technical exchange meeting.

C.7. Performance Standards.

The following standards shall be directed at the overall contract level.