Vision Example¶
Purpose¶
This section contains the completed ES-101 — Vision and Problem Definition example for the LMU Campus Operations and Incident Coordination Platform.
This is the business setup for the entire LMU/COICP example repository. It explains why LMU would fund the work, what operational problems matter, which business priorities should shape engineering decisions, what must remain out of scope, and which concrete university scenarios will flow through Requirements, Planning, Architecture, Design, Implementation, Integration, Testing, Release, Operations, Deployment, Monitoring, Stewardship, and Governance.
Vision context¶
| Field | Value |
|---|---|
| Vision baseline produced | LMU-COICP-VISION-001 |
| Requirements baseline expected next | LMU-COICP-REQ-001 |
| Planning baseline expected later | LMU-COICP-PLAN-001 |
| Architecture baseline expected later | LMU-COICP-ARCH-001 |
| Design baseline expected later | LMU-COICP-DES-001 |
| Implementation baseline expected later | LMU-COICP-IMPL-001 |
| Integrated baseline expected later | LMU-COICP-INT-001 |
| Release candidate expected later | LMU-COICP-RC-001 |
| Downstream release posture | Internal engineering review only |
| Planned downstream review environment | LMU-COICP Internal Engineering Review Environment |
| Planned downstream dataset | Spring Semester Synthetic Incident Dataset |
| Planned downstream synthetic records | 421 |
| Planned downstream reviewer accounts | 24 |
| Planned downstream review window | March 18–22, 2026 |
| AI Incident Summary | Deferred / disabled |
| Operational pilot | Not approved |
Business case in one paragraph¶
LMU needs a shared, evidence-preserving coordination workspace for selected non-emergency campus operations issues because current coordination across email, phone calls, chat messages, spreadsheets, local tickets, and personal notes does not reliably preserve ownership, status, handoff rationale, or reviewable evidence. COICP is intended to improve coordination and learning for bounded campus operations scenarios without replacing emergency response, official records systems, or accountable human judgment.
Initial business scenario set¶
| Scenario ID | Business Scenario | Business Problem | Vision Role | Downstream Lineage |
|---|---|---|---|---|
| COICP-SYN-001 | Information Commons ceiling leak near public printer area | High-traffic student space has a facilities issue that must be recorded quickly and handed to the right group without creating duplicated email trails. | Baseline intake and evidence scenario. | Vision business priority → FR-001 → Planning WP-002 → Architecture create flow → Design IF-001/WF-001 → Testing TC-001 |
| COICP-SYN-118 | Damen Hall water leak affecting evening student event setup | Campus Operations must hand off responsibility to Facilities before an event while preserving ownership, timing, and rationale. | Primary handoff and evidence scenario. | Vision handoff priority → FR-002/FR-004/FR-005 → Planning WP-003 → Architecture evidence flow → Design IF-002/WF-002 → Testing TC-005/TC-007 |
| COICP-SYN-204 | Residence hall exterior door access issue at Mertz Hall | Residence Life needs visibility into its assigned scenario without unrestricted access to unrelated operational records. | Access-control and least-privilege scenario. | Vision confidentiality priority → FR-006 → Planning WP-004 → Architecture Access Control Service → Design access matrix → Testing TC-004/TC-011 |
| COICP-SYN-219 | HVAC outage affecting three evening classrooms in Cudahy Science | Facilities must track status and closure rationale for classroom-impacting mitigation. | Status and closure scenario. | Vision continuity priority → FR-003/FR-011 → Planning WP-005 → Architecture state/evidence flow → Design WF-004 → Testing TC-006 |
| COICP-SYN-322 | Emergency-related safety concern mistakenly entered as COICP item | Campus Safety must ensure COICP never becomes emergency dispatch or emergency notification workflow. | Boundary and prohibited-use scenario. | Vision safety boundary → FR-012/C-001 → Planning WP-006 → Architecture policy boundary → Design WF-005/ERR-003 → Testing TC-012 |
| COICP-SYN-407 | Wi-Fi disruption affecting scheduled class check-in in Mundelein Center | Campus Operations and IT need coordination visibility without turning COICP into enterprise IT service management. | Optional ownership/handoff extension scenario. | Vision scope-control priority → FR-002/FR-004/C-009 → Planning WP-007 → Architecture optional extension → future testing |
Recommended workflow¶
Problem Statement
↓
Vision Statement
↓
Stakeholders
↓
Scope
↓
Assumptions
↓
Success Metrics
↓
Vision Readiness Summary
↓
ES-102 Requirements and ConstraintsRepository location¶
docs/examples/lmu-coicp/vision/
In a project workspace, the comparable evidence would normally live under:
docs/project-workspace/vision/
Example set¶
Problem Statement
Define the LMU business problem, operating pain, and concrete scenario evidence before proposing a solution.
02Vision Statement
Describe the desired university operating future, business objectives, priorities, and trust expectations.
03Stakeholders
Identify executive, business, operational, engineering, support, governance, and affected stakeholders.
04Scope
Set business scope, scenario scope, exclusions, deferred work, and prohibited uses.
05Assumptions
Record assumptions about adoption, data, roles, evidence, AI disablement, and internal engineering review.
06Success Metrics
Define business, operational, engineering, trust, governance, adoption, and educational success signals.
07Vision Readiness Summary
Summarize readiness to begin ES-102 Requirements with a concrete scenario handoff.
ES-101 establishes the business case and direction. It does not approve operational pilot, production use, real campus incident handling, AI Incident Summary, emergency response, sensitive-record processing, or autonomous decision-making.