USERNAME PASSWORD

HPE Enterprise Maps


Armstrong Process Group (APG) is an HPE Partner that is committed to proven and practical process guidance for aligning information technology and systems engineering capabilities with business strategy.

Integration to:

Sparx Enterprise Architect

Overview

Ensure delivery of your business, application and infrastructure investments based on business strategy.

HPE Enterprise Maps drives IT Transformation agendas by understanding the overall IT landscape, linking it with business outcomes, identifying wase and assuring IT is aligned to business strategies.

HPE Enterprise Maps


HPE Enterprise Maps

HPE Enterprise Maps (HPE EM) together with proper enterprise architecture (EA) standards implementation addresses the main IT transformation challenges, by introducing visibility, governance and connectivity across all the demand through fulfillment activities.

  • Accelerate Time to Market
    A key requirement of many IT organizations is to continuously speed up the time to market of their services. In order to do this, IT must be able to quickly understand and decompose the business requirements in the right level of detail. All changes need to be evaluated and properly incorporated into the existingplan of record. HPE Enterprise Maps speeds up the demand planning by providing accurate information about the actual IT and current plans. Architects and analysts can focus on change moreefficiently by re-using existing capabilities in design. The HPE EM lifecycle assures standard processes and planning deliverables. HPE EM evaluates impacts of change to quickly identify consequences.
  • Reduce Costs
    While delivering services, IT needs to keep the overall budget in check. HPE EM provides traceability and visibility to planned cost, actual transformation spend and total cost of ownership. Immediate feedback on cost savingsopportunities is provided for variousstakeholders by aggregating financial information in an enterprise architecture model. For each project, HPE Enterprise Maps defines a clear‘desired state’ driven by business requirements and costs. HPE EM ensures real-time visibility of cross- project dependencies and provides real-time what-if analyses.
  • Improve Quality
    Maintaining high quality deliverables per project is another key requirement. HPE EM continuously evaluates high- risk, unreliable services during the planning cycle so that they are addressed during the transformation.The quality of the design is improved through connecting all aspects of the deliverables (from infrastructure to applications to the business) and governing through the entire delivery cycle. Organizational quality standards are managed and ensured by design policies that are validated and enforced in all project phases.

Typical Transformation challenges

Today’s IT organizations are under constant pressure from the Lines of Business to decrease time to deliver services, systematically reduce the cost of IT, and increase the overall project quality.

The reality is that most business requirements in the demand queue are never fully implemented or there is severe delay or gap between expectations and the results. These problems lead to lower quality deliveries, reduced market share and lost revenue. Even if the requirements are delivered, project costs are typically way over budget.

A critical prerequisite for making good informed decisions is precise information about IT systems, their relationships to processes, business capabilities and company goals.


Key takeaways

Main values provided by HPE Enterprise Maps:

  • Utilizing many principles from ArchiMate® and TOGAF® EA standards
  • Integrates with HPE software tools out of the box
  • Speed-up Demand to Solution Process
  • Identify IT Waste and Redundant IT Spending
  • Speed-up Business Responses by Simplifying IT
  • Reduce IT Projects Risks Driven by Business Strategy Changes
  • Eliminate Appl. Silo & Vendor Lock-in Issues
  • Propose and Manage Transformation


Download
Data Sheet

em-video-thumbWatch Video


Getting Started

  • Step #1: Build Enterprise Model HPE Enterprise Maps guides customers how to build their enterprise model and consolidate new EA models from projects and deployments.
    The first step is to collect data from various enterprise applications, projects and assets into a centralized model, using existing information where available. HPE EM model supports ArchiMate®, an open standard modelling language for enterprise architecture that is supported by multiple vendors and consulting firms. ArchiMate® provides enterprise modelling semantics that describes the entire organization. HPE EM supports out of the box synchronizations with Sparx EA, HPE PPM, HPE uCMDB, spreadsheets, XML files and databases.
  • Step #2: Understand dependencies
    hp-understand-dependencies

    Once the enterprise models are defined, the next step is to understand the various interconnections and dependencies. HPE EM tracks these connections and offers various views identifying inconsistencies between layers and even derived relationships.
  • Step #3: Visualizations for key Stakeholders
    HPE Enterprise Maps creates reports, views and dashboards based on specific user roles to help each stakeholder make critical business decisions.Typical key stakeholder questions:hp-cfo-screenshot

    Chief Financial  Officer – What is the actual application cost? Are we investing appropriately with our strategy? What is the current IT cost distribution? Are our current capabilities over budget?

    hp-cio-screenshot

    Chief Information Officer – What are the candidates for an application transformation or cloud initiative? What is the impact of delays in our IT delivery roadmap?

    hp-ea-screenshots

    Enterprise Architects – How is IT supporting the Business? Are our solutions and projects adhering to compliance regulations? What are the impacts of a change? Has the requested service been delivered?

    hp-ta-screenshot

    Technology Architects – Are we using approved SW? Which business is impacted most by our technology decisions? What is SW/HW technology roadmap?