CASE STUDY / INTERNAL OPERATIONS
Know where every resource is. Know what happened to it.
ERIS gives regional responders a single operational view of equipment availability, reservations, dispatch movements, returns, and audit history.
ERIS — EMERGENCY RESOURCE INFORMATION SYSTEM · REGION 10
THE LIFECYCLE
Resources move. ERIS remembers.
Every resource follows an accountable state from inventory readiness through reservation, dispatch, return, and reporting. Click a state — or play the whole lifecycle.
RESOURCE / GEN-092
SIMULATED
- STATUS
- DISPATCHED
- LOCATION
- Municipality 07
- ASSIGNED TO
- Incident #2041
- LAST MOVEMENT
- 14:32
- NEXT EVENT
- Return pending
- Resource is in the field
- Movement recorded
- Operational state active
MOVEMENT HISTORY
14:32
RESOURCE DISPATCHED
Incident #2041
13:48
RESOURCE RESERVED
Municipality 07
12:03
INVENTORY VERIFIED
Generator GEN-092
THE SHIFT
From scattered records to one accountable state.
BEFORE
AFTER — ERIS
REGIONAL VISIBILITY
One region. A live picture of resource readiness.
Select a municipality to see its operational picture — availability, reservations, dispatches, returns.
REGION 10 — SIMULATED
MUNICIPALITY 03
- AVAILABLE
- 5
- RESERVED
- 2
- DISPATCHED
- 4
- RETURNING
- 1
ARCHITECTURE
One accountable state, across the whole system.
Dashboards, reservations, and reporting all read and write the same operational state — Laravel underneath, with MySQL, role-based access, and backups.
ACCESS
The same resource. Different responsibilities.
Pick a role to see what it can do — access follows operational responsibility.
ACCESS — COORDINATOR
- ✓View available resources
- ✓Reserve resources
- ✓Dispatch resources
- —Manage state & permissions
- —Review movement history
WHAT SHIPPED
The operational scorecard.
- RESOURCE VISIBILITY
- Availability visible across municipalities.
- DISPATCH ACCOUNTABILITY
- Movement history preserved.
- RETURN TRACKING
- Resource lifecycle remains traceable.
- AUDITABILITY
- State transitions remain reviewable.
- REPORTING
- Operational information surfaced for reporting.
MY ROLE: Product architecture, development, and QA for critical workflows
ENGINEERING LOG
The problems worth solving.
01
RESOURCE STATE
PROBLEM
How do you prevent resource state from becoming inconsistent across reservations, dispatch, and returns?
DECISION
Centralize the operational state, with movement history baked into the data model.
02
AUDITABILITY
PROBLEM
How do you preserve an accountable history of resource movement across municipalities?
DECISION
Record state transitions as part of the operational workflow — accountability isn't an afterthought.
03
ACCESS CONTROL
PROBLEM
Different municipalities and operational roles need different access to the same resources.
DECISION
Role-based access built around operational responsibilities, not just permissions.
SYSTEM
The technical map.
INTERFACE
Vue · Inertia
APPLICATION
Laravel
DATA
MySQL
OPERATIONS
RBAC · Backups · Reporting
When operational data needs to stay accountable.
I build internal systems that turn fragmented operational workflows into reliable, traceable software.
RELATED SERVICES