Composable M&amp;S Web Services for Net-Centric Applications

Tolk, Andreas; Turnitsa, Charles; Diallo, Saikou Y.; Winters, Leslie S.

doi:10.1177/875647930600300104

Cited by 59 publications

(43 citation statements)

References 20 publications

(35 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This has also been affirmed by the findings of [27].  3D city models are currently scattered over public and private sectors in different systems, different conceptual models, different data formats, different data schemas, different levels of detail and different quality [34]. In addition, the potential of 3D models goes beyond visualization of 3D objects of virtual scenes to real 3D city models.…”

Section: The Research Approachmentioning

confidence: 84%

A Unified Building Model for 3D Urban GIS

El-Mekawy

Östman

Hijazi

2012

IJGI

120

View full text Add to dashboard Cite

Several tasks in urban and architectural design are today undertaken in a geospatial context. Building Information Models (BIM) and geospatial technologies offer 3D data models that provide information about buildings and the surrounding environment. The Industry Foundation Classes (IFC) and CityGML are today the two most prominent semantic models for representation of BIM and geospatial models respectively. CityGML has emerged as a standard for modeling city models while IFC has been developed as a reference model for building objects and sites. Current CAD and geospatial software provide tools that allow the conversion of information from one format to the other. These tools are however fairly limited in their capabilities, often resulting in data and information losses in the transformations. This paper describes a new approach for data integration based on a unified building model (UBM) which encapsulates both the CityGML and IFC models, thus avoiding translations between the models and loss of information. To build the UBM, all classes and related concepts were initially collected from both models, overlapping concepts were merged, new objects were created to ensure the capturing of both indoor and outdoor objects, and finally, spatial relationships between the objects were redefined. Unified Modeling Language (UML) notations were used for representing its objects and relationships between them. There are two use-case scenarios, both set in a hospital: "evacuation" and "allocating spaces for patient wards" were developed to validate and test the proposed UBM data model. Based on these two scenarios, four validation queries were defined in order to validate the appropriateness of the proposed unified building model. It has been validated, through the case scenarios and four queries, that the UBM being developed is able to integrate CityGML data as well as IFC data in an apparently seamless way. Constraints and enrichment functions are used for populating empty database tables and fields. The motivation scenarios also show the needs and benefits of having an integrated approach to the modeling of indoor and outdoor spatial features.

show abstract

Section: The Research Approachmentioning

confidence: 84%

A Unified Building Model for 3D Urban GIS

El-Mekawy

Östman

Hijazi

2012

IJGI

120

View full text Add to dashboard Cite

show abstract

“…In addition, we believe that hybrid simulation can also contribute to model-based systems engineering. Hybrid simulation modeling can be integrated with descriptive environments such as SysML [2] and embedded from single computer processing systems to distributed architectures using the High-Level Architecture (HLA) and the Semantic Web [5], and cloud computing. Distributed architectures can provide the recommended loosely coupled environment and standards such as HLA and the Semantic Web can facilitate interoperability.…”

Section: Discussionmentioning

confidence: 99%

Hybrid Simulation in the Enterprise and Model-Based Systems Engineering

Rabelo¹

2012

Ind Eng Manage

View full text Add to dashboard Cite

Hybrid discrete-continuous simulation models of the enterprise and of the life cycle of systems are very important. This set of models consists of system dynamics models, continuous models of the higher hierarchical and more abstracted levels and connected to it are a number of discrete event simulations for selected operational, tactical functions, and phases of the life cycle. For example, system dynamics modeling best fits the macroscopic nature of activities at the higher management levels while the discrete models best fit the microscopic nature of the operational and tactical levels in the enterprise. On the other hand, system dynamics model can represent the nature of systems architecture development and discrete models the operations of a particular system.There are several questions to be answered in the future:• Why practitioners are not trying to develop/use hybrid models of enterprises?• Why system engineers are not trying to integrate models of the different phases of the life cycle of a system?• Why system engineers are not archiving in an executable way simulation models of systems of phases before op-erations has been started? Hybrid Simulation Modeling in Enterprise Management Hybrid Simulation Modeling in Model-Based Systems Engineering (MSBE)The definition of Systems Engineering used is that which is given by the International Council on Systems Engineering (INCOSE) [1] "Systems Engineering is an interdisciplinary approach and means to enable the realization of successful sys-tems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, and then proceeding with design synthesis and system validation while considering the complete problem". On the other hand, INCOSE [2] defines MBSE as "the formalized application of modeling to support system requirements, design, analysis, verification, and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases".In the last decade, system engineers have started to replace the traditional documenting process of system engineering which has proven inappropriate for modeling the various levels of functionality The management of the Enterprise is one of the classical business problems. Even components of the enterprise such as its supply chain has already enough complexity. A supply chain is a network of facilities that procure raw mate-rials/services/technologies, transform them into intermediate goods and final products/services/technologies, and deliver the products/services/technologies to customers through a distribution system. The purpose of supply chain management is to provide the right quantity of the right product at the right time to the right customers at an optimal cost. A typical manufacturing supply chain is comprised of five elements: suppliers, manufacturers, distributors, retailers and customers. The process of integrating all these elements involves the coordination and cross-functioning of production pl...

show abstract

“…This example of a successful application of components of the common data engineering architecture is described in Tolk and Boulet (2007 Sudnikovich et al (2004) using the ideas described in Tolk et al (2006). During the first phase of experimentation, one selected system was equipped with an interface to identify challenges system experts are confronted with when they have to support the two requirements listed above.…”

Section: Data Engineering Supporting a Common Language Between Heteromentioning

confidence: 99%