Planview_AdaptiveWork-Planview_to_3rd_Party_Integrations_-_Scope_of_Work_TSD-20261922.pdf

Integration Subscription Scope Description

The Planview Connectivity Subscription defined herein is designed to help companies connect their Planview product(s) to third-party product(s) where there is an endpoint-to-endpoint integration need. This Subscription includes the integration platform, implementation and hosting as well as support for changes during the subscription term.

Utilizing the Planview Deployment Methodology, Planview will work with its customers during the engagement to align on the desired outcome(s) for their integration(s) and advise on which Planview Connectivity Solution best fits their need.

The schedule for the design, development and deployment of the integration(s) to be mutually agreed by both parties.

Overview The Planview Connectivity Subscription is based on the number of Integration Data Streams.

During the subscription period, Planview shall provide the following as outlined below:

Scope

Subscription Feature Description Details Number of Integrations Distinct Integration Data Streams 2

Integration Platform Available IAAS and/or PV Hub with OOTB Connectors •

Implementation & Hosting Documentation, Development, Deployment •

Support & Maintenance Integration support via Planview Portal •

Integration Assurance Number of hours per annum to assist with changes 15hrs/year

Additional Details Platform finalized during engagement See Appendix

Notes:

• Planview product must be the source or destination for any integration.

• A distinct integration stream is defined as a single directional data flow between two systems and counts as a separate integration.

• Customers must provide access to the systems involved in the integration as required.

• Integration Assurance hours do not roll over from year to year; they are on a “use it or lose it” basis.

• Integration Assurance hours cannot be used for the development or implementation of new integrations.

• Any work initiated by Customer in the final month of the period must be completed before the Period ends.

• For details see description of PV Hub out-of-the-box (OOTB) connectors in the Planview Customer

Success Center (CSC).

Planview AdaptiveWork-Planview to 3rd Party Integrations - Scope of Work

Exclusions Except to the extent expressly described in this Scope Description, the following services are excluded. These services may be performed by Planview under a separate Scope Description, if desired by Customer.

• Reporting services (e.g. specialized PowerBI reporting) not defined herein

• Planview Hub Universal Connector services

• Artifact Association migration

• Training and education services

• Data entry services not defined here

Planview AdaptiveWork-Planview to 3rd arty Integrations - Scope of Work

Applies to Planview Hub Integrations

The Midmarket Enablement defined herein is designed to help companies rapidly deploy the Planview Hub product where there is an endpoint-to-endpoint integration need. This program provides training, best practice recommendations, and support for the introduction of Planview Hub into a Customer’s environment.

Utilizing the Planview Deployment Methodology, Hub Administrators will be empowered with the knowledge and skills to configure and maintain Planview Hub to meet their needs.

Overview This Midmarket Enablement includes training through the University of Planview and one-on-one coaching with a Hub Consultant where the customer will perform all integration deployment & configuration as described in this document. The duration of this enablement is up to 8 weeks from kick-off or until Hub is deployed, whichever comes first. The Planview Consultant will guide the Customer’s resource(s) to successful completion.

Scope

Third-party Source Repositories Non-Planview source Lifecycle tool connections Up to 1

Project 1 to1 mapping between a single pairing of projects between each repository 1

Artifact/Issue type Mapping for a repository artifact/issue type (e.g., Epic, Story) Up to 2

Models Common template used to normalize field types and field values Up to 2

Extensions Example of an Extension scenario could include:

• Defining person reconciliation strategies between repositories

• Enabling one custom data transformation between fields

Up to 10

Integration Mechanism for connecting source repositories to target repositories and vice versa

Up to 2

Field Mapping Mechanism for connecting source repositories to target repositories and vice versa

Up to 15

Enablement Highlights

Training The Midmarket Enablement includes access to The University of Planview catalog of virtual on-demand training courses. The catalog comprises of courses such as an Introduction to Planview Hub, Integration Basics, Monitoring and Optimizing as well as others.

Planview Consultant During the 8-week enablement, the Hub Consultant will lead the Customer through the deployment and enablement process by supporting them through the deployment methodology below.

Deployment Methodology

• Assess--work with key Customer stakeholders to review integration patterns to understand relevant artifacts and data flows within the existing environments.

• Design--guide Customer in identifying artifact mappings between repositories, assist in data format analysis.

• Validate--assist Customer in testing Planview Hub.

• Launch--assist Customer in deployment of Planview Hub to the production environment.

Logistics The Consulting Services will be performed remotely. Enablement support will be provided during normal business hours, Monday through Friday, except holidays.

Applies to IaaS Integrations

The Midmarket Integration as a Service (IaaS) defined herein is designed to help companies deploy custom integrations where there is an endpoint-to-endpoint integration need.

Overview This Midmarket IaaS includes requirement gathering, specifications, development and deployment where the Customer and Planview will work collaboratively as described in this document to achieve the desired customer outcomes.

Scope Midmarket IaaS includes up to 2 integration streams. For each individual Integration Stream, the following is included:

IaaS Activity Design of the Integration and Development of the Integration Specification Develop and test the Integration stream according to the approved Integration Specification.

Deploy individual Integration stream to Planview Sandbox environment Provide guidance and support during Customer’s UAT phase Provide potential rework after Customer’s UAT findings Deploy Integration stream to Planview target Production environment

IaaS Highlights

Collaboration Integration as a Service is a strong collaboration between the customer and Planview where the customer’s subject matter experts will actively participate in requirements gathering sessions, provide expertise on their systems to be integrated, participate in specification development, User Acceptance Testing (UAT) as well as other activities until the desired custom integration is successfully deployed.

Planview Consultant The IaaS Consultant will lead the Customer through the deployment methodology outlined below.

Deployment Methodology For each Integration Stream, the customer and Planview will work together utilizing the following approach:

Specification Development

• Integration workshops will be conducted to define required functional and technical details to create a specification document.

• The output of the workshops will be the specification document signed-off by the customer prior to any development work and/or configuration beginning. Where the required business rules, transformations, data mapping rules, error handling and technical details are specified for the applicable integration stream.

Development, Test, and Deployment

• Planview will develop the integration according to the approved specification document and validate using a representative set of high-quality sample data provided by the customer or by leveraging the output from the integration. Moreover, Planview will o Perform unit testing o Address any incidents identified during unit testing and update relevant documentation if necessary o Package and generate Integration release for deployment.

• The Customer will ensure Planview has login access as appropriate, and all repository configurations are stable with the final configurations in place. Additionally, all sandbox/test environments are sufficiently representative of Production and aligned with the right data model

Support Customer UAT (Testing)

• In addition to providing support and guidance on how to use the interface, Planview will work with the Customers to ensure their functional and technical validation is completed and approved prior to production deployment.

• To facilitate success, the customer will provide the following:

• Provide representative test cases and prepare high quality sample data from

Customer’s existing software for unit testing and UAT

• Actively perform System Integration Testing (UAT) by using test plans, test cases, and scenarios.

• Coordinate with the integration team and potential third-party stakeholders, to resolve any issues that might arise.

• Ensure defects identified during testing are logged, tracked, and prioritized for resolution.

Deployment

• Planview will work with the customer to deploy the integrations to a sandbox environment where the customer can validate and confirm specification document requirements are met. Upon acceptance, the integrations will be deployed to Production.

Logistics The Consulting Services will be performed remotely during normal business hours, Monday through Friday, except Planview holidays.