Skip to content

FousOCIMF SIRE 2.0

Turn your SIRE 2.0 inspections into an API

Read each vessel's photograph status, your Inspections Pending Operator Comments and the negative observations in a draft report with one API call each. Or have a workflow check the fleet's photographs every Monday, before the next PIQ Review.

Start building freeBook a demo

Works with your own OCIMF SIRE 2.0 account. Fous is an independent product.

What you can build on SIRE

  • Get a vessel's photograph status

    Build this

    Reads the SIRE 2.0 Vessel Photographs grid for one vessel: each photo location, whether it is uploaded and when it was last validated.

    Takes
    Vessel name
    Returns
    Vessel, photo template, and per location: photo location, photo description, uploaded, last updated, last validated on, unavailable reason

  • List inspections pending operator comments

    Build this

    Reads the Inspections Pending Operator Comments grid on the home screen: the draft reports the submitting companies have released to you.

    Takes
    Nothing
    Returns
    Vessel, inspection date, submitting company, inspection type

  • Get the negative observations in a draft report

    Build this

    Opens one inspection with Enter Comments and reads every negative observation by chapter and question, with the comments already entered.

    Takes
    Vessel name, inspection date
    Returns
    Chapter, question, response type, observation text, operator comments entered, attachments

  • Create an inspection request

    Build this

    Starts Create Inspection Request on the Vessel Details screen, fills in Voyage, Vessel and the submitting companies, agrees the Member Agreements and sends it.

    Takes
    Vessel name, location, dates at terminal, cargo, availability, agent, invoice company, submitting companies in order
    Returns
    Vessel, inspection type, first submitting company, request status

Automate SIRE with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Photo locations missing or not validated in six months

    Build this
    Starts
    Every Monday at 7:00
    Step 1
    For each vessel you name, get the photograph status from the SIRE 2.0 Vessel Photographs grid.
    Step 2
    Keep the locations with Uploaded set to No or a Last Validated On date more than six months ago.
    Step 3
    Email you the list, one section per vessel.

  • New draft reports waiting for operator comments

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    List the inspections in the Inspections Pending Operator Comments grid.
    Step 2
    Keep the inspections that were not there on the last run.
    Step 3
    Post each one, with vessel, inspection date and submitting company, to your webhook.

  • Negative observations sent to your QHSE system

    Build this
    Starts
    When your system calls the workflow's webhook with a vessel name and inspection date
    Step 1
    Get the negative observations in that inspection's draft report.
    Step 2
    Group them by response type: Hardware, Process, Human factors and Photograph validation.
    Step 3
    Post them as JSON to your QHSE or defect system's webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get a vessel's photograph status” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "ocimf-sire.org/get_vessel_photograph_status",
    "input": {
      "vessel": "Northwind Spirit"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "vessel": "Northwind Spirit",
    "photo_template": "Crude / product / chemical tankers / OBO",
    "locations": [
      {
        "photo_location": "1",
        "photo_description": "Bow area from dead ahead.",
        "uploaded": true,
        "last_updated": "2026-03-18",
        "last_validated_on": "2026-04-02",
        "unavailable_reason": null
      }
    ]
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

SIRE’s own options

On the SIRE website, operators create inspection requests, confirm the PIQ, manage vessel photographs and certificates, and enter operator comments, each on its own screen. SIRE raises message centre alerts for expired vessel certificates and published reports, and emails the operator when a booking is cancelled.

OptionWhat it coversWhat it takes
Message centre alertsExpired vessel certificates and published inspection reports, shown under messages in SIRE.A SIRE account. Booking cancellations are also sent by email.
The SIRE website by handVessel Details, the PIQ, photographs, certificates (downloadable as a zip), inspection requests and operator comments.A SIRE operator account. Some screens need a role, such as managing vessel photographs or vessel certification.

Read on November 12, 2026: SIRE 2.0 Inspection Management Processes, Vessel Operator.

Signing in to SIRE

SIRE signs you in with an Account ID, a Username and a case-sensitive Password, and what each user can change depends on the roles assigned to them. With Fous you sign in once through SIRE's own sign-in with your own account: the login is sealed with AES-256, code and AI agents never see it, and an expired session is signed back in.

Worth knowing

14 days to comment, then it publishes
Once the submitting company releases the draft report, you have 14 days to comment on each negative observation. Without comments the report is published automatically, and the period starts again after a resubmission.
PIQ data is fixed once you sign
Signing the declaration in PIQ Review confirms the PIQ, photographs and certificates and generates the CVIQ. PIQ data in the final report cannot be corrected after that, and an inaccurate published report can only be withdrawn.
Requests go to one submitting company at a time
You list up to 5 submitting companies in order of preference. Each invitation is open for 72 hours, and if none of them accepts, the request is cancelled.
Photographs go stale after six months
A vessel's photo status turns Amber when any photograph was last validated more than six months ago, and Red when a location has no entry. A location with no photo needs a reason: not available or equipment not fitted.

More in Maritime and aviation

Other industries: AppFolio Property Manager, myCHEP, Home Depot Supplier Hub, Asda Supplier Portal, Verizon Enterprise Center, Thumbtack Pro.

Frequently asked questions

OCIMF's vessel operator guide describes the SIRE website: you create inspection requests, confirm the PIQ, manage photographs and certificates and enter operator comments there. SIRE also raises message centre alerts and emails booking cancellations. A method you build in Fous reads one of those screens and returns JSON.

14 days from the submitting company releasing the draft report. If no comments are published in that time, the report is published automatically without them. You can still add comments after publication and select Publish Changes.

OCIMF asks for it at least 48 hours before the inspection, and for all information to be uploaded at least two days before. The declaration confirms the PIQ, photographs, certificates, HVPQ and crew matrix, and signing it generates the CVIQ.

Yes, with a method you build in Fous. It reads the SIRE 2.0 Vessel Photographs grid for each vessel, and a workflow can run it on a schedule, loop over your vessels and email you the locations that are missing or not validated in six months.

No. Fous is an independent product. You use it with your own SIRE account, and a method reads and does only what that account can.

Put OCIMF SIRE 2.0 behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Start building freeBook a demo

Read nexteNOADQ88RightShip PlatformAppFolio Property ManagerHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of OCIMF SIRE 2.0 (Oil Companies International Marine Forum). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.