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 – Occurrence
Occurrence is the likelihood that a specific failure cause /mechanism will occur during the design life.
The estimate is based on experience with similar products or previous versions. It is necessary to consider how the new version/new product differs and how these changes affect the probability of failure.
If the data is not available, expert judgment is used.
If the estimate is on the boundary of two levels, the higher level is used. If it cannot be estimated, level 10 is used.
Occurrence Rating
Very High
Rank 10 New technology/new design with no history. ≥ 100 per thousand
High
Rank 9 Failure is inevitable with new design, new application, or change in duty cycle/operating conditions. 50 per thousand
Rank 8 Failure is likely with new design, new application, or change in duty cycle/operating conditions. 20 per thousand
Rank 7 Failure is uncertain with new design, new application, or change in duty cycle/operating conditions. 10 per thousand
Moderate
Rank 6 Frequent failures associated with similar designs or in design simulation and testing. 2 per thousand
Rank 5 Occasional failures associated with similar designs or in design simulation and testing. 0,5 per thousand
Rank 4 Isolated failures associated with similar design or in design simulation and testing. 0,1 per thousand
Low
Rank 3 Only isolated failures associated with almost identical design or in design simulation and testing. 0,01 per thousand
Rank 2 No observed failures associated with almost identical design or in design simulation and testing. ≤ 0,001 per thousand
Very Low
Rank 1 Failure is eliminated through preventive control.