Upload
nasapmc
View
13.787
Download
0
Tags:
Embed Size (px)
Citation preview
RiskapediaAn ESMD Risk Management Service
for NASA’s Project Managers, Project Engineers, and Risk
Practitioners
Presented by Isaac Addison HeardARES Corporation
on behalf of ESMD Integrated Risk & Knowledge Management Systemsat the NASA 2010 Program Management Challenge February 9th, 2010
1Used with permission
2
Every year or so, web-based technology is introduced which revolutionizes the way we work…
3
wiki
4
wi·ki (wĭk'ē) n. pl. wi·kisA collaborative website whose content can be edited by anyone who has access to it.
Wikipedia is written collaboratively by volunteers from all around the world; anyone can edit it. Since its creation in 2001, Wikipedia has grown rapidly into one of the largest reference web sites, attracting at least 684 million visitors yearly by 2008. There are more than 75,000 active contributors working on more than 10,000,000 articles in more than 260 languages. As of today, there are 2,859,752 articles in English. Every day, hundreds of thousands of visitors from around the world collectively make tens of thousands of edits and create thousands of new articles to augment the knowledge held by the Wikipedia encyclopedia.
“The new force that is bringing people together on the net to create a giant brain.”
5
ESMD has over 350 wikis spaces in ICE
wikis in ESMD
• News R&KM updates• R&KM related Process, People,
Meetings, and Tools• Most recent directorate top risk list
• Meeting Calendar Archive• Contacts, ICD and IRD Development • Upcoming meeting info and useful links
• Repository of Ares PDR data
• Offers quick links to relevant pages
• Schedules, contacts, and other useful info
6
Riskapedia
7
Riskapedia (pronounced risk·ĕ·pē·diə)
A collaborative website to help NASA engineers identify, analyze, and mitigaterisks.
Risk Managers Project Managers Project Engineers
8
9
Astronauts use checklists and you should too…
Smart people have learned a lot of lessons learned into checklists that can help youidentify risks on your project.
10
The Identify Risk section is a checklist
based approach to defining risks
TRIMS
MITRE Risk Management
Tool Kit
Constellation Program Hazard
Analysis Methodology
Software Development
Taxonomy Carnegie
Mellon
11
Risk identification wiki in practice…3 easy steps for any engineer
1. Select the Risk Identification icon and select the relevant risk identification checklists / taxonomies.
2. Use one or more checklists / taxonomies to identify a candidate risk list.
3. Augment Riskapedia identification checklists / taxonomy based on experience (if required)
12
Tools enable a team to assess risk
Pro
bab
ility
Den
sity Requirement
Weight
Relative Area = Probability of Meeting
Requirement
Failure ofSystem
Failure ofSub-System A
Failure ofSub-System B
Failure ofSub-System C
Failure ofSub-System F
Failure ofSub-System E
Failure ofSub-System G
Failure ofSub-System D
Or
PRA Techniques
0.0
0.2
0.4
0.6
0.8
1.0
11/22/98 12/6/98 12/20/98 1/3/99 1/17/99 1/31/99 2/14/99 2/28/99 3/14/99
Revised Evaluation Initial Evaluation
12/31/98
Date CSOC Ready to Proceed
Like
lihoo
d
Schedule Analysis
1. LTA Processes2. LTA
Resources
1. LTA Time 1. Agenda
4. LTA Meeting Ground Rules
6. LTA Minutes / Doc of Decisions
2. LTA Facility
3. LTA Participation
3. Confrontational
3. Expectations (data v. discussion) 2. LTA Preparation
1. Wrong People (too many, too few, no portfolio)
3. LTA Presentation Template
2. LTA Agenda
1. Unclear Purpose
7. LTA Leadership6. LTA Web-Based Tools
4. Expectations (Content)
4. Security
2. Usability /Speed
3. Access / Registration
1. ThinkTank / CoPs / Wikis / Portals
1. Articulation of Values / Goals / Objectives / Importance / Alignment
2. LTA Time Mgmt
3. Engagement
4. Support5. Support
7. LTA Action Tracking
1. Too Much/Little
3. Clarity (font, acronym)
9. LTA Content Format
4. “Hidden Agendas5. Actions Assignment / Outcome
5. Too Quiet / Dominant4. AV-Laptops/Projection
5. Attendees
6. PDA/cell Use
2. Format (ppt v. Narrative)
4. Density
5. Graphics
1. Activities / Sched
3. Risks
2. Issues
4. Consequences
5. Interactions
8. LTAContent Relevancy
6. Convention
2. Scheduling - Notification
4. Dist. of Read-Ahead Mat.
3. Submission/Input of Crit Read-Ahead
5. Other
Fish BonesRoot Cause
AoA
Affinity DiagramBalanced ScorecardCost/Benefit
Analysis
Decision Trees
Etc…
Risk Matrices
1
2
3
4
5
1 2 3 4 5
Prob.
Impact
13
Probablistic Risk
Assessment5x5 matrix
1. Summary2. How to3. Examples4. References
Visual Literacy
Critical Path Analysis
14
Risk Assessment wiki in practice1. Start with your risk records
2. Some risks have gone stale or need stronger characterization
3. Browse tools targeted at assessing risk and select one; perhaps the cause-and-effect diagrams
4. Hold a 2-hour facilitated team activity to re-energize the risk thinking amongst your team
Brainstorm what went wrong in critical lifting process
% Potential Ideas on
Topic
Structured Brainstorm Round 1
Structured Brainstorm Round 2Unstructured
Brainstorm Round 1
Brainstorming
Unclear Work Instructions
Handling Ring Design
Lift Crew Training Communications
Time Pressure
Coordination Between Lift Team & SMA
- Training was not adequate for this new operation
- No time for training entire crew
- Background noise
- New
- Holes did not line up
- Poor documentation
- Headset static
- Mixed messages from managers
- SMA and lift team never pre-briefed
- Vague
- No diagrams
- No explanation
Diagramming
Participant 1 2 3 4 5 6
Add Photos 20 10 10
Explain rationale for each step
10 25 15
Provide Tech Edit 45 5 …….. etc
Provide video 50 10 60
Provide QA & Lessons Learned
20 10 10
Prioritizing Action Plan Teambuilding15
You are not alone…
Others have solved similar risks and you
can learn from what they did
Risks similar to yours have caused
failures in other programs and you
can learn from these
… but you don’t have time to go search for this
information 16
Nodes are focused on risk mitigations in engineering
disciplines
Verification Risks
Engineering Design Risks
Quality Assurance
Risks
Human Factors
andSoftware(recently added)
17
Table of ContentsSynopsisFishboneRisk Prevention StrategiesDesign Engineering Risks Good Examples from ARM and IRMAExperience-based InsightsNoted Space System FailuresRelevant DocumentsReferencesKeywordsRelated Topics
Informed By
Lets take a tour through TOC…
18
Table of ContentsSynopsisFishboneRisk Prevention StrategiesDesign Engineering Risks Good Examples from ARM and IRMAExperience-based InsightsNoted Space System FailuresRelevant DocumentsReferencesKeywordsRelated Topics
19
Supporting Functions
Risk University
Get Help – Risk Squad
Discussion Forums20
Syllabus designed to teach Level 3 and Level 2 risk managers the best practices of risk management
Currently 8 self study courses• How to create well written risk
statements• Integration risks• NASA risk policy• Etc…
Suggested study duration and timeline
21
PANEL URGES SHIFT IN STATION’S ORBITBy WILLIAM J. BROADPublished: June 9 , 1993
The expert panel advising the White House on redesigning the space station has called for the proposed astronaut outpost to be launched into a “world orbit” where it could be reached not only by American space shuttles but also by Russian, Japanese, and Chinese rockets.
…“It would change things in a fundamental way,” said Dr. Bruce Murray, a planetary scientist at the California Institute of Technology. “It would say it’s not an American space station but an international one. It would say that the Cold War really is over and that we’re enthusiastic about going on to the new phase instead of acting like we’re trying to prevent time from marching on.”
…Today, winged spaceships soaring out of Cape Canaveral usually fly into an orbit inclined 28.5 degrees to the Equator, a path beyond the reach of the Russians. That orbit was also where the space station, proposed in 1984 amid the Cold War, was to be built piecemeal as the American shuttle fleet carried its numerous parts into space.
…Now, the 16-member White House advisory panel, headed by Dr. Charles M. Vest, president of the Massachusetts Institute of Technology, has endorsed a higher inclination for the American station in working papers and a draft report for President Clinton.
…If the station is launched into an orbit the Russians can reach, the white paper said, the United States could “use their entire stable of previously developed Soviet launch vehicles – as needed.”
…Cooperation with Russians could reduce costs, but the paper noted that the station’s current international partners, Japan, Canada, and Europe, “generally disagree with us about the desirability of this orbital inclination.”
The drawback of the proposed path, it noted, is that shuttles flying to a higher inclination can lift less payload, up to 11,500 pounds less than the craft’s top lifting power of 55,000 pounds…
Now, the 16-member White House advisory panel, headed byDr. Charles M. Vest, president of the Massachusetts Institute of Technology,
has endorsed a higher inclination for the American station in working papers and a draft report for President Clinton.
Lightweight Tank – Risk Management Case Study Asynchronous
collaboration –brainstorm, bin, rank, actions.
Process 2.0 –Facilitation techniques to involve yourgroup in solving yourproblems
Brainstorm what went wrong in critical lifting process
% Potential Ideas on
Topic
Structured Brainstorm Round 1
Structured Brainstorm Round 2Unstructured
Brainstorm Round 1
22
• Ask a question• Propose discussion on a topic of interest• Answer someone else’s question
23
Riskapedia
Designed to help you1. Identify risks2. Analyze risks3. Mitigate risks
…And get work done24
Riskapedia is currently based on input from some smart people…
… but not as smart as everyone in this room.
We want your input, your insights, and your examples to help NASA projects benefit from your knowledge!
25
What you can do…
… contribute!
26
Challenge: Contribute something this week – just one thing.
• Edit content in Risk ID, Risk Assessment, and Risk Mitigation notes (almost all content is editable).
• Initiate or participate in discussions
• Vote, rank, or comment on content usefuleness
• In consultation with ESMD - become a subject matter practitioner with full editing rights to “own” a content area.
ITAR, SBU(not allowed in wikis)
27
Your benefit for contributing
1. You will feel good about sharing your insights
2. You will have participated 1st hand in the wiki movement
3. Some NASA engineer, somewhere, will be grateful as they incorporate your advice into solving their problem.
28
Questions?
29