HDbeammachineBeam Machine Docs
Help Center

Beam Machine Operations Manual

User manual for fixed assets, fleet, rental, inventory, and related operational control workflows.

publicusers

Running Daily Operations in Beam Machine

This page shows operations users how Beam Machine tracks real-world assets, equipment, rentals, and stock so the system matches what actually happened.

Product: Beam Machine
Module: Operations
Role: Operations Clerk, Asset Controller, Storeman, Rental Coordinator, Operations Manager
Difficulty: Beginner to Intermediate
Time: 12 minutes first read
Last Updated: 2026-03-10
Version: Current Beam Machine app build in this repo

Before You Start

  • You should know which entity, warehouse, asset pool, or rental book you are working in.
  • You should have the real-world source information ready, such as an asset detail, receipt, maintenance event, or rental movement.
  • Keep 14-asset-rental-stock-and-fleet.md open if you need the deeper SOPs.

What is operations work in Beam Machine?

Operations work in Beam Machine is the part of the product that keeps the system record tied to a physical thing. On paper, this would be your asset register, stock cards, rental diary, maintenance file, and warehouse movement sheets. In Beam Machine, those controls live in Fixed Assets, Fleet, Rental, and Inventory.

The basic rule is simple: if something moved, was counted, was serviced, or changed hands in real life, that event must exist in the system.

When do you use this?

Use this page when you need to manage equipment, record rental activity, update fixed assets, control stock, or explain why the physical world and the system no longer agree.

If these events are captured late or outside the system, the next user makes decisions on bad information with good confidence.

Where do you find operations work?

Primary path: Use the Operations area of the left sidebar.
Reference: Use 98-screen-map.md for exact route families.

How to run operations work safely

Operations route map

Area Main routes Main use
Fixed Assets /dashboard/fixed-assets/* Asset register, depreciation, disposals, reconciliation
Fleet /dashboard/fleet/* Equipment register, maintenance, insurance
Rental /dashboard/rental/* Rental creation, calendar, check-out, check-in, rates
Inventory /dashboard/inventory/* Items, warehouses, movements, stocktakes

Start every operation with the same control checks

  1. Confirm the active entity.
  2. Confirm the correct item, asset, equipment unit, or rental record already exists.
  3. Confirm the real-world event date before you capture it.
  4. Confirm whether the transaction also affects finance, approvals, or supporting documents.

Register and maintain fixed assets

  1. Open Fixed Assets.
  2. Review the totals for asset count, total cost, and net book value.
  3. Open Asset Register.
  4. Add the asset if it does not exist yet.
  5. Review Depreciation before you assume the book value is correct.
  6. Use Disposals when an asset leaves the business.
  7. Use Reconciliation to compare the operational asset view against finance data.

✅ Checkpoint: Each asset should have a record, a clear status, and a visible trail for depreciation or disposal where relevant.

Maintain the equipment register

  1. Open Fleet.
  2. Review total assets, active equipment, and maintenance due.
  3. Open Equipment Register.
  4. Add new equipment before it enters regular use.
  5. Use Maintenance to log or review service events.
  6. Use Insurance to review cover status and renewal information.

✅ Checkpoint: Equipment should be traceable by record, not by memory or side notes.

Run a rental lifecycle

  1. Open Rental.
  2. Use New Rental to create the booking before the equipment moves.
  3. Check Calendar for scheduling conflicts.
  4. Use Check Out when the equipment leaves.
  5. Use Check In when the equipment returns.
  6. Use Rates to confirm pricing rules when something looks wrong.

✅ Checkpoint: The rental should exist before movement, and the status should match the real-world stage.

Manage stock and warehouses

  1. Open Inventory.
  2. Review item count, low-stock alerts, and warehouse count.
  3. Use Items to maintain stock masters.
  4. Use Warehouses to control storage locations.
  5. Use Movements to trace stock movement history.
  6. Use Stocktakes for physical verification.

✅ Checkpoint: Items, locations, and movement history should all agree well enough to explain a stock balance.

Stay honest about maturity

  1. Use the live screens for day-to-day work.
  2. Do not promise advanced monitoring, optimization, or exception automation unless it is visible in your environment.
  3. Use 99-functionality-gap-map.md when a user asks for deeper behavior that exists only in source docs or Auto_todo packs.

Common Questions & Issues

"The equipment moved already, so I’ll update the system later"

Why this happens: Teams often treat the system as a reporting tool instead of the operational source of truth.

Fix: Capture the rental, asset, stock, or maintenance event as close to the real-world action as possible.

"We keep the real register in a spreadsheet and Beam Machine is just for reporting"

Why this happens: Legacy habits survive after rollout.

Fix: Pick one master record. If Beam Machine is the system of record, stop keeping the live truth somewhere else.

"The route exists, but the smarter automation is missing"

Why this happens: Some deeper operational intelligence described in intake documents and Auto_todo packs is still future work.

Fix: Use the current route set for live work and confirm delivery status in 99-functionality-gap-map.md.

What's Next

Related Pages

Still Stuck?

Was this page helpful?

[Yes] [No]