PS Onboarding and Adoption Outcomes

• Customer must specify the authentication method they wish to use for logging into Harness and validate the login to the platform with the specified login method

• • SAML
  • LDAP
  • OAuth

• Base RBAC functionality for users is implemented and validated with the users and user groups mapped to Roles

• • SCIM
  • Just in time provisioning

• Customer must specify the organizational structure which needs to be mapped with the Account/Organization/Project structure of Harness

• Integrate with customer’s secret manager platform and validate the retrieval of these secrets in a sample pipeline
• AWS KMS and AWS secret manager
• GCP KMS and GCP secret manager
• Hashicorp vault secret manager
• Azure key vault secret manager
• Custom secret manager

• Integrate with customers SMTP configuration
• Customer has a delegate which can send email notifications

Initial Installation

• Connected mode
• Nginx
• Internal Database
• Self signed certificate

• Customer must specify the infrastructure where they wish to install the Harness Self Managed Platform
• Managed k8s some text
  • EKS (AWS)
  • GKE (GCP)
  • AKS (Azure) 
• Self managed k8s

• Customer must specify and provide the artifact repo they want to use with Air Gapped mode

• Customer must specify and bring their own Istio for the installation

• Customer must bring their own external databases for MongoDB, PostgresQL, Redis, TimescaleDB

• Customer must have Velero buckets for backup and restore
• Suggest disaster recovery strategy and support the architecture

• Up to 4 basic chaos experiments
  • For one k8s application
• Up to 4 basic chaos experiments
  • For one Linux/Windows application
• Up to 1 resilience probe integration

• Up to 8 basic chaos experiments
  • For one k8s application
• Up to 8 basic chaos experiments
  • For one Linux/Windows application
• Up to 8 resilience probe integrations

• Up to 16 basic chaos experiments
  • For one k8s application
• Up to 12 basic chaos experiments
  • For one Linux/Windows application
• Up to 12 resilience probe integrations

All Chaos Experiment dependencies have been integrated

Experiment development integrated with change management process

Custom Chaos Hub setup

Chaos Experiments integrated into CD pipelines

Basic Chaos Dashboards configured and ready

• Up to 12 chaos experiments
  • Across 1-2 Apps
• Up to 10 resilience probe templates
  • Across 1-2 Apps
• Up to 2 hours of Chaos Experiment Developer Training

• Up to 50 chaos experiments
  • Across 1-2 Apps
• Up to 30 resilience probe templates
  • Across 1-2 Apps
• Up to 6 hours of Chaos Experiment Developer Training
  • Including CD and APM integrations

• Up to 100 chaos experiments
  • Across 1-2 Apps
• Up to 50 resilience probe templates
  • Across 1-2 Apps
• Up to 8 hours of Chaos Experiment Developer Training
  • Including CD and APM and LT integrations

• Reporting - OOTB Perspectives/Dashboards
• Up to 10 Auto Stopping Rules
• Up to 10 Asset Governance Rules
• Commitment Orchestrator - Visibility

• Reporting - OOTB Perspectives/Dashboards
• Up to 20 Auto Stopping Rules
• Up to 20 Asset Governance Rules
• Commitment Orchestrator - Visibility

• Pre-sales to Post-sales Transition / POV involvement
• Project Kick off
• SCIM/SSO Implementation
• RBAC Implementation
• Create billing connector
• Cluster Costs (Delegate and 2 connectors) Implementation

• Custom Perspective Implementation
• Custom Dashboard Implementation
• Cost Categories Implementation
• Anomaly Overview
• Budget Implementation

• Recommendations Overview
• AutoStopping Setup
• AutoStopping Schedule Implementation
• AutoStopping Traffic Implementation
• Asset Governance Setup
• Asset Governance Rule Enforcement
• Commitment Orchestrator Setup
• Commitment Orchestrator Review Recommendations

• Up to 20 additional custom Dashboards setup

• Up to 10 Custom Perspective / Dashboard Templates
• Up to 40 Auto Stopping Rules with automation via TF/API to scale
• Up to 40 Asset Governance Rules with automation to scale

• Up to 20 unique Custom Perspective / Dashboard Templates
• Up to 75 Auto Stopping Rules with automation via TF/API to scale
• Up to 75 Asset Governance Rules with automation to scale

• Only applicable to Dashboard Migration Package:
  
  • Eligible for bulk purchases based on migration scope
  • Dashboard Migration scope analysis
  • Custom Dashboard Migration
    
    • Estimated level of effort is 4 hours per Dashboard

• Custom Perspective Implementation
• Custom Dashboard Implementation
• Cost Categories Implementation
• Anomaly Overview
• Budget Implementation

• Recommendations Overview
• AutoStopping Setup
• AutoStopping Schedule Implementation 
• AutoStopping Traffic Implementation 
• Asset Governance Setup
• Asset Governance Rule Enforcement 
• Commitment Orchestrator Setup
• Commitment Orchestrator Review Recommendations
• Automated purchasing and management of RIs and SPs through Commitment Orchestrator

• Anomaly Overview
• Guidance for 
  
  • Custom Perspective Implementation
  • Custom Dashboard Implementation
  • Cost Categories Implementation
  • Cost Budget Implementation

• Recommendations overview
• AutoStopping Setup
  
  • Guidance for schedule-based Autostopping Rules
  • Guidance for traffic-based Autostopping Rules
• Asset Governance 
  
  • Guidance for setup and rule enforcement 
• Commitment Orchestrator 
  
  • Guidance for setup and review of recommendations
• Guidance for automated purchasing and management of RIs and SPs through Commitment Orchestrator

• Customers must specify the services they wish to target for Onboarding and agree upon the scope of the services they wish to target for onboarding.

• Each Pipeline must deploy successfully to a respective target
• Working pipelines can deploy to any environment (non-prod or prod - does not need to be Prod)
• Service must be deployed to an environment

• Shell script configuration
• Service and environment onboarding

• Approval gate configuration
• ServiceNow and Jira integration
• Bi-Directional Git Sync / Git Experience to backup configurations and setup
• Deployment Step Configuration
• Cloud Providers
• Infrastructures are configured
• Services and Environments are configured

Users have delegates that can perform deployment tasks

• Delegate INIT SCRIPT are configured
• Delegate Upgrade process is defined
• Immutable and Custom Delegate Image - Process in place to maintain and update
• Network Connectivity to resources
• High Availability of Delegates
• Prod vs Non Prod Access for Delegates

Users will be able to govern their Deployments via Policies as Code.

• Level 1
  • Not Applicable
• Level 2
  • Max 6 Policies
• Level 3
  • Max 8 Policies

Users will have various templates configured in their account to prepare to scale adoption of Harness to other teams

• Level 1
  • Max 4 Templates
• Level 2
  • Max 12 Templates
• Level 3
  • Max 20 Templates

Integrated health data sources with Harness CV, including the development of the relevant data queries

• Level 1
  • 1 CV Step, 1 Monitored Service with 1 Query
• Level 2
  • 3 CV Steps, 3 Monitored Services with 3 Queries
• Level 3
  • 5 CV Steps, 5 Monitored Services with 5 Queries

Customer creates Pipelines to help onboard the services with Harness support

Adopt more advanced features like overrides, variable expression usage and manifest

Users are deploying their services to production with Harness

Customer has an onboarding automation tool to help users scale to the next set of services; the time required to add and configure new services decreases for the customer

Base RBAC for CD Teams is implemented

The Customer gets an Account Setup, Integration Setup, Pipeline Design that is reusable and can handle the new services and teams they onboard. This is to ensure the short onboarding time and the reduction in new configuration

• Set goals/ timelines needed for the migration
• Infrastructure, network access, connectors is setup to run CI builds

• Tutorials and Pre-Implementation Orientation

• Setup infrastructure for self-hosted scenarios
• Codebase connector to clone codebase in CI pipeline

• Get the first 1st pipeline running in Harness with all the optimization to make builds faster

• Migrate. Optimize pipeline#2 and identity patterns that can be generalized through templates

• Create policies and dashboards so the customer can roll out CI pipelines and measure the ROI

• Create templates based on common patterns identified so customer can rollout CI pipelines

• Do functional, performance, security testing to ensure that this effort meets the business goals
• No shadow mode for the pipeline migrated to Harness CI
• Developer Satisfaction
• Case study for the benefits realized

• Migration goals/ internal rollout plan (people, process, culture, direction)
• Infrastructure, network access, connectors is setup to run CI builds

• Tutorials and Orientation Pre-Implementation
• Migration

• Setup infrastructure for self-hosted scenarios
• Codebase connector to clone codebase in CI pipeline

• Get the first 1st pipeline running in Harness with all the optimization to make builds faster

• Migrate. Optimize pipeline#2 and identity patterns that can be generalized through templates

• Create policies and dashboards so the customer can roll out CI pipelines and measure the ROI

• Create templates based on common patterns identified so customer can rollout CI pipelines

• Onboard 20-30% of engineering teams/ developers
• Run Harness & existing CI system in Shadow mode

• Business Outcomes results realized based on the SKU and initial rollout scope
• Technical acceptance for functional, performance, security goals
• CSAT Completion
• Developer Satisfaction
• Case study for the benefits realized

• Migrate all pipelines (optimize or deprecate)
• Harness CI becomes the primary system
• Existing CI system deprecated/ any infrastructure used is deprecated

• Do functional, performance, security testing to ensure that this effort meets the business goals
• No shadow mode for the pipeline migrated to Harness CI
• Developer Satisfaction
• Case study for the benefits realized

• Onboarding of in-scope DB Schemas specified by the Customer
• Onboarding of Environments and DB Instance definitions

• Approval gate configuration
• ServiceNow and Jira integration
• Deployment Step Configuration

• User Groups, Users are all mapped to Roles to begin deployment

• Codebase connector to clone codebase in DB DevOps pipeline

Users will be able to govern their Deployments via Policies as Code.

• Level 1 
  
  • Not Applicable
• Level 2
  
  • Max 6 Policies
• Level 3
  
  • Max 8 Policies

Customer gets a review of their current DB DevOps Practices from PS

Customer gets the best practices to implement Harness DB DevOps from PS

• Level 1 
  
  • Not Applicable
• Level 2
  
  • Not Applicable
• Level 3
  • Not Applicable

Adopt more advanced features like overrides, variable expression usage and manifest

Users are deploying their services to production with Harness

Customer has an onboarding automation tool to help users scale to the next set of services; the time required to add and configure new services decreases for the customer

Build Custom Dashboards for use with DB DevOps Data

• Level 1 
  
  • Up to 2 Custom Dashboards
• Level 2
  
  • Up to 4 Custom Dashboards
• Level 3
  • Up to 6 Custom Dashboards

Base RBAC for DB DevOps Teams is implemented

The Customer gets an Account Setup, Integration Setup, Pipeline Design that is reusable and can handle the new schemas and teams they onboard. This is to ensure the short onboarding time and the reduction in new configuration

Codebase connector to clone codebase in DB DevOps pipeline

• Up to 5 feature flags
• Up to 1 experiment or alert
• Administration set-up
  
  • Projects, Environments, Permissions & Approvals
• Up to 2 hours of technical sessions
• Up to 4 hours of training and workshops

• Up to 5 feature flags

• Up to 4 experiments or alerts
• Administration set-up
  
  • Projects, Environments, Permissions & Approvals
• Up to 4 hours of technical sessions
• Up to 7 hours of training and workshops
• Up to 1 custom playbook

• SDK install & validation
  
  • Architecture & infrastructure recommendations
• Integrations with third-party tools
• Admin API and webhooks configurations
• Sending events - data flow recommendations & set-up

• Migration script review 
• Migration testing

• SSO/SCIM configuration
• Projects & Environments set-up
• Custom targeting option set-up of at least one of the following:
  
  • Traffic types
  • Segments
  • Attributes
• Custom configuration of permissions, restrictions & approval flows
• User group configuration
• Pilot team onboarding

• Create feature flags
• Test & validate targeting use cases
• Create metrics
• Set up experiments
• Set up alerts

Users will be able to govern their Deployments via Policies as Code.

• Feature Flag Foundations
• Feature Flag Best Practices
• Feature Flag Use Cases
• Measurement & Analysis
• Release Monitoring
• Experimentation Design
• Metrics Set-up

• Maturity Assessment
  
  • Review of the current experimentation program to assess maturity level for organisation and/or team(s)
• Gap Assessment
  
  • Identify gaps in process, tools, skills and culture
• Action Plan 
  
  • Prioritised action plan for improving experimentation effectiveness

• Experiment Design Brief 
  
  • Complete an experiment design brief, with detail on the experiment treatments, metrics, targeting and experiment details etc 
• Create Metrics
  
  • Metrics training and foundations 
  • Build key, supporting and guardrail metrics 
  • Build any relevant alerts 
• Set Up A Feature Flag 
  
  • Configure an experiment feature flag 
• Set up experiment dashboard 
  
  • Configure an experiment dashboard 
  • Add metrics 
  • Review experiment settings 
• QA & Launch 
  
  • QA best practices 
  • Launch process and steps 
• Experiment Analysis 
  
  • How to interpret the results 
  • Best practices

• Assessment 
  
  • Assess current state vs desired state of maturity, and identify gaps and opportunities 
• Establish Goals 
  
  • Establish goals for scaling based on four categories, leadership & culture, program management, process & planning, knowledge & training 
• Recommendations & Plan 
  
  • High level actions for next 9 months

• Review
  
  • SDK Implementation, including Synchronizer, Split Proxy, Redis, Split Evaluator, and traffic type ID usage for Client-side SDKs 
• Recommendations Document 
  
  • Architectural recommendation document diagram with the description of the recommended approach

• Review
  
  • This engagement provides a review of the requirements,  opportunities and options for automating flag changes, approvals and configuration 
• Recommendations Document 
  
  • Architectural recommendation document diagram with the description of the recommended approach

• Review
  
  • This engagement provides a review of the requirements,  opportunities and options for integration of impressions and events to ensure that the systems that need them can get them for experimentation and data analysis
• Recommendations Document 
  
  • Architectural recommendation document diagram with the description of the recommended approach

• Review
  
  • This engagement provides a review of the requirements,  opportunities and options for project and environment setup for multiple engineering and product teams  
• Recommendations Document 
  
  • Architectural recommendation document diagram with the description of the recommended approach

• Review 
  
  • This engagement provides a review of the requirements, options, and opportunities for migrating your feature flags from an external system to Harness FME
• Recommendations Document 
  
  • Architectural recommendation document diagram with the description of the recommended approach

• Discovery 
  
  • Session to understand the request for support 
• Prep Work 
  
  • Prepare what is needed to support 
• Guidance, Training and Recommendations
  
  • Deliver and discuss recommendations, resources and/or training for support request

• Up to 10 Workspaces
  • Across 1-2 Projects
• Up to 1 OPA Policy
• Up to 2 Basic Pipelines
• Cost Estimation Setup

• Up to 50 Workspaces
  • Across 3-5 Projects
• Up to 2 OPA Policies
• Up to 5 Basic Pipelines
• Cost Estimation Setup

• Up to 100 Workspaces
  • Across 8-10 Projects
• Up to 3 OPA Policies
• Up to 10 Basic Pipelines
• Cost Estimation Setup

All infrastructure dependencies have been integrated into the provisioning pipeline(s)

Consolidated state and configuration management within Harness

Provision Infrastructure via Harness Pipelines

Pipelines integrated with Change Management processes

Establish delegate architecture and build for scale

• Up to 40 Workspaces
  • Across 10 Projects
• Up to 5 OPA Policy
• Up to 10 Advanced Pipelines

• Up to 80 Workspaces
  • Across 20 Projects
• Up to 10 OPA Policies
• Up to 20 Advanced Pipelines

• Up to 150 Workspaces
  • Across 30 Projects
• Up to 15 OPA Policies
• Up to 30 Advanced Pipelines

Establish a cultural center of excellence for organization-wide Infrastructure-as-Code practices and reusable solutions

Advanced infrastructure provisioning pipelines, including plugin integrations

Drift Detection Schedule enabled and set

Pipelines integrated with Change Management processes

• Up to 3 OOTB Catalog Plugins
• Onboarding for up to 35 Catalog Components
• Up to 2 Self-Service Workflows
• Up to 6 Catalog Readiness Scorecard Checks
• Up to 2 Custom Data Ingestions with corresponding Maturity Scorecard Checks

• Up to 5 OOTB Catalog Plugins
• Up to 75 components onboarded into Software Catalog
• Up to 5 Self-Service Workflows
• Up to 12 Catalog Readiness Scorecard Checks
• Up to 5 Custom Data Ingestion Integration with corresponding Maturity Scorecard Checks

• Platform Fundamentals
  • RBAC Persona Configuration
  • SSO Integration
  • Secret Management Integration
  • Setup of Initial Account Structure
• Integrate developer systems with Harness Platform
• Create Systems and Domains to represent hierarchy

• Integrate and configuration Catalog Plugins
• Define dependencies and relationships between components
• Onboard software components into Software Catalogs
• Create Scorecard for Catalog Readiness
• Complete training for Administrators & End Users

• Create self-service Workflows to support development organization
• Integrate with CI / CD platforms to automate the scale of pipelines
• Integrate with IaC frameworks to automate the scale of environments and application dependencies
• Integrate with Change Management / Issue Tracking software to automate any governance and compliance requirements

• Up to: 3 OSS or 1 OSS security scanners and 1 commercial security scanners have been integrated into an automation pipeline, including a basic scan governance policy
• For up to 15% of licensed users

• Up to: 5 OSS or 1 OSS security scanners and 3 commercial security scanners have been integrated into an automation pipeline, including a basic scan governance policy
• For up to 15% of licensed users

• Up to: 7 OSS or 1 OSS security scanners and 5 commercial security scanners have been integrated into an automation pipeline, including a basic scan governance policy
• For up to 15% of licensed users

• Prepare Security Scan Hosting Platform
• Prepare any Self-signed Certificate Dependencies
• Deploy Delegate to manage Security Scans
• Create Scanning Infrastructure Connector

• Create STO Pipeline Template
• Configure Pipeline Variables
• Configure Pipeline Notifications
• Configure Flow Control (if applicable)
• Configure Policy Sets (if applicable)
• Configure Advanced Pipeline Options (if applicable)
• Configure Harness Approval Stage Template (if applicable)
• Create STO Stage Template
• Create Code Repository Connector (if applicable)
• Create Artifact Repository Connector
• Configure Codebase
• Configure Infrastructure Tab
• Configure Stage Variables
• Configure Execution Tab
• Configure Security Tests Step
• Run initial tests and configure baselines
• Target name and variant acceptance review
• Setup automation for vulnerability baselines

• Configure Dashboard

• Configure Governance Policy

• Enable AIDA Recommendations
• Develop vulnerability exemption management workflow

• Jira Integration
• Slack Integration

• STO integrated with developer Pull Request pipelines resulting in vulnerabilities being fixed by devs prior to main merge using up to an additional 3 OSS or 1 OSS/1 Commercial scanners
• For up to 75% of contracted users

• STO integrated with developer Pull Request pipelines resulting in vulnerabilities being fixed by devs prior to main merge using up to an additional 5 OSS or 1 OSS/3 Commercial scanners
• For up to 75% of contracted users

• STO integrated with developer Pull Request pipelines resulting in vulnerabilities being fixed by devs prior to main merge using up to an additional 7 OSS or 1 OSS/5 Commercial scanners
• For up to 75% of contracted users

• Prepare Security Scan Hosting Platform

• Prepare any Self-signed Certificate Dependencies
• Deploy Delegate to manage Security Scans
• Create Scanning Infrastructure Connector

• Create STO Pipeline Template
• Configure Pipeline Variables
• Configure Pipeline Notifications
• Configure Flow Control (if applicable)
• Configure Policy Sets (if applicable)
• Configure Advanced Pipeline Options (if applicable)
• Configure Harness Approval Stage Template (if applicable)
• Create STO Stage Template
• Create Code Repository Connector (if applicable)
• Create Artifact Repository Connector
• Configure Codebase
• Configure Infrastructure Tab
• Configure Stage Variables
• Configure Execution Tab
• Configure Security Tests Step
• Run initial tests and configure baselines
• Target name and variant acceptance review
• Setup automation for vulnerability baselines

• Configure Governance Policy
• Enable AIDA Recommendations
• Develop vulnerability exemption management workflow

• Jira Integration
• Slack Integration

Initial onboarding for up to 2 teams

• OOTB Integrations: Jira, Azure Boards, GitHub, GitLab, Bitbucket, Jenkins, Harness, Azure Pipelines, GitHub Actions
• SSO & SCIM setup (Okta, Entra ID, OneLogin)
• Setup Collections for up to 2 teams
• Setup and visualize Efficiency, Productivity, and Alignment reporting
• RBAC setup and group walkthrough
• Walkthrough on navigation and administration

Expanded onboarding for up to 10 teams

• OOTB Integrations: Jira, Azure Boards, GitHub, GitLab, Bitbucket, Jenkins, Harness, Azure Pipelines, GitHub Actions
• SSO & SCIM setup (Okta, Entra ID, OneLogin)
• Setup Collections for up to 10 teams
• Setup and visualize Efficiency, Productivity, and Alignment reporting
• RBAC setup and group walkthrough
• Walkthrough on navigation and administration

Initial onboarding for up to 2 teams

• OOTB Integrations: Jira, Azure Boards, GitHub, GitLab, Bitbucket, Jenkins, Harness, Azure Pipelines, GitHub Actions
• SSO & SCIM setup (Okta, Entra ID, OneLogin)
• Setup Collections for up to 20 teams
• Setup and visualize Efficiency, Productivity, and Alignment reporting
• RBAC setup and group walkthrough
• Walkthrough on navigation and administration

• Integration Setup
  • Out of the Box Integrations
• Satellite Install
  • Configure the satellite
  • Run the satellite container
  • Managing the satellite
• Collaborator Setup
• SSO & RBAC Setup

• Hierarchy setup
  • Asset and People based
  • Centralized Profiles setup

Instructor led admin training on:

• Integration setup
• Keeping collaborator identities up-to-date
• Creating and modifying collections
• Creating new Profiles and Workspaces
• Modifying Thresholds
• Customization of Dashboards
• Widget Walkthrough

• Up to 100 SBOM's for built artifacts or repositories including different versions across pipelines with 3 OPA policy for enforcement

• Up to 250 SBOM's for built artifacts or repositories including different versions across pipelines with 5 OPA policies for enforcement

• Up to 500 SBOM's for built artifacts or repositories including different versions across pipelines with 10 OPA policies for enforcement

• Pipeline Creation with git connectors
• Setting up codebase and building artifact in CI
• Setup Deployment Stage and Configuration

• Include SBOM Orchestration Step in Build Stage
• Configure Attestation with Public & Private Key
• Download SBOM and Verify Attestation in Artifact Registry

• Create SBOM OPA policies to block components 
• Enforce governance in Deploy stage using SBOM Enforcement Step

• View components used in building artifacts
• Understand licenses used along with supplier details

• Up to 100 SBOM's for built artifacts or repositories including different versions across pipelines with 3 OPA policy for enforcement with SLSA Level 2 provenance validation for built artifacts to ensure integrity and trust on Harness Hosted Builds

• Up to 250 SBOM's for built artifacts or repositories including different versions across pipelines with 5 OPA policies for enforcement with SLSA Level 2 provenance validation for built artifacts to ensure integrity and trust on Harness Hosted Builds

• Up to 500 SBOM's for built artifacts or repositories including different versions across pipelines with 10 OPA policies for enforcement with SLSA Level 2 provenance validation for built artifacts to ensure integrity and trust on Harness Hosted Builds

• Pipeline Creation with git connectors
• Setting up codebase and building artifact in build stage
• Setup deployment stage and configuration

• Include SBOM Orchestration Step in Build Stage
• Configure Attestation with Public & Private Key
• Download SBOM and Verify Attestation in Artifact Registry

• Create SBOM OPA policies to block components
• Enforce governance in Deploy stage using SBOM Enforcement Step 

• View components used in building artifacts
• View licenses used along with supplier details

• Enforce SLSA Verification Step in Deployment
• Setup OPA policies needed to ensure artifact integrity
• Validate provenance by checking build system attributes such as users, branch etc

• Create remediation trackers to block components containing zero day vulnerabilities
• Assign tickets to developers and track remediation status in deployed environments