The Gate Keeper
The quality gate at the end of every SAP Activate phase, checked in code, packed with the evidence, and put to the named signer only when every check passes.
The machine holdsPrepares the quality gate pack at the end of an SAP Activate phase: reads the gate result Pam's fixed rules computed from the deliverables, the RAID log, the tests and the loads, lists each check that holds with its evidence and the owner who can clear it, and proposes the gate as ready to the named signer only when the gate result says every check passes. It never passes a gate.
A named human signsThe steering committee signs the gate; the agent packs the evidence and proposes.
The receiptthe phase and the products in scope; every check, its result and its evidence line; the signer named on the rules card and the decision they recorded. Any override: who, when and why.
The leverNo gate goes to the steering committee on a slide: every check is computed, and every hold names its owner
Runs on: the programme's deliverables register, RAID log and test and load registers, read only, with Pam's fixed rules (pam-rules.v1); SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Phase gateGo no go
The RAID Keeper
Every risk, assumption, issue and dependency owned, dated and moving: the gaps found by rule, the chasers drafted, the escalations proposed.
The machine holdsKeeps the RAID log honest: reads the RAID rows and the findings Pam's fixed rules computed (no owner, no due date, overdue past the grace the card allows, a high risk with no mitigation, an issue older than the card allows), drafts the chaser to each owner, proposes an owner where there is none, and proposes for the steering committee the items the card says must go there.
A named human signsThe programme manager assigns owners and closes items; the steering committee takes the escalations.
The receiptthe RAID rows read and their findings; the chasers drafted and to whom; the owner the programme manager assigned, or none. Any override: who, when and why.
The leverA RAID log nobody has to clean before the steering committee: every item owned, dated and in date
Runs on: the RAID log export, read only, with Pam's fixed rules (pam-rules.v1 raid); SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Daily
Path Watch
The critical path across S/4HANA, Ariba and SuccessFactors: every milestone that starts before its predecessor lands, and every slip past the baseline the card allows.
The machine holdsWatches the integrated plan across the three products: reads the milestones and the findings Pam's fixed rules computed (a sequence breach, a cross-product dependency such as the Employee Central foundation objects before the finance design of company codes and cost centres, a predecessor not in the plan, a critical milestone slipping past its baseline by more than the card allows), and proposes for each the replan conversation between the two workstream leads.
A named human signsThe workstream leads agree a replan; the steering committee moves a baseline.
The receiptthe milestones read and the breaches found; the replan proposed and the two leads named; the decision the programme manager recorded. Any override: who, when and why.
The leverThe cross-product dependencies that sink SAP programmes, found the day they slip, not at the gate
Runs on: the integrated plan export (milestones with baselines, forecasts and predecessors), read only, with Pam's fixed rules (pam-rules.v1 dependencies); SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Weekly
The Status Writer
The weekly status in one page: the RAG from the rules, the milestones, the top risks, the decisions due, every figure from the registers.
The machine holdsDrafts the weekly programme status for the programme manager to sign: the RAG per product exactly as Pam's fixed rules set it, with the rule that set it; the milestones this week and next; the top risks and issues; the decisions due; and the budget lines as given. Every figure is copied from the input; a figure that does not reconcile is flagged, never fixed.
A named human signsThe programme manager signs the status; the steering committee reads it.
The receiptthe week and the RAG per product with its rule; every figure quoted and its source register; the programme manager's signature or edits. Any override: who, when and why.
The leverA status report that takes minutes to sign, not a morning to assemble, and a RAG nobody can argue with
Runs on: the RAG and findings from pam-rules.v1, the plan, the RAID log, the decision log and the budget lines, read only; SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Weekly
The Change Desk
Every change request set out on scope, time, cost and the other two products, complete before the change board sees it.
The machine holdsPrepares each change request for the change board: checks it carries a reason, an owner, the products touched, the effort and the cost from the requester; sets out the impact on scope, the dates and the other products from the plan and the registers as given; asks for what is missing; and routes it to the board the rules card names. It never accepts or rejects a change.
A named human signsThe change control board accepts or rejects a change; the programme manager rebaselines after it.
The receiptthe request id and what it carried; the impacts set out and their sources; the board's decision and who recorded it. Any override: who, when and why.
The leverNo change reaches the board half-written, and no change slips in without one
Runs on: the change request register and the integrated plan, read only; SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Phase gate
The Decision Log
Every open design decision with its owner, its date and the build it blocks, on the design authority's agenda before it blocks anything.
The machine holdsKeeps the design decisions moving: reads the decision log and the deliverables each decision blocks, finds the decisions past their needed-by date or blocking a build, drafts the chaser to the owner, and proposes the next design authority agenda in the order of what each decision blocks. It never makes a decision.
A named human signsThe design authority decides and records the decision.
The receiptthe decisions read and the builds they block; the agenda proposed; the decision the design authority recorded and who recorded it. Any override: who, when and why.
The leverNo build waits on a decision nobody knew was due
Runs on: the decision log and the deliverables register, read only; SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Daily
Fit to Standard
Every gap from the fit-to-standard workshops classed against the clean core: adopt the standard, extend side by side, or change the process, for the design authority to decide.
The machine holdsWorks through the gap backlog from the fit-to-standard workshops: for each requirement it proposes one class from the programme's clean core rule (adopt the standard process, a side-by-side extension on SAP BTP, a process change for the business owner, or out of scope), with the words from the workshop note that support it, and flags any request that would modify the SAP core. It never approves a modification.
A named human signsThe design authority decides every gap; the business owner accepts a process change.
The receiptthe gaps read and the class proposed for each; the core modifications flagged; the design authority's decision and who recorded it. Any override: who, when and why.
The leverA clean core by default: every gap classed before anyone writes code
Runs on: the fit-to-standard gap backlog and the clean core rule on the rules card, read only; SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Phase gate
Test Exit
Each test cycle against the exit criteria the programme signed: every open defect that holds the exit, with its owner, and the exit proposed only when the rules say it may.
The machine holdsPrepares the exit of a test cycle (unit, SIT, UAT, regression) for the test manager: reads the cycle's result Pam's fixed rules computed against the exit criteria on the rules card, lists each open defect that holds the exit with its severity and owner, proposes a retest where a fix is ready, and proposes the exit only when the result allows it.
A named human signsThe test manager signs the exit; the business process owners sign user acceptance.
The receiptthe cycle, the open defects by severity and the criteria; the defects held and their owners; the test manager's decision. Any override: who, when and why.
The leverNo cycle exits on optimism: the defects that hold it are named, owned and dated
Runs on: the defect log and the test plan, read only, with Pam's fixed rules (pam-rules.v1 testExit); SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Daily
Load Check
Every mock data load reconciled object by object: what loaded, what was rejected, and what the data owner must cleanse before the next one.
The machine holdsReads the result of a mock data migration load object by object (business partners, materials, open purchase orders, contracts, employees): the source count, the loaded count, the rejected count and the reconciliation the migration lead recorded, against the number of mock loads and the reconciliation the rules card asks; flags each object short of it and proposes the cleansing action for its data owner.
A named human signsThe data migration lead signs a load; each data owner signs their object.
The receiptthe load, the objects and their counts; the objects flagged and the owners named; the data migration lead's sign-off. Any override: who, when and why.
The leverNo cutover on data nobody reconciled
Runs on: the mock load register (the Migration Cockpit results as exported), read only; SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Phase gate
Cutover Ready
The go/no-go pack from the rules: every criterion, every rehearsal, every unowned task, for the steering committee to decide.
The machine holdsPrepares the go/no-go pack for the steering committee: reads the deploy gate result Pam's fixed rules computed (tests exited, mock loads reconciled, supplier enablement, payroll parallel runs, rehearsals passed, every cutover task owned) and the cutover runbook, lists each criterion with its evidence, chases the owner of any task without one, and proposes the pack. It never calls a go-live.
A named human signsThe steering committee decides go or no-go; the cutover manager runs the cutover.
The receiptthe criteria, their results and their evidence; the unowned tasks chased; the steering committee's go or no-go and who recorded it. Any override: who, when and why.
The leverA go/no-go decided on evidence the room can read in five minutes
Runs on: the cutover runbook, the rehearsal log and the deploy gate result from pam-rules.v1, read only; SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Go no go
Network Enablement
Suppliers on the SAP Business Network in waves by spend, so invoicing goes live with the suppliers that matter already on it.
The machine holdsPlans and tracks SAP Ariba supplier enablement: reads the supplier list with each supplier's annual spend, wave and status, measures the share of spend enabled against the share the rules card asks before invoicing goes live, proposes the next wave in order of spend, and drafts the chaser the enablement lead sends to a supplier who has not responded. It never invites a supplier itself.
A named human signsThe supplier enablement lead invites and enables suppliers; the head of procurement signs the waves.
The receiptthe suppliers read, the share of spend enabled and the target; the wave proposed; the enablement lead's decision. Any override: who, when and why.
The leverInvoicing live with most of the spend already on the network, not a quarter later
Runs on: the supplier enablement tracker (Ariba Supplier Enablement as exported), read only; SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Weekly
Parallel Run
Each payroll parallel run explained employee by employee and component by component, inside the tolerance the payroll lead signed, before payroll goes live.
The machine holdsReads a SuccessFactors Employee Central Payroll parallel run against the legacy payroll: the employees, the net pay totals and the variances by component, against the tolerance on the rules card; sets out each variance outside it with the components that make it, proposes a rerun where a fix is in, and proposes the run to the payroll lead as clean only when every variance is inside the tolerance. It never adjusts pay or submits anything to HMRC.
A named human signsThe payroll lead signs each parallel run; the HR director signs payroll go-live.
The receiptthe run, the totals and the variances outside the tolerance; the rerun proposed; the payroll lead's sign-off. Any override: who, when and why.
The leverPayroll goes live on parallel runs the payroll lead can sign, not on hope
Runs on: the parallel run comparison report (legacy against Employee Central Payroll), pseudonymised employee references only, read only; SAP Cloud ALM, Jira, Smartsheet or Microsoft Project as the record (read only)
Also on: Dynamics 365 (Dynamics 365 Project Operations: projects, tasks and risks) · NetSuite (NetSuite SuiteProjects: projects, tasks and milestones) · Oracle Fusion (Oracle Fusion Project Management: project plans, issues and deliverables) · Workday (Workday Projects: project plans, milestones and risks)
Try it with Pam, on your own key →
Phase gate