Configuration is also engineering work that needs to be delivered
According to page 2 of Yusys Technology’s Investor Relations Activity Record No. 2026-007, the FDE team is responsible for communication, configuration and troubleshooting, and will hand over prompt words, rules and other adjustments to the delivery team for processing. The statement about bank project verification comes from the company's own disclosure, and no customer acceptance data is provided for review by ChinaOPC. This article studies the division of labor and does not discuss its security value.
The question worth exploring here is: when the field engineer can adjust the system behavior, how to let the customer know what has been changed, on what basis, and who will take over if there is a problem. The following process is an original suggestion from ChinaOPC. It is neither an internal operation manual of Yusys Technology nor a general requirement for all financial institutions.
A modification first corresponds to a specific problem
A change order can be used to record problem examples, the results expected by business personnel, the current version and the location of modifications. For example, internal data retrieval often cannot find updated documents. You should first determine whether the data has entered the index, rather than continuously lengthening the prompt words. Otherwise, a data update issue may be masked as a language issue, making it difficult to locate later.
Divide the content to be modified into data, business rules, prompt words and procedures. Explain each time what has changed, which tests need to be rerun, and who has the authority to confirm the business implications. The classification here is for troubleshooting and cannot be used to bypass the customer's existing technical and business approvals.
What permissions does the delivery team need?
- Review: Reproduce input and results within permitted limits to avoid duplicating full data for troubleshooting.
- Edit: Limit adjustable configuration items, record operator and time.
- Test: Compare the fixed samples before and after modification in the agreed environment.
- Release: Authorized personnel will confirm the activation scope and save the version correspondence.
Being able to edit on-site does not mean that on-site personnel can directly approve it for online use. Small teams can have multiple technical steps completed by the same engineer, but business effects, data usage and release authorization still require clear confirmation from the customer. How to divide the authority should be agreed upon based on the specific tasks and the customer environment.
Keep the old version and why it needs to be changed
In addition to old configuration files, corresponding profile versions, test results, known limitations, and interim measures expiry dates should also be retained. Restoring the old prompt words may not restore the old index or undo external writes, so it is necessary to explain in advance what changes can be covered by the rollback. If it involves messages that have been sent or business records that have been modified, separate follow-up handling measures should be prepared.
For delivery enterprises, the investigation process can be organized into a desensitized problem library: symptoms, confirmation basis, final cause, resolution level and review results. Only troubleshooting methods are reused, and customer private information and exclusive rules are not reused by default. Only in this way can experience accumulation and customer boundaries be clear at the same time.
The source records only describe how the company describes its FDE practices and do not disclose the quotes, processing times, and accuracy of the examples in this article. Whether a similar division of labor is adopted should be verified by customers and service teams in actual tasks; Yusys Technology is not classified as a small OPC company because it is a research object.
Extended reading: FDE deployment and permissions; Project delivery evidence chain.