GenAI Configuration
Prerequisites
Project Template
Create a project containing the folder structure you want to use. If you do not have a project template, please contact Blueprint Support for assistance.
Your template should include the preconfigured folder structure and any standard artifacts you want to use in the project.

This project will be used when creating new projects that use the “Import Using GenAI” feature and will be your template project when configuring the GenAI settings in Blueprint.
GenAI Token
Before configuring the GenAI settings in BLueprint, you must have an OpenAI account and create a token for Blueprint. The token must have at least the following permissions:
- Models = Read
- Model Capabilities = Write
- Assistants = Write
- Threads = Read
- Evals = None
- Fine Tuning = None
- Files = Write
GenAI Blueprint Configuration
After completing the prerequisites, and before using the GenAI import solution, a System Administrator will need to configure the GenAI connection, configure the template project, and create the required artifact associations and trace mappings that will be used during the artifact creation.
To access the GenAI configuration, please go to:
- Admin Portal (
gear icon top right of the screen in the Blueprint UI)
- Select GenAI

GenAI Connection
To use the GenAI import solution, a connection to your GenAI must be created using a OpenAI Token. Blueprint does not provide the token; you must supply your own.
To enable:
- Expand the GenAI Connection settings box
- Select the Enable GenAI Features check box, with a check mark the option is enabled.
- Enter your API Token into the text field.
- Click the Test button to ensure the connection is successful.
- Once successfully connected, choose the desired OpenAI model from the selection list
- Click the Save button at the bottom of the page to apply changes.

Document Import Specification
- Select Project Template: a project containing folders used to organize the newly created requirements. The folders in this project will be available for selection in the “Path” column of the Category Table below. This project should also be used as the template for the Project that will use the “Import Using GenAI” feature.
- TOC Artifact: this is the artifact type that will be used to store the source document sections
- Trace Requirements: when enabled, Blueprint will create traces between the newly created requirements according to the ‘Traces’ settings in the Category Table below.
- Trace Document Sections with Requirements: When enabled, traces will be added between the newly created requirements and the source document section from which they were extracted.
- Create Single Requirement from Document Section: When enabled, a single requirement artifact will be created for the entire contents of each document section. Otherwise, Blueprint will decompose the document section into multiple requirements artifacts.
- Category Table: This table determines how the GenAI will discover requirements, the artifact type used when creating requirements, in which folder the requirements will be stored, and which requirement types can be traced.
- Category: GenAI uses this category solely to detect requirements in the source text. They are not used and do not appear anywhere else in the product. Categories should be common industry-standard terms for kinds of requirements. The defaults provided by Blueprint have met this criteria, but you can modify or add your own.
- Path: The folder where requirements of this category should be stored within Blueprint. The set of available folders are those from the selected template project above.
- Artifact Type: The Blueprint artifact type to be used for requirements of this category.
- Traces: Categories will be examined for possible relationships for which traces may be created.
