S1814___Data_Call_001_-_NB_SATCOM,_REV2,_26SEP18.pdf
PDF 236 KB Posted
- Attached to
- C5ISR 2018 BAA (Formerly S&TCD) Rev 16
- Solicitation number
- BAA-18-R-STCD
About this file
The purpose of this amendment is to revise the data call 001 and update the BAA. 1. Data call 001 revised in response to questions received.
View the file
Other files
Show 40 more
50 files listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
REQUEST FOR INFORMATION (RFI) / DATA CALL
Broad Area Announcement (BAA)
Solicitation: BAA-18-R-STCD, Topic #: S1814
Narrowband SATCOM Transport Controller Research
DATA CALL 001
REV2, 26SEP18
1.0 INTRODUCTION
This call for White Papers (WP) is being issued under Broad Agency Announcement (BAA) BAA- 18-R-STCD, which was published on FedBizOpps.gov on 20 June 2018, and last updated on 3 July 2018. Offerors must refer to the solicitation document entitled “STCD_BAA 20180627 Final Ver1 Additional Topic,” which incorporates Amendment 1, and it must be read in conjunction with this call for WP’s. All instructions set forth in the BAA-18-R-STCD solicitation document apply to this call.
The Space and Terrestrial Communications Directorate (S&TCD) is soliciting this call for WP’s, in accordance with (IAW) Topic # S1814. To be eligible for consideration and possible contract award, the technology or methodology shall be in the nature of either basic research, applied research, or advanced technology development, not for a specific system/hardware, or demonstration and validation.
1.1 DATA CALL INFORMATION
S&TCD provides Science and Technology (S&T) solutions to the Department of Defense (DoD), U.S. Army Joint Programs of Record (PoR), and the Warfighter. S&TCD performs research, development, and engineering functions in all aspects of terrestrial, avionics, and space-dependent communications technology to include adaptive, reliable seamless battlefield communications with full electronic counter-countermeasures capability and cybersecurity/Information Assurance
(IA).
S&TCD is interested in developing an Open Standard Architecture (OSA) compliant Gateway Transport Management System (GTMS), for the Satellite Communications (SATCOM) Divisions networks, that is capable of leveraging machine learning technologies. S&TCD is interested in the SATCOM GTMS solutions, and commercially available technical concepts and ideas for inclusion into future system designs. The development of the GTMS will directly support the U.S.
Solicitation: BAA-18-R-STCD Data Call 001, Rev2 Topic #: S1814
Army’s modernization priorities for network transport performance and technology integration, as identified herein.
1.1.1 BACKGROUND
In Fiscal Year (FY) 2018 (FY18), the Communications Electronics Research, Development, and Engineering Command (CERDEC) initiated a multi-year formal Research and Development (R&D) program to commence in FY19. This multi-year R&D program shall provide the development of the GTMS, and Automated Network Management Systems (ANCS), to supporting future Mission Command (MC) SATCOM networks, providing real-time physical through network layer sensing capabilities, and enabling transport services orchestration.
1.1.2 KEY CAPABILITIES
The key capabilities in which an Offeror should focus for the development of a product and/or solution for BAA Topic S1814, for S&TCD, SATCOM Division include:
Monitors Global Narrowband SATCOM Transports based on OSA standards.
Provides Smart Routing Based on Transport Health and User Demands
Improves Network Connectivity with Transport Management utilizing Applied Machine
Learning
Waveforms Performance Optimization
Over The Air Waveform Provisioning and Key Management
Minimize Network Admissions and Load Balancing
Provides transport network resiliency to tactical users These capabilities where derived from the Army’s modernization priorities with focus on enhance Network, Command
Control and communication (C3I) supporting key capabilities; Long Range Precision Fires, Next Generation Combat Vehicles, Future Vertical Lift, Air and Missile Defense and
Solider Lethality.
Program is a multiyear research and development effort developing enhanced transport management systems that enables cross-hub command and control operations.
1.1.3 NARROWBAND SATCOM PROBLEM STATEMENT/OVERVIEW
The current SATCOM transport architecture consists of one controller for every transport;
however, the current capabilities do not allow for one (1) controller to manage multiple transports, and is not scalable or flexible in the event of transport link degradation, as a result of a congested or contested environment The intended objective for Narrowband SATCOM is to develop a single gateway transport controller that can interact with and has ability to manage simultaneously multiple Satellite transports.
Figure 1: Narrowband SATCOM Operation View
2.0 AWARD INFORMATION
2.1 ANTICIPATED AWARD DATE: MAY 2019 (FY19, QUARTER (Q) 3 (Q3))
2.2 FUNDING AND PERIOD OF PERFORMANCE
Under this call, the United States Government (USG) intends to award up to two (2) contracts with an approximate Period of Performance (PoP) of fifty-four (54) months, with anticipated funding of approximately $13.5M, per awarded contract.
NOTE: The total PoP for this call is not to exceed (NTE) FY23, Q4; and, may be delineated in the following Phases (PH) (periods and/or Option Years (OY)):
Base Period (PH I): twelve (12) months;
OY1 (PH II): NTE twelve (12) months;
OY2 (PH III): NTE twelve (12) months;
OY3 (PH IV): NTE eighteen (18) months;
NOTE: This funding profile is an estimate only, and is not a contractual obligation for funding.
All funding is subject to change due to USG discretion and availability. Potential Offerors should be aware that due to unanticipated budget fluctuations, funding, in any or all areas, may change with little or no notice. Awards under this call are expected to range from $13.5 M to $27M;
however, USG reserves the right to award smaller or larger contracts, or assistance instruments.
USG reserves the right to select all, part, or none of the WP’s received, subject to the availability of funds.
2.3 BAA TYPE
This call for WP’s will be governed by the “two-step” process described in the General Information section of BAA-18-R-STCD. Offerors that submit a proposal without first submitting a WP may not be eligible for award.
2.4 SUBMISSION INSTRUCTIONS
All submissions shall be IAW the instructions provided within the baseline BAA-18-R-STCD, via Section III, for instructions on WP preparation, submission, and evaluation.
2.4.1 TECHNICAL APPROACH
Interested parties are requested to respond to this call for WP’s by submitting a Technical Approach describing their technical capabilities, concepts, ideas, and, relevant experience in developing similar components.
All responses shall provide sound reasoning and a description of component level functionality to support the proposed component and/or architecture. This information will be shared with DoD personnel, and DoD SETA Contractors involved in WP evaluations and review only.
Interested parties providing proposed components or technologies shall also provide thorough technical content explaining the operation, and performance of the component or technology. This portion of the response can be marked with proprietary markings.
2.5 QUESTIONS DUE DATE AND TIME
Technical questions shall be submitted No Later Than (NLT) 3:00 PM EST, 25 SEPTEMBER 2018, via email to the Technical Point of Contact (TPOC), with a carbon copy (CC) to the Contracting Officer (KO), Contract Specialist (KS), and Acquisition Management Team (AMT) Mailbox, as listed below.
USG will publish questions and answers received by industry to FBO, via a revision to this Data Call, per ADDENDUM 001, Technical Questions and Clarifications, herein.
2.6 WHITE PAPER DUE DATE AND TIME
All WP’s shall be submitted NLT 3:00 PM EST, 18 OCTOBER 2018, via email to the TPOC, with a carbon copy (CC) to the KO, KS, and AMT Mailbox, as listed below.
AMT Mailbox: usarmy.apg.rdecom-cerdec.mbx.stcd-amt@mail.mil KO, Brian Holman: brian.j.holman2.civ@mail.mil KS, Andrew Pilone: andrew.m.pilone.civ@mail.mil TPOC, Rahul Pandya: rahul.p.pandya.civ@mail.mil Alternate TPOC, Peter Bach: peter.a.bach4.civ@mail.mil
If the submission will be classified, Offerors should contact the TPOC and KO for instruction on how to submit the WP via appropriate methods/channels. The KO shall be informed, in writing, that a classified WP has been submitted, referencing the submissions title and to whom it was submitted.
Contractual questions may be directed to the KO and/or KS at any time.
ADDENDUM 001
TECHNICAL QUESTIONS AND CLARIFICATIONS
26 September 2018
Q-1: As far as military SATCOM is concerned, is the focus on next-generation NB-
SATCOM (MUOS)?
If so, does S&TCD expect the Waveform Optimizer to be limited to WCDMA or should it also optimize legacy waveforms or other waveforms considered for NB- SATCOM (e.g., OFDM)?
Are there any specific radios or other waveforms that are in scope?
USG RE: By definition MILSATCOM now (DoDI 8420.01) refers to any DoD owned or leased capability. If the DoD is paying for it, it falls under the umbrella term “MILSATCOM”.
As for Military SATCOM, NB-SATCOM is looking at supporting "low data rate traffic" over one or more transports available in a region, today and into the future.
Considerations include, but are not limited to: MUOS, (W)CDMA, 5G, OFDM, Iridium.
Specific Radios have not been defined yet and waveform implementations are dependent on the region and RF environments.
Q-2: The RFI lists seven key capabilities in Section 1.1.2. Is S&TCD interested only in solutions that address all the capabilities or also in the ones that offer a partial concept (e.g., a Smart Routing solution or a waveform optimization approach or a combination of the two)?
USG RE: S&TCD is interested in solutions that can address the key capabilities listed.
Q-3: Are software-based solutions acceptable or does S&TCD also want performers to provide/build transport controller hardware (e.g., modem to each waveform type)?
USG RE: Software solution is preferred, that is modular in design to accept API's or interfaces to physical modems that provide SATCOM IF modulated waveforms. The solution should be scalable to accept multi-vendor modems for Provisioning, configurations and management of remote devices.
NOTE: API requirements would need to be developed in support of this effort.
Q-4: In the instructions to the BAA-18-R-STCD, it references in White Paper Preparation, Submission, and Evaluation paragraph 1.c.v. that technology can be matured sufficiently to meet a TRL of 5 after 12 months of effort; but, in the Data Call, it references an approximate PoP of 54 months – does the TRL 5 in 12 months still apply?
USG RE: OY periods are available to extend the time needed to mature capabilities to a TRL 5, if required. USG prefers the vendor provides a TRL 5 capabilities with minimal OY periods.
Q-5: The request for a ROM – is that for 12 months (~ $3M) or 54 months (~ $13.5M)? 3
USG RE: IAW Section 2.2, Funding and Period of Performance, USG intends to award up to two
(2) contracts with an approximate PoP of fifty-four (54) months, consisting of one (1) twelve (12) month Base/ Phase I period, two (12) twelve (12) month OY (OY1/Phase II, and OY2/Phase III) periods, and one (1) eighteen (18) month OY4/Phase IV period;
with anticipated funding of approximately $13.5M, per awarded contract.
Q-6: The request for a ROM— is a bottom line number with a clarification that the ROM does/does not include fee acceptable?
USG RE: IAW Section 2.2, Funding and Period of Performance, the ROM is NTE the aforementioned funding of $13.5M, per contract award.
Q-7: Can the government please clarify is a Rough Order of Magnitude (ROM) is required for the S1814 Data Call? The instructions in the separate announcement do not request it, but BAA‐18‐R‐STCD mentions including a ROM as part of the submittal.
Is a White Paper incomplete without a ROM?
USG RE: All Data Calls/Calls for WP’s are in conjunction with the BAA-18-R-STCD, and, are used to provide granularity/requirement specifications for a specific topic; therefore, yes, a ROM is required for each WP submission, and, would be considered incomplete if the WP submission did not include a ROM.
File details come from the government source that posted it.