Demo CloudHarbor: data-center operations day

Demo CloudHarbor operates colocation facilities in Dubai, Frankfurt, and Singapore. It rents racks, cages, power circuits, cross-connects, and managed services to banks, retailers, and software companies. OSERP connects customer contracts, cabinets, devices, power meters, access badges, maintenance, incident SLAs, recurring billing, supplier costs, and capacity reporting.

1. Set up sites, rooms, and capacity

The site master records legal entity, address, data residency, certification, utility provider, reporting currency, and status. Room records store floor, zone, cooling class, fire zone, security class, rack capacity, power capacity, and effective dates. Rack records store rack ID, U position capacity, power feeds, PDU, customer allocation, cage, and status.

Field	Demo value	Impact
Site	CloudHarbor DXB-1	Legal and service scope
Room	Hall B / Zone 4	Cooling and access
Rack	B4-R018	Capacity and customer asset
Power	Dual 20 kW feeds	Billing and resilience
Customer	Demo FinServe Bank	Contract and SLA
Billing currency	USD	Invoice and receipt
Data residency	UAE	Compliance and access
Certification	ISO 27001 valid	Sales and audit evidence

Capacity snapshots record available U space, power, cooling, floor, network ports, and reserved capacity. A rack cannot be sold twice or exceed either power feed.

2. Create a colocation contract

The contract header records customer, site, room, service tier, start/end dates, renewal, currency, payment terms, tax, SLA, access policy, insurance, and approval. Lines record rack or cage, U space, power commitment, cross-connect, remote hands, managed firewall, IP block, installation fee, and recurring rate.

Demo FinServe leases 12 racks at USD 2,400 per rack monthly, 180 kW committed power at USD 190/kW, and four cross-connects at USD 320 each. The schedule separates base space, power, cross-connect, installation, tax, and any prepaid deposit. A signed contract reserves capacity and creates access and installation work items.

An amendment adding two racks from 15 October creates a prorated charge and updates capacity. A price or SLA change is versioned; posted invoices remain tied to their original rate card.

3. Install customer equipment and control access

Installation orders record contract, rack, device, serial, weight, power draw, network port, installer, permit, date/time, and acceptance. Asset records store customer owner, model, serial, warranty, firmware, criticality, and status. A device cannot be commissioned until safety, cabling, and power tests pass.

Access badges store person, company, identity evidence, role, zone, approval, start/end, escort requirement, and revocation. Visitor logs record arrival, escort, room, badge, departure, and incident. Expired badges and incomplete approvals block entry while preserving historical access evidence.

4. Meter power and generate recurring invoices

Meter records store PDU, circuit, opening/closing reading, kWh, peak kW, timestamp, device, quality flag, and tariff. Billing lines show committed power, measured overage, energy, cooling allocation, cross-connect, remote hands, tax, discount, and credit.

FinServe’s 180 kW commitment is billed monthly. If measured peak reaches 196 kW, the extra 16 kW is charged at the contract overage rate. A missing or implausible read is estimated with an explicit flag and trued up later. Billing is idempotent by contract, meter, and period.

5. Operate incidents and service levels

Incident headers record customer, site, rack, service, severity, opened time, SLA clock, commander, affected devices, communications, root cause, and status. Timeline entries are immutable. A P1 cooling incident starts a 15-minute response clock and records detection, acknowledgement, containment, recovery, and customer updates.

SLA credits reference incident, downtime, contract rule, calculation, tax, currency, approval, and credit note. A planned maintenance window records notice, affected customers, approval, and exemption from SLA measurement where contractually allowed.

6. Maintain power, cooling, and security assets

Equipment assets store UPS, generator, chiller, CRAC, fire panel, PDU, battery, cost, useful life, depreciation book, inspection interval, and location. Work orders record asset, failure, permit, technician, parts, contractor, downtime, test, and return-to-service approval.

Fuel, refrigerant, filters, batteries, and critical spares use serial/batch, expiry, storage, and compatibility controls. A failed generator test creates an exception and blocks a resilience certificate. Supplier invoices match contract, work order, delivery, and acceptance.

7. Manage cross-connects, remote hands, and capacity

Cross-connect records store customer, source rack, destination provider, port, cable, installation date, recurring rate, redundancy, owner, and status. Remote-hand requests record ticket, customer authorisation, technician, start/end, task, materials, photos, and billable time.

Capacity planning stores forecast, committed, reserved, installed, and available power/U space by site and room. A new sale requires capacity approval; oversubscription is permitted only under a documented engineering rule and approval.

8. Multi-currency and data-center close

The group reports in USD while Frankfurt suppliers bill EUR and Singapore power costs SGD. Each invoice, receipt, supplier bill, meter adjustment, and credit stores transaction rate, source, timestamp, realised FX, and revaluation status. Space, power, energy, maintenance, depreciation, and SLA credits remain separate dimensions.

Close reconciles contracts to racks, racks to equipment, meters to invoices, invoices to receivables, receipts to bank, access badges, incidents to credits, assets to maintenance, supplier invoices, capacity, tax, FX, and GL. Certification and insurance expiry reports retain evidence and owner.

KPI	Before OSERP discipline	After OSERP discipline	Improvement
Rack-to-invoice accuracy	94.5%	99.8%	+5.3 points
Power billing variance	6.2%	1.0%	84% lower
P1 response within SLA	86%	98%	+12 points
Capacity forecast accuracy	69%	91%	+22 points
Monthly close	12 days	4 days	67% faster

Practice challenge

Create a data-center site, room, rack, and capacity snapshot, approve a colocation contract, install a customer device, issue an access badge, import a meter read, bill power overage, open a P1 cooling incident, calculate an SLA credit, complete generator maintenance, raise a cross-connect request, settle an EUR supplier bill, revalue balances, and close the month. Explain every field, status, permission, formula, journal, tax result, API identifier, exception, and audit event.

Related: Fixed Asset field guide, AR Invoice field guide, Inventory field guide, Workflow and Approval field guide, and API cookbook.