Arctic MFC (ARC MFC Clause Samples

Arctic MFC (ARC MFC. In situ observations are needed in ARC MFC for calibrating the models, validating model products and reducing errors in the model fields via data assimilation. A description of general requirements on in situ observations for Arctic forecast and reanalysis is given in Table 2.3. 1. There are in total 10 different applications, ranging from offline Calibration/Validation (Cal/Val) of physical ocean products to offline data assimilation in biogeochemical reanalysis. All activities need in situ data with Arctic coverage. For Cal/Val purpose, a limited number of stations with high frequency sampling is an ideal solution. For generating Quality Identification Document (QUID) report and historic reanalysis, only offline observations are needed. For Near Real Time (NRT) analysis and forecast product validation, NRT data are needed. Applications in interim scales, i.e., 1-12 months before present, observations have to be available in corresponding time. Considering scientific and service purposes, priority areas of observations are given to Nordic Seas, Straits and important shipping areas e.g. Cape Farewell, Kara Sea and Northern Sea routes. For biogeochemical product validation, coastal shelf seas are important monitoring areas. Freshwater inputs are also important for models. Table 2.3.1 General requirements on in situ data for Arctic forecast and reanalysis: PHY – Physics, BGC – Biogeochemical, DA – Data Assimilation, RAN - Reanalysis 3.1. The reduction of the temperature biases is gone 1 year after the assimilation stops. Due to such long temporal impacts of in situ data, even 12 profiles per day in the Arctic Ocean can generate significant positive impacts. Hence 12 T/S profiles per day in the Arctic can be regarded as the minimum spatial resolution required for data assimilation. Figure 2.3.1 All assimilated Temperature (left) and Salinity (right) profiles in the ARC MFC Physical reanalysis in the whole period 1992-2016. Table 2.3.2 Overview of the impact and priority assessment of in situ data in the ARC MFC (▇▇▇▇▇▇▇, 2018). Impact: “Real” = Has been documented. “Ongoing” = is being documented. “Ind.”: Indirect through calibration of remote sensing products. “Science”: Data is used for process studies. “None”: Data not available or insufficient. Priority A = urgent, B= Second priority, C: Not a priority for the time being. (Source: ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, 2018)
View SourceView Similar (2)

Related to Arctic MFC (ARC MFC

  • Reverse ADSL Loops If a CLEC’s ADSL Transmission Unit (including those integrated into DSLAMs) is attached to Sprint’s Network and if an ADSL Copper Loop should start at an outside location, and is looped through a host or remote, and then to the subscriber, the copper plant from the outside location to the Sprint host or remote central office must be a facility dedicated to ADSL transmission only and not part of Sprint’s regular feeder or distribution plant.

  • Unbundled Copper Loop – Non-Designed (UCL-ND 2.4.3.1 The UCL–ND is provisioned as a dedicated 2-wire metallic transmission facility from BellSouth’s Main Distribution Frame (MDF) to a customer’s premises (including the NID). The UCL-ND will be a “dry copper” facility in that it will not have any intervening equipment such as load coils, repeaters, or digital access main lines (DAMLs), and may have up to 6,000 feet of bridged tap between the End User’s premises and the serving wire center. The UCL-ND typically will be 1300 Ohms resistance and in most cases will not exceed 18,000 feet in length, although the UCL-ND will not have a specific length limitation. For Loops less than 18,000 feet and with less than 1300 Ohms resistance, the Loop will provide a voice grade transmission channel suitable for Loop start signaling and the transport of analog voice grade signals. The UCL-ND will not be designed and will not be provisioned with either a DLR or a test point. 2.4.3.2 The UCL-ND facilities may be mechanically assigned using BellSouth’s assignment systems. Therefore, the Loop Makeup (LMU) process is not required to order and provision the UCL-ND. However, CBX One-Stop can request LMU for which additional charges would apply. 2.4.3.3 For an additional charge, BellSouth also will make available Loop Testing so that CBX One-Stop may request further testing on the UCL-ND. Rates for Loop Testing are as set forth in Exhibit A of this Attachment. 2.4.3.4 UCL-ND Loops are not intended to support any particular service and may be utilized by CBX One-Stop to provide a wide-range of telecommunications services as long as those services do not adversely affect BellSouth’s network. The UCL- ND will include a NID at the customer’s location for the purpose of connecting the Loop to the customer’s inside wire. 2.4.3.5 OC will be provided as a chargeable option and may be utilized when the UCL-ND provisioning is associated with the reuse of BellSouth facilities. OC-TS does not apply to this product. 2.4.3.6 CBX One-Stop may use BellSouth’s Unbundled Loop Modification (ULM) offering to remove excessive bridged taps and/or load coils from any copper Loop within the BellSouth network. Therefore, some Loops that would not qualify as UCL-ND could be transformed into Loops that do qualify, using the ULM process.

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters). The UCL-D will be offered in two versions - Short and Long. 2.4.2.2 A short UCL-D (18,000 feet or less) is provisioned according to Resistance Design parameters, may have up to 6,000 feet of bridged tap and will have up to 1300 ohms of resistance. 2.4.2.3 The long UCL-D (beyond 18,000 feet) is provisioned as a dry copper twisted pair longer than 18,000 feet and may have up to 12,000 feet of bridged tap and up to 2800 ohms of resistance. 2.4.2.4 The UCL-D is a designed circuit, is provisioned with a test point, and comes standard with a DLR. OC is a chargeable option for a UCL-D; however, OC is always required on UCLs where a reuse of existing facilities has been requested by Granite. 2.4.2.5 These loops are not intended to support any particular services and may be utilized by Granite to provide a wide-range of telecommunications services so long as those services do not adversely affect BellSouth’s network. This facility will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the loop to the customer’s inside wire. 2.4.2.6 BellSouth will make available the following UCL-Ds:

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.