Linked data
Tables, reference lists, records and their relations.
PROJECTBASE · PROJECT DATA
Linked project data in one working base.
Tables, records, relations, files and computed fields live with the project. Use different views for installation, purchasing, review and contractors without copying the source data.
PROJECTBASE · PROJECT DATA
Not a set of tables. A linked project structure.
A room, device, cable, document and specification item are separate entities. Links replace copying the same data into multiple journals.
Calculations
Formulas, lookup, rollup and dependent values.
Views and publishing
Filters, grouping, public views, CSV and PDF.
PROJECTBASE SCREENS
Data, relations and external output in one interface.
Four screens show the path from a row and record card to links and a prepared public view.
GRID
A table for daily work.
Rows, fields, statuses and values stay in one working set with a quick route to the record.
working table
RECORD CARD
A record stores data and work context.
A table row is only the start. The card opens every object detail and returns to the journal without losing the place.
-
Fields
Manual and computed record values.
-
Linked records
Routes to the room, device, cable and catalog.
-
Attachments
Files, photos and source documents.
-
Discussion
Questions and decisions about this record.
DATA MODEL
Not a set of tables. A linked project structure.
A room, device, cable, document and specification item are separate entities. Links replace copying the same data into multiple journals.
ENTITY RELATIONSA link leads back to the source record.
One record can appear in several views and be used in formulas, discussions and publishing.
- 01Room
Installation place and project relation.
- 02Device
An equipment item with parameters.
- 03Cable
Line, section and connection.
- 04Document
File, drawing or source material.
- 05Specification item
SKU, quantity and catalog record.
Linked records remain one source: a change to the source row appears in connected views.
FIELDS & CALCULATIONS
Derived values come from the linked model.
Input fields, record links and computed fields separate manual data from the result that can be checked.
- 01Linked records
Link a device to a room, a cable to a panel and an item to a catalog record.
- 02Formula
Calculate a value from row fields and an expression.
- 03Lookup
Pull an SKU, name or parameter from a linked record.
- 04Rollup
Aggregate quantity, sum or another value across linked rows.
A derived field does not become a manual value: source data and result remain distinguishable.
VIEWS
One base, different ways to work.
Configure visible fields, filters, sorting, grouping, column order and totals for each view. Roles get the slice they need without another table copy.
Fields
Hide service columns and keep the fields needed for installation or purchasing.
Filters and sort
Show the right records and order them by status, date or value.
Groups and totals
Group rows by room, phase or category and see totals.
Working mode
Save a view for the team, personal work or controlled external output.
A view changes how data is read, not the underlying table.
SYSTEM CAPABILITIES
The base grows with the project.
System bases and automation help the team avoid rebuilding every working structure from zero.
Import
Load a CSV after checking field mapping.
Public view
Share a selected view through a separate link.
CSV
Export view rows for further processing.
Fix a prepared view for delivery or archive.
Template base
A starting structure for a repeatable project type.
Reference base
Shared catalogs and records for linked bases.
Automation / scripts
Scripts for repeatable actions and data processing.
Custom base
Your own table, field and relation model for a specific operation.
Template and Reference speed up the start without changing ownership of project data. A public view is limited to the selected view; working fields and drafts stay out.
PROJECTBASE QUESTIONS
What to check before launch.
ProjectBase stores a linked model and prepared views. These boundaries matter for data, formulas and external output.
What is an SHD project base?
It is a working model of project tables, fields, views and linked records. Access and external output are configured separately.
Will a contractor see the whole base?
No. An external participant gets a separate view with selected fields, filters and permissions.
Can a formula be edited in a cell?
No. A formula is calculated by the system. A manual value belongs in a regular field so its source is clear.
What does ProjectBase not replace?
The base does not replace drawings or engineering documents. It stores data, relations and the work context around them.
PROJECTBASE LAUNCH
We will shape a base around the project work.
We will map current journals, catalogs, relations and external views, then build a structure the team can use every day.
Start with the tables and records you already have.