Solutions
These are the domains WorkKit delivers in, and the domains its knowledge base is built from. Each one carries specifications, rates, deployment processes and the standing assumptions that decide whether a project is profitable — the things that normally live in one person's head.
Sensor-driven and touch-driven experiences where the hardware, the content and the failure modes all have to be specified before anyone quotes a price.
In the knowledge base
Sensor and compute specifications, calibration processes, on-site commissioning time.
Large-format projection across irregular surfaces, where lumens, throw distance, blending and rigging determine both the design and the budget.
In the knowledge base
Projector and media server classes, blend and warp workflows, rigging and access assumptions.
Identity and interaction at scale — visitor journeys, access, personalisation and the reader network that has to stay up for the duration of an event.
In the knowledge base
Reader and tag selection, network topology, event-day deployment and handover processes.
Connected devices, show control and the network underneath them — the part that is invisible when it works and the entire project when it does not.
In the knowledge base
Gateways, PoE switching, edge compute, UPS sizing, structured cabling.
Permanent installations judged over years rather than days, where maintainability, warranty and spares matter as much as the opening night.
In the knowledge base
Warranty terms, standing exclusions, service and maintenance assumptions.
Visual proof
Not an illustration. Every quantity below is extracted from the proposal for a delivered event network, and the caveat under it is part of the record.
Worked example
8 doors · 16 UHF readers · 8 operator laptops · 2-day event · fully temporary
Client uplink
30 Mbps · single NATed connection
Portable rack case
Gateway router
VLANs · NAT
Core PoE+ switch
8 home runs
Edge server
reader ingest
UPS
mains interruption
one Cat6 home run per door · ≤ 80 m
Door 1
mini PoE+ switch, 5 port
Reader
Reader
Laptop
Door 2
mini PoE+ switch, 5 port
Reader
Reader
Laptop
2 × Wi-Fi 6 access point — staff devices only
deliberately off the critical path
This is one quoted configuration, not a reference architecture. The knowledge entry records it as stated for this event and refuses to generalise it — whether these quantities scale linearly with door count cannot be known from a single document. Figures extracted from the project proposal into knowledge/projects/rfid_event_network.
Most projects do not. The interesting ones tend to sit across three of these at once, which is exactly the case a spreadsheet handles worst.
