2. Joe Faghani, Lead Enterprise Application Architect, VMware
As Lead EA for Corporate IT at VMware, Joe is responsible for the continuous refinement of
current state solution architectures, the development of future state solution architectures
and the delivery of the company’s application portfolio roadmap. He also directs VMware’s
Architecture Review Board and oversees a team of system domain architects in charge of
reviewing solution and technical architectures. Prior to VMware Joe worked at Rambus
(Software Architect Emerging Technologies), Juniper Networks (EA), the US Army (Soldier
of Future Project SBIR), Cadence and Learning Tree (Software Architect Distance Learning)
Joe earned a bachelors degree in Computer Science from University of London
Mind the Gap: Closing the Gap between IT and Business
Improving business capabilities requires that all stakeholders understand the current state
from soup to nuts. Often key tribal knowledge is deeply hidden in various formats. At
VMware blueprints are developed to: operationalize tribal knowledge, help the business
fully understand the impact of the change and quickly show how IT aligns with business
capabilities. Unfortunately the architecture approval process and creation of these
blueprints can be time consuming. Please join us to learn how VMware streamlined their
architecture approval process and see how Troux is helping to close the gap between IT
and Business.
3. EPM Accelerate Headlines & Goals
Save 3% in operational costs by identifying and eliminating duplicate and
redundant processes, tools and technologies.
Reduction of business process, tools across the enterprise
Aligning top level goals & strategies to investments
Reduce project impact analysis time by 50% (from 3 weeks to 1.5 weeks)
Support the SDLC with outputs from Troux (at SDLC gates)
Improve business capabilities
Single source of Capabilities – capture previous work and standardize.
Increase mobile access to applications.
Improved employee & partners access to apps
Reduce risk , improve compliance and security
Improved compliance to standards
IAM Governance
5. Data Quality & Information Analysis
(July - October 2013)
Objective:
• Data loading into Troux
• Ensuring accuracy of data needed for targeted analytics
• Identify data stewardship structure
• Enable domain stewards through best practices for keeping key data current, correct, &
complete
Key Outputs:
• Reviewed/refined current data collection
• Identified the stewardship structure
• Analyzed the “to date” data collection
• Established a plan to mature data through iterative collections.
7. Planning for Governance & Stewardship
What we should be thinking about
• How will we establish stewardship?
– Top down support from our Sponsor and Key Stakeholder
– Continue to evangelize the benefits of Troux to the Business Functional Areas
• What will be our governance criteria?
– Project review process for ATRB, ITRB & ARB
– Enabling a project review workflow supporting the ATRB, ITRB, & ARB.
• Who will make our governance decisions?
– ATRB,ITRB, will review for completeness, & make recommendations as
necessary, ARB will make the final decision on projects.
7
17. Can you tell me…
• How many SaaS applications used by your organization allow direct or
“dual mode” authentication?
• How many of your SaaS applications contain SOX, PCI or PII?
• What are the Top 5 At-Risk SaaS applications used by your
organization?
18. IAM Governance using Troux
• Inventory the applications and data using Troux Portfolios
• Identify the compliance status with IT standards with Troux Insight
• Correlate common identity & access risks with information objects
• Tag and identify your applications by type using application functions
• Understand dependencies using web service object relationships
20. Accelerator Successes
• Improved Time to Value
– Impact analysis artifacts supporting governance decisions has been greatly reduced from weeks to less
than a day (25 artifacts delivered).
– Capturing tribal knowledge & disparate sources of information into a central repository has greatly
improved the accuracy of data analysis.
– Key infrastructure asset inventory available in a central store
• Improved Communications and Transparency.
– Providing a current state baseline data set for each portfolio established a “self service” source of
information. Communicating the availability of the data supported the initial principle of “Build it and they
will come”.
– The transparency of data has reinforced data quality as an ongoing necessity.
– Connection of business areas to IT Support Services.
21. TROUX ACTIVITY DASHBOARD
0/0
5/2
+10/0
314/10502
0
1501
Business
Architecture
Applications Technology
7418
2/0
+5/6 +5/2
0/21/1
Administration
(new users/existing)
Governance
(modeled/
ARB workflow)
Asset Management
(CRUD)
Analytics
(line of site/reports)
0/0
Information
0
+1/1
0
1 - Boston consulting expected to provide a refresh
2 - First number is applications; second number is integrations
22. Overall Lessons Learned
Critical Success Factors
22
• Data collection required more time than initially envisioned, initial inventories existed, but
required some cleanup. Connecting the dots between the inventories often required input from
subject matter experts.
• Scope of the components and relationships targeted was aggressive, driving through a more
focused set of use cases would tighten up the outputs provided by Troux.
• Collecting a wide foundation of data did support the socialization and evangelization of the
benefits of Troux.