10.11.2014 Views

NAVAL AVIATION SYSTEMS - NASA Wiki

NAVAL AVIATION SYSTEMS - NASA Wiki

NAVAL AVIATION SYSTEMS - NASA Wiki

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CHAPTER XI: KEY TOPICS<br />

PART L: INTEGRATED BASELINE REVIEWS (IBRs)<br />

Purpose: The purpose of the IBR is to achieve a mutual understanding of the plan and its relationship to the<br />

underlying management control systems and processes that will operate during contract execution. Consequently,<br />

while an IBR may surface disagreements, the contractor cannot fail an IBR.<br />

Source Documents: DoDR 5000.2-R, SECNAVINST 5000.2B<br />

Discussion: Effective program cost and schedule management depends upon establishment of reliable contractor<br />

cost, schedule, and technical baselines. By the above references, program managers and their technical staffs of<br />

Integrated Product Teams (IPTs) are required to review contractor planning baselines within six months after<br />

contract award. This review is required for contracts requiring compliance with the DoD Earned Value<br />

Management Systems (EVMS) Criteria or Cost/Schedule Status Report requirements. The objectives of the IBR<br />

are as follows:<br />

a. Ensure reliable plans and performance measurement baselines are established which capture the entire scope<br />

of work, are consistent with contract schedules, and have adequate resources assigned to complete program tasks.<br />

b. Improve the use of cost/performance data by government and contractor program managers as a management<br />

tool.<br />

c. Reduce the number of EVMS criteria management system reviews based on insights developed throughout the<br />

assessment of the contractors actual implementation of their management system and processes.<br />

Responsibilities:<br />

a. The program managers, as leaders of the IPTs, are responsible for the conduct of the IBR (e.g. determining<br />

IBR timing, scope, and designating composition of the team) and using IBR findings to improve cost and schedule<br />

management.<br />

b. The Assistant Commander for Research and Engineering (AIR-4.0) is responsible for the<br />

development/maintenance of IBR guidelines and processes and recommending candidate programs subject to IBRs.<br />

Assistant Program Managers for Systems Engineering will lead the technical assessment during IBRs (assisted by<br />

assigned Assistant Program Managers for Logistics, NAVAIR Headquarters and field activity personnel, and<br />

contract administration offices) as directed by the PMA.<br />

c. Procuring Contracting Officers will ensure that contractors are informed, in appropriate Request for Proposal<br />

(RFP) language, of the governmentís intent to conduct IBRs after award. (Contractual authority for conducting<br />

IBRs can be found in the data access provision of the EVMS Clause 252.234-7001.) In drafting the RFP, IPTs<br />

should consider requiring submission of an appropriate level of baseline information as part of the contractor's<br />

proposal. This information may then be used in the evaluation of proposals during source selection. Contractor<br />

proposals should be prepared and evaluated in full awareness of planned IBR requirements, and IBR schedules<br />

promulgated so that the contractor can properly prepare for such reviews.<br />

d. Upon completion, the PMA should insure that the results of the IBR are documented and provided to<br />

appropriated TEAM members. Additionally, the PMA should ensure that an action plan is prepared to correct any<br />

problem areas discovered during the review. Action plan items should be regularly addressed by the PMA with the<br />

contractor during program reviews until the corrective actions are completed.<br />

3. With proper planning and preparation, IBRs can provide a means for PMAs to manage program<br />

cost/performance through a better understanding of the contractor's internal control system.<br />

61

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!