03.05.2014 Views

COPC Action Items (as of 20 August 2009) Spring 2009 Action Items ...

COPC Action Items (as of 20 August 2009) Spring 2009 Action Items ...

COPC Action Items (as of 20 August 2009) Spring 2009 Action Items ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>COPC</strong> <strong>Action</strong> <strong>Items</strong><br />

(<strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09)<br />

<strong>Spring</strong> <strong>20</strong>09 <strong>Action</strong> <strong>Items</strong><br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>09-1.1: CSAB will acquire an NPP/C1/C2 antenna deployment schedule<br />

and identify product delivery latency at each major milestone in the schedule.<br />

Priority: (M)<br />

Advocate: CSAB [Nauman]<br />

Suspense: Fall <strong>20</strong>09 <strong>COPC</strong>.<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 June <strong>20</strong>09. NESDIS not on the telcon. Jim Vermeulen presented an NPOESS<br />

chart with some latency information. We still need more information about exactly when<br />

the latency reductions take place for each receptor site implementation/activation.<br />

• CSAB 16 July <strong>20</strong>09. Selina Nauman will review Jim Vermeulen’s NPOESS chart and<br />

check with Kathy Kelly for additional information.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Selina Nauman, Jim Vermeulen, and Allan Darling will develop<br />

a briefing for <strong>COPC</strong> using the NPOESS chart and add discussion points about possible<br />

latency reductions by reordering the schedule. Review the briefing at the CSAB F2F.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>09-1.2: Final reductions in NPOESS product latency will not be realized<br />

until C2 implementation (SafetyNet). CSAB will identify technical and/or budgetary issues that<br />

could be addressed to influence the schedule to deliver reduced product latency earlier in the<br />

schedule.<br />

Priority: (L)<br />

Advocate: CSAB [Darling]<br />

Suspense: Fall <strong>20</strong>09 <strong>COPC</strong>.<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 June <strong>20</strong>09. Allan Darling – we will wait for the latency schedule from <strong>20</strong>09-<br />

1.1.<br />

• CSAB 16 July <strong>20</strong>09. JAG/ODAA will look into getting budgetary figures for receptor<br />

installments. CSAB will need to develop possible recommendations that could reduce<br />

latency and present this at the Fall <strong>COPC</strong>.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. This will be covered within the briefing developed for response<br />

to <strong>COPC</strong> <strong>20</strong>09-1.1.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>09-1.3: CSAB will collect Operational Processing Center’s operational<br />

impacts related to decommissioning <strong>of</strong> GOES-10 and report out to <strong>COPC</strong> Principles.<br />

Priority: (H)<br />

Advocate: CSAB [Zapotocny]<br />

Suspense: June <strong>20</strong>09<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Closed.<br />

• CSAB 18 June <strong>20</strong>09. John Zapotocny sent a letter to each center and will compile the<br />

impacts before the end <strong>of</strong> June. Preliminary results show that only AFWA <strong>of</strong> the centers,<br />

will have minor to moderate impacts.<br />

• CSAB 16 July <strong>20</strong>09. John Zapotocny sent the list <strong>of</strong> impacts to OFCM. Donell Woods<br />

sent the results to the <strong>COPC</strong> Directors and TDs on 30 June <strong>20</strong>09. This item will be<br />

completed with inclusion into the CSAB briefing to <strong>COPC</strong>.


• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. This item will be completed with inclusion into the CSAB<br />

briefing to <strong>COPC</strong>.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>09-1.4: CSAB will collect Operational Processing Center’s operational<br />

impacts during invocation <strong>of</strong> current NESDIS CIP capability, identify impacts that would be<br />

mitigated by a hot backup capability and report out to <strong>COPC</strong>.<br />

Priority: (M)<br />

Advocate: CSAB<br />

Suspense: Fall <strong>20</strong>09 <strong>COPC</strong>.<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 June <strong>20</strong>09. Allan Darling – will send out a request for each center to identify<br />

impacts with the current CIP capability. These impacts will be compiled into a strawman<br />

statement showing what <strong>COPC</strong> would expect from a hot backup capability and what<br />

impacts could possibly be alleviated.<br />

• CSAB 16 July <strong>20</strong>09. Allan Darling w<strong>as</strong> not able to attend. John Zapotocny – AFWA<br />

h<strong>as</strong> sent out a request to all field units to review the priority schedule <strong>of</strong> products.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Allan Darling will compile each Center’s response into one<br />

briefing to be presented at the <strong>COPC</strong> meeting. Review the briefing at the CSAB F2F.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>09-1.5: The dropout team will evaluate the affect <strong>of</strong> satellite wind,<br />

satellite radiance, and aircraft data on model dropouts. They will also invite JCSDA and<br />

ECMWF to coordinate in their efforts.<br />

Priority: (M)<br />

Advocate: JAG/ODAA<br />

Suspense: Fall <strong>20</strong>09 <strong>COPC</strong>.<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 June <strong>20</strong>09. Brad Ballish – looking into the aircraft temperature bi<strong>as</strong><br />

correction, trying to refine how to use aircraft data. Brad will send out another invitation<br />

to ECMWF to get them more involved in addressing the dropouts for possible solutions.<br />

• CSAB 16 July <strong>20</strong>09. Brad Ballish – drafted a work plan and had it reviewed by the<br />

NCEP Dropout Team and his branch chief. Incorporated these comments and sent it out<br />

to Jim Vermeulen, Chuck Skupniewicz, and Rolf Langland for comment.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Brad Ballish – The NCEP and Navy members <strong>of</strong> the dropout<br />

team have approved a draft plan <strong>of</strong> action. Bradley Ballish h<strong>as</strong> met with Dr. Sid<br />

Boukabara, the JCSDA deputy and Dr. Lars Peter Riishojgaard, the JCSDA director. The<br />

JCSDA is planning for more involvement with the dropout team, and Lars will <strong>as</strong>sist the<br />

dropout team in <strong>as</strong>king questions and requesting more involvement with the ECMWF.<br />

Lars is a good friend with the new director <strong>of</strong> research at the ECMWF. Review at the<br />

CSAB F2F.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>09-1.6: NAVO will determine if Ocean Glider data is rele<strong>as</strong>able and if<br />

so, CSAB will acquire details on the content and format <strong>of</strong> data to be made available from the<br />

NAVO Ocean Glider Program and explore the possibility <strong>of</strong> a data delivery pilot.<br />

Priority: (L)<br />

Advocate: CSAB [M<strong>as</strong>on]<br />

Suspense: Fall <strong>20</strong>09 <strong>COPC</strong>.<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Closed.<br />

• CSAB 18 June <strong>20</strong>09. George M<strong>as</strong>on – NAVO is still investigating the rele<strong>as</strong>ability <strong>of</strong><br />

the glider data, however, currently it is not rele<strong>as</strong>able.


• CSAB 16 July <strong>20</strong>09. Lamar Russell – this is not the <strong>of</strong>ficial response yet, but it looks<br />

like this data will not be made available to non-DoD users.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Lamar Russell – the <strong>of</strong>ficial response is this data will not be<br />

made available to non-DoD users. Recommend closure and inclusion into the CSAB<br />

briefing.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>09-1.7: AFWA, FNMOC and NAVOCEANO will review, sign and<br />

implement the WestPac alignment/back plan document, Option 1 and continue to explore<br />

implementation <strong>of</strong> Option 2.<br />

Priority: (H)<br />

Advocate: JAG/OCM [Kuchera]<br />

Suspense: Fall <strong>20</strong>09 <strong>COPC</strong>.<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 June <strong>20</strong>09. Evan Kuchera – document h<strong>as</strong> been reworked to separate option 1<br />

and option 2. Goal is to be at the signature point during late summer and starting<br />

implementation in late fall.<br />

• CSAB 16 July <strong>20</strong>09. Evan Kuchera – document is ready for signatures. Evan will send<br />

the document to Ken for distribution to CSAB. CSAB will need to review the document<br />

to determine the appropriate level <strong>of</strong> signatures.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Evan Kuchera – Option 1, the document is ready for signatures.<br />

Option 2, is not being addressed at this time. Results <strong>of</strong> the action will be added to the<br />

JAG/OCM briefing for CSAB and <strong>COPC</strong>.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>09-1.8: CSAB will coordinate a workshop for subject-matter experts to<br />

plan development and testing <strong>of</strong> a WestPac ensemble intended for future operations. Plan will<br />

include development milestones, methods for developing and managing ensemble diversity, type<br />

<strong>of</strong> products, number <strong>of</strong> members and an estimate <strong>of</strong> resource requirements.<br />

Priority: (M)<br />

Advocate: CSAB [Darling, Kuchera]<br />

Suspense: Fall <strong>20</strong>09 <strong>COPC</strong>.<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 June <strong>20</strong>09. Evan Kuchera – both AFWA and CNMOC feel they are not ready<br />

to hold a workshop on ensembles. Continue monitoring and develop a respond to this<br />

action item for the fall <strong>COPC</strong>.<br />

• CSAB 16 July <strong>20</strong>09. Evan Kuchera and Chuck Skupniewicz – developed ensembles<br />

vision bullets and this is proposed fulfillment <strong>of</strong> <strong>20</strong>09-1.8, <strong>as</strong> all parties agree it is too<br />

early to begin making exact specifications for ensemble exchange due to unresolved<br />

scientific issues. In addition, there is a mesoscale ensembles workshop at the DTC on<br />

23-24 September that can also serve <strong>as</strong> fulfillment <strong>of</strong> this AI.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Evan Kuchera –the Ensembles Vision Paper along with the<br />

mesoscale ensembles workshop can serve <strong>as</strong> fulfillment <strong>of</strong> this AI.<br />

Other <strong>COPC</strong> <strong>Action</strong> <strong>Items</strong> Status<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>08-2.11: JAG CCM shall coordinate the development <strong>of</strong> the next<br />

generation <strong>COPC</strong> shared network infr<strong>as</strong>tructure with DoD and NOAA IT leadership. The JAG


CCM shall leverage projects currently underway that are planning a NOAANet-DoD enterprise<br />

network capability. [NUOPC related]<br />

Priority: (M)<br />

Advocate: JAG/CCM – [Craig Hegemann]<br />

Suspense: <strong>Spring</strong> <strong>20</strong>09 CSAB meeting or (April 1, <strong>20</strong>09).<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 December <strong>20</strong>08. CCM h<strong>as</strong> invited Craig Hegemann to brief the current effort<br />

<strong>of</strong> a NOAAnet to DOD enterprise solution, at the next CCM telcon. The goal is to<br />

widen the scope <strong>of</strong> this project to also consider Navy and NESDIS. Review and update<br />

the status at the next CSAB telcon.<br />

• CSAB 22 January <strong>20</strong>09. Luis Cano – CCM h<strong>as</strong> a meeting scheduled for 11 Feb <strong>20</strong>09<br />

with AFWA TD, CNMOC N6, Navy TDs, NESDIS Deputy CIO, and TOC Director.<br />

Review and update the status at the next CSAB telcon.<br />

• CSAB 26 February <strong>20</strong>09. Luis Cano – CCM held the meeting and produced the Next<br />

Steps, which includes a data requirements gathering effort.<br />

• CSAB 19 March <strong>20</strong>09. Luis Cano – need to hear back from Craig Hegemann to see if<br />

he h<strong>as</strong> been in contact with the appropriate level at DISA. Review and update the status<br />

at the next CSAB meeting.<br />

• CSAB 16 April <strong>20</strong>09. JAG/CCM recommends keeping this action open. This action<br />

item is being actively worked and an enterprise solution timeline will be presented at the<br />

<strong>Spring</strong> <strong>COPC</strong>.<br />

• CSAB 18 June <strong>20</strong>09. Ken Barnett – held a successful meeting with DISA and CCM at<br />

DISA HQ. Working a short-term solution for DATMS-U bandwidth constraints that will<br />

connect with the long-term <strong>COPC</strong> Enterprise solution.<br />

• CSAB 16 July <strong>20</strong>09. Luis Cano – DISA working a short-term solution for DATMS-U<br />

bandwidth constraints. The technical approach h<strong>as</strong> been approved and now this effort is<br />

waiting for higher level DISA approval.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Luis Cano – working hard with DISA for the short-term<br />

solution for DATMS-U bandwidth constraints. The JAG/CCM is waiting for CNMOC to<br />

approve submitting the TSRs.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>08-2.12: JAG CCM will provide an ongoing process to capture and<br />

coordinate telecommunication requirements across <strong>COPC</strong> partners. These requirements would<br />

include the size <strong>of</strong> the data, when the data needs to be transmitted, when the data needs to be<br />

received, which <strong>COPC</strong> partner will send the data, which <strong>COPC</strong> partner will receive the data, the<br />

schedule <strong>of</strong> when new data will or needs to be enabled, encryption requirements, other data<br />

restrictions, and related <strong>COPC</strong> business functions. As a follow-on action item, this process would<br />

be used to validate technical designs and resource estimates for new network infr<strong>as</strong>tructure<br />

initiatives. This process would provide <strong>COPC</strong> continuing value by supporting network capacity<br />

management for existing infr<strong>as</strong>tructure and help justify funding requests for future network<br />

upgrades. [add nuopc-specific language: capture rqmts against proposed NUOPC data rqmts]<br />

[NUOPC related]<br />

Priority: (M)<br />

Advocate: JAG/CCM – [Luis Cano (Chair)]<br />

Suspense: <strong>Spring</strong> <strong>20</strong>09 CSAB meeting or (April 1, <strong>20</strong>09).<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 December <strong>20</strong>08. The CCM plan is to develop a template to gather<br />

requirements to allow for technical analysis on the capacity that is needed for the future<br />

and to <strong>as</strong>sist with budgetary decisions.


• CSAB 22 January <strong>20</strong>09. Luis Cano – CCM h<strong>as</strong> a meeting scheduled for 11 Feb <strong>20</strong>09<br />

and we may start to touch on each OPC’s requirements. Review and update the status at<br />

the next CSAB telcon.<br />

• CSAB 26 February <strong>20</strong>09. Luis Cano – CCM held the meeting and produced the Next<br />

Steps, which includes a data requirements gathering effort.<br />

• CSAB 19 March <strong>20</strong>09. Luis Cano – The requirements gathering data call went out to<br />

the <strong>COPC</strong> CIOs on 11 March with a response date <strong>of</strong> 24 April. Review and update the<br />

status at the next CSAB meeting.<br />

• CSAB 16 April <strong>20</strong>09. JAG/CCM recommends keeping this action open. The JAG/CCM<br />

is beginning to analyze the requirements. Current status will be presented at the <strong>Spring</strong><br />

<strong>COPC</strong> meeting.<br />

• CSAB 18 June <strong>20</strong>09. Ken Barnett – still waiting for the final CNMOC approved Navy<br />

requirements and continuing to analyze. CCM will push again for long-term<br />

requirements once the short-term solution is implemented.<br />

• CSAB 16 July <strong>20</strong>09. Luis Cano –final CNMOC approved Navy requirements is close to<br />

being returned to CCM.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Luis Cano –still waiting for final CNMOC approved Navy<br />

requirements. Jim Vermulen will send an email to CNMOC to stress the importance <strong>of</strong><br />

these two actions.<br />

<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>08-2.15: CSAB will formally invite NUOPC Program Manager (or<br />

designee) to attend all future <strong>COPC</strong> meetings and to participate in CSAB meetings. [NUOPC<br />

related]<br />

Priority: (H)<br />

Advocate: John Zapotocny, Allan Darling, Ken Barnett<br />

Suspense: December <strong>20</strong>08 CSAB Telcon.<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 18 December <strong>20</strong>08. OFCM will send a letter to Fred Toepfer with the request to<br />

join <strong>COPC</strong>. After a NUOPC representative is on <strong>COPC</strong>, we will work to have<br />

representation on CSAB and JAG/OCM.<br />

• CSAB 22 January <strong>20</strong>09. Ken Barnett – will draft a letter for review by Allan and John<br />

and then for signature by the Federal Coordinator.<br />

• CSAB 26 February <strong>20</strong>09. Ken Barnett – this h<strong>as</strong> not been done.<br />

• CSAB 19 March <strong>20</strong>09. Ken Barnett – draft letter is in for final review and will be sent<br />

from the Federal Coordinator to the Executive Steering Group and CC to <strong>COPC</strong>. Review<br />

and update the status at the next CSAB meeting.<br />

• CSAB 16 April <strong>20</strong>09. CSAB recommends keeping this action open and the removal <strong>of</strong><br />

the JAG/OCM participation. Waiting for a response from the Executive Steering Group<br />

about NUOPC participations on CSAB.<br />

• CSAB 18 June <strong>20</strong>09. Ken Barnett – OFCM will wait until after the July NUOPC ESG<br />

meeting for an <strong>of</strong>ficial response to the letter.<br />

• CSAB 16 July <strong>20</strong>09. Ken Barnett – still waiting for the NUOPC ESG meeting which<br />

h<strong>as</strong> been rescheduled to the first week <strong>of</strong> <strong>August</strong>.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Ken Barnett – no response back from NUOPC ESG but a recent<br />

meeting w<strong>as</strong> held and the coordination with <strong>COPC</strong> w<strong>as</strong> discussed. .


<strong>COPC</strong> <strong>Action</strong> Item <strong>20</strong>08-1.5: Develop a monitoring system to analyze differences between the<br />

NCEP and FNMOC global models and the ECMWF global model in real-time and make this<br />

real-time system available to OPCs <strong>as</strong> a daily tool.<br />

Priority: (M)<br />

Advocate(s): JAG/ODAA – [Mr. James Vermeulen, Dr. Bradley Ballish]<br />

Suspense: <strong>Spring</strong> <strong>20</strong>09 CSAB meeting for status update<br />

Status <strong>as</strong> <strong>of</strong> <strong>20</strong> <strong>August</strong> <strong>20</strong>09: Open.<br />

• CSAB 29 July, <strong>20</strong>08. Jim Vermeulen noted link to the same work <strong>as</strong> the preceding two<br />

AIs (<strong>COPC</strong> AI <strong>20</strong>08-01.3 and <strong>20</strong>08-01.4) and that work is ongoing.<br />

• CSAB 26 <strong>August</strong>, <strong>20</strong>08. CDR Moran noted the briefing out to <strong>COPC</strong> should cover all<br />

three AIs (<strong>COPC</strong> AI <strong>20</strong>08-01.3, <strong>20</strong>08-01.4, and <strong>20</strong>08-01.5).<br />

• CSAB 18 September, <strong>20</strong>08. Recommend closing three AIs (<strong>COPC</strong> AI <strong>20</strong>08-01.3, <strong>20</strong>08-<br />

01.4, and <strong>20</strong>08-01.5) by preparing one briefing that addresses the content <strong>of</strong> each AI.<br />

Status: Prepare a briefing to review the global models issues for <strong>COPC</strong> and a draft<br />

briefing at the next CSAB meeting.<br />

• CSAB 22 October, <strong>20</strong>08. Determine the way forward from the <strong>COPC</strong> Executive<br />

Session. After the Dropout Team’s briefing to <strong>COPC</strong>, does <strong>COPC</strong> want continued work<br />

towards developing a real-time monitoring system <strong>as</strong> a daily analysis tool.<br />

• CSAB 21 November, <strong>20</strong>08. Jim Vermeulen and Brad Ballish will have a<br />

recommendation at the next CSAB telcon.<br />

• CSAB 18 December <strong>20</strong>08. Allan Darling will work with Jim Vermeulen and Brad<br />

Ballish to determine if this item needs to be adjusted in scope.<br />

• CSAB 22 January <strong>20</strong>09. Allan Darling – Nothing to report on this action.<br />

• CSAB 26 February <strong>20</strong>09. Allan Darling – Nothing to report on this action.<br />

• CSAB 19 March <strong>20</strong>09. Allan Darling, James Vermeulen, and Brad Ballish will hold a<br />

telcon to discuss this action. Review and update the status at the next CSAB meeting.<br />

• CSAB 16 April <strong>20</strong>09. CSAB recommends keeping this action open. A status briefing<br />

will be presented at the <strong>Spring</strong> <strong>COPC</strong>.<br />

• CSAB 18 June <strong>20</strong>09. Brad Ballish – review and update at the next CSAB telcon.<br />

• CSAB 16 July <strong>20</strong>09. Brad Ballish – in conjunction with AI <strong>20</strong>09-1.5, a work plan h<strong>as</strong><br />

been drafted but who will actually perform the tool development is yet to be determined.<br />

• CSAB <strong>20</strong> <strong>August</strong> <strong>20</strong>09. Brad Ballish – The NCEP and Navy members <strong>of</strong> the dropout<br />

team have approved a draft plan <strong>of</strong> action. Bradley Ballish h<strong>as</strong> started work on a draft<br />

Project Management Charter for the work needed to accomplish this action item

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!