Department of Homeland Security Pilot - PowerPoint PPT Presentation

1 / 42
About This Presentation
Title:

Department of Homeland Security Pilot

Description:

Create the application through Pure Assembly, using standard components and ... Create, modify, run, integrate and distribute high quality applications easily ... – PowerPoint PPT presentation

Number of Views:64
Avg rating:3.0/5.0
Slides: 43
Provided by: webser
Category:

less

Transcript and Presenter's Notes

Title: Department of Homeland Security Pilot


1
Department of Homeland Security Pilot

May 7, 2003
2
Contents
  • Vision
  • The Pilot
  • What the Pilot will Demonstrate
  • Architecture
  • Government Initiatives
  • Adoption of Web Services
  • Components and Reuse
  • ObjectBuilders LiveXML Product
  • Conclusion

3
Vision

4
Vision
  • Rapidly solve an existing business challenge
    through the use of Web Services
  • Create the application through Pure Assembly,
    using standard components and technology, storing
    the application in a technology independent way
  • Accelerate the adoption of Web Services by
    rapidly assembling New Solutions from COTS
    components

ObjectBuilders LiveXML Creates Technology
Independent Rich Client Internet Applications and
Web Services
5
Background
  • Homeland Security - The creation of the
    Department of Homeland Security (DHS) is the most
    significant transformation of the U.S. government
    since 1947, when Harry S. Truman merged the
    various branches of the U.S. Armed Forces into
    the Department of Defense to better coordinate
    the nation's defense against military threats.
    Tasked with integrating 22 various agencies, DHS
    must simultaneously provide for a secure homeland
    while architecting an infrastructure that rapidly
    integrates agencies, systems and cultures in a
    manner that can scale with the least amount of
    duplication and costs.

The investigation failed to turn up a single
agency, database or computer network that
integrates all counterterrorism information
nationwide Eleanor Hill, Director of Joint
Congressional Inquiry
6
Challenge
  • Business
  • What information can or should we make available
  • Who should have access to the information
  • Under what conditions should they have access to
    the information
  • Technical
  • Secure foundation
  • An architecture to integrate all the disparate
    systems
  • An integrated data model

7
Known
  • We need to deliver rapidly
  • The agreement on what information will be
    available and how will take significant time and
    effort
  • There is useful information that is currently
    only unavailable because of the lack of an
    integrated solution

8
Focus
  • The pilot is focused on providing a solution
    today that will integrate disparate systems and
    data sources
  • The pilot is focused on making the information
    that is already available through disparate
    systems or unrealistic manual request processes
    automatic and instantaneous
  • The pilot is focused on a solution that can grow
    dynamically and automatically
  • The pilot is focused on making it easy to publish
    information

9
Addressed in other Pilots
  • The pilot is not focused on security
  • The architecture used in this pilot is capable of
    using most security mechanisms and can easily be
    configured or adapted to use future mechanisms
  • The pilot is not focused on the political or
    policy debate over what information should be
    made available to whom, and when
  • It is the intention of this pilot to provide an
    application today that can dynamically grow
    (whereby information and agencies can be
    seamlessly brought on-line as new information is
    needed, or is made available) and provide a
    secure means for integrating and accessing
    information for disparate systems
  • The pilot is not focused on a standard data model
  • The pilot will demonstrate the ability to link
    different data models into one virtual business
    object model

We are already talking to other vendors about
their pilot projects and how we would combine the
pilots together
10
Need
  • Create a solution that can
  • Handle current and future security needs
  • Integrate disparate systems and data elements
  • Grow vertically and horizontally
  • Be maintained centrally and independently
  • Deliver rapidly and change even faster
  • Provide a simple mechanism to contribute data
  • Work online and offline

11
The Pilot

12
What the Pilot Demonstrates
  • Data Interchange via Web Services
  • Integration of common and disparate data
  • Multiply data formats
  • No integration server or bottleneck
  • Dynamic Discovery of New Services
  • Including presentation
  • Register Service and Share Models
  • Rich Client Application Created in XML
  • No integration server or bottleneck
  • Dynamic Update of Application
  • New functionality added real-time to client
    and/or server
  • Simple Toolkit for Publishing Service

13
Web Services Features Demonstrated
  • Web Services that integrate the Data, provide
    Business Functionality and have a Rich Client and
    Administrative Interface
  • Integration of disparate systems and data sources
    without and integration server
  • Web services working together to provide one
    application
  • Dynamic discovery of new services
  • Rich functionality over a thin pipe
  • A Library of Reusable Components

14
Architecture
15
Government Initiatives

16
E-Government Applications
  • The Federal Enterprise Architecture (FEA) is a
    business-focused framework for cross-agency,
    government-wide improvement
  • The FEA is providing OMB and Federal agencies
    with a new way of describing, analyzing, and
    improving the Federal Government and its ability
    to serve the citizen
  • The FEA will eliminate the organizational
    obstacles that have historically hindered
    improvement without forcing reorganization
  • The FEA is a business-focused approach and is not
    just for IT
  • The FEA provides a common framework for improving
    a variety of key areas

Citizen Centered
Business Line Focus
  • Budget allocation
  • Horizontal and vertical information sharing
  • Performance measurement and budget/performance
    integration
  • Component Based Architecture
  • Cross-agency collaboration
  • Improved service to the citizen
  • E-Government
  • Process integration
  • Call center convergence
  • and more

17
Web Services
  • The Web Services promise is not unlike the
    promises of the past. Better, faster and higher
    quality development has plagued software
    developers since the beginning. Each technology
    addition adds complexities.
  • Integration of disparate systems and
    architectures
  • Multiple hardware and software platforms
  • Multiple deployment options
  • Why will Web Services succeed where others have
    failed?
  • Assemble, vs. Coding
  • Web Services forces more assembly concepts
  • Leverages strengths of the Web Architectures
  • Most Software and Hardware Vendors support

18
Web Services
  • By applying four basic concepts, Web Services can
    deliver on the promise of better, faster and high
    quality applications that provide rapid
    integration and technology independence
  • Encapsulate component frameworks into easy to use
    services where the interface is as simple as
    using/learning one component
  • Provide configuration utilities and user screens
    to fill out the power of the service or framework
  • Build services so that they can be assembled
  • Provide a pure assembly layer (XML)
  • Technology, platform and deployment independence
    is achieved through the pure assembly layer.

19
Components and Reuse
  • Components are the key to reuse and speed,
    however, they can also be a curse if used
    improperly
  • When selecting components it is important to
    remember that we are trying to manufacture, not
    code.
  • Do I have to learn an entire framework of objects
    or can I access the power through one simple
    component or interface?
  • Can I assemble the component into my application
    or do I have to create a significant amount of
    interface code?
  • Does it perform the functionality that I need or
    am I creating add-ons or work arounds?

20
The ApplicationDelivery Real Business Value
  • Technology is ever changing and there will always
    be different cultural issues, preferences and
    yes, camps.
  • All technology advancements seem to have their
    strengths and weaknesses. The debates aside, they
    all have significant effects on our end user
    applications.
  • We are constantly rebuilding the end user
    application, the only questions is how far back
    did we go to get how far forward? It is desirable
    to keep moving forward.
  • It is necessary for the front end application to
    be independent of language, technology and
    platform.
  • By utilizing a Document Strategy (ASCII format
    like XML), this can be achieved. Documents like
    MS Word and this MS PowerPoint Document have
    achieved it, now we have a need for Application
    Documents.

21
The LiveXML Product

22
XML and LiveXML
  • XML and Web Services deliver components,
    ObjectBuilders products assemble the components
    into solutions without traditional code.

23
Business and Technical Challenges
  • The Next Generation Internet Application
  • Rich sophisticated client over a thin Internet
    pipe
  • They will contain the integration, intuitiveness
    and interactive capability of a traditional
    client server application
  • Multiple deployments simultaneously browser
    based, PDA, TV or remote
  • Continue to work when disconnected
  • Reduced latency, bottlenecks and congestion
  • Extensibility, maintainability, reuse and dynamic
    extensibility
  • Business Applications Need to be Deployed Rapidly
    and Change Even Faster
  • Real time WYSIWYG extensibility, maintainability
    and reuse
  • Provide a means for dynamically discovering new
    features and services
  • The Ability to Reuse, Share and Integrate
    Existing and New Technologies
  • Integration of disparate systems and data sources
  • New to integration Web Services and XML formats

24
Highlights of LiveXML
  • XML for specifying an application including
    presentation, business logic and data that is
    independent of technology
  • White Box Modules are preassembled service and
    business level components and subsystems that can
    easily be customized
  • Solutions are preassembled complete and package
    solutions that can be rapidly tailored to
    specific needs
  • Scalable engine is capable of distributing
    processing to an unlimited number of servers
  • Flexible because changes can be made live and
    real time in a WYSIWYG application or through any
    XML editor.

25
How LiveXML Works
MP3
LiveXML
Purpose
Record, edit, playback and distribute high
quality music easily and effectively.
Create, modify, run, integrate and distribute
high quality applications easily and effectively.
File Format (document)
MP3
LiveXML (XML)
Player
Microsoft Media Player
LiveApp Player
Creation Tools
MP3 Studio
LiveIntegrator, LiveModeler or any XML Editor
26
Assemble OnceDeploy Anywhere Simultaneously
Full (Fat) Client
Rich Client
Thin Client
PDAClient
27
Assemble OnceDeploy Anywhere Simultaneously
Rich Clients
28
Integrateand Expose
  • Integrate, Extend and Expose Existing and New
    Systems

LiveModeler Holds the XML MetaData to define a
Virtual Business Object Model (VBOM)
  • Ready To Assemble into real applications
  • End-point agnostic

Direct Data Access
  • No integration server bottleneck

Web Services
Application Servers
Legacy Application Interface
  • Host based to n-tiered can be easily integrated

BEA, IBM, Oracle, LiveApp Player
VB, COBOL, PowerBuilder
BEA, .Net, LiveApp Player
RDBMS, OODBMS
Data Sources, Legacy Applications
Data Sources, Legacy Applications
Data Sources, Legacy Applications
  • Bidirectional capability allows different formats
    to be converted and published real time

29
The Power of the Application Layer
  • LiveXML more than a presentation layer, an
    Application Layer can deliver and process the
    three tiers where needed

Three Tiered Architecture With Application Layer
Three Tiered Architecture
30
The Power of the Application Layer
31
Models and Reuse
  • Raise Reuse to New Heights
  • The application layer is completely assembled

Client Specific Configuration
BRM
BRM
Product Specific Models and Templates Retail
Sales, Partner Settlement, Insurance
Application Layer Assembled XML Documents
Solution Modules Commissions
SRM
Technology Modules Security, Auditing, Allowed
Values
SRM
Virtual Business Model Business Objects and Data
DRM
Productivity Tool LiveIntegrator -- Bridging
the Gap between the Developer and User.
LiveApp Player
TRM
Traditional Code
Existing Applications, Web Services, Legacy
Systems, Third Party Products and Components
TRM
32
White Box Modules
  • White Box Modules are preassembled and can be
    customized
  • GUI
  • Faxing
  • Security
  • Imaging
  • Auditing
  • Memo
  • Email
  • Web Service
  • HTML
  • Transactions
  • Reporting
  • Business Rules
  • Distributed
  • Threshold
  • Events
  • Schedule
  • Integration Virtual Business Object Model
  • Workflow/Process
  • Allowed Values
  • Import Export
  • Task Scheduler
  • Graphical Editing
  • Resource and Document Manager

33
Some Preassembled Solutions
  • Reinsurance Contract Management System
  • All aspects of contract management including
    billing premium and losses, commissions, fees,
    taxes and reporting
  • Insurance Agent Commission System
  • Manages agent hierarchy and type, compensation
    plan and integrates with third party for checks
    and statements
  • Specialty Warranty System
  • Complete paperless office system for a call
    center of 300 processing 300,000 claims per
    month with over 10 million enrollments
  • Retail Commission System
  • Multiple product rollups with territory and
    organizational rollups
  • Web Based Reporting System for Medicare
  • Primary care provided reporting systems
  • Auto Policy Electronic Funds Transfer
  • Customer service and sign up for automatic
    deduction of payments
  • Entertainment Partner Settlement System
  • Complete settlement system including payment,
    auditing and reporting

34
Configuration Utilities
Meaningful Results
Business RelationshipRules
RawData
Data Source
Web Service
White Box Modules
Applications
Client Specific
Business Relationship Rules, Report, Connect,
Collaborate, Resolve
Administrative Interface
Presentation Process, Rules
LiveIntegrator
Data Define/Create Business Objects, Data
Access, Connect and Expose
LiveModeler
Change Management
ConfigurationControl
35
Deployment Architectures
LiveXML Documents can interact with and be served
from any Web server, Web service or XML literate
application server
Applications, are written in XML (runs anywhere
the LiveApp Player is installed)
LiveApp Player is a one time download of 800KB
and LiveXML documents average 20KB
The LiveApp Player is shown where it is able to
run. Only one LiveApp Player is required.
36
Completely Scalable
  • Each module can be distributed
  • New servers and clusters can be added real time
  • Millions of Transactions per Day
  • Unlimited Users
  • 7/24
  • Hundreds of Millions of Records
  • Billions of Dollars Processed

37
Typical Challenges Solved with LiveXML
  • Deliver Robust Sophisticated Applications Over
    The Internet
  • The next generation internet application
  • Provide Easier, Real Time Change and Change
    Management
  • Real time WYSIWYG creation, modification and
    deployment
  • Real time update, no need to bring the system
    down
  • Integrate Disparate Systems and XML Formats
  • Provide Pre-Assembled Solutions and Solution
    Modules

38
LiveXML FeaturesThe Technology Independent
Solution
  • Deliver Robust Sophisticated Applications Over
    The Internet
  • Rich Client LiveXML Player
  • Deliver Simultaneously to Different Platforms and
    Technology
  • Technology Independent LiveXML and LiveXML
    Player
  • Integration of Disparate Systems and Data Sources
  • Virtual Business Object Model (VBOM)
  • Easier, Real Time Change and Change Management
  • Real time WYSIWYG creation, modification and
    deployment
  • Real time update, no need to bring the system
    down
  • Reuse, Sharing and Web Services Integration
  • Application Layer Fully Assembled
  • XML Initiatives, Multiple XML Formats
  • Virtual Business Object Model (VBOM)

39
Additional LiveXML Capabilities
  • Virtual Integration Server
  • Object/Data model from multiple server comes
    together on the client
  • Application Presentation and Business Logic gets
    streamed in from Multiple Systems and comes
    together to form a Single Application on the
    Client
  • General Servers Waiting for a Job
  • Assemble a job or some distributed processing and
    send to any server that has a LiveApp player
    server running
  • Create New Application and Web Services Real Time
  • Upload an LiveXML document to a LiveApp Server
    and instantly it is offering a new Web Service

40
Conclusions

41
The Value
  • Providing a solution today that will make
    available current information that exists in
    disparate systems
  • Provide a solution that can be centrally
    maintained and can grow dynamically
  • Provide a solution that allows for custom views
    of information to maintained and served
    independently
  • Provide a Web Service in a Box an safe, easy
    and secure way to publish data to DHS
  • Provide for the dynamic discovery of new services
    with no extra costs or equipment
  • Provide integration without disruption to
    existing systems

42
Contact Information
  • Robert Schmitter
  • ObjectBuilders
  • 20134 Valley Forge Circle
  • King of Prussia, PA 19406

www.objectbuilders.com 610.783.7748 rschmitter_at_
objectbuilders.com
Write a Comment
User Comments (0)
About PowerShow.com