SHIELD seamless approach Sample Clauses

SHIELD seamless approach. The SHIELD SPD functionalities will be conceived to be seamlessly introduced in the existing embedded systems. In particular, such functionalities will be embedded in SHIELD SPD modules which will be transparently inserted in each of the previously mentioned layers; transparency means that the insertion of these modules does not entail any modification of the pre-existing algorithms and procedures. Each SPD module will implement a specific set of SHIELD SPD functionalities which can be dynamically enabled/disabled and, in case of activation, properly configured following the decisions of the SHIELD Overlay (see the next issue).
AutoNDA by SimpleDocs

Related to SHIELD seamless approach

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe 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 InterGlobe. 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 InterGlobe (e.g. hairpinning):

  • Integrated Digital Loop Carriers The feeder portion of some loops may be provide by means of Integrated Digital Loop Carrier (IDLC). IDLC provides a fiber optic cable transmission path that travels directly into BellSouth’s central office local switch. Where BellSouth uses IDLC ,if technically feasible and capacity does exist, BST will provide Al-Call with a Designed DS0 UVL by using alternative provisioning techniques including but not limited to such as “hairpinning” and DAC grooming. Alternative provisioning techniques will be provided at no additional cost to Al-Call . Hairpinning involves providing a DS0 signal from an IDLC-served loop to Al-Call ’s collocation equipment by using a dedicated pathway that traverses BellSouth’s central office switch. BellSouth will provide such DS0 signal to Al-Call by establishing a copper cross connect between the BellSouth switch and Al-Call ’s collocation equipment.

  • Crossing Picket Lines The Company will not expect an employee to cross a picket line, including a picket line at a customer site, if to do so would place the employee's life, limb or personal property in jeopardy.

  • ROAD DIMENSIONS Purchaser shall perform road work in accordance with the dimensions shown on the TYPICAL SECTION SHEET and the specifications within this road plan.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Verizon OSS Facilities Any gateways, interfaces, databases, facilities, equipment, software, or systems, used by Verizon to provide Verizon OSS Services to CBB.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • FABRICATION Making up data or results and recording or reporting them.

Time is Money Join Law Insider Premium to draft better contracts faster.