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

CCM shall leverage projects currently underway that are planning a NOAANet-DoD enterprise
network capability. [NUOPC related]
Priority: (M)
Advocate: JAG/CCM – [Craig Hegemann]
Suspense: Spring 2009 CSAB meeting or (April 1, 2009).
Status as of 20 August 2009: Open.
• CSAB 18 December 2008. CCM has invited Craig Hegemann to brief the current effort
of a NOAAnet to DOD enterprise solution, at the next CCM telcon. The goal is to
widen the scope of this project to also consider Navy and NESDIS. Review and update
the status at the next CSAB telcon.
• CSAB 22 January 2009. Luis Cano – CCM has a meeting scheduled for 11 Feb 2009
with AFWA TD, CNMOC N6, Navy TDs, NESDIS Deputy CIO, and TOC Director.
Review and update the status at the next CSAB telcon.
• CSAB 26 February 2009. Luis Cano – CCM held the meeting and produced the Next
Steps, which includes a data requirements gathering effort.
• CSAB 19 March 2009. Luis Cano – need to hear back from Craig Hegemann to see if
he has been in contact with the appropriate level at DISA. Review and update the status
at the next CSAB meeting.
• CSAB 16 April 2009. JAG/CCM recommends keeping this action open. This action
item is being actively worked and an enterprise solution timeline will be presented at the
Spring COPC.
• CSAB 18 June 2009. Ken Barnett – held a successful meeting with DISA and CCM at
DISA HQ. Working a short-term solution for DATMS-U bandwidth constraints that will
connect with the long-term COPC Enterprise solution.
• CSAB 16 July 2009. Luis Cano – DISA working a short-term solution for DATMS-U
bandwidth constraints. The technical approach has been approved and now this effort is
waiting for higher level DISA approval.
• CSAB 20 August 2009. Luis Cano – working hard with DISA for the short-term
solution for DATMS-U bandwidth constraints. The JAG/CCM is waiting for CNMOC to
approve submitting the TSRs.
COPC Action Item 2008-2.12: JAG CCM will provide an ongoing process to capture and
coordinate telecommunication requirements across COPC partners. These requirements would
include the size of the data, when the data needs to be transmitted, when the data needs to be
received, which COPC partner will send the data, which COPC partner will receive the data, the
schedule of when new data will or needs to be enabled, encryption requirements, other data
restrictions, and related COPC business functions. As a follow-on action item, this process would
be used to validate technical designs and resource estimates for new network infrastructure
initiatives. This process would provide COPC continuing value by supporting network capacity
management for existing infrastructure and help justify funding requests for future network
upgrades. [add nuopc-specific language: capture rqmts against proposed NUOPC data rqmts]
[NUOPC related]
Priority: (M)
Advocate: JAG/CCM – [Luis Cano (Chair)]
Suspense: Spring 2009 CSAB meeting or (April 1, 2009).
Status as of 20 August 2009: Open.
• CSAB 18 December 2008. The CCM plan is to develop a template to gather
requirements to allow for technical analysis on the capacity that is needed for the future
and to assist with budgetary decisions.