3.1.2.2 Session: Exploration of server-client technologies

Exploration of server-client technologies

Organize students into groups each group must have at least one PC
Divide client roles of the manufacturing scenario one to each group (lathe machine, AGV, )

Ideate phase

Each group must define manufacturing tasks for the corresponding client based on the previous session
Define the use of interface messages for the control of the client
- example for AGV
  # command move, pamareter s source, parameter t destination move -s lathe -t assembly
Clients don’t need to be fully automated they can be controlled manually using proper commands from the command line. For example, moving AGV from one to another location can be monitored by a stopwatch accompanied by accordingly requests to the server
Each group must define which information it needs from the server
From the collected information a list of requirements for the HTTP client must be created.
The list must include:
- Type of request (GET, POST)
- data format (JSON) and data content (message structure)
- Error handling strategy (how the client responds to failed requests)

Prototype

Implementation of HTTP server (10 min)

Ideate phase

Create a NodeJs app for the HTTP server
Each group builds a part of the server that corresponds to their mock server from the previous task

Prototype

Create a NodeJs app for the HTTP server
Each group builds a part of the server that corresponds to their mock server from the previous task
The server group integrates the routes of others (clients) to their app
Test the manufacturing application where
- clients make calls to real servers not mock

Manufacturing app (60 min)

Ideate phase

All participants together build an SD that represents the complete process of manufacturing one end product that is assembled nut and bolt

Prototype