AWS prescriptive-guidance documentation change
Summary
Updated documentation structure, formatting, and terminology related to IIoT blueprint architecture. Changes include navigation link fixes, emphasis on 'blueprint' and 'North Star vision' through italics, image path updates, bold formatting for architectural layer headings, and minor grammatical improvements.
Security assessment
The changes are primarily editorial improvements and formatting adjustments. While the 'Cross-cutting considerations' section mentions security requirements, this was already present in the original text. No new security vulnerabilities, mitigations, or security feature documentation were added.
Diff
diff --git a/prescriptive-guidance/latest/strategy-iiot-transformation/phase-3.md b/prescriptive-guidance/latest/strategy-iiot-transformation/phase-3.md index 35749b87c..8597c59aa 100644 --- a//prescriptive-guidance/latest/strategy-iiot-transformation/phase-3.md +++ b//prescriptive-guidance/latest/strategy-iiot-transformation/phase-3.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Building an industrial Internet of Things (IIoT) digital transformation strategy](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Building an industrial Internet of Things (IIoT) digital transformation strategy](introduction.html) @@ -7 +7 @@ -North Star visionCore tenets of successBuilding blocksAWS IDP solution offering +North Star visionCore tenets of a successful solution frameworkRepeatable and reusable building blocksAWS IDP solution offering @@ -11 +11 @@ North Star visionCore tenets of successBuilding blocksAWS IDP solution offering -Based on the evaluation of your current state in the previous phase, you can start building your blueprint. A blueprint is an end-to-end IIoT system reference architecture you adopt on your digital transformation journey. It serves as the foundation of your IIoT digitalization journey and helps you realize your business objectives. A blueprint: +Based on the evaluation of your current state in the previous phase, you can start building your blueprint. A _blueprint_ is an end-to-end IIoT system reference architecture you adopt on your digital transformation journey. It serves as the foundation of your IIoT digitalization journey and helps you realize your business objectives. A blueprint: @@ -26 +26 @@ Sometimes, you might need a quick proof of concept to demonstrate value and feas -Your blueprint should be guided by your North Star vision, which is a clear, concise, and long-term goal that provides direction for making business decisions. If you don’t have a North Star vision, think big when creating one. This vision generally takes 3–5 years to realize. To achieve this vision, starting small and scaling fast are the keys to success. +Your blueprint should be guided by your _North Star vision_ , which is a clear, concise, and long-term goal that provides direction for making business decisions. If you don't have a North Star vision, think big when creating one. This vision generally takes 3–5 years to realize. To achieve this vision, starting small and scaling fast are the keys to success. @@ -30 +30 @@ Your blueprint should be guided by your North Star vision, which is a clear, con -To create a unified IT and OT data backbone in your blueprint, you need a functional architecture. Based on our experiences, we’ve identified the following three core tenets of the solution framework: +To create a unified IT and OT data backbone in your blueprint, you need a functional architecture. Based on our experiences, we've identified the following three core tenets of the solution framework: @@ -73 +73 @@ The _building blocks_ of an IIoT digital transformation journey are the various - + @@ -77 +77 @@ The following are the layers of a blueprint: - * Data ingestion – This edge layer collects data from various sources in your on-premises infrastructure or cloud environment. Typical IT/OT data sources might include telemetry data from supervisory control and data acquisition (SCADA) systems, distributed control systems (DCS), PLCs, secondary sensors, manufacturing execution systems (MES), software as a service (SaaS) and legacy applications, enterprise resource planning (ERP) systems, customer relationship management (CRM) systems, various supply chain systems, and data historians. + * **Data ingestion** – This edge layer collects data from various sources in your on-premises infrastructure or cloud environment. Typical IT/OT data sources might include telemetry data from supervisory control and data acquisition (SCADA) systems, distributed control systems (DCS), PLCs, secondary sensors, manufacturing execution systems (MES), software as a service (SaaS) and legacy applications, enterprise resource planning (ERP) systems, customer relationship management (CRM) systems, various supply chain systems, and data historians. @@ -79 +79 @@ The following are the layers of a blueprint: - * Edge insights and applications – Depending on your use cases, you might want to deploy this edge layer. This layer is used to address any low latency and data residency requirements for your architecture, support production continuation when disconnected from the cloud, and enable innovation at the edge. + * **Edge insights and applications** – Depending on your use cases, you might want to deploy this edge layer. This layer is used to address any low latency and data residency requirements for your architecture, support production continuation when disconnected from the cloud, and enable innovation at the edge. @@ -81 +81 @@ The following are the layers of a blueprint: - * Data management – This layer is responsible for various aspects of typical data management functions, such as: + * **Data management** – This layer is responsible for various aspects of typical data management functions, such as: @@ -91 +91 @@ The following are the layers of a blueprint: - * Data insights – This cloud layer is used for business insights that range from simple, such as near real-time KPI dashboards, to advanced, such as predictive maintenance, demand forecasting, and inventory management that uses the flexible data consumption service from the data management layer. + * **Data insights** – This cloud layer is used for business insights that range from simple, such as near real-time KPI dashboards, to advanced, such as predictive maintenance, demand forecasting, and inventory management that uses the flexible data consumption service from the data management layer. @@ -93 +93 @@ The following are the layers of a blueprint: - * Data serving – This cloud layer is used to democratize access to the data for various end users, such as various OT personas, data scientists, data engineers, and data analysts. This layer seamlessly serves data to other enterprise systems and third-party solutions to enable use cases and business applications. + * **Data serving** – This cloud layer is used to democratize access to the data for various end users, such as various OT personas, data scientists, data engineers, and data analysts. This layer seamlessly serves data to other enterprise systems and third-party solutions to enable use cases and business applications. @@ -95 +95 @@ The following are the layers of a blueprint: - * Use cases and business applications – This is the top layer of the architecture. This cloud layer contains the business applications and tools that address your business use cases. As needed, the applications and tools in this layer access the data and insights in the supporting layers. + * **Use cases and business applications** – This is the top layer of the architecture. This cloud layer contains the business applications and tools that address your business use cases. As needed, the applications and tools in this layer access the data and insights in the supporting layers. @@ -97 +97 @@ The following are the layers of a blueprint: - * Cross-cutting considerations – This layer contains key non-functional requirements that apply to the data sources, edge, and cloud. This layer includes must-have elements, such as end-to-end security, configuration management, logging, compliance, and regulatory requirements. This layer helps you securely and efficiently operate your architecture, providing opportunities to enhance performance, reduce costs, or use automations that enable rapid deployment at scale across sites. + * **Cross-cutting considerations** – This layer contains key non-functional requirements that apply to the data sources, edge, and cloud. This layer includes must-have elements, such as end-to-end security, configuration management, logging, compliance, and regulatory requirements. This layer helps you securely and efficiently operate your architecture, providing opportunities to enhance performance, reduce costs, or use automations that enable rapid deployment at scale across sites. @@ -106 +106 @@ To create this unified data solution, we recommend using a unified functional ar -AWS Professional Services uses a tried-and-tested approach, AWS Industrial Data Platform (IDP), to discover, design, and implement a flexible and extensible unified data solution for Industry 4.0 (also known as smart manufacturing, smart factory, or smart industrial) success. The AWS IDP addresses a catalog of common use cases, such as: +AWS Professional Services uses a tried-and-tested approach, AWS Industrial Data Platform (IDP), to discover, design, and implement a flexible and extensible unified data solution for Industry 4.0 (also known as _smart manufacturing_ ,_smart factory_ , or _smart industrial_) success. The AWS IDP addresses a catalog of common use cases, such as: