Embed Size (px)
Citation preview
Enabling NCW: Interoperability
and Information Sharing
Vijay Kapur
National Technology Officer,
Microsoft India
Network Centricity
Interoperability
Standards in the IT world
Interoperability @ Microsoft
Case study
Translates an Information Advantage into a decisive Warfighting Advantage
Information Advantage - enabled by the robust networking of well informed geographically dispersed forces
Characterized by:
- Information sharing- Shared situational awareness- Knowledge of commander’s intent
Warfighting Advantage - exploits behavioral change and new doctrine to enable:
- Self-synchronization- Speed of command- Rich Collaboration- Increased combat power
Exploits Order of Magnitude Improvement in Information Sharing
Communities of Interest with different requirements
C4ISR
Services, Support and Info Systems
Knowledge and Intelligence Communities
Increasing expectation of integrated service
Rapidly deliver new capability from existing investments
Integration “hurt” has reached the breaking point:Systems not designed to work together
Interoperability requirement “came later”
Integration is very expensive, time consuming, and rigid.
Joint and Combined operations is today’s reality
Technology ClimateRapid Change
Security and Privacy
Limited Bandwidth
Legacy Applications
Disparate IT and User Skills
Strategic ImperativesNetwork Centric Operations
Internal Security Operations
Asymmetric Warfare
Transformation
Processing
StorageShugart’s Law
Larger storage size
Smaller form factor & cheaper
Moore’s LawFaster
Smaller, lower power & cheaper
Metcalfe’s LawIncreased bandwidth
Cheaper lower bandwidth connections
Interconnection
From a tightly coupled programming model (APIs)
to a loosely coupled programming model (Protocols)
Fundamentally Changing
the Programming Model
Applications
OS
Computers
Processors
Solutions
Storage
Applications
OS
Computers
Processors
Solutions
Storage
Applications
OS
Computers
Processors
Solutions
Storage
Applications
OS
Computers
Processors
Solutions
Storage
Interoperability circa. 1980, vertical solutions = limited interoperability
Storage
EMC, Dell, Network Appliance, HP
Processors
X86-32, X86-64, Sparc, PPC, IA64
Networking Vendors
Cisco, Lucent, Nortel, 3COM, Redback
Systems Vendors
HP, EDS, Fujitsu, IBM, ICL, SNI
Operating Systems & Middleware
Apple, HP, IBM, MS, Sun
Databases
IBM, MS, Oracle
Client Applications
Open Office, Star Office, Microsoft Office
Adobe Creative Suite, Picture IT, AOL,
Symantec Norton, McAfee, Intuit
Turbo Tax, Mozilla, Netscape Opera,
Server Applications
ERP, CRM, Messaging, Management,
Web Serving, Host Integration,…
Multi-Vendor, Horizontal Solutions
Technical
Semantic
Process
Business Process and Organisational
interoperability is about the organising of
business processes and organisational
structures, including process restructuring,
aligning rules and regulations. Also user
specific
Semantic interoperability is concerned with
ensuring consistency in the way in which
information is represented and understood.
User specific; require involvement and
leadership of users.
Technical interoperability relies upon
solutions that enable information to move
successfully between systems. Generally
industry led
• NASA lost the $125 million Mars Climate Orbiter because Lockheed Martin used imperial units whilst NASA used metric.
• After a 286-day journey, the probe fired its engine on September 23 1999 to push itself into orbit.
• The engine fired but the spacecraft came within 60 km of the planet - about 100 km closer than planned and about 25 km beneath thelevel at which the it could function properly.
Mars Climate Orbiter
http://mars.jpl.nasa.gov/msp98/news/mco990930.html
http://edition.cnn.com/TECH/space/9909/30/mars.metric.02/
Technical
Semantic
Organisational
Information
System
Real
World
System
• Data Representation
• Application
• Hardware
• People
• Process
• Information
ResponseRequest
Da
ta &
Div
ers
e
Sys
tem
s
Infrastructure
Applications
Data
Connecting People,Data, and Diverse
Systems
Org
. Stru
ctu
re
Law
Busin
ess P
rocess
People
Slow Change
Rapid
Change
Software fundamentally
different than
physical goods
Translatability
“Physical” metaphors mislead
Translation
Uniformity
Compared
To
Translation
Uniformity
Adapted from - Standards: The Rough Road to t he Common Byte, Martin Libicki, Harvard University
Hard Case
Technology
Matures
Market
Matures
Time
Standardise Here
at this time
Easy Case
Technology
Matures
Market
Matures
Adop
tion
Deliberate delivery of interoperability
in Microsoft products and technologies
Focus on boundary of product
Protocols
Data Formats
APIs
Focus on enablers of interop
Documentation
SDKs / DDKs
Samples
IP As Basis For Collaboration
Commercial Licensing
Community Licensing
Open Specification Promise
Enable Translation
Remove Legal Barriers To Interoperability
Listen to and work with customers, partners, and competitors to
build bridges and coexist
Build business relationships
Partner Programs
Joint Development
X-Licensing Agreements
Community At Large
Industry Roundtables
OSS Development Projects
Feedback Mechanisms
Make Microsoft technology assets available to others
Participate in standards bodies
and support product standards
to foster interoperability
Specifications
Contribute Innovations To Specifications
Work With SIG, Consortia, and De Jure Orgs.
Standardize The Minimum Necessary
Implementations
Support Stds In Products
Deliberate delivery of interoperability
in Microsoft products and technologies
Listen to and work with customers, partners, and competitors to
build bridges and coexist
Make Microsoft technology assets available to others
Participate in standards bodies
and support product standards
to foster interoperability
Services for MacintoshServices for
NetWare
Servicesfor UNIX
SystemsCenter
Meta-directoryServices
ActiveDirectory
SQL
BizTalkExchange
InterixHost
IntegrationServer
Linux, Tru64
Novell NDS, UNIX NIS,
NovellGroupwise,
Smart Phones and PDAs
Informix, DB2, VSAM
PeoplesoftOracle Financials
J.D. EdwardsSiebelSAPAmdahl, Hitachi
3270CICSCobolRPG
DHCP
TCP/IP
XMLDNS
IPX PKI
LDAP
HTTP
Kerberos
Synchronised Air Power
Management
A daily “air tasking order” (ATO) assigns
missions to all military aircraft in an operation.
Detailed mission plans must be developed from
the ATO. This includes schedules, planes, air
crews, weapons, routes, etc.
Detailed planning typically takes 5+ hours after
the ATO is received.
There is a critical need to be able to do
detailed planning faster and to be able to
change the plans quickly to meet new
battlefield conditions.
Oracle
Sun Solaris
(UNIX)Sun Solaris
(UNIX)
Microsoft
Windows
Microsoft
Windows
Microsoft
Windows
TBMCS
Force Level
TBMCS
Unit Level
(Ops)
TBMCS
Unit Level
(Intel)
Mission
Planning
(JMPS)
Air Force
Weather
Oracle Oracle Oracle
BEA WebLogic
(J2EE)
Oracle 9i
And VB
(Microsoft COM)
VB and C++
(Microsoft COM)
VB and C++
(Microsoft COM)
ColdFusion
Theater Battle Management Control System (TBMCS)
Microsoft
TBMCS
Force Level
Sun Solaris
(UNIX)
Oracle
BEA WebLogic
(J2EE)
Microsoft
Windows
TBMCS
Unit Level
(Ops)
Oracle
Oracle 9i
And VB
(Microsoft COM)Microsoft
Windows
TBMCS
Unit Level
(Intel)
Oracle
VB and C++
(Microsoft COM)
Microsoft
Windows
Mission
Planning
(JMPS)
VB and C++
(Microsoft COM)
Microsoft
Sun Solaris
(UNIX)
Air Force
Weather
Oracle
ColdFusion
New Applications
and
Middleware
Information exchange
with XML web services
90 Days…XML Web Services in Action!
Prepare Air
Battle Plan
Publish ATO
Synchronize
TBMCS Force
and Unit Level
Oracle
Database
Prepare
Daily
Schedule
WG CC
Brief
Mission
Data Sheet
Stick Routes
Fly out
package
AAF
Analyze
Threats
Mensurate
Targets
Detailed
Mission
Planning
(Per Mission)
Import threat,
weather,
schedule data
7 56
121110
8 4
21
9 3
7 56
121110
8 4
21
9 3
7 56
121110
8 4
21
9 3
Minutes
Minutes
Minutes
Enabled by
XML Web Services
in only 12 weeks!
120
Minutes today
with SAPM
300+
Minutes
Earlier
20 240+ 2045 30 55
20 45 15 15 10 5
Art of War Decisions
~ ~~ ~
10
Streamlining the process of servicing targets
15
Compress the “Kill Chain” and streamline the process of servicing targets using XML web
services
Quickly drive towards the vision of Interoperability
Leveraged XML Web Services (including .Nettechnologies)
Quickly showed how XML Web Services can affect key metrics, including:
Dramatically reduce mission planning and execution time
Reduce number of humans involved in the process
Allow humans to focus on “art of war” decisions
Open Standards compliance
people
data
Diverse systems
OperationalWorkflows
Processes
Policies
TechnicalApplications
Infrastructure
SemanticInformation
DB/Files
Metadata
Optimizing performance within and
among organisations
Connecting…
Need to build
capabilities...
…based on integrated architectures…
…not silos…
Thank you!
