[NASA Logo]

NASA Procedures and Guidelines

This Document is Obsolete and Is No Longer Used.
Check the NODIS Library to access the current version:
http://nodis3.gsfc.nasa.gov

NPR 9501.3
Eff. Date: November 24, 2002
Cancellation Date: March 31, 2006

Earned Value Management Implementation on NASA Contracts
| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | Appendix_a | Appendix_b | ALL |


Appendix A: Example Data Requirements Descriptions (DRD)

A.1 EVM System Description (Criteria)

1. DPD NO.: XXX ISSUE: Standard 2. DRD NO.: STD/MA-MSD-C
3. DATA TYPE: 1 4. DATE REVISED:
5. PAGE: 2/1

6. DESCRIPTION/USE: To provide a description of the contractor's methods, policies, and procedures utilized in meeting the requirements of NPD 9501.3A.

7. OPR : RS40 8. DM :

9. DISTRIBUTION: Per Contracting Officer's letter

10. INITIAL SUBMISSION: After notification of selection, but prior to contract award per NFS 1852.242-74.

11.SUBMISSION FREQUENCY: Per the direction of the cognizant Government Contracting Officer; update as required.

12. REMARKS: Reference is made to NPD 7120.4B, Program/Project Management and NPG 7120.5A, Program and Project Management Process and Requirements. These documents shall be used as guides in preparation of the Earned Value Management System Description. Changes to the EVMS shall be processed in accordance with NFS 1852.242-75.

13. INTERRELATIONSHIP: NFS 1852.242-74, "Notice of Earned Value Management System" (March 99) and NFS 1852.242-75, Earned Value Management System (March 99)

14. DATA PREPARATION INFORMATION:

14.1 SCOPE: The EVM System Description shall provide a description of the system and the contractor's comprehensive plan for complying with the requirements of NPD 9501.3A.

14.2 APPLICABLE DOCUMENTS

14.3 CONTENTS: The EVM System Description shall provide an understanding of each activity required to meet the requirements of NPD 9501.3A. The document shall briefly, but comprehensively, present the contractor's approach and schedule of internal activities to comply with NPD 9501.3A requirements and to demonstrate this compliance to each NASA Center. The document shall include the contractor's plan for implementation of and activities leading up to the demonstration review with the NASA Center Compliance Review Team. The contractor shall provide a monthly status of progress toward meeting this plan until the contractor's management system is accepted by the NASA Center Review Team. The plan shall address the requirements of NFS 1852.242-74 and NFS 1852.242-75.

14.4 FORMAT: Contractor format is acceptable.

14.5 MAINTENANCE: Changes shall be incorporated by change page or complete reissue.

A.2 EVM System Description (Modified Criteria)

1. DPD NO.: XXX ISSUE: Standard 2. DRD NO.: STD/MA-MSD-NC
3. DATA TYPE: 3 4. DATE REVISED:
5. PAGE: 1/2

6. DESCRIPTION/USE: To provide a description of the contractor's methods, policies, and procedures utilized in meeting the requirements of NPD 9501.3A.

7. OPR : RS40 8. DM :

9. DISTRIBUTION: Per Contracting Officer's letter

10. INITIAL SUBMISSION: Summary with proposal per NFS 1852.242-77.

11. SUBMISSION FREQUENCY: Per the direction of the cognizant Government Contracting Officer; update as required.

12. REMARKS: Reference is made to NPD 7120.4B, Program/Project Management and NPG 7120.5A, Program and Project Management Process and Requirements. These documents shall be used as guides in preparation of the Earned Value Management System Description. Changes to the EVMS shall be provided in accordance with NFS 1852.242-76.

13. INTERRELATIONSHIP: NFS 1852.242-76, Modified Cost Performance Report (March 99) and NFS 1852.242-77, Modified Cost Performance Report Plans (March 99)

14. DATA PREPARATION INFORMATION:

14.1 SCOPE: The Earned Value Management System Description shall provide a description of the system and the contractor's comprehensive plan for complying with the requirements of NPD 9501.3A.

14.2 APPLICABLE DOCUMENTS

14.3 CONTENTS: The EVM System Description shall provide an understanding of each activity required to meet the requirements of NPD 9501.3A. The document shall briefly present the contractor's approach and schedule of internal activities to meet the requirements of NPD 9501.3A. The document shall include the contractor's plan for implementation of and activities leading up to the demonstration review with the NASA Center Compliance Review Team. The contractor shall provide a monthly status of progress until the contractor's management system is accepted by the NASA Center. The description shall address the procedures required by NFS 1852.242-76.

14.4 FORMAT: Contractor format is acceptable.

14.5 MAINTENANCE: Changes shall be incorporated by change page or complete reissue.

A.3 Cost Performance Report

1. DPD NO.: XXX ISSUE: Standard 2. DRD NO.: STD/MA-CPR
3. DATA TYPE: 3 4. DATE REVISED:
5. PAGE: 1/3

6. DESCRIPTION/USE: To provide information for (1) integrating cost and schedule performance data with technical performance measures, (2) assessing the magnitude and impact of actual and potential problem areas causing significant cost and schedule variances, and (3) providing valid, timely project status information to higher management.

7. OPR: RS40 8. DM:

9. DISTRIBUTION: Per Contracting Officer's letter

10. INITIAL SUBMISSION: 90 days after Authority to Proceed. Format 5: Initial Cost Performance Report (CPR) shall contain rankings of cost and schedule drivers.

11. SUBMISSION FREQUENCY: Monthly; by the 10th working day following the close of the prior month accounting period. Format 5: Updated list of the rankings every 6 months, based on performance to date.

12. REMARKS:

13. INTERRELATIONSHIP: The Financial Management Reports (DRD STD/MA-FMR) shall include a reconciliation between the Monthly Contractor Financial Management Report/Quarterly Contractor Financial Management Report (533M/533Q) and the Cost Performance Report, which shall be submitted as an attachment to the 533M/533Q reports. The CPR reporting levels and frequency shall be in accordance with the Contract WBS (DRD STD/MA-WBS) and contract provisions.

14. DATA PREPARATION INFORMATION:

14.1 SCOPE: The Cost Performance Report (CPR) includes data to measure cost and schedule performance.

14.2 APPLICABLE DOCUMENTS DI-MGMT-81466 Data Item Description for Cost Performance Report (available at http://www.acq.osd.mil/pm/newpolicy/cpr_cfsr/cpr_finl.html)

14.3 CONTENTS: The CPR shall include data pertaining to all authorized contract work, including both priced and unpriced effort, that has been authorized at a not-to-exceed amount in accordance with the Contracting Officer's direction. The CPR shall separate direct and indirect costs and identify elements of cost for all direct reporting elements. The CPR shall consist of the following:

  1. Format 1, Work Breakdown Structure (WBS): Format 1 shall provide data to measure cost and schedule performance by summary level WBS elements, and the hardware, software, and services NASA is buying. Critical/major subcontractor summary-level performance measurement data shall be included as an attachment to Format 1. Subcontractor CPR or Cost/Schedule Status Report (C/SSR) are acceptable.
  2. Format 2, Organizational Categories: Format 2 provides the same data as Format 1, sorted by the contractor organization. If the contractor is organized by product, Format 2 is optional. Organizational category reporting shall be to the first level of the program's organizational structure.
  3. Format 3, Baseline: Format 3 provides the budget baseline plan against which performance is measured. It is the baseline report used to track all changes to the Performance Measurement Baseline (PMB). Format 3 shall contain workforce forecasts for two 3-month periods (columns 10 and 11), two subsequent 12-month periods (columns 12 and 13), and the remainder of the contract for the last period (column 14).
  4. Format 4, Staffing: Format 4 shall provide workforce staffing forecasts for correlation with the budget plan and cost estimates and contain the workforce baseline which will be updated and submitted whenever the Performance Measurement Baseline changes. Organizational category reporting shall be to the first level of the program's organizational structure. Format 4 shall contain baseline and workforce forecasts for two 3-month periods (columns 10 and 11), two subsequent 12-month periods (columns 12 and 13), and the remainder of the contract for the last period (column 14).
  5. Format 5, Explanations and Problem Analyses: Format 5 shall be a narrative report used to explain significant cost and schedule variances and other identified contract problems. Subcontractor variance analyses (determined by the prime contractor) and a discussion of the prime contractor's analysis of the subcontractor's performance shall be provided in Format 5. In the initial submission of the CPR (Format 5), the contractor shall rank, in descending order of criticality (i.e., the most critical elements will be at the top of the list and the least critical will be at the bottom), all reporting-level WBS elements anticipated (as determined by the contractor Project Manager) to be schedule drivers, and all WBS elements (in a similar ranking) anticipated to be the cost drivers on the project. The contractor shall submit an updated list of the rankings every 6 months, based on performance to date. The Government reserves the right to modify this ranking based on Government perception of criticality. If the contractor uses "critical path" scheduling techniques, identification of the critical path by WBS element will meet the schedule drivers' requirement. Ranking of the critical path cost drivers shall also be provided. These critical elements shall reconcile to the Master Schedule submitted to the Government.
  6. Variance Analysis: The Variance Analysis shall be a narrative report addressing the following:
  1. Reporting elements that equate to 50 percent of the list of the schedule drivers (i.e., if 20 schedule drivers are listed, the 10 most critical schedule driver variances over $100k will be addressed). If there are 10 or less schedule driver variances, all variances over $100k shall be addressed.
  2. Reporting elements that comprise the top 50 percent of the cost drivers (i.e., if 20 cost drivers are listed, the top 10 most critical cost driver variances over $100k). If there are 10 or less cost driver variances, all cost variances over $100k shall be addressed.
  3. Impact to the contract Estimate-at-Complete (EAC) for all cost and schedule driver variances addressed.
  4. Explanation for all variances at completion over $500k.
  5. Corrective Action Plan, as applicable.

14.4 FORMAT: CPR formats shall be completed according to the instructions outlined in DI-MGMT-81466 and the following forms: Format 1 (DD Form 2734/1); Format 2 (DD Form 2734/2); Format 3 (DD Form 2734/3); Format 4 (DD Form 2734/4); and Format 5 (DD Form 2734/5). Images of the CPR forms are located at http://www.acq.osd.mil/pm/newpolicy/cpr_cfsr/cpr_gif_new.html. Contractor format shall be substituted for CPR formats whenever they contain all the required data elements at the specified reporting levels in a form suitable for NASA management use. The CPR shall be submitted electronically and followed up with a signed paper copy. The American National Standards Institute (ANSI) X12 standards (transaction sets 839 for cost and 806 for schedule), or the United National Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) equivalent, shall be used for Electronic Data Interchange. This information is located at http://www.unece.org/trade/untdid/.

14.5 MAINTENANCE: None required

A.4 Modified Cost Performance Report

1. DPD NO.: XXX ISSUE: Standard 2. DRD NO.: STD/MA-MCPR
3. DATA TYPE: 3 4. DATE REVISED:
5. PAGE: 1/3

6. DESCRIPTION/USE: To provide information for (1) integrating cost and schedule performance data with technical performance measures, (2) assessing the magnitude and impact of actual and potential problem areas causing significant cost and schedule variances, and (3) providing valid, timely program status information to higher management.

7. OPR : RS40 8. DM :

9. DISTRIBUTION: Per Contracting Officer's letter

10. INITIAL SUBMISSION: Within 90 days after Authority to Proceed. Format 5: Initial Modified Cost Performance Report (MCPR) shall contain rankings of cost and schedule drivers.

11. SUBMISSION FREQUENCY: Monthly; by the 10th working day following the close of the prior month accounting period. Format 5: Updated list of the rankings every 6 months, based on performance to date.

12. REMARKS:

13. INTERRELATIONSHIP: The Financial Management Reports (DRD STD/MA-FMR) shall include a reconciliation between the Monthly Contractor Financial Management Report/Quarterly Contractor Financial Management Report (533M/533Q) and the Modified Cost Performance Report, which shall be submitted as an attachment to the 533M/533Q reports. The MCPR reporting levels and frequency shall be in accordance with the Contract WBS (DRD STD/MA-WBS) and contract provisions.

14. DATA PREPARATION INFORMATION:

14.1 SCOPE: The MCPR includes data to measure cost and schedule performance.

14.2 APPLICABLE DOCUMENTS DI-MGMT-81466 Data Item Description for Cost Performance Report (available at http://www.acq.osd.mil/pm/newpolicy/cpr_cfsr/cpr_finl.html)

14.3 CONTENTS: The MCPR shall include data pertaining to all authorized contract work, including both priced and unpriced effort, that has been authorized at a not-to-exceed amount in accordance with the Contracting Officer's direction. The MCPR shall separate direct and indirect costs and identify elements of cost for all direct reporting elements. The MCPR shall consist of the following:

  1. Format 1, Work Breakdown Structure (WBS): Format 1 shall provide data to measure cost and schedule performance by summary level WBS elements, and the hardware, software, and services NASA is buying. Critical/major subcontractor summary level performance measurement data shall be included as an attachment to Format 1. Subcontractor MCPR or Cost/Schedule Status Report (C/SSR) are acceptable.
  2. Format 3, Baseline: Format 3 provides the budget baseline plan against which performance is measured. It is the baseline report used to track all changes to the Performance Measurement Baseline (PMB). Format 3 shall contain baseline forecasts for two 3-month periods (columns 10 and 11), next two subsequent 12-month periods (columns 12 and 13), and the remainder of the contract for the last period (column 14).
  3. Format 5, Explanations and Problem Analyses: Format 5 shall be a narrative report used to explain significant cost and schedule variances and other identified contract problems/actions. Subcontractor variance analyses (determined by the prime contractor) shall be provided and a discussion of the prime contractor's analysis of the subcontractor's performance shall be provided in Format 5. In the initial submission of the MCPR (Format 5), the contractor shall rank, in descending order of criticality (i.e., the most critical elements will be at the top of the list and the least critical will be at the bottom of the list), all reporting level WBS elements anticipated (as determined by the contractor Project Manager) to be schedule drivers, and all WBS elements (in a similar ranking) anticipated to be the cost drivers on the project. The contractor shall submit an updated list of the rankings every 6 months, based on performance to date. The Government reserves the right to modify this ranking based on Government perception of criticality. If the contractor uses "critical path" scheduling techniques, identification of the critical path by WBS element will meet the schedule drivers' requirement. Ranking of the critical path cost drivers shall also be provided. These critical elements shall reconcile to the Master Schedule submitted to the Government.
  4. Variance Analysis: The Variance Analysis shall be a narrative report and address the following:
  1. Reporting elements that equate to 50 percent of the list of the schedule drivers (i.e., if 20 schedule drivers are listed, the 10 most critical schedule driver variances over $100k will be addressed). If there are 10 or less schedule driver variances, then all variances over $100k shall be addressed.
  2. Reporting elements that comprise the top 50 percent of the cost drivers (i.e., if 20 cost drivers are listed, the top 10 most critical cost driver variances over $100k). If there are 10 or less cost driver variances, then all cost variances over $100k shall be addressed.
  3. Impact to the contract Estimate-at-Complete (EAC) shall be provided for all cost and schedule driver variances addressed.
  4. Explanation for all variances at completion over $500k.
  5. Corrective Action Plan, as applicable.

14.4 FORMAT: MCPR formats shall be completed according to the instructions outlined in DI-MGMT-81466 and the following forms: Format 1 (DD Form 2734/1); Format 3 (DD Form 2734/3); and Format 5 (DD Form 2734/5). Images of the MCPR forms are located at http://www.acq.osd.mil/pm/newpolicy/cpr_cfsr/cpr_gif_new.html. Contractor format shall be substituted for M/CPR formats whenever they contain all the required data elements at the specified reported levels in a form suitable for NASA management use. The MCPR shall be submitted electronically and followed up with a signed paper copy. The American National Standards Institute (ANSI) X12 standards (transaction sets 839 for cost and 806 for schedule), or the United National Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) equivalent, shall be used for Electronic Data Interchange. This information is located at http://www.unece.org/trade/untdid/.

14.5 MAINTENANCE: None required

A.5 Work Breakdown Structure (WBS) and WBS Dictionary

1. DPD NO.: XXX ISSUE: Standard 2. DRD NO.: STD/MA-WBS
3. DATA TYPE: 2 4. DATE REVISED:
5. PAGE: 1/4

6. DESCRIPTION/USE: To establish a framework for reporting program cost, schedule, and technical performance. To provide a basis for uniform planning, reporting status, program visibility, and assignment of responsibilities.

7. OPR: RS40/VS10 9. DM:

9. DISTRIBUTION: Per Contracting Officer's letter

10. INITIAL SUBMISSION: Draft with proposal.

11. SUBMISSION FREQUENCY: 30 days after Authority To Proceed, update as required. Revised pages shall be submitted 10 calendar days after contract WBS changes (following Government approval).

12. REMARKS: NPD 7120.4B, Program/Project Management, and NPG 7120.5A, Program and Project Management Processes and Requirements, and MIL-HDBK-881, Department of Defense Handbook Work Breakdown Structure, shall be used as guides in the preparation of the WBS and the WBS dictionary.

13. INTERRELATIONSHIP:

14. DATA PREPARATION INFORMATION:

14.1 SCOPE: The WBS establishes a product-oriented logical subdivision of hardware, software, services, facilities, etc., that make up the total project scope of work. The WBS Dictionary provides a narrative description of the tasks and effort to be performed in each WBS element.

14.2 APPLICABLE DOCUMENTS: None

14.3 CONTENTS:

  1. The WBS index shall include--
  1. Line item number.
  2. WBS elements/tasks listed by title and indentured to reflect the level (e.g., level 1 is total contract; levels 2 and following are successively lower levels).
  3. Indication of phase (i.e., research, development, test and evaluation; or production; or both) with which the WBS element is associated.
  4. Contract line item associated with the WBS element.
  5. Statement Of Work (SOW) paragraph numbers associated with the WBS element.
  6. Specification number of the specification that covers the WBS element (if applicable). If the specification is associated with more than one WBS element, indicate the specification paragraph numbers associated with the WBS element.
  7. Contract end item number of WBS element (if applicable).
  1. WBS Dictionary - The WBS dictionary shall describe the technical and cost content of every WBS element and efforts associated with each element (e.g., design, development, manufacturing). For WBS elements specified elsewhere for cost reporting, the WBS dictionary definitions shall also include the exact narrative of the directly associated SOW paragraphs. The WBS dictionary shall be arranged in the same order as the contract WBS index. Following the description of the WBS element shall be a listing of lower level WBS elements. The WBS dictionary shall include the following for each WBS element:
  1. WBS element title, number, and element task description.
  2. Performance Measurement Criteria (PMC).
  3. SOW paragraph number.
  4. Specification (number and title) associated with the WBS element.
  5. Contract line item associated with the WBS element.
  6. Date, revision number, revision authorization, and approved changes.
  7. Contract end item/data item number and quantity.
  8. Cost content and description.
  9. WBS code and work order/work authorization.
  10. Technical content.
  11. System contractor.
  12. Associate or subcontractor.
  13. Applicable SOW narrative.

14.4 FORMAT: The WBS shall be in a chart format showing element relationships, arranged in the same order as the WBS provided in the Request for Proposal. The WBS Dictionary shall be ordered in consonance with the WBS index and shall reference each WBS element by its identifier and name.

14.5 MAINTENANCE: Changes shall be incorporated by change page or complete reissue.



A.6 Project Schedules

1. DPD NO.: XXX ISSUE: Standard 2. DRD NO.: STD/MA-PS
3. DATA TYPE: 2 4. DATE REVISED:
5. PAGE: 1/2

6. DESCRIPTION/USE: To provide the contractor's time-phased plan, current status, key milestones, task interdependencies, and major development phases necessary to accomplish the total scope of work. To provide management visibility into contractor status and potential problem areas, critical path identification and assessment, trend analysis, and to serve as a basis for evaluating contractor performance.

7. OPR : RS40 8. DM :

9. DISTRIBUTION: Per Contracting Officer's letter

10. INITIAL SUBMISSION: Preliminary with proposal. Initial -- first calendar month following the end of the first full month after Authority To Proceed.

11. SUBMISSION FREQUENCY: Monthly, no later than the 10th day of the calendar month following the end of the contractor's calendar month.

12. REMARKS: Reference is made to NPG 7120.5A, NASA Program and Project Management Processes and Requirements. This document shall be used as a guide in preparation of the Project Schedules.

13. INTERRELATIONSHIP: DRD's, Work Breakdown Structure and Dictionary (STD/MA-WBS), and, Project Management Plan (STD/MA-PMP)

14. DATA PREPARATION INFORMATION:

14.1 SCOPE: The Project Schedules provide data for the assessment of contract schedule and logic network of the tasks to be performed.

14.2 APPLICABLE DOCUMENTS: NPD 9501.3A Earned Value Management

14.3 CONTENTS: The Project Schedule and Logic Network report shall document the contractor's time-phased plan for completing the total contracted scope of work. Schedules shall contain the approved baseline schedule as well as current forecasted dates and shall be traceable to the approved Contract Work Breakdown Structure (CWBS). Project Schedules and Logic Network shall be reported in four sections. All data contained in the sections shall be consistent, statused monthly and based on the same cutoff date.

  1. Project Master Schedule -- One page, top level, Gantt-type summary document arranged by WBS that reflects all contract and controlled milestones, major project phases (i.e., design, fabrication, integration, assembly) and all end item deliveries.
  2. WBS Summary Schedules -- Gantt-type summary documents arranged by WBS that cover each WBS level TBD element. Data reflected within these schedules shall be at least at the WBS level TBD with lower level detail being provided as required by MSFC project management. These schedules shall contain identification of major project phases (i.e., design, fabrication, integration and assembly, test and acceptance), all contract and controlled milestones, key subcontractor milestones, and end item delivery dates, critical path identification, key data delivery dates, and key Government Furnished Property (GFP) need dates. (To prevent potential conflicts in schedule data and to minimize data maintenance, it is recommended that these schedules be summary extractions from the automated logic network database.)
  3. Logic Network Database -- An automated logic network database consisting of schedule data for all CWBS elements. The entire scope of work shall be broken into schedule tasks and milestones at a consistent level of detail to allow discrete progress measurement and visibility into the overall development, fabrication, integration, assembly, test, and delivery phase of each end item deliverable. Additionally, all schedule tasks/milestones shall be integrated with the appropriate sequence relationships to provide a total end-to-end logic network leading to each end-item delivery. The logic network database serves as the basis for identification of project critical paths as well as critical schedule analysis.
  4. Contractor Schedule Assessment Report -- This report shall contain a trend analysis of weeks ahead/behind for each WBS level TBD element, primary and secondary critical path narrative, variance rationale and impact statements for contract/controlled milestone variances, and proposed work-around plans for significant behind schedule situations.

14.4 FORMAT: Contractor format is acceptable. Submission of the project schedules and logic network shall be by standard hardcopy and electronic media. Electronic media submittals shall be in a format compatible with the project office requirements. (A legend identifying the contractor's schedule symbols used and their meaning shall be provided.)

14.5 MAINTENANCE: Changes shall be incorporated by change page or complete reissue.

A.7 Technical Performance Report

1. DPD NO.: XXX ISSUE: Standard 2. DRD NO.: STD/MA-TPR
3. DATA TYPE: 3 4. DATE REVISED:
5. PAGE: 1/2

6. DESCRIPTION/USE: To provide data for the assessment of the design, development, test, evaluation, and related integration for the system and its elements.

7. OPR: RS40 8. DM:

9. DISTRIBUTION: Per Contracting Officer's letter

10. INITIAL SUBMISSION: The first calendar month following the end of the first full month after Authority To Proceed, unless otherwise specified by the Contracting Officer.

11. SUBMISSION FREQUENCY: Monthly, submit no later than the 10th day of the calendar month following the end of the contractor's accounting month.

12. REMARKS: Reference is made to NPD 7120.4B, Program/Project Management and NPG 7120.5A, Management of Major Systems Programs and Projects. These documents shall be used as guides in preparation of the Technical Performance Report.

13. INTERRELATIONSHIP:

14. DATA PREPARATION INFORMATION:

14.1 SCOPE: The Technical Performance Report presents a comparison of the expected performance and physical characteristics with the contractually specified values. It is the basis for reporting established milestones, and describes progress toward meeting the technical requirements.

14.2 APPLICABLE DOCUMENTS: NPD 9501.3A, Earned Value Management NFS 1827.406-70, NASA Federal Acquisition Regulation Supplement, Reports of Work

14.3 CONTENTS: The Technical Performance Report shall identify specific technical parameters that are considered critical. These items shall include critical requirements such as those identified in the contract end item specification(s). The provisions for measurement and tracking each parameter may include items such as:

  1. Specification requirements and approved changes.
  2. Program events significant to the achievement of the end value.
  3. Conditions of measurement.
  4. Current measurement values.
  5. Predicted value of end product.

Identify variances from the approved technical requirements where adjustments are not made, if such variances will cause the performance of critical items to fall below the established minimum values.

In critical areas, analyze variances exceeding the tolerances to determine causes and assess the impact of changes on measurement control parameters, interface requirements, schedule, and cost, as appropriate. In instances of subcontract impact, the subcontractor's evaluation shall be obtained.

For identified performance deficiencies, procedures for developing recovery plans shall be specified that identify appropriate implications.

The contractor shall include a completed report documentation page (Standard Form 298) as the final page of each report submitted per NFS 1827.406-70.

14.4 FORMAT: Contractor format is acceptable. Quantitative measurements shall be utilized to determine program success.

14.5 MAINTENANCE: None required.



| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | Appendix_a | Appendix_b | ALL |
 
| NODIS Library | Financial Management(9000s) | Search |

DISTRIBUTION:
NODIS

This Document is Obsolete and Is No Longer Used.
Check the NODIS Library to access the current version:
http://nodis3.gsfc.nasa.gov