Design Report v1.2

Design Report
Scoping and Design of IT Systems Upgrade for National

Electrification Administration
7 October 2015
Scoping and Design of IT Systems Upgrade for NEA (Confidential) 1

Acronyms
ACAM Accounting and Cost Allocation Manuals
AMGD Accounts Management and Guarantee Department
ATEO Accelerated Total Electrification Office
BLEP Barangay Line Enhancement Program
BYOL Bring Your Own License
CAPEX Capital Expenditure
COB Cash Operating Budget
CPO Corporate Planning Office
CRUD Created, Read, Update and Delete
CMMI Capability Maturity Model Integration
DMC Distribution Management Committee
DMZ Demilitarized Zone
DSM Distribution, Supply, Metering
EC Electric Cooperative
ED Engineering Department
EDDM Early Detection of Default Mechanism
eICPM Enhanced Integrated Computerized Planning Model
EPIRA Electric Power Industry Reform Act
EPIRA IRR Electric Power Industry Reform Act Implementing Rules and Regulations
ERC Energy Regulatory Commission
FI Financial Indicators
FIT Financial, Institutional, Technical
FSD Financial Services Department
FTE Full Time Equivalent
GI Governance Indicators
GIFMIS Government Integrated Financial Management Information System
GMC Grid Management Committee
GOCC Government-Owned and Controlled Corporation
GSIS Government Service Insurance System
HW Hardware
IaaS Infrastructure as a Service
IDD Institutional Development Department
ISMS Information Security Management Systems
ISO International Organization for Standardization
ITCSD Information Technology and Communications Services Development
ITIL Information Technology Infrastructure Library
KPI Key Performance Indicator
KPS Key Performance System
KRA Key Result Area
LTO Linear Tape-Open
MAG Management Assistance Group
MB Megabyte
MER Management Engineering Report
MFSR Monthly Financial Statistical Report
MIR Monthly Institutional Report
NEA National Electrification Administration
NPC-SPUG National Power Corporation - Small Power Utilities Group
NPV Net Present Value
OEI Operational Efficiency Indicator
OLAP Online Analytical Processing
OPASS Office for Performance Assessment and Special Studies
OPEX Operating Expenditure
PaaS Platform as a Service
PHP Philippine Peso
PSALM Power Sector Assets and Liabilities Management
PSMR Performance Standards Monthly Report
QCR Quarterly Compliance Report
RDBMS Relational Database Management System
RFSC Reinvestment Fund for Sustainable CAPEX
RSEC-WR Rules for Setting Electric Cooperatives Wheeling Rates
SaaS Software as a Service
SAIDI System Average Interruption Duration Index
SAIFI System Average Interruption Frequency Index
SAN Storage Access Network
SEP Sitio Electrification Program
SQL Sequential Query Language
SW Software
TA Technical Assistance
TCO Total Cost of Ownership
TMMI Test Maturity Model Integration
TOR Terms of Reference
TWG Technical Working Group
UTM Unified Threat Management
WB World Bank
WESM Wholesale Electricity Spot Market

Table of Contents
Acronyms .......................................................................................................................................................... 2
Index of Tables.................................................................................................................................................. 6
Index of Figures ................................................................................................................................................ 6
1 Executive Summary .................................................................................................................................... 9
2 Business Requirements ............................................................................................................................12
3 Data Requirements ...................................................................................................................................14
3.1 Data Entry Templates ........................................................................................................................14
3.2 Data Models .......................................................................................................................................15
3.2.1 Subject Area: Energy Sales ........................................................................................................17
3.2.2 Subject Area: System Performance ............................................................................................19
3.2.3 Subject Area: Financial Performance .........................................................................................21
3.2.4 Subject Area: Institutional Information ........................................................................................23
3.2.5 Subject Area: Project Statistics ...................................................................................................25
3.2.6 Report to Data Model Mapping ...................................................................................................27
3.3 Key Outputs........................................................................................................................................30
3.4 Data Dictionary ...................................................................................................................................33
3.5 Data Governance ...............................................................................................................................34
3.5.1 Data Maintenance Process .........................................................................................................34
3.5.2 Data Owner and Custodian.........................................................................................................35
3.6 Historical Data ....................................................................................................................................36
3.7 Data Retention and Archiving ............................................................................................................37
4 Application and Technology Architecture ..................................................................................................38
4.1 Application Architecture .....................................................................................................................38
4.1.1 Business Intelligence (BI) ...........................................................................................................39
4.1.2 Web Portal ..................................................................................................................................48
4.2 Technology Architecture ....................................................................................................................52
4.2.1 Hardware Requirements .............................................................................................................52
4.2.2 Database Requirements .............................................................................................................54
4.2.3 Network Requirements ...............................................................................................................55
4.2.4 Work Station Requirements ........................................................................................................57
4.2.5 Delivery Models ..........................................................................................................................57
4.3 Cost Estimates ...................................................................................................................................62
4.4 Service Delivery Standards ................................................................................................................64
4.4.1 Service Availability ......................................................................................................................64
4.4.2 Security .......................................................................................................................................65
4.4.3 IT Operations and Maintenance .................................................................................................68
4.4.4 Exit Process ................................................................................................................................71

5 Implementation Phase ...............................................................................................................................72
5.1 NEA Preparation for Implementation .................................................................................................72
5.2 List of Implementation Activities .........................................................................................................74
5.3 BI System Implementation .................................................................................................................76
5.4 Web Portal Implementation ................................................................................................................77
5.5 High-level Change Management Plan ...............................................................................................78
6 Annexes .....................................................................................................................................................82
6.1 Key Data Entry Templates .................................................................................................................82
6.1.1 Data Entry - EC - Monthly Data ..................................................................................................82
6.1.2 Data Entry - EC - Create New, Edit List of Values ...................................................................102
6.1.3 Data Entry - NEA - Create New, Edit List of Values .................................................................104
6.1.4 Data Entry - EC - eICPM...........................................................................................................105
6.1.5 Data Entry - NEA - Audit Findings ............................................................................................108
6.1.6 Data Entry - NEA - BOD, GM Performance Rating ..................................................................109
6.1.7 Data Entry - Price Index ............................................................................................................110
6.2 Data Dictionary .................................................................................................................................111
6.3 Key Process Maps for Data Governance .........................................................................................142
6.3.1 T4.0 Data Governance..............................................................................................................143
6.3.2 T4.1 Data Maintenance.............................................................................................................144
6.3.3 T4.2 Data Upload - Standard ....................................................................................................147
6.3.4 T4.3 Data Upload – Special Handling .......................................................................................148
6.3.5 T4.4 NEA Data Approval...........................................................................................................149
6.3.6 T4.5 Data Warehouse Processing ............................................................................................150
6.4 Use Case Diagrams .........................................................................................................................151
6.5 User Stories......................................................................................................................................152
6.6 Cost Estimate Assumptions .............................................................................................................157
6.6.1 Inclusions and Exclusions .........................................................................................................157
6.6.2 Detailed Cost Breakdown - Commercial Solution BI On Cloud (amounts in PHP) ..................159
6.6.3 Detailed Cost Breakdown - Commercial BI Solution On Premise (amounts in PHP)...............161
6.6.4 Detailed Cost Breakdown - Open Source BI Solution on Cloud (amounts in PHP) .................162
6.6.5 Detailed Cost Breakdown - Open Source BI Solution On Premise (amounts in PHP).............164
6.7 IT Practice Recommendations .........................................................................................................165
6.7.1 Strategy .....................................................................................................................................165
6.7.2 Standards ..................................................................................................................................165
6.7.3 Organizational Functions ..........................................................................................................167
6.8 Implementation Project Team ..........................................................................................................171
6.9 NEA IT Implementation Schedule – Condensed .............................................................................174

Index of Tables
Table 1: Hardware Specifications .....................................................................................................................11
Table 2: Energy Sales Multi-Dimensional Matrix ..............................................................................................18
Table 3: System Performance Multi-Dimensional Analysis Matrix ...................................................................20
Table 4: Financial Performance Multi-Dimensional Analysis Matrix ................................................................22
Table 5: Institutional Information Multi-Dimensional Matrix ..............................................................................24
Table 6: Project Statistics Multi-Dimensional Matrix ........................................................................................26
Table 7: Report to Data Model Mapping...........................................................................................................27
Table 8: Data Maintenance Process Flows ......................................................................................................34
Table 9: BI System Functional Requirements ..................................................................................................40
Table 10: Commercial vs. Open Source...........................................................................................................42
Table 11: Best of Breed vs. End-to-End ...........................................................................................................43
Table 12: Summary of Solution Recommendations .........................................................................................44
Table 13: BI Solution Brand Comparison .........................................................................................................44
Table 14: Summary of Web Portal Activities ....................................................................................................48
Table 15: Web Portal Functional Requirements ...............................................................................................48
Table 16: Technology Architecture Components .............................................................................................53
Table 17: Hardware Specifications for Web Portal ...........................................................................................53
Table 18: Hardware Specifications for BI .........................................................................................................54
Table 19: Connectivity Requirements...............................................................................................................55
Table 20: Delivery Model Comparison .............................................................................................................57
Table 21: IT System Cost Estimates (Amounts in PHP) ..................................................................................63
Table 22: Service Level Agreement Examples ................................................................................................70
Table 23: List of Implementation Activities .......................................................................................................75
Table 24: Change Management Plan ...............................................................................................................80
Index of Figures
Figure 1: BI System Components .....................................................................................................................10
Figure 2: Server Landscape .............................................................................................................................10
Figure 3: Implementation Schedule ..................................................................................................................12
Figure 4: Portion of Multi-Dimensional Analysis Matrix for System Performance ............................................16
Figure 5: Cross-Analysis of Subject Areas .......................................................................................................16
Figure 6: Energy Sales Data Model ..................................................................................................................17
Figure 7: System Performance Data Model .....................................................................................................19
Figure 8: Financial Performance Data Model ...................................................................................................21
Figure 9: Institutional Information Data Model ..................................................................................................23
Figure 10: Project Statistics Data Model ..........................................................................................................25
Figure 11: Sample Output Dashboard 1 ...........................................................................................................30

Figure 16: Historical Data Upload .....................................................................................................................36
Figure 17: IT Design for NEA ...........................................................................................................................38
Figure 18: BI System Components ...................................................................................................................39
Figure 19: Web Portal Sample Screenshot ......................................................................................................48
Figure 20: Server Landscape ...........................................................................................................................52
Figure 21: NEA Landscape with Existing Security Solutions ...........................................................................66
Figure 22: Application Support .........................................................................................................................70
Figure 23: NEA IT Implementation Schedule ...................................................................................................74
Figure 24: Sample BI System Implementation Schedule .................................................................................76
Figure 25: Sample Web Portal Implementation Schedule ...............................................................................77
Figure 26: Change Management Framework ...................................................................................................78
Figure 27: Data Upload Details ........................................................................................................................82
Figure 28: NGCP Bill ........................................................................................................................................83
Figure 29: Power Supply ..................................................................................................................................83
Figure 30: Input and Output Energy .................................................................................................................83
Figure 31: Interruption ......................................................................................................................................85
Figure 32: Distribution Lines, Substation & Power Quality ...............................................................................85
Figure 33: Compliance to PDC .........................................................................................................................86
Figure 34: Compliance to PGC .........................................................................................................................87
Figure 35: BOD Meeting, Resolutions ..............................................................................................................90
Figure 36: BOD Accounts Payable, Advances .................................................................................................90
Figure 37: Connections - Delta .........................................................................................................................90
Figure 38: List of Employees - Delta ................................................................................................................91
Figure 39: Salary ..............................................................................................................................................91
Figure 40: Complaints.......................................................................................................................................91
Figure 41: Labor Management Issues - Delta ..................................................................................................92
Figure 42: Institutional - Others ........................................................................................................................92
Figure 40: Income Statement ...........................................................................................................................94
Figure 41: Balance Sheet .................................................................................................................................96
Figure 42: Power Accounts Payable ................................................................................................................97
Figure 43: Rates ...............................................................................................................................................98
Figure 44: Cash Flow........................................................................................................................................99
Figure 45: Accounting of Reinvestment Fund for Sustainable CAPEX (RFSC) ............................................100
Figure 46: Cash Advance ...............................................................................................................................100
Figure 47: Accounting of Universal Charge ....................................................................................................101
Figure 48: Prompt Payors ...............................................................................................................................101
Figure 49: Delinquent Customers ...................................................................................................................101
Figure 50: Schedule of Amortization Part 1 of 2 .............................................................................................102

Figure 51: Schedule of Amortization Part 2 of 2 .............................................................................................102
Figure 52: Power Supplier Agreement - Create New, Edit .............................................................................102
Figure 53: Substation - Create New, Edit .......................................................................................................103
Figure 54: BOD ...............................................................................................................................................103
Figure 58: Brand - Create New .......................................................................................................................104
Figure 59: Power Supplier - Create New, Edit ...............................................................................................104
Figure 60: Power Plant - Create New, Edit ....................................................................................................105
Figure 61: DDP - General Provision ...............................................................................................................106
Figure 62: DDP - Demand ..............................................................................................................................106
Figure 63: DDP - Supply Indicative ................................................................................................................107
Figure 64: DDP - DDP ....................................................................................................................................108
Figure 65: Projects..........................................................................................................................................108
Figure 66: Audit Findings ................................................................................................................................109
Figure 67: BOD and GM Performance Rating ................................................................................................109
Figure 68: Price Index.....................................................................................................................................110

1 Executive Summary
The Design Phase is the final and concluding phase of this project.
Based on the findings from the Inception and Discovery phases, the IT Design for NEA was prepared in
accordance with what will help NEA ultimately meet the mandate to support total electrification through the
technical and financial proficiency of the Electric Cooperatives (ECs).
Business Requirements
The primary needs recognized that will have to be addressed by the IT Design are:
(1) Receipt and organization of EC data, and
(2) NEA's analysis of EC data for more effective support to the ECs.
The IT System is expected to address the current process inefficiencies in reportorial submission and
management. Once the IT System is implemented and process inefficiencies are addressed, significant
enhancement in NEA’s effectiveness is expected as the system shall facilitate data exploration, mining and
analysis, enabling NEA to use accurate and timely data to more effectively fulfil its EC oversight function.
Once NEA starts using the technology and evolves in its data analysis maturity, it is expected that they will
then be performing even deeper, more insightful, more creative, and non-siloed analyses as a result of
having EC data that are easily accessible through the system.
Data Requirements
For effective analysis, data must be collected from the ECs in a structured format and granularity meant to
address the analysis needs.. Use of standard report templates with clearly defined data elements in the data
dictionary is necessary to facilitate data collection and enforce the right data format needed. These data will
be uploaded into the centralized data warehouse in accordance to the defined data models to allow data
mining, exploration and analysis. The recommended data models presented in this document were designed
to consider all the data needed to perform the BI analysis opportunities identified during the Discovery
Phase.
Once these data are uploaded in the data warehouse, various reports prepared by NEA and the ECs (i.e.,
MFSR, MER, MIR, Fact Sheet, etc.) can then be automatically generated by the system through regular
batch and/or ad-hoc processes. More importantly, pertinent analyses that are key to NEA’s fulfilment of its
EC oversight function can then be performed efficiently, with just a few clicks, as quality data will be readily
accessible in the system through the reports and dashboards which are standard features of a BI System.
The usefulness of the reports and dashboards is only as good as the quality of data used by the IT System.
As such, data integrity must be ensured throughout the end-to-end process of data collection, upload,
processing and consumption. For this reason, it is important to establish Data Governance to define a set of
policies, procedures and accountabilities aimed at ensuring integrity of data stored in the database to
manage end-to-end data quality. This involves establishment of processes for data management and
maintenance, as well as definition of data owners and custodians for the data specified in the data models.
Data Governance has to be in place before the system goes live to ensure that there is appropriate control
needed to maintain the quality of data used by the data consumers.
Application Architecture
The technology identified to support the business requirement of supporting efficient EC data collection and
providing effective data analysis is an IT System composed of a BI System and a web portal. The web portal
will serve as a data entry facility with which the ECs and NEA can upload data through structured templates.
These templates are to be populated offline to address the internet access limitations of some ECs. The BI
System, on the other hand, will be the technology for data organization, storage and processing which NEA
can use to analyse EC data. The designed BI System is composed of three components: (1) Data Integration
layer, the component that collects raw data from sources, transforms it into structured data and loads into the
data warehouse. (2) Data Warehouse, the central storage of data for analysis, and (3) Business Intelligence

layer, the component that provides user interface for data analysis, simulations, dashboard and report
preparation; this can be used to prepare reports and dashboards on trends and correlation, combine and
simulate scenarios using a mix of Financial, Institutional and Technical (FIT) data for policy and decision-
making, strategizing and planning how to support the ECs.
Figure 1: BI System Components

BI Technology Components
Data Business
Warehouse Intelligence
Layer
Relational • Database access
Database • Audit user activities
• Secure and Control
Reporting & Analytics

Metadata • Standard/Template
Submitted Reports
• Predictive Models
Data • Historical Data
Data Model and Analysis
Integration
• Custom search and
filters
• Charts, Graphs &
other Analytics
ETL
Integration
Metadata
Extract,
Data Entry Analyze, Publish &
Transform Query & Mine
Web Portal Share
& Load
Comparison of major software products available in the market was also done to highlight strengths and
weaknesses, which can serve as inputs to the software product evaluation to be conducted in the next
phase.
Technology Architecture
One key aspect in any solution is having the necessary infrastructure resources to run the solution. This will
help ensure that the desired system performance is achieved during the day-to-day operation of the system.
The recommended system architecture for the IT System is illustrated below (Figure 2). As the system will be
exposed to external users (ECs, DOE, ERC, etc.), the architecture should have a demilitarized zone where
some system components will be located to provide a secure channel or gateway for external users to
access the system and view information stored in the system without affecting the internal components of the
system.
Figure 2: Server Landscape

The server requirement is described in the table below (Table 1). This specification is based on the
estimated number of concurrent users on peak hours, number of simultaneous transactions, volume of
upload and download data expected, among others.
Table 1: Hardware Specifications

WEB PORTAL BI
Data Data Data
Application Database
Web Server ETL Server Warehouse Warehouse Warehouse
Server Server
Web Server APP Server DB Server
CPU
2 Cores 4 Cores 4 Cores 4 Cores 2 Cores 4 Cores 6 Cores
(Cores)
Memory
8 GB 32 GB 32 GB 16 GB 8 GB 16 GB 32 GB
(GB RAM)
System
100 GB 100 GB 100 GB 100 GB 100 GB 100 GB 100 GB
Disk Space
1.5TB (3x500
GB with FC
Data Disk
300 GB 1 TB 1 TB 300 GB 300 GB 1 TB Card to
Space
connect via FC
to SAN)
Windows, Windows, Windows, Windows, Windows, Windows,
Windows, Linux
OS Linux or Linux or Linux or Linux or Linux or Linux or
or equivalent
equivalent equivalent equivalent equivalent equivalent equivalent
Any RDBMS
Software
that can
(for
N/A N/A provide the N/A N/A N/A N/A
Database
required
Servers)
functionalities.
Service Delivery Options

There are different options for the service delivery of the IT System and these include On-Premise or Cloud.
On-Premise is a service delivery model where the system is installed and operated from an organization’s in-
house server and computing infrastructure. As for Cloud, this can either be Software as a Service (SaaS),
Platform as a Service (PaaS), Infrastructure as a Service (IaaS) or a hybrid of the three.
SaaS is a model of service delivery where one or more applications and the computational resources
to run them are provided for use on-demand as a turnkey service.
PaaS is a model of service delivery where the computing platform is provided as an on-demand
service upon which applications can be developed and deployed.
IaaS is a model of service delivery where the basic computing infrastructure of servers, software,
and network equipment is provided as an on-demand service upon which a computing platform to
develop and execute applications can be established.
The main advantage of a Cloud service delivery model is that hosting of software, platform and infrastructure
will be in the Cloud service provider’s environment, allowing the organization to avoid high upfront capital
expenditures upon system implementation. Its main drawback, however, is a generally higher recurring
operation cost for the continued use of the service during the entire system lifecycle. Additionally, the
organization’s critical data and application assets will be in the custody of and are accessible to the Cloud
service provider.
A wide variety of service delivery combinations exist within the Cloud option permuting different scenarios on
where the software, platform and infrastructure are hosted. For instance, a SaaS solution may be
implemented either with an IaaS model or as a "Bring Your Own License" (BYOL) scheme which can be
treated similar to an on-premise delivery from a SaaS provider; furthermore each of the three layers of the BI
System may be implemented either on-premise or on-cloud. The range of Cloud options is wide. For this
reason, a quick comparison was made based on two major scenarios: 1) full on-premise where all
components (software, platform and infrastructure) are on-premise, and 2) Cloud delivery model where all
software applications with BYOL scheme are hosted in the cloud. The 5-year total costs of ownership (TCO)
were compared for these two scenarios. The TCO comparison shows that implementing the full cloud
scenario is more expensive than full on-premise, but the latter does not incorporate other costs such as
manpower and manpower development (training) to maintain the hardware, cost of rental or space for a data
center and its maintenance, data center engineering, and environmental strengthening needed for full on-
premise installation. Moreover, this estimate should be interpreted with care as IT vendors can leverage on

their individual strengths, competitive advantages, and partnership with other IT vendors, hence can be
creative in offering a solution combining different delivery options (cloud or on-promise), software products
(commercial – best of breed, commercial – end-to-end, open source) per software component, and hardware
products to offer a cost-effective solution package that addresses the client’s functional, technical and
budgetary requirements. Further, the listed prices of software products and hardware components offered by
vendors are typically not fixed, and significant discounts can be offered during bidding and negotiation
depending on factors such as the size and complexity of the project, partnership with the software vendor,
reseller discount, and strategic value of the project on their business, among others. Thus, estimates
presented in this Design Report should be used for initial estimation purposes only. The more important
aspect is that the organization should understand the various options available, the advantages,
disadvantages and risks of each option, and how these risks can be mitigated to select the most appropriate
system and delivery option that will address the organization’s business needs.
When the IT System goes live, regardless of the delivery model utilized, service delivery standards have to
be satisfied to ensure efficient system operations. These include standards on service availability, security,
and operation and maintenance, and an exit process for the case of cloud delivery. Guidelines on these
standards are also provided in the report.
Implementation Phase
As presented in the schedule below, the expected duration for the implementation of both the web portal and
BI System is 10 months, with concurrent implementation of the two systems and excluding the additional
year for post-implementation support.
Figure 3: Implementation Schedule

Year 1 Year 2 Year 3
1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3
1 Establish a project team
2 Implementation Planning
3 Bidding and Awarding
4 Orientation to System Implementation
5 Implement Web Portal
6 Data Cleansing and Alignment (Optional)
7 Historical Data Upload (Optional)
8 Training/Cascade to NEA and EC End Users
9 Implement BI System
10 Prepare policies, procedures and guidelines
11 Training on Portal and BI Application Administration (for IT)
12 Employee orientation relevant to system/s implemented
During the Implementation Phase, an effective change management strategy is necessary to facilitate
acceptance of the change and promote commitment of stakeholders on the project. Key aspects of Change
Management include proper communication of change, strong leadership and support from management,
capacity building, and measurement of key result areas and success factors of the project. Change
management is important during implementation to minimize resistance to change and promote a smoother
transition from the current to the envisioned state, increasing the factors that will make NEA attain the
project’s objective of promoting more effective support to the ECs through the use of technology that
facilitates efficient data collection and management.
2 Business Requirements
The foremost objective of the NEA IT Design Project is to support how NEA can be more effective in meeting
the mandate of total electrification. Currently, data is submitted by the ECs in MS Excel files containing
reports that are not uniform in format when submitted. Additional data comes from the biennial activity, the
eICPM, where ECs prepare their demand, sales and financial forecasts. All the data received by NEA is
processed to extract the relevant data which is summarized further into more reports. This activity entails re-
encoding and extensive word processing activities that take up NEA resources. Often, the focus is derailed
from getting a thorough and comprehensive understanding of the ECs to meeting report submission
deadlines.
To support the objective of understanding the data to provide ECs with guidance and advice, these are two
key business needs realized throughout the duration of this project, which this project intends to address:
(1) Receipt and organization of data from the ECs, and;
(2) Analysis of data from the ECs to arrive at effective feedback and action plans.
During the Discovery Phase, data collected from ECs was dissected to arrive at analysis opportunities that
could further enhance NEA's regular review and assessment of the ECs' operating situation, in accordance
to NEA’s mandates of total electrification, ensuring EC financial viability and technical proficiency,
implementing EC governance, receipt and monitoring of reports, restructuring of ailing ECs, and support for
deregulation. The analysis opportunities were identified from the perspective of data being strategically
organized and accessible with the help of Business Intelligence (BI) technology and will serve as the basis
for the design details presented in this Design Report.
The implementation of a BI System is expected to address the process inefficiency of reportorial submission.
Once the technology is implemented, improvement in effectiveness is expected to follow as the tool shall
facilitate data exploration, mining and analysis. The identified BI support opportunities specified in the
Discovery Report are just the initial list of possible analyses that can be done by NEA to more effectively fulfil
its EC oversight function. Once NEA starts using the technology and evolves in its data analysis maturity
level, it is expected that NEA will then be performing deeper, more insightful, more creative, and non-siloed
analyses as a result of having accurate, timely and readily available EC data that will be easily accessible
through the system.
In addition, during the Discovery Phase, it was also realized that there are ECs in locations that have internet
connection problems. Hence, it is imperative that the IT System be designed such that this constraint will not
hinder the efficient submission and uploading of data into the centralized database that will be for NEA's
various analyses.

3 Data Requirements
As much as data is critical to NEA's operations, its handling is fundamental in BI technology. This section
aims to discuss how data will be received and managed moving forward with such a system.
Data will enter the system through defined data entry templates with fixed fields and expected values (i.e.,
numeric, 10 characters, 4 decimal places, value 1, 2, n, etc.). These templates will contain the data sufficient
to generate the MER, MIR, MFSR, MPSMR and other key outputs. It is critical that the content of these
templates be established and followed accordingly as validation rules could be set up in the system to
ensure only the required and correct data are entered in the system. Once loaded in the system, the data will
be organized according to defined the Data Models.
To ensure common understanding of each data item, a Data Dictionary was initialized through this project
which NEA will maintain moving forward. This can also be further elaborated or refined by the system
implementor to incorporate other data entities that will be decided on in the final technical design during the
implementation phase. Aside from this, certain governance procedures relevant to data management will
have to be established and practiced.
The initial data content of the NEA IT system recommended will rely on a data upload activity to enter
historical data into the system. As one of the activities in preparation for implementation, guidance is
provided in this document. Lastly, also in preparation for implementation, NEA must decide on how long data
must be available in the system, as well as the procedures for obtaining data beyond the defined period of
availability.
These data requirements are described in more detail in the succeeding sections.
3.1 Data Entry Templates

The content of the data entry templates must be standard fields that will receive all the data required by NEA,
regardless of department. This will require a standard understanding across NEA and the ECs of what
1
specific fields mean and how they should be calculated . For instance, if NEA will require the ECs to submit a
balance sheet, the components that make up a balance sheet should be uniformly established in the
template and complied with by the ECs. Additional line items and adjustments will not be accepted by the
template and by the system.
The Design Report includes sample data entry templates designed based on the reports currently required
2
by NEA from the ECs, reports generated by NEA and the BI Analysis items raised in the Discovery Report.
Redundancies across the MFSR, MER and MIR are eliminated. There are field names or column headers
that were renamed to follow the standard terms, aligned with the Data Dictionary. There are new fields added
to support additional data required by BI Analysis items (i.e., Start Date of Meter Reading, End Date of Meter
3
Reading). Fields for calculated or summarized data are removed while fields for its granular data are
retained and/or re-organized: for example, Total Number of Sustained Customer Power Interruption is no
longer required to be manually entered; instead the interruption details, same details sent to the Distribution
Management Committee (DMC), is required in the designed data entry template. The system will perform the
calculations to generate the required measures coming from these granular data.
During the Discovery Phase, it was noted that there are ECs that make use of NEA's reportorial
requirements for their own analysis. As such, the data entry templates were designed in a similar manner to
retain this advantage for the ECs, such that the some pertinent values will have to be calculated offline
based on values entered in other fields. For example, existing financial reports require two (2) values to
calculate the variance. In the data entry templates, the variance will be calculated in the template itself based
on EC-entered values, but the system need not pick up the variance values, rather the system will store only
the EC-entered values and calculate the variance within the system.
Having these standard data entry templates will be beneficial as follows:
1
Governed by the Data Dictionary described in Section 3.4 Data Dictionary
2
Complete list in Section 3.3 Key Outputs.
3
Some fields for calculated or summarized data are retained in the Data Entry Templates but only for EC’s reference while
accomplishing the template. These fields will not be picked up by the web portal; instead, necessary calculations to generate different
measures using similar granular data will be performed in the system.
 For the ECs – data required will be entered and submitted in a single instance only. No more
4
multiple entries of the same data.
 For NEA - the templates and web portal will require and accept the defined values only. Data
received from the ECs will be in the same format and granularity for easier comparison and analysis
without data re-encoding.
The templates are recommended to be in MS Excel format so that these can be completely populated by
5
ECs with or without automated systems or a stable internet connection . Accomplished templates will then be
uploaded into the web portal.
The mature technology options available for the report submission templates include electronic forms (such
as but not limited to those sold by software companies such as Adobe, Microsoft, IBM, etc.) as well as
spreadsheets (e.g. Microsoft Excel). These technologies can address the requirement of allowing ECs to
enter structured data into the templates offline without the need for internet connection. These technologies
also allow certain fields to be calculated based on the data entered in other fields, as well as provide offline
data validation as first level data check (e.g. data should be numeric, data should be in the pre-defined list of
valid values, value should be positive, etc.). However, some features of electronic forms cannot be
maximized due to internet limitations of some ECs in remote locations. These features include online
workflow management, online approval of forms, online collaboration for accomplishment of the form, etc.
require reliable internet connection. On the other hand, using MS Excel as a template addresses the
requirement for data entry and provides advantages such as (1) familiarity of both NEA and ECs with the
tool, requiring minimal effort to transition (2) high usability as it is easier to enter multiple data fields in
spreadsheets and allows copy-pasting of values from other external files (3) NEA and most ECs (if not all)
are already using and have existing licenses for Microsoft Excel. For any technology, built-in security
features of the technology to secure the templates must be utilized to protect the template (formulas, list of
valid values, format, etc.) from being manipulated by the ECs or other unauthorized users. This must be
6
complemented by policies and penalties/sanctions for those who will manipulate the standard templates .
Data entry will not only for ECs' monthly reportorial requirements. Data from the biennial eICPM will also be
uploaded to track and monitor developments in the planned projects of the ECs, especially projects in
support of total electrification. Also, there are data entry templates designed to enter data from NEA such as
Audit Findings.
Samples of these envisioned data entry templates are provided in Annex 6.1. It must be noted that the data
entry templates are samples and are for illustration purposes only. It is expected that the system
implementor will further refine and elaborate on the templates as needed, for their detailed technical
specification prepared.
3.2 Data Models

A Data Model is a structure that organizes data elements, their format and standardizes how the data
elements relate to one another in a data warehouse.
7
In the NEA IT System, the Data Model is further structured into five Subject Areas :
1. Energy Sales - contains data on EC sales, rates and related statistics such as energy demand
2. System Performance - contains data on the ECs' distribution assets such as substations and circuit
lines, as well as data on energy supply, reliability and safety
3. Financial Performance - contains EC financial data
4. Institutional Information - contains EC institutional data such as BODs, employees, performance
ratings
5. Project Statistics - contains data on EC projects such as those reported during the eICPM workshop
and project status
Relating these five Subject Areas back to the F-I-T NEA data classification: Financial Performance subject
area contain data under "Financial". Data covered by the System Performance subject area are those under
4
These templates are designed to replace the MFSR, MIR, MER, PSMR templates, etc. currently used by the ECs to submit required
data. Instead, the MFSR, MIR, MER and other reportorial requirements will be prepared using the NEA IT System based on submitted
data.
5
Since there are ECs that might not be able to comply with online entry of templates, the offline option ensures that all ECs will be able
to comply.
6
Other government regulatory agencies that have implemented BI (e.g. Bangko Sentral ng Pilipinas) have established policies and
sanctions to prevent manipulation of standard templates (e.g. Bangko Sentral ng Pilipinas as regulator of universal, commercial, thrift,
rural and cooperative banks);
7
There is a single Data Model designed for the NEA IT System, however, for presentation purposes in this document, the Data Model is
presented per Subject Area.
"Technical". Project Statistics and Energy Sales subject areas contain data related to both Financial and
Technical. Institutional Information is similar to "Institutional".
Sections 3.2.1 to 3.2.5 present the Data Model for each of the Subject Area. Each of the section is also
accompanied with a Multi-Dimensional Analysis Matrix. The Multi-Dimensional Analysis Matrix presents how
the subject areas can be analyzed through the dimensions (listed in the left-most column).
As an example, Figure 4, a portion of the Multi-Dimensional Analysis Matrix for the Subject Area Energy
Sales, shows that data related to Energy Output Statistics can be analyzed using the Calendar, EC Profile,
Location Details and Class of Service Type dimensions. Specifically, this means that Power Sales (kWh)
(stored in the Energy Output Statistics table) can be analyzed by looking at Power Sales per month, quarter
or year (under the Calendar dimension). Furthermore, Power Sales can be analyzed using the combination
of Power Sales per month, quarter or year per Class of Service (i.e. Residential, Commercial, Industrial) per
region and so on.
8
Figure 4: Portion of Multi-Dimensional Analysis Matrix for Energy Sales
Additionally, the matrices also show cross-analysis of subject areas wherein data from different subject areas
may be compared using the same dimensions. To illustrate, Sales per Employee (Energy Sales Subject
Area) and Salaries (Financial Performance Subject Area) can be compared using the Island Group
dimension (Location Details) that can show, for example, in Luzon, ECs with higher Sales per Employee
have higher employee salaries, but in Visayas, the profile is the opposite.
Figure 5: Cross-Analysis of Subject Areas
8
Complete table in Section 3.2.1
3.2.1 Subject Area: Energy Sales
Figure 6: Energy Sales Data Model
P rojec ted Connections

Date ID
Grid Ty pe E C ID
Grid Ty pe ID [0,n ] [0,1 ]
Grid Ty pe ID
[0,1 ] Class of S erv ic e ID
Grid Ty pe Name Rel a ti o n_ 2 69 6
Des cription V alue
S tart D ate
Calendar Dimension
E nd D ate Rel a ti o n_ 1 15 3 8 P rojec ted Demand
Char D ate ID
Date ID Rel a ti o n_ 1 15 3 9 Calendar Date [0,1 ]
[0,1 ]
E C ID Full Name Calendar D ate
[0,n ]
[0,n ] Class of S erv ic e ID Day N ame E nergy O utput S tatistics
Rel a ti o n_ 2 75 7 Grid Ty pe ID Day in W eek No [0,n ]
Rel a ti o n_ 2 69 7 Date
[0,1 ] P eak Utility Time Day in Month E C ID
Utility Consumer Ty pe P eak Utility Month W eek in Month No Class S ervic e Type ID
Utility Consumer Ty pe ID Rel a ti o n_
[0,n
1 15
] 04 P eak Demand V alue W eek in Y ear N o
[0,1 ] [0,n ]
[0,1 ]
Meter Reading S tart D ate
Utility Consumer Ty pe Name P rojec ted Utility E nergy Consumption and D emand Month Name Meter Reading E nd Date
[0,n ]
Des cription Date ID Month No Count of A ctual B illed Connections
[0,1 ] Rel a ti o n_ 2 75 8 Y ear Month
S tart D ate E C ID Initial Count of C onnec tions
E nd D ate Rel a ti o n_ 2 75 9 Month A go [0,1 ]
Grid Ty pe ID [0,1 ] Count of D is c onnec tions
Rel a ti o n_ 2 03 [0,n ] Y ear
Utility Consumer Ty pe ID [0,1
Rel] a ti o n_ 1 15 4 1 Count of R ec onnec tions
[0,n ] Y ear A go
E nergization S tatus [0,n ] [0,1 ] P ower S ales (k W h)
Date ID [0,1 ]
Quarter Rel a ti o n_ 1 14 7 4 Count of Min B ill
E C ID [0,1 ] Quarter A go [0,n ] P ower Coop Us ed
Count of E nergiz ed [0,n ]
S eason E nergy RRel
ecovered
a ti o n_ 1 15 9 0
Rel a ti o n_ 9 62 Fis c al S tart [0,n ]
Connections S erved Total O utput (Deriv ed)
Fis c al E nd Max D emand (D eriv ed)
Unbundled R ates
Rel a ti o n_ 1 44 7 P ower S ales (A mount B illied)
Date ID [0,1 ]
E C P rofile P eak Demand
Charge Ty pe [0,n ] E C ID [0,1 ]
[0,1 ] E C ID A s s et Data C ompletion in S y sLos s S egregation Tool as of las t update
Charge Ty pe ID Rel a ti o n_ 1 14 9 0 Charge Ty pe ID
Charge Ty pe Name E C Name
Lifeline R ate
Des cription [0,1 ] Grid Ty pe Rel a ti o n_ 1 14 7 3
Universal Charge Rel a ti o n_ 1 44 9 [0,n ]
[0,n ] S tart D ate Rel a ti o n_ 2 69 8
S tart D ate
[0,1 ]
E nd D ate E nd D ate
[0,1 ]
Charge Ty pe A mount Date of Inc [0,n ]
Rel a ti o n_ 1 15 9 2
Date of First E nergen
[0,n ]
E C P rofile H istory Loc ation D etails Members hip
[0,n ]
S urrogate E C ID B arangay ID P S P Clas sification
E C ID Inc ome C las s ID RS E C W R Class ific ation
Loc ation D etails History
E C Name Dis tric t CD A Clas sification
City B arangay ID Class of S erv ic e Ty pe
Grid Ty pe
P rovince [0,1 ]
[0,n ] Dis tric t
E ffectivity Date Rel a ti o n_ 4[0,n
78 0] Class of S erv ic e ID
Region
Rel a ti o n_ 4 79 8 City
Date of Inc [0,n ]
Rel a ti o n_ 1 03 0 [0,1 ] Rel a ti o n_
[0,n ] 9 1 Class of S erv ic e Ty pe Name
1 15
Island Group [0,1 ] P rovince
Date of First E nergen S tart D ate
S tart D ate Region
Members hip [0,n ] E nd D ate
E nd D ate Island Group
P ower S ourc e Rel a ti o n_ 1 03 1 E C Geography
S us ceptibility to Ty phoon E ffectivity Date
Urban Rural Class ific ation [0,1 ] E C ID
P opulation B arangay ID
P er Capita Income

Table 2: Energy Sales Multi-Dimensional Matrix
Table
Projected Utility
Energy
Energy Projected Projected Unbundled
Output
Consumption Demand Connections Rates
Statistics
and Demand
Dimension Calendar x x x x x
EC Profile x x x x x
Location Details x x x x x
Class of Service Type x x x x x
Grid Type x x x x
Charge Type x x

3.2.2 Subject Area: System Performance
Figure 7: System Performance Data Model
Power Sup pl y Fo re ca st
Date I D
EC
Power Plan t ID Sys te m St at is tic s
Fue l Re qu ire m en t L oc at io n De ta ils Hist ory EC Ge og ra ph y Date
In st al le d Ca pa ci ty Relat ion_7594
L oc at io n De ta ils Relat ion_1698
EC I D EC I D
[Bara
0, 1] n ga y ID [ 0, 1]
Net De p en da b le Ca pa c ity Relat ion_7595
Dist ric t [ 0, 1] Bara n ga y ID Bara n ga y ID Pea k Lo ad (KW)
Net Prod uc ti on L oa d Fa ct or
City In co m e Cl as s ID [ 0, 1]
Con tra c ted De ma n d [ 0, 1] [ 0, 1]
Relat ion_1031 M AI FI
Prov in c e Dist ric t [ 0, n] Relat ion_1697
Con tra c ted En erg y [ 0, 1] SAIDI
Reg io n City
Cap ac it y Us ed fo r Own Lo ad Relat ion_4798
SAIFI
Is la nd Gro up Prov in c e
Ene rg y Us ed f or Own Lo a d SARVI
Effe ct iv ity Dat e Reg io n [ 0, 1]
Ene rg y Su pp ly [ 0, n] CAIDI
Is la nd Gro up
Firm Co ntrac te d Ca pa c ity Relat ion_1722
[ 0, 1]
Sys te m Lo s s
[ 0, n] Start Da te EC Pro fi le Hi st ory
Power Sup pl y Sta ti sti cs End Dat e Surrog a te EC I D Tec hn ic al L os s
Power Sup pl ie r Power Sup pl ie r His tory Relat ion_1030
Non te ch ni ca l Lo ss
Date Sus ce p tib ili ty to Typ ho o n EC I D
Power Sup pl ie r ID Surrog a te Po wer Su pp li er ID [ 0, n] Sys te m Lo s s Ca lc ula ti on Too l
EC I D Urba n Rura l Cl as si fic at io n EC Na m e
Power Plan t ID Relat ion_4780
Sup pl ie r VAT Reg TIN Pop ul at ion [ 0, n] [ 0, 1] Grid Typ e Date o f La st Upd at e
Plan t Na m e Relat ion_7596
Power Plan t ID
Sup pl ie r Nam e [ 0, 1] Per Ca p ita In c om e [ 0, n]
Effe ct iv ity Dat e Ass et Date
Plan t In form at ion Actu a l Dis pa tc he d M ax Powe r
Sup pl ie r Add re ss Power Plan t Date o f Inc
Plan t Lo ca ti on Actu a l Dis pa tc he d En e rg y [ 0, n]
Sup pl ie r Con ta ct No Power Plan t ID Date o f First Ene rg en
Plan t Ty pe Curt ai le d En ergy
Sup pl ie r Con ta ct Pers o n Sup pl ie r ID M em b e rsh ip
Sup pl ie r Typ e Sup pl ie r VAT Reg TIN Relat ion_7480 Plan t Na m e Power Sou rc e
Plan t Owne r ID EC Pro fi le
Plan t In form at ion Ene rg y Inp u t Sta tis tic s
Cap ac it y (M W) Plan t Lo ca ti on [ 0, 1] EC I D
[ 0, 1] Date
[ 0, n] Con ne c tio n Po in t Plan t Ty pe EC Na m e
Fue l Re qu ire m en t Relat ion_11423 Relat ion_1652 Grid Typ e EC I D
[ 0, n] VAT Reg TIN [ 0, 1] Relat ion_1654
[ 0, 1]
Relat ion_7530 [ 0, n]
Power Sup pl ie r Typ e [ 0, n] Start Da te [ 0, n] Ene rg y Pu rc ha se d
Cap ac it y (M W)
[ 0, 1] Stat us
Relat ion_1721
Relat ion_11422
End Dat e [ 0, n] Ene rg y Ge ne ra te d
Con ne c tio n Po in t [ 0, n] [ 0, 1]
Effe ct iv ity Dat e Date o f Inc Tota l In pu t
Fue l Re qu ire m en t
Relat ion_4057 Date o f First Ene rg en
Relat ion_7533 Power Sup pl ie r Typ e [ 0, n]
Power Plan t De ta ils [ 0, n] Stat us [ 0, n] M em b e rsh ip
[ 0, n] Relat ion_3886 Relat ion_3882
[ 0, n] PSP Cla ss ifi ca tio n
PP I D Proj ec te d Ut ili ty Lo ad
Relat ion_7529 RSEC WR Cla s sif ic ati on
Power Plan t ID [ 0, 1] Date I D
[ 0, 1] [ 0, 1] [ 0,[n]
0, n] CDA Cla ss ifi ca tio n
Power Sup pl ie r ID EC I D
Dist rib u tio nCo de Com p lia nc e Grid Co d e Co m pli an ce Relat ion_3880 Power Plan t ID
[ 0, 1]
Sub st at ion De tai ls Hi st ory Date I D Date I D [ 0, 1] [ 0, 1]
Con tra c ted Pe ak Dem a nd k W
Power Sup pl ie r Agree m en t
Surrog a te Su b sta ti on ID EC I D EC I D [ 0, n] With d ra wn Cap ac it y k W
EC I D Com p Grid ID
Sub st at ion I D (Se ri al No ) Com p Dist ID Con tra c ted En erg y M Wh
Power Plan t ID App lic a ble Pa ram Co un t [ 0, n]
Rate d Cap ac it y App lic a ble Pa ram Co un t With d ra wn Cap ac it y M Wh
Agre e m en t Sta rt Da te Circ ui t L in e Proje c tio n
Sub st at ion Ty pe Com p lia nc e Cou nt Com p lia nc e Cou nt
Agre e m en t En d Da te [ 0, n]
L oc at io n Stat us o f Co m pli an ce (De riv e d) Stat us o f Co m pli an ce (De riv e d) Date I D Relat ion_7700
ERC Cas e ID Com p lia nc e Ass es sm e n t (De riv ed ) [ 0, n] [ 0, 1] [ 0, 1]
Bran d Com p lia nc e Ass es sm e n t (De riv ed ) Relat ion_4060 [ 0, 1] EC I D
Con tra c ted Pe rio d
Own ersh ip Circ ui t L in e ID
Ann ua l Co nt ra cte d Ca p ac ity [ 0, n][ 0, n] [ 0, n]
Tran s fo rm er Unit R
[el
0,at1]ion_11417 [ 0, 1]
Circ ui t L in e va lu e
Ann ua l Co nt ra cte d En e rg y
Fee de r [ 0, n]
[ 0, 1] Relat ion_11418
Con ne c tio n Po in t [ 0, n]
Gen Set [ 0, 1] Relat ion_4058 Circ ui t L in e Ty pe
Disp a tc h Se qu en c e Relat ion_7532
KVA Rat ing Com p lia nc e Di strib uti on Cod e Com p lia nc e Grid Co de [ 0, n] Circ ui t L in e ID
Fue l Re qu ire m en t
In st al la tio n Da te Com p Dist ID Com p Grid ID Circ ui t L in e Ty pe
In st al le d Ca pa ci ty
Effe ct iv ity Dat e Title Title [ 0, 1] Cale n da r Dim e ns io n Start Da te
Net De p en da b le Ca pa c ity
Para m Cou n t Para m Cou n t Relat ion_4059 End Dat e
Net Prod uc ti on Cha r Da te ID
Relat ion_5839 Relat ion_11419 Cale n da r Da te
[ 0, 1] Con tra c ted De ma n d [ 0, 1] [ 0, n]
[ 0, 1]
[ 0, n] Relat ion_7531
Relat ion_4909 L oa d Fa ct or Full Nam e Cal en da r Da te
Com p lia nc e Grid Hi sto ry [ 0, n]
Con tra c ted En erg y Com p lia nc e Di strib uti on His to ry Day Nam e
[ 0, n] Surrog ra te Grid ID Day in We ek No Circ ui t L in e St ati st ics
[ 0, 1] [ 0, 1]
Surrog ra te Dis t ID
Com p Grid ID Day in M o nt h Relat ion_1593 Date [ 0, 1]
Com p Dist ID
Sub st at ion De tai ls Sub st at ion Sta tis ti cs Title [ 0, n] Wee k in M o nt h No EC L o ca tio n Relat ion_1592
Title Relat ion_1720
Sub st at ion I D (Se ri al No ) Para m Cou n t Wee k in Yea r No Circ ui t L in e ID
Date Para m Cou n t [ 0, n]
L oc at io n Effe ct iv ity Dat e M on th Nam e Circ ui t L in e Va lu e
EC I D Effe ct iv ity Dat e [ 0, n]
Bran d [ 0, 1] M on th No [ 0, n] [ 0, 1] M ON
Sub st at ion I D Relat ion_1594
Own ersh ip Relat ion_1677 Sub st at ion Ca pa ci ty Proj ec tio n Yea r M o nt h
Sou rc e Vo lta g e Pe ak
Tran s fo rm er Unit [ 0, n] [ 0, 1] M on th Ago
Sou rc e Vo lta g e Off Pe a k Date I D Relat ion_1679
Fee de r Yea r
Sec on d ary L in e Cu rre n t A EC I D
Gen Set Yea r Ag o
Sec on d ary L in e Cu rre n t B Proj ec ti on Typ e
KVA Rat ing Qua rte r
Sec on d ary L in e Cu rre n t C Tran s fo rm er Typ e
Stat us [ 0, 1] Qua rte r Ag o
Pea k No o f un its
In st al la tio n Da te Relat ion_1678 Sea so n
Power Fac to r
[ 0, n] Fisc a l Sta rt
L oa d Fa ct or
Fisc a l End
Perc e nt Lo a di ng

Table 3: System Performance Multi-Dimensional Analysis Matrix
Table
Power Power Power Substation Circuit Circuit Projected Energy Distribution Grid Code
Substation System
Supply Supplier Supply Capacity Line Line Utility Input Code Comp-
Statistics Statistics
Forecast Agreement Statistics Projection Projection Statistics Load Statistics Compliance liance
Calendar x x x x x x x x x x x x
EC Profile x x x x x x x x x x x x
Location Details x x x x x x x x x x x x
Dimension
Class of Service Type x x x x x

Power Plant x x x
Power Supplier x x
Substation Details x x
Circuit Line Type x x
Distribution Code x
Grid Code x

3.2.3 Subject Area: Financial Performance
Figure 8: Financial Performance Data Model
To p 1 0 Pro m p t Pa y o r Cu s to m e r
Po we r S u p p li e r Bi ll in g
NGCP Bi ll in g Da t e I D
Po we r S u p p li e r I D Relation_5696
Relation_7661
EC ID Cl a s s o fSe rv ic e Ty p e
[ 0, 1]
St a te m e n t Da t e ID EC ID [ 0, 1] Relation_11623 [ 0, 1]
Cl a s s o f Se rv i c e ID
Relation_5691 L o c a t io n I d [ 0, n]
[ 0, 1] EC ID Bi ll St a rt Da te Relation_5694 EC Pro f i le His t o ry Cl a s s o f Se rv i c e Ty p e Na m e
[ 0, n] Relatio[n_5693
0, n] Cl a s s o f Se rv i c e ID
Bi ll in g De t e rm i n a n t ID BI ll En d Da[ 0,t e1] [ 0, 1] Su rro g a te EC I D Rela[tio
0,
[ n_11622
0,1]n]
St a rt Da te
Cu s t o m e r Ac c o u n t No
Relation_5692 BI ll Re f No Bi ll De t e rm i n a n t I D Ca l e n d a r Di m e n s io n EC ID En d Da t e
[ 0, n] [ 0, 1] Cu s t o m e r Na m e
[ 0, n] BD Va lu e Bi ll Re f No Ch a r Da te ID EC Na m e No o f Da y s Be f o re De a d l in e
To t a l Ch a rg e s BD Va lu e Ca l e n d a r Da t e Grid Ty p e
Relation_7662 Am o u n t
Bi ll in g De t e rm i n a n t To t a l Ta x e s To t a l Ch a rg e s Fu l l Na m e Ca l e n d a r Da te Ef fe c t iv it y Da t e
Bi ll in g De t I D To t a l Ta x e s Da y Na m e Da t e o f In c
De t e rm i n a n t Na m e [ 0, n] Da y in W e e k No Da t e o f Firs t En e rg e n
Fi n a n c i a l Ch a rt o f Ac c o u n t s
De s c rip ti o n [ 0, n] Da y in M o n th
Ac c o u n t ID M e m b e rs h i p
[ 0, n] Ag g re g a t e d Fi n a n c i a l M e a s u re s
St a rt Da te W e e k i n M o n t h No Po we r S o u rc e
De s c rip ti o n
En d Da t e [ 0, n] RR
ela
elatio
tion_7634
n_778 W e e k i n Ye a r No Da t e I D
Fi n a n c i a l Gro u p in g [ 0, n] [ 0, n]
Relation_777 M o n th Na m e EC ID
Re p o rt Gro u p in g Ba l a n c e Sh e e t [ 0, n]
M o n th No De b t Se rv i c e
St a rt Da te Da t e I D [ 0, 1]
[ 0, 1] Ye a r M o n t h Relation_197 L i q u id i t y
En d Da t e [ 0, 1] EC L o c a t io n ID
Relation_4846 M o n th Ag o Ca s h Ge n e ra l Fu n d
Ac c o u n t Ty p e ID
Relation_13813 Ye a r [ 0, n]
[ 0, 1] Co n s u m e r Ac c Re c e i v a b l e s
Fi n a n c i a l Ch a rt o f Ac c o u n t s His t o ry [ 0, 1] Ac t u a ls [ 0, n]
[ 0, 1]
Ye a r Ag o [ 0, n] Re i n v e s t m e n t Fu n d
Su rro g a te Ac c o u n t I D Qu a rte r Ca s h Ad v a n c e
Ac c o u n t ID [ 0, n] [ 0, 1]
Relation_760 Qu a rte r Ag o No n Po we r Co s t
[ 0, 1]
De s c rip ti o n Se a s o n Co l le c t i o n Ef fi c i e n c y
[ 0, n] Relation_7686
Fi n a n c i a l Gro u p in g Fi s c a l St a rt Pric e In d e x As s e t T u rn o v e r
Re p o rt Gro u p in g I n c o m e a n d Ex p e n s e Bre a k d o wn
[ 0, 1] Fi s c a l En d Da t e I D Po we r A c c o u n t s Pa y a b le
Ef fe c t iv it y Da t e Da t e I D [ 0, n] [ 0, 1]
[ 0, 1]
[ 0, 1] EC ID EC ID
Un i v e rs a l Ch a rg e Relation_761 I te m I D
Ac c o u n t Ty p e ID [ 0, 1]
UC OR No [ 0, n] [ 0, 1] I te m Cl a s s i fi c a t io n
Relation_13812 Ac t u a ls Relation_199 [ 0, 1]
UC SBR No [ 0, 1] EC Pro f i le EC Un it Pri c e
Bu d g e t
[ 0, ID
EC n] NEA Un i t Pri c e [ 0, 1]
Relation_1453 Relation_7687
[ 0, 1] EC Na m[ 0,en] Relation_1456
[ 0, n] [ 0, n]
RFSC Ac c o u n t i n g Bu d g e t Ch a rt o f Ac c o u n t s Hi s t o ry [ 0, n] Grid Ty p e
Relation_1454
Su rro g a te COA ID Bu d g e t Ch a rt o f Ac c o u n t s St a rt Da te
Da t e I D [ 0, n] [ 0, n]En d Da t e [ 0, n]
EC ID COA ID [ 0, 1] [ 0, 1] COA ID [ 0, n] [ 0, n] [ 0, 1]
Ac c o u n t Sta t u s [ 0, n]
De s c rip ti o n De s c rip ti o n Relation_7636 Da t e o f In c Relation_4780
Be g i n n i n g Ba l a n c e Relation_4860 Po we r A c c o u n t s
Bu d g e t Gro u p i n g Ac c o u n t Sta t u s ID Da t e o f Firs t En e rg e n
Co l le c t i o n Bu d g e t Gro u p i n g Rel[a0,
tio1]
n_207 Da t e I D [ 0, n] [ 0, n] [ 0, n]
[ 0, n] De s c rip ti o n M e m b e rs h i p Relation_1455
Ef fe c t iv it y Da t e Relation_5695
Tra n s fe r o f Fu n d s [ 0, 1] EC ID Relation_1451
St a rt Da te [ 0, n] PSP Cla s s if ic a ti o n
Relation_7635
I n te re s t I n c o m e [ 0, 1] De l in q u e n t Co n s u m e rs
Ac c o u n t Sta t u s ID
En d Da t e RSEC W R Cl a s s i fi c a ti o n
Ad j u s tm e n t s Va l u e Da t e I D
CDA Cla s s if ic a ti o n Ex p e n d it u re s
Di s b u rs e m e n t s EC ID
[ 0, 1] Da t e I D
[ 0, n] Relation_814[ 0, n] Cl a s s o f Se rv[ 0,i 1]
c e ID
Relation_3959 EC ID
Ac c o u n t No[ 0, 1]
Relation_3960 Ex p e n s e Ty p e I D
[ 0, n] Ac c o u n t Sta t u s
Ex p e n s e Va l u e
Ac c o u n t Na m e
Bu d g e t Pe rf St a t is t ic s [ 0, n] No o f Bi ll s
[ 0, n]
Da t e I D Pe n a l ty Cre d it o r Pro fi le Hi s to ry
EC ID [ 0, 1] Bi ll e d A m o u n t Su rro g a te Cre d it o r ID
Relation_1452
[ 0, 1]
Relation_733 Ac c o u n t Ty p e ID L o c a t io n
[ 0, De
1] t a i ls Cre d it o r I D
Relation_734 Cre d it o r Pro fi le
Bu d g e t [ 0, 1]
Cre d it o r Na m e
Ba ra n g a y ID [ 0, n] Cre d it o r I D
Ac t u a ls De s c rip ti o n
I n c o m e Cl a s s ID Am o rt iz a ti o n Du e Cre d it o r Na m e Relation_4830
Cre d it o r Ty p e
Di s tric t Da t e I D De s c rip ti o n
[R
0,ela1]tion_826 Relation_840 [ 0, n] Ef fe c t iv it y Da t e
Ci ty EC ID Cre d it o r Ty p e
L o c a t io n De t a i ls His t o ry EC Ge o g ra p h y
Pro v in c e Relation_1031 Relation_1457
[ 0, 1] Cre d it o r I D
[ 0, n]
Ba ra n g a y ID Re g i o n EC ID [ 0, 1]
[ 0,
Rel1]
ation_1030 Cre d it o r Na m e
Di s tric t Relati[o0,n_4798
1] I s la n d Gro u p
[ 0, 1] Ba ra n g a y ID
Am o u n t d u e
Ci ty [ 0, n] St a rt Da te L o a n Ty p e
L o a n Ty p e ID
Pro v in c e En d Da t e L o a n Ty p e ID
Re g i o n Su s c e p ti b il it y to Ty p h o o n [ 0, 1] [ 0, n]
L o a n Ty p e Na m e
I s la n d Gro u p Urb a n Ru ra l Cl a s s i fi c a t io n Relation_11634 De s c rip ti o n
Ef fe c t iv it y Da t e Po p u l a t io n St a rt Da te
Pe r Ca p it a I n c o m e En d Da t e

Table 4: Financial Performance Multi-Dimensional Analysis Matrix
Table
Income and Power Amor- BOD Budget Aggregated Top Prompt
Expen- Balance NGCP RFSC Top Delinquent
Expense Supplier tization Power Perf Financial Payor
ditures Sheet Billing Accounting Consumers
Breakdown Billing Due Accounts Statistics Measures Customers
Calendar x x x x x x x x x x x x
EC Profile x x x x x x x x x x x x
Location Details x x x x x x x x x x x x
Dimension
Class of Service Type x x x x x x x

Financial Chart of Accounts x x x
Budget Chart of Accounts x x x x
Creditor Profile x
Account Status x
Project Type x
Billing Determinant x x

3.2.4 Subject Area: Institutional Information
Figure 9: Institutional Information Data Model
L o c a t i o n De t a i l s
B a ra n g a y I D
I n c o m e Cl a s s I D
Di s t ri c t
E m p l o y e e M a s t e rl i s t B OD P ro f i l e Ci t y
S u m m a ry o f Co m p l a i n t s Relat ion_5720 P ro v i n c e
T IN T IN [ 0, 1]
Na m e Da t e I D E C Ge o g ra p h y Relat ion_1031 Re g i o n
Em p l o y m e n t T y p e L o c a t i o n De t a i l s Hi s t o ry
Po s i ti o n E C I D [ 0, 1] [ 0, n] I s l a n d Gro u p P a t ro n a g e Cre d i t Re f u n d
Po s i ti o n T y p e EC ID [ 0, n] Relat ion_4798 B a ra n g a y I D
Co m p l a i n t T y p e I D S t a rt Da t e Cre d i t Re l e a s e Da t e I D
Em p l o y m e n t Sta tu s Di s t ri c t B a ra n g a y I D [ 0, n] [ 0, 1] Di s t ri c t
Co n t a c t I n f o Co m p l a i n t S t a t u s R ela t o
i n_6102 E n d Da t e EC ID
E m p l o y e e Na m e Ci t [ 0, 1]
y
Co m p l a i n t Co u n t Rela[[t 0,
ion_1030
1] Su s c e p ti b i l i ty to T y p h o o n F o rm u l a
Da t e o f B i rt h Ca n d i d a t e i n t h e L a s t E l e c t i o n 0, n]
P ro v i n c e [ 0, 1]
E l e c t i o n P o s i t i o n Rela t o
i n_639 Re m a rk s E C P ro f i l e Urb a n Ru ra l Cl a s s i f i c a t i o n Re c i p i e n t Co u n t
E m p l o y e e Co n t a c t I n f o [ 0, n] Re g i o n
E C I D Po p u l a ti o n I n s t i t u t i o n a l M e a s u re T o ta l Am o u n t
Hi g h e s t L e v e l o f E d u cR[ela0, att1]
ioi n_6290
o Da t e o f L a s t P re c e d i n g E l e c t i o n
[ 0,nn] I s l a n d Gro u p
Da t e S t a rt [ 0, n] E C Na m e P e r Ca p i t a I n c o m e Da t e I D
De g re e Relat ion_6126 E f f e c t i v i t y Da t e
Hi re Da t e Da t e E n d B OD P o we r o f A c c o u[ n0, tn]s P a y a b l e Gri d T y p e EC L o c a ti o n ID Relat ion_6103
Relat ion_6008 Relat ion_6046
E n d Da t e T e rm o f Of f i c e (d e ri v e d ) Relat ion_641 Da t e I D S t a rt Da t e [ 0, n]
[ 0, 1]
E[ C0, n]Ra t i n g
Relat ion_6082 [ 0, n] [ 0, n] E C Cl a s s i f i c a t i o n I n c o m e Cl a s s i f i c a t i o n
E m p l o y e e Re a s o n f o r E n d No o f Y e a rs o f S e rv i c e EC L o c a ti o n ID E n d Da t e
[ 0, 1] [ 0, 1] [ 0, n] I n c o m e Cl a s s I D
P o s i t i o n Re m a rk s Go o d M o ra l Ch a r Do c u m e n t [ 0, 1] T IN Relat ion_5943 Da t e o f I n c Relat ion_1458 [ 0, n] B OD Ra t i n g
Relat ion_1462
[ 0, n] Cl a s s Na m e
Ra n k M e m b e r o f Go o d S t a n d i n g A c c o u n t [ 0, S 1]ta tu s Da t e o f F i rs t[ 0, E n]
n e rg e n GM Ra t i n g
[ 0, 1] De s c ri p t i o n
S a l a ry W i t h S p o u s e Ho l d i n g Hi g h e r E l e c t i v e Ac c o u n t Am o u n t M e m b e rs h i p [ 0, n]Relat ion_8889 E m p Rleloatyion_1459 e e Co u n t (De ri v e d )
T e rm i n a t e d f ro m P re v i o u s E m p l o y m e n t Ca s h A d v a n c e S t a t u s P S P Cl a s s i f i c a t i o n [ 0, n] M e m b e r Co n s u m e r Co u n t Da t e S t a rt
4 t h De g re e o f A f f i n i t y Co m p l a i n t T y p e Ca s h A d v a n c e A m o u n t RS E C W R Cl a s s i f i c a t i o n E s t i m a t e d A n n u a l Re t i re e s Da t e E n d
[ 0, 1] V o t e r' s T u rn o u t Co m p l a i n t T y p e I[ D 0, 1] Rela[t[0,
io0,n_4780
n] CDA Cl a s s i f i c a t i o n
1] E s t i m a t e d M o n t h l y Re t i re e s
[ 0, 1] Relat ion_6273 No o f V o t e rs Co m p l a i n t Na m e E C P ro f i l e Hi s t o ry Re t i re m e n t F u n d
De s c ri p t i o n [ 0, n] Fund M anager
F i n a n c i a l I n t e re s t Relat ion_5719 S u rro g a t e E C I D Ca l e n d a r Di m e n s i o n [ 0, 1] I n f o E d u c a t i o n Ca m p a i g n
[ 0, n] Da t e S t a rt EC ID [ 0, n] F u l l T i m e Eq u i v a l e n t
[ 0, 1] Ch a r Da t e I D Da t e I D
Da t e E n d E C Na m e [ 0, 1]
Relat ion_6274 [ 0, 1] Ca l e n [d0,an][r0,Da n] t e Relat ion_198
[ 0, 1] EC ID
Em p l o y m e n t Sta tu s Gri d T y p e
F u l l Na Rel
[ 0, n]
mat ioen_5761 Ca l e n d a r Da t e E C P ro g ra m
Em p l o y m e n t Sta tu s T y p e E f f e c t i v i t[y0, n] Da t e [ 0, n] Relat ion_5760
[ 0, n] Relat ion_5721
Da y Na m e M e d i a In fo
De s c ri p t i o n Da t e o f I n c B OD A c t i o n s S t a t u s A u d i t Ra t i n g
B OD A t t e n d a n c e S t a t Da y i n W e e k No B OD A c t i o n T y p e P ro g ra m S c h e d u l e
Da t e S t a rt Da t e o f F i rs t E n e rg e n [ 0, n] Da t e I D Co v e ra g e Da t e
Da t e I D Da y i n M o[ 0, n n]th Ac ti o n ID
E m p l o y m e n t Cl a s s i f i c a t i o n [ 0, n] Da t e E n d M e m b e rs h i p E C I D EC ID
[ 0, n] EC ID W e e k i n M o n t h No [ 0, 1] A c t i o n De s c ri p t i o n
E m p l o y m e n t Cl a s s T y p e Relat ion_642 P[o0,we 1] r S o u rc e [ 0, 1] [ 0, 1] Ac ti o n T y p e ID Au d i t T y p e
[ 0, 1] T IN W e e kRelai tnRioeln_1460 aY t ioen_1463
a r No Da t e S t a rt
De s c ri p t i o n Relat ion_6275 [ 0, n] Rel[a0,
t[ io0,
1] n]
n_667 Re p o rt P u b l i s h Da t e
M e e ti n g T y p e M o n t h Na m e Co u n t Da t e E n d [ 0, 1]
Da t e S t a rt [ 0, n] [ 0, n] Relat ion_666 A u d i t Ra t i n g
Da y s P re s e n t Relat ion_643 M o n t h No [ 0, n] [ 0, 1] Relat ion_6140
Da t e E n d Un i o n A s s o c i a t i o n L i s t Hi s t o ry E x i t Co n f e re n c e Da t e
[ 0, n] Da y s A b s e n t [ 0, 1][ 0, 1] Y e a r M o n t h[ 0, n] [ 0, n]
[ 0, n]
S a l a ry Ce i l i n g Un i o n I D M e e ti n g T y p e R ela t o
i n_6081
[ 0, n] M o n th Ag o [ 0, 1] A u d i t o r Na m e
R ela t o
i n_6141 [ 0, n]
S u rro g a t e Un i o n I D M e e ti n g ID Relat ion_640 Ye a r [ 0, n] Relat ion_202 A u d i t Cl a s s i f i c a t i o n
Un i o n A s s o c i a t i o n Na m e [ 0, 1] Co m p l i a n c e
De s c ri p t i o n Ye a r Ag o Cu s tRoelam e r S e rv i c e S t a n d a rd
t ion_5870
Affi l i a ti o n [ 0, n] Au d i t F i n d i n g s
Da t e S t a rt Qu a rt e r Cu s t o m e r S e rv i c e S t a t i s t i c s Cu s t o m e r S e rv i c e P a ra m e t e r I D
Da t e E s t a b l i s h e d Relat io[n_205
0, 1]
Da t e E n d Qu a rt e r A g o Da t e I D S t a n d a rd
A d d re s s [ 0, 1] Se a s o n EC ID [ 0, n]
[ 0, 1]
S t a rt Da t e
[ 0, n] Co n t a c t I n f o o f Un i o n P re s i d e n t F i s c a l S t a rt Co m p l i a n c e [ 0, 1] B A P A De t a i l s
E n d Da t e
E f f e c t i v i t y Da t e F i s c a l En d Da t e I D
[ 0, 1]
EC ID
[ 0, 1] B A P A Org a n i z e d Co u n t
Relat ion_5871
[ 0, n] A c c i d e n t De t a i l s Op e ra t i o n a l B A P A Co u n t
[ 0, 1] Un i o n A s s o c i a t i o n L i s t CB A [ 0, n] [ 0, 1]
A c c i d e n t Da t e M e m b e r Co u n t
Po s i ti o n T y p e Un i o n A s s o c i a t i o n I D Un i o n I D [ 0, 1] [ 0, n] Relat ion_6006 Relat ion_6005 E q u i p m e n t T y p e
[ 0, 1] [ 0, 1]
EC ID
Po s i ti o n T y p e ID Un i o n A s s o c i a t i o n Na m e [ 0, n] A g re e m e n t Da t e I D Relat ion_6007 Eq u i p m e n t ID
[ 0, n]
Ac c i d e n t T y p e ID [ 0, n]
De s c ri p t i o n Relat ion_5963 Affi l i a ti o n EC ID [ 0, 1] De s c ri p t i o n
Relat ion_5941 [ 0,[[0,
n]0,Rn]
el
n]at ion_5942 [ 0, n]
Eq u i p m e n t T y p e ID M SEAC o r Eq u i v a l e n t
Da t e S t a rt Da t e E s t a b l i s h e d A GM A Da t e S t a rt Da t e
[ 0, 1] [ 0, n] Em p l o y e e ID Da t e o f A p p o i n t m e n t
Da t e E n d A d d re s s E c o n o m i c B e n e f i t s [ 0, 1] E n d Da t e
Relat ion_7701 Ou t s o u rc e E m p l o y e e I n v o l v e d EC ID
Co n t a c t I n f o o f Un i o n P re s i d e n t Am o u n t [ 0, 1] M SEAC Se c to r
Relat ion_6313 Ac c i d e n t T y p e Co n s u m e r I n v o l v e d Se c to r ID
A c c i d e n t I D A c c i d e n t De s c ri p t i o n [ 0, 1]
B o a rd Re s o l u t i o n No Se c to r ID
Relat ion_5899
De s c ri p t i o n Da m a g e E x t e n t [ 0, 1] Na m e Rela[[t 0,
0, n]
1]
ion_5898 De s c ri p t i o n
L a b o r M g t Is s u e s Relat ion_5900 S t a rt Da t e
B o a rd Re s o l u t i o n s L a b o r Is s u e T y p e S t a rt Da t e Da m a g e Co s t T e rm o f Of f i c e
I s s u e F i l i n g Da t e I D Ac ti o n T a k e n E n d Da t e
EC ID Is s u e T y p e ID E n d Da t e [ 0, 1]
CS R Ac ti v i ty T a k e n
B y L a ws A m e n d m e n t EC ID
Re s o l u t i o n No De s c ri p t i o n Da t e I D A p p ro v e d p e r Di e m s
S u b m i s s i o n Da Is s u e T y p e ID
Re s o l u t i o n Da t e [ 0, t1]e I D Da t e S t a rt Relat ion_7565 F e d e ra t e d (De ri v e d )
Da t e A p p ro v a l I D 0, n] Co n c e rn De s c ri p t i o n Relat ion_7566 EC ID
Re s o l u t i o n T i t l e Da t e E n d R[el0,
at 1]
io[n_6080
EC ID [ 0, n] [ 0, 1] Sta tu s CS R P ro j e c t T y p e CS R P ro j e c t T y p e
NE A A c t i o n [ 0, n] [ 0, 1] Relat ion_6125 [ 0, 1]
B o a rd Re s o l u t i o n No
B o a rd Re s o[ l0,u[n]0, t i 1]
o n No Re m a rk s RRelelaattioion_6045 CS R T y p e I D
Re s o l u t i o n Cl a s s i f i c a t i o n 1 Relat ion_7568 n_7567
[ 0, n] P ro j e c t Na m e Ca p a c i t y B u i l d i n g
A GM A Re s o l u t i o n P ro j e c t T y p e
Re s o l u t i o n Cl a s s i f i c a t i o n 2 Relat ion_7564 S e m i n a r Da t e I D
Re s o l u t i o n Cl a s s i f i c a t i o n 3
A p p ro v a l S t a t u s P ro j e c t De s c ri p t i oRelnat ion_6044 P ro j e c t De s c ri p t i o n EC ID
Relelaattioion_6213
n_6214 [ 0, 1] [ 0, 1] S t a rt Da t e
[ 0, 1]
[ 0, 1] B e n e f i c i a ry Co u n t
Re s o l u t i o n Re m a rk s R P a rt i c i p a n t E m p I D
Relat ion_7702 P ro j e c t Co s t
E n d Da t e T ra i n i n g Na m e
E I CP M a p p ro v e d
Da m a g e E x t e n t S p o n s o ri n g A g e n c y
Da m a g e Co s t
Ac ti o n T a k e n

Table 5: Institutional Information Multi-Dimensional Matrix
Table
BOD
BOD Board Customer By-Laws Info Patronage
Institutional Employee Power of Summary of Labor Mgt Accident Audit Capacity MSEAC or BAPA
Attendance Resol Service CBA Amendm Education CSR Credit /
Measures Masterlist* Accounts Complaints Issues Details Rating Building Equivalent Details
Stat utions Statistics ent Campaign Refund
Payable
Calendar x x x x x x x x x x x x x x x x x
EC Profile x x x x x x x x x x x x x x x x x
Location Details x x x x x x x x x x x x x x x x x
Employee Masterlist* x x x x
Employee Position Type x
Dimension
Employee Status x
BOD Profile x x x x x x
BOD Meeting Type x
Complaint Type x x x
Board Resolution Classification x x x x
Labor Issue Type x
Accident Type x
Equipment Type x
*Both a dimension and a table

3.2.5 Subject Area: Project Statistics
Figure 10: Project Statistics Data Model
P roject Completion Status
Funding A llocation Details P roject Status ID

Description
[ 0,1] Date Rel ati on_250 P roject Energization Status P roject Impact Type
Calendar Dimension S tart Date [ 0,1]
E C ID [ 0,1] Date Impact Type Id
Char Date ID E nd Date [ 0,n]
Funding S ource E C ID Impact Type
Target Rel ati on_1465 Calendar Date
[ 0,1] P roject Status ID S tart Date
Rel ati on_894 Full Name Calendar Date
Funding Requirement S itio Count E nd Date
P roject Funding Source Day Name A mount
Rel ati on_895
Day in Week No
Rel ati on_4881
[ 0,n] S ource ID
[ 0,n] Day in Month
Description
Week in Month No [ 0,1] [ 0,n]
P roject Accomplishment
Week in Year No
Date Month Name
[ 0,n] [ 0,n] Rel ati on_240
E C Location Month No [ 0,1]
[ 0,n] [ 0,1]
Funding S ource Y ear Month Rel ati on_4009
Target Project Cost [ 0,n] Month Ago
[ 0,1] Date Released Y ear P rojected Energization Coverage
[ 0,n] B idding S chedule Y ear Ago Date ID
[ 0,1] Date Awarded [ 0,1]
Rel ati on_879
Rel ati on_1464
Rel ati on_880 Quarter E C ID
Construction S tart Rel ati on_11610 Quarter Ago Grid Type ID
Date Completed [ 0,1]
S eason P roject ID
P roject Funding Source History Date Energized [ 0,n] [ 0,n]
Rel ati on_11612
[ 0,1] Fiscal Start P roject Status ID P roject Masterlist
S urrogate Source ID Initial HHC Fiscal End Count of Barangays
Final Inspection P roject ID
S ource ID Count of Households
Remarks
[ 0,n] P roject Type ID
Description No of S itios Impact Type ID
E ffectivity Date [ 0,n]
[ 0,n]
Rel ati on_1466
P roject Description
[ 0,1]
[ 0,n] P lanned Start
[ 0,n]
[ 0,1] P lanned End
Rel ati on_3984 [ 0,1] [ 0,1]
Rel ati on_3985 Rel ati on_11611 P articulars Value
P articulars UOM
E C Profile Location Details
Funding S ource ID
E C ID B arangay ID
E C Profile History P roject Budget
E C Name Income Class ID Location Details History
S urrogate EC ID A ctual P roject Cost
Grid Type District B arangay ID CAP EX nonCAP EX Classification
E C ID S tart Date City District
E C Name Rel[ 0,1]
ati on_4780 E nd Date E C Geography
Rel ati[ 0,1]
on_1030 P rovince
Grid Type Rel ati on_1031
[ 0,n] on_4798 City
Rel ati[ 0,n]
[ 0,n] Date of Inc [ 0,n] E C ID Region
E ffectivity Date [ 0,1]
P rovince
Date of First Energen B arangay ID Island Group [ 0,1]
Date of Inc Region
Membership S tart Date
Date of First Energen Island Group
P SP Classification E nd Date
Membership E ffectivity Date
RSE C WR Classification S usceptibility to Typhoon
P ower S ource CDA Classification Urban Rural Classification
P opulation
P er Capita Income

Table 6: Project Statistics Multi-Dimensional Matrix
Table
Funding Project
Project Project
Allocation Energization Price Index
Masterlist Accomplishment
Details Coverage
Calendar x x x x x
EC Profile x x x x x
Dimension
Location Details x x x x x
Project Type x x
Project Funding Source x x x x
Project Impact Type x
Project Completion Status x x x x

3.2.6 Report to Data Model Mapping
The Report to Data Model Mapping aims to present how each of the key outputs (reports and dashboards)
are mapped against the Subject Areas. This mapping also checks completeness of the Data Model to be
able to provide the required data to generate the reports and dashboards.
Table 7: Report to Data Model Mapping

SUBJECT AREA
PROJECT
ORGANIZATIONAL FINANCIAL ENERGY SYSTEM
FINANCIAL
INFORMATION PERFORMANCE SALES PERFORMANCE
STATISTICS
REPORT
Budget Performance
Chronicle Data
BLEP Subsidy
SEP Subsidy
Unbundled Rates
Fact Sheet
Financial and
Statistical Data
KM of Lines
Power Market Report
Sales Revenue
Program Status &
Accomplishments
Status of Energization
Status of Projects
Substation Report
System Reliability
QCR
PSMR
MER
MIR
MFSR
9
BI ANALYSIS
01-01 Analysis of
impact on system loss
01-02 Analysis of
impact of change in
engineering design to
system loss
01-03 Analysis of
impact on OPEX
01-04 Analysis of
impact on collection
efficiency
01-05 Assessment of
EC’s risk rating for
ERC’s risk-based
CAPEX approval
process
01-06 Monitoring of
projects
01-07 Other CAPEX
Planning Data Analysis
9
For details on the BI Analysis items, see Discovery Report Section 5.1 Recommendations on Effectiveness

01-08 Analysis of
sitio/household growth
for electrification
program planning
01-09 NEA Price Index
01-10 Groupings and
parameters
02-01 Analysis of Tariff
Sufficiency
02-02 Support for
Castalia' ongoing study
of RSEC-WR
02-03 OPEX
Monitoring
02-04 Policy-alignment
of the Budget
02-05 Calculation of
one month working
capital
02-06 Assessment of
EC financial standing
based on working
capital
02-07 Analysis of EC
payables
02-08 Analysis of
amortization schedule
02-09 Analysis of ECs
for approval of loan
application
02-10 Analysis of Asset
Value
02-11 Additional
analysis options for
collection efficiency
02-12 Comparison of
collection efficiency
with other performance
indicators
02-13 Analysis of Sales
02-14 Analysis of
Profitability
03-01 Monitoring of
system loss trend per
EC
03-02 System loss data
10
per feeder
03-03 System loss
trend compared with
granular data trend
03-04 Monitoring of
system loss % change
per EC
10
On inquiries with NEA and ECs, data on input and output (kWh) per feeder, consequently, system loss data per feeder, will be difficult
for some ECs to provide. Given this, it is recommended to do a phased implementation wherein the first phase will include
implementing the system (data architecture, system configurations including formula and dashboards displaying system loss data per
feeder) that can accommodate the per feeder data. However, the data entry template and the Web Portal will not require the per
feeder data. At the end of this phase, any report or dashboard supposed to display system loss per feeder is implemented but will not
show any figures due to lack of data. At a later phase, when all the ECs are ready to provide the per feeder data, the change will be
limited to a revision in the data entry template and data validations to be done by the Web Portal; no changes required in the data
architecture, formula and dashboards.

03-05, 03-06
Comparison of system
loss with other
measures that
commonly affect
fluctuations
03-07 Segregated
system loss analysis
03-07 Comparison of
system loss with profit
margins
03-09 Review of
common PGC and
PDC codes not or
partially complied with
03-10 Comparison of
system loss with tariff
to detect possible
consumer behavior
pattern
03-11 Comparison of
reliability indicators
with other measures
04-01 BI support in
KPS/KPGS rating
analysis
05-01 Analysis of
customer-employee
ratio with consideration
of FTE and cost aside
from number of
employees
05-02 BI support in EC
audit
05-03 Use of data for
validation of policy
compliance
05-04 Analysis of
impact of new policies
05-05 Analysis of
complaints reported
by ECs
05-06 Statistical
analysis for
performance
monitoring of EC
Management and BOD
05-07 Most Delinquent
Customers
06-01 Security of
Power Supply
06-02 Aggregation
Potential
06-03 Savings on
WESM Purchases
07-01, 07-02 Detection
of early signs of
defaults or
deteriorating EC
performance
07-03 Quarterly
Performance Color
Coded Classification
07-04 Deployment of
PS

3.3 Key Outputs
For key outputs, the NEA IT System, at the minimum, should be able to generate all of the existing reports
included in the reportorial requirements, those required by other agencies as well as those shared with the
public.
Highlighting that the primary objective of NEA is to enable ECs to achieve Total Electrification and
strengthen its sustainability through financial viability and technical proficiency, mainly through policies,
programs and performance monitoring, NEA should be able to effectively analyze information. To strengthen
NEA’s analysis capabilities, the NEA IT System should be able to generate dashboards displaying the BI
Analysis items identified in the Discovery Phase. These dashboards will enable NEA to perform analysis of
trends, with a portfolio view of all ECs or groups of ECs, rather than on an individual basis, dynamic
information (non-static, unlike reports) to facilitate ease of investigation and comparison across multiple sets
of information. The dashboards should also be intuitive so that users may be able to build and test their own
measures and performance metrics in the form of charts, graphs and other graphics most effective in
representing information and trends.
Below are the sample output dashboards recommended for NEA:
Figure 11: Sample Output Dashboard 1

Figure 13 shows a pop-out window after clicking the Collection Efficiency bar in Figure 12 to show a similar
bar graph but considering only the ECs (34% out of the 120) that did not meet the Collection Efficiency
performance indicator, and out of that statistic, what percentage of those ECs did not meet other
performance indicators.

The above dashboards are composed of measures currently monitored by NEA and the BI Analysis items
identified in the Discovery Report. All data required to generate these dashboards are incorporated in the
Data Model, Data Dictionary, as well as the Data Entry templates. It must be noted that the dashboards and
its figures are samples and are for illustration purposes only. It is expected that the system implementor will
further elaborate on the complete list of dashboards needed as part of their detailed technical specification.

3.4 Data Dictionary
11
A data dictionary describes the business content of all columns and tables across the data warehouse . It is
a repository of information about data such as its description or meaning, relationship with other data,
formula (if it is derived) and format.
This serves as the single reference for data definitions – one term one meaning – across organizations/users
and systems accessing, updating, using and analyzing the data. This is one of the elements to ensure high
data quality entered and maintained in the system.
The proposed Data Dictionary for the NEA IT system is structured in this manner:
Element Description
Term The name of the term such as “Class of Service” or “System Loss”
Description, Business The description of the term, any business rules related to the term, the formula
Rules, Formula, Source if the term is to be derived from other data in the system, and other relevant
information to provide context to the term. The source of the definition,
business rules or formula is also included. For example, “Memo 2011-016” or
“RA 9136 Section 34”
Technical Specifications
of the Term
Data Format The format of the term if it is alphanumeric, numeric, date (mm/dd/yyyy or
mm/yyyy) or time.
Dimension/ A data classification if the term is a dimension, a measure or an attribute.
Attribute/
Measure  Dimensions give meaning to an occurrence or transaction. For NEA,
dimensions include “Class of Service” (Residential, Commercial,
Industrial and so on) and “Loan Status” (Current, Restructured, In
Arrears). Dimensions may have a hierarchy: for example, Geography
(Island Group, then Regions, then Provinces and so on)
 Attributes give additional meaning to a dimension. By itself, an attribute
will not provide much information. It needs to be associated with a
dimension to have effective meaning. For NEA, attributes include
“Count of Connections” which may be associated with dimensions
Class of Service or Geography or both. Another example of an
attribute is “Start Date: which can be associated with dimensions
“Employees”, “Interruption” or “Project”.

12
Measures are transactional or operational occurrences that are
quantitative in nature. For NEA, measures include “Input Energy” and
“Average Annual Growth Rate”.
Origin An indication on how the data is entered into the system:

 Entered - manually entered (in free text or with a defined format).
Examples include Technical Loss or Billing Period Start Date.
 Defined - selected from a defined list of values. Examples include
Interruption Cause Code and RSEC-WR Classification.
 Calculated – or derived data based on formula and other rules.
Examples include System Loss and Sales per Connection.
List of Values This is applicable only for terms with origin “Defined”. These are the list of
values available to be selected to provide data related to the term.
See proposed Data Dictionary in Annex 6.2.
11
Kimball, Ralph, Margy Ross, Warren Thornthwaite, Joy Mundy, Bob Becker. The Data Warehouse Lifecycle Toolkit. John Wiley &
Sons, 2008.
12
Measures elicited during interviews with NEA and ECs such as Power Sales per Connection have been included in the Data
Dictionary. Measures to support recommended BI Analysis are also included in the Data Dictionary.

Data Dictionary Alignment, Maintenance and Accessibility
It should be considered for this data dictionary to be aligned with data dictionaries of other government
agencies, especially those related to energy.
If there will be new systems that will access the Database/BI system or if the latter will use other systems as
a data source, data dictionaries of these systems should be aligned to ensure consistencies of data.
A Dictionary is a living document and should be continuously maintained following the Data Governance
Framework. The unit responsible for its maintenance is the Data Governance Team composed of Data
13
Owner and Data Custodian . Changes to the Data Dictionary (such as the terms, definition and formula)
may be triggered by new or revised regulations and policies and changes in business requirements.
New measures may also be added to support refined and enhanced analysis of existing information,
monitoring of new regulations, policies and programs, new indicators (such as new KPGS) and other early
warning indicators for declining performance. Should new measures require additional data, this should also
entail changes in the Data Dictionary following the defined Data Governance Framework.
At the minimum, the following elements shall be defined during the Implementation Phase:
 For Terms with Origin “Entered”, the number of characters to be accepted by the system should be
defined
 For Terms with Data Format “Numeric” and “Percentage”, the number of decimal numbers should be
defined.
To ensure ease of accessibility of the definition of terms, it is recommended to make the Data Dictionary
(selected elements such as the term, description/formula at the minimum) published at the Web Portal.
3.5 Data Governance
Data Governance is the “organizational bodies, rules, decision rights, and accountabilities of people and
14
information systems as they perform information-related processes” . This involves establishing a set of
policies and procedures aimed at ensuring the integrity of data stored in the database to manage end-to-end
data quality. Data Governance is important especially for organizations implementing enterprise-wide
information systems such as a BI System, primarily because data will be coming from different sources,
centrally stored in an integrated database system, and consumed/used by different personnel internal and
external to the organization. Data Governance is important as it will ensure that controls are in place to
maintain the quality of data used by the data consumers.
This section will discuss the data governance processes necessary to maintain data integrity at NEA when
the NEA IT System is implemented.
3.5.1 Data Maintenance Process

Information systems such as the BI System and web portal facilitate the management of data in terms of
collection, storage and usage. They also serve as tools for keeping the integrity of the data. However,
maintaining data integrity cannot be ensured by merely implementing an information system; rather, this
must be complemented by corresponding data management processes. For the implementation of the NEA
IT System, it is important to establish and implement the following data maintenance processes:
Table 8: Data Maintenance Process Flows

Process Description
Data Maintenance Process for changing the data model, templates, master data and data
configuration due to changes triggered by events such as new or
updated policies or regulations and new BI analysis opportunities
13
Described in Section 3.5.2.
14
As defined by The Data Governance Institute

Process Description
Master Data Maintenance Process for changing (add, modify, delete) the list of valid values for
certain data entities (e.g. substation, employees, BOD, etc.) that will be
used to verify the data entered in templates and/or uploading of
uploaded in the system
Template Maintenance Process for updating the templates used by the ECs in entering
reportorial data for upload into the system
Data Upload – Standard Process for uploading accomplished reports (e.g. equivalent reports for
MFSR, MER, MIR, audit findings) to the system on a periodic basis
under normal circumstances.
Data Upload – Special Handling Process for uploading reports to the system that could not be
performed through the “Data Upload (Standard)” process due to special
circumstances (e.g. unreliable internet connection in the EC’s area,
template has not been completed/uploaded in time for the defined
report submission cut-off date, system in unavailable, data errors that
require investigation by the Data Governance Team, etc.)
NEA Data Approval Process for approving the data content uploaded either through “Data
Upload (Standard)” or “Data Upload (Special Handling)” process to
ensure high quality of data to be stored into the database. This is an
optional process which will have to be agreed upon during the system
implementation phase.
Data Warehouse Processing Batch processes that perform ETL of approved data, storage of data
into the database as well as generate reports and dashboards.
These processes are typically defined by the system implementor as part of the detailed functional/technical
specification phase. However, for the purpose of illustrating what these processes contain, sample data
maintenance processes (as specified above) which are relevant to the BI System are shown in Annex 6.3.
This can serve as the basis for the processes which can be refined and progressively elaborated by the
system implementor during the implementation phase
3.5.2 Data Owner and Custodian
As part of Data Governance, organizations accountable for data integrity have to be defined. In particular,
Data Owners (sometimes referred to as Data Stewards) and Data Custodians have to be designated for the
sets of EC-related data collected and stored by NEA.
Data Owners are resources responsible for the content, context and business rules regarding data. They are
responsible for the data stored in a data field. As such, data owners should have the knowledge,
responsibility and authority to describe, establish and enforce business rules pertaining to the data. In
summary, the main responsibilities of the data owners include:
 Establishment of business rules pertinent to data
 Definition of business requirements and context that will serve as input to the definition of the Data
Architecture (i.e. data model, data dictionary)
 Determination of access rights for data within their ownership
 Decision on the quality of data stored in the database
On the other hand, Data Custodians are responsible for the maintenance, transfer, and storage of data. They
are responsible for the fields that store the data, the information systems that manage the data, and the
implementation of business rules pertaining to data management. Thus, the main responsibilities of the data
custodian include:

 Maintenance of Data Architecture (i.e. data model and data dictionary) in consultation and validation
with the Data Owners
 Enforcement of information security policies to secure data access and to secure the data stored in
the database
 Enforcement of processes and system rules for the creation and management of data created by the
processes and information systems.
The data models discussed in Section 3.2 list the data needed by NEA. The Data Owners for Financial data
such as expenditures, power supplier billing, amortization due, etc. could be those from the Financial
Services and/or Accounts Management and Guarantee Departments. The Data Owners for Technical,
Institutional and Project data could be from the ED, IDD and Corplan, respectively. It should be noted that it
is not necessary that an entire subject area should be assigned to a single department for Data Ownership. It
may be more effective for some data within a subject area to be assigned to personnel from another
department.
These roles are recommended to be permanently upheld by NEA to ensure that there are persons assigned
to ensure data alignment and integrity at all times. This is not a full time assignment and tasks related to data
governance are not expected to occur all day, 5 days a week. Rather, it is an additional responsibility that
could be assigned to a person or group of persons (Data Governance Team) over a period of time then
transferred to others of the same subject matter expertise, as necessary.
3.6 Historical Data

Figure 16: Historical Data Upload
In using a new BI system, the presence of some historical data is preferred as it will allow users to perform
historical and trend analysis immediately upon implementation. It is ideal to have this completed prior to BI
Implementation. However, this should not be treated as a pre-requisite to system implementation especially
if schedule slips due to data conversion of historical record or due to unavailability of quality historical
records. The BI System will still operate without historical record and will still provide some BI analysis
particularly those that compare ECs using data within the current period, but trends and analysis based on
historical data will not be possible.
Important factors in preparing historical data are:
(1) The "cleanliness" of data, which refers to the uniformity in the format of data (i.e., number of decimal
places, character length, etc.) and its completeness such that all fields in the destination system will be
populated and not left blank.
(2) A decision on how much historical data could be made available and in encoded in the system. Note that
a minimum of a year's worth of data would be sufficient when viewing data on a monthly level of detail. Older
data could be considered though five years of data may entail too much manpower to retrieve, cleanse and
encode all 120 ECs' monthly data.

(3) Consistency in the business logic and rules for transforming data from its legacy or manual sources,
should it be needed prior to encoding in the templates (i.e., particular calculations like the removal of VAT
from revenue amounts). There should also be a set of processes and procedures for handling data to ensure
its consistent quality regardless of being from various sources (the ECs) and for data to be ready within a set
schedule aligned with the implementation timeline.
(4) The existence of a Data Dictionary which contains data definitions and formulas to ensure the common
understanding of data among users. This is discussed in Section 3.4.
For the historical data upload, it is necessary to create a data team from NEA to be responsible for planning
and preparing the procedures for making the historical data available to be loaded into the system. The data
team shall collect historical data from its files/archives, perform the necessary data cleansing and data
quality validation, and encode them in structured templates to enter the data into the system. Then a batch
process could be executed to upload the cleansed data in populated templates to the system.
3.7 Data Retention and Archiving

Through time, as more and more data is stored in the system, old data will have to be transferred to make
room for new data as they are continuously expected to grow. This makes the development of a data
retention plan necessary to an organization. A data retention plan contains the rules, policies and procedures
on what data should be kept and how. Recent data is typically considered relevant and maintained in the
system where it can be easily accessed. What needs to be initially defined is the set of criteria for data to be
removed from the easily accessible database. Usually, this would be data from several years ago or data
that is no longer applicable due to a regulation or law that has since been modified. From the identification of
such data, further guidelines are needed to determine what to do with the data. The most extreme option is
disposal. However, should the organization need its data in the future, the safe option is archiving.
Data Archiving is the process of removing selected data records from operational databases that are not
expected to be referenced again and storing them in an archive data store where they can be retrieved if
needed. Different systems may have various built-in archiving functionalities that produce archive files to free
up the system's main database and optimize system performance.
In archiving, it is recommended for a file to be generated in a standard format (i.e., comma separated values)
that can be read by numerous standard tools (i.e., MS Excel, MS SQL, database tools, etc.) and not
necessarily specific BI tools and technology. This could be from the system's database, if the standard
archiving process of the system produces a file in proprietary format. This way, should the archived data be
needed for viewing and analysis, the archive files could be easily retrieved and viewed using the available
technology. On the other hand, if proprietary formats are preferred for archiving, it must be noted that such
files may need conversion prior to viewing using systems other than where it originated. Other things to
consider in data retention and archiving are:
 Which data to archive? Sample retention guidelines:
o Data from the past 3 years are maintained in monthly granularity in the main database
o Data from 3 to 5 years ago will be maintained in quarterly granularity in the main
database. Monthly data corresponding to this will be archived.
o Data from 5 to 10 years and over are maintained in annual granularity in main database;
Monthly and quarterly data corresponding to this will be archived.
 What file types to maintain? (word documents, PDF files, images)
 How long to keep archive files?
 What granularity of data to store for archive or if data should be aggregated? (i.e., for data over
20 years old, maintain annual, semestral and quarterly values but dispose monthly)
Storage options for archived files are the same as typical databases such that both physical and cloud
storage are applicable.

4 Application and Technology Architecture
Figure 17: IT Design for NEA
4.1 Application Architecture

This application architecture is focused on providing BI technology for NEA to use in reaping the benefits of
having a wealth of data from the ECs' reportorial submissions. This technology, often used in decision-
making and planning, is identified as the key to further enhancing NEA's capabilities to support the ECs and
meet its mandate through deep-dive analysis. This system will also be the centralized source of regularly
15
required reports from ECs and NEA and of information for external agencies and the public . The BI system
designed for NEA is composed of three (3) components: (1) Export, Transform, Load (ETL), (2) a Data
Warehouse and (3) Data Visualization Tools.
In the Discovery Report, a BI technology component called a Data Collection System (DCS) was identified
for data upload, sorting and filtering of data in a systematic way before storage. In the Design Phase, it was
realized that the more appropriate tool is a web portal that can serve the need to collect data, provide simple
reports on submission statistics and more importantly, house an automated validated process to ensure data
quality. As a system in itself, the web portal will have a database where raw data will be stored prior to its
processing in the BI system for analysis and reporting. This database will serve as the initial source of
validated and approved data of the BI system. In addition, this database can also contain other data not
necessarily for BI analysis as well as attachments to reportorial submissions typically used as reference in
validating submitted data such as power bills, board resolutions and other relevant documents.
The eICPM, an MS Excel-based tool used by the ECs to present their forecasts and planned projects, will
not be replaced by any of the applications in this report as its main function is word processing to transform
content into different report formats (i.e., Work Plan, DDP, CAPEX Plan, etc.). Such word processing is not a
function of BI or the data collection system (web portal). The ideal technology solution to replace the eICPM
tool is a customized application system (i.e., project monitoring application) that will also facilitate project
planning and monitoring, which NEA could consider as a future initiative specific to expanding their
15
To avoid duplication, the BI system's output may be published or made public through the NEA Website.

application portfolio. In the interim, the existing eICPM is very well capable of presenting and providing the
data (by data upload through the web portal) necessary for analysis in the BI system.
Further detail on the design of the BI system and web portal are presented in the sections below.
4.1.1 Business Intelligence (BI)

BI is a set of tools and techniques that facilitates the transformation of voluminous raw data into relevant and
useful information. Within organizations, it is typically coupled with the establishment of a Data Warehouse
environment which promotes the coordinated, architected and periodic process of managing data from
various sources into a repository that is optimized for analytical and informational processing.
The logical architecture of the BI System depicting integration between the Data Warehouse and BI
environments is presented in the diagram below.
Figure 18: BI System Components
BI Technology Components
Data Business
Warehouse Intelligence
Layer
Relational • Database access
Database • Audit user activities
• Secure and Control
Reporting & Analytics

Metadata • Standard/Template
Submitted Reports
• Predictive Models
Data • Historical Data
Data Model and Analysis
Integration
• Custom search and
filters
• Charts, Graphs &
other Analytics
ETL
Integration
Metadata
Extract,
Data Entry Analyze, Publish &
Transform Query & Mine
Web Portal Share
& Load
The diagram presents three (3) major components. The first component is the data integration layer, also
known as the ETL component. As the first layer, it is responsible for the collection of raw data. The data
then undergoes a transformation process (i.e., calculations, string manipulation, setting of default values,
logical operations, merging of data sets etc.) through the application of business rules to make the data fit for
end user consumption. The processed data is loaded and stored into the data warehouse.
The Data Warehouse is the second major component. It is at this layer where data is organized according to
a data model that promotes a complete and unified view of consolidated data based on the reporting and
analytical requirements of the organization.
To fully realize the benefit of the Data Warehouse, it is necessary to implement the third component of the
system – which is BI. This layer is designed to be the user-interfacing layer composed of tools and functions
to facilitate data analysis, simulations, visualization and reports preparation. Through these tools, users can
create and view various graphs, charts, perform geographical analysis, etc. The output from this layer is
what can be published and distributed to an organization's stakeholders.
4.1.1.1 Functional Requirements

Presented below are the functional requirements specific to the ETL and BI layers that are deemed to be
fundamental to a BI System.

Table 9: BI System Functional Requirements
BI System Component
Functionality
/ Capability
ETL Layer
Flexibility The design of the ETL processes must be flexible to handle change in business
rules, data source connections, new data elements, report requirements, new
formats of source files, additional aggregation details, etc.
All pre-built transformations can be configured to allow organization specific
conditions.
Capacity ETL must be able to apply both bulk and incremental data updates.
Scheduling The ETL jobs can be scheduled based on availability of data sources or other
conditions/events.
Monitoring The ETL tool must have an intuitive interface to monitor the execution of the
jobs from which logs can be accessed and from which jobs can be restarted at
certain checkpoints.
Business Intelligence Layer
System Capabilities
Reporting Enables the creation of formatted and interactive reports.
 Interactive reporting enables users to create, display and save prompts
that filter the data and the layout of the report;
 Formatted reports are familiar and easy to use;
Allows offline mode for users with limited internet access; Allows for navigation
and search of information in the report and serves as a repository of reports.
Allows versioning of reports.
Dashboards End users must be able to build their own performance metrics in the form of
charts, graphs, buttons and other graphics.
Ad Hoc Query Enables the users to enter and execute a query for retrieving information,
calculations and filters in a business-friendly universal layer, without the need for
programming.
Online Analytical Allows end users to analyze data with extremely fast query and calculation
Processing (OLAP) performance; Can perform sophisticated sorting/ranking, alternate hierarchies,
calculations and drill down on measures.
Visualization Tools Allows numerous aspects of data to be displayed more efficiently by using
interactive pictures, graphs and charts.
User Experience User-friendly intuitive interface that is easy to navigate and explore.
System Features
Web Portal Access Ability to publish and organize the BI objects into a web-based interface.
Connectivity with other Capability to integrate with different data sources such as Relational Databases,
databases OLAP Data Sources and Flat Files.
Scheduling Automatic update of reports and dashboards to reflect changes to metrics based
on schedules and/or events, new data.

Distribution Automated and scheduled distribution of reports in various formats through
different channels. (i.e., email, web publishing)
Offline Support Allows offline usage for end users who have none or limited internet access.
Mobility Can deploy reports and dashboards through mobile devices. (i.e., mobile
phones, tablets)
Administration Features
BI Infrastructure Can deploy all BI functionalities from a single installation with emphasis on
common security, metadata, administration, integration, data model, query
engine and interface.
Metadata Management Can accommodate various types of BI metadata, including author, dates, etc.;
Includes the feature to search and the ability to promote and reuse metadata
across different users, developers and application types for coherence in data
identification.
Logs changes to metadata including user involved, time and date of change,
etc.
Security Can secure and control access to data, the different BI objects and the modules
of the BI application.
Logs changes to security settings including user involved, time and date of
change, etc.
Auditing Can assign and track events or tasks performed by the systems and/or users
and administrators.
The user perspective of having these functional requirements is presented in Annexes 6.4 and 6.5 through
use case diagrams and user stories.

4.1.1.2 Solution Options
BI is a mature software class, and is readily available off-the-shelf from several software vendors. Unlike
transactional systems, where transaction details such as order and number of steps in a process vary, BI
systems are straightforward such that it is exclusive for reporting and analysis. Thus, when it comes to
implementing, rather than identifying how, the decision to be made is on which solution is best suitable to an
organization.
Generally, there are commercial software products and there are open source software products. Open
source typically connotes investing less on a product though maintenance fees could sometimes be required
similar to commercial products. However, vendors are able to package their offerings to meet a client
organization's needs and budget, even with commercial software, giving the different solutions equal footing
in the competitive market.
Table 10: Commercial vs. Open Source

Commercial Open Source
 Tried and tested reliable solutions usually  The investment may be limited to support and
with a global-wide reach. documentation since there are no software

Advantages
Pool of service providers available for license costs.

implementation, training and maintenance  Solution is always improving due to frequent
support needs. software upgrades for additional features and
 Generally regarded as more stable than open bug fixes.
source with functions having been tested  Should an organization have unique needs, the
rigorously. solution can be customized to meet special
requirements.
 Up-front and maintenance costs are generally  Many open source vendors charge for other
higher. features such as support services, access to
 Due to a huge client base, there may be codes that have been enhanced for specific
competition for support availability. requirements, and extensions.
 Need for skilled developers and staff to
implement and maintain the system.
 Generally, their user interfaces are less
appealing to business users, hence will get
less buy-in from the users.
Disadvantages
 Software companies that develop open source

applications are smaller in scale, raising
concerns on their application roadmap and
sustainability of their software products. There
is uncertainty on the future of these
applications as their development may be
discontinued, or their company may be
acquired by larger software companies.
 Less available consultants for implementation
and support.
 Externally developed modules, features and
extensions may not be rigorously tested.
 Typical concern for open source applications is
their lack of accurate and updated functional
and technical documentation.

Among the commercial products, BI solutions can be categorized into - "Best of Breed" and "End-to-End":
(1) Best of Breed Solutions are those that focus and specialize on a particular BI function or tool. It is due to
this specialization that such expertise is developed in handling varied organization scenarios. Such solutions
are recommended for technologically mature organizations with a robust IT landscape in need of BI solutions
to handle extreme situations and handle global-scale data.
(2) End-to-End Solutions are inclusive of all BI functions, guaranteeing seamless integration between BI
functions. This is recommended for organizations with defined fundamental BI solution needs that may or
may not have transactional systems from which the BI solutions will integrate.
To further distinguish each category, advantages and disadvantages for each are summarized in the table
below.
Table 11: Best of Breed vs. End-to-End

Best of Breed End-to-End
 Focused research and development of  Completeness of vision.

specific products, resulting in superior  The organization gets to deal with a single
Advantages
and exceptional performance and richer software vendor for support and issues resolution.
functionalities available for each BI  They generally tend to have overall lower software
component. license costs as the vendors are able to offer
 Not tied to an enterprise application packaged solutions containing multiple products.
stack.  System interfaces are well thought out in the
design.
 Separate brand solutions per BI  Product development may not be as robust and
component results in separate support aggressive as independent providers as overall
and maintenance skills required. company spending is distributed across other
 May need several vendors for support. offerings (i.e. ERP, CRM software).
 Total software license costs generally
Disadvantages
tend to be more expensive as they

provide richer features and functionality
for every BI component.
 IT will require additional technical training
to be able to perform system
administration functions. These trainings
may include different operating systems,
databases, servers, and programming
languages.
 More complex IT maintenance, especially
if there are software upgrades.
This categorization must not at all serve as a hindrance from getting a combination of solutions from either
category. Integration is very much possible between solutions of both categories, and depending on an
organization's needs, could be the recommended approach.
For NEA, since this will be a first major system implementation, a generally simpler end-to-end solution
would be an ideal initial step. Then, as the organization and its needs grow, best of breed solutions may be
chosen to upgrade the initial setup to incorporate special system features.

The table below provides a shortlist of BI solution brands and shows the functions covered and which
category they belong to.
Table 12: Summary of Solution Recommendations

BI Solution/ Data
Category BI Solutions Database ETL Data Visualization/
Warehouse Discovery
Informatica x
Commercial Microstrategy x x
"Best of Breed" Tableau x
Qlik x
Microsoft x x x x
Commercial SAP x x x x
"End to End"
(DB-ETL-BI) Oracle x x x
IBM x x x
Pentaho x x
Open Source
Jaspersoft x x
4.1.1.3 Brand Comparison

Presented below is a table listing strengths and weaknesses for each BI solution identified in Table 12.
These are based on comments from organizations that have used the solutions and results of studies as
compiled within the Magic Quadrant and Wave Reports of technology research firms Gartner and Forrester.
Table 13: BI Solution Brand Comparison

BI Solution Strengths Weaknesses
 High implementation success rate.  This software product specializes on ETL

Informatica claims to have the highest and data integration only.
success rate for ETL -- nearly 100%.  High cost of ownership
Product rate of renewal and customer
loyalty (94% and 92% ) is significantly
high compared to the industry average.
 Readily available tool and easy to learn
training modules.
 Does not require database expertise to
use the software.
 Has built-in internal scheduler function
unlike other tools that need to utilize
external third-party scheduler.
 High availability of resources to
implement and support the system.
 High scores in usability and satisfaction
from clients.

 Strong in BI platform administration,  Limited content from the MicroStrategy
internal platform integration, metadata community
management and traditional styles of  High availability of resources in the IT
analysis. industry to implement and support the
 Vendor of choice for complex enterprise system.
requirements.  The out-of-box graphics in a
 Supports rapid prototyping of dashboards. MicroStrategy report are unusable, and
 User friendly web-based tool for self- formatting them to be presentable takes
service creation of visualizations. It longer than building the schema.
features drag-and-drop analysis for  Some elements are complex to use such
business users without the need to have as dimensionality attributes, document
database and programming knowledge. design, data mining, etc.
 Features beautiful dashboards which  High learning curve for users, primarily
increases business user buy-in. because it supports highly complex
 Has strong features for creation of mobile reporting and analysis requirements.
application.  Complex software licensing mechanism.
 Has strong customer references with
enterprise-wide BI implementation
 Solid company profile. This is the third
largest independent BI platform vendor
with more than 3,000 customers.
 BI skills not required, user friendly. Its UI  Limited product line focused on data
is intuitive, with drag and drop features discovery.
allowing non-technical resources to easily  Weak in traditional analysis, metadata
use it. management, BI platform administration.
 Analytic dashboards, free-form  Tableau Server has a scalability issue:
exploration, business-user data mash up working with a large data set is not that
and cloud deployment are platform fast.
strengths.  Does not support functionality for
 Data synchronization is seamless. scheduling or notification of reports.
Supports fast connection to multiple data
sources (database, Excel, text files, etc.)
in one click
 Easy to generate fairly complex reports
that supports interactive visualizations
and decision support for quick analysis in
an intuitive, drag and drop manner.
 Supports mobile deployment.
 Comprehensive online resources
available.
 Market leader in data discovery.  Limited in performing traditional analysis.
 Known for ease of use.  Need for skilled developers to develop
 Low implementation time and effort. dashboard applications. Qlik utilizes
 Has a large online community. proprietary SQL for database queries.
 Has a robust mobile application. Hence, end users will have difficulty
creating dashboards and ad-hoc reports
without support from IT.
 Based on a survey done by Gartner, Qlik
has a below than average rating for
customer support.

 Has a very strong data integration  Instability of platform reported.
component. It has the capability to  Limited support resources locally
connect to multiple (and almost any) data available. Less Pentaho consultants are
sources as input and output. available in the market as compared to
 Easy to use data integration even for the other tools.
business users.  Difficulty in developing scheme
 The data integration component provides workbench. Use of metadata layer is not
a preview of the data allowing data intuitive enough for business users.
analysis even while development is  Does not offer as much functions to
ongoing. customize reports contents, look and
 Reporting has fast response time due to system behavior as the other tools
in-memory caching processing.  Lack of detailed documentation especially
 Supports commonly-used platforms: for the community edition.
Android, iPhone, iPad, Mac, Web-based,
Windows.
 Being an open source tool, Jaspersoft is a  Report customization requires Java
low-cost alternative to commercial BI programming knowledge.
software products.  If the organization customizes the
 Report writing, distribution and ETL is functionality for their specific needs, they
easy to use. It has powerful features that can no longer fully rely on Jaspersoft for
allow quick deployment of basic reports. support.
 Functionality is comparable with leading  Requires reports to be compiled prior to
commercial solutions. executing them, which adds a step in
 Provides clear installation instructions. report deployment.
 Difficult to create "ranking" (Top-N, Top-
N%, Bottom-N, and Bottom-N%) reports.
 Less available resources to implement
and support the tool.
 Offers end-to-end BI solution, including  Complex product portfolio particularly
Integration Services for ETL, Reporting within the Power BI products.
Services, Analysis Services and PowerBI  Requires current versions of office, SQL
for the BI layer, SQL Server and Parallel server, SharePoint for on premise
Data Warehouse for the Data deployment.
Warehouse. The mentioned BI tools are  Reported weaknesses in mobility.
bundled with varying functionalities within
the different editions of SQL Server –
Enterprise, Business Intelligence and
Standard Editions.
 Low cost of ownership.
 Supports integration with Microsoft
Office/365.
 Easy to use.
 Good visualizations and graphics.
 Flexible and relatively straightforward to
implement.
 Has good integration capabilities with
Microsoft Excel. Power BI utilizes the
familiarity of most users in Excel, to allow
the user to easily start using the tool.
 Solid customer references from an
average of 6,600 end users.
 Power Query allows business users to
access data sources without the need for
advanced IT knowledge.
 Online training materials are readily
available from Microsoft.

 Offers end-to-end BI solution, including  Costly licenses. This also causes some
Data Services for ETL, BusinessObjects organizations not to expand their
for the BI layer, Sybase IQ and/or HANA Business Objects deployment.
for the Data Warehouse. SAP offers  Limited support resource availability.
bundled licensing for this end-to-end  Needs improvement on user experience.
solution.  Low scores in self-service usability.
 Considered strength is in ad-hoc query  Below average features in mobile
and template reporting. deployment.
 Highly scalable as it is designed to
support the requirements of large
organizations.
 Business Objects can connect to a variety
of data sources and integration points.
 SAP is a well-established company with a
solid reputation for its enterprise
applications and significant financial and
technical resources (25% market share).
 Offers end-to-end BI solution, including  Does not normally offer the BI tools as a
Oracle Data Integrator for ETL, Oracle packaged solution.
BIEE for the BI layer, Oracle DB and  Costly licenses.
Exadata for the Data Warehouse.  Needs improvement in terms of customer
 Supports large-scale enterprise-wide BI experience. Based on a Gartner survey,
implementation. most notable concerns are on the area of
 Strong in traditional analysis. usability, difficulty in development and
 OBIEE is a complete solution. It provides administration, and quality of support.
Business Intelligence tools for reporting,  Low scores in self-service usability.
analysis, ETL and a database to serve as
a Data Warehouse.
 Features a powerful analytics tool without
the need for SQL or database table
knowledge.
 Can support complex reporting
requirements.
 Offers end-to-end BI solution, including  Costly software licenses.

Datastage for ETL, Cognos BI for the BI  Need for skilled IT staff to maintain and
layer, IBM DB2 and/or Netezza for the support the system.
Data Warehouse. IBM offers bundled  Lagging in terms of self-service
licensing for this end-to-end solution. visualization and data exploration.
 Supports large-scale implementation.  Low scores in self-service usability.
 Supports tiered architecture, which makes
it scalable for an increasing user base.
 Has mature mobile application features
supporting native applications for iPad,
iPhone and Android.
 Has powerful features that can address
all the complex business intelligence
requirements.
 The tool can access a wide variety of data
sources.

4.1.2 Web Portal
Figure 19: Web Portal Sample Screenshot
The web portal is an application designed to support and manage the collection and validation of data
between the ECs and NEA. It will be on the web for accessibility of the ECs regardless of location and could
accommodate the following activities to be done by the corresponding user:
Table 14: Summary of Web Portal Activities

Web Portal Activities EC NEA
Upload of templates for EC to access X
Submission of data through templates (monthly, quarterly, etc.) X X
Submission of attachments (power bills, board resolutions, etc.) X X
Approval/acceptance of submitted data X
Management of Master Data X
Monitoring of submission statistics X X
Link to viewing reports X X
4.1.2.1 Functional Requirements

The requirements enumerated below are designed according to the NEA and the ECs' needs and could
serve as the preliminary guideline for assessment of how the web portal will be developed, which will be
elaborated by the system implementor as part of their functional and technical specification preparation
phase.
Table 15: Web Portal Functional Requirements
Process/Capability Functionality
User Management
User Access User types are maintainable.
User profile and access types are maintainable.
Log In/Out Allow users to log in/out of the system.
Allows password administration.
Data Collection

16
Data Entry Allows users to upload populated templates (.xlsx files ) and other
necessary attachments into the system.
Organizes the uploaded files and data according to selected
parameters (i.e., reporting date, type of attachment, etc.).
Data Validation Ensures all required fields are populated.
Checks the content of selected defined cells for format, type of data,
etc.
Generates a file indicating the errors found in the uploaded data.
Notifications
Alerts and Email Can set up email notifications to provide users with reminders on
portal activity such as a submission, approval, etc.
Data Inquiry and Viewing
Reporting Consolidates various usage statistics into reports such as:
 EC submissions as of date
 Trend of EC submissions in the past 6 months
Allows NEA users to create simple reports on usage and
submission statistics.
Ad Hoc Query Enables the users to enter and execute a query for retrieving
uploaded data through a business-friendly universal layer, without
the need for programming.
Download Allows users to download the submitted templates into MS Excel
files.
Approval and Comments
Approval and Comments Enables NEA users to approve data submitted by the ECs and add
comments on approval/disapproval.
Tags approved data as available for ETL.
Interfacing
Links Can accommodate the links to other websites such as the NEA
website and the web location of specific BI output (reports,
dashboards, etc.)
w/ BI system Allows data access to BI system for capture of approved data for
ETL.
System Administration
Scheduling Allows an administrator to manage/set up the deadline of
submission for every reporting period.
Back Up Allows an administrator to schedule and back up the full database

into a non-proprietary file (i.e., csv, db).
System Logs Records a log of all system activities of all users.
16
It is highly recommended that a standard format be established and complied with to ensure streamlined development and that files
accomplished and submitted to the portal are always valid.

The user perspective of having these functional requirements is presented in Annexes 6.4 and 6.5 through
use case diagrams and user stories.
4.1.2.2 Custom Development

The web portal is designed specifically for the needs for NEA and though there may be existing solutions
that can be acquired off-the-shelf with select similar functionalities, configuration and other changes to the
application will still be required to meet all the functional requirements identified. As this will entail effort and
resources, custom development is the recommended approach to ensure that all required functionalities are
covered for the application to perform as designed.
17
Java and .NET are the recommended development platforms for this application for the following reasons:
 Certified resources with such skills are commercially accessible and supported by a huge community
of experienced technical professionals.
 Tried and tested in the development of similar applications.
 Can be integrated with other mainstream systems.
 Stable, reliable and secure development environments guaranteed.
 Better support for connection with big databases and visual studio programming.
 Performs well under a heavy load of data leading to efficient use of hardware resources.
The activities involved in custom development will be discussed in Section 5.4 Web Portal Implementation.
4.1.2.3 NEA's Current Initiative - Online Unified Reporting System (OURS)
As of this Design Report, NEA is undergoing user acceptance tests for OURS, an online web-based system
intended for use of the ECs in submitting their monthly requirements. OURS is considered as an overlap with
the web portal system, as they both function as a data capture system. In addition, the following issues on
OURS' implementation are summarized below:
1) As a data capture facility, the design of OURS must include the additional data and granularity
requirements according to the data models prepared for this IT design. The data entry templates (Section
3.1) and data dictionary (Section 3.4) illustrate the specific data entities and granularity required.
2) OURS should be able to easily reconfigure its database and data entry screens to be able to address the
additional data and data granularity needed to support identified and future BI analysis.
3) Additional development on OURS will be necessary to generate the file(s) that will pass on data to the BI
system.
4) OURS must be able to support offline submission/uploading of reports to ensure that ECs with internet
connectivity issues are still able to submit complete data by the set timelines. If not, NEA should be able to
support those ECs. Apart from this, OURS must be able to support the other functions envisioned for the
web portal such as the validation and approval of key data submitted to NEA and publishing of BI generated
reports, etc. as discussed in Annex 6.5 User Stories.
5) As subscription payments are required for an EC to be able to use OURS, NEA should be able to manage
the risk of some ECs who might be unable or opt not to pay for those subscription payments and therefore
will be unable to submit data online through OURS.
6) OURS and the integration that will be built for it to address the BI system's needs will have to be
completely and thoroughly documented to ensure NEA's security and sustainability such that other
implementors/vendors could study the system, troubleshoot and provide support and maintenance, as
needed.
17
.NET requires a minimal investment on development license cost as opposed to Java which does not.

7) Implementation of OURS must not delay the implementation of the BI system. If OURS will be the source
of raw data, it should be stable and running by the time the BI system is ready for implementation.
However, as OURS is already being implemented, the following are NEA's options moving forward:
Option 1: Continue implementation of OURS to serve as the data collection system
In order to make OURS the data collection system, it is pre-requisite that all issues identified above are
addressed to ensure its seamless integration with the BI system. The implication of this option is that
NEA will need to coordinate with 2 system implementors (i.e. Prudentia and web portal/BI implementor).
As these are two separate providers, both providers will rely on NEA to do the coordination work
including interdependent activities such as integration design and testing. Another risk of this option is
that no matter how well the BI system is developed, it will not be usable unless all issues on OURS are
resolved and are completed prior to the testing phase of the BI system. As a standard practice, the BI
implementor cannot be held contractually liable in case Prudentia fails to deliver. OURS' implementation
timeline has stretched and extended beyond its planned schedule. This would be a risk to the
implementation of the BI system, if it will depend on OURS for data collection.
Also, OURS is basically considered a SaaS solution that is being custom-developed specifically for NEA.
The vendor will not charge anything to NEA but will charge subscription fees to the ECs on a monthly
basis. If OURS will have to be customized to develop the additional requirements for a data collection
system, there is no clarity on who will shoulder this cost.
Option 2: Discontinue OURS, and replace it with a new web portal
To avoid having 2 redundant systems catering to a similar function, the other option is to discontinue
OURS upon implementation of the BI System and have a web portal component developed based on the
envisioned functional design. If implementation of the web portal is followed according to the details and
schedule in this design document, the solution composed of the identified functional requirements
needed to have an integrated system fully functional upon system implementation will be available to
NEA. Although not a requirement, if both the web portal and BI system are contracted to a single system
implementor, this would help reduce project implementation risks on NEA’s part, as the system
implementor will be responsible in ensuring that the end-to-end system design (from data collection,
organization to visualization) will work seamlessly to ultimately provide an integrated system that
facilitates effective and efficient data reporting and analysis.

4.2 Technology Architecture
4.2.1 Hardware Requirements
The hardware resources needed are based on a set of parameters such as the number of users in total and
during peak periods, as well as on the expected volume of transactions that the system will process. The
figures for the parameters are the estimated workload that the system needs to process in the immediate
term aligned with the desired performance and service levels for day-to-day operations with an additional
allowance or contingency in place for abnormal situations that may arise and for the future when
expansion/increased utilization can be expected.
Figure 20: Server Landscape
The diagram above shows a logical setup which can be adopted and implemented for the system. In this
setup, it can be seen that the servers for the solution will have a presentation layer – Web Server – located
18
in a DMZ or the demilitarized zone (also called perimeter network), a public-facing zone. This layer will
serve as the gateway and point of contact of the different users of the system (ECs and the public like DOE,
ERC, etc.). The business logic will be separated and hosted on an application server located within the non-
public facing zone of the network separate from the Web presentation layer. In addition, the database server
is also located in a non-public facing zone. It is also important to have the necessary storage for storing and
processing the expected voluminous data to be processed by the system. A common storage solution can
be used for managing the transactional data which can also be used for creating data snapshots or backup
which can then be offloaded to cheaper storage media such as tape or portable storage devices and further,
be stored in a secure off-site location.
To guide in the selection of hardware for the BI system, the following table outlines key components
characteristics or capabilities to allow for a future-ready and flexible application:
18
“In computer networks, a DMZ is a physical or logical sub-network that separates an internal local area network (LAN) from other
untrusted networks, usually the Internet. External-facing servers, resources and services are located in the DMZ so they are
accessible from the Internet but the rest of the internal LAN remains unreachable. This provides an additional layer of security to the
LAN as it restricts the ability of hackers to directly access internal servers and data via the Internet.” (Techtarget.com)

Table 16: Technology Architecture Components
Technology Architecture
Components and Description Remarks/Notes
Characteristics
Server Operating System Should support Proprietary and Opensource This includes brands
operating systems such as MS Windows and such as but not limited
Linux for x86 64-bit to Windows, Linux, Unix
Work Station Operating Should support Proprietary and Opensource Such as:
System operating systems such as MS Windows and Windows/Linux/MAC
Linux for x86 64-bit
Database Support Should support major Relational Database Commercial and Open
Management Systems (RDBMS) Source RDBMS
Architecture Should support multi-tier architecture to allow n/a
separating of application layers for security and
performance concerns: presentation, business
logic, database, others
Usability & Accessibility Should be web-accessible using major/common Such as: IE, Chrome,
browsers on a number of different devices Firefox, Safari, etc.
including mobile devices
Interoperability & Should be able to integrate and work with external Such as: RPC, Web
Integration or 3rd party solutions using standard Services, Message
connectivity/integration approaches Queues, etc.
Scalable Should be able to support a minimum of 50 n/a
concurrent users and can scale to support 1 TB of
data or higher
High-Availability The solution should be configurable to run in a high n/a
Configuration availability / redundant setup (i.e., use of horizontal
scaling, clustering, and other similar technologies)
Based on the system and end users transaction requirements, the following hardware specifications are
required to host the envisioned solutions.
Table 17: Hardware Specifications for Web Portal
Production Non-production (QAS & DEV)
Application Web/Application
Web Server Database Server Database Server
Server Server
CPU (Cores) 2 Cores 4 Cores 4 Cores 4 Cores 4 Cores
Memory (GB
8 GB 32 GB 32 GB 32 GB 32 GB
RAM)
System Disk
100 GB 100 GB 100 GB 100 GB 100 GB
Space
Data Disk
300 GB 1 TB 1 TB 1 TB 1.5TB
Space
Windows, Linux Windows, Linux Windows, Linux or Windows, Linux Windows, Linux or
OS
or equivalent or equivalent equivalent or equivalent equivalent
Any RDBMS that Any RDBMS that
Software
can provide the can provide the
(for Database N/A N/A N/A
required required
Servers)
functionalities. functionalities.

Table 18: Hardware Specifications for BI
Production Non-production (QAS & DEV)
Data Data Data Data Warehouse
ETL Server Warehouse Warehouse Warehouse ETL Server Server
Web Server APP Server DB Server (Web, App & DB)
CPU
4 Cores 2 Cores 4 Cores 6 Cores 2 Cores 4 Cores
(Cores)
Memory
16 GB 8 GB 16 GB 32 GB 8 GB 16 GB
(GB RAM)
System
100 GB 100 GB 100 GB 100 GB 100 GB 200 GB
Disk Space
1.5TB (3x500
GB with FC
Data Disk
300 GB 300 GB 1 TB Card to 300 GB 500 GB
Space
connect via FC
to SAN)
Windows, Windows, Windows, Windows,
Windows, Linux Windows, Linux or
OS Linux or Linux or Linux or Linux or
or equivalent equivalent
equivalent equivalent equivalent equivalent
Software Any RDBMS that
(for can provide the
N/A N/A N/A N/A N/A
Database required
Servers) functionalities.
The specifications above can be used as a guideline in procuring physical servers for an on-premise setup or
for provisioning cloud based services.
For high-availability of an on-premise setup, an additional set of hardware to mirror the production servers
may be procured to provide local redundancy.
An alternative approach for procuring individual servers for an on-premise setup would be to consolidate the
server requirements for production and non-production, and procure large servers which can be managed
and partitioned accordingly using a virtualization tool. This will allow an organization to have some
capabilities available similar to cloud services, providing more control over their computing landscape (i.e.
how servers are provisioned, utilized and managed). The limitation would be the type of services available
compared to public cloud offers as well as expansion capabilities as the organization will only have a finite
set of compute, storage and network resources. The following can be considered for such consolidated
setup:
Non-Production Production Server

Production Servers
Servers Hardware
CPU (Cores) 26 14 26
Memory (GB RAM) 144 88 144
For the physical servers, non-consolidated/individual servers and consolidated servers setup, a shared fiber
channel / iSCSI Storage Access Network (SAN) device is recommended for better disk storage
management. This should be paired with dual SAN switches with redundancy for resiliency. The SAN
storage solution will also allow more efficient utilization of storage resources and easier expansion.
In addition, an enterprise backup tape system, using Linear Tape-Open (LTO) technology should be
considered as a means to create copies of the system backup to portable media (tape, in this case) to allow
the organization to easily transport copies of the backup to secure remote locations for safe-keeping.
4.2.2 Database Requirements

A database platform is where data is managed, stored and processed. There are different options in data
management but the following should be supported:
 Basic database operations – CRUD (Created, Read, Update and Delete) records.

 Sequential query language (SQL) access for the database.
 Object storage requirements of the application – supporting various schema formats (2NF, 3NF,
etc.).
 Stored procedures/functions which can be invoked internally in the database or externally by an
application transacting with the database.
 Management of concurrency access to ensure data integrity and prevention of users from executing
transactions on the same specific data element.
 Management of data transactions to ensure completed transactions are committed and reflected in
the database, and incomplete transactions rolled back and cleared up.
 Enforcement of referential integrity to ensure data integrity across the database using primary,
secondary and foreign keys and are consistent across the system.
 Redundancy/failover features to support data availability and protection.
 Advanced database features such as partitioning, indexing, auto resize, and others to allow
performance tuning.
 Advanced administration tools and functions for easy database management.
Having the right database component as part of the solution is critical in the success of deployment and
operation of the system. At the same time, it assures management, administrators, end users (internal and
external) of data security and accessibility.
4.2.3 Network Requirements

Given the mandate of the agency, NEA has to ensure that the NEA IT System is accessible to NEA users at
the NEA office, at meetings outside the NEA building and when on assignments that require travel. In
addition, key functions of these systems need to be accessible to the ECs. This requires NEA to have a
strong network setup wherein internal and external users are able to access the different systems easily
without any slowdown.
The network design should also be secure from internal and external threats. Currently NEA already has an
existing LAN and WAN setup and has an existing Unified Threat Management (UTM) solution in place. The
current structured cabling of NEA is also planned to undergo an upgrade which will include expansion and
replacement/addition of active network components.
Currently, NEA has dual internet links 20Mbps and 15Mbps with an incoming appliance to provide bandwidth
management and balancing services to ensure that internet access is fast for internal users and for NEA
systems to be accessible to external users.
For the envisioned solution, an essential component for the NEA IT System is a high-speed internet link.
However, considering that there are locations that have challenges in terms of access to reliable internet, the
design incorporates an offline mode which will allow ECs to prepare their data entries offline, then upload
them when internet access is available on location or in a nearby facility. In extreme scenarios when internet
connection cannot be accessed after exerting all reasonable effort, the system should allow a NEA resource
to upload the accomplished data entry templates in behalf of the ECs.
The following are the assumed connectivity requirements that need to be supported:
Table 19: Connectivity Requirements

Parameter Value
Assumed peak number of 50
concurrent users accessing the
Assumes:
system via the internet 30 EC users (25% of total number of ECs, 1 user each);
15 NEA users
5 Other users (DOE, ERC, etc.)
Size of upload per user 5 MB

EC data uploading Schedule End of the month
Size of reports downloaded per 3 MB
user

Schedule of report release and First week of the month
distribution
Based on the parameters provided above, the data traffic and transmission time are shown below:
Peak
Concurrent Upload Size per With Network Transmit time at Transmit time at
Total Upload per
Access / Session Overhead 10Mbps 25Mbps
Session (MB)
Session (MB) (10%; MB) (hh:mm:ss) (hh:mm:ss)
(Users)
50 5 250 275 00:03:40 00:01:25
The estimated transmission time assumes that the full bandwidth is allocated or dedicated for the data
transmission though actual performance will be affected based on the utilization of the link. Based on the
information on the upgraded link of NEA (20Mbps and 15Mbps) that is load balanced, these should be able
to support the system if hosted internally in NEA or on the cloud.
To ensure that the network infrastructure of NEA is able to support the needs of the proposed system as well
as other systems currently running or planned, the following activities are recommended:
 Ensure all network documentations are updated and reflects what is implemented in production (e.g.
Network Topology & Design, LAN segmentation, IP Addressing scheme, Network Equipment
inventory with status, Access list, Current Internet Link Utilization, Network Routing, and others)
 Assess current network status and develop recommendations and action plans.
 Update the Network Design and Configuration in alignment with the recommendations and action
plans as well as with access and security policies.
 Implement the recommendations and action plans.
Prior to system implementation projects, it is assumed that NEA has already completed all ongoing Network
related initiatives for 2015:
 Completion of government interconnection via DOST-ICTO
 Upgrade of the internet links to 20Mbps and 15Mbps
 Implementation of a network load balancer
 Upgrade of the LAN via a structured cabling project
As there are other factors that contribute to the overall network performance, the following needs to be
included in the network assessment to determine other components that need to be in place:
 Actual network traffic/utilization at LAN, WAN and Internet level
 Network topology, design and configuration that govern how network traffic moves, this will include
the network segmentation, routing rules, access list, hops, and others
 Information Security rules and policies are reflected in the network design and configuration, as the
network performance will have some overhead as a result of information security
scanning/inspection of network traffic
 Current status of network equipment – health, capacity, bandwidth
 Elimination of possible malware activities in the network (Worms, Trojans, etc.)
The cost estimates for the project does not include the network upgrades/enhancements as the final
recommended actions/initiatives for improving overall network performance can only be determined after a
detailed assessment, a dedicated initiative in itself.

4.2.4 Work Station Requirements
There are two types of workstations needed depending on user type. If a user will only access the system to
upload files and download (static) reports but will not run the advanced BI reports/interface, the following are
the work station minimum specifications:
 CPU: i3
 Memory: 4GB
 Storage: 80GB
 Network: Internet and/or LAN connection (1 Mbps)
 OS: Windows 7 or latest, Mac OS X, Ubuntu
 Software
o Web browser (IE10, Google Chrome, Mozilla Firefox, Safari)
o MS Office 2007
o PDF Reader
For users who will use the BI reporting system:

 CPU: i5
 Memory: 16GB
 Storage: 80GB
 Network: Internet and/or LAN connection (1 Mbps)
 OS: Windows 7 or latest version, Mac OS X, Ubuntu
 Software
o Web browser (IE10 and above, Google Chrome, Mozilla Firefox, Safari)
o MS Office 2007
o PDF Reader
A typical desktop acquisition cost on average is Php 35,000 depending on the brand, final specifications,
add-ons, features, expandability and model. An alternative to acquisition is to lease units however leasing
may only be viable for large volumes to achieve economies of scale. NEA’s workstation requirement is not
considered as huge, hence leasing might not be a cost-effective option for now but should definitely
considered should the opportunity to merge with other government organization/s to increase required
volumes arise.
4.2.5 Delivery Models
The table below presents the advantages and disadvantages of using on-premise delivery technology as
compared to having full or a portion of the implemented application, database or infrastructure in the cloud,
as well as the risks to consider.
Table 20: Delivery Model Comparison

Option On-Premise
This is a service delivery model where the system is installed and operated from an
organization’s in-house server and computing infrastructure.
Advantages
Will work on local intranet connection.
Internet is not necessary for internal NEA users.
Generally has lower software maintenance agreement cost upon implementation on an annual basis.
Less risky in terms of information security as data is stored on-premise where access to the data can be
better monitored and controlled.
Disadvantages
Higher upfront investment cost.
Organization is responsible for the maintenance of the application (which may either be done in-house, or
outsourced and managed by the organization).
Need to maintain skills internally or manage third-party service providers for maintenance and support.
Organization is responsible for capacity planning and system upgrades, which often requires significant

effort.
Potential Risks Risk Mitigation Strategies
Skilled and experience personnel resignation. Effective succession planning for key IT resources
that will maintain the system.
Outsource to providers of managed services
specific activities/roles, so that internal NEA
personnel can be freed up to focus on higher value
tasks/activities. The service provider will now be
responsible to ensure that trained and skilled
personnel are available to fulfil the role.
Budgeting and acquisition cycle versus capacity Effective capacity planning in alignment of the IT
requirements and actual utilization. It takes time to budgeting process.
acquire new resources should there be a need to
add capacity or replace/repair components.
Risk of computing facility failure (e.g. power outage Establish DR/Business Continuity Site.
or fire in server room).
Option SAAS
Software as a Service is a service delivery model where one or more applications and the
computational resources to run them are provided for use on-demand as a turnkey service. Its
main purpose is to reduce the total cost of hardware and software development, maintenance,
and operations. Security provisions are carried out mainly by the cloud provider. The cloud
consumer does not manage or control the underlying cloud infrastructure or individual
applications, except for preference selections and limited administrative application settings.
Advantages
Maintenance activities are minimal.
Server management and maintenance activities are taken care of by the SAAS provider, except for some
functions that are organization specific and delegated by the solution the organization consuming the
service (i.e., creation of application end-user accounts, deletion of reports, etc.).
No need to maintain IT skills to maintain applications.
SLA-based support from service provider.
Lower upfront investment cost. Typically only a subscription fee is required to be paid on a set
period/cycle.
All system & application patches and upgrades will be managed by the service provider.
Disadvantages
Internet connection is required to access software.
Generally higher recurring software subscription cost than an on-premise software's maintenance
agreement cost.
Critical and confidential data is entrusted to service provider, and hosted on a shared infrastructure base
though logically segregated/separated from other organizations.
System availability is dependent on internet and service provider’s availability. If either is down or faulty,
the system would be inaccessible.
Integrations with other corporate systems is more complex as data will have to be sent through the
internet.
Full dependence on provider such that if the Endeavor to establish an amendment or additional
provider is acquired, stops the service or closes clause in the contract for cloud services to govern
shop, there is a potential disruption to the business the use of providers cloud services,
and may take NEA some time to select a new data/information security and engagement between
SaaS solution and perform data migration from NEA and the cloud services provider. This is an
current to new SaaS provider. There is also the risk addendum extending the standard agreement to

that data is deleted / not copied after migration, cover specific needs of the organization.
etc.).
This may not be applicable to all Cloud services
provider and in case this is doable may result in
premium rates being applied.
Risk of system unavailability if internet connection Establish a business continuity plan to resort to
or service provider’s system is unavailable. alternative automated and/or manual processes
during downtime and a mechanism to transport
data to the system one it becomes available.
Subscription to premium service for higher

resiliency feature.
Require a robust information security plan from the

provider. Further mitigation includes requiring the
provider to undergo third party information security
audits on a regular basis.
Option PAAS
Platform as a Service is a service delivery model where the computing platform is provided as
an on-demand service upon which applications can be developed and deployed. Its main
purpose is to reduce the cost and complexity of buying, housing, and managing the underlying
hardware and software components of the platform, including any needed program and
database development tools. The development environment is typically special purpose,
determined by the cloud provider and tailored to the design and architecture of its platform. The
cloud consumer has control over applications and application environment settings of the
platform. Security provisions are split between the cloud provider and the cloud consumer.
Advantages
No need to invest in technology for platform that will be used only for development
No need to maintain IT skills needed to maintain the platform.
The main advantage of public PaaS is that the consumer of PaaS services does not have to manage and
maintain the infrastructure or the application stack (operating system, application server, database, and
programming language).
Development team can focus on developing codes for the application.
Disadvantages
Might not be beneficial to NEA if they are not planning to keep an in-house IT team that will develop
applications using the platform.
Need to pay recurring maintenance cost for software components that were obtained from PaaS.
Once the subscription expires, an application running on the PaaS platform may stop working, experience
performance degradation, or have annoying pop-ups.
System availability is dependent on internet and service provider’s availability. If either is down or faulty,
the system is inaccessible.
Full dependence on provider. If provider is Endeavor to establish an amendment or additional

acquired, if provider stops the service or closes clause in the contract for cloud services to govern
shop, there is a potential disruption to the business the use of providers cloud services,
(it may take time to select a new PaaS solution, data/information security and engagement between
data migration from current PaaS provider may be NEA and the cloud services provider. This is an
challenging. There is also a risk that data is deleted/ addendum extending the standard agreement to
not copied after migration, etc.) cover specific needs of the organization.
Risk of system unavailability if internet connection Establish a business continuity plan to resort to
or service provider’s system is unavailable. alternative automated and/or manual processes
during downtime and a mechanism to transport

data to the system one it becomes available.
Subscription to premium service for higher

resiliency feature.

Option IAAS
Infrastructure as a Service is a service delivery model where the basic computing infrastructure
of servers, software, and network equipment is provided as an on-demand service upon which
a platform to develop and execute applications can be established. Its main purpose is to avoid
purchasing, housing, and managing the basic hardware and software infrastructure
components, and instead obtain those resources as virtualized objects controllable via a service
interface. The cloud consumer generally has broad freedom to choose the operating system
and development environment to be hosted. Security provisions beyond the basic infrastructure
are carried out mainly by the cloud consumer.
Advantages
Server management and maintenance activities not necessary.
Less upfront capital cost for hardware/infrastructure.
Utility-based or pay-as-you-go model which promotes highly scalable resources that can easily be
adjusted as the need arises. This eliminates high upfront capital costs of hardware.
Savings can be realized in terms of equipment maintenance (i.e., manpower, facilities management,
HW/SW procurement, provisioning, patching, etc.)
Some administrative tasks (Hardware Maintenance, upgrades, repairs, expansion, etc.) are taken care of
by the provider.
Service provider takes care of infrastructure, risks to ensure high availability and disaster recovery are
also within provider's responsibility.
Disadvantages
Higher recurring service subscription fee/ cost.
Critical and confidential data is entrusted to service provider.
Infrastructure availability is dependent on internet and service provider’s infrastructure availability. If either
is down, the system is inaccessible.
Heavy reliance on service provider and internet for Comprehensive review of SLAs, data security
availability and data security warranties and exit process prior to contracting to
ensure acceptable service level is achieved.
Critical and confidential data is entrusted to service Endeavor to establish an amendment or additional
provider. clause in the contract for cloud services to govern
the use of providers cloud services,
data/information security and engagement between
NEA and the cloud services provider. This is an
addendum extending the standard agreement to
cover specific needs of the organization.
Should be part of the contract terms (i.e., assurance
that data is deleted upon termination of service,
migration to new service provider in case of change
of provider, etc.)
Risk of failure at provider’s server site Subscription to premium service for higher
resiliency feature.

There are a number of vendors in the Cloud Hosting services area each with their own set of offerings and
tools which can be a variation or combination of the aforementioned three types of cloud services models
(SaaS, PaaS, IaaS). In terms of deployment model, there also different options such as:
 Private Cloud – where a cloud computing setup is dedicated for the use of a private organization.
 Public Cloud – where a cloud computing services provider offers cloud-based resources consumed
by different organizations they share the underlying resources (hardware, software, etc) though there
is a mechanism for logically separating the different organizations' allocated resources such that
these (sub-partitions / cloud service) are dedicated to the organization.
 Community Cloud – this is somewhere between a public and private cloud, wherein the cloud
resources are shared and dedicated to two or more organizations that have a common set of cloud
computing requirements, standards, privacy, security, and regulatory settings, instead of just for a
single organization.
 Hybrid – pertains to a setup wherein a combination of private, public or community is implemented to
allow its users to interoperate with one another.
Numerous cloud option combinations are applicable to the implementation of the NEA IT System and it can
be expected that various vendors will propose varying approaches and may result in some refinement to the
initial design.
Given the variety of cloud types/models and deployment models, and in consideration of the type of
workload foreseen for NEA’s future requirements, for the purposes of this study, only two setup models were
analyzed for Total Cost of Ownership (TCO). The first option being the private on-premise and the second
option, a full-cloud setup. For the on-premise setup, NEA will acquire their own hardware and software
resources, then install the solution within NEA’s offices. The full cloud setup on the other hand refers to a
scenario wherein NEA will host the solution on a public cloud provided by one of the leasing cloud services
providers. An important consideration in a cloud setup is the incoming and outgoing data traffic to a cloud
services provider’s network, as the incoming traffic is usually free, however for outgoing traffic, there is
typically a set free amount of data volume, beyond which incremental charges may apply.
The TCO analysis will allow equivalent comparison of hosting the solution on-premise or in the cloud. As
cloud generally has less upfront cost but has more costly operation and maintenance, while on-premise has
a high upfront cost but is less costly to maintain, TCO will remove the bias of one scenario over the other,
thereby providing a better estimation of costs associated with the acquisition and operation of the
technology. The study however does not limit NEA to these two setup options so as not to limit prospective
bidders who may choose to adapt and apply a different approach and may chose a public, private,
community or hybrid cloud deployment model integrated with an on-premise approach. Vendors may also
leverage on their individual strengths and experience to arrive at the best package.
Scenario 1: On-Premise
The on-premise option gives the organization full control as to what will be done to their applications, data
and equipment. However, this would entail significant effort and investment from NEA; investment not only
on the equipment, but also on skilled manpower for operations and maintenance, and space for both the
manpower and equipment.
Scenario 2: Full Cloud
The second scenario is a cloud delivery model where a cloud server will be used to host both the BI and web
portal applications. The BI software will basically be an on-premise license installed on the cloud to provide
19
the flexibility to install the license on-premise or on the cloud, as necessary . As for the web portal, as it will
be a custom-developed application using Java or .NET, it will not have any application license cost, and the
developed software application will be installed in the same cloud server.
Generally, use of the cloud is known as a cost effective option as it eliminates the need for an organization to
invest on skilled manpower for implementation and maintenance, on equipment and physical space.
19
This is also known as the Bring-Your-Own-License (BYOL) setup.

However cloud use can also entail significant costs if payments are based on metered outgoing traffic.
Should this be the case, it is recommended that a file server be purchased and maintained on-premise. This
file server will serve as the only recipient of data from the cloud to limit outgoing traffic. Then users could
simply access the on-premise server instead of the access the cloud directly.
4.3 Cost Estimates

As part of any solution delivery, there are common and specific components per solution. The common
components for NEA IT System would be the following:
 Compute Resources (Servers)
 Storage Resources (SAN Storage, SAN Switch, Tape Storage and Media)
 Software (Operating System, Relational Database Management System)
The BI system has the following cost components in addition to the common components mentioned above:
 ETL
 BI Solution
 Data Visualization Tools
 Configuration Services
 Implementation Services
Note that the web portal and BI will share the same hardware as it is assumed to be logically partitioned
using a virtualization tool.
Vendor packages may cover one or all of these cost components accordingly.
The table below presents the yearly breakdown and an aggregated cost of ownership for 5 years, adjusted to
a net present value (NPV) with an assumed 4% discount rate. This is applicable to the BI software,
20
hardware , services (estimated at 27 million pesos for BI and 17 million pesos for the web portal) and
maintenance. The costs are VAT exclusive.
The cost for the commercial BI solution which is inclusive of all three components is based on listed prices of
a high-end variant for the estimate to be conservative. There are BI solutions, however, that could be as low
as the estimated cost for an open source solution (for instance, one commercial end-to-end BI from a
reputable vendor costs around Php 8 million for a 5-year software license). In addition, the proposals may
vary according to how vendors adjust their pricing strategy.
It may seem, through the cost comparison, that to implement on the cloud would be more expensive.
However, it must be noted that the on-premise cost estimates do not include other expenses that are
expected such as the cost of manpower and manpower development (training) to operate and maintain the
hardware, cost of rental or space for a data center and its maintenance, data center engineering, and
environmental strengthening, which is not applicable to implementation on the cloud.
20
The hardware cost represents the consolidated hardware cost of BI and web portal which will be logically partitioned using a
virtualization tool.

Table 21: IT System Cost Estimates (Amounts in PHP)
Year 1 Year 2 Year 3 Year 4 Year 5 NPV
Commercial BI Solution On Cloud
Services Web Portal n/a n/a n/a n/a

17,000,000 17,000,000
Services BI n/a n/a n/a n/a
27,000,000 27,000,000
SW
25,208,511 5,545,872 5,545,872 5,545,872 5,545,872 45,339,447
HW
2,417,037 3,226,737 3,403,587 3,580,437 3,757,287 15,061,216
Other HW and Peripherals n/a n/a n/a n/a
4,250,000 4,250,000
Total
75,875,548 8,772,609 8,949,459 9,126,309 9,303,159 108,650,663
Commercial BI Solution On Premise

17,000,000 17,000,000
27,000,000 27,000,000
SW
27,114,341 5,965,155 5,965,155 5,965,155 5,965,155 48,767,229
HW n/a n/a
6,737,042 1,010,556 1,010,556 8,499,251
4,250,000 4,250,000
Total
82,101,383 5,965,155 5,965,155 6,975,711 6,975,711 105,516,479
Open Source BI Solution on Cloud

17,000,000 17,000,000
27,000,000 27,000,000
SW
4,620,116 2,576,426 2,576,426 2,576,426 2,576,426 13,972,271
HW
2,417,037 3,226,737 3,403,587 3,580,437 3,757,287 15,061,216
4,250,000 4,250,000
Total
55,287,153 5,803,163 5,980,013 6,156,863 6,333,713 77,283,487
Open Source BI Solution On Premise

17,000,000 17,000,000
27,000,000 27,000,000
SW
6,525,946 2,995,708 2,995,708 2,995,708 2,995,708 17,400,053
HW n/a n/a
6,737,042 1,010,556 1,010,556 8,499,251
4,250,000 4,250,000
Total
61,512,988 2,995,708 2,995,708 4,006,264 4,006,264 74,149,303
* Cost estimate assumptions are shown in Annex 6.6 Cost Estimate Assumptions. Detailed cost estimate
breakdown details are shown in Annexes 6.6.2, 6.6.3, 6.6.4, and 6.6.5.

4.4 Service Delivery Standards
Certain service delivery standards must be satisfied to ensure efficient system performance during the
operation of the system. Whether the systems will be implemented on-premise or on the cloud, the same
service delivery standards apply.
4.4.1 Service Availability

Service availability is defined as “the delivery of undisrupted services despite any system component failure.
A system configured with redundant components that fail could switch over to the standby components
without jeopardizing the metrics of reliability or availability. Service availability encompasses both the
requirements for high availability and the requirements for high reliability as they pertain to continuity of
21
service” .
A solution or service is only as strong as its weakest link, therefore it is important to establish delivery
standards that govern how the service is delivered and managed on a day-to-day basis. Certain service
delivery standards must be satisfied to ensure efficient system performance. Whether the systems will be
implemented on-premise or on the cloud, the same service delivery standards apply.
It is understandable that certain components of the solution will be subject to wear and tear resulting in
unplanned outages or resources may be used up which may lead to system performance degradation.
However, whether a system is classified as critical, high or medium importance, the goal is to minimize the
occurrence of possible service disruptions and ensure consistent availability of the service to users. This can
be achieved with the following:
 Design with high availability and redundancy in mind – systems should take advantage of the
advances in technology and engineering by factoring in the following:
o Use of clustering or similar technology at the various layers of the solution / system
o Use of load balancing of application delivery controllers
o Use of failover or standby technology
o Ensure rigorous testing to ensure the system does not break easily:
 Unit testing
 Load testing
 Stress testing
o Ensure that security hole or non-essential ports are secured
o Ensure proper exception handling and garbage collector/clean-up
 Regular scheduled maintenance – underlying components are checked and given preventive
maintenance. It is also important to ensure that the facilities where the system will reside have
regular preventive maintenance work (e.g. cooling, power, sensors, access devices, cameras, etc.)
 Capacity review and planning – definition of capacity thresholds (i.e., max percentage utilization of
CPU and RAM, minimum required free storage space, etc.), regular monitoring of system utilization,
monitoring of logs to ensure that system resources are available and within the set thresholds.
Definition of trigger points and the process for either freeing up resources via clean-up or acquisition
of additional resources.
 Establishment of a Disaster Recovery and Business Continuity Plan to continue availability of the
system in the event of an undesirable/abnormal situation.
 Establishment of an Operations Monitoring process and team to constantly monitor that services are
up and running within performance parameters set.
 Establishment of a service desk that will provide the necessary services for providing level 1 support
services, and will coordinate and escalate to level 2 and 3 support services.
The solution for NEA to serve ECs and other agencies the system and its services should be available, at a
minimum:
 12 hours a day for 7 days a week
 Off hours will be used for batch jobs and maintenance work
 Should be accessible via the internet using secure connection
21
Source: Service Availability Forum – Whitepaper

 Support services to end users should be available 8 hours x 5 days a week, with on-call support
depending on severity during off-hours.
4.4.2 Security
In IT, security often pertains to information security. To provide a holistic approach to securing the most
important asset in an organization, its information security needs to encompass technology, process,
application and infrastructure layers and the organization. This is important as entities with ill intent will
explore and use different avenues of attack.
With the growth in automation of key processes in an organization, there is a need for security of these
systems as these contain critical business information which if lost, damaged or breached can negatively
impact the enterprise. The impact can result to financial loss, loss of competitive edge, operational efficiency
degradation, and loss of reputation.
The threat to security can come from different sources – internal or external to the organization, through
various channels/mediums used by the attackers – such as physically infiltrating a facility to steal physical
files or storage devices, use of malwares and rootkits to exploit system weaknesses and to gain access to
the systems allowing data to be stolen or for the system to be destroyed or crippled, via social engineering to
gain access to the systems by finding ways to get valid access, and other various means.
To defend against these threats, an organization must take a proactive approach by defining and
establishing the necessary security policies, processes and procedures, supported by reliable technologies.
The Information Security framework should cut across the organization from policies, process, data,
applications & technology dimensions. In addition, it is critical to employ continuous education on recent
trends in information security and enabling staff to handle the current and emerging threats.
Data security refers to protective privacy measures to prevent unauthorized access to computers, databases
and websites. It is the practice of keeping data protected from corruption and unwanted access.
For prevention, the following approaches may be employed:
 Development and implementation of a secure network design and routing (e.g. proper configuration
of routers, VPN, and other network component to manage and control how data traffic is allowed
within the organization).
 Setup and configuration of firewalls (single or multiple) – implement firewalls to segment network and
limit traffic to authorized hosts, ports, protocols.
 Setup of Intrusion Detection and Prevention Solutions – detection of malicious activities and provide
mechanisms to prevent the malicious action by sending alerts to concerned administrators, reset of
the suspect connection, blocking of certain traffic/ip, and other measures.
 Setup of Anti-Spam solutions – screening of emails for SPAM. Some emails are used for phishing
and other forms of attack.
 Setup of Anti-Virus solutions – detection and neutralization of computer virus, worms, trojans and
other malwares.
 Operating system or software hardening – strengthening the software layer by turning off
unnecessary/unused services, securing user accounts especially those with power or administration
rights, application of necessary patches/fixes to plug security holes or bugs (such as buffer
overflows) that may be exploited by an attacker to breach a system.
Ideally, there should be multiple measures set up for detecting malicious activities in a network or system,
and the internal team should have the capability to neutralize these threats. An effective backup and
recovery strategy, disaster recovery and business continuity plan can complement information security by
allowing a means for the organization to recover the state prior to the breach.

Figure 21: NEA Landscape with Existing Security Solutions
The diagram above shows the current network landscape with some of the existing security solutions in
place at NEA.
4.4.2.1 Policies and Process

4.4.2.1.1 Role Based Access (Authorization)
It is important to set standards and policies which can protect relevant information from being extracted and
accessed by unauthorized users. All user accounts, computers, printers and other security principals, should
be registered in a centralized database. Authentication should take place on domain controllers. Each
person who uses computers within a domain should receive a unique user account that can then be
assigned access to resources within the domain.
The utilization of user role/profile based access increases the security level of the systems. The user profiles
can help users to maintain their own preferences, network settings and application settings when logging on
to a workstation. Also, the user profile can be assigned with unique functionalities depending on one’s role in
the system.
Benefits of utilizing user profiles are the following:
 Multiple users on a computer can retain their personal settings
 System policies can be applied individually or per group
 Limit/control information access based on user necessities
For a NEA network computer, there are three main types of users who can log into the workstations, and
each type of user (known as user profile) will have certain access restrictions in the system.
 EC User. This user profile mainly has the capability to upload, revise and view their data.
 NEA User. This profile also has the capability to upload, revise and view their data as well as the
data submitted by the ECs
 NEA System Administrator. This user has the capability to create and manage system settings, user
accounts and profiles.
The Information Security Policies and Procedures will be a key driver for a secure computing environment.
All stakeholders, not just the users, must be properly trained on information security best practices.

4.4.2.1.2 Username and Password Guidelines
User password creation and renewal guidelines should be defined to guide and secure the system.
Passwords are more secure if they are at least 8 characters long, utilize a mix of small and capital letters,
numbers and special characters. Common dictionary words should also be avoided. Users should be
encouraged to choose a password that they can easily recall to avoid having to write it down.
The processes for creating, reset, expiration and renewal of passwords should be clearly defined and
communicated to all concerned to avoid password related attacks and compromises on the system.
Another approach to having a secure and strong password is the use of two-factor authentication, wherein
instead of requiring a user to login with his username and password only, the user is also required to provide
a token that only he would know or possess (for example, a USB drive that contains a certificate or secret
token, a device that provides a key generated from a pre-agreed logic/algorithm).
4.4.2.1.3 Authentication and Authorization

With unique usernames and passwords, the system should identify the users' authenticity so they can be
allowed to proceed using the system. There are two steps as to which the system can allow the user’s
access, namely authentication and authorization. Authentication is the verification of the credentials of the
connection and access attempt. This process consists of sending credentials from the client to the remote
access server in plain text or encrypted using an authentication protocol. Authorization is the verification that
the connection attempt is allowed.
Authorization occurs after successful authentication. Authorization determines what an authenticated user
can do in the system. It limits what a particular user can do (i.e., inquire/read only, create new records only,
or create, update, delete and read). Authorization requires that the different user roles in a system be
predefined mapping users to the specific role or roles in the system. For example, an ordinary user can login
and only do inquiries and generation of reports, versus an administrator type user can be restricted to not be
able to do transactions but can execute admin-level tasks such as password resets of users, unlock of users,
backup of system data.
4.4.2.2 Physical Security

In the process of protecting information stored in the system, physical security is often overlooked. Buildings
and rooms such as Data Centers that contain information and information technology systems must be
protected to avoid damage or unauthorized access. In addition, workstations containing this information
(laptops, disk drives, file cabinets) must be protected as well. Equipment theft is a primary concern, but other
aspects should also be considered such as damage/loss due to fire, flood, temperature and other
environmental concerns.
Prevention is a key solution for physical security. This can be applied through an Access Control System.
This system shall be used to monitor and control traffic through specific access points and areas in NEA.
This can be done using either any or a combination of the identification cards, biometrics/fingerprint
scanning, CCTV surveillance cameras, security guards, electronic/mechanical control systems such as
doors and locks. Electronic access control systems make use of credentials which determine the level of
authorization of an individual. The control panel compares the credentials to an access control list which
grants or denies the access request. In addition, the use of metal doors and reinforced glass for windows
and walls prevent unauthorized access and break-ins to the physical facility.
4.4.2.3 Network Security

There are many threats which could compromise the system. These may include physical threats like theft,
system threats like brute force hacking and hacking through the system’s network. The most common
threats include:
 Malware: Virus, worms, Trojan horse

 Spyware
 Hacker attacks
 Identity theft
These threats can be prevented with the use of a network security system. A network security system
typically relies on layers of protection and consists of multiple components including network monitoring and
security software in addition to hardware and appliances. All components work together to increase the
overall security of the computer network. One network security system that can manage these is the UTM. It

is a term that describes a wide range of security functions and features combines into a single
appliance/solution. As described earlier, multiple security solution (Firewalls, IDS, IPS, Anti-Span, Anti-Virus,
etc.) tools can be employed and are typically integrated to form a UTM solution.
Typically, a UTM is a combination of firewall, anti-virus, intrusion and spam detection and prevention. The
principal advantage of a UTM product is its ability to reduce complexity. The principal disadvantage is that a
UTM appliance can become a single point of failure. As of date, NEA has installed a UTM application to
protect their information from being hacked or compromised through the network.
4.4.2.4 Database Security
Database technology is a core component of the system and should also be secured from unauthorized
access. Database security concerns the use of a wide range of information security controls to protect
databases against compromises of their confidentiality, integrity and availability. Databases have been
secured against hackers and other threats through network security measures such as firewalls, and
network-based intrusion detection systems that have also been stated earlier. While network security
controls remain valuable in this regard, securing the database systems themselves, and the
programs/functions and data within them, has arguably become more critical as networks are increasingly
opened to wider access from the Internet.
Many organizations develop their own security standards and designs detailing basic security control
measures for their database. These may reflect in user accessibility through granting and revoking,
obligations imposed by corporate information security policies and perhaps security recommendations from
the database system and software vendors. The security designs for specific database systems typically
specify further security administration and management functions (such as administration and reporting of
user access rights, log management and analysis, database replication/synchronization and backups) along
with other information security controls such as data entry validation and audit trails. Furthermore, other
operational management of the databases will fall under maintenance which should be incorporated by the
organization for a more specific and detailed policy.
As part of ensuring service availability and information security, it is important for the organization to have a
disaster recovery plan. This plan provides policies and procedures supported by technology that will help
ensure recovery after man-made or natural disasters with minimal to no data loss.
With the organization increasing its reliance on computer systems, a failure or a disaster can cause major
damage to the organization. Typically, a disaster recovery plan requires for a risk identification, assessment
and mitigation exercise to be completed. An enterprise class backup is required to ensure that its data at the
application and database level are secured.
The following measures can be set up to implement database security at the minimum. The amount of
acceptable downtime and data loss will determine the type of backup strategy to be employed.
 a regular backup schedule should be defined, with the frequency defined.
 a regular backup restore test should be done to ensure that the backup process / system works and
can be counted on during an emergency.
 one or more offsite backup location/s should be put in place so that copies of the backup can be
stored for possible use.
 required agreements with 3rd party providers need to be established so that in the occurrence of a
scenario where the backup will be needed, the organization can have the necessary resources on
standby or be made available on short notice.
4.4.3 IT Operations and Maintenance

Once the NEA IT System goes live, the following IT Operations and Maintenances activities need to be
performed to ensure efficient IT System Operation:
 Application Maintenance
 Ad-hoc Requirements – This involves configuration or development of new or revised
functionality, and other major project work
 Application Support – Resolution of incidents, errors, and minor project work
 Helpdesk Support – Providing guidance to a user in using the system or assistance in
conducting basic troubleshooting

 Application Administration – Configuration of tables in the IT System such as creation / deletion
of new user, profile definition, update of list of valid values, etc.
 Server and Data Maintenance
 Server Maintenance and Administration – Administration and optimization of servers and related
components as well as keeping the server software updated and running to keep the hosted
systems running
 Database Maintenance and Administration – Management and maintenance of database
management systems software which includes activities such as: configuration/upgrade of
database server software, execution of backup and recovery procedures, implementation of
database security, database performance monitoring, and troubleshooting.
Application Support
Application Support must be available to provide support to incidents and issues reported by the users. This
may be provided either by NEA, the system implementor and/or the software vendor. Application Support
can be classified into three levels.
Level 1 (also referred to as L1, Tier 1 or T1). This is the initial support level that involves gathering basic
information regarding user issues. L1 support will aim to understand the issue by gathering as much
relevant information as possible and record them in an incident log. Basic troubleshooting will also be
done such as: resolving user access problems, verification of software version, system navigation
assistance, procedural clarification, etc.
Level 2 (L2, Tier 2, T2). When the tickets are complex in nature and cannot be resolved by the L1
support, tickets are then escalated for L2 support for in-depth technical support. The L2 support team is
more experienced, skilled and technically proficient than L1, which are typically comprised of application,
server and database specialists.
Level 3 (L3, Tier 3, or T3)
The final escalation is L3, which is the most difficult/advanced problem to resolve. Tickets escalated to
L3 are mostly related to bugs that require deeper analysis. Configuration and codes may be analyzed to
identify the root cause. As such, in-depth domain expertise, application configuration and programming
skills may be needed for L3 tickets.
Level 4 (L4, Tier 4, or T4)
Unresolved L3 tickets are finally escalated to L4, which involves defects related to the software product
or hardware. They are escalated to the vendor for analysis and resolution. Tracking such issues is still
necessary to monitor vendor service level.

Figure 22: Application Support
Service Levels have to be established for operations and maintenance support. The service level typically
depends on the severity of the ticket which is classified based on their impact and urgency to operations.
The following table shows a severity classification based on impact and urgency.
IMPACT
URGENCY HIGH MEDIUM LOW

HIGH 1 2 3
MEDIUM 2 3 4
LOW 3 4 5
For each severity level, the service level in terms of a guaranteed resolution time has to be established. A
sample set of service level per ticket severity is shown below:
Table 22: Service Level Agreement Examples

Severity Level Description / Definition Guaranteed
Resolution Time
Priority Level 1 - System is down Within the day
(P1) - Critical - Major function unavailable
- Dramatic performance issues impacting
most users
- Corporate-wide or department-wide
- No workaround
- Applications or Systems are not down 1 Business Day
Priority Level 2
- Large number of users or are impacted
(P2) - High
- Performance or operational degradation
- Particular service is unavailable or
dysfunctional

- Problem causes production slowdown
- Workaround is available
- Applications or Systems are not down 3 Business Days
Priority Level 3
- Issues affects small number of users
(P3) - Medium
- Workaround is available
- Resolution of issue is not critical from 5 Business Days
Priority Level 4-
users’ perspective
5 (P4-5) - Low
- Involves a single user
- Is a user request
- Performance of modifications to existing
applications and systems
- All “How to” queries
- Predictable tasks
22
The SLAs are normally confirmed during the implementation transition phase and can be periodically
updated during the actual delivery of the service.
Once the NEA IT System is implemented, all the above IT operation and maintenance activities will have to
be performed regardless of the service delivery model utilized (cloud or on-premise). These services can
either be provided internally by NEA or outsourced to a third-party service provider.
Having these functions performed by NEA will require NEA to maintain resources with the skill sets needed
to maintain the application and hardware. Apart from continuous training, NEA’s IT must have an effective
succession plan to ensure that the necessary IT skills are retained in the organization in case of resignation
or retirement of IT personnel.
Outsourcing Services
An alternative is to outsource the IT operation and maintenance activities to a third-party service provider.
The advantage of outsourcing is that NEA no longer has to manage retention and continuous training of the
resources. Further, third-party service providers typically implement industry standard quality frameworks
applicable to such services such as Information Technology Infrastructure Library (ITIL), Capability Maturity
Model Integration (CMMI), Test Maturity Model Integration (TMMI), and Information Security Management
Systems (ISMS) that ensure delivery of quality services through adoption of international IT best practices.
Outsourcing these services would be a more strategic and cost-effective option for IT System Operation and
Maintenance. Outsourcing such services will allow NEA to focus on its core mandate of being an oversight
body to the ECs supporting total electrification, and their IT department can then focus on the more strategic
and high-value aspects of IT services, rather than on the day-to-day operation and maintenance of the NEA
IT System.
4.4.4 Exit Process

The Exit Process applies to the cloud delivery model where the organization’s data and/or application assets
are hosted in the cloud provider’s environment. This may also apply to similar models wherein the client
outsources/hosts their applications and data in a 3rd party vendor’s / provider’s facility or on leased / for-rent
servers. This refers to a clause in the service agreement with regard to the termination of service and the
mechanism for smooth turnover of the organization’s assets from the provider’s premises to the organization
for reasons such as service performance issue, contract term violation, closing of shop, transfer of service to
another provider, etc.
This is a critical aspect of a cloud service that should be agreed upon at the onset of the service. The Exit
Process must ensure smooth transition and minimal disruption to the client’s business during the service
termination phase. Preservation and transfer of data and/or application stored in the provider’s environment
are critical as these are important to ensure business continuity. A detailed process for extracting the
data/application from the cloud must be defined. The process must also specify in what format these will be
extracted to, in what medium these will be stored, who will be primarily responsible in performing and
22
The period when the system has just been implemented and is being stabilized)

providing support for such tasks and the expected processing time. The Exit Process must also specify a
clause ensuring the safe removal of the organization’s data upon successful transfer of custody, and a
written agreement that the cloud provider will not keep any copy of the data and use it for any purpose. The
organization must verify whether such terms are incorporated in the contract with the service provider.
5 Implementation Phase
5.1 NEA Preparation for Implementation

Technology implementation projects are a massive undertaking for any organization requiring commitment
and preparation for the organization to manage the project well, to be able to effectively work with the system
implementor, as well as to mitigate potential risks. This section lists the preparation tasks for NEA prior to the
system implementation projects.
1. Form a Project Team.
This should be composed of NEA resources and may include key EC participants. Prior to the
system implementation projects, the project team will be responsible for establishing NEA's
readiness for the implementation projects by planning for and leading implementation pre-requisite
activities such as those that will be discussed below.
During implementation, the project team will be highly involved in activities such as requirements
analysis and validation, testing, preparation of training materials and events. Due to the demands of
system implementation preparation and projects, there is a risk of high work load due from this team
– it is recommended to free them of usual NEA work for them to be able to work full-time on the
system implementation preparations and activities. Another option is to complement the team with
NEA-hired consultants (independent from the system implementor) that will be managed by NEA
resources.
The envisioned project team composition is presented in Annex 6.8 Implementation Project Team.
2. Align the requirements across all departments in NEA and with ECs.
The project team will conduct alignment meetings within NEA departments to standardize and unify
requirements in terms of level of detail and format. (i.e. standard format for statement of Income and
Expenses, Balance Sheet, etc.)
3. Establish review of operational policies and procedures as a regular (i.e., monthly) activity facilitated
by a particular department within NEA or by the project team. In preparation for system
implementation, this is expected to include policies on information security such as on passwords
and maintaining central repositories.
4. Establish processes to properly cascade policies and procedures. In addition, establish a centralized
entity to consolidate issues involving guidelines, policies and procedures. The stability of this
process will be valuable and useful to the need to cascade information and guidelines once the
application systems are available.
5. Conduct manpower capacity review and address identified gaps through training and/or outsourcing
which may include:
 IT skills assessment to ensure availability of resources to manage and administer
information systems (includes virtualization administration training, OS administration, DB
administration, web/portal administration, network administration, cloud administration. For a
full list, see Annex 6.7.3)
 Information Security
 Basic ITIL training to manage outsourced services
 Creative analysis which must be present in all key depts. (FIT)
6. Define Data Governance Process and form Data Governance Team (see Section 3.5)
7. Maintain Data Dictionary (see Section 3.4)

8. Define process for Operations and Maintenance Support (see Section 4.4.3) and communication of
those processes to all users
9. Prepare historical data to be uploaded into the system (see Section 3.6)
10. Review IT Asset Inventory and update as necessary. Though this should also be a regularly
conducted activity, it is critical to be done prior to the system implementation projects to identify
necessary purchases that if delayed may hold the implementation project timelines as well.
11. IT Facilities Upgrade. Aside from the inventory update, existing IT facilities' condition must also be
checked and set up for upgrade (may involve purchases) as necessary for all equipment to be ready
for the implementation of systems. NEA's network facilities are critical to the operations of systems
and should be prioritized in the conduct of this activity.
12. Prepare plans for Back Up and Disaster Recovery. For additional data security, back up and disaster
recovery plans will need to be established and ready by the time systems go live.

5.2 List of Implementation Activities
For NEA's guidance for the Implementation Phase, a high-level implementation schedule is presented below.
Figure 23: NEA IT Implementation Schedule

NEA Proj Team IT Impelementor WB
1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3
1 Establish a project team x
2 Implementation Planning x x
3 Bidding and Awarding x x
4 Orientation to System Implementation x
5 Implement Web Portal x x
6 Data Cleansing and Alignment (Optional) x
7 Historical Data Upload (Optional) x x x
8 Training/Cascade to NEA and EC End Users x
9 Implement BI System x x
10 Prepare policies, procedures and guidelines x
11 Training on Portal and BI Application Administration (for IT) x
12 Employee orientation relevant to system/s implemented x
Activities to be done by NEA and/or World Bank

Implementation activities to be done by NEA and Implementor
Post-implementation support to be provided by the Implementor
The schedule presented above aims to list and plot the estimated duration of the implementation activities for the IT systems of NEA as well as the
responsible stakeholder groups involved per activity. There will be one implementation project each for the BI system and the web portal. Additional activities
are included in the schedule to complement the implementation projects. All activities are discussed in further detail in the succeeding table. The estimated
project duration for web portal and BI System implementation is 13 months. This can still be shortened, depending on the commitment not just of the system
implementor, but also of NEA as several deliverables and responsibilities will be shared by both stakeholders.
An alternate condensed (more aggressive) implementation schedule is provided in Annex 6.9 NEA IT Implementation Schedule – Condensed.

Table 23: List of Implementation Activities
Duration
Activity Participants Description
(in months)
1. Establish a Project NEA 1 This is a team composed of point persons from
Team NEA that will work full time with the WB and
implementors prior to and throughout the
implementation projects to ensure that the
implementors are provided with what they need
from NEA to proceed with the projects smoothly
and without delay.
2. Implementation Project Team, 3 This is for planning and deciding on which dates
Planning World Bank should the pre-implementation and
implementation activities start and who should be
involved.
This would involve planning for and facilitating
the activities as enumerated in section 5.1 NEA
Preparation for Implementation.
3. Bidding and Awarding Project Team, 4 The process of selecting the
World Bank vendor/implementors to execute the activities of
the Implementation Phase.
4. Orientation to System NEA 2 Due to this being NEA's first system
Implementation implementation experience, it is recommended
that NEA obtain resources and training to be
familiar with the activities and requirements of
implementation projects.
5. Web Portal Project Team, 9 See 5.4 Web Portal Implementation for details.
Implementation Implementors
6. Data Cleansing and NEA 2 This activity is a pre-requisite to the historical
Alignment data upload. It will require an agreement on the
level of detail and scope of historical data to be
entered in the system.
7. Historical Data Upload Project Team, 2 See 3.6 Historical Data for details.
IT,
Implementors
8. Training/Cascading to NEA 1 In preparation for the deployment of the web
the ECs portal to the ECs, this activity is to ensure that all
ECs are knowledgeable of how to use the web
portal upon its launching.
9. BI System Project Team, 12 See 5.3 BI System Implementation for details.

Implementation Implementor
10. Prepare relevant NEA 5 Though this should be a regular activity (to
policies, procedures update) moving forward, it is essential to make
and guidelines revisions in policies, procedures and guidelines in
accordance to the changes in employees' tasks
and responsibilities brought about by the BI
system.
This also includes the initial preparation of the
systems' user manuals
11. Training for System Implementor 1 This involves the transfer of knowledge and
Administrators responsibility from implementors to NEA's system
administrators.

12. Employee Orientation NEA 2 An activity informing all NEA employees of the
developments in the organization's technology
landscape. This activity would include the
distribution of updated policies and guidelines in
accordance with the acquisition of BI technology.
5.3 BI System Implementation
Figure 24: Sample BI System Implementation Schedule
During the Discovery Phase, the prioritization for the identified BI analysis opportunities was explored based
on feedback from the ECs on which data is easy/difficult to provide and feedback from NEA on which
analysis is critical to their regular assessment of EC situations. However since it was reported that most
23 24
data can be provided by the ECs, phasing the implementation of the BI system is no longer necessary
and all of NEA's subject areas can be implemented within a period of eight (8) months. This grants NEA the
full benefit of having BI technology as soon as possible, which is through the analysis that can be done
across subject areas (i.e., combination of technical and financial analysis).
The diagram above presents the following activities within a BI implementation project. Note that though the
schedule of Post-Implementation Support could be beyond 3 months, the schedule is displayed as such to
focus on actual implementation activities.
 Project Initiation - setting up and introduction between the implementors and NEA, this includes the
project kick-off.
 Requirements Analysis - data requirements and report output details are validated and finalized in
preparation for the succeeding development efforts.
 Installation and Configuration of Software - initial setup of the system from unboxing to installation
and preliminary configuration. This may include the setup of environments (development, quality
assurance, production) and the user profiles of developers and testers.
 System Design - preparation of the final documentation for guidance of the development team
based on requirements finalized.
 Development
o ETL Development and Unit Test - preparation and deployment of scripts that will execute
the ETL processes. This includes unit testing to ensure that the outputs returned based on
the system design are as expected.
23
The only exceptions were feeder-level data and savings on WESM transactions.
24
In other organizations, implementation is broken into sequential phases wherein each phase is focused on a single data model (i.e.,
financial only).

o Front-End Development and Unit Test - preparation and deployment of output reports and
25
dashboards as agreed to be within the scope of the project .
o Integration Test - culminating tests conducted involving all system functions to ensure the
separately developed components of the system operate together smoothly.
 User Acceptance Test - implementor-facilitated tests conducted by the users to gain their
acceptance of the developed system
 Migration to Production – build-up of the production environment with the user-approved system
components
 Knowledge Transfer - training of trainers and key users
 Go Live - the start of a system's actual operation
 Post-Implementation Support/Warranty - a period immediately after go live wherein the implementor
remains available to fix bugs that may arise from system operations
5.4 Web Portal Implementation
Figure 25: Sample Web Portal Implementation Schedule
The activities within the web portal project implementation schedule are similar to the activities in the BI
system implementation. However, its execution will be quite different as the web portal will be developed
ground up as opposed to the BI system being a COTS solution. Each activity will be described below noting
the distinctions it would have from the BI system implementation, when applicable.
 Project Initiation - setting up and introduction between the implementors and NEA, this includes the
project kick-off.
 Requirements Validation - the project scope in terms of the data templates and system functionalities
are validated and finalized.
 Design - based on the finalized requirements, details for each such as fields and validation rules for
each template are validated and finalized in preparation for development. This activity overlaps with
the development effort because this project is estimated to be effective following an agile software
development method wherein users and analysts work closely with the developers following an
26
iterative approach in addressing the requirements .
The standardization of templates and data granularity (including line items in financial statements in
such as the balance sheet and income statement) required are essential to this phase. If not yet
accomplished by NEA, it may delay the implementation timeline.
 Development - preparation and deployment of scripts that will execute functions the system will be
composed of. Following an agile method, this is inclusive of testing.
25
Beyond the project implementation timeline and scope, the organization owning the BI system has full right to continue preparing their
own additional dashboards and reports as well as revising those that were prepared for them within the implementation project's
duration.
26
As opposed to the traditional Waterfall Development Methodology wherein project activities are sequential (not parallel) and will not
start until the previous activity is completed.

 Regression Testing - Testing conducted post-development to validate that the end-product is free of
issues
 Delivery Testing - Testing conducted by the analysts of an implementation team to ensure that the
requirements defined are met by the end-product
 User-Acceptance Testing - implementor-facilitated tests conducted by the users to gain their
acceptance of the developed system
 Training - Conducted to teach the users and trainers how to operate the system
 Historical Data Upload - Entry of historical data into the system for the BI system's reference. See
3.6 Historical Data for details
 Go Live - the start of a system's actual operation
 Post-Implementation Support/Warranty - a period immediately after go live wherein the implementor
remains available to fix bugs that may arise from system operations
5.5 High-level Change Management Plan

In the adaptation of technology, organizations give their full attention to the implementation of the solution.
However, technology implementation also requires a strategy designed towards awareness and
management of change to facilitate acceptance and commitment of all stakeholders. As such, a Change
Management Framework is presented in this section to support the recommended initiatives and
implementation strategies. These elements are critical as foundation for improvement as they provide a
basis which the technology can be applied. Without these elements, the stakeholders may only go back to
the ‘way it was before’ and not be able to maximize the investments on the new technology and process.
Change Management -- the systematic process of applying knowledge, tools and resources to lead an
organization through change with minimal distress and maximum acceptance – can help in ensuring that
changes will be integrated into the organization. This process requires a balance between processes, human
resources, structure and organizational culture.
The Change Management Framework for the success of the NEA IT System Implementation Project
involves the following key elements:
Figure 26: Change Management Framework

1. Awareness and Proper Communication of Change
When implementing a particular technology, organizational readiness, in terms of process
awareness, culture and values should be considered. Communication is crucial in making changes
in an organization effective which starts with awareness of change. Stakeholders, especially those
that will directly use the system should be aware of the change that is coming and must understand
the need for this change. Geographical set-up poses a challenge to this system implementation as
ECs are dispersed; and as for NEA, although considered as a governing organization, is an
organization separate from the ECs. Thus, a communication strategy and plan should be in place to
explain the rationale and the actual change to be implemented.
A well planned and consistent communication approach will address interests and even hesitations
of the different stakeholder groups.
2. Strong Leadership and Support from Management
Another element to a successful implementation of the change is the unwavering support from the
leaders of the organization. As observed, ECs and NEA have a culture that is anchored in respect
for their leaders. Management and leaders should also be advocates of the system and its purpose.
Their commitment, belief and reinforcement of the change could affect the disposition of the whole
organization. Their support and involvement will be the main drivers of the implementation and its
sustainability.
3. Culture of Commitment, Concern and Contribution Within the Organization

A culture of commitment, concern and contribution can lead to an optimal use of the system and
reap all the possible benefits.
 Commitment entails ownership and will result to compliance. Involving and communicating
to people also create opportunities for others to participate in planning and implementing the
changes, which spreads the organizational load. This creates a sense of ownership and
familiarity among the people affected. Acknowledgement of their accountability and
ownership of the project will encourage actions towards the success of the system.
 Concern for the achievement of the overall mandate should be fostered within the
organization. If this has been assimilated in their culture, there will be an understanding of
the importance of the data entered into the system and how this ultimately serves as a tool
to provide support to the ECs.
 A culture of contribution ensures that each member feels accomplished when they are able
to give value-adding inputs to their job and the overall goal. Now that information is at hand,
the motivation to contribute will push them to be more creative and innovative to further
investigate and analyze data.
This change in culture requires a series of interventions and planned activities to encourage
compliance to new processes and procedures. Staff and management should understand and
acknowledge the importance of each other’s contribution towards the improvement of the current
state and attainment of the mandate.
4. Training and Knowledge Requirements

Critical to a system implementation is an appropriate training plan to make sure that stakeholders
are able to execute the new processes correctly and be able to maximize the use of the new
technology.
The end-users must be trained on the necessary knowledge and skills to explore the application
efficiently and to make proper use of the functions and features of the new system. Such training
must cover the concepts and terminologies of the application and help the user to perceive benefits
that the application gives to routine work. The training should also adapt the learning environment in
ECs and NEA.
For technical users, the training programs should enable them to maintain and resolve issues related
to the data architecture, data model and other technical aspects of the system.

5. Key Result Areas and Success Factors
Critical success factors are key elements that need to be in place to measure the achievement of
project objectives. These should incorporate the overall mandate and objectives of the project.
Attainment of the success factors and key result areas should be reported stakeholders to provide
them with visible and tangible benefits as an effect of their effort in adapting to the change.
Change Management Plan

Below is a high-level change management plan that outlines activities to ensure the smooth integration of the
change into the organization.
Table 24: Change Management Plan

Activity Purpose and Objective Output Methodology and
Success Metrics
What are the Why is this needed? What is/are the
chronological activities/ deliverable/s or How will it be
steps to be expected results? delivered? What
undertaken? will make it
successful?
Project Kick-off
Project Kick-off: This survey aims to measure Change Readiness This will serve as
Change Readiness organizational readiness. Assessment Report. baseline measure.
Assessment The results can be used to
define change management
interventions needed by the
organization.
Project Planning
Accomplish detailed A detailed communication Communication plan and Success of

Communication plan that will plot the communication communication can
Strategy and Plan communication approach for collaterals be measured on the
the whole project and for receipt collaterals
each stakeholder group. and awareness of
stakeholders.
System Development
Project orientation to Orientation is a series of List of stakeholder -Not Applicable-

different stakeholder meetings with different concerns
groups stakeholder groups to orient
them of the purpose of
project, why it is needed and
the benefits expected from
the project. As no major
information system has yet
been implemented at NEA,
an orientation on System
Development/Implementatio
n Lifecycle shall also be
included to orient relevant
stakeholders project
implementation
methodology, particularly

emphasizing the
responsibilities of both the
system implementor and the
client organization in
ensuring timely completion
of each milestone in the
project plan.
Process Orientation Process Orientation is Process Documentation -Not Applicable-

conducted for end-users to
be aware of the new or
enhanced processes.
System Orientation System Orientation is System User Guide -Not Applicable-

conducted for end-users to
be familiar with the system.
Role Mapping This document will outline User Role Mapping List -Not Applicable-
the roles and responsibilities
of each end-user. This will
clarify changes in job
responsibilities and promote
accountability
Before Go-Live
End-User Training / Customized trainings are End-User Training Success can be

Caravan conducted to transfer presentation measured by
knowledge to end-users. attendance to
Training Guide
This aims to make end- trainings and count
users comfortable and of specific concerns
confident in using the raised during
system. implementation.
Distribution of Go-Live The Go-Live Kit aims to System Manual A notable

Kit provide assistance to users percentage of end-
Quick Reference Guide
during implementation. users have received
the Go-Live Kit.
After Go-Live
Establishment of Concerns and questions are Handholding Support Issues and concerns
Handholding Support expected when end-users Plan are resolved within
start to use the system. The agreed SLAs.
handholding support
structure aims to help users
during the first month of
implementation.
Measurement of results Information regarding the Accomplishment reports Achievement of

achievement of goals is reports over
important to acknowledge specified time
the effort and compliance of
users to the new system.

6 Annexes
6.1 Key Data Entry Templates
This section presents the key data entry templates designed for EC and NEA.
For more descriptions on the data entry templates, see Section 3.1 Data Entry Templates.
Legend:
Column header or field title, or a field for calculated or summarized data.

Gray-colored field
Field cannot be modified by the user.
Field is for data entry of the user whether for manual data entry (free text or
Yellow-colored field with defined format) or for data entry with defined list of values. Value in
these fields will be picked up by the Web Portal and saved in the system.
Field exists in the template but value in these fields will not be picked up by
White-colored field the Web Portal and will not be saved in the system. Applicable only for
Data Entry - EC - eICPM in Annex 6.1.4
6.1.1 Data Entry - EC - Monthly Data

 Template User: EC
 Process/es where this template is to be used: T4.2 Data Upload - Standard in Annex 6.3.3 and
T4.3 Data Upload – Special Handling in Annex 6.3.4.
 Description: This template includes fields for data required from the ECs on a monthly basis. The
template contains multiple worksheets. The template is to be uploaded into the Web Portal as a
single file.
Figure 27: Data Upload Details

Figure 28: NGCP Bill
Figure 29: Power Supply
Figure 30: Input and Output Energy

Figure 31: Interruption
Figure 32: Distribution Lines, Substation & Power Quality

Figure 33: Compliance to PDC

Figure 34: Compliance to PGC

Figure 35: BOD Meeting, Resolutions
BOARD'S MEETINGS / ATTENDANCE
Meetings
Regular Special Committees/Others
BOD Position Name of BOD Count of

Count of
Count of Regular Count of days Count of days Count of days Count of Committee Count of
Count of Special Meetings days
Meetings present absent present days absent Meetings / days present
absent
Others
President
Vice President
Secretary
Treasurer
Auditor
Member 1
Member 2
Member n
Independent Board Director
NEA Representative to the Board
Remarks
BOARD RESOLUTIONS - Create New

Board Board
NEA Action Board Resolution Board Resolution
Board Resolution Number Resolution Board Resolution Title Resolution Remarks
Required? Classification 1 Classification 2
Date Classification 3
BOARD RESOLUTIONS - Edit Information - NEA IDD User

Board Board
Board Resolution NEA Action Board Resolution Board Resolution NEA
Board Resolution Number Resolution Resolution
Title/Subject Required? Classification 1 Classification 2 Remarks
Date Classification 3
Figure 36: BOD Accounts Payable, Advances

STATUS OF POWER ACCOUNTS PAYABLE / CASH ADVANCES
Power Account Cash Advance
Name of BOD
Status Amount Status Amount
Figure 37: Connections - Delta

Are there changes in any
data this reporting month?
Count of Count of New Count of Removed Count of Count of

Count of New Connections
Geography Connections Class of Service Member-Consumers Member-Consumers Disconnections Reconnections
this Month
(Potential) this Month this Month this Month this Month
ELECTRIC COOPERATIVE
MONTH YEAR
Initial Count of
Sitio/Purok Geography Date Energized Fund Source Power Source
Connections

Figure 38: List of Employees - Delta
Are there changes in any
data this reporting month?
Name of Highest Level of
Tax Identification Number Date of Birth Mobile Number Email Address Degree Date of Hiring Employment Status Position Position Remarks Rank Salary
Employee Education
Figure 39: Salary
Figure 40: Complaints

Figure 41: Labor Management Issues - Delta
Figure 42: Institutional - Others

BAPA
Are there changes in any data
this reporting month?
Count of
Count of Members
Count of BAPA Organized Operational
(To Date)
BAPA (To Date)
MSEAC or Equivalent
District / Municipalities / Cities Name/s of Date of Term of Activities
Sector
Covered Members Appointment Office Taken
NEA Approved Per Diems Board

(Per Quarter) Resolution No.
Federated
ACCIDENTS
Name of Name of Type of ID of
Name of
Outsourced Member- Property/E Property/Eq Description of Cost of Action
Date of Accident Type of Accident Employee Extent of Damage
Employee Consumer/s quipment uipment Accident Damage Taken
Involved
Involved Involved Involved Involved
*Any of these 3 fields is mandatory if Type *This field is mandatory

of Accident = Person if Type of Accident =
Information Education Campaign:

EC Program/Issues Category EC Program/Issues Description Media/Info Materials Schedule/Duration
(ex:Radio Program, Fora/Symposia,

Newsletter, Recoreda etc)
ANNUAL GENERAL MEMBERSHIP ASSEMBLY (AGMA)

Date per EC By- Count of
Date of Conduct AGMA Venue/s Remarks
Laws Attendees
CORPORATE SOCIAL RESPONSIBILITY / IMAGE BUILDING

Included in
Board
CSR Project No. of Intended CSR Project CSR Project the latest
CSR Project Name Resolution
Category Beneficiary/ies Cost Description eICPM
No.
approved?
RETIREMENT PROGRAM
Actuarial Retirement
Estimated No. of Retiree/s for
Estimated No. of Retiree/s for the Year Fund Fund Manager
the Month
(Php)
Scoping
CAPACITY and Design of IT Systems Upgrade for NEA (Confidential)
BUILDING 92
Name of Training/Seminar Date of Trianing / Sponsoring
Name of Participant
Information Education Campaign:
EC Program/Issues Category EC Program/Issues Description Media/Info Materials Schedule/Duration
(ex:Radio Program, Fora/Symposia,

Newsletter, Recoreda etc)
ANNUAL GENERAL MEMBERSHIP ASSEMBLY (AGMA)

Date per EC By- Count of
Date of Conduct AGMA Venue/s Remarks
Laws Attendees
CORPORATE SOCIAL RESPONSIBILITY / IMAGE BUILDING

Included in
Board
CSR Project No. of Intended CSR Project CSR Project the latest
CSR Project Name Resolution
Category Beneficiary/ies Cost Description eICPM
No.
approved?
RETIREMENT PROGRAM
Actuarial Retirement
Estimated No. of Retiree/s for
Estimated No. of Retiree/s for the Year Fund Fund Manager
the Month
(Php)
CAPACITY BUILDING
Name of Training/Seminar Date of Trianing / Sponsoring
Name of Participant
Attended Seminar Agency
PATRONAGE CREDIT/REFUND
Formula Total Number of Recipients Total Amount Date Released
BY-LAWS AMENDMENT
NEA Action
AGMA Resolution Board Resolution Date of Submission
Date Approved Date Disapproved
EXTERNAL AUDIT
External Audit this reporting
month?
COVERING PERIOD TO
PUBLISH DATE OF AUDIT REPORT
EXTERNAL AUDIT RATING
CUSTOMER SERVICE STANDARD

Customer Service Parameter Compliance
1. Processing/Approval of applications for service connection
Within day/s upon receipt of application
(with complete requirements)
2. Service-drop connection Within day/s upon payment of fees
3. Restoration of service after line fault on the secondary side, Within hour/s upon on-site arrival
4. Response time on Consumer Complaints (Billing, Payment and Within hour/s after receipt of complaints
5. Timeframe in informing Customer on scheduled power Within day/s before scheduled interruption
6. Response time to emergency calls Within hour/s after receipt of call
hour/s after settlement of amount due/compromise
7. Response time to reconnection of service due to disconnection Within
agreement
INFORMATION, EDUCATION & COMMUNICATION TECHNOLOGY

Technology
Information, Education & Communication Technology Parameter
Exists?
Website
Hotline for Complaints
Online Tellering
Short Messaging System
Automated Meter Reading
Billing & Collection (MRBC)

Figure 43: Income Statement
Income Statement
To Date as % of Total
This Month Last Month To Date Operating Revenue
1. Uti l i ty Opera ti ng Revenue

1.1 Opera ti ng Revenues
1.1.1. Pa s s Through Cha rges
1.1.1.1 Genera ti on
1.1.1.2 Tra ns mi s s i on
1.1.1.3 Uni vers a l Cha rge
1.1.1.4 Sys tem Los s Cha rge
1.1.2. EC Revenue
1.1.2.1 Di s tri buti on
1.1.2.2 Suppl y
1.1.2.3 Meteri ng
1.1.3 Other Cha rges
1.1.3.1 Cha rge for RFSC
1.1.3.2 Li fel i ne Subs i dy
1.1.3.3 FIT-ALL
1.1.4. EC-Speci fi c Cha rges
1.2 Other Opera ti ng Revenue (N-1)
1.3 Tota l Opera ti ng Revenue
2. Power Cos t
2.1 Power Producti on Cos t
2.11 Fuel & Oi l
2.12 Others
2.2 Purcha s ed Power
2.3 Tota l Cos t of Power Purcha s ed
3. Tra ns mi s s i on Expens es
4. Di s tri buti on Expens es
4.1 Opera ti on
4.1.1 Opera ti ons Supervi s i on a nd Engi neeri ng
4.1.2 Sta ti on Equi pment
4.1.3 Overhea d Li ne Expens es
4.1.4 Street Li ghti ng & Si gna l Expens es
4.1.5 Meter Expens es
4.1.6 Cons umer Ins ta l l a ti on Expes es
4.1.7 Rents
4.1.8 Mi s cel l a neous Di s tri buti on-Opera ti ons Expens es
4.2 Ma i ntena nce
4.2.1 Ma i ntena nce - Supervi s i on & Engi neeri ng
4.2.2 Ma i ntena nce - Overhea d Li nes
4.2.3 Ma i ntena nce - Sta ti on Equi pment
4.2.4 Ma i ntena nce - Li ne Tra ns formers
4.2.5 Ma i ntena nce - Street Li ghti ng & Si gna l Sys tem
4.2.6 Ma i ntena nce - Meters
4.2.7 Ma i ntena nce - Genera l Pl a nt
4.3 Tota l Di s tri buti on Expens e
5. Cons umer's Account Expens e
5.1 Supervi s i on
5.2 Meter Rea di ng Expens es
5.3 Cons umer Records & Col l ecti on Exp.
5.4 Uncol l ecti bl e Account
5.5 Informa ti ona l & Ins t. Adverti s i ng Expens es
5.6 Cons umer's PPD
5.7 Mi s cel l a neous Cons umer Accounts
6. Admi ni s tra ti ve a nd Genera l Expens e
6.1 Admi ni s tra ti ve Sa l a ri es
6.2 Offi ce Suppl i es & Expens es
6.3 Outs i de Servi ces Empl oyed
6.4 Property Ins ura nce
6.5 Injuri es & Da ma ges
6.6 Empl oyee Pens i on a nd Benefi ts
6.7 Fra nchi s e Req. a nd Reg. Commi s s i on
6.8 BOD Per Di em a nd Al l owa nce
6.9 Rents
6.10 Ma i ntena nce of Offi ce & Gen. Pl a nt
6.11 Ta xes on Property
6.12 Offi cers Al l owa nces & Benefi ts
6.13 Tra vel
6.14 Tra i ni ng
6.15 Mi s cel l a neous Genera l Expens es

7. Tota l Opera ti ng & Ma i ntena nce Expens e
8. Opera ti ng Ma rgi n
9. Depreci a ti on a nd Amorti za ti on Expens e
10. Interes t Expens e
11. Net Opera ti ng Ma rgi n
12. Non-Opera ti ng Revenue
13. Non-Opera ti ng Expens es
14. Extra ordi na ry Items
15. NET MARGIN/(LOSS) before RFSC & UCS
16. LESS: MCC for CAPEX & UCS
17. NET MARGIN/(LOSS) a fter RFSC & UCS
 The line items of the Income Statement and Balance Sheet have to be standardized during system
implementation.

Figure 44: Balance Sheet
BALANCE SHEET
ASSETS AND OTHER DEBITS LIABILITIES AND OTHER CREDITS

UTILITY PLANT EQUITIES AND MARGINS
1. Gros s Uti l i ty Pl a nt (Book Va l ue) 44. Members hi p
2. Appra i s a l Increment 45. Dona ted Ca pi ta l
3. Accumul a ted Depreci a ti on (Book Va l ue) 46. Cons . Cont. to Dept. Svc.
4. Accumul a ted Depr. (Appra i s a l Increment) 47. Contr. i n Ai d of Cons t.
5. Net Uti l i ty Pl a nt - 48. Reva l ua ti on Increment
6. Cons t. Work i n Progres s 49. Other Ca pi ta l Accounts
7. Tota l Uti l i ty Pl a nt - 50. Appropri a ted Ma rgi ns
OTHER PROPERTY & INVESTMENT 51. Una ppropri a ted Ma rgi ns
8. Net Non-Uti l i ty Property - 51.1 Current Yea r
8.1 Non-Uti l i ty Property (Book Va l ue) 51.2 Pri or Yea rs
8.2 Accumul a ted Depreci a ti on (Book Va l ue) 51.3 Tota l Una ppropri a ted Ma rgi ns -
9. Inves tment i n As s oc. Orga ni za ti on 52. Tota l Equi ti es a nd Ma rgi ns -
10. Other Inves tment LIABILITIES
11. Res tri cted Funds 53. Long Term Debt - Cons tructi on
11.1 Members hi p Funds /Meter Depos i t 54. Long Term Debts - WB RERP
11.2 Reti rement Fund 55. Long Term Debts - Reha bi l i ta ti on
11.3 Si nki ng Fund For Rei nves tment 56. Long Term Debt - Expa ns i on
11.4 Subs i dy/Gra nts 57. Long Term Debt - Logi s ti ca l
11.4 Tota l Res tri cted Funds - 58. Long Term Debt - SLRP
12. Inves tment i n Pol es Procurement 59. Other Long Term Debt
13. Tota l Other Property a nd Inves tment - 60. Long Term Debt - Res tuctured Loa n
CASH & TEMPORARY INVESTMENT 61. Long Term Debt - Re Loa n
14. Ca s h i n Ba nk
14.1 Ca s h i n Ba nk (Genera l Fund) 62. Cons umers Depos i t
14.2 Ca s h i n Ba nk - (Loa n Funds ) 63. Tota l Long Term & Short Term Debts -
14.3 Ca s h i n Ba nk - Others CURRENT AND ACCRUED LIAB.
17. Ca s h on Ha nd 64. Notes Pa ya bl e
18. Worki ng Funds 65. Accounts Pa ya bl e - Power
19. Tempora ry Ca s h Inves tment 66. Accounts Pa ya bl e - Others
20. Tota l Ca s h - 67. Accounts Pa ya bl e - NEA
NOTES & ACCOUNTS RECEIVABLE 68. Accounts Pa ya bl e - Phi l reca
21. Notes Recei va bl e 68. Due to Other RECS
22. Cons . Accounts Recei va bl e - Energy a nd RFSC - 69. Ta xes Accrued
22.1 Cons .Accounts Recei va bl e-Energy
22.2 Cons . Accounts Recei va bl e-RFSC
23. Al l owa nce for Uncol l ecti bl e Accounts 70. Interes ts Accrued - Long Term Debt
24. Net Cons . Accts . Rec. - Energy - 71. Interes ts Accrued - Short Term Debts
25. Cons . Accounts Rec. - Others - 72. VAT Pa ya bl e
25.1 Cons umers ' Accounts Recei va bl es - Uni vers a l Cha rge 73. Ma tured Short Term Debts
25.2 Cons umers ' Accounts Recei va bl es - VAT GENCO 74. Ma tured Interes t Pa ya bl e
25.3 Cons umers ' Accounts Recei va bl es - VAT NGCP 75. Wi thhol di ng Ta x Pa ya bl e
25.4 Cons umers ' Accounts Recei va bl es - VAT Di s tri buti on 76. Tota l Current & Accrued Li a bi l i ti es -
25.5 Cons umers ' Accounts Recei va bl es - Bus i nes s Ta xes OTHER CURRENT & ACCRUED LIAB.
25.6 Cons umers ' Accounts Recei va bl es - Fra nchi s e Ta xes 77. Mi s c. Current & Acc. Li a bi l i ti es
26. Tota l Cons . Accts . Rec. - DEFERRED CREDITS
27. Other Accts . Rec. 78. Cons . Adva nces for Cons tructi on
28. Adva nces to Offi cers a nd Empl oyees 79. Cons umer Energy Pa yment
29. Due from other RECS 80. Other Deferred Credi ts
30. Tota l Notes & Accts . Rec. - 81. Tota l Deferred Credi ts -
MATERIALS & SUPPLIES RESERVES
31. Ma teri a l s a nd Suppl i es - Fuel Stock 82. Res erves
32. Ma teri a l s a nd Suppl i es - El ectri c
33. Ma teri a l s a nd Suppl i es - Hous ewi ri ng
34. Ma teri a l s a nd Suppl i es - Others
35. Offi ce Suppl i es
36. Stores Expens e Undi s tri buted
37. Tota l Ma teri a l s a nd Suppl i es -
OTHER CURRENT AND ACCRUED ASSETS
38. Prepa yments
39. Mi s c. Current a nd Accrued As s ets
40. Tota l Other Current a nd Accrued As s ets -
41. Reti rement Work i n Progres s -
42. Other Deferred Debi ts
43. Tota l Deferred Debi ts -
TOTAL ASSETS AND OTHER DEBITS - TOTAL LIAB. & OTHER CREDITS -

Figure 45: Power Accounts Payable
Schedule of Power Accounts Payables
INTEREST,
CURRENT RESTRUCTURED OVERDUE
PENALTIES & TOTAL STATUS/REMARKS
ACCOUNT ACCOUNT ACCOUNT
PARTICULARS SURCHARGES
A. POWER SUPPLIERS
1. PSALM
2. NPC
3. NPC - SPUG
4. AES
5. SMEC
6. MASINLOC POWER PARTNER & LTD.
7. FIRST GEN
8. APRI
9. NGCP
10. SNAP - MAGAT
11. GREEN CORE (GCGI)
12. WESM
13. DMCI MASBATE POWER CORP.
14. GLOBAL
15. BIP CORE
16. TRANS ASIA
17. NORTHWIND
18. TEAM ENERGY
B. RES
1. GN POWER
B. VAT

Figure 46: Rates
Unbundled Rate Charges
LOW VOLTAGE HIGH VOLTAGE
RESIDENTIAL
C/Ind/SL/PB Industrial
Generation Charges
Generation System Charge Php/kWh
Franchise & Benefit to Host Communities
Transmission Charges
Demand Charges Php/kW
Transmission System Charge Php/kWh
System Loss Charge Php/kWh
Distribution Charges
Demand Charges Php/kW
Distribution System Charge Php/kWh
Supply Charges
Retail Customer Charge Php/cust/mo
Supply System Charge Php/kWh
Metering Charges
Retail Customer Charge P hp/meter/mo
Metering System Charge Php/kWh

RFSC/MCC Php/kWh
Universal Charges
Missionary Electrification Charge
Environmental Share/ Watershed
NPC Stranded Contract Cost
Lifeline Subsidy Php/kWh
Franchise Tax Php/kWh
Feed-in Tariff Allowance (FIT - ALL) Php/kWh
Expanded Value Added Tax
EVAT on Generation Cost
EVAT on Transmission Cost
EVAT on System Loss - Generation
EVAT on System Loss - Transmission
EVAT on Distribution (Fixed Charges)
EVAT on Distribution per Kwh
Fixed Charges per bill
Power Rate per KWH

Conumption Range Lifeline Discount % Lifeline Rate
Net of applicable discount
from Generation,
Transmission, System Loss,
Distribution, Supply and
Metering Charges.
Senior Citizen Discount/Subsidy

Senior Citizen Discount (5%)
Senior Citizen Discount (Center)
Senior Citizen Subsidy

Figure 47: Cash Flow
Statement of Cash Flows
Approved Budget Budget Balance
Account Name This Month To Date Budget Balance
for the Year (%)
INTERNAL CASH GENERATION
1. Collection from Customers A/R
1.a. From Energy Sales
1.b. From RFSC
1.c. From Universal Charge
1.d. From VAT
2. Non-Operating Revenue
2.a. Reconnection & Other Fees
2.b. Interest Income
2.c. Collection from Non-Operating Revenue
3. Other Receipts
4. Loan from NEA/Banks/Other Fin. Institutions
5. Subsidy
Total
CASH FOR OPERATIONS
1. Cost of Power
2. Non-Power Cost -
2.a. Salaries & Wages
i. Payroll
ii. Others
2.b. SSS/Medicare/ECC/Pag-Ibig
2.c. Employee Benefits
2.d. Utilities
2.e. Office Materials & Supplies
2.f. Travel
2.g. Transportation
2.h. Repairs & Maintenance
2.i. Directors' Per Diems
2.j. Allowances/Representation
2.k. Outside Professional Service
2.l. Seminars/Trainings
2.m. Institutional Activities
2.n. Insurance/Registration
2.o. Sundries
Property Tax
Sub-Total
CASH FOR DEBT SERVICE (CURRENT & LONG-
TERM)/OTHER USES
1. NEA/Bank/Other Payables
2. Payable to Power Suppliers
3. Universal Charge
4. VAT Payable
Sub-Total
CASH FOR CAPITAL EXPENDITURES
CASH FOR SINKING FUNDS
CASH AFTER SINKING FUNDS
Add: Cash Balance, Beginning
CASH BALANCE, END

Figure 48: Accounting of Reinvestment Fund for Sustainable CAPEX (RFSC)
Figure 49: Cash Advance

Figure 50: Accounting of Universal Charge
UC COLLECTED UC REMITTED
AMOUNT UC - SBR NO. OR NO. AMOUNT
MONTH ME EC SCC ME EC SCC ME EC SCC ME EC SCC
Previous Year Month 1

Current Year Month 1
Figure 51: Prompt Payors
Figure 52: Delinquent Customers

Figure 53: Schedule of Amortization Part 1 of 2
Figure 54: Schedule of Amortization Part 2 of 2
6.1.2 Data Entry - EC - Create New, Edit List of Values

 Process/es where this template is used: Master Data Maintenance in Annex 6.3.2
 Description: This template is for new list of values from ECs that are only created after specific
events such as signing of a Power Supply Agreement, installation of a substation, and election or
appointment of a Board of Director. If data for the reporting month are associated with these new
data, these data should be uploaded using this data entry template prior to the upload of data
through the Data Entry - EC - Monthly Data (Annex 6.1.1). Data validations will be configured if,
for example, the power supplier being reported in the Data Entry - EC - Monthly Data exists in the
database for that EC. If the power supplier does not exist for the EC, the system will trigger an
error and will reject the Data Entry - EC - Monthly Data template being uploaded by the EC.
Figure 55: Power Supplier Agreement - Create New, Edit

Figure 56: Substation - Create New, Edit
Figure 57: BOD
New BOD or Edit Tax Identification Home

BOD Name Cellphone Number Email Address Date of Birth Age
Existing BOD? Number Address
District /
Number of Elected / Total No. of Voter's End Date of Reason for End of
Start Date of Term No. of Voters Municipalities / BOD Position
Term of Office Appointed? Years as BOD Turnout Term Term
Cities Covered

Documentary With Spouse Holding Was a candidate in With a relative
Terminated
Highest Level of Member of Good of Good SG 16 or Higher the last preceding Date of last within 4th Degree Financial
Degree Position from Previous Remarks
Education Standing Moral Appointive or national or local preceding election of Consanguinity Interest
Employment?
Character Elective? election? of Affinity?
6.1.3 Data Entry - NEA - Create New, Edit List of Values

 Template User: NEA
 Process/es where this template is used: Master Data Maintenance in Annex 6.3.2
 Description: This template is for new list of values from NEA created, for example, because of
new/updated policies and regulations, new BI Analysis and new dimensions.
Figure 58: Brand - Create New
Figure 59: Power Supplier - Create New, Edit

27
Figure 60: Power Plant - Create New, Edit
6.1.4 Data Entry - EC - eICPM

 Process/es where this template is used: T4.2 Data Upload - Standard in Annex 6.3.3
 Description:
 The existing outputs of the eICPM tool (such as the DDP-General Provision, DDP-Demand)
shall be used as data entry templates for eICPM-related data to be uploaded into the NEA IT
System. No change is required in these existing templates. However, on data upload, the
system will only pick up and save in the database values from selected fields (such as
forecasted data). These fields are highlighted in yellow. Figure 6 DDP-General Provision is
an example of this template.
 The Data Entry - EC - Project Details (Figure 7) is a new template related to details coming
from the eICPM. It may be considered that this template be automatically be accomplished
by the eICPM tool using its existing functionality is a word processor.
27
It should be noted that DOE maintains a list of existing power plants. NEA should consider using this list and align with DOE in terms
of data maintenance relevant to power plants in the NEA IT System.

Figure 61: DDP - General Provision
1. Name of Utility in Full CAMARINES SUR I ELECTRIC COOPERATIVE, INC. (CASURECO I) DDP - GENERAL PROVISION
2. ERC/NEA Authority/License No./R.A.# # 021
3. Brief Description of Franchise Area: (Province/s and Municipality/ies covered; Area in Sq. Km.)
Province/s and Municipality/ies Covered CASURECO I has a coverage area of 10 towns – 4 from the first congressional district, namely, Ragay, Sipocot, Lupi and Cabusao; 5 from the second congressional district, namely, Libmanan, Pamplona, Pasacao, San F
Area in Sq. Km 1,528.97
Franchise Population 414,491
(Attach additional sheet if necessary)
4. Grid 100MVA Naga Substation
5a. Brief description of methodology used in load forecasting and supply expansion plan:
Load Forecasting is based on the models provided by NEA during the Biennial e-ICPM Workplan.

5b. Brief description and sources of assumptions:

Historical Forecast
Forecast/Planning Results
2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
6. Number of Barangays in Franchise 309 309 309 309 309 - - - - - - - - - -

6.a Number of Energized Barangays (On-Grid) 287 287 287 287 287
6.b Number of Energized Barangays (Off-Grid)
6.c Number of Waived Barangays
22 22 22 22 22
(Serviced by Alternative Service Provider)
7. Number of Households in Franchise 93,840 95,283 96,649 98,017 99,386 - - - - - - - - - -
7.a Number of Energized Households (On-Grid) 57,051 60,054 62,938 66,085 69,389
7.b Number of Energized Households (Off-Grid)
8. Number of Customer Connections
Residential 48,598 50,494 53,467 56,967 60,765 - - - - - - - - - -
On-grid 48,598 50,494 53,467 56,967 60,765
0ff-grid
Commercial 2,329 2,328 2,293 2,439 2,601 - - - - - - - - - -
On-grid 2,329 2,328 2,293 2,439 2,601
0ff-grid
Industrial 54 55 56 59 63
On-grid 54 55 56 59 63
0ff-grid
Others 3,868 3,931 4,080 4,347 4,635 - - - - - - - - - -
Public Bldgs 791 805 833 888 947 - - - - - - - - - -
On-grid 791 805 833 888 947
0ff-grid
Street Lights 3,067 3,116 3,237 3,449 3,678 - - - - - - - - - -
On-grid 3,067 3,116 3,237 3,449 3,678
0ff-grid
Others (i.e., irrigation, etc.) 10 10 10 10 10 - - - - - - - - - -
On-grid 10 10 10 10 10
0ff-grid
TOTAL Number of Customer Connections 54,849 56,808 59,896 63,812 68,064 - - - - - - - - - -
8a. Number of Large Load Customers
1 MW and above
750 kW up to 999 kW
9a. Number of Barangays in the Franchise Area 309 309 309 309 309
9b. Number of Households in the Franchise Area 93,840 95,283 96,649 98,017 99,386
9c. Number of Sitios in the Franchise Area 653 653
Figure 62: DDP - Demand

Historical Forecast DDP - DEMAND
Forecast/Planning Results Units
2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
10. ENERGY REQUIREMENT

10a. Electricity Consumption (On-grid)
Direct Sales To Customers (1a)
Residential MWh 27,138 29,442 33,515 36,292 33,745
Commercial MWh 7,905 6,784 7,423 8,038 7,474
Industrial MWh 1,874 2,095 2,236 2,422 2,252
Others MWh 3,530 3,714 4,131 4,069 3,791 - - - - - - - - - -
Public Bldgs MWh 2,524 2,729 3,042 2,924 2,721
Street Lights MWh 618 635 653 708 658
Company Use: Company/Office/ Housing MWh 278 286 335 328 311
Company Use: Utility's Station use MWh
Others (Direct sale or Large Load ) MWh 109 65 101 109 102
On-Grid: Direct Sales to Customers MWh 40,446 42,035 47,306 50,822 47,262 - - - - - - - - - -
10b. Electricity Consumption (Off-Grid)

Direct Sales To Customers (1b)
Residential MWh
Commercial MWh
Industrial MWh
Others MWh - - - - - - - - - - - - - - -
Public Bldgs MWh
Street Lights MWh
Company Use: Company/Office/ Housing MWh
Company Use: Utility's Station use MWh
Others (Direct sale or Large Load ) MWh
Off-grid: Direct Sales to Customers MWh - - - - - - - - - - - - - - -
10c. Electricity Consumption (Franchise)

Direct Sales To Customers 1: (1a+1b)
Residential MWh 27,138 29,442 33,515 36,292 33,745 - - - - - - - - - -
Commercial MWh 7,905 6,784 7,423 8,038 7,474 - - - - - - - - - -
Industrial MWh 1,874 2,095 2,236 2,422 2,252 - - - - - - - - - -
Others MWh 3,530 3,714 4,131 4,069 3,791 - - - - - - - - - -
Public Bldgs MWh 2,524 2,729 3,042 2,924 2,721 - - - - - - - - - -
Street Lights MWh 618 635 653 708 658 - - - - - - - - - -
Company Use: Company/Office/ Housing MWh 278 286 335 328 311 - - - - - - - - - -
Company Use: Utility's Station use MWh - - - - - - - - - - - - - - -
Others (Direct sale or Large Load ) MWh 109 65 101 109 102 - - - - - - - - - -
Total: Direct Sales to Customers MWh 40,446 42,035 47,306 50,822 47,262 - - - - - - - - - -

Figure 63: DDP - Supply Indicative
Supply Forecast
Supply Expansion Plan
2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
13a. Utility Owned Power generating Facilities
Name:
Status:
Fuel Requirement (liters, tons, etc.)
Installed Capacity KW
Net Dependable Capacity KW
Net Production MWH
Name:
Status:
Net Production MWH
Name:
Status:
Net Production MWH
Name:
Status:
Net Production MWH
Sub Total (Utility-Owned RE-based Generating Facility only)

Installed Capacity KW - - - - - - - - - -
Net Dependable Capacity KW - - - - - - - - - -
Net Production MWH - - - - - - - - - -
Total (Utility Owned Power Generating Facilities)

Installed Capacity KW - - - - - - - - - -
Net Dependable Capacity KW - - - - - - - - - -
Net Production MWH - - - - - - - - - -

Figure 64: DDP - DDP
Forecast/Planning Units Historical Forecast
Results 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
Subtransmission Facilities: (Acquisition and Expansion)
15a. Subtransmission lines (CUMULATIVE TOTAL) (ANNUAL)
Voltage, 230kV ckt-km
Voltage, 138kV and less than
ckt-km
230kV
ckt-km
138kV
ckt-km
115kV
41 41 41 41 41 - 78 - - - - 45 - - -
Subtransmission Facilities: (Replacement and Rehabilitation)
15b. Subtransmission lines (CUMULATIVE TOTAL) (ANNUAL)
Voltage, 230kV ckt-km
ckt-km
230kV
ckt-km
138kV
ckt-km
115kV
- - - - - - - - - - - - - - -
Distribution Facilities: (Acquisition and Expansion)
15c. Distribution lines (CUMULATIVE TOTAL) (ANNUAL)
Voltage, 34.5kV and less than
ckt-km
69kV
ckt-km
34.5kV
ckt-km
13.8kV (3 Phase)
(V Phase) ckt-km
(1 Phase) ckt-km
1,257 1,259 1,302 1,306 1,326 - - - - - - - - - -
Distribution Facilities: (Replacement and Rehabilitation)
15d. Distribution lines (CUMULATIVE TOTAL) (ANNUAL)
ckt-km
69kV
ckt-km
34.5kV
ckt-km
13.8kV (3 Phase)
(V Phase) ckt-km
(1 Phase) ckt-km
- - - - - 8 26 - - - - - - - -
16a. Substation Capacity, MVA (Additional) (CUMULATIVE TOTAL) (ANNUAL)
Transformer Capacity, 100 and
MVA up
No. of Units
MVAless than 100
No. of Units
MVAless than 50
No. of Units
MVAless than 25
No. of Units
Transformer Capacity, less MVA
than 10
No. of Units
Total Capacity MVA 20 20 20 20 20 - 5 - - - - 5 - - -
16b. Substation Capacity, MVA (Uprating) (CUMULATIVE TOTAL) (ANNUAL)

MVA up
No. of Units
MVAless than 100
No. of Units
MVAless than 50
No. of Units
MVAless than 25
No. of Units
Transformer Capacity, less MVA
than 10
No. of Units
Total Uprating MVA - - - - - - - - - - - - - - -
Figure 65: Projects

Project Planned Start Planned End Actual Start Planned
Project ID CAPEX/Non-CAPEX Type ID Project Type Project Description Date Date Date Actual End Date Particulars - Val
nd Actual Start Planned Actual Particulars - Project Budget Actual Project

Date Actual End Date Particulars - Value Value Particulars UOM Impact Project Status Funding Source in Peso Cost in Peso Notes/Remarks
6.1.5 Data Entry - NEA - Audit Findings
 Template User: NEA


 Description: Data required in this template is for BI Analysis 05-02.
Figure 66: Audit Findings
6.1.6 Data Entry - NEA - BOD, GM Performance Rating

 Description: This template is to enter the performance ratings of the BOD and GM required as a
criteria in the KPS/KPGS rating
Figure 67: BOD and GM Performance Rating
BOD Performance Rating

BOD Position Name of BOD Performance Rating
President Name
Vice President Name
Secretary Name
Treasurer Name
Auditor Name
Member 1 Name
Member 2 Name
Member n Name
Independent Board Director Name
NEA Representative to the Board Name
GM Performance Rating
Name of GM Name
GM Performance Rating Parameters Performance Rating

Relationship with the Board of Directors
Relationship with EC Employees
Management of Linkages
Innovativeness
Personality

6.1.7 Data Entry - Price Index
 Template User: EC and NEA
 Description: This is the template to collect unit prices from EC. The same template shall be used
by NEA when uploading the defined NEA price per item into the system. The system shall
validate if the Unit Price being uploaded is from EC or NEA depending on the user log in details.
Data required in this template is for BI Analysis 01-02 and 01-09.
Figure 68: Price Index

6.2 Data Dictionary
Term Description Data Format Attribute/ Origin List Of Values

Measure/
Dimension
% Change Deviation % difference between % Change in System Loss and Average % Change in Numeric Measure Calculated
System Loss Across Period n
Formula:
System Loss Change Deviation = (% Change in System Loss) - (Average %
Change in System Loss)
% Change in Input % change of Input Energy in one period compared to the previous period Numeric Measure Calculated
Energy
% Change in Output % change of Output Energy in one period compared to the previous period Numeric Measure Calculated
Energy
% Change in System % change of System Loss in one period compared to the previous period Numeric Measure Calculated
Loss
Formula:
% Change in System Loss = ([(Current Period System Loss) - (Last Period
System Loss)] / [(Current Period System Loss)])*100%
% of Lifeline Percentage Measure Calculated
Connections
% Status of Compliance % compliance to a code Percentage Measure Calculated x%, No Input
Formula:
% Status of Compliance = ((Count of Applicable Parameters Complied With)
/ (Count of Applicable Parameters)*100%
If Count of Applicable Parameters = 0, then "No Input"
Accounts Payable Accounts payable of an EC to creditors, suppliers, vendors and other parties Numeric Dimension Entered
Accounts Payable - An indicator that states the ability of the EC to pay its maturing power Alphanumeric Dimension Configured Current, Restructured-Current, In
Power - Indicator accounts to GENCOs, NGCP and PEMC including VAT Arrears
Formula:
If Cash General Fund >= (Ave. Power Cost for the last 12 months) + (Ave.
Non-Power Cost for the last 12 months), then Compliant.
If Cash General Fund < (Ave. Power Cost for the last 12 months) + (Ave.
Non-Power Cost for the last 12 months), then Non-compliant.
Source:
Parameters and Standards in the Assessment of the EC Financial Condition
and Operational Performance
Action Taken Action taken by the EC on an accident Alphanumeric Attribute Entered
Activities Undertaken Activities undertaken related to MSEAC or equivalent Alphanumeric Attribute Entered
Actual Dispatched - Actual energy dispatched by a power supplier Numeric Attribute Entered
Energy

Actual Dispatched - Actual maximum power dispatched by a power supplier Numeric Attribute Entered
Maximum Power
Actual Dispatched Actual dispatched energy of a power supplier Numeric Measure Entered
Energy
Actuarial Retirement Numeric Attribute Entered
Fund (Php)
Adjustments - RFSC Adjustments made to the RFSC account Numeric Dimension Entered
Administrative Expense This refers to expenses involved in utility administration such as Numeric Dimension Calculated 1 Administrative Salaries
office supplies, travel, training, salaries and allowances. 2 Office Supplies & Expenses
3 Outside Services Employed
4 Property Insurance
5 Injuries & Damages
6 Employee Pension and Benefits
7 Franchise Req. and Reg.
Commission
8 BOD Per Diem and Allowance
9 Rents
10 Maintenance of Office & Gen. Plant
11 Taxes on Property
12 Officers Allowances & Benefits
13 Travel
14 Training
15 Miscellaneous General Expenses
AGMA Resolution AGMA resolution related to by-laws amendment Alphanumeric Attribute Entered
AGMA Venue/s Venue/s where the AGMA was conducted Alphanumeric Attribute Entered
Allowance for Numeric Measure Entered
Uncollectible Accounts
Amount Amount of Collective Bargaining / Negotiation Agreement Numeric Attribute Entered
Annual Contracted Annual contracted capacity as indicated in the Power Supply Agreement Numeric Attribute Entered
Capacity
Annual Contracted Annual contracted energy as indicated in the Power Supply Agreement Numeric Attribute Entered
Energy
Asset Data Complete in A Yes/No indicator if asset data in System Loss Segregation Calculation tool Alphanumeric Dimension Defined Yes
System Loss is complete or not. Note that only asset data being used for completed No
Segregation Calculation projects (where connections have been energized) should be included in the
Tool as of Last Update? calculation tool.
Asset Turnover An indicator of how much the EC earns from its assets. Simulations of asset Numeric Measure Calculated
turnover may also be used in assessing potential asset-expansion projects.
Formula = Net Sales/Average Net Utility Plant
Assets Assets of an EC ranging from cash and temporary investments to accrued Numeric Dimension Calculated Cash and Temporary Cash
assets and deferred debits etc. Investment, Notes and Accounts
Receivable, Materials and supplies,
Accrued Assets, Deferred Debits,
Other Property and Investment
Attendance Status Present or Absent status of a BOD in a meeting Alphanumeric Dimension Defined Present, Absent

Audit Finding Applicable only if Audit Type = NEA Alphanumeric Dimension Defined Operating Performance - Comparative
Classification Analysis
Financial Condition
NEA Loan and Utilization of NEA

Subsidy Releases
Loans from Other Financial Institutions
Consumer Accounts
Rates
Collections
Pilferage Recoveries
Other Income
Salaries
Benefits and Allowances
Cash Advances to Officers and
Employees
Retirement
Power Supplier Accounts

Power Supply Agreements
Procurement of Materials, Equipment,
Services
Inventory of Materials and Equipment
Construction
Accounting and Internal Control

Systems
- Cash on Hand
- Cash in Bank
- Check for Disbursements
- Internal Control
Complaint
Others
Audit Finding Applicable only if Audit Type = NEA Alphanumeric Attribute Entered
Description
Audit Rating Alphanumeric Dimension Defined If Audit Type = NEA Audit
- Blue
- Purple
- Red
If Audit Type = External Audit

- Unqualified
- Qualified
Audit Type Alphanumeric Dimension Defined NEA Audit, External Audit
Auditor Name Alphanumeric Attribute Entered
Average % Change in Average % change of System Loss within a defined period (for ex, past 6 Numeric Measure Calculated
System Loss Across months, past 12 months or pas 3 years)
Period n

Formula: Average % Change in System Loss = (Sum of System Loss over x
months)/(x months)
Average Administrative Coop Use (kWh or mWh) as a percentage of Total Input Energy (kWh) Numeric Measure Calculated
Loss %
Formula: Average Administrative Loss % = Coop Use / Input Energy
Average Annual Growth Average annual growth rate of a measure. May be calculated for the number Numeric Measure Entered
Rate of connections or sales.
Average CAPEX per Formula: CAPEX per Connection = [Sum(CAPEX)] / [Sum(Count of Numeric Measure Calculated
Connection Connections)]
Average Collection Numeric Measure Calculated
Efficiency
Average Collection A measure of how quickly the consumers pay their power bills to the EC Numeric Attribute Calculated
Period
Formula: Average collection period = {average receivables *[(Beginning +
End)/2]}/ daily sales for 365 days
Source: Memo 2013-024

Average End Date of Average (arithmetic mean) of end dates of meter reading for a given month mm/dd/yyyy Measure Calculated
Meter Reading for the
Month Formula: Average End Date of Meter Reading for the Month =
AVERAGE(End Date of Meter Reading1+End Date of Meter Reading2+End
Date of Meter Reading)
Average Non-Technical Numeric Measure Calculated
Loss %
Average Normalized Formula: Average Normalized System Loss % = Average(Normalized Numeric Measure Calculated
System Loss % per EC System Loss % per EC)
Average Power Rate The buying rate (for power) of the EC. Averaged through time and across Numeric Measure Calculated
various suppliers. Expressed in PHP/kWh.
Average Price EC Average price of an item or group of items based on EC-submitted prices Numeric Measure Calculated
Average Price NEA Average price of an item or group of items based on NEA-selected price Numeric Measure Calculated
Average Reading Cycle Average reading cycle of a group of ECs or per Class of Service Numeric Measure Calculated
Average Reading Period Average reading period of a group of ECs or per Class of Service Numeric Measure Calculated
Average Salaries and Numeric Measure Calculated
Wages per Connection
Average Sales per Average sales in PHP per connection among a group of ECs Numeric Measure Calculated
Connection
Average Sales per KM Average sales in PHP per KM of Line among a group of ECs Numeric Measure Calculated
Length of Line
Formula: Average Sales per KM Length of Line = Sum([Sales])/Sum([KM
Length of Line])

Average Start Date of Average (arithmetic mean) of start dates of meter reading for a given month mm/dd/yyyy Measure Calculated
Meter Reading for the
Month Formula: Average Start Date of Meter Reading for the Month =
AVERAGE(Start Date of Meter Reading1+Start Date of Meter
Reading2+Start Date of Meter Reading)
Average System Loss % Alphanumeric Measure Calculated
Average System Rate The selling rate of the EC. Averaged through time and expressed in Numeric Measure Calculated
PHP/kWh.
Average Technical Loss Numeric Measure Calculated
%
Average Total Input per Formula: Average Total Input per Day per EC = (Total Input in kWh) / Numeric Measure Calculated
Day per EC (Reading Cycle)
Average Total Output per Formula: Average Total Output per Day per EC = (Total Output in kWh) / Numeric Measure Calculated
Day per EC (Reading Cycle)
Bidding Schedule Bidding schedule of SEP/BLEP project mm/dd/yyyy Attribute Entered
Billing Determinant Determinants of NGCP followed by ECs for billing consumers. Numeric Measure Entered
- Load Billing Determinant
- System Loss
- Power Factor
- Billing Determinant Energy
Billing Determinant Billing Determinant Demand Numeric Dimension Entered

Demand (BDD)
Billing Determinant Billing Determinant Energy Numeric Dimension Entered
Energy (BDE)
Billing Period End Date End date of the billing period indicated in the power bill provided by the mm/dd/yyyy Attribute Entered
power supplier
Billing Period Start Date Start date of the billing period indicated in the power bill provided by the mm/dd/yyyy Attribute Entered
power supplier
Board Resolution Board resolution related to by-laws amendment Alphanumeric Attribute Entered
Board Resolution Alphanumeric Dimension Defined EC-wide:
Classification - CAPEX
- PSA
Financial
- Loan
- Rate application to ERC
- Procurement
- Others
Institutional
- Regular Activities (this includes
- Organization
- Salaries
- District Elections
- Board Qualifications
- GM/DM Selection
- MSEAC, AGMA or BAPA)

- Innovation
- CSR
- Others
Technical
- Request for Technical Assistance
- Others
Board Resolution Date mm/dd/yyyy Attribute Entered
Board Resolution No. Alphanumeric Attribute Entered
Board Resolution Title Alphanumeric Attribute Entered
BOD District Geography represented by a BOD Alphanumeric Attribute Entered
BOD Meeting Type Alphanumeric Dimension Defined Regular, Special, Committee
Business Tax Municipality-imposed Numeric Measure Entered
RA 7160 Section 143

Calendar Year Numeric Dimension Defined
Semester
Quarter
Month
Others
Capacity Used from Own Numeric Measure Entered
Load Actual
Capacity Used from Own Numeric Measure Entered
Load Forecast
CAPEX per Connection Formula: CAPEX per Connection = CAPEX / Count of Connections Numeric Measure Calculated
CAPEX/Non-CAPEX Alphanumeric Attribute Defined CAPEX, Non-CAPEX
Classification
Capital Expenditure Amount spent/allotted for a long-term asset or investment. For the ECs, such Numeric Measure Defined
(CAPEX) investment is allotted for distribution assets and supporting technology.
Cash Advance Amount Value obtained from EC funds for employee's use Numeric Attribute Entered
Cash Advance Status Alphanumeric Dimension Defined Up to date, With Arrears
Cash and Temporary Tangible or liquid assets of an EC reported in the Balance Sheet. This Numeric Dimension Calculated Cash on Hand, Cash in Bank, Working
Cash Investment includes the EC's cash on hand, in banks, working funds and short term Funds, Temporary Cash Investment
investments.
Cash Balance Beginning Amount of cash at the beginning of the reporting period. This is equivalent to Numeric Dimension Calculated
the ending cash balance of the previous period.
Cash Balance End Amount of cash at the end of the reporting period based on a beginning cash Numeric Dimension Calculated
balance from which use of cash for the reporting period is deducted.
Cash for Capital Numeric Dimension Entered
Expenditures
Cash for Debt Service Numeric Dimension Entered
Cash for Sinking Funds Numeric Dimension Entered
Cash General Fund Not to be mistaken with Cash in Balance Sheet, this is a requirement for Numeric Measure Calculated
measuring color coded quarterly performance
Formula: Cash General Fund = (Working Fund, Revolving Fund, Petty Cash
Fund-General Fund) + (Cash in Banks-General Fund) + (Cash on Hand-

General Fund) + (Temporary Cash Investments) + (Prudential Requirements,
Security Deposits) + (Investment to Escrow Accounts for NGCP) +
(Consumers' Energy Deposit)
Source: Parameters and Standards in the Assessment of the EC Financial

Condition and Operational Performance
Cash General Fund A standard that states that an EC's Cash General Fund should be greater Alphanumeric Dimension Configured
Indicator than or equal to its one month power cost + non-power cost

Cash General Fund A measure of how sufficient the Cash General Fund is to cover a month's Numeric Measure Calculated
Sufficiency power and non power cost.
Cash Operating Budget Budget imposed on ECs to limit their operating expenses. This is approved Numeric Dimension Calculated
(COB) and monitored by NEA.
CDA Classification A classification system which groups ECs into CDA and non-CDA Alphanumeric Attribute Defined CDA, Non-CDA
Charge Type Type of charge Alphanumeric Measure Defined Generation Charge, Transmission
Charge, Distribution Charge
Circuit Line Alphanumeric Dimension Defined A classification of circuits
Classification - Voltage, 230kV
- Voltage, 138kV and less than 230kV
- Less than 69kV
- Quadruple
- Triple
- Double
- Three Phase
- Two Phase
- Single Phase
- Secondary
- UB
- OS
Circuit Line Value Measurement of a circuit line in kilometers Numeric Measure Calculated
Circuit No. Reference number or name of a circuit serving a Alphanumeric Attribute Entered
Town/City/Barangay/Subdivision
Class of Service A classification system which groups connections Alphanumeric Dimension Defined Residential Customers
- Residential
- BAPA
- Sale for Resale
Low Voltage Customers
- Commercial
- Industrial
- Public Building
- Street Lights
- Large Load
- Irrigation
- Water System
- Wholesale to Sister Coop
- Energy Recovered

- Others
High Voltage Customers
- Commercial
- Industrial
- Public Building
- Street Lights
- Large Load
- Irrigation
- Water System
- Wholesale to Sister Coop
- Energy Recovered
- Others
Code Compliance No. PDC or PGC compliance reference number Alphanumeric Attribute Configured
Code Compliance Title PDC or PGC compliance title Alphanumeric Attribute Configured
Collected RFSC Numeric Dimension Entered
Collection Efficiency Capability of ECs to collect consumer accounts receivables. Numeric Measure Calculated
Total Collection for the Year includes Collection from Sales and Outstanding
Accounts, Collection from Reinvestment Fund for Sustainable CAPEX
(RFSC), Collection from Universal Charge (UC) and Collection from Value
Added Tax (VAT) but excludes interest penalties and surcharges collected.
Gross Receivables include Receivable from Energy, RFSC, UC and VAT.
Operating Revenue includes Revenue from Energy, RFSC, UC and VAT.
Collection Efficiency = Total collection for the year / (Gross A/R Beg.) +
(Operating Revenue - Current Month Operating Revenue)

Collection Efficiency An indicator that states that an EC's collection efficiency should be at least Numeric Attribute Calculated
Indicator 95%.
Formula: If Collection Efficiency >= 95%, then Compliant.

If Collection Efficiency < 95%, then Non-compliant.

Complaint Status Alphanumeric Dimension Defined Received, Acted Upon
Compliance Compliance indicator for policies Alphanumeric Dimension Defined Compliant, Partially Compliant, Non-
Compliant
Compliance Assessment Formula: If % Status of Compliance = 100%, then Full Compliance Alphanumeric Measure Calculated Full Compliance (FC), Partial
If % Status of Compliance = 1% to 99%, then Partial Compliance Compliance (PC), Non-Compliance
If % Status of Compliance = 0%, then Non-Compliance (NC), Not Applicable (NA)
If % Status of Compliance = "No Input", then NA
Compliance to the Alphanumeric Dimension Defined Various
Customer Service
Parameter
Connection Point Connection point to be used in the Power Supply Agreement Alphanumeric Attribute Entered
Connection Status A classification system indicating if a customer is connected or disconnected Alphanumeric Attribute Defined Connected, Disconnected
Consumer Accounts This refers to expenses of the EC on operations relevant to consumer Numeric Dimension Calculated Supervision, Meter Reading Expenses,

Expense accounts such as meter reading, record keeping and advertising expense. Consumer Records & Collection Exp.,
Uncollectible Account, Informational &
Inst. Advertising Expenses,
Miscellaneous Consumer Accounts
Consumer Accounts Receivable of an EC for sold energy Numeric Measure Entered
Receivable
Consumer Average Numeric Measure Calculated
Interruption Duration
Index (CAIDI)
Consumer Average An indicator showing if the EC's CAIDI is above or below the CAIDI Standard Numeric Measure Configured
Index (CAIDI) Indicator
Consumer Average A standard stating that CAIDI should not be more than 4.0 hour Numeric Measure Configured
Index (CAIDI) Standard
Consumer Deposit Cash paid by customer to EC for which the EC has not yet provided the Numeric Measure Entered
energy in exchange.
Consumer's Energy Prepayments of an EC regarding consumers' energy Numeric Measure Entered
Prepayments
Contact Information E-mail address Alphanumeric Attribute Entered
Telephone number
Mobile phone number
Fax number
Contracted Energy Numeric Measure Entered
Forecast
Contracted Period Period contracted with a power supplier Numeric Attribute Calculated
Coop Use (kWh or mWh) Energy used by the EC for its operations Numeric Measure Entered
Cost of Damage Cost of damage of the accident Alphanumeric Attribute Entered
Count of Accidents Count of accidents Numeric Attribute Entered
Count of Actual Billed Numeric Measure Entered
Connections
Count of Applicable Parameters applicable to an EC per code Numeric Attribute Entered
Parameters
Count of Applicable Count of Applicable PDC and PGC Parameters Complied With Numeric Attribute Entered
Parameters Complied
With
Count of Attendees Total count of AGMA attendees Numeric Attribute Entered
Count of BAPA Numeric Attribute Entered
Organized
Count of Barangays Numeric Measure Calculated
Actual
Count of Barangays Numeric Measure Entered
Forecast
Count of Complaints Complaints received by an entity (EC, NEA or others) from customers and Numeric Measure Entered
other third parties
Count of Connections Count of connections within a geography. Numeric Measure Entered
A member-consumer may have more than one connection
Count of Customers Numeric Attribute Entered
Affected by Interruption
Count of Disconnections Count of connections with Disconnected status within a given period Numeric Measure Entered

Count of Energized Formula: Connection Count per Circuit Kames. of Line = Count of Energized Numeric Measure Calculated
Customers per Circuit Customers / Circuit Kames. of Line
Kames. Of Line
Count of Energized Formula: Count of Energized Customers per Coverage Area (sqm) = Numeric Measure Calculated
Customers per Coverage Connection Count / Coverage Area (sqm)
Area (sqm)
Count of Energized Formula: Count of Energized Customers per KM Length of Line = Numeric Measure Calculated
Customers per KM Connection Count / KM Length of Line
Length of Line
Count of Meetings Count of BOD Meetings Alphanumeric Attribute Entered
Count of Member- Total number of member-consumers within a geography Numeric Measure Calculated
Consumers
Count of Members (To Count of BAPA members as of a specific date Numeric Attribute Entered
Date)
Count of Minimum Bill Count of bills with lifeline rate Numeric Measure Entered
Count of Operational Numeric Attribute Entered
BAPA (To Date)
Count of Parameters Total count of parameters per PDC and PGC code Numeric Attribute Configured
Count of Reconnections Numeric Measure Entered
Count of Sitios Actual Numeric Measure Calculated
Count of Sitios Forecast Numeric Measure Entered
Coverage Area (Name) Count of Disconnections Alphanumeric Attribute Entered
Coverage Area (sqm) Count of Reconnections Alphanumeric Measure Entered
Covering Period End End of the coverage period of an audit mm/dd/yyyy Attribute Entered
Covering Period Start Start of the coverage period of an audit mm/dd/yyyy Attribute Entered
Creditor Type The types of organization with which the EC can take on a loan. Alphanumeric Dimension Defined Bank, Supplier, Regulator
CSR Project Category Alphanumeric Attribute Defined Livelihood, Scholarship, School
Lighting, Greening, Others
CSR Project Cost Numeric Attribute Entered
CSR Project Description Alphanumeric Attribute Entered
CSR Project Name Alphanumeric Attribute Entered
Current Account Current payable to a power supplier or financial institution. Numeric Dimension Entered
Current and Accrued This refers to the EC's payables for power purchases, matured debts and Numeric Dimension Calculated Notes Payable, Accounts Payable,
Liabilities accrued taxes, among others. Due to Other RECS, Taxes Accrued,
Interests Accrued. VAT Payable,
Matured Short Term Debts, Matured
Interest Payable, Withholding Tax
Payable, Other Current and Accrued
Liabilities
Current Power Bill Total amount billed by NGCP to the EC Numeric Attribute Calculated
Amount
Formula: Current Power Bill = Total Charges + Total Taxes
Current Power Supplier Total amount billed by the power supplier to the EC Numeric Attribute Entered
Bill Amount
Formula: Current Power Supplier Bill Amount = Basic Charges + Variable
Charges + Adjustments + Others + Total Taxes
Curtailed Energy Energy not supplied by the power supplier to the EC due to power supplier's Numeric Measure Entered
scheduled interruption
Customer Account No A number to identify the consumer account. Alphanumeric Attribute Entered

Customer Geography Alphanumeric Dimension Defined
Customer Service Alphanumeric Dimension Configured
Parameter
Date Awarded Awarded date mm/dd/yyyy Attribute Entered
Date Completed Date of completion of a project mm/dd/yyyy Attribute Entered
Date Energized Date when an entity (geography, connection or others) has been energized mm/dd/yyyy Attribute Entered
Date of Accident Date when the accident occurred mm/dd/yyyy Attribute Entered
Date of AGMA approval Date of AGMA approval related to a CBA mm/dd/yyyy Attribute Entered
Date of Appointment Date of appointment of a member of MSEAC or equivalent mm/dd/yyyy Attribute Entered
Date of Approval Date of approval of a salary bracket mm/dd/yyyy Attribute Entered
Date of Birth Date of birth of an Employee or BOD mm/dd/yyyy Attribute Entered
Date of Conduct Date when AGMA was conducted mm/dd/yyyy Attribute Entered
Date of Decision from Date of NEA decision (approve or reject) on an EC's by-laws amendment mm/dd/yyyy Attribute Entered
NEA
Date of Filing of Date of Filing of a Labor-Management issue or concern mm/dd/yyyy Attribute Entered
Issue/Concern
Date of First Energization Date of first energization of an EC mm/dd/yyyy Attribute Entered
Date of Incorporation Date of incorporation and registration of an EC Alphanumeric Attribute Entered
and Registration
Date of last preceding Formula: Not required to be reported for Position = Manager or Employee mm/dd/yyyy Attribute Entered
election
Date of Last Update of Date when the asset data in the System Loss Segregation Calculation Tool mm/dd/yyyy Attribute Entered
Asset Data in System was last updated, regardless of completeness of the data uploaded
Loss Segregation
Calculation Tool
Date of Submission Date of submission of the board resolution on by-laws amendment to NEA mm/dd/yyyy Attribute Entered
Date of Training/Seminar mm/dd/yyyy Attribute Entered
Date per EC By-Laws Date per EC By-Laws related to AGMA mm/dd/yyyy Attribute Entered
Date Released Date released of SEP/BLEP subsidy for a Sitio/Barangay/Municipality mm/dd/yyyy Attribute Entered
Date Released Date when patronage credit/refund was released mm/dd/yyyy Attribute Entered
Debt Ratio A measure of the degree of indebtedness or financial leverage of the EC. It is Alphanumeric Measure Calculated
used to measure the proportion of assets financed by creditors.
Formula: Debt Ratio = Total Liabilities / Total Assets
Source: Memorandum No. 2013-024

Debt Service Cover A leverage ratio that measures if the EC has the ability to service its debts. Numeric Measure Calculated
Amortization Due (in the formula) includes amortization due to NEA, PSALM,
NPC-SPUG, REFC, Banks and other Financial Institutions
Formula: Debt Service Cover = (Earnings before income tax + depreciation) /

(amortization Due (Principal + Interest) for the year)

Decision from NEA Approve/reject decision from NEA Alphanumeric Attribute Defined Approved, Rejected
Deferred Credits Deferred credits of an EC such as unpaid advances for construction and Numeric Dimension Calculated Cons. Advances for Construction,
energy payments received in advance. Consumer Energy Payment, Other
Deferred Credits
Deferred Debits Prepaid recurring expense of an EC carried forward as an asset, until the Numeric Dimension Entered Retirement work in progress,
associated service or benefit is received Prepayments - BIR

Degree Degree held by an Employee or BOD Alphanumeric Attribute Entered
Depreciation and This refers to the cost incurred due to the decrease in the value of an asset Numeric Measure Entered
Amortization Expense as it is used over time.
Description of Accident Free text description of the accident Alphanumeric Attribute Entered
Disbursements Release of cash from a particular account Numeric Dimension Entered
Dispatch Sequence Dispatch sequence to be used as indicated in the Power Supply Agreement Alphanumeric Attribute Defined Base, Intermediate, Peaking
Distribution Charge A component of the EC's rate intended to cover expenses on operations and Numeric Measure Defined Demand Charge, Distribution System
maintenance of the distribution system. Charge
Note: applicable separately per
customer and not aggregated
Distribution Expense This refers to the expenses on operations and maintenance of distribution Numeric Dimension Calculated Operations
facilities. 1 Operation Supervision & Engineering
2 Station Equipment
3 Overhead line Expenses
4 Street Lighting & Signal Expenses
5 Meter Expenses
6 Consumer Installation Expenses
7 Rents
8 Miscellaneous Distribution-
Operations Expenses
Maintenance
1 Maintenance - Supervision &
Engineering
2 Maintenance - Overhead Lines
3 Maintenance - Station Equipment
4 Maintenance - Line Transformers
5 Maintenance - Street Lighting &
Signal System
6 Maintenance - Meters
7 Maintenance - General Plant
District / Municipalities / District / Municipalities / Cities covered by an MSEAC or equivalent Alphanumeric Attribute Entered
Cities Covered
Documentary of Good Not required to be reported for Position = Manager or Employee Alphanumeric Attribute Entered
Moral Character
DSM Revenue Revenue of an EC on Distribution, Supply, and Metering Numeric Measure Calculated
Duration * Count of Duration * Count of Customers affected by an interruption Numeric Measure Entered
Customers Affected
EC Classification A classification system which groups ECs based on 6 financial and Alphanumeric Dimension Defined Green, Yellow 1, Yellow 2, Red
(Compliance) operational standards and parameters under the Guidelines for the
Classification of ECs

EC Classification (Size) A classification system which groups ECs based on volume of Average Alphanumeric Dimension Calculated Small, Medium, Large, Extra Large,
MWH Sales, Number of Service Connections and Average Kms of Lines Mega Large
EC Program/Issues Alphanumeric Dimension Defined Conversion, System Loss, Collection
Category Efficiency, Rates, Power Interruption,
Others
EC Program/Issues Alphanumeric Attribute Entered
Description
Economic Benefits for Alphanumeric Attribute Entered

Unionized Coops
Election Position A classification system for employees. Alphanumeric Dimension Entered
Not required to be reported for Position = Manager or Employee
Electric Cooperative (EC) Short or full name of an EC. For example, NORECO II, Negros Oriental II Alphanumeric Attribute Defined
Name Electric Cooperative, Inc.
Electricity Consumption This is compared to Electricity Consumption Actual (Power Sales). Numeric Measure Entered
Forecast
Employee Contact Information of an employee or BOD such as Name, Address (district), Mobile Alphanumeric Attribute Entered
Information Number, Email Address
Employee Count Total number of employees Numeric Measure Calculated
Employee End Date If Position = Manager or Employee, this is the date when the employee left mm/dd/yyyy Attribute Entered
the EC. If Position = BOD, this is the end date of term and/or appointment of
the BOD.
Employee Position Alphanumeric Attribute Defined Department Manager, Middle
Management, Associates/Employee
Employee Position A classification system of employees or BOD Alphanumeric Dimension Defined BOD
- President
- Vice President
- Secretary
- Treasury
- Auditor
- Member
- Independent BOD
- NEA Representative to the Board
Manager
- General Manager
- Department Manager
- Division Manager
- Area Manager
- General Manager (OIC)
- Department Manager (OIC)
- Division Manager (OIC)
- Area Manager (OIC)
Associates/Employee
- Teller
- Meter Reader
- Lineman
- Bill Collector
- Driver
- Foreman
- Substation Tender
- ROW Cutter
- Administrative Assistant
- Secretary
- Disconnector
- Auditor
- Messenger
- Clerk/Typist
- Others

Employee Reason for Alphanumeric Attribute Defined Resignation, Termination, Death,
End Date Disqualification, Others
Employee Start Date If Position = Manager or Employee, this is the hiring date. If Position = BOD, mm/dd/yyyy Attribute Entered
this is the start date of the term of office
Employee Status Status of employment of an EC employee Alphanumeric Dimension Defined Regular, Probationary, Casual/
Contracted, Outsourced/ Project-
based, Elected, Appointed
Employee TIN TIN number of employee or BOD Numeric Attribute Entered
Employee-Customer Ratio representing the number of customers served per employee. Numeric Measure Calculated
Ratio Employee-Customer Ratio = (no. of customers / no. of employees)
Employee-Customer An indicator showing the status of an EC’s payment to its power suppliers. Alphanumeric Measure Configured Compliant, Non-Compliant
Ratio Indicator For example, Current, In Arrears.

Employee-Customer Employee-Customer Ratio = 1:350 Numeric Measure Configured
Ratio Standard Source: Memo 2013-024
End date of Meter Latest date of meter reading for a geography for the month. This includes re- mm/dd/yyyy Attribute Entered
Reading reading of meter (for example, due to erroneous reading) or going back to a
meter because the meter reader was unable to read the meter at the initially
scheduled date.
Energization Status A classification system which groups customers, connections or geography Alphanumeric Dimension Defined Energized, Unenergized/Potential
depending if it has been energized or not
Energy Delivered (kWh) Total energy delivered or dispatched by the power supplier to the EC Numeric Attribute Entered
Energy Used for Own Numeric Measure Entered
Load Actual
Energy Used for Own Numeric Measure Entered
Load Forecast
Equities and Margins A credit component referring to the equities of an EC based on its Numeric Dimension Calculated 1. Membership
membership pool, capital accounts and appropriated margins. 2. Donated Capital
3. Cons. Cont. to Dept. Svc.
4. Contr. in Aid of Const.
5. Revaluation Increment
6. Other Capital Accounts
7. Appropriated Margins
8. Unappropriated Margins
ERC Case Number ERC Case Number for the Power Supply Agreement Alphanumeric Attribute Entered
Escrow a bond, deed, or other document kept in the custody of a third party, taking Numeric Measure Entered
effect only when a specified condition has been fulfilled
Estimated No. of Numeric Attribute Entered
Retiree/s for the Year
Exit Conference Date Applicable only if Audit Type = NEA mm/dd/yyyy Attribute Entered
Extent of Damage Free text description of the extent of damage of the accident Alphanumeric Attribute Entered
Extraordinary Items Other ad hoc expenses not regularly incurred. Numeric Measure Entered
Federated An indicator if MSEAC or equivalent is federated or not Alphanumeric Attribute Defined Yes, No
Feed-In Tariff Allowance Allowance applicable to on-grid application of energy from renewable Numeric Measure Defined
(FIT-All) - EC sources.
Source: RA 9513
Feed-In Tariff Allowance Numeric Attribute Entered
(FIT-All) - NGCP

Financial Interest Not required to be reported for Position = Manager or Employee Alphanumeric Attribute Defined Yes, No
Formula Formula of Patronage Credit/Refund Alphanumeric Attribute Entered
Franchise Tax Local Franchise Taxes go to the local government Numeric Measure Entered
Source: RA 7160 Section 137

Fuel Requirement Numeric Measure Entered
Forecast
Fuel Type Alphanumeric Dimension Defined Scrap, Debris, Crops, Manure, Others
Full Time Equivalent Hours worked by an employee on a full-time basis Numeric Measure Entered
(FTE)
Fund Manager Alphanumeric Attribute Entered
Fund Source Source of the funds to energize the sitio/purok Alphanumeric Attribute Entered
Generation Charge A component of the EC's rate intended to cover the cost of generation Numeric Measure Entered
agreed between the EC and the power supplier.
Generation Rate for the Generation rate indicated in the power supplier bill. This may change every Numeric Attribute Entered
Month month.
Geography Alphanumeric Dimension Defined
Growth in Sales Growth in sales. Expressed in PHP. Numeric Measure Calculated
Highest Level of Highest level of education attained by an employee or BOD Alphanumeric Attribute Defined High School, Undergraduate/
Education Bachelor's Degree, Graduate Degree
Highest Salary Numeric Attribute Entered
ID of Property/Equipment ID of property/equipment involved in the accident, if any Alphanumeric Attribute Entered
Involved
Included in the latest Alphanumeric Attribute Defined Yes, No
eICPM approved?
Inclusive date of the Alphanumeric Attribute Entered
Agreement
Income Classification for A classification system grouping municipalities based on the income classes Alphanumeric Dimension Defined First, Second, Third, Fourth, Fifth,
Provinces, Cities and according to their average annual income during the previous four calendar Sixth
Municipalities years. The classification of the provinces, cities and municipalities is defined
by the Department of Finance.
Indicative Demand Numeric Measure Entered
Forecast
Information, Education & Alphanumeric Dimension Configured
Communication
Technology Parameter
Initial HHC Alphanumeric Attribute Entered
Input Energy The Purchased Energy measured at the Billing Determinant Energy (BDE) Numeric Measure Calculated
and Generated Energy measured at the Connection Point excluding the
Transmission Loss and Site Specific Loss Adjustment. This may be
represented in kWh or mWh.
Formula: Input Energy = Purchased Energy + Generated Energy

Installed Capacity In KW; On utility's owned power generating facilities Numeric Measure Entered
Forecast
Inter-class Cross Refers to an amount charged by Distribution Utilities to industrial and Numeric Measure Entered
Subsidy commercial End-users as well as to other subsidizing customer sectors to
reduce electricity rates of other customer sectors such as the residential

consumers, hospitals, and streetlights.
Interest Expense This refers to the cost incurred due to borrowings or loans. This is calculated Numeric Measure Entered
based on the interest rate and the terms of a loan.
Interest Income - RFSC Income earned from storing RFSC in a bank account Numeric Dimension Entered
Interest, Penalties and Charges due in accordance with an unpaid debt. Numeric Measure Entered
Surcharges
Internal Cash Generation Cash generated (inflow) by the EC through collections and other receipts. Numeric Dimension Calculated 1. Collection from Customers A/R
a. From Energy Sales
b. From RFSC
c. From Universal Charge
d. From VAT
2. Non-Operating Revenue
a. Reconnection and other fees
b. Interest Income
c. Collection from Non-Operating
Revenue
3. Other Receipts
4. Loan from NEA/Banks/Other
Financial Institutions
5. Subsidy
Interruption Cause Code Numeric Attribute Defined 8, 9, 10, …
Interruption Duration Duration of an interruption. May be expressed in minutes or hours. Numeric Measure Calculated
Formula: Interruption Duration = ((Restoration Date-Start Date of

Interruption)+(Restoration Time-Start Time of Interruption))*1440
Interruption Duration Numeric Attribute Entered
Interruption Equipment Numeric Attribute Defined 301, 302, …
Failed Code
Interruption Isolation Numeric Attribute Defined 201, 202, …
Device Code
Interruption Weather Numeric Attribute Defined 101, 104, …
Code
Item Classification A classification system for items in the NEA Price Index Alphanumeric Attribute Defined
Item Description For example, "Insulator, Pin Type, Porcelain, ANSI, Class 55 - 3" or "Meter, Alphanumeric Attribute Defined
KWH, 3 Phase, Class 20, 240 V, 4 Wire, Form 9S"
Item ID A reference ID for items in the NEA Price Index Alphanumeric Attribute Defined
KM Length of Line Circuit length of a line in km. If 3-phase, single circuit subtransmission line x Numeric Measure Calculated
3. If 3-phase, double circuit (parallel) subtransmission line x 6. If 3-phase
primary or secondary distribution line x 3. If V-phase primary or secondary
distribution line x 2. If 1-phase primary or secondary distribution line x 1.
KPS/KPGS Rating Key Performance Standard rating of an EC Alphanumeric Dimension Calculated AAA, AA, A, B, C, D
kWh not sold from Formula: kWh not sold from Outages due to Force Majeure = [(Duration * No. Numeric Measure Calculated
Outages due to Force of Cust. Affected by Outages due to Force Majeure)] * [Average kWh
Majeure consumption per n (where n could be minute, day, week, etc)]
kWh not sold from Formula: kWh not sold from Outages due to generation, transmission line, Numeric Measure Calculated
Outages due to transmission substation failure = [(Duration * No. of Cust. Affected by
generation, transmission Outages due to generation, transmission line, transmission substation
line, transmission failure)] * [Average kWh consumption per n]
substation failure
where n could be minute, day, week, etc

Labor-Management Issue Alphanumeric Attribute Entered
and Concerns
Description
Labor-Management Issue Alphanumeric Attribute Defined
and Concerns Type
Labor-Management Alphanumeric Attribute Defined Open,
Issues and Concerns Closed
Status
Liabilities and Other The credit side of an EC's balance sheet composed of equities and margin, Numeric Dimension Calculated • Equities and Margin
Credits long and short term debts, current and accrued liabilities etc. • Long Term Debt and Short Term
Debits
• Current and Accrued Liabilities
• Total Current and Accrued Liabilities
• Deferred Credits
Lifeline Consumption Consumption ranges for which a lifeline discount would be applicable. Numeric Attribute Entered
Range
Lifeline Discount Rate Refers to the discount rate applied to low-consumption consumers (below Percentage Measure Entered
100kwh). The rate varies depending on the actual consumption of a
customer (i.e., 0-20 kwh get 50% discount, 20-40kwh get 40%, etc.).
Accordingly, costs to cover the discounted amount of the bill are subsidized
by all other customers with a consumption above 100 kwh.
Source: EPIRA
Lifeline Rate In pesos. This is the rate applied to consumption within lifeline consumption Numeric Measure Calculated
ranges.
Lifeline Subsidy An amount added to regular consumers' electricity bill to subsidize the Numeric Measure Entered
discount provided to lifeline bills.
Load Factor - EC Measure of electrical usage efficiency of an EC. Represented in % Percentage Measure Calculated
Formula: System Load Factor = [(Total Input kWh/8760)*100] / [Peak

Demand in mW x 1000]
Load Factor - NGCP Load factor indicated in the NGCP bill Percentage Attribute Entered
Load Factor Forecast Forecasted load factor of an EC Percentage Measure Entered
Loan Status The status of the EC's loan based on its ability to pay. Alphanumeric Dimension Defined Current, Restructured, In Arrears
Loan Term Description Agreed conditions between the lender and borrower specific to the Alphanumeric Attribute Entered
repayment of a loan. This includes the interest rate to be applied, frequency
of payment, etc.
Loan Type Alphanumeric Dimension Defined Short Term, Long Term
Long Term Debt Long term liabilities of an EC for various needs such as construction, Numeric Dimension Entered
rehabilitation, expansion, etc.
Loss Factor Loss factor indicated in the NGCP bill Numeric Attribute Entered
Lowest Salary Numeric Attribute Entered
MAIFI Measures the average number of momentary interruptions that a customer Numeric Measure Calculated
experiences during a time period
Formula: MAIFI = Summation of number of interrupting device operations *

Total number of customers interrupted / Total number of customers served
Materials and Supplies A balance sheet component referring to the value of the EC's existing Numeric Dimension Calculated 1. Materials and supplies
inventory which is composed of materials and supplies such as fuel stock, a) Fuel Stock
materials for electric works, house wiring, office supplies, etc. This value may b) Electric
be adjusted should there by damaged inventory items. c) House wiring

d) Project materials
2. Office Supplies
3. Stores expense undistributed
Media/Info Materials Alphanumeric Attribute Entered
Member of Good Not required to be reported for Position = Manager or Employee Alphanumeric Attribute Defined Yes, No
Standing
Metering Charges A component of the EC rate intended to cover meter-related expenses such Numeric Dimension Defined • Retail Customer Metering Charge
as reading, maintenance, etc. • Metering System Charge
Metering Point Count Total count of metering points Numeric Measure Calculated
Name of Creditor Alphanumeric Attribute Entered
Name of Customer Alphanumeric Attribute Entered
Name of Employee Name of employee involved in the accident, if any Alphanumeric Attribute Entered
Involved
Name of Member- Name of member-consumer/s involved in the accident, if any Alphanumeric Attribute Entered
Consumer/s Involved
Name of Outsourced Name of outsourced employee involved, if any Alphanumeric Attribute Entered
Employee Involved
Name of Participant Name of a participant in a Capacity Building program or activity Alphanumeric Attribute Entered
Name of Alphanumeric Attribute Entered
Training/Seminar
Attended
Name of Alphanumeric Attribute Entered
Union/Association
Name/s of Members Name/s of members of an MSEAC or equivalent Alphanumeric Attribute Entered
Nature of Complaints Alphanumeric Dimension Defined No Light/Power
Low Voltage
Transformer (Busted)
Secondary/Primary Line (Tripping)
Leaning Pole/Rotten Pole
Complaints on Service Drop
Complaints on KWH Meter
Others (Board, Management,
Employees)
NEA Action Required? A Yes/No indicator if NEA action is required on an EC Board Resolution Alphanumeric Attribute Defined Yes, No
NEA Approved Per Alphanumeric Attribute Entered
Diems (Per Quarter)
NEA Remarks NEA remarks on EC Board Resolution Alphanumeric Attribute Entered
Net Dependable Capacity In KW; On utility's owned power generating facilities Numeric Measure Entered
Forecast
Net Margin/Loss after Net Margin/Loss before RFSC and UCS less RFSC and UCS. Numeric Measure Calculated
RFSC and UCS
Net Margin/Loss before All revenue items inclusive of RFSC and UCS collected less all expense Numeric Measure Calculated
RFSC and UCS items.
Net Operating Margin Operating margin less depreciation, amortization and interest expense. Numeric Measure Calculated
Net Production Forecast In MWH; On utility's owned power generating facilities Numeric Measure Entered

Net worth Indicator An indicator that measures the value of an EC, considering it is composed Alphanumeric Measure Configured Positive, Negative
primarily of all the money and properties that have been invested since its
inception, as well as the retained earnings for the duration of its operation.
Formula: If Total Liabilities > Total Assets, then Negative.

If Total Liabilities < Total Assets, then Positive.

No. of Bills Unpaid Numeric Attribute Entered
No. of Days Before Numeric Attribute Entered
Deadline
No. of Intended Numeric Attribute Entered
Beneficiary/ies
No. of Years in Existence Number of years of EC existence since its date of incorporation and Numeric Attribute Calculated
registration
No. of years of Service If Position = BOD, then this will be presented in a report as No. of Years as Numeric Attribute Calculated
BOD".
If Position is not equal to BOD, then this will be presented in a report as "No.
of years of Service".
Non-Operating Expenses Expenses other than that generated due to the operations and sales of Numeric Measure Entered
energy.
Non-Operating Revenue Revenue other than that earned from energy sales. Numeric Measure Entered
Non-Power Cost Operating costs of EC other than power cost which generally consists of Numeric Measure Calculated 1. Salaries & Wages
distribution, consumers, administrative and general expenses. a. Payroll
b. Others
2. SSS/Medicare/ECC/Pag-Ibig
3. Employee Benefits
4. Utilities
5. Office Materials & Supplies
6. Travel
7. Transportation
8. Repairs & Maintenance
9. Directors' Per Diems
10. Allowances/Representation
11. Outside Professional Service
12. Seminars/Trainings
13. Institutional Activities
14. Insurance/Registration
15. Sundries
16. Property Tax
Non-Power Cost per Part of KPI Analysis Numeric Measure Calculated
Connection
Formula: Non-Power Cost per Connection = Total Non-Power Cost / Total
Count of Connections
Non-power cost per Ratio of non-power cost over the count of customers Numeric Measure Calculated
customer ratio
Formula: Non-power cost per customer = Total non-power cost / count of
customers
Non-Technical Loss % A percentage of non-technical loss over the total Input Energy Percentage Measure Calculated

Formula: Non-Technical Loss % = System Loss % - Technical Loss %
Non-Technical Loss A type of loss within the distribution network resulting from theft, metering Numeric Measure Entered
(kWh or mWh) errors and data handling errors. This is measured between the metering
point read by the power supplier and the customer connection.
Formula: Non-Technical Loss (kWh or mWh) = System Loss (kWh or mWh) -

Technical Loss (kWh or mWh)
Non-Technical-System Average % allocation of non-technical loss out of the total system loss of a Numeric Measure Calculated
Loss Ratio Average group of ECs
Normalized System Loss Formula: Normalized System Loss % per EC = [(Total Input per Day per EC)- Numeric Measure Calculated
% per EC (Average Total Output per Day per EC)]*100%
Notes and Accounts Notes and accounts receivable by an EC reported under Assets in the Numeric Dimension Calculated 1. Notes Receivable
Receivable Balance Sheet mainly involving receivables on sold energy, advances, etc. 2. Net Cons. Accts. Rec. - Energy
3. Cons. Accounts Rec. - Others
4. Other Accts. Rec.
5. Advances to Officers and
Employees
6. Due from other RECS
Number of Metering Numeric Attribute Entered
Points
On-Grid/Off-Grid A classification system which groups customers, connections, ECs, Power Alphanumeric Dimension Defined On-Grid, Off-Grid
Classification Purchased (kWh) or geography depending on its source of energy
Operating Expense per A measure of the EC's efficiency in operations. Could also be broken down Numeric Measure Calculated
Connection per component of operating expense - metering and billing, office operations,
etc.
Operating Margin Measures the portion of operating revenue left of an EC after paying Numeric Dimension Calculated
operating fixed and variable costs.
Operating Margin per Operating Margin before Depreciation Expense and Interest Expense Numeric Measure Calculated
Connection Average Operating Margin per Connection
Operating Revenue Represents the energy sales of an EC. This is based on the kwh sales Numeric Measure Calculated
multiplied by the rates applicable per type of consumer.
Operational Expense Generic term for … Numeric Measure Calculated
Reported as …
Inclusive of…..
Calculated and compared against...
Operational expense of an EC used to uphold day to day operations
OPEX per Employee Numeric Measure Calculated
OPEX per KM Length of Numeric Measure Calculated
Line
Other Current and Refers to items expected to be converted to cash or consumed by the EC Numeric Dimension Calculated 1. Prepayments
Accrued Assets within the fiscal year. This includes pre-payments received from consumers 2. Misc. Current and Accrued Assets
and other deferred debits. 3. Retirement Work in Progress
4. Other Deferred Debits

Other Property and A balance sheet component referring to all the assets of an EC beyond their Numeric Dimension Calculated 1. Net Non-Utility Property
Investment distribution systems. This may include land, buildings, investments and a) Non-Utility Property (Book Value)
restricted funds. b) Accumulated Depreciation (Book
Value)
2. Investment in Assoc. Organization
3. Other Investment
4. Restricted Funds
a) Membership Funds/Meter Deposit
b) Retirement Fund
c) Sinking Fund For Reinvestment
d) Subsidy/Grants
e) Total Restricted Funds
5. Investment in Poles Procurement
Output Energy Energy sold to customers or other entities, or used by the EC Numeric Measure Calculated

Output Tax - Distribution Deferred credit for output tax regarding distribution of an EC Numeric Measure Entered
Overdue Account Overdue payable to a power supplier or financial institution. Numeric Measure Entered
Peak Demand Actual Numeric Attribute Entered
Peak Demand Forecast Numeric Attribute Entered
Peak Load Maximum electrical power demand of consumers at a given cycle time Numeric Measure Entered
Per Capita Income Numeric Measure Entered
Performance Rating - Alphanumeric Dimension Defined Compliant, With Minor Lapses, With
BOD Adverse Audit Findings, With
ADCOM/Court Cases
Performance Rating - GM Alphanumeric Dimension Entered
Population Numeric Measure Entered
Position Remarks Additional description to the Position of the employee Alphanumeric Attribute Entered
Power Account Amount Numeric Attribute Entered
Power Account Status Alphanumeric Dimension Defined Up to date, With Arrears
Power Account Status Alphanumeric Dimension Defined Up to date, With Arrears
Power Bill/Statement Alphanumeric Attribute Entered
Reference Number
Power Bill/Statement Bill or statement reference number indicated in the power bill provided by the Alphanumeric Attribute Entered
Reference Number power supplier
Power Coop Used Power the EC used. May be expressed in kWh or mWh. Numeric Measure Entered
Power Cost Cost of power purchased from power suppliers Numeric Measure Calculated
Power Factor - EC Ratio of the real to the apparent power in the circuit within the distribution Percentage Measure Calculated
system
Formula: Power Factor = (Real Power/ Apparent Power) * 100

Power Factor - NGCP Ratio of the real to the apparent power in the circuit within the transmission Percentage Attribute Entered
system
Power Generated (kWh Energy generated by the power plant of an EC. May be expressed in kWh or Numeric Measure Entered
or mWh) mWh.

Power Plant Capacity Capacity of the power supplier. Expressed in MW Alphanumeric Attribute Entered

Power Plant ID ID assigned to the power supplier Alphanumeric Attribute Defined
Power Plant Information Name of power supplier Alphanumeric Attribute Entered
Power supplier capacity
Geography
Power Supplier Connection Point
Power Plant Location Geography of the power supplier Alphanumeric Attribute Entered
Power Plant Name Name of the power supplier (for example, Magat Hydro) Alphanumeric Attribute Entered
Power Plant Type A classification system of power suppliers depending on its source of energy Alphanumeric Dimension Defined Coal, Diesel, Natural Gas, Hydro,
Solar, Geothermal, Wind, Biomass,
Market, Others
Power Plant VAT Reg TIN VAT Registration TIN No. of the power supplier Numeric Attribute Entered
No.
Power Purchased (kWh Energy purchased by the EC from power supplier(s). May be expressed in Numeric Measure Entered
or mWh) kWh or mWh.

Power Recovered Energy not registered by the consumers' billing meters but were recovered Numeric Measure Entered
(Settled) later due to corrective measures undertaken by the EC, and have been paid
for by the concerned consumer. May be expressed in kWh or mWh.
The energy recovered shall be considered in the computation of systems

loss upon settlement and/or execution of promissory note by the concerned
consumer and that the energy was recovered with the same year in review.

Power Recovered Energy not registered by the consumers' billing meters but were recovered Numeric Measure Entered
(Unsettled) later due to corrective measures undertaken by the EC, and have been paid
for by the concerned consumer. May be expressed in kWh or mWh.
Power Sales (in PHP) Refers to the value of energy sold by the EC to member consumers. Numeric Measure Calculated
Calculated based on the EC rate schedule and the kWh consumption of
customers. Also known as the EC's Operating Revenue.
Power Sales (kWh or Total energy or electric consumption of the consumers as read from their Numeric Measure Entered
mWh) billing meters. May be expressed in kWh or mWh.
Power Source An indication of the power source of a newly energized sitio/purok (i.e. solar, Alphanumeric Attribute Entered
grid)
Power Supplier Address Alphanumeric Attribute Entered
Power Supplier Contact Alphanumeric Attribute Entered
Number
Power Supplier Contact Alphanumeric Attribute Entered
Person
Power Supplier Name Alphanumeric Attribute Entered
Power Supplier Name Name of the power supplier owner (for example, Aboitiz Power) Alphanumeric Attribute Entered
Power Supplier Owner A classification system of power supplier owners Alphanumeric Dimension Defined Distribution Utility, NPC, Local Private
Type Supply, Others
Power Supplier VAT Reg VAT Registration TIN No. of the power supplier owner Alphanumeric Attribute Entered
TIN No.
Power Supply Agreement mm/dd/yyyy Attribute Entered
End Date

Power Supply Agreement mm/dd/yyyy Attribute Entered
Start Date
Principal Amount Initial amount borrowed. Numeric Measure Entered
Profitability Indicator An indicator that states an EC's productivity which reflects the amount of Alphanumeric Measure Configured Positive, Negative
income before RFSC/percentage of peso sales after all cost and expenses
have been deducted

Project Budget An amount allocated for the procurement of necessary materials/equipment Numeric Dimension Calculated
and implementation of a project. Includes labor and project overhead costs.
This is typically monitored by a project manager. Applicable to ECs' CAPEX
projects.
Project Cost Actual Numeric Measure Entered
Project Description Description of a project. For example, "Construction of 69KV Line from Bito- Alphanumeric Attribute Entered
on, Dumanjug to Tomonoy, Moalboal", "Installation of reclosers (630A 3Ph)",
"Installation of Line AVRs along Feeders".
Project End Date Actual mm/yyyy Attribute Entered
Project End Date A description of the target impact of a project. For example, "For 2015, mm/yyyy Attribute Entered
Planned additional connections of 1,680" or "Generated additional sales and served
additional consumers"
Project Funding Source Alphanumeric Dimension Defined Subsidy
Loan
Existing Funds
Others (w/ Free Text field for
description required)
Project ID Alphanumeric Attribute Entered
Project Impact Alphanumeric Dimension Defined Line expansion
Additional connections
Accommodated Add-On Connections
System Upgraded (?)
Improved System Reliability
Reduced System Loss
Improved Power Quality
Complied with safety requirements of
PGC and PDC
Buffer stock for emergency
Improved customer service/corporate
image
Improved service efficiency and
mobility
Improved manpower efficiency and
safety
Project Notes/Remarks Alphanumeric Attribute Entered
Project Particulars Alphanumeric Attribute Entered
Actual
Project Particulars Alphanumeric Attribute Entered
Planned
Project Particulars UOM Alphanumeric Attribute Entered
Project Start Date Actual mm/yyyy Attribute Entered
Project Start Date mm/yyyy Attribute Entered
Planned

Project Status Alphanumeric Dimension Defined 1 Not Started
Pending ERC approval
Pending funding availability
Pending resource availability
2 Ongoing
Procurement
Implementation
Close Out
Documentation
3 Completed
Project Type A classification system which groups projects into network and non-network Alphanumeric Dimension Defined I. Network Projects
projects, and so on A. Electrification Projects
1. Primary Distribution Project
2. Submarine Cable and Underground
Cable
3. Land and Land Rights
4. User Development Projects
5. Renewable Energy
B. Reliability Projects
1. Looping of Subtransmission System
2. Looping of Distribution System
3. SAIFI/SAIDI sectionalized device
installation
4. SAIDI Switching Device Installation
5. Conducting Transformer Load
Management
6. Preventive Subtransmission and
Distribution Line Maintenance
B. Power Quality Projects
1. Capacitor Replacement and
Installation
2. Installation of AVR, OLTC and
others
3. Conductor Uprating
4. Reconfiguration of Primary
Distribution Line
5. Installation of New Power
Transformer
C. System Loss Projects
1. Conductor Uprating
2. System Uprating
3. Rationalization of Distribution
Capacity
4. Logistical I.T. Equipment
5. I.T. Equipment Listing and Cost
Estimates
D. Subtransmission Development
1. Acquisition of Subtransmission Line
2. Refurbishment or Rehabilitation
3. Reinforcement or Construction
E. Substation Projects
1. New Power Transformer and

Substation Equipments
2. Rehab and Uprating of Power
Transformer and Substation
Equipment
F. Add-ons Consumer Requirements
1. Distribution Transformers, Meters
and Service Drops
2. Primary and Secondary Line
Expansion
G. Distribution Projects
1. System Reliability
2. System Loss Reduction
II. Non-Network
A. Property
1. Land and Land Rights
2. Building Structures and
Improvement
B. Equipment
1. Office Furniture and Equipment
2. Transportation Equipment
3. Store Equipment
4. Tools, Shop, Safety Gadgets and
Garage Equipments
5. Laboratory Equipment
6. Information Systems Equipment
7. Power Operated Equipment
C. Institutional Projects
1. Organizational Development
2. Human Resource Development
3. Corporate Image and Public
Relations
4. Institutional Support for GCP and
PIP
5. Preparation for Competitive Electric
Market
6. Other Institutional Projects
D. Other Network Asset
1. WESM Requirement
2. Logistical I.T. Requirement
3. Other CAPEX Projects
PSP Classification A classification system which groups ECs into PSP (Private Sector Alphanumeric Attribute Defined PSP
Participation) or non-PSP Non-PSP
Publish Date of Audit mm/dd/yyyy Attribute Entered
Report
Quick Ratio A liquidity ratio that measures the ability of the EC to satisfy its short-term Numeric Measure Calculated
obligations as they become due. Receivables (in the formula) is inclusive of
VAT, UC and RFSC (Net of Allowance for Doubtful Accounts)
Formula: Quick Ratio = (Cash + Marketable Securities + Receivables) /

Current Liabilities

Ranks Salary ranks of an employee classification such as Department Managers, Alphanumeric Attribute Entered
Managers and Associates
Reactive Power Energy alternately stored and released by inductors and/or capacitors Numeric Measure Entered
Reading Cycle Average number of days in between reading per connection Numeric Measure Calculated
Formula: Reading Cycle = Average Start Date of Meter Reading of Current

Month - Average End Date of Meter Reading of Previous Month
Reading Period Range of days in a month from the start date of meter reading up to the end Numeric Measure Calculated
date of meter reading. For example, 24th (of the month) to 2nd (of the
month)
Formula: Reading Period = (DAY(Average Start Date of Meter Reading for

the Month)) "to" (DAY(Average End Date of Meter Reading for the Month))
Reference/Basis Reference/basis of a salary rank (i.e. NEA, CBA, DOLE) Alphanumeric Attribute Entered
Reinvestment Fund for Previously referred to as Members Contribution for Capital Expenditure Numeric Dimension Calculated
Sustainable CAPEX (MCC). This is a component of the EC's rate intended for use to cover
(RFSC) CAPEX project related expenses.
Remarks Remarks on complaints Alphanumeric Attribute Entered
Remarks EC remarks on EC Board Resolution Alphanumeric Attribute Entered
Remarks Remarks on a project Alphanumeric Attribute Entered
Remarks Remarks on Labor-Management Issues and Concerns Alphanumeric Attribute Entered
Remarks Remarks on the conduct of an AGMA Alphanumeric Attribute Entered
Reserves A credit component reported in the balance sheet referring to the amount Numeric Dimension Entered
owed by the EC so stakeholders. This may be inclusive of benefits unpaid
such as retirement, etc.
Restoration Date Date that an interruption was restored mm/dd/yyyy Attribute Entered
Restoration Time Time that an interruption was restored hh:mm Attribute Entered
Restructured Account Restructured payable to a power supplier or financial institution. Numeric Measure Entered
RRE RRE indicated in an NGCP bill Numeric Attribute Entered
RSEC-WR Classification A classification system which groups ECs of their RSEC-WR group set by Alphanumeric Attribute Defined A, B, C, D, E, F, G
the ERC
SAIDI Indicator Formula: If EC = On-Grid and SAIDI <= 2,7002 minutes per year, then score Numeric Measure Configured
= 7.5.
If EC = On-Grid and SAIDI > 2,7002 minutes per year, then score = 0.
If EC = Off-Grid and SAIDI <= 3,3752 minutes per year, then score = 7.5.
If EC = Off-Grid and SAIDI < 3,3752 minutes per year, then score = 0.

SAIFI Formula: SAIFI = (total no. of sustained customer power interruptions within Numeric Measure Calculated
a given period) / (total number of customers served within the same period)

SAIFI Indicator If EC = On-Grid and SAIFI <= 25 interruptions per customer per year, then Numeric Measure Configured
score = 7.5.
If EC = On-Grid and SAIDI > 25 interruptions per customer per year, then
score = 0.
If EC = Off-Grid and SAIFI <= 30 interruptions per customer per year, then
score = 7.5.
If EC = Off-Grid and SAIFI < 30 interruptions per customer per year, then
score = 0.

Salaries and Wages per Numeric Measure Calculated
Connection
Salary Salary of an employee Numeric Attribute Entered
Salary Ceiling Salary ceiling amount for a chosen salary classification Numeric Attribute Entered
Salary Rank Salary rank of an employee Alphanumeric Attribute Entered
Sales per Connection Sales in PHP per connection Numeric Measure Calculated
Formula: Sales per Connection = (Sales) / (Count of Customers)

Sales per KM Length of Sales per KM Length of Line = Sales / KM Length of Line Numeric Measure Calculated
Line
Schedule/Duration Schedule/duration of an Information Education Campaign Alphanumeric Attribute Entered
Secondary Line Current Current through a substation secondary line Numeric Attribute Entered
Sector Sector of an MSEAC or equivalent (i.e. Civic, Farmer, Religious) Alphanumeric Attribute Entered
Segregated Collection Numeric Measure Calculated
Efficiency
Senior Citizen Discount - Discounted rate applied to accredited DSWD senior citizen centers. Percentage Measure Entered
Center
Senior Citizen Discount - Discounted rate applied to individual senior citizen customers. Percentage Measure Entered
Individual
Senior Citizen Subsidy An amount added to regular consumers' electricity bill to subsidize the Numeric Measure Entered
discount provided to senior citizens.
Short Term Debt Short term liabilities of an EC such as emergency loans and consumer Numeric Dimension Entered
deposits.
Simulated Operating Simulated Operating Revenue = Average System Rate * Power Sales in kWh Numeric Measure Calculated
Revenue
Simulated System Loss Sales per KM Length of Line = Sales / KM Length of Line Numeric Measure Calculated
without Outages due to
Force Majeure = Total
Input - Simulated Total
Output
Simulated Total Output Simulated Total Output = Simulated Total Sales without Outages due to Numeric Measure Calculated
Force Majeure + Coop Use in kWh + Total Recovered in kWh
Simulated Total Sales Numeric Measure Calculated
without Outages due to Simulated Total Sales without Outages due to Force Majeure = (kWh not
Force Majeure sold from Outages due to Force Majeure) + (Total Sales in kWh)
Sinking Fund Restricted funds allotted by ECs for various uses such as power purchase Numeric Measure Entered
agreement refunds, reinvestment or other programs.
Sitio/Purok Name of sitio/purok Alphanumeric Attribute Entered
Sponsoring Agency Sponsoring agency of a capacity building program or activity Alphanumeric Attribute Entered
Start Construction Date mm/dd/yyyy Attribute Entered
Start Date of Interruption mm/dd/yyyy Attribute Entered
Start Date of Meter Start date of meter reading for a geography for the month mm/dd/yyyy Attribute Entered
Reading
Start Time of Interruption hh:mm Attribute Entered
Statement Date Statement date of an NGCP bill mm/dd/yyyy Attribute Entered

Status of Payment to The status of an EC’s payment to its power suppliers. For example, Current, Alphanumeric Dimension Defined Current, Restructured-Current, In
Power Suppliers In Arrears. Arrears
If Current Account > 0, Restructured Account = 0, and Overdue Account = 0,

then "Current".
If Current Account >=0, Restructured Account > 0, and Overdue Account = 0,
then "Restructured-Current".
If Current Account >= 0, Restructured Account = 0, and Overdue Account >
0, then "In Arrears".
If Current Account >= 0, Restructured Account > 0, and Overdue Account >
0, then "Restructured-In Arrears".
Substation Brand Brand of the substation Alphanumeric Attribute Entered
Substation Feeder ID Feeder IDs associated with the substation Alphanumeric Attribute Entered
Substation Geography Geographical location of substation Alphanumeric Attribute Entered
Substation Installation Date of installation of the substation in the geography mm/dd/yyyy Attribute Entered
Date
Substation No. of Number of outgoing feeders from the substation Numeric Attribute Calculated
Feeders
Count of Feeder IDs per Substation ID
Substation Owner Owner of Substation Alphanumeric Attribute Entered
Substation Rated Capacity of a substation. Expressed in MVA. Numeric Attribute Entered
Capacity
Substation Serial No. Serial number of the substation Alphanumeric Attribute Entered
Substation Source Source voltage of an EC during non-peak hours Numeric Attribute Entered
Voltage - Off-Peak
Substation Source Source voltage of an EC during peak hours Numeric Attribute Entered
Voltage - Peak
Substation Status Alphanumeric Dimension Defined Operational, Standby, Damaged
Substation Type Type of Substation Alphanumeric Dimension Defined Distribution, Power Plant
Supply Charge A component of the EC rate intended to cover the cost of rendering service Numeric Measure Defined • Retail Customer Charge
to customers, such as billing, collection, customer assistance, etc. • Supply System Charge
Susceptibility to a classification system of geography depending on its susceptibility to Alphanumeric Attribute Entered
Typhoon typhoon
System Average A measure that refers to the average interruption duration per customer Numeric Measure Calculated
Interruption Duration during the period. It is calculated by dividing the sum of customer-minutes of
Index (SAIDI) sustained power interruptions by the average number of customers served
during the period
SAIDI = (total duration of sustained customer power interruptions within a

given period) / (total number of customers served within the same period)
Memo 2013-024
System Average RMS Numeric Attribute Entered
Voltage Index (SARVI)
110
System Average RMS Numeric Attribute Entered
Voltage Index (SARVI) 90

System Loss % The percentage difference between energy input and energy output. System Percentage Measure Calculated
Loss shall be classified into three categories: Technical Loss. Non-Technical
Loss, and Administrative Loss.
System Loss % =((Input Energy - Output Energy)/Input Energy)*100%

System Loss % Forecast Percentage Measure Calculated
System Loss (kWh or The difference between Total Input Power and Total Output Power Numeric Measure Calculated
mWh) expressed in kWh or mWh.
System Loss = (Input energy - Output energy) / Input Energy
Memo 2013-024
System Loss Cap A percentage cap that the ERC shall, after due notice and hearing, prescribe Numeric Measure Configured
on the system loss that the Distributor can pass on to its End-Users.
System Loss Cap = 13%
Source: RA 10531
System Loss Charge Represents the amount recovered by the ECs from their consumers for the Numeric Dimension Entered
cost of power lost due to technical and non-technical losses.
Only 13% system loss can be recovered from the consumers. If EC's system
loss is beyond, such cost is shouldered by the EC.
System Loss Indicator An indicator that states that an EC is non-compliant if its system loss is Alphanumeric Measure Configured Compliant, Non-Compliant
above the System Loss Cap, and compliant if below or equal to the System
Loss Cap.
If System Loss % <= System Loss Cap, then Compliant.

If System Loss % <= System Loss Cap, then Non-compliant.

System Loss Name of EC's System Loss Segregation Calculation Tool (i.e. Synergee, Alphanumeric Dimension Defined Synergee, DSAS, Others, None
Segregation Calculation DSAS)
Tool
Tapping Point From Geography name of a start tapping point Alphanumeric Attribute Entered
Tapping Point To Geography name of an end tapping point Alphanumeric Attribute Entered
Technical - Non- NEA-defined % allocation of technical loss and non-technical loss out of a Numeric Measure Entered
Technical System Loss defined system loss % (i.e. 70/30 for 6% system loss)
Ratio
Technical Loss % A percentage of technical loss over the total Input Energy Percentage Measure Calculated
Technical Loss % = (Technical Loss / Input Energy) * 100%

Technical Loss (kWh or A type of loss within the distribution network resulting from the inevitable Numeric Measure Entered
mWh) physical loss of electricity. This is measured between the metering point read
by the power supplier and the customer connection.
Technical-System Loss Average % allocation of technical loss out of the total system loss of a group Numeric Measure Calculated
Ratio - Average of ECs

Technology Exists? Indicator if the Information, Education & Communication Technology exists in Alphanumeric Dimension Defined Yes, No
the EC or not
Term of Office Term of office of a member of MSEAC or equivalent Numeric Attribute Entered
Term of Office Term of office of a BOD. For example, 1, 2, or 3. Numeric Attribute Entered
Applicable to employees with Position = BOD only.

Terminated from Not required to be reported for Position = Manager or Employee Alphanumeric Attribute Defined Yes, No
Previous Employment?
Total Amount Total amount of a patronage credit/refund Numeric Attribute Entered
Total Charges Includes Basic Charges, Variable Charges, Adjustments and other Charges Numeric Attribute Entered
(excluding VAT and other taxes)
Total Charges Includes Basic Charges, Variable Charges, Adjustments and other Charges Numeric Attribute Entered
(excluding VAT and other taxes)
Total Number of Total number of recipients of a patronage credit/refund Numeric Attribute Entered
Recipients
Total Taxes VAT and other taxes Numeric Attribute Entered
Total Taxes Includes VAT on Ancillary Service, National Franchise Tax, VAT on FIT-All Numeric Attribute Entered
(Renewable)
Town/City/Barangay/or Town/City/Barangay/or Subdivision affected by an interruption Alphanumeric Attribute Entered
Subdivision Affected
Training and Seminar Name of training or seminar attended by a BOD or employee Alphanumeric Attribute Entered
Attended
Transfer of Funds to Numeric Dimension Entered
RFSC
Transformer Brand Brand of Transformer Alphanumeric Attribute Entered
Transformer Serial Serial number of a transformer Alphanumeric Attribute Entered
Number
Transformer Unit ID Identification name or number of a transfer in the substation Alphanumeric Attribute Entered
Transformer Unit no. Identification number of a Transformer unit of a substation Alphanumeric Attribute Entered
Identification
Transmission Charge A component of the EC rate intended to cover the regulated cost or charges Numeric Dimension Defined • Demand Charge
for the use of a transmission system. • Transmission System Charge
Source: EPIRA customer and not aggregated
Transmission Expense Refers to the cost of bulk transfer of electricity (over 69KV). This is only Numeric Measure Entered
applicable to ECs with transmission lines within their scope and
or/ownership.
Type of Accident A classification system of accidents Alphanumeric Dimension Defined Person, Property/Equipment
Type of Type of property/equipment Involved in the accident, if any Alphanumeric Dimension Defined Conductor, Pole, Substation,
Property/Equipment Transformer, Vehicle, Wire, Others
Involved
UC OR. No. A reference number on the document that serves as proof of PSALM's Alphanumeric Attribute Entered
receipt of an EC's remittance of the universal charge.
UC SBR No. A reference number on the document that serves as proof of an EC's Alphanumeric Attribute Entered
remittance of the universal charge.
Unbundled Rate for Refers to the rate multiplied with the customer's consumption to arrive at a Numeric Measure Calculated
Residential Customer power bill. Expressed in PHP/kWh.
Unit Price EC Unit price submitted by an EC Numeric Measure Entered
Unit Price NEA Unit price selected by NEA to be included in the NEA Price Index (or the Numeric Measure Entered
Equipment/Materials Price Index)
Universal Charge Amount in pesos referring to the universal charges collected by an EC. Numeric Measure Entered

Collected
Universal Charge Amount in pesos referring to the universal charges remitted by the EC to Numeric Measure Entered
Remitted PSALM.
Universal Charges (UCS) Refers to the non-by passable charge imposed for the recovery of stranded Numeric Dimension Defined NPC Stranded Contract Cost,
debts (SCC), missionary electrification (ME), equalization of taxes and Missionary Electrification,
royalties applied to renewable sources of energy, environmental charges Environmental Charge
(EC), etc. This is collected by the ECs through the energy bill they prepare
for the member consumers and collected amounts are remitted to PSALM.
Source: RA 9136 Section 34

Urban/Rural A classification system grouping municipalities and barangays based on the Alphanumeric Dimension Defined Urban, Rural
Classification area's level of urbanization. The classification of the municipalities and
barangays are defined by the National Statistical Coordination Board.
Utility Plant A balance sheet component under Assets referring to the value of an EC's Numeric Dimension Calculated 1. Gross Utility Plant (Book Value)
distribution facilities. This is typically stated in gross value (i.e., historical 2. Appraisal Increment
cost) and adjusted according to recorded depreciation values to arrive at a 3. Accumulated Depreciation (Book
net value. Values of assets still ongoing construction may be included as Value)
well. 4. Accumulated Depr. (Appraisal
Increment)
5. Net Utility Plant
6. Const. Work in Progress
Utility Plant per KM Provides an estimate of the value of distribution utilities of an EC. May be Numeric Measure Calculated
Length of Line helpful for comparison across ECs with similar characteristics.
Utility's Monthly Numeric Measure Entered
Coincident Peak Actual
Utility's Monthly Numeric Measure Entered
Coincident Peak
Forecast
Value Added Tax (VAT) Numeric Measure Entered
Variance The difference between two comparable data Numeric Dimension Calculated
Variance % The variance as a percentage of another given measure. Typically used to Percentage Measure Calculated
determine the size of one measure compared to another such as expense as
a percent of revenue.
Was a candidate in the Not required to be reported for Position = Manager or Employee Alphanumeric Attribute Defined Yes, No
last preceding national
or local election?
With a relative within 4th Not required to be reported for Position = Manager or Employee Alphanumeric Attribute Defined Yes, No
Degree of Consanguinity
of Affinity?
With Final Inspection Alphanumeric Attribute Entered
With Spouse Holding SG Not required to be reported for Position = Manager or Employee Alphanumeric Attribute Defined Yes, No
16 or Higher Appointive
or Elective?
Working Capital Liquidity factor of operating capital. Calculated based on a month's worth of Numeric Measure Calculated
power and non power cost.


6.3 Key Process Maps for Data Governance
Process
Reference Process Level 1 Process Level 2 Description
28
Number
T4.0 Data Governance N.A. Key Data Governance processes
T4.1 Data Governance Data Maintenance To identify and validate changes or additions triggered by events such
as new or updated policies or regulations and new BI analysis
opportunities to the master data, templates, data architecture and data
configurations in the system
T4.2 Data Governance Data Upload – Standard To upload data (e.g. equivalent data from MFSR, MER, MIR, audit
findings) from ECs or NEA into the system on a periodic basis under
normal circumstances.
T4.3 Data Governance Data Upload – Special Handling To upload data from EC or NEA into the system that may have issues
and cannot be performed through the "Data Upload (Standard)”
process due to special circumstances (e.g. unreliable internet
connection in the EC’s area, template has not been
completed/uploaded in time for the defined report submission cut-off
date, system in unavailable, data errors that require investigation by the
Data Governance Team, etc.)
T4.4 Data Governance NEA Data Approval To approve the data content uploaded either through the “Data Upload
(Standard)” or “Data Upload (Special Handling)” process to ensure high
quality of data to be stored into the database.
T4.5 Data Governance Data Warehouse Processing To perform ETL of NEA-approved data, storage of data into the
database as well as to generate key output report and dashboards
28
Process Reference Numbers are a continuation of the Process Reference Numbers of the To-Be Process Maps in the Discovery Report Section 7.12.

6.3.1 T4.0 Data Governance
Level 2: Data Governance
T-10 to T0
Data Upload -
Up to T-11 T-9 to T+1* T+2 onwards*
Standard
NEA Data Data Warehouse

Data Maintenance T+1 onwards
Approval Processing
Data Upload –
Special Handling
T0 = Deadline of Submission for a Reporting Month. For example, for Reporting Month January, Deadline of Submission (T0) is February 28.
*Note that output of Data Warehouse Processing could still be incomplete as there could still be some ECs that have not uploaded data up to
this time

6.3.2 T4.1 Data Maintenance
Level 3: Data Maintenance

Management
Governance
Changes
Team
Data
approved? Announce relevant

updates to stakeholders
Data Owners
No
Identify impact to
Data Dictionary, Data
Entry Templates,
Reports, Dashboards
Architecture
Yes
Data
Identify impact to
Data Model
Changes Master Data

required to List Maintenance
System/Data Administrator
of Values
Changes to Template
Templates Maintenance
required
Changes to
Data Data Architecture
Architecture Maintenance
required
Changes to Implement
system changes in the
configuration system
required configuration
Output
Input /
New/Update New BI New Data Impact Impact

Policies and Analysis Required Analysis Analysis
Regulations [For Approval] [Approved]
Interface

Level 3: Master Data Maintenance
EC/NEA
T-13 to T11
Upload Download
Log-in to web
accomplished template with Correct errors
portal
template data errors
Generate file
with identified
System
No
cells with errors
Show
Perform data
Yes confirmation
validation
message
All data valid?
Input / Output
For example,
New BOD; Changes in BOD
information Date and Time of
New Employee; Changes in Employee Data data upload
Data Information
New PSA
New Substation; Changes in Create New, Edit List Template [with
substation information of Values Template Data Errors]
New/edited list of values for other
fields
[Accomplished]
Interface

Level 3: Template Maintenance
Template
required to be
updated
Implement Upload updated Announce that update
NEA
updates in the templates in web templates are available in

template portal web portal
Download latest
Log in to web portal version of
EC
templates
Output
Input /
Template version n
Interface

6.3.3 T4.2 Data Upload - Standard

6.3.4 T4.3 Data Upload – Special Handling
Level 3: Data Upload – Special Handling
Valid for Requires

special correction by
A handling? EC? A
Indicate Upload Download
Log-in to Correct
Yes Reporting accomplished template with No
web portal errors
Month and Year template data errors
NEA
Yes Yes
Proceed Send template Upload

No with data errors attachments
with data
upload? to EC
A
No Email
Correct
accomplished
errors
template to NEA
Email accomplished
EC
template and
attachments to NEA
Data for same

Reporting Generate file Data for same
Month already with identified Reporting
exists? No cells with errors
Yes Month already
exists?
Show
System
Show message Perform data

Yes No confirmation
that data for validation
All data message
same Reporting valid? Yes
Month already
exists
Overwrite
existing data
Input / Output
Date and Time of

Data data upload
Template version n Template [with

[Accomplished] Data Errors]
Interface
Problem NEA Data

Management Approval

6.3.5 T4.4 NEA Data Approval
Level 3: NEA Data Approval
All data valid?

Data Owner
View data Approve data

Yes
requiring approval uploaded
No Reject data
uploaded
Generate file Notify EC that

System
with identified data uploaded

cells with errors has been rejected
Output
Input /
Notification to EC of
Data Rejection
Interface
Data Upload - Data Upload – Data Warehouse

Standard Special Handling Processing

6.3.6 T4.5 Data Warehouse Processing
Level 3: Data Warehouse Processing
Generate ad hoc
reports
NEA
View standard
dashboards
EC
Download
standard reports
Administrator
System
Initiate ETL
No
Data
approved by Generate
Data Owner? standard
System
Perform Store data in dashboards

Yes
automated ETL database
Data to be uploaded
is on or before the Publish standard
Generate
Reporting Month reports in Web
standard reports
deadline? Portal
Output
Input /
Standard Reports Dashboards Ad Hoc Reports

Interface

6.4 Use Case Diagrams
To illustrate the coverage envisioned for the different types of users and how will they be using the web portal and BI, the following Use Case Diagrams are
presented below. Each stick man represents a user type and the circular elements represent the tasks that they will be capable of doing with each solution.
Broken lines express how a task can be succeeded by other tasks ("extending" the task).
Figure 69: Web Portal Use Case Diagram

Figure 70: BI Use Case Diagram

6.5 User Stories
The ECs are the main users of the Web Portal for their submission of populated templates for reporting and corresponding attachments.
# As a/an I want so that Acceptance Criteria Condition/Remarks

I can be confident in my
1 EC user To access the system securely I am logged in the system Internet Connection
document/report transactions
To leave the system when I no I can be confident that the information
2 EC user I am logged out of the system Internet Connection
longer need to use it in my account is safe
Get the relevant templates from I can provide NEA the data according
3 EC user Template is downloaded Internet Connection
NEA to their specific format
To be able to attach documents I can provide NEA its required
Up to 10 mb of file
4 EC user and files relevant to the attachments for checking and Files are attached
attachments are allowed
report/template validation of such data
NEA can note compliance, perform Data is uploaded with up to ___
To send my data to NEA with
5 EC user necessary analysis and provide mb of data including the Internet Connection
attachments
feedback on my performance attachments
To be notified of the incorrect

6 EC user I can revise or change it accordingly There is an error notification
data in my submission
The entire template will be
re-uploaded. This is
necessary because there
To be able resubmit the revised To provide NEA with the corrected
7 EC user Resubmitted revised template are validation calculations
report or data data
which will have to be
checked upon revision of
singular values.
Data uploaded in the last
To view the data that I have
8 EC user I can validate that the data is correct Data uploaded is displayed 12 months can be
uploaded
displayed
To view reports from previous I can analyze and compare data that is Link redirects user to the portal
9 EC user Link to BI portal
months relevant and needed for reports submitted
I can easily view certain files that I Filters;

10 EC user To search files with filters Search result successful
need Search feature

As the key users of BI, NEA will first ensure data acceptance beyond automated validations and approve the EC-submitted templates in the portal. This
provides clearance for the data to proceed to BI where NEA users will analyze the reported data of the ECs.
# As a/an I want so that Acceptance Criteria

1 NEA user To view the data that I have uploaded I can validate that the data is correct Data uploaded is displayed
I can analyze and compare data that is Link redirects user to the portal for
2 NEA user To view reports from previous months
relevant and needed reports submitted
I can be confident in my document/report

3 NEA user To access the system securely I am logged in the system
transactions
To leave the system when I'm not I can be confident that the information in my
4 NEA user I am logged out of the system
using it account is safe
It can be used for analysis and can be
5 NEA user To be able to upload my data Data is uploaded
viewed by the users
To view previous report submissions
I can analyze and compare data that is
6 NEA user with complicated analysis based on View Report with detailed filter
relevant and needed
desired filter
They can be already saved or backed-up to
To be able to tag reports that have
7 NEA user another destination and can be separated Reports are tagged
been reviewed and validated
from those that have yet to be checked
8 NEA user To search data with filters I can easily view certain data that I need Search result successful
To create customized output reports I can easily know the specific information
9 NEA user Report is generated
and analytics that I need
To generate certain reports within a I can create customized reports by date
10 NEA user Report is generated
specific date according to a specific time duration
To give feedback to certain data from It can be used and included as a KPI in EC
11 NEA user Report feedback
the ECs evaluation
The ECs can change their mistakes and the
12 NEA user To request ECs for revisions Revisions Requested
correct data will be recorded to the system
Other users of the system like ERC,
13 NEA user To publish reports DOE,DMC/GMC, GOCC and the public can Reports published online
view them

System administrators ensure that systems are in place for reporting to proceed smoothly.

1 System Admin To create a new user for the system It can allow new users to access the system New user account is added
I can give permissions to different levels of
To manage a user's account for the
2 System Admin access, edit certain information, associate User account has been updated
system
e-mail addresses, etc.
To delete a user account in the I can remove a user for a certain reason
3 System Admin User account is deleted
system (inactivity, removal from position, etc.)
I can organize and decide the documents
4 System Admin To manage system file back up and reports that needs back up and for how File is backed-up
long.
To be able to change the data directly I can change previous reporting data in
5 System Admin Data is changed
from the database case there is a need for it
To be able to access all levels of I can test and consult with IT when there
6 System Admin Validation completed
users are issues or changes
To be able to create queries from time I can make sure that formulas/equations
to time and reports are valid and correct.
To be able to validate and check the When there are changes, it can be
policies uploaded and implemented immediately
I can review, change, add or delete current
To be able to manipulate and manage
9 System Admin data, policies and business rules Managed the master list
the master data
incorporated within the system
There is a standard template where users
10 System Admin To prepare reports/dashboards Reports and dashboards are prepared
can view, follow and use them
11 System Admin To search data with filters I can easily view certain data that I need Search result successful
To validate and approve the reports The data can be used for analysis, reports
12 System Admin Approve EC Reports
submitted by NEA and reference
To be able to upload the reports of
13 System Admin I can aid them when they are unable to do it Upload EC Report
the EC
The ECs can change their mistakes and the
14 System Admin To request ECs for revisions Revisions Requested
correct data will be recorded to the system

Other User Stories
To view the various reports
1 ERC User representing the performance of the I can determine if the EC's tariff is sufficient
EC
To view the various reports
I can assess if whether that EC's potential
2 ERC User representing the performance of the
CAPEX project should be approved or not
EC
I can track the success of the projects I
3 ERC User To view CAPEX project progress
approved
To view/extract data available in the
system such as:
 Supplier and transmission data
 Sales per Class of Service
 Number of customers
Monitor implementation of its decisions as
ERC User  Coincident Peak Report is generated
well as review or craft new policies
 System Loss
 Lifeline Data
 Senior Citizen Data
 Implemented Rates
 Statistics on customer complaints
system such as:
 power consumption by Class of
Service (such as Residential,
Commercial, Industrial) and by
I can plan for the efficient supply and
4 DOE User geographical area served by the Report is generated
economical use of energy
ECs
 system loss by geographical area
 installed generating capacity of
ECs by type (such as Coal, Hydro,
New RE) and by geographical area
GMC/DMC To view the compliance of ECs to the I can identify violations to the PGC and
5 Report is generated
User PGC and PDC PDC
system such as:
6 GMC User Report is generated
 Energy and System Loss per
month

 Substation Capacity
 Peak Demand
 No. of Distribution Transformers
 Total Circuit Length by type of
line/circuit
 Load Factor
 Power Factor
 Interruption
system relevant to NEA’s Key Result
Areas such as:
 Number of energized sitios through
SEP
7 GOCC User  Target number of sitios to be Assess performance of NEA Report is generated
energized
 Number of energized barangays
through BLEP
 Target number of barangays to be
energized
To view/extract data on outstanding
8 DBM User uncollected billings due from any local Report is generated
government unit (LGU)
View same reports as in website now
Member of the
9 (Financial Profile, status of
general public
electrification, etc.

6.6 Cost Estimate Assumptions
6.6.1 Inclusions and Exclusions
Parameters Inclusions Exclusions

30 BI user licenses for developing On-premise software cost includes
Software reports operating system and virtualization tool for
servers.
Applies to both web portal and BI  Production and non-production servers  Network devices and antivirus (NEA
for both web portal (non-OURS) and BI, already has these).
including a virtualization tool  Technical IT training on the following, if
 Shared storage device
29
not yet provided. Estimated costs per
 OS and DB licenses trainee are also presented below for
 Tape drive for back-up reference:
o Server administration (Php 25,000-
40,000)
o Database administration (Php
35,000-60,000)
Hardware o Network administration (Php
100,000)
o Virtualization administration (Php
90,000)
o Cloud architect (Php 75,000)
o Cloud operations and
30
administration (Php 90,000)
o Service Desk Management (Php
31
40,000)
o Information security administration
(Php 100,000)
 100 work stations to be replaced,  CPU w/ OS  Uninterruptible Power Supply (UPS)
32
Other Hardware & Php 35,000 per unit. This may be  Keyboard device
Peripherals reduced once the workstation  Mouse  Office Productivity Suite (NEA is
upgrade plan of NEA is
29
All cost estimates are VAT exclusive.
30
May be provided by some cloud vendors for free.
31
If certification is preferred, the estimated cost is Php 80,000, VAT exclusive.
32
Estimated cost starts at Php 5,000 for typical office use models.

completed as the same  Monitor assumed to have existing license
workstations may be used to agreements to cover this)
access the BI and web portal.
 50 mobile devices to be acquired,
Php 15,000 each
 Development and implementation of  Encoding and verification of historical

web portal is included. data that will be uploaded to the data
 System configuration and warehouse. This can be done by NEA.
implementation activities related to BI  Cost of NEA’s manpower that will be part
are included. of the full-time NEA project
 1 year warranty/support for both web implementation team.
portal and BI (after implementation)  Travel cost to areas outside of Metro
 BI tool training. The implementor may Manila for implementation, information
have different approaches for this. They cascading, road shows, etc.
can either provide non-certification  Production of materials/collateral for
training, and certification training from execution of change management plan
the software vendor. They can either (i.e., tarpaulin printing, copying,
use train-the-trainer, or train the end- professional costs for videography,
users approach. The BI service cost photography, etc.)
Services estimate is inclusive of non-certification
train-the-trainer approach as this is the
minimum training necessary to use and
operate the system.
 Change management planning,
preparation, including change
management plan execution for a
duration of 8 months, a schedule to be
aligned with implementation such that
the last 2 months will be post go-live.
This is applicable to both BI and Web
Portal implementation. The combined
cost of change management for both
systems is already incorporated in the
BI Services cost.

6.6.2 Detailed Cost Breakdown - Commercial Solution BI On Cloud (amounts in PHP)

Commercial BI Solution On Cloud
Services Web Portal 17,000,000 0 0 0 0 17,000,000
Services BI 27,000,000 0 0 0 0 27,000,000
SW 25,208,511 5,545,872 5,545,872 5,545,872 5,545,872 45,339,447
BI
Business Intelligence 8,913,250 1,960,915 1,960,915 1,960,915 1,960,915
ETL 10,400,000 2,288,000 2,288,000 2,288,000 2,288,000
Database 3,275,145 720,532 720,532 720,532 720,532
Web Portal
Database 2,620,116 576,426 576,426 576,426 576,426
HW 2,417,037 3,226,737 3,403,587 3,580,437 3,757,287 15,061,216
BI
Servers
Prod-App Server 135,216 270,432 270,432 270,432 270,432
Prod - Web Server 67,608 135,216 135,216 135,216 135,216
Prod - ETL 11,268 22,536 22,536 22,536 22,536
Prod - DB 278,208 556,416 556,416 556,416 556,416
Nprod - ETL 101,412 45,072 45,072 45,072 45,072
Nprod - DWH 202,824 90,144 90,144 90,144 90,144
Storage
Prod-App Storage 8,925 17,850 17,850 17,850 17,850
Prod - Web Storage 7,140 14,280 14,280 14,280 14,280
Prod - ETL Storage 7,140 14,280 14,280 14,280 14,280
Prod - DB Storage 72,000 216,000 288,000 360,000 432,000
Nprod - ETL 10,710 14,280 14,280 14,280 14,280
Nprod - DWH 24,638 49,275 65,700 82,125 98,550
Portal
Servers

Prod-App Server 135,216 270,432 270,432 270,432 270,432
Prod - Web Server 135,216 270,432 270,432 270,432 270,432
Prod - DB 278,208 556,416 556,416 556,416 556,416
Nprod - WebApp 405,648 180,288 180,288 180,288 180,288
Nprod - DB 405,648 180,288 180,288 180,288 180,288
Storage
Prod-App Storage 11,063 22,125 22,125 22,125 22,125
Prod - Web Storage 8,925 17,850 17,850 17,850 17,850
Prod - DB Storage 72,000 216,000 288,000 360,000 432,000
Nprod - WebApp 13,388 17,850 17,850 17,850 17,850
Nprod - DB 24,638 49,275 65,700 82,125 98,550
Other HW and Peripherals 4,250,000 0 0 0 0 4,250,000
Workstation 3,500,000 0 0 0 0
Tablet 750,000 0 0 0 0
Total 75,875,548 8,772,609 8,949,459 9,126,309 9,303,159 108,650,663

6.6.3 Detailed Cost Breakdown - Commercial BI Solution On Premise (amounts in PHP)

Commercial BI Solution On Premise
Services BI 27,000,000 0 0 0 0 27,000,000
SW 27,114,341 5,965,155 5,965,155 5,965,155 5,965,155 48,767,229
BI System
ETL 10,400,000 2,288,000 2,288,000 2,288,000 2,288,000
Database 3,275,145 720,532 720,532 720,532 720,532
Operating System (Server) 1,040,000 228,800 228,800 228,800 228,800
Virtualization Tool/Platform 865,830 190,483 190,483 190,483 190,483
Web Portal
Database 2,620,116 576,426 576,426 576,426 576,426
HW 6,737,042 0 0 1,010,556 1,010,556 8,499,251
Production Server 1,627,522 0 0 244,128 244,128
Non-Prod Server 291,590 0 0 43,739 43,739
SAN Storage 2,033,070 0 0 304,961 304,961
SAN Switch (2units) 2,004,860 0 0 300,729 300,729
Tape Backup 780,000 0 0 117,000 117,000
Workstation 3,500,000 0 0 0 0
Tablet 750,000 0 0 0 0
TOTAL 82,101,383 5,965,155 5,965,155 6,975,711 6,975,711 105,516,479

6.6.4 Detailed Cost Breakdown - Open Source BI Solution on Cloud (amounts in PHP)

Open Source BI Solution on Cloud
Services BI 27,000,000 0 0 0 0 27,000,000
SW 4,620,116 2,576,426 2,576,426 2,576,426 2,576,426 13,972,271
BI
ETL
Database
Web Portal
Database 2,620,116 576,426 576,426 576,426 576,426
HW 2,417,037 3,226,737 3,403,587 3,580,437 3,757,287 15,061,216
BI
Servers
Prod-App Server 135,216 270,432 270,432 270,432 270,432
Prod - Web Server 67,608 135,216 135,216 135,216 135,216
Prod - ETL 11,268 22,536 22,536 22,536 22,536
Prod - DB 278,208 556,416 556,416 556,416 556,416
Nprod - ETL 101,412 45,072 45,072 45,072 45,072
Nprod - DWH 202,824 90,144 90,144 90,144 90,144
Storage
Prod-App Storage 8,925 17,850 17,850 17,850 17,850
Prod - Web Storage 7,140 14,280 14,280 14,280 14,280
Prod - ETL Storage 7,140 14,280 14,280 14,280 14,280
Prod - DB Storage 72,000 216,000 288,000 360,000 432,000
Nprod - ETL 10,710 14,280 14,280 14,280 14,280
Nprod - DWH 24,638 49,275 65,700 82,125 98,550
Web Portal
Servers

Prod-App Server 135,216 270,432 270,432 270,432 270,432
Prod - Web Server 135,216 270,432 270,432 270,432 270,432
Prod - DB 278,208 556,416 556,416 556,416 556,416
Nprod - WebApp 405,648 180,288 180,288 180,288 180,288
Nprod - DB 405,648 180,288 180,288 180,288 180,288
Storage
Prod-App Storage 11,063 22,125 22,125 22,125 22,125
Prod - Web Storage 8,925 17,850 17,850 17,850 17,850
Prod - DB Storage 72,000 216,000 288,000 360,000 432,000
Nprod - WebApp 13,388 17,850 17,850 17,850 17,850
Nprod - DB 24,638 49,275 65,700 82,125 98,550
Workstation 3,500,000 0 0 0 0
Tablet 750,000 0 0 0 0
TOTAL 55,287,153 5,803,163 5,980,013 6,156,863 6,333,713 77,283,487

6.6.5 Detailed Cost Breakdown - Open Source BI Solution On Premise (amounts in PHP)

Open Source BI Solution On Premise
Services BI 27,000,000 0 0 0 0 27,000,000
SW 6,525,946 2,995,708 2,995,708 2,995,708 2,995,708 17,400,053
BI System
OS 1,040,000 228,800 228,800 228,800 228,800
Virtualization Tool 865,830 190,483 190,483 190,483 190,483
Portal
Database 2,620,116 576,426 576,426 576,426 576,426
HW 6,737,042 0 0 1,010,556 1,010,556 8,499,251
Production Server 1,627,522 0 0 244,128 244,128
Non-Prod Server 291,590 0 0 43,739 43,739
SAN Storage 2,033,070 0 0 304,961 304,961
SAN Switch (2units) 2,004,860 0 0 300,729 300,729
Tape Backup 780,000 0 0 117,000 117,000
Workstation 3,500,000 0 0 0 0
Tablet 750,000 0 0 0 0
TOTAL 61,512,988 2,995,708 2,995,708 4,006,264 4,006,264 74,149,303

6.7 IT Practice Recommendations
For NEA's further guidance in transitioning to a BI-supported organization, IT practice recommendations are
presented in this annex.
6.7.1 Strategy
It is ideal for the current and future IT requirements of the organization be realized based on the mandate,
vision and directions of the organization as upheld by management which will then be translated into specific
and actionable goals and supported by a strategy plan and for continuity, recommendations are as follows:
(i) Establish IT strategic planning as a regular activity supported by management and the departments
collectively with a formal planning process from which annual strategic plans are identified for execution
throughout the year and aligned with the defined long-term strategies and goals of NEA.
(ii) Establish the IT function as an enabler and an asset. The function is not just for technical support but
also in managing and enabling integrated technology needs throughout the organization.
(iii) Enhance, acquire and/or develop technical skills. This is necessary for the organization to not be
dependent on external vendors at all time. Skills may be acquired through training and development of
existing staff, hiring of seasoned professionals, acquisition of professional services that will provide and
transfer the necessary skills to NEA's internal technical staff.
(iv) Establish necessary IT standards that will help guide IT investments. These will help support faster
decision-making and avoid unnecessary investments in non-standard areas. Standards also serve as
guidance in what technical skills to focus capacity building on and protection for investments from challenges
posed by the use of non-standard solutions.
(v) Set up and maintain an industry standard Data Center. This is applicable to organizations with technology
hosted on-premise.
6.7.2 Standards
An IT standard is a technical specification that used in guiding various IT activities – planning, design,
implementation and operations. It defines what an organization would officially use and how. It is important to
have standards as it will serve as the accepted common basis within the organization when making
decisions (e.g. design, plans, purchase, upgrades, etc.). Standards also provide the following benefit:
 Cost savings as it will support economies of scale, skills development and training will be on a fewer
set of tools and technologies, personnel skill set growth will not be disparate, variety of systems to
support will be less
 Faster Time to Market/Deploy. Having standards in place will allow decisions to be made faster.
 Reduces risk as adoption of standards typically require that industry standards which have been
tested are adopted are used/adopted internally. Risks are not totally eliminated but are minimized.
 Better understanding across divisions and with external parties when used as reference during
discussions such as project/contract negotiations, POC, short listing of options, etc.
 Supports Innovation. Standards can serve as the important building blocks when the organization
and its partners/suppliers are doing solution architecting exercises
An initial set of standards to define would be, but are not limited to, the following:
 Standards for Operating System Platforms

 Standards for Database Management Systems
 Standards for Applications and Application System Platforms
 Standards for Middleware and Integration

 Standards for Collaboration
 Standards for Computing and Storage Devices and Technology
 Standards for Web and Mobility
 Standards for Social Media
 Standards for Connectivity (Data and Voice)
 Standards for Information Security
 Standard Frameworks, Methodology, Modeling and Documentation
 Standard Policies
To ensure that the establishment of standards will be successful as well as the use of it will not be too
restrictive to the organization the following recommendations can be adopted:
(i) Establish the role / function of a lead Architect. This role will ensure that the defined architecture
standards for NEA will be compliant to standards.
(ii) Establish a primary, secondary and alternative or limited standards. Although there is a need to have a
standard that needs to be complied with, there are cases where the primary standard will not be able to
support the needs of an enterprise. The secondary, alternative or limited standard is meant to allow for this
minor deviation (during an agreed period) with the goal of eventually complying to the primary standard; and
in cases where it is determined to be necessary, update the standards defined.
(iii) Establish a common repository for the standards to make it easy to be used for compliance, governance
and monitoring as well as when there is a need to update.

6.7.3 Organizational Functions
The section below presents IT organizational functions to serve as guidance in developing IT capabilities in
an organization. Since these are functions, each item need not represent a single person or group and may
be a responsibility shared by a group of persons. Similarly, a number of functions may be handled by a
single person. Should the functions needed not be available in the current organization and/or non-strategic
IT function in nature, such could be acquired by hiring or outsourcing.
Presented below are the main tasks, responsibilities and skills that are covered by each function. Key skills
and competencies of the person/s to be assigned such function are also included as additional guidance.
Information Technology Leadership
Main Tasks and Responsibilities:
 Define and enforce metrics to quantify performance and daily operations

 Establish and implement policies related to Information Technology and Information Systems as
applicable to the organization
 Oversee the development and implementation of standard procedures for hardware, software and
network infrastructure usage
 Keep track of and identify emerging technologies to be incorporated into operations and other
initiatives such as projects
 Develop strategic plans for the continuous improvement of the technology infrastructure and system
portfolio
 Establish and implement short- and long-range goals and objectives to align IT activities with the
organization's growth and ensure current and upcoming projects are appropriately complemented
with the right technology
 Prepare and manage an IT budget
 Direct the information and data integrity
 Oversee all IS/IT project implementations
 Contribute to planning and contracting projects with IS/IT related components
Key Skills and Competencies:

 Thorough knowledge of information technology/systems and industry trends
 Leadership
 Project Management
 Strategic Thinking
 Communication
 People Management
 Change Management
 Risk Management
 Negotiation
Information Security
Information Security is a critical function to ensure that information is managed according to how it is
intended. The objective of this function is to identify, develop, manage, enforce and resolve processes,
procedures, standards and associated documentation relative to security of information systems, networks
and telecommunication to address privacy and confidentiality accordingly. This includes the protection of
information from unauthorized access, modification and destruction as well as the proper education of
employees in maintaining information security in day-to-day activities.

 Oversee the establishment and maintenance of technical computer and network security systems
and protocols
 Oversee the establishment and maintenance of administrative computer and network security
systems and protocols
 Establish and maintain written policies and procedures for the handling and release of information

 Knowledge of security assessment and related incident prevention, detection and recovery
 Attentive to detail
 Organized and meticulous
 Change Management
 Communication
 Teamwork
Operations and Maintenance
IT Operations and Maintenance is responsible for providing for the daily computing needs across an
organization and ensuring smooth day-to-day operations involving all IT-related facilities. For manageability
of scope, responsibilities are further distributed and grouped to Network, Support and Infrastructure
Operations and Maintenance.
Network Operations and Maintenance
This function is responsible for the consistent, reliable and secure network availability for collaboration
needs.

 Enforce and monitor activities to set up, support, manage and ensure operating capability of Voice,
LAN and WAN networks both wireless and wired for all hours of operation.
 Ensure the availability and reliability, install and configure hardware, devices, accessories and
peripherals used to support network connectivity and telephony.
 Establish standard metrics and processes to guide the implementation of network facilities across
NEA.
 Formulate and execute plans for the provision of network improvements
 Plan and manage network security such as the setup of firewalls, managing host security, applying
cryptography to network applications and the performance of regular network monitoring activities to
ensure intrusions are avoided at all times
Key Skills and Competencies
 Specialist Network Knowledge - networking protocols, security principles, remote access services,
etc.
 Network Diagnostics
 Problem Solving
 Teamwork

Support Operations and Maintenance
Support Operations and Maintenance is the central receiver and manager of all communicated IT needs and
ensures that all IT-related needs and requests are properly delegated to the respective persons-in-charge for
immediate resolution.

 Establish, maintain and implement service level agreements in ticket resolution
 Set up a system and processes for sending and receiving, organizing, delegating and responding to
requests
 Formulate support manuals containing standard procedures for recurring requests and guides and
templates for troubleshooting and resolution
 Set up and administration user accounts across systems and tools
 Maintain required master data for application systems
Key Skills and Competencies
 Customer Service
 Communication/Listening
 Patience and Diplomacy
Infrastructure Operations and Maintenance
As the backbone of all IT facilities, it is crucial to have strong Infrastructure Operations and Maintenance to
guarantee the stability of servers, databases, assets and other hardware.

 Ensure availability of facilities for compute and data storage capacity
 Install and configure systems to support the web, mail, database and application Servers
 Plan and perform regular backup and archival activities. This may be daily, weekly, monthly, etc.
depending on the granularity and type of data as well as the media for back up
 Perform regular system monitoring, verify the integrity and availability of all hardware, server
resources, systems and key processes, review of application logs and ensure the completion of all
scheduled jobs
 Ensure hardware, software, and network upgrades, installs, re-installs, changes and relocations are
efficiently completed as required
 Facilitate and monitor the deployment of IT fixed assets such as laptop and desktop computers,
printers, scanners, etc.
 Define and maintain system and technology standards (usually monitored by a lead
solution/infrastructure architect)
 Maintain all IT fixed assets to ensure reliability throughout its defined useful life
 Plan and implement disaster recovery and business continuity plans

 Technical knowledge of systems architecture and server management
 Innovation; Familiarity with recent trends in computing (e.g. cloud computing, mobility, etc.)
 Problem Solving and Troubleshooting
 Teamwork
 Risk Management

Delivery
The objective of Delivery is to ensure that evolving IT needs of an organization are addressed, that each IT
initiative is designed to suit the organization's needs and that all IT investments are maximized. As opposed
to Operations and Maintenance involvement with daily operations, the work of Delivery would be project or
initiative-based.
Service Planning and Requirements Management
This group is responsible for representing the organization to the world of IT and on the other hand,
representing the organization when dealing with external entities such as IT Consultants and Vendors.
 Plan and identify needs computing and automation needs of the organization
 Design automated solutions for implementation
 Configure information systems according to the organization's needs
 Test systems, programs and tools to identify errors and inconsistencies
 Manage and monitor implementation projects
 Facilitate IT implementation related training
 Vendor Management
 Client Management
 Negotiation
 Business Analysis
 Problem Solving
 Presentation
 Facilitation
 Project Management
 Attentive to Details
 Teamwork
 Communication/Listening
Development
The Development Group serves as the technical arm of Delivery. Side by side with Service Planning and
Requirements Management, this group executes the changes to an organization's IT landscape through the
creation of forms, reports and programs.
 Prepare development plans and strategy for solutions identified
 Develop and deploy solutions in the form of automated programs
 Troubleshoot errors and inconsistencies found in information systems and programs
 Test developed programs to ensure quality in development activities
 Proficiency in applicable Development Language/s
 Analytical and Logical Thinking
 Teamwork
 Attentive to Details

6.8 Implementation Project Team
The diagram and table below presents the proposed implementation project team composition as mentioned
in section 5.1 NEA Preparation for Implementation. This team requires its members' full-time attention and
33
dedication for a defined period of time prior to, during and after project implementation.
Figure 69: Project Implementation Team
Table 25 Implementation Project Team
Role Recommended Qualifications Responsibilities

Project Sponsor  Knowledgeable of NEA culture,  Uphold a sense of project ownership
dynamics in behalf of NEA
 A person of authority  Champion and promote the project
 Must believe in the benefits to be  Represent NEA as part of a steering
brought about by the change committee
 Provide overall direction
 Decide on project issues escalated
by the project manager especially for
changes in scope, schedule, quality
and budget
 Perform day-to-day management of
Project Manager Knowledge and experience in:
the project in coordination with the
 IT Project Management consultant PM counterpart
 Resource Management  Communicate management
 Risk Management expectations to the consultant's
 Leadership project team
 Must be familiar with system  Manage issues and risks
implementation  Ensures timely review and approval
 Must be organized of deliverables
 Must be able to adapt to NEA's  Monitor and report project status to
culture while upholding a sense of relevant stakeholders on a regular
authority basis
 Better if this person has experience in  Perform necessary coordination
system implementation project within NEA to be able to obtain final
management with at least 5 members decisions required by the project
33
As opposed to Data Ownership or being part of a Data Governance Team, which is a permanently required role even beyond
implementation though can be transferred to different persons as necessary. Transfer of responsibilities as part of the Project Team
is discouraged as the assignment is temporary and relies heavily on continuous full-time involvement.

 Deep knowledge in reporting and
NEA Process  Lead the standardization of data
analysis of EC data
Experts entry templates
 Must be familiar with BI concepts
 Ensure NEA resources are available
 At least 1 each
for business requirements gathering,
for Financials,
testing, training and other
Technical,
implementation activities
Institutional and
Project  Define NEA’s analysis requirements
Reporting for each subject matter
 Define NEA's reporting processes
and requirements
 Review, validate and approve the
project deliverables
 Act as a resource for each subject
matter
 Provide sample data necessary for
testing
 Participate in user training as a
facilitator
 Could be data owners as well
 Provide technical guidance to NEA
IT Representative Knowledgeable and preferably with
management when needed for
experience in:
decision-making
 NEA reporting processes and  Review technical components of
requirements consultant's deliverables
 Application systems implementation  Analyze and resolve technical issues
(i.e., COTS implementation, or encountered
ground-up development SDLC, agile
or similar methodology)
 BI concepts and technology
 Server, Web/App, Database and
Network, Virtualized Infrastructure
Administration
 Cloud Computing (Architecture,
Operations and Administration)
 Service Management/ITIL
 Basic Information Security Practices
Historical Data Team

In case NEA decides to proceed with the effort of cleansing historical data for upload into the system, a
historical data team will be required.
The functions here can be performed by the NEA Process Experts unless it will prevent them from
participating in project implementation activities. These functions could also be performed by members of
the data governance team as this is a temporary initiative whereas being part of the data governance team is
not.
Table 26 Historical Data Team
Role Recommended Qualifications Responsibilities
Team Leader Leadership skills  Key counterpart of the consultant

project team with regard to historical
data; Represent Historical Data
Team in key project meetings
 Plan the duration of the historical
data clean up and uploading

 Identify the optimum number of
resources needed
 Assign tasks to team members and
monitor accomplishment
Data Validator Financial / Technical / Institutional  Gather data from various sources
Analysis  Define the criteria of acceptability of
a set of data in accordance to the
data dictionary
 Decide on which data to use for each
EC and time period that will be
entered into the standard templates
 May need to validate data with the
ECs
Encoder MS Excel -proficient  Enters validated data into standard

templates
 Ensures all completed templates are
properly populated
 Upload templates to system

6.9 NEA IT Implementation Schedule – Condensed
This is a condensed implementation schedule to present which activities can be shortened, accomplished in parallel and sooner, resulting to an earlier go-
live of the Web Portal and the BI System. The condensed timeline shows that the Web Portal will be implemented two months earlier than the
Implementation Scheduled (Figure 23) in Section 5.2, and the BI system four months earlier.
Figure 70: Condensed NEA Implementation Schedule

NEA Proj Team IT Impelementor WB
1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3
1 Establish a project team x
2 Implementation Planning x x
3 Bidding and Awarding x x
4 Orientation to System Implementation x
5 Implement Web Portal x x
6 Data Cleansing and Alignment (Optional) x
7 Historical Data Upload (Optional) x x x
8 Training/Cascade to NEA and EC End Users x
9 Implement BI System x x
10 Prepare policies, procedures and guidelines x
11 Training on Portal and BI Application Administration (for IT) x
12 Employee orientation relevant to system/s implemented x
Activities to be done by NEA and/or World Bank

Implementation activities to be done by NEA and Implementor
Post-implementation support to be provided by the Implementor

11-12th Floors, Tower 1
Rockwell Business Center
Ortigas Avenue
Pasig City 1600
Philippines
T +63 2 620 3888

F +63 2 620 3889
www.bc.indracompany.com

Design Report v1.2

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Design Report v1.2

Caricato da

Copyright:

Formati disponibili

Design Report

Scoping and Design of IT Systems Upgrade for National

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 1

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 3

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 4

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 5

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 6

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 7

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 8

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 9

Figure 1: BI System Components

Reporting & Analytics

Figure 2: Server Landscape

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 10

Table 1: Hardware Specifications

Service Delivery Options

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 11

Figure 3: Implementation Schedule

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 13

3.1 Data Entry Templates

3.2 Data Models

Figure 5: Cross-Analysis of Subject Areas

P rojec ted Connections

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 17

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 18

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 19

Class of Service Type x x x x x

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 20

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 21

Class of Service Type x x x x x x x

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 22

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 23

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 24

P roject Completion Status

Funding A llocation Details P roject Status ID

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 25

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 26

Table 7: Report to Data Model Mapping

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 27

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 28

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 29

Figure 11: Sample Output Dashboard 1

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 30

Figure 13: Sample Output Dashboard 3

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 31

Figure 15: Sample Output Dashboard 5

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 32

Origin An indication on how the data is entered into the system:

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 33

3.5 Data Governance

3.5.1 Data Maintenance Process

Table 8: Data Maintenance Process Flows

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 34

3.5.2 Data Owner and Custodian

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 35

3.6 Historical Data

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 36

3.7 Data Retention and Archiving

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 37

Figure 17: IT Design for NEA

4.1 Application Architecture

Scoping and Design of IT Systems Upgrade for NEA (Confidential) 38

4.1.1 Business Intelligence (BI)