RFI QA - Brand Name or Equal WebFocus.xlsx
XLSX spreadsheet 11 KB Posted
- Solicitation number
- Not on record
About this file
This is a Questions and Answers document from an RFI (Request for Information) regarding business intelligence software solutions equivalent to WebFOCUS. The FBI's Analytical Technology Services (ATS) division issued this RFI to evaluate vendor capabilities for deploying a COTS BI platform in secure, air-gapped environments. The Q&A addresses clarifications on technical requirements outlined in the Statement of Work, including approval workflow capabilities, read/write adapter functionality for data integration, device auto-discovery and CMDB integration, server utilization monitoring across FBI infrastructure and cloud environments (AWS-SC2S), and data lineage/metadata visibility for tracking dataset creation and transformation logic.
The document also seeks clarification on licensing quantities and pricing models, as the government is evaluating support for up to 5,000 user licenses distributed across three categories: 3,000 general users, 1,500 ad hoc reporting users, and nine developer users. The government specifically requests comparative pricing breakdowns across different licensing tiers to conduct cost-benefit analysis, given that active user volumes are expected to be dynamic. Vendors are asked to confirm whether the 5,000-user total is an aggregate or additive to the specified user categories, and whether counts represent named users or concurrent users. The RFI emphasizes the need for solutions that support HTML and JavaScript form-based workflow development, integration with existing FBI IT service-management and case-management systems via APIs, and the ability to collect monitoring metrics from enterprise tools including Windows and AWS platforms.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DRAFT Statement of Work (SOW) WebFOCUS .pdf | ||
| WebFOCUS_RFI Final.pdf |
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
Sheet1
| Brand Name or Equal to WebFocus RFI | |
| Q&A | |
| Question | Answer |
| Please define the “approval workflows” referenced in SOW §1.1, including the business process being approved, the participants, required routing or escalation, and any audit-history requirements. Would integration with an existing FBI workflow, IT service-management, or case-management system through supported APIs satisfy this requirement? | Approval workflow, We are trying to ensure support in capability of utilizing HTML & Javascript forms to build our transactional workflows of ingested data in WebFocus remains. |
Integrating with existing workflow, IT service management through supported API is beneficial as well.
For TR-3-02 through TR-3-04 and TR-3-11, please confirm whether the “read/write adapter” language is primarily intended to ensure that the solution can read and combine data from the identified sources. If limited write capability is required, would controlled entry of discrete values—such as comments, status updates, annotations, or approvals—through an integrated write-back utility into a designated database table satisfy the requirement, without directly updating the underlying systems of record? Read/write adapter (To ensure we have connectors to read and combine data from intended data sources)
| TR-4-07 appears incomplete: “Supports device self-discovery option for populating.” Please provide the complete requirement and clarify what must be populated, the types of devices to be discovered, and whether active network discovery is required. Would importing device inventory from an existing CMDB, asset-management system, or infrastructure-monitoring platform satisfy this requirement? | Looking for Automatic Data discovery, connected data environments (databases, files, views, etc.) and automatically detect available tables, fields, and structures. |
| For TR-4-08, does server-utilization monitoring apply only to servers supporting the proposed BI platform, or to the broader FBI infrastructure? Would collecting metrics through existing Windows, AWS-SC2S, or enterprise monitoring tools and loading those metrics into the BI platform for reporting satisfy the requirement? | Both to some extent goal is to have ability to collect different metrics through existing Windows, AWS-SC2S, or enterprise monitoring tools and loading those metrics into the BI platform for reporting |
| For TR-3-16, please clarify what level of visibility is required to demonstrate how datasets are created and changed. Would the ability to review the application’s data load script—including source connections, transformation logic, joins, filters, and calculated fields—satisfy this requirement? | We want to have as granular capability as possible engrained through metadata. Source connection, Transformation logic, filters, calculated fields, load time. |
| Please clarify the intended licensing quantities and user populations. Is the requirement for “up to 5,000 user licenses” an aggregate total that includes the 1,500 ad hoc reporting users and nine developer users, or are those quantities additive? The deliverables section separately identifies 3,000 general users, 1,500 ad hoc users, and nine developers. Please confirm the total number of unique users, whether users may overlap across categories, and whether the counts represent named users or expected concurrent users. | We are currently evaluating licensing models to support an expected user base of up to 5,000 individuals. Because our active user volumes are dynamic, we need to understand how different pricing structures scale.Could you please provide a comparative pricing breakdown for different models? Having visibility into these tiers will allow us to run a cost-benefit analysis and determine the most optimized license count. |
File details come from the government source that posted it. Updated .