Initial Setup. Jurisdiction shall furnish the following items in order to use the SUTS System:
1) Jurisdiction Depository Information: Jurisdiction will provide bank deposit information (routing & account number) to CDOR’s appropriate Vendors within 5 days of signing this Agreement. This information will be utilized for the deposits of taxes, penalties, and interest from the SUTS System. It is the responsibility of Jurisdiction to provide updated depository information should this account need to be changed at any point in time.
Initial Setup. The Agency will provide assistance to ICOE staff during the initial setup of the services. These activities include but are not limited to:
i. Making configuration changes to the Agency’s firewall, email and directory system as noted on Exhibit 1.
ii. Provide ICOE with a working email account for testing purposes.
iii. Provide a user account to perform Active Directory end-user validation (LDAP).
iv. Coordinate DNS changes to include adding or modifying records (A, CNAME, MX) to the public DNS table to accommodate the services under this Agreement.
Initial Setup. Verily will provide County personnel with: (i) the Playbook, (ii) training on the Platform, including the scheduling and booking system required for County personnel to input schedule and test availability at the site, and (iii) either a recommendation for requisition and label printing hardware or a Verily-provided requisition and label printing hardware, at Verily’s option. Each County will be responsible for establishing appropriate IT and internet infrastructure.
Initial Setup. Using the MK-312BT for the first time is very simple. Just follow these easy steps:
1. Connect the supplied AC Adapter to the VDC input jack when the battery needs charging. The MK-312BT may be used while charging.
2. Make sure the unit is OFF before connecting the desired accessories to the output jacks (see: 5 • Connections). Both plugs of each leadwire must be connected to an electrode surface to form a complete circuit for current to flow. It’s advisable for e-stim beginners to keep all connections below the waist and follow the directions supplied with your accessories.
3. Turn both Output Level controls all the way down (to the left).
4. Pull the power switch toggle handle OUT while flipping UP to turn the unit ON. This safety switch prevents accidental powering of the unit.
5. Use the grey NEXT [→] and PREVIOUS [←] buttons to select the desired mode (see 9 • Modes). The name of each mode is displayed on the LCD.
6. Set the Level and MultiAdjust controls to produce the desired stimulation. (See 6 • Controls).
Initial Setup. Before turning on your computer, plug the unit into a power outlet and make sure to connect all accessories. For laptops, install the battery (make sure the battery is properly aligned with the guides to avoid damage to the pins) and for desktops, connect the mouse, keyboard and monitor. Only press the power button once after all accessories are connected. Let the computer completely load to the Windows setup screen before turning off. Acer: Start>All Programs>Acer System>User Guide eMachine: Start>All Programs>eMachines>eMachine Documentation Gateway: Start>All Programs>Gateway Documentation Acer: Start>All Programs>Acer>Acer Recovery Management eMachine: Start>All Programs>eMachines>eMachines Recovery Management Gateway: Start>All Programs>Gateway>Gateway Recovery Management
Initial Setup. The Supplier will handle the initial setup of the Control Map platform, ensuring it is tailored to the Client's specific compliance requirements. This setup includes configuring the platform, integrating it with the Client's systems, and providing necessary training to Client personnel.
Initial Setup. Initial setup consists of:
a. Installation of the git and [drush or wp-cli] maintenance tools as needed; [web/ CiviCRM only]
b. a security reset to ensure that only authorized users have access to the CMS and server (e.g. removing public keys, resetting passwords, disabling root access);
c. setup of a development site (see “Development Site” below); [web/ CiviCRM only] d. an initial round of Backdrop updates (see “Backdrop Updates” below); [Backdrop only]
e. an initial round of Drupal updates (see “Drupal Updates” below); [Drupal only]
f. an initial round of WordPress updates (see “WordPress Updates” below);
g. Audit and documentation of any existing CMS custom code and patches; [web/ CiviCRM only] h. an initial round of CiviCRM updates (see “CiviCRM Updates” below); [CiviCRM only]
i. Review and adjustment of core CiviCRM settings for mail, addressing, geocoding, payment processor, PHP, user permissions, and Backdrop/Drupal/Wordpress integration; [CiviCRM only]
j. Audit and documentation of any existing CiviCRM custom code and/or extensions;
k. Restructuring and standardization of module directories for easier automation and administration; [Backdrop and Drupal only] l. an initial round of log review (see “Log Review” below); [WordPress only]
m. Creation of a Debian 10 Linode VPS with appropriate block storage; [Nextcloud only]
n. Customization of VPS for optimal docker web server usage; [Nextcloud only]
o. Installation of Nextcloud docker container; [Nextcloud only]
p. Creation of Client Nextcloud user accounts; [Nextcloud only]
q. monitoring setup (see “Monitoring” below); and
r. setup and configuration of backups (see “Backups” below).
Initial Setup. Verily will provide County personnel with: (i) the Playbook and (ii) training on the Platform as necessary for County and/or Site to support testing operations and perform the activities required under this Agreement, including the scheduling and booking system required for County personnel to input schedule and test availability at the site.
Initial Setup. Customer shall furnish the following items in order to use the functionality provided by MR:
Initial Setup. The performance of the system with the initial setup is summarized in Table 1. False calls were the most common type of detection error, with an accumulated frequency of about 0.55% of the total number of activations generated by the radar units. Most of the false calls were created by bicycles and pedestrians, and the remaining errors were due to calls generated when no objects were in the crossing or when the gates were moving. A relatively low number of vehicles were missed by one of the two radar units (0.07%), but there were no cases in which both radar units missed the same vehicle. This finding indicates that the redundancy provided by the two radar units prevented missed vehicles for the system as a whole in the selected datasets. Similarly, no stuck-on calls or dropped calls were found. Recall that the total number of activations from loop and radar detectors may not be the same even if no errors are reported, or when subtracting false calls and adding missed calls to the activations by the radars. As explained in the Methodology section, closely-spaced vehicles and turning movements may cause a single call in one of the systems, but two separate calls in the other without generating any type of error. Therefore, differences in the total number of activations between the two systems are dependent on traffic patterns for the specific days analyzed. NORMAL WEATHER - Initial Setup (Fall 2012) Date Activations Trains False calls (including bicycles and pedestrians that radars detected, but loops did not) Missed Calls Stuck-on Calls Not detected by subject radar in any lane Not detected by any radar in any lane Wavetronix Loop Bicycles Pedestrians No object Gates Moving TOTAL Oct 9, 2012 (24hrs) 7956 7440 129 6 8 19 8 41 8 0 0 Oct 15, 2012 (24hrs) 7219 6832 121 8 9 6 2 25 3 0 0 * A total of 7 activations due to motorcycles were generated by radar. All cases were small scooter-type motorcycles riding inside the traveled lane not detected by the loops. The total number of motorcycles using the crossing and detected by the two systems is unknown. In addition to the summary by day, results are also presented by radar unit and lane in Table 2. As shown in Table 2, the two radar units generated a similar number of calls caused by bicycles, pedestrian, and motorcycles. However, Radar1–Lane1 was slightly more prone to false calls when no vehicles were present or the gates were moving, whereas missed calls were more likely for Radar 2 in both lanes. Table 2. An...