Speak to a rep about your business needs
See our product support options
General inquiries and locations
Contact usBMC Helix Voice, Tone, and Style Guide
By following these guidelines, we can all effectively communicate the brand’s message and values while fostering a cohesive and unified brand experience across different channels and content creators. It’s divided into sections to help you:
If you’re looking for design guidance on the BMC Helix look and feel, check out the BMC Helix Brand Guide here.
When we create BMC Helix content, our audience includes everyone, from customers and partners at our respective peer levels up through the C-suite, and each has their own preferred method of contact and communication. The most important thing to remember is that you are a human being speaking to other human beings. You’re not a machine speaking to a machine.
Regardless of the audience, your goal should always be to make technical language accessible and understandable to general audiences, not just IT pros. Non-technical users should be interested in and understand our products, services, and thought leadership ideas because we describe them in clear, conversational, decipherable terms. Technical users should be intrigued by the content, which is of value to them and their business.
BMC Helix exists to serve our customers, and our voice and tone are the basis for everything we say, write, and do as a company, and individually as its representatives.
In this section, we’ll talk about how you should and shouldn’t use language. IT has evolved, and with that evolution, a lot more people understand the basic ins and outs of technology. Our language should level set with that basic knowledge, and as we move toward more specific, niche, or, frankly, weedy language, it’s important to not lose the thread—or your audience.
| Our voice is: | Our voice is not:
|
|
|
Here are a few pointers on setting the right tone.
The BMC Helix voice is aligned to our vision to become the key strategic partner for our customers and empower them to achieve successful outcomes. It emphasizes opportunity with realistic optimism and a focus on the future.
For example, we do not use geopolitical events as an opportunity to communicate or market, but we acknowledge their impact to set the context for the future and opportunity.
Copy example: Organizations around the world are facing challenges to evolve their business faster than humanly possible—adopting new operating models and realizing the value of existing investments to position themselves to be more agile, increase customer centricity, and act quickly on insights. BMC Helix offers the software, solutions and expertise to stay competitive and realize opportunities that emerge amidst times of rapid change.
Here are a few pointers on setting the right tone.
The BMC Helix voice is aligned to our vision to become the key strategic partner for our customers and empower them to achieve successful outcomes. It emphasizes opportunity with realistic optimism and a focus on the future.
For example, we do not use geopolitical events as an opportunity to communicate or market, but we acknowledge their impact to set the context for the future and opportunity.
Copy example: Organizations around the world are facing challenges to evolve their business faster than humanly possible—adopting new operating models and realizing the value of existing investments to position themselves to be more agile, increase customer centricity, and act quickly on insights. BMC Helix offers the software, solutions and expertise to stay competitive and realize opportunities that emerge amidst times of rapid change.
BMC Helix communication do’s and dont's
Do | Don't | |
Relevant |
|
|
Confident/Knowledgeable |
|
|
Relatable |
|
|
Empowering |
|
|
Visual |
|
|
Tense |
|
|
Lead with the get |
|
|
Be mindful of diversity and inclusiveness when you speak to your audience.
BMC Helix has joined the Inclusive Naming Initiative, a cohort of industry leaders dedicated to promoting and facilitating the replacement of harmful and exclusionary language in information technology.
Our current public-facing statement on inclusive language, which can be used in customer deliverables, is:
“BMC Helix is committed to delivering products, services, and insights that can serve everyone. The BMC Helix Product Experience team is applying inclusive and gender-neutral principles throughout all three areas of UX design: content, interaction, and visual design, including adopting neutral pronouns and inclusive phrases that avoid assumptions and stereotypes and creating illustrations and graphics that are age, gender, orientation, cultural, racial, body type, and ability inclusive, and equitably accessible with a focus on usability and reduced cognitive load.
We internally develop solutions with the assistance of accessibility expert resources and in compliance with the latest Web Content Accessibility Guidelines (WCAG), Revised Section 508 standards, and EN 301 549 requirements to ensure that our products, content materials, services, and websites are equitably accessible.”
We also invite you to check out our annual Corporate Citizenship and ESG Impact Report to stay up to date on current BMC Helix activities in this area.
Here, we’ve compiled specific examples of representation to keep in mind as you create content—words and visuals. This is by no means exhaustive, but it addresses some of the easiest, often unconscious, mistakes and biases.
Avoid terms that connote racial bias or have negative historical overtones. If you are referring to a specific race or ethnicity in your content, it should be capitalized: “Black, Asian, Indigenous, Latino/Latina/Latinx” etc.
Speech and colloquialisms that refer to some sort of physical or emotional disability should not be used. Avoid terms such as crazy (“This may sound crazy”), insane (“insane profit margin” or “sanity check”), etc. If you are discussing people with different abilities, don’t describe people without disabilities as “normal” or “healthy.” Use “nondisabled” person, sighted person, hearing person, etc., instead. Do not quantify a disability with, “victim of, suffering from, wheelchair-bound,” etc. Use “experiencing, living with, uses a wheelchair,” etc., instead.
Unless it’s relevant to your content, do not write about age. If it is relevant to the context of your content, avoid terms such as “elderly, aged, seniors, senior citizens, and X years young” and use “older adults or aging population,” common generational terms (“Millennials” or “Baby Boomers”), or the relativity to another person discussed (parent, sibling, etc.).
When possible and appropriate, avoid using “he” and “she” and instead change to “you,” pluralize the actor (“they”) and the verb (“are, were,” etc.), or reword the sentence to remove the actor altogether. Avoid terms that assign the male gender such as “salesman, manpower, mankind, or man-hours” and instead use “salesperson, workforce, humankind, and person-hours.” The Chicago Manual of Style has nine techniques for avoiding gendered use. If you are interviewing someone to be quoted, or introducing someone at an event, ask what their preferred pronouns are so you can attribute quotes and introduce them correctly.
BMC Helix is a global company, so don’t assume that your audience is US-based. Avoid region-specific holidays, sports, cultural practices, and colloquialisms that may alienate some of your audience. Remember that global audience, too, when you select images and video. Note, however, that our primary language in global deliverables is US English.
Avoid terms that connote racial bias or have negative historical overtones. If you are referring to a specific race or ethnicity in your content, it should be capitalized: “Black, Asian, Indigenous, Latino/Latina/Latinx” etc.
Speech and colloquialisms that refer to some sort of physical or emotional disability should not be used. Avoid terms such as crazy (“This may sound crazy”), insane (“insane profit margin” or “sanity check”), etc. If you are discussing people with different abilities, don’t describe people without disabilities as “normal” or “healthy.” Use “nondisabled” person, sighted person, hearing person, etc., instead. Do not quantify a disability with, “victim of, suffering from, wheelchair-bound,” etc. Use “experiencing, living with, uses a wheelchair,” etc., instead.
Unless it’s relevant to your content, do not write about age. If it is relevant to the context of your content, avoid terms such as “elderly, aged, seniors, senior citizens, and X years young” and use “older adults or aging population,” common generational terms (“Millennials” or “Baby Boomers”), or the relativity to another person discussed (parent, sibling, etc.).
When possible and appropriate, avoid using “he” and “she” and instead change to “you,” pluralize the actor (“they”) and the verb (“are, were,” etc.), or reword the sentence to remove the actor altogether. Avoid terms that assign the male gender such as “salesman, manpower, mankind, or man-hours” and instead use “salesperson, workforce, humankind, and person-hours.” The Chicago Manual of Style has nine techniques for avoiding gendered use. If you are interviewing someone to be quoted, or introducing someone at an event, ask what their preferred pronouns are so you can attribute quotes and introduce them correctly.
BMC Helix is a global company, so don’t assume that your audience is US-based. Avoid region-specific holidays, sports, cultural practices, and colloquialisms that may alienate some of your audience. Remember that global audience, too, when you select images and video. Note, however, that our primary language in global deliverables is US English.
Avoid abbreviations and acronyms whenever possible and practical. We can’t assume that our users will understand the same shortened terminology that we use internally or as industry jargon. When making an acronym (or any word) plural, do not use an apostrophe. Example: VPNs, not VPN’s.
See the Glossary: A to Z index for specific guidance on acronyms that are exceptions to the rule. If used, always spell the full term out on first use unless it is widely known. When spelling out the words in an acronym, where the letters are pronounced as a word (SaaS), or with initials, where each letter is pronounced separately (API), on first mention, do not capitalize them unless they are proper nouns.
Do not capitalize functions such as IT operations, sales and marketing, etc., unless you are referring to a specific group in a named organization.
Correct: Previously part of IBM’s IT Operations group, she now works for AMD Sales Engineering.
Incorrect: Security and Operations teams often experience miscommunication.
Do not capitalize unless they are BMC Helix brand names.
| Correct: | Incorrect:
|
|
|
Do not capitalize big data, cloud, customer, mainframe, multicloud, incident, internet, intranet, service desk, service management, web, website, web page, webinar, workload automation, etc., unless they are used in a title.
Current brand guidance is to use sentence case headers and headlines in formatted/designed documents and on web pages. Blogs currently use title case for the title and sentence case for the subheads.
Examples: This Is Title Case | This is sentence case
Punctuation is allowed in headlines, but is not required, and the recommendation is to use a headline that can convey intent succinctly enough so as not to require punctuation.
Capitalize a job title and the department, regardless of whether it appears in front of or immediately following a person’s name. Do not capitalize generic job roles by themselves.
Examples:
Do not capitalize functions such as IT operations, sales and marketing, etc., unless you are referring to a specific group in a named organization.
Correct: Previously part of IBM’s IT Operations group, she now works for AMD Sales Engineering.
Incorrect: Security and Operations teams often experience miscommunication.
Do not capitalize unless they are BMC Helix brand names.
| Correct: | Incorrect:
|
|
|
Do not capitalize big data, cloud, customer, mainframe, multicloud, incident, internet, intranet, service desk, service management, web, website, web page, webinar, workload automation, etc., unless they are used in a title.
Current brand guidance is to use sentence case headers and headlines in formatted/designed documents and on web pages. Blogs currently use title case for the title and sentence case for the subheads.
Examples: This Is Title Case | This is sentence case
Punctuation is allowed in headlines, but is not required, and the recommendation is to use a headline that can convey intent succinctly enough so as not to require punctuation.
Capitalize a job title and the department, regardless of whether it appears in front of or immediately following a person’s name. Do not capitalize generic job roles by themselves.
Examples:
When adding a footnote in copy passages that are punctuated, the footnote number should follow the comma, semicolon, or period, with no space between them but a normal space afterward. If you're footnoting something before an em dash, place the footnote between the word and the em dash with no spaces. General rule of thumb is to only cite sources published within two years of your document. If you are refreshing an older document that pushes your citations outside that two-year window, then update them.
If referencing Gartner or Forrester research, your asset must be approved by them, at which time, they may request wording changes on both the quote and the citation. Refer to that guidance. Please work with your BMC Helix content partner to get those approvals.
The general citation style (note the punctuation) for a standard book or periodical is:
Author Last Name, Author First Name. Publication Name. Publisher, City, Month Year.
Example: Jones, Paulette. Winning at Life: A Memoir. Incredible Books, New York City, April 2016.
The general citation style (note the punctuation) for an analyst publication or online article is:
Analyst group, Title of study/survey/article, Month Year.
Example: IDG, A Consumer Guide to Service Desk Solutions, April 2016.
Example with website: B2B Advocate, Why Customers Don’t Come Back, http://www.wesbitewitharticle, Accessed April 2017.
For an easy hack, you can also plug your details into the Citation Machine and get an auto-generated citation.
Dates and times should be written out to avoid confusion. Time of day can be indicated as lowercase with periods or uppercase without periods. Do not use :00 to indicate the top of the hour. Be consistent within your document on whichever format you use, i.e., a.m. and p.m. or AM and PM.
When listing an event, use this order: time, day of the week, month, numbered date, year. Example: “9 a.m., Tuesday, May 7, 2024.” Note the placement of commas. Outside North America (such as in the UK), list the numbered day prior to the month, without commas, on the date, as in “9 a.m., Tuesday, 7 May 2024.” Check with in-country personnel if you are unsure of usage.
Since BMC Helix is a global company, use Greenwich Mean Time (GMT) for general time references, online events, or other global references.
Example: “The webinar will be held at 1 p.m. (GMT).” For reference, here is a time zone converter. For local events, use local time and reference the time zone. Example: “The seminar in Houston will be held at 1 p.m. (CDT).” Note the parentheses.
Use en dashes with no spaces between numbers/words (not hyphens) to indicate time spans or ranges. See the Dashes section for more information about how to properly use the en dash. Here are some usage examples.
Correct | Incorrect |
February 10, 2024 | 2/10/24 (could be February 10 or October 2) |
9 am 9 AM | 9 A.M. 9 a.m. 9:00 AM |
May 22–24, 2025 | May 22-24, 2025 |
Q4 in FY2026 | 4th quarter in Fiscal 26 |
24x7 24 hours a day, 7 days a week | 24/7
|
Use bullets instead of numbers, unless you’re describing an ordered sequence. Use parallel construction for all items in a list; if you begin one list item with a verb, begin all of them with a verb. Capitalize the first word in each list item and do not use periods unless the item constitutes a complete sentence—be consistent so that all bullets either have punctuation or don’t.
Spell out numbers one through nine and use numerals to indicate the numbers 10 and up. An exception may be made when citing a number in a heading, such as “3 paths to service management excellence.” Exceptions may also be made for graphics and for SEO performance—contact the BMC Helix Brand and SEO teams for asset-specific guidance. Here is some general guidance:
Capitalize the word after a colon only if it is a proper noun or the start of a complete sentence. Example: His point was this: We will achieve our goals.
Use a colon to introduce a list. Example: There are three concerns: time, money, and resources.
Use the Oxford (or serial) comma, e.g., include the last comma in a list.
Correct: I like green, blue, and purple.
Incorrect: I like green, blue and purple.
Use em dashes with no spaces to indicate a pause or relate one part of a sentence to another. Use en dashes with no spaces between numbers/words to indicate time spans, ranges, or definitions. Do not use hyphens in place of proper dashes. Hyphens should only be used as connectors in words or to create compound terms (see Hyphens below). Word will autocorrect double dashes to em dashes, or you can insert manually as a symbol.
| Em dash | En dash
|
|
|
In general, use exclamation points very sparingly. To be more colloquial and human in our style, we can use exclamation marks for less-formal executions like blogs or promotional emails for events. Do not use in headers/sub-headers or in email subject lines, as they will often trigger spam filters.
Keep headers as brief as possible: seven words or fewer. Use active verbs for subheads and avoid gerunds (“ing” words). Don’t punctuate a header or subhead unless it includes a question or is longer than seven words, and then be consistent with any other sentences in the header. Don’t use exclamation points.
Hyphenate temporary compounds (two adjectives or an adjective and an adverb) in front of the noun, but not after, as a rule. Some words always take a hyphen. Examples: the prefixes all (e.g., all-encompassing), self (e.g., self-healing), and ex (e.g., ex-partner). State-of-the-art, up-to-date, long-term, cost-effective, data-driven, and out-of-the-box are hyphenated when used as an adjective. If they follow the verb, they are not hyphenated. Capitalize the second word in a capitalized, hyphenated compound, such as Third-Party or Self-Service. Do not hyphenate an adverb compound when the adverb ends in “ly,” e.g., “The finally completed report was ready to publish.” Here are some additional examples.
| Correct | Incorrect
|
|
|
Avoid the use of italics for emphasizing text unless referencing the actual title of a book or name of a publication. Example: Continuous Compliance in Identity Management: An Online Discussion; The Boston Globe. Consider boldface for emphasis. Do not use ALL CAPS for emphasis.
Use double quotation marks (“” and not single ‘’) when:
Do use single quotes if there is a secondary quote referenced.
Closing punctuation marks (periods and commas) always go inside quotation marks unless their inclusion will cause confusion about the term quoted. Use a lead-in comma before the first quotation mark in a quoted passage, but not before quoting individual words.
Examples:
Use when separating two independent but related ideas, or a list of long or complex items.
Examples:
Use the forward slash “/” without spaces, e.g., AI/ML.
Use one space between sentences. Always.
Capitalize the word after a colon only if it is a proper noun or the start of a complete sentence. Example: His point was this: We will achieve our goals.
Use a colon to introduce a list. Example: There are three concerns: time, money, and resources.
Use the Oxford (or serial) comma, e.g., include the last comma in a list.
Correct: I like green, blue, and purple.
Incorrect: I like green, blue and purple.
Use em dashes with no spaces to indicate a pause or relate one part of a sentence to another. Use en dashes with no spaces between numbers/words to indicate time spans, ranges, or definitions. Do not use hyphens in place of proper dashes. Hyphens should only be used as connectors in words or to create compound terms (see Hyphens below). Word will autocorrect double dashes to em dashes, or you can insert manually as a symbol.
| Em dash | En dash
|
|
|
In general, use exclamation points very sparingly. To be more colloquial and human in our style, we can use exclamation marks for less-formal executions like blogs or promotional emails for events. Do not use in headers/sub-headers or in email subject lines, as they will often trigger spam filters.
Keep headers as brief as possible: seven words or fewer. Use active verbs for subheads and avoid gerunds (“ing” words). Don’t punctuate a header or subhead unless it includes a question or is longer than seven words, and then be consistent with any other sentences in the header. Don’t use exclamation points.
Hyphenate temporary compounds (two adjectives or an adjective and an adverb) in front of the noun, but not after, as a rule. Some words always take a hyphen. Examples: the prefixes all (e.g., all-encompassing), self (e.g., self-healing), and ex (e.g., ex-partner). State-of-the-art, up-to-date, long-term, cost-effective, data-driven, and out-of-the-box are hyphenated when used as an adjective. If they follow the verb, they are not hyphenated. Capitalize the second word in a capitalized, hyphenated compound, such as Third-Party or Self-Service. Do not hyphenate an adverb compound when the adverb ends in “ly,” e.g., “The finally completed report was ready to publish.” Here are some additional examples.
| Correct | Incorrect
|
|
|
Avoid the use of italics for emphasizing text unless referencing the actual title of a book or name of a publication. Example: Continuous Compliance in Identity Management: An Online Discussion; The Boston Globe. Consider boldface for emphasis. Do not use ALL CAPS for emphasis.
Use double quotation marks (“” and not single ‘’) when:
Do use single quotes if there is a secondary quote referenced.
Closing punctuation marks (periods and commas) always go inside quotation marks unless their inclusion will cause confusion about the term quoted. Use a lead-in comma before the first quotation mark in a quoted passage, but not before quoting individual words.
Examples:
Use when separating two independent but related ideas, or a list of long or complex items.
Examples:
Use the forward slash “/” without spaces, e.g., AI/ML.
Use one space between sentences. Always.
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P |Q | R | S | T | U | V |W | X | Y | Z
A
AGI: artificial general intelligence
AI: artificial intelligence; often used in tandem with machine learning; if used together, spell out first use as “artificial intelligence and machine learning (AI/ML)” and reference thereafter as AI/ML
AIOps: artificial intelligence for IT operations
AISM: artificial intelligence service management
ampersand: The ampersand (&) should not be used in place of the word “and.” Exceptions: R&D, Q&A, the ampersand is part of an official trademarked term, or character restrictions require it.
analyst references: Per analyst rules, do not use names (Gartner, Forrester, etc.) in subject lines without express prior permission. Review Citations for analyst references.
and/or: Don’t use this construction
API: application programming interface
APAC/APJ: refers to the regions of Asia Pacific and Japan
APM: application performance management or application performance monitoring; confirm intended usage and spell out first instance followed by (APM)
apostrophe: Don’t use it to form the plural of a word (the Smiths, not “the Smith’s”; three PCs, not “three PC’s”). Apostrophes show possession (Jane’s laptop) and take the place of a letter in a contraction (won’t).
AR: analyst report, analyst relations or augmented reality; confirm intended usage and spell out on first instance
Asia Pacific: Use this to refer to the region. Do not use “Asia Pac” or “Asia-Pacific.
B
backup vs. back up: The first is a noun and adjective; the second is a verb. Example: The backup server was used as a backup to back up the data.
backend vs. back end: The first is an adjective and the second is a noun. Example: The backend server was used on the back end of the system.
BAU: Business as usual
BI: business intelligence
big data: Only capitalize if in a title or part of a product name.
BMC Helix: Always use the prefix BMC before Helix due to trademarks; see BMC Helix Trademark Guidelines.
BOM: bill of materials
BPM: business process management or business performance management; confirm intended usage and spell out first instance followed by (BPM)
brand tagline: Turn AI into action.
bullets: See Lists under Grammar, usage, and style
BYOD: Acronym for “bring your own device” (no hyphens)—spell out on first use, no caps (as shown)
C
CAGR: compound annual growth rate
capitalization: See Capitalization under Grammar, usage, and style.
CASB: cloud access security broker catalog: Use this short spelling instead of catalogue for US audiences
CI/CD: continuous integration and continuous deployment or continuous integration and continuous delivery; confirm intended usage and define on first instance
CISO: chief information security officer. See Job titles under Grammar, usage, and style.
cloud: Only capitalized if in a title or part of a product name
CMDB: configuration management database; the BMC Helix product is BMC Helix CMDB and does not need to be spelled out when referencing the product
CMP: content management platform or cloud management platform; confirm intended usage and spell out on first instance
COBIT: Control Objectives for Information and related Technology; when using COBIT in print, if at all possible, make the “OBI” one size smaller font than the “C” and “T”
CoE: center of excellence
commas: BMC Helix uses the serial comma. See Punctuation in Grammar, usage, and style for more information.
company-wide: use the hyphen
contractions: contractions are acceptable as part of our tone (isn’t, don’t, etc.).
copyrights: See BMC Helix Trademark Guidelines.
COVID-19: The coronavirus pandemic
COTS: commercial off the shelf
CRM: customer relationship management
CSO: chief security officer. See Job titles under Grammar, usage, and style.
CSP: cloud service provider or communication service provider; confirm intended usage and spell out the first time
CSR: corporate social responsibility
D
DA: delivery automation
data: Although technically plural, it is treated as a singular noun. Example: The data was compelling.
database: One word
data center: Two words data-driven: Use the hyphen
DataOps: Shortened version of data operations. It doesn’t need to be spelled out on first instance.
datasheet: One word
dates: See Dates/Times under Grammar, usage, and style.
Davos: A short way to reference the World Economic Forum (WEF), an annual meeting of global, political, and corporate leaders that often strongly influences corporate IT decision-making.
DEI: diversity, equity, and inclusion
DevOps: Should be capitalized as shown
DIY: do it yourself
dollar vs. $: Spell out dollar in this context: “Give me a dollar.” or “The project cost millions of dollars.” Use the dollar symbol ($) when referencing a specific amount of money (e.g., “I spent $35 at the store.”). See Currency.
DORA: DevOps Research and Assessment LLC (often followed by “metrics”) or Digital Operational Resilience Act; confirm intended usage when spelling out first instance.
double-click vs. double click: Use the hyphenated form as a verb, but no hyphen as a noun. Example: Double-click the icon to open the document. A double click will open the file.
downtime: One word, not down time
DSM: digital service management
DX: digital experience
E
e-: When using the prefix “e” to mean “electronic,” use a hyphen, as in “e-commerce” and “e-business.” Exception: email is used without the hyphen. For headlines and other uses requiring capitals, capitalize the “e.”
e-book: Include the hyphen (if capitalized for category listings, use E-book)
e.g.: Abbreviation for “for example”; always followed by a comma, and can include one or more examples (in contrast with i.e., which typically references a specific item).
ecosystem: One word, not eco system
edge: Do not capitalize unless used in a formal name (BMC Helix Edge), title, or as the first word in a subhead.
email: Email is used without the hyphen. For headlines and other uses requiring capitals, capitalize the “e.”
EMEA: Acceptable on first reference to mean “Europe, Middle East, and Africa.”
end-user or end user: Use the hyphenated form as an adjective, but do not include a hyphen when used as a noun. Example: The end user read the end-user documentation.
enterprise-wide: Use the hyphen.
ESG: environmental, social, and governance
ESM: enterprise service management; do not capitalize unless referring to BMC Helix Enterprise Service Management, which should not be abbreviated
EX: employee experience
exclamation points: See guidance in Punctuation in Grammar, usage, and style.
F
failover vs. fail over: The first is an adjective and the second is a verb. Example: A failover data center for business continuity will fail over to another machine.
FedRAMP: Federal Risk and Authorization Management Program; note capitalization
follow-up vs. follow up: The first is an adjective or noun and the second is a verb. Example: The team conducted a follow-up visit on the issue after promising the customer they would follow up.
FootPrints: Capital F, capital P (FootPrints from BMC Helix) Front-end vs. front end: The first is an adjective and the second is a noun. Example: The front-end interface demonstrated that BMC Helix is on the front end of innovation.
G
GenAI or Gen AI: Generative artificial intelligence; spell out on first instance and lower case all words unless Generative begins a sentence. It's OK to use full term instead of abbreviation, and abbreviate as GenAI or Gen AI as it's a new term, but align on consistent usage in collateral.
gender: See Gender-neutral under Language.
GUI: graphical user interface; no need to spell out on first mention
H
handheld: One word, no hyphen (a handheld device) headings and subheads: Use sentence case. See guidance in Punctuation in Grammar, usage, and style.
healthcare: One word
high-tech: Hyphenate as an adjective only when it precedes the noun. Example: “It’s a high-tech solution.” and “The solution was very high tech.” Do not hyphenate as a noun: “That’s the nature of high tech.”
HIPAA: Health Insurance Portability and Accountability Act; note capitalization
home page: Two words
hyperautomation: One word, no capitalization unless in a title, no hyphen
I
IDaaS: identity as a service
IDE: integrated development environment
IIoT: Industrial Internet of Things. Note the capitalization of Internet in this instance only. Spell out on first use, followed by a parenthetical IIoT.
IL4: Impact Level 4, note capitalization and do not hyphenate
IL5: Impact Level 5, note capitalization and do not hyphenate
ILOB: independent line of business
industry-wide: Use the hyphen internet: Do not capitalize
IoT: Internet of Things. Note the capitalization of Internet in this instance only,
IP: intellectual property
IPA: intelligent process automation
iPaaS: integration platform as a service
ISV: independent software vendor
IT vs I.T.: Abbreviation for information technology. In almost all instances, use IT without periods. If using without periods will create confusion due to typeface or content, add the periods.
intranet: Do not capitalize
italics vs. quotation marks: See Punctuation under Grammar, usage, and style.
ITIL®: IT Infrastructure Library. Should be trademarked ITIL® and does not need to be spelled out on first use.
ITIM: IT infrastructure monitoring
ITOM: IT operations management
ITOps: IT operations
ITPA: IT process automation
ITSM: IT service management; no need to spell out on first use
its vs. their vs. it’s: Use the possessive “its” to refer to a company or other entity. Example: BMC Helix announced its newest solution at the event. Note: Microsoft announced their latest partnership. When referring to a group or team, use “their” or reword to indicate ownership. Example: The team presented their project. It’s is an abbreviation for “it is” and should not be used to indicate a possessive. Example: It’s just one way that BMC Helix is proving its innovation.
J
Java: A high-level, general-purpose programming language
JavaScript: A scripting language
K
K: Used to indicate thousands in graphics and callouts. Capitalize. Example: 500K users.
kilobyte: A unit of storage capacity on a computer. Abbreviate and list with a number and no space: “10KB.”
knowledge base: Two words
L
less vs. fewer: Use less to refer to a quantity and fewer to refer to numbers of things. Example: The snack wasn’t great because there was less milk in the bottle and fewer cookies in the box.
lifecycle: One word, no hyphen
Linux®: Not LINUX, and include the ® per legal agreement
lists: See Lists under Grammar, usage, and style.
LOB: line of business
login vs. log in: The first is a noun and adjective; the second is a verb. Example: She could not log in to the system, although her login credentials were correct.
logon vs. log on: The first is a noun and adjective; the second is a verb. Example: He could not log on to the system, although the logon page was working properly.
LPAR: logical partition
M
M&A: mergers and acquisitions
megabyte: A unit of storage capacity on a computer; abbreviate and list with a number and no space: “250MB”
MFA: multi-factor authentication
midmarket: No hyphen
mid-sized: Hyphenate when used as an adjective.
ML: machine learning
MLC: monthly licensing charges
MLOps: machine learning operations
MM: Abbreviation for “million”
more than vs. over: Use “more than” to refer to numbers and “over” to describe heights. Example: He had more than 20 years of experience, and his webinar about the building he designed, which was over 40-feet tall, attracted more than 300 attendees.
MQ: Gartner® Magic Quadrant; note required usage of Gartner registration symbol. Any usage referencing an evaluation of BMC Helix solutions requires review and approval by Gartner. See Citations section in this guide.
MSU: million service units
MTTR: mean time to repair or mean time to recovery; confirm usage and spell out on first use, no hyphens
multicloud: One word, no hyphen
Mr., Ms., etc.: BMC Helix does not use these courtesy titles with names.
N
NIST: National Institute of Standards and Technology; its Cybersecurity Framework is sometimes referenced as CSF even though cybersecurity is one word; spell out both on first usage and note capitalization.
NLP: natural language processing
non-: Do not use a hyphen in instances of compound words that do not have special meaning and can be understood if not is used instead before the base word (i.e., nonsensical is as equally understood as not sensical). Use a hyphen before proper nouns or in awkward combinations, such as non-nuclear.
noon: Acceptable for 12 p.m. Do not use the redundant, 12 p.m. noon. Do not use all caps.
number (or #): Instead of # as an abbreviation to indicate position or rank, you can also use “No.” (note the period) followed by a number. Be mindful in web design that # as a hashtag is indicative of a link.
numbers: Spell out numbers one through nine and use numerals to indicate the numbers 10 and up. An exception may be made when citing a number in a heading, such as “3 paths to service management excellence.” See Numbers under Grammar, usage, and style.
O
offline: Not off-line nor off line
on demand vs. on-demand: On demand is a prepositional phrase that usually comes after the noun; on-demand is an adjective that precedes the noun and is hyphenated. Example: What is the right on-demand solution for your business? If you need help on demand, join our live webinar.
online: Not on-line nor on line
on-premises: Always plural, is an adjective, and should be hyphenated. Example: The team handled the on-premises installation.
OT: operational technology
OTAC: one-time authentication code
P
PCI-DSS: Payment Card Industry Data Security Standard; note capitalization
PDP: policy decision point
percent vs. %: In longform content like white papers, datasheets, and e-books, always use the word “percent” in copy, e.g., 100 percent. The % symbol is acceptable for web copy for SEO purposes, as well as online banners, documents with limited space, charts, callouts, sidebars, and tabular materials.
pen test or pentest: penetration testing
PII: personally identifiable information
Plug-in vs. plug in: The first is a noun and adjective; the second is a verb. Example: Plug in the adapter in the plug-in slot on the device.
plus sign (+): Use to indicate “more than” in limited character space. Example:+4MM or 4MM+ users. Style considerations may dictate whether plus sign is placed before or after the corresponding number.
podcast: One word
pro bono: Do not hyphenate products: Use the official spelling, letter casing, and character spacing for BMC Helix product names. This includes the “BMC Helix” in front of product names that are not trademarked or those that are trademarked with BMC Helix in the name. See BMC Helix Trademarks.
Q
quarter: Use Q1 or Q4 to indicate the quarter of the year (for business, finance, sales)
R
(R): Stands for “registered” and indicates registered trademark or patent. Format with a superscript ® after the word. No space between the word and the symbol.
RBA: run book automation
re-: A hyphen is used if the prefix ends in a vowel and the word that follows begins with the same vowel. Examples: regain, re-elect.
real time vs. real-time: The first is a noun; the second is an adjective. Example: The real-time data was delivering results in real time.
Remedy: This product is now called BMC Helix ITSM Remedyforce: The F is not capitalized and should contain the prefix of “BMC Helix” to be BMC Helix Remedyforce. See BMC Helix Trademark Guidelines.
ROI: return on investment
ROX: return on experience
RPA: robotic process automation
run time vs. run-time: The first is a noun; the second an adjective. Example:The run-time process reduced the system’s overall run time.
S
salesperson, salesforce: One word; only capitalize Salesforce if referencing the company.
SDI: software-defined infrastructure
SEM: search engine marketing
SEO: search engine optimization
ServiceOps: A paradigm that merges IT service management (ITSM) and IT operations management (ITOM). Note: you may see instances of BMC Helix ServiceOps in BMC Helix collateral—it is a framework and not a formal product.
SI: systems integrator
SLA: service level agreement
shift left vs. shift-left: The first is a verb; the second is an adjective. Example: Shift-left testing allowed the team to review which processes it could shift left.
SIEM: security information and event management
SOAR: security orchestration, automation, and response
SaaS: software as a service; no need to spell out on first usage
standalone: All one word, adjective. Example: It’s a standalone computer terminal.
start-up vs. start up: The first is a noun and adjective; the second is a verb. Example: The business was a start-up and its signature solution promised to reduce start-up costs. The first step is to start up the installation.
states: Spell out state names unless part of an address—Texas, not TX.
T
TCO: total cost of ownership
TEI: Forrester Total Economic Impact Report™ note required usage of Forrester trademark symbol. Any usage referencing an evaluation of BMC Helix solutions requires review and approval by Forrester. See Citations section in the guide.
telephone numbers:
United States:
International (outside US):
TFP: tailored-fit pricing
that and which vs. who and whom: Use that or which as the pronoun for objects and who or whom as the pronoun for people. Example: The staff who arrived early enjoyed the breakfast that was provided for them. Add a comma transition with which and no comma with that. Example: The breakfast, which was served cold, was not the meal that the attendees expected.
third-party, third party: Hyphenate as an adjective; do not hyphenate as a noun. Do not use “3rd” in place of “third” in any instance. Example: A third party owns the third-party software.
time: See Dates/Times under Grammar, usage, and style
time zones: Do not list the time zone in a communication distributed to a local audience, such as a print invitation, because readers will assume the time is local. For online events or other global references, use Greenwich Mean Time (GMT). See Dates/Times under Grammar, usage, and style.
titles: See Job titles under Grammar, usage, and style.
TM: Stands for “trademark” and should be used to designate official trademarks; format with a superscript ™ after the trademarked word, no space between the word and the symbol. Use the TM symbol ™ in Office; do not type out and superscript the letters.
total cost of ownership: Spell out on first use with acronym; “TCO” alone is acceptable thereafter.
Track-It!: Include the hyphen, capital “I,” and exclamation point; CVT product.
trademarks: Use the official spelling, letter casing, and character spacing for BMC Helix trademarks. See BMC Helix Trademark Guidelines.
TrueSight: Capital T, capital S (TrueSight); note that TrueSight is a trademark and is not prefaced with “BMC Helix.” See BMC Helix Trademark Guidelines.
U
UEBA: user- and entity-based behavior analytics
UK: Acceptable as a noun or adjective for the United Kingdom; do not add periods
UNIX: Not Unix, and include a superscript ® on first use, per legal agreement
URL: This is the accepted abbreviation for Uniform Resource Locator. Do not spell out.
US: The abbreviation is acceptable as a noun or adjective for United States. Use periods only if meaning may be misconstrued.
users: Unless the document deals with technical issues, try to use one of the following terms, which are not as impersonal—people, employees, workers, coworkers, customers, clients
username: One word
use vs. utilize: Use is simpler and is preferable
UX: user experience
V
versions: When abbreviating the word “versions” for new releases of BMC Helix products, use this format: “BMC Helix (product name) V7.0.” Note that the “V” is a capital letter.
versus: Use instead of vs. in copy. Example: The solution automated the steps versus relying on older, manual processes. The abbreviation can be used in graphics and callouts.
VM: virtual machine
VOC: voice of the customer
voicemail: One word
VR: virtual reality
vs.: Only use in lieu of versus in graphics and callouts; always include the period afterward.
W
web page vs. website: Web page is two words. Website is one word. No caps in either, unless in a title or the first word of a sentence.
WEF: Abbreviation for the World Economic Forum, an annual meeting of global, political, and corporate leaders that often strongly influences corporate IT decision making; see Davos.
white paper: Two words—not whitepaper
workflow: One word—not work-flow, nor work flow
worldwide: One word, no hyphen
workstation: One word—not work-station, nor work station
X
x: Should not be used as a substitute for “times” in body copy. Example: The product increased server performance by five times. The exception to this rule is usage in headers, titles, callouts, or graphics where space is limited.
XaaS: everything as a service
Y
you: It is acceptable to address your audience with “you” to help create a personal tone in many assets; in general, datasheets and solution white papers should maintain a more objective, third-person tone.
Z
Zero Trust: Capitalize the term. It may be followed by framework, methodology, model, etc., which are not capitalized.
DIVE DEEPER
E-book
Refer to this comprehensive guide to BMC Helix design principles when creating branded assets.