Tasks are internal processes included in a bill of materials. They are elements assigned and scheduled to capture execution times by any system user. Examples of tasks would be: design, review, and validate received documentation, generate and sign drawings by an engineer, send drawings to the client for validation, archive drawings in a document, etc.
The problem with this distribution is the number of tasks that would need to be performed. This makes timekeeping complex and hampers objectives. To reduce the number and facilitate searches, Selenne ERP has created qualified tasks.
This creates a single timetable task to which different characteristics, criteria, and actions can be linked. In other words, the same task is grouped with related and added elements according to the steps to be performed, but for which no time clocking is required, since only the times for the main task are recorded. This is freely selectable and its use is completely flexible for each case.
Example of a qualified task:
DESIGN
Review and validate received documentation
Generate and sign drawings by an engineer
Send drawing to the client for validation
File drawing in a document
In this example, design is an assignable and schedulable task, and this is where the signing would take place. It would also have four characteristics and sequences to perform: Review and validate received documentation, Generate and sign drawings by an engineer, Send drawing to the client for validation, and File drawing in a document.
In Selenne ERP, you can create and modify as many characteristics, actions, and internal quality criteria as the company needs to link them to a task and qualify it. Additionally, you can apply behaviors to them, such as making them mandatory and using validators to ensure compliance with the sequences defined in each task. That is, if all mandatory checks are not completed, the task and the phase to which it belongs cannot be closed. But, in addition to the mandatory checks, there are many other options to expand the qualifications of each of these dynamic fields, such as descriptions, codes, values, certificates, etc.
