GovPrint Interoperability Standards

[KeithHoughton]

Create A Challenge

Title

GDS GovPrint cross departmental printing system interoperability standard

Category

• [X ] Technical

Challenge Owner

GovPrint Product Owner

Short Description

User research has shown three key user needs / scenarios.

1. Mobile Workers - users are becoming increasingly mobile and need to access print services in all locations where they are working. Often these locations are in other departments and there are no printers connected to the users home department.
2. Host Departments - one department hosts another department. Currently the hosted department has to put in additional printers to provide print services, this can lead to multiple printers in a location. Ideally hosted users should be able to access the host departments print service without the need to register for the department.
3. Hub Buildings / multiple tenants - provide print services for all tenants in the hub / shared building

Currently most departments implement their own print solution. As more departments move to cloud services it could offer significant benefits if these services could support interoperability.

By supporting the ability of different print services to interoperate this would enable: Users can print where and when they need to in order to complete their tasks Eliminate the need to provide multiple devices in locations where several departments are located

This type of functionality is unlikely to be delivered by the major vendors unless government departments demand it. Having a standard

User Need

The user need that this challenge seeks to address, including a description of the types of users it involves.

Most users still need to print even though this requirement is reducing as departments become increasingly digital. In some areas printed output is a key part of a business process and if users cant print then they Access to print in all locations where a user works can impact on their working tasks. If users go to locations where their home departments does not provide print services they are unable to print.

Some departments provide a guest printing facility but this usually requires some form of registration and the process to submit and release print jobs can be cumbersome.

In buildings where multiple departments are located each department has their own print service and their own printers. This can lead to multiple underutilised print devices. For example at 1 Horse Guards print areas have devices from several departments rather than a single device to support all departments.

Expected Benefits

The benefits for users, and the operational, social or environmental benefits that could be realised if this challenge is successfully resolved. These should be specific, measurable, achievable and realistic. If you have any information on current costs and expected savings, include that here.

Users cant print when they need to and where they need to

Locations with multiple departments not need to deploy multiple systems and multiple printers to support all users

Overall reduction of the number of devices across government

Enable commoditisation of print services and print devices, reducing overall cost for providing print services

Simplify migration between service providers and reduce vendor lock in

Support suppliers to deliver the functionality required to support user needs

Functional Needs

The functional needs that the proposal must address.

As a user in a location where my department does not provide a print service I need to be able to: Submit print jobs to my print service Authenticate and release print jobs as a guest

GovPrint Design Concept Summary v1 (1).pptx

[KeithHoughton]

We are currently engaging with the market to see whether cloud print software suppliers will participate in developing a draft standard and will kick off a project if we get at least 2 suppliers. If we do start the project are there any GDS people that would be interested in participating?

[KeithHoughton]

2018-12-18 GovPrint Interoperability Concept Design v1.pdf

At today's GovPrint Community of Interest Meeting we discussed an option for interoperability between cloud print services using Open Standards, would welcome any thoughts or comments on this idea.

[edent]

Thanks for that Keith, we'll share it around. I suppose one concern will be trusting a 3rd party printer with login credentials. I also wonder if they'll support 2FA.

[KeithHoughton]

Hi Terence

Fully agree with the comments about a 3rd party printer having access to login credentials, thats the reason for suggesting an authentication service based on OpenID Connect/OAuth. Would welcome everyones thoughts.

Cheers

Keith

On Wed, 19 Dec 2018 at 12:33, Terence Eden notifications@github.com wrote:

Thanks for that Keith, we'll share it around. I suppose one concern will be trusting a 3rd party printer with login credentials. I also wonder if they'll support 2FA.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alphagov/open-standards/issues/64#issuecomment-448579879, or mute the thread https://github.com/notifications/unsubscribe-auth/ApZSddr5P4s0dbTnzX7plQN6BdPAOxgNks5u6jICgaJpZM4Wv4jw .

--

Prostate Cancer UK Cycling Challenge, please like my website https://www.keithscyclingchallenge.org/ Keith Houghton Product Owner - GovPrint 07805 829816 Government Digital Service

[edent]

The problem with OAuth is that I still have to type my credentials - and 2FA - into an unknown device. How can I trust that printer won't store and/or abuse my credentials?

Also, my password is 32 characters long. I don't really want to prod around on a tiny touchscreen, struggling to find the special characters, just to print.

[KeithHoughton]

There would need to be assurance of the software solution that is used to support a service that deploys the standard.

Also as part of the operational processes around the standard we would have to have some form of agreement that outlines the responsibilities of each party. Very similar to the MOU that organisations sign when they sign up to GovWifi.

On Thu, 20 Dec 2018 at 08:48, Terence Eden notifications@github.com wrote:

The problem with OAuth is that I still have to type my credentials - and 2FA - into an unknown device. How can I trust that printer won't store and/or abuse my credentials?

Also, my password is 32 characters long. I don't really want to prod around on a tiny touchscreen, struggling to find the special characters, just to print.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alphagov/open-standards/issues/64#issuecomment-448919880, or mute the thread https://github.com/notifications/unsubscribe-auth/ApZSdX7I91m9CLfLGUfev93kNlHDTSqGks5u607rgaJpZM4Wv4jw .

--

Prostate Cancer UK Cycling Challenge, please like my website https://www.keithscyclingchallenge.org/ Keith Houghton Product Owner - GovPrint 07805 829816 Government Digital Service

[jondodsworth]

We at UK SBS are already providing a service which I believe covers all of the above. A full cloud-based, multi-tenant system with the ability to print from any device, anywhere, on any network. Provides guest and mobile printing, and so far is very stable with 9 organisations working currently. Happy to discuss...

[KeithHoughton]

Would be happy to have a discussion. Possibly where the requirement is different to what you already have is that we are looking for interoperability between services not just between tenancies within a service. Do you have a contact number?

[oughnic]

We at UK SBS are already providing a service which I believe covers all of the above. A full cloud-based, multi-tenant system with the ability to print from any device, anywhere, on any network. Provides guest and mobile printing, and so far is very stable with 9 organisations working currently. Happy to discuss...

@jondodsworth Do you use any underpinning standards for interoperability or are you tied to one vendor's solution?

[jondodsworth]

Hi Keith, Yes, (REDACTED)

[edent]

I'm removing your phone numbers from the public GitHub repository.

[KeithHoughton]

2018-12-18 GovPrint Interoperability Concept Design v1a.pptx Updated Interoperability concept design, we have been looking at the option of using OAuth Device flow instead of OpenID Connect, would welcome thoughts on this.

[KeithHoughton]

Updated Interoperability Concept Design with additional description of the OpenID Connect and OAuth Device flows. Would welcome any thoughts or comments, particularly peoples views on the benefits of using the different flows.

2018-12-18 GovPrint Interoperability Concept Design v1b.pptx

[KeithHoughton]

Based on the previously shared presentations we have created a discussion paper to support interoperability discussions with print software suppliers. I would welcome any comments please. 2019-04-15 GovPrint Interoperability Discussion Paper V1.pdf

[KeithHoughton]

We will be holding the first GovPrint Interoperability Workshop with suppliers on the 28th October from 11:00 to 13:00. It will be both onsite at GDS and online. The main purpose of the meeting will be to review and discuss the Interoperability Discussion Paper with suppliers and government departments. I will be issuing a new version of the discussion paper next week based on feedback we have received from suppliers, I will post a copy on here. If you would like to join the workshop please let me know and I will send an email invitation.

Best regards

Keith

[KeithHoughton]

2019-10-14 GovPrint Interoperability Discussion Paper V2 DRAFT.docx Updated discussion paper to be reviewed at the Interoperability Workshop on the 28th Oct.

[DidacFB-CDDO]

No challenge owner identified. Given the time lapsed since the suggestion was made we are closing the suggestion.