Benefits & Challenges of Fully Integrated VODM Portal

Since vendor modernization involves user journey that majorly overlaps in terms of functionalities for VODM and VMDM, an approach of creating only one portal has been suggested.

By doing this, VODM will manage complete user experience for both external and internal (Maersk) users/ADS. VMDM will still be the only source of master data creation.

Detailed design needs to be created/discussed, however this page is to evaluate this option on a high level.

Areas	Benefits	Challenges / Risks	Comments
Avoid duplicate efforts of developing portal application that exposes partly common features.
Single place of access for all internal & external users
Project Management	1	Ownership for VODM developmentUI development along with Vendor life cycle.Experience APIs.BBU / workflowDQ dashboardworkflow reportAudit history.Document Upload	Chetan, Harsha to align with Immanuel / Tamim and come back.Need to align on these key identified areas starting from UI to database.
Production Support	Complicated production support & SOPs : Identifying root cause, triaging tickets rightly. Creating CIs.Production support model: current MDM platform production support is limited to 24/7 only on Sev 1 issues.	The service model needs to be revisited and to be aligned with leadership. (eg: additional support team, cross functional expertise etc…), currrent support model for MDM is only UTC time and week days.
Backend services	API Performance: Services that needs to be developed specifically for VODM may need to satisfy specific criteria’s like faster response time, higher availability etc… Consumption of Internal APIs, not governed through MIM.Future development/enhancements - Resolving development of overlapping feature areas, Prioritization in both teams, Tightly coupled release management etc.	Currently no such NFRs exist for MDM applications . SMDS API doesnt fall under threshold of Experience API category. Please do note that any API that is consumed by a UI, either it be a unified portal or split portals will need to be treated as an Experience API or has to be consumed as an Experience API. Ajit Vijay Daware The API’s don’t change. You will still build API’s specific to administrative and onboarding journeys. These will need to follow the domain driven and REST API best practices. Any API’s that is being consumed by UI will need to be performant, responsive and consistent. You can define different SLO’s for different API’s. This is how it should be. Releases need not be tightly coupled as UI targeting a specific journey can be deployed as a Single page app. This will be delivered as a separate pipeline. Similarly each API will have a
MVP Definition	Linking the same with timelines of moving out of Informatica license for SMDSCurrent alignment needs to be revisited for MVP1 on features that needs UI representation taking into consideration
Technical Skill set	Learning curve : different technologies for portal, experience APIs, security etc.
Future Enhancement roadmap	Difficult to envision the (low-level) impact we may have based on future Enhancements that are part of roadmape.g. Joint features / user journey for Customer+Vendor could become challenging in case there are additional features desired out of Customer which are already present on CMD Portal (only specific to internal users/ADS).
Centralized Access - Users can access all functionalities from one location, eliminating the need to navigate through multiple portals. This saves time and reduces user frustration.
Consistent User Experience - A single portal allows for a consistent user interface and experience across all functionalities. Users don't have to learn different interfaces for different functions, leading to improved usability and user satisfaction.
Efficient Integration - Integrating various functionalities is easier when they are part of a single portal. Data sharing and communication between different modules or services are streamlined, reducing development complexity and costs
Improved Analytics and Reporting - With all functionalities consolidated in one place, it's easier to gather comprehensive data for analytics and reporting purposes.
Scalability & Flexibility - A single portal can be more scalable and flexible than multiple standalone portals. It allows for easier expansion and adaptation to changing business needs or technological advancements.
Enhanced Security - Centralizing functionalities can improve security by implementing consistent security measures across all components of the portal. It reduces the potential attack surface and makes it easier to enforce security policies
Better User Engagement - Offering a wide range of functionalities in one place can increase user engagement. Users are more likely to explore and utilize additional features when they are conveniently accessible from the same portal.