Академический Документы
Профессиональный Документы
Культура Документы
l
= Mean of lead time
o
2
l
= Variance of lead time
o
l
= Standard deviation of lead time
c = Standard error (we assume that error is 0 in this casedeterministic)
Z
j
= Objective function, where j = 1 is the objective function of the buyer, and
j = 2 is the objective function of the seller
The objective functions of the buyers and sellers (logistics service providers) can
be treated as the matching criteria to select their choice of seller or buyer respectively).
In our current model, the cost of service forms a major aspect for the selection of
logistics service providers and hence in the matching of buyers with sellers. Thus, we
assign maximum weightage to the cost factor o. The second major factor in the partner
selection in the market place is the lead time (
l
, mean of lead time in specific). The
final factor incorporated into the objective function is the standard deviation of lead
time (o
l
), and variance of the lead time (o
2
l
).
Solution Architecture
We give a detailed solution architecture for agent-based B2B market place using Unified
Modeling Language (UML) framework.
UML Modeling for the Agent-Based B2B Market Place for Logistics
Service Providers
For the basics of UML modeling one can refer to Booch et al. (2000) and
Narahari (2002).
Requirements
The agent registers the buyers in the market place.
The agent also registers the sellers in the market place.
The IUP Journal of Operations Management, Vol. X, No. 4, 2011 12
The agent maintains the database of both buyers and sellers.
The agent can update/delete (unregister) details of a buyer.
The agent can update/delete (unregister) details of a seller.
The agent evaluates the requirements of buyers.
The agent evaluates the performance of sellers.
The agent generates the reports of buyers and allows its access to sellers
(logistics service providers) upon request.
The agent generates the reports of sellers (logistics service providers) and
allows its access to the buyers upon request.
The agent does the task of efficient matching of the buyers with the sellers
(logistics service providers).
Analysis
The analysis is intended to capture and describe all the requirements of the system
developed, and to make a model that defines the key domain classes in the system
(i.e., what is handled in the system, by the system, etc.).
The purpose of analysis is to provide an understanding and enable a communication
about the system between the developers and the people establishing the requirements
(i.e., users of the system).
Analysis is not restricted to the technical solutions or details. It is the first step of
really understanding the requirements and the reality of the system under design.
Requirements Analysis
The first step in the analysis is to define the use cases, which describe what the agent-
based B2B market place provides in terms of functionalitythe functional requirements
of the system.
Use case analysis involves reading and analyzing the specifications, as well as
discussing the system with potential usersbuyers and sellers (logistics service
providers).
Identifying the Actors in the System
There are three actors in the system:
1. Agent
2. Buyer; and
3. Seller
Key Use Cases of Each Actor
Agent:
Updating the database of buyers.
13 Designing an Agent-Based B2B Market Place for Third Party
Logistics Service Providers (3PLs)
Updating the database of sellers (logistics service providers).
Registering new users (buyer/seller) in the market place.
Deleting the users (buyer/seller) from the market place.
Generating the reports of users (buyers/sellers) registered in the market place.
Evaluating the performance of sellers (logistics service providers).
Considering the requests of buyers.
Buyer:
Registering with the market place.
Unregistering with the market place.
Updating the details in the market place.
Requesting for the reports of sellers from agent.
Finding the logistics service provider who matches the requirements.
Seller (Logistics Service Provider):
Registering with the market place.
Unregistering with the market place.
Updating the details in the market place.
Requesting for the reports of buyers from agent.
Finding the potential buyer who matches the requirements.
Based on the above-mentioned key use cases, the use case diagram is given in
Figure 3. It is evident from the use case diagram that both buyer and seller (logistics
service provider) depend on the agent for the transactions in the market place. In this
context agent can be treated as the administrator of the system, who does the
maintenance of the system, updates databases of both buyers and sellers, deletes
databases if required, appends new buyers or sellers to databases.
An On-Line Analytical Processing (OLAP) system can be employed in conjunction
with the agent, which facilitates the agent to surf the net and search for potential users
(both buyers and sellers).
Analysis of the System Designed and the Domain
To conduct domain analysis, the specification of the system and the use cases should
be thoroughly understood. The aspects on which the system should focus should be
made clear.
The domain classes in the system are identified as: agent, buyer, seller (logistics
service provider). These domain classes are defined with a stereotype <<Business
Object>>, which is user-defined stereotype specifying that objects of the class are
The IUP Journal of Operations Management, Vol. X, No. 4, 2011 14
part of the key domain and should be stored persistently in the system. The class
diagram of the system is presented in Figure 4.
The class diagram is a more general case of the B2B market place with multiple
agents for a single market. In the present model, we focus on single-agent model.
The state transition diagram for matching of buyers with logistics service providers
is given in Figure 5.
Figure 3: Use Case Diagram for Design of Agent-Based B2B Market Place
for Logistics Service Provider
15 Designing an Agent-Based B2B Market Place for Third Party
Logistics Service Providers (3PLs)
Design
The design phase expands and details the analysis model by taking into account all
technical implications and restrictions.
The main purpose of design phase is to specify a working solution that can be
easily translated into programming code. The classes defined in the analysis are
detailed in this phase, and new classes are added to handle technical areas, such as a
database, Graphical User Interfaces (GUIs), etc.
The design can be divided into two segments:
1. Architectural Design: This is a high-level design where the packages
(subsystems) are defined, including the dependencies and primary
communication mechanisms between the packages. The goal of architectural
design is to come up with a clear and simple architecture.
Figure 4: Class Diagram for Agent-Based B2B Market Place
for Logistics Service Provider
Agent
code: Code
addbuyer()
deletebuyer()
modifybuyer()
addlsp()
deleteseller()
modifyseller()
rep_buyer()
rep_seller()
matchbuyers()
matchsellers()
Has
Has Has
1..n 1..n
LSP(Seller)
Integer:
name:
lsp_register()
lsp_unregister()
lsp_update()
lsp_req_report()
lsp_match_buyer()
buy_register()
buy_unregister()
buy_update()
buy_req_report()
buy_match_seller()
Integer:
name:
Buyers
1..n
Has
1..n
Integer:
name: Market
Market
addagent()
deleteagent()
updateagent()
generatereports()
The IUP Journal of Operations Management, Vol. X, No. 4, 2011 16
In the current model, we have used Visual Basic as the front end (since it has the
features of object orientation). Besides, it forms a good choice for interface design with
good GUI features. The database such as DB2 can be used to link the JAVA code via
JDBC.
A well-designed architecture is the foundation for an extensible and changeable
system. The packages can concern either handling of a specific functional area or a
specific technical area. It is vital to separate the application logic (i.e., the domain
classes) from the technical logic so that changes in either of these segments can be
done easily without much impact on the other part. The internal design of package
with architectural overview of application packages, database, and their dependencies
is shown in Figure 6.
2. Detailed Design: This part details the contents in the package, so that all
classes are described in detail to give clear specifications to the programmer
for coding the class. The purpose of detailed design phase is to describe the
new technical classes (classes in the GUIs) and database packages to expand
Figure 5: State Transition Diagram for Matching Buyers
and Logistics Service Providers
Not Matched
Entry: No. of Matches
= 0
Buyer/Seller registry/
No. of matches ++
Matches removed (if an LSP
is chosen by buyer)
[No. of matches = 1]/No. of
matches
Matched
Matching Buyer and LSP/
No. of matches ++
Match chosen [No. of
matches >1]/ No. of
matches
17 Designing an Agent-Based B2B Market Place for Third Party
Logistics Service Providers (3PLs)
and detail the descriptions of
the business object class,
which is already done in the
analysis phase.
Database Package
This application of the design of
agent-based market place for logistics
service provider must have the
objects to be stored persistently,
therefore a database layer must be
added to provide this service. The
natural solution in a full-fledged
application is to use a commercial
database such as IBM-DB2 for this
purpose. The application layer does
not expose details of data storage to
either parties (buyers and suppliers).
The details of storage in the database
is hidden from the user and is
accessible through web browser via
Java code, as insert (), delete (),
update () are facilitated via the Java
database code.
Activity Diagrams
The activity diagrams give a pictorial view of the various functionalities of the system
designed. The activity diagrams of buyer and seller (logistics service provider) are
shown in Figures 7 and 8 respectively.
Sequence Diagrams
A sequence diagram for matching buyers and sellers is shown in Figure 9. These are
helpful in designing the user interfaces for the system.
Market Negotiation Mechanism
The current model, works on the principle of Double Auction for winner determination
(refer Kameshwaran and Narahari, 2001, for a detailed survey on various auction
mechanisms in market place design), i.e., each buyer checks the reports of the price
quotes, mean lead times of delivery and variance of lead times of the logistics service
providers, and depending on the quotes of sellers (logistics service providers), she
can update her quote for price, mean delivery time and also the variance of the lead
time. Similarly, the logistics service provider can see the reports of the quotes of the
buyers of the service and accordingly they can modify (increase or decrease) their
Figure 6: Internal Design of Package
GUI (Browser)
Business Objects
(Java)
Database Package
(DB2)
Utility Package
(Agent-Based
B2B Market
Application)
The IUP Journal of Operations Management, Vol. X, No. 4, 2011 18
Figure 8: Activity Diagram for Logistics Service Provider (Seller)
Seller
Agent
Register in
Market place
Add details
of seller
Generate reports
of buyer
Request for
buyers
Select buyer
Figure 7: Activity Diagram for Buyer
Register in
Market place
Buyer
Agent
Add details of
buyer
Generate reports
of seller
Request for
seller reports
Select
LSP (Seller)
19 Designing an Agent-Based B2B Market Place for Third Party
Logistics Service Providers (3PLs)
price quotes. Thus, the market mechanism functions and results in maximizing the
overall satisfaction of the market stakeholders.
Conclusion and Future Work
In this paper, we have proposed a solution framework for B2B market for Third-Party
Logistics Service Providers (3PLs). We have employed UML for architecting this
framework. We use a double auction mechanism that would maximize the overall
satisfaction of the market stakeholders.
Some areas for future work include:
Extending our model and framework specifically to capture the interaction
between price bundles and service quality.
Extending to other auction models.
Considering the B2C market: the requirement in this case would be to enhance
the scalability of the model.
Enhancing the features and mobile enablement for agile decision making.
Figure 9: Sequence Diagram for the Use Case of Matching LSP for a Buyer
Add Buyer
Window
Buyer
Details
Generate
Reports of
Seller
Match LSP
to Buyer
Agent
1. Find Buyer
2. Find
(String)
3. Add Buyer()
4. Generate
Reports of LSP
5. Match LSP()
The IUP Journal of Operations Management, Vol. X, No. 4, 2011 20
References
1. Booch G, Rumbaugh J and Jacobson I (2000), The Unified Modeling Language
User Guide, Addison Wesley, Pearson Education Asia.
2. Bowersox Donald J and David J Closs (1996), Logistical Management: The
Integrated Supply Chain Process, AAAI Technical Report SS-96-02, McGraw Hill.
3. Chavez Anthony and Maes Pattie (1996), Kasbah: An Agent Marketplace for
Buying and Selling Goods, MIT Media Lab.
4. Chavez Anthony, Dreilinger Daniel, Guttman Robert and Maes Pattie (1997),
A Real-Life Experiment in Creating an Agent Marketplace, MIT Media Lab.
5. Garg Dinesh (2002), Design of Six Sigma Supply Chains, M.Sc. (Engg.) Thesis,
Department of Computer Science and Automation, Indian Institute of Science,
Bangalore.
6. Hopp W J and Spearman M L (1996), Factory Physics, Irwin.
7. Kameshwaran S and Narahari Y (2001), Auction Algorithms for Achieving
Efficiencies in Logistics Marketplaces, International Conference on Energy,
Automation and Information Technology (EAIT 2001), IIT Kharagpur,
December 10-12.
8. Lau H C and Lo Yuk Ting G (2000), A Multi-Agent Framework for Supporting
Web-Based Intelligent Fourth Party Logistics, Proceedings of the First International
Conference On Integrated Logistics (Logistics 2001), School of Computing,
National University of Singapore.
9. Ledyard John O, Olson Mark, Porter David et al. (2002), The First Use of a
Combined-Value Auction for Transportation Services, Interfaces, Vol. 32, No. 5,
pp. 0004-0012.
10. Narahari Y (2002), Object Technology Vgraphs on Object Technology and
UML, Department of Computer Science and Automation, Indian Institute of
Science, Bangalore.
11. Rothkopf Michael H and Park Sunju (2001), An Elementary Introduction to
Auctions, Interfaces, Vol. 31, No. 6, pp. 83-97.
12. Simchi-Levi David and Philip Kaminsky Edith (1999), Designing and Managing
the Supply Chain: Concepts, Strategies and Case Studies, Irwin/McGraw-Hill.
13. Srinivasa Raghavan N R, Viswanadham N, Lakshminarayanan A and Deshpande
Mukund (2002), Agent Based Order Management System for Virtual
Manufacturing Networks, Technical Report, Department of Management Studies,
Indian Institute of Science, Bangalore.
21 Designing an Agent-Based B2B Market Place for Third Party
Logistics Service Providers (3PLs)
14. Tewari Gaurav and Maes Pattie (2000), Design and Implementation of an Agent-
Based Intermediary Infrastructure for Electronic Markets, in Proceedings of the
2
nd
ACM Conference on Electronic Commerce, pp. 86-94.
15. Viswanadham N (2000), Analysis of Manufacturing Enterprise, Kluwer Academic
Publishers.
16. Viswanadham N and Gaonkar Roshan (2001), E-Logistics: Trends and
Opportunities, E-Logistics Research WP: TLI-AP/01/01 , January, The Logistics
Institute Asia-Pacific.
17. Zhang Liang-Jie, Yadav Pooja, Chang Henry et al. (2001), ELPIF: An E-Logistics
Processes Integration Framework Based on Web Services, Research Report, IBM,
T J Watson Research Center.
Reference # 07J-2011-11-01-01
Copyright of IUP Journal of Operations Management is the property of IUP Publications and its content may
not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written
permission. However, users may print, download, or email articles for individual use.