Fewer things to keep in step
One database for the floor, the work and the spend: nothing to synchronise, no integration to keep running between them.
Compare
One platform, or three tools kept in step by hand?
Most data centres run on some mix of spreadsheets and drawings, a DCIM tool and a separate service desk. Here is how that compares with one record for all of it, and where another kind of tool may suit you better.
Side by side
This compares kinds of tools, not particular products: products in each kind differ, and some do more than shown. Ask any vendor, us included, to show you each line.
| What you need | Spreadsheets and drawings | A stand-alone DCIM tool | A separate ITSM tool | Divjyot ONE |
|---|---|---|---|---|
| Racks, devices and floor plans | By hand | Yes | As configuration items, without the floor | Yes, with a 3D twin |
| Cables, traced end to end through patch panels | By hand | Often | Rarely | Yes, with labels and a register |
| Power chain with A and B sides and failover loads | Hard to keep right | Often | No | Yes |
| Cooling units and zones, with their redundancy | By hand | Often | No | Yes, N to 2N |
| Forecasts of when capacity runs out | By hand | Sometimes | No | Yes, with a likely range |
| VMs linked to the hosts, racks and power feeds they run on | By hand | Sometimes, through an integration | In the CMDB, through discovery | Yes, from six platforms |
| Sensor monitoring and alerts | No | Often, sometimes as a separate product | Through an integration | Yes, with early warnings |
| Incidents, requests, changes and problems with SLAs | No | Sometimes basic workflows; usually an integration | Yes | Yes |
| Tickets linked to the exact rack, device and service | No | Through an integration | If the CMDB is kept up to date | Yes, on one record |
| Workflow automation and runbooks | No | Varies | Yes | Yes, on the same record |
| A change approval that carries out the move itself | No | Varies | Approves it; someone updates the DCIM tool | Yes: MAC requests |
| Moves that re-patch cables in the new rack | No | Varies | No | Yes, shown before saving |
| A location history for every device | No | Often a change log | Of the record, not the floor | Yes, with a log per hall and CSV |
| Phones on the floor: scanning, offline, camera rack audits | No | Varies, often an add-on | Mobile tickets | Yes, in the browser |
| Purchase orders, invoices, contracts, licences and spares | In other spreadsheets | Rarely | Asset management, sometimes | Yes, tied to the equipment |
| One audit trail across all of it | No | For its own records | For its own records | Yes, append-only |
| Run on your servers or hosted | Anywhere | Depends on the product | Often hosted only | Both, from the same release |
- Covered
- Partly, depends on the product, or by hand
- Not covered
Why it matters
The cost is in the hand-offs
Each tool may be good at its own job. The trouble starts between them: every move, every ticket and every purchase has to be copied from one to another, and anything copied by hand drifts.
Answers that agree
The rack, its ticket, its power and its purchase history come from the same record, so reports don't contradict each other.
One set of permissions
One sign-in through your identity provider, one set of roles per environment, and one audit trail to show an auditor.
Being fair
When something else may suit you better
We'd rather you chose the right tool. Divjyot ONE may not be the best fit if:
You need airflow simulation
Divjyot ONE shows measured temperatures, airflow and cooling. Computational fluid dynamics (CFD) modelling of a planned hall needs a CFD tool; it can sit beside Divjyot ONE.
You only watch a few edge sites
If all you need is power and temperature alarms from a handful of small rooms, a monitoring appliance may be simpler. Divjyot ONE watches edge sites too, on a map with their collectors, but earns its keep when space, cables, tickets and spend need to agree.
Discovery across all software and cloud is the goal
Divjyot ONE discovers network equipment over SNMP and LLDP, polls devices for readings, and reads VMs from virtualisation platforms and instances from AWS, Azure and Google Cloud. Mapping every application and its dependencies across an enterprise is a job for a dedicated discovery tool, which can feed Divjyot ONE through its imports, partner connectors and API.
Your service desk serves the whole company
If an enterprise-wide ITSM platform already runs HR, facilities and IT requests, keep it: Divjyot ONE connects to ServiceNow and Jira, and runs the data centre's own work alongside.
Check each line for yourself
Bring this table to a demo and we'll show you every line in the product, with demo data.