Artisan is fundamentally a data-centric planting design and specification system. Unlike workflows that begin with drawing objects and then attempt to derive planting information from them, Artisan begins with authoritative planting data sourced from centrally managed cloud libraries.
The workflow is therefore:
Central Plant Libraries → Project Palette → Design Placement → Reporting & Specification
Users begin by searching CloudScapes' centralised cloud-based planting libraries.
These libraries contain:
The cloud repository acts as the single source of truth.
Selected species are added to a project-specific palette.
The palette becomes the project's working planting dataset.
A palette may contain:
The palette acts as the design team's controlled selection of materials.
Design decisions are separated from graphic representation in CAD.
Planting data may exist before anything is placed on a drawing.
Once a palette has been assembled, items are placed into CAD drawings using Artisan labels.
Labels represent planting content within the design.
Planting quantities are determined dynamically according to planting type:
Quantity is derived from:
Quantity is derived from:
Quantity is derived from:
The drawing remains linked to the underlying full planting information.
As projects progress:
Artisan continuously synchronises:
Changes occur at the data level and propagate automatically throughout the project.
Reports provide the project's deliverable outputs.
Typical reports include:
Users can control:
Include or exclude:
For example:
For example:
Select precisely which data is displayed.
This is often summarised internally as:
Palettes → Labels → Reports
The philosophy remains identical, but the placement mechanism is BIM-based.
Create project palette from cloud-hosted plant libraries.
Project palette entries become:
Quantities are calculated automatically from:
Revit schedules are generated directly from connected palette data.
Summarised as:
Palettes → Model Components → Schedules
The defining characteristic of Artisan is not the drawing technology used (CAD or BIM), but the fact that the planting data model is primary.
The centralised cloud repository remains the authoritative source throughout the project lifecycle.
Users:
while maintaining synchronisation between:
This allows planting information, specification content, and reporting outputs to remain consistent as the design evolves through concept, planning, tender, construction, and delivery phases.
A concise internal summary might be:
Artisan is a cloud-connected, data-centric planting system where project palettes derived from authoritative plant libraries drive placement, quantification, specification, and reporting. In ArtisanAC/BC the workflow is Palettes → Labels → Reports; in ArtisanRV it is Palettes → Model Components → Schedules.