FirstNet releases answers to third set of RFP questions
What is in this article?
FirstNet releases answers to third set of RFP questions
Only a handful of changes were made to the FirstNet request for proposal (RFP) in last week’s third set of answers to inquiries about the procurement, but the responses do offer insights about how future expansions to the proposed nationwide public-safety broadband network (NPSBN) will be executed.
Many RFP changes referenced in this batch of 92 answers were administrative in nature, such as clarifying whether the inclusion of certain maps would count against the page limit for a response. But one question resulted in a change to one of the 16 FirstNet objectives that represent the core functionality sought in the RFP. The change involves the support of software container solutions within the device-ecosystem objective.
“The ecosystem shall support Bring Your Own Device (BYOD) as well as, at a minimum, devices that … support secure containers to isolate FirstNet applications,” the amended objective states.
Another answer added clarification about the kind of network-resiliency descriptions that offerors should make when submitting their bids, which are due on May 13.
“Provide the network design including survivability assumptions to maintain an acceptable level of service in the face of natural disasters, faults and other challenges, which may include but are not limited to any natural or man-made events that adversely impact Public Safety Entities’ access to or use of the NSPBN pertaining to normal operation,” the answer states. “Outline the process to maintain and improve network resiliency for the NPSBN.”
Meanwhile, another response to an inquiry provided some information about how future expansions to the FirstNet system would be addressed. The contractor can include expansion proposals in its RFP bid, and it would be obligated to meet the terms outlined in the bid.
After the FirstNet contract is awarded, expansions not addressed in the RFP bid can be proposed by either the federal government or by the contractor, according to the answer to a question on the matter.
“If the Contractor’s proposed solution included future expansions to the NPSBN, upon award, the Contractor would be responsible for costs related to those expansions,” the answer states.
“With regard to Government-defined future expansions of the NPSBN, a subsequent task order would be issued and funded under this contract or through a separate RFP process. In the case of Contractor-offered expansions post-award, the Contractor would be required to follow the process identified in Section H.11, Technology Refresh/Enhancement Proposals.”
One thing that scares me.
One thing that scares me. “After the FirstNet contract is awarded, expansions not addressed in the RFP bid can be proposed by either the federal government or by the contractor, according to the answer to a question on the matter”. This is commonly known as a ‘Change Order’. Anyone that has ever managed a project knows that this means $$$$. With FirstNet’s budget, it’s something they may not be able to afford. I say this with the understanding that technology is a ‘road race’ and is getting to the point that when you buy a newly released product, drive it home and take it out of the box-it’s almost obsolete already! And, we’re looking a couple of years down the road before the first sites built by FirstNet come online.
As for ‘Public Safety Hardening’, I for one do NOT want any details discussed publicly. Do we discuss security with prision inmates? I have faith that between standards suggested by the NPSTC and others, several redundent layers will be mandated for operation and security.
With the scope and magnitute of this project, we need to tip our hats to the FirstNet board! Seems like they’re doing their best to get it right.