Blend Request Scenarios - Sanjel-Energy-Services/eService_WorkItems GitHub Wiki

Scenarios-场景

1. Schedule blend haul to a bin attached to a rig for a job (Has call sheet)

  • Existing Rig Board function

2. Schedule blend haul to a job go with crew (Has call sheet)

  • Existing Rig Board function

3. Schedule a blend for a job and load to a bin attached to bulk plant awaiting blend test (Has call sheet)

  • Need to number silos/bins in Bulk Plant
  • Treat Bulk Plant as Rig, the silos and bins can be attached to Bulk Plant
  • Need blend database to store the blend information

4. Schedule a haul to transfer pre-blended blend to a bin attached to a rig for a job (Has call sheet)

  • Need blend database to store the blend information associated to the call sheet.
  • Select bulker (Sanjel or 3rd Party)
  • Scenario 1 is one step of Scenario 3 and 4
  • Mock S4-1, All blend in test are listed under one second level sub menu, third level sub menu show passed blend as enabled, still testing blend as disabled.
    • Before we have functions to update test status, all blends are enabled. Dispatch manage them manually.

5. Schedule a haul to transfer pre-blended blend to go with crew (Has call sheet)

  • Need blend database to store the blend information associated to the call sheet.
  • Select bulker (Sanjel or 3rd Party)
  • Scenario 2 is one step of Scenario 3 and 5
  • Mock S4-1 support this scenario

6. Schedule a blend haul for a project to a storage attached to a rig (No call sheet)

  • Need program to provide recipe
  • Or blend database is needed for storing recipe
  • Combination of Scenario 7 and Scenario 15, mechanism is similar to Scenario 1

7. Schedule a blend and transfer to a bin attached to bulk plant (No call sheet)

  • Need to number silos/bins in Bulk Plant
  • Treat Bulk Plant as Rig, the silos and bins can be attached to Bulk Plant
  • Need program

workaround- 8. Schedule a blend for product sale with customer's recipe and haul to customer's location (Has call sheet)

  • Need customer's recipe is entered in program and call sheet is created from the program.
  • Select bulker (Sanjel or 3rd Party)
  • Free-text loading destination (Location)
  • Call Sheet doesn't have a rig, need to create a fake rig for customer. Then the process will be same as job blend haul.
  • May need break down to blend and haul two steps

workaround- 9. Schedule a blend for product sale with customer's recipe and load to customer's bulker (Has call sheet)

  • Need customer's recipe is entered in program and call sheet is created from the program.
  • Free-text destination (Bulker) , add customer bulker as third party bulker
  • Call Sheet doesn't have a rig, need to create a fake rig for customer. Then the process will be same as job blend haul.

workaround-10. Schedule a blend for product sale with Sanjel blend recipe and haul to customer's location (Has call sheet)

  • Need program and call sheet is created from the program
  • Select bulker (Sanjel or 3rd Party),add customer bulker as third party bulker
  • Call Sheet doesn't have a rig
  • May need break down to blend and haul two steps

workaround-11. Schedule a blend for product sale with Sanjel blend recipe and load to customer's bulker (Has call sheet)

  • Need program and call sheet is created from the program
  • Free-text loading destination (Bulker)
  • Call Sheet doesn't have a rig
  • May need break down to blend and haul two steps upon customer request sample testing

workaround-12. Schedule a neat blend for product sale and haul to customer's location (Has call sheet)

  • Need program and call sheet is created from the program
  • Call Sheet doesn't have a rig
  • This may be treated as same as 10, no blending process will be handled by BPAVS

workaround-13. Schedule a neat blend for product sale and load to customer's bulker (Has call sheet)

  • Need program and call sheet is created from the program

  • Call Sheet doesn't have a rig

  • This may be treated as same as 10, no blending process will be handled by BPAVS

Not in scope - 14. Schedule a blend by using a previous blend to modify into a new blend. (Has call sheet, may apply to 1, 2,3,10,11)

  • Need blend database to storing the historical blend records also for the returned blend.
  • Need blend calculator upgrade

15. Schedule a haul for blended product from one location to another (Bulk Plant storage or Project storage or Rig storage) (No call sheet)

  • Need to number silos/bins in Bulk Plant
  • Need blend database to storing the historical blend records also for the returned blend.
  • Need blend information for the content stored in a bin/silo.
  • Same function as Scenario 4, but start points may be different

Not in scope - 16. Schedule a product transfer from one Bulk Plant to another (No call sheet)

  • Similar to scenario 15, but for inventory product only.

Not in scope - 17. Return Cement from job into storage attached to bulk plant (Refer to Call Sheet)

  • Need to number silos/bins in Bulk Plant
  • Current process use original MTS to ship it back, BPO determine the storage and track it on whiteboard or spreadsheet tracker.

Not in scope - 18. Pre-hydrated/Add-On-Fly additives load

  • May be multiple load sheets, these additives are loaded once.

Additional function discovered

  • Load Request Board, specifically use the track load requests.
  • Auto-generate load request email

Definitions

  • Bulk Plant Storage – any storage resides in the Bulk Plant. We need to number them and enter in the system, both eServiceOnline and BPAVS will reference same list of storage.
  • Project Storage - remote storage for blended product that is NOT assigned to a rig. I assume most of these storages have bin number. We need to number the rest.
  • Rig Storage – storage assigned to a rig. All of these storages have bin number.

Project Goal

  • Implement blend schedule process to utilize blend calculator in most of scenarios

  • Implement blend haul process for product transfer, product sale and blend quarantine needs

Technical Goal

  • Eliminate Call Sheet Export/Import

  • Decouple header and service line specific section to achieve more flexible solutions.

  • Decouple blend request and shipping request in product haul to achieve more flexible solutions.

  • Implement blend database for all blend using in jobs and also interim blends.

  • Enhance blend calculator to handle preblended blend modification.

  • Managing bulk plant storage in bin information systems.

  • Implement storage master database with pod structure

中文翻译

场景-场景

1. 为作业搅拌输到连接到钻机的储仓（有调度单）

  • 现有的钻机板功能

2. 为作业搅拌输并带作业队伍（有调度单）

  • 现有的钻机板功能

3. 为作业搅拌加载到连接到散装厂的储仓搅拌试（有调度单）

  • 需要为散装厂的储仓编号
  • 将散装厂视为钻机，储仓和储罐可以连接到散装厂
  • 搅拌据库来搅拌息

4. 调度运输搅拌拌到连接到钻机的储仓以进行作业（有调度单）

  • 搅拌据库来存储与调度单关搅拌息。
  • 选择散装车（Sanjel或第三方）
  • 场景1是场景3和4的一步
  • 模拟S4-1，搅拌试都在一个二级子菜单下列出，三级子菜单显示已搅拌启用，仍在测搅拌禁用。
    • 在我们拥有更新测试状态的功能之前，搅拌是启用的。调度员手动管理它们。

5. 调度运输搅拌拌到带作业队伍（有调度单）

  • 搅拌据库来存储与调度单关搅拌息。
  • 选择散装车（Sanjel或第三方）
  • 场景2是场景3和5的一步
  • 模拟S4-1支持此场景

6. 为项目搅拌输到连接到钻机的存储（无调度单）

  • 需要程序提供配方
  • 或者搅拌据库来存储配方
  • 场景7和场景15的组合，机制类似于场景1

7. 搅拌转移到连接到散装厂的储仓（无调度单）

  • 需要为散装厂的储仓编号
  • 将散装厂视为钻机，储仓和储罐可以连接到散装厂
  • 需要程序

workaround- 8. 搅拌于产品销售，使用客户的配方并运输到客户地点（有调度单）

  • 需要客户配方输入程序并从程序创建调度单。
  • 选择散装车（Sanjel或第三方）
  • 自由文本装载目的地（地点）
  • 调度单没有钻机，需要为客户创建一个假钻机。然后流程将与搅拌输相同。
  • 可能需要分搅拌运输两个步骤

workaround- 9. 搅拌于产品销售，使用客户的配方并装载到客户的散装车（有调度单）

  • 需要客户配方输入程序并从程序创建调度单。
  • 自由文本目的地（散装车），将客户散装车添加为第三方散装车
  • 调度单没有钻机，需要为客户创建一个假钻机。然后流程将与搅拌输相同。

workaround-10. 搅拌于产品销售，使用Sanj搅拌方并运输到客户地点（有调度单）

  • 需要程序并从程序创建调度单
  • 选择散装车（Sanjel或第三方），将客户散装车添加为第三方散装车
  • 调度单没有钻机
  • 可能需要根据客户请求样本测试分搅拌运输两个步骤

workaround-11. 搅拌于产品销售，使用Sanj搅拌方并装载到客户的散装车（有调度单）

  • 需要程序并从程序创建调度单
  • 自由文本装载目的地（散装车）
  • 调度单没有钻机
  • 可能需要根据客户请求样本测试分搅拌运输两个步骤

workaround-12. 调度搅拌于产品销售并运输到客户地点（有调度单）

  • 需要程序并从程序创建调度单
  • 调度单没有钻机
  • 这可能被视为与10相同，BPAVS不会搅拌程

workaround-13. 调度搅拌于产品销售并装载到客户的散装车（有调度单）

  • 需要程序并从程序创建调度单
  • 调度单没有钻机
  • 这可能被视为与10相同，BPAVS不会搅拌程

不在范围内 - 14. 使用之前搅拌成新搅拌调度单，可能适用于1, 2,3,10,11）

  • 搅拌据库来存储搅拌录以及返回搅拌
  • 需要搅拌算器

15. 调度运搅拌品从一个地点转移到另一个地点（散装厂存储或项目存储或钻机存储）（无调度单）

  • 需要为散装厂的储仓编号
  • 搅拌据库来存储搅拌录以及返回搅拌
  • 搅拌息以了解储存在储仓/储罐中的内容。
  • 与场景4相同的功能，但起点可能不同

不在范围内 - 16. 调度产品从一个散装厂转移到另一个散装厂（无调度单）

  • 类似于场景15，但仅适用于库存产品。

不在范围内 - 17. 将水泥从作业返回到连接到散装厂存储（参见调度单）

  • 需要为散装厂的储仓编号
  • 当前流程使用原始MTS将其运回，BPO确定存储并在白板或电子表格追踪器上跟踪。

不在范围内 - 18. 预水合/飞行添加剂装载

  • 可能有多个装载单，这些添加剂是一次性装载的。

发现的附加功能

  • 装载请求看板，特别用于跟踪装载请求。
  • 自动生成装载请求邮件

项目目标

  • 搅拌度流程以利用大多数场景搅拌算器
  • 搅拌输流程以满足产品转移、产品销搅拌离需求

技术目标

  • 消除调度单导出/导入
  • 解耦标题和服务行特定部分以实现更灵活的解决方案。
  • 搅拌求和装运请求以实现更灵活的解决方案。
  • 实现所有作业中使搅拌据库以及临搅拌
  • 搅拌算器以处理搅拌改。
  • 管理散装厂存储在信息系统中。
  • 实现带有pod结构的存储主数据库

Design Ideas

  • Upgrade concept "Rig" to "Operation Site", use same mechanism to process storage relations.

    • Add type to the entity
      • Operation Rig (Cement Jobs, Remedial Jobs)
      • Customer Site (for Product Sale, Project Camp )
      • Bulk Plant (Sanjel Bulk Plant)
    • Show Operation site on RigBoard as single RigJob on the bottom.
    • Schedule product transfer between Bulk Plant

  • Upgrade concept Bin and Bulker as storage

    • Implement pod structure
      • Give the pod unique identifier, can be referenced independently.
      • Add pod capacity information.
    • Implement bulk capacity reference
      • Bulk Density calculation
    • Add storage total capacity
    • Implement Storage Content Tracking
      • Implement pod level tracking
      • Overlap with blend database
      • Pop up operation page for storage tracking

  • Program back tracing

    • Start from Bin attached to rig
      • Schedule same blend for same program
      • Find future program for same client if the bin is empty.
      • Business Gap: Program expected start date and expected rig not updated in system, has sent Jeff and Brett Henry to ask.

  • Separate blend and load process

    • Per blend product haul two steps operation, blend and load.
    • Two step can be combined as one
    • Blend and load to bulk plant storage.
    • Haul preblended product from bulk plant storage to job site.

Project Scope

  • Eliminate Call Sheet Export/Import
  • Eliminate unnecessary validations for non-operation call sheet/job.
  • Company Information Section Refactoring.
  • "Revert Approval" button.
  • Master data.
    • Storage and cement transfer bulker pod level numbering, include Sanjel Bulk Plant, Project Bulk Plant, Bulker, B-Train, P-Tank, Silos, PIG LBT, etc.
    • Rig. Operation site concept implementation to extend Rig Board to support non-job associated blend and haul.
  • Process enforcement
    • Product sale must have a call sheet.
    • Job associated blend must have a call sheet
    • Project associated pre-blend must have a program.
    • Workaround 8-13 by following approach
      • Add fake rig for product sale customer to work through call sheet and Rig Board process.
      • Add customer's bulker as third party bulker crew if needed.
  • Scenario 1 - 7, 15
  • Bug fixes