How To
- Approve order function.
- Cost Activities
- How does the “Approved Supplier” (QA status) functions work?
- How does the Approve direct purchases onshore work?
- How does the rule-based approval matrix work?
- How To - Set Failure Report Running Number
- How To - Add SQL Server to Windows Firewall Exception
- How To - Access the report template editor
- How To - Accounts and Budget (v. 2.662 and later)
- How To - Active a unit for use with the Incidents Module
- How To - Add same document on multiple components
- How To - Approve Purchase Orders and Change Requests when using Approval Rules and Change Approval
- How To - Assign user rights
- How To - Automatically resize images
- How To - Backup TMv2
- How To - Cancel Job History (Job Signed Out In Error)
- How To - Cancel job history (Video Link)
- How To - Catalogs
- How To - Change a Unit Code in TM Master V2
- How To - Check for File Not Found Error. Document Handling.
- How To - Circulating Components
- How To - Company tags
- How To - Connect the TM Master v2 Client Application
- How To - Connect the TM Master v2 client to more than one database
- How To - Contract Management
- How To - Copy Components, Component Jobs and Spare Parts
- How To - Create a new unit
- How To - Create a New User TM Master v2
- How To - Create and use batch jobs in TM
- How To - Create Credit Note
How To - Generate NCRs from Overdue Critical Jobs
It is possible for TMv2 to automatically generate a non-conformance report (NCR) if a critical job becomes overdue by a certain period.
NOTE: The NCRs will only be generated from a vessel installation (to avoid both sides triggering generation) and therefore this feature requires a replicating system.
The following criteria must be met:
- 'System > Settings > General Settings > Do NCR Calculations' must be ticked at each of the vessel installations.
- The v2 service must be running. Each time the service loops, it will check for any new overdue critical jobs and create NCRs.
- The critical jobs must have a critical category code set. If you go to 'Administration > Codes > Critical Category', you can give each code a 'Non-Deviation Period'. This is the amount of days that the job is allowed to go overdue before an NCR is created.
If all of the above requriments have been satisfied, each time the service loops at the vessel it will check for any critical jobs that are overdue by more than their non-deviation period as defined by their critical category code. Any jobs meeting this criteria will trigger a new NCR to be created. This will be replicated back to the office
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article