Overview
The Extended Enterprise business pattern, which is also known as the Business-to-Business pattern or B2B pattern, addresses the interactions and collaborations between business processes in separate enterprises. This pattern can be observed in solutions that implement programmatic interfaces to connect inter-enterprise applications. In other words, it does not cover applications that are directly invoked using a user interface by business partners across organizational boundaries.
Extended Enterprise Examples
-
Cross Industry Examples
-
Buy Side
- Direct Procurement (SCM)
- Indirect Procurement (MRO)
- Supply chain execution
-
Sell Side
- B2B e-commerce (Distributors)
- B2C e-commerce (Consumers)
-
Trading Partner Modernization
- EDI Modernization
-
Exchange Participation
- Private e-exchanges
- Public e-exchanges
-
Buy Side
-
Industry Specific Examples
-
Manufacturing
- Supply chain planning
- Supply chain execution
- Vendor Managed Inventory
-
Travel
- Checking flight or room availability
- Making or modifying reservations
-
Retail
- Checking supplier inventory
- Placing replenishment orders
- Paying suppliers automatically
-
Financial
- Transferring payments
- Checking account balances
- Obtaining credit information
- Loan Origination
- Processing securities
-
Telecommunication
- OSS Integration
- Cross organization order management
- Managed service provider interconnect
-
Manufacturing
What's Next
If you're not yet sure that your business problem can be solved by the functionality enabled through an Extended Enterprise solution design, the Extended Enterprise general guidelines page provides additional information on choosing this Business pattern. Business and IT drivers, the e-business context appropriate for this solution type, and additional solution details are discussed here.
If you've determined that the Extended Enterprise business pattern can provide an appropriate solution design for your business need, the next step is to select an Application pattern. The Extended Enterprise business pattern can be implemented using any one of three different Application patterns with a number of variations, providing solution flexibility so that the determined Business pattern can address the specific needs of the business process being automated.
