Download Section 3: Terms of Reference (TOR)

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Prognostics wikipedia , lookup

Intelligent maintenance system wikipedia , lookup

Transcript
Section 3: Terms of Reference (TOR)
BACKGROUND
IRENA is operating a database of energy statistics for more than 180 countries, in cooperation with
the International Energy Agency and the United Nations. IRENA federates the statistical databases of
those organisations, details the information for each renewable energy source, and improves the
accuracy of the renewable energy statistics. The database is continuously updated in cooperation with
the IRENA members, and contains validated information up to 2011.
The management of the database is currently done manually, with very large Excel files. A prototype
database using SQL Server was designed in house in 2011, which was not connected to an interface
application.
A user interface and data management tools, such as queries, data extraction and data manipulation,
need to be developed, to allow a user-friendly, consistent and secure management of the data. The
structure of the prototype SQL database needs to be modified to respond to the functionalities of the
interface.
In this context, IRENA is looking for an external software developing firm to create the tools needed
for its data warehousing and data management.
OBJECTIVES AND SCOPE
While a prototype of the database SQL has been developed in 2011, its architecture needs to be
validated and adapted to the requirements of the future user interface. A high-level scope of the
interface project is given below. The annex provides a description of some features of the application.
Scope
User management
Database
maintenance
Transfer mechanism
Data manipulation
functions
Macro language
User interface
Data transfer
Database history
Training and closure
The solution should provide different levels of access to the database:
administrator, read, write.
The solution should enable users to insert, update and delete records in
database tables.
The solution should enable users to transfer data from other databases and
Excel files to the SQL database, and to export data into other formats,
including but not limited to Excel and csv.
The solution should enable users to perform operations including but not
limited to the basic four operations, merging/demerging dimensions, handling
data qualifiers, conditional operations.
The solution should include a macro language that allows if conditions and
loops plus all the data manipulation functions listed above, with a recording
engine, macro management tools (create, save, delete, load, change) and
documentation.
The solution should allow the display of data as time series in an Excel-based
environment and all the functionalities listed above.
The solution should allow the data transfer between the internal and external
databases.
The solution should include a log of all changes to the records in the database
that can be used as a “restoration table” to undo changes that were made.
The developer of the solution should provide all the tools, training and
maintenance necessary for the effective use of the solution, including but not
limited to: system usage guides, trainings for administrators, developers and
users, system documentation, system maintenance contracting, system support
1
and system upgrades
The creation of the statistical application and associated databases is the first step towards the creation
of a website-based statistical information system that allows the external users to make personalised
queries and visualise the data, which will be developed separately. The statistical application, internal
and external databases should therefore be developed using formats that are not proprietary.
MILESTONES (Provide a project implementation plan indicating time required )
Milestone
Time period
Task
Deliverable
Define with IRENA the functionalities of the
system. Evaluate the current architecture of the
database and amend it if needed after
consultation with IRENA.
Catalogue of system
functionalities. Assessment of the
database structure and proposed
new structure for validation by
IRENA
Develop, test and validate the application user
interface, functions, menus, dialog boxes and
forms in consultation with IRENA. Develop,
test and validate a macro language, macro
management tools and documentation.
User interface with full set of
functions, menus, dialog boxes
and forms; macro language,
macro management tools and
documentation
Develop the user management system and
database maintenance functionalities with
documentation
User management system and
database maintenance
functionalities and documentation
Create the data transfer mechanism between the Data transfer mechanism between
internal and external databases, keeping in mind the internal and external databases
the ultimate goal of having a database accessible
from the Internet with functionalities such as
data extraction, dynamic maps and dynamic
charts.
Transfer the existing database into the new one
and perform integrity tests.
Database transferred, integrity
tested and validated
End user training
End user training
Go live
Go live
3 to 4 months
TOTAL DEVELOPMENT TIME
Post go-live support (onsite or remotely)
Post go-live support
2 months
Warranty
Warranty
6 months
Criteria for evaluation of offers
I. Evaluation
The Technical evaluation will consist of three stages:
2
1. Stage one: the technical proposals shall be evaluated based on the criteria listed hereunder in
table 1. The passing score for this stage is 70%, which will qualify the proposers to the
following stage.
Overall weight for this stage is 60%
2. Stage two: all companies who attained the minimum passing in stage one, shall be invited to
present a demo on the ERP software solution suggested in their technical proposal. The demo
criteria are listed hereunder as table 2. Overall weight for this stage is 40%.
3. Stage three: scores from stage one and stage two will be calculated. Those who attain 70%
and above shall have their financial proposals open.
The overall evaluation score will be on a combination of the technical score (60%) and the financial
score (40%).
Technical evaluation criteria:
Table 1:
Technical Proposal Evaluation Form
Points
Company
Obtainable
A
B
C
D
E
Technical component: The obtainable number of points specified for each evaluation criterion
indicates the relative significance or weight of the item in the overall evaluation process.
1. Technical Approach [45 points]
1.1 Company technical profile
5
1.2 Approach designed to implement the Software
10
1.3 Project management implementation plan to be
15
submitted including the time frame for
implementation.
1.4 Experience in solution software industry
15
including similar projects. Three references of
past development including a portfolio
demonstrating the work.
2. Software integration and technology [15 points]
2.1 The suggested solution should be based on
10
technology that is already available.
2.2 The solution must be able to integrate within the
5
current IRENA system as needed.
3. Personnel [40 points]
3.1 CVs for system analyst, developer and project
40
manager who should have a minimum of 5 years
of experience in software development.
Table 2:
Presentation of the Proposed Solution Total time: 30 minutes
1.
Introduction (10 minutes)
Demo of proposed interface features (20 minutes)
Total
Score
Weight
100
Points
Obtainable
100
3
Annex:
The tables in the database have up to 6 dimensions:
- Country (with up to 250 elements)
- Time (elements can be years, quarters, months)
- 4 other dimensions with up to 100 elements in each
Each combination of elements (one from each dimension) is linked to a unique value. For example:
Country: World
Time: 2010
Product: Hydro
Flow: Electricity generation
 Value is 3437483
Each data point is composed of a numerical value and a qualifier. Examples of qualifier are:
 Observation (default setting)
 Estimate (“e”)
 Not available (“..”)
 Not applicable (“x”)
 Confidential (“c”)
There should be at least three visualization modes in Excel (“|” indicates the limits of cells):
- Values only (e.g. 10)
- Values with qualifiers in the same cell (e.g. 10e)
- Values with qualifiers in two different cells (e.g. 10|e)
It would be good if the possibility to have text values in a dimension could be explored.
4