ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] Framework for the FY12 Operating Plan and Budget Posted for Community Review

  • To: Council GNSO <council@xxxxxxxxxxxxxx>
  • Subject: [council] Framework for the FY12 Operating Plan and Budget Posted for Community Review
  • From: Glen de Saint Géry <Glen@xxxxxxxxx>
  • Date: Sun, 20 Feb 2011 13:50:12 -0800
  • Accept-language: fr-FR, en-US
  • Acceptlanguage: fr-FR, en-US
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AcvQjrLg/HrrYJ3wTmy7s6d7oZav3wAXcGMw
  • Thread-topic: Framework for the FY12 Operating Plan and Budget Posted for Community Review

FYI
http://www.icann.org/en/announcements/announcement-18feb11-en.htm

Framework for the FY12 Operating Plan and Budget Posted for Community Review

18 February 2011

Proposed Framework for the Fiscal Year 2012 (FY12) Operating Plan and 
Budget<http://www.icann.org/en/planning/ops-budget-framework-fy2012-en.pdf> 
[PDF, 1.07 MB]

FY12 Summary of SO/AC/SG Additional 
Requests<http://www.icann.org/en/financials/so-ac-sg-requests-summary-fy12-en.pdf>
 [PDF, 48 KB]

Translated versions of the Framework will be available in the following 
languages soon:

 *   Español
 *   العربية
 *   Français
 *   Русский
 *   中文

The release of Proposed Framework for the Fiscal Year 2012 (FY12) Operating 
Plan and 
Budget<http://www.icann.org/en/planning/ops-budget-framework-fy2012-en.pdf> 
[PDF, 1.07 MB] kicks off the operational planning process for ICANN, providing 
the community with their first look at the current and planned work, along with 
estimated financial resources required for FY12.

There are several noticeable changes in this year's Framework. One is that it 
is in a presentation format to provide an overview of the proposed components 
that will evolve into a full Operating Plan and Budget for the coming year. The 
feedback and involvement of the ICANN community in the evolution from Framework 
to Operating Plan is critical in making this a workable and implementable 
budget. Second, this year there was early and targeted engagement between the 
ICANN staff and the leaders of the various SO's, AC's and SG's, establishing an 
agreed upon base of services and support that have been and will continue to be 
included in the yearly budget. Along with this came the opportunity for these 
constituencies to provide input regarding additional services and activities 
for fiscal year 2012. The schedule of this input is posted with the Framework 
in the public comment area. It is now up to the community to comment on this 
set of identified priorities and how they should fit into the FY12 plan. Last 
but not least, a shift in how the budget is viewed: from both an Operating and 
Fixed Cost standpoint as well as from planned and ongoing Project work costs. 
Core Operations is everything that is the daily work of ICANN(support, 
maintenance, services) and Projects are the short and long term activities and 
programs that are born out of community and /or Board requests, funded, and do 
reflect ICANN's Strategic Plan and Mission.

The Framework will be discussed with members of the ICANN community at the 
Silicon Valley meeting in San Francisco this March, with feedback received 
through both the online public comment process as well as through individual 
meetings and conference calls with ICANN Supporting Organizations (SO), 
Advisory Committees (AC) and Stakeholder Groups (SG). A more detailed draft 
FY12 Operating Plan and Budget will be posted by 17 May 2011. After additional 
public comment and feedback is received and synthesized, the budget will be 
sent to the ICANN Board for adoption at ICANN Public Meeting 41 in June 2011.

Please go to 
http://www.icann.org/en/public-comment/public-comment-201104-en.htm#op-budget-fy2012
 and provide your input by 4 April 2011.

Glen de Saint Géry
GNSO Secretariat
gnso.secretariat@xxxxxxxxxxxxxx<mailto:gnso.secretariat@xxxxxxxxxxxxxx>
http://gnso.icann.org



<<< Chronological Index >>>    <<< Thread Index >>>