For our capstone project, we have to write code for sensor components in the design. It was my responsibility as well as another team member to take care of the code. At first, we would constantly talk to each other to ask each other what the other did in the code. We would always need to understand what the other wrote because neither of us really understood what the other was trying to accomplish. It went on like this for about a week until we both decided to start writing comments in our code. After that simple method of logging, we saved so much time from needlessly cross-referencing and immediately were on the same page. I knew what code he was writing, and he knew what code I was writing. Logging that kind of data was very useful because it got us on the same page. We split the code up as alpha versions, e.g., v0.1, v0.2, v0.3, etc. This was to help us keep track of each iteration. Logging helped me save time and provided a reference for each bit of work we did during the duration of the project.

Keeping a log for my current positions is critical. Each meeting, each dollar spent, each appointment, and summary of the nature of the appointments must be submitted to the Director of the EOP program. As a Project Coordinator, I am responsible for making sure that each tutor knows the rules and regulations of NJIT as well as the standards for this program. All tutoring hours, appointments must take place on campus in order to avoid any liability issue. In order to do that, each tutor must be a record of their appointments, time, meeting place, and approved by me. This record log makes sure If an incident was to occur, I can go back to my record log and see which tutor was assisting a particular student.

At the end of the semester, this record log for all intents and purposes is reviewed by me, the director of the program and the assistant director. A evaluation report is generated by me and then approved by all parties responsible for this program. Therefore, keeping a log in my current position is very important and always used as a reference to make future adjustments to the program.

While working at General Dynamics Electric Boat, I would hold bi-weekly teleconferences with all parties involved in the project. This included people at the Naval Research Laboratory, Lockheed Martin, other vendors, and gov officials. During this meeting, I would take meeting minutes and at the end of each meeting email them out along with a list of action items and when those actions need to be completed. A lot happened during these meetings and even though it was just two weeks between meetings, we would always forget what was said at one meeting or another. The meeting minutes kept a log of everything we completed in those weeks and where we were. This helped if anyone was out of this office and made sure everyone was held accountable and progress continued efficiently. It helped us all see the big picture of what everyone was contributing and gave a time for us to work through problems and plan for the future.

For one of my projects at work I had to figure out a way to sort through a whole bunch of data and easily find something that was needed. Because we use MATLAB in school, I decided to use MATLAB to do what I needed. I began writing a whole bunch of lines of code and it turned out that the code was taking longer than I expected. The next day when I began to work on the code, I forgot what some of the lines of code did and what they were used for. Unfortunately, I had to restart because at that point it would have taken me longer to figure out what the line meant than to start over. Once I restarted, I began commenting the lines of code so that I can easily figure out what it did. Not only that, when I submitted the program to my boss, she also wanted to see how the code worked. With the comments she was easily able to figure out what was running and she could easily change whatever she needed to sort through the data.

For my capstone project, I found it very important to log every step of the process, Even the small details and changes I made to the entire thing. My team and I started was one intention to the design and ended up with a lot of changes that we sometimes forgot that we made and if we hadn't written all the details of the changes we would have been repeating unnecessary steps and design ideas. Keeping a log of why we made those specific changes or the thoughts on a specific area of the design really helped us moving forward and saving a lot of time and effort. We could easily refer back to changes and explanations when asked by the instructor.

At my current job validating and verifying medical devices, it is extremely important to keep an accurate detailed notebook of everything down in the laboratory. This is critical because the devices take upwards of 14 hours to pass all the testing required for them to meet specifications and be deemed fit for hospitals and analytical laboratories. Due to the long testing, multiple employees could be validating/ verifying each instrument as it goes through its testing phase. As one 8 hour shift ends, the next employee has to be able to seamlessly pick up on the testing responsibilities; knowing each and every detail of every passed/ failed test (hundreds of individual tests). Without the detailed log, this task would be made extremely difficult if not impossible and valuable time/ money/ recourses would be wasted that could otherwise be utilized elsewhere in the company. These highly detailed logs are also of the utmost importance when the FDA audits the company. If the information contained within the electronic notebook was either missing or incorrect, massive consequences would result to both the individual responsible and possibly the entire project.

During one of my internships during my senior year for undergraduate, I worked a lot with the design and validation and verification of a product's design. So I often had to run these products through many tests ensuring that they're up to specification and they're meeting certain standards. I worked there for about five months and within those five months keeping track of previous work was a definite big help. Because of this I was able to see what aspects of a design worked and didn't work when it came to meeting a certain specification. Not only did my previous logged work help, but because I had access to the logged work of previous interns before me I was able to see how the design of a product basically transformed and matured. This just really highlights how important it is for a company to log their work as it helps both current and new employees coming in taking over the project.

During one of my co-op experience, I worked with the design and instrument validation of many measuring devices. As a result, I was involved keeping critical notes on file because validation of a device is not something that can be finished easily without running multiple variations of the tests. Many times, I had to refer to my own notes to see on how the specific test was performed and outcome of the test. Because of this log keeping, I was also able to describe my tests ran and the results to the weekly team meetings without any confusion. This has also helped the company during any regulatory audits. For example, if FDA comes in for an audit and request the specific device validation protocol, the auditor will see the step by step procedures on how the machine was validated. This will limit the auditor from asking questions. All in all, it is really important for a company to keep track of design validation as well as project completion by logging in the work as it helps the individual looking at it and the company in making the best decisions in the future.

Logging work is definitely an important aspect of research and development for any company. When I started working for my current company about 2 years ago logged research was essential in helping me understand how the research progressed and the key experiments that lead to certain thought processes on how to move forward with the research. Experimental research protocols are logged both on the computer and hard copies are also kept of all experiments conducted with discussions and conclusions on what was learnt from conducting the experiment and what the next steps will be in future experiments. Also as mentioned by Dr. Simon there was something similar to a lessons learned section in order to avoid repeated mistakes and strange observations that were observed during a new protocol. The hard copy books are also photocopied and stored for FDA audits as backups to the computer data, so that there is always a physical backup.This logging of work has proved beneficial in keeping track of the many experiments conducted and allowed for ease of tracking of the thought process between research steps taken.

Logging information is essential for progress in a project. Working in automation, we keep daily fault logs for the computer system and the robot error codes in order to have a full time table of the day to see how efficient the machine is running. Any fault that occurs too often is escalated and dealt with as soon as possible. Not only that, but logging everything that goes wrong is the best way to learn a new process or procedure, and for new people to learn from as well. This also includes several system updates, software updates, and SOPs which all come about because of logging in all the information that is done over time.

Currently I am working in a laboratory where I keep updating of my work in the sheets where we always share everything so that each of a lab member who works in the research has access of all the events taking place at present. Since we are running a human research project the recruitment work is handled by me were I always update everything in sheets. So that the person who is going to come after me can even handle everything. Keeping a log of events is really a useful one. Even the log should consist of constructive details so that it will be helpful for further analysis. Even if we leave it and later another research work can be handled with this piece of information. And even storing of data at various places is also important.

At my current job, logging and lack thereof, has proven to be far more critical than anticipated. As I work primarily in R&D and am responsible for much of the new product development, logging my work in a registered laboratory notebook is critical. The project I am currently working on is already on its 16th formulation, and tracking each change and its result on the end product is vital in order to determine what next step to take. In addition, the project that I am working on is a carry over from our previous formulation chemist. Much of the difficulty in this challenge comes from the fact that the previous chemist failed to log enough information in their laboratory notebook. While some of the information is there, much of it is missing and has to be rehashed by myself and the rest of the team. Many man hours and research could have been saved had adequate logging been employed by the previous project lead. There has been an enhanced focus on logging with detail on all projects moving forward.

Logging the work that you do is extremely important.

An example of this is a recent event at my current workplace. The telemetry system had gone down and I was called in to repair it. This just so happened to occur on an observed holiday. I logged everything that was done that day, as well as the fix to the issue. This is important for different reasons the first being RCA meetings. Having this log allows me to have something to look back on in future meetings vs relying on memory of an event from weeks ago. A second reason is that anyone can look at this log and have an idea of what can fix the issue they are having(assuming they are experiencing an event with similar issues).

Logging your work is very important when you are working on a project as a team as there are people working on different parts of a certain project and projects take time. Logging/commenting will help when people leave the project midway or when somebody is unavailable and another guy has to cover. The other guy will take less time to understand the project due to proper logging of the various tasks of the project. This will save time as well as help to finish the project on time.