"Web site, App Transport" requierments
Components to be developed
Component pages and their requirements
General requirements
1.Back-end Administration page for apps(framework)
2.Android / iOS for customers (framework)
3. Android / iOS drivers application (framework)
4. Front-end Site Web Interface (framework)
1.Back-end Administration page for apps(framework)
1.1 Back-end to develop
1.2 Dashboard
1.3 DriverManager
1.4 Driver List
1.5 Driver Name and Surname and Indicative ( each driver car,truck will have a number in the sistem) (visibile in customer apps)
1.6 Vehicle Model (visibile in customer apps)
1.7 Vehicle Icon on map (visibile in customer apps)
1.8 Transport type (ex: taxi, van, truck&trailer, Bus, Autocar)(visibile in customer apps)
1.9 Reg NO
1.10 Docs (document to upload)
1.11 Driver Licence
1.12 CPC (Certificat of Professional Competence)
1.13 Card Tahograph
1.14 Vehicle Registrations document
1.15 Vehicle transport licence
1.16 Vehicle&goods Insurance
1.17 Vehicle MOT/ITP
1.18 Chat between dispatcher and driver
1.19 Dispach jobs to drivers
1.20 Driver Bank details
1.21 Driver Contact NO
1.22 Driver Email ID/Indicative
1.23 Driver Wallet
1.24 Driver Status Control Approve/Disapprove
1.25 Driver Delete Control-delete
1.26 Driver map Radius setting control
1.27 CustomerManager List
1.28 Customer UID
1.29 Name
1.30 Surname
1.31 Company details
1.32 for Company Documents to upload
1.33 Customer Bank details
1.34 Customer Contact NO1. Components
1.35 Customer Email ID
1.36 Customer Status approve/disapprove
1.37 Customer Delete Control
1.38 Radius on map setting control
1.39 Trips Status
1.40 Trip List
1.41 Records
1.42 Search
1.43 No
1.44 Begin Time
1.45 End Time
1.46 Starting Time
1.47 Destination
1.48 Driver/indicative ( each driver car,truck will have a number in the sistem)
1.49 Customer
1.50 Payment Method, Card or cash
1.51 Fee/amount
1.52 Status, Finished
2.Android / iOS for customers (framework)
2.1. Android/iOs customer /Application pages
2.2- Login / Register page with email and password, name, surname, phone
Customer / driver application:
The application will be one with the client or driver registration option.
After installing the application, the customer or driver registers by e-mail
2.3 Name
2.4 Surname
2.5 Company details
2.6 Payment options, cash or card, invoices sistem generator.
2.7 When the customer open first page of app he/she see ( google maps page and the closest drivers (range 0~ 3 km)
2.8 Radius setting in customer app ( Customer set radius in app depending on wich type of transport he/she need, if he/she need a taxi, logic he/she will set a minumum distance like 1 or 2 km because the taxi wich are in he/she radius will arrive in maxim 10 minute to adress he/she made the order if the customer need a Truck for goods he/she will look for a truck in area where is the warehouse is so radius must include area that customer is interested
2.9 Drivers appear on the map with icon depending on the type of transport, eg: taxi -> car, -> truck, bus, courier, limousine, classical cars.
2.10 The app opens, the customer sees on the map what car/truck/taxi...has within a radius of 0-3 / km around he/she, if he/she is registered with a bank card he/she can access any transport service.
2.11 When customer clicks on a driver / logo this will display a driver's pop-up (window)
2.12 When customer click on the driver / logo, the profile opens and it has the following information:
2.13 -1) first name, surname
2.14-2) picture
2.15-3) tariff / KM
2.16-4) distance in km / hour.
2.17- 5) Then option for address, street, no, block, staircase.
2.18-6) GPS coordinates or postal code (if applicable)
2.19-7) Job detail message/chat sistem.
2.20 Command option to the selected driver or to all drivers of the services, eg taxis, trucks, buses.
2.21- Payment in bank account will be made after the discussion with the driver, because in the application we will not know the cost that involves the route / destination / to be transported.
2.22 - Are all enrolled drivers on the client map or just the ones who have open / online application? Only the ones online appear but in the beginning for promotion, it would be good to have drivers / auto disconnected!
2.23 When a client orders the driver, a window will appear on the screen and can be accepted or rejected
2.24 For trucks or other types of transport, I think that the customer needs to discuss the driver with the driver and they want to give the client the opportunity to call the driver in the application and the driver to call the customer immediately if he sent the order.
2.25 - When the command option is pressed by the customer, the driver receives notification with written information from the client, the driver will have the option to answer/accept/reject, driver confirm( I will arrive in 1-3-5-10-15 minutes, hours or days (as the case may be)
2.26 In driver app notification, order (popup windows) the driver must recive it by nerest distance, ex: 500meters first shown, second order 700 meters simultaneosly
2.27 In both driver / client applications somewhere at the top (online drivers no ...- online clients no ..)
2.28 A buzz button in both client / driver notification apps "where are you? I've arrived!" Chat for details / real time information.
2.29 Connecting disconnection between client / driver during the race, the two can be seen on the map until one of them disconnects the application.
2.30 Option to send customer order (tick / debif in client app) to all taxi, truck, bus, limo drivers. From the selected driver profile.
2.31 Page BURSA DE MARFURI Customer drop on map diffrent types of goods for transport( visibile in driver app) a good example of functionality is “my maps by Google LLC” or Map Marker by theandroidseb”
3. Android / iOS drivers application (framework)
3.1. Drivers application pages
3.2 Driver log-in
3.3 After installing the application, the driver registers by e-mail and adds the options to connect with facebook.
fields:
3.4 -1) Name
3.5-2 Surname
3.6-Indicative
3.7-3) Payment options, invoice sistem generator.
3.8 Once in the application the driver has the opportunity to see his personal profile, add additional information (personal picture, car picture, identity card picture, driving license, car picture, license photo, taxi authorization, car model, Engine, year of registration, numbers, color). Here is the account to be activated after checking the documents, so an activation function in the control panel!
3.9 Cash or card.
3.10-After registration (if applicable) before being approved by the manager, driver will have the option to upload the following photographed documents:
3.11-Driver Name and Surname and Indicative ( each driver car,truck will have a number in the sistem) (visibile in customer apps)
3.12-Vehicle Model (visibile in customer apps)
3.13- Vehicle Icon on map (visibile in customer apps)
3.14- Transport type (ex: taxi, van, truck&trailer, Bus, Autocar)(visibile in customer apps)
3.15- Reg NO
3.16- National ID/Passport
3.17-Driver Licence
3.18-CPC (Certificat of Professional Competence)
3.19-Card Tahograph
3.20- Vehicle Registrations document (certificate)
3.21-Vehicle Authorization / License for transport type3.22- Vehicle&goods Insurance
3.23- Vehicle MOT/ITP
3.24- Chat between dispatcher, driver or customer
3.25-Driver Bank details
3.26- Driver Contact NO
3.27-Driver Email ID
3.28-In Control Panel (There must be an option to add / remove documents in the control panel so that we do not modify the application each time a new document appears)
3.29-(In the driver option to set customer visibility from 0 to 1000 / km).
3.30-When a customer gives their order on profile drivers screen, they will have a window and the possibility of accepting or reject it.
3.31-Simultaneously when the driver recive an order, they are shown in order by distance, ex: first order 500 meters, second order 700 meters….etc.
3.31 Invoice system, generate an invoice for customer and driver or company driver if option is selected in apps..
4. Front-end Site Web Interface (framework)
4.1-Front-end site first page will look exactly like old page www.uncal.ro
4.2- All functionalities from customer/driver apps will be the same like in apps in folowing pages; UN TAXI?, UN TRANSPORT?, UN CURIER?, UN RECOVERY?,BURSA DE MARFURI, ANGAJARI. In rest of the pages they will be connect to a forum
4.3 Page BURSA DE MARFURI Customer drop on map diffrent types of goods for transport( visibile in driver app) a good example of functionality is “my maps by Google LLC” or Map Marker by theandroidseb”
4.4 Invoices system generator between customer/drivers, transport company and platform uncal and customer or drivers/ company transport
Legal requierment for Romania
The clauses of this Agreement and any disputes, controversies or differences arising out of, or in connection with them, will be governed, interpreted and respectively resolved according to the Romanian legislation.
In order to obtain the technical opinion, the digital platform for alternative transport intermediation must cumulatively fulfill the following technical conditions:
a) contain the fiscal registration data and contact details of the digital platform operator;
b) keep the automatic record of the expiration dates of the driving licenses and the documents necessary for performing the alternative transport operations and automatically notify the alternative transport operator in order to update the documents uploaded on the digital platform;
c) to propose, display and record the route traveled, using localization technologies in accordance with the Community legislation in force;
d) to provide data on the fare for a race on the route established under the conditions letter. c) before the passenger accepts the race;
e) to provide data on the registration number of the car with which the race is performed;
q) to process personal data in compliance with Law no. 190/2018 on measures to implement Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals with regard to the processing of personal data and on the free movement of such data and repealing of Directive 95/46 / EC (General Data Protection Regulation);
r) to ensure the issuance and transmission to the passenger of the order, as well as of the electronic invoice issued based on it;
s) to ensure access to its services only to the transport operators, drivers and cars that meet the legal conditions for performing the alternative transport;
t) to have implemented appropriate methods and procedures for ensuring cyber security and data protection, which comply with the security requirements mentioned in art. 7 of this order;
u) to have implemented a quality verification system for the alternative transport activity offered by the alternative transport operators / drivers accepted on the digital platform;
v) to ensure the use of the Romanian language for all interfaces, information displayed or printed.
Article 7. -
The minimum security requirements of the information systems through which the digital platforms for alternative transport by car and driver are provided refer to:
a) confidentiality and integrity of communications between the digital platform, the customer and the driver regarding the races performed;
b) mechanisms that guarantee the confidentiality and non-repudiation of the alternative transport activities carried out through the digital platform;
c) the authenticity of the parties participating in the alternative transport activities and the existence of the authentication methods in accordance with the security level of the digital platform, as well as the means of guaranteeing the identity;
d) the confidentiality, authenticity and integrity of the information / data related to the alternative transport activities carried out through the digital platform during their processing, storage and archiving;
e) the traceability of intermediate transport activities through the digital platform;
f) observing the protection of personal data in computer systems;
g) storing, keeping the recorded data and journaling them, as well as keeping safe backups of data and alternative transport activities intermediate through the digital platform;
h) preventing / limiting / eliminating the impact of computer security incidents, safely resuming the alternative transport activity and recovering the affected information;
i) detection, recording and management of computer security incidents;
j) evaluation of the risks of computer security and their management measures;
k) ensuring a formal and continuous (at least annually) process of preparing the human resources involved in the operation, maintenance and administration of the digital platforms that mediate alternative transport activities;
l) continuity of the services offered to the clients;
f) to monitor all the races, continuously, through a location system;
g) to provide passengers with the option to communicate information about disability / reduced mobility and to communicate with the driver to whom the race was assigned and provide information on the location and estimated time of arrival;
h) to provide passengers with the opportunity to report to the digital platform operator any incidents regarding the race;
i) to ensure a communication interface available and accessible for 24 hours a day, 7 days a week for incidents regarding the race;
m) management and administration of the computer system;
n) the impact of the operations to modify:
- the architecture within the computer system (hardware / software components) and the software applications used in the life cycle of the digital platform;
- the security plan specific to the security related to the digital platform;
o) any other technical activities or measures undertaken for the safe exploitation of the computer system through which the digital platform is made available.
Article 8. -
The technical and organizational measures taken to meet the technical requirements listed in art. 6 will be in line with the technology used and the potential risks.
Article 9. -
The operator of the digital platform has the obligation to implement IT security measures, to continuously monitor and to evaluate annually the operational risks generated by the use of the information systems through which the digital platform is made available, in compliance with the national law and the Community regulations.
Article 10. -
The data mentioned for keeping in the Government Emergency Ordinance no. 49/2019 regarding the alternative transport activities by car and driver, as well as the documents issued in electronic format, whose keeping is obligatory according to the norms in force, related to the alternative transport activities carried out through the digital platform, will be filed according to the national legislation regarding electronic archiving.
"Web site, App Transport" requierments
Components to be developed
Component pages and their requirements
General requirements
1.Back-end Administration page for apps(framework)
2.Android / iOS for customers (framework)
3. Android / iOS drivers application (framework)
4. Front-end Site Web Interface (framework)
1.Back-end Administration page for apps(framework)
1.1 Back-end to develop
1.2 Dashboard
1.3 DriverManager
1.4 Driver List
1.5 Driver Name and Surname and Indicative ( each driver car,truck will have a number in the sistem) (visibile in customer apps)
1.6 Vehicle Model (visibile in customer apps)
1.7 Vehicle Icon on map (visibile in customer apps)
1.8 Transport type (ex: taxi, van, truck&trailer, Bus, Autocar)(visibile in customer apps)
1.9 Reg NO
1.10 Docs (document to upload)
1.11 Driver Licence
1.12 CPC (Certificat of Professional Competence)
1.13 Card Tahograph
1.14 Vehicle Registrations document
1.15 Vehicle transport licence
1.16 Vehicle&goods Insurance
1.17 Vehicle MOT/ITP
1.18 Chat between dispatcher and driver
1.19 Dispach jobs to drivers
1.20 Driver Bank details
1.21 Driver Contact NO
1.22 Driver Email ID/Indicative
1.23 Driver Wallet
1.24 Driver Status Control Approve/Disapprove
1.25 Driver Delete Control-delete
1.26 Driver map Radius setting control
1.27 CustomerManager List
1.28 Customer UID
1.29 Name
1.30 Surname
1.31 Company details
1.32 for Company Documents to upload
1.33 Customer Bank details
1.34 Customer Contact NO1. Components
1.35 Customer Email ID
1.36 Customer Status approve/disapprove
1.37 Customer Delete Control
1.38 Radius on map setting control
1.39 Trips Status
1.40 Trip List
1.41 Records
1.42 Search
1.43 No
1.44 Begin Time
1.45 End Time
1.46 Starting Time
1.47 Destination
1.48 Driver/indicative ( each driver car,truck will have a number in the sistem)
1.49 Customer
1.50 Payment Method, Card or cash
1.51 Fee/amount
1.52 Status, Finished
2.Android / iOS for customers (framework)
2.1. Android/iOs customer /Application pages
2.2- Login / Register page with email and password, name, surname, phone
Customer / driver application:
The application will be one with the client or driver registration option.
After installing the application, the customer or driver registers by e-mail
2.3 Name
2.4 Surname
2.5 Company details
2.6 Payment options, cash or card, invoices sistem generator.
2.7 When the customer open first page of app he/she see ( google maps page and the closest drivers (range 0~ 3 km)
2.8 Radius setting in customer app ( Customer set radius in app depending on wich type of transport he/she need, if he/she need a taxi, logic he/she will set a minumum distance like 1 or 2 km because the taxi wich are in he/she radius will arrive in maxim 10 minute to adress he/she made the order if the customer need a Truck for goods he/she will look for a truck in area where is the warehouse is so radius must include area that customer is interested
2.9 Drivers appear on the map with icon depending on the type of transport, eg: taxi -> car, -> truck, bus, courier, limousine, classical cars.
2.10 The app opens, the customer sees on the map what car/truck/taxi...has within a radius of 0-3 / km around he/she, if he/she is registered with a bank card he/she can access any transport service.
2.11 When customer clicks on a driver / logo this will display a driver's pop-up (window)
2.12 When customer click on the driver / logo, the profile opens and it has the following information:
2.13 -1) first name, surname
2.14-2) picture
2.15-3) tariff / KM
2.16-4) distance in km / hour.
2.17- 5) Then option for address, street, no, block, staircase.
2.18-6) GPS coordinates or postal code (if applicable)
2.19-7) Job detail message/chat sistem.
2.20 Command option to the selected driver or to all drivers of the services, eg taxis, trucks, buses.
2.21- Payment in bank account will be made after the discussion with the driver, because in the application we will not know the cost that involves the route / destination / to be transported.
2.22 - Are all enrolled drivers on the client map or just the ones who have open / online application? Only the ones online appear but in the beginning for promotion, it would be good to have drivers / auto disconnected!
2.23 When a client orders the driver, a window will appear on the screen and can be accepted or rejected
2.24 For trucks or other types of transport, I think that the customer needs to discuss the driver with the driver and they want to give the client the opportunity to call the driver in the application and the driver to call the customer immediately if he sent the order.
2.25 - When the command option is pressed by the customer, the driver receives notification with written information from the client, the driver will have the option to answer/accept/reject, driver confirm( I will arrive in 1-3-5-10-15 minutes, hours or days (as the case may be)
2.26 In driver app notification, order (popup windows) the driver must recive it by nerest distance, ex: 500meters first shown, second order 700 meters simultaneosly
2.27 In both driver / client applications somewhere at the top (online drivers no ...- online clients no ..)
2.28 A buzz button in both client / driver notification apps "where are you? I've arrived!" Chat for details / real time information.
2.29 Connecting disconnection between client / driver during the race, the two can be seen on the map until one of them disconnects the application.
2.30 Option to send customer order (tick / debif in client app) to all taxi, truck, bus, limo drivers. From the selected driver profile.
2.31 Page BURSA DE MARFURI Customer drop on map diffrent types of goods for transport( visibile in driver app) a good example of functionality is “my maps by Google LLC” or Map Marker by theandroidseb”
3. Android / iOS drivers application (framework)
3.1. Drivers application pages
3.2 Driver log-in
3.3 After installing the application, the driver registers by e-mail and adds the options to connect with facebook.
fields:
3.4 -1) Name
3.5-2 Surname
3.6-Indicative
3.7-3) Payment options, invoice sistem generator.
3.8 Once in the application the driver has the opportunity to see his personal profile, add additional information (personal picture, car picture, identity card picture, driving license, car picture, license photo, taxi authorization, car model, Engine, year of registration, numbers, color). Here is the account to be activated after checking the documents, so an activation function in the control panel!
3.9 Cash or card.
3.10-After registration (if applicable) before being approved by the manager, driver will have the option to upload the following photographed documents:
3.11-Driver Name and Surname and Indicative ( each driver car,truck will have a number in the sistem) (visibile in customer apps)
3.12-Vehicle Model (visibile in customer apps)
3.13- Vehicle Icon on map (visibile in customer apps)
3.14- Transport type (ex: taxi, van, truck&trailer, Bus, Autocar)(visibile in customer apps)
3.15- Reg NO
3.16- National ID/Passport
3.17-Driver Licence
3.18-CPC (Certificat of Professional Competence)
3.19-Card Tahograph
3.20- Vehicle Registrations document (certificate)
3.21-Vehicle Authorization / License for transport type3.22- Vehicle&goods Insurance
3.23- Vehicle MOT/ITP
3.24- Chat between dispatcher, driver or customer
3.25-Driver Bank details
3.26- Driver Contact NO
3.27-Driver Email ID
3.28-In Control Panel (There must be an option to add / remove documents in the control panel so that we do not modify the application each time a new document appears)
3.29-(In the driver option to set customer visibility from 0 to 1000 / km).
3.30-When a customer gives their order on profile drivers screen, they will have a window and the possibility of accepting or reject it.
3.31-Simultaneously when the driver recive an order, they are shown in order by distance, ex: first order 500 meters, second order 700 meters….etc.
3.31 Invoice system, generate an invoice for customer and driver or company driver if option is selected in apps..
4. Front-end Site Web Interface (framework)
4.1-Front-end site first page will look exactly like old page www.uncal.ro
4.2- All functionalities from customer/driver apps will be the same like in apps in folowing pages; UN TAXI?, UN TRANSPORT?, UN CURIER?, UN RECOVERY?,BURSA DE MARFURI, ANGAJARI. In rest of the pages they will be connect to a forum
4.3 Page BURSA DE MARFURI Customer drop on map diffrent types of goods for transport( visibile in driver app) a good example of functionality is “my maps by Google LLC” or Map Marker by theandroidseb”
4.4 Invoices system generator between customer/drivers, transport company and platform uncal and customer or drivers/ company transport
Legal requierment for Romania
The clauses of this Agreement and any disputes, controversies or differences arising out of, or in connection with them, will be governed, interpreted and respectively resolved according to the Romanian legislation.
In order to obtain the technical opinion, the digital platform for alternative transport intermediation must cumulatively fulfill the following technical conditions:
a) contain the fiscal registration data and contact details of the digital platform operator;
b) keep the automatic record of the expiration dates of the driving licenses and the documents necessary for performing the alternative transport operations and automatically notify the alternative transport operator in order to update the documents uploaded on the digital platform;
c) to propose, display and record the route traveled, using localization technologies in accordance with the Community legislation in force;
d) to provide data on the fare for a race on the route established under the conditions letter. c) before the passenger accepts the race;
e) to provide data on the registration number of the car with which the race is performed;
q) to process personal data in compliance with Law no. 190/2018 on measures to implement Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals with regard to the processing of personal data and on the free movement of such data and repealing of Directive 95/46 / EC (General Data Protection Regulation);
r) to ensure the issuance and transmission to the passenger of the order, as well as of the electronic invoice issued based on it;
s) to ensure access to its services only to the transport operators, drivers and cars that meet the legal conditions for performing the alternative transport;
t) to have implemented appropriate methods and procedures for ensuring cyber security and data protection, which comply with the security requirements mentioned in art. 7 of this order;
u) to have implemented a quality verification system for the alternative transport activity offered by the alternative transport operators / drivers accepted on the digital platform;
v) to ensure the use of the Romanian language for all interfaces, information displayed or printed.
Article 7. -
The minimum security requirements of the information systems through which the digital platforms for alternative transport by car and driver are provided refer to:
a) confidentiality and integrity of communications between the digital platform, the customer and the driver regarding the races performed;
b) mechanisms that guarantee the confidentiality and non-repudiation of the alternative transport activities carried out through the digital platform;
c) the authenticity of the parties participating in the alternative transport activities and the existence of the authentication methods in accordance with the security level of the digital platform, as well as the means of guaranteeing the identity;
d) the confidentiality, authenticity and integrity of the information / data related to the alternative transport activities carried out through the digital platform during their processing, storage and archiving;
e) the traceability of intermediate transport activities through the digital platform;
f) observing the protection of personal data in computer systems;
g) storing, keeping the recorded data and journaling them, as well as keeping safe backups of data and alternative transport activities intermediate through the digital platform;
h) preventing / limiting / eliminating the impact of computer security incidents, safely resuming the alternative transport activity and recovering the affected information;
i) detection, recording and management of computer security incidents;
j) evaluation of the risks of computer security and their management measures;
k) ensuring a formal and continuous (at least annually) process of preparing the human resources involved in the operation, maintenance and administration of the digital platforms that mediate alternative transport activities;
l) continuity of the services offered to the clients;
f) to monitor all the races, continuously, through a location system;
g) to provide passengers with the option to communicate information about disability / reduced mobility and to communicate with the driver to whom the race was assigned and provide information on the location and estimated time of arrival;
h) to provide passengers with the opportunity to report to the digital platform operator any incidents regarding the race;
i) to ensure a communication interface available and accessible for 24 hours a day, 7 days a week for incidents regarding the race;
m) management and administration of the computer system;
n) the impact of the operations to modify:
- the architecture within the computer system (hardware / software components) and the software applications used in the life cycle of the digital platform;
- the security plan specific to the security related to the digital platform;
o) any other technical activities or measures undertaken for the safe exploitation of the computer system through which the digital platform is made available.
Article 8. -
The technical and organizational measures taken to meet the technical requirements listed in art. 6 will be in line with the technology used and the potential risks.
Article 9. -
The operator of the digital platform has the obligation to implement IT security measures, to continuously monitor and to evaluate annually the operational risks generated by the use of the information systems through which the digital platform is made available, in compliance with the national law and the Community regulations.
Article 10. -
The data mentioned for keeping in the Government Emergency Ordinance no. 49/2019 regarding the alternative transport activities by car and driver, as well as the documents issued in electronic format, whose keeping is obligatory according to the norms in force, related to the alternative transport activities carried out through the digital platform, will be filed according to the national legislation regarding electronic archiving.
