SOLUTION REQUIREMENTS Clause Samples

SOLUTION REQUIREMENTS. TECHNICAL REQUIREMENTS

SOLUTION REQUIREMENTS those requirements that define the Supplier Solution based on Solution Components;

SOLUTION REQUIREMENTS. 8.1.1. All solution requirements are documented in a software requirement specification. 8.1.2. ▇▇▇▇▇▇▇ software engineers develop the solution according to the software requirements specification. 8.1.3. An independent team of testers conducts verification testing to confirm that the requirements have been met. 8.1.4. Confidential ▇▇▇▇▇▇▇ test data are adequately protected, controlled, and removed from environments used for development and testing. 8.1.5. All changes to the production environment require approval by a cross-functional team in a formal design review or change board. Risks are identified, evaluated, and addressed according to strict internal procedures. 8.1.6. Access to code and the development and production environments is secured rigorously and is only possible from the ▇▇▇▇▇▇▇ internal network, subject to passing MFA, and, in case of the production environment, only from specially dedicated, hardened machines.

SOLUTION REQUIREMENTS. For all work, standard practices and tools will be utilized to manage service delivery, including but not limited to:

SOLUTION REQUIREMENTS. The Supplier Solution shall be an Open Access Network which supports the UK's broadband policy objectives by providing Retail Service Providers the Wholesale Access Products and Services through Solution Components that can support Take-up.

SOLUTION REQUIREMENTS. The Contractor’s solution must: A. Adhere to CDT’s SIMM 140 Cloud Security Guide (▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/policy/simm), State Administrative Manual (▇▇▇), and SIMM requirements for the State of California. B. Strive to align with SIMM 25 A for accessibility of user interfaces and solution output as applicable. C. Ensure the GenAI solution integrates with CDT’s managed cloud environments. D. Utilize a pre-trained, fully functional GenAI solution. E. Retrieve, store, and analyze log data from all workloads. F. Provide performance analysis information of all potential workloads to determine resources and cost consumption. G. Demonstrate that the solution has implemented network access controls to restrict unnecessary network traffic. H. Demonstrate the solution’s ability to encrypt data at rest and in transit. I. Integrate with CDT’s enterprise Security Information and Event Management (SIEM) solution and allow CDT the ability to monitor logs (per SIMM 140). J. Demonstrate the methodology to detect and report security vulnerabilities. K. Be scalable to accommodate additional data sets as they become available. L. Be user-friendly, intuitive, and accessible to an unlimited number of CALTRANS users from a browser-based network connection to the hosted POC environment. M. Store all State Data, as defined in Section 14 - Data Handling and Ownership, within CDT’s managed cloud environments. State Data may be stored in the Contractor’s managed cloud environments only for the specific purposes of tuning to prepare data for the GenAI solution. State Data may not remain in the Contractor’s managed cloud environments outside of these specific activities. N. Acquire publicly available data as required to demonstrate the solution. The scope of publicly available data will include available data on and off the State Highway System (SHS) that impact safety and inform related factors such as environment, geographic, and equity on the SHS. This data may include incident reporting and clearance times, roadway weather and environmental data, crash data, traveler information feeds, and other data deemed relevant to achieving the objectives of the POC. O. Identify locations in different areas of the state on the State Highway System with high risk of crash incidents based on established criteria and by looking at roadway user vulnerabilities, non-conducive speeding trends, and areas that can benefit from speed management as well as separating users in space. P. Recommend potential so...

SOLUTION REQUIREMENTS. Hardware and Software requirements Services Included Hand Hygiene NZ Application: Connectivity: During initial roll-out ADHB will ensure that << System upgrades: System upgrades to latest versions of operating

SOLUTION REQUIREMENTS. One hundred percent of mandatory requirements shall be met at complete implementation. The new system is a portal for all users – including both program and project applicants/personnel and HCD staff – to submit, interact with, and manage project data and information. Detailed requirements are found in Exhibit E (Bidder Requirement Spreadsheet), and workflow view and task relationships can be found in Attachment 4. In addition to the primary eGrants system for Owner Occupied Reconstruction (OOR), MB3 Inc. (MB3) will deliver a 2018 OOR system instance of eGrants for HCD’s 2018 CDBG-DR Owner Occupied Rehabilitation and Reconstruction Program. The 2018 OOR system instance will be an exact duplicate of the eGrants system that MB3 delivered to HCD for the management of its original OOR Program. Costs for the 2018 OOR system instance of eGrants are limited to the effort to configure, test, and deploy the new instance, as well as ongoing maintenance and operations. There are no additional versions of the deliverables in Exhibit D required for the 2018 OOR system instance as it is a replica of the initial eGrants system implementation. As a high-level overview, the solution provided shall include the following:  Creation, deployment, receipt and analysis of customizable full grantapplications based on survey results.  2018 eGrant creation, deployment, receipt and analysis of customizable full grant applications based on survey results to be completed within 60 days of contract execution.  Homeowner rehabilitation/reconstruction grant application, review, selection, reporting, oversight and data compilation  Assignable workflow management  Storage, search, and retrieval of project records and documents  Calculate, complete and track Duplication of Benefits  Management and tracking of project communications and grantee relationships  Analysis of project data and report compilation  Centralize and link all related program and project information and documents  Aggregate accomplishments across projects and report on those accomplishments  Data transfer with the State’s new Grant Management System  Standardize common practices and procedures  Security functionality for protecting all Personal Identifiable Information (PII) 8.1 SYSTEM GENERATED GRANT MANAGEMENT REPORTING

SOLUTION REQUIREMENTS. The Customer must comply with the following requirements in order to receive the Email Migration Services • Customer just have their own registered and active domain name. • The following email clients are supported as source clients by the Email Migration Services: o Microsoft Office 365 o Exchange 2003+ o G Suite/Gmail o IMAP o POP The exact Customer data that will be migrated will differ based on the source and destination mail client, as set out in the table below. Source 🡫 Email Calendar Contacts Notes Tasks Email Calendar Contacts Notes Tasks Microsoft Office 365 ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Microsoft Exchange ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ G Suite / Gmail ✓ ✓ ✓ ✓ ✓ ✓ IMAP ✓ ✓ POP ✓