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
Meeting
Digitising meeting management is a key way to work effectively with information across the business
Preparing for a meeting
Preparing for a meeting consists of creating a new Meeting record (object) within which everything that is needed for the meeting is prepared:
- list of participants
- setting the date and time of the meeting
- information to be discussed (e.g. minutes from the last meeting)
- tasks to be evaluated
- decisions to be made
Once prepared, the system sends invitations to all participants.
Generating preparation
Tip: Meetings usually have the same participants and cover the same areas. Typically, tasks are discussed in the meetings until they are completed. You can easily create a new meeting by generating a new one from a the previous one – use the command Repeatable for several new meetings or New meeting for a single new meeting.Automatic generation of a recurring meeting includes:
- copying the list of participants
- adding pending items from the previous meeting to the agenda
- if the previous meeting includes a date for the next meeting, scheduling it for that date and scheduling it for the next meeting the same time later; if not, the repeat dates must be entered
Meeting invitation
The meeting agenda is available to all invited persons. They have even possibility to add new themes (linke their task that requires collaboration). The cooperation at the meeting agenda definition simplifies work for the meeting manager.
If it is necessary to send the agenda to participants who do not have access to AyMINE, a PDF copy of the agenda could be generated directly from AyMINE and distributed.
Excuse from the meeting
A participant can send an apology from the meeting in advance by creating an apology text for his/her participation in the meeting.
Meeting invitation and submission of documents
Meeting participants will receive an invitation from which they can open the meeting table. On the table they will see everything that will be discussed at the meeting, so they have the opportunity to prepare in advance.
If the agenda needs to be sent to external participants who do not have access to AyMINE, it is possible to generate it as minutes of the meeting even before the meeting starts and send out the generated PDF.
Apology from the meeting
A participant can send an apology from the meeting in advance by creating an apology with the text of the apology for his/her participation in the meeting.
Implementation of the meeting
Participation in the meeting
For each participant, it is possible to confirm his/her participation in the meeting or apology.
It is possible to cancel a meeting with a reason, both before and after the meeting has started. A typical reason for cancellation may be insufficient number of members to make a decision.
Discussion of items
The conduct of the meeting is supported by the meeting table. On this table are all the items of the meeting and support for working with them
- A record of the meeting can be added to the information and tasks. At the same time, information that they have been discussed is saved
- Tasks can be declared closed at the meeting (can be done by the person in charge or by the meeting organizer if the person in charge is among the participants)
- Decision-making can be conducted in accordance with its internal process. A record of its preparation can be kept within the meeting
A PDF record is then generated of all the steps and records of the deliberation. The meeting leader can send out information about the minutes. The minutes become a document stored in the meeting.
Icons on the desktop
Icons for objects on the workbench help orientation. By default, the icons for objects are for that object, but they change during meetings.
Meeting objects
During processing, objects – program points – in a deliberation are put into different states expressed by an icon:
– Assigned to the meeting for resolution
– Solved and closed. The object (a meeting agenda topic) is closed by the meeting and will not be addressed by the next meeting
– Moved to the next meeting. Item will be addressed again at the next meeting.
– New – newly created in the meeting
Meeting participant
Some meetings may require that all persons who participated in full or in part in the meeting be recorded (e.g. for meetings where classified information is discussed). Therefore, AyMINE allows multiple participant roles to be defined:
– regular participant
– Speaker A participant invited to present a position; the participant is not a full participant, typically does not attend the whole meeting, does not vote, and in principle the content of the meeting is not a working topic for the participant. This may be a proponent of a solution that the consultation is concerned with who is not a voting member.
– Secretary, secretary or someone else where he/she takes care of ensuring the processes related to the meeting
– An attendee is invited to the meeting for any reason but is not a full participant. (E.g. interpreter)
– Press A guest who keeps the wider community informed of the events and outcomes of the meeting
The status of a regular participant in a meeting is represented by icons:
– Present throughout the meeting.
– Present only part of the time
– Not attending the meeting
– Attendance not recorded
Status of the meeting itself
– The meeting is in preparation and has not yet been officially announced. Participants have not received invitations
– invitations have been sent out
– the meeting is ongoing
– the meeting has taken place
– meeting has been cancelled (not held and not scheduled)
Meeting minutes’ approval
If the approval of the meeting minutes is to be formally recorded, we recommend that a vote on the minutes be included as the last item of the meeting. The minutes are immediately visible in detail and everyone can view and comment on them.
If the minutes need to be finalized manually and then approved, it is also possible to open the meeting afterwards and change the edited minutes. Formal documented approval of the minutes is possible in several ways:
- Vote on the minutes at the next meeting.
- Create a vote on the minutes outside the meeting and invite participants to comment (It is preferable to create this vote during the meeting and leave it unresolved. This will make it immediately retrievable from the meeting.)