Every CupixWorks 5.0 project has two halves in its menu. Apps is where people use the project. Admin is where the project is set up and kept in order, on six pages. This article explains how the six fit together; each page has its own article.
- Admin - Activity, Captures, Skeleton, Library, Work Areas and Configuration. Only admins see this half of the menu.
- Apps - the project's SiteViews and add-ons, for everyone on the project.
The six admin pages
| Page | What it is for | Article |
|---|---|---|
| Activity | The project's log: who did what, and when | Activity - the project's log |
| Captures | Every capture as a record: where it is, who took it, how far it has processed | Captures - every capture in the project |
| Skeleton | The built world: site, buildings, levels, where they sit, and what is attached to each | Skeleton - sites, buildings, levels and coordinates; Mount and publish |
| Library | Every design file, and the Design References taken out of them | Library - design files; Align Design References |
| Work Areas | Zones you draw: safety areas, inspection routes, phases | Work Areas - sets, areas and where they apply |
| Configuration | The project's own settings: profile, location, capture methods, integrations, viewers, note groups, members | Configuration - the project's settings |
How a project is built
A project is made of three things: a structure, some content, and the links between them. The structure is the Skeleton. The content is a set of Design References, taken from the design files you upload. Mounting attaches a piece of content to a place in the structure, and publishing lets the apps show it.
| Job | Where | What it produces |
|---|---|---|
| Describe the built world | Skeleton | Site, buildings, levels, and where they sit on the map |
| Bring in the design files | Library | Source files, processed and Ready |
| Extract Design References | the file's editor | Drawings and 3D BIMs, in Draft |
| Align them | the file's editor | References placed in the project's coordinates: Aligned |
| Mount them | Skeleton, or the Library | Each reference attached to the nodes it belongs to |
| Activate and publish | editor, Library, Skeleton | References approved, and switched on for the apps |
| Draw work areas | Work Areas | Zones for inspection, safety, phasing |
| Check readiness | Skeleton > Setup Status | What is done and what is missing |
Design References and their status
A Design Reference is not the file. It is the content taken out of a design file; the product shortens it to DR. A BIM file (Revit, Navisworks, IFC, SketchUp) gives exactly one 3D BIM, with its views, rooms, levels and grid lines inside it. A drawing file gives one Drawing per page or sheet you extract. A Work Area Set is a Design Reference too, and is mounted the same way.
A reference moves forward Draft > Aligned > Activated: extracted but not positioned; positioned; approved for use. Two more switches are not statuses: a reference is mounted to one or more nodes, and each mount is published or not.
| To do this | The reference needs to be |
|---|---|
| Mount it to a node | Aligned (or Activated) |
| See it in the Skeleton | Activated, and mounted to that node |
| See it in the apps | Activated, mounted to that node, and published on that node |
Setup Status - is the project ready?
Setup Status, in the Skeleton's header, answers is this project ready? It gives a readiness percentage with a pass / warn / fail count, the lifecycle above in the product's own words, a Project Summary, the project's coordinate frames, and further down each building with its own readiness.
The rule it checks: every building needs at least one reference that is Activated, mounted to it, and published there. Any kind counts; a floor plan will do. A building that fails has nothing for the apps to show, and reads Blocked.
- Readiness - how ready the project is, as a percentage, with the pass / warn / fail count on the right.
- DR Status lifecycle - Draft, Aligned, Activated, and the two switches that are not statuses: Mount and Node-Publish.
- Project Summary - how many buildings, levels, source files, DRs and work area sets the project holds.
- Hand Over to Customer - for a Cupix CSM who set the project up on your behalf.
Changes from 4.0
| In 4.0 | In 5.0 |
|---|---|
| One origin per project, so each building needed its own project. | Each building carries its own origin, so a campus fits in one project. |
| A different workflow for each file format. | One Library for every supported format. |
| A revised file meant re-uploading and re-aligning by hand. | A new version is recorded against the source file, and you choose when to apply it. |
| The same drawing uploaded once per floor. | One drawing mounted to as many levels as it serves. |
| Work areas belonged to a single level. | A Work Area Set is a Design Reference and can be mounted in many places. |
| A fixed admin sequence. | Jobs you do in any order, as the design files arrive. |
| One publish switch per file governed every location at once. | Publish is set per node, so one floor can be switched off without touching the others. |
| Captures, activity and project settings sat in different places. | All six admin pages sit together under Admin in the project's menu. |