Application Husk
The DOT Application Husk contains a number of modules to aid in using the DMIS Part 2 interfaces. These are designed to encapsulate and simplify common operations, and they provide an important structure that streamlines significant areas of interaction with the DMIS engine (the DOT kernel).

Connection Manager
The husk contains classes and functions to manage the connection between a DMIS client application and the DMIS server. (For the DOT toolkits, this is the DOT Kernel; however, the husk should support connection to any DMIS Part 2 compliant DMIS server). These can find and connect to an existing (running) DMIS server, or start the DMIS server locally if it is not running. The husk classes also contain methods to attach and detach event handlers, to create, load, single step and execute DMIS programs, and to perform other fundamental operations. The husk also maintains a shared reference for each of the commonly used DMIS Part 2 objects. It also allows multiple event handlers to be registered and deregistered for event notification.

Event Scanner
The husk contains a layered subsystem for processing DMIS events of interest during execution of a DMIS part program. These layers successively break down the event information into greater detail. The event scanner layer simplifies compound event information, and orders event handler callbacks to ensure the correct sequencing of definitions and dependent calls.

DMIS Model
The husk event subsystem contains a flexible, user-extensible DMIS model which is built dynamically during event processing. This model correlates various information about when, where, and in some case, how symbols are defined (like features, tolerances, sensors, etc) and operations occur (like measurements, constructions, and tolerancing) within a DMIS program; and can be queried or extended to allow the Application Code to correlate its internal data structures with the DMIS program.

DMIS Import
The final layer of the DMIS event subsystem is a DMIS import module that breaks down key elements of DMIS program execution into parameterized callbacks. For instance, during feature or tolerance definition, the actual parameters from the DMIS program are broken down individually into positions, direction vectors, diameters, tolerance zones, etc. This can significantly simplify their processing within the Application Code.

Support Library
A library of helper classes, smart pointers, and macros is also included, to simplify managing DMIS Part 2 data, and to increase portability. Math classes supply vector arithmetic, matrix transformations, and other common operations. This library is also used within math and equipment plug-ins.

XML Conversion
The husk permits extraction of DMIS VFORM output in a proprietary XML format. This can be passed through readily available XML conversion tools using an appropriately designed XSLT stylesheet to transform into another XML format.