Semiant Webinar: Accelerate Product Development With AI

Is your product team stretched thin? Is everybody demanding time with your experts, keeping them from getting work done? Then add Semiant to your team to relieve your experts and to align your team.

Get a live demonstration on how Semiant works in any web-based application like DOORS Next, Jama or Jira. Learn what we have planned for the future. Discover how Semiant can save you time and reduce risk in product development.

Not sure what Semiant is all about?

Would you like to learn more? Then let’s have a 15-minute conversation:

Glossary Semiant

Work more efficiently with Semiant glossary browser extension

We are torn what to think of glossaries: on the one hand, everyone on the team is grateful when there’s a well-maintained glossary. On the other hand, no one wants to create and maintain it. The coordination process can also lead to disgruntlement and eat up a lot of time. And even if there is a good glossary: There’s a big risk that many stakeholders won’t hear about it and it will gather dust in a drawer.

We just released several glossary-related features of Semiant. Hopefully, we can help the glossary achieve a renaissance. We invite all readers to try out the latest version of Semiant.

Usefulness of a glossary

For a glossary to be useful, it must be accurate and used. When that’s the case, a glossary has a lot of benefits:

  • Fewer misunderstandings save time, avoid mistakes, and reduce friction
  • New employees can familiarize themselves more quickly and take up less of the experts’ time
  • It is less error-prone to deal with product lines and variants
  • Maintenance over the product lifecycle is simplified

Standard glossary or controlled vocabulary?

Why reinvent the wheel? After all, there are ready-made glossaries on many specialized topics, from “automotive” to “zoology”. And indeed, if there is a suitable glossary, we should use it. For example, INCOSE’s Systems Engineering Handbook includes a glossary (Appendix C: Terms and Definitions).

Standard glossaries are useful in education. But in projects, a standard glossary rarely covers all relevant terms. In addition, terms that are familiar to certain stakeholders may have different meanings. Therefore, controlled vocabulary is an important category of a glossary that can complement or replace a standard glossary. Ideally, then, we have both a standard glossary and a specific glossary. This can be project- department- or organization-specific.

Merge glossaries intelligently with Semiant with the browser extension

Semiant is a virtual quality assistant that performs mundane tasks in product development. To do this, Semiant hooks the glossary into any web-based application via a web browser extension (currently only for Chrome and Edge).

The current version of Semiant is minimal, but already supports multiple sources for the glossary and allows merging in the web browser. How this works can be seen in this video:

Development partner wanted

As you can see in the video, Semiant is currently a minimal demonstrator. However, this shows that the technology works in principle. We have many questions and ideas on where to go from here. We are looking for a development partner who recognizes the potential and wants to help determine the further direction os Semiant. Specific ideas and questions are:

  • Which data sources should we support? Currently Semiant reads existing glossaries from RDF/Turtle data sources.
  • How useful is glossary term extraction via Natural Language Processing (NLP)?
  • What team and categorization capabilities should we implement? Also, how expressive should the data structures be?
  • How important is the use case of gathering contextually relevant information from applicable documents and standards?
  • How can we improve the usability of the glossary with the browser extension?

Have we aroused your interest?

Then let’s have a converation >>

Semiant Traceability

What tools shall Semiant integrate with?

Like any team member, a virtual quality assistant has to access data. Semiant will access the same tools that the other team members use. The question is: What tools are relevant, and which are the most important tools? Which tool shall we integrate with first?

Please help us to answer this question in this poll. And please read on to find out what Semiant would use the integration for.

Integrate with Data Sources

The primary use case for integration is to access data sources. Semiant will analyze the integrated data source to extract glossary terms. This will also allow to establish traceability between the glossary terms and the “items” in that specification.

What exactly an item is depends on the integrated tool. In a classical requirements management tool (Polarion, Jama, etc.), this would be an individual requirement. In a document system or Wiki (Confluence, Google Docs), this could be a sentence, a paragraph or section.

Integration for Other Use Cases

Eventually, we need integrations for other use cases. For instance, Semiant might integration with a task management system to communicate with users. This could be anything like build-in collaboration, which many tools provide. But it could also be an external collaboration platform, like Slack.

Any other thoughts?

If you have an important use case or integration need that is not covered here, then please reach out by using the contact button at the bottom of this page. Also, check out our 2021 roadmap.

Image Source: FreePic


2021 Semiant Roadmap

We officially launched Semiant in July 2021. Semiant uses Natural Language Processing (NLP) to identify key concepts found in your product specifications. From this, it produces an interactive glossary with traceability into your specification. This forms the basis for a solution that aligns language in your team and enables collaboration across departmental boundaries.

Roadmap Until the End of 2021

By the end of this year we will finish building a solution that supports engineers building complex products that must comply with regulatory requirements. Semiant will analyze thousands of pages of standards and related documents and summarize the relevant parts to give practitioners contextualized insights. This will accelerate your team’s work, improve the quality and reduce the risk of missing an audit or to receive contractual penalties.

Summarize relevant passages from standards or applicable documents


We launched our demonstrator in July and are actively looking for feedback. Please contact us to join the program.

July 2021


The demonstrator is a “proof of concept” that allows you to evaluate our technology. You can upload a specification and inspect the resulting glossary.

July 2021

August 2021

Web Browser Extension

The browser extension gives you access to your glossary on any web page: Jira, Zendesk, Jama, you name it.

August 2021

Winter 2021/22


To be valuable in a production environment, we will integrate Semiant with Confluence. This will provide you with an always up to date Glossary for you team.

Winter 2021/22

Spring 2022

Related Information Aggregation

Imagine you have thousands of pages of related documents and standards. You provide a requirement or some text as a starting point, and Semiant will give you summaries of all relevant sections from those documents.

Spring 2022

Roadmap Beyond

We have many ideas on how Semiant can assist practitioners in product development and enable organizational alignment. If you are interested to hear what’s possible, or if you have specific needs that Semiant could address, let’s have a conversation.

We encourage our users to help us shape the future of Semiant. Please join the program so that we can take your feedback into account.