ALYORARMATURES
The operating system for rebar fabricatorsDesigned in Réunion
Every bar knows where it came from, what it must become and where it is going. ALYOR connects detailing, material, production, quality, delivery and management — without turning your teams into IT specialists.
Drag the bar to rotate it
01BBS and 3D shapessame mark, same revision
0212 roles · 72 permissionseach team sees its own workday
03Enterprise serverbusiness-controlled data and backups
04Audit trailuser, action, date and context
This is more than a bar.
In ALYOR, above all, it is one continuous history.
Demonstration scenarioSample data · real product logic
The quote does not disappear when the job begins. At each handover, R01 changes status, gains evidence and moves to the right person.
The accepted quote retains the customer, terms, estimate and planned margin. The job starts without re-entering its history.
Not 50 modulesOne clear question for every role
Margin remains on target, but machine loading pushes delivery back by 1.5 days.
BBS laboratoryGeometry makes the data understandable
The 3D view represents the recorded segments, arcs and bend radii. The schedule, dimensions, weight and revision remain synchronised with the same bar mark.
Drag to rotate · double-click to recenter
What the view doesRead and compare deterministic BBS geometry.
What it does not doInvent an ambiguous bend or replace detailing approval.
BIM / IFCPlacement in the structure remains separate from fabrication geometry.
Two workspaces. One job.Production and management no longer get in each other's way
Jobs and BBS, material requirements, purchasing, lots and heats, scheduling, machines, execution, quality, packing and dispatch.
Customers, quotes, orders, purchasing, invoices, payments and reporting remain clear without exposing the entire factory to every user.
CSV/BBS, EBP, IFC and machines are classified by status: available, controlled import or connector requiring qualification in your environment.
See the qualification method ↓Go-live mattersSoftware does not arrive on its own
ALYOR is configured around your roles, data and evidence. A machine is only declared compatible after its model, protocol and environment have been qualified.
Plan my deploymentSites, roles, data, risks and expected outcome.
Migration, permissions, server, backups and test environment.
Your jobs, documents, exception cases and restore procedures.
Each role learns its workday, not the system's 174 tables.
Phased rollout, adoption monitoring and exception handling.
Words with consequencesEvery promise carries a status
Import, validation, revisions and deterministic representation.
Receipt, quarantine, location, consumption and history.
Work orders, operations, inspections, decisions, packs and dispatches connected.
Every manufacturer, model, version and protocol must be tested.
Exchanges depend on your edition, data and agreed scope.
Acceptance by two workshops before any claim of certified production readiness.
No fake customer logos. No assumed compatibility. No “real time” without measurement. Read the trust centre →
The complete workflow is includedOnly scale changes
The complete business system, roles, updates and support tools.
The same complete workflow, with multi-site organisation and enhanced support.
For complex migrations, multiple entities or sensitive connections.
Prices are commercial starting points and exclude implementation. Term, hosting, support and conditions are confirmed in a signed proposal. This website does not take payment today.
Straight answersBefore changing how you work
ALYOR manages the rebar workflow and includes its own management workspace. An EBP exchange can be assessed, but availability depends on your edition and must be validated against your data.
No. Roles and permissions limit workspaces and actions. An operator can open their work order and next operation directly, while management retains the overall view.
No, and we do not claim that it does. A connection is qualified manufacturer by manufacturer and model by model, with its protocol, version, tests and fallback procedure.
The server deployment keeps PostgreSQL, documents and backups within the company's environment. A dedicated cloud option may be offered with explicit contractual responsibilities.
The engine is advanced, but a genuine industrial V1 requires signed acceptance tests, endurance testing, an independent audit and real machine qualifications. A version number must never replace evidence.