AsgharianKnow what you can sell, today
One live power tree from utility feed to rack, fed by the EPMS and the CRM, with 2N derating and stranded-capacity detection. Sales, design and operations quote from the same number.
What we buildEngineering studio · Dublin · data center programmes
Custom software for data center developers.
We build the systems between your drawings and your racks: live capacity models, construction and commissioning trackers, BMS and DCIM integrations, tenant portals and AI operators. Start with a three-week Discovery Sprint: working software on your data, not a deck.
IT load
14.2MW
PUE
1.21trailing 24h
Supply air
24.6°C
Level 4 IST68% · 14 scripts left
Systems we build on and integrate with every week
Schneider EcoStruxureVertivSiemens DesigoHoneywellNlyteSunbird DCIMModbusBACnetSNMPOPC UAProcoreAutodesk Construction CloudRevit / IFCServiceNowSalesforceSnowflakeTimescaleDBAzureAWSKubernetesSchneider EcoStruxureVertivSiemens DesigoHoneywellNlyteSunbird DCIMModbusBACnetSNMPOPC UAProcoreAutodesk Construction CloudRevit / IFCServiceNowSalesforceSnowflakeTimescaleDBAzureAWSKubernetes
What we build
One team, every phase of the site.
The same engineers carry your project from feasibility model to operations dashboard, so nothing gets re-entered, re-modelled or lost between phases.
Capacity and power modelling
A live model of every megawatt from utility feed to rack, so sales, design and operations argue from the same numbers.
- Power tree with N, N+1 and 2N derating
- Committed versus contracted versus drawn
- What-if scenarios for density and cooling changes
- Exports to investor and lender reporting
Power tree derated, 2N
Utility feed A/B2 × 40 MW
UPS string 1 (Hall A)12.0 / 16.0 MW
UPS string 2 (Hall B)14.2 / 16.0 MW
PDU B-071.71 / 1.80 MW
Contracted26.2 MW
Drawn (peak)21.1 MW
Stranded2.9 MW
Construction tracking
Milestones, long-lead equipment, RFIs and cost to complete in one place, pulled from the tools your contractors already use.
- Procore and Autodesk Construction Cloud sync
- Long-lead equipment tracker with vendor ETAs
- Earned value and cash-flow forecasting
- Weekly board pack generated, not assembled
Milestones plan vs actual
Shell and coreDone
MV switchgearDone
Generators (8)6 of 8 set
Chillers (6)ETA +3 wk
Fit-out58%
CommissioningL1 started
Chiller 4 delivery slipped to 14 Nov. Critical path impact: 9 days unless L3 resequenced.Risk
Commissioning management
Level 1 to Level 5 scripts, witnessed results and punch lists in a system of record, with the evidence your tenants and insurers ask for.
- Script library with tagged assets and pass criteria
- Offline-capable field app for witnesses
- Live trend capture from BMS during IST
- Handover package generated from the record
| Script | System | Witness | Status |
|---|---|---|---|
| IST-04.12 Utility loss, gens carry load | Electrical | Owner, CxA | Pass |
| IST-04.13 UPS ride-through 12 min | Electrical | Owner, CxA | Pass |
| IST-04.18 Chiller failover N+1 | Mechanical | CxA | Retest |
| IST-04.21 Load bank 100% 8h | Combined | Owner, Tenant | Running |
| IST-04.22 EPO and restart | Combined | Owner | Scheduled |
Hall B L468% · 14 left
Open punch items31 (4 critical)
Operations and AI agents
Dashboards for the NOC, portals for tenants, and agents that triage alarms, draft work orders and explain what changed, with every action logged.
- Unified alarm feed across BMS, EPMS and DCIM
- Agent-drafted work orders with approval gates
- Tenant portal with power, environment and tickets
- Receipts for every automated action
CRAC B-03 supply air 27.9 °C, setpoint 24. Return delta collapsing.Major
PDU B-07 95% of derated capacity for 20 min.Warning
Watch agent
B-03 fan speed dropped to 40% at 02:14, matching a BMS override written by user
fm-night. PDU B-07 rise is tenant 12’s new GPU row, within contract. Recommend: clear the override, open a WO to inspect the B-03 VFD.✓ bms.read_trend B-03 · 60 min · 212 ms
✓ epms.read_pdu B-07 · contract 1.8 MW
⏳ cmms.create_wo · waiting for NOC approval
Services
Built for the software gaps between the drawings and the racks.
Off-the-shelf tools stop at the edges of their category. We build what sits in between, on top of the systems you already own.
See the slip before the critical path does
Long-lead equipment against the commissioning sequence, and a Cx system of record where scripts, witnesses and BMS trends land together. Handover the day IST passes.
What we buildOne stream from every system on the floor
Outbound-only collectors for Modbus, BACnet, SNMP and OPC UA into a historian you own. Everything else we build sits on that stream.
What we buildTenants who answer their own questions
Power, environment, cross-connects and requests on live data with tenant-scoped access. Support tickets down 41% for one operator.
What we buildReports a lender can trace to a meter
PUE, WUE, utilisation and EU Energy Efficiency Directive returns calculated from source points, with a link on every figure.
What we buildAlso, once the telemetry is in place: AI operators for the NOC, behind approval gates
Buy, build or both
Where custom software pays for itself
Vendor DCIM, BMS and construction tools are good at their own category. The cost shows up between categories: the spreadsheet that reconciles them, the report assembled by hand, the decision waiting on an export. That is where we build.
- Keep the vendor systems you have. We integrate, not replace.
- Build only the layer that is specific to your programme.
- Own the result: code, data and licence stay with you.
| Need | Vendor tools | Spreadsheets | Asgharian |
|---|---|---|---|
| One view across BMS, EPMS, CRM and schedule | One category each | Manual, goes stale | Live, one model |
| Fits your process and contracts | Configurable to a point | Fully | Fully, and stays in sync |
| Evidence trail | Per system | None | Receipts and source links |
| Time to first value | Months of rollout | Days | Three-week sprint |
| Ownership | Vendor licence | Yours | Yours, with source |
How we work
Outcome first. Software in weeks, not quarters.
A fixed-scope discovery sprint proves the idea with working software. Then a dedicated squad builds in two-week increments against a roadmap you own. When it is live, we run it or hand it over. Your choice.
01 · Discovery sprint
Discovery sprint
We map the phase you are in, the systems you have and the decisions that are slow or manual today. You get an architecture, a costed roadmap and a working thin slice of the highest-value piece.
Architecture and integration
Collectors for your BMS, EPMS, DCIM and construction tools go in first, so every later feature is built on live data rather than spreadsheets. Security review and data residency are settled here.
Build in two-week increments
A dedicated squad ships to production every fortnight. You see it working in your environment, on your data, with your users. Priorities change; the roadmap changes with them.
Run and evolve
We operate what we built under an SLA, or hand it over with documentation, training and a clean codebase in your repositories. Most clients keep a small retainer for the next site.
Selected work
Recent builds
Hyperscale developer
2.9MW stranded capacity recovered
Portfolio capacity model
Replaced 40 spreadsheets with a live power tree across three campuses. Sales, design and operations now quote from the same number.
CapacityEPMSSnowflake
Colocation operator
11days cut from L4 to handover
Commissioning system of record
Scripts, witnesses and BMS trends in one record. The handover package is generated the day IST passes.
CommissioningBMSField app
Edge fleet
62% of alarms triaged by agent
NOC watch agent
An agent that reads BMS and EPMS trends, explains changes and drafts work orders behind an approval gate, for 140 unstaffed sites.
AI agentsDCIMCMMS
Start here
The Discovery Sprint: three weeks, one hall, working software
Fixed scope. We connect to your systems, build the highest-value thin slice on live data, and hand you an architecture, a systems audit and a costed roadmap. If the slice is not running on your data by day 15, we do not invoice the sprint.
Days 1–5Systems inventory, read-only access, choose the slice
Days 6–10Collectors live, slice version one, Friday demo
Days 11–15Live data, costed roadmap, security review, readout
You getPrototype, audit, architecture, roadmap, go or no-go
You keepEverything, whether or not you continue
ThenBuild squad, run and evolve, or an embedded team
Common questions
Before you get in touch
Do you replace our DCIM or BMS?
No. We integrate with what you have and build the software that sits between and on top of those systems. When a vendor tool does the job, we tell you to buy it.
Who owns the code and the data?
You do. We build in your repositories and your cloud accounts. Asgharian Core modules are licensed to you for the deployment with source access, so there is no lock-in.
Can you work inside our security and data-residency rules?
Yes. We regularly deploy into air-gapped OT networks, EU-only regions and client-managed Kubernetes. Security review is part of the discovery sprint.
How quickly can you start?
A discovery sprint typically starts within two to three weeks of signing. Squads are staffed from the sprint team, so there is no handover gap.
Do you work with contractors and CxAs, or only owners?
Mostly owners and developers, but our commissioning and construction tooling is used daily by their contractors and commissioning agents, and we onboard them as part of the build.
What about AI? Is it safe in an OT environment?
Our agents read telemetry and propose actions; they do not write to control systems without an approval gate, and every action is logged with a receipt. You decide what they can touch.
Tell us about the site
Megawatts, halls, phase and target go-live. We will come back within one business day with a proposed sprint scope.