Skip to main content
GullySystem
Technology

Dashboards and KPIs for Data centre operators

Present agreed business measures from their underlying records.

Analytics

Does this function belong in your operation?

Use when decisions depend on a small set of consistently defined operational measures.

Managers need a consistent view of current performance.

Operators see free power by hall, racks let and tickets open. Capacity planners compare the figures with signed contracts. Hot halls are marked for action by the facility head.

Bring the records the workflow depends on.

  • Metric definitions
  • Source records
  • Viewer access and refresh requirements

Outputs to check

  • Defined operational scorecard
  • Source-reconciled drill-down
  • Data-refresh and exception status

Follow the dashboards and kpis workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the measure

    Agree its calculation, scope, owner and decision purpose.

  2. 2. Connect the source

    Identify records and the permitted refresh method.

  3. 3. Validate the figure

    Reconcile known totals and test missing-data cases.

  4. 4. Publish the view

    Show the period, filters and last successful data update.

  5. 5. Investigate exceptions

    Trace unexpected movements before changing operations or metric definitions.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner

Reviews agreed measures and assigns investigation of figures that differ from expectations.

Branch manager

Sees their own collection, stock and pending jobs before the staff arrive.

Accounts assistant

Reconciles financial measures with the source ledger and checks overdue balances requiring action.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Source refresh fails

Show the last successful data date and the affected measures.

Definitions differ by branch

Resolve the calculation before presenting a combined comparison.

Unexpected movement

Trace the figure to source entries before treating it as an operating result.

Can this work independently?

A dashboard requires the source records for each displayed measure. It can use reviewed files rather than live connections, provided the data date is visible. Report builders shape detail, while operational systems own transactions; dashboard filters must not alter source records or hide missing data.

Systems and records it connects with

  • Report builder: Saved field selections, filters and permitted report outputs.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Your accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • You tell us which figures you chase and which you ignore. You get a written list of tiles proposed for each role. Fewer tiles work better.
  • We locate where each figure lives in your current records. You get a note naming the source and any gaps. Gaps are listed honestly. A first dashboard is built on your data for a few roles. You try it, and move or remove tiles.
  • Periods, targets and viewing rights are agreed. Each person is given a login that opens only their screen. The scheduled summaries are turned on for a small group. The group reports back on timing and content.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Measures reconcile with source totals.
  • Filters use consistent definitions.
  • Missing data is distinguishable from zero.
Data centre operators

How the business operates.

A data centre operator leases cages, racks and individual units to customers who bring their own servers. Each lease commits a power allocation, a number of circuits on two feeds, and any cross-connects to carriers. The operator sells reliability, so every maintenance task and every visit leaves a record.

Customer contracts and capacity

Hold each lease with its racks, cages, power allocation, circuits, term and notice dates, and show reserved and free capacity per room.

Rack and cable register

Record what sits in each rack unit, which circuit powers it and every cross-connect between customer cages, carriers and meet-me rooms.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Rooms, cages and racks. Model each hall, cage and rack with unit positions, rated power and cooling zone, then show which racks are reserved, in use or free to sell.
  • Customer contracts. Hold leases with rack list, power allocation, circuits, service levels, term, notice and rate rules, and keep every dated amendment so billing reads the version in force.
  • Rack contents and power ports. Record each device by rack unit, owner and PDU outlet, so that removing a server frees the unit and the circuit capacity it used. Nothing stays reserved by accident.
  • Cross-connect register. List every link between customer cages, carrier handoffs and the meet-me room, with cable label, both ends, fibre or copper type, order date and monthly charge.

Operational bottlenecks to check

Power is sold faster than it is measured

Contracts promise a kilowatt allocation per rack. Meter readings sit in a building system, so overdraw is found at billing or when a breaker trips. Nobody sees it early.

Rack and cable records disagree with the floor

A customer moves a server between units and tells nobody. The rack plan, the cross-connect list and the real cabling then differ. The floor wins every argument.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Reservation

    Sales reserves racks or a cage for a prospect against a hall’s remaining kVA and floor space, and the hold carries an expiry date and a named salesperson. Holds lapse.

  2. 2. Contract and onboarding

    The signed lease records racks, power allocation, A and B feed circuits, cross-connects and notice terms, and the customer’s approved visitor list and technical contacts are added beside it. Escalation numbers sit beside it.

  3. 3. Delivery and installation

    Inbound equipment is checked against the delivery notice, tagged at the dock and wheeled to the cage, where rack units, power ports and patch cabling go into the register. Every box is tagged.

  4. 4. Daily operation

    Visits are pre-booked and badges issued, remote hands requests become tickets with a technician and a completion note, and power and temperature readings are logged by rack and hall. Every visit is logged.

  5. 5. Maintenance

    Generator runs, UPS battery checks, cooling servicing and gas suppression tests follow a calendar, and each task closes with the engineer’s note and the next due date. Dates are kept.

  6. 6. Billing and renewal

    The invoice carries rack fees, metered power over allocation, cross-connect charges and extra remote hands hours, and renewal dates arrive with the usage recorded over the term. Finance reviews each line first.

Industry reports to connect with

  • Power committed, drawn and free by hall, row and rack
  • Rack and cage occupancy with reserved holds and expiry dates
  • Cross-connects by carrier, customer and monthly charge
  • Remote hands tasks by customer, with included hours used

Questions before implementation.

When should data centre operators consider dashboards and kpis?

Use when decisions depend on a small set of consistently defined operational measures. Managers need a consistent view of current performance.

What should we bring to the requirements discussion?

Bring anonymised examples of Metric definitions; Source records; Viewer access and refresh requirements. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Present agreed business measures from their underlying records. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A dashboard reports recorded activity. Managers must investigate causes and decide actions before attributing a change to business performance.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Measures reconcile with source totals. Use this check when reviewing the first working version.

Talk to us

Discuss dashboards and kpis for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements