Skip to main content
GullySystem
Technology

Stock Tracking and Alerts for Data centre operators

Record stock movements and flag items reaching configured levels.

Inventory Management

Does this function belong in your operation?

Use when the business holds physical stock or consumables requiring quantity control.

Goods are received, issued, transferred or counted.

Spare patch leads, rack screws, blanking panels and fibre cassettes are counted in the store. Low items raise a request. Customer-owned spares are kept in a separate list.

Bring the records the workflow depends on.

  • Item and location list
  • Opening quantities
  • Reorder and movement rules

Outputs to check

  • Item-location balance register
  • Movement and count-adjustment history
  • Replenishment exception list

Follow the stock tracking and alerts workflow.

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

  1. 1. Set opening stock

    Approve item-location quantities and tracking rules.

  2. 2. Record movements

    Capture authorised receipts, issues, sales and transfers.

  3. 3. Compare counts

    Investigate physical differences before adjustment.

  4. 4. Review thresholds

    List shortages using the appropriate item and location level.

  5. 5. Handover replenishment

    Send requirements to purchasing or production without treating an alert as an approved order.

Who uses the module, and who approves?

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

Storekeeper

Issues material against a job, counts a rack on a slow afternoon, and answers for the difference. Every difference gets a name.

Counter staff

Checks recorded stock and location before confirming availability under the business's reservation rules.

Owner

Reads the alert list and the dead stock report, which is where the tied-up working capital sits.

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.

Count differs from record

Investigate recent movements and approve an adjustment with the reason.

Negative balance attempted

Apply the agreed hold or exception rule and expose the cause.

Goods held for inspection

Keep them distinct from stock available for issue or sale.

Can this work independently?

Stock tracking can run from entered receipts and issues, but every physical movement needs a record. Purchase, sales, production and warehouse connections provide those movements. Reorder alerts signal a threshold; purchasing still decides quantity, supplier and approval.

Systems and records it connects with

  • Purchase order management: Authorised supplier commitments and open line balances.
  • Goods receipt: Counted, accepted and rejected supplier-delivery quantities.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Multi-outlet stock: Outlet quantities and acknowledged transfer movements.

Configure, test and introduce the workflow.

  • Show us the godown and the counters. A note lists the locations and the item groups.
  • Supply levels per item and place, or ask for suggestions from history. Balances and alerts then appear for trial. A count is taken and loaded as the opening balance. The team checks a sample against the shelf.
  • Each group practises receipts, issues and transfers. Short cards for the shelves follow. Alerts reach named people. A review once the opening season ends lists slow stock.

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.

  • Movements reconcile with location balances.
  • Count adjustments retain approval.
  • Alerts use the correct item and location threshold.
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 stock tracking and alerts?

Use when the business holds physical stock or consumables requiring quantity control. Goods are received, issued, transferred or counted.

What should we bring to the requirements discussion?

Bring anonymised examples of Item and location list; Opening quantities; Reorder and movement rules. 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. Record stock movements and flag items reaching configured levels. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Recorded balances depend on timely movement entries. Physical availability must be confirmed through the agreed count and reservation process.

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. Movements reconcile with location balances. Use this check when reviewing the first working version.

Talk to us

Discuss stock tracking and alerts 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