AyMINE – Technical documentation
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Region / project / methodology
Change management process in a project
Qualification of user or contact
Right to Manage Qualifications
Methodology and Quality Management systems
What a methodology / QMS consists of
Objects affected by the problem
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
Objects related to the task pattern
Contacts and directories module (CRM)
Address book or people and companies
Web management and automation
Receiving a message from the web
Asset management module
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
The AyMINE framework module
Configure how your system looks and works
Gestures and keyboard shortcuts
How the system works and how it protects data
Private notes and tags for objects
Filtering in the list of records
Additional functions with files
Copying and moving files between objects
Files (documents) linked to the object
Product categories are a general tool for segmenting products and assets. They are essentially a codebook that allows for segmentation according to the needs of the company.
Examples of categories for a bank might be:
- For a bank: investment services, credit services, cards.
- For a manufacturing company: electronic parts, components, fasteners.
- For a car dealership: new cars, used cars, service, rental.
What is the relationship between products and categories?
Every product belongs to a category. A category can therefore be seen as a more general concept than a product. Specific assets always also have a category, but so it is always derived from the product, so it corresponds to the category to which the product belongs.
Categories can be structured into a hierarchy for a more detailed breakdown. If you use a hierarchy, we recommend using only the lowest level of the hierarchy for products for clarity. You should actually have a reasonable reason to copy the category hierarchy into products as well.
Categories and products may form multiple trees, or they may not form a hierarchy at all. Therefore, it makes sense to create your own category and product trees or groups for the products you manufacture and purchase. Even within purchased, it is useful for clarity to separate those purchased for production and those purchased by the organization to support its own operations, i.e. typically for offices, building management, etc.
How and why use categories?
The main purpose of categories is to allow a global breakdown of products as is customary in the organization and how assets are broken down for reporting. This is also what the category structure should follow.
In principle it is not necessary to use categories, they are only for clarity. It is possible to have only one single category – e.g. an all-encompassing all; at least one is needed because without it you cannot record assets or define products.