Module
SIAARU HR
Leave and skills judged against what the plant actually needs that week.
What it produces
- Employees with skills, proficiency and certification expiry, by plant
- Leave requests with an approval trail
- Skill cover per plant per week, so a leave approval can be judged against it
- Certifications lapsing before the work that needs them
A worked example
Plant B, week of 14 Sep — one CNC operator covered
3 of 4 CNC operators on approved leave
remaining operator's certification expires 11 Sep
→ approving the fourth request leaves the cell unmanned
Illustrative figures. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
Leave approval and skill cover are the same question asked twice. A skill held by four people with three away the same Tuesday averages out comfortable across the week and stops the cell on Tuesday, so cover has to be judged on the worst day in the window rather than the mean of it. Certifications complicate it further: somebody whose certification lapses on the eleventh is not available on the twelfth, whatever the roster says, and the roster is what the approval is usually checked against.
Opened by the administrator, the supply chain manager and the planner — what each of them sees first.
Said before you ask
What is not finished.
BETA rather than AVAILABLE. The engine judges cover the way a plant does — on the single worst day in the window rather than on an average across it, because a skill held by four people with three away the same Tuesday averages out comfortable and stops the line on Tuesday. A lapsed certification removes somebody outright rather than warning about them. No customer has yet run it against their own roster. Two things it deliberately does not do. It does not approve or reject leave: that decision involves a funeral, a visa appointment, and how many times this person has already been asked to move a holiday — none of which is on file here, and a module that answered anyway would be wrong about something human and rightly never trusted again. And half-days are not modelled, because the leave record does not model them and modelling them badly is worse than not modelling them.
Where this sits
One of 16 modules, on one engine.
SIAARU HR reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 15 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.