Skip to main content
GullySystem
Technology

Business solutions for Data centre operators

Explore software for work such as “Rack and cage colocation”. Review each business function below, including when it fits and what to check before implementation.

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.

Power and environment readings

Log meter readings per rack and per feed, with temperature and humidity logs by room, and flag a rack that passes its contracted draw.

Visitor and access control

Keep each customer’s approved visitor list, pre-book visits, record badge issue and sign-in, and expire access when a contract ends.

Deliveries and remote hands tickets

Log inbound equipment against a delivery notice and handle customer requests as tickets with a technician, a completion note and included-hours count.

Facility maintenance calendar

Schedule and record generator runs, UPS battery checks, cooling servicing and fire system tests, with the engineer’s note and next due date.

Cross-connect order register

Records each fibre or copper link between two customers or to a carrier, with the ports and the date patched. Network staff work from it. Disconnects clear on the same line.

Generator and UPS test log

Notes each test run of generators, batteries and UPS units, with load held and result. The facility engineer signs it. Failed tests open a repair task straight away.

Customer move-in and move-out checklist

Lists equipment arrival, rack placement and badge issue for new customers, and the reverse on exit. The site manager ticks each step. Final power-down is confirmed in writing.

Carrier and meet-me room record

Holds the network carriers present in the building, their cabinets and circuit IDs. Customers ordering connectivity pick from it.

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.
  • Power and environment readings. Log kWh readings per rack and feed, with temperature and humidity by hall, and flag any rack that passes its contracted draw before the invoice run does.
  • Visitor and badge control. Maintain approved visitor lists per customer, book visits ahead, record badge issue and sign-in at the mantrap, and expire access when the contract ends.
  • Delivery and dock log. Match inbound pallets to customer delivery notices, record weight and carton count, hold unmatched items in a named bay and trace each box to its rack.
  • Customer task tickets. Customers raise a task against a rack, a technician accepts and completes it with a note, and the minutes count against the contract’s included remote hands hours.

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.

Access lists go stale

Customers add and remove engineers by email. The security desk works from a printed list, so a former contractor can still arrive with a valid name. The printed list is the only check.

Remote hands work is billed late

A technician swaps a drive on request and notes it on a pad. Whether it falls within the included hours is decided weeks afterwards. Customers dispute it.

Maintenance proof is scattered

Generator tests, UPS battery checks and cooling filter changes are recorded in different places. Customers asking for an audit extract wait for someone to collect them.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  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.

Roles and responsibility boundaries.

For sales and capacity planners

See free kilowatts and floor space by hall, place holds for prospects and read which contracts approach renewal, with the power and space each one actually used.

For facilities engineers

Work from the maintenance calendar, log meter and temperature readings on a tablet, and close each task with a note and the next due date.

For technicians on customer tasks

Open the rack, read the customer’s instructions, complete the swap or re-cable, and record the minutes taken and any part used from the spares cage.

For security and reception

Check each visitor against the customer’s approved list, issue badges at the mantrap and see exactly who is inside the building right now.

For customers

Book visits, raise remote hands tasks, read power usage for their own racks and download invoices without emailing the operations desk.

Reports your managers need.

  • 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
  • Visitor log by customer, building and date
  • Maintenance tasks done and due by system and hall
  • Contracts by renewal date, with power and space used

Connections to scope

  • Power and environment monitoring export
  • Email
  • SMS
  • Access control badge list
  • Accounting export
  • Payment gateway

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Floor and power model

Halls, rows, racks, feeds and circuit ratings are entered as your single-line diagram and floor plans show them, so the register starts from drawings your engineers already trust.

Rate rules

Rack fees, power allocation, overage rates, cross-connect charges and included remote hands hours are set per contract type, then tested against two real invoices before go-live.

Access rules

Visitor approval, badge types, escort rules and out-of-hours entry follow your security policy, and the wording is reviewed with your team and the auditor’s checklist.

Reading sources

Meter and sensor data arrive by file import or an interface to your monitoring system, and the choice between them is scoped during implementation with your facilities lead.

Data brought across

Your existing sheets of customers, rack contents, cross-connects and open tickets are read in, and the facility team walks each hall with a printout to confirm them.

Hosted by GullySystem

GullySystem hosts the system, so sales, engineering, security and billing work from the same facility record. No team holds a private copy of the facility record.

Limitations to settle before implementation

  • A server room inside a single office with no outside tenants can be tracked in a spreadsheet.
  • Firms that run client networks and helpdesks rather than a facility will find Managed Service Provider Management Software closer.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Rack and cage colocation
  • Disaster recovery sites
  • Managed hosting and private cloud
  • Connectivity and carrier options
  • Remote hands and on-site support
  • Security and access control
  • Compliance and audit support
  • Expansion for existing customers
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

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