Assumptions and Constraints Sample Clauses

Assumptions and Constraints. <what constraints or assumptions are required to support the CR>

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. b. All data gathering processes will remain internal to the Customer’s network. c. Customer is responsible for ensuring that all technical, organizational, and logistical prerequisites have been met, as provided by Entrust and mutually agreed upon with Customer. d. Customer is responsible for the security and availability of any secure communications channels required for data transfer between its internal network locations. e. Statistical data gathered will be shared with Entrust for process analysis and consulting and for establishing Analytics Production Software performance and effectiveness. f. Specific process statistics received by Entrust during implementation, testing and consulting engagements will be considered “customer confidential” and will not be shared or released outside of the Entrust organization without permission. g. For consulting engagements: i. Unless otherwise agreed to, the analysis period is presumed to be 3 to 4 weeks of data ii. Requests for additional consulting support or custom features / dashboards can be accommodated and may be purchased as a separate line item on an Order or under an additional Order

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. 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. 1. The Contractor is working under the authority and direction of the State to enable countermeasures to be deployed during the COVID 19 health threat which constitutes a public health emergency, said work to include the administration of the program and investigation asneeded to execute necessary countermeasures to combat the threat to the public health. Contractor will perform all services under the State’s instructions, specifications, and requirements with respect to regulatory compliance and the State’s legislative, executive and administrative responsibilities. The foregoing assumption shall not exempt the Contractor from its compliance with any applicable State and Federal statutes or regulations as set forth in theGeneral Provisions – Information Technology, Section 7. 2. With respect to the collection and reporting of data, the parties will work together to define the specific scope of any analytics/reporting services. The Contractor’s scope shall exclude the collection of any data via mobile phones or other devices in the initialrelease. The State may add the need for mobile phone use to the backlog and prioritize the work during grooming. 3. The parties will work together in good faith to determine if general data canbe obtained, through legally permissible means and in compliance with applicable privacy law and policies, to help identify open or closed healthfacilities, stores and/or businesses. 4. The Contractor’s Services will be delivered using the Contractor DeliveryMethodology for Agile Development. 5. The State will access the Contractor’s Delivery Tools (e.g. ACP/AIP) during theTerm of this Agreement, as described more fully below. 6. The State and the State’s subcontractors working on the Project will be sufficiently skilled to participate in and support the approach deployed by the Contractor. Anytraining or additional effort required to address any differences in approach or deficiencies in this regard will be remedied through training and resource sha...

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. 2. No overtime pay shall be authorized for non-standard work hours. 3. Time off for the Contractor’s staff shall be authorized if there is no foreseeable impact to the expected rollout schedule, as determined by the CDCR EIS Network Engineering Manager, or selected representative. 4. The primary work location shall be at the CDCR EIS’s Aerojet facility in Rancho Cordova, California, but may be subject to change upon the CDCR EIS Network Engineering Manager approval. Some remote telework may be available and offered at the discretion of the CDCR. 5. The Contractor must submit a resume for review of all personnel substitutions in advance. The proposed substitute must meet or exceed all mandatory qualifications listed under Section C, Mandatory Qualifications. All Contractor personnel substitutions must be approved by the CDCR EIS Network Engineering Manager. 6. Any modifications to tasks within the SOW of this Agreement will be defined, documented and mutually agreed upon by the Contractor and the CDCR EIS Network Engineering Manager, or selected representative, prior to starting work on the modified task. Modifications outside the original scope of work will require Agreement amendment and control agency approval prior to commencement of work. Modifications are considered to be Unanticipated Tasks and will be listed in detail on Exhibit A-1, Unanticipated Tasks form. 7. The CDCR and the Contractor are mutually obligated to keep open and regular channels of communication in order to ensure the successful execution of this Agreement. Both parties are responsible for communicating any potential problem or issue to the CDCR EIS Network Engineering Manager, or selected representative, and the Contractor, respectively, within 48 business hours of becoming aware of said problem. 8. The Contractor certifies that it has appropriate systems and controls in place to ensure that CDCR funds shall not be used in the performance of this Agreement for the acquisition, operation or maintenance of computer software in violation of copyright laws.

Assumptions and Constraints. 3.1. [List any assumptions or constraints for the project]

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. 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.