Inventory Asset Classification and Lifecycle Definition SOP

Standard Operating Procedure: Inventory Asset Classification & Lifecycle Definition

---

1. Executive Summary & Purpose

This document establishes the institutional definition of an "Inventory Asset." An asset is defined as any tangible or intangible resource owned or controlled by Template Registry that provides measurable economic value, carries a lifecycle cost, and requires systematic tracking for auditability, depreciation, and operational continuity. The purpose is to ensure uniformity in data entry, valuation, and life-cycle management across all departments.

2. Scope & Prerequisites

• Scope: Applies to all hardware, software licenses, intellectual property, and physical inventory housed or managed within Template Registry facilities.
• Tools: Asset Management System (AMS), Barcode/RFID scanner, Enterprise Resource Planning (ERP) credentials.
• Software: Unified Inventory Registry (UIR) v4.2+.
• PPE: N/A (Standard office/data center safety protocols apply).

3. Roles & Responsibilities (RACI)

---

4. Step-by-Step Procedure

Phase I: Identification & Valuation

• Verify the item exceeds the capitalization threshold (>$500 USD per unit).
• Confirm the item has a projected useful life > 12 months.
• Assign a unique Asset ID using the TR-Standard nomenclature: [LOC]-[TYPE]-[YYYY]-[NNN].

Phase II: Registration in AMS

• Input Asset Name, Serial Number, and Manufacturer details into UIR.
• Categorize asset type (Hardware, Software, Infrastructure, Data).
• Tag with specific depreciation schedule (Straight-line vs. Accelerated).
• Assign an "Owner" (The primary custodian of the asset).

Phase III: Lifecycle Tagging

• Apply physical RFID/Barcode tag to hardware assets.
• Log software licenses to the digital entitlement vault.
• Perform "Check-in" confirmation against the procurement purchase order (PO).

---

5. Quality Assurance & Pro-Tips

QA Metrics:

• Asset Variance: Discrepancy between AMS and physical audit must be < 0.5%.
• Data Completeness: 100% of assets must have an assigned owner and location tag.

Pro-Tips:

• The "Goldilocks" Rule: Do not over-track consumables (cables, keyboards, paper). Focus on assets that require maintenance, security patching, or financial depreciation.
• Automated Discovery: Use network discovery agents to update software asset status automatically to avoid "Ghost Licenses."

---

6. Frequently Asked Questions

Q: Is a cloud-hosted SaaS subscription considered an "Inventory Asset"?

• A: Yes. While intangible, it holds a recurring cost and usage license. It must be logged in the Software Asset Management (SAM) module of the UIR, with expiration and renewal dates tracked as metadata.

Q: If an item is under the $500 threshold, does it need a tag?

• A: Generally, no. Items under the capitalization threshold are classified as "Operational Expense" (OpEx) supplies. Exceptions exist for high-security items (e.g., security tokens), which must be tracked regardless of cost.

Q: What is the primary cause of inventory "drift"?

• A: Failure to record "Internal Transfers" (moving an asset from Desk A to Desk B). Ensure all hardware movements are triggered via a status change request in the UIR portal.

---

Approved by: Julian Vance, Chief Architect Template Registry Engineering Division