972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Government and regulatory

EDI 195 Federal Communications Commission (FCC) License Application

The X12 document used between applicants, frequency coordinators and licensing authorities to submit and acknowledge license applications.

Sent by
Applicant or frequency coordinator
Received by
Licensing authority or coordinator
Standard
ANSI ASC X12

What is an EDI 195?

The EDI 195 Federal Communications Commission (FCC) License Application is the ANSI X12 transaction set that provides a uniform medium between applicants, coordinators and license granting authorities for submitting and acknowledging new applications and related filings.

Radio licenses, for example for land mobile systems, often require frequency coordination before the application reaches the regulator. A common electronic format lets coordinators pass applications on without rekeying. The regulator now operates its own electronic filing systems, so current formats should be confirmed.

How the EDI 195 worksDiagram of the EDI 195 Federal Communications Commission (FCC) License Application. Applicant or frequency coordinator sends it to licensing authority or coordinator. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment). 4 optional loops are listed by their first segment.How the EDI 195 worksFederal Communications Commission (FCC) License Application: who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 195SENDERApplicant or frequencycoordinatorRECEIVERLicensing authority orcoordinator997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code LAGS … GETransaction set 195ST … SEHEADINGBGNBeginning Segment+ 3 optional loops, starting with:CRCAMTN1DETAIL+ 1 optional loop, starting with:PO1Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 195. Your trading partner's implementation guide adds its own requirements.
How the EDI 195 worksDiagram of the EDI 195 Federal Communications Commission (FCC) License Application. Applicant or frequency coordinator sends it to licensing authority or coordinator. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment). 4 optional loops are listed by their first segment.How the EDI 195 worksFederal Communications Commission (FCC)License Application: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 195SENDERApplicant orfrequencycoordinatorRECEIVERLicensingauthority orcoordinator997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code LA (GS … GE)Transaction set 195 (ST … SE)HEADINGBGNBeginning Segment+ 3 optional loops, starting with:CRCAMTN1DETAIL+ 1 optional loop, starting with:PO1Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 195. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 195, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 195 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Submitting radio license applications
  • Passing coordinated applications to the regulator
  • Receiving acknowledgments of applications

Where it fits in the document flow

This document 195 Federal Communications Commission (FCC) License Application
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 195 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • CRC
  • AMT
  • N1
  • REF
  • LM
  • LQ
  • PO1
  • MEA
  • SE

Practical example

The 195 in practice

A utility needs licenses for a new two-way radio system. A frequency coordinator selects suitable frequencies and forwards the application to the licensing authority. The authority acknowledges receipt and later grants the licenses.

Implementation

Implementation considerations for the 195

  • Confirm the regulator's current filing systems and formats.
  • Complete frequency coordination before filing.
  • Track each application through to grant.
  • Keep license records and their renewal dates.

How ECOM helps

Automate the 195 with ECOM

Industry

Telecom and Media

Equipment supply chains, service billing and partner data exchange for telecom and media companies.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related government and regulatory documents

All 29 government and regulatory documents

Need help with the EDI 195?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us