Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.
Format and Content 51.2.1 Unless otherwise specified by CenturyLink, the forecasting forms located on the CenturyLink Wholesale Website will be used by CLEC for the requirements of this Section. 51.2.2 The joint planning process/negotiations should be completed within two (2) months of the initiation of such discussion. 51.2.3 Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 51.2.4 Parties shall meet to review and reconcile the forecasts if forecasts vary significantly. 51.2.5 CLEC shall provide an updated trunk forecast when ordering or requesting additional trunks from CenturyLink anytime after the initial trunk implementation.
Formatted Font: 12
ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.
Physical File Characteristics 7.2.1 The EODUF feed will be distributed to Comcast Phone over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among Comcast Phone’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and Comcast Phone for the purpose of data transmission. Where a dedicated line is required, Comcast Phone will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Comcast Phone will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Comcast Phone. Additionally, all message toll charges associated with the use of the dial circuit by Comcast Phone will be the responsibility of Comcast Phone. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. Version 4Q01 12/01/01 All equipment, including modems and software, that is required on Comcast Phone’s end for the purpose of data transmission will be the responsibility of Comcast Phone.
Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27
Abbreviated Documentation Requirements Compile and submit:
Investment Analysis and Implementation In carrying out its obligations under Section 1 hereof, the Advisor shall: (a) supervise all aspects of the operations of the Funds; (b) obtain and evaluate pertinent information about significant developments and economic, statistical and financial data, domestic, foreign or otherwise, whether affecting the economy generally or the Funds, and whether concerning the individual issuers whose securities are included in the assets of the Funds or the activities in which such issuers engage, or with respect to securities which the Advisor considers desirable for inclusion in the Funds' assets; (c) determine which issuers and securities shall be represented in the Funds' investment portfolios and regularly report thereon to the Board of Trustees; (d) formulate and implement continuing programs for the purchases and sales of the securities of such issuers and regularly report thereon to the Board of Trustees; and (e) take, on behalf of the Trust and the Funds, all actions which appear to the Trust and the Funds necessary to carry into effect such purchase and sale programs and supervisory functions as aforesaid, including but not limited to the placing of orders for the purchase and sale of securities for the Funds.
Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO. b. A description or identification of the statistical sampling software package used by the IRO.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
