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
Improvements and Preventive Measures
Methodology and Quality Management systems
What a methodology / QMS consists of
Problems, tickets and their management
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
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
Improvements and Preventive Measures
Improvements and Preventive Measures are an essential tool for quality improvement. In AyMINE, their management is part of the quality management module
- Differences between improvement and preventive action
- Documentation of improvements and preventive action
- Improvements are not within the project
- Improvement Process
Differences between improvement and preventive action
The purpose of improvement is to improve the way the action is carried out. The logical consequence of improvement is either
- Improved product quality (includes improved quality consistency, i.e. less variation), or
- Lower process cost, or
- Higher speed
The purpose of preventive action is to prevent problem from occurring, whether it be a product problem or an incident within the production process or a mismatch in quality compliance.
Documentation of improvements and preventive action
Both are monitoring within the areas in AyMINE. In order to benefit from improvement or preventive action, you must have an active standards area and an active process quality management area.
Improvements are not within the project
Preventive measures or improvements are not part of the project management. In the project, Preventive Measures are part of risk management, namely the risk minimisation plan. Process improvements are addressed outside the project as part of internal process improvements (quality management). Product Improvements are addressed with solutions within change requirements or directly within product analysis.
Improvement Process
- An improvement proposal can occur at any time and in any process. The standard procedure is that the proposal is sent to the quality manager or the owner of the process to which the improvement relates.
- The quality manager or the owner of the process records the proposal among the improvement proposals. The manager manages generic proposals that are not directed to a specific process or involve multiple processes. The owner of the process manages the improvements to a specific process.
- Improvement proposals can be discussed at a meeting. The specific improvements are thought-out directly in the proposal (under the Solution Proposal tab).
- To implement individual steps, the design manager creates tasks directly from the proposal. As a result, the tasks are linked to the proposal and it is documented whether and how the proposal was processed.
- After the proposal is completed, its status is changed to terminated.