Notice ID: bf8d7bbc6dcd391c87ba7b440b0dcadeAward NoticeAwarded
NASA Goddard Information Technology Integration and Support Services (GITISS)
Awarded on September 29, 2016. Full description on SAM.gov.
Awarded tounder NNG16Vu01C (source: SAM.gov award notice)• $206
Overview
- Posted
- January 23, 2017
- Notice type
- Award Notice
- NAICS
- 541513: Computer Facilities Management Services
Notice details
- PSC
- D: IT AND TELECOM - INFORMATION TECHNOLOGY AND TELECOMMUNICATIONS
- Last updated
- Dec 3, 2025
- Award date
- Sep 29, 2016
- Award amount (SAM.gov award notice)
- $206
Identifiers
- Solicitation number
- NNG14475415R
- Notice ID
- bf8d7bbc6dcd391c87ba7b440b0dcade
- Award number (PIID)
- NNG16Vu01C
Description
The Government now anticipates an announcement in early Fall (September/October).
Award Overview
Award Number
NNG16Vu01C
Award Amount (SAM.gov award notice)
$206
Award Date
Sep 29, 2016
Awardee
Awardee UEI
NBELUNT3NMG3
Original Solicitation
Notice ID: bf8d7bbc6dcd391c87ba7b440b0dcade
Posted Date: Jan 23, 2017
Original Response Deadline: Not specified
Contract Details
Contract data not yet available
Contract details typically appear within 2-4 weeks after award; DoD awards are published about 90 days after signature.
Contacts
Contracting Officer
Primary Contact
Documents
No documents available.
Lifecycle
Solicitation:
NNG14475415R- Pre-Solicitation
- Solicitation
- Combined Synopsis
- Awarded
This opportunity has been awarded.
- 25×Pre-SolicitationApr 23, 2014
D--GODDARD INFORMATION TECHNOLOGY INTEGRATION AND SUPPORT SERVICES
- SolicitationMar 4, 2015
D--GODDARD INFORMATION TECHNOLOGY INTEGRATION AND SUPPORT SERVICES
- 2×Combined SynopsisFeb 18, 2016
NASA Goddard Information Technology Integration and Support Services (GITISS)
- AwardedCurrentJan 23, 2017
NASA Goddard Information Technology Integration and Support Services (GITISS)
Similar Opportunities
Title | Match | Phase | Deadline |
|---|---|---|---|
See attached RFI and draft Performance Work Statement (PWS) attached. The U.S. Department of State, Bureau of Global Acquisitions, is conducting market research to determine whether qualified firms, particularly small businesses, are available and able to meet the requirements described in this notice and the attached draft Performance Work Statement (PWS). Interested sources should demonstrate proven experience successfully performing work similar in scope and scale to the work described in the draft PWS. The Department also invites industry comments on the draft PWS. The Government is issuing this RFI to conduct market research under Federal Acquisition Regulation (FAR) Part 10 and FAR 15.201(c)(7), and to identify vendors capable of performing the work described in this notice. This RFI is for information and planning purposes only. It is not a Request for Proposals (RFP), and it is not a promise to issue an RFP in the future. This RFI does not commit the Government to award a contract for any supply or service. The Government is not seeking proposals at this time and will not accept unsolicited proposals. The Government will not accept telephone calls or answer questions about this RFI. The Government will not pay for any information provided or for any costs incurred in responding to this RFI. Respondents bear all costs of responding. Firms that do not respond to this RFI may still take part in any future solicitation. If the Government issues a solicitation, it may post the notice on SAM.gov. Potential offerors are responsible for monitoring SAM.gov for more information about this requirement. The Bureau of Diplomatic Security, Office of Security Technology (DS/C/ST), requires a contractor to operate, maintain, and enhance the Department's Physical Security Information Management (PSIM) system and High-Definition Security Video System (HDSVS) enterprise. The requirement also includes 24/7/365 operations center support, global security network operations, video analytics, 3-D facility modeling, IBM Maximo asset management support, SharePoint application development, domestic alarm network administration, cybersecurity risk mitigation engineering, and training. A Top Secret facility clearance is required. See the attached draft PWS for details. | 87% | Market Research | 11/12/2026 |
United States Census Bureau (USCB) Enterprise RFID Technology, Installation, and Azure WIMS Integration REQUEST FOR INFORMATION (RFI) This RFI is solely for information and planning purposes – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. Further, the USCB is at the early stages of market research and is not, at this time, seeking proposals and will not accept unsolicited proposals. Interested parties are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. 1.0 Purpose The U.S. Census Bureau (USCB) issues this Request for Information (RFI) for market research under Federal Acquisition Regulation (FAR) Part 10 to understand current business practices and identify industry capabilities for furnishing, installing, configuring, testing, and integrating radio frequency identification (RFID) technology with the USCB’s existing Warehouse Inventory Management System (WIMS). The USCB seeks industry input on these types of services and expertise in achieving the desired objectives in accordance with federal requirements. To date, the USCB has already developed a scalable WIMS platform using Microsoft technologies in its Microsoft Azure environment. This RFI does not seek a replacement warehouse management platform. The USCB’s primary interest is to acquire industry recommendations on RFID equipment and supporting software, facility deployment and integration services, and secure delivery of RFID event data into the existing WIMS environment. The USCB believes industry has the best knowledge of current offerings and how to plan for, acquire, and integrate evolving technology trends. Vendors are encouraged to provide recommendations and describe innovative, commercially available, and proven approaches that address the objectives detailed within this RFI without being constrained by a prescriptive equipment design or configuration. 2.0 Background and Operational Environment The USCB manages survey forms, printing and mailing materials, shipping supplies, and other inventory supporting demographic, economic, and decennial programs, including preparations for 2030 Census tests. Inventory is received, stored, moved, issued, transferred, and shipped through multiple facilities. Automated identification and transaction capture can reduce manual inventory handling and improve the accuracy and timeliness of enterprise inventory records. Potential locations include National Processing Center operations in Charlestown, Indiana; Census Bureau Headquarters in Suitland, Maryland; a warehouse in Franconia, Virginia; Regional Offices; and other Government-designated facilities. Actual locations, installation scope, sequencing, and site access would be determined by the Government. These locations may have different layouts, physical security restrictions, network conditions, and operating requirements. 3.0 Objectives and Mission-Critical Capability Areas The USCB intends to leverage industry knowledge, feedback, recommendations, and expertise on proven approaches and best practices that achieve the objectives listed below. 3.1 RFID identification and multi-level tracking The USCB is interested in tracking at the item or box, pallet, and rack or storage-location levels. Industry recommendations may include passive or active RFID, hybrid approaches, or complementary identification methods where appropriate. Recommended solutions should support reliable identification and location/movement events during receiving, putaway, internal transfers, picking, shipping, cycle counting, and reconciliation. Input is requested to address read accuracy, interference, duplicate or missed events, and the practical limits of location precision. 3.2 Equipment provision, site assessment, and installation The contemplated effort includes facility assessments; design and equipment selection; provision of tags, readers, antennas, handheld or mobile equipment, portals, and supporting components as appropriate; physical installation and configuration; and operational testing. Respondents shall provide input into the considerations made in regards to site dependencies, secured-space work practices, commissioning, warranties, support, and expansion to additional facilities, as directed. 3.3 Secure integration with existing Microsoft Azure WIMS The RFID solution must exchange usable, timely data with the existing Government WIMS rather than create a competing inventory system of record. Respondents are requested to recommend integration of reader and edge-device feeds with Azure-hosted WIMS through appropriate secure interfaces, APIs, messaging, middleware, or other standards-based methods. Anticipated work may include event filtering, data mapping to Government inventory identifiers and locations, interface development, custom fields or components as needed, error handling, testing, documentation, and knowledge transfer. Specific Azure services and interface specifications will be coordinated with the Government during subsequent planning. 3.4 Security, reliability, and sustainment The USCB seeks recommended approaches and solutions suitable for controlled federal facilities and integration with its existing authorized cloud boundary, subject to applicable security review and approval. Respondents are requested to provide information which describes secure communications, device administration, access control, logging, resilience during network interruptions, patching, lifecycle support, and long-term costs. The USCB seeks recommended approaches which permit Government operation and sustainment without unnecessary vendor lock-in. 4.0 Industry Response and Feedback Questions A. RFID technology and operational performance 1. Describe your recommended technology and architecture for identifying and tracking individual items or boxes, pallets, and racks or storage locations in multiple warehouse facilities. Explain any recommended RFID or hybrid approaches. 2. Identify the major hardware and software components your recommended approach would provide, including tags, fixed or mobile readers, antennas, portals, edge components, and management tools. Distinguish commercial products from custom components. 3. How would your solution capture receiving, putaway, internal movement, picking, shipping, transfers, and cycle-count events, and associate them with the correct inventory identifiers and locations? 4. What read accuracy and location precision can realistically be achieved, and how do you address dense racks, metal, packaging, interference, missed reads, and duplicate events? 5. What mobile, handheld, exception-resolution, and offline or intermittent-connectivity capabilities are available for warehouse operators? B. Facility assessment, installation, and rollout 6. Describe your approach to surveying facilities, developing a site-specific equipment design, and determining reader, antenna, portal, and network placement. 7. Describe your ability to furnish, install, configure, and commission equipment in secured Government spaces at Charlestown, IN; Suitland, MD; Franconia, VA; Regional Offices; and other locations as directed. Identify subcontractor dependencies. 8. What facility, electrical, networking, physical security, access, and Government-furnished resources would typically be needed for installation and operation? 9. Identify a phased pilot-to-enterprise deployment approach, including indicative schedule, testing and acceptance criteria, and the approach for minimizing disruption to ongoing warehouse operations. C. Existing WIMS and Azure integration 10. Describe how RFID data would be securely transmitted, processed, and integrated into an existing Microsoft Azure-hosted WIMS, without replacing the Government’s inventory platform. 11. What integration interfaces and patterns are available (such as APIs, webhooks, message queues, middleware, or edge processing), and how would your recommended approach accommodate Government-defined data schemas and custom fields? 12. How would your recommended solution convert raw RFID reads into reliable inventory events, manage duplicates and errors, reconcile exceptions, and preserve traceability and audit records? 13. What, if any, technical personnel or services would be recommended for Azure connectivity, interface development, configuration, end-to-end testing, documentation, and transfer of knowledge to Government IT staff? D. Security, sustainment, and market considerations 14. Identify cybersecurity and device-management controls, including encryption, authentication, access management, logging, patching, and operation within an existing federal cloud authorization boundary. Identify any external cloud services or data flows. 15. How would your recommended solution handle network outages, delayed data delivery, hardware failures, recovery, and scaling across additional facilities? 16. Describe ongoing support, maintenance, warranties, equipment replacement, licensing, proprietary dependencies, and the ability for Government personnel to sustain and expand upon the recommended solution. 17. Provide your relevant experience with multi-site RFID installations and integrations with existing enterprise or Azure-hosted systems, including lessons learned and measurable results where available. 18. Provide rough-order-of-magnitude cost drivers or illustrative cost ranges, separated where possible into equipment/tags, site installation, integration and engineering, licensing, training, and recurring sustainment. Identify assumptions and cost-saving alternatives. D. Company Overview and Capabilities 19. Provide a Company Overview and Capabilities to include: Business name, company website, and headquarters address. Name of company representative and their business title. Unique Entity ID number. Socio-economic status, business size, and size standard/applicable. Certified North American Industry Classification System (NAICS) codes for required services stated in objectives. Contract vehicles that would be available to the Government for the procurement of the requirements, to include General Service Administration, NASA Solution for Enterprise-Wide Procurement, Federal Supply Schedules, or any other Government Agency contract vehicle. Brief description of your company’s relevant core corporate capabilities and demonstrated prior relevant experience. 6.0 RESPONSES Interested parties are requested to respond to this RFI. Responses shall be in Microsoft Word or Office compatible format using a 12-point font. Responses are due no later than Wednesday, November 4, 2026 at 12:00 noon EST. Responses shall be limited to 14 pages. The email subject line should be: “(Insert Company Name), RFI Response: RFID Integration”. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. RFI responses shall be sent, via email, to: Pamela Miller, Contract Specialist Pamela.A.Miller@census.gov Kristina Hartman, Contracting Officer Kristina.D.Hartman@census.gov | 80% | Market Research | 11/04/2026 |
Information Technology Purchase for Portsmouth Paducah Project Office -Keyboard Video Mouse (KVM) Switches | 78% | Awarded | Open |
This CSO is for AMC/A6 Information Technology Needs hosted by the 763rd Enterprise Sourcing Squadron for Air Force Operations A6. Individual Area's of Interest (AOIs) issued against the CSO will be posted under this notice. 03/19/2026: FA4452-26-S-C001 AOI (1) - AMC/A6 Information Technology Needs Commercial Solutions Opening (CSO) - Amendment 01 All details regarding submission and evaluation factors are provided in any posted Areas of Interest (AOIs) This CSO Solicitation is a competitive solicitation that is open until 26 February 2031. Submissions will only be accepted following specific AOI submission due dates and times. The Government reserves the right to extend this CSO beyond the closed date by amendment if the authority is extended. *White Paper due date for the Base IT Modernization AOI is extended to 12 May 2026. | 65% | Combined Synopsis | 02/26/2031 |
Request for Information Multi-X Security (MXS) Platform Operations and Maintenance 15 October 2026 1.0 Description The Air Force Life Cycle Management Center, in support of the Advanced Technology Branch (AFLCMC/HNJT), is seeking information from interested companies with the capability to provide Operations and Maintenance, and continuous modernization of the Multi-X Security (MXS) Platform. 2.0 Background Between 2019 and 2026, the Advanced Technology program office developed the MXS (pronounced “Maxis”) Platform as a modern security model, data model, reference architecture, and reference implementation, based on open standards and protocols to support software development and secure information sharing at multiple security levels. MXS' goal is to enable Protection Level 3 (PL3) software solution development by third-party developers within security-constrained environments, as typically employed by communities working with Special Access Programs (SAPs). 3.0 Description of Requirements 3.1 Scope & Operating Environment: AFLCMC/HNJT requires information on industry capabilities to operate, maintain, and continuously enhance a multi-tenant, cloud-native platform supporting Air Force and mission-partner applications. The platform operates across multiple security enclaves, including Unclassified, Secret//Special Access Required (SAR), Top Secret//SAR, and Top Secret//Sensitive Compartmented Information (SCI)//SAR cloud environments. 3.2 Platform Operations, Maintenance & DevSecOps: Prospective contractors are expected to provide proactive 24/7/365 system availability, platform administration, and lifecycle sustainment across all designated cloud environments. Core focus areas include: 3.2.1 Cloud-Native Infrastructure: Operating and maintaining containerized environments (e.g., Kubernetes), service meshes, Application Programming Interface (API) gateways, and Infrastructure-as-Code (IaC) baselines. 3.2.2 DevSecOps Toolchain: Sustaining an automated continuous integration/continuous delivery (CI/CD) pipeline that enables secure cross-domain software progression. 3.2.3 Telemetry & Resource Monitoring: Providing automated, granular visibility into platform health, microservice performance, compute/storage utilization, and licensing. 3.2.4 Enterprise ICAM & Certificate Services: operate and maintain enterprise identity management infrastructure across multiple tenants. 3.2.5 Managed Database Services, Registered Queries & API Mediation: Provision, sustain, and optimize managed database services across cloud environments, engineer registered and parameterized queries for controlled data access and governance, and diagnose latency or throughput bottlenecks. 3.3 Continuous Platform Evolution: Delivering agile enhancements, feature updates, and technical debt remediation in alignment with government-prioritized backlogs. 3.4 Tenant Enablement & Multi-Tier Support: To support diverse tenant software programs, the platform requires integrated customer enablement services. 3.4.1 Tenant Onboarding and Offboarding: Assisting tenant developer teams with architectural guidance, common control inheritance, and standardized integration toolkits. 3.4.2 Service Desk Operations: Operating a tiered technical service desk (Tier 1–3) providing incident management, troubleshooting, and user assistance across all classification levels. 3.5 Cybersecurity & Continuous Authorization: The platform must maintain a rigorous cybersecurity posture compliant with DoD, Intelligence Community, and SAP directives. 3.5.1 Sustaining existing Risk Management Framework (RMF) Authorizations to Operate (ATOs). 3.5.2 Executing Static Application Security Testing (SAST) and Dynamic Application Security Testing (DAST), container vulnerability assessments, dependency assessments (Software Bill of Materials (SBOM), Vulnerability Exploitability eXchange (VeX), etc.), and rapid vulnerability remediation. 3.5.3 Generating and maintaining RMF bodies of evidence and security documentation to maintain inheritance relationships for hosted software and systems. 3.6 Potential Security, Facility, and Personnel Requirements. The Government is conducting market research regarding the availability, timing, and feasibility of contractor personnel clearances, secure facilities, and cybersecurity qualifications that may be required for a future acquisition. The requirements of any future solicitation, including timing and acceptability of facilities, will be established only in that solicitation. 3.6.1 Personnel Clearances: Contractor personnel must possess active Top Secret clearances and applicable DoD 8140 baseline certifications at the time of contract award, with the ability to obtain SCI and SAP access within 30 days of contract award 3.6.2 Secure Facilities: Within 30 days of contract award, the Contractor shall possess and maintain accredited Sensitive Compartmented Information Facility (SCIFs)/Special Access Program Facility (SAPFs), as required to perform the classified development and operational activities under this contract. Each facility shall maintain current written accreditation by the cognizant accrediting authority and comply with applicable requirements of ICD 705, DoDM 5105.21, Volume 2, and DoDM 5205.07. 4.0 Specific Areas of Interest 4.1 Corporate Overview & Business Classification 4.1.1 Entity Identification: State your company name, Commercial and Government Entity (CAGE) code, and business size/socioeconomic status under the designated North American Industry Classification System (NAICS) code. 4.1.2 Contract Vehicles: List the relevant Government-Wide Acquisition Contracts (GWACs), Multiple Award Schedules (e.g., GSA MAS, NASA SEWP, OASIS+), or agency vehicles your organization currently holds. 4.2 Experience & Technical Approach 4.2.1 Relevant Past Performance: Provide up to three (3) examples (within the past 5 years) demonstrating prime or major subcontractor experience operating multi-tenant cloud platforms of comparable scope, complexity, and classification (including Amazon Web Services (AWS)/Azure Secret, Top Secret, or SAP enclaves). 4.2.2 Platform Management & DevSecOps: Describe your experience managing cloud-native infrastructure (e.g., Kubernetes, service mesh, Infrastructure as Code (IaC)) and sustaining multi-fabric DevSecOps pipelines across air-gapped or cross-domain environments. 4.2.3 Platform Software Development Kits (SDKs) & Toolkits: Summarize your experience developing and sustaining SDKs, shared libraries, and developer modules to accelerate tenant application delivery. 4.2.4 Enterprise Identity, Credential, and Access Management (ICAM) & Certificate Services: Describe your experience deploying and sustaining enterprise and external Certificate Authorities (CAs) across multi-tenant and air-gapped environments, including certificate validation and revocation infrastructure (e.g., Online Certificate Status Protocol (OCSP) responders, Certificate Revocation List (CRL) distribution points). 4.2.5 Managed Database Services, Registered Queries & API Mediation: Describe your experience provisioning, optimizing, and troubleshooting cloud-managed database services, including engineering registered and parameterized queries for controlled access and governance. Detail your experience developing middleware, abstraction layers, or gateway adapters for protocol bridging, query translation, and data transformation across disparate APIs. 4.2.6 Protection Level 3 (PL-3) Multi-Level Access Control & Attribute-Based Authorization: Describe your experience engineering and operating applications within PL3 SAR environments to restrict data access to users' explicit clearance and compartment authorizations. Detail your approach to synchronizing identity attributes from Authoritative Data Sources (ADS) and implementing, enforcing, and auditing Role-Based Access Control (RBAC), Mandatory Access Control (MAC), and Attribute-Based Access Control (ABAC) policies using Policy Enforcement Points (PEPs), Policy Decision Points (PDPs), and fine-grained, object-level filtering and data labeling. 4.3 Tenant Enablement & Multi-Tenant Operations 4.3.1 Onboarding & Isolation: Describe your approach to onboarding diverse tenant applications to a shared cloud environment while maintaining strict logical isolation, zero trust boundaries, and zero service interruption to existing tenants. 4.3.2 Training & Enablement: Outline the standard onboarding artifacts, API documentation, and training support that should be provided to tenant engineering teams. 4.3.3 Tiered Technical Support: Describe your operational model for delivering Tier 1–3 service desk and platform support across both unclassified and classified environments. 4.3.4 Service Level Agreements (SLAs) & Operational Sustainment: Describe your recommended Service Level Agreements (SLAs) for the platform, such as uptime/availability targets, incident response and resolution thresholds by severity, performance baselines, and Recovery Time Objective (RTO)/Recovery Point Objective (RPO) across unclassified and classified environments. Detail your operational support model, monitoring tooling, escalation procedures, and staffing strategy to guarantee and report on compliance with these metrics. 4.4 Cybersecurity & Compliance 4.4.1 Continuous Authorization: Detail your methodology for maintaining RMF accreditation. 4.4.2 Security Test Automation: Summarize your approach to code scanning and test automation to include tools, artifacts, processes, and gating criteria within a DevSecOps pipeline. 4.4.3 Security Standards Compliance: Outline your experience implementing JSIG/CNSSI 1253 Rev 5, DoDM 5205.07, Zero Trust Architecture, or any other applicable DoD/DoW requirements. 4.5 Security Clearances & Facilities 4.5.1 Personnel Clearance Readiness: Describe your labor pipeline and ability to provide qualified, certified personnel with Top Secret clearances with eligibility for access to SCI and SAP, and general timelines. 4.5.2 Secure Facility: Confirm whether your organization currently operates an accredited SCIF/SAPF suitable for classified contract execution or has a facility that could be accredited or modified within 30 days of contract award to meet applicable ICD 705 and SAP security requirements within the required contract performance timeline. 4.6 Cost Models, Funding Intake & Contract Structure 4.6.1 Cost Drivers: Identify primary cost drivers for baseline platform sustainment versus new feature development. 4.6.2 Consumption Metering & Showback: Describe your approach to tracking and reporting tenant consumption (compute, storage, service desk) to support customer-funded usage and line-of-accounting showback/chargeback. 4.6.3 Contract Structure Recommendations: Recommend suitable contract types (e.g., Firm Fixed Price, Time & Materials, hybrid) and incentive structures that balance performance, flexibility, and risk. 4.7 Contemplated Gating Strategy Feedback: The Government is contemplating an administrative Pass/Fail Phase 1 gate evaluated on an Acceptable/Unacceptable basis (e.g., verified prime contractor experience of similar scope, active facility clearance/accreditation, and baseline cyber certifications) prior to technical proposal evaluation. The contemplated gating approach is provided solely to obtain market research feedback. The Government has not established final evaluation factors, minimum qualification requirements, acquisition strategy, contract type, or source-selection methodology. Any future solicitation will independently state all applicable requirements and evaluation criteria. 4.7.1 Impact on Competition: Does the proposed Phase 1 gate unduly restrict your organization’s ability to compete as a prime contractor or participate as part of a joint venture/team? If yes, fully explain. 4.7.2 Recommended Criteria: What objective metrics, scope parameters, or dollar thresholds should define "similar experience" to ensure robust, qualified competition? 5.0 Response Interested vendors are invited to submit an unclassified capability statement demonstrating their ability to satisfy Section 3.0 requirements, along with detailed responses to the questions in Section 4.0. Do not include classified or SAP data in the submission. Submissions must not exceed twelve (12) single-spaced, single-sided pages (8.5 × 11 inch, 12-point font). Please send responses to this RFI electronically to the Contract Specialist within thirty (30) days after publication of this announcement. Questions concerning this RFI should be directed to Capt Matthew Gauert via email at matthew.gauert.2@us.af.mil with the subject line “RFI Response - MXS Platform O&M - [Company Name].” Note: only electronic responses will be considered. Respondent’s information shall contain respondent company name; company address; primary point of contact for information provided; and company website address that provides any additional information about the respondent’s company. Respondents shall clearly identify and mark any proprietary or confidential commercial information contained in their submissions. The Government will protect properly identified information from disclosure to the extent authorized by law and regulation. Information received may be used solely for market research and acquisition-planning purposes. Submission of a response does not grant the Government any license or other rights in a respondent’s proprietary information beyond those necessary to evaluate and use the response for those purposes. 6.0 Summary This RFI does not constitute an Invitation for Bids (IFB), Request for Proposal, Request for Quote (RFQ), nor does this issuance restrict the Government’s acquisition approach. Any information received is considered market research and may be utilized by the Air Force in developing its acquisition strategy. This market research will be used to assess the availability and adequacy of potential sources. The Government will not respond or conduct formal or informal briefings to vendors or respondents to this RFI. The Government does not reimburse respondents for any costs associated with submission of information being requested/received, nor reimburse expenses incurred to interested parties for responses to this RFI. THIS RFI IS ISSUED SOLELY FOR INFORMATION AND PLANNING PURPOSES AND DOES NOT CONSTITUTE A SOLICITATION. THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS RFI, AND RESPONSES TO THIS NOTICE ARE NOT OFFERS AND CANNOT BE ACCEPTED BY THE GOVERNMENT TO FORM A BINDING CONTRACT. RESPONSES TO THIS RFI WILL NOT BE RETURNED. | 65% | Market Research | 11/16/2026 |
Additional Details
Solicitation Number
NNG14475415R
Archive Date
Jan 1, 2022