topquadrant semantic web and fea © copyright 2001-2005, topquadrant inc. the information in this...

TopQuadrant Semantic Web and FEA

© Copyright 2001-2005, TopQuadrant Inc.

The information in this presentation is proprietary to TopQuadrant and should not be duplicated, used or disclosed without permission.

The Semantic Web and the Federal Enterprise Architecture

© Copyright 2001-2005 TopQuadrant Inc., “TopMIND Training - Getting Ready for the Semantic Web”, slide 2

TopQuadrant

For Humans: Who is using what business systems to do what? Who is using what technologies and products to do what? Where components are being re-used or could be re-used? Who can we partner with at our agency and other

agencies? How is our agency architecture aligned with the FEA? How new technologies (ie; XML, Web, Security) are being

taken up at our agency and at other agencies? Are they mature enough for e-government?

What systems and business processes will be affected if we upgrade a software package?

…

For applications: Using an SOA, it can provide “An Active Enterprise

Architecture”, that is “Consultable” “Executable”

What is Enterprise Architecture for? Answering questions


TopQuadrant

Semantic Enterprise Architecture Environments: Lifting the “lid on the enterprise”

Enterprise Architecture is a “System of

Systems”


TopQuadrant

A Problem Statement

Over 150 executive agencies are supporting information initiatives: some for internal use, some for direct service to citizens.

Many of them are doing very similar things, but calling it by different names.

How can we get the whole government to work as if it were a coordinated unit, rather than 450 different approaches?


TopQuadrant

Federal Enterprise Architecture – Reference Model

What is a “Reference Model”?

A basic model for something (system, architecture, whatever)

When someone builds their own (system, architecture, whatever) they extend the reference model


TopQuadrant

Reference Models we know and love

OSI – Open Systems Interconnection (networking)

RM-ODP – Open Distributed Processing

OAIS – Open Archival Information Systems

CIDOC – Cultural Heritage (Museums)

DERM – “Digital Earth” – geospatial information

OGC – Geospatial information


TopQuadrant

FEA high level view

Business Reference Model (BRM)• Lines of Business• Agencies, Customers, Partners

Service Component Reference Model (SRM)• Service Layers, Service Types• Components, Access and Delivery Channels

Technical Reference Model (TRM)• Service Component Interfaces, Interoperability• Technologies, Recommendations

Data Reference Model (DRM)• Business-focused data standardization • Cross-Agency Information exchanges

Performance Reference Model (PRM)

• Government-wide Performance Measures & Outcomes• Line of Business-Specific Performance Measures & Outcomes

Federal Enterprise Architecture (FEA)

Busin

ess-D

riven A

ppro

ach

(Citize

n-C

ente

red Fo

cus)

Com

ponent-B

ase

d A

rchite

cture

s


TopQuadrant

English (describe the model and how to extend it)

Diagrams

XML (DTD, XSD, etc.) RDF/S

OWL

How are reference models expressed?


TopQuadrant

Why use RDF for an Reference Model?

Flexible, expressive models

Extensible in many different ways

Compatible with well-known modeling paradigms (e.g., OO)

Declarative expression of models for re-use

General graph modeling

Graph merging is a primitive operation

RDFS provides frame structure

OWL Description Logic

RM Requirements RDF Features


TopQuadrant

FEA Reference Models – at a glance

PRM


TopQuadrant


BRM


TopQuadrant


SRM


TopQuadrant


TRM


TopQuadrant

FEA is More Than a Set of Simple Taxonomies

From FEA SRM v.1.0 – Use case, page 28


TopQuadrant

Our FEA RMO (Reference Model Ontologies) Work

A modular framework: FEA Core FEA BRM FEA PRM FEA SRM FEA TRM FEA DRM BRM – PRM Bridge

Agency extensions: Agency template DoD extensions (connections to DODAF) FAA extensions


TopQuadrant

Competency Questions for FEA RM O

What are the Measurement Areas for the PRM? What are the Business Areas for the BRM? What are the Service Domains for the SRM? What are the Service Areas for the TRM?

For a given Measurement Areas, what are the Measurement Categories?

…

For a given Line of Business, what Business Area is it in? …


TopQuadrant

Competency Questions for FEA RMO

This isn’t as easy as it sounds . . . From the PRM:

[in the context of the Mission and Business Results Measurement Area] More specifically, the PRM’s Measurement Categories are the same as the BRM’s Business Areas and Lines of Business. The Generic Measurement Indicators of the PRM are the same as the Sub-functions of the BRM


TopQuadrant

Competency Questions for FEA RMO

Questions about technology initiatives, components, products, etc.

What Measurement Area measures the performance of some technology product?

In what Service Standard or Specification is a product classified in?

What Service Specifications are in a particular Service Category? …

What components support this business area? What Access Channels are used by this component? What are other similar components? (defined by the

OMB directions as components that belong in the same SRM category, support the same business subfunctions, use the same technology, use the same generic measurement indicators, etc)


TopQuadrant

Competency Questions become Modeling Requirements

Entities in the model (business areas, service specifications, etc.) are sometimes used: as classes

“which access channel is used for this component?” – there is a set of service specifications that are access channels – Web service, Blackberry, Internet Explorer, etc.

and sometimes as instances “access channels is one of service categories”

Parts of one model (namely, BRM) are re-used in another model (PRM)


TopQuadrant

Modeling Requirements become Model Constructs (in OWL)

Parts of one model (namely, BRM) are re-used in another model (PRM)

[in the context of the Mission and Business Results Measurement Area] More specifically, the PRM’s Measurement Categories are the same as the BRM’s Business Areas and Lines of Business. The Generic Measurement Indicators of the PRM are the same as the Sub-functions of the BRM


TopQuadrant


More specifically, the PRM’s Measurement Categories are the same as the BRM’s Lines of Business.

subClassOf

rdf:type

??

brm:ManagementOfGovernmentResources

brm:LineOfBusiness

brm:ServiceForCitizens

brm:SupportDeliveryOfServices

brm:LineOfBusinessMeasurementCategory

prm:MeasurementCategory

subClassOf

HumanResourceMgmt

IncomeSecurity

RevenueCollection

rdf:type

rdf:type

rdf:type

HumanResourceMgmt

IncomeSecurity

RevenueCollection

subClassOf

SupplyChainMgmt


TopQuadrant


Entities in the model are sometimes used as classes and sometimes

as instances

prm:MeasurementArea prm:MeasurementCategory

prm:CustomerResultsMsmtCatCustomerResults

ServiceCoverage

ServiceQuality

ServiceAccessibility

CustomerBenefit

rdf:type

Timeliness

rdf:type rdfs:subClassOf


TopQuadrant



as instances


CustomerResults

ServiceCoverage

ServiceQuality


CustomerBenefit

rdf:type

Timeliness


NOT OWL-DL COMPLIANT

Solution 1: combine instance and class as a

single entity.


TopQuadrant



as instances


prm:CustomerResultsMsmtCatCustomerResults

ServiceCoverage

ServiceQuality


CustomerBenefit

rdf:type

Timeliness


Solution 2. Link class and instance

together with a Restriction

comprises

comprises


TopQuadrant

Modeling Patterns

Why all this work?

Can’t we just put all the entities into a tree?


TopQuadrant

The Whole Model – Tree of Instances, Organized in Parallel Classes

CustomerResults

ServiceCoverage

ServiceQuality


CustomerBenefit

Timeliness

comprises

Quality

Reliability

Info and Data

Financial

Efficiency

DeliveryTime

ResponseTime

Access

Automation

Integration

Availability

ITComposition

Functionality

Compliance

rdf:type

prm:MeasurementAreaprm:MeasurementCategory

prm:CustomerResultsMsmtCat rdf:type

rdf:type

rdfs:subClassOf

prm:TechnologyMsmtCat rdf:type

prm:MeasurementIndicator

prm:Timeliness


rdf:type


rdf:type


TopQuadrant

FEA Ontologies in SWOOP


TopQuadrant

FEA-RMO Lessons

Good natural language Reference Models help ontology development

Modeling Principles and Patterns are key – often evolve iteratively

Modular Architecture benefits concurrent lifecycle management

OWL works and reasoning pays off in generic code

Semantic Applications can be built quickly




TopQuadrant FEA REGISTRY - A SEMANTIC WEB APPLICATION


TopQuadrant

FEA Registry – semantic application


TopQuadrant

Ontology-Based EA Registry: TopSCAPE-EAFEA and DOD extensions

Select either FEA Ontology or Agency-Specific Ontologies

Service specifications with links to more details

Search over all models for concepts

Demonstration at www.topquadrant.com/EAworld/index.htm


TopQuadrant

TopSCAPE-EA:Search Example – “Quality”

Search results show FEA path

Demonstration at www.topquadrant.com/EAworld/index.htm


TopQuadrant

TopSCAPE-EAExample of DOD extensions to FEA

Agency-specific extensions shown “green”

Hot links to TRM areas


TopQuadrant

TopSCAPE-EAExample of DOD extensions to FEA (cont.)

Replacements as well as additions are shown


TopQuadrant

EA Analyst – Extension Report


TopQuadrant

EA Analyst – Comparing two extensions

One agency makes a replacement where another agency does not

Two agencies make different replacements


TopQuadrant

Mapping Components to the FEA Models - 1

Available elements from merged reference models


TopQuadrant

EA Analyst – Initiatives Report


TopQuadrant

Federal Enterprise Architecture – now and future

EA reference expressed in prose

Additions/replacements made as documents

Electronic access follows prose presentation (human intervention)

EA reference expressed as model

Additions/replacements made in model

Both electronic and prose follows model


TopQuadrant

Beyond Enterprise Architecture

Reference models have been around for a while (OSI, RM-ODP, etc.)

NetworkingDistributed ProcessingGeospatial dataCultural heritageArchiving WorkfloweLearningSupply chain operations


TopQuadrant

Example of Exporting OWL: FAA

<?xml version="1.0" ?>

- <rdf:RDF xmlns:fea="http://www.osera.gov/owl/2004/11/fea/fea#" xmlns:srm="http://www.osera.gov/owl/2004/11/fea/srm#" xmlns:ns1="http://www.topquadrant.com/owl/2005/03/fea/faasrm#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:owl="http://www.w3.org/2002/07/owl#">

- <owl:Ontology rdf:about="http://www.topquadrant.com/owl/2005/03/fea/faasrm">

<owl:imports rdf:resource="http://www.osera.gov/owl/2004/11/fea/srm" />

</owl:Ontology>

- <srm:BusinessComponentSystem rdf:about="http://www.topquadrant.com/owl/2005/03/fea/faasrm#AirTrafficCRU-X_System">

<fea:mnemonic rdf:datatype="http://www.w3.org/2001/XMLSchema#string">CRU-X</fea:mnemonic>

<srm:realizes rdf:resource="http://www.osera.gov/owl/2004/11/fea/srm#TimeReporting" />

<srm:usedBy rdf:resource="http://www.osera.gov/owl/2004/11/fea/brm#FederalAviationAdministration" />

<ns1:hasDeploymentStatus rdf:resource="http://www.topquadrant.com/owl/2005/03/fea/faasrm#CommissionedInitalDeployment" />

<rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Air Traffic CRU-X System</rdfs:label>

</srm:BusinessComponentSystem>

…

…


TopQuadrant

Semantic FEA Solutions:OMB and Agency Budget Proposal System

Pro

po

sed

Bu

sin

ess

Ca

se

Sco

pe V

alid

ate

A

ssess

FEA Reference Models•feedback re. quality

•feedback re. use•feedback re. relevancefor strategic planning,

capital planning,& risk management

Metrics

Recommendations for improvement and

partnering

Ontology-Based Budget

ProposalRepository

Validate Value Proposition

C. Potential for reuse of Technologies and Components

A. Business Area and LOB supported?

B. Number of proposals with same capabilities?

Budget Proposal Assessment

FEA

Onto

logy-B

ase

d Im

port

D. Synergies for partnering

Adapted from: Dr. Michael J. Kurtz, “The Role of Electronic Records Management in Implementing eGovernment: Electronic Records and the Federal Enterprise Architecture”, NARA, 4/15/04

Assessment down from 3 months to 7 weeks

Re-submit period up from 1 week to 6 weeks - allowing time for collaborations to be negotiated


TopQuadrant

Semantic EA Solutions:IT Governance

TopSCAPE-ITG

Web-Services

Web Services

Active ModelsCC

FEA, BEA Models

Government Agencies

Analytics Engine

Web

Web-Services

Business Cases

Partnerships and Projects

OW

L

OW

L

OW

L

OW

LA

naly

tics

Bro

kerCCCC

Rules and Policies

Capabilities and

ComponentsComponent Registries

Forms and Documents

OW

L

IT G

overn

ance

D

ash

board

CC

Deci

sion

Su

pport

Advis

or

Dynam

ic F

orm

s B

roker

CC

Busi

ness

Case

C

onst

ruct

or

CC

topquadrant semantic web and fea © copyright 2001-2005, topquadrant inc. the information in this...

Documents

topquadrant semantic

topquadrant copyright

reference model slide

agency architecture

active enterprise architecture

topmind training

business systems

reference models