1. Designate the Internet as the default way to interact with users, other than for defined exceptions. We will look to establish a Digital Service Standard and Digital Design Guide, modeled on the UK equivalents, to ensure consistent design of current and future services.

3. Seek to ensure every Government interaction that occurs more than 50,000 times per year can be achieved online by 2017. Video-conferencing via technologies such as WRTC will be an acceptable substitute for physical proximity in most cases.

Ensure Agencies report what proportion of their digital services are not mobile-accessible from 2015. Digital services and information should be platform-agnostic and useable from devices such as tablets and smartphones.

Publish league tables of agencies ranking performance on online engagement, platform-agnostic services, availability of data sets and customer satisfaction.

Below are the totals for each jurisdiction where information is available.
· Federal: 44

· Queensland: 3

· Queensland Local: 1

· Tasmania: 1

· South Australia: 3

· Western Australia: 5

· Victoria: 8

· New South Wales: 16

· Northern Territory: 1

· Northern Territory Local: 1

December 2013

· Pageviews 2,321,994

· Visits 1,417,821

· Unique Visitors 1,208,706

• Cost effective

• Relatively plentiful technical resources

• Good community support

• Abundant content oriented plug-ins and functionality

• More control available to content team for metadata values and taxonomy

• Drupal is more flexible than an enterprise CMS. The vast majority of our requirements could be met in some way. We never came across an issue where we just couldn’t do a piece of functionality or layout. There is none of the “clunkiness” that we have experienced with other enterprise content management systems.

• Administration interface easy to learn and use – we now do things faster and better.

• Not suitable for applications that need even low-level business logic, database storage or reporting.

• Caution required for enterprise/critical level requirements, e.g. ATO, DHS style sites. Community instead of vendor support not sufficient for critical systems, market needs extra paid services to fill the gap around back-end integration to enterprise systems (B2B, messaging queuing, data transformation, etc.).

• Vast array of plug-ins need to carefully managed especially thinking about how to manage future upgrades.

• No Staging environment to see how content will look on the site before publishing. We were able to get around this, and could possibly come up with an even better solution in the future, but it is a disadvantage that Drupal does not accommodate staging.

• We were not able to integrate workflow and workflow messaging in with our other modules. This was OK for our implementation, but in a distributed environment we would have had to address this.

• Although many people claim to have Drupal skills on the market, there is a shortage at present of skilled, cleared, government experienced resources in the Canberra market.