Disasters and Other Contingencies. The FEMA IPAWS Program Office will notify the COG by telephone, e-mail or other acceptable means in the event of a disaster or other contingency that disrupts the normal operation of IPAWS-OPEN.
Disasters and Other Contingencies. Both parties shall:
Disasters and Other Contingencies. The FEMA IPAWS Program Office will notify the COG by telephone, e- mail or other acceptable means in the event of a disaster or other contingency that disrupts the normal operation of IPAWS-OPEN. System Interconnections: This MOA is intended for systems interoperating with IPAWS-OPEN using SOAP over HTTPS via the public Internet. If in the future, an interconnection (i.e. dedicated system-to-system connection) is required to IPAWS-OPEN, this MOA must be updated and an Interconnection Security Agreement (ISA) must be executed. If a change in status from interoperating to interconnected system is required, the initiating party will notify the other party at least 3 months before the planned interconnection is to be in place. Discontinuation of Use: In the event the use of IPAWS-OPEN is no longer required, the COG agrees to immediately notify, in writing, the FEMA IPAWS Program Office at which time the COGID and associated access credentials will be deactivated. Personnel Changes: Both parties agree to provide notification of changes to their respective system owner or technical lead. In addition, both parties will provide notification of any changes in the point of contact information provided in Appendix B. All relevant personnel changes and changes to contact information must be provided within 5 business days of the change.
Disasters and Other Contingencies. The technical staff will immediately notify their designated counterpart by telephone or e-mail in the event of a disaster or other contingency that disrupts the normal operation of one or both of the connected systems.
Disasters and Other Contingencies. Both parties shall notify immediately their designated counterparts as defined in the information system contingency plan in the event of a disaster or other contingency that disrupts the normal operation of one or both of the connected networks. If any personnel changes occur involving the POCs listed in this ISA, the terms of this ISA shall remain in full force and effect, unless formally modified by both parties. Any modifications that change the security posture to this ISA shall be in writing and agreed upon and approved in writing by either parties or their designees.
Disasters and Other Contingencies. System staff who experience a disaster or other contingency that disrupts the normal operation of one or more of the systems covered by this interconnection MOU will immediately notify their designated counterparts by telephone or e-mail. Data Redisclosure: OIG will redisclose data only as authorized by the ODAS System of Records Notice (SORN). Any disclosure outside of what is authorized by the XXXX XXXX must be mutually agreed upon by both OIG and FSA.
Disasters and Other Contingencies. Technical staff of each organization will immediately notify their designated counterparts by telephone or e-mail in the event of a disaster or other contingency that disrupts the normal operation of one or both connected systems. Material Changes to System Configuration: Planned technical changes to the system architecture will be reported to technical staff before such changes are implemented. The initiating party agrees to conduct a risk assessment based on the new system architecture and to modify and re-sign the ISA within one (1) month of implementation. New Interconnections: The initiating party will notify the other party at least one (1) month before it connects its IT system with any other IT system, including systems that are owned and operated by third parties.
Disasters and Other Contingencies. Technical staff will notify their designated counterparts within 24 hours by telephone or e-mail in the event of a disaster or other contingency that disrupts the normal operation of one or both of the connected systems. Material Changes to System Configuration: Planned technical changes to the system that will affect data exchange will be reported to the other party’s technical staff at least one (1) month before such changes are implemented. The initiating party agrees to conduct a risk agreement based on the new system architecture to ensure the changes will not introduce significant risks to the other party. If a major change is implemented, the system must undergo recertification and reaccreditation. New Interconnections: The initiating party will notify the other party at least one (1) month before it connects its IT system with any other IT system external to its system boundaries, including systems that are owned and operated by third parties, such as contractors or vendors.
Disasters and Other Contingencies. Both parties shall notify immediately their designated counterparts as defined in the information system contingency plan in the event of a disaster or other contingency that disrupts the normal operation of one or both of the connected networks.
Disasters and Other Contingencies. Technical staff will immediately notify their designated counterparts by telephone or e-mail in the event of a disaster or other contingency that disrupts the normal operation of one or both of the connected systems. Material Changes to System Configuration: Planned changes (i.e. changes not associated with routine maintenance) to the system architecture that impact or have the potential to impact services will be reported to technical staff before such changes are implemented. Such changes must be agreed upon by both parties, and documented. {ETS Contractor} must notify the E-Gov Travel PMO of such changes. These changes must be reviewed by the E-Gov Travel PMO ISSO. Changes that are deemed to require a risk assessment or re-authorization of the system must be approved by the GSA AO before being implemented. Appropriate documents must be updated when applicable, including but not limited to, Configuration Management Plan, System Security Plan, Risk Assessment, and the Continuity of Operations Plan. The system must maintain a valid and current Authority to Operate (ATO) prior to establishing a connection and through the duration of this agreement. Personnel Changes: {ETS Contractor} and {Agency} agree to provide notification of the separation or long-term absence of their respective system owner or technical lead. In addition, both parties will provide notification of any changes in “point of contact” information. Both {ETS Contractor} and {Agency} will provide notification of changes to user profiles, including users who resign or change job responsibilities. The technical details of the interconnection will be documented in an Interconnection Security Agreement (ISA). The parties agree to work together to develop the ISA, which must be signed by {ETS Contractor}, {Agency (ies)}, an E-Gov Travel PMO Senior Official, and the GSA AO. Any proposed changes to either system or the interconnecting medium will be reviewed and evaluated to determine the potential impact on the interconnection. The ISA will be renegotiated before changes are implemented. At a minimum, signatories to the ISA shall be a senior company official for {ETS Contractor}, the AO or other senior official for {Agency (ies)}, and the GSA AO. The functional and technical details of application interoperability will be documented in an Integration Agreement (IA). {ETS Contractor} and the {Agency} agree to work together to develop the IA. Proposed changes to application interoperability will be ...
