Changes between Version 1 and Version 2 of BluePrintBuildingInformationSystem

Timestamp:

03/20/12 05:28:48 (13 years ago)

Author:

Gavin Treadgold

Comment:

added some more info

BluePrintBuildingInformationSystem

@@ -1 +1 @@
 
 == Overview ==
-This blueprint is based on the need to manage multiple types of information about buildings pre- and post-event. This blueprint is based largely on Gavin Treadgold's experiences with post-earthquake building damage assessment following the Canterbury Earthquake Sequence that started on 4 September 2010.
+This blueprint is based on the need to manage multiple types of information about buildings pre- and post-event. This blueprint is based largely on Gavin Treadgold's experiences with post-earthquake building damage assessment following the Canterbury Earthquake Sequence that started on [[http://en.wikipedia.org/wiki/2010_Canterbury_earthquake|4 September 2010]], and included the [[http://en.wikipedia.org/wiki/2011_Christchurch_earthquake|22 February 2011 aftershock]] that killed 185 people, as well as the [[http://en.wikipedia.org/wiki/June_2011_Christchurch_earthquake|June 13 2011 aftershock]] that caused considerable more damage to the built environment.
 
 == Concept ==
@@ -18 +18 @@
  * Status Changes - some of the key information, such as the building state, needs every state change to be recorded. E.g. when a building was marked as 'yellow/restricted access', and when this was later changed to 'red/no access', or 'green/no restriction on access'. These state changes, that are usually triggered by an assessment, need to be recorded.
 
+It isn't the responsibility for the BIS module to provide all the tools, but rather to integrate and produce an overview from information contained in other Eden applications. Assessment, for example, will be links to the actual assessments in the [[http://eden.sahanafoundation.org/wiki/BluePrintAssessment|Assessment application]]
+
 == Users ==
 The primary user will be the local authority that has the regulatory authority to manage the built environment e.g. a local council. Secondary users will include, but not be limited to the building owner, the building manager, the tenants, and the insurers. All of these users will potentially need access to multiple buildings in the system. If the BIS is publicly deployed, then many of these individuals and organisations will need the ability to self-register, and start linking themselves to buildings in the database e.g. an engineering firm may register, and then identify all the buildings that they are acting as the engineer for. It would be the building owners responsibility to approve their request to be 'added' to the building.