Getting started

Bloom PLM is EmbedLabs’ product lifecycle management app. It covers requirements, controlled documents, verification, risks, changes, defects, baselines, and end-to-end traceability. You self-host it with one container image plus PostgreSQL.

What Bloom provides

• Requirements and controlled documents across supported artefact types
• Test cases, suites, campaigns, concepts, and verification planning
• Risks, changes, defects, parameters, and baselines
• Traceability links, relationship views, and coverage analysis
• Notifications, and project-wide search across artefacts
• Inline # tags that turn a mention in a document body into a link a reader can follow
• Stable document IDs such as PRJ-REQ-001 for controlled project records
• Administrator, maintainer, and external-user access controls
• ReqIF and Markdown document import; test cases import from CSV and XML and export as CSV, XML, and Markdown
• PDF and CSV exports, with an optional administrator company logo on PDF reports
• GitHub, GitLab, and Jira synchronization for defects and change requests
• Optional test case execution outcomes from Bud TMP
• Readiness, health, metrics, structured logging, and backup workflows

How Bloom fits with Bud

Bloom manages product definition, traceability, and verification intent. Bud manages test execution evidence. Each product runs independently.

When the two are connected, the execution path is:

1. Tests use budtestlibrary for lifecycle, assertions, results, and optional Bloom test case metadata.
2. bud-runner executes those tests and uploads results to Bud TMP.
3. Bud sends scoped execution outcomes to the matching Bloom test cases.
4. Bloom answers with the campaigns those outcomes reached, so a run in Bud links back to the campaign it came from.

Bloom does not require Bud, bud-runner, or budtestlibrary for its PLM workflows, and Bud does not require Bloom. The link in either direction appears when a pairing exists and is absent otherwise. The test side is covered in the Bud docs.

First steps

1. Install Bloom with Docker Compose or on Cloudron.
2. Open /setup on your instance and create the first administrator. Setup closes once a user exists.
3. Configure outgoing email so Bloom can send invitations, verification and password reset links.
4. Give people access: a role each, then a group of policies in each project.
5. Optionally connect Bud so test case execution outcomes reach Bloom.

Then read the concepts that shape a project: artefact IDs, typed links, suspect links, coverage and issue tracker sync.