Roadmap OverviewAxiell User Conference, Denver, 2019

Andrea BoyesGlobal Product Manager, ALM

Presentation Ideas…Axiell staff dress up and perform the dance from the Chemical Brothers “Go” video.

Finale - firing glitter cannons

But I don’t get to do a mic drop, so it ain’t happening…

Instead I will explain what we are doing and why https://youtu.be/LO2RPDZkY88

What we are doingBuilding a new CMS stack

MongoDB Elastic search

Business rules services

Responsive user interfacesPluggable data repository with a separate query engine

Data/Process logic

User interfaces

Why a new CMS stack?

e.g. Oracle, Texpress, DScribe

PL/SQL, ADAPL, Java, C#, TCL

Windows only, bulky, desk-bound

Expensive/aging back-ends

Disparate logic in various places

Interface/platform constraints

2 ideas and a mistake

Idea #1 (2013)

We need to supply a browser-based CMS.

It should include most of the functionality of a desktop client.

It should be built with larger screens in mind.

It should re-use as much code as possible to reduce dev time.

It should be based on a .NET/SQL Server stack to leverage MS.

Idea #2 (2015)

We need to supply browser-based access to a CMS.

It should deliver tailored, task-based interactions.

It should be built with smaller, more mobile devices in mind.

It should use common technologies for future-proofing.

It should have a pluggable, service-based architecture.

Mistake

Idea #1 was called Axiell Collections.

Idea #2 was called….. Axiell Collections.

And we hung onto that with a vice-like grip until it became clear that this was totally unclear.

So what did we do about it?We renamed Axiell Collections (Idea #2), Axiell Go

Why?We wanted to satisfy use cases that required real-time interactions with the CMS that take place away from your desk.

Will Axiell Go replace my desktop client?Not until it has the expected feature set to satisfy collections management use cases. Until it does, it will run alongside an existing CMS.

Will Axiell Go be the only UI?Could be, but probably not. We will likely deploy a number of UIs that are optimized to specific tasks. For example, a form building UI, administrative UIs, process flow UIs.

Recap

Axiell Collections

Upgrade path for Adlib

Complete CMS

UI designed for wide-screen

Desktop app in a browser

Axiell Go

Deployed alongside a CMS

UI for the new CMS stack

Designed for small/mobile devices

Will be the “face” of Axiell Flow

Dilbert break

What else are we doing?Maintaining and updating 5 CMS

Calm – CalmView

EMu – EMu 6

Mimsy – OpenJDK, interface updates

Micromusée – version 7

Adlib – Axiell Collections

Why this?

Calm – high priority for responsive collections search sites

EMu – need to keep pace with Windows/improve user experience

Mimsy – Oracle is charging for its build of the JVM (head slap!)

Micromusée – improvements to user experience

Adlib – upgrade path for Adlib, demand for a CMS in a browser

But wait, there’s more (sorry, no ginsu knives)

Creating / maintaining add-ons

Just released / pre-release

Axiell Go (r)Axiell Move Premium (pr)

Updates

Axiell DAMS

In development

Axiell Flow

- A curator or ten

Don’t get me wrong, I like(fill in the CMS), I just want tospend less time with it.

Anecdote

Questions for the floor

Does your institution actively use all of the modules available in your CMS?

How often do you have to write things down (or remember them) for later entry?

How many of you want to spend less time with your Axiell CMS?

Thank you!If you have any questions, email andrea.boyes@axiell.com

For presentation ideas, please contact alex.fell@axiell.com.