Exhibit_A_Functional_Non-Functional_Requirements.xlsx
XLSX spreadsheet 113 KB Posted
- Attached to
- Cannabis Integration System (CSI) - DCC
- Solicitation number
- 0000039409
- Issued by
- California
About this file
This is a Functional and Non-Functional Requirements document for the Cannabis Systems Integration Project (Project Number 1115-005) submitted to the Department of Cannabis Control (DCC). The document establishes 200 functional requirements and associated non-functional requirements that bidders must address to be considered responsive. Requirements are categorized by function type—Compliance, Global, and Licensing—and classified as Mandatory, Mandatory-Optional, or Optional. Critical priorities dominate the requirements, covering core system capabilities including user authentication, document management, workflow automation, case management, inspection and investigation processes, recalls and remediation procedures, complaint handling, citations and fines processing, and license application review workflows. Bidders must indicate whether they can meet each Mandatory and Mandatory-Optional requirement with a "Y" or "N" response. For affirmative responses, bidders must select one response code indicating how requirements will be met: Out of the Box, Minor Configuration/Development (20 hours or less), Major Configuration/Development (21-39 hours) or Third Party Tools, or Customization (more than 40 hours). Any bid lacking "Y" responses for every Mandatory or Mandatory-Optional requirement will be deemed non-responsive and ineligible for evaluation.
The document provides detailed instructional guidance for bidder submissions across 200 requirement codes (FC-01 through FC-200, FG-01 through FG-83, and FL-01 through FL-165). Key functional areas address compliance management including regulatory updates and legislation adaptation; global capabilities such as data protection, document management, integration with third-party systems via APIs, workflow prioritization, and reporting; and licensing functions encompassing application review and processing, payment processing, refund procedures, delinquency management, collections, and equity application processing. The requirements emphasize system flexibility to accommodate regulatory changes without significant development effort, multi-user workflows with role-based access controls, automated notifications and escalations, document automation with template-based letter generation, and comprehensive audit logging and reporting capabilities. Three mandatory-optional requirements (FC-93, FC-94, FC-95) require bidder response but may not be included in final project scope; associated costs would be drawn from a separate cost workbook line item if the State elects to include them.
View the file
Other files
Show all 43
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
Bidder Instructions
| Respondent's Bid |
| In order for a Bid to be considered responsive, the Bidder must respond to "Bidder Response Met Y/N", column I and indicate how the requirement will be met, columns J-M (see below definitions) if "Y" response is provided. Place an "X" in appropriate column for how the requirement will be met. The Non-Functional Requirements worksheet only requires the 'Met (Y/N)' column to be completed. |
Mandatory-Optional requirements FC-93, FC-94 and FC-95 require bidder response. These requirements, are mandatory-optional as the State requires a bidder response, however, may not be added to project scope. If the State decides to include them in project scope, cost for these requirements will be drawn from the Exhibit C Cost Workbook, Mandatory-Optional line item.
| Definitions - Informational |
| Column A - Requirement Category: Identifies if the requirement is licensing, compliance or global function |
| Columns B - Requirement #: Unique identifier for each functional and non-functional requirement |
| Column C - Main Business Capability/Function: Overarching process which can result in several sub business functions |
| Column D - Sub Business Capability/Function: Mid-level process of a main business functional |
| Column E - Business Process: Specific workflow for a business function |
| Column F - Requirement Description: System functionality or behavior required, including what the system must do |
| Column G - Priority: Critical, high, medium or Low as it pertains to project scope |
| Column H - Classification: Requirement is Mandatory, Mandatory-Optional or Optional |
| Column I - Met (Y/N) |
| Enter either “Y” or “N” in this column, indicating that the Bidder can meet the requirement. Note: Any bid which does not include a "Y" after every Mandatory or Mandatory-Optional requirement will be considered as non-responsive and not eligible for evaluation/consideration. |
| Response Codes - Require one to be selected |
| The Bidder must choose one, and only one, Response Code for each mandatory and mandatory-optional requirement. Bidder must enter only the values identified below in the appropriate column; only one column may contain a value per requirement. Entering a response in more than one column for each requirement may result in disqualification of the bid. |
| Column J - Out of the Box |
| Enter an "X" in this cell if requirement can be met in its baseline form without minor or major configuration, or additional software or processes of any kind. Requirement is met “out of the box.” |
| Column K - Minor Configuration/Development (20 hours or less) |
| Enter an "X" in this cell if the requirement represents functionality that can be achieved via standard configuration or development of an existing system component. Examples of minor configuration or development is the flexibility to add fields, change field names, define drop down lists, add buttons, business rules, create and or update workflows and alerts, etc. (20 hours or less of contractor time for Design, Development and Implementation). |
| Column L - Major Configuration/Development (or Third party tools (21 - 39 Hours)) |
| Enter an "X" in this cell if the requirement represents functionality which must be achieved via additional Major Configuration or development of any component of the system or can be met with third party tools of extensions. The requirement can be met, but requires integrator staff who are skilled and knowledgeable of processes, data structures, and systems integration. Major configuration is considered the more complex changes using built-in scripting features or programming language. (21- 39 hours of contractor time for Design, Development and Implementation). |
| Column M - Customization (More than 40 Hours) |
| Enter an "X" in this cell if the requirement can be met with code changes, integrations or other alternatives which create functionality outside of the software platform that is not available through configuration. |
Functional Requirements
| Project Number: 1115-005 Cannabis Systems Integration Project | Bidder Response | Response Codes (See instructions for Definitions) | ||||||||
| Requirement Category | Requirement # | Main Business Capability/Function | Sub Business Capability/Function | Business Process | Requirement Description | Priority | Classification | Met? | ||
| (Y/N) | Out of the Box | Minor Configuration/Development | ||||||||
| (20 hours or less) | Major Configuration/Development (21 - 39 Hours) | |||||||||
| or Third Party Tools | Customization |
(More than 40 Hours)
| COMPLIANCE | FC-01 | Global | Data Protection | User Sign In | The system shall allow a user to sign in to the DCC Portal to conduct any action with DCC. | Critical | Mandatory | |
| COMPLIANCE | FC-02 | Global | Compliance Management | Regulatory Updates and License Adaptation | The system shall be capable of being configured to accommodate changes to DCC regulations or Legislation across all License categories. This includes updating workflows, criteria, and decision rules without requiring significant development effort. | High | Mandatory | |
| COMPLIANCE | FC-03 | Global | Document Management | File Upload | The system shall display a message or notification to the users indicating the acceptable document types for upload, allowing users as well as Previewer to check files requirements without exiting the system. | Medium | Optional | |
| COMPLIANCE | FC-04 | Inspections | Inspection Record/Active Case Management | Case Management | The system shall separate cases with parent ID's and link Parent ID's to the Case number. | High | Mandatory | |
| COMPLIANCE | FC-05 | Inspections | Inspection Record/Active Case Management | Incident tracking | The system shall have a dropdown menu for the Compliance Staff to select recommended action. | High | Mandatory | |
| COMPLIANCE | FC-06 | Investigations | Investigation Process | Case Management | The system shall separate cases with parent ID's and link Parent ID's to the Case number. | Critical | Mandatory | |
| COMPLIANCE | FC-07 | Investigations | Investigation Process | Incident tracking | The system shall have a dropdown menu for the Compliance Staff to select recommended action. | Medium | Optional | |
| COMPLIANCE | FC-08 | Referrals | Complaint Submission | Complaint Referrals | The system shall allow the user to submit a minimum character limit determined by DCC and must be configurable, summary of complaint, Respondent information (name of the entity/ Location/address), first & last name, email, phone number, and a check box to verify the statement. | |||
| minimum character limit summary of complaint, Respondent information (name of the entity/ Location/address), first & last name, email, phone number, and a check box to verify the statement. | Critical | Mandatory | ||||||
| COMPLIANCE | FC-09 | Referrals | Spam Detection | Complaint Referrals | The system must automatically verify and flag complaints as spam to prevent irrelevant or fraudulent submissions from entering the complaint process. | Critical | Mandatory | |
| COMPLIANCE | FC-10 | Referrals | Acknowledgment Notification | Complaint Referrals | The system must send an automatic acknowledgment notification to the complainant once the complaint is successfully submitted and validated. | High | Mandatory | |
| COMPLIANCE | FC-11 | Global | Document Management | File Upload | The system shall set configurable file size limits determined by DCC for uploads to ensure efficient processing. | Medium | Mandatory | |
| COMPLIANCE | FC-12 | Global | Document Management | File Upload | The system shall allow file size limits for uploads to be configurable to ensure efficient processing. | Medium | Mandatory | |
| COMPLIANCE | FC-13 | Global | Document Management | File Upload | The system shall allow a user to upload more than one document with an associated category. | Medium | Mandatory | |
| COMPLIANCE | FC-14 | Global | Document Management | File Upload | The system shall allow a user to indicate if the uploaded file is for internal use only. | Critical | Mandatory | |
| COMPLIANCE | FC-15 | Global | Document Management | File Upload | The system shall allow a user to view, add, and delete files uploaded before submitting an application for review. | Medium | Mandatory | |
| COMPLIANCE | FC-16 | Global | Document Management | File Upload | The system shall allow a user to view and add files for upload after submitting an application for review. | Medium | Mandatory | |
| COMPLIANCE | FC-17 | Global | Document Management | File Upload | The system shall validate uploaded files during the application intake process and prevent the acceptance of restricted and Blank file formats. | High | Mandatory | |
| COMPLIANCE | FC-18 | Global | Document Management | File Upload | The system shall allow a user to modify an existing document and its description. | High | Mandatory | |
| COMPLIANCE | FC-19 | Global | User Experience | Interface Design | The system shall provide users a tooltip on instructions for how to successfully complete an application. | Low | Optional | |
| COMPLIANCE | FC-20 | Global | Integration | Third-Party System Compatibility | The system shall support integration with external system through standardized APIs for seamless data exchange. | High | Mandatory | |
| COMPLIANCE | FC-21 | Global | Application Forms | Save | The system shall allow users to save and return back to the application form at a later time to pick up where they left off or allow the user to navigate to the beginning of the application. | High | Mandatory | |
| COMPLIANCE | FC-22 | Global | Document Management | File Download | The system shall allow a user to download their application in a PDF format. | Critical | Mandatory | |
| COMPLIANCE | FC-23 | Global | Workflow | Progress Bar | The system shall incorporate a progress bar within each business process to indicate the status of the workflow. | High | Optional | |
| COMPLIANCE | FC-24 | Global | Logging | Reporting | The system shall provide a flexible reporting capability for each business unit. | Critical | Mandatory | |
| COMPLIANCE | FC-25 | Global | Document Management | Document Storage | The system shall automatically create a folder for each licensee using the licensee’s name and license number as the folder name. This folder will be used to store all documents related to that licensee. | Critical | Mandatory | |
| COMPLIANCE | FC-26 | Global | Document Management | Document Storage | The system shall automatically add any received documents to the corresponding licensee's folder based on the licensee’s identifier, ensuring proper organization and storage of documents | Critical | Mandatory | |
| COMPLIANCE | FC-27 | Global | Workflow | Prioritization | The system shall allow the users the flexibility to shuffle the order of cases based on priority. | High | Mandatory | |
| COMPLIANCE | FC-28 | Global | Workflow | Identification | The system shall create a unique identifier number for Recall or Remediation cases. | Critical | Mandatory | |
| COMPLIANCE | FC-29 | Inspections | Inspection Record | Assignment | The system should allow the supervisor to optionally assign inspection records to specific Compliance Staff members. | Medium | Optional | |
| COMPLIANCE | FC-30 | Inspections | Inspection Record/Active Case Management | Case Management | The system should display a dashboard showing the workload distribution across regions. | Medium | Optional | |
| COMPLIANCE | FC-31 | Inspections | Inspection Record/Active Case Management | Case Management | The system must display the current workload and case status for the Compliance Staff | High | Mandatory | |
| COMPLIANCE | FC-32 | Inspections | Inspection Record/Active Case Management | Data Retrieval | The system should pre-fill fields (e.g., inspector name or case type) based on previous inspection data. | Medium | Optional | |
| COMPLIANCE | FC-33 | Inspections | Inspection Record/Active Case Management | Documentation | The system must ensure all required fields are completed before submitting. | Critical | Mandatory | |
| COMPLIANCE | FC-34 | Inspections | Inspection Record/Active Case Management | Incident tracking | The system shall include a checklist for the Compliance Staff to select the type of violation, a drop-down menu to choose the appropriate enforcement action, and a free-form text box to add any additional violations. | High | Mandatory | |
| COMPLIANCE | FC-35 | Inspections | Inspection Record/Active Case Management | Documentation | The system shall enable Compliance Staff to complete the enforcement letter, which will be automatically prefilled with relevant data based on the selected template, allowing for final review and adjustments before generation. | Critical | Mandatory | |
| COMPLIANCE | FC-36 | Inspections | Inspection Record/Active Case Management | Notification | The system should notify the supervisor when the enforcement letter is ready for review. | High | Mandatory | |
| COMPLIANCE | FC-37 | Inspections | Inspection Record/Active Case Management | Reporting and Analytics | The system shall generate a report that calculates and displays the total time taken from the date of the inspection to the date the enforcement letter is sent out to the recipient | Medium | Optional | |
| COMPLIANCE | FC-38 | Inspections | Inspection Record/Active Case Management | Incident tracking | The system must enable the Compliance Staff to select the case status from various options, including "In Progress," "Completed," "With Legal," "With Attorney General's Office," "Under Supervisor Review," "Awaiting Licensee/Designated Responsible Party Response," and others as applicable. | Medium | Mandatory | |
| COMPLIANCE | FC-39 | Inspections | Inspection Record/Active Case Management | Documentation | The system shall allow Compliance Staff to upload additional photos and documents associated with the inspection throughout the entire process. | Medium | Optional | |
| COMPLIANCE | FC-40 | Inspections | Inspection Record/Active Case Management | Admin Review | The system shall prompt the supervisor to request additional information from the Compliance Staff if required information or documents are missing or incomplete during the review process. | High | Mandatory | |
| COMPLIANCE | FC-41 | Inspections | Inspection Record | Admin Review | If additional information is required, the system must re-assign the inspection record to Compliance Staff | High | Mandatory | |
| COMPLIANCE | FC-42 | Inspections | Inspection Record/Active Case Management | Admin Review | The system shall allow Compliance Staff to add requested information and return the record to the supervisor. | High | Mandatory | |
| COMPLIANCE | FC-43 | Inspections | Inspection Record/Active Case Management | Document Automation | The system shall generate a letter template automatically based on the selected violation(s) and enforcement action(s). | High | Mandatory | |
| COMPLIANCE | FC-44 | Inspections | Inspection Record/Active Case Management | Notification | The system shall notify the Compliance staff that the supervisor has received the violation letter for review. | High | Mandatory | |
| COMPLIANCE | FC-45 | Inspections | Inspection Record/Active Case Management | Notification | The system shall send a notification to the Compliance Staff that the violation has been sent out after the violation is sent. | High | Mandatory | |
| COMPLIANCE | FC-46 | Inspections | Inspection Record/Active Case Management | Documentation | The system should allow users to filter and search case notes for quicker access to relevant information. | Medium | Optional | |
| COMPLIANCE | FC-47 | Inspections | Inspection Record/Active Case Management | Documentation | The system must allow sending the enforcement | |||
| letter to additional relevant parties for review as necessary. | High | Mandatory | ||||||
| COMPLIANCE | FC-48 | Inspections | Inspection Record/Active Case Management | Admin Review | The system must allow relevant parties to | |||
| approve or reject the enforcement letter. | High | Mandatory | ||||||
| COMPLIANCE | FC-49 | Inspections | Inspection Record/Active Case Management | Admin Review | The system must require the reviewer to provide | |||
| feedback and send the letter back to the originator if rejected. | High | Mandatory | ||||||
| COMPLIANCE | FC-50 | Inspections | Inspection Record/Active Case Management | Document Automation | If approved, the system must send the enforcement letter to the designated responsible party. | High | Mandatory | |
| COMPLIANCE | FC-51 | Inspections | Inspection Record/Active Case Management | Notification | Notifications must be generated for the following actions: |
- Rejection of the letter.
- Approval of the letter.
| - Reminder notification if no action is taken. | High | Mandatory | ||||||
| COMPLIANCE | FC-52 | Investigations | Investigation Process | Assignment | The system shall allow a supervisor to assign Compliance Staff investigation task(s). | Medium | Optional | |
| COMPLIANCE | FC-53 | Investigations | Investigation Process | Categorization | Once the Compliance Staff prioritizes the investigation complaints received, the system shall categorize the complaints. | High | Mandatory | |
| COMPLIANCE | FC-54 | Investigations | Investigation Process | Data Retrieval | The system shall retrieve relevant information, including the license number, associated codes, and subtypes, based on the keywords and details entered, such as the name of a person or business. | Critical | Mandatory | |
| COMPLIANCE | FC-55 | Investigations | Investigation Process | Documentation | The system shall allow the Compliance Staff to input information collected from the field investigation. | High | Mandatory | |
| COMPLIANCE | FC-56 | Investigations | Investigation Process | Incident tracking | The system shall include a checklist for the Compliance Staff to select the type of violation, along with a drop-down menu to choose the appropriate enforcement action and a free-form text box to add any additional violations. | Medium | Optional | |
| COMPLIANCE | FC-57 | Investigations | Investigation Process | Document Automation | The system shall generate a letter template based on the violation selected on the dropdown menu. | High | Mandatory | |
| COMPLIANCE | FC-58 | Investigations | Investigation Process | Admin Review | The system shall initiate the process of sending the violation letter to the supervisor for review when the compliance staff selects the 'Supervisor Review' option . Upon triggering this action, the supervisor will receive the violation letter for review and approval before it is finalized and sent to the intended recipient." | High | Mandatory | |
| COMPLIANCE | FC-59 | Investigations | Investigation Process | Admin Review/Notification | The system shall notify the Compliance staff when the supervisor has received the violation letter for review, immediately after the supervisor has been notified of the letter being submitted for review. | High | Mandatory | |
| COMPLIANCE | FC-60 | Investigations | Investigation Process | Notification | The system shall send an email and letter out to the Licensee & Primary Contact. | High | Mandatory | |
| COMPLIANCE | FC-61 | Investigations | Investigation Process | Notification | The system shall send an notification to the Compliance Staff that the enforcement letter has been sent out. | High | Mandatory | |
| COMPLIANCE | FC-62 | Investigations | Investigation Process/Close Investigation Case | Documentation | The system shall allow Compliance Staff to input any further information gathered during the investigation. | High | Mandatory | |
| COMPLIANCE | FC-63 | Investigations | Investigation Process/Close Investigation Case | Assignment/Admin Review | The system shall assign the case to the supervisor for review once the Compliance Staff recommends actions and submits the case. The supervisor will then be notified to begin their review process. | High | Mandatory | |
| COMPLIANCE | FC-64 | Investigations | Investigations | Case Management | The system shall provide a page for Compliance Staff that displays the status of all cases, allowing them to view and track the current progress of each case. | Medium | Optional | |
| COMPLIANCE | FC-65 | Investigations | Investigation Process | Assignment/Review | The system shall allow the supervisor to reassign a case to Compliance Staff to review. | High | Mandatory | |
| COMPLIANCE | FC-66 | Investigations | Closing Investigation Case | Case Management | The system shall allow the supervisor to close out the case. | High | Mandatory | |
| COMPLIANCE | FC-67 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Referral information | The system shall receive referral Information. | High | Mandatory | |
| COMPLIANCE | FC-68 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Referrals | The system shall send request for Derived Package Report to Metrc staff. | High | Mandatory | |
| COMPLIANCE | FC-69 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Referrals | The system prioritizes recalls based on the category. | High | Mandatory | |
| COMPLIANCE | FC-70 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Referrals | The system creates a recall profile where all the recall information can be viewed and added such as the info sheet, lab results, and licensee information from the licensing system. | High | Mandatory | |
| COMPLIANCE | FC-71 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Document Automation | The system shall pull information from the Derived Package Report & Compliance staff reviews | High | Mandatory | |
| COMPLIANCE | FC-72 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Document Automation | The system shall draft a letter template based on the referral to send to Licensee. | High | Mandatory | |
| COMPLIANCE | FC-73 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Recall Hold Placement | The system shall implement Metrc holds on the items that will be recalled once confirmed by Compliance Staff. | High | Mandatory | |
| COMPLIANCE | FC-74 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Document Automation | If there's evidence of Probable Cause, The system shall produce a Pre-Embargo Letter and send it to the Licensee. | High | Mandatory | |
| COMPLIANCE | FC-75 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Document Automation | If there's Evidence, The system shall produce a Notice of Adulteration and sends it to the Licensee. | High | Mandatory | |
| COMPLIANCE | FC-76 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Document Automation | If there's a Combination of Evidence & Probable Cause, The system shall produce a Pre-Embargo Letter and Letter of Adulteration and send it to the Licensee. | High | Mandatory | |
| COMPLIANCE | FC-77 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Voluntary Recall Submission | The system shall submit the Case as a Voluntary Recall if they agree with the Pre Embargo Letter or Notice of Adulteration/Misbranding | High | Mandatory | |
| COMPLIANCE | FC-78 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Mandatory Recall Submission | The system shall submit the Case as a Mandatory Recall if they do not agree with the Pre Embargo Letter or Notice of Adulteration. | High | Mandatory | |
| COMPLIANCE | FC-79 | Recalls | Mandatory & Voluntary Recalls & Pre-Embargo Process | Embargo Initiation | The system shall submit the case as an "Embargo" and send out an Embargo Notice to the Licensee if they do not agree with the Pre Embargo Letter. | High | Mandatory | |
| COMPLIANCE | FC-80 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Document Automation | The system must automatically draft a recall letter based on the submitted recall case. | High | Mandatory | |
| COMPLIANCE | FC-81 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Document Approval | The system must send the approved recall letter to the responsible licensee upon supervisor approval. | High | Mandatory | |
| COMPLIANCE | FC-82 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Case Management | If no response is received from the licensee, the system must send an automated reminder. | High | Mandatory | |
| COMPLIANCE | FC-83 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Case Management | The system must automatically escalate the case to ISB after a set period (e.g., after Recalls and Remediation Unit follow-up on Day 2). | High | Mandatory | |
| COMPLIANCE | FC-84 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Case Management | The system must allow supervisors to approve or reject recall letters. | High | Mandatory | |
| COMPLIANCE | FC-85 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Case Management | If a recall is set aside, the system must remove the METRC hold and notify relevant parties. | High | Mandatory | |
| COMPLIANCE | FC-86 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Case Management | The system must send decisions to Executives, Legal, and named stakeholders (e.g., Mina/Jeff). | High | Mandatory | |
| COMPLIANCE | FC-87 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Case Management | The system must send mandatory recall letters to retailers if licensee disagrees with outcome of affirm/modify. | High | Mandatory | |
| COMPLIANCE | FC-88 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Automated reminders | The system must send automated reminders to retailers who do not respond | High | Mandatory | |
| COMPLIANCE | FC-89 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Case Management | The system must escalate unresponsive retailers to ISB automatically after a set interval. | High | Mandatory | |
| COMPLIANCE | FC-90 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Audit | The system must log all recall-related interactions with licensees and retailers | High | Mandatory | |
| COMPLIANCE | FC-91 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Decision Branching | The system must allow branching decisions based on input (e.g., response received or not, agreement status). | High | Mandatory | |
| COMPLIANCE | FC-92 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Decision Branching | The system must route informal hearing requests and record their outcomes. | High | Mandatory | |
| COMPLIANCE | FC-93 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Case Management | The system must support referral to the "Post Implementation Process for Mandatory & Voluntary Recalls | High | Mandatory | |
| COMPLIANCE | FC-94 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Manual Over rides | The system must allow manual overrides or comments to be added by Recalls and Remediation Unit or ISB staff. | High | Mandatory | |
| COMPLIANCE | FC-95 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Decision Branching | The system must support decision branching logic (Affirm, Modify, Set Aside) with traceable actions. | High | Mandatory | |
| COMPLIANCE | FC-96 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Notifications | The system must send notifications to relevant stakeholders at each major step (approval, escalation, closure) | High | Mandatory | |
| COMPLIANCE | FC-97 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Reporting | The system should provide dashboard summaries of recall status by case type and response time. | Medium | Mandatory | |
| COMPLIANCE | FC-98 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Automated reminders | The system should allow customizable reminder schedules (e.g., change from 2 days to 3 days). | High | Mandatory | |
| COMPLIANCE | FC-99 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Reporting | The system should allow auto-generation of summary reports for recall outcomes. | High | Mandatory | |
| COMPLIANCE | FC-100 | Recalls | Mandatory Recalls Process (Notification to Licensee) | Automated reminders | The system should support sending follow-up messages via multiple communication channels (email, SMS). | High | Mandatory | |
| COMPLIANCE | FC-101 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Case Management | The system must initiate the Post Implementation Process once a recall is triggered. | High | Mandatory | |
| COMPLIANCE | FC-102 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Document Approval | The system must send a draft Executive Notice for approval | High | Mandatory | |
| COMPLIANCE | FC-103 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Notifications | The system must notify the internal team once the Executive Notification is approved by the Deputy Director. | High | Mandatory | |
| COMPLIANCE | FC-104 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Notifications | The system must send a Public Announcement (PA) request once the notification is approved. | High | Mandatory | |
| COMPLIANCE | FC-105 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Reporting and Analytics | The system must generate and send an inventory list to the licensee. | High | Mandatory | |
| COMPLIANCE | FC-106 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Document Automation | The system must send out a destruction/remediation letter. | High | Mandatory | |
| COMPLIANCE | FC-107 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Case Management | The system must automatically remove the METRC hold once remediation or destruction is approved and completed. | High | Mandatory | |
| COMPLIANCE | FC-108 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Document Automation | The system must issue a Destruction Notice if a destruction plan is submitted. | High | Mandatory | |
| COMPLIANCE | FC-109 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Notifications | The system must send automated reminders to licensees when destruction footage is not received. | High | Mandatory | |
| COMPLIANCE | FC-110 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Case Management | The system must escalate non-response cases to ISB automatically after one business day. | High | Mandatory | |
| COMPLIANCE | FC-111 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Case Management | The system must accept and store licensee-submitted recall procedures templates and public notices. | High | Mandatory | |
| COMPLIANCE | FC-112 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Case Management | The system must allow submission and review tracking of corrective action plans for remediation. | High | Mandatory | |
| COMPLIANCE | FC-113 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Case Management | The system must support tracking of destruction plan submissions and notify appropriate teams. | High | Mandatory | |
| COMPLIANCE | FC-114 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Case Management | The system must track approval/denial status of remediation plans and act accordingly. | High | Mandatory | |
| COMPLIANCE | FC-115 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Notifications | The system must notify licensees when additional information is needed after destruction footage review. | High | Mandatory | |
| COMPLIANCE | FC-116 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Decision Branching | The system must refer non-compliant licensees to ISB when additional information is not received. | High | Mandatory | |
| COMPLIANCE | FC-117 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Decision Branching | The system must support user-driven routing depending on whether the process involves remediation, destruction, or both. | High | Mandatory | |
| COMPLIANCE | FC-118 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Decision Branching | The system must support branching logic for additional review steps after footage is submitted. | High | Mandatory | |
| COMPLIANCE | FC-119 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Decision Branching | The system must allow tracking of whether licensee has destruction footage and prompt next steps based on answer. | High | Mandatory | |
| COMPLIANCE | FC-120 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Audit | The system must allow Recalls and Remediation Unit to review and log destruction footage decisions. | High | Mandatory | |
| COMPLIANCE | FC-121 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Reporting and Analytics | The system should provide a dashboard view of open recalls by status (e.g., pending footage, pending approval). | High | Mandatory | |
| COMPLIANCE | FC-122 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Auto tag | The system should auto-tag cases involving both remediation and destruction for split-tracking. | High | Mandatory | |
| COMPLIANCE | FC-123 | Recalls | Post Implementation Process for Mandatory & Voluntary Recalls (Executive Notification, Remediation, and Destruction) | Notifications | The system should allow stakeholders to receive alerts via multiple channels (email, internal alerts). | High | Mandatory | |
| COMPLIANCE | FC-124 | Referrals | Allegation Verification | Complaint Referrals | The system must verify if the complaint contains one or more allegations from a Licensee. | High | Mandatory | |
| COMPLIANCE | FC-125 | Referrals | Multiple Complaint Separation | Complaint Referrals | If the complaint contains multiple allegations from a Licensee, the system must automatically separate the complaint into individual cases, and the analyst must confirm this separation. | High | Mandatory | |
| COMPLIANCE | FC-126 | Referrals | License Status Verification | Complaint Referrals | The system must verify the complainant's | |||
| license status | High | Mandatory | ||||||
| COMPLIANCE | FC-127 | Referrals | Desk Investigation and Processing | Complaint Referrals | The system must enable analysts to conduct |
desk investigations and process the associated worksheet.
| This includes gathering any necessary supporting documents and ensuring all relevant information is collected. | High | Mandatory | ||||||
| COMPLIANCE | FC-128 | Referrals | Complaint Referral to Regulatory Agencies | Complaint Referrals | The system will route the complaint to the appropriate agency or agencies once it is determined the complaint needs to referred to another agency. | Critical | Mandatory | |
| COMPLIANCE | FC-129 | Referrals | Agency Referral Notification | Complaint Referrals | If a transfer is necessary, | |||
| the system must automatically send an email to the relevant Regulatory Agency with the complaint details. | High | Mandatory | ||||||
| COMPLIANCE | FC-130 | Referrals | Complainant Referral Notification | Complaint Referrals | Once the complaint is referred to another Regulatory Agency, the system must send an email to the complainant informing them that their complaint has been transferred to the appropriate agency for further handling | High | Mandatory | |
| COMPLIANCE | FC-131 | Remediation | Remediation Corrective Action Plan Review Procedure | Case Management | The system must assign new remediation cases to Environmental Scientist (ES) based on predefined logic that prioritizes existing working relationships while also balancing workload across the team. | Critical | Mandatory | |
| COMPLIANCE | FC-132 | Remediation | Remediation Corrective Action Plan Review Procedure | Case Management | The system must notify the Environmental Scientist | |||
| immediately upon case assignment. | High | Mandatory | ||||||
| COMPLIANCE | FC-133 | Remediation | Remediation Corrective Action Plan Review Procedure | Notifications | The system must notify Environmental Scientist upon | |||
| receipt of documents from the licensee via the portal. | High | Mandatory | ||||||
| COMPLIANCE | FC-134 | Remediation | Remediation Corrective Action Plan Review Procedure | Service Level Agreement | The system must monitor and track Service Level Agreement deadlines (15 business days) and send automated reminders. | High | Mandatory | |
| COMPLIANCE | FC-135 | Remediation | Remediation Corrective Action Plan Review Procedure | Case Management | The system must ensure all required documents are verified and attached to the case before final review | High | Mandatory | |
| COMPLIANCE | FC-136 | Remediation | Remediation Corrective Action Plan Review Procedure | Notifications | The system must notify Senior Environmental Scientist that the | |||
| case is ready for Quality Assurance review. | High | Mandatory | ||||||
| COMPLIANCE | FC-137 | Remediation | Remediation Corrective Action Plan Review Procedure | Case Management | The system must update case status to “Ready for QA review” upon completion of Environmental Scientist review. | High | Mandatory | |
| COMPLIANCE | FC-138 | Remediation | Remediation Corrective Action Plan Review Procedure | Case Management | The system must route the case back | |||
| to Environmental Scientist if Environmental Scientists requests additional information. | High | Mandatory | ||||||
| COMPLIANCE | FC-139 | Remediation | Remediation Corrective Action Plan Review Procedure | Case Management | The system must update internal case and batch statuses, and notify ISB if failed batches exist. | High | Mandatory | |
| COMPLIANCE | FC-140 | Remediation | Remediation Corrective Action Plan Review Procedure | Document Automation | The system must send a final decision letter to the licensee. | High | Mandatory | |
| COMPLIANCE | FC-141 | Remediation | Remediation Inbox Procedure | Inbox monitoring | The system must monitor the remediation inbox and register any incoming emails automatically. | Critical | Mandatory | |
| COMPLIANCE | FC-142 | Remediation | Remediation Inbox Procedure | Inbox monitoring | The system must identify whether the incoming email is related to a failed batch. | High | Mandatory | |
| COMPLIANCE | FC-143 | Remediation | Remediation Inbox Procedure | Decision Branching | If a failed batch is detected, the system must route the case to the “Failed Batch Procedure.” | Critical | Mandatory | |
| COMPLIANCE | FC-144 | Remediation | Remediation Inbox Procedure | Decision Branching | The system must identify if an email contains general inquiries and notify the assigned Environmental Scientist for response. | Medium | Mandatory | |
| COMPLIANCE | FC-145 | Remediation | Remediation Inbox Procedure | Service Level Agreement | The system must enforce a response Service Level Agreement of two business days for Environmental Scientist replies to general questions. | High | Mandatory | |
| COMPLIANCE | FC-146 | Remediation | Remediation Inbox Procedure | Decision Branching | The system must detect if the email includes a remediation plan or request. | Critical | Mandatory | |
| COMPLIANCE | FC-147 | Remediation | Remediation Inbox Procedure | Decision Branching | The system must determine whether the licensee's inquiry relates to a retest or Certificate of Analysis.. | Medium | Mandatory | |
| COMPLIANCE | FC-148 | Remediation | Remediation Inbox Procedure | Decision Branching | If the inquiry is related to retesting or Certificate of Analysis, the system must forward the request to the Testing Labs inbox or portal. | High | Mandatory | |
| COMPLIANCE | FC-149 | Remediation | Remediation Inbox Procedure | Manual override | The Environmental Scientist must be able to route non-remediation emails to the appropriate DCC inbox from within the system interface. | Medium | Mandatory | |
| COMPLIANCE | FC-150 | Remediation | Remediation Inbox Procedure | Case Management | The system must verify and store the licensee’s contact information for all valid remediation plan emails. | High | Mandatory | |
| COMPLIANCE | FC-151 | Remediation | Remediation Inbox Procedure | Case Management | The system must auto-generate a case folder and store the remediation plan and original email submitted. | Critical | Mandatory | |
| COMPLIANCE | FC-152 | Remediation | Remediation Inbox Procedure | Document Automation | The system must send a confirmation email to the licensee upon creation of a remediation case. | High | Mandatory | |
| COMPLIANCE | FC-153 | Remediation | Remediation Inbox Procedure | Case Management | Upon withdrawal by licensee, the system must update the case status to “Withdrawn.” | High | Mandatory | |
| COMPLIANCE | FC-154 | Remediation | Remediation Inbox Procedure | Case Management | The system must provide current case status to the licensee in response to a status request. | Medium | Mandatory | |
| COMPLIANCE | FC-155 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall received Lab Test Data Failure Spreadsheet. | High | Mandatory | |
| COMPLIANCE | FC-156 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall receive Reconcile Daily Failure Test Data. | High | Mandatory | |
| COMPLIANCE | FC-157 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall verify and extract data from the Reconcile Daily Failure Data. | High | Mandatory | |
| COMPLIANCE | FC-158 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall save Certificates of Analysis into Share drive folder. | High | Mandatory | |
| COMPLIANCE | FC-159 | Remediation | Failed Cannabis Goods Procedure | Document Automation | The system shall utilize email template to input batch information. | High | Mandatory | |
| COMPLIANCE | FC-160 | Remediation | Failed Cannabis Goods Procedure | Document Automation | The system shall send out email to Distributors Licensees | High | Mandatory | |
| COMPLIANCE | FC-161 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall input date email was sent into the Failed Goods Tracker. | High | Mandatory | |
| COMPLIANCE | FC-162 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall store email to the Failed Batch Licensee Folder. | High | Mandatory | |
| COMPLIANCE | FC-163 | Remediation | Failed Cannabis Goods Procedure | Notifications | The system shall review disposition of batch and notify ISB for approval. | High | Mandatory | |
| COMPLIANCE | FC-164 | Remediation | Failed Cannabis Goods Procedure | System routing | The system shall forward batches to ISB | High | Mandatory | |
| COMPLIANCE | FC-165 | Remediation | Failed Cannabis Goods Procedure | Notifications | If the Distributor elects to destroy the batch, the system shall notify ISB. | High | Mandatory | |
| COMPLIANCE | FC-166 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall file email from RP inbox template or Remediation Template. | High | Mandatory | |
| COMPLIANCE | FC-167 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall update "Licensee decision" section on the Failed Goods Tracker. | High | Mandatory | |
| COMPLIANCE | FC-168 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall require Licensee to input Remediating Licensee number. | High | Mandatory | |
| COMPLIANCE | FC-169 | Remediation | Failed Cannabis Goods Procedure | Notifications | The system shall send out email to the remediating Licensee. | High | Mandatory | |
| COMPLIANCE | FC-170 | Remediation | Failed Cannabis Goods Procedure | System routing | The system shall send out information to testing lab. | High | Mandatory | |
| COMPLIANCE | FC-171 | Remediation | Failed Cannabis Goods Procedure | Notifications | If there is non complaint activity, the system shall notify compliance@cannabis.ca.gov | High | Mandatory | |
| COMPLIANCE | FC-172 | Remediation | Failed Cannabis Goods Procedure | Notifications | The system shall notify the inspection and compliance case manager if there is non complaint activity. | High | Mandatory | |
| COMPLIANCE | FC-173 | Remediation | Failed Cannabis Goods Procedure | Case Management | The system shall assign Notice to Comply to the Scientist in the Recalls and Remediation Unit if there is non complaint activity. | High | Mandatory | |
| COMPLIANCE | FC-174 | Global | Workflow | Prioritization | The system shall allow case administrators to sign off on the prioritization of recall or remediation cases. | High | Mandatory | |
| COMPLIANCE | FC-175 | Global | Workflow | Profile Creation | The system shall create a Recall or Remediation profile dashboard housing information about the recall or remediation. | High | Mandatory | |
| COMPLIANCE | FC-176 | Global | Workflow | Progress Status | The system shall allow users to track the status of recall through the Recall dashboard or Remediation dashboard. | High | Optional | |
| COMPLIANCE | FC-177 | Global | Notification Management | Role-Based Alerts | The system must support role-based notifications (e.g., ES, SESS, ISB) based on case status and outcome. | High | Mandatory | |
| COMPLIANCE | FC-178 | Global | Returns Management | Failed Goods Tracking | The system shall have a Failed Goods Tracker . | High | Mandatory | |
| COMPLIANCE | FC-179 | Global | Case Management | Communication Logging | The system shall allow communication information to be stored in the Failed Goods Tracker. | High | Mandatory | |
| COMPLIANCE | FC-180 | Complaints | Complaint Submission | Unlicensed Complaints | The system shall allow the user to submit a minimum character limit determined by DCC and must be configurable, summary of complaint, Respondent information (name of the entity/ Location/address), first & last name, email, phone number, and a check box to verify the statement. | Critical | Mandatory | |
| COMPLIANCE | FC-181 | Complaints | Complaint Submission | Unlicensed Complaints | The system must automatically verify and flag complaints as spam to prevent irrelevant or fraudulent submissions from entering the complaint process. | Critical | Mandatory | |
| COMPLIANCE | FC-182 | Complaints | Acknowledgment Notification | Unlicensed Complaints | The system must send an automatic acknowledgment notification to the complainant once the complaint is successfully submitted and validated. | High | Mandatory | |
| COMPLIANCE | FC-183 | Complaints | File Creation | Unlicensed Complaints | The system should create a digital file for each complaint automatically, using a predefined naming convention to ensure consistency and easy access. | High | Mandatory | |
| COMPLIANCE | FC-184 | Complaints | Attachment Handling | Unlicensed Complaints | Upon submission, the system should automatically detect and associate any attached documents to the complaint file. | Medium | Optional | |
| COMPLIANCE | FC-185 | Complaints | Complaint Worksheet Generation | Unlicensed Complaints | The system must generate a complaint worksheet and associate it with the respective complaint file to ensure analysts can easily input and track relevant details. | High | Mandatory | |
| COMPLIANCE | FC-186 | Complaints | Complaint Assignment | Unlicensed Complaints | The system must intelligently assign complaints to analysts based on predefined rules: |
If there’s a previous relationship with an analyst, the system will automatically route the complaint to that analyst.
| If there’s no established relationship, the system assigns the complaint to an analyst based on their current workload. | Critical | Mandatory | ||||||
| COMPLIANCE | FC-187 | Complaints | Prioritization of Complaints | Unlicensed Complaints | The system must prioritize complaints automatically based on urgency and deadlines to ensure the most time-sensitive complaints are handled first. | High | Mandatory | |
| COMPLIANCE | FC-188 | Complaints | Duplicate Detection | Unlicensed Complaints | The system must analyze complaints for potential duplicates, flagging them automatically based on set criteria (e.g., identical content, similar complainant info). | Critical | Mandatory | |
| COMPLIANCE | FC-189 | Complaints | Duplicate Review | Unlicensed Complaints | Analysts should be able to review flagged potential duplicates within the system and either combine, reject, or validate the complaints. | High | Mandatory | |
| COMPLIANCE | FC-190 | Complaints | Document Management | Unlicensed Complaints | The system should allow analysts to upload supporting documents (e.g., screenshots, reports, evidence) into the digital complaint file, maintaining proper organization. | Medium | Mandatory | |
| COMPLIANCE | FC-191 | Complaints | Case Resolution Tracking | Unlicensed Complaints | The system should allow analysts to track the status of each case and ensure that each complaint is resolved and closed in a timely manner. | High | Mandatory | |
| COMPLIANCE | FC-192 | Complaints | Enter Recommended Disposition | Licensed Complaints | The system must allow the analyst to enter | |||
| a recommended disposition for the complaint. | High | Mandatory | ||||||
| COMPLIANCE | FC-193 | Complaints | Complete AGPA Review Workflow | Licensed Complaints | The system must provide an automated internal user review workflow to route complaints through the appropriate approval process. | High | Mandatory | |
| COMPLIANCE | FC-194 | Complaints | ISB Referral Check | Licensed Complaints | The system must allow the analyst to check | |||
| if a complaint needs to be referred to the ISB and manage the referral process. | Critical | Mandatory | ||||||
| COMPLIANCE | FC-195 | Complaints | Transfer to ISB | Licensed Complaints | If the complaint needs to be referred to ISB, the system must allow the analyst to refer the complaint to ISB. | Critical | Mandatory | |
| COMPLIANCE | FC-196 | Complaints | Manager Review for Insufficient Info | Licensed Complaints | The system must automatically flag complaints with closure recommendations and refer them to the manager for further review. | High | Mandatory | |
| COMPLIANCE | FC-197 | Complaints | Manager Review and Approval | Licensed Complaints | The system must allow the manager to | |||
| review the complaint and approve or reject it | Critical | Mandatory | ||||||
| COMPLIANCE | FC-198 | Complaints | Rejection and Return to Analyst | Licensed Complaints | If the manager rejects a complaint, the system | |||
| must reject it and return it to the analyst for corrections. | Critical | Mandatory | ||||||
| COMPLIANCE | FC-199 | Complaints | Resubmission for Manager Review | Licensed Complaints | After the analyst corrects the complaint, | |||
| the system must allow them to resubmit it to the manager for review. | High | Mandatory | ||||||
| COMPLIANCE | FC-200 | Complaints | Complaint Closure | Licensed Complaints | The system must allow the manager to confirm and close the complaint once it has been reviewed and approved. | High | Mandatory | |
| GLOBAL | FG-01 | Global | Cite and Fines | Issue Citation | The system shall allow a Field Employee to select Issue Citation when retrieving a License on DCC Portal. | Critical | Mandatory | |
| GLOBAL | FG-02 | Global | Cite and Fines | Issue Citation | The system shall allow a Field Employee to complete DCC Form 8107 to draft the citation. | Critical | Mandatory | |
| GLOBAL | FG-03 | Global | Cite and Fines | Issue Citation | The system shall generate a citation Fee if a template is used to document the citation. | Critical | Mandatory | |
| GLOBAL | FG-04 | Global | Cite and Fines | Issue Citation | The system shall allow the Field Employee to forward the citation to Supervisor/Assistant Branch Chief for review and approval. | Critical | Mandatory | |
| GLOBAL | FG-05 | Global | Cite and Fines | Issue Citation | The system shall notify the Supervisor/Assistant Branch Chief when a citation is pending review. | Critical | Mandatory | |
| GLOBAL | FG-06 | Global | Cite and Fines | Issue Citation | The system shall allow the Supervisor/Assistant Branch Chief to modify the citation or add comments to the citation for Field Employee to review. | Critical | Mandatory | |
| GLOBAL | FG-07 | Global | Cite and Fines | Issue Citation | The system shall allow the Supervisor/Assistant Branch Chief to approve and forward the citation to Legal for review. | Critical | Mandatory |
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 .