The residential system is selected for online billing, and the manufacturer's presentation usually is beautiful: big screen reports, one key opening, automatic reconciliation, all of which are wanted. It takes a year to buy back and find that the points not mentioned in the presentation are daily pain points. We have made several rounds of selection assessments and found schools most vulnerable to falling into their heads in a few invisible places. This list lists the things they can easily ignore when choosing but they are on line every day to help you put the necessary items on the table.
And not just the number of people you can call it.
The manufacturer likes to say,"Support 100,000 terminal."But the problem with the dormitory is that it's instantaneous, not total. This peak is true when thousands of people are certified for the first time in the first few days of school. We suggest that manufacturers take the real number of your schools and press them together, see how the authentication servers and databases respond, rather than look at the brochure numbers. The 100,000 but peaks do not last as much as 5,000 but the peak is five thousand.
The ability to connect is more important than the function.
The accommodation billing is rarely an isolated system, which has to be managed by the dormitory, consolidated identity and paid reconciliations. Many manufacturers have a full capacity, but the interface is private, not a file, and it really needs to be developed or not done. We suggest that when you choose to match the matching requirements, we can put them on a list, so that the vendor shows how to do it, and it is better to see a real interface sample on the spot. If you have weak capacity, each connection will be supplemented manually, with the cost of transport far exceeding the cost of saving software.
Reconciliation and refunds are performed on site
The reconciliation and refunds occur every day, as long as the system is a collection of money. Some manufacturers have made good statements, but they are not fully exported on a monthly basis, their repayments are manually re-arranged, and the financial month-end reconciliations are exhausted. We suggest that the model be selected with the finance present, and that the field show be able to export the fluid, make a refund, check a consumption breakdown, and see how it goes."End of story."The function doesn't look sexy, but the maximum frequency after you get online. The demonstration ignores it most often.
The vendor's response to the transmission is written into the contract.
The system is often in trouble at midnight or the day of school, when the vendor can respond in a timely manner and has more impact than it does on its ability to function. We suggest that the choice be made to write the service level into a contract: response time, attendance time, security for major festivals, and version upgrades free of charge. Some vendors are cold after selling, leaving problems with the school itself. It is equally important to ask those who have used the same type of schools more about their sales commitments than about them.
There's room for expansion and evolution.
The dormitory buildings are built up, the student councils are increased, and the bandwidth increases. Some programmes are closed, with a building repurchases authorization, a bandwidth change, and later tied to death. We suggest that when you choose, you ask: how much can you add node, how do you calculate it, and whether data can be exported? The structure is open, and the cost of evolution is low; the closure saves money and the long term.
Don't get distracted by value added features.
Manufacturers often use a lot of additional capabilities to attract you: behavioral analysis, content auditing, advertising. Some of these are useful for you, but they can increase price and complexity. We suggest that the selection should be made sure that all necessary items are met and value added is not valuable. The requisites are stable collection, stable certification, clear reconciliation; value addition is missing without affecting the main line.
And you're gonna use the pilot to crack the beautiful words in the presentation.
In the final phase of the selection, we strongly recommend a small-scale pilot instead of a demonstration. Pick one or two buildings, hundreds of students, run the manufacturer's system for weeks, watch and send reconciliations, check docking, watch transport, and respond ten times as much as PPT. The demonstration was done by the firm. The real dormitory peaks, dirty data, flashes are mirrors."I'll find out if you buy it."Many schools skip the pilot and then come online and find out that the promised functionality is more expensive to develop.
Don't forget to count the cost of ownership.
The option is easy to look at the software offers, ignoring subsequent renewals of authorizations, extension fees, custom development costs. We suggest that manufacturers be asked to make clear what they can do over three years, so that they don’t get low prices and high rates for renewal.
The choice of a system for billing the Internet in accommodation is never a major function, but rather a routine link that can be easily ignored. List the necessary items and let the manufacturer press the peak to show itself, visit the slogans and do much more than divide them. Right, the rest of the years are less focused; right, and it is self-employed who chooses to go back to work.