1. Overview
Foundation
A good fabrication workflow is not simply about drawing faster. It is about maintaining control over
content, consistency, outputs, and the relationship between the model and downstream manufacture,
installation, and coordination. Strong fabrication workflows reduce confusion, improve repeatability,
and produce more dependable outputs.
Content control
Use the right items, the right services, and the right database from the start.
Workflow control
Move through modelling, numbering, spooling, and export in a deliberate sequence.
Output control
Reports and exports should reflect verified model information, not assumptions.
2. Workflow stages
Typical sequence
Typical fabrication workflow
- Set the correct profile and database
- Check services and content
- Model consistently
- Apply numbering rules
- Generate reports
- Define and create spools where needed
- Run exports and final outputs
Why sequence matters
- Early content mistakes spread quickly
- Bad numbering affects later reports
- Premature spooling creates rework
- Poor exports often reflect upstream issues
3. Content, services & database control
Start correctly
In fabrication workflows, setup quality has a major effect on downstream quality. Service templates,
service types, item folders, ITM content, and database control are all part of the workflow standard.
Profile & database
- Use the correct fabrication profile
- Check the active database path
- Avoid uncontrolled local edits
Services
- Use approved service templates
- Keep service structure understandable
- Do not mix temporary and approved content
ITM content
- Use controlled item content
- Keep folders organised logically
- Review patterns and item behaviour carefully
Warning:
If users start modelling on poor services or bad content, the workflow usually becomes inconsistent long before output stage.
4. Fabrication modelling practice
Model with outputs in mind
Fabrication modelling should support reporting, numbering, spooling, and installation understanding.
That means model decisions should be made with downstream use in mind, not only immediate drawing needs.
Good practice
- Use consistent item selection for similar conditions
- Model in a way that supports clean reporting
- Keep connectivity and logic clear
- Check coordination before committing too far downstream
What strong modelling supports
- Cleaner reports
- More reliable numbering
- Less spool rework
- Better communication to manufacture and installation
5. Numbering & reporting
Output logic
Numbering and reporting are not separate from the model. They depend on consistent content use and a
clear understanding of what should count as the same item versus a different item.
Numbering
- Agree numbering logic early
- Be clear about what makes items unique
- Avoid unnecessary variation in similar items
Reports
- Use standard report layouts
- Use reports to check quality
- Review outputs before issue
Consistency
- Match report needs to model behaviour
- Keep data clear and structured
- Check before bulk issue
6. Spooling workflows
Only when stable
Spooling should happen when the model is stable enough to justify it. If major coordination or content
changes are still expected, spooling too early often creates avoidable rework.
Before spooling
- Check content consistency
- Confirm numbering logic
- Resolve major coordination concerns
- Be clear on what scope is ready
Do not spool too early
- If content is still unstable
- If numbering rules are unclear
- If coordination is still changing heavily
- If spool boundaries are not agreed
7. Export workflows
PCF and other outputs
Export workflows such as PCF should be treated as part of the controlled fabrication process. Weak
exports often indicate weak model preparation rather than only a technical export issue.
Check before export
- Connectivity is correct
- The right items are selected
- The intended scope is clear
- Downstream naming/location rules are known
Good export behaviour
- Run small tests first
- Use standard naming and storage rules
- Treat export quality as part of QA
8. QA expectations
Check before issue
Fabrication workflows need QA at several stages: content setup, modelling consistency, numbering,
reports, spools, and exports.
Content QA
- Correct services
- Correct item content
- Correct database source
Model QA
- Consistent items
- Clear connectivity
- Resolved major coordination concerns
Output QA
- Reports reviewed
- Spools checked
- Exports validated
Final QA point:
Reports, spools, and exports are not just deliverables — they are also evidence of whether the model has been built in a controlled way.
9. Do / Don’t guidance
Quick reference
Do
- Use the correct profile and database
- Control service templates and item content
- Agree numbering logic early
- Model consistently
- Use reports and exports as QA checks
Don’t
- Let users invent their own service logic
- Start spooling unstable models
- Assume export issues are only command issues
- Ignore poor numbering consistency
- Automate broken standards
Final takeaway:
Strong fabrication workflows are built on controlled setup, consistent modelling, clear output logic, and disciplined QA.