Here is a non-exhaustive list of the main candidate big-tickets items which are considered for future iterations of the MyStandards products.
Primary Candidates Post-MyStandards V2.1
Online Usage Guideline Editor
Be able to change and update specifications through your browser online, instead of a local installation.
Be able to assign permissions to group members at a more granular level. Default group membership and the three assignable roles ('Owner', 'Publisher', 'Portal Publisher') unlock a pre-defined set of features. This does not always match well with the governance processes. Hence, having more fine-grained control over which member can do which task is desirable.
Be able to have metrics on user interactions with specifications and how test portals are used as well as having insights into how an organisation leverages the platform.
Secondary Candidates Post-MyStandards V2.1
More Restriction Types
Expand the current set of possible restriction types which can be used in a message specification. For example, 'default value', or 'truncate', or 'unique value'.
When testing a message in the Readiness Portal, be able to assign different Usage Guidelines to validate different parts of the message.
External Code Lists
Message specifications allow for the inclusion of code lists defined by external groups and organisations. These lists are often agreed upon at market level and used across the board. Storing and distributing these lists through the MyStandards platform would be a good fit.
Change Request Management
Be able to aggregate, review, discuss, and process upcoming changes to both Base Messages and related Usage Guidelines through a built-in, formalised Change Request management system.
Full MX Extension Support
Be able to define Extensions for MX Base Messages, generate the XML Schema online, and have full testability through the Readiness Portal.
Be able to enrich Usage Guidelines unilaterally as an individual user by adding business specific details to fit a particular usage scenario. This additional information would be viewable and exportable by the individual user only.
Non-MT or MX Standards
Be able to support other standards by extending the MyStandards platform and leveraging the existing feature set.
Assisted Content Creation
Enable the platform to prompt users on best practice and make suggestions on possible to-be-applied restrictions during Usage Guideline creation and maintenance.
Usage Guideline Generation
Be able to analyse historical message data, for example from the Alliance Access archive files, to automatically generate the representative Usage Guideline.
Enhance the way the MT tree-like structures are represented.
Sample Message Management
Be able to publish and maintain an up-to-date, accurate, and accessible set of sample messages which are in line with related specifications.
MT x98 Support
Be able to formally define the 'envelope messages', for example the MT 798 and MT 598, which are often used to define "standards within the standard".
Integration With Proprietary Systems
Integrate the Readiness Portal with the customer's testing or message repair infrastructure to speed-up the repair and provide a more integrated reporting.
Exportable Machine-Readable Rules
Be able to add restrictions to Usage Guidelines which can be exported into a machine-readable format and used to validate and tested against automatically, resulting in more intelligent straight-through processing.
Be able to capture business processes and business glossaries and link them to any associated usage guidelines and message flows.