eCIO PPT Plan of Action for a Systems Integrations (SAP) Project

PROCESS OVERVIEW FOR

DEVELOPING A PLAN OF ACTION (POA) FOR A LARGE-SCALE SYSTEMS INTEGRATION (SI) PROGRAM

(DOC #: SI.PPT.OVR 001 V 0.6DRAFT FOR DISCUSSION PURPOSES)

EXECUTIVE LEVEL PRESENTATION

as of: April 15, 2013

Prepared for: • Project IT OCI’s• Those interested in understanding the systems integration

process

Prepared By: David Niles, Integration Program Manager, PCO

Page: 1Tuesday, May 2, 2023ECIO EXECUTIVE WORKBENCH

OVERVIEW

• Purpose of Todays Presentation– Provide a high level overview of the Project Systems Integration Efforts– Outline the steps and challenges in developing the System Integration

Plan for the Project– Identify the go-forward plan of action (WIP)

• Takeaways– Understanding of the timelines, touch points and potential impact on

“my” organization– Expression of any concerns/issues that “I” have ownership or oversight

to– Illustrate the hand-offs to the down-stream process of Application

Retirement/decommissioning of applications


1. Synopsis and Overview of the framework of an Systems Integration Plan– Definition & Purpose, Best Practices & Checklists– Integration, Risks and Metrics, Timelines– Integration & Verification Strategies

2. Systems Integration Plan of Action– Touch Points– By the N#mbers– The Challenges in developing the System Integration plan– The “Plan”

• Approach: “How do we get there from here?”• Preliminary Steps and Activities• Deliverables & Work products

3. Next Steps & Activities

AGENDA


• What we’re not going to address (out-of-scope)!– Funding/budgeting in support of Systems Integration– Risk & Issues Management Processes (separate Presentation)– Overall project management & governance– Applications Retirement (sun setting) process (separate Presentation)– Data Governance & Master Data Management (MDM) (separate Presentation)

• Following the K.I.S.S. principle– Detail discussions/ logistics involving systems development, architecture,

production release cycles etc. will be held in separate forums..• But “unresolved” topics will be added to the “parking lot”

• Questions?– Your expectations?

LEVEL SET EXPECTATIONS


• Systems Integration is the process of:– Assembling the constituent parts of a systems in a logical, cost-effective way, comprehensively

checking systems execution (all nominal & exceptional paths), and including a full functional check-out

– Assembling the various parts of system delivery including hardware/software (net new, decommissioning, use if existing)

• 1st purpose of an Integration Plan. – A project’s integration and verification strategy is closely tied to the design of the system and its

decomposition into sub-systems. – Whatever the project goals were, the Integration Plan needs to be structured to bring the

components together to create each sub-system and to bring the various sub-systems together to make the whole system.

• 2nd purpose– Describe to the participants the necessary work

• “How do we know we’re doing a SI plan correctly?”

PURPOSE OF AN INTEGRATION PLAN


“Systems should be audited against a Integration checklist to ensure conformance with recommendations”

Does the Integration Plan include and cover integration of all of the components and sub-systems, either developed or purchased, of the project?

Does the Integration Plan account for all external systems to be integrated with the system [for example, communications networks, field equipment, other complete systems owned by the agency or owned by other agencies]?

Does the Integration Plan fully support the deployment strategy. For example, when and where the sub-systems and system is to be deployed?

Are the integration steps defined in the Integration Plan consistent with the verification activities defined in the Verification Plan?

For each integration step, does the Integration Plan define what components and sub-systems are to be integrated? For each integration step, does the Integration Plan identify all the needed participants and define what their roles

and responsibilities are? Does the Integration Plan establish the sequence and schedule for every integration step? Does the Integration Plan spell out how integration problems are to be documented and resolved? . . .

CHECKLIST: CRITICAL INFORMATION/ BEST PRACTICES


INTEGRATION @ [SUB-SYSTEM AND SYSTEM LEVEL INTEGRATION]

• OBJECTIVE:– Integration is the process of successfully combining hardware and software

components, sub-systems, and systems into a complete and functioning whole.

• DESCRIPTION:– Integration is an iterative process:

• Integration planning starts when the project activities are first defined.• A complex project needs a written Integration Plan.. Integration activities are

driven by:– system requirements– internal interfaces within the system– external interfaces to legacy systems and the deployment strategy– Integration activities are performed iteratively along with verification.

• When Does Integration Occur?


WHERE DOES INTEGRATION TAKE PLACE IN THE PROJECT TIMELINE?

• Typical life cycle for integration planning• ASAP (Accelerated SAP Methodology) has references to steps necessary

for integration..– We will need a “blended” model!


KEY AREAS FOR INTEGRATION TOUCH POINTS WITHIN THEASAP METHODOLOGY

• Phase 1: Project Preparation– 1.7 Integrated Solutions Management

• Implementation Plan & Roll Strategy• Data Cleansing Strategy

• Phase 2: Business Blue Print• Phase 3: Realization

– Develop & Test Interfaces• Phase 4: Final Preparation• ….


INTERFACES & TOUCH POINTS (CONTEXT DIAGRAM)


• 35 Applications are currently defined as “in-scope” – 21 are scheduled for

decommissioning– 14 are undergoing some level of

revision• Per: XLS “….”

BY THE N#MBERS


VARIOUS TECHNOLOGIES, TOPOLOGIES, LANDSCAPESAND PROJECTS ARE EMPLOYED

– Mainframe– Distributed systems– Standalone– O/S– Middleware/transport– Databases & file systems

• IDMS end-of life– Hosting Environments


Challenge35 applications have been identified as in-scope Staffing needs and Impact

Impact of “extracting” functionality FROM applications..Training and documentation challenges

Governance in terms of change control, and influence

Strategies under consideration

Projects Influencing delivery E-portal, E-manifest, MDM, BTB et alChanges in interfacesOngoing systems modifications..

CHALLENGES/ ASSUMPTIONS AND CAVEATS


• Several practices to be understood and blended in– Release management– Software Configuration management (SCM)– Backup and Recovery– Production Cutover– Change Request– Technical environments– Testing Strategy & Plan– Service level Agreements (SLA’s), Operational level Agreement (OLA’s),

Underpinning Contracts (UC’s)– Performance and Capacity Planning– Etc..

OTHER PROCESSES TO BE VALIDATED AND/OR INTEGRATED


• Challenge: “Old” practices to be blended into “New” Processes– New Software applications– JIRA– MQ Series– Data Stage– Quality Stage– Rational Composer– Solutions Manager Test Workbench– SAP Quality Center by HP– CA Clarity– Endeavour

SYSTEMS SOFTWARE AND TOOLKITS


APPROACH

• Utilize the foundation of the ASAP methodology– Commercial off the shelf (COTS) Framework– Will need to blend with Organizational processes

• In concert with Infrastructure and architecture and systems development teams

• Link to solution deployment releases


• Information Discovery & background collection– Overviews, data set definitions, high level application flow

• Need to establish a consolidated Functional Baseline Universe• Blue Printing to ratify requirements (business)• Solution Mapping• Establishes and further defines additional background for the integration

work packages details

APPROACH“HOW DO WE GET THERE … FROM HERE?”

Can I see a

picture?


REQUIREMENTS AND MAPPING TO INTEGRATION

Legacy Applications Functionality

Decommissioned Legacy Applications

PSCD Core Features

Other Solution Sets (In/out of

scope of Project)

Other Technologies

Core Requirements


SYSTEMS INTEGRATION: AREAS REQUIRING FOCUS

Other Solution

Sets (In/out of scope of <Project>)

Other Technologies

<Project> Core Requirements

Integration Focus: Areas Of Concern

Infrastructure


• Estimate the work efforts to “extract” functionality from that release• Continued Development of the IT Roadmap (integration)• Follow a standard release development cycle

– Data sets Single Point of Truth (SPOT) Investigation


SCHEDULE


• Illustrative example of early stages of work package scheduling

• Continue to drill down

POTENTIAL SCHEDULE COMPLEXITY

Business Functionality

Remove Functionality

Decommissioning


ROLES & WORKING RELATIONSHIPS

• Systems Integrations Manager– Responsible for facilitation and guidance with the applications

owners/managers and Organizational POC (points of contacts) • Integration Team

– Integration POC for each application– Business Integration

• Development teams


• Integration Master Plan of Action• Work package by release

– Applications detailed– Infrastructure affected– Build Plans

• Other related documentation– Testing strategy– Migration Strategy– Decommissioning strategy

DELIVERABLES


25

INTEGRATION MASTER PLAN OF ACTION TOC

• Some sections will reference other documents, as the SPOT• Posted on Project library

– Confluence when approved


INTEGRATION BUILD PLAN(S)

• Objectives– A brief description of the purpose of the Integration Build Plan.

• Scope– Brief description of what the Integration Build Plan applies to; what is affected or

influenced by this document.• References

– A list of related or referenced documents.• Subsystems

– State subsystems to implemented in this iteration. Also stated are the preferred order in which the subsystems should be implemented to be ready in time for integration.

• Builds– The integration (in the iteration) is divided into a number of increments, each

resulting in a build, which is integration-tested. This section specifies which builds to create and which subsystems should be part of each build.


ENSURING SYSTEMS INTEGRATION & TRACEABILITY

Files Systems

Applications(s)

Interfaces

Business Goals,

Objective, Work

Packages

Blue Printing,

Fact Finding & Discovery

Traceability Traceability

ArchitectureFunctionality, Requirements Added

Functionality, Requirements Deleted


Tuesday, May 2, 2023

APPLICATION COLLECTION PROCESS

ECIO EXECUTIVE WORKBENCH Page : 33

Tombstone DataStrategic Value

OwnershipUser Community

Risk ProfileAssociated Events

Applications Quality


APPLICATION PROFILES


Strategic BucketsStrategic Intentions

Functions Supported


FUNCTIONAL PROFILE: E.G. CONFIGURATION MANAGEMENT


Tombstone DataRoles

Goals, KPIs, Performance IndicatorsInputs/Outputs

Process Activities


FUNCTIONAL PROFILE: CONFIGURATION MANAGEMENT


TemplatesAssociated documentation

Supporting ApplicationsRelated Contracts/Agreements

ServicesRelated Functions

Terms & Definitions

• Continuation of the collections of legacy artifacts– Backgrounds– Application profiles, CMDB

• Validate requirements from other Internal and external departments and expected lead times– Standards, Guidelines, Policies, Procedures, Work Instructions

• Incorporate any milestones/deliverable dependencies from other projects touch points

• Continue refinement of the Integration POA (WIP)

NEXT STEPS AND ACTIVITIES


..Questions?

¿Conclusion…


FUTURE STATE


Tuesday, May 2, 2023ECIO EXECUTIVE WORKBENCH

PRESENTERS BACKGROUND

• David Niles ([email protected])– Director, Systems Development

• USA Federal Government Health Care, Washington DC– Director Enterprise Infrastructure

• Sanmina-SCI Contract Manufacturing, San Jose CA, Huntsville AL• Largest Oracle ERP instance in the world… HSV Z series, Superdomes

– Director, Project Control And Service Management• Sanmina-SCI, Chennai India Guadalajara MX• Mergers and Acquisitions, DRP, SOX, GSC, PMO

– Sr. Director Support Services• Burlington Coat Factory, Philadelphia PA • Change Control, GSC, Asset Management, Field Services, Technical Services,

PMO– Program Director, Day 2 Wipro– Special advisor, CIO/COO Macmillan Publishing NYC

Page: 40

mailto:[email protected]


TOOLKITS USED IN THE ASSISTANCE FOR COLLECTION OF INFORMATION

• Mindmap• eCIO Executive Workbench

– Toolkit and examples for all facets of the workplace for managers, executives and the individuals contributor

– Leave your card and I’ll get you a copy

Page: 41ECIO EXECUTIVE WORKBENCH


END OF PRESENTATION

Page: 43ECIO EXECUTIVE WORKBENCH

Date post:	11-Apr-2017
Category:	Documents
Upload:	david-niles
View:	279 times
Download:	1 times

eCIO PPT Plan of Action for a Systems Integrations (SAP) Project

Documents