© Crown copyright 2015
This publication is licensed under the terms of the Open Government Licence v3.0 except where otherwise stated. To view this licence, visit nationalarchives.gov.uk/doc/open-government-licence/version/3 or write to the Information Policy Team, The National Archives, Kew, London TW9 4DU, or email: email@example.com.
Where we have identified any third party copyright information you will need to obtain permission from the copyright holders concerned.
This publication is available at https://www.gov.uk/government/publications/open-document-format-odf-procurement/open-document-format-odf-and-procurement
The UK government has selected ODF as the standard for editable office documents to be used across government. ODF was selected as the standard for government because it:
- allows citizens, businesses and other organisations to share and edit documents with government – and vice versa
- allows people working in government to share and edit documents with each other
- is compatible with a wide range of software
- is a reliable long-term solution for storing and accessing information
When procuring an application, product or service that deals with editable documents and their lifecycle you must make sure your specification includes ODF compliance. Editable documents include text documents, spreadsheets and presentations. A document’s lifecycle involves creation, viewing, changing (including revisions), exchanging and archiving.
Documents that are for viewing rather than editing, eg PDFs, must also comply with a separate set of open standards. Read about open standards and how they relate to procurement in the UK government’s Open Standards Principles.
Buying products and services based on ODF
Make sure the ODF requirement for services and products is clear in your tender documentation, particularly in the tender specification. Your contract should specify that the supplier is required to ensure ODF support at the time of deployment, according to the agreed specifications and requirements.
ODF requirements for tendering
Include a clear statement in your technical specification of your functional and user needs so that suppliers can make sure that the proposed solution meets them. Review the government policy paper on sharing or collaborating with government documents to help prepare your statement. You can also download and use this sample text for ODF procurement specifications.
You should make sure that all statements in procurement documentation, regarding the application or service you intend to procure, state that it works reliably with revisable ODF text documents, spreadsheets and presentations for purposes of:
- tracking changes (where required; specify that ODF documents keep track of changes to the document so they can be reviewed and individually approved or rejected)
Full support for ODF
You should also ensure that:
- products retain all relevant information when storing output in ODF or importing or exporting data
- there are no dependencies on other file formats
- suppliers don’t hardwire their software with a specific office application but not support the standard
ODF is able to incorporate ‘foreign elements’. These are data elements that can be added to give software developers some flexibility to deliver added functionality. These foreign elements may make documents less portable (ie possibly incompatible with some other tools) and can make functionality more difficult to migrate from one solution to another. If a different application can’t interpret the meaning of some elements within a document, it won’t be able to make use of the information it contains.
You should understand where and how software makes use of such foreign elements. You should state in the procurement documents that suppliers should provide complete documentation about any foreign elements used in their software. You may request sample documents to test in multiple applications, or ask suppliers to demonstrate compliance with an ODF validator.
You should ask suppliers to address how they use and handle foreign elements when submitting their tender.
Any product or service you procure should allow editable documents to work equally well across platforms (ie, different software, operating systems and devices). If you create a document in ODF using the proposed solution on one platform, you should be able to read, modify and save it on another – and vice versa. Make sure the supplier gives you the necessary information to test functionality between various platforms.
Supplier confirmation of ODF support
You should ask potential suppliers to declare one of the following, in relation to whether their product or service supports ODF:
(a) Yes, our application/solution can use ODF as its default format and complies in full and without any restrictions regarding any of the requirements around ODF.
(b) By using third party software, through a plugin or add-in, our application is able to read, create and revise documents according to the ODF 1.2 standard. If the end user selects ODF as its default format, he or she will have no restrictions on the functionality of our software based on an incomplete implementation. We are not aware of any loss of information that would occur to documents edited or reviewed by our solution, provided that they conform to the ODF 1.2 specification.
(c) Another. Please provide details ………………………………………………………….
Using free open source software based on ODF
You must still ensure that any free software you use supports ODF. See Requirements for more information.