These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Business Process Modeler
- Who it's for
- Shared services
Shared services
A shared services group may receive work from several teams while one operating organization owns the process model. The model's owner, linked scenario and nodes make the handoffs explicit. Review decisions and state history make it possible to see which revision was accepted for a simulation and which person made that decision.
How Business Process Modeler is set up for you
Common path
Name the shared process once, then map the sequence of intake, review and fulfillment work as nodes.
Controlled comparison
Keep a scenario's effective dates and policy reference with the revision used for each run.
Follow-through
Assign verification follow-ups when an output needs investigation or correction.
A shared services group may receive work from several teams while one operating organization owns the process model. The model's owner, linked scenario and nodes make the handoffs explicit. Review decisions and state history make it possible to see which revision was accepted for a simulation and which person made that decision.
Pick a request type with a clear start and end. Let the Model Designer map the transfer between an intake team and the specialist who fulfills it. The Process Owner should check whether the node sequence includes each responsibility change. If source and target fields cross a connector, review their mapping version and transformation rule before a simulation relies on them.
Run one revision through validation and independent review. Have the reviewer inspect the operation steps and evidence reference, then approve or return it with a reason. After a simulation, compare the result against the scenario that was effective for that run. A later policy change should lead to a controlled comparison with a new basis rather than a reinterpretation of the earlier result.
Give the Evidence Steward a specific follow-up case. The assignee should be able to locate the original model, run and receipt, record a resolution and close the action after verification. This is a practical check of whether a shared services team can explain a result across organizational handoffs.
Features to start with
Roles on the team
- Admin
- Sets organization access and oversees configuration.
- Process Owner
- Owns a model revision and decides when it is ready for validation.
- Model Designer
- Maps process nodes and maintains scenario-linked model details.
- Simulation Operator
- Runs reviewed revisions and examines the operation trace.
- Independent Reviewer
- Reviews a specific revision and its recorded evidence.
- Evidence Steward
- Checks external receipts and resolves assigned verification work.
Set up Business Process Modeler your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.