Att. E_Qs_As_0001.xlsx
XLSX spreadsheet 47 KB Posted
- Solicitation number
- DJA-25-ALAB-PR-0242
About this file
This document is a comprehensive Questions and Answers (Q&A) file for a Laboratory Information Management System (LIMS) Modernization solicitation issued by the Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF). The solicitation (Number 15A00025Q00000095) is a 100% small business set-aside for modernizing the agency's laboratory information management system, with an estimated period of performance from 11/17/2025 through 11/16/2030. The Q&A document covers 155 detailed questions addressing technical requirements, system integration, data migration, user access, training, security protocols, and implementation expectations.
Key details include a requirement to quote for up to 200 users, with initial on-site training and potential remote configurations, and a technical demonstration process where vendors will be invited to showcase their LIMS solution after an initial submission. The current LIMS uses StarLIMS and FireTOSS systems with Microsoft SQL servers, and vendors are expected to migrate existing data from these systems. The solicitation emphasizes comprehensive requirements covering evidence tracking, instrument integration, chain of custody, reporting capabilities, and compliance with government security standards. Vendors must provide a solution that meets all required features, with the ability to potentially add value-added features, and must be prepared to support ongoing system evolution and laboratory needs.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SF1449_15A00025Q00000095_0002.pdf | ||
| Att. E_Qs_As_0002.xlsx | XLSX spreadsheet | |
| SF1449_15A00025Q00000095_0001.pdf | ||
| Attachment B - LIMS Features Questionnaire.docx | DOCX document | |
| Attachment 1 - QASP.pdf | ||
| PWS.pdf | ||
| SF1449__15A00025Q00000095.pdf | ||
| Attachment D - Past Performance Survey.docx | DOCX document | |
| Attachment C - Demonstration Outline.docx | DOCX document | |
| Att. E_Qs_As.xlsx | XLSX spreadsheet | |
| Attachment A - LIMS Required and Value Added Features.docx | DOCX document | |
| Attachment 2 - DOJ Self-Attestation.pdf |
Show all 12
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| # | RFQ Reference | ||||
| (i.e., Contract Line-Item Number {CLIN}, SF1449, PWS, Quotation Instructions, Evaluation Criteria, etc.) | CONTRACTORS' QUESTION | ATF's RESPONSE | |||
| 1 | PWS | Could you provide the number of analysts conducting DNA analysis (e.g. building plates, completing and/or reviewing extraction, quantitation, amplificaton, or detection steps)? | We currently have about 20 DNA analysts but that will expand into our new location with a projected number of 10 more DNA (these are already included in the 200 people). All disciplines will have the ability to use all required features, but not all required features will be used by each disipline. | ||
| 2 | PWS | In regards to Objective 12 Instrument Integration, can you please provide a list of instrumentation that you are expecting integrate, as well as expectations for migration? | Each lab with have instruments that will be included from each section such as DNA and chemistry instruments. The instruments have currently been merged to drop their data onto a drive. We will need the ability to grab that data from that drive and drop it into Lims. We will do a full data call on a number of instruments after the demonstrations (when quotes are due) so the pricing can be included in your quote. | ||
| 3 | Attachment A - 15.1.39 | Will the U.S. ATF be willing to sponsor and fund the selected vendor to obtain FedRamp compliancy? | No | ||
| 4 | Contract Line-Item Number 0005 | Could you provide additional information related to what service(s) or expectation(s) would fall under CLIN 0005 Off-site Consulting? | Off site consulting will include things such as helping get worksheets created/updated, help with implimenting upgrades/updates. Technical support availability. | ||
| 5 | PWS 3.0 Required Additions | Many of these items are able to be added or removed at any time, but come at an additional cost if it is outside of or in addition to the included services on the initial proposal. Could you please provide expectations surrounding how you would like vendors to approach this requirement? | Please include any added feature in the quote that is a "required feature" and if you have any features that add benefit from our list, they should also be included in the base price. | ||
| 6 | Factor 1 Subfactor 2 Technical Demonstration | Is it possible for a hybrid demonstration, where some representatives come onsite for the demonstration while others log in remotely if needed? | Yes. Only Offerors receiving a "Satisfactory" or higher adjectival rating will receive an advisory notification to proceed with Subfactor 2, Technical Demonstration. After notification is received, the Offeror can arrange the Demo however they like. | ||
| 7 | Solicitation 15A00025Q00000095 | Would the ATF consider extending the due date of the solicitation to October 1, 2025? | Solicitation extended through September 29, 2025. | ||
| 8 | PWS & Solicitation Section 2.6 Section F – Factor 3, Price | The PWS states that the Laboratory Services division employs 250 people whereas the Solicitation indicates pricing for 200 people. Can you confirm the number of users you anticipate needing access to the LIMS solution? | Not all the ATF employees will need access to the LIMS system. Only quote for up to 200 users. | ||
| 9 | Attachment C - Demonstration Outline | To prepare for a potential demonstration, could you provide the amount of time that will be alotted to vendors for the technical demonstration (e.g. 3 hour time slot)? Additionally, what is the expected time frame that will be provided between the demonstration invitation and the scheduled demonstration date (e.g. vendor invited to provide demonstration in two weeks)? | Each demonstration will take at least one (1) business day. The morning to show us your product and the afternoon to ask questions and allow you to show us or clarify the questions. We anticipate the demos to start within two (2) weeks after closing the solicitaion and after your submission of Attachment B. Once you are notified, you will be able to sign up for a time slot that best suits your schedule. | ||
| 10 | PWS | In regards to Objectives 2, 6 and 7, what is the ATF's definition of "Pilot"? | We will have a team of individuals from each section to pilot or test the system to go to get out any questions of kinks we may encounter so that we/you can make any adjustments we may need before going live with everyone. | ||
| 11 | Attachment A - 2.6.12 | What is the ATF's definition of "deferral" in regards to rejected evidence? | A blanketed statement that gets put in when the evidence is rejected. So we can automatically say no analysis and the case is closed without manually having to close/open the case. | ||
| 12 | Attachment A - 2.6.13 | Does this Value Added Feature refer to the one-time static event of migrating all historical data from existing laboratory systems via a data migration (as opposed to a live integration between the existing labortory systems and the new solution to continuously import data from the existing laboratory systems into the new solution)? | The added features are things your solution can do that will benefit the laboratory while using your solution. If they are available, they should be incoorprated into the price at the beginning. These items increase our usability upfront. Any features we request after will be in addition to this contract. | ||
| 13 | Attachment A - 2.6.19 | In regards to this Required Feature, what is the ATF's definition of "Notify"? | Send the reassigned or assigned examiner a notification that the evidence is ready for them. | ||
| 14 | PWS Section 10.0 Required Travel and Other Direct Costs | We typically recommend remote configuration services and training due to the flexibility, enhanced understanding utilizing shorter sessions over time, and proven success we've had with implementing our solutions. Would the ATF consider remote configuration and/or training in place of on-site? | Initial training will be onsite, and hardware configurations might need to be onsite. Most configurations can be completed remotely though our LIMS admin team. Initial training shall be on-site. Plan for up to 12 visits over the course of the contract to consist of 2-5 days a visit. | ||
| 15 | Subfactor 3: Technical Capabilities quote | To prepare as much as possible for potential next steps in this solicitation, can you provide formatting expectations and/or guidelines for the technical capabilities quote submission? Will this submission be narrative in format? | See sections 2.3 section C of 1449; offeror shall be able to provide how or what requirements are being met from the PWS in any format of your choice. See sections 2.6 F for specifics on listing out the service and products separately for pricing purposes. | ||
| 16 | Attachment A - 2.6.36 | In regards to the example provided for this Required Feature, how does the Evidence Record differ from the Item? Additionally, is the chain of custody tracked for both the Evidence Record and the Item? | The evidence record includes everything within the case (chain of custody). The case may have 5 or more items and each item will need to have chain of custody tracked as well as the overall case. You present how you would track the evidence. | ||
| 17 | Attachment A - 2.6.37 | In regards to this Value added Feature, does a round of testing correlate to a unique set of results? Additionally, are the unique results contained with the same or separate customer requests? | Round of testing will refer to how many times we use a particular instrument/testing for that item. If something has to be retested on the same instrument can that analyses/instrument/proceedure be added more than once? | ||
| 18 | SF 1449 | Per the solitication this is a 100% small business set aside. The document references FAR 52.219-14 "Limitations on Subcontracting" and states that if a small business is acting as the prime they must perform at least 15% of the contract work with its own employees, and sub-contractor (who may be a large business) can perform up to 85%. What documentation or reporting would be required by ATF to demonstrate compliance with FAR 52.219-14 when a small business is the prime and has a large business as a sub-contractor? | FAR 52.219-14(e)(1) applies as this is a services contract. Once awarded, the Contractor shall comply with the limitations on subcontracting "By the end of the base term of the contract and then by the end of each subsequent option period". Documentation and or reporting will be discussed post-award. | ||
| 19 | SF 1449 | Aside from FAR 52.219-14, are there any additional limitations or considerations (i.e. FAR clauses, ATF-specific requirements, or contractural clauses) should a small business (as prime) partnering with a large business (as a sub-contractor) be aware of? We understand that prior approval from the Contracting Officer is required pre-contract and that the prime must flow down security requirements (DOJ-05), security clearance requirements, and data breach reporting obligations (DOJ-02). | Please review the SF 1449 for all terms and conditions. | ||
| 20 | SF 1449, Section 2.3 | Section 2.3 states that ATF will not consider alternative terms and conditions, does this prohibition apply to all contractural terms and conditions after award (meaning no negotiation on contract) or only technical/pricing, etc. as set out in the solicition, or both? | Applies to the solicitation requirements. Anything after, requires negotiation / bilateral agreement. | ||
| 21 | SF 1449, Section 2.3 | Given that ATF will not consider alternative terms and conditions, would ATF be able to provide a sample contract? This would help offerors understand the exact terms to be accepted. If no, is there any additional information ATF can provided about the contract/terms. | "SF1449__15A00025Q00000095 lists all the terms and conditions the awarded Offerror agrees on. No new terms and condtions added without the awarded Offerors review/signature. | ||
| 22 | SF 1449, Section 1.4 | How would contract modifications (ex: scope changes, new requirements, etc.) be handled during performance given the FPP contract type? | See FAR 52.212-4(c) and FAR 43.103. | ||
| 23 | SF 1449, DOJ-02 (3) | What is the typical timeline for the Contracting Officer to approve subcontractors? Is there any requirements or documentation needed for this process? Can the approval process begin pre-award or only after award? | The subcontractors will need to be available during the demo stage of the solicitation and be included in the past performance section to ensure they meet the governments requirements. (Applicability |
Contracting officers must include the clause in all new contracts, orders, Blanket Purchase Agreements, Basic Ordering Agreements, or other procurement vehicles involving the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposal of personally identifiable information (PII), whether that PII relates to Federal employees or contractors, or members of the public.)
| 24 | Attachment A - 2.6.41 | Does this Required Feature apply only to DNA analysis or does it also apply to other disciplines? Additionally, for number 2: Can you please define the term "move" in the context of how it applies to the recording of data within a batch of samples? | The required features are collectively for all disciplines some features may not be used by them all but they will have to ability to use them. 2. Move is defined as the ability to Transfer/move an item to other users during the batch process. |
| 25 | Attachment A - 2.6.45 | Can you please list the required fields that must be shown to the user when performing their review? | You must be able to complete/demonstrate everything in the Demonstration outline Attachemnt C. All required features in Attachment B may be asked to be shown during the question and answer section on the demonstration day. |
| 26 | PWS | With regards to Objective 4 - Does the existing LIMS have a relational database structure? Is the database SQL, Oracle or some other type? To determine accurate data migration time estimations: How many tables and columns exist within the existing LIMS database? | The ATF laboratories currently stores information in two different electronic LIMS systems: StarLIMS (COTS) and FireTOSS (GOTS). Database information and linked files from both systems have to be migrated to the new LIMS solution. |
StarLIMS Database:
StarLIMS uses Microsoft SQL server. There are at least 500 tables, and over 2000 columns. Some database information is duplicated in multiple tables. ATF does not have entity relationship diagrams for the information in the StarLIMS database.
FireTOSS Database:
FireTOSS uses Microsoft SQL server. The database is divided into a definitions database and a results database. The results database contains the data that needs to be migrated to the new LIMS Solution. The data in the results database is stored in two tables in a parent object /child data configuration. It should be relatively straightforward to map the results in FireTOSS to the record structure in the new LIMS solution.
| 27 | PWS | With regards to Objective 4 - Does the GOTS FireTOSS system have a relational database structure? To determine accurate data migration time estimations: How many tables and columns exist within the GOTS FireTOSS database? | See question #26 |
| 28 | Attachment A - 10.5.1 | How are electronic signatures stored in the current LIMS? In a database table or as a physical attachment? What is the file type and size of each signature? | They are not currently stored. Only the signed document is being stored. |
| 29 | Attachment A - 10.5.3 | What data importing capabilities does FireTOSS have? Does it utilize an API? If Yes, what type of API? | The FireTOSS applications use a DLL written in Microsoft Visual Studio. The DLL has functions for interacting with the database and for copying files. |
| 30 | Attachment A - 8.1.7 | How does an Internal dashboard differ from a web-based dashboard, in the context of this Required Feature? | The primary requirement for 8.1.7 is that the dashboard show current metrics and not a view of metrics that were previously generated. |
The reference to internal versus web-based dashboards was an attempt to have a performance-based requirement instead of requiring the LIMS Solution to use a specific technology for the dashboard. For example, if the LIMS Solution uses a product like PowerBI for dashboards, the user might be viewing a dashboard in an application instead of a Web-based dashboard.
31 Attachment A 10.2 Spartan What type of database does Spartan use? Does the application have APIs available? Please clarify if the intended integration is to import cases from Spartan into the new LIMS solution to generate a case within LIMS with information entered into Spartan. SPARTAN is a custom application developed by ATF based upon the pega development platform. ATF contracts with a team of developers for SPARTAN. I have reached out to the SPARTAN developers to get more information about the database that SPARTAN uses.
The goal is for the ATF agents to initiate requests for laboratory services from within SPARTAN so that they do not need to retype any case information. Whether this means that a form will be created in SPARTAN that will pass information to the LIMS solution or that a link will be added to SPARTAN to open a form in the new LIMS will have to be decided during the system configuration.
| 32 | Attachment A 10.3 FireTOSS | Would the ATF lab personnel prefer to review the data before it becomes part of their LIMS system, or would they prefer to make additions or changes to the data directly within the LIMS system? | it will be reviewed at the instrument level then sent for merge directly in the LIMs. But we would like to ability to add things such as initials of dates to the data in LIMS. |
| 33 | Attachment A 10.5.2 | Typically data migrations from legacy systems to new systems take place all at once. Is this requirement indicating that data will continue to be added to the legacy system post data migration that will need to continually be synced or added to the new LIMS solution? | They will be migrated at the time of implimenting the new LIMS system. There will be a short time during the pilot that the merge will be continuous. But once it goes live where everyone is using it, all legacy data should already be incoorperated. |
| 34 | Attachment A 15.1.41 | How are existing attachments stored? As a var binary value in an existing database or in a physical file share with a given value linking back to the appropriate system/subsystem? | StarLIMS File Attachments: |
StarLIMS uses a SDMS server to store linked files.
FireTOSS Linked Files:
The linked files in FireTOSS are stored on a network storage device. The filename and locations of the files are stored in the FireTOSS results database.
| 35 | Attachment A 15.1.42 | Does your existing system store a unique value for each leg of an evidence items’ chain of custody? | FireTOSS contains a similar system, but I believe has a less formalized setup than a full document management server setup. It also uses links however to pull data stored in another data storage server. |
| 36 | Attachment A 15.1.43 | Please clarify what constitutes a test sample, whether it is a specific analytical result test or an overall test case encompassing all data elements involved in a case? Will ATF provide the vendor with a full copy of sanitized (PII removed) test case data? | Test sample information includes every examination from each of the instruments used during that analysis. Each instruments data should be pulled in to be stored and viewed in LIMS then all together, it becomes a part of that item/test sample.Yes you will recieve examples of what we need to pull in and make part of the case data. |
| 37 | PWS 2.1.15 Deliver Entity Relationship Diagram (ERD) | Would ATF accept a database dictionary document in place of an entity relationship diagram? | At least a ‘high level’ Entity Relationship Diagram must be provided illustrating major database tables, field structures, and database joins. |
The database dictionary document that described the high-level and low-level details of the database relationships would be acceptable as an addition to the ‘high-level’ ERD.
| 38 | pg 1 of PWS states ATF employs 250 chemists, engineers, firearm..., but the RFQ wants pricing for 200 users. How many of these 200 should have administrative privileges? I.e. Be able to configure and update the LIMS? | Not all the ATF employees will need access to the LIMS system. Only quote for up to 200 users. We will do a data call at the completion of the demonstration (when quotes are due) to abtain how many administrative rights will be needed. |
| 39 | How many external users are expected to access the system monthly? What kind of access do they need? In addition to the 200 identified in the RFQ | No external users. |
| 40 | For past performance, the requirement is to have 2-3 Federal clients or clients with equivalent complexity complete Attachment D and submit to you, Steven Jaimes before 11AM EST on Sept 24. A CPAR is not required for each reference, simply a completion of attachment D. Correct? | Incorrect. The requirements of 2.5, Section E - Factor 2, Past Performance is only applicable IF the Government notifies the top rated Offerors to submit a technical capabilities quote with Solution for Subfactor 3… and to submit Volum 3, Factors 2 and 3, Past Performance and Price respectively. |
Under 2.5, Section E - Factor 2, Past Performance, Offer shall also provide the Contractor Performance Assessment Reporting System (CPARS) finalized for referenced contracts/orders with the Federal Government, however, submit Attachment D Past Performance Survey for the submitted references...if a CPARS cannot be obtained.
| 41 | Regarding the 12 site visits, is this expected per year? | Per 5 year contract up to 12 total (includes training sessions). We expect each site visit during that time to take about 2-5 days each. | |||
| 42 | For the Sept 24 due date, are we required to submit a price/budget for the project or will this be required after Subfactor 2. i.e. do we need this now or wait until after the demo? | See question #6 above. | |||
| 43 | General Question | Are there any limitations or restrictions on the use of agentic AI or AI-assisted development tools for tasks requiring customization to the LIMS solution offered? | As of current, there are no restrictions or limitations. | ||
| 44 | General Question/PWS Objective 11 | Are there any limitations or restrictions on the use of machine learning models for data engineering, analytics, or modeling tasks related to LIMS operations, such as the metrics and analytics reports? | As of current, there are no restrictions or limitations. | ||
| 45 | PWS - Objective 4 | Will the ATF provide a data model or entity-relationship diagram (ERD) for the integrating systems (Qualtrax, SPARTAN, FIRETOSS), if available, to assist in estimating the level of effort for data migration? | You will be provided what you will need for the subfactor 2 during the demonstration. Pricing is not due until you reach that subfactor and the Demostrations are cmplete. A data call will be completed to determine the databases to be merged and the number of instruments to be merged in. | ||
| 46 | PWS - Objective 12 | Will the ATF provide example instrument output files containing anonymized or generic data, representative of those the LIMS solution will import for analysis results, to assist in estimating the level of effort for instrument integration? | You will be provided what you will need for the subfactor 2 pricing at that time. See question #45. | ||
| 47 | Attachment A - LIMS Required and Value Added Features - 4.5.15 Required Feature | ||||
| Access to each secure evidence location can be assigned to each staff member individually or to designated task groups to which members belong. [ERP_139*] | We would appreciate clarification on whether the scope of this required feature: |
1) Is the requirement intended to limit access to evidence locations within the LIMS solution, or
2) Is the requirement that the LIMS solution must integrate with existing physical access control systems?
| 3) If physical access control is intended, can additional information be provided on any existing physical access control systems (PACS) the solution may need to integrate with. This question interrelates with our question below on value added feature 4.5.27 (see below). | #1 this allows us to place the evidence in only a secure location, to a physical person or to a designated task location (e.g. if there is a task group for evidence vault) all will be internal to the LIMS. | ||
| 48 | Attachment A - LIMS Required and Value Added Features - page 33 - 4.5.27 Value added Feature | ||
| The Solution can control access to evidence lockers to provide secure transfer of evidence to the assigned person while maintaining an automatic chain-of-custody. The feature can include notifications to inform users of evidence transfer requests and when evidence is ready to be retrieved. | We would appreciate clarification on whether this requirement refers to two distinct capabilities: |
1) Is the requirement that the LIMS solution must integrate with existing physical access control systems to control access to Evidence Lockers – e.g., via key card, biometric authentication, or smart locker systems, to ensure only authorized personnel can access physical evidence storage?
2) Is the requirement that the integration of the LIMS solution with existing physical access control systems to record automatic Digital Evidence Transfer Workflow & Chain-of-Custody – i.e., the ability to assign evidence to individuals, notify them of transfer requests, and maintain a secure, auditable digital record of all interactions with the evidence.
| 3) If physical access control is intended, can additional information be provided on any existing physical access control systems (PACS) the solution may need to integrate with. This question interrelates with our question below on value added feature 4.5.15 (see above). | Yes this also follows the above question (#47). A secure location (lockers) is controled by the ATF people not by LIMS. We only need the ability to transfer electronically in LIMS to a specific locker/room and a notification go to the transferee letting them know they need to complete the transfer in LIMS then they can pick up evidence from secure location. Again LIMS will not have access to that location it is done externally by the evidence control people. | ||||
| 49 | PWS | Is the LIMS Modernization project focused on modernizing the existing system, or is it aimed at implementing an entirely new solution? | Implementing a new system. | ||
| 50 | PWS | Are vendors allowed to propose their own technologies for the LIMS modernization, or is there a preference for maintaining compatibility with existing systems such as Spartan, FireTOSS, and Qualtrax? | They may need to be able to merge some data from Spartan during evidence control. To be determined and will do a data call to verify after the demonstrations (before quotes are submitted). | ||
| 51 | PWS | What specific techniques, technologies, and skills does ATF expect vendors to utilize in the proposed solution for the LIMS modernization? | You can utilize an Commercial Off-The-Shelf (COTS) solution or propose one of your own solutions. | ||
| 52 | PWS | What is the expected level of expertise or experience required from the vendor’s project team, particularly in the context of LIMS modernization? | They must be able to create, build or utilize a LIMS system and be able to fully support the system and all our requirements | ||
| 53 | PWS | What specific requirements or guidelines should vendors follow for data migration from the current LIMS system to the modernized solution? | This will be more discussed after the demonstration before the quotes. But ultimately you will need to be able to merge our instruments so their data gets pulled into your solution. | ||
| 54 | PWS | Does the LIMS Modernization project allow vendors to propose and implement a completely new solution, or are vendors required to work within the existing technology stack chosen by ATF? | NEW | ||
| 55 | PWS | If vendors are allowed to propose a new solution, would there be flexibility to integrate the case manager solution of our choice, or is the integration with an existing case manager system mandatory? | You create the solution you feel meets the requirements on intergrating into our current LIMS, other than transfer of original data of old cases. | ||
| 56 | PWS | How should the new system handle existing data? Specifically, does it need to feed directly into an existing case manager, or can vendors propose a new method for managing and utilizing case data? | See question #57. Please propose what your solution can accomplish for data management. | ||
| 57 | PWS | What level of integration is required with the current systems, and are there specific data flow requirements that must be followed when feeding data into case management systems? | No specific data flow. Instruments are currently feeding to one location and that needs to be pulled (manually) into the LIMS. It would be great to have the data automatically transferred into the case. | ||
| 58 | PWS | How should vendors approach the integration of legacy data with the new system to ensure seamless continuity of operations? | This will be more discussed at the demonstration. But the legacy data should be able to be metrged into the new system. | ||
| 59 | PWS | What are the main challenges you're currently facing with the existing LIMS system? | Our current LIMs is no longer upgradable as it was programed. | ||
| 60 | PWS | Are there any specific features or functionalities that the current LIMS lacks, which you would like to see in the new system? | We require all the Required features, no exception. Any of the other features just adds value to your solution. Please include all the features you can supply | ||
| 61 | PWS | Are there any legal or compliance standards (e.g., FISMA, ISO) that the new system must meet? | We are ISO certified and ANAB accredited the required features cover all the items that come from these two entities. | ||
| 62 | PWS | How do you see the new system integrating with your current lab instruments and other software systems? | Instruments are connect to one server currently, we will just need to migrate them into the LIMS to drop the data there. | ||
| 63 | PWS | Will the new system need to work with external agencies or partners for data sharing or collaboration? If so, what kind of data needs to be shared? | Only Spartan as of current but more information after the demonstration. | ||
| 64 | PWS | Do you foresee the need for any data migration from the current LIMS or other systems (e.g., FireTOSS)? | Yes current cases data will need to be moved over to be stored on the new solution. | ||
| 65 | PWS | Will the new system need to support integration with existing databases or forensic tools, such as CODIS or AFIS? | Not currently, but this can also be asked during the demonstration. Please provide any information you have to support integration. | ||
| 66 | PWS | How do you currently manage workflows and task assignments within the lab? Would you like the new system to automate task tracking and notifications? | Task tracking would be helpful. Notification of assignments is currently being used. | ||
| 67 | PWS | What types of reporting and analytics would be most beneficial to your team (e.g., workload tracking, case progress, performance metrics)? | This is questions for the team during demonstration. All of those are possible types of reporting. Please be prepared to show or explain your different features in reporting and analytics. | ||
| 68 | PWS | Are there any specific roles or permissions you’d like to define in the new system to ensure proper access to case and evidence information? | Yes there will be specific assignments and roles throughout the four different laboratories. | ||
| 69 | PWS | How do you track the chain of custody for evidence, and what additional features would you want in the new system to improve this? | Please see the section 2.3 and 4 in Attachment A. | ||
| 70 | PWS | What level of training do your staff need to effectively use the new system? Would you require both initial and ongoing training sessions? | Initial for the polit team and LIMS admin, then a training session for each lab. | ||
| 71 | PWS | Do you have any specific preferences regarding training formats, such as on-site, virtual, or hybrid training options? | On site training for the initial training, then virtual will be allowed for any additional training that may be required. | ||
| 72 | PWS | What is the expected timeline for the full implementation of the new system? Are there any key milestones or deadlines we should be aware of? | We would like it implemented within the first year and instrument/data migration can be in year 2. But subject to change. | ||
| 73 | PWS | What is your preferred approach for testing the new system (e.g., pilot testing, full-scale deployment)? | Pilot testing with people from all our disiplines . | ||
| 74 | PWS | How do you envision the transition from the old system to the new one? Will there be a phased approach, or would you prefer a complete switch-over? | After the pilot, a complete switch over. But this is also subject to change/disscuss at the demonstration. | ||
| 75 | PWS | What security protocols must the new system adhere to, especially considering the sensitive nature of forensic data? | To be discussed more at the demonstration. See section 1.7 in the PWS for documents | ||
| 76 | PWS | Do you require the system to meet any specific government cybersecurity standards (e.g., FIPS, NIST)? | To be discussed more at the demonstration. See section 1.7 in the PWS for documents | ||
| 77 | PWS | What level of encryption and data protection will be necessary for the new system to secure sensitive information? | To be discussed more at the demonstration. | ||
| 78 | PWS | What is the preferred timeline for deploying the new LIMS system? Are there specific deadlines or milestones we should be aware of? | We would like it implemented within the first year and instrument/data migration can be in year 2. But subject to change | ||
| 79 | PWS | Would the deployment of the new system require setting up new infrastructure, or will it be integrated with your existing infrastructure? | Setting up a whole new system. | ||
| 80 | PWS | How would you like the deployment to proceed—should it be phased (e.g., testing, pilot, then full deployment) or done all at once? | Yes testing envoironment, pilot to each discipline, and full deployment. | ||
| 81 | PWS | Do you have any preferences regarding cloud-based vs. on-premise deployment? If cloud-based, do you have a preferred provider (e.g., AWS, Microsoft Azure)? | We are currently cloud based. See questions #27 and #29 for more detail. | ||
| 82 | PWS | What technology stack is your current LIMS built on, and are there any specific platforms or technologies you prefer or are currently using? | See questions #26, #27 and #29. | ||
| 83 | PWS | Do you have any specific technology preferences for the new system (e.g., programming languages, frameworks, databases)? | Not at this time. | ||
| 84 | PWS | How do you envision the new system integrating with other law enforcement or government systems? Are there specific APIs or data-sharing standards that should be supported? | The goal that the new system be able accept input from an outside (law enforcement) database, such as Spartan. As stated in the second half of the question, the answer is yes, the goal would be to accept case information from Spartan and generate case information into the new LIMS system. More information during the demonstration. | ||
| 85 | PWS | Do you prefer using a Commercial Off-The-Shelf (COTS) solution for the new LIMS, or do you require a custom-built solution tailored specifically to your needs? | Whatever solution you feel will best siute our requirements. | ||
| 86 | PWS | If you are considering a COTS solution, are there any specific platforms or products you’ve evaluated or would like to integrate with? | No, not at this time. | ||
| 87 | PWS | How important is it for the new system to be scalable and easily upgradable in the future? Will you need to support additional users, labs, or types of evidence over time? | Yes important, it will need to be easily upgradable and continue to support new users, multiple laboratories and a variety of evidence. | ||
| 88 | PWS | Are there any legal or compliance requirements (e.g., government regulations, security standards) that must be considered when choosing between a COTS or custom-built system? | To be discussed more at the demonstration. See section 1.7 in the PWS for documents detailing security requirements. | ||
| 89 | PWS | Would you prefer a modular system where different parts of the system (case management, evidence tracking, reporting, etc.) can be added or modified as needed? | All the disiplines should be included at the beginning with proposal, modifiable as needed. Any additions might be added later | ||
| 90 | Instructions | Will commercial past performance of similar type be accepted? | Yes. The Offeror shall submit Attachment D, Past Performance Survey for the submitted references to the CO, Steven Jaimesvia email (Steven.Jaimes@ATF.gov) if a CPARS cannot be obtained. For this factor, Recent is defined as LIMS Solution installed with a successful existing LIMS data migration and product support within the last three (3) years. Relevant is defined as work similar in complexity, magnitude, and type of the work described in the PWS. | ||
| 91 | Instructions | Are there any specific certifications or security clearances required for the personnel working on this project? | See section 1.7 in the PWS for documents detailing security requirements. Also see section 13.2 of PWS for clearence requirements. | ||
| 92 | Instructions | What insurance coverage is required for vendors participating in this project? | See FAR 28.306. | ||
| 93 | Instructions | What pricing structure is preferred for this LIMS modernization project? | Address all required features. See FAR 2.6 Section F -Factor 3, Price for requirement. | ||
| 94 | Instructions | How is the configuration of the solution accounted for in the pricing? | Address all required features and structure the price according to Section 2.6 Section F of the 1449. The configuration should be an all around fix price based on Section 2.6. | ||
| 95 | Instructions | How many past performance references are required, and how many years back should they go for these references? | See Section E - Factor 2, Past Performance | ||
| 96 | Instructions | Will subcontractors be considered for this project, and what are the requirements for their involvement? | Yes you will need to provide who your subcontractor is during the demonstration. | ||
| 97 | Instructions | Are all resources required to be direct employees of the vendor, or can subcontractors be used? | Subcontractors can be used for this project. See question # 96. | ||
| 98 | Instructions | Where is the LIMS solution expected to be deployed (on-premise or cloud-based), and are there any restrictions on the deployment location? | See Section 12.0 in PWS | ||
| 99 | Instructions | Are there any restrictions on candidates holding work permits (such as H1-B, Green Card, or U.S. Citizenship) for this project? | The Department of Justice does not permit the use of Non-U.S. citizens in the performance of this contract or commitmentfor any position that involves access to or development of any DOJ IT system. By signing the contract or commitmentdocument, the contractor agrees to this restriction. In those instances where other non-IT requirements contained in thecontract or commitment can be met by using Non-U.S. citizens, those requirements shall be clearly described. See section 1.7 in the PWS for documents detailing security requirements. | ||
| 100 | Instructions | If the reference is an end client where we were a subcontractor, would that still be considered valid for past performance requirements? | Yes. | ||
| 101 | Instructions | Are there any specific eligibility or background requirements for personnel working on this project? | See question #91. | ||
| 102 | Instructions | Is on-site presence required for the project, and if so, how often and for what tasks? | See question # 41. | ||
| 103 | Instructions | What is the exact location where the services need to be performed (e.g., ATF offices, laboratory sites)? | See PWS, Section 1.6, Place of Performance | ||
| 104 | Instructions | Is it required for vendors to be certified as a FEDRamp-authorized provider to participate in this project? | |||
| "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." | Yes this is required. | ||||
| 105 | PWS | pg, 20 Is Microsoft GCC Dataverse Power Platform acceptable in ATF tenant? RE: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. | Please provide the best "solution" you see fit for this project. It will be detetermined if it meets our needs. | ||
| 106 | PWS | There is an inconstant note pg. 5 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. pg. 20 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. If we need to provide travel cost they need to be estimated and fixed and not on a Cost basis? | Yes they need to be estimated as a fixed cost included in the final quote. | ||
| 107 | SF 1449, p. 39, Section1.0 Quotation Instructions | The instructions state that the offeror should submit no more than two files, Non-PRICE quote (Vol. 1) and PRICE quote (Vol. 2). However in the table on the following page it outlines 3 separate volumes. Please advise if Vol. 1 Introduction & Other Documentation and Volume 2 Non-Price Section should be sent as one combined file. | The two files shall be Volume 1 (all together) and Attachment B from Volume 2 subfactor 1. Not quotes will be submitted until afer the demonstration by invite only. | ||
| 108 | SF1449, p.42, 2.5 Section E - Factor 2 Past Performance | Section E - Factor 2 Past Performance it states that offeror "shall provide references for a maximum of 3 contracts w/ federal or commercial customers," please clarify if there is a minimum number of references. | Corrected. Offeror shall only provide up to 3. Offeror shall submit Atachment D…. If a CPARS cannot be obtained. | ||
| 109 | SF1449, p.42, 2.5 Section E - Factor 2 Past Performance | SF1449, p.42, 2.5 Section E - Factor 2 Past Performance states that an offeror shall submit recent and relevant past performance for team members provided they clearly explain their significant involvement in the proposed task order. Can you confirm that a team member providing the technology/platform the LIMS solution is built on would be considered significant and acceptable as a contributor for past performance. | The team member needs to have significate knowledge of the product and how it works. | ||
| 110 | SF 1449 p.41, Section 2.4 | The RFP states that the "Offeror should have 100% of the required features in current version of the products. If the Offeror cannot provide 100% of the required features, Offeror can propose a Solution that should make up 100% of the required features." Can you clarify what is meant by that? | If the offeror can provide another means to meet this requirement through a different section in their features, then they are considered able to meet the requirement through a proposed solution. e.g 4.5.3 required feature: The Solution can transfer an item of evidence to another user without restriction. If this can't be done directly, can you propose a solution to complete it through another means? Like moving the item of evidence to it's own container, or sub-exhibiting the item to be transfered. | ||
| 111 | SF 1449 p.41, Section 2.4 | The RFP states that the exact date, time, address for the demonstrations will be provided after evaluation of Subfactor 1; for the resource planning purposes could you provide an estimate of the amount of time between submission and demonstration we should expect to have in order to prepare? | See question #9. | ||
| 112 | Attachment A, 3.2 Record Types | Provided in attachment A were details on numbers of record types, will DOJ provide any obfuscated/redacted data (such as types of evidence provided or tests, analysis requested, types of details captured within an overall case, etc.) for the demonstration phase so we can best bring to life the environment we are being asked to present? | You will follow the demonstration outline (Attachment C) for the demonstration. We can discuss the types of worksheets/reports that will be needed at the demonstration. Data pulled from our instruments will be pulled over with no changes. | ||
| 113 | SF 1449 p.43, Section 2.6 | For the proposed 200 system users, can you please provide a description of the anticipated monthly utilization. | A data call will be completed to determine the monthly utilization and provided to those invited to submit a quote after the demonstration. | ||
| 114 | SF1449_15A00025Q00000095, Page 9 of 62 | ATF-09 Notice of Delay Performance (April 2025) - These terms reference an 8(a) award. Will the Government please confirm whether this procurement is a 100% Small Business Set-Aside (SBSA) and not an 8(a) award? | It will be a 100% Small Business Set-Aside. ATF-09 does not apply and removed. | ||
| 115 | SF1449, Offer Due Date | Will the Government consider an extension to the due date of proposals to enable offerors to review and incorporate responses to questions? | See question #7. | ||
| 116 | PWS 2.1.6 | Will the Government share the pilot requirements in advance of technical demonstration? | See objective 2 in PWS, This will be part of the initial meetings after the award of the contract. Please follow Attachment C for the demonstration. | ||
| 117 | PWS 2.1.12 | Please provide the total data storage capacity currently in use within your environment for your LIMS and FireToss systems, respectively. | A data call will be completed and the information will be provided after the demonstrations. | ||
| 118 | PWS 2.1.12 | Can you share the current size and struture of data storage footprint? | See Questions 27 and 29. A data call can be completed and information for current size can be provided at the demonstration. | ||
| 119 | PWS Objective 12 | How many instruments for each laboratory site will be migrated/ integrated? | A data call can be completed and information for instrument migration can be provided at the demonstration. | ||
| 120 | PWS 3.0 | Will the Government expand in detail what is meant by "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."? | All of these items SHOULD be already included as part of your quote. If you did not add them, after the award of the contract, we have the right to add them or remove them at no extra cost. If any item was not agreed upon during the contract negotioation, the goverment will purchase that item as a separate contract or modification to the contract. | ||||
| 121 | PWS 3.0 | Of the 200 employee user licenses referenced, how many licenses will be named users? | We will do a data call at the completion of the demonstration (when quotes are due) to abtain how many named users will be needed. | ||
| 122 | PWS 3.0 | Of the 200 employee user licenses referenced, how many licenses will be concurrent users? | We will do a data call at the completion of the demonstration (when quotes are due) to abtain how many concurrent will be needed. | ||
| 123 | PWS 2.1.6 | Can the Government provide access to its test compendium to ensure all deliverables are tested against the offical standard? | This will all be arranged during the post award meetings. | ||
| 124 | PWS 1.1 | Will the Government share annual number of tests? | We can do a data call for the demonstration and provide the approximate number of tests per year. | ||
| 125 | PWS 1.1 | Does Government expect annual number of tests to increase and/or surge? Please expand with details. | The annual number is dependant on the amount of cases per year. We can provide a data call with the average amount over the last few years. | ||
| 126 | Attachment A - Req: 3.16.99 | Value added Feature - The Solution has authentication functionality to compare a file that the user selects with the case record that is selected in the Solution. Can you expand on what the requirement is? Please provide an example. | The laboratory is concerned that someone might modify a file that the laboratory produced. The laboratory wants the new LIMS to have functionality to compare a file with the file stored in the LIMS and verify/authenticate that the file is exactly the same. | ||
| 127 | PWS Objective 12 | What barcode scanners/related hardware are in use today? | None are currently being used. | ||
| 128 | PWS 1.3 | What is the existing (incumbent) LIMS solution ? | StarLims | ||
| 129 | 2.0 QUOTATION CONTENT | In Volume 2, Section D, Subfactor 3, - Will the Technical Capabilities Quote be due at same time as Technical Demonstration or at a later date and by invite only? | All the quotes will be submitted after the demonstration (invite only). | ||
| 130 | 2.0 QUOTATION CONTENT | In Volume 3, - Will the Section F – Factor 3, Price Section Quote be due at the same time as Volume 2 Subfactors 2&3, or at a later date and by invite only? | All the quotes will be submitted after the demonstration (invite only). | ||
| 131 | 2.0 QUOTATION CONTENT | In Volume 3, - Will the Section E – Factor 2, Past Performance be due at the same time as Volume 2 Subfactors 2&3, or at a later date and by invite only? | The past performance will be submitted after the demonstration (invite only). | ||
| 132 | 2.0 QUOTATION CONTENT | Can the Government confirm Volume 1 (Section A, B, and C) and Volume 2 (Section D, Subfactor 1, Attachment B) are the only items required for submission on September 24th? | Yes confirmed. | ||
| 133 | 2.0 QUOTATION CONTENT | Can the Government provide its anticipated timeline between submission on September 24th and invitation notification/dates for the Technical Demonstration? | Each demonstration will take at least one (1) business day. The morning to show us your product and the afternoon to ask questions and allow you to show us or clarify the questions. We anticipate the demos to start within two (2) weeks after closing the solicitaion and after your submission of Attachment B. Once you are notified, you will be able to sign up for a time slot that best suits your schedule. | ||
| 134 | Quote Instructions 2.5 Past Performance | All other variable aside, will federal and commerical sourced past performance submissions be weighted equally? | Yes as long as the past performance is applicable to the task. | ||
| 135 | 2.0 QUOTATION CONTENT | Can the Government confirm Subfactor 3, Technical Capabilities Quote is a written response document? | Yes it is a written response. | ||
| 136 | 1.0 QUOTATION INSTRUCTIONS | The instructions state "The Offeror shall submit condensed, un-zipped files, attaching no more than two (2) files: its Non-PRICE quote (Vol. 1) and its PRICE quote (Vol. 2). " |
| In the table, Volume 1 is identified as "Introduction and Other Documentation Section". Volume 2 is identified as "Non-Price". Please confirm these are the intended volumes for the 9/24/25 submission, and that PRICE (Vol 3) is to be submitted at a later time. | Section Updated. See 0001. | ||||
| 137 | 2.0 QUOTATION CONTENT | Can the Government confirm that the submission on September 24th should be two unzipped files, one containing Volume 1 (Sections A, B, C) and Volume 2: Section D, Subfactor 1, Attachment B? | Correct. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .