> For the complete documentation index, see [llms.txt](https://docs.aisl.science/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisl.science/applications/additional-hsw-services.md).

# Additional HSW Services

In addition to AISL-hosted applications, AISL administers access to selected **FHNW School of Business (HSW)** teaching tools. These services use separate access or licensing arrangements and are typically provided as part of a module.

## Flowable

A process-management and automation platform used in selected HSW modules and project work.

**Best for:** Process modeling, execution, and automation activities defined in a course.

[Open Flowable](https://fhnw.cloud.flowable.com/)

## Trisotech

A modeling environment used in selected HSW modules for business process and decision modeling.

**Best for:** Course activities involving process and decision models.

[Open Trisotech](https://fhnw.trisotech.com)

## Visual Paradigm

Visual Paradigm licenses are made available in selected HSW modules for modeling and related coursework.

**Best for:** Modeling activities where the module specifically uses Visual Paradigm.

{% hint style="info" %}
**Access:** Follow the instructions provided by your instructor or module team. Access and licenses can differ by course.
{% endhint %}

For general access questions, contact <engines@aisl.science>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aisl.science/applications/additional-hsw-services.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.