Appendix 3B: solution Description
advertisement
DATE DOCUMENT CONTACT MAIL 2 February 2015 Appendix 3B: Solutions description Peter Holst Herzberg phol@vd.dk APPENDIX 3B: SOLUTION DESCRIPTION Niels Juels Gade 13 PO Box 9018 DK-1022 Copenhagen K Phone +45 7244 3333 vd@vd.dk roaddirectorate.dk EAN 5798000893450 CBR 60729018 PHONE PAGE 2 of 31 Guidelines to the Tenderer This appendix must be completed by the Tenderer prior to submitting the tender. Only areas marked with yellow may be changed. Answers can be in English or Danish. Overall description of the delivered System Chapter 1 of this appendix is divided into two parts. In the first part, the Tenderer shall fill in the answers to the information requirements from Appendix 3A. In the second part the Tenderer shall make an overall description of the proposed system. The description can include brochures, user manuals etc. Description of the fulfilment of the requirements In chapter 2 of this appendix the tenderer shall describe how each requirement is fulfilled by the delivered system. This section under the heading "Guidelines to Tenderer" will not form part of the final Contract. PAGE 3 of 31 TABLE OF CONTENTS 1 2 DESCRIPTION OF THE DELIVERED SYSTEM ............................................................................................................................ 4 1.1 Information requirements ............................................................................................................................................................ 4 1.2 The Tenderer shall describe the offered solution ....................................................................................................................... 9 FULFILLMENT OF THE REQUIREMENTS................................................................................................................................... 10 2.1 Requirements from Contract appendix 3A ...................................................................................................................... 11 PAGE 4 of 31 1 DESCRIPTION OF THE DELIVERED SYSTEM 1.1 INFORMATION REQUIREMENTS Req. 55. Generalisation The Supplier shall describe in detail how the requirements in section Error! Reference source not found.- Error! Reference source not found. above will be fulfilled. [The Tenderer shall insert the answer here.] Req. 171. Data output format comments The Supplier shall in appendix 3B, section 1 describe how to deliver the data as outlined in the above table. Dynamic Data Data name Format Comment Traffic Conditions, DynDB & DynAPM DATEX II [To be filled by the Tenderer] WEB CAM Denmark DATEX II [To be filled by the Tenderer] VINTERMAN DATEX II [To be filled by the Tenderer] PAGE 5 of 31 Ferries DATEX II [To be filled by the Tenderer] Limfjords Tunnel DATEX II [To be filled by the Tenderer] Limfjords Bridge DATEX II [To be filled by the Tenderer] Trafikman2 DATEX II [To be filled by the Tenderer] Real time parking area information DATEX II [To be filled by the Tenderer] Warm Asphalt DATEX II [To be filled by the Tenderer] Critical announcements DATEX II [To be filled by the Tenderer] Bicycle Routes for Nav. Sys GPX Export format for bicycle routes navigation systems. Req. 203. Description of the IT architecture The Supplier shall describe the proposed IT architecture and especially describe how the IT architecture will fulfil the requirements PAGE 6 of 31 to information security (cf. Appendix 3A6) and the service level requirements (cf. Appendix 6). The description includes IT infrastructure components (system software, tools etc.), the interfaces, input/output data processing. The IT architecture shall be flexible, interoperable and make use of standards. The Customer emphasizes that: The IT architecture is service oriented. Both data and function shall be accessed through services. The interfaces to the System are standardized as shown on the architecture drawing. The IT architecture is based on the Model-View-Control pattern. The System is configurable. The System is redundant The System is designed for use 24 hours a day all year. The IT architecture is robust, flexible, open and based on well-known standards. The purpose is to have low cost maintenance and a system that is easy to evolve and integrate to other systems. The Customer shall approve the IT architecture and the architecture design produced by the Supplier during the Clarification Phase. [The Tenderer shall insert the answer here] Req. 204. New types of integrations to other IT systems The Supplier shall show that the System is flexible regarding new data types, new data sources and changes in existing data and PAGE 7 of 31 sources. The Supplier shall therefore describe how the following is handled: New data sources New data types Changed data sources from existing sources Changed data types from existing sources [The Tenderer shall insert the answer here] Req. 206. Description of the map implementation The Supplier shall describe the techniques that will be implemented allowing fast access to the data in the various themes, and the ability to display the data almost instantly when selecting new themes or when zooming, panning etc. This can for example include techniques such as cashing and preloads. [The Tenderer shall insert the answer here] PAGE 8 of 31 Req. 230. Description of integration and caching layer The Supplier shall describe how the integration and caching layer handles high demands of dynamic data. [The Tenderer shall insert the answer here] PAGE 9 of 31 1.2 THE TENDERER SHALL DESCRIBE THE OFFERED SOLUTION [THE TENDERER SHALL INSERT A DESCRIPTION OF THE PROPOSED SYSTEM HERE] PAGE 10 of 31 2 FULFILLMENT OF THE REQUIREMENTS This chapter contains the requirements from all the Contract Appendixes. Each requirement is described with following attributes: Number Requirement Number from the actual Contract appendix. Description A brief description of the requirement. Type Minimum requirement: Minimum requirements are requirements that must be fulfilled in order to make the tender valid. Important requirement: Important requirements are requirements that the Customer considers important for the proposed solution. The fulfilment of the requirement will be included in the evaluation of the offer as described in the tender specification (Udbudsbetingelserne). Information requirement: Information requirements is an Important requirement asking the Supplier to give a detailed answer to a specific question given in the requirement. The description must be included in Appendix 3B section 1.1, in which a specific field is allocated to each answer to each information requirement. The answer to the information requirements will be included in the evaluation of the offer as described in the tender specification. Fulfilled The Tenderer shall indicate if the requirement are fulfilled (yes), partly fulfilled (partly) or not fulfilled (no) by the offered System. Comment The suppliers description of how partly fulfilled requirements are fulfilled or other comments from the supplier. The description can be made by a reference, e.g. to chapter 1. In this appendix. PAGE 11 of 31 2.1 REQUIREMENTS FROM CONTRACT APPENDIX 3A Number Description 1 Mock-up as main design 2 Type Fulfilled (yes, partly, no) Comment Minimum YES N/A Adjust according to test results Minimum YES N/A 3 Participating in on-going design process Minimum YES N/A 4 Lack of update of Mock-up Important 5 Differences between requirements and Mock-up Important 6 Platforms Minimum YES N/A 7 Browser support Important 8 No plugins Important 9 Optimization for different layout Minimum YES N/A 10 Detect User platform Minimum YES N/A 11 Automatic scaling to screen resolution Important 12 Landscape and portrait Important PAGE 12 of 31 Number Description Type 13 Linking to User Interface Important 14 Embedding the User Interface Important 15 Zoom Icon Important 16 Footer Important 17 Header Important 18 Facebook button Important 19 Twitter button Important 20 Background maps Minimum 21 Change of background maps Important 22 Automatically switch to failover map Important 23 Automatically switch to primary map Important 24 Miniature maps Minimum 25 Layout of miniature maps Important 26 Stamps on Miniature maps Important 27 Initial zoom level Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A PAGE 13 of 31 Number Description Type 28 Showing the position of the User Important 29 Showing the blue dot behind icons Important 30 Hovering Important 31 Click on the map Important 32 Popup Important 33 Touching Important 34 PC Important 35 Tablet and smartphone Important 36 Displaying data themes Minimum 37 Selecting data themes Important 38 Icons in the data themes Important 39 URL parameter control Minimum 40 URL parameter content Important 41 Priority between URL parameters and configuration files Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A PAGE 14 of 31 Number Description Type 42 Number of URL parameter calls Important 43 Follow industry standards Minimum 44 Reduction of coordinates Important 45 Reduction of roads Important 46 Reduction of information Important 47 Generalisation of icons Important 48 Hovering (Icons) Important 49 Restrictions on generalisation of icons Important 50 Display of more than one icon per location Important 51 Icons for double icon Important 52 Generalisation of traffic conditions Important 53 Zooming out Important 54 Zooming in Important 55 Generalization Information Fulfilled (yes, partly, no) Comment YES N/A N/A N/A PAGE 15 of 31 Number Description Type 56 Critical announcements Minimum 57 Yellow information box Important 58 Dynamical Important 59 Multiple critical announcements Important 60 Reduction of Yellow information box Important 61 Small box Important 62 Subscription Minimum 63 Link in hover information Important 63A Subscribed themes Important 64 Subscription e-mail Important 65 Confirmation e-mail Important 66 Users administrative interface Important 67 Access to Users administrative interface Important 68 E-mail cancelation Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A PAGE 16 of 31 Number Description Type 69 Update with cancellation option Important 70 Administrative interface Important 71 Updates based on Yellow information boxes and icons Important 72 Updates Important 73 Renewal Important 74 Log Important 75 Different sections Minimum 76 Use of icons Important 77 Car Traffic Minimum 78 Themes of car traffic Important 79 Typical traffic popup ‘inside’ Control Panel Important 80 Typical traffic popup when clicking a road segment Important 81 Live traffic Important 82 Typical traffic Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A PAGE 17 of 31 Number Description Type 83 Lorry traffic user interface control panel Minimum 84 Drop down Important 85 User interface Control panel Important 86 Download or print webpages Important 87 Download of document Important 88 Clearance height Minimum 89 Clearance height icon Important 90 Clearance height administrative tool Important 91 Active municipalities Important 92 Non active municipalities Important 93 Pop up information Important 94 Icons with numbers Important 95 Pop up for Clearance Heights Important 96 Icon types Important 97 Initial view Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A PAGE 18 of 31 Number Description Type 98 Entering height information Important 99 Disclaimer Important 100 Weight restrictions Minimum 101 Two options Important 102 Showing Heavy Goods Road Network Important 103 Showing structures and Webnumber field Important 104 Coloring of roads Important 105 Showing icons Important 106 Pop up information Important 107 Color of icons Important 108 No Web-number Important 109 Disclaimer for Heavy Lorries Road Network Important 110 Entering Web-number Important 111 Road classes document Important 112 Administrative tool for roads Important Fulfilled (yes, partly, no) Comment YES N/A PAGE 19 of 31 Number Description Type 113 Clicking on road segments Important 114 Using FOT Important 115 Download of segments ID Important 116 Resetting Important 117 Upload Important 118 Dangerous Goods Road Network Minimum 119 Icons Important 120 Coloring of selected roads Important 121 Specific provisions icon popup Important 122 City icons Important 123 Link to further information about the Dangerous goods road network Important 124 Road Train Road Network Minimum 125 Showing the Road Train Road Network Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A PAGE 20 of 31 Number Description Type 126 Four layers Important 127 Text pop ups Important 128 Detour routes Important 129 Parking facilities Minimum 130 Parking facilities information Important 131 Icons for parking facilities Important 132 Data about parking facilities Important 133 Pop ups Important 134 Real Time Parking Area Minimum 135 Parking Area information Important 136 Real time parking area information Important 137 Icons for Real Time Parking Area facilities Important 138 Data about Real Time Parking Areas Important 139 Pop ups Important 140 Traffic information Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A PAGE 21 of 31 Number Description Type 141 Warm asphalt Minimum 142 Data availability for Warm asphalt Important 143 Yellow information box Important 144 Dynamical Important 145 Reduction of Yellow information box Important 146 Small box Important 147 Subscription to Warm asphalt Important 148 Display cycle routes Minimum 149 List of cycle routes Important 150 Highlighting cycle routes Important 151 Download of all GPS coordinates Important 152 Download of specific GPS coordinates Important 153 Winter conditions Minimum 154 Winter themes Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A YES N/A PAGE 22 of 31 Number Description Type 155 Slippery roads Important 156 Hovering winter conditions Important 157 Snow clearing Important 158 Icons about municipalities Important 159 Location of snow clearing vehicles Important 160 Temperature Important 161 Wind conditions Important 162 Hovering slippery roads icon Important 163 Configuring Minimum 164 Obsolete configuration files Important 165 Editing configuration files Important 166 Administrator interface Important 167 Protection against hacking Important 168 Configuration parameters Important 169 Separate interface Important 170 Output formats for 3rd parties Important Fulfilled (yes, partly, no) Comment YES N/A PAGE 23 of 31 Number Description Type Fulfilled (yes, partly, no) Comment 171 Data output format comments Information N/A N/A 172 Implementation of the different operating modes Important 173 Additional implementation of the different operating modes Important 174 Read data theme as WMS and WFS Important 175 The system shall support usage of Google Maps for Works as background map Minimum YES N/A 176 The system shall support usage of GST background map Minimum YES N/A 177 The system shall support usage of FOT road network Minimum YES N/A 178 The system shall support usage of all specified data from VD GeoCloud Minimum YES N/A 179 The system shall support usage of bridge data Minimum YES N/A PAGE 24 of 31 Number Description 180 The system shall support usage of all specified data regarding bicycle routes 181 Type Fulfilled (yes, partly, no) Comment Minimum YES N/A The system shall support usage of Traffic conditions Minimum YES N/A 182 The system shall support usage of E-certificates Minimum YES N/A 183 The system shall support usage of Webcams Minimum YES N/A 184 The system shall support usage of Vinterman data Minimum YES N/A 185 The system shall support usage of ferry data Minimum YES N/A 186 The System shall be able to read the status of each lane in the Limfjord Tunnel Minimum YES N/A 187 The system shall support usage of Limfjord Bridge data Minimum YES N/A 188 The system shall support usage of Trafikman2 data Minimum YES N/A PAGE 25 of 31 Number Description 189 The system shall support usage of Real Time Parking area data 190 Type Fulfilled (yes, partly, no) Comment Minimum YES N/A The system shall support usage of Warm Asphalt messages Minimum YES N/A 191 Announcements Minimum YES N/A 192 Typical traffic data Minimum YES N/A 193 GPX data Minimum YES N/A 194 Prepared for further development Minimum YES N/A 195 Prepared for 3rd party development Important 196 Encryption of source code Important 197 Environments Important 198 Testing of changes Important 199 High load simulation Important 200 Automatic tool to measure response times Important PAGE 26 of 31 Number Description Type Fulfilled (yes, partly, no) Comment 201 Easily configuration of automatic tool Important 202 IT Reference Architecture Policy Important 203 Description of the IT architecture Information N/A N/A 204 New types of integrations to other IT systems Information N/A N/A 205 Time synchronization Important 206 Description of the map implementation Information N/A N/A 207 Development tools Important 208 No loss of data Important 209 Robust if breakdown of a data source Important 210 Service level Goals Minimum YES N/A 211 Training of System administrators Important 212 Location of training Important PAGE 27 of 31 Number Description Type 213 Accessibility Important 214 Incident handling Important 215 ITIL compliance Important 216 Amount of data and transactions Important 217 Future amount and number of transactions Important 218 Using Google Analytics Minimum 219 Google analytics and event tracking requirements Important 220 Requirements for Google Analytics Important 221 Functionality of Google Analytics Important 222 Flexible User interface Minimum 223 Non independence of Users web page Important 224 Automatically adjustment to iframes Important Fulfilled (yes, partly, no) Comment YES N/A YES N/A PAGE 28 of 31 Number Description Type Fulfilled (yes, partly, no) Comment 225 Redirection Important 226 Security Important 227 Monitoring of data sources Important 228 Secure login to integration and caching layer Important 229 Scalability of Integration and caching layer Important 230 Description of integration and caching layer Information N/A N/A 230A Dynamic data via integration and caching layer Minimum YES N/A 231 Integration to traffic data Important 232 Database for configuration data Important 233 Database for subscription data Important 234 Establishment of the operation environment Minimum YES N/A 235 Responsibly for the capacity Minimum YES N/A PAGE 29 of 31 Number Description Type 236 Documentation Important 237 Automatically up- and downscaling of capacity Important 238 Test of capacity, scalability and security before start of operating Minimum 239 Operation and monitoring the operation Important 240 Procedures for handling alarms Important 241 Maintenance of the operation environment Important 242 Service windows Important 243 Responsible for the capacity needed Important 244 Operation support Important 245 Responsible for all incidents in the operation Important 246 Advice to the Customer Important Fulfilled (yes, partly, no) Comment YES N/A PAGE 30 of 31 Number Description Type 247 Backup and restore services Minimum 248 Backup media location Important 249 Monitoring of backup Important 250 Restore service Important 251 Security management Important 252 Certify that the security procedures are applied and respected Important 253 Inspection of the security process Important 254 Contingency plan for restore of services Important 255 Using API from Google Maps Important 256 Using components from Google Map API Important 257 Entering origin and destination Important 258 Route from Google Maps API Important Fulfilled (yes, partly, no) Comment YES N/A PAGE 31 of 31 Number Description Type 259 Choosing among several suggestions Important 260 Subscriptions Important 261 Selection of time period Important 262 Selection of traffic information types Important 263 Routes matching Important 264 Monitoring changes of information types Important Fulfilled (yes, partly, no) Comment
