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 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 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. 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 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. The following assumptions and constrains apply to the beta release of the components: • Only limited algorithms training options are available. The delivery of the full set of analytics functions and respective algorithms options is planned for release 1.00, (M18) based upon the needs and feedback received from the BEYOND End-user’s tools.
Assumptions and Constraints. The following assumptions and constrains apply to the beta release of the components: • the implementation of the DEM is based on the anticipated attributes of a dataset, as defined in the preliminary version of BEYOND CIM (see D3.2). Since for a data asset to be discoverable, it shall be ingested to the platform and mapped to the BEYOND CIM concepts, it is anticipated that further modifications might be required to its structure, so as to fulfil all future needs and updates of the model.
Assumptions and Constraints. Any issues or constraints that may affect the cost, time or performance of a task must be identified in this section.
Assumptions and Constraints. To the maximum extent practicable, data made available from CMS quality reporting, interoperability, and value-based purchasing (VBP) programs and their underlying information systems should be primary sources of information for QIOs as defined by Section 1153 of the Social Security Act and performing the functions outlined in Section 1154 of the Social Security Act. Leveraging existing information and resources, including data that have been statutorily mandated to be reported to CMS, will reduce provider burden associated with data collection and reporting while driving evidence-based quality improvement efforts. The Contractor will be onboarded no later than 10 business days after CMS receipt of the intake form to QualityNet IT Services for the Health Care Quality Information Systems (HCQIS) network. The ISG Contract Engagement Lifecycle Standard Operating Procedures can be found here: xxxxx://xxxxxxxxxxxxxx.xxx.xxx/display/ISGCO. Further information on the ISG Contract Engagement onboarding process can be found here: xxxxx://xxxxxxxxxxxxxx.xxx.xxx/display/ISGCO/Access+to+Services. QualityNet IT Services that can be found online here: xxxxx://xxxxxxxxxx.xxxxx.xxx/ This link connects to the latest information on the QualityNet Collaboration Hub Tools and Services, this is a public facing site and any contractor may need to work with these tools and services within our environment. The Contractor’s staff shall be trained on all software and tools required for, but not unique to, this contract. Software and tools required are referenced throughout this PWS. The Contractor shall work cooperatively and collaborate with other external support staff as designated by CMS. CMS expects the Contractor to exhibit a comprehensive understanding of agency healthcare data and agency specific technical standards in order to provide high quality services to CMS. Provide or maintain access to working technologies such as quality measures engine, performance scoring engine, advanced data analytics, and monitoring/reporting tools. Regularly advise the CMS quality users on emerging technologies, tools, applications, and recommendations for improving the integration and implementation of an agency’s legacy platform and related cloud technology ecosystem. The Contractor will provide adequate staff to provide support for project team meetings, design, deployments, help desk, testing, outages, troubleshooting and triaging defects and environment issues, and maintenance weekends....
Assumptions and Constraints. The Sustainability and Phase-Out Plans above are based on the assumption that the functions, structures and systems of a district health system will crystallize by the end of 2003. There is every reason to believe this will be the case, since the DOH is firmly committed to building an integrated, decentralized and equitable local system. Nevertheless, the exact level at which various functions and responsibilities will be located is still unclear. Once the system is fully instituted, some modifications in the sustainability objectives are to be expected. These modifications should not be extensive, however, and MCDI is fully prepared to respond to any changes in the emerging district health system as necessary.
