201-26-045 Exhibit C Implementation Statement of Work (SOW).docx

Contract No. 201-26-045, Exhibit C [Instructions to Supplier: The VDOE has completed the following Implementation Scope of Work with key information about the implementation of this solicitation. Supplier should carefully review this document and return a thoroughly marked-up redline copy with any and all changes or additions needed for successful implementation of the project as detailed in Solicitation and Exhibit A: Requirements. The response should be labeled “10 [Supplier Name] Exhibit C. Implementation Statement of Work (SOW).”

NOTE: As noted in Exhibit A: Requirements section 21, Supplier is responsible for project management and documentation. The goal for this initial implementation statement of work is successful completion of test administration cycles in the first year after contract execution (and thereafter, ultimately, the fulfillment of all requirements in Exhibit A: Requirements). The redline response should be the foundation for the vendor-led project management approach, and should reflect Supplier’s approach to implementation to ensure this initial goal and then ultimately all requirements are achieved.]

EXHIBIT C: IMPLEMENTATION STATEMENT OF WORK (SOW)

Statement of Work (SOW) Between the Virginia Department of Education and [SUPPLIER NAME]

Issued Under

CONTRACT NUMBER 201-26-045

This Implementation Statement of Work (“SOW”), between the Virginia Department of Education (hereinafter referred to as “Agency” or “VDOE”) and [Supplier Name] (“Supplier”) is issued pursuant to the terms of Contract. In the event there is any conflict between the terms of this SOW and the terms and conditions of the Contract, the terms and conditions of the Contract will control.

The objective of the implementation project described in this SOW is for the Supplier to provide the VDOE with implementation services to implement the Solution (“Solution”) for VDOE’s Virginia Statewide K-12 Student Assessment Program (SOL).

Implementation Period of Performance The implementation work authorized in this SOW will commence seven (7) calendar days after execution of the Contract and will continue for a period of twelve (12) months. Implementation Services will be considered complete when all work detailed in this SOW is finalized, the Solution is in productive use by the Agency, and the Agency has issued formal Acceptance of the Solution to the Suppler.

Place of Performance for implementation Tasks associated with this project implementation will be performed at the Agency’s location(s) in Richmond, Virginia, at Supplier’s location(s) in City/State, or other locations as required by the effort and mutually agreed to under this SOW.

Project Definitions [All definitions are located in the Contract and shall apply to and take precedence over this SOW.]

Project Scope FOR IMPLEMENTATION Project Scope and Purpose The Implementation work authorized in this SOW is the work needed to operationalize a comprehensive, supplier‑hosted cloud solution that supports the full lifecycle of Virginia’s statewide K‑12 summative assessment program, including test development, dual‑mode (online and paper) delivery, scoring, administration, reporting, and associated psychometric and project management services, with successful operation of the test administration cycles in the first year after contract award. The implementation work needs to ensure the successful migration of assessment content and data from the incumbent vendor, and the continuity of core operations during the transition period, and the preparation for and delivery of the assessment program (including test design, administration, scoring and reporting, and psychometric services) in the first year of contract award. The implementation work must also lay the foundation for success throughout the contract period, including the ongoing operation of aa scalable, reliable, and secure assessment system that delivers timely, accurate results; supports instructional improvement; incorporates appropriate innovations such as technology‑enhanced and constructed‑response items; and meets all functional, technical, and support requirements outlined in Exhibit A: Requirements.

Project Boundaries The project’s boundaries are defined by the scope and limitations established in the contract, including that the Contractor is responsible only for the development, administration, scoring, reporting, technical systems, and project management activities explicitly outlined in Exhibit A: Requirements while several elements remain out of scope—such as content development for the Virginia Alternate Assessment Program (VAAP), which continues to be provided by the University of Oregon; the State Testing Identifier system; and any assessments outside the Virginia statewide K‑12 summative program. Additionally, implementation activities must align with technology requirements, including security and cloud compliance standards, and a mandatory assessment and approval process for any proposed uses of artificial intelligence/generative artificial intelligence (AI/GenAI) and mandated timelines. The work will commence seven (7) days after contract award,and will continue through the first year of the contract period, including the fall, spring, and summer test administration cycles of the first year.

Project Implementation Requirements

0. Agency’s Specific Implementation Requirements The Agency requires that the implementation of the statewide K‑12 assessment solution adhere to specifications outlined in Exhibit A: Requirements, including compliance with VITA and VDOE security directives, cloud and data privacy requirements, and all business functional, technical, and support specifications.

Special Considerations for Implementing Technology at Agency’s Location(s) [The Agency does not anticipate any on-site technology or equipment needs at its locations, but if the Supplier foresee any such need or considerations, the Supplier should include them here].

Other Project Characteristics to Ensure Success Successful implementation of the Solution will rely on several key project characteristics, including strong, continuous collaboration between the Contractor, VDOE, the previous Contractor, and other partners such as the University of Oregon’s BRT during front‑end transition; robust project governance supported by detailed documentation, clear communication pathways, and well‑defined roles and responsibilities; and the Supplier’s ability to maintain strict adherence to security, accessibility, and performance requirements throughout all systems and processes. Success will also depend on the Supplier’s capacity to manage complex, concurrent workstreams—including system configuration, content migration, CAT algorithm replication, test form development, training, scoring readiness, and reporting—while meeting compressed statewide administration timelines and legislative deadlines. Additionally, the Contractor must demonstrate adaptability to evolving policy, legislative, and instructional priorities, ensure high system reliability during peak loads, and provide proactive risk management and quality control practices that support a smooth transition and sustained operational effectiveness.

Required Products (or Solution Components)

· Content Management System

· Test Administration Management System

· Online Test Delivery Platform

· Online reporting portal

· Test Development across all tests in the Virginia Assessment Program, other than the Virginia Alternate Assessment Program (VAAP)

· Test Administration across all tests in the Virginia Assessment Program

· Scoring and Reporting across all tests in the Virginia Assessment Program

· Psychometric Services across all tests in the Virginia Assessment Program

· Educator Support and Family Communications

· All other components as specified in Exhibit A: Requirements

Required Implementation Services Development and/or configuration and deployment of the Content Management System, Test Administration Management System, and Online Test Delivery Platform, in line with all system requirements as specified in Exhibit A: Requirements.

Front-end Transition Requirements as specified in Exhibit A: Requirements, 8.1.1-33.

All other activities as required to assume full ownership of the statewide summative assessment program in time to successfully administer the spring 2028 test administration cycle.

Project Specific Performance Requirements Project specific performance Requirements are outlined in Exhibit I: Service Level Agreements (SLAs).

Project Specific Deliverable Requirements The list below outlines key deliverables and references the main requirements in which they are detailed as a guide, but are not comprehensive of all provisions. The definitive record of requirements the Offeror must meet is Exhibit A: Requirements.

· Item specification requirements review plan (1.2.3) and execution

· Item development plan (1.1.8) and execution in line with all item specifications (section 1.2)

· Item documentation for each item at each step of development process (1.2.13 and section 1.2)

· Item descriptions for each operational test item (1.2.17)

· Item review committee staffing (1.3.1), training (1.3.2 and 1.3.3), and execution

· Item review committee decision documentation (1.3.4)

· Item writing staffing (1.3.5), training (1.3.6) and execution

· Field test schedule and methodology (1.4.2-4)

· Field test statistical analysis (1.4.5)

· Annual report of item review and data review (1.4.7)

· Cognitive labs plan, execution, report, as applicable when new item types are considered (1.4.8)

· New or revised test blueprints as needed upon new content standards adoption or revision (1.5.2)

· Ancillary materials development as needed upon new content standards adoption or revision (1.5.3)

· Development of new performance level descriptors upon new content standards and as needed (1.5.5)

· Standards of Learning (SOL) Grades 3-8 Math Computer Adaptive Test (CAT) algorithm plan and implementation (1.5.6 and 8)

· SOL Grades 3-8 Reading CAT algorithm plan and implementation (1.5.7 and 8)

· 3-8 Math and Reading CAT Algorithm simulation results (1.5.8)

· Linear test forms for all linear form tests (as listed in Solicitation Table 1) and for 3-8 Math and Reading paper versions (1.5.9)

· Paper braille and large print forms for each test (1.5.10-11)

· Answer keys and test map specifications for all tests (1.5.12)

· Grades 5 and 8 Integrated Reading and Writing tests and score reports (section 1.6)

· Achievement/performance level setting establishment and review (2.2.1-2)

· Standard setting plans, execution, and narrative reports (2.2.3-4)

· Standard setting committee staffing, training, and report (2.2.5-6)

· Technical Advisory Committee (2.3.1)

· Equating and scaling plan and execution (2.4.2)

· Results reporting on 100-point scale (2.4.3)

· Equating and scaling quality assurance (2.4.4)

· Technical reports (2.5.1)

· Additional analyses as specified by VDOE (2.5.2)

· Virginia Alternate Assessment Program (VAAP) materials and administration (3.1.1 and 2)

· VAAP scoring and reporting (3.1.3)

· Test administration manuals (4.2.1-2)

· Paper test booklets (4.2.3) preparation

· Paper answer documents preparation (4.2.4)

· Packaging, distribution, and return of paper test materials (4.2.5-8)

· Test retake administration (4.3.1-3)

· Scoring and reporting specifications (5.1.1-2)

· Timely provision of Individual Score Reports and school, division, state date (5.1.4)

· Scoring multiple choice and technology-enhanced items (section 5.2)

· Constructed response items scoring methodology (5.3.1 and throughout section 5.3)

· Constructed response item range-finding facilitation and execution (5.3.7)

· Constructed response items scoring staff recruitment, training and management (5.3.8-13)

· Constructed response item scoring monitoring and quality control (5.3.12-16)

· Score reports and data files (5.5.1-7)

· Data forensics and investigations support (5.5.8-11)

· Report suite (sections 6.1, 6.3.2, and 12.5)

· Online reporting portal (6.1.2 and section 12.5)

· Practice and released items publication (6.2.1)

· Educator resource on constructed response items and scoring (6.3.1)

· Educator supports for assessment and instruction (6.3.3)

· Feedback plans, execution, and findings (6.4.1-2)

· Security breach and web monitoring (7.1.9)

· Transition plan and rollback/contingency plan (8.1.1)

· Import of all existing test content and associated data (8.1.3-5 and 18.1.1-2)

· Demonstration of item rendering (8.1.3-4 and 18.1.3) including corrections of issues, and functionality and security of item transfer system (8.1.8)

· Replication of CAT algorithms (1.5.6-8, 8.1.12) and equating and scaling of linear forms (2.4.2, 2.4.4, 8.1.13).

· Networking and test simulation tool for divisions (8.1.17 and 13.2.8)

· All other front-end transition activities as specified in section 8.1

· Back-end transition activities as specified in section 9.

· System documentation (10.4.1)

· Content management system (section 11)

· Test administration management system (section 12)

· Online test delivery system (section 13)

· Load testing of online test delivery system to ensure testing capacity of at least 500,000 Virginia students simultaneously (14.2.1-2)

· Role-based and organization-based access to systems (section 15)

· In-person and virtual trainings for VDOE staff (20.1.1)

· Division training plan (20.2.2) and execution (20.2.3-6).

· Technical support plan and execution (20.2.7-8)

· Educator committee meeting planning and execution (20.3.1-2)

· Project management and staffing plan and execution (section 21)

Each deliverable must meet the acceptance criteria defined in the SOW—such as being submitted in the required format, aligning with Exhibit A requirements, and achieving Agency approval—and must be timely delivered.

Project Specific Materials, Equipment, Facilities and Property

i. Provided by the Agency As noted in Exhibit A Requirements, current versions of the following VDOE and other documents and resources can be found as follows:

· Test blueprints: https://www.doe.virginia.gov/teaching-learning-assessment/student-assessment/virginia-sol-assessment-program/test-blueprints

· Test administration materials: https://www.doe.virginia.gov/teaching-learning-assessment/student-assessment/virginia-sol-assessment-program/sol-test-administration-development

· Student record collection layout: https://www.doe.virginia.gov/data-policy-funding/data-reports/data-collection/student-record-collection

· Test accommodations: https://www.doe.virginia.gov/teaching-learning-assessment/student-assessment/virginia-sol-assessment-program/sol-test-administration-development

· Travel and per diem rates in the Commonwealth Accounting Policies and Procedures (CAPP) Manual: https://www.doa.virginia.gov/reference.shtml#CAPP

· 1EdTech interoperability standards: https://www.1edtech.org/specifications.

In addition, the VDOE will provide the following to the awarded Offeror:

· With the incumbent vendor, secure test content, scoring information, and related assessment artifacts, under a limited, non‑exclusive license to use such data to perform obligations under the contract resulting from this solicitation.

· Information about the State Testing Identifier Management System going forward

ii. Provided by the Supplier

Other Technical/Functional Requirements See Exhibit A: Requirements Functional and Technical requirements (sections 1-19).

Training Requirements and/or Agency Self-Sufficiency/Knowledge Transfer The Supplier will be required to provide comprehensive training services that ensure VDOE, school divisions, and authorized users can successfully operate, administer, and maintain all components of the assessment Solution, as outlined in the Support Requirements section of Exhibit A: Requirements. Training must include structured onboarding for the Test Administration Management System, the Content Management System, and the Online Test Delivery System, as well as the reporting portal, along with role‑specific guidance for division and school staff.

Agency’s Security Requirements

i. Security procedures for the Agency’s location may include, but are not limited to, background checks, records verification, photographing, and fingerprinting of Supplier’s employees or agents.

ii. Execution of additional forms, such as a non-disclosure agreement (NDA), to be signed by each of the Supplier’s employees or agents acknowledging that all Agency information that Supplier employees or agents may have contact with is confidential and proprietary. Any unauthorized release of proprietary information by the Supplier, or an employee or agent of the Supplier, will constitute a breach of Contract.

iii. Additional Agency security requirements are listed in Exhibit A, under VDOE's Security Requirements tab, in section 17, and throughout (e.g., secure destruction of paper test materials, security requirements for AI use, etc.).

Implementation Support Requirements Key implementation support requirements are outlined in Exhibit A: Requirements, Front-end Transition Requirements sections 8 and 18. The Supplier must provide implementation support in the following overarching areas:

· Verified import of content and data. The supplier must import legacy item banks, test content, and associated metadata. The supplier must also import the prior year’s test administration data.

· Demonstration of systems/mechanisms for secure data transmission with the VDOE and with the State Testing Identifier management system.

· Demonstration of key assessment functions, including:

· Replication of CAT algorithms

· Replication of equating and scaling of linear forms

· Functionality of scanning and scoring program for paper administration

· Replication of scoring of constructed response items

· Demonstration of functionality of systems, including the Content Management System, Test Administration Management System, online Test Delivery Platform, and the reporting portal

· Demonstrated ability to meet load/capacity requirements for smooth operation of the system with up to 500,000 simultaneous test takers

· Network testing and test simulation system utilities for divisions to prepare for online testing

· Training and support for VDOE staff, and for divisions and schools, including help desk.

Personnel Requirements for Implementation See overall project/ongoing implementation staffing requirements as specified in Exhibit A: Requirements section 21 and Supplier Profile, as well as for specific functions and committees throughout, including but not limited to 1.3.1, 1.3.5, 2.2.5, and 5.3.10.

Closeout Requirements for Project Implementation

At the conclusion of the implementation period, the Supplier shall complete all project closeout activities necessary to ensure a smooth transition into full operational use and compliance with the Contract’s transition‑of‑services provisions. These activities include providing final Deliverable Acceptance Receipts for all outstanding milestones; completing financial closeout by confirming all invoicing, payments, and reconciliations; and delivering a comprehensive documentation handoff that includes all finalized system manuals, operating procedures, configuration documentation, training materials, warranty information, and any other records developed under the SOW. The Supplier shall also administer and provide results from required stakeholder surveys, post‑project evaluations, and lessons‑learned reports to support continuous improvement. All closeout documentation, including the formal Project Closeout Documentation identified in the milestones section, must be submitted no later than 365 days after contract execution, unless otherwise modified by the Agency, to align with the established milestone for Transition and Project Closeout.

Implementation Project Assumptions & Project Roles and Responsibilities

0. Project Assumptions The following assumptions are specific to this project:

0. Project Roles and Responsibilities The following roles and responsibilities have been defined for this project:

Responsibility Matrix Legend:

R = Responsible for execution/completion of work A = Final approval authority C = Must be consulted I = Must be informed

Per Exhibit A: Requirements 21.1.16, the supplier shall define governance and approval workflows (e.g., RACI or other similar framework) that specify who approves key deliverables (e.g., blueprints, forms, score reports, data files) and the timing of VDOE review windows in the master schedule. Supplier shall add additional items to this chart as needed.

Milestones, Deliverables, AND Epics (If Applicable) Supplier shall provide the milestone events and deliverables identified below by the associated due date identified in the table. The following table identifies milestone events and deliverables to be provided by Supplier under this SOW, the Deliverable description, the associated Deliverable Acceptance (“exit”) criteria, and the associated due date (days are calendar days unless otherwise specified). All pricing information related to this implementation SOW shall be detailed in Exhibit B Pricing and broken out by Milestone/Deliverable.

Execution + 7 days

· Initial Project Schedule is provided by Supplier to Agency within 30 days

· Initial Project Schedule is in a format compatible to VDOE, as described in Exhibit A Requirements

· VDOE receives and reviews the Schedule for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt

Initial plan within 30 days of Execution, then monthly review to assess progress and discuss any necessary updates*

*Significant changes must be reviewed and approved by Agency prior to execution of such change

· The plan outlines the strategy for transition-in planning and the go/no-go checkpoints to ensure successful statewide operational delivery of assessments or triggering of the rollback/contingency plan (next deliverable).

· Plan is submitted by due/review date.

· Plan is in a format compatible to VDOE

· VDOE receives and reviews the plan for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Initial plan at execution + 45 days or August 15 of year of contract execution, whichever is sooner.

then monthly review to assess progress and discuss any necessary updates*

*Significant changes must be reviewed and approved by Agency prior to execution of such change

See also Exhibit A: Requirements 8.1.1.

· The plan outlines a rollback plan including decision triggers and recovery steps.

· The plan includes realistic contingency/back-up plans that meet core federal and state annual assessment requirements, to be used if needed.

· Plan is submitted by due/review date.

· Plan is in a format compatible to VDOE

· VDOE receives and reviews the plan for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Initial plan at execution + 45 days or August 15 of year of contract execution, whichever is sooner, then monthly review to assess progress and discuss any necessary updates*

*Significant changes must be reviewed and approved by Agency prior to execution of such change

This deliverable will provide VDOE with documentation of the successful Import of all existing test content (blueprints, items, item metadata) into the supplier’s Content Management System. The deliverable will document the accuracy of item rendering across assessments and item types; the accuracy and completeness of all associated metadata, supplier systems and of quality assurance process the Supplier used in its checks for validity and completeness.

See also Exhibit A: Requirements 8.1.3-5 and 18.1.1-3.

· The documentation is submitted for review prior to Go/No-Go decisions for blueprint construction for fall testing, and includes evidence of successful import and quality assurance process for validity and completeness.

· VDOE has at least two weeks to review the results for accuracy and completeness and provide feedback.

· VDOE issues a Deliverable Acceptance Receipt confirming receipt and acceptance of the results.

Initial import and supplier verification by execution + 75 days or September 15 of year of contract execution, whichever is sooner

· VDOE has at least two weeks to review the results for accuracy and completeness and provide feedback.

· VDOE issues a Deliverable Acceptance Receipt confirming receipt and acceptance of the results.

Supplier to propose in Draft Project Schedule.

· VDOE has at least two weeks to review the results for accuracy and completeness and provide feedback.

· VDOE issues a Deliverable Acceptance Receipt confirming receipt and acceptance of the results.

Supplier to propose in Draft Project Schedule.

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Execution + 90 days or October 1 of year of contract execution, whichever is sooner

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Execution + 90 days or October 1 of year of contract execution, whichever is sooner

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Execution + 90 days or October 1 of year of contract execution, whichever is sooner

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Supplier to propose in Draft Project Schedule.

· The deliverable is submitted with all required components, showing evidence of meeting all applicable requirements from Exhibit A: Requirements

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements, accuracy, and completeness, and provides feedback.

· VDOE returns Deliverable Acceptance Receipt Supplier to propose in Draft Project Schedule.

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Supplier to propose in Draft Project Schedule.

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Supplier to propose in Draft Project Schedule.

· The deliverable is submitted with all required components, showing evidence of meeting all applicable requirements from Exhibit A: Requirements

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Supplier to propose in Draft Project Schedule.

The deliverable will include documentation with screenshots as evidence of the test’s success or failure.

· The deliverable is submitted with all required components, showing evidence of meeting all applicable requirements from Exhibit A: Requirements 14.2.1-2.

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Execution + 90 days or October 1 of year of contract execution, whichever is sooner

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Supplier to propose in Draft Project Schedule.

8.1.17 and 13.2.8 among others), and of how it was tested in various wireless environments, similar to what schools operate in for accuracy.

· The deliverable is submitted with all required components, showing evidence of meeting all applicable requirements from Exhibit A: Requirements

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt

Execution + 60 days or September 1 of year of contract execution, whichever is sooner

· The deliverable is submitted with all required components, showing evidence of meeting all applicable requirements from Exhibit A: Requirements

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Execution + 90 days or October 1 of year of contract execution, whichever is soonest

· VDOE receives and reviews the deliverable for its conformance with Exhibit A Requirements

· VDOE returns Deliverable Acceptance Receipt Supplier to propose in Draft Project Schedule.

Acceptance Criteria The Acceptance process for this Solution is described in the Acceptance and Cure Period Section of the Contract (Section 12) and will be based on the Agency’s determination that the Services, Software, Solution, Application, Products, and/or Deliverables meet the Requirements in accordance with the Contract, this SOW, test plan, or other written agreement between the Parties.

Each Deliverable created under this Statement of Work will be delivered to the Agency Project Manager with a Deliverable Acceptance Receipt. This receipt will describe the Deliverable and provide the Agency’s Project Manager with a space to indicate if the Deliverable is Accepted, rejected, partially Accepted, or conditionally Accepted. Conditionally Accepted Deliverables will contain a list of deficiencies that need to be corrected for the Deliverable to be Accepted by the Agency Project Manager.

Risk Management during Implementation

0. Risk Management Process

1. Risk Identification Process: Describe the process for risk identification.

2. Risk Evaluation and Prioritization: Describe how risks are evaluated and prioritized.

3. Risk Mitigation Options: Describe, in general terms, the risk mitigation options. They must be realistic and available to the project team.

4. Risk Plan Maintenance: Describe the methods for maintaining or updating the risk plan during the project lifecycle.

5. Risk Management Responsibilities: Identify all project team members with risk management responsibilities (e.g., an individual responsible for updating the plan or an individual assigned as a manager).

Risk Management Plan Risk reviews will take place at least bi-weekly as a dedicated section in recurring project management meetings between Supplier and the VDOE. As risks are identified and evaluated, any risks that rise to the level of jeopardizing successful implementation must be incorporated into the transition-in plan (and the roll-back/contingency plan if necessary).

Reporting during Implementation

0. Weekly/Bi-weekly Status Update The weekly/bi-weekly status report, to be submitted by Supplier to the Agency, should include accomplishments to date as compared to the project plan; any changes in tasks, resources or schedule with new target dates; all open issues or questions regarding the project; action plan for addressing open issues, risks, or questions and potential impacts on the project; and risk management reporting.

Supplier Performance Self-Assessment.

Within 30 calendar days of Contract kickoff, the Supplier and the Agency will agree on Supplier performance self-assessment criteria. Supplier shall prepare a monthly self-assessment to report on such criteria. Supplier shall submit its self-assessment to the Agency who will have five (5) business days to respond to Supplier with any comments. If the Agency agrees with Supplier’s self-assessment, such Agency will sign the self-assessment and upload a copy to the Project documents in Planview, the Commonwealth Technology Portfolio.

Change Request Process All changes to this SOW must comply with the Contract. Price changes must comply with the Code of Virginia, § 2.2-4309. Modification of the Contract, found at this link: http://law.lis.virginia.gov/vacode/title2.2/chapter43/section2.2-4309/ All changes to this SOW shall be in written form via a modification to the Contract and fully executed between the Agency and the Supplier’s authorized representatives. For administrative changes, the parties agree to use the change template, attached to the Contract. For technical/functional change management Requirements, listed below, the parties agree to follow the processes and use the templates provided at this link: https://www.vita.virginia.gov/it-governance/project-management/project-management-templates-tools/ Point of Contact For the duration of this project, the following project managers shall serve as the points of contact for day-to-day communication:

Agency: __________________________ Supplier: _________________________

Implementation Statement of Work (SOW) Page 2 of 11