| Key Term |
Description |
| 3-D or 3D |
3 components to the object's physical dimensions (e.g. height, width, depth) |
| 4-D or 4D |
4 dimensional - adds a time-dimension to a 3-D object |
| Artificially intelligent facility |
Highly automated project and facility management environment |
| Asset Lifecycle Information System |
The intent of this term is to:
a) Represent the RESULT of implementing the Technical Framework (as described in the Element 9 tactical plan).
b) Be the "thing" that all Elements of the Roadmap refer to when indicating their needs for data and information integration.
The following were taken into consideration in choosing the name:
a) "Asset" (rather than Facility) encompasses facilities, capital projects, and large objects such as bridges and ships that may not be normally be referred to as facilities,
b) Information is also an Asset,
c) The name refers to the whole "system" as used in a traditional mathematical or scientific sense, to mean "that which acts upon the information asset", including creating, controlling, validating, and otherwise managing the information asset throughout the lifecycle of the physical asset,
d) To NOT represent a static database or repository, but rather to represent the integration of data held in multiple repositories or applications in a way that satisfies business requirements for persistence, consolidation and exchange of data,
e) To NOT represent a single software application, but to imply the aggregation of tools and processes to enable the management of information about assets,
f) A term that is not too much of a mouthful,
g) The name did not bring up any search results using the Google Web search engine (and those brought up by its acronym "ALIS" did not seem to be in conflict or otherwise used within our domain).
|
| Capability to capture pertinent data |
Example: sensors with real time data recording where pertinent data is required in real-time |
| Capital Expense |
A financial categorization of costs for accounting and taxation purposes (also Operating Expense - OPEX) |
| Capital Project |
The planning, engineering, procurement, construction and operation of predominantly large-scale buildings, plants, facilities and infrastructure including, for example, vessels and bridges.
Note 1: 'Capital' is not defined in strictly accounting terms.
Note 2: The end-user of a capital project may be from any industry, government or non-profit organization. Examples include: pulp and paper, utilities, oil and gas, pharmaceutical, semi-conductor, shipbuilding, bridge-building, universities, libraries, museums.
Note 3: A capital project may be conducted by the end-user owner/operator or by contractors or by a mix of owner/operator and contractors.
|
| Capital Project Lifecycle |
The lifecycle of the plant or facility, consisting of the phases "feasibility - design - construct - startup - operate - renew" |
| Capital Projects Technology Roadmap (CPTR or the Roadmap)
|
A cooperative effort of associations, consortia, government agencies, and industry, working together to accelerate the deployment of emerging and new technologies that will revolutionize the capabilities of the capital projects industry. The Roadmap presents a vision for the capital projects industry and a strategy and plan for achieving that vision.
|
| Charrette |
"The French word, "Charrette" means "cart" and is often used to describe the final, intense work effort expended by art and architecture students to meet a project deadline." "Charrette is a collaborative planning process that harnesses the talents and energies of all interested parties to create and support a feasible plan that represents transformative community change." Excerpt from www.charretteinstitute.org/charrette.html |
| Data, Information, and Knowledge |
This trilogy has been in common use for decades, with multiple definitions. This one draws from a paper at http://www.systems-thinking.org/dikw/dikw.htm. Another paper on the origins of the Data, Information, Knowledge, Wisdom Hierarchy (DIKW) by Nikhil Sharma was found at http://www-personal.si.umich.edu/~nsharma/dikw_origin.htm
Data - data are raw symbols (the display of a digital thermometer reads 98.6 deg-F, which can be directly encoded in ASCII, Unicode, etc.)
Information - information is data processed to be useful (my body temperature is 98.6 deg-F, which can be represented, for example, in XML using the previous data encoding but with special tags defined to convey the notion of temperature and measure)
Knowledge - knowledge is information processed to be useful (if my body temperature is greater than 98.6 deg-F, then I may be ill, which can be represented, for example, in XML, using the previous data encoding but with special tags defined to convey its rule-based nature.)
|
| Data representation |
The representation of data, information or knowledge in different forms, e.g. graphical, textual, digital. A data representation model (DRM) is a description used to provide identification of all data elements within a system, including their attributes and the logical relationships between data elements. In object-oriented terminology, this is viewed as a class hierarchy, and described through a graphics-based design tool. Each major type of data with important or explicit relationships is captured to show its logical relationship to other types of data. A DRM is not an implementation of a database, but a depiction of the types of data within the system.
|
| Data representation model |
A data representation model (DRM) is a description used to provide identification of all data elements within a system, including their attributes and the logical relationships between data elements. In object-oriented terminology, this is viewed as a class hierarchy, and described through a graphics-based design tool. Each major type of data with important or explicit relationships is captured to show its logical relationship to other types of data. A DRM is not an implementation of a database, but a depiction of the types of data within the system. |
| Engineering /Procurement / Construction (EPC) |
Often used to refer to companies that provide all three services. |
| Enterprise knowledge system |
Front end applications that provide access to backend data |
| Equipment, processes and system function |
The relationships between equipment, processes and system function in a plant or facility. Example: plant processes are maintained by protecting system function, and system functions are protected by maintaining equipment. |
| Extended enterprise |
Industry organization and its supply chain. |
| Extensible Markup Language |
(XML) An internet language standard that enables seamless flow of text-based information via the web. |
| Front End Loading |
Work done at the beginning of a capital project to develop the business plan, establish the business objectives and review processes, gain buy-in from sponsors, and identify hazards prior to any detailed work starting on the project. Intended to maximize efficiencies in capital projects. |
| Industry |
The capital projects industry. The industry that executes capital projects. (Not only in the U.S., also international.) |
| Industry Foundation Classes |
A classification developed by the IAI ("International Alliance for Interoperability") The IAI is a division of the ISO ("International Standards Organization") - the body that controls the IGES and STEP data standards. |
| Industry knowledge base |
A shared information asset developed to organize and disseminate relevant knowledge in the form of comprehensive practice guidelines for one specific industry. |
| International Graphics Exchange Specifications |
Products may be designed as either a two-dimensional, three-view drawing layout, or as a full three-dimensional model with associated drawing views and dimensions using a Computer Aided Design (CAD) system. The IGES format serves as a neutral data format to transfer the design to a dissimilar system. Translators, developed to the IGES Standard, are used to export a design into an IGES file for exchange and for importing the IGES file into the destination system. |
| Interoperable systems |
Applications that support open standards and are tied together via exchange standards and messaging/transport protocols |
| Interoperability in the construction and buildings industry |
The dynamic and seamless exchange of accurate, useful information on the built environment among all members of the building community throughout the lifecycle of facilities |
| Leadership in Energy and Environmental Design, Green Building Rating System® |
A voluntary, consensus-based national (U.S.) standard for developing high-performance, sustainable buildings |
| Legacy data |
Offline or archived data. A legacy data source is any file, database, or software asset (such as a web service or business application) that supplies or produces data and that has already been deployed. |
| Lifecycle data management |
The management of data throughout the capital project or plant lifecycle |
| Model-based information management |
Use of a model for software development and information management. The model covers the entire process (e.g. for building services implementation it would include design, manufacturing, contracting, facilities management). |
| Ontology |
An ontology is a specification of a conceptualization. It is an explicit formal specification of how to represent the objects, concepts and other entities that are assumed to exist in some area of interest and the relationships that hold among them. See Tom Gruber's definition at http://www-ksl.stanford.edu/kst/what-is-an-ontology.html, or refer to http://www.si.umich.edu/UMDL/glossary.html |
| Performance goals |
Performance goals examples include: Return On Investment is x%; No outage of data availability from knowledge bases; Costs of operation are covered by user fees. |
| Plug-and-play |
Requires system abstraction and encapsulation |
| Radio frequency identification |
A generic term for technologies that use radio waves to automatically identify people or objects. |
| Roadmap, the |
The Capital Projects Technology Roadmap |
| Seamless |
Transparent, global, location transparent … the user has no perception that technical boundaries have been crossed |
| Smart Container for Information |
High fidelity container of Knowledge, Information, Data. A Smart Container is a container that could contain other Smart Container. The goal of a Smart Container would be to provide a container rich in meta data and history without any loss of information during any transactions or transformation. |
| Seamless integration of long-term supply and support networks |
Information communication between organizations in a supply chain or support network via widely accepted exchange standards and protocols. |
| STandards for Exchange of Product data (STEP) |
STEP is an unofficial name. The actual designation of the STEP standard is ISO10303 Industrial Automation Systems - Product Data Representation and Exchange. The STEP project was initiated in 1984 by the ISO (International Standards Organization). The objectives were:
- Create a single international standard
- Implement this standard in Industry
- Standardize a mechanism for describing data throughout enterprise life cycle.
- Separate data description from implementation to facilitate neutral file exchange, shared product databases, and long term archiving |
| State |
Measured values, or other indicator of the position of the object within its lifecycle (example: planned, active, complete). |
| Structured vs. unstructured data |
Structured data is anything that has an enforced composition to the atomic data types. Structured data is managed by technology that allows for querying and reporting against predetermined data types and understood relationships.
Unstructured data is the "stuff" that makes up 80 to 90 percent of the information in an organization: the Word and PowerPoint files, the emails, and the intranet newsletters -- the files that store the words that run the companies.
|
| Supply chain |
"A network of facilities and distribution options that performs the functions of procurement of materials, transformation of these materials into intermediate and finished products, and the distribution of these finished products to customers". (Ganeshan and Harrison, 1995) |
| Understanding, and Wisdom |
Two other levels of the Data, Information, Knowledge, Wisdom (DIKW) hierarchy are Understanding (or Expertise) and Wisdom:
Understanding / Expertise - expertise is knowledge applied to a bounded subject. It is the process by which I can take knowledge and synthesize new knowledge from the previously held knowledge.
Wisdom - wisdom is knowing how and when to apply knowledge. Wisdom is a uniquely human state, and wisdom requires one to have a soul, for it resides as much in the heart as in the mind.
|
© 2005 FIATECH. All rights reserved
