IEC TR 61967-1-1:2015

IEC TR 61967-1-1 ®
Edition 2.0 2015-08
TECHNICAL
REPORT
colour
inside
Integrated circuits – Measurement of electromagnetic emissions –
Part 1-1: General conditions and definitions – Near-field scan data exchange
format
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing more than 30 000 terms and
Technical Specifications, Technical Reports and other definitions in English and French, with equivalent terms in 15
documents. Available for PC, Mac OS, Android Tablets and additional languages. Also known as the International
iPad. Electrotechnical Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a More than 60 000 electrotechnical terminology entries in
variety of criteria (reference number, text, technical English and French extracted from the Terms and Definitions
committee,…). It also gives information on projects, replaced clause of IEC publications issued since 2002. Some entries
and withdrawn publications. have been collected from earlier publications of IEC TC 37,

77, 86 and CISPR.
IEC Just Published - webstore.iec.ch/justpublished

Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
IEC TR 61967-1-1 ®
Edition 2.0 2015-08
TECHNICAL
REPORT
colour
inside
Integrated circuits – Measurement of electromagnetic emissions –

Part 1-1: General conditions and definitions – Near-field scan data exchange

format
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 31.200 ISBN 978-2-8322-2880-7

– 2 – IEC TR 61967-1-1:2015 © IEC 2015
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
2 Normative references . 8
3 Terms, definitions and abbreviations . 8
3.1 Terms and definitions . 8
3.2 Abbreviations . 9
4 General syntax rules and guidelines . 9
4.1 General . 9
4.2 XML requirements . 9
4.2.1 General . 9
4.2.2 XML declaration . 9
4.2.3 XML elements . 9
4.2.4 Root element . 10
4.2.5 Comments . 10
4.2.6 Line terminations . 10
4.2.7 Element hierarchy . 10
4.3 Keyword requirements . 11
4.3.1 General . 11
4.3.2 Keyword characters . 11
4.3.3 Keyword syntax . 11
4.3.4 Root element keywords . 12
4.4 File structure . 12
4.4.1 General . 12
4.4.2 File names . 12
4.4.3 File paths . 12
4.4.4 Single XML file . 12
4.4.5 Multiple XML files . 12
4.4.6 Separate data files . 13
4.4.7 Additional files . 13
4.4.8 File compression . 13
4.5 Values . 14
4.5.1 General . 14
4.5.2 Numerical value syntax . 15
4.5.3 Numerical value with units syntax . 15
4.5.4 Text string . 15
4.5.5 Valid units . 15
4.6 Coordinate systems . 16
4.6.1 General . 16
4.6.2 Cartesian coordinate system . 16
4.6.3 Cylindrical coordinate system . 17
4.6.4 Spherical coordinate system . 18
4.6.5 Coordinate offsets . 19
4.6.6 Image coordinates . 20
4.7 Field type and orientation . 21
4.8 Data syntax . 24

4.8.1 General . 24
4.8.2 Data arrangement . 24
4.8.3 Data with coordinate information . 25
4.8.4 Data without coordinate information . 25
4.8.5 Data format . 26
4.8.6 Data notation . 26
4.9 Probe factor . 28
4.10 Images . 30
4.10.1 General . 30
4.10.2 Image file types . 30
4.10.3 Image file name and path . 30
4.11 3D objects . 30
4.11.1 General . 30
4.11.2 3D object file types . 30
4.11.3 3D object file name and path . 30
4.11.4 3D map object file name and path . 30
Annex A (informative) Example files . 31
A.1 Minimum default file . 31
A.1.1 Example file . 31
A.1.2 Default value description . 31
A.2 File with magnitude and angle data . 32
A.2.1 Example file . 32
A.2.2 Default value description . 32
A.3 File with field azimuth and zenith orientation . 33
A.3.1 Example file . 33
A.3.2 Default value description . 33
A.4 File with optimised field azimuth orientation . 34
A.4.1 Example file . 34
A.4.2 Default value description . 34
A.5 File with piece-wise linear time domain data in a separate binary file . 35
A.5.1 Example file . 35
A.5.2 Default value description . 35
A.6 File without coordinate information . 35
A.6.1 Example file . 35
A.6.2 Default value description . 36
A.7 File for immunity scan with multiple criteria . 36
A.7.1 Example file . 36
A.7.2 Default value description . 37
A.8 File for emission scan with probe factor . 38
A.8.1 Example file . 38
A.8.2 Default value description . 38
A.9 File for immunity scan with probe factor . 39
A.9.1 Example file . 39
A.9.2 Default value description . 39
A.10 File with image and 3D image . 40
A.10.1 Example file . 40
A.10.2 Default value description . 40
A.11 File with plane rotation . 41
A.12 Emission scan in several XML files . 42

– 4 – IEC TR 61967-1-1:2015 © IEC 2015
Annex B (normative) Valid keywords . 44
B.1 General . 44
B.2 File header keywords . 44
B.3 Global keywords . 44
B.4 Component section keywords . 44
B.5 Setup section keywords . 45
B.6 Probe section keywords . 46
B.7 Data section keywords . 46
Annex C (normative) Keyword usage rules . 49
Bibliography . 63

Figure 1 – Multiple XML files . 13
Figure 2 – XML files with data files . 14
Figure 3 – Additional files . 14
Figure 4 – Right-hand Cartesian coordinate system . 17
Figure 5 – Left-hand Cartesian coordinate system . 17
Figure 6 – Cylindrical coordinate system . 18
Figure 7 – Spherical coordinate system . 19
Figure 8 – Offsets and image positioning (right-hand Cartesian) . 20
Figure 9 – Offsets and image positioning (left-hand Cartesian) . 21
Figure 11 – Field orientation – Right-hand Cartesian coordinate system . 22
Figure 12 – Field orientation – Left-hand Cartesian coordinate system . 22
Figure 13 – Field orientation – Cylindrical coordinate system . 23
Figure 14 – Field orientation – Spherical coordinate system. 23
Figure A 1 – Example .obj file . 40
Figure A.2 – Coordinates in DUT reference plane . 41
Figure A.3 – Coordinates in the measurement reference plane . 42

Table 1 – Valid logarithmic units . 16
Table 2 – Relationship between azimuth, zenith angles and field component . 24
Table 3 – Permitted values for the keyword: Coordinates . 25
Table 4 – Order of measurement points when coordinates are not included . 27
Table 5 – Probe factor linear units . 29
Table 6 – Probe factor logarithmic units . 29
Table A.1 – Data matrix . 36
Table A.2 – Magnetic field strength for emission . 38
Table A.3 – Magnetic field strength for immunity . 39
Table C.1 – File header keywords . 49
Table C.2 – Global keywords . 50
Table C.3 – Component section keywords . 51
Table C.4 – Setup section keywords . 53
Table C.5 – Probe section keywords . 56
Table C.6 – Data section keywords . 58

INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INTEGRATED CIRCUITS –
MEASUREMENT OF ELECTROMAGNETIC EMISSIONS –

Part 1-1: General conditions and definitions –
Near-field scan data exchange format

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
The main task of IEC technical committees is to prepare International Standards. However, a
technical committee may propose the publication of a technical report when it has collected
data of a different kind from that which is normally published as an International Standard, for
example "state of the art".
IEC TR 61967-1-1, which is a technical report, has been prepared by subcommittee 47A:
Integrated circuits, of IEC technical committee 47: Semiconductor devices.
This second edition cancels and replaces the first edition published in 2010. This edition
constitutes a technical revision.
This edition includes the following significant changes with respect to the previous edition:
• Addition of:
– 6 – IEC TR 61967-1-1:2015 © IEC 2015
– 4.11 3D objects;
– Binary data files;
– Piece-wise linear time domain and frequency domain data;
– Vectors permitting rotation and offset of measurement and DUT reference planes;
– Transducer gain and probe factor can be complex;
– New keywords: Object3d, Mapobj, Maxhold, Datafileformat, Vx, Vy, Vz, Target,
Software, Data_source.
• Updating of:
– 4.9 Probe factor and corresponding keywords.
• Modification of:
– Keywords: Average.
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
47A/953/DTR 47A/962/RVC
Full information on the voting for the approval of this technical report can be found in the
report on voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts of the IEC 61967 series, under the general title Integrated circuits –
Measurement of electromagnetic emissions, can be found on the IEC website.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC website under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.

IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
INTRODUCTION
Near-field scan measurements, as described for example in IEC TS 61967-3 [1] or
IEC TS 62132-9 [2], and simulations generate a large amount of data. Many different formats
are used for storing the data, thereby rendering its exchange extremely difficult.
The proposed format is intended to facilitate exchange of near-field scan data between
industrials, academics, EDA tool vendors and end customers. It is based on the well-known
XML format, which is both machine and human readable. Its structure allows the files to be
generated and processed on any operating system. In order to limit the file size, it is possible
to store the information and data in a single file or multiple files. Moreover, the ASCII-based
XML format allows the files to be compressed to a very high level with readily available
compression software.
The three conventional coordinate systems (Cartesian, cylindrical and spherical) are
supported by the proposed exchange format. Information on the device under test, the test
set-up, the probe, etc., is also included in the files. Notes and links to external documents
allow complex test environments to be well described.
The version of the exchange format described in this technical report is 2.0. Future revisions
will add items, such as new keywords and rules, considered to be "enhancements" to Version
1.0. Consequently, all future revisions will be considered supersets of Version 2.0, allowing
backward compatibility.
_____________
Figures in square brackets refer to the Bibliography.

– 8 – IEC TR 61967-1-1:2015 © IEC 2015
INTEGRATED CIRCUITS –
MEASUREMENT OF ELECTROMAGNETIC EMISSIONS –

Part 1-1: General conditions and definitions –
Near-field scan data exchange format

1 Scope
This part of IEC 61967 provides guidance for exchanging data generated by near-field scan
measurements.
The described exchange format could also be used for near-field scan data generated by
simulation or computation software. It should be noted that, although it has been developed
for near-field scan, its use is not restricted to this application. The exchange format can be
applied to emission and immunity near-field scan data in the frequency and time domains.
The scope of this technical report includes neither the methods used for the measurements or
simulations, nor the software and algorithms used for generating the exchange file or for
processing or viewing the data contained therein.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 60050 (all parts), International Electrotechnical Vocabulary (available at
)
IEC 61967-1, Integrated circuits – Measurement of electromagnetic emissions, 150 kHz to
1 GHz – Part 1: General conditions and definitions
ISO 8879, Information processing – Text and office systems – Standard Generalized Markup
Language (SGML)
ANSI INCITS 4:1986, Information Systems – Coded Character Sets – 7-Bit American National
Standard Code for Information Interchange (7-Bit ASCII)
TM
IEEE Std 754 -2008: IEEE Standard for Floating-Point Arithmetic
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 61967-1,
IEC 60050-131 [3] and IEC 60050-161 [4], as well as the following, apply.
3.1.1
section
XML element placed one level below the root element or within another section, and that
contains one or more XML elements, but no value

3.1.2
parent
keyword, one level above another keyword (child)
3.1.3
child
keyword, one level below another keyword (parent)
3.1.4
probe factor
ratio of electric or magnetic field strength at a specified location in near-field evaluation to the
signal level measured at the output connection or applied to the input connection of a probe
[SOURCE: IEC 61967-3:2014, 3.1.2]
3.2 Abbreviations
EDA Electronic Design Automation
NFS Near-Field Scan
XML eXtensible Markup Language
SGML Standard Generalized Markup Language
4 General syntax rules and guidelines
4.1 General
The following rules and guidelines ensure that files intended for exchange will be correctly
recognised and processed by viewers and processors. Examples of XML files conforming to
the present exchange format are given in Annex A.
4.2 XML requirements
4.2.1 General
This exchange format uses XML 1.0 fourth edition to structure the information. XML shall
conform to the standard generalized markup language (SGML) (ISO 8879).
The rules below ensure that the NFS files can be parsed correctly by an NFS parser.
4.2.2 XML declaration
Although the XML declaration is optional in an XML file, the NFS file should include an XML
declaration, dedicated to basic XML parsers. An NFS file parser does not interpret this header.
A file header example is given below:

The XML declaration shall be the first line of the file.
4.2.3 XML elements
All information is saved in the form of XML elements. Each element starts with a start-tag and
ends with an end-tag. The start-tag consists of a keyword enclosed in triangular brackets,
“”. The end-tag consists of the same keyword prefixed by the character "/" and

– 10 – IEC TR 61967-1-1:2015 © IEC 2015
enclosed in brackets, “”. Content in the form of text is enclosed by a start-tag and
an end-tag.
An example of an element is given below:
 
text 
 
It is also allowed to write an element on the same line, for example, to include short content.
text
The contents of an element may consist of one or more other elements or a value (numerical,
or alphanumerical). For clarity, tab characters may be used for indenting. Except when used
for surrounding keywords, triangular brackets "<" and ">" shall not be part of content.
An empty element may be included to indicate that a particular keyword exists, but has no
content:

4.2.4 Root element
The XML file shall contain one, and only one, root element. It encloses all the other elements
and is therefore the sole parent element to all the other elements. The start-tag of the root
element is placed at the beginning of the file or after the XML declaration when present. The
end-tag of the root element is at the last entry of the file.
4.2.5 Comments
Comments may be inserted into the file between “”. An example is given below:


Comments can be inserted anywhere in the file, except inside start- and end-tags, and written
on a single line or on several lines. All text enclosed by comment brackets is considered as a
comment and may be ignored.
4.2.6 Line terminations
In order to facilitate readability, it is usual to organise the file into lines. The line termination
sequence shall be either a linefeed character or a carriage return character followed by a
linefeed character.
4.2.7 Element hierarchy
The order of the elements is not important, but their hierarchy shall be respected.
example layout:
.

.
.

.
An acceptable equivalent layout of the example:

.
.

.
.

In this layout the order is changed, but the hierarchy is respected.
An unacceptable layout of the example:
.
.
.

.

In this layout the hierarchy is not respected.
4.3 Keyword requirements
4.3.1 General
Keywords, placed in start- and end-tags, are used to introduce descriptions, values and
sections that are specific to NFS measurements and simulations. A list of keywords is given in
Annex B and a more detailed description of each keyword is given in Annex C.
Keywords for sections with the Root element as parent, such as Component, Setup and Probe,
shall only appear once in an XML file or a group of XML files (see 4.4.5). However, an XML
file or a group of XML files (see 4.4.5) may contain several data sections. This allows the
measurements on a component using, for example different lists of frequencies or coordinate
offsets, to be included in the same XML file or group of XML files.
Some keywords, such as Frequencies, Unit, List, etc., may be present in several sections.
A parent keyword is required when a child keyword is present.
The rules below ensure that the file can be correctly parsed by an NFS parser.
4.3.2 Keyword characters
Only ASCII characters, as defined in ANSI INCITS 4:1986, shall be used in the files. The use
of characters with codes greater than hexadecimal 07E is not allowed. Also, ASCII control
characters (those numerically less than hexadecimal 20) are not allowed, except for tabs or in
a line termination sequence. For example, the "°" character (ASCII 176) is not permitted. Only
alphabetical or numerical characters can be used to write keywords. Spaces are not permitted.
If needed, the underscore "_" character can separate the parts of a multi-word keyword.
4.3.3 Keyword syntax
The content of the files is case sensitive. All keywords shall be written in lower case starting
with an upper case letter.
– 12 – IEC TR 61967-1-1:2015 © IEC 2015
4.3.4 Root element keywords
As described in 4.2.4, all elements of the file shall be enclosed within the root element. The
following keywords are reserved for root elements and shall not be used for any other
purposes in the file:
EmissionScan
ImmunityScan
If the proposed XML file format is used for other applications, other keywords may be used in
the root element, but NFS parsers may not be able to parse the file.
4.4 File structure
4.4.1 General
The information to be exchanged may be stored in a single XML file or in several XML and
data files. The following rules and guidelines ensure that the files can be correctly located by
an NFS parser.
4.4.2 File names
To facilitate portability between operating systems, file names should have a base name of no
more than forty characters followed by a period ".", followed by a filename extension of no
more than three characters. The file name and extension shall use characters from the set
(space, " ", 0x20 is not included):

a b c d e f g h i j k l m n o p q r s t u v w x y z
0 1 2 3 4 5 6 7 8 9 _ ^ $ ~ ! # % & – { } ) ( @ ' `

4.4.3 File paths
In order to ensure portability and compressibility, only relative paths can be used to define a
path name. An absolute path is not exportable and is not permitted. The relative path shall
start with "./" to indicate that the path name of the picture file will be appended to the path of
the current XML file. It is not permitted to browse to a higher level from the current XML path
(e.g. by using "./"). A file name without "./" is assumed to be located in the same directory as
the current XML file.
4.4.4 Single XML file
When the information is contained in a single XML file, it shall conform to the rules and
guidelines applicable to XML files, as described in 4.2.
Data is included in the Data section of the file within the XML element using the keyword: List
and shall be stored in ASCII form. When binary data is to be stored, it shall be included in
separate data files as described in 4.4.6.
4.4.5 Multiple XML files
The XML document is divided into several sections having the root element as parent. Such a
section contains information on a particular part of the NFS environment and is defined by
keywords such as Component, Setup, Probe and Data. Each XML file may contain one or
more sections and shall conform to the rules and guidelines applicable to XML files as
described in 4.2 and 4.3.1. An example of multiple XML files is given in Clause A.12.
In order to ensure portability and compressibility, all the XML files shall be placed in the same
directory, as shown in Figure 1. The NFS parser shall parse all the XML files that are in the
main directory.
Main directory
XML_File1.xml
XML_File2.xml
XML_File3.xml
XML_FileN.xml
IEC
Figure 1 – Multiple XML files
4.4.6 Separate data files
Information may be contained in a single file or multiple XML files and the data contained in
one or more additional data files. XML files shall conform to the rules and guidelines
applicable to XML files, as described above and in 4.2. Data files shall contain only lines of
data as described in 4.8. The names and paths of the data files are defined by the keyword:
Data_files and shall conform to 4.4.2 and 4.4.3.
The information contained in the data file(s) may be stored in ASCII form for human
readability or in binary form. Binary data shall conform to the binary32 interchange floating-
TM
point format described in IEEE Std 754 -2008. This 32-bit format includes 1 sign bit, an 8 bit
biased exponent and a 23 bit trailing significant field. The format of the data files is specified
by the keyword: Datafileformat. If the keyword: Datafileformat is empty or absent, it is
assumed that the data is stored in ASCII form. All data files shall use the same data format.
In order to ensure portability and compressibility, the data files shall be placed either in the
same directory as the XML files or in a sub-directory located at the same level or a lower level
as the XML files, as shown in Figure 2. It is not permitted to locate the additional files at a
higher level than the XML files.
4.4.7 Additional files
An XML file may contain references to other files such as image files (Keyword: Image) and
document files (Keyword: Documentation). In order to ensure portability and compressibility,
these additional files shall be placed either in the same directory as the single XML file or in a
sub-directory located at the same level or a lower level as the XML files, as shown in Figure 3.
It is not permitted to locate the additional files at a higher level than the XML files.
4.4.8 File compression
When compressing the file system, care shall be taken to include the paths of the various
XML and data files in the compressed file. This ensures that, when decompressed, the file
structure is conserved. The paths are not required when all files are stored in the same
directory.
NOTE The most common compression used is the .ZIP File Format [5]. When the various XML and data files are
compressed using the .ZIP File Format, the extension may be .nfs.

– 14 – IEC TR 61967-1-1:2015 © IEC 2015

Main directory
XML_File1.xml
Main directory
XML_File2.xml
XML_File1.xml
XML_File2.xml
Sub-directory
Data_file1.dat
Data_file1.dat
Data_file2.dat
Data_file2.dat
Data_fileN.dat
Data_fileN.dat
IEC IEC
Figure 2a) – Data files in the same directory Figure 2b) – Data files in a sub-directory
Figure 2 – XML files with data files
Main directory
File1.xml
File2.xml
Main directory
File1.xml
Sub-directory
File2.xml
Image.jpg Image.jpg
Document1.doc
Document1.doc
Document2.pdf Document2.pdf
IEC IEC
Figure 3a) – Additional files in the same directory Figure 3b) – Additional files in a sub-directory
Figure 3 – Additional files
4.5 Values
4.5.1 General
When an element contains a value, this may be a numerical value (e.g. “123.45”), a numerical
value with units (e.g. “123.45MHz”) or a text string (e.g. “This is text string number 2”).

4.5.2 Numerical value syntax
Numerical values may be expressed in decimal form with the period as the decimal separator
(e.g. “123.45”) or in scientific form (e.g. 1.2345e2). Spaces " " and commas "," which are often
used as thousand separators, and other characters, are not allowed.
In cases where several numerical values are required, they shall be separated by spaces " "
or tab characters.
4.5.3 Numerical value with units syntax
The numerical value (see 4.5.2) is followed by valid units, as described in 4.5.5 (e.g.
123.45MHz). Spaces are not allowed between the numerical value and the units.
4.5.4 Text string
A text string may represent a word recognised by the NFS parser or it may be a file name, a
description, etc. A text string may contain any of the alphanumerical characters given in 4.3.2.
4.5.5 Valid units
Units may be expressed as simple linear units or as logarithmic units (dB).
Although not strictly a near-field parameter, power flux density has also been included in the
list of valid units for completeness.
Valid units are:
V for volt A for ampere W for watt  ohm for ohm
Hz for Hertz m for metre s for second
Inverse units are also valid:
S for siemens =1/ohm
Combined units are permitted, such as:
V/m for volt per metre
A.m for ampere metre
/V.m for per volt metre
Valid scaling factors are:
T = tera: 1e12 k = kilo: 1e3  n = nano: 1e-9
G = giga: 1e9  m = milli: 1e-3  p = pico: 1e-12
M = mega: 1e6  u = micro: 1e-6  f = femto: 1e-15
When no scaling factors are specified, the appropriate base units are assumed. These are
volts, amperes, watts, ohms, siemens, hertz, metres and seconds. Abbreviations for the units
(e.g., pV, nA, ms, MHz) shall be used, except ohm, which shall be written in full.
All temperatures shall be represented in degrees Celsius. Symbol "°C" is not required.
...