Attachment A - Requirements 2025.xlsx
XLSX spreadsheet 32 KB Posted
- Attached to
- Cannabis Traceability
- Solicitation number
- 2025-01
- Issued by
- Thurston County, Washington
About this file
This is a requirements document from the Washington State Liquor and Cannabis Board (WSLCB) detailing technical specifications for a new cannabis traceability system to replace their current Cannabis Central Reporting System (CCRS). The document outlines mandatory and recommended system requirements across multiple functional areas including WSLCB systems integration, data management, reporting, technology/security, public health and safety, and testing capabilities. The system must integrate with existing WSLCB platforms like LEEADS (Licensing, Education, Enforcement, and Administrative Data Systems), support end-to-end cannabis tracking from cultivation to sale, enable product recalls, facilitate lab testing data management, and provide robust security features.
The technical requirements emphasize the need for scalability, API integration capabilities with other state agencies, modern security protocols including multi-factor authentication, and performance standards such as 99.9% uptime. The system must support multiple user types including WSLCB staff, licensees, and integrators with appropriate role-based access controls. Key functionalities include real-time data tracking, reporting capabilities, document management, and integration with various point-of-sale systems. The document presents these as part of an RFI process to gather vendor information for preparing a feasibility study and future funding requests, though specific pricing and funding details are not included.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 2025-01-RFI-Cannabis Traceability.docx | DOCX document |
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
Instructions
| Information |
| Requirements related to Priority: |
Must = Mandatory Should = Should Have
| Instructions |
| In the Notes field (Column E), please provide the following indication for your solution: |
M - Meets the requirement C - Can meet the requirement D - Does not meet the requirement Please send this workbook back to the procurement coordinator, by the date and time listed on the RFI.
Requirements # Requirement Priority Scope of Work Notes M - Meets the requirement C - Can meet the requirement D - Does not meet the requirement
| 4.1.1.1 | The system must integrate with all WSLCB business and enforcement systems | Mandatory | WSLCB Systems Integration |
| 4.1.1.1.1 | The system must integrate with LEEADS (Licensing, Education, Enforcement, and Administrative Data Systems), a Salesforce platform, to provide detailed or summarized historical views into licesee information, such as updates and status, payments and fees, respective connected integrators, licensee types, etc. | Mandatory | WSLCB Systems Integration |
| 4.1.1.1.2 | The system should be able to access relevant historical data from previous systems related to licensee accounts. | Should Have | WSLCB Systems Integration |
| 4.1.1.1.3 | The system must allow integration and/or access to other WSLCB's systems, to include Public Disclosure system, Laserfiche, ArcGIS, Enforcement Notebook, Tax and Fee. | Mandatory | WSLCB Systems Integration |
| 4.1.2.1 | The system must support traceability of cannabis from cultivation to sale of product. | Mandatory | Data Management |
| 4.1.2.1.1 | The system must provide authorized WSLCB staff the ability to add or change new products and services as required. | Mandatory | Data Management |
| 4.1.2.1.2 | The system must provide authorized WSLCB staff the ability to add or change multi-product types, such as joint cream with multi-strains, party packs, etc. | Mandatory | Data Management |
| 4.1.2.1.3 | The system must provide authorized WSLCB staff the ability to add or change new product types other than cannabis, such as psilocybin, synthetics, hemp products, etc. | Mandatory | Data Management |
| 4.1.2.1.4 | The system must be able to track and trace all cannabis products from cultivation to sale of product. | Mandatory | Data Management |
| 4.1.2.1.5 | The system must be able to track/assign unique identifiers for individual plants, plant groups, and lots. | Mandatory | Data Management |
| 4.1.2.1.6 | The system must preserve the linkage between parent and child lots throughout the supply chain, regardless of product transformation. | Mandatory | Data Management |
| 4.1.2.1.7 | The system must provide WSLCB staff with visibility into product pricing, including sales and purchases, throughout the supply chain. | Mandatory | Data Management |
| 4.1.2.2 | The system must provide authorized WSLCB staff or the system developer the ability to add or modify system components pertaining to data fields and validation, drop down lists, error messaging, etc. | Mandatory | Data Management |
| 4.1.2.2.1 | The system must allow authorized WSLCB staff or the system developer the ability to add or modify required fields. | Mandatory | Data Management |
| 4.1.2.2.2 | The system must allow authorized WSLCB staff or the system developer the ability to enhance or modify data validation rules and error messaging. | Mandatory | Data Management |
| 4.1.2.2.3 | The system must allow authorized WSLCB staff or the system developer to modify system business rules, including field logic, data calculations, etc. | Mandatory | Data Management |
| 4.1.2.2.4 | The system must allow authorized WSLCB staff or the system developer the ability to add or modify drop down lists, order of presentation, respective radio buttons or check boxes, etc. | Mandatory | Data Management |
| 4.1.2.2.5 | The system must allow authorized WSLCB staff or the system developer full control over job scheduling and sequencing, batch processing, maintenance, and system troubleshooting. | Mandatory | Data Management |
| 4.1.2.3 | The system must allow authorized WSLCB staff to utilize special circumstances flags. | Mandatory | Data Management |
| 4.1.2.3.1 | The system must integrate with LEEADS, providing authorized WSLCB staff the ability to view, add, or update notes, comments, flags, and alerts. | Mandatory | Data Management |
| 4.1.2.3.2 | The system must integrate with LEEADS to view, add, or update flags on records indicating special circumstances and or handling, such as licensee violations, temporary licensee suspensions, etc. | Mandatory | Reporting |
| 4.1.2.3.3 | The system must be able to place flags related to special circumstance alerts (pesticides, recalls, upload errors or issues, etc.) | Mandatory | Public Health and Safety |
| 4.1.2.4 | The system must support the identification and issuance of product recalls. | Mandatory | Public Health and Safety |
| 4.1.2.4.1 | The system must provide product identification concerning recalls of affected products. | Mandatory | Public Health and Safety |
| 4.1.2.4.2 | The system must provide authorized WSLCB staff the ability to block transfers for specific products related to recalls. | Mandatory | Public Health and Safety |
| 4.1.3.1 | The system should provide access and integration to LEEADS to obtain respective forms, templates, documents, etc. | Should Have | WSLCB Systems Integration |
| 4.1.3.1.1 | The system should integrate with LEEADS to provide searchable access to a central repository of forms or templates (e.g., letters, reports, data request etc.) that authorized WSLCB staff may need related to cannabis traceability. | Should Have | WSLCB Systems Integration |
| 4.1.3.1.2 | The system should allow integration with WSLCB's DocuSign system. | Should Have | WSLCB Systems Integration |
| 4.1.4.1 | The system should be intuitively usable by licensees, integrators, and WSLCB staff. | Mandatory | Technology and Security |
| 4.1.4.1.1 | The system should have external user interface screens designed and configured in conjunction with WSLCB staff and select end-user input. | Should Have | Technology and Security |
| 4.1.4.1.2 | The system should meet industry standards for usability and "look and feel" for all public-facing screens when accessed via personal computer, mobile device, and other personal digital devices | Should Have | Technology and Security |
| 4.1.4.1.3 | The system should have the ability for spell check to be available in any field. | Should Have | Technology and Security |
| 4.1.4.1.4 | The system should support keyboard and/or mouse shortcuts for common functions such as copy and paste. | Should Have | Technology and Security |
| 4.1.4.1.5 | The system should provide clear and descriptive error messages and integrate with online help functions. | Should Have | Technology and Security |
| 4.1.5.1 | The system must provide tools and functions necessary to support WSLCB and customer service-related needs. | Mandatory | Technology and Security |
| 4.1.5.1.1 | The system must provide robust access and functionality related to email messages, chats or chat bots, searchable Frequently Asked Questions (FAQs) or self-help information, etc. | Mandatory | Technology and Security |
| 4.1.5.1.2 | The system must provide training information and a support a training program for all users regarding usage of the system. | Mandatory | Technology and Security |
| 4.1.5.1.3 | The system must provide access to, or integration with Knowledge-Based Articles (KBAs) and help documentation. | Mandatory | Technology and Security |
| 4.1.5.1.4 | The system should include a feature for licensees to submit suggestions for consideration. | Should Have | Technology and Security |
| 4.1.5.2 | The system must provide ticketing (service and incident management) capabilities. | Mandatory | Technology and Security |
| 4.1.5.2.1 | The system must support the ability for users to submit tickets regarding service requests or issues with the system, either through the system directly or via WSLCB ticketing system. | Mandatory | Technology and Security |
| 4.1.6.1 | The system should support the future use of RFID (Radio-Frequency Identification) tags, at the discretion of the licensee or WSLCB. | Should Have | Data Management |
| 4.1.6.1.1 | The system should allow the integration of data upon scan of RFID tags. | Should Have | Data Management |
| 4.1.6.1.2 | The system should allow communication with RFID tags from other states. | Should Have | Data Management |
| 4.1.6.1.3 | The system should allow all product types (flowers, lots, etc.) from producers/processors to facilitate RFID tagging. | Should Have | Data Management |
| 4.1.6.1.4 | The system vendor should offer an option of RFID tags for purchase by all producers/processors. | Should Have | Data Management |
| 4.1.6.2 | The system must facilitate the addition of retailers, producers, processers and other regulated business entities in Washington State and other states. | Mandatory | Data Management |
| 4.1.6.2.1 | The system must be scalable, allowing the addition and updates of new licensee types. | Mandatory | Data Management |
| 4.1.6.2.2 | The system must support the future ability to create, maintain state identification. (Example: interstate commerce) | Mandatory | Data Management |
| 4.1.6.3 | The system must support the acceptance and storage of Lab testing data and facilitate WSLCB business rules based on testing data. | Mandatory | Testing |
| 4.1.6.3.1 | The system must provide authorized WSLCB staff the ability to customize cannabis testing thresholds with actionable outcomes when thresholds are met/not met based on WSLCB business rules. | Mandatory | Testing |
| 4.1.6.3.2 | The system must provide the ability to generate a Certificate of Analysis (COA) based on Lab submitted data. | Mandatory | Testing |
| 4.1.6.3.3 | The system must support the future ability to validate COA from out of state users based on WSLCB rules. | Mandatory | Testing |
| 4.1.6.3.4 | The system must link the COA from the original batch to the final product throughout the supply chain, maintaining the link despite product transformations. | Mandatory | Testing |
| 4.1.6.3.5 | The system must identify and track products that meet WA State Department of Health (DOH) standards for tax-exempt sales to patients. | Mandatory | Testing |
| 4.1.6.4 | The system must provide authorized WSLCB staff the ability to communicate, and lock or release products to support rules, prevent diversion, and address public health and safety. | Mandatory | Public Health and Safety |
| 4.1.6.4.1 | The system must provide authorized WSLCB staff the ability to lock and release the commerce (between licensees) and sale of products to the public. | Mandatory | Public Health and Safety |
| 4.1.6.4.2 | The system must provide the ability to communicate with user or licensee via direct and mass messaging (Example: Email, chat, dashboard banner pop up, etc.) | Mandatory | Public Health and Safety |
| 4.1.6.4.3 | The system must provide the ability for authorized WSLCB staff to view, add, and update communication notifications to respective licensees and integrators regarding recalls or status of recalls (Dashboard banner pop up, etc.) | Mandatory | Public Health and Safety |
| 4.1.6.5 | The system must provide licensees with the ability to request the amendment of previously filed reports | Mandatory | Reporting |
| 4.1.6.5.1 | The system must require approval by authorized WSLCB Staff before implementing proposed report amendments. | Mandatory | Prevention of Diversion |
| 4.1.6.5.2 | The system must provide licensees with the ability to request to amend previously filed reports or data | Mandatory | Reporting |
| 4.1.6.5.3 | The system must provide licensees the ability to view previously filed reports that have been amended. | Mandatory | Reporting |
| 4.2.1.1 | The system must allow licensees and contracted integrators to submit, and view required reporting documentation. | ||
| Mandatory | Reporting | ||
| 4.2.1.1.1 | The system must allow integrators the ability to upload and apply cannabis traceability data for multiple licensees at one time. | Mandatory | Data Management |
| 4.2.1.1.2 | The system must allow licensees to submit and view data reports for them by authorized WSLCB staff, as required. | Mandatory | Data Management |
| 4.2.1.1.3 | The system should include a search function for accessing current and past uploads, reports, and data by WSLCB staff, licensees, and integrators. | Should Have | Data Management |
| 4.2.1.1.4 | The system should include a search function that allows WSLCB staff, licensees, and integrators to filter uploads by success or failure status. | Should Have | Data Management |
| 4.2.2.1 | The system must allow the creation and maintenance of privilege profiles for internal and external users. | Mandatory | Technology and Security |
| 4.2.2.1.1 | The system must provide an "administrator" role to manage system functions, capabilities, rules, tables and standard user profiles. | Mandatory | Technology and Security |
| 4.2.2.1.2 | The system must be able to assign multiple security profiles to a single user but prevent multiple security profiles applied to a single user if the profiles are in conflict. | Mandatory | Technology and Security |
| 4.2.2.1.3 | The system must allow authorized WSLCB staff or licensee to disable user profiles from accessing the system. | Mandatory | Technology and Security |
| 4.2.2.1.4 | The system must allow authorized WSLCB staff to easily configure and maintain security profiles which grant and limit access to specific system functions and data. | Mandatory | Technology and Security |
| 4.3.1.1 | The system must support the ability for authorized WSLCB staff to create, update, identify, and maintain data. | Mandatory | Data Management |
| 4.3.1.1.1 | The system must provide authorized WSLCB staff the ability to create, alter and maintain data thresholds and allow the proactive flagging of data anomalies and take actionable outcomes based on WSLCB business rules. (Low/High yields, High Waste %, etc.) | Mandatory | Data Management |
| 4.3.1.1.2 | The system must provide point-in-time data and real-time data including historical data references. | Mandatory | Data Management |
| 4.3.1.1.3 | The system must allow authorized WSLCB staff the ability to input, update, and maintain data uploads on behalf of a licensee | Mandatory | Data Management |
| 4.3.1.1.4 | The system must allow authorized WSLCB staff to edit and update all table values, rules engine entries and must incorporate the effective date during processing. | Mandatory | Data Management |
| 4.3.1.2 | The system should be able to accept upload of cannabis reporting data and validate based on WSLCB business rules. | Should Have | Technology and Security |
| 4.3.1.2.1 | The system should be able to accept upload of user submitted data (Sales, Tax, Manifest, Inventory, etc.) based on WSLCB business rules. | Should Have | Technology and Security |
| 4.3.1.2.2 | The system should provide the ability to setup data upload validation based on WSLCB business rules. | Should Have | Technology and Security |
| 4.3.1.3 | The system must capture, store, and maintain all data entered into or generated by the system. | Mandatory | Data Management |
| 4.3.1.3.1 | The system must capture, store, and maintain all data pertaining to licensee sales and transactions with all questions and responses, certifications, attestations, etc. | Mandatory | Data Management |
| 4.3.1.3.2 | The system must provide, store, and retrieve transaction information detailing all information provided by the licensee and WSLCB decisions on exceptions | Mandatory | Data Management |
| 4.3.1.3.3 | The system must allow authorized WSLCB staff full access to Licensee accounts and all data (creation, alteration, suspension, flag, data insertion, etc.) | Mandatory | Data Management |
| 4.3.2.1 | The system must be capable of performing data validation based on WSLCB business rules and requirements. | Mandatory | Data Management |
| 4.3.2.1.1 | The system must provide authorized WSLCB staff the ability to create, update, and maintain data validation rules for data uploads. | Mandatory | Data Management |
| 4.3.2.1.2 | The system must provide authorized WSLCB staff the ability to create, update, and maintain data validation rules for data adjustments. | Mandatory | Data Management |
| 4.3.3.1 | The system must capture, store, and maintain data to generate reports to fulfill Public Disclosure requests. | Mandatory | Reporting |
| 4.3.3.1.1 | The system must allow authorized WSLCB staff to flag fields as sensitive or confidential and restrict access which will redact personal information based on the flag. | Mandatory | Reporting |
| 4.3.3.1.2 | The system must allow authorized WSLCB staff to create, update and maintain reports encompassing Public Disclosure data (Sales, Manifest, etc.) per WSLCB business rules. | Mandatory | Data Management |
| 4.3.4.1 | The system must be able to create, update, and maintain data reports. | Mandatory | Data Management |
| 4.3.4.1.1 | The system must provide statistical reports based on WSLCB requirements, customer service expectations and business rules. | Mandatory | Reporting |
| 4.3.4.1.2 | The system must provide ability to create, modify, and maintain reports for all data points collected from licensees and integrators (sales, tax, inventory, manifest, etc.) | Mandatory | Reporting |
| 4.3.4.1.3 | The system must provide the ability for authorized WSLCB staff to create, modify and maintain data reports that can be used by Licensees | Mandatory | Reporting |
| 4.3.4.1.4 | The system must provide the ability for authorized WSLCB staff to create, update, and maintain ad-hoc reports | Mandatory | Reporting |
| 4.3.4.1.5 | The system must store ad-hoc report templates for future use in either a personal or shared repository that allows authorized WSLCB users to easily search for and reuse. | Mandatory | Reporting |
| 4.3.4.1.6 | The system must provide the data analytics to authorized WSLCB staff. (linking Manifest to Sales data, etc.) | Mandatory | Data Management |
| 4.3.4.1.7 | The system should be able to export queries or data to be used by Power BI or other analysis and reporting applications. | Should Have | Technology and Security |
| 4.3.4.1.8 | The system must notify WSLCB, the shipper, and the receiver upon the creation or update of a manifest. | Mandatory | Technology and Security |
| 4.4.1.1 | The system must be accessible using remote and on-premise access through Secure Access Washington (SAW) and Active Directory. | Mandatory | Technology and Security |
| 4.4.1.1.1 | The system must facilitate integration with WSLCB's Active Directory for authentication and authorization of internal user access. | Mandatory | Technology and Security |
| 4.4.1.1.2 | The system must facilitate integration with WaTech's Secure Access Washington (SAW) for authentication and authorization of external user access | Mandatory | Technology and Security |
| 4.4.1.1.3 | The system must provide remote access capability to WSLCB Users if they work in remote location, out of state or on-site premise visits. | Mandatory | Technology and Security |
| 4.4.1.1.4 | The system must provide single sign-on capability allowing users to access authorized modules and features without separate log-in. | Mandatory | Technology and Security |
| 4.4.1.1.5 | The system must provide support for Multi-Factor Authentication (MFA). | Mandatory | Technology and Security |
| 4.4.1.2 | The system must meet appropriate security safeguards as defined by OCIO. | Mandatory | Technology and Security |
| 4.4.1.2.1 | The system must provide role-based user access to all system functions. | Mandatory | Technology and Security |
| 4.4.1.2.2 | The system must allow only authorized and authenticated WSLCB staff and licensees access to the system and data. | Mandatory | Technology and Security |
| 4.4.1.2.3 | The system must automatically notify appropriate WSLCB staff if there are attempts to breach system authorized security level, based on WSLCB business rules. | Mandatory | Technology and Security |
| 4.4.1.2.4 | The system must be able to timeout a user session or suspend a user after a predetermined period of non-activity at the workstation or on a device. At a minimum, section 6.4 (6) of OCIO IT Security Standards specifies a period of 30 minutes. | Mandatory | Technology and Security |
| 4.4.2.1 | The system must meet compatibility requirements. | Mandatory | Technology and Security |
| 4.4.2.1.1 | The system must be scalable and to be compatible with Standard Query Language (SQL) Server 2016 and higher. | Mandatory | Technology and Security |
| 4.4.2.1.2 | The system must be compliant with Service Oriented Architecture (SOA), modular in nature, and integrate or interface with other components/systems within WSLCB as needed. | Mandatory | Technology and Security |
| 4.4.2.1.3 | The system must utilize standard email protocols (e.g., Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), Post Office Protocol 3 (POP3), Simple Mail Transfer Protocol (SMTP), etc.). | Mandatory | Technology and Security |
| 4.4.2.1.4 | The system must support industry standard web browsers based on WSLCB and OCIO standards. WSLCB staff use current versions of Chrome, Firefox, and Microsoft Edge; for external users the must also support major Apple product browsers (e.g., Safari). | Mandatory | Technology and Security |
| 4.4.2.1.5 | The system must support multiple OS (Operating System) variations such as Apple, Windows, Linux, etc. | Mandatory | Technology and Security |
| 4.4.2.1.6 | The system and respective websites or dashboards must comply with WCAG 2.1 Level AA accessibility standards (ADA American's with Disabilities). | Mandatory | Technology and Security |
| 4.4.3.1 | The system must capture, store, maintain and backup all data entered into or generated by the system. | Mandatory | Technology and Security |
| 4.4.3.1.1 | The system must be capable of capturing, storing, and maintaining all data transactions and information provided by licensees, WSLCB staff, or other authorized users, using secure storage or backup methods (creation, updates, attachments, questions, responses, certifications, attestations, etc..). | Mandatory | Technology and Security |
| 4.4.3.1.2 | The system must be able to utilize WSLCB's or WaTech's defined backup and storage architecture and processes. | Mandatory | Technology and Security |
| 4.4.5.1 | The system must provide tools to facilitate API (Application Programming Interface) Key Management. | Mandatory | Technology and Security |
| 4.4.5.1.1 | The system must provide authorized WSWSLCB staff or the system developer the ability to manage API Keys (creation, deletion, restrictions, etc.). | Mandatory | Technology and Security |
| 4.4.5.1.2 | The system must provide an API to allow licensees and integrators to access and upload data from external systems and applications. | Mandatory | Technology and Security |
| 4.4.5.1.3 | The system must provide API access to Washington State agencies (DOH, DOR, etc.) and third parties. | Mandatory | Technology and Security |
| 4.4.5.1.4 | The system must allow API to accept uploads of all reporting requirements based on WSLCB rules. | Mandatory | Technology and Security |
| 4.4.5.1.5 | The system must be able to work with different point of sale systems and establish APIs to allow integration and access from licensees. | Mandatory | Technology and Security |
| 4.4.5.2 | The system must be capable of API integration with other state and federal agencies, and third parties. | Mandatory | Technology and Security |
| 4.4.5.2.1 | The system must provide the capability of API integration with the WSP (Washington State Patrol) "Access" (A Central Computerized Enforcement Service System) system. | Mandatory | Technology and Security |
| 4.4.5.2.2 | The system must provide the capability of API integration with the DOR (Department of Revenue) tax reporting system. | Mandatory | Technology and Security |
| 4.4.5.2.3 | The system must provide the capability of API integration with other state and federal agencies, and third parties as required. | Mandatory | Technology and Security |
| 4.4.6.1 | The system must provide security safeguards for user session management | Mandatory | Technology and Security |
| 4.4.6.1.1 | The system architecture must provide user session isolation, so that a failure in one session has no impact on other user sessions. | Mandatory | Technology and Security |
| 4.4.6.1.2 | The system must have established procedures for shutting down and reauthorizing inactive sessions after a defined period of inactivity. | Mandatory | Technology and Security |
| 4.4.6.1.3 | The system must provide data encryption at rest and in transit per industry and Office of the Chief Information Officer (OCIO) standards. | Mandatory | Technology and Security |
| 4.4.7.1 | The system must provide system logging that captures data changes, application access attempts, uploads, etc. | Mandatory | Technology and Security |
| 4.4.7.1.1 | The system must authenticate and log all authorized and unauthorized attempts to access the application, database, session, or transaction. | Mandatory | Technology and Security |
| 4.4.7.1.2 | The system must provide ability to capture any data changes, user that performed the changes, date/time stamps of changes, etc. | Mandatory | Technology and Security |
| 4.4.7.1.3 | The system must allow authorized WSLCB staff access to all logs | Mandatory | Technology and Security |
| 4.4.8.1 | The system must be structured for optimal performance. | Mandatory | Technology and Security |
| 4.4.8.1.1 | The system must allow for multiple types of activities to occur concurrently and allow concurrent user access to update (ticket creation, updates, attachments, etc.) without loss of information for all updates/activity. | Mandatory | Technology and Security |
| 4.4.8.1.2 | The system must allow system administrators to control the priority and sequencing of batch processes based on operational guidelines. | Mandatory | Technology and Security |
| 4.4.8.1.3 | The system should maintain application performance of returning results/saving 90% of the time in 3 seconds or less, and 100% of the time in less than 10 seconds. | Should Have | Technology and Security |
| 4.4.8.1.4 | The system must be structured to allow queries to be run at any time without degrading the performance of other core business services and systems. | Mandatory | Technology and Security |
| 4.4.8.1.5 | The system must allow the person who initiated or a query, and a system administrator to terminate or cancel the query while it is either processing or printing. | Mandatory | Technology and Security |
| 4.4.8.1.6 | The system must provide system performance reporting, and on demand scaling for resources such as storage, servers, etc. to meet performance and availability. | Mandatory | Technology and Security |
| 4.4.8.1.7 | The system architecture must ensure batch processing does not interfere with online responsiveness, performance, or availability. | Mandatory | Technology and Security |
| 4.4.8.1.8 | The system architecture must be structured in a way that increasing number of concurrent users does not impact performance of core business services and systems. | Mandatory | Technology and Security |
| 4.4.8.1.9 | The system architecture must be redundant and fault tolerant allowing automated failover capability, providing 99.9% up-time. | Mandatory | Technology and Security |
File details come from the government source that posted it. Updated .