Tài liệu Module 9: Creating a B2B Integration Design pptx

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.. Components of a P

Contents

Overview 1

Review 15

Lab A: Creating a B2B Integration Design 16

Module 9: Creating a B2B Integration Design

Information in this document, including URL and other Internet Web site references, is subject to change without notice Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred Complying with all applicable copyright laws is the responsibility of the user Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property

 2001 Microsoft Corporation All rights reserved

Microsoft, Windows, BackOffice, BizTalk, FrontPage, Hotmail, PowerPoint, Visual Basic, Visual C++, Visual Studio, and Windows Media are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries

The names of actual companies and products mentioned herein may be the trademarks of their respective owners

Instructor Notes

This module provides students with a guide for the creation of a business-to-business (B2B) integration design plan The module reviews concepts that were presented in earlier modules about the elements of trading partner integration, and gives students an opportunity to synthesize the elements

After completing this module, students will be able to:

! Research their organization’s goals to create a project vision for a B2B integration solution

! Research their organization’s technical requirements to create a project design for a B2B integration solution

To teach this module, you need the following materials:

! Microsoft® PowerPoint® file 2420A_09.ppt

! Video file 2420A_09v005.wmv

! Video file 2420A_09v010.wmv

To prepare for this module:

! Read all of the materials for this module

! Complete the lab

! Play the video files

How to Teach This Module

This section contains information that will help you teach this module

Lesson: Creating a Project Vision

This lesson focuses on the first part of the design specification, the project vision It reintroduces the concept of a design specification from Module 2,

“Conducting Project Research,” as a way to state the goals of a design plan and how the organization plans to achieve those goals The content in this lesson is drawn from Modules 1, “Introduction to B2B Integration,” and Module 2, and

is meant as review and preparation for the paper-based lab at the end of this module

To begin, students gather information about their organization and its goals They also gather information about their trading partners that can influence the overall design

Lesson: Creating a Project Design

This lesson focuses on the second part of the design specification, the project design The content in this lesson is drawn from Modules 3 through 8 of this course and is meant as review and preparation for the paper-based lab Students can also use this lesson as a checkpoint to assess their mastery of the material that they learned during the course This lesson provides you, as an instructor, the opportunity to clarify and reinforce the major decision points of a B2B integration solution with the students before they leave the class

Lab: Creating a B2B Integration Design

This lab introduces students to Hanson Brothers, a company that is considering B2B integration with one or more of its trading partners Students will watch videos of several Hanson Brothers representatives as they discuss the business situation of the company and the goals and requirements of their own

departments

In Exercise 1, Creating a Project Vision, introduce the exercise and then play the video file 2420A_09v005.wmv After students finish watching the video, divide them into design teams and have them answer the questions in the exercise Then, ask students to discuss their answers as a class

In Exercise 2, Creating a Project Design, introduce the exercise and then play the video file 2420A_09v010.wmv After students watch the second video, in which Hanson Brothers representatives provide additional information, tell the students to continue to work in their design teams and create a high-level B2B design plan that satisfies the requirements that are stated in the videos Then, ask the design teams present their designs, and have them discuss the designs as

a class for the remainder of the day

At a minimum, student answers should include the design points from the second lesson of this module The lab answer that is provided is neither complete nor definitive It is intended as a sample of what a solution may include Use the lab answer to encourage classroom debate and discussion about the solutions that the students create

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

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

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

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 objectives

Business Information to Obtain

" 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 trading partners

Product information

Order processing

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:

processes, including how it submits orders and transmits other types of business documents, such as invoices

Language (XML)-based schemas that the trading partner uses for electronic catalogs, purchase orders, and other business documents

can specify one or more Internet protocols to use

documents and other trading partner information, including securing the protocol that you use to transmit business documents

other technical restrictions that affect your B2B integration solution

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

Important

Components of a 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

Project vision

Project design

Components of a Project Vision

Section Type of information to include

Problem statement

solve, such as:

# The central business problem that B2B integration must solve, such as:

#Lost sales and customer defection

#Mandate from large B2B trading partner

Business drivers

# Specific motivating factors for B2B integration, such as:

#Decrease transaction costs

#Eliminate manual business processes

Project metrics

# Specific goals to accomplish, such as:

#Reduce customer defection

#Increase sales

#Reduce errors in order processing

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

Project metrics

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

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 objectives

Considerations for Organizing Product Information

Design issues Criteria to consider

Storage method for your master content source

Storage method for your master content source

# Amount of product information

# Number of people managing product information

# Security of the product information

Attributes to include # Usefulness of the information to your trading

partners and to your organization

# Usefulness of the information to your trading partners and to your organization

Content migration

# Existing sources of product information

# Necessary preprocessing and restructuring

# Migration method

Management of your master content source

Management of your master content source

# Maintenance of the master content source

# Authorization of changes

# Security of the product information

***************************** ILLEGAL FOR NON - TRAINER USE ******************************

As the basis of your product catalogs, the master content source contains all of your product information You can use it to create catalogs rapidly for any trading partner You must ensure that the product information in the master content source is complete, accurate, and up to date

When you create a design for the organization of your product information, consider:

storage method that ranges from very simple, such as file formats, to something more robust, such as enterprise database applications The amount of product information, the number of people who manage the master content source, and the security requirements of your trading partners help determine the appropriate storage method

can vary, from attributes that describe a product to business information about the organizations that procure the product, where it is manufactured, and so on Include attributes that trading partners will find useful

make any necessary premigration changes, and then choose a method to migrate product information to the master content source

manage product information in the master content source Determine where you will make updates, who will be authorized to make changes, who will maintain the master content source, and what the security requirements are for the product information

Introduction

Considerations