JOURNEY PLANNER REF. NO. : SPAD/RFP/009/10/2014 - Clarification on Technical Compliance Item 1.1.4 (Page 2) 1.2.3 (Page 3) 1.4.2.1 (Page 4) 1.4.2.2 (Page 4) Statement Question Answer Able to validate the initial real-time input/data received from all the data sources above Q1 . Can we get more information about the validation required. A generic validation method to enable vendor to perform the necessary checks on data received from multiple sources for e.g. route data from different transport operators (which will have different coding on data such as public transport stops). An example is KL Sentral where many transport operators provides service and uses different codes for their stops and trains. The ability to quickly validate these data will have an impact on the search engine Able to validate the initial input/data received above from stage bus/rail operators Q2. Can we get more information about the validation required. Similar to Q1. Able to fetch service disruption notification social media account for all PT modes (bus & rail) involved Q3. Can we get further elaboration on this point please Able to provide the service Q4. Can we get further disruption info received elaboration on this point from the social media to please. journey Planner application and also S.P.A.D website. Some of the public transport operators (e.g. ERL, RapidRail), may publish disruption notification via social media must faster than updating in their system. The journey planner should be able to catch social media updates (e.g. from Twitter) from these operators. Similar to Q3 4.3.1 (Page 11) 4.15.8 (Page 15) 4.15.22 (Page 16) 4.16.3 (Page 16) 4.19.2 (Page 18) The proposed solution for the web application must be fully compliance to IE7 and above, Mozilla Firefox, Safari and Google Chrome client web browser. List all the browsers & versions supported and the level of usability in the respective browsers. Q5. In terms of IE, our Not a concern platform supports only IE 9 and above, will that be a concern? The application logs must be stored separately from the application binaries so that access is not available thru the application Q6. We would like to have more information about the nonpersistent cookies, (e.g. are we referring to sessions? ) Must be random and comply with rules for complexity, size and content: i.e. >= 7 character in length, contain mixed case, special character, and numerals, and should not be a dictionary word or proper name. (See SPAD password guideline) Q7. Which dictionary Standard the document is dictionary referring to? Non-Persistent cookies are stored in RAM on the client and are destroyed when the browser is closed. Session cookies is created when you create a session object. Session are Non-Persistent Oxford English Should time-out and disable access after a period of users’ inactivity (e.g. after 10 minutes idle) Q8. According to this point session time-out is 10 minutes. However, throughout the document it changed to 20 and 30 minutes. What is the exact session period required. Fall over interruptions (e.g. on loss of web/ application/database server): Q9. Can we get the full a) RSO – number service form of RSO, RTO, and performance to be provided RPO? from IT service due to a major incident. b) RTO - duration of time and a service level within which a business process must be restored after a disaster. a) RSO: 50% of service performance b) RTO: <= 2 hours The timeout numbers are meant as a guide. It should be configurable. For consistency, use 10 minutes. c) RPO: close to 0 Note: these metrics are confined to the primary site, DR site and Call Center c) RPO - period in which data might be lost from an IT service due to a major incident.
© Copyright 2024 ExpyDoc
