Skip to content

Business Needs and User Stories for Cannabis Track and Trace

Notifications You must be signed in to change notification settings

CDTProcurement/trackandtrace

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 

Repository files navigation

California Track and Trace System Procurement

In partnership with the California Department of Food and Agriculture and other state agency partners, the California Department of Technology will be conducting a procurement to acquire a system to "Track and Trace" cannabis products within California.

If you have comments or questions please submit a Github Issue by noon on 12/23/2016.

Administrative Requirements

Business Needs and User Stories for Cannabis Track and Trace System

Below, the State has defined preliminary business needs and user stories for the Cannabis Track and Trace System.

###Licensee As a, ###1. I would like to be notified of recalls. ###2. I would like to obtain / create unique Identifier & Tags (Tag ID) ###3. I would like to document these events; ###a. Tagging, labeling, processing, manufacturing, packaging and repackaging events ###2. I would like to ship product. ###3. I would like to label shipments of products. ###4. I would like to create, update, print & receive shipping manifest. ###5. I would like to report cultivation details (plant and batch) ###6. I would like to report product information ###7. I would like to report cannabis plants by type, strain and name. ###8. I would like to track and report cloned, germinating and mother cannabis plants by count, type, strain ###9. I would like to enter lab test report ###10. I would like to report losses and product changes ###11. I would like to report irregularities ###12. I would like to grandfather plants through lifecycle stages ###13. I would like to track and report on cloned and germinating plants sold to licensed dispensaries ###14. I would like to handle multiple drivers on transport ###15. I would like to track and report inventory, purchases, sales and ending inventory on a real-time or daily basis ###16. I would like to track and report inventory loss from plant death, failure to grow, theft, etc.) ###17. I would like to track and report all disposal of cannabis and cannabis products. ###18. I would like to track cannabis plants through the entire cultivation lifecycle. ###19. I would like to track all materials and ingredients used during the cultivation lifecycle (e.g., soil, growth regulators, pesticides, etc.) ###20. I would like to track accountability for all aspects of the cannabis plant including trim, leaves, flowers, stems, stalks, etc. ###21. I would like record transfers of small amounts of cannabis and cannabis products to a laboratory for testing. ###22. I would like a secure web service API for integrating my 3rd party information system. ###23. I would like to upload data into the system from my 3rd party information system ###24. I would like the ability to verify and correct uploaded data before it is posted to the system. ###25. I would like the correct/amend/supplement posted data and information. ###26. I would like a training and testing program to ensure I / my staff know how to correctly use the system. ###27. I would like to document receipt of a shipment from another licensee. ###28. I would like to integrate, in real-time, with hardware / equipment used to weigh cannabis and cannabis products, scanners, printers.

###Law Enforcement Officer As a, ###1. I would like to retrieve shipping manifest. ###2. I would like to verify shipment and associated licensee information. ###3. I would like to notify Licensor of infraction ###4. I would like to search Track & Trace data. ###5. I would like to handle destruction of products and tags/ids upon arrests / confiscations. ###6. I would like to verify transporter has: ###a. Manifest, cannabis license, company security badge identifying the employee works for the licensee, driver’s license Cannabis License Expiration Date, Cannabis License Issue Date.

###Regulator As a, ###1. I would like unique identifiers to be created and issued for each cannabis plant. ###2. I would like unique identifiers that can be attached to the base of each cannabis plant. ###3. I would like unique identifiers to be created and issued for lots of cannabis plants ###4. I would like to perform analytics, program & management reporting. ###5. I would like ad-hoc reporting capabilities for all tables and all data within the system. ###6. I would like to export/display any report in multiple formats (MS Excel, PDF, CSV, HTML, text files, etc.) ###7. I would like to download datasets and reports. ###8. I would like the ability to configure the system in response to any address any changes to regulations or statutes or to address enforcement needs that arise. ###9. I would like to have to the information necessary to assess, levy, collect and track cultivation and excise taxes: ###a. In a way that minimizes manual labor. ###b. Tag or mark to identify when/if, by licensee taxes paid. ###c. Identify when tagged or marked product changes possession (i.e., sale from cultivator to distributor, or sale from distributor to manufacturer) ###d. Subsequently tag or mark previously tagged or marked product when it changes composition, i.e. leaves turned into extract, or extract turned into edible. ###e. Subsequently tag or mark previously tagged or marked product when it changes packaging or size, i.e. 1 lb bag broken down into 16 one ounce bags. ###f. Traceable back to origin of harvest. ###10. I would like track if product is returned, and be able to show the adjustment in the track and trace system. ###11. I would like to easily verify (i.e. via physical inspection; perhaps via visual inspection) that taxes have been paid/levied on a product. ###12. I would like an audit log for historical purposes, data analysis and/or data restoration. ###13. I would like the system to track all changes in the system including adds, updates, and deletes by any registered system user and the associated date/time stamps. ###14. I would like to suspend access to the system for a licensee and all associated users when the applicable license status is not active. ###15. I would like the ability to configure system user access to functions, data and reports appropriate to the individual and their user group. ###16. I would like to prevent the creation of a shipping manifest when a destination address is outside of California. ###17. I would like a means to determine the validity of a hardcopy shipping manifest produced by the system.
###18. I would like to send specified data elements on demand or as a scheduled job in a specified timeframe, to an external system in a defined format(s). ###19. I would like the capability to grant security access to the system / data elements in a granular manner. ###20. I would like to track and monitor inventory discrepancies for any transfer of inventory between licensees. ###21. I would like to maintain a record of all electronic shipping manifests. ###22. I would like to access to all electronic shipping manifests.

###Inspector/Investigator As an, ###1. I would like to differentiate function and purpose for an inspection versus an investigation ###2. I would like to enter data associated with a site inspection while in the field/working remotely. ###3. I would like a secure, web-based application which inspectors may use to access and record data. ###4. I would like to retrieve data for site inspection. ###5. I would like to receive automated alerts on track and trace irregularities (reuse of unique identifiers, identifiers don’t match product/packaging, product designated as recalled, destroyed or stolen). ###6. I would like to perform site inspection. ###7. I would like to record data and information associated with a site inspection ###8. I would like to track, monitor and report irregularities in reported data based upon defined business rules ###9. I would like to be notified of irregularities or violated thresholds (business rules). ###a. I.e. “smart inspections” ###10. I would like to be able to configure the tax events in the supply chain – track and trace system. ###11. I would like to track and monitor all movement/transfer of cannabis and cannabis products on a licensed cultivator’s premises during the cultivation lifecycle (e.g., germination, vegetative growth, and flowering) and during the harvesting process (e.g., drying, trimming, storage) for each harvest batch of cannabis. ###12. I would like to track unique identifiers issued to a licensee. ###13. I would like to track the agent receiving unique identifiers issued to a licensee. ###14. I would like a unique identifier that provides safeguards against creation of fraudulent identifiers and helps to limit diversion of unique identifiers to unlicensed individuals. ###15. I would like to conduct a periodic inventory reconciliation of a licensee. ###16. I would like to inspect and input information regarding outbound and inbound shipments of cannabis and cannabis products for any licensee.

###Government Stakeholder As a, ###1. I would like to access activity records ###2. I would like to search Track & Trace data. ###3. I would like to track lot and batch information through the entire supply chain and cross-reference and analyze data between and across all licensees. ###4. I would like to ensure that my interests, goals, and objectives are represented in operations. ###5. I would like to run reports; e.g. ###a. “Total” summary by license: ###i. Manufactured, grown, moving through the system; i.e. what the system is producing. ###b. How much is grown and moved through the system. ###c. # Of cultivators. ###d. In a way that allows to divide by license type. ###e. Ad hoc (various); per field (location); per global (location); per plant; per batch, etc. ###f. How much water used per crop. ###g. Site visits. ###h. Defined relationship between tags & license types and cross reference reports by license type. #Tying #associating license number to unique id. ###i. #Tying #associating transporter license number to manifest to driver license number . ###j. Number of plants by cultivator. ###k. What is moving through the system? ###l. Reports by Licensee. ###m. How much is being manufactured? ###n. How much is being grown? ###o. Cultivators using ground water, surface water, etc.

###Tester or Licensor As a , ###1. I would like to document a product recall.

###Licensor As a, ###1. I would like to verify product quality. ###2. I would like to do a product recall. ###3. I would like to be notified of irregularities or violated thresholds (business rules). ###4. I would like to handle cultivator nurseries. (Final place for flowering); ###a. Aka. I would like to handle hybridizing Research and Development (R&D) ###5. I would like to grandfather plants through lifecycle stages ###6. I would like to handle returns. ###7. I would like to administer the concept of - >> sell by/expiration date. ###8. I would like to integrate with existing industry systems / processes. ###6. I would like the ability to create, update delete data as needed ###9. I would like to audit licensees and their products; ###a. E.g. Distributor ###i. Product’s Cultivator’s name ###ii. Transporter(s) and license number(s) ###iii. Type of goods received ###iv. Type by weight and count ###v. Date of receipt ###vi. Details of dispensary ###vii. Transportation to Dispensary details including vehicle and license number ###viii. Samples given to Dispensary ###b. E.g. Dispensary ###i. Distributor and Transporter details ###ii. Delivery details

###Tester As a, ###1. I would like to document test results.

###Tester, Distributor, Manufacture, Transporter, Dispenser As a, ###1. I would like to receive and verify receipt of product.

###Bureau of Medical Cannabis Regulation (BMCR) Track and Trace Requirements

###Distributor Requirements A distributor shall enter the following events into the track-and-trace database: ###(a) Receipt of goods from cultivator or manufacturer. ###(1) Enter the following information: ###(A) Cultivator’s or manufacturer’s name and license number; ###(B) Name of licensee who transported the goods and license number; ###(C) Type of goods received; ###(D) Amount received, by weight or count; ###(E) Best-by, sell-by, or expiration date of the batch; ###(F) Party who holds title to the goods; ###(G) The date of receipt of goods; ###(H) The unique identifiers associated with the goods; and ###(I) Other information required elsewhere by the Bureau.

###(b) Sample taken by testing laboratory. ###(1) Enter the following information: ###(A) The testing laboratory’s name and license number; ###(B) The name of the lab agent who obtained the sample; ###(C) Total weight of the sample obtained; ###(D) The date the sample was obtained; and ###(E) Other information required by the Bureau.

###(c) Sale to dispensary. ###(1) If a distributor purchases medical cannabis, the distributor shall enter the following information: ###(A) Name of dispensary licensee with whom the distributor contracted for sale and dispensary’s license number; ###(B) The date of the contract for sale; ###(C) The type of goods contracted for sale; ###(D) The amount of goods contracted for sale, by weight or count; ###(E) The date title passed to the dispensary; and ###(F) Other information required by the Bureau.

###(d) Transportation to dispensary. ###(1) If the distributor uses his or her transporter license to transport the medical cannabis to a dispensary, the distributor shall enter the following information: ###(A) Transportation license number; ###(B) Amount of goods transported, by weight or count; ###(C) Vehicle license plate number used for transportation; ###(D) Date of transport; and ###(E) Other information required by the Bureau.

###(e) Provision of a sample given to a dispensary or manufacturer for business purposes under section [11]. ###(1) Enter the following information: ###(A) Licensee to whom the sample was provided and license number; ###(B) Type of sample provided; ###(C) Weight of sample provided; ###(D) Date sample was provided; and ###(E) Other information required by the Bureau.

###Dispensary Requirements A dispensary shall enter the following events into the track-and-trace database: ###(a) Receipt of goods from a distributor. ###(1) Enter the following information: ###(A) Distributor’s name and license number; ###(B) Name of licensee who transported the goods and license number; ###(C) Type of goods received; ###(D) Amount received, by weight or count; ###(E) Best-by, sell-by, or expiration date of each product received; ###(F) The date of receipt of goods; ###(G) The unique identifiers associated with the goods received; and ###(I) Other information required by the Bureau.

###(b) Sale of goods to a qualified patient or primary caregiver ###(1) Enter the following information: ###(A) The name of the licensed dispensary employee who processed the sale; ###(B) The name or patient identification number of the qualified patient or primary caregiver who made the purchase ###(C) The date and time of the transaction; ###(D) A list of all of the medical cannabis or medical-cannabis product purchased, including a description of the quantity purchased; ###(E) The unique identifiers associated with the goods sold; and ###(F) Other information required by the Bureau.

###(c) Return of goods from a qualified patient or primary caregiver ###(1) If a dispensary accepts a return of medical cannabis from a qualified patient or a primary caregiver, the dispensary shall enter the following information: ###(A) The name of the licensed dispensary employee who processed the return; ###(B) The name or patient identification number of the qualified patient or primary caregiver who made the purchase ###(C) The date and time of the transaction; ###(D) A list of all of the medical cannabis or medical-cannabis product returned, including a description of the quantity purchased; ###(E) The unique identifiers associated with the goods; and ###(F) Other information required elsewhere by law.

###(d) Return of goods to a distributor ###(1) Enter the following information: ###(A) Distributor’s name and license number; ###(B) Name of licensee who transported the goods and license number; ###(C) Type of goods returned; ###(D) Amount received, by weight or count; ###(E) Best-by, sell-by, or expiration date of each product returned; ###(F) The date of the return of goods; ###(G) The unique identifiers associated with the goods returned; and ###(I) Other information required by the Bureau.

###(e) Destruction of goods ###(1) Enter the following information: ###(A) The name of the licensed dispensary employee who performed the destruction; ###(B) The date and time of the destruction; ###(C) A list of all of the medical cannabis or medical-cannabis product destroyed, including a description of the quantity destroyed; ###(E) The unique identifiers associated with the goods destroyed; and ###(F) Other information required by the Bureau.

###(f) Transfer of goods to a distributor for destruction ###(1) Enter the following information: ###(A) Distributor’s name and license number; ###(B) Name of licensee who transported the goods and license number; ###(C) Type of goods transferred; ###(D) Amount transferred, by weight or count; ###(E) The date of the transfer of goods; ###(F) The unique identifiers associated with the goods transferred; and ###(G) Other information required by the Bureau.

###Transporter Requirements A transporter shall enter the following events into the track-and-trace database: ###(1) Enter the following information: ###(A) Name and license number of transporter; ###(B) Date transporter receives goods from licensee for transport; ###(C) Amount transported, by weight or count; ###(E) Date transporter delivers product to licensee;
###(F) The unique identifiers associated with the goods transferred; ###(G) Spoilage or accidental fouling of product; ###(H) Any event resulting in exposure or compromise of the product and ###(G) Other information required by the Bureau.

About

Business Needs and User Stories for Cannabis Track and Trace

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published