Schools buy wireless Portal, which is most often on demand books. Either it's too empty, the factory-commercial presentation belt is biased; or the border is unclear and we get online to find that it doesn't contain it. We have changed the bidding parameters for schools, found a few pits, and saved a lot of dirt from the back.
Puddle I: The authentication boundary is not well written
The most important thing in the book of need is that this system does not matter. Many schools only write.“Construction of wireless authentication system”, does not say if it contains content filtering or bandwidth management. The result is that the manufacturer delivers on a minimum set and the school wants to pay for the functions in a second time. We suggest that the need book should list the boundaries: authentication, billing, roaming, logs at each level, and which ones are excluded. The boundary is clear and the manufacturer is afraid to change the concept.
Punk two: A capacity to shoot a head.
The capacity is the easiest to manipulate in a bid. Some schools write it.“Support for full school development”No numbers are given; some of the parameters for a different school are not valid. We suggest that the size be determined by using a peak model after the touchdown, with clear and distributed online numbers, single account terminals, and late peaks. Without the volume requirements for the number, the evaluation is never more than true, and the manufacturer can fill it in. It is only by writing down the number that you can block water.
Trail three: the docking requirement is vague
The need book is always written about the integration of identity.“Support authentication docking”No protocol, no list of sources. The middle bidder says our platform is too old to be connected and it needs to be matched with money. We suggest that the docking protocol, the identity type, and whether or not the visitors are included in the request should be requested for a docking test report.
Pocket IV: No measurable standards for acceptance and inspection
A lot of writing.“System stability”“It's a good experience.”We suggest that each requires a measurable acceptance action: support for high-situation, which is measured by pressure; guarantee data security, which checks whether passwords are stored explicitly and log marks are left; travel across buildings, which actually takes the equipment to two buildings. Once demand documents are measured, manufacturers are afraid to fill them in with words.
Powder Five: lack of accountability for the carrier
We suggest that the drafts be included in the contract: response time, stay or long-range, and payment for a major malfunction. The liability is unclear; the company's network centre is pushed on the line and the problem is being broken. The code is so small that it is a personal shield.
Punk Six: No mention of the reserve.
No one thought three years later at the time of the tender, but Wireless Portal was used for several years. We suggested that the demand book would require opening interfaces, data to export, and support smooth upgrades, not tied to private agreements. The change in presets were written in, and the subsequent upgrades did not have to be reversed. Many schools had chosen a closed solution cheaply, and they found that data could not be exported and only dropped with hardware.
Demonstrate the authenticity of the environment
The vendors prefer to use carefully prepared environmental performances, but the environment and your school is often far from being real. We suggest that manufacturers be asked to demonstrate on the test environment or real data in schools rather than using self-contained models. In particular, co-matching and matching must be measured under conditions close to reality. The demonstration is true, and the difference between the winning bid and the closing mark is small. This way of writing an evaluation will block a lot of racks.
Don't miss the training.
The system is for human use, and whether the network centre teacher will be able to access it or not. We suggest that the demand book should make clear how many people are trained, how long they train, how long they can give them a manual and a guide to discharge. Many schools have forgotten this, the system is in the process of being used, and the vendor's distance guidance is slow and difficult for the first month.
Write the requirements into the contract text
The boundaries, capacity, and matching requirements in the request form are ultimately set out in the contract text, not just as an attachment. We suggest that after evaluation of the bid, parameters identified by the winning bidder be copied into the contract to serve as a basis for acceptance. Many school needs are hard-written, contracts are soft, and final manufacturers deliver them according to the minimum contractual standards.
Don't put the treasure on the family.
One or two alternative vendors are selected for the bidding process, and one can avoid being tied up. We suggest that a short list of at least three be kept public, with no relationship between who meets the criteria.
Wireless Portal bidding needs are most likely to step on the pits at borders, capacity, docking, receiving and inspection, wiring, replacing them. The adjective is replaced by numbers and movements that kill the tender, which can be evaluated horizontally against the real one, without being used as a demo. A stronger book of needs, with less effort in the years ahead, is much more important than cutting down prices.