their potential in VR applications for diverse
purposes, such as ergonomic studies, safety training
for Health, Safety Environments (HSE), and
visualization of physical simulations, project
documentation and real-time operational data.
EnViron is integrated into CEE offering
resources for real-time 3D visualization and
interaction in CAD models with enough realism and
performance to be used for collaborative virtual
prototyping, design review, change management
systems, training, and visualization of engineering
simulations among other activities.
4.4 CEE Scientific Workflow
In recent years, several industries have improved
their operations through Workflow Management
Systems (WfMS) – improvement of data
management and better coordination of activities
through specific Business and Scientific and
Engineering Process. However, there are remarkable
differences between Business (BWfMS) and
Scientific Workflows (ScWfMS). (Weske et al.,
1998) identified that in a scientific environment
scientists will typically specify their workflows
themselves, while in a business environment; a
system administrator is commonly responsible for
this task. Another characteristic of ScWfMS pointed
in their work is the need to trace workflow
executions. An engineer may need to reuse a
workflow in order to reproduce results. The
operations a user performs on a given data must be
recorded in order to provide engineers with the
benefits of successful and unsuccessful workflows.
Scientific workflows often begin as research
workflows and end up as production workflows.
Early in the lifecycle, they require considerable
human intervention and collaboration; later they
begin to be executed increasingly automatically.
Thus in the production mode, there is typically less
room for collaboration at the scientific level and the
computations are more long-lived. During the
research phase, scientific workflows need to be
enacted and animated (fake enactment) far more
intensively than business workflows. In this phase,
which is more extensive than the corresponding
phase for business workflows, the emphasis is on
execution with a view to design, and thus naturally
includes iterative execution. The corresponding
activity can be viewed as a “Business Process
Engineering” (BPE). For this reason, the approaches
for constructing, managing, and coordinating
process models are useful also in scientific settings.
In this way, Scientific Workflows are to PSEs what
Business Workflows are to Enterprise Integration.
4.5 CEE Implementation
Service-Oriented Architecture (SOA) is a style of
architecting software systems by packaging
functionalities as services that can be invoked by
any service requester (Ort, 2005). An SOA typically
implies a loose coupling between modules.
Wrapping a well-defined service invocation
interface around a functional module hides details of
the module implementation from other service
requesters. This enables software reuse and also
means that changes to a module’s implementation
are localized and do not affect other modules as long
as the service interface is unchanged.
The adoption of an SOA for CEE produced a
reduction of technology development costs by
leveraging functions already built into legacy
systems. SOA architectures are becoming a popular
and useful means of leveraging internet technologies
to improve business processes in the oil & gas
industry nowadays.
An Enterprise Service Bus (ESB) is a pattern of
middleware that unifies and connects services,
applications and resources within an enterprise. ESB
is a platform built on the principles of SOA and
other open standards to help applications integrate
seamlessly. Put another way, it is the framework
within which the capabilities of a business'
application are made available for reuse by other
applications throughout the organization and
beyond. The ESB is not a new software product, it's
just a new way of looking at how to integrate
applications, coordinate distributed resources and
manipulate information. Unlike previous approaches
for connecting distributed applications, such as RPC
or distributed objects, the ESB pattern enables the
connection of software running in parallel on
different platforms, written in different languages
and using different programming models.
Our proposed CEE has component-based
architecture in order to facilitate the reuse of
elements. The architecture of the CEE uses a BPEL
ScWfMS as its kernel while the CSVTool, Environ
and the other components are seamlessly accessed
through the ESB according to the collaborative
necessities of the teamworkers.
When the service-oriented approach is adopted
for designing the CEE, every component, regardless
of its functionality, resource requirements, language
of implementation, etc., provides a well-defined
service interface that can be used by any other
component in the environment. The service
INTEGRATING VR IN AN ENGINEERING COLLABORATIVE PROBLEM SOLVING ENVIRONMENT
127