Title Description

Context

Local content (LC) requirements can arise from regulatory, community and social performance requirements and expectations. LC promises are made early during negotiations and can be missed as requirements during opportunity framing, which can make them costly or difficult to realise in later phases. It may also result in opportunities being locked into solutions that will not meet the LC expectations.

Therefore, this control is needed to ensure that LC requirements are identified and assessed as part of the Planning for Success in the Front End process resulting in a credible LC value proposition.

Activity

Verify that LC requirements are understood and are considered in the concept identification.

Identify what is realistically achievable, and what is needed to meet the stakeholder expectations.

Purpose

To identify the gaps between LC requirements and unconstrained range of concepts to understand the value/cost/risks trade-offs with meeting these requirements. This will allow the opportunity team to engage stakeholders and decision makers on the impact associated with meeting LC requirements.

Requirements from other Standards

  • Shell General Business Principles
  • Code of Conduct

Evidence recorded in

Feasibility Report

Accountability for meeting Control Intent

Front End Development Manager

Phase

Assess