MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION 1 MONALISA 2.0 – Activity 3 Customisation for Pilot Application Document No: MONALISA 2 0_D3.1.5
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
1
MONALISA 2.0 – Activity 3
Customisation for Pilot Application
Document No: MONALISA 2 0_D3.1.5
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
2
DocumentInformation
Project MONALISA2.0SecuringthechainbyintelligenceatseaFoundedby The Trans-European Transport Network (TEN-T) of the European
Union Activity 3 - Safer ShipsWorkPackage 3.1 - HSQE (Health Safety Quality Environment)
HistoryVersionTable
Version Date Author Comments1.0 20140905 IB DRAFTtoMIT2.0 20140930 IB ApprovedbyMITforreleasetotheconsortium
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
3
TableOfContents1 Introduction.......................................................................................................4
1.1 General...............................................................................................................4
1.2 Aboutthisdocument..........................................................................................4
1.3 Conclusions.........................................................................................................5
2 DataBASE2.0®UDGRADES.................................................................................5
3 “MOBILE”aspectsofDataBASE2.0®..................................................................7
AppendixA-“Specifichedeirequisiti_20140305”(separatepdffile)..........................11
AppendixB-“Analisi_20140305–pages37-66”(separatepdffile)............................11
AppendixC-“Grigliafunzionalità_20140305”(separatepdffile)................................11
AppendixD-“dataBASE_Obiettivi_Riunioni_Pannello_eMail_v1”(separatepdffile).11
AppendixE–MOCKUP...............................................................................................11
AppendixF-DataBASE2.0®executable(storedonIBDataCentre)............................17
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
4
1 Introduction
1.1 GeneralAccording to theSAP (pages14and25), theaimssub-activity3.1are toassess thepossibilityand benefits of transferring the BBS approach to the maritime sector as a tool to improveoperationalsafetybyreducingunsafebehaviorsduringnormaloperations. Hence,thegoalofthe sub-activity is to adapt the BBS methodology and related ICT tools for use in maritimeapplicationsandtestthemasappropriatethroughsuitableprototype(s).Themethodusedencompassesthefollowingsteps:•adaptBBSpracticesandICTtools(widelyapplied inother industrialsectors)toMoS.Theso
adaptedpracticesandtoolsareindicatedas“BBStools”inthefollowing;•testtheBBStoolsinatleastonerealisticpilotapplicationinvolvingsuitableoperators;• calibrate/refine the BBS tools based on the feed-back from the field and identify possible
obstaclestoitsvoluntaryapplicationbytheshippingindustry;•assess,throughouttheprocess,compatibilitywithIMOaswellasClassrequirementsThreedifferentorganisationsco-operate(IBandErgoprojectas implementingbodiesof ItalianMinistryofTransportandCIMNEfromSpain),undertheleadofIB,asfollows:• analysis of BBS best practice and success factors in other industries, possibility that the
same/similar success factors can be triggered in the maritime sector. Identification ofavailable BBS methodology and certification standard(s) and of their applicability to themaritime sector, identification of possible and meaningful test cases/scenarios for amaritimeapplication(IBandCIMNE).WorkcompletedandreportedinD3.1.1.Methodologyadaptedtomarinedomain;
•adaptationoftheBBSmethodologyandBBSICTtoolstotheselectedmaritimescenarios(IBand CIMNE). Work completed and reported in D3.1.2: BBS ICT tool adapted to marinedomain;
•definition,specification,planning,preparation(e.g.tuningofICTtoolstothespecifiedcases)of at least one demonstrator in realistic scenario (IB and CIMNE). Work completed andreported in this document D3.1.3: User, task and environmental profiles and developerrequirements
•developmentofdemonstrator(s) includingadhoc(preliminaryversion)ICTtoolformaritimeBBS applications. Work ongoing and to be reported in D3.1.5: Customization for pilotapplications;
• execution of at least two pilot applications (one in Italy and one in Spain) using thedemonstrator(s). Feedback frompilots andapplicationof aHuman-CenteredDesign (HCD)approach,basedoncurrentandfutureregulations(e.g.IMO’se-navigation),toevaluateitsapplicabilityandeffectivenesstoICTtoolsandpromoteeaseofuseandacceptancebythetarget users. Work ongoing and to be reported in D3.1.6: Execution and Report on pilotapplications.
1.2 AboutthisdocumentThisdocumentisorganizedasfollows:- upgradesdonefromDataBASE®toDataBASE2.0®aredescribedinChapter2;- somehintsontheuseofDataBASE2.0®areprovidedinChapter3;- DataBASE2.0®specificationsandrelatedaspectsaretheobjectofAppendicesAtoD;
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
5
- screenshotsofDataBASE2.0®aregiveninAppendixE;- executableversionofDataBASE2.0®isstordeinIBDataCenter(seeAppendixF).
1.3 ConclusionsInD.3.1.1,theapplicabilityofBBSmaritimeoperationswasconfirmed.InD.3.1.2applicability tomaritimeBBSof theDataBASE®1existing ICTtoolwasdiscussedandthenecessaryupgradestoenableitsuseonmaritimeapplications(DataBASE2.0®)wasoutlined.InD.3.1.3detailsandtechnicalspecificationswereprovidedonpilotapplications.
D.3.1.5
AimofthisdocumentistoprovidedetailsontheItaliandemonstratorDataBASE2.0®.
ThepreliminaryversionofDataBASE2.0®describedinthisdocumentisexpectedtofulfilltheneeds of maritime BBS. Verification will be the scope of the Italian pilots currently underdevelopmentwhichwillbereportedinD3.1.6.
2 DataBASE2.0®UDGRADESAs described in D3.1.2, DataBASE2.0® incorporates and upgrades DataBASE® to the extentnecessary to deal withmaritime BBS applications. (see Tables 2.1 and 2.2, reproduced fromdocumentD3.1.2).Besidesthat,thefollowingupgradeshavealsobeenmade:- improvedlogicalflow- revisedcomponentstoallowfortheuseofmobileinfrastructure(particularlyimportantfor
useona“mobile”environmentasships);- allowingforan“almost”paperlessapproach;- allowingrealtime(i.e.“onthefield”)datareporting.The following features were included being them necessary for one or more of the aboveupgrades:- dataisrecordedatthesameoftheobservation;- possibility to accessonline toobservedand storeddata also to (authorized)personsnot
belonging to the companywhichusesBBS;examplesof such “authorized”personnel arerepresentativesfromFlagAdministration;
- automaticforwardingofmessagesandalerts;- realtimefeedbacktotheobserverofthe“observedbehavior”;- possibilitytoattachphoto/picturestotherecord;
1TheDataBase® ICTtoolhasbeendesignedanddevelopedbyAARBA(AssociationforAdvancementofRadical Behavior Analysis) that in Europe acts on behalf og CCBS (Cambridge Center for BehavioralStudies).AARBAReference:http://www.aarba.eu/CCBSReference:http://www.behavior.org/
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
6
- automaticMeetingplanningandmanagement.
Tab.2.1:technologicalimplementation
Tab.2.2:methodologicalimplementation.
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
7
3 “MOBILE”aspectsofDataBASE2.0®The BBS process managed by the new ICT tool is described in Figure 3.1 (reproduced fromD3.1.2).
Figure3.1Theprocess
Belowthelogicalweblay-outoftheDataBASE2.0®:
Thegeneralarchitectureofthedevelopedsystemis:
• 3-tierdistributedarchitecture(seefigure3.2)• Server:
MVCmodel(robustness,security);SupportforDBpopular;JAVA.
• Client:webstandards:html/css/javascript;mobileclientforAndroid.
ThewebclientarchitectureisdetailedinFigure3.3.TheMobilefeaturesallowthefollowingcapabilities:
●Checklistimportfromserver;●Checklistcompilationalsoinoff-linemodality;●Compileddocuments(observations)exporttoserver.
Infigure3.4theMobileInfrastructuredevelopedSchemeisshown.
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
8
Figure3.2The3-tierdistributedarchitecture
Figure3.3Thewebclientarchitecture
Mobile’sfeaturesofDataBASE2.0®arethefollowings:
• Database,RepositoryandDatamanagedlocallyonthemobiledevices;• DatabaseServerinDataCenteroronShipOwneronshoretechnicaloffice;• DataEntryfunctionalityonlyavailableOnMobiledevices;• Otherfunctionsareintraditionalinterface(Web).
ExampleofBBSmobileapplicationonAndroiddevicesisshowninFig.3.5.
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
9
Figure.3.4MobileInfrastructureScheme
Step1Step2ID
MenùResultVocalidentification
Figure3.5Mobileapplication
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
10
AdetaileddescriptionofthetokenprocessandrelevanttheICTtollmanagementisprovideinAppendix4(confidential).
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
11
Appendix A - “Specifiche dei requisiti_20140305” (separate pdffile)Confidentialitwillbeprovided,ifsorequested,onlytotheEuropeanCommission.
AppendixB-“Analisi_20140305–pages37-66”(separatepdffile)Confidential: it specifies data model and ER (Entity and Relationship) diagrams. It will beprovided,ifsorequested,onlytotheEuropeanCommission.
AppendixC-“Grigliafunzionalità_20140305”(separatepdffile)Confidential: it covers system functionalities and the roles and authorization of each actorinvolvedintheprocess.Itwillbeprovided,ifsorequested,onlytotheEuropeanCommission.
Appendix D - “dataBASE_Obiettivi_Riunioni_Pannello_eMail_v1”(separatepdffile)Confidential:describethetokenprocessandrelevantICTmanagement.itwillbeprovided,ifsorequested,onlytotheEuropeanCommission.
AppendixE–MOCKUP
FigureE.1Logintosystem
FigureE2DefinitionandInitialization:AlldatarelevanttothecurrentOrganizationarefilledin
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
12
FigureE.3Languageselection
FigureE.4Usersname,roleandresponsibility
FigureE.5Activitiesdefinition
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
13
FigureE.6Inizializationofworkingareaandfacilities
FigureE.7Detailsofworkingareaandfacilities
FigureE.8workingareaandfacilitiesmanagement(workingtimeetc.)
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
14
FigureE.9Observationareaslinkingtoaspecificgroup
FigureE.10Checklistdefinition
FigureE.11Exampleofchecklistobservationcompilation
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
15
FigureE.11Exampleofchecklistobservationcompilationwithremarks(OSSERVAZIONI)
FigureE.12Results:outputofgraphicsandtablesobservations
FigureE.13Resultsfiltersdefinitionfor:observationperiod,workingtime,workingarea,facilitiesetc.)
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
16
FigureE.14Periodicmeetingplanningandmanagement
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
17
FigureE.15Tokeneconomyinitializationandallocationcriteria
FigureE.16Tokeneconomyexampleofassignment
AppendixF-DataBASE2.0®executable(storedonIBDataCentre)
MONALISA 2.0 - CUSTOMISATION FOR PILOT APPLICATION
18
39 partners from 10 countries
taking maritime transport into the digital age
By designing and demonstrating innovative use of ICT solutions MONALISA 2.0 will provide the route to improved
SAFETY - ENVIRONMENT - EFFICIENCY
Swedish Maritime Administration ◦ LFV - Air Navigation Services of Sweden ◦ SSPA ◦ Viktoria Swedish ICT ◦ Transas ◦ Carmenta ◦ Chalmers University of Technology ◦ World
Maritime University ◦ The Swedish Meteorological and Hydrological Institute ◦ Danish Maritime Authority ◦ Danish Meteorological Institute ◦ GateHouse ◦ Navicon ◦ Novia
University of Applied Sciences ◦ DLR ◦ Fraunhofer ◦ Jeppesen ◦ Rheinmetall ◦ Carnival Corp. ◦ Italian Ministry of Transport ◦ RINA Services ◦ D’Appolonia ◦ Port of
Livorno ◦ IB SRL ◦ Martec SPA ◦ Ergoproject ◦ University of Genua ◦ VEMARS ◦ SASEMAR ◦ Ferri Industries ◦ Valencia Port Authority ◦ Valencia Port Foundation ◦
CIMNE ◦ Corporacion Maritima ◦ Technical University of Madrid ◦ University of Catalonia ◦ Technical University of Athens ◦ MARSEC-XL ◦ Norwegian Coastal Administration
www.monalisaproject.eu
http://www.monalisaproject.eu