Issue

The Mobility solution streamlines logistics and warehouse 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. Therefore, Syensqo has implemented Neptune implemented Neptune-based Mobility Solution (In short, Neptune Solution), which is a is a set of mobile applications developed based 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 and optimize the current highly customized Neptune solution, and also assess some other options  to implement a standard, simplified and future proof mobile solution across Syensqo. 
• As part of current Neptune Solution, different apps with similar functionalities were developed for 2 SAP instances (WP1 and PF1) used in Syensqo. Consolidation of functionalities is reasonable moving forward to SAP S/4HANA.   
• KDD014 - Future-proof Warehouse Operations describes that as part of the transition into SAP S/4HANA, the SAP WM module is obsolete. Also for that reason, the current mobility solution should be reviewed.
  

Recommendation

The recommendation is to use Future Neptune-based Solution, which offers both online and offline capabilities to ensure users can perform daily tasks continuously even during network disruptions. The Future Neptune Solution also provides warehouse users with unified view of both logistics and warehouse management functionalities. Furthermore, change management is limited since the users are familiar with the Neptune App navigations.  

Depending on the future process design, the decision will be made later in detailed design phase whether to develop highly customised applications in-house or utilize the third-party vendor pre-built applications with reasonable enhancements.

Background & Context

Background & Context

Mobility solutions facilitate the effective and efficient execution across all logistics and warehouse processes of inbound, outbound, production integration and internal goods movements. Some examples are:

Neptune is a Norwegian company that sells and distributes whose Neptune platform is used to design and deploy mobile applications which can interface with SAP applications. In Syensqo the Nereid project rolled out the Neptune-based mobility solution of Neptune across the organisationto selected plants and warehouses. 

Syensqo Neptune Solution, 's Nereid solution, sitting on Neptune DX Platform Planet 8 moduleSAP Edition, includes a set of business tailored applications which applications which support and manage on the site logistics and warehouse management 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.  .   

Some examples of apps in Syensqo's Neptune solution are:

• Goods Receipt for purchase order
• Putaway in Warehouse Management
• Pick and Load
• Pallet / SU (Storage Unit) Creation
• PP-PI, PP-REM Material Consumption
• Inventory Counting for IM (Inventory Management) and WM (Warehouse Management) 
• IM/WM Location Moves
• Bin to Bin Movement
• Label Printing etc.

Assumptions

• The current Neptune solution covers functionalities of Logistics, Warehouse Management (WM) and Plant Maintenance (PM). The Plant Maintenance Functionalities are covered in the the EAM - Mobility Solution KDD and not further discussed in this document.
• The business requirements for mobile functionalities are expected to be refined further during the detailed design phase.
• The focus during detailed design is to keep it simple. This will ensure intuitive and efficient registration. The UX design should focus on minimizing user inputs, utilizing device features such as barcode scanning, and providing clear navigation paths. 
• Language requirements for the mobile applications are covered in a separate KDD (Reference 5) and in detailed design. 
• This document assumes the recommendation of KDD014 of KDD014 - Future-proof Warehouse Operations is followed in the future design meaning EWM will be implemented. 
• For sites to be rolled out the mobility solution, the scale of required hardware and infrastructure will be assessed during the detailed design phase.
• For sites already have current mobility solution implemented, the existing hardware and infrastructure will be reviewed during the detailed design phase to ensure meet the requirements of the future Neptune-based solution. 
• It is assumed that the third-party Neptune partner solution is augmented, which can be expanded and enhanced to fit in the Syensqo specific business requirements.  

Constraints

By understanding the below challenges, we can mitigate risks and optimize the Neptune-based mobile solution to meet the Syensqo specific needs for logistics operation.

User Experience (UX) in Mobile Context:  Although Neptune allows for custom UX design, which can lead to a highly tailored user experience, however, inconsistencies or complex functionalities may impact user adoption and productivity. So to  ensure the intuitive and efficient workflows that align with logistics business processes,  the UX design should focus on  minimizing user inputs, utilizing device features such as barcode scanning, and providing clear navigation paths. 

Mobile App Lifecycle Management: Neptune solution is not an one-off implementation, but requires Syensqo requires Syensqo to manage the mobile application lifecycle and ensure the mobility solution is compatible with evolving SAP releases, operating system updates, and device changes. This may involve continuous software update and version management etc., which requires proactive planning and regular maintenance.

Vendor Support and Roadmap:  Dependency on Neptune as a third-party solution provider necessitates understanding their support policies, product roadmap, and future compatibility with SAP updates. Regular communication with Neptune regarding updates, patches, and new features is essential to stay current and leverage enhancements.

Impacts

Process and functionalities: Functionalities: Although the Future Neptune Solution can leverage the current designs and features, SAP S/4HANA will introduce changes in the processes, functionalities, as well as role definition and

authorizations, therefore the future solution will start from the To-Be design requirements, review the current mobile functionalities, assess the usability of prebuild Neptune-based apps and decide whether to build new or enhance the pre-build applications.

User Training and Change Management: Users familiar with ECC-based processes will need training on new processes and features introduced in S/4HANA, which ensures smooth adoption of the new Neptune solution. Sufficient and qualitative end user training across all relevant plants and warehouses is required for a successful implementation.

Data Mapping and Conversion: Data structures and data models in S/4HANA differ from the ones in ECC. The Future Neptune Solution must accommodate these changes and ensure data integrity.

Licensing and Cost Implications: Extra licensing costs will be incurred to roll-out the mobility solution to those sites which don't have Neptune Solution implemented currently.

Implementation Resources: Additional resources will be needed to implement the mobility solution as part of S/4HANA project. Especially if Syensqo chooses to develop highly customized applications in-house, significant resources will be required, including extra technical, testing, training and change management resources etc. This will have financial impact on project budget.

Business Rules

• The selected future solution should be implemented where the current mobility solution is already in place. To rolled out to other relevant Syensqo sites, the cost-benefit should also be evaluated during the detailed design phase, while considering site-specific conditions/hardware regulations such as explosion and flammability risks.

Business Rules

• Potentially, the selected mobility solution should be rolled out to all the Syensqo Manufacturing Plants, DCs (Distribution Centers) operated and managed by Syensqo, R&I Centers and Spare part warehouses. Defined processes and further updates will be determined during the detailed design phase.

• Warehouses for which a Warehouse Management System will be implemented based on criteria defined in KDD on Mobility Solutions in Warehouse Management Syensqo sites to be implemented of Mobility Solution will have sufficient mobile devices to support the execution of their Warehouse Management processesthe daily operations and exceptions.

Options

Considered

Option A: SAP

Standard Mobile Solution

SAP offers two standard options covering different aspects of Logistics Executions:

SAP Inventory Manager, covering Logistics

SAP Inventory Manager

is a complete wireless inventory management solution. It provides the company with the tools to improve and manage inventory levels, efficiently fill customer orders, and track the movement of materials using mobile devices with scanning functionality. The mobile application accesses the SAP Enterprise Asset Management (EAM) solution and provide the technicians and warehouse staff with the ability to execute stockroom operations in an automated and seamless way.

Inventory Manager can be deployed on a wide range of mobile devices, such as phone, tablet and windows mobile devices. It

supports 19 different languages. Refer to List of Languages Supported by SAP Inventory Manager

below

.

Extended RF Framework from EWM, covering Warehouse Management

It enables various warehouse activities, such as picking, putting away, packing, counting, and more, to be managed efficiently and accurately. Screen personas can be used to adapt the screens with greater flexibility and limited complexity. 

This is an example of the basic RF menu to display for the warehouse operators. These menus are easily adjustable on warehouse operator level. However the underlying technology is quite old and does not produce complex or user-friendly UIs. 

Image AddedFrom Warehouse Management perspective, SAP is offering the X

Option B: Future Neptune-based Solution

Based on business requirements the Neptune applications will be built with leveraging the current functionalities. 

Option C: Third-party vendor 

Applications prebuilt by third party vendor can be considered.

Examples of third-party vendors are The Config Team (Prebilt) and HRC Software.

Option D: SAP Fiori Solution

Based on business requirements the Fiori applications will be built with leveraging the current functionalities. 

Utilize the intuitive and customizable UX, offline data sync capabilities, and close integration with SAP S/4HANA provided by the Neptune platform to meet Syensqo's logistics and warehouse management requirements. The Neptune platform has been proven through existing Syensqo deployments (e.g. Nereid), as well as past experience in different clients. Importantly, several out-of-the-box options exist for apps providing functionality in the logistics and warehouse management domains providing surety that Syensqo will be able to deploy a fit-for-purpose solution using one of two approaches utilizing this platform:

1. Adopt, and if required extend with custom functions, an out-of-the-box solution provided by third-party Neptune partner (e.g. PreBilt, HRC); or
2. Develop a fully-custom mobile app tailored to Syensqo's processes and needs in-house, by leveraging pre-developed components, modules and libraries provided as part of the Neptune platform. 

The exact choice of approach will be finalised during Detailed Design through in-depth analysis of both the requirements and available commercial options using the principles listed below. Such an analysis is beyond the scope of Conceptual Design.

• Functional Requirements: Meets all essential and applicable functionalities in both online and offline/occasionally-disconnected environments.
• Technical alignment with S/4HANA for seamless synchronization
• User Experience (UX): Aligns with Fiori UX and ease of use by logistics and warehouse personnel (e.g. single sign-on)
• Unified View: Provides a consistent entry for warehouse operations even if using different SAP functionalities

Option C: SAP Mobile Design Solution

Based on business requirements, Syensqo can also utilize SAP Fiori or Mobile Services to build customized applications with leveraging the current functionalities. 

• SAP Fiori Apps: SAP Fiori is SAP's user experience (UX) design system that provides a set of applications that can be used on desktops, tablets, and mobile devices. It offers a consistent and intuitive user experience following SAP's design principles. Covers a wide range of logistics and warehouse processes. However, it will need customization for specific business processes beyond standard SAP functionality.
• SAP BTP Mobile Services: Provides a framework and tools for developing, deploying, and managing mobile applications that integrate with SAP systems. It offers flexibility to build tailored mobile solutions for specific business requirements, supports offline capabilities and integrates with device management solutions. However, this approach requires development effort and expertise, have cost implications for licensing, and would rely on a technology stack that is relatively unproven and subject to SAP's frequent historical changes in direction.

Evaluation

Based on five different criteria, the matrix below compares the pros and cons of the potential options for logistics & warehouse management mobility solution.

Evaluation

Option A: SAP standard solution

Option B:

Neptune-Based Solution	Option C:

Third- Party VendorOption D: SAP Fiori

SAP Mobile Design Solution
Functional Fit	Only SAP standard functionalities available.

Not all current functionalities of Syensqo are available

Syensqo specific functionalities are not supported. Inventory Manager is

specifically

specifically designed for enterprise asset management (EAM) processes.

 

Require additional customization for broader logistics operations.

Covers essential processes required

.  A detailed assessment is required, however it is expected that not

by Syensqo. Can leverage the current Neptune functionalities and design. If adopting Neptune partner solution, a detailed assessment is required during detail design to make sure the pre-build applications align with business requirements

all current functionalities of Syensqo are available

.	Covers essential processes required by Syensqo.
Integration with SAP	Native SAP mobile

solution, which seamless integration capabilities with SAP

-capable solution provided natively by the S/4HANA system without add-ons.

Although it can be tightly integrated with SAP, it is not as seamless integration as the standard SAP solutions.

Integration with S/4 HANA is required. This is depending of the solution used by the vendor. More detailed assessment is required.

Native SAP mobile solution, which seamless integration capabilities with SAP S/4HANA.

	Neptune-based solution provided by an SAP S/4HANA Add-on, and adheres to SAP standards for integration and security.	Cloud-hosted mobile platform and native app on device, which presumably integrates well with SAP S/4HANA as the entire tech stack is owned by SAP.
Usability

Usability  

Provides real-time access to SAP data.

Users

In EWM extended RF framework environment, users won't be able to continue transactions in mobile devices during

disconnect

disconnection or limited access to network. Different look & feel and even different logins for logistics and warehouse management functionalities.

 

Users will be able to continue transactions in mobile devices during

disconnect

disconnection or limited access to network.

Similar Look & Feel for

Unified view for warehouse users to perform both logistics and warehouse management functionalities.

Expected that these solutions are user friendly and easy to navigate.   Provides

Provides real-time access to SAP data.

Users

When using SAP Fiori Apps, users won't be able to continue mobile transactions

in mobile devices

during

disconnect

disconnection or limited access to network.
Offline Capabilities

No

In EWM extended RF framework environment, no offline capabilities

if required

to

operate

support operations in a remote area without network if required.

Offline capabilities can

be used if required to operate

support operations in a remote area without network

. Vendor can be selected based on offline capabilities

if required.

No

Standard SAP Fiori Apps have no offline capabilities

if required

to

operate

support operations in a remote area without network if required.

Implementing

effort

Efforts and Change Management

Sufficient user training is

Thorough and comprehensive user trainings are critical.

Development is

Major development efforts are required to fit to the Syensqo specific needs

of Syensqo

.

Development

is

may be required to fit to the

needs of Syensqo. The design can be facilitated by leveraging the current functionalities. 

future S/4HANA solution design. Use of the Neptune platform ensures extensibility without modification of vendor-delivered code. Reliance on additional vendors adds complexity to implementation and change management. Users are familiar with navigation within Neptune

. Extra complexity to work with both SAP and third-party vendor.

Apps Existing Syensqo IT infrastructure and processes for deploying and managing Neptune apps are reused.

Major development efforts are most likely

Development is

required to fit to

the needs of Syensqo.

Scalability and
future growth

Syensqo specific needs.

As shown in the matrix, the Future Neptune-based Solution provides Syensqo unified view of logistics and warehouse management functionalities. The online and offline capabilities ensure business operation continuity. Depending on the degree of standardization in future processes and the expandability of third-party solution, Syensqo may choose to build highly customized applications or adopt an out-of-the-box solution after further assessments in detailed design phase.    

See also

1. List of Languages Supported by SAP Inventory Manager

• ar - Arabic
• cs - Czech
• de - German
• es - Spanish
• fr - French
• he - Hebrew
• hu - Hungarian
• it - Italian
• ja - Japanese
• ko - Korean
• pl - Polish
• pt - Portuguese
• ro - Romanian
• ru - Russian
• sh - Serbian
• sk - Slovakian
• sv - Swedish
• tr - Turkish
• zh-CN - Simplified Chinese

Change log

Workflow history