The province of Prince Edward Island is located on the east coast of Canada and is connected to the mainland
by the Confederation Bridge. It’s the smallest and greenest province. The Island is a place of natural
beauty where the air and water are fresh and clean.
The government of Prince Edward Island (GPEI) wished to create a modern and versatile online Webforms and eServices portal to meet current compliance and mobility capabilities. GPEI approached OpenPlus in need of a solution that allows them to build and deploy eServices with three main objectives.
Generic Online Forms for eServices
Integration with 3rd Party Systems
The Government of Prince Edward Island (GPEI) approached OpenPlus in need of a solution that allows them to build and deploy eServices with three main objectives.
Versatile Online Forms
The solution had to be generic; yet versatile that can support a wide range of Online Services and Web Forms with complex workflows and business requirements.
In order to meet the growing demand for online services, it was important for GEPI to be able to prototype, build and deploy services quickly.
Integration with 3rd Party Systems
GPEI needed a solution that can be easily integrated with their current back-end systems while being future proof for new systems.
OpenPlus began by meeting with variety of stakeholders to understand the user and business requirements,
analyze current online and paper services and all the back-end systems that we need to interact with.
These insights we gain, was the foundation for identifying an opportunity to introduce the eServices product with a vision to help the Government of PEI to quickly build and deploy their online services, while keeping their current infrastructure.
We have built many workflow maps to illustrate the different type of services, the processing of those services and the interactions with back-end systems. Our strategy was approved, and we proceeded with our solution.
A Versatile and Generic Solution
OpenPlus has built a solution that can encompass a variant of online forms. Using our solution, it's
extremely easy to create online forms that can be used as standard fillable forms, to multi-step forms, with
attachments, payment, workflows, notifications, and so on.
Using our solution, GPEI is now able to build a range of eServices, from simple information requests to complex workflows, with calculations and payment processing with full integration with their current systems.
Service Discovery is the main landing page that collects and displays all services, regardless if it’s an
online service, offline or that points to an external service.
The benefit of the Service Discovery page is that all services are indexed in one place, which helps the users to find and search all services.
Standardization and Service Templates
We have created Service Templates to standardize the different services into common and generic service. The
template contains common settings such as is the payment required, does it require a PDF upload, and based
on the service request the template will handle the common requests.
Each template is built to keep the form components consistent, multilingual, localized, and accessible to provide a uniform user experience across different Services.
For the unique service requirements, the Service Template can be extended by GPEI for each service.
Pay Services with Fixed or Variable Cost
No Pay Services
To keep services consistent when collecting or displaying information, our web form solution comes with a
set of widgets. Having standard widgets keeps the user experience consistent and makes it easy to update
widgets across all services.
GPEI can easily clone and modified a Widget for edge cases, or built new ones and plug them into our solution.
Example of Widgets
We have all the standard form fields, from checkboxes to data pickers and then some.
Validation and Formatting
Standard Address Fields
and many more!
Using some of the predefined Templates and Widgets, it becomes extremely fast to deploy a service. As more
Widgets become available, the quicker it will be for GPEI to build new Services, while ensuring consistency
across old and new services.
To deploy a service that requires payment, GPEI would select a Service Template that requires payment, select a Widget to collect user information, address and payment, assign a business process and with one click, publish the service online.
Building a fully functional, mid-size online service with a payment gateway and integration to GPEI’s back-end system takes about 10 minutes.
To integrate with an external service or infrastructure, such as GPEI’s Moneris Payment Gateway or Alfresco
for Business Process Management (BPM), each eService uses APIs and metadata to pass information to the 3rd
The API and metadata are open and standardized formats that contains information about the service, so it can be easily ingested and processed by the external services. With our experience, it has been proven that the open and standardized approach gives great flexibility, scalability and interoperability to a platform and prevents vendor lock-in.
Under the hood powered by OpenSource
For a full case study on this project