Simplified Technical English Archives | Page 5 of 5 | Shufrans TechDocs Home // Simplified Technical English Archives | Page 5 of 5 | Shufrans TechDocs

Dozuki Workshop Series – Optimize your technical content (Part 1 of 3)

Dozuki Workshop Series – Optimize your technical content (Part 1 of 3)

Your content matters

To follow-up with the audience on the webinar session on 26 July 2016, we will share in more detail some examples of how you can prepare your content for optimum re-use, readability, and translatability.

In the three-part text analysis that follows, we will highlight areas for improvement, then provide the same information based on Simplified Technical English (STE) writing rules.

 

Replace iphone 5c power button STE

 

RULE: 1.2 Use approved words from the Dictionary only as the part of speech given.

1a) Standard English:

If your display is cracked, keep further breakage contained and prevent bodily harm during your repair by taping the glass.

1b) STE:

If there are cracks in your display glass, use tape to prevent more damage and possible injuries.

Analysis:

‘Crack’ is only approved as an STE technical noun, not a verb. For this reason, we changed the past participle form ‘cracked’ to ‘cracks’.

It is also not advisable to use fake verbs or a passive construction such as ‘by taping’ in your sentence. This is a violation of rule 1.2 where ‘tape’ is used only as a noun, and also hides the doer of the action. Instead, write ‘use tape to prevent more damage..’ to sound more direct.

We also removed unnecessary phrasings like ‘keep further breakage contained’ and ‘bodily harm’, substituting them with the simple verb ‘to prevent’, and unambiguous words such as ‘more damage’ to the equipment, and ‘possible injuries’ to the user for a more concise sentence construction.

 

RULE: 1.6 Use a Technical Name only as a noun, not as a verb.

2a) Standard English:

Lay overlapping strips of clear packing tape over the iPhone’s display until the whole face is covered.

2b) STE:

Make a cover for the full display glass area with overlapping strips of clear tape.

Analysis:

‘Cover’ is a non-approved verb in STE. Instead, use ‘cover’ as a technical noun. In this sentence pair above, we removed redundant words like ‘lay’, ‘over’, and ‘until’. The result is a concise, more direct sentence for the reader to complete his task more quickly and efficiently.

 

RULE: 1.3 Keep to the approved meaning of a word in the Dictionary. Do not use the word with any other meaning.

3a) Standard English:

This will keep glass shards contained and provide structural integrity when prying and lifting the display.

3b) STE:

This will keep glass shards together and give structural integrity when you move the display.

Analysis:

The STE verb ‘contain’ is defined as to have in something or to hold in something. The approved STE adverb ‘together’ appears simpler in meaning and more accurately describes the situation.

‘Provide’ as an unapproved STE verb is replaced with ‘give’, a shorter and more direct alternative.

‘Prying’ and ‘lifting’ can easily be described as ‘to move’. We hardly need to go into detail yet about prying and lifting as we risk confusing the reader at this point in time. Also, the –ing form or present participle verb form is not used in STE unless it is part of a technical name. For instance: lighting, missing, servicing.

 

RULE: 1.3 Keep to the approved meaning of a word in the Dictionary. Do not use the word with any other meaning.

4a) Standard English:

Wear safety glasses to protect your eyes from any glass shaken free during the repair.

4b) STE:

Use safety glasses for eye protection during the repair. 

Analysis:

‘Wear’ is defined as the action of becoming damaged as a result of friction. For other possibly valid meanings of ‘wear’, STE prefers the verbs ‘use’ or ‘put on’ safety glasses.

Further reading: Dozuki Workshop Series – Optimize your technical content (Part 2 of 3)

 

Missed this session? The on-demand presentation is now available below.

 

 


Shumin Chen

About the speaker

Since 2006, Ms Shumin Chen has been working as a consultant with customers in various industries worldwide: aerospace and defence, banking, consumer products, healthcare, IT, medical and fitness equipment. She has helped many companies with their documentation needs, based on standards where possible, and is widely regarded as a leading expert in ASD-STE100 Simplified Technical English training, aviation documentation and multilingual documentation.

Ms Chen now heads the ASD-STE100 training arm of Shufrans TechDocs. In her current role, Ms Chen continues to focus on the practical implementation of international standards to facilitate the efficient creation and management of multilingual documentation.

Copyright © 2016 Shufrans TechDocs. All rights reserved. No part of this article may be reproduced or transmitted in any form or by any means whatsoever without express written permission from the author, except in the case of brief quotations embodied in critical articles and reviews. 

Sounds interesting?

For a list of STE approved and non-approved verbs, drop us a line!

Request for the STE verbs list

 

Why S1000D recommends the use of Simplified Technical English, or ASD-STE100?

Why S1000D recommends the use of Simplified Technical English, or ASD-STE100?

ASD-STE100 is mandated by several commercial and military specifications (MIL-SPEC) that control the style and content of maintenance documentation. Military defence standards (MIL-SPEC / MIL-STD) such as MIL-STD-3048, as well as technical documentation standards like S1000D and ATA iSpec 2200 recommend the use of ASD-STE100.

Join us for a live conversation with Shumin Chen, Head of Training and ASD-STE100 Implementation at Shufrans TechDocs, on Tuesday July 26th, 2016 at 11:00AM (PDT) to learn more about this controlled English standard, and the online resources that are made freely available to you!

 

 

Future-proof your technical English writing skills

Future-proof your technical English writing skills

In this year’s economic slowdown, training budgets are often the first to shrink, if not, put on hold, as companies try to reduce costs in all areas. Unfortunately, businesses also start to see a direct impact on their level of competitiveness and overall success when they do not continue to invest in employee training.

Thankfully, many quality assurance (QA) managers know about the importance of documentation and the importance of standards to support their documentation.

QA managers recognise that to continue to deliver high quality services and products to their customers, their companies cannot stop investing in competence development to improve their employees’ skills, knowledge and career confidence. Motivated employees suggest a more promising outlook for any business’ future.

Reasons for acquiring Simplified Technical English (STE) writing skills as a professional asset

English happens to be a very rich language, meaning that, amongst other things, it has a huge vocabulary.

English has about three times as many words as French or German. However, in French or German you can say just the same things that you can say in English.

This implies that English has redundant or ambiguous words. Also, English grammar is a problem even for most native English speakers, and it can be highly confusing especially to people who speak English as a second language. Therefore, we want to try and do away with this huge, unnecessary part of the vocabulary, and we want to simplify grammar to what is essential to getting our message across.

Keeping your technical content concise yet precise – the basic principles of STE

1) Only use one word for one function, procedure or object.

2) Use each word in the ASD-STE100 dictionary based on its defined meaning and specific part of speech only.

3)Write only one instruction per sentence.

Most importantly, Simplified English is unique because this is a very balanced, and rather complete set of rules. It was not based on the personal preferences of just one or two people, but a whole committee that has developed this standard.

Working with great partners from all over the world to bring you high quality training workshop events

Certified STE workshops Spring 2016

Organised in collaboration with partners in Holland, Germany, Austria, India and Russia, our global Simplified Technical English (STE) workshops deliver high-quality training content that allows participants to create technical content in STE with great ease and 100% confidence.

Training offers in spring

Our STE training workshops equip technical communication professionals with the skills and confidence to create user-friendly and readable technical documentation, making it easier to translate, or doing away with the need for translations altogether. Refer to our STE training schedule below:

  1. Singapore, 3 – 4 March 2016
  2. Hyderabad & Bangalore, India, 10 – 15 March 2016
  3. Berlin, Germany, 4 – 5 April 2016
  4. Tiel, the Netherlands, 21 – 22 April 2016
  5. Helsinki, Finland, 9 – 10 May 2016
  6. St Petersburg, Russia, 19 – 20 May 2016

For more information on Shufrans’ training courses, please refer to our training page. Shufrans also offers customised ASD-STE100 training solutions that are tailored to meet your specific business requirements. These training workshops are usually conducted on-site at the customer’s premises or at our offices in Singapore.

To register for one of our open STE training classes, call +65 9777 4730 or email register@shufrans-techdocs.com.

 

Copyright © 2016 Shufrans TechDocs. All rights reserved. No part of this article may be reproduced or transmitted in any form or by any means whatsoever without express written permission from the author, except in the case of brief quotations embodied in critical articles and reviews. 

Are you ready to make STE your strategic partner?

Explore our FAQ section below.
Your Tactical Advantage | Emirates Defence Industries Company

Your Tactical Advantage | Emirates Defence Industries Company

STE as part of your global content strategy

Simplified Technical English as part of your content strategy

EDGE is creating opportunities in autonomous capabilities, directed energy, cyber-physical systems, advanced propulsion systems, robotics and smart materials, with artificial intelligence embedded across its products and services. Transforming how we live, and ensuring a more secure future, is what we do. Our mission is to bring innovative technologies and services to market with greater speed and efficiency.

ASD-STE100 Simplified Technical English (STE) is a controlled language that is used to write technical manuals in such a way that they can be more easily understood by an international audience. To put it across plainly, STE is a form of controlled language that is guided by 53 technical writing rules that were put together by a committee of linguists, engineers, and manufacturers who established over the years that these writing rules made sense and allowed them to re-write any of their existing documentation based on these rules, making their documentation easier to understand, while maintaining accuracy, safety, and validity.

Develop, deploy, and deliver documentation with STE

STE Quick facts

Background: With the widespread dissemination of user documentation published in various delivery formats across several language translations, the relevance of global information management has become greater in an attempt to stem terminology inconsistencies, mistranslations, and the disproportionate escalation of costs associated with the maintenance, reuse, and consumption of technical content.

Year: In use since 1986

Current Version: Issue 8, May 2021.

Technical writing rules: 53

Dictionary word entries: approx. 2400 terms.

The STE specification also includes a core vocabulary of around 930 approved words and 1500 non-approved words that let technical authors write just about everything that they need for for procedural and descriptive texts. Therefore, the use of approved words, compliance with the standard, and a language quality checker tool to complement your content strategy efforts is akin to pooling your most valuable resources where people, internal processes, and innovative technologies become more aligned.

 

The role of technical authors and technical documentation managers

Technical writers are the go-between for subject-matter-experts (SMEs), engineers, designers and the end-users of documentation. Consequently, the responsibility of creating effective documentation falls on technical authors who will then endeavour to send out a clear, unambiguous, and user-friendly message about their products and line of services.

At the level of global information management, technical writing professionals should consider short-term tactics and longer-term strategies to overcome the following:

  • An ever-increasing volume of words to write and translate
  • Snowballing translation and documentation management costs
  • Overlapping information across different versions of similar document types
  • Low comprehension levels for the English language jargon.

STE in practice

If this is your first time hearing about STE, the example that follows will hopefully shed more light on the principles and best practices that govern good STE writing. Here is an original piece of text presented in standard English writing:

THE SYNTHETIC LUBRICATING OIL USED IN THIS ENGINE CONTAINS ADDITIVES WHICH, IF ALLOWED TO COME INTO CONTACT WITH THE SKIN FOR PROLONGED PERIODS, CAN BE TOXIC THROUGH ABSORPTION.

And here it is again in STE:

THE OIL IS POISONOUS. DO NOT GET THE ENGINE OIL ON YOUR SKIN.  IT CAN GO THROUGH YOUR SKIN AND INTO YOUR BODY.

Making the comparison between the two types of writing above, you will see that the original writing is rather cumbersome in expression. It is also very likely that the person reading this sentence will have difficulties following the writer’s line of thought because of the longer sentence length and unnecessary information included. In contrast, the text written in STE is much more to the point and simply distils what is pertinent to the person doing this work:

  1. The oil is poisonous.
  2. I must always be careful not to touch oil without protection.

From this example, STE shows us that warnings and cautions must always start with a simple and clear command that is usually substantiated by a reasoning that comes before or after.  A command informs the user about the precautionary measures to take to avoid danger. Presenting information as if it were a general comment in the original writing obscures the importance of the message and is not specific enough.

 

What customers are saying.. | NIMR Automotive

Thuraya Al Mehrzi, Production Engineer, NIMR Automotive
“Shumin gave a good introduction to Simplified Technical English. Instead of writing long sentences that are difficult to read, I prefer the STE rule of presenting long sentences in a list that makes it much easier to understand the work that is required to be completed. The STE exercises were pretty engaging, and this is particularly so for day 2 of the rewriting workshop that gave the team a lot of insight into our documentation. Trainees also had the opportunity to replace many unapproved standard English words with STE ones that helped us better appreciate the application of STE rules in a real-world context. This is a training that I have rated 10/10 for.”

Nour Bazuhair, Engineer Trainee, NIMR Automotive “The introduction to Simplified Technical English (STE) was simple to follow and understand. Rule 1.4 to use only the approved forms of verbs and adjectives from the STE dictionary is something that I appreciate very much. Applying the rules faithfully was a challenging albeit enjoyable process. There is a lot of good writing rules to learn here. I’ve found the exercises to be very useful for learning reinforcement, and they have helped me to apply STE rules in a more efficient manner and I’ve gained a much better understanding of STE as a result. Shumin’s training methodology is easy to follow, and she offers us great technical writing advice and has simplified the process for us. Every aspect of this training is a 10/10 for me.”

Abdel Alazeem Arafah, Service Coordinator, NIMR Automotive “This was a great course with very useful and practical knowledge for my work. Simplified Technical English (STE) encourages users to always refer to the approved list of verbs and nouns in the STE dictionary before writing their technical documentation. The active voice is also a very useful and powerful tool in sending loud and clear instructions to our users. Starting a warning or caution with a simple and clear command is also very crucial in my line of work. Shumin’s delivery of the training is highly organised, and she has been most patient with our comments, questions, and feedback the whole time.”

An innovative approach to consider for your global documentation landscape

Over the last three decades, STE has emerged as a rather important and universal standard for technical English. Predictably, as a result of language standardisation, STE helps us to achieve a number of benefits. Technical writers become more consistent on a word level. This starts with the simple fact that we are going to use the same word whenever we refer to the same thing, so that means an improved level of consistency and consequently quality improvements.

Where can I learn more about STE?

Shufrans TechDocs regularly hosts online training workshops for technical writers, SMEs, and engineers at different time zones for your convenience. To learn more about our diverse course offerings and workshop customisations that we can do for you and your global technical documentation team, speak to us today!

 

 

Content Connections 2015 by Acrolinx

Content Connections 2015 by Acrolinx

Content Connections - The virtual conference for content professionals 2015

Date: 5 November 2015

Location: Online Conference

Time: 10:00 AM to 05:00 PM CET

Register

Achieving Compliance and much more with Simplified Technical English (STE), by Shumin Chen at 01:50 PM CET

Safety starts with quality. The best product is only as good as its documentation and technical data allow the customer to make optimum use of it. Documentation is a vital and integral part of your product. Most crucially, the documentation needs to do its part to ensure the safe and correct use of the product by providing complete, accurate and effective information.

In this session, Shumin will highlight some of the key benefits and identify rules of STE that can help to address 99% of the main challenges behind documentation processes, such as high cost, ease of translation, damage to product, delayed time-to-market and inadequate customer support.

The advantages of STE are most evident when creating documentation that will be translated into a number of languages. Text in STE is easier to understand and may not even require translation. Where translation is needed, STE helps to drastically reduce translation cost and time-to-market, as it effectively eliminates redundant words and improves consistency. As the text volume is reduced by at least 20% and the remaining text becomes more repetitive, the use of STE typically results in 30 to 40% less translation cost.

With the ever increasing number of languages that companies need to deal with, the savings add up quickly. In other words, Simplified English pays for itself. Moreover, the time-to-market is reduced by a similar percentage. As content in STE is easier to validate, technical writers will be more productive and fewer iterations and less rework will be required.

 

Who should attend?

  • Compliance managers
  • CIO, COO, CTO
  • Customer support managers
  • Documentation managers
  • Editors
  • Engineering managers
  • Engineers and SMEs who create documentation
  • ILS managers
  • Maintenance managers
  • Operation managers
  • Product managers
  • Project managers
  • Quality managers
  • Technical writers
  • Translation managers
  • Translators.

About the speaker

Ms. Shumin Chen has a background in life sciences with a specialisation in biomedical sciences. She has worked as a consultant with customers in various industries worldwide, and is widely regarded as a leading expert in ASD-STE100 Simplified Technical English training, aviation documentation and multilingual documentation. In her current role with Shufrans TechDocs in Singapore, Shumin continues to focus on the practical implementation of international standards to facilitate the efficient creation and management of multilingual documentation.

Shumin now leads the ASD-STE100 training arm of Shufrans TechDocs. She received her professional on-the-job training in the field of STE under the tutelage of Dr Frans Wijma, a linguist, ILS consultant, documentation expert and private pilot who has been in the field of controlled language, multilingual documentation and aerospace & defence standards for 15 years.

Together as an experienced global team, they provided their combined knowledge and dedication to benefit customers worldwide. To date, they have provided training and consultancy services to over 170 companies.

 

ASD-STE100

 

 

Missed this session? The on-demand presentation is now available below.

 

 

Addressing human errors in the healthcare industry

Addressing human errors in the healthcare industry

It is important that operation and management information be understandable to the target audience. Sometimes, operation information is conveyed through a less-than-optimum selection of words. The manufacturer’s technical language can result in incomprehensible operation documentation.

Governance of Picture Archiving and Communications Systems: Data Security and Quality Management of Filmless Radiology, Carrison K.S. Tong, Eric T.T. Wong, Human Factors & Culture, 2009

English is the de facto language for almost all industries, including healthcare where communication is crucial to ensure operational efficiency and accuracy. Without good communication among healthcare professionals such as referring medical doctors, technologists, radiologists, clinicians, nurses, suppliers, maintenance and service engineers would imply that high quality standards become impossible to maintain.

 

Human errors can be expensive, lead to accidents, and risk product quality

More often than not, operation information is conveyed through a less-than-optimum selection of words. To cite a real-life example of a maintenance procedure where a certain step was ‘proscribed’ meaning prohibited, the technical personnel who read this instruction decided that the procedural step was ‘prescribed’ and hence recommended. Regrettably, he proceeded to carry out the prohibited action with dire consequences.

New manuals, job cards, operations and maintenance service bulletins are prime examples of documentation that must be proofread and beta-tested before being widely circulated. Proportionately, the labour costs involved in such documentation management processes can be immensely high.

 

Document complexity & volume

With the latest medical products and technology made available on the market, the increasing complexity and volume of medical data and healthcare information that must be created, recorded, integrated and managed cannot be avoided. Indeed, voluminous and complex writing that read very differently since they must have been supplied by various product manufacturers can negatively impact hospital’s operations when misread or misinterpreted. Volumes of user manuals from various sources with at times overlapping information also seem impossible to store and manage usefully.

A popular example in the aerospace industry is the well-known paper stack from aircraft manufacturers that supposedly exceeds the height of Mount Everest. Paper documentation support the work of aircraft operators. Airlines used to afford warehouses full of such paper stacks that document historical records of their aircraft maintenance. All of which proved too expensive to maintain later on.

Consequently, unmanageable volumes of text, document complexities, time-critical operations, as well as the growing proportion of healthcare workers whose first language is not English, all point to the need for a unifying English language standard that would allow the community to speak with one voice and convey critical information using fewer words.

Create manuals that speak with one voice

Safety begins with quality. Even the best product is only as good as its documentation and technical data, which allow the customer to use it safely and effectively.

Many incidents identified in the healthcare industry revealed poor technical understanding and communication due to missing user manuals, inadequately described operating instructions, and badly maintained  equipment that add to the series of errors and accident occurrences.

Let’s take a close look at the following case study excerpt. Our customer is a manufacturer of mobile X-ray based imaging solutions. They created an operator manual and a service manual in Standard English that was subsequently edited in a controlled language known as Simplified Technical English (STE).

Standard English: inconsistent tone and excessive use of words

Control Panel Both the C-arm stand and the monitor cart have a control panel. The two control panels always show the same screen, enabling you to use them for system operation.Depending on the selected function, other controls (buttons, input boxes, displays, etc.) will appear on the control panel screen.The Vision Center control panel is designed as a touch screen. For system operation, just press the desired button or option directly on the touch screen.

STE: uniform tone of voice and standardised sentence structure

Control Panel The C-arm stand and the monitor cart each have a control panel screen. These screens show the same control panel. Each panel lets you operate the system. The panels have different controls for different functions.The control panel is a touch screen. To operate the system, touch the correct button or option.

At the time our customer was writing a range of user and maintenance manuals  for their X-ray imaging equipment. Although the manuals were created and edited by more than 10 technical writers in a team, our customer wanted all manuals to read like they came from one single source. STE provided a cost-saving and easily implemented solution as evidenced by the rewritten STE sample text highlighted above.

ste_casestudy_chart.001

Say it better with fewer words

The implementation of STE in the healthcare sector proved to be a great success. Using a smaller number of words with defined meanings and parts of speech, while adopting a simplified English language structure meant that user manuals now provide a highly consistent and unambiguous tone of voice with a 20% reduction in text volume. Above all, healthcare professionals depend on reliable documentation to operate medical devices and equipment safely and efficiently. STE therefore helps medical equipment manufacturers meet documentation compliance requirements, and can also increase the efficiency and productivity of their employees.

To summarise, an instruction found in a technical procedure must never become a case of interpretation. Work instructions communicated in technical manuals must be concise and let the user or maintenance personnel do their jobs properly, putting patient safety first and foremost.

Copyright © 2015 Shufrans TechDocs. All rights reserved. No part of this article may be reproduced or transmitted in any form or by any means whatsoever without express written permission from the author, except in the case of brief quotations embodied in critical articles and reviews.

Are you ready to make STE your strategic partner?

Explore our FAQ section below.
Simplified Technical English at the core of your documentation strategy

Simplified Technical English at the core of your documentation strategy

Why Simplified Technical English (STE)?

Whether you are looking to implement working standards such as DITA, S1000D, ATA iSpec 2200, RailDex, or ShipDex to standardise your information structure and facilitate content re-use, it is important to give due consideration to the quality of your source text when creating your technical content. Ambiguous or inconsistently worded documentation can result in non-compliant data deliveries, poor customer support, potential legal liabilities, equipment damage, as well as safety risks.

A well-written source text ensures the ease of downstream content management processes such as translations

Improved readability for your technical content

STE prescribes the use of grammar rules that are relatively more restrictive than the standard rules of the English language.

The general vocabulary has only 900 approved words while explicitly listing 1500 other non-approved words with alternative suggestions.

By introducing these grammar and vocabulary restrictions, technical authors can avoid writing overly long sentences and leave out unnecessary technical details where applicable, all of which are obstacles to the ease of readability and sound understanding.

Recommended by global documentation standards

Military defence standards (MIL-SPEC / MIL-STD) such as MIL-STD-3048, as well as technical documentation standards like S1000D and ATA iSpec 2200 recommend the use of ASD-STE100.

Although the S1000D standard was originally intended for the aerospace and defence industry, this widely successful specification has been customised for the shipping and train manufacturing and operations communities giving rise to both ShipDex and RailDex. Likewise, sound and consistent STE writing rules are highly applicable and practical for use across industries.

Simplifying or eliminating the need for translations?

STE is an international aerospace standard that helps to make technical documentation easy to understand. However, the benefits of STE have proven very highly applicable to all industries. That is why 60% of STE users today come from industries outside of aerospace & defence.

Understandably, STE was designed with non-native speakers of the English language in mind. By providing technical writers with a common set of standardised writing rules and general vocabulary, STE enables teams of writers to write technical manuals that are consistently accurate and require less proofreading and editing effort. Consequently, this does away with the need for translations altogether.

Besides the aerospace maintenance industry however, product exports are still subjected to much scrutiny in terms of their paperwork, documentation and associated product translations. Therefore, the use of STE to create technical content can support downstream translation processes in several ways:

  • A 900-word general vocabulary dictionary eliminates the need for other non-approved, and possibly uncommon synonyms. This reduces the likelihood of term-related clarifications and queries from translators, resulting in faster translation processes.
  • Enforcing STE rules strictly guarantees a high level of consistency at word-, phrase-, and sentence-levels.  This allows project managers to leverage on existing translation memories to substantially reduce translation costs.
  • With fewer technical terms to translate and a more uniform translation memory, translators can provide cheaper, faster and better translations thanks to STE.
  • Having STE content in place will result in exceptional translation quality with machine translations as well.

 

In a nutshell

For many years now, the use of STE as a controlled language authoring strategy has successfully taken off not just at large organisations, but also in small and medium enterprises.

With professional Simplified Technical English training that costs only a fraction of supposed “full implementation”, and yet achieves 75% – 85% of the benefits and results of an approach that includes checker software, getting started with STE is no longer the major and expensive investment it used to be.

Training technical writers and engineers to write in STE within two to three days may sound like a simple and straightforward undertaking. However, to change the way your technical authoring team works does require some managerial direction while the team transits to STE. Trained technical writers will experience on a more regular basis, the many benefits that STE as a controlled language writing strategy offers.


Shumin Chen

About the author

Since 2006, Ms Shumin Chen has been working as a consultant with customers in various industries worldwide: aerospace and defence, banking, consumer products, healthcare, IT, medical and fitness equipment. She has helped many companies with their documentation needs, based on standards where possible, and is widely regarded as a leading expert in ASD-STE100 Simplified Technical English training, aviation documentation and multilingual documentation.

Ms Chen now heads the ASD-STE100 training arm of Shufrans TechDocs. In her current role, Ms Chen continues to focus on the practical implementation of international standards to facilitate the efficient creation and management of multilingual documentation.

Copyright © 2015 Shufrans TechDocs. All rights reserved. No part of this article may be reproduced or transmitted in any form or by any means whatsoever without express written permission from the author, except in the case of brief quotations embodied in critical articles and reviews. 

Are you ready to make STE your strategic partner?

Attend a 2-day certified ASD-STE100 workshop at any of our worldwide locations
Optimise what is between the tags

Optimise what is between the tags

Depending on your industry and requirements, it normally is a great step forward to implement DITA or S1000D to standardise on your information structure and facilitate re-use from a technical point of view. Now, learn how ASD-STE100 Simplified Technical English can help you take things to the next level, thus preparing your content for optimum re-use, readability and translatability.

Data Protection Solutions STE

Simplified Technical English (STE) deconstructed – a textual analysis

In the textual analysis that follows, we will underline unapproved words (according to the ASD-STE100 specification) in the Standard English text and then provide the corresponding approved words in STE underlined where possible.

A general misconception might be that STE rewriting is mostly a word for word replacement. However, this is clearly not the case as illustrated in the examples here:

1a) Standard English: The main idea of Exchange clusters is to provide high database availability with fast failover and no data loss.

1b) STE: Exchange clusters have high database availability with fast failover and no data loss.

Analysis: In this above sentence pair, we removed redundant words that do not add meaning to the sentence. The result is a concise, more direct sentence.

2a) Standard English: Usually, it is achieved by having one or more copies of databases or storage groups on the members of the cluster (cluster nodes).

2b) STE: There normally are one or more copies of databases or storage groups on the cluster nodes.

Analysis: ‘Achieved by’ is a passive verb form that is not approved in STE since it hides the doer of the action. By simply stating that ‘there are one or more copies of databases or storage groups ..’ already supports the first sentence.

In the ASD-STE100 specification, Issue 6, January 2013, rule 1.12, writers are advised not to use different technical names for the same thing. In Standard English, ‘members of the cluster’ was presented synonymously alongside ‘cluster nodes’. This is a clear violation of the rule 1.12 that can cause potential readability issues.

In this case, a good technical writing professional must already decide at the outset which technical term to use and then consistently apply the same term when describing the same thing.

3a) Standard English: If the cluster node hosting the active database copy or the active database copy itself fails, the other node hosting the passive copy automatically takes over the operations of the failed node and provides access to Exchange services with minimal downtime.

3b) STE: If there is a problem with the active database copy or its cluster node, a different node with a passive copy automatically replaces the unavailable node and gives access to Exchange services after a short time.

Analysis: ‘Host’ qualifies as an approved technical verb based on the nature of this text. However, in STE, only a limited group of verb tenses is allowed. The –ing form or present participle verb form is not used in STE unless it is part of a technical name. For instance: lighting, missing, servicing. From the STE example, notice that the verb ‘hosting’ is not necessary since we used the possessive determiner ‘its’ to indicate the association between the active database and the cluster node.

It is also not common to use phrasal verbs in STE as each individual verb could hold a different meaning from the phrasal verb itself. We substituted ‘takes over’ with ‘replaces’ and that adds to one less word count – a win-win. ‘Provides’ as an unapproved STE verb is replaced with ‘gives’, a verb with a more direct and clear definition.

4a) Standard English: Thus, the clusters are already serving as a disaster recovery solution themselves.

4b) STE:

Analysis: The last sentence is a summary of all that has been described and is considered repetitive in STE.

 

The case for STE – concluding points

From the brief analysis provided, it is clear by now that STE when implemented properly lets you have:

  • Higher documentation quality due to increased comprehensibility and readability
  • Standardised, concise and meaningful content
  • Reduced translation costs thanks to better source texts.

STE allows technical writers to achieve their professional goals in a timely manner with mastery of this specification in less than three training days. When correctly applied, STE writing rules help the technical author present complex information in a well-thought-out and developed style.

 

Copyright © 2015 Shufrans TechDocs. All rights reserved. No part of this article may be reproduced or transmitted in any form or by any means whatsoever without express written permission from the author, except in the case of brief quotations embodied in critical articles and reviews.

Using ASD-STE100 to apply Lean Six Sigma concepts to your documentation processes

Using ASD-STE100 to apply Lean Six Sigma concepts to your documentation processes

By Ms. Shumin Chen and Dr. Frans Wijma

ASD-STE100 Simplified Technical English and Six Sigma

Below, we will outline the basic synergy between Six Sigma and Simplified Technical English.

An important Six Sigma method is known as DMAIC:

  • Define the project goals
  • Measure key aspects of the current process and collect relevant data
  • Analyse the data to identify root defects
  • Improve or optimise the current process based on the data collected
  • Control the new process to ensure that any deviations from target are corrected before they result in defects

In the domain of ASD-STE100 Simplified Technical English in relation to content creation and content management (authoring, editing, change management, version management), the basic parallel is:

  • Define the writing rules
  • Mine legacy data
  • Analyse the data to identify the common violations
  • Improve the documentation by applying the relevant rules
  • Check the documentation to ensure correct and consistent use of the rules, thus reducing the number of violations and improving output quality

 

Our ASD-STE100 working model

Shufrans-six-sigma-ste-small

ASD-STE100 Simplified Technical English provides the baseline set of writing rules that can be used as objective parameters to measure content quality. Shufrans TechDocs can extract relevant error information from your legacy publications, helping to identify the main problem areas. We then train your staff in effectively applying the rules that remedy these problems.The delivered content aims to provide key decision support for further STE implementation across departments and future technical writing projects.

Finally, we help you to implement and form of Simplified Technical English checker software to monitor and control the content creation and output. The exact implementation will be based on your existing or planned documentation process and entails many variables.

 

Your bottom line impact

ASD-STE100 Simplified Technical English involves all aspects of the documentation life cycle. It looks to make significant improvements in your content creation and content management workflow. Typically, text written in Simplified Technical English will show a 20 to 30% reduction in text volume without any information loss and at least a 60% increase in readability and user-friendliness. As the text volume is reduced by at least 20% and the remaining text becomes more repetitive, the use of Simplified Technical English typically results in 30 to 40% less translation cost.

After all, the best product is only as good as its documentation and technical data allow the customer to make optimum use of it without stretching the budget too far.

Copyright © 2015 Shufrans TechDocs. All rights reserved. No part of this article may be reproduced or transmitted in any form or by any means whatsoever without express written permission from the author, except in the case of brief quotations embodied in critical articles and reviews.