Internship PPT


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Internship PPT

  1. 1. Warehouses Connected In A Network Topology <ul><li>An Extension of the Dual T </li></ul><ul><li>Anuvrat Singh </li></ul><ul><li>16 July, 2008 </li></ul>
  2. 2. <ul><li>The Present </li></ul><ul><ul><li>Guillaume Zufferey and Patrick Jermann working on the Dual T Furniture </li></ul></ul><ul><ul><li>Dual T Furniture simulates a warehouse </li></ul></ul><ul><ul><li>Complement the apprentices theoretical schooling with an interactive visual emulation of a real warehouse </li></ul></ul><ul><ul><li>Teachers propose an exercise for the day and the apprentices have to model the warehouse keeping the teachers instructions in mind </li></ul></ul><ul><ul><li>After the apprentices have designed a warehouse, a simulation runs to show how effective their design was </li></ul></ul><ul><ul><li>The teacher can pause the simulation to drive home an interesting observation that may have presented itself during the course of the simulation </li></ul></ul>
  3. 3. <ul><li>A Vision </li></ul><ul><ul><li>Connecting the furniture's together into a network to enable them to exchange data </li></ul></ul><ul><ul><li>A network of warehouses to have consumers, producers and intermediaries </li></ul></ul><ul><ul><li>Simulation runs each warehouse on the client, but when the warehouse run out of materials, they look towards the network to obtain new items </li></ul></ul><ul><ul><li>Communication between warehouses </li></ul></ul>
  4. 4. <ul><li>The Objective </li></ul><ul><ul><li>Setup a network of warehouses which will be managed by a centralized server </li></ul></ul><ul><ul><li>Server always know about the transactions occurring between different clients </li></ul></ul><ul><ul><li>Have the clients synchronized </li></ul></ul><ul><ul><li>Model the delay in transactions </li></ul></ul>
  5. 5. <ul><li>The Model </li></ul><ul><ul><li>A centralized server which monitors the activities of the clients </li></ul></ul><ul><ul><li>Server responsible for setting the parameters of the simulation, starting and stopping the simulation </li></ul></ul><ul><ul><li>Clients are categorized into consumers, producers and intermediaries </li></ul></ul><ul><ul><li>Two modes of simulation </li></ul></ul><ul><ul><ul><li>Automatic </li></ul></ul></ul><ul><ul><ul><li>Manual </li></ul></ul></ul><ul><ul><li>For each of the above modes, two additional options </li></ul></ul><ul><ul><ul><li>Connectivity Dependency : True </li></ul></ul></ul><ul><ul><ul><li>Connectivity Dependency : False </li></ul></ul></ul><ul><ul><li>All in all, 4 modes of operation built into the system </li></ul></ul>
  6. 6. <ul><li>The Implementation </li></ul><ul><ul><li>Adaptive Communications Environment (ACE) framework was used to build the application so as to ensure portability among different operating systems </li></ul></ul><ul><ul><li>Only port number needs to be configured – client runs a ServerSearch module which discovers the servers’ location – further communication with the server now possible </li></ul></ul><ul><ul><li>UDP and TCP connections both on the same port number – this is to have fewer configuration specifications </li></ul></ul><ul><ul><li>Server acts as the central master – sets the parameters for the experiment – starts and stops the simulation </li></ul></ul><ul><ul><li>Server chooses one of the 4 modes – the manual mode being more logistics oriented </li></ul></ul><ul><ul><li>A module within server maintains the clients in synchronization using the time of the server as a measure of relative speeds – the time measured in seconds </li></ul></ul><ul><ul><li>Delay of transportation modeled as a delay list with the client – the client checks the delay list for updates when it has run out of its inventory </li></ul></ul>
  7. 7. <ul><li>Achievements </li></ul><ul><ul><li>A platform independent C++ implementation of the network topology of warehouses consisting of a centralized server control and clients </li></ul></ul><ul><ul><li>Only one configuration parameter – the port - which could be hard-coded into the program to avoid the hassles of the user having to configure the system </li></ul></ul><ul><ul><li>The ACE acceptor / connector reactor model used to design the server and clients – ease of communication which can be initiated by either the server or the client </li></ul></ul><ul><ul><li>The clients are always synchronized within a few cycles of each other – the speed of the clients can be as low as executing the main loop in hundreds of milliseconds – faster than this the clients are not synchronised </li></ul></ul><ul><ul><li>The delay was modeled </li></ul></ul>
  8. 8. <ul><li>Further Work </li></ul><ul><ul><li>As the server always knows the details of all the clients, a GUI at the server end could be used to effectively monitor the interactions between the warehouses </li></ul></ul><ul><ul><li>As of now the clients can be at most as fast as executing the main loop in hundreds of milliseconds – improving the speed is possible by adopting either of the two options </li></ul></ul><ul><ul><ul><li>Count the clock ticks instead of seconds </li></ul></ul></ul><ul><ul><ul><li>Instead of using time() use ACE_OS::clock_gettime() – the latter provides time value in seconds and nanoseconds </li></ul></ul></ul><ul><ul><li>Caution to be observed while implementing either of the above given alternatives </li></ul></ul>