The building of a separate account for the WiFi network billing system is one of the most easily underestimated problems in the project. We have seen schools, where the billing system sends its own accounts and its own passwords, so students have to write two sets of codes and forget one of them. Worse still, when they leave school, they only sell numbers in the uniform identification system, the billing system remains alive, continues to generate bills or is used by people. So the first thing that comes out of the new dormitory billing system is whether it can eat the school's unified identity instead of starting a stove.
We'll confirm the agreement for a unified school identity.
Before we do this, we need to find out what interfaces are open for the school's unified identification package. Some schools use standard light catalogue access protocols, others run single-point login based on statements, and others simply self-developed interfaces, which are not necessarily complete. The billing system has to be connected to at least three things: students' only number, name, department or building. Without the faculty and building, it is impossible to get a bill of buildings and share the costs with the college. So the first step in matching is not to write codes, but to check the list of fields that the certification system can give you.
Keep your accounts in sync.
Some options allow the system to take full accounts and listen to them, but 10,000 students are under pressure for a full amount of time each time, network and database, and the billing system fails once it is temporarily maintained. More robustly, it is an event-driven approach: when students register, resume, drop out, the certification system pushes in one message, and the costing system increases only.
Password and cipher process to be closed.
The change of passwords for students must be done at the level of uniform identification, where the billing system does not have a code or provide a password entry. This is a dead letter. We've seen the opposite: the billing system itself has a copy of the code, which is then dragged into storage and the students complain about leaks from the school. The correct course is to send it only as a confirmation transmission, to send the verification to the school for a unified identity, and to get a time-bound certificate.
We need to combine the billing number and online account number.
There is also a frequently overlooked point: the number of accounts that students use to access the Internet and the billing account for charging them, preferably the same. If you have to register another mobile phone account on the Internet, it is easy for students to mix up and double their passenger service directly. It is better to use the charge system as a primary account, with a charge-back set or payment-weed, but without creating an identity. In this way, students can access the Internet on certified pages, enter a code for the school number, and the balances and bills are posted under a school number, checking, rebuffing, transferring money.
The school-leaving number is closed.
Graduates and drop-outs are a crucial moment in determining the availability of the connection. Ideally, students in school uniform accreditation will be sent on that day to the billing system, automatically disentangled from Internet access, frozen balances, and created pending lists. But, often in actual projects, because of delays or missing field pushers, people are missing or left unclaimed. We suggest that we do an exercise before going online with a real collection of school leaving data, confirming that the chain is open from state change to fee-side stop, freeze, and exit list.
The docking failure needs a demotion.
The good match will also be protected against a one-hand certification system. We usually ask the billing system to keep a local cache of vouchers that allows students to access the network for a few minutes while the uniform identification is temporarily unavailable, rather than immediately disconnecting the entire dormitory. This cache is time-bound and rechecked as soon as it is restored. It is not intended to bypass certification but to avoid single troubles that drag down the building.
The matching documents are to be left behind by the school itself.
Once the interface is done, the interface documents, field definitions, and push formats must be left to the school itself, not just in the manufacturer's head. We have seen the vendor change, the details of the match are not explained, and the next upgrade has to come back. The document is the key to avoiding being tied to the school, and it is the basis for our own follow-up on the question.
Run through the test environment and then produce.
Before officially going online, it is important to run the entire chain in a series of real accounts and buildings before testing environments. The environment exposes problems such as field absence, delay in pushing, code-coupling, and does not affect real students. We are used to writing tests into implementation plans as prefixing conditions for online, preferring two days of testing and not using the Internet to match thousands of students.