Skip to content

Inventories

The JAG-Node System offers a comprehensive solution for managing and conducting inventory counts. With this function, companies can efficiently conduct and manage both complete and partial inventories of their fabric rolls and components.

Basic Concept

The foundation of the inventory system consists of inventory templates that serve as reusable templates for regular inventories. When creating a template, users can set various basic parameters. This includes a flexible naming and description scheme that is dynamically adjusted through placeholders such as current date, time, or sequential numbers. Print templates can be stored for later documentation, which are used for automatic PDF generation.

A particularly useful feature is the ability to set up automatic repetitions. These can be defined using standard intervals or precise cron expressions, allowing even complex inspection cycles to be mapped. For example, an inventory can be automatically triggered every workday at 9 AM or every 4 hours.

Inventory Types

The system distinguishes between two basic types of inventories: complete inventories and partial inventories. In a complete inventory, all objects in the selected warehouses are subject to inspection. The special feature here is the booking process - changes only take effect when the entire inventory is completed and manually finalized. This enables a comprehensive review of all entries before the final stock update.

Partial inventories, on the other hand, focus on a defined selection of objects. The system automatically selects these based on predetermined criteria, where recently checked objects can be excluded or certain quantity thresholds can be considered. A key difference from complete inventory is that bookings are made directly after each individual object inspection. Once all planned inspections are completed, the partial inventory is automatically finalized.

Execution

The practical inventory process begins with starting the inventory, for which the system offers three different options. Users can either start the inventory via the detail view, scan the first inspection object, or use the start button in the scan view. This flexibility accommodates different workflows.

The actual inspection is carried out via the scan page, where objects are recorded via barcode scan. Various inspection characteristics can be checked for each object, which can be divided into logical groups or steps. Deviations are documented and can be supplemented with photos and additional remarks if needed. If errors occur during an inspection, it can be corrected by rescanning the object.

A particularly practical function is the ability to manually add additional inspection objects during an ongoing inventory. The system automatically prevents conflicts by blocking objects that are already recorded in other active inventories. If an object to be inspected cannot be found, authorized users can mark this accordingly in the system.

Completion and Documentation

The completion of an inventory varies depending on the type. While partial inventories are automatically finalized once all inspection objects have been checked, a complete inventory requires manual completion. Upon finalization, the system generates a checksum that ensures the integrity of the recorded data.

For documentation purposes, the system automatically creates PDF documents, both as an overall inventory overview and as individual documents for each inspection object. A detailed history records all actions, and a progress overview provides insight into the current status of the inventory at any time.

The system uses a clear status concept: A new inventory starts in "New" status, changes to "In Progress" during execution, and is finally marked as "Finalized". If needed, an inventory can also be terminated early.

Security and Control

Security and traceability are ensured through various mechanisms. A differentiated rights management controls access to various functions, while automatic blocking of objects prevents conflicts in parallel inventories. Every change is logged and traceable. The checksum generated upon completion ensures that subsequent changes to the inventory data are detectable.