Operate
Review scanner health, maintain supported configuration, triage incidents and keep the accepted estate usable. Operational work stays visible in its own backlog.
PDI GovernForward . Managed governance for Informatica CDGC
PDI GovernForward keeps your accepted CDGC foundation useful with 8×5 shared-team support and a tested monthly release. $20,000 per year in services fees.
For an existing, licensed and accepted MVP or equivalent. Proposed service offering; subject to qualification and an agreed service schedule.
Your catalog foundation
The next useful release. Then the next.
A complementary managed service after the professional-services project – not a change to your Informatica software support.
The 66-PSU MVP and 20-PSU implementation item are published scope references. Review Informatica MVP scope (opens in a new tab) · Review the monthly build benchmark (opens in a new tab). The allowance is one prioritized release within aggregate scope limits, not all category maxima at once or a balance of vendor credits. See the build-and-test boundaries →
Keep the foundation useful
A scanner changes. A steward moves roles. A definition waits for a decision. The catalog can stay available while its usefulness starts to drift.
An MVP establishes the foundation. GovernForward gives the accepted environment a continuing service lead, a clear change process and a regular path from business request to tested improvement.
Governance should accumulate accepted outcomes – not an unowned backlog.
Review scanner health, maintain supported configuration, triage incidents and keep the accepted estate usable. Operational work stays visible in its own backlog.
Turn ready priorities into an agreed monthly release. Design, configuration, positive and negative tests, bounded regression and acceptance evidence belong together.
Keep owners, stewards, definitions, decisions and documentation current. Review the operating model and year-one roadmap as the agreed estate grows.
A monthly rhythm, not a credit balance
Twelve planning and delivery cycles in the service year. The release brief defines what this month will deliver; readiness and acceptance determine what is complete.
Choose the ready outcome, named owner, dependencies and acceptance criteria.
Configure the selected assets within the agreed monthly scope and change controls.
Validate behavior, permissions and affected assets. Record defects and retest.
Secure customer approval. Update the runbook, inventory and steward guidance.
Every accepted release leaves evidence: scope record · test record · ownership record · release record
What “done” includes
The technical whitepaper
A closer look at the nine disciplines, the monthly implementation benchmark, testing obligations and the boundaries of the proposed annual service.
14 pages · PDF · September 2026
New build and testing are included each service month. The allowance is benchmarked to the scope of Informatica’s 20-PSU CDGC Execution & Implementation item. A jointly prioritized release brief names the actual deliverables; routine incidents do not silently consume that commitment.
Review the implementation benchmark (opens in a new tab). See aggregate monthly limits.
Yes. Additions accepted within the pre-agreed year-one growth envelope join the managed inventory without a second support fee. Inventory and scan-workload limits are set before subscription and reviewed before new work is committed.
No. It is an independent, complementary PDI service for ongoing operation and improvement of your accepted CDGC estate. Your customer-owned software support entitlement remains the route for product defects and vendor-operated SaaS restoration.
Start with the catalog, the owners and the backlog you already have.