AyMINE – Technical documentation
User Modules
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Adminitration of areas, projects, calendars
Region / project / methodology
Change management process in a project
GDPR and record of qualifications
Qualification of user or contact
Right to Manage Qualifications
Methodology and Quality Management systems
What a methodology / QMS consists of
Customer Service Response Generation
Objects affected by the problem
Return project plan by baseline
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
The person responsible for the task
Working procedure – task definition
Objects related to the task pattern
Contacts and directories module (CRM)
orderSVG Order overview for customer groups
Web management and automation
Receiving a message from the web
Human resources
Human Resources module security
Manage department / division data
Synchronizing staff and system users
Products, assets and sales
Received order for goods or services
Finance management
Metrics and Measurements
Technical Modules
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
System Modules
The AyMINE Framework Module
Configure how your system looks and works
Gestures and Keyboard Shortcuts
More about how the system works
Private notes and tags for objects
Filtering in the list of records
System Management
Securing posts and internal discussions
Additional functions with files
Copying and moving files between objects
Files (documents) linked to the object
Formatted texts in the application
Gateway settings for external messages
IMP gateway settings for email communication
Internet Call Gateway Settings
Products
Products are a general description of a certain type of asset. The definition may sound complicated, but the product is exactly the same as the general use of the term.
Examples of products are refrigerators, mortgages, a CNC program to cut out a cabinet, a car, a Skoda, Octavia, a text editor, MS Word, a gear wheel 25mm in diameter with 50 teeth, etc.
The product can also be work, e.g. changing the wheels, repairing the fender, baking a cake, a German lesson for employees, etc.
What they are for in the system and how they are broken down
Products are used to determine what assets are present in a company. For example, if a company has programs for NC machines for various products, each of them is an asset. In order to better classify them according to their common characteristics, they are broken down into products.
In principle, products of 3 categories are distinguished:
- Purchased_ are products that a company acquires to use or consumes to produce its own products. Typically, they are inventories, consumer goods, investment purchases as well as procured services.
- Produced are products that are produced in a company. Typically sold products, semi-finished products (including those that are further consumed in downstream production), internal calculated works and provided services
- Traded are products procured for resale. Typically, they are products supplied for stock for resale.
The determination of products is, of course, always fully dependent on the company – what one uses, the other produces.
Product hierarchy
Products can be many in a company, and for better organization, they can be broken down hierarchically from a more general description to a more detailed description.
Examples of a hierarchy are the above examples auto > damage > Octavia. Keeping products in a hierarchical organization brings the possibility of order and better description. Detail depends on the number of products that are registered.
An important importance of a hierarchy is in relation to the categorization of suppliers. If you have a supplier that supplies a whole group of products, it is advisable to have this group together. You can then easily for the whole group save information about the supplier
Another possibility of organizing products are categories. Each product belongs to a category and with their help further subdivision is possible. The above mentioned car product may belong to the category of the company fleet.
Note: The product hierarchy is promoted when the status changes. If you change the state of a product, the states of all its specific variants will change. Products that do not have a state in common are unlikely to form a hierarchy expressing the relationship between the generic product and its specific variant. Consider whether there should be a breakdown across product categories in that case.
Product states
Product state is important information describing whether a product can be used. Therefore, pay attention to product status. Read more about product statuses here.
Composition of the product
Within the product it is possible to register its composition, i.e. what products and in what quantity are needed for its creation. Of course, the composition of the product makes sense to break down only in the case of manufactured products. The description of the composition of the product allows to calculate the price of the final product, the case of the order, and to check whether the product can be manufactured e.g. from stock.