Abstract: A system and method to compile different types of data from different locations into one reliable assemblage is provided. The assemblage may include an index of information provided to a user. The assemblage may be in the form of a three dimensional (3D) representation of an object, where the 3D representation includes an index and links to more detailed information regarding the object. The 3D representation may be of any object, for example, a body part in the context of medical imaging, or a building in the context of architectural and engineering design. The assemblage may be comprised of 3D and 2D artifacts. The 2D artifact may include 2D vector and raster embellishment in a variety of forms, such as vector graphics, raster graphics from many sources included hand drawn graphics that are scanned, specification documents, texts, cost data from cost databases, data in tabular form, notes, text, dimensions, link icons (links to other media).

Abstract: An assembly for use with a non-compliant laser device comprising the combination of an emission indicator assembly configured to indicate the actuation of the non-compliant laser device, a key control assembly configured to selectively provide electrical continuity throughout the circuitry of non-compliant laser device, and a remote interlock assembly configured to selectively provide for remote control of the non-compliant laser device and provide electrical continuity throughout the circuitry of non-compliant laser device.

Abstract: Conventional file-based engineering design data for an engineering model are represented by a plurality of components. The plurality of components are kept in stores, which reside on servers. Each store contains the components that correspond to the elements of one design file. The stores also maintain a history of changes made to the components. A plurality of client computers are bidirectionally connected to the servers. Each client computer may obtain the current version of the components and may send locally edited versions of the components back to the servers to replace the current versions in the stores. At the client computer, the user interacts with the components using conventional file-based software.