PWS.pdf

Performance Work Statement (PWS)

General

1.1 Introduction

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 Science and Technology (OST) is responsible for supporting ATF’s mission through delivery of professional, high-quality services related to information, financial investigation, laboratories, and through the strategic acquisition and/or development of advanced technologies supporting ATF. Implementation of this strategy will ensure a robust enterprise infrastructure and support the delivery of services to ATF’s stakeholders, Federal, State, local, tribal, and international law enforcement partners. Effective delivery of these services will facilitate information sharing between ATF personnel and partners, including providing real-time data to agents, investigators, and intelligence specialists in the field.

OST has developed an ATF Application Architecture based on Software Defined Architecture (SDA) concepts leveraging applications programmable interfaces (APIs) to achieve application integration, data access, and data sharing between ATF mission’s applications. The application architecture will allow data sharing between ATF and other government agencies. As OST modernizes legacy applications, the new applications will utilize the ATF Application Architecture.

The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) Laboratory Services Division comprises four laboratories in three locations. Two laboratories are Forensic Science Laboratories (FSLs) and are located in Atlanta, Georgia (FSL-A); and Beltsville, Maryland (FSL-W). A new laboratory site located in Wichita, Kansas will house the Forensic Crime Gun Intelligence Laboratory (FCGIL). The fourth laboratory is the Fire Research Laboratory (FRL) that is co-located with the FSL-W in Beltsville, Maryland. In general, the FSLs serve distinct geographic regions, but, casework is sometimes transferred between laboratories for logistical reasons. The FRL supports all ATF offices.

The Laboratory Services Division employs approximately 250 chemists, engineers, firearm and toolmark examiners, fingerprint specialists, biologists, questioned document examiners, specialized laboratory technicians and administrative support personnel. Three laboratories are currently accredited by ANAB under the ISO/IEC 17025 criteria. The new laboratory, FCGIL, accreditation will be forthcoming.

ATF Laboratory Services provide scientific and engineering services in support of ATF’s law enforcement mission, which focuses on violent crime. Primary areas of ATF jurisdiction include criminal activity related to firearms, arson, and explosives.

FSL Examinations:

The FSLs conduct examinations of physical evidence in the following areas of forensic science:

• Firearm and Toolmark Examinations, including microscopic comparisons of fired ammunition components, toolmark examinations and comparisons, and serial number restorations;

• Explosives Examinations, including the chemical analysis of intact explosive materials, post-blast residues, precursor chemicals, and the examination, identification and comparison of components used in improvised explosives devices (IEDs);

• Fire Debris Analysis, including the chemical analysis of materials recovered from fire scenes for the presence of ignitable liquids, and the examination of incendiary devices or chemicals;

• DNA, including the examination of biological evidence to associate individuals to crime scene evidence, primarily through “trace DNA”. Suitable DNA profiles are uploaded to CODIS databases to aid in providing investigative leads;

• Latent Print Examinations, including the development and comparison of friction ridge detail from fingers, palms, or soles of feet; entry into and searching the NGI database;

• Impressions, including the examination, characterization and comparison of shoe, tire or other impressions;

• Trace Evidence, including examination of hairs, fibers and fabrics, coatings, polymers, pressure sensitive tapes, glass, and general chemical unknowns;

• Questioned Documents, including the examination of handwriting and hand printing, the detection of altered documents, and restoration and identification of obliterated or indented writing; and

• Triage, including the development of friction ridge detail, sampling for potential DNA evidence, and test firing firearms.

FRL Examinations:

The FRL conducts examinations, some of which do not include physical evidence submitted to the laboratory, in support of fire investigations to aid in origin and cause determinations, including:

• Engineering evidence examinations, including testing and failure analysis of electrical products, fire protection devices, components, equipment and wiring. This type of examination may include examination of evidence that was submitted to the laboratory or evidence that was examined at a remote location. This type of examination also includes examining exemplar items;

• Engineering testing, including testing in accordance with ASTM, ISO, and NFPA test standards as well as discrete event simulation in accordance with methods published by ATF. This type of examination may include examination of evidence that was submitted to the laboratory or evidence that was examined at a remote location and was never in ATF custody. This type of examination also includes examining exemplar items. This type of examination may not include any physical evidence;

• Engineering analysis, potentially including calculations, computer modeling, hypothesis testing, and evaluating opinions from non-ATF experts; these types of examinations frequently do not involve physical evidence; and

• On-Scene Support, including on-scene examinations, witness interviews, calculations, analyses, and other services requested by the customer.

• FRL employs a wide variety of scientific and analytical instrumentation. Many of the instruments used in FRL tests are managed by FireTOSS, a unique software system developed for the FRL to convert, store, and manage instrument data.

In addition to the examinations listed above, scientists and engineers from all four laboratories have other major job functions for which time is tracked. Examiners and engineers conduct research to improve analytical methods and understanding of issues related to fire, explosives, and firearms. Laboratory personnel respond with ATF’s National Response Team that investigates major fire and or explosion scenes and laboratory personnel may also be called upon to provide technical assistance for search warrants or other situations. Laboratory personnel also provide expert testimony in courts of law, provide training to law enforcement and scientific/engineering personnel locally, nationally, and internationally, and represent the ATF in professional committees.

As awareness of the need for explosives and firearms expertise in national security initiatives increases, it is expected that ATF will have additional information sharing challenges. Secure, efficient methods for collaborating and sharing information with other Department of Justice and Homeland Security partner agencies will be a necessary future responsibility of ATF. This responsibility should be supported by the acquired LIMS solution. The proposed LIMS solution should offer sufficient flexibility to be able to accommodate potential future expansions.

1.2 Objective

The objective of this acquisition is to further streamline Laboratory Services existing workflow processes with a technological LIMS solution that will increase overall productivity by providing improved user experience and usability through an organized, integrated, and highly intuitive user interface.

The LIMS solution will automate Laboratory Services in the areas of electronic case record storage and management, evidence processing, evidence chain of custody, case workload and test sample management, instrumentation integration, evidence inventory, interactive data worksheets, examiner report generation and quality review controls, real-time dashboard performance analytics and ad hoc reporting, resource tracking, and system interoperability.

1.3 Scope of Work

The scope of this requirement covers a new LIMS solution deployments, requirements pilot testing, data migration, training, instrument and system integration, enhanced analytics capabilities, and solution support.

• Combining software platforms into an integrated ‘LIMS Solution’ that meets the requirements specified in this performance work statement.

• Deployment of the Solution in development, test and production environments;

• Utilizing the development environment to configure solution in accordance with pilot requirements;

• Utilizing the test pilot system as a basis for user acceptance testing of required functionality to replace existing LIMS solution;

• Migration of existing LIMS data into test and production environments;

• Integration of laboratory instruments and systems;

• Reporting of workloads and performance-based dashboard analytics;

• Training of Government personnel on the use and administration of the solution; and

• Transiting solution to production environment.

1.4 Type of Contract Contemplated

The Government anticipates the contract will be a Firm Fixed Price.

Other direct costs, such as Travel, will be on a Cost basis.

1.5 Period of Performance

Period of performance is one (1) year base and four (4) one-year options.

Estimated dates:

Base Year: 11/17/2025 – 11/16/2026 Option Year 1: 11/17/2026 – 11/16/2027 Option Year 2: 11/17/2027 – 11/16/2028 Option Year 3: 11/17/2028 – 11/16/2029 Option Year 4: 11/17/2029 – 11/16/2030

The dates are estimated. Award in Fiscal Year 26 is a possibility. Dates will be established at time of award.

1.6 Place of Performance

The primary place of performance shall be at the Contractor location. During deployment stages in person reporting may be required at the National Laboratory Center in Beltsville, Maryland.

In-person and on-site training shall be held at the following Government laboratory facility locations:

• National Laboratory Center, Beltsville, Maryland

• Forensic Science Laboratory – Atlanta, Georgia

• Forensic Crime Gun Intelligence Laboratory – Wichita, Kansas

On-site performance will occur only on days on which government operations are being conducted.

1.7 Applicable Documents Reference in PWS

• ATF Information Technology Governance Manual, Version 1.2,

• ATF Information Technology Service Management Policy, ATF O 7200.2C,

• ATF Electronic and Digital Signature Policy, ATF O 7031.1,

• DOJ Cyber Security Program, Order 0904,

• PGD 15-03 Security of Information and Information Systems,

• ATF Rules of Behavior and Customer Agreement for Computing Devices, ATF H

7250.1,

• Attachment A - LIMS Required and Value Added Features

1.8 Other Federal, Justice, and ATF Guidance

• DOJ, Privacy Act of 1974 https://www.justice.gov/opcl/privacy-act-1974

• Federal Information Processing Standard (FIPS) 199 https://csrc.nist.gov/pubs/fips/199/final

• Federal Information Security Modernization Act (FSIMA) https://csrc.nist.gov/topics/laws-and-regulations/laws/fisma

• NIST Special Publication 800-53 – Security and Privacy Controls for Federal Information Systems and Organizations https://doi.org/10.6028/NIST.SP.800-53r5 or latest version

• NIST Special Publication 800-161 – Supply Chain Risk Management Practice for Federal Information Systems and Organizations https://csrc.nist.gov/pubs/sp/800/161/r1/upd1/final

• OMB/NARA Memorandum (M-19-21), Transition to Electronic Records https://www.archives.gov/files/records-mgmt/policy/m-19-21-transition-to-federal-records.pdf

• Section 508 Compliance, Accessibility Conformance Checklists https://www.hhs.gov/web/section-508/accessibility-checklists/index.html

• ATF Information Technology Governance Manual August 23, 2022 Version 1.2

2.0 Specific Objectives/Tasks

Objective 1 - Laboratory Services Introduction

2.1.1. Kickoff meeting

The Contractor and Government team kickoff meeting shall be held within 5 days after favorable background investigations of Contractor personnel. The meeting will focus on the scope of work, objectives, assumptions and constraints, and deliverables and schedule.

Deliverable 1: Kickoff meeting agenda

Deliverable 2: Kickoff meeting minutes

2.1.2. Project Management Plan Development

The Contractor shall work with the Government PM to deliver a project management plan that includes the project team personnel, organizational structure, and available resources. To include the total number of resources anticipated for supporting the ongoing operations and maintenance of the new LIMS solution in production. The Project Management Plan shall include the listed Objectives and associated tasks with projected start/end dates, responsible person, any task contingencies. The Project Management Plan shall align with the Government PM target completion dates. The Government PM will validate final target completion dates and approve for execution.

https://www.justice.gov/opcl/privacy-act-1974 https://csrc.nist.gov/pubs/fips/199/final https://csrc.nist.gov/topics/laws-and-regulations/laws/fisma https://doi.org/10.6028/NIST.SP.800-53r5 https://csrc.nist.gov/pubs/sp/800/161/r1/upd1/final https://www.archives.gov/files/records-mgmt/policy/m-19-21-transition-to-federal-records.pdf https://www.archives.gov/files/records-mgmt/policy/m-19-21-transition-to-federal-records.pdf https://www.hhs.gov/web/section-508/accessibility-checklists/index.html

Deliverable 3: Vendor Project Management Plan

2.1.3. Project Schedule Development

The Contractor shall deliver a project schedule with a work break down structure.

The tasks shall be broken down based off the listed objectives and tasks with assigned responsible personnel. Once the project schedule has been agreed upon by the Contractor PM and Government PM it will be incorporated into the overall project schedule. The schedule will be baselined, and the Contractor shall provide updates to the tasks under their responsibility per direction of the Government

PM.

Deliverable 4: Vendor Project Schedule

2.1.4. Establish Support Teams

The Contractor PM and Government PM will establish the support teams and provide contact information, work hours, and backups for key personnel to support the following Objectives and tasks.

Deliverable 5: Vendor Support Team and Backup Contact Information

2.1.5. Establish Hardware/Software Expectations

The Contractor PM will provide the Government PM with necessary hardware and software requirements necessary to fulfill the following Objectives.

Deliverable 6: Vendor Hardware and Software Requirements

Objective 2 - Laboratory Services Pilot Requirements Review

2.1.6. Validate pilot requirements

The Contractor shall collaborate with the Government support team to ensure full understanding of the pilot requirements. The Contractor will have the capabilities for testing, delivering and supporting the required functionality.

2.1.7. Develop pilot requirements validation checklist

The Contractor shall develop a validation checklist to ensure that all pilot requirements have been deployed and tested to function as expected. This checklist will support the Contractor’s validation efforts when deploying to the various environments as defined in the following Objectives.

Deliverable 7: Vendor Pilot Requirements Validation Checklist

Objective 3 - Deploy Development Environment

2.1.8. Deploy solution in development environment

The Contractor with the established support team will deploy the LIMS solution on the development environment.

The development environment will become the baseline deployed to the test environment for pilot testing and training purposes.

The Government Technical Lead will document the deployment of the LIMS solution into the development environment to include all system configuration necessary for deployment on the Government platform. The deployment documentation will be provided to the Government Contractor engineering team providing instructional guidance for a LIMS deployment onto test and production environments.

2.1.9. Implement Laboratory Services pilot requirements

The Contractor will deploy the solution components and configuration settings necessary to fulfill the pilot testing requirements.

2.1.10. Validate pilot requirements with validation checklist The Contractor will utilize the checklist to ensure the development environment supports all defined requirements.

2.1.11. Verify reporting and analytics functionality

The Contractor will work with the Government PM to ensure solution reporting and dashboard analytics supports queries from management and personnel. The visual dashboards should increase user awareness for discipline workload, case load based on priorities and include interactive data linking to visual graph depictions.

Objective 4 – Data Migration Planning

2.1.12. Develop Data Migration Plan

The Contractor will work closely with the Government support teams to establish a migration plan. This plan will include, but is not limited to, time necessary to acclimate with existing LIMS data structure, identify existing database tables/fields which require migration, define database tables/fields which are subject to on-going updates (i.e., Field office names, addresses, FPC changes, FireTOSS data feeds), identify and establish an ongoing upgrade strategy, identify and develop testing elements for ongoing upgrades, and determine data migration method.

The Data Migration Plan must include data migrated from existing LIMS, as well as GOTS FireTOSS system. The two systems from which data will be exported shall be treated as two separate sources for import into the new solution.

Deliverable 8: Vendor Data Migration Plan

2.1.13. Develop Data Migration Schedule

The Contractor will develop the data migration schedule based off the data and volume required to be retained. Once the project schedule has been agreed upon by the Contractor PM and Government PM it will be incorporated into the overall project schedule. The schedule will be baselined, and the Contractor shall provide updates to the tasks under their responsibility per direction of the Government

PM.

Deliverable 9: Vendor Data Migration Schedule

2.1.14. Develop Data Migration Mapping

The Contractor will work closely with the Government support teams to establish a data migration mapping. This map will detail what data elements are necessary for capturing in the new LIMS solution. The location where the data will be extracted from and where the data will be imported to are critical elements of this map.

Deliverable 10: Vendor Data Migration Mapping

2.1.15. Deliver Entity Relationship Diagram (ERD)

The Contractor shall deliver the database Entity Relationship Diagram which depicts the LIMS solutions database tables, field structures, and data joins. The ERD visualizes the relationships between items in a database and how they relate to each other. The ERD is an important tool to support database problem-solving, security and management, data migration efforts, and establishes a solid understanding of the underlying data structure for ad hoc reporting and dashboard design purposes.

Deliverable 11: Vendor Entity Relationship Diagram (ERD)

Objective 5 – Deploy Test Environment

2.1.16. Validate with pilot requirements checklist

The Contractor will utilize the checklist to ensure the test environment accurately represents the solution and supports all defined requirements. The test environment will become the baseline for pilot testing and user training purposes.

Ensure complete compliance with Section 508.

Deliverable 12: Complete and submit Section 508 Compliance Checklist

Objective 6 – Pilot User Training

2.1.17. Establish pilot user training plan

The Contractor shall reference the pilot requirements validation checklist to ensure all required functionality is covered in the pilot user training session. This will further ensure the testing participants fully understand the functional operations and how to execute commands within the new environment. The training plan will include any deliverables necessary to assist the users through the pilot testing process, such as quick reference guides on the application interface. The training will be hosted onsite at the National Laboratory Center and should also include virtual participant options.

Deliverable 13: Vendor Pilot User Training Plan

2.1.18. Develop Pilot User Training Schedule

The Contractor will develop the pilot user training schedule based on the pilot requirements checklist. Once the pilot training schedule has been agreed upon by the Contractor PM and Government PM it will be incorporated into the overall project schedule. The schedule will be baselined, and the Contractor shall provide updates to the tasks under their responsibility per direction of the Government

PM.

Deliverable 14: Vendor Pilot User Training Schedule

2.1.19. Execute Government pilot user group training

The Contractor PM and Government PM will work together to ensure all LIMS users involved with the pilot testing have been fully trained.

Objective 7 – Pilot Assessment

2.1.20. Execute Government pilot user testing

The Government PM will execute the pilot user group testing phase. The support team will ensure the pilot testers have access to resources for questions and problem solving where needed.

2.1.21. Review user group pilot testing results

The Government PM will communicate pilot testing results. Any testing result deficiencies will be discussed between the Contractor PM and Government PM to determine resolution and establish a plan of action. The test plan acceptance criteria are defined by the pilot requirements.

Deliverable 15: Pilot Testing Results with Plan of Action

2.1.22. Establish pilot action plan schedule

In the event the pilot testing results generate an action plan, the Contractor will develop the action plan schedule. Once the action plan schedule has been agreed upon by the Contractor PM and Government PM it will be incorporated into the overall project schedule. The schedule will be baselined, and the Contractor shall provide updates to the tasks under their responsibility per direction of the Government PM. This schedule will include user group pilot retesting and training if necessary.

Deliverable 16: Pilot Testing Plan of Action Schedule

Objective 8 – All-Hands Training Sessions

2.1.23. Establish All-Hands Training Plan - Curriculum and Material

The Contractor PM and Government PM will work together to ensure all the solution elements are captured in the training syllabus. The training sessions shall be focused on the attendee’s roles or permissions. The training shall include written and practical exercises.

A separate training session should be designed for management reporting and analytics. Any instrument or systems integration shall be handled in a separate training session(s).

Deliverable 17: All-Hands Training Curriculum and Material

2.1.24. Establish training schedules to include make-up sessions The Contractor will develop the training schedule based off the training curriculum. Once the training schedule has been agreed upon by the Contractor PM and Government PM it will be incorporated into the overall project schedule.

The schedule will be baselined, and the Contractor shall provide updates to the tasks under their responsibility per direction of the Government PM.

Deliverable 18: All-Hands Training Schedule

2.1.25. Establish Train the Trainer - Curriculum and Material The Contractor PM and Government PM will work together to ensure all the solution elements are captured in the training syllabus. The training sessions shall be focused on the attendee’s roles or permissions. The training shall include written and practical exercises.

Deliverable 19: Train the Trainer Curriculum and Material

2.1.26. Establish training schedules to include make-up sessions The Contractor will develop the training schedule based off the training curriculum. Once the training schedule has been agreed upon by the Contractor PM and Government PM it will be incorporated into the overall project schedule.

The schedule will be baselined, and the Contractor shall provide updates to the tasks under their responsibility per direction of the Government PM.

Deliverable 20: Train the Trainer Training Schedule

2.1.27. Execute training sessions

The Contractor PM and Government PM will work together to execute the All- Hands training sessions. The support team will ensure the attendees have access to resources for questions and problem solving where needed.

Objective 9 – Deploy Production Environment

2.1.28. Validate with pilot requirements checklist

The Contractor will utilize the checklist to ensure the production environment accurately represents the solution and supports all defined requirements including any changes from the pilot testing action plan, if appliable.

2.1.29. Pre-production security scans

The Contractor PM will work closely with the Government PM to ensure compliance with all pre-production security scans and remediate any identified vulnerabilities or non-conformances without delay to system production to achieve Authorization to Operate.

Deliverable 21: Security Scan Remediation Action Plan & Schedule, if appliable

Objective 10 – Execute Data Migration (Test, Production)

2.1.30. Execute data migration

The support teams will work closely to ensure the data migration is executed in accordance with the data migration schedule. Any deviations from the schedule must be approved by the Government PM to prevent any extended stop work occurrences.

2.1.31. Establish validation testing

The Contractor PM, Government PM and support teams will work closely to ensure successful data migration validation testing. Any data inconsistencies must be addressed and tested before production goes online.

Objective 11 – Enhanced Analytics

2.1.32. Validation of analytics and reporting

After the successful deployment and data migration of the new LIMS, the system shall have the capabilities to generate standard management workload, electronic case record, and laboratory statistics and reporting. The LIMS will have the capability to present the data in an organized, clear and concise manner for analysis and decision making.

Objective 12 – Instrument Integration

2.1.33. Execute instrument migration at FSL-W and FRL

The support teams will work closely to ensure the instrument migration is executed in accordance with a migration schedule for the FSL-W/FRL located at 6000 Ammendale Road, Beltsville, MD. Any deviations from the schedule must be approved by the Government PM to prevent any extended stop work occurrences. Any data inconsistencies must be addressed and tested before production goes online.

2.1.34. Execute instrument migration at FSL-A

The support teams will work closely to ensure the instrument migration is executed in accordance with a migration schedule for the FSL-A located at 2600 Century Parkway, Atlanta, GA 30345. Any deviations from the schedule must be approved by the Government PM to prevent any extended stop work occurrences.

2.1.35 Execute instrument migration at Wichita

The support teams will work closely to ensure the instrument migration is executed in accordance with a migration schedule for the Wichita located at Forensic Crime Gun Intelligence Laboratory, 4504 E 18th ST N, Wichita, KS 67208. Any deviations from the schedule must be approved by the Government PM to prevent any extended stop work occurrences.

Objective 13 – Features

2.1.36. Required Features

All required features listed in Attachment A must be currently available and provided.

2.1.37 Value added Features

As many currently available value added features listed in Attachment A shall be provided.

3.0 Required Additions

The contractor shall provide the ability to add or remove, at no additional cost, the following:

• Annual base license

• User Licenses for approximately 200 employees

• Customized Reports or Dashboards

• Interactive Examiner Worksheets

• Training Courses

• Application Integration/API Development

• Laboratory Instrument Integration

• Any Value Added Feature listed in Attachment A as they become available.

4.0 Key Personnel

The contractor shall provide capable team(s) with knowledge, skill, and ability to implement the LIMS solution and will be responsible for deployment team configuration and organization.

Key personnel may not be removed or substituted on this project without the written consent of the Contracting Officer. Should the key personnel vacate the position, the contractor shall notify the CO immediately and provide a fully trained, qualified replacement within two (2) business days. The notification shall include an explanation of the circumstances necessitating the replacement, a complete resume of the proposed replacement, and any other information required by the CO to enable the Government to verify the proposed replacement meets or exceeds the mandatory qualification. The CO shall approve any changes in key personnel, whether temporary or permanent. No diversion shall be made of key personnel to other programs without the advanced written consent of the CO.

Key Personnel include:

Project Manager – The Project Manager (PM) shall have relevant federal or industry experience in managing a successful LIMS deployment with an existing LIMS data migration. The PM shall work with the Government Project Manager (GPM), the Government Contracting Officer (CO), and other Government and contractor personnel to ensure that the Government PM approved LIMS implementation schedule is followed and maintained. The PM is responsible for ensuring that the Performance Work Statement (PWS) requirements are met and all contractor work performed under the PWS is compliant, timely, and within budget.

Technical Product Specialist – The Technical Product Specialist (TPS) will work closely with the Government support teams to gain a thorough understanding and obtain background knowledge pertaining to Laboratory Services operations. TPS will manage the technical LIMS solution setup, integration, and oversee the pilot testing phase.

5.0 Contractor Quality Assurance

The Government will follow the QASP, Attachment 2, to verify the completion and quality of each PWS Objective task. The Contractor may propose additional performance measures and monitoring methods.

6.0 Deliverables

The Contractor shall provide all applicable deliverables in a Microsoft Office 365 Apps for Enterprise or newer compatible format via email, and/or uploaded to a specific site as requested by the Contracting Officer’s Representative (COR).

Deliverable No.

Deliverable Title/Description Deliverable Due Date

1 & 2 Kickoff meeting Within 5 business days after security clearance approvals of all participating contract employees are completed.

- Kickoff meeting agenda within 5 days after award.

- Kickoff meeting minutes following completion of Kickoff meeting within 1 day.

3 Vendor Project Management Plan

Objectives with tasks detailed, responsible party assigned, and task dependencies and contingencies.

Within 10 business days after Kickoff meeting.

4 Vendor Project Schedule

Listing of Objectives with tasks containing start/end target dates. Project schedule show reflect final production deployment date.

Within 10 business days after kickoff meeting. Updated schedule as needed or at ATF’s request.

5 Vendor Support Team and Backup Contact Information

Listing of vendor support personnel names, titles, contact phone numbers, email address, and backup personnel.

Within 5 business days after kickoff meeting.

Deliverable No.

Deliverable Title/Description Deliverable Due Date

6 Vendor Hardware/Software Requirements

Listing of hardware and software requirements for new LIMS.

Within 10 business days after kickoff meeting.

7 Vendor Pilot Requirements Validation Checklist

As determined by ATF and within 3 business days of request.

8 Vendor Data Migration Plan

Listing of tasks associated with the data migration from existing LIMS and FireTOSS systems, points of contact, and task dependencies and contingencies.

As determined by ATF and within 3 business days of request.

9 Vendor Data Migration Schedule

Listing of tasks for data migration with completion start/end dates.

10 Vendor Data Migration Mapping

New LIMS interface with database tables, fields defined with existing LIMS and FireTOSS data elements defined.

11 Vendor Entity Relationship Diagram

(ERD)

New LIMS database table and field structure.

12 Section 508 Compliance Checklist As determined by ATF and within 3

13 Vendor Pilot User Training Plan

Training geared for pilot testers. Plan should include syllabus and training material requirements.

14 Vendor Pilot User Training Schedule

Training dates/times for pilot tester training.

Deliverable Title/Description Deliverable Due Date

15 Pilot Testing Results Action Plan, if applicable

Plan should identify pilot testing results, modifications, resolution, deployment timeframe.

16 Pilot Testing Plan of Action Schedule

Generated in accordance with the Project Plan Schedule, includes start/end timeframes and resolution deployment timeframe.

17 All-Hands Training Curriculum and Material

Listing of all user training curriculum and training material.

18 All-Hands Training Schedule

Listing of all user training groups, training start/end dates, make-up training start/end dates.

19 Train the Trainer Curriculum and Material

Listing of train the trainer curriculum and training material.

20 Train the Trainer Schedule

Listing of all train the trainer groups, training start/end dates, make-up training start/end dates.

21 Security Scan Remediation Action Plan & Schedule, if applicable

List of areas where Contractor security compliance or vulnerabilities are identified, define resolution, identify responsible personnel, provide start/end dates.

As determined by ATF and within 3 business days of request.

Remediation shall be completed in a manner that will not cause delay with the production deployment schedule.

Deliverable Title/Description Deliverable Due Date

22 LIMS software, documentation, training materials, and all supported written project materials are considered Government property.

23 LIMS licensing package As determined by ATF and within 3

24 Laboratory Instrument Integration As determined by ATF and within base year

7.0 Acceptance

Supplies or services delivered under this contract shall be inspected and accepted by the Contracting Officer’s Representative (COR). The Contractor shall only tender for acceptance those items that conform to the requirements of this contract. 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 bases for acceptance shall be compliance with the Requirements/objectives/constraints set forth in the contract, and other terms and conditions of the contract. Deliverable items rejected shall be corrected in accordance with the 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.

Rejection Procedures. If the COR rejects any deliverable, that rejected deliverable will be handled in the following manner:

After notification that the deliverable did not meet the acceptance criteria, the Contractor shall resubmit an updated/corrected version within five (5) business days after receipt of Government comments.

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 might consider the Contractor as having deficient performance with respect to the subject task/subtask.

Any rework of 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.

8.0 Access to Records, Data and Facilities

The Contractor shall permit the CO and/or designed representative(s) access at any reasonable time to all records, data and facilities used in performance for the services covered in this PWS.

9.0 Meetings

Meetings will be conducted at either the National Laboratory Center location at 6000 Ammendale Road, Beltsville, MD 20705, or through an alternative method of communication (such as a teleconferencing), as approved by the contracting officer and Government PM.

9.0.1 Post-Award Kickoff Meeting

The government will conduct a post-award kickoff meeting within 5 business days of contract award if virtual meeting method is agreed upon. For an in-person meeting after security clearance approvals of all participating contract employees are completed.

9.0.2 Intermittent Project Status Reviews

At the sole discretion of the government, intermittent project status reviews may be conducted on an informal basis (by telephone or teleconference) or in person at National Laboratory Center with agreed upon schedule as approved by the Contracting Officer, COR, or Government PM.

9.0.3 Monthly Project Status Reviews

Monthly status meetings will be conducted on the first Monday of each month.

The Contractor is responsible for reporting the previous month’s activities (including any risks, issues, or concerns, and actual or recommended actions for mitigation), and projected activities for the following month.

10.0 Required Travel and Other Direct Costs (ODCs)

The Government anticipates travel to occur during LIMS deployment and LIMS user training sessions.

Although the LIMS server deployment is anticipated to be completed on a virtual server(s) in-person support is necessary to ensure proper configuration, system setup and system administrator and user training.

End-user training will be held in-person at each laboratory site to include the following:

• National Laboratory Center o 6000 Ammendale Road, Beltsville, MD 20705

• Forensic Science Laboratory – Atlanta o 2600 Century Parkway, Atlanta, GA 30345

• Forensic Crime Gun Intelligence Laboratory o 4504 E 18th ST N, Wichita, KS 67208

The Government anticipates at least twelve (12) visits with duration lasting up to five (5) days per visit. All travel expenses shall be provided by the Contractor.

11.0 Special Instructions

The Contractor PM shall identify any functionality that cannot be supported with the COTS product(s) and requires customized coding. All custom code created to develop, test, deploy, and migrate data, or for any other use will be thoroughly documented and delivered as both source and object code. Documentation shall include an estimate of the percentage of capability that will require custom coding, timeline to develop and test, and any costs associated.

12.0 Government Furnished Property/Equipment/Information

The Government anticipates the new LIMS solution to be deployed on Government leased virtual servers housed in the AWS GovCloud and managed by Government and Government Contractor personnel. The hardware will be defined by the Contractor hardware specifications.

13.0 Security

13.1 System

The LIMS solution shall be compliant with all relevant security controls outlined in the Federal Information Processing Standard (FIPS) and the Federal Information Security Management Act (FISMA) to include, but not limited to, the ability of the federal Government to perform a security certification and accreditation (C&A) process to obtain an authorization to operate that will be signed by the federal principal without delay to system deployment.

13.2 Personnel

DOJ/ATF has determined that all Contractor(s)/Subcontractor(s) performing work under the Laboratory Services Laboratory Information Management System (LIMS) Modernization contract will have access to sensitive but unclassified information, which requires DOJ/ATF Suitability Clearance 5C (Moderate Risk) position of public trust adjudication.

All Contractor employees must have clearances with background investigations conducted by ATF. The clearance process is anticipated to take a minimum of two (2) months and could take up to six (6) months or longer. Contractors are reminded that ATF is a law enforcement agency when selecting personnel for the project. All Contractor personnel must be U.S. born or naturalized citizens.

Standard non-disclosure statements shall be provided as required for personnel who may have access to Government data in the course of their duties.

14.0 Glossary of Abbreviations and Acronyms

Abbreviation/Acronym Description ANAB ANSI National Accreditation Board API Applications programmable interfaces ASTM American Society for Testing and Materials ATF Bureau of Alcohol, Tobacco, Firearms and Explosives ATO Authorization to Operate CLIN Contract line identification number CO Contracting Officer CODIS Combined DNA Index System Contractor PM Contractor Project Manager COR Contracting Officer’s Representative COTS Commercial Off-the-Shelf CPM Contractor Project Manager DOJ Department of Justice DNA Polymer composed of chains ERD Entity Relationship Diagram FAR Federal Acquisition Regulation FCGIL Forensic Crime Gun Intelligence Laboratory FedRAMP The Federal Risk and Authorization Management Program managed by the FedRAMP Program Management Office.

FIPS Federal Information Processing Standards FireTOSS Federal developed GOTS system developed for converting, storing, and managing instrument data.

FISMA Federal Information Security Management Act FPC Federal Purchasing Code FRL Fire Research Laboratory FSLs Forensic Science Laboratories FSL-A Forensic Science Laboratory - Atlanta FSL-W Forensic Science Laboratory - Washington GOTS Government Off-the-Shelf Government PM Government Project Manager IED Improvised explosive devices ISO International Organization of Standardization ISO/IEC 17025 International standard for testing and calibration laboratories Item Item is a test sample (a.k.a. exhibit) LIMS Laboratory Information Management System Managed Services On-premise solutions that require on-site technical staff to manage and maintain the software.

NFPA The National Fire Protection Association NGI Next Generation Identification OST Office of Science and Technology PM Project Manager POC Point of contact POP Period of performance

PWS Performance Work Statement SaaS Software as a Service is a cloud-based software delivery model where customers pay for software products on a subscription bases.

SDA Software Defined Architecture Section 508 Section 508 of the Rehab Act Electronic and Information

Technology Accessibility for Persons with Disabilities

14.0 Glossary of Abbreviations and Acronyms