What to check when equipment is delivered
On the day equipment arrives, write the unique identifier, model and serial number, physical location, who accepted it, and what failed inspection into the same asset record. Update the inventory at installation or removal, not at the next month-end count. Lease versus buy, the rental system, barcode versus RFID, and the telemetry protocol each have their own note.
On this page
- Open one asset line on the day it arrives
- NIST asks for an inventory that matches the system and is not double-counted
- Match model, serial number, and place to the nameplate
- Update the inventory at installation and at removal
- Who accepted it, and what failed
- Telemetry and the business system come after this line
- Do not mark a failed unit as installed
- On removal, change status under the same identifier
Open one asset line on the day it arrives
On the day equipment is delivered or installed, the warehouse or site lead opens the asset record and writes one line: the company's unique identifier, the model and serial number on the nameplate, the place it is installed, who accepted it on site, and the inspection items that failed. The person who accepts it signs and writes the time. A failed item stays on that line. It does not move to a slip that can only be matched later. The identifier is assigned before delivery. The day itself matches the physical item to that line.
Lease versus buy decides who keeps the asset at the end and when cash leaves. It does not replace the delivery inspection. Choosing a rental system is about how assets, contracts, the calendar, maintenance, and returns are recorded. Delivery acceptance writes where this item is today, who accepted it, and what failed, into the asset record already in use. Those two notes are How to choose whether to lease or buy equipment and How to choose an equipment rental management system. Equipment can be bought, rented, or taken forward in the same project as development; see Buy, lease, or plan it with development on the homepage.
NIST asks for an inventory that matches the system and is not double-counted
Read on 20 October 2026, the catalog page for NIST SP 800-53 Rev. 5 gives the publication date as September 2020, including updates as of 10 December 2020, and the document history marks 10 December 2020 as SP 800-53 Rev. 5 (Final). A planning note dated 27 August 2025 describes a minor Release 5.2.0. The controls listed as changed there do not include CM-8. The control text below is from that publication, DOI 10.6028/NIST.SP.800-53r5. CM-8, System Component Inventory, says to develop and document an inventory that accurately reflects the system, includes all components within the system, does not include duplicate accounting of components or components assigned to any other system, is at the granularity needed for tracking and reporting, and includes the organization-defined information needed for accountability. The inventory is reviewed and updated at an organization-defined frequency.
The discussion says system components are discrete, identifiable information technology assets that include hardware, software, and firmware. Preventing duplicate accounting requires a unique identifier for each component. It also says inventory specifications include date of receipt, cost, model, serial number, manufacturer, supplier information, component type, and physical location. Cost stays on the purchase document. The asset record notes whether that field exists and which document holds the figure. It does not invent a second price on the delivery sheet. The publication states no service level and no number of hours in which delivery must be finished.
Match model, serial number, and place to the nameplate
Acceptance compares three strings: the model and serial number on the nameplate, the same string on the packing list, and the line reserved in the asset record. If they differ, the difference is written in the failed column. The packing list is not edited to match the nameplate, and the nameplate is not edited to match the order. Where the discussion's specification fields call for manufacturer and supplier, copy the names already printed on the nameplate and the order. Do not invent a short name on site. The date of receipt is the date it actually arrived.
Physical location is specific enough that the next person on site can find it: building, floor, bay, or room, not only "customer site". For networked components the discussion also mentions machine names and network addresses across implemented protocols. If an address is not assigned on delivery day, the location field still records the physical place, and the network owner adds the address later with the date it was added. Software installed with the equipment is recorded, as the discussion describes, on the system where it is installed and managed, so the central inventory does not hold a copy with no system association.
Update the inventory at installation and at removal
The text of CM-8(1) is: update the inventory of system components as part of component installations, removals, and system updates. The discussion says that if inventories are not updated at these times, there is a greater likelihood the information will not be captured. System updates include hardware, software, and firmware. Delivery acceptance treats installation as one of those times: the moment it is installed, write the identifier, the place, and the acceptance; the moment it is removed, write the removal date and the new status on the same line. Do not wait for month-end or the annual count.
Equipment that is not yet installed is not marked installed. While it sits in receiving, the location is receiving and the status is waiting for installation. After installation, place and status change, and the original unique identifier stays. A new identifier because the room changed is the duplicate accounting the discussion warns about: one physical item becomes two lines, and accountability no longer matches. How that identifier is printed as a barcode or written to an RFID tag is a separate note, How to choose barcode or RFID for equipment tracking.
Who accepted it, and what failed
The person named as accepting the delivery was on site and saw the item. The name is not added later from an office. CM-8(4) is a control enhancement. It asks the inventory to identify, by name, position, or role, the individuals responsible and accountable for administering those components. That is administrative responsibility. It is not the same field as who accepted the item today. When both are needed, write them on separate lines: acceptor plus date, administrator plus role. A line with no acceptance signature is not a completed delivery inspection.
A failed item names the condition: missing part, serial number mismatch, visible damage, will not power on, accessories that do not match the packing list. Each line names who found it, when, and who takes it next. Passed items do not need praise. The check column says passed, with a signature. A supplier's repair promise and arrival time stay in the contract. They are not rewritten into a status on this inventory.
Telemetry and the business system come after this line
Delivery acceptance does not choose MQTT or HTTP, and it does not choose which business field receives a reading. Those decisions wait until the equipment has an identifier and the inventory status is installed. The protocol note is How to choose MQTT or HTTP for equipment telemetry. How a reading reaches a system already in use is How to connect equipment to existing business systems. A unit that failed inspection is not treated as a sensor already online.
When to open a maintenance order depends on condition after the equipment is running, not on the signature on the delivery sheet. Predictive maintenance covers measurements and work orders. The delivery record tells the maintenance lead the identifier, the place, and any defect already written at delivery. See How to do predictive maintenance for equipment. If a defect becomes a work order, the order cites this identifier and the original failed-item text.
Do not mark a failed unit as installed
If the serial number does not match, or a part required to run is missing, the status stays "pending", the location is where the item actually sits, and it is not marked installed. The responsible person names who replies to the supplier and which photo or packing-list line goes with the reply. The supplier's receipt number is written back on the same line. Until the status becomes installed, the calendar and the rental order do not promise this unit to the next user.
Visible damage that does not affect identification or operation is still written as failed or as an accompanying defect. The person who accepted it and the equipment owner decide together whether it can be installed. The decision is written on the same line, with a date. Saying "use it for now" while the record is empty leaves the next count unable to tell whether the item is on the books. Only a decision to install updates the inventory to installed under CM-8(1), and the defect text stays.
On removal, change status under the same identifier
When equipment leaves the site, the same identifier used at delivery changes status to removed or returned. The line records the removal date, the place it left, and who confirmed it on site. CM-8(1) lists removal beside installation as a time to update the inventory. If the component is then assigned to another system, CM-8 says not to account for it twice. The inventory changes the owning system and the location. It does not add a new identifier with no history.
How often to review the inventory is for the organization to define. CM-8 leaves the frequency as an assignment and gives no number of days. Delivery and removal are the installation and removal events. A long review cycle does not replace an update at those two events. Price, late-delivery penalties, and supplier ranking stay on the contract and the receiving document. The inventory is accurate when each item has one identifier, place and status change on the day of installation or removal, and a failed item is written on that same line.