What you’ll learn
How CRIBWISE tracks each serial number of a serialized item: the seven statuses an instance can hold, what the instance detail shows, and what the documents, history and comments tabs are for.
When an item is set as serialized, the Serialized item tab appears on the item and lists every serial number that exists, with its current location and status.
Serialized item statuses
| Status | Set when |
| New | The default. The item was restocked from a purchase order, or the instance was created during assignment. It has not been used in production yet. |
| Used | The item has been picked and returned as used. |
| Refurbished | Service has been performed. Set when the item is restocked from service. |
| Scrapped | The item cannot be used any more – returned as scrap, scrapped from a service order or list, or the loan time was exceeded with an auto scrap period. |
| For service | The item was returned for service, or automatic service rules triggered it. It is not offered for pick, and it can be added to a service list or service order. |
| In assembly | The item was picked to create a new assembly. It is a permanent part of that assembly and cannot be picked or serviced separately. |
| In service | The item is currently picked for service against a service list or service order. |
The instance detail
To see more about a serial number, select it in the list and press 
to open the instance detail.
General information
This tab shows the condition of the item, its current location and its service information. If the instance is picked for service or transfer, the related service order, service list or transfer list is shown as the current location.
When the item is set to be serviced, these fields appear:
| Field | What it shows |
| Target service date | The date the instance will automatically be set to service. Selected with a date picker. |
| Last service | The date of the last service, meaning the date of restock from a service order or list. |
| Service interval ends | For time-based automatic service: the date the instance will be set to service, from the rules Time after first use and Time interval on the item definition. If both are used, the closest date is shown. |
| Time picked remaining | For service based on time in production: the time left before the instance is set to service, from the rule Time picked and the total picked time of the instance. |
| Remaining # of picks | For service based on number of picks: the picks left before the instance is set to service, from the rule Number of times used and the total picks of the instance. |
Note: Both Target service date and Service interval ends can be set on one instance – the first date wins. Where several service rules apply, the instance is set to service as soon as any one of them is fulfilled.
Change instance status
Statuses are handled automatically by the operations performed on the SFI, so there is normally no reason to change one by hand. Special cases exist – an instance picked in service whose order or list was deleted, or restoring an instance that was scrapped by mistake.
To change it, press 
next to the instance status and confirm the new state.
Warning: Changing an instance status manually can lead to unexpected behaviour in the SFI and misleading transaction data. Proceed with caution.
Documents
Any number of documents can be added to a serial number. A document can be of any type, up to 10 MB.
 |
Creates a new document |
 |
Deletes the selected document |
 |
Updates the selected document |
 |
Downloads the selected document |
History
This tab shows every transaction related to the instance. Press 
to open the full transaction report in the standard report viewer, where you can filter it further or export it.
Comments
This tab shows all user comments on the instance, whether they were created from the Admin Portal, the SFI or the API. Comments are also visible on the SFI during any flow that works with serialized items, and operators can add new ones there.
To open an existing comment, press . To create one, press 
, fill in the text and confirm.
Common confusion
| People often think… | But actually… |
| Instance statuses are maintained by an administrator. | They follow automatically from operations on the SFI. Manual changes are for exceptions only. |
| An item in assembly can still be serviced on its own. | It became a permanent part of the assembly and can no longer be picked or serviced separately. |
| Only one service rule can apply. | Several can. The instance goes to service as soon as the first of them is fulfilled. |
| Comments are Admin Portal only. | They can be created from the Admin Portal, the SFI or the API, and operators see them during SFI flows. |
Take action
Need to create one? See How to create and assign a serialized item. To trigger service automatically from usage, see How to set up tool life tracking and automatic service triggers.
Related articles
- How to create and assign a serialized item – create the item and its first instances.
- How to set up tool life tracking and automatic service triggers – automatic service based on consumed tool life.
- Understanding service scripts: automated calibration checks – how items set For service reach a service order.
- Understanding the serialized item overview – all serial numbers across the system in one list.