Skip to main content

Report From the 1986 Workshop on Integrated Data Base Development for the Building Industry (1987) / Chapter Skim
Currently Skimming:

'FUTURE DIRECTIONS FOR THE INTEGRATED DATA BASE'
Pages 49-58

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 49...
... An outline of the IDB concepts with the intent that they be developed by the Committee on Integrated Data Base Development for communication to industry and the public sector, B An explanation of some key issues that need further work and validation prior to development of an IDB, and C
Read the entire page →
From page 50...
... The heterogeneous, distributed nature of the IDB provides a means of including all interested organizations as participants and contributors. Data Base Management Facilities The IDB is based on the concept of a comprehensive set of data base management capabilities including, but not limited to: • Data security -- means to control access and use of data, and monitoring threats to data in the IDB by unauthorized persons; no data are lost or changed, • Privacy -- controlled access to data that are used to develop aggregate data, • Data integrity -- that quality of data, and the associated processes that ensure the consistency, reliability, accuracy, and preservation of data maintained by the IDB; data derived from information in the IDB may be stored or rederived, depending on the complexity of derivation and likelihood of downstream use; stored or computed data that accurately reflect the state of the project at that time, • Configuration control -- the set of processes that address maintenance of integrity and control of information as they evolve throughout the building process; included are currency, version control, revisions, authorization, approval reviews, and release status (the as-designed, as-planned, and as-built sequence)
Read the entire page →
From page 51...
... For example, in a case where office partitions have been moved and space assignments have changed, the designed performance values no longer reflect the current performance of the actual building system. Another type of deterioration occurs when changes in computer hardware and software require input data that are not stored in or accessible by the IDB.
Read the entire page →
From page 52...
... These data types and a set of operations on them represent the normal functions on CURRENT USERS IDS USERS APPLICATIONS (Energy AnalysIs) APPLICATIONS INFORMATION SYSTEM CAPABILITIES APPLICATIONS (Energy AnalysIs)
Read the entire page →
From page 53...
... Many users already have major investments in large data bases and application software. Therefore, the IDB concept must support a productive migration to this new environment.
Read the entire page →
From page 54...
... The role of the IDB in translating between local systems is, in part, like that of a data base exchange standard. A data base exchange standard acts as a common denominator in the transfer of data between dissimilar systems in a heterogeneous computing environment.
Read the entire page →
From page 55...
... As an illustration of how such a large data base would be unmanageable, one workshop participant speculated that a comprehensive data base for a building would need to consist of at least three gigabytes of data types. This does not yet account for the amount of data types required to support all possible formats used by different computing systems.
Read the entire page →
From page 56...
... Rule systems for both spatial or property consistency are required if data integrity is to be enforced. The maintenance of these properties is a formidable challenge in homogeneous data base systems.
Read the entire page →
From page 57...
... 2. The Committee on Integrated Data Base Development should report the IDB concepts and issues formally to agencies of the Federal Construction Council through a committee report.
Read the entire page →

Key Terms

  • data types
  • idb environment
  • integrated data
  • woods hole
  • hole workshop

  • atomic data
  • data consistency
  • user interface
  • base management
  • user languages

  • local computing
  • data maintained
  • idb concept
  • global idb
  • idb concepts

  • public sector
  • management capabilities
  • hardware interfaces
  • computing environment
  • base development

  • structural design
  • lowest level
  • exchange standard
  • building performance
  • base exchange

  • energy analysis
  • current data
  • comprehensive data
  • stored data
  • idb users


    • This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
    More information on Chapter Skim is available.