Federated Search

The RFI clarifies discrepancies regarding submission deadlines, confirming GSA eBuy as the active platform until March 25. It specifies that the RFI is open market research for all businesses, not exclusively small businesses. The document also addresses submission format, indicating that a 15-page white paper in PDF format should be attached, rather than using eBuy's fields. Key technical requirements include an advanced hybrid retrieval model for federated search, handling 1-5TB of data with an annual growth of 500GB-1TB, and implementing Attribute-Based Access Control (ABAC) with field-level granularity. The system should support up to 500 concurrent users. ATF will provide AWS GovCloud environments, CI/CD pipelines, and licenses for required tools like Digital.ai. All work must be completed onsite at ATF Headquarters in Washington, DC, with all personnel requiring SECRET eligibility. The anticipated architecture is a hybrid federated-plus-indexed model with centralized metadata storage. Mandatory components include photo upload, image attachments, robust text editing, database optimization, API development, and SSIS packages. The contractor will support a new Authority to Operate (ATO) package, with FedRAMP authorization preferred for COTS components. The system is expected to support 5000 accounts with 500 concurrent users and handle an estimated 83 million records with 20% annual growth. The contract vehicle and specific socio-economic set-aside are yet to be defined.

The Spartan UI & UX Style Guide outlines the design principles for the Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) new case management system, Spartan. The guide details critical elements such as the ATF Seal symbolism and the Spartan mission statement, emphasizing innovation in criminal enforcement and industry operations. It specifies primary and secondary color palettes, banner and form state colors, and background colors. Typography is standardized to Open Sans, with guidelines for fonts, sizes, link styles, body text, and headings. The document also covers UI elements like buttons (styles, sizes, states), sidebars, global navigation, checkboxes, radio buttons, form elements, and specialized templates like the Rich Text Editor and Date Format. Screen structure, imagery for home and alternate backgrounds, application headers, search bars, and contact cards are all defined. Additionally, it provides banner styles, notification placements, banner verbiage for various messages (success, error, warning, information), and email content styling for external communications. Iconography for records, processes, licenses, and general system functions is included, along with instructions for screen instructions, milestone transitions, and receiving new assignments.

The ATF Agile Playbook outlines the methodology, practices, and artifacts for teams engaged in ATF Agile projects, emphasizing scope flexibility, team empowerment, and continuous improvement through iterative and incremental development. It details a Scrum-based process adapted for ATF's specific needs, focusing on frequent delivery of working products for feedback. The playbook is maintained on SharePoint for easy updates and covers the project lifecycle from Discovery/Sprint 0 through Release Integration testing. It defines roles and responsibilities for a core team (Product Owner, Scrum Master, Developers, Testers) and supporting teams (SMEs, DBAs, Security Officers), ensuring a collaborative and efficient development process. The accompanying Agile Tool Suite provides software and infrastructure to support this Agile enablement effort, aiming to improve software quality and reduce delivery time by replacing traditional quality control with continuous integration and automation, with a long-term goal of achieving continuous delivery.

The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) and the United States Bomb Data Center (USBDC) have outlined comprehensive checklists for their "Definition of Done" in user stories and sprints, specifically for the Bomb Arson Tracking System (BATS) Modernization project. The User Story Checklist details 18 tasks, ensuring completeness of tasks, code reviews, acceptance criteria fulfillment, and validation of non-functional requirements such as performance, maintainability, scalability, and security. It also emphasizes Section 508 compliance, thorough testing (unit, end-to-end, functional), documentation updates, and security vulnerability checks. User stories must be accepted by the Product Owner. The Sprint Checklist, comprising nine tasks, builds upon the user story requirements, mandating that all user stories within a sprint meet their "Definition of Done." It also includes passing all unit tests, fixing bugs, moving incomplete stories to the Product Backlog, updating the backlog, and ensuring environments are prepared for release. The staging environment is designated for production pushes, not testing.

The ATF O 7231.1 order establishes the Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) Data Governance Policy, outlining technical and behavioral standards for data creation, management, quality, consistency, security, compliance, and access. It assigns responsibilities to various offices and individuals, emphasizing data governance as a crucial element for successful business processes and protecting information assets. The policy details a data governance framework, activities, benefits, and goals, including establishing a governance structure, defining operational roles, and enforcing compliance. Key stakeholders and their roles, such as the Chief Data Officer, Data Governance Board, Data Owners, and Data Stewards, are identified. The policy also addresses data stewardship, existing data guidelines, new data acquisition, standard database design, and naming conventions. The Office of the Chief Data Officer leads data-driven strategies to enhance decision-making and operational efficiency, working with the Data Governance Board to ensure data standardization and effective management.

The Department of Justice's Bureau of Alcohol, Tobacco, Firearms, and Explosives (ATF) Data Governance Handbook (Version 4.2, updated March 11, 2019) outlines data governance standards and guidelines for developing, enhancing, and maintaining new and existing systems. Applicable to all ATF project personnel, the handbook aims to provide a comprehensive reference for data management. It details the benefits of data governance and standardization, responsibilities of data governance and development teams, and the Database Development Life Cycle. Key sections cover data administration, database security, design and naming standards for various database objects (tables, columns, indexes, views, etc.), common data elements (CDE), and data access API standards. The document emphasizes the use of ER Studio Data Architect for modeling and adherence to NIEM standards where appropriate. It also addresses data migration, design reviews, change management, and configuration management procedures for new and modified databases.

This document,

The U.S. Department of Justice, Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) issued a Request For Information (RFI) for planning purposes to identify small businesses capable of developing and implementing a scalable Federated Search solution. This solution aims to enable real-time information retrieval across ATF's disparate internal and authorized external digital platforms. Key requirements include secure internal and external data connectivity, data segregation to prevent cross-contamination, selective query logic in the user interface, and scalability across production, training, and testing environments. The solution must comply with NIST SP 800-53 security controls, integrate with the agency's Identity, Credential, and Access Management (ICAM) system, and adhere to Section 508 accessibility standards. The RFI also emphasizes conformity to ATF’s Agile Scrum and IT methodologies, data management requirements, and enterprise standard technologies. Respondents are asked to provide information on their company's capabilities, past performance, program management experience, security and compliance expertise, and operations and maintenance experience. Responses are due by March 20, 2026.

The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) Office of Intelligence Operations (OIO) is seeking a contractor for a Federated Search solution. The objective is to design, develop, and implement a seamless, real-time information retrieval system that integrates multiple internal and external data sources into a single, centralized interface. This will reduce search latency and increase operational efficiency for law enforcement intelligence analysts. The scope of work includes developing customized connectors for various platforms (e.g., SharePoint, SQL, AWS, Accurint AVCC, Clear), implementing data segregation, and ensuring NIST SP 800-53 security compliance and Section 508 accessibility. The contractor will also provide comprehensive training, adhere to ATF's Agile Scrum Methodology, and be responsible for project management, application development, UI/UX development, and testing. The contract is a firm-fixed price task order with a base year and four one-year options, requiring work at both the contractor's location and ATF headquarters. The solution must comply with various ATF IT governance and data management standards.