DE · EN
Call us
+41 44 508 80 00 Ueberlandstrasse 1, 8600 Dübendorf
build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | ● 0 skipped | | format
apiVersion: soultec.ch/v1kind: Servicemetadata: name: enterprise-architecture locale: en labels: group: consulting capability/architecture: 2.93 capability/strategy: 3.54 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 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 looks at more than how the IT systems interact. It takes in stability, availability, sustainability and agility, and alongside the technical side, the processes that go with them, because an architecture without the workflows around it is just a diagram. - 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: 267 solutions: - {ref: solutions/hpe/hpe-server, 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.53}
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "enterprise-architecture", "locale": "en", "labels": { "group": "consulting", "capability/architecture": "2.93", "capability/strategy": "3.54" }, "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", "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 looks at more than how the IT systems interact. It takes in\nstability, availability, sustainability and agility, and alongside the technical side, the\nprocesses that go with them, because an architecture without the workflows around it is\njust a diagram." }, { "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": 267, "solutions": [ { "ref": "solutions/hpe/hpe-server", "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.53" } ] }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "enterprise-architecture"locale = "en"[metadata.labels]group = "consulting""capability/architecture" = "2.93""capability/strategy" = "3.54"[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"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[[sections]]heading = "

What it covers

"body = '''Enterprise architecture looks at more than how the IT systems interact. It takes instability, availability, sustainability and agility, and alongside the technical side, theprocesses that go with them, because an architecture without the workflows around it isjust a diagram.'''[[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.'''[[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 = 267[[status.solutions]]ref = "solutions/hpe/hpe-server"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.53"
<?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.93</entry> <entry key="capability/strategy">3.54</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> <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> </spec> <sections> <section> <heading>

What it covers

</heading> <body>Enterprise architecture looks at more than how the IT systems interact. It takes instability, availability, sustainability and agility, and alongside the technical side, theprocesses that go with them, because an architecture without the workflows around it isjust a diagram. </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> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/hpe/hpe-server</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.53</score> </item> </alsoLike> </status></manifest>
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.93 Strategy 3.54
03Solutions
02Capabilities
267Corpus

What it covers

Enterprise architecture looks at more than how the IT systems interact. It takes in stability, availability, sustainability and agility, and alongside the technical side, the processes that go with them, because an architecture without the workflows around it is just a diagram.

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.

Experts for this

Focus areas are not yet confirmed, so nobody is suggested here automatically.

Maybe you? Take a look at our open roles.

You might also like

service 1.00

IT Strategy

service 1.00

Requirements Engineering

post 0.53

VMware by Broadcom – License Changes