Issue

During The Conceptual Design phase , it is been endorsed that Syensqo will use included endorsement of a Future Neptune - based Solutionsolution for essential Syensqo logistics and warehousing operations via mobility devices, which offers both online and offline capabilities to ensure users can mobile handheld scanners. This is to provide online functionality but also ensuring that users can continue to perform daily tasks continuously  even during any network disruptionsdropouts.

Potentially, there are two approaches to implementing the solution: Pre-built Applications versus In-house Developments. This KDD seeks to compare these approaches and evaluate the most effective option for the mobility solution.

Recommendation

Background & Context

Neptune is a Norwegian company whose Neptune platform is designed to create and deploy mobile applications that interface seamlessly with SAP applications. As a SAP-native solution, Neptune enables efficient integration while minimizing the need for middleware. The platform integrates multiple data sources and environments into a single launchpad or view.

Syensqo has rolled out the Nereid project to selected plants and warehouses. Nereid solution is a Neptune-based mobility solution, which sits on Neptune DX Platform SAP Edition, including a set of business tailored applications which support and manage the site logistics and warehouse operations.  

During the Conceptual Design phase, a decision was made to continue using the Neptune platform with the Future Neptune Solution, which will provide warehouse users with an unified view of both logistics and warehouse management functionalities within the SAP S/4HANA environment. It will not only offer online and offline capabilities to ensure operational continuity, but also minimize change management impacts, facilitating a smooth transition to SAP S/4HANA. More details are described in KDD025 - Mobility Solutions in Logistics and Warehouse Management Processes.

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

Assumptions

1. The scope of this KDD excludes the mobility solution for Plant Maintenance (PM).
2. Current handheld functionalities may be harmonized to align with the SyWay program principles. However, the future mobility solution must continue to meet all relevant business needs. 
3. This KDD also includes an assessment of the potential vendors offering pre-built Neptune solutions. 
4. Engagement with Neptune or any potential pre-built solution provider will be handled separately from this KDD.  
5. A separate assessment will be carried out to determine the scale of hardware and infrastructure required for sites planned to roll out the future mobility solution. 
6. A review of existing hardware and infrastructure will be conducted separately for sites have already implemented the currently mobility solution.  
7. 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

Impacts

Business Rules

• The selected future solution should be implemented to sites where the current mobility solution is already in place.
• To rolled out the solution to other relevant Syensqo sites, the cost-benefit should also be evaluated while considering site-specific conditions/hardware regulations such as explosion and flammability risks. 
• Ensure to have sufficient mobile devices to support the execution of the daily operations and exceptions at sites to implement the future mobility solution.

The SyWay design intent is to provide the business with unified mobile applications that support the different business scenarios. e.g. The app for processing Inbound Deliveries should support IM-NonHU, IM-HU and EWM scenarios, to avoid the need for users to select from separate apps depending on the scenario.

The two potential approaches considered to implement this solution are: 

Option A. HRC solution plus in-house build

Option B. Full in-house build

This KDD seeks to compare these approaches and evaluate the most effective option for Syensqo.

Recommendation

Option B: Full in-house build

This approach ensures a solution tailored exactly to Syensqo operational processes. This option has the following advantages:

• Gives Syensqo full control over the features, roadmap and security.
• Provides unified apps that support all Syensqo scenarios.
• Lower total cost of ownership compared to HRC option
• Allows faster adjustments when the business needs corrections or changes. 
• Removes constraints related to changing existing apps from HRC.

Although full in-house development will mean a longer initial development time, requiring dedicated in-house resources, Syensqo can leverage the existing standard SAP EWM mobile functionality, the existing Neptune apps used by Syensqo and the existing SyWay team members that have experience of building similar in-house developed global solutions for handheld scanners. This recommendation also aligns with KDD016 - Mobility Solution Direction for Enterprise Asset Management. 

Estimates for developments required to augment the HRC solution and for the full in-house build attached: SyWay Neptune Mobile Apps - HRC - With revised coverage

Background & Context

Neptune is a Norwegian company whose Neptune platform is designed to create and deploy mobile applications that interface seamlessly with SAP applications. As a SAP-native solution, Neptune enables efficient integration while minimizing the need for middleware. The platform integrates multiple data sources and environments into a single launchpad or view.

Syensqo has rolled out the Nereid project to selected plants and warehouses. The Nereid solution is a Neptune-based mobility solution, which sits on Neptune DX Platform SAP Edition, including a set of business tailored applications which support and manage the site logistics and warehouse operations.  

During the Conceptual Design phase, a decision was made to continue using the Neptune platform with the Future Neptune Solution, which will provide warehouse users with an unified view of both logistics and warehouse management functionalities within the SAP S/4HANA environment. It will not only offer online capabilities, while supporting network dropouts to ensure operational continuity, but also minimize change management impacts, facilitating a smooth transition to SAP S/4HANA. More details are described in KDD025 - Mobility Solutions in Logistics and Warehouse Management Processes.

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

Assumptions

1. The scope of this KDD excludes the mobility solution for Plant Maintenance (PM), which is handled by KDD072 - Mobility Application for Enterprise Application Management. 
2. The as-is handheld functionality will be harmonized to align with the SyWay program principles. However, the future mobility solution must continue to meet all relevant business needs. 
3. This KDD included an assessment of the potential vendors offering pre-built Neptune solutions.
4. A separate assessment will be carried out to determine the scale of hardware and infrastructure required for sites planned to roll out the future mobility solution. 
5. A review of existing hardware and infrastructure will be conducted separately for sites have already implemented the as-is mobility solution.  
6. Any third-party Neptune partner solution will be augmented, via additional in-house app development and enhancements, to meet all Syensqo specific business requirements. 

Constraints

While choosing full in-house build for the Neptune-based mobility solution is strategically sound, it may present certain constraints and challenges. These challenges are not necessarily unique to the in-house approach; but could also arise with off-the-shelf partner solutions, although in different forms and degrees.

• Project Timeline Constraints

The SyWay program involves both the core S/4HANA transition and end-to-end process reengineering. In parallel, the development of the Neptune-based mobile applications will proceed as a separate but closely linked workstream. This parallel execution increases the complexity of coordination, particularly in areas such as integration testing, user training, and change management. Additionally, any design changes within the core S/4HANA program may have downstream impacts on the handheld application design. 

To mitigate these risks, it is essential to establish an integrated project plan that clearly defines interdependencies and coordination points between workstreams. This includes aligning on shared milestones such as test cycles, integration checkpoints, and readiness gates to ensure consistency and alignment throughout the program lifecycle.

• Resource & Skills Constraints

In-house development requires the project team to have the necessary skills and resources. Without proper planning and prioritization, key teams such as development, QA, and SAP functional resources may become overstretched during the transition. To mitigate this risk, it is essential to establish a dedicated sub-team focused on the mobility solution, prioritize high-impact use cases, and phase the delivery accordingly. Additionally, creating a centralized repository for shared design documents will promote alignment across teams. Cross-training SAP and mobile application developers on basic integration principles can also help reduce reliance on a small group of specialists and foster stronger cross-functional collaboration. 

Impacts

Going with full in-house build as part of SAP S/4HANA transition doesn’t only affect the mobility solution itself, but may have broadercross-cutting impacts on other areas of the project, such as the process, integration among different modules and IT landscape etc.

• Process Alignment & Optimization

Heavy involvement are needed from process owners to define/refine logic within Neptune apps, as well as the greater alignment between business and development. The custom apps may preserve existing, non-standard processes rather than adopting S/4HANA best practices.

• Integration with Other SAP Modules

The mobile apps will need to not only be able to handle warehouse related activities, such as goods receipt, goods issue etc. The solution also needs to cater for different warehouse structures, such as IM based with and without handling unit management and EWM based warehouses, and being able to interact with other function modules such as production material staging, goods issue and goods receipt and Transportation Management. General support is also needed batch management, label printing and item serial numbers.

• Custom Development Governance

An in-house approach increases the custom footprint, which adds to future maintenance effort, and could also mean more regression testing is required. In-house developments need strict development standards, code reviews, and versioning standards across Neptune and SAP ABAP. When there are multiple teams involved, this could bring the risk of inconsistency among different teams. 

Business Rules

• The selected future solution should be implemented at sites where the as-is mobility solution is already in place and to all other plants that will benefit from the functionality.
• To roll out the solution to other relevant Syensqo plants, the cost-benefit should be evaluated while considering site-specific conditions/hardware regulations such as explosion and flammability risks. 
• All plants using handling units will need to use the mobility solution for handheld scanners.
• Plants using the mobility solution will need to ensure sufficient mobile devices to support the execution of the daily operations and exceptions.
• To rollout a single device, to be used globally at all locations that do not have an ATEX safety requirement and a single device to be used globally at all locations that have an ATEX safety requirement. Ideally the ATEX compliant device would be an intrinsically safe version of the standard global device. Limiting the number of models used globally facilitates the mobility solution build regarding the scanner interface, device operating system version and software and a standard device staging process. This approach also facilitates device support.

Options considered

Business Requirements

A study has been conducted on the functionalities of the as-is Neptune solution. Due to the presence of two SAP instances, there are duplications, overlaps or inconsistencies in some functions. While the existing functionalities serve as the foundation for the business requirements, they will be harmonized to align with the principles of the SyWay program and adapted to meet the evolving business needs. For a detailed overview of as-is mobile functionalities, refer to the attachments on this KDD.

See attachment: Overview of As-Is Handheld Functionalities.xlsx

Based on the analysis of the as-is Neptune functionalities, the SyWay scope and workshops, to effectively support the logistics and warehouse operations, the Future Neptune-Based Solution should address the cross process business requirements, user experience and technical dimensions, as outlined in the table below.

Option A: HRC solution plus in-house build

Solution Overview

With this option, Syensqo will select the pre-built solution from HRC, and add further developments to fulfill the additional business requirements of Syensqo.

HRC provides a suite of ready-to-deploy Neptune mobile applications that cover key logistics and warehousing operations, backend integration with SAP S/4HANA, and run Fiori-style Apps optimized on Android-based industrial handheld devices. 

To fully support the above business requirements, the HRC solution will need to be augmented and enhanced for Syensqo specific needs. The customizations would include:

• Custom development of apps to meet requirements not supported by HRC. e.g. LE-HUM and TM functionality.

• Enhancements to pre-built apps (e.g. additional validation or operation logics)

• UI/UX adjustments for improved usability on handheld devices

• Localization or language support if applicable

Vendor/Partner Engagement

To identify a potential pre-built solution, a partner search was conducted using information on the Neptune Software website. The Config Team and HRC were the two official Neptune partners selected for further analysis as they both provided pre-built solutions. The matrix below presents an overview assessment and the summary findings based on a series of demonstration and discussion meetings. The full list of vendor partners initially assessed is attached: Neptune - Partner Study.xlsx.

The Config Team's heavy reliance on RF Framework configuration (Both standard EWM, Custom EWM and custom IM) would add a burdensome overhead, especially for customizations to standard PreBilt applications and to in-house built applications. With this approach we would be reducing the benefits already provided by the decision to use Neptune, where this config is unnecessary.

The user interface of PreBilt was also basic compared to the impressive user interface from HRC.

For these reasons it was decided to only consider the HRC solution for this KDD.

 Option B: Full in-house build

Solution Overview

With this option, a Neptune-based mobility solution will be fully developed as part of the SyWay program. The mobile apps will support the required logistics and warehouse operations in S/4HANA, fulfilling key functional and technical requirements:

• Align with SyWay program principles and requirements
• Enable real-time data capture, validation and postings via mobile handheld scanners.
• Provide unified applications for end users, based on process. e.g. A single app for Processing Inbound Deliveries, rather than separate apps depending on IM and EWM.
• Application functionality designed specifically for Syensqo requirements
• Support SAP S/4HANA integration with components such as Embedded EWM and TM
• Multilingual support
• Fiori-like responsive UI via Neptune
• Mobile transactions monitoring report

Implementation Team

By choosing the full in-house developments option, the implementation team must be carefully structured and resourced to handle both technical and functional complexities, while aligning with the overall program.

• Skill & Expertise Requirements

Both SAP functional and technical expertise will be required, for example, the functional expertise on SAP IM/EWM/Handling Unit/Serial Number Management etc, the Neptune platform expertise on App design with SAPUI5/Fiori principles and b ackend integration via ABAP and OData etc., the integration / middleware expertise on SAP gateway, OData publishing, and interfacing mobile apps with printers and scanners, as well as mobility & UX expertise on UX design following Fiori guidelines etc.

 Here is a role and responsibilities matrix to consider.

Evaluation

Options considered

Business Requirements

A study has been conducted on the functionalities of the current Neptune solution. Due to the presence of two SAP instances, there are duplications, overlappings or inconsistencies in some functions. While the existing functionalities serve as the foundation for the business requirements, they need to be harmonized to align with the principles of SyWay program and adapted to meet the evolving business needs. For a detailed overview of current mobile functionalities, refer to section: See also - Overview of Current Handheld Functionalities.xlsx. 

Based on the analysis of current Neptune functionalities and insights gathered from business, to effectively support the logistics and warehouse operations, the Future Neptune-Based Solution should address the business requirements cross process, user experience and technical dimensions, as outlined in the table below.

DimensionsKey FunctionalitiesBusiness Processes

1. Inbound Logistics

Support inbound logistics in both IM and EWM environments.

• Goods Receipt (GR) 

  • Scan and register incoming deliveries (inbound deliveries and returns).

  • Support barcode scanning for accuracy and speed.

  • Support unloading and packing the inbound delivery.

  • Support goods receipt with or without HU.

  • Real-time posting to SAP (material document creation).

  • Generate and print relevant labels.
• Putaway
  • System guided putaway (IM - Inventory Management or EWM - Extended Warehouse Management).

  • Confirmation of putaway via scanning.

  • Support putaway with or without HU.

2. Outbound Logistics

• Picking

  • Display picking list with priority and location information.

  • Scan items for confirmation.

  • Multi-order picking (if applicable).

• Packing

  • Assign materials to handling units.

  • Support unpack/repack/multi-level packing.

  • Generate and print shipping related labels.

  • Support for packing instructions.

• Loading by HU or w/o HU

• Goods Issue (GI)

  • Confirm GI against outbound delivery.

  • Update stock in real time.

3. Internal Warehouse Processes

• Stock Transfers / Transfer Postings / Replenishment

  • Storage Location (SLoc) - to - SLoc transfers. 

  • Bin-to-bin transfers.

  • Transfer postings.

  • Replenishment for picking areas.

• Cycle Counting / Physical Inventory

  • Support for ad hoc or planned inventory counting.

  • Barcode scanning for faster data entry.

4. Production 

• GR from production
• Material staging 
• Material consumption

5. Stock Management and Visibility

• Stock Overview

  • View stock on hand figures at different levels, such as plant/SLoc/bin/material/batch/HU.

  • Drill-down for HU, batch and serial number details.

• Batch/Serial Number Handling

  • Capture and validate batch/serial numbers during movements.

• HU Management

  • Create, manage, and move HUs.

  • Nested HU support if required.

6. TM?

7. Reverse Transactions

Usability and User Experience

• Support Offline Mode
  • Synchronize and store data for operations in areas with weak connectivity or network disconnection.

• Unified Entry
  • User select handheld Apps based on business processes for example Goods Receipt App, rather than technical differences, such as IM or EWM.

• Simple and Touch-friendly Design

  • Support current Zebra handheld devices.

  • Support explosion proof mobile tablet - ATEX mobile phones.

• Multi-language 
• Quick transaction postings

Architecture and Technical Integration

• Built on Neptune DXP: UI5-based Fiori-style apps optimized for rugged devices
• Integration with SAP S/4HANA via OData or RFCs etc.

• Security and authentication (e.g., SSO, user roles)

• Device management and support

• Logging and monitoring of mobile transactions

Option A: Pre-built Solution with Reasonable Customized Developments

Solution Overview

With this option, Syensqo will select a pre-built solution from a third-party partner, and incorporate targeted customized developments to fulfill the specific business requirements in Syensqo.

A third-party pre-built Neptune solution typically includes a suite of ready-to-deploy mobile applications that cover key logistics and warehousing operations, backend integration with SAP S/4HANA, and run Neptune Fiori-style Apps optimized on Android-based industrial handheld devices. 

To fully support the above business requirements, the pre-built solution should also offer the flexibility and capability to be tailored to Syensqo specific needs. The targeted customizations may include:

• Enhancements to pre-built apps (e.g. additional validation or operation logics)

• UI/UX adjustments for improved usability on handheld devices

• Integration with custom Z-processes or Syensqo legacy third-party applications 

• Localization or language support if applicable

Vendor/Partner Engagement

Based on the above requirements, a partner search has been conducted in Neptune Software website, and the following partners are the Neptune official partners who provide the pre-built logistics and warehouse mobility solution based on the Neptune platform. The matrix below presents an overview assessment based on the above business requirements. The complete assessment is provided in section: See also - Neptune - Partner Study.xlsx.

Solution PartnerOverviewFunctionalitiesUsability & User Experience

Architecture & Technical Integration

PreBilt -

The Config Team

The Config Team provides PreBilt™, a suite of mobile applications designed to digitize end-to-end supply chain processes within warehousing, manufacturing, and distribution centers. Built on Neptune Software’s DX Platform, PreBilt™ offers a highly configurable, low-code solution that streamlines supply chain operations.

• Offers a suite of mobile applications designed to digitize end-to-end supply chain processes within warehousing, manufacturing, and distribution centers.

• Provides a KPI and Analytics application that supports both EWM and WM, allowing enterprises to monitor performance and identify bottlenecks.

• Highly configurable and out-of-the-box solution, enabling deployment in days.

• Simplified user interface designed to reduce training time; one customer reported reducing new staff training time from four days to two hours.

• Built on Neptune Software’s DX Platform, ensuring seamless integration with SAP systems.

• Supports hybrid app development, allowing switching between platforms or mixed systems from iOS, Android, and Windows operations anytime.

HRC Software

HRC provides ready-to-use integrated applications for SAP Supply Chain & Maintenance and Procurement processes. 

• Click here for Neptune partner details.
• Click here for HRC solution introductions.

• Provides ready-to-use web and mobile applications for Supply Chain (SAP WM, SAP HUM, SAP EWM), Maintenance (SAP PM), and Procurement processes.

• Allows customers to fully integrate SAP documentation (SAP GOS, SAP DMS) within the process and adapt to their strategy with deep-linking between apps.

• Designed and built by focusing on end-users, ensuring applications are optimized for industrial devices (PDA and tablet).

• Installation of apps can happen within a 24-hour period, facilitating quick deployment.

 

• Built on Neptune DXP, ensuring seamless integration with SAP systems.

• Supports hybrid app development, allowing switching between platforms or mixed systems from iOS, Android, and Windows operations anytime.

 

Mygo Consulting

Mygo Consulting offers nxEWM, a comprehensive mobile solution for SAP Extended Warehouse Management (EWM). Built on the Neptune DX Platform, nxEWM covers the complete RF/EWM process, including goods receipt, putaway, picking, packing, and physical inventory.

• Click here for Neptune partner details.
• Click here for Mygo solution introductions.

• Comprehensive Coverage: nxEWM encompasses the full RF/EWM process, including goods receipt, putaway, picking, packing, loading, ad hoc bin-to-bin transfers, and physical inventory. This broad functionality ensures that all critical warehouse operations are supported.

• Prebuilt Applications: The solution includes 13 mobile applications tailored for EWM, developed using the Neptune DX Platform. Mygo Consulting has developed over 500 mobile apps for its clients, demonstrating their capability to create complex mobile applications efficiently. 

• Rapid Development: Mygo Consulting can develop complex mobile applications in less than a month, allowing for quick deployment and adaptation to specific business needs.

• Intuitive Interface: The nxEWM solution is designed with a user-friendly interface that simplifies warehouse tasks. Users can easily navigate through tasks, reducing the learning curve and enhancing productivity.

• Minimal Training Required: Implementations have reported a 95% reduction in training costs due to the solution's intuitive design. Users can quickly adapt to the system, leading to faster onboarding and reduced operational disruptions.

• Offline Capabilities: The solution supports offline operations, ensuring that warehouse activities can continue uninterrupted even in areas with limited connectivity.

 

• Built on Neptune DX Platform: nxEWM leverages the Neptune DX Platform, a low-code application development platform that facilitates rapid development and deployment of applications. This platform ensures seamless integration with SAP systems, including both ECC and S/4HANA environments.

• Modular and Scalable: The solution's modular architecture allows for scalability, enabling businesses to expand and customize the system as their operations grow and evolve.

• Device Compatibility: nxEWM is compatible with various devices, including Zebra handheld devices and tablets, ensuring flexibility in hardware choices.

 

 Option B: Full In-house Developments

Solution Overview

With this option, a Neptune-based mobility solution will be developed as part of the SyWay program. It will integrate seamlessly with SAP S/4HANA to support logistics and warehouse operations, fulfilling key functional and technical requirements.

• In align with SyWay program principles and requirements
• Enable real-time and off-line data capture, validation and access via mobile devices
• Support core logistics and warehouse operations
• Provide an unified entry for end user based on process, such as goods receipt or goods issue, rather than technical objects, such as IM, or EWM
• Utilise current handheld devices
• Leverage the lates technologies, including Neptune DXP (SAP Fiori-based UI) for frontend, OData services or RFCs to connect the mobile UI with the SAP backend, and user authorization via SSO or SAP user credentials
• Support SAP S/4HANA integration with components such as Embedded EWM or TM
• Multilingual support
• Fiori-like responsive UI via Neptune
• Mobile transactions queue management and monitoring report

Implementation Team

Evaluation

User Experience (UX)

Option A  Pre-built Solution with Reasonable Customized Developments	Option B Full In-house Developments
Function Fit & Customization	Limited customization options, although many pre-built apps offer configuration settings.	High degree of customization, as Syensqo can design the solution to fit your specific requirements.
Scalability	Generally scalable, as they are designed for a wide range of use cases, and may have limitations in extreme scaling scenarios.	Scalability can be tailored to business needs Requires careful design and ongoing monitoring.
Typically follow SAP Fiori UX design principles, which are user-friendly and familiar to users.	Syensqo will have full control over the design and user experience. To achieve a high-quality, intuitive UX may take more time and effort.
Integration with SAP S/4HANA	Out-of-the-box integration with SAP S/4HANA, leveraging standard APIs and predefined processes.	Can be tailored for specific integration needs but may require more development effort and testing to ensure seamless integration with SAP S/4HANA.
Time to Implement	If there are few customization requirements, in general, faster implementation and go-live, as they are ready-to-use with minimal configuration. Product unique skills are required, so will be largely rely on the expertise and availabilities from vendor.	Longer time frame required for design, development, testing, and deployment. Expertise base is much wider and generic. Has less limitation and constraints on the required skills.
Maintenance and Support  (** Country Base, Language etc.)	Regular updates from the vendor or SAP ensure the app stays up to date. Vendor updates may not always align with your timeline. HRC release 4 updates per year. Although HRC advised that these updates were not mandatory, Syensqo would need to regularly update. HRC Consulting is the current partner for the support of Neptune apps Vendor updates require full regression testing.	Syensqo will have Syensqo will have full control over updates and maintenance but must allocate internal own resources to manage it.
Security	Need to rely on the HRC solution security control capability.	Better control over security policies and internal access protocols compared to vendor-hosted apps.
Innovation and Future-Proofing	Likely to be HRC solution is currently continuously updated by the vendor. Vendor updates may not always align perfectly with your evolving needswill Syensqo requirements.	Flexibility to incorporate new features and innovative technologies. Requires ongoing investment.
Cost Considerations	Initial Investment Licensing and subscription costs. Lower initial cost. On-going Costs Maintenance, updates, support costs. Ongoing fees.	Initial Investment Development costs (including resources , and training, infrastructure). Higher initial cost. On-going Costs Maintenance, bug fixing, future upgrades, and resource requirements for ongoing support. Potentially lower long-term maintenance.

See also

KDD016 - Mobility Solution Direction for Enterprise Asset Management

KDD025 - Mobility Solutions in Logistics and Warehouse Management Processes

KDD072 - Mobility Application for Enterprise Application ManagementOverview of Current Handheld Functionalities.xlsx

Attachments
preview false patterns ^(?!.*\.(png|jpg|jpeg|svg)$).* sortOrder descending

Change log

Workflow history