System Setup. 7.2.1.1 Issues relating to current PA projects, system setup, business flow process, or the configuration or installation of products. Different products have different levels of configuration. Configuration includes the parameters, data and logic that a consultant adds to an installed product to deliver a solution. These issues will be escalated to your Inside Account Manager who will contact you to discuss Consulting Services assistance. Note: Current PA project issues are managed as part of the project engagement.
System Setup. The tasks in system setup include designing and finalizing the technical specification for the system, defining the processes used in the system, and specifying any requirements for operating the system. For example, a blockchain governing body (the Governing Body in the present document) needs to define the process for incorporating a new consensus node operator. Or, the governing body needs to set the security requirements an entity must meet in order to host a consensus node. The creation of the present document can be viewed as a system setup task. Other setup tasks include defining system roles and responsibilities as well as the mechanism for authorization and revocation of such roles and responsibilities.
System Setup. A schematic representation of the different gas/liquid systems are depicted in Fig.
System Setup. Customer agrees to maintain an adequate staff of persons who are knowledgeable with the systems currently used by Customer to process data. Customer further agrees to cooperate fully with any reasonable requests of Cardinal necessary to complete the deployment and conversion in a timely and efficient manner. Cardinal will provide Customer written network and equipment specifications for proper operation of the Software. Customer is responsible for procuring and installing the appropriate equipment in accordance with Cardinal’s specifications, including cabling and any configuration or telecommunications changes required for communications, to enable Customer’s proper use of the Software as well as remote access to the Software by Cardinal for the remote performance of Maintenance Services.
System Setup. System Setup: The PDR-2000 system parameters are programmed with the System Setup menus. Since many of these settings affect the way the rest of the unit is programmed, it is advised that the System Setup be programmed first. There are nine choices spread over three menus in System Setup. Press the F2 and F3 screens to toggle between the three menus. Figure 3-5. System Setup Menu A Figure 3-6. System Setup Menu B Figure 3-7. System Setup Menu C UNIT IDENTITY is used to program the PDR-2000 Unit ID and to turn the Unit ID feature on/off. Unit ID increases security by requiring receiving units to be programmed to receive Trips on a particular channel and only from a unit with the proper ID number. PASSWORD allows the unit’s password to be changed. SEND TRIP MANUALLY is a feature that can be used to initiate Trips on any or all channels for a specified period of time. WARNING: this feature can result in a Trip being output on the receiving end of the channel(s) depending on receive logic. PACKET FORWARDING is a feature that when turned on instructs the PDR-2000 to retransmit any packets containing Trip and/or Guard commands. Packet Forwarding allows PDR-2000s to be strung together and can also be used as redundant communication paths in a loop configuration. DATE/TIME SET is the manual internal clock setup for the sequence of events recorder. This is used to enter the year when first powering on the unit when an IRIG-B input is used. When an IRIG-B input is not used, this is used to set the internal clock for time and date. ALARM SETUP is used to set the programmable status relays and change the default time delays on the Alarm, Block, LOC1, and LOC2 Relays. This section is also used to change the different available optional Trip Cut Out switches. These options are either a separate Cut Out Switch module or an integrated switch on the Trip Out module. Both these options have different functionality. COM SETTINGS allows the user to turn On or Off the Com ports. Using two Com ports allows for the use of Packet Forwarding and schemes using strings, loops, and three terminal applications. This section also includes the settings for the synchronous clock source. AUTO PING TEST is used to set up the automatic testing to another unit. The test confirms proper communications and channel delay between two units. See Section 6, System Tests, for more information about Ping test options and other testing methods. Programming a status relay for Ping test fail is perform...
System Setup. A. UNIT ID NUMBER
I. Every PDR-2000 is assigned a Unit ID number whether or not the Unit ID feature is used. The current Unit ID number assigned to the unit can be found in the top left corner of the Default display. It is important that no unit be assigned number 00. The unit will not operate correctly with a Unit ID number 00.
II. To enter a new Unit ID number, enter a two digit number from 01 to 99 (01 to 03 for units equipped with an Audio Communications module) and press F1 (OK). To exit without changing the number, press F4 (Exit).
III. To turn the Unit ID feature On/Off press 1 then F1 (OK) to enter the Unit ID menu again. The * will show if the Unit ID is currently On or Off. To change this setting press 1 then F1 (OK). The next menu offers the On/Off choice. Again the * shows the current setting. Press 1 for On and 2 for Off then press F1 (OK).
IV. Press F4 (Exit) to return to the System Settings menu.
B. PASSWORD
I. Press 2 and F1 (OK) to enter the Password menu.
II. The current password is displayed. Enter a new 4 digit number (do not use Function keys) for the password and press F1 (OK) to change the password. Repeat the number to confirm and press F1 (OK). Press F3 (Clr) to erase an entry on the display. Press F4 (Exit) to exit without making a change to the password.
System Setup. Given security parameter 1k, the KGCs generates two groups G1, G2, and an admissible bilinear map eˆ : G1 × G1 −→ G2, where G1 denotes a cyclic additive group of prime order q and G2 is a multiplicative group of the same order. The KGCs chooses a generator P of G1 and publishes the system parameters params = {G1, G2, eˆ, P, H1, H2, H3}, here H1 : {0, 1}∗ → Z∗, H2 : G2 → Z∗, H3 : Z∗ × Z∗ → Z∗ are cryptographic hash own subgroup key. Thus, when a member joins or leaves functions. the communication group, it joins or leaves only its lo- cal subgroup. As a result, only the local subgroup com- munication key needs to be refreshed and the scalability problem is greatly mitigated. We use a ’group’ of key generation centers (KGCs) to share the overall key gener- ation and distribution workload. In our scheme the task The basic idea of our scheme is the usage of an iden- tity tree, where each node in the tree has an identity. The leaf node’s identity is corresponding to a user’s iden- tity and the interior node’s identity is generated from it’s children’s identity. Figure 4 shows an example of identity tree. A node in the identity tree is also associate with a sv)−1P and the node N 1’s private key P 1 = (Q1 +sω)−1P
System Setup. The system parameters (G1, G2, e, P, H1, H2) are generated and published, where G1 is an additive cyclic elliptic curve group generated by P with a prime order q, G2 is a multiplicative group with the same order q, e: G1╳G1 →G2 is an bilinear map, and H1: G1 → Zq* , H2: G2 → Zq* are the hash functions. The nodes of the quad key tree adopted in our scheme can be classified into three roles. The root node is associated with the shared group key which can be computed by all the members in the group. The key node located at the internal node is associated with two or three keys depending on the number of its sibling nodes and its position. When the number of sibling nodes is smaller than four, there will be two keys: one is the blinded key for the group that goes public, and the other is the key generation key which can be computed by all the members in the subtree rooted at this key node. For a node with four child nodes, a union blinded key is assigned to its rightmost child node additionally. The member node represents each group member as a leaf node. The keys that come with the member nodes are similar to those of the key node except that the key generation key is randomly chosen from Zq*. Figure 1 shows an example of the key tree. Table 1 summarizes the notations used in the proposed scheme.
System Setup. × →
1) Bilinear: eˆ : G1 × G1 → G2 is bilinear if eˆ(aP, bQ) = eˆ(P, Q)ab for all P, Q ∈ G1 and all a, b ∈ Z. Given P, aP, bP, cP for some a, b, c Z∗q , to compute W = eˆ(P, P )abc G2. A number of notations used in the report are listed in the following table: Ui The ith user Ei( ) ID-based encryption using Ui’s identity as the public key EK ( ) Symmetric encryption with K Nymi Pseudonym for user Ui ri Random number selected by Ui SIGi Signature computed over the corresponding message by Ui
h A hash function mapping from G2 G1 0, 1 k, where k is the security parameter.
System Setup. Basically, the system setup phase is similar to that of Boneh and Franklin’s work. How- ever, in our system, there are total n different PKGs, which do not share common system parameters. Therefore, each PKG must configure its parameters as follows: – Each PKGi chooses its basic system parameter: (G(i), G(i), e(i)), where G(i) is an additive group of order q(i), G(i) is a multiplicative group of order q(i), and e(i) is admissible bilinear map between G(i) and G(i).
