1the process of combining different subsystems or components of
a larger system into a unified whole
System Integration
2the specific kind of enterprise systems to integrate
data across and be comprehensive in supporting all the major functions of the
organization
Integrated Program Planning
3Integration is a cornerstone of today's enterprise environments with their multitude of
enterprise resource planning (ERP) systems.
Enterprise Resource Planning (ERP) system
4a standard messaging protocol that
operating systems use to communicate via Hypertext Transfer Protocol (HTTP) and
Extensible Markup Language (XML).
Simple Object Access Protocol (SOAP)
5REpresentational State Transfer (REST)
conforms to the constraints of REST
architectural style and allows for interaction with RESTful web services and was created
by computer scientist Roy Fielding.
6systems leverage the principles of REST for creating scalable, simple,
and interoperable web services.
RESTful
7EVOLUTION OF ENTERPRISE SYSTEMS (5)
-INVENTORY MANAGEMENT AND CONTROL
-MATERIAL REQUIREMENTS PLANNING (MRP
-MANUFACTURING REQUIREMENTS PLANNING (MRP II)
-ENTERPRISE RESOURCE PLANNING (ERP)
-EXTENDED ENTERPRISE RESOURCE PLANNING (ERP II)
8most organizations designed silo systems
for their departments. As the production department grew bigger, with
more complex inventory management and production scheduling,
INVENTORY MANAGEMENT AND CONTROL
9which mainly involved planning the product or parts
requirements according to the master production schedule.
MATERIAL REQUIREMENTS PLANNING (MRP)
10emphasis on optimizing manufacturing processes, included such areas as shop floor and distribution management, project
management, finance, job-shop scheduling, time management, and
engineering.
MANUFACTURING REQUIREMENTS PLANNING (MRP II)
11To provide an integrated
solution to the increased complexity of businesses and support
enterprises
ENTERPRISE RESOURCE PLANNING (ERP)
12providing back-end support for such electronic business functions
as business-to-business (B2B) and electronic data interchange (EDI).
EXTENDED ENTERPRISE RESOURCE PLANNING (ERP II)
131. Identifying the target data is an important first step
2. A transaction is an atomic unit of work
3. The firewall is needed in or while the processes
4.Connectivity and security constraints should be identified and verified early on in
the project.
5. SOAP interface that allows for the typical data operations
Those are true
14allows organizations to share data with all of their
stakeholders based on their needs and authorization.
Logical System Integration
15provides seamless connectivity between heterogeneous
systems
Physical System Integration
16software that provides the appearance of seamless data presentation to
the end user and maintains data integrity and synchronization within each application
system database.
Middleware
17inability to meet the market demand effectively can have
unfortunate consequences
Program Integration
18STEPS IN INTEGRATION SYSTEM (8)
1. Resource Categorization
2. Compliance and Standards
3. Legacy Systems Support
4. Middleware Tools
5. Authentication and Authorization Policies
6. Centralized IT Services and Help Desk Support
7. Backup, Recovery, and Security Policies
8. Hardware and Software Standardization Policies
19Take an inventory of the various hardware and software resources focusing on
vendors, operating systems platform, IS architecture used in these resources.
Resource Categorization
20Check whether the database and other technologies used in various applications
are such supporting standards as JDBC/ODBC compliance for databases.
Compliance and Standards
21Develop a policy in support of older legacy applications.
Legacy Systems Support
22most organizations will not dispose of their old system right away for systems integration. These tools are essential for
integration in the short term
Middleware Tools
23Develop a single sign-on policy for application and data access because all
employees and external partners will need access to an integrated system from
anywhere, anytime.
Authentication and Authorization Policies
24Instituting IT support for an integrated systems environment is necessary to avoid
support and maintenance problems with the integrated system
Centralized IT Services and Help Desk Support
25Planning data and disaster recovery for organization’s data in an integrated
system IT is crucial for building the trust and confidence for the new system
Backup, Recovery, and Security Policies
26Develop organization standards and policy on acquisition of new hardware and
software which are aligned with organization IT strategy.
Hardware and Software Standardization Policies
27Benefits of System Integration (4)
Increased revenue and growth
Leveling the competitive environment
Enhanced information visibility
Increased standardization
28Limitations of Systems Integration (4)
High initial setup costs
Power and interdepartmental conflicts
Long-term and intangible ROIS
Creativity limitations
29Responsible for ensuring that project teams are
working well together and addressing functionality issues in a timely, open, and efficient
manner. It works through the business processes that will be involved in the execution
based on the project’s goals
Project Management Office (PMO)
30CRITICAL SUCCESS FACTORS (4)
Decision-Making Process
Project Scope
Teamwork
Change Management
31A well-defined decision-making process will minimize a number of issues
related to scope, efficiency, and productivity throughout the project
implementation cycle.
Decision-Making Process
32The project manager has many responsibilities. Scope defines what needs to be delivered by the project, and a changing scope means the project will have difficulty in achieving project goals
Project Scope
33Each team will have its own set of forces at work based on the knowledge
and character of the individuals involved.
Teamwork
34Communication and training are the keys to a successful change
management effort
Change Management
35TECHNICAL PERFORMANCE MEASUREMENT TECHNIQUE (3)
Implementation Team and Executive Team
Managing Scope Creep
Implications for Management
36The program manager and the project manager are critical to a successful
ERP implementation, but there are other groups that are also critical to
that success.
Implementation Team and Executive Team
37 well-thought-out process to manage changes to scope is critical to a
project’s success
Managing Scope Creep
38managing these changes through a change process and governance
Change Control
39consists of a description of the issue or new functionality, including the options available with advantages and
disadvantages
White paper
40-The success or failure of a project often rests with the skills and abilities of
the PMO
-PMO must monitor a number of activities and issues throughout the
length of the implementation.
-Hiring and selecting skilled and competent staff
Implications for Management
41The ERP implementation’s success depends significantly on redesigning
processes rather than customizing.
Customization is expensive
Those are true
42It is the process of developing new information that basically includes a
systematic process of planning, designing, and creating an information system
for organizations
SYSTEM DEVELOPMENT LIFE CYCLE (SLDC)
43It provides a structured top-down problem identification and bottom-up solution
process for managing complex problems
SYSTEM DEVELOPMENT LIFE CYCLE (SLDC)
44PHASES OR STAGES OF TRADITIONAL SDLC (5)
System Investigation
System Analysis
System Design
System Implementation
System Operations and Maintenance
45consists of system investigation, analysis, design, implementation,
and operations maintenance.
Maintenance Cycle
46consists of system design and system implementation only.
Testing Cycle
47-Determine whether a business problem or opportunity exists
-Conduct a feasibility study to determine whether a new or improved
information system is needed.
System Investigation
48Analyze in detail the information needs of end users, the organizational
environment, and any system presently used
System Analysis
49Develop logical input, processing, output, storage, and control., Develop specifications for the hardware (machines and media), software
(programs and procedures), people (specialists and end users), data
resources
System Design
50Acquire (or develop) and install hardware and software
Test and document the system
Train people to operate and use the system.
Convert to the new system
System Implementation
51Use a postimplementation review process to monitor, evaluate, and modify
the system as needed.
System Operations and Maintenance
52THREE MAJOR ERP IMPLEMENTATION PLAN CHOICES (3)
Comprehensive
Middle of the road
Vanilla
53It involves implementation of the full functionality of the ERP software in
addition to industry-specific modules.
Comprehensive
54It involves some changes in the core ERP modules and a significant
amount of BPR
Middle of the road
55It utilizes core ERP functionality and exploits the best practice business
processes built into the software
Vanilla
56TRADITIONAL ERP LIFE CYCLE (5)
Stage 1 : Scope and Commitment Stage
Stage 2 : Analysis and Design Stage
Stage 3 : Acquisition and Development Stage
Stage 4 : Implementation stage
Stage 5 : Operation stage
57conducting the feasibility study, and a number of task parameters or characteristics of the ERP implementation need to be defined at the planning stage.
Scope and Commitment Stage
58 creating plans for data conversion, system conversion, and training. the team must develop a detailed change management strategy and plan for the release of the new system
Analysis and Design Stage
59The organization has to purchase the license for the production version of the
software and build the production version of the system
Acquisition and Development Stage
60The focus for this stage is on installing and releasing the system to the end users
(i.e., “Go-Live”) and on monitoring the system release to the end users
Implementation stage
61often managed by the operation team with assistance from the
implementation team
Operation stage
62s the major activity as support for the new system is
migrated to the help desk and support staff
Knowledge transfer
63Four basic conversion approaches
1.Phased Approach
2.Pilot Approach
3.Parallel Approach
4.Direct Cutover or Big Bang Approach
64gradual movement of the company from the
existing legacy system(s) to the ERP implementation
Phased Approach
65implements a small version of the final system
Pilot Approach
66most up-front cost because the ERP system is
implemented and used in conjunction with the legacy system
Parallel Approach
67highest-risk approach but the most straightforward and clean
Direct Cutover or Big Bang Approach
68The company moves from the legacy
system directly and immediately to ease the ERP system
Direct Cutover or Big Bang Approach