F35项目风险管理

发布时间 : 星期一 文章F35项目风险管理更新完毕开始阅读

MOOG

AIRCRAFT GROUP

to score each risk in Probability of Occurrence and Consequence of Occurrence on Performance, Schedule and Cost. These Risk Templates are included in Appendix B. We then used Lockheed Martin’s Risk Assessment chart to obtain an overall risk rating for each risk. The ratings are grouped into High, Moderate or Low (Red, Yellow or Green), depending on the overall score

This risk scoring process will continue to be used for future risks identified through the course of the program. 3.4

Risk Workbooks

A Risk Workbook was developed for each of the 6 identified risks with a Moderate or High rating. The workbook is in the form of an Excel spreadsheet. Lockheed Martin’s Active Risk Manager (ARM) tool reads data directly from each risk workbook as a means to gain visibility of the WFAS risks and to roll them up into Lockheed Martin’s overall risk management process.

Lockheed Martin’s ARM system captures a description of the risk issue, its consequence, scoring and fallback plan as well as the risk mitigation steps that will drive the risk level to Low over time, including dates and workaround plans. The WFAS Excel workbooks are submitted to BAE Systems/Lockheed Martin for their inputs to ARM. 3.5

Risk Mitigation Work Packages

Once each risk’s mitigation plan and a risk owner have been defined, the mitigation steps defined in each plan are entered into the Master Program Schedule or appropriate detail schedule for tracking purposes. 3.6

Reviews

The WFAS team presently meets weekly on Mondays for overall program status and communication. The WFAS Risk Manager will utilize the first Monday of every month to review status of the risk issues in a team setting and to take action, where necessary. Each meeting will address the following agenda items:

? Review status of every High risk issue and assign action items as necessary

to keep the risk mitigation plans on track ? Review status of Moderate risk issues not addressed the previous month and

assign action items as necessary to keep the risk mitigation plans on track ? Solicit and discuss new “worries”

? Review “worry” list and consider converting any worries to risk if appropriate.

Assign Owners to any new risks.

MOOG

MOOG INC. TORRANCE, CA 90501

CAGE CODE 0ZWK8

PAGE 5 OF 59

MRE13419

MOOG

AIRCRAFT GROUP

? Approve proposed risks and their mitigation plans ? Approve fallback plans, trigger points & funding

Following the monthly status meetings, the information is used to update the program schedules containing these mitigation steps. Overall risk status is provided on a monthly basis.

3.7 Roles And Responsibilities

The roles and responsibilities for the participants are as follows.

Tim BaptistProduct Line Mgr.WFASJeff Hadfield, PMWFAS Project Engr.NguyenConfig MgmtW. RollinsCont. Admin.S. MillerQualityG. FillmanILSC. BartolottaCostJones/FrydrychData Mgmt.P. PolcariMat'ls PlanningS. FaunceMfg Engr.R. CameronMech. DesignGitnes/ScottMech. Sys. AnalysisE. PolcuchReliabilityG. LiuLab EngrR. VetterStress/ThermalL. El-BayoumyMOOG

MOOG INC. TORRANCE, CA 90501

CAGE CODE 0ZWK8

PAGE 6 OF 59

MRE13419

MOOG

AIRCRAFT GROUP

Figure 1. F-35 WINGFOLD ACTUATION SYSTEM MOOG ORGANIZATION

? WFAS Risk Manager: This person is responsible for overseeing the WFAS risk reduction process. This responsibility includes ensuring that the Teams continue using standardized processes, keeping track of risk mitigation progress, updating BAE Systems/Lockheed Martin of the risk status, and presiding over the monthly risk review meetings. ? Risk Owners: These owners oversee the identification, scoring, and

execution of mitigation plans for the risks assigned to them. ? Risk Worriers: All other contributors to the WFAS program are encouraged to be risk worriers and suggest items for addition to the worry list.

3.8 New Risks

The Risk Worriers initially identify new risks. For each potential new risk, the appropriate Risk Manager works with the risk worrier to establish a proposed initial risk score. If this score falls in the moderate or high-risk categories, they will establish a risk mitigation plan. The risk is then presented to the WFAS during the monthly Risk Management described in section 3.6.

Once the team reviews the risk, and if scored moderate or high, the mitigation steps are planned and added to the appropriate program schedule, as described in section 3.5. The completed risk workbook is submitted to BAE Systems/Lockheed Martin for approval and incorporated into ARM. 3.9

Closing Risks

A risk is closed if it is deemed to have changed to a low risk per the risk scoring process before the planned mitigation steps are complete. This would happen if circumstances change from that initially foreseen at the risk’s initial scoring, such as if requirements are changed. The process is similar to that of adding a new risk in that the appropriate Risk Worrier and Risk Manager propose a change in risk scoring with rationale to the Risk team meeting. If the team approves the change in risk rating to low the Risk Manager submits the proposed re-scoring with written rationale to BAE Systems/Lockheed Martin for approval.

Risks can also be closed from tracking and reporting if the originally proposed mitigation steps have been completed and the risk is now considered low per the originally established exit criteria.

MOOG

MOOG INC. TORRANCE, CA 90501

CAGE CODE 0ZWK8

PAGE 7 OF 59

MRE13419

MOOG

AIRCRAFT GROUP

3.10 Status Reporting

Moog reports WFAS risk status at monthly reviews and at major design reviews (PDR and CDR). The format presented (a quad chart and a waterfall chart) is generated from ARM based on an ARM-generated status report sent from BAE Systems/Lockheed Martin. This report is sent to Moog at least once a month and it consists of a list of risk mitigation steps that are either past due or due within sixty days and a Status field for each step. Moog fills in the status for each mitigation step and returns the document to BAE Systems/Lockheed Martin. Each risk owner provides the status to the WFAS Risk Manager who compiles it for insertion onto the status summary.

For mitigation steps that are not on track, the status will provide the rationale and indicate a back on track date.

MOOG will eventually have access to LM IMF(Integrated management framework), which provides visibility and reporting capability for risk data. 3.11 Configuration Management

Once WFAS risks are approved by BAE Systems/Lockheed Martin and incorporated into ARM, BAE Systems/Lockheed Martin through ARM maintains their configuration management. However, the WFAS Risk Manager is responsible for configuration management of risks that have not yet been customer approved and for change requests. Unapproved risks are maintained as risk workbooks, described in section 3.4, and are labeled with version numbers within the filename per the following convention:

XXXXXX_VerYY

where XXXXXX is the risk name and YY is the version number. The risk name can be any number of characters, whereas the version number is always two characters. When risk plan changes are requested of the customer/or internal requests, the WFAS Risk Manager keeps a copy of the written request and maintains configuration of those requests. Once the requested change is approved, the risk work book is updated with the re-plan information and the revised risk work book is supplied to LM for ARM import. 4.

SUPPLIER RISK MANAGEMENT The Risk Manager and team risk worriers will assume the responsibility of overseeing the risks associated with component suppliers. These suppliers are expected to be active participants in risk mitigation steps and their planning as appropriate, but will not be asked to practice a formal risk management process, such as the plan outlined herein.

MOOG

MOOG INC. TORRANCE, CA 90501

CAGE CODE 0ZWK8

PAGE 8 OF 59

MRE13419

联系合同范文客服:xxxxx#qq.com(#替换为@)