Posts Tagged ‘Process’

Know More About Chemical Process Plant

Wednesday, September 22nd, 2010

A chemical process plant is meant for creating an industrial environment to manufacture various chemicals. In some of these plants, chemicals are being processed into new materials. In order to produce different products & chemicals, complex chemical processes are needed to be carried out.

There are several steps involved in a chemical process plant known as unit operations. A particular unit operation is generally carried out in a separate area, or unit, of the chemical process plant. These units are interconnected to one another in a way that allows materials to be transported to the next unit when each unit operation is complete.

Chemicals and chemical-based products are known be inherited from other objects. The first unit operation in a chemical process plant includes input of raw materials, known as feedstocks. A feedstock refers to the first input of raw materials, or material inducting into a certain unit. The output resulted from a certain unit operation is known as matter. It can refer to matter that has completed the entire chemical process and ready to come out of the plant. Often, a chemical product or chemical requires only one unit operation whereas output originated form one unit operation may be used as a feedstock.

The construction of a chemical process plant requires lot of efforts as it is a complex process requires not only buildings and offices but more consideration into plant architecture.

The feedstocks and output from these plants may cause serious implications to environmental health. A single mistake in chemical process can cost high to human and animal health. Chemical engineers should use high quality process plant and machinery to ensure good quality output.

Since there are numerous chemical processes employed and outputs vary, there is no set standard chemical plant. Design often based on a number of important factors, including temperature and location.

Green Plant is a UK based quality equipment Provider Company, specializes in new and used chemical process plant equipments & machinery, stainless steel tanks, reactors, mixers, mono pumps, and vessels to all industries.

Software Development Process

Wednesday, August 25th, 2010

A software development process is a structure imposed on the development of a software product. Synonyms include software life cycle and software process. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process. . Let us see the steps involve in any software development.

Domain Analysis

Often the first step in attempting to design a new piece of software, whether it be an addition to an existing software, a new application, a new subsystem or a whole new system, is what is generally referred to as “Domain Analysis”. Assuming that the developers (including the analysts) are not sufficiently knowledgeable in the subject area of the new software, the first task is to investigate the so-called “domain” of the software. The more knowledgeable they are about the domain already, the less the work required. Another objective of this work is to make the analysts who will later try to elicit and gather the requirements from the area experts or professionals, speak with them in the domain’s own terminology and to better understand what is being said by these people. Otherwise they will not be taken seriously. So, this phase is an important prelude to extracting and gathering the requirements.

Software Elements Analysis

The most important task in creating a software product is extracting the requirements. Clients typically know what they want, but not what software should do, while incomplete, ambiguous or contradictory requirements are recognized by skilled and experienced software engineers. Frequently demonstrating live code may help reduce the risk that the requirements are incorrect.

Specification

Specification is the task of precisely describing the software to be written, possibly in a rigorous way. In practice, most successful specifications are written to understand and fine-tune applications that were already well-developed, although safety-critical software systems are often carefully specified prior to application development. Specifications are most important for external interfaces that must remain stable.

Implementation (or coding)

Reducing a design to code may be the most obvious part of the software engineering job, but it is not necessarily the largest portion.

Testing

Testing of parts of software, especially where code by two different engineers must work together falls to the software engineer.

Documentation

An important (and often overlooked) task is documenting the internal design of software for the purpose of future maintenance and enhancement. Documentation is most important for external interfaces.

Software Training and Support

A large percentage of software projects fail because the developers fail to realize that it doesn’t matter how much time and planning a development team puts into creating software if nobody in an organization ends up using it. People are occasionally resistant to change and avoid venturing into an unfamiliar area so, as a part of the deployment phase, it is very important to have training classes for the most enthusiastic software users (build excitement and confidence), shifting the training towards the neutral users intermixed with the avid supporters, and finally incorporate the rest of the organization into adopting the new software. Users will have lots of questions and software problems which lead to the next phase of software.

Maintenance

Maintaining and enhancing software to cope with newly discovered problems or new requirements can take far more time than the initial development of the software. Not only may it be necessary to add code that does not fit the original design but just determining how software works at some point after it is completed may require significant effort by a software engineer. About ? of all software engineering work is maintenance, but this statistic can be misleading. A small part of that is fixing bugs. Most maintenance is extending systems to do new things, which in many ways can be considered new work.

SehelSoft team specialized in Visual basic solutions with both Access and SQL database.
Expertises are available for .Net and PHP solutions as well.

Encyclopedia

5 Tips for Fresh Process Engineers

Tuesday, July 6th, 2010

I received an email from a fresh engineer 7 days ago. After reading his email, I thought of answering his question inside my blog (off course for the benefit of other young engineers and those who’ll be graduating soon).

The email message was something like the this:
“I’m Fahmi. I know you from your chem-eng blog. I want to ask for your advice. I just started working as a production engineer in an oleochemical plant in Klang. As a fresh graduate, I am a bit lost on what should I learn as an engineer. If possible, I want to know how you learn when you are a process engineer.”

Well, the email stops there and after reading his email, I thought of responding immediately. However, due to certain constraint, I delayed responding to his email. Now, I’m going to share some of my experiences when I started working as a process engineer. Some of them might be OK for you to follow, while some others might not. Judge and justify them yourself.

1. Get to know everybody as soon as possible. When I first be a process engineer, I make sure I know all engineers, executives, supervisors, technicians, fitters, plant operators and event store clerk as soon as possible. Why? Simply because I’ll be dealing with them all the time throughout my daily job At least you know their name and create a common interest with them. This will ease and create good relationship with them. However, do not be too close with your down line manpower. There’s a reason for this which I’ll cover some other day (please remind me if I forgot).

2. Get to know the process of your plant. This is very important because you are a process engineer and you need to know the detail of the processes in your plant. First of all, you need to get the PID diagram of your plant. Identify and learn the lines, pumps, valves, heat exchangers, tanks and other important units in the PID diagram. Then, go to the plant and trace the lines and compare it with the PID diagram. If it is difficult for you to trace the lines (pipelines), ask a supervisor or plant operator to help and guide you. This is also the reason why I provide tips #1. The job will be easier if you know the right people to help you. As for me, I was assiged to traced each and every valve in my plants. In order to do that, I need not only to trace the lines but also identify all types of valves in the plant. There are basically hundreds of valves installed in the plant. It was tough but after the exercise, I was able to trace the lines, process and know all type of valves.

3. Learn everything as fast as possible. This is very important and is too much to elaborate. You need to be able to pick up everything you learn from your manager, other engineers and executives. Don’t be shy to ask from your supervisors, plant operators, technicians and fitters. They have the skill and knowledge that you don’t have when you first enter the plant. Learn from all of them. Integrate what they know with what you’ve learn during your degree. Create and maintain a log book to record everything that is important. Avoid remembering because you might forget. Another way of learning is by asking to the suppliers or vendors. They are the expert of the product or service that they are selling. Hence, don’t be shy to asked from them. They’ll provide technical information that is important for you. I’ve done this a lot of time and I appreciate their explanation and teachings. Some times, suppliers / vendors will offer in house training for you and your colleagues. At the end of the day, if you are able to perform your duty as a process engineer smoothly, effectively and efficiently, you’ll get good reward from your boss…

Being a process engineer, you need to be able to prepare and produce reports to be presented to your superiors. Understanding the report and preparing them is crucial. Normally, you have various types of reports to prepare such as daily report, monthly report, costing report, meeting minutes reports and others. So, make sure you prepare good report.

4. Understand the politics in your workplace. This is very important. You need to know how things are going on in your plant/factory. This is very subjective and not thought in any chemical engineering text book. You need to get the information and knowledge from various people in your organization. That’s why point #1 (above) is vital. Some companies have a culture which will blame somebody else for any errors occuring and this is not healthy. Some other cultures are professional and will accept responsibility of any problem.

5. Communicate properly. This is very important as a process engineer because you’ll receive instruction and also provide instruction to your supervisors and plant operators. You need to possess good communication skills to ensure all mesagges and directions are conveyed correctly. Delegate your jobs to your downline with clear cut informations. What we practice in our plant is to have an instruction recording book. Every shifts should refer and sign the book to acknowledged that they read the instruction. This is different from the quality and recording books. If they have problem comprehending the instruction, they should call us for further clarification. Failure to receive and provide correct instruction will lead to massive errors which will make your life misserable in later stage. So, please, ensure you communicate properly.

Conclusion

Those are just 5 tips for me to share for the time being. I never asked anybody for the tips. I figured them myself and I compile it (in this post) for the benefit of new process engineers. I’m glad that I managed to know everybody and learn lots of thing quickly. Being a successful engineer is critical for your career development. In later stage, you’ll get promoted as a senior engineer before becoming a manager. If you are lucky, somebody (head/job hunter) will search you because they know you are an engineer with such a great caliber and offer you better remuneration.