Flush requirement

[awangatsanjel]

According to meeting memo of "Cut Size and Flushing Meeting Minutes" on Aug 1, 2024.

Flush

-  All direction should come from the server
- What will require a flush
  - Red job under 10T
  - Any Black Job
  - Certain extra sensitive blends
  - If the previous blend through meets a certain criteria (high levels of accelerators, etc.)
- Would like to see a new class of material come out “PF” that the server would automatically add based on the requirements.
  - BPAVS would prioritize the flush to be the first “cut”
    - All values would be reported to eSO for additional reporting/BI
- Adam would like to just send a flag to trigger a “standard flush”
  - 500kg of flyash or sil flour
  - BPAVS could handle this in the same way and stack a cut up before the rest of the actual blending happens.
- Urgency, what is our timeline?
  - Leadership expects this to be completed within 2024.
  - Adam is heading off on holidays, Neville is fully occupied.
  - Earliest development would be approximately start of September
- Colin
  - Treating a flush like a cut 1
      - How would these show up in BI?
        - Would show in BI as a separate “PF” cut for that product haul
  - Would not want a the flush chem to show up as part of the overall tolerance for the blend.
    - Anything that is part of a “PF” stage/cut would be filtered out of the blend accuracy for the rest of the blend, if they were using the same product to flush that is also in the blend, the chem in the blend would not be over reported.

Flush Rules by Colin

As discussed in the meeting yesterday, here are the initial rules we are proposing for a plant flush

IF

the current blend is:

1. Any Black Job
2. Any Red Job and the cut size is less than 10 tonne
3. Visweep DMIS
4. EVERcrete
5. Ciment Fondu

AND

The previous blend was one of the following:

1. ECOlite 1325
2. ECOlite 1400
3. LCS 1820
4. Expandomix
5. SURFACEmix LW PRO
6. THERMAmix THX
7. SURFACEmix PRO

We must flush the plant with 0.5 tonne of flour (if flour not available then flyash)

These rules may evolve by the time we are ready for implementation. Currently, with this criteria we would have completed 53 plant flushes in 2024 to date. (45 of which would be DMIS)

[awangatsanjel]

Architect Notes.

1. We will need a list of flush requirement, so we can build up a ruleset to manage it.
2. Blend Chemical should have a flag "NeedFlush".
   • In master data, there may be some blends need flush all the time.
     3. Blend Request should have a flag "NeedFlush". This flag is set when blend request is created. It will rely on the ruleset defined in No.1.
     4. Bulk Plant API needs update to expose the predetermined "NeedFlush" flag to BPAVS.
     5. Will need to talk to EOS team for the solution of previous blend.

[JasonSchneider19]

@awangatsanjel Colin agrees with the above statements

[awangatsanjel]

@lukeyang1972 @belazh @censinli 请进行一下预估

[zhangyuan5]

@awangatsanjel 需求理解：结合上下文，在Online系统中，创建BlendReqest时候并不知道哪些BaseBlend数据需要NeedFlush，因此需求定义了

1. Any Black Job
2. Any Red Job and the cut size is less than:
3. 10 tonne
4. Visweep DMIS
5. EVERcrete
6. Ciment Fondu and
7. ECOlite 1325
8. ECOlite 1400
9. LCS 1820
10. Expandomix
11. SURFACEmix LW PRO
12. THERMAmix THX
13. SURFACEmix PRO 这些[BlendRecipe]类型的配方在Chemical 中需要标志出NeedFlush，以便于在在创建BlendReqest时候知道是否需要NeedFlush， 同时对提供的Bulk Plant API 中访问到NeedFlush 任务评估： 1,SanjelData. Blend Chemical和SanjelData. [ProductHaulLoad] 增加 NeedFlush.Blend Chemical 代码中以增加 2.增加引用实体FlushRules,建立起[BlendRecipe]和需要标注NeedFlush的字段，从而区分出哪些Blend是NeedFlush的，在SanjelLibary中增加对Chemical .NeedFlush的逻辑处理，或者不通过实体，直接后台代码增加创建BlendRequest 的逻辑实现。10H 3.BlendRequest可能需要显示一个只读的属性，方便操作人员知道是否需要NeedFlush（create blend request ，ProductHau，reschedule ProductHau）。6H 4.Bulk Plant API涉及的获取Blend Chemical 接口和BlendRequest 的接口，提供NeedFlush属性的访问。4H

[awangatsanjel]

@zhangyuan5

NeedFlush是需要在创建BlendRequest来预决定的，并根据BPAVS提交的数据来最终决定是否需要Flush。在你的分析中没有对涉及的业务逻辑概念提出问题。如什么是Black Job/Red Job? 规则的逻辑关系是什么？所以有些问题中涉及的实体识别错误。你没有仔细读我写的Architect Notes。

• [x] SanjelData. Blend Chemical 增加 NeedFlush. Only Visweep DMIS, EVERcrete, Ciment Fondu are set true as above rules
• [x] SanjelData. ProductHaulLoad 增加 NeedFlush.Blend Chemical 代码中以增加
• [x] 增加静态代码实体FlushRule，字段包括，MinRiskMatrix, MaxRiskMatrix,MinCutSize,MaxCutSize, PreviousBlendChemical 序列化Rule 1 and 2, and the previous blend rules as data. 这个实体待以后验证可行性后再加入到SanjelData，本次项目暂不实现
• [x] 修改eServiceOnline中创建、修改Blend Request（ProductHaulLoad)的逻辑，根据规则确定NeedFlush的值。在这个逻辑中，PreviousBlendChemical是未知的。本着严格的原则，只检查RiskMatrix和CutSize（BlendRequest.TotalTonnage）
• [x] 修改BPVAS API，在获取BlendRequest列表方法中，返回值中增加NeedFlush的标签。
• [x] 修改BPVAS API，在获取单一BlendRequest方法中，根据已完成的最后一个BlendRequest的数据，重新评估NeedFlush的值，返回值中增加NeedFlush的标签。

在以上解决方案中，未解决如何触发Flush，Flush所用材料如何处理，如何入账等问题。需要与Logistics和EOS团队协商，如果功能展再分析和识别开发任务。

cc @lukeyang1972 @censinli

你们理解一下看是否有问题。没有问题可以进行开发。

[awangatsanjel]

@zhangyuan5 任务5，6已经完成。你不需要再做了

cc @censinli