Exhibit 300 Name - Risk Register
(Submission Date = )
Identify Analyze Monitor MONITOR
Likelihood
of Impact
Original Date
ID Occurence (1-5) Status Actions Taken Date of Last
Risk Category Risk Description Indentified Priority Potential Mitigation Strategy
Number (1-5) (Low to (Activity per month) Review
(mm/dd/yy)
(Least to High)
Most)
# Technical, Schedule, Description of the risk The date the risk was The order in Potential approaches to mitigate the risk; the Open / Closed What has been done so far; left blank if no action has been taken to date Date the risk was
Budget, IT Security raised which the risk BOLDED strategy indicates the strategy updated
should be chosen
considered /
dealt with on a
L / M / H scale;
based on an
average of the
potential impact
and probability
of the risk
08/31 Lease awarded
10/20 Currently working with CSC to mesh the schedules. PM continues to monitor the Facilities schedule
11/08 Scheduling workshop held Nov 3 - 5
12/01 - Expect final construction design December 17. Construction progressing
12/22 Received 100% drawings Additional design required. Addendum will be issued.
1/10 Government responded with comments to 100% design. The Vendor has over 81 issues remaining
from 90% comments.
1/11 PM escalated project management concerns with GSA, resulting in Executive meeting on 1/21
> Extend existing R&D contracts to ensure 1/12-14 Meetings on site to address design gaps for Doors, Security, Telecom, IT, AV, and monitor
continuous computing capability for short progress
delays 1/21 Executive level meeting held with GSA, NOAA, and Contractor
> Make temporary use of additional research 1/21 Contractor promised to address all Government comments during a 3-day non-Govt design team
If GSA leased data center space is not prepared on schedule for the meeting on site
compute capacity for development work for
1 Schedule delivery and installation of the computer system, the computer system will 5 5 Low Open 1/25 Contractor set new date of 2/14 to deliver design Addendum to address constructibility problems 03/02/11
longer delays
not be operational on schedule 1/28 Contractor missed deadline to provide updated, realistic baseline project schedule
> Phase data center prep activities with
delivery, installation, and acceptance of 2/01 Contractor added draft project management plan to the web site to address near-term Government's
system quality surveillance concerns
02/02/2011 - Expecting recovery schedule in one week. Will readdress impact and probability in one
week. Contractor updated baseline and recovery project schedules are due 2/03 Contractor design
Addendum is due 2/14
02/03/2011 Activity entries prior to 07/09/2010 are available in the archive, removed old entries to facilitate
viewing recent.
03/02 Revised Project schedule provided by Contractor. Looks like 3rd floor will be ready on April 4. Rest
of building schedule slip of about 3 weeks.
4/19/2009
Retraining Personnel with critical skills may become a challenge as it Reallocating positions to fill critical skill 4/8/2010: Work with HR
could impact the project ability to provide service . shortages 6/7/2010: Reviewed No Change
Fill Vacancies in a timely manner 9/3/2010: Reviewed No Change
3 Resources 2 3 Medium Open 12/20/ 2010 Submitted Paperwork to HR 1/20/2011
1/20/2011 - Working with HR
4/8/2010
10/20: Need to fully understand the process, who's responsible, meeting to be
scheduled, CCR to be submitted requesting file restore.
Test with ESPC. Map out current
11/24: COTR to propose backup strategy (under 3K), if not acceptable will propose
coverage and current holes.
1 5 Medium Open alternate plan
Describe plans to get full coverage.
12/16: NDE collecting list of assets that need to be backed-up. Geof will take it from
Close when coverage in place.
there.
4 Technical/Operations Recovery of backup mechanism not verified 10/1/2010 01/19/2011 - List to be furnished to ESPC via CCR, HJ will coordinate 1/20/2011
Work with user community to review
5 Technical/ Operations If training documents and processes do not meet users needs, 2 2 Low and improve training documents and Open
then productivity will be reduced 3/2/2011 processes. 3/2/2011
6 Budget If adequate funds are not availabe after the transition to steady 2 2 Low Review O&M funding and investigate Open
state, adjustments will need to be made 3/2/2011 additional sources of funding if needed 3/11/2011
Open 1 of 2 43afa5c7-09b7-4d8a-904f-489f7b4f7274.xlsx
Name of NOAA System - Risk Register
Likeli-
hood of Impact
Original Date
occurance (1-5) Status Actions Taken
Number Risk Category Risk Description Indentified Priority Potential Mitigation Strategy Date Closed
(1-5) (Low to (Activity per month)
(mm/dd/yy)
(Least to High)
Most)
4/23/2010: Test resource to become available upon contract award. Award expected June
2010.
Anticipate additional test resources will be provided upon
If adequate test resources do not become available, then 06/17/10: Plan is to use OSO test engineers for support, coordination meeting to be
Technical 12/3/2009 3 4 medium activation of the new ESPDS Development contract in Closed 10/20/2010
software quality suffers due to lack of validation. scheduled
April of 2010.
07/23/2010: no change
8/19/2010: New Dev contractor to conduct interviews for test engineers
9/22/2010: Commit 1 staff member and hired additional test engineer. LMCO plans to hire a
2 junior test engineer. Recommend closure.
Closed
Closed 2 of 2 43afa5c7-09b7-4d8a-904f-489f7b4f7274.xlsx