REPUBLIC OF INDONESIA THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE TERMS OF REFERENCE (TOR) FOR DEVELOPMENT OF CITY ROAD MANAGEMENT SYSTEM (CRMS) February, 2020 JICA Project Team |The Project for the Improvement of Regional Road Governance (PIRRG) TABLE OF CONTENTS 1. Background 2. Objective of the Services 3. Scope of the Services.. 3.1. CRMS Detailed Design Report. 3.2. Installation of IT Facilities 3.3. CRMS Development. 3.31. Basie Policy for CRMS Development. 3.32. Design Platform. 3.33. Database Design... 3.3.4. CRMS Design, Development of System API/Web Service.. Prepare User Manuals... ‘System Installation, Trial Run and Testing. Conduct Training... Revise Incorporating Feedbacks from the Users. Handover CRMS and Technical Support. 4. Implementation Schedule.. 5. Team Composi 6. Deliverables Requirements 7, Implementation Structure for CRMS Development Appendix-1: Database Framework Appendix-2: Design System Interfaces/Windows Appendix-3: Outline of Maintenance Planning Module Appendix-4: Standard Forms and Template i ‘CRMS Terms of Reference DKThe Project for the Improvement of Regional Road Governance (PIRRG) TERMS OF REFERENCE (TOR) FOR DEVELOPMENT OF CITY ROAD MANAGEMENT SYSTEM (CRMS) 1. BACKGROUND ‘The Project for the Improvement of Regional Roads Governance (the Project) is aim ta improve the regional roads governance through capacity enhance of Center of Facilitation for Regional Infrastructure (CFI) and local government (cities) through formulation of regional road database, development of management system, data collection in the pilot areas, formulation of maintenance budget plans using the road management system to be developed, implementation of pilot projects, etc Formulation of database framework and development of City Road Management System (CRMS) ate key activities of the Project. In order to enhance the capacity of CFRI and local government for roginal road governance, the Project is intending to develop CRMS by using IT Consulting Services (the Services) employing local software development company (the IT Consultant) based in Indonesia, ‘CRMS to be developed under the Project will be basically for pavement maintenance planning, which is commonly known as Pavement Management System (PMS) for regional roads. The term City Road Management System is used because the system may expand/upgrade to incorporate ather city road assets as well such as drainage system, culvert, retaining wall, and bridges. The CRMS to be developed under the Project will be exclusively run on the road database to be developed under the Project. 2. OBJECTIVE OF THE SERVICES ‘The main objective of the Services is to develop CRMS for CFRI and local government. The Services shall also prepare relevant documents related to development and operation of CRMS such as detailed design, user manuals, conducting training and technical support after completion of the CRMS development and the Project. 3. SCOPE OF THE SERVICES ‘The IT Consultant shall carryout the following tasks but not limited to: 3.1. CRMS Detailed Design Report The IT Consultant shall prepare a detailed design report based on the conceptual design prepared by the Project. The CRMS development work shall start after basic approval of the draft design by the Project. It is advised to prepare a prototype version of CRMS together with draft detailed design report in order to avoid misunderstanding on the required system functions, etc. CRMS shall develop in consultation with the Project and the end user. All feedbacks and comments to be provided by the Project and the users shall incorporate in the Final Detailed Design Report. The Final Detailed Design report shall submit together with the Final version of CRMS. 3.2, Installation of IT Facilities ‘The Project is intending to provide IT facilities (servers, etc.) to CFRI and twa lacal governments (cities) to install and run the CRMS on their own servers. Therefore, the IT Consultant shall install the 1 CRMS Terms of ReferenceThe Project for the Improvement of Regional Road Governance (PIRRG) TT facilities in CFRI and local government offices upon provided by the Project. Also, the IT Consultant is requested to recommend the suitable IT facilities to install CRMS at CFRI and local government (2 cities: Sukabumi in West Java and Tebing Tinggi in North Sumatra), 3.3. CRMS Development ‘The IT Consultant shall develop CRMS based on the conceptual design provided by the Project. The IT Consultant shall consider the conceptual design as reference only. The detailed design of CRMS shall carryout by the IT Consultant by themselves. If the IT Consultant wants to modify any of the ‘conceptual design, the IT Consultant shall consnit with the Project hefore reflecting the changes in the detailed design. The design and development of CRMS shall comply with the IT facilities to be provided by the Project to CFRI and the local government. If any modification is necessary during installation of CRMS to the IT facilities, the IT Consultant shall modify promptly by themselves without any additional cost. 33.1. Basie Policy for CRMS Development The IT Consultant shall develop CRMS considering the following basic development policies: ‘© Customized into users’ need ‘© Simple and user friendly + Balitable for future upgrade (source code and copyright to be provided to the Project) ‘* Affordability and sustainability (Cost and technology perspective) © Web-based operation + Relational Database + Incorporation of GIS ‘+ Internet (web) security and data backup system 33.2. Design Platform CRMS shall be developed in the following Design Platform: ‘© Operating System: Linux / Window ‘+ Database System: PostgresSQL / MySQL / Oracle / SQL Server ‘© Programming Language: Java / php / ‘© Method of Operation: Online / Offline © Language of Interface: Bilingual (English / Bahasa) ‘© Server Types: Dedicated Web Server / Cloud Computing © Base Map: BIG Map/Open Street / Esti (ArcGIS) web map / Google Map / QGIS fete. Note: Design platforms in bold letters are recommended by the Project. However, the IT Consultant is free to propose alternative platform if they will be better than the recommended above. In case of alternative platform 1o be proposed by the IT Consultant, the advantages against the recommended above shall be specified and explained to the Project. Design platforms and IT facilities to be provided to CFRI and local government shall be compatible each other. 2 CRMS Terms of ReferenceThe Project for the Improvement of Regional Road Governance (PIRRG) 3.33, Database Design The IT Consultant shall proparc a detailed database desigh based ou dalabuse framework attached (Appendix-1), Database design shall he designed in a flexible platform considering future expansion of database. General architecture of CRMS database is shown in Figure 1. Figure 1 shows the conceptual architecture of Database and the IT Consultant shall prepare a detailed database design and shall include in the detailed design report of CRMS. + + Connection Using APE API: Application Programming Interfoce (Web Service) Figure 1 General Architecture of the Database CRMS shall develop in close cooperation among the Project, the Project Counterpart and the IT Consultant. The following data type, but not limited to, shall include in the database design, ‘© Road Administration Data (Management Agency, Road Administrat City, ete.) ‘e Location (Province, ‘+ Road Network Data (Road Name, Road Class, Width, Pavement Type, Number of Lanes, tc.) © Asset Inventory and Condi + Pavement + Side Drain + Service Lane + Culvert + Median/Lane Separator + Motoreyele Lane + Shoulder + Bicycle Lane + Footpath/Sidewalk + Bus Stops / Bus Bay + Street Lighting + Guard Rail + Traffic Lights + Others 3 ‘CRMS Terms of Reference‘The Project for the Improvement of Regional Road Governance (PIRRG) ‘Maintenance Work Monitoring / Repair History + Traffic Volume Repair Unit Cost © Others ‘The detailed data items/field/attributes (draft) is provided in database framework as attached Appendix-1. If there will be any changes in the database framework, the Project will provide such information in due course. 3.3.4. CRMS Design (1) Overall Structure The overall structure of CRMS is shown in Figure 2. Figure 2 is conceptual structure only and IT Consultant shall review the conceptual design and prepare a detailed design by themselves. s+ !Comection Using APL Figure 2 Overall Structure of CRMS @) CRMS Function Depending on the perspective CRMS users’ (CFRI & Local Government), CRMS shall have the following functions at the Front-end: ‘Table 1 CRMS Functions (Tentative only) ‘CRMS Functions in (CFRI Version) | CRMS Function in Local Government Version 1. Data Management 1. Data Management + Data input, Data Importation from * Data Input (Administration Data, Road Local Governments. Integration. Inventory, Road Assets, Traffic Volume, ete.) Output, ete. ‘+ Data Import (Road Inspection Data) 4 CRMS Terms of ReferenceThe Project for the Improvement of Regional Road Governance (PIRRG) + Road Video Screening 2. Monitoring (Network, Budget & Road | 2. Monitoring and Analysis (in Tabular and Map) Maintenance Works) + Inventory Data Display + Inventory and Inspection Data + IRI Data Display Display (Tabular & Map) + Visual Inspection Data Display + Budget Monitoring + Field Verification Data Display + Inspection Works Analysis 3. Evaluation and Assessment a " + Benchmarking Evaluation + Performance Evaluation 4, Budget Allocation Planning 3. Maintenance Budget Planning + Setting of Conditions + Formulation of Budget Plan + Simulation of Budget Allocation + Medium-term Plan Plans + Annual Plan + Monitoring of Maintenance Works 5 ‘ical Report + Static Report + Static Report + Dynamic Report (user's + Dynamic Report (user’s customization) customization) In addition to the above-mentioned functions at the front end of CRMS, CRMS shall have system administration module at the back end to administer the system as a whole including system revise, system troubleshooting, data backup, user management, etc.). Administration module shall also manage the master data (i.e. common to multiple data category) such as; ‘List of Road Name, Road Number and Road ID * Link Name and Link 1D ‘© Administrative Data (province, city, ete.) ‘© Repair Work Method © Repair Work Unit Cost © Pavement Damage Category Drop-down Menu List © Others (3) User Level Depending on the perspective CRMS users’ (system administrator & ordinary user), CRMS shall have the following user levels: A. Administrator (Back End User) 3 CRMS Terms of Reference‘The Project for the Improvement of Regional Road Governance (PIRRG) © Admin Level | Admin Level | user shall have full control of the system including any modification of the system, © Admin Level 2 Admin Level 2 user shall have limited rights to modify the system such as eligible for modifying master tables, copying data to data server directly and data backup. B. Ondinary Users (Fruut Bud User) © User Level 1 In addition to utilization of all functions of the system, User Level | shall have rights to create user account etc. © User Level 2 User Level 2 shall have rights to utilization of all functions of the systems. © User Level 3 User Level 3 shall have limited rights to view the data only (viewer). It is advised to develop the user management module in a flexible way (cheek box & style) to deploy/un-deploy the particular function to the specific user. (4) CRMS Modules (Front End) CRMS will comprise of the following modules: 2) Data Inputting Module ‘The IT Consultant shall develop the inputting module for inputting of road inventory, asset inventory, road unit cost, traffic volume, etc. IT Consultant shall develop road administration sub-module to input administrative {administrative location, management agency, etc.) and predefined information (road coding/naming, repair method, repair unit cost, criteria, etc ), ete and these privilege shall bbe given to the higher level of user such as admin level 1, 2 and user level 1. b) Road Inspection Module ‘The IT Consultant shall develop the inspection module to import inspection data (IRI ‘measurement, pavement visual inspection, pavement field verification and facility inspection data), stote and management of condition state (inspection) data of the road assets The data from IRI measurement system and visual inspection system shall import/copy into the database either using import function or direct copying into the database. In case of big volume data, importing data using internet may not be suitable. Therefore, a tool to copy the inspection data from external hard-drive shall develop the at back-end. Import tool at front-end shall develop to import small volume data with restriction on import file size (ie a restriction on max. data volume shall set in order to prevent overloading of webserver). ‘Since inspection surveys may carryout every year, the imspection data shall store in the yearly folder 6 CRMS Terms of ReferenceThe Project for the Improvement of Regional Road Gavernance (PIRRG) Since data collected in IRI will use for video screening, results of video screening will be used for pavement visual inspection and result of visual inspection will be used for field verification, proper data shall be copied from the database in order not to mismatch the data. The following cycle shall follow while importing data from database and inspection systems, Input Inventory Data IRI Mesurement Survey Video Screening Visual Inspection Field Verification Legend: —> _Inputimport Data into DB 1c” Import Data from DB to Module/Mobile/Survey Devices| 4 Take Reference of Data Stored in DB Figure 3 Data Relationship among ifferent System Modules CRMS shall provide access to other systems (IRI data processing, video screening, inspection system, field verification)_to copy and import data from CRMS. Therefore, IT Consultant shall closely work with the developer of IRI Data Processing System, Video Screening System, Visual Inspection System, and Field Verification System. Data Importing Format: Since data in vehicle inspection system, video sereening system and visual inspection system will be in GIS format, IT consultant shall select an optimal method to copy/import the date from above mentioned system to CRMS or vice-versa either in GIS format (Shape file) or XML or any other format that will be convenient to combine/merge data in CRMS keeping data compatibility among the systems. Also, data may need combine such as inventory and inspection data or inspection data only such as pavement inspection data; vehicle inspection (IRI) and visual inspection data (Rut, Crack, Potholes, etc.) to prepare data in a single table. However, this combining/merging task may cary out after coping/importing the data separately (individually) in database and then ‘combine them within the database system. IT Consultant shall closely work with the developer of IRI Data Processing System, Video Screening System, Visual Inspection System, and Field Verification System to share and use the data among the systems. Status of Data Import: The system shall have a function to display status of data import from IRT Measurement System, Video Screening, Visual Inspection and Field Verification. i CRMS Terms of Reference° 4) e) The Project for the Improvement of Regional Road Governance (PIRRG) This function shall develop in a separate tab under inspection module and the function shall display data importation log (tabular summary: date of import, section information, etc.) and GIS layer to check in map also. Upon successful completion of data import, data import completion notification (import date, ete.) shall also send to inspection system from where the data are to be imported. When importing data, data overlapping shalll be checked in order to avoid data duplication and overwriting. A warning message shall show by the system and the following action shall take accordingly. Phenomena Deseription Action, If data is tried to import | (1) Show warning message ® Data Duplication | more than one time for the | (2) Ask the user whether to overwrite (Fully of Partially) | Same section within a year. the existing data or not. (3) DONOT accept data duplication Map Module The IT Consultant shall develop map module using open street map as base map or the MAP to be provided by the Ministry of Public Works and Housing (ie. Badan Informasi Geospatial (BIG) National Mapping Agency of Indonesia because itis the official map (BIG Map) (hitp:/Aanahair.indonesia.g0.id/portal-web). In case of BIG map, MPWH shall provide It officially in due course. The data stored in database (inventory, inspection and planning) shall display in the map using data layers and shall be selectable by the user. There is a possibility that two different maps may use such as Open Street Map for CRMS (Local Government Version) and BIG map for CFRI Version of CRMS. Road Video Screening Module The IT Consultant shall develop road video screening module to support to identify the road pavement condition by analyzing the images/video taken during the IRI measurement survey. The module shall be capable to show road videos by road/route. Pavement inspection priority shall divide into three categories as shown in the system windows design (Appendix-2-1), This module shall also have a function to check the status of completion of video screening preferably in GIS layer. Data Monitoring and Analysis Module ‘The IT Consultant shall develop monitoring and analysis module to display and analysis of road inspection data (tabular and images) in GIS (open street map) using XY data collected during road inspection survey. Also, inputted road inventory and asset data shall also display in the map. The monitoring analysis module shall have search and filter/sorting function for convenience of the users. Similarly, edit, export and link to map functions shall be provided in each system windows. As for CFRI, budget implementation status (DAK budget only) shall also display in CFRI version of CRMS. This module shall also consist a function to display pavement condition based on IRI category and severity damage. The system windows designs are provided in Appendix-2-1 and Appendix-2-2. 8 ‘CRMS Terms of Reference8) hy dD DS) The Project for the Improvement of Regional Road Governance (PIRRG) Maintenance Planning Module ‘The IT Consultant shall develop the planning module for formulating maintenance plan by utilizing inventory data, inspection data and prioritization criteria. Repair methods, repair work unit costs, criteria for selection of repair method, repair priority shall set up in the road administration sub-module. The general algorithm/flowchart for this module are provided in Appendix-3 and the detailed will be provided by the Project in due course. The module shall be capable of formulating budget request for DAK (submit to BAPPENAS), provincial funding and self-funding (city funding) from the long list (budget plan) Project Formulation and Contract Packaging Module ‘The IT Consultant shall develop project formulation and contract packaging tool based on criteria to be provided by the Project in due course Reporting Module ‘The IT Consultant shall develop reporting tool to generate static (i.e. defined format) report and dynamic (j.¢, user's selection). The format/template of static report will be provided by the Project in due course. The IT Consultant shall also develop analysis tool to generate the report in tabular, graphical, ete. format. Integration Module (to integrate with other systems) ‘The IT Consultant shall develop integration tool to integrate CRMS with other system such as SIPDID, Budget Monitoring, and IRMS (Indonesia Road Management System for National Roads). The Project will provide the details of the system and data to be integrated in due course. ‘Therefore, the IT Consultant shall design and develop CRMS considering relational database for possibility needs of integration with other systems, Documents Module ‘The IT Consultant shall develop document module to store relevant documents such as user ‘manual, road maintenance manual, norms and standards, and project related documents (As-buit, |5|8]s | RRR ERR ER RFR RR 15 ‘CRMS Terms of ReferenceThe Project for the Improvement of Regional Road Governance (PIRRG) DAPA‘TYP, DATA ATTRIBUTE AND DATA DEFINITION 16 ‘CRMS Terms of Reference l‘The Project for the Improvement of Regional Road Governance (PIRRG) DATA TYP, DAIA ATIRIBUTE AND DATA DEFINITION [a Pon ira. ear Zz a ae Bs Be raz ‘a ea Bo 2 a] 2a Bs "ae mr 235 2 20] 20] ae 243 207] 2 26 25 = 3 3 a 5 261 Esl a 255 ELSIS/ 3 ]3]2/3) & i 7 (CRMS Terms of Reference‘The Project for the Improvement of Regional Road Governance (PIRRG) [DATA TYFE, DATA ATTRIBUTE AND DATA DEFINITION [en f 22 2] a] 25] ae] 727] 2] Ed 0] I 22 2 2 35 ea 27 2H Ed 300 om i] a] aa a] 37] sae] sae S] Sie || fel) ee ele }3 |) (ee felslelslslelelsls 18 (CRMS Terms of Reference aThe Project for the Improvement of Regional Road Governance (PIRRG) DATA TVPE, DATA ATTRIBUTE AND DATA DEFINITION 19 CRMS Terms of ReferenceThe Project for the Improvement of Regional Road Governance (PIRRG) DATA TP, DATA ATTRIBUTE AND DATA DEEINETION El: EEEREREEER i BEEBEBEBEBEEEEERIEESEEEERERBEEBEES 20 ‘CRMS Terms of Reference aThe Project jor the Improvement of Regional Road Governance (PIRRG) DATA TVPF, DATA ATTRIBUTE AND DATA DEFINITION ra ras] 6] mI oI a 3 So 306 5 21 ‘CRMS Terms of ReferenceThe Project for the Improvement of Regional Road Governance (PIRRG) Appendix-2-1 (for Local Guverumeut Version) and Appendix-2-2 (for CFRI Version): Design Syntem Interfaccs/ Windows Please refer to PPT file enclosed with this TOR. 2 CRMS Terms of Reference GHThe Project for the Improvement of Regional Road Governance (PIRRG) Appendix-3: Outline of Maintenance Planning Module (1) Workflow of Maintenance planning ‘The workflow for formulation of maintenance planning is shown in Figure 4 Figure 4 Workflow for Formulation of Maintenance Planning (2) Flowchart of Maintenance Planning Module 3B CRMS Terms of Reference‘The Project for the Improvement of Regional Road Governance (PIRRG) Import Repair Unit Cost and eel work 4... Prepare Long List of Repair ‘Repaie Work Selecton Criteria | CSR freee aa fe cee ete Prepare List for Held Bost Availity and MaitenanceInvesient Poly “41 ld Variation Survey Ress | Prepare Badget Request List BudetPlan en, bs poeererar Figure 5 General Flowchart of Maintenance Planning for Local Government 24 CRMS Terms of Reference (‘The Project for the Improvement of Regional Road Governance (PIRRG) _ ourrur (a (aie vaerinann Dat”) 4 Import Budget Request of Fall Reis ‘Government (LG) bianchi, I Prepare Budget Request List Tor Fach City + ‘Caniyout Beuele Mary Evaluation t cplon leon, Prepare Budget Request List “~ Budget Allbeation Criteria for LG t= Master Table (Budget Plan) sto Budget Constant (NovYes) Mig-Term ad Prepare Budget Request |__| Budget Avaability Info for “Aas Plan (Medium-tera/Annual Plan) t “Annual Repair Bast Proposal Submit Budget Proposal to | ‘MOF (DAK) ‘MOF via BAPPENAS: | ergo Update Budget Monitoring System with Approved Project + End | Figure 6 General Flowchart of Maintenance Planning for CFRI (3) Screen transaction of Maintenance Planning Process Visual Inspection Table Long list of repair candidate segments a 1 ; = [S| |= [oe [= - => = ]- 2 hed ‘Selection criteria, & NT ae, I Low ————> Mid-Team plan é High ———— Annual Plan coerce Figure 7 Preparation of Long List for Field Verification Works 25 CRS Terms of ReferenceThe Project for the Improvement of Regional Road Governance (PIRRG) Long list of repair candidate segments Figure 8 Preparation of Long List of Repair Works (Budget Plan) Figure 9 Preparation of Medium-Term and Annual Plan Annual maintenance plan Figure 10 Preservation of Repair Work Records 26 ‘CRMS Terms of Reference (‘The Projec for the Improvement of Regional Road Governance (PIRRG) Appondx-4; Standard Forms and template ‘To be provided later after confirming with Local Government and CFRI. 27 (CRMS Terms of ReferenceREPUBLIC OF INDONESIA THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE Ministry of Public ‘Works and Hausing Draft System Design of CRMS in (Local Government Version) February, 2020 JICA Project Team ¥ 2 jica Appendix-2-1OuTLINE of CRMS CRMS Function in Local ST ae oNg) 1. Data Management 2. Monitoring 3. Assessment and Analysis 4. Budget Allocation Planning 5. Reporting 1. Data Management 2. Monitoring 3. Assessment & Analysis 4. Formulation of Maintenance Plan 5. Reporting ek Dear Bec THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCESTART MENU PCa re COT cs Dea LuCD) Peay PONS Welcome to the CITY ROAD MANAGEMENT SYSTEM. Data Management M & Analysis Planning GIs Map Locin Report ‘THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEVIDEO SCREENING DATA MANAGEMENT FACILITY INVENTORY | [search IMPORT = Save SETTING ee Edit DATA MANAGEMENT > DATA INPUT > ROAD INVENTORY sm | Province Kola Route inf Route lenath Direction Lanes: with Tete (nameinumnber) (m) (2) (m) Volume ¥ v v v v v v 7 1 2 3 4 5 THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCESERVICELANE | MOTOR-CYCLELANE DATA MANAGEMENT OAD SHOULDER BICYCLE LANE FOOTPATH/SIDEWALK ‘SIDE DRAIN/DITCH TANE SEPARATOR ROAD INVENTORY SEARCH FUNCTION BussTor/eusBay | GUARDRAIL : a Ls ; IMPORT a Save VIDEO SCREENING SETTING SS eS Z Edit DATA MANAGEMENT > DATA INPUT > ROAD INVENTORY ow | yn S%22e | S88 | ven | Bm | an | ser | suene | repetn | pe | Ret | eet | saat | page Fo N | INVENTORY Legh Type ‘Spe Oh Type Date ‘Metod | Quertty | ReperGot | Raby: a ~~ vee pe ~~ Rede ~ Stee ~ Be ~~ . ae “ROAD INVENTORY” can expand data list when change Mark Eto Tis cl a wg ete oa nS Pa s SieaDATA MANAGEMENT ROAD INVENTORY FACILITY INVENTORY Pca eas Pa ‘VIDEO SCREENING DATA MANAGEMENT > DATA INPUT > IMPORT i IMPORT DATA, _————————— PAVEMENT INSPECTION (IRI) ree Reersacaea) enh FIELD VERIFICATION cre DRAG-AND-DROP Bemnucc yen Pere recut view RECORDDATA MANAGEMENT Prorat Pa VIDEO SCREENING re rrr Eun co eas Seah curen Prete PONTE LUCLy ROAD INVENTORY FACILITY INVENTORY IMPORT Eau DATA MANAGEMENT > DATA INPUT > SETTING Poutanen elas BUDGET CONSTRAINT REPAIR METHOD AND UNIT COST 3m Repair Method Repair cost 1 | overlay vases IDR /m? 2 | cutting 3 | Pothole patehing Teer 4 | crackseaiing veoee ‘THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEWreeecaid rg M&A Pramas POMC Lur) DATA MANAGEMENT DATA MANAGEMENT > DATA INPUT > VIDEO SCREENCING aaa 2 : THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEMONITORING & ANALYSIS DATA MANAGEMENT > MONITORING & ANALYSIS INSPECTION YEAR PRUs ; SEARCH FUNCTION v Search } or view v} ait er fan Bo Data Management > MONITORING & ANALYSIS > IRI DATA SIN Route infe D/W/Y XY (From) XY (To) Segment i (name/numter) (inspection) length (mmr/m) SEONG x a 1 foo 2 3 esl 7 Prag = - ROS MAP Export rit rok A OMEN SE A » SewPN nog MONITORING & ANALYSIS DATA MANAGEMENT > MONITORING & ANALYSIS. INSPECTION YEAR SEARCH FUNCTION VIEW {fst = J Data Management > MONITORING & ANALNSIS> VISUALINSPECTION 7] toaente ‘DMN | Damage | Wark | Damage w ‘Severity of 7a Comment | Photolink N | oamenumber) | unescton) | Tipe” | ee | Mesure comes < re x x a enn) z 2 cate 4 om z “Ly Boao Peng Poo cureny MAP Export THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEMONITORING & ANALYSIS DATA MANAGEMENT > MONITORING & ANALYSIS INSPECTION YEAR, SEARCH FUNCTION aE i FIELD VERIFICATI Data Management > MONITORING & ANALYSIS > FIELD’ EO | | meine) | unlehns core SYS. INTEGRAT| DocuMENT! Our ‘THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEMAP GISMAP POs M&A ie) mm 2cokmeri-t + Video screening A wieeotomark-2 okmath-3 eT Cos mm Goat 4 Moderate WRiData BZ) Be ioe corned mm Seve damaged Semcon Pret 2 Visual Een CEU) Damage Point Damage Type Severity of Damage EB Field Verification oO f » bf THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE 12 jicarg POT coe Pees euCn) Pires POU GIS MAP EB Field Verification © Survey Works Analysis = Vehicle Routes in 2019 Inspection Routes in 2018 = Visual wnepetin = BAD MAP THE PROJECT FOR THE IMPROVEMENT OF REGIGNAL ROADS GOVERNANCEMAINTENACE PLANNING CUNGaIS maa 7 5 = PLANNING > MAKE LIST Pers ee ‘SELECTION CRITERIA FOR CANDIDATE LIST SEVERITY OF DAMAGE BY VISUAL INSPECTION Peart) CANDIDATE LIST SEVERITY LEVEL 3 feds BUDGET PLAN ‘MID-TERM PLAN, ‘ANNUAL PLAN, MONITORING ANDIDATE LIST FOR FIELD VERIFICATION Route info Damagetype XY (From) XY (To) cals s/n (name/oumber) Beata Prete _— = ened cl ane avant Or Ra ae awceNGrE a jica)MAINTENACE PLANNING events wanes: j PLANNING > MAKE LIST SELECTION CRITERIA FOR LONG LIST(PROPOSAL LIST) SEVERITY OF REPAIR BY FIELD VERIFICATION SEVERTY LEVEL 5 Set BUDGET PLAN (MID-TERM PLAN < ANNUAL PLAN - te] ONDER LONG UST FOR REPAIR WORKS Sato paeae [ Dyaye Damage type | Repair Method Repairarea | Repair cost | Accumulated Severity < » 2 mar |__ Export ‘THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE 15 jica‘MAKE LIST ‘MID-TERM PLAN ‘ANNUAL PLAN, MONITORING MAINTENACE PLANNING Clas) PLANNING > BUDGET PLAN ea ee | see | eee ee suber nesounce ae haee tonal oak eau | province | Pad | ToraL = a 2 a = a THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEPca roe cod mig saa Beau) Pitan emo cure MAINTENACE PLANNING rg PLANNING > BUDGET PLAN BUDGET REQUEST THE PROJECT FOR THE IMPROVEMENT OF REGICNAL ROADS GOVERNANCE 7 feaMAINTENACE PLANNING Pca ner PLANNING > MID-TERM PLAN ro [ iweur APPROVAL BUDGET pees BUDGET PLAN Roe ‘ANNUAL PLAN, MID-TERM PLAN oweinio | ona | umasetvoe | Fepuirtdeunod | Repair arex ccumuisted | seventy | munnic am | omen ‘Gmone) ‘con on soe Peed S : . rs = 7 G . = b Senco 2 Anew = more | Prey « = ECM aeurea) ee a jfeaMAINTENACE PLANNING EOS PLANNING > ANNUAL PLAN INPUT APPROVA.. BUDGET eur) Bocas BUDGET CONSTRAINT EOUaea) ‘ANNUAL PLAN aaah Route info ohare Damage Type: Repair Method Repair area Tepaircost | Accumdated sn (cameroumer . ene ei Sa Ura) a x a = = 1 Peay 2 < ———— = PON geue is Pacver fon nishasacniaueT oc Feacuat caps eres » JicaNACE PLANNING MAINTENANCE PLANNING > MONITORING rete Be | ee | eer set 5 | oaraiou | steioe | 4,82, | "won | 0 0m) | arte, | meas MAKE LISTS. be) sara ce BUDGET PLAN Implemented the planed repair work ‘MID-TERM PLAN ‘ANNUAL PLAN, Un-implemented the planed repair work THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE Implemented the planed repair work exceptedREPORT REPORT > STATISTICAL SUMMARY INSPECTION YEAR y] IRI Condition Summary JALAN #4 IRI Conditic seek, a 8 = 45% 20% 10% 20% 30% 25% 25% Rowe te | haute eneth (rm) ae Slightly Severe Bamage | damages This figure shows the conditon rate on the route is worse than. average in Kota, ‘THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEREPORT STATISTICAL SUMMARY REPORT > SURVEY ANALYSIS VEHICLE INSPECTION YEAR 2. YEAR SELECT Route info S/N | (name/numb Route length Latest vehicle inspection date Inspection length " () THE PROJECT FOR THE IMPROVEMENT OF REGIOWAL ROADS GOVERNANCEREPORT REPORT > SURVEY ANALYSIS. Ones MOBILE INSPECTION YEAR M&A Onin co STATISTICAL SUMMARY nts Beau urea Plat enue THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE 23 jicaSYSTEM INTEGRATION ‘SYS"EM INTEGRATION > SIPDID PUNE ts rg Maa onic REPORT Brace ery) CRMS ee | Pre SiPDJD OST 17 pROse Fonsi enous ox enundt cars goneanANs z jftaDOCUMENTATION DOCUMENT Coy cUP * User Manual for CRMS binscaslsnsid * Standard Norms foe * Project Documents Sean rureny Pra OMe THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEADMINISTRATION Pace M&A CONS Ces Boao oue Pert EONS oi ADMINISTRATION User Administration S/N Name | Organization | E-mail Date Ranges Licenses Note aloluie New user THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEDATA FLOW ON VIDEO SCREENING PROCEDURE (DRAFT) impor” Sapa i) Procedures order f onary a — Pr arascrd i] eon Management System i. Visual Inspection Esk = Inspection Priority VIDEO SCREENIG DISPLAY LINE SHP by GIS Hi jfea) THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCEOutline on CITY ROAD MANAGEMENT SYSTEM (DRAFT) ae _ eral ~N a) iia Value ener Visual Inspection 7 and Maintenance Planning (vate a fepat Work ong Ut) and a (9) Monitoring info. and Maintenance Planning info. ne) __, (5) Data Management, Report A fear 7 \y yf sync — (8) Data Management and Maintenance Planning (wakes REPORT'S "3 Make polygon and splay 3 implemented range of visual inspection CRMs (Gab) Repair work THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE (772) ml: {and sho file) Field Verification PsREPUBLIC OF INDONESIA THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE Ministry of Public ‘Works and Housing Draft System Design of CRMS in (CFRI Version) February, 2020 JICA Project Team Ye jfta) Japan international Cooperation Agency Appendix-2-2OuTLINE of CRMS CRMS PMS Functions in (CFRI Version) PMS Function in Local erica) 1. Data Management 2. Monitoring 3. Assessment and Analysis 4. Budget Allocation Planning 5. Reporting 1. Data Management 2. Monitoring 3. Assessment & Analysis 4. Formulation of Maintenance Plan 5. Reporting re Doerr System 2 THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCECRMS Function for CFRI 1. Data Management 3. Budget Allocation - Statistical data management |- Criteria setting - Data import from LG - Budget plan (request to Bappenas) 2. Monitoring 4. Evaluation & Assessment - GIS map - Mid/Long term budget Budget Implementation simulation Bench-marking evaluation + THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE2. Monitoring * GIS map — Same function with in LG version — Data of selected cities (multiple) or all cities shown ee THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE2. Monitoring * Budget Implementation — DAK only — GAP analysis between annual plan & implemented 7 az ‘aiasetiuidialeedeamcl aes tte jen)3. Budget Allocation * Criteria setting — For budget allocation — Some factors (to be discussed) 8 a ‘THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE3. Budget Allocation * Budget plan — Function and export form shall be decided bw To bapenass a THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE4. Evaluation & Assessment * Mid/Long term budget simulation — Condition setting — Simulation under some scenarios — Algorism of the simulation shall be discussed later 10 a THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE4. Evaluation & Assessment * Bench-marking evaluation — Performance measure of each city — To consider next assessment and technical support for city Performance measure a ‘THE PROJECT FOR THE IMPROVEMENT OF REGIONAL ROADS GOVERNANCE