Standard Insurance Co., Inc.

CRMS Master Plan

2008
This document describes the
proposed CRMS Master Plan and
corresponding proposed detailed
tasks to accomplish it.

Engr. Leovin L. de Ramos and Engr. Oliver B.

Barbosa

08
 CRMS Updates 2
008

TABLE OF CONTENTS

CRMS MASTERPLAN...........................................................................................6

PHASES OF IMPLEMENTATION.............................................................................7

............................................................................................................ .............7

Phase 1 – Documentation of existing functions, operation and issues...................7

Issue on Non-standardized addresses.......................................................... ........................7
Issue on Unplotted policies in I90............................................................................. ..........11
Issue on Non-functional accumulation monitoring functionality.........................................15

Phase 2 – Resolving existing issues, expanding functions and operation.............15

Metro Manila to Nationwide Datasets.................................................................... .............15
Addition of Hazard Layers for CRMS Version 1.0 Phase 2...................................................16
Refining the accumulation monitoring functionality...................................... .....................17
Additional Proposed Functionalities of CRMS...................................................... ................17
Propagating from Visual Basic CRMS to ArcGIS CRMS........................................................22

Phase 3 – Involving the Risk Management Department and Branches in the CRMS
procedure........................................................................................... .............24
Proposed workflow.................................................................................... .........................24
Infrastructure Setup..................................................................................... ......................25
Personnel.............................................................................................. .............................27
Tools.................................................................................................................... ...............28
...................................................................................................................................... .....30
Training Component..................................................................................... ......................31

Phase 4 – Proposal and implementation of procedural policies...........................33

Draft procedures and policies....................................................................................... ......33

ANNEX.................................................................................................... .........33

Initial Automation excel macro to categorize addresses in the i90 database.......33

Arcview SCRIPT to Automate policy locations based on i90 municipality address

info ................................................................................................................35

Proposed Work Program of ITD – Continued Programming of CRMS within Visual

Basic...............................................................................................................38

Submitted Proposal – Reprogramming CRMS within ArcGIS................................39

2 | Page
 CRMS Updates 2
008
Introduction................................................................................................................. .......39
Purpose.......................................................................................................... ....................39
Scope of the Project................................................................................ ...........................39
Methodology......................................................................................... .............................39
Timeframe.................................................................................................................. ........40
Costing................................................................................................................... ............40

LIST OF FIGURES

FIGURE 1 THE PROPOSED CRMS MASTER PLAN FOR SICI......................................6

FIGURE 2 STAGES OF IMPLEMENTATION FOR THE PROPOSED CRMS MASTERPLAN..7

FIGURE 3 EXISTING ADDRESS INPUT INTERFACE IN THE I90 SYSTEM.....................8

FIGURE 4 EXISTING STORAGE OF ADDRESS RECORDS WITHIN THE I90 DATABASE. .9

FIGURE 5 CATEGORIZED ADDRESS RECORDS IN THE CRMS DATABASE, SHOWING

ENTRIES ON DISTRICTS.......................................................................................9

FIGURE 6 CATEGORIZED ADDRESS RECORDS IN THE CRMS DATABASE, SHOWING

ENTRIES ON PROVINCES...................................................................................10

FIGURE 7 ADMINISTRATIVE BOUNDARY MAPS THAT WILL BE USED FOR

AUTOMATING LOCATION OF I90 POLICIES WITHIN THE CRMS...............................13

FIGURE 8 BARANGAY BOUNDARY OVERLAIN ON THE GOOGLE EARTH FOR DIRECT

PINPOINTING OF THE LOCATION OF A POLICY.....................................................14

FIGURE 9 A 3D VIEW CAPABILITY OF THE GOOGLE EARTH ..................................15

FIGURE 10 CONTROL POINTS SHOWING THE “FROM” VIEW (INITIAL LOCATIONS OF

THE BOUNDARIES) AND THE “TO” VIEW (INTENDED LOCATION OF THE
BOUNDARIES) WHERE THE BOUDARIES ARE INTENDED TO BE AT AFTER GIS
PROCESSING OF THE BLUE POLYGON.................................................................16

FIGURE 11 THE ORANGE POLYGON SHOWS THE ADJUSTED BOUNDARIES OF THE

ORIGINAL BLUE POLYGON AFTER PROCESSING...................................................16

3 | Page
 CRMS Updates 2
008
FIGURE 12. SIMULATED I90 ACCOUNT LOCATIONS IN CRMS.................................17

FIGURE 13. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES - HIGHLIGHTING

MUNICIPALITIES WITH EXISTING I90 ACCOUNTS.................................................18

FIGURE 14. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES – CENTROID DOT

OF EACH MUNICIPALITY SYMBOLIZED AS RED CIRCLES OF VARYING RADIUS
PROPORTIONAL TO # OF EXISTING ACCOUNTS WITHIN THE MUNICIPALITY..........19

FIGURE 15. THE COMMAND WINDOW IN ARCGIS THAT SHOWS THE OPTIONS OF
DERIVING STATISTICAL VALUES ASSOCIATED WITH THE ANTITIES A USER MAY
WANT TO ANALYZE...........................................................................................19

FIGURE 16. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES – REGIONAL

CENTROIDS WITH SIZES PROPORTIONAL TO SI CONTENTS, AND THE PIE CHART
BEING REPRESENTED BY THE PREMIUMS A AND B..............................................20

FIGURE 17. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES – REGIONAL

CENTROIDS WITH SIZES PROPORTIONAL TO POLICY COUNT, AND THE PIE CHART
BEING REPRESENTED BY THE SI BUILDING AND CONTENT...................................21

FIGURE 18. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES – REGIONAL

CENTROIDS WITH SIZES PROPORTIONAL TO SUM INSURED, AND THE PIE CHART
BEING REPRESENTED BY THE THE SI BUILDING AND CONTENT.............................22

FIGURE 19 ONE OF THE ERRORS THAT OCCURS WHEN QUERYING A REPORT OF A

PLOTTED POLICY IN CRMS.................................................................................23

FIGURE 20 ONE OF THE MANY ADDITIONAL POTENTIAL OF CRMS WHEN

PROGRAMMED WITHIN THE ARCGIS. THE CIRCLE SIZES SHOWS THE TOTAL SUM
INSURED FOR THE CORRESPONDING MUNICIPALITY AS OF 2007.........................24

FIGURE 21 SIMPLIFIED PROPOSED WORKFLOW DIAGRAM OF THE CRMS WITHIN

SICI.................................................................................................................25

FIGURE 22 THE MASTERPLAN WITH CHECKMARKS TO EMPHASIZE THE WORKFLOW

BETWEEN PERSONNELS AND SYSTEMS USED TO ACCOMPLISH THE TASKS
INVOLVED........................................................................................................25

FIGURE 23 INFRASTRUCTURE PLAN FOR THE CRMS............................................26

4 | Page
 CRMS Updates 2
008
FIGURE 24 THE MASTERPLAN WITH CHECKMARKS TO EMPHASIZE THE SYSTEMS IN
PLACE TO GUIDE THE INFRASTRUCTURE SETUP..................................................26

FIGURE 25 PROPOSED TASKS AND FUNCTIONS OF INVOLVED DEPARTMENTS AND

PERSONNELS...................................................................................................28

FIGURE 26 THE MASTERPLAN WITH CHECKMARKS TO EMPHASIZE THE PERSONNEL

THAT WILL PERFORM THE TASKS.......................................................................28

FIGURE 27 GOOGLE EARTH SHOWING THE LOCATION OF EXISTING POLICIES

PLOTTED IN THE CRMS.....................................................................................29

FIGURE 28 GOOGLE EARTH OVERLAIN WITH EXISTING EARTHQUAKE HAZARD......29

FIGURE 29 GOOGLE EARTH FOCUSES AND SHOWS BOUNDARIES OF THE SELECTED

REGION WITH A SIMPLE CLICK ON THE REGIONS LIST.........................................30

FIGURE 30 GOOGLE EARTH FOCUSES AND SHOWS BOUNDARIES OF THE SELECTED

MUNICIPALITY WITH A SIMPLE CLICK ON THE MUNICIPALITIES LIST.....................30

FIGURE 31 GOOGLE EARTH FOCUSES AND SHOWS BOUNDARIES OF THE SELECTED

BARANGAY WITH A SIMPLE CLICK ON THE BARANGAY LIST.................................31

FIGURE 32 E-TREX NAVIGATION GPS THAT WILL BE DISTRIBUTED TO THE

CORPORATE AND BRANCHES OF SICI FOR CRMS USE..........................................32

FIGURE 33 SIMPLEST FORM OF DOCUMENT TRACKING SYSTEM FOR TRACKING OF

POLICY REQUESTS FOR CRMS...........................................................................32

FIGURE 34 A FREEWARE THAT CAN BE USED FOR COORDINATE TRANSFORMATION

FOR USE ON THE GPS, THE CRMS AND GOOGLE EARTH ......................................32

FIGURE 35 GOOGLE EARTH SHOWING THE EXTENT OF THE PHILIPPINE LANDS. THIS
WILL BE INSTALLED IN THE PROPOSED GIS WORKSTATIONS AS A PRELIMINARY USE
BEFORE LINKING I90 POLICIES WITH THE CRMS.................................................33

5 | Page
 CRMS Updates 2
008

CRMS MASTERPLAN
After consolidation and assessment of the details of the existing setup of the CRMS within
SICI and coming up with the initial version of the CRMS Operations Manual, discussions lead
to options for improving the present setup of CRMS with due consideration for future
development to be quick, easy, cost-effective and automated. Thus, the following figure
shows the diagram of the updated proposed setup of CRMS.

FIGURE 1 THE PROPOSED CRMS MASTER PLAN FOR SICI

Basic consideration in coming up with this revised masterplan:

 CRMS fully functional for hazard assessment and accumulation monitoring,

aligned with the company’s business procedures
 Least cost and time in making the first bullet item happen

6 | Page
 CRMS Updates 2
008
 Least additional task to involved staff from concerned departments and Branches

PHASES OF IMPLEMENTATION

FIGURE 2 STAGES OF IMPLEMENTATION FOR THE PROPOSED CRMS MASTERPLAN

PHASE 1 – DOCUMENTATION OF EXISTING FUNCTIONS, OPERATION AND ISSUES

A documentation of the existing function, operation and issues for the CRMS can be seen at
the initial version of the CRMS Operations Manual prepared prior to this document. Outlined
below are the major issues and first steps that need to be addressed as pertinent steps in
progressing with improving the existing CRMS.

ISSUE ON NON-STANDARDIZED ADDRESSES

Information systems intend to assist company operation in terms of making work more
efficient, and easier. This is usually done through automation of regular tasks that may
otherwise be performed by the personnel manually.

The basic scenario we would want to happen why we want to emphasize working on this
issue of non-standard address between the SICI databases is that when anybody encodes a
new policy within the i90 database, automated, accurate plotting of that policy within the
network CRMS and return of a location map, hazard assessment report and accumulation

7 | Page
 CRMS Updates 2
008
monitoring report can be done in seconds with just a click of the corresponding request
button on the local computer being used (in just 1 sitting). This can only be done with a
standardized addresses between the i90 and CRMS.

Automation tasks needed for CRMS includes the very basic but very important task of
assigning accurate policy location before and hazard assessment or accumulation
monitoring can be most efficiently performed, as precedent to the need to have plots of all
policies in CRMS as discussed in the previous Section. In its linkage with the i90 system, this
point location can automatically be derived (or accurately approximated) from the location
information indicated by the address fields. Not deviating from any other information system
which needs standardized ID system of field masterlist contents for different information to
be automatically linked, the address information from the i90 database should exactly match
that of the CRMS. The following figure xx best shows the necessary linkage of location
formation between the i90 and CRMS databases, for automatic location assignment of
policies:

But this is not the case at the moment. The following figure 2 shows the existing operation
of address input within the i90 database system, while figure 3 shows the existing address
information in the CRMS database where i90 needs to be linked.

FIGURE 3 EXISTING ADDRESS INPUT INTERFACE IN THE I90 SYSTEM

8 | Page
 CRMS Updates 2
008

FIGURE 4 EXISTING STORAGE OF ADDRESS RECORDS WITHIN THE I90 DATABASE

FIGURE 5 CATEGORIZED ADDRESS RECORDS IN THE CRMS DATABASE, SHOWING ENTRIES ON DISTRICTS

9 | Page
 CRMS Updates 2
008

FIGURE 6 CATEGORIZED ADDRESS RECORDS IN THE CRMS DATABASE, SHOWING ENTRIES ON

PROVINCES

An initial pilot work was done to be able to have a view of the existing status of city naming
convention in the i90 databse and the NSO, in an initial attempt to automate the linking of
the two databases in terms of the city names. Shown in table xx is the existing naming
convention of the two databases. Attached in Annex xx is the excel visual basic macro
program written to automate the extraction of the city name from the i90 database.

I90 CITY NAMES NSO CITY NAMES

ANGELES CITY ANGELES CITY
ANTIPOLO CITY CITY OF ANTIPOLO
BACOLOD CITY BACOLOD CITY (Capital)
BAGO CITY BAGO CITY
BAGUIO CITY BAGUIO CITY
BALANGA CITY CITY OF BALANGA (Capital)
BATANGAS CITY BATANGAS CITY (Capital)
BOHOL CITY
CAGAYAN DE ORO CITY CAGAYAN DE ORO CITY (Capital)
CALAPAN CITY CITY OF CALAPAN (Capital)
CALOOCAN CITY KALOOKAN CITY
CARLOS CITY SAN CARLOS CITY
CAVITE CITY CAVITE CITY
CEBU CITY CEBU CITY (Capital)
CITY OF SAN FERNANDO CITY OF SAN FERNANDO (Capital)
CITY OF STA. ROSA SANTA ROSA
DAGUPAN CITY DAGUPAN CITY
DASMARINAS DASMARIÑAS

10 | P a g e
 CRMS Updates 2
008
DAVAO CITY DAVAO CITY
FERNANDO CITY CITY OF SAN FERNANDO (Capital)
GENERAL SANTOS CITY GENERAL SANTOS CITY (DADIANGAS)
ILIGAN CITY ILIGAN CITY
ILOILO CITY ILOILO CITY (Capital)
KALOOCAN CITY KALOOKAN CITY
LAOAG CITY LAOAG CITY (Capital)
LAS PINAS CITY CITY OF LAS PIÑAS
LEGAZPI CITY LEGAZPI CITY (Capital)
LIPA CITY LIPA CITY
MAKATI CITY CITY OF MAKATI
MALOLOS CITY MALOLOS (Capital)
MANDALUYONG CITY CITY MANDALUYONG
MARIKINA CITY CITY MARIKINA
MUNTINLUPA CITY CITY MUNTINLUPA
OLONGAPO CITY OLONGAPO CITY
PARANAQUE CITY CITY OF PARAÑAQUE
PARANAQUE CITY CITY OF PARAÑAQUE
PASAY CITY PASAY CITY
PASIG CITY CITY OF PASIG
P'QUE CITY CITY OF PARAÑAQUE
QUEZON CITY QUEZON CITY
ROXAS CITY ROXAS CITY (Capital)
SAN JUAN CITY SAN JUAN
SANTIAGO CITY CITY OF SANTIAGO
STA. ROSA CITY SANTA ROSA
TAGAYTAY CITY TAGAYTAY CITY
TAGBILARAN CITY TAGBILARAN CITY (Capital)
TAGUIG CITY TAGUIG
TARLAC CITY CITY OF TARLAC (Capital)
URDANETA CITY CITY URDANETA
VALENZUELA CITY CITY OF VALENZUELA
ZAMBOANGA CITY ZAMBOANGA CITY

TABLE 1 INITIAL MATCH-UP OF PILOT DATA FROM THE I90 DATABASE TO THAT OF THE CRMS DATABASE

The address information in the CRMS database will be endorsed by the CRMS team for
adaptation for the i90 as a first step towards automation of pinpointing the exact location of
the policies on the CRMS maps.

ISSUE ON UNPLOTTED POLICIES IN I90

It is always expected by the common user that GIS maps and policy point locations within
the CRMS should already be very accurate once this is implemented to be part of a regular
assessment procedure. This is normal, and should always of course be the target in mind.
But here in the Philippines where austerity measure is a big factor, we take a different
practical approach that does not compromise the goal of accuracy in mind: we make the
CRMS already operational with its objective assessment methods in place, while we update

11 | P a g e
 CRMS Updates 2
008
the maps and policy point locations to be more accurate as the system and its procedures
are being implemented. Of course, again, operation of the CRMS at any point should not
compromise attainable accuracy of maps and point locations.

The CRMS utilize the latest accurate maps that the designated national authority for those
maps release. With the implementation of a standardized address datasets between i90 and
the CRMS, point locations for policies are intended to be plotted accurately following the
recommended procedures, which are as follows:

 Automated plotting of policies in GIS – automated plotting of accounts within the

barangay boundaries indicated by the existing CRMS national barangay map,
based from a matching address information from the i90.

 Validation of Plots/Plotting using Google Earth – complemented with a GPS

reading and other reference layers like roads, structures, water bodies, etc. to
guide the more accurate pinpoint of location of the policy by the user.

By far, ~ 1000 policies out of the total ~14,000 CMG accounts/policies have been assigned
map locations within the CRMS. This is confined within the Metro Manila areas as the focus
of CRMS Phase 1.

It is worthwhile to note that the first bullet already brings a possibility for a rather accurate
overall policy assessment that is beneficial for the RED and ITD on simulating the over-all
functionality of the CRMS, and is beneficial for the SICI Management committee for having a
grasp of a thorough assessment of all policies related to any location-based analysis. This
automation of giving point location based on addresses is technically referred to in GIS as
simulation of location and analysis scenarios.

S TEP 1 – A UTOMATED P LOTTING USING GIS

This involves the automated approximate plotting of the policy based on the most specific
and accurate available location information. (I.e. municipal information if barangay
information is not present).

This automation script within arcGIS will assign approximate location of the new policies
downloaded from the i90 database. The approximation will be flagged through a specified
field that identifies the method with which the location was pinpointed, i.e. “arcGIS” or
“Google Earth”. This Step 1 concerns the arcGIS automation.

“Why give approximated locations in advance?”, most users may ask. This is basically to
make an advance analysis of each of all the SICI policies which can be performed as soon as
a day after a policy has been encoded in the i90 database. This advance analysis includes
the hazard assessment report, accumulation monitoring report, and other macro-level
analysis which basically includes locational statistics like minimum, maximum, average and
sum of policies processed and SI, policies pending, policies denied, all these and others at a
level that may be per zone, per administrative area, or per a specific category that may not
be locational but results are significantly visualized when displayed related to location.

12 | P a g e
 CRMS Updates 2
008

FIGURE 7 ADMINISTRATIVE BOUNDARY MAPS THAT WILL BE USED FOR AUTOMATING LOCATION OF I90
POLICIES WITHIN THE CRMS

S TEP 2 – V ALIDATION OF A UTOMATED P LOTTING

Ideally 1 GIS work station per SICI department and each of the SICI branches will be
assigned, basically intended to have the Google Earth and all other GIS-utilities that are
connected in procedure with that of CRMS. The work station Google Earth will be uploaded
with administrative boundary maps to assist the user into exactly pinpointing the location of
the policy of interest, as demonstrated in the figure.

Trainings will be given by RED in terms of how to specifically use the GIS Work station in
determining the location of the policy of interest. This will be easy when the location of the
policy has high resolution satellite imagery at the Google Earth, but a more challenging best-
practices approach on determining the location based on not-so-high resolution satellite
imagery will also be taught.

13 | P a g e
 CRMS Updates 2
008

FIGURE 8 BARANGAY BOUNDARY OVERLAIN ON THE GOOGLE EARTH FOR DIRECT PINPOINTING OF THE
LOCATION OF A POLICY

14 | P a g e
 CRMS Updates 2
008

FIGURE 9 A 3D VIEW CAPABILITY OF THE GOOGLE EARTH

ISSUE ON NON-FUNCTIONAL ACCUMULATION MONITORING FUNCTIONALITY

(Inputs from Rudy)

PHASE 2 – RESOLVING EXISTING ISSUES, EXPANDING FUNCTIONS AND OPERATION

METRO MANILA TO NATIONWIDE DATASETS

Currently, expansion of the datasets to cover the whole Philippines is being performed
thorugh digitizing of gathered national maps. The following is the initial list of national data
being digitized:

 Philippine administrative map up to barangay level

 Philippine fault map and trenches at the scale of 1:250,000
 Philippine liquefaction map at the scale of 1:250,000
 Philippine tsunami prone areas

Details of the work done on bullet 1 was stitching the metro manila barangay level data to
the NSO barangay level data, without altering the consistency of the polygons in terms of
completely representing the whole Philippine barangays. Then with the general plan of
implementing the use of Google earth in the risk management divisions and the other

15 | P a g e
 CRMS Updates 2
008
Standard Insurance branches, final editing of the barangay polygons will be on fitting the
outline to be as much as possible consistent with the displayed satellite image shorelines.

FIGURE 10 CONTROL POINTS SHOWING THE “FROM” VIEW (INITIAL LOCATIONS OF THE BOUNDARIES)
AND THE “TO” VIEW (INTENDED LOCATION OF THE BOUNDARIES) WHERE THE BOUDARIES ARE
INTENDED TO BE AT AFTER GIS PROCESSING OF THE BLUE POLYGON

FIGURE 11 THE ORANGE POLYGON SHOWS THE ADJUSTED BOUNDARIES OF THE ORIGINAL BLUE
POLYGON AFTER PROCESSING

ADDITION OF HAZARD LAYERS FOR CRMS VERSION 1.0 PHASE 2

EXISTING HAZARD LAYERS PROPOSED ADDITIONAL HAZARD LAYERS

(CRMS Version 1.0 Phase 1) (CRMS Version 1.0 Phase 2)

Earthquake Hazard Tsunami Hazard

Ground rupturing

Ground shaking

Liquefaction potential

Earthquake Source Proximity effects

Typhoon Hazard Storm Surge Hazard

Flood Hazard Lightning Hazard

16 | P a g e
 CRMS Updates 2
008
River flooding

Flood hazard by Mancebo

Flood hazard by

Flood hazard by

Volcanic Hazard Tornado Hazard

Landslide Hazard

(ILABAS CONTENTS AS A LIST)

TABLE 2. EXISTING AND PROPOSED HAZARD LAYERS FOR NATURAL HAZARD ASSESSMENT IN THE CRMS

REFINING THE ACCUMULATION MONITORING FUNCTIONALITY

(Inputs from Rudy)

ADDITIONAL PROPOSED FUNCTIONALITIES OF CRMS

FIGURE 12. SIMULATED I90 ACCOUNT LOCATIONS IN CRMS

17 | P a g e
 CRMS Updates 2
008

FIGURE 13. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES - HIGHLIGHTING MUNICIPALITIES WITH
EXISTING I90 ACCOUNTS

18 | P a g e
 CRMS Updates 2
008

FIGURE 14. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES – CENTROID DOT OF EACH
MUNICIPALITY SYMBOLIZED AS RED CIRCLES OF VARYING RADIUS PROPORTIONAL TO # OF EXISTING
ACCOUNTS WITHIN THE MUNICIPALITY

FIGURE 15. THE COMMAND WINDOW IN ARCGIS THAT SHOWS THE OPTIONS OF DERIVING STATISTICAL
VALUES ASSOCIATED WITH THE ANTITIES A USER MAY WANT TO ANALYZE

19 | P a g e
 CRMS Updates 2
008

FIGURE 16. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES – REGIONAL CENTROIDS WITH SIZES
PROPORTIONAL TO SI CONTENTS, AND THE PIE CHART BEING REPRESENTED BY THE PREMIUMS A AND
B.

20 | P a g e
 CRMS Updates 2
008

FIGURE 17. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES – REGIONAL CENTROIDS WITH SIZES
PROPORTIONAL TO POLICY COUNT, AND THE PIE CHART BEING REPRESENTED BY THE SI BUILDING AND
CONTENT.

21 | P a g e
 CRMS Updates 2
008

FIGURE 18. INHERENT ANALYSIS CAPABILITY OF GIS SOFTWARES – REGIONAL CENTROIDS WITH SIZES
PROPORTIONAL TO SUM INSURED, AND THE PIE CHART BEING REPRESENTED BY THE THE SI BUILDING
AND CONTENT.

PROPAGATING FROM VISUAL BASIC CRMS TO ARCGIS CRMS

The existing programming of CRMS was done in visual basic. Generally it functions properly,
but several pertinent concerns are being addressed in its current operation including the
following:

 It runs slow, much slower than the same functions automated and running within
a commercial GIS software

 Re-programming to accommodate additional layers (from the existing 5 hazard

layers upto the planned 9 hazard layers) foresees complications and will take up
much time of the ITD staff, given its existing workload.

 The expansion of the data layers to contain nationwide data pre-empts a much
slower processing time based form its existing performance of running with the
existing Metro Manila datasets.

 Programming the GIS functionalities in visual basic is equivalent to the CRMS

having the capabilities in spatial data analysis limited to the programmed
functionalities. This restricts the company in easily exploring and adapting other
inherent GIS functionalities already existing in pre-built GIS softwares.

22 | P a g e
 CRMS Updates 2
008

FIGURE 19 ONE OF THE ERRORS THAT OCCURS WHEN QUERYING A REPORT OF A PLOTTED POLICY IN
CRMS

23 | P a g e
 CRMS Updates 2
008

FIGURE 20 ONE OF THE MANY ADDITIONAL POTENTIAL OF CRMS WHEN PROGRAMMED WITHIN THE
ARCGIS. THE CIRCLE SIZES SHOWS THE TOTAL SUM INSURED FOR THE CORRESPONDING MUNICIPALITY
AS OF 2007.

At the present, an option for outsourcing the work has been arranged with a freelance
programmer, and the proposed workflow, timeframe and costing is attached in Annex XXX of
this manual.

PHASE 3 – INVOLVING THE RISK MANAGEMENT DEPARTMENT AND BRANCHES IN THE

CRMS PROCEDURE

PROPOSED WORKFLOW

24 | P a g e
 CRMS Updates 2
008

FIGURE 21 SIMPLIFIED PROPOSED WORKFLOW DIAGRAM OF THE CRMS WITHIN SICI

FIGURE 22 THE MASTERPLAN WITH CHECKMARKS TO EMPHASIZE THE WORKFLOW BETWEEN

PERSONNELS AND SYSTEMS USED TO ACCOMPLISH THE TASKS INVOLVED

INFRASTRUCTURE SETUP

25 | P a g e
 CRMS Updates 2
008

FIGURE 23 INFRASTRUCTURE PLAN FOR THE CRMS

FIGURE 24 THE MASTERPLAN WITH CHECKMARKS TO EMPHASIZE THE SYSTEMS IN PLACE TO GUIDE
THE INFRASTRUCTURE SETUP

P URCHASED CRMS W ORKSTATION S PECS

Preferred specs Optional specs if item in

26 | P a g e
 CRMS Updates 2
008
previous column is not
available

Intel® Core™2 Quad Processor Q6600

(2.40GHz, 8Mb L2 cache) 1066MHz
Processor Up to Intel® Core®2 Duo QX6850 FSB LGA775
MSI P6N-SLI
Inno3D i-Chill 8500GT 512Mb DDR2
Video Card NVIDIA Quadro FX 4600 768MB Arctic / XStriker
at least 4GB DDR3 PC3-8500 ECC Transcend 2.0Gb 667MHz DDR2 PC2-
Internal RAM UDIMM 5300 DIMM, Memory (2x 1.0Gb)
(2 items) 120Gb Serial ATA Harddrive at 7200
Hard Disk RPM
Preferably external LightScribe SATA Double Layer
DVD Drive (8.5Gb) 20X 20AIS DVD+/-RW Drive (black)
Floppy Disk
Drive 1.44Mb Floppy Drive (black)
ATX Case Silver/Black w/ Dynamo Pro 600Watts,
Ventilation Triple Fans PSU / 24 Pins Connector
and Transparent Side Panel AirDuct

Mouse and Logitech Internet PRO Desktop Keyboard / Optical

Keyboard Mouse (black)
22-inches HD-Ready widescreen LCD (support to 22" Samsung 226BW Widescreen LCD
Monitor WUXGA resolution) Monitor
Speaker Altec Lansing BXR1121 Speaker
Integrated High Definition Audio
Internet 56Kb Internal Modem
UPS APC-USA ES UPS 500VA (black)
Operating
System Windows XP Sevice pack 3
Microsoft 2007 Suite, with excel, word, powerpoint, visio,
Office project)
Accessories 1 Multi Card Reader
1 USB adapter cable
1 Optical baby mouse for laptop (midsize)

R ECOMMENDED GIS W ORKSTATION S PECS

R ECOMMENDED GPS S PECS

PERSONNEL

27 | P a g e
 CRMS Updates 2
008

FIGURE 25 PROPOSED TASKS AND FUNCTIONS OF INVOLVED DEPARTMENTS AND PERSONNELS

FIGURE 26 THE MASTERPLAN WITH CHECKMARKS TO EMPHASIZE THE PERSONNEL THAT WILL PERFORM
THE TASKS

TOOLS

28 | P a g e
 CRMS Updates 2
008

FIGURE 27 GOOGLE EARTH SHOWING THE LOCATION OF EXISTING POLICIES PLOTTED IN THE CRMS

FIGURE 28 GOOGLE EARTH OVERLAIN WITH EXISTING EARTHQUAKE HAZARD

29 | P a g e
 CRMS Updates 2
008

FIGURE 29 GOOGLE EARTH FOCUSES AND SHOWS BOUNDARIES OF THE SELECTED REGION WITH A
SIMPLE CLICK ON THE REGIONS LIST

FIGURE 30 GOOGLE EARTH FOCUSES AND SHOWS BOUNDARIES OF THE SELECTED MUNICIPALITY WITH
A SIMPLE CLICK ON THE MUNICIPALITIES LIST

30 | P a g e
 CRMS Updates 2
008

FIGURE 31 GOOGLE EARTH FOCUSES AND SHOWS BOUNDARIES OF THE SELECTED BARANGAY WITH A
SIMPLE CLICK ON THE BARANGAY LIST

TRAINING COMPONENT

Aligned with the proposed operation of the CRMS shown in the Masterplan figure, the
training will focus on the following pertinent details of operation where the roles of the RMD
and the branches come in:

• Presentation on the following

o CRMS functionalities

o Over-all plan for CRMS focusing on their and the company’s benefits

o Their specific roles within the proposed procedures

• Training and procedural role-play on the following

o E-trex GPS use

o Google Earth use

o TatukGIS use

o Sending policy assessment reports request

o Retrieving policy assessment reports request

31 | P a g e
 CRMS Updates 2
008

FIGURE 32 E-TREX NAVIGATION GPS THAT WILL BE DISTRIBUTED TO THE CORPORATE AND BRANCHES
OF SICI FOR CRMS USE

FIGURE 33 SIMPLEST FORM OF DOCUMENT TRACKING SYSTEM FOR TRACKING OF POLICY REQUESTS
FOR CRMS

FIGURE 34 A FREEWARE THAT CAN BE USED FOR COORDINATE TRANSFORMATION FOR USE ON THE
GPS, THE CRMS AND GOOGLE EARTH

32 | P a g e
 CRMS Updates 2
008

FIGURE 35 GOOGLE EARTH SHOWING THE EXTENT OF THE PHILIPPINE LANDS. THIS WILL BE INSTALLED
IN THE PROPOSED GIS WORKSTATIONS AS A PRELIMINARY USE BEFORE LINKING I90 POLICIES WITH
THE CRMS

PHASE 4 – PROPOSAL AND IMPLEMENTATION OF PROCEDURAL POLICIES

DRAFT PROCEDURES AND POLICIES

ANNEX
INITIAL AUTOMATION EXCEL MACRO TO CATEGORIZE ADDRESSES IN THE I90 DATABASE
Sub clusterAddressBasedOnCity()

Dim myAddArray() As Variant

'concatenate addresses
myRow = 2
mycellvalue = Cells(myRow, 1).Value
Do Until mycellvalue = vbNullString

add1 = Cells(myRow, 1).Value

If add1 <> vbNullString Then
'add comma in field entry if not ended in comma
If InStr(add1, " ") <> 0 Then
add1 = Left(add1, InStr(add1, " "))
End If
If Right(add1, 2) <> ", " Then
add1 = Left(add1, Len(add1) - 1) & ","

33 | P a g e
 CRMS Updates 2
008
End If
End If

add2 = Cells(myRow, 2).Value

If add2 <> vbNullString Then
If InStr(add2, " ") <> 0 Then
add2 = Left(add2, InStr(add2, " "))
End If
If Right(add2, 2) <> ", " Then
add2 = Left(add2, Len(add2) - 1) & ","
End If
End If

add3 = Cells(myRow, 3).Value

If add3 <> vbNullString Then
If InStr(add3, " ") <> 0 Then
add3 = Left(add3, InStr(add3, " "))
End If
End If

add4 = add1 + add2 + add3

'write concatenated string in the next column

Cells(myRow, 4).Value = add4

'segment address based on comma, and assign to array

mySegCount = 1
add5 = add4
myStrComma = InStr(add5, ",")
Do Until myStrComma = 0
add5 = Mid(add5, myStrComma + 1, Len(add5))
mySegCount = mySegCount + 1
myStrComma = InStr(add5, ",")
Loop
ReDim myAddArray(mySegCount) As Variant

mySegCount = 1
myStrComma = InStr(add4, ",")
Do Until myStrComma = 0
myAddArray(mySegCount) = Left(add4, myStrComma - 1)
add4 = Mid(add4, myStrComma + 1, Len(add4))
mySegCount = mySegCount + 1
myStrComma = InStr(add4, ",")
Loop
myAddArray(mySegCount) = add4

'assign segments based on keywords

For i = 1 To mySegCount
'remove spaces before and after word or phrase
If Left(myAddArray(i), 1) = " " Then myAddArray(i) = Mid(myAddArray(i), 2, Len(myAddArray(i)))
If Right(myAddArray(i), 1) = " " Then myAddArray(i) = Left(myAddArray(i), Len(myAddArray(i)) - 1)

'segregate based on city as pivot point"

If InStr(myAddArray(i), "CITY") Then
If myAddArray(i) = "CITY" Then
If i > 1 Then
MyBeforeString = myAddArray(1) & " "

34 | P a g e
 CRMS Updates 2
008
For j = 2 To i - 2
MyBeforeString = MyBeforeString & myAddArray(j)
Next
Cells(myRow, 7).Value = MyBeforeString
End If

Cells(myRow, 8).Value = myAddArray(i - 1) & " " & myAddArray(i)

If i + 1 = mySegCount Then
Cells(myRow, 9).Value = myAddArray(i + 1)
End If
Else
'complete the all entry before city as 1 address line
If i > 1 Then
MyBeforeString = myAddArray(1) & " "
For j = 2 To i - 1
MyBeforeString = MyBeforeString & myAddArray(j)
Next
Cells(myRow, 7).Value = MyBeforeString
End If

Cells(myRow, 8).Value = myAddArray(i)

If i + 1 = mySegCount Then
Cells(myRow, 9).Value = myAddArray(i + 1)
End If
End If
End If
Next i
myRow = myRow + 1
mycellvalue = Cells(myRow, 1).Value
Loop

End Sub

ARCVIEW SCRIPT TO AUTOMATE POLICY LOCATIONS BASED ON I 90 MUNICIPALITY

ADDRESS INFO

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
' Name of the script: Randompoint per municipality
' Date created: April 3 2008
' Date modified:
' Author: Oliver Barbosa
' Description: This script creates pseudo points for the industrie database per municipality
' Requiered scripts:
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
'select the floating table of policies in dbf format and the the field with the city names
theView = av.GetActiveDoc
theFTVTab = av.GetProject.FindDoc( "mymatch2.dbf" ).GetVTab
theFTCityField = theFTVTab.FindField("Muncitynso")
theFTRecIDField = theFTVTab.FindField("myID")

'Select the llda shape file to pick a random point from a municipality

35 | P a g e
 CRMS Updates 2
008
theAdminTheme = theView.FindTheme("Sici_municipality.shp")
theAdminTheme.clearselection
theAdminTheme_VTab = theAdminTheme.GetFTab
'theGISCityField = theAdminTheme_VTab.FindField("City")
theAdminTheme.SetVisible(FALSE)

'make a new shapefile for the coordinates

MyFtab = Ftab.MakeNew("d:\Sici\Scripts\".AsFileName.MakeTmp( "random", "shp" ),POINT)
MyFTRecIDField = Field.Make("ID_res",#FIELD_LONG ,10,0)
MyMun_nameField = Field.Make("City_res",#FIELD_CHAR ,50,0)
MyFtab.AddFields({MyFTRecIDField,MyMun_nameField})

'For each record in floating table, add record to shapefile and randomly pick coordinate
for each rec in theFTVTab
'get data for each field attribute
myFTRecID = theFTVTab.ReturnValue(theFTRecIDField, rec)
myFTCity = theFTVTab.ReturnValue(theFTCityField, rec)

'select same municipality in llda shapefile

myFTCityStr = myFTCity.AsString
theBitmap = theAdminTheme_VTab.GetSelection
theQuery = "[City] = " + myFTCityStr.Quote
'MsgBox.Info(theQuery.AsString,"This is the query line")

theAdminTheme_VTab.Query(theQuery, theBitmap, #VTAB_SELTYPE_NEW)

theAdminTheme_VTab.UpdateSelection
theNumber = theAdminTheme_VTab.GetNumSelRecords
'MsgBox.Info(theNumber.AsString,"There is a selected record in the shapefile based from
FT!")

if (theNumber = 1) then

'generate a graphic of the queried polygon in admin to base point randomization of FT

account on
theBitmap = theAdminTheme_VTab.GetSelection
for each rec in theBitmap
theShapeField = theAdminTheme_VTab.FindField("Shape")
aShape = theAdminTheme_VTab.ReturnValue(theShapeField, rec)
aGraphic = GraphicShape.Make(aShape)
end
theRect = Rect.MakeEmpty
theRect = aGraphic.GetBounds
MyFactorN = 1

36 | P a g e
 CRMS Updates 2
008
'here the while statement needs to come in
while (true)
mun_ok = true

'due to the fact I work in this script with SelectByPoint to check wether a pseudo point
'lies in the correct municipality, we need to zoom in really far to minimize the mistakes
'caused by the problem that SelectByPoint has a tolerance of three screen pixels
ZoomRect = theAdminTheme.ReturnExtent
d = theView.GetDisplay
d.ZoomToRect(ZoomRect)
'I zoom in to cm's per pixels, no error is possible
d.ZoomIn(10000000)
'Show/flush the changes to the display
d.Flush

'create the virtual random point coordinate

MyX = (Number.MakeRandom (theRect.GetLeft * MyFactorN, theRect.GetRight *
MyFactorN) / MyFactorN)
MyY = (Number.MakeRandom (theRect.GetBottom * MyFactorN, theRect.GetTop *
MyFactorN) / MyFactorN)
MyPoint = Point.Make(MyX,MyY).Clone

'select from admin theme the polygon intersected by the virtual random point coordinate
if (theAdminTheme.CanSelect) then
theAdminTheme.SelectByPoint(MyPoint, #VTAB_SELTYPE_NEW)
end
theAdminTheme_VTab.UpdateSelection

'Prepare the VtabSort

theGISCityField = theAdminTheme_VTab.FindField("City")
fldList = {theGISCityField}
directionList = {TRUE}
SelOnly = TRUE
CaseSensitive = FALSE
vSort = VTabSort.Make(theAdminTheme_VTab, fldList, directionList, SelOnly,
CaseSensitive)
theSortNumber = vSort.GetLen
'MsgBox.Info(theSortNumber.AsString++"is the result","theSortNumber")
TheMunNumber = vSort.GetRec(0)

'Select something from the Vsort by creating a new Vtab

newVtab = vSort.GetVtab
MunField2 = newVtab.FindField("City")
s = newVtab.ReturnValueString(MunField2,TheMunNumber)
'MsgBox.Info(s,"This is the municipality where the point lies in")
'MsgBox.Info(myFTCityStr,"This is the desired municipality where the point should be")

37 | P a g e
 CRMS Updates 2
008
vSort.Refresh
if (s = myFTCityStr) then
'MsgBox.Info(s +" equals "+ myFTCityStr,"They are the same")
mun_ok = false
else
'MsgBox.Info(s +" is not equal to "+ myFTCityStr,"They are not the same")
end
if (not mun_ok) then
break
end
end
'here the while statement needs to be ended

NewRec = MyFtab.AddRecord
MyPoint = Point.Make(MyX,MyY).Clone
MyFtab.SetValue(MyFtab.FindField("shape"),newrec,MyPoint)
MyFtab.SetValue(MyFTRecIDField,newrec,myFTRecID)
MyFtab.SetValue(MyMun_nameField,newrec,myFTCity)
MyFtab.Flush
MyNewTheme = FTheme.Make(MyFtab)

if (rec = 0) then
MyNewTheme.SetVisible(TRUE)
theView.AddTheme(MyNewTheme)
end

theAdminTheme.clearselection
'zoom back to original extent of the llda shape
d.ZoomToRect(ZoomRect)
d.Flush

ZoomRect = MyNewTheme.ReturnExtent
e = theView.GetDisplay
e.ZoomToRect(ZoomRect)

end

end

MyFtab.SetEditable(FALSE)
MyFtab.Flush

PROPOSED WORK PROGRAM OF ITD – CONTINUED PROGRAMMING OF CRMS WITHIN

VISUAL BASIC

38 | P a g e
 CRMS Updates 2
008
SUBMITTED PROPOSAL – REPROGRAMMING CRMS WITHIN ARCGIS

INTRODUCTION

This document details the Project for Revised CRMS of Standard Insurance. Part II of this
document will discuss the Objectives of the Project. Part III will be the Scope and Limitation,
defining the boundaries of the system and functional requirements. Part IV is the
Methodology and Approach. Part V the Cost Benefit Analysis.

CRMS is an expert system designed to provide analysis reports for decision makers. It is a
tool for measuring risks with a mapping component linked to External Databases (Sybase
and I90).

PURPOSE

• Enhance the current CRMS in VB6 and migrate it to ARCGIS 9

• Optimize and speed up geoprocessing and report generation
• Automate DB connection and link (if possible)

SCOPE OF THE PROJECT

Since the project is merely focusing on optimization, migration and enhancement, the
project however will not require the following documentation:

1. SRS - Software Requirement Specification

2. FRS - Functional Requirement Specification
3. Database Design

The functionalities of the software will only depend on the current system. Meaning Standard
Insurance will grant access to their current application or provide a documentation of the
current system. Enhancements will be added to the existing documentation of Standard
Insurance. Any changes on procedures, newly generated report template, or changes that
may tagged as "new" in the current system will be charged as an Add-On to system
features.

Software and licenses needed for the development environment will be provided by
Standard Insurance.

METHODOLOGY

The following will be submitted as a part of project deliverable:

1. Project Timeline
2. Status Report
3. Meeting once a week
4. Presentation of Output
5. Coding Documentation
6. User Manual
7. Test Scripts and Test Cases

39 | P a g e
 CRMS Updates 2
008
Meeting comprises presentation of output; clarification on system functionalities; issues and
concerns; request for change. Status Report will be submitted before the meeting;

1. Project Plan - finalization of functionalities and approach

2. Environment Set-up and Coding - Status Reports and Presentation of Output
3. QA/QC - Unit Testing - Rialyn Morales; System Testing - Programmer from your end;
Integration Testing - Programmer from your end; UAT - Users of the Actual System;
Implementation to Production - the system should pass all the testing above and be
certified before promoting it to production database.
4. Training and Technology Transfer - Training Manual
5. Maintenance - includes bug fixes; tech support; tips and tricks; does not include
enhancement of functionalities

TIMEFRAME

The project will be completed within 3 months. Time allotment will be 2 months for coding
and 1 month for maintenance.

Basic Assumptions for the 3 months timeframe:

1. System development will include hazard assessment and accumulation monitoring as
part of the Core Module
2. Business Process Analysis is not included in the proposed timeframe
3. There is a separate timeframe and resources for segregating the historical records
account addresses in the i90 for input to the CRMS

COSTING

TASK % of Proposed Cost Task Cost

Security Features 10 17,500
Core Module - Risk Plotting 35 61, 250
Report Generation 15 26,250
Optimization 15 26,250
Training and Technology 10 17,500
Transfer
Maintenance 10 17,500
Other Project related 5 8750
Expenses

40 | P a g e