| Status | |
| Owner | The person responsible for driving this decision and documenting it. Type @ to mention people by name |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Issue
As part of KDD016 - Mobility Solution Direction for Enterprise Asset Management a decision was made to implement a specialized Enterprise Asset Management (EAM) mobility solution to enhance Syensqo’s Work Management process and ensure effective asset and work management.
Syensqo currently utilizes a custom-built Neptune-based application for Enterprise Asset Management (EAM). However, as part of the ERP Rebuild project Syensqo is introducing new SAP S/4HANA functionalities, including Work Clearance Management (WCM), Phase-Based Maintenance and Resource Scheduling (RSH). These enhanced functionalities, along with other process improvements necessitate an EAM mobility solution that seamlessly integrates with SAP S/4HANA, ensuring real-time data synchronization and streamlined process execution. The solution must offer a modern, intuitive user experience aligned with SAP Fiori UX principles, provide robust offline capabilities for uninterrupted field operations in remote or low-connectivity areas and support key functionalities such as Dynamic Forms, Inspection Rounds & Checklists and Digital Permit to Work.
To identify the most suitable solution, this Key Decision Document (KDD) evaluates commercially available specialized EAM mobility applications, assessing their functional, technical and usability aspects in alignment with Syensqo’s strategic objectives. The selection will focus on a future-ready solution that meets current operational requirements while ensuring scalability, compliance and digital innovation to support Syensqo’s long-term growth.
Recommendation
Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.
Background & Context
Syensqo is actively exploring new mobility solutions for the management of field operations, including maintenance, inspections and asset management tasks. Currently, Syensqo uses a custom Neptune-based application deployed across 46 global plants. However, this solution needs to evolve to align with the new capabilities and functionalities introduced by the ERP Rebuild project such as Work Clearance Management, phase-based maintenance processes and the integration with SAP S/4HANA. The goal is to adopt a mobile solution that supports these changes while ensuring operational efficiency, safety and compliance.
The assessment of specialized EAM mobility applications was undertaken with the aim of identifying a solution that can scale with the business and meet future requirements. The decision will be guided by a set of criteria focused on synchronization with S/4HANA, user experience, offline capabilities and alignment with Syensqo’s operational needs.
Assumptions
Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited.
Constraints
Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.
Impacts
Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.
Business Rules
The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order".
Options considered
List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.
Option A: Option Title
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Option B: Option Title
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Option C: Option Title
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Option D: Option Title
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Evaluation
Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.
Option A | Option B | Option C | Option D | |
|---|---|---|---|---|
| Criterion 1 |
|
|
|
|
| Criterion 2 |
|  Con |
|
|
| Criterion 3 |  Pro | Con | Con | Pro |
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
