Raisereq2

How to Request a New Standard

How to Request a New Standard

Posted on: September 28, 2021


Our Best-In-Class Standards Management Platform

The LIXI Standards are incredibly comprehensive - covering a wide range of products, and covering different transactions and events across the entire product lifecycle. By maintaining the LIXI Domain Model, 'the LDM' (previously called the Master Schema), and deriving smaller standards for specific use cases as a subset of the LDM, we make it easier to use the individual transaction standards, whilst maintaining consistency for those using multiple transaction standards.

The LIXI standards are managed and developed collaboratively with our LIXI Members, who are invited to raise change requests and to participate in the process of clarifying and generalising the requirement, discussing the proposed solution and testing the standards prior to release. All this takes place on issue tickets in LIXILab, and if your organisation is a member of LIXI, you can register for an account here if you don't already have one.

From the detail on the ticket, our build process executes the changes to the standards, automatically tests hundreds of samples and associated business rules and rebuilds a variety of our demonstration projects. All of this makes our change management platform best-in-class in terms of being able to reliably support our members and the broader industry.

Raising a Request For a New Standard

Because of the high level of automation embedded in LIXILab, the process of creating a new transaction standard that shares common items from the existing LDM has never been easier.

Requesting a new standard can simply be done by raising a change request by creating an issue ticket in LIXILab outlining the broad details of how the new standard would be used.

LIXI staff will then evaluate the use case, and request further context if required - assessing if there are enough common data items already in the LDM for the development of the new standard to be worthwhile.

If there are enough common items, three types of issue tickets need to be created:

  1. An issue ticket that lists all the common items (attributes and elements) that will form the basis of the new standard.
  2. An issue ticket that details the items that will form the instruction element - this explains what the recipient is expected to do with the content of the message.
  3. Issue tickets that detail new items - these are identical to the regular change requests that we deal with every day.

How long does it take?

With the high level of automation, a draft of the new standard can be available within days if there are sufficient details on the first two ticket types. The time required for the standard to be published as a version in RFC Status (Request For Comment) depends upon the number of new items required but could be ready in as little as 4 weeks. In our experience, the limiting factor is the requester providing the details rather than our time in implementing them.

Standards in Development

LIXI is in the process of developing three new standards - Application Fraud Detection (AFD), Account Creation New Zealand (ACZ) and Credit Decisioning New Zealand (CDZ). Application Fraud Detection will soon be added to the suite of standards as a request for comment (RFC) standard.


Related Blogs


Written by:
Shane Rigby, LIXI Limited CEO
First Published: September 28 2021