request for proposal (rfp) - pvsc open data rfp.pdf · 2016-03-01 · request for proposal (rfp)...

Tel 902.720.7812 Suite 200, Park Place II Toll Free 800.380.7775 238A Brownlow Avenue Fax 902.720.7873 Dartmouth, NS B3B 2B4 www.pvsc.ca

Request for Proposal (RFP) RFP-PVSC-2016-02

Procurement of Open Data Portal Solution Components

For

Property Valuation Services Corporation

At a minimum, the terms and conditions and supplements contained in this document apply to this procurement. By submitting your response to this Request for Proposal (RFP), you acknowledge that you have read and complied with this document. This document is available from Property Valuation Services Corporation at 238A Brownlow Avenue Suite 200, Dartmouth NS or online at: http://www.pvsc.ca/en/home/aboutpvsc/tendersrfps.aspx

Facsimile and e-mail bids will not be accepted for this Request for Proposal.

This Request for Proposal is valid only to 4:00 pm Atlantic

Time on March 23th, 2016.

Request for Proposal prepared by:

http://www.pvsc.ca/en/home/aboutpvsc/tendersrfps.aspx

Property Valuation Services Corporation

i

TABLE OF CONTENTS

1 Overview ................................................................................................................................. 1

1.1 PVSC Mandate ........................................................................................................................ 1

1.2 Open Data Project Overview ................................................................................................. 1

2 Project Scope and Time Frames.............................................................................................. 4

2.1 Open Data .............................................................................................................................. 4

2.2 RFP Schedule .......................................................................................................................... 4

2.3 The following schedule is provided for guidance and is subject to change without

notice. ................................................................................................................................................ 4

2.4 Open Data Service Components ........................................................................................... 4

2.5 Requirements ......................................................................................................................... 6

2.5.1 Functional Requirements ............................................................................................... 7

2.5.2 Non-Functional Requirements ..................................................................................... 13

2.6 Property Valuation Services Corporation Responsibilities ................................................ 14

2.7 Assessment of Contractor Performance and Deliverables ................................................ 15

2.8 Status Reporting and Presentation of Results .................................................................... 15

2.9 Special Conditions ................................................................................................................ 15

2.10 Enquiry Contacts .............................................................................................................. 15

2.11 Contract ............................................................................................................................ 15

3 Evaluation Process ................................................................................................................ 16

3.1 Governance .......................................................................................................................... 16

3.2 Evaluation Scoring ............................................................................................................... 16

3.3 Proposal Addendums ........................................................................................................... 17

4 Proposal Content and Response Guidelines ......................................................................... 18

4.1 Executive Summary ( 3 pages maximum) ........................................................................... 18

4.2 Executive Summary (3 pages maximum) ............................................................................ 18

4.3 Project Approach and Implementation Plan (3 pages maximum) .................................... 18

4.4 Operating Model (3 pages maximum) ................................................................................ 19

4.5 Requirements ....................................................................................................................... 19

4.6 References (3 pages maximum) .......................................................................................... 19

ii

4.7 Pricing Response .................................................................................................................. 19

4.7.1 Fixed Price per Deliverable .......................................................................................... 19

4.7.2 Per Diem Rates ................................................................. Error! Bookmark not defined.

4.7.3 Note Regarding Travel Expenses ................................................................................. 19

4.8 Value Added ......................................................................................................................... 20

5 Packaging .............................................................................................................................. 21

FIGURES & TABLES

Figure 1 – Solution Component Overview ...................................................................................... 5

Figure 2 – Project Governance ........................................................................................................ 5

Table 1 – RFP Schedule ................................................................................................................. 16

Table 2 – Weighing Criteria ........................................................................................................... 15

Table 3 – Key Dates ....................................................................................................................... 15

of 21

1 OVERVIEW

1.1 PVSC Mandate

Property Valuation Services Corporation (PVSC) is an independent, not-for-profit organization funded by Nova Scotia’s 51 municipalities.

PVSC is responsible for valuing all real property in Nova Scotia, approximately 600,000 properties, on an annual basis. Each January, PVSC provides an assessment roll to municipalities, which is used to calculate property taxes, and delivers property assessment notices to every Nova Scotia property owner.

PVSC adheres to mass appraisal standards set by the International Association of Assessing Officers (IAAO), and is mandated by the Nova Scotia Assessment Act and governed by the PVSC Act. The total market value of the 2016 assessment roll was over $103 billion, of which $79 billion is residential and $23 billion is commercial. Last year, PVSC responded to over 40,000 client inquiries, reviewed in excess of 35,000 sales, and reviewed just under 10,000 building permits as part of its assessment activities. PVSC is also responsible for administering the Capped Assessment Program (CAP) and the Seasonal Tourist Business Designation program on behalf of the Province.

Through a joint partnership between PVSC and the municipalities, the Integrated Property Services Council (IPSC) oversees the operation of existing shared services and supports the development of new services. These services include managing common mailing address data, the electronic delivery of tax and utility bills and assessment notices, and a portal for the electronic exchange of building permit and inspection data.

1.2 Open Data Project Overview

Open Data is a growing trend being embraced by governments and private businesses

throughout the world. Citizens increasingly expect greater access to data about their

community and government.

Some reasons behind the push for Open Data are that it promotes:

Transparency and accountability;

Research, innovation, and economic development;

Reduced demand for government services; and

Problem solving and informed decision-making.

Given the potential benefits the PVSC, and more broadly the Integrated Property Services

Council, is interested in offering an Open Data Portal service to enable access to data from a

of 21

variety of sources including the PVSC and municipalities. This RFP is an important step towards

establishing a portal to support such a service.

PVSC envisions the Open Data portal functioning in a “hybrid” model, which allows the portal to

be used in two ways:

1. Direct – In this mode data suppliers upload their data directly to the portal’s data

catalog. Groups and jurisdictions that do not have their own Open Data portal would

use the portal in this fashion. In the following diagram PVSC, CBRM, other

municipalities, and academic institutions fall into this category.

2. Federated – In this mode data suppliers (HRM, NSG) have their own Open Data catalogs,

and these remote catalogs are referenced by the central Open Data portal.

The following diagram shows a conceptual view of the Open Data portal and these two modes

of operation.

Federated Open Data

Catalog

NSG Open Data Catalog

CBRM

PVSC

Other Municipalities

HRM Open Data Catalog

Academic Institutions

Open Data Catalog

Citizen

Researcher

Application developer

Government employee

Business Owner

Other Open Data Catalog

of 21

A consumer accessing the central Open Data portal is able to search for and find datasets that

may reside in a remote portal, thus establishing a single place where a user can find Open Data.

Examples of remote Open Data portals which are now permanent services to businesses and

citizens alike include the Province of Nova Scotia (https://data.novascotia.ca/) and the Halifax

Regional Municipality (http://catalogue.hrm.opendata.arcgis.com/).

https://data.novascotia.ca/

of 21

2 PROJECT SCOPE AND TIME FRAMES

2.1 Open Data

The objectives of this RFP are to:

Select a single partner to develop, host, and support an open data portal for PVSC. This

includes hosting and ongoing support that will be required for a period of 3 years.

Provide a detailed itemization of the functional and non-functional components that are

required to implement the Open Data Portal Service.

Provide proponents with the timeframes and rules for response in reference to the

Open Data RFP.

Provide a summary of the goals and vision associated with the PVSC Open Data Portal

project.

PVSC is interested solely in a commercial off-the-shelf (COTS), cloud based solution.

Respondents may have their own software product, or they may be a services firm offering

implementation of a commercial or open-source software platform. Responses must cover both

the portal software and any necessary implementation services.

2.2 RFP Schedule

2.3 The following schedule is provided for guidance and is subject to change without notice.

Date Milestone

February 29th/2016 RFP issue date

March 10th /2016 Deadline for submission of clarifying questions

March 15th /2016 Deadline for PVSC to respond to questions/issue Addenda

March 23rd/2016 Deadline for RFP responses

April 8th/2016 Vendor Selection

Table 1 – RFP Schedule

2.4 Open Data Service Components

For context the Open Data Service will be made up of several components, each of which fulfills

a specific role as shown below:

of 21

Figure 1 - Solution Component Overview

The purpose of this procurement is to select a single partner for the Open Data Portal, the

Website Interface and User Authentication components. Proponents are requested to provide

a work plan and costing (including both implementation and operation fees) for delivering

these components as a hosted service.

For context figure 2 below shows the proposed PVSC Open Data Portal in the context of shared

services currently overseen by PVSC.

of 21

Connected Systems

Service Center

SAI Mailing Address Service

Open DataAdapter

Infrastructure

PVSC.CA

IPSC Portals(SAI, PDX, eDelivery)

Stakeholders

Stakeholder Interfaces

Shared Services

Businesses Municipalities PVSC

eDelivery Service

iasWorld PictometryNSCAF Uplink

Service

Other Related Services

PublicPublic

ServicesProvincial

GovernmentOther

Agencies

Open DataApps

Permit Data Exchange (PDX)

SNS Property Online

Open Data Portal

Federated Open Data Catalogue

Open Data CataloguesOpen Data CataloguesOpen Data Catalogues

Figure 2 – PVSC Shared Services

2.5 Requirements

This section will outline the requirements for the Open Data Portal. Mandatory (M)

requirements are must have capabilities of the proposed solution. Failure to meet a mandatory

requirement will result in the proposal being disqualified. Rated (R) requirements will be

assessed and scored by members of the evaluation team for the degree to which the proposed

solution meets the requirement. The requirements are outlined as functional and non-

functional. The functional requirements focus on the functionality of the solution where the

non-functional requirements focus on the qualities of the solution.

of 21

2.5.1 Functional Requirements

Functional requirements have been defined for the following areas of the Open Data Portal:

Site and User Management

Social Media and other Channels

Searching, Filtering and Sorting

Data Management

Visualization

Reporting

Auditing

Administration

Metadata

Data Import/Export

For readability, the Open Data Portal is referred to as ‘The Service’.

2.5.1.1 Site and User Management

ID Requirement Mandatory (M) \ Rated (R)

F1 The Service should allow users to self-register for an account.

M

F2 The Service should allow users to manage their own passwords, including choosing their password and retrieving if forgotten.

M

F3 Users should be allowed to comment on and rate data sets

R

F4 The Service shall display to a logged-in user the date and time of their last log in.

R

F5 The Service shall allow a user to delete their portal account.

M

F6 The Service should allow moderation of comments and ratings.

R

F7 The Service shall allow a user to comment on a dataset.

R

F8 The Service shall allow a user to delete any comments he/she created.

R

F9 The Service shall allow a user to flag an inappropriate comment.

R

F10 The Service shall notify a user via email when one of his/her comments has been flagged as inappropriate.

R

F11 The Service shall allow a user to comment on another user’s comment, in a threaded, discussion forum format.

R

of 21


F12 The Service shall allow a registered user to rate a dataset.

R

F13 The Service shall notify the data supplier via email when a comment is made on a dataset he/she owns.

R

F14 The Service shall allow an administrator to create a disclaimer that will be displayed to a user during the account setup process.

R

F15 The Service shall support PVSC branding the look and feel, including setting colours and configuring a logo image, and customizing page headers and footers.

M

F16 The Service shall allow an administrator to create help pages, FAQ’s and user guides that are available within the portal.

M

F17 The Service shall allow a user to notify a dataset owner of an error or omission in the data.

R

2.5.1.2 Social Media and Other Channels


F18 The Service should allow a user to embed in a web page a visualization (e.g. table, chart, graph, or map) created in the portal. Some example scenarios would include allowing a blogger to include a visualization in a post, or allowing a media outlet to include a visualization in an article published on their website.

R

F19 The Service shall allow embedded visualizations to be previewed before being published.

R

F20 The Service shall allow a user to share datasets and visualizations on Facebook.

R

F21 The Service shall allow a user to share datasets and visualizations on Twitter.

R

F22 The Service shall allow a user to share datasets and visualizations on Google Plus.

R

F23 The Service shall allow a user to share datasets and visualizations by emailing a link.

R

F24 The Service shall allow users to subscribe to the Open Data catalogue via RSS.

R

of 21

2.5.1.3 Searching, Filtering and Sorting


F25 A user should have the ability perform an advanced search, specifying keywords as well as specific metadata values (e.g. searching by author, or by date created).

M

F26 The Service shall index text within datasets and use this when executing searches.

R

F27 The Service shall allow a user to navigate and filter search results by certain key metadata (e.g. data type, category, and publisher).

R

F28 The Service shall allow users to search all data sets by keyword.

R

2.5.1.4 Data Management


F29 The Service shall display the following details for each data set: name, description, date posted, date updated, and data supplier.

M

F30 The Service shall store the data supplier of each data set.

R

F31 The Service shall allow administrators to enforce that data sets created by certain users (or user groups) go through one or more approvals before they are made visible on the portal. (Staging of datasets prior to them being made available to the public).

R

F32 The Service shall support setting an owner for each dataset. The owner will typically be the data supplier that created the data set, unless it is being published on behalf of another owner.

R

F33 The Service shall support manual refresh of datasets through a browser interface.

M

F34 The Service should allow subscribers to be notified for newly published or updated datasets (for example, via RSS)

R

F35 The Service shall support the automated refresh of datasets, which can be scheduled for specific days and times.

M

F36 The Service shall allow an administrator to federate a dataset found on an external Open Data portal, so that this external dataset can be found on the local portal.

M

of 21


F37 The Service shall allow an external administrator to federate a data set found on the local Open Data portal, so that the local dataset can be found on the remote portal.

M

F38 The Service shall allow versioning of datasets, so

that old versions of the data set are still available

as the dataset is updated. Versions shall be tagged

with the date and time of the update as well as

who made the update.

R

2.5.1.5 Visualization


F39 The Service shall allow a user to view tabular data sets in their browser.

M

F40 The Service shall allow a user to sort tabular data sets.

M

F41 The Service shall allow a user to view geospatial data on a map within the portal.

M

F42 The Service shall allow a user to search for geospatial data on a map within the portal.

R

F43 The Service shall allow a user to create charts (bar, line, and pie charts) directly in the portal.

R

F44 The Service shall allow a user to save maps or charts created in the portal.

R

F45 The system shall allow the use of different base maps, open license services like OpenStreetMap.

R

F46 The Service shall support the use of satellite and/or aerial photography imagery for the display of spatial data.

R

2.5.1.6 Reporting


F47 The Service shall provide a report of the number of downloads per dataset

M

F48 The Service shall provide a report of the number of API calls, with resolution down to the number of calls per developer account.

R

F49 The Service shall provide a report of the number of page views.

M

F50 The Service shall provide a report of the number of shares done through each social media platform (Facebook, Twitter, Google Plus, email).

R

of 21


F51 The Service shall provide a report of the number of visualizations created, including the type (e.g. chart or map).

R

2.5.1.7 Auditing


F52 The Service shall provide a report of comments flagged as inappropriate.

R

F53 The Service shall provide tracking and reporting on creation, modification, federation, and deletion of data sets, including a user ID and timestamp.

R

F54 The Service should include statistics enabling PVSC to understand the value of the service in terms of portal visits, dataset downloads and API usage.

R

2.5.1.8 Administration


F55 The Service shall provide a report showing the amount of data stored in the portal, with the ability to drill down into details to see what the largest datasets are.

R

F56 The Service shall provide a report showing the activity of data supplier, including the number of data sets created and updated per supplier.

R

2.5.1.9 Metadata


F57 The Service shall have ability for an administrator to add/edit/remove metadata for a dataset.

R

F58 The Service shall allow data suppliers to upload or populate metadata using industry standard metadata formats or custom metadata formats.

R

F59 The Service shall have the ability for all users to easily view the metadata associated with any dataset.

R

of 21

2.5.1.10 Data Import/Export


F60 The Service shall allow users to export and download tabular data sets in the following formats:

1. JSON 2. CSV 3. PDF 4. XLS 5. XLSX 6. XML 7. RDF

R

F61 The Service shall allow users to export and download spatial data sets in the following formats:

1. ESRI shapefile 2. KML 3. KMZ

R

F62 The Service shall allow a publisher to upload geospatial data in the following formats at a minimum:

1. ESRI shapefile; 2. ESRI file geodatabase 3. KML

R

F63 The Service shall allow all spatial datasets to be uploaded in a commonly used projection i.e. NAD83 CSRS or WGS84.

R

F64 The Service shall allow a publisher to upload a tabular dataset in the following formats: • csv (comma-separated value) • ODS (OpenDocument Spreadsheet) • Excel

R

2.5.1.11 Non Functional Requirements

The following section covers requirements relating to the qualities of the system, as opposed to

its functionality. Many of these requirements are technical in nature:

Usability

Integration

Extensibility

Privacy and Security

Technical Architecture

Integration

Maintainability

of 21

2.5.2 Non-Functional Requirements

2.5.2.1 Usability


NF1 The Service shall be responsive and accessible via modern browsers including Internet Explorer, Chrome, Firefox, and Safari and should not be bound to a particular version or browser.

M

NF2 The Service shall be accessible via mobile (smartphone and tablet) browsers, including those on iPhone/iPad and Android devices.

R

2.5.2.2 Integration


NF3 The Service shall provide a web-based API that application developers can use to build applications that pull data from the portal.

M

NF4 The Service’s API shall support one or more of the following formats for geospatial datasets:

1. GeoJSON 2. WMS (web map service) 3. WFS (web feature service)

M

NF5 The API shall support querying and retrieval of subsets of data so that the entire dataset does not have to be retrieved each time.

R

2.5.2.3 Extensibility


NF6 The Service shall provide a mechanism to extend the functionality of the site via customization or a plug-in/module mechanism.

R

2.5.2.4 Privacy and Security


NF7 The Service shall support access over https. M

NF8 User data shall not be used or shared by any other companies.

M

NF9 The Service should have a mechanism built into platform to keep data secure (e.g. password policies, role-based security)

M

of 21

2.5.2.5 Technical Architecture


NF10 The vendor will provide a high-level view of their technical architecture showing the components (servers, databases, and network connections) that make up the solution.

R

NF11 The Service should be delivered through a cloud-hosted model, where the vendor hosts the portal software on the client’s behalf.

M

NF12 The vendor should offer an option for a client to host the software on premise in their own data centre.

R

NF13 For on premise deployment, the system shall support running in a virtualized server environment.

M

2.5.2.6 Integration


NF14 The Service should support federation of datasets that reside on a remote Open Data portal.

M

NF15 Federation with a remote portal, running on the same software platform should be supported in the base product (i.e. without customization).

M

NF16 The Service should provide an API to support access by third-party software applications.

R

2.5.2.7 Maintainability


NF17 The Service should be capable of downloading security patches and product updates. The Service should have a mechanism in place to alert users about such updates/patches.

R

2.6 Property Valuation Services Corporation Responsibilities

The PVSC will provide the successful proponent with access to a project sponsor and primary

contact within the PVSC. This person will be the contact for all communications with the PVSC,

periodically meet with the proponent to monitor the progress of the project, work with the

of 21

proponent to identify potential problems early and possible solutions. Any problems or

concerns must be identified to this person immediately.

2.7 Assessment of Contractor Performance and Deliverables

All deliverables must be approved by the PVSC Executive.

2.8 Status Reporting and Presentation of Results

Regular status updates are to be prepared as determined by the PVSC.

2.9 Special Conditions

The PVSC reserves the right to approach the successful proponent for additional requirements

outside of this proposal. The cost of the additional requirements will be agreed upon between

PVSC and the supplier.

2.10 Enquiry Contacts

Proponents requiring further information on this Request for Proposal should contact Cheryl

Fenerty from the PVSC by email at [email protected].

All enquiries are to be directed to the person(s) named above. Information obtained from any

other source is not official and may be inaccurate. Enquiries and responses may be recorded

and may be distributed to all proponents at the option of PVSC.

2.11 Contract

The successful proponent will enter into a standard contract for services with the PVSC. At the

least, this document will include the vendor name, contact information, per diem rate, critical

dates, etc. A ‘Schedule A’ will be included to reference the tender documents and the proposal

submitted by the successful supplier, and may be expanded to reference any correspondence

or clarifications.

The term of the contract will be for 3 years with the option for up to 5 successive 2 year

extensions at the sole discretion of the PVSC. Revised costs may be negotiated as part of the

extension process.

of 21

3 EVALUATION PROCESS

3.1 Governance

The following reflects the governance structure in place for the project and the level of

authority governing this RFP

Figure 2 - Project Governance

PVSC Board of Directors

Integrated Property Services Council

Open Data Evaluation Team

An evaluation team is established representing Open Data stakeholders, business and technical

staff to evaluate and recommend a preferred vendor to the Integrated Property Services

Council (IPSC). The IPSC will accept or reject the recommendation and forward the

recommendation to the PVSC Board of Directors for final approval.

3.2 Evaluation Scoring

Proposals will be evaluated iteratively throughout the process using the following criteria and

associated weighting.

Criteria Weight Description

Executive Summary

5 Assess the maturity, stability and strength of the vendor.

Project Approach and Implementation

10 Assess the degree to which the project plan/process meet the proposed solution requirements and impact on stakeholders/time to market.

of 21

Operating Model 10 Assess the completeness, impact on stakeholders, of the proposed model for support.

Functional Requirements

20 Assess the degree to which functional requirements are met by the proposed solution option.

Non-Functional Requirements

15 Assess the degree to which non-Functional requirements are met by the proposed solution option.

References 20 Assess the experience, familiarity and success the vendor demonstrates with the solution option through similar engagements.

Pricing Response 20 Cost will be based on the following formula: (lowest implementation cost/proponent implementation cost) * 8 + (lowest operating cost/proponent operating cost) *10 + (lowest blended per diem rate/proponent per diem rate) * 2

Value Added 0 Can add up to an additional 5 points

Table 2 – Weighting Criteria

3.3 Proposal Addendums

The proponent is responsible for obtaining any addendums issued to this RFP. Vendors are to

note in the executive summary that they acknowledge receipt of any published addenda.

Addendums will be posted on the pvsc.ca website at the following location:



of 21

4 PROPOSAL CONTENT AND RESPONSE GUIDELINES

The proposal and financial attachments should include the following sections, described in

more detail below:

Executive Summary;

Proposed Team;

Project Approach and Implementation Plan;

Operating Model;

Requirements;

Contact Information for References;

Pricing Response;

Value Added

4.1 Executive Summary (3 pages maximum)

High level (2-3 page) description of the key elements of your proposal and a brief description of

your organization.

Years in Business;

Size of the Organization;

Number and nature of clients;

Past experience with projects of similar size and nature;

Ability to meet deadlines and provide quality assurance;

Ability to research new and creative solutions;

Ability to respond to unforeseen difficulties;

Your plans for continued development and enhancement for your solution components

over the next 3-5 years (product road map).

Provide brief overview on the proposed implementation team, including Proponent Executive

Sponsor. Provide a biography/resume for the Proponent Engagement Lead and/or Project

Manager.

4.2 Executive Summary (3 pages maximum)

Provide brief overview on the proposed implementation team, including Proponent Executive

Sponsor. Provide a biography/resume for the Proponent Engagement Lead and/or Project

Manager.

4.3 Project Approach and Implementation Plan (3 pages maximum)

The Proponent must describe the following topics as they relate to the Open Data Portal

implementation:

of 21

Approach and work breakdown schedule outlining the activities, tasks, key

dependencies and timeline (including a GANTT chart) from the time of procurement

award to post-implementation steady state; and,

Key assumptions and constraints.

4.4 Operating Model (3 pages maximum)

Please summarize your operating model as outlined below:

Describe the help desk services provided;

Describe your process for communicating, prioritizing, and addressing application

problems of varying severity levels;

4.5 Requirements

For each of the requirements outlined in section 2.5 explain how the proposed solution meets

the requirement. Download and complete the requirements template and include in your

response. The template is can be found at:


4.6 References (3 pages maximum)

Please a brief summary and contact information for three references for solution

implementations similar to the requirements outlined in this document.

4.7 Pricing Response

4.7.1 Fixed Price per Deliverable and Per Diem Rates

Download and complete the pricing response template and include in your response. The

template is can be found at:


4.7.2 Note Regarding Travel Expenses

Travel expenses will be granted only for projects that require the successful proponent to travel

away from the work location (PVSC) for project work. Expenses connected with travel of

resources to the work location are the responsibility of the successful proponent



of 21

4.8 Value Added

Please describe additional features of your implementation plan and operating model that may

be of interest to PVSC and Integrated Property Services Council members including, but not

limited to:

Sustainable and environmentally friendly business practices;

Contribution to Nova Scotia economy; and,

Additional current or planned capabilities beyond those requested in this document.

of 21

5 PACKAGING

One original and 8 copies of all documents submitted are required. The original shall be left

unbound and clearly marked ORIGINAL on the title page and all copies shall be clearly marked

COPY on the title page. The original will be retained by PVSC as the official record of

submissions received. The original and all copies must be identical. In addition, a virus free

memory stick or cd containing electronic copies of all documents is required.

All documents are to be printed on one side, using Letter size paper (8.5” x 11”), single spaced

in 12 point font (10 point font is acceptable for tables and graphics). Legal size (8.5” x 14”) may

be used in landscape mode and folded for GANTT charts.

Proposal package to be delivered to:

Cheryl Fenerty, Manager, IT/IM, PVSC

Suite 200, Park Place II

238A Brownlow Avenue

Dartmouth, NS B3B 2B4

request for proposal (rfp) - pvsc open data rfp.pdf · 2016-03-01 · request for proposal (rfp)...

Documents