Transcript Service Architecture eme

EME Web Architecture - Initial proposals
Tim Taylor
Mike Capewell
25 August 2000
Agenda


Assumptions
Approach
 dealing with uncertainty
 service architecture
 why use services?




Possible standards
“Straw Man” architecture
Issues
Next Steps
Major Assumptions

There will be 3 main areas to be supported by the EME
web architecture
 “Intranet”
 Extranet
 E-business

provision of information to EME employees
bi directional exchange of information with ESP’s
full integration with selected partners systems,
including financial transactions, eg: e-procurement
Systems architecture requiring integration
 majority of back end
data in Oracle
Wayleaves
CORGOS
SCADA
GIS
NMS
ELIS
PCNAFIRS
CLASS
Verification
Programme
Planning
Asset Values
Expenses
Payroll
PCMS
IBIS
CIS
Asset
Repository
MS-Access
MS-Access
MS-Access
132kV
DataEase
Stock Level
MMIS
Approach - dealing with uncertainty

The current lack of clear business direction leads to
some fundamental requirements for any proposed
architecture, ie: it must be
 scalable, able to support growth in a controlled manner, without
extensive reworking
 flexible, able to support a variety of business models
 adaptable, capable of including new functions without major rework

To achieve these objectives, an architecture based on
Services is proposed
 separating the elements of architecture and defining the
communications required between them

To reduce the risk of costly errors, implementation
should start small
 prove the architecture
 expand delivery on to a proven platform
Approach - service architecture
A service is a
component of the
architecture which
you ask a question
of, and get a
predictable
response.
They have always
been present in
systems.
A service
architecture just
makes them
explicit, and
classifies them
according to their
function.
“Can I change
my dd payment
amount?”
Logon.
s erv Communication
“Sorry, Mr
anon, but your
current balance
of £nn does not
allow this”
Dd payment
must not be <
curbal/12
serv System
Receipt of incoming requests from clients.
Dispatch of requests for external processes.
s erv Presentation
Output of formatted information for
presentation on client (for browser services
likely to be HTML).
serv Business Logic
Application of business rules to data, eg: MIS,
Workflow.
s erv Data Management
select dd
payment &
curbal where
cust = anon
Management of interactions with back end
data sources
Wayleaves
CORGOS
GIS
NMS
SCADA
ELIS
PCNAFIRS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
Asset
Repository
MS-Access
MS-Access
MS-Access
132kV
DataEase
MMIS
System
management
and security.`
Approach - why use services?
Traditional project specific
architecture would
implement most of these
elements independently,
many times.
s erv Communication
serv System
Hardware is dedicated to end
to end processing for systems
Mainframe
Application B
Server
s erv Data Management
Application A
serv Business Logic
Client
s erv Presentation
Changes to one
component requires
changes to others
Integration and
communication between
systems is often only
achievable at the data level
There may be some scope for
reuse, eg: of databases, but
this is often not maximised
Approach - why use services?
Helps ensure that as
many elements of the
architecture as possible
can be reused
s erv Communication
serv System
Hardware can be optimised
for specific tasks for multiple
applications
Web server
s erv Presentation
serv Business Logic
Changes to one
component do not
require changes to
others
Application Server
App A
App B
Integration and
communication between
systems can be achieved
where most appropriate
s erv Data Management
Data Server
Data can be reused by many
applications
Wayleaves
CORGOS
GIS
NMS
SCADA
ELIS
PCNAFIRS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
Asset
Repository
MS-Access
MS-Access
MS-Access
132kV
DataEase
MMIS
If done properly, otherwise - CHAOS!
Possible standards - Communication services

Networking Services






Network Protocols – TCP/IP, IPX/SPX, NetBEUI
Routing Protocols – ARP, ASs, BGP-4, EIGRP, ICMP
Network Topology – Star, Bus, Ring
Addressing
Router Topology
Network Utilisation
s erv Communication
serv System
s erv Presentation
serv Business Logic
s erv Data Management
Wayleaves
CORGOS
GIS
NMS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS

Directory Services (LDAP, X500)






Databases
Partitioning
Replication
Caching
Access Control
Organisation and data relationships
SCADA
ELIS
PCNAFIRS
Asset
Repository
MS-Access
MS-Access
MS-Access
MMIS
132kV
DataEase
PRIORITY
• User groups
• Security
requirements
CONSIDERATIONS
• Powergen corporate
• Shared services
Possible standards - Presentation services

User Interface Design



Consistent User Interface
Human-Computer Interface Standards
Ease of Use
s erv Communication
serv System
s erv Presentation
serv Business Logic
s erv Data Management
Wayleaves
CORGOS
GIS
NMS
SCADA
ELIS
PCNAFIRS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
Asset
Repository
MS-Access
MS-Access
MS-Access
MMIS
132kV
DataEase
• “Style guide”
• not a major priority?
Possible standards - Business Logic services

Application Programming Interfaces (API) and
Development Platform Services







serv System
s erv Presentation
serv Business Logic
s erv Data Management
Wayleaves
CORGOS
GIS
NMS
SCADA
ELIS
PCNAFIRS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
Asset
Repository
MS-Access
MS-Access
MS-Access
MMIS
132kV
DataEase
GroupWare Services




Programming Languages – C/C++, Java
Development Tools & Strategies
Frameworks & Reusability
Threads
Inter-Process Communication
Internationalisation
s erv Communication
E-mail Service
Fax Service
Web Servers
Transaction Services







Transaction Monitoring
Object Technology
Rollover and Rollback
Transactional Roles
ACID
Resource Manager
Transaction Manager
PRIORITY
• Toolsets
• Languages
• Hardware
CONSIDERATIONS
• Existing projects
• Pilots
• Skillsets
Possible standards - Data Management services

Database Services





Data Model
Database Engine
Database Model - Relational, Object-Oriented, etc
Connectivity Interfaces
s erv Communication
serv System
s erv Presentation
serv Business Logic
s erv Data Management
Online Storage Devices and Services
Wayleaves
CORGOS
GIS
NMS




Offline Backup Storage Devices and Services



FDDI
Hardware/Software RAID
Storage Area Networks
Tape Backup
Automated Scheduling Software
Integration with Legacy Systems






Mainframe/Mini Hardware`
Networking/Communication
Transaction Systems (CICS, VSAM, etc)
Database Systems
Legacy Applications
Emulation
SCADA
ELIS
PCNAFIRS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
Asset
Repository
MS-Access
MS-Access
MS-Access
MMIS
132kV
DataEase
PRIORITY
• Information
Architecture
CONSIDERATIONS
• Current data
architecture
• Existing projects
• Pilots
• Skillsets
Possible standards - System services

Security Services





s erv Communication
Manageability versus strength
Inside versus outside the firewall
Cryptography – Public Key Cryptography, Digital Certs
Communications – SSL
Authentication - Kerberos
serv System
s erv Presentation
serv Business Logic
s erv Data Management
Wayleaves
CORGOS
GIS
NMS

Environment, Distributed Objects, Component Models








Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
Asset
Repository
MS-Access
MS-Access
MS-Access
MMIS
132kV
DataEase
PRIORITY
• Security services
• Firewall
• Middleware
• Basic systems
management
Management and Maintenance Services




Concepts - Components, Objected Oriented
Object Middleware - COM/DCOM, CORBA, EJB
Operating Systems - Windows, UNIX, Linux, Solaris
Web Server
Performance - Local, Network, Load Balancing, Clustering
Robustness , Resilience, Scalability
Failover & Recovery, Disaster Recovery
SCADA
ELIS
PCNAFIRS
Remote Management Services, Fault Alerts
Self Healing Mechanisms
Asset Management, Configuration Management
Device Sharing Services and Integration

Integration with external devices
CONSIDERATIONS
• Current systems
• Existing projects
• Shared services
Straw Man architecture - initial configuration
Hardware
s erv Communication
serv System
Web Server
Software
Components
• 1 x Web Server
• 1 x app/db server
• Cost: £5k - £10k
Components
• development toolkit
• Cost: £5k-10k
Options
• SUN
• HP
• IBM
Options
• integrated, eg: Oracle
Internet Application
Server (IAS)
• Components, eg:
WebLogic, iPlanet
Application Server,
and WebSphere 3.5
s erv Presentation
serv Business Logic
Application
& data Server
s erv Data Management
Wayleaves
CORGOS
SCADA
GIS
NMS
ELIS
PCNAFIRS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
MMIS
Asset
Repository
MS-Access
MS-Access
MS-Access
132kV
DataEase
Total Cost: approx £10k - £20k
Straw Man architecture - mid size
Hardware
s erv Communication
serv System
Web Server
s erv Presentation
serv Business Logic
Application
& data Server
s erv Data Management
Wayleaves
CORGOS
Software
Components
• approx. £20k per
processor required
• 1 x Web Server (1)
• 1 x app/db server (2)
• Cost: £50k - £100k
Components
• development toolkit
• system management
tools
• middleware
• Cost: £25k-50k
Options
• SUN
• HP
• IBM
Options
• integrated, eg: Oracle
Internet Application
Server (IAS)
• Components, eg:
WebLogic, iPlanet
Application Server,
and WebSphere 3.5
SCADA
GIS
NMS
ELIS
PCNAFIRS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
MMIS
Asset
Repository
MS-Access
MS-Access
MS-Access
132kV
DataEase
Total Cost: approx £75k - £150k
Straw Man architecture - ‘full strength’
Hardware
s erv Communication
serv System
Web Server
s erv Presentation
serv Business Logic
Application Server
s erv Data Management
Data Server
Wayleaves
CORGOS
Components
• approx. £20k per
processor required
• n x Web Server
• n x app server
• n x db server
• Cost: £100k - £200k
Options
• SUN
• HP
• IBM
Software
Components
• development toolkit
• system management
tools
• middleware
• Cost: £50k-100k
Options
• integrated, eg: Oracle
Internet Application
Server (IAS)
• Components, eg:
WebLogic, iPlanet
Application Server,
and WebSphere 3.5
SCADA
GIS
NMS
ELIS
PCNAFIRS
Programme
Planning
CLASS
Payroll
PCMS
IBIS
CIS
MMIS
Asset
Repository
MS-Access
MS-Access
MS-Access
132kV
DataEase
Typical Cost: approx £150k - £300k
Example of a ‘full-strength’ architecture
AT
Guest
Connection via
Internet
M
-H
ot
el
Lin
k
Database Servers
Oracle 8.x
UNIX
Processors: 8
Mem: 16 GB
Disk: 20GB x 3 (RAID)
UNIX
Processors: 8
Mem: 16GB
Disk: 20GB x 3 (RAID)
Site Load Balancing
Replication
Database Server
Oracle 8.x
UNIX
Processors: 8
Mem: 16GB
Disk: 20GB x 3 (RAID)
DNS/Web Server
Netscape (iPlanet)
Web Server 4.0
Enterprise Edition
Windows NT 4.0
Processors: 8
Mem: 4GB
Disk: 20GB x 3 (RAID)
Cisco
Local Director
Cisco 4700M
Distributed Director
Firewall
CheckPoint Firewall
Backup Server
Veritas Netback 3.2
Windows NT 4.0
Processors: 8
Mem: 2GB
Disk:9.1GB
Windows NT 4.0
Processor: 4
Mem: 2GB
Disk: 9.1GB
Tape Silo
100 Base/T
Sun Enterprise 450
UNIX
Processors: 8
Mem: 16GB
Disk: 20GB x 3 (RAID)
OS:
Processors:
Mem:
Disk:
Payment Server
UNIX
Processors: 8
Mem: 16GB
Disk: 20GB x 3 (RAID)
Windows NT 4.0
Processors: 8
Mem: 1GB
Disk: 20GB x 3 (RAID)
Fax/E-mail Server
Microsoft Exchange
Server 5.5 with Fax
Connector
OS: Sun OS 2.5
Processors: 1
Mem: 1GB
Disk: 9.1GB
Monitoring
Tivoli
IBM Workgroup Server
43P Model 260
OS: IBM AIX 4.3
Processors: 1
Mem: 512MB
Disk:9.1GB x 2
GDS Servers
NetBackup Client (3.1.1)
Application Servers
Oracle Application
Server 4.0.8
Example of Web-Based Hotel Central Reservation & Property
Management System
Central - Network Architecture
Issues

Complexity of web architecture - if poorly implemented
will make the current situation look like a picnic!





multiple components
complex interactions
process driven
open to outside scrutiny
Needs to be integrated with other architectures
 information (what data is being used)
 functional (which business functions are being transacted)
 business (needs to be process driven)




Relationship with PowerGen initiatives and architecture
Hosting / ASP
Uncertain business model (plans, priorities etc)
Business ownership and buy in
Next Steps - framework
1
Learning
Gaining understanding of the e-business marketplace
2
Planning
Determining your e-commerce strategy
3
System
Evaluating your current system software
Network
5 Security
4
Evaluating your internal and external network infrastructure
Adding security to your web site, intranet and extranet
6
Payment
How you will be paid, and how you will pay suppliers
7
Buying
Purchasing from suppliers over the internet
8
Supplier
Linking into a centralised suppliers catalogue for purchasing
9
Logistics
Using the internet to manage stock levels and deliver goods
10 Selling
Creation of selling and affiliation tools for your web site
11 Customer
Creating a community of customers through your web site
12 Personalisation
Creating electronic relationships
What are we currently addressing?
1
Learning
Gaining understanding of the e-business marketplace
2
Planning
Determining your e-commerce strategy
3
Evaluating your current system software
4
4
5
5
System
Network
Security
Security
6
Payment
How you will be paid, and how you will pay suppliers
7
Buying
Purchasing from suppliers over the internet
8
Supplier
Linking into a centralised suppliers catalogue for purchasing
9
Logistics
Using the internet to manage stock levels and deliver goods
Evaluating your
your internal
internal and
and external
external network
network infrastructure
infrastructure
Evaluating
Adding security
security to
to your
your web
web site,
site, intranet
intranet and
and extranet
extranet
Adding
10 Selling
Creation of selling and affiliation tools for your web site
11 Customer
Creating a community of customers through your web site
12 Personalisation
Creating electronic relationships
Next Steps

Connect with the business
 what is the e-business strategy?
 what current developments are happening in this area?
 SELL, SELL, SELL
• the e-business framework
• why they need an architectural approach


Understand PowerGen Shared Services standards and
architecture
Tie in with current architecture work
 provide focus for detailed investigation
 include in plan (update to follow)
 include in model