IETEL OS · Pass 5 vertical slice 1.1
Solution Design — IET-ASMT-2026-001
What IETEL proposes to build, and how we will later know it succeeded — consuming the Assessment output without re-asking any of it.
Prototype UI — nothing you change here is saved. Reloading the page resets it to the sample data.
Requirements & Assessment Summary
Reused from the Assessment Workspace, not re-entered — Capture Once, Reuse Many.
Observed- Business problem
- Warehouse and main entrance currently use shared brass keys — no record of who entered or when, and a lost key means rekeying the whole building.
- Operational objective
- Every entry logged per person, lost credentials revoked in minutes instead of a full rekey, and after-hours access restricted to approved staff only.
Operational requirements
- Every entry at the warehouse receiving door and main entrance must be individually logged.Critical
- Lost or terminated credentials must be revocable without rekeying the building.Critical
- After-hours access restricted to a named approval list.Critical
- A mobile-credential option would be convenient for office staff, but is not required for launch.Nice-to-have
Risks / Unknowns
- Rekeying constraint at the warehouse door if fire code requires free egress hardware.
- Warehouse-side power panel location not yet confirmed.
- Available network port at the warehouse door not yet confirmed.
Customer actions / Third-party actions
- Confirm employee roster source for credential issuance.
- Local fire marshal review for the warehouse door hardware change.
Design Decisions
Each module pairs what Assessment observed with what the design decides — the two stay visually distinct on purpose.
System Architecture & Components
System Components
Access Control Openings — Design Decisions
Power
Observed (from Assessment)
Design decision
Network / Controller
Observed (from Assessment)
Design decision
Cybersecurity
Observed (from Assessment)
Design decision
Assumptions, Exclusions & Design-Derived Actions
New items the design itself introduces — customer/third-party actions Assessment already found are shown in the Requirements summary above, not repeated here.
Design assumptions / exclusions
Customer actions (design-derived)
Third-party actions (design-derived)
Acceptance Criteria
Derived from Requirements + approved Design Decisions — not from Testing/Commissioning, which will consume these later.
For requirement: Every entry at the warehouse receiving door and main entrance must be individually logged. Critical
For requirement: Lost or terminated credentials must be revocable without rekeying the building. Critical
For requirement: After-hours access restricted to a named approval list. Critical
For requirement: A mobile-credential option would be convenient for office staff, but is not required for launch. Nice-to-have
Design Validation
An internal gate inside Solution Design, not a new lifecycle stage — the same 9 conditions from the real Design Validation decision point, consolidated into 6 checks.
Prototype logic only — a local browser-side check for this demo, not production enforcement.
Estimate Handoff Preview
What a future Estimate would receive from this approved design — not Estimate itself, which this slice does not build.
Approved Baseline Comparison
Pass 5 · Vertical Slice 4.1 — compares this live working Design against the Design Snapshot the current Approved Estimate Revision actually priced.