• Get started
  • Documentation

Data Manager - Compute (object class)

Assets Data Manager for Jira Service Management Cloud is currently rolling out in Open Beta and will be available to all Premium + Enterprise sites by end of October 2024.

The Compute object class is a default object class that is included in Assets Data Manager out-of-the-box. The compute object class is often used to hold information about:

  • Laptops

  • Desktop

  • Physical and virtual servers (on-prem and cloud)

  • Mobile devices

  • Tablets

Default Attributes

The Compute object class includes the following default attributes:

These default attributes were selected based on the most common attributes relevant for cross-comparative analysis. There may be additional attributes that are specific to individual sources only (e.g. AssetStatus and OperationalStatus).

We recommend managing those directly in the source system (e.g., an Asset schema) to prevent the Data Manager from overwriting their values. Where statuses from different tools need to be compared, we recommend using an additional status column.

Attribute Name

Description

Assets Data Manager Data Type

1

Name

The name of the object.

String

2

LastUpdatedInAssetsSchema

 

Date/Time

3

AssetTag

 

String

4

FirstDiscovered

Date the record was first seen in any tool.

Date/Time

5

LastUserUpdate

The date a user manually updates a record in the source system.UpdatedByUser.

String

6

UpdatedByUser

The user that last updated the record in the source system.

String

7

Manufacturer

 

String

8

ModelName

 

String

9

ManufacturerPartNumber

 

String

10

MaintenanceContract

 

String

11

PONumber

 

String

12

InvoiceNumber

 

String

13

PurchaseDate

 

String

14

PurchasePrice

 

Decimal

15

Currency

All prices on this record will be represented in this currency.

String

16

DepreciationMethod

 

String

17

DepreciationPeriod

Deprecation period (in years).

String

18

DepreciationRate

 

Decimal

19

RefreshDate

 

Date/Time

20

InstallDate

 

Date/Time

21

DeliveryDate

 

Date/Time

22

DisposalDate

 

Date/Time

23

LastScanDate

The date that dynamic inventory was provided.

Date/Time

24

UpdatedBySystem

User name or system last updated by (eg Discovery)

String

25

LastPhysicalAuditDate

The date that the record was last physically audited.

Date/Time

26

LastPhysicalAuditor

Can be system generated through inventory auditor tool OR a person

String

27

OwnershipType

Used to identify if the device is Company Owned, BYOD, Leased etc.

String

28

OwnerGroup

The group that is financial responsible for the asset.

String

29

InfrastructureType

Calculated Attribute - "InfrastructureType".

This attribute is Computed.

String

30

Platform

Normalised OS Version type (Windows, Linux, Unix, zOS etc), as per Data Manager platforms

This attribute is Computed.

String

31

OSVersion

This attribute is Computed.

String

32

OperatingSystem

 

String

33

OSServicePack

 

String

34

FullOSVersion

Ability to report to the build version, important for Evergreen operating systems

String

35

Environment

The environment that this end point reside in

String

36

SupportGroup

The group that is responsible for maintaining/supporting the asset

String

37

IMEI

The IMEI reference of the device

String

38

PhoneNumber

The phone number allocated to this device

String

39

IPAddress

 

String

40

MACAddress

 

String

41

DomainName

 

String

42

GeneralAvailability

When was this model become available on the market?

Date/Time

43

EndOfSupport

When will support no longer be available from the supplier?

Date/Time

44

EndOfSale

When was the model no longer for sale.

Date/Time

45

HostedIn

What cloud provider hosts this endpoint?

String

46

ResourceID

Unique ID from cloud provider (eg Azure)

String

47

InstanceID

Unique ID from cloud provider (eg AWS)

String

48

AssignedToUser

Who is the device assigned to?

String

49

AssignedToService

What system/service is the device assigned to?

String

50

CalculatedUser

From discovery sources to show who the last user is (EUC only)

String

51

IsVirtual

 

Boolean

52

Host

What HOST is the VM running on?

String

53

VMType

 

String

54

MemoryRAM

 

Integer

55

DiskSpace

 

Integer

56

ProcessorType

 

String

57

Processors

 

Integer

58

Cores

 

Integer

59

Sockets

 

Integer

60

CostCenter

 

String

61

Location

 

String

62

Department

 

String

63

WarrantyEndDate

 

Date/Time

64

ExtendedWarrantyContract

 

String

65

ResalePrice

The price that the asset was resold at.

Decimal

66

ResidualValue

The estimated value of a fixed asset at the end of its lease term or useful life

Decimal

67

WrittenOffValueremove AsPerCurrency

 

Decimal

68

LeasePrice

 

Decimal

69

LeaseContract

 

String

70

LeasePrice

 

Decimal

71

LeaseCost

 

Decimal

72

LeaseCostFrequency

How frequently does the lease need to be paid?

String

73

LeaseStartDate

The date the lease starts

Date/Time

74

LeaseEndDate

The date the lease ends

Date/Time

75

LeaseTerminationDate

If the Lease was terminated, rather than running its course, what was the date it was terminated?

Date/Time

76

LeaseTerminationReason

 

String

77

RetirementDate

 

Date/Time

78

RetirementReason

 

String

79

Vendor

The company where the product was purchased from

String

Default Computed Dictionaries

Computed Dictionary

Usage

Source Attribute/s

Destination Attribute

OSVersion

Used to normalize the various operating systems into one clean label.

For example, our data source might contain values like WinXP, OS_WinXP, and Windows XP Professional x64, three separate values that actually refer to the same thing: Windows XP.

OperatingSystem

OSVersion

Platform

Used to group the OSVersions into platforms like Windows, Linux etc

OSVersion (Computed)

Platform

InfrastructureType *

To enable grouping of endpoints into a type like Physical, Virtual, or Cloud Servers, Containers, Laptops or Desktops, etc.

Manufacturer, ModelName

InfrastructureType

* Raw data for these Computed Dictionaries are not provided, but rather, the Computed Dictionary fields are set up. Upon your first Import, the system will generate the Computed Issues; which will require mapping.

Still need help?

The Atlassian Community is here for you.