Set Up the Enterprise Requirements Area

This article guides OnePlan administrators through setting up and managing an Enterprise Requirements Area in OnePlan. It covers recommended configuration for Plan Types, fields, forms, views, dashboards, and process steps to effectively capture, prioritize, and trace enterprise‑wide business needs and requirements.

While this guide assumes prior OnePlan administration experience, new administrators can also use it as a reference to understand how the Enterprise Requirements Area is structured and managed.

This is an extensive guide, so buckle in and let's get configuring!

What you will accomplish
After completing this guide, you will be able to:
- Create and configure an Enterprise Requirements Area in OnePlan
- Define a Business Need → Requirements Plan Type hierarchy
- Configure lookup fields to support Requirements traceability
- Design Plan Details forms for Business Needs and Requirements
- Create preconfigured views to support prioritization and reporting

Requirements

OnePlan Administrator / Owner permissions

Background

Organizations need a clear, consistent way to manage enterprise‑wide business, regulatory, and operational requirements. OnePlan’s Enterprise Requirements Area provides a centralized location to capture, prioritize, and manage these Requirements while keeping them aligned with strategic goals and delivery initiatives.

By serving as a single source of truth and enabling direct connections to strategies, products, projects, risks, and other plans, the Enterprise Requirements Area improves traceability, visibility, and impact analysis. This supports better decision‑making and coordinated execution across the organization.

Step 1: Create the Enterprise Requirements Area

In this step, you will create the Enterprise Requirements Area and apply the recommended base settings.

To do this, follow the instructions in Create and Manage Areas.

Here are the recommended settings for this Area:

Name: Enterprise Requirements
Description: OnePlan’s Enterprise Requirements Area enables organizations to centrally capture, manage, and prioritize enterprise-wide requirements, ensuring they are consistently aligned with strategic objectives and delivery initiatives. This Area provides a single source of truth for business, regulatory, and operational requirements and allows seamless association with strategies, products, projects, risks, and other plans. By improving traceability, impact analysis, and visibility, the Enterprise Requirements Area supports informed decision-making and coordinated execution across the organization.
Icon Name: Stack
Available Views: List, Board, Dashboard
Available Controls: Gantt
Display on left navigation panel: ✔️

Pasted image 20260225110213.png

Step 2: Create the Enterprise Requirements Plan Type Hierarchy

In this step, you will create new Plan Types and associate existing Plan Types to build a Plan Type hierarchy for this new Area.

Before you can save your new Area, you must add Plan Types. First, create the net new Plan Types, Business Need and Requirements. Then you will create a new lookup field, Associated Requirements, so you can add associated Plan Types into the hierarchy.

Why this matters
The Plan Type hierarchy defines how Business Needs and Requirements relate to each other and to delivery plans. Correct configuration is required for traceability, reporting, and association with other OnePlan Areas.

1. Add the Business Need Plan Type

Business Need should be at the top of the Plan Type hierarchy. Follow the instructions in Create and Update Plan Types to create the new parent Plan Type.
Pasted image 20260225113350.png

2. Add the Requirements Plan Type

Add Requirements as a child Plan Type of Business Need. Follow the instructions in Create and Update Plan Types to create the new child Plan Type.
Pasted image 20260225113417.png

⚠️ Important
Save your form configuration before navigating away to another Plan Type or section.

3. Create a New Associated Requirements Lookup Field

For the recommended Plan Type hierarchy to function properly, you must configure a new multi-lookup field for Requirements, called Associated Requirements. This will allow you to associate other Plan Types to the Requirements Plan Type.

See Configure Lookup Fields for instructions.

Here is the recommended configuration for the Associated Requirements field:

Pasted image 20260225105842.png

4. Add Associated Plan Types to the Enterprise Requirements Plan Type Hierarchy

Return to the Enterprise Requirements Area configuration and add associated Plan Types as children of the Requirements Plan Type. Recommended Plan Types to add into the hierarchy include:

Key Result
Project
Epic
Engagement
Product
Application

See Add Existing Plan Types to a Hierarchy for instructions.

Pasted image 20260225110023.png

Step 3: Configure the Business Need Plan Details Form

In this step, you will configure the Plan Details form for the Business Need Plan Type.

See Set Up Plan Details Forms for instructions.

The following sections detail the recommended settings for the Business Need Plan Details form.

1. Business Need Process Steps and Available Tabs

First, configure the Business Need Process Steps. See Configure the Plan Details Process Flow for instructions.

The recommended process steps and available tabs are as follows:

Process Step	Available Tabs
Identify	Details, Reporting - Visualize
Align	Details, Reporting - Visualize
Approve	Details, Reporting - Visualize
Decompose	Details, Reporting - Visualize
Track	Details, Reporting - Visualize
Closed	Details, Reporting - Visualize

Pasted image 20260225120610.png Pasted image 20260225120632.png

2. Business Need Plan Details Fields and Sections

Next, set up the Plan Details form sections and fields. See Set Up Plan Details Forms for detailed instructions on setting up Details forms.

Note
Fields marked as “New field, must be configured” require creation before they can be added to the form. See Add, Edit, or Remove Form Fields for instructions on how to add new fields directly from the Plan Details configuration interface.

Section 1

Section Name: Business Need Information
Section Layout: 2 Equal Columns
Plan Details Form 2 Equal Sections.png
Section Fields:

Column 1 Fields	Field Type	Field Values / Information	Notes
Name	Text		Existing field, no configuration required
State	Choice	Proposed, Active, Closed, On Hold	Existing field, no configuration required
Status	Choice	(1) On Track, (2) At Risk, (3) Off Track	Existing field, no configuration required
Owner	Lookup		Existing field, no configuration required
Requested By	User		Existing field, no configuration required
Submission Date	Date		New field, must be configured

Column 2 Fields	Field Type	Field Values / Information	Notes
Priority	Choice	(1) High, (2) Medium, (3) Low	Existing field, no configuration required
Urgency	Choice	Critical (Immediate), Short Term (<6 months), Long Term (>6 months)	New field, must be configured
Business Unit	Choice	Organization-specific	Existing field, organization-specific, must be configured
Source	Choice	Internal Stakeholder, Market Research, Customer Feedback, Compliance Requirements	New field, must be configured
Business Driver	Multi-Choice	Revenue Growth, Cost Reduction, Compliance, Customer Experience, Operational Efficiency	New field, must be configured
Benefits	Currency		Existing field, no configuration required

Section 2

Section Name: Description
Section Layout: 1 Column
Plan Details Form 1 Section.png
Section Fields:

Column 1 Fields	Field Type	Field Values / Information	Notes
Description	Rich Text	AI Enabled – Use for plan creation Note: You can hide the column header since it is the only field in the column	Existing field, no configuration required

Section 3

Section Name: Associated Plans
Section Layout: 1 Column
Section Elements:

This section contains a Child Plans Table Element that you must configure. See Create, Add, Edit, or Remove Form Elements for instructions.

Column 1 Elements	Work Type	Lookup Type	Plan Types	Columns	Notes
Child Plans > Associated Requirements	Child Plans	Child Plans	Requirements	Name, Status, Manager, Business Unit	New element, must be configured.

Here is the recommended configuration for the Child Plans table element:

Pasted image 20260225121356.png

Step 4: Configure the Requirements Plan Details Form

You also need to configure the Plan Details form for the new Requirements Plan Type.

See Set Up Plan Details Forms for instructions.

The following sections detail the recommended settings for the Requirements Plan Details form.

1. Requirements Process Steps and Available Tabs

First, configure the Requirements Process Steps. See Configure the Plan Details Process Flow for instructions.

The recommended process steps and available tabs are as follows:

Process Step	Available Tabs
New	Details, Files, Reporting - Visualize
In Review	Details, Files, Reporting - Visualize
Approve	Details, Files, Reporting - Visualize
In Development	Details, Files, Reporting - Visualize
Implemented	Details, Files, Reporting - Visualize
Rejected	Details, Files, Reporting - Visualize
Deferred	Details, Files, Reporting - Visualize

Pasted image 20260226114817.png Pasted image 20260226114836.png