Risk assessments- At Field's level of configuration Tables

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      Configuration tables usually store information such as company codes, plant codes or construction project codes, sales organisation or sales channels and other parameters that define the organisation structure of the company.

In building design functions, other types of tables or databases can be used to store and manage design-related information, such as design specifications, building codes, material properties, and construction standards.

These tables or databases (By whatever names they are called and not necessarily configuration tables)can be used to organize and manage the design process and ensure that the project meets the requirements and regulations.

Software tools(like Building information modelling-BIM ) can support the design functions of construction projects and allow for creating and managing design-related data. Such BIM software can create 3D models of building designs and store relevant data about the building's components, systems, and materials. This data can then be used to support construction planning and decision-making.

This blog covers the following aspects vis a-vis building design functions

·       Five activities for assessing risks at field choice levels, along with a template

·       Activities that can adversely impact business

Five activities to asses risks at - Field Choice level of “Database” (or configuration table) tables

1. Identify parameters that can influence the “Database” level (or configuration table) level Risks

Once “Database” (or configuration table) requirements /conceptualization have been done, the HOD/design functional team Identifies the consequences of incorrect accessing and use of specific /identified “Database” (or configuration table)vis-à-vis:

·      Adverse impact on Package specifications or Project package design

·      Negative impact on BOQ quality or construction quality

·       Adverse effect on Statutory conformance

·      Adverse effects on Project costs

2. Design a Risk assessment template at the field choice level of the “Database” (or configuration table) level

3. Software Programming of the Risk Assessment template

4. Populate the field choice level of the “Database”(or configuration table) level risks in the template.

5. Affecting changes in the field choices in above

A similar assessment is to be carried out for other Fields.

 Activities that can adversely impact business

·      Inappropriate levels/positions of “Design functions” team members with consequent inadequate skills for comprehending “Database” (or configuration table) level risks.

·      Inappropriate software development and workflow of risk templates make risk capturing at the field level of the “Database” (or configuration table) cumbersome and inefficient.

·      Inadequate understanding and hence inappropriate capturing of Consequence of Incorrect accessing and use of “Database” (or configuration table) in “Design functions” *    

·      Inaccurate classification of Risk at “Field choice level” of “Database” (or configuration table)-High, or Medium, or Low by functional team member *

·      Non-periodic/non-timely review of previously populated risk template to incorporate changes in “Database” (or configuration table) level risks and so on *

 Handbook of the author 

A template illustrating risk classification as High, Medium, or Low at the field choice level of the “Database” (or configuration table)level is included in chapter 10 (annex 15D) in the handbook of the author and titled” ETHICS in the real estate and hospitality industry, Volume 1- Architectural, Interior design, and MEP services. “