A  Period Type that is an arbitrary period of time.

 Period Type is used to define the period on which Time Events or Event Concepts can occur.

Examples:

- Year - the set of all years (..., -5000, ... 50, ..., 800, ..., 1000, ..., 1789, ..., 1946, ..., 2050, ...)

- 3.345 Nanoseconds- the set of all 3.345 Nanosecond periods.

- Quater - the set all all quaters : 1 quater of 1492, 3rd quater of 2056, ....

- 7000 Years- the set of all 7000 Year period.

An  Action Process is a Behavior that describes a typical course of action intended to produce Outcome Events, through the involvement of Agents as Active Participants.

During its course of action, a process consumes or produces Functional Assets, including Information Assets.

1) It may memorize or access Information Assets from and to its Process Stores.

2) It may receive Functional Assets at its boundary: Outcome Consumptions.

3) It may signal the production of Functional Assets at its boundary: Outcome Productions.

The course of actions of a  Action Process is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do.

Within  SysFEAT, we can examine  Action Processes from two distinct perspectives:

a) A conceptual standpoint is provided by Value Streams.

b) A concrete implementation standpoint is provided by Resource Action Processes.

An  Agent is an Operating Asset which is able to participate actively to Behaviors, to produce and react to Outcome Events.

1.  Agents participate to Action Processes (Active Participant) and/or conduct Action Processes (Performed Process).

2.  Agents participate to Interaction Process (Scenario Participant) describing how they interact with other  Agents.

These actions and interactions define  Agents boundaries described by Service Interfaces.

An  Agent State is a temporal slice type of an Agent related to its lifefcyle.
Examples:

. The lifecycle phases of a person, such as childhood, adulthood, eldery stage.

. The lifecyle phases of a hospital such as construction phase, operation and maintenance phase, renovation and expansion phase, decommissioning phase.

A  Behavior is an Operating Asset that describes any action or reaction of an Agent to external or internal Behavioral Events.  Behaviors include Action Processes (action), Interaction Processs (stories) or interactions (Service Interface).

The course of actions of a  Behavior is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do.

A  Behavioral Event is a Temporal Bounding Type that establishes a temporal connection between Behaviors.

A  Behavioral Event connects a Predecessor  Behavioral Event, to a Successor  Behavioral Event.

A  Behavioral Rule is a Directive intended to guide the Behavior of Agents, in compliance with enterprise Policy(ies) or regulations.

Often, a  Behavioral Rule is derived from a Policy.  Behavioral Rules are enforced in Processes and Agents.

A  Capability is a functional  Asset Property which refers to the ability to produce an Outcome Event.

Capabilitys are fulfilled by Agents performing Processes and interacting with other Agents to produce the desired Outcome Event.

A  Class of Bounded Individual is a Class of Individual which denotes Bounded Individuals that have a proper life cycle, bounded by Temporal Bounding Types.

 Class of Bounded Individual is the powertype of  Bounded Individual. It means that all sub-types of Bounded Individual are instances of  Class of Bounded Individual.

Examples:

- Car, , Application,

- A Process Type (Action Process) such as the registration process used at the Oackland digital hospital during the COVID-19 pandemic.

Counterexamples:

- Project is not a  Class of Bounded Individual because its instances have a spatio-temporal extent. Project is a subtype of Bounded Individual.

- Capability is not a  Class of Bounded Individual. It is a Property.

An  Environment Interaction Process is a story that describes how an Agent interacts with its partners (Partner Agent) to achieve Outcome Events in a specific Operating Eco-System (Agent Environment).

This includes:

1) A course of events represented by Object Flows depicting the succession of intermediate Outcome Events towards the production and consumption of final Outcome Events.

2) Interacting partners who participate to the story in the considered Operating Eco-System.

 Functional Assets encompasse all  Architecture Asset Types used to describe why and how systems operate/function. This includes the Operating Eco-System where system operates to fulfill these purposes (Agents and their  Behaviors).

 Functional Assets include:

1. Blocks defining results of Behaviors of the enterprise or its sub-systems, that benefit to it internal or external customers : Outcome Event,

2. Blocks used to describe information: Information Asset.

3. Blocks used to describe how the enterprise operates: Operating Assets (Agent, Behavior, Service Interface).

All  Functional Assets are constrained by Policys and are exposed to Risk Types.

An  Individual Event is a Temporal Bounding that establishes a temporal connection between Individual Behaviors.

An  Individual Event connects a Previous Behavioral Event, to a Next Behavioral Event.

An  Individual Macro Operating Asset is an Individual Operating Asset which correspond to a large-scale enterprise assets. This level of analysis is concerned with understanding how large enterprise systems operate and how they interact with each other.

Examples of macro-level systems:

. Legal entities

. The overall enterprise IT System

. The internet

. System of Systems

. The Enterprise itself.,

A  Individual Mezzo Operating Asset at is the intermediate level between the foundational  Individual Mezzo Operating Assets and the overarching Individual Micro Operating Assets.

At the mezzo level, aggregates or collections of Micro Operating Assets come together to form larger entities or sub-systems.

Boundaries and signals at the mezzo level arise from the interactions and emergent behaviors of micro-level components, yet they also have their own distinct properties and rules not strictly reducible to the micro behaviors.

Emergence at the mezzo level can be analyzed:

1) Bottom-up: Looking at how interactions and behaviors at the micro level give rise to emergent phenomena, structures, or behaviors at the mezzo level.

2)Top-down: Understanding how meso-level structures influence and constrain the behaviors and interactions of the micro-level components within them.

A  Individual Micro Operating Asset represents the foundational level at which a system's structure and interactions can be analyzed without further subdivision into smaller constituent parts.

 Individual Micro Operating Assets set the stage for how higher-level behaviors emerge. As one moves up to higher hierarchical levels (mezzo, macro, etc.), the signals and boundaries at each of those levels are influenced by the foundational interactions set at the micro level.

An  Information Asset  represents anything that can be communicated or memorized by an Agent to produce and react to Outcome Events.

An  Information Asset is either an Information Entity or an  Information Property.
The difference lies in their relationship to change and to time. Information Entity(ies) can change over time and have a lifeycle while  Information Propertys are immutable characteristics.

An  Interaction Process is a story (Behavior) that describes how the components of an Agent interacts to produce and consume Outcome Events.
This includes:

1) A course of events represented by  Object Flows depicting the succesion of  intermediate Outcome Events towards the production of the final Outcome Events.

2) Interacting Agents who participate to the story.

A  type of  Macro Operating Asset is an Operating Asset which corresponds to a large-scale enterprise assets. This level of analysis is concerned with understanding how large enterprise systems operate and how they interact with each other.

Examples of macro-level systems:

. Type of Legal entities

. System of Systems

A type of  Mezzo Operating Asset at is the intermediate level between the foundational Micro Operating Assets and the overarching Macro Operating Assets.

At the mezzo level, aggregates or collections of Micro Operating Assets come together to form larger entities or sub-systems.

Boundaries and signals at the mezzo level arise from the interactions and emergent behaviors of micro-level components, yet they also have their own distinct properties and rules not strictly reducible to the micro behaviors.

Emergence at the mezzo level can be analyzed:

1) Bottom-up: Looking at how interactions and behaviors at the micro level give rise to emergent phenomena, structures, or behaviors at the mezzo level.

2)Top-down: Understanding how meso-level structures influence and constrain the behaviors and interactions of the micro-level components within them.

A type of  Micro Operating Asset represents the foundational level at which a system's structure and interactions can be analyzed without further subdivision into smaller constituent parts.

 Micro Operating Assets set the stage for how higher-level behaviors emerge. As one moves up to higher hierarchical levels (mezzo, macro, etc.), the signals and boundaries at each of those levels are influenced by the foundational interactions set at the micro level.

An  Operating Asset is a Functional Asset that describes the way Outcome Events are produced and consumed: how (Behaviors) and by whom (Agents).

 Operating Assets fulfill Capability(ies) (Fulfilled Capability).

As any  Functional Architecture Asset,  Operating Assets are subject to Policy Conformances. In addition, they define Rule Enforcements to indicate how Policy Conformances are met.

A  Policy is a Directive that is not directly enforceable whose purpose is to govern, guide or constrain the structure and Behavior of Agents in the enterprise.

Policies provide the basis for rules and govern Behaviors carried out by Agents.

Example of Policys are Regulation Articles, Business Policys or Architecture principles.

A  Risk Type is a distinct category or classification of risk based on its origin, nature, or potential impact. It helps in organizing and addressing different sources of uncertainty or potential harm that an individual, organization, or system might face. By categorizing risks into different types, entities can develop more targeted mitigation strategies and response plans.

Common risk types include Operational Risk Type, Privacy Risk Type, and Compliance Risk Type, among others,

A  Whole Life Agent is an Agent that is not the temporal slice type of any other Agent.

Examples:

. A type of building such as a skycraper.

. A type of person such as a philosopher.

. A type of facility such as a Hospital.

An  Action Process is a Behavior that describes a typical course of action intended to produce Outcome Events, through the involvement of Agents as Active Participants.

During its course of action, a process consumes or produces Functional Assets, including Information Assets.

1) It may memorize or access Information Assets from and to its Process Stores.

2) It may receive Functional Assets at its boundary: Outcome Consumptions.

3) It may signal the production of Functional Assets at its boundary: Outcome Productions.

The course of actions of a  Action Process is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do.

Within  SysFEAT, we can examine  Action Processes from two distinct perspectives:

a) A conceptual standpoint is provided by Value Streams.

b) A concrete implementation standpoint is provided by Resource Action Processes.

An  Agent is an Operating Asset which is able to participate actively to Behaviors, to produce and react to Outcome Events.

1.  Agents participate to Action Processes (Active Participant) and/or conduct Action Processes (Performed Process).

2.  Agents participate to Interaction Process (Scenario Participant) describing how they interact with other  Agents.

These actions and interactions define  Agents boundaries described by Service Interfaces.

A  Behavior is an Operating Asset that describes any action or reaction of an Agent to external or internal Behavioral Events.  Behaviors include Action Processes (action), Interaction Processs (stories) or interactions (Service Interface).

The course of actions of a  Behavior is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do.

A  Behavioral Event is a Temporal Bounding Type that establishes a temporal connection between Behaviors.

A  Behavioral Event connects a Predecessor  Behavioral Event, to a Successor  Behavioral Event.

An  Environment Interaction Process is a story that describes how an Agent interacts with its partners (Partner Agent) to achieve Outcome Events in a specific Operating Eco-System (Agent Environment).

This includes:

1) A course of events represented by Object Flows depicting the succession of intermediate Outcome Events towards the production and consumption of final Outcome Events.

2) Interacting partners who participate to the story in the considered Operating Eco-System.

 Functional Assets encompasse all  Architecture Asset Types used to describe why and how systems operate/function. This includes the Operating Eco-System where system operates to fulfill these purposes (Agents and their  Behaviors).

 Functional Assets include:

1. Blocks defining results of Behaviors of the enterprise or its sub-systems, that benefit to it internal or external customers : Outcome Event,

2. Blocks used to describe information: Information Asset.

3. Blocks used to describe how the enterprise operates: Operating Assets (Agent, Behavior, Service Interface).

All  Functional Assets are constrained by Policys and are exposed to Risk Types.

An  Individual Event is a Temporal Bounding that establishes a temporal connection between Individual Behaviors.

An  Individual Event connects a Previous Behavioral Event, to a Next Behavioral Event.

An  Individual Macro Operating Asset is an Individual Operating Asset which correspond to a large-scale enterprise assets. This level of analysis is concerned with understanding how large enterprise systems operate and how they interact with each other.

Examples of macro-level systems:

. Legal entities

. The overall enterprise IT System

. The internet

. System of Systems

. The Enterprise itself.,

A  Individual Mezzo Operating Asset at is the intermediate level between the foundational  Individual Mezzo Operating Assets and the overarching Individual Micro Operating Assets.

At the mezzo level, aggregates or collections of Micro Operating Assets come together to form larger entities or sub-systems.

Boundaries and signals at the mezzo level arise from the interactions and emergent behaviors of micro-level components, yet they also have their own distinct properties and rules not strictly reducible to the micro behaviors.

Emergence at the mezzo level can be analyzed:

1) Bottom-up: Looking at how interactions and behaviors at the micro level give rise to emergent phenomena, structures, or behaviors at the mezzo level.

2)Top-down: Understanding how meso-level structures influence and constrain the behaviors and interactions of the micro-level components within them.

A  Individual Micro Operating Asset represents the foundational level at which a system's structure and interactions can be analyzed without further subdivision into smaller constituent parts.

 Individual Micro Operating Assets set the stage for how higher-level behaviors emerge. As one moves up to higher hierarchical levels (mezzo, macro, etc.), the signals and boundaries at each of those levels are influenced by the foundational interactions set at the micro level.

An  Interaction Process is a story (Behavior) that describes how the components of an Agent interacts to produce and consume Outcome Events.
This includes:

1) A course of events represented by  Object Flows depicting the succesion of  intermediate Outcome Events towards the production of the final Outcome Events.

2) Interacting Agents who participate to the story.

A  type of  Macro Operating Asset is an Operating Asset which corresponds to a large-scale enterprise assets. This level of analysis is concerned with understanding how large enterprise systems operate and how they interact with each other.

Examples of macro-level systems:

. Type of Legal entities

. System of Systems

A type of  Mezzo Operating Asset at is the intermediate level between the foundational Micro Operating Assets and the overarching Macro Operating Assets.

At the mezzo level, aggregates or collections of Micro Operating Assets come together to form larger entities or sub-systems.

Boundaries and signals at the mezzo level arise from the interactions and emergent behaviors of micro-level components, yet they also have their own distinct properties and rules not strictly reducible to the micro behaviors.

Emergence at the mezzo level can be analyzed:

1) Bottom-up: Looking at how interactions and behaviors at the micro level give rise to emergent phenomena, structures, or behaviors at the mezzo level.

2)Top-down: Understanding how meso-level structures influence and constrain the behaviors and interactions of the micro-level components within them.

A type of  Micro Operating Asset represents the foundational level at which a system's structure and interactions can be analyzed without further subdivision into smaller constituent parts.

 Micro Operating Assets set the stage for how higher-level behaviors emerge. As one moves up to higher hierarchical levels (mezzo, macro, etc.), the signals and boundaries at each of those levels are influenced by the foundational interactions set at the micro level.

An  Operating Asset is a Functional Asset that describes the way Outcome Events are produced and consumed: how (Behaviors) and by whom (Agents).

 Operating Assets fulfill Capability(ies) (Fulfilled Capability).

As any  Functional Architecture Asset,  Operating Assets are subject to Policy Conformances. In addition, they define Rule Enforcements to indicate how Policy Conformances are met.