ShiftManager for air traffic control

The same facts, two readings. The CEO reads the top register and knows what was delivered. The CTO reads the bottom one and knows how. No one is forced to translate in their head.

The schedule was built in Excel, adjusted over email and paper diaries. Expired authorizations were caught, at best, by the human check before the shift. Last-minute changes traveled by phone, with no record of who approved what and when.

The planner sees the whole organization on one screen, moves shifts by drag-and-drop across sectors, and the Timefold solver (run as an isolated JVM service) builds valid options in a few seconds. PHP 8.3 serves the UI and the session, Node.js 18 exposes the planning API in TypeScript, MariaDB through Prisma 5 stores the model. Authorizations are checked against their validity dates per sector, instructor-trainee pairs respect the on-the-job training requirements, and every change leaves a trace in the audit trail. Browser push notifications travel via Service Worker over BullMQ/Redis. Security is calibrated to the critical perimeter: JWT with rotation, CSRF on hash_equals, bcrypt cost 12, cross-origin isolation headers.

1. 01PHP 8.3 · FPM
2. 02Node.js 18 · Express · TypeScript
3. 03Prisma 5 · MariaDB 8
4. 04Redis · BullMQ
5. 05Timefold Solver (Java)
6. 06Vite 5 · Service Worker
7. 07Nginx · PM2 · Let's Encrypt

1. Publicly verifiable

   This project's domain is private, not publicly exposed. The scores were measured on the client's production environment with Google PageSpeed Insights, Google's official tool, and can be re-verified under a confidentiality agreement.

2. Reference point

   The scores reflect the project's state at the moment of handover to the client (2025). The source code and infrastructure belong to the client afterwards, and the project may be modified, deactivated or migrated with no notice from us.

The weekly schedule is generated in seconds. An invalid shift cannot be saved; an expired authorization blocks it in the UI before it reaches the database. API under 80 ms at p50, contractual uptime of 99.9% on a dedicated VPS. Handover to production: 28 days from kickoff.

1. M.01Weekly schedule generationhours → seconds
2. M.02API median (p50)< 80 ms
3. M.03Production handover28 days from kickoff

1. [1]

   Lighthouse scores captured at 2025 on the client's production environment. Private domain, not publicly exposed.

2. [2]

   The source code and infrastructure belong to the client after handover. The scores, the stack and the metrics reflect the delivered state, not the current state of the project.

3. [3]

   The detailed technical documentation, the implementation logs and the test reports are archived in the internal Arcane Tech repository, available under a confidentiality agreement.