DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get service/enterprise-architecture -o yaml$ soultec get service/enterprise-architecture -o json$ soultec get service/enterprise-architecture -o toml$ soultec get service/enterprise-architecture -o xml$ python3 enterprise-architecture.pyPS> ./enterprise-architecture.ps1$ go run enterprise-architecture.go$ node enterprise-architecture.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: enterprise-architecture locale: en labels: group: consulting capability/architecture: 2.51 capability/strategy: 2.87 annotations: source: src/content/services/en/enterprise-architecture.md route: /en/services/enterprise-architecture/ schema: /nerd/schema/services.json markdown: /en/services/enterprise-architecture.mdspec: title: Enterprise Architecture group: consulting audience: [enterprise, provider] order: 2 tags: [architecture, strategy] summary: >- Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them. photoNeed: >- A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table stub: false draft: false sections: - heading:

What it covers

body: | Enterprise architecture covers how the IT systems interact, their stability, availability, sustainability and agility, and the processes that go with them. - heading:

What comes out of it

body: | A big picture of your IT landscape and your IT services, and from it a roadmap: where applications and systems get consolidated, where the interface between application and process has to improve, and which operating model fits, on premises, hybrid or in the public cloud. Requirements, constraints, assumptions and risks are documented, following a design methodology we have used for years. - heading:

Why the scope grew

body: | IT services increasingly bear directly on a company's products. A device installed at a customer sends system data back; that gets analysed centrally, and where something looks wrong the maintenance can be planned before anything fails. Services like that add value to the product and are a competitive advantage. For them to be possible at all, IT has to be involved early in product development, so that the framework exists. - heading:

What follows from it

body: | An offering like that needs more than the mechanical or electronic engineering. It needs the IT department, and usually further applications and services. It also forces a decision on whether the collected system data is stored and processed locally or directly in a public cloud. That decision is not purely technical. It hangs on data protection, on the contracts with end customers, and on who may analyse the data later.status: corpus: 315 solutions: - {ref: solutions/hpe/hpe-server, score: 0.41} - {ref: solutions/hpe/hpe-server/hpe-synergy, score: 0.41} - {ref: solutions/ibm, score: 0.41} - {ref: solutions/ibm/ibm-power10, score: 0.41} alsoLike: - {ref: services/it-strategie, score: 1.00} - {ref: services/requirements-engineering, score: 1.00} - {ref: posts/vmware-license-changes-2025, score: 0.52} experts: - {ref: experts/aldo-gwerder, score: 0.36} - {ref: experts/steven-rodenburg, score: 0.34} - {ref: experts/fabian-faessler, score: 0.33} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "enterprise-architecture", "locale": "en", "labels": { "group": "consulting", "capability/architecture": 2.51, "capability/strategy": 2.87 }, "annotations": { "source": "src/content/services/en/enterprise-architecture.md", "route": "/en/services/enterprise-architecture/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/enterprise-architecture.md" } }, "spec": { "title": "Enterprise Architecture", "group": "consulting", "audience": [ "enterprise", "provider" ], "order": 2, "tags": [ "architecture", "strategy" ], "summary": "Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": false, "draft": false, "sections": [ { "heading": "

What it covers

", "body": "Enterprise architecture covers how the IT systems interact, their stability, availability,\nsustainability and agility, and the processes that go with them." }, { "heading": "

What comes out of it

", "body": "A big picture of your IT landscape and your IT services, and from it a roadmap: where\napplications and systems get consolidated, where the interface between application and\nprocess has to improve, and which operating model fits, on premises, hybrid or in the public\ncloud. Requirements, constraints, assumptions and risks are documented, following a design\nmethodology we have used for years." }, { "heading": "

Why the scope grew

", "body": "IT services increasingly bear directly on a company's products. A device installed at a\ncustomer sends system data back; that gets analysed centrally, and where something looks\nwrong the maintenance can be planned before anything fails.\n\nServices like that add value to the product and are a competitive advantage. For them to be\npossible at all, IT has to be involved early in product development, so that the framework\nexists." }, { "heading": "

What follows from it

", "body": "An offering like that needs more than the mechanical or electronic engineering. It needs the\nIT department, and usually further applications and services. It also forces a decision on\nwhether the collected system data is stored and processed locally or directly in a public\ncloud.\n\nThat decision is not purely technical. It hangs on data protection, on the contracts with\nend customers, and on who may analyse the data later." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-server", "score": "0.41" }, { "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.41" }, { "ref": "solutions/ibm", "score": "0.41" }, { "ref": "solutions/ibm/ibm-power10", "score": "0.41" } ], "alsoLike": [ { "ref": "services/it-strategie", "score": "1.00" }, { "ref": "services/requirements-engineering", "score": "1.00" }, { "ref": "posts/vmware-license-changes-2025", "score": "0.52" } ], "experts": [ { "ref": "experts/aldo-gwerder", "score": "0.36" }, { "ref": "experts/steven-rodenburg", "score": "0.34" }, { "ref": "experts/fabian-faessler", "score": "0.33" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "enterprise-architecture"locale = "en"[metadata.labels]group = "consulting""capability/architecture" = 2.51"capability/strategy" = 2.87[metadata.annotations]source = "src/content/services/en/enterprise-architecture.md"route = "/en/services/enterprise-architecture/"schema = "/nerd/schema/services.json"markdown = "/en/services/enterprise-architecture.md"[spec]title = "Enterprise Architecture"group = "consulting"audience = ["enterprise", "provider"]order = 2tags = ["architecture", "strategy"]summary = "Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them."photoNeed = "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table"stub = falsedraft = false[[spec.sections]]heading = "

What it covers

"body = '''Enterprise architecture covers how the IT systems interact, their stability, availability,sustainability and agility, and the processes that go with them.'''[[spec.sections]]heading = "

What comes out of it

"body = '''A big picture of your IT landscape and your IT services, and from it a roadmap: whereapplications and systems get consolidated, where the interface between application andprocess has to improve, and which operating model fits, on premises, hybrid or in the publiccloud. Requirements, constraints, assumptions and risks are documented, following a designmethodology we have used for years.'''[[spec.sections]]heading = "

Why the scope grew

"body = '''IT services increasingly bear directly on a company's products. A device installed at acustomer sends system data back; that gets analysed centrally, and where something lookswrong the maintenance can be planned before anything fails.Services like that add value to the product and are a competitive advantage. For them to bepossible at all, IT has to be involved early in product development, so that the frameworkexists.'''[[spec.sections]]heading = "

What follows from it

"body = '''An offering like that needs more than the mechanical or electronic engineering. It needs theIT department, and usually further applications and services. It also forces a decision onwhether the collected system data is stored and processed locally or directly in a publiccloud.That decision is not purely technical. It hangs on data protection, on the contracts withend customers, and on who may analyse the data later.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/hpe/hpe-server"score = "0.41"[[status.solutions]]ref = "solutions/hpe/hpe-server/hpe-synergy"score = "0.41"[[status.solutions]]ref = "solutions/ibm"score = "0.41"[[status.solutions]]ref = "solutions/ibm/ibm-power10"score = "0.41"[[status.alsoLike]]ref = "services/it-strategie"score = "1.00"[[status.alsoLike]]ref = "services/requirements-engineering"score = "1.00"[[status.alsoLike]]ref = "posts/vmware-license-changes-2025"score = "0.52"[[status.experts]]ref = "experts/aldo-gwerder"score = "0.36"[[status.experts]]ref = "experts/steven-rodenburg"score = "0.34"[[status.experts]]ref = "experts/fabian-faessler"score = "0.33"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>enterprise-architecture</name> <locale>en</locale> <labels> <group>consulting</group> <entry key="capability/architecture">2.51</entry> <entry key="capability/strategy">2.87</entry> </labels> <annotations> <source>src/content/services/en/enterprise-architecture.md</source> <route>/en/services/enterprise-architecture/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/enterprise-architecture.md</markdown> </annotations> </metadata> <spec> <title>Enterprise Architecture</title> <group>consulting</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>2</order> <tags> <item>architecture</item> <item>strategy</item> </tags> <summary>Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them.</summary> <photoNeed>A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table</photoNeed> <stub>false</stub> <draft>false</draft> <sections> <section> <heading>

What it covers

</heading> <body>Enterprise architecture covers how the IT systems interact, their stability, availability,sustainability and agility, and the processes that go with them. </body> </section> <section> <heading>

What comes out of it

</heading> <body>A big picture of your IT landscape and your IT services, and from it a roadmap: whereapplications and systems get consolidated, where the interface between application andprocess has to improve, and which operating model fits, on premises, hybrid or in the publiccloud. Requirements, constraints, assumptions and risks are documented, following a designmethodology we have used for years. </body> </section> <section> <heading>

Why the scope grew

</heading> <body>IT services increasingly bear directly on a company's products. A device installed at acustomer sends system data back; that gets analysed centrally, and where something lookswrong the maintenance can be planned before anything fails.Services like that add value to the product and are a competitive advantage. For them to bepossible at all, IT has to be involved early in product development, so that the frameworkexists. </body> </section> <section> <heading>

What follows from it

</heading> <body>An offering like that needs more than the mechanical or electronic engineering. It needs theIT department, and usually further applications and services. It also forces a decision onwhether the collected system data is stored and processed locally or directly in a publiccloud.That decision is not purely technical. It hangs on data protection, on the contracts withend customers, and on who may analyse the data later. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/hpe/hpe-server</ref> <score>0.41</score> </item> <item> <ref>solutions/hpe/hpe-server/hpe-synergy</ref> <score>0.41</score> </item> <item> <ref>solutions/ibm</ref> <score>0.41</score> </item> <item> <ref>solutions/ibm/ibm-power10</ref> <score>0.41</score> </item> </solutions> <alsoLike> <item> <ref>services/it-strategie</ref> <score>1.00</score> </item> <item> <ref>services/requirements-engineering</ref> <score>1.00</score> </item> <item> <ref>posts/vmware-license-changes-2025</ref> <score>0.52</score> </item> </alsoLike> <experts> <item> <ref>experts/aldo-gwerder</ref> <score>0.36</score> </item> <item> <ref>experts/steven-rodenburg</ref> <score>0.34</score> </item> <item> <ref>experts/fabian-faessler</ref> <score>0.33</score> </item> </experts> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "enterprise-architecture", "locale": "en", "labels": { "group": "consulting", "capability/architecture": 2.51, "capability/strategy": 2.87, }, "annotations": { "source": "src/content/services/en/enterprise-architecture.md", "route": "/en/services/enterprise-architecture/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/enterprise-architecture.md", }, }, "spec": { "title": "Enterprise Architecture", "group": "consulting", "audience": ["enterprise", "provider"], "order": 2, "tags": ["architecture", "strategy"], "summary": "Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": False, "draft": False, "sections": [ { "heading": "

What it covers

", "body": ( "Enterprise architecture covers how the IT systems interact, their stability, availability,\n" "sustainability and agility, and the processes that go with them." ), }, { "heading": "

What comes out of it

", "body": ( "A big picture of your IT landscape and your IT services, and from it a roadmap: where\n" "applications and systems get consolidated, where the interface between application and\n" "process has to improve, and which operating model fits, on premises, hybrid or in the public\n" "cloud. Requirements, constraints, assumptions and risks are documented, following a design\n" "methodology we have used for years." ), }, { "heading": "

Why the scope grew

", "body": ( "IT services increasingly bear directly on a company's products. A device installed at a\n" "customer sends system data back; that gets analysed centrally, and where something looks\n" "wrong the maintenance can be planned before anything fails.\n" "\n" "Services like that add value to the product and are a competitive advantage. For them to be\n" "possible at all, IT has to be involved early in product development, so that the framework\n" "exists." ), }, { "heading": "

What follows from it

", "body": ( "An offering like that needs more than the mechanical or electronic engineering. It needs the\n" "IT department, and usually further applications and services. It also forces a decision on\n" "whether the collected system data is stored and processed locally or directly in a public\n" "cloud.\n" "\n" "That decision is not purely technical. It hangs on data protection, on the contracts with\n" "end customers, and on who may analyse the data later." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-server", "score": "0.41", }, { "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.41", }, { "ref": "solutions/ibm", "score": "0.41", }, { "ref": "solutions/ibm/ibm-power10", "score": "0.41", }, ], "alsoLike": [ { "ref": "services/it-strategie", "score": "1.00", }, { "ref": "services/requirements-engineering", "score": "1.00", }, { "ref": "posts/vmware-license-changes-2025", "score": "0.52", }, ], "experts": [ { "ref": "experts/aldo-gwerder", "score": "0.36", }, { "ref": "experts/steven-rodenburg", "score": "0.34", }, { "ref": "experts/fabian-faessler", "score": "0.33", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'enterprise-architecture' locale = 'en' labels = [ordered]@{ group = 'consulting' 'capability/architecture' = 2.51 'capability/strategy' = 2.87 } annotations = [ordered]@{ source = 'src/content/services/en/enterprise-architecture.md' route = '/en/services/enterprise-architecture/' schema = '/nerd/schema/services.json' markdown = '/en/services/enterprise-architecture.md' } } spec = [ordered]@{ title = 'Enterprise Architecture' group = 'consulting' audience = @('enterprise', 'provider') order = 2 tags = @('architecture', 'strategy') summary = 'Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them.' photoNeed = 'A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table' stub = $false draft = $false sections = @( [ordered]@{ heading = '

What it covers

' body = @'Enterprise architecture covers how the IT systems interact, their stability, availability,sustainability and agility, and the processes that go with them.'@ } [ordered]@{ heading = '

What comes out of it

' body = @'A big picture of your IT landscape and your IT services, and from it a roadmap: whereapplications and systems get consolidated, where the interface between application andprocess has to improve, and which operating model fits, on premises, hybrid or in the publiccloud. Requirements, constraints, assumptions and risks are documented, following a designmethodology we have used for years.'@ } [ordered]@{ heading = '

Why the scope grew

' body = @'IT services increasingly bear directly on a company's products. A device installed at acustomer sends system data back; that gets analysed centrally, and where something lookswrong the maintenance can be planned before anything fails.Services like that add value to the product and are a competitive advantage. For them to bepossible at all, IT has to be involved early in product development, so that the frameworkexists.'@ } [ordered]@{ heading = '

What follows from it

' body = @'An offering like that needs more than the mechanical or electronic engineering. It needs theIT department, and usually further applications and services. It also forces a decision onwhether the collected system data is stored and processed locally or directly in a publiccloud.That decision is not purely technical. It hangs on data protection, on the contracts withend customers, and on who may analyse the data later.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/hpe/hpe-server' score = '0.41' } [ordered]@{ ref = 'solutions/hpe/hpe-server/hpe-synergy' score = '0.41' } [ordered]@{ ref = 'solutions/ibm' score = '0.41' } [ordered]@{ ref = 'solutions/ibm/ibm-power10' score = '0.41' } ) alsoLike = @( [ordered]@{ ref = 'services/it-strategie' score = '1.00' } [ordered]@{ ref = 'services/requirements-engineering' score = '1.00' } [ordered]@{ ref = 'posts/vmware-license-changes-2025' score = '0.52' } ) experts = @( [ordered]@{ ref = 'experts/aldo-gwerder' score = '0.36' } [ordered]@{ ref = 'experts/steven-rodenburg' score = '0.34' } [ordered]@{ ref = 'experts/fabian-faessler' score = '0.33' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "enterprise-architecture", "locale": "en", "labels": map[string]any{ "group": "consulting", "capability/architecture": 2.51, "capability/strategy": 2.87, }, "annotations": map[string]any{ "source": "src/content/services/en/enterprise-architecture.md", "route": "/en/services/enterprise-architecture/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/enterprise-architecture.md", }, }, "spec": map[string]any{ "title": "Enterprise Architecture", "group": "consulting", "audience": []any{"enterprise", "provider"}, "order": 2, "tags": []any{"architecture", "strategy"}, "summary": "Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": false, "draft": false, "sections": []any{ map[string]any{ "heading": "

What it covers

", "body": "Enterprise architecture covers how the IT systems interact, their stability, availability,\n" + "sustainability and agility, and the processes that go with them.", }, map[string]any{ "heading": "

What comes out of it

", "body": "A big picture of your IT landscape and your IT services, and from it a roadmap: where\n" + "applications and systems get consolidated, where the interface between application and\n" + "process has to improve, and which operating model fits, on premises, hybrid or in the public\n" + "cloud. Requirements, constraints, assumptions and risks are documented, following a design\n" + "methodology we have used for years.", }, map[string]any{ "heading": "

Why the scope grew

", "body": "IT services increasingly bear directly on a company's products. A device installed at a\n" + "customer sends system data back; that gets analysed centrally, and where something looks\n" + "wrong the maintenance can be planned before anything fails.\n" + "\n" + "Services like that add value to the product and are a competitive advantage. For them to be\n" + "possible at all, IT has to be involved early in product development, so that the framework\n" + "exists.", }, map[string]any{ "heading": "

What follows from it

", "body": "An offering like that needs more than the mechanical or electronic engineering. It needs the\n" + "IT department, and usually further applications and services. It also forces a decision on\n" + "whether the collected system data is stored and processed locally or directly in a public\n" + "cloud.\n" + "\n" + "That decision is not purely technical. It hangs on data protection, on the contracts with\n" + "end customers, and on who may analyse the data later.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/hpe/hpe-server", "score": "0.41", }, map[string]any{ "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.41", }, map[string]any{ "ref": "solutions/ibm", "score": "0.41", }, map[string]any{ "ref": "solutions/ibm/ibm-power10", "score": "0.41", }, }, "alsoLike": []any{ map[string]any{ "ref": "services/it-strategie", "score": "1.00", }, map[string]any{ "ref": "services/requirements-engineering", "score": "1.00", }, map[string]any{ "ref": "posts/vmware-license-changes-2025", "score": "0.52", }, }, "experts": []any{ map[string]any{ "ref": "experts/aldo-gwerder", "score": "0.36", }, map[string]any{ "ref": "experts/steven-rodenburg", "score": "0.34", }, map[string]any{ "ref": "experts/fabian-faessler", "score": "0.33", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "enterprise-architecture", locale: "en", labels: { group: "consulting", "capability/architecture": 2.51, "capability/strategy": 2.87, }, annotations: { source: "src/content/services/en/enterprise-architecture.md", route: "/en/services/enterprise-architecture/", schema: "/nerd/schema/services.json", markdown: "/en/services/enterprise-architecture.md", }, }, spec: { title: "Enterprise Architecture", group: "consulting", audience: ["enterprise", "provider"], order: 2, tags: ["architecture", "strategy"], summary: "Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them.", photoNeed: "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", stub: false, draft: false, sections: [ { heading: "

What it covers

", body: "Enterprise architecture covers how the IT systems interact, their stability, availability,\n" + "sustainability and agility, and the processes that go with them.", }, { heading: "

What comes out of it

", body: "A big picture of your IT landscape and your IT services, and from it a roadmap: where\n" + "applications and systems get consolidated, where the interface between application and\n" + "process has to improve, and which operating model fits, on premises, hybrid or in the public\n" + "cloud. Requirements, constraints, assumptions and risks are documented, following a design\n" + "methodology we have used for years.", }, { heading: "

Why the scope grew

", body: "IT services increasingly bear directly on a company's products. A device installed at a\n" + "customer sends system data back; that gets analysed centrally, and where something looks\n" + "wrong the maintenance can be planned before anything fails.\n" + "\n" + "Services like that add value to the product and are a competitive advantage. For them to be\n" + "possible at all, IT has to be involved early in product development, so that the framework\n" + "exists.", }, { heading: "

What follows from it

", body: "An offering like that needs more than the mechanical or electronic engineering. It needs the\n" + "IT department, and usually further applications and services. It also forces a decision on\n" + "whether the collected system data is stored and processed locally or directly in a public\n" + "cloud.\n" + "\n" + "That decision is not purely technical. It hangs on data protection, on the contracts with\n" + "end customers, and on who may analyse the data later.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/hpe/hpe-server", score: "0.41", }, { ref: "solutions/hpe/hpe-server/hpe-synergy", score: "0.41", }, { ref: "solutions/ibm", score: "0.41", }, { ref: "solutions/ibm/ibm-power10", score: "0.41", }, ], alsoLike: [ { ref: "services/it-strategie", score: "1.00", }, { ref: "services/requirements-engineering", score: "1.00", }, { ref: "posts/vmware-license-changes-2025", score: "0.52", }, ], experts: [ { ref: "experts/aldo-gwerder", score: "0.36", }, { ref: "experts/steven-rodenburg", score: "0.34", }, { ref: "experts/fabian-faessler", score: "0.33", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 74 lines · YAML · validated at build# 104 lines · JSON · validated at build# 113 lines · TOML · validated at build# 129 lines · XML · validated at build# 129 lines · Python · read back at build, equals the JSON record# 126 lines · PowerShell · read back at build, equals the JSON record# 133 lines · Go · read back at build, equals the JSON record# 118 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/enterprise-architecture.md

Service · consulting

Enterprise Architecture

Not only how the systems fit together, but stability, availability, sustainability and agility. And the processes behind them.

Topics Architecture 2.51 Strategy 2.87

04Solutions

02Capabilities

315Corpus

photograph wantedA working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table

What it covers

Enterprise architecture covers how the IT systems interact, their stability, availability, sustainability and agility, and the processes that go with them.

What comes out of it

A big picture of your IT landscape and your IT services, and from it a roadmap: where applications and systems get consolidated, where the interface between application and process has to improve, and which operating model fits, on premises, hybrid or in the public cloud. Requirements, constraints, assumptions and risks are documented, following a design methodology we have used for years.

Why the scope grew

IT services increasingly bear directly on a company’s products. A device installed at a customer sends system data back; that gets analysed centrally, and where something looks wrong the maintenance can be planned before anything fails.

Services like that add value to the product and are a competitive advantage. For them to be possible at all, IT has to be involved early in product development, so that the framework exists.

What follows from it

An offering like that needs more than the mechanical or electronic engineering. It needs the IT department, and usually further applications and services. It also forces a decision on whether the collected system data is stored and processed locally or directly in a public cloud.

That decision is not purely technical. It hangs on data protection, on the contracts with end customers, and on who may analyse the data later.