AyMINE – Technical documentation
sys
- Translations
- System Management
- User Administration
- System User
- Documents and files
- System Groups and Teams for rights settings
- Record Relationships
- Client
- Dashboard
- Public link to the document
- Client settings
- Revisions and comments
- User administration
- Copying and moving files between objects
- Object location on the board
- Additional functions with files
- Client items
- Picture presentation
- Secure login to the sytem
- Configure gateways for external messages
- Connecting users to VOIP PBX
- Call directly from CRM
- Send SMS directly from CRM
- Formatted texts in the application
- Secure business communication
- System Configuration
- User Processes
- Processes in use
- Message with the outside world
- Email messages
- Relation types
- Securing posts and internal discussions
- Recent Files
- Crypto Wallet
- Electronic sign even on mobile device
tsk
- Required qualifications
- Package definition
- Phrases and terms
- Data Area
- Test
- Risk
- Task
- Business event
- Task, project & quality management
- Records and protocols
- Directives and Policies
- Events
- Risk Pattern
- Information
- Meeting
- Problems, tickets and their management
- 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
- Project definition
- Activity log
- List of event instances
- Task patterns saves work and improve quality
- Methodology and Quality Management systems
- My Tasks
- Task planning both in project and daily business
- Project Team
- Events and meetings
- Sample tasks and methodologies of the area
- Events and meetings
- List of event instances
- Client Settings
- Processed objects
- Mark patterns
- Manage your marks
- Region / project / methodology
- Personal calendar
- Objects of decision making
- Event activation buttons
- Objects affected by the problem
- Variant decision-making
- Recorded activities
- Self-Reminders
- Assigning a new task
- Objects related to the task pattern
- Effect of the task on the right to modify the attached object
- Level of Competence
- Manager approval with the task report
- Requirements waiting for you
- Notification events
- List of business areas
- Qualification of user or contact
- Activation buttons
- Why some data can't be deleted
- Starting events
- Qualification of user or contact
- My projects
- Objects processed in the task
- Project
- Reminders and Messages
- Notification events
- Objects of decision making
- Starting events
- Sample tasks and methodologies of the area
- Activation buttons
- Records managed by a project
- Timesheet
- Project role
- What makes up the methodology / SMJ
- Drag & Drop between records
- Location
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Type of tests
- The person responsible for the task
- Deals / Contracts
- Customer Service Response Generation
- 8D report - tool for problem resolution
- 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
- Notice – example of use
- 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
- FMEA Analysis
- Management of responsibilities - RACI Matrix
- RACI Matrix for Project
- Improvements and Preventive Measures
crm
- Directory or people and companies
- Address books
- Contact per person or company
- Order overview for customer groups
- Customer Order Overview
- Message patterns
- Quickly available contacts
- Contacts and directories module (
- Address book list and management
- Privacy policy
- Groups of contacts
- System Permissions and CRM Module Settings
- Contracts
- Send bulk messages in compliance with GDPR
- Bulk email footer
- Bulk Emails
- Partner in a contract
- Unsubscribe and set preferences
for bulk mail - How to correctly forget a person's details
am
- Product Categories
- Shared analytical model accelerate your project and development
- Products, assets and sales
- Products and Goods
- Tendering and purchasing
- Product Supplier
- Product status and change
- Project Goal
- Business Offer
- Recalculate bid
- Pricing
- Pricing – volume discounts
- Offers summaries
- Order Reports
- Quality criteria
- Creating and processing orders
- Product or Product Property
- Why are the Quality criteria usefull
- DFEMA - FMEA of the product design
- HARA for product
- Offer and Price Access Rights
- Product Units
- System order status query
frm
- List of records
The AyMINE Framework Module- AyMINE releases
- AyMINE – Initial advice
- AyMINE Modules
- Object locks
- Configure how your system looks and works
- Filtering in the list of records
- Icons in AyMINE
- Deleting
- Your main dashboard
- Object lists
- More about how the system works
- Object detail
- Private notes and tags for objects
- ClipLink
- Gestures and keyboard shortcuts
- Drag & Drop between records
- System rights
- AyMINE (C) 2020
- Gestures and Keyboard Shortcuts
- Password retention policy
- framework user rights
- AyMINE — Windows Application
- AyMINE — Tips for Mobile Usage
- Overview of Modules and Record Types
hr
- Human resources
- Worker
- Human Resources module security
- Personalistics – User Permissions and roles
- Manage department / division data
- Synchronizing staff and system users
- Responsible HR Manager
- HR module role
- Registration of job seekers
- An overview of your staff
- Digital Personnel Archive
- Job Position
- Worker overview
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.