Federated Search PWS.docx

PWS for <Project> Page 2 of 17

Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) Office of Intelligence Operations (OIO)

Performance Work Statement for the Federated Search

03/05/2026

Table of Contents

Note that while, as a matter of policy, some agencies require the government to prepare the PWS, the guidance at FAR 37.602(a) stipulates that “a Performance work statement (PWS) may be prepared by the Government or result from a Statement of objectives (SOO) prepared by the Government where the offeror proposes the PWS.”

Performance Work Statement (PWS) for the Federated Seach

The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) is a law enforcement agency within the United States Department of Justice (DOJ). ATF is dedicated to the reduction of violent crime and the protection of our nation. ATF is responsible for the investigation and prevention of crimes that involve the unlawful use, manufacture, sale, trafficking and possession of firearms, illegal use, and storage of explosives; acts of arson and bombings; acts of terrorism; and illegal trafficking of alcohol and tobacco products. ATF regulates the firearms and explosives industries from manufacture and/or importation through retail sale, and leverages partnerships to enhance its business in regulatory, law enforcement, training, and forensic mission areas. The commitment and skills of ATF’s employees are required to accomplish the Bureau’s critical mission.

The Office of Intelligence Operations (OIO) provides critical law-enforcement (LE) resources in support of reducing violent crime and protecting the public; and its mission has always been to enhance decision-making Bureau-wide by providing timely, accurate and focused intelligence through the collection and analysis of information. It is staffed by dedicated LE intelligence analysts, support professionals, and officials.

1.2 Objective

To enable Government to design, develop and implement a Federated Search solution that enables seamless, real-time information retrieval across the agency’s disparate digital platforms. By integrating multiple internal databases and content repositories into a single, centralized interface, the system will eliminate the need for manual, platform-specific queries, thereby reducing search latency and increasing operational efficiency. The solution must deliver consolidated, high accuracy results through a unified relevancy ranking system, ensuring that personnel can access critical data points instantly from a single point of entry while maintaining the integrity and security protocols of the underlying source systems.

1.3 Scope of Work

This contract will require a multiple disciplinary team of experts proficient in enterprise information architecture, secure API integration and advanced data retrieval algorithms. The contractor team must possess the technical maturity to bridge disparate data silos-ranging from the legacy on-premises databases to modern cloud-based applications- without compromising the performance of the source systems. Beyond mere software installation, the skill work encompasses the development of customized connectors, the importation of sophisticated relevancy-ranking-logic, and the design of highly intuitive user interface that mimics modern commercial search experiences. Success in this program relies on the contractor’s ability to harmonize complex backend security protocols (such as single sign-on and role-based access controls) with a frontend that deliveries fast, accurate and actionable results through a single, unified lens. The contractor shall provide all personnel and services necessary to design, develop, and maintain the Federated Search environment. This includes API development, data isolation protocols, and a comprehensive training program for Government personnel.

· Technical Requirements

· API and connector development

· Internal connectivity: The contractor shall develop and configure secure connectors for internal agency repositories (e.g. SharePoint, SQL, On-premises Files, shares, AWS, ETC) using industry-standard protocols. This shall be for ATF programs Spartan, Nforce, Ness, and Etrace.

· External Connectivity: The contractor shall develop connectors for the authorized external/third-party data sources. These sources shall be Accurint AVCC, Clear, i2 Analyst Notebook, Transunion TLO, Vigilant/ License Plate Reader, Pennlink, Tangles, and Whooster

· Data Segregation: The contractor shall implement a “Search-Time:” aggregation architecture. All data from the internal and external sources shall remain logically and physically separate within the indexing layer to prevent cross-contamination of sensitive data.

· Selective Query Logic: The user interface (UI) shall provide functional “toggle” or “filter” capabilities allowing users to explicitly select internal, external or hybrid search modes prior to query execution.

· Security and Compliance

· NIST Compliance: The solution shall comply with NIST SP 800-53 security controls at the (moderate/high) impact level.

· Identity Management: The system shall integrate with the Agency’s identity, credential, and access management (ICAM) system (e.g PIVCAC, OKATA, Active Directory)

· Section 508: The UI shall be fully compliant with Section 508 of the Rehabilitation Act (36 CFR 1194)

· Training and Knowledge Transfer:

· General User Training: Unlimited access to live and virtual training and on-demand web-based training (WBT) for the life of the contract.

· Project Manager (PM) Training: Technical Orientation on system analytics, vendor performance monitoring, and scalability management.

· Designated Security Officer (DSO) Training: Specialized instruction on audit log retrievals, encryption key management and data isolation verification.

· Environments:

· Production, Training and Testing and make assure scalability on all environments/platform for future needs

1.4 Background

The Government previously used Sematica pro as a Federated Search and was decommissioned in 2023 due maintenance and user experiences.

1.5 Type of Contract Contemplated

Government will issue a firm-fixed price task order for this requirement.

1.6 Period of Performance

The period of performance of this contract is a base year (12 months) and (4) one year options.

1.7 Place of Performance

Will be partially at the contractor’s location, located within the United States and partially at ATF headquarters as needed for meetings and onsite work needed with ATF OST.

1.8 Operating Constraints:

· Conformity to ATF’s Agile Scrum Methodology and IT Methodology: All Contractor provided work shall conform to the applicable policies, procedures, and standards described in the Attachment ATF IT Governance Manual. OST has developed and implemented an agile development methodology to enable the efficient development and delivery of applications. The ATF methodology is based on the “Agile Scrum” methodology and utilizes industry standard application development principles. This methodology is described in section 5 of Attachment: ATF IT Governance Manual in addition to Attachment: ATF Agile Playbook. As part of this ATF Agile Methodology, a continuous integration / continuous delivery environment (CI/CD) has been implemented. The environment, described in section 6 of Attachment: ATF IT Governance Manual, provides a complete set of tools to automate the development, testing, and deployment of applications in addition to Attachment: ATF Enterprise Standard Technologies

· Conformity to the Data Management Requirements: The Contractor shall conform to the data management requirements as prescribed by the ATF Data Management Division, refer to Attachment: Data Governance Handbook, version 4.2

· Conformity to ATF Enterprise Standard Technologies: Current technologies are listed in Attachment: ATF Enterprise Standard Technologies and Attachment. The tools listed in the attachment are subject to change with approval by the Chief Technology Officer (CTO). The contractor shall design, develop, and iteratively deploy a fully integrated Federated Search application that leverages ATF’s Application Architecture, DevOps framework and Attachment: SPARTAN UI & UX Style Guide.

Other Administrative Requirements The contractor shall:

1. Act as an independent contractor and not as an agent of the Government. Furnish management and labor necessary to perform the requirements in this statement of work and in partnership with government Product Owners. Examples of Government furnished equipment include workstations and enterprise software tools.

Obtain Government approval prior to use of contractor provided hardware and software in the performance of this work. Hardware, Commercial Off-the-Shelf (COTS) software, custom-developed software, and data provided during the execution of this contract shall become property of the Government.

Build the solution within Government approved GovCloud environments. The solution shall be built within Government authorized development, testing, training and production environments.

Collaborate with Government cloud support teams, the Information System Security Office (ISSO), ATF’s privacy office, the Government Task Monitor (GTM), the System Owner, and Product Owner before deploying to production.

Utilize commercial best practices when delivering services, including but not limited to:

Agile Scrum Methodology Continuous Integration/Continuous Delivery (CI/CD) Automated Testing Automated Deployments Use Government provided tools to accurately document, administer, maintain code, configuration settings, system documentation, project artifacts, and user guides. (Refer to Attachments: ATF IT Governance Manual;: ATF Enterprise Standard Technologies; Definition of Done User Story and Sprint Checklist; Attachment: ATF Governance Manual ver.4.2 ATF Agile Playbook; Attachment SPARTAN UI & UX Style Guide.

Use ATF CI/CD tools for system integration and stress testing. Refer to Attachment: ATF IT Governance Manual; Attachment: ATF Enterprise Standard Technologies Prepare and present written oral briefings on progress of work as requested by the Government.

Be able to interface effectively and professionally with Government personnel, DOJ and other component personnel, other Government contractors, and industry representatives. Maintaining proper business relationships with other contractor employees in a cooperative effort involving the Contacting Officer (CO), Contracting Officer’s Representative (COR), GTM, and appropriate project leads are critical to the success of this effort.

Comply with all Government Personnel and IT Security policies and procedures.

Perform and conduct work by contractor personnel who have completed a suitability determination by Government’s Personnel Security Division (PSD) Use industry standards and best practices where applicable to ensure the delivered product/service meets Government’s expectations.

If and when the Federated Search Application is transferred to a different contractor, conduct knowledge transfer sessions with the Government and new Contractor teams. Provide system documentation and any other artifacts as required by the Government and the teams assuming responsibility of the system. These actions shall be completed prior to the end of the contract period and any transition.

Agree to perform work during a normal work schedule. A normal work schedule consists of 8-hour workdays plus one-half hour or one hour for lunch, Monday through Friday, between the hours of 6:30 AM and 6:00 PM. If a contractor employee chooses to take a one-hour lunch, then the contractor employee must work a 9-hour day. A full-time resource shall not perform more than 1,912 hours per year unless approved in advance by the CO or COR/GTM. The core hours for contractor personnel shall be 9:00 AM – 3:00 PM Central time zone. The Government reserves the right to check the network logs to ensure contractor personnel are working the proper hours. If there is any evidence the contractor employee is not working the proper hours, the Government will reject any invoice that is invalid for hours claimed worked.

Implement all necessary work and time management control processes to endure timely accurate accomplishment of work requirements as well to permit tracking work in progress.

Any uses of artificial intelligence (AI) in the provided capabilities, whether they involve standalone AI capabilities or AI that is embedded within third-party products or services, must comply with the requirements set forth in ATF Executive Order 14110, Safe Secure and Trustworthy Development and Use of Artificial Intelligence, and Office of Management and Budget (OMB) memorandum M-24-10, Advancing Governance, Innovation, and Risk Management for Agency Use of Artificial Intelligence.

1.1. Applicable Documents

2.0 Specific Requirements/Tasks

Task 1: Project Management The contractor shall provide project management services (i.e., planning, direction, coordination, and control of contractor resources) to oversee and ensure the execution of the contract and deliver the stated required contract services and deliverables.

The contractor shall:

Provide a Project Manager that will act as the primary point of contact for resolving all contract execution issues between the contractor and the Government.

Provide project management staff with full company authority to oversee the assigned resources and enable rapid resolution of day-to-day service delivery issues.

Report issues affecting the performance of Contractor personnel to the immediate attention of the GTM/COR.

Provide project team with guidance on all areas of engagement and a primary customer contact for all major support issues through the length of the project.

Develop a Project Familiarization brief to demonstrate an understanding of the project.

Work in partnership with Government COR/GTM in conjunction with OST and the Product Owner to document and verify user stories (business requirements), and to identify the best approach or solution for implementing each user story.

Attend and provide leadership during routine management meetings.

Provide input during Sprint reviews on accomplishments and Product status.

Identify risks or issues during Sprint retrospectives.

Provide an Action Item list at each Sprint planning meeting.

Provide staffing updates at each Sprint retrospective.

Provide all reports and meeting notes stipulated in the SOW along with any other reports the Government deems necessary following the schedule outlined in Section 7.0, Deliverables.

Provide meeting notes as applicable across all tasks contained within the PWS.

Reports include:

Sprint Progress Report – This report shall include a burn down chart and velocity of the sprint. Include a count of backlog items broken down by severity/priority (i.e., Critical, High, Medium, Low) and type (i.e., new, defect, repeat defect) which may be generated from Digital AI within three (3) business days of the request of the Government.

Release Report – This report shall include the epic/user story and release burn down for any defined multi-sprint releases including technical information about changes, contributors, and potential issues within three (3) business days of the request of the Government.

Release Notes – This report shall include a summary of new features, bug fixes, and improvements within three (3) business days of the request of the Government.

Periodic reports and meetings related to project management, velocity, timelines, milestones, development, or other matters pertaining to the project, as determined by the Government shall be provided within three (3) business days of the request of the Government.

Task 2: Application Development The Contractor shall provide Federated Search development support overseeing the tasks and activities necessary to manage product backlogs, perform application development with security practices in place, deployment, and enhancements, as well as address defects, issues, and security findings as prioritized by the COR/GTM in conjunction with OST and the Product Owner.

Deployments of application development or enhanced functionality shall be made to production as frequently as is practical, as determined by the COR/GTM in conjunction with OST and the Product Owner and terms of any approved Deployment Automation Plan.

The Contractor shall develop, test, and support deployment of the Federated Search application following the ATF Agile methodology, so that new functionality can continue being deployed to production through frequent releases following the CI/CD pipeline. User stories (business requirements) will be captured in ATF’s Agile Project Management Tool (currently Digital.ai) to be placed in a product backlog. The COR/GTM in conjunction with OST and the Product Owner will be accountable for ensuring user stories are created, prioritized, and clearly communicated to the scrum team. As part of the delivery of the Task 3, the Contractor shall:

· Create a plan for the Sprint, Sprint backlog.

· Instill quality by adhering to the Definition of Done - Refer to Attachment: Definition of Done User Story and Sprint Checklist.

· Adapt their plan each day toward the Sprint Goal defined by the COR/GTM in conjunction with OST and the Product Owner.

· Leverage the ATF Agile Development Methodology to assess existing functionality and software architecture; plan iterative enhancement strategies to evolve products to the desired state; then design, develop, and deploy incremental product updates.

· Size story points based on complexity or risk utilizing the Fibonacci sequence or using a standard approach agreed upon by the COR/GTM in conjunction with OST and the Product Owner.

· Forecast backlog items and/or accompanying milestones, as appropriate.

· Develop and assist the COR/GTM in conjunction with OST and the Product Owner with verification of product backlog items.

· Develop a presentation of Engineering Practices geared for Automation of CI/CD pipeline.

· Create a Deployment Automation Plan.

Create features without existing open source drop in components:

Clean photo upload/thumbnail display.

Attach images to system generated e-mails with a queuing system to handle performance Develop a robust text editor with solution to allow formatting and images in line with text within the narrative sections.

Evaluate and update existing databases, structures, and schemas to optimize, eliminate redundancies, and inconsistencies while improving performance.

Develop APIs using industry standards and Attachment: ATF Data Governance Manual, ver. 4.2 to allow data sharing within all relevant ATF applications as well with other government agencies.

Update the Government data dictionary for each data element used by the API and develop data flow diagrams of core data used by each application.

Create /update table and column level description/definition (used by the API) using best practices to the authoritative database.

Develop application code to optimize performance.

Develop automated release package for all code deployment.

Make use of Government’s standard containerization platform for all deployments that can be containerized.

Automate the deployment using CI/CD pipeline.

Provide documentation stating which tests are run in the automated pipeline.

Ensure application is cluster-able and can be load balanced.

Ensure production deployments can be made with zero downtime, while users are using the application, to the maximum extent possible.

Automate application specific technology stack configurations using scripts and provided tools for the specific component.

Develop documentation outlined in Attachment: ATF IT Governance Manual, section IT Software/Systems Development Lifecycle. Refer to the Deliverables table. (Section 7) Enhance and maintain application to effectively handle usability and growth.

Address application related production issues/defects within 24-48 hours unless the issues/defects are with the servers, Government network, DNS, or other issues outside of contractor control.

Address application related security findings within the agreed upon timeline by the Product Owners.

Work closely with the OST Server Team, Database Administration (DBA) Team, and the Network Team to maintain the application.

Develop SQL Server Integration Services (SSIS) packages for Data Migration.

Maintain application infrastructure with timely upgrades of the development platform.

Comply with all Federal, DOJ and Government standards for application and system development.

Comply with Government configuration management policies and procedures.

Update and provide the Section 508 checklist within ten (10) business days after each release.

Develop 508 compliance code.

Assist with completing the Federated Search application ISSO paperwork.

· Provide expertise with the NIST 800-53 Rev 5 requirements, create, deliver, and maintain various system documentation in support of complying with Federal Information Security Management Act (FISMA) requirements to minimize cybersecurity risk.

· Apply security practices throughout the software development lifecycle.

· Work with the COR/GTM in conjunction with OST and the Product Owner to balance feature development with paying off technical debt, shoring up CI/CD, tooling, and architecture with a Technical Roadmap.

· The government shall retain ownership of the product backlog and may reprioritize, add, remove, or alter work items at any time.

· Changes to backlog items shall not constitute a contract modification provided the overall level of effort and team size remains within the agreed scope.

Task 3: UX Development The Contractor shall provide UI/UX expertise to design and develop high fidelity wireframes or pages utilizing Adobe XD in the Federated Seach Application as prioritized by the COR/GTM in conjunction with OST and the Product Owner.

The Contractor shall:

Translate business needs and optimize the look and usability of the application without affecting performance.

Illustrate design ideas using storyboards, process flows, and sitemaps.

Develop UI mockups, wireframes, and prototypes that clearly illustrate usability.

Develop graphic user interface elements, web pages, menus, tabs, widgets, and application navigation to meet Section 508 compliance.

Ensure style standards are consistent on fonts, colors, and images, refer to Attachment: SPARTAN UI & UX Style Guide.

Prepare and present improvement ideas to scrum team and key stakeholders.

Identify and troubleshoot UI/UX problems.

Conduct layout adjustments based on stakeholder’s feedback.

Develop mobile prototype(s), as prioritized by the COR/GTM in conjunction with OST and the Product Owner.

Develop a presentation of UX Designer Basic Design Principles.

Verify and validate that user experience requirements are met through user testing.

Task 4: Testing The contractor shall provide system testing support for the Federated Seach application. The Tester(s) assigned shall work closely with the development team, and COR/GTM in conjunction with OST and the Product Owner to develop automated repeatable tests for end-to-end Federated Seach application functionalities, effectively identify defects, and report to the development team for timely resolution. The Contractor shall:

Automate testing using tools available in ATF CI/CD environment.

Create and maintain end to end automated test scripts throughout the period of performance.

Conduct automated regression testing which includes functional testing.

Conduct load testing where applicable.

Identify ways to optimize and streamline application testing.

Identify and document application defects as user stories in ATF’s Agile project management tool.

Assist with smoke testing in conjunction with scheduled deployments.

Work with the Federated Seach application development team and Scrum Master to identify additional quality assurance and/or testing requirements for the Federated Seach application.

Develop User Acceptance Testing (UAT) criteria and work with COR/GTM in conjunction with the Product Owner on behalf of Government & external users to ensure defects identified by UAT personnel are documented and provided to the Federated Seach application development team.

Work with COR/GTM in conjunction with OST and the Product Owner to verify that all user stories pass all associated tests and acceptance criteria before they are accepted as complete.

Conduct System Integration testing.

Conduct security testing.

Conduct Section 508 testing.

Develop and utilize scripts for unit testing.

Conduct static code analysis.

Conduct integration testing.

Task 5: Transition Out During the final 60 days of the contract period, the Contractor shall work with COR/GTM, product owner and OST which is assuming responsibility for the Federated Seach application, to ensure proper hand-off and minimize operational impact to the Federated Seach application.

The Contractor shall provide a Transition plan as requested by the government to transition tasks from the last exercised option period to Government designated resources and any pertinent updates to documentation including but not limited to the development activities and operations and maintenance.

This plan shall include system management roles, systems access, technical overview of environments, environment builds, microservices, Application Programming Interfaces Schemas, CI/CD Pipeline, testing processes, GitLab repositories and data management, system technologies, libraries, and document libraries. The plan shall be reviewed and require Government acceptance before scheduling.

Task 6: Post-Production Support and Operations & Maintenance (Optional) This optional support may be exercised at any time during the period of performance based on the government’s needs, available funding, and/or satisfactory acceptance.

The Contractor will provide post-production support break-fix and minor enhancements (as determined by the Integrated Project Team).

The Contractor shall provide an O&M plan when/if this support is exercised at any point during the contract period of performance.

3.0 Contractor Quality Assurance.

· Supplies or services delivered under this contract shall be inspected and accepted by COR. The Contractor shall only tender for acceptance those items that conform to the requirements of this task order. The Government reserves the right to inspect or test any supplies or services that have been tendered for acceptance in accordance with the appropriate inspection and acceptance clause.

· The basis for acceptance shall be in compliance with the requirements set forth in this task order, and other terms and conditions. Deliverable items rejected shall be corrected in accordance with applicable clauses.

· Acceptance Criteria

· The COR will review all draft and final deliverables to ensure accuracy, functionality, completeness, professional quality, and overall compliance within the guidelines/requirements of the delivery order.

· The Contractor shall ensure the accuracy and completeness of all deliverables. Errors, misleading or unclear statements, incomplete or irrelevant information, and or excessive rhetoric, repetition, and “padding”, shall be considered deficiencies and shall be subject to correction by the Contractor, at no additional cost to the Government.

Unless otherwise indicated, the government will require 10 business days to review and comment on deliverables. If the deliverable does not meet the noted criteria, the Government will return it. If the Government does not respond in the 10 business day period, the contractor should verify that the deliverable has been accepted as delivered unless the government requests a delay in writing.

· Rejection Procedures. If the GTM/COR rejects any Deliverable, that rejected document will be handled in the following manner: (1) After notification the deliverable did not meet the acceptance criteria, the Contractor shall resubmit an updated/corrected version within three (3) business days after receipt of Government comments. (2) Upon re-submission by the Contractor, the Government will reapply the same acceptance criteria. If the deliverable does not meet the acceptance criteria a second time, the Government may consider the Contractor as having deficient performance with respect to the subject task.

· Any rework or rejected deliverables will be completed at no additional cost to the government.

· No payments will be issued against rejected deliverables, until they are corrected and accepted by the government. The contractor will not receive additional compensation for any additional work needed to correct rejected deliverables.

5.0 Meetings

Task One Task 1: Transition In

· Contract Kick-Off Meeting

· Within five (5) business days of the contract being awarded the Contractor shall schedule a kick-off meeting. This includes the Contracting Officer (CO), Contracting Officer’s Representative, (COR), Government Task Monitor (GTM), the Product Owner. The purpose of the meeting is to ensure a complete understanding and agreement of the scope by both the Government and the contractor. This meeting will be conducted virtually via Microsoft Teams or WebEx.

· The Contractor shall provide a kickoff briefing with an agenda and high-level approach for all tasks outlined within the SOW.

· The Contractor shall also document the kick-off meeting discussion and provide meeting minutes within three (3) business days of the meeting for review. Comments and clarifications from the Government shall be incorporated in the final version and are due back to the Government within three (3) business days of receipt of comments from the Goverment.

· Meeting topics shall include:

Introduction of key Contractor and Government personnel Team Structure Chart Government-furnished information Points of Contact Prioritization of Contractor activities (if applicable) Review of Assumptions (if applicable) Discuss personnel security requirements and designated security officer

· Project Kick off meeting

· Within five (5) business days of Key Personnel security packages being approved by PSD, the Contractor shall schedule a kick-off meeting with key personnel who will be assigned to the contract. This includes the Contracting Officer (CO), Contracting Officer’s Representative, (COR), Government Task Monitor (GTM), the Product Owner, and representatives from the Infrastructure, Data Governance, and CyberSecurity teams to review their understanding of the requirements, business norms, discuss the project/scoping approach, policies, procedures, project planning, metrics, deliverables, and milestones. The purpose of the meeting is to ensure a complete understanding and agreement of the scope by both the Government and the contractor. This meeting will be conducted virtually via Microsoft Teams or WebEx.

· The Contractor shall provide a kickoff briefing with an agenda and high-level approach for all tasks outlined within the PWS.

· The Contractor shall also document the kick-off meeting discussion and provide meeting minutes within three (3) business days of the meeting for review. Comments and clarifications from the Government shall be incorporated in the final version and are due back to the Government within three (3) business days of receipt of comments from the Government.

Meeting topics shall include:

Introduction of key Contractor and Government personnel performing work under the various tasks in this contract.

Team Structure Chart Government furnished information Status Reporting at Sprint Reviews, Sprint Retrospectives Points of Contact Prioritization of Contractor activities (if applicable) Review of Assumptions (if applicable) The government is amenable to adding other topics to the meeting as suggested by the Contractor Security & Background Investigations The COR/GTM will provide the required forms and information to the contractor immediately upon contract award. Security packages for all contractor staff that will work on this contract shall be submitted within fifteen (15) business days of contract award. The person responsible for interfacing with the Contractor on security related matters will be identified during the Contract’s Kick-Off meeting.

Please note it may take 60-120 days for individuals to be successfully adjudicated via a full Government background investigation. There are times when waivers may be granted or reciprocity applied, if a previous background investigation has been completed that meets Government’s personnel security requirements, but the contractor should expect up to at least 120 days for the background investigation process to be completed. The Government will make every effort possible to expedite this process. Individuals may be granted permission to work on tasks that do not require access to Government systems or information. The Government Task Manager (GTM) or Contracting Officer’s Representative (COR) will make this determination as needed. As individuals are cleared, the Government expects them to begin work immediately.

6.0 Government Furnished Property/Equipment/Information

· The Government will provide the following government furnished items:

1. Laptops or similar devices with keyboard, mouse, and docking station

1. Computer monitor(s)

1. ATF Contractor ID and PIV card

PWS for Federated Search Page 2 of 17

Source Selection Information – See FAR 2.101 and 3.104.

Table 1: Model for List of Deliverables For fixed-price line items:

OR

Period of performance Destination

OR

Place of performance SOW reference*

Typically one, but If multiple accounting classifications for a single deliverable apply, include the dollar amount for each

Due date or frequency

Not required in the line item if there are associated deliverable subline items that include the actual detailed identification

002-01

002-02

For informational (administrative) subline items, an accounting classification citation is not required

Add rows as needed

For cost-reimbursement line items:

OR

Period of performance Destination

OR

Place of performance SOW reference*

Typically one, but if multiple accounting classifications for a single deliverable apply, include the dollar amount for each

Due date or frequency

002-01

002-01

Add rows as needed image1.jpeg