AECOSF
This is a post prompted by posts like The most open-BIM CDE and Continuous Integration in IFC Git repositories using IDS and validation.
Getting inspiration from @brunopostle here are a some thoughts on how an AEC Open Source Framework would look like.
Design LifeCycle:
1. Designer commits IFC (some_model_part.ifc) -> pushes branch feature/l2-floor-slab
2. Forgejo CI (Action) runs validation pipeline -> posts report as comment
3. Designer opens Pull Request -> feature/l2-floor-slab → shared
4. Assigned reviewers (discipline leads) review diff, comment, approve
5. If all required approvals met -> merge allowed → triggers “Publish” workflow
6. Forgejo Action exports validated IFC + COBie?
7. Forgejo creates a release artifact (with signed metadata and approval record)
Defect LifeCycle:
1. CI detects error or user creates issue -> Forgejo Issue (BCF) opened
2. BIM coordinator assigns to discipline lead -> Assignee + Label added
3. Designer fixes IFC and pushes new branch -> New PR linked to issue
4. Validator confirms fix -> CI passes, comment added
5. Reviewer closes issue -> Issue marked resolved
Validation stack (this is a huge one):
1. Schema & Syntax Validation -> openshell.validate
2. Geometry Validation -> Clash detection, duplicates, small gaps, etc.
3. Semantic / Information Validation -> IDS
4. Spatial Validation -> ?? Any tool to address this? Like elevatin levels ok, spaces are bounded or the like
5. MEP -> Any tool to verify ports/connections, etc?
6. Energy -> gbXML, OpensStudio/Energy+
7. Structural -> what simple tool vs FEM?
Communication: What tools? Mail/Whatsapp, etc?
Deployment: Multitenant/dedicated instance?
Your feedback is greatly appreciated.
Thanks!