AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
Business excelenece
Balance Scroecards
Task & Project Control
- Helpdesk ticket - reply to customer
- Test
- Qualification of user or contact
- Project role
- What makes up the methodology / QMS
- dragdrop
- Location
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Processing time sheets
- Records managed by a project
- 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
- Type of tests
- Deal management
- FMEA - Detection
- FMEA - Features
- FMEA Methodology | AyMINE
- FMEA - Occurence analysis
- FMEA Severity analysis
- FMEA
- Management of responsibilities - RACI Matrix
- RACI Matrix for Project
- Improvements and Preventive Measures
- Notice – example of use
- tskproblem_terminology
- 8D report
- Task Scheduling
- Administration of the Task Management Module
- Adminitration of areas, projects, calendars
- Discussion
- GDPR and record of qualifications
- 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
- Decision
- Configuration Package
- Record template
- Change management process in a project
- Task list
- Requirements
- Team Member
- Right to Manage Qualifications
- Input requirements
- Obligation
- Competencies and Skills
- Problems, tickets and their management
- Meeting
- Package definition
- Phrases and terms
- 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
- QMS and Task Management
- 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
- tskdefusertask
- Quality Management System (QMS)
- tsktask_batasks
- Project Team
- Events and meetings
- Events and meetings
- List of event instances
- moduleclientoptions
- Processed objects
- Mark patterns
- Notification events
Interprocess management
Human Resources
- hrstcontract
- roles
- Human resources
- Digital Personnel Archive
- Personalistics – User Permissions and roles
- Registration of job seekers
- Manage department / division data
- Job Position
- Worker
- Worker overview
- An overview of your staff
- Responsible HR Manager
- Synchronizing staff and system users
- modulesafety
Asset Management
- Products, assets and sales
- Tendering and purchasing
- Analytical model
- Product Supplier
- Product Categories
- Product or Product Property
- Project Goal
- Business Offer
- Offers summaries
- Recalculate bid
- 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
- Quality criteria
- Why are the Quality criteria usefull
- DFMEA - Product FMEA
- Hara | Hazarad & Risk Analysis
Customer Relationship - CRM
- Contacts and directories module (
- System Permissions and CRM Module Settings
- Customer Order Overview
- Address books
- Address book list and management
- Privacy policy
- Send bulk messages in compliance with GDPR
- Bulk email footer
- Unsubscribe and set preferences
for bulk mail - How to correctly forget a person's details
- Bulk Emails
- Contracts
- Partner in a contract
- Message patterns
- Groups of contacts
- Order overview for customer groups
- Directory or people and companies
- Contact per person or company
- Quickly available contacts
Finance management
System modules
System management
- moduleclientoptions
- digiSign
- formattedtexts
- System Configuration
- Processes in use
- Client
- Public Client
- Configure gateways for external messages
- E-mails and external communication
- Email messages
- Rules for external messages
- Secure business communication
- Send 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
- sysrole
- User Processes
- System module
- System User
- User administration
- User Administration
- Secure login to the sytem
- Connecting users to VOIP PBX
- Secure Key Wallet
Framework
- frmobjectextension
- introhelp
- introhelp_mobile
- introhelp_aplikace
- versioninfo
- releases
- AyMINE modules and basic types
- cliplink
- introhelp_settings
- introhelp_deleting
- introhelp_dragdrop
- list_filtering
- AyMINE intro
- AyMINE access security
- AyMINE Modules
- Object locks
- System rights
- introhelp_keyshortcuts
- introhelp_shortcuts
- introhelp_icons
- list
- introhelp_generalinfo
- introhelp_objectdetail
- introhelp_objectlist
- introhelp_privateobjectnotes
- AyMINE User Rights Control
- introhelp_dashboard
Assignment of a New Task According to the Methodology
Assigning a task in accordance with established methodologies means clearly defining who is responsible for what, when the work must be completed, and how. By automating tasks, you can save a significant amount of work and, most importantly, greatly support efficient performance and collaboration.
Task assignment is a natural activity for every team. However, it is also the first and one of the most important moments that determine whether the team follows established work procedures or not.
Why QMS and Task Management Belong Together
There is a fundamental difference between assigning a task with a vague instruction like “just get it done” and assigning a task that includes all necessary components:
- Responsibilities in accordance with the RACI matrix
- Deadlines
- Work procedure
- Control procedure (control list, checklist)
- A clear reference to what should be worked with (documents, products, clients, etc.)
Manual task assignment with everything it should include only makes sense if each task is unique. However, once tasks start repeating — and the vast majority do — it becomes necessary to automate their assignment as well. Quality Management Systems (QMS) should include in their work procedures everything that forms part of a proper task assignment, so integrating QMS with task management is both natural and meaningful.
How QMS and Tasks Work in Practice
When a manager or generally a task assigner creates a new task:
- The system offers documented procedures. The assigner selects those that relate to the area where the task is being created.
- The assigner chooses the documented procedure to be performed.
- Based on the selected procedure, the system creates a new task from the work procedure (task template).
- If roles are defined in the system (whether project-based or organizational), the system automatically assigns the appropriate employees to the task according to the RACI responsibility matrix — e.g., executors, approvers, etc.
- The task detail opens for review and any necessary additions.
If processing requires multiple tasks, the manager can launch a process that schedules all required tasks and manages their execution step by step.
Using tasks derived from the QMS differs slightly depending on whether they relate to a project or not. The difference lies in the fact that a project has defined project roles to which employees are appointed.
Assigning a Task to a Project Team Member
In projects, tasks usually do not arise automatically but are created by the project manager as part of planning and work allocation. Ideally, they should be created based on a project template plan. Individual steps in the project template plan simultaneously represent work procedures of the project methodology.
In project tasks, each task has defined project responsibilities — a RACI matrix of project roles. When creating a task, employees are assigned to it according to their roles. (If multiple people hold a particular role, the team leader receives the task and may delegate it.)
If there is no employee in the project with the required role, the project manager takes responsibility for the task. Once the role is filled by the appropriate employee, the task can be transferred to them. However, we recommend always assigning all mandatory project roles before planning according to the project template plan.
Note: In project teams, the setting of a responsible role is not used.
Assigning a Task Within Company Agenda
A task may be created automatically based on an event, or it may be assigned manually by an employee.
When it is created automatically, it must have a designated person responsible for handling it. Therefore, a responsible role is defined for the task.
How Task Assignment Works
- If only one employee is assigned to the role, the task is assigned to them.
- If multiple people are assigned to the role:
- If the role has a designated leader, the leader receives the task.
- If no leader is defined for the role, the first person in the group receives the task.
Tasks are always categorized within a specific area. Employees who receive responsibility for tasks are selected only from those who actively work in that area. The same task activated in a different area may therefore be assigned to a different employee.
⚠️ If no role is defined, or if no one is assigned to it, the system cannot initiate the task. In the case of a manually created task, the employee who creates it becomes directly responsible for it.