RFI Elastic Alternative - Analysis.xlsx
XLSX spreadsheet 19 KB Posted
- Attached to
- FA8307_RFI_Elastic_Alternatives
- Solicitation number
- HNCKP_Platform_One_FY25_Elastic_Licenses
About this file
This is a Request for Information (RFI) spreadsheet seeking alternative solutions to Elastic software licensing for the Department of Air Force's Platform One (P1) program. The RFI requests detailed information about alternative licensing models, including enterprise, cloud-managed, and open-source editions, with specific focus on how these alternatives compare to current Elastic licensing in terms of features, restrictions, and capabilities.
The document includes a comprehensive requirements capability sheet with 31 specific technical requirements, focusing on capabilities such as log aggregation, data integration, visualization tools, FedRAMP authorization, Kubernetes support, and security features including RBAC and ABAC implementation. Vendors must indicate whether each capability is available on day one or planned for future implementation. The RFI also requests pricing information, including transition and training costs, various pricing plans (monthly, trial, annual), and willingness to enter into contracts with a base year plus up to four option years. Responses must address deployment in GovCloud Impact Level 5 and 6 environments and demonstrate ability to handle terabytes of daily data ingest.
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
RFI Excel version of Word sheet
| Alternative License Types: | |
| 1 | What alternate licensing models or solutions do you offer for Elastic? |
(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: | |
| 1 | For 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: | |
| 1 | Are 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
| Elastic ALTERNATIVE: | [PUT NAME HERE] | ||||
| Instructions: | Please select Y/N | Please select Y if Yes, N if no plans, or N/A if ready on day 1 | Please insert # of days from award to build capability or a date if known | Please insert comments, questions, or concerns for each requirement if needed | |
| Requirement: | Ready on Day 1 | Future Capability | Estimated date of Capability | Comments | |
| 1 | Ability to aggregate logs from all systems and applications | ||||
| 2 | Data integration enabling correlation and analysis of historical logs with real-time ingest | ||||
| 3 | Create visualizations for application and infrastructure monitoring | ||||
| 4 | Ability to create custom alerts | ||||
| 5 | Scalabe to handle order of magnitude of terrabytes of ingest per day | ||||
| 6 | Handle large amounts of diverse data/logs | ||||
| 7 | Ability to save searches/queries as a template for future triage use | ||||
| 8 | Ability to share searches/queries among users | ||||
| 9 | Ability to view and audit history of searches/queries among users | ||||
| 10 | Existing FedRAMP authorization and compatibility to be deployed on GovCloud Impact Level 5 and 6 environments | ||||
| 11 | Comprehensive documentation for setup, configuration, and operation | ||||
| 12 | Training courses available on configuration and operation of the software | ||||
| 13 | Natively support Kubernetes container deployment via Helm Charts | ||||
| 14 | High availability and failover mechanisms | ||||
| 15 | Distributed architecture and ability to federate and share data with other organizations' deployments of software in hybrid- and multi-cloud ecosystem | ||||
| 16 | Role-Based Access Control (RBAC): Fine-grained access control to restrict user access to specific data, indices, and dashboards based on roles. | ||||
| 17 | Attribute-based access controls (ABAC) implementation | ||||
| 18 | Authentication & Single sign-on: Integration with enterprise identity management systems (e.g., LDAP, Active Directory, OAuth). | ||||
| 19 | Audit Logging : traceability of all user log-ins, log-outs, and activities | ||||
| 20 | Data Lifecycle Management: Integration with ILM (Index Lifecycle Management) for managing indices across different phases (hot, warm, cold, and frozen). | ||||
| 21 | Incident Management System capability built-in | ||||
| 23 | Pre-built integrations available to other Incident Management Systems | ||||
| 24 | Ability to ingest logs from Fluentbit/Fluentd and logstash | ||||
| 25 | Security Orchestration Automation and Response built-in capability or integrations available | ||||
| 26 | Ability to execute complex searches over multiple ingest sources across terrabytes of data | ||||
| 27 | Adjustable/customizable User Interface | ||||
| 28 | Ability to filter logs by specific fields and timeframe | ||||
| 29 | Ability to tag and transform the data as it is collected/ingested | ||||
| 30 | Ability to save snapshots for long-term storage beyond normal retention policies for select data feeds and timeframes of interest | ||||
| 31 | Threat intelligence integration capability |
Leave Blank(DO NOT DELETE)
| Y | Y |
| N | N |
| N/A |
File details come from the government source that posted it. Updated .