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
GDPR and record of qualifications
GDPR is definitely relevant from the point of view of record of competencies and qualifications. Here we discuss the legal grounds for record-keeping
- Qualification of an internal worker from the point of view of GDPR
- Qualification of a former worker
- Candidate for a job and the processing of his/her data
- External Associate and GDPR
- Supply company
- Remember – distinguishing legal reasons is important
Every legal ground has its justification:
Qualification of an internal worker from the point of view of GDPR
For an internal worker, the legal grounds are:
-
Legal ground can be applied to qualifications that you have to check and secure by law. Typically these are qualifications of so-called tied trades / professions -
-
Welder,
-
Electrician,
-
Authorized engineer for a certain type of construction
-
Pharmacist
-
Forensic expert
-
Trained worker for OSH in a factory environment
If you provide services that are legally tied to a qualification, you must be able to prove that the worker has that qualification. -
Legitimate interest can be applied to qualifications that you need in your activities and for the provision of services you need to know who has that qualification and can be entrusted with the job. Typically these are qualifications
-
Graduates of courses for certain technologies (e.g. installation of solar systems, device diagnostics, etc.)
-
Language skills for projects that require them
-
Consent of the worker Consent is relevant for skills that are not needed by the company, but it may be useful to know that a worker has the skill. An example can be any of the skills listed above if the company does not need it
Qualification of a former worker
Even for a former worker, information on qualifications for which there were legal reasons must be kept. At least for as long as the activities that were bound to the qualification can be checked. In practice this means forever for many activities, because e.g. qualifications in the construction sector are checked even after decades when there is a problem (see e.g. collapse of a 30-year-old bridge)
Other groups of qualifications can only be kept on the basis of the worker's consent. It is important that this consent is given to you when you leave – the consent given for the time you are an employee must not be used, because with a significant change in the situation (termination of employment) such consent loses its validity. It is also important to remember that no consent can be given permanently, so at the latest after 5 years the data must be deleted or the consent (in writing) renewed.
Candidate for a job and the processing of his/her data
In the case of a candidate, all data are kept on the basis of the consent. This may be a mandatory part of the information provided by the candidate.
Remember that consent for the purpose of the selection procedure is not consent for long-term storage. These consents may not even be merged. You can stipulate that the candidate by providing data automatically consents to the processing of the data during the selection procedure, but you can only request consent to long-term storage of this data after the selection procedure has been completed and for a limited period. For example, the rejected candidate may agree to the retention of the qualifications for 3 years in order to be approached with a suitable job position.
External Associate and GDPR
Legal Reason If an external associate performs activities legally related to the qualifications with you, you are obliged to check the qualifications with him and to keep the data as if it were an internal employee.
As this is a legal reason, the associate has no right to request that you delete (forget) the data after the cooperation has ended.
All other types of qualifications are only covered by the possibility of consent. For example, you can register their language skills with external cooperating drivers based on consent, but this is not your legitimate interest.
Supply company
The provisions of the GDPR do not apply to the supply contract. In addition, the supply company is typically also itself liable for the services being supplied by qualified workers with compulsory education. As part of the contractual relationship, you can request the possibility of checking whether the work is supplied by a qualified worker, but the right to keep this data would have to be given to you directly by the worker, not by the company. A company is not entitled to give consent to any processing of data about its workers to other persons. It is understandable if a worker gives consent to his company to provide e.g. a CV to other companies, if this is important for obtaining contracts or work for the worker. (This applies not only to staffing agencies, but also to many other companies). However, this consent is not consent for the same data to be further processed by a third party.
Remember – distinguishing legal reasons is important
Since you have to delete some data, e.g. when a worker leaves, and others do not, it is important to monitor the legal reason for individual qualifications. It is also important to note that the same qualifications can be given to different workers for different legal reasons.
Example: A worker e.g. with a qualification for supervising building works:
- If you have accepted him to do this work for you, it is in your legitimate interest to manage the qualification documents. Upon the departure of a worker, the legitimate interest ceases.
- By the time you first use a worker as part of a building project, registration is already a legal obligation, as you may be required to prove his qualification
- If you are not a construction / engineering firm, but e.g. a staffing agency, you only keep the qualification on the basis of the worker's consent. This consent automatically ceases when the worker leaves, unless you conclude the consent on the departure.