# SUBSYSTEM OVERVIEW

S214 Interface (S214) Subsystem

The S214 subsystem provides functions specific to STEP AP 214. The S214 subsystem provides STEP dependent functions for creation of STEP information models as well as creation of a minimum set of configuration management entities.

# GENERAL CONCEPTS

The s214_Initialize() and s214_Terminate() functions set up the required data structures. The function s214_Initialize must be called once before any other s214 function. The call to s214_Initialize must follow the step_Initialize call. Once processing is complete, the function s214_Terminate should be called prior to calling step_Terminate.

# CREATING A STEP AP 214 MODEL

To create a STEP model that is ready to work with AP 214 Committee Draft entity structures, the following code sequence is used:

    #include "ddf_Interface.h"
    #include "mda_Interface.h"
    #include "step_Interface.h"
    #include "s214_Interface.h"
            .
    MDA_MODEL_INFO m_info;
    int model;
            .
    pdx_Initialize (PDX_NOOPT);
    step_Initialize (STEP_NOOPT);
    s214_Initialize (S214_NOOPT);
            .
    mda_GetModelDefaults (MDA_NOOPT, &m_info);
    s214_InitModelInfo (STEP_NOOPT, &m_info);
            .
    /*  Other m_info fields set  */
            .
    mda_AllocateModel (MDA_NOOPT, &m_info, &model);

The model is now ready to have STEP entities added. The model can be populated with the contents of a STEP Physical file by calling mda_ParseFile. The contents of a model can be written to a STEP Physical file by calling mda_FormatFile. The mda_intro manual page describes how additional entities are added to the model.