Asset Management Physical Inventory

1
Asset ManagementPhysical Inventory

• March 2006

2
Agenda

• Goals
• Process Overview
• Walkthrough
• Expected File Formats
• Types of Match Results
• Types of Transactions Produced
• Discussion Questions

3
Process Overview
4
1. Setup the Inventory Session
The scan scope and extract are defined using AMs
Mass Change functionality. No data is actually
changed when the extract and scope are processed.
5
1. Setup the Inventory Session
The Inventory Occurrence definition links the
scope and extract, and establishes settings for
generated asset transactions.
6
2. Create the Extract
The extract file contains information about
assets that may be scanned during the inventory
session. It is uploaded to the scanner.
7
2. Create the Extract
The extract is uploaded via a scanner-specific
software Intermecs software is called the
FileCopy Utility. Having asset data on the
scanner allows an assets information to be
displayed when it is scanned, for example.
8
Scanner Input File Layout

• Field Name Len. Description
• TagNumber 12 Assets tag number.
• SerialID 20 Assets serial number.
• AssetID 12 Assets system ID same as tag .
• DeptID 10 Core-CT department ID of the asset.
• Model 30 Assets model number or name.
• Location 10 Core-CT location ID of the asset.
• Descr 30 Description of the asset.
• Custodian 30 Name of the Custodian
• EmplID 11 Employee ID of the asset custodian.
• Manufacturer 30 Assets manufacturer.

9
Scanner Input File - Sample Data

• Field Name Len. Sample Data
• TagNumber 12 8001008251
• SerialID 20 6952CJNKK721
• AssetID 12 8001008251
• DeptID 10 DOC88403
• Model 30 DeskPro
• Location 10 ASOS000003
• Descr 30 Computer
• Custodian 30 Smith,Susan
• EmplID 11 124356
• Manufacturer 30 Compaq

10
3. Perform Inventory

• Scanner Code requirements
• Ability to read the Core-CT extract.txt file so
  it can display asset information while scanning.
• Allowing modifications to be made to certain
  fields during scanning
• Enabling compatibility with Core-CT location
  codes.
• Ability to produce a Core-CT-compatible scan.csv
  file that contains Physical Inventory results.

11
4. Load Inventory Results
After performing the inventory, the scan data is
uploaded into Core-CT using the FileCopy Utility
Physical Inventory page.
12
Scanner Output File - Layout

• File Layout Len. Description
• TagNumber 12 Assets tag number.
• SerialID 20 Assets serial number.
• AssetID 12 Assets system ID same as tag .
• Dept ID 10 Core-CT Department of the Asset
• Model 30 Assets model number or name.
• Location 10 Core-CT location ID of the asset.
• Description 30 A description of the asset.
• Custodian 30 Name of the asset custodian.
• EmplID 11 Employee ID of the asset custodian.
• Manufacturer 30 Assets manufacturer.
• MatchStatus 1 Reserved by the system.
• Review 1 Review requested for asset
• IP Address Not used.
• IP Alias Not used.
• SW Version Not used.
• Scan BU Not used.
• PI Operator 30 Name of Scanner operator.
• Comment 900 Operator comments .

13
Scanner Output File Sample Data

• File Layout Len. Description
• TagNumber 12 8001008251
• SerialID 20 6952CJNKK721
• AssetID 12 8001008251
• Dept ID 10 DOC88403
• Model 30 DeskPro
• Location 10 ADOC333027
• Description 30 Computer
• Custodian 30 Smith,John
• EmplID 11 123456
• Manufacturer 30 Compaq
• MatchStatus 1 O
• Review 1 Y
• IP Address Not used.
• IP Alias Not used.
• SW Version Not used.
• Scan BU Not used.
• PI Operator 30 Jones
• Comment 900 Review asset status

14
5. Resolve Duplicate Tag Serial s
Scan results with duplicate tags must be handled
prior to matching and generating transactions.
15
6. Match Scanned Data w/ Scan Scope
The Generate Results step in the PI Process
matches the scanned data against the scan scope
defined earlier. The results are viewed via the
Review Matching Results page. Click a line for
more detailed information about the entry
16
6. Match Scan Data w/ Scan Scope
17
Types of Match Results - Status

• All match results are marked with a status
• Inventory - Assets that were expected to scan and
  did scan. The asset was defined in the scan scope
  and collected in the scan data.
• Over - Assets that were not expected to scan, but
  did scan. These assets were collected in the scan
  data but not defined in a scan scope.
• Under - Assets that were expected to scan, but
  did not scan. Defined in a scan scope but not
  collected in the PI scan data.

18
Types of Match Results - Flags

• Match results may also be marked by a flag
• Result in Error indicates the asset could not be
  processed any further due to one of three
  conditions
• If any duplicate tags still exist in the scanned
  data, the results generated for those duplicates
  will contain errors.
• A scanned asset is recorded as retired in AM.
• A scanned tag was found for an asset in a
  business unit other than the one for which youre
  processing Physical Inventory.
• Manual Review Required is set if the scan
  operator requested a special review of the asset.
• These flags are fixed manually in Core-CT.

19
7. Generate Transactions

• The Generate Transactions step of the PI
  process creates transactions that reconcile the
  data in Core-CT Asset Management with the results
  of the physical inventory.
• Transactions are processed through the AM
  interface. They are reviewed, and loaded into AM
  via the Transaction Loader process.

20
Questions