The "5S" Grid in the Roadmap for Networked Organizations

1
The "5S" Gridin the Roadmap for Networked
Organizations

• Prof. iga Turk and Dr. Peter Katranuschkov
• Global Grid Forum 16Athens, Greece, February
  13-16, 2006

2
Presentation Contents

• VO Context
• 5S requirements
• All good things in life start with an "S"
• Semantics is one of them
• Semantic Framework in InteliGrid

3
CE Vision 2010 Industrial Innovation Transition
CE-NET A Roadmap towards the Collaborative
Enterprise - CE Vision 2010
www.ESoCE.net
4
Virtual Organization
a temporary collaboration to exploit a business
opportunity (with each business transaction being
performed by a collaborating legal entity)
Engineering VO sharing semantic and sensitive
information
a temporary network of companies, suppliers,
customers, or employees, linked by information
and communications technologies, with the purpose
of delivering a service or product.

• Common requirements
• functional
• technical

VTT
5
Virtual Organization Research

• Baseline
• 30 projects in FP5 IST Most projects developed
  their own ontologies and prototype platforms.
• In other words the VO interoperability problem
  has been made worse by RD so far.
• Growing expectation in the VO community
• Collaborative ICT infrastructure needs to become
  embedded in the standard Internet infrastructure
• Semantic web, grid?
• user survey who are the users ?

6
Applied Roles in InteliGrid

• Engineering End User - further subdivided in
  domain-specific subroles, e.g. in
  AEC/FM architect, structural engineer,
  building services engineer etc.
• Project Manager / VO Manager
• Grid Administrator
• Software Developer
• Service Provider
• Real Organisation CIO
• Virtual Organisation CIO
• Client (Owner)

Many of these are typical New Economyroles
7
The Unified Templatefor User Requirements
CaptureSpecifically adaptedto InteliGrids
needs
8
Results -Synthesized Requirements
synthesis ?
9
The "5S" Requirements

• security - industry eager to move to a ground-up
  secure environment
• simplicity - must work seamlessly with current
  client applications and operating systems (read
  Windows, not Linux)
• stability standards - a need for stable
  long-term specifications (not 4 evolving and
  competing specs. for semantic annotation of web
  services - let alone grid services)
  Corruptissima re publica plurimae leges
• scalable service orientation - well accepted and
  known
• semantics - must support rich, domain specific
  semantics - not about disks and CPUs but about
  fuselages, walls, proteins

10
Semantics

• InteliGrid technical framework
• InteliGrid conceptual framework
• InteliGrid ontology framework
• InteliGrid architecture
• InteliGrid use case framework

11
Technical framework
"real" world
modelled in
conceptual layer
implemented in
software layer
using
basic resource layer
modelled in
12
ConceptualFramework
syntactic
structural
semantic interoperability
semantic web stack
XML,XMLSchema
RDF, RDFS
rules
logic
proof
trust
ontology
common sense
CYC
conceptual stack
eng. productsand processes
engineering ontology
IFC
STEP
IFO
?
process protocol
web servicesand grid services
OWL-S, WSDL-SWSMO
WS-I WSDL, UDDI, SOAP
GSDL
OWLOWL-GGSMO
WS-IWSRF
primitiveresources
architecture
13
Ontology Framework
generic
Distributedrun-time environment
OrganisationalOntology
User/RoleAuthorisations
Auth.Service
represents
descr
uses
Product/ProcessModel
Ontology-BasedVirtual User Desktop
OWL
RBAC
ref
WSRFServices
BusinessProcessOntology
ServiceOntology
Services
represents
uses
descr
WebServices
WebServices
OWL-S
OWL
WSDL
ref
run on
ResourceOntology
SystemResources
represents
uses
descr
OWL
?
grid
Semantics Specs
14
InteliGridarchitecture
applications
analysisapplication
CAD designapplication
project management
projectcollaboration
businessservices
productdatabase
simulation
exchange rates
code checking
interoperabilityservices
generic ontology services
domain ontology services
about servicesWSDLUDDI
grid ontology
domainont. 1
domainont. n
domainont. 2
Gridlabservices
condor
grms
viz
OGSA-DAI services
gas
corelayer
architecture
15
Generic engineering process use case framework
DEMO authentication,security
core ontology server functions running

• join the VO
• find object to work on (with aid of semantics)
• match object to tool (with the aid of semantics)
• use the tool (on the grid providing high
  performance)
• share results on the grid

core ontology server functions running
secure,robust,scalable
demonstrated on Sofistik applications
demonstrated, OGSA-DAI access to Conject, EPM
16
Use case framework
Ontology Service
1a. Get Data
Conject
CONJ-g
Business Object
BO Data -gt URIs
1b. Get Data
EPM-g
EPM
BO Process Schema
2. Process Data
SOF-g
Sofistik
3.
Typicalworkflow
0. Get Business Object
InteliGrid Client
17
Collaboration
generic
Distributedrun-time environment
OrganisationalOntology
User/RoleAuthorisations
Auth.Service
represents
descr
uses
Product/ProcessModel
Ontology-BasedVirtual User Desktop
OWL
RBAC
ref
WSRFServices
BusinessProcessOntology
ServiceOntology
Services
represents
uses
descr
WebServices
WebServices
OWL-S
OWL
WSDL
ref
run on
ResourceOntology
SystemResources
represents
uses
descr
OWL
?
grid
Semantics Specs
18
Conclusions

• User needs can be summarized as "5S" - security,
  simplicity, standards, semantics and service
  orientation.
• There are two "real" worlds that need to be
  modelled (with semantics)
• The domain
• IT infrastructure - the grid
• Are the two linked and how?
• processes are using resources to produce products
  and services