1 / 6

Lecture 4.3c: Technical Performance Measures (SEF S14-A)

Lecture 4.3c: Technical Performance Measures (SEF S14-A). Dr. John MacCarthy UMBC CMSC 615 Fall, 2006. TPMs are key technical parameters selected by management (recommended by SE) that are used to: Monitor technical progress Provide early warning of potential technical problems (risk)

ranae
Download Presentation

Lecture 4.3c: Technical Performance Measures (SEF S14-A)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lecture 4.3c: Technical Performance Measures (SEF S14-A) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

  2. TPMs are key technical parameters selected by management (recommended by SE) that are used to: Monitor technical progress Provide early warning of potential technical problems (risk) Note TPM is used in two senses: A technical performance parameter that is monitored An analysis and control process for monitoring TPMs TPM Process: Develop a TPM Planned Profile: Calculate the probable performance of each TPM (over the development cycle) based on the best information available Periodically measure the actual performance of the TPM (using a prototype or model) Compare the actual vs. projected performance vs. threshold requirement value Is predictive model accurate? Why are there differences? Are predicted and measured values trending to satisfy threshold requirement? TPM Reports are periodically provided to management & government (at technical reviews and PMRs) TPM Reports include both graphic displays and narrative explanations Technical Performance Measurement

  3. Graphic Portion: Predicted Actual Requirement Threshold and Goal Values Planned Profile and Tolerance/ Uncertainty Band Narrative Portion: Explains the graphic Identifies reasons for deviations between Planned Profile and Measured Profile Explains why deviation is serious or not Identifies actions underway (or recommended) to correct situation (if required) Note one may have to recommend a revision to the predictive model (and a revision to the Planned Profile) based on the current status (and additional information) TPM Reports [1]

  4. Contractor TPM list will generally be longer than the Government TPM list Government TPM Reports will generally be a CDRL TPMs selected for delivery to the government are expected to: Be critical to program success Trace to user operational needs Provide visibility into technical performance of key WBS elements Factors in TPM Reporting: Resources to perform TPM activities Complexity of the system Phase of Development Past experience with similar systems Ability to develop a Planned (Performance) Profile and/or measure performance during development (if not, should not be a TPM) TPM Reports [2]

  5. To identify TPMs, one should start with the End Product part of the WBS and ask: What are the critical functional performance requirements? What are subsystems/CIs perform these functions? What critical performance requirements are at most risk (consequence & likelihood)? TPM Selection, Risk, and the WBS

  6. Summary • TPMs are an important tool in the program manager’s (and SE’s) systems analysis and control tool kit • TPMs provide early warning about deviations in key technical parameters, which if not controlled, can impact system success in meeting user needs • TPMs should be reported periodically at technical reviews and project management reviews (PMRs) • TPM Reports should permit a manager and/or customer (whether technical or not) to make perceptive judgments about system technical performance and needed corrective actions when deviations occur.

More Related