Assumptions and Constraints. <what constraints or assumptions are required to support the CR> DATE RESPONSE DUE FROM RECEIVING PARTNER: ESTIMATED DATE TO REVIEW WITH CORE TEAM: <date that the CR will be reviewed with Core Team> CR DISPOSITION: <Go/ No Go decision and why> AUTHORIZED SIGNATURES: Signature Signature Date Date Name Name American Airlines, Inc. and Aircell LLC Confidential and Proprietary Information Exhibit D-2 EXHIBIT E PACKING LIST (for 767-200) [***] American Airlines, Inc. and Aircell LLC Confidential and Proprietary Information EXHIBIT F INSTALLATION SCHEDULE, TRAINING AND SUPPORT FOR TRANSCON LAUA/CH INSTALLATION SCHEDULE See Exhibit A for the agreed-upon Installation Schedule for the 767-200 Fleet.
Assumptions and Constraints. This STANAG was developed using the following assumptions and constraints: • Elements of the system (e.g., Core UAV Control System (CUCS), Data Link Interface (DLI) Vehicle Specific Module (VSM), Command and Control Interface (CCI), Command and Control Interface Specific Module (CCISM),) are not required to be co-located. • The STANAG requirements have been developed independent of national CONOPS. Thus it is not the intent to define or imply specific CONOPS in this STANAG. • This STANAG addresses the interface with Airspace Management Authority required to coordinate the operation of UAVs in a controlled air space. It does not address or imply the overall requirements and required certifications that may be necessary to operate UAVs in controlled air space. • Critical real/near real time requirements of UAV and payload control should be allocated to the VSM function. • The UAV system scalability is independent of the contents of the STANAG.
Assumptions and Constraints. The State understands the Contractor’s performance is dependent on the State’s timely and complete performance of those tasks and responsibilities specified in this SOW (“State Responsibilities”). In addition, the State understands the Contractor agreed to perform the Services based on the assumptions listed below (the “Assumptions”). In addition to any other responsibilities or duties described in this SOW, set forth below are the State Responsibilities and Assumptions for the Project.
Assumptions and Constraints a. All data collected by the Product Analytics Software will be anonymous statistical production information only. The Software is not designed to collect or store any private customer data or sensitive card holder information as defined by PCI guidelines.
Assumptions and Constraints. The following statements of assumptions and constraints are relevant to this BPA PWS: DHA will utilize Information Technology Service Management (ITSM) which covers incident management, problem management, change management, configuration management, knowledge management, service catalog management, and request management capabilities. DHA will use ServiceNow’s ITSM suite of products to operate and support its infrastructure transition and sustainment according to industry best practices, to include: Information Technology Infrastructure Library (ITIL), Agile, Scrum, and Development and Operations (DevOps) based processes. DHA will provide an ITSM software solution and licenses for use to the EITSI and other service providers. DHA has acquired ServiceNow as its ITSM tool. Other tools are referenced in 5.2.7 Service Management Systems. DHA will leverage operational and industry best practices for service delivery and support, including Enterprise ITIL-based practices, such as problem management for recording, managing and eliminating recurrent or chronic failures, configuration baseline management and change control for recording and executing infrastructure changes identified as necessary to meet operational objectives; all while minimizing adverse risks to overall service availability and component and service capacity, demand management, and availability management. DHA expects to move to the ITIL 4 framework as part of establishing the EITS Environment, and thereby evolve from the current processes that conform to ITILv3 or do not follow ITIL practices at all. DHA will continue to deliver shared services equal to or better than existing capabilities and service expectations. All IT infrastructures will have a valid Life Cycle Management Plan (LCMP) in adherence to the corresponding Authority to Operate (ATO). Once D2D-PEO is complete, the Enterprise will be on a standardized transport via Multiprotocol Label Switching cloud network known as the Medical Community of Interest (Med-COI) and operating on the Medical Joint Active Directory (mJAD). Med-COI is the common network transport for MHS services. mJAD provides single common authentication and centralized identity management framework for the MHS. DHA will leverage DoD Enterprise Cloud Environment, a multi-cloud, multi-vendor ecosystem of cloud services. Traffic to and from these multi-cloud environments into Med-COI must ingress and egress through Med-COI Cloud Access Points (CAPs) ...
Assumptions and Constraints. 3.1. [List any assumptions or constraints for the project]
Assumptions and Constraints. 1. The Consultant’s work hours must be consistent with CDCR/CCHCS’s key staff work hours on-site. CDCR/CCHCS normal core business hours are 7 A.M. to 6 P.M., PST, Monday through Friday, except for State holidays and State mandated furlough days. Working hours may be modified as needed.
Assumptions and Constraints. 1. The Contractor/Consultant work hours must be consistent with the CDCR’s key staff on- site. The CDCR normal business hours are 8 A.M. to 5 P.M., Pacific Standard Time (PST), Monday through Friday, except for State holidays. Maintenance that may disrupt connectivity must occur during non-business hours. It is expected that the Contractor shall be available during implementations that are scheduled within these windows.
Assumptions and Constraints. 16.1. A SOW will proceed with the following identified assumptions. Additional assumptions and constraints may be listed in a SOW. Any further assumptions or constraints that are identified as the SOW progresses will be subject to a change control and an impact analysis, which may affect the cost and timescales of the SOW. Where these changes were not reasonably identifiable by InfoTrust then the customer will bear any costs. InfoTrust requires that:
Assumptions and Constraints. 3.1.10 Risk Mitigation Plan for identified Obstacles and Risks.
