HC1047-19-R-0010_N4143.pdf

PDF 2 MB Posted Nov 1, 2019

Attached to: Advanced Wireless Services-3 (AWS-3) 2025-2110 Megahertz (MHz) Spectrum Management/Coordination System (SMCS)
Solicitation number: HC104719R0010
Issued by: Defense Information Systems Agency

About this file

Written by GovTribe AI · Dec 28, 2023

This document provides details for a federal contract solicitation seeking support services for spectrum management coordination. The solicitation will be released on or about October 25, 2019 via FBO.gov for the Advanced Wireless Services-3 (AWS-3) 2025-2110 Megahertz (MHz) Spectrum Management/Coordination System (SMCS). The contractor shall provide an integrated system to automate coordination of spectrum access between DoD systems and incumbent broadcast operations in the 2025-2110 MHz band. The contractor must utilize agile development and continually enhance the coordination system to address evolving requirements over a base period of performance plus four option years. The contractor shall manage software development, system operations and sustainment. The Defense Information Systems Agency - National Capital Region is the procuring agency.

From the source

RFP_HC104719R0010

View the file

Other files

File	Type	Posted
Question_From_Industry_SMCS_12102019.xlsx	XLSX spreadsheet	Dec 10, 2019
Question_From_Industry_SMCS_12042019.xlsx	XLSX spreadsheet	Dec 4, 2019
HC104719R0010_AMD03_SMCS_N4143_12042019.pdf	PDF	Dec 4, 2019
Question_From_Industry_SMCS_11272019.xlsx	XLSX spreadsheet	Nov 27, 2019
HC104719R0010_AMD02_SMCS_N4143_11272019.pdf	PDF	Nov 27, 2019
9- User Accounts Master List Template (DoD).xlsx	XLSX spreadsheet	Nov 21, 2019
10- User Accounts Master List Template (NAB-SBE).xlsx	XLSX spreadsheet	Nov 21, 2019
2- SMCS Operational Requirements.pdf	PDF	Nov 21, 2019
N4143 Hybrid Price Template 21NOV2019.xlsx	XLSX spreadsheet	Nov 21, 2019
5- SMCS Future Objectives List.pdf	PDF	Nov 21, 2019
8a- 2025-2110MHz ENG Data Snapshot.pdf	PDF	Nov 21, 2019
HC104719R0010_AMD01_SMCS_N4143_11212019.pdf	PDF	Nov 21, 2019
Question_From_Industry_SMCS_11212019.xlsx	XLSX spreadsheet	Nov 21, 2019
8b- 2025-2110MHz ENG Data Dictionary.pdf	PDF	Nov 21, 2019
6- SMCS Background Info.pdf	PDF	Nov 21, 2019
3- SMCS Software Requirements.pdf	PDF	Nov 21, 2019
7- SMCS User Procedures Guide.pdf	PDF	Nov 21, 2019
8c- 2025-2110MHz ENG Data ReadMe (1).pdf	PDF	Nov 21, 2019
1- SMCS Reading Room - GFI List.xlsx	XLSX spreadsheet	Nov 21, 2019
8b-_2025-2110MHz_ENG_Data_Dictionary.pdf	PDF	Nov 5, 2019
8c-_2025-2110MHz_ENG_Data_ReadMe.pdf	PDF	Nov 5, 2019
2-_SMCS_Operational_Requirements.pdf	PDF	Nov 5, 2019
8a-_2025-2110MHz_ENG_Data_Snapshot.pdf	PDF	Nov 5, 2019
9-_User_Accounts_Master_List_Template_(DoD).xlsx	XLSX spreadsheet	Nov 5, 2019
6-_SMCS_Background_Info.pdf	PDF	Nov 5, 2019
1-_SMCS_Reading_Room_-_GFI_List.xlsx	XLSX spreadsheet	Nov 5, 2019
4-_SMCS_Reference_Architecture-v1.0.mdzip	—	Nov 5, 2019
3-_SMCS_Software_Requirements.pdf	PDF	Nov 5, 2019
7-_SMCS_User_Procedures_Guide.pdf	PDF	Nov 5, 2019
Question_Template_SMCS.xlsx	XLSX spreadsheet	Nov 5, 2019
5-_SMCS_Future_Objectives_List.pdf	PDF	Nov 5, 2019
HC104719R0010_SMCS_N4143_11052019.pdf	PDF	Nov 5, 2019
10-_User_Accounts_Master_List_Template_(NAB-SBE).xlsx	XLSX spreadsheet	Nov 5, 2019
DD254_Initial.pdf	PDF	Nov 1, 2019
Past_Performance_Worksheet.doc	DOC document	Nov 1, 2019
Consolidated_Product_List.xls	XLS spreadsheet	Nov 1, 2019
NDA_SMCS.docx	DOCX document	Nov 1, 2019
N4143_Hybrid_Price_Template.xlsx	XLSX spreadsheet	Nov 1, 2019
Initial_QASP.docx	DOCX document	Nov 1, 2019

Show all 39

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

CODE

(Hour)

PAGE(S)

until local time

A X B X C

X G F 114

X H 116 - 118 franky.m.awuvey.civ@mail.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

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

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

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

1 118

(If other than Item 7)

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

AND

ADDRESS SIGN OFFER (Type or print)

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 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)

FRANKY M. AWUVEY 301-225-4519

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 19

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT

PACKAGING AND MARKING

20 - 52 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

54 - 55 X K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 56 - 57 X

SPECIAL CONTRACT REQUIREMENTS

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

61 - 113

PART II - CONTRACT CLAUSES

DISA/CONTRACTS-NCR

6914 COOPER AVE

FORT MEADE MD 20755-7090

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.

N4143

5. DATE ISSUED

01 Nov 2019

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

HC104719R0010

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 12 Months Task 1 - Program Management

FFP

The contractor shall provide labor to complete the requirements specified in the Advanced Wireless Services-3 (AWS-3) 2025-2110 Megahertz (MHz) Spectrum Management/Coordination System (SMCS) Performance Work Statement (PWS).

FOB: Destination

PURCHASE REQUEST NUMBER: N4143

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0002 1 Lot Task 2 - SMCS Development

CPFF

(PWS).

FOB: Destination

PURCHASE REQUEST NUMBER: N4143

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0003 1 Lot Task 3 - SMCS Operations and Maintenance

CPFF

(PWS).

FOB: Destination

PURCHASE REQUEST NUMBER: N4143

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0004 12 Months Task 4 - Disaster Mitigation Support

FFP

FOB: Destination

PURCHASE REQUEST NUMBER: N4143

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0005 12 Months Task 5-Transition-Out & Cont of Service

FFP

FOB: Destination

PURCHASE REQUEST NUMBER: N4143

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0006 1 Lot Travel

COST

Travel shall be in support of the tasks in the Advanced Wireless Services-3 (AWS-3) 2025-2110 Megahertz (MHz) Spectrum Management/Coordination System (SMCS) Performance Work Statement (PWS). No profit shall be paid on purchases or on travel made under this CLIN. DCAA approved burden rates are authorized. 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.

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

FOB: Destination

PURCHASE REQUEST NUMBER: N4143

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0007 1 Lot Other Direct Costs (ODC)

COST

ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable. ODCs may be purchased from General Service Administration (GSA) Schedules or Enterprise Software Initiative (ESI), if available and authorized by the Contracting Officer. ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved in writing by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31.

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

FOB: Destination

PURCHASE REQUEST NUMBER: N4143

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

1001 12 Months OPTION Task 1 - Program Management

FFP

FOB: Destination

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

1002 1 Lot OPTION Task 2 - SMCS Development

CPFF

(PWS).

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

1003 1 Lot OPTION Task 3 - SMCS Operations and Maintenance

CPFF

(PWS).

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

1004 12 Months OPTION Task 4 - Disaster Mitigation Support

FFP

FOB: Destination

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

1005 12 Months OPTION Task 5-Transition-Out & Cont of Service

FFP

FOB: Destination

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

1006 1 Lot OPTION Travel

COST

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

1007 1 Lot OPTION Other Direct Costs (ODC)

COST

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

FOB: Destination

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

2001 12 Months OPTION Task 1 - Program Management

FFP

FOB: Destination

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

2002 1 Lot OPTION Task 2 - SMCS Development

CPFF

(PWS).

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

2003 1 Lot OPTION Task 3 - SMCS Operations and Maintenance

CPFF

(PWS).

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

2004 12 Months OPTION Task 4 - Disaster Mitigation Support

FFP

FOB: Destination

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

2005 12 Months OPTION Task 5-Transition-Out & Cont of Service

FFP

FOB: Destination

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

2006 1 Lot OPTION Travel

COST

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

2007 1 Lot OPTION Other Direct Costs (ODC)

COST

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

3001 12 Months OPTION Task 1 - Program Management

FFP

FOB: Destination

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

3002 1 Lot OPTION Task 2 - SMCS Development

CPFF

(PWS).

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

3003 1 Lot OPTION Task 3 - SMCS Operations and Maintenance

CPFF

(PWS).

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

3004 12 Months OPTION Task 4 - Disaster Mitigation Support

FFP

FOB: Destination

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

3005 12 Months OPTION Task 5-Transition-Out & Cont of Service

FFP

FOB: Destination

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

3006 1 Lot OPTION Travel

COST

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

3007 1 Lot OPTION Other Direct Costs (ODC)

COST

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

4001 12 Months OPTION Task 1 - Program Management

FFP

FOB: Destination

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

4002 1 Lot OPTION Task 2 - SMCS Development

CPFF

(PWS).

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

4003 1 Lot OPTION Task 3 - SMCS Operations and Maintenance

CPFF

(PWS).

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

4004 12 Months OPTION Task 4 - Disaster Mitigation Support

FFP

FOB: Destination

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

4005 12 Months OPTION Task 5-Transition-Out & Cont of Service

FFP

FOB: Destination

MAX

NET AMT

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

4006 1 Lot OPTION Travel

COST

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

4007 1 Lot OPTION Other Direct Costs (ODC)

COST

Refer to the CLIN Summary Tab of the Pricing Template Worksheet for the plug in number.

FOB: Destination

MAX COST

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

9999 UNDEFINED Lot OPTION SURGE Support

COST

The Government may require surge support during the base or any option period, and surge modifications will be in-scope to provide increased support for the defined task areas of the PWS. Surge support is OPTIONAL and is not a guarantee. Surge is NTE 10%.

FOB: Destination

See Exhibit A

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

as of 05 September 2019

Contract Number: TBD Task Order Number TBD Contractor Name TBD Tracking Number: N4143 Follow-on to Previous Contract and Task Order Number:

Not applicable. This is a new development effort.

1. Contracting Officer’s Representative (COR). Identified in Local Clause G1 – Points of Contact

2. Contract Title. Advanced Wireless Services-3 (AWS-3) 2025-2110 Megahertz (MHz) Spectrum Management/Coordination System (SMCS)

3. Background. This effort is required to support the spectrum management and coordination of the 2025-2110 MHz band as a result of the third Advanced Wireless Services (AWS-3) auction. In March 2014, the Federal Communications Commission (FCC), in collaboration with the National Telecommunications and Information Administration (NTIA), developed rules for the auction and reallocation of the 1695-1710 MHz and 1755-1780 MHz radio frequency bands, which at that time were allocated exclusively for Federal use. Between November 2014 and January 2015, the FCC conducted the third Advanced Wireless Services (AWS) auction (“Auction 97”) to establish new AWS licenses in the 1695-1710 MHz, 1755-1780 MHz, and 2155-2180 MHz bands. For reference, AWS-3 Transition information can be found at the following website: https://www.ntia.doc.gov/category/aws-3-transition.

The Defense Spectrum Organization (DSO) is responsible for providing common Department of Defense (DoD) services including the overarching capabilities and analyses required to implement the DoD’s Transition Plans. The Defense Information Systems Agency (DISA) - DSO Transition Plan includes six tasks:

• DISA1: 1755-1780 MHz Early Entry Portal

• DISA2: 1755-1780 MHz Federal Spectrum Management System Portal

• DISA3: 1780-1850 MHz Compression and Optimization Tool

• DISA4: 2025-2110 MHz Spectrum Management/Coordination System

• DISA5: 1755-1780 MHz Spectrum Sharing Test & Demonstration Program

• DISA6: DoD Spectrum Relocation Management Team (DSRMT)

The DSRMT oversees DSO activities being conducted under the DISA Transition Plan, including oversight of contracted work.

Under the DISA4 activities, and as part of the AWS-3 transition, selected DoD system operations are targeted to gain access to the 2025-2110 MHz band and operate on a co-primary status on a non-interference basis with incumbent Television Broadcast Auxiliary Service (BAS), the Cable Television Relay Service (CARS), and the Local Television Transmission Service (LTTS) operations. The SMCS will be used to facilitate spectrum sharing between the incumbent licensees’ operations, and the transitioning DoD system operations.

This effort will be a new start; however, the DSO has been conducting DISA4 planning with various stakeholders, to include the BAS and the office of the DoD Chief Information Officer. DSO has conducted multiple transition planning exercises and has enlisted contractor support for these planning activities under the T4140 – “2025- 2110MHz Coordination and Collaboration Support” contract.

4. Objectives: The primary objective of the SMCS Development Task Order (TO), is to provide an integrated system-of-systems that automates an end-to-end workflow for coordinating spectrum access between DoD system operations and incumbent Television BAS, CARS, and LTTS operations (hereafter referred to as Electronic News Gathering (ENG) operations).

The contractor shall apply an advanced working knowledge of spectrum engineering, spectrum requirements, data management, and business process workflow development to manage SMCS development, deployment, operations, maintenance, and continual enhancement services. The contractor shall manage the software development lifecycle, delivery and deployment of the initial SMCS capability, and continually enhance the SMCS. It is envisioned that the spectrum sharing of the 2025-2110 MHz will include a wide range of sharing scenarios, including cases where DoD access has been pre-coordinated with the ENG community, and cases where active coordination between DoD and the ENG community will be required. SMCS shall be able to facilitate these various sharing scenarios. The contractor shall implement industry standard agile development methodologies to develop and deliver the initial operational release of the SMCS, continuing to develop and deliver additional features and automation.

5. Scope. This requirement will provide an integrated system-of-systems that automates an end-to-end workflow for coordinating spectrum access between DoD system operations and ENG operations as defined in this PWS and applicable DoD guidelines. This requirement may in the future expand, change or be revised due to upgrades to systems as a result of technology evolution, industry standard changes and DoD regulatory requirements. It is the expectation of this requirement that the contractor shall continuously evolve this requirement in parallel with evolving and emerging technologies.

The contractor shall develop, deliver, operate, and sustain a web-accessible SMCS that will automate and facilitate the coordination process for the sharing of the 2025-2110 MHz band between DoD and ENG operations based on requirements over time. The SMCS shall include:

• A database of DoD and ENG operational and technical characteristics and coordination history.

• Automation of end-to-end business process coordination workflow and data exchange between authorized DoD and ENG stakeholders, including a tracking system of the coordination efforts.

• Analytical tools to determine interference-free (coexistence) operations between the DoD and the ENG operations in the 2025-2110 MHz band.

SMCS will evolve over the period of performance (PoP) to address the following DoD systems, in order of priority:

• TRR

• SUAS

• HRV

• TTNT

In accordance with Defense Federal Acquisition Regulation Supplement (DFARS) Subpart 227.72, the Government will retain Unlimited Rights for all SMCS software and SMCS deliverables developed under this effort. As a result, the Government may use, modify, release, reproduce, display or disclose any such software or deliverables created under this effort.

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 10% 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.

The initial operational release of SMCS will support the business process for coordinating DoD Tactical Radio Relay (TRR) operations with the ENG community, represented by the Society of Broadcast Engineers (SBE). The business process will likely evolve as DoD and the ENG community adapt to lessons learned while coordinating shared spectrum use.

A database of ENG and DoD operations (to include operational and technical characteristics of ENG and DoD systems), and business process transactions shall also be required for the initial operational release with data update capabilities provided to selected business process participants. The database shall also hold archival data and data at rest. The database shall support display/archive/export results and reports as defined by the requirements.

Beyond the initial version, additional Electromagnetic Compatibility (EMC) analysis capabilities shall be incorporated into SMCS to include, but not limited to Point-to-Point and composite path loss, and contours using industry standard models. The data analysis requirements shall become more robust as they evolve to support more complex spectrum sharing when ground based and airborne DoD capabilities with larger bandwidth requirements transition their operations to the 2025-2110 MHz band. DoD systems currently plan to transition operations into the

2025-2110 MHz band which include TRR, Small Unmanned Aerial Systems (SUAS), High Resolution Video (HRV), and Tactical Targeting Network Technology (TTNT). These analysis tools will need to be integrated with the database and automated workflow.

The Government anticipates future SMCS requirements to be driven by currently unknown user needs, and by the integration of advanced analytical algorithms and enhancements from other sources. An example could be the outcome of Spectrum Access Research and Development Program (SARDP) projects, that may provide improved reallocation and transition analysis techniques, to include DoD system enhancements. The contractor’s agile development methodology shall enable the Government to prioritize future SMCS enhancements.

6. Performance Requirements

6.1 Task 1 – Program Management (FFP) (Operations & Maintenance (O&M)): Program Management encompasses those activities necessary to effectively manage the SMCS development, operations, and sustainment effort. The contractor shall utilize industry best practices in the course of conducting program management activities.

The contractor shall provide personnel with the capabilities to develop and maintain SMCS, and possess experience and working knowledge of spectrum engineering and requirements, including at a minimum: EMC Coexistence Algorithms, Electromagnetic Interference (EMI) interactions, EMI between and related to spectrum-dependent systems, Electromagnetic Propagation, Electromagnetic Environmental Effects, and DoD and SBE spectrum management concepts and principals to include frequency allocation and assignment/licensing.

6.1.1 Subtask 1.1 – Program Management Planning and Reporting: The contractor shall manage the technical, cost, schedule, performance, and risk parameters to meet requirements.

The contractor shall deliver a Program Management Plan (PMP) that addresses the following topics: cost and invoice management; staff management, to include key personnel management; stakeholder (including DoD and SBE stakeholders) communication and management; risk, issue and opportunity (RIO) management; action item tracking; and technical management of SMCS development, operations, and sustainment.

For understanding and planning purposes, Key Personnel are those personnel necessary to accomplish requirements and are capable of leading program activities. At a minimum, Key Personnel shall include a Program Manager (PM) and a Technical Lead (TL). Key Personnel shall be documented in the Program Management Plan, and the contractor shall notify the COR and Contracting Officer (KO) of any Key Personnel changes within three (3) business days. All changes in Key Personnel shall be approved by the COR. The contractor shall replace personnel within 2 weeks.

The PM shall be the single management interface to the Government, shall manage and coordinate the development of SMCS and apply an operational understanding of DoD spectrum management business processes, frequency assignment, and user equipment information to the development effort. The PM shall also serve as an interface with other vendors and stakeholders on programmatic matters.

The TL shall be the technical interface to the Government, to include other vendors and stakeholders for technical matters. Additionally, the TL shall be the subject matter expert for studies, shall manage the contractor’s expertise in spectrum operations (from planning through to execution), to include applying the concepts and principles of:

current and emerging DoD and National Association of Broadcasters / Society of Broadcast Engineers (NAB/SBE) spectrum management business processes; spectrum deconfliction engineering analysis; frequency assignments; and emerging spectrum technologies (e.g., spectrum-dependent systems and related management systems). The TL shall manage business process improvement practices to reengineer spectrum management and interference analysis methodologies/principles and business process modernization projects.

The contractor shall deliver a Monthly Activity and Status Report (MASR) that includes a summary of: recent accomplishments, status of ongoing technical activities, and future activities for all tasks/subtasks in the contract/ task order; the status and progress of costs (planned vs actual), invoicing, and financial status; complete Government Furnished Information/Government Furnished Equipment/Government Furnished Software/Government Furnished (GFI/GFE/GFS/GFx) artifacts GFI/GFE/GFS/GFx inventory; schedule status; technical performance; actions;

metrics; and risks. For reporting purposes, metrics shall include:

Number of user stories selected for a time-boxed development increment (e.g., a development sprint), consistent with the contractor’s agile approach

Number of user stories completed during a time-boxed development increment, consistent with the contractor’s agile approach Number of bugs discovered after a release Definition of work elements consistent with the contractor’s agile approach (e.g., story points or work hours)

a. Total work elements committed to a time-boxed development increment, consistent with the contractor’s agile approach

b. Total work elements completed in a time-boxed development increment, consistent with the contractor’s agile approach

c. Planned cost per work element

d. Actual cost per work element

The contractor shall evaluate and present open RIOs in the MASR. The contractor shall describe agile development progress and status in each MASR.

The contractor shall provide monthly invoices, including detailed billing reports for all associated tasks and work completed each month. Monthly invoices shall mirror the contract POP dates based on award date and shall be submitted within thirty (30) days of the period (month) end. A FINAL INVOICE, capturing all outstanding expenses related to the correlating period of performance (POP), will be submitted within ninety (90) days of the completion of the POP (base year, option period, etc.) without exception. At a minimum, these reports shall include the number of labor hours charged per task and a list of any cost reimbursable purchases completed. Invoices shall be submitted to the Contracting Officer’s Representative (COR) for review and concurrence at least five (5) business days prior to submission into the required, automated system (currently: Procurement Integrated Enterprise Environment (PIEE), Wide Area Workflow (WAWF)).

The contractor shall manage RIOs for the program. The contractor shall evaluate and include open RIOs and any closed RIOs during the reporting period in the MASR. Those RIOs that require immediate Government attention shall be brought to the COR’s attention as soon as they are identified.

The contractor shall conduct a Kickoff Meeting within thirty (30) days of PoP start. This meeting shall fully address the technical requirements, the contractor’s plan and schedule for execution, management processes, agile development approach, and plan for the first shippable increment of the SMCS. The contractor shall present the integrated master schedule, and, after Government approval, establish the final schedule and performance baselines.

The contractor shall prepare and deliver Kickoff Meeting Materials and Kickoff Meeting Minutes in accordance with the delivery table for these CDRLs.

The contractor shall host Bi-weekly Status Reviews with the COR and DSO stakeholders. At each Bi-weekly Status Review, the contractor shall deliver a status presentation, and shall host and conduct a collaborative exchange among stakeholders. The Bi-weekly Status Review shall cover relevant topics, to include at a minimum: Agile backlog review, SMCS Development status, status updates of all technical activities, RIOs, future activities, technical issues, financial status, schedule status, actions, metrics, and any other topics of interest. These meetings will primarily be of a technical and programmatic nature, and shall be used to provide updates to and elicit requirements from stakeholders. The contractor shall use these opportunities to populate the SMCS product backlog. The contractor shall prepare and deliver Status Review Materials prior to each meeting and Status Meeting Minutes at the conclusion of each meeting.

For all in-person meetings and reviews, the contractor shall provide facilities capable of hosting meetings, and providing demonstrations (as appropriate). These facilities shall be within thirty (30) linear miles of the DSO Annapolis facility. The contractor shall provide logistical coordination for meetings, to include at a minimum:

scheduling rooms, enabling remote access to meetings, coordinating dates, inviting participants, developing and distributing agendas, maintaining action item lists, recording and distributing meeting minutes, conducting post meeting follow-up actions, etc. Remote access may include setting up Defense Collaboration Services, teleconference phone bridges, Wi-Fi/guest network access, web conferencing, etc.

6.1.2 Subtask 1.2: General Technical Support and Meetings: The contractor shall contribute to and/or host on average six (6) customer, technical and/or external stakeholder meetings per month, as directed by the COR. These meetings will primarily be of either a technical nature or programmatic update. Additionally, the contractor shall hold technical meetings in support of their proposed agile methodology. Meetings shall ensure that the stakeholder community, holistically, understands and contributes to key SMCS considerations, to include at a minimum: the current state of SMCS, required updates/changes to SMCS, timing of future releases, requests for information to/from stakeholders, and upcoming training events. The following table describes potential (but not all) meetings:

Potential Engagement Location Anticipated Number of Annual Occurrences

Meeting at the National Association of Broadcasters (NAB) Headquarters

Washington D.C. 12

Presentations to DSO Staff regarding technical and programmatic topics

Joint Spectrum Center, Annapolis

Stakeholder Meetings DISA Headquarters, Ft. Meade MD 6

Participation in Technical discussions and/or process definition Table-Tops

McLean, VA 6

NAB Conference Las Vegas, NV 1

Periodic status meetings Joint Spectrum Center, Annapolis

Technical and programmatic discussions with the office of the DoD Chief Information Officer

Crystal City, VA 2

Site visit for information gathering, training, or other purposes

TBD 3

Other technical and/or user group meeting As defined by PWS 33

Technical meetings will include problem-solving discussions, where the contractor’s SMCS and process experts will provide perspectives, elicit requirements and/or help stakeholders resolve issues. Programmatic review meetings will include informing external stakeholders and senior leaders of SMCS capabilities and status. During any technical support engagement, the contractor shall provide SMCS perspectives, deliver update information, and lead problem solving discussions. Support shall include the following types of engagement, at a minimum:

Integration, process, and technical discussions with ENG community representatives Verbal and written updates to DoD Chief Information Officer (CIO), DISA, and other senior leader representatives Integration and requirements planning with user groups Planning, Integration and technical problem resolution with SARDP representatives (leading to future capability integrations in SMCS) Updates, process, and technical discussions with the military services.

Meetings shall include technical exchanges with stakeholder user groups to evolve the SMCS business process, evolve the SMCS software requirements, and describe planned functionality for current and future SMCS releases.

Engagements with external stakeholders (to include user groups) shall be coordinated with and approved by the COR, to include all materials presented to external stakeholders prior to presentation. For each meeting, the contractor shall prepare and deliver Stakeholder Meeting Materials and Stakeholder Meeting Minutes.

6.1.3 Subtask 1.3: Project Data and Information: The contractor shall manage and retain a repository of all Project Data and Information. The contractor shall provide, as requested by the COR, relevant working Project Data and Information products created in the process of performing work during the period-of-performance. Such artifacts include at a minimum: documents, briefings communications, software scripts, software components, and software development artifacts that are produced in association with this effort. These artifacts are considered key for historical purposes, knowledge management, collaboration, and information sharing. Deliverables shall be provided in their native formats using a delivery mechanism agreed to by the COR.

6.1.4: Equipment Management: The contractor shall maintain a GFI/GFE/GFX/GFx List and deliver it on a monthly basis. The GFI/GFE/GFS/GFx List shall document any equipment, information, or item that the Government provides to successfully execute the requirements of this effort. Each GFI/GFE/GFS/GFx request shall be coordinated with the COR.

CDRL

PWS

Task

Deliverable Title Format Due Date Distribution/

Copies Frequency and Remarks

A001 6.1.1 Program Management Plan

DI-MGMT-80347,

including additional content required by

PWS 6.1.1

MS-Word and/or Adobe PDF

Draft due five (5) days prior to Kickoff.

Final due five (5) business days after receipt of DSO comments

Standard Distribution*

One (1) Time

A002 6.1.1 Monthly Activity and Status Report

Government-provided format.

MS-Word and/or Adobe PDF, MS- Excel, MS-Project

NLT 15th calendar day of each month

Standard Distribution*

Monthly

A003 6.1.1 Monthly Invoices

Contractor proposed, and COR approved format (PDF or MS- Word) and in WAWF

NLT 15th calendar day of each month

Standard Distribution*

Monthly

A004 6.1.1 Monthly Financial Tracking Summary

Government-provided format

NLT 15th calendar day of each month

Standard Distribution*

Monthly

A005 6.1.1 6.1.2 6.2.2

Meeting Minutes

Contractor proposed, and COR approved format

Kickoff Meeting: Kickoff meeting must be held within thirty (30) days of PoP start. Minutes due two (2) business days following meeting.

Status Meetings: Due two (2) business days following meeting Stakeholder Meetings:

Due two (2) business days following meeting

Standard Distribution*

Kickoff Meeting:

Once Status Meetings:

Once in every two-week period throughout the contract PoP Stakeholder Meetings: As requested by the

COR

ORR: For each release

A006 6.1.1 6.1.2 6.2.2

Meeting Materials

Contractor proposed, and COR approved format in accordance with requirements in the PWS

Kickoff Meeting: Kickoff meeting must be held within 30 days of PoP start; materials due two business days prior to meeting.

Status Meetings, Stakeholder Meetings, and ORRs: Agenda and materials due two business days prior to meeting

Standard Distribution*

Kickoff Meeting:

Once Status Meetings:

One time in every two-week period throughout the contract period of performance Stakeholder Meetings: As requested by the

COR

ORR: For each release

A007 6.1.3 Project Data and Information

Contractor proposed, and COR approved format

Coordinated between COR and contractor at time of requirement

Standard Distribution*

As required by the

COR

CDRL

PWS

Task

Deliverable Title Format Due Date Distribution/

Copies Frequency and Remarks

A008 6.1.4 GFI/GFE/GF

S/GFx List

Contractor proposed, and COR approved format

NLT 15th calendar day of each month

Standard Distribution*

Monthly

* Standard Distribution: One (1) copy of the transmittal letter without the deliverable to the Contracting Officer (KO); One (1) copy of the transmittal letter with the deliverable to the Primary COR; One (1) copy of the deliverable to the Alternate COR; and One (1) copy posted to a site designated by the Government. The copy of the deliverable sent to the Primary and Alternate COR may be in electronic format if requested by the Government.

6.2 Task 2 – SMCS Development (CPFF) (RDT&E): The contractor shall develop, deploy, and continually enhance SMCS using industry standard agile development methodologies to:

Develop and deploy an initial operational release of SMCS that meets the specified requirements Provide a construct for Government prioritization of continual SMCS enhancement Capture user-generated requirements for continual SMCS enhancement Maintain a web-based SMCS system environment Continually deploy enhanced SMCS capabilities to meet evolving requirements Rapidly fix any bugs and rapidly deploy any requisite emergency releases Provide the appropriate level of information assurance and security, based on role-based access controls.

INTEGRATE CONTINUOUS SECURITY PRACTICES, INCLUDING INTEGRATING

VULNERABILITY ANALYSIS

The contractor shall use open interface standards and apply modular, open systems architecture principles to SMCS development:

The contractor shall employ modular designs that are cohesive, encapsulated, self-contained, and highly binned. The contractor shall use broad modular definitions to enable commonality and reuse, and each module shall not constrain other modules.

The contractor shall develop and maintain an architecture that incorporates reconfigurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradability, and long-term supportability.

The architecture shall be layered, modular, and shall maximize the use of standards-based commercial off-the-shelf (COTS) components that all utilize either non-proprietary or non-vendor-unique interfaces, to include non-proprietary data formats.

The design approach shall result in a layered system design, maximizing software independence from any hardware.

The architectural approach shall ensure the rapid and affordable insertion and refreshment of technology through modular design, the use of open standards and open interfaces.

The contractor shall implement and report on interface metrics, in an Interface Metrics Report to include at a minimum:

a. Number of interfaces between major modules

b. Number of message types per interface

c. Message sizes on each interface

d. Number of message interchanges for use cases

SMCS shall be compliant with the Government’s SMCS Reference Architecture. The contractor shall use this GFI to guide the development of the initial operational release of SMCS. The initial operational release must support the operational construct defined by the SMCS Operational Requirements Document (ORD), and meet the software requirements of the SMCS Initial Software Requirements Specification (SRS). The SMCS Reference Architecture, ORD, and Initial SRS will be provided to the contractor as GFI. The initial SMCS operational release shall enable effective coordination between stakeholders and utilize a commercial web services framework.

Future operational releases of SMCS shall contain User-Based Coordination, Coexistence Analysis, and Database functionality. The contractor shall use the SMCS Future Objectives List (provided as GFI) to help form candidate requirements in future SMCS releases, and develop an SMCS development roadmap. Due to the transition timeline of systems entering the target band, the Government anticipates demand for SMCS development to decrease over the life of the SMCS effort. At a minimum, the contractor shall deliver operational releases, in accordance with the table below; however, the contractor is encouraged to deliver operational capability as frequently as possible in accordance with the proposed agile development methodology.

Base Year Option Year 1 Option Year 2 Option Year 3 Option Year 4 The contractor shall deliver at least two

(2) operational releases, including the initial operational capability

The contractor shall deliver at least three

(3) operational releases

The contractor shall deliver at least two

(2) operational releases

The contractor shall deliver at least two

(2) operational releases

The contractor shall deliver at least one

(1) operational release

The contractor shall provide a Software Development Plan (SDP) that documents the comprehensive agile software development process, to include requirements analysis, coding, testing, deployment, documentation, problem analysis, and problem resolution. Additionally, the SDP shall address the software architecture, the requirements traceability processes, the process for managing and delivering emergency bug fixes (to include testing, validation, and deployment), the incorporation of agile methodologies, the maintenance of the Product Backlog (PB), and the defect identification and resolution processes.

The contractor shall provide a Configuration Management Plan (CMP).

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Dec 28, 2023.