FAC certification Russia: certificate or declaration for network equipment

FAC certification Russia is the conformity document for equipment that attaches to the public communications network in Russia: a certificate from a body in the communications certification system, or a declaration registered with the federal telecom regulator. The basis is Article 41 of Federal Law No. 126-FZ On Communications, and a Government list names the classes that must take the certificate. The document is valid in Russia only. It does not replace the EAC declaration under TR CU 020/2011 and TR CU 004/2011, and it is separate from the radio frequency conclusion and the encryption notification. A Russian legal entity files it, and a certificate runs for one year or three years depending on the scheme.

Which equipment needs an FAC certificate, and which takes a declaration?

Article 41 makes conformity confirmation mandatory for every communications facility used in the public network, and for equipment in a private or special-purpose network at the point where it connects to the public one. The law itself names the classes that must be certified. Everything else in scope takes a declaration, so the first job on any file is to place each model on the right side of that line.

The certificate side, as the law lists it: switching systems, digital transmission systems, control and monitoring systems, equipment that records the volume of services on public networks, terminal equipment whose failure can disturb the network, radio-electronic communications facilities, and lawful-intercept equipment including its software. Base stations, exchanges and operator-grade transport gear land here. Subscriber terminals, small business routers and structured cabling for the public network are in scope too, and most of them go by declaration.

The argument we have most often is over a router with WAN ports. Sold to an enterprise as a subscriber terminal it declares; the same hardware sold to an operator as transmission equipment certifies. The body decides against the Government list, and we put the question to it before quoting, because the answer changes the cost by one full round of accredited testing and adds a document that expires.

How is the FAC document different from EAC, the RFC conclusion and the encryption notification?

Four documents answer four questions. EAC says the product is safe and electromagnetically compatible under the technical regulations, and it is valid across the Eurasian Economic Union. The FAC document says the equipment may attach to the Russian public network, and it is Russian only. The RFC conclusion clears radio spectrum at import. The notification covers cryptography, union-wide.

So a base station with Wi-Fi backhaul needs the EAC declaration under TR CU 020/2011 on electromagnetic compatibility and TR CU 004/2011 on low-voltage equipment (see the Russian EAC page), the FAC certificate for attachment, the RFC conclusion for the radio, and the encryption notification for the link encryption. None of the four is satisfied by any of the others. A Kazakh or Belarusian operator will not accept the FAC document either: it is an instrument of a Russian federal law and it has no standing outside Russia.

We open the three Russian files in the same week. They draw on one technical description and one set of samples, and the last file to close sets the ship date, which is why the 4 to 10 weeks quoted for Russian telecom clearances is a range for all three running side by side. Filing FAC first and the RFC conclusion after it, because the second seemed to depend on the first, is the sequencing mistake that turns ten weeks into twenty.

Who can apply for FAC certification in Russia, and how long does the document last?

The applicant is a Russian legal entity: the importer, a local subsidiary, or a representative the manufacturer appoints under contract. The law lets the manufacturer or the seller present equipment for certification, but a foreign company cannot hold the document in its own name, and the register entry is tied to the applicant, so the choice of applicant is a choice about who controls the product in Russia later.

Article 42 sets the statutory clock. The application goes to the certification body with a technical description in Russian detailed enough to identify the equipment and its parameters; the body has thirty days to consider it and thirty days after the test reports arrive to decide. A certificate is issued for one year or for three years depending on the scheme. A declaration under Article 43 is signed by the applicant on its own evidence plus accredited-laboratory reports, registered by the federal telecom regulator within three days, and kept with its evidence for the term plus three years after it ends.

A product family is filed as one type when the models share the platform and the interfaces; a model with a different radio module or a new WAN interface is a different type and a new file. Firmware is the softer case: Article 41 lets the manufacturer respond to a software change with a declaration that refers back to the earlier certificate, so tell us the firmware roadmap at the start and the change lands as paperwork instead of a repeat of the tests. The Russian technical description is the item that slows most files, because a translator without telecom vocabulary produces a document the body sends back.

The register entry is what gets checked. The operator that will attach the equipment asks for it before installation, and a customs broker asks for it next to the RFC conclusion. A certificate that has quietly reached the end of its one-year term still looks valid on paper, and it is the operator, at the point of attachment, who finds out that it is not.

The FAC document next to the documents it is confused with

An operator-grade router or a base station carries the first, third, fourth and fifth rows. The first two rows never apply to the same model at once: the Government list decides which one.