Contracts
Statement of Work - Site Migration
Effective April 9th 2020
DownloadTable of Contents
Statement of Work - Site Migration
Purpose: Pantheon professional services team is being engaged by Subscriber to support moving Subscriber’s current sites over to Pantheon Services.
A. Pantheon Scope. All terms not defined in this statement of work (“SOW”) shall have the meaning ascribed to them in the Order Form. Subscriber and Pantheon hereby add the following activities to be performed by Pantheon pursuant to the Order Form (“Professional Services”):
1. Pantheon will migrate those sites listed in Attachment A - “Sites within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
a. Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
B. Exclusions. Migration of sites specified in Attachment A are on an as-is basis, except as set out in Section A.2 above. The following activities are expressly excluded from Professional Services under this SOW:
1. Migration of functionality based on resources that are not available on the Pantheon platform (e.g., code that relies on specific PHP extensions or code that relies on specific server packages that are not currently on Pantheon, java, python, perl not on platform);
2. Performance or caching optimization;
3. Preservation of git history;
4. Updating of custom or contrib modules/plugins;
5. Troubleshooting or fixing issues that already existed on source server; and
6. Adding any new functionality that didn't previously exist on the site (e.g., implementation work).
C. Subscriber Responsibilities. Subscriber shall actively participate in the following manner:
1. Provide a site inventory for each site in Attachment A prior to the kick-off meeting;
2. Join and participate in the dedicated migration support channel that will be provided in Pantheon’s slack instance;
Attachment A - Sites within Scope
To be completed at the kick-off meeting by Pantheon
The sites specified below are within scope for purposes of this SOW:
Name | URL |
Attachment B - Project Requirements
To be completed at the kick-off meeting by Pantheon
A. Pantheon Team. The Pantheon team and other key roles participating for purposes of this SOW shall consist of the following initial assignments:
Initial Assignment | Role | Scope |
Pantheon Migrations, Program Manager | Escalations | |
Pantheon Migrations, Engagement Manager | Perform Pantheon scope | |
Pantheon Migrations, Engagement Manager | Perform Pantheon scope | |
Pantheon Migration Partner | If applicable, will be identified |
B. Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Migration Process Overview (single-site migration)
[Pantheon to maintain updates here starting with the kick-off meeting]
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
Migration Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Migration | Pantheon | Approximately 1 week |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch / Post Launch | Pantheon and Subscriber | 48 hours |
*Migration timelines will be affected by additional complexities. For instance, 1-2 additional weeks per secure integration, Advanced CDN configuration, or custom application engagements will be necessary. For 2-5 sites, allow an additional 2 weeks. Add approximately 2 weeks for each additional 5 sites.
C. Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
1. None, unless otherwise specified.
D. Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
1. None, unless otherwise specified.
E. Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Effective April 8th 2020 to April 9th 2020
DownloadTable of Contents
Statement of Work - Site Migration
Purpose: Pantheon professional services team is being engaged by Subscriber to support moving Subscriber’s current sites over to Pantheon Services with the objective of achieving reasonable performance parity.
A. Pantheon Scope. All terms not defined in this statement of work (“SOW”) shall have the meaning ascribed to them in the Order Form. Subscriber and Pantheon hereby add the following activities to be performed by Pantheon pursuant to the Order Form (“Professional Services”):
1. Pantheon will migrate those sites listed in Attachment A - “Sites within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
a. Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
B. Exclusions. Migration of sites specified in Attachment A are on an as-is basis, except as set out in Section A.2 above. The following activities are expressly excluded from Professional Services under this SOW:
1. Migration of functionality based on resources that are not available on the Pantheon platform (e.g., code that relies on specific PHP extensions or code that relies on specific server packages that are not currently on Pantheon, java, python, perl not on platform);
2. Performance or caching optimization;
3. Preservation of git history;
4. Updating of custom or contrib modules/plugins;
5. Troubleshooting or fixing issues that already existed on source server; and
6. Adding any new functionality that didn't previously exist on the site (e.g., implementation work).
C. Subscriber Responsibilities. Subscriber shall actively participate in the following manner:
1. Provide a site inventory for each site in Attachment A prior to the kick-off meeting;
2. Join and participate in the dedicated migration support channel that will be provided in Pantheon’s slack instance;
Attachment A - Sites within Scope
To be completed at the kick-off meeting by Pantheon
The sites specified below are within scope for purposes of this SOW:
Name | URL |
Attachment B - Project Requirements
To be completed at the kick-off meeting by Pantheon
A. Pantheon Team. The Pantheon team and other key roles participating for purposes of this SOW shall consist of the following initial assignments:
Initial Assignment | Role | Scope |
Pantheon Migrations, Program Manager | Escalations | |
Pantheon Migrations, Engagement Manager | Perform Pantheon scope | |
Pantheon Migrations, Engagement Manager | Perform Pantheon scope | |
Pantheon Migration Partner | If applicable, will be identified |
B. Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Migration Process Overview (single-site migration)
[Pantheon to maintain updates here starting with the kick-off meeting]
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
Migration Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Migration | Pantheon | Approximately 1 week |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch / Post Launch | Pantheon and Subscriber | 48 hours |
*Migration timelines will be affected by additional complexities. For instance, 1-2 additional weeks per secure integration, Advanced CDN configuration, or custom application engagements will be necessary. For 2-5 sites, allow an additional 2 weeks. Add approximately 2 weeks for each additional 5 sites.
C. Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
1. None, unless otherwise specified.
D. Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
1. None, unless otherwise specified.
E. Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Effective April 8th 2020 to April 8th 2020
DownloadTable of Contents
Statement of Work - Site Migration
Purpose: Pantheon professional services team is being engaged by Subscriber to support moving Subscriber’s current sites over to Pantheon Services with the objective of achieving reasonable performance parity.
A. Pantheon Scope. All terms not defined in this statement of work (“SOW”) shall have the meaning ascribed to them in the Order Form. Subscriber and Pantheon hereby add the following activities to be performed by Pantheon pursuant to the Order Form (“Professional Services”):
1. Pantheon will migrate those sites listed in Attachment A - “Sites within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
a. Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
B. Exclusions. Migration of sites specified in Attachment A are on an as-is basis, except as set out in Section A.2 above. The following activities are expressly excluded from Professional Services under this SOW:
1. Migration of functionality based on resources that are not available on the Pantheon platform (e.g., code that relies on specific php extensions or code that relies on specific server packages that are not currently on Pantheon, java, python, perl not on platform);
2. Performance or caching optimization;
3. Preservation of git history;
4. Updating of custom or contrib modules;
5. Troubleshooting or fixing issues that already existed on source server; and
6. Adding any new functionality that didn't previously exist on the site (e.g., implementation work).
C. Subscriber Responsibilities. Subscriber shall actively participate in the following manner:
1. Provide a site inventory for each site in Attachment A prior to the kick-off meeting;
2. Join and participate in the dedicated migration support channel that will be provided in Pantheon’s slack instance;
Attachment A - Sites within Scope
To be completed at the kick-off meeting by Pantheon
The sites specified below are within scope for purposes of this SOW:
Name | URL |
Attachment B - Project Requirements
To be completed at the kick-off meeting by Pantheon
A. Pantheon Team. The Pantheon team and other key roles participating for purposes of this SOW shall consist of the following initial assignments:
Initial Assignment | Role | Scope |
Pantheon Migrations, Program Manager | Escalations | |
Pantheon Migrations, Engagement Manager | Perform Pantheon scope | |
Pantheon Migrations, Engagement Manager | Perform Pantheon scope | |
Pantheon Migration Partner | If applicable, will be identified |
B. Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Migration Process Overview (single-site migration)
[Pantheon to maintain updates here starting with the kick-off meeting]
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
Migration Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Migration | Pantheon | Approximately 1 week |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch / Post Launch | Pantheon and Subscriber | 48 hours |
*Migration timelines will be affected by additional complexities. For instance, 1-2 additional weeks per secure integration, Advanced CDN configuration, or custom application engagements will be necessary. For 2-5 sites, allow an additional 2 weeks. Add approximately 2 weeks for each additional 5 sites.
C. Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
1. None, unless otherwise specified.
D. Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
1. None, unless otherwise specified.
E. Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Statement of Work - Managed Updates
Effective July 11th 2020
DownloadTable of Contents
Statement of Work - Managed Updates
Purpose: Pantheon’s professional services team is being engaged by Subscriber to apply updates to the core and contrib modules/plugins of Drupal and WordPress. These updates are detected and validated to provide a model for the timely update of sites and apply visual regression testing.
A. Pantheon Scope. All terms not defined in this statement of work (“SOW”) shall have the meaning ascribed to them in the Order Form. Subscriber and Pantheon hereby add the following activities to be performed by Pantheon pursuant to the Order Form (“Professional Services”):
- Pantheon will update sites only as specified in the inclusion list and confirmed in writing by Pantheon through the kick-off meeting as set out in Attachment A - “Sites within Scope” to this SOW. Any sites not listed in Attachment A are excluded from the scope of this SOW.
- Managed updates for sites specified in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Performing initial updates and patches (patches applicable to Drupal 8 only) to the sites and applicable core and contrib modules listed in Attachment A;
- Updates shall be applied in accordance with Pantheon’s development workflow tools;
- For any failures during testing process, provide the following: (i) prompt alerts of failure by email (ii) support identification of the root cause of error, (iii) recommendations around possible solutions to be decided by Subscriber, and (iv) designate an engagement manager to support Subscriber in the event of a failure to apply an update;
- Provide visual Regression testing of up to 20 urls;
- Apply updates to the git repository for any Pantheon efforts under this SOW;
- Monitor and provide security updates to applicable core and contrib modules within 3 business days of detection;
- Monitor and provide other updates in scope (as set out in Attachment B) within one week of their release.
B. Exclusions. Services are provided in accordance with Section A.2 above. The following activities are expressly excluded from Professional Services under this SOW:
- Application issues that may arise from implementing the Services is out of scope; and
- Any integration scope of services would require a separate custom development workflow (available separately as a service offering).
C. Subscriber Responsibilities. Subscriber shall actively participate in the following manner:
- Provide the Pantheon team with timely updates regarding Attachments A and B hereto; and
- At Subscriber’s option, perform user acceptance testing with multidev during the 3 business day period before updates are deployed for the Services hereunder.
Attachment A - Sites within Scope
To be completed at the kick-off meeting by Pantheon
The sites specified below are within scope for purposes of this SOW:
Name | URL |
Included core and contrib modules for updates | |
Applicable URLs for Visual regression test | |
Attachment B - Project Requirements
To be completed at the kick-off meeting by Pantheon
Initial Assignment | Role | Scope |
Managed Updates Process Overview
Provided below is an overview of the process for managed updates:
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
Subscriber understands that the Pantheon Team for this SOW has usual business hours and is available between Monday to Friday, 8am to 5pm EST. Outside of these hours, Subscriber may reach out to Pantheon's support team.
E. Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Effective April 8th 2020 to July 11th 2020
DownloadTable of Contents
Statement of Work - Managed Updates
Purpose: Pantheon’s professional services team is being engaged by Subscriber to apply updates to the core and contrib modules/plugins of Drupal and WordPress. These updates are detected and validated to provide a model for the timely update of sites and apply visual regression testing.
A. Pantheon Scope. All terms not defined in this statement of work (“SOW”) shall have the meaning ascribed to them in the Order Form. Subscriber and Pantheon hereby add the following activities to be performed by Pantheon pursuant to the Order Form (“Professional Services”):
- Pantheon will update sites only as specified in the inclusion list and confirmed in writing by Pantheon through the kick-off meeting as set out in Attachment A - “Sites within Scope” to this SOW. Any sites not listed in Attachment A are excluded from the scope of this SOW.
- Managed updates for sites specified in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Performing initial updates and patches (patches applicable to Drupal 8 only) to the sites and applicable core and contrib modules listed in Attachment A;
- Updates shall be applied in accordance with Pantheon’s development workflow tools;
- For any failures during testing process, provide the following: (i) prompt alerts of failure by email (ii) support identification of the root cause of error, (iii) recommendations around possible solutions to be decided by Subscriber, and (iv) designate an engagement manager to support Subscriber in the event of a failure to apply an update;
- Provide visual Regression testing of up to 20 urls;
- Apply updates to the git repository for any Pantheon efforts under this SOW;
- Monitor and provide security updates to applicable core and contrib modules within 3 business days of detection;
- Monitor and provide other updates in scope (as set out in Attachment B) within one week of their release.
B. Exclusions. Services are provided in accordance with Section A.2 above. The following activities are expressly excluded from Professional Services under this SOW:
- Application issues that may arise from implementing the Services is out of scope; and
- Any integration scope of services would require a separate custom development workflow (available separately as a service offering).
C. Subscriber Responsibilities. Subscriber shall actively participate in the following manner:
- Provide the Pantheon team with timely updates regarding Attachments A and B hereto; and
- At Subscriber’s option, perform user acceptance testing with multidev during the 3 business day period before updates are deployed for the Services hereunder.
Attachment A - Sites within Scope
To be completed at the kick-off meeting by Pantheon
The sites specified below are within scope for purposes of this SOW:
Name | URL |
Included core and contrib modules for updates | |
Applicable URLs for Visual regression test | |
Attachment B - Project Requirements
To be completed at the kick-off meeting by Pantheon
Initial Assignment | Role | Scope |
Managed Updates Process Overview
Provided below is an overview of the process for managed updates:
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration |
E. Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Effective April 8th 2020 to April 8th 2020
DownloadTable of Contents
Statement of Work - Managed Updates
Purpose: Pantheon’s professional services team is being engaged by Subscriber to apply updates to the core and contrib modules/plugins of Drupal and WordPress. These updates are detected and validated to provide a model for the timely update of sites and apply visual regression testing.
A. Pantheon Scope. All terms not defined in this statement of work (“SOW”) shall have the meaning ascribed to them in the Order Form. Subscriber and Pantheon hereby add the following activities to be performed by Pantheon pursuant to the Order Form (“Professional Services”):
- Pantheon will update sites only as specified in the inclusion list and confirmed in writing by Pantheon through the kick-off meeting as set out in Attachment A - “Sites within Scope” to this SOW. Any sites not listed in Attachment A are excluded from the scope of this SOW.
- Managed updates for sites specified in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Performing initial updates and patches (patches applicable to Drupal 8 only) to the sites and applicable core and contrib modules listed in Attachment A;
- Updates shall be applied in accordance with Pantheon’s development workflow tools;
- For any failures during testing process, provide the following: (i) prompt alerts of failure by email (ii) support identification of the root cause of error, (iii) recommendations around possible solutions to be decided by Subscriber, and (iv) designate an engagement manager to support Subscriber in the event of a failure to apply an update;
- Provide visual Regression testing of up to 20 urls;
- Apply updates to the git repository for any Pantheon efforts under this SOW;
- Monitor and provide security updates to applicable core and contrib modules within 3 business days of detection;
- Monitor and provide other updates in scope (as set out in Attachment B) within one week of their release.
B. Exclusions. Services are provided in accordance with Section A.2 above. The following activities are expressly excluded from Professional Services under this SOW:
- Application issues that may arise from implementing the Services is out of scope; and
- Any integration scope of services would require a separate custom development workflow (available separately as a service offering).
C. Subscriber Responsibilities. Subscriber shall actively participate in the following manner:
- Provide the Pantheon team with timely updates regarding Attachments A and B hereto; and
- At Subscriber’s option, perform user acceptance testing with multidev during the 3 business day period before updates are deployed for the Services hereunder.
Attachment A - Sites within Scope
To be completed at the kick-off meeting by Pantheon
The sites specified below are within scope for purposes of this SOW:
Name | URL |
Included core and contrib modules for updates | |
Applicable URLs for Visual regression test | |
Attachment B - Project Requirements
To be completed at the kick-off meeting by Pantheon
Initial Assignment | Role | Scope |
Managed Updates Process Overview
Provided below is an overview of the process for managed updates:
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration |
E. Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Statement of Work - Advanced Global CDN
Effective June 11th 2025
DownloadTable of Contents
- Pantheon will provide AGCDN services as listed in Attachment A - “AGCDN Services within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
- AGCDN Services included in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Customization or configuration of AGCDN based on Attachment A.
- Updates to the core and contrib modules/plugins of Drupal and WordPress;
- Site Migration from Subscriber’s current sites to Pantheon Services; and
- AGCDN Services that are not in scope, as specified in Attachment A.
- Join and participate in the dedicated AGCDN support channel that will be provided in Pantheon’s slack instance;
- Provide Pantheon AGCDN team with necessary access to current host or to code, database, and files;
- Perform any user acceptance testing within the timeline specified in Attachment B;
- Perform DNS cutover within the timeline specified in Attachment B.
Within Scope? Yes/No | AGCDN SERVICES |
Image Optimization (IO) | |
Geo Block or Allow Listing | |
IP Block or Allow Listing | |
Non-Pantheon Origins | |
Custom Rewrites | |
URL Redirects | |
Non SSL | |
Domain Masking | |
Custom TLS Certificates | |
Web Application Firewall (WAF) | |
| Rate Limiting | |
Others: | |
Others: | |
Others: |
- Pantheon Team. Pantheon will make available resources to provide the Professional Services described in this SOW, which may include consultation and configuration.
- Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
AGCDN Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Configuration or Customization | Pantheon | Approximately 3 weeks |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch** / Post Launch | Pantheon and Subscriber | 48 hours |
- Deemed Acceptance. Subscriber will be deemed to have accepted the AGCDN Services if Subscriber fails to notify Pantheon in writing prior to the end of the User Acceptance Testing Period that it has passed or failed its User Acceptance Tests.
- Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
- None, unless otherwise specified.
- Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
- None, unless otherwise specified.
- Change Management. Pantheon shall provide 4 hours of change management per quarter, scheduled between Mondays to Fridays, 9am to 5pm Eastern Standard time. Change Management usage is not applicable for new feature development, front end work, or other tasks generally reserved for normal support services. Change Management usage requested in excess of 4 hours shall be billed according to Pantheon’s Professional Services rates. Unused hours shall automatically expire at the end of each quarter.
- New Features. Subscriber can request new features at no additional charge. “New Features” is defined as a service not scoped in Attachment A and would take more than the Subscriber’s balance of Change Management hours in the current quarter. New Features will require a new Statement of Work between the parties.
- Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Effective February 1st 2021 to June 11th 2025
DownloadTable of Contents
- Pantheon will provide AGCDN services as listed in Attachment A - “AGCDN Services within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
- AGCDN Services included in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Customization or configuration of AGCDN based on Attachment A.
- Updates to the core and contrib modules/plugins of Drupal and WordPress;
- Site Migration from Subscriber’s current sites to Pantheon Services; and
- AGCDN Services that are not in scope, as specified in Attachment A.
- Join and participate in the dedicated AGCDN support channel that will be provided in Pantheon’s slack instance;
- Provide Pantheon AGCDN team with necessary access to current host or to code, database, and files;
- Perform any user acceptance testing within the timeline specified in Attachment B;
- Perform DNS cutover within the timeline specified in Attachment B.
Within Scope? Yes/No | AGCDN SERVICES |
Image Optimization (IO) | |
Geo Block or Allow Listing | |
IP Block or Allow Listing | |
Non-Pantheon Origins | |
Custom Rewrites | |
URL Redirects | |
Non SSL | |
Domain Masking | |
Custom TLS Certificates | |
Add on: Web Application Firewall (WAF) | |
Others: | |
Others: | |
Others: |
- Pantheon Team. Pantheon will make available resources to provide the Professional Services described in this SOW, which may include consultation and configuration.
- Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
AGCDN Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Configuration or Customization | Pantheon | Approximately 3 weeks |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch** / Post Launch | Pantheon and Subscriber | 48 hours |
- Deemed Acceptance. Subscriber will be deemed to have accepted the AGCDN Services if Subscriber fails to notify Pantheon in writing prior to the end of the User Acceptance Testing Period that it has passed or failed its User Acceptance Tests.
- Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
- None, unless otherwise specified.
- Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
- None, unless otherwise specified.
- Change Management. Pantheon shall provide 4 hours of change management per quarter, scheduled between Mondays to Fridays, 9am to 5pm Eastern Standard time. Change Management usage is not applicable for new feature development, front end work, or other tasks generally reserved for normal support services. Change Management usage requested in excess of 4 hours shall be billed according to Pantheon’s Professional Services rates. Unused hours shall automatically expire at the end of each quarter.
- New Features. Subscriber can request new features at no additional charge. “New Features” is defined as a service not scoped in Attachment A and would take more than the Subscriber’s balance of Change Management hours in the current quarter. New Features will require a new Statement of Work between the parties.
- Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Effective July 1st 2020 to February 1st 2021
DownloadTable of Contents
- Pantheon will provide AGCDN services as listed in Attachment A - “AGCDN Services within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
- AGCDN Services included in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Customization or configuration of AGCDN based on Attachment A.
- Updates to the core and contrib modules/plugins of Drupal and WordPress;
- Site Migration from Subscriber’s current sites to Pantheon Services; and
- AGCDN Services that are not in scope, as specified in Attachment A.
- Join and participate in the dedicated AGCDN support channel that will be provided in Pantheon’s slack instance;
- Provide Pantheon AGCDN team with necessary access to current host or to code, database, and files;
- Perform any user acceptance testing within the timeline specified in Attachment B;
- Perform DNS cutover within the timeline specified in Attachment B.
Within Scope? Yes/No | AGCDN SERVICES |
Image Optimization (IO) | |
Geo Black or White Listing | |
IP Black or White Listing | |
Non-Pantheon Origins | |
Custom Rewrites | |
URL Redirects | |
Non SSL | |
Domain Masking | |
Custom TLS Certificates | |
Add on: Web Application Firewall (WAF) | |
Others: | |
Others: | |
Others: |
- Pantheon Team. Pantheon will make available resources to provide the Professional Services described in this SOW, which may include consultation and configuration.
- Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
AGCDN Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Configuration or Customization | Pantheon | Approximately 3 weeks |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch** / Post Launch | Pantheon and Subscriber | 48 hours |
- Deemed Acceptance. Subscriber will be deemed to have accepted the AGCDN Services if Subscriber fails to notify Pantheon in writing prior to the end of the User Acceptance Testing Period that it has passed or failed its User Acceptance Tests.
- Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
- None, unless otherwise specified.
- Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
- None, unless otherwise specified.
- Change Management. Pantheon shall provide 4 hours of change management per quarter, scheduled between Mondays to Fridays, 9am to 5pm Eastern Standard time. Change Management usage is not applicable for new feature development, front end work, or other tasks generally reserved for normal support services. Change Management usage requested in excess of 4 hours shall be billed according to Pantheon’s Professional Services rates. Unused hours shall automatically expire at the end of each quarter.
- New Features. Subscriber can request new features at no additional charge. “New Features” is defined as a service not scoped in Attachment A and would take more than the Subscriber’s balance of Change Management hours in the current quarter. New Features will require a new Statement of Work between the parties.
- Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
Effective May 13th 2020 to July 1st 2020
DownloadTable of Contents
- Pantheon will provide AGCDN services as listed in Attachment A - “AGCDN Services within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
- AGCDN Services included in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Customization or configuration of AGCDN based on Attachment A.
- Updates to the core and contrib modules/plugins of Drupal and WordPress;
- Site Migration from Subscriber’s current sites to Pantheon Services; and
- AGCDN Services that are not in scope, as specified in Attachment A.
- Join and participate in the dedicated AGCDN support channel that will be provided in Pantheon’s slack instance;
- Provide Pantheon AGCDN team with necessary access to current host or to code, database, and files;
- Perform any user acceptance testing within the timeline specified in Attachment B;
- Perform DNS cutover within the timeline specified in Attachment B.
Within Scope? Yes/No | AGCDN SERVICES |
Image Optimization (IO) | |
Geo Black or White Listing | |
IP Black or White Listing | |
Non-Pantheon Origins | |
Custom Rewrites | |
URL Redirects | |
Non SSL | |
Domain Masking | |
Custom TLS Certificates | |
Add on: Web Application Firewall (WAF) | |
Others: | |
Others: | |
Others: |
- Pantheon Team. Pantheon will make available resources to provide the Professional Services described in this SOW, which may include consultation and configuration.
- Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
AGCDN Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Configuration or Customization | Pantheon | Approximately 3 weeks |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch** / Post Launch | Pantheon and Subscriber | 48 hours |
- Deemed Acceptance. Subscriber will be deemed to have accepted the AGCDN Services if Subscriber fails to notify Pantheon in writing prior to the end of the User Acceptance Testing Period that it has passed or failed its User Acceptance Tests.
- Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
- None, unless otherwise specified.
- Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
- None, unless otherwise specified.
- Change Management. Pantheon shall provide 4 hours of change management per quarter, scheduled between Mondays to Fridays, 9am to 5pm Eastern Standard time. Change Management usage is not applicable for new feature development, front end work, or other tasks generally reserved for normal support services. Change Management usage requested in excess of 4 hours shall be billed according to Pantheon’s Professional Services rates. Unused hours shall automatically expire at the end of each quarter.
- New Features. Subscriber can request new features at no additional charge. “New Features” is defined as a service not scoped in Attachment A and would take more than the Subscriber’s balance of Change Management hours in the current quarter. New Features will require a new Statement of Work between the parties.
- Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
- [Include this section for Diamond Usage] Support for Diamond Usage. Diamond Users can apply their Diamond Support hours to supplement Change Management hours.
Effective May 13th 2020 to May 13th 2020
DownloadTable of Contents
- Pantheon will provide AGCDN services as listed in Attachment A - “AGCDN Services within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
- AGCDN Services included in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Customization or configuration of AGCDN based on Attachment A.
- Updates to the core and contrib modules/plugins of Drupal and WordPress;
- Site Migration from Subscriber’s current sites to Pantheon Services; and
- AGCDN Services that are not in scope, as specified in Attachment A.
- Join and participate in the dedicated AGCDN support channel that will be provided in Pantheon’s slack instance;
- Provide Pantheon AGCDN team with necessary access to current host or to code, database, and files;
- Perform any user acceptance testing within the timeline specified in Attachment B;
- Perform DNS cutover within the timeline specified in Attachment B.
Within Scope? Yes/No | AGCDN SERVICES |
Image Optimization (IO) | |
Geo Black or White Listing | |
IP Black or White Listing | |
Non-Pantheon Origins | |
Custom Rewrites | |
URL Redirects | |
Non SSL | |
Domain Masking | |
Custom TLS Certificates | |
Add on: Web Application Firewall (WAF) | |
Others: | |
Others: | |
Others: |
- Pantheon Team. Pantheon will make available resources to provide the Professional Services described in this SOW, which may include consultation and configuration.
- Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
AGCDN Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Configuration or Customization | Pantheon | Approximately 3 weeks |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch** / Post Launch | Pantheon and Subscriber | 48 hours |
- Deemed Acceptance. Subscriber will be deemed to have accepted the AGCDN Services if Subscriber fails to notify Pantheon in writing prior to the end of the User Acceptance Testing Period that it has passed or failed its User Acceptance Tests.
- Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
- None, unless otherwise specified.
- Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
- None, unless otherwise specified.
- Change Management. Pantheon shall provide 4 hours of change management per quarter, scheduled between Mondays to Fridays, 9am to 5pm Eastern Standard time. Change Management usage is not applicable for new feature development, front end work, or other tasks generally reserved for normal support services. Change Management usage requested in excess of 4 hours shall be billed according to Pantheon’s Professional Services rates. Unused hours shall automatically expire at the end of each quarter.
- New Features. Subscriber can request new features at no additional charge. “New Features” is defined as a service not scoped in Attachment A and would take more than the Subscriber’s balance of Change Management hours in the current quarter. New Features will require a new Statement of Work between the parties.
- Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
- [Include this section for Diamond Usage] Support for Diamond Usage. Diamond Users can apply their Diamond Support hours to supplement Change Management hours.
Effective May 13th 2020 to May 13th 2020
DownloadTable of Contents
- Pantheon will provide AGCDN services as listed in Attachment A - “AGCDN Services within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
- AGCDN Services included in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Customization or configuration of AGCDN based on Attachment A.
- Updates to the core and contrib modules/plugins of Drupal and WordPress;
- Site Migration from Subscriber’s current sites to Pantheon Services; and
- AGCDN Services that are not in scope, as specified in Attachment A.
- Join and participate in the dedicated AGCDN support channel that will be provided in Pantheon’s slack instance;
- Provide Pantheon AGCDN team with necessary access to current host or to code, database, and files;
- Perform any user acceptance testing within the timeline specified in Attachment B;
- Perform DNS cutover within the timeline specified in Attachment B.
Within Scope? Yes/No | AGCDN SERVICES |
Image Optimization (IO) | |
Geo Black or White Listing | |
IP Black or White Listing | |
Non-Pantheon Origins | |
Custom Rewrites | |
URL Redirects | |
Non SSL | |
Domain Masking | |
Custom TLS Certificates | |
Add on: Web Application Firewall (WAF) | |
Others: | |
Others: | |
Others: |
- Pantheon Team. Pantheon will make available resources to provide the Professional Services described in this SOW, which may include consultation and configuration.
- Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
AGCDN Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Configuration or Customization | Pantheon | Approximately 3 weeks |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch** / Post Launch | Pantheon and Subscriber | 48 hours |
- Deemed Acceptance. Subscriber will be deemed to have accepted the AGCDN Services if Subscriber fails to notify Pantheon in writing prior to the end of the User Acceptance Testing Period that it has passed or failed its User Acceptance Tests.
- Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
- None, unless otherwise specified.
- Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
- None, unless otherwise specified.
- Change Management. Pantheon shall provide 4 hours of change management per quarter, scheduled between Mondays to Fridays, 9am to 5pm Eastern Standard time. Change Management usage is not applicable for new feature development, front end work, or other tasks generally reserved for normal support services. Change Management usage requested in excess of 4 hours shall be billed according to Pantheon’s Professional Services rates. Unused hours shall automatically expire at the end of each quarter.
- New Features. Subscriber can request new features at no additional charge. “New Features” is defined as a service not scoped in Attachment A and would take more than the Subscriber’s balance of Change Management hours in the current quarter. New Features will require a new Statement of Work between the parties.
- Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
- [Include this section for Diamond Usage] Support for Diamond Usage. Diamond Users can apply their Diamond Support hours to supplement Change Management hours.
Effective May 12th 2020 to May 13th 2020
DownloadTable of Contents
- Pantheon will provide AGCDN services as listed in Attachment A - “AGCDN Services within Scope” to this SOW as confirmed through the kick-off meeting. Any sites not listed in Attachment A or otherwise exceeding the number of sites specified in the Order Form requiring migration hereunder shall require a Change Order and additional scoping.
- AGCDN Services included in Attachment A shall consist of:
- Initial kick-off meeting as scheduled by Pantheon with Subscriber to confirm timeline, deliverables, project team, and project scope in the format set out in Attachment B - “Project Requirements” to this SOW;
- Customization or configuration of AGCDN based on Attachment A.
- Updates to the core and contrib modules/plugins of Drupal and WordPress;
- Site Migration from Subscriber’s current sites to Pantheon Services; and
- AGCDN Services that are not in scope, as specified in Attachment A.
- Join and participate in the dedicated AGCDN support channel that will be provided in Pantheon’s slack instance;
- Provide Pantheon AGCDN team with necessary access to current host or to code, database, and files;
- Perform any user acceptance testing within the timeline specified in Attachment B;
- Perform DNS cutover within the timeline specified in Attachment B.
Within Scope? Yes/No | AGCDN SERVICES |
Image Optimization (IO) | |
Geo Black or White Listing | |
IP Black or White Listing | |
Non-Pantheon Origins | |
Custom Rewrites | |
URL Redirects | |
Non SSL | |
Domain Masking | |
Custom TLS Certificates | |
Add on: Web Application Firewall (WAF) | |
Others: | |
Others: | |
Others: |
- Pantheon Team. Pantheon will make available resources to provide the Professional Services described in this SOW, which may include consultation and configuration.
- Timeline. The estimated timeline for the Professional Services below is subject to Subscriber’s availability and requirements for the Professional Services remaining unchanged from the kick-off meeting. Pantheon Professional Services shall not exceed the scope specified in this SOW without a subsequent signed written amendment and adjustment to the Fees.
Process Overview | Owner (Pantheon vs. Subscriber) | Start Date and Duration* |
AGCDN Kickoff | Pantheon and Subscriber | 1 - 1.5 hours |
Information Collection | Subscriber | Approximately 1 week |
Initial Configuration or Customization | Pantheon | Approximately 3 weeks |
User Acceptance Testing | Pantheon and Subscriber | Approximately 2 weeks |
Launch Planning | Pantheon and Subscriber | Approximately 1 week |
Launch** / Post Launch | Pantheon and Subscriber | 48 hours |
- Deemed Acceptance. Subscriber will be deemed to have accepted the AGCDN Services if Subscriber fails to notify Pantheon in writing prior to the end of the User Acceptance Testing Period that it has passed or failed its User Acceptance Tests.
- Adjustments to Project Scope. This SOW shall include the following adjustments to the Professional Services. Except as specifically set out below, Pantheon shall not be responsible for any additional activities except as set out in the standard Pantheon Professional Services SOW.
- None, unless otherwise specified.
- Deliverables. Except as specifically set out below, this SOW does not include any specific Deliverables, which are defined as the tangible work product of the Professional Services performed by Pantheon on behalf of Subscriber under this SOW.
- None, unless otherwise specified.
- Change Management. Pantheon shall provide 4 hours of change management per quarter, scheduled between Mondays to Fridays, 9am to 5pm Eastern Standard time. Change Management usage is not applicable for new feature development, front end work, or other tasks generally reserved for normal support services. Change Management usage requested in excess of 4 hours shall be billed according to Pantheon’s Professional Services rates. Unused hours shall automatically expire at the end of each quarter.
- New Features. Subscriber can request new features at no additional charge. “New Features” is defined as a service not scoped in Attachment A and would take more than the Subscriber’s balance of Change Management hours in the current quarter. New Features will require a new Statement of Work between the parties.
- Any known issues or limitations. Pantheon and Subscriber have identified the following issues or limitations during the course of the kick-off meeting as specified below. Any other material issues or limitations shall result in a separate signed written SOW between the parties.
- [Include this section for Diamond Usage] Support for Diamond Usage. Diamond Users can apply their Diamond Support hours to supplement Change Management hours.