1.1 Components
The Parts component on the go Service Management plugin corresponds to the present ServiceNow Configuration Item model. This model is also used in the Enterprise CMDB Plugin. The Field Service control plug-in adds the ideas of consumable to locate quantity and component number to facilitate choice. To get more details, see Enterprise CMDB Plugin.
There are two main forms of parts:
Consumable components are traced because of the system quantitatively. Whenever component is used or set up within service purchase location, the total amount of that component is updated in system. Observe that characteristics, such as for example in which the consumable part happens to be installed, are not tracked.Non-consumable parts match configuration things defined up-front within the system. The entire life period of configuration items is tracked by monitoring modifications of status and area. A configuration product developed or changed inside system becomes an inventoried part as long as it satisfies here conditions:
- CI place is a warehouse at this time defined into the system
- Model ID is a part at this time defined in the system
The creation, change, or deletion of a setup product immediately updates the total amount of the non-consumable part for sale in the system. For more detail by detail information, see .
1.2 Warehouse Kinds
To optimize component choice, the warehouse kind has two significant traits:
- Priority: proposes the order of warehouses the parts should-be sourced from. Example: in the event that “Field Agent car” associated with assigned representative offers the required component, it must be preferred into “Central Warehouse” due to the fact component in the Agent’s car will not need distribution
- Shipment Required(true/false): informs the machine if “transfer order” creation will undoubtedly be essential in the event that component is sourced through the warehouse regarding the given kind. Example: the part inside “Field Agent Vehicle” wont need shipment so no transfer order needs to be produced.
At this time, the Field provider control plugin defines the following types of warehouses:
CI Hardware Reputation | CI Hardware Sub-Status | Stock Status | Inventory Sub-Status |
in_stock | available | ||
reserved | |||
out_of_stock | ordered | ||
awaiting_vendor_delivery | |||
gotten | |||
deferenced | |||
faulty | repairable | ||
throwaway | |||
in_transit | |||
pending_transfer | |||
installed’ | in-use | ||
in_maintenance | |||
in_disposition | |||
retired | lost | ||
sold | |||
credit | |||
divested | |||
taken | |||
contributed | |||
scrapped | |||
duplicate_error | |||
on_order | |||
pending_install | |||
pending_repair |
The stock Management add-on enables to create a brand new transfer purchase for all the part motion inside business warehouse system and outside it. This is done through the devoted component known as Create Transfer Order.
3.1 Create Transfer Purchase Form
The image below shows an example of an empty New Transfer Order. Many areas into the type are interdependent. After info is registered into one field, other areas uses the guide qualifiers to restrict the readily available information.
These industries tend to be interdependent:
- Component
- Stock Item
- Configuration Item
- From warehouse
3.2 Stock Item referenced by Transfer Order Form
After the mandatory fields tend to be filled-in, plus the new transfer purchase is posted, the device creates the new Inventory Item Line matching to Pending Transfer condition. This line is truly referenced because of the stored Transfer purchase as shown on the screens above and below (orange arrows).
The screenshot shows the Create TO Form before the record is submitted.
This screen reveals the condition of Transfer Order conserved and reopened. The stock Item referenced changed to Pending.
After the inside is gotten and acknowledged, the display appears as follows, because of the stock Item in brand-new location.
From Inventory Management point of view, the status of the stock role USB10 USB Cable is presented on stock Form as shown.