Those who have purchased the Authentication & Billing system several rounds know that the technical parameters in the solicitation documents appear to be met by one, but when the system reaches the scene, there are always a few cases where it cannot run or achieve publicity. It is no coincidence that some of these types of parameters are common in the industry and deserve special attention when drafting the tender documents or evaluating bids.
The first category is the simultaneous issuance of certification capabilities.. The solicitation documents are often available"N-per second for authentication"The parameters require, but the number is measured under what conditions, and few manufacturers have come to a clear view. Portal certification processing capacity is influenced by multiple factors such as server hardware configuration, database response speed, network delay, etc. The numbers that run out in the manufacturer’s own test environment may differ significantly from the performance in the actual deployment environment.
The second is"Support N-maker equipment"Compatibility parametersThe support for mainstream producers like China, Central H3C, Sharp and Cisco sounds extensive. But support means whole series of products or partial models. What is the counterpart? Have you actually tested it? There are a lot of moisture in this. Some manufacturers have different performances on RADIFUS under different solid versions."Support to mainstream manufacturers"。
The third category is high availability and resilience.。"Support dual heater"In many solicitation documents, it is necessary to do so in a very different way. Some systems have two-beds that are only prepped for main switching, which will be interrupted by several seconds or even longer of authentication; some have met the meeting synchronizing and the online user does not turn off after the switch; and others call them ""Hot"In these cases, the differences in user experience are significant. The solicitations should be clearly requested: whether online users need to re-validate after master switching, how many seconds before switching and provide acceptance records for similar items.
The fourth category is the expansionary parameters of the system。"Support horizontal expansion""Support distributed deployment"Such descriptions are found in almost every manufacturer’s product document, but what is the expanded operation? Do you need to be out of business? How do data consistency ensure after expansion? Online users will not be affected when new nodes are added? These details are usually not written in solicitation documents and only when there is a real need for extension will it become much more complex than expected.
The fifth category is the ability to retain a log.The public security filing requires that the user log be kept for not less than 180 days, which is almost all the NATSHEL_AUTH_BILLING bid requirements. The question is whether the fields retained by the log are complete (including user identification, terminal MAC, access location, down-to-down time, traffic). Can the log search and export as required? What is the strategy after the log is fully stored? These details determine whether the log will be used in actual compliance checks, rather than just whether there is a single one in the system. If the log field is incomplete or the query function is inadequate, compliance will be problematic when auditing.
The sixth category is the SLA commitment to response time.. Technical services and after-sale support are often available"7×24-hour response.""Remote support response time does not exceed Nh"The response here is whether to connect the telephone or solve the problem. If only to connect the phone is a response, the substantive value of this commitment is limited. It should require that a distinction be made between the response time for different levels of failure and the resolution time, such as an all-network certification break being an emergency, requiring remote N intervention within minutes and normal N recovery within hours.
The core of the solicitation parameters is to be verifiable and quantifiable, avoiding vague descriptions leaving too much room for the manufacturer to explain. A field presentation of the priority parameters at the evaluation stage or a request for a receiving and inspection report on the true case is an effective means of reducing moisture.
There's another parameter."Upgrade service guarantee"The solicitation documents usually require vendors to provide free upgrade support for several years, but what is the scope of the upgrade? Are there only bug fixes or new functionalities? Do you need to stop the upgrade? How long does the shutdown take? How safe the data are during the upgrade process? These details determine actual experience at the end of the user's side over the next few years, not just a sentence."3-year upgrade service"It's covered.
The last point is the consistency of bid parameters with acceptance criteria. Many projects have a full technical basis for solicitation, but the acceptance phase test project has only several basic functions and many of them do not have an appropriate intake. This gives the manufacturer space to operate——The solicitation is accompanied by a commitment to monitor the receipt and inspection, and any subsequent problems become contentious. It is recommended that, when the solicitation documents are drafted, the sample for the simultaneous design of the acceptance and inspection test be matched with the test scene and acceptance pass criteria for each key parameter, which will allow the tender parameters and acceptance standards to form a complete closed link.