1. WFO Planning Tool RFC & FCT
STMicroelectronics
Wafer Foundry Outsourcing

2. Team Members & Roles Matric No Name Role A0066009J
Chetan Krishna Dhulipalla
Project Manager
A A
Swetha Vardharajan
B.A/Project Lead
A R
Rama Rao Dutta
Technical Lead
A N
Kyaw Lwin Phyo
Quality Manager/ DB Admin
A Y
Venkatakrishnan Kambarajan
Test Lead

3. Business Objective
Need for medium term forecast of the demand and supply to plan business growth.
Improve the correctness in the decision making process of WFO planning team and ST management, by providing the pattern of the demand and supply from ST customers and ST foundries respectively on a one year scale.
Improve the productivity and effectiveness of the WFO Planners.

4. Scope WFO Planning Tool assists WFO planner in bridging Supply demand.
Developing a medium term forecast module (FCT) for analyzing the business of the company for future plans and also to enhance the functionality of the current short term forecast module (RFC).
Based on the data from FCT, implement the enhancement in the RFC module.

5. Business Flow Foundry A ST Group A (China) Product 1 Request
Foundry B
(Malaysia)
ST Group A
Product 1
ST Group B
(Product 3
Needs/Request
Needs/ Request
WFO
Planning
Team
Request
Commit

6. Required System Foundry A (China) Cap-50 ST Group A Request - 50
Product 1
Request - 50
Needs -80
Request - 50
WFO
Planning
Team
Capacity- 50
Commit-50
Commit-80
Commit-50
ST Group B
Product 3
Needs -80
Request - 50
Request - 50
Request - 80
Request - 80
Foundry B
(Malaysia)
Cap-50
Capacity- 50
Capacity- 80
+ Cap-30

7. STM  WFO  FDY Planning Process –Requirements of RFC and FCT
Monthly CRP Request
Request
By PN
FCT
Tool
Forecast
By Area / Capa
Monthly Visibility 12 Months horizon
CRP Com & CCAR
Commit by
Area / MP / Group
Alloc
Confirmation
By Area / Capa
Real demand by PN & Capacity Limitation by Area / MP / Group / W
Manual
entry
Request
by PN
RFC
Constrained order
by PN
Weekly orders 17weeks horizon
I2 / MPS
Commit
By PN
Commit
By PN
CCP
WFO 7

8. Development Strategy
Phase-1, Phase-2 activity of project is performed in waterfall model.
Phase-3 is developed using SCRUM methodology.
Total Number of Sprints – 5.
Life time of Sprint – 1 Week.
Developed in Client location, as the tool is tightly integrated with STMicroelectronics internal OrgSec tool.
Client suggested iterative incremental model, as parallel work is being done on the same tool.

9. Reasons for Choosing SCRUM
Client need to integrate continuously with the current system.
As parallel development work is occurring team expected last minute change requests.
SCRUM provides easy feedback system from client, as client is closely involved in the project progress – vital to project success.

10. UCMS for FCT

11. UCMS for RFC 11

12. System Architecture 12

13. Physical Architecture overview13

15. Technical Issues During Phase 3
Issue with design of RFC – In the current application the complete logic is performed in Week17Page.
Issue with setting up Configuration Management System – The clearcase on the system could not be configured.
Issue with Database – Parallel usage of DB led to ‘Lock of the DB Procedures’.

16. Solution for Technical Issues
Issue with design of RFC – We designed and implemented the enhancement based on the existing structure/design for RFC.
Issue with setting up Configuration Management System – The entire application was divided into modules and split the work individually and integrated using the common shares folder at the end of each day.
Issue with Database – Cleared the issue by defining separate schema for our project, there by ensuring the DB lock do not occur.

17. Demonstration Video 17

18. Acceptance Procedure
As part of SCRUM Methodology, team delivered the components/deliverables on sprint (week) basis.
The Customer would examine the deliverable and share the feedback with the team.
At the end of project, after the system testing is performed by the team, User performs official Acceptance Testing before the sign off.

19. Customer Feedback
As the development was performed on client location, the user had a closer view on the daily activity of the team.
The customer identified an issue with deliverable of sprint 1, he raised it during the sprint 3 process. Team rectified the issue during the sprint 4.
User reviewed the team’s System test log, bug tracking system, and performed an informal acceptance testing before signing off the Project Acceptance.

20. Project Progress – Planned / Actual20

21. Project Progress – Planned / Actual

22. Project Progress – Planned / Actual

23. Project Progress – Planned / Actual

24. Project Progress – Planned / Actual

25. Project Progress – Planned/ Actual Effort (Man Days)

26. Management Problems – Phase 3
Tasks from Planned Phase 2 – Detailed Design
Detailed design and system test plan were finished and finalized before the start of coding phase.
Delay in start of Phase 3 – Started on 17/1/2011 but planned to start on 10/1/2011.
Addressed with contingency. Prepared System Test Plan during this period.
Late notice of unavailability of QM.
Cancelled Sprint 2 re-planned the sprints, Additional Sprint.

27. Management Problems – Phase 3
Unexpected leaves at the end of January.
Cancelled Sprint 2.
Closure of ST for Chinese New Year (Forced Vacation)
The schedule was delayed. But, have sufficient contingency.
Unavailability of systems at STMicroelectronics.
Two heads on same code, increased effectiveness and reduced the number of bugs in coding phase.

28. What’s Next??? The next milestones for WFOPT are envisioned as:
Additional Features on Medium Term Forecast Module.
The next stage of WFOPT would be to develop Long term forecast tool which would be on 2 years to 5 years period on quarters scale.
Similar to the request restriction in RFC based on the capacity value from FCT. The content in FCT could be controlled based on the data from long term forecast tool which would make the tool even more effective.

29. Lessons Learnt Resource Planning (Back up)
No Back up for the activities performed by a single assigned resource.
Faced few issues due to sudden unavailability of quality manager.
Customise Process to suit your project.
Implemented SCRUM for the coding phase alone.
Enabled to identify defects early.
Simplified the Integration and User Acceptance activities.
Code Walk Through and Resource Management
Due to constraint in system availability, team engaged two heads on single code.
This reduced defects in coding, thus reduced rework. 29

30. Q & A

31. Thank You

32. Plan for Implementation Phase - SCRUM
Client Proposal – Iterative Incremental Development.
Team’s Proposal – SCRUM.
Product Backlog:
RFC Functionality.
FCT Functionality.
Data Transfer between RFC & FCT.
Validation/Approval in FCT.
Download/Upload data in FCT.
Sprint Duration – 1 week.
Number of Sprints – 4. 32 32

33. Sprint Release Planning
Sprint-1 Backlogs
RFC Functionality
New Parameters for a particular product.
Capacity validation using M-FEG data from DB
Sprint-2 Backlogs
FCT Functionality & Integrate RFC & FCT
Attributes for a product to be added.
Change in attribute should reflect in RFC.
Sprint-3 Backlogs
Validate functionality in FCT & Upload, Download Functionality.
Validate functionality similar to RFC.
Upload and download the data of the particular product from DB.
Sprint-4 Backlogs
System Testing & Contingency
System Testing and test documentation and results.
Rectification activity.
Contingency.

34. Product Backlog