Historical case summary / 02
Floorplan Automation Pipeline
Construction workflow automation · Deterministic rules · Reporting
Historical work led by Hugo Sequier before State Method · Client: BTP Consultants

Case overview
Problem and system
- Problem
- Technical controllers manually selected plan areas and ran geometric checks one by one.
- System
- The pipeline took in PDFs, extracted polygons, post-processed geometry, enriched metadata, ran rule-based PMR and fire-safety checks, and generated a report.
Evidence / linked source
Source-reported result
The canonical source reports a 30% productivity increase, 90,000 hours saved and approximately €2 million in economic gains in the project context.
Detailed baselines and calculation methods are not public. This result belongs only to the historical project context.
Canonical Floorplan Automation Pipeline case study ↗State Method relevance
Boundary, authority and review.
- System boundary
- The described workflow starts at PDF intake and ends with report generation. Extracted plan information is kept distinct from the deterministic geometric rules that produce checks for technical controllers.
- Human / control relevance
- Deterministic PMR and fire-safety checks hold a different role from plan extraction. The resulting report supports technical controllers rather than replacing their role.
Do not generalize
Context limits
- 01These results belong to the named historical project context.
- 02Detailed baselines and calculation methods are not public.
- 03The client did not contract with State Method, and this page does not imply endorsement of State Method.
- 04The result does not transfer to a different organization, plan class or workflow.