Table of Contents | Next Page: Open Standards -> |
Introduction
The objective of this whitepaper is to outline the drivers, benefits, risks, considerations, and governance taken into account when determining when and where to adopt Open Standards and use as well as contribute to Open Source Software (OSS). This whitepaper captures the Government of Canada’s (GC) approach to move towards a more open environment which includes changes in how we work, purchase solutions, and provide information and services to Canadians.
Scope
This whitepaper has for scope the following elements: Open Standards; OSS Use; OSS Contribution (which includes publishing OSS); Open Markets; Open Culture; and some common Legal Considerations. Each concept will have the following structure: the benefits; the risks and drawbacks; and best practices.
The following concepts are not part of the whitepaper as they have their own dedicated teams and communities: the broader Open Government initiatives including the Open Government Partnership, Open Data, Open Information, Open Dialogue, Open Science. Their importance is nonetheless recognized as critical to an open and transparent GC.
Strategic Environment
Organizational Overview
Openness and transparency are fundamental to ensuring Canadians’ trust in their government and in democracy overall. Citizens expect their government to be open, transparent, and accountable. They also expect their government to deliver real, meaningful results, in a fair, efficient, and responsible manner. The GC’s commitment to openness is intended to foster greater transparency and accountability, and to help create a more cost-effective, efficient, and responsive government for all Canadians. (Third Biennial Plan to the Open Government Partnership)
The GC is committed to raising the bar on openness and transparency. The ministerial mandate letters sent to each of the Cabinet Ministers reinforces expectations that all federal departments and agencies will do their part to ensure an open, honest government that is accountable to Canadians, lives up to the highest ethical standards, and advances Canadians’ priorities with a renewed sense of collaboration.
We are delivering on that with the Open Government Portal that enables searching GC open datasets and open information digital records. Canada has also been an active Open Government Partnership (OGP) member since 2012; In September, 2017, Canada came first in the election of the new OGP Steering Committee members, and assumed its seat on the Steering Committee. Canada will also be hosting the OGP Global Summit in Ottawa in May 2019.
In October 2017, Treasury Board of Canada Secretariat (TBS) reached a Memorandum of Understanding (MOU) concerning Digital Government with the United Kingdom that includes open data and open government, but also add other principles of digital development such as open standards, OSS and open markets.
Soon after, the GC Strategic Plan for IM and IT 2017-2021 included a new planned action to introduce a strategy for use of OSS and open standards. TBS will lead the development of a strategy to set direction for the government on the use and release of OSS and open standards that will be ratified by GC EARB.
In December 2017 the GC EARB members endorsed that GC EARB supports the formalization of a common GC-wide approach to the adoption of open source within government, resulting in a more robust open community within the GC.
In February 2018, Canada signs the Digital 7 (D7) charter and joins Estonia, Israel, South Korea, New Zealand, the UK and Uruguay committing to working towards core principles of digital development, with a focus on user needs, open government, and a commitment to share and learn from D7 member nations. The D7 charter, which also calls for commitments to open standards, OSS, open government and teaching children to code.
In May 2018, TBS reached a MOU on cooperation in the field of digital government and economy with Estonia, a fellow member of the D7 and the OGP.
Business Need
The GC’s departments and agencies need to find effective ways to offer the best digital services possible to citizens and users. This implies working in the open by default, by releasing all non-sensitive data, information and source code under an open licence that enables sharing and reuse. There’s a need for improved interoperability between systems; more independence from data formats, software, technologies and vendors; substitutability of solutions and service providers and; avoiding lock-in to enable greater flexibility in the management of IT solutions. The GC also needs to attract digital talent and increase job satisfaction by embracing leading practices and the latest technologies. Finally, the GC must provide public benefits to the public-at-large as well as support the Canadian economy and communities.
Drivers for Change
Policy
In recent years, the GC has taken multiple steps towards being a more open organization, including commitments to open Government, use open standards and OSS as well as release source code under an open licence. These commitments are in Memorandums of Understanding around digital services, with D7 partners, the United Kingdom and Estonia. The ministerial mandate letters sent to each of the Cabinet Ministers reinforces expectations that all federal departments and agencies will work in the Open by default. These policy changes challenge the status quo and force the various organizations of the GC to adapt their technologies.
Technology and Efficiency
Leveraging technologies that are built on open standards mitigate against the risk of lock-in and offers the interoperability, independence and substitutability required to design enterprise level applications and services. OSS by default encourages the use of open standards and their inherent flexibility enables rapid response to changing missions and markets as well as swift provisioning of both known and unanticipated users.
Using OSS means you can benefit from solving common problems with readily available technology and you have more time and resource for customized solutions to solve the rare or unique problems. OSS is particularly suitable for rapid prototyping and experimentation. The testing process generates minimal costs, and encourages the identification and elimination of defects not recognized by the original development team. For the public sector, like all organizations, cost is important, but other public benefits can also motivate public sector use of OSS.
From a support and maintenance perspective, OSS - as opposed to more burdensome usages of proprietary software and their users licences - provides a real cost advantage where multiple copies of software are required, or when the user base grows. Since there is no need to manage individual user licence, the focus is more on maintaining the application itself. Using OSS and service providers also helps avoid lock-in as it is possible to seek other service providers to support the maintenance and development of the solution.
Economy
Adopting and using open standards means it is possible to move between different technologies when needed, thus avoiding lock-in and opening up the range of companies that the organization can purchase from. Doing so would encourage more of them to use the same standards and encourage a wider range of both open source and closed-source software.
OSS provides an advantage in that it creates an open marketplace for providers of all types of support. Any support business with sufficient software development competencies can add new features and fix bugs in the software; OSS users can also switch to a different support provider whenever an existing company no longer meets their needs or timelines. Using OSS may better support local businesses in Canada as it would encourage Open Markets.
Community, Demography and Society
Citizens expect accessibility, official languages and continuous improvements of digital services provided by the GC. The flexibility of using OSS compel GC to meet user needs by modifying existing or creating new OSS.
Canada has set a very clear Open Government mandate to “create greater transparency and accountability, increase citizen engagement, and drive innovation and economic opportunities through open data, open information, and open dialogue”. Sharing in-house software programs under an OSS licence naturally align with the role of public administrations in providing wide benefits to the public-at-large, such as in maintaining society’s technological infrastructure and helping it evolve. OSS can also help maximize overall economic efficiency within society. Where software is freely available, and where anyone can add any new features needed, companies can make use of these existing resources rather than expend effort duplicating an existing project.
Releasing an in-house software code under an OSS licence can encourage external contributions and collaboration from governments, companies, students and citizens in the form of source code, bugs and documentation. The project can be a joint effort amongst multiple companies, public sector workers, and individual volunteers. Releasing software as OSS to encourage others to collaborate on it can also help ensure the viability of a project into the future. The release of OSS by public sector organizations can also help stimulate innovation in the private sector. It enables companies to create specialized offerings built on OSS, even where such software might otherwise be too expensive for the company to develop in-house.
Business Outcomes
The expected results of the GC working in the open, using open standards and open source software are as follows:
- Canadians are able to find, use and contribute to GC software projects and source code as well as open source software used by the GC to support meaningful engagement with their government and communities.
- Enable greater flexibility in the management of information and communication technologies (ICT).
- Support and increase collaboration with other public administrations in Canada and around the world.
- Improve the overall availability of re-usable technology within government and society.
Strategic Fit
The GC Digital Playbook includes principles on the use of open standards to ensure your system works and communicates with other products or systems, and can easily be upgraded and expanded; the use of OSS since, by their nature, they are publicly available specifications, and the availability of their source code promotes open, democratic debate around their specifications, making them both more robust and interoperable; and working in the open by making source code open and reusable under an appropriate OSS licence, so that other developers can benefit from your work and build on it.
There are great opportunities to learn and engage with our D7 partners, for example by aligning and collaborating with the UK Open Standards Board on selecting open standards for government.
Detailed Description of the Business Need
Problem/Opportunity Statement
Open standards and OSS are only slowly gaining traction in the GC, particularly when compared to the private sector and other public administrations (US, UK, France, Italy, Estonia, New Zealand, etc.). Relatively low levels of adoption have been attributed to a lack of understanding of the potential benefits, accompanied by a risk-averse technical and procurement culture, compounded by significant levels of misconceptions.
Open Standards are essential to ensure interoperability between systems and enables easier migration and transitions to different systems. More so, the use of OSS supports interoperability and information sharing and should be considered in the assessment of IM-IT solutions. Both help mitigate the risks of lock-in, enable the GC to support for the Canadian economy and open communities, provide lower total cost of ownership, attract top digital talent and lead to better job satisfaction.
If TBS wants the GC to become an open organization and shift to a more open culture especially around digital and technology, it should strongly endorse the adoption of open Standards for data, information and communications; the use of OSS in our technology stack; contributing to upstream development of OSS; releasing code developed internally under OSS licenses and collaborating more widely with other public administrations in Canada and around the world.