Contract No. VA-161128-AT&T, Exhibit D
Page 1 of 11
EXHIBIT D STATEMENT OF WORK (SOW) TEMPLATE
BETWEEN (NAME OF AUTHORIZED USER) AND AT&T DATACOMM LLC
ISSUED UNDER
CONTRACT NUMBER VA-161128-AT&T
BETWEEN
VIRGINIA INFORMATION TECHNOLOGIES AGENCY
AND
AT&T DATACOMM LLC
Exhibit D, between (Name of Agency/Institution) and AT&T Datacomm LLC (“Supplier”) is hereby
incorporated into and made an integral part of Contract Number VA-161128-AT&T (“Contract”) between
the Virginia Information Technologies Agency (“VITA”) on behalf of the Commonwealth of Virginia and
Supplier.
In the event of any discrepancy between this Exhibit D and the Contract, the provisions of the Contract
shall control.
(Note to Template Users: Any Service, Licensed Services, Solution or Software provided under this SOW
must comply with all COVA Security and Enterprise Architecture ITRM policies, standards and guidelines
located at: http://www.vita.virginia.gov/library/default.aspx?id=537
and all COVA Enterprise Architecture
Data Standards and requirements located at:
http://www.vita.virginia.gov/oversight/default.aspx?id=10344.
If Authorized User is a State Agency and determines any area of non-compliance with the ITRM PSGs at
the above links in the Service, Licensed Services, Solution or Software to be provided by Supplier under
this SOW, such Authorized User’s Project Manager must obtain written waiver from VITA in accordance
with the waiver process prior to placing any related order or authorizing Supplier to commence any work.
Agency should collaborate with their designated Customer Account Manager to obtain such waiver.)
[Note to Template Users: Instructions for using this template to draft a Statement of Work are in gray
highlight and italics. These instructions should be deleted after the appropriate text has been added to
the Statement of Work. Contractual language is not italicized and should remain in the document. Text
that is highlighted in blue is variable based on the nature of the project.]
STATEMENT OF WORK
This Statement of Work (SOW) is issued by the (Name of Agency/Institution), hereinafter referred to as
“Authorized User” under the provisions of the Contract,”. The objective of the project described in this
SOW is for the Supplier to provide the Authorized User with a Solution (“Solution”) or Services
(“Services)” or Software (“Software”) or Hardware and Maintenance or Licensed Application Services” for
Authorized User Project Name. (Customize the last sentence to state what you are getting from the
Supplier, based on the VITA Contract language, and with your project name.)
1. PERIOD OF PERFORMANCE
The work authorized in this SOW will occur within XX (XX) months of execution of this Statement of
Work. This includes delivery, installation, implementation, integration, testing and acceptance all of
products and services necessary to implement the Authorized User’s Solution, training, and any
support, other than on-going maintenance services. The period of performance for maintenance
services shall be one (1) year after implementation or end of Warranty Period and may be extended
for additional one (1) year periods, pursuant to and unless otherwise specified in the Contract.
(Customize this section to match what you are getting from the Supplier, based on the allowable
scope of the VITA Contract and your project’s specific needs within that allowable scope.)
Contract No. VA-161128-AT&T, Exhibit D
Page 2 of 11
2. PLACE OF PERFORMANCE
(Assign performance locations to major milestones or any other project granularity, depending on
your transparency and governance needs, if needed.)
Tasks associated with this project will be performed at the Authorized User’s location(s) in City/State,
at Supplier’s location(s) in City/State, or other locations as required by the effort.
3. PROJECT DEFINITIONS
Provide project unique definitions so that all stakeholders have the same understanding. Ensure
these do not conflict with the Contract definition.).
All definitions of the Contract shall apply to and take precedence over this SOW. Authorized User’s
specific project definitions are listed below:
4. PROJECT SCOPE
(Provide a description of the scope of your project and carve out what is NOT in the scope of your
project. Remember that it must fit within the VITA Contract scope.).
A. General Description of the Project Scope
B. Project Boundaries
5. AUTHORIZED USER’S SPECIFIC REQUIREMENTS
(Provide information about your project’s and your agency’s specific requirements for this particular
project including, but not limited to the following subsections):
A. Authorized User-Specific Requirements
B. Special Considerations for Implementing Technology at Authorized User’s Location(s)
C. Other Project Characteristics to Insure Success
6. CURRENT SITUATION
(Provide enough background information to clearly state the current situation to Supplier so that
Supplier cannot come back during performance claiming any unknowns or surprises. Some example
subsections are provided below. You may collapse/expand as you feel is necessary to provide
adequate information and detail.)
A. Background of Authorized User’s Business Situation
B. Current Architecture and Operating System
C. Current Work Flow/Business Flow and Processes
D. Current Legacy Systems
E. Current System Dependencies
F. Current Infrastructure (Limitations, Restrictions)
G. Usage/Audience Information
7. PRODUCTS AND SERVICES TO SUPPORT THE PROJECT REQUIREMENTS (AND/OR
SOLUTION)
A. Required Products (or Solution Components)
(List the products, or if your project is for a Solution, the Solution components, (hardware, software,
etc.) provided by Supplier that will be used to support your project requirements. Identify any special
configuration requirements, and describe the system infrastructure to be provided by the Authorized
User. Provide an overview that reflects how the system will be deployed within the Authorized User’s
environment. You are urged to refer to the VITA Contract for allowable scope and other guidance in
drafting language for this section.)
Contract No. VA-161128-AT&T, Exhibit D
Page 3 of 11
B. Required Services
(List the services (e.g., requirements development, Solution design, configuration, interface design,
data conversion, installation, implementation, testing, training, risk assessment, performance
assessment, support and maintenance) that will be provided by Supplier in the performance of your
project. You are urged to refer to the VITA Contract for the definition of Services and for the allowable
scope in drafting language for this section. You will notice subsections ”C” and “D” below offer areas
for expanded detail on training, support and maintenance services. You may add other subsections in
which you wish to expand the information/details/requirements for other service areas as well. It is
likely some of this detail will be a combination of your known needs and the Supplier’s proposal. In all
cases the provisions should include all negotiated commitments by both parties, even if you reference
by incorporation the Supplier’s proposal in any subsection.)
C. Training Requirements and/or Authorized User Self-Sufficiency/Knowledge Transfer
(Provide an overview and details of training services to be provided for your project and any special
requirements for specific knowledge transfer to support successful implementation of the Solution. If
the intent is for the Authorized User to become self-sufficient in operating or maintaining the Solution,
determine the type of training necessary, and develop a training plan, for such user self-sufficiency.
Describe how the Supplier will complete knowledge transfer in the event this Statement of Work is not
completed due to actions of Supplier or the non-appropriation of funds for completion affecting the
Authorized User. You may refer to the VITA Contract for guidance on the allowable scope for this.
D. Support and Maintenance Requirements
(Document the level of support, as available under the Contract, required by your project to operate
and maintain the Solution. This may include conversion support, legacy system integration, transition
assistance, Solution maintenance (including maintenance level), or other specialized consulting to
facilitate delivery or use of the Solution.
E. Personnel Requirements
(Provide any supplier personnel qualifications, requirements, licenses, certifications or restrictions
including project manager, key personnel, subcontractors, etc., but ensure they do not conflict with
the VITA Contract terms.)
F. Transition Phase-In/Phase-Out Requirements
(Describe any specific requirements for orientation or phasing in and/or phasing out of the project with
the Supplier. Be specific on what the project needs and expected results are, the duration and other
pertinent detail, but ensure they do not conflict with the VITA Contract provision(s) regarding
Transition of Services or with any other training requirements in the SOW.)
8. TOTAL PROJECT PRICE
The total Fixed Price for this Project shall not exceed $US XXX.
Supplier’s invoices shall show retainage of ten percent (10%). Following completion of Solution
implementation, Supplier shall submit a final invoice to the Authorized User, for the final milestone
payment amount shown in the table in section 9 below, plus the total amount retained by the
Authorized User. If travel expenses are not included in the fixed price of the Solution, such expenses
shall be reimbursed in accordance with Commonwealth of Virginia travel policies as published by the
Virginia Department of Accounts (http://www.doa.virginia.gov
). In order to be reimbursed for travel
expenses, Supplier must submit an estimate of such expenses to Authorized User for approval prior
to incurring such expenses.
(Sections 9 through 11 should be used or deleted depending on the project’s complexity, risk and
need for governance. For a simple project you may only need the section 10 table, but for a more
complex project, or a major IT project, you may need a combination of or all of the tables for check
and balance and redundancy.)
Contract No. VA-161128-AT&T, Exhibit D
Page 4 of 11
9. PROJECT DELIVERABLES
(Provide a list of Supplier’s deliverable expectations. The table is to be customized for the Authorized
User’s project. You may want to categorize deliverables for each phase or major milestone of the
project and then categorize other interim deliverables and/or performance and status reports under
one of them or under an Administrative or Project Management section.)
The following deliverables are to be provided by Supplier under this SOW. Subsequent sections may
include further detail on the content requirements for some deliverables.
No.
Title
Due Date
Format
Required (i.e.,
electronic/hard
copy/CD/DVD
Distribution
Recipients
Review
Complete
Due Date
Final Due
Date
Project Plan
Design Plan
Implementation Plan
Data Conversion Plan
Risk Assessment Plan
Test Plan
Training Plan
Performance Plan
Contingency Plan
Disaster Recovery Plan
Cutover Plan
Change Management
Plan
Transition Plan
Monthly Status Reports
Quarterly Performance
/SLA Reports
Training Manual
Final Solution
Submission Letter
Final Acceptance Letter
10. MILESTONES, DELIVERABLES, PAYMENT SCHEDULE, AND HOLDBACKS
(This table should include the project’s milestone events, associated deliverables, when due,
milestone payments, any retainage amount to be held until final acceptance and the net payment you
promise to pay for each completed and accepted milestone event. This table includes sample data
only and must be customized for your project needs.)
The following table identifies milestone events and deliverables, the associated schedule, any
associated payments, any retainage amounts, and net payments.
Event
Associated
Milestone
Schedule
Payment
Retainage
Net Payment
Contract No. VA-161128-AT&T, Exhibit D
Page 5 of 11
Deliverable(s)
meeting
---
Execution + 5
days
---
---
---
Site survey
report
Execution + 10
days
---
---
---
Analysis &
Development
Design Plan
Execution+45
days
$30,000
$15,000
$15,000
Project Plan
Execution+45
days
Implementation
Plan
Execution + 45
days
Implementation
Execution + 60
days
& Mapping
Execution + 90
days
$10,000
$3,000
$7,000
software
---
Execution + 90
days
$10,000
$1,000
$9,000
hardware
---
Execution + 90
days
$10,000
$1,000
$9,000
and testing
---
Execution + 120
days
---
---
---
Training manual
Execution + 130
days
$10,000
$1,000
$9,000
Acceptance
Testing
---
Execution + 160
days
$20,000
$2,000
$18,000
complete
Solution
Execution + 160
days
$10,000
--
$10,000
Acceptance
Execution + 210
days
--
--
$23,000
11. EVENTS AND TASKS FOR EACH MILESTONE
(If needed, provide a table of detailed project events and tasks to be accomplished to deliver the
required milestones and deliverables for the complete Solution. Reference each with the relevant
milestone. A Work Breakdown Structure can be used as shown in the table below or at the very least
a Project Plan should have this granularity. The Supplier’s proposal should be tailored to the level of
detail desired by the Authorized User’s business owner/project manager for project governance.)
The following table identifies project milestone events and deliverables in a Work Breakdown
Structure format.
WBS No.
Milestone
Milestone Event
Milestone Task
Interim Task
Deliverables
Duration
1.0
Site survey
1.1
Conduct
interviews
1,1,1
Schedule
interviews
None
20 days after
contract start
1.1.2
Complete
interviews
Interview Results
Report
25 days after
contract start
1.2
Receive AU
information
Contract No. VA-161128-AT&T, Exhibit D
Page 6 of 11
12. ACCEPTANCE CRITERIA
(This section should reflect the mutually agreed upon UAT and Acceptance Criteria specific to this
engagement. Please read the VITA contract definitions for the definitions or Requirements and
Acceptance. Ensure the language in this section does not conflict with the VITA Contract language.)
Acceptance Criteria for this Solution will be based on a User Acceptance Test (UAT) designed by
Supplier and accepted by the Authorized User. The UAT will ensure that all of the requirements and
functionality required for the Solution have been successfully delivered. Supplier will provide the
Authorized User with a detailed test plan and acceptance check list based on the mutually agreed
upon UAT Plan. This UAT Plan check-list is incorporated into this SOW in Exhibit B-X.
Each deliverable created under this Statement of Work will be delivered to the Authorized User with a
Deliverable Acceptance Receipt. This receipt will describe the deliverable and provide the Authorized
User’s Project Manager with space to indicate if the deliverable is accepted, rejected, or conditionally
accepted. Conditionally Accepted deliverables will contain a list of deficiencies that need to be
corrected in order for the deliverable to be accepted by the Project Manager. The Project Manager
will have ten (10) days from receipt of the deliverable to provide Supplier with the signed Acceptance
Receipt unless an alternative schedule is mutually agreed to between Supplier and the Authorized
User in advance.
13. PROJECT ASSUMPTIONS AND PROJECT ROLES AND RESPONSIBILITIES
(This section contains areas to address project assumptions by both the Supplier and the Authorized
User and to assign project-specific roles and responsibilities between the parties. Make sure that all
assumptions are included to alleviate surprises during the project. Ensure that all primary and
secondary (as needed) roles and responsibilities are included. You will tailor the Responsibility Matrix
table below to fit your project’s needs.)
A. Project Assumptions
The following assumptions are specific to this project:
B. Project Roles and Responsibilities
The following roles and responsibilities have been defined for this project:
(Sample Responsibility Matrix)
Responsibility Matrix
Supplier
Authorized
User
Infrastructure – Preparing the system infrastructure that meets the
recommended configuration defined in Section 2B herein
√
Server Hardware
√
Server Operating
√
Server Network Connectivity
√
Relational Database Management Software (Installation and
Implementation)
√
Server Modules – Installation and Implementation
√
PC Workstations – Hardware, Operating System, Network Connectivity
√
PC Workstations – Client Software
√
Application Installation on PC Workstations
√
Wireless Network Access Points
√
Cabling, Electric and User Network Connectivity from Access Points
√
Wireless Mobile Computing Products – Scanners, printers
√
Project Planning and Management
√
√
Contract No. VA-161128-AT&T, Exhibit D
Page 7 of 11
Requirements Analysis
√
√
Application Design and Implementation
√
Product Installation, Implementation and Testing
√
Conversion Support
√
Conversion Support -- Subject Matter Expertise
√
Documentation
√
Training
√
Product Maintenance and Support
√
Problem Tracking
√
√
Troubleshooting – IT Infrastructure
√
Troubleshooting – Solution
√
14. COMMONWEALTH AND SUPPLIER-FURNISHED MATERIALS, EQUIPMENT, FACILITIES AND
PROPERTY
(In this section, provide details of any materials, equipment, facilities and property to be provided by
your Agency or the Supplier in performance of this project. If none, so state so that the requirements
are clear. If delivery of any of these is critical to the schedule, you may want to identify such delivery
with hard due dates tied to “business days after project start’ or “days after event/milestone.” Be sure
to specify the delivery and point of contact information.)
A. PROVIDED BY THE COMMONWEALTH
B. PROVIDED BY THE SUPPLIER
15. SECURITY REQUIREMENTS
(Provide (or reference as an Attachment) Authorized User’s security requirements.)
For any individual Authorized User location, security procedures may include but not be limited to:
background checks, records verification, photographing, and fingerprinting of Supplier’s employees or
agents. Supplier may, at any time, be required to execute and complete, for each individual Supplier
employee or agent, additional forms which may include non-disclosure agreements to be signed by
Supplier’s employees or agents acknowledging that all Authorized User information with which such
employees and agents come into contact while at the Authorized User site is confidential and
proprietary. Any unauthorized release of proprietary information by the Supplier or an employee or
agent of Supplier shall constitute a breach of the Contract.
Supplier shall comply with all requirements in the Security Compliance section of the Contract
16. REQUIRED STANDARDS, CERTIFICATIONS AND SPECIFICATIONS
In addition to any standards and specifications included in the Contract, Supplier shall follow the
standards and specifications listed below during performance of this effort.
(List any specific Commonwealth, VITA, Federal, engineering, trade/industry or professional
standards, certifications and specifications that Supplier is required to follow or possess in performing
this work. The first bullet includes a link to COVA-required standards for all Commonwealth
technology projects. The rest are examples only and highlighted to reflect this. If you need a waiver of
any COVA-required standard, please follow the process located at this link:
http://www.vita.virginia.gov/oversight/default.aspx?id=10344
and select the Data Standards Guidance
bulleted link. Your Customer Account Manager can assist you.
• COV ITRM Policies and Standards: http://www.vita.virginia.gov/library/default.aspx?id=537
• IEEE 802®
Contract No. VA-161128-AT&T, Exhibit D
Page 8 of 11
• HIPAA
• SAS 70 Type II
17. U.S. ENVIRONMENTAL PROTECTION AGENCY’S AND DEPARTMENT OF ENERGY’S ENERGY
STAR GUIDELINESRISK MANAGEMENT
(Risk is a function of the probability of an event occurring and the impact of the negative effects if it
does occur. Negative effects include schedule delay, increased costs, failure of dependent legacy
system interoperability, other project dependencies that don’t align with this project’s schedule, and
poor quality of deliverables. Depending on the level of risk of this project, as assessed by your Project
Manager and/or Steering Committee, this section may contain any or all of the following components,
at a level of detail commensurate with the level of risk. Remember to add them to the Deliverables
table.)
C. Initial Risk Assessment
Authorized User and Supplier shall each provide an initial assessment from their point of view.
D. Risk Management Strategy
(The list below is taken from VITA PMD template discussing what should go into a Risk Management
Strategy. Don’t forget to consider and plan for any budget contingencies to accommodate potential
risks that are identified.)
1. Risk Identification Process: The processes for risk identification.
2. Risk Evaluation and Prioritization: How risks are evaluated and prioritized.
3. Risk Mitigation Options: Describe the risk mitigation options. They must be realistic
and available to the project team.
4. Risk Plan Maintenance: Describe how the risk plan is maintained during the project
lifecycle.
5. Risk Management Responsibilities: Identify all project team members with specific risk
management responsibilities. (e.g., an individual responsible for updating the plan or an
individual assigned as a manager).
E. Risk Management Plan
(Include a description of frequency and form of reviews, project team responsibilities, steering and
oversight committee responsibilities and documentation. Be sure to add all deliverables associated
with risk strategizing and planning to the list of Deliverables.)
18. DISASTER RECOVERY
Planning for disaster recovery for your project is paramount to ensure continuity of service. The
criticalness and complexity of your project, including its workflow into other dependent systems of the
Commonwealth or federal systems, will help you determine if you require a simple contingency plan
or a full-blow contingency plan that follows the Commonwealth’s ITRM Guideline SEC508-00 found at
this link:
http://www.vita.virginia.gov/uploadedFiles/Library/ContingencyPlanningGuideline04_18_2007.pdf
It is advisable that you visit the link before making your decision on how you need to address
contingency planning and related deliverables in this SOW; as well as, how this will impact your
planned budget. A likely deliverable for this section would be a Continuity of Operations Plan. You
may choose to include the above link in your final SOW to describe what the Plan will entail. The
same link includes the following processes, which you may choose to list in your final requirements
for this section, to be performed by your team, the Supplier or both and/or a steering committee if
your project warrants such oversight and approval:
• Development of the IT components of the Continuity of Operations Plan (COOP)
• Development and exercise of the IT Disaster Recovery Plan (IT DRP) within the COOP
Contract No. VA-161128-AT&T, Exhibit D
Page 9 of 11
• Development and exercise of the IT System Backup and Restoration Plan
19. PERFORMANCE BOND
(If your project is sizeable, complex and/or critical, and the VITA Contract does not already provide for
a performance bond, you may want the Supplier to provide one. The VITA Contract may include an
Errors and Omissions insurance requirement, which would cover the Supplier’s liability for any breach
of the Contract or this SOW. Be sure to read the Contract for this information. However, if you feel
that this project warrants further performance incentive due to the project or the Supplier’s viability,
you may include the following language in this section.)
The Supplier shall post performance bond in an amount equal to one hundred percent (100%) of the
total contract value and provide a copy of the bond to Authorized user within (10) days of execution of
this SOW Agreement. In the event that the Supplier or any subcontractor or any officer, director,
employee or agent of the Supplier or any subcontractor or any parent or subsidiary corporation of the
Supplier or any subcontractor fails to fully and faithfully perform each material requirement of this
SOW Agreement, including without limitation the Supplier’s obligation to indemnify the Authorized
User, the performance bond shall be forfeited to Authorized User. The bond shall be in a form
customarily used in the technology industry and shall be written by a surety authorized to do business
in Virginia and that is acceptable to Authorized User.
20. OTHER TECHNICAL/FUNCTIONAL REQUIREMENTS
(Provide any other unique project technical and functional requirements and expectations in sufficient
detail in this section. Ensure they do not conflict with existing requirements in the VITA Contract.
Several examples are listed.)
A. Service Level Requirements
B. Mean-Time-Between-Failure Requirements
C. Data Access/Retrieval Requirements
D. Additional Warranties
21. REPORTING
(The following are examples of reporting requirements which may be included in your SOW
depending on the project’s need for governance. In an effort to help VITA monitor Supplier
performance, it is strongly recommended that the SOW include “Supplier Performance
Assessments”. These assessments may be performed at the Project Manager’s discretion and are
not mandated by VITA.)
A. Weekly/Bi-weekly Status Update.
The weekly/bi-weekly status report, to be submitted by Supplier to the Authorized User, should
include: accomplishments to date as compared to the project plan; any changes in tasks, resources
or schedule with new target dates, if necessary; all open issues or questions regarding the project;
action plan for addressing open issues or questions and potential impacts on the project; risk
management reporting.
B. Supplier Performance Self-Assessment.
Within thirty (30) days of execution of the project start, the Supplier and the Authorized User 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 Authorized
User who will have five (5) days to respond to Supplier with any comments. If the Authorized User
agrees with Supplier’s self-assessment, such Authorized User will sign the self-assessment and
submit a copy to the VITA Supplier Relationship Manager.
C. Performance Auditing
(If you have included service level requirements in the above section entitled, Other
Technical/Functional Requirements, you will want to include a requirement here for your ability to
audit the results of the Supplier’s fulfillment of all requirements, Likewise, you may want to include
Contract No. VA-161128-AT&T, Exhibit D
Page 10 of 11
your validation audit of the Supplier’s performance reporting under this Reporting section. It is
important, however, that you read the VITA contract prior to developing this section’s content so that
conflicts are avoided. Suggested language is provided below, but must be customized for your
project.)
Authorized User (or name of IV&V contractor, if there is one), will audit the results of Supplier’s
service level obligations and performance requirements on a monthly/quarterly basis, within ten
(10) days of receipt of Supplier’s self-assessments and service report(s). Any discrepancies will
be discussed between the Authorized User and Supplier and any necessary invoice/payment
adjustments will be made. If agreement cannot be reached, the Authorized User and Supplier will
escalate the matter in accordance with the Escalation provision of the Contract. (If none, you may
add your escalation procedure in this section.)
D. Supplier Performance Assessments
(You may want to develop assessments of the Supplier’s performance and disseminate such
assessments to other Authorized Users of the VITA Contract. Prior to dissemination of such
assessments, Supplier will have an opportunity to respond to the assessments, and independent
verification of the assessment may be utilized in the case of disagreement.)
22. CHANGE MANAGEMENT
(Changes to the baseline SOW must be documented for proper project oversight. Depending on your
project, you may need to manage and capture changes to configuration, incidents, deliverables,
schedule, price or other factors your team designates as critical. Any price changes must be done in
compliance with the Code of Virginia, § 2.2-4309. Modification of the contract, found at this link:
http://leg1.state.va.us/cgi-bin/legp504.exe?000+coh+2.2-4309+500825. Changes to the scope of this
SOW must stay within the boundaries of the scope of the VITA Contract.
For complex and/or major projects, it is recommended that you use the VITA PMD processes and
templates located at: http://www.vita.virginia.gov/oversight/projects/default.aspx?id=567.
Administrative or non-technical/functional changes (deliverables, schedule, point of contact, reporting,
etc.) should extrapolate the affected sections of this SOW in a “from/to” format and be placed in a
numbered modification letter referencing this SOW and date, with a new effective date. The VITA
Contract may include a template for your use or you may obtain one from the VITA Contract’s Point of
Contact. It is very important that changes do not conflict with, but do comply with, the VITA Contract,
which takes precedence. The following language may be included in this section, but additional
language is needed to list any technical/functional change management areas specific to this SOW;
i.e., configuration, incident, work flow, or any others of a technical/functional nature.)
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://leg1.state.va.us/cgi-
bin/legp504.exe?000+coh+2.2-4309+500825
All changes to this SOW shall be in written form and fully executed between the Authorized User’s
and the Supplier’s authorized representatives. For administrative changes, the parties agree to use
the change template, attached to this SOW. For technical/functional change management
requirements, listed below, the parties agree to follow the processes and use the templates provided
at this link: http://www.vita.virginia.gov/oversight/projects/default.aspx?id=567
23. 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:
Authorized User: __________________________
Supplier: _________________________
Contract No. VA-161128-AT&T, Exhibit D
Page 11 of 11
By signing below, both parties agree to the terms of this Exhibit.
Supplier: Authorized User:
___________________________________ ____________________________________
(Name of Supplier) (Name of Agency/Institution)
By: ________________________________ By: __________________________________
(Signature) (Signature)
Name: _____________________________ Name: _______________________________
(Print) (Print)
Title: ______________________________ Title: _________________________________
Agency Head or Designee
Date: ______________________________ Date: _________________________________