2.2.1 70B06C25R00000019 DRAFT Attachment 2- Statement of Work.pdf

REQUEST FOR PROPOSALS (RFP)

70B06C25R00000019

Attachment 2

STATEMENT OF WORK

For

Forensic Laboratory Information Management System

(LIMS)

January 31, 2025

Prepared by

U.S. Customs and Border Protection

Laboratories and Scientific Services

Version: V 1.1.6 DRAFT

Statement of Work (SOW)

Forensic Laboratory Information Management System (LIMS)

1.0 BACKGROUND:

The Department of Homeland Security (DHS), U. S. Customs and Border Protection

(CBP), Laboratories and Scientific Services (LSS) is the scientific and forensic branch of

CBP that represents one of the largest and most diverse Government laboratories in the world. LSS’s mission is to provide rapid, accurate, and reliable forensic, scientific and testing services to protect the homeland in six functional areas to include: controlled substances, digital forensics, friction ridge examinations, trade, reachback (narcotics and radiation/nuclear), and palynology. The laboratory system is accredited by the American

National Standards Institute (ANSI) American National Accreditation Board (ANAB) and complies with the International Organization for Standardization / International

Electrotechnical Commission (ISO/IEC) 17025 standards in the forensic and trade disciplines.

To fulfill the LSS mission with ultimate operational efficiency and compliance, LSS is seeking to modernize its current LIMS system with a commercial off-the-shelf (COTS)

Forensic Laboratory Information Management System (LIMS) geared towards a forensic laboratory. This COTS system shall be capable of handling evidence entry and routing, chain of custody tracking, case creation, case/sample assignments, case data input, image storage, reporting, and tracking and monitoring current and future work loads of LSS’s regional laboratories, Forward Operating Labs (FOLs), Joint Forensic Centers, (JFC’s), Reachback Centers and Mobile Operations, as well as any additional functional areas that may be added at a later date.

2.0 PURPOSE:

This document defines the system requirements for a COTS Forensic LIMS with the goal of soliciting a response from contractors offering Forensic LIMS products. The COTS

Forensic LIMS shall have the ability for customization and configuration initially performed by the contractor and guided by the Government who will eventually perform these functions after receiving the proper training. Proposed systems shall support evidence chain of custody and have been used in and undergone legal scrutiny in U.S. courts of law.

To ensure correct configuration, the contractor shall baseline/map the solution against LSS processes listed in Appendix 1 and 2 to assist with initial trade off analysis with the goal of reducing configuration and using as much of the COTS solution as possible.

3.0 GENERAL REQUIREMENTS:

a. Licenses: LSS is seeking a system with for 400 concurrent users and 30 administrative license, and additional test and training users.

b. Data Integrity: The system shall authenticate data integrity by a secure audit trail. Audit trail functionality captures laboratory activities with a date and time stamp along with other details, such as username.

c. Configurable: Functionality created with tools or software through direct contractor interaction for workflows in each LSS functional area (controlled substances, digital

DRAFT

forensics, friction ridge, trade, reachback (narcotics and radiation/nuclear), and palynology.

d. Customizable: Workflow functionality that is created using built-in tools provided by the contractor. Workflows can be edited when necessary, initially by the contractor, with guidance from the Government who will eventually perform this function after receiving the proper training. These workflows will make processing evidence consistent and accurate as it proceeds through the various stages of laboratory analysis.

e. COTS mapping: the Contractor will work with Government to perform a mapping of the COTS offering to a specification to be designed in agreement with the Government

“Analytical Summary” documents contained in Annex 1

f. Chain of Custody: Ability to support electronic and physical chain-of-custody that uses bar-codes and maintains chain of custody records that document the transfer of each item of evidence from collection to laboratory submission to final disposition. The record includes the person or location receiving the evidence and any subsequent transfers. Subdivided evidence is also tracked through a documented chain of custody record. Secure and auditable date and time stamps for transactions are essential. System shall demonstrate support of electronic chain-of-custody at the Federal, state, and local levels as well in courts of law. Demonstration shall show previous/current system utilization in a forensic laboratory and actual use in legal proceedings in U.S. Courts of

Law at the Federal or state or local level.

g. Search and Query Functions: Enables records to be searchable and export attributes into reports. It provides ad hoc queries for all entered data and creates exportable reports for entered data. The system can also calculate metrics.

h. Process Management: Ability to track a sample from intake to report issuance and beyond.

i. Case Management: Ability to assign and track casework

j. Resource Management: Ability to manage evidence, and/or samples, equipment, and supplies in inventory. Expiration dates and quantity of supplies need to be tracked. The system shall notify assigned users when actions are necessary.

k. Report Generation: Ability to consistently generate credible, dependable, and complete reports regardless of whether the end goal is trend analysis, prosecution, or research.

Shall be flexible enough to allow customization when needed. Provides an integrated user-friendly tool for data visualization and to create and display multiple internal dashboards. End-users can configure internal dashboards to display user-defined metrics (e.g., unit pending, priority assignments, due dates, turnaround time, backlogs).

Additionally, the Forensic LIMS provides the ability for the Forensic LIMS administrator or designee to assign permissions to create, modify, save, and access internal dashboards to individuals or groups. Internal and web-based dashboards should display real-time metrics when accessed.

1. Use business intelligence and statistical software such as Databricks, Cognos, Salesforce, Tableau, PowerBI, Microsoft Excel, R, and Python to analyze data on an ad hoc basis for data analytics purposes.

l. Electronic Routing: Ability to electronically route documents with automatic notifications to assigned users

m. Electronic Signatures: Ability to sign electronically with automatic notifications to assigned users

n. Barcode/QR RFID System: The system shall meet the following to includes all hardware (scanners and printers and any other hardware needed to utilize the barcoding capability). Shall have the ability to generate barcode labels and print for samples and/or for the containers and aliquots as they are pre-logged or received. Barcode label formats must be configurable and flexible to include any additional information or integration with an evidence management system to integrate the tag information into

Solution for the following:

• Print barcode labels for the overall case, test request and/or for the items

/containers as they are pre-logged.

• Allow users to configure barcode label formats and be flexible to include additional information.

• Generate unique and random barcode labels

• Register/link the barcodes to any test request and/or items/containers

• Restrict the same barcode to be registered/linked/used for more than one item

• Conform with or be eligible for insertion in the DHS and CBP Technology

Reference Model (TRM).

1. Four hundred (400) compatible/integrated handheld barcode scanners

2. Seventy (70) compatible/integrated barcode printers

a. Include High-capacity barcode labels for each printer

3. Integrated with the Forensic LIMS system and evidence/sample workflow/chain of custody and inventory management.

4. Label information in human readable, 2D barcode, QR code, and radiofrequency identification format.

5. Supports chain of custody and accreditation (Item 3.0 f.).

6. Shall support industry standard barcodes such as ISO 15415 (2D Barcodes) and ISO

15416 (1D Barcodes) or newer, network and secure wireless protocols. Capability shall also include read/write function for barcodes on materials commonly used within CBP.

7. System shall have the capability to associate user login information to when a barcode is scanned.

8. Functionalities include user barcode for evidence chain of custody and transfer, processing the chain of custody transfer, physical custody location barcode for a chain of custody and transfer, and other uses such as lot numbers, quality assurance designation, and instrument calibrations.

9. Compatibility with non-proprietary industry standard 1D and 2D barcode scanning or newer, and current barcode scanning and barcode printing equipment, such as

Zebra barcode printers, barcode scanners, and various document scanners. The

Forensic LIMS shall allow barcode scanners to read any side and type (e.g., 1D &

2D) of the barcode without changing set-up parameters, allow users to create 1D and 2D barcodes of varied sizes and to print those varied sizes without changing set-up parameters, support already established custody locations and corresponding

1D/2D barcodes, allow for external barcodes to be scanned for data entry, such as commercial delivery tracking numbers, and provide the ability for the expansion of future technologies and workflows.

o. Accreditation Compliance: Supports requirements for forensic laboratory accreditation compliance of the following bodies:

1. ANAB or another Accreditation Body

2. ISO/IEC 17025

p. Case Number Customization: support for alphanumeric case numbers generated based upon fiscal year, LSS location, sample type (s), and sequential sample number.

q. Training and Support: Forensic LIMS contractor shall provide training curriculum and training materials for all functional areas and user/administrator levels. Forensic LIMS contractor shall conduct initial training for all functional areas, in accordance with their proposed schedule, once approved by the Government.

r. Data Integration: Forensic LIMS contractor shall integrate current LSS LIMS data into new Forensic LIMS system.

s. High availability: Shall have 99.9% uptime to include software updates and upgrade outages.

t. Privacy and Security

1. The Forensic LIMS system shall support industry IT Security standards.

2. The Forensic LIMS system shall comply with CBP and DHS security policies and associated guidance to include DHS Sensitive System Policy Directive 4300A and

NIST 800-53 Rev 4 (or any future versions) Security and Privacy Controls for

Federal Information Systems and Organizations.

3. The Forensic LIMS system shall comply with DHS Management Directive (MD)

047-01, Privacy Policy and Compliance, and accompanying instructions.

4. The Forensic LIMS system shall enable role-based access controls.

5. The Forensic LIMS system shall support zero trust authentication / Personal

Identity Verification access.

6. The Forensic LIMS system shall contain a time-stamped audit log recording all changes to a record as well as all users who have accessed the system.

7. The Forensic LIMS system shall include tiers of access and compartmentalization based on operational need.

u. IT Compliance

1. The Forensic LIMS system shall be capable of being Federal Risk and

Authorization Management Program (FedRamp) certified.

2. The Forensic LIMS system shall adhere to industry open IT standards.

3. The Forensic LIMS system shall meet specifications outlined by Section 508 compliance requirements.

4. The Forensic LIMS system shall support a Software as a Service (SaaS) cloud-based application model including all underlying infrastructure, middleware, application software, and application data storage.

v. Data Migration: The Contractor shall migrate data from the existing LIM system after the new system is installed and operating. Data migration, at a minimum, includes activities such as:

• Identifying and mapping data

• Identifying any necessary data conversions

• Validating the data mapping

• Validating data conversions

• Executing the migration and conversions

• Testing the migration and conversions

• Correcting data migration and conversion issues

• Validating the migrated and/or converted data

w. Integration Support and Coordination: the contractor shall provide support for design, development, and engineering of interface solutions (such as Application Programming

Interfaces) and shall promote the use of decoupled and reusable methods for integrating with external and internal data sources and systems, as needed. To include:

1. Develop and maintain integration solutions, for example using Application

Programming Interfaces (APIs) where feasible, and use decoupled and reusable methods for integrating with external and internal data sources and systems while avoiding custom integration efforts where possible.

2. Develop and maintain integration documentation to include, but not limited to

Interface Control Documents (ICDs) and design documentation that ensures clear understanding of integration design mapped to business and system processes.

4.0 DELIVERABLES

All written contract deliverables require COR approval and formal acceptance by the COR.

The Government will have up to ten (10) business days after receipt of a deliverable to accept or reject any product. If the COR rejects a deliverable, the Contractor will be provided specific written comments detailing the basis for the rejection and recommended corrective action. The Contractor shall have up to ten (10) calendar days to address each specific written comment by either incorporating the requested Government change or providing an explanation of why the Government change is not being incorporated. The

Government will have an additional five (5) calendar days to review and provide a final decision regarding acceptance or rejection of the deliverable.

a. Project Management Plan

Provide project management support required to carry out the tasks and comply with this Statement of Work (SOW). Contractor progress against tasks shall be assessed in informal status daily discussions (where discussions could include phone conversations and/or email exchange) between the Contractor and the Contracting Officer’s

Representative (COR). The Contractor shall support the weekly status meetings to be chaired by the project manager. Additionally, the Contractor shall prepare and submit monthly status reports to the COR. As a minimum, the report shall contain the following:

• Activity summary, including each item in Section 3.0

• Analysis/mapping of the COTS system against LSS current processes to develop an optimize system with minimal customization o Change control report detailing current LSS process to new process

• Major milestones.

• Open action items.

• Staffing, to include roles, responsibilities, and allocation to the project (% of their overall work to this project)

• Project risks and responses.

• Modification progress to schedule performance.

• Major activities planned for the succeeding month; and

• Status of configuration changes including due dates for mockups and implementation, as well as an updated accounting record of configuration changes.

Tasks that are late shall be listed on monthly status reports with an explanation of why they are late, and a discussion of remediation actions planned to alleviate the schedule delay. This report shall be prepared in a narrative format suitable for reproduction.

Electronic submittal may be made via email to the COR and the Contracting Officer.

The monthly status reports shall be reviewed during the monthly meeting with the

Contractor. These status reports shall include unforeseen issues that impact the:

• Critical path.

• Risks.

• Known issues; and/or

• The completion date of the project, which shall also be reported to the COR via email within four (4) business hours of their discovery.

b. Quality Control Plan

The Quality Control (QC) Plan (QCP) is to define the quality requirements for the

Forensic LIMS System program to implement and maintain high-quality services, work products/deliverables, and meet or exceed the standards outlined in the SOW while ensuring excellent customer service. This document describes how the team plans to implement proven quality control and quality assurance (QA) methodologies across all

Forensic LIMS Systems tasks, utilizing methodologies that build on Continual Service

Improvement (CSI) from the start of the program to ensure an excellent customer experience throughout the life of the program. The QCP is a living document and will be managed through the same CSI approach as the services provided to CBP.

c. Transition-In Plan

The Contractor shall submit a transition-in plan with their proposal that is in sufficient detail to identify all transition-in actions, documentation, and staffing proposed to prepare the workforce to assume full operations on the first operational performance day of contract performance. During the 10-calendar day period prior to the start of the baseline Contract, the proposed Contractor’s personnel, as identified in the proposal, shall be on-site at each location to observe all operations pertinent to the contract requirements to include office functions, procedures, and operations, and any other operations as deemed necessary by the Contractor, that will enable Contractor personnel to become both knowledgeable in, and familiar with, their assigned areas of responsibility.

During the Transition-In Period, the Contractor shall train their personnel to perform completely all related contract requirements before the full operational start date. All deficiencies that are identified by the COR shall be completed in an urgent manner within 5 days of the prior to full operational start date.

d. Transition Plan – Outgoing Transition

The Contractor shall submit a transition-out plan with their proposal that is in sufficient detail to identify all transition-out actions, documentation, and staffing proposed to successfully execute the transition-out process. During the 30-calendar day period immediately prior to the end of the final baseline Contract (if the Contractor is not awarded the subsequent contract for this service), the Contractor shall permit the successor Contractor and the successor Contractor’s employees to observe and become familiar with any and all operations under the contract. The Contractor shall prepare and submit to the COR any changes to the transition-out plan submitted as part of the original proposal. The Contractor shall not defer any identified deficiencies for the purpose of transferring responsibility to the successor Contractor.

The Contractor shall fully cooperate with the successor Contractor and the Government so as not to interfere with their work or duties.

The Contractor shall ensure that Government furnished equipment and/or files are in a condition equal to or better than when the Contractor began this contract.

45-calendar days prior to the end of the final baseline Contract, the COR and the

Contractor shall identify all deficiencies to files and Government furnished equipment that need to be corrected before the expiration of this Contract. A Close-out Report will jointly be generated of all deficiencies noted. The Contractor shall correct all of the cited deficiencies noted in the Close-out Report before the expiration of this contract. Final payment to the Contractor may be withheld until all cited deficiencies are corrected.

e. Implementation Plan

The purpose of the Implementation Plan is to define the high-level tasks required across all phases of the Forensic LIMS System’s implementation, including but not limited to installation, customization, integration, testing, certification, transition to production, and ongoing support. This document describes how the team plans to implement proven information technology methodologies across all tasks to successfully deliver the

Forensic LIMS Systems in an acceptable time period. The implementation plan includes a Microsoft Project Plan detailing the tasks and milestones needed to deliver the

Forensic LIMS Systems to production, including their projected dates and their dependencies, whether internal or external to the program. Tasks will include the

Contractor’s delivery of all needed documentation and artifacts required by the

Government for acquisition, enterprise architecture, systems engineering, systems accreditation, and general oversight as part of implementation on to the CBP-Network.

These tasks will include but not be limited to Security, Accreditation, and Authorization

Artifacts; and Enterprise Architecture artifacts; Technology Reference Model Insertions;

Technical Data Package(s); Systems Engineering Lifecycle (SELC) documentation;

Project Management documentation; and Configuration/Change Management for all system changes including installation, upgrades, patches, security updates and ongoing product improvement requests.

The MS Project Plan is a living document and will be managed through the length of the

Forensic LIMS System Implementation, completing with transition into production.

f. Environments Management Plan

The contractor shall provide an environments management plan on how the contractor will follow and implement best practices for code development, testing, and implementation. The environments management plan will flow in lock step with the implementation plan. At a minimum, it will cover the locations (contractor or

Government sites), purpose/uses, and users for development, testing (and integration), systems acceptance testing and production environments.

g. Monthly Status Report

The Contractor shall submit a monthly status report to the COR by the tenth (10) business day of each month via email. The monthly status report shall address functional accomplishments, issues, unresolved problems, and a plan of action for resolving any problems identified by the Government.

This report shall contain the following information:

• cover letter with the Contractor’s name and address, the contract number, the date of the report, and the period covered by the report.

• significant changes to the Contractor’s organization or method of operation.

• description of significant events occurring during the reporting period.

• status of pending deliverables with expected delivery dates.

• problem areas affecting technical, schedule, or cost elements of the contract, including background, impact, and recommendations· for resolution.

• results related to previously identified problem areas with conclusions and recommendations.

• Listing of all help desk tickets to include date, source, status (open/closed) and time to resolution

• trip reports and significant results.

• Name and telephone number of the preparer of the report.

• Planned accomplishments for the next reporting period; and

• For each task area, the Contractor shall provide the status and expected timeframe for completing the associated tasks.

h. Weekly Meeting with COR

Weekly status meetings shall be conducted via teleconference to discuss the following topics:

• Issues

• Anomalies

• Upgrades, enhancements, and modifications

• Projects (provide status, updates to schedules, milestones)

The Contractor shall submit meeting minutes and all action items to the COR within five

(5) business days of the end of the meeting via email. At a minimum, the Contractor shall provide at least one (1) project manager and one (1) systems engineer to provide administrative and system updates for all weekly meetings. The Government will provide at least one (1) systems administrator and the COR. Additional personnel may be provided on either side based on need.

i. Deliverable Schedule

DELIVERABLE DESCRIPTION DUE DATE

Contract Kick-off meeting minutes

The contractor shall hold an in-person kickoff within 7 days of contract award. Key Personnel and at least 2 corporate representatives will be in attendance with CBP CO, COR and other program leadership to discuss the goals, logistics, funding, and critical expectations for the delivery effort.

Kick-off- Within 15 days of award

Minutes – 3 days after kick-off

Project

Management

Plan

This includes a deliverables schedule. The contractor shall propose a deliverable schedule in their response for any deliverables beyond

Overview via Oral

Presentations those listed below, inclusive of deliverable title, type, delivery date or frequency, acceptance criteria, and description.

Draft- Within 15 days of contract award

Final- Within 15 days after Government review of Draft.

LSS Module Plan The contractor will provide an additional plan specific to the customization, demonstration, review and finalization of the different functional modules. The plan will end with user acceptance of the last module.

Draft due within 15 days of award

Final within 15 days review of Draft

Quality Control

Plan (QCP)

The contractor shall provide a QCP describing how the implement of proven quality control and quality assurance (QA) methodologies will be applied and used across all tasks.

Final- Within 30 days of Government review of Draft

Implementation

Plan

The contractor shall provide an Implementation

Plan defining the high-level tasks required across all phases of the Forensic LIMS System’s implementation, including but not limited to installation, customization, integration, testing, certification, transition to production and ongoing support. The implementation plan will also illustrate how acquisition and systems engineering deliverables provided by the contractor as required for implementation on hardened Federal Government networks will be provided in sufficient time for both OIT and

LSS review before acceptance.

review of Draft

On-going monthly updates before the 10th of Each Month

Transition Plans The contractor shall provide transition plans.

This deliverable shall outline detailed plans on how the Contractor will transition support both at the time of Transition-In and Transition-Out

Transition In Plan is due within 10 working days of contract award.

Transition Out Plan is due no later than 120 calendar days before the end of the Period of Performance.

Environments

Management Plan

The contractor shall provide an environments management plan on how the contractor will follow and implement best practices for code development, testing, and implementation.

review of Draft

Ad Hoc reports, whitepapers, briefings, presentations, and other related artifacts

The contractor shall create and present as required or as identified by the Government.

Government

Required technical documentation and related artifacts

The Contractor shall provide Forensics LIMS documentation and artifacts required by the

Government for acquisition, enterprise architecture, systems engineering, systems accreditation, and general oversight as part of implementation on to the CBP-Network. These tasks will include but not be limited to Security, Accreditation and Authorization Artifacts; and

Enterprise Architecture artifacts; Technology

Reference Model Insertions; Technical Data

Package(s); Systems Engineering Lifecycle

(SELC) documentation; Project Management documentation; and Configuration/Change

Management

As required by

Government implementation, governance and oversight process and as documented by the approved

Implementation Plan.

Monthly Status

Report (MSR)

The Contractor shall submit MSR to the COR by the tenth (10) business day of each month via email. The monthly status report shall address functional accomplishments, financial status of the project (detailing invoices, incurred costs, burn rate (actual and projected) and fund status of all line items), issues, unresolved problems, and a plan of action for resolving any problems identified by the Government.

Monthly, On Or

Before The 10th Of

Each Month

Weekly Meeting The contractor shall host weekly status meetings to be conducted via teleconference to discuss issues, anomalies, upgrades, enhancements, and modifications, project status, updates to schedules, milestones)

Weekly

Contractor Trip

Reports

Contractor shall prepare a consolidated trip report providing a summary of the trip, outcomes, and after actions with due dates.

Trip reports are due to the COR NLT 5 business days after travel.

Training Material Complete documentation for all applications developed and deployed under this contract and provide training materials (user guides, administrator’s guide, job aids, role specific job review guides, Standards of Procedure, video, After approval and 45 days prior to the start of training etc.) that will enable end users to utilize the system. User guides which detail system functions and user actions needed to execute those functions, as well as applicable troubleshooting instructions.

Training Plan Phased schedule that addresses training for all

LSS personnel as part of the implementation, plus train-the-trainer sessions for ongoing support. Phased training will follow in lock step with the phased implementation plan, to ensure that training is conducted an appropriate amount of time in advance of system use.

review of Draft

Agendas and

Meeting Minutes

Agendas and meeting minutes shall be delivered as an outcome of formal contractor and

Government engagements taking place under this contract

Agendas shall be made available at a minimum of one working day prior to meetings and minutes delivered 3 working days following meetings

Release Notes This report shall provide information for brand-new products, bug fixes, and feature enhancements.

The reporting of Release Notes with a variation of information that is equal but not limited to including the following information: Header that includes a Document name, Product name, Release number, Date of Release, Release note date, and Release note version; Overview;

Purpose; Issue Summary; Resolution; End-

User Impact; Impact Notes; Company

Disclaimers and Support Contact

Information.

This report shall provide information for brand-new products, bug fixes, and feature enhancements.

5.0 SUPPORTING INFORMATION:

a. Place of Performance

The work for this contract will be performed at the Contractor’s location and various

CBP locations located CONUS, Hawaii, and Puerto Rico.

b. Period of Performance

The period of performance shall include a base year with nine (9) 1 year option year periods.

c. Government Furnished Equipment (GFE) and Government Furnished

Information (GFI)

The Government anticipates a limited need for CBP-issued laptops in order to assist with integration efforts. The Government will provide information for SSO, Integration with CBP systems, and data migration as required.

Contractor must take all reasonable efforts to safely, securely, and properly handle and maintain all Government-furnished property provided to the Contractor for use under this contract. Contractor must track and maintain all Government furnished property and only use Government-furnished property for use in the performance of this contract.

Contractor is responsible for any loss or damage to Government-furnished property.

d. Data Rights

Notwithstanding any other clause concerning data, all Government data produced, recorded, transferred, or manipulated under this contract, including all trainings, shall remain the exclusive property of the Government. The Government shall retain exclusive right and domain over any by-product, document, or data produced under this contract, or any other use of the data produced under this contract. These documents and data shall be confidential and shall not be disclosed to any third party without prior written permission of CBP.

e. Travel

Temporary travel may be required to travel to other than the assigned work location. The

Contracting Officer (CO) or the COR must approve all travel in advance. If approved, the Contractor shall be authorized travel expenses consistent with the substantive provisions of the applicable Travel Regulation and the limitation of funds specified in this contract. All travel requires Government authorization/approval and notification to the COR. Trip reports are due to the COR NLT 5 business days after travel. The

Contractor shall submit invoices for reimbursement, citing the appropriate CLIN. All supporting documentation for travel must be legible, error free and clearly identify the amount of reimbursement being sought as part of the Monthly Financial Report.

Appendix 1

LSS Analytical Summary

Lab #: [(Alphanumeric Characters) Unique Report ID]

FP&F #: [unique identifier associated with evidence]

Case #: [(Alphanumeric Characters) unique identifier associated with evidence]

Analyst: [dropdown of Analyst Name]

Date(s) Laboratory Activities Performed: [date dropdown] to [date dropdown]

Attachments

1. [customizable dropdown of case records and associated documentation examples] Chain of Custody #: [(Alphanumeric Characters) unique identifier associated with evidence. Each FP&F number or Case Number can have multiple chain of custodies associated with it] Evidence Bag #: [(Alphanumeric Characters) unique identifier associated with evidence bag evidence is submitted in. Each FP&F number, Case Number, and chain of custody can have multiple evidence bag numbers associated with it.] Sample Description: [free text to describe sample]

Weighing and Sampling Methods: [dropdown of method names and numbers, e.g. ASTM Dxyz] Date(s) Performed: [date dropdown] Instrument(s) Used: [dropdown of instruments available for use] Initial [Weight type] Weight: grams +/- [Uncertainty value] Final [Weight type] Weight: grams +/- [Uncertainty value] Sampling Performed: [free text to describe how samples were taken and/or describe what was analyze]

[Method Description] Method: [dropdown of method names and numbers, e.g. ASTM Dxyz] Method Uncertainty: [free text to enter method uncertainty value] Date(s) Performed: [date dropdown] Instrument(s) Used: [dropdown of instruments available for use] Instrument Method(s): [free text for name of instrumental parameter set used] File Path: [free text of path where files are stored on instrument computer] Tune(s) Performed: [date dropdown]Tune Evaluation(s) Performed: [date dropdown] Verification Standard(s): [free text of reference standards used for verification] Sample & Standard File Name(s): [free text for file names of samples and standards] Solvents & Lot Numbers Used: [free text to list solvents used and associated lot and manufacturer] Reagent Preparation and Validation: [free text to list how reagents were prepared and validated]

Sample Preparation: [free text of sample and standard preparation] Results: [free text or data table/excel spreadsheet to summarize results] Conclusion: [free text to summarize results] Conclusion FP&F #: [unique identifier associated with evidence] Case #: [unique identifier associated with evidence]

Chain of Custody #: [unique identifier associated with evidence. Each FP&F number or Case Number can have multiple chain of custodies associated with it] Evidence Bag #: [unique identifier associated with evidence bag evidence is submitted in. Each FP&F number, Case Number, and chain of custody can have multiple evidence bag numbers associated with it.]

Line item: [free text to ID line item from chain of custody. Applicable if multiple line items are present.] Description: [free text to describe sample] Initial [Weight type] Weight: grams +/- [Uncertainty value] Final [Weight type] Weight: grams +/- [Uncertainty value] Sampling: [free text to describe how samples were taken and/or describe what was analyzed]

Substance(s) identified: [free text of substance identified] Substance(s) presumptively identified: [free text of substances presumptively identified] Methods of analysis: [dropdown of methods of analysis]

Comments:

1. [free text or dropdown for further details related to analysis or procedures]

Appendix 2

Lab #: [Unique Report ID]

Entry/ID #: [unique identifier for imported merchandise]

Analyst: [dropdown of Analyst Name]

Attachments

1. [customizable dropdown of case records and associated documentation]

Sample Description: [free text to describe sample]

Information Requested: [free text to document what analysis is being requested]

Sampling Performed: [free text to describe how samples were taken and/or describe what was analyzed]

[Method Description]

Method: [dropdown of method names and numbers, e.g. ASTM Dxyz]

Method Uncertainty: [free text to enter method uncertainty value]

Date(s) Performed: [date dropdown]

Instrument(s) Used: [dropdown of instruments available for use]

Instrument Method(s): [free text for name of instrumental parameter set used]

File Path: [free text of path where files are stored on instrument computer]

Verification Standard(s): [free text of reference standards used for verification]

Sample & Standard File Name(s): [free text for file names of samples and standards]

Solvents & Lot Numbers Used: [free text to list solvents used and associated lot and manufacturer]

Sample Preparation: [free text of sample and standard preparation]

Results: [free text or data table/excel spreadsheet to summarize results]

Conclusion: [free text to summarize results]

Conclusion

Date(s) Laboratory Activities Performed: [date dropdown]

Sample Description: [free text to enter sample description or populated based on field above]

Information Requested: [free text to enter sample description or populated based on field above]

Sampling Performed: [free text to enter sample description or populated based on field above]

Conclusion: [free text and/or data table to summarize results]

Methods of analysis: [dropdown of methods of analysis]

Comments:

1. [free text or dropdown for further details related to analysis or procedures] DRAFT