This page is the online register under Article 26(b) of Regulation (EU) 2023/2854 (the Data Act). Frontier Solutions hosts the register. It describes the structures, formats and specifications for exportable project data from Taktbygg. It does not describe the internal database. It contains no customer data and no secrets.
The service agreement refers to this page. A copy of the register, as it stands on the day an export package is delivered, is included in that package. The copy does not replace this page.
1. Record types
Each record has a stable id. A child record refers to the parent record’s id. Every field in the table is present on each record of that type. If a value is absent, the field is null in JSON and empty in CSV. Field names are the same in every language.
| Record type | Files | Fields | Relation |
|---|---|---|---|
| Project | project.json, project.csv | id, name, description, start_date, end_date, takt_length, time_resolution, week_anchor | No parent record. |
| Plan | plans.json, plans.csv | id, project_id, name, description, revision, scale, drawing_path | project_id is the project id. drawing_path points to the drawing file. |
| Zone | zones.json, zones.csv | id, plan_id, code, name, description, type, floor, area, sort_order, geometry | plan_id is the plan id. geometry is a GeoJSON geometry object. |
| Activity | activities.json, activities.csv | id, zone_id, contractor_id, title, description, type, status, week, hour, order, planned_staffing, actual_staffing, dependency_ids, tags, hindrance_category | zone_id is the zone id. contractor_id is the contractor id. dependency_ids are ids of other activities. |
| Comment and hindrance note | comments.json, comments.csv | id, activity_id, text, type, reply_to_id, mentions, attachment_paths | activity_id is the activity id. reply_to_id is the id of the comment being replied to. attachment_paths point to attached files. |
| Contractor | contractors.json, contractors.csv | id, project_id, name, organisation_number, contact, trade_category, emails, roles | project_id is the project id. |
| Progress | progress.json, progress.csv | id, project_id, contractor_id, week, staffing, reconciliation_lines, contract_amount, deductions | project_id is the project id. contractor_id is the contractor id. contract_amount and deductions are amounts the customer has entered. |
| Authorised user | users.json, users.csv | id, project_id, name, email, role | project_id is the project id. Passwords, sessions and other sign-in secrets are not included. |
| File manifest | files.json, files.csv | id, path, original_format, linked_type, linked_id | linked_type is plan, activity or comment. linked_id is that record’s id. The file is provided in its original format. |
2. Formats and specifications
- Structured data is provided as UTF-8 JSON (RFC 8259) and as UTF-8 CSV (RFC 4180), with the same records, one file per record type.
- Dates and times use ISO 8601.
- Zone geometry uses GeoJSON (RFC 7946). In JSON,
geometryis a geometry object. In CSV, the same GeoJSON is text in the cell. - A list, such as
dependency_ids,tags,mentions,attachment_paths,emails,rolesandreconciliation_lines, is a JSON array. In CSV the same values are separated by semicolons in the cell. Quoting follows RFC 4180. - Uploaded project files are provided in the format in which they were uploaded, together with the file manifest.
- No harmonised standard and no common specification for this service type have been published. Until one is published, the formats on this page are those used for the export under Article 30(5).
3. What is not included
Source code, algorithms, interface design, internal calculation fields and platform logs are not included. The register does not cover the internal database.
4. How the package is delivered
This page is not a programming interface to the service. The customer, or a destination provider the customer names in writing, requests the package in writing. Frontier compiles it and delivers it by a time-limited link to private object storage, or directly to the recipient’s device. It is not sent as an attachment in service email. Software can read the delivered files. That is reading the package, not a call to the service. The terms are in section 11.8 of the service agreement.