Public Area
|
About Emplacement ConceptEmplacement ConceptEmplacement Concept is descriptive grand total as representation of a technical entity that integrates all aspects together with relation to geometrical, mechanical and functional point of view. Emplacement Concept represents a comprehensive description of all aspects of a module functionality including all implications from product side, from process side and from interaction with other modules. The format of all files bases on XML and are standardised with XML Schemas. Information is stored into single location and used and viewed in many. As example the human readable documentation of a Emplacement or Blue Print can be generated on fly upon the request. This ensures that the information remains always valid and e.g. documentation is not becoming obsolete.
EmplacementThe Emplacement file is an electronic specification of a collection of similar kind of modules as a meta-module and the content of these files are controlled by the User Group promoting and developing the technology. The emplacement offers the standardisation and harmonisation over the content of a module, but it always remains at higher abstraction and generalisation levels than a hardware module and its associated BP file. The Emplacement file presents all the available interfaces, specifies the processes present, and the names of the offered properties. In other words Emplacement specifies the standardised minimum set of requirements and abstractions, which are fulfilled and specified later in details by the BP file. The Emplacement is composed of one or more Profiles, which contain the specifications for the modules. ProfileThe Profile is a reusable building block for module specifications. The module description i.e. BP will be instantiation of one Profile and Emplacement. Blue PrintThe Blue Print (BP) file is an electronic specification of a real implemented module i.e. virtual representation of the module and its features. The file is created and supplied by the vendor of the module and it is supposed to travel along the module throughout the module's lifetime. The very same BP file is shared by all the modules of the same type. History ContainerThe History Container (HC) is the file containing the module instance specific information. It is as well created by the module provider and shall travel together with the module having even tighter relationship with it than the BP. The HC will be updated during the use of the module at important events like change of owner of the module, after test and calibration runs, usage hours, service events, etc. References
Last updated : 2016-07-06 Copyright © 2006- TUT / MEI / Niko Siltala |