Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process. 6.2 <<customer_name>> shall submit any BFR/NBR in writing to <<customer_name>>’s Account Manager. The BFR/NBR shall specifically identify the requested service date, technical requirements, space requirements and/or such specifications that clearly define the request such that BellSouth has sufficient information to analyze and prepare a response. The BFR/NBR also shall include <<customer_name>>’s designation of the request as being (i) pursuant to the Telecommunications Act of 1996 or (ii) pursuant to the needs of the business.
Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.
Third Party Request Should a Third Party, including, but not limited to law enforcement, former employees of the LEA, current employees of the LEA, and government entities, contact Provider with a request for data held by the Provider pursuant to the Services, the Provider shall redirect the Third Party to request the data directly from the LEA and shall cooperate with the LEA to collect the required information. Provider shall notify the LEA in advance of a compelled disclosure to a Third Party, unless legally prohibited. The Provider will not use, disclose, compile, transfer, sell the Student Data and/or any portion thereof to any third party or other entity or allow any other third party or other entity to use, disclose, compile, transfer or sell the Student Data and/or any portion thereof, without the express written consent of the LEA or without a court order or lawfully issued subpoena. Student Data shall not constitute that information that has been anonymized or de-identified, or anonymous usage data regarding a student’s use of Provider’s services.
Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)
Procedures for LNP Request The Parties shall provide for the requesting of End Office LNP capability on a reciprocal basis through a written request. The Parties acknowledge that Verizon has deployed LNP throughout its network in compliance with FCC 96-286 and other applicable FCC Regulations. 15.4.1 If Party B desires to have LNP capability deployed in an End Office of Party A, which is not currently capable, Party B shall issue a LNP request to Party A. Party A will respond to the Party B, within ten (10) days of receipt of the request, with a date for which LNP will be available in the requested End Office. Party A shall proceed to provide for LNP in compliance with the procedures and timelines set forth in FCC 00-000, Xxxxxxxxx 80, and FCC 97-74, Paragraphs 65 through 67. 15.4.2 The Parties acknowledge that each can determine the LNP-capable End Offices of the other through the Local Exchange Routing Guide (LERG). In addition, the Parties shall make information available upon request showing their respective LNP-capable End Offices, as set forth in this Section 15.4.
Billing and Payment Procedure for Forest Products Delivered The State will compute and forward to Purchaser a billing statement of charges for forest products delivered during the billing period at the delivered rate shown in P- 028.2 clause. After receipt of the billing statement, Purchaser’s payment must be received by the Department of Natural Resources on or before the due date shown on the billing statement. Purchaser agrees to make payment, payable to the Department of Natural Resources. Failure to pay on time for forest products delivered is considered a breach of contract. Included with the billing statement will be a summary report for the billing period compiled by the State or their log and load reporting service. The State will adjust final xxxxxxxx to account for any State approved payment reductions. Advance payments made under P-045 or P-045.2 remaining on account above the value for the charges shall be returned to Purchaser within 30 days following the final report of charges. Refunds not made within the 30 day period will accrue interest at the interest rate, as established by WAC 000-000-000, computed on a daily basis until paid.
Stop Payment Order Request Any owner may request a stop payment order on any check or draft drawn on the owner’s account. To be binding, the order must be in writing, dated and signed, and must accurately describe the check or draft, including the exact account number, the check or draft number, and the exact amount of the check or draft. This exact information is necessary for the Credit Union’s computer to identify the check or draft. If we receive incorrect or incomplete information, we will not be responsible for failing to stop payment on the check or draft. In addition, we must receive sufficient advance notice of the stop payment order to allow us a reasonable opportunity to act on it. If we recredit your account after paying a check or draft over a valid and timely stop payment order, you agree to sign a statement describing the dispute with the payee, to assign to us all of your rights against the payee or other holders of the check or draft, and to assist us in any legal action.
Contract Task Order A- E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The County Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with County Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by County Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, County Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned County Project Manager within the timeframe indicated in the CTO or as directed by County Project Management staff.
Data Subject Requests To the extent legally permitted, Okta shall promptly notify Customer if Okta receives a request from a Data Subject to exercise the Data Subject's right of access, right to rectification, restriction of Processing, erasure (“right to be forgotten”), data portability, object to the Processing, or its right not to be subject to an automated individual decision making (“Data Subject Request”). Factoring into account the nature of the Processing, Okta shall assist Customer by appropriate organizational and technical measures, insofar as this is possible, for the fulfilment of Customer’s obligation to respond to a Data Subject Request under Data Protection Laws and Regulations. In addition, to the extent Customer, in its use of the Service, does not have the ability to address a Data Subject Request, Okta shall, upon Customer’s request, provide commercially- reasonable efforts to assist Customer in responding to such Data Subject Request, to the extent that Okta is legally authorized to do so, and the response to such Data Subject Request is required under Data Protection Laws and Regulations. To the extent legally permitted, Customer shall be responsible for any costs arising from Okta’s provision of such assistance.
Proposed Goods and Services Proposed Goods and Services pdf D/M/WBE Certification OPTIONAL No response Warranty No response