ALM RoadmapAxiell User Conference, London, 2019

Andrea BoyesGlobal Product Manager, ALM

CLARITYROADMAP

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.

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

CORE

Adlib/Axiell CollectionsCalmEMu

MicromuséeMimsy XG

New CMS stack

What we are doingBuilding a new CMS stack

MongoDB Elastic search

Business rules services

Responsive user interfacesPluggable database engine with a separate query engine (CDP)

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

Not until it has the expected feature set to satisfy collections management use cases.

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

When will the new CMS be available?

Dilbert break

What else are we doing?Maintaining and updating 5 CMS

Calm – CalmView

EMu – EMu 6

Mimsy XG – OpenJDK, query API

Micromusée – version 7 / SNB new release

Adlib – Axiell Collections

Why this?

Calm – high priority for responsive collections search sites

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

Mimsy XG – Oracle is charging for its build of the JVM

Micromusée – improvements to user experience

Adlib – solidifying the upgrade path for Adlib

Add-onsCreating / maintaining add-ons

Pre-release

Axiell Move Premium

Updates

Axiell DAMS

In development

Axiell Flow

CONTRIBUTE

Where are we with the new stack?

CDP, version 1.0

Schemas/Business rules

Axiell Go, release 1.0

Pluggable database engine with a separate query engine

Data/Process logic

User interfaces

How you can contribute

• Product Ideas portals

• Process Ideas portals

• Common schema / use case consultations

• UI/UX design consultations

• Full-stack beta testing

Ideas portals

• https://axiellcollections.ideas.aha.io

• https://axiellgo.ideas.aha.io

• https://calm.ideas.aha.io

• https://emu.ideas.aha.io

• https://mimsy.ideas.aha.io

- 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.