Industries

One core. Fifteen industries. 712 specified use cases.

WillowCreek is one industry-agnostic core plus configuration-only industry packs. A pack is terminology, dashboards, workflows, reports and default rules on the same engines. It's never new code. That's why one platform can serve fifteen industries without becoming fifteen products.

How a pack works

Same platform, your vocabulary

Seven universal roots

Every pack relabels the same seven platform roots: Person, Zone, Worker, Site, Equipment, Campus, Controller. A Patient in a hospital, a Resident in aged care and a Prisoner in a correctional centre are one root wearing the industry's own words.

Five questions, everywhere

Every pack answers the same five operational-awareness questions: where is it, what is happening, is it safe, does someone need to respond, and can the response be automated.

Configuration, never code

A pack changes what the platform is called and how it is worked, not what it is. The engines underneath (safety, location, rules, escalation, reporting) are identical in every industry.

One rule no pack can bend: a pack can never suppress, delay, downgrade or acknowledge a life-safety notification. Whatever the industry, duress behaves the same way: priority one at origination, escalated until a human acknowledges, and never gated by licence or commercial state.

The solution packs

Twelve more industries, specified in full

Each solution pack is a written catalogue of use cases, terminology, workflows and compliance templates for its industry. Every one is specified and mapped to the core engines that would deliver it. None of them runs today, and each pack page carries its whole catalogue so you can see exactly what was scoped rather than a summary of it.

The catalogue idea

The whole menu, visible from day one

Every pack is specified as a selectable catalogue of use cases, fifty in most industries and 712 across all fifteen, each carrying its own identifier so it can be scoped and tracked. A customer enables the subset they need and inherits the rest as latent capability on the same tags, the same infrastructure and the same core engines. A hospital that starts with staff duress already holds the wiring for asset search; a terminal that starts with pedestrian proximity already holds the wiring for muster. A vertical is never reduced to its wedge capability.

And because the packs share one core, the strongest use cases recur everywhere: mobile duress, evacuation muster, lone worker, vehicle–pedestrian proximity, asset search, incident replay. See the cross-industry use cases →

Start with your industry

Tell us the vocabulary your floor already speaks. We'll walk the platform in it.