AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
Business excelenece
Balance Scroecards
Task & Project Control
- Send customer answer in regards to the complaint
- Bundle of Documentation and records
- Test and Inspection Management
- Qualification of user or contact
- Project role
- Methodological framework
- Physical and virtual location management
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Processing time sheets
- Project management items
- Activation buttons
- Why some data can't be deleted
- Starting events
- Qualification of user or contact
- task_taskobjects
- Project
- Reminders and Messages
- eventobj_raisingevents
- decision_decobjects
- eventobj_startingevents
- eventobj_eventbuttons
- Hierarchy of testi types
- Deal management
- FMEA criteria for detection evaluation
- FMEA system functionality analysis
- Methodology how to conduct FMEA
- FMEA analysis of the failure occurence
- Analysis of the FMEA Severity
- Support for FMEA Analysis
- Management of responsibilities - RACI Matrix
- RACI matrix for project
- Improvements and Preventive Measures
- Plan
- Notice – example of use
- tskproblem_terminology
- 8D report - quality problem resolution
- Task Scheduling to the right time and scope
- Administration of the Task Management Module
- Adminitration of areas, projects, calendars
- Discussion
- System rights for the task management module
- Project Planning
- Employee Tasks
- Incident and Quality Issue Management
- Collaborative Resolution of Multiple Problems
- List of business areas
- Required qualifications
- Plan template / strategy
- Management and documentation of the decision
- Configuration Package
- Record template
- Change management process in a project
- Task list
- Requirements
- Team Member
- Right to Manage Qualifications
- Obligation
- Competencies and Skills
- Problems, tickets and their management
- Meeting
- Package definition
- Terminology and Nomenclature
- Data Area
- Risk
- Task
- Business event
- Task, project & quality management
- Records and protocols
- Directives and Policies
- Events
- Risk Pattern
- Information
- Project definition
- Activity log
- eventinstances
- Personal calendar
- Objects of decision making
- Event activation buttons
- Objects affected by the problem
- Variant decision-making
- Recorded activities
- Self-Reminders
- Assignment of a New Task According to Methodology
- Objects related to the task pattern
- Effect of the task on the right to modify the atta
- Level of Competence
- Manager approval with the task report
- Region / project / methodology
- Manage your marks
- Task patterns saves work and improve quality
- Management system
- Task planning both in project and daily business
- Project Team
- Events and meetings
- Events and meetings
- List of event instances
- moduleclientoptions
- Processed objects
- Mark patterns
Interprocess management
Human Resources
- roles
- Staffer / Worker Management
- Human resources
- Employee access to the contract files
- Personalistics - User Permissions and roles
- Candidates Management
- Manage department / division data
- Job Position
- Employee dashboard with personal data
- An overview of your staff
- Responsible HR Manager
- Synchronizing staff and system users
- Management of the staffer contracts
- Safety of the HR module
Asset Management
- Products, assets and sales
- Tendering and purchasing
- Analytical model
- Product Supplier
- Product Categories
- Product or Product Property
- Manage projects by goals
- Create offer for premium or B2B clients
- Offers summaries
- Create and recalculate offer using price lists
- Offer and Price Access Rights
- Creating and processing orders
- System order status query
- Order Reports
- Pricing
- Pricing – volume discounts
- Products and Goods
- Product status and change
- Product Units
- Definition and Control Quality Criteria
- Why Quality Criteria is a requisite part of QMS
- DFEMA - FMEA of the product design
- HARA for product
Customer Relationship - CRM
- Contacts and directories module (
- System Permissions and CRM Module Settings
- Customer Order Overview
- Address book management and protection
- Address book list and management
- Privacy policy
- Send bulk messages in accordance with GDPR
- Link in bulk message to set preferences or unsubscribe
- GDPR: Support to set preferences over the web
- GDPR: Support for subject forgetting
- Sending Bulk Emails - manual
- Contracts
- Partner in a contract
- Generate messages from system with patterns and AI
- Group of contacts from address books for better management
- Evidence of contacts and related business data
Finance management
System modules
System management
- moduleclientoptions
- Electronic sign even on mobile device
- formattedtexts
- System Configuration
- Processes in use
- Client
- Member Management for churches, non-profit organisations
- Configure gateways for external messages
- Corporate email and communication processing
- Email messages
- Rules for external messages
- Secure business communication
- Sending SMS directly from CRM
- Call directly from CRM
- Documents and files
- Additional functions with files
- Copying and moving files between objects
- Picture presentation
- Public link to the document
- Recent Files
- Dashboard
- Object location on the board
- Client items
- Revisions and comments
- Securing posts and internal discussions
- Translations
- Record Relationships
- Relation types
- System Groups and Teams for rights settings
- User Processes
- System module
- System User
- User administration
- User Administration
- Connecting users to VOIP PBX
- Trusted User Device
- Secure Key Wallet - Safe storage for digital keys
- Data vault for Company secret & Classified data storage
Framework
- AyMINE frm module - corestone of the ecosystem
- Description of the view of the record details
- Private Notes to Records that no one can read
- AyMINE Access control and security
- Introduction to the application
- Using Drag & Drop even on mobile devices
- AyMINE icons are language for fast orientation
- Delete object to the trash
- Principal dashboard
- Settings your own configuration
- AyMINE Gestures and Keyboard Shortcuts
- AyMINE User Rights Control
- Install AyMINE to windows
- About AyMINE
- Work with list of records
- AyMINE on mobile device
- List of records
- How filtering in lists works
- cliplink
- System rights
- Module is the principal brick of the aymine ecosystem
What Makes Up the Methodological framework
A quality management system consists of a number of record types. Each of them is described separately below.
- What Makes Up the Methodological framework
- Types of Records
- Obligation (Obligation)
- Term from the Glossary (Term, Phrase)
- Policy / Regulation (Policy, Regulation)
- Default Plan Template (Default Plan Template)
- Working Procedure Template (Working Procedure, Task Pattern)
- Process
- Record Template (Record Template)
- Competency & Qualification (Competency & Qualification)
- Business Events (Business Event)
- Project Role
- Project Template
- More Information
Types of Records
The diagram above shows the typical layers that make up a Methodological framework. For each layer, the records belonging to that layer are listed. The right-hand column shows the primary records that are created when the the framework is applied in practice.
A Methodological framework forms a system of the management or a part of it. In general management system standardizes a specific area of activities. It therefore contains all records required to define what it means to perform an activity in a quality-compliant manner.
Each component of the framework has its own documentation page—follow the links for detailed information.
For clarity, the English name of each QMS element is shown in parentheses after its Czech name.
Obligation (Obligation)
An Obligation that internal management system must fulfil or comply with. Obligations typically represent “input requirements.” They stand somewhat outside the methodology itself, but that does not make them less important—quite the opposite.
Term from the Glossary (Term, Phrase)
A Glossary is an essential part of every norm and standard and should also be included in internal management system. Ideally, a single shared glossary is used across all part of the system within the organization.
Glossaries support multilingual definitions of terms. Within one glossary, you can therefore provide both the Czech translation and the original definition (and, in general, any number of languages).
Multilingual definition is not limited to glossaries; it is particularly valuable for working procedures as well. Within a single part of the system, you can define a quality and safety management system simultaneously in Czech and English, making it understandable to local staff, international colleagues, and customer auditors alike.
Policy / Regulation (Policy, Regulation)
Policies form the backbone of the entire quality management system and other part of the system.
Policies at different management levels may have different names—directives, policies, regulations, etc. Specific document types can be defined directly in the system.
Default Plan Template (Default Plan Template)
Default plans are the foundation of standardized planning, especially in project management, but they are useful wherever planning is required and defined by a methodology.
Examples of default plans include:
- Project default plan
- Master Test Plan – Test Strategy
Working Procedure Template (Working Procedure, Task Pattern)
A working procedure corresponds to operating procedures used in traditional quality management systems.
The key advantage of an automated processes over document-based systems is that real tasks are created directly from working procedure templates. The system therefore saves significant effort and eliminates the need for employees to know every detail or search for the correct procedure.
Working procedures are part of defined processes. On the other hand, they create WBS (Work Breakdown Structure). A typical example of a complex step is a project phase.
Process
A process describes a sequence of operations. It consists of both human-performed steps and automated steps.
Processes are essential for activity automation. However, there are many cases where a well-defined working procedure is sufficient on its own, without being part of a process. Examples include:
- Procedure for unblocking a safety device
- Emergency opening of a server room during a power outage
- Testing connectivity to an information system
- Checking the validity of fire extinguisher certificates
Management system do not require working procedures to be part of processes and often it makes no sense to create complete process for each operation. AyMINE supports both approaches. It is therefore worth considering whether introducing a process would actually complicate usage. For standalone working procedures, it is important that their scope and context are clearly defined—this ensures they can be easily found and used.
Record Template (Record Template)
A record template is used for records that must be created during work and where fully automated records are not sufficient.
Record templates are typically used when documentation must be submitted to an approval authority. They are not used where the purpose is only internal documentation of an activity and its outcome.
Competency & Qualification (Competency & Qualification)
Competencies and qualifications define the capabilities required of employees who perform specific tasks. They do not replace organizational roles, but they are essential for a completeness of the management system.
Although competencies are part of management system, they also serve as a basis for recording employee skills and are therefore used by the HR module as well.
Business Events (Business Event)
Business events support activity automation. Events allow one process execution to trigger another, enabling the automation of complex chains of activities.
Project Role
A project role defines the competencies required of a person participating in a project. Project roles are also assigned default tasks via working procedure templates.
Project roles are meaningful only within project-related methodologies. Outside of project management, they are not used.
Project Template
A project template defines all components that a project of a given type must include. A separate template can be defined for each project type.
Based on a project template, a new project can be initiated in full compliance with the methodology in just a few minutes.
More Information
You can read more about methodological frameworks and their importance for quality management here.
