Two sides to printing

Printing. At best it’s something that just happens. At worst it involves visits to the IT helpdesk, long login processes, or simply the hunt for toner. It’s not interesting. Or is it? In CTS we are creating a blueprint for printing.