# Identification technology pilot plan

Version: ____  Date: ____  Site/scope: ____  Decision owner: ____
This worksheet records a local qualification exercise. Results apply to the documented conditions; they are not a general technology accuracy claim.

## 1. Required observation

Operational question to answer: ____
Object being identified: ____  Asset/location/connection distinction: ____
Required timing and scope: ____
Current workflow and independently checked baseline: ____
Proposed barcode/RFID/AIM/combined workflow: ____
Evidence the method can establish: ____
Conclusions it must not infer without other evidence: ____
Named asset owner: ____  Connection owner: ____  Field reviewer: ____
System administrator: ____  Integration owner: ____

## 2. Identity and coverage

Asset or connection identifier convention: ____
Encoded payload/tag-to-record mapping and owner: ____
Tag assignment and independent physical association check: ____
Replacement/duplicate/unknown identifier handling: ____
Intended inventory area or monitored connection points: ____
Outside-control area/IDs: ____
AIM supported components and unmonitored segments, when applicable: ____
Manual fallback and current confirmed record retained during uncertainty: ____

## 3. Exact trial configuration

Tag or printed-label part: ____  Attachment method and location: ____
Reader/scanner/controller and antenna references: ____
Software, firmware and configuration revision: ____
Equipment/surface/orientation/door/neighbor conditions: ____
Connection mode, accounts, external services and permissions: ____
Supplier documentation and unresolved application limits: ____
Tag battery requirements and maintenance, if applicable: ____
Approved change or isolated test arrangement: ____
Observation window and operator: ____

## 4. Predefined acceptance gates

| Requirement | Project-specific criterion | How checked | Owner |
| --- | --- | --- | --- |
| Expected-object coverage | ____ | ____ | ____ |
| Boundary exclusion | ____ | ____ | ____ |
| Correct identity lookup | ____ | ____ | ____ |
| Connection-event mapping if in scope | ____ | ____ | ____ |
| Interrupted integration/recovery | ____ | ____ | ____ |
| Exception closeout and fallback | ____ | ____ | ____ |

Independently verified inside population and evidence: ____
Independently verified outside controls and evidence: ____

## 5. Observation register

| Session/time | Object key | Expected inside/outside/event | Observed result | Duplicate/unknown/missed | Record decision | Evidence/reviewer |
| --- | --- | --- | --- | --- | --- | --- |
| ____ | ____ | ____ | ____ | ____ | ____ | ____ |

Inside distinct IDs observed: ____ / expected inside IDs: ____ = ____%
Outside controls observed: ____ / defined outside controls: ____ = ____%
State this as a rate for the chosen control set, not a general technology false-positive rate.
Repeated observations excluded from distinct-object counts: ____
Unknown identifiers: ____  Unresolved mapping conflicts: ____
AIM expected endpoint event versus observed endpoint event: ____
Stale/delayed events and integration interruption outcome: ____
Physical observations requiring separate confirmation: ____
Corrective action, configuration revision and affected retests: ____

## 6. Operating effort and decision

Measured preparation/observation/exception/reconciliation time: ____
Hardware and tagging cost from dated quotes: ____
Software, support, integration and maintenance cost scope: ____
Excluded/unknown costs and assumptions: ____
Retirement process for object, physical tag and mapping: ____
Record of failed as well as accepted sessions: ____
Pass/conditional pass/unresolved: ____  Authorized scope: ____
Remaining conditions and owners: ____
Fallback until closure: ____  Next decision date or trigger: ____