Hardware installation and testing……….M5-M9 These tasks are split into two phases.
The first phase refers to the installation and laboratory testing of the multi-sensor system at SATA (M5 – M9), so as to prove the feasibility of the integration between signals from the infra-red sensor and the RFID reader.
This second phase refers to the installation of the complete solution at the BRIDGE premises (M10-M12). This is where controlled tests can be performed on the behaviour of the multi-sensor infrastructure.
RFID-ROI-SME: Pilot RFID Deployments and ROI Studies for SME using Open Source Middleware and Tools
WP1- Requirements and Use Cases Definition Deliverable D2.3: “Detailed Project Plan of Pilots”
Results are reported in D5.1 and D5.2.
Software and middleware installation and testing M6-M10 In the previous task the integration is tested initially with a simplified interface specifically designed to this purpose.
Then, the new middleware and functions are integrated into the existing video-surveillance application, so as to obtain its enhanced version.
The last software version include the automated video recording whenever an event of interest occurs.
Results are reported in D5.1 and D5.2.
RFID systems testing………M9-M11
The third task refers to the installation and testing in open air and operational conditions of the smart pole. The test includes the definition of the detection geometry and camera region/area of interest (ROI), and the definition of the area where RFID must work and read active tags.
Controlled tests are performed on both the behaviour of the RFID system and the usability of the new application, so as to make the BRIDGE reference persons (used to work with construction site security managers and video-surveillance operators) in condition to get familiar with the system and to evaluate more in depth the possible impacts on the internal work organisation.
Results are reported in D5.1 and D5.2.
5.6 Training of users in testing environment,
preparation of technical documentation M10-
M12
During this task a User Manual, a User Acceptance Test Scenario (UAT), and a Technical Installation manual are prepared. User groups are: (i) BRIDGE technicians, who should understand in detail the new application, (ii) control room operators, which should master the new video- surveillance application, (iii) workers, who are just informed on the importance of wearing a tag and changing it when not working properly. The training language is Italian.
A training video is also prepared to support the construction companies in training their employees also in distance learning mode. Results are reported in D5.4.
The following tasks relate to the actual operation with the new RFID- enabled processes.
RFID enabled Process Operation………M13-M24 The first real construction site to monitor is very close to one of the BRIDGE yard border, then to control its access it is sufficient to set properly the sensors on the smart pole installed within the BRIDGE yard. This is an ideal condition because it is still a controlled environment but the test is in real life.
After refining and tuning the smart pole sensor settings, a number of controlled validation sessions are planned in the M13-M14 period. Each session includes: 10 BRIDGE people entering/exiting the yard without tags (intruders, alarms risen), 10 tagged BRIDGE people and 10 tagged customer workers entering/exiting the yard with tags (20 read tags, no alarms), 10 cars and 10 trucks entering/exiting the yard without tags (intruders, alarm on), 10 tagged cars and 10 tagged trucks entering/exiting the yard with tags (20 read tags, no alarms).
In the M13-M14 period it will be possible to check the system behaviour in winter time (cold + bad weather conditions), in the M15-M19 period it will be possible to check the system in summer time (high temperature), so as to detect possible bad influences from the external environment.
Of course in case of damage or mis-functioning of hardware components BRIDGE and SATA will search for another component and realise its integration into the whole system.
Since M15 the RFID tags will be given to workers and put on cars, operating machines and trucks.
Results are reported in D6.1, D6.2 and D6.3.
Technical Support to Process Operation………….M13-M24 SATA as solution provider will support the whole validation phase at BRIDGE, by fixing bugs in the RFID application, if any, and providing the second level help-desk (being the first level ensured by the trained BRIDGE technicians). SATA will also organise and analyse requests and comments coming from the users, so as to incorporate them into the second and third release of the RFID application (see next task).
SATA will set up an automated download procedure for bug fixing, so as to put the RETE ICT staff in condition to install in some minutes new software versions needed to remove critical errors and restore data consistency and correctness.
Results are reported in D6.1 and D6.3.
New RFID application releases ………..M17-M24
Besides new software versions needed to fix bugs, SATA envisages two software releases after the initial one.
RFID-ROI-SME: Pilot RFID Deployments and ROI Studies for SME using Open Source Middleware and Tools
WP1- Requirements and Use Cases Definition Deliverable D2.3: “Detailed Project Plan of Pilots”
The first update will be issued at the end of the controlled experiment (end of April 2010), so as to include operational improvements that can help the video-surveillance operators working on the real scenes.
The second update is expected at the end of year 2011, after seven months of living pilot.
This last update is accompanied by a requirement specification document reporting problems met, solutions implemented and a list of open requirements, which could be implemented after the end of the project. Results are reported in D6.1 and D6.3.
Feedback and Processes and Services Improvement……. M13-M24
This task, in charge of BRIDGE, refer to bug fixing and new requirement collections during pilot operations.
Every problem met during the day-by-day operation is reported to BRIDGE project responsible and its technical staff, and, if necessary, to SATA for removing possible software errors.
Every suggestion for improvement is reported to BRIDGE project responsible, who is in charge of prioritising them and issue a requirement list to discuss with SATA. The result of this discussion consists of the decision on which functions will be included into the two software releases respectively due at end of April and end of December 2011.
At the end of the pilot phase, the system users are requested to complete a questionnaire to derive opinions, hints, suggestions and lessons learnt. Results are reported in D6.1, D6.2 and D6.3.