Searcharxiv⌕ Search

arXiv subjects

Z. Kovacs

Publications and source records attributed to Z. Kovacs.

22 records · Page 2Linked to original sources

Design Patterns for Description-Driven Systems

In data modelling, product information has most often been handled separately from process information. The integration of product and process models in a unified data model could provide the means by which information could be shared across an enterprise throughout the system lifecycle from design through to production. Recently attempts have been made to integrate these two separate views of systems through identifying common data models. This paper relates description-driven systems to multi-layer architectures and reveals where existing design patterns facilitate the integration of product and process models and where patterns are missing or where existing patterns require enrichment for this integration. It reports on the construction of a so-called description-driven system which integrates Product Data Management (PDM) and Workflow Management (WfM) data models through a common meta-model.

physics.ins-det↗

Getting Physics Data From the CMS ECAL Construction Database

CMS ECAL physicists must be able to extract physics characteristics from the ECAL construction database for the calibration of sets of detector components. Other applications, such as geometry for simulation and physics event reconstruction, will also need to extract data from the construction database. In each case, application software needs to query the construction database and to extract data that satisfies a particular view. These viewpoints are defined for a specific purpose (e.g. simulation, slow control, calibration) and data must be extracted into the viewpoint for a set of defined detector components (e.g. readout channels) called physics elements. The ECAL construction database follows an object-oriented design to maximise flexibility and reusability. An meta-modelling approach has been taken in its design, which promotes self-description and a degree of data independence. A query facility is being provided to allow navigation around so-called meta-objects in the construction database, facilitating the extraction of physics data into a particular viewpoint. This paper outlines how viewpoints can be populated with data extracted from the construction database, for a set of detector elements relevant for analysis.

physics.ins-det↗

Detector Construction Management and Quality Control: Establishing and Using a CRISTAL System

The CRISTAL (Cooperating Repositories and an Information System for Tracking Assembly Lifecycles) project is delivering a software system to facilitate the management of the engineering data collected at each stage of production of CMS. CRISTAL captures all the physical characteristics of CMS components as each sub-detector is tested and assembled. These data are retained for later use in areas such as detector slow control, calibration and maintenance. CRISTAL must, therefore, support different views onto its data dependent on the role of the user. These data viewpoints are investigated in this paper. In the recent past two CMS Notes have been written about CRISTAL. The first note, CMS 1996/003, detailed the requirements for CRISTAL, its relationship to other CMS software, its objectives and reviewed the technology on which it would be based. CMS 1997/104 explained some important design concepts on which CRISTAL is and showed how CRISTAL integrated the domains of product data man- agement and workflow management. This note explains, through the use of diagrams, how CRISTAL can be established for detector production and used as the information source for analyses, such as calibration and slow controls, carried out by physicists. The reader should consult the earlier CMS Notes and conference papers for technical detail on CRISTAL - this note concentrates on issues surrounding the practical use of the CRISTAL software.

physics.ins-det↗

From Design to Production Control Through the Integration of Engineering Data Management and Workflow Management Systems

At a time when many companies are under pressure to reduce "times-to-market" the management of product information from the early stages of design through assembly to manufacture and production has become increasingly important. Similarly in the construction of high energy physics devices the collection of (often evolving) engineering data is central to the subsequent physics analysis. Traditionally in industry design engineers have employed Engineering Data Management Systems (also called Product Data Management Systems) to coordinate and control access to documented versions of product designs. However, these systems provide control only at the collaborative design level and are seldom used beyond design. Workflow management systems, on the other hand, are employed in industry to coordinate and support the more complex and repeatable work processes of the production environment. Commercial workflow products cannot support the highly dynamic activities found both in the design stages of product development and in rapidly evolving workflow definitions. The integration of Product Data Management with Workflow Management can provide support for product development from initial CAD/CAM collaborative design through to the support and optimisation of production workflow activities. This paper investigates this integration and proposes a philosophy for the support of product data throughout the full development and production lifecycle and demonstrates its usefulness in the construction of CMS detectors.

physics.ins-det↗