Attachment A Seed to Sale Tracking System and Resources - Mandatory and Desirable Criterias final.xlsx
XLSX spreadsheet 47 KB Posted
- Solicitation number
- 23-440DFPR-SECRE-B-29251
- Issued by
- Cook County, Illinois
About this file
This document is the Attachment A Seed to Sale Tracking System and Resources - Mandatory and Desirable Criteria for the Joint Purchase Cannabis Seed to Sale Tracking System and Resources RFP issued by the State of Illinois. The RFP seeks a system that will track the full "seed to sale" product lifecycle for the cannabis industry, including functionality for state agencies, cannabis businesses, and consumers. Mandatory criteria include compliance with state laws, system integration and hosting requirements, and proposal submission details. Desirable criteria cover advanced search and alert features, inventory management, quality assurance, reporting, system administration, and integration with third-party systems.
The RFP does not provide pricing details or set-asides. The current environment and funding sources are not specified. The contract term is not explicitly stated, but the solution must be able to scale with program growth based on new regulatory requirements. Offerors must demonstrate their ability to provide the required functionality and begin contracted services upon execution of the contract.
View the file
Other files
Show all 18
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
Worksheet Information
STATE OF ILLINOIS CANNABIS SEED TO SALE
MANDATORY AND DESIRABLE CRITERIA ASSESSMENT
Worksheet Information
| Tabs in this Worksheet | |
| Worksheet Information | This tab includes the information about the contents of this worksheet. |
| Mandatory Criteria Tab | Contains Mandatory Criteria the Department has identified and their related data. |
| Desirable Criteria Tab | Contains Desirable Criteria the Department has identified and their related data. Offerors shall notify the Department of any Desirable Criteria Offeror believes should have been included and may add Functional Criteria thru their submitted narratives. Additional criteria should not be added to the existing list. The Department encourages innovation, this is one method for Offerors to highlight their proposed Solution's innovation. |
| Columns in the Mandatory Criteria Tab | |
| Criteria ID | Assigned # to track the Criteria. |
| Category | Assigned Primary Category for the Criteria. |
| Criteria Description | This is a description of the Criteria. |
| Notes | Additional information or links to external sites that have been referenced in the Criteria |
| Assessment | Offeror is requested to indicate its solution is in compliance with the criteria using 'Yes' or 'No'. The Offeror's narrative in both the Business and Technical Narrative sections should address the criteria in more detail. |
Yes/Can Comply = Proposed Solution currently provides the criteria, or can be modified to completely provide the criteria, and is considered as part of the Offeror's price proposal. The work for this criteria is already complete and functional in production.
No/Cannot Comply = Proposed Solution does not, or cannot, provide this criteria.
| Comments | The Offeror is requested to explain how the Offeror or its Solution will satisfy a given Technical Criteria. Offeror's comments will justify their assessments and may reference other narratives, plans, or documents to further justify their assessments and reduce response redundancy. |
| Columns in the Desirable Criteria Tab | |
| Criteria ID | Assigned # to track the Criteria. |
| Category | Assigned Primary Category for the Criteria. |
| Criteria Description | This is a description of the Criteria. |
| Role/User | The role or user this criteria applies to. Criteria can apply to 1 or more roles. |
| Assessment | The method of compliance selected by the Offeror indicates what type of work, if any, is requested to be completed for the Offeror’s proposal to meet a given criteria. |
(4) Out of the Box/No Code = The Offeror’s proposed Solution currently meets this criteria. The proposed Solution is prepackaged and already complete and functional.
(3) Configurable = The Offeror’s proposed Solution must be configured in order to meet this criteria. Tools within the application can be used to meet specific requirements without the use of custom code.
(2) 3rd Party Integration/API needed = The Offeror's proposed Solution needs to have a 3rd party integration in order to meet this criteria.
(1) Custom build/Code needed = The Offeror’s proposed Solution must use custom code in order to meet this criteria.
(0) Cannot Implement = The Offeror’s proposed Solution does not meet, or cannot meet, this criteria.
Comments The Offeror is requested to describe in detail how the Offeror or its Solution will satisfy a given Functional Criteria. Offeror's comments will justify their assessments and may reference other narratives, plans, or documents to further justify their assessments and reduce response redundancy.
DCFS PO19-164 CCWIS Attachment D Functional Criteria Page &P of &N
Mandatory Criteria
| MANDATORY CRITERIA | ASSESSMENT | ||||
| ID# | Category | Criteria Description | Notes | Assessment | Comments |
| M.1 | State Laws | Offeror shall partner with the State of IL to make all necessary changes to the final Solution to achieve CRTA compliance. Offeror certifies their Offer meets this requirement. | Cannabis Regulation and Tax Act | ||
| M.2 | State Laws | Offeror shall partner with the State of IL to make all necessary changes to the final Solution to achieve CMCP compliance. Offeror certifies their Offer meets this requirement. | Compassionate Use of Medical Cannabis Program Act | ||
| M.3 | System Integrator | Offeror shall be incorporated as a business in the United States. | |||
| M.4 | System Integrator | Offeror shall have a minimum of three (3) years of experience in the development, production deployment, and support of implementing a fully Offeror-hosted product inventory solution along with documenting all previous implementation efforts. | |||
| M.5 | S2S Product Lifecycle | Offeror shall provide a system that outlines the State of Illinois licensee's daily cannabis business operations (processes and transactions). | S2S system shall show the full 'seed to sale' product lifecycle starting with a cultivator (cultivation center or craft grow), processing (cultivation center or infuser), continuing through a QA lab for testing, transportation, and ending with the dispensary. | ||
| M.6 | State Regulators View | Offeror shall provide a system with the State of Illinois agencies' perspective on the daily cannabis business operations (processes and transactions) and system administration functions. | S2S System shall show the ease of finding products, auditing lifecycle trails, showing any ‘flags’ of abnormal transactions, products, or activities, initiating recalls, holds and quarantines, and conducting compliance reporting. It should also include regulatory features of alert notifications, account setup, room/product setup and edits, permissions, and log of data changes. | ||
| M.7 | Public-Facing Consumer Portal | Offeror shall provide a system with medical patient and consumer perspective of cannabis information. | S2S system shall show how a customer can view a product’s information, including lab results, THC/CBD levels, product types, harvest/manufacture dates, and other cannabis related information. It should also allow medical patients, caregivers, and medical dispensaries to view allowance remaining and purchase histories. | ||
| M.8 | Proposal Submission | Offeror shall submit a completed Attachment A Seed to Sale Tracking System and Resources – Mandatory and Desirable Criteria (D.2.1 and D.2.2) and return back in Packet 1. | Offeror shall comply with all Mandatories listed in the Mandatory Criteria tab to be considered a responsive and responsible offeror. Offeror shall fully complete all the Desirables listed in the Desirable Criteria tab. Offeror's comments in both tabs should provide details to justify their assessment, and may reference other narratives, plans, or documents to further justify their assessments and reduce response redundancy. | ||
| M.9 | Proposal Submission | Offeror shall comply with the content in IT Governance and Legal Requirements (D.2.11, Attachment E) and return back in Packet 1. | RFP Section D.2.11. - Information Technology (IT) Governance and Legal Requirements: The Awarded Vendor shall comply with all identified IT specifications listed in Attachment E Seed to Sale Tracking System and Resources – IT Governance and Legal Requirements. The documented specifications are State standard requirements for third-party solutions and were provided by the Department of Innovation and Technology (DoIT). The Offeror shall review, sign, and return the completed attachment back in Packet 1. |
tc={006C15AF-051B-4F72-B3C5-95EB08E2A510}: [Threaded comment]
Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924
Comment:
If a vendor failed to accidently sign this page, it isn't something that the Agency would like the option to cure instead of deeming NR?
Reply:
DoIT Enterprise and DoIT Legal recommended we maintain a strong stance on these IT governance and requirements.
| M.10 | System Integrator | Offeror's solution shall be capable of expansion to scale with program growth based on any newly required Administrative, Executive, Legislative, or Judicial mandates. | |
| M.11 | System Integrator | System shall be hosted on a cloud-based platform accessible through a web application using a W3C-compliant browser. | W3C-compliant browsers = Browsers must be compliant with the World Wide Web Consortium (W3C), in that they conform to the set-forth standards and should deliver a consistent web experience across browsers. Example: supported versions of Microsoft Edge and Google Chrome Version 97.0.4692.99 (Official Build) (64-bit) or higher. |
| M.12 | System Integrator | The Offeror must be able to begin the contracted services upon execution of the contract. |
https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=3992https://www.ilga.gov/legislation/ilcs/ilcs3.asp?ActID=3503&ChapterID=35 Desirable Criteria
| DESIRABLE CRITERIA | ASSESSMENT | ||||
| ID# | Category | Criteria Description | Role/User | Assessment | Comments |
| D.1 | Advanced Search | Describe Proposed solution's ability to perform advanced searches within the S2S solution. | All Users | ||
| D.2 | Alert | Describe Proposed solution's ability to flag issues at a particular location. | DFPR | ||
| D.3 | Alert | Describe Proposed solution's ability to provide a chatbot with businesses, regulators, and system vendor for quick validity checks on one-off unique inquiries that could be handled in real time. | All Users | ||
| D.4 | Alert | Describe Proposed solution's ability to receive real-time system push notifications for compliance changes or fraud detections from the State. | Dispensaries Cannabis Business | ||
| D.5 | Alert | Describe Proposed solution's ability to check real-time system credential status for patient and caregivers. | Dispensaries | ||
| D.6 | Alert | Describe Proposed solution's ability for all dispensary’s contacts on file to receive real-time system push notifications when the State places an administrative hold/quarantine order and to inform the contacts if product(s) is/are under investigation. | DFPR | ||
| D.7 | Alert | Describe Proposed solution's ability to send/receive general warning messages to/from the State. | All Users | ||
| D.8 | Alert | Describe Proposed solution's ability to receive alerts if pre-defined transaction thresholds are met. | DFPR | ||
| D.9 | Alert | Describe Proposed solution's ability to alert the cannabis businesses and the State when the QA result becomes available with a Pass/Fail status. | Labs | ||
| D.10 | Alert | Describe Proposed solution's ability to provide system notification when a request for QA testing was made. | Labs | ||
| D.11 | Alert | Describe Proposed solution's ability to receive a system notification when a mother plant of any product is quarantined or has an administrative hold. | All Users | ||
| D.12 | Alert | Describe Proposed solution's ability to provide alerts for any State updates or notices. | Labs | ||
| D.13 | Alert | Describe Proposed solution's ability to be alerted when there is a product or a strain being quarantined, recalled or on hold. | Cultivators |
DPH
ISP
| D.14 | Alert | Describe Proposed solution's ability to post messages to all users. | ISP |
| D.15 | Alert | Describe Proposed solution's ability to receive real-time notification when products are ready for transportation. | Transporters |
| D.16 | Alert | Describe Proposed solution's ability to receive real-time notification when there are any weather or road closure events | Transporters |
| D.17 | Compliance | Describe Proposed solution's ability to prohibit new genetic material from entering the system without State approval. | DFPR IDOA |
| D.18 | Compliance | Describe Proposed solution's ability to perform State-controlled administrative holds preventing products from being sold or transferred without removing the product from the inventory. | Cultivators |
DFPR
| D.19 | Compliance | Describe Proposed solution's ability to provide a workflow engine that will allow for approval process. | IDOA IDFPR |
| D.20 | Compliance | Describe Proposed solution's ability to ensure HIPAA Compliance is mandatory. | All Users |
| D.21 | Destruction | Describe Proposed solution's ability to choose a quantity of the item when destroying any product, so that the item can be destroyed individually rather than in a batch. | Dispensaries Cannabis Business |
Labs
| D.22 | Destruction | Describe Proposed solution's ability to track destructions including method of destruction and non-cannabis mixed material. | All Users |
| D.23 | Destruction | Describe Proposed solution's ability to keep the assigned/original lot number when a product destruction is executed | DFPR |
| D.24 | Destruction | Describe Proposed solution's ability to view the destruction of cannabis details executed by a licensee. | State Users |
| D.25 | Destruction | Describe Proposed solution's ability to schedule waste destruction and track destruction events. | Process Flow |
| D.26 | Destruction | Describe Proposed solution's ability to view the records for waste destruction. | Process Flow |
| D.27 | Destruction | Describe Proposed solution's ability to view and visit schedule waste destructions and view corresponding documentation and information for each scheduled event. | State Users |
| D.28 | Inventory | Describe Proposed solution's ability to create cultivation rooms. | Process Flow |
| D.29 | Inventory | Describe Proposed solution's ability to create inventory rooms. | Process Flow |
| D.30 | Inventory | Describe Proposed solution's ability to access any cultivation rooms. | Process Flow |
| D.31 | Inventory | Describe Proposed solution's ability to access any inventory rooms. | Process Flow |
| D.32 | Inventory | Describe Proposed solution's ability to sublot products. | Cultivators (Cannabis Growers) |
| D.33 | Inventory | Describe Proposed solution's ability to decipher between a plant that is frozen or not frozen. | Cultivators (Cannabis Growers) |
| D.34 | Inventory | Describe Proposed solution's ability to make inventory adjustments. | DOA |
| D.35 | Inventory | Describe Proposed solution's ability to create product in the system and track it through it's lifecycle. | All Users |
| D.36 | Inventory | Describe Proposed solution's ability to harvest plants and monitor the steps involved. Including but not limited to: mother plants, vegetative plants, flower plants, harvested batches, cannabis waste products, extracted products and packaged products. | Cultivators (Cannabis Growers) |
| D.37 | Inventory | Describe Proposed solution's ability to convert products and track that process. | Cultivators (Cannabis Business') |
| D.38 | Inventory | Describe Proposed solution's ability to quarantine products and track that process. | Cultivators Dispensaries |
| D.39 | Inventory | Describe Proposed solution's ability to stop the product/lot/batch from moving if it's in quarantine, under administrative hold, or recalled. | Cultivators (Cannabis Growers) |
| D.40 | Inventory | Describe Proposed solution's ability to destroy products and track that process. | Cultivators |
| D.41 | Inventory | Describe Proposed solution's ability to batch/lot manufacture products. | Cultivators |
| D.42 | Inventory | Describe Proposed solution's ability to create strains. | Process Flow |
| D.43 | Inventory | Describe Proposed solution's ability to create a product inventory. | Process Flow |
| D.44 | Inventory | Describe Proposed solution's ability to create plants. | Process Flow |
| D.45 | Inventory | Describe Proposed solution's ability to record plant and harvest curing. | Process Flow |
| D.46 | Inventory | Describe Proposed solution's ability to create lot and sublots. | Process Flow |
| D.47 | Inventory | Describe Proposed solution's ability to create extracts. | Process Flow |
| D.48 | Inventory | Describe Proposed solution's ability to create infused product and record the details in the system. | Process Flow |
| D.49 | Inventory | Describe Proposed solution's ability to return products easily, more specifically with a auto-generated new manifest for returns. | Cultivators |
| D.50 | Inventory | Describe Proposed solution's ability for rejections, transfers and/or quarantines to have their own business process. | Cultivators |
| D.51 | Inventory | Describe Proposed solution's ability to create combined conversion types, with multiple conversion types such as premium, multiple mixed strain, etc. | Cultivators |
| D.52 | Inventory | Describe Proposed solution's ability to do State directed QA recalls, internal QA recall and any voluntary recalls. | Cultivators |
QA Lab
| D.53 | Inventory | Describe Proposed solution's ability to register products in the system. | Cultivators |
| D.54 | Inventory | Describe Proposed solution's ability for my extraction team to be able to sub-categorize products. | Cultivators |
| D.55 | Inventory | Describe Proposed solution's ability to edit the harvest birthdate if it is not todays date with strict controls for auditing purposes and to limit inaccurate adjustments. | Cultivators |
| D.56 | Inventory | Describe Proposed solution's ability to adjust the weight of flower lots based on inventory audits with strict controls and State approval. | Cultivators |
| D.57 | Inventory | Describe Proposed solution's ability to scan a barcode for each grow room, table, plants, etc. so that it makes it easier to move larger bulk items. | Cultivators |
| D.58 | Inventory | Describe Proposed solution's ability to fill out a product registration form. | DOA |
| D.59 | Inventory | Describe Proposed solution's ability to upload or take a picture of the label. | DOA |
| D.60 | Inventory | Describe Proposed solution's ability to distinguish between a strain and a product. | DOA |
| D.61 | Inventory | Describe Proposed solution's ability to review, approve, deny, and reject product registrations. | DOA |
| D.62 | Inventory | Describe Proposed solution's ability to enter comments related to a product registration. | DOA |
| D.63 | Inventory | Describe Proposed solution's ability to flag registrations that have the certain ingredients in them (such as Delta 8). | DOA |
| D.64 | Inventory | Describe Proposed solution's ability to receive automated notifications that update me on the status of my product registration. | DOA |
| D.65 | Inventory | Describe Proposed solution's ability if certain fields are changed on a product registration then it will reroute to a new workflow for a new application with a new fee. | DOA |
| D.66 | Inventory | Describe Proposed solution's ability to do multiple registrations within 1 transaction so I don't have to keep going back in and re-entering. | DOA |
| D.67 | Inventory | Describe Proposed solution's ability to calculate the deduction amount accurately from patient limit in real-time. |
| Dispensaries | |||
| D.68 | Inventory | Describe Proposed solution's ability to apply the same-site limits to recreational users, similar to as I do for medical patients with larger allotments. | Dispensaries |
| D.69 | Inventory | Describe Proposed solution's ability to have these data fields in the system for a product: |
Batch numbers, QA results, expiration date, harvest date, package date, product names and details, Strain names and current inventory, product pricing and transfers, real-time allotment taken up per item (for medical purchases).
| Dispensaries | ||||
| D.70 | Inventory | Describe Proposed solution's ability to see the test results for all types of cannabinoids (CNB, CBC, CBG, etc.) not limited to THC and CBD if available. | Dispensaries | |
| D.71 | Inventory | Describe Proposed solution's ability to track product transfers in the following stages: | ||
| (1) in possession of the cultivation center/craft grower and transfer to (2) the transport organization and from the transport organization to (3) the dispensary or (4) the lab/other authorized person. | All Users | |||
| D.72 | Inventory | Describe Proposed solution's ability to separate storage “rooms” within a cannabis business. | DFPR | |
| D.73 | Inventory | Describe Proposed solution's ability to track cannabis additives to cannabis products. | DFPR | |
| D.74 | Inventory | Describe Proposed solution's ability to track nutrients, pesticides and fungicides that are used. | DFPR | |
| D.75 | Inventory | Describe Proposed solution's ability to have a method of accounting for moisture loss of flower or concentrate, and any other intermediary or end products. | DFPR | |
| D.76 | Inventory | Describe Proposed solution's ability to create QR codes on product labels with following data points included: | ||
| full test results, harvest date, package date, additives, use by date and shipment dates. | DFPR | |||
| D.77 | Inventory | Describe Proposed solution's ability to print labels with all State-required information. | DFPR | |
| D.78 | Inventory | Describe Proposed solution's ability to display “usable cannabis” conversion on the product label. | DFPR | |
| D.79 | Inventory | Describe Proposed solution's ability to perform “usable cannabis” conversion for manufacturers. | DFPR | |
| D.80 | Inventory | Describe Proposed solution's ability to have clear definition for column headings and provide explanations on the data elements. | All Users | |
| D.81 | Inventory | Describe Proposed solution's ability to measure product testing and sales by usable weight rather than "quantity." | DFPR | |
| D.82 | Inventory | Describe Proposed solution's ability to create additional product categories. | State Users | |
| D.83 | Inventory | Describe Proposed solution's ability to manage and track product returns. | DFPR | |
| D.84 | Inventory | Describe Proposed solution's ability to view and track a product sample throughout its' lifecycle from the original flower lot to distillate. | Labs | |
| D.85 | Inventory | Describe Proposed solution's ability to have a complete set of data elements tested for all product types. | Labs |
DFPR
| D.86 | Inventory | Describe Proposed solution's ability to view product quarantine information. | ISP |
| D.87 | Inventory | Describe Proposed solution's ability to track lot and sublot history. | ISP |
| D.88 | Inventory | Describe Proposed solution's ability to view all sales figures/prices, date of sale, and location of sale. | DOR |
| D.89 | Inventory | Describe Proposed solution's ability to view tax rates and taxes collected on each sale. | DOR |
DFPR
| D.90 | Inventory | Describe Proposed solution's ability to view the purchases of cannabis to and from Cultivators. | DOR |
| D.91 | Inventory | Describe Proposed solution's ability to see the THC% and adjusted THC% associated with cannabis products. | DOR |
| D.92 | Inventory | Describe Proposed solution's ability to see all product details and transaction history. | DOR |
| D.93 | Inventory | Describe Proposed solution's ability to collect the waste. | Process Flow |
| D.94 | Inventory | Describe Proposed solution's ability to transfer QA results, package dates, and harvest dates to the label-making functionality, so that I can reproduce a compliance label after a sublot occurs on the retail side. | Dispensaries |
| D.95 | Inventory | Describe Proposed solution's ability to view real-time QA Lab results. | All Users |
| D.96 | Inventory | Describe Proposed solution's ability to set permissions for groups of users to access certain QA Lab results. | All Users |
| D.97 | Inventory | Describe Proposed solution's ability to view test results when they become live in the system. | DFPR |
| D.98 | Inventory | Describe Proposed solution's ability for test results to be carried along with the product all the way to sales. | DFPR |
| D.99 | Inventory | Describe Proposed solution's ability to initiate inventory transfer. | Process Flow |
| D.100 | Inventory | Describe Proposed solution's ability to receive inventory transfer. | Process Flow |
| D.101 | Inventory | Describe Proposed solution's ability to accept or reject the product. | Process Flow |
| D.102 | Inventory | Describe Proposed solution's ability to either fully or partially reject the product. | Process Flow |
| D.103 | Inventory | Describe Proposed solution's ability to generate to a separation of batches which initiates a new barcode to be designated for the weight/quantity returned to the originating location, once it's accepted. | Process Flow |
| D.104 | Inventory | Describe Proposed solution's ability to create and edit a manifest in a downloadable and printable format. | All Users |
| D.105 | Inventory | Describe Proposed solution's ability to populate multiple drivers/passengers on the manifest as required by legislation, and auto populate most data elements that are already in the system. | All Users |
| D.106 | Inventory | Describe Proposed solution's ability to place and manage large orders. | Dispensaries |
| D.107 | Inventory | Describe Proposed solution's ability to manage and fulfill larger orders. | Cultivators |
| D.108 | Inventory | Describe Proposed solution's ability to register my companies vehicle and receive a printable certificate to put in the vehicle. | Cannabis Business Transporters |
| D.109 | Inventory | Describe Proposed solution's ability to have the vehicle available in the dropdown for the manifest in order to chose my transporting vehicle. | DOA |
| D.110 | Inventory | Describe Proposed solution's ability to see a list of all my registered vehicles. | DOA Transporter |
| D.111 | Inventory | Describe Proposed solution's ability to create, update, edit and delete vehicle registration information. | DOA Transporter |
| D.112 | Inventory | Describe Proposed solution's ability to provide an automated email letting me know the vehicle has been registered in the solution. | DOA Transporter |
| D.113 | Inventory | Describe Proposed solution's ability to provide an automated email yearly to remind me to update all my vehicles in the solution. | DOA Transporter |
| D.114 | Inventory | Describe Proposed solution's ability to view and download product manifest in the system. | Labs |
| D.115 | Inventory | Describe Proposed solution's ability to have all required information on the manifest to follow ISO and State compliance regulations. | Labs |
| D.116 | Inventory | Describe Proposed solution's ability to view, search and run report on manifest amendments by date or by facility. | ISP |
| D.117 | Inventory | Describe Proposed solution's ability to view real-time data on the transportation manifest. | ISP |
| D.118 | Inventory | Describe Proposed solution's ability to make non-material amendments on the manifest prior to the shipment, without voiding it and with a thorough audit trail. | ISP |
DFPR Cultivators Dispensaries
| D.119 | Inventory | Describe Proposed solution's ability to pull following data elements from the system: Name of Delivery Team, Receiving and Sending Facilities/Parties, Beginning and Ending Time of Delivery, Actual Route Taken, and Package Details and Photos. | Transporters |
| D.120 | Inventory | Describe Proposed solution's ability for the system to automatically, in real-time, acknowledge when a package is picked up and delivered | Transporters |
| D.121 | Inventory | Describe Proposed solution's ability for the system to have scannable packaging labels that include weight and dimension information | Transporters |
| D.122 | Inventory | Describe Proposed solution's ability to enter in route details to and from each business locations in a manifest. | Transporters |
| D.123 | Inventory | Describe Proposed solution's ability for the system to track location of vehicles in route through GPS. | Transporters |
| D.124 | Inventory | Describe Proposed solution's ability to allow dispensary-to-dispensary transfers without issuing a new tracking number. | DFPR |
| D.125 | Inventory | Describe Proposed solution's ability to identify the ownership of a product when it is in transit. | DFPR |
| D.126 | Inventory | Describe Proposed solution's ability to record the details of the sales. | Process Flow |
| D.127 | Inventory | Describe Proposed solution's ability to track or "flag" buyer's daily allowance for recreational usage. | Dispensaries |
| D.128 | Inventory | Describe Proposed solution's ability to have these data fields in the system for Sales - Sales data, and Profit percentages; transaction history and taxes. | Dispensaries |
| D.129 | Inventory | Describe Proposed solution's ability to allow dispensaries or other licensed entities to add recalled or returned products back into their inventory before destruction. | DFPR |
| D.130 | Inventory | Describe Proposed solution's ability for the user interface to be split up by phase of Seed to Sale. For example, pre harvest and post harvest- having things categorized out 1) Grow house (cultivation), 2) Harvest, 3) Post Harvesting (processing) | Cannabis Business' |
| D.131 | Inventory | Describe Proposed solution's ability to have a method which doesn't require log-in to look up the product information, test result and harvest date using a unique product identifier (a 16-digit product number or QR code). | DFPR |
| D.132 | Inventory | Describe Proposed solution's ability to create a SMART unique ID so that it is intuitive and searchable. | Cultivators |
| D.133 | Inventory | Describe Proposed solution's ability to use language that reflects the common terminology used in the State. | DFPR |
| D.134 | Inventory | Describe Proposed solution's ability to track hemp as a substitute for cannabis. | Community Colleges |
| D.135 | Inventory | Describe Proposed solution's ability to request department approval for remediation of lots with failed test results and to permit, with approval, transfer/sale to another cannabis entity. | Cultivators |
| D.136 | Inventory | Describe Proposed solution's ability to enter and track inventory for purposes of sale and compliance. | Cannabis Business Dispensaries |
| D.137 | Patient | Describe Proposed solution's ability to look up Patients and Caregiver in the system by their IDs. | Process Flow |
| D.138 | Patient | Describe Proposed solution's ability to view medical patient purchasing history and to generate corresponding report. | Dispensaries |
DPH
| D.139 | Patient | Describe Proposed solution's ability to have these data fields in the system for Customer - Member status, revoked patient cards, caregiver status (active/inactive with alert), and caregiver/patient info. | Dispensaries |
| D.140 | Patient | Describe Proposed solution's ability to accept multiple caregivers being linked to one patient. | Dispensaries |
| D.141 | Patient | Describe Proposed solution's ability to look up and verify medical patient's purchasing limits in real-time. | Dispensaries |
DFPR
DPH
| D.142 | Patient | Describe Proposed solution's ability to look up their own remaining allotments. | DFPR |
| D.143 | Patient | Describe Proposed solution's ability to view all medical patients accounts and data. | DPH |
ISP
| D.144 | Patient | Describe Proposed solution's ability to export medical patients' information to Excel spreadsheets. | DPH |
| D.145 | QA | Describe Proposed solution's ability to create QA samples for intermediary and end-consumer products. | Process Flow |
| D.146 | QA | Describe Proposed solution's ability to create QA samples for the infused product. | Process Flow |
| D.147 | QA | Describe Proposed solution's ability to create QA Samples in a batch for testing. | Process Flow |
| D.148 | QA | Describe Proposed solution's ability to view and search all QA test result by the Batch with Sample IDs. | Process Flow |
| D.149 | QA | Describe Proposed solution's ability to have detailed data fields on the test result page following the State's and ISO compliances. | Labs |
| D.150 | QA | Describe Proposed solution's ability to pass/fail the sample and the specific cannabinoid elements in a sample tested. | Labs |
| D.151 | QA | Describe Proposed solution's ability to choose different types of QA testing (i.e. a testing matrix) with the corresponding data elements available for requested sample testing. | Cannabis Business |
| D.152 | QA | Describe Proposed solution's ability to view, sort and search previous test results. | Labs |
| D.153 | QA | Describe Proposed solution's ability to see a listing of samples requested testing assigned to my lab. | Labs |
| D.154 | QA | Describe Proposed solution's ability to search modified test results by product sample or batch #. | Labs |
| D.155 | QA | Describe Proposed solution's ability to modify QA test results and capture what has been modified and by whom and when. | Labs |
| D.156 | QA | Describe Proposed solution's ability to export current and historical QA test results in a spreadsheet. | Labs |
| D.157 | QA | Describe Proposed solution's ability to enter and report detailed data on QA testing broken down by analyte, rather than by total. | Labs |
| D.158 | QA | Describe Proposed solution's ability to download and upload a full Certificate of Analysis (COA) once testing is complete. | Labs |
| D.159 | Reporting | Describe Proposed solution's ability to report sales on all products. | Process Flow |
| D.160 | Reporting | Describe Proposed solution's ability to report tax obligations on all sales. | Process Flow |
| D.161 | Reporting | Describe Proposed solution's ability to access inventory/plant counts in one room or across a set of locations. | ISP |
| D.162 | Reporting | Describe Proposed solution's ability to view 40% rule violations (410 ILCS 705/(p)(5) production entity “shall not be more than 40% of the total inventory available for sale” at one dispensary). | ISP |
| D.163 | Reporting | Describe Proposed solution's ability to run reports based on my product registrations. | DOA |
| D.164 | Reporting | Describe Proposed solution's ability to run reports for my inspections. | DOA |
| D.165 | Reporting | Describe Proposed solution's ability to separate inventory reports by bulk storage and sales floor rooms. | DFPR |
| D.166 | Reporting | Describe Proposed solution's ability to run scheduled reports. | All Users |
| D.167 | Reporting | Describe Proposed solution's ability to email reports to specific users both internal to the S2S system and external. | All Users |
| D.168 | Reporting | Describe Proposed solution's ability to pull auditing reports. | All Users |
| D.169 | Reporting | Describe Proposed solution's ability to provide a reporting module so that I can produce compliance reporting. | DOA |
| D.170 | Reporting | Describe Proposed solution's ability generate visual representations of data in the system. | All Users |
| D.171 | Reporting | Describe Proposed solution's ability to generate and export new/customized reports that can be used for website and other contents. | DFPR |
| D.172 | Reporting | Describe Proposed solution's ability to select subsets of data to include in reports (i.e., some dispensaries or cultivation centers selected by region). | All Users |
| D.173 | Reporting | Describe Proposed solution's ability to run audit trail/user history report to trace user activities. | All Users |
| D.174 | Reporting | Describe Proposed solution's ability to provide a description on every report. | All users |
| D.175 | Reporting | Describe Proposed solution's ability to provide a reporting database that is a direct copy of production in order to run reports off of without impairing the production environment. | All Users |
| D.176 | Reporting | Describe Proposed solution's ability to authorize additional users to access certain reports. | |
| D.177 | Reporting | Describe Proposed solution's ability to generate reports based on specific products, product histories, and customize the export fields for external analysis--including in Excel or CSV formats. | All Users |
| D.178 | Reporting | Describe Proposed solution's ability to generate a report on product returns. | DOR |
| D.179 | Reporting | Describe Proposed solution's ability to create reports. | All Users |
| D.180 | Reporting | Describe Proposed solution's ability to execute and export ad-hoc reports related to transportation information in the system. | Transporters |
| D.181 | Reporting | Describe Proposed solution's ability to execute and export ad-hoc reports related to my business and/or company. | All Users |
| D.182 | Reporting | Describe Proposed solution's ability to execute and export reports related to lab test containing historical data. | Labs |
| D.183 | Reporting | Describe Proposed solution's ability to execute and export reports containing historical data. | All Users |
| D.184 | System Administration | Describe Proposed solution's ability to track admin user activity and credentials who completed that task instead of the user that is logged in. | Dispensaries |
| D.185 | System Administration | Describe Proposed solution's ability to have a data dictionary providing explanation on the data elements in the system. | All Users |
| D.186 | System Administration | Describe Proposed solution's ability to add permissioning to a new employee. | Process Flow |
| D.187 | System Administration | Describe Proposed solution's ability to add cultivation centers, craft growers, infusers, vendors, and retailers. | Process Flow |
| D.188 | System Administration | Describe Proposed solution's ability to make users inactive in the system. | All Users |
| D.189 | System Administration | Describe Proposed solution's ability to set up role-based permission and configuration. | All users |
| D.190 | System Administration | Describe Proposed solution's ability to have and configure dashboards within the system. | All users |
| D.191 | System Administration | Describe Proposed solution's ability to view employee data. | ISP |
| D.192 | System Administration | Describe Proposed solution's ability of technical infrastructure to accommodate future industry growth. | Dispensaries |
| D.193 | System Administration | Describe Proposed solution's ability to provide a low code/no code solution. | DFPR |
| D.194 | System Administration | Describe Proposed solution's ability to access the S2S system both on Mac and Windows/PC. | DFPR |
| D.195 | System Administration | Describe Proposed solution's ability to work as partner to continuously develop new features and reports as State's compliances and rules change. | DFPR |
| D.196 | System Administration | Describe Proposed solution's ability to adhere to ADA Compliance rules. | All Users |
| D.197 | System Administration | Describe Proposed solution's ability to use the solution on mobile devices such as a cell phone or tablet so that I can do work in the field. | All Users |
| D.198 | System Administration | Describe Proposed solution's ability to be accessible 24 hours a day, 7 days a week | All Users |
| D.199 | System Integration | Describe Proposed solution's ability to integrate with IDOA product registration solution for purposes of processing approval workflows with bi-directional data exchanges. | Cultivators |
| D.200 | System Integration | Describe Proposed solution's ability to choose companywide region and operate at all or selected store level with one log-in if I am a Multi State Operating (MSO) dispensary. | Dispensaries |
| D.201 | System Integration | Describe Proposed solution's ability to send and receive (bulk) data from S2S system to third-party systems in real time. | All Users |
| D.202 | System Integration | Describe Proposed solution's ability to have an API that allows for the addition of new cannabis patients to be updated in real-time on third-party POS systems used by licensees. | DFPR |
DPH
| D.203 | System Integration | Describe Proposed solution's ability to integrate to send/receive data with regulatory case management and enforcement systems. | DFPR |
| D.204 | System Integration | Describe Proposed solution's ability to have real-time API integration with third-party lab systems | Labs |
DPH
| D.205 | System Integration | Describe Proposed solution's ability to upload QA test results in the system or via real-time interfaces from an external file source. | Labs |
| D.206 | System Integration | Describe Proposed solution's ability to provide IDOR's tax account ID to be integrated with the license # in the system. | DOR |
| D.207 | System Integration | Describe Proposed solution's ability to integrate with a payment vendor for multiple payment types. | All Users |
| D.208 | System Integration | Describe Proposed solution's ability to integrate with the IDOA credentialing solution. | Dispensaries DOA |
| D.209 | System Integration | Describe Proposed solution's ability to have real-time synchronization with third-party POS systems to avoid duplicate sales transactions and other errors. | All Users |
| D.210 | System Integration | Describe Proposed solution's ability to have robust API or integration toolkit to allow a better integration with outside systems and 3rd party tools. | All Users |
| D.211 | System Integration | Describe Proposed solution's ability to integrate with the agencies credentialing solution so I know the agents and patients are credentialed. | IDFPR IDOA IDPH |
| D.212 | Technical Support | Describe Proposed solution's ability to receive release notes from the Offeror prior to the release. | All Users |
| D.213 | Technical Support | Describe Proposed solution's ability to be notified in advance (at least 24 hours) when system upgrade requires a downtime. | All Users |
| D.214 | Technical Support | Describe Proposed solution's ability to have defined SLAs i.e. Level 1, 2, 3, etc. coverage within the contract and are in compliance with DoIT security in order to guide the help desk tiered support. | All Users |
| D.215 | Technical Support | Describe Proposed solution's ability to provide easy access to a help desk within the S2S solution that is available 24 hours/day. | All Users |
| D.216 | Training | Describe Proposed solution's ability to provide a (specific to the State solution) user guide for the S2S solution easily accessible in the solution. | All Users |
| D.217 | Training | Describe Proposed solution's ability to provide a sandbox environment to test out new updates as well as provide training on the solution. | All Users |
| D.218 | Training | Describe Proposed solution's ability to have in-depth live or recorded trainings to be made available to the users regarding solution functionality. | All Users |
| D.219 | Training | Describe Proposed solution's ability to have specific training on auditing scenarios for DOR. | DOR |
| D.220 | Training | Describe Proposed solution's ability for Community College instructors and students to set permissions to the relevant parts of the training environment solution as it relates to their community college partnerships. | Community Colleges |
Data
| Desirable Assessment | Mandatory Assessment |
| 4-Out of the box/No Code | Yes/Can Comply |
| 3-Configurable | No/Cannot Comply |
| 2-Third Party Integration/API Needed | |
| 1-Custom build/Code Needed | |
| 0-Cannot Implement |
File details come from the government source that posted it. Updated .