Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Add a new idea Subscribe
Status Future consideration
Categories Universal Access
Created by Nigel Barriscale
Created on Oct 7, 2021

RELATED IDEAS

Add Product Support for a Fully Decoupled Modular Universal Access System of Engagement.

Universal Access (UA) has the capability to act as a standalone Client Digital portal (System of Engagement - SoE) with integration to remote back end systems, or a separate instance of Cúram(Systems of Record - SoR).

There are two elements to the request:

  1. Ability to deploy a base minimal and modular set of SPM end to end componentry required for Universal Access to function as a stand-alone decoupled modular System of Engagement.

  2. Provide REST API equivalents to all of the existing UA Webservices.

Enhancement Element #1: We are looking to UA deploy as a standalone decoupled and more modular System of Engagement (SoE). This is a very similar fashion to MSD in New Zealand. Universal Access will be deployed in its own instance, with its own database. This requires a full SPMP instance underneath it to enable UA to function. Only UA configuration data and in-flight benefit applications are persisted in the UA instance’s database. Benefit applications will be pushed (via REST API) to the separate back end Benefit Processing SPMP instance. UA will integrate (via REST APIs) to the back end System(s) of Record in order to service requests for the Citizen Account and the pre-population of benefit application scripts for linked users.

In order to support and optimize this more modular deployment approach we are seeking an enhancement to modularize SPMP to service just UA as a SoE. The modularized server component would include; the minimal server artefacts and infrastructure elements that UA requires; an administration console(s) to support UA only. The resulting database schema would also only house tables for the above deployment.

Enhancement Element #2: Universal Access comes with a set of web services:

https://www.ibm.com/docs/en/spm/7.0.9?topic=SS8S5A_7.0.9/com.ibm.curam.content.doc/UniversalAccessCustomization/c_UACUST_Customizing9UniversalAccessWebServices1.html

There are some REST API equivalents to these webservices that would service a decoupled architecture. The request is to have a fully equivalent set of REST API to support a decoupled modular UA instance to communicating with a back end SPMP instance/SoR. The enhancement would include a concrete implementation of the equivalent REST API for the Process Application Service on the back end SPMP instance, whereby the application process is seamless in a decoupled environment, as is the case

Customer Name ESDC
  • Attach files
  • Benoit Tremblay
    Reply
    |     Sep 28, 2023

    This is nice to have but not essential for now, low to medium priority

  • Guest
    Reply
    |     Dec 16, 2021

    Hi Nigel,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
    · You are seeking product support for a standalone version of Universal Access (UA) that has the minimum infrastructure elements of SPM Platform required to service Universal Access in order to implement a more modular System of Engagement.
    · You are also seeking a set of REST APIs that are equivalent to all web services that currently come with UA in order to communicate with a backend system of record.

    Decoupling Universal Access is aligned with our current multi-year strategy for our product; therefore, we have accepted your suggestion to decouple Universal Access as a consideration for a future release.

    Please note that not all items accepted for further consideration will make it into a release and we may address the problem in a different way than suggested here. As plans are confirmed, you will be notified when a specific release includes this enhancement.

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    Thank you,
    Drake Broussard, SPM Product Management team

    Note: We have improved your RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
    Additional details can be found here.

  • Guest
    Reply
    |     Nov 17, 2021

    Hi Nigel,

    Thank you for providing the additional information requested. Within the next 30 days, we will review the details you have provided and inform you of our analysis and decision.

    Regards,
    Shane McFadden, SPM Offering Management team

  • Nigel Barriscale
    Reply
    |     Nov 16, 2021

    Re: What are the base minimal set of functional requirements you would need in the decoupled version of UA?

    Right now UA provides a specific set of business functionality. The request would be to maintain that set of functionality. There are business services and technical services that are part of the enterprise framework/infrastructure that are needed to support the business functionality in UA. I would expect these business services and technical services to be retained in a modular UA deployment. Examples of these services would be printing a PDF.

    Re: Would your team be open to a decoupled UA that is delivered through a Software as a Service (SaaS) delivery model, assuming it meets the requirements outlined above? If not, please explain why.

    No. In the short to medium term, we would not be interested in a SaaS delivery model. This would be a departure from the reasoning behind the procurement of the platform. There would be multiple impacts on DevOps, security, contractual, governance...the list goes on. It would also be a significant departure from the programme's approved architecture. In the long term it might be something that could be considered.

    Re: What is your current implementation timeline for UA?
    This is something we would be more than happy to talk about offline.

  • Guest
    Reply
    |     Nov 5, 2021

    Hi Nigel,

    We have reviewed your enhancement suggestion and require more information to properly understand the issue and the business scenario you are trying to support.
    Based on the information provided, our understanding of your request is:

    • You are seeking product support for a standalone version of Universal Access (UA) that has the minimum infrastructure elements of the SPM Platform required to service Universal Access in order to implement a more modular System of Engagement.
    • You are also seeking a set of REST APIs that are equivalent to all web services that currently come with UA in order to communicate with a backend system of record.
    We have the following additional questions:

    • What are the base minimal set of functional requirements you would need in the decoupled version of UA?
    • Would your team be open to a decoupled UA that is delivered through a Software as a Service (SaaS) delivery model, assuming it meets the requirements outlined above? If not, please explain why.
    • What is your current implementation timeline for UA?

    Please provide the requested information within 30 days so we may proceed with our evaluation. If we do not hear from you within that timeframe we will have to close the request due to insufficient information.

    Thank you,
    Shane McFadden, SPM Offering Management team

  • Guest
    Reply
    |     Oct 9, 2021

    Hi Nigel,

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    We will review the information you have provided and get back to you within 30 days. If additional details are required in order to complete our evaluation, we will send you a request for more information.

    Thank you,
    Shane McFadden, SPM Offering Management team
    Note: We have improved your RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
    Additional details can be found here.