Multi- Artisan Jurisdiction Ecosystems

22-01-2024
Grant Ford

Up until now, Artisan has served BCAs with a single Artisan jurisdiction. This allows BCAs to create shotlists, set up projects and remotely assess building code compliance through Artisan's workflows. However, as Artisan use and confidence in its abilities have grown, BCAs and others have put Artisan to use in new ways.

There are now pure QA instances of Artisan and those instances can accommodate volume builder's entire franchise. The Franchisor/ HQ has a "Parent" Artisan Jurisdiction with multiple "Child" jurisdictions corresponding to each franchisee. This enables the entire franchise to develop new compliance "shotlists" for their particular building methodology, and continuously improve and share those shotlists with each individual child jurisdiction. The child/ local franchisee maintains their autonomy in setting up and quality-assuring their projects. The franchisor is able to look over the entire franchise through the parent jurisdictions' oversight abilities, compare quality and ensure performance across the franchises that share their methodology and brand. 

Ecosystem management through parent and child jurisdictions has also had applications for BCAs.  Factory builders and even volume builders with specific building methodologies are finding themselves served through Artisan child Jurisdictions that have 'shotlists' unique to their particular methodologies and needs.

The Artisan Mobile App accepts projects from any jurisdiction and is also evolving with ecosystem thinking to make it more obvious which jurisdiction; BCA or QA, a particular project has originated from and who the reviewing agency will be for it.

22-01-2024
Grant Ford
Ecosystem Admin Console