kipdf.com
Open in
urlscan Pro
2a06:98c1:3121::3
Public Scan
Submitted URL: http://kipdf.com/reference-architecture-implementation-guide-ceb-enterprise-architecture-leadersh_5ab660711723dd3...
Effective URL: https://kipdf.com/reference-architecture-implementation-guide-ceb-enterprise-architecture-leadersh_5ab660711723dd3...
Submission: On May 29 via manual from US — Scanned from NL
Effective URL: https://kipdf.com/reference-architecture-implementation-guide-ceb-enterprise-architecture-leadersh_5ab660711723dd3...
Submission: On May 29 via manual from US — Scanned from NL
Form analysis
4 forms found in the DOMGET https://kipdf.com/search
<form method="GET" target="_top" action="https://kipdf.com/search">
<div class="form-group">
<div class="input-group">
<input type="text" class="form-control ui-autocomplete-input" name="s" id="document_search" placeholder="Search Documents" autocomplete="off">
<div class="input-group-btn">
<button type="submit" class="btn btn-default"><i class="fa fa-search"></i></button>
</div>
</div>
</div>
</form>
GET https://kipdf.com/search
<form method="GET" target="_top" action="https://kipdf.com/search">
<div class="form-group">
<div class="input-group input-group-lg">
<input type="text" class="form-control" name="s" id="document_search" placeholder="Search Documents">
<div class="input-group-btn">
<button type="submit" class="btn btn-default"><i class="fa fa-search"></i></button>
</div>
</div>
</div>
</form>
POST https://kipdf.com/report/5ab660711723dd339c813cf1
<form role="form" method="post" action="https://kipdf.com/report/5ab660711723dd339c813cf1" style="border: none;">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
<h4 class="modal-title">Report "Reference Architecture Implementation Guide. CEB Enterprise Architecture Leadership Council"</h4>
</div>
<div class="modal-body">
<div class="form-group">
<label>Your name</label>
<input type="text" name="name" required="required" class="form-control">
</div>
<div class="form-group">
<label>Email</label>
<input type="email" name="email" required="required" class="form-control">
</div>
<div class="form-group">
<label>Reason</label>
<select name="reason" required="required" class="form-control">
<option value="">-Select Reason-</option>
<option value="pornographic" selected="selected">Pornographic</option>
<option value="defamatory">Defamatory</option>
<option value="illegal">Illegal/Unlawful</option>
<option value="spam">Spam</option>
<option value="others">Other Terms Of Service Violation</option>
<option value="copyright">File a copyright complaint</option>
</select>
</div>
<div class="form-group">
<label>Description</label>
<textarea name="description" required="required" rows="3" class="form-control" style="border: 1px solid #cccccc;"></textarea>
</div>
<div class="form-group">
<div style="display: inline-block;">
<div class="g-recaptcha" data-sitekey="6LeFAE0UAAAAAHbTtXbsdmgbOoiM_Tt6w-zBZHm6">
<div style="width: 304px; height: 78px;">
<div><iframe title="reCAPTCHA"
src="https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LeFAE0UAAAAAHbTtXbsdmgbOoiM_Tt6w-zBZHm6&co=aHR0cHM6Ly9raXBkZi5jb206NDQz&hl=nl&v=CDFvp7CXAHw7k3HxO47Gm1O9&size=normal&cb=vc9oklv7zgbp" width="304"
height="78" role="presentation" name="a-p0d2b64qxdbo" frameborder="0" scrolling="no" sandbox="allow-forms allow-popups allow-same-origin allow-scripts allow-top-navigation allow-modals allow-popups-to-escape-sandbox"></iframe></div>
<textarea id="g-recaptcha-response" name="g-recaptcha-response" class="g-recaptcha-response"
style="width: 250px; height: 40px; border: 1px solid rgb(193, 193, 193); margin: 10px 25px; padding: 0px; resize: none; display: none;"></textarea>
</div><iframe style="display: none;"></iframe>
</div>
</div>
</div>
<script src="https://www.google.com/recaptcha/api.js"></script>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
<button type="submit" class="btn btn-primary">Save changes</button>
</div>
</form>
POST https://kipdf.com/login
<form action="https://kipdf.com/login" method="post">
<div class="form-group">
<label class="sr-only" for="email">Email</label>
<input class="form-input form-control" type="text" name="email" id="email" value="" placeholder="Email">
</div>
<div class="form-group">
<label class="sr-only" for="password">Password</label>
<input class="form-input form-control" type="password" name="password" id="password" value="" placeholder="Password">
</div>
<div class="form-group">
<div class="checkbox">
<label class="form-checkbox">
<input type="checkbox" name="remember" value="1">
<i class="form-icon"></i> Remember me </label>
<label class="pull-right"><a href="https://kipdf.com/forgot">Forgot password?</a></label>
</div>
</div>
<button class="btn btn-primary btn-block" type="submit">Sign In</button>
</form>
Text Content
* Home * Add Document * Sign In * Create An Account REFERENCE ARCHITECTURE IMPLEMENTATION GUIDE. CEB ENTERPRISE ARCHITECTURE LEADERSHIP COUNCIL Reference Architecture Implementation Guide CEB Enterprise Architecture Leadership Council A Framework for Member Conversations The mission of CEB... -------------------------------------------------------------------------------- Author: Arline Greene 24 downloads 1 Views 576KB Size Report Download PDF RECOMMEND DOCUMENTS DoD Enterprise Architecture Technical Reference Model -------------------------------------------------------------------------------- Organizing HR to Lead Enterprise Change. CEB Corporate Leadership Council -------------------------------------------------------------------------------- REFERENCE ARCHITECTURE -------------------------------------------------------------------------------- Enterprise Architecture in Enterprise Engineering -------------------------------------------------------------------------------- An Enterprise Information System Data Architecture Guide -------------------------------------------------------------------------------- ENTERPRISE ARCHITECTURE CONSULTANCY -------------------------------------------------------------------------------- Enterprise Architecture as Inventory -------------------------------------------------------------------------------- Enterprise Architecture Management Tools -------------------------------------------------------------------------------- Journal of Enterprise Architecture -------------------------------------------------------------------------------- Enterprise Applications Architecture -------------------------------------------------------------------------------- 10 Valuing Enterprise Architecture -------------------------------------------------------------------------------- Leichtgewichtige Enterprise Architecture -------------------------------------------------------------------------------- Visual Enterprise Architecture Planning -------------------------------------------------------------------------------- Government Enterprise Architecture -------------------------------------------------------------------------------- Journal of Enterprise Architecture -------------------------------------------------------------------------------- Journal of Enterprise Architecture -------------------------------------------------------------------------------- Attendance Enterprise Architecture -------------------------------------------------------------------------------- Effective Enterprise Architecture Management -------------------------------------------------------------------------------- Enterprise Architecture Principles -------------------------------------------------------------------------------- OpenShift Enterprise 3.1 Architecture -------------------------------------------------------------------------------- Enterprise Architecture. An Overview -------------------------------------------------------------------------------- SOA REFERENCE ARCHITECTURE BLUEPRINT -------------------------------------------------------------------------------- Open Cloud Reference Architecture -------------------------------------------------------------------------------- Epiphany Architecture Reference -------------------------------------------------------------------------------- Reference Architecture Implementation Guide CEB Enterprise Architecture Leadership Council A Framework for Member Conversations The mission of CEB Inc. and its affiliates is to unlock the potential of organizations and leaders by advancing the science and practice of management. When we bring leaders together, it is crucial that our discussions neither restrict competition nor improperly share inside information. All other conversations are welcomed and encouraged. Confidentiality and Intellectual Property These materials have been prepared by CEB Inc. for the exclusive and individual use of our member companies. These materials contain valuable confidential and proprietary information belonging to CEB, and they may not be shared with any third party (including independent contractors and consultants) without the prior approval of CEB. CEB retains any and all intellectual property rights in these materials and requires retention of the copyright mark on all pages reproduced. Legal Caveat CEB Inc. is not able to guarantee the accuracy of the information or analysis contained in these materials. Furthermore, CEB is not engaged in rendering legal, accounting, or any other professional services. CEB specifically disclaims liability for any damages, claims, or losses that may arise from a) any errors or omissions in these materials, whether caused by CEB or its sources, or b) reliance upon any recommendation made by CEB. INTRODUCTION Enterprise Architecture (EA) groups recognize the potential benefits of reference architecture (RA). Council polling results reveal that 72% of members consider an RA extremely or very important to EA’s success—but few have been able to realize reference architecture’s full potential. Fewer than 10% of EA groups rate themselves as mature in this area. Leading EA groups manage reference architectures as a program by establishing the processes to define, deliver, and manage them through their full lifecycle. To help member organizations better manage their reference architectures, the Council has collected artifacts from each stage of the lifecycle and highlighted the key takeaways: 1. Initiating: Ensure that all stakeholders define reference architecture consistently, promote the associated benefits, and tailor stakeholder communications. 2. Building: Provide reference implementations that tangibly support solutions delivery teams and develop an RA portfolio to ensure focus on high priority areas. 3. Deploying: Promote adoption by focusing on the customer experience, providing easy access to resources and collaboration opportunities, and sharing ownership with subject matter experts. 4. Governing: Fast-track governance for solutions teams using reference architectures and lease RAs to ensure alignment with current standards. 5. Maintaining: Incorporate RAs into technology roadmaps and build in event-based triggers to better anticipate and respond to change. For more information, visit our Reference Architecture topic center on our website: cebglobal.com/architecture. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 3 ■■ Savings from a Single RA Compared to an RA Programa Five Year Time-Horizon A single RA covering 5% of the portfolio reduces the IT budget by 2%. 0.4– 1.9% 100% Maintenance cost reductions, which constitute approximately two-thirds of the savings, mount as the RA portfolio grows and the practice matures. ■■ ■■ Technology procurement FTE costs for creation and maintenance 1.2– 4.4% ■■ ■■ Prescriptive patterns and reuse Reduced solutionsdelivery time 0.34– 1.8% ■■ 0.15– 5.4% Standardization of infrastructure ■■ ■■ Efficient Solutions Delivery See our Reference Architecture Cost Savings Estimation Model to customize to your organization. S M Ap av ai pl in nt ic gs en at in an ion ce In S f In ras avi ve tr ng st uc s m tu in en re ts D Ap Sav ev p in el lic g op a s m tio in en n t D C ev os el t op of m RA en t Ex A pe nn n ua Pr dit l IT e- ur R e A ■■ Reduction in number of trouble tickets Reduced mean time to repair Standardization of supporting infrastructure 0.45– 6.8% ■■ ■■ ■■ 83– 98% Standardization of infrastructure Reduction in number of trouble tickets Reduced mean time to repair R Ex ed pe uc Po nd ed st itu IT -R re A ■■ ECONOMIC MODEL FOR AN RA IMPLEMENTATION In S M fras av ai tr in nt u gs en ct in an ure ce A successfully run RA program can deliver annual savings equivalent to 17% of the IT budget. Simplified IT Operations Source: American Express Company; Footloose, Inc. (pseudonym); CEB 2011 Budget and Benchmarking Survey. a The cost savings ranges provided are based on the percentage of the project portfolio that uses a RA. We assume a minimum of 5% portfolio coverage and a maximum of 80%. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 4 ECONOMIC MODEL FOR AN RA IMPLEMENTATION (CONTINUED) Overall Assumptions ■■ ■■ ■■ A single RA implementation will cover 5% of the project portfolio in its first year of operation. A well-maintained RA program composed of multiple RAs will cover 80% of the IT portfolio after five years of operation and lead to the standardization of 70% of the infrastructure and virtualization of approximately two-thirds of the servers. The use of an RA shortens solutions delivery time by at least 50%, reducing FTE costs incurred on development projects by approximately the same amount. Specific Assumptions for a Single RA Implementation ■■ ■■ ■■ ■■ ■■ For the best ROI in application development, the first RA selected to pilot the program is a technology used by at least 30% of the application portfolio. Specific Assumptions for an RA Program Implementation ■■ ■■ Standardization of the infrastructure results in more effective vendor negotiations, reducing project software costs by 5%. ■■ Standardization also allows projects to share hardware capacity, bringing down project hardware costs by 20%. ■■ The RA’s adoption by 10% of the platforms in the organization reduces the operating expenditure on hardware by 20%. Lessons learned from the first RA help streamline development of future RAs, lowering the cost of developing and maintaining subsequent RAs. With infrastructure standardization, project software costs decrease by 30%. Project hardware costs are reduced by 50% due to commodity hardware, standardization, and virtualization. Over a period of five years, the widespread adoption of RAs leads to a 50% reduction in trouble tickets and an 80% reduction in mean time to repair, which reduces FTE costs for application maintenance by 50% and infrastructure maintenance by 60%. Increased technology standardization results in a 30% reduction in problems and a 20% reduction in the mean time to repair for those platforms using the RA, lowering associated FTE costs for application and infrastructure maintenance costs by about 40%. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 5 RA LIFECYCLE Initiate Galvanize IT stakeholders with a formal RA initiative. Build Deploy Govern Maintain Partner with project teams and developers to select and develop the most useful reference architectures. Provide the communication, education, and support necessary for maximum adoption. Establish oversight mechanisms to monitor the uptake and proper use of RAs. Ensure RAs are kept current and relevant. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 6 1. INITIATING A REFERENCE ARCHITECTURE PRACTICE EA groups looking to start an RA initiative struggle to build an effective business case because they have trouble communicating what an RA is, the benefits it can bring, and the investment necessary to manage the practice effectively. To initiate a successful reference architecture practice, leading EA groups begin with four steps: A. Establish a common vocabulary to communicate effectively with stakeholders. B. Relate reference architecture to other EA activities. C. Quantify the benefits to make the case for investment. D. Adopt a program management approach. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 7 RAs are documented best practices that help solutions delivery teams make effective design and technology choices. ■■ ■■ The purpose of an RA is increasing standards adoption, speeding time to market, and advancing toward the target state architecture. This toolkit includes all core deliverables needed to successfully implement an RA. 1A. DEFINE RA COMPONENTS Business and IT Strategy Capability and Technology Roadmaps Solution and Service Implementation Project Design and Delivery Business Capability Enablement Reference Architecture Toolkit AUDIENCE Senior IT and EA Leadership To Govern and Ensure Alignment with Strategy Principles: Highest level guidelines for governance of the enterprise architecture To Guide and Direct Solution Design To Improve Solution Delivery Reference Models: A common vocabulary and taxonomy of accepted concepts used to describe an organization’s capabilities Standards: Prescribed or preferred technology, design, data, and process elements that conform to architectural principles Patterns: Prepackaged and pretested design and technology combinations to build or modify a system Solutions Architects and SMEs Decision Frameworks: Use cases and decision trees that recommend particular patterns and standards Solutions Developers PURPOSE Implementation Guides: Detailed user manuals to instruct solutions teams on correct usage of standards and patterns Reference Working Prototypes: Practical instantiation of standards and patterns to provide a proof of concept to solutions developers Reusable Source Code: Repository of code objects used by developers to accelerate the building of frequently used functionality Adopt Source: CEB analysis. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 8 Principles are the highest level of guidance outlined for governance of the overall enterprise architecture. ■■ They help retain consistency of the overall architecture, while aligning IT implementations with the priorities of the organization. 1A. RA COMPONENTS: PRINCIPLES 1. Architecture will set the strategy for technology for three to five years into the future. 2. Weighted consideration should be given to a vendor architecture that contributes to and strengthens Johnson & Johnson EA. 3. For IT investments, the project design process includes architectural review and design certification by an enterprise architect. 4. A complete architecture includes the following five components: business process, information/data, applications, integration, and infrastructure. 5. Global use will be a determining factor in design: ■■ Every application should be designed with the expectation to be global, scalable, and flexible. ■■ Applications must have a planned lifecycle and asset map. ■■ Architect applications as systems, and engineer them for supportability. ■■ The architecture frameworks for all components must be designed to support internal and external customers and interfaces on a global level. ■■ Johnson & Johnson data standards will be established and globally used by all applications. ■■ Industry standards will be used wherever feasible. 6. Johnson & Johnson information is a valued asset and use must be designed and protected at the enterprise level, not by a specific company or project. 7. Applications will be designed for the adoption of, not mapping to, data standards. 8. Data quality management and transparency will govern design to establish authoritative data sources and ownership. 9. IT standards will be used; a nonstandard IT will require an exception waiver, and all required resources will be fully funded by the owner. 10. 11. Information Security services and solutions will be standards based. Security decisions will be based on a risk management process: “a risk taken by one is a risk shared by all.” Source: Johnson and Johnson; CEB analysis. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 9 A reference model is a common vocabulary and taxonomy of unifying concepts used to describe an organization’s capabilities. ■■ Reference models are usually defined either at the enterprise or BU level for a specific functional or technology domain. 1A. RA COMPONENTS: REFERENCE MODEL Information Systems Reference Model System User Information Provider Network Layer MPLS Leased Line VPN (Internet) LAN/WAN Channel Services Security Services Gateway Services File Gateway Service SFTP User Interaction Services Internet Gateway Service Presentation Services Composite User Interface Service Enterprise Service Bus User Interface Metadata Service Reporting Services BI Report Delivery Service Scheduling Service Report Management Service Transformation Service Service Management Access Management Service Directory Services Single Sign-On Service Identification Service Identity and Access Management Entitlement Service Authorization Service Provisioning Service Identity Management Service Content Management Service Metadata Management Service Document Service Definition Service Aggregation Service Repository Service Information Services Information Integration Service Application Integration Service Routing Service Extract-Transform-Load Service Data Warehouse Business Process Management Process Definition Service Transactional Database Process Execution Service Data Mart Operational Data Store Business Applications Chemicals Pharma Shared Group Source: Merck KGaA; CEB analysis. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 10 Standards are the prescribed or preferred technology, design, data, and process elements that help project teams conform to architectural principles. 1A. RA COMPONENTS: STANDARDS List of Technology Standards Across 132 Products Server, Desktop, Network, and Edge Protection Security Application Security SSL VPN—F5 L7 Firewall—F5 Vulnerability Tool—Foundstone Proxy—Bluecoat Vulnerability Scanner—Cenzic Source Code Review—Fortify L2 Firewall— Juniper NAC—Cisco ILP—Vontu AV—McAfee Risk Assessment/ Management—RSAM DB Compliance/ Enforcement—Guardiam Authentication/Authorization End-User Computing Collaboration, Presentation, and Application Services Integration, Messaging, and Data Transport Data Protection/Encryption Account Management Active Directory CA ACF2 Oracle LDAP 6.x SecureFX Voltage SecureData SecureCRT TIM 5.1 EMC RSA TAM 6.1 Pointsec Tumbleweed TDI 7.0 Vintella VAS Vshell 3.x Voltage Secure Mail Desktop Print Mobility Messaging Client Systems Windows XP Xerox Blackberry Exchange Microsoft Internet Explorer Microsoft Office Portal/Web Content Management Collaboration BPM/Workflow/Process Management/Rules Engines Vigenette Sharepoint FileNet BPM Miscellaneous Application Servers WebSphere Application Server Jboss/Tomcat V6.1 NET and II Mainframe CICS Application Integration V4.1 AmberPoint (Service Gateway) Blaze Microsoft IM Guidewire Application Messaging Bridje SOA IBM WebSphere MQ v6 Source: CNA; CEB analysis. INTRODUCTION INITIATING A REFERENCE ARCHITECTURE PRACTICE © 2015 CEB. All rights reserved. EAEC4283015SYN 11 Thank You for Your Interest in CEB Research! If you’re a member, please log into your account to access the full study. Member Login © 2014 CEB. All rights reserved. CIO9884614SYN If you would like access to this full study, please contact CEB to learn more. Contact CEB Contact CEB to Learn More IT.Support@cebglobal.com +1-866-913-8101 cebglobal.com/IT © 2015 CEB. All rights reserved. EAEC4283015SYN 12 SUGGEST DOCUMENTS -------------------------------------------------------------------------------- DOD ENTERPRISE ARCHITECTURE TECHNICAL REFERENCE MODEL Read more ORGANIZING HR TO LEAD ENTERPRISE CHANGE. CEB CORPORATE LEADERSHIP COUNCIL Read more REFERENCE ARCHITECTURE Read more ENTERPRISE ARCHITECTURE IN ENTERPRISE ENGINEERING Read more AN ENTERPRISE INFORMATION SYSTEM DATA ARCHITECTURE GUIDE Read more ENTERPRISE ARCHITECTURE CONSULTANCY Read more ENTERPRISE ARCHITECTURE AS INVENTORY Read more ENTERPRISE ARCHITECTURE MANAGEMENT TOOLS Read more JOURNAL OF ENTERPRISE ARCHITECTURE Read more ENTERPRISE APPLICATIONS ARCHITECTURE Read more 10 VALUING ENTERPRISE ARCHITECTURE Read more LEICHTGEWICHTIGE ENTERPRISE ARCHITECTURE Read more VISUAL ENTERPRISE ARCHITECTURE PLANNING Read more GOVERNMENT ENTERPRISE ARCHITECTURE Read more JOURNAL OF ENTERPRISE ARCHITECTURE Read more JOURNAL OF ENTERPRISE ARCHITECTURE Read more ATTENDANCE ENTERPRISE ARCHITECTURE Read more EFFECTIVE ENTERPRISE ARCHITECTURE MANAGEMENT Read more ENTERPRISE ARCHITECTURE PRINCIPLES Read more OPENSHIFT ENTERPRISE 3.1 ARCHITECTURE Read more ENTERPRISE ARCHITECTURE. AN OVERVIEW Read more SOA REFERENCE ARCHITECTURE BLUEPRINT Read more OPEN CLOUD REFERENCE ARCHITECTURE Read more EPIPHANY ARCHITECTURE REFERENCE Read more × REPORT "REFERENCE ARCHITECTURE IMPLEMENTATION GUIDE. CEB ENTERPRISE ARCHITECTURE LEADERSHIP COUNCIL" Your name Email Reason -Select Reason- Pornographic Defamatory Illegal/Unlawful Spam Other Terms Of Service Violation File a copyright complaint Description Close Save changes Copyright © 2023 KIPDF.COM. All rights reserved. About Us | Privacy Policy | Terms of Service | Help | Copyright | Contact Us × SIGN IN Email Password Remember me Forgot password? Sign In -------------------------------------------------------------------------------- Login with Google Login with Facebook