Related links
Framework Core functionality
- Client-Defined attributes
- Framework dependency on the open-source libraries
- Default server methods
- Export collection of objects
- AyMINE Framework Server
- The AyMINE licence model
- System Rights
- Import collection of objects
- Multi tenant Architecture
- Strings and translations
- System messaging
- User sessions
- Configuration of the user-defined fields
SOA Architecture
Support for Service Object Architecture and Internal Event ManagementLibraries & Lincences
Module - support for management
Front-End Scripting
System Management
- SaaS Management Module
- Management of the SaaS service client
- Encryted wallet storing access keys for data vault
- Definition and Management users in the SaaS system
- Management of the system users
- System right management
- System role is how user administrator sets the rights
- File access, storing and locking
- Communication geateways
- Private Object Marks, Sign & Notes
Task Management Module
- About TSK module
- Support for voting and decision management
- Support and implementation notes for FMEA
- Support for the Methodology Management
- Project Methodology Support
- Project Roles - Data model and implementation notes
- Actions and Meeting Agenda
- Description of person and supplier competencies
- Business event
- Problem & Helpdesk management support
- TSK module releases
- User Reminder
Task & Task pattern
Mobile & Web Application
- clientprogramming_fevaldataobject
- userinterface-objectstructure
- cliplink
- npmlibraries
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- npmlibraries_stringlibrary
- clientprogramming
- mobileapplication
- languagesupport
- objectdefinition_multiupdate
- Object API – object <g>
- clientprogramming_fevallanguage
- clientprogramming_fevaluser
- objectdefinition_viewdefinition
- offlineobjects
- System console
- Runtime debugging
- objectdefinition_detailview
CMS - Content Management & Web API services
FI - Finance Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partHR - Human Resources
Acquisition and purchase support
- Acquisition business view
- Acquisition business data model
- Pruchase – technical implementation
- Acquisition data view
Delivery supports evidence and process steps related with the asset order and delivery. During the delivery process user can also create the delivery evaluation as a part of the supplier quality evaluation and qualification.
Acquisition business view
The delivery business view presents the following view:
Acquisition business data model
Business objects of the acquisition support:
Pruchase – technical implementation
Acquisition object
Acquisition encapsulates the whole acquisition and delivery process. It contains data necessary to manage the acquisition process as well as links order and delivery data.
Acquisition could be a multilayer object where super-layer encapsulates the subordinated. Super-layer is used only in case that single acquisition requires acquisition from several suppliers. The decision process is then linked with the super-object and all parts of the acquisition is approved at once
At the lowest level, single acquisition
- Can be linked with several suppliers requested to make a bid
- Is linked with single supplier with offer
If acquisition is split between two or more suppliers during the offer evaluation, the acquisition is split to two or more sub-acquisitions single for each supplier.
Purchase Delivery object
Note: Purchase delivery is internally managed as the same object as the selling-deliery object. It supports both processes.
Changes from abstract ancestor
- Delivery defines its own user types
Delivery record
Records are object implemented in the task module. They are reused here. Delivery record is one of the supported types for records and so extension is not necessary.
Acquisition data view
Appropriate part of the data model:
Other modules extensions
Decision
Delivery object extends list of objects that can be linked with the decision