Data Manager - Network (object class)

Assets Data Manager for Jira Service Management Cloud is a Premium and Enterprise only feature that is currently in Open Beta development. View and vote on our list of upcoming features.

If you find a bug or have questions, please reach out to Atlassian Support or the Atlassian Community.

The Network Object Class is a default object class that is included in Assets Data Manager out-of-the-box.

The Network Object Class is often used to hold information about:

Routers
Switches
Hubs
Firewalls
Load balancer
Wireless access points
Network adaptors

Default Attributes

The Network 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 Data Manager from overwriting their values.

	Attribute Name	Description	Assets Data Manager Data Type
1	Name	The name of the Network.	String
2	LastUpdatedInAssetsSchema		Date/Time
3	AssetTag		String
4	SerialNumber	The serial number of the device.	String
5	FirstDiscovered	Date the record was first seen in any tool.	Date/Time
6	LastUserUpdate	The date a user manually updates a record in the source system.UpdatedByUser.	String
7	UpdatedByUser	The user that last updated the record in the source system.	String
8	Manufacturer		String
9	ModelName		String
10	ManufacturerPartNumber		String
11	MaintenanceContract		String
12	PONumber		String
13	InvoiceNumber		String
14	PurchaseDate		String
15	PurchasePrice		Decimal
16	Currency	All prices on this record will be represented in this currency.	String
17	DepreciationMethod		String
18	DepreciationPeriod	Deprecation period (in years).	Integer
19	DepreciationRate		Decimal
20	RefreshDate		Date/Time
21	InstallDate		Date/Time
22	DeliveryDate		Date/Time
23	DisposalDate		Date/Time
24	LastScanDate	The date that dynamic inventory was provided.	Date/Time
25	UpdatedBySystem	User name or system last updated by (eg Discovery)	String
26	LastPhysicalAuditDate	The date that the record was last physically audited.	Date/Time
27	LastPhysicalAuditor	Can be system generated through an inventory auditor tool OR a person	String
28	OwnershipType	Used to identify if the device is company-owned, BYOD, Leased, etc.	String
29	OwnerGroup	The group that is financially responsible for the asset.	String
30	IsVirtual	This attribute is Computed.	String
31	InfrastructureType	This attribute is Computed.	String
32	Firmware	The firmware and version (as provided by discovery).	String
33	Environment	The environment that this endpoint resides in	String
34	SupportGroup	The group that is responsible for maintaining/supporting the asset	String
35	IPAddress		String
36	MACAddress		String
37	PortNumber	Network port used.	String
38	DomainName		String
39	GeneralAvailability	When did this model become available on the market?	Date/Time
40	EndOfSupport	When will support no longer be available from the supplier?	Date/Time
41	EndOfSale	When was the model no longer for sale?	Date/Time
42	MemoryRAM		Integer
43	DiskSpace		Integer
44	CostCenter		String
45	Location		String
46	Department		String
47	WarrantyEndDate		Date/Time
48	ExtendedWarrantyContract		String
49	ResalePrice	The price that the asset was resold at.	Decimal
50	ResidualValue	The estimated value of a fixed asset at the end of its lease term or useful life	Decimal
51	WrittenOffValue		Decimal
52	LeaseContract		String
53	LeasePrice		Decimal
54	LeaseCost		Decimal
55	LeaseCostFrequency	How frequently does the lease need to be paid?	String
56	LeaseStartDate	The date the lease starts	Date/Time
57	LeaseEndDate	The date the lease ends	Date/Time
58	LeaseTerminationDate	If the Lease was terminated, rather than running its course, what was the date it was terminated?	Date/Time
59	LeaseTerminationReason		String
60	RetirementDate		Date/Time
61	RetirementReason		String
62	Vendor	The company where the product was purchased from	String

Default Computed Dictionaries

Computed Dictionary	Usage	Source Attribute/s	Destination Attribute
IsVirtual*	Identifying if a network device is virtual or physical	Manufacturer, ModelName	IsVirtual
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.

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community