skla

SKLA Rail

Crews by segment and yard with network governance

Restricted operational windows require traceable schedules and tower contingencies.

Access platformContact

While traditional systems manage people, SKLA governs people, assets, and rules in the same operational decision.

Why it is not just scheduling software

Traditional systems manage who works which shift. SKLA governs people, assets, and rules in one flow — with a tower to decide before operational impact.

Typical fragmented operation

  • Schedules in one system, fleet or capacity in another
  • Compliance verified after the fact
  • Exceptions handled via chat or spreadsheets
  • No unified view across sites and modes

SKLA enterprise

  • People, assets, and rules in one decision
  • Rule Engine and alerts in the operational flow
  • Tower prioritizes exceptions with full context
  • Multi-site and multimodal governance when contracted

Control tower

Exceptions prioritized by operational impact and criticality.

Integrated compliance

Labor and operational rules before and during the shift.

Multimodal

Road, rail, air, and maritime under one governance.

Repositioning

Reallocate teams and assets across bases, sites, or modes.

Operational challenges

Real day-to-day complexity — on two axes that must be governed together.

Crew and teams

  • Critical teams spread by segment and yard
  • Tight shift windows and pressured changes
  • Absences leaving segments uncovered
  • Compliance and hours on complex networks

Consists and network

  • Consists and segments with tight operational windows
  • Unplanned stops affecting the network
  • Low availability visibility per yard
  • Contingencies without a unified tower

What your operation gains

Crew and teams

  • Better team distribution on critical segments
  • Faster response to shift changes
  • Traceability in crew operations
  • Fewer reactive decisions in tight windows

Consists and network

  • More predictability on the operational network
  • Fewer uncovered windows on critical segments
  • Yard and segment view in one place
  • Foundation for integrated multimodal tower

Who it is for

  • Rail control center
  • Maintenance coordination
  • Crew management

Key capabilities

  • Schedules by segment, yard, and operational window
  • Critical crew availability control
  • Coverage risk alerts by network and shift
  • Operational history for audit and improvement

Line highlights

Smart scheduling

Rules by contract, sector, shift, and unit with traceable publishing.

Real-time coverage

Gap, absence, and reassignment alerts before operational impact.

Decision tower

Unified panel to prioritize incidents and mobilize teams.

Integrated compliance

Labor and regulatory risk indicators in daily workflows.

Real-time operations

Timeline, duty, and tower connected — illustrations based on the SKLA interface.

Timeline

Global search
Sign out

Operational timeline

Driver × hour grid — trips and duty.

Live

Drag to move, drop on another row to swap resource, or use edges to resize. Validation before save.

Refresh
THU 06/18FRI 06/19SAT 06/20SUN 06/21MON 06/22

Legend

  • Depot preparation
  • Empty repositioning
  • Operational ride (repositioning)
  • Check-in / handover
  • Commercial trip
  • Freight segment (driving)
  • Overnight between legs
  • Relay (off duty)
  • Closeout
  • Full duty span
00:00
04:00
08:00
12:00
16:00
20:00
Demo Admin SKLA — Executive van
demo-day-trip-01
demo-day-trip-01 — Demo HQ → Pilot client
Demo Admin SKLA
demo-day-trip-02

Consist, train run, and onboard crew.

Tower

Global search
Sign out

Control tower

Operational cockpit: coverage, exceptions, and same-day actions.

LiveAuto-refresh every 30s; operational events trigger WebSocket refresh.
06/18/2026 — 06/18/2026

Day pulse

Scheduled staff

0

People with confirmed shifts on this date.

Allocated assets

0

Vehicles linked to trips in the period.

Blocking issues

0

Problems that block publishing or completing the operation.

Pending swaps

0

Requests awaiting acceptance or approval.

Day status

The lower the index, the more blocking or attention items exist on this date.

48%

Reference: 06/18/2026

Domain views

Exceptions(13)PeopleAssetsOperations(13)MultimodalCompliance

Exceptions (13 items, 0 blocking)

  • Needs attentionShort planned overnight

    Interval between legs shorter than regulated rest

    Bento Gonçalves → Manaus (integration)

    Open
  • Needs attentionExtended relay (>72h)

    Dual crew above 72h — schedule 6h rest

    Bento Gonçalves → Manaus (integration)

    Open

Crew deficits and rail exceptions.

Illustrative representation of the interface — not a client environment screenshot.

Compliance in operational workflows

Risk indicators and blocks integrated into scheduling — not just after-the-fact reports.

  • Labor law and hours
  • Safety standards
  • Driver hours law
  • Audit trail

Use case example

A rail operation distributes crews on critical segments, reduces uncovered windows, and improves shift-change predictability.

Line differentiators

Talk to an expert →