--- title: "Platform · SystemTracker" description: "Bring every part of your project together. Plan the work, see how it connects, and turn project knowledge into better decisions with people and AI." url: https://systemtracker.com/platform/ lang: en --- # Bring every part of your project together. Give every team a shared view of what matters. Plan the work, see how it connects, and turn project knowledge into better decisions, with people and AI working from the same structure. ### Plan Systems, components, the work on them, the people and their AI: everything that runs a project, today. ### Visualize 2D drawings, a connected work canvas and BIM, every system in view where it is. ### Intelligence Dashboards and data views from live project data, shared with anyone, and the learnings of every project. ## Plan Everything that runs a project, on one structure: in four parts. ## One structure. The whole project connected. Connect systems, people and project data from day one. Every requirement, test and decision adds to a shared picture that the whole team and their AI can work from. ### Every system becomes a shared workspace. Open any system and see the work, documents and conversations that belong to it. One connected history, from the first requirement to operation. “Build the system list for Building B from these tender documents.” #### Your code standard NS 3451, TFM or your company’s own codes, from the first day. #### One tree, every level From chapters down to single components, with what is under each in view. #### No loose ends Every piece of information belongs to a system, so it is always found where it should be. ### One TFM master for every component type. Component types, TFM codes and what each type needs, kept once for the whole project and attached to the systems they serve. “Which component types have no checklist template yet?” #### Tags that match the site TFM tags follow the project’s pattern, so the labels on site, in the model and in the O&M files agree. #### Types carry what they need Requirements, checklist templates and required documents, set once per component type. #### BIM object sync, coming Match model objects that carry the same component codes, and keep them in step. ### Every system in its place. Buildings, floors and rooms in one tree. Place a system or a component, and its location goes with it, so everyone on site knows where to find it. “Place every system on Plan 2 of Building B in its room, from the drawings.” #### Places inside places Buildings, floors, rooms and areas, nested as deep as the project needs, in the order you drag them into. #### What is where Each place shows how many systems and components sit in it, and in everything below it. #### The location beside the code A placed system carries its location, such as +Bygg B/Plan 2, wherever it shows up. ### Every requirement, with its full history. Requirements written on the systems, components and integrations they govern, with every change shown in redline: who added what, who removed what, and when. “What changed in the ventilation requirements since the tender?” #### Where they apply On the system, component type or integration they govern, not in a separate binder. #### Redline history Compare revisions, with every addition and deletion signed by person and company. #### Always the latest revision The team and their AI automatically work from the latest revision. Earlier versions stay available, with every change in context. ## The work, on the systems it belongs to. Progress, checklists, integrations, responsibilities, documents, punch items and scheduling, each tied to a system or a component. ### See every system’s maturity at a glance. Every system through your phases and MMI levels on one grid, from basic information to operation, across every company on the project. “Which systems in Building B are still below MMI 400?” #### Your maturity model MMI and FMI out of the box, or your own phases and levels. #### Progress lives on the system Not in a status report. Update the system and everyone sees it. #### Filters that match the site By chapter, location, company or phase, top-down or one system in depth. ### Tests and inspections, prepared once and signed off everywhere. Checklists from templates or written with AI, each with a builder, a performer and QA, followed from draft to approved on the system it belongs to. “Create functional test checklists for every AHU, based on the requirements.” #### Roles built in Builder, performer and QA on every checklist, so nobody signs off their own work. #### Evidence attached Protocols, photos and measurements on the item they prove. #### Templates and AI Start from a template, or let your AI draft them from the requirements. ### Every interface between systems, specified and tested. The interfaces between trades, alive: each integration links two systems, carries its own specification and owner, and gets tested, so nothing falls between companies. “Read the fire strategy and create every integration it implies.” #### Specifications with revisions Write the interface once. Every change is a new revision, not a new email. #### Integrated tests Checklists per integration, with the result on both systems. #### Both sides, one click Jump between the two systems an interface connects. ### Who does what, per system, per company. A living responsibility matrix: companies as groups, roles as codes and people on systems, carried down the tree so nothing is left unassigned. “Set up the responsibility matrix from this contract appendix.” #### One group per company Access, interfaces and invitations follow the company. #### Carried down Assign once on a chapter, and every system and component below inherits it. #### Plan before they join Placeholders for people who are not invited yet. ### The documentation matrix that shows what is missing. Every document filed per system and NS 3456 category, with revisions and status codes, so the documentation is complete before anyone asks. “Sort these O&M files into the right systems and categories.” #### Requirements per system The matrix says what each system needs, from day one. #### Revisions and status codes Know which version is current and whether it is approved. #### Sorted by your AI Upload a folder and your AI files every document on its system and category. ### Defects that close, not linger. Punch items pinned to systems and components, assigned to the responsible company, prioritised and tracked to done. “Turn these walk-through notes into punch items.” #### Priorities your way Name and colour your own priority levels. #### Assigned by responsibility Punch items go to the company that owns the system, never to the wrong trade. #### Overdue, automatically Open, in progress, completed, and overdue the moment the date passes. ### Plan tests with dependencies that respect reality. Put checklists on a timeline, link what depends on what, and see what is unscheduled before it becomes late. “Plan the fire scenario tests for week 42 in the right order.” #### Dependencies Sprinkler flow switch before fire alarm, fire alarm before AHU stop. #### Nothing unplanned in hiding Every checklist is on the plan or on a backlog you can see. #### Days to months This week’s tests or the whole commissioning phase. ## Everyone finds the same answer. Chat, search and the Log keep every conversation, answer and change where the whole team can find them, their AI included. ### A conversation on everything. Chatrooms for the project, direct messages for quick questions, and a thread on every system, checklist, document, integration and punch item, with the history kept for whoever comes next. “Summarise everything said about =365.001 this month.” #### Chatrooms and direct messages Rooms for the project, a trade or a week of commissioning, and anyone one click away. #### Tag anything Mention people and tag systems, documents or punch items. Tags become links, and links become history. #### Threads on the work Every system, checklist and punch item has its own conversation. ### Find anything on the project in seconds. One full-screen search across systems, components, documents, checklists, punch items, conversations and people. Press ⌘K anywhere and go straight there. #### Everything in one box Systems, TFM tags, documents, checklist items, punch items, messages and people. #### Filter in a keystroke Narrow to one kind of result without leaving the keyboard. #### Opens in context Every result opens where it lives: the system, the checklist or the conversation. ### Every change, on record. Who changed what and when, on every system, whether it was a person or an AI. Open any system and read its full story. “What changed on =562.001 in the last 30 days, and who changed it?” #### The full story Every system’s history in order, from the first sketch. #### People and AI, told apart Every change made by an AI is marked as AI. #### Yours to keep The record goes with the building, not with the contract. ## Set up the way your project works. Project settings, exports and your own AI, so SystemTracker fits your company instead of the other way round. ### Shape the project to how you work. Modules, steps, code standards, statuses, priorities, role codes and locations: set them up for the project, and change them mid-project without losing anything. “Set up this project like our last hospital project, with NS 3451 and TFM.” #### Your phases and levels Rename, add and reorder steps, with the levels inside each. #### Your codes and colours Document statuses, punch priorities and role codes, named the way your team says them. #### Change it any time Everything already in the project keeps its place. ### Take everything out. Any time. One click. Export any part of the project in the structure you built: PDF, Excel, or a ZIP that mirrors your system tree. No asking, no fees, no lock-in. “Which systems would arrive as empty folders in the handover ZIP today?” #### In the structure you built Every export follows your system tree, so the files make sense without SystemTracker. #### Every list, in system order Systems, components, integrations, responsibilities and punch items, in Excel. #### Gaps you can see Anything missing in your data shows up in the export, from documents and checklists to responsibilities and punch items, before anyone else spots it. ### Every module, open to your AI. Connect the AI you already use. It works in every module through MCP, with your access, and every change it makes is marked as AI. Bring your own agents and the workflows you have built. No AI tokens to buy from us. #### Your assistant, your choice Bring any MCP-ready assistant or agent, and swap any time. #### Your permissions, no more It sees and changes only what you may. #### Marked as AI Everyone sees what was done by an AI, and on whose behalf. ## Visualize See every system where it is: on the drawings, on the model and on one canvas the whole team works on. - 2D drawings that know your systems - A connected work canvas - BIM, connected to every system ## Intelligence Ask for the numbers you need. Dashboards and data views from live project data, shared with anyone, and the learnings of every project. - Dashboards from a prompt - Shared with the team, and outside - A platform for what you learn ## Let every project make the next one better. We are building organisational intelligence: find the people who make a difference, understand the patterns across projects and put shared experience to work. ### Learnings Get insights from earlier projects, connected to the decisions, tests and results behind them. Test the fire dampers against the fire alarm before the full-scale test. ### Keep experience in the company. Preserve why decisions were made and what happened next, even when people change roles or a project ends. Why we tested the interfaces earlier. ### Find the people who move projects forward. Discover strong teams and companies, recognise the people who help others, and bring their experience into new projects. ### Spot recurring problems earlier. Find patterns in delays, test failures and product issues across projects, with the context needed to understand them. ### Carry good practice further. Find what successful projects have in common and share proven approaches across teams, projects and countries. ### Plan with better evidence. Compare tender assumptions and forecasts with actual delivery. Use the differences to improve the next estimate and plan. Illustrative previews of upcoming features.