MOC, Technical Query,
Concession, and Deviation
Definitions, Differences, Similarities, and
Application Scenarios
2025
© 2025 Oceaneering International, Inc. All rights reserved.
Rev 6
Objectives
•
Understanding the Differences and When to Apply Each.
2
Definitions
MOC: Structured process for evaluating and controlling significant changes.
•
Use MOC for changes in procedures, equipment, personnel, or environment.
Technical Query: Request for clarification of technical requirements.
•
Use Technical Query for clarification of specs or drawings.
Concession: Request to accept non-conforming product/service after production.
•
Use Concession when product doesn't meet specs after production.
Deviation: Request to change a spec before production begins.
•
3
Use Deviation when spec can't be met before production.
Similarities and differences across all four
Similarities
•
Formal mechanisms to manage changes or exceptions
•
Require documentation, review, and approval
•
Ensure safety, compliance, and quality
•
Minimize risk and disruption
Differences
4
•
MOC: Internal change affecting safety, quality, or operations.
•
Technical Query: Clarification without requesting change.
•
Concession: Post-production non-conformance approval.
•
Deviation: Pre-production spec change request.
What is a Deviation?
•
•
A Deviation is a temporary exception to a standard, specification, or procedure.
It is used when something cannot be done as originally planned, but you still want to proceed — with
approval.
When to Use a Deviation
•
•
•
•
Temporary use of a part/process that does not meet original specification.
Issue affects a limited quantity or time.
Non-conformances that need to be accepted or worked around.
No permanent change to the standard.
Examples
• Temporary use of alternate material/component.
• Skipping a test step for a specific batch.
• Limited quantity acceptance of non-conforming items.
• Temporary process change due to tool limitations.
5
What is Management of Change (MOC)?
•
MOC is a formal process for evaluating, approving, and implementing significant or permanent changes
to systems, processes, equipment, or organizational structure.
When to Use MOC
•
•
•
•
The change is permanent or long-term.
It affects safety, quality, compliance, operations, or performance.
Introducing new risks, modifying workflows, or changing equipment.
Stakeholder awareness, risk assessment, and documentation required.
Examples
• Changing supplier mid-project.
• Modifying procedures permanently.
• Personnel changes affecting safety or performance.
• Environmental condition changes during operations.
• Introducing new chemicals or equipment
6
Deviation vs MOC - Comparison
7
Feature
Deviation
MOC
Purpose
Temporary exception
Significant or permanent
change
Scope
Limited time/quantity
Broad impact
Approval Process
Faster, fewer approvers
Formal review
Tool Used
Deviation Request Form
(D-0851355)
Global MOC Application
Examples
Accepting non-standard bolts
Changing supplier
Impact
Low risk
High risk
Flowchart: Deviation or MOC?
Proposed change
or
non/conformance
Is the change
temporary?
Does it
have a
significant
impact
(on safety, quality,
compliance, operations,
or performance)
?
Use an MOC
8
Use a deviation
•
Use Deviation if: Temporary, low risk, limited scope.
•
Use MOC if: Permanent, cross-functional, high risk.
•
Examples:
•
Substituting bolts temporarily → Deviation
•
Skipping test step for one batch → Deviation
•
Changing supplier → MOC
•
Modifying procedure permanently → MOC
Any questions?
Round Table Discussion
9