Source: https://www.revisor.mn.gov/statutes/2008/cite/403/full
Timestamp: 2019-10-15 22:19:05
Document Index: 717565480

Matched Legal Cases: ['art 3', 'art 2', 'art 10', 'art 6', 'art 10', 'art 6', 'art 10', 'art 6', 'art 2', 'art 4', 'art 1', 'art 2', 'art 3', 'art 2', 'art 1', 'art 2', 'art 10', 'art 6', 'art 8', 'art 10', 'art 2', 'art 10', 'art 1', 'art 2', 'art 6', 'art 1', 'art 2', 'art 5', 'art 6']

﻿ Ch. 403 MN Statutes
403.38 STATEWIDE INTEGRATION.
"Governmental agency" means any unit of local government or special purpose district located in whole or in part within this state that provides or has authority to provide fire-fighting, police, ambulance, medical, or other emergency services.
"Wireless telecommunications service provider" means a provider of commercial mobile radio services, as that term is defined in United States Code, title 47, section 332, subsection (d), including all broadband personal communications services, wireless radio telephone services, geographic area specialized and enhanced specialized mobile radio services, and incumbent wide area specialized mobile radio licensees, that offers real-time, two-way voice service interconnected with the public switched telephone network and that is doing business in the state of Minnesota.
1977 c 311 s 2; 1987 c 56 s 1,2; 1990 c 543 s 1; 1994 c 616 s 6; 1995 c 149 s 1; 1997 c 202 art 3 s 18,19; 3Sp1997 c 3 s 1; 2002 c 372 s 2-6; 1Sp2003 c 1 art 2 s 102; 2004 c 282 s 3-7; 2005 c 136 art 10 s 3-6; 2006 c 260 art 6 s 2
(c) The contract language or subsequent amendments to the contract must include a description of the services to be furnished to the county or other governmental agencies operating public safety answering points. The contract language or subsequent amendments must include the terms of compensation based on the effective tariff or price list filed with the Public Utilities Commission or the prices agreed to by the parties.
(d) The contract language or subsequent amendments to contracts between the parties must contain a provision for resolving disputes.
1977 c 311 s 1; 2002 c 372 s 1; 2004 c 282 s 2; 2005 c 136 art 10 s 7,8; 2006 c 260 art 6 s 3
Services available through a 911 system shall include police, firefighting, and emergency medical and ambulance services. Other emergency and civil defense services may be incorporated into the 911 system at the discretion of the public agency operating the public safety answering point.
1977 c 311 s 3
1977 c 311 s 5; 2002 c 372 s 7; 2005 c 136 art 10 s 9; 2006 c 260 art 6 s 4
Disputes between parties must be resolved pursuant to section 403.025, subdivision 7, paragraph (d).
1977 c 311 s 9; 1980 c 614 s 123; 1995 c 149 s 3; 2002 c 372 s 11; 1Sp2003 c 1 art 2 s 107
(c) The fee may not be less than eight cents nor more than 65 cents a month until June 30, 2008, not less than eight cents nor more than 75 cents a month until June 30, 2009, not less than eight cents nor more than 85 cents a month until June 30, 2010, and not less than eight cents nor more than 95 cents a month on or after July 1, 2010, for each customer access line or other basic access service, including trunk equivalents as designated by the Public Utilities Commission for access charge purposes and including wireless telecommunications services. With the approval of the commissioner of finance, the commissioner of public safety shall establish the amount of the fee within the limits specified and inform the companies and carriers of the amount to be collected. When the revenue bonds authorized under section 403.27, subdivision 1, have been fully paid or defeased, the commissioner shall reduce the fee to reflect that debt service on the bonds is no longer needed. The commissioner shall provide companies and carriers a minimum of 45 days' notice of each fee change. The fee must be the same for all customers.
(g) Competitive local exchanges carriers holding certificates of authority from the Public Utilities Commission are eligible to receive payment for recurring 911 services.
1977 c 311 s 11; 1978 c 680 s 1; 1980 c 614 s 123,147; 1Sp1985 c 13 s 330; 1987 c 404 s 174; 1989 c 335 art 4 s 85; 1990 c 543 s 4; 1994 c 616 s 7,8; 1994 c 634 art 1 s 22; 1995 c 265 art 2 s 29; 1997 c 202 art 3 s 21; 1Sp2001 c 10 art 2 s 78; 2002 c 372 s 13-19; 2002 c 401 art 1 s 3; 1Sp2003 c 1 art 2 s 108,135; 2005 c 136 art 10 s 12-14; 2006 c 260 art 6 s 6-10; 2007 c 54 art 8 s 3-5
(a) The commissioner of finance, if requested by a vote of at least two-thirds of all the members of the Statewide Radio Board, shall sell and issue state revenue bonds for the following purposes:
(a) The commissioner may sell and issue the bonds on the terms and conditions the commissioner determines to be in the best interests of the state. The bonds may be sold at public or private sale. The commissioner may enter any agreements or pledges the commissioner determines necessary or useful to sell the bonds that are not inconsistent with sections 403.21 to 403.40. Sections 16A.672 to 16A.675 apply to the bonds. The proceeds of the bonds issued under this section must be credited to a special 911 revenue bond proceeds account in the state treasury.
(b) Before the proceeds are received in the 911 revenue bond proceeds account, the commissioner of finance may transfer to the account from the 911 emergency telecommunications service account amounts not exceeding the expected proceeds from the next bond sale. The commissioner of finance shall return these amounts to the 911 emergency telecommunications service account by transferring proceeds when received. The amounts of these transfers are appropriated from the 911 emergency telecommunications service account and from the 911 revenue bond proceeds account.
2005 c 136 art 10 s 19
The amount necessary to pay debt service costs and reserves for bonds issued by the Metropolitan Council under section 403.27 or by the commissioner of finance under section 403.275 is appropriated from the 911 emergency telecommunications service account established under section 403.11 to the commissioner of finance. The commissioner of finance shall transmit the necessary amounts to the Metropolitan Council as requested by the council.
1Sp2003 c 1 art 2 s 117,135; 2005 c 136 art 10 s 20
Subdivision 1.County planning process.
(a) No later than two years from May 22, 1995, each metropolitan county shall undertake and complete a planning process for its public safety radio subsystem to ensure participation by representatives of local government units, quasi-public service organizations, and private entities eligible to use the regional public safety radio system and to ensure coordination and planning of the local subsystems. Local governments and other eligible users shall cooperate with the county in its preparation of the subsystem plan to ensure that local needs are met.
Subd. 2.Cities of first class; planning process.
Each city of the first class in the metropolitan counties shall have the option to participate in the county public safety radio subsystem planning process or develop its own plan.
Subd. 3.Submission of plans to board.
Each metropolitan county and each city of the first class in the metropolitan area which has chosen to develop its own plan shall submit the plan to the regional radio board for the metropolitan area for the board's review and approval.
Subd. 4.Local government joinder.
Local government units, except for cities of the first class, quasi-public service organizations, and private entities eligible to use the regional public safety radio system cannot join the system until its county plan has been approved by the regional radio board for the metropolitan area.
1995 c 195 art 1 s 14; 1Sp2003 c 1 art 2 s 135; 2006 c 260 art 6 s 17
(6) the commissioner of finance;
Subd. 1f.Advisory groups.
(a) The Statewide Radio Board shall establish one or more advisory groups for the purpose of advising on the plan, design, implementation, and administration of the statewide, shared trunked radio and communication system.
(b) At least one such group must consist of the following members:
(1) the chair of each regional radio board or, if no regional radio board has been formed, a representative of each region of development as defined in the statewide, shared, trunked radio and communication plan, once planning and development have been initiated for the region, or a designee;
(2) the chief of the Minnesota State Patrol or a designee;
(3) a representative of the Minnesota State Sheriffs' Association;
(4) a representative of the Minnesota Chiefs of Police Association;
(5) a representative of the Minnesota Fire Chiefs' Association; and
(6) a representative of the Emergency Medical Services Board.
(4) a policy for the lease of excess space or capacity on systems constructed under the project plan, consistent with section 174.70, subdivision 2, with priority given first to local units of government for public safety communication transmission needs and second to any other communications transmission needs of either the public or private sector.
2002 c 401 art 1 s 12; 1Sp2003 c 1 art 2 s 119,135; 2004 c 201 s 16; 2005 c 156 art 5 s 21,23; 2006 c 230 s 1; 2006 c 260 art 6 s 19,20
In addition to any other powers specifically provided by law, the Statewide Radio Board has the powers given in this section.
2004 c 201 s 17
Notwithstanding any provision to the contrary in sections 403.21 to 403.40, the Statewide Radio Board has the final authority over technical and operational standards necessary to provide for the development and implementation of a statewide backbone that maximizes the integration of the public safety radio communication system throughout the state, including the backbone previously established by the Metropolitan Radio Board. Technical and operational standards that do not interfere with the integration of the system may be established locally or regionally.
2004 c 201 s 18
The Statewide Radio Board may establish the following additional advisory committees with representatives from each region of implementation to advise on the following topical areas:
(3) an operations and technical committee to make recommendations on the plan and operational issues related to the technical aspects of the system backbone and interoperability infrastructure.
2004 c 201 s 20