Showing posts with label B5. Show all posts
Showing posts with label B5. Show all posts

Tuesday, February 13, 2018

B5- Database

Database

I think data is the real asset of an organization. We will most likely interact heavily with databases during our professional career. Core database concepts and practices are extremely durable, and are likely to serve us for years to come. So, a collection of related data organized for easy storage and retrieval in electronic form will dramatically increase the efficiency of processing and understanding them. Almost any construction firm or other company in this field of appreciable complexity has information management requirements that are hard to satisfy without using a database. Since construction process always involve multiple companies working together from different aspects, the arrangement of database allows a number of different kinds of applications to work with the same set of data. Database can also ensure that the data must always meet certain conditions, such as ‘the span can’t be entered twice,’ regardless of the measurement manipulating it. We can also get the benefits of its security and concurrency. We can control who is authorized to manipulate what and govern what types of activities can take place at the same time. A database can also prevent data loss since it has the character of backup and disaster recovery. The most important thing is it can present different users with customized views of the same data. For example, each of your subcontractors will only have access to the data you want them to read. This can avoid wrangling and protect your trade secret in some degree.

I want to share an experience as the support of my above opinions. I was working for a small energy company for my first co-op cycle. Their duty is to re-design old structure's HVAC (heating, cooling and ventilating) system. I was involved in both field work and engineering design process. Their data managing techniques are relatively primary. They are collecting data from site investigation manually and I have to spend two hours per day for inputting them into computer. They do not process raw data before modeling or designing even though it is easy to be done on excel. I always need to convert units of the data for different design purpose. There are thousands of folders on their server and it always consumes a lot of time to find the proper one. These make their working efficiency lower than it should be. If they have a database that can perform all of the advantages as discussed in the first paragraph, their business will grow a lot faster and their work quality will increase a lot.
Comments:


Uses of databases in design offices
Shaden
We were doing the same topic. I am more focusing on database’s advantages while you made good efforts on illustrating the functions of database. You made a comparison between excel and database. This is really helpful to me since these two are having similar format and I sometimes confused about them.

SQL – What is it and why is it important?
Thomas
This is an informative and interesting post. I have only heard of database but I never know that there is a thing playing key roles interacting with elements in a database. I am taking a construction management course and I am taught to use Procore. It is an online software that the architect, engineer, GCs, owners can share and modify data. I think this platform is a good example of SQL. You can take a look of it if you are interested.

Object Oriented Database
Sherry
I like the graphs you used to help us to have a better understanding of object oriented databases. I have also read the original articles you listed in references. They are informative and helpful.

Quelly Wk 6-1: B5, Databases in Construction

B5: Functionality of Databases during Construction

With my little experience in construction management (working as a construction inspector for PWD), one of the main challenges I faced on the job site was the communication of information from the clients (the PWD design engineers) to the contractor, and back (to me in the field). As database technology continues to develop, there is therefore an increasing applicability in the construction process.

B5 - What is SQL? - Maita


Structured query language, or SQL, is considered to be today’s standard means of manipulating and querying data in relational databases. SQL is a domain specific language that is utilized in programming. In addition to managing the data that is stored in the relational database, SQL can stream the processes in a management stream. There have been many systems that do what SQL does, called APIs. SQL has generally surpassed its competition by introducing the concept of accessing a multitude of records by using a single command. SQL also eliminates the use for an index by letting the user bypass entering a command to access a record.




Resources:
https://www.infoworld.com/article/3219795/sql/what-is-sql-structured-query-language-explained.html

https://en.wikipedia.org/wiki/SQL

B5 - Uses of databases in design offices


Uses of databases in design offices

In order to understand what is the use of database for design offices one must understand the proper definition of database, because some may mistake excel for being a database due to its data recording capabilities as it’s similar to the concept of a database where it stores and records data.

What is database?
“Database is a gathered collection of information that is structured according to the relationship of data with one another for each access and management” (Kilkelly, ArchSmarter).Managing a database includes but not limited to entering, deleting, and exporting data. Example of database management system that are used to design database are MS Access, MySQL, FileMaker, and Oracle.

What is Excel?
Excel is a spreadsheet that is use primarily for analyzation of data, while it cannot handle very large amount of recorded data as a database.

Database Vs Excel
“Databases are designed to in a way to refer to information without actually requiring to load all of the information into memory.” (Valentina-db)
The following table below compares “MS Excel” to “MS Access”, which gives an idea of what’s the difference between a database such as Access and a spread sheet such as Excel.

(Source: Gavin, Excel Vs. Access)

How may database be used for design office
For large projects that contain many requirements in terms of the architectural and engineering design aspect, a database may be used to record and track data, where the database is structured based on the considerations of the owner’s requirements, requirements completed, requirements need to be completed, problems required to be solved, solved problems, and their solution, keeping track of whose working on what and who changed what. In addition to storing data such as before and after files, which is beneficial for reverse of change if required.

Other use of database may be for file management purposes, where files can be accessed, downloaded and edited from anywhere. In addition to securing the files by controlling who can and can’t access the database for a certain project.

Other benefits of a database for design offices is recording client’s information such as address, name, phone number, projects previously worked on and details such as cost, change orders, etc. Keeping track of issues or change orders with clients would be beneficial for creating a better strategy for future projects if any. In addition, keeping track of the office’s performance compared to the past days, weeks, months and years.  

Reading
“What is in a Database and Why Excel IS NOT a Database.” Valentina-Db, 4 Feb. 2017, www.valentina-db.com/dokuwiki/doku.php?id=valentina:products:adk:v4rev:howto:databases_from_zero:what_is_in_a_database_and_why_excel_isnt_a_database.

Phillips, Gavin. “Excel Vs. Access – Can a Spreadsheet Replace a Database?” MakeUseOf, 7 Nov. 2014, www.makeuseof.com/tag/excel-vs-access-can-spreadsheet-replace-database/.

Kilkelly, Michael. “How to Better Manage Your Project Data (or the Architect's guide to databases) - ArchSmarter -.” ArchSmarter, 17 Mar. 2015, archsmarter.com/manage-project-data/.

Summerfield, Jason. “Architectural File Management System & Database.” HSS Web Technologies, www.hswsolutions.com/work/case-studies/architecture-file-management-database/.

Migrator. “Benefits of database development.” Nibusinessinfo.co.uk, 8 Dec. 2017, www.nibusinessinfo.co.uk/content/benefits-database-development.


Comments:

B5- Databases in Construction Firms

 I would like to point out that construction firms, and firms involved with estimating highly depend on historical data of past projects aside from RS Means, because in some cases it may be more reliable than RS Means especially for productivity rates which are used for scheduling purposes. So even if RS Means produces an online version to it, these firms would still be more dependent on their historical data.

Object Oriented Databases - Hillinger

Carlos,
The examples of capabilities of relation and object-oriented database that you have given in your discussion have been useful. However, I don’t see how entities, relationships and attributes make a database, where I feel it would have been beneficial if you would have given a simple example to that and how may they be related.

Sarah Hollis - SQL

I appreciate the advantage of the disadvantage you have mentioned in regard to SQL, where it’s interesting how simple stuff such as dates, and not being able to distinguish a capital letter from a none capital letter.

Uses of Databases in Construction


You have done a great job with mentioning what are the capabilities of database use in construction. I have always heard of CMiC, but I never really knew what are its capabilities. I never even really considered it as database up until I’ve learned more about database by reading your discussion. In addition to reading others discussions about what database are or could be.   

Monday, February 12, 2018

B5 - Object-oriented databases


Databases are simply a compendium of information that are more easily accessed by organizing it into comprehensible packages or categories that can be related to keys throughout the system.  There are myriad types of models used for this process and some of the common logical data models can be seen below:

  • Hierarchical database model.
  • Network model.
  • Relational model.
  • Entity–relationship model. Enhanced entity–relationship model.
  • Object model.
  • Document model.
  • Entity–attribute–value model.
  • Star schema
A large extent of these utilize tables to store information and much of it works like a digital ladder, especially hierarchical based ones.  To examine the object-oriented approach, this concept allows for a more direct, and therefore faster retrieval of the data requested.  This task is completed by associating the elements with a particular language or often a visual graphic.  The required parameters for this are: class of data, extensibility, inheritance, and persistence.  These are general guidelines of all database management systems (DBMS's) though the object oriented method allows for a more user-friendly process and interface, while also allowing the necessary maintenance and upgrading of the system to be feasible for the programmers.


Comments:


Luciana,

I found the point of superimposing the OODB approach onto relational schema very interesting and would like to see how this is done.  I'm sure the original integration may be challenging, but the idea of updating a system with a new type of DBMS is an exciting one considering how much time it would save compared to creating a new one all-together.


Jianfeng,

You brought up some very good points on the collection of data, though I think much of databases are the organization and eventual use of said data.  There are numerous methods for this, of course, as are there for the collection as you have mentioned.


Chris,

I agree that databases are useful for all of the purposes listed above.  I think it would be very beneficial for not only the construction side of things, but for the design world as well if the paths for databases were simplified enough to be easily understood yet had the breadth needed for numerous request types.  For example, if someone within a firm wants to look up a similar detail for a previous job they had and re-purpose a model of special component then it can sometimes be a virtual nightmare to find exactly where it is if you are lacking the exact job information.  Using DBMS's such as object oriented databases they could potentially assign particular objects to category for easier retrieval based on what they know such as the type of room the model would be in, or perhaps its general specifications.  

 

B5-Object Oriented Database - Tangari

Object Oriented Database
An object oriented database or an object database management system (ODBMS) stores objects rather than data such as ingriedents, strings of real numbers. These objects are used in various languages such as C++ and Java.  They can contain attributes which is data that defines characteristics of an object and there are methods which define the behavior of an object.  These systems support the modelling and creation of the data as an object. The idea is that the object orientated database concepts can be superimposed on relational databases which are more commonly used.
Object Databases are a good choice for use in businesses that are high performing on complex data. This database is also used for less complex data because it allows for a smaller team and faster development because there is only one data model.  This database offers many advantages such as reduced maintenance, code reusability, real world modeling and improved reliability and flexibility. Real world modeling here has a more complete fashion where objects are organized into classes of objects and objects are associated with behaviors, its focus is on objects and not processing.
After to reading through the material that lead me to these above conclusions, my understanding of object oriented databases was still pretty weak.  With the video found through the following link my understanding is a more solid. Object oriented databases are better equip for storing complex data in comparison to relational databases which can store simpler data like employees names and hire dates where orientated data bases can store media, graphics, CAD and even geographical satellite information.  There is a terrific analogy referring the two to cars where OODMS is like a car that you drive into a parking garage and turn off the engine until you are ready to use it but relational data base you would have to break down the car into parts, put the pieces on different shelves then put it back together the next time you want to use it which leads to mistakes and errors.  A special language would be needed to put the relational information together as intended where OODMS would need no such language only to be told to start. Allowing data to be found where relational you would have to lock the table to change just one thing. Now I understand OODMS is capable of holding more complex data but is capable of being accused quickly and efficiently.

http://www.dba-oracle.com/t_object_oriented_approach.htm


Jianfeng Xiao
I like how you found an article that was able to relate back to how object oriented data bases could be used in creating a design. Having tools that are able to calculate data in an efficient and fast way such as the application you discussed will help designers and engineers make their projects more efficient and more functional.

Chris Thach
I agree that databases have come a long way in the construction world. Working on several projects over co-ops, I have seen how important databases can be even to keep track of small things such as employees, work hours, project hours and so on. This not only helps to keep projects organized and efficient but by being able to reference information in a quick and easy to use database allows for companies to be more liable and have proof and back up if something was to occur or if plans deviated from what was intended.

Carlos Hillinger
Your description of the difference between the two was great, I wish I had read it before performing my own research to get a better foundation of the difference. Some definitions out there are very complex and just understanding objects like photos and videos are what is put into object data bases versus code used for relational databases helps to understand why object orientated databases may be easier to manage.

Relational Database Theory - Deutsch - B5

Before diving directly into what "Relational Database Theory" is I think it is first important to fully comprehend how a database is defined, along with how Big Data is defined. 

In general, a database can be defined as any collection or storage of information that is valuable, organized, searchable and applicable. In other words, it allows for management of files and their records which can be searched, grouped, rearranged and cross-referenced to facilitate easy retrieval for its users. Databases can be organized in any number of ways that are most applicable for what is being structured. A new technique that is being used more commonly as of late, is combining separate databases into larger entities which are now defined as "data warehouses". This is done mostly to help assist in pattern recognition which just reinforces how important databases and data sources are. 

Next, there is Big Data. According to Cringely, "Big Data" can be defined as "the accumulation and analysis of information to extract meaning." Even though this definition is quite broad, I like how far it allows us to delve into how much data we use and rely on without even knowing or realizing that we do so. I feel as though Big Data is similar to the "data warehouses" I mentioned earlier. In the past, storage of data and the capability to analyze that data was expensive and not done as often. Ever since individual computers became a normalized thing, data collection and storage has become much easier and cheaper to keep records of. Big Data is important because it aids in predicting events, the safety of groups or individuals, problem solving and connecting seemingly unrelated events that would have never otherwise been noticed. 

BIM is similar to Big Data and data warehouses in the way that it is also its own "environment". What I mean is that we treat it like data warehouses when we combine separate Autodesk programs in order to complete a project and use them as cross references, as our guest speaker last week, Derek, had mentioned he does often. It is also used as Big Data in the way that it keeps and stores all information in an organized and applicable way that allows its files to be easily accessed and managed by all those who require it to do so. 

This takes me to Relational Database theory. As stated by Darwin "Relational database theory is built around the concept of a relation" which is meant to be taken from a mathematical standpoint so that any number of things can be more easily related. What is important to remember when thinking of this definition is that relationships between multiple characteristics or objects are relational and not exactly "equal to" and this can be shown most easily by using a table, or most specifically the tables given by Darwin himself:
This table does not depict a relation
This table does depict a relation

What is of utmost importance to note however, is that although the second picture does demonstrate relational data, it does not matter what order the columns and rows are shown in. This data in these tables shown can then be searched. When a this relational data is searched, it is called a "query". To output specific information, constraints dictated by the inputted "query statement" will be applied and this will produce the desired data. Microsoft makes a program named Access Database which allows you to set up your own relational tables and query it at the end. It can be done using any desired informational fields, whether large or small.
 Although I had never thought too much about databases until this term, this is now the second time I have come across it since we just used Microsoft Access in my AE T580 class to teach ourselves how to relate specific data we came up with ourselves in a simple way. As explained by Darwin the order in which we defined our relationships did not matter when we ran a query. Seeing this fact in action helped me understand relational database theory much better. 

Sources:

https://dvikan.no/ntnu-studentserver/kompendier/an-introduction-to-relational-database-theory.pdf

https://www.evernote.com/pub/aengineer/ae-510#st=p&n=b751f481-0f42-4f45-a51b-a77127a94351&t=ec0a31ef-f3b4-42b8-b58d-6ed4124da841

https://www.britannica.com/technology/database


Comments:

Dung Tran - 
I really like how you approach the main topic of relational databases by first defining databases in general. I did something similar in my post. I also think you did an exceptional job in explaining how the the math side of relational data, or the relational algebra, connects to the overall concept. I did not get the chance to check out Codd's research paper but it seems to be very helpful in understanding this broad and complicated theory.

Chris Thatch - 
I agree that databases are of utmost importance within the construction field, especially within the management aspect of things. I know that a lot more companies are making a bigger effort in going paperless in more recent years which would be very helpful when it comes to contributing to the databases already in existence. While this is more efficient, offices have found themselves actually using more paper. I wonder why this is, do you have any input? Also, could you define what RS Means is in a bit more detail? I have never heard of it but it seems to be quite important.

Jianfeng Xiao - 
Reading your post is very interesting. I like the examples you give that connect ways in which we use data readily available to us now through new technologies that make prior methods of achieving the same tasks obsolete. Data is such a useful tool when it comes to design because it allows for us to take what we know and apply it in smarter ways, hence smarter buildings and environments also! I will have to check out the articles you cited.