Asset CSV

Asset records correspond to a physical asset register. They are separate from the records of inventory devices, just as an asset register is separate from the physical devices it lists. The asset records and inventory device records are linked. (In the following table, long attribute names have been wrapped for publication, but in the CSV files each is one unbroken string.)

Table 1. Spreadsheet columns for `Asset` DDI
Column	Details
`AcquisitionMode`	Type: String. Optional. Maximum: 100 The acquisition mode. Standard modes are: `Purchased` `Leased` `Rented` `Loaned`. If no value is specified for a new asset, no value is set in the database record. For single tenant on-premises implementations, new acquisition modes will be created for non-existing values. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.)
`AssetName`	Type: String. Mandatory. Maximum: 256 The name of the computer or a brief description of the asset.
`AssetStatus`	Type: String. Optional. Maximum: 100 The asset's status. Standard values are: `Purchased` `In Storage` `Installed` `Retired` `Disposed` `Other`. If no value is specified for a new asset, the value will set to `Purchased`. For single tenant on-premises implementations, new asset status values not yet in the compliance database but found in the incoming data will be created automatically. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.) Tip: Setting the `AssetStatus` to any of `In Storage`, `Retired`, or `Disposed` for import through the Business Importer excludes the device linked to the asset record from license consumption calculations. Setting `AssetStatus` by this method does not: Remove installation records for the linked device Remove individual license allocations for the linked device. Those effects rely on the status being changed through the web interface for IT Asset Management.
`AssetTag`	Type: String. Optional. Maximum: 256 The asset tag that identifies the physical device. This may be something like a barcode number.
`AssetType`	Type: String. Optional. Maximum: 64 The asset type. Standard types are: `Workstation` `Server` `Monitor` `Desk` `Chair` `Printer` `Router` `Switch` `Telephone` `Cell phone` `Laptop` `Mobile Device`. If no value is specified for a new asset, the `Workstation` value is used. For single tenant on-premises implementations, new asset types are created for incoming non-existing values (so beware of typographical errors): for behavior and presentation, the `Workstation` template will be applied to these new types. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.)
`AssignToUser`	Type: String. Optional. Maximum: 128 The employee number of the asset assigned user. The user must exit in the compliance database; if not, the value will be discarded.
`BusinessUnit`	Type: String. Optional. Maximum: 500 (64) The business unit of the asset: the name of the last level or some of the last levels or all levels. Level and sub-levels must be separated by the forward slash [`/`] character. The maximum size for each level is 64 characters.
`Category`	Type: String. Optional. Maximum: 500 (64) The category of asset: the name of the last level or some of the last levels or all levels. Level and sub-levels must be separated by the forward slash [`/`] character. The maximum size for each level is 64 characters.
`ChargesAmount`	Type: Float. Optional. Maximum: - Amount to be charged back for the use of this asset.
`ChargesFrequency`	Type: String. Optional. Maximum: 100 The frequency with which the charge back price is charged. Standard values are: `None` `Weekly` `Monthly` `Quarterly` `Yearly` `Lump Sum`. If no value is specified for a new asset, no value is set in the compliance database. For single tenant on-premises implementations, new period descriptions will be created for non-existing values. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.)
`Comments`	Type: String. Optional. Maximum: 4000 Comments entered about the asset.
`ContractNo`	Type: String. Optional. Maximum: 60 The contract number (foreign key) for any contract attached to the asset.
`CostCenter`	Type: String. Optional. Maximum: 500 (64) The cost center of the asset: the name of the last level or some of the last levels or all levels. Level and sub-levels must be separated by the forward slash [`/`] character. The maximum size for each level is 64 characters.
`CurrencyCode`	Type: String. Optional. Maximum: 32 The currency code must match an existing currency code in. See the list in Currency Codes.
`CurrencyDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. Date the exchange rate is valid.
`CurrencyRate`	Type: Float. Optional. Maximum: - The currency exchange rate against the default currency value set in System Defaults.
`CurrencySnapshotName`	Type: String. Optional. Maximum: 256 The name of the conversion rate snapshot to be applied to currencies in this import, when converted to the default currency. This must be an exact match for an entry in the `SnapshotName` column of the `CurrencyRateSnapshot` table of the compliance database.
`DeliveryDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The delivery date.
`Depreciation CurrentValue`	Type: Float. Optional. Maximum: - The current value of the asset.
`DepreciationMethod`	Type: String. Optional. Maximum: 100 The depreciation method. Standard values are: `Straight Line` `Residual Value`. If no value is specified for a new asset, no value is set in the compliance database. For single tenant on-premises implementations, new depreciation methods will be created for non-existing values. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.)
`DepreciationPeriod`	Type: Integer. Optional. Maximum: - The depreciation period (in years), used only for straight line depreciation.
`DepreciationRate`	Type: Float. Optional. Maximum: - The percentage per year that the asset depreciates, expressed as a decimal fraction. For example, 33% p.a. should be represented as `0.33`. This property is used only for residual value depreciation.
`Depreciation ResidualValue`	Type: Float. Optional. Maximum: - The residual value of the asset.
`DisposalDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The date the asset was disposed of.
`EndOfLifeRecipient`	Type: String. Optional. Maximum: 128 The person or organization who received the asset when it was disposed of.
`InstallationDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The date the asset was installed.
`InventoriedBy Electronic`	Type: String. Optional. Maximum: 64 The name of the tool used to perform inventory on the assets. This property is overwritten by inventory imports.
`InventoriedBy Physical`	Type: String. Optional. Maximum: 64 The name of the person or tool that performed the last manual inventory.
`InventoryDate Electronic`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The date the asset last had inventory reported through software. This property is overwritten by inventory imports.
`InventoryDatePhysical`	Type: Date. Optional. The date the asset last had inventory updated (entered) manually.
`LeaseAgreement`	Type: String. Optional. Maximum: 200 The contract name of the lease agreement for this asset. This must be an exact match for a `ContractName` property of an entry in the `Contract` table of the compliance database. (For consistent data, this same contract should have a ContractTypeID of `2`, which represents a lease agreement.)
`LeaseBuyoutCost`	Type: Float. Optional. Maximum: - The cost to purchase this asset at the conclusion of the lease agreement. Depending on the agreement, this may be specified as $1 (a 'dollar buyout'), a price specified in the agreement, or the 'fair market value' of the asset at the expiry of the lease.
`LeaseEndDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The date that the current lease on this asset runs out. (For early termination, you may prefer to use `LeaseTerminationDate`.)
`LeaseNo`	Type: String. Optional. Maximum: 60 The contract number of the lease agreement for this asset.
`LeasePeriodicPayment`	Type: Float. Optional. Maximum: - The value of recurring payments for this individual asset as defined in its lease agreement. This is sometimes called the 'lease rate'.
`LeasePeriodType`	Type: String. Optional. Maximum: 1000 The frequency with which recurring payments are made. The value should match a `PeriodTypeDefaultValue` in the `PeriodType` table in the compliance database. Standard values are: Weekly Monthly Quarterly Yearly Lump Sum. For single tenant on-premises implementations, new period types will be created for non-existing values. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.)
`LeasePrice`	Type: Float. Optional. Maximum: - You may use this field to record a total liability under a lease agreement, or other purposes as you require. Keep in mind that you have separate fields for: The regular rental payments for the assets covered by the lease (see `LeasePeriodicPayment`) A buyout figure to take over ownership of the assets at the expiry or termination of the lease (see `LeaseBuyoutCost`)
`LeaseStartDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The date that the lease on this asset became effective. In general, this is the date from which you may use rented assets, and from which payment schedules are measured.
`LeaseTerminationDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The date that the lease on this asset was terminated. Normally, use this field for early termination of the lease. If a lease expires in the normal course of business, you may prefer to use `LeaseEndDate`.
`LeaseTerminationReason`	Type: String. Optional. Maximum: 100 The reason that the lease for this asset was terminated. Value must be matched in the `DefaultValue` column of the `LeaseEndReason` table of the compliance database. Standard values are: `Lease Ended - Asset Returned` `Early Termination - Asset Returned` `Buyout` `Early Buyout` `Trade`. For single tenant on-premises implementations, lease end reasons will be created for non-existing values. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.)
`Location`	Type: String. Optional. Maximum: 500 (64) The location of the asset. The value can be specified as a single description level or as levels and sub-levels separated by the forward slash [`/`] character. The maximum size for each level is 64 characters.
`ManufacturerName`	Type: String. Optional. Maximum: 200 The name of the manufacturer.
`ManufacturerPartNo`	Type: String. Optional. Maximum: 100 The manufacturer's part number.
`ModelNo`	Type: String. Optional. Maximum: 200 The model number.
`ResalePrice`	Type: Float. Optional. Maximum: - The amount the asset was sold for.
`RetirementDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The date the asset was retired.
`RetirementReason`	Type: String. Optional. Maximum: 100 The reason the asset was disposed of. Standard values are: `Lost` `Stolen` `Disposed` `Sold` `Donated` `Broken`. If no value is specified for a new record of an asset, no value is set in the compliance database. For single tenant on-premises implementations, retirement reasons will be created for non-existing values. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.)
`SerialNo`	Type: String. Key. Mandatory. Maximum: 150 The asset's serial number. Used to link to incoming records of inventory devices.
`WarrantyEndDate`	Type: Date. Optional. For formats, see Entering Dates in the CSV Templates. The warranty expiration date.
`WarrantyType`	Type: String. Optional. Maximum: 100 The type of warranty. Standard values are: `None` `One Year on site` `Three years on site`. If no value is specified for a new asset, the value is set to `None`. For single tenant on-premises implementations, new asset warranty types will be created for non-existing values. (Not supported for multi-tenant implementations for managed service providers, nor for cloud implementations.)
`WrittenOffValue`	Type: Float. Optional. Maximum: - The value of the asset at time of retirement/disposal.

IT Asset Management (Cloud)

Current