QA for RFI__.pdf

Item VENDOR QUESTION GOVERNMENT RESPONSE 1 Is this RFI intended to inform a successor or follow-on for any capabilities currently performed under the

Technology Applications Development and Sustainment (TADS) contract, FA4600-20-D-0002, or should industry view this as a separate AFLCMC-led requirement?

This is a separate effort.

2 The RFI describes the current AFW environment as AWS-based. For purposes of this market research, should industry treat the existing cloud architecture as the future-state baseline, or is the Government interested in alternative cloud, hybrid, on-premises, and consumption-based approaches where they may improve mission performance, resiliency, or cost?

The Government will consider any and all options for Cloud provider.

3 Is the intent of Section 3.2, Everything as a Service (XaaS), to gather industry feedback on alternative consumption and service-delivery models, or primarily to identify additional XaaS capabilities that could operate within the current environment?

The Government will consider any and all suggestions and recommendations for XaaS capabilities.

4 Would the Government consider comparable DoD or Federal experience with enterprise IaaS/XaaS, HPC, multi-enclave operations, cross-domain data, and mission-critical IT relevant even when that experience was performed outside the Air Force Weather enterprise?

Yes

5 Would the Government welcome industry recommendations that reduce dependency on any single cloud service provider, OEM, software provider, or integrator while preserving Government control of data, interfaces, cybersecurity, and mission outcomes?

Yes

6 The RFI discusses the Government retaining the Lead System Integrator role while leaving flexibility in that approach. Is the Government seeking industry feedback through this RFI on the most effective allocation of integration responsibilities between the Government and industry?

Yes

7 Has the Government made any preliminary determination regarding whether the six task sections are best performed as an integrated effort, individually, or in some combination, or is industry feedback intended to help inform that decision?

The Government seeks recommendations.

8 Section C.5 requests proposed RTS standards and uptime criteria for a “PaaS environment,” although Section C addresses SaaS, DevSecOps, and other software. Can the Government confirm whether C.5 is intended to reference the Section C SaaS/software environment?

C.5 is intended to reference SaaS environments.

9 Regarding the XaaS framework described in Section 3.2...Does the Government anticipate onboarding specialized commercial weather or environmental analytics SaaS capabilities into the AFW Enterprise through the XaaS framework described in Section 3.2?

The Government will consider any and all suggestions and recommendations for XaaS capabilities.

10 If so, does the Government anticipate that the Government or an enterprise integrator would manage the RMF/ATO onboarding process for those commercial offerings at the applicable Impact Level?

The Government will consider any and all suggestions and recommendations for XaaS capabilities. These processes could be handled in either way.

11 Will the Government provide the current and target technical stack (including commercial SaaS tools), along with relevant scale metrics such as number of users, ticket volumes, and system throughput, within the bidders’ library to ensure offerors can accurately evaluate technical complexity and propose appropriately tailored solutions?

Intent is to post available documents as part of Bidder's Library

12 For Section F: Digital Materiel Management / Digital Engineering, will the Government provide a detailed list of key tasks—consistent with the level of specificity provided for previous sections within the RFI scope—to ensure offerors can fully align technical, management, and delivery approaches with the Government’s expectations?

Intent is to post appropriate requirements and objectives as part of future postings.

Section d3.0 notes the Government expects to hold the Lead System Integrator role and that interested parties may respond to individual sections or combinations. If a solicitation results, does the Government anticipate awarding the six task sections (and the Section 3.2 XaaS scope) as separate awards or task orders under the Government's integration, or as a single consolidated award? How does the Government intend to manage configuration and interface control between multiple section performers?

Exact acquisition strategy is in development. The Government is considering multiple options and will factor in current and future RFI as well as future USG- Industry discussions.

Section C emphasizes integrating and managing third-party SaaS solutions for weather and meteorological cloud operations, and question C.2 addresses integrating commercial SaaS products into government systems. Where a commercially operated weather intelligence SaaS already delivers a required capability (e.g., decision-quality forecast products, impact-based alerting, API delivery), is the Government's intent to consume that capability as a service under the Section 3.2 model rather than develop or sustain a government-unique equivalent?

In general, the acquisition preference is to purchase commercial rather than government-unique equivalents, but each situation must be considered carefully on its own.

Sections A.1, E.3, and F.2 address multi-enclave data flow and cross-domain solutions. Given the ongoing consolidation of on-premises infrastructure supporting the weather enterprise, does the Government intend the future contract to provide enterprise cross-domain transport as part of the scope, and are cloud-native, already-accredited CDS services operating within existing Department of the Air Force cloud environments (e.g., DAF CloudWorks) considered in scope for the Section 3.2 service catalog?

Enterprise cross-domain transport is a key component of the AFW Enterprise.

Specific solutions will be evaluated in the future.

16 Section 3.2 names Security as a Service among the intended consumption-based offerings, and Section D requires managing RMF through ATO and Continuous ATO. Will the Government consider commercially provided, already-accredited DevSecOps and authorization-inheritance platforms (SecaaS) as a means of satisfying Section D functions and the Section 3.2 requirement to shepherd third-party XaaS offerings through RMF, including for Secret and TS/SCI enclaves?

The Government will consider any and all options for platforms and methods to meet cybersecurity requirements.

For the Section 3.2 consumption-based model, does the Government anticipate the resulting vehicle will support subscription and consumption-based pricing structures for SaaS and Data-Analytics-as-a-Service offerings (with FinOps-style cost transparency), rather than solely labor-hour or completion-form CLINs? Exact acquisition strategy is in development.

18 Question F.1 references commercial cloud environments including AWS and Azure. Is the Government open to a multi-cloud, CSP-agnostic architecture under the MOSA approach in Section E, including use of Department of the Air Force enterprise cloud environments where services are already accredited, or is continuity on the current cloud service provider a constraint for the future contract? The Government will consider any and all options for Cloud provider.

In responding to Sections 1 and 2, should respondents identify capabilities already authorized and operating in DoD cloud environments at specific impact levels (e.g., IL5/IL6), and will demonstrated authorization status inform the Government's market research conclusions and acquisition strategy? The Government will consider any and all optionsduring market research.

REQUEST FOR INFORMATION - Q&A

Sheet1