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
Objects affected by the problem
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
Objects related to the task pattern
Contacts and directories module (CRM)
Address book or people and companies
Web management and automation
Receiving a message from the web
Human resources
Asset management module
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
How the system works and how it protects data
Private notes and tags for objects
Filtering in the list of records
System services
Additional functions with files
Copying and moving files between objects
Phrases and terms
Terms allow you to define a corporate vocabulary and thus stabilize nomenclature.
In particular, it is important to clearly define the terminology used in regulations and standards, so the ability to define terms is part of the methodology. You define terms once and they are valid for all guidelines and standards.
Hierarchical breakdown of terms
Terms can be defined hierarchically in the same way as in dictionaries. You can define the main term Strategy and under it define the refining terms Business Strategy and Financial Strategy.
Terms in multiple languagesh
For each term, you can define its explanation in multiple languages. Use the button to do this. This allows the terms to be understood accurately even by people who do not know your commonly used language well enough. Each user will then see the terms in the original language and translated into their own language.
Warning: We recommend writing the entire methodology in one language. Do not alternate the basic language, otherwise users will have languages in a messy way.