Skip to content
Interface language: English
Oriens / Signal

A charger from China and a Polish operator: sharing a protocol acronym is not the same as working together

How to read an OCPP claim, a public certificate and the operator system's role before discussing a specific partnership with a Chinese charger manufacturer.

Article language: English

A woman in a red dress and light outer garment stands beside a stone-edged pool in a high-ceilinged hall.
In this article

Imagine a Polish company managing charging points in conversation with a Chinese equipment manufacturer. The supplier shows the acronym OCPP on a slide. The operator uses a system that also supports OCPP. The meeting could end with the pleasant conclusion that the main issue is settled. In fact, there is only now a basis for a more precise question: what is to work together, in which version and with which system?

The device, its software and the management system are separate elements of the offer. The Polish company might buy a charger, seek a partner supplying a complete solution or develop its own software for existing equipment. In each case public protocol information matters, but it does not describe the whole relationship. It must be connected to the right product and the operator's task.

Researching sources helps prepare that conversation. It does not replace integration trials or an assessment of electrical safety, installation and requirements for a particular use. Here we consider what public material can establish and what questions arise from its limits. An investment decision and technical design need their own evidence and responsible people.

First establish which side of the connection you are on

The Open Charge Alliance's official FAQ defines OCPP as an open communication protocol between a charging station and a charging-station management system. This puts the acronym in the right place. It is not the name of an entire service operation or proof that any infrastructure component works with every other one.

In our fictional example, the operator wants its own system to receive information about the device's status. The manufacturer may present a device together with its own platform. Both sides can say "charger management" while meaning different delivery boundaries. Before comparing claims, they should identify who supplies the equipment, who supplies the management software and who is responsible for connecting them.

This distinction affects a list of potential partners. An equipment manufacturer does not necessarily provide the operator's whole service. A platform provider may handle selected integrations without making hardware. An organisation assembling the solution may need information from both sides. A corporate group's public website does not automatically identify which of its entities will take part in a particular partnership.

In an initial list, record the organisation's role and the basis for identifying it alongside the product name. "Has a charger in its catalogue" and "offers a connection between this model and an external system" are different pieces of information. If the second rests only on a general claim of openness, it remains a question. It should not become a confirmed feature simply because it fits the Polish company's plan.

A comparison with servicing a machine from China in Poland (in Polish) is useful. Delivering the equipment alone does not describe how a later service request will be handled. A charger adds a relationship with another party's software. Asking about parts or service presence does not replace establishing who will investigate a problem at the boundary between the device and the system.

A certificate has a product name and version of its own

The public OCA.0016.0661.CS certificate for Artemis concerns OCPP 1.6 and identifies a charging station, software version 1.0.7b1.0.8 and certification date 22 January 2024. The document limits its application to the designated product and is not a general guarantee of its quality. The name and version are part of the evidence, not decorative fine print.

This is an example of how to read a specific public document. It does not confirm that any current StarCharge offer is the same product in the same configuration. If a sales conversation introduces a different model name, clarify its relationship to the document. A similar name is not a basis for filling in a missing connection yourself.

In a hypothetical conversation, the Polish company may receive a certificate alongside a presentation of a new variant. Ask which exact product will be delivered and which document describes its implementation. The answer should connect the designations, not merely assure you that "the whole series works similarly". If the manufacturer identifies another document, that becomes further material to read and assess.

Do not extend evidence beyond what it describes. Tested protocol implementation conformance is not the same question as installation safety, operation in a particular car park or a partner's ability to handle service requests. Each has different materials and appropriate assessors. Separating them avoids a conversation in which one word, "certified", has to carry every unknown at once.

The public certificate also names Starcharge Energy Pte. Ltd. Keep that name beside the document designation when preparing a contact list. Do not automatically replace it with the brand name on a presentation. The person assessing the material should see who is named as certificate holder and who presents the partnership offer. A logo alone does not explain the relationship among all entities that may appear in the discussion.

A hypothetical comparison can therefore keep separate entries for the contact entity, designation of the product to be delivered and document relating to the implementation. If an intermediary passes on another company's certificate, ask how its offer relates to that product. Clarify the intermediary's role rather than assigning it all of the manufacturer's characteristics and obligations because of an attachment.

This record can begin partner verification in China (in Polish), but does not complete it. Public documents help establish names and questions. Readiness for a technical discussion, scope of service offered and the actual role of a local entity need separate confirmation. Distinguish those findings in the report so the person making the next contact knows the basis for each item.

Use similar discipline with the scope of a laboratory's accreditation in China (in Polish). Connect the institution, method, subject and document. This compares how evidence is used. It does not mean laboratory accreditation and an OCPP certificate prove the same thing or replace each other.

Aeneia conceptual photography

"Ready" does not remove "to be determined"

On the StarCharge Artemis V2 product page, the integration description lists OCPP 1.6J and "OCPP2.0 ready". The parameters table for backend communication, however, lists OCPP 1.6J and OCPP 2.0 marked "TBD". Record both indications instead of converting them into independently confirmed availability of 2.0.

That difference is a good question for the supplier. What does readiness mean for the variant offered? What is available now, and what needs further agreement? Which documentation describes the version the recipient will receive? The page alone does not establish whether the cause is the development stage, an outdated table or a different division of variants. That is precisely what remains unknown.

The Polish company must preserve that uncertainty in subsequent material. If a researcher shortens the row to "supports OCPP 2.0", the next participant will not see the qualification. An assumption can then enter an enquiry, offer comparison and trial schedule as an alleged fact. The error need not arise in translating a Chinese document. Over-smoothing an English product page is enough.

Instead, record the precise question and the source that prompted it. A working comparison can separate confirmed document content from the explanation expected from the manufacturer. There is no need to invent a long list of possible faults. First, the parties need to agree on the subject of the discussion. Technical specialists can then establish the appropriate scope of testing.

When preparing communication about an Asian product for a Polish audience (in Polish), retain the meaning of status words too. "Planned", "ready to extend" and "available in the stated version" can lead to different decisions. Concise Polish should preserve the difference. Shortening a sentence is not a good reason to remove a condition.

A trial concerns a specific relationship, and a report needs a recipient

Suppose that after clarifying the labels the parties want to test the device with the operator's system. Research should now give way to a technical agreement led by the appropriate people. The Polish company should establish the model and version entering the trial, who supplies the system and how the result will be recorded. A general claim of interoperability, the ability of components to work together, is not enough.

In this example, start with an ordinary operator's question: after an agreed action, will its team receive information allowing it to continue the service? The responsible technical people must agree the specific events, conditions and criteria. A market researcher should not replace them with a list of arbitrary commands or suggest that a manufacturer's remote demonstration covers the entire Polish service model.

When a result is unclear, do not immediately assign responsibility to one side. The equipment and software teams may need an agreed basis for reproducing the event. In the partnership discussion establish who receives a report, who gathers information and who investigates the discrepancy with the other party. Otherwise the client may receive two impeccably written links to someone else's support.

Ask separately about later changes. If one side changes its software, the others need to know how they will learn the scope and what needs rechecking. We are not assuming every update causes a problem. The aim is to keep visible the version on which the earlier result was based. Evidence without a configuration is hard to use in the next service request.

The right partner depends on the boundary of the offer

Supplier comparisons should concern the same task for the Polish company. One offer may cover equipment, another equipment with its own platform, and a third a defined integration job. Comparing them only by unit price hides different scopes. Before comparing terms, identify what remains with the operator and its existing suppliers.

In the Chinese photovoltaic value chain (in Polish), too, components, equipment and a whole installation must be distinguished. Liquid cooling in data centres (in Polish) shows the boundary between IT equipment and building infrastructure. These comparisons do not transfer standards or requirements between sectors. They help name what the supplier is actually being asked to partner on.

A claim about a wider energy ecosystem also needs a specific use. Second-life batteries and recycling in Korea (in Polish) describe separate tasks and entities. Putting these areas in one presentation does not mean one document or one contact can answer every question. Partnership scope should follow the actual proposal.

Aeneia Oriens can help identify Chinese manufacturers, public material and partner roles for a specified cooperation model. Start with the Polish recipient, the element offered and the question the contact should resolve. The company list then serves a concrete discussion about use and scope.

Aeneia Oriens

Before discussing chargers from China, organise manufacturers, product designations and public material relevant to the planned cooperation with a Polish operator.

Identify partners and the scope of an offer from China

After this preparation, the operator should be able to identify the document, the variant offered and the right person for the next question. If something has not been confirmed, keep that gap in the plan. A shared acronym on a slide can start the conversation. What follows depends on whether both sides mean the same task and configuration by it.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear