why is architecture important - · pdf filebusiness architecture roadmap input from strategy...
TRANSCRIPT
Why is ArchitectureWhy is ArchitectureWhy is ArchitectureWhy is ArchitectureImportantImportant
2012/December/052012/December/05
Grid-Interop 2012
Architecture as usually practicedArchitecture as usually practiced
ARCHITECTUREARCHITECTURE OR BUY A VENDOR’S PACKAGEOR BUY A VENDOR’S PACKAGE
(Apologies to Mr Adams and my fellow architects)
There is never enough time (or money) to do it right the first timeThere is never enough time (or money) to do it right the first timeThere is always enough time and money to fix it over and over againThere is always enough time and money to fix it over and over again
--AnonymousAnonymous
There is never enough time (or money) to do it right the first timeThere is never enough time (or money) to do it right the first timeThere is always enough time and money to fix it over and over againThere is always enough time and money to fix it over and over again
--AnonymousAnonymous
Grid-Interop 2012
Siloed Implementation ApproachSiloed Implementation Approach
AMI
FieldAuto
ResDRDER PEVSubSta
AutoServProv
WASACore Utility Automation
SCADA
CISEMS/DMS
Mobile Field Mgt
GIS StateEstimate
Core Utility Automation
SCADA
CISEMS/DMS
Mobile Field Mgt
GIS StateEstimate
ESB
AMI Market
ESB
DR OMS
Grid-Interop 2012
What is (Enterprise) Architecture?What is (Enterprise) Architecture?
• It starts with the idea that one should plan business processes, technology purchases and development ahead of time
• It is not IT, Systems or • It is not IT, Systems or Solution Architecture
and …
• Here's the important part: the business stakeholders, not technology people, should determine what is needed (the goals/requirements)
Architecture provides an Architecture provides an actionable plan to enact actionable plan to enact Smart Grid as seen from the Smart Grid as seen from the stakeholder perspectivestakeholder perspective
Grid-Interop 2012
Why We Need ArchitectureWhy We Need Architecture
First in first out/
Logical – but … ?
Yes, it’s a Kitchen/
Bathroom
ArchitecturalProcess
Input Output
First in first out/Priority of the day
OR
Grid-Interop 2012
ArchitectureArchitectureIt’s much more than technology It’s much more than technology
People
• Businesses specify service requirements and service levels
• Activities maximize re-use across business
• Business and ICT jointly model services
• Governance model for services ( rollout, policies, etc)
Process
• Design process embraces reuse of existing services
• Embrace standards
• Manage life cycle and evolution of services that support business drivers
Technology
• Tools to jointly (Business and ICT) design and capture service models
• Monitor and manage SLAs
• Enforce policies (e.g. Security)
Grid-Interop 2012
Smart Grid Architecture ProducesSmart Grid Architecture Produces
• Strategic Plans • Technical Road Maps• Business processes• Use Cases• Reference Models• Reference Models• Recommended standards• Migration Plans• Change Management• Security and Governance
In short what is required to move from today’s state to the stakeholder’s goal
Grid-Interop 2012
Architecture uses FrameworksArchitecture uses Frameworks
• Including TOGAF*, DoDAF, MoDAF, FEA, Zachman, &c
• They have their own Methodology, Techniques and Toolsand Tools
• Incorporate Lifecycle maps for Project Management (PMO) and Systems Engineering lifecycles (ITIL)
* The Open Group Architecture Framework
Grid-Interop 2012
Use CasesUse CasesBridges the gap between business and technologist - Clarifies how a Smart Grid requirement is envisioned to work and provides the overarching:• Functional requirements• Non-Functional requirements• Interfaces• Interfaces• Sequence• Actors (roles)
They are used and refined throughout the architectural process
Grid-Interop 2012
Services focus on how the Services focus on how the organization worksorganization works
Grid-Interop 2012
Architecture Architecture Service OrientationService OrientationOpen Group DefinitionOpen Group Definition
• Service orientation is a way of thinking in terms of services and service-based development and the outcomes of services
• A service:Is a logical representation of a repeatable business activity that has a specified outcome (e.g., provide weather data, locate fault, dispatch DER)– Is self-contained– May be composed of other services
Process/Service
Input Output
Actor Actor
interfacesSimply put: Simply put: Services are “black boxes”, messages come into them, they work their magic, and resulting message are sent out
– May be composed of other services– Is a “black box” to consumers of the service– An architectural style is the combination of distinctive features in which
architecture is performed or expressed.
(role an actor assumes)
Grid-Interop 2012
Architecture Architecture PhasesPhasesRather then trying to “eat an elephant all at once”, architecture identifies goals and decomposes them into services that ultimately relate to the physical entities
This breaks-down into:•• PreliminaryPreliminary, What do you have & what are
your organization’s drivers•• VisionVision, what goals you trying to achieve•• RequirementsRequirements, what needs do the goals •• RequirementsRequirements, what needs do the goals
impose•• Business ServicesBusiness Services, what abstracted services
are needed to support a requirement•• Information (Information (or Automationor Automation) Services) Services, what
sort of applications and information models are needed to support the abstracted service
•• Technical ServiceTechnical Service, what is actually performing the service
Don’t worry we’ll cover phases E H later
Plus CrossPlus Cross--Cutting Services: Cutting Services: • Security – How information, processes
& infrastructure are protected• Governance – How oversight is executed Grid-Interop 2012
TOGAF Iteration & Architecture layersTOGAF Iteration & Architecture layers
TOGAF cycle and corresponding Artifact level of detail
Contextual
Contextual/VisionContextual/Vision• What are the Goals• What is the current state
ConceptualConceptual• What it shall accomplish• What services are required
ConceptualLogicalPhysical
ConceptualLogicalPhysical
ConceptualLogicalPhysical
• What services are required
LogicalLogical• How it shall be accomplished• How is the architecture structured
PhysicalPhysical• What resources shall be required
Physical
Grid-Interop 2012
TechnicalArchitecture
Automation Architecture
Information Architecture
Business Architecture
Business
Architecture roadmapArchitecture roadmap
Input from strategy &
context
Vision/Contextual
Conc
eptu
alW
hat?
What is the business
What are the info processing
What type of applications
What technical IT services are
Automation Technologies
Contextual Why?
Conc
eptu
alW
hat?
Logi
cal
How
?Ph
ysic
alW
ith
wha
t?
business info processing requirements
applications are required
IT services are required
How is the business structured
How is information structured
How are these systems structured
How are the “boxes” structured
Which parts of the business will change
What manual & automated processes need to be linked
What packages & bespoke software
What Hardware, software & network component
Grid-Interop 2012
Simple Building Architecture ExampleSimple Building Architecture Example
Vision Require-ments
BusinessServices
AutomationServices
TechnicalServices
Process/Service
Input Output
interfacesMagic in this case is the ability to infer the options
Comfort
Green
Budget
mentsWaterHeat/AirLightOutside environSanitary
Energy EffMaterial Reuse
Op CostsInitial CostTimeframe
ServicesHot WaterSourceTreatment
Rebates
Rate Incentive
ServicesSolarGasElectric
ServicesPanelsBatteriesInverter&c
Grid-Interop 2012
Why we need sequenceWhy we need sequence
Sequence ensures the right thing is done in the right order & illuminates alternativesIt’s not as easy as it soundsIt’s not as easy as it sounds
1. Build High Rise Complex
2. Dig drainage canal to prevent flooding
Impact of no sequence
Grid-Interop 2012
The Rest of the StoryThe Rest of the StoryOk, now we understand what it takes to design a
Smart Grid. NowNow we have to implement it, migrate legacy procedures/systems, operate it, handle changes and ensure governance
YikesYikes …. Remember the other YikesYikes …. Remember the other half of the cycle?That’s where those areas are handled
This ensures the architecture stays viable instead of stale Think of this as your “honey-do” list
Grid-Interop 2012
Service OrientationService Orientationshifts the way organizations workshifts the way organizations work
Traditional Service-Oriention
Designed to last Designed to change
Tightly coupled Loosely coupled, agile and adaptive
Siloed and inflexible Composed of business services
Code-oriented (IT-related) Process-oriented
Long development cycles Interactive and iterative cycles
Business unit centered Business initiative centered
Favors homogeneity Favors heterogeneity
Grid-Interop 2012
SOA enables the move from SOA enables the move from maintenance to innovationmaintenance to innovation
IT future stateApplication
Maintenance 15%
IT current state
ApplicationMaintenance
30%
19
ApplicationInnovation
45%
InfrastructureInnovation
10%
InfrastructureMaintenance
30%ApplicationInnovation
23%
InfrastructureInnovation
5%
InfrastructureMaintenance
42%
Source: Client Grid-Interop 2012
ArchitectureArchitecture AsideAside
Executives will never ever use architecture models…
….but they will always need the outputs
Provide what they need in a form they like
Grid-Interop 2012
ArchitectureArchitecture SummarySummary
Enterprise Architecture is a means to:Mitigate risk
Understand how the business operates today and what changes are needed to achieve the business’ Smart Grid objectives/goalsSmart Grid objectives/goals
Gain operational efficiencies
Maximize Capital expenditures
Bring order to IT delivery - aligning Business Services with the underlying IT Services-Oriented (SOA) foundation
Grid-Interop 2012
Questions ?
How does this work?How does this work?
STEPHAN AMSBARYDirector, Utility Enterprise Architecture
[email protected]: +1.828.559.1110
FAX: 865.218.89991993 Grants Mountain Rd, Marion, NC, 28752-9513
Electric Research, Engineering, and Consulting
Grid-Interop 2012
Conceptual ArchitectureConceptual Architecture
Is Critical for Future-Proofing Interoperability!
Grid-Interop 2012
Agenda
• What is Conceptual Architecture• A simple example of Conceptual Architecture• Reasons why you should care• Smart Grid Conceptual Architecture ProjectsSmart Grid Conceptual Architecture Projects• Artifacts
Grid-Interop 2012
• What are we doing• ServicesConceptual
• How are we doing itLogical • How are we doing it• ComponentsLogical
• With what are we doing it• Physical productsPhysical
Grid-Interop 2012
Conceptual Services
• Business• Information• Automation• Technical
Con
cept
ual
Business Function
BusinessActor
Business mission
Information object
Principles Architecture principles
Business principles Information principles
IS principles TI principles Sec principles Gov principles
Architecture assumption
Architecture scope
Architecture constraints
Support products
Business context
Technology context
Business
Business activity
Business
TI Patterns, TI service types,
TI reference models
Architecture objectives
IS Patterns, IS service types,
IS reference models
Bus. Patterns, Bus. service types,
Bus. reference models
Information
Actor Security Requirements
Business Security Domains
IS Service Group Security
Requirements
SEC PatternsSecurity Mechanisms -
Services XRef
Other Support products
Actor Gov Requirements
Business Governance
Domains
IS Service GroupGovernance
Requirements
GOV PatternsGovernance Mechanisms -
Services XRef
GivenPolicies
GOVPolicies
SECPolicies
Info Patterns, Info reference models
Technical• Security• Governance
Org & Gov model
Business process model
Logi
cal
Phy
sica
l
LBC contrac
tLBC interaction
model
Business Implementation
guidelines
Logical information component
Information Implementation
guidelines
IS service
IS serviceContract
IS serviceInteraction
model
LISC
Logical IS interaction
model
Physical IS component
Physical IS component interaction
TIservice
TI serviceContract
TI serviceInteraction
model
LTIC
LTICContrac
tLogical TI interaction
model
Physical TI component interaction
Physical BC interaction
model
Physical IC interaction
model
Physical Information component
TI standard
TI guideline
TI specification
IS standard
IS guideline
IS specification
Logical Business
component
Business Information
service
LICrelation
Business service
Business interaction
model
BusinessService
Collaboration contract
BI service – IS Service xref
IS Service - TI Service xref
LICstructure
model
Information interaction
modelActor / ISSG –
Business Domain Xref
SEC Service
SEC Service Contract
SEC service Interaction
Model
Logical SECComponents
Logical SEC Interaction Model
Physical SEC Component
Physical SEC Component Interaction
SEC standard
SEC guideline
SEC specification
LISCContract
Physical TI component
Actor / ISSG –Business
Domain Xref
GOV Service
GOV Service Contract
GOV service Interaction
Model
Logical GOV Interaction Model
Physical GOV Component
Physical GOV Component Interaction
GOV standard
GOV guideline
GOVspecification
Processes
Procedures
LSC Comp. Contract
LGC Contract
BI serviceCollaborati
on contract
LogicalBIS
component
LBISCinteraction
model
LBISC contrac
t
Logical GOVComponents
Business tasks
Physical Business
component
The whole architecture process Grid-Interop 2012
Simple Example
• Order• Eat• Pay
• What happens when we play with these? • Can we do different things with them?
Grid-Interop 2012
6 Business TypesOrderPay Eat=Fast Food
PayEat=Buffet
EatOrder Pay=Food Tasting Party
Eat=Army Mess or a Soup Kitchen
OrderEatPay=Restaurant
PayOrderEat=Mongolian BBQ
Playing with services can be profitable Grid-Interop 2012
Why do I care?
• Defined points of interoperability• Defined points of communication• Common interface design• Standards for points of interoperabilityStandards for points of interoperability• Simple business re-arrangement
Grid-Interop 2012
The Poker Deck
• Think of services as a large poker deck• Business can deal a “winning” hand from the
deck, knowing that they fit within the industry framework– Their business can be completely unique– Their business can be completely unique– The industry understands by the services chosen
what the interoperability issues are
Grid-Interop 2012
Three Key Industry Projects
• European M490• SGIP Architecture Working Party• China National Grid Architecture Project
Grid-Interop 2012
M490 – Use Case Evaluation Framework
Grid-Interop 2012
SGAC “Deck”
manage unit commitment
manage unit commitment
schedule
topology
forecast
availability
• The deck is based on the universe of Use Cases
• It has been tested in a number of architecture projects
• It continues to evolve• New use cases are being added
to the library The services make deciding
Manager
contract
Each Service has:• A name• A description• Inputs• Outputs • Actors• Traceability to UC
• The services make deciding what interfaces to build much easier
• It makes deciding which standards to accelerate much easier
Grid-Interop 2012
Questions?
• Stephan Amsbary – [email protected]
• Doug Houseman– [email protected]
Thank You!
Grid-Interop 2012