PDI GovernForward / Coverage
Full discipline coverage.
Explicit delivery boundaries.
One managed service carries all nine CDGC catalog disciplines forward. The cadence changes after the MVP; the responsibility continues.
01Kickoff & Engagement PlanningOnboarding + change
Establish the managed inventory, roles, escalation routes, delivery calendar and release-approval process. Refresh when responsibilities or boundaries change.
Service charter and inventory.
02Business Discovery & Use Case DefinitionMonthly planning
Maintain a prioritized backlog tied to the agreed use case. Turn ready requests into a monthly release brief with an owner and acceptance criteria.
Prioritized backlog and approved release brief.
03CDGC Operating Model Design & Execution PlanningMonthly + quarterly
Maintain ownership, stewardship, metadata templates and practical decision rules. Review with stewards monthly and revisit the model quarterly.
Ownership matrix, issue log and updated procedures.
04CDGC Technical Requirements Definition & ValidationEvery release
Check access, source compatibility, dependencies and technical readiness before work is committed to a release.
Readiness checklist and documented dependencies.
05CDGC Configuration & SetupBusiness days + planned maintenance
Administer the accepted environment and supported configuration: Secure Agent checks, approved access changes and scanner scheduling.
Configuration record and operating runbook.
06CDGC Solution DesignEvery monthly release
Design the approved increment: relationships, taxonomy, persona experience, classification behavior, workflow and dashboard changes.
Concise design and acceptance mapping.
07CDGC Execution & ImplementationMonthly
Deliver the prioritized new-build-and-test allowance benchmarked to the published 20-PSU implementation scope, with controlled configuration and validation.
Configured assets, test results and accepted release record.
08CDGC Knowledge Transfer & End User DocumentationEach release
Demonstrate the accepted change, update runbooks and user guidance, and equip designated owners and stewards. Up to two one-hour handover sessions per release when needed.
Updated documentation and recorded decisions.
09CDGC First Year Roll-out PlanQuarterly refresh
Maintain a rolling view of priorities, adoption needs, dependencies and approved asset growth. Distinguish funded monthly work from larger expansion.
Roadmap and the next quarter’s delivery priorities.
Catalog names follow the published Informatica scope. Cadences and managed-service responsibilities above describe the proposed PDI offering. Review Informatica professional-services offerings (opens in a new tab).
02 / The monthly release
20-PSU-equivalent.
Defined by scope.
One jointly prioritized monthly new-build-and-test release, benchmarked to Informatica’s 20-PSU CDGC Execution & Implementation item. Review Informatica scope (opens in a new tab).
The release mix is agreed before work starts. These are aggregate monthly ceilings – not per-ticket allowances or a promise to deliver every category maximum concurrently.
No purchase, transfer or redemption of Informatica PSUs. No fixed labor-hour entitlement. No monetary-value or ROI conversion.
| Connectivity & lineage | Up to 3 out-of-the-box scanner connections. Resource and lineage scanners share that limit. One source-to-target lineage-code demonstration, such as one mapping or report. |
|---|---|
| Classification | 8 standard + 2 custom data-element classifications and 1 data-entity classification. |
| Governance content | 20 glossary terms, 2 policies and 2 processes. The bounded metadata load covers up to two domains/subdomains within the same existing two-domain service boundary – not two new domains each month. |
| Technical metadata seed | 2 system records; 5 datasets per system; 10 attributes per dataset; 1 custom attribute. These are bulk-load limits, not a 100-attribute ceiling on the harvested catalog. |
| Workflow & dashboards | 1 change-request workflow; 2 dashboards, each with up to 5 widget types allowed by the catalog item. The selected widget types are named in the release brief. |
All quantitative implementation ceilings: CDGC Execution & Implementation (opens in a new tab). Scanner-counting rule: CDGC Technical Requirements Definition & Validation (opens in a new tab).
One agreed use case, one environment and up to two existing domains/subdomains. Source access, substantially ready content, timely decisions and acceptance are customer prerequisites.
03 / The definition of done
Testing is included.
Not an add-on.
The configured object is only part of the outcome. Each selected build includes validation, evidence and acceptance support – with no separate testing charge or additional PSU requirement.
- Configuration checks
Validate the selected scanner results, metadata relationships and classification behavior.
- Positive & negative tests
Check workflow routing, dashboard behavior, permissions and failure paths where relevant.
- Bounded regression
Recheck affected existing assets. Record failures, corrections and retest results.
- Acceptance & handover
Secure named customer approval. Update release records, inventory and user guidance.
Routine operations and incidents do not silently consume enhancement capacity. Provider-caused defects and retesting do not use a second new-build allowance. PDI-caused delays are made good under the agreed schedule; the obligation does not disappear at month-end.
04 / The run service
Business-hours coverage.
Human response. Clear ownership.
8×5 means 09:00–17:00 Eastern.
Monday–Friday, America/New_York, excluding the agreed holiday calendar. A shared team provides intake, triage and coordination, with a named service lead and backup route.
Not 40 dedicated consultant hours, continuous human monitoring or 24×7 incident response.
| Priority | Proposed initial human response |
|---|---|
| P1 · Critical | 4 business hours |
| P2 · Material | 1 business day |
| P3 · Routine | 2 business days |
Proposed targets are subject to confirmed staffing and the service order. Response means acknowledgement, initial impact assessment and next action – not guaranteed restoration or resolution. Out-of-window requests enter the next coverage period.
How are priorities defined?
P1: The accepted service is unavailable to the in-scope user group, with no workaround. P2: A supported capability is materially impaired, with a workaround or limited impact. P3: A noncritical issue, access request, content amendment or enhancement request.
PDI owns the operating rhythm.
- Business-day scan-outcome and scanner-health review.
- Supported configuration and approved access administration.
- Incident triage and vendor-case coordination.
- Routine metadata housekeeping and stewardship issue routing.
- Separate operational and enhancement backlogs, plus a monthly service review.
The customer keeps decision authority.
Business ownership, source-system administration, access approval, infrastructure ownership and acceptance remain with the customer. Product defects and vendor-operated SaaS restoration follow the customer’s Informatica support entitlement.
A critical incident may reschedule a build window by agreement. It does not silently cancel that month’s build commitment.
05 / Price & boundaries
One annual services fee.
No ambiguity about the starting point.
USD · annual services fee.
Not a monthly price or software bundle.
- Qualified 8×5 shared-team run service
- Monthly 20-PSU-equivalent new build and testing
- All nine catalog disciplines carried forward
- Release documentation and quarterly roadmap reviews
Eligibility comes before commitment.
Start from an existing, licensed and accepted CDGC MVP or equivalent. Onboarding validates that baseline; it does not include a fresh 66-PSU initial implementation.
Informatica’s reference setup describes one environment and Secure Agent installation, with bounded initial configuration. Review configuration and setup scope (opens in a new tab). Production readiness is qualified – not inferred from MVP acceptance.
What footprint does the annual fee cover?
One agreed use case, one environment and up to two existing domains/subdomains. The service order records the supported users, source types, inventory, harvested-asset scale, scan workload and year-one growth envelope before commencement.
Do accepted monthly additions cost extra to support?
Not within the pre-agreed year-one growth envelope. Accepted additions join managed operations without a second support fee. The starting inventory, growth limits and scan-workload thresholds are agreed before subscription. Out-of-bound expansion requires separately approved scope; there is no automatic price change or surprise invoice.
What is outside the default service?
Software licenses, infrastructure, third-party costs, formal vendor training, travel and applicable taxes are separate. So are additional environments, use cases or domains; custom or unsupported scanners; major architecture changes or production hardening; HA/DR engineering; CDQ rule development and data remediation; MDM; Marketplace; and enterprise-wide governance redesign.
After-hours coverage, 24×7 monitoring, security incident response and guaranteed third-party restoration are not included.
Does onboarding replace the first monthly release?
No. Onboarding is included for the qualified existing baseline and scheduled alongside the first month’s release – not automatically substituted for that month’s build-and-test allowance. Required remediation or initial implementation is named before signing.
What if a release is blocked or delayed?
Customer-blocked work is replanned under the service schedule; unused allowance is not an unlimited bank that accumulates indefinitely. PDI-caused delivery delays remain obligations to make good. Correction and retesting of PDI defects are included, not relabeled as next month’s new build.
Is this an Informatica subscription or endorsed extension?
No. GovernForward is an independent, complementary PDI managed service. “PSU-equivalent” is a scope benchmark – not official Informatica credits, a fixed number of labor hours or a claim of Informatica endorsement. Informatica licenses and software support remain separate.
Bring the scope into focus.
Review the baseline, agree the growth envelope and choose a first ready release.