[AI series Talk #2] From PoC to Production - A Case Study
0 likes132 views
The document discusses the transition from the Proof of Concept (PoC) phase to production in AI projects, highlighting various challenges such as client expectations, communication issues, and bureaucratic processes. It emphasizes that during production, clients expect full integration and ongoing support while frequently altering requirements without providing real data. The author also outlines the importance of performance and sensitivity testing to ensure system reliability and success.
[AI series Talk #2] From PoC to Production - A Case Study
- 1. From PoC to Production A case study Eugene Nguyen, PMP Technical Consultant at Nexus FrontierTech CSO, Lecturer at PMA Vietnam
- 2. - Every single AI team Wow, we have done the PoC phase Let's move it to production
- 3. Why this slide is so dark?
- 4. What every body think about AI Production PoC PoC Module A Module B Module C Module D
- 5. The true is PoC Another system that you never ever ever think about
- 6. What happen? • In PoC phase • Client want to know if the solution work or not • Client want to test your ability • Client will proceed many PoC with many team • In Production phase • Client want to apply the solution to the system • Client and you will live or die together • You are the only choice and only
- 7. Fact • Big corp only treat AI project as an experiment. • Member of AI project usually is a side task, not their main responsibility • They never focus to the project, until last responsible minutes • When PoC complete, other team will take the place and do everything to make the project done
- 9. Communication • Different time zone • Online meeting may not work • Different people from different country in same meeting (Indian, English, Spanish, etc ...) • Even client's people don't understand each other
- 10. Stakeholder • Unexpected stakeholder keep appearing • The one who work with you in the PoC phase is not the one who work with you in Production phase • Information, verbal deal with old stakeholder will be forgotten
- 11. Client expectation • No they don't have that • They expect everything • Expectation of stakeholders is different, even in a same team
- 12. Bureaucratic • Everything follow their process • Their process is very heavy and slow • A lot of rule and audit have to follow
- 13. Client infrastructure • It's not a machine, it's a system • It has a ton of security level • You never have access to the system • Debug is nightmare • They never have what you want
- 14. Change request • Change request come in hourly basis • Change request conflict • Urgent change request • Supporting update: Not for production, for their testing only
- 15. Data • You never get the real data • The example data that you have in PoC may not have any reference to the real data
- 16. Performance • You have to process ton of data every day. You have to calculate and propose the hardware for that • Every single crash may not accepted • Sensitivity testing is a must • Performance testing is a must