The Reports, Workflow, and Operations surfaces are the scaffolding the rest of the JMS hangs on: the Workflow Runner and Designer (every multi-step process), Threat Assessments (the case-management surface), Staff Management and Time Clock, Asset Tracking, Evidence & Property, Patrol Map, Field Operations, and Reports (Sales Tax and beyond).
What it does
- The Workflow Runner executes any multi-step process — intake, release, medical screening, disciplinary, investigation — with attribution and timestamping at every step.
- The Workflow Designer lets administrators build new workflows; the Scheduler runs them on a recurring schedule.
- Threat Assessments are the case-management surface — open, classify, evidence, decision — backed by the canonical ThreatAssessmentCase model (real case ids 1, 2, 3, not fictional 7xxx/9xxx that the FK rejects).
- Staff Management and Time Clock cover roster, shift assignments, and timekeeping. Asset Tracking and Evidence & Property cover physical inventory and the chain of custody.
- Patrol Map and Field Operations support patrol-side staff with live unit positions and assignments.
- Reports/SalesTaxReport is the first of many — an extensible reporting surface where future reports plug in.
How it works
The Workflow Runner is a single execution engine; every named workflow is data, not code. New workflows are designed in the Designer and run by the Runner. Threat Assessments are workflows of a specific shape with mandatory case-id linkage. Staff, asset, and evidence surfaces share the same Manager/DataConnection patterns.
Data captured
- Workflow definitions and per-run execution traces
- Threat Assessment cases with severity, evidence, decisions
- Staff records, shift assignments, time-clock punches
- Asset and evidence inventory with chain-of-custody log
- Patrol unit positions and assignments (for patrol-equipped sites)
Compliance & retention
Workflow execution traces are retained per the originating process’s retention class. Threat Assessment cases follow case retention rules. Staff records follow employment-records retention; evidence records follow chain-of-custody retention. The same audit-log pattern covers them all.
The part about threat assessments being baked into the workflow runner is exactly what we’ve been missing — right now our deputies are bouncing between three different systems just to flag a high-risk intake. Does this tie directly into the booking module or is it a separate module that has to be configured independently?
The workflow runner piece is what caught my eye — we’ve been doing threat assessments manually on paper and it’s a nightmare trying to track follow-ups across shifts. Would love to know if this integrates with existing JMS booking records or if it runs as a standalone module.
The mention of threat assessments integrated right into the workflow runner is what caught my attention — we’ve been juggling three separate systems for that and it’s a headache every shift. Does the evidence module tie directly into the reporting side, or is that still a manual export situation? Really hoping this is the consolidation we’ve been waiting for.
We migrated to a new JMS last spring and the reporting module was honestly the biggest headache — half our deputies had no idea how to pull custom date-range reports without calling IT. Curious whether your workflow runner has a way to surface those commonly-used report templates right on the dashboard so staff aren’t digging through menus. That alone would save us probably an hour a day across the shift.
We’ve been struggling with getting our threat assessment data to actually connect with our daily ops reports — curious if the workflow runner here handles cross-module triggers or if those still have to be configured manually. Real pain point for us right now.
Glad someone is finally laying out how these pieces connect — we’ve been running threat assessments completely separate from our evidence tracking and it’s been a nightmare come audit time. Does the workflow runner allow custom triggers based on classification changes, or is that still a manual step? That one feature alone would save my staff hours every week.