Skip to main content

How positions and the org structure work

A position is the role a person holds on an installation or in the organisation, for example ROV Pilot or Deck Foreman. It is the single most important piece of structure in People, because most of what the rest of Markular does hangs off it.

What a position carries​

  • A place in the organisation. Positions belong to departments and locations, which together form the org chart you see under Org Chart.
  • Competency requirements. A position defines the competencies and certificates a person in that role is expected to hold. This is what lets Markular tell you when someone is scheduled into a role they are not yet qualified for.
  • A link to planning. When a rotation needs "an ROV Pilot", it is asking for the position, not a named person, so the schedule can be built before the specific people are assigned.

Why it works this way​

Keeping requirements on the position rather than on each person means the rule is defined once and applied everywhere. Change what an ROV Pilot must hold, and every person and every scheduled seat for that position is measured against the new rule automatically. This is how People, Planner, and Skills stay in agreement about who is allowed to do what.

What you can do​