AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
Business excelenece
Balance Scroecards
Task & Project Control
- Send customer answer in regards to the complaint
- Bundle of Documentation and records
- Test and Inspection Management
- Qualification of user or contact
- Project role
- Methodological framework
- Physical and virtual location management
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Processing time sheets
- Project management items
- 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
- Hierarchy of testi types
- Deal management
- 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
- Support for FMEA Analysis
- Management of responsibilities - RACI Matrix
- RACI matrix for project
- Improvements and Preventive Measures
- Plan
- Notice – example of use
- tskproblem_terminology
- 8D report - quality problem resolution
- Task Scheduling to the right time and scope
- Administration of the Task Management Module
- Adminitration of areas, projects, calendars
- Discussion
- 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
- Management and documentation of the decision
- Configuration Package
- Record template
- Change management process in a project
- Task list
- Requirements
- Team Member
- Right to Manage Qualifications
- Obligation
- Competencies and Skills
- Problems, tickets and their management
- Meeting
- Package definition
- Terminology and Nomenclature
- 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
- Assignment of a New Task According to Methodology
- 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
- Task patterns saves work and improve quality
- Management system
- Task planning both in project and daily business
- Project Team
- Events and meetings
- Events and meetings
- List of event instances
- moduleclientoptions
- Processed objects
- Mark patterns
Interprocess management
Human Resources
- roles
- Staffer / Worker Management
- Human resources
- Employee access to the contract files
- Personalistics - User Permissions and roles
- Candidates Management
- Manage department / division data
- Job Position
- Employee dashboard with personal data
- An overview of your staff
- Responsible HR Manager
- Synchronizing staff and system users
- Management of the staffer contracts
- Safety of the HR module
Asset Management
- Products, assets and sales
- Tendering and purchasing
- Analytical model
- Product Supplier
- Product Categories
- Product or Product Property
- Manage projects by goals
- Create offer for premium or B2B clients
- Offers summaries
- Create and recalculate offer using price lists
- 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
- Definition and Control Quality Criteria
- Why Quality Criteria is a requisite part of QMS
- DFEMA - FMEA of the product design
- HARA for product
Customer Relationship - CRM
- Contacts and directories module (
- System Permissions and CRM Module Settings
- Customer Order Overview
- Address book management and protection
- Address book list and management
- Privacy policy
- Send bulk messages in accordance with GDPR
- Link in bulk message to set preferences or unsubscribe
- GDPR: Support to set preferences over the web
- GDPR: Support for subject forgetting
- Sending Bulk Emails - manual
- Contracts
- Partner in a contract
- Generate messages from system with patterns and AI
- Group of contacts from address books for better management
- Evidence of contacts and related business data
Finance management
System modules
System management
- moduleclientoptions
- Electronic sign even on mobile device
- formattedtexts
- System Configuration
- Processes in use
- Client
- Member Management for churches, non-profit organisations
- Configure gateways for external messages
- Corporate email and communication processing
- Email messages
- Rules for external messages
- Secure business communication
- Sending 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
- System Groups and Teams for rights settings
- User Processes
- System module
- System User
- User administration
- User Administration
- Connecting users to VOIP PBX
- Trusted User Device
- Secure Key Wallet - Safe storage for digital keys
- Data vault for Company secret & Classified data storage
Framework
- AyMINE frm module - corestone of the ecosystem
- Description of the view of the record details
- Private Notes to Records that no one can read
- AyMINE Access control and security
- Introduction to the application
- Using Drag & Drop even on mobile devices
- AyMINE icons are language for fast orientation
- Delete object to the trash
- Principal dashboard
- Settings your own configuration
- AyMINE Gestures and Keyboard Shortcuts
- AyMINE User Rights Control
- Install AyMINE to windows
- About AyMINE
- Work with list of records
- AyMINE on mobile device
- List of records
- How filtering in lists works
- cliplink
- System rights
- Module is the principal brick of the aymine ecosystem
Project Goals
Goal allows to include the definition of the project objective in the project analysis, in particular to link requirements to objectives.
Objectives are part of the project documentation. Describing them as a separate element in the analysis gives the possibility to define for each requirement which project objective is fulfilled by it.
The logic of the goal in the documentation corresponds to its concept in the motivation layer ArchiMate.
Common program goals for multiple projects

A goal is always included in some part of the analytical model. The motivation model should be part of the project documentation, so the objective will logically belong to the project. However, the same goal can be followed by multiple projects and can refer to a common goal.
If you are implementing projects pursuing common goals, it's a common to define the program under which the goals are pursued and the projects are coordinated. The programme defines programme objectives, which can then be subdivided into sub-objectives that are met by individual projects.
Projects may fulfil their own objectives, derived programme objectives or a direct programme objective. The structure of the objectives should be adapted to the programme complexity. Be careful not to hunt to many rabbits at once :)
How the programme and its objectives are defined
The programme is registered in the system as a "global" project and the individual projects are its sub-projects. Thus, the projects will take their target from the programme to which they belong.
We recommend keeping the programme objectives and sub-objectives within one analytical model, i.e. the programme. The objectives can be better managed and reviewed when they are together. The programme manager has simple overview that all goals relate each other correctly.
If you want to model the incentive level in detail and create an incentive scheme, it is possible to use connector to Enterprise Architect and manage the model there.
The business goal in the analytical model
Goal is a part of the project's analytical modal, it is not a part of the enterprise architecture. Enterprise architecture model describes As-Is state , whilst the goal describes direction to the To-Be state.