Enterprise operations

Enterprise Projects & Portfolio Delivery

Connect proposed initiatives, investment decisions, dependencies, milestones, controlled changes, deliverable acceptance and benefit review.

12 workspace menus · 5 role profiles · Connected records

Designed for portfolio management offices and project sponsors

Enterprise Projects & Portfolio Delivery workspace interface preview; illustrative records and figures.
Enterprise Projects & Portfolio Delivery — operational workspaceInterface preview · Illustrative dataView full interface →

Explore the system interface.

Operational workspace and record review. Select a screen to inspect it in full.

Operational dashboards and work queues.

Operational views

Review work, evidence, exceptions and authorised decisions within a defined operating scope.

Business unitPeriodAssigned teamReview state

Dashboard measures

  • Active service movements
    Count of all records in the selected workspace.
  • Review queue
    Records at the third stage of the business workflow.
  • Needs attention
    Records with an assigned review requirement.
  • Final-stage records
    Records in the fourth business workflow stage.

Business workflow and operating scope

Connect proposed initiatives, investment decisions, dependencies, milestones, controlled changes, deliverable acceptance and benefit review. A portfolio dashboard can show progress while hiding the approvals and dependencies that determine whether an outcome is deliverable. The system links the investment decision to delivery responsibilities, change control and acceptance, making unresolved issues visible alongside the promised benefits.

Operational visibility

  • Accepted project milestone completion rate
  • Portfolio status dashboard
  • Milestone and gate ageing
  • Budget / funding status
  • Risk, issue and benefit report

Operations

Operational overview

Review the work position and priority actions.

Initiative intake

Coordinate initiative intake with assigned responsibilities, linked records and review history.

Investment approval

Coordinate investment approval with assigned responsibilities, linked records and review history.

Dependency planning

Coordinate dependency planning with assigned responsibilities, linked records and review history.

Milestones and deliverables

Coordinate milestones and deliverables with assigned responsibilities, linked records and review history.

Issues and risks

Coordinate issues and risks with assigned responsibilities, linked records and review history.

Controlled scope changes

Coordinate controlled scope changes with assigned responsibilities, linked records and review history.

Acceptance and benefits review

Coordinate acceptance and benefits review with assigned responsibilities, linked records and review history.

Insights

Reports and saved views

Review the reporting scope and export agreed operational views.

Governance

Approvals and exceptions

Review delegated decisions, exceptions and recorded conditions.

Audit history

Trace accepted changes, decisions and accountable actions.

Access and configuration

Manage the agreed role permissions and configurable operating rules.

The end-to-end business journey.

From intake to authorised completion, with evidence at each decision.

01

Register the initiative

Register proposed initiatives with outcomes and ownership.

02

Approve delivery commitments

Approve funding, dependencies and delivery plans.

03

Manage work and changes

Manage milestones, issues and controlled changes.

04

Accept and review benefits

Accept deliverables and review realised benefits.

Governance and control

  • Projects require an accountable sponsor and owner.
  • Gate progression requires the specified evidence and approval.
  • Budget changes above tolerance require authorised approval.
  • Overdue milestones and unresolved high risks must escalate.
  • Closure requires agreed deliverables and outstanding actions to be accounted for.

Accountable roles

Project sponsor
Portfolio manager
Project manager
Deliverable owner
Investment approver

Permissions are configured and tested for the agreed responsibilities.

Data, interfaces and operating requirements.

Core records

Programme / projectApplication / business caseMilestoneBudget / fundingRisk / issueDecisionDeliverableCloseout record

Systems and interfaces

  • Approved finance records
  • Delivery tools
  • Document and notification services

Interface scope, data mapping and testing are agreed for each engagement.

Implementation requirements
Core application; organisational investment rules and optional finance or delivery tool integrations apply.

Mobile and tablet access

Review milestones, issues and delegated approvals through responsive portfolio views.

Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.

AI extensions

Prepare draft progress summaries from recorded delivery evidence for project manager review.

AI extensions are scoped around the required data, business outcome and review controls.

Engineered with Genesis.

Structured application engineering

Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.

Controlled changes

Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.

Deployment and support

Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.

An example operating scenario

See the process, its exception and the evidence.

An initiative is approved with funding and dependencies. A milestone is blocked by another workstream, a scope change is reviewed and the revised plan is authorised. The sponsor accepts the deliverable and the benefit-review obligation remains visible.

What to review

  • A saved end-to-end transaction
  • An exception and its authorised resolution
  • Different operator, approver and reviewer permissions
  • Final records, history and the relevant report

Questions before implementation.

How is this system adapted to our organisation?

Roles, approval authority, business rules, records and reporting are configured around your operating model. Scope definition connects the required business outcome to workflows, interfaces and acceptance criteria.

How are approvals and responsibilities defined?

Operators, reviewers and authorised decision makers have defined responsibilities. Approval limits, exception handling and access permissions are agreed with your business owners and tested against the selected workflows.

Can it connect with our existing systems?

Interface requirements cover your existing business systems, data ownership, mapping and authentication. Connection design and testing form part of the agreed implementation scope.

What will we review in a solution walkthrough?

Start with a relevant business transaction, then review its approvals, an exception, role permissions and final records. Discuss the integrations, reporting and operating requirements that matter to your organisation.