Measurement View

The Measurement view displays all data files uploaded to Specification Compliance Manager from each stage of the product development cycle. Specification Compliance Manager compares the data in each of these files with the information defined in the Spec view for the product to determine specification compliance health status.

Files that you upload to the Measurement view must be saved as a CSV file and the file contents must meet specific format requirements. The CSV file content format requirements are defined in Measurement Data File Template. These requirements are also defined in a PDF document that is included in the measurement data template ZIP file.

Note Click Upload Data on the right side of the Measurement view to upload data files. If the Measurement view is empty, the Upload Data and Download Measurement Data Template buttons appear in the center of the view.

A progress bar appears at the bottom of the Measurement view during the file upload process. If Specification Compliance Manager encounters an error or warning during the upload process, the progress bar displays an indicator to highlight issues that require attention. Hover over an icon with your cursor to view a summary of errors in the measurement data file.

Tip The error summary in the progress bar displays only up to five errors.

Measurement Data File Template

A measurement data file contains information about each individual measurement taken during validation test, simulation test, or production test for the product. Specification Compliance Manager requires specific formatting and column naming conventions in all measurement data files that you upload to ensure compatibility with the relevant product specifications.

Open the menu in the top-right corner of the Measurement view and click Download Measurement Data Template to download a template file to use as a starting point for your own measurement data files.

Note Specification Compliance Manager requires that measurement data files are saved in CSV file format. Additionally, Specification Compliance Manager will parse through measurement data files during the upload process to identify any data formatting errors.

The measurement data file consists of three types of rows: column names, column types, and measurement data.

The first row defines the column names. Each column name in the measurement data file must be unique. Additionally, column names cannot contain square bracket characters or comma characters.

The second row defines the column type. The column type definitions in the measurement data file must match the following list of abbreviations for each column type:

  • Metadata—META
  • Standard—STD
  • Condition—COND
  • Information—INF

All other rows contain measurement data values and the information associated with the relevant measurement. Formatting rules for entries in these rows depend on the column name and column type. Refer to the following sections for information about specific column formatting requirements.

Metadata Columns (META)

Metadata columns define reference information about the operation(s) that produced the measurement data, such as the name of the test lot or product revision information. All metadata columns are optional and the values have a 200-character limit. Specification Compliance Manager only parses the first row of metadata columns. All other rows in the metadata column can be empty.

Specification Compliance Manager supports only the following Metadata columns. Metadata column titles are case sensitive and must match the following text exactly.

  • DeviceIdentifier
  • RunId
  • SpecProductId
  • ProductName
  • ProductRevision
  • PackageType
  • LotName
  • ChipId
  • ProgramName
  • TestBench
  • Operator
  • Lab
  • StartTime
  • FinishTime
  • RunComment
  • RunModeName

You can insert metadata columns into a measurement data file in any position before the SpecID column. The values in the first row of each Metadata column apply to all data in the measurement file. Values that are not in the first row of a Metadata column are not considered.

Standard Columns (STD)

Standard columns contain required information about the measurement data that is used to define the data value and its relationship to a product specification. Do not change the order of standard columns in the measurement data file template.

Specification Compliance Manager supports only the following standard column names. Standard column names are case sensitive and must match the following text exactly.

  • SpecID
  • MeasurementName
  • Value
  • Unit

The SpecID column defines the ID that Specification Compliance Manager uses for classification and mapping. SpecID values can contain up to 32 alphanumeric characters. Entries in the SpecID column can contain a single SpecID or multiple SpecIDs. If the entry includes multiple SpecIDs, each SpecID must be separated by a comma and the list must be enclosed in quotation marks: “Spec01,Spec02,Spec03”.

You can also include an empty value in a list of multiple SpecIDs and use the Spec Mapping view to map the data to a SpecID: “Spec01,,Spec03”.

Note When editing CSV files in MS Excel, multiple SpecIDs entered as a comma separated string will be automatically enclosed in quotation marks when saved.

The MeasurementName column contains the name of the measurement that generated the data sample. Entries in the MeasurementName column have a 200-character limit. This column is required for rows of measurement data.

The Value column contains the data sample. Each entry in the Value column must either contain a numerical value or one of the supported functional string values. Empty Value cells in a measurement data file cause an error during the file upload process.

For parametric measurements, this column supports floating point values and can include either scientific notation or the SI prefix for the data point, but not both. For example:

  • 8.96
  • 1.25m
  • 5.2e-2

For functional measurements, this column supports the following case-insensitive values:

  • PASS and FAIL
  • TRUE and FALSE
  • GOOD and BAD
  • 1 and 0

The Unit column defines the unit of measure that applies to the data sample. The base unit of measure for each parametric data sample must match the unit of measure for the relevant specification. If the specification definition does not include a unit of measure, the relevant data samples cannot contain a value in this column. If the unit of measure is empty and it is mapped to a specID with a unit, the measurement file will error out during upload. Unit column values have a 200-character limit.

Notice Do not assign a unit of measure to functional data. If a functional specification includes a unit, you cannot map it to a functional specification.

If the specification definition does not include a unit of measure, the relevant data samples cannot contain a value in this column. If there is a defined unit of measure for the specification and the data sample does not include a unit, Specification Compliance Manager applies the unit of measure for the specification to the data sample.

Entries in the Unit column can contain a prefix if needed, which must be the first character in the string.

Specification Compliance Manager supports the following unit prefixes:

  • f—Femto (1e-15)
  • p—Pico (1e-12)
  • n—Nano (1e-9)
  • u, μ—Micro (1e-6)
  • m—Milli (1e-3)
  • c—Centi (1e-2)
  • d—Deci (1e-1)
  • da—Deka (1e+1)
  • h—Hecto (1e+2)
  • k—Kilo (1e+3)
  • M—Mega (1e+6)
  • G—Giga (1e+9)
  • T—Tera (1e+12)

    • Specification Compliance Manager supports the following base units of measure:

    • Temperature: °C, degC, °F, degF, K
    • Voltage: V, dBV, dBmV
    • Current: A
    • Pressure: Pa, atm – atmospheric pressure, bar, Torr
    • Force: N
    • Power: W, dBm, dBW, dBmW
    • Energy/Heat: J, cal, eV, Wh
    • Resistance: Ω, ohm
    • Length: m
    • Mass: g, t, ton, tonne
    • Time: s
    • Gain: dB
    • Electric Conductance: S
    • Capacitance: F
    • Inductance: H
    • Frequency: Hz
    • Electric Charge: C
    • Magnetic Flux: Wb
    • Magnetic Flux Density: T
    • Level of phase noise and harmonics: dBc
    • Volume: l, L, litre
    • Angle: rad, sr, deg
    • Amount of substance: mol
    • Luminous intensity: cd - candela
    • Luminous Flux: lm
    • Radioactivity: Bq
    • Ionizing radiation dose: Gy, Sv
    • Sound: dBA
    • Other engineering units:
      • Np
      • dBFS
      • V/s
      • V/ms
      • V/us
      • V/µs
      • V/ns
      • V/A
      • °C/W
      • degC/W
      • °F/W
      • degF/W
      • V/V
      • V/rtHz
      • V/sqrtHz
      • V²/Hz
      • ppb/°C
      • ppb/degC
      • ppb/°F
      • ppb/degF
      • ppm/°C
      • ppm/degC
      • ppm/°F
      • ppm/degF
      • %/°C
      • %/degC
      • %/°F
      • %/degF
      • Vrms
      • V-rms
      • Vpp
      • V-pp
      • A/mT
      • V/mT
      • bit
      • bit/s
      • bits
      • bits/s
      • Vs
      • V-s
      • %FSR
      • UI
      • delta
      • X
      • Az

    Condition Columns (COND)

    Condition columns capture descriptive information about the measurement data for additional context to consider during analysis of specification compliance. Condition columns are customizable with minimal formatting requirements. These columns can contain numerical values, including floating point numbers, and string values.

    It is optional to include a unit of measure in a Condition column name. If a unit is included, you must enclose it in parenthesis, and it must follow the condition name immediately with no space in between. For example, ConditionName(Unit). The unit of measure should not contain any whitespaces. If you specify a unit of measure for a Condition column, only insert numerical values in the column. The Condition column name is case-insensitive and each Condition column name must be unique within a measurement data file.

    Note Only specify a unit of measure for numerical data values in Condition columns. If the metric prefix of the condition unit of measure differs from the specification unit of measure, Specification Compliance Manager converts the condition data to match the specification unit of measure.

    You cannot use the following reserved names for Condition columns. This restriction includes instances of a reserved name followed by a unit of measure, such as Unit(mA).

    • DeviceIdentifier
    • RunId
    • SpecProductId
    • ProductName
    • ProductRevision
    • PackageType
    • LotName
    • ChipId
    • ProgramName
    • TestBench
    • Operator
    • Lab
    • StartTime
    • FinishTime
    • RunComment
    • RunModeName
    • SpecID
    • MeasurementName
    • Value
    • Unit
    • BaseUnit
    • ResultType
    • DBSerial_No
    • MeasurementConditionGroupID
    • ResultData

    Condition column names have a 64-character limit. The optional unit of measure has a 32-character limit. Condition column values have a 200-character limit.

    Tip NI recommends a maximum of 20 condition columns to ensure optimal performance.

    Each cell within a Condition column can contain only a single condition value. Do not express multiple condition values as a comma-separated list in a single cell. For example, the entry 1,2,3,4 is processed as a single value for the condition.

    Information Columns (INF)

    Information columns contain extra information about the measurement data as needed. A measurement data file can include a maximum of 20 information columns. These columns support only string data. The column names have a 32-character limit and column values have a 1000-character limit.

    You cannot use the following reserved names for Information columns:

    • DeviceIdentifier
    • RunId
    • SpecProductId
    • ProductName
    • ProductRevision
    • PackageType
    • LotName
    • ChipId
    • ProgramName
    • TestBench
    • Operator
    • Lab
    • StartTime
    • FinishTime
    • RunComment
    • RunModeName
    • SpecID
    • MeasurementName
    • Value
    • Unit
    • BaseUnit
    • ResultType
    • DBSerial_No
    • MeasurementConditionGroupID
    • ResultData