Issue

The Mobility solution streamlines logistics execution by providing automatic real-time data capture and updates, and facilitates the effective and efficient processing of the inbound, outbound and internal goods movements. To manage on site logistics operations, Syensqo has implemented Neptune based Mobility Solution (In short, Neptune Solution), which is a set of mobile applications developed based on Neptune platform integrating with SAP ECC backend programs. 

• As transitioning into SAP S/4HANA, it is a good opportunity to review the current customized Neptune solution and also assess some other options such as the SAP native mobile solution Inventory Manager, so to implement a standard, simplified and future proof logistics mobile solution across Syensqo. 
• KDD014 (Reference 3) describes that as part of the transition into SAP S/4HANA, the SAP WM module is obsolete.
  For that reason, the current mobility solution should be reviewed.
  

Recommendation

Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.

The recommendation is to keep on working with the Neptune application. It is advised to work together with a vendor offering prebuilt functionalities which interface with EWM in SAP S/4HANA. Functionalities for which the vendor does not offer a prebuilt solution will be built from scratch in the Neptune platform. The general guideline for the mobility solution is to keep it simple and intuitive for the end-user. 

Background & Context

Explain the context in which the decision is being made.

Mobility solutions facilitate the effective and efficient execution across all warehouse processes:

• Inbound examples:
  • • Goods receipt for purchase order
    • Putaway in Warehouse Management
• outbound
  • Examples:
    • Picking
    • Packing
• production integration
  • Examples:
    • Staging to production
    • Goods receipt for process order 
• internal goods movements:
  • Examples:
    • Physical inventory counting 
    • Ad hoc movement in Warehouse Management

Neptune is a Norwegian company that sells and distributes Neptune platform to design and deploy mobile applications which can interface with SAP. In Syensqo the Nereid project rolled out the mobility solution of Neptune across the organisation. 

Syensqo Neptune Solution, sitting on Neptune DX Platform Planet 8 module, includes a set of business tailored applications and developed zebra devices, which support and manage on the site logistics operations, from goods receipt, material consumption, production declaration / goods receipt, to the internal goods movements, to all the way through outbound processing such as picking, packing and loading controls etc.  

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. 

• The current Neptune solution covers functionalities of Logistics, Warehouse Management (WM) and Plant Maintenance (PM). The Plant Maintenance Functionalities are covered in the EAM - Mobility Solution KDD and not further discussed in this document. 

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	Pro Con	Pro Pro	Pro Con	Pro Con
Criterion 2	Pro Con	Con	Pro Pro	Con 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.

Change log

Workflow history