Skip to content

RIP R2.2 VO Bundle

The R2.2 bundle is the second Regular Infrastructure Projects (RIP) process bundle shipped for the Province of Flevoland. It covers the voorlopig ontwerp (preliminary design) phase, picking up exactly where the R2.1 bundle's "Fase 1 voltooid → R2.2" end event leaves off.

It lives at examples/organizations/flevoland/rip-phase-22/ and is deployed to Operaton in a single multipart request from the BPMN Modeler's Deploy modal, the same way every other bundle is.

The process was derived from R2_2 - VO.pdf (rev. 21-11-2024), one of the Flevoland phase specifications kept under examples/organizations/flevoland/rip-phases-left/.

Process flow

RipR22Process has four lanes and nine user tasks.

Lane Responsible for
Projectleider Overall progress and the client-requirements feedback loop
Ontwerper The design itself — concept VO through definitive VO
RIP-team, Aandrager, Adviseur Investigations, requirements gathering and review
Omgevingsmanager Cables and pipelines, and the framework permit
Task id Name
Task_UitvoerenConditionerendeOnderzoeken Uitvoeren conditionerende onderzoeken
Task_VerzamelenKlanteisen Verzamelen klanteisen
Task_InventariserenKabelsLeidingen Inventariseren kabels en leidingen
Task_AanvragenRaamvergunning Aanvragen raamvergunning
Task_OpstellenConceptVO Opstellen concept VO
Task_BesprekenConceptVO Bespreken concept VO
Task_BesprekenKlanteisenKL Bespreken klanteisen en kabels en leidingen
Task_TerugkoppelenKlanteisen Terugkoppelen klanteisen
Task_OpstellenDefinitiefVO Opstellen definitief VO

The join gateway takes all five branches

All five branches of the opening parallel split rejoin the join gateway. The source PDF does not draw it that way. It shows Inventariseren kabels en leidingen and Aanvragen raamvergunning leaving the pool into CO1 and JU3.5 and never coming back — which, read as control flow, deadlocks at the join, because a parallel join waits for every incoming branch.

Those two hand-offs are modelled as textAnnotations instead. A callActivity would have been the faithful alternative, but CO1 and JU3.5 do not exist as fixtures, so it would dangle at deploy time and fail the manifest's calledElement test. Both are referenced by several phases and belong in a shared bundle of their own.

A deviation from the specification, on purpose

This is the one place where the bundle deliberately does not mirror the drawing. The annotation records the hand-off without asserting a flow that would not execute.

Bundle contents

Fifteen files deploy together: one BPMN, nine forms and five document templates.

Forms

One per user task, bound with camunda:formRef. Field types stay inside the eight the R2.1 bundle already uses — text, textarea, textfield, checkbox, datetime, select, radio, button — because nothing beyond those is exercised against this Camunda 7.21 stack.

Form Task
rip-conditionerende-onderzoeken.form Uitvoeren conditionerende onderzoeken
rip-verzamelen-klanteisen.form Verzamelen klanteisen
rip-inventariseren-kabels-leidingen.form Inventariseren kabels en leidingen
rip-aanvragen-raamvergunning.form Aanvragen raamvergunning
rip-concept-vo.form Opstellen concept VO
rip-bespreken-concept-vo.form Bespreken concept VO
rip-bespreken-klanteisen-kl.form Bespreken klanteisen en kabels en leidingen
rip-terugkoppelen-klanteisen.form Terugkoppelen klanteisen
rip-definitief-vo.form Opstellen definitief VO

Two modelling decisions are worth knowing:

  • The specification's conditional "LCC-raming (indien variantenafweging)" is a checkbox plus a reference field on rip-concept-vo.form rather than an artifact of its own, since it exists only when a variant trade-off actually happened.
  • klicMeldingReferentie is collected only on rip-inventariseren-kabels-leidingen.form. The concept-VO task reads the same information but does not also write it — two forms writing one process variable would mean whichever task completes last silently wins.

Document templates

One per green "Format …" box in the specification. A Format there and a .document here are the same thing: a template with bindings. The blue outputs drawn beside them are instances of these templates rather than artifacts of their own.

Template Attached to
rip-kes.document Task_VerzamelenKlanteisen
rip-ontwerptoelichting.document Task_OpstellenConceptVO
rip-bevindingenformulier.document Task_BesprekenConceptVO
rip-hoeveelheidsbepaling.document Task_OpstellenDefinitiefVO
rip-objectenboom.document (deliberately unattached — see below)

Zone keys are signOff and contactInformation, camelCase, from the start — unlike R2.1's templates, which shipped with signoff and contactInfo, keys DocumentZones never declares, leaving their signature blocks silently unrendered until v2026.08.4 repaired them.

ronl:documentRef is single-valued, so one task carries at most one template

Task_OpstellenConceptVO produces both the Ontwerptoelichting and the Objectenboom, and its one slot went to the Ontwerptoelichting. rip-objectenboom therefore ships and imports normally but carries no task badge in the Modeler. Its reference is maintained in Relatics instead. This is a limitation of the attribute, not an oversight in the bundle.

Deploying the bundle

Deployment is identical to any other bundle — see Deploying the bundle on the R2.1 page. Select the bundle directory in the Deploy modal and all fifteen resources are posted to Operaton in one multipart request.

The mirrored copy

Every RIP bundle exists twice on disk:

Path Role
examples/organizations/flevoland/rip-phase-22/ the authored source
e2e-fixtures/flevoland/ the mirror the E2E suite imports and deploys

Nothing stopped the two drifting, and they had. A parity test now asserts that every file in a mirrored bundle is byte-identical to its twin; a new bundle opts in by adding an entry to MIRRORED_BUNDLES.

The parity test does not run on a pull request

The backend deploy workflow triggers on push, not on pull_request, so no pull request runs these tests. A parity break surfaces on acc after merge, where npm test gates the deploy step — leaving a red acceptance branch and no deployment. Edit both copies together, or run the backend suite locally before opening the pull request.