CSM_BITS_ANM_0002
BITSAP LCSM Site Unavailability During Night Hours
Status: PENDING CLIENT SERVER ACTION
Updated Oct 7, 2026 7:10 PM IST
1. BUG REGISTRATION
| S.No. | Attribute | Entry |
|---|
| 1 | Safety Anomaly ID | CSM_BITS_ANM_0002 |
|---|
| 2 | Bug Title | BITSAP LCSM Site Unavailability During Night Hours |
|---|
| 3 | Bug Description | The BITSAPlCSM site becomes unavailable while working on the Chip Manager tool after 12:00 AM and remains inaccessible until the morning. The issue has been observed three times. |
|---|
| 4 | Detection Source | User Observation |
|---|
| 5 | Initial Evidence | Site was observed to be inaccessible after 12:00 AM during Chip Manager usage. The site became accessible again during the morning. Issue observed on three separate occasions. |
|---|
| 6 | Reported By | Bits student |
|---|
| 7 | Reported Date/Time | 29/09/2026 |
|---|
2.INITIAL ASSESSMENT
| S.No. | Attribute | Entry |
|---|
| 1 | Affected Item | bitsaplcsm.com deployed application availability / client server hosting environment |
|---|
| 2 | Version / Configuration | Current deployed CSM BITS site hosted on client-provided server |
|---|
| 3 | Anomaly Classification | Infrastructure / Server Availability Anomaly |
|---|
| 4 | Safety Relevant? | No |
|---|
| 5 | Initial Safety Impact | No direct functional-safety impact identified. The issue affects site availability during the server shutdown window only. |
|---|
| 6 | Responsible Person | BITS IT/server team with AiSemi support for application verification |
|---|
| 7 | Initial Evidence | Windows Event Logs show planned server shutdown around 12:06 AM and server/event-log start around 6:02 AM on multiple days. |
|---|
| 8 | Initial Assessment Comment | Initial assessment indicates that the application is unavailable because the client server itself is shut down during the night window. No application coding failure was identified from the available evidence. |
|---|
| 9 | Replication / Triage Status | Confirmed / Routed to Client Server Team |
|---|
| 10 | State Entry Date/Time | 2026-09-29 10:30:00 |
|---|
| 11 | State Exit Date/Time | 2026-09-29 11:00:00 |
|---|
3.ANALYSIS & ROOT CAUSE ANALYSIS
| S.No. | Attribute | Entry |
|---|
| 1 | Reproducible? | Yes, based on repeated server event-log pattern. |
|---|
| 2 | Reproduction Result | The site unavailability aligns with repeated planned server shutdown events after midnight and startup events around 6 AM. |
|---|
| 3 | Reproduction Steps | 1. Access bitsaplcsm.com after 12:00 AM.
2. Observe site unavailable.
3. Review Windows System Event Logs.
4. Confirm planned shutdown around 12:06 AM and startup around 6:02 AM. |
|---|
| 4 | Failure Mode | The BITS site becomes unavailable when the hosting server is shut down. |
|---|
| 5 | Failure Mechanism | The client-provided server is shut down during the night window, so the web application and dependent services cannot respond to user requests. |
|---|
| 6 | Technical Analysis | Windows System Event Logs show Event ID 1074 planned shutdown initiated by SYSTEM/svchost.exe with comment 'Calling CleanShutdown by wvchelper', followed by Event ID 6005 server/event-log startup in the morning. This indicates infrastructure-level shutdown rather than application code failure. |
|---|
| 7 | Impact Analysis | Users cannot access the site during the shutdown window. Existing application data, saved work products, login logic, and safety analysis calculations are not altered by this event. |
|---|
| 8 | RCA Method | Windows Event Log Review / Infrastructure Availability Analysis |
|---|
| 9 | Root Cause | The client-provided server is scheduled or configured to shut down during the night window and restart in the morning. |
|---|
| 10 | Contributing Cause | Server availability policy or maintenance schedule was not confirmed before 24/7 application availability expectation. |
|---|
| 11 | Verification Gap | Earlier deployment verification did not include confirmation of client server availability policy for the 12 AM to 6 AM window. |
|---|
| 12 | Analysis Conclusion | The issue is caused by client server shutdown behavior and is not an application coding issue. Application availability depends on the server remaining powered on and reachable. |
|---|
| 13 | Analysis Evidence | Windows Event Logs showing repeated planned shutdown around 12:06 AM and startup around 6:02 AM; user observation of site unavailability in the same window. |
|---|
| 14 | RCA Dependency / Delay | Resolution depends on confirmation/action from BITS IT/server team regarding server shutdown policy. |
|---|
| 15 | State Entry Date/Time | 2026-09-29 11:00:00 |
|---|
| 16 | State Exit Date/Time | 2026-09-29 11:30:00 |
|---|
4.CRITICALITY / SAFETY EVALUATION
| S.No. | Attribute | Entry |
|---|
| 1 | Safety Goal Impact | No impact identified. |
|---|
| 2 | Safety Requirement Impact | No impact identified. |
|---|
| 3 | Safety Mechanism Impact | No impact identified. |
|---|
| 4 | Criticality | Low for safety; Medium for availability. |
|---|
| 5 | ASIL Impact | No ASIL impact. ASIL values were not altered. |
|---|
| 6 | Risk Evaluation | The issue affects site access during server downtime only. It does not modify safety data, safety requirements, safety mechanisms, project records, or calculation logic. |
|---|
| 7 | Residual Risk | Low safety risk; availability risk remains until server schedule is confirmed or changed. |
|---|
| 8 | Evaluation Rationale | The anomaly is infrastructure availability related. When the server is running, the application can be accessed normally; during shutdown, no web application can remain available on that server. |
|---|
| 9 | Evaluation Evidence | Event log evidence and server boot/shutdown timing review. |
|---|
| 10 | State Entry Date/Time | 2026-09-29 11:30:00 |
|---|
| 11 | State Exit Date/Time | 2026-09-29 11:45:00 |
|---|
5.CONTAINMENT & CORRECTIVE ACTION
| S.No. | Attribute | Entry |
|---|
| 1 | Containment Required? | No application safety containment required.(restricted) |
|---|
| 2 | Containment Action | Inform client/BITS IT team about the observed shutdown schedule and request confirmation whether it is an intentional server policy. |
|---|
| 3 | Corrective Action | Request BITS IT/server team to confirm whether the 12 AM to 6 AM shutdown is policy-driven, and to change or remove the schedule if 24/7 access is required. |
|---|
| 4 | Safety Measure | No product safety measure required. Server availability action is required from the infrastructure side. |
|---|
| 5 | Change Required? | No application code change required |
|---|
| 6 | Change Reference | Client server shutdown schedule / infrastructure availability clarification. |
|---|
| 7 | Action Owner | BITS IT/server team; AiSemi to support verification after server-side action. |
|---|
| 8 | Implementation Status | Pending BITS IT/server team confirmation |
|---|
| 9 | Action Evidence | Windows Event Log evidence captured; client clarification mail/request prepared. |
|---|
| 10 | State Entry Date/Time | 9/29/2026 |
|---|
| 11 | State Exit Date/Time | 9/29/2026 |
|---|
6.VERIFICATION & EFFECTIVENESS
| S.No. | Attribute | Entry |
|---|
| 1 | Fix Verification | 9/29/2026
Application-side verification completed; server-side availability requires BITS IT confirmation/action. |
|---|
| 2 | Verification Method | Review of Windows Event Logs, server boot/shutdown time, and application availability behavior outside the shutdown window. |
|---|
| 3 | Verification Result | Application code issue not identified. Site availability is blocked when the hosting server is shut down. |
|---|
| 4 | Effectiveness Verified? | Partially. Root cause identified; final effectiveness depends on server schedule change or policy confirmation. |
|---|
| 5 | Residual Impact | Site will remain unavailable during the shutdown window unless the client server schedule is changed or alternative hosting availability is provided. |
|---|
| 6 | Verification Conclusion | The issue is confirmed as server/infrastructure availability related, not application coding related. Further action is required from BITS IT/server team for 24/7 access. |
|---|
| 7 | Verification Evidence | Windows Event IDs 1074, 6006, and 6005 showing planned shutdown and morning startup pattern. |
|---|
| 8 | Verifier | AiSemi software team |
|---|
| 9 | State Entry Date/Time | 9/29/2026 |
|---|
| 10 | State Exit Date/Time | 9/29/2026 |
|---|
7.CLOSURE & APPROVAL
| S.No. | Attribute | Entry |
|---|
| 1 | Closure Route | Routed to BITS IT/server team for server policy confirmation and required infrastructure action. |
|---|
| 2 | Safety Measure Adequate? | Yes. No product safety measure was required. |
|---|
| 3 | Effectiveness Verified? | Root cause identified; 24/7 effectiveness requires client server schedule action. |
|---|
| 4 | Unreasonable Risk? | No safety risk identified. |
|---|
| 5 | Closure Rationale | The anomaly is not caused by BITS application coding. Evidence shows the client-provided server is shut down during the reported downtime window. The issue is routed to the BITS IT/server team to confirm or change the shutdown policy if 24/7 access is required. |
|---|
| 6 | Closure Evidence | Windows Event Log evidence, server boot time, planned shutdown records, and user downtime observation. |
|---|
| 7 | Rationale Reviewed? | Yes (we ask about evidance here that willbe writtten down) |
|---|
| 8 | Review Comments | Application-side review completed. Server-side policy confirmation/action is pending with BITS IT/server team. |
|---|
| 9 | Closure Decision | PENDING CLIENT SERVER ACTION |
|---|
| 10 | Reviewer | AiSemi software team / BITS IT server team |
|---|
| 11 | Final State | PENDING CLIENT SERVER ACTION |
|---|
| 12 | State Entry Date/Time | 9/29/2026 |
|---|
| 13 | State Exit Date/Time | Pending BITS IT/server confirmation |
|---|
