HVAC/R contractors
MEP contractors and design-build firms, typically 20–500 people.
HellCold product line
APS × Business Centralfrom model to margin
Five extensions for MEP companies connecting Autodesk Platform Services with Microsoft Dynamics 365 Business Central — replacing manual re-entry with connected workflows.
05
product extensions
01
shared HC APS Core platform
BC
Business Central as ERP
MEP
HVAC/R, fabrication and service
Who it is for
Built around MEP workflows
BC + Autodesk
Teams using Business Central alongside AEC Collection / Forma.
Data without re-entry
Budgets, fabrication, asset handover and service in connected workflows.
ISV portfolio
Five products. Five specific workflows.
A shared integration platform reduces duplicated effort across future extensions.
01 / 05
HC BIM2Job
A new Revit model version updates the project budget in BC. Estimators review and approve changes instead of re-entering quantities.
Problem addressed
Estimates and WBS are re-entered from the model into the ERP.
- Buyer
- Operations director, estimator
- Validated by
- BIM / Design & Build
AEC Data Model: GA (read)
How it works
- 01A Forma Data Management webhook detects a new model version.
- 02AEC Data Model reads MEP elements and their quantity parameters.
- 03Rules map category, type and parameters to an Item / Resource and Job Task in BC.
- 04BC shows differences from the previous version; approval creates a Budget Job Planning Lines revision.
Product building blocks
- HC APS Model Version
- HC APS Element Link
- HC BIM Mapping Rule
- HC BIM Quantity Diff
- Quantity review page and HVAC WBS templates.
Value
MEP mapping rules, model-to-budget comparisons, and traceability from model element to budget line.
Constraint / to validate: Requires a Revit model published in Forma Data Management. The Lite IFC / schedule import path is a separate scope.
02 / 05
HC PrefabFlow
Model spools move into BC production, with fabrication and installation status visible against each element in the 3D viewer.
Problem addressed
Information is disconnected between the model, fabrication workshop and installation.
- Buyer
- Fabrication manager
- Validated by
- Prefabrication Workshop
Design Automation: GA · property write-back: beta
How it works
- 01Design Automation for Revit exports Fabrication Parts to JSON.
- 02BC creates BOMs, production or assembly orders, and QR labels.
- 03QR scans update status: planned, fabricated, shipped or installed.
- 04Status is displayed in the viewer; writing it back to the model remains dependent on the beta API.
Product building blocks
- HC Prefab Spool
- HC Prefab Status Entry
- HC APS Viewer
- Spool labels and loading lists.
Value
One status timeline from model to installation; site managers can see in 3D what is ready to install.
Constraint / to validate: Writing properties to AEC Data Model is in public beta. Until GA, status stays in BC and is overlaid in the viewer.
03 / 05
HC Handover & F-Gas
As-built data becomes Service Items, contracts and leak-check schedules, without re-keying spreadsheets.
Problem addressed
Installed equipment does not make it into service, and F-gas records are maintained manually.
- Buyer
- Service manager
- Validated by
- HVAC Service
Forma Build Assets / Tandem: GA
How it works
- 01Import assets from Forma Build Assets or Tandem, including location, warranty and equipment details.
- 02For refrigeration, t CO₂e is calculated from refrigerant type, quantity and GWP.
- 03BC creates Service Items, a Service Contract and a leak-check schedule based on t CO₂e.
- 04A mobile inspection report updates the asset record, and inspection status is sent back to Forma / Tandem.
Product building blocks
- HC Refrigerant
- HC F-Gas Equipment Log
- HC Leak Check Schedule
- Asset handover wizard, equipment register and inspection reports.
Value
Connects project handover with recurring service and F-gas records.
Constraint / to validate: Integration with national CRO / UDT needs validation, including API availability or file-export support.
04 / 05
HC TwinService
Niagara alarms and Tandem data create the right BC service order, while technicians can locate the asset in the 3D model.
Problem addressed
A BMS alarm does not create a service order for the right asset.
- Buyer
- Facility manager, service team
- Validated by
- Digital Twin, Niagara
Tandem Data API: GA
How it works
- 01Niagara sends points and alarms to Tandem streams.
- 02Threshold rules in middleware call the BC API, for example after a sustained delta-T anomaly.
- 03BC creates a Service Order for the linked Service Item, prioritized by its SLA.
- 04Closing an order updates service date and cost in Tandem; counters can inform maintenance schedules.
Product building blocks
- HC Twin Alarm Rule
- HC Twin Alarm Log
- hcTwinAlarms API
- Tandem link, 3D view and service KPIs.
Value
A bridge between Digital Twin / BMS and ERP: costs, invoices and service contracts in BC.
Constraint / to validate: Position it as ERP integration, not a CMMS replacement; details depend on the systems' available APIs and scope.
05 / 05
HC Forma Cost Connector
Forma Cost Management syncs with BC Jobs, while actual costs from BC flow back to Forma.
Problem addressed
Budgets, contracts and change orders are entered twice.
- Buyer
- CFO, project controller
- Validated by
- HellCold Finance
Forma Cost API: GA (ERP integration fields)
How it works
- 01Budget → Job Task and Job Planning Line (Budget).
- 02Subcontract and main contracts → commitments, Sales Quote or Job in BC.
- 03Change Order → budget revision and contract change.
- 04Expense → posted purchase invoice / Job Ledger Entry; integration fields track sync state.
Product building blocks
- HC Forma Cost Sync Log
- HC Forma Cost Mapping
- Job Queue sync and an error page with retry.
Value
A quick-to-demonstrate improvement in project accounting and a natural entry product for other integrations.
Shared foundation
HC APS Core
One integration layer and a shared AL base app. Future products primarily add workflow logic rather than rebuilding integrations from scratch.
Element links
File URN and element ID ↔ Business Central record.
Shared API
APIPublisher = 'hellcold' · APIGroup = 'aps'
Viewer in BC
ControlAddIn for viewing models and element status.
Secrets stay out of AL
Middleware provides a short-lived token for viewing only.
Integration pattern
Autodesk Forma / Revit / Tandem↔HellCold middleware↔Microsoft Dynamics 365 Business Central
Packages and model
Per-tenant licensing, workflow value
Tiers based on active projects or Service Item count rather than per-user licensing. All prices are hypotheses to validate with 3–5 pilot customers, not confirmed market pricing.
Implementation: MEP mappings and WBS templates as a service, indicatively 5–15 days.
Autodesk: Forma / Tandem subscriptions on the customer side; Design Automation billed in Flex tokens.
Lite edition: IFC / CSV import for BIM2Job to validate as a lower-cost entry path.
PackageProductsMetricPrice hypothesis
HC Build Starter
BIM2Job + Forma Cost Connector
BIM2Job + Forma Cost Connector
Active projects (Jobs)
from EUR 390 / month for up to 10 projects
HC Build Pro
Starter + PrefabFlow
Starter + PrefabFlow
Active projects + workshop
from EUR 890 / month
HC Operate
Handover & F-Gas + TwinService
Handover & F-Gas + TwinService
Number of Service Items
from EUR 0.50 / asset / month; EUR 250 minimum
Go-to-market
From in-house projects to AppSource
Validate with HellCold and Polish HVAC contractors first, then publish an entry package and expand into premium products.
- 01
Design partner
HC APS Core, BIM2Job and Forma Cost Connector on HellCold projects.
- 02
Polish pilots
3–5 HVAC contractors: validate pricing, mappings and real workflows.
- 03
AppSource and service
Publish HC Build Starter; pilot Handover & F-Gas.
- 04
Premium products
PrefabFlow after AEC Data Model write-back reaches GA; TwinService with Niagara partners.
Autodesk
Partner / APS Accelerator, App Store and webinars with CEE resellers.
Microsoft
AppSource and Business Central implementation partners without BIM expertise.
Industry
HVAC/R associations, installation events and HellCold case studies.
Assumptions to validate
Risks built into the plan
AEC Data Model mutations remain in beta
Keep status in BC and overlay it in the viewer until GA.
Potential overlap between Forma / CMMS and TwinService
Position the product as a bridge to ERP and Business Central.
Customer does not use Forma Data Management
Validate a Lite edition with IFC / CSV imports.
BC API limits on large models
Use delta sync, queues and batching.
Autodesk endpoint and product-name changes
Isolate them in the HC APS Core adapter layer.
Start with the workflow