CIPS L4M2 Based on Real Exam Environment

Comprehensive and Detailed Explanation (paraphrased from CIPS L4M2 content)

CIPS L4M2 explains that specifications in procurement serve several fundamental purposes, including:

Defining the requirement clearly – so that all stakeholders (user, buyer, supplier) have a shared understanding of what is needed.

Forming the technical basis for contracts and orders – what is being purchased.

Providing measurable criteria to assess quality and conformance – what will be inspected and tested.

Therefore:

A. To define the requirements – correct. This is one of the primary roles of a specification.

D. To provide a means of evaluating the quality or conformance – correct. Specifications set the criteria against which delivered goods/services are checked.

The other options do not reflect the core role of specifications:

B. Supplier appraisal and selection – this uses specifications indirectly but supplier appraisal is a separate process (using financial, capability, and performance criteria).

C. Define the bargaining strength of the buyer – bargaining strength is shaped by market structure and spend, not by the specification itself.

E. Minimise the bargaining strength of the supplier – not an explicit purpose of specification, and could actually backfire (e.g. over-specification reducing competition).

Relevant CIPS L4M2 areas:

Purpose and role of specifications in the procurement cycle

Specification as a basis for quality assurance and contract management

Links between specification and supplier evaluation

Explanation

Robots in manufacturing help to create jobs by reshoring more manufacturing work. Robots protect workers from repetitive, mundane and dangerous tasks, while also creating more desirable jobs, such as engineering, programming, management and equipment maintenance.

LO 2, AC 2.1

Explanation

This question mentions about specification in construction. In this sector, specifications are written documents that describe the materials and workmanship required for a development. They do not include cost, quantity or drawn information and need to be read alongside other contract documentation such as quantities, schedules and drawings.

Specifications vary considerably depending on the stage to which the design has been developed, ranging from performance (open) specifications that require further development by a contractor or supplier, to prescriptive (closed) specifications for which the design is already complete when the project is tendered.

Prescriptive specifications typically contain detailed descriptions of the following components:

- General requirements relating to regulations and standards.

- The type of products and materials required.

- The execution and installation methods required.

Prescriptive specifications give the client much more certainty about the end product when making investment decisions (such as when they appoint the contractor), and place a greater burden on the designer to ensure proper installation rather than the contractor.

Explanation

The writing of a complex specification should be treated as a project because it requires the brain power from different stakeholders. Many tools and processes of project management can be applied to complex specification development. Before engaging with the stakeholders and implementing the project, the project initial document should developed.

A Project Initiation Document (PID) is one of the most important components of project manage-ment, which forms the foundation for a company project. It is a reference point during the entire project, for the client as well as for the project team.

A PID bundles documentation into a logical reference work that collects all important information needed to start and run a project from a good foundation. After that, Project Initiation Document must be transferred to all stakeholders, including business sponsors.

This forms the basis for the project management. The documentation from which the PID is com-posed include the business case in which the project’s justification can be found, the communica-tion plan and the project plan.

The PID is composed out of collected information and includes, among others, the following com-ponents:

- Project goal(s); what do you want to achieve with the project?

- Project size; how large is the project, how long does it take and how many people are involved?

- Project organisation; who are involved in the project, what are their tasks, responsibilities and authority?

- Limits and risks; what can cause a project to stagnate and are there risks related to the project?

- Stakeholders; who has a stake in the success of the project?

- Project checks and frame reporting; by carefully taking into account evaluation moments, it is clear to everyone what sample tests can be carried out during the process.

In addition, it is important that the Project Initiation Document also contains the following infor-mation:

- The background and occasion of the project, which together provide information about the con-text.

- The project organisational structure, which describes who has which management responsibility in the project.

- The project quality plan, describing who controls the quality of the products to be delivered and how it will take place.

- The total project planning, including the duration of all activities.

- The exception process, which describes how exceptions are dealt with and the steps of the escalation procedure.

- The risk log, including the measures that will be taken when there are unforeseen risks.

- The documentation structure of the project, in which the encoding and storage of all documents and products to be provided by the project has been recorded in advance.