AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
CalDav, WebDav using Sabre
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
- Configure gateways for external messages
- Message with the outside world
- Email 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
Groups of contacts
Contact Groups are used to break them down according to different criteria. Within CRM, they are used to profile customer groups and set terms of service
Customer Groups
Customer breakdown allows you to fully manage the quality and prices of services as well as customer care responsibilities.
Customer Price List
You can define your own price lists for each customer group. Customers can thus have prices set individually or according to different business criteria.
In customer group detail, you can select price lists that are applied to orders from all customers in the group.
If a customer is in multiple groups and each sets its own price lists, they are used within the order according to their priorities.
SLA Terms for Customer Groups
You can assign SLA Contract to each customer group. The SLA Contract is automatically assigned to each new reported problem. The SLA for a problem can be changed – typically when its severity is reduced. For a customer group, therefore, the default level of SLA conditions is always defined and applies until the severity of the problem is evaluated.
Customer Care Responsibility Management
For each process area, it is possible for a customer group to determine separately who is responsible for it and to which processing area it belongs.
If the data is filled in, then each message that comes from a customer in a particular group is assigned according to the set worker for processing. Together with the worker, the user group can be filled in. This can further limit who has access to the communication.
Helpdesk area
The helpdesk setting is an example of one process group setting
The area where helpdesk tickets are processed allows problems from individual customer groups to be processed separately. If the area is not filled in, the ticket is based in the area defined by the module setting – see the administration of the tsk module.
Good to know
Customer group is not a address book
The system allows you to split contacts into multiple directories. Directories also define access rights, so they allow you to limit who sees which contacts.
By contrast, customer groups organizationally are part of a single recipient, but can contain contacts from multiple directories. An employee who has the right to access a customer group, but does not have access to contacts from another address book, does not gain this access by including them in the group.
How to protect communication with a customer
Communication with a customer is generally visible to workers who have the right to see information about the customer. However, there are options to protect communication:
- By splitting customers into directories and setting up address book access, you ensure that everyone can only see the stored contacts they have. If someone does not have access rights to a address book, they will not know about the contact at all. But be careful that workers responsible for specific processes have the access they need
- By including a specific communication in an area, you ensure that messages are only seen by staff with access to that area. This distinction is important, for example, for projects. If you have a stored contact for a staff member who sends you messages related to a project, by including messages in a project, you ensure that only those with access to the project can see them.
- By marking a message as private, you ensure that only the recipient can see it. But others can see that such a message has arrived.
Public Groups
You can publish a group. If you give the group a public name and description, the addressees can unsubscribe themselves from the group and thus withdraw their consent. You will fulfill the GDPR obligation and you will also have proof of when and how people expressed their contact. More about published groups and GDPR consent to messages here.
To Contact List
In the list of contacts included in the group, you can show when and how a contact got into the group – whether they logged in themselves via the site, or by whom they were included. The columns with information about inclusion in the group are colour coded for better clarity.