MAP is the operations platform for a motorsport team's factory, race team and office. Twelve apps, one set of records: how each assembly was built, what's on each car, how far every part has run, and the planning, purchasing, finance and people around it.
Overview
Each app is switched on for your installation by your licence key, and every licensed user gets every app on the licence. Admin and user management comes with every licence. Choose an app to jump to it.
Build sheets, sign-off queues, packing, shipments and turnarounds.
Serialised parts, car trees, mileage limits and service intervals.
Jobs at the track, assemblies to fit, Run Plans and returns.
Plan which build goes on which car, for every event.
Raise, assign and track jobs, with Part Care Notes.
Stock by location, a full movement ledger and stock counts.
Raise, approve and receive orders against your suppliers.
Routed manufacturing and service orders, materials and time.
Company Calendar, leave, capacity forecast and workload.
Reports, dashboards and a SQL workbench over MAP's data.
Ledger, payables, receivables, VAT, budgets and the cost cap.
Employment, leave balances, recruitment, training and payroll inputs.
How it fits together
The same records follow a part through every app it touches, so nobody has to type a serial number twice or reconcile two lists.
Factory
Every assembly gets a build sheet, stamped from your templates, that records the parts fitted by serial number, the questions answered and the checklists run. When the builder submits it, it moves through the sign-off stages its template needs, and every sign-off records who signed and when.
Service Teams sign their own stage alongside, before the last one.
Mileage Tracking
The Part Catalogue holds what a part is: its part number, race and test mileage limits and service intervals. Each physical part is its own serialised record, fitted in a tree on its chassis. Add mileage to a car and it flows down to every part fitted underneath, however deeply nested.
Trackside
Trackside gives the race team what they need during an event: what's fitted to each car, the jobs to finish before the next session, and what's going back to the factory. It works on a phone or tablet, so it goes wherever the team goes.
Allocations
Pre Allocation lays out each car's slots for an event: Mandatory, Optional and spare. Drop a build onto a chassis and its linked sub-assemblies follow it into their own matching slots, left and right hand respected. Mandatory slots stay flagged until they're filled.
Jobs, stock and manufacture
A lightweight ERP layer, there so that the movement of parts is recorded in the same system that tracks their build and their life. A serial number is created once, whether it arrives on a purchase order or comes off a work order.
Raise, assign and track the jobs that aren't build sheets, from "re-machine bracket" to "investigate vibration on car 2". Give a job an event and a chassis and it becomes a task for the race team at the track.
A stock catalogue with quantities at each stores location and an append-only ledger of every receipt, issue, transfer and adjustment. Serialised stock shares its records with Mileage Tracking.
Raise purchase orders against your suppliers and receive against them. Receiving a serialised part creates its record in Mileage Tracking at the same moment.
Manufacturing and service work orders, routed from operation templates and loaded with materials straight from a BOM. A build sheet raises its own work order automatically, unless you switch that off.
Resource Planning
Resource Planning brings the Company Calendar, leave, company holidays and a capacity forecast together, built on the same jobs and work orders as the rest of MAP, so the plan and the work never drift apart.
The office
The cost of a build and the hours behind it come from the same records as the build itself, so the office works from what the factory and the race team have already recorded.
Build reports and dashboards by dragging charts onto pages, and share them in workspaces. People who know SQL can query the same data in a read-only SQL workbench.
The books for each legal entity, fed by what MAP already records: journals, payables and receivables, bank reconciliation, fixed assets, budgets, and VAT returns and filings.
The person behind each account: employment over time, working patterns, leave balances, skills and training, recruitment, reviews, health and safety, event rosters and timesheets.
Admin
Day-to-day set-up happens in Admin, without code changes or restarts. It comes with every licence, whichever apps you choose.
Sign-in and security
Sign-in fits the way your organisation already works, and every action is checked against a named permission on the server, whatever the screen shows.
Any number of OpenID Connect or SAML 2.0 identity providers, such as Microsoft Entra ID, Google, Okta or Auth0, added in Admin with no code change or restart. Group claims can map to MAP permission groups.
Your identity provider creates, updates and deactivates MAP accounts as people join, move and leave, so nobody has to mirror group membership by hand.
Local accounts can add an authenticator app, with recovery codes, and an administrator can require it for everyone. Passwords need at least 12 characters, and an idle session signs out after an hour.
Every page and server action checks a named permission. Business areas are a hard boundary: a record in another area behaves as if it doesn't exist, in the app and through the API.
Sign-ins, sign-offs, settings and every Public API write are recorded with who, when, and the values before and after. Nothing in MAP can change or delete an audit event once written.
Bank details, employees' personal details, HR cases and authenticator secrets are encrypted by MAP itself (AES-256-GCM) under your installation's own key before they reach the database.
Integrations
The Public API and SCIM provisioning are licensed as add-ons for each installation. See pricing.
A versioned REST API (/api/v1), read and write, cursor-paged and described by an
OpenAPI 3 document. An OpenAPI 2.0 version imports straight into a Power Platform custom
connector. Each API key acts as one MAP user and can never exceed that user's permissions.
Provision MAP users from your identity provider, with their own bearer tokens. A SCIM delete deactivates the account and keeps its history.
Import and export Excel workbooks in many places, from stock to work orders, and print PDFs where paper still matters: build sheets, Run Plans and shipping manifests.
Deployment
Both options run the same software, with the same apps and the same features.
Install MAP on your own servers, with your data in your own PostgreSQL database. Your licence is signed, and MAP checks it on the server itself, so it runs with no internet connection at all.
No IT team to spare? We host your MAP installation for you, so there are no servers for your team to look after. Your people simply sign in from a browser.
Everyday use
Every page works on a phone or tablet. Add MAP to the home screen and it opens like an app; scan barcodes and QR codes with the camera when loading a shipment.
Set your company name, logo, colours and font in Admin. Your company name carries through to emails and exported files too.
A Help guide inside MAP explains how it works, with step-by-step how-to guides and help for each page.
After an update, each person sees the release notes for the parts of MAP they use, once.
Raise a support ticket from any screen. Each gets its own reference and is tracked in Admin, even if email isn't set up.
Light and dark themes, and a choice of standard, colour-blind friendly or high-contrast status colours.
How MAP is designed
MAP is shaped by subject-matter experts: people who build, inspect, plan and race. They describe what they need in their own words, try each change on a preview with sample data, and every change is reviewed before it goes into a release.
That's why MAP uses the words your team already uses, and why it's strict about the details that matter: a serial number is created once, every sign-off records who and when, and history is kept, never overwritten.
For IT and engineering
For the people evaluating how MAP is built as much as what it does.
A single-page React app built with Vite, talking to the server over a JSON API. The Inter typeface is served with the app, and the app makes no calls to third-party sites. The first download is kept under 154 KB of compressed script; the rest loads as pages are opened.
A Node.js service on Express that checks permissions on every request and handles OIDC and SAML sign-in and Excel and PDF files. Sessions are kept in the database, so several server processes can share the load.
PostgreSQL 15 or newer (16 recommended), through the Prisma ORM with versioned migrations. The audit table belongs to a separate database role, so MAP's own role can be refused permission to change or delete it.