Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO 25297-1:2012 NODIF Standard Optical Design Data Exchange STEP-Based Application Protocol
Nominal definition of the optical hardware interface – Part 1: STEP-based data exchange for optical systems
1. Introduction to ISO 25297-1 and the NODIF Standard
ISO 25297-1:2012 specifies the NODIF (NOminal Definition of the optical hardware Interface) standard for the exchange of optical design data between different optical design software packages. The standard defines a STEP-based (ISO 10303) application protocol that enables seamless data transfer of optical system definitions, including surface parameters, materials, and evaluation data, across different computing environments.
The standard was developed to address the long-standing interoperability problem in optical engineering: optical design software from different vendors (Zemax, Code V, OSLO, etc.) each used proprietary file formats, making collaborative optical design across organizations extremely difficult. NODIF provides a vendor-neutral, standardized format based on the EXPRESS information modeling language that preserves the full fidelity of optical design data.
For optical system engineers working across multiple design platforms or collaborating with external partners, NODIF eliminates the data loss and re-entry errors that plague proprietary format conversions. A single NODIF file can transfer complete optical system definitions including surface data, materials, tolerances, and performance evaluations.
2. Technical Architecture of the NODIF Information Model
2.1 Units of Functionality (UoFs)
The NODIF information model is organized into five Units of Functionality (UoFs), each representing a distinct aspect of optical system design data:
| UoF | Name | Scope | Key Entities |
|---|---|---|---|
| UoF 1 | optical_system_definition | Overall system structure, coordinate systems, and references | optical_system, coordinate_system, aperture_definition |
| UoF 2 | optical_surface_definition | Surface geometry, position, and orientation | optical_surface, surface_profile, aspheric_coefficients |
| UoF 3 | optical_material_definition | Glass types, refractive indices, and dispersion data | optical_material, glass_catalog, dispersion_formula |
| UoF 4 | optical_tolerance_definition | Manufacturing tolerances and sensitivity data | tolerance_parameter, sensitivity_analysis, compensator |
| UoF 5 | optical_evaluation_definition | Performance evaluation results and criteria | evaluation_function, merit_function, image_quality_metric |
2.2 Surface Representation Models
NODIF supports multiple surface representation models essential for modern optical design. The standard explicitly defines spherical surfaces through curvature and conic constant, aspheric surfaces through polynomial coefficients (up to 20th order), diffractive surfaces through grating equations and efficiency data, and freeform surfaces through Zernike or spline representations. For each surface type, the standard specifies the coordinate system conventions, sign conventions for radii and distances, and the mathematical formulations used for ray tracing.
A common source of data exchange errors is sign convention mismatch. NODIF mandates the ISO 10110 sign convention: radii are positive when the center of curvature lies to the right of the surface vertex, and negative when to the left. All exchanging systems must adhere to this convention or provide explicit conversion.
3. Engineering Implementation and Practical Considerations
3.1 STEP Implementation Architecture
The NODIF standard is implemented as an Application Protocol (AP) within the ISO 10303 (STEP) framework. The physical file format uses the STEP clear text encoding (ISO 10303-21), which provides a human-readable ASCII format. The EXPRESS schema (ISO 10303-11) defines the information model using entities, attributes, and constraints. An implementation requires three components: a STEP file parser/writer, the NODIF-specific schema mapping to internal data structures, and validation checking for completeness and consistency.
Typical NODIF file sizes range from 50 KB for simple singlets to several megabytes for complex multi-element systems with tolerance data. The standard recommends that implementations support at minimum the five core UoFs, with optional support for additional application-specific extensions.
3.2 Validation and Compliance Testing
ISO 25297-1 defines a three-level compliance classification. Level 1 (basic) requires support for spherical surfaces, standard glass catalogs, and basic system definition. Level 2 (intermediate) adds aspheric surfaces, tolerances, and wavelength data. Level 3 (advanced) requires full support for all UoFs including diffractive surfaces, freeform geometries, and complete evaluation data exchange. Any implementation claiming NODIF compliance must clearly state its compliance level.
Best practice: When implementing NODIF data exchange, perform round-trip testing: export a reference design from System A, import into System B, and re-export back to NODIF. Compare the original and re-exported files to verify that no data degradation has occurred. Key parameters to check are surface radii (tolerance < 0.01%), thicknesses (< 0.1%), and aspheric coefficients (< 0.1%).
4. Practical Applications and Industry Impact
The NODIF standard has found significant adoption in multi-vendor optical design workflows, particularly for aerospace and defense applications where optical systems are designed by prime contractors and manufactured by specialized suppliers. It enables the transfer of design data with full tolerance information from the design house to the manufacturer, ensuring that manufacturing variations are correctly accounted for in system performance predictions. The standard also supports archive and long-term preservation of optical designs in a vendor-independent format.
5. Frequently Asked Questions
Q1: Is NODIF compatible with all commercial optical design packages?
Major optical design packages including Zemax OpticStudio, Code V, and OSLO provide NODIF import/export support either natively or through plug-ins. However, support levels vary: some packages implement only Level 1 compliance, while others fully support Level 3.
Major optical design packages including Zemax OpticStudio, Code V, and OSLO provide NODIF import/export support either natively or through plug-ins. However, support levels vary: some packages implement only Level 1 compliance, while others fully support Level 3.
Q2: How does NODIF handle non-standard or proprietary surface types?
NODIF provides an extensibility mechanism through the “user_defined_surface” entity, which allows proprietary surface types to be represented using parameter lists and descriptions. However, full interoperability for custom surfaces requires bilateral agreement between exchanging parties.
NODIF provides an extensibility mechanism through the “user_defined_surface” entity, which allows proprietary surface types to be represented using parameter lists and descriptions. However, full interoperability for custom surfaces requires bilateral agreement between exchanging parties.
Q3: What is the relationship between ISO 25297-1 and ISO 10110?
ISO 25297-1 references ISO 10110 (Optics and photonics – Preparation of drawings for optical elements and systems) for sign conventions, tolerance notation, and surface form specifications. The two standards together provide a complete framework for optical design data exchange.
ISO 25297-1 references ISO 10110 (Optics and photonics – Preparation of drawings for optical elements and systems) for sign conventions, tolerance notation, and surface form specifications. The two standards together provide a complete framework for optical design data exchange.
Q4: Can NODIF handle non-sequential optical systems?
The current version of NODIF (ISO 25297-1:2012) is primarily designed for sequential ray tracing systems. Non-sequential systems (illumination design, stray light analysis) may require additional application-specific extensions beyond the five core UoFs.
The current version of NODIF (ISO 25297-1:2012) is primarily designed for sequential ray tracing systems. Non-sequential systems (illumination design, stray light analysis) may require additional application-specific extensions beyond the five core UoFs.
