The request for proposals document is the central expression of all ideas in the school's WiFi system and the only standard for subsequent acceptance. Unfortunately, too many schools have demand files that either copy the manufacturer's white paper or write it empty and general, and anyone can say when evaluating the bid."I'm satisfied."And then it turns out that it's not doing as much as it really wants. The need is not good, so you give the voice to the manufacturer ahead of time. This thing deserves serious and real.
Needs are based on their current status, not on the manufacturer's functional chart.
The situation is being examined, and it's now useful. The document should start with a clear description: how many dormitory buildings we have in the school, how many students are living, what certifications are available, how large the exports are, and how much the historical peaks are. These background factors determine the amount of each technology that comes up."Support for harmonized authentication, support to billing, support to multiple terminals"The company is naturally based on minimum standards. With its own numbers, it is not afraid to delete them at will.
Take it."Yes."and"- I'd better have it."Write it down. Don't mix it up.
The most taboo thing about the need documents is"Support"What is the level of support? Is it core or is it a good idea? The proposal is clearly divided into three categories: rigid indicators for one veto, important but moderate, and possibly optional sub-items."The late peak supports 5,000 with certification."It's rigid."Supports graphic reports"It's a plus. After the grade, the evaluation is justified and the manufacturer knows where to go. Write it all down."Support"The consequence is that the most critical capacity indicators are buried in a pile of fancy functions.
The capacity and performance are dead numbers, not adjectives.
"High performance""Steady and reliable."This word is zero in demand. It must be written: authentication and distribution, average response not more than milliseconds, single point failure transition time, and the range of measurement errors. These figures are derived from the previous touchdown and peak measurements, not taken. Dead numbers, followed by acceptance, have a ruler. We've seen the most disproportionate needs."Meeting school development needs"The manufacturer has put in a small system that lasts two years and the school can't say it defaulted. The adjective is digging its own pit.
Match and Compatibility to Specific Objects, not only"Open Interface"
Harmonization of authentication docking, compatibility of the PNT and existing switchboards, which cannot be merely written"Support standard interface"You have to write: which certification protocols we use, which brands are compatible with and which core exchange on the Internet is connected. It would be better if manufacturers were asked to provide a docking program rather than a promise when bidding. The more specific the demand, the less the later the ripping."Open Interface"Four words enough to get the manufacturer back to school when they deliver."You're in a special situation."。
The most demanding part of the demand is the delivery and receipt clause.
Many of the requests are for functions, and all the receipt and inspection is gold. The system turns up, nobody's watching surveillance, they're guessing about malfunctioning, they're only receiving."Can you log in?"The need should be to indicate which particle size monitoring, how a failure alarm is sent, which receiving and inspection scenes must run, and how long the test runs."What do we do when we get online?"Write"I'm going to buy something I promised before."The price of the sale is all school.
Leave some room for yourself, and leave the grip to take.
The evaluation and the on-site presentation are the last things to happen.
The demand is well written, and the bid is not true or for nothing. It is suggested that a live demonstration be added to the evaluation: let the manufacturer test the environment in the school and run out the hard-on indicators of the need one by one instead of reading the commitment book. For example, it's good to send certifications, check accounts, batch operations."Look at the material."Changed"Watch your ass."The manufacturer is afraid to use the template and every demand in the need is met.
Don't forget to write down the consequences of failure to pass.
The demand is accompanied by rigid indicators."What if you don't meet the target?". Is it a rejection, a cutback, a fixed term, or a fine? Many schools have hard-writing and soft contracts, resulting in 80% of the system being handed over by the manufacturer, which is simply squeezed because they don't have a refusal clause. It is recommended that the acceptance threshold for key indicators be written directly into the contract annex to match demand."It's basically working."Let's play games."Completely achieved"The last amount of demand for a tender should be insurance.
Finally, the need is not to write so much about the lack of space, but rather to make room for a better understanding in the construction process. But leaving room is not to leave ambiguity, but to put it on the right track."Needs Change Process"It's written: what can be fine-tuned, who will pedal and how to record. And keep a receipt knife.——The key indicators are not met. The demand for bids for the WiFi system of boarding houses is essentially a contract between schools and manufacturers, which makes it easier to run off.