Anonymized architectural enterprise
Diagram understanding and delivery aids
Datawhale
Construction/engineering
Explicit FDE engagement
Standard case | Useful reference with remaining gaps
Evidence level A
POC / validating
A
Evidence level
Datawhale FDE Case 100 | No. 21: From manual drafting to intelligent collaboration in architectural delivery
Evidence level measures whether a source can be located and reviewed; it does not mean vendor-reported claims were independently audited.
Standard case | Useful reference with remaining gaps
7 / 12
Business context1 / 2
Transformation workflow / 2
Technical workflow2 / 2
Human roles & governance1 / 2
Measured outcomes1 / 2
Source traceability2 / 2
Remaining gaps: Business context, Transformation workflow, Human roles & governance, Measured outcomes
Business problem
The drawings and design materials are complex and the process of extracting, checking and delivering information takes time.
Solution
Multi-module understanding of drawings and documents supports extraction, checking, synthesizing and design delivery.
Technical architecture & production workflow
Step 01
Business Data/Documents/System Inputs
→
Step 02
Data cleansing and business semantics
→
Step 03
AI/rules are understood, matched or generated
→
Step 04
Final check or business rule check
→
Step 05
Manual handling of low confidence/high-risk matters
→
Step 06
Turns out to write back the original business process and continue to settle the feedback.
Key technology & infrastructure components
Enterprise data/documentsLLM/Semantic UnderstandingOperational rulesHuman-in-the-loopOriginal operational system
Human roles & accountability
Construction/engineering professionals retain design responsibility and security judgement.
FDE delivery actions
- Take a full workflow with the first line of staff and confirm the real bottlenecks, not just the required documents.
- Inventory of available data, permissions, system interfaces and hidden operating rules
- Dismantling tasks into AI, rules/traditional software, three types of human responsibility
- We'll start with a narrow scene, PoC, and we'll use real samples to verify accuracy and business value.
- Embedded to the original system and designed for abnormal upgrades, feedback and follow-up iterative mechanisms
Reusable delivery patterns
- HF, high-cost, verifiable narrow-flow selection
- Steps that can be validated with a certainty tool to prevent model self-assessment
- Retain manual responsibility for high-risk actions
- For each manual amendment to follow-up searchable context/rules
Business outcomes & delivery results
Reduction in time for duplicate inspections and documentation; indicators not made public.
Evidence boundaries & verification notes
- Public information confirming business processes; technical components are abstract architecture based on public description
- The source can be directly located in the case; the value remains disclosed by the source and does not represent an independent audit.