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
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
Objects related to the task pattern
Contacts and directories module (CRM)
Order overview for customer groups
Contacts and directories module (CRM)
System Permissions and CRM Module Settings
Send bulk messages in compliance with GDPR
How to correctly forget a person's details
Unsubscribe and set preferences
for bulk mail
Web management and automation
Receiving a message from the web
Human resources
Personalistics – User Permissions
Human Resources module security
Manage department / division data
Overview of Personnel Information for pracov# Employment Contract
Synchronizing staff and system users
Products, assets and sales
Received order for goods or services
Finance management
Metrics and Measurements
Technical Modules
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
Enterprise Architect connector
System Modules
The AyMINE Framework Module
AyMINE — Tips for Mobile Usage
Configure how your system looks and works
Gestures and Keyboard Shortcuts
More about how the system works
Private notes and tags for objects
Overview of Modules and Record Types
Filtering in the list of records
System Management
Securing posts and internal discussions
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
Quality criteria
Quality criteria make it possible to record the quality criteria throughout the life cycle of the production/sample, the requirements of the items as well as the properties of the premises
- Meaning and meaning of quality parameters
- Qualitative properties of instruments, tools and machines
- Quality criteria for the premises
- Using parameters
- Practical use
- Specific use of attributes
- Validity tracking
- Custom criteria option
- You ask
Meaning and meaning of quality parameters
Quality parameters are crucial for the selection of suitable equipment for the production or storage space so that the premises meet the conditions required by the object:
Examples of quality criteria are given in other sections.
Qualitative properties of instruments, tools and machines
- Measurement accuracy
- Production accuracy
- Working speed – e.g. measuring speed productivity per minute, etc.
Quality criteria for the premises
Quality criteria for the premises are both the properties of the premises themselves as well as the requirements of the products and specific objects
- Requirement that the product be kept cool – e.g. 0 – 5°C (typically food, but also e.g. medical test samples)
- Requirement for indoor placement (building materials that must not be wet)
- Maximum humidity requirement (electronics)
Using parameters
Parameters system allows you to record
- For all areas (warehouses, rooms, cabinets, etc.) it allows to define what conditions are secured in them.
- For products (products, samples, parts, components) the conditions that must be ensured during their storage are defined
- For specific subjects (e.g. a specific sample) it is also possible to define the conditions. Here the description makes sense when it comes to a unique object for which the description is not a form of product, or would not make sense.
Practical use
In addition to the documentation, the parameters are used to locate a suitable repository for the new product and to check that the productions are kept in accordance with the rules.
Examples of use:
- Shipment planning makes it possible to check the summary terms of all products shipped together. The expedition can, for example, find out the need to provide air-conditioned transport, because there is a product in the shipment that requires specific conditions.
- Inclusion of new products in the warehouse allows checking that products will not be stored in violation of their conditions
I don't know.
Specific use of attributes
- Attributes also allow recording of product quality class. For example, for a specific product, it is possible to store a flag that it is designed for operation at high temperatures. Within the product, it is then possible to check whether all its components meet this criterion.
Validity tracking
For each criterion for both product and space it is possible to record the date until which the value is valid. By the date of validity, the measurement or check should take place whether the qualitative conditions are still met. For all devices, devices and premises, it is possible to view what conditions are set for them together with the date of the required inspection.
Custom criteria option
The system defines basic groups of criteria, but at the same time allows you to define your own criteria. Using the user code list, the administrator can add the names of other monitored criteria.
You ask
How to store information that a particular device has been measured and meets the quality criteria.
If the inspection is outsourced or by an internal testing service, the information is supported by a measurement report – most often it is a file (PDF) that should be stored among the files of the device (asset) to which it relates.
There is not necessarily a document – there can be an internal protocol and a record of the inspection. In particular, a methodological task is created for the asset, which contains a checklist of the inspections carried out. The control officer is given a task to confirm the inspections carried out. Details of the documentation of the inspection carried out are described by a model methodological task (see ISO 9001, field of metrology).