Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
    • About Us
    • Colophon
    • Survey
  • Reliability.fm
  • Articles
    • CRE Preparation Notes
    • NoMTBF
    • on Leadership & Career
      • Advanced Engineering Culture
      • ASQR&R
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Maintenance Management
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • RCM Blitz®
      • ReliabilityXperience
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Field Reliability Data Analysis
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability by Design
      • Reliability Competence
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
      • Reliability Knowledge
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Institute of Quality & Reliability
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Statistical Methods for Failure-Time Data
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Glossary
    • Feed Forward Publications
    • Openings
    • Books
    • Webinar Sources
    • Podcasts
  • Courses
    • Your Courses
    • Live Courses
      • Introduction to Reliability Engineering & Accelerated Testings Course Landing Page
      • Advanced Accelerated Testing Course Landing Page
    • Integral Concepts Courses
      • Reliability Analysis Methods Course Landing Page
      • Applied Reliability Analysis Course Landing Page
      • Statistics, Hypothesis Testing, & Regression Modeling Course Landing Page
      • Measurement System Assessment Course Landing Page
      • SPC & Process Capability Course Landing Page
      • Design of Experiments Course Landing Page
    • The Manufacturing Academy Courses
      • An Introduction to Reliability Engineering
      • Reliability Engineering Statistics
      • An Introduction to Quality Engineering
      • Quality Engineering Statistics
      • FMEA in Practice
      • Process Capability Analysis course
      • Root Cause Analysis and the 8D Corrective Action Process course
      • Return on Investment online course
    • Industrial Metallurgist Courses
    • FMEA courses Powered by The Luminous Group
    • Foundations of RCM online course
    • Reliability Engineering for Heavy Industry
    • How to be an Online Student
    • Quondam Courses
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home
  • Barringer Process Reliability Introduction Course Landing Page
  • Upcoming Live Events
You are here: Home / Articles / Using Simplified Technical English to Write Effective Maintenance Procedures

by James Kovacevic Leave a Comment

Using Simplified Technical English to Write Effective Maintenance Procedures

Reduce the Variability in Your Work Routines and Procedures

Based on our understanding of the six failure patterns, we can see that there is a large probability of failure when the equipment is first installed and started up.   One of the Englisch causes of this increase in probability is the fact that the equipment was not installed or maintained correctly.  This may be due to the installer or maintainer not using or following procedures.  Having procedures is the first step to reducing these failures, but the procedures must be written in a clear, easy to follow manner.  When writing procedures, it is critical to ensure that there are no interpretations in the written instructions.  How can this be accomplished?

The universal language for aviation is english, which is considered very safe and reliable.  How has this industry been able to overcome the fact that many of the people involved in aviation are not native English speakers?   How does a large company such as Boeing supply aircraft all over the world and the customers perform the maintenance in a consistent manner?  The aviation and defense industries use a controlled language by the name of Simplified Technical English.

What is Simplified Technical English?

Simplified Technical English is a controlled version of English, that is designed to help the users of English-language maintenance documentation understand what they read.  Technical writing can be complex and difficult to understand even for native English speakers.  Complex writing can be misunderstood, which may lead to accidents or premature failures.  Simplified Technical English makes procedures easy to understand and follow, eliminating language issues and reducing premature and maintenance induced failures.

Simplified Technical English provides a set of Writing Rules and a Dictionary of controlled vocabulary. The Writing Rules cover grammar and style.  The Dictionary specifies the words that can be used and those that can’t be used. For the words selected, there is only one word for one meaning and one part of speech for one word.  Some of the benefits of Simplified Technical English may include;

  • Reduce ambiguity
  • Improve the clarity of technical writing, especially procedural writing
  • Improve comprehension for people whose first language is not English
  • Improve Reliability concerns of maintenance and assembly by reducing their probability to introduce defects

The Simplified Technical English specification is not easy to learn, but there are training and software available (if you are interested in this standard, please visit the ASD Simplified Technical English website).   The detailed contents of the Simplified Technical English specification will not be covered, but instead, the rest of the post will cover what you can immediately do to make your procedures more readable and drive reliability.

Writing Procedures Using Simplified Technical English

So without becoming an expert in Simplified Technical English, how can you begin to write better procedures?   You can begin with some basic writing practices and by reviewing the procedures before it issued.  Some of the basic practices to use when writing procedures include;

  • Use short sentences. (The recommended maximum is 20 words in a procedural sentence and 25 words in a descriptive sentence.)
  • Restrict noun clusters to less than 3 nouns
  • Restrict paragraphs to less than 6 sentences
  • Avoid slang or jargon
  • Avoid the passive voice
  • Be as specific as possible
  • Use articles such as “a/an” and “the” wherever possible
  • Use simple verb tenses (past, present, and future)
  • Write sequential steps as separate sentences
  • Put commands first in warnings and cautions, with the exception of conditions
    • For example, write Make sure that the valve is open. Do not write Make sure the valve is open.Use the conjunction that after subordinate clauses that use verbs such as make sure and show.
  • Introduce a list item with a dash (hyphen).

Once the procedure is written, be sure to review and delete any information which is not relevant (i.e. Instead of synthetic lubricating oil, use only).  well-written should help in eliminating any interpretation and driving clarity.

Here is an example of how the wording of a procedural step could be open to interpretation.  The task “Replace the filter” could mean either of the following:

  • Put back the filter that you took out.
  • Install a new filter.

Now you can see how one person may perform a task and how another would perform it differently.  Once the task is clear, a technical specification should be added to ensure the task is performed to a standard such as;

  • Tighten to 15 ft-lbs

The end result of ensuring the task is clear, and a specification is present is “Install a new filter and tighten to 15 ft-lbs”  This task is simple, clear and easy to understand.

When following these basic steps a well written procedure will be developed to ensure clarity and repeatability, thereby reducing maintenance induced failures.  Do you use a Simplified Technical English or a form of it in your procedures or job plans?  If not, how are you actively working to reduce maintenance induced and start-up related failures?

Remember, to find success, you must first solve the problem, then achieve the implementation of the solution, and finally sustain winning results.

I’m James Kovacevic
Eruditio, LLC
Where Education Meets Application
Follow @EruditioLLC

References;

  • ASD Simplified Technical English, Specification ASD-STE100

 

Filed Under: Articles, Maintenance and Reliability, on Maintenance Reliability

About James Kovacevic

James is a trainer, speaker, and consultant that specializes in bringing profitability, productivity, availability, and sustainability to manufacturers around the globe.

Through his career, James has made it his personal mission to make industry a profitable place; where individuals and manufacturers possess the resources, knowledge, and courage to sustainably lower their operating costs.

« Address Your LOI Before Your ROI
Is Making Assumptions Similar to Making Mistakes »

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Maintenance & Reliability series


by James Kovacevic

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

Recent Articles

  • Today’s Gremlin – It’ll never work here
  • How a Mission Statement Drives Behavioral Change in Organizations
  • Gremlins today
  • The Power of Vision in Leadership and Organizational Success
  • 3 Types of MTBF Stories

© 2025 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy