Presentation on theme: "The Value of Technical Performance Measures Ann Lynn The Boeing Co. (314) 234-9714 All Data in this pitch is Notional – for example."— Presentation transcript:
The Value of Technical Performance Measures Ann Lynn The Boeing Co. (314) 234-9714 firstname.lastname@example.org All Data in this pitch is Notional – for example only
Agenda TPM Definition Typical Types of TPMs Constructing TPM Profiles –Performance Thresholds –Plan Over Time –Uncertainty –Management Process –Allocation of Margin Roll-up (Parent/Child) TPMs Value to a Program
Technical Performance Measures Represent critical technical thresholds and goals for success of the program Should be variable and responsive to engineering changes Usually exist in a hierarchy corresponding to the spec levels (system, subsystem, component…) Have target values corresponding to specification values –that is, your TPM should be a parameter in a spec at some level Are tracked and statused against their defined plan and represent the technical health of the program
Typical Types of TPMs Parameters that flow from and/or support KPPs Key Constraints and Performance Reqmts –Weight, power, heat load –Reliability/ Maintenance parameters –System / subsystem performance Endurance Range Latency Accuracy Efficiency Etc –Cost (e.g. AUPC) Parameters associated with Program Technical Risks or areas of technical challenge TPMs should represent a balanced set of key parameters; Dont monitor something just because you can
Example TPM Status Chart This view shows:Title/DefinitionStatus against spec Status Color (RYGB)Maturity of the status Example Monthly / Quarterly Status
Definition of Performance Thresholds (Generic) Blue – the system exceeds requirements by more than x (and may be subject to re-allocation) Green – the system meets all performance requirements Yellow – the system can meet some objectives but does not meet all performance requirements Red – the system cannot perform satisfactorily TPM margin Spec value TPM margin Note, reqmts can be negotiated/updated with corresponding updates to Specs and TPMs. Setup as shown, the parameter has to meet the spec to be green.
TPM Profile Over Time This view of the TPM allows you to see history and trends in performance
Profiles over time (cont.) For this TPM, performance is planned to improve over time. If actual progress >= planned, you are green, even if you havent achieved the end-state target (spec value) TPMSpecStatus Unit Efficiency24%22.2% (Meas.) TPM using current status, not predicted status at end of program
Weight Management 9 Current Baseline Wt. 3588.0 lb Spec NTE Weight 3850 lb IPT Weight Allocations 3588 lb Baseline weight reflects current configuration sized to loads at NTE weight requirement. Projected weight includes planned design changes and X% weight maturity growth risk for post PDR design maturity. 9 Current Projected Wt. (w/ Growth Risk) 3971.3 lb Projected weight (projected value at end of program) includes a historical growth factor TPMSpecStatus System Weight38503971 (projected) TPMSpecStatus System Weight38503588 (current) TPM if using current status TPM if using projected status Weight TPM usually plotted per the Weight Mgmt process; Show both values, status to Projected;
TPM Profile with uncertainty bar include an uncertainty bar for each reported value Spec value line If your project has significant Risk, or it is early in the project, TPM status can be deceiving unless uncertainty is understood
TPM Management Process (Generic) TPM margin Spec value TPM margin The approach to monitor and control is predicated on correct allocations of margin In the blue: consider adjusting that parameters spec value and taking relief elsewhere In the green: press on! In the yellow, or alarming trend: take a program-defined action (put on Risk Watch list, initiate reqmts/design trade, establish new risk mitigation, initiate change to design, reqmts, or plan) In the red: take a program-defined action (establish new risk mitigation, initiate change to design, reqmts, or plan)
Definition of TPM Margins Factors to consider: 1.Margin may be allocated based on the amount of risk (e.g. Red Risk or low TRL subsystem gets a greater share of margin) 2.Margin may be allocated based on relative impact to System performance (accounts for sensitivities) 3.Margin may be limited by the hard points - those parameters that have a hard stop which prevents acceptable operation (e.g. structural limits for weight) TPM margin Spec value TPM margin Margin: How bad can it get before status goes red? How good must it be before status goes blue?
*System Parameter* Tree *System Parameter* Energy Collection Energy Storage Power Distribution Power Consumption SPC efficiency ESS RT efficiency EPD efficiency PPX efficiency Convertor efficiency Wiring efficiency Propulsion ConsumptionSubsys Pwr Consump VMS / MS Subsys Z ESS components A components B components Prop efficiency Aero efficiency AV Weight VMS Subsys Z ESS Subsys A Subsys B Propulsion Subsys X ESS param Drag maneuvers Stability High Sensitivity Lower sensitivities Cruise consump ESS degradation This diagram maps the subsystem parameters that contribute to the system-level parameter; Sensitivities are noted.
Associated Risks *Sys Parameter* Energy Collection Energy Storage Power Distribution Power Consumption SPC efficiency ESS RT efficiency EPD efficiency PPX efficiency Convertor efficiency Wiring efficiency Propulsion ConsumptionAvionics & PSS Consump VMS Subsys Z ESS components A components B components Prop efficiency Aero efficiency AV Weight VMS Subsys Z ESS Subsys A Subsys B Propulsion Subsys X Subsys x param ESS param Drag maneuvers Stability Cruise consump ESS degradation 46-xxx 1-xxx 41 - xxx 7-xxx 2-xxx 24-xxx 56-xxxx 51-xxx 50-xxx 57-xxxx 56-xxxx 6-xxx 18-xxx 54-xxx High Sensitivity Lower sensitivities This diagram maps Risk to the subsystem parameters. Helps show where margin is needed. Shows Risk #, Title, and current level (RYG)
Interdependent TPMs Competing for their share of the overall margin Their performance needs to be monitored as a group Change (re-allocation of margin, spec adjustment) has to be managed for the group
KPPs and TPMs TPMs System level Sub- System & Cmpnt level -Propulsion Power consump -VMS Power consump -Airframe Power consump -ESS Power consump -Subsys A Power consump -Subsys Z Power consump -VMS weight -Propulsion weight -Airframe weight -ESS weight -PPX weight -Subsys A weight -Subsys Z weight (AV Efficiency at End of Mission, AV Performance) -Propulsion eff -ESS round trip eff -PPX eff -SPC eff -AV Aero eff AV Weight Time of Year at which Energy balance is closed KPPs *System Parameter* AV Power Consumption KPPs represent customer operational objectives; TPMs shown represent measurable design parameters that contribute to the KPP
Relationship of System and subsystem TPMs Example: Command Latency <= 160 ms If supplier specs are more stringent, that means margin is held at subsystem level above supplier Spreadsheets can help account for values and margins at each level Many PMs prefer to monitor Supplier-owned TPMs when available WeaponLnchrSMSMCPVI 255 5030 Launcher Spec = 5 ms Weapon Spec = 20 ms System margin PVI CMPNT1 Spec = 35 ms PVI CMPNT2 Spec = 15 ms
Example parent/child TPMs (1 of 3) OwnerTPM TitleSpec Value Current Status CESystem Command Latency160 ms136 ms Dsplys^PVI Cmd Latency50 ms Msn Cmptr ^MC Cmd Latency25 ms Stores^SMS Cmd Latency25 ms Stores^Lnchr Cmd Latency5 ms Stores^Weapon Cmd Latency25 ms31 ms System TPM can be green even when child (subsystem) TPM is red; in this case because of margin held at system level
Example parent/child TPMs (2 of 3) OwnerTPM TitleSpec Value Current Status CESystem Command Latency160 ms121 ms Dsplys^PVI Cmd Latency50 ms35 ms Msn Cmptr ^MC Cmd Latency25 ms Stores^SMS Cmd Latency25 ms Stores^Lnchr Cmd Latency5 ms Stores^Weapon Cmd Latency25 ms31 ms System TPM status can be green if child (subsystem) TPMs balance out
Example parent/child TPMs (3 of 3) Over time, System TPM margin may need to be re-allocated to compensate for subsystem over target Example: Command Latency <= 160 ms WeaponLnchrSMSMCPVI 255 5030 Launcher Spec = 5 ms Weapon Spec = 25 ms System margin 2035 Subsystem TPM in the blue range may have spec adjusted and give back margin to the System level or to another subsystem
TPMs - Takeaways Create a balanced set of key parameters Ensure the full Profile is understood by program technical leadership, even if only the stoplight format is used for periodic reviews Profile over time current vs projected status Basis for margin maturity / uncertainty Assess the risk and sensitivity of parameters to support appropriate margin allocation Know where your margin is … and isnt, so you can react to changes in reqmts or in design status TPMs can be used as a predictor of success … and failure
The Value of TPMs Track the right things –Make sure your TPMs correlate to key technical parameters Track technical progress compared to planned –Your monitoring system is only as good as the plan & thresholds you set it up with Spend the time upfront to set up correctly! –Your monitoring system is no more accurate than the data you put in maturity / uncertainty of reported data must be evaluated Conisder plotting uncertainty bars on data points to avoid false sense of security