Module 9: Creating a B2B Integration Design v
The design lab is scheduled for 75 minutes, but it can run longer depending on
classroom participation and enthusiasm. After students watch the Exercise 1
video, divide them into small teams and ask them to spend 15 minutes
discussing the scenario and preparing answers for Exercise 1. Then, discuss the
answers with the class. After students watch the second video, ask them to
spend 45 minutes discussing the scenario and preparing answers for Exercise 2.
Then, ask each team to present its answers to the class.
Although the lab scenario provides a clear path to certain design decisions, it
contains enough ambiguity to encourage student discussion and debate.
Students may disagree with the answers that are provided in the Delivery Guide
and the Student Materials compact disc. Disagreement is acceptable if the
student can provide adequate business or technical justification. To increase
student involvement, ask a representative of each team to present the team’s
answers to the class and then defend the design.
Timing
Discussion
vi Module 9: Creating a B2B Integration Design
Customization Information
This section identifies the lab setup requirements for a module and the
configuration changes that occur on student computers during the labs. This
information is provided to assist you in replicating or customizing Microsoft
Official Curriculum (MOC) courseware.
This module contains a single paper-based design lab. There are no hands-on
labs in this module, and as a result, there are no lab setup requirements or
configuration changes that affect replication or customization.
Module 9: Creating a B2B Integration Design 1
Overview
! Creating a Project Vision
! Creating a Project Design
*****************************
ILLEGAL FOR NON
-
TRAINER USE
******************************
In business-to-business (B2B) integration, no generic solutions exist because
each organization is unique and has different business and technical
requirements, processes, and systems. For example, some large organizations
use a sophisticated electronic data interchange (EDI) infrastructure and have
spent years perfecting B2B business practices. In contrast, some midmarket
organizations still use paper catalogs and enter orders manually.
To create a design that translates your goals into actions, you complete a design
specification. In the first part of the design specification, called the project
vision, you research and document your organization’s business goals and
drivers for B2B integration. In the second part, called the project design, you
specify actions that your organization must take to meet your goals and
complete your B2B integration solution.
After completing this module, you will be able to:
!
Research your organization’s goals to create a project vision for your B2B
integration solution.
!
Research your organization’s technical requirements to create a project
design for your B2B integration solution.
Introduction
Objectives
2 Module 9: Creating a B2B Integration Design
Lesson: Creating a Project Vision
! Business Information to Obtain
! Trading Partner Information to Obtain
! Components of a Design Specification
! Components of a Project Vision
*****************************
ILLEGAL FOR NON
-
TRAINER USE
******************************
To guide the integration of your trading partners, you create a design
specification that lists the problems that your organization faces and how you
intend to solve them. To begin, you gather information about your business and
your trading partners. Then, you complete the components of the project vision.
After completing this lesson, you will be able to:
!
Describe the information to obtain about your business.
!
Describe the information to obtain about your trading partners.
!
Explain the major components of a design specification.
!
Organize your high-level design criteria in a project vision.
Introduction
Lesson ob
j
ectives
Module 9: Creating a B2B Integration Design 3
Business Information to Obtain
! Trading partners
"
Current and potential trading partners
"
Integration requirements
! Product information and catalog management
"
Location of information
"
Catalog creation
! Order processing
"
How your organization receives and processes
purchase orders
"
Level of integration with other business systems
*****************************
ILLEGAL FOR NON
-
TRAINER USE
******************************
To create a successful B2B integration solution for your organization, gather
the necessary background information about your organization and your trading
partners. Three major factors influence your design: the buyers who buy your
products, the catalogs that present product information to buyers, and the order
processing transactions that occur when buyers buy from you electronically.
You must identify your current and potential B2B trading partners. Your
trading partners and their integration requirements directly influence the scope
and complexity of your design. Simple integration designs may connect your
organization with a single online marketplace, whereas complex designs may
integrate your organization with multiple individual buyers and their dissimilar
infrastructures.
To create catalogs that meet the requirements of your trading partners, first
identify where your organization currently stores product information and how
it manages that information. Then, identify how you create your catalogs and
whether they are electronic, paper, or both. Knowing the complexity of your
catalog creation process will help you allocate time and resources for planning
the project, so that you can create catalogs rapidly for your trading partners.
Trading partners must be able to submit purchase orders (POs) electronically to
your organization for order processing. How your organization receives and
processes orders and the degree of automation that you want will determine to
what extent you will integrate your organization’s business systems.
You can choose to do a small amount of internal integration of your business
systems or a significant amount. For example, you may decide only to integrate
purchase order receiving and internally route POs to an Enterprise Resource
Management (ERP) system. Or, you may decide to integrate your POs
throughout your full procurement cycle and process the entire transaction
electronically from start to finish through many dissimilar business systems.
Introduction
B2B tradin
g
partners
Product information
Order processing
4 Module 9: Creating a B2B Integration Design
Trading Partner Information to Obtain
For each trading partner, obtain:
"
Business practices and requirements
"
Preferred business document schemas
"
Preferred protocols for transmitting business
documents
"
Security of information
"
Trading partner restrictions
"
Service level agreement
*****************************
ILLEGAL FOR NON
-
TRAINER USE
******************************
In the planning stages of your integration design, identify the main trading
partners that you consider to be candidates for B2B integration. As a supplier,
your trading partners may be marketplaces, buyers, or both. Understand the
requirements and restrictions of each trading partner so that you can design the
most appropriate B2B integration solution.
A trading partner agreement is a document that lists the essential components
that are necessary to integrate a trading partner in your B2B system. A typical
trading partner agreement includes:
!
Business practices and requirements. The trading partner’s typical business
processes, including how it submits orders and transmits other types of
business documents, such as invoices.
!
Preferred business document schemas. The type of Extensible Markup
Language (XML)-based schemas that the trading partner uses for electronic
catalogs, purchase orders, and other business documents.
!
Preferred protocols for transmitting business documents. Trading partners
can specify one or more Internet protocols to use.
!
Security of information. The measures that you will take to protect business
documents and other trading partner information, including securing the
protocol that you use to transmit business documents.
!
Trading partner restrictions. Limitations on the size of catalogs and any
other technical restrictions that affect your B2B integration solution.
!
Service level agreement. A technical document that specifies the level or
quality of service that you and your trading partner guarantee to provide to
each other.
Because a trading partner agreement is legally binding, it is strongly
recommended that you consult with your organization’s legal representatives
before you create one.
Introduction
Trading partner
agreement
Importan
t
Module 9: Creating a B2B Integration Design 5
Components of a Design Specification
Design Specification
Design Specification
Business information
that guides the
design process
Detailed design
information that
the implementation team
uses to complete
the project
# Project vision includes:
# Problem statement
# Business drivers
# Project metrics
# Proposed solution
# Project design includes:
# Master content source
# Catalog design and publishing
# Order processing
# Remote shopping
# UDDI integration
# XML Web services
*****************************
ILLEGAL FOR NON
-
TRAINER USE
******************************
A design specification typically includes two main sections: the project vision
and the project design. Because each B2B integration solution is unique, each
design specification is unique. For example, your trading partners may have
certain requirements in common, such as transport protocols for order
processing, but they may differ on other items, such as catalog schemas. When
you design a B2B integration solution for your organization, you can expand
upon the basic template that is shown in the preceding slide and modify the
solution when necessary.
The project vision is the foundation of the project design. It defines current
business challenges in the form of a problem statement and includes other
business drivers for your B2B integration with trading partners. The vision also
contains an executive summary of the proposed solution and the metrics that
your organization will use to measure the progress and success of the project.
The project design contains your detailed proposal for B2B integration. The
project’s implementation team uses the information in the project design to
build the B2B integration solution.
Introduction
Pro
j
ect vision
Project design
6 Module 9: Creating a B2B Integration Design
Components of a Project Vision
Section
Section
Section
Type of information to include
Type of information to include
Type of information to include
Problem statement
Problem statement
# The central business problem that B2B integration must
solve, such as:
# Lost sales and customer defection
# Mandate from large B2B trading partner
# The central business problem that B2B integration must
solve, such as:
# Lost sales and customer defection
# Mandate from large B2B trading partner
Business drivers
Business drivers
# Specific motivating factors for B2B integration, such as:
# Decrease transaction costs
# Eliminate manual business processes
# Specific motivating factors for B2B integration, such as:
# Decrease transaction costs
# Eliminate manual business processes
Project metrics
Project metrics
# Specific goals to accomplish, such as:
# Reduce customer defection
# Increase sales
# Reduce errors in order processing
# Specific goals to accomplish, such as:
# Reduce customer defection
# Increase sales
# Reduce errors in order processing
Proposed solution
Proposed solution
# A brief summary of your project design and physical
design
# A brief summary of your project design and physical
design
*****************************
ILLEGAL FOR NON
-
TRAINER USE
******************************
The project vision, which contains the high-level design criteria, is the
component of the design specification that you use to obtain executive approval
for the project. Typically, a project vision includes a problem statement,
business drivers, project metrics, and an executive summary of the proposed
solution.
The problem statement states succinctly why you are undertaking this project
and what its level of importance is. An example problem statement is: The
organization is losing sales and experiencing customer defection due to lack of
e-procurement support for trading partners.
Business drivers are additional motivating factors for your organization’s B2B
integration solution. Business drivers elaborate on the problem statement or are
closely related to it. The business drivers that you identify will help you
determine the proposed solution.
Examples of business drivers include:
!
Expand the organization’s customer base.
!
Lower the cost of sales to increase profit.
!
Eliminate manual business processes for the processing and fulfillment of
orders.
Project metrics describe how your organization will measure the success of the
project. They help you measure the progress and quantify how well your project
solves the business problem and meets the business drivers. Project metrics
must be measurable, specific, timed, and attributable.
Examples of project metrics include:
!
Reduce customer defection to 0 percent in the next six months.
!
Increase sales to trading partners by 10 percent in the next 12 months.
!
Reduce errors in order processing by 20 percent in the next 18 months.
Introduction
Problem statement
Business drivers
Pro
j
ect metrics
Module 9: Creating a B2B Integration Design 7
The proposed solution is a short, usually nontechnical explanation of the
solution to the problem statement. The proposed solution is intended primarily
for key business stakeholders. It briefly explains how you intend to solve the
business problem.
An example of an introduction to a proposed solution is: The organization will
design and implement a B2B e-commerce infrastructure, based on XML, that
integrates internal technical and business processes to retain the existing
customer base, gain new customers, and reduce sales costs. The rest of the
proposed solution contains a brief overview of the project design.
Proposed solution
8 Module 9: Creating a B2B Integration Design
Lesson: Creating a Project Design
! Considerations for Organizing Product Information
! Considerations for Designing and Publishing Catalogs
! Considerations for Processing Orders
! Considerations for Designing Remote Shopping
! Considerations for Using UDDI
! Considerations for Integrating XML Web Services
*****************************
ILLEGAL FOR NON
-
TRAINER USE
******************************
In the project design component of a design specification, you list the major
elements that you intend to integrate with trading partners in order to fulfill the
project vision. To create your project design, carefully examine each element of
B2B integration and determine what steps your organization will take.
After completing this lesson, you will be able to evaluate considerations for:
!
Organizing product information.
!
Designing and publishing catalogs.
!
Processing orders.
!
Designing remote shopping.
!
Using Universal Description, Discovery and Integration (UDDI).
!
Integrating XML Web services.
Introduction
Lesson ob
j
ectives
Không có nhận xét nào:
Đăng nhận xét