BERT Documentation
  • Getting Started
    • Get Started with BERT
    • Why BERT?
    • Creating Your First System
      • Step 1: Starting a New Project
      • Step 2: Define Your System of Interest
      • Step 3: Identify Primary Output
      • Step 4: Define Output Interface
      • Step 5: Add Customer Sink
      • Step 6: Add a Waste Output
      • Step 7: Identify Primary Inputs
      • Step 8: Traverse The Boundary
      • Step 9: Add Boundary Subsystems
      • Step 10: Adding Internal Flows
      • Step 11: System Decomposition
      • Step 11: Share JSON
      • Next Steps
      • System Elements
      • Advanced Features
      • Video Tutorial
    • Reference Guide
    • Glossary
    • Examples
      • A Home
      • A Cell
      • An LLM
  • Case Studies
    • Bitcoin
  • Analysis, Modeling and Simulation
    • Deep Systems Analysis
    • Modeling
    • Simulation
  • For Researchers
    • System Ontology
    • System Language
  • For Developers
    • Contributing
    • Architecture
  • Roadmap
    • Alpha
  • Beta
  • 1.0
Powered by GitBook
On this page
  1. Getting Started
  2. Creating Your First System

Step 3: Identify Primary Output

PreviousStep 2: Define Your System of InterestNextStep 4: Define Output Interface

Last updated 2 months ago

Identifying your System's Core "Product"

After we have identified our SOI our next step is to identify its primary product output flow.

All systems can be understood as dynamic entities that operate over time scales. To maintain themselves as systems, as opposed to disconnected parts, they must continuously:

  1. Receive inputs

  2. Process those inputs

  3. Create outputs that are useful to some entity in its environment, which consists of other systems.

Ask yourself — what is the purpose of your system. What is the most important thing that it creates?

Of course, most complex adaptive systems we are interested in will have multiple important purposes and outputs, but for the sake of simplicity we begin our analysis by identifying a single one that feels most relevant given our objectives.

Systems analysis is a blend of art and science, and there are many stages like this where subjectivity comes into play. What's important is that we are transparent with ourselves and others about when we are making subjective choices.

Once you've identified what the core product is, it's time to name it and specify its nature as a flow.

Flows represent the measurable materials, energy, or information that move within your system and between your system and its environment

Click the green button to open up a flow arrow.

Click on the word flow to open up an element details box.

Interaction Usability:

  • Product

  • Waste

  • Resource

  • Disruption

Interaction Type:

  • Flow

  • Force

Substance Type:

  • Material Flows: Physical substances (water, products, raw materials)

  • Energy Flows: Power, heat, mechanical energy

  • Information Flows: Data, commands, feedback

Learn about the other details in advanced features.