Actions

Difference between revisions of "Gartner's PACE Layered Application Strategy"

(PACE Layered Application Strategy is a methodology to govern software applications through their entire life-cycle in support of evolving business requirements.Pace layered approach has been developed by the advisory firm Gartner.)
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
== PACE Layered Application Strategy Definition ==
 +
'''PACE Layered Application Strategy''' is a [[methodology]] to govern [[Application Lifecycle Management (ALM)|software applications through their entire life-cycle]] in support of evolving [[Business Requirements|business requirements]]. Pace layered approach has been developed by the advisory firm Gartner.
  
===PACE Layered Application Strategy Definition===
 
PACE Layered Application Strategy is a methodology to govern software applications through their entire life-cycle in support of evolving business requirements.Pace layered approach has been developed by the advisory firm Gartner.
 
  
 
'''Gartner Pace layered application strategy'''<br/>
 
'''Gartner Pace layered application strategy'''<br/>
 
[[File:GartnerPaceLayered.png|400px|Gartner Pace layered application strategy]]<br />
 
[[File:GartnerPaceLayered.png|400px|Gartner Pace layered application strategy]]<br />
 +
 +
 +
__TOC__
  
  
 
Pace Layered thinking has four salient features:
 
Pace Layered thinking has four salient features:
*Governance Framework: The focus is on better IT decisions - higher business value at a lower cost, and risk
+
*[[IT Governance Framework|Governance Framework]]: The focus is on better IT decisions - higher [[Business Value|business value]] at a lower cost, and [[risk]]
 
*Application Life Cycle: These decisions are along the entire application lifecycle - identify, select, fund, build, deploy, operate, and sunset
 
*Application Life Cycle: These decisions are along the entire application lifecycle - identify, select, fund, build, deploy, operate, and sunset
*Application Portfolio: The decisions are common across a group of applications...
+
*[[Application Portfolio Management (APM)|Application Portfolio]]: The decisions are common across a group of applications...
*Application Layers: ...that fit into a category or "layer" which contains applications with similar characteristics requiring similar governance approach
+
*Application Layers: ...that fit into a category or "layer" which contains applications with similar characteristics requiring similar [[governance]] approach
*Evolving Business Requirements: The objective is to adapt the application portfolio driven by changing business needs for maximum business value  
+
*[[Business Requirements|Evolving Business Requirements]]: The [[objective]] is to adapt the [[Application|application]] [[Portfolio|portfolio]] driven by changing [[Business Requirements|business needs]] for maximum business value  
  
Pace layer thinking takes a more granular approach to business applications in a portfolio - does this application support a common requirement, a unique business methodology or an innovative new business process? This allows the organization to apply the appropriate governance, funding and data models, based on the characteristics of each application.
+
Pace layer thinking takes a more granular approach to [[Application Portfolio Management (APM)|business applications in a portfolio]] - does this application support a common requirement, a [[Methodology|unique business methodology]] or an [[Business Process|innovative new business process]]? This allows the [[organization]] to apply the [[Governance|appropriate governance]], funding and [[Data Model|data models]], based on the characteristics of each application.
  
Pace layers force the categorization of applications by process or function rather than the more common cross-process package (ERP, CRM etc.) classification used in the enterprise. For example, financial accounting, order entry and collaborative demand planning are often part of a single ERP package, but are separate application modules that belong in three different layers in the Pace-Layered Application Strategy. <ref>Understanding Gartner's PACE Layered Application Strategy [https://www.gartner.com/doc/1890915/accelerating-innovation-adopting-pacelayered-application Gartner]</ref>
+
Pace layers force the categorization of applications by [[process]] or function rather than the more common cross-process package ([[Enterprise Resource Planning (ERP)|ERP]], [[Customer Relationship Management (CRM)|CRM]] etc.) classification used in the enterprise. For example, financial [[accounting]], order entry and collaborative [[demand]] planning are often part of a single ERP package, but are separate application modules that belong in three different layers in the Pace-Layered Application Strategy. <ref>Understanding Gartner's PACE Layered Application Strategy [https://www.gartner.com/doc/1890915/accelerating-innovation-adopting-pacelayered-application Gartner]</ref>
  
  
Line 24: Line 27:
  
 
====Gartner defines pace layered approach as follows:====
 
====Gartner defines pace layered approach as follows:====
Gartner’s Pace-Layered Application Strategy is a methodology for categorizing, selecting, managing and governing applications to support business change, differentiation and innovation.<ref>Definition - What is Gartner's Pace Layered Application Strategy [http://www.gartner.com/it-glossary/pace-layered-application-strategy/ Gartner]</ref>
+
Gartner’s Pace-Layered Application Strategy is a methodology for categorizing, selecting, managing and governing applications to [[Change Management|support business change]], differentiation and [[Innovation|innovation]].<ref>Definition - What is Gartner's Pace Layered Application Strategy [http://www.gartner.com/it-glossary/pace-layered-application-strategy/ Gartner]</ref>
  
  
 
===Application Layers===
 
===Application Layers===
Gartner postulates that there are different layers of software applications in an organization. Each layer contains applications with common characteristics related to the speed of adaptation, and change. Therefore, governance requirements are different between layers but applications in each layer can be governed similarly.  
+
Gartner postulates that there are different layers of [[software]] applications in an organization. Each layer contains applications with common characteristics related to the speed of adaptation, and change. Therefore, governance requirements are different between layers but applications in each layer can be governed similarly.  
  
 
Gartner has defined three application categories, or "layers," to distinguish application types and help organizations develop more appropriate strategies for each:<ref>The Three Layers of application types [http://www.gartner.com/newsroom/id/1923014 Gartner]</ref>
 
Gartner has defined three application categories, or "layers," to distinguish application types and help organizations develop more appropriate strategies for each:<ref>The Three Layers of application types [http://www.gartner.com/newsroom/id/1923014 Gartner]</ref>
  
*Systems of Record — Established packaged applications or legacy homegrown systems that support core transaction processing and manage the organization's critical master data. The rate of change is low, because the processes are well-established and common to most organizations, and often are subject to regulatory requirements.
+
*Systems of Record — Established packaged applications or [[Legacy Systems|legacy homegrown systems]] that support core transaction processing and manage the [[Master Data|organization's critical master data]]. The rate of change is low, because the processes are well-established and common to most organizations, and often are subject to [[Compliance|regulatory requirements]].
*Systems of Differentiation — Applications that enable unique company processes or industry-specific capabilities. They have a medium life cycle (one to three years), but need to be reconfigured frequently to accommodate changing business practices or customer requirements.
+
*Systems of Differentiation — Applications that enable unique company processes or [[Business Capability|industry-specific capabilities]]. They have a medium life cycle (one to three years), but need to be reconfigured frequently to accommodate changing business practices or [[customer]] requirements.
*Systems of Innovation — New applications that are built on an ad hoc basis to address new business requirements or opportunities. These are typically short life cycle projects (zero to 12 months) using departmental or outside resources and consumer-grade technologies.
+
*Systems of [[Innovation]] — New applications that are built on an ad hoc basis to address new business requirements or opportunities. These are typically [[Project Life Cycle|short life cycle projects]] (zero to 12 months) using departmental or outside resources and consumer-grade technologies.
  
  
 
===Business Innovation===
 
===Business Innovation===
Gartner claims that adopting a Pace-Layered Application Strategy can build a business application strategy that accelerates innovation - faster response, and better ROI, without sacrificing integration, integrity and/or governance.
+
Gartner claims that adopting a Pace-Layered Application Strategy can build a business application strategy that accelerates [[Innovation|innovation]] - faster response, and [[Return on Investment (ROI)|better ROI]], without sacrificing integration, integrity and/or governance.
  
  
 
===Pace Layering, and Shearing Layers===
 
===Pace Layering, and Shearing Layers===
Pace layering is a concept built upon the [shearing-layers|shearing layers] concept coined by architect Frank Duffy, and elaborated by Stewart Brand in his book, How Buildings Learn: What Happens After They’re Built (Brand, 1994).
+
Pace layering is a concept built upon the [[Shearing Layers|shearing layers]] concept coined by architect Frank Duffy, and elaborated by Stewart [[Brand]] in his book, How Buildings Learn: What Happens After They’re Built (Brand, 1994).
  
  
Line 56: Line 59:
  
 
===See Also===
 
===See Also===
 +
== See Also ==
 +
[[Gartner]]<br />
 +
[[Gartner's Hype Cycle Methodology]]<br />
 +
[[Gartner Business Value Model]]<br />
 +
[[Gartner Magic Quadrant]]<br />
 +
[[Gartner's MarketScopes]]<br />
 +
[[Gartner Vendor Rating]]<br />
 +
[[Gartner Market Forecast]]<br />
 +
[[Gartner's Market Share Analysis]]<br />
 
[[Application_Portfolio_Management_(APM)|Application Portfolio Management (APM)]]<br />
 
[[Application_Portfolio_Management_(APM)|Application Portfolio Management (APM)]]<br />
 
[[Project_Portfolio_Management_(PPM)|Project Portfolio Management (PPM)]]<br />
 
[[Project_Portfolio_Management_(PPM)|Project Portfolio Management (PPM)]]<br />
 
[[Application_Lifecycle_Management_(ALM)|Application Lifecycle Management (ALM)]]<br />
 
[[Application_Lifecycle_Management_(ALM)|Application Lifecycle Management (ALM)]]<br />
[[IT_Governance|IT Governance]]
+
[[IT_Governance|IT Governance]]<br />
 +
[[Enterprise Architecture]]<br />
 +
[[Enterprise Architecture Framework]]<br />
 +
[[Enterprise Architecture Governance]]<br />
 +
[[Enterprise Architecture Life Cycle (EALC)]]<br />
 +
[[IT Governance Framework]]<br />
 +
[[IT Strategy (Information Technology Strategy)]]<br />
 +
[[IT Strategy Framework]]<br />
 +
[[Application Layer]]<br />
 +
[[Application Lifecycle Framework]]<br />
 +
[[Application Integration]]
  
  

Revision as of 17:35, 1 March 2021

PACE Layered Application Strategy Definition

PACE Layered Application Strategy is a methodology to govern software applications through their entire life-cycle in support of evolving business requirements. Pace layered approach has been developed by the advisory firm Gartner.


Gartner Pace layered application strategy
Gartner Pace layered application strategy



Pace Layered thinking has four salient features:

Pace layer thinking takes a more granular approach to business applications in a portfolio - does this application support a common requirement, a unique business methodology or an innovative new business process? This allows the organization to apply the appropriate governance, funding and data models, based on the characteristics of each application.

Pace layers force the categorization of applications by process or function rather than the more common cross-process package (ERP, CRM etc.) classification used in the enterprise. For example, financial accounting, order entry and collaborative demand planning are often part of a single ERP package, but are separate application modules that belong in three different layers in the Pace-Layered Application Strategy. [1]


Gartner Pace layered application strategy Innovation
source: Gartner


Gartner defines pace layered approach as follows:

Gartner’s Pace-Layered Application Strategy is a methodology for categorizing, selecting, managing and governing applications to support business change, differentiation and innovation.[2]


Application Layers

Gartner postulates that there are different layers of software applications in an organization. Each layer contains applications with common characteristics related to the speed of adaptation, and change. Therefore, governance requirements are different between layers but applications in each layer can be governed similarly.

Gartner has defined three application categories, or "layers," to distinguish application types and help organizations develop more appropriate strategies for each:[3]

  • Systems of Record — Established packaged applications or legacy homegrown systems that support core transaction processing and manage the organization's critical master data. The rate of change is low, because the processes are well-established and common to most organizations, and often are subject to regulatory requirements.
  • Systems of Differentiation — Applications that enable unique company processes or industry-specific capabilities. They have a medium life cycle (one to three years), but need to be reconfigured frequently to accommodate changing business practices or customer requirements.
  • Systems of Innovation — New applications that are built on an ad hoc basis to address new business requirements or opportunities. These are typically short life cycle projects (zero to 12 months) using departmental or outside resources and consumer-grade technologies.


Business Innovation

Gartner claims that adopting a Pace-Layered Application Strategy can build a business application strategy that accelerates innovation - faster response, and better ROI, without sacrificing integration, integrity and/or governance.


Pace Layering, and Shearing Layers

Pace layering is a concept built upon the shearing layers concept coined by architect Frank Duffy, and elaborated by Stewart Brand in his book, How Buildings Learn: What Happens After They’re Built (Brand, 1994).


Pace Governance

Gartner Pace Approach Governance View
Source: Data Chatter Box


Pace Layered Architecture

Pace layered applications
Source: Data Chatter Box


See Also

See Also

Gartner
Gartner's Hype Cycle Methodology
Gartner Business Value Model
Gartner Magic Quadrant
Gartner's MarketScopes
Gartner Vendor Rating
Gartner Market Forecast
Gartner's Market Share Analysis
Application Portfolio Management (APM)
Project Portfolio Management (PPM)
Application Lifecycle Management (ALM)
IT Governance
Enterprise Architecture
Enterprise Architecture Framework
Enterprise Architecture Governance
Enterprise Architecture Life Cycle (EALC)
IT Governance Framework
IT Strategy (Information Technology Strategy)
IT Strategy Framework
Application Layer
Application Lifecycle Framework
Application Integration


References

  1. Understanding Gartner's PACE Layered Application Strategy Gartner
  2. Definition - What is Gartner's Pace Layered Application Strategy Gartner
  3. The Three Layers of application types Gartner


Further Reading

  • Enable a Pace-Layered Approach to Business Technology Progress
  • Pace-Layered Application Strategies, Fact or Fiction? Adrian Bridgwater
  • Applying Pace Layering to ERP Strategy Nigel Rayner