Company : Evomarine Inc, USA

Location : Chennai

Work Type : Contract

Position : Maritime Digital Library Content Editor

1. Technical Knowledge Library

This to create a centralized technical library that will become the knowledge base used by the The documents themselves should be stored in a controlled company repository, preferably Microsoft SharePoint, with proper permissions, revision control and document ownership.

I propose the following main folders:

IMO / International Maritime Regulations

SOLAS

MARPOL relevant IMO Codes and circulars fire safety requirements lifesaving requirements pollution prevention requirements

Classification Society Rules

ABS

DNV

Lloyd’s Register

Bureau Veritas

IACS Unified Requirements / Unified Interpretations

U.S. Navy / NAVSEA

NAVSEA Standard Items

JFMM requirements applicable NAVSEA technical manuals

MIL-SPEC

MIL-STD

Qualified Products / approved material requirements where applicable welding, NDT, piping, electrical, coatings and preservation requirements

MARAD / U.S. Government Maritime applicable MARAD vessel specifications

USCG requirements

46 CFR requirements vessel-specific technical specifications

ABS requirements applicable to government vessels contract-specific requirements

Engineering Standards

ASME

ASTM

AWS

ISO

IEC

IEEE

NFPA

API standards where relevant

NACE / AMPP where relevant for corrosion and coatings

Manufacturer Technical Documentation valve manufacturers pump manufacturers

HVAC manufacturers electrical equipment automation piping systems

GRE/GRP steel cables switchboards sensors motors heat exchangers filters sewage systems

BWTS scrubber equipment etc.





EvoMarine Internal Knowledge previously approved BOMs previous RFQs successful suppliers approved technical submittals previous material substitutions lessons learned

NCRs commissioning issues preferred manufacturers historic pricing delivery performance supplier ratings technical clarifications from previous projects

All standards and controlled documents must be obtained legally from the official publisher, classification society or approved subscription service.

We should not build the system around uncontrolled PDF copies from the internet.

2. Technical Requirement Matrices

Uploading standards is not enough.

We need to convert engineering knowledge into structured rules.

For every major material category, we should create a Technical Requirement Matrix.

For example, for a valve, the system should know that “3-inch valve” is not enough information.

Before procurement can proceed, it should check for information such as:





valve type nominal diameter pressure rating design pressure operating pressure design temperature operating temperature fluid/service material of body trim material seat material end connection flange standard actuator/manual operation fail-open/fail-close requirement fire-protected requirement class approval marine approval testing requirements certification requirement applicable standard quantity delivery location required delivery date

If mandatory fields are missing, the AI should automatically return questions to the Project Manager or Engineer.

The same approach should be developed for:

pipes fittings flanges valves pumps motors cables electrical equipment instrumentation

HVAC heat exchangers structural steel welding consumables insulation coatings

GRE/GRP machinery

- automation components

Each technical family should have its own checklist.

3. Hierarchy of Technical Requirements The system must understand that not every project follows the same standards.

The applicable rules should depend on the project.

For example

Commercial / Cruise vessel

Contract / Client Specification

→ Classification Society

→ IMO/SOLAS/MARPOL

→ Engineering Standard

→ Manufacturer Requirement

U.S. Navy project:

Contract / SOW

→ NAVSEA requirements

→ NAVSEA Standard Items / JFMM / applicable MIL-SPEC

→ ABS or other class requirements if applicable

→ engineering standards

→ manufacturer requirements

MARAD project

Contract / Vessel Specification

→ MARAD / USCG requirements

→ 46 CFR

→ ABS/class

→ applicable engineering standards.

The AI must never assume that one standard automatically overrides another.

The hierarchy must be configured by project.

Qualification

M. Tech in marine Engineering

Must have Sailing Experience or Working knowledge of the Maritime Laws and Codes and Standards

📌 Martime Digital Library - Editor (Chennai)
🏢 EVOMARINE
📍 Chennai