Specifications from the context of engineering.
The term "Engineering specifications" is used differently in different technical contexts they often refer to particular documents or particular information within them. It is the records of the information processing equipment with detailed documentation of its construction, wiring, arrangement and its related engineering details.These are the set of goals that inorder to achieve, it is necessary to meet the user's requirements. Engineering specifications are quantitative, which a product is designed to satisfy that includes engineering units commonly defined and adopted by convention and law and is used as a standard for measurement of the same physical quantity of any amount. Specifications are the restatement of the design problem in terms of parameters that can be measured and have target values. With the specifications you will learn to use the house of quality methodology.
The What, Why and How of Engineering Specifications.
-What: Capture the Appropriate Amount of the Right Information. What does an effective engineering specification look like?
At the most basic level, specs are a group of documents detailing requirements for a product, process or material. An effective engineering specification capture the amount of the right information. Your specs present requirements that are not covered by regulatory bodies and industry codes. To be effective, specs should be almost impossible to misread or misinterpret, written in clear, precise language explicit, but not so detailed they require constant clarifications or deviation requests from your vendors or fabricatorsconcise yet comprehensive, stating precisely what you need, what you prefer, and what you’re not willing to accept.
-Why: Reduce Errors, Save Time and Manage Risk
Having specs for these topics mean that every time you kick off a project, you aren’t starting from scratch, giving you a running start. If your specs aren’t written clearly, they’re easy to misinterpret. Having a set of reliable, well-reviewed specs saves you time and effort when undertaking projects. Similarly, confusingly structured information might lead your suppliers to miss some of your requirements. If you provide the wrong materials to site, your project might fall behind schedule or your facility’s downtime might increase, costing you money. Effective specs also help to mitigate risk. In the event of legal or regulatory challenges, safety incidents or environmental problems, you need to be able to produce documented proof that your company isn’t at fault. If your specs are missing important requirements, conflict with code, or contradict other information your company provides, you could be liable.
How: Improve Readability, Write Unambiguously, Eliminate Redundancy
Best practices in preparing specifications.
Best practices for writing specifications includes applying the Five Cs of communication. Your specs need to be clear, concise, correct, complete and consistent. Professional technical writers and editors with experience in the engineering and energy industries can help.
Specifications need to use simple language and short sentences. A lot of technical documents are written to impress, not to inform. It captures each requirement in a single, numbered statement or clause, avoid lumping together several requirements in a “wall of words” that will let readers skim over. It should state explicitly who is responsible for each requirement. Using the active voice helps—for example, state “The Vendor shall provide suitable protection for all pipes” rather than “Suitable protection for all pipes shall be provided.” The latter statement is unclear as to who is responsible. It should eliminate redundancy and contradictions. Repeating similar information introduces the possibility that one statement will contradict another, or that a reader could wilfully “cherry pick” one interpretation over another. It should be streamline, wherein if your company has recently acquired another company that had its own specs, it’s important to reconcile and harmonize them before confusion sets in.
Section 5 (a) of RA 10915 which embraces preparation of specifications for what ABE fields of specialization and relate to the use of Code of technical standards in aiding the preparation of specifications.
The specifications of ABE such as preparation of engineering designs, plans, specifications, project studies, feasibility studies and estimates of irrigation and drainage, soil and water conservation and management systems and facilities, agrometeorological systems, agricultural and biosystems power, and machinery, agricultural and biosystems buildings and structures, renewable/bio-energy systems and farm electrification, agricultural and bio-processing and post harvest facilities and system, agricultural and biological waste utilization and management, agricultural and bio-information system, agricultural and biosystems resource conservation and management, and agricultural and bio-automation and instrumentation system, which embraces preparation for Agricultural and Biosystems Power and Machinery; Irrigation and Drainage Engineering, Soil and Water Conservation Engineering, Agricultural and Biosystems Buildings and SStructures, Agricultural and Bio-process Engineering, Food Engineering, Renewable/Bio-Energy and Farm Electrificatio, Agricultural and Biological Waste Management, Aquacultural Engineerin, Forest Engineering, Agricultural and Biosystems Automation and IInstrumentatio, Agricultural and Bio-Information System, Agrometeorology, an Agricultural and Biological Resource Conservation and Management shall be in accordance to Philippine Agricultural and Biosystems Engineering Standards (PABES) and shall serve as Code of Technical Standards of all registered and licensed agricultural and biosystems engineers in the practice of their profession.
Keep posting, I'll stay updated...