Content Plan
Everything that must be produced before the training can be delivered. Each item has an ID used in the Trainer Guide and Participant Enablement.
Note
Owners and status are placeholders to be filled in.
Deliverables
Program
| ID |
Deliverable |
Description |
Owner |
Status |
| C-01 |
Trainer guide |
This documentation site |
TBD |
Draft |
| C-17 |
Invitation and agenda |
Outcome-first invitation, agenda, and practical information for participants |
TBD |
Not started |
| C-16 |
Feedback form |
Measures whether the mindset shift landed (see Success Measures) |
TBD |
Not started |
Session 1 – Keynote
| ID |
Deliverable |
Description |
Owner |
Status |
| C-02 |
Keynote deck |
Vision, Vanguard, AI-native operations, digital twins, agentic systems, time-to-value, value streams A vs. B, operational data, Understand → Act → Create |
TBD |
Not started |
Session 2 – DevOps Agents
| ID |
Deliverable |
Description |
Owner |
Status |
| C-03 |
DevOps Agents demo |
Demo script with pre-tested intents (data model, business logic, integration, guardrails), prepared demo environment, fallback recording |
TBD |
Not started |
Session 3 – App Builder Workshop
| ID |
Deliverable |
Description |
Owner |
Status |
| C-04 |
Workshop slides |
Recap, verticals, problems, flow, show & tell format |
TBD |
Not started |
| C-05 |
Outcome Canvas |
Printable and digital handout |
TBD |
Not started |
| C-06 |
Problem cards (15) |
One card per problem: vertical, user role, key question, context |
TBD |
Not started |
| C-07 |
Data model cheat sheets (5) |
Per vertical: DOM objects and fields, real-time data, how to combine them in App Builder |
TBD |
Not started |
| C-08 |
Backend Catalog packages (5) |
See Backend Package Work |
TBD |
Design |
| C-09 |
Reference apps |
At least one app per vertical that answers each of its three problems; used as trainer answer key and to validate the data |
TBD |
Not started |
Session 4 – Specialized Agents Workshop
| ID |
Deliverable |
Description |
Owner |
Status |
| C-10 |
Workshop slides and agent design card |
Recap, knowledge vs. data, agent design card, guardrails |
TBD |
Not started |
| C-11 |
Knowledge packs (5) |
Per vertical: policies, procedures, escalation rules, standards – consistent with the package seed data |
TBD |
Not started |
| C-12 |
Reference agents (5) |
One working agent per vertical, used to demonstrate and unblock |
TBD |
Not started |
Session 5 – Agent-to-Agent
| ID |
Deliverable |
Description |
Owner |
Status |
| C-13 |
Agent-to-Agent demo |
Scenario script, pre-built agents with clear roles, approval step, fallback recording |
TBD |
Not started |
Environment
| ID |
Deliverable |
Description |
Owner |
Status |
| C-14 |
Training environment |
DataMiner Systems, user accounts and rights, Catalog visibility, agent tooling access |
TBD |
Not started |
| C-15 |
Dry run |
Full run of all sessions on the training environment, with the readiness checklists |
TBD |
Not started |
Backend Package Work
Each of the five packages (C-08) requires the same work. Details per vertical are on the package pages.
| # |
Work item |
Done when |
| 1 |
DOM model |
Definitions and fields match the package page; stable IDs; installs idempotently |
| 2 |
Install script |
Creates DOM module, 9 elements, 3 services, view, and seed data with correct links |
| 3 |
Element data and templates |
Parameters, alarm thresholds, and trending as on the package page |
| 4 |
Scenario scripts |
Baseline, StartScenario, and Reset produce the documented timeline |
| 5 |
Catalog listing |
Package published as a private Catalog item with a clear description and prerequisites |
| 6 |
Validation |
Every problem's seeded answer is visible in App Builder (checked with C-09) |
Dependencies
flowchart LR
C08[C-08 Backend packages] --> C07[C-07 Cheat sheets]
C08 --> C09[C-09 Reference apps]
C08 --> C11[C-11 Knowledge packs]
C11 --> C12[C-12 Reference agents]
C12 --> C13[C-13 Agent-to-Agent demo]
C14[C-14 Environment] --> C15[C-15 Dry run]
C09 --> C15
C12 --> C15
C13 --> C15
C03[C-03 DevOps demo] --> C15
C02[C-02 Keynote] --> C15
Recommended order:
| Phase |
Deliverables |
| 1. Design |
Finalize the backend design and open decisions; outline the decks |
| 2. Build |
C-08 packages, C-02 keynote, C-03 DevOps demo, C-14 environment |
| 3. Build on the backend |
C-07 cheat sheets, C-09 reference apps, C-11 knowledge packs, C-05/C-06 handouts |
| 4. Agents |
C-12 reference agents, C-13 Agent-to-Agent demo |
| 5. Validate |
C-15 dry run, fixes, C-16 feedback form, C-17 invitation |
Consistency Rules
Content is produced by different people but must tell one story.
| Rule |
Applies to |
| Use the vertical terminology from the backend overview (e.g. Event, Mission, Network Service) |
All materials |
| Names, numbers, and thresholds match the package seed data |
C-06, C-07, C-09, C-11, C-12 |
| Knowledge pack rules must be testable against the scenario (e.g. escalation thresholds match the DOM values) |
C-11, C-12 |
| Every problem card has a seeded answer in its package |
C-06, C-08 |
| AI output is never stored in the backend |
C-08, C-12, C-13 |
| Outcome first: every deck starts with the operational outcome |
C-02, C-03, C-04, C-10 |
Success Measures
What the feedback form (C-16) should measure:
| Measure |
Question |
| Mindset |
Can participants describe Understand → Act → Create? |
| Value |
Can participants name the decision their app supports and its value? |
| Prioritization |
Do participants understand why a higher-value stream can win over a started one? |
| Knowledge |
Do participants see why agents need organizational knowledge, not only data? |