Implementation Project

A defined project to configure the product or platform, integrate it with your systems, migrate data, test, train your people and go live. It is charged once, as a fixed price or on time and materials, set out in a statement of work, and ends at an agreed acceptance point. Every implementation follows the same phases; their length depends on scope, so the plan in your proposal gives the dates.

1. DiscoveryWe learn how the work is done today, the regulations it answers to, the systems around it and what success has to look like. Agreed outcome: signed-off scope, success measures and plan.
2. DesignThe target configuration, integrations, data model, security controls and hosting, written down before anything is built. Agreed outcome: an approved design; later changes go through change control.
3. ImplementationConfiguration and build in a non-production environment, shown to your team as it progresses. Agreed outcome: a build ready for testing.
4. MigrationMoving records and history from the systems being replaced, with checks that nothing is lost or changed in transit. Agreed outcome: a reconciled trial migration you have approved.
5. TestingSystem, integration, performance, security and accessibility testing by Moraph, and user acceptance testing by your own staff against the agreed success measures. Agreed outcome: acceptance, recorded in writing.
6. Go-liveMoving to production on a planned date, with a rehearsed cut-over and a way back if it is needed. Agreed outcome: production use, with a period of close support before handover.
7. Ongoing operationsHandover from the project team to the people who will run and support the system for the rest of the term. Agreed outcome: service measured against the levels in your agreement.

Change control

Either side can raise a change request. Moraph assesses its effect on scope, plan, cost and risk, in writing, and nothing changes until you approve it in writing.

Acceptance criteria

Each deliverable has criteria agreed in advance. Acceptance is given in writing, against those criteria, not by impression.

Escalation

Your product owner and our delivery lead first, then the engagement executive, then a Moraph executive sponsor at steering level. Risks, issues, decisions and dependencies are kept in a shared log you can see.

A sponsor

Someone senior who owns the outcome, can settle competing priorities and joins steering meetings.

A product owner

The person who makes day-to-day decisions about how the system should work, and can get answers from the business quickly.

Subject-matter experts

The people who do the work today, for discovery, design reviews and user acceptance testing.

Technical access

Access to the systems and environments we integrate with, and contacts in the teams that run them.

Security and compliance contacts

People who can review controls, approve connections and answer for your own regulatory obligations.

Timely decisions

Decisions and sign-offs when the plan needs them. Delays on either side are tracked, and their effect on the plan is shown openly.