Seamless Inspection through Repeated Rechecks
With FASTEC 4 PRO Version 3.4.9, rechecks are repeated until a successful inspection is completed. Until now, the number of rechecks was limited to the predefined levels in the configuration. In the new version, a repeat rule can now be set at the final level of a recheck chain. When activated, the corresponding recheck is automatically triggered again until it is successfully completed.
This ensures a seamless inspection process – regardless of the originally defined number of levels. Users increase both process and product quality and gain more flexibility in the configuration of inspection processes.
Flexible Documentation of Unplanned Repairs Directly in the Process
In day-to-day maintenance operations, unplanned repairs are a frequent occurrence, with the specific tasks required often only becoming clear during execution. Rigid checklists are insufficient in such cases – important measures may not be documented at all or only partially. What’s missing is the ability to spontaneously capture additional inspection points directly within the process.
With the new feature in FASTEC 4 PRO, checklists can be extended directly within the production client – even after an order has already been created. This provides greater flexibility for documenting repairs directly at the terminal and ensures complete traceability of spontaneous maintenance actions.
Maximilian Claes, Team Lead Product Management
In addition, a unified user interface for the office and production client is created, along with improved communication and handover between shifts or technical teams.
Multi-Level State Logic for Complex Data Structures
FASTEC 4 PRO version 3.4.9 offers users a tree structure for categories. The previous three-level hierarchy (Category / Status / Free Text) was predefined and did not provide sufficient depth for many real-world application scenarios. The new version now allows for multi-level nesting within the categories. The assignment of a status to exactly one category remains unchanged. In the views, the new structure is displayed as a path, e.g., “Malfunction > Mechanics > Bearing Defect.”
What this means for customers: They can now map complex status logics within individual company structures and perform precise and differentiated analyses.
