AWS aws-supply-chain documentation change
Summary
Restructured onboarding documentation with detailed steps for creating demand plans, added data validation/analysis phases, and updated configuration workflow
Security assessment
Added reference to role-based access control documentation ([Role-based access control](./rolebased.html)) in step 3, indicating security awareness. However, no concrete evidence of addressing a specific vulnerability or security incident. The primary focus is workflow improvements and data quality enforcement.
Diff
diff --git a/aws-supply-chain/latest/userguide/onboarding.md b/aws-supply-chain/latest/userguide/onboarding.md index 8aaa6cbbe..db589e8e5 100644 --- a//aws-supply-chain/latest/userguide/onboarding.md +++ b//aws-supply-chain/latest/userguide/onboarding.md @@ -5 +5 @@ -# First time configuration of Demand Plan +# Create your first demand plan @@ -7 +7 @@ -You can create demand plans to forecast your inventory demand accurately across your organization. +When you log into Demand Planning for the first time, you will be able to view the onboarding pages that highlight key product features and help you get familiar with the Demand Planning capabilities. @@ -9 +9 @@ You can create demand plans to forecast your inventory demand accurately across -###### Note +**Overview of the process:** @@ -11 +11 @@ You can create demand plans to forecast your inventory demand accurately across -When you log into Demand Planning for the first time, you'll be able to view the onboarding pages that highlight the key features. This helps you to get familiar with the Demand Planning capabilities. Once Demand Planning is configured, you can view or modify the demand plan configuration settings under _Settings > Organization > Demand Planning_. +To create your first forecast, from the left navigation bar, choose **Demand Planning** , **Manage Demand Plan** , and **Create forecast**. The system guides you through the following steps. For more information, see [Role-based access control](./rolebased.html). @@ -13 +13,9 @@ When you log into Demand Planning for the first time, you'll be able to view the -###### Note + 1. _Data ingestion_ – Before proceeding with configuration, the system verifies that required datasets are ingested into Data Lake. You need the following, at minimum. For more information about which table and columns are used by Demand Planning, including prerequisites, see [Demand Planning](./required_entities.html). + + * Required: Outbound Order Line and Product data + + * Recommended: Product Alternate and Supplementary Time Series data + + 2. _Plan configuration_ – After data ingestion is complete, you'll configure various aspects of your demand plan, including forecast dimensions, time frames, settings, and scheduling options. After Demand Planning is configured, you can view or modify the demand plan configuration settings by choosing **Settings** , **Organization** , and **Demand Planning**. + + 3. _Plan creation_ – After configuration, choosing **Generate Forecast** initiates three sub-processes: @@ -15 +23 @@ When you log into Demand Planning for the first time, you'll be able to view the -Overrides are not allowed on the locked forecast periods. For more information, see [Forecast lock](./forecast_lock.html). + * Data Validation: System validates data quality and completeness @@ -17 +25 @@ Overrides are not allowed on the locked forecast periods. For more information, -The Enterprise Demand Plan is derived from single forecast configuration settings. Make sure that someone in your organization has used the following steps to complete the forecast configuration settings. If they have already been set up by someone else in your organization, then you won't need to complete these steps. Instead, you will be directed to the **Demand Planning** page where you can start reviewing the forecast. + * Demand Pattern Analysis & Recommendations: System analyzes historical patterns and provides insights @@ -19 +27 @@ The Enterprise Demand Plan is derived from single forecast configuration setting - 1. Open the AWS Supply Chain web application. + * Forecast Creation: System generates the forecast @@ -21 +28,0 @@ The Enterprise Demand Plan is derived from single forecast configuration setting - 2. In the left navigation pane on the AWS Supply Chain dashboard, choose **Demand Planning**. @@ -23 +29,0 @@ The Enterprise Demand Plan is derived from single forecast configuration setting - 3. On the **Demand Planning** page, choose **Next**. @@ -25 +30,0 @@ The Enterprise Demand Plan is derived from single forecast configuration setting -You can read through to understand what Demand Planning offers, or choose **Next** until you get to the **Configure Demand Planning** page. @@ -27 +32,3 @@ You can read through to understand what Demand Planning offers, or choose **Next - 4. On the **Configure Demand Planning** page, there are five steps to configure Demand Planning. +In an ideal scenario, where no data validation errors are found, the system smoothly proceeds through all three steps, creating both the demand pattern analysis report and forecast. However, if any data validation errors are detected, the system halts both the forecast creation and demand pattern analysis until the errors are resolved. Work with your data administrator to correct the underlying data issues, and choose **Retry** to try forecast creation again. + + 1. On the **Configure Demand Planning** page, there are five steps to configure Demand Planning. @@ -39 +46 @@ You can read through to understand what Demand Planning offers, or choose **Next - 5. Under **Scope** , **Planning Horizon** , select the following: + 2. Under **Scope** , **Planning Horizon** , select the following: @@ -57 +64 @@ Make sure that the required hierarchy attributes have information in the product - 6. Choose **Continue**. + 3. Choose **Continue**. @@ -59 +66 @@ Make sure that the required hierarchy attributes have information in the product - 7. On the **Configure your dataset** page, under **Configure Forecast Input** , you should configure the required and recommended datasets. + 4. On the **Configure your dataset** page, under **Configure Forecast Input** , you should configure the required and recommended datasets. @@ -69 +76 @@ AWS Supply Chain recommends uploading two to three years of outbound order line - 8. Under **Required Datasets** , expand **Historical Demand** and choose **Configure** to set the negative value for missing data. _outbound_order_line_ dataset is the primary source of historical demand. + 5. Under **Required Datasets** , expand **Historical Demand** and choose **Configure** to set the negative value for missing data. _outbound_order_line_ dataset is the primary source of historical demand. @@ -75 +82 @@ AWS Supply Chain recommends uploading two to three years of outbound order line - 9. No additional configuration is required for _product_ data entity. Product attributes are used for filters, configure hierarchy, and for training the learning model. + 6. No additional configuration is required for _product_ data entity. Product attributes are used for filters, configure hierarchy, and for training the learning model. @@ -77 +84 @@ AWS Supply Chain recommends uploading two to three years of outbound order line - 10. Under **Recommended Datasets** , no additional configuration is required for _product_lineage_. You can use the _product_alternate_ data entity to provide information on alternate or previous version of the product. For more information on product lineage, see [Product lineage](./product_lineage.html). + 7. Under **Recommended Datasets** , no additional configuration is required for _product_lineage_. You can use the _product_alternate_ data entity to provide information on alternate or previous version of the product. For more information on product lineage, see [Product lineage](./product_lineage.html). @@ -79 +86 @@ AWS Supply Chain recommends uploading two to three years of outbound order line - 11. Select **Demand Drivers** if you have demand drivers information such as promotions, price changes, and so on, you can use _supplementary_time_series_ data entity to ingest data. You can select up to 13 demand drivers and configure aggregation and missing data filling strategy. For more information on demand drivers, see [Forecast based on demand drivers](./demand_drivers.html). + 8. Select **Demand Drivers** if you have demand drivers information such as promotions, price changes, and so on, you can use _supplementary_time_series_ data entity to ingest data. You can select up to 13 demand drivers and configure aggregation and missing data filling strategy. For more information on demand drivers, see [Forecast based on demand drivers](./demand_drivers.html). @@ -81 +88 @@ AWS Supply Chain recommends uploading two to three years of outbound order line - 12. Choose **Continue**. + 9. Choose **Continue**. @@ -83 +90 @@ AWS Supply Chain recommends uploading two to three years of outbound order line - 13. On the **Forecast Settings** page, you need to configure the following: + 10. On the **Forecast Settings** page, you need to configure the following: @@ -153 +160 @@ When the last order date falls within the time boundary, Demand Planning will tr - 14. Choose **Continue**. + 11. Choose **Continue**. @@ -155 +162 @@ When the last order date falls within the time boundary, Demand Planning will tr - 15. On the **Demand Plan Publish Scheduler** page, under **How do you like to manage ongoing forecast refresh and demand plan release?** , choose **Auto** to view your next forecast plan published on the Demand Planning page. + 12. On the **Demand Plan Publish Scheduler** page, under **How do you like to manage ongoing forecast refresh and demand plan release?** , choose **Auto** to view your next forecast plan published on the Demand Planning page. @@ -161 +168 @@ Under **Set the release frequency for the final demand plan** , choose the frequ - 16. Choose **Continue**. + 13. Choose **Continue**. @@ -163 +170 @@ Under **Set the release frequency for the final demand plan** , choose the frequ - 17. Under **Organization Settings** , note the Amazon Simple Storage Service (Amazon S3) path where the demand plans are published. + 14. Under **Organization Settings** , note the Amazon Simple Storage Service (Amazon S3) path where the demand plans are published. @@ -169,6 +175,0 @@ You can also find the Amazon S3 path for the published demand plans on the **Set - 18. Choose **Complete**. - -The **Enterprise Demand Plan** page appears. To start using Demand Planning, choose **Create Forecast**. - -###### Note - @@ -180,2 +180,0 @@ Forecast is generated only when you ingest data into AWS Supply Chain. Make sure -After you set the forecast settings, you can generate the forecast and demand plan for the time horizon that you set. On the **Enterprise Demand Plan** page, choose **Create Forecast**. - @@ -190 +189 @@ Terminology used in Demand Planning -Forecast Algorithms +Data Validation and Demand Pattern Analysis