Build on Cloud

Solutioning and Delivery Guidance

Build on Cloud Solution Guidance Overview
Build on Cloud Demand Profile cover a broad spectrum of solutions. Based on experience, following types of solutions
can be expected

1. Micro - Service Applications

2. API-enablement of existing Systems
3. Internet of Things
4. Monolithic applications implemented on cloud

Hybrid IT landscape is considered as a given for all these applications; hybrid aspect is not limited to a combination
of on-premise, public or private cloud but also includes a combination of PaaS, IaaS and SaaS service models as
well

This guidance provides a view of key areas to be considered while solutioning and the technique to be followed for
getting the cost/price for labor & platform (infra + software) components

This version focuses on Micro Services and API enabled applications hosted on IBM Bluemix Platform as a Service
platform.

During solutioning; this demand profile may need to be combined with App Ops on Cloud Demand profile

Overall, a template based approach is recommended for Build on Cloud. This requires use of pre-defined templates
and t-shirt sizes that can be selected based on opportunity requirements ; primarily to accelerate solution development

In the current version, this guidance is provided for Micro-Service Applications & API Solutions. In future versions, this
will be extended for the other types of solutions

2015 IBM Corporation

Build on Cloud Solution Entry Points
Proof of
Minimum Viable Solution @
Concept /
Product Scale
Technology
Market-ready Scope Scale from functional coverage as
Minimal Scope Focus on optimum business functionality well as Production grade SLA/SLO
Focus on idea proofing, rapid build coverage coverage
Internal Team consumption; Buildout in 4-6 months
Buildout over multiple phases in 6-
production grade not required Production Release for limited users/groups
18 months
Work Details Work Details
IBM Design Thinking Workshop IBM Design Thinking Workshop
UX and Visual Design UX and Visual Design
Build Prototypes on Bluemix
Build Prototypes on Bluemix User Testing
User Testing DevOps Setup & Application Development
Deliverables Knowledge Transfer & Go Live
Minimum Viable Product Deliverables
Statement Production Quality code on Bluemix
Design Artifacts Design Artifacts
Live Prototype on Bluemix Project documentation
User Testing outcome User validation report
Test and delivery artifacts
Duration : 4 -6 weeks High Level Roadmap
IBM Participants: Design Thinking Operations Handbook
SME, Garage Solution Architect/Technical IBM Participants: Design Thinking SME,
Lead, UX/Visual Developer, Developer Garage Solution Architect/Technical Lead,
Client Participants: Business & IT UX/Visual Developer, Developer
Leaders, Product Managers/Delegate, Client Participants: Business & IT Leaders,
Architect/Delegate, Project Manager Product Managers/Delegate, Architect/Delegate,
Project Manager Customized solution ; T-Shirt sized solution
can be used partially; will require additional
considerations
Staffing
Use Template + T-Shirt Size Guidance
2015 IBM Corporation
Build on Cloud + App Ops On Cloud : Solution Component View

Integrated Operations*

Build on Cloud
(Design +Build services)

GBS Middleware
Mgmt

Managed Infra Mgmt PaaS SaaS GBS GBS

Security Testing
Services DevOps Services
IaaS

Private Public Local Dedicated Public

Hybrid Cloud Platform
*Integrated Ops might be required during design/build as well

Build on Cloud App Ops on Cloud GTS Collaboration IBM/ other Cloud Platform Components

2015 IBM Corporation

Solution Component Guidance &Scenario Mapping
# Key Solution Components Guidance Summary Scenario / Approaches Entry point applicability

a) Cloud native solution reference a) Micro Services Application Proof of Minimum Solution @
Concept / Viable Product Scale
Cloud Native Application architecture b) API-enablement Technology
1
Design Build b) Standard t-shirt size solution c) Internet of Things Solution
(incl. Estimation, Delivery Squad ) d) Cloud native monolithic architecture solutions
Proof of
a) Standard t-shirt size solution for a) IBM Cloud used for Design build Concept /
Minimum Solution @
2 Application Delivery Platform Technology
Viable Product Scale
PaaS b) Non-IBM Cloud used for Design Build

a) Standard t-shirt size solution for

a) SOC services for end to end support
4 Business Solution Operations a system (S/M/L) Minimum
Viable Product
Solution @
Scale
b) SOC Services for platform only
b) Portfolio applications

a) Standard t-shirt size solution for

a system (S/M/L)
b) Custom DevOps toolchain a) DevOps Minimum Solution @
5 Business Solution DevOps Viable Product Scale
(shared / dedicated) on Cloud b) SOC Services for platform only
c) Custom DevOps toolchain
hosted / managed by IBM
Middleware Management Minimum Solution @
6 Standard rate-card based MW services baked into any solution context Viable Product Scale
Services
a) Standard t-shirt size solution for
a) IBM takes end to end ownership of a portfolio / or a
Business Solution Security & a system Minimum Solution @
7 system. Viable Product Scale
Compliance b) Custom solution for portfolio of
b) IBM builds / transfer solution to client.
applications

a) Deployment model needs to be

analyzed for MSP solution a) MSP Support for IaaS and/or PaaS (Bluemix) Minimum Solution @
8 Managed Services Support Viable Product Scale
design. Bill of Material, NFR together.
including SLAs are needed.

2015
BuildIBM
on Corporation
Cloud App Ops on Cloud
Build on Cloud : Overall Solution Flow (Primarily for MVP and Scale)
A Functional + Technical B Operational B Contractual
Initiate
1 Collect Volumetric Attributes
1 Determine Functional Scope/Attributes
Use App Ops
2 Select Platform T-Shirt Size on Cloud
2 Determine Technical Attributes guidance
GBS (incl. non functional)
Solution Define Application Architecture 3
N BAFO Price
Calculate Platform ROM Price Submission?
Architect 3 ( using Template + Guidance)

4 Select MW Management Size Y

4 Estimate Effort point using Guidance

Select Delivery Team T-Shirt Size 5 Select DevOps Services Size Tailor RACI Template
5 1
(based on Effort Points)

6 Select Security Services

6 Complete ITDA Reviews
Cloud
Platform 7 Provide Platform Firm Price 2 Agree on DOU / RACI
Seller
4
Create Addl Solution Artifacts
(as reqd by SIH/IOT)
GBS 7 Create Staffing Plan Solution @
(based on template) 8 Select Integrated Ops Size Complete SIH/IOT Reviews Scale
Solution 5
Manager Create Overall Delivery Plan
8 6 Finalize SoW / Proposal etc Minimum
Viable Product

Provide summarized cost inputs for

7 Pricing

Complete
Select Platform Management T-Shirt Size
Platform 9
Mgmt.
Provide Platform Management Price 3 Agree on DOU / RACI
Team(GTS) 10

2015 IBM Corporation

A. Functional + Technical Areas
# Activity Step Guidance

1 Define / Adapt Technical Solution Determine Functional Scope / Attributes Identify Key Users, systems & Data Flow (adapt system
context)
Define MVP & End State Scope
Identify Channels & Key User Experiences

Define Technical Attributes
Identify integration mechanisms & Frequency with upstream
channels & downstream SoRs
Determine persistence requirements (e.g. transactional,
analytical etc)
Identify Non Functional Requirements

Adapt Application Architecture Use Standard Templates and tailor wherever required
Finalize Architecture Decisions and Technology Selections

2 Select Application T-Shirt Size for Delivery Estimate Effort using Guidance Use Effort estimation t-Shirt Sizing to calculate Effort Points

5 Select T-shirt size for delivery Use Delivery Team T-shirt sizing and composition based on
Effort Points

3,4 Adapt Staffing Plan Use Delivery Guidance

Adapt Delivery Plan

2015 IBM Corporation

Define/Adapt Technical Solution Non Functional Considerations
Non Considerations
Functional
Requirement
Availability Is there upfront, known affinity with on-premise applications & low response latency?
Network connectivity between on-premise apps and cloud may not be amenable to the response time requirements
Is this a mission critical application with aggressive availability / disaster recovery requirements ?
Check latest Terms of Use for PaaS availability
PaaS availability (for e.g. Bluemix) could depend on multi-region deployment. This in turn, could have an impact on cost
https://www-03.ibm.com/software/sla/sladb.nsf/sla/bm-6606-09
Disaster
Recovery Identify and document Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for the application
Choose Persistence Options based on DR Requirements and SLA/SLO of services provided
Make additional considerations for Data Replication etc. if required
Security & Data Identify Authentication & Authorization Requirements
Privacy Authentication can be possible through Bluemix SSO, but that would require SAML / Oauth based authentication provider at
customer end. Consider Cloud Identity Services (CIS) as an alternative
User Credential Management is a key responsibility - This is best done by customer teams, its important that the responsibility here
is identified early and documented clearly
Identify additional requirements, specifically Intrusion Detection, Secure Communications etc
Identify specific requirements for Data Encryption in-flight and at-rest
Manageability

2015 IBM Corporation

API Development : Complexity and T-shirt size selection steps

Delivery Squads will

Calculate Effort primarily provide Design,
Point using Coding & Unit Test
Guidance Services

Architecture & Service

Discovery will be
Determine provided by a common
number of arch + design team
Delivery +
Support Squads System Testing, UAT
Squads need to be
selected separately
Determine
Application T-
Shirt Size for
Delivery

2015 IBM Corporation

Calculate Effort Point API Development

Integrated Operations # Component Type Description Effort Point Calculation

Guidance
Securi Integr API Gateway
ty ation
b 1 API a. API Implementation with a. API Effort Point
Implementation business logic; business rules Calculation
b c Self Service Portal b. API endpoint exposure ; API
b security; throttling; version
management
API Management b c. Integration (composition,
orchestration ) with external
systems using existing
Implementation services
a

Testing DevOps

Management & Monitoring

Hybrid Cloud Platform

2015 IBM Corporation

API Effort Point Calculation
1. Identify APIs and their Operations.
2. For Each factor, select the applicable complexity level (e.g. it is possible to have an API to have Complex # of endpoints and Simple Operations)
3. Award effort points per factor based on the last column. It is either same as the # for the factor or is a weight based on the applicable complexity
4. Total Effort points will be required to identify number of delivery squads

Effort Point per

Factors Simple Medium Complex
Parameter
Same as number of
Number of endpoints/Services Invoked 1 2 3 to 5
endpoints
No. of API Entities (e.g. Customer, Account) 1 2 3-5 1,2,3

No. of API Operations (e.g. Get/Put/Post/Delete) 1-4 5-8 9-20 1,2,3

API Data Models (Total no. of attributes) <20 20 to 40 40-100 1,2,3

2
3 to 5
1 (Aggregation of Same as number of
Data mapping complexity (Aggregation of 1-3 Proxy &
(Simple Proxy) 1 Proxy & 1 new aggregations
1-2 new API assembly)
assembly)
Validation None Mandatory fields >10 fields 1,3
Error Handling Standard Error codes Custom Error codes Framework 1,2,3
Rules None Simple Complex 2,3
Basic
Security None Custom/header based/OAuth 2,3
(Client id/Secret)
Publishing APIs 3 4-6 6-10 1,2,3

Basic plan Up to 3 Plans with rate >3 plans with rate limiting
Subscription/Usage Management 1,2,3
(<5 users) limiting (<10 users) (>10 users)

2015 IBM Corporation

API Development : Delivery Squad Roles
API Designer Scrum Master
How do I assemble APIs? Remove impediments
How do I manage security? Communications Management
Will the infrastructure scale? Conflict Management
How do I measure performance? Maintain Velocity

API Developer
Create and configure APIs
Reuse assets & apply
patterns
Technical implementation of
APIs
Unit Test

Operations Lead DevOps Lead

How do I manage all the API DevOps & Automation Evangelist
Environments that are being requested? Release Strategy?
How can I scale each environment? Configuration Management
How can I easily find and fix issues?

Functional Tester Automation Tester

What test cases will be required for core What level of automation can be achieved
functional testing? considering the functionality ?
What are the different scenarios that How to implement and integrate with
need to be covered ? DevOps ?

2015 IBM Corporation

 API DEVELOPMENT: DETERMINE NUMBER OF DELIVERY & SUPPORT SQUADS*
Lead Designer
IBM Architect Lead Business Lead Designer API Product
Common Lead Designer Test Lead
Arch + Analyst Manager**
Design

Delivery Squad Infra Management Squad Ops Squad

(for IaaS components only)

Offshore
Analysis
+
Designers
Onshore System Engineers Operations Lead

Offshore
Scrum Master
Design
Build
Landed Offshore
Infra Mgmt Lead DevOps Lead
Designer Developer / Tester Onshore

Offshore Offshore
Developer Automation Functional DevOps SME Developer
Developer
Tester Tester

1 Analysis + Design Build Squad can deliver 80 points / month ( Design+Code+Unit Test). This roughly equals
2 Simple, 2 Medium, 1 Complex API

*Test Squads would need to be added separately

2015 IBM Corporation
**Optional
 API DEVELOPMENT : DETERMINE DELIVERY TEAM T-SHIRT SIZE
Calculate Effort Points for API Solutions
Select number of Delivery Squads based on Effort Points and Delivery Timeframe ( 80 Effort points / month / Squad metric)
Choose Application T-Shirt Size based on the number of delivery squads required to get the total dedicated team size
Use Staffing Plan templates and tailor based on delivery & support timelines

Small Medium Large

# of API Delivery Squads 1 2-4 5-7

Common Arch + Design 3 4 5

Overall Governance Team Size 1 2 2

Total Dedicated Team Size 10-14 25-50 60-100

Shared Teams

# of Infra Management Squads 1 1 2-3

(Shared)

# of Ops Squads (Shared) 1 1 2

Shared Team Size 8 8 16-20

2015 IBM Corporation

MicroService Applications Complexity and T-shirt size selection steps

Select Delivery Squads will

microservice primarily provide Design,
application Coding & Unit Test
complexity using Services
t-Shirt Size
Architecture & Service
Discovery will be
Determine provided by a common
number of arch + design team
Delivery +
Support Squads System Testing, UAT
Squads need to be
selected separately

Determine
Delivery Team T-
Shirt Size

2015 IBM Corporation

MicroService Application
MicroService Architecture based solutions require multiple components to be considered for estimation, which are summarized
in the table below
Solution T-Shirt Size should be selected based on the combination of complexity factors of these components

Integrated Operations # Component Type Description

Security IPC API Gateway 1 1 API Gateway a. Effort for API Endpoint Exposure,
3.c Management, Authentication, Key
1 Proxy 1 Circuit Breaker 1 Management

BFFs 2 2 BFF a. Effort for building a user experience specific

API composition and orchestration layer

3 MicroService Application a. Effort for building a micro-service application

MicroService Business API
3.a including Persistence Representation &
Persistence retrieval logic as well as business logic, rules
per bounded context
ETL 3.b b. Effort required for loading/synching data
between microservice persistance & external /
MicroService Application SOR persistence
c. Effort required for IPC
Testing DevOps

Management & Monitoring

Hybrid Cloud Platform

2015 IBM Corporation

 MicroServices Application T-Shirt Size Selection
Components Simple Medium Complex
API Gateway , 1-2 Endpoints 3-5 Endpoints 6-10 Endpoints
Proxy, Circuit Synchronous Invocation only Synchronous OR Asynch Invocation Synchronous AND Asynch Invocation
Breaker Basic Management Plan (<5 Users) Upto 3 Plans with Rate Limiting (<=10 users) >3 Plans with Rate Limiting
BFF Proxy Exposure

Proxy Standard Load Balancing Load Balancing + Canary Testing Load Balancing + Canary Testing

Circuit Breaker Not used, self-sufficient app; Circuit breaker services for 1-2 external Circuit breaker services for 3-6
Services external services

Security Basic Platform Security ; does not require user Cliend ID / Secret Oauth, Customer header based,
credential validation SSO

BFF 1-2 BFFs 3-5 BFFs 3-5 BFFs

<=2 operations/BFF 2-3 Operations/BFF 3-4 Operations/BFF
<= 2 API Compositions Orchestration across upto 2 Business APIs Orchestration across 3-5 Business
APIs

Microservice API & Persistence Logic API & Persistence Logic API & Persistence Logic
Application : <= 2 Entities <= 4 Entities <= 6 Entities
Business API & <= 20 Fields / Entity <= 20-40 Fields / Entity <= 50-100 Fields / Entity
Persistence <=4 operations <=8 operations <=9-20 API operations
Standard Error Codes Standard + Custom Error Codes Error Mgmt Framework
REST Exposure Simple Business Logic Complex Business Logic

Microservice One to One Mapping for 2 Entities, upto 20 One-Many OR Many-One mapping for 4 Combination of One-One, One-Many
Application : ETL fields / Entity entities, 20-40 fields/entity > 10 Fields validation
No Validation Validation for Mandatory fields only

Microservice No external integrations <= 2 external integrations 3-6 external integrations

Application: IPC Synch OR Asynch communication Synch AND Asynch communication
REST or SOAP REST+SOAP + Other protocol
combination
2015 IBM Corporation
MicroService Applications : Delivery Squad Roles
BFF Designer /Developer
What are the channel specific API
Requirements
What API endpoints and operations
need to be consumed ?
What is the orchestration /
consumption logic required ?
MicroService ETL Developer
What is the mapping required for
microservice data
How frequently does the data
need to be synched
/transformed?
Operations Lead
How do I manage all the API
Environments that are being
requested?
How can I scale each environment?
How can I easily find and fix issues?
Functional Tester
What test cases will be required for core
functional testing?
What are the different scenarios that
need to be covered ?
2015 IBM Corporation
MicroService Designer Scrum Master
What is the bounded context? Remove impediments
What is/are the core functions Communications
exposed by MicroService App? Management
What is the business logic Conflict Management
required for implementation ? Maintain Velocity
MicroService Data Modeler MicroService Business API Developer
What entities should be Create and Configure APIs
included? Implement Business Logic
Which fields do I need per Implement Persistence Retrieval
entity? Logic
Implement IPC/ Failure Mgmt.
DevOps Lead
DevOps & Automation Evangelist
Release Strategy?
Configuration Management
Automation Tester
What level of automation can be achieved
considering the functionality ?
How to implement and integrate with
DevOps ?
 MICROSERVICE APPLICATIONS: DETERMINE NUMBER OF DELIVERY & SUPPORT SQUADS*

Lead Designer
IBM Architect Lead Business Lead Designer
Common Lead Designer Test Lead
Arch + Analyst
Design

Delivery Squad Infra Management Squad Ops Squad

(for IaaS components only)

Offshore
Analysis
+
MicroService Designer
Onshore System Engineers Operations Lead

Offshore
Scrum Master
Design
Build
Landed Offshore
Infra Mgmt Lead DevOps Lead
MicroServices BFF Designer Onshore
Designer

Offshore Offshore
DevOps SME Developer
Developer
BFF Biz API ETL Data Automati
Developer Developers Functional
Dev Model on Tester Tester
er

*Test Squads would need to be added separately

2015 IBM Corporation
MICROSERVICE APPLICATIONS - DETERMINE DELIVERY TEAM T-SHIRT SIZE
Identify number of MicroService Applications and Complexity based on T-Shirt Size guidance
Select number of Delivery Squads based on Effort Points and Delivery Timeframe ( 80 Effort points / month / Squad metric)
Choose Delivery Team T-Shirt Size based on the number of delivery squads required to get the total dedicated team size
Use Staffing Plan templates and tailor based on delivery & support timelines

Small Medium Large

# of Microservice Delivery Squads 1-2 2-4 5

Common Arch + Design 3 4 5

Overall Governance Team Size 1 2 2

Total Dedicated Team Size 12-24 25-40 50-100

Shared Teams

# of Infra Management Squads 1 1 2-3

(Shared)

# of Ops Squads (Shared) 1 1 2

Shared Team Size 8 8 16-20

2015 IBM Corporation

 BUILD FOR CLOUD: DELIVERY GUIDANCE

Cloud technologies like platform-as-a-service, evolution in software defined environments, and tooling frameworks have given rise to true realization of
the Cloud Native applications and primarily leveraging microservices architectural style. Build on Cloud encompasses methods and processes to build
cloud native applications for clients. The primary method of delivery is the IBM Bluemix Garage ++ Method

Delivery Lifecycle
1
1. Design
2. Develop POC 3. Develop MVP 3. Scale (Continuous enhancements)
Thinking

Minimal Scope Market-ready Scope

Focus on idea proofing
Rapid PoC (4-6 weeks)
Internal Team consumption;
production grade not required
Focus on optimum business
functionality coverage
Buildout in 4-6 months
Production Release for limited
users/groups
Scale from functional coverage as well
as Production grade SLA/SLO
coverage
Buildout over multiple phases in 6-18
months

Delivery methodology Components

Method & Templates Talent Model & Team Tool Based Delivery Service Delivery Foundation

IBM Garage Method ++ based with
hybrid cloud scenario extensions
Deliverables and templates
Project Management Guide
Normative guidance, Estimation
templates/tools
2015 IBM Corporation
Team composition roles, band mix
guidance, responsibilities, skill sets
Agile Squad based delivery model
different types of squads (co-located
and remote squads)
DevOps toolchain driven model.
Continuous planning, development,
integration, delivery and monitoring
Code discovery tooling for
modernization
Foundation Technical Services
configured for Solution Pattern
- , Agile & DevOps, Security,
Testing, Solution Operations
Center*
* Optional services
BUILD FOR CLOUD: IBM GARAGE METHOD WITH EXTENSIONS FOR HYBRID CLOUD DELIVERY

2015 IBM Corporation

Methods and Templates
Innovation Workshop POC Sprint Analysis & Macro MVP Sprints & Architecture Refinement & Enterprise Scale Sprints &
(1 Week) (4-6 Weeks) Design(4-6 weeks) Playbacks(12-16 weeks) Analysis for Scale Playbacks

WEEK |
Proposed schedule
1 2 3 4 5 6 .. .. 16
MVP Sprint 1.N Enterprise Scale Sprint 1 - N
Design Workshops

Architecture
On Paper
Review Playbacks MVP

High Level Design

Frameworks Demo
Arch Refine ment for Scale

Stories/Ta Demo Stories/Ta

Stories/Ta Demo
sks sks
sks
Iterate
&
Stories/Ta
Deliver Stories/Ta Demo
Stories/Ta Demo
sks
sks sks

Demo Demo
Stories/T Demo Stories/T
asks asks Project
Project Playback
Playback

Continuous Backlog Refinement Continuous Backlog Refinement Continuous Backlog Refinement

Activities = Deliverable
Activities Activities Activities
Conduct Activities Activities Activities
Development Space Setup Define Operational Architecture Production and Test Space Setup
Introductory Identify & Agree Apply Scale Considerations Production and Test Space
Implementation Define Application Architecture Implementation
Workshops Hills Refine Operational Architecture Update
Daily Scrum Calls Volumetrics Daily Scrum Calls
Confirm Sponsor Define Priority Refine Application Architecture Implementation
Conduct Playbacks API Identification Conduct Playbacks
Users and Personas Identify Skills Update API and MicroService Daily Scrum Calls
Backlog Refinement & MicroService Identification Backlog Refinement &
Confirm Key catalog Conduct Playbacks
Reprioritization Reprioritization
Challenges Backlog Refinement &
Conduct Design Reprioritization
Thinking Workshop
Candidate Solutions
Deliverables Deliverables
Deliverables Deliverables Deliverables Deliverables Deliverables
Design Hills / Features Design Hills / Features
Personas, Sponsor Minimum Viable Application Architecture Application Architecture Design Hills / Features
Executables Code, Unit Tests Executables Code, Unit Tests
Users Product Statement Operational Architecture Operational Architecture Executables Code, Unit Tests
Apps / Deployables Apps / Deployables
POC Candidates Live Prototype API and Microservices Catalog API and Microservices Catalog Apps / Deployables
 BUILD ON CLOUD : DEV TOOLING FRAMEWORK

Requirement Cloud Code Trigger Test the Deploy to Proactive

s Grooming Native Check-in Build Build Production Monitoring
All the stakeholders Developmen
Developers leverage Developers check-in Before the code gets The code is then Fully tested and verified The Continuous
collaboratively identify Bluemix PaaS and other their code to the Git committed, it is promoted to the test applications are then Monitoring tools help
& prioritize the Product
t
Cloud services to Repository on Bluemix automatically built, environment, where promoted to the pre- pro-actively monitor the
Backlog Items develop at least once a day analyzed and tested for end-to-end testing is prod environment for deployed application
Cloud native sanity done UAT, and then to
applications production

Bluemix Track & Plan Build Orchestration

Used for capturing Tools for pro-active and
tool responsible for automated monitoring
requirements, project Continuous
planning & reporting Integration
Collaboration
Git & its variations Repository Tools for automated deployments, &
Management tool Static Code Analyzer Test tools that enables
Source Code Repository provisioning environments
automated testing

2015 IBM Corporation

 BUILD ON CLOUD : OPS TOOLING FRAMEWORK
Dashboards & Reporting
Service Level Management Reports Grafana/Freeboard

Runbooks
Custom monitoring IBM Runbook Automation
alerts

Monitoring
NewRelic Collaboration

Dynatrace Tealeaf Slack

Nagios AICS MW Tools Mural.ly

Operate Event
Bluemix Notification
Trend Micro AV Management
TSM Monitoring/A PagerDuty
Runscope nalytics Netcool Omnibus
Bluemix Key Impact (NOI) Incident
Management
Protect
IBM Control
Bluemix
Logging Desk
Autoscaling
Splunk QRadar

Manage 2015 IBM Corporation Analyze

Monitor
 BUILD ON CLOUD: DELIVERY STAFFING & ROLES

Roles Staffing

2015 IBM Corporation

 B. OPERATIONAL AREAS
# Step Guidance

1 Collect Volumetric Attributes Identify key parameters that impact application performance and infrastructure sizing
Identify base values and assumptions
Get a view of volume increase over 3-5 years to create a view of current and future volumes

Typical Parameters considered

Number of Users (for each type of user e.g. Employee, customer )
Number of Concurrent users
Average Message Load / Transaction
Total Transactions
Number of access locations
Number of Devices
Data stored / user / transaction

2015 IBM Corporation

App Ops : Hybrid Platform Service Selection for Build on Cloud
No
No PaaS service
available?
GBS Hybrid Cloud &
(i.e. Management
functional Services
/ operational fit)
Yes SaaS
Solution Operation Center
Container service No
available?
available?(i.e. Migration Factory/ GBS DST
(i.e.
functional functional (SW product management)
/ operational fit) / operational fit)
GTS IMI
Where applicable due
to Client needs, non- Yes
(OS, Network, Storage
IBM PaaS can also be
considered mgmt.)
Assumption:
SaaS is fully IaaS (IBM, Non-IBM)
managed

For Build on Cloud Solution For Cloud only

Service
- Run / Manage /
Composition / Operate
Service Service Service
Integration
- Integrated Service
Management from SOC
2015 IBM Corporation
App Ops : Most common scenarios for Service Selection

DevOps Services Integrated Ops Services Security Services

For Most Cloud Native Consider Scenarios Custom Service

Applications the SOC Support of Selection based on
scenario DevOps for a One System compliance to
system one solution SOC Support Customer
for all components should for Portfolio Specific Policies
be used T-Shirt Size can be Data Privacy
T-Shirt Size can be selected based on App Requirements
selected based on App Ops Guidance further Budget
Ops Guidance further

T-Shirt Sizing and Pricing for selected scenarios is available as part of App Ops on Cloud Demand
Profile

2015 IBM Corporation

 ARCHITECTURE TEMPLATE GUIDANCE

2015 IBM Corporation

 2. Web & Mobile App with MicroServices Architecture
Adapt Application Architecture https://www.ibm.com/devops/method/content/architecture/implement
ation/web_mobile_e2e_scenario
Templates

3. Microservices invoking SOR via messaging

https://www.ibm.com/devops/method/content/architecture/implement
ation/arch_omni_messaging_imp

1. Omnichannel Architecture
https://www.ibm.com/devops/method/content/architecture/omnichannelArch
itecture

2015 IBM Corporation

Adapt Application Architecture Templates (contd.)
Reference Architecture : MicroServices Application

2015 IBM Corporation

 API SOLUTIONS : TYPICAL TECHNOLOGY STACK

Integrated Operations App Ops On Cloud Tool Stack

Securi Integr API Gateway

ty ation

Self Service Portal IBM API Connect

API Management

Implementation Runtimes (Node.js, Websphere Liberty Profile)

Testing DevOps Bluemix Continuous Delivery

Management & Monitoring

App Ops On Cloud Tool Stack

Hybrid Cloud Platform

2015 IBM Corporation

 MICROSERVICE APPLICATIONS : TYPICAL TECHNOLOGY STACK
Integrated Operations App Ops On Cloud Tool Stack

IBM API Connect

Security IPC API Gateway
SSO Message
Hub Eureka
Proxy Circuit Breaker
Hystrix

BFFs
Runtimes (Node.js,
Websphere Liberty Profile)
MicroService Business API

Persistence Mongo / Cloudant / DashDB

ETL Lift / Data Connect

MicroService Application

Testing DevOps Bluemix Continuous Delivery

Management & Monitoring

App Ops On Cloud Tool Stack

Hybrid Cloud Platform

2015 IBM Corporation
 BACKUP/ OLD SLIDES

2015 IBM Corporation

 PAAS BASED TECHNOLOGY STACK

Small Medium Large

API Gateway 100K API Calls / Month Upto 5 M API Calls / Month Upto 25M API Calls / Month
(IBM API Connect )
Proxy
BFF 200GB Hrs. 500 GB Hrs. 700 GB Hrs.
MicroService Application API 360 GB Hrs. 700 GB Hrs. 1000 GB Hrs.
Persistence Technology 500 GB 1 TB 1 TB
IPC - Messaging
Single Sign On

2015 IBM Corporation

 APP OPS ON CLOUD: END TO END VIEW OF SOLUTION COMPONENTS

Application Design a) Application 1

Cloud Application Support
& Development Support

b) Solution Operations Center, Delivery

GBS Application Operations Management, Help Desk, Service 2
6 Reporting
i) Managed Services Platform (joint
solutioning between GBS / GTS and
IBM Cloud) IaaS Platform & Operations PaaS
Platform &
Operations

GBS DevOps Services

GBS Middleware Service Management
4

Managed Security
h) Middleware Managed Services

Servics
c) Bluemix Platform supported by Cloud (per
g) Infrastructure administrative support MSA)
and maintenance GTS IMI Infrastructure Service Management

f) Bluemix Infrastructure supported by Softlayer GBS

Cloud (per MSA being negotiated)
(infrastructure, network, co-lo)
GTS

Security
e) DevOps engineering of continuous
test and deployment platform d) Security tools deployment and
5
3 Cloud
management (AA to assume monitoring
responsibility Bluemix Garage

Solution Components owned & delivered by GBS Non-GBS solution components created collaboratively

2015 IBM Corporation

Build on Cloud : Overall Solution Flow
A Functional + Technical B Operational C Contractual
Initiate
GBS Solution Run manage
1 1
Architect Define / Adapt Technical Solution Select Platform T-Shirt Size Required ?

Y
2 Select Application T-Shirt Size for Delivery
N BAFO Price
Submission?

Y 1 Adapt RACI Template

2 Calculate Platform ROM Price

Cloud Platform 3 Provide Platform Firm Price

2 Agree on DOU / RACI
Seller

4
Create Addl Solution Artifacts
Estimate Appl Maintenance effort (as reqd by SIH/IOT)
Adapt Staffing Plan 4
3
(based on template) Complete SIH/IOT Reviews
GBS Solution 5
Manager
Adapt Delivery Plan w Scope/Sprint
4 (based on Template) 6 Finalize SoW / Proposal etc

Provide summarized cost inputs for

7 Pricing

Complete
Select Platform Management T-Shirt Size
Platform Mgmt. 5
Team
(GTS) Provide Platform Management Price 3 Agree on DOU / RACI
2015 IBM Corporation 6
 A Functional + Technical B Operational B Contractual
Initiate
1 Collect Volumetric Attributes
1 Determine Functional Scope/Attributes

2 Select Platform T-Shirt Size

2 Determine Technical Attributes
GBS (incl. non functional)
Solution Define Application Architecture 3
N BAFO Price
Calculate Platform ROM Price Submission?
Architect 3 (using Template + Guidance)

4 Select MW Management Size Y

4 Estimate Effort point using Guidance

Select Delivery Team T-Shirt Size 5 Select DevOps Services Size Tailor RACI Template
5 1
(based on Effort Points)

Complete ITDA Reviews 6 Select Security Services

6
Cloud
Platform 7 Provide Platform Firm Price 2 Agree on DOU / RACI
Seller
4
Create Addl Solution Artifacts
(as reqd by SIH/IOT)
GBS 7 Create Staffing Plan
(based on template) 8 Select Integrated Ops Size Complete SIH/IOT Reviews
Solution 5
Manager Create Overall Delivery Plan
8 6 Finalize SoW / Proposal etc

Provide summarized cost inputs for

7 Pricing

Complete
Select Platform Management T-Shirt Size
Platform 9
Mgmt. 3
Provide Platform Management Price Agree on DOU / RACI
Team(GTS) 2015 IBM Corporation 10