01 / OT to IT
Why plant data never reaches the cloud, and the boring fix that gets it there
Every site tells the same story. The historian holds a decade of data and nobody downstream can use a byte of it. The blocker is almost never bandwidth.
Otomatik Pty LtdPerth, Western AustraliaEst. 2024 Available Q4 2026
From the sensor to the ledger.
Engineering for the systems that never stopquietly hold uppay for everything
- 01 Cloud platforms and delivery
- 02 Data engineering
- 03 AI agents with real access
- 04 Control and connected systems
Otomatik is a small consulting practice working from the control system up to the cloud. Cloud platforms, data pipelines, AI agents, and the industrial systems underneath them, built by an engineer who has shipped on both sides of that boundary.
Shaped by work at
BHPFBRVerbrecRCTMechanical RockAustralian Finance Group
01 — Capability
Four disciplines, one head.
Every line below is work already shipped in production. Anything outside this list, we will say so and point you at someone better.
01
Cloud platforms and delivery
Serverless AWS architectures, multi tenant on day one, provisioned entirely as code. Pipelines authenticate with short lived OIDC credentials, so a deployment never depends on a shared key in someone’s terminal.
InfrastructureAWS CDK, Terraform
RuntimeLambda, API Gateway
IdentityCognito, Entra ID
DeliveryGitHub Actions, OIDC
02
Data engineering
Ingestion, modelling and governed sharing. On one platform this took client onboarding from three weeks down to 48 hours, with data refreshing every 15 minutes instead of overnight.
WarehouseSnowflake
TransformDBT
IngestFivetran
RelationalPostgreSQL, Drizzle
03
AI agents with real access
Context aware assistants wired to your own APIs, with an explicit limit on what they may change in a single turn. Useful enough to save real time, constrained enough to hand to staff.
ModelBedrock, Claude
ToolingMCP, tool use
TransportStreaming, SSE
GuardrailOne mutation per turn
04
Control and connected systems
PLC logic, HMI work, industrial protocols and edge provisioning. This is the half most software consultancies quietly subcontract, and the reason projects that cross the OT boundary tend to stall.
ControlAllen Bradley, IEC 61131
HMICitect, FactoryTalk
BusCANBUS, J1939, Modbus
SensingLidar, IMU, fusion
48hrs
Client onboarding, down from three weeks
15min
Data refresh interval, down from overnight
6
Engineers led on a distributed squad
8yrs
Across control systems, data and cloud
02 — The practice
Small on purpose.
No account manager in front of an offshore team. You brief the engineer, and the engineer writes the code.
LT
Leon Ticharwa
Principal Engineer & Director
BEng Computer Systems, Curtin University. AWS Developer Associate. Perth, Western Australia.
The two halves of industrial software are usually solved by two people who never meet.
Leon started at the hard end. CANBUS diagnostics and J1939 replay rigs, PLC logic in structured text to IEC 61131, HMIs for reclaimers and stackers on fixed plant, laser trackers and sensor fusion for robotics. When the code is wrong there, something physical stops moving. That sets a standard you carry into every project afterwards.
The second half came from data and cloud. Lead data engineer on a secure data sharing platform, then architecting the decomposition of a monolith into domain driven microservices for a national finance group, leading a distributed squad of six and putting behaviour driven testing in front of every release.
Leon Ticharwa
RolePrincipal Engineer & Director
FoundedOtomatik Pty Ltd, 2024
ExperienceEight years, industry side
CertificationAWS Developer Associate
EngagementDirect with the engineer
03 — Journal
Notes from the work.
Written during live engagements. Specific, occasionally opinionated, never produced in bulk.
02 / Architecture
Multi tenancy is an IAM problem, not a database one
Scoping every query by tenant id is the first wall, not the only one. What a per request scoped credential actually buys you.
03 / Data
From three weeks to 48 hours, onboarding clients with data shares
What changed when we stopped shipping extracts and started sharing governed views, plus the three assumptions that had to die first.
04 / AI
Agents that do the work, and the one mutation rule
A useful assistant needs write access. A safe one needs a hard limit on how much it can write per turn.
04 — Contact
Tell us what is broken.
A short call, an honest read on whether we are the right fit, and a scope you can act on either way.
Emailhello@otomatik.com.au
Phone0422 819 869
LocationPerth, Western Australia
EntityOtomatik Pty Ltd
ResponseWithin one business day