Solicitation.pdf

CODE

(Hour)

PAGE(S)

until local time

X

A X B X C

D

EX

X G F 86 - 98

99 - 124 X H 125 - 134

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 134

(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 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and 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 - 5

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

6 - 60 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

62 X K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 63 - 65 X

SPECIAL CONTRACT REQUIREMENTS

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

72 - 84

PART II - CONTRACT CLAUSES

DISA/DITCO-NCR

P.O. BOX 549

FT. MEADE MD 20755-0549

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

20 Mar 2025

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

HC104725R0005

Section B - Supplies or Services and Prices

SECTION B

B.1. MAXIMUM CONTRACT CEILING AND MINIMUM CONTRACT GUARANTEE

(a) Maximum. The maximum contract ceiling value of all Task Orders (TO) in this single award procurement is established at $62,364,899.

(b) Minimum. The minimum guaranteed award amount for this Indefinite-Delivery, Indefinite-Quantity (ID/IQ) contract is $5,000.00 for the full term of the contract. The minimum guarantee only applies if the awardee does not receive a TO within the base period of performance. The minimum guarantee of this ID/IQ contract is anticipated to be fulfilled/obligated with the issuance of TO 001.

(c) The Government has no obligation to issue TO to the contractor beyond the amount specified in paragraph (b).

B.2. TASK ORDER CONTRACT TYPES

This is a single award ID/IQ Contract for Defense Information Systems Agency (DISA) and Program Executive Office, Spectrum that allows for the issuance of TO. TO contract types permitted include FAR 16.2 Fixed- Price and FAR 16.3 Cost-Reimbursement, to include variants therein. TO may include FAR 17.1 multi-year contracting and FAR 17.2 Option periods. These contract types can be used individually or in combination within a single TO comprising of multiple CLINs.

B.3. FIXED PRICE (FP) LABOR RATES

The FP Labor Rates proposed represent the Offeror’s fully burdened fixed price hourly labor rates for each skill classification for work performed at both contractor and Government sites within Contiguous United States (CONUS). The rates provided in the pricing template will be used as ceiling labor rates for pricing of all labor proposed under future fixed priced TO issued under this ID/IQ contract. At time of award, the contractor’s FP ceiling labor rates will be incorporated into the contract.

B.4 MATERIALS AND OTHER DIRECT COSTS (ODC) (ALL ORDER TYPES)

Materials and ODCs may consist of software, licenses, subscriptions, materials, and TO-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 Materials/ODC in the performance of this contract. Profit is not allowed on materials or ODCs for any TO; however, applicable burdens are allowed in accordance with Contractor’s accounting practices. If applicable, the Contracting Officer will identify a not-to-exceed ODC ceiling under a separate CLIN on the TO.

B.5. TRAVEL PRICING (ALL ORDER TYPES)

Contractor personnel may be required to travel to support the requirements of this contract as stated in individual TOs. Local travel and travel outside of the local area will be CONUS . For those TOs requiring travel, the contractor shall include estimated travel requirements in the proposal as required by the TO instructions. For those TOs requiring travel, the specific travel requirements will be included in the order’s request for proposal. Travel will be considered local travel within 50 miles of the individual’s main place of performance/duty station and will not be reimbursed. The Government will not reimburse for local travel between the contractor facility (or facilities) and the DISA facility at Ft. Meade, MD and Annapolis, MD. Non-local travel shall be approved in writing by the COR prior to the travel occurring. Travel shall not commence without prior written consent in accordance with instructions in the task orders.

If the awardee does not have an approved accounting system at the time of award, upon award the awardee shall immediately initiate an accounting system review by Defense Contract Audit Agency (DCAA) and provide verification of such to the Contracting Officer. Reimbursement of travel costs under SIS TOs will be paid in accordance with the Joint Travel Regulation (JTR). If the awardee has an approved accounting system, DCAA approved burden rates are authorized on travel. Burdened travel rates are impermissible if the awardee does not possess an approved accounting system.

B.6. PROHIBITION ON ACCOMMODATION PURCHASING AND SUBCONTRACTING

Accommodation purchasing and subcontracting means the procurement of supplies and/or subcontracting of services which are not essential in the discharge of the contractor’s technical responsibilities under this contract.

These actions are usually prompted by a desire to achieve expedited procurement not warranted by technical program needs, or to avoid the requirements of current federal procurement regulation which are applicable if procurements were performed by the Government directly. Accommodation purchasing and subcontracting does not include cases in which the contractor is serving as a prime contractor in roles such as principal investigator, system integration agent or technical direction agent for which the volume of purchases or subcontracting, and sometimes the identification and management of subcontracting sources, is determined by program requirements. The contractor shall not perform accommodation purchasing and subcontracting, including any purchases or subcontracting which the Contracting Officer identifies to the contractor prior to executing the contract action as constituting accommodation purchasing and subcontracting. In such cases, the Contracting Officer will have the responsibility to communicate its concerns and decision to the cognizant technical sponsor. In addition, should the Contractor have a reasonable belief as to whether a particular action will constitute accommodation subcontracting, no action shall be taken to consummate the contract action until such time as the Contracting Officer is contacted and appropriate guidance is provided.

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 Lot

FFP Labor

FFP

Contractor's Firm-Fixed-Price efforts in accordance with section C.

FOB: Destination

PSC CD: DA01

NET AMT

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0002 Lot

CPFF Labor

CPFF

Contractor's Cost-Plus Fixed-Fee efforts in accordance with section C.

FOB: Destination

PSC CD: DA01

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0003 Lot

Materials/ODCs

COST

Materials and non-travel related Other Direct Costs (ODCs) to associated with the Contractor’s efforts in accordance with Section C. ODCs may consist of software, licenses, 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 Material/ODC in the performance of this Contract. Profit is not allowed on Materials/ODCs for any Task Order; however, applicable burdens are allowed in accordance with Contractor’s accounting practices.

FOB: Destination

PSC CD: DA01

ESTIMATED COST

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0004 Lot

Travel

COST

Travel-related Other Direct Costs (ODCs) to associated with the Contractor’s efforts in accordance with Section C. Travel will be reimbursed at actual cost in accordance with the limitations in the task order as well as those set forth in FAR Subpart 31.205-46, Travel Costs. Profit shall not be applied to travel costs. To the extent authorized by the Task Order, Contractors may apply indirect costs to travel in accordance with the Contractor’s usual accounting practices consistent with FAR 31.2.

FOB: Destination

PSC CD: DA01

ESTIMATED COST

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Surge

COST

The Government may require surge support at the task order level, and surge modifications will be within the scope of that task order and provide increased support for the defined task areas of the task order PWS. Surge amounts will be defined at the task order level. In the event the Government does elect to exercise the Surge Option, surge support will be realigned under new or existing CLINs for the relevant task areas identified in the task order PWS or SOW, and an equal amount will be deducted from Optional Surge CLIN 9999.

FOB: Destination

PSC CD: DA01

ESTIMATED COST

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

Award/Mod Effective Version Date Award To Be Determined (TBD)

Contract Number: TBD Task Order Number: N/A Contractor Name TBD Tracking Number: 632469573 Follow-on to Previous Contract and Task Order Number:

Electromagnetic Spectrum Situational Awareness (EMS SA):

W52P1J18DA045, HC104720F0010

1. Contracting Officer’s Representative (COR).

a. Primary COR. See Defense Information Technology Contracting Organization (DITCO) Additional Text G1 - Points of Contact

b. Alternate COR. See DITCO Additional Text G1 - Points of Contact

c. Property Administrator (PA). See DITCO Additional Text G1 - Points of Contact

2. Contract Title.

Spectrum Information System (SIS) Sustainment and Enhancement NOTE: This is the base requirement for the indefinite delivery/indefinite quantity (ID/IQ). Individual task orders will be defined and awarded under this overarching requirement.

3. Background.

The Defense Information Systems Agency (DISA) Program Executive Office (PEO) Spectrum must sustain the Spectrum Information System (SIS) capabilities along with other various Department of Defense (DoD) supported agencies and organizations within the Global Electromagnetic Spectrum Information System (GEMSIS) environment as described in the software baseline. This requirement will support and sustain the training, operations, maintenance, test, and enhancements of the current server, and software/system architecture. This shall include maintaining the systems usability, data administration activities, security posture, system administration and documentation, development of administrative interfaces, automation of data ingest, ingest of additional data sources, and additional User Interface (UI) customization for both the Non-Secure Internet Protocol Router Network (NIPRNet) and Secure Internet Protocol Router Network (SIPRNet).

GEMSIS is a National Security System (NSS) used by DoD to provide spectrum related data to support strategic and tactical electromagnetic spectrum operations. The system provides a suite of tools for accessing, exchanging, visualizing, and analyzing DoD and related Electromagnetic Spectrum (EMS) data needed for planning, deciding, directing, and executing operations.

The baseline software for this effort consists of:

Integrated spectrum desktop (ISD): A centralized web portal capability that enables integration, interface, identify access, and authentication management; and federation of the GEMSIS and associated EMS capabilities on NIPRNet and SIPRNet.

End-to-End Supportability System (E2ESS): A web-based tool integrated into a common architecture with the Joint Spectrum Data Repository (JSDR) on NIPRNet and SIPRNet supporting the collection of spectrum-related parameter data for use in EMS functions and coordination processes and functions related to Spectrum Certification and Host Nation Coordination (HNC). E2ESS combines the following capabilities:

o Editor: Creates and maintains Spectrum Certification records.

o Integrated Web Services: Provides for cloud-based data exchanges with the National

Telecommunications and Information Administration (NTIA).

o Integrated Content Management System (Alfresco): Tracks the status of Spectrum Certification records as they move through the business process workflow. This capability creates and tracks spectrum supportability requests for host nation coordination and manages all the data content within the E2ESS application.

Joint Spectrum Data Repository (JSDR): A web browser application that operates on both NIPRNet and SIPRNet with the potential to also be deployed on the Joint Worldwide Intelligence Communication System (JWICS). JSDR is a DoD authoritative spectrum database that provides user access to a wide-variety of federated DoD, national, and international spectrum-related data through data exchange with other capabilities and queries (custom and universal). JSDR provides the user with integrated business analysis and modeling tools to compare, plot, quantify, render, and analyze customizable data sets from many sources. JSDR contains the following modules:

o Standard structured Queries o Universal Queries o Business Intelligence and Analytics, Content Management Information System o Satellite Line-of-Sight Heat Map analysis o 2-D and 4-D mapping interfaces engineering services based on terrain-based propagation modeling, and a terrain server.

JSDR is an integration of multiple Commercial-off-the-Shelf (COTS) products as well as custom JavaScript UI components. JSDR currently interfaces with multiple disparate data sources and capabilities (e.g. Background Environmental Information; Joint Equipment Tactical and Space database; intelligence data; Spectrum XXI; Electronic Warfare Planning and Management Tool; Spectrum Services Framework;

EMBM-J (Electromagnetic Battle Management -Joint) for synchronization of EMS data in addition to National Geospatial Agency (NGA) for obtaining map layers. JSDR currently has a Representational State Transfer (REST) Application Programming Interface (API) that can provide data to external systems in Standard Frequency Action Format (SFAF) and JavaScript Object Notation (JSON) formats.

Joint Equipment Tactical and Space (JETS) database: An EMS database and editor within the JSDR infrastructure containing operating parameters and unit to platform to equipment relationships for DoD spectrum dependent systems using an xml data model.

JSDR Strategic Planning and Analysis Dashboard Extensions (JSPADE): A capability that leverages JSDR native business intelligence and analytic engines on SIPRNet to produce dashboards for query and visualization of datasets for strategic and operational use cases.

JSDR Data Extraction tool: A capability that utilizes and extracts all relevant spectrum parametric data from E2ESS SSRF xml format for analytics and post processing. The xml parser maintains hierarchical data relationships found within the E2ESS schema and provides an intuitive GUI design.

Joint Interference Reporting System Online (JSIRO): A SIPRNet capability that provides semi-automated/automated business workflow with automated notifications, dashboards, and data repository enabling DoD to report and visualize electromagnetic interference events for use within platform and by other systems via machine-to-machine and API connections and exportable files (e.g. JSON, xml, CSV).

World Radio Conference tool (WRC): A business workflow and visualization capability that tracks WRC agenda items, assessed operational risk, and risk burn indexed to specific WRC-related actions within the NIPR common environment.

4. Objectives:

The objective of this requirement is to support the sustainment, maintenance, operation, enhancement, and training of the baseline software capabilities described above by leveraging the existing operational enterprise capability within the DISA Stratus NIPRNet and SIPRNet cloud environment. These capabilities have been assessed to meet DoD operational requirements which will need to be sustained and expanded to further meet the operational spectrum needs of the DoD. This requirement shall support the extension of the current software architecture, data storage, and feature sets supporting the integration of additional data sets and analytics. This contracting effort includes tasks for accelerating the development and maintenance of blue system data, improving the data development processes and visualization features, enhancing the databases, and adding additional data sources for the planning and execution of joint electromagnetic spectrum operations.

5. Scope.

This requirement provides for the operations, maintenance, sustainment, enhancement, and training of EMS software capabilities for the DoD and interfacing with NTIA, these services may include:

Operating, sustaining, and maintaining existing baseline software capabilities.

Enhancing software usability and streamline sustainment, to include the implementation of agile Development, Security, Operations (DevSecOps) pipeline to support NIPRNet, SIPRNet and JWICS.

Maintaining and enhancing capabilities to query and download data sets, to store and retrieve documents, and to perform analytics on data sources, while working with the customer base to address Change Requests (CRs).

Importing and maintaining extensive data on spectrum dependent equipment and spectrum usage to support tactical, training, or sustaining-base operations, operational assessments, and research and development efforts, and populating the unstructured repository with documentation of interest for the spectrum community.

Extending the capabilities of the current baseline software capabilities following agile software development and DevSecOps best practices to ensure PWS requirements are met and are within cost and schedule.

Integrating additional data and provide user access, filtering options, analytical tools to characterize and gain situation awareness of the data.

Providing intuitive, configurable, layered, filterable, User Defined Operational Picture (UDOP) for display and analysis of data using engineering services.

Supporting technical exchange meetings (TEMs) between subject matter experts (SMEs) and the other agencies (e.g. NTIA) in support of evolutionary data exchange enhancements.

Providing management and engineering support for leveraging the architecture and products to address the Program Executive Office (PEO), Spectrum (PEO Spectrum) and external customer spectrum analytics in parallel with technical requirements.

The contractor shall provide all personnel, equipment, tools, materials, vehicles, supervision, and other items necessary to perform the tasks outlines in this PWS and specified in the task order issued under this contract.

This requirement shall leverage the current software architecture and products to perform DoD spectrum analytics, national and international strategic planning, and answer rapid data calls for PEO Spectrum and external customers.

The contractor shall provide personnel, tools, and other items necessary to perform these optional tasks without impacting the performance of the PWS primary tasks. Additional extensions to the GEMSIS (ISD, JSDR, E2ESS) software base include the Joint Spectrum Interference Reporting Online (JSIRO) tool (Task 17), the Stepstone Query capability (Task 18), the JSDR Strategic Planning and Analysis Dashboard Extensions (JSPADE) (Task 19), the World Radio Conference (WRC) Strategic Planning Tool (SPT) (Task 20).

Wherever possible, integration with COTS, other Government-off-the-Shelf (GOTS), and DoD capabilities will be accomplished instead of developing custom software.

This requirement shall accommodate future expansions, changes, or be revisions due to upgrades to systems resulting from technology evolution, industry standard changes and DoD regulatory requirements.

The Government may require surge support during the base or any option period, and surge modifications will be within the scope of the contract and provide increased support for the defined task areas of this PWS. Surge support over the life of the contract will not exceed 45% of the contractor’s total proposed cost/price for the base and all option periods, excluding any six-month extension of services pursuant to Federal Acquisition Regulation (FAR) 52.217-8.

6 Performance Requirements.

The JSDR system is composed of the following four Computer Software Configuration Items (CSCIs).

Access Control CSCI Data Service CSCI Analytics CSCI User Interface/User Experience (UI/UX) CSCI

Each CSCI is described in Appendix 1 - Computer Software Configuration Items, to aid in understanding the GEMSIS architecture and system documentation. Reference diagrams are included in Appendix 2 – System Architecture Diagrams. The ISD serves as the landing page for the GEMSIS enclave and provides users links to a variety of spectrum resources as well as spectrum and news related widgets. The goal for JSDR is to provide universal, standardized, layer-based display and manipulation of data containing a frequency component. The data may originate in disparate data sources. However, the goal for JSDR is to provide one common place where that data can be visualized and analyzed regardless of the user’s role within the spectrum community.

CSCIs shall comply with in place endpoint APIs within the JSDR. Any proposed modifications to the current architectures shall be identified within the first 60 business days to include COTS change out, additional servers or server capacity, etc.

The contractor shall ensure that the architecture framework allows integration of additional engineering services and propagation loss models and associated algorithms in the future with minimal level of effort. The current APIs utilizes an open interface using web services over standard ports. JSDR extensions should also maximize utilization of web services over standard ports to the degree possible for data exchange. The current JSDR provides engineering services to support coverage analysis (i.e., calculation and map overlays of signal strength), point-to-point link analysis, and satellite line-of-sight analysis considering terrain or earth curvature blockage. The contractor shall maximize speed for JSDR engineering services. The contractor shall enable engineering analytics to be able to predict areas and times for congestion/interference, predict and deconflict Joint Restricted Frequency List (JRFL) conflicts, and assess impact of hostile jamming with minimal operator input required. The contractor shall implement, deliver, and deploy software changes into the Government Master Repository (GMR) using agile and DevSecOps software development life cycle (SDLC) best practices.

The contractor shall provide a Technical Data Package (TDP) or TDP Updates with each software release based on Appendix 3 – TDP Reference Documentation.

TDP Reference Documentation Engineering and design-related information are provided in a reference library as part of this PWS to support the bidding process. Reference documents are provided in the form of Technical Data Package (TDP) that include documents such as System and Sub-System Design Description, Interface Design Description (IDD), Interface Control Document (ICD), and User/Administrative Help manuals. There are four TDPs for JSDR, one for each CSCI listed in this section and in Appendix 3 – TDP Reference Documentation.

TDP Documentation Updates The contractor shall update the content of TDP documentation as necessary during the execution of the contract to reflect changes in software and system design, training, administrative updates, or changes related to COTS and GOTS. TDP documentation that may require updating are those included as part of the reference documentation in Appendix 1 and Appendix 3 – TDP Reference Documentation.

Changes to the architecture may impact documents in multiple TDP. Software updates may also affect more than one TDP document. The contractor shall incorporate all relevant changes to be made as necessary in the TDP document to keep documentation current with the operational baseline software systems.

Source Code The contractor shall formally deliver updated source code for bug fixes, enhancements, or other approved requirements, prior to deployment for functional and security testing and accreditation. Under no circumstance shall source code developed under this PWS contain, rely on, or otherwise use proprietary information without prior written Government approval regardless of the category of proprietary information. Existing source code will be provided after the requirement is awarded.

TDPs shall include the following:

Installation Package (IP): The IP shall include all executables, installers, scripts and/or data needed for a full install and full uninstall. The installs shall be fully automated and include a “silent install” option (i.e., an option that does not require user interaction).

Installation Guide: The Installation Guides shall identify all the settings, steps for manual installation;

Source Code Package (SCP): The SCP shall contain all source codes, schemas, scripts, libraries, data, and instructions needed to rebuild the executables and install package.

Software Requirements Specification (SRS): The SRS shall meet all DI-IPSC-81433A requirements;

IDD and ICD: The IDD and ICD shall address all machine-to-machine interfaces (e.g., file imports, exports, web service interfaces);

System Design Documentation (SDD): - The SDD shall include a System Design Description conforming to Data Item Description (DID) DI-IPSC-81435A, and any other "contractor defined format" documents needed to describe the design and compliance with security requirements;

Requirements Traceability Matrix (RTM): The RTM shall map the requirements in the high-level requirements document, to the requirements in the SRS, to the software component(s), and to the test cases;

Risk Management Framework (RMF) documentation: The RMF documentation shall have traceability with the Security Controls Traceability Matrix (SCTM), Security Technical Implementation Guide

(STIG) checklists, source code review, data type data flow diagrams, network and database access analysis, and all phases of Information Assurance (IA);

Test Plan: The Test Plan shall utilize test descriptions that follow DI-IPSC-81439A Software Test Description (STD). The Test Plan shall include test cases, scripts, data, and all software and data required for the Government to independently execute the automated and manual test cases. The contractor shall include test reports, documenting the results of the contractor’s testing;

A Software Installation Plan (SIP);

Installation guide;

Software Version Description (SVD);

Request for Change (RFC) documentation;

Maps and data needed;

Other data and documentation (e.g., Information Assurance (IA) documentation);

Code Reviews Results; and Software Vulnerability Assessment Report.

User-training materials shall be delivered and updated with each release. The work performed under this contract shall meet Key Performance Parameter (KPP) requirements. The software shall work with all browsers available to DoD as configured with applicable STIGs.

All TDP artifacts shall be delivered in editable file formats. If a locked version of the file is required, an editable unlocked version shall also be provided.

6.1 Task 1 – Task Order Management.

The contractor shall provide the management, personnel, planning, and coordination support necessary to accomplish all work requirements specified at the contract and task order level.

The contractor shall provide a Program Manager to oversee, coordinate, and provide leadership and the controls necessary to manage all task order activities under the ID/IQ contract. The Program Manager shall manage deliverable targets, maintain staffing at levels required to satisfy customer requirements, team and/or subcontract as needed, budget, risks, and interface directly with Government leaders for all supported areas, and exercise control over assigned task personnel. The Program Manager must have the appropriate security clearance to access up to Top Secret (TS)/Secret Compartmented Information (SCI).

Project managers and technical staff are required to formally manage, track, and report project activities with respect to schedule, cost, risk, and key milestones in accordance with established Government business processes and direction from the Government. The contractor’s management effort shall include administration, program controls, product effectiveness, data and configuration management, risk and issue management, subcontract management, staff management, and security management. The contractor shall insure that all staff members comply with mandatory contractor training requirements. The Project Manager must have the appropriate security clearance to access up to Top Secret (TS)/Secret Compartmented Information.

The contractor shall identify and utilize software development-related best practices for all software activities specified at the contract and the task order level. This includes requirements definition and analysis, software design and design documentation, code development, maximum use of automated testing, documentation and inspection, user interface development and inspection, testing (verification and validation (V&V)), configuration management, interface definition and controls, risk management, quality management, scheduling, and all planning. The contractor shall ensure their software development-related processes and procedures used for any tasks specified at the task order level are documented, and the processes include continuous process improvement.

The contractor shall prepare an SRS and a Preliminary Design Review (PDR) (deliverables for Task 2) for each major sprint for approval by the GEMSIS Program Manager and the COR specified at the contract and task order level.

The contractor shall supply all subject matter expertise required to accomplish all tasks specified at the contract and task order level, including in the areas of: data science, database administration and management, spectrum management, spectrum engineering, electronic warfare, intelligence data, Joint Electromagnetic Spectrum Operations (JEMSO), E2ESS operations, JSDR operations, blue force SDS equipment and parametric data, IA expertise, information technology (IT) expertise, system/software engineering, and web browser applications.

The contractor shall comply with the Government’s Configuration Management Plan and use configuration management and change management systems to ensure product version control is in place. As new capabilities are demonstrated, tested, and fielded, the user community shall be able to make CRs through the Configuration Management process, including the Baseline Control Board (BCB). The user community consists of stakeholders, the Configuration Control Board (CCB), the Project Control Board (PCB), and the Program Management Office (PMO). Stakeholders will contribute suggestions for software and data changes to GEMSIS throughout the life of this requirement. The Configuration Control Board (CCB) and Project Control Board (PCB) evaluate and prioritize requirements, and the GEMSIS Program Management Office (PMO) defines the software release contents based largely on the CCB and PCB input. The contractor shall maintain all CRs, and product version records specified at the contract and task order level.

The contractor shall conduct both functional and physical configuration audits on the development and production environments and provide audit results to the Government specified at the contract and task order level.

Configuration management of TDPs shall occur in the approved DoD enterprise collaboration/interoperability and IT project management services, and on delivered Digital Video Disks (DVDs) or via Government approved electronic means. A TDP is not considered delivered until it is provided to the COR and loaded into the DoD repository (e.g. Confluence, Git repository).

6.1.1 Subtask 1: Kick-Off meetings. The contractor shall prepare and conduct kick-off meetings. These events are intended to establish a common understanding of TO requirements, schedule details, and expectations.

6.1.2 Subtask 2 – Task Order Management Reviews (TOMRs). Product TOMRs will be conducted monthly and cover all aspects of quality, resource utilization, and funding/invoicing. The contractor shall track and provide a presentation on all efforts/activities performed at the contract level and across all task orders. The review presentation shall address financial status (planned vs. actual), staffing levels, task costs, sprint costs, variances, organizational structure, work breakdown structure, schedule, risk, and quality issues for the contract/task orders.

TOMR presentation materials shall be provided to the COR as specified in the task order. The contractor shall make COR requested changes to the TOMR presentation format and content within ten business days as specified in the task order. All changes to the TOMR presentation material must be finalized and approved by the Government prior to conducting the monthly TOMR. The contractor shall document all issues and risks in the TOMR that could cause problems with the software development lifecycle, sustainment, operational support, or operational availability of the web applications. Issues and risks identification shall include probability, consequence, and mitigation approach information.

Non-Disclosure Agreements (NDA) shall be required by all personnel performing on all awarded task orders. The contractor is responsible for identifying that all personnel, to include any new personnel on the contract and task orders, have executed the DISA provided NDAs in accordance with the timeline stated in the task order PWS. The contractor shall track and provide an updated list of NDAs every TOMR. The contractor shall report on the status of staff completion of mandatory training.

6.1.3 Subtask 3 - Interim Progress Reviews (IPRs). The Government will conduct bi-weekly IPRs as specified in the task order. The contractor shall prepare agendas and presentation materials for the IPRs for all efforts within this PWS. The IPRs shall summarize ongoing activities, accomplishments, deliverable statuses, and issues. The contractor shall prepare meeting minutes based on the content of the actual meetings, to include a synopsis of discussion and action items and list of participants. These minutes and actions shall be reviewed, and statuses incorporated in the next IPR.

6.1.4 Subtask 4 - Integrated Master Schedule (IMS). The contractor shall develop and maintain an integrated master schedule using Microsoft Project to track and monitor task activities as specified in the task order. The IMS shall include logically networked program activities and dependencies. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, and activities from task order award to the completion of this requirement. The IMS shall clearly link all subsystems and related activities for deployments to support operations and sustainment planning. The contractor shall quantify risk in hours, days, or weeks of delay and provide most likely duration for each IMS activity and event. The contractor shall work with the GEMSIS program office staff to deconflict and coordinate deployment tasks and maintenance releases.

6.1.5 Subtask 5 - Technology Report. The contractor shall provide a technology report identifying all technologies embedded in the system and used by the contractor for the development, testing and operations of the systems. The report shall contain the following for each technology: source, purpose, version utilized, software licenses, end of support information (i.e., Dates, Options and Costs for extended support), and a proposed approach for addressing technology obsolescence with related Non-Developmental Item (NDI) cost information. The contractor shall notify the Government in writing and receive approval before adding any new technology into the software baseline (i.e., any new technology required for development, testing or operations).

6.1.6 Subtask 6 - Technical Exchange Meetings (TEMs). The contractor shall support approximately 12 Government site visits to the contractor facility per year for Government review of management processes, development processes, test activities, configuration control of software and TDP products, and the monitoring and disposition of defect/problem reports.

The contractor shall provide demonstrations of software, as requested by the Government, for a variety of audiences.

The audience shall include the technical staff as well as senior leadership. The contractor shall support technical interchange meetings, and customer engagements at either the contractor site, PEO SPECTRUM, DISA Headquarters (HQ), Pentagon, or locations requiring travel. (See Task 2). The contractor shall document meeting minutes, outcomes, and action items. The contractor shall support the Government as required supplying updated information/materials/slides for presentation to external parties and senior leadership.

Deliverables:

PWS

Task#

Deliverable Title Format Due Date Distribution/Copi es

Frequency and Remarks

6.1 PCB

Presentations

Government- Approved Format (GAF)

As specified at the task order level.

COR As specified at the task order level.

6.1 Functional and

Physical Configuration Audits

Government Specified/Suppli ed Format (GSF)

As specified at the task order level.

Standard Distribution*

As specified at the task order level.

6.1.1 Kick-off Meeting Contractor-

Determined Format

As specified at the task order level.

COR As specified at the task order level.

6.1.2 TOMRs Contractor-

Determined and

GAF

As specified at the task order level.

COR As specified at the task order level.

6.1.3 IPRs Contractor-

Determined and

GAF

As specified at the task order level.

COR As specified at the task order level.

6.1.4 IMS Microsoft Project As specified at the

task order level.

COR As specified at the task order level.

6.1.5 Technology

Report

Contractor- Determined and

GAF

As specified at the task order level.

COR As specified at the task order level.

6.1.6 Customer

Engagement and Demonstration

Contractor- Determined and

GAF

As specified at the task order level.

COR As specified at the task order level.

6.1.7 Meeting

Materials

Contractor- Determined and

GAF

As specified at the task order level.

COR As specified at the task order level.

* Standard Distribution: One copy of the transmittal letter with the deliverable to the Primary COR and GEMSIS Configuration Manager. Deliverable and transmittal letter stored in accordance with the GEMSIS Configuration Management Plan.

6.2 Task 2 – Transition-In/Transition-Out of Contract and Continuity of Services.

The objective of the transition-in and transition-out task areas is to ensure continuity of services during the transition between the ID/IQ effort and/or specific task orders.

6.2.1 Subtask 1 - Transition-In. The contractor shall execute a smooth and seamless transition-in, ensuring continuity of services as specified, if appropriate, at the task order level.

6.2.2 Subtask 2 - Transition-Out. The contractor shall execute a smooth and seamless transition-out, ensuring continuity of services as specified, if appropriate, at the task order level.

During the contract transition, the incumbent contractor shall coordinate with and provide training to the follow-on contractor, and support the contract transition as directed by the COR.

Deliverables:

PWS

Task#

Deliverable Title Format Due Date Distribution/Copi es

Frequency and Remarks

6.2.1 Transition-In

Plan

Contractor- Determined and

GAF

First draft due on the 14th business day after task order award date.

COR As specified at the task order level.

6.2.2 Transition-Out

Plan

Contractor- Determined and

GAF

Four months prior to end of the task order PoP.

COR As specified at the task order level.

* Standard Distribution: One copy of the transmittal letter with the deliverable to the Primary COR. Deliverable and transmittal letter stored with GEMSIS Configuration Management (CM) according to the GEMSIS Configuration Management Plan.

6.3 Task 3 – Engineering Support and Outreach.

TS/SCI clearance is required for the contractor to obtain appropriate access to JWICS. The contractor must have access to SIPRNet and JWICS to successfully perform work under this task. This access is required to enable assessment of technical integrations and cross domain solutions for JSDR between NIPRNet, SIPRNET, and

JWICS.

6.3.1 Subtask 1 – Sprint Planning

The contractor shall collaborate with the GEMSIS PMO, product leads and external stakeholders to perform requirements analysis and develop sprint plans that meet requirements. This includes collaborative software development and support. Sprint plan execution may include collaboratively developing software and TDP materials with other projects, programs, and contractors.

Sprint Plans. The contractor shall develop sprint plans that implement the requirements. The contractor shall plan and track sprint releases in the IMS.

• The contractor shall conduct sprint planning and deliver sprint plans per the COR approved IMS delivery schedule.

• Each sprint plan shall include an updated SRS for each sprint. These documents shall identify which requirements are to be satisfied by the current sprint and identify requirements satisfied by previous sprints.

The SRS shall conform to DID DI-IPSC-81433A.

• The sprint plans shall identify requirements implemented and requirements remaining to be implemented.

• The sprint planning shall include requirements analysis for each sprint, and the results shall be documented in the SRSs. The contractor shall ensure the SRS requirements are clear, complete, verifiable (i.e., testable), and unambiguous.

• This task includes requirements analysis and coordination to analyze, refine and validate the CSCI requirements.

• The contractor shall identify impacts to the following in all sprint plans: System Architecture, Software, Hardware, Licensing/Cost, Security / IA, System Performance, Interfaces, Interoperability and Backwards Compatibility, Data, Data Migration, Reliability, Availability, and Maintainability (RAM), Training, Training Materials, Software Documentation, System Administration documentation, Help Desk documentation, Business Process, Installation, and Deployment process on all target platforms and networks.

• The contractor shall ensure COTS or GOTS used in the system meets system and IA requirements.

• The contractor shall set up periodic meetings with the Government to coordinate sprint planning and review sprint progress.

The contractor’s established sprint plans must be approved by the Government. The contractor shall develop software under this contract using an agile development methodology to comply with the PWS requirements. Sprint planning shall be conducted under task 6.3 Engineering Support and Outreach, and sprint execution shall be conducted under task 6.4 Software Maintenance and Enhancement. The contractor shall prepare an SRS and a PDR for each sprint plan for approval by the GEMSIS Systems Engineer and the COR. The contractor shall provide materials for each sprint and other formal meetings at least one-week before the corresponding meeting. The contractor shall obtain written approval from the COR before adding any software development, software testing or system operations technologies to the technology baseline. CRs to be included in sprints will be determined and prioritized through the PCBs and CCBs. The CCB and PCB evaluate and prioritize requirements, and the GEMSIS PMO defines the release contents based largely on the CCB and PCB inputs.

CRs to be included in sprints will be determined and prioritized through sprint prioritization working groups. The Government user representative will provide prioritized requirements. The GEMSIS PMO defines the release contents based largely on the prioritized requirements and sprint prioritization working group inputs.

6.3.2 Subtask 2 – Data Analysis

The contractor shall evaluate Government designated data sources and work with Government SMEs to develop and document a data integration strategy including data correlation across various sources to ensure comprehensive and actionable insights, and capability to automatically ingest data from originating sources, and/or query and display data from federated data sources. The contractor shall evaluate data formats and compatibility with existing data requirements and standards and establish the methodology to integrate. The contractor shall leverage or develop an interface as well as a process to extract the data from identified external data sources, transform it as needed to map to JSDR, and enable access to it from the JSDR environment, maximizing automation. The contractor shall create CRs to integrate these changes to the baseline. The contractor shall implement processes that minimize and simplify efforts in administration and maintenance of the ingest function. The system will provide audit access for data connections and/or downloads. The contractor shall configure the system to log data access, including user identification, date and time of access, and the query being performed. The contractor shall develop ICDs for external interfaces, to be delivered with TDPs.

The contractor shall develop a strategy for evaluating and managing data content within the software to meet DoD Chief Digital and Artificial Intelligence Office (CDAO) data requirements. This strategy will contain recommendations for data review, data retention, and data governance policies. This will include such assessments as leveraging metadata as necessary to maintain traceability of the data (searchable, source, etc.) as well as potential rule sets for determining best sources of data when disparate sources conflict. The contractor shall document this strategy in a Content Management Data Strategy deliverable.

6.3.3 Subtask 3 – Outreach

The contractor shall participate in TEMs with interfacing data provider organizations, service EMS programs, external systems, and stakeholders, as required to support software operations, sustainment, and enhancements.

TEMs will be required approximately one per month or as specified in the task order, which may require travel, and occur with other Government programs and organizations including (but not limited to): Electronic Warfare Planning and Management Tool (EWPMT), Spectrum Services Framework (SSF), Fusion Analysis Development Effort (FADE) – Multiple Intelligence Spatial Temporal (MIST) (FADE-MIST), Global Combat Support System – Joint (GCSS-J), Integrated Broadcast Service (IBS), Real Time Spectrum Operations (RTSO), System Planning Engineering and Evaluation Device (SPEED), Joint SATCOM (Satellite Communications) Management and Planning System (JSMPS), Joint Integrated SATCOM Tool (JIST), etc. The contractor shall support quarterly Electromagnetic Spectrum Data Community of Interest (ESDCoI) working group meetings on-site at PEO Spectrum locations at DISA Ft. Meade, Maryland and/or PEO-SPECTRUM Annapolis, Maryland. The contractor shall provide demonstrations of software capabilities as requested by the Government.