Plio out of beta, now officially live!

We’ve been spending the last couple of months beta testing with our early customers. You’ve given us plenty of feedback which we’ve fed back into our design and development process. Today I’m pleased to announce that we’ve just gone live with a big new release of Plio (v0.2.81) which includes a number of significant improvements.

We’ve made improvements in 7 areas:

1. Workspace screen custom titles

It’s now possible to create your own titles for each of the modules on the main Plio workspace. For example, if you want to call the Standards module “Compliance manual”, no problem, just go to Organization settings, select Workspace titles and make the appropriate change.

2. Online help

We now provide full on-line help, accessed from the main Plio workspace. This uses the same document manager front end as the Plio Standards screen, making it easy to find what you need.

3. Enhanced discussions

When creating a discussion around a Standard, a Risk or a Non-conformity you can now address a discussion message to a specific user, by prefixing with the “@” command. This user will then receive a notification pointing to that message, via email and via desktop notifications.

4. Memory optimisation

We’ve worked hard to reduce the memory requirements for Plio, and we’ve achieved a 10% reduction in the memory used by your browser. This has been done by rationalizing the app code, CSS and fonts.

5. Data export

Users can now create custom data exports from the Risk register, from the Nonconformities screen and from the Work inbox screen. Just click onto the 3-dot button on the right hand side of the header bar, click on “Data export” and then select the data fields that you want to export. Plio downloads a CSV file to your browser which you can then click on to open in Excel.

6. Standards numbering

You can now assign unique codes and numbers to your Standards documents. For example, you might want to prefix standard operating procedures with “SOP” and give each operating procedure a number e.g. SOP14. Plio doesn’t automatically assign these numbers, but lets you create your own manually. This lets Plio users move across numbering systems that many organizations already have in place.

7. Other small enhancements

We’ve improved the ordering of risks in the Risk register, ordering them by score in descending order in the left hand side list view. In the “Risks by status” list view, risks are now ordered by status colour (red before amber, amber before green) and then by Risk score within a status colour. This makes for a much more intuitive display of information.   We’ve also re-ordered the Work inbox items so that items with the earliest target completion date get displayed first, which we think is more intuitive.
We hope you find at least some of these new features useful, and look forward to getting your feedback over the coming days and weeks.

Plio is now in beta

It’s been a busy week as we run through our final tests to get Plio live. I thought I’d just bring you up to date with the Plio story so far.

We started the software development at the end of April this year. Previously we’d created a user interface prototype to get feedback from some potential customers. We reached out to firms in two different markets – financial compliance and ISO management systems. We spoke to compliance managers in regulated firms, and we spoke to compliance consultants. That feedback made it pretty clear which features were must-haves, and which were nice-to-haves.   It’s taken up about six months to go from our initial spec to a fully-working system.

Plio version 1 launches with 4 modules:

  • a document manager
  • a non-conformity tracker
  • a risk register
  • a workflow manager.

The purpose is to streamline your compliance-related work, moving away from the time-consuming stream of emails, Word and Excel files that compliance processes normally generate.

The last month has been mostly about testing and bug-fixing. We’ve organized this into two cycles – internal testing and a final cycle of external testing carried out by our test partner the original source.   A total of 210 issues got flagged, and we’re a good way through the process of dealing with these. It can be a bit painful when you see problems highlighted for the first time, but it gives you a lot of confidence in the platform as these get worked through and resolved.

Next week, we’ll update you on our roadmap for the next couple of versions. We’ve got some cool new features on the drawing board….