AyMINE – Technical documentation
Modules
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Adminitration of areas, projects, calendars
Region / project / methodology
Change management process in a project
GDPR and record of qualifications
Qualification of user or contact
Right to Manage Qualifications
Failure Analysis for an Individual Property of a Component or Process
FMEA – Probability of Detection
FMEA – Probability of Occurrence
Task, project & quality management
Administration of the Task Management Module
System rights for the task management module
Methodology and Quality Management systems
What a methodology / QMS consists of
Collaborative Resolution of Multiple Problems
Customer Service Response Generation
Incident and Quality Issue Management
Objects affected by the problem
Problems, Incidents, Helpdesk Tickets
Return project plan by baseline
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
The person responsible for the task
Working procedure – task definition
Contacts and directories module (CRM)
Web management and automation
Human resources
Products, assets and sales
Technical Modules
Enterprise Architect connector
System Modules
The AyMINE Framework Module
System Management
Additional functions with files
Copying and moving files between objects
Files (documents) linked to the object
Formatted texts in the application
Gateway settings for external messages
IMP gateway settings for email communication
Internet Call Gateway Settings
Message with the outside world
Record template
A record template allows you to define a template for a log or other work record.
Patterns of protocols are part of the IQMS and and they are documented by the methodology
A record generally means any outputs that need to be used to document the progress of an activity and its outcome. However, a sample record can generally be used for any pattern where you need to prepare a template for the documents being created in the methodology.
Typical examples of a record are:
- Test record
- Check record
What sample records are not suitable for
Automatically generated records
AyMINE automatically creates activity records. For the creation of automatic records, templates are not used, they are generated by the system with standard functionality. They save a lot of time and it is therefore advisable to use them wherever possible.
If automatic records are sufficient to record an activity, a template is useless, it would also be confusing for workers.
Objects supported by the system
In quality systems, there are often records e.g. for reporting a bug or a problem. AyMINE supports these and a number of other common agendas and has directly prepared objects for recording. It is advisable to use them, because in addition to the possibility of a more accurate description, they also support the process of processing them. In addition, the processed template would be, as in the previous case, confusing for workers.
Pattern as a record or a separate document?
Records often require the completion of a precisely prescribed form. For this, it is best to create a template in the format of an editable PDF with prepared fields. The sample PDF can be stored in the attachments of the sample record.
Similarly, if there are pre-prepared patterns e.g. a spreadsheet editor (Libre Calc etc.) it is possible to upload them into the pattern.
If, for example, a chcek klist – a check sheet needs to be filled in, it is preferable to use the AyMINE document directly, workers will not have to open separate documents and there is no risk that they will forget to insert the completed form into the system.
In general, if there is a sufficient record directly in AyMINE, it is preferable to a separate document. However, AyMINE supports both variants – as the AyMINE document directly and the attached template.