ABB Collaboration Damand Management Process GF-IS Application Operations, Piotr Jakima, 2015-06-25 ABB Collaboration Damand Management Process © ABB Group September 19, 2018 | Slide 1

Agenda Demand Management Process overview Main roles in Demand Management Process Onboarding Proces overview © ABB Group September 19, 2018 | Slide 2 2

Demand Management Process overview © ABB Group September 19, 2018 | Slide 3

Demand Management Process overview – major roles SLM (Marek Hacuś): responsible for overall Service and Demand Management Process, Demand Manager (Łukasz Kutera): responsible for collecting all requests and for make sure that all requests will be processed through all required sub-processes like Demand, Change Management and Sales Processes. Business Analyst (Tomasz Mizak): responsible for detailed analysis, for driving decision where requirements should be implemented (Sites, Custom Apps) Onboarding Manager (Piotr Jakima): responsible for Onboarding Process activities coordination on Collaboration Team side Solution Architect (Roman Plaza): responsible for Development Team, conducting architecture and code review during the Onboarding Process. Operation Manager (Stanisław Delost): Responsible for Operation Team, keep our environment fully operational and stable, he is doing all activities related to the deployment process. © ABB Group September 19, 2018 | Slide 4

Onboarding Management Process – roles and responsibilities Application owner (person from the Business side in which the application will be used): Representative from the business with full mandate and responsibility to make decisions related to the scope and budget for the application and its operations. Project Manager (Business, optional role): Person appointed by the Application Owner to drive the onboarding process from the business perspective. Typically the development project manager if it is a development project. Technical contact /Architect (Business or IS/IT organization): Person appointed by the Application Owner. SPOC (Single Point of Contact) for all technical matter (including application architecture). This person should have a good understanding of SharePoint architecture and ABB’s IS landscape and guidelines. This person is a Single Point Of Contact for Solution Architect and Infrastructure Architect. Service Level Manager (Hosting Team): Owner of the Global SharePoint Hosting service, with service delivery and budget responsibility. Onboarding Manager: responsible for Onboarding Process activities coordination on Collaboration Team side Solutions Architect (Hosting Team): Person responsible for ensuring that application which is going to be deployed on common Global SharePoint Environment meets all requirements, guidelines and strategy required by ABB Collaboration Platform. Responsible for Architectural Review and Code Review of new applications. Infrastructure Architect (Hosting Team): Person responsible for all arrangements and activities related to the infrastructure layer, for new application’s versions deployment on test and production environments.

Onboarding Management Process – Initiation Phase

Onboarding Management Process – Implementation

Onboarding Process – main features and things necessary to be take into consideration Demand Management Process is designed to deal with requests which are not clear vision how particular requirements and goals should be achieved. If Customer wants to host his app on SP farm then Onboarding Process can be started instead of Demand Management. During Onboarding Process commercial offer will be prepared also. ABB Collaboration Team prefer to be involved in the new project as early as possible to be able to: actively contribute to the success of the project from the beginning and ease the deployment and operations of your application in the common hosted platform avoid situation when crucial decisions about technical design are taken without appropriate consulting with ABB Collaboration specialists (in that case new application can be rejected). Onboarding Process consists of following major activities: Request for Hosting, Onboarding Site creation, Feasibility Chech-point, Commercial Offer preparation, Architecture Review, Code Review, Deployments (on Test or Production env.) Application without iGAR number cannot be deployed on any SP environment. Commercial Offer must be accepted before the application can be deployed on SP farms ABACUS code must be delivered by Customer before production launch. Without this information (necessary in settlement process) application won’t be installed on production. Link to iCAR registry: link to the document How to use iCAR (basics): link to the document All official information and documents are stored on iCAR: link to the document © ABB Group September 19, 2018 | Slide 8

Onboarding Process – taking decision (SP farm is the right place for particular app or not) For demand management activities (buy brand-new solution, custom application creation, new application hosting) Collaboration Team will help customer to define target domain for application in following way: If ABB Collaboration Team decides that Collaboration domain is the right choice for particular application, Customer can and ask EA Team to create iGAR number. Customer is responsible for iGAR creation process and cooperation with EA team, iGAR number must be delivered by Customer in order to start demand processing (hosting or development), If ABB Collaboration Team decides that application is targeted to non-Collaboration domain or to new domain (Share Point farm is not the right place for particular application) then EA Team needs to be involved. Customer must contact with EA Team on their own and try to finalize arrangements and decision process: what is the right direction to follow, which platform is the right choice. Please note: ABB Collaboration Team will not act as middleman or proxy between EA team and Customer, Customer is responsible for carrying all required arrangements and correspondence in order to clarify all issues related to their demand. © ABB Group September 19, 2018 | Slide 9

iCAR – short overview – Main Page © ABB Group September 19, 2018 | Slide 10

iCAR – short overview – Action Items © ABB Group September 19, 2018 | Slide 11

© ABB Group September 19, 2018 | Slide 12