Key Assumptions. Number of patients to be screened 300
Key Assumptions. IBM's estimates to perform the Statement of Work, are based on the following key assumptions. Deviations that arise during the proposed project will be managed through the procedure described in the Project Change Control Procedure section of the Procedures Manual.
Key Assumptions. The 51st State Responsibilities and Charges within this Transaction Document are based on the Key Assumptions below:
1. The server architecture contains single points of failure.
2. No growth is assumed. 51st State will utilize incremental ordering and/or Project Change Requests for pricing new and additional capacity.
3. The server environment will be hardened (e.g. operating system).
4. Commercially supported levels of software will be maintained.
5. Unix root and NT administrative access is controlled by 51st State and is not available to you. Within the limitations of the operating system 51st State will however, establish access to a limited set of privileged commands as mutually agreed upon.
6. Access for you to any systems level commends such as shutdown, reboot, and kill is not provided as it may affect the rest of our server environment. Physical machine shutdown and re-initialization will be performed by 51st State.
7. 51st State will retain execution of all system level maintenance, privileged, and administrative commands.
8. 51st State will not share administrative control of the firewall, if any are specified in Attachment 1, with you.
Key Assumptions. The Cordexa Responsibilities and Charges within this Transaction Document are based on the Key Assumptions below:
1. The server architecture contains single points of failure.
2. No growth is assumed. Cordexa will utilize incremental ordering and/or Project Change Requests for pricing new and additional capacity.
3. The server environment will be hardened (e.g. operating system).
4. Commercially supported levels of software will be maintained.
5. Unix root and NT administrative access is controlled by Cordexa and is not available to you. Within the limitations of the operating system Cordexa will however, establish access to a limited set of privileged commands as mutually agreed upon.
6. Access for you to any systems level commends such as shutdown, reboot, and kill is not provided as it may affect the rest of our server environment. Physical machine shutdown and re-initialization will be performed by Cordexa.
7. Cordexa will retain execution of all system level maintenance, privileged, and administrative commands.
8. Cordexa will not share administrative control of the firewall, if any are specified in Attachment 1, with you.
Key Assumptions. The following are key assumptions on which the Fees in this Schedule are based: • Pricing assumes software listed in Attachment L to the Agreement. Additional software requirements will incur additional charges if discovered after the Effective Date. • ACS will be allowed to install and execute SOFT AUDIT to validate software inventory. • Symetra will retain responsibility for copying Symetra Data at the Xxxxxxx data center from both physical tape and the VSM to ACS VTS and physical drives temporarily installed at the RDC for migration purposes. • Safeco ACF2 security database with Symetra Data will be provided to ACS for migration purposes. • ACS will be allowed to use full system lift methodology to perform the transition from the Safeco data center to the ACS data center. • Channel and DASD requirements for migration purposes at Safeco data center are retained expenses. • Assumes Symetra data will be segregated by DASD volumes to support full volume dumps. • Safeco and Symetra will provide necessary IT configuration and architectural information in ACS-requested format required to establish the new Symetra IT Table of Contents Symetra Life Insurance Company (Symetra) Schedule 3—Fees infrastructure, thus simplifying configuration of new enterprise equipment and environment. • Pricing for hot site includes 300 MIPS, 1.2GB DASD, one hundred twenty (120) shared servers, one (1) email retention server, disaster recovery analyst travel and seventy-two (72) hours annual test time. • Processor utilization is defined as physical machine utilization taken from the SMF type-70 records as reported by IBM’s “RMF CPU Summary Report”. SMF records are recorded on a fifteen (15)-minute interval (ninety-six (96) intervals each day) and report the average processor utilization during the interval. • Baseline configuration is defined as an IBM Z890 system configured for 410 MIPS offered capacity. [***] Dollars ($[***]) monthly fee for twelve (12) months post transition that will serve as ‘term insurance’ for capability to increase to 489 MIPS with option to renew term insurance annually. Upon direction by Symetra to discontinue the 489 MIP option, ACS will reduce recurring xxxxxxxx by [***] Dollars ($[***]) per month. • To increase mainframe capacity to a 489 MIP Mainframe processor, a High-Utilization-Week is defined as five (5) consecutive non-holiday weekdays (Monday through Friday) with average CPU utilization of seventy percent (70%) or higher of the Baseline configur...
Key Assumptions. This description of Services and WildCard's pricing to perform the Services are based on the following key assumptions. Deviation from these assumptions may require an adjustment to price, the solution architectural description, the proposed implementation plan, the service standards, and the description of Services. -------------------------------------------------------------------------------- Program Name UGT Card -------------------------------------------------------------------------------- Program Anticipated Live Date June 2003 -------------------------------------------------------------------------------- Initial Card Stock Order -------------------------------------------------------------------------------- Card/Account Branding Novus/Discover on the back of Cards -------------------------------------------------------------------------------- Card/Account Type - Some are Non-Reloadable, Others are Reloadble -------------------------------------------------------------------------------- Card/Virtual Account Acceptance Only Authorized as Select Merchants -------------------------------------------------------------------------------- Card Fulfillment TBD - Oberthur will Manufacture Cards -------------------------------------------------------------------------------- PIN Notification Method. No PIN -------------------------------------------------------------------------------- Card Account Design Physical, Custom Cards -------------------------------------------------------------------------------- Card Accounts Issued During Year One 250,000 -------------------------------------------------------------------------------- Card Accounts Issued During Year Two 500,000 -------------------------------------------------------------------------------- Card Accounts Issued During Year Three 1,000,000 -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Card Account Ordering Method Written Request to WildCard -------------------------------------------------------------------------------- Value Load Frequency One or Two Times as Configured -------------------------------------------------------------------------------- Value Load Source EFT from Client -------------------------------------------------------------------------------- Value Load Method Pre-Determined by Client ----------------------------------------------------------------------...
Key Assumptions. As of the Effective Date, the following items shall be deemed Key Assumptions which were used to prepare the initial Development Plan, the Regulatory Plan and the Commercialization Plan and associated Payment Schedule agreed upon by the Parties: • The budget and associated Payment Schedule are estimates based on activities that are currently planned in the long term for support clinical trials has been provided and are subject to change based on the assumptions listed below and may be modified in the future as the scope of the project becomes more fully defined. Abbott and Epizyme will agree upon modification of the scope and budget of long-term activities according to the terms of this agreement. Confidential Materials omitted and filed separately with the Securities and Exchange Commission. A total of three pages were omitted. [**]. EXHIBIT C REGULATORY PLAN Epizyme and Abbott will actively cooperate in the regulatory process for the development and global regulatory registration of the Diagnostic Test. The regulatory process includes the development of regulatory strategy, the sharing of regulatory information and data and the submission and liaison with global Regulatory Authorities. Abbott will serve as the formal sponsor of any submissions to global Regulatory Authorities that pertain to the Diagnostic Test, and therefore will be ultimately responsible for the submission of such required documentation per the jointly agreed timelines; provided, however, that the preparation, including strategy, for such submissions will be done in cooperation and consultation with Epizyme and Epizyme shall have the right to attend and participate in all meetings between Abbott and Regulatory Authorities relating to the co-development of the Diagnostic Test. Activities included in the regulatory process that are subject to this regulatory plan include the following: • Routine interactions of Abbott and Epizyme regulatory representatives to share regulatory information relevant to the agreed strategy for development and registration of the Diagnostic Test. • Abbott will inform Epizyme about any inspections from Regulatory Authorities related to the Diagnostic Test and will provide reports of any findings to Epizyme. • [**]. • [**]. • [**]. • Epizyme and Abbott will jointly develop a timeline and priority list for regulatory submissions. The timeline will include submission dates and anticipated approval dates for both the Diagnostic Test and the Epizyme Product. As a p...
Key Assumptions. Client will manage all communications with investors upon introduction by Consultant or regarding any investment in the Company, with Consultant assisting as requested with marketing and public relations guidance.
Key Assumptions. 1.2.1. For the purpose of this Contract:
1.2.1.1. PCS charge is defined as the charge from the Provider to the Commissioner that is a result of the agreed financial contract for activity as outlined in each individual Operational Service Level Agreement (SLA)
Key Assumptions. A. All work performed under this Agreement shall be done at SRC’s offices in Center Valley, PA, except as may be determined by SRC as required to complete the work outlined in all SOWs attached to this Agreement.
B. The relationship of each of the parties to the other party shall be that of an independent contractor, and nothing contained herein or in any SOW shall be deemed or construed to create any kind of joint venture, partnership, employment, agency, or other relationship between the parties for any purpose.
C. Neither party shall have the authority to bind, represent or commit the other party in any way and neither party shall have the authority to assume or create any obligation or responsibility, express or implied, on behalf of, or in the name of, the other party or to enter contracts on behalf of the other party hereto.
D. CLIENT shall be responsible for providing personnel who will become familiar with the use and operation of the Deliverables. Unless hosted by SRC, this will include all the activities associated with maintenance (backups, security, etc.) of the application.
E. CLIENT shall be responsible for developing whatever documentation may be necessary to serve its internal users and customers, unless explicitly specified in the Project Plan or any SOWs to this Agreement. SRC shall provide information, support and assistance as requested by CLIENT during the project regarding the use and operation of the Deliverables.
F. No hardware or software shall be provided by SRC unless specified herein or in any SOWs to this Agreement. CLIENT, with SRC’s assistance, shall acquire any required hardware and software in a timely manner.
