it-sow 4-4-16 rfp_schedule... · web viewthe mdtmb project manager must approve any tools, in...

RFP # 007117B0010538

Schedule A - Statement of Work (SOW)

1.000 Project Identification

1.001 PROJECT REQUEST

The State of Michigan (State) invites qualified entities to submit a proposal for the design, installation, and operation of a statewide broadband wireless system to serve Michigan public safety entities. It is the intent of this request for proposal (RFP) to provide an alternative to the offer from the First Responder Network Authority (FirstNet). The Michigan Public Safety Broadband Network (MPSBN) shall be fully interoperable now and in the future with the FirstNet National Public Safety Broadband Network (NPSBN). Subject to the limitations contained in this RFP, the State will consider the responses to this RFP in weighing its options for a MPSBN.

This RFP contemplates a Public-Private-Partnership (PPP) with an entity (the Partner) that meets the qualifications of a wireless network operator with one or more national wireless networks for roaming service.

No funds have been appropriated by the Michigan Legislature to enter into an agreement with a supplier of goods and services described in this RFP. The MPSBN will need to be financially self-sustaining for the anticipated lifespan of the network. If the State moves forward with this project, the Partner will be required to develop a self-sustaining business model leveraging the licensed 20 MHz of Band 14 spectrum within Michigan to build, deploy, operate, and maintain the NPSBN to serve public safety and may elect to monetize the excess capacity to provide commercial service to end users.

This RFP follows an objectives-based approach, in contrast to a requirements-based RFP in which much detail is contained. Objectives are generally in parallel with those expressed in the FirstNet RFP1

1.002 BACKGROUND

1.002.1 The Middle Class Tax Relief and Job Creation Act of 2012

In February 2012, the Middle Class Tax Relief and Job Creation Act (Act) was signed into law. The Act, among other things, created FirstNet as an independent authority within the National Telecommunications and Information Administration (NTIA). FirstNet was given the license to 20 megahertz (MHz) of spectrum within the 700 MHz band and charged with constructing a NPSBN dedicated to the needs of public safety. The network is expected to be built across all 50 states, plus six territories, and is intended to provide ubiquitous interoperability between jurisdictions. Massive planning efforts for the network have been underway since the date of the Act, and are expected to continue through 2022, the date mandated by the Act for the network to be fully functional.

FirstNet issued a RFP on January 16, 2016, that is intended to result in the issuance of an Indefinite Delivery Indefinite Quantity (IDIQ) contract in the manner of a PPP to design, build, and operate the NPSBN. Proposals were due May 31, 2016, and that selection process is underway.

Under the Act, the Governor of each state and territory will receive a plan for deployment of the NPSBN in their jurisdictions. Governors will be provided a review period of 90 days during which a decision will be expected as to whether the state or territory will accept the offer or “opt-out.” A decision to opt-out places responsibility with a respective state for the design, implementation, and operation of a Radio Access Network (RAN)2 that is fully compatible with FirstNet and triggers a period of 180 days within which time the alternate state plan is required to be submitted to the Federal Communications Commission (FCC).

1 The link to the FirstNet RFP can be found at: https://www.fbo.gov/index?s=opportunity&mode=form&tab=core&id=33106ecc75222458a6e4405b0f66bd2e&_cview=0

2 A RAN is the portion of the NPSBN that a State may choose to provide. A RAN consists of radio base stations (EnodeB), antenna systems, and a network that connects individual cell sites to the larger network (backhaul), and network interfaces required for the State and NPSBN.

https://www.fbo.gov/index?s=opportunity&mode=form&tab=core&id=33106ecc75222458a6e4405b0f66bd2e&_cview=0


1.002.2 State Options

The State has not made a decision to accept the proposal made by FirstNet for a NPSBN to serve public safety entities in Michigan. Neither has the State chosen to opt-out of the FirstNet offered RAN to serve its public safety entities. It is the intent of this RFP to explore options available to the State that will that will be most responsive to the needs of public safety entities and which will be sustainable over the coming 25-year period.

If the State elects to move forward with this project, it will be on the basis of an opt-out decision made by Michigan’s Governor. If the Governor decides to opt out, then he/she is required to notify FirstNet, NTIA, and the FCC. After providing the notification, the Governor has 180 days to develop and complete plans for the construction, maintenance and operation of the RAN within the State. The State is required to submit their Alternate RAN to the FCC that is interoperable with the NPSBN and complies with the minimum technical interoperability requirements under the Act3. If the FCC does not approve the State’s Alternate RAN, a contract may not be awarded as a result of this RFP.

Following FCC approval, the State is required to submit their Alternate RAN to the NTIA to demonstrate it can provide comparable security, coverage, quality of service, and cost effectiveness to that of the NPSBN4. If the NTIA does not approve the State’s Alternate RAN, a contract may not be awarded as a result of this RFP.

The Spectrum Management Lease Agreement (SMLA) is approved by the FirstNet Board. The FirstNet Board was established as part of the Middle Class Tax Relief and Job Creation Act of 2012. The FirstNet Board will have to approve a SMLA for the State and its partner in order for the State to enter into a contract to be awarded. If FirstNet does not approve a SMLA for the state, a contract may not be awarded as a result of this RFP.

No funds for this project have been appropriated for this project by the Michigan Legislature.

Proposers are advised that a contract will not be entered into by the State unless 1) the State opts-out of the FirstNet offer; 2) a plan for design, deployment, and operation of a State RAN is approved by the FCC; 3) the State can demonstrate to the NTIA it can provide comparable security, coverage, quality of service, and cost effectiveness to that of the NPSBN; 4) the SMLA is approved by the FirstNet Board; and 5) the Michigan Legislature appropriates sufficient funding for State expenditures related to the MPSBN.

The State may terminate this RFP for any or no reason.

1.002.3 Public Private Partnership (PPP)

If the State chooses to opt-out, it will need a partner with wireless network experience at the national level, financial stability, consumer sales channels, and access to a legacy network(s) that provides both LTE coverage and capacity in Michigan as well as the rest of the United States for roaming purposes. The Partner will provide network design, deployment, operations, maintenance, and customer support for public safety entities in Michigan. It is the intent of the State to receive and evaluate proposals from potential Partners to provide the services required to permit the State to consider an opt-out from the NPSBN for the purposes of operating a RAN that fully meets the needs of its public safety entities.

This RFP anticipates a PPP with a wireless network operator with one or more national wireless networks for roaming service. A consortium or team that provides the equivalent services will be considered for qualification.

1.002.4 Spectrum Manager Lease Agreement (SMLA)

If the State chooses to opt-out and construct a RAN, it is expected that the MSPBN will operate under a SMLA for access to Band 14 of the 700 MHz spectrum licensed to FirstNet. It is anticipated this spectrum lease will provide for the monetization of the excess capacity of the 20 MHz of Band 14 spectrum within Michigan by the Partner for the purposes of providing commercial service to end users. 3 Information found at: http://www.firstnet.gov/consultation/state-decision#State Decision on FirstNet’s RAN Plans4 Information found at: http://www.firstnet.gov/consultation/state-decision#State Decision on FirstNet’s RAN Plans

2Version (4/2016)

The terms and conditions of such a spectrum lease are unknown at this time and may produce constraints in the deployment of a RAN for Michigan public safety entities. Examples of two SMLA approved by the FirstNet Board for the states of Texas5 and New Jersey6 can be found online.

1.002.5 Public Safety Entities Defined in the Act

Public safety entities are generally understood to be the providers of protection of life and property in the United States. This term is important, as it defines what entities are authorized to operate on the NPSBN. A definition of “public safety entity” is contained in Public Law 112-96, “the Act” that created FirstNet, and refers to two other Federal laws.

The term ‘‘public safety entity’’ means an entity that provides public safety services. The term ‘‘public safety services’’ (A) has the meaning given the term in section 337(f) of the Communications Act of 1934 (47 U.S.C. 337(f)); and (B) includes services provided by emergency response providers, as that term is defined in section 2 of the Homeland Security Act of 2002 (6 U.S.C. 101).

The Communications Act of 1934, as amended, Title 47 U.S.C. 337 (f) of the United States Code defines “public safety services” as:

(A) the sole or principal purpose of which is to protect the safety of life, health, or property;(B) that are provided (i) by State or local government entities; or (ii) by nongovernmental

organizations that are authorized by a governmental entity whose primary mission is the provision of such services; and

(C) that are not made commercially available to the public by the provider.

The Homeland Security Act of 2002 (6 U.S.C. 101) 6) states the term ‘‘emergency response providers’’ includes Federal, State, and local governmental and nongovernmental emergency public safety, fire, law enforcement, emergency response, emergency medical (including hospital emergency facilities), and related personnel, agencies, and authorities.

The Act requires equipment used on the NPSBN to be “…(ii) capable of being used by any public safety entity and by multiple vendors across all public safety broadband networks operating in the 700 MHz band.”

1.002.6 Michigan Interpretation of Public Safety Entities

Michigan has conducted a survey of the public safety entities that serve the State, including tribal nations. In interpreting the term “public safety entities,” the State has reviewed Michigan statutes and some federal agency definitions of public safety entities and public safety personnel.

Law enforcement agencies are defined by the U.S. Department of Justice, Bureau of Justice Statistics.

The generic name for the activities of the agencies responsible for maintaining public order and enforcing the law, particularly the activities of prevention, detection, and investigation of crime and the apprehension of criminals.7

Law enforcement agencies in Michigan employ police officers who are engaged in the enforcement of laws, ordinances and regulations.

Police officers or law enforcement officers are defined by Act 203 of 1965, Commission on Law Enforcement Officers Standards Act. 1965 PA 203 § 28.602 defines “police officer” or “law enforcement officer” as follows:

"Police officer" or "law enforcement officer" means, unless the context requires otherwise, any of the following:

5 Texas SMLA: https://wireless2.fcc.gov/UlsEntry/attachments/attachmentViewRD.jsp;ATTACHMENTS=ZZ5pXLgDMcwXZhznmh3jv0fRfzvdPsDGpGTlbJhlr2nrvpPN11Dn! - 1991798947!127806463? applType=search&fileKey=1531681465&attachmentKey=19453708&attachmentInd=licAttach6 New Jersey SMLA: http://www.ntia.doc.gov/files/ntia/publications/firstnet_resolution_50_re_smla_with_new_jersey.pdf7 http://www.bjs.gov/index.cfm?ty=tp&tid=7

3Version (4/2016)

(i) A regularly employed member of a law enforcement agency authorized and established by law, including common law, who is responsible for the prevention and detection of crime and the enforcement of the general criminal laws of this state. Police officer or law enforcement officer does not include a person serving solely because he or she occupies any other office or position.

(ii) A law enforcement officer of a Michigan Indian tribal police force, subject to the limitations set forth in section 9(7).

(iii) The sergeant at arms or any assistant sergeant at arms of either house of the legislature who is commissioned as a police officer by that respective house of the legislature as provided by the legislative sergeant at arms police powers act, 2001 PA 185, MCL 4.381 to 4.382.

(iv) A law enforcement officer of a multicounty metropolitan district, subject to the limitations of section 9(8).

(v) A county prosecuting attorney's investigator sworn and fully empowered by the sheriff of that county.

(vi) A fire arson investigator from a fire department within a village, city, township, or county who is sworn and fully empowered by the chief of police of that village, city, township, or county.

(m) "Rule" means a rule promulgated under the administrative procedures act of 1969, 1969 PA 306, MCL 24.201 to 24.328.8

Firefighters are defined by Act 291 of 1966, Firefighters Training Council Act. 1966 PA 291 § 29.362 defines “firefighter” as follows:

"Firefighter" means a member, including volunteer members and members paid on call, of an organized fire department who is responsible for, or is in a capacity that includes responsibility for, the extinguishment of fires, the directing of the extinguishment of fires, the prevention and detection of fires, and the enforcement of the general fire laws of this state. Firefighter does not include a person whose job description, duties, or responsibilities do not include direct involvement in fire suppression.9

EMS agencies and emergency medical technicians (EMTs) are defined by Act 368 of 1978, Public Health Code.10

“Emergency medical services” means the emergency medical services personnel, ambulances, non-transport prehospital life support vehicles, aircraft transport vehicles, medical first response vehicles, and equipment required for transport or treatment of an individual requiring medical first response life support, basic life support, limited advanced life support, or advanced life support.

“Emergency medical services personnel” means a medical first responder, emergency medical technician, emergency medical technician specialist, paramedic, or emergency medical services instructor-coordinator.

“Emergency medical services system” means a comprehensive and integrated arrangement of the personnel, facilities, equipment, services, communications, medical control, and organizations necessary to provide emergency medical services and trauma care within a particular geographic region.

“Emergency medical technician” means an individual who is licensed by the department to provide basic life support.

8 http://www.legislature.mi.gov/(S(cukb4dllq1tb1spmpafrtdz0))/mileg.aspx?page=getObject&objectName=mcl-28-6029 http://www.legislature.mi.gov/(S(nl55wo54iwgyeluxehhmtexk))/mileg.aspx?page=getObject&objectName=mcl-29-36210 http://www.legislature.mi.gov/(S(apyqcb13trr0pep212uzwliu))/mileg.aspx?page=GetObject&objectname=mcl-368-1978-17-209

4Version (4/2016)

http://www.legislature.mi.gov/(S(apyqcb13trr0pep212uzwliu))/mileg.aspx?page=GetObject&objectname=mcl-368-1978-17-209

http://www.legislature.mi.gov/(S(apyqcb13trr0pep212uzwliu))/mileg.aspx?page=GetObject&objectname=mcl-368-1978-17-209

“Emergency medical technician specialist” means an individual who is licensed by the department to provide limited advanced life support.

Emergency management personnel/emergency management in Michigan is coordinated by the Michigan State Police under the authority of Act 390 of 1976. 1976 PA 390 § 30.402 defines “emergency management coordinator” as follows:

“Emergency management coordinator” means a person appointed pursuant to section 9 to coordinate emergency management within the county or municipality. Emergency management coordinator includes a civil defense director, civil defense coordinator, emergency services coordinator, emergency program manager, or other person with a similar title and duties.11

Public safety entities include those entities with responsibilities defined in the disaster and emergency operations plans of the State; examples include the following:

Michigan Department of Transportation – clearing snow, landslides, bridge issues, travelers’ information and warnings

Michigan Department of Health and Human Services Not-for-profit and faith-based disaster relief agencies, e.g., American Red Cross, Salvation Army Transit authorities and agencies – evacuation of the public from hazards School transportation – coordination of evacuations Schools – security monitoring, emergency response, shelter operations Utilities – gas, water, electric for emergency response, mitigation and restoration Special authorities and districts – dams and flood control Parks – security, coordination of emergency response

The list above is not all inclusive. Indeed, public safety entities from other states and federal agencies exist that have cross-border response duties within Michigan.

The State intends to determine eligible public safety users by creating and maintaining a system that will review and approve applications for access to the MPSBN. Generally, the State will encourage participation on the MPSBN by bona fide public safety entities in order to increase interoperability and to provide access to public safety information sources and applications.

1.002.7 Michigan Data Collection and Analysis

The State compiled a comprehensive Data Collection and Analysis Report in September 2015 that contained a representative sampling from across the Michigan public safety community. The information provided in the document was collected through multiple methods such surveys, face-to-face meetings, and personal contact with Michigan’s public safety stakeholder community.

This RFP contains a summary of the data collected from stakeholders, and presents the FirstNet baseline coverage objectives and a comparison of FirstNet regulations. The State has identified requirements beyond those areas covered under the FirstNet baseline, such as rural coverage in Michigan’s Upper Peninsula and northern Lower Peninsula, inland waterways, and Great Lakes shorelines. The data serves to identify and focus on the requirements Michigan has formulated for the MPSBN and provides baseline information about its public safety entities, calls for service, and other details that may be useful in the design of a RAN.

A summary of this information is contained in Schedule A, Attachment 1 - Michigan Data Collection and Analysis. Proposers are encouraged to provide solutions that meet the needs of the State to a greater degree than the FirstNet baseline coverage. Creative solutions by proposers are sought and encouraged.

Certain critical infrastructure information may be provided during this procurement to qualified proposers that is sensitive and confidential. This information may concern existing telecommunications infrastructure and

11 http://www.legislature.mi.gov/(S(nmdrbwtsrv3rk0o4apeyg2yx))/mileg.aspx?page=getObject&objectName=mcl-30-402

5Version (4/2016)

software applications in use by the public safety entities in Michigan. At such time this information is provided to qualified proposers it will be protected by a non-disclosure agreement (NDA) between parties.

1.100 Scope of Work and Deliverables

1.101 IN SCOPE

This RFP contemplates a PPP with a Partner that will provide network design, deployment, operations, maintenance, and customer support for public safety entities in Michigan.

Proposers are encouraged to provide solutions that meet the needs of the State to a greater degree than the FirstNet baseline coverage12. Creative solutions by proposers are sought and encouraged.

In its RFP, FirstNet seeks,

…a comprehensive network solution covering each of the 56 states and territories. The comprehensive network solution shall provide FirstNet services that include: the deployment and provisioning of a nationwide Core Network (“Core”), and Radio Access Network (RAN) services; backhaul, aggregation, and the use of national transport networks and operation centers; a device ecosystem; use of network infrastructure; deployable capabilities; use of operational and business support systems; an applications ecosystem; network services; and the integration, maintenance, operational services, and ongoing evolution of these systems required to function fully as an operational wireless 3rd Generation Partnership Project (3GPP) standards-based Long Term Evolution (LTE) NPSBN.

Michigan is seeking alternatives to the FirstNet Plan that will be submitted to each state and territory for the purpose of evaluating options and to select the best path forward to make available to public safety entities a wireless broadband network that satisfies operational needs for at least the next 25 years.

A more detailed description of the services (work) and deliverables sought for this project is provided in Article 1, Section 1.104, Work and Deliverables.

1.102

OUT OF SCOPEMPSCS Radio Tower Infrastructure.

1.103 ENVIRONMENTThe links below provide information on the State’s Enterprise information technology (IT) policies, standards and procedures which includes security policy and procedures, eMichigan web development, and the State Unified Information Technology Environment (SUITE).

Contractors are advised that the State has methods, policies, standards and procedures that have been developed over the years. Contractors are expected to provide proposals that conform to State IT policies and standards. All services and products provided as a result of this RFP must comply with all applicable State IT policies and standards. Contractor is required to review all applicable links provided below and state compliance in their response.

Enterprise IT Policies, Standards and Procedures:http://michigan.gov/dtmb/0,4568,7-150-56355_56579_56755---,00.html

All software and hardware items provided by the Contractor must run on and be compatible with the MDTMB Standard Information Technology Environment. Additionally, the State must be able to maintain software and other items produced as the result of the Contract. Therefore, non-standard development tools may not be used unless approved by MDTMB. The Contractor must request, in writing, approval to use non-standard software 12 Refer to Schedule A, Attachment 1 - Michigan Data Collection and Analysis for a summary of State findings.

6Version (4/2016)

http://michigan.gov/dtmb/0,4568,7-150-56355_56579_56755---,00.html

development tools, providing justification for the requested change and all costs associated with any change. The MDTMB Project Manager must approve any tools, in writing, before use on any information technology project.

It is recognized that technology changes rapidly. The Contractor may request, in writing, a change in the standard environment, providing justification for the requested change and all costs associated with any change. The State’s Project Manager must approve any changes, in writing, and MDTMB, before work may proceed based on the changed environment.

Enterprise IT Security Policy and Procedures:http://www.michigan.gov/documents/dmb/1210.32.pdfhttp://www.michigan.gov/documents/dmb/1325_193160_7.pdfhttp://www.michigan.gov/documents/dmb/1335_193161_7.pdfhttp://www.michigan.gov/documents/dmb/1340_193162_7.pdf

The State’s security environment includes: MDTMB Single SignOn service (“MiLogin”) MDTMB provided SQL security database. Secured Sockets Layer/Transport Layer Security (“SSL/TLS” cryptographic protocols). SecureID (State Security Standard multi-factor authentication service for external network access and

high risk Web systems)

Look and Feel Standard

ADA ComplianceThe State is required to comply with the Americans with Disabilities Act of 1990 (ADA), and has adopted a formal policy regarding accessibility requirements for websites and software applications. The State is requiring that Contractor’s solution conform, where relevant, to level AA of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) 2.0. Contractor may provide a description of conformance with the above mentioned specifications by means of a completed Voluntary Product Accessibility Template for WCAG 2.0 (WCAG 2.0 VPAT and GPAT) or other comparable document. Contractor may consider, where relevant, the W3C’s Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) for non-web software and content. Any additional compliance requirements shall be specified in the Statement of Work.

The State Unified Information Technology Environment (SUITE):Includes standards for project management, systems engineering, and associated forms and templates – must be followed: http://www.michigan.gov/suite

Agency Specific Technical EnvironmentEntities responsible for the administration, maintenance, and support as it relates to the services requested in this RFP.

Capacity Projections – CSS Current Workload Profile – CSS Disaster Recovery Requirements and Priorities – Infrastructure Reporting tools – CSSInterfaces –CSS Current enhancements under way – CSS Classes of users – CSS Other systems/applications requiring integration – Infrastructure

Bidders: Describe in detail, your proposed solution to meet this service, including State roles and Contractor roles

7Version (4/2016)

http://www.michigan.gov/suite

http://www.michigan.gov/documents/dmb/1340_193162_7.pdf



http://www.michigan.gov/documents/dmb/1210.32_Information_Processing_Report_390411_7.pdf?20150721085447

1.104 WORK AND DELIVERABLES

I. Services and Deliverables To Be Provided

For the purpose of preparing proposals, Vendors should propose a phased deployment schedule that will begin immediately following FCC and NTIA acceptance of the system proposal13. The phased deployment will follow the Initial Operational Capability (IOC) milestones and Final Operational Capability (FOC) milestones identified in the FirstNet RFP Section J, Attachment J-8. Temporary coverage provided by deployable radio base station systems may be used to complement persistent coverage, but does not count in satisfaction of IOC/FOC coverage deployment percentage goals. These deliverables are not all inclusive. Contractors may propose other deliverables.

A. Business Requirements

Michigan is seeking alternatives to the FirstNet Plan for the purpose of evaluating options and to select the best path forward to make available to public safety entities a wireless broadband network that satisfies operational needs for at least the next 25 years.

Objectives established for the MPSBN parallel those established by FirstNet14 for the NPSBN. The State shares these objectives in order to develop a RAN that will be fully compliant with the objectives of FirstNet and which will provide seamless interoperability now and in the future with the NPSBN. The Partner will be responsible for meeting these objectives as tailored for Michigan.

In responding to the Michigan RFP, proposers should address the following deliverables as adapted to an opt-out decision.

Deliverable(s)

Building, Deployment, Operation, and Maintenance of the NPSBN

In its RFP, FirstNet seeks to,

…Provide nationwide interoperable public safety broadband network service that ensures network coverage 24 hours a day, 7 days a week, 365 days a year and complies with the technical requirements…throughout the RFP and its attachments.

Alignment with this objective provides for RAN deployment within Michigan for interoperable PSBN service that ensures network coverage 24 hours a day, 7 days a week, 365 days a year and complies with the technical requirements of the FirstNet NPSBN, including future upgrades to the nationwide network as 3GPP standards revisions are adopted by FirstNet.

The minimum technical requirements for the MPSBN are as established in Recommended Minimum Technical Requirements to Ensure Nationwide Interoperability for the Nationwide Public Safety Broadband Network 15 , and in the FirstNet RFP, Section J, Attachment J-4.

It is contemplated that the Partner will manage the design, construction, deployment, and optimization of the RAN with inspection and approval by the State. Operation of the MPSBN will be required, including provision of functions such as customer service, sales and service of user equipment, network monitoring, routine and emergency maintenance, and operation and maintenance of the backhaul facilities. The Partner will work with the State regarding validation of public safety entities and personnel for access to the MPSBN.

13 1.002.2 State Options14 The link to the FirstNet RFP solicitation and referenced documents can be found at: https://www.fbo.gov/index?s=opportunity&mode=form&tab=core&id=33106ecc75222458a6e4405b0f66bd2e&_cview=015 https://www.fbo.gov/utils/view?id=6e04ef9287e37ebaa1d95a56c9452da0

8Version (4/2016)

https://www.fbo.gov/utils/view?id=6e04ef9287e37ebaa1d95a56c9452da0







Hardening of the network to public safety-grade is a primary requirement of the State. Public safety-grade is defined as the recommendations of the National Public Safety Telecommunications Council (NPSTC) in its report Defining Public Safety Grade Systems and Facilities16, dated 5/22/2014. To the greatest extent possible, the recommendations of the NPSTC report shall be applied to the MPSBN.

Michigan requests that proposers describe the design and operation of the RAN based upon the needs of the state’s public safety entities. Proposers shall provide a technical description of the solution, including but not limited to equipment, software, design, and services to be provided; system design information, including a complete detailed description, block diagrams and network designs necessary to provide a complete and comprehensive description. Proposers should describe warranties that will be applicable to the RAN, site improvements, backhaul network, or other equipment or software that will be the basis of the MPSBN.


Financial Sustainability


….Maximize the impact of government funding and leverage all 20 MHz of Band 14 to build, deploy, operate, and maintain the NPSBN to serve public safety and for secondary use while ensuring a self-sustaining business model...

No funds have been appropriated by the Michigan Legislature to enter into an agreement with a supplier of goods and services described in this RFP. The MPSBN will need to be financially self-sustaining for the anticipated lifespan of the network. Proposers shall provide a financial model outlining the 25-year partnership with the State that demonstrates the sustainability of the MPSBN and explains how their offer will provide the coverage, capacity, network connectivity, QoS, and other objectives within the scope of services described in this RFP while remaining self-sufficient through the monetization of excess Band 14 capacity within Michigan and other revenue sources.

Proposers shall provide a financial model that anticipates a basis for the financial plan to be submitted by Proposers should be the monetization of the use of the excess capacity on the leased Band 14 spectrum within the state of Michigan, within the constraints of the spectrum manager lease agreement.

Proposers should address the integration of the Band 14 infrastructure into a legacy LTE network(s) in order to provide service in the First Operational Configuration and subsequent configurations in a manner that both provides roaming services as well as providing an opportunity to optimize revenue, while preserving the integrity of the MPSBN.

Proposers shall provide a fixed cost for the construction of the RAN and backhaul network for the coverage area defined by the State. This coverage area is considered to be the baseline coverage area, and it is understood that further investment in the network may be needed to meet the needs of Michigan public safety entities during the contemplated lifetime of the network.

Coverage solutions such as small cells or coverage through 5G devices (at such time they are available and compatible with the NPSBN) should be described and quoted.

Proposers shall offer a method by which the network may be expanded in the future and/or which technology refreshment will be made to maintain compatibility with FirstNet. This method may include expansion of the Band 14 network in a manner that increases fees from monetization of excess network capacity and/or further investment by the State, local governments, or other entities to meet particular operating requirements.

16 http://www.npstc.org/download.jsp?tableId=37&column=217&id=3066&file=Public_Safety_Grade_Report_140522 .pdf

9Version (4/2016)

http://www.npstc.org/download.jsp?tableId=37&column=217&id=3066&file=Public_Safety_Grade_Report_140522.pdf

http://www.npstc.org/download.jsp?tableId=37&column=217&id=3066&file=Public_Safety_Grade_Report_140522

http://www.npstc.org/download.jsp?tableId=37&column=217&id=3066&file=Public_Safety_Grade_Report_140522

Proposers shall address in the financial plan the allocation of funds for operations and maintenance of the RAN and backhaul network, and the potential use of the backhaul network for transport of an ESInet for NG9-1-1.

Proposers shall address in the financial plan the allocation to the State of some portion of the user fees paid by public safety entities for work and services provided by the State in support of the MPSBN (i.e. user profile assignments, validation of public safety entities and personnel for access to the MPSBN), within the constraints of the spectrum manager lease agreement.

The State intends that the monthly user fees for access to the MPSBN will be maintained at the lowest practical level. Surveys of public safety entities within the state indicated price sensitivity, and fees are a potential hurdle to achieving maximum use of the network. FirstNet restricts states’ application of user fees in an opt-out scenario to maintenance of the RAN. Proposers shall address the issue of user fees, including the cost and variety of user subscription fee pricing, in their financial models as a component of determining the sustainability of the MPSBN.

Some payments to FirstNet will be required to be made under the spectrum manager lease agreement and support of the FirstNet core infrastructure. The terms and conditions of the lease agreement are presently unknown, as is the calculation of the payments for access to and support of the FirstNet core infrastructure. Proposers should identify the method by which such payments would be calculated and paid.

Proposers shall identify and demonstrate the financial capability of providing the operating capital that will be needed to bridge the gaps between payment milestones and other investment to the PPP. A description shall be provided of the source of funds that will be used for the initial network rollout, and for working capital purposes as the network is deployed and before break-even operations are achieved, as well as any additional capital contributions that may be required to be made by the Partner to facilitate construction and operation of the MPSBN.

Proposers shall demonstrate financial stability, and that of its key suppliers/operating team, through the provision of audited financial statements for the last three fiscal years. If the firm has a bond rating, the source and documentation of that rating shall be supplied.

If a proposer relies on an outside lender or equity partner for funds, that source shall be identified and financial data shall be provided that demonstrates the capability to fund the MPSBN.

Bidders: Describe in detail, your proposed solution to meet the requirements of this section, including State roles and Contractor roles

First Responder User Adoption


…Establish (i) compelling, differentiated, and competitively priced service packages and (ii) sales, distribution, and marketing capabilities to ensure adoption of FirstNet products and services by a majority of eligible PSEs17 within four years of award…NPSBN services, at a minimum, shall include data, voice services, messaging, machine-to- machine, virtual private network (VPN), video, unique public safety mission-critical services, and location services.

Michigan has provided information gathered from existing users of broadband services in this RFP18. Also included is a gross number of public safety personnel. Other potential users of the network, including agencies that are providers of certain public safety services under emergency conditions are not contained in these estimates.

17 Public safety entities18 Schedule A, Attachment 1 - Michigan Data Collection and Analysis

10Version (4/2016)


Device Ecosystem


…Provide and maintain a 3GPP-compliant, Band-14-capable device portfolio that evolves with the 3GPP standards and provides functionality and price points that meet the needs of the FirstNet public safety customer base and drive substantial subscribership. FirstNet anticipates NPSBN public safety customers will expect mass market as well as ruggedized devices that are capable of gloved, one-handed, or hands-free operation as well as those capable of multimedia and high-definition data transmission both from humans and machine-based sensors. The ecosystem shall support Bring Your Own Device (BYOD) as well as, at a minimum, devices that:

• Operate seamlessly on the NPSBN and roam onto networks, including non-Band 14 commercially available networks

• Interoperate with FirstNet’s applications ecosystem• Support associated Universal Integrated Circuit Card (UICC) features and options, including

the ability to home and, if applicable, roam on to multiple networks while prioritizing them appropriately

• Support software containers to isolate FirstNet applications• Operate seamlessly with a comprehensive device management system to allow remote

provisioning and control

The selected contractor shall be required to establish a device ecosystem to provide a variety of compatible devices to public safety entity users of the NPSBN including support of “bring your own device” (BYOD). As the MPSBN evolves, the network shall maintain backwards compatibility with user devices.

Proposers shall identify the types of user equipment that will be compatible with the MPSBN and which will provide full interoperability with the NPSBN. Proposers shall identify the manufacturers or distributors of user equipment that will be offered to the State. Evidence of an agreement between the proposer and the manufacturer or distributor shall be provided to the State in the qualifications package.


Proposers shall describe the availability of devices through the Partner organization, as well as the types of purchase or lease options that may be available.


Proposers responding to this RFP shall explain how they would access this ecosystem, or how a separate ecosystem tailored to the needs of Michigan would be established.

11Version (4/2016)


Applications Ecosystem


…Provide an applications ecosystem that supports the NPSBN with capabilities and services relevant to public safety. The ecosystem shall include, at a minimum:

• An evolving portfolio of mobile and enterprise applications, as well as cloud services• An applications development platform• A vibrant third-party applications developer community• An applications store• Local control of users, subscriptions, services, and applications• User friendly federation of identity management• Data, application, and resource sharing across diverse PSEs• Core service and application delivery platforms• Data and applications security and privacy compliance across local, tribal, state, regional,

and federal users…

At the Federal level, the FirstNet RFP required the selected contractor to establish an Applications Ecosystem to provide public safety entities a source of applications compatible with the NPSBN. It is understood by Michigan that many applications used by public safety entities are customized to the needs of specific operating parameters that are unique from location to location.

If the State elects to opt-out of the federal program, the MPSBN is intended to provide services to public safety entities that will improve first responder safety and increase efficiency in the provision of those services. Proposers shall identify any partners on its team that will be providers of software applications and the experience and qualifications of those firms. Any system integrators or other parties that will be involved in the deployment of applications shall be identified.


In response to the Michigan RFP, proposers shall provide information on how they would access the FirstNet applications ecosystem, or how such products, either custom or off-the-shelf would be provided.


Accelerated Speed to Market


…Achieve operational capabilities in accordance with the schedule and feature sets denoted in RFP Section J, Attachment J-819, FirstNet Section J, IOC/FOC Target Timeline, which may include an initial

19 https://www.fbo.gov/utils/view?id=bc4a63534ebd1fd64cd01ff070f2560312

Version (4/2016)

https://www.fbo.gov/utils/view?id=bc4a63534ebd1fd64cd01ff070f25603

provision for operating the NPSBN using existing wireless services (similar to that of a mobile virtual network operator [MVNO]), Band 14 capabilities, significant subscribership to the NPSBN, and substantial rural coverage milestones in accordance with the IOC/FOC milestones.

In its RFP Section J, Attachment J-820, FirstNet established an Initial Operational Capability (IOC) timeline that is correlated with the 3rd Generation Partnership Project (3GPP) standard body release timeline; the milestones of the corresponding NPSBN deployment referenced in the RFP. Persistent coverage that satisfies the coverage requirements of the RFP are used in establishing IOC milestones and Final Operational Capability (FOC) milestones. Temporary coverage provided by deployable radio base station systems may be used to complement persistent coverage, but does not count in satisfaction of IOC/FOC coverage deployment percentage goals.

For the purposes of this RFP, it is the intent of the State to comply with the IOC/FOC goals of FirstNet to the extent practical (subject to a decision to opt-out, and approval of the Michigan plan by the FCC, events which may create a delay when compared to the FirstNet projected dates of completion of milestones).

FirstNet in its RFP J-8, Table 1 sets milestones for IOC-1 that will be completed six months after award to a contractor. The coverage and capacity solution is nationwide coverage on Band 14 or non-Band 14 spectrum. Achievement of this milestone is largely dependent on the availability of devices, applications, and services that will be compatible with an existing commercial wireless network that provides LTE service.

Michigan intends to meet the goal of IOC-1 in a similar manner, provided that the network offered by the Partner will operate using a compatible LTE network configuration at 3GPP Release 12. Compatible, as used in this paragraph means compatible with the 3GPP LTE release that will be used on the initial deployment of FirstNet and the MPSBN.

Michigan speculates that the deployment of the MPSBN will be phased over a period of five years from contract award, in close approximation to the IOC/FOC timeline specified by FirstNet. Deployment of the network will be governed by coverage priorities, public safety entity demand, and strategic objectives of the State based on hazards, emergency response plans and protocols, and other factors.

Proposers shall describe how they intend to meet these requirements.


The State assumes that in the initial configuration of the RAN the Partner will provide roaming service on a compatible LTE network that will provide coverage and capacity on an interim basis until the MPSBN is deployed to an extent to provide reliable service in defined areas of Michigan. It is a critical requirement that the Partner will be ready within the first six months after award of contract to provide roaming coverage on a network that it controls or on which it is authorized to act as an agent.

Proposers shall identify the existing LTE network(s) proposed for the initial operational configuration, and ongoing roaming service for the proposed MPSBN. If roaming will require reverse compatibility with a 3G technology, the standard and version of that technology shall be specified.


User Service Availability

20 https://www.fbo.gov/utils/view?id=bc4a63534ebd1fd64cd01ff070f2560313

Version (4/2016)

https://www.fbo.gov/utils/view?id=bc4a63534ebd1fd64cd01ff070f25603


…Provide a broadband service with availability of 99.99% as measured in a rolling 12 - month window within each reporting area. Offerors should consider areas that contain mission-critical infrastructure as needing enhanced hardening and increased availability. Service restoration activities shall be undertaken with the highest available priority but shall not exceed two hours for any impaired service. For restoration of service via temporary or secondary service capabilities, the temporary or secondary service must be transparent to the users and provide similar capability.

Michigan will comply with the user service availability objective of 99.99 percent on a rolling 12-month window. Proposers shall describe the services that will provide for 24-hours a day, 7-days a week priority response to network outages or service-interrupting events with a response time goal of two hours or less in urban areas and four hours or less in rural areas.

If the potential Partner is teamed with rural telecommunications providers in the state, a description shall be provided in the proposal of the operating procedures that will be implemented to create a single point of contact and response for network management.

Network monitoring of the RAN shall be provided to the State at MPSCS Network Communication Center (NCC) in Dimondale, MI . The State assumes that primary NOC service will be provided by the Partner. Proposers shall describe the NOC and associated systems that will provide network monitoring and alarms, service dispatch and notification to the State of outages, trouble ticket management, and generation of management reports related to network performance, availability, and related metrics. Proposers shall identify the provider and location of the NOC. Qualifications and experience of any third-party firm that will be involved in staffing, operating, maintaining, and backing up the NOC shall be identified.

Proposers shall identify the maintenance provider of the RAN, standby power supplies, backhaul network, and other components of the MPSBN. If this service is provided by employees of the proposer, the responsible person (title) shall be provided and identified on the organizational chart submitted in the proposal. If maintenance support is provided by a third-party, that firm shall be identified. Experience and qualifications of the firm, including references, shall be provided to the State.

Proposers shall describe the preventative maintenance schedule for the network, and a description of the services that will be provided to meet the operational availability objective of this project.


Service Capacity


…Provide service capacity to support geographically dispersed public safety usage (in accordance with FCC TAB RMTR 4.4.6.5, Capacity) throughout the life of the contract.

…Coverage and Capacity Definitions, includes a map noting first responder density and current mobile data usage. This will serve as a baseline for public safety data demand, and mobile data demand is expected to increase throughout the life of the contract.

Michigan will comply with the service capacity as referenced in the FirstNet RFP Section J-3 Interoperability for the Nationwide Public Safety Broadband Network.21

21 https://www.fbo.gov/utils/view?id=6e04ef9287e37ebaa1d95a56c9452da014

Version (4/2016)




Network capacity should be predicated on the number of potential users throughout the state in the public safety community. Guidance for capacity planning has been provided in various maps and charts concerning current mobile data usage and desired usage in Schedule A, Attachment 1 - Michigan Data Collection and Analysis of this RFP. Workshop information from the Department of Homeland Security (DHS), Office of Emergency Communications (OEC) will be furnished after NDA execution.

A fair estimate of potential public safety network users in Michigan is approximately 120,000; this takes into account not only primary first responder disciplines, but also those persons/entities with ancillary public safety duties such as transportation entities, public utilities, etc. Additionally, assuming the network allows users to “bring their own device” for use on the network, 1.5 devices per person is reasonable according to current industry information.

Proposers shall describe how the MPSBN will provide the capacity needed to accommodate the mix of traffic described in the user survey results.


Cybersecurity


…Provide cybersecurity solutions using the extensive set of industry standards and best practices contained in the International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) security guidance for networks (ISO/IEC 27033, ISO/IEC 17099, and ISO/IEC 27002), FCC TAB RMTR, and 3GPP specifications (TS23.401, TS33.102, TS33.210, TS33.310, TS33.401, and TS33.402).

…Provide encryption capabilities to support federal, state, and local public safety users. Protective measures will need to be applied end to end across the FirstNet enterprise environment and will include securing user equipment (UE), applications running on UE, and the RAN…Additionally, considerations to support Identity, Credential, and Access Management in a user friendly, secure, federated fashion will be key to any successful cybersecurity solution (details can be found in FirstNet nationwide RFP, Section J, Attachment J-10, Cybersecurity).

Proposers shall comply with the FirstNet cybersecurity requirements. Alignment with this objective means protective measures shall be applied end to end across the MPSBN environment and shall include securing UE, applications running on UE, and the RAN.


Proposers shall coordinate with providers of local, state, and federal criminal justice information systems that will be connected to the MPSBN to determine the method of secure interconnection. Interfaces shall meet network security requirements established now or in the future by FirstNet.


15Version (4/2016)

Proposers shall describe what type of connections to the network core will be accommodated, the location of such connections, and the redundancy that will be provided for such connections.


Priority Services


…Provide a solution that allows the assignment of quality of service, priority, and preemption (QPP) parameters to user profiles using the standard service control parameters defined by 3GPP and the Internet Engineering Task Force, including Access Class, Quality Class Indicator (QCI), Allocation and Retention Priority (ARP), and Differentiated Service (Diff Serve). Allow control and management of static and dynamic assigned QPP parameters for public safety users and the ability to change user profiles in real time in response to incidents. User profile assignments and changes should be managed locally by PSEs.

Proposers shall comply with these requirements to provide full compatibility with the NPSBN. Authentication of users, setting of static priority, and control of user profile assignments and changes shall be under the control of the State. The Partner will be responsible for providing access to the MPSBN Home Subscriber Server (HSS) node by the State or its public safety entities for this purpose, among other user parameters.

Proposers are asked to provide a description of how these services would be provided, and what systems will be in place to accommodate access by authorized personnel in the user agencies


Public safety communications shall have the highest priority on the MPSBN, including ruthless preemption. Proposers shall describe how that priority will be maintained during peaks of activity, and the methods of preemption of commercial traffic or other technology that will be implemented to provide dynamic shifts in priority to support emergency operations.


Integration of State-Deployed RANs


…Integrate the NPSBN across state and territory deployed RANs so that users operate without service interruptions, including when crossing RAN service area boundaries…

16Version (4/2016)

The Partner will be responsible for interface of the MPSBN with the NPSBN in accordance with the FirstNet RFP, Section J, Attachment J-4. The Partner will be responsible for maintaining compatibility of this interface in accordance and full compatibility with the future evolution of such connectivity by the NPSBN.


Connection shall provide for routing diversity to meet the network availability goal of FirstNet and to eliminate single points of failure. Interoperability shall comply with the Recommended Minimum Technical Requirements to Ensure Nationwide Interoperability for the Nationwide Public Safety Broadband Network 22, in accordance with the FirstNet RFP, Section J, Attachment J-3.


Interfaces to the NPSBN shall be configured in such a manner that the MPSBN will remain operational for, at a minimum, intrastate operation in the event of failure of the FirstNet interconnecting network or its network components including network core functionality. Redundancy in connections to FirstNet shall be provided in a manner to eliminate single points of failure. Applications connected to the network at the state and local government levels in Michigan shall not be interrupted as a result of a failure in the FirstNet operated infrastructure.


Mobile and handheld devices associated with the MPSBN shall remain functional within the coverage area of the MPSBN in the event of FirstNet interconnecting network failure, or other network components failure, including the core. Access to local or state applications, databases, and communications capabilities (such as peer to peer communications) shall remain functional during FirstNet failures.


Proposers shall specify the manner in which the MPSBN would be connected to the NPSBN in accordance with the design requirements of FirstNet and maintain continuity of intrastate operations.



17Version (4/2016)





Integration of Existing Infrastructure to Support MPSBN Services


…Integrate existing assets— where economically desirable in accordance with Section 6206 of the Act and as further interpreted in FirstNet's request for public comments — with an emphasis on assets owned and operated by rural telecommunications providers.

Integration and use (to the extent practical) of existing commercial, federal, state, tribal and local public safety communications systems and assets into the MPSBN is a desired outcome of a PPP for the provision of the MPSBN. Integration may include interface of push-to-talk operation through gateways, dual-mode devices, or other means to permit participating public safety entities a means to interoperate with the MPSBN. Assets may include antenna sites, rooftops, backhaul facilities, emergency operations centers, network operations centers (NOCs), or other systems, applications, or property that may be available from participating public entities.

Proposers shall describe how they intend to pursue and accomplish this objective.


Life-Cycle Innovation


…Evolve the NPSBN solution—including products and services—and incorporate 3GPP LTE standards as they evolve and mature throughout the life of the contract, in accordance with the FCC TAB RMTR, the Act, including in particular Section 6206(c)(4), and the attachments in Section J.

Proposers should specify how their offer complies with this objective. This includes the method by which the network may be expanded, lifecycle innovations, and maintaining compatibility with FirstNet throughout the 25 year period of this contract.


Program and Business Management

Provide program management in the context of project work in accordance with Department of Technology, Management & Budget State Unified Information Technology Environment (DTMB SUITE)23 and Government Accountability Office cost guidelines.

Provide all ongoing operations and business services within the framework of Information Technology Infrastructure Library (ITIL®), Control Objectives for Information and Related Technologies (COBIT) and Government Accountability Office cost guidelines.

Proposers shall provide documentation on their approach to project management, financial controls, and reporting in alignment with this objective and to any grant(s) that may be provided by NTIA.

Customer Care and Marketing

In its RFP, FirstNet seeks to,23 http://www.michigan.gov/suite/

18Version (4/2016)

Market NPSBN products and services to public safety users in all states, territories, and tribal lands. Provide highly responsive and quality customer acquisition, service, and customer care. Support development and refinement of state plans, in consultation with FirstNet, and an online tool for their delivery. Provide life-cycle service and support to all users.

Michigan seeks a Partner that will operate essentially as an MVNO.

A source of funds for the sustainment of the MPSBN will be the monetization of the excess capacity on the Band 14 spectrum. The Partner will be responsible for sales and marketing activities to end users on legacy networks to gain access to the excess spectrum.

Public safety entities will be customers on the MPSBN and will require some of the same services that consumer wireless customers would expect. The Partner will also provide assistance to the State in marketing to public safety entities access to the MPSBN that will result in user fees to fund the operation and maintenance of the RAN.

Proposers shall describe what services will be provided in support of users and public safety entities in daily operations, such as account management, operational help desk, and other functions.

Proposers shall identify any other entities that will provide support of the user equipment that will be supplied to the State. Information of the qualifications of these entities shall be provided to the State.

The Partner will be responsible for billing Michigan public safety entities for access and usage of the MPSBN. Proposers shall describe the administrative and billing support it will provide for this function. Information concerning any applications that will be employed in this service and the sources of these applications shall be provided. Detail shall be provided about who will provide the administrative and billing support functions (whether provided as an integral part of the proposer’s firm or whether this is outsourced in all or part to a third-party). The location(s) of account administration, customer service, and billing operations shall be provided. If applicable, information shall be provided about the experience and qualifications of any third-party that will perform these functions.

It will be the responsibility of the selected proposer to provide an interface to public safety entities in Michigan for the purpose of supplying user equipment on the MPSBN. This function will require availability of user equipment, development of a fee schedule, and educating public safety entities regarding the capabilities of user equipment.

Proposers shall describe the sales and marketing team that will be assigned to the MPSBN. Information shall be supplied on the location of sales personnel, accessibility by email, on-line ordering, or telephone. Customer support tools that will be employed to service orders and network access requests shall be identified and described.

Proposers shall identify the manufacturers or distributors of user equipment that will be offered to the State. Evidence of an agreement between the proposer and the manufacturer or distributor shall be provided to the State.


Program and Business Management

Proposers shall provide program management in the context of project work in accordance with Department of Technology, Management & Budget State Unified Information Technology Environment (DTMB SUITE)24 and Government Accountability Office cost guidelines.

24 http://www.michigan.gov/suite/19

Version (4/2016)

All ongoing operations and business services shall be provided within the framework of Information Technology Infrastructure Library (ITIL®), Control Objectives for Information and Related Technologies (COBIT) , and Government Accountability Office cost guidelines.

Proposers shall provide documentation on their approach to project management, financial controls, and reporting in alignment with this objective and to any grant(s) that may be provided by NTIA.


Facilitation of FirstNet’s Compliance with the Act and Other Laws


…Perform all objectives and provide information and services in a manner that facilitates FirstNet’s compliance with its statutory requirements under the Act and all other applicable laws.

Under a SMLA with FirstNet, the State is likely to be required to assist FirstNet in compliance with the terms of the Act and other laws as they apply to the MPSBN and its connection to the NPSBN.

Proposers shall describe the steps they would take to assist the State in this responsibility if selected as the Partner.


Public Private Partnership

It is clear to the State that if it chooses to opt-out of the federal program, it will need a Partner with wireless network experience at the national level, financial stability, consumer sales channels, and access to and integration of Band 14 infrastructure into a legacy network(s) that provides both LTE coverage and capacity in Michigan as well as the rest of the United States for roaming purposes. Roaming provisions on a national wireless carrier during the initial operational stages of the MPSBN shall be a requirement of the Partner.

This RFP contemplates a PPP with a wireless network operator with one or more national wireless networks for roaming service. A consortium or team that provides the equivalent services will be considered for qualification.

Proposers shall demonstrate their ownership and management of a commercial wireless broadband network based on long-term evolution (LTE) technology compatible with the requirements of FirstNet or shall have a teaming partner that owns and operates such a network and is committed to a 25-year marketing and interoperability agreement with the proposer. Proposers shall identify all teaming partners. The State has right of refusal to any change of identified teaming partners.


20Version (4/2016)

Backhaul – State Microwave System Assets

The State encourages the use of existing state- or local government - owned facilities25 where practical and teaming with existing providers of broadband services that can meet a committed information rate required for public safety communications. The State also encourages development of new broadband services for backhaul that may also be expanded in functionality to improve broadband services to underserved areas.

Proposers shall provide the method of backhaul proposed from cell sites, whether microwave, fiber optic network, or other means.

Michigan is interested in the potential for sharing a backhaul broadband network that will support a statewide Emergency Services Internet Protocol (IP) network (ESInet) for Next Generation 9-1-1 (NG9-1-1) as an adjunct to deployment of a PSBN RAN. Proposers should address the feasibility of such a network that would provide connectivity between public safety answering points (PSAPs) in Michigan and the MPSBN for applications, and the addition of a separate fiber-based network for connectivity of the PSAPs with one another and with inputs from wireless and wireline networks.


Coverage Mapping Requirements

Rural coverage is a priority for the Michigan public safety community. Michigan has a vast amount of rural land that currently has limited or no public safety communications capabilities. These areas also have limited or no commercial communications capabilities. There are many components of Michigan’s critical infrastructure situated in these areas, which creates a substantially higher risk for a public safety response.

Urban coverage is anticipated to be comparable to current commercial cellular coverage, with similar coverage levels. The preferred level of coverage within urban areas is “in-building” coverage to the greatest extent possible.

Proposers shall provide coverage and capacity mapping at the level of actual signal strength for deployment phases IOC-1-through 5 and the FOC as defined in FirstNet RFP J-8 Section F.4.2.2.

Proposers shall provide maps that identify the proposed coverage provided by the Band 14 service and for the non-Band 14 offering for roaming service for: 1) the State of Michigan; 2) each county within the state; and 3) the national roaming coverage. The maps shall be submitted in both .jpg and shapefile formats that support image overlays and provide standard image manipulation features such as zoom in, zoom out, move, etc. Proposers shall take into account terrain, bodies of water, and natural or manmade obstructions that may impact projections.

Proposers shall provide maps that identify the proposed capacity provided by the Band 14 service and for the non-Band 14 offering for roaming service for: 1) the State of Michigan; 2) each county within the state; and 3) the national roaming coverage. The maps shall be submitted .jpg and shapefile formats that support image overlays and provides standard image manipulation features such as zoom in, zoom out, move, etc. Proposers shall take into account terrain, bodies of water, and natural or manmade obstructions that may impact projections.

Coverage mapping shall be provided to the State for the cases of High Risk Areas, Rural Areas, and Urban Areas for vehicular-mounted user equipment (high- and low-powered), portable devices in- vehicle and on-street, and handheld devices (smartphones) in-vehicle, on-street, and in-buildings (6,15, and 30 decibels [dB]

25 Information on tower and antenna site assets owned or occupied by the State of Michigan that have been registered with the FCC can be searched at http://wireless.fcc.gov/antenna/index.htm?job=home. Radio communications facilities licensed to the State of Michigan can be searched at http://wireless.fcc.gov/uls/index.htm?job=home . Information regarding microwave routes licensed to the State of Michigan can be searched at the FCC Universal Licensing System site http://wireless.fcc.gov/uls/index.htm?job=home .

21Version (4/2016)

http://wireless.fcc.gov/uls/index.htm?job=home

http://wireless.fcc.gov/uls/index.htm?job=home

http://wireless.fcc.gov/antenna/index.htm?job=home

penetration loss). Proposers shall take into account terrain, bodies of water, and natural or manmade obstructions that may impact projections.


Acceptance Criteria

High-level acceptance criteria are listed in Section 1.501. In addition to the general acceptance criteria, upon acceptance of the preliminary plan, the State will outline system acceptance procedures applied to the RAN that will be measured against the Partners proposed plan.

II. Requirements

Bidders: Describe in detail, your proposed solution for the MPSBN, including State roles and Contractor roles. Responses shall be formatted to follow the sequence, pagination, and required technical detail identified in the Recommended Minimum Technical Requirements to Ensure Nationwide Interoperability for the Nationwide Public Safety Broadband Network 26 , and in the FirstNet RFP - Section J, that are relative to the MPSBN in an opt-out scenario.

1.200 Roles and Responsibilities

1.201 CONTRACTOR STAFF, ROLES, AND RESPONSIBILITIES

A. Contractor StaffThe Contractor will provide resumes using Schedule A, Attachment 2 – Resume Template, for staff, including subcontractors, who will be assigned to the Contract, indicating the duties/responsibilities and qualifications of such personnel, and stating the amount of time each will be assigned to the project. The competence of the personnel the Contractor proposes for this project will be measured by the candidate’s education and experience with particular reference to experience on similar projects as described in this Statement of Work. The Contractor will provide sufficient qualified staffing as confirmed by the State Agency representative to satisfy the deliverables of this Statement of Work.

1. Single Point of Contact

The Contractor will identify a Single Point of Contact (SPOC). The duties of the SPOC shall include, but not be limited to:

supporting the management of the Contract, facilitating dispute resolution, and advising the State of performance under the terms and conditions of the Contract.

The State reserves the right to require a change in the current SPOC if the assigned SPOC is not, in the opinion of the State, adequately serving the needs of the State.

2. Key Personnel

The contractor must submit a letter of commitment for Key Personnel, signed by the identified resource, stating their commitment to work for the contractor/subcontractor on this project contingent on award of


Version (4/2016)






the bid. If the identified personnel are currently assigned to a State project the contractor must provide a letter signed by the State Project Manager releasing the individual from the project upon execution of the contract.

The Contractor will provide, and update when changed, an organizational chart indicating lines of authority for personnel involved in performance of this Contract and relationships of this staff to other programs or functions of the firm. The organizational chart shall include a description of the proposer’s Key Personnel and responsibilities that will be assigned to delivering the service of this agreement. This chart must also show lines of authority to the next senior level of management and indicate who within the firm will have prime responsibility and final authority for the work.

All Key Personnel may be subject to the State’s interview and approval process. Any key staff substitution must have the prior approval of the State. The State has identified the following, at a minimum, as key personnel for this project:

Relationship Manager as the Single Point of Contact (SPOC) Project Manager Lead RAN Infrastructure Engineer WAN/ LAN System Architect/ Engineer Cybersecurity Engineer

The Contractor shall provide resumes using Schedule A, Attachment 2 - Resume Templates, of the Key Personnel’s experience in providing the professional services which are the same or substantially similar to those services identified as required in this RFP, including a list of at least three (3) references with complete point of contact information.

Professional Services

The Relationship Manager (SPOC) shall coordinate all activities of the Service Integrator personnel assigned to the project and create all reports required by the State. Their responsibilities shall include, at a minimum:

Act as the Single Point of Contact (SPOC) for any issue related to the issued contract as it relates to the Contractor, 3rd party suppliers and appropriate Service Providers.

Manage all defined Service Integrator responsibilities in this Scope of Services. Act as the escalation point for contract issues, risks, and other concerns. Assist in developing the Contract Initiation Plan. Utilize Contract Change Management in coordination with the State Communicate on order and delivery status and issues. Manage resolution of order and delivery issues. Route calls or requests to the appropriate resource. Provide information on business processes for using the contract. Manage and report on the project’s budget. Process all submitted SOW requests and deliver detailed service and price proposals. Deliver all contract required reports on product and service delivery, and SLA compliance. Facilitate dispute resolution. Advise the State of performance under the terms and conditions of the Contract.

The Project Manager responsibilities shall include, at a minimum: Ability to deliver all aspects for the introduction of the services. Manage the network build team involving additional project management resources, internal

technical resources, 3rd party suppliers and appropriate Service Providers, account team members and client stakeholders.

Interface with 3rd party suppliers and appropriate Service Providers, involving agreement, planning, timelines and quality of deliverables.

Produce detailed project plans to manage all aspects of development of services including interdependencies.

Manage the expenditure in the development of all services ensuring all costs are recorded against products and services delivered.

23Version (4/2016)

Deliver all plans for the development of services in line with recognized best practice methodology (including but not limited to managing risk, governance, quality assurance, issue resolution, reporting), where the successful implementation of service resource skills and processes are just as critical to project success as technology.

Ensure the development of all services are successfully completed within agreed time constraints and meet the contracted level of quality.

Review the outcomes of the development of services to determine any corrective actions that could be taken to improve future delivery in terms of cost, quality and SOM’s satisfaction.

Ensure services are developed and sustained within a project-management framework. Apply business and technical knowledge to enable, support and review all aspects of change in

the service.

The Lead RAN Infrastructure Engineer responsibilities shall include, at a minimum: Participate in the analysis, design, planning and implementation phases of all RAN related

systems and infrastructure. Oversee the build, test and deploy of all RAN related systems, configurations and

infrastructure. Prepare and maintain high level infrastructure and application’s documentation in support

of project requirements and operations. Monitor efficiency of the RAN Develop solutions to complex problems that arise in the RAN. Provide RAN related technical expertise in all RAN design improvement as it may pertain

to the FirstNet service. Analyze the need for new hardware and software systems or upgrades and modifications

to existing systems by evaluating the effectiveness of the current systems. Identify system, hardware and software components required to meet RAN user needs. Identify opportunities to improve business processes by building on existing/ new

technologies and applications. Analyze and translate business strategies, plans and requirements into IT principles,

directions and standard. Conduct due diligence on equipment and service propositions. Maintain in the area of Demonstrated and maintain knowledge and experience (including industry trends and

strategies) with (at a minimum) the following RAN areas: system design architecture and applications Infrastructure equipment. Operation and maintenance of the network. Network Operations Center (NOC) Operation and maintenance of extended network systems as they pertain to

FirstNet.

The Lead WAN/ LAN Infrastructure Engineer responsibilities shall include, at a minimum: Participate in the analysis, design, planning and implementation phases of all WAN/ LAN

related systems and infrastructure. Oversee the build, test and deploy of all WAN/ LAN related systems, configurations and

infrastructure. Prepare and maintain high level infrastructure and application’s documentation in support

of project requirements and operations. Monitor efficiency of the WAN/ LAN Develop solutions to complex problems that arise in the WAN/ LAN. Provide WAN/ LAN related technical expertise in all WAN/ LAN design improvement as it

may pertain to the FirstNet service. Analyze the need for new hardware and software systems or upgrades and modifications

to existing systems by evaluating the effectiveness of the current systems.

24Version (4/2016)

Identify opportunities to improve business processes by building on existing/ new technologies and applications.

Analyze and translate business strategies, plans and requirements into IT principles, directions and standard.

Conduct due diligence on equipment and service propositions. Maintain in the area of Demonstrated and maintain knowledge and experience (including industry trends and

strategies) with (at a minimum) the following WAN/ LAN areas: system design architecture and applications Infrastructure equipment. Operation and maintenance of the network Network Operations Center (NOC) Operation and maintenance of extended network systems as they pertain to

FirstNet.

The Lead Cybersecurity Engineer responsibilities shall include, at a minimum: Participate in the analysis, design, planning and implementation phases of all RAN/ WAN/

LAN related systems and infrastructure to assure their security. Oversee the build, test and deploy of all RAN/ WAN/ LAN related systems, configurations

and infrastructure to assure their security. Analyze and translate business strategies, plans and requirements into cybersecurity policy

and procedures. Prepare and maintain cybersecurity policy and procedure documentation. Monitor the adherence to these policy and procedures. Monitor cybersecurity of the RAN/ WAN/ LAN Conduct intrusively testing on network, equipment and service. Provide cybersecurity expertise in all RAN/ WAN/ LAN design improvement particularly as

they may pertain to the FirstNet service. Maintain in the area of Demonstrated and maintain knowledge and experience (including industry trends and

strategies) with (at a minimum) in the following RAN/ WAN/ LAN areas: system design architecture and applications Infrastructure equipment. Operation and maintenance of the network Network Operations Center (NOC) Operation and maintenance of extended network systems as they pertain to

FirstNet

Bidder must complete Personnel Resume Templates –Schedule A, Attachment 2 - Resume Templates

3. Subcontractors

If the Contractor intends to utilize subcontractors, the Contractor must disclose the following:

The subcontractor’s legal business name, address, and telephone number; a description of the subcontractor’s organization and the services it will provide; and information concerning the subcontractor’s ability to provide the Contract Activities.

The relationship of the subcontractor to the Contractor. Whether the Contractor has a previous working experience with the subcontractor. If yes,

provide the details of that previous relationship. A complete description of the work that will be performed or provided by the subcontractor. Of the total bid, the price of the subcontractor’s work.

25Version (4/2016)

B. On Site Work Requirements

1. Location of Work

The work is to be performed, completed, and managed at the locations proposed by the bidder. Bidder to identify locations here below:

Bidders: Identify locations at which the work will be performed.

2. Hours of Operation:

a. Normal State business hours are 8:00 a.m. to 5:00 p.m. EST, Monday through Friday, with work performed as necessary after those hours to meet project deadlines. No overtime will be authorized or paid.

b. The State is not obligated to provide State management of assigned work outside of normal State working hours. The State reserves the right to modify the work hours in the best interest of the project.

c. Contractor shall observe the same standard holidays as State employees. The State does not compensate for holiday pay.

3. Travel:

a. No travel or expenses will be reimbursed. This includes travel costs related to training provided to the State by Contractor.

b. Travel time will not be reimbursed.

4. Additional Security and Background Check Requirements:

Proposers shall comply with screening of all personnel to be assigned to the design, deployment, operation, and maintenance of the MPSBN. Whether employees or contractors of the proposer, all persons shall comply with security screening.

Contractor must present certifications evidencing satisfactory Michigan State Police Background checks ICHAT and drug tests for all staff identified for assignment to this project.

In addition, proposed Contractor personnel will be required to complete and submit an RI-8 Fingerprint Card for the National Crime Information Center (NCIC) Finger Prints, if required by project.

Contractor will pay for all costs associated with ensuring their staff meets all requirements.

Proposers shall describe the process that will be in place for the duration of the PPP to ensure that sensitive public safety data is not compromised by the selected proposer.

Bidder: Describe in detail your proposed solution to meet the requirements of this section, including State roles and Contractor roles.

1.202 STATE STAFF, ROLES, AND RESPONSIBILITIESAgency should specify State personnel dedicated to project, and identify their associated roles and responsibilities.

26Version (4/2016)

The State project team will consist of Executive Subject Matter Experts (SME’s), project support, and a MDTMB and Agency project manager.

Executive Subject Matter ExpertsThe Executive Subject Matter Experts representing the business units involved will provide the vision for the business design and how the application shall provide for that vision. They shall be available on an as needed basis. The Executive SME’s will be empowered to:

Resolve project issues in a timely manner Review project plan, status, and issues Resolve deviations from project plan Provide acceptance sign-off Utilize change control procedures Ensure timely availability of State resources Make key implementation decisions, as identified by the Contractor’s project manager, within 48-hours

of their expected decision date.

Name Agency/Division TitlePamela Matelski MDTMB/Center for Shared Solutions Program ManagerRich Reasner MDTMB/CyberSecurity CyberSecurity SMEDavid Wilson MDTMB/Network & Telecommunications RAN SMEJohn McQuaid MDTMB/Infrastructure Design & Delivery Mobile Device & Application SMEJack Harris MDTMB/Enterprise Architecture RAN SME

State Project Manager- (MDTMB and Agency)

MDTMB will provide a Project Manager who will be responsible for the State’s infrastructure and coordinate with the Contractor in determining the system configuration.

The State’s Project Manager will provide the following services: Provide State facilities, as needed Coordinate the State resources necessary for the project Facilitate coordination between various external contractors Facilitate communication between different State departments/divisions Provide acceptance and sign-off of deliverable/milestone Review and sign-off of timesheets and invoices Resolve project issues Escalate outstanding/high priority issues Utilize change control procedures Conduct regular and ongoing review of the project to confirm that it meets original objectives and

requirements Document and archive all important project decisions Arrange, schedule and facilitate State staff attendance at all project meetings.

Name Agency/Division TitleJohn Ruzicka MDTMB/EPMO Project ManagerPamela Matelski MDTMB/CSS Program Manager

MDTMB shall provide a Contract Administrator whose duties shall include, but not be limited to, supporting the management of the Contract.

Name Agency/Division TitleLorri White MDTMB/Procurement Category Manager

1.300 Project Plan

1.301 PROJECT PLAN MANAGEMENT

27Version (4/2016)

Preliminary Project Plan Contractor will provide a Preliminary Project Charter (PMM-0101), Project Management Plan with Project Schedule (PMM-0102) as described following with the proposal for evaluation purposes, including necessary time frames and deliverables for the various stages of the project and the responsibilities and obligations of both the Contractor and the State.

1. In particular, the Preliminary Project Schedule will include a MS Project plan or agreed equivalent containing:

a. A description of the deliverables to be provided under this contract.b. Target dates and critical paths for the deliverables.c. Identification of roles and responsibilities, including the organization responsible. Contractor is

to provide a roles and responsibility matrix.d. The labor, hardware, materials and supplies required to be provided by the State in meeting the

target dates established in the Preliminary Project Plan.e. Internal milestonesf. Task durations

Note: A Final Project Plan will be required as stated in Article 1, Section 1.301 (C) Project Control.

Orientation Meeting

Upon 15 calendar days from execution of the Contract, the Contractor will be required to attend an orientation meeting to discuss the content and procedures of the Contract. The meeting will be held in Lansing, Michigan, at a date and time mutually acceptable to the State and the Contractor. The State shall bear no cost for the time and travel of the Contractor for attendance at the meeting.

Performance Review Meetings

The State will require the Contractor to attend monthly meetings, at a minimum, to review the Contractor’s performance under the Contract. The meetings will be held in Lansing, Michigan, or by teleconference, as mutually agreed by the State and the Contractor. The State shall bear no cost for the time and travel of the Contractor for attendance at the meeting.

Project Control

1. The Contractor will carry out this project under the direction and control of MDTMB, Center for Shared Solutions (CSS), Infrastructure, and Cyber Security.

2. Within 15 working days of the execution of the Contract, the Contractor will submit to the State project manager(s) for final approval of the project plan. This project plan must be in agreement with Article 1, Section 1.104 Work and Deliverables, and must include in the format of Project Management Plan with Project Schedule (PMM-0102) the following: The Contractor’s project organizational structure. The Contractor’s staffing table with names and title of personnel assigned to the project. This must

be in agreement with staffing of accepted proposal. Necessary substitutions due to change of employment status and other unforeseen circumstances may only be made with prior approval of the State.

The project work breakdown structure (WBS) showing sub-projects, activities and tasks, and resources required and allocated to each.

The time-phased plan in the form of a graphic display, showing each event, task, and decision point in the WBS.

3. The Contractor will manage the project in accordance with the State Unified Information Technology Environment (SUITE) methodology, which includes standards for project management, systems engineering, and associated forms and templates which is available at http://www.michigan.gov/suite a. Contractor will use Microsoft Project or other agreed automated tool for planning, monitoring, and

tracking the Contract’s progress and the level of effort of any Contractor personnel spent performing Services under the Contract. The tool shall have the capability to produce: Staffing tables with names of personnel assigned to Contract tasks.

28Version (4/2016)

http://www.michigan.gov/suite

Project plans showing tasks, subtasks, deliverables, and the resources required and allocated to each (including detailed plans for all Services to be performed within the next 15 calendar days, updated semi-monthly).

Updates must include actual time spent on each task and a revised estimate to complete. Graphs showing critical events, dependencies and decision points during the course of the

Contract.b. Any tool(s) used by Contractor for such purposes must produce information of a type and in a

manner and format that will support reporting in compliance with the State standards.c. Contractor will provide an updated Project Management Plan (PMM-0102) when requested by the

State.

4. The Contractor will be responsible for maintaining a Configuration Management Database (CMDB) of all RAN assets and configurations that is viewable/auditable by the State.

Bidder’s Response

1.302 REPORTS

Contractor will submit by EOB Friday each week by email the following status report:1. Cover page in ½ page or less summarizing week accomplishments, missed target dates, outstanding

risks, outstanding issues.2. MS Project Gant Chart of no more than 10 high level milestones covering next 3 to 12 months

deliverables.3. Full MS Project task list at current state showing tasks, predecessors, successors.

Contractor will schedule and hold a 30-minute conference call with screen share on alternate Monday mornings with the following agenda:

1. 15-minute status review using the weekly report from the prior Friday.2. 15-minute topics as needed covering announced topics, change requests, risks, issues based on an

updated Project Management Plan (PMM-0102).

Reporting formats must be submitted to the State’s Project Manager for approval within 15 business days after the execution of the contract resulting from this RFP. Once both parties have agreed to the format of the report, it shall become the standard to follow for the duration of the contract.

Weekly Project status Updated project plan Summary of activity during the report period Accomplishments during the report period Deliverable status Schedule status Action Item status Issues Change Control Repair status Maintenance Activity

Bidder’s Response

1.400 Project Management

1.401 ISSUE MANAGEMENTAn issue is an identified event that if not addressed may affect schedule, scope, quality, or budget.

The Contractor shall maintain an issue log within the framework of the Project Management Plan (PMM-0102 for issues relating to the provision of services under this Contract. The issue management log must be

29Version (4/2016)

communicated to the State’s Project Manager on an agreed upon schedule, with email notifications and updates. The issue log must be updated and must contain the following minimum elements:

Description of issue Issue identification date Responsibility for resolving issue. Priority for issue resolution (to be mutually agreed upon by the State and the Contractor) Resources assigned responsibility for resolution Resolution date Resolution description

Issues shall be escalated for resolution from level 1 through level 3, as defined below:

Level 1 – Business leadsLevel 2 – Project ManagersLevel 3 – Executive Subject Matter Experts (SME’s)

Bidder’s Response

1.402 RISK MANAGEMENTA risk is an unknown circumstance or event that, if it occurs, may have a positive or negative impact on the project.

The Contractor is responsible for establishing a risk management plan and process, including the identification and recording of risk items, prioritization of risks, definition of mitigation strategies, monitoring of risk items, and periodic risk assessment reviews with the State within the framework of the Project Management Plan (PMM-0102).

A risk management plan format shall be submitted to the State for approval within twenty (20) business days after the effective date of the contract resulting from the upcoming RFP. The risk management plan will be developed during the initial planning phase of the project, and be in accordance with the State’s PMM methodology. Once both parties have agreed to the format of the plan, it shall become the standard to follow for the duration of the contract. The plan must be updated bi-weekly, or as agreed upon.

The Contractor shall provide the tool to track risks and report within the framework of the Project Management Plan (PMM-0102). The Contractor will work with the State and allow input into the prioritization of risks.

The Contractor is responsible for identification of risks for each phase of the project. Mitigating and/or eliminating assigned risks will be the responsibility of the Contractor. The State will assume the same responsibility for risks assigned to them.

The Contractor is responsible for identification of risks for each phase of the project. Mitigating and/or eliminating assigned risks will be the responsibility of the Contractor. The State will assume the same responsibility for risks assigned to them.

Bidder’s Response

1.403 CHANGE MANAGEMENTProject Change ManagementProject change management is defined as the process to communicate, assess, monitor, and control all changes to system resources and processes. The State also employs change management in its administration of the Contract.

30Version (4/2016)

Contract Change ManagementIf a proposed contract change is approved by the Agency, the Contract Administrator will submit a request for change to the Department of Technology, Management and Budget, Procurement Buyer, who will make recommendations to the Director of DTMB-Procurement regarding ultimate approval/disapproval of change request. If the DTMB Procurement Director agrees with the proposed modification, and all required approvals are obtained (including State Administrative Board), the DTMB-Procurement Buyer will issue an addendum to the Contract, via a Contract Change Notice. Contractors who provide products or services prior to the issuance of a Contract Change Notice by the DTMB-Procurement, risk non-payment for the out-of-scope/pricing products and/or services.

The Contractor must employ change management procedures to handle such things as “out-of-scope” requests or changing business needs of the State while the migration is underway following the State guidelines as set forth in SUITE.

The Contractor will employ the change control methodologies to justify changes in the processing environment, and to ensure those changes will not adversely affect performance or availability.

Bidders: Acknowledge understanding and acceptance of these two process areas and explain in detail proposed methods for meeting these requirements.

1.500 Acceptance

1.501 CRITERIA

FirstNet has specified the general quality measures to be applied to each work product. The State intends to review all work products of the Partner against these measures.

Accuracy – Work products shall be accurate in presentation, technical content, and adherence to accepted elements of style.Clarity – Work products shall be clear and concise. Any/all diagrams shall be easy to understand and be relevant to the supporting narrative. Consistency to Requirements – All work products shall satisfy the requirements of this contract.File Editing – All text and diagrammatic files shall be editable by the Government. Format – Work products shall be submitted in hard copy (where applicable) and in media, unless otherwise specified herein. Hard-copy formats shall follow any specified directives or manuals. Media formats shall follow the mutual agreement of the parties unless specified elsewhere.Timeliness – Work products shall be submitted on or before the due date specified herein or submitted in accordance with a later scheduled date determined by the Government.

1.502 FINAL ACCEPTANCE

A final proposed plan will be mutually agreed upon between the State and the Partner. In its agreement with the Partner, the State will outline system acceptance procedures that will be applied to the RAN that will be measured against the Partners final proposed plan in addition to the general acceptance criteria. Factors that will comprise acceptance, and which will govern progress payments, include the following:

Coverage – Band 14 system coverage of specified service areas as defined in this RFP; coverage will be based on achievable data rates on the cell edge within the coverage area

Capacity – Testing of the network under conditions of simulated or actual high traffic and a measure of the RAN QoS

Backhaul functionality and achievement of data rates Quality of installations – public safety-grade Standby power system functionality, fuel supply, installation

31Version (4/2016)

Site monitoring and security functions Network management functions operational Administrative functions – asset management, inventory Billing interfaces functional Business systems; financial reporting operational and functional User equipment programming interfaces functional Application interfaces and functionality

1.600 Compensation and Payment

1.601 COMPENSATION AND PAYMENT

Bidder will be required to make payments to the State under the SMLA, in support of the FirstNet core infrastructure, and for work and services provided by the State in support of the MPSBN. The terms and conditions of the SMLA, the calculation of the payments for access to and support of the FirstNet core infrastructure, and the scope of work and services provided by the State are presently unknown.

Proposers should identify the method by which such payments would be calculated and paid.

Bidders: Acknowledge understanding and acceptance of this requirement and explain in detail proposed method for meeting this requirement.

Method of PaymentPayments will be made to the State in a combination of an annual lump sum payment for fixed costs and on a monthly basis for rated services.

Bidder must identify the factors and components which contribute to the financial model proposed.

Extended purchasing program volume requirements are not included, unless stated otherwise.

Travel

The State will not pay for any travel expenses, including hotel, mileage, meals, parking, etc. Travel time will not be reimbursed.

Out-of-Pocket Expenses

Contractor out-of-pocket expenses are not separately reimbursable by the State.

Statements of Work for Changes and Issuance of Associated Purchase Orders Unless otherwise agreed by the parties, each Statement of Work will include:

1. Background2. Project Objective3. Scope of Work4. Deliverables5. Acceptance Criteria6. Project Control and Reports7. Specific Department Standards8. Payment Schedule9. Travel and Expenses

10. Project Contacts11. Agency Responsibilities and Assumptions12. Location of Where the Work is to be performed13. Expected Contractor Work Hours and Conditions

32Version (4/2016)

The parties agree that the Services/Deliverables to be rendered by Contractor pursuant to this Contract (and any future amendments of it) will be defined and described in detail in Statements of Work or Purchase Orders (PO) executed under this Contract. Contractor shall not be obliged or authorized to commence any work to implement a Statement of Work until authorized via a PO issued against this Contract. Contractor shall perform in accordance with this Contract, including the Statements of Work/Purchase Orders executed under it.

InvoicingContractor will submit properly itemized invoices to

DTMB – Financial ServicesAccounts PayableP.O. Box 30026Lansing, MI [email protected]

. Invoices must provide and itemize, as applicable: Contract number; Purchase Order number Contractor name, address, phone number, and Federal Tax Identification Number; Description of any commodities/hardware, including quantity ordered; Date(s) of delivery and/or date(s) of installation and set up; Price for each item, or Contractor’s list price for each item and applicable discounts; Maintenance charges; Net invoice price for each item; Shipping costs; Other applicable charges; Total invoice price; and Payment terms, including any available prompt payment discount.

The State may pay maintenance and support charges on a monthly basis, in arrears. Payment of maintenance service/support of less than one (1) month’s duration shall be prorated at 1/30th of the basic monthly maintenance charges for each calendar day.

Incorrect or incomplete invoices will be returned to Contractor for correction and reissue.

1.602 HOLDBACKReserved

33Version (4/2016)

mailto:[email protected]

it-sow 4-4-16 rfp_schedule... · web viewthe mdtmb project manager must approve any tools, in...

Documents