The file's text, extracted by GovTribe without its formatting.
RFP SCC-26-018-BFI: Short-Term Lending Database
Exhibit A: Services Agreement
< Insert Offeror Name >
1 DEFINITIONS
| Acceptance Criteria |
| The criteria established by the Agreement and Implementation Plan, or otherwise in writing by the Parties, to confirm that a Deliverable meets its functional, technical, design, and performance specifications in all material respects. |
| Acceptance or Accepted |
| The written determination in SCC’s sole but reasonable discretion that the delivery and performance of the Services, a Deliverable, or a Component conforms with all technical, design, and functional specifications of the Agreement, the Requirements, the Acceptance Criteria, Third Party Vendor Documentation, and all other applicable requirements agreed upon in writing by the Parties. |
| Affected Services |
| The Services that will cease to be performed in whole or in part by Supplier upon expiration of the Agreement or because of termination. |
| Affiliate |
| With respect to an entity, any other entity or person that has a ten (10) percent or more voting or economic interest in that entity or controls, is controlled by, or is under common control by that entity, whether directly or indirectly through management, share ownership, a trust, joint venture, partnership, contract, or otherwise. |
| Application |
| The software programs in object code and other related data, including intellectual data, proprietary information and Documentation, and any Licensed Services hosted and supported by Supplier under the Agreement as part of the Solution or as described in the Requirements, including any updates, enhancements, and replacements to the Application. |
| Application User(s) or Users |
| All individuals and entities authorized by SCC to use the Application as well as customers, suppliers, members of the public, and other entities who may be provided access to the use the Application pursuant to the Agreement. |
| Artificial Intelligence or AI |
| An engineered or machine-based system that can, for a given set of objectives, generate outputs such as predictions, recommendations, or decisions influencing real or virtual Environments, designed to operate with varying levels of autonomy. |
| Bureau |
| Bureau of Financial Institutions, a division of the State Corporation Commission. |
| Business Continuity Plan |
| The documented, company-wide resources and processes implemented to ensure that Supplier can maintain or promptly resume its business operation and delivery of the Services during and after a System failure, disaster, disruption, Security Incident, interruption, or similar occurrence. The plan addresses continuity of critical business functions, Supplier Personnel, Supplier Facilities, Systems, and includes industry-standard measures for preparedness, response, and recovery to minimize the impact of an interruption on the business. |
| Business Day |
| Any day on which the Licensee is able to make loans pursuant to Chapter 18 of Title 6.2 (§ 6.2-1800 et seq.) of the Code of Virginia |
| Change |
| A modification of the scope of the Services or Solution, including any Deliverable, Milestone, due date, or related obligation of Supplier, within the general scope of the Agreement. |
| Claim |
| Any demand or any civil, criminal, administrative, action, lawsuit or proceeding, whether commenced or threatened, asserted by an entity, person, or Governmental Authority. |
| Cloud Provider |
| Means any third party Cloud Services provider utilized by Supplier to host the Application or any Services or Component, or Supplier, if it is fulfilling such role. |
| Cloud Services |
| A collection of services and infrastructure to provide hosted computing capacity or Software services typically available via the public Internet. |
| Commencement Date |
| The date upon which at least a portion of the Services first commence in the production Environment under the Agreement, following the completion of Implementation for such Services. The expected Commencement Date is set forth in the Implementation Plan as an Implementation Milestone. |
| Commonwealth |
| The Commonwealth of Virginia, including its agencies and departments. |
| Component |
| Any part or grouping of the Solution, Application, Deliverable, or Services provided by Supplier under the Agreement. |
| Content |
| Any data, including the selection, arrangement and organization of such data, entered or uploaded to the Application by any Application User, and any information or data, from whatever source, provided by SCC or Application User to Supplier for use with the Solution or in connection with the Agreement. |
| DSBSD |
| The Commonwealth of Virginia Department of Small Business and Supplier Diversity. |
| Database |
| Short-term lending database, a real-time and internet-accessible database that contains such short-term loan information as the State Corporation Commission may require, used in business of making short-term loans under Chapter 18 of Title 6.2 (§ 6.2-1800 et seq. of the Code of Virginia). |
| Database Inquiry Fee |
| Pursuant to Code § 6.2-1810(B)(4) and 10 VAC 5-200-115, the compensation payable to Supplier based on short-term loans consummated between Licensees and borrowers pursuant to Chapter 18 of Title 6.2 of the Code of Virginia. The Database Inquiry Fee is established periodically through an order of the State Corporation Commission and shall bear a reasonable relationship to the actual cost of the operations of the database. All Database Inquiry Fees are paid to Supplier by Licensees. |
| Deliverable |
| Software, Documentation, Components, plans, reports, data, Work Product, Materials, items, or events, in each case described or itemized as something that is developed, prepared, or created and delivered, or required to be developed, prepared, or created and delivered, or made available to SCC as part of the Services, Solution, Software, or Application. It also means any improvements, enhancements, modifications or customization made to Supplier Materials as part of or in the course of performing the Services. |
| Disaster Recovery Plan |
| A documented set of technical resources and processes implemented to restore Supplier’s Systems and the Solution, Application, and any Component to operational status following a disruption, System failure, disaster, disruption, or similar occurrence. The plan must include all restoration, failover, and recovery strategies necessary to meet the Requirements and to ensure timely resumption of the Services. |
| Documentation |
| The written materials, specifications, technical manuals, training materials, guides, flow diagrams, file descriptions, notes and other written information, including as may be associated with a Deliverable, System, Component, or otherwise in connection with the Services, required by the Agreement or required to facilitate use of the Application and Solution by SCC and Application Users. |
| eVA |
| The Commonwealth’s electronic procurement portal website at http://www.eva.virginia.gov. |
| Employment Services Organization |
| As defined by Virginia Code § 2.2-4310. |
| Environment |
| Means a subset of the infrastructure that is used for a particular purpose. For Example: live Environment, test Environment, build Environment. Also used to reference physical Environments such as facilities, air conditioning, power systems, etc. |
| Equipment |
| Means the computers, telecommunications, and facility‐related hardware, apparatus, and peripherals (and all modifications, replacements, upgrades, enhancements, Documentation, materials, and media related thereto) that are used in connection with the Services, including by Supplier. |
| Event |
| Means an Incident, a failure of Services, Solution, Application, a Security Incident, a disruption caused by a Non-Conformity, or other interruption in the performance of the Services. |
| Federal Tax Information (FTI) |
| Federal tax returns and federal tax return information (and information derived from them) that is in the possession or control of any Authorized User and which is covered by the confidentiality protections of the Internal Revenue Code and subject to the IRC § 6103(p)(4) safeguarding requirements, including IRS oversight. FTI is categorized as Sensitive Data and may contain Personal Identifying Information. |
| Governmental Authority |
| Any national, state, or local government or governmental, regulatory, or administrative authority, agency, commission, board, bureau, court, or authority having jurisdiction over the Services or the Parties. |
| Implementation |
| The process of creating, building, or developing a Component of the Services to meet the Agreement, Requirements, and needs of the Solution, including analyzing Requirements, installation, configuration, customization, running, testing, systems integrations, User training, delivery, and all associated and necessary refinements and modifications. |
| Implementation Milestone |
| Means a key activity or Deliverable to be provided by Supplier in support of Implementation. |
| Implementation Plan |
| Means the plan by which an Implementation will be performed and which meets all provisions of the Agreement. |
| Incident |
| An occurrence or series of occurrences which cause or may cause disruption to or a reduction in the quality or delivery of Services or impact the use of the Solution or Application by a User. |
| Infrastructure |
| Means the entire portfolio of Equipment, System Software, and network components required for the integrated provision and operation of SCC’s IT systems and Applications. |
| Intellectual Property |
| Any (a) rights associated with works of authorship, including exclusive exploitation rights, copyrights, database rights, moral rights, neighboring rights and mask works; (b) trademark and trade name rights and similar rights and associated goodwill; (c) trade secret rights, know‐how, design guides, design rights, methodologies, developmental tools, techniques, hardware, software, systems, technologies, skills, and processes (including any enhancements, improvements, or modifications thereto); (d) patents and industrial property rights; (e) inventions, discoveries, designs, processes, or other proprietary rights in intellectual property of every kind and nature; and (f) rights in or relating to registrations, renewals, extensions, combinations, divisions, reversions and reissues of, and applications for, any of the rights referred to in subsections (a) through (e) of this sentence. |
| Intellectual Property Rights |
| All past, present, and future rights in and to Intellectual Property that may exist or be created under the Laws of any jurisdiction in the world. |
| Laws |
| Any (i) law, statute, regulation, ordinance or subordinate legislation; (ii) applicable common law; (iii) binding court order, judgement, or decree (including consent agreements); (iv) order, directive, instruction, corrective action plan, directive, mandate, policy or rule that is binding on a Party or any of its Affiliates and that is made or given by a Governmental Authority. |
| Licensee |
| As defined in Code § 6.2-1800, a person to whom a license has been issued under Chapter 18 of Title 6.2 of the Code of Virginia. |
| Licensed Services |
| The operation of the Application, Solution, and/or a Component, and the necessary operating system software, hardware, and utilities on Supplier’s host computer system; furnishing Services to Users; storing Content; and making the Application, Content, and Solution available to Users. |
| Losses |
| All losses, liabilities, damages, liens, Claims, demands, costs, proceedings, suits, actions, assessments, expenses, and other charges suffered or incurred, including reasonable attorneys’ and accountants’ fees and disbursements, costs of investigation, litigation, settlement, and judgment, and any taxes, interest, penalties, and fines (whether criminal or civil), judgments and settlements with respect to any of the foregoing. |
| Materials |
| Collectively, Software, literary works, other works of authorship, documented specifications, designs, analyses, processes, methodologies, concepts, inventions, know‐how, programs, program listings, programming tools, documentation, reports, drawings, databases, spreadsheets, machine‐readable text and files, and financial models, whether tangible or intangible. |
| Milestone |
| A date by which an action or event successfully must be completed, including compliance with all Acceptance Criteria and applicable Requirements and provisions of the Agreement. |
| Non‐Conformity |
| An error, defect, failure to meet Requirements or Acceptance Criteria, or other noncompliance with the Agreement. |
| Personal Identifying Information (PII) |
| All forms of data about an identified or identifiable individual that are: (a) unique identifiers (e.g., SSN, driver’s license, biometric data, IP address); (b) linkable to an individual (e.g., name, email, phone); or (c) Sensitive (e.g., health, financial, reproductive, demographic data). It includes any information covered under Health Insurance Portability and Accountability Act (HIPAA), the Gramm-Leach-Bliley Act (GLBA), the Children's Online Privacy Protection Act (COPPA), Virginia Code § 18.2‑186.6, the Virginia Consumer Data Protection Act (Virginia Code § 59.1-575 et seq.), the Government Data Collection and Dissemination Practices Act (Virginia Code § 2.2-3800 et seq.), and any other applicable state or federal privacy Laws. |
| Protected Health Information (PHI) |
| Any individually identifiable health information that is (i) transmitted in electronic media, (ii) maintained in electronic media, or (iii) transmitted or maintained in any other form or medium. |
| Quality Assurance |
| Actions and processes to review Supplier’s work to ensure and provide confidence that the Services are rendered consistent with the Agreement and that the Solution, Application, Deliverables, and any Component will work as required both individually and collectively. |
| Requirements |
| The functional, performance, operational, compatibility, Acceptance testing criteria, and other parameters and characteristics of the Solution, Services, Application, and Deliverables, including all Components, as set forth in the Agreement, and such other parameters, characteristics, or performance standards that may be agreed upon in writing by the Parties. |
| SCC Data |
| (i) all data and information in any form, whether or not Confidential Information, entered in Software or Equipment, directly or indirectly, by or on behalf of SCC under or in connection with the Agreement, including any data originated or provided by SCC, Supplier, or a Third Party; (ii) all data and information, whether or not Confidential Information, directly or indirectly obtained by Supplier from, in connection with, or as a result of the Services or the Agreement, including in connection with the negotiation and execution of the Agreement; and (iii) all data and information derived from the above information. |
| Security Incident |
| Any (i) circumstance pursuant to which Laws requires notification to be given to affected parties or other activity to be taken in response to an Event, breach of Systems, breach of Agreement, data loss, intrusion, or other computer or data security‐related incident; (ii) actual, attempted, suspected, threatened, or unauthorized access, disclosure, alteration, loss, or destruction of SCC Data; (iii) interference with SCC System; or (iv) occurrence that compromises, or could reasonably be expected to compromise, the security of any SCC Data or SCC System. |
| Security Plan |
| The plan provided by Supplier to support security and data management, in accordance with Exhibit B (Solution Requirements). |
| Sensitive Data |
| Any data of which the compromise with respect to confidentiality, integrity, and/or availability could have a material adverse effect on SCC interests, the conduct of SCC programs, or the privacy to which individuals are entitled by Laws, including PII and PHI. |
| Services |
| The work performed, product supplied, and services to be provided by Supplier, including the design and development of the Solution, Implementation, installation, maintenance, support, testing, training, or other provision of Services, as required by the Agreement. Services include all functions, responsibilities, activities, and tasks of Supplier that are an inherent, necessary, or customary part of the Services, or are required for the proper performance or provision of the Services. As permitted by the Agreement, Services may include the discovery, creation, or development of Work Product. |
| Software |
| Any programs or code consisting of instructions or statements in a form readable by individuals (source code) or machines (object code), and related Documentation and supporting Materials therefore, in any form or medium, including electronic media used by Supplier in the performance of the Services or provided or to be provided by Supplier as a component(s) of any Deliverable or Component, and any subsequent modification of such programs and code. |
| Solution |
| Supplier’s contractually committed technical approach for solving SCC business objectives and to fulfill the Solution Description and Requirements as set forth in the Agreement. Solution means all Supplier and Supplier’s Third Party Vendors, Subcontractors, and Cloud Providers Components making up the Solution, including but not limited to the Application, configuration design, Implementation, Supplier-developed interfaces, Services, and Work Product. |
| Source Code |
| The (a) underlying programming code, including without limitation, all queries, data structures, instructions, routines or objects that exists in the form of programming statements and instructions in connection therewith, that is generally written by, and is readable by, a trained human software developer, but that is not generally directly executable by a computer without first being translated for operation on computer equipment through assembly or compiling, and accompanied by Documentation, in sufficient detail to enable a trained Software developer through study or such Documentation to maintain and/or modify such software without undue experimentation, and (b) all interfaces, compilers and other tools necessary to enable SCC to access, use and operate the software code. The Source Code and object code will be in a format and on a storage medium suitable for loading into the applicable System and will not be encrypted (except to the extent SCC requests otherwise). |
| Subcontractor |
| Any entity to which Supplier (or other Subcontractor of any tier) has subcontracted for performance of, or delegated any of its responsibilities under the Agreement, including an Affiliate of Supplier. |
| Supplier |
| The entity identified in the Agreement as Supplier and all of Supplier’s Affiliates. |
| Supplier Materials |
| Any pre‐existing Materials (including documents, drawings, designs, computer code, or other tangible form or medium in which a work of authorship or expression is fixed; or any invention, business method, or process materials) and Intellectual Property developed by Supplier prior to execution of the Agreement or developed by Supplier independent of its obligations under the Agreement. |
| Supplier Personnel |
| Supplier’s directors, officers, employees, Subcontractors, Third Party Vendors, licensors, representatives, and agents who perform any Services. |
| Support Services |
| Continuous oversight, twenty-four hours a day, seven days a week, to ensure that a device, Application, Solution, Software, Component, or process performs its designated function, including responsibility for performing all necessary repairs, preventive maintenance, patching, upgrades, and performance tuning as required to ensure that the device, Application, Solution, Software, Component, or process operates in without Non-Conformities and in accordance with its normal operations and Requirements. |
| SWaM |
| SWaM refers to the following types of businesses recognized by Virginia Code § 2.2-4310: small businesses; businesses owned by women, minorities, and service-disabled veterans; military family-owned businesses; and Employment Services Organizations. |
| System |
| Hardware, Software, networks, Applications and Equipment that comprise a technical Environment. |
| Third Party |
| Any person or entity that is neither a Party to the Agreement nor an Affiliate of a Party. |
| Transition Out Assistance Period |
| The period during which Supplier is providing or is required to provide Transition Out Assistance. |
| Transition Out Plan |
| The written plan developed by Supplier addressing the transition of Supplier’s contractual obligations, in whole or in part, away from Supplier and to SCC, or its designee, after the expiration or termination of the Agreement. |
| Vendor |
| A supplier of goods or services that is registered with eVA and agrees to furnish goods or services to Supplier or SCC. |
| VITA |
| The Virginia Information Technologies Agency, an agency of the Commonwealth of Virginia pursuant to Chapter 20.1 (§§2.2‐2005 et seq.) of the Code of Virginia. VITA makes available most standards and guidelines at this public website: https://www.vita.virginia.gov/resources/vita‐rules/. |
| Work Product |
| Materials (including documents, drawings, designs, computer code, or other tangible form or medium in which a work of authorship or expression is fixed), in each case produced by Supplier, Supplier Personnel, or Subcontractors as part of the Services and delivered to SCC in the course of performing the Services, including Materials produced jointly with another party. |
| 2 | PERFORMANCE |
| 2.1 | General Responsibility. |
Supplier is responsible for managing and successfully performing, completing, and delivering the Services in conformity with the Agreement. Supplier shall deliver the Solution, including all Documentation, Application(s), and Components, and the Services in the timeframes and Milestones set forth in the Agreement.
| 2.2 | Time of Performance |
| 2.2.1 | Supplier will provide the resources necessary to complete, and will complete, the Services in accordance with the Implementation Plan and the time schedules set forth in the Agreement and in Exhibit E (Deliverables) and will ensure that all Services are available to SCC and fully functional by the dates specified in the Agreement. Supplier agrees that TIME IS OF THE ESSENCE of the Agreement. |
2.2.2 Supplier promptly will notify SCC upon becoming aware of any circumstances that may reasonably be expected to jeopardize the timely and successful completion (or delivery) of any Services. Supplier promptly will inform SCC of the steps Supplier is taking or will take to regain the schedule of activities to ensure timely completion of the Services.
2.2.3 Supplier agrees that failure to meet any one or more of the Milestones or to deliver the Services in accordance with the Agreement shall constitute a material breach resulting in damages to SCC. Unless otherwise excused by a provision of this Agreement, if Supplier is late in satisfying any Milestone or Deliverable by more than thirty (30) days, SCC may terminate the Agreement for material breach, collect damages, and/or pursue any other remedy available under the Agreement or at law or equity, except that SCC shall not assess nor shall it be entitled to collect damages for a day or days of delay solely caused by SCC.
2.3 Manner of Performance.
Supplier will perform the Services in compliance with the Agreement. For matters not covered by Service Level Agreements, Supplier shall perform the Services at levels of accuracy, quality, completeness, timeliness, responsiveness, and resource efficiency that are equal to or higher than the accepted industry standards of leading suppliers of similar services. Supplier shall ensure that the Services, Deliverables, Solution, and Application meet or exceed the Requirements.
2.4 Supplier Personnel.
2.4.1 Supplier shall ensure that all Supplier Personnel are competent and knowledgeable of the Agreement. Supplier shall be solely responsible for the supervision and conduct of Supplier Personnel, including all acts, omissions, gross negligence, and willful misconduct of Supplier Personnel.
2.4.2 SCC at all times maintains the right to require the immediate removal from the Services of any Supplier Personnel whose performance, conduct, or behavior is unacceptable or unprofessional or results in a security or safety breach.
2.5 Quality Assurance.
Supplier represents it has the resources, skill, experience, and qualifications to perform Quality Assurance activities for the Services. Supplier will perform commercially reasonable Quality Assurance processes to ensure that Services are performed in conformance with the Agreement, on a timely basis, and with the required high degree of professional quality and reliability.
2.6 Term and Renewals. The Agreement is effective and legally binding as of the Effective Date and shall continue for an initial period of two (2) years (the “Initial Term”) subject to the Agreement being terminated earlier or extended as provided for by the Agreement. SCC, in its sole discretion, may renew the Agreement for up to three (3) additional two (2) year renewal periods (each a “Renewal Term”) following the expiration of the Initial Term on the terms, conditions, and pricing then in effect. SCC may exercise its intention to exercise a Renewal Term by providing written notice to Supplier no later than thirty (30) days prior to expiration of the then-current term.
3 DATABASE INQUIRY FEES
| 3.1 | Database Inquiry Fees, Generally |
| 3.1.1 | No compensation or Database Inquiry Fees shall be paid to Supplier by SCC. In accordance with Chapter 18 of Title 6.2 (§ 6.2-1800 et seq.) of the Code of Virginia, each Licensee shall pay a Database Inquiry Fee to Supplier for a short-term loan consummated between a Licensee and borrower and such fees will be paid by Licensee directly to Supplier. Supplier shall be responsible for collecting all Database Inquiry Fees directly from Licensees on a weekly basis. SCC is not responsible for reimbursing Supplier, its employees, subcontractors, partners, or third-party providers if any Licensee fails to pay Database Inquiry Fees. |
3.1.2 Database Inquiry Fees collected by Supplier from Licensees are based on the fee schedule established by Commission order. The Commission may use the proposed fee provided by the Supplier in Exhibit F: Proposed Fee & Cost Analysis to inform its approved fee schedule.
3.1.3 Supplier will not be compensated, reimbursed, or paid any other fees, costs, travel, incidentals, or other type of expense unless agreed upon via Change Order executed by both parties.
| 3.2 | Subcontractor Payments |
| 3.2.1 | Within seven (7) days after receipt of amounts paid to Supplier by Licensee for work or services performed by a subcontractor, supplier, or vendor to Supplier under the Agreement, Supplier shall: |
a. Pay the subcontractor, supplier, or vendor for the proportionate share of the total payment received from Licensee attributable to the work or services performed or the Materials furnished by the subcontractor, supplier, or vendor under the Agreement; or
b. Notify SCC and the subcontractor, supplier, or vendor, in writing, of Supplier’s intention to withhold all or a part of the payment with the reason for nonpayment.
3.2.2 Supplier shall pay interest to its subcontractor, supplier, or vendor on all amounts owed by Supplier that remain unpaid after seven (7) days following receipt by Supplier of payment from SCC for work performed or Materials furnished by the subcontractor, supplier, or vendor except for amounts withheld as allowed under subsection 3.2.1(b) above. Unless otherwise provided under the terms of the Agreement, interest shall accrue at the rate of one percent per month.
3.2.3 Supplier shall include in each subcontract or purchase order a provision requiring the subcontractor, supplier, or vendor to include in each of its subcontracts or purchase orders a provision requiring each of its subcontractors, suppliers, and vendors to include or otherwise be subject to the same payment and interest requirements with respect to each lower-tier subcontractor, supplier, and vendor. Each subcontractor shall include with its invoice to, or request for payment from, Supplier a certification that that subcontractor has paid each of its suppliers and lower-tier subcontractors their proportionate share of previous payments received from Supplier attributable to the work performed or the Materials furnished by it under the Agreement.
| 3.2.4 | The obligations of this section are the obligations of Supplier only and shall not be construed to obligate SCC in any manner nor shall Supplier seek any changes to the Agreement or other reimbursement for interest charges owed to Supplier’s subcontractors, suppliers, or vendors. |
| 4 | TAXES |
| 4.1 | Generally. Pursuant to Commonwealth Laws, SCC is exempt from the assessment of Commonwealth taxes on any property or services acquired under Commonwealth jurisdiction, including sales and use taxes. In addition, SCC is exempt from federal taxes pursuant to 26 U.S.C. §§ 4253(i) and (j). SCC makes no representation whatsoever as to the liability or exemption from liability of Supplier to any tax imposed by any Governmental Authority and all local, state, federal and other taxes associated with the Services and their performance by Supplier are Supplier’s responsibility. |
| 4.2 | Tax Filings. Supplier represents, warrants, and covenants that it will file appropriate tax returns, and pay applicable taxes owed arising from or related to the provision of the Services in all applicable jurisdictions. |
5 INFORMATION TECHNOLOGY AND COMMUNICATION SERVICES
5.1 Data Privacy. In accordance with Code of Virginia § 2.2-2009(A)(5), during the performance of this Agreement, Supplier shall comply with all applicable federal and state laws and regulations pertaining to information security and privacy.
5.2 ITAA Compliance. All information and communications technology (“ICT”) provided by Supplier as part of the Agreement shall comply with the Information Technology Access Act, Code of Virginia §§ 2.2-3500 et seq. ICT includes any website, application, or other product or service intended to fulfill or enable the function of information processing and communication by electronic means, including transmission and display via the internet. Supplier must certify that ICT provided to SCC under the Agreement conforms with accessibility requirements as defined in Virginia Code § 2.2-3501. If Supplier cannot certify full conformance of the accessibility of the ICT, Supplier must provide:
a. Supplier-paid and completed Accessibility Conformance Report (as defined in Virginia Code § 2.2-3501) indicating the level of conformance with accessibility of the ICT being procured; and
b. Supplier-paid and completed Vendor Accessibility Roadmap (as that term is defined in Virginia Code § 2.2-3501) documenting any areas of nonconformance and including a timeline for each nonconforming area's completion, within a commercially reasonable timeframe.
Notwithstanding Supplier’s obligations, and consistent with 28 C.F.R. § 35.201 and 36 C.F.R. Part 1194, Appendix A, § E202, SCC may, in its sole discretion, procure ICT that does not conform with accessibility requirements if such procurement does not result in individuals with disabilities being denied the benefit of any SCC program, service, or activity.
5.3 Prohibited Technology. Pursuant to Code of Virginia § 2.2-5514, Supplier is prohibited from providing, whether directly or indirectly through subcontractors, any hardware, software, or services that have been prohibited for use on federal government systems by the U.S. Department of Homeland Security or which are prohibited pursuant to 2 C.F.R § 200.216. Supplier is prohibited on any government-issued device or government-owned or government-leased equipment, including mobile phones, desktop computers, laptop computers, tablets, or other devices capable of connecting to the Internet, or while connected to any wired or wireless Internet network owned, operated, or maintained by SCC or the Commonwealth of Virginia from downloading or using any application or accessing access any website: (a) developed by ByteDance Ltd. Or Tencent Holdings Ltd., including TikTok or WeChat; or (b) developed by DeepSeek (see Executive Order 46 (2025)).
5.4 Warranty. Supplier warrants that it is the owner of the software or technology being provided as part of the Services or that it otherwise has the right to use it and to grant SCC the right or license to use the technology without infringing or violating any law, rule, regulation, copyright, patent, trade secret, or other proprietary rights of a Third Party.
5.5 Artificial Intelligence Disclosure and Consent Requirement. Supplier shall not use any artificial intelligence as part of or in connection with the Services without prior disclosure to SCC and receipt of SCC’s prior written consent. Supplier promptly shall disclose any aspect of the Services utilizing or relying upon artificial intelligence. No usage of artificial intelligence will be authorized without Supplier’s full demonstration and warranty that the usage has appropriate safeguards and complies with SCC then-current policy on artificial intelligence and all applicable state and federal laws. Supplier shall not use SCC data for any artificial intelligence queries, training, or program creation. Supplier shall not use SCC data to develop machine learning models or to train artificial intelligence programs or databases or related technology. Any artificial intelligence incorporated into the Services must be capable of being enabled or disabled upon SCC request.
| 6 | SERVICE LEVELS |
| 6.1 | Service Levels and Other Performance Standards. Supplier’s level of performance will be equal to or exceed the performance standards required by the Agreement and those designated as “Service Levels” in Exhibit D (Service Level Agreements) (the “Service Level(s)”). For the avoidance of doubt, if Supplier breaches its performance obligations under the Agreement, the fact that such breach did not cause Supplier to miss a Service Level shall not relieve Supplier of responsibility for such breach or any resulting damages. If Supplier fails to meet any Service Level, then, in addition to other remedies available to SCC, Supplier shall pay to SCC the Service Level Credits to the extent provided in Exhibit D (Service Level Agreements), in recognition of the diminished value of the Services resulting from Supplier’s failure to meet the required level of performance, and not as a penalty. |
6.2 Measuring and Reporting Service Levels. Supplier will implement and utilize all measurement and monitoring tools and procedures required to measure and report Supplier’s performance against the Service Levels. Such tools shall permit reporting at a level of detail sufficient to verify compliance with the Service Levels and will be subject to review and verification by SCC. Supplier will provide SCC with information and access to such tools and procedures upon request for purposes of verification. In addition, Supplier will make available to SCC any data in Supplier’s possession regarding measurements taken by Supplier with respect to any Service Levels.
6.3 Determining Incident and Event Severity. Supplier will respond to and resolve Incidents and Events associated with the Services. Each Incident or Event will be assigned a Severity Level in accordance with the agreed upon Severity Level definitions. Supplier will make an initial assignment of Severity Level for Incidents and Events as they arise; however, each Severity Level designation is subject to SCC review and approval. Any change in an Incident or Event will require re-evaluation of the Severity Level.
7. IMPLEMENTATION AND DELIVERABLES
7.1 Implementation Generally. Supplier will perform the Services necessary to complete the Implementation in accordance with the Agreement, including Exhibit B (Solution Requirements) and Exhibit C (Solution Description) (collectively, the “Implementation Services”). The Implementation Services will be conducted in accordance with the Requirements and the Implementation Plan.
| 7.2 | Performance and Completion of Implementation |
| 7.2.1 | Supplier will comply with the agreed timetable for performance of each Milestone and identify and resolve any problems encountered in the timely completion of each Milestone and other Implementation Services. An Implementation is not complete until (a) all Milestones have been Accepted by SCC in accordance with the Acceptance Criteria and procedures described in the Implementation Plan and (b) notwithstanding anything to the contrary in the Agreement, SCC determines, in its sole discretion, that, in all material respects (i) Supplier is capable and ready to perform the Services without interruption, (ii) all necessary data transfer and conversions have been completed successfully, and (iii) the Services are capable of meeting all Requirements. |
7.2.2 The Implementation Plan shall including, at a minimum: (a) a description of the technology methods and procedures, personnel, and organization that Supplier will use to perform such Implementation; (b) a schedule of Implementation activities; (c) a detailed description of the respective roles and responsibilities of SCC, Supplier, and other parties; (d) identification of the specific resources to be provided by SCC to support the Implementation; (e) the completion date for each Implementation activity; (f) the Acceptance Criteria (and, if appropriate, testing) to be applied by SCC in evaluating Implementation Deliverables and Milestones; (g) such other information and planning as are necessary to ensure that the Implementation takes place on schedule in a manner to timely meet and provide all Milestones and Deliverables.
7.2.3 Supplier will be responsible for preparing, revising, and finalizing the Implementation Plan, provided that: (a) Supplier will cooperate and work closely with SCC in finalizing the Implementation Plan (including incorporating SCC changes, modifications, and enhancements to the Implementation Plan and addressing SCC comments); and (b) the Implementation Plan (and any changes thereto, including any Implementation activities agreed upon after the Implementation start date) will be subject to written approval by SCC.
7.2.4 SCC responsibilities with respect to the Implementation Plan and Milestones shall be only those expressly set forth in the Implementation Plan and accepted by SCC.
7.2.5 SCC maintains the right to monitor, test, observe, and participate in the Implementation Services. Supplier will notify SCC without delay if such monitoring, testing, or participation has caused (or if Supplier expects it to cause) a problem or delay in an Implementation and will work with SCC to prevent or circumvent the problem or delay.
7.3 Deliverables. All Deliverables shall be tested for performance, compliance with Requirements, and ease of use or reference by Supplier prior to delivery to SCC. No update, engineering change, or revision made to a Deliverable shall degrade its performance below that established by the Requirements. Supplier warrants the interoperability of a Deliverable with all other Components of the Application and Solution.
7.3.1 Upon Supplier’s delivery of a Deliverable and certification that the Deliverable complies in all material respects to the Requirements, SCC may review and, if applicable, test such Deliverable to determine whether it is free from errors and defects and meets the technical, design, and functional specifications of all applicable Acceptance Criteria. Supplier acknowledges and agrees that SCC has broad discretion over the process and criteria for the review and testing of each Deliverable. The Review Period for each Deliverable will be thirty (30) Business Days after delivery (“Review Period”). Supplier will assist SCC throughout the Review Period, including by cooperating with SCC efforts, providing a technical Environment to facilitate SCC review, and providing applicable Documentation and information that may assist with SCC review and testing.
7.3.2. If Supplier receives a Deliverable Review Statement from SCC indicating rejection of a Deliverable, Supplier will provide a proposed corrective action plan within three (3) Business Days. The corrective action plan shall indicate Supplier’s plan to correct the Deliverable so that no Non-Conformities remain within ten (10) Business Days. Upon Supplier’s revision or correction of the Deliverable, Supplier will provide SCC with the revised Deliverable, whereupon the acceptance Review Period will be repeated.
7.4 Solution Acceptance. The Solution will be Accepted when SCC determines, following Acceptance testing, that the Solution operates in accordance with all Requirements and consistent with the Solution Description and the Acceptance Criteria. SCC shall have an Acceptance testing period of not less than ten (10) Business Days after Supplier’s deployment of the Solution in which to conduct testing. If SCC rejects the Solution as failing to meet all Acceptance Criteria and Agreement requirements, Supplier will provide a proposed corrective action plan within three (3) Business Days. The corrective action plan shall indicate Supplier’s plan to correct the Solution so that no Non-Conformities remain within ten (10) Business Days. Upon Supplier’s revision or correction of the Solution, the Solution Acceptance testing process will be repeated.
8 MAINTENANCE AND SUPPORT
Supplier shall provide all maintenance and Support Services required by the Agreement and Exhibit B (Solution Requirements), Exhibit C (Solution Description), and Exhibit D (Service Level Agreements).
| 9 | DATA SECURITY AND PROTECTION |
| 9.1 | Compliance with Data Privacy and Data Protection Laws. In performing its obligations under the Agreement, Supplier will observe and remain compliant with the privacy and security requirements mandated by Laws and the requirements of the Agreement. When accessing or handling any SCC Data or Content that contains Personally Identifiable Information, Protected Health Information, Federal Tax Information, or Sensitive Data, Supplier will comply with all Laws specifically relating to such information. |
| 9.2 | SCC Data, Generally. |
| 9.2.1 | SCC Data will be and remain the property of SCC and the applicable User. Supplier may not use SCC Data for any purpose other than to render the Services. No SCC Data will be sold, assigned, leased, or otherwise disposed of to Third Parties or commercially exploited by or on behalf of Supplier (or any of its Subcontractors, Vendors, Cloud Providers, or Supplier Personnel). Neither Supplier nor any of its Subcontractors, Vendors, Cloud Providers, or Supplier Personnel may possess or assert any lien or other right against or to SCC Data. Without limiting the generality of the foregoing, (a) Supplier may use SCC Data only as strictly necessary to render the Services and must restrict access to such information to Supplier Personnel on a strict need-to-know, least privilege basis, and (b) Supplier will not download, copy, transmit, or make available any SCC Data to any Third Party, except as expressly permitted by the Agreement. |
9.2.2 When SCC Data is in Supplier’s possession or under Supplier’s control and an event occurs that prevents or hinders the access to or reliable use of such SCC Data, Supplier will re-create or restore such data immediately, or in any case, as soon as reasonably practicable, to the last scheduled back-up applicable to such SCC Data in accordance with Supplier’s responsibilities hereunder. Any such re-creation or restoration will be at Supplier’s expense.
9.2.3 Supplier shall always maintain and provide SCC with a secure method of exporting SCC Data when requested in an industry standard format that provides for interoperability and portability. The Services shall provide and maintain a backup of all SCC Data such that SCC Data can be recovered in an orderly and timely manner within a predefined frequency consistent with recovery time and recovery point objectives. The Services shall store a backup of SCC Data, at least daily, in an off-site “hardened” facility, located within the United States, maintaining the security of SCC Data. SCC will have the right to keep backup files for SCC Data. Supplier will provide SCC with downloads of SCC Data, as requested or directed by SCC, to enable SCC to maintain such backup copies. SCC Data will be returned or otherwise provided to SCC, upon request, in the form and format as requested by SCC.
9.2.4 Supplier will never refuse for any reason, including SCC’s material breach of the Agreement, to provide SCC with SCC Data.
| 9.3 | Data Security Program. |
| 9.3.1 | Supplier must implement and maintain a data security program consisting of comprehensive technical, administrative, physical, and organizational safeguards to protect Content and SCC Data from loss, damage, destruction, unauthorized alternation, corruption, and unauthorized, accidental, and unlawful access, use, disclosure, modification or destruction. Supplier regularly shall update the data security program to address new and evolving technologies, updates to industry standard practices, and changing security threats, without diminishing the Services or Service Level Agreements. |
9.3.2 Supplier shall have and maintain Business Continuity and Disaster Recovery Plans designed to maintain the access to the Services and to prevent the unintended destruction or loss of SCC Data. The Plans should provide a predefined frequency, consistent with recovery time and recovery point objectives, as specified in the Agreement, for disaster recovery and archival purposes of Content at a secure facility located within the United States.
| 9.4 | Security Incident |
| 9.4.1 | Any unauthorized release or disclosure of any SCC Data, Confidential Information, Content, or SCC or Commonwealth proprietary information by Supplier constitutes a breach of the Agreement. |
9.4.2 Supplier shall notify SCC without undue delay, and in no event later than twenty-four (24) hours, after discovery of a Security Incident. Notification shall include all known details regarding the nature, scope, and actual, potential, and suspected impact of the Security Incident on the Solution, Application, Services, Content, and SCC Data.
9.4.3 Following a Security Incident, Supplier shall: (a) immediately initiate its incident response procedures; (b) take all reasonable steps to contain, mitigate, and remediate the Security Incident; (c) preserve all relevant evidence and logs; and (d) provide SCC with regular updates regarding Supplier’s investigation of the Security Incident that, depending on the nature of the incident, could be as frequent as hourly updates as determined by SCC in its sole discretion.
9.4.4 To the extent permitted by law, Supplier shall permit SCC the opportunity to participate in the investigation of the Security Incident and shall not limit SCC’s investigation of the nature, extent, and cause of the Security Incident.
9.4.5 For any Security Incident caused by the negligent acts or omissions of or breach of the Agreement by Supplier, Supplier will pay for any expenses to Supplier, SCC, and Third Parties as a result of the Security Incident, including the cost of any required legal compliance (e.g., notices required by applicable Laws), the expenses related to the investigation and remediation of the Security Incident, and any identity protection services.
10. DISPUTES AND CLAIMS (Code of Virginia § 2.2-4363) Claims, whether for money or other relief, shall be submitted by Supplier in writing to SCC Procurement Manager (“Procurement Manager”), no later than sixty (60) days after final payment; however, written notice of Supplier’s intention to file such claim must be given to the Procurement Manager at the time of the occurrence or beginning of the work upon which the claim is based and shall clearly state that it is a “notice of intent to make a claim.”
A claim shall clearly state that it is a “claim” and set forth the relief sought by Supplier, including any additional costs or damages claimed by Supplier and the basis for the relief requested, including the specific contractual basis upon which Supplier believes it is entitled to the relief requested. Failure to timely submit a notice of intent to make a claim, or to submit a claim, shall preclude any relief to Supplier.
The Procurement Manager shall render a final decision in writing within ninety (90) days after its receipt of Supplier’s written claim or within ninety (90) days after final payment, whichever date is later. The failure of the Procurement Manager to respond, or to timely respond, to a claim shall be deemed a denial of the claim by the Procurement Manager.
If Supplier’s claim is denied in whole or in part by the Procurement Manager, Supplier may request an administrative review of the final decision pursuant to SCC’s Procedure for Administrative Review of Procurement Decisions, dated October 6, 2015, available at Virginia SCC - Procurement. Supplier may not invoke review under these procedures prior to receipt of the Procurement Manager’s decision on a claim unless the Procurement Manager fails to timely render a decision.
Supplier’s remedies shall be limited to recovery of monetary damages and interest as may be allowed by law. In no event shall Supplier’s remedies include the right to terminate the Agreement, except as expressly provided herein.
The existence of a claim or an ongoing dispute resolution process shall not excuse Supplier from continuing performance under the Agreement or from properly complying with any changes ordered by SCC.
11 GENERAL TERMS & CONDITIONS
11.1 Applicable Law and Venue. This solicitation and any resulting contract shall be governed by the laws of the Commonwealth of Virginia and any litigation with respect thereto shall be brought in the Supreme Court of Virginia. Supplier shall comply with all applicable federal, state and local laws, rules, and regulations. Nothing in the Agreement will be construed to waive the Commonwealth’s sovereign immunity as it extends to SCC.
11.2 Authorized to Conduct Business. (Code of Virginia § 2.2-4311.2). Supplier, if organized as a stock or nonstock corporation, limited liability company, business trust, or limited partnership or registered as a registered limited liability…
This is the start of the file's text. The full file is on GovTribe.