7/27/2019 Rp Dev Guidelines

http://slidepdf.com/reader/full/rp-dev-guidelines 1/2

AACE® International Recommended Practice (RP) Development Guidelines (Rev 2013-11-14)

Page 1 of 2 

Recommend Practice (RP) Development Guidelines

Expectations and Requirements:

RPs must be submitted and reviewed by AACE International subject matter experts and

approved by the AACE Technical Board. The following are some expectations of RP content;

  Professional — Peer review publication quality with appropriate references.

  Fit for use — The RP will address practical needs of the professional community.

 Use a variety of materials — An RP may contain original content, existing material, or acombination of material from any source (in compliance with copyright laws).

  References — List applicable AACE reference materials. Use or refer to external

references in compliance with copyright laws.

  Scoping Document – The RP should be aligned with a corresponding pre-approved

scoping document.

  Concise — Attempt to limit each RP to 10 pages or less.

  Benchmark practices — Where there are a variety of acceptable practices, identify the

range of practices and compare them in the RP. Specific examples from industry or

other organizations are valuable where appropriate. Most RP’s are intended to be

generic in nature, unless written as an “As Applied In” RP. 

  Appropriate Level – The RP must convey the technical content written at an appropriate

level of understanding.

  Define terms — All terminology must be consistent with 10S-90, Cost Engineering

Terminology. Any key terms not contained in 10S-90, must be submitted for inclusion Tis

includes not only new terms, but revisions as well.

RP Types

There are two types of RP’s, “Generic” and “As Applied In”: 

  Generic — A broad overview of the practice at a summary level that applies to most

industries. It may be centered on a generic process diagram with summary description

7/27/2019 Rp Dev Guidelines

http://slidepdf.com/reader/full/rp-dev-guidelines 2/2

AACE® International Recommended Practice (RP) Development Guidelines (Rev 2013-11-14)

Page 2 of 2 

of process steps. Defines basic processes, practices, guidelines, etc., and avoids specific

“how-to” details. Serves as a foundation to “As Applied In” RPs. For example: 17R-97:

Cost Estimate Classification System.

  As Applied In — A detailed examination of a generic RP to a specific application or

industry. Includes references, benchmarks, and practices specific to that application orindustry. Should be in alignment with generic RP (if it exists). May provide “how-to”

specifics. For example: 18R-97: Cost Estimate Classification System - As Applied in

Engineering, Procurement, and Construction for the Process Industries

Typical RP Outline

RP outlines may vary, but the following are typical headings for a document. (Double-click on

the icon below to view)

RP Template/Outline