A03 Sources Sought Notice - D-25-TC-0025 - 2024 10 28.pdf

Brief Description: Sources are sought for small businesses that have relevant past performance providing operations and programming services on Laboratory Information Management System (LIMS) using agile software methodology. DEA’s LIMS system consists of the following components purchased by the Government: STARLiMS Commercial‐off‐the‐Shelf (COTS) software (Abbott Laboratory, Inc.), LabX software (Mettler‐Toledo), and numerous peripherals. These services would be conducted at HQ’s, but would support all DEA laboratories.

Response Date: 6 November 2024

Contract Specialist: Randy Bell Sr. (randy.bellsr@dea.gov)

Primary NAICS Code: 541511 (Custom Computer Programming Services)

Place of Performance: The location of work will be in Arlington, VA.

THIS IS NOT A FORMAL SOLICITATION. This Sources Sought Announcement/Market Survey is to determine if responsive and responsible small businesses are available to meet this requirement.

However, a solicitation for this requirement is planned to be published in November 2024.

The purpose of this “Sources Sought/Market Survey” is to gain knowledge of potential qualified sources and to develop additional knowledge of the existing market for the required services. Feedback on individual submissions will not be provided.

Capability Packages:

Certified Small Business firms are encouraged to submit capability packages. Businesses having the ability to provide the services listed in the attached Draft Statement of Work shall provide clear and comprehensive information supporting their experience, expertise, and current company profile to include the number of employees, office location(s), DUNS number CAGE code, small business designation/status claimed and annual revenue. The capability packages not to be proposals, but rather statements with background information supporting the company’s existing experience in relation to the area specified in the SOW. Capability statements must include the contact information (name, e‐ mail, and phone number) for government or non‐governmental clients that can verify your firms experience as a prime or subcontractor in the work described in the draft SOW.

Capability statements must describe your firm’s relevant past performance performing the following tasks/standards on the LIMS product for a client with multiple laboratories (which include forensics):

‐ Maintaining and supporting a Laboratory Information Management System ‐ Compliance with ISO/IEC 17025:2005 standards and ANSI National Accreditation Board (ANAB) requirements;

‐ Configuring the STARLiMS application on an Agency‐specific network ‐ Keeping a STARLIMS application up with the latest releases of the COTS software;

‐ Experience with the STARLIMS Forensic solution ‐ Configuring the different modules of the STARLiMS application;

‐ Integration of STARLiMS with other agency systems;

‐ Configuring and upgrading SDMS protocols for laboratory instruments;

‐ Integration of STARLiMS with LABX software ‐ Enhancing, developing and implementing testing procedures for load testing, unit testing, and system responsiveness;

‐ Providing expert advice and support regarding the configuration of the LIMS servers to include SDMS and grabbers to ensure optimum performance of the STARLiMS application and the LIMS system.

A draft SOW is attached for your information. This document is not in final form and is subject to change.

Interested parties must submit the information requested above by 6 November 2024, 5:00 pm EDT to randy.bellsr@dea.gov. Capability statements must include company name, address, telephone number, and client points of contact (phone number and email address). Capability packages must not exceed 5 pages (12‐point font preferred), and must be submitted electronically. Telephone calls regarding this notice will not be accepted. All information is to be submitted at no cost or obligation to the

Government. All information marked {Proprietary to ‘company name’} will not be disclosed outside of the DEA.

THIS SOURCES SOUGHT IS BEING ISSUED FOR PLANNING AND MARKET RESEARCH PURPOSES ONLY. THIS

IS NOT A SOLICITATION. RESPONSES TO THIS NOTICE ARE NOT CONSIDERED AS OFFERS AND CANNOT BE

ACCEPTED BY THE GOVERNMENT TO FORM A BINDING CONTRACT. THE GOVERNMENT IS NOT AND WILL

NOT BE RESPONSIBLE FOR ANY COSTS INCURRED BY INTERESTED PARTIES RESPONDING TO THIS

SOURCES SOUGHT.

Laboratory Information Management System (LIMS) Statement of Work (SOW)

SECTION C1 – DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

The mission of the Drug Enforcement Administration (DEA) is to enforce the controlled substances laws and regulations and to bring to the criminal and civil justice systems those organizations and/or individuals involved in the growing, manufacture, or distribution of controlled substances appearing in or destined for illicit traffic in the United States and its territories. DEA’s operation and support activities are distributed across five core business lines that include the following:

Investigative

Forensic

Financial

Intelligence

Administration

The core business lines require significant information technology (IT) resources to carry out key processes.

In support of the DEA mission, Information Systems Division (TC) provides IT services to include developing, deploying, and maintaining DEA’s mission critical and business applications as well as their supporting infrastructure. TC, the primary provider of IT support services for DEA’s Sensitive but Unclassified (SBU) IT infrastructure, is located at DEA Headquarters (HQ) in Arlington, Virginia, the Sterling Park Technology Center (SPTC) in Sterling, Virginia and the DEA office in Merrifield, VA.

The IT services provided by TC include planning, designing, developing, documenting, deploying, and maintaining DEA’s mission-critical and business applications and their supporting infrastructure.

The Software Operations Section (TGS) manages the development and enhancements to the Laboratory Information Management System (LIMS) using the agile software methodology.

LIMS provides a seamless and virtually paperless laboratory environment to the Office of Forensic Sciences (SF) and the over seventeen (17) laboratories located across the continental United States. TGS provides supporting estimates and schedules and coordinates resources to successfully complete the project and manage the project scope. TGS ensures communication/use of standard practices of the agile software methodology, software configuration standards, and functional testing standards. TGS supports ongoing application and database maintenance and provides Operations and Maintenance support to the LIMS system.

C.2 BACKGROUND

DEA’s workforce is comprised of over 14,000 personnel. The workforce includes law enforcement officers and administrative, technical, and professional support personnel. DEA’s Office of Forensic Sciences (SF) provides administrative support and management to seventeen

(17) laboratory locations across the continental United States. The laboratories provide service to DEA and other federal agencies’ mission and may assist state and local agencies.

Approximately 550 DEA employees, which include Laboratory staff and Headquarters staff, have access to the LIMS system. DEA’s laboratory enterprise consists of one (1) research laboratory, one (1) digital evidence laboratory, eight (8) regional laboratories, six (6) sub-regional laboratories, and one (1) training laboratory. Their locations and office designations are as follows:

Special Testing and Research Laboratory (SFL1, Dulles, VA) Digital Evidence Laboratory (SFL9, Lorton, VA)

Regional Laboratories:

Northeast Laboratory (SFL2, New York, NY) Mid-Atlantic Laboratory (SFL3, Largo, MD) Southeast Laboratory (SFL4, Miami, FL) North Central Laboratory (SFL5, Chicago, IL) South Central Laboratory (SFL6, Dallas, TX) Western Laboratory (SFL7, Pleasanton, CA) Southwest Laboratory (SFL8, Vista, CA) New England Laboratory (SFL10, Bedford, NH)

Sub-regional Laboratories:

Nashville (under SFL3) Three Digital Evidence laboratories (under SFL9) in Chicago, Houston and San

Diego Phoenix (SFLP) (under SFL8) Atlanta (SFLA) (under SFL4)

Training Laboratory (SFT, Quantico, VA)

The regional laboratories (SFL2 – SFL8, SFL10) are also known as ‘Field Laboratories’ because they directly support enforcement efforts of the DEA field offices. Regional laboratories support investigations by performing chemical analyses, latent print examinations, and other functions.

Conversely, SFL1 conducts only chemical analyses; SFL9 examines digital evidence; and SFLT provides chemical training.

DEA’s LIMS system consists of the following components purchased by the Government:

STARLiMS Commercial-off-the-Shelf (COTS) software (Abbott Laboratory, Inc.), LabX software (Mettler-Toledo), and numerous peripherals for the laboratories to include:

Corded barcode scanner

Honeywell, Xenon 1900h, USB Scanner Kit Honeywell, Xenon 1900h, RS-232 Scanner Kit

Inventory scanner

Intermec CK3 Scanner Kit (w/DEA STARLiMS Program Install) Honeywell CK65 (w/DEA LIMS Program Install)

Wireless barcode scanner

Motorola Barcode Reader DS6878 Honeywell Xenon 1902 Honeywell Xenon 1952

Barcode Printers

Zebra GX430t Zebra ZD621

Document Scanner

Fujitsu fi-8170 Fujitsu fi-7160 Fujitsu fi-6130

Keyboard/Video/Mouse (KVMs)

XTENDEX KVM Extender (HI RES KVM EXTENDER VIA CAT5 UP TO 1000

FT WITH RS232)

An additional module of STARLiMS, the Scientific Data Management System (SDMS) is used to parse data from laboratory instruments into LIMS and auto-populate raw data, charts, and/or graphs into defined LIMS test fields.

LabX® is a method-based software program specifically for Mettler-Toledo balances that is used to manage weighing activities and produce data for SDMS.

The LIMS solution provides all software necessary (including STARLiMS and LABX) within the existing DEA infrastructure and provides unimpeachable chain-of-custody tracking for items of evidence. STARLiMS provides compliance with ISO/IEC 17025:2005 standards and provides each DEA laboratory the ability to maintain records relative to the ANSI National Accreditation Board (ANAB) International accreditation program. LIMS manages forensic analyses, enables DEA to control laboratory business processes, and stores data regarding the forensic analyses performed by the DEA. This includes integration of data from DEA’s instruments and balances directly into the LIMS application.

The configuration and customization of STARLiMS began in 2009 and was deployed to production in January 2013 through July 2015. After several iterations of customized changes to the STARLIMS product, the DEA LIMS solution consists of a customized version of STARLiMS, SDMS, and LabX. This LIMS solution was deployed to most laboratories SFL1 currently has the following programs on StarLIMS:

a “lite” solution implemented where only the balances are integrated;

Referrence Materials (RefMat) program;

Fentanyl Profiling Program (FPP);

SFL9 and its sub-regional laboratories are being upgraded to STARLiMS v12.

The LIMS project enhances the support currently provided to DEA Special Agents, Diversion Investigators, the Office of Intelligence, other enforcement agencies, and the courts, by giving the laboratories the ability to provide “real time” information concerning the analysis and storage of evidentiary material. LIMS is a major component of the Concorde initiative. Concorde is a business-driven IT program providing unified access to and sharing of information in accordance with the DEA mission and the Department of Justice (DOJ) strategic plan. The Concorde program will eliminate stove-piped systems by integrating business functions and allowing for information sharing across the five main DEA business areas: Investigative, Intelligence, Forensic, Financial and Administrative. By modernizing legacy applications supporting these five business areas and integrating their business functionality, accurate real-time DEA information can be disseminated to authorized users. LIMS will fulfill the Forensic area of Concorde and provide real-time updates to applications within Concorde and allow information sharing within DEA systems. This will better allow SF to support DEA’s enforcement and intelligence operations worldwide.

C3. SCOPE OF WORK

In order to continue to advance the laboratories business processes, the contractor’s primary objective is to complete upgrade of STARLIMS version 12 (including customization) provide operations and maintenance support of production versions make minor configuration changes of the STARLiMS COTS product based on a prioritized list of configuration items following the agile methodology and maintain the current DEA STARLIMS application versions in line with Vendor software updates.

3.1 Project Tasks

The Contractor shall perform the tasks described in the following subsections.

3.1.1 Requirements Gathering

The Contractor shall interface with the Champion, Working Groups and Product Owners to identify and clarify detailed requirements for configuring the STARLiMS application.

Requirements shall be written as user stories and associated requirements shall be documented in Team Foundation Server (TFS). Discussions/actions documented via Meeting Minutes and forwarded to the appropriate Product Owner(s) for approval before dissemination to the Champion and other customers in attendance.

3.1.2 Participate in Daily Agile Stand-Up Meeting

The Contractor shall participate in daily Agile Stand-up meetings whereas each team member shall report work performed the previous day, work to be performed on the current day and any impediments to their performance of tasks. This information is strictly a verbal exchange and do not require a deliverable.

3.1.3 Attend Planning Sessions

The Contractor team shall attend a Planning Session at the start of each sprint where all developers on the team are in attendance. Team velocity will be established at the start of each planning session based on historical velocity of the development team, and any anticipated resource reduction due to vacations, etc. for the upcoming Sprint.

Prior to the planning session, requirements for user stories shall be fully documented in TFS for review and discussion by developers. Developers will “vote” via “Points Poker” to provide estimates for completion of prioritized Sprint user stories.

The Contractor shall document the results of the planning session in Team Foundation Server to include the team’s planned velocity and points assigned to each user story.

3.1.4 Attend mid-Sprint Reviews (as applicable)

The Contractor shall attend a mid-Sprint review to assess the month’s progress to date, with each developer on the team identifying the probability of completion of work assigned, as defined on the approved Sprint list in the planning session. The contractor shall identify any impediments and any need to potentially reallocate developers to the month’s highest priority tasks.

The Contractor shall document the results of this meeting and provide meeting minutes to the appropriate Government Product Owner for approval.

3.1.5 Attend Retrospective Sessions

The Contractor shall attend a retrospective meeting at the end of each month where each team member articulates the effectiveness of the month’s Sprint, issues encountered, and lessons learned. The team leads shall review the tasks completed and report the team’s velocity to include identification of points assigned and completed by each team member.

The Contractor shall document and provide minutes of the Retrospective Session to include all items discussed in the session to the appropriate Government Product Owner for approval.

3.1.6 Use of approved Application Lifecycle Management software (ALM) tools and approved Development servers

The Contractor shall utilize the current approved tool Azure DevOps, (formerly Microsoft Team Foundation Server (TFS)), to document epics, user stories, requirements, change requests, bugs and tasks.

The Contractor shall utilize source control and each developer shall track hours expended per task daily. At the end of each day, every Contractor developer shall either place their source code within the approved development server or request a code review by their team lead. If the code passes review, it can be checked in for potential inclusion in the next build.

3.1.7 Testing

The Contractor shall perform testing of user stories at various levels, usually performed by a Requirements Analyst/Tester (RA), the testing should include unit testing by developer, code reviews by Contractor Team Lead. Once the RA has successfully tested a user story, the Government Product Owner shall be notified that user stories can be tested and subsequently closed, if tested successfully. No code moves to production without the involvement of two developers (usually a developer and a team lead).

3.1.8 Maintenance and Support

The contractor shall provide ongoing O&M support of the LIMS solution.

The contractor shall identify and correct application defects, perform problem resolution, identification and documentation of application performance issues, provide user help support and system administration including system monitoring and file maintenance, system upgrades, system documentation updates as needed. The LIMS team must provide continuous system response time during normal business hours at all DEA laboratories, which are located across the continental United States (US) in different time zones.

The contractor shall provide helpdesk as well as Operation and Maintenance (O&M) support for the LIMS solution for all laboratories. The helpdesk support shall include, but is not limited to, answering of phone calls and emails, monitoring and updating DEA’s Service Desk system, and communicating with the end user regarding issue through resolution. In addition, the contractor shall provide Service Desk reports of all Service Desk calls. The report shall include calls received through DEA’s Service Desk (Service Center), transferred calls from program offices, and all calls received directly and/or all issues identified by the users. The Government shall review all reports for completeness and accuracy.

3.2 STARLiMS Configuration and Implementation Support

By using DEA’s Subject Matter Experts (SMEs), the contractor shall continue to configure STARLiMS, which includes the following, at a minimum:

Continue to maintain and support the LIMS application to meet the needs of the DEA Laboratories;

Continued compliance with ISO/IEC 17025:2005 standards and ANSI National Accreditation Board (ANAB) requirements;

Configure SDMS protocols for laboratory instruments;

Continue to upgrade SDMS to its latest version releases;

Continue to Configure the STARLiMS application and DEA-specific configurations to keep up with the latest releases of the software;

Configure any new module of the STARLiMS application as deemed necessary for DEA;

Maintain the STARLiMS interface with DEA’s Concorde systems including the DEA data warehouse, IMPACT, and Evidence Tracking systems;

Improve system performance;

Enhance, develop and implement testing procedures for load testing, unit testing, and system responsiveness.

3.3 Delivery of Incremental Software Beta Release

The Contractor shall bundle functional user stories at the end of each Sprint, if feasible, for deployment to a beta environment for further testing by selected users.

3.4 Delivery of Incremental Software Production Releases

With approval by the Product Owner, and Government, the Contractor shall promote beta versions into production following DEA’s Configuration Management Deployment Process and provide post-deployment support. Production releases are generally scheduled shortly after the end of each sprint but may occur in the middle of a sprint if requested by the Government and Product Owner.

3.5 Script Development and Data Warehouse support

The Contractor shall develop monthly or as needed scripts to load, process, or retrieve data.

Additionally, the contractor shall support any data warehouse needs regarding LIMS data.

3.6 Security Support

Certification and Accreditation (C&A) and Security Test and Evaluation (ST&E) activities are required to satisfy DEA and DOJ security requirements as found in the National Institute of Standards and Technology (NIST)/DOJ Guidelines. The contractor shall provide the following, as necessary:

Input to the LIMS C&A Plan (to include a Security Test Plan);

Updated System Features Users Guide (SFUG);

Participation in ST&E related meetings;

Updated supplemental software documentation not provided with standard STARLiMS documentation, needed to mitigate any security findings and technical support to mitigate all security findings to address OIG Findings;

Mitigate security findings as needed.

3.7 Documentation Support

Upon request of the TM, the Contractor shall provide documentation of procedures, application reference materials, workflows, and business processes and data structures. Additional documentation shall include Concorde Technical reference documentation, for use by the development teams to assist in clarification as software development is in progress, and to use as reference for any future software enhancements or modifications. The Contractor shall develop Quick Reference Guides (QRG) for each new feature released, to provide “at-a-glance” instructions of primary application functionality and modifications.

3.8 Project Management

The Contractor shall provide, at a minimum, monthly status briefings to the Contracting Officer’s Representative (COR), TGS/ TGR Section and Unit Chiefs, providing statistical charts and slides to demonstrate progress and trends of development teams, staffing status and issues and current contract burn rate and contract balance. The Contractor shall maintain acceptable staffing levels, with the contract fully staffed (having provided security packages to DEA) for at least the identified key personnel within 30 days of contract award date. Staffing levels shall be maintained at no less than 90% at any time during the contract. Offerors should thoroughly understand the DEA clearance process and be prepared for candidates to have several months wait times for a full clearance to be awarded. Contractors cannot begin billing to this contract without a full clearance.

The Contractor shall provide project management support to COR, Unit Chiefs, Section Chief and TGS Product Owners in providing historical, trending and financial reports.

The Contractor shall provide support to the Government Product Owners in the development of Sprint prioritization lists.

C4. DELIVERABLES – FORMAT/CONTENT

All deliverables are subject to review and approval by the COR. The COR will return comments and/or approvals within ten (10) business days of submission by the Contractor.

The Contractor shall submit the deliverables delineated in Section 4.1, Table 1.

Project deliverables shall be provided in the format specified by DEA (i.e. Microsoft Word, Excel, or PowerPoint; source code in TFS).

A. Articles of Delivery

Table 1 – Articles of Delivery

SOW

Reference

Deliverable Deliverable Format

Due Date

3.1.1 Requirements Gathering – user

stories/requirements in TFS

Electronic 2 business days after meeting

3.1.3 Document results of Planning

Sessions in TFS Electronic 1 business day after meeting

3.1.4 Document mid-Sprint Reviews Electronic –

attachment in TFS

1 business day after meeting

3.1.5 Document results of

Retrospective Sessions

Electronic – attachment in TFS

1 business day after meeting

3.1.6 Epics, User Stories, Requirements, Change Requests, Bugs and Tasks

Electronic Before COB of day identified by government

3.1.7 Update testing status in TFS Electronic Before COB of day tested

3.1.8 Operations and Maintenance Help

Desk Report

Electronic Weekly on Monday Morning

3.2

a) SQL and Data Migration

b) CERTS/LIMS Integration

c) Database backup or scripts

d) STARLiMS upgrades to include SDMS

a) & b) Electronic

a) One week prior to scheduled deployment or migration

b) As needed and requested by the TM

3.3 Software Build –Beta Electronic

deployment package

After successful testing and approval by the Product Owner and concurrence by the TM

3.4 Software Build –Production Electronic

deployment package

After successful testing and approval by the Product Owner and concurrence by the TM

3.5 Database Scripts and Data

Warehouse Support

Electronic As needed and requested by the TM

3.7 Requested documentation as

needed

Electronic or paper copies as needed

As needed and requested by the TM

3.8 Monthly status presentation and

supporting documentation

Electronic By 7th day of each month for preceding month’s data

C5. TELECOMMUTE AND EMERGENCY SUPPORT FOR

CONTRACTORS

Subject to the Contracting Officer’s Representative (COR) approval, eligible contractors may be able to telecommute on a situational basis to complete a specific work assignment.

Telecommuting may be designated for either a short period of time, or a longer period predicated upon a case by case basis. All telecommuting will be in compliance with provided DEA telecommuting guidelines. The Contractor shall be responsible for submitting to the COR for pre-approval, a plan that describes how the services would be performed during a closure and the level of support needed.

Telecommute contractors will not be allowed to perform work at home that requires access to DEA sensitive, classified, or Privacy Act protected information unless they have access to a Secure Network Solution (SNS) laptop computer or Firebird Anywhere token.

Before telecommuting on a situational basis, a contractor must request and receive approval from the COR prior to the actual date(s) of telecommuting. The request should be submitted in writing (email acceptable) sufficiently in advance to allow for prior approval

The COR will respond to the request documenting approval or disapproval.

If a contractor who has been approved to telecommute on a situational basis is unable to request and receive approval prior to the actual dates(s) of telecommuting as required for an unassigned or a situational telecommute day due to a weather-related or any other emergency, he or she has the option of telecommuting without prior approval when authorized by the Office of Personnel Management (OPM). This is called unscheduled telecommute. The contractor must still notify his or her COR of his or her intent to work unscheduled telecommute.

Equipment and Supplies: The contractor is responsible for protecting any DEA-owned equipment and to use the equipment only for official purposes. DEA is responsible for servicing and maintaining any DEA-owned equipment issued to the contractor. The contractor is responsible for installing, servicing and maintaining any personal equipment used. DEA is not liable for damages to the contractor’s personal or real property while the contractor is working at the approved alternative work site.

Communication: Contractors participating in the program shall be available to supervisors, co-workers and other contacts by telephone, E-mail, voice mail, Jabber, and Teams or other communication during their scheduled duty day as directed by their supervisors.

Monitoring Work Performance: The COR will verify what the contractor produces by examining the product(s) or results of the contractor’s efforts. This can be done by using project schedules, key milestones, regular status reports and team reviews. The COR may call contractors’ employees who are working at home or an approved alternate location.

C6. CONTRACTOR KEY PERSONNEL

TGS has designated all personnel from the following labor categories under this contract to be considered critical personnel. Being critical to the support of the DEA mission, the Contractor shall identify and provide a resume (maximum three pages per resume) and letter of commitment for each of the five (5) contractor personnel proposed for these labor categories.

01- Project Manager/Technical Lead 02- LIMS Architect

The following categories of labor shall work under this contract. The duties and minimum qualifications required of the persons performing in the labor categories are identified below.

All labor categories are exempt from coverage under the Service Contract Act. All personnel shall have thorough knowledge, formal training, and a high level of experience in a specific specialty as listed in the qualification column in the chart below.

6.1 Required Expertise

The contractor shall identify the following personnel.

ID Quantity Description Qualifications

01 – Project Manager

Key Personnel

1 Responsible for the quality and efficiency of the work performed under this contract, to include both technical issues and business processes.

15+ years of professional IT experience

5+ years of project management; experience in the implementation and maintenance of LIMS systems is optional.

5+ years of experience managing development teams using Agile or other development methodologies.

02 - LIMS

Architect

Key Personnel

1 Serves as the LIMS Architect; leads technical planning meetings; demonstrating critical soft skills in terms of professionalism, conduct and execution in a client-facing role; Ensures all development consistently follow prescribed Concorde development methodologies. Serves as the system architect for the LIMS project; provides expert advice regarding the

Documented experience as a system architect for a LIMS enterprise scale system having more than 1,000 users and a Database Management with more than 500 tables and 100 million total data rows. Resume must document significant contributions to overall system architecture.

5+ years of experience managing development teams using Agile or other development methodologies.

10+ years of software development experience.

10+ years of web development experience.

configuration of the LIMS servers, to include SDMS and grabbers to ensure optimum performance of the STARLiMS application and the LIMS system.

5+ years of experience with STARLiMS project Architecture and Development

5+ years of experience developing and implementing the STARLiMS Forensic system/application

Knowledge and experience with the implementation and integration of the SDMS software and STARLiMS in order to automate the population of results from analytical instrumentation with varying outputs (PDF, CSV, etc.);

Knowledge and experience with Mettler- Toledo balances and LabX® software a plus

03 - Sr. SQL Developer

1 Senior SQL Developer shall be responsible for maintaining the SQL database and responsible for all the application development efforts. Works in a team environment, utilizing agile development methodologies. Takes direction from the LIMS Technical Lead

8+ years of experience in the design, development and implementation of SQL Server databases to include creating and maintaining SQL Procedures, functions, packages and triggers.

Knowledge and experience with SQL databases including data conversion and database management

Knowledge and experience in forensic science to include drug analysis, fingerprint, and digital evidence examination

Knowledge and experience with all aspects of STARLiMS application, including: configuration, testing, implementation and operations and maintenance and bar-coding

Knowledge of Scientific Working Group for the Analysis of Seized Drugs/ Scientific Working Group on Digital Evidence (SWGDRUG/SWGDE) and Scientific Working Group on Friction Ridge Analysis; Study and Technology (SWGFAST) recommendations

Knowledge of ISO/IEC 17025:2005 standards and ANAB requirements

Knowledge and experience with data and system security including network security, encryption protocols, and electronic signatures

04 - STARLiMS Subject Matter

1 Responsible for all the application development efforts. Works in a team environment, utilizing agile

8+ years of web development experience.

ASP.Net C# MVC based web development experience is a plus

Expert development methodologies. Takes direction from team lead and LIMS Technical Lead.

Knowledge and experience with all aspects of STARLiMS application, including: configuration, testing, implementation and operations and maintenance and bar-coding

Experience with Agile development methodologies

Knowledge and experience with appropriate tools and techniques for productivity and code quality: debuggers, profilers, unit testing, source control

Knowledge and experience with the implementation and integration of the SDMS software and STARLiMS in order to automate the population of results from analytical instrumentation with varying outputs

Experience with Mettler-Toledo balances and LabX® software a plus

Additionally, the SMEs must possess at least three (3) of the following skills and attributes from the list below:

Knowledge of ISO/IEC 17025:2005 standards and ANAB requirements;

Knowledge and experience with AFIS and IAFIS systems;

Knowledge of SWGDRUG, SWGDE and SWGFAST recommendations;

04 - STARLiMS Subject Matter Expert

• 4+ years of web development experience.

• ASP.Net C# MVC based web development experience is a plus

• Knowledge and experience with all aspects of STARLiMS application, including:

configuration, testing, implementation and operations and maintenance and bar-coding

• Experience with Agile development methodologies

• Knowledge and experience with appropriate tools and techniques for productivity and code quality: debuggers, profilers, unit testing, source control

• Knowledge and experience with the implementation and integration of the SDMS software and STARLiMS in order to automate the population of results from analytical instrumentation with varying outputs

Responsible for all the application development efforts. Works in a team environment, utilizing agile development methodologies. Takes direction from team lead and LIMS Technical Lead.

05 – Requirements Analyst/ Helpdesk

2 Responsible for delivery high quality, on time, and on budget LIMS solutions that address customer business and workflow requirements. This includes conducting product gap analysis, managing and participating in configuration activities.

3+ years of experience capturing requirements

Experience writing Agile user stories and requirements documentation

Strong knowledge of laboratory fundamentals, processes and equipment required

Understanding of Laboratory regulatory regulations (ISO, CAP, GXP) highly desirable

Knowledge and experience with all aspects of STARLiMS application.

Computer Skills: Strong affinity to IT systems with working knowledge of LIMS desirable

In addition to the qualifications listed in the chart above, the contract team, as a whole, must also possess the following:

Knowledge and experience with analytical instrumentation utilized in a chemistry laboratory

Knowledge of the processing of evidence for the presence and analysis of latent prints Knowledge of ISO 17025 Experience implementing STARLiMS into an accredited forensic laboratory

6.2 Training

DEA expects the Contractor to provide personnel with the required skills to support the requirements identified in the contract. This includes the skills required to operate in the DEA IT environment. However, if Contractor training is required for tools or services not identified in the contract, DEA will fund either the training cost or the Contractor’s time for training,

• Experience with Mettler-Toledo balances and LabX® software a plus

• Additionally, the SMEs must possess at least three (3) of the following skills and attributes from the list below:

• Knowledge of ISO/IEC 17025:2005 standards and ANAB requirements;

• Knowledge and experience with AFIS and IAFIS systems;

• Knowledge of SWGDRUG, SWGDE and SWGFAST recommendations whichever is most beneficial to the government. DEA may fund time for training if training is DEA specific (e.g., DEA Security Awareness training, Firebird, etc.). If additional Contractor training is identified during the contract that would be beneficial to the government, DEA will determine on a case-by-case basis.

6.3 DEA-2852.211-70 PERIOD OF PERFORMANCE (BASE AND OPTIONS) (MAY

2012)

(a) The period of performance of Base Period of this contract begins on March 05, 2025, and ends on March 04, 2026.

(b) Pursuant to clause 52.217-9, Option to Extend the Term of the Contract, in the event that the Contracting Officer exercises an option, the period of performance for each option period shall be as follows:

Option Period I: March 05, 2025 - March 04, 2026 Option Period II: March 05, 2026 - March 04, 2027 Option Period III: March 05, 2027 - March 04, 2028 Option Period IV: March 05, 2029 - March 04, 2030

(c) The exercise of any options is subject to the availability of funding and the continuing needs of the Government.

6.4 Place of Performance

Work will primarily be performed at DEA work locations. This will be at either 600 and 700 Army Navy Drive, Arlington, Virginia or the 22400 Shaw Rd, Sterling, VA location and other local locations as specified by the COR. The Contractor shall work a regular 40-hour work week, between 6:30 a.m. to 6 p.m., Monday through Friday, but may fluctuate to meet operational needs. The annual number of hours should not exceed 1920 hours per FTE unless approved in advance by the COR. As needed, individual contractors may be authorized to work remotely for support of software deployments or to work outside of these hours.