The human data processing platform

The work happens once.
The data goes further.

Maranics connects the information people produce at work with the teams and systems that depend on it. From the first observation to the next decision.

Follow the connection
01 /How it fits together

The connection between
people and systems.

Keep the knowledge from the work moving.
Keep the context with it.

01Where it starts

Your people

  • Checks & inspections

    The result of a routine, captured once.

  • Observations & photos

    What someone sees. The detail behind it.

  • Operational logs

    A record of what happened on board.

02Make it usable

Maranics

Human data processing
  1. Capture

    A workflow for the task in front of you.

  2. Structure

    Validated input, with context and evidence.

  3. Connect

    Ready for the next person or system.

One reusable record.Context and evidence stay with it.
03Where it is needed

Your systems

  • Maintenance

    Plan the follow-up and keep it connected.

  • Safety & compliance

    Keep the record and its evidence together.

  • Operations & reporting

    Share a view across ship and shore.

Capture on board. Sync when connected.Your workflows. Your existing systems.
Conceptual overview. Connections are configured around your workflows and systems.
02 /Inside the platform

One routine.
Different working views.

Follow an equipment inspection.
From the person on deck to the team ashore.

For the person doing the work

A clear task. A useful record.

Follow the steps for the job. Record a result, add a photo and explain what needs attention. The observation stays connected to the equipment and the inspection.

  • Checks, notes and photos together
  • Capture on board; sync when connected
Example / Mooring equipment inspection

Illustrated workflow. Views and steps depend on your configuration.

For the person following up

See what needs your attention.

Use views and filters to find the records that matter to your team. Review the context and start the next action from the same place.

  • Views shaped around your responsibilities
  • Actions connected to the next workflow
Example / Mooring equipment inspection

Illustrated workflow. Views and steps depend on your configuration.

For the people configuring the work

Make it fit your routine.

Define the steps, information and responsibilities around the work. Configure what happens next, including actions triggered by a result or an event from a connected system.

  • Define the input and the follow-up
  • Set access for the people involved
Example / Mooring equipment inspection

Illustrated workflow. Views and steps depend on your configuration.

A look inside Flow ManagerExplore the interface

From completed work
to a shared record.

Find a completed routine. See who recorded it, what it contains and the checklist behind it. Explore an example of how that information comes together in Flow Manager.

MaranicsFlow ManagerOperations workspace
Workspace / Data List
Collection

Compliance programme

Completed routines and the information behind them.

Shared view
04records
Illustrative compliance records. Choose a record to see its contents.
RoutineRecordedStatusView record
0142Policy acknowledgementDeck team20 Oct 202609:41Completed
0141Security awareness trainingEngine team20 Oct 202608:35Completed
0140Policy acknowledgementShore team19 Oct 202616:12Completed
0139Security awareness trainingDeck team19 Oct 202614:08Completed
Showing 4 of 4 recordsAll times shown as recorded
Record details0142
Back to recordsCompleted
Policy acknowledgement
Responsible
Deck team
Recorded
20 Oct 202609:41
Included in this routine
  • Data handling
  • Access policy
  • Backup routines

The current policies have been reviewed and acknowledged.

Original checklistRetained with this record
Flow Manager Interface conceptIllustrative records
03 /A fit for your operation

Built for the conditions.
Connected to your setup.

Work with an intermittent connection

Capture information on board and synchronise when connectivity returns. Sharing with shore teams and external systems depends on an available connection.

We look at where the work happens and what must remain available locally as part of the deployment.

Connect the systems you already use

Open APIs make structured data available beyond a single workflow. Start with the information you want to move, the system that needs it and what should happen next.

Each connection needs the right data mapping, access and behaviour for the systems involved.

Choose the right place to run it

Maranics supports cloud, local on-board and self-hosted deployment options. The right setup depends on your connectivity, infrastructure and operating requirements.

Bring your IT team into the conversation early so deployment and integration decisions can be made together.

Talk through your architecture
04 /Getting started

Start with one flow.
Learn from real work.

Bring a routine you want to improve.
We work with your people to make it useful.

  1. 01

    Understand the work.

    Maranics
    Map the routine, the information and the systems involved.
    Your team
    Bring the people who do the work and a practical problem to solve.

    An agreed starting point.

  2. 02

    Set up the first flow.

    Maranics
    Configure the workflow and agree the deployment and connections.
    Your team
    Check the steps, responsibilities and access with operations and IT.

    A flow ready to try.

  3. 03

    Put it to work.

    Maranics
    Support onboarding and adjust the flow using feedback.
    Your team
    Use it in the working day and tell us what needs to change.

    A routine tested in practice.

  4. 04

    Build from experience.

    Maranics
    Review what is working and help plan the next use case.
    Your team
    Decide where the same approach can make a difference next.

    A clear next step.

The scope, pace and support are agreed around your operation.

Talk about your first flow

A practical place to start

Bring us your
everyday challenge.

A routine that takes too long. Information you keep chasing.
Let’s see what one connected flow could change.

Talk to Maranics

Start with one flow.
Grow on the same platform.

Built in Gothenburg.
At work at sea.