1. 1
Cora Carmody
Chief Information Officer
Litton PRC
October, 2000
Enterprise Technology;
Architecture and Trends

2. 2
Agenda
 Introduction
 Emerging Technologies and IT Trends
 The Litton PRC Enterprise Architecture
 The Architecture Development Project
Backup material

3. 3
Introduction
What is an architecture and why
do we need one?

4. 4
What is an architecture?
 GartnerGroup defines IT architecture as
the framework and guidelines to be
used to implement any IT system
 An enterprise architecture provides a
path to guide the implementation of
systems toward an established set of
values and principles

5. 5
Why do we need an Enterprise
Architecture?
 Ensure integrability and interoperability
 Support and maintain consistency between IT
and business processes
 Communicate current state and future
direction
 Capture current and evolving customer
requirements and show translation into
solutions
 Guides technology selection, applications
selection and operations

6. 6
Why do we need an Enterprise
Architecture?
 Predict the future
 Allows us a context in which we can judge relative
impact of emerging technologies
 Framework in which we can more easily plan
implementation
 Prioritize expenditures
 Standards allow us to focus investments on those
that will work within existing architecture
 Allow us to select technologies with greatest
business impact
 Control costs
 Standards allow us to leverage volume discounts

7. 7
Additional benefits of following a
standardized Architecture
 The ability to speed up new systems
implementation; many choices have already
been narrowed
 Lower support costs; as the variety of
products is reduced
 Modularity lends flexibility to make future
modifications easily.
 More consistent approach to system
management

8. 8
Emerging Technologies and
IT Trends

9. 9
Radical changes have occurred in
 the number of individuals that can be
reached with information
 in the richness of information content
and format
 in its instantaneousness and currency
 in the ability to respond directly
and in the cost to do all this
Information Hyperflow
What implications does this have on business?

10. 10
The speed, intensity and ease of
access to information is impacting
 The overall speed of business performance
 Initiation of activity to fulfillment is shorter
 The nature of sales and marketing
 Buyer power has increased. Information, choice, options and
convenience has increased, lowering costs
 Internal decision making at lower levels based on
new information access
 The use of external sources
 Whole links in the value chain can now be performed externally
due to intense information flow
 The use of intellectual capital, even more
dispersed
 Leveraging of knowledge through rapid and broad sharing is
increasing performance

11. 11
The Zero Latency Enterprise
 Information Hyperflow can produce a Zero-
Latency Enterprise
 No appreciable time lag between information
introduction and utilization
 Regardless of amount of geographic or organization
distance between entry and utilization points
 Regardless of language or enablement differences
between individual knowledge workers
When supported by appropriate
information technology

12. 12
The Evolution of Computing
Networked Computing
Contextual Computing
Spontaneous Computing
The
advent of G
lobal-Class
com
puting

13. 13
Era Summary

14. 14
Global Class Computing
 Opening up the enterprise to compete in the
networked economy
 Does NOT convey larger scale than enterprise
applications
 Differences are relative to global distribution,
Internet standards, Web protocols, and customer
focus
 Dependent on both network computing
architectures and robust enterprise applications
 Issue of ‘single sign-on’ perpetuates through
need for unique global identity

15. 15
99 Ð 00 Ð 01 Ð 02 Ð 03 Ð 04 Ð 05 Ð 06 Ð 07 Ð 08 Ð 09 Ð 10
Speech dialog,
narrow domain
Agent Interface
common
Handwriting
recognition
common
Gesture recognition
Improved speech
synthesis Improved haptic
feedback
Speech dialog,
general purpose
Anthropomorphic agent
intermediaries
140 million people
on Internet
Gen-WWW
enters workforce
Ubiquitous
smart devices
High-res flat-
screen displays
Embedded process
knowledge
Instant-on devices
Automatic platform
& profile adjustment
Wearable computers
Wireless LAN/WAN
Untethered ops center
Network Computing Contextual Computing Spontaneous Computing
IT Trends
Source; Gartner Group

16. 16
Futuristic Scenarios
 Knowledge is only useful when the worker
has time to work on it
 IT will radically change the way we
 Conduct meetings
 View the physical office
 Obtain administrative assistance
 Spend our commute time
 Conduct international business
 Deal with physical disablement in the workforce

17. 17
The Litton PRC Enterprise
Architecture

18. 18
Workgroup Servers
Workgroup Data
Personal Data
Access Device
User Interface
Enterprise Servers
Enterprise Data Stores
Enterprise Services
Workgroup Services
Workgroup Applications
Knowledge
CoreSupport
Architecture
Work Group
Architecture
User View
Architecture
Process
Enterprise
Architecture
Enterprise Apps
Transport
Network
Devices
Core
Services
Systems
Management
Security
Management
The Architecture

19. 19
Technology Taxonomy
A way to categorize technologies

20. 20
Most Promising Technologies
 We have developed a technology watch
table, which allows us to maintain
visibility of promising technologies
 Each technology is rated 1-4 in 3 areas
 Analysis of the table can give us both
point technologies to watch and
aggressively pursue, as well as
technology areas primetime
zone
impact on
business
cost to
implement
Less than 2 years Major Minor 1
2-5 years 2
5 to 10 years 3
greater than 10 years Minor Major 4

21. 21
Litton PRC
Technology
Watch
List
as of
August
2000
Architecture Technology Technology Type
primetime
zone
impact on
business
cost to
implement
XML Data/Knowledge 1 1 2
text analysis Data/Knowledge 1 2 2
data, analysis, decision support Data/Knowledge 1 1 2
content based retrieval Data/Knowledge 2 1 3
Brilliant content Data/Knowledge 2 3 3
Audio Mining Data/Knowledge 4 3 3
Intelligent Agents Data/Knowledge 1 2 3
speech recognition Input 2 2 2
natural language processing Input 2 3 4
display technologies Output 2 2 3
digital ink Output 3 3 4
handwriting recognition Input 2 2 3
speech synthesis Output 2 3 2
wearables (embedded
miniature computers) Device 4 3 3
Automatic Platform Adjustment Transport/Connectivity 2 1 3
Enterprise Portals Data/Knowledge 1 1 2
Voice Portals Data/Knowledge 2 2 2
Quantum Computing Device 4 3 4
Web tops Data/Knowledge 2 2 3
Linux Device 1 1 1
B2B Electronic Commerce Application 1 1 2
CRMs Application 1 1 3
ASP's Application 1 2 4
Workflow engines Application 1 1 3
Wireless Web (WAP/WML) Transport/Connectivity 2 1 2
DSL/Cable modems Transport/Connectivity 1 2 2
Enterprise Directory/w LDAP Access 2 2 3
Digital Authorization Access 1 2 2
Biometrics Access 2 2 3
Smartcards Access 2 2 2
Voice over IP Transport/Connectivity 1 3 4
Bluetooth Transport/Connectivity 2 1 2

22. 22
Top Ten Technologies
 Linux
 XML
 Data, analysis, decision support
 Enterprise Portals
 B2B Electronic Commerce
 Text analysis
 Customer Relationship Management
 Workflow engines
 Wireless Web (WAP/WML)
 DSL/Cable modems
Subject to change at almost
a moment’s notice

23. 23
The Architectural
Development Project

24. 24
PRC
Architectural
Development
Process

25. 25
ID Task Name
1 IIS Architecture Development
2 Functional Requirements
3 IIS Collection/Review of Existing FR
4 List of Workgroups and Adds
5 List of IIS Advocates
6 Set up Focus Group Reviews
7 Focus Group Validation of FR
8 SA100 - Define System Requirements
9 SA110 - Establish Architecture Framework
10 SA120 - Baseline Existing Architecture
11 SA130 - Analyze, Catagorize, and derive System Requirements
12 SA140 - Identify Issues and Constraints
13 SA150 - Identify Requirements Related to Production and Operations
14 SA200 - Define Design Solution
15 SA210 - Create/Modify Architecture Model
16 SA230 - Select Services
17 SA240 - Define Candidate Architecture
18 SA250 - Select Building Blocks
19 SA260 - Define Interface Requirements
20 SA270 - Additional Requirements
21 SA280 - Requirements Satisfaction
22 SA290 - Business Goal Satisfaction
23 SA300 - Capture Design and Document
24 SA310 - Identify Deliverables
25 SA320 - Establish Document Production Environment
26 SA330 - Establish Mechanism to Capture and Maintain Engineering Notes
27 SA340 - Prepare Requirements Traceablity and Design Documents
28 SA350 - Conduct Internal Technical Review
29 SA360 - Review and Accept Document
30 SA370 - Baseline and Control Architecture Document
31 Total Monthly Seat Cost
32
33 Architecture Review
5/14 5/21 5/28 6/4 6/11 6/18 6/25 7/2 7/9 7/16 7/23 7/30 8/6 8/13 8/20
June July August
Architectural
Development
Schedule

26. 26
Focus Group
Activities
 We have
validated
functional
requirements
through focus
groups based on
work group and
role definitions
 Examples 
Standard Business Workgroup Types
Business Admin
Admin Asst
Business Mgr (Levels)
Line Mgr (Levels)
Proposal
Sales
Inside Sales
Field Sales
Contracts Administration
Order Management
Order Mgr
Project Management
Project Manager
Systems Engineering
DB Design
DB Admin
Analyst
Developer
Systems Admin
Telecommunications
Network Design
Network Admin
Web Design
Web Server Admin
Security Admin
Workflow Admin
Tech Writer
Inventory Control
Production Mgmt
Quality Control
Configuration Mgmt
Helpdesk Support
Field Services
Training
Process Engineering
Technical Transfer and Communications
Corporate Business Workgroup Types
Finance
Tax
Treasury
Internal Audit
DCAA
Cost Accounting
GL Mgr
GL Line
Accounts Payable
AP Mgr
Accounts Receivable
AR Mgr
Billing Mgr
Billing Line
Collections
Procurement
Administrator
Procurement Mgr
Buyer/Catalog Manager
Purch Requisitioner
Human Resources
Staffing
Appraisal
Compensation
Payroll
Benefits
Workforce Development
Legal
Regulatory Affairs
Physical Security
Facilities Mgmt
Real Estate
Mail Room
Shipping and Receiving
Asset Mgmt
Publications
Technical Library
Marketing

27. 27
Summary
 An architecture is not an easy thing to
develop
 There are many many differing definitions of
what constitutes an architecture
 Agreement on one definition and structure is
the best first step towards investment
prioritization and predicting the future!
 And reuse of another enterprise architecture
is a great way to start!