Many schools have been discussing it over and over again when they're preparing to go to the school network billing system."What specific problem are we dealing with?"But..."Which system is the most functional on the market?"The list of functions is drawn on the screen, and everyone can pick out a few points they think they need. Once we've finished the report, it doesn't seem to be solving any real problems."Product comparison table"This is too common in the information program of schools, and it often results in spending money, getting online, not really taking care of things.
Take it."Charges"Consider it"Fees"It's the first one to run off.
It's in the school network billing system."Charges"And a lot of people understand it."Fees"Not the same thing. The real problem in schools is not to take money from student accounts, but rather how the flow is distributed, who is using it, where it is used, and how the network resources are prioritized by population groups."Charges"I understand."Fees"The item is oriented toward the financial system, and the products that are eventually selected may be very cost-effective, but they do not care about real network management claims like flow orthopaedics, time strategies, user groups, etc."Fees are a tool, network resource management is an end", the later functional selection is justified.
Take it."- All schools are unified."It's a common mistake to be targeted.
Some schools set the goal of a school network billing system when setting up projects."A school-wide network, a uniform certification, a common billing"It sounds ambitious, but practical in its implementation there are a variety of real constraints. For example, the teaching areas are used with high daily density, the dormitories at night, and both scenarios have different flow characteristics, user behaviour, and costing logic, which are often not well-managed by the same strategy. The more pragmatic approach to this is to sort out what priority areas are, which are suspended, how the strategies are connected between them."- All schools are unified."As a long-term vision, it could be possible but not realistic as the objective of a project.
Take it."Authentication of real names"and"Charges"It's too tight.
Real name certification is a compliance requirement, and billing is a resource management tool. Both things are often mixed up in the school network costing system, but actually two logics. The real name authentication requires each user to be identified retroactively, corresponding to logs, audits, division of responsibilities. The charge requires that every user use of the network be measurable, matching traffic, duration, and set-up. If both things are tied into one demand at the time of setting up, the last selected system may not work well on either side.——The certification module is complicated by the need to balance the billing scene, and the costing module loses flexibility by balancing the audit landscape."System of accounts"and"Fees policy"Separate discussions to identify what is necessary and what is required.
Take it."Support multi-end"I understand."Support all devices"
There are a variety of terminals, such as mobile phones, table boards, notebooks, desktops, smart bracelets, Iot devices, visitor equipment."To support all terminals"The school network billing system is about the end of a real use scenario, not a technically supported list. For example, smart bracelets are in very low demand and little is being used to capture network resources."Which end categories must be supported"/ To set aside categories not covered for the time being and to consider their expansion when there is a real need.
Take it."Extendable"As a mighty shield.
"Extendable"These three words appear in almost all of the reports on the creation of a school network billing system, but they are themselves an uninformation-based description. The systems certainly have to be expanded, but what is specifically expanded, how much it costs, and what preconditions for expansion are often not written in the reports."Support for future expansion to graduate student dormitories"——This sounds reasonable, but to do so requires a system of billing that supports new user groups, new tariff templates, new authentication methods and matching with existing graduate studies systems. If these details are not discussed when the items are set out, then it is called"Extendable"Just a key word on a PPT, not actually binding.
Take it."Connecting existing systems"It's too simple.
The school network billing system needs to be connected to a lot of systems.——Each system has its own data format, interface specifications, and a team of drivers."Just a little bit."But in actual projects, the matchmaking often accounts for 30-50% of the total project workload and there are many risk points."List of required systems"and"The head of each system docked"All listed, not just written."Support docking"This item is solid, and the rest of the project is scheduled.
Take it."Pilot first"Being solid is the best way to avoid a hitch.
The school network billing system project in a number of schools was opened directly throughout the school without piloting, resulting in a concentrated outbreak of problems when it got online.——The authentication page is open, the billing data are inaccurate and there is a surge in user complaints."Started with a dormitory area or an academy running on a pilot basis for 2-3 months, then rolled out to the whole school"The pilot is not about proving the system's availability, but about exposing problems in a real use scenario."It's a separate phenomenon."The story is biased."Pilot feedback mechanism"It's much more useful than writing a 10-page functional comparison.