AyMINE – Technical documentation
User Modules
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Region / project / methodology
Change management process in a project
Qualification of user or contact
Right to Manage Qualifications
Methodology and Quality Management systems
What a methodology / QMS consists of
Customer Service Response Generation
Objects affected by the problem
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)
Web management and automation
Receiving a message from the web
Human resources
Human Resources module security
Manage department / division data
Synchronizing staff and system users
Products, assets and sales
Received order for goods or services
Technical Modules
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
System Modules
The AyMINE Framework Module
Configure how your system looks and works
Gestures and keyboard shortcuts
More about how the system works
Private notes and tags for objects
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
FMEA – Severity evaluation
Severity evaluation in the FMEA process is defined by the FMEA process itself.
Description here is bases on the general standard.
Describe as precisely as possible the possible effect of the disorder. FMEA authors should carefully consider all effects directly attributable to the failure. However, they should avoid assigning a severity rating based on the basis of secondary effects of the disturbance, unless the disturbance causes immediate injury to the user or impedes the safe operation of the vehicle. Always consider primary operation and most severe failures.
In case of several potential failure of the feature, all potentials should be described, but the evaluation is bases on the most severe effect.
The measure described below is based on the automotive industry standard. Check if that is relevant for your case before use!
Effect: Failure to Meet Safety and/or Regulatory Requirements
Rank 10: Potential failure mode affects safe vehicle operation and/or involves noncompliance with government regulation without warning.
Rank 9: Potential failure mode affects safe vehicle operation and/or involves noncompliance with government regulation with warning.
Effect: Loss or Degradation of Primary Function
Rank 8: Loss of primary function (vehicle inoperable, does not affect safe vehicle operation).
Rank 7: Degradation of primary function (vehicle operable, but at reduced level of performance).
Effect: Loss or Degradation of Secondary Function
Rank 6: Loss of secondary function (vehicle operable, but comfort /convenience functions inoperable).
Rank 5: Degradation of secondary function (vehicle operable, but comfort /convenience functions at reduced level of performance).
Effect: Annoyance
Rank 4: Appearance or Audible Noise, vehicle operable, item does not conform and noticed by most customers more than 75%
Rank 3: Appearance or Audible Noise, vehicle operable, item does not conform and noticed by many customers (about 50%)
Rank 2: Appearance or Audible Noise, vehicle operable, item does not conform and noticed by discriminating customers (up to 25%)
No Effect
Rank 1: No discernible effect