Begin with the responsibility
Name the work, decision owner, user, source and completion condition that require a stable operating route.
Current product edition · 2026
Bom Runtime™
Bom Runtime™ products and services
Choose the operating depth from the responsibilities, processes, sources, users, tools, evidence and review conditions that must work together.
02Bom Runtime™
How to use this guide
Count the operating units
Roles, processes, sources, user groups, environments, workflows and review gates determine product depth.
Confirm ownership and evidence
Every result ends with accepted owners, sources, access, completion evidence, exceptions and a next review condition.
This guide is the commercial interpretation of Bom Runtime™. The system publication remains the methodological definition. Open · Bom Runtime™ ↗
03Bom Runtime™
Contents
04Bom Runtime™
Choose the operating result
BN07 / BN10
Resolve one process or one compact operating product.
RTM-10
Establish responsibility, decisions and operating rhythm.
RTM-20
Connect processes, procedures, quality and transfer.
RTM-30
Govern sources, knowledge, access and migration.
RTM-40
Prepare one business area for responsible AI-supported operation.
RTM-50 / 51
Review or maintain an accepted operating system.
05Bom Runtime™
Buyer-persona fit
Personas identify who carries the buying and operating decision. Runtime depth follows responsibility, source authority, process count, information conditions and adoption boundary.
P1
Decision, authority and operating ownership
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P2Use, delivery, specialist or implementation context
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P3Use, delivery, specialist or implementation context
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P4Decision, authority and operating ownership
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P5Use, delivery, specialist or implementation context
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P6Use, delivery, specialist or implementation context
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P7Use, delivery, specialist or implementation context
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗06Bom Runtime™
Touchpoint, readiness and evidence fit
Touchpoints locate the commercial decision. Readiness and evidence overlays qualify whether an operating architecture can begin.
07Bom Runtime™
System responsibility and product boundary
Bom Runtime™
Owns repeatable operationRoles, decisions, sources, rhythm, processes, quality, transfer, context and review.
Bom Blueprint™
Supplies governing architectureAccepted business model, offer, operating decisions, dependencies and change authority.
Bom Flow™
Supplies accepted routesEntry, choice, action, transfer and service movements requiring continuing ownership.
Bom Creation™
Supplies operating materialsAccepted interfaces, documents, forms, checklists, templates and publication assets.
08Bom Runtime™
The governing definition of Bom Runtime™
Bom Runtime™ turns approved architecture into repeatable operating practice. It assigns responsibility, decision authority, sources, rhythm, completion criteria, transfer conditions and review triggers.
The agency result is a governed operating architecture. The organisational effect is a shared standard for how people, tools and AI-supported work carry accepted decisions into everyday use.
Open · complete system definition ↗09Bom Runtime™
Six Runtime functions
Role
Responsibility map covering work ownership, decision rights, interfaces and escalation.
Rhythm
Operating rhythm for opening, executing, reviewing and closing recurring work.
Source
Source-of-Truth structure with authority, status, ownership, version and relationship rules.
Quality
Definition of Done, checklists, evidence and exception routes for recurring work.
Transfer
Handover and onboarding records carrying context and readiness into the receiving role.
AI context
Approved sources, role boundaries, process logic, verification and update rules for business AI use.
10Bom Runtime™
Eleven RUN mechanisms
Functions describe operating responsibility. RUN codes identify method mechanisms. RTM codes identify commercial products.
| Code and mechanism | Operating function |
|---|---|
| RUN-01 · Responsibility mapping | Assigns roles, decision owners, mandate and RACI relations. |
| RUN-02 · Decision and escalation model | Defines criteria, authority and escalation for recurring decisions. |
| RUN-03 · Operating-rhythm design | Establishes review and coordination cycles. |
| RUN-04 · SOP and checklist design | Converts repeatable work into sequence, conditions and responsibility. |
| RUN-05 · Definition of Done and quality control | Defines completion, review, approval and readiness. |
| RUN-06 · System and source registry | Records documents, decisions and tools with owners and status. |
| RUN-07 · Knowledge-repository architecture | Structures access, ownership, versions and navigation. |
| RUN-08 · Onboarding and knowledge transfer | Enables people and partners to assume context and responsibility. |
| RUN-09 · AI-context governance | Maintains approved context, human ownership and update rules. |
| RUN-10 · Automation and workflow direction | Identifies work suitable for integration or automation. |
| RUN-11 · Maintenance and learning governance | Connects source review, operating evidence and recalibration. |
11Bom Runtime™
What an operating unit means
An operating unit is one recurring responsibility expressed as work that can be assigned, completed, evidenced, reviewed and transferred.
Trigger and input
The event, source and conditions that begin the work.
Owner and authority
The role performing the work and the role authorised to decide or accept.
Sequence and output
The required actions and the resulting record, object or state.
Completion and evidence
The criteria and evidence confirming usable completion.
Exception and escalation
The recovery or decision route when the standard sequence changes.
Transfer and review
The next owner, required context and review condition.
12Bom Runtime™
Product ladder
01
RTM-10
Responsibility and Operating Rhythm
A team requires explicit responsibility, recurring decisions and a usable operating cadence.
- Hours
- 60
- Review gates
- 3
RTM-20
Process and Quality Operating System
Several related recurring activities require one sequence, responsibility model and completion standard.
- Hours
- 112
- Review gates
- 4
RTM-30
Source and Knowledge Architecture
Work is dispersed across documents, tools and people and requires a governed knowledge environment.
- Hours
- 126
- Review gates
- 4
RTM-40
AI-Ready Operating Architecture
One business area requires approved context, human responsibility and a controlled route for AI-supported workflows.
- Hours
- 182
- Review gates
- 5
RTM-50
Runtime Review
An accepted operating system reaches a review event or scheduled control point.
- Hours
- 32
- Review gates
- 1
RTM-51
Runtime Stewardship
An accepted operating system requires controlled monthly maintenance and learning.
- Hours
- 24
- Review gates
- 2
13Bom Runtime™
How every price is constructed
Agency task register
Every task has a definition, responsible specialisation, hours, rate, subtotal and acceptance evidence.
Two reference constructions
Agency work uses 100 EUR per hour or 440 PLN per hour before visible product-level rounding.
External and specialist costs
Platforms, licences, integrations, migration, security, legal and specialist work receive separate accepted lines.
Scope change
A new area, team, repository, platform, workflow, information class or operating model triggers a new assessment.
14Bom Runtime™
One delivery and acceptance cycle
Qualify
Name the recurring responsibility, users, current operating condition and smallest useful boundary.
Admit
Confirm authority, sources, access, information class, evidence, dependencies and specialist triggers.
Design
Build roles, decisions, rhythm, processes, sources, quality, transfer and review conditions.
Review
Use consolidated gates to decide corrections across dependent operating units.
Transfer
Assign ownership, access, operating guidance, evidence and the first continuing review.
15Bom Runtime™
Qualified entries and their boundaries
Qualified entries resolve one bounded responsibility before the organisation commits to a wider operating architecture.
KT08 · Business AI Use Training
One user introduces AI-supported work in one agreed business area.
BN07 · Operating Process Architecture
One recurring business activity requires a stable sequence, ownership and completion conditions.
BN08 · AI-Ready Business Entry
One business area requires a controlled AI-use route with a named human owner and approved sources.
BN09 · AI Workflow & Automation Architecture
One repeatable workflow requires a controlled AI-assisted or automated route.
BN10 · Micro Operating Product
One recurring task requires a compact register, board, form, checklist, template family or controlled dashboard.
16KT08
KT08 · Business AI Use Training
560 EUR · 2,500 PLNActive- Activating situation
- One user introduces AI-supported work in one agreed business area.
- Included agency result
- Goal calibration, tailored examples, a 120-minute session and a practical operating note.
- Scope
- One user and one business-use area. Further users, areas, integrations, licences and implementation receive separate scope.
- Next responsible route
- BN08 or RTM-40.
17BN07
BN07 · Operating Process Architecture
950 / 1,650 / 2,750 EUR · 4,200 / 7,300 / 12,100 PLNLimited- Activating situation
- One recurring business activity requires a stable sequence, ownership and completion conditions.
- Included agency result
- Basic: process map and responsibility line. Medium: role matrix and procedure. Max: controls, Definition of Done, measurement and onboarding route.
- Scope
- One process in a supported format. Multi-process systems, migration and organisational redesign receive separate scope.
- Next responsible route
- RTM-10 or RTM-20.
18BN08
BN08 · AI-Ready Business Entry
830 / 1,950 / 4,100 EUR · 3,700 / 8,600 / 18,100 PLNActive- Activating situation
- One business area requires a controlled AI-use route with a named human owner and approved sources.
- Included agency result
- One to several use-case cards, source boundary, responsibility model, implementation sequence and tier-appropriate role guidance.
- Scope
- One business area. Several areas, teams or source systems route to RTM-40 or individual architecture.
- Next responsible route
- KT08, BN09 or RTM-40.
19BN09
BN09 · AI Workflow & Automation Architecture
830 / 1,950 / 4,100 EUR · 3,700 / 8,600 / 18,100 PLNLimited- Activating situation
- One repeatable workflow requires a controlled AI-assisted or automated route.
- Included agency result
- From an architecture specification to one eligible production workflow, depending on the accepted tier.
- Scope
- One workflow and approved environment. Regulated judgment, sensitive information, unsupported platforms and wider engineering require specialist scope.
- Next responsible route
- RTM-40 for a wider operating architecture.
20BN10
BN10 · Micro Operating Product
950 / 1,650 / 2,750 EUR · 4,200 / 7,300 / 12,100 PLNLimited- Activating situation
- One recurring task requires a compact register, board, form, checklist, template family or controlled dashboard.
- Included agency result
- One to three linked operating modules, tier-appropriate guide, acceptance check and handover.
- Scope
- Supported formats and current capacity. Custom software, extensive integrations and wider operating systems receive separate scope.
- Next responsible route
- RTM-10, RTM-20 or RTM-30.
21RTM-10
RTM-10 · Responsibility and Operating Rhythm
6,000 EUR · 26,400 PLN60 h · 3 to 4 weeks- Activating situation
- A team requires explicit responsibility, recurring decisions and a usable operating cadence.
- Scope
- Up to eight roles, six recurring decision classes and daily, weekly and monthly rhythm with three review gates.
- Included agency result
- Responsibility map, decision and escalation route, operating rhythm, meeting and record architecture and ownership handover.
- Next responsible route
- RTM-20 for processes and quality; RTM-50 for review.
22RTM-10
RTM-10 · result, reason, effect and acceptance
Included agency result
Responsibility map, decision and escalation route, operating rhythm, meeting and record architecture and ownership handover.
Why this approach
Responsibility and time become one operating agreement rather than separate expectations.
Organisational effect
Predictable decisions, reviews, escalations and ownership across recurring work.
Acceptance evidence
Every included role, decision class and recurring event has an accepted owner, input, output, authority and exception route.
23RTM-10
RTM-10 · task and price record
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Start Gate and operating boundaryConfirms the team, roles, recurring decisions, sources, access, owner and acceptance route. | Collaboration architect | 4 | 400 | 1,760 |
| Source and responsibility intakeAdmits current role, process, meeting and decision records and records conflicts. | Information architect | 6 | 600 | 2,640 |
| Responsibility architectureDefines ownership, mandate, backup, interfaces, inputs, outputs and workload for up to eight roles. | Operating architect | 14 | 1,400 | 6,160 |
| Decision and escalation routeDefines up to six recurring decision classes, criteria, authority and escalation. | Operating architect | 10 | 1,000 | 4,400 |
| Operating rhythmDesigns daily, weekly and monthly opening, execution, review and closure events. | Operating architect | 10 | 1,000 | 4,400 |
| Three consolidated review gatesCoordinates decisions and accepted corrections across roles and rhythm. | Runtime delivery lead | 9 | 900 | 3,960 |
| Operating record and direct handoverRecords owners, events, sources, escalation and the first review point and transfers them to the team. | Documentation architect | 7 | 700 | 3,080 |
| Fixed product price | 60 | 6,000 | 26,400 |
24RTM-20
RTM-20 · Process and Quality Operating System
11,200 EUR · 49,300 PLN112 h · 6 to 8 weeks- Activating situation
- Several related recurring activities require one sequence, responsibility model and completion standard.
- Scope
- Up to four linked processes, twelve roles, eight procedures or checklists and four review gates.
- Included agency result
- Process architecture, role matrix, procedures, checklists, Definition of Done, quality and exception routes and onboarding package.
- Next responsible route
- RTM-30 for sources and knowledge; RTM-50 for review.
25RTM-20
RTM-20 · process, quality and transfer architecture
Process architecture
Trigger, input, action, decision, owner, output, control, exception and transfer are recorded for every included process.
Procedures and checklists
Accepted processes become working sequences with conditions, evidence and responsibility.
Quality and exceptions
Definition of Done and exception routes make usable completion and recovery observable.
Onboarding and transfer
The receiving roles obtain sources, access, instructions, acceptance conditions and a first review point.
26RTM-20
RTM-20 · task and price record I
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Start Gate and process boundaryConfirms processes, roles, sources, users, access, dependencies and acceptance route. | Collaboration architect | 5 | 500 | 2,200 |
| Process-source and evidence intakeAdmits current procedures, records, tools, obligations and evidence and records conflicts. | Information architect | 10 | 1,000 | 4,400 |
| Linked process architectureDefines triggers, inputs, actions, decisions, owners, outputs, controls and exceptions for up to four processes. | Operating architect | 28 | 2,800 | 12,320 |
| SOP and checklist systemTurns accepted processes into up to eight usable procedures or checklists. | Process architect | 24 | 2,400 | 10,560 |
| Task subtotal | 67 | 6,700 | 29,480 |
27RTM-20
RTM-20 · task and price record II
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Definition of Done and quality gatesDefines completion, review, approval, evidence and readiness for the included outputs. | Quality architect | 18 | 1,800 | 7,920 |
| Exception and escalation routesDefines decision authority, recovery and escalation for material exceptions. | Operating architect | 8 | 800 | 3,520 |
| Four consolidated review gatesCoordinates decisions and accepted corrections across dependent processes. | Runtime delivery lead | 11 | 1,100 | 4,840 |
| Onboarding package and direct handoverPrepares role guidance, access requirements, first-use route and transfer of operating ownership. | Knowledge-transfer architect | 8 | 800 | 3,520 |
| Explicit Poland-market rounding | Commercial decision owner | 0 | 0 | +20 |
| Task subtotal | 45 | 4,500 | 19,800 |
112 h · 11,200 EUR49,300 PLN
28RTM-30
RTM-30 · Source and Knowledge Architecture
12,600 EUR · 55,400 PLN126 h · 7 to 9 weeks- Activating situation
- Work is dispersed across documents, tools and people and requires a governed knowledge environment.
- Scope
- Up to sixty admitted sources, five user groups, one repository environment and four review gates.
- Included agency result
- Source and system register, authority and version rules, repository architecture, access model, migration route and operating guide.
- Next responsible route
- RTM-40 for AI-ready operation; RTM-50 for review.
29RTM-30
RTM-30 · source, access, version and migration
Authority and status
Every source states whether it governs, informs, evidences, awaits decision or has been superseded.
Access and ownership
User groups receive proportionate access and every source receives an owner and review trigger.
Version and relationship
Current versions connect to dependent records, earlier sources and the decisions they support.
Migration and continuity
Preparation, movement, verification, redirects, archive and operating handover follow one accepted sequence.
30RTM-30
RTM-30 · task and price record I
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Start Gate and repository boundaryConfirms source population, user groups, repository environment, access, owner and acceptance route. | Collaboration architect | 5 | 500 | 2,200 |
| Source, system and tool inventoryInventories up to sixty sources with authority, status, owner, version, relation and location. | Information-governance architect | 14 | 1,400 | 6,160 |
| Source of Truth and system registryDefines governing records, authority rules, status vocabulary, ownership and review triggers. | Information-governance architect | 22 | 2,200 | 9,680 |
| Knowledge-repository architectureDesigns navigation, taxonomy, relationships, user routes and controlled information placement. | Knowledge architect | 24 | 2,400 | 10,560 |
| Task subtotal | 65 | 6,500 | 28,600 |
31RTM-30
RTM-30 · task and price record II
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Access, version and lifecycle rulesDefines user groups, permissions, version states, retention, review and retirement. | Information-governance architect | 18 | 1,800 | 7,920 |
| Migration and continuity routeSequences source preparation, movement, verification, redirects, archive and continuity steps. | Migration architect | 14 | 1,400 | 6,160 |
| Four consolidated review gatesCoordinates decisions and corrections across the source and repository model. | Runtime delivery lead | 16 | 1,600 | 7,040 |
| Operating guide and direct handoverDocuments everyday use, ownership, maintenance and the first scheduled review. | Documentation architect | 13 | 1,300 | 5,720 |
| Explicit Poland-market rounding | Commercial decision owner | 0 | 0 | -40 |
| Task subtotal | 61 | 6,100 | 26,840 |
126 h · 12,600 EUR55,400 PLN
32RTM-40
RTM-40 · AI-Ready Operating Architecture
18,200 EUR · 80,100 PLN182 h · 9 to 12 weeks- Activating situation
- One business area requires approved context, human responsibility and a controlled route for AI-supported workflows.
- Scope
- One business area, up to three workflows, six user roles, one approved platform context and five review gates.
- Included agency result
- Use-case portfolio, source and context architecture, responsibility and human-review model, workflow specifications, implementation briefs and operating rhythm.
- Next responsible route
- RTM-50 for review; RTM-51 for continuing stewardship.
33RTM-40
RTM-40 · human ownership, context and triggers
Human ownership
Every supported decision retains a named human owner, reviewer, escalation route and acceptance authority.
Approved context
Use cases receive current sources, permitted inputs, version rules and update ownership.
Verification and quality
Expected outputs, review criteria, evidence and Definition of Done are explicit for each workflow.
Specialist triggers
Legal, security, regulated, sensitive-information and technical conditions route to qualified sources and people.
The product supplies operating architecture and implementation briefs. Technical implementation, licences, integrations and specialist determinations receive separate accepted lines.
34RTM-40
RTM-40 · task and price record I
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Start Gate, eligibility and information boundaryConfirms the business area, workflows, users, platform context, information class, sources, owners and specialist triggers. | Collaboration architect | 6 | 600 | 2,640 |
| Source, data, use-case and tool intakeAdmits current workflows, information sources, tool constraints, policies and evidence and records conflicts. | AI-context architect | 14 | 1,400 | 6,160 |
| Responsibility and human-review architectureDefines human decision ownership, permissions, review, escalation and accountability across up to six roles. | Operating architect | 18 | 1,800 | 7,920 |
| AI-context architectureStructures approved sources, context packs, information boundaries, version rules and update ownership. | AI-context architect | 32 | 3,200 | 14,080 |
| Workflow and automation directionDesigns up to three workflows, control points, suitability conditions and implementation sequence. | Workflow architect | 36 | 3,600 | 15,840 |
| Task subtotal | 106 | 10,600 | 46,640 |
35RTM-40
RTM-40 · task and price record II
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Implementation briefsTranslates accepted workflow and context decisions into bounded briefs for approved environments or providers. | Implementation architect | 24 | 2,400 | 10,560 |
| Risk and specialist-trigger registerRecords information, legal, security, regulated and technical triggers, owners and required evidence. | Information-governance architect | 12 | 1,200 | 5,280 |
| Role guidance and knowledge transferPrepares users to apply the approved context, review, quality and escalation rules. | Knowledge-transfer architect | 12 | 1,200 | 5,280 |
| Five consolidated review gatesCoordinates decisions and corrections across context, workflows, roles and briefs. | Runtime delivery lead | 16 | 1,600 | 7,040 |
| Operating rhythm and direct handoverRecords maintenance, learning, review ownership and the first operating cycle. | Documentation architect | 12 | 1,200 | 5,280 |
| Explicit Poland-market rounding | Commercial decision owner | 0 | 0 | +20 |
| Task subtotal | 76 | 7,600 | 33,440 |
182 h · 18,200 EUR80,100 PLN
36RTM-50
RTM-50 · Runtime Review
3,200 EUR · 14,100 PLN32 h · 8 business days- Activating situation
- An accepted operating system reaches a review event or scheduled control point.
- Scope
- One accepted Runtime baseline, current evidence and up to six correction decisions.
- Included agency result
- Review register, drift and dependency account, correction decisions, owners, next action and review date.
- Next responsible route
- A correction scope, RTM-51 or the next recorded review.
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Review Gate and baseline boundaryConfirms the event, baseline, owners, sources, evidence and correction authority. | Collaboration architect | 2 | 200 | 880 |
| Current source and evidence intakeAdmits current operating records, incidents, feedback, changes and measurements. | Information architect | 4 | 400 | 1,760 |
| Role, rhythm and transfer reviewChecks ownership, decisions, cadence, escalation, onboarding and handover integrity. | Operating architect | 8 | 800 | 3,520 |
| Process, quality, source and AI-context reviewChecks processes, completion standards, sources, permissions, workflows and update conditions. | Quality architect | 10 | 1,000 | 4,400 |
| Up to six correction decisionsRecords decision, consequence, priority, owner, scope and acceptance evidence. | Operating architect | 4 | 400 | 1,760 |
| Consolidated review gateCoordinates correction decisions and affected dependencies. | Runtime delivery lead | 2 | 200 | 880 |
| Review handoverRecords next action, owner, date, evidence requirement and implementation route. | Documentation architect | 2 | 200 | 880 |
| Explicit Poland-market rounding | Commercial decision owner | 0 | 0 | +20 |
| Fixed product price | 32 | 3,200 | 14,080 |
37RTM-51
RTM-51 · Runtime Stewardship
2,400 EUR · 10,600 PLN / month24 h · monthly cycle- Activating situation
- An accepted operating system requires controlled monthly maintenance and learning.
- Scope
- Twenty-four agency hours per month, accepted backlog and two consolidated review gates.
- Included agency result
- Current operating register, approved source, role, rhythm and quality updates, evidence record and month-close handover.
- Next responsible route
- The next monthly cycle or a separately accepted extension.
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Monthly Start Gate and backlogConfirms backlog, affected components, owners, sources, evidence, access, capacity and acceptance. | Collaboration architect | 3 | 300 | 1,320 |
| Operating evidence and source reviewReviews current events, evidence, incidents, feedback, source changes and dependencies. | Information-governance architect | 5 | 500 | 2,200 |
| Approved operating updatesApplies accepted changes to roles, rhythms, sources, procedures, quality, transfer or AI context. | Operating architect | 8 | 800 | 3,520 |
| Two consolidated review gatesCoordinates decisions and corrections within the monthly backlog. | Runtime delivery lead | 4 | 400 | 1,760 |
| Month close and handoverRecords current state, evidence, owners, dependencies, next backlog and review condition. | Documentation architect | 4 | 400 | 1,760 |
| Explicit Poland-market rounding | Commercial decision owner | 0 | 0 | +40 |
| Fixed product price | 24 | 2,400 | 10,560 |
38Bom Runtime™
Evidence, transfers and code index
Applied evidence
Bom Dia Creation™Responsibility, source, decision, publication, review and owner-control records in current use.↗HugMeControlled source, production, review and handover structures.↗POLVALVETechnical-information review, correction, production and quality routes.↗JednoWinoCatalogue, print, exception, publication and source-status records.↗Products and method codes
KT08 / BN07-10Open governing context↗RTM-10 / 20 / 30 / 40Open governing context↗RTM-50 / 51Open governing context↗Runtime F01-F06Open governing context↗RUN-01-RUN-11Open governing context↗Bom Blueprint™ 04 / 06Open governing context↗Evidence supports the method, artefacts and implemented control structures. Productivity, adoption, time saving, error reduction and commercial performance require current measurements for the relevant environment.
39Bom Runtime™
Responsibilities, access, information, timing and acceptance
Client responsibility
Provide authorised sources, decision and acceptance owners, users, access, information classifications, consolidated feedback and decisions within the agreed calendar.
Agency responsibility
Perform accepted tasks, record sources and decisions, coordinate named work, protect operating quality and supply acceptance evidence.
Access, information and third parties
The proposal and agreement record access authority, information conditions, platform roles, provider terms, rights and specialist-review requirements.
Timing and acceptance
Time begins after the complete Start Gate. Late sources or decisions, accepted changes and provider dependencies update the recorded schedule.
The accepted proposal and agreement establish transaction-specific scope, price, tax, timetable, rights, access, information, payment, responsibility and acceptance.
Bom Runtime™
Take the next operating decision
Name the recurring responsibility and intended operating state. Confirm owners, sources, access, evidence and specialist triggers. Count roles, processes, sources, user groups, environments and workflows. Choose the smallest Runtime product that can establish accepted operation and continuing review.