[Vietnam Mobile Day 2013] - Mobilization process for enterprise

PRESENTER NAMEApril 13, 2023

MOBILIZATION PROCESSMobilizing Your Enterprise

© Copyright by FPT Software 2013

2

AgendaCritical success factor:

“Can someone who is on the move do his/her job with just a mobile device?”

Enterprise Mobility Roadmap1

Application Mobilization Process2

Application Mobilization Assessment3

Mobility Architecture Considerations4


3

ENTERPRISE MOBILITY ROADMAP APPLICATION MOBILIZATION PROCESS

Section 1


4

Enterprise Mobility Roadmap

Organization Enablement

Infrastructure Enablement

Business Enablement

• Enterprise Mobile Strategy & Roadmap

• Business Mobile Policy Development

• Enterprise Mobility Governance

Organization Enablement

• Mobile Device Management

• Mobile Device Security• Mobile Device Policy

Infrastructure Enablement • Mobile Device

Communication• Mobile Application

Management• Enterprise Application

Mobilization

Business Enablement


5

Application Mobilization Scenarios


Desktop web browser is available => Need for mobile browser interface.

Desktop Windows application is available =>Need for a native iOS and Android app.

iOS application is available=> Need for a complementary Windows Phone app;

Nothing is there yet =>Needs for a cross platform mobile application with native user experience.

Real life application

mobilization scenarios

6

Readiness & Planning• Objectives

Assessment readiness and program planning

• OutputsReadiness Report, High Level Plan, etc.

Assessment• Objectives

Analyze and define program details

• OutputsAssessment Report, Platform & Architecture Selection, etc.

Implementation• Objectives

Design and implement applications

• OutputsArchitecture & Detailed Design, Application Package, etc.

Support• Objectives Maintain

and support program

• OutputsSupport Service, Knowledge Base, etc.

Application Mobilization Process


7

Application Mobilization Process

Readiness & Planning• Business case analysis• Review existing

mobile data, device, application and document strategy

• Roles and responsibilities

• Success criteria• Program scope• Communication plan• Target technologies

and solutions• High level roadmap• Program plan in place• Launch approach

Assessment• Categorize applications• Prioritize applications,

select top mobilization candidates

• Infrastructure coordination

• Conduct a proof of concept optimization

• Verify and course correct process

• Launch refined process• Business case

confirmation• Program plan revise if

necessary

Implementation• Mobile application

development optimization, replacement or redesign

• Requirement specifications

• Factory development iterations

• Test iterations• Final inspection and

result validation• Train the trainers• Final production

rollout

Support• Support and

maintenance• Continued monitoring

for compliance and segregation of duties

• Survey success and areas to improve

• Continue to add functionalities

• Maintain systems and processes to address new user requirements


8

APPLICATION MOBILIZATION ASSESSMENTSection 2


9

Assessment Approach


Scoping Assessing

Platform & Architecture Selection

Prove of Concept

Defining Strategy

Reporting

10

Defining StrategyDefine the customized mobilization assessment strategy and methodology based on current situation and need.


Analyze the current situation and needs

for mobilization

Establish the mobilization assessment strategy and methodology

•Define the communication & interview plan/approach•Define the awareness approach for

application owner/users/etc.•Define the approach to rate application

complexity•Define/customize the tentative templates

for all required deliverables (i.e. Application Inventory, Assessment Report, etc.)•Approach /plan to produce the required

assessment result (i.e. RASCI Model, etc.)

Revise and update the strategy and

methodology along the way

11

Scoping & Assessing


Scoping Assessing

Establish the initial scope and collect initial data for assessment.

Understand the context and complexity of applications to provide

concrete estimation.• Application Inventory Establishment Application Inventory from ITPM Communication with application

owners• Initial Data Collection• Scope Confirmation

• Manual Assessment Analyze documents, collected data and

interview results Evaluate the application complexity,

Categorize and Prioritize applications Identify and Suggest valid target

platforms and application architecture• Estimation

From POC, derive challenges and risks which contribute to the estimation

Establish estimation norms for each complexity level and each application

12

Platform & Architecture Selection

• Investigate and Analyze mobile strategy to Identify the target platforms• Identify the high level architecture of mobile applications for such

platforms• Identify the approach, criteria and decision tree for target platform and

architecture selection

Identify approach for mobile platform and architecture selection.


13

Deliverables

Application Inventory• Lists all applications in scope of mobilization assessment• Contains collected information & analysis results• Contains raw data sheets for pivoting and analysis• Contains predefined reporting sheets

Assessment Report• Contains all analysis result of assessment phase• Includes summary of the final application inventory with all analysis reports• Includes the tentative implementation plan• Accompanies with FPT’s quotation for mobilization service

Platform & Architecture Selection• Identifies all mobility platforms in scope• Identifies all high level application architecture in scope• Defines the criteria and rules for platform & architecture

selection

Input Target Application

Is it business critical?3.4.3.6

Does it conform to SharePoint

capabilities?3.4.1

No

dSPACE 2010 dWeb PHP DAP

Yes

Yes

NoIs it web publishing?

3.4.3.4

Yes

No

Is it heavily data centric? 3.4.3.2

Yes

No

Is it collaboration?3.4.3.1

Yes

NoIs it heavily enterprise

or process centric?3.4.3.3/5

Yes

Is it complex process centric

3.4.3.3

Additional MESH

Yes

NodWeb Java


14

Customer Involvements

• Customer to provide any related documents and information for assessment readiness and planning.

• Customer to allocate suitable resources to actively work with FPT to achieve assessment results including mobility managers, architects, application managers, coordinators, etc.

• Customer to provide the initial scope of applications to perform mobilization assessment.

• Customer to actively participate into the assessment process to review and ensure the results are as expected.

• Customer to provide access to corporate network, infrastructure, knowledge based and any related information stores as required by assessment exercise.


To ensure a successful assessment phase, the following customer involvements must be required:

15

MOBILITY ARCHITECTURE CONSIDERATIONS

Section 3


16

General Architecture

Application/ERP ServersDatabase Systems

MiddlewareMobile Service Gateway

Wireless Networks

LAN/Internet


17

Deployment Model

SAMPLE


18

Cross Platform

Server Processing

No Video

Little OS Integration

No Camera

Online Mode

Easy Distribution

Extensive Reach

High Portability

Geo-location

Camera

OS Integration

Video

Unique Distribution

Limited Reach

Browser-Free

Zero Portability

Offline Mode

Manageable Rich UX

Manageable and Rich UX

Online and Offline

Mobile Web App

Resident Mobile App

Hybrid App


19

Cross Platform Dimensions

Application Deployment

Static

Dynamic

Mixed

Application Runtime

Operation System

Browser

Container

Virtualization

Code Partitioning

Device

Mixed

Server

Data Residency

Device

Mixed Cache

Mixed Unsync-ed

Mixed Sync-ed

Server


20

Other Considerations


Connectivity & Storage

Data compression “over the air”

Server and local cache implementation

Least amount of data possible on mobile devices

Data synchronization scenarios based on connection speed

Preference of light weighed standards(i.e. REST over SOAP)

Deployment

Public:• Generally available in the default App

Stores• Suitable for B2C apps

Public with activation:• Generally available with pass code/PIN

activation• Suitable for non critical applications

Private:• Publish and available through the

Enterprise Store• Deployment and management through

MDM/MAM solutions• Suitable for highly matured enterprises

21

Other Considerations


Security

Match authentication mechanism to information risk on a per-use-case basis

Industrial standards for channel security (i.e. SSL)

Device lock, remote wipe, encryption, etc. as a part of MDM solution

Practices

Focus on user experience design;

Simple apps do one thing well, not a portal experience;

Employ commercial service gateway/middleware solutions;

Information Risk

Stronger Authentication

Solution

High Required Hardware OTP, Smart Card

Medium Required Software OTP, Out-Of-Band

Low Not Required Username/Password, OAuth

No single solution/architecture for mobile application development

Single point of control over application deployment & life cycle management

22

Technology

[Vietnam Mobile Day 2013] - Mobilization process for enterprise