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
Product status and change
Product status is important information that indicates whether a product can be used in production, as part of other products, or for sale.
The Change of product state is evaluated in AyMINE with respect to the effects on other objects.
Product states
The system supports the following product states:
Product status In preparation
Products in preparation are entered into the system but are not yet ready for their target use. Typically:
- They are being developed, but development is not complete.
- The product is to be purchased from a supplier, is being counted on, but their approval is pending
- They are planned in the business plan but not yet available
Product status Ready
Product development or approval has run its course, its documentation is complete, and it is eligible to be actively used. However, it has not yet been actively used.
The status is sometimes called Listing because the product (typically from an external vendor) is listed in an internal catalog.
A product that is ready is not in stock. It is typically not physically available except for test samples.
Product is Currently in use (shortly Active)
Product is being manufactured or purchased and physical copies are actually or generally available. This is the stage when no development is underway on the product. (However, there might be new version of the product under the development.)
Status Invalid
The product cannot be used for some reason. The status does not express whether or not the product has been active before, but cannot be used at the moment.
If a previously active product reaches the In Disorder state, the effects on other products that depend on it must be addressed (see below).
A product in In Disarray is assumed to be able to return to staging or active use once the deficiencies have been addressed.
Examples of reasons for temporary status:
- Certification or approval has expired, renewal is anticipated but has not yet taken place.
- The product has been temporarily discontinued by the supplier so that it cannot be used in further production
- The product has developed defects which are being investigated. The product has been withdrawn pending resolution, but is expected to be returned to production or sale
Status Withdrawn
The product is withdrawn if it is not expected to ever be available again in active use.
It is not necessary that the withdrawn product be in active use prior to withdrawal; it may have been withdrawn during development or through testing, typically based on unsatisfactory test results.
Status Undetermined
There may be products in the inventory whose status is not tracked. These have a status of undetermined.
Change of status within the product hierarchy
Products support hierarchical record keeping. If the status of a product that has specific variants is changed, the status of all specific variants is changed. If you want to change the status of only one specific variant, you must change the status for that variant.
If you only want to track the status of specific variants, set the general product to Undefined. This status will remain set only for the general variant, it will not carry over to the specific ones. You can continue to manage the statuses of specific product variants independently.
Products with an Undefined state should not be part of other products, as there is no active control over the effects of changing the state.
Change of state impact control
The system requires that for a product state change, attention is paid to all the impacts that the change will cause. If the product is used in other products, the responsible persons are notified by an alert sent in AyMINE that they must pay attention to the change of state of the product.
Warning: If a product used in other products becomes unusable, the responsible personnel for each individual product will be notified, but the status of those products will not themselves be actively changed. Staff must assess the impacts and decide what the actual impacts are on other products.
The change is not automatic immediately, as often the impact of invalidation is not immediate. For example, a product may be withdrawn but production from stock is still in progress.