Sensia JV Data Extraction

Published on
Embed video
Share video
Ask about this video

Scene 1 (0s)

[Audio] The Sensia JV Historical Data Extraction project aims to transfer historical data from Optimus BI/BW to Sensia's Blob Storage, which is crucial for our operational transition post our migration from Optimus SAP systems..

Scene 2 (17s)

Introduction.

Scene 3 (23s)

Project Overview. [image]. 01.

Scene 4 (29s)

[Audio] The primary objective of this project is to ensure the seamless transfer of historical data from Optimus BI/BW to Sensia's Blob Storage. This transfer is critical for facilitating Sensia's operational transition following its migration from Optimus SAP systems..

Scene 5 (46s)

[Audio] A data flow has been established between Optimus SAP and Sensia's Blob Storage, which was successfully approved in December of the previous year. This existing infrastructure serves as a foundation for our current project, enabling us to build upon a solid base..

Scene 6 (1m 3s)

[Audio] A one-time historical data extraction is required to guarantee that all pertinent data is accessible within the new Sensia system. This extraction will concentrate specifically on the recognized datasets and their corresponding filters..

Scene 7 (1m 17s)

[image]. Requirements. 02.

Scene 8 (1m 23s)

[Audio] To extract the historical data accurately, we need to apply specific filters to ensure that only relevant data is transferred. These filters include plant codes ranging from J004 to J013, company codes such as US28, CA28, GB28, and AE28, and specific profit centers like 711 and 719. By applying these filters, we can guarantee that the data extracted is precise and meets our requirements..

Scene 9 (1m 56s)

[Audio] The data flow from Optimus BW/BI to Sensia's Blob Storage will utilize the SIMS ETL tool. This path was chosen to ensure efficient data management and retrieval. By leveraging this established route, we can streamline the process and guarantee seamless data transfer..

Scene 10 (2m 15s)

[Audio] The dataset essentials emphasize the significance of adhering to defined filters during the data extraction process. Defined filters are a vital component in ensuring that the transferred datasets meet Sensia's operational needs. By concentrating on specific tables containing Sensia-relevant data, we can confirm that the extracted information accurately represents the company's requirements..

Scene 11 (2m 39s)

Implementation Proposal. [image]. 03.

Scene 12 (2m 45s)

[Audio] To facilitate secure access and data management, we will establish a SharePoint site for restricted external access. This solution is designed to enhance security controls and provide tracking capabilities for data access. The site will be configured to allow specific user permissions, ensuring that sensitive data is protected while remaining accessible to authorized personnel..

Scene 13 (3m 8s)

[Audio] Files transferred to SharePoint will undergo encryption to protect data integrity and confidentiality during the upload process. The encryption strategy ensures that all files placed in the Sensia designated folder are secured, requiring decryption by authorized Sensia personnel before access. This added layer of security is crucial given the sensitive nature of the historical data being transferred..

Scene 14 (3m 33s)

[Audio] Files uploaded to SharePoint will be handled according to specific guidelines due to storage limitations. Large files exceeding 15 gigabytes will be split into smaller segments to simplify management and reduce the risk of system overload. Sensia's team will be responsible for decrypting, retrieving, and unzipping these files before loading them into SQL..

Scene 15 (3m 56s)

[image]. Timeline and Costs. 04.

Scene 16 (4m 3s)

[Audio] The project is on track to meet its completion deadline, with a scheduled finish date between December 2024 and February 2025. We have made significant progress towards achieving our objectives, including the successful extraction of 115 HANA views, which meets Sensia's requirements. Additionally, we will ensure that all operational workflows remain uninterrupted throughout the transition process..

Scene 17 (4m 29s)

[Audio] The project's cost breakdown reveals a comprehensive picture of expenses incurred throughout its duration. The SIMS team received $20000, which ensured seamless integration between systems. Substantial resources were dedicated to SAP BW/BI efforts, totaling $26,500, focusing on streamlining data extraction processes. Security measures were implemented to safeguard sensitive information, costing $1,800. Careful consideration was given to FS document requirements, resulting in an expenditure of $4000. These various components collectively contributed to a total project cost of approximately $52,300..

Scene 18 (5m 14s)

[Audio] The comparison between projected and actual estimates reveals that although our initial calculations were accurate, unforeseen circumstances arose during implementation, requiring adjustments. Consequently, we encountered variances in specific areas, including SAP BW/BI efforts and document management. This underscores the significance of flexibility and adaptability in project planning, enabling us to address unexpected challenges efficiently..

Scene 19 (5m 42s)

Challenges. [image]. 05.

Scene 20 (5m 48s)

[Audio] Several challenges have arisen during the data extraction process, primarily due to issues with the integrity and functionality of HANA views. Complications with full loads when extracting data from SAP tables have significantly impacted overall efficiency and reliability..

Scene 21 (6m 6s)

[Audio] The presence of special characters within the extracted data has significantly impacted our ability to successfully complete the data transfer process. The SIMS team has faced numerous challenges while attempting to extract records from HANA views, as the system's limitations on record checks have hindered our ability to identify and address problematic entries. These issues have resulted in frequent load failures, which have slowed down our progress and increased the risk of errors. To overcome this challenge, we will need to develop a more robust approach to handling special characters in the extracted data..

Scene 22 (6m 43s)

[Audio] The high volume of user accesses to the Optimus system has raised concerns about system performance. As we move forward with the historical data transfer from Optimus to Sensia's Blob Storage, it's crucial that we consider the potential impact on system performance. With multiple Sensia employees accessing the data, there's a risk of straining the existing infrastructure and degrading service quality. We need to ensure that our solution minimizes any negative effects on system performance..

Scene 23 (7m 15s)

[Audio] The Sensia JV Historical Data Extraction project is a critical initiative that ensures a smooth transition from Optimus to Sensia's data management systems. By addressing the identified challenges and implementing the proposed strategies, we can significantly improve data accessibility and operational efficiency, all while maintaining robust security practices..

Scene 24 (7m 38s)

[Audio] We appreciate your attention throughout this presentation, which has covered the key aspects of our proposal to extract historical data from Optimus to Sensia's Blob Storage. We have outlined the implementation plan, discussed the benefits, and addressed potential concerns. Now, it's time to address any questions you may have. Please feel free to ask anything that's unclear or requires further clarification. Your input is valuable to us, and we are here to support you throughout this process..