Engineers at HPTSC conduct concept studies and analyses. These studies include the systems engineering and processes that turn vague system objectives and abstracts into defined requirements and conceptual approaches. In so doing, we help mature programs and support successful navigation through program milestone decisions.

We begin with requirements definition and analysis intended to clarify program and system missions and environments. We gather data to support functional definitions and top level performance objectives for system implementation and assess the data to define performance envelopes and design constraints. Our holistic approach includes determining requirements and standards, process owners, strategies involved in the domain, measures of success for those strategies, and expectations. We identify the boundaries of process sub-groups, all internal and external customers, and suppliers. We determine process metrics and control points; establish measurement criteria for all inputs and outputs, sub-groups, and end items; and define the means of collecting data to make the measurements. We select the media for collecting and determining the scope of process data, and we define the statistical tools used to measure process efficiency and effectiveness. As part of this process, our engineers analyze and quantify risk elements in alternative design approaches that meet performance specification objectives. Based on this quantification of risk, we examine risk mitigation scenarios and select the design alternative with the most favorable risk mitigation set. We develop a detailed risk management plan to ensure continuous risk assessment actions during engineering, design, integration, and production.

Our engineers are adept at capturing conceptual design data through operational, technical, or system reference models. We use operational reference models to capture the applicable set(s) of process sub-tasks in an enterprise and their logical relationships. We use IDEF 0 modeling techniques or another customer-preferred technique to develop and implement these process activity models. We use data models to identify the structure, content, and logical relationships of data and information available within the enterprise activity. We use IDEF 1 modeling techniques or another customer-preferred technique to develop and document these data models. We use technical reference models to identify technical migration road maps leading to incorporating emerging information technology and protocol standards. We use system reference models to allocate functions and identify interfaces (physical and logical) that provide the basis for developing a performance specification.

Go Home