RFI_Odoo_FY26.xlsx

XLSX spreadsheet 26 KB Posted

Attached to
ODOO or Alternatives - Request for Information
Solicitation number
FA830726RB026
Issued by

About this file

This file is a Request for Information (RFI) Requirements Capability Sheet issued by the Air Force Life Cycle Management Center (AFLCMC), Cryptologic and Cyber Systems Division (CCSD), located at Joint Base San Antonio-Lackland, Texas. The RFI explicitly states this is market research for software alternatives and is not intended for award evaluation. Vendors are requested to provide information about Odoo licensing alternatives, including details on enterprise, cloud-managed, and open-source/community editions, along with how each option differs in features, scalability, support, and compliance capabilities related to logging and monitoring needs.

The submission template requires vendors to complete several sections: alternative licensing models with comparisons to the listed license; pricing information including transition costs, training schedules, and pricing plans (monthly, trial, annual); and other considerations such as advanced features and contract term flexibility (base year plus up to four one-year options). Vendors must complete a detailed Requirements Capability Sheet indicating whether 19 specific technical and functional capabilities are ready on day one, planned for future implementation, or available upon award. Key requirements include self-hosting, containerization with Helm Charts, AWS EKS compatibility, SSO/OIDC/SAML support, full ERP tooling, CRM, accounting suite, project management, eSignature capability, API compatibility with Atlassian Jira and Confluence, and compatibility with Accumulus and Kubecost systems. All responses must be submitted using the attached Excel template to the listed points of contact.

View the file

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

T&C and Contact Information

Note: Please read and complete the middle portion.
1This solicitation is issued in accordance with Federal Acquisition Regulation (FAR) Part 12, Acquisition of Commercial Products and Commercial Services, and in conjunction with FAR Part 13, 14, or 15 procedures as specified in the accompanying solicitation documents. The Air Force Life Cycle Management Center (AFLCMC), Cryptologic and Cyber Systems Division (CCSD), Joint Base San Antonio–Lackland, Texas, hereby requests proposals from responsible and qualified offerors for the commercial products and/or services described in this solicitation.

This announcement constitutes a formal request for information (RFI). The Government intends to award a contract resulting from this solicitation to the offeror whose proposal represents the best value to the Government, as determined in accordance with the evaluation criteria set forth herein. Offerors are responsible for reviewing all solicitation provisions, clauses, attachments, and amendments. Submission of a proposal shall signify the offeror’s acknowledgment, understanding, and acceptance of all terms and conditions included in this solicitation.

The Government anticipates using streamlined procedures authorized under FAR Part 12 to the maximum extent practicable. Offerors must ensure that all proposed products and services meet the definition of “commercial” as defined in FAR 2.101.

2 This announcement constitutes a formal solicitation for commercial products and/or commercial services in accordance with FAR Part 12. Offerors are invited to submit proposals in response to the requirements identified in this solicitation. All submitted proposals shall be prepared in accordance with the instructions, terms, and conditions provided herein and in any accompanying attachments or amendments.

This solicitation is a request for proposals and may result in the award of a contract. The Government reserves the right to award without discussions, to hold discussions if necessary, or to make no award depending on the needs of the Government and the quality of the proposals received. Offerors are responsible for monitoring this solicitation for any amendments or updates.

By submitting a proposal, offerors acknowledge and understand that the Government is not obligated to award a contract and that the preparation of proposals is at the offeror’s own expense. The Government will not pay for any costs associated with preparing or submitting proposals, participating in discussions, or providing additional information.

Company Name:
CAGE Code:
Address:
POC Name:
POC E-mail:
POC Phone Number:
3As indicated above, this is solely market research for software alternatives. Please be advised that any quote for software that is already in use, quote for alternative software, or any submissions intended for award evaluation should not be included in conjunction with this document. Any input on this document that contains responses for the software already in-use should not be included and should only contain alternative software data/answers. Your responses will only be used for planning purposes. Please address any comments and/or questions you may have regarding this RFI in writing to the listed POC.

RFI Q&A

Alternative License Types:
1What alternate licensing models or solutions do you offer for Odoo?

(Please provide details on available options, such as enterprise, cloud-managed, or open-source/community editions. For each licensing option/solution set, please provide how it differs from the listed license.)

2 For each licensing option/solution set, please provide how it is similar from the listed license.

(Specify any feature restrictions, scalability limitations, or support differences among the licenses (e.g., data retention, search query limits, or alerting capabilities)

3 For each licensing option/solution set, please provide how it meets the above requirements.

(Identify core features or capabilities that are shared across all options, such as log aggregation, visualization tools, and monitoring capabilities, regardless of the license type.)

4 For each licensing option/solution set, clarify how it meets the above requirements for our logging and monitoring needs.

(Please highlight specific ways in which each licensing tier can address our operational, security, and compliance needs, particularly in areas like multi-environment visibility, role-based access control, and support for compliance auditing.)

Pricing Information:
1For each license, please provide estimated transition and training costs and schedule for both transitioning to and from your proposed solution.

(Include details on onboarding costs, consulting, or configuration support required for a smooth transition. Specify any training options available, such as workshops, online courses, or documentation resources, and their associated costs.)

2 For each license, please provide any price plans associated such as monthly, trial, annual.

(Indicate if discounts are offered for longer-term contracts or high-volume deployments. For cloud-managed options, provide cost breakdowns for storage, query processing, and other usage-based charges.)

Other Considerations:
1Are there any additional features or benefits associated with the different licenses that we should consider?

For example, are advanced analytics, machine learning-based anomaly detection, or pre-built integrations with other monitoring tools included at higher licensing tiers? - Clarify any value-added services, such as dedicated account support, proactive health checks, or best-practice workshops, that come with certain licenses.

2 Is your company willing to enter into contracts with a base year with up to four one-year options? If not, how many years is your company willing to agree to?

(For longer-term contracts, specify any guarantees on pricing, renewal terms, or opportunities to adjust the contract scope to accommodate potential changes in our data volume or monitoring requirements.)

Requirements Capability Sheet

Odoo Alternative:[PUT NAME HERE]
Instructions:Please select Y/NPlease select Y if Yes, N if no plans, or N/A if ready on day 1Please insert # of days from award to build capability or a date if knownPlease insert comments, questions, or concerns for each requirement if needed
Requirement:Ready on Day 1Future CapabilityEstimated date of CapabilityComments
1Must be capable of being self-hosted.
2Must be capable of being containerized.
3Must be deployable with containers and Helm Charts.
4Must be compatible with Amazon Web Services (AWS) EKS.
5The solution must be able to leverage Single Sign On (SSO), and OIDC and SAML compatibility.
6Must provide a full suite of ERP tooling
7Must Provide Contacts Management system
8Must provide CRM capability for tracking multiple companies and all business workflows
9Must provide complete quotation and sales capability for selling and tracking customer purchases
10Must provide LMS for training program
11Must provide a full Accounting suite
12Must provide a complete suite of marketing, survey, social media managemnt, and Event management
13Must provide a complete Project Management suite capable of running complex projects across multiple orgs and companies
14Must be capable or eSign
15Must provide complete workforce task management capability
16Must provide customizable customer, product, lead, and sales dashboardss for external review and consumption
17All modules must be cross-module capable with the ability to share data across all workflow stages
18Must be API compatible with all Atlassian Jira and Confluence systems
19Must be API and Database compatible with Accumulus and Kubecost systems

File details come from the government source that posted it. Updated .