The bidding process is the most easily held by manufacturers in building the school WiFi web-based NATSHELLL_AUTH_BILLING system. The vendor’s bid documents are often well written, a good list of functions and a real landing list, and half of them will either add money or not fit for the school scene.
The demand comes from research, not from the manufacturer's page.
The list is the skeleton of the need file. The hard parameters are required in the original form if there is only one in the demand document."Support for large-scale simultaneous development"This empty phrase allows the manufacturer to match the bid with a minimum configuration and then raise it later."How much support is it?""Which protocols are we on?""Compatibility of existing equipment models"The manufacturer cannot manipulate the hard indicators written with numbers.
Consistency and compatibility as binding conditions
Schools are not white paper, new systems are to be integrated into the existing environment. The need documentation must clearly identify the system to be docked: what is the protocol for uniform identification, what is the name of the wireless controller, what model of export equipment, whether or not to move data to the current billing system. These are written as non-derogable constraints and the bidders must answer each question on their ability to do it, how they do it, and not generally."Support docking"We've seen schools forget to write old-fashioned switches, and when they come in, the manufacturers don't get it. They either change equipment or cut half their functionality, and they lose all their power.
The functional list is to be divided into necessary and optional
Do not list all desired functions as optional options, either to push the budget out of line or force manufacturers to steal jobs elsewhere. It is proposed that the functionality be divided into three categories: necessity, recommendation, and sub-items. The requisites are essential for schools to operate, such as Portal certification, account management, base billing, Log Audit; the recommended items are obvious improvements in experience but unnaturally dead, such as no sensory authentication, multi-school synchronization; and the sub-items are fancy. A negative vote is required when evaluating bids, which recommends and sub-points are given at a satisfaction level. This allows both bottom line control and reasonable room for the manufacturer to make use of it.
The acceptance criteria are to be included in the contract attachment.
The worst part is that it's all-perfect, but not standard."It's done."And the school can't say."I didn't.". The need document is accompanied by an operational receiving and inspection list: what measure each core function will be measured, what performance pressure will be achieved. For example, the certification success rate will be no lower than a given value for one week in a row, and how much will it reach at late peaks and how much will it be sent. These quantitative indicators are linked to payment nodes, which will not be accepted until they have been paid. Schools will only have their hands on the WiFi web site Authentication & Billing system, essentially buying a long-term capability, not a functional list.
Don't ignore the service and training provisions.
The system is bought back for human security. The demand documents are to specify the delivery that the manufacturer must provide: deployment of files, interface instructions, a guidebook, training times and targets. Many schools are only looking at software functionality, neglecting knowledge and capability transfer, and as soon as the company withdraws, no one moves on its own, and small problems are always high-cost.
Make the bid evaluation a priority.
Many schools have over-valued their bids, technical responses were too generous, resulting in low price marks, a sharp reduction in function when they landed, and an additional cost that was much more than minimal. It is suggested that technology conformity, matchability, and service terms be revalued above prices, especially hard to reject. The evaluation experts need someone who really knows the network and certification, not just origin and offer.
Saves a good interface and residual for phase two.
The need to include in the demand document a system that supports subsequent expansion: additional campuses, additional certifications, and matching new management platforms cannot require a reversal. Delegation of authority will also be left to buy at current peak multipliers, avoiding renegotiations as soon as next year’s increase is achieved. Evolvable writing into contracts will not lock down future initiatives in schools.
The acceptance is to be checked out by a third party.
The acceptance is the easiest part of school to relax."Done."The latter is left to itself. It is more prudent to introduce a relatively independent third party to conduct acceptance tests, with the quantitative indicators in the demand file checking by item: how much capacity is available; whether certification success rates are not lower than one week in a row; and whether the interface system is normal. Third parties do not necessarily represent a more professional but at least have different positions, stating that the vendor has failed to do so.