SEW myHR UYOD App

Status Quo

SEW currently faces significant challenges in providing HR services to blue collar workers:

• No dedicated devices for blue collar workers, making temporary workers poorly connected
• Time representatives (Zeitbeauftragte) handle all time services at roughly 1:100 ratio
• Legacy SAP HCM system (~1997) with many in-house ABAP developers
• Information distributed via bulletin boards (Litfaßsäulen)
• Existing browser-based PoC has limitations:
  • No data encapsulation
  • Cannot pass through permissions properly
  • No distinction between internal and external user rights

Current system landscape includes Oracle HCM for newer functions while time management remains on legacy SAP P02.

Goal

For production management, it must be proven that time and absence services can be used via app on unmanaged devices for blue collar workers in order to save time and administrative costs (for example, vacation requests).

For the works council, it must be demonstrated that the integration of blue collar employees is making concrete progress. For example, in the form of internal job postings and application processes.

From a technical perspective, it must be proven that myHR (Oracle HCM and SAP HR) can be permission-limited for unmanaged devices. Usability and employee acceptance must also be demonstrable. In addition, SEW security standards must be taken into account.

Primary Focus

The solution focuses on blue collar workers (Werker) in Germany as the primary user group, with the capability to extend access to all SEW employees. The app should provide an intuitive, lightweight interface that doesn't overwhelm users while maintaining high security standards and SEW's corporate design identity.

Business Case

The works council and management require proof that time management services can be controlled via app on unmanaged devices to save time and administrative costs.

• Save HR capacity for manual / workaround processes
• Distribute information to future employees not in myHR, again to cut down on manual processes
• Reduced need for time representatives (currently ~1 time manager per 100 employees)

Key Requirements

Usability & User Experience

• Easy and intuitive operation for all skill levels
  • Focused, streamlined functionality
  • Clear navigation across all features
  • Seamless transitions between different tools and systems
  • Unified look & feel consistent with SEW corporate design
• Multi-language support (German and English minimum)
• Print and export capabilities for necessary documents

Technical Requirements

Prove technical feasibility for:

• Authentication & authorization on unmanaged devices
• Mobile device management (MDM)
• Usability & user acceptance
• High security standards compliance
• Simple setup and onboarding process
• Integrated support process

Functional Scope

Technical Proof-of-Concept

Minimum Viable Product (MVP)

MVP Phase 2

Full Rollout

Security & Compliance

• User acceptance with familiar look & feel
• Unified UI across systems (Oracle HCM compliant, ATOSS may need new UI)
• IT security & device management compliance
• SEW corporate design standards
• Data protection and privacy controls

Required Support from SEW

Solution Space

Device Strategy

Technical Architecture

Current Integration Flow

graph LR
    User[User] --> SAP[SAP Fiori Launchpad]
    SAP --> Oracle[Oracle myHR]
    SAP --> Legacy[SAP P02 Legacy]

    classDef current stroke:#0277bd,stroke-width:2px
    class User,SAP,Oracle,Legacy current

Challenges:

• Complex integration requiring deep links
• SAP UI5 Launchpad in browser
• SAP time tracking currently with SSO in new browser window
• Smart card authentication (MIFARE chips) being updated
• Employees don't know their AD passwords

User Journey & Personas

Target Personas

1. Pre-boarding Users (future employees)
2. Blue Collar Workers without managed devices
3. Workers with stationary devices
4. Management users

Core User Journeys

Use Cases Overview

Current vs Future Touchpoints

Current:

1. Time booking terminal / "time clock" with notifications
2. Time officer for minor time corrections
3. Clerk for payroll questions
4. Supervisor for additional requests

Future:

1. In-app help desk replacing clerks and time officers
2. Supervisor remains for "special processes"
3. Time booking terminal with signals for open tasks/messages

Development Approach

Design Sprint Process:

• User research and requirements gathering
• Prototype development and testing
• Iterative improvement based on feedback

User Acceptance Testing:

• Test management tool setup
• Automation tools configuration
• Metrics and monitoring tools
• Test data generation
• 3-tier staging environments for on-premise systems
• 2-tier HCM (Q-System very production-like)

Proposed Solution

Technologies

Implementation Timeline

Timeline and work packages assume that access to SEW's infrastructure is complete in the first sprint and that support from SEW's IT is ongoing and quick.

Specifically authentication & authorization, as well as access to Oracle and SAP systems may turn out to be more difficult. Because of these risks, we propose a technical PoC to verify our assumptions and update this project plan.

gantt
    dateFormat YYYY-MM-DD
    axisFormat Sprint %U

    section Research & Design
    Research & Wireframe          :s1, 0, 4d

    section PoC Development
    Kickoff & Authentication      :s2, after s1, 8d
    Recruiting & Learning APIs    :s3, after s1, 6d
    PWA Frontend                  :s4, after s3, 5d
    Deployment & Testing          :s5, after s4, 11d
    PoC Complete                  :milestone, m1, after s5, 0d

    section MVP Development
    Timetracking Frontend         :s7, after s5, 7d
    Multi-language & SAP Connect  :s6, after s5, 10d

    section MVP Testing & Rollout
    Testing & UAT                 :s8, after s6, 11d
    Feedback & Rollout            :s9, after s8, 8d
    MVP Complete                  :milestone, m2, after s9, 0d

Work packages

Work packages and budget include the technical PoC and the MVP phases.

Outlook

We estimate an additional 80 days for MVP Phase 2 and a product rollout, with these assumptions:

• Most additional services are simple to embed into an app with SSO
• 1-2 of the services require a dedicated API service to send & receive data
• Part of the rollout is training material for SEW's support team, so it can handle L1 & L2 support

After the full rollout, we estimate around 1000€/month for an SLA that covers a baseline of ongoing L3 support, as well as security updates for a PWA version of the app. Additional support work is billed through daily rates.

There are no additional license costs.

Rollen und Kosten

Rate Card

Es gilt die Rate Card aus dem Rahmenvertrag, Stand 2025: