| 1. |
- Boström, Henrik, et al.
(författare)
-
On the Definition of Information Fusion as a Field of Research
- 2007
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- A more precise definition of the field of information fusion can be of benefit to researchers within the field, who may use uch a definition when motivating their own work and evaluating the contribution of others. Moreover, it can enable researchers and practitioners outside the field to more easily relate their own work to the field and more easily understand the scope of the techniques and methods developed in the field. Previous definitions of information fusion are reviewed from that perspective, including definitions of data and sensor fusion, and their appropriateness as definitions for the entire research field are discussed. Based on strengths and weaknesses of existing definitions, a novel definition is proposed, which is argued to effectively fulfill the requirements that can be put on a definition of information fusion as a field of research.
|
|
| 2. |
- Bubenko, Janis, et al.
(författare)
-
An Intentional Perspective on Enterprise Modeling
- 2010
-
Ingår i: Intentional Perspectives on Information Systems Engineering. - Berlin, Heidelberg : Springer Berlin/Heidelberg. - 9783642125430 - 9783642125447 ; , s. 215-237
-
Bokkapitel (övrigt vetenskapligt/konstnärligt)abstract
- Enterprise Modeling (EM) has two main purposes: (1) Developing the business, which entails developing business vision, strategies, redesigning the way the business operates, developing the supporting information systems, etc., and (2) ensuring the quality of the business where the focus is on sharing the knowledge about the business, its vision and the way it operates, and ensuring the acceptance of business decisions through committing the stakeholders to the decisions made. In addition, EM has also shown to be useful as a general tool for articulating, discussing, and solving organizational problems. Based on a number of case studies, interviews and observations this chapter defines what is required from EM when adopted for these purposes and intentions respectively. More precisely, it addresses the following types of requirements; documents and models required as input, models that should be developed, requirements on the modeling language, requirements on the modeling process, tool requirements and model quality requirements. The defined requirements are then discussed taking a specific EM method, Enterprise Knowledge Development (EKD) as example.
|
|
| 3. |
|
|
| 4. |
|
|
| 5. |
- Schmidt, Bernard, 1981-, et al.
(författare)
-
Big data in maintenance decision support systems : aggregation of disparate data types
- 2016
-
Ingår i: Euromaintenance 2016 Conference Proceedings. - 9786188260108 ; , s. 503-512
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- There is need to obtain reliable information on current and future asset health status to support maintenance decision making process. Within maintenance two main sources of data can be distinguished: Computerized Maintenance Management System (CMMS) for asset registry and maintenance work records; and Condition Monitoring Systems (CM) for direct asset components health state monitoring. There are also other sources of information like SCADA (Supervisory Control and Data Acquisition) for process and control monitoring that can provide additional contextual information leading to better decision making. However data produced acquired and processed and in those system are of disparate types, nature and granularity. This variety includes: event data about failures or performed maintenance work mostly descriptions in unstructured natural language; process variables obtained from different types of sensors and different physical variables from transducers, acquired with different sampling frequencies. Indeed, condition monitoring data are so disparate in nature that maintainers deal with scalars (temperature) through waveforms (vibration) to 2D thermography images and 3D data from machine geometry measuring. Integration and aggregation of those data is not a trivial task and requires modelling of knowledge about those data types, their mutual dependencies and dependencies with monitored processes. There are some attempts of standardisation that try to enable integration of CBM data from different sources. The conversion of those amount of data in meaningful data sets is required for better machine health assessment and tracking within the specific operational context for the asset. This will also enhance the maintenance decision support system with information on how different operational condition can affect the reliability of the asset for concrete contextual circumstances.
|
|
