WCNI BadgerNet Update
March 11, 2005
1. Background / Expectations
a. Contract negotiations
i. Typical period 6 months to a year
ii. Accomplished in 4 months
iii. Communication blackout
1. Dec 20 through March 2nd
2. March 2, 2005 Contract signed
a. March 3rd BadgerNet Conversion Website Online
i. www.doa.state.wi.us
ii. BadgerNet rates posted for all customers
3. Conversion Process
a. Contract signed for 6 business days.
b. Held 2 extensive meetings with vendor
i. Vendor has 50 professionals assigned to conversion process
ii. 7 functional groups
1. Formulating all service delivery and support processes
c. DET customers - 6 major groups
d. Scheduled Kick Off Meetings (Being established with contacts)
i. WADEN 29 March
ii. Libraries 31 March
iii. Technical Colleges 5 April
iv. State agencies April 11 or the 13th (to be determined)
v. UW System 12
vi. WAICU 14 April
e. Anticipate meeting with CESAS
f. TEACH Information Package releases 10 March
4. Communication Plan-Gathering Order Information
a. May initial service order target
b. Each customer group is unique
i. Have specific needs, concerns, funding issues
ii. We essentially need to communicate 6 plus plans
c. Will work with individual customers after kickoff
5. Customer Conversion Planning Guides
a. Identifies DET, vendor and
customer responsibilities
b. Spreadsheets identifies current service
i. Your contact person
ii. Solicitation bandwidth request
iii. Asks you to verify bandwidth/ service to be ordered
iv. Billing information
v. Asks times you can not cut
vi. When you would like to cut
vii. Asks if you need dual service for possibly week/month
viii. Asks if you want 2 hour response/dispatch
ix. Populated as much information for you as possible
c. Identifies what happens prior to installation
i. What happens of installation
ii. Describes the actual data service installation
iii. Describes the actual video service installation
iv. Identifies HVAC, power and 4x4 plywood requirements
v. You will know who needs to be where when
6. Timelines (dates are still tentative)
a. Core installed July 5th
b. Aggregation nodes installed July 12th
c. Acceptance Pilot Video and Data Late July through August
i. Have identified number of pilot sites
ii. Need to firm up UW pilot sites.
d. Following successful pilot start conversion
i. Conversion should start in September
ii. 7 to 14 data sites a day
iii. Approximately 30 video sites / month
iv. Conversion customer timeline will be published
v. Review status on vendor portal
vi. Speed of conversion may
vary
7. Summary
a. Still in very early communication stage
b. There are many questions
c. FAQ site high daily volume
d. TEACH customers have many
questions about TEACH
i. Pending budget language for e-rate for extra lines
e. Expectations are high
f. Tension is high
g. We expect to meet your needs
i. Only ask you for what we need
ii. Be efficient as possible
iii. Communicate clearly
iv. Ask that you meet your timelines
v. When in doubt ask questions
John Nichols
From: Stuessy, Robert [Robert.Stuessy@doa.state.wi.us]
Sent: Thursday, March 03, 2005 9:54 AM
To: WCNI Committee; WCNI Technical Working Group; *DOA DET IT Directors;
State NDSC;
*DOA DET Router Management Users Group (RMUG)
Subject: Important BadgerNet Converged
Network Update
The Wisconsin Department of
Administration (DOA) has entered into an agreement with SBC Global Services, Inc.,
representing the Wisconsin BadgerNet Access Alliance (WBAA), to provide data
and video services to the State of
monthly rate for a state agency T-1 will drop from $1,067 to $600. Rates can be
found on the BCN Web site at www.doa.state.wi.us/badgernet.
DOA staff will soon start
the process of contacting customers, including state agencies, municipal
governments, and educational institutions, to gather and disseminate
information necessary to begin conversion to the new network. To stay on track
with the conversion plan, and to meet contractual deadlines, DOA will submit
circuit orders within 75 calendar days of contract signing. Therefore, DOA will
soon request that customers finalize and submit a list of sites, services
required at each site, and a commitment for the amount of bandwidth requested
at each site. DOA will also need to know specific time periods during which each
organization cannot allocate staff to work on the conversion, e.g., the
Department of Revenue's tax period. The conversion timeline will be set for each location after
successful completion of the acceptance pilots. DOA anticipates the initial
pilot will take place this summer. The timeline, as soon as it's available,
will be posted on the BadgerNet Web site. In the meantime, updates on progress
of the acceptance pilot testing will be provided to your organization's IT
management and technical staff.
Questions regarding TEACH,
its subsidies, and e-rate should be sent to teach@doa.state.wi.us.
BadgerNet network questions should be sent to badgernet@doa.state.wi.us
.
BadgerNet FAQs can be found at http://www.uwex.edu/disted/badgernet/fag/.
Bob Stuessy
Director, Bureau of
Infrastructure and Networks
Wisconsin Department of
Administration
P.O. Box 7844
Madison, Wi 53707-7844
Phone: (608)264-6186
Fax: (608)266-2164
Email:
robert.stuessy@doa.state.wi.us
DRAFT
3/23/05
BadgerNet Converged
Network (BCN) Advisory Council
1.0 Purpose:
The purpose of the Advisory Council shall be to advise the contract holder (Dept. of Administration) and the service provider for the BCN on customer issues relating to the network contract, the operation of the network, and the process for developing timely solutions to problems related to services provided under the state contract. In order to provision and manage a successful complex and changing network, customers must have regular and direct communication with the contract and network managers. The Advisory Council will serve as a conduit for customer feedback and guidance to help guarantee success. The Advisory Committee will also provide a forum for communication and planning among education and government agency customers.
A. Advising:
The Advisory Council will have as its primary goals the discovery of multi-institutional network issues and the development of policies and procedures to govern the relationship between network customers and the service provider. The “discovery” goal will include revealing issues that arise in performance of contract obligations, but more importantly, issues that arise between network components where solutions to problems are much more difficult to determine and may lie outside the boundaries of the contract. The Council will also develop policies and procedures for interaction among network members with a view to enhancing customer support and ensuring the successful operation of the network.
B. Planning
& Operations
The Advisory Council will deliberate on future network applications that may have implications for the contract and the services currently provided by the vendor. In addition, the Advisory Council will discuss interoperability issues both at the customers’ premises before entering the WAN and operational issues outside the boundaries of the WAN and the customers’ premises. As needed, the Advisory Council will provide the vendors with advice on changes/enhancements to the current network architecture or functionality and provide advice on the next generation network architecture
C. Collaboration
The Advisory Council will address collaborative issues affecting the mission and objectives of education, research, and government within a networked environment and where those collaborations may be affected by the network.
2. Membership
Membership on the Advisory Council will consist of representatives of the principal “customer” stakeholders. Representatives will be chosen by the stakeholder community (i.e., WAICU institutions will choose a representative from the private colleges and universities who use BCN). Each representative will be a voting member. Voting members may delegate an alternate to attend as a substitute in the event they cannot attend meetings. Department of Administration and WBAA/contract holders will choose a non-voting member to the Council.
The Council will be made up of representatives of the following groups:
· School Districts (2 members)
· State Agencies other than UW, WTCS, and DPI (2 members)
· UW (2 members)
· Technical Colleges (1 member)
· Libraries (1 member)
· CESAs (1 member)
· WAICU (1 member)
· DPI (1 member)
· WADEN (1 member)
· DOA (2 non-voting members)
· Vendor (1 non-voting member)
The Council will meet at least eight times a year, and may find it appropriate to meet more as events require. At least seven voting members will be required for a quorum. All meetings will be open meetings.
The Council will provide regular and sufficient communication to all interested members of the educational and governmental communities. Council members are responsible for maintaining open communications with, and seeking input from, the constituent group they represent. The Council will also seek advice and support from stakeholders who are not designated representatives, groups, for example, such as local government.
3. Council Structure
The Officers of the Council shall consist of a Chairperson, a Vice-Chairperson, and a Secretary. Their responsibilities are as follows:
- Chairperson
- Preside at general meetings and Executive Committee meetings
- Establish the agenda for general and executive meetings
- Represent the Council at appropriate meetings
- Appoint Council committees as directed.
- Vice-chairperson
- Preside at general meetings and Executive Committee meetings in the absence of the Chairperson
- Represent the Council in the Chairperson’s absence
- Secretary
- Prepare minutes of regular meetings and Executive Committee meetings
- Transmit minutes of general meetings to members within two weeks of the meetings
- Arrange the logistics for Council meetings
4. Committees
- Executive Committee
The Executive Committee will be a smaller working group to represent the interests of participating stakeholders. It shall consist of five members including the Chairperson, the Vice Chairperson, the Secretary, and two at large members. Its duties are:
1. Recommend the establishment of committees from among Council members or others as appropriate.
2. Recommend appropriate policies and procedures for decisions by the Council
3. Recommend Council positions on important issues for decision by the Council.
4. Act on emergency or time-sensitive network issues.
- Technical Committee
A Technical Committee will consist of network professionals from member institutions. Its task will be to work with DOA and the vendor community to help solve network problems and ensure that the technical components of the WAN work consistently with member LANs and the Internet. One member of the Advisory Council will serve as chair and convenor of the Technical Committee
- Other committees as agreed to by the Advisory Council.
The Advisory Council may appoint other permanent or ad hoc committees as it deems necessary. [Election Committee, for example]
5. Elections
Officers and Executive Committee members will be elected at the last meeting in a calendar year. Each member’s term will be for two years except in the initial election wherein three members shall serve for two years and two for one year so as to have staggered terms. Elections shall be by a vote of the majority of the quorum.
6. Meetings
Meetings, voting and other communications may be held via distance technologies to reduce cost and/or enhance attendance.
7. Amendments to the Bylaws
Amendments may be made by a 2/3 vote of the quorum at any regular or special meeting provided a 45 day notice has been provided to all members.