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/it-architecture -o yaml$ soultec get service/it-architecture -o json$ soultec get service/it-architecture -o toml$ soultec get service/it-architecture -o xml$ python3 it-architecture.pyPS> ./it-architecture.ps1$ go run it-architecture.go$ node it-architecture.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: it-architecture locale: en labels: group: consulting capability/architecture: 2.51 capability/cloud: 1.92 annotations: source: src/content/services/en/it-architecture.md route: /en/services/it-architecture/ schema: /nerd/schema/services.json markdown: /en/services/it-architecture.mdspec: title: IT Architecture group: consulting audience: [enterprise, provider] order: 3 tags: [architecture, cloud] summary: >- Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several. 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 comes out of it

body: | A design for an infrastructure that matches your requirements and fits into the systems you already run. Where it runs is open: on your site, in a co-location, in the public cloud, or spread across several of those. - heading:

How we get there

body: | In requirement workshops we capture the requirements and the constraints for the new platform. The design follows from those, using a design method we have used for years. The point of that method is not the shape of the document. It is that what comes out meets the requirements of everyone involved, not only the technical ones. An architecture that works technically and then fails on procurement, on operations or on data protection is not finished being designed, only finished being drawn. The design is vendor-independent. Requirements, constraints, assumptions and risks are documented in it, and a transformation plan says in which steps the existing estate becomes the new one. - heading:

How this differs from Enterprise Architecture

body: | Enterprise architecture looks at the IT estate as a whole, including processes and the role IT plays in the business. IT architecture designs one concrete platform inside that. Either can be commissioned on its own. When they happen together the order gets easier: first the frame, then the platform that belongs in it.status: corpus: 315 solutions: - {ref: solutions/hpe/hpe-server, score: 0.45} - {ref: solutions/hpe/hpe-server/hpe-synergy, score: 0.45} - {ref: solutions/ibm, score: 0.45} - {ref: solutions/ibm/ibm-power10, score: 0.45} alsoLike: - {ref: posts/vmware-data-services-manager, score: 0.45} - {ref: posts/vmware-cloud-on-aws, score: 0.45} - {ref: services/health-check, score: 0.41} experts: - {ref: experts/yannick-gerber, score: 0.35} - {ref: experts/aldo-gwerder, score: 0.32} - {ref: experts/marco-mattei, score: 0.31} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "it-architecture", "locale": "en", "labels": { "group": "consulting", "capability/architecture": 2.51, "capability/cloud": 1.92 }, "annotations": { "source": "src/content/services/en/it-architecture.md", "route": "/en/services/it-architecture/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/it-architecture.md" } }, "spec": { "title": "IT Architecture", "group": "consulting", "audience": [ "enterprise", "provider" ], "order": 3, "tags": [ "architecture", "cloud" ], "summary": "Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several.", "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 comes out of it

", "body": "A design for an infrastructure that matches your requirements and fits into the systems\nyou already run. Where it runs is open: on your site, in a co-location, in the public\ncloud, or spread across several of those." }, { "heading": "

How we get there

", "body": "In requirement workshops we capture the requirements and the constraints for the new\nplatform. The design follows from those, using a design method we have used for years.\n\nThe point of that method is not the shape of the document. It is that what comes out meets\nthe requirements of everyone involved, not only the technical ones. An architecture that\nworks technically and then fails on procurement, on operations or on data protection is not\nfinished being designed, only finished being drawn.\n\nThe design is vendor-independent. Requirements, constraints, assumptions and risks are\ndocumented in it, and a transformation plan says in which steps the existing estate becomes\nthe new one." }, { "heading": "

How this differs from Enterprise Architecture

", "body": "Enterprise architecture looks at the IT estate as a whole, including processes and the role\nIT plays in the business. IT architecture designs one concrete platform inside that.\n\nEither can be commissioned on its own. When they happen together the order gets easier:\nfirst the frame, then the platform that belongs in it." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-server", "score": "0.45" }, { "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.45" }, { "ref": "solutions/ibm", "score": "0.45" }, { "ref": "solutions/ibm/ibm-power10", "score": "0.45" } ], "alsoLike": [ { "ref": "posts/vmware-data-services-manager", "score": "0.45" }, { "ref": "posts/vmware-cloud-on-aws", "score": "0.45" }, { "ref": "services/health-check", "score": "0.41" } ], "experts": [ { "ref": "experts/yannick-gerber", "score": "0.35" }, { "ref": "experts/aldo-gwerder", "score": "0.32" }, { "ref": "experts/marco-mattei", "score": "0.31" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "it-architecture"locale = "en"[metadata.labels]group = "consulting""capability/architecture" = 2.51"capability/cloud" = 1.92[metadata.annotations]source = "src/content/services/en/it-architecture.md"route = "/en/services/it-architecture/"schema = "/nerd/schema/services.json"markdown = "/en/services/it-architecture.md"[spec]title = "IT Architecture"group = "consulting"audience = ["enterprise", "provider"]order = 3tags = ["architecture", "cloud"]summary = "Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several."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 comes out of it

"body = '''A design for an infrastructure that matches your requirements and fits into the systemsyou already run. Where it runs is open: on your site, in a co-location, in the publiccloud, or spread across several of those.'''[[spec.sections]]heading = "

How we get there

"body = '''In requirement workshops we capture the requirements and the constraints for the newplatform. The design follows from those, using a design method we have used for years.The point of that method is not the shape of the document. It is that what comes out meetsthe requirements of everyone involved, not only the technical ones. An architecture thatworks technically and then fails on procurement, on operations or on data protection is notfinished being designed, only finished being drawn.The design is vendor-independent. Requirements, constraints, assumptions and risks aredocumented in it, and a transformation plan says in which steps the existing estate becomesthe new one.'''[[spec.sections]]heading = "

How this differs from Enterprise Architecture

"body = '''Enterprise architecture looks at the IT estate as a whole, including processes and the roleIT plays in the business. IT architecture designs one concrete platform inside that.Either can be commissioned on its own. When they happen together the order gets easier:first the frame, then the platform that belongs in it.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/hpe/hpe-server"score = "0.45"[[status.solutions]]ref = "solutions/hpe/hpe-server/hpe-synergy"score = "0.45"[[status.solutions]]ref = "solutions/ibm"score = "0.45"[[status.solutions]]ref = "solutions/ibm/ibm-power10"score = "0.45"[[status.alsoLike]]ref = "posts/vmware-data-services-manager"score = "0.45"[[status.alsoLike]]ref = "posts/vmware-cloud-on-aws"score = "0.45"[[status.alsoLike]]ref = "services/health-check"score = "0.41"[[status.experts]]ref = "experts/yannick-gerber"score = "0.35"[[status.experts]]ref = "experts/aldo-gwerder"score = "0.32"[[status.experts]]ref = "experts/marco-mattei"score = "0.31"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>it-architecture</name> <locale>en</locale> <labels> <group>consulting</group> <entry key="capability/architecture">2.51</entry> <entry key="capability/cloud">1.92</entry> </labels> <annotations> <source>src/content/services/en/it-architecture.md</source> <route>/en/services/it-architecture/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/it-architecture.md</markdown> </annotations> </metadata> <spec> <title>IT Architecture</title> <group>consulting</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>3</order> <tags> <item>architecture</item> <item>cloud</item> </tags> <summary>Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several.</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 comes out of it

</heading> <body>A design for an infrastructure that matches your requirements and fits into the systemsyou already run. Where it runs is open: on your site, in a co-location, in the publiccloud, or spread across several of those. </body> </section> <section> <heading>

How we get there

</heading> <body>In requirement workshops we capture the requirements and the constraints for the newplatform. The design follows from those, using a design method we have used for years.The point of that method is not the shape of the document. It is that what comes out meetsthe requirements of everyone involved, not only the technical ones. An architecture thatworks technically and then fails on procurement, on operations or on data protection is notfinished being designed, only finished being drawn.The design is vendor-independent. Requirements, constraints, assumptions and risks aredocumented in it, and a transformation plan says in which steps the existing estate becomesthe new one. </body> </section> <section> <heading>

How this differs from Enterprise Architecture

</heading> <body>Enterprise architecture looks at the IT estate as a whole, including processes and the roleIT plays in the business. IT architecture designs one concrete platform inside that.Either can be commissioned on its own. When they happen together the order gets easier:first the frame, then the platform that belongs in it. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/hpe/hpe-server</ref> <score>0.45</score> </item> <item> <ref>solutions/hpe/hpe-server/hpe-synergy</ref> <score>0.45</score> </item> <item> <ref>solutions/ibm</ref> <score>0.45</score> </item> <item> <ref>solutions/ibm/ibm-power10</ref> <score>0.45</score> </item> </solutions> <alsoLike> <item> <ref>posts/vmware-data-services-manager</ref> <score>0.45</score> </item> <item> <ref>posts/vmware-cloud-on-aws</ref> <score>0.45</score> </item> <item> <ref>services/health-check</ref> <score>0.41</score> </item> </alsoLike> <experts> <item> <ref>experts/yannick-gerber</ref> <score>0.35</score> </item> <item> <ref>experts/aldo-gwerder</ref> <score>0.32</score> </item> <item> <ref>experts/marco-mattei</ref> <score>0.31</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": "it-architecture", "locale": "en", "labels": { "group": "consulting", "capability/architecture": 2.51, "capability/cloud": 1.92, }, "annotations": { "source": "src/content/services/en/it-architecture.md", "route": "/en/services/it-architecture/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/it-architecture.md", }, }, "spec": { "title": "IT Architecture", "group": "consulting", "audience": ["enterprise", "provider"], "order": 3, "tags": ["architecture", "cloud"], "summary": "Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several.", "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 comes out of it

", "body": ( "A design for an infrastructure that matches your requirements and fits into the systems\n" "you already run. Where it runs is open: on your site, in a co-location, in the public\n" "cloud, or spread across several of those." ), }, { "heading": "

How we get there

", "body": ( "In requirement workshops we capture the requirements and the constraints for the new\n" "platform. The design follows from those, using a design method we have used for years.\n" "\n" "The point of that method is not the shape of the document. It is that what comes out meets\n" "the requirements of everyone involved, not only the technical ones. An architecture that\n" "works technically and then fails on procurement, on operations or on data protection is not\n" "finished being designed, only finished being drawn.\n" "\n" "The design is vendor-independent. Requirements, constraints, assumptions and risks are\n" "documented in it, and a transformation plan says in which steps the existing estate becomes\n" "the new one." ), }, { "heading": "

How this differs from Enterprise Architecture

", "body": ( "Enterprise architecture looks at the IT estate as a whole, including processes and the role\n" "IT plays in the business. IT architecture designs one concrete platform inside that.\n" "\n" "Either can be commissioned on its own. When they happen together the order gets easier:\n" "first the frame, then the platform that belongs in it." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-server", "score": "0.45", }, { "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.45", }, { "ref": "solutions/ibm", "score": "0.45", }, { "ref": "solutions/ibm/ibm-power10", "score": "0.45", }, ], "alsoLike": [ { "ref": "posts/vmware-data-services-manager", "score": "0.45", }, { "ref": "posts/vmware-cloud-on-aws", "score": "0.45", }, { "ref": "services/health-check", "score": "0.41", }, ], "experts": [ { "ref": "experts/yannick-gerber", "score": "0.35", }, { "ref": "experts/aldo-gwerder", "score": "0.32", }, { "ref": "experts/marco-mattei", "score": "0.31", }, ], "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 = 'it-architecture' locale = 'en' labels = [ordered]@{ group = 'consulting' 'capability/architecture' = 2.51 'capability/cloud' = 1.92 } annotations = [ordered]@{ source = 'src/content/services/en/it-architecture.md' route = '/en/services/it-architecture/' schema = '/nerd/schema/services.json' markdown = '/en/services/it-architecture.md' } } spec = [ordered]@{ title = 'IT Architecture' group = 'consulting' audience = @('enterprise', 'provider') order = 3 tags = @('architecture', 'cloud') summary = 'Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several.' 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 comes out of it

' body = @'A design for an infrastructure that matches your requirements and fits into the systemsyou already run. Where it runs is open: on your site, in a co-location, in the publiccloud, or spread across several of those.'@ } [ordered]@{ heading = '

How we get there

' body = @'In requirement workshops we capture the requirements and the constraints for the newplatform. The design follows from those, using a design method we have used for years.The point of that method is not the shape of the document. It is that what comes out meetsthe requirements of everyone involved, not only the technical ones. An architecture thatworks technically and then fails on procurement, on operations or on data protection is notfinished being designed, only finished being drawn.The design is vendor-independent. Requirements, constraints, assumptions and risks aredocumented in it, and a transformation plan says in which steps the existing estate becomesthe new one.'@ } [ordered]@{ heading = '

How this differs from Enterprise Architecture

' body = @'Enterprise architecture looks at the IT estate as a whole, including processes and the roleIT plays in the business. IT architecture designs one concrete platform inside that.Either can be commissioned on its own. When they happen together the order gets easier:first the frame, then the platform that belongs in it.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/hpe/hpe-server' score = '0.45' } [ordered]@{ ref = 'solutions/hpe/hpe-server/hpe-synergy' score = '0.45' } [ordered]@{ ref = 'solutions/ibm' score = '0.45' } [ordered]@{ ref = 'solutions/ibm/ibm-power10' score = '0.45' } ) alsoLike = @( [ordered]@{ ref = 'posts/vmware-data-services-manager' score = '0.45' } [ordered]@{ ref = 'posts/vmware-cloud-on-aws' score = '0.45' } [ordered]@{ ref = 'services/health-check' score = '0.41' } ) experts = @( [ordered]@{ ref = 'experts/yannick-gerber' score = '0.35' } [ordered]@{ ref = 'experts/aldo-gwerder' score = '0.32' } [ordered]@{ ref = 'experts/marco-mattei' score = '0.31' } ) 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": "it-architecture", "locale": "en", "labels": map[string]any{ "group": "consulting", "capability/architecture": 2.51, "capability/cloud": 1.92, }, "annotations": map[string]any{ "source": "src/content/services/en/it-architecture.md", "route": "/en/services/it-architecture/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/it-architecture.md", }, }, "spec": map[string]any{ "title": "IT Architecture", "group": "consulting", "audience": []any{"enterprise", "provider"}, "order": 3, "tags": []any{"architecture", "cloud"}, "summary": "Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several.", "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 comes out of it

", "body": "A design for an infrastructure that matches your requirements and fits into the systems\n" + "you already run. Where it runs is open: on your site, in a co-location, in the public\n" + "cloud, or spread across several of those.", }, map[string]any{ "heading": "

How we get there

", "body": "In requirement workshops we capture the requirements and the constraints for the new\n" + "platform. The design follows from those, using a design method we have used for years.\n" + "\n" + "The point of that method is not the shape of the document. It is that what comes out meets\n" + "the requirements of everyone involved, not only the technical ones. An architecture that\n" + "works technically and then fails on procurement, on operations or on data protection is not\n" + "finished being designed, only finished being drawn.\n" + "\n" + "The design is vendor-independent. Requirements, constraints, assumptions and risks are\n" + "documented in it, and a transformation plan says in which steps the existing estate becomes\n" + "the new one.", }, map[string]any{ "heading": "

How this differs from Enterprise Architecture

", "body": "Enterprise architecture looks at the IT estate as a whole, including processes and the role\n" + "IT plays in the business. IT architecture designs one concrete platform inside that.\n" + "\n" + "Either can be commissioned on its own. When they happen together the order gets easier:\n" + "first the frame, then the platform that belongs in it.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/hpe/hpe-server", "score": "0.45", }, map[string]any{ "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.45", }, map[string]any{ "ref": "solutions/ibm", "score": "0.45", }, map[string]any{ "ref": "solutions/ibm/ibm-power10", "score": "0.45", }, }, "alsoLike": []any{ map[string]any{ "ref": "posts/vmware-data-services-manager", "score": "0.45", }, map[string]any{ "ref": "posts/vmware-cloud-on-aws", "score": "0.45", }, map[string]any{ "ref": "services/health-check", "score": "0.41", }, }, "experts": []any{ map[string]any{ "ref": "experts/yannick-gerber", "score": "0.35", }, map[string]any{ "ref": "experts/aldo-gwerder", "score": "0.32", }, map[string]any{ "ref": "experts/marco-mattei", "score": "0.31", }, }, "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: "it-architecture", locale: "en", labels: { group: "consulting", "capability/architecture": 2.51, "capability/cloud": 1.92, }, annotations: { source: "src/content/services/en/it-architecture.md", route: "/en/services/it-architecture/", schema: "/nerd/schema/services.json", markdown: "/en/services/it-architecture.md", }, }, spec: { title: "IT Architecture", group: "consulting", audience: ["enterprise", "provider"], order: 3, tags: ["architecture", "cloud"], summary: "Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several.", 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 comes out of it

", body: "A design for an infrastructure that matches your requirements and fits into the systems\n" + "you already run. Where it runs is open: on your site, in a co-location, in the public\n" + "cloud, or spread across several of those.", }, { heading: "

How we get there

", body: "In requirement workshops we capture the requirements and the constraints for the new\n" + "platform. The design follows from those, using a design method we have used for years.\n" + "\n" + "The point of that method is not the shape of the document. It is that what comes out meets\n" + "the requirements of everyone involved, not only the technical ones. An architecture that\n" + "works technically and then fails on procurement, on operations or on data protection is not\n" + "finished being designed, only finished being drawn.\n" + "\n" + "The design is vendor-independent. Requirements, constraints, assumptions and risks are\n" + "documented in it, and a transformation plan says in which steps the existing estate becomes\n" + "the new one.", }, { heading: "

How this differs from Enterprise Architecture

", body: "Enterprise architecture looks at the IT estate as a whole, including processes and the role\n" + "IT plays in the business. IT architecture designs one concrete platform inside that.\n" + "\n" + "Either can be commissioned on its own. When they happen together the order gets easier:\n" + "first the frame, then the platform that belongs in it.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/hpe/hpe-server", score: "0.45", }, { ref: "solutions/hpe/hpe-server/hpe-synergy", score: "0.45", }, { ref: "solutions/ibm", score: "0.45", }, { ref: "solutions/ibm/ibm-power10", score: "0.45", }, ], alsoLike: [ { ref: "posts/vmware-data-services-manager", score: "0.45", }, { ref: "posts/vmware-cloud-on-aws", score: "0.45", }, { ref: "services/health-check", score: "0.41", }, ], experts: [ { ref: "experts/yannick-gerber", score: "0.35", }, { ref: "experts/aldo-gwerder", score: "0.32", }, { ref: "experts/marco-mattei", score: "0.31", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 70 lines · YAML · validated at build# 100 lines · JSON · validated at build# 106 lines · TOML · validated at build# 122 lines · XML · validated at build# 122 lines · Python · read back at build, equals the JSON record# 119 lines · PowerShell · read back at build, equals the JSON record# 128 lines · Go · read back at build, equals the JSON record# 113 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/it-architecture.md

Service · consulting

IT Architecture

Turning requirements and constraints into an infrastructure design that fits the estate you already have. On site, in a co-location, in the cloud, or across several.

Topics Architecture 2.51 Cloud 1.92

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 comes out of it

A design for an infrastructure that matches your requirements and fits into the systems you already run. Where it runs is open: on your site, in a co-location, in the public cloud, or spread across several of those.

How we get there

In requirement workshops we capture the requirements and the constraints for the new platform. The design follows from those, using a design method we have used for years.

The point of that method is not the shape of the document. It is that what comes out meets the requirements of everyone involved, not only the technical ones. An architecture that works technically and then fails on procurement, on operations or on data protection is not finished being designed, only finished being drawn.

The design is vendor-independent. Requirements, constraints, assumptions and risks are documented in it, and a transformation plan says in which steps the existing estate becomes the new one.

How this differs from Enterprise Architecture

Enterprise architecture looks at the IT estate as a whole, including processes and the role IT plays in the business. IT architecture designs one concrete platform inside that.

Either can be commissioned on its own. When they happen together the order gets easier: first the frame, then the platform that belongs in it.