1. URS & Functional Documentation
1.1. Updated Functional Documentation of Addverb System
2. AMC Finalization
3. System Performance
3.1. Database Sizing
3.1.1. Database Indexing & Archival Policy Definition
3.2. Hardware Capability
3.2.1. Identification of Hardware Requirements - Enterprise Application and Reporting Server Split
3.2.1.1. Costing Details in Progress
3.2.2. Detailing of Archival Policy and moving the archived data from Production Server
3.2.2.1. Costing Details in Progress
4. Application Issues
4.1. Immediate
4.1.1. Issue Resolution [18 Issues]
4.1.1.1. Bin to Bin Process [6 Issues]
4.1.1.1.1. SOP's
4.2. Long Term
4.2.1. Load Testing
4.2.1.1. Connection Pooling
4.2.1.1.1. PutAway
4.2.1.1.2. PutAway and Picking [C Class]
4.2.1.1.3. Query Fine Tuning
4.2.2. Exception Handling
4.2.3. Code Review
4.2.4. Query Fine Tuning
4.2.5. Implement Application Monitoring Tool
4.2.5.1. Implement Prometheus [ETC 02/07]
4.2.5.2. Log 4J2 Upgrade to Log 4J2 [ETC 02/07]
4.2.5.3. Grafana HW Monitoring Implementation [ETC 02/07]
4.2.5.3.1. Performance: Historical Performance Monitoring Enabling
4.2.6. Staging Server for Production Testing
4.2.7. Enabling SIT and UAT Servers for software and hardware testing
4.2.7.1. Test Server Sizing & Licensing Requirements Proposal Details
4.2.7.2. Costing Details
4.3. Logging and Exception handling
4.3.1. Application Logs to be made available for easier and faster debugging
4.3.2. Proper error messages to be thrown so that troubleshooting is faster
5. Network Issues
5.1. Immediate
5.1.1. Faulty Device Replacement
5.1.2. Internet Speed Monitoring ( by ISP)
5.1.3. Internet Link & Network Support
5.1.3.1. Availability of a dedicated person from Addverb for Network Support
5.1.3.2. Make Airtel as Primary Link
5.1.3.2.1. Hardware Configuration to enable 25MBPS in the warehouse
5.1.3.3. Add Sify as secondary link
5.1.3.3.1. Automatic Swap between two links in the warehouse
5.1.3.3.2. Automatic Swap outside the warehouse network
5.1.4. 24*7 Network Support by Skylark
5.1.4.1. Proposal Submission for Dedicated support by Skylark to Addverb
5.1.5. Wifi Installation at the Blind Spot
5.1.5.1. Implement Network Monitoring Tool
5.1.5.1.1. Discussion Kickstart
5.1.6. Dedicated cooling room for Server
5.1.7. A/B testing of networks to identify the impact
5.2. Long Term
5.2.1. Assessment of Network Topology
5.2.1.1. Survey by Cisco team
5.2.1.1.1. All physical documents and pictures shared with Cisco Team
5.2.1.2. Addverb Dashboard Query Fine Tuning
5.2.1.2.1. Testing Abhishek / Bharath [ETC 04/07]
6. Governance
6.1. Setup Service Review every on Monday, Wednesday and Friday
6.2. Demand Management
6.2.1. Wk IPM Call Setup
6.3. L1/L2 Process Finalization
6.3.1. Setup CAB Process
6.3.2. Freshdesk Tool Implementation
6.4. Ways of Working
6.4.1. Knowledge Management
6.4.1.1. Manual Error Scenario's
6.4.1.1.1. Bug Categorization
6.4.1.2. SOPs
6.4.1.2.1. Updated SOPs and FSDs to be shared
6.4.2. Release Management Process
6.4.2.1. Documentation of Release Notes and Signs offs of Test results from Addverb including Regression Testing Results
6.4.3. Documentation & Signoff of FSD, Test Scenario btw Addverb & Unilever Functional Team
6.4.4. Setup Critical Issue Governance
6.4.4.1. Issue monitoring process and categorization of issues in Daily Huddle
6.4.5. Response Time from Addverb and POC for Application Development, Application Support and Network Support
6.4.6. Google sheet created for logging of issues
7. Changes, New Requirement
7.1. New Reports
7.1.1. Report Format Evaluation Complete and Prioritization Complete
7.1.1.1. Identification of Data sets to generate reports & design the wireframe
7.1.1.2. Development Timeline discussion in progress
7.2. Change List
7.2.1. URS Documentation of Aug - October Release Complete (expansion related requirements)
7.2.1.1. Development in Progress as per prioritization
7.2.2. Backlog of Bug Fixing
7.3. Automation of Repeated L1 issues
8. Completed
9. In Progress
10. Existing Data Availability
10.1. Immediate
10.1.1. Data Accessibility of Existing Reports
10.1.1.1. Enabled Accessibility of Daily reports in a Central Location on Teams Site
10.1.1.1.1. Automation of Excels - do we need to get this enabled ?
10.1.2. Historical Data Dumps
10.2. Long Term
10.2.1. Creation of Dedicated S3
10.2.2. Datalake and Cataloging
10.2.2.1. Discussion Kickstart
11. Future Design
11.1. Automated slotting
11.2. Inventory ownership
11.3. Utilizing idle time for maintenance activities
11.4. Norms improvisation
11.5. Ensuring enough tasks are there at all zones
11.6. Right sizing of zones
11.7. 2 shift operations
11.7.1. No operations on Sunday