AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
CalDav, WebDav using Sabre
Business excelenece
Balance Scroecards
Task & Project Control
- 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
- Customer Service Response Generation
- 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
- Assigning a new task
- 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)
- My Tasks
- 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
- Crypto 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
FMEA – Probability of Detection
Probability of detecting a failure if it has occurred.
The definition varies for different types of FMEA analysis. Therefore, it is necessary to specify the type of analytical process (for individual failures or for properties).

The following overview is based on the automotive industry standard. Before using, check whether it is relevant for your case!
DFMEA
- Level 1: It is known that the design cannot fail
- Level 2: Verified standard procedures, aging control
- Level 3: Verified standard procedures, failure test
- Level 4: Verified standard procedures, function pass test
- Level 5: Verified standard procedures in the late development phase, aging control
- Level 6: Verified standard procedures in the late development phase, failure test
- Level 7: Verified standard procedures in the late development phase, low, function pass test
- Level 8: New test procedures are used, which are not verified
- Level 9: Known tests are not specifically designed to verify potential failures
- Level 10: Test procedures have not yet been developed
PFMEA
- Level 1: Failure is virtually impossible or cannot go undetected
- Level 2: Proven reliable detection methods; machine inspections prevent the occurrence of defective products
- Level 3: Proven detection methods; defective products are automatically detected
- Level 4: Proven detection methods; reliable inspections detect the problem during production and reject defective products
- Level 5: Verified inspections; semi-automatic detection alerts the operator
- Level 6: Verified inspections; manual inspection of products or samples detects defects
- Level 7: Unverified inspections; semi-automatic detection alerts the operator
- Level 8: Unverified inspections depend on manual inspection of products or samples to detect defects
- Level 9: It is unlikely that inspections will detect the problem; sample checks may not easily identify the issue
- Level 10: It is unlikely or impossible to detect the issue through inspections
FMEA-MSR
- Level 1: Always detected – significantly more than 99.9%; the system responds to failures
- Level 2: Detected with probability > 99.9%, the system is very likely to identify the failure
- Level 3: Automatic detection identifies failures with probability > 99% with a short response time, automatic reaction is highly probable
- Level 4: Detection with probability > 97% with medium response variability; the system will usually react to failures
- Level 5: Detection with probability 90–97%, with moderate response variability; the system will usually respond automatically to failures
- Level 6: The failure is detected by the user or system with probability > 90% and will likely be able to respond
- Level 7: Low probability that the user will recognize and respond; diagnostics reveal the problem with >60% accuracy.
- Level 8: Rarely possible to detect the problem, diagnostics detect failure with < 60% accuracy; user may not always respond
- Level 9: Failure will almost never be detected; system or user response cannot be relied upon
- Level 10: Cannot be detected; no response during operation