Automate Worksheet

population
Problem statement:
When B screen populated using G FEDEBOM BOMFEDED (WERS ID) through automate process
and worksheet populated with interop admin WERS ID (manually), the system isn’t allowing to AC
the activity as its missing the worksheet with BOMFEDED user.

Possible usecases
• 1 D&R engineer has 2 parts for 2 activities
• 1 D&R engineer 2 Functions(CPSC,SEQ etc could be different) but same activity
• Multiple D&R engineers with same activity
• Multiple D&R engineers with different activities
Suggested approach (Lead Engineer):
1) Creation of B screen population with Lead engineers rather than the Generic ID BOMFEDED/ BOMFEDEQ
2) Automation of populating 1 screen (Engineer estimate) for Lead engineers
3) Back office can use Activity summary (G screen) to AC the concern (can be considered for Automation)
4) This way Notice gets created along with Parts

Task-wise:
•Concern creation and B screen population at the time CMF moves to Contributor input
•Automation of (Engineer Estimates) 1 screen according to Lead Engineer at the time of 'Confirm Engineering Input Complete'(Engineering Worksheet)
Task completion

To resolve when 2 different activities for same engineer:

Engineer worksheet in FEDEBOM: Only one single Engineer Worksheet for every Lead engineer irrespective of activity, we might not able to separate them in 1 (Engineer Estimate)
screen
-Can we have different worksheets for Lead Engineers when there is more than 1 activity?

Important Points to note:

1. B screen population – Part function activity must match with the User activity, there should not be any mismatch
2. Lead Engineer change – not a prominent usecase. If changes to Lead Engineer current WERS process to be followed
3. If there are multiple D&R Engineers belonging to different activities, once worksheets for a particular activity is updated, should be allowed to AC and
create Notices for that activity rather than wait for all activity worksheets to be updated
Notice Grouping
• Currently, Grouping Indicator not populated in BOMWork file. Interop to do manually by directly
look into the CMF
• Need to consider when Notice grouping changes in FEDEBOM, it has to be cascaded to WERS in
the ‘Grouping Indicator’ field through BOMWork file. At present, there is no trigger point when
Notice grouping changes
• Need to have Incremental Glidepath for Automation process
• Verify if the Default Notice grouping logic in FEDEBOM is matching with the grouping logic in
WERS
 Appendix
Non-Fedebom concerns with non-blank userids (WERS Worksheet Estimate data)
Concern Created Date range: 10/01/2022 to 04/30/2023
Data snapshot taken on 6/23/2023

% of Zero vs Non-Zero estimates

1.04% 0.84% 0.73% 0.13% 0.07% 0.05% 0.03%
100.00%
4.77%
8.48% 7.94%

90.00%

80.00%

70.00%

98.96% 99.16% 99.27% 99.87% 99.93% 99.95% 99.97%

95.23%
60.00% 91.52% 92.06%

50.00%

40.00%

30.00%