As part of stakeholder analysis, projects often incorporate stakeholders into their Systems Engineering (SE) model to identify stakeholders from all phases of the system’s life cycle. Examples of stakeholders include local government, emergency services, public utilities, commercial companies, communities, residents, users, maintainers, and others. After intensive contact with stakeholders during the project, the needs of these stakeholders are identified and formulated as stakeholder requirements.
Based on observations at projects, the basic model consists of a type element named Stakeholder, which includes type properties to store the name, email, and phone number.
Typically, the type property Name has a data type of Single line text (to contain a brief name for recognizing the stakeholder), the type property Email has a data type of Single line text (to provide the stakeholder’s email address), and the type property Phone number has a data type of Single line text (to provide the stakeholder’s phone number).
Address
Sometimes, projects incorporate address information for stakeholders in their SE Model. For example, to visit stakeholders during a meeting or to inform stakeholders by mail.
Single address
Based on observations at projects, the type element Stakeholder has been enriched with type properties to store the street address, postal code, and city.
Typically, the type property Street address has a data type of Single line text (to contain the street where the stakeholder is located), the type property Postal code has a data type of Single line text (to provide the postal code that matches the address), and the type property City has a data type of Single line text (to provide the name of the city that matches the address).
Multi addresses
Sometimes, stakeholders are located at different addresses. For example, a local government or commercial company that has multiple offices.

In the model, a derived type element Address is created for the type element Stakeholder. The cardinality of the derived element is set to Multi, which allows multiple addresses to be created for a stakeholder. Additionally, the setting Act as inner element is enabled for the derived type element. Since most users are not interested in seeing a full overview of addresses regardless of the stakeholder, an address is generally considered an inner type element.
Common properties for an attachment include Street, postal code, and City. The data types are similar to those described for the single address model pattern.
Scope
A stakeholder is not always the same; in some cases, it is an individual, while in others, it is an organization. The ideal model pattern for your project may depend on the differences in the amount and type of information you need to store in Relatics for stakeholder persons versus stakeholder organizations.
Stakeholders with scope property
One way projects account for the scope of a stakeholder is by labeling each stakeholder as Organization or Person. The main advantage of this approach is flexibility, as you can easily toggle the scope of an existing stakeholder at a later time. This model pattern is ideal when stakeholder organizations and stakeholder persons share the same properties and relations.
When projects adopt this model pattern, a type property Scope is created in the model for the type element Stakeholder. Typically, the type property Scope has a data type List that includes the values Organization and Person to denote whether it concerns a stakeholder organization or a stakeholder person.
Stakeholder organization versus Stakeholder person
Another model pattern involves distinguishing between stakeholder organizations and stakeholder persons. This model’s key advantage is that it allows for different properties and relations to be assigned to stakeholder organizations compared to stakeholder persons.
In this approach, projects create distinct type elements in the model for Stakeholder Organization and Stakeholder Person. As shown, each element type has a unique set of properties. Further, a type relation is contact person of has been created in the model between the Stakeholder Person and Stakeholder Organization type elements. As some stakeholder organizations (e.g., local governments) can have multiple contact persons, this model allows you to find a specific contact person.
Categorization
In some projects, stakeholders are categorized to clarify their role. This helps filter out irrelevant stakeholders by filtering them into a list.
In the model, for the type element Stakeholder, a property Category is created. Typically, the type property Category has a data type of List. Examples of values include Local government, Competent authority, Plot owner, Local business, and Resident.
Assessment
It is common in stakeholder management to assess stakeholders to identify their roles and priorities in the project. Projects often assess stakeholders’ power, influence, and importance. Ranking projects on these properties helps projects make decisions on stakeholder requirements.
Through reporting, it can be useful to set these properties as a List property with an additional column for possible calculations. This setup also makes it easier to filter and sort stakeholders, for example, based on their Importance.
The extra column can be used to create a calculated property, which would represent the total ‘weight’ of the stakeholder. For instance, the sum of the Power, Influence, and Importance could result in a total Weight for the stakeholder.
Attitude
If land lots that are part of the project scope are owned or used by stakeholders, projects sometimes decide to track their attitudes relative to the land lots. In stakeholder management, this can help the project know how to approach and communicate with stakeholders in case the land lots are affected or needed during construction.
In the model, a middle type element Attitude is created for the type element Stakeholder. The cardinality of the derived element is set to Multi, as stakeholders can have a stake at multiple land lots. Additionally, the setting Act as inner element is enabled for the derived type element. Since most users are not interested in seeing a full overview of attitudes regardless of the stakeholder, an attitude is generally considered an inner type element.
The target relation of the middle type element is set to the type element Land lot. This assures that an attitude can only exist for a combination of a stakeholder and a land lot. Finally, the feature Enforce uniqueness on origin-target combinations is enabled. This restricts a unique combination of a stakeholder and a land lot to having only one attitude. In practice, projects only assess the attitude once.
Common properties of an attitude include Involvement and Influence. Typically, the type property Involvement has a data type of List (to categorize the involvement of the stakeholder towards the land lot), and the type property Influence has a data type of List (to categorize the influence of the stakeholder towards the land lot).