Hussman Scheduled maintenance 

Planned Maintenance  Activities

1. As planned performed the HOPS Weekly Maintenance Cycle to avoid failure notification for HOPS DB Events.  

2. Performed weekly maintenance Cycle to avoid failure notification for USINT0600 (TCAdeptiaDBP database down).  

3. We are monitoring the bank integration JPMB_PF_USINT0700_701_GenENCR_EDI820_Hussmann_JPMC  every day at 12:31 PM CST. If the integration fail, then we report it immediately as it is a critical failure.) 

4. We are monitoring the integration HUS_FTPE_USINT0706_ACS_HussmannBranch every day between 6 PM to 7 PM CST as it is time sensitive.

5. Tavant downtime performed in a weekend.

HOPS Weekly Maintenance Cycle

1. Schedule Maintenance:

   • Plan and schedule the HOPS Weekly Maintenance Cycle at a time with minimal impact on users.

2. Notify Stakeholders:

   • Inform relevant stakeholders about the scheduled maintenance to avoid unexpected disruptions.

3. Backup HOPS DB:

   • Ensure a full backup of the HOPS database is completed before beginning maintenance activities.

4. Perform Maintenance:

   • Execute the weekly maintenance tasks such as database optimization, index rebuilding, and log file cleanup.

5. Verify System Health:

   • Check the system logs and performance metrics to ensure that the HOPS DB is functioning optimally post-maintenance.

6. Document Activities:

   • Record all actions taken during the maintenance cycle, including any issues encountered and resolutions applied.

Weekly Maintenance Cycle for USINT0600 (TCAdeptiaDBP Database)

1. Plan Maintenance Window:

   • Schedule the maintenance for a low-traffic period to minimize user impact.

2. Communicate with Team:

   • Notify the relevant team members and stakeholders of the planned maintenance window.

3. Backup Database:

   • Perform a full backup of the TCAdeptiaDBP database to prevent data loss.

4. Conduct Maintenance:

   • Execute the necessary maintenance tasks such as updating configurations, cleaning up logs, and ensuring database integrity.

5. Test System Functionality:

   • Validate that the TCAdeptiaDBP database is operational and no critical errors are present.

6. Report Completion:

   • Document the maintenance activities and communicate the successful completion to the team.

Daily Monitoring of JPMB_PF_USINT0700_701_GenENCR_EDI820_Hussmann_JPMC Integration

1. Set Up Monitoring Tool:

   • Ensure monitoring tools are configured to track the JPMB_PF_USINT0700_701_GenENCR_EDI820_Hussmann_JPMC integration.

2. Daily Check:

   • Review the integration status every day at 12:31 PM CST.

3. Alert Configuration:

   • Configure alerts to notify the team immediately if the integration fails.

4. Immediate Reporting:

   • If a failure is detected, report it to the concerned team as it is a critical failure that needs urgent attention.

5. Log Issues and Resolutions:

   • Maintain a log of any issues identified and the steps taken to resolve them.

Daily Monitoring of HUS_FTPE_USINT0706_ACS_HussmannBranch Integration

1. Configure Monitoring Schedule:

   • Set up monitoring for the HUS_FTPE_USINT0706_ACS_HussmannBranch integration between 6 PM and 7 PM CST.

2. Perform Daily Monitoring:

   • Check the integration status during the specified time window to ensure it is running as expected.

3. Setup Alerts:

   • Configure alerts to detect and notify the team of any failures or anomalies in the integration.

4. Action on Failure:

   • Immediately investigate and resolve any integration failures as it is time-sensitive.

5. Report and Document:

   • Report any issues to the relevant stakeholders and document the incident and resolution steps.

Tavant Downtime Maintenance

1. Plan Downtime:

   • Schedule the Tavant downtime during a weekend to reduce the impact on business operations.

2. Inform Stakeholders:

   • Notify all affected users and stakeholders about the planned downtime in advance.

3. Prepare for Maintenance:

   • Backup all critical data and ensure all necessary resources and personnel are ready for the maintenance tasks.

4. Execute Maintenance:

   • Perform the required maintenance activities, such as updates, patches, or system optimizations.

5. System Validation:

   • After maintenance, verify that all systems are up and running correctly and perform necessary tests to ensure stability.

6. Communicate Completion:

   • Inform stakeholders that the maintenance is complete and provide a summary of the activities performed.

7. Post-Maintenance Monitoring:

   • Monitor the system closely for any post-maintenance issues and address them promptly.

By following these steps, you can ensure that critical systems are well-maintained, integrations are monitored effectively, and any issues are promptly addressed to maintain system stability and performance.