Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-8346

Forecast Import Baseline with current file

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Sprint:
      CFAMX 2020R2 Sprint 4
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      2
    • Work Type Classification:
      Sustaining

      Description

      We import forecasts form Chick-fil-A on a daily basis.

      • A part of the forecast import, is to provide a Service Type, today all records in the files provided to us have Service Type of 3, which represents Inside Sales.
      • During December there was an issue identified where the Last Years Sales were not being displayed for Outside sales.
        • The reason for this is that when a Forecast is Import, we do not gather any historical data for the generation of the System Forecast. We do however gather the data for any future Outside Sales (deferred orders) that have been placed for the day for which the forecast is being generated
      • To resolve this issue, of no Last Year Sales for Outside sales, CFA are going to enhance their forecast generation process to also include Last Years Sales data for Outside Sales
      • The forecast import supports including multiple service types within the same file, we have successfully processed sample files provided by CFA that include a second Service Type
        • My anecdotal evidence is that the file size doubled when CFA added this second Service Type
      • This feature is to:
        • Measure the perf when processing the current files
        • Create sample files that contain a second service type
        • Measure the perf when processing the new files

      Step 1 of this feature:

      1. Work with Corey Amend to get his dummy endpoint populated with forecasts using service type 3, for 2,000 stores
      2. Process all of these forecasts, and measure/time the performance of the Forecast Import process

      Step 2:

      1. Work with Corey Amend to update the files in his dummy endpoint, to represent both Service Type 3 (inside) and Service Type 2 (outside)

      Step 3:

      1. Process all of these new forecasts (with records for service type 2 & 3), and measure/time the performance of the Forecast Import process

        Attachments

          Issue Links

          1.
          Review Test Scripts QA Task Done Unassigned

          100%

          Original Estimate - 0.5h Original Estimate - 0.5h
          Time Spent - 1h
          2.
          Deploy QA Task Done Unassigned

          100%

          Original Estimate - 0.5h
          Time Spent - 1m Time Not Required
          3.
          Functional Review with QA Dev Task Done Unassigned

          100%

          Original Estimate - 0.5h
          Time Spent - 1m Time Not Required
          4.
          DIT Dev Task Done Unassigned

          100%

          Original Estimate - 0.5h
          Time Spent - 1m Time Not Required

            Activity

              People

              • Assignee:
                will.englefield Will Englefield (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2h Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 6.05h
                  6.05h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.