top 10 considerations for upgrading ca user group meeting l.
Download
Skip this Video
Download Presentation
Top 10 Considerations for Upgrading CA User Group Meeting

Loading in 2 Seconds...

play fullscreen
1 / 83

Top 10 Considerations for Upgrading CA User Group Meeting - PowerPoint PPT Presentation


  • 102 Views
  • Uploaded on

Top 10 Considerations for Upgrading CA User Group Meeting. Romeo Sequeira. Why Upgrade?. Periodic Application Refresh . Proactive Application Management. Regular Applications Value Reviews. Competitive Opportunity. Practical Competitive Optimum. Status Quo. Go Live. Competitiveness.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Top 10 Considerations for Upgrading CA User Group Meeting' - tayten


Download Now An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
proactive application management

Periodic

Application

Refresh

Proactive Application Management

Regular Applications Value Reviews

Competitive

Opportunity

Practical Competitive Optimum

Status Quo

Go Live

Competitiveness

Competitive Erosion

Time

By harnessing the power of new technology, you can achieve competitive advantage

slide4

Can customizations be reduced ?

Can upgrade provide new business value?

Productivity

Cost

Upgrade Cost Drivers

Business justification examines the overall impact to your organization’s performance

benefits of upgrading
Benefits of Upgrading

Take advantage of new functionality

Reduce customizations

Reduce operational costs

Respond to globalization and consolidation needs

Increase user productivity

Ensure compliance

Optimize application and system performance

Drive lean principles throughout the organization

value of upgrading
Value of Upgrading

According to Aberdeen Group, Best-in-Class manufacturing companies are 35% more likely than Laggard companies to operate on a current version of ERP.

slide8

global

platform

Munich

domains

Shared Services

Sarbanes-Oxley Compliance

Enterprise Integration

Flexible global Deployment

Common Data

Global Governance

Interoperability & Integration

Washington

Tokyo

Rio de Janeiro

Sydney

slide9

total enterprise

capability

Enterprise Resource Planning

Enterprise Asset Management

Product Lifecycle Management

Demand ManagementCustomer Relationship Management

Service and Support Management

Transportation Management

Product Information Management

slide10

human

engineering

.NET User Interface

Data AccessIntegration

Consistency

Roles

Process

recent enhancements new modules
Recent Enhancements, New Modules

2007

MANUFACTURING

EXECUTION

WORKBENCH

JUST-IN-TIME

SEQUENCING

TRANSPORTATION

MANAGEMENT

DESKTOP

SHIPPING

SALES FORCE

AUTOMATION

.NET UI

2007

MARKETING

AUTOMATION

QAD ENTERPRISE

APPLICATIONS 2007

recent enhancements new modules12
Recent Enhancements, New Modules

2008

GLOBAL

ENTERPRISE

EDITION

JUST-IN-TIME

SEQUENCING

ENHANCED

CONTROLS

MOBILE

FIELD

SERVICE

PRODUCTION

SCHEDULER

WORKBENCH

CONFIGURATOR

.NET UI

2007

DEMAND

MANAGEMENT

DISTRIBUTED

ORDER

MANAGEMENT

qad enterprise applications development
QAD Enterprise Applications Development

March

2007

September

2007

March

2008

September

2008

April 2009

2002

2005

MFG/PROeB2

MFG/PROeB2.1

QAD2007

QAD 2007.1

QAD2008 EE

QAD 2008 SE

QAD 2008.1 EE

QAD2008.1 SE

QAD2009 EEQAD2009 SE

QAD Standard Financials

Shared Services Domains

QAD Enterprise Financials (EF)

QAD Internationalizations

two versions of qad 2009
Two versions of QAD 2009
  • QAD 2009 Enterprise Edition (EE)
    • Includes Enterprise Financials
    • Also includes enhancements in other areas of Enterprise Applications, including Manufacturing & Distribution
    • New UI Shell version
  • QAD 2009 Standard Edition (SE)
    • Includes Standard Financials (as in eB2.1)
    • Equals QAD 2007.1 plus Service Packs
    • New UI Shell version
  • Differences in add-on availability and versions of add-ons
slide15

Upgrade

Considerations

top 10 considerations for an upgrade
Top 10 Considerations for an Upgrade
  • Technical Considerations
  • Business Considerations
  • Security Considerations
  • Implementation Considerations
  • Customization Considerations
top 10 considerations for an upgrade contd
Top 10 Considerations for an Upgrade (contd.)
  • Financial / Regulatory Considerations
  • Standardization Considerations
  • Reporting Considerations
  • Training Considerations
  • Tool Considerations
slide18

1. Technical

Considerations

18

technical considerations
Technical Considerations
  • Architectural
    • Number of databases
    • Number of domains
    • Options
      • Single database with multiple domains
      • Multiple databases with multiple domains
      • Single database with single domain
technical considerations20
Technical Considerations
  • Database and domains considerations
    • Strategy for points of failure (single or multiple)
    • Database maintenance or shutdowns strategy
    • Language considerations in the same database
    • How many sites are you willing to upgrade at once
    • Time zone considerations
    • What level of separation or granularity do you require
technical considerations21
Technical Considerations
  • Hardware considerations
    • Centralized, decentralized or hosted
    • Number of servers
    • Location of servers
    • Server size and capacity
    • Will existing infrastructure support the envisioned environments
technical considerations22
Technical Considerations
  • Data communication considerations
    • Network bandwidth
    • Network latency
    • Bridges between ISP providers
    • What UI’s will be running
    • What other applications will be running over the lines (telecom, radio frequency, email systems, and voice)
technical considerations23
Technical Considerations
  • Business Continuity strategy
    • Up time requirements and support strategy
    • Backup strategy
    • Fail over strategy
    • Disaster Recovery strategy
technical considerations24
Technical Considerations

Presentation

Exposed

Services

QXtend

EDI

Business Services

Data Access

Platforms

24

slide25

2. Business

Considerations

25

business considerations
Business Considerations
  • Is there a clear understanding of business drivers / objectives and reporting requirements (KPIs / Metrics) at all levels?
  • Measure baseline metrics before upgrade
  • What is the level of local autonomy versus central control?
  • Is there an understanding of internal supply chain requirements and flow?
  • Degree of change management or managing change that will be required
  • Is there a clear definition and understanding regarding shared services requirements ?
business considerations27
Business Considerations
  • The amount of business process reengineering that is envisioned to support initiatives such as Lean, Shared services, etc.
    • Customer Service Applications
    • Support Operations
    • Accounts Receivable
    • Accounts Payable
business considerations28
Business Considerations
  • Is there an understanding of what new functionality is available or net change from legacy version
  • Will there be new features and functionality the business will be taking advantage
    • Enhanced security
    • CRM
    • Lean manufacturing
    • PIM
    • Production schedulers
    • EAM
    • DOM or CSS
    • Configurator
    • Warehousing
slide29

3. Security

Considerations

29

segregation of duties sod
Segregation of Duties (SOD)

Objective

Limit the duties of individuals to certain areas of responsibility

Minimize the ability of any individual to misappropriate company property – without collusion between individuals

Specify roles that are conflicting from a segregation of duties perspective

Identify users that have any access rights that are part of conflicting roles

User

Conflicts

Role A

Access right

Access right

….

Role B

Access right

Access right

….

segregation of duties sod31
Segregation of Duties (SOD)

Partition all activities (menu options) to only one category

Define sets of categories that are mutually exclusive

No individual can have access privileges to functions that are defined as being mutually exclusive

Establish rules and verify no violations

Rule 1: Activities granted to a role must belong to compatible SOD categories

Rule 2: User roles must have compatible SOD categories

role based security
Role Based Security

All application security in QAD 2009 EE is role based

Roles are defined for each discrete area of the business using Segregation of Duties concepts

Roles are linked to menu functions using Role Permissions

Users are assigned access to Domains and Entities

Users are assigned to roles for Entities and Domains

business considerations33
Business Considerations

Define Roles and Permissions

Segregation of Duties:

Define conflicting roles

User Interface depending on Role

role membership
Role Membership

Users will typically be assigned more than one role

Users may have different roles in different Domains/Entities

default roles and permissions
Default Roles and Permissions

Default set of pre-defined roles and permissions supplied with QAD 2009 EE

Around 80 roles are already defined

Roles are defined using Segregation of Duties Principles

Separate role for PO creation and PO receipt

Separate roles for supplier creation, supplier invoice recording and supplier payments

Separate roles for inquiry access by functional area

Tools provided for the automatic loading and editing of default roles and permissions

XML integration already available

slide36

4. Implementation

Considerations

36

implementation considerations
Implementation Considerations
  • Is this project considered a new implementation, technical upgrade or is it a reimplementation
    • Will a business process assessment (BPA) be required
    • Will business process reengineering (BPR) be required
  • Is this project a “Lilly pad” for another upgrade – If so how can it be positioned for the next upgrade
upgrade scenarios
Upgrade Scenarios

Technical Migration with data conversion

Customization

Data

Conversion

Small

Process

Changes

Optimization

Technical Migration without data conversion

Optimization

Conversion

Data

Load

Small

Process

Changes

Re-Implementation

Re-define Business Processes

Non-Intrusive

Customizations

Data

Load

38

centralize standardize first
Centralize/Standardize First

QAD 2007QAD 2008 Standard Edition

QAD MFG/PRO

8.6, 9.0, eB, eB2

QAD 2009 Enterprise Edition

ERP

Database

Plant 1

ERP

Database

Plant 1

ERP

Database

Plant 1, 2 and 3

ERP

Database

Plant 1, 2 and 3

ERP

Database

Plant 2

ERP

Database

Plant 2

ERP

Database

Plant 3

ERP

Database

Plant 3

39

migrate first to qad 2009 enterprise edition than centralize and standardize
Migrate first to QAD 2009 Enterprise Edition, than Centralize and Standardize

QAD MFG/PRO

8.6, 9.0, eB, eB2

QAD 2009 Enterprise Edition

ERP

Database

Plant 1

ERP

Database

Plant 1

ERP

Database

Plant 1, 2 and 3

ERP

Database

Plant 2

ERP

Database

Plant 2

ERP

Database

Plant 3

ERP

Database

Plant 3

40

q advantage implementation methodology
Q-Advantage Implementation Methodology

Plan

Design &

Configure

Test &

Accept

Deploy & Evolve

Implement

Manage

Complete Process

& Technical

Design

Complete Final

Data Load

Kick-off Project

Train

End Users

Agree on

Business Process

Solution Design

Train Core Team

Complete Data

Validation &

Functional Testing

Execute Cut-Over

Plan

Agree on Project

Controls

Build System, Scripts &

User Procedures &

Convert Data

Complete System

& Performance

Testing

Post-Launch

Evaluation

Conduct

Stakeholder

Validation Session

Manage

Applications &

Support

Develop, Deliver

& Test

Custom Solution

Agree on Project

Plan & Resources

Determine Core

Model / Rollout

Requirements

Develop Cut-Over

& Deployment

Strategy

Validate / Refine

Solution

via CRP Cycles

Adjust Core Model

& Rollout Plan

Communication & Change Management

Program & Project Management

41

slide42

5. Customization

Considerations

42

customization considerations
Customization Considerations
  • The number and types of customizations to the legacy system
    • Is there a definitive list of customizations
    • Is there an understanding of who owns each customization
    • Is there an understanding of what each customization does.
    • A go forward review and migration strategy for all customization will be required
    • Remember - every customization in a multi domained database will have to be domainized
customization considerations44
Customization Considerations
  • API’s and interfaces to 3rd party software
    • Needs to be fully identified and go forward strategy developed.
  • Is it within scope to update 3rd party software solutions
customization considerations46
Customization Considerations

Maintenance

Reports

CUSTOMIZATIONS

46

customization considerations47
Customization Considerations

Customizations Not Used

Maintenance

Reports

CUSTOMIZATIONS

47

customization considerations48
Customization Considerations

QAD Enterprise Applications 2009 EE or SE

Customizations Not Used

Maintenance

Reports

CUSTOMIZATIONS

48

customization considerations49
Customization Considerations

QAD Enterprise Applications 2009 EE or SE

QAD.NET User Interface

Customizations Not Used

Maintenance

Reports

CUSTOMIZATIONS

49

customization considerations50
Customization Considerations

QAD Enterprise Applications 2009 EE or SE

ICT

QAD.NET User Interface

Reports

CUSTOMIZATIONS

50

customization considerations51
Customization Considerations

Always make sure that the domainization has been done on the customization to be migrated before starting the Realization

Do not just compile your old programs against the new database

Not even reporting!

Make sure you are trained in the Data Model of the new release (be aware of the changes related to add-on modules)

Always consider ICT as alternative

51

financial regulatory considerations
Financial / Regulatory Considerations
  • Do current polices, practices and system utilization optimally meet requirements
    • SOX requirements
    • IFRS requirements
    • US GAAP reporting requirement
    • Local regulatory reporting requirements
    • Tax reporting requirements
    • FDA validation requirements
    • ISO compliance
financial considerations
Financial Considerations
  • Do current policies, practices and system utilization optimally meet requirements and what is the impact of an upgrade?
  • Will documentation have to be updated?
  • Financial reporting and consolidation
    • Is current entity configuration and reporting satisfactory
    • Are the financial consolidation toolsets adequate or will it be replaced or upgraded
    • Is QAD’s enterprise application 2009 in your upgrade plans
qad internationalization
QAD Internationalization

Compliance with laws and business practices across the globe

Example audit files:

Argentina

Brazil

Columbia

Venezuela

Spain

Portugal (SAF-T)

Germany (GDPdU)

China

slide57

7. Standardization

Considerations

57

standardization considerations
Standardization Considerations

Core models (for multi-site implementations)

Do core models exist today and if not should they?

Are the core models that exist today for both organic and acquisition growth being followed?

Is there a data standardization/normalization strategy and is data replication required?

What is the condition or state of your current data?

58

standardization considerations59
Standardization Considerations
  • Non-domained tables standardization
    • Users
    • Currency code
    • Country codes
    • Site codes
    • Entity codes
standardization considerations60
Standardization Considerations
  • Is there data standardization / normalization strategy and is data replication required
    • Chart of Accounts
    • Customers
    • Suppliers
    • Item masters
    • Bill of Material
    • Other master data
data replication solution
Data Replication Solution

QAD QXtend

Outbound

(QXO)

Domain 1

Domain 3

Master Domain

Domain 4

Domain 2

Domain 5

QAD QXtend

Inbound

(QXI)

Standardization Considerations

slide62

8. Reporting

Considerations

62

reporting considerations
Reporting Considerations

Ad hoc reporting

Inquiries

Typically a one-time request for data

Standard reporting

Typically run weekly, monthly, etc.

Fairly static in layout, query parameters, etc.

Can be run in batches and on a schedule

Forms and labels

Invoices, orders, etc.

Package labels, barcodes

BI reporting

Data Warehousing

Metrics/models

OLAP reporting

Requirement

Solution

.NET Browses

.NET Reporting

QAD BI

63

slide64

9. Training

Considerations

64

training considerations
Training Considerations
  • For the average user, QAD.NET UI training only is necessary for the new user interface.
  • For an organization with heavy use of Excel, advanced QAD.NET UI Browse training is advisable.
  • Consider Enterprise Financials as an implementation of a new module, so extensive training is necessary.
  • The ‘traditional operational’ module area needs minimal training effort during upgrade
  • IT training, especially for the new infrastructure, due to the QAD.NET solution requiring web technology.
slide68

10. Tools

Considerations

slide69

Tools

  • Domain Conversion Tool
  • Domain Merge Tool
  • Program Tracer Tool
  • Integrated Customization Toolkit (ICT)
  • QScan
slide70

Domain Conversion Tool

  • Purpose
    • Modifies a schema definition file to add domain to selected tables and indexes, and modifies simple schema validation statements
    • Goes through the Progress source code and modifies all search and create statements with the domain statement
  • Benefits
    • Reduces costs of manual update of the source set with the domain statement
    • Reduces the risks to get errors out of this manual process
source code transformation how it works
Source Code TransformationHow it Works

Read

Plug-ins

Read

Create

Find

Transform

Transform

Code Lines

fields

etc.

Write

slide72

Domain Merge Tool

ERP

Database

AR

ERP

Database

CO

ERP

Database

PE

ERP

Database

BR

ERP

Database

MI

ERP

Database

PR

ERP

Database

CL

ERP

Database

MX

ERP

Database

VE

AR

Domain

CO

Domain

PE

Domain

BR

Domain

MI

Domain

PR

Domain

CL

Domain

MX

Domain

VE

Domain

Single QAD QAD SE 2008 Database

slide73

Program Tracer Tool

  • Purpose
    • To identify what customized functions are actively used in your application
    • To identify how users are using your QAD applications
    • The results of the Program Tracer helps you to eliminate customizations and/or provide feedback on customization areas that needs review
  • Benefits
    • Eliminate unused functions from those to be migrated
    • Analyze how users use specific functions in order to improve the overall process
slide75

Integrated Customization Toolkit (ICT)

  • Purpose
    • The ICT Services Product enables you to develop customizations in a non-intrusive way
    • Eliminates or significantly reduces the need to change the standard source code set
  • Benefits
    • Decrease of development costs for initial developments and following upgrades of the customization
    • Enables customization without having the source code rights
    • Decrease implementation effort related to patches and services packs with impact on the customization
    • Easy to track changes and debug in case of issues
qad ict components

User Interface

Business Logic

Database

Security / Role Model

QAD Standards

Tracking & Tracing

Control & Debugging

QAD ICT Components

QAD Integrated Customization Toolkit

qscan process
QScan Process
  • Identify Pain Points
  • Develop Recommendations
  • Establish Metrics
  • Quantify Benefits
inventory control pain points issues
Inventory Control – Pain Points, Issues
  • High Inventory Levels for New Parts
  • No visibility of WIP Stock
  • Difficult to explain floor stock expenses on P&L
  • Machined parts in the warehouse not being used
  • Inventory counts not always accurate line shut down
  • Receipts take too long due to PO record locking
  • Warehouses – parts not identified properly
inventory control recommendations
Inventory Control – Recommendations
  • Implement
    • Develop Inventory Analysis Reports
      • Inventory Turns
      • Excess and Obsolete
      • Transaction Report
    • Implement Cycle Count/Inventory Control module:
      • ABC Classification designation
    • Extend the use of RF for all inventory movement transactions
    • Introduce Lean Concepts / Investigate MFG/PRO Lean module
    • Change the way Material Flow is organized in QAD
inventory control benefits
Inventory Control – Benefits
  • Better Control over New Parts Inventory  potential cost savings (actual inventory = $30million)
    • Reduce Line stoppages
    • Reduce expediting costs (freight)
  • Storing Parts:
    • Lower cost for warehousing space
    • Lower cost for handling stock (transport, labeling, pickup and putaway)
  • More efficient stock handling in the warehouse (bar coding)
ad