Why fill out a declaration with no prize money seriously?
Yesterday, a client in the auto industry posted a screenshot of a notice in the group and asked, "Does this HarmonyOS + solicitation have any money?"
I read through the November 19 notice from the Guangzhou Municipal Bureau of Industry and Information Technology, and there is not a single funding subsidy clause in the entire text. What it does is solicit two types of items: one is “HarmonyOS+” typical application scenarios, aimed at scenarios that have not yet been built but have a clear intention to build; the other is “HarmonyOS+” typical cases, aimed at practical results that have already been built and put into operation. After the latter is selected, it enters the “typical case list” and the reserve pool for subsequent policy support and benchmark demonstration projects.
Note this wording—reserve pool. It is not “priority access to subsidies,” nor “giving rewards.” To be honest, many companies swipe away as soon as they see there is no bonus, and I can understand that. But those of us doing implementation see it differently: an application form asks you to fill in clearly, column by column, the system version, quantifiable results, and which data you plan to open up; these fields themselves are a ready-made digital inventory of your assets. If you cannot fill it out smoothly now, it means your ledgers are in arrears; if you can fill it out smoothly, then when a policy actually lands someday, the materials are ready.
The application window opens at 09:00 on November 20; the deadline for enterprises' first submission is 18:00 on December 9, and those returned for revision must complete submission by 18:00 on December 11. The manufacturing sector is the first of the five categories this time, specifically naming HarmonyOS-based applications for production equipment, control systems, and management platforms in automotive, electronics, consumer goods, and equipment manufacturing, as well as smart factories and smart workshops.
In the "version number" column, the key question is whether the device cards are granular enough
The case-type application form has a field called “Version Information”; the original text requires: the name and version number of the HarmonyOS-family operating system used (including OpenHarmony commercial distributions and industry distributions).
There is a pitfall here. We have encountered companies writing "adopted HarmonyOS" in similar applications—five characters, which looks fine, but in fact this field is as good as unfilled. What it requires is the name plus version number, whether it is a commercial distribution or an industry distribution, and exactly which version. This is not wordplay; the reviewing authority wants something that can be verified.
Pull back a level: where should this version number be stored? In Odoo, it should not be a descriptive sentence; it should be a field on the equipment card. For a CNC machine, a production line's control system, or an edge gateway, if you want to report a “HarmonyOS-based application,” the card must have at least these columns: control method, communication protocol, operating system and version, and commissioning date. When we build equipment master data for customers, many factories initially record only the original value and depreciation period—that is a financial basis, not a basis that can be used for declaration. The two tables need to align, and the gap between them is exactly these columns.
In the scenario-based application form, there is an even more interesting section called "Resources to Be Opened," which requires listing the data, equipment, business systems, funds, and other resources to be opened to external partners, as well as the opening methods. This section is essentially a checklist: which business systems (which MES modules, which ERP tables), which equipment (which units, what protocols), which data (process parameters, quality inspection records, or work order flow), and in what way they will be opened (interfaces, exports, or on-site read access). If you cannot even clearly explain which of your own systems can be connected, then for this section you will have to go back to the office and dig through the configuration lists.
I’m not saying the equipment management module has to go fully live tomorrow. Quite the opposite—for this round of reporting, you can absolutely use a no-code approach: add four custom columns to the existing equipment ledger and fill in the version number and commissioning date first. Don’t rush to implement a big system. Recording the facts first is more useful than putting up a beautiful data dashboard.
“Quantifiable outcomes” require before-and-after comparison, not adjectives
In the “Achievements and Highlights” section of the case application form, specific achievements, distinctive highlights, and impacts are required to be written item by item; the wording emphasizes highlighting quantifiable direct benefits, and it is best to provide before-and-after effect comparisons; if there are AI-integrated applications, they can be highlighted. The original text uses the phrase “quantifiable direct economic benefits”; for exactly which categories of benefits are listed, simply read the notice attachment word for word—this is not the place to copy them all out on its behalf.
To emphasize once again, this is a call with no prize money, but its requirement for "quantifiability" is not vague at all. Here I must add an honest caveat: the original policy text does not provide a prescribed template for quantified outcomes, nor does it say which type of numbers must be used. Therefore, the data sourcing approach below is our project practice, not an official requirement—as of today, there is no public explanation of what measurement standard the reviewers will ultimately accept.
Our approach is this: for the numbers used in effect comparisons, we try as much as possible to take them from the system's business documents rather than copying them from reporting PPTs. For example, for the changeover time of a production line before and after HarmonyOS transformation, the work order table (mrp.workorder) contains start and completion timestamps, so we can calculate it by taking one statistical interval before and one after; for the first-pass yield of a quality inspection stage, take the qualified count and total count from the quality inspection records; for the change in utilization rate after equipment networking, take it from the on/off records of points in the collection gateway. These numbers share one thing in common—they were recorded at the time, not recalled afterward.
Here is a pitfall we actually ran into. A client took part in another type of case collection and wrote “efficiency significantly improved” in the results column, but the submission was returned for supplementary materials. When they scrambled to supplement it, no one remembered the baseline figures from before the transformation anymore, so they could only back-calculate from one month of post-transformation data; the definitions before and after didn't match, and in the end even they didn't dare trust that comparison. The lesson is straightforward: baselines must be recorded before changes are made, and recorded in the system with timestamps—not saved in someone's WeChat favorites.
Just to clarify one point: the provincial solicitation for smart home interoperability cases dated November 10 (Yue Gongxin Xiaofei Han [2026] No. 129, which we wrote about in our 27th article) is not the same thing as this one. That one is at the provincial level, aimed at interoperability products and scenarios, and involves evidence of adaptation against the draft mandatory national standard; this one is at the Guangzhou municipal level and is for inclusion of cases in the OpenHarmony system and scenario case repository. The administrative level, the subject of evidence, and the fields to be filled in are all different, so don't mix up the materials for the two.
Three things you can do this week
First, determine which category you are applying for. The criteria are very specific: if you already have results based on OpenHarmony that are up and running and in operation, apply for the case category (you need to submit the version number and quantifiable results); if you only have the intention to build and have not yet built it, apply for the scenario category (you need to submit the resources planned to be opened and the construction requirements). If both apply, there is no limit on the application type or number for the same organization, and you can apply separately. Complete the first submission before 18:00 on December 9.
Second, spend an hour going through the equipment cards. Criteria: randomly select three designated pieces of production and manufacturing equipment (automotive, electronics, consumer goods, and equipment industries all count), and check whether the cards have these three columns: operating system version, commissioning date, and communication protocol. Fill in any missing ones first, even if you use custom fields. This step does not require waiting for any system changes.
Third, define the data measurement basis for a baseline number. Pick a metric you plan to write into “results” (changeover time, first-pass yield, utilization rate—any will do), and today record its current value and statistical interval in the table. The criterion is: this number can be found from some timestamped business document. If it cannot be found, switch to one that can. Before December 9, take the same measurement basis again after the improvement, and the two numbers will naturally emerge.
There was no money in that notice. But the positioning as a reserve pool is right there—next time funding becomes available, the list will most likely be chosen from the existing case list. Will there still be time to fill in the ledger by then?
