C_SIGPM sample questions & answers

Velmora Textiles, a mid-sized fabric maker in Porto, Portugal, grew from one weaving line to five in just three years. Order fulfillment now slips constantly. When a wholesale order arrives by email, a sales clerk keys it into a spreadsheet, then verbally tells the planning desk, who scribble it onto a whiteboard for the dye house. Nobody has ever agreed where one team's job ends and the next begins, so dye batches are sometimes started before credit is checked and sometimes wait days because each team assumes another owns the next step. Two large orders were dyed the wrong colour last month because the shade code lived only in the clerk's head. The five lines now share suppliers and machines, so a stall in one team's step quietly cascades into the others, and the wholesale accounts that drive most revenue are hit hardest. Leadership blames "careless staff," yet every team is faithfully following what it believes is the process; the trouble appears at the seams between them. A new operations lead wants to address the root cause rather than bolt on more checking that would only slow every order further.

Which recommendation best addresses the underlying cause of Velmora's fulfillment failures?

At Halcyra Papermill in Gothenburg, the process office has published dozens of diagrams describing pulp handling and shipping. Reviewers notice that the same warehouse management system appears under three different names across the diagrams: one team wrote it one way, another abbreviated it, and a third used an old project label. When the system was recently renamed, an analyst had to open every affected diagram by hand to update the label, and several were missed, leaving stale names in production models. The underlying cause is that each modeler typed the system name as free text directly onto activities and data objects rather than referencing a shared, governed entity. Without a single source for such recurring objects, terminology drifts, searches miss diagrams, and any future change means another manual sweep. Leadership wants a way to keep names consistent and to make a single edit propagate everywhere the system is used. As the Signavio consultant advising the modeling team, you must recommend a sustainable approach that fixes the root cause rather than patching the current symptoms one diagram at a time.

What should you recommend to keep recurring object names consistent across all diagrams?

Havstein Tannery in Trondheim, Norway modeled its raw-hide intake process in SAP Signavio Process Manager. After an 'Inspect incoming hide' task, an analyst placed a parallel gateway that splits flow into two branches, 'Route to tanning line' and 'Return batch to supplier', and both branches then continue as if they always execute together. In practice each delivered hide is either accepted and sent to tanning or rejected and returned, never both. Reviewers notice that when the model is walked through, every inspected hide appears to travel down both branches at once, producing token counts that never reconcile at the downstream merge. The quality lead asks how the diagram should represent this accept-or-reject decision so that exactly one branch runs for each hide, driven by the inspection result. The team wants the correction to reflect standard BPMN 2.0 flow-control semantics rather than a workaround such as deleting one branch or adding manual notes. They also want the fragment to remain readable to auditors who follow the flow. Which change correctly captures the intended behaviour?

Which change correctly models the accept-or-reject decision after inspection?

Idrija Furnace Co in Slovenia is rolling out its Signavio workspace to about forty people, and during onboarding the administrator assigned everyone a modeler license so that nobody would ever find themselves blocked. In day-to-day practice, however, only six people actually author or change process diagrams; the remaining staff open models solely to read them, add the occasional comment, and check published versions before an internal audit. Procurement has now flagged that the paid modeler licenses are almost exhausted and the next round of hires cannot be added without purchasing more, which was not budgeted. Reviewing the activity logs, the administrator confirms that the six authors are the only people who ever save a change, while everyone else has view and comment behavior only. Leadership wants to keep every employee's ability to see the models and to preserve the reviewers who depend on read access ahead of the audit, but it also wants to stop paying for edit rights that are never exercised. The administrator is now examining how each license type maps to what individuals genuinely do in the workspace before submitting any request for additional license budget.

What is the most appropriate way to resolve the license shortage?

Quenby Foundry in Sheffield is redesigning how it handles bespoke casting orders after complaints about a confusing intake experience. The improvement team opens SAP Signavio and immediately begins mapping the internal steps its sales and production planners follow, from order receipt through scheduling and dispatch. A facilitator notices the resulting diagrams describe only what the foundry does internally and never show how a buyer perceives placing an order, waiting for a quote, or chasing delivery updates. Management has stated the goal is to improve the buyer's experience, yet the current models cannot reveal where buyers feel frustration or lose confidence. The team debates whether the internal process diagrams alone are enough, or whether a different modeling lens is required to surface where the experience actually breaks down for the person on the other side of the transaction. They want the redesign anchored in how customers move through their own decision and interaction stages, not only in how the foundry executes work internally. What the foundry needs is a view that follows the buyer through their own decision path, comparing suppliers, requesting a quote, then living with the wait for confirmation. Only that lens can reveal the exact points where a customers trust in Quenby quietly erodes.

What modeling approach best anchors the redesign in the buyer's experience?

Kairnos Logistics, a freight forwarder in Gdansk, Poland, handles customs clearance for several hundred shipments a week. Officially there is "one" clearance procedure, but in practice each of the four branch offices has evolved its own way of preparing documents: some collect the commercial invoice first, others start with the packing list, and one skips a broker pre-check entirely whenever the desk is busy. New hires simply learn whatever their local mentor happens to do. Clearance times swing wildly, with the Hamburg desk averaging six hours while the Riga desk takes two days for identical shipment types, and every delayed clearance racks up demurrage charges the customer sees. Management assumes Riga just has weaker staff and is weighing whether to replace the team. In reality, nobody has ever compared the branches side by side; the "standard" survives only as a title on an old slide, and each undocumented variant carries its own rework whenever a required document turns out to be missing. Before any staffing decision is taken, a consultant is asked to determine what is really driving the inconsistency and to recommend a defensible first move.

Which recommendation best targets the real driver of Kairnos's inconsistent clearance times?