0.25;\n```\n\n**Inserting Into a Table with Error Logging: Example** The following statements create a raises table in the sample schema hr, create an error logging table using the DBMS_ERRLOG package, and populate the raises table with data from the employees table. One of the inserts violates the check constraint on raises, and that row can be seen in errlog. If more than ten errors had occurred, then the statement would have aborted, rolling back any insertions made:\n\n```sql\nCREATE TABLE raises (emp_id NUMBER, sal NUMBER\n CONSTRAINT check_sal CHECK(sal > 8000));\n```\n\nEXECUTE DBMS_ERRLOG.CREATE_ERROR_LOG('raises', 'errlog');\n\nINSERT INTO raises\n SELECT employee_id, salary*1.1 FROM employees\n WHERE commission_pct > .2\n LOG ERRORS INTO errlog ('my_bad') REJECT LIMIT 10;\n\nSELECT ORA_ERR_MESG$, ORA_ERR_TAG$, emp_id, sal FROM errlog;\n\nORA_ERR_MESG$ ORA_ERR_TAG$ EMP_ID SAL\n---------------------- --------------- ------ -------\nORA-02290: check constraint my_bad 161 7700\n(HR.SYS_C004266) violated\n\n**Inserting into a Remote Database: Example** The following statement inserts a row into the `employees` table owned by the user `hr` on the database accessible by the database link `remote`:\n\n```sql\nINSERT INTO employees@remote\n VALUES (8002, 'Juan', 'Fernandez', 'email@example.com', NULL,\n TO_DATE('04-OCT-1992', 'DD-MON-YYYY'), 'SH_CLERK', 3000,\n NULL, 121, 20);\n```\n\n**Inserting Sequence Values: Example** The following statement inserts a new row containing the next value of the `departments_seq` sequence into the `departments` table:\n\n```sql\nINSERT INTO departments\n VALUES (departments_seq.nextval, 'Entertainment', 162, 1400);\n```\n\n**Inserting Using Bind Variables: Example** The following example returns the values of the inserted rows into output bind variables `:bnd1` and `:bnd2`. The bind variables must first be declared.\n\n```sql\nINSERT INTO employees\n (employee_id, last_name, email, hire_date, job_id, salary)\nVALUES\n (employees_seq.nextval, 'Doe', 'firstname.lastname@example.org',\n SYSDATE, 'SH_CLERK', 2400)\nRETURNING salary*12, job_id INTO :bnd1, :bnd2;\n```\n\n**Inserting into a Substitutable Tables and Columns: Examples** The following example inserts into the `persons` table, which is created in \"Substitutable Table and Column Examples\" on page 16-70. The first statement uses the root type `person_t`. The second insert uses the `employee_t` subtype of `person_t`, and the third insert uses the `part_time_emp_t` subtype of `employee_t`:\n\n```sql\nINSERT INTO persons VALUES (person_t('Bob', 1234));\nINSERT INTO persons VALUES (employee_t('Joe', 32456, 12, 100000));\nINSERT INTO persons VALUES (\n part_time_emp_t('Tim', 5678, 13, 1000, 20));\n```\n\nThe following example inserts into the `books` table, which was created in \"Substitutable Table and Column Examples\" on page 16-70. Notice that specification of the attribute values is identical to that for the substitutable table example:\n\n```sql\nINSERT INTO books VALUES (\n 'An Autobiography', person_t('Bob', 1234));\nINSERT INTO books VALUES (\n 'Business Rules', employee_t('Joe', 3456, 12, 10000));\nINSERT INTO books VALUES (\n```\n\n'Mixing School and Work',\npart_time_emp_t('Tim', 5678, 13, 1000, 20));\n\nYou can extract data from substitutable tables and columns using built-in functions and conditions. For examples, see the functions TREAT on page 5-234 and SYS_TYPEID on page 5-209, and \"IS OF type Condition\" on page 7-25.\n\n**Inserting Using the TO_LOB Function: Example** The following example copies LONG data to a LOB column in the following long_tab table:\n\n```sql\nCREATE TABLE long_tab (pic_id NUMBER, long_pics LONG RAW);\n```\n\nFirst you must create a table with a LOB.\n\n```sql\nCREATE TABLE lob_tab (pic_id NUMBER, lob_pics BLOB);\n```\n\nNext, use an INSERT ... SELECT statement to copy the data in all rows for the LONG column into the newly created LOB column:\n\n```sql\nINSERT INTO lob_tab\n SELECT pic_id, TO_LOB(long_pics) FROM long_tab;\n```\n\nWhen you are confident that the migration has been successful, you can drop the long_pics table. Alternatively, if the table contains other columns, then you can simply drop the LONG column from the table as follows:\n\n```sql\nALTER TABLE long_tab DROP COLUMN long_pics;\n```\n\n**Multitable Inserts: Examples** The following example uses the multitable insert syntax to insert into the sample table sh.sales some data from an input table with a different structure.\n\n---\n\n**Note:** A number of NOT NULL constraints on the sales table have been disabled for purposes of this example, because the example ignores a number of table columns for the sake of brevity.\n\n---\n\nThe input table looks like this:\n\n```sql\nSELECT * FROM sales_input_table;\n```\n\n| PRODUCT_ID | CUSTOMER_ID | WEEKLY_ST | SALES_SUN | SALES_MON | SALES_TUE | SALES_WED | SALES_THU | SALES_FRI | SALES_SAT |\n|------------|-------------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|\n| 111 | 222 | 01-OCT-00 | 100 | 200 | 300 | 400 | 500 | 600 | 700 |\n| 222 | 333 | 08-OCT-00 | 200 | 300 | 400 | 500 | 600 | 700 | 800 |\n| 333 | 444 | 15-OCT-00 | 300 | 400 | 500 | 600 | 700 | 800 | 900 |\n\nThe multitable insert statement looks like this:\n\n```sql\nINSERT ALL\n INTO sales (prod_id, cust_id, time_id, amount)\n VALUES (product_id, customer_id, weekly_start_date, sales_sun)\n INTO sales (prod_id, cust_id, time_id, amount)\n VALUES (product_id, customer_id, weekly_start_date+1, sales_mon)\n INTO sales (prod_id, cust_id, time_id, amount)\n VALUES (product_id, customer_id, weekly_start_date+2, sales_tue)\n INTO sales (prod_id, cust_id, time_id, amount)\n VALUES (product_id, customer_id, weekly_start_date+3, sales_wed)\n INTO sales (prod_id, cust_id, time_id, amount)\n VALUES (product_id, customer_id, weekly_start_date+4, sales_thu)\n```\n\nAssuming these are the only rows in the sales table, the contents now look like this:\n\n```\nSELECT * FROM sales\nORDER BY prod_id, cust_id, time_id;\n```\n\n| PROD_ID | CUST_ID | TIME_ID | C | PROMO_ID | QUANTITY_SOLD | AMOUNT | COST |\n|---------|---------|-----------|---|----------|---------------|--------|------|\n| 111 | 222 | 01-OCT-00 | | | | | 100 |\n| 111 | 222 | 02-OCT-00 | | | | | 200 |\n| 111 | 222 | 03-OCT-00 | | | | | 300 |\n| 111 | 222 | 04-OCT-00 | | | | | 400 |\n| 111 | 222 | 05-OCT-00 | | | | | 500 |\n| 111 | 222 | 06-OCT-00 | | | | | 600 |\n| 111 | 222 | 07-OCT-00 | | | | | 700 |\n| 222 | 333 | 08-OCT-00 | | | | | 200 |\n| 222 | 333 | 09-OCT-00 | | | | | 300 |\n| 222 | 333 | 10-OCT-00 | | | | | 400 |\n| 222 | 333 | 11-OCT-00 | | | | | 500 |\n| 222 | 333 | 12-OCT-00 | | | | | 600 |\n| 222 | 333 | 13-OCT-00 | | | | | 700 |\n| 222 | 333 | 14-OCT-00 | | | | | 800 |\n| 333 | 444 | 15-OCT-00 | | | | | 300 |\n| 333 | 444 | 16-OCT-00 | | | | | 400 |\n| 333 | 444 | 17-OCT-00 | | | | | 500 |\n| 333 | 444 | 18-OCT-00 | | | | | 600 |\n| 333 | 444 | 19-OCT-00 | | | | | 700 |\n| 333 | 444 | 20-OCT-00 | | | | | 800 |\n| 333 | 444 | 21-OCT-00 | | | | | 900 |\n\nThe next examples insert into multiple tables. Suppose you want to provide to sales representatives some information on orders of various sizes. The following example creates tables for small, medium, large, and special orders and populates those tables with data from the sample table oe.orders:\n\n```\nCREATE TABLE small_orders\n (order_id NUMBER(12) NOT NULL,\n customer_id NUMBER(6) NOT NULL,\n order_total NUMBER(8,2),\n sales_rep_id NUMBER(6)\n );\n\nCREATE TABLE medium_orders AS SELECT * FROM small_orders;\n\nCREATE TABLE large_orders AS SELECT * FROM small_orders;\n\nCREATE TABLE special_orders\n (order_id NUMBER(12) NOT NULL,\n customer_id NUMBER(6) NOT NULL,\n order_total NUMBER(8,2),\n sales_rep_id NUMBER(6),\n credit_limit NUMBER(9,2),\n cust_email VARCHAR2(30)\n );\n```\n\nThe first multitable insert populates only the tables for small, medium, and large orders:\n\n```sql\nINSERT ALL\n WHEN order_total < 100000 THEN\n INTO small_orders\n WHEN order_total > 100000 AND order_total < 200000 THEN\n INTO medium_orders\n WHEN order_total > 200000 THEN\n INTO large_orders\nSELECT order_id, order_total, sales_rep_id, customer_id\n FROM orders;\n```\n\nYou can accomplish the same thing using the `ELSE` clause in place of the insert into the `large_orders` table:\n\n```sql\nINSERT ALL\n WHEN order_total < 100000 THEN\n INTO small_orders\n WHEN order_total > 100000 AND order_total < 200000 THEN\n INTO medium_orders\n ELSE\n INTO large_orders\nSELECT order_id, order_total, sales_rep_id, customer_id\n FROM orders;\n```\n\nThe next example inserts into the small, medium, and large tables, as in the preceding example, and also puts orders greater than 290,000 into the `special_orders` table. This table also shows how to use column aliases to simplify the statement:\n\n```sql\nINSERT ALL\n WHEN ottl < 100000 THEN\n INTO small_orders\n VALUES (oid, ottl, sid, cid)\n WHEN ottl > 100000 and ottl < 200000 THEN\n INTO medium_orders\n VALUES (oid, ottl, sid, cid)\n WHEN ottl > 200000 THEN\n into large_orders\n VALUES (oid, ottl, sid, cid)\n WHEN ottl > 290000 THEN\n INTO special_orders\nSELECT o.order_id oid, o.customer_id cid, o.order_total ottl,\n o.sales_rep_id sid, c.credit_limit cl, c.cust_email cem\n FROM orders o, customers c\n WHERE o.customer_id = c.customer_id;\n```\n\nFinally, the next example uses the `FIRST` clause to put orders greater than 290,000 into the `special_orders` table and exclude those orders from the `large_orders` table:\n\n```sql\nINSERT FIRST\n WHEN ottl < 100000 THEN\n INTO small_orders\n VALUES (oid, ottl, sid, cid)\n WHEN ottl > 100000 and ottl < 200000 THEN\n INTO medium_orders\n VALUES (oid, ottl, sid, cid)\n WHEN ottl > 290000 THEN\n INTO special_orders\n WHEN ottl > 200000 THEN\n```\n\nINTO large_orders\n VALUES(oid, ottl, sid, cid)\nSELECT o.order_id oid, o.customer_id cid, o.order_total ottl,\n o.sales_rep_id sid, c.credit_limit cl, c.cust_email cem\nFROM orders o, customers c\nWHERE o.customer_id = c.customer_id;\n\nLOCK TABLE\n\nPurpose\n\nUse the LOCK TABLE statement to lock one or more tables, table partitions, or table subpartitions in a specified mode. This lock manually overrides automatic locking and permits or denies access to a table or view by other users for the duration of your operation.\n\nSome forms of locks can be placed on the same table at the same time. Other locks allow only one lock for a table.\n\nA locked table remains locked until you either commit your transaction or roll it back, either entirely or to a savepoint before you locked the table.\n\nA lock never prevents other users from querying the table. A query never places a lock on a table. Readers never block writers and writers never block readers.\n\nSee Also:\n\n- Oracle Database Concepts for a complete description of the interaction of lock modes\n- COMMIT on page 13-47\n- ROLLBACK on page 18-97\n- SAVEPOINT on page 19-2\n\nPrerequisites\n\nThe table or view must be in your own schema or you must have the LOCK ANY TABLE system privilege, or you must have any object privilege on the table or view.\n\nSyntax\n\nlock_table::=\n\n\\[\\rightarrow LOCK \\rightarrow TABLE \\rightarrow \\{schema\\} \\rightarrow . \\rightarrow \\{table | view\\} \\rightarrow \\{partition_extension_clause\\} \\rightarrow \\{@ \\rightarrow dblink\\} \\rightarrow \\{IN \\rightarrow lockmode \\rightarrow MODE \\rightarrow \\{NOWAIT | WAIT \\rightarrow integer\\}\\}\\]\n\nSemantics\n\n**schema**\nSpecify the schema containing the table or view. If you omit *schema*, then Oracle Database assumes the table or view is in your own schema.\n\n**table / view**\nSpecify the name of the table or view to be locked.\n\nIf you specify *view*, then Oracle Database locks the base tables of the view.\n\nIf you specify the *partition_extension_clause*, then Oracle Database first acquires an implicit lock on the table. The table lock is the same as the lock you specify for the partition or subpartition, with two exceptions:\n\n- If you specify a *SHARE* lock for the subpartition, then the database acquires an implicit *ROW SHARE* lock on the table.\n- If you specify an *EXCLUSIVE* lock for the subpartition, then the database acquires an implicit *ROW EXCLUSIVE* lock on the table.\n\nIf you specify *PARTITION* and *table* is composite-partitioned, then the database acquires locks on all the subpartitions of the partition.\n\n**Restriction on Locking Tables** If *view* is part of a hierarchy, then it must be the root of the hierarchy.\n\n**dblink**\nSpecify a database link to a remote Oracle Database where the table or view is located. You can lock tables and views on a remote database only if you are using Oracle distributed functionality. All tables locked by a *LOCK TABLE* statement must be on the same database.\n\nIf you omit *dblink*, then Oracle Database assumes the table or view is on the local database.\n\n**See Also:** \"References to Objects in Remote Databases\" on page 3-114 for information on specifying database links\n\n**lockmode Clause**\nSpecify one of the following modes:\n\n**ROW SHARE** *ROW SHARE* permits concurrent access to the locked table but prohibits users from locking the entire table for exclusive access. *ROW SHARE* is synonymous\n\nwith SHARE UPDATE, which is included for compatibility with earlier versions of Oracle Database.\n\n**ROW EXCLUSIVE** ROW EXCLUSIVE is the same as ROW SHARE, but it also prohibits locking in SHARE mode. ROW EXCLUSIVE locks are automatically obtained when updating, inserting, or deleting.\n\n**SHARE UPDATE** See ROW SHARE on page 18-73.\n\n**SHARE** SHARE permits concurrent queries but prohibits updates to the locked table.\n\n**SHARE ROW EXCLUSIVE** SHARE ROW EXCLUSIVE is used to look at a whole table and to allow others to look at rows in the table but to prohibit others from locking the table in SHARE mode or from updating rows.\n\n**EXCLUSIVE** EXCLUSIVE permits queries on the locked table but prohibits any other activity on it.\n\n**NOWAIT**\n\nSpecify NOWAIT if you want the database to return control to you immediately if the specified table, partition, or table subpartition is already locked by another user. In this case, the database returns a message indicating that the table, partition, or subpartition is already locked by another user.\n\n**WAIT**\n\nUse the WAIT clause to indicate that the LOCK TABLE statement should wait up to the specified number of seconds to acquire a DML lock. There is no limit on the value of integer.\n\nIf you specify neither NOWAIT nor WAIT, then the database waits indefinitely until the table is available, locks it, and returns control to you. When the database is executing DDL statements concurrently with DML statements, a timeout or deadlock can sometimes result. The database detects such timeouts and deadlocks and returns an error.\n\n**See Also:** Oracle Database Administrator’s Guide for more information about locking tables\n\n**Examples**\n\n**Locking a Table: Example** The following statement locks the employees table in exclusive mode but does not wait if another user already has locked the table:\n\n```\nLOCK TABLE employees\n IN EXCLUSIVE MODE\n NOWAIT;\n```\n\nThe following statement locks the remote employees table that is accessible through the database link remote:\n\n```\nLOCK TABLE employees@remote\n IN SHARE MODE;\n```\n\nMERGE\n\nPurpose\n\nUse the MERGE statement to select rows from one or more sources for update or insertion into a table or view. You can specify conditions to determine whether to update or insert into the target table or view.\n\nThis statement is a convenient way to combine multiple operations. It lets you avoid multiple INSERT, UPDATE, and DELETE DML statements.\n\nMERGE is a deterministic statement. You cannot update the same row of the target table multiple times in the same MERGE statement.\n\nNote: Oracle Database does not implement fine-grained access control during MERGE statements. If you are using the fine-grained access control feature on the target table or tables, then use equivalent INSERT and UPDATE statements instead of MERGE to avoid error messages and to ensure correct access control.\n\nPrerequisites\n\nYou must have the INSERT and UPDATE object privileges on the target table and the SELECT object privilege on the source table. To specify the DELETE clause of the merge_update_clause, you must also have the DELETE object privilege on the target table.\n\nSyntax\n\nmerge::=\n\n\\[\\text{MERGE} \\rightarrow \\text{hint} \\rightarrow \\text{INTO} \\rightarrow \\text{schema} \\rightarrow \\text{table} \\rightarrow \\text{t_alias} \\rightarrow \\text{USING} \\rightarrow \\text{schema} \\rightarrow \\text{table} \\rightarrow \\text{view} \\rightarrow \\text{subquery} \\rightarrow \\text{ON} \\rightarrow \\text{condition} \\rightarrow \\text{merge_update_clause} \\rightarrow \\text{merge_insert_clause} \\rightarrow \\text{error_logging_clause}\\]\n\n(merge_update_clause::= on page 18-76, merge_insert_clause::= on page 18-76, error_logging_clause::= on page 18-76)\n\nmerge_update_clause::=\n\n→ WHEN → MATCHED → THEN → UPDATE → SET → column → = → (expr | DEFAULT) → , →\n→ where_clause → DELETE → where_clause →\n\nmerge_insert_clause::=\n\n→ WHEN → NOT → MATCHED → THEN → INSERT → (column) → , →\n→ VALUES → (expr | DEFAULT) → ) → where_clause →\n\nwhere_clause::=\n\n→ WHERE → condition →\n\nerror_logging_clause::=\n\n→ LOG → ERRORS → INTO → schema → table → (simple_expression) →\n→ REJECT LIMIT (integer | UNLIMITED)\n\nSemantics\n\nINTO Clause\nUse the INTO clause to specify the target table or view you are updating or inserting into. In order to merge data into a view, the view must be updatable. Refer to \"Notes on Updatable Views\" on page 17-20 for more information.\n\nUSING Clause\nUse the USING clause to specify the source of the data to be updated or inserted. The source can be a table, view, or the result of a subquery.\n\nON Clause\nUse the ON clause to specify the condition upon which the MERGE operation either updates or inserts. For each row in the target table for which the search condition is true, Oracle Database updates the row with corresponding data from the source table.\n\nIf the condition is not true for any rows, then the database inserts into the target table based on the corresponding source table row.\n\n**Restrictions on the ON Clause** Oracle Database does not implement fine-grained access control during `MERGE` statements. If you are using the fine-grained access control feature on the target table or tables, then use equivalent `INSERT` and `UPDATE` statements instead of `MERGE` to avoid error messages and to ensure correct access control.\n\n**merge_update_clause**\n\nThe `merge_update_clause` specifies the new column values of the target table. Oracle performs this update if the condition of the `ON` clause is true. If the update clause is executed, then all update triggers defined on the target table are activated.\n\nSpecify the `where_clause` if you want the database to execute the update operation only if the specified condition is true. The condition can refer to either the data source or the target table. If the condition is not true, then the database skips the update operation when merging the row into the table.\n\nSpecify the `DELETE where_clause` to clean up data in a table while populating or updating it. The only rows affected by this clause are those rows in the destination table that are updated by the merge operation. The `DELETE WHERE` condition evaluates the updated value, not the original value that was evaluated by the `UPDATE SET ... WHERE` condition. If a row of the destination table meets the `DELETE` condition but is not included in the join defined by the `ON` clause, then it is not deleted. Any delete triggers defined on the target table will be activated for each row deletion.\n\nYou can specify this clause by itself or with the `merge_insert_clause`. If you specify both, then they can be in either order.\n\n**Restrictions on the merge_update_clause** This clause is subject to the following restrictions:\n\n- You cannot update a column that is referenced in the `ON condition` clause.\n- You cannot specify `DEFAULT` when updating a view.\n\n**merge_insert_clause**\n\nThe `merge_insert_clause` specifies values to insert into the column of the target table if the condition of the `ON` clause is false. If the insert clause is executed, then all insert triggers defined on the target table are activated. If you omit the column list after the `INSERT` keyword, then the number of columns in the target table must match the number of values in the `VALUES` clause.\n\nTo insert all of the source rows into the table, you can use a **constant filter predicate** in the `ON` clause condition. An example of a constant filter predicate is `ON (0=1)`. Oracle Database recognizes such a predicate and makes an unconditional insert of all source rows into the table. This approach is different from omitting the `merge_update_clause`. In that case, the database still must perform a join. With constant filter predicate, no join is performed.\n\nSpecify the `where_clause` if you want Oracle Database to execute the insert operation only if the specified condition is true. The condition can refer only to the data source table. Oracle Database skips the insert operation for all rows for which the condition is not true.\n\nYou can specify this clause by itself or with the `merge_update_clause`. If you specify both, then they can be in either order.\n\nRestriction on Merging into a View You cannot specify DEFAULT when updating a view.\n\nerror_logging_clause\n\nThe error_logging_clause has the same behavior in a MERGE statement as in an INSERT statement. Refer to the INSERT statement error_logging_clause on page 18-78 for more information.\n\nSee Also: \"Inserting Into a Table with Error Logging: Example\" on page 18-66\n\nExamples\n\nMerging into a Table: Example The following example uses the bonuses table in the sample schema oe with a default bonus of 100. It then inserts into the bonuses table all employees who made sales, based on the sales_rep_id column of the oe.orders table. Finally, the human resources manager decides that employees with a salary of $8000 or less should receive a bonus. Those who have not made sales get a bonus of 1% of their salary. Those who already made sales get an increase in their bonus equal to 1% of their salary. The MERGE statement implements these changes in one step:\n\n```sql\nCREATE TABLE bonuses (employee_id NUMBER, bonus NUMBER DEFAULT 100);\n\nINSERT INTO bonuses(employee_id)\n (SELECT e.employee_id FROM employees e, orders o\n WHERE e.employee_id = o.sales_rep_id\n GROUP BY e.employee_id);\n\nSELECT * FROM bonuses ORDER BY employee_id;\n\nEMPLOYEE_ID BONUS\n------------ ---------\n 153 100\n 154 100\n 155 100\n 156 100\n 158 100\n 159 100\n 160 100\n 161 100\n 163 100\n\nMERGE INTO bonuses D\n USING (SELECT employee_id, salary, department_id FROM employees\n WHERE department_id = 80) S\n ON (D.employee_id = S.employee_id)\n WHEN MATCHED THEN UPDATE SET D.bonus = D.bonus + S.salary*.01\n DELETE WHERE (S.salary > 8000)\n WHEN NOT MATCHED THEN INSERT (D.employee_id, D.bonus)\n VALUES (S.employee_id, S.salary*.01)\n WHERE (S.salary <= 8000);\n\nSELECT * FROM bonuses ORDER BY employee_id;\n\nEMPLOYEE_ID BONUS\n------------ ---------\n 153 180\n```\n\n| | |\n|---|---|\n| 154 | 175 |\n| 155 | 170 |\n| 159 | 180 |\n| 160 | 175 |\n| 161 | 170 |\n| 164 | 72 |\n| 165 | 68 |\n| 166 | 64 |\n| 167 | 62 |\n| 171 | 74 |\n| 172 | 73 |\n| 173 | 61 |\n| 179 | 62 |\n\nNOAUDIT\n\nPurpose\n\nUse the NOAUDIT statement to stop auditing operations previously enabled by the AUDIT statement.\n\nThe NOAUDIT statement must have the same syntax as the previous AUDIT statement. Further, it reverses the effects only of that particular statement. For example, suppose one AUDIT statement A enables auditing for a specific user. A second statement B enables auditing for all users. A NOAUDIT statement C to disable auditing for all users reverses statement B. However, statement C leaves statement A in effect and continues to audit the user that statement A specified.\n\nSee Also: AUDIT on page 13-27 for more information on auditing\n\nPrerequisites\n\nTo stop auditing of SQL statements, you must have the AUDIT SYSTEM system privilege.\n\nTo stop auditing of schema objects, you must be the owner of the object on which you stop auditing or you must have the AUDIT ANY system privilege. In addition, if the object you chose for auditing is a directory, then even if you created it, you must have the AUDIT ANY system privilege.\n\nSyntax\n\nnoaudit:-\n\n\\[\\rightarrow \\text{NOAUDIT} \\rightarrow \\begin{cases} \\text{audit_operation_clause} \\\\ \\text{audit_schema_object_clause} \\\\ \\text{NETWORK} \\end{cases} \\rightarrow \\begin{cases} \\text{WHENEVER} \\\\ \\text{NOT} \\\\ \\text{SUCCESSFUL} \\end{cases}\\]\n\n(audit_operation_clause::= on page 18-80, audit_schema_object_clause::= on page 18-81)\n\naudit_operation_clause::=\n\n**Semantics**\n\n**audit_operation_clause**\n\nUse the *audit_operation_clause* to stop auditing of a particular SQL statement.\n\n**statement_option** For *sql_statement_shortcut*, specify the shortcut for the SQL statements for which auditing is to be stopped. Refer to Table 13–1 on page 13-33 and Table 13–2 on page 13-35 for a list of the SQL statement shortcuts and the SQL statements they audit.\n\n**ALL** Specify ALL to stop auditing of all statement options currently being audited because of an earlier AUDIT ALL . . . statement. You cannot use this clause to reverse an earlier AUDIT ALL STATEMENTS . . . statement.\n\n**ALL STATEMENTS** Specify ALL STATEMENTS to reverse an earlier AUDIT ALL STATEMENTS . . . statement. You cannot use this clause to reverse an earlier AUDIT ALL . . . statement.\n\n**system_privilege** For *system_privilege*, specify the system privilege for which auditing is to be stopped. Refer to Table 18–1 on page 18-39 for a list of the system privileges and the statements they authorize.\n\n**ALL PRIVILEGES** Specify ALL PRIVILEGES to stop auditing of all system privileges currently being audited.\n\n**auditing_by_clause** Use the *auditing_by_clause* to stop auditing only those SQL statements issued by particular users. If you omit this clause, then Oracle Database stops auditing all users' statements.\n\n- Specify **BY user** to stop auditing only for SQL statements issued by the specified users in their subsequent sessions. If you omit this clause, then Oracle Database stops auditing for all users' statements, except for the situation described for **WHENEVER SUCCESSFUL**.\n\n- Specify **BY proxy** to stop auditing only for the SQL statements issued by the specified proxy, on behalf of a specific user or any user.\n\n**Restriction on auditing_by_clause** The **IN SESSION CURRENT** clause is not supported in a NOAUDIT statement.\n\n**audit_schema_object_clause**\n\nUse the *audit_schema_object_clause* to stop auditing of a particular database object.\n\n**sql_operation** For *sql_operation*, specify the type of operation for which auditing is to be stopped on the object specified in the **ON** clause. Refer to Table 13–3 on page 13-36 for a list of these options.\n\n**ALL** Specify **ALL** as a shortcut equivalent to specifying all SQL operations applicable for the type of object.\n\n**auditing_on_clause** The *auditing_on_clause* lets you specify the particular schema object for which auditing is to be stopped.\n\n- For object, specify the object name of a table, view, sequence, stored procedure, function, or package, materialized view, or library. If you do not qualify *object* with *schema*, then Oracle Database assumes the object is in your own schema. Refer to AUDIT on page 13-27 for information on auditing specific schema objects.\n\n- The **DIRECTORY** clause lets you specify the name of the directory on which auditing is to be stopped.\n\n- Specify **DEFAULT** to remove the specified object options as default object options for subsequently created objects.\n\n**NETWORK** Use this clause to discontinue auditing of database link usage and logins.\n\n**WHENEVER [NOT] SUCCESSFUL** Specify **WHENEVER SUCCESSFUL** to stop auditing only for SQL statements and operations on schema objects that complete successfully. Specify **WHENEVER NOT SUCCESSFUL** to stop auditing only for statements and operations that result in Oracle Database errors.\n\nIf you omit this clause, then the database stops auditing for all statements or operations, regardless of success or failure.\n\n**Examples**\n\n**Stop Auditing of SQL Statements Related to Roles: Example** If you have chosen auditing for every SQL statement that creates or drops a role, then you can stop auditing of such statements by issuing the following statement:\n\n```\nNOAUDIT ROLE;\n```\n\nStop Auditing of Updates or Queries on Objects Owned by a Particular User:\nExample If you have chosen auditing for any statement that queries or updates any table issued by the users hr and oe, then you can stop auditing for queries by hr by issuing the following statement:\n\nNOAUDIT SELECT TABLE BY hr;\n\nThe preceding statement stops auditing only queries by hr, so the database continues to audit queries and updates by oe as well as updates by hr.\n\nStop Auditing of Statements Authorized by a Particular Object Privilege: Example\nTo stop auditing on all statements that are authorized by DELETE ANY TABLE system privilege, issue the following statement:\n\nNOAUDIT DELETE ANY TABLE;\n\nStop Auditing of Queries on a Particular Object: Example If you have chosen auditing for every SQL statement that queries the employees table in the schema hr, then you can stop auditing for such queries by issuing the following statement:\n\nNOAUDIT SELECT\n ON hr.employees;\n\nStop Auditing of Queries that Complete Successfully: Example You can stop auditing for queries that complete successfully by issuing the following statement:\n\nNOAUDIT SELECT\n ON hr.employees\n WHENEVER SUCCESSFUL;\n\nThis statement stops auditing only for successful queries. Oracle Database continues to audit queries resulting in Oracle Database errors.\n\nPURGE\n\nPurpose\n\nUse the PURGE statement to remove a table or index from your recycle bin and release all of the space associated with the object, or to remove the entire recycle bin, or to remove part of all of a dropped tablespace from the recycle bin.\n\nCaution: You cannot roll back a PURGE statement, nor can you recover an object after it is purged.\n\nTo see the contents of your recycle bin, query the USER_RECYCLEBIN data dictionary view. You can use the RECYCLEBIN synonym instead. The following two statements return the same rows:\n\n```sql\nSELECT * FROM RECYCLEBIN;\nSELECT * FROM USER_RECYCLEBIN;\n```\n\nSee Also:\n\n- Oracle Database Administrator’s Guide for information on the recycle bin and naming conventions for objects in the recycle bin\n- FLASHBACK TABLE on page 18-27 for information on retrieving dropped tables from the recycle bin\n\nPrerequisites\n\nThe database object must reside in your own schema or you must have the DROP ANY ... system privilege for the type of object to be purged, or you must have the SYSDBA system privilege.\n\nSyntax\n\n```plaintext\npurge::=\n PURGE {TABLE | INDEX | RECYCLEBIN | DBA_RECYCLEBIN | TABLESPACE} [USER user] ;\n```\n\nSemantics\n\n**TABLE or INDEX**\n\nSpecify the name of the table or index in the recycle bin that you want to purge. You can specify either the original user-specified name or the system-generated name Oracle Database assigned to the object when it was dropped.\n\nIf you specify the user-specified name, and if the recycle bin contains more than one object of that name, then the database purges the object that has been in the recycle bin the longest.\n\nSystem-generated recycle bin object names are unique. Therefore, if you specify the system-generated name, then the database purges that specified object.\n\nWhen the database purges a table, all table partitions, LOBs and LOB partitions, indexes, and other dependent objects of that table are also purged.\n\n**RECYCLEBIN**\n\nUse this clause to purge the current user’s recycle bin. Oracle Database will remove all objects from the user’s recycle bin and release all space associated with objects in the recycle bin.\n\n**DBA_RECYCLEBIN**\n\nThis clause is valid only if you have `SYSDBA` system privilege. It lets you remove all objects from the system-wide recycle bin, and is equivalent to purging the recycle bin of every user. This operation is useful, for example, before backward migration.\n\n**TABLESPACE** *tablespace*\n\nUse this clause to purge all the objects residing in the specified tablespace from the recycle bin.\n\n**USER** *user* Use this clause to reclaim space in a tablespace for a specified user. This operation is useful when a particular user is running low on disk quota for the specified tablespace.\n\n**Examples**\n\n**Remove a File From Your Recycle Bin: Example** The following statement removes the table `test` from the recycle bin. If more than one version of `test` resides in the recycle bin, then Oracle Database removes the version that has been there the longest:\n\n```sql\nPURGE TABLE test;\n```\n\nTo determine system-generated name of the table you want removed from your recycle bin, issue a `SELECT` statement on your recycle bin. Using that object name, you can remove the table by issuing a statement similar to the following statement. (The system-generated name will differ from the one shown in the example.)\n\n```sql\nPURGE TABLE RB$S33750$TABLE$0;\n```\n\n**Remove the Contents of Your Recycle Bin: Example** To remove the entire contents of your recycle bin, issue the following statement:\n\n```sql\nPURGE RECYCLEBIN;\n```\n\nRENAME\n\nPurpose\n\nCaution: You cannot roll back a RENAME statement.\n\nUse the RENAME statement to rename a table, view, sequence, or private synonym.\n\n- Oracle Database automatically transfers integrity constraints, indexes, and grants on the old object to the new object.\n\n- Oracle Database invalidates all objects that depend on the renamed object, such as views, synonyms, and stored procedures and functions that refer to a renamed table.\n\nSee Also: CREATE SYNONYM on page 16-2 and DROP SYNONYM on page 18-3\n\nPrerequisites\n\nThe object must be in your own schema.\n\nSyntax\n\nrename::=\n\n```\nRENAME <old_name> TO <new_name>;\n```\n\nSemantics\n\nold_name\n\nSpecify the name of an existing table, view, sequence, or private synonym.\n\nnew_name\n\nSpecify the new name to be given to the existing object. The new name must not already be used by another schema object in the same namespace and must follow the rules for naming schema objects.\n\nRestrictions on Renaming Objects\n\nRenaming objects is subject to the following restrictions:\n\n- You cannot rename a public synonym. Instead, drop the public synonym and then re-create the public synonym with the new name.\n\n- You cannot rename a type synonym that has any dependent tables or dependent valid user-defined object types.\n\nSee Also: \"Database Object Naming Rules\" on page 3-108\n\nExample\n\nRenaming a Database Object: Example The following example uses a copy of the sample table `hr.departments`. To change the name of table `departments_new` to `emp_departments`, issue the following statement:\n\n```\nRENAME departments_new TO emp_departments;\n```\n\nYou cannot use this statement directly to rename columns. However, you can rename a column using the `ALTER TABLE ... rename_column_clause`.\n\nSee Also: `rename_column_clause` on page 12-51\n\nAnother way to rename a column is to use the `RENAME` statement together with the `CREATE TABLE` statement with `AS subquery`. This method is useful if you are changing the structure of a table rather than only renaming a column. The following statements re-create the sample table `hr.job_history`, renaming a column from `department_id` to `dept_id`:\n\n```\nCREATE TABLE temporary\n (employee_id, start_date, end_date, job_id, dept_id)\nAS SELECT\n employee_id, start_date, end_date, job_id, department_id\nFROM job_history;\n\nDROP TABLE job_history;\n\nRENAME temporary TO job_history;\n```\n\nAny integrity constraints defined on table `job_history` will be lost in the preceding example. You will have to redefine them on the new `job_history` table using an `ALTER TABLE` statement.\n\nREVOKE\n\nPurpose\n\nUse the REVOKE statement to:\n\n- Revoke system privileges from users and roles\n- Revoke roles from users and roles\n- Revoke object privileges for a particular object from users and roles\n\n**Note on Oracle Automatic Storage Management** A user authenticated AS SYSASM can use this statement to revoke the system privileges SYSASM, SYSOPER, and SYSDBA from a user in the Oracle ASM password file of the current node.\n\n**Note on Editable Objects** A REVOKE operation to revoke object privileges on an editable object actualizes the object in the current edition. See *Oracle Database Advanced Application Developer’s Guide* for more information about editions and editable objects.\n\n**See Also:**\n\n- GRANT on page 18-33 for information on granting system privileges and roles\n- Table 18–2 on page 18-48 for a listing of the object privileges for each type of object\n\nPrerequisites\n\nTo revoke a **system privilege**, you must have been granted the privilege with the ADMIN OPTION. You can revoke any privilege if you have the GRANT ANY PRIVILEGE system privilege.\n\nTo revoke a **role**, you must have been granted the role with the ADMIN OPTION. You can revoke any role if you have the GRANT ANY ROLE system privilege.\n\nTo revoke an **object privilege**, you must previously have granted the object privilege to the user and role or you must have the GRANT ANY OBJECT PRIVILEGE system privilege. In the latter case, you can revoke any object privilege that was granted by the object owner or on behalf of the owner by a user with the GRANT ANY OBJECT PRIVILEGE. However, you cannot revoke an object privilege that was granted by way of a WITH GRANT OPTION grant.\n\n**See Also:** “Revoke Operations that Use GRANT ANY OBJECT PRIVILEGE: Example” on page 18-95\n\nThe REVOKE statement can revoke only privileges and roles that were previously granted directly with a GRANT statement. You cannot use this statement to revoke:\n\n- Privileges or roles not granted to the revokee\n- Roles or object privileges granted through the operating system\n- Privileges or roles granted to the revokee through roles\n\n**Syntax**\n\n*revoke:*\n\n\\[ \\text{REVOKE} \\rightarrow \\{ \\text{revoke_system_privilege} \\mid \\text{revoke_object_privileges} \\} \\]\n\n(revoke_system_privileges::= on page 18-89, revoke_object_privileges::= on page 18-89)\n\n*revoke_system_privileges:*\n\n\\[ \\text{system_privilege} \\mid \\text{role} \\mid \\text{ALL} \\mid \\text{PRIVILEGES} \\rightarrow \\text{FROM} \\rightarrow \\text{grantee_clause} \\]\n\n(grantee_clause::= on page 18-89)\n\n*revoke_object_privileges:*\n\n\\[ \\text{object_privilege} \\mid \\text{ALL} \\mid \\text{PRIVILEGES} \\rightarrow \\text{on_object_clause} \\]\n\n\\[ \\text{FROM} \\rightarrow \\text{grantee_clause} \\rightarrow \\{ \\text{CASCADE} \\mid \\text{CONSTRAINTS} \\mid \\text{FORCE} \\} \\]\n\n(on_object_clause::= on page 18-90, grantee_clause::= on page 18-89)\n\n*grantee_clause:*\n\n\\[ \\text{user} \\mid \\text{role} \\mid \\text{PUBLIC} \\rightarrow \\{ \\text{IDENTIFIED BY password} \\} \\]\n\nSemantics\n\n**revoke_system_privileges**\n\nUse these clauses to revoke system privileges.\n\n**system_privilege**\n\nSpecify the system privilege to be revoked. Refer to Table 18–1 on page 18-39 for a list of the system privileges.\n\nIf you revoke a system privilege from a user, then the database removes the privilege from the user's privilege domain. Effective immediately, the user cannot exercise the privilege.\n\nIf you revoke a system privilege from a role, then the database removes the privilege from the privilege domain of the role. Effective immediately, users with the role enabled cannot exercise the privilege. Also, other users who have been granted the role and subsequently enable the role cannot exercise the privilege.\n\nSee Also: \"Revoking a System Privilege from a User: Example\" on page 18-93 and \"Revoking a System Privilege from a Role: Example\" on page 18-94\n\nIf you revoke a system privilege from PUBLIC, then the database removes the privilege from the privilege domain of each user who has been granted the privilege through PUBLIC. Effective immediately, such users can no longer exercise the privilege. However, the privilege is not revoked from users who have been granted the privilege directly or through roles.\n\nOracle Database provides a shortcut for specifying all system privileges at once: Specify ALL PRIVILEGES to revoke all the system privileges listed in Table 18–1 on page 18-39.\n\n**Restriction on Revoking System Privileges** A system privilege cannot appear more than once in the list of privileges to be revoked.\n\n**role**\n\nSpecify the role to be revoked.\n\nIf you revoke a role from a user, then the database makes the role unavailable to the user. If the role is currently enabled for the user, then the user can continue to exercise the privileges in the role's privilege domain as long as it remains enabled. However, the user cannot subsequently enable the role.\n\nIf you revoke a role from another role, then the database removes the privilege domain of the revoked role from the privilege domain of the revokee role. Users who have been granted and have enabled the revokee role can continue to exercise the privileges in the privilege domain of the revoked role as long as the revokee role remains enabled. However, other users who have been granted the revokee role and subsequently enable it cannot exercise the privileges in the privilege domain of the revoked role.\n\n**See Also:** \"Revoking a Role from a User: Example\" on page 18-93 \nand \"Revoking a Role from a Role: Example\" on page 18-94\n\nIf you revoke a role from PUBLIC, then the database makes the role unavailable to all users who have been granted the role through PUBLIC. Any user who has enabled the role can continue to exercise the privileges in its privilege domain as long as it remains enabled. However, users cannot subsequently enable the role. The role is not revoked from users who have been granted the role directly or through other roles.\n\n**Restriction on Revoking System Roles** A system role cannot appear more than once in the list of roles to be revoked. For information on the predefined roles, refer to *Oracle Database Security Guide*.\n\n**grantee_clause**\n\nFROM grantee_clause identifies users or roles from which the system privilege, role, or object privilege is to be revoked.\n\n**PUBLIC** Specify PUBLIC to revoke the privileges or roles from all users.\n\n**revoke_object_privileges**\n\nUse these clauses to revoke object privileges.\n\n**object_privilege**\n\nSpecify the object privilege to be revoked. You can substitute any of the object privileges described on Table 18–2 on page 18-48.\n\n---\n\n**Note:** Each privilege authorizes some operation. By revoking a privilege, you prevent the revokee from performing that operation. However, multiple users may grant the same privilege to the same user, role, or PUBLIC. To remove the privilege from the grantee's privilege domain, all grantors must revoke the privilege. If even one grantor does not revoke the privilege, then the grantee can still exercise the privilege by virtue of that grant.\n\n---\n\nIf you revoke an object privilege from a user, then the database removes the privilege from the user's privilege domain. Effective immediately, the user cannot exercise the privilege.\n\n- If that user has granted that privilege to other users or roles, then the database also revokes the privilege from those other users or roles.\n- If that user's schema contains a procedure, function, or package that contains SQL statements that exercise the privilege, then the procedure, function, or package can no longer be executed.\n\nIf that user's schema contains a view on that object, then the database invalidates the view.\n\n- If you revoke the REFERENCES object privilege from a user who has exercised the privilege to define referential integrity constraints, then you must specify the CASCADE CONSTRAINTS clause.\n\nIf you revoke an object privilege from a role, then the database removes the privilege from the privilege domain of the role. Effective immediately, users with the role enabled cannot exercise the privilege. Other users who have been granted the role cannot exercise the privilege after enabling the role.\n\nIf you revoke an object privilege from PUBLIC, then the database removes the privilege from the privilege domain of each user who has been granted the privilege through PUBLIC. Effective immediately, all such users are restricted from exercising the privilege. However, the privilege is not revoked from users who have been granted the privilege directly or through roles.\n\n**ALL [PRIVILEGES]**\n\nSpecify ALL to revoke all object privileges that you have granted to the revokee. (The keyword PRIVILEGES is provided for semantic clarity and is optional.)\n\nIf no privileges have been granted on the object, then the database takes no action and does not return an error.\n\n**Restriction on Revoking Object Privileges**\n\nA privilege cannot appear more than once in the list of privileges to be revoked. A user, a role, or PUBLIC cannot appear more than once in the FROM clause.\n\n*See Also:*\n\n\"Revoking an Object Privilege from a User: Example\" on page 18-94, \"Revoking Object Privileges from PUBLIC: Example\" on page 18-94, and \"Revoking All Object Privileges from a User: Example\" on page 18-94\n\n**CASCADE CONSTRAINTS**\n\nThis clause is relevant only if you revoke the REFERENCES privilege or ALL [PRIVILEGES]. It drops any referential integrity constraints that the revokee has defined using the REFERENCES privilege, which might have been granted either explicitly or implicitly through a grant of ALL [PRIVILEGES].\n\n*See Also:*\n\n\"Revoking an Object Privilege with CASCADE CONSTRAINTS: Example\" on page 18-95\n\n**FORCE**\n\nSpecify FORCE to revoke the EXECUTE object privilege on user-defined type objects with table or type dependencies. You must use FORCE to revoke the EXECUTE object privilege on user-defined type objects with table dependencies.\n\nIf you specify FORCE, then all privileges are revoked, all dependent objects are marked INVALID, data in dependent tables becomes inaccessible, and all dependent function-based indexes are marked UNUSABLE. Regranting the necessary type privilege will revalidate the table.\n\n*See Also:*\n\nOracle Database Concepts for detailed information about type dependencies and user-defined object privileges\n\nThe `on_object_clause` identifies the objects on which privileges are to be revoked.\n\n**object** Specify the object on which the object privileges are to be revoked. This object can be:\n\n- A table, view, sequence, procedure, stored function, package, or materialized view\n- A synonym for a table, view, sequence, procedure, stored function, package, materialized view, or user-defined type\n- A library, indextype, or user-defined operator\n\nIf you do not qualify object with `schema`, then the database assumes the object is in your own schema.\n\n**See Also:** \"Revoking an Object Privilege on a Sequence from a User: Example\" on page 18-94\n\nIf you revoke the SELECT object privilege on the containing table or materialized view of a materialized view, whether the privilege was granted with or without the GRANT OPTION, then the database invalidates the materialized view.\n\nIf you revoke the SELECT object privilege on any of the master tables of a materialized view, whether the privilege was granted with or without the GRANT OPTION, then the database invalidates both the materialized view and its containing table or materialized view.\n\n**DIRECTORY directory_name** Specify the directory object on which privileges are to be revoked. You cannot qualify `directory_name` with `schema`. The object must be a directory.\n\n**See Also:** CREATE DIRECTORY on page 14-42 and \"Revoking an Object Privilege on a Directory from a User: Example\" on page 18-95\n\n**EDITION** Specify the name of the edition on which the USE object privilege is to be revoked. You cannot qualify `edition_name` with `schema`.\n\n**JAVA SOURCE | RESOURCE** The JAVA clause lets you specify a Java source or resource schema object on which privileges are to be revoked.\n\n### Examples\n\n**Revoking a System Privilege from a User: Example**\n\nThe following statement revokes the DROP ANY TABLE system privilege from the users `hr` and `oe`:\n\n```\nREVOKE DROP ANY TABLE\n FROM hr, oe;\n```\n\nThe users `hr` and `oe` can no longer drop tables in schemas other than their own.\n\n**Revoking a Role from a User: Example**\n\nThe following statement revokes the role `dw_manager` from the user `sh`:\n\n```\nREVOKE dw_manager\n FROM sh;\n```\n\nThe user `sh` can no longer enable the `dw_manager` role.\n\nRevoking a System Privilege from a Role: Example The following statement revokes the CREATE TABLESPACE system privilege from the dw_manager role:\n\n```\nREVOKE CREATE TABLESPACE\n FROM dw_manager;\n```\n\nEnabling the dw_manager role no longer allows users to create tablespaces.\n\nRevoking a Role from a Role: Example To revoke the role dw_user from the role dw_manager, issue the following statement:\n\n```\nREVOKE dw_user\n FROM dw_manager;\n```\n\nThe dw_user role privileges are no longer granted to dw_manager.\n\nRevoking an Object Privilege from a User: Example You can grant DELETE, INSERT, SELECT, and UPDATE privileges on the table orders to the user hr with the following statement:\n\n```\nGRANT ALL\n ON orders TO hr;\n```\n\nTo revoke the DELETE privilege on orders from hr, issue the following statement:\n\n```\nREVOKE DELETE\n ON orders FROM hr;\n```\n\nRevoking All Object Privileges from a User: Example To revoke the remaining privileges on orders that you granted to hr, issue the following statement:\n\n```\nREVOKE ALL\n ON orders FROM hr;\n```\n\nRevoking Object Privileges from PUBLIC: Example You can grant SELECT and UPDATE privileges on the view emp_details_view to all users by granting the privileges to the role PUBLIC:\n\n```\nGRANT SELECT, UPDATE\n ON emp_details_view TO public;\n```\n\nThe following statement revokes UPDATE privilege on emp_details_view from all users:\n\n```\nREVOKE UPDATE\n ON emp_details_view FROM public;\n```\n\nUsers can no longer update the emp_details_view view, although users can still query it. However, if you have also granted the UPDATE privilege on emp_details_view to any users, either directly or through roles, then these users retain the privilege.\n\nRevoking an Object Privilege on a Sequence from a User: Example You can grant the user oe the SELECT privilege on the departments_seq sequence in the schema hr with the following statement:\n\n```\nGRANT SELECT\n ON hr.departments_seq TO oe;\n```\n\nTo revoke the SELECT privilege on departments_seq from oe, issue the following statement:\n\nREVOKE SELECT\n ON hr.departments_seq FROM oe;\n\nHowever, if the user hr has also granted SELECT privilege on departments to sh, then sh can still use departments by virtue of hr's grant.\n\n**Revoking an Object Privilege with CASCADE CONSTRAINTS: Example** You can grant to oe the privileges REFERENCES and UPDATE on the employees table in the schema hr with the following statement:\n\n```\nGRANT REFERENCES, UPDATE\n ON hr.employees TO oe;\n```\n\nThe user oe can exercise the REFERENCES privilege to define a constraint in his or her own dependent table that refers to the employees table in the schema hr:\n\n```\nCREATE TABLE dependent\n(dependno NUMBER,\ndependname VARCHAR2(10),\nemployee NUMBER\n CONSTRAINT in_emp REFERENCES hr.employees(employee_id) );\n```\n\nYou can revoke the REFERENCES privilege on hr.employees from oe by issuing the following statement that contains the CASCADE CONSTRAINTS clause:\n\n```\nREVOKE REFERENCES\n ON hr.employees\n FROM oe\n CASCADE CONSTRAINTS;\n```\n\nRevoking oe's REFERENCES privilege on hr.employees causes Oracle Database to drop the in_emp constraint, because oe required the privilege to define the constraint.\n\nHowever, if oe has also been granted the REFERENCES privilege on hr.employees by a user other than you, then the database does not drop the constraint. oe still has the privilege necessary for the constraint by virtue of the other user's grant.\n\n**Revoking an Object Privilege on a Directory from a User: Example** You can revoke the READ object privilege on directory bfile_dir from hr by issuing the following statement:\n\n```\nREVOKE READ ON DIRECTORY bfile_dir FROM hr;\n```\n\n**Revoke Operations that Use GRANT ANY OBJECT PRIVILEGE: Example** Suppose that the database administrator has granted GRANT ANY OBJECT PRIVILEGE to user sh. Now suppose that user hr grants the update privilege on the employees table to oe:\n\n```\nCONNECT hr\nGRANT UPDATE ON employees TO oe WITH GRANT OPTION;\n```\n\nThis grant gives user oe the right to pass the object privilege along to another user:\n\n```\nCONNECT oe\nGRANT UPDATE ON hr.employees TO pm;\n```\n\nUser sh, who has the GRANT ANY OBJECT PRIVILEGE, can now act on behalf of user hr and revoke the update privilege from user oe, because oe was granted the privilege by hr:\n\n```\nCONNECT sh\n```\n\nREVOKE UPDATE ON hr.employees FROM oe;\n\nUser sh cannot revoke the update privilege from user pm explicitly, because pm received the grant neither from the object owner (hr), nor from sh, nor from another user with GRANT ANY OBJECT PRIVILEGE, but from user oe. However, the preceding statement cascades, removing all privileges that depend on the one revoked. Therefore the object privilege is implicitly revoked from pm as well.\n\nROLLBACK\n\nPurpose\n\nUse the ROLLBACK statement to undo work done in the current transaction or to manually undo the work done by an in-doubt distributed transaction.\n\nNote: Oracle recommends that you explicitly end transactions in application programs using either a COMMIT or ROLLBACK statement. If you do not explicitly commit the transaction and the program terminates abnormally, then Oracle Database rolls back the last uncommitted transaction.\n\nSee Also:\n\n- Oracle Database Concepts for information on transactions\n- Oracle Database Heterogeneous Connectivity User’s Guide for information on distributed transactions\n- SET TRANSACTION on page 19-63 for information on setting characteristics of the current transaction\n- COMMIT on page 13-47 and SAVEPOINT on page 19-2\n\nPrerequisites\n\nTo roll back your current transaction, no privileges are necessary.\n\nTo manually roll back an in-doubt distributed transaction that you originally committed, you must have the FORCE TRANSACTION system privilege. To manually roll back an in-doubt distributed transaction originally committed by another user, you must have the FORCE ANY TRANSACTION system privilege.\n\nSyntax\n\nrollback: =\n\nSemantics\n\nWORK\n\nThe keyword WORK is optional and is provided for SQL standard compatibility.\n\nTO SAVEPOINT Clause\n\nSpecify the savepoint to which you want to roll back the current transaction. If you omit this clause, then the ROLLBACK statement rolls back the entire transaction.\n\nUsing ROLLBACK without the TO SAVEPOINT clause performs the following operations:\n\n- Ends the transaction\n- Undoes all changes in the current transaction\n- Erases all savepoints in the transaction\n- Releases any transaction locks\n\n**See Also:** SAVEPOINT on page 19-2\n\nUsing ROLLBACK with the TO SAVEPOINT clause performs the following operations:\n\n- Rolls back just the portion of the transaction after the savepoint. It does not end the transaction.\n\n- Erases all savepoints created after that savepoint. The named savepoint is retained, so you can roll back to the same savepoint multiple times. Prior savepoints are also retained.\n\n- Releases all table and row locks acquired since the savepoint. Other transactions that have requested access to rows locked after the savepoint must continue to wait until the transaction is committed or rolled back. Other transactions that have not already requested the rows can request and access the rows immediately.\n\n**Restriction on In-doubt Transactions** You cannot manually roll back an in-doubt transaction to a savepoint.\n\n**FORCE Clause**\n\nSpecify FORCE to manually roll back an in-doubt distributed transaction. The transaction is identified by the string containing its local or global transaction ID. To find the IDs of such transactions, query the data dictionary view DBA_2PC_PENDING.\n\nA ROLLBACK statement with a FORCE clause rolls back only the specified transaction. Such a statement does not affect your current transaction.\n\n**See Also:** Oracle Database Administrator’s Guide for more information on distributed transactions and rolling back in-doubt transactions\n\n**Examples**\n\n**Rolling Back Transactions: Examples** The following statement rolls back your entire current transaction:\n\n```\nROLLBACK;\n```\n\nThe following statement rolls back your current transaction to savepoint banda_sal:\n\n```\nROLLBACK TO SAVEPOINT banda_sal;\n```\n\nSee \"Creating Savepoints: Example\" on page 19-2 for a full version of the preceding example.\n\nThe following statement manually rolls back an in-doubt distributed transaction:\n\n```\nROLLBACK WORK\n FORCE '25.32.87';\n```\n\nThis chapter contains the following SQL statements:\n\n- SAVEPOINT\n- SELECT\n- SET CONSTRAINT[S]\n- SET ROLE\n- SET TRANSACTION\n- TRUNCATE CLUSTER\n- TRUNCATE TABLE\n- UPDATE\n\nSAVEPOINT\n\nPurpose\n\nUse the SAVEPOINT statement to create a name for a system change number (SCN), to which you can later roll back.\n\nSee Also:\n\n- Oracle Database Concepts for information on savepoints.\n- ROLLBACK on page 18-97 for information on rolling back transactions\n- SET TRANSACTION on page 19-63 for information on setting characteristics of the current transaction\n\nPrerequisites\n\nNone.\n\nSyntax\n\nsavepoint:==\n\nSAVEPOINT savepoint ;\n\nSemantics\n\nsavepoint\n\nSpecify the name of the savepoint to be created.\n\nSavepoint names must be distinct within a given transaction. If you create a second savepoint with the same identifier as an earlier savepoint, then the earlier savepoint is erased. After a savepoint has been created, you can either continue processing, commit your work, roll back the entire transaction, or roll back to the savepoint.\n\nExample\n\nCreating Savepoints: Example To update the salary for Banda and Greene in the sample table hr.employees, check that the total department salary does not exceed 314,000, then reenter the salary for Greene:\n\nUPDATE employees\n SET salary = 7000\n WHERE last_name = 'Banda';\nSAVEPOINT banda_sal;\n\nUPDATE employees\n SET salary = 12000\n WHERE last_name = 'Greene';\nSAVEPOINT greene_sal;\n\nSELECT SUM(salary) FROM employees;\n\nROLLBACK TO SAVEPOINT banda_sal;\n\nUPDATE employees\n SET salary = 11000\nWHERE last_name = 'Greene';\n\nCOMMIT;\n\nSELECT\n\nPurpose\n\nUse a SELECT statement or subquery to retrieve data from one or more tables, object tables, views, object views, or materialized views.\n\nIf part or all of the result of a SELECT statement is equivalent to an existing materialized view, then Oracle Database may use the materialized view in place of one or more tables specified in the SELECT statement. This substitution is called query rewrite. It takes place only if cost optimization is enabled and the QUERY_REWRITE_ENABLED parameter is set to TRUE. To determine whether query write has occurred, use the EXPLAIN PLAN statement.\n\nSee Also:\n\n- Chapter 9, \"SQL Queries and Subqueries\" for general information on queries and subqueries\n- Oracle Database Data Warehousing Guide for more information on materialized views and query rewrite\n- EXPLAIN PLAN on page 18-20\n\nPrerequisites\n\nFor you to select data from a table or materialized view, the table or materialized view must be in your own schema or you must have the SELECT privilege on the table or materialized view.\n\nFor you to select rows from the base tables of a view:\n\n- You must have the SELECT privilege on the view, and\n- Whoever owns the schema containing the view must have the SELECT privilege on the base tables.\n\nThe SELECT ANY TABLE system privilege also allows you to select data from any table or any materialized view or the base table of any view.\n\nTo issue an Oracle Flashback Query using the flashback_query_clause, you must have the SELECT privilege on the objects in the select list. In addition, either you must have FLASHBACK object privilege on the objects in the select list, or you must have FLASHBACK ANY TABLE system privilege.\n\nSyntax\n\nselect:-\n\n(subquery_factoring_clause::= on page 19-5, for_update_clause::= on page 19-13)\n\nsubquery::=\n\n(query_block::= on page 19-5, order_by_clause::= on page 19-13)\n\nquery_block::=\n\n(select_list::= on page 19-6, table_reference::= on page 19-6, join_clause::= on page 19-8, where_clause::= on page 19-9, hierarchical_query_clause::= on page 19-10, group_by_clause::= on page 19-10, model_clause::= on page 19-11)\n\nsubquery_factoring_clause::=\n\nsearch_clause::=\n\nSEARCH {DEPTH | BREADTH} FIRST BY c_alias {ASC | DESC} {NULLS FIRST | NULLS LAST}\n\nSET ordering_column\n\ncycle_clause::=\n\n→ CYCLE → c_alias → SET → cycle_mark_c_alias → TO → cycle_value → DEFAULT → no_cycle_value →\n\nselect_list::=\n\n→ t_alias → . → *\n\n→ query_name\n\n→ schema → . → table\n\n→ view\n\n→ materialized view\n\n→ AS → c_alias\n\n→ expr\n\ntable_reference::=\n\n→ ONLY ( ) query_table_expression )\n\n→ query_table_expression\n\n→ pivot_clause\n\n→ unpivot_clause\n\n→ flashback_query_clause\n\n→ t_alias\n\n(query_table_expression::= on page 19-7, flashback_query_clause::= on page 19-6, pivot_clause::= on page 19-7, unpivot_clause::= on page 19-8)\n\nflashback_query_clause::=\n\n→ VERSIONS BETWEEN ( SCN | TIMESTAMP ) expr MINVALUE AND expr MAXVALUE\n\n→ AS OF ( SCN | TIMESTAMP ) expr\n\nquery_table_expression ::=\n\nquery_name\n\nschema . table\nview\nmaterialized view\nsubquery\ntable_collection_expression\n\npartition_extension_clause\n@ dblink\n@ dblink\nsample_clause\n\n(subquery_restriction_clause := on page 19-8, table_collection_expression := on page 19-8)\n\npivot_clause ::=\n\nPIVOT XML\n\n( aggregate_function ) ( expr ) AS alias\npivot_for_clause pivot_in_clause\n\npivot_for_clause ::=\n\nFOR column\n( column )\n\npivot_in_clause ::=\n\nIN ( expr )\n( subquery )\nANY\n\nunpivot_clause ::= UNPIVOT [INCLUDE | EXCLUDE] NULLS (column [, column] ...) pivot_for_clause unpivot_in_clause\n\nunpivot_in_clause ::= IN (column [, column] ...) AS (constant [, constant] ...)\n\nsample_clause ::= SAMPLE BLOCK (sample_percent) SEED (seed_value)\n\npartition_extension_clause ::= PARTITION (partition) FOR (partition_key_value) SUBPARTITION (subpartition) FOR (subpartition_key_value)\n\nsubquery_restriction_clause ::= WITH {READ ONLY | CHECK OPTION} CONSTRAINT constraint\n\ntable_collection_expression ::= TABLE (collection_expression) (+)\n\njoin_clause ::= table_reference {inner_cross_join_clause | outer_join_clause}\n\ninner_cross_join_clause::=\n\nINNER JOIN table_reference\n ON condition\n USING (column)\n\nCROSS JOIN table_reference\n\nNATURAL INNER JOIN table_reference\n\n(table_reference ::= on page 19-6)\n\nouter_join_clause::=\n\nquery_partition_clause\n outer_join_type JOIN\n NATURAL outer_join_type JOIN\n\ntable_reference query_partition_clause\n ON condition\n USING (column)\n\n(table_reference ::= on page 19-6, query_partition_clause ::= on page 19-9)\n\nquery_partition_clause::=\n\nPARTITION BY expr\n , expr\n\nouter_join_type::=\n\nFULL OUTER\nLEFT\nRIGHT\n\nwhere_clause::=\n\nWHERE condition\n\nhierarchical_query_clause::=\n\n\\[\n\\begin{align*}\n&\\text{CONNECT BY} \\rightarrow \\text{NOCYCLE} \\rightarrow \\text{AND} \\rightarrow \\text{condition} \\\\\n&\\text{START WITH} \\rightarrow \\text{condition} \\rightarrow \\text{CONNECT BY} \\rightarrow \\text{NOCYCLE} \\rightarrow \\text{AND} \\rightarrow \\text{condition}\n\\end{align*}\n\\]\n\ngroup_by_clause::=\n\n\\[\n\\begin{align*}\n&\\text{GROUP BY} \\rightarrow \\text{expr} \\\\\n&\\quad \\text{rollup_cube_clause} \\\\\n&\\quad \\text{grouping_sets_clause}\n\\end{align*}\n\\]\n\n(rollup_cube_clause::= on page 19-10, grouping_sets_clause::= on page 19-10)\n\nrollup_cube_clause::=\n\n\\[\n\\begin{align*}\n&\\{\\text{ROLLUP} \\mid \\text{CUBE}\\} \\rightarrow (\\text{grouping_expression_list}) \\rightarrow\n\\end{align*}\n\\]\n\n(grouping_expression_list::= on page 19-10)\n\ngrouping_sets_clause::=\n\n\\[\n\\begin{align*}\n&\\text{GROUPING SETS} \\rightarrow (\\text{rollup_cube_clause} \\mid \\text{grouping_expression_list}) \\rightarrow\n\\end{align*}\n\\]\n\n(rollup_cube_clause::= on page 19-10, grouping_expression_list::= on page 19-10)\n\ngrouping_expression_list::=\n\n\\[\n\\begin{align*}\n&\\text{expression_list}\n\\end{align*}\n\\]\n\nexpression_list::=\n\n\\[\n\\begin{align*}\n&\\text{expr} \\\\\n&\\quad \\text{expr}\n\\end{align*}\n\\]\n\nmodel_clause ::=\n\nMODEL cell_reference_options return_rows_clause reference_model main_model\n\n(cell_reference_options::= on page 19-11, return_rows_clause::= on page 19-11, reference_model::= on page 19-11, main_model::= on page 19-11)\n\ncell_reference_options ::=\n\nIGNORE KEEP NAV UNIQUE DIMENSION SINGLE REFERENCE\n\nreturn_rows_clause ::=\n\nRETURN UPDATED ALL ROWS\n\nreference_model ::=\n\nREFERENCE reference_model_name ON ( subquery ) model_column_clauses cell_reference_options\n\n(model_column_clauses::= on page 19-11, cell_reference_options::= on page 19-11)\n\nmain_model ::=\n\nMAIN main_model_name model_column_clauses cell_reference_options model_rules_clause\n\n(model_column_clauses::= on page 19-11, cell_reference_options::= on page 19-11, model_rules_clause::= on page 19-12)\n\nmodel_column_clauses ::=\n\nPARTITION BY ( expr c_alias ) DIMENSION BY ( expr c_alias ) MEASURES ( expr c_alias )\n\nmodel_column ::=\n\nexpr AS c_alias\n\nmodel_rules_clause ::=\n\nRULES\n UPDATE\n UPSERT ALL\n AUTOMATIC SEQUENTIAL ORDER\n model_iterate_clause\n\n(model_iterate_clause ::= on page 19-12, cell_assignment ::= on page 19-12, order_by_clause ::= on page 19-13)\n\nmodel_iterate_clause ::=\n\nITERATE ( number ) UNTIL ( condition )\n\ncell_assignment ::=\n\nmeasure_column ( )\n condition\n expr\n single_column_for_loop\n multi_column_for_loop\n\n(single_column_for_loop ::= on page 19-12, multi_column_for_loop ::= on page 19-12)\n\nsingle_column_for_loop ::=\n\nFOR dimension_column\n IN ( literal subquery )\n LIKE pattern FROM literal TO literal\n INCREMENT literal\n DECREMENT literal\n\nmulti_column_for_loop ::=\n\nFOR ( )\n dimension_column ( )\n IN ( )\n IN ( literal subquery )\n\n**Semantics**\n\n**subquery_factoring_clause**\n\nThe `WITH query_name` clause lets you assign a name to a subquery block. You can then reference the subquery block multiple places in the query by specifying `query_name`. Oracle Database optimizes the query by treating the query name as either an inline view or as a temporary table.\n\nThe column aliases following the `query_name` and the set operators separating multiple subqueries in the `AS` clause are valid and required for recursive subquery factoring. The `search_clause` and `cycle_clause` are valid only for recursive subquery factoring but are not required. See “Recursive Subquery Factoring” on page 19-13\n\nYou can specify this clause in any top-level `SELECT` statement and in most types of subqueries. The query name is visible to the main query and to all subsequent subqueries. For recursive subquery factoring, the query name is even visible to the subquery that defines the query name itself.\n\n**Recursive Subquery Factoring** If a `subquery_factoring_clause` refers to its own `query_name` in the subquery that defines it, then the `subquery_factoring_clause` is said to be **recursive**. A recursive `subquery_factoring_clause` must contain two query blocks: the first is the **anchor member** and the second is the **recursive member**. The anchor member must appear before the recursive member, and it cannot reference `query_name`. The anchor member can be composed of one or more query blocks combined by the set operators: `UNION ALL`, `UNION`, `INTERSECT` or `MINUS`. The recursive member must follow the anchor member and must reference `query_name` exactly once. You must combine the recursive member with the anchor member using the `UNION ALL` set operator.\n\nThe number of column aliases following `WITH query_name` and the number of columns in the `SELECT` lists of the anchor and recursive query blocks must be the same.\n\nThe recursive member cannot contain any of the following elements:\n\n- The `DISTINCT` keyword or a `GROUP BY` clause\n\n- The `model_clause`\n- An aggregate function. However, analytic functions are permitted in the select list.\n- Subqueries that refer to `query_name`.\n- Outer joins that refer to `query_name` as the right table.\n\n**search_clause** Use the `SEARCH` clause to specify an ordering for the rows.\n\n- Specify `BREADTH FIRST BY` if you want sibling rows returned before any child rows are returned.\n- Specify `DEPTH FIRST BY` if you want child rows returned before any siblings rows are returned.\n- Sibling rows are ordered by the columns listed after the `BY` keyword.\n- The `c_alias` list following the `SEARCH` keyword must contain column names from the column alias list for `query_name`.\n- The `ordering_column` is automatically added to the column list for the query name. The query that selects from `query_name` can include an `ORDER BY` on `ordering_column` to return the rows in the order that was specified by the `SEARCH` clause.\n\n**cycle_clause** Use the `CYCLE` clause to mark cycles in the recursion.\n\n- The `c_alias` list following the `CYCLE` keyword must contain column names from the column alias list for `query_name`. Oracle Database uses these columns to detect a cycle.\n- `cycle_value` and `no_cycle_value` should be character strings of length 1.\n- If a cycle is detected, then the cycle mark column specified by `cycle_mark_c_alias` for the row causing the cycle is set to the value specified for `cycle_value`. The recursion will then stop for this row. That is, it will not look for child rows for the offending row, but it will continue for other noncyclic rows.\n- If no cycles are found, then the cycle mark column is set to the default value specified for `no_cycle_value`.\n- The cycle mark column is automatically added to the column list for the `query_name`.\n- A row is considered to form a cycle if one of its ancestor rows has the same values for the cycle columns.\n\nIf you omit the `CYCLE` clause, then the recursive `WITH` clause returns an error if cycles are discovered. In this case, a row forms a cycle if one of its ancestor rows has the same values for all the columns in the column alias list for `query_name` that are referenced in the `WHERE` clause of the recursive member.\n\n**Restrictions on Subquery Factoring** This clause is subject to the following restrictions:\n\n- You can specify only one `subquery_factoring_clause` in a single SQL statement. Any `query_name` defined in the `subquery_factoring_clause` can be used in any subsequent named query block in the `subquery_factoring_clause`.\n- In a compound query with set operators, you cannot use the `query_name` for any of the component queries, but you can use the `query_name` in the `FROM` clause of any of the component queries.\n\n- You cannot specify duplicate names in the column alias list for `query_name`.\n- The name used for the `ordering_column` has to be different from the name used for `cycle_mark_c_alias`.\n- The `ordering_column` and cycle mark column names cannot already be in the column alias list for `query_name`.\n\n**See Also:**\n- *Oracle Database Concepts* for information about inline views\n- \"Subquery Factoring: Example\" on page 19-36\n- \"Recursive Subquery Factoring: Examples\" on page 19-37\n\n**hint**\n\nSpecify a comment that passes instructions to the optimizer on choosing an execution plan for the statement.\n\n**See Also:** \"Hints\" on page 3-73 for the syntax and description of hints\n\n**DISTINCT | UNIQUE**\n\nSpecify `DISTINCT` or `UNIQUE` if you want the database to return only one copy of each set of duplicate rows selected. These two keywords are synonymous. Duplicate rows are those with matching values for each expression in the select list.\n\n**Restrictions on DISTINCT and UNIQUE Queries** These types of queries are subject to the following restrictions:\n\n- When you specify `DISTINCT` or `UNIQUE`, the total number of bytes in all select list expressions is limited to the size of a data block minus some overhead. This size is specified by the initialization parameter `DB_BLOCK_SIZE`.\n- You cannot specify `DISTINCT` if the `select_list` contains LOB columns.\n\n**ALL**\n\nSpecify `ALL` if you want the database to return all rows selected, including all copies of duplicates. The default is `ALL`.\n\n***(all-column wildcard)***\n\nSpecify the all-column wildcard (asterisk) to select all columns, excluding pseudocolumns, from all tables, views, or materialized views listed in the `FROM` clause. The asterisk can be preceded with a table alias specified in the `FROM` clause of the same subquery. The columns are returned in the order indicated by the `COLUMN_ID` column of the `*_TAB_COLUMNS` data dictionary view for the table, view, or materialized view.\n\nIf you are selecting from a table rather than from a view or a materialized view, then columns that have been marked as `UNUSED` by the `ALTER TABLE SET UNUSED` statement are not selected.\n\n**See Also:** `ALTER TABLE` on page 12-2, \"Simple Query Examples\" on page 19-40, and \"Selecting from the DUAL Table: Example\" on page 19-57\n\nselect_list\n\nThe `select_list` lets you specify the columns you want to retrieve from the database.\n\nquery_name\n\nFor `query_name`, specify a name already specified in the `subquery_factoring_clause`. You must have specified the `subquery_factoring_clause` in order to specify `query_name` in the `select_list`. If you specify `query_name` in the `select_list`, then you also must specify `query_name` in the `query_table_expression` (FROM clause).\n\ntable.* | view.* | materialized view.*\n\nSpecify the object name followed by a period and the asterisk to select all columns from the specified table, view, or materialized view. Oracle Database returns a set of columns in the order in which the columns were specified when the object was created. A query that selects rows from two or more tables, views, or materialized views is a join.\n\nYou can use the schema qualifier to select from a table, view, or materialized view in a schema other than your own. If you omit `schema`, then the database assumes the table, view, or materialized view is in your own schema.\n\nSee Also: \"Joins\" on page 9-11\n\nexpr\n\nSpecify an expression representing the information you want to select. A column name in this list can be qualified with `schema` only if the table, view, or materialized view containing the column is qualified with `schema` in the FROM clause. If you specify a member method of an object type, then you must follow the method name with parentheses even if the method takes no arguments.\n\nSee Also: \"Selecting Sequence Values: Examples\" on page 19-58\n\nc_alias\n\nSpecify an alias for the column expression. Oracle Database will use this alias in the column heading of the result set. The AS keyword is optional. The alias effectively renames the select list item for the duration of the query. The alias can be used in the `order_by_clause` but not other clauses in the query.\n\nSee Also:\n\n- Oracle Database Data Warehousing Guide for information on using the `expr AS c_alias` syntax with the UNION ALL operator in queries of multiple materialized views\n- \"About SQL Expressions\" on page 6-1 for the syntax of `expr`\n\nRestrictions on the Select List\n\nThe select list is subject to the following restrictions:\n\n- If you also specify a `group_by_clause` in this statement, then this select list can contain only the following types of expressions:\n - Constants\n - Aggregate functions and the functions USER, UID, and SYSDATE\n - Expressions identical to those in the `group_by_clause`. If the `group_by_clause` is in a subquery, then all columns in the select list of the subquery must match the GROUP BY columns in the subquery. If the select list and\n\nGROUP BY columns of a top-level query or of a subquery do not match, then the statement results in ORA-00979.\n\n- Expressions involving the preceding expressions that evaluate to the same value for all rows in a group\n\n- You can select a rowid from a join view only if the join has one and only one key-preserved table. The rowid of that table becomes the rowid of the view.\n\nSee Also: Oracle Database Administrator’s Guide for information on key-preserved tables\n\n- If two or more tables have some column names in common, and if you are specifying a join in the FROM clause, then you must qualify column names with names of tables or table aliases.\n\n**FROM Clause**\n\nThe FROM clause lets you specify the objects from which data is selected.\n\n**query_table_expression**\n\nUse the query_table_expression clause to identify a table, view, materialized view, partition, or subpartition, or to specify a subquery that identifies the objects.\n\nSee Also: “Using Subqueries: Examples” on page 19-50\n\n**ONLY** The ONLY clause applies only to views. Specify ONLY if the view in the FROM clause is a view belonging to a hierarchy and you do not want to include rows from any of its subviews.\n\n**flashback_query_clause**\n\nUse the flashback_query_clause to retrieve past data from a table, view, or materialized view.\n\nThis clause implements SQL-driven Flashback, which lets you specify a different system change number or timestamp for each object in the select list. You can also implement session-level Flashback using the DBMS_FLASHBACK package.\n\nA Flashback Query lets you retrieve a history of changes made to a row. You can retrieve the corresponding identifier of the transaction that made the change using the VERSIONS_XID pseudocolumn. You can also retrieve information about the transaction that resulted in a particular row version by issuing an Oracle Flashback Transaction Query. You do this by querying the FLASHBACK_TRANSACTION_QUERY data dictionary view for a particular transaction ID.\n\n**AS OF** Specify AS OF to retrieve the single version of the rows returned by the query at a particular change number (SCN) or timestamp. If you specify SCN, then expr must evaluate to a number. If you specify TIMESTAMP, then expr must evaluate to a timestamp value. Oracle Database returns rows as they existed at the specified system change number or time.\n\n**VERSIONS** Specify VERSIONS to retrieve multiple versions of the rows returned by the query. Oracle Database returns all committed versions of the rows that existed between two SCNs or between two timestamp values. The rows returned include deleted and subsequently reinserted versions of the rows.\n\n- Specify BETWEEN SCN ... to retrieve the versions of the row that existed between two SCNs. Both expressions must evaluate to a number. MINVALUE and\n\nMAXVALUE resolve to the SCN of the oldest and most recent data available, respectively.\n\n- Specify BETWEEN TIMESTAMP ... to retrieve the versions of the row that existed between two timestamps. Both expressions must evaluate to a timestamp value. MINVALUE and MAXVALUE resolve to the timestamp of the oldest and most recent data available, respectively.\n\nOracle Database provides a group of version query pseudocolumns that let you retrieve additional information about the various row versions. Refer to \"Version Query Pseudocolumns\" on page 2-5 for more information.\n\nWhen both clauses are used together, the AS OF clause determines the SCN or moment in time from which the database issues the query. The VERSIONS clause determines the versions of the rows as seen from the AS OF point. The database returns null for a row version if the transaction started before the first BETWEEN value or ended after the AS OF point.\n\n**Restrictions on Flashback Queries** These queries are subject to the following restrictions:\n\n- You cannot specify a subquery in the expression of the AS OF clause.\n- You cannot use the VERSIONS clause in flashback queries to temporary or external tables, or tables that are part of a cluster.\n- You cannot use the VERSIONS clause in flashback queries to views. However, you can use the VERSIONS syntax in the defining query of a view.\n- You cannot specify this clause if you have specified query_name in the query_table_expression.\n\n**See Also:**\n\n- *Oracle Database Advanced Application Developer’s Guide* for more information on Oracle Flashback Query\n- “Using Flashback Queries: Example” on page 19-41\n- *Oracle Database Advanced Application Developer’s Guide* and *Oracle Database PL/SQL Packages and Types Reference* for information about session-level Flashback using the DBMS_FLASHBACK package\n- *Oracle Database Administrator’s Guide* and to the description of FLASHBACK_TRANSACTION_QUERY in the *Oracle Database Reference* for more information about transaction history\n\n**partition_extension_clause** For PARTITION or SUBPARTITION, specify the name or key value of the partition or subpartition within table from which you want to retrieve data.\n\nFor range- and list-partitioned data, as an alternative to this clause, you can specify a condition in the WHERE clause that restricts the retrieval to one or more partitions of table. Oracle Database will interpret the condition and fetch data from only those partitions. It is not possible to formulate such a WHERE condition for hash-partitioned data.\n\n**See Also:** “References to Partitioned Tables and Indexes” on page 3-116 and “Selecting from a Partition: Example” on page 19-41\n\nFor `dblink`, specify the complete or partial name for a database link to a remote database where the table, view, or materialized view is located. This database need not be an Oracle Database.\n\n**See Also:**\n\n- \"References to Objects in Remote Databases\" on page 3-114 for more information on referring to database links\n- \"Distributed Queries\" on page 9-16 for more information about distributed queries and \"Using Distributed Queries: Example\" on page 19-57\n\nIf you omit `dblink`, then the database assumes that the table, view, or materialized view is on the local database.\n\n**Restrictions on Database Links** Database links are subject to the following restrictions:\n\n- You cannot query a user-defined type or an object REF on a remote table.\n- You cannot query columns of type ANYTYPE, ANYDATA, or ANYDATASET from remote tables.\n\n**table | view | materialized view** Specify the name of a table, view, or materialized view from which data is selected.\n\n**sample_clause**\n\nThe `sample_clause` lets you instruct the database to select from a random sample of data from the table, rather than from the entire table.\n\n**See Also:** \"Selecting a Sample: Examples\" on page 19-41\n\n**BLOCK** `BLOCK` instructs the database to attempt to perform random block sampling instead of random row sampling.\n\nBlock sampling is possible only during full table scans or index fast full scans. If a more efficient execution path exists, then Oracle Database does not perform block sampling. If you want to guarantee block sampling for a particular table or index, then use the FULL or INDEX_FFS hint.\n\n**sample_percent** For `sample_percent`, specify the percentage of the total row or block count to be included in the sample. The value must be in the range .000001 to, but not including, 100. This percentage indicates the probability of each row, or each cluster of rows in the case of block sampling, being selected as part of the sample. It does not mean that the database will retrieve exactly `sample_percent` of the rows of `table`.\n\n**Caution:** The use of statistically incorrect assumptions when using this feature can lead to incorrect or undesirable results.\n\n**SEED seed_value** Specify this clause to instruct the database to attempt to return the same sample from one execution to the next. The `seed_value` must be an integer between 0 and 4294967295. If you omit this clause, then the resulting sample will change from one execution to the next.\n\nRestriction on Sampling During Queries When sampling from a view, you must ensure that the view is key preserved. One way to do this is to use a CREATE TABLE ... AS subquery statement to materialize the result of an arbitrary query and then perform sampling on the resulting query.\n\nRestrictions on sample_clause You cannot specify the SAMPLE clause in a subquery in a DML statement.\n\nsubquery_restriction_clause The subquery_restriction_clause lets you restrict the subquery in one of the following ways:\n\nWITH READ ONLY Specify WITH READ ONLY to indicate that the table or view cannot be updated.\n\nWITH CHECK OPTION Specify WITH CHECK OPTION to indicate that Oracle Database prohibits any changes to the table or view that would produce rows that are not included in the subquery. When used in the subquery of a DML statement, you can specify this clause in a subquery in the FROM clause but not in subquery in the WHERE clause.\n\nCONSTRAINT constraint Specify the name of the CHECK OPTION constraint. If you omit this identifier, then Oracle automatically assigns the constraint a name of the form SYS_Cn, where n is an integer that makes the constraint name unique within the database.\n\nSee Also: \"Using the WITH CHECK OPTION Clause: Example\" on page 19-48\n\ntable_collection_expression\n\nThe table_collection_expression lets you inform Oracle that the value of collection_expression should be treated as a table for purposes of query and DML operations. The collection_expression can be a subquery, a column, a function, or a collection constructor. Regardless of its form, it must return a collection value—that is, a value whose type is nested table or varray. This process of extracting the elements of a collection is called collection unnesting.\n\nThe optional plus (+) is relevant if you are joining the TABLE collection expression with the parent table. The + creates an outer join of the two, so that the query returns rows from the outer table even if the collection expression is null.\n\nNote: In earlier releases of Oracle, when collection_expression was a subquery, table_collection_expression was expressed as THE subquery. That usage is now deprecated.\n\nThe collection_expression can reference columns of tables defined to its left in the FROM clause. This is called left correlation. Left correlation can occur only in table_collection_expression. Other subqueries cannot contain references to columns defined outside the subquery.\n\nThe optional (+) lets you specify that table_collection_expression should return a row with all fields set to null if the collection is null or empty. The (+) is valid only if collection_expression uses left correlation. The result is similar to that of an outer join.\n\nWhen you use the (+) syntax in the WHERE clause of a subquery in an UPDATE or DELETE operation, you must specify two tables in the FROM clause of the subquery. Oracle Database ignores the outer join syntax unless there is a join in the subquery itself.\n\n**See Also:**\n\n- \"Outer Joins\" on page 9-12\n- \"Table Collections: Examples\" on page 19-54 and \"Collection Unnesting: Examples\" on page 19-54\n\n**t_alias**\n\nSpecify a **correlation name**, which is alias for the table, view, materialized view, or subquery for evaluating the query. This alias is required if the select list references any object type attributes or object type methods. Correlation names are most often used in a correlated query. Other references to the table, view, or materialized view throughout the query must refer to this alias.\n\n**See Also:** \"Using Correlated Subqueries: Examples\" on page 19-57\n\n**pivot_clause**\n\nThe **pivot_clause** lets you write cross-tabulation queries that rotate rows into columns, aggregating data in the process of the rotation. The output of a pivot operation typically includes more columns and fewer rows than the starting data set. The **pivot_clause** performs the following steps:\n\n1. The **pivot_clause** computes the aggregation functions specified at the beginning of the clause. Aggregation functions must specify a GROUP BY clause to return multiple values, yet the **pivot_clause** does not contain an explicit GROUP BY clause. Instead, the **pivot_clause** performs an implicit GROUP BY. The implicit grouping is based on all the columns not referred to in the **pivot_clause**, along with the set of values specified in the **pivot_in_clause**.\n\n2. The grouping columns and aggregated values calculated in Step 1 are configured to produce the following cross-tabular output:\n - All the implicit grouping columns not referred to in the **pivot_clause**, followed by\n - New columns corresponding to values in the **pivot_in_clause**. Each aggregated value is transposed to the appropriate new column in the cross-tabulation. If you specify the XML keyword, then the result is a single new column that expresses the data as an XML string.\n\nThe subclauses of the **pivot_clause** have the following semantics:\n\n**XML** The optional XML keyword generates XML output for the query. The XML keyword permits the **pivot_in_clause** to contain either a subquery or the wildcard keyword ANY. Subqueries and ANY wildcards are useful when the **pivot_in_clause** values are not known in advance. With XML output, the values of the pivot column are evaluated at execution time. You cannot specify XML when you specify explicit pivot values using expressions in the **pivot_in_clause**.\n\nWhen XML output is generated, the aggregate function is applied to each distinct pivot value, and the database returns a column of XMLType containing an XML string for all value and measure pairs.\n\nFor `expr`, specify an expression that evaluates to a constant value of a pivot column. You can optionally provide an alias for each pivot column value. If there is no alias, the column heading becomes a quoted identifier.\n\nA subquery is used only in conjunction with the `XML` keyword. When you specify a subquery, all values found by the subquery are used for pivoting. The output is not the same cross-tabular format returned by non-XML pivot queries. Instead of multiple columns specified in the `pivot_in_clause`, the subquery produces a single XML string column. The XML string for each row holds aggregated data corresponding to the implicit `GROUP BY` value of that row. The XML string for each output row includes all pivot values found by the subquery, even if there are no corresponding rows in the input data.\n\nThe subquery must return a list of unique values at the execution time of the pivot query. If the subquery does not return a unique value, then Oracle Database raises a run-time error. Use the `DISTINCT` keyword in the subquery if you are not sure the query will return unique values.\n\nThe `ANY` keyword is used only in conjunction with the `XML` keyword. The `ANY` keyword acts as a wildcard and is similar in effect to `subquery`. The output is not the same cross-tabular format returned by non-XML pivot queries. Instead of multiple columns specified in the `pivot_in_clause`, the `ANY` keyword produces a single XML string column. The XML string for each row holds aggregated data corresponding to the implicit `GROUP BY` value of that row. However, in contrast to the behavior when you specify `subquery`, the `ANY` wildcard produces an XML string for each output row that includes only the pivot values found in the input data corresponding to that row.\n\n**See Also:** *Oracle Database Data Warehousing Guide* for more information about `PIVOT` and `UNPIVOT` and \"Using PIVOT and UNPIVOT: Examples\" on page 19-48\n\nThe `unpivot_clause` rotates columns into rows.\n\n- The `INCLUDE | EXCLUDE NULLS` clause gives you the option of including or excluding null-valued rows. `INCLUDE NULLS` causes the unpivot operation to include null-valued rows; `EXCLUDE NULLS` eliminates null-values rows from the return set. If you omit this clause, then the unpivot operation excludes nulls.\n\n- For `column`, specify a name for each output column that will hold measure values, such as `sales_quantity`.\n\n- In the `pivot_for_clause`, specify a name for each output column that will hold descriptor values, such as quarter or product.\n\n- In the `unpivot_in_clause`, specify the input data columns whose names will become values in the output columns of the `pivot_for_clause`. These input data columns have names specifying a category value, such as Q1, Q2, Q3, Q4. The optional `alias` lets you map the column name to any desired value.\n\nThe unpivot operation turns a set of value columns into one column. Therefore, the data types of all the value columns must be in the same data type group, such as numeric or character.\n\n- If all the value columns are `CHAR`, then the unpivoted column is `CHAR`. If any value column is `VARCHAR2`, then the unpivoted column is `VARCHAR2`.\n\nIf all the value columns are NUMBER, then the unpivoted column is NUMBER. If any value column is BINARY_DOUBLE, then the unpivoted column is BINARY_DOUBLE. If no value column is BINARY_DOUBLE but any value column is BINARY_FLOAT, then the unpivoted column is BINARY_FLOAT.\n\n**join_clause**\n\nUse the appropriate *join_clause* syntax to identify tables that are part of a join from which to select data. The *inner_cross_join_clause* lets you specify an inner or cross join. The *outer_join_clause* lets you specify an outer join.\n\nWhen you join more than two row sources, you can use parentheses to override default precedence. For example, the following syntax:\n\n```sql\nSELECT ... FROM a JOIN (b JOIN c) ...\n```\n\nresults in a join of b and c, and then a join of that result set with a.\n\n**See Also:** \"Joins\" on page 9-11 for more information on joins, \"Using Join Queries: Examples\" on page 19-49, \"Using Self Joins: Example\" on page 19-50, and \"Using Outer Joins: Examples\" on page 19-51\n\n**Inner Joins**\n\nInner joins return only those rows that satisfy the join condition.\n\n**INNER** Specify INNER to explicitly specify an inner join.\n\n**JOIN** The JOIN keyword explicitly states that a join is being performed. You can use this syntax to replace the comma-delimited table expressions used in WHERE clause joins with FROM clause join syntax.\n\n**ON condition** Use the ON clause to specify a join condition. Doing so lets you specify join conditions separate from any search or filter conditions in the WHERE clause.\n\n**USING (column)** When you are specifying an equijoin of columns that have the same name in both tables, the USING column clause indicates the columns to be used. You can use this clause only if the join columns in both tables have the same name. Within this clause, do not qualify the column name with a table name or table alias.\n\n**Cross Joins**\n\nThe CROSS keyword indicates that a cross join is being performed. A cross join produces the cross-product of two relations and is essentially the same as the comma-delimited Oracle Database notation.\n\n**Outer Joins**\n\nOuter joins return all rows that satisfy the join condition and also returns some or all of those rows from one table for which no rows from the other satisfy the join condition. You can specify two types of outer joins: a conventional outer join using the table_reference syntax on both sides of the join, or a partitioned outer join using the query_partition_clause on one side or the other. A partitioned outer join is similar to a conventional outer join except that the join takes place between the outer table and each partition of the inner table. This type of join lets you selectively make sparse data more dense along the dimensions of interest. This process is called **data densification**.\n\nouter_join_type The outer_join_type indicates the kind of outer join being performed:\n\n- Specify RIGHT to indicate a right outer join.\n- Specify LEFT to indicate a left outer join.\n- Specify FULL to indicate a full or two-sided outer join. In addition to the inner join, rows from both tables that have not been returned in the result of the inner join will be preserved and extended with nulls.\n- You can specify the optional OUTER keyword following RIGHT, LEFT, or FULL to explicitly clarify that an outer join is being performed.\n\nquery_partition_clause The query_partition_clause lets you define a partitioned outer join. Such a join extends the conventional outer join syntax by applying the outer join to partitions returned by the query. Oracle Database creates a partition of rows for each expression you specify in the PARTITION BY clause. The rows in each query partition have same value for the PARTITION BY expression.\n\nThe query_partition_clause can be on either side of the outer join. The result of a partitioned outer join is a UNION of the outer joins of each of the partitions in the partitioned result set and the table on the other side of the join. This type of result is useful for filling gaps in sparse data, which simplifies analytic calculations.\n\nIf you omit this clause, then the database treats the entire table expression—everything specified in table_reference—as a single partition, resulting in a conventional outer join.\n\nTo use the query_partition_clause in an analytic function, use the upper branch of the syntax (without parentheses). To use this clause in a model query (in the model_column_clauses) or a partitioned outer join (in the outer_join_clause), use the lower branch of the syntax (with parentheses).\n\nRestrictions on Partitioned Outer Joins Partitioned outer joins are subject to the following restrictions:\n\n- You can specify the query_partition_clause on either the right or left side of the join, but not both.\n- You cannot specify a FULL partitioned outer join.\n- If you specify the query_partition_clause in an outer join with an ON clause, then you cannot specify a subquery in the ON condition.\n\nSee Also:\n- \"Outer Joins\" on page 9-12 for additional rules and restrictions pertaining to outer joins\n- Oracle Database Data Warehousing Guide for a complete discussion of partitioned outer joins and data densification\n- \"Using Partitioned Outer Joins: Examples\" on page 19-52\n\nON condition Use the ON clause to specify a join condition. Doing so lets you specify join conditions separate from any search or filter conditions in the WHERE clause.\n\nRestriction on the ON condition Clause You cannot specify this clause with a NATURAL outer join.\n\n**USING column** In an outer join with the USING clause, the query returns a single column which is a coalesce of the two matching columns in the join. The coalesce functions as follows:\n\n\\[\n\\text{COALESCE (a, b)} = \\begin{cases} \na & \\text{if } a \\text{ NOT NULL}, \\\\\nb & \\text{else}.\n\\end{cases}\n\\]\n\nTherefore:\n\n- A left outer join returns all the common column values from the left table in the FROM clause.\n\n- A right outer join returns all the common column values from the right table in the FROM clause.\n\n- A full outer join returns all the common column values from both joined tables.\n\n**Restriction on the USING column Clause**\n\n- Within this clause, do not qualify the column name with a table name or table alias.\n\n- You cannot specify a LOB column or a collection column in the USING column clause.\n\n- You cannot specify this clause with a NATURAL outer join.\n\n**See Also:** \"Using Outer Joins: Examples\" on page 19-51\n\n**NATURAL JOIN** The NATURAL keyword indicates that a natural join is being performed. A natural join is based on all columns in the two tables that have the same name. It selects rows from the two tables that have equal values in the relevant columns. When specifying columns that are involved in the natural join, do not qualify the column name with a table name or table alias.\n\nOn occasion, the table pairings in natural or cross joins may be ambiguous. For example, consider the following join syntax:\n\n\\[\na \\text{ NATURAL LEFT JOIN } b \\text{ LEFT JOIN } c \\text{ ON } b.c1 = c.c1\n\\]\n\nThis example can be interpreted in either of the following ways:\n\n\\[\na \\text{ NATURAL LEFT JOIN (b LEFT JOIN c ON b.c1 = c.c1)}\n\\]\n\\[\n(a \\text{ NATURAL LEFT JOIN b}) \\text{ LEFT JOIN c ON b.c1 = c.c1}\n\\]\n\nTo avoid this ambiguity, you can use parentheses to specify the pairings of joined tables. In the absence of such parentheses, the database uses left associativity, pairing the tables from left to right.\n\n**Restriction on Natural Joins** You cannot specify a LOB column, columns of ANYTYPE, ANYDATA, or ANYDATASET, or a collection column as part of a natural join.\n\n**where_clause**\n\nThe WHERE condition lets you restrict the rows selected to those that satisfy one or more conditions. For *condition*, specify any valid SQL condition.\n\nIf you omit this clause, then the database returns all rows from the tables, views, or materialized views in the FROM clause.\n\nNote: If this clause refers to a DATE column of a partitioned table or index, then the database performs partition pruning only if:\n\n- You created the table or index partitions by fully specifying the year using the TO_DATE function with a 4-digit format mask, and\n- You specify the date in the where_clause of the query using the TO_DATE function and either a 2- or 4-digit format mask.\n\nSee Also:\n- Chapter 7, \"Conditions\" for the syntax description of condition\n- \"Selecting from a Partition: Example\" on page 19-41\n\n**hierarchical_query_clause**\n\nThe hierarchical_query_clause lets you select rows in a hierarchical order.\n\nSELECT statements that contain hierarchical queries can contain the LEVEL pseudocolumn in the select list. LEVEL returns the value 1 for a root node, 2 for a child node of a root node, 3 for a grandchild, and so on. The number of levels returned by a hierarchical query may be limited by available user memory.\n\nOracle processes hierarchical queries as follows:\n\n- A join, if present, is evaluated first, whether the join is specified in the FROM clause or with WHERE clause predicates.\n- The CONNECT BY condition is evaluated.\n- Any remaining WHERE clause predicates are evaluated.\n\nIf you specify this clause, then do not specify either ORDER BY or GROUP BY, because they will destroy the hierarchical order of the CONNECT BY results. If you want to order rows of siblings of the same parent, then use the ORDER SIBLINGS BY clause.\n\nSee Also: \"Hierarchical Queries\" on page 9-3 for a discussion of hierarchical queries and \"Using the LEVEL Pseudocolumn: Examples\" on page 19-55\n\n**START WITH Clause**\n\nSpecify a condition that identifies the row(s) to be used as the root(s) of a hierarchical query. Oracle Database uses as root(s) all rows that satisfy this condition. If you omit this clause, then the database uses all rows in the table as root rows.\n\n**CONNECT BY Clause**\n\nSpecify a condition that identifies the relationship between parent rows and child rows of the hierarchy. The connect_by_condition can be any condition as described in Chapter 7, \"Conditions\". However, it must use the PRIOR operator to refer to the parent row.\n\nSee Also:\n- Chapter 2, \"Pseudocolumns\" for more information on LEVEL\n- \"Hierarchical Queries\" on page 9-3 for general information on hierarchical queries\n- \"Hierarchical Query Examples\" on page 19-44\n\ngroup_by_clause\n\nSpecify the GROUP BY clause if you want the database to group the selected rows based on the value of expr(s) for each row and return a single row of summary information for each group. If this clause contains CUBE or ROLLUP extensions, then the database produces superaggregate groupings in addition to the regular groupings.\n\nExpressions in the GROUP BY clause can contain any columns of the tables, views, or materialized views in the FROM clause, regardless of whether the columns appear in the select list.\n\nThe GROUP BY clause groups rows but does not guarantee the order of the result set. To order the groupings, use the ORDER BY clause.\n\nIf the NLS_SORT parameter has a setting other than BINARY and the NLS_COMP parameter is set to LINGUISTIC, then expression values are compared linguistically according to the linguistic definition specified in NLS_SORT to decide if they are equal and therefore belong to the same group. When character values are compared linguistically for GROUP BY, they are first transformed to collation keys and then compared like RAW values. The collation keys are the same values that are returned by the function NLSSORT and are subject to the same restrictions that are described in \"NLSSORT\" on page 5-120. As a result of these restrictions, two values may compare as linguistically equal and be grouped together if they do not differ in the prefix that was used to produce the collation key, even if they differ in the rest of the value.\n\nSee Also:\n\n- Oracle Database Data Warehousing Guide for an expanded discussion and examples of using SQL grouping syntax for data aggregation\n- the GROUP_ID, GROUPING, and GROUPING_ID functions on page 5-81 for examples\n- \"Using the GROUP BY Clause: Examples\" on page 19-42\n\nROLLUP The ROLLUP operation in the simple_grouping_clause groups the selected rows based on the values of the first n, n-1, n-2, ... 0 expressions in the GROUP BY specification, and returns a single row of summary for each group. You can use the ROLLUP operation to produce subtotal values by using it with the SUM function. When used with SUM, ROLLUP generates subtotals from the most detailed level to the grand total. Aggregate functions such as COUNT can be used to produce other kinds of superaggregates.\n\nFor example, given three expressions (n=3) in the ROLLUP clause of the simple_grouping_clause, the operation results in \\( n+1 = 3+1 = 4 \\) groupings.\n\nRows grouped on the values of the first \\( n \\) expressions are called regular rows, and the others are called superaggregate rows.\n\nSee Also: Oracle Database Data Warehousing Guide for information on using ROLLUP with materialized views\n\nCUBE The CUBE operation in the simple_grouping_clause groups the selected rows based on the values of all possible combinations of expressions in the specification. It returns a single row of summary information for each group. You can use the CUBE operation to produce cross-tabulation values.\n\nFor example, given three expressions (n=3) in the CUBE clause of the simple_grouping_clause, the operation results in \\( 2^n = 2^3 = 8 \\) groupings. Rows grouped on\n\nthe values of \\( n \\) expressions are called **regular rows**, and the rest are called superaggregate rows.\n\n**See Also:**\n\n- *Oracle Database Data Warehousing Guide* for information on using CUBE with materialized views\n\n- \"Using the GROUP BY CUBE Clause: Example\" on page 19-43\n\n**GROUPING SETS** GROUPING SETS are a further extension of the GROUP BY clause that let you specify multiple groupings of data. Doing so facilitates efficient aggregation by pruning the aggregates you do not need. You specify just the desired groups, and the database does not need to perform the full set of aggregations generated by CUBE or ROLLUP. Oracle Database computes all groupings specified in the GROUPING SETS clause and combines the results of individual groupings with a UNION ALL operation. The UNION ALL means that the result set can include duplicate rows.\n\nWithin the GROUP BY clause, you can combine expressions in various ways:\n\n- To specify **composite columns**, group columns within parentheses so that the database treats them as a unit while computing ROLLUP or CUBE operations.\n\n- To specify **concatenated grouping sets**, separate multiple grouping sets, ROLLUP, and CUBE operations with commas so that the database combines them into a single GROUP BY clause. The result is a cross-product of groupings from each grouping set.\n\n**See Also:** \"Using the GROUPING SETS Clause: Example\" on page 19-43\n\n**HAVING Clause**\n\nUse the HAVING clause to restrict the groups of returned rows to those groups for which the specified condition is TRUE. If you omit this clause, then the database returns summary rows for all groups.\n\nSpecify GROUP BY and HAVING after the where_clause and hierarchical_query_clause. If you specify both GROUP BY and HAVING, then they can appear in either order.\n\n**See Also:** \"Using the HAVING Condition: Example\" on page 19-44\n\n**Restrictions on the GROUP BY Clause:** This clause is subject to the following restrictions:\n\n- You cannot specify LOB columns, nested tables, or varrays as part of expr.\n\n- The expressions can be of any form except scalar subquery expressions.\n\n- If the group_by_clause references any object type columns, then the query will not be parallelized.\n\n**model_clause**\n\nThe model_clause lets you view selected rows as a multidimensional array and randomly access cells within that array. Using the model_clause, you can specify a series of cell assignments, referred to as rules, that invoke calculations on individual cells and ranges of cells. These rules operate on the results of a query and do not update any database tables.\n\nWhen using the `model_clause` in a query, the `SELECT` and `ORDER BY` clauses must refer only to those columns defined in the `model_column_clauses`.\n\n**See Also:**\n\n- The syntax description of `expr` in \"About SQL Expressions\" on page 6-1 and the syntax description of `condition` in Chapter 7, \"Conditions\"\n- *Oracle Database Data Warehousing Guide* for an expanded discussion and examples\n- \"The MODEL clause: Examples\" on page 19-45\n\n**main_model**\n\nThe `main_model` clause defines how the selected rows will be viewed in a multidimensional array and what rules will operate on which cells in that array.\n\n**model_column_clauses**\n\nThe `model_column_clauses` define and classify the columns of a query into three groups: partition columns, dimension columns, and measure columns. If the `expr` in these three subclauses is a model column, then the column alias (`c_alias`) is optional. If the `expr` is not a model column, then the column alias is required.\n\n**PARTITION BY** The `PARTITION BY` clause specifies the columns that will be used to divide the selected rows into partitions based on the values of the specified columns.\n\n**DIMENSION BY** The `DIMENSION BY` clause specifies the columns that will identify a row within a partition. The values of the dimension columns, along with those of the partition columns, serve as array indexes to the measure columns within a row.\n\n**MEASURES** The `MEASURES` clause identifies the columns on which the calculations can be performed. Measure columns in individual rows are treated like cells that you can reference, by specifying the values for the partition and dimension columns, and update.\n\n**model_column** `model_column` identifies a column to be used in defining the model. A column alias is required if `expr` is not a column name. Refer to \"Model Expressions\" on page 6-11 for information on model expressions.\n\n**cell_reference_options**\n\nUse the `cell_reference_options` clause to specify how null and absent values are treated in rules and how column uniqueness is constrained.\n\n**IGNORE NAV** When you specify `IGNORE NAV`, the database returns the following values for the null and absent values of the data type specified:\n\n- Zero for numeric data types\n- 01-JAN-2000 for datetime data types\n- An empty string for character data types\n- Null for all other data types\n\n**KEEP NAV** When you specify `KEEP NAV`, the database returns null for both null and absent cell values. `KEEP NAV` is the default.\n\n**UNIQUE SINGLE REFERENCE** When you specify UNIQUE SINGLE REFERENCE, the database checks only single-cell references on the right-hand side of the rule for uniqueness, not the entire query result set.\n\n**UNIQUE DIMENSION** When you specify UNIQUE DIMENSION, the database checks that the PARTITION BY and DIMENSION BY columns form a unique key to the query. UNIQUE DIMENSION is the default.\n\n**model_rules_clause**\n\nUse the model_rules_clause to specify the cells to be updated, the rules for updating those cells, and optionally, how the rules are to be applied and processed.\n\nEach rule represents an assignment and consists of a left-hand side and right-hand side. The left-hand side of the rule identifies the cells to be updated by the right-hand side of the rule. The right-hand side of the rule evaluates to the values to be assigned to the cells specified on the left-hand side of the rule.\n\n**UPSERT ALL** UPSERT ALL allows UPSERT behavior for a rule with both positional and symbolic references on the left-hand side of the rule. When evaluating an UPSERT ALL rule, Oracle performs the following steps to create a list of cell references to be upserted:\n\n1. Find the existing cells that satisfy all the symbolic predicates of the cell reference.\n2. Using just the dimensions that have symbolic references, find the distinct dimension value combinations of these cells.\n3. Perform a cross product of these value combinations with the dimension values specified by way of positional references.\n\nPlease refer to *Oracle Database Data Warehousing Guide* for more information on the semantics of UPSERT ALL.\n\n**UPSERT** When you specify UPSERT, the database applies the rules to those cells referenced on the left-hand side of the rule that exist in the multidimensional array, and inserts new rows for those that do not exist. UPSERT behavior applies only when positional referencing is used on the left-hand side and a single cell is referenced. UPSERT is the default. Refer to *cell_assignment* on page 19-31 for more information on positional referencing and single-cell references.\n\nUPDATE and UPSERT can be specified for individual rules as well. When either UPDATE or UPSERT is specified for a specific rule, it takes precedence over the option specified in the RULES clause.\n\n---\n\n**Notes on UPSERT [ALL] and UPDATE:** If an UPSERT ALL, UPSERT, or UPDATE rule does not contain the appropriate predicates, then the database may implicitly convert it to a different type of rule:\n\n- If an UPSERT rule contains an existential predicate, then the rule is treated as an UPDATE rule.\n- An UPSERT ALL rule must have at least one existential predicate and one qualified predicate on its left side.\n - If it has no existential predicate, then it is treated as an UPSERT rule.\n - If it has no qualified predicate, then it is treated as an UPDATE rule.\n\n**UPDATE** When you specify UPDATE, the database applies the rules to those cells referenced on the left-hand side of the rule that exist in the multidimensional array. If the cells do not exist, then the assignment is ignored.\n\n**AUTOMATIC ORDER** When you specify AUTOMATIC ORDER, the database evaluates the rules based on their dependency order. In this case, a cell can be assigned a value once only.\n\n**SEQUENTIAL ORDER** When you specify SEQUENTIAL ORDER, the database evaluates the rules in the order they appear. In this case, a cell can be assigned a value more than once. SEQUENTIAL ORDER is the default.\n\n**ITERATE ... [UNTIL]** Use ITERATE ... [UNTIL] to specify the number of times to cycle through the rules and, optionally, an early termination condition. The parentheses around the UNTIL condition are optional.\n\nWhen you specify ITERATE ... [UNTIL], rules are evaluated in the order in which they appear. Oracle Database returns an error if both AUTOMATIC ORDER and ITERATE ... [UNTIL] are specified in the model_rules_clause.\n\n**cell_assignment**\n\nThe cell_assignment clause, which is the left-hand side of the rule, specifies one or more cells to be updated. When a cell_assignment references a single cell, it is called a **single-cell reference**. When more than one cell is referenced, it is called a **multiple-cell reference**.\n\nAll dimension columns defined in the model_clause must be qualified in the cell_assignment clause. A dimension can be qualified using either symbolic or positional referencing.\n\nA **symbolic reference** qualifies a single dimension column using a Boolean condition like dimension_column=constant. A **positional reference** is one where the dimension column is implied by its position in the DIMENSION BY clause. The only difference between symbolic references and positional references is in the treatment of nulls.\n\nUsing a single-cell symbolic reference such as a\\[x=null,y=2000\\], no cells qualify because x=null evaluates to FALSE. However, using a single-cell positional reference such as a\\[null,2000\\], a cell where x is null and y is 2000 qualifies because null = null evaluates to TRUE. With single-cell positional referencing, you can reference, update, and insert cells where dimension columns are null.\n\nYou can specify a condition or an expression representing a dimension column value using either symbolic or positional referencing. condition cannot contain aggregate functions or the CV function, and condition must reference a single dimension column. expr cannot contain a subquery. Refer to \"Model Expressions\" on page 6-11 for information on model expressions.\n\n**single_column_for_loop**\n\nThe single_column_for_loop clause lets you specify a range of cells to be updated within a single dimension column.\n\nThe IN clause lets you specify the values of the dimension column as either a list of values or as a subquery. When using subquery, it cannot:\n\n- Be a correlated query\n- Return more than 10,000 rows\n\nBe a query defined in the WITH clause\n\nThe FROM clause lets you specify a range of values for a dimension column with discrete increments within the range. The FROM clause can only be used for those columns with a data type for which addition and subtraction is supported. The INCREMENT and DECREMENT values must be positive.\n\nOptionally, you can specify the LIKE clause within the FROM clause. In the LIKE clause, pattern is a character string containing a single pattern-matching character %. This character is replaced during execution with the current incremented or decremented value in the FROM clause.\n\nIf all dimensions other than those used by a FOR loop involve a single-cell reference, then the expressions can insert new rows. The number of dimension value combinations generated by FOR loops is counted as part of the 10,000 row limit of the MODEL clause.\n\nmulti_column_for_loop\n\nThe multi_column_for_loop clause lets you specify a range of cells to be updated across multiple dimension columns. The IN clause lets you specify the values of the dimension columns as either multiple lists of values or as a subquery. When using subquery, it cannot:\n\n- Be a correlated query\n- Return more than 10,000 rows\n- Be a query defined in the WITH clause\n\nIf all dimensions other than those used by a FOR loop involve a single-cell reference, then the expressions can insert new rows. The number of dimension value combinations generated by FOR loops is counted as part of the 10,000 row limit of the MODEL clause.\n\nSee Also: Oracle Database Data Warehousing Guide for more information about using FOR loops in the MODEL clause\n\norder_by_clause\n\nUse the ORDER BY clause to specify the order in which cells on the left-hand side of the rule are to be evaluated. The expr must resolve to a dimension or measure column. If the ORDER BY clause is not specified, then the order defaults to the order of the columns as specified in the DIMENSION BY clause. See order_by_clause on page 19-33 for more information.\n\nRestrictions on the order_by_clause Use of the ORDER BY clause in the model rule is subject to the following restrictions:\n\n- You cannot specify SIBLINGS, position, or c_alias in the order_by_clause of the model_clause.\n- You cannot specify this clause on the left-hand side of the model rule and also specify a FOR loop on the right-hand side of the rule.\n\nexpr\n\nSpecify an expression representing the value or values of the cell or cells specified on the right-hand side of the rule. expr cannot contain a subquery. Refer to \"Model Expressions\" on page 6-11 for information on model expressions.\n\nreturn_rows_clause\n\nThe return_rows_clause lets you specify whether to return all rows selected or only those rows updated by the model rules. ALL is the default.\n\nreference_model\n\nUse the reference_model clause when you need to access multiple arrays from inside the model_clause. This clause defines a read-only multidimensional array based on the results of a query.\n\nThe subclauses of the reference_model clause have the same semantics as for the main_model clause. Refer to cell_reference_options on page 19-29, model_column_clauses on page 19-29, and cell_reference_options on page 19-29.\n\nRestrictions on the reference_model clause\n\nThis clause is subject to the following restrictions:\n\n- PARTITION BY columns cannot be specified for reference models.\n- The subquery of the reference model cannot refer to columns in an outer subquery.\n\nSet Operators: UNION, UNION ALL, INTERSECT, MINUS\n\nThe set operators combine the rows returned by two SELECT statements into a single result. The number and data types of the columns selected by each component query must be the same, but the column lengths can be different. The names of the columns in the result set are the names of the expressions in the select list preceding the set operator.\n\nIf you combine more than two queries with set operators, then the database evaluates adjacent queries from left to right. The parentheses around the subquery are optional. You can use them to specify a different order of evaluation.\n\nRefer to \"The UNION [ALL], INTERSECT, MINUS Operators\" on page 9-8 for information on these operators, including restrictions on their use.\n\norder_by_clause\n\nUse the ORDER BY clause to order rows returned by the statement. Without an order_by_clause, no guarantee exists that the same query executed more than once will retrieve rows in the same order.\n\nSIBLINGS\n\nThe SIBLINGS keyword is valid only if you also specify the hierarchical_query_clause (CONNECT BY). ORDER SIBLINGS BY preserves any ordering specified in the hierarchical query clause and then applies the order_by_clause to the siblings of the hierarchy.\n\nexpr\n\nexpr orders rows based on their value for expr. The expression is based on columns in the select list or columns in the tables, views, or materialized views in the FROM clause.\n\nposition\n\nSpecify position to order rows based on their value for the expression in this position of the select list. The position value must be an integer.\n\nYou can specify multiple expressions in the order_by_clause. Oracle Database first sorts rows based on their values for the first expression. Rows with the same value for the first expression are then sorted based on their values for the second expression, and so on. The database sorts nulls following all others in ascending order and preceding all others in descending order. Refer to \"Sorting Query Results\" on page 9-10 for a discussion of ordering query results.\n\nASC | DESC Specify whether the ordering sequence is ascending or descending. ASC is the default.\n\nNULLS FIRST | NULLS LAST Specify whether returned rows containing null values should appear first or last in the ordering sequence.\n\nNULLS LAST is the default for ascending order, and NULLS FIRST is the default for descending order.\n\nRestrictions on the ORDER BY Clause The following restrictions apply to the ORDER BY clause:\n\n- If you have specified the DISTINCT operator in this statement, then this clause cannot refer to columns unless they appear in the select list.\n\n- An order_by_clause can contain no more than 255 expressions.\n\n- You cannot order by a LOB, LONG, or LONG RAW column, nested table, or varray.\n\n- If you specify a group_by_clause in the same statement, then this order_by_clause is restricted to the following expressions:\n\n - Constants\n - Aggregate functions\n - Analytic functions\n - The functions USER, UID, and SYSDATE\n - Expressions identical to those in the group_by_clause\n - Expressions comprising the preceding expressions that evaluate to the same value for all rows in a group\n\nSee Also: \"Using the ORDER BY Clause: Examples\" on page 19-45\n\nfor_update_clause\n\nThe FOR UPDATE clause lets you lock the selected rows so that other users cannot lock or update the rows until you end your transaction. You can specify this clause only in a top-level SELECT statement, not in subqueries.\n\nNote: Prior to updating a LOB value, you must lock the row containing the LOB. One way to lock the row is with an embedded SELECT ... FOR UPDATE statement. You can do this using one of the programmatic languages or DBMS_LOB package. For more information on lock rows before writing to a LOB, see Oracle Database SecureFiles and Large Objects Developer’s Guide.\n\nNested table rows are not locked as a result of locking the parent table rows. If you want the nested table rows to be locked, then you must lock them explicitly.\n\nRestrictions on the FOR UPDATE Clause This clause is subject to the following restrictions:\n\n- You cannot specify this clause with the following other constructs: the DISTINCT operator, CURSOR expression, set operators, group_by_clause, or aggregate functions.\n\nThe tables locked by this clause must all be located on the same database and on the same database as any LONG columns and sequences referenced in the same statement.\n\nSee Also: \"Using the FOR UPDATE Clause: Examples\" on page 19-47\n\nUsing the FOR UPDATE Clause on Views In general, this clause is not supported on views. However, in some cases, a SELECT ... FOR UPDATE query on a view can succeed without any errors. This occurs when the view has been merged to its containing query block internally by the query optimizer, and SELECT ... FOR UPDATE succeeds on the internally transformed query. The examples in this section illustrate when using the FOR UPDATE clause on a view can succeed or fail.\n\n- Using the FOR UPDATE clause on merged views\n\nAn error can occur when you use the FOR UPDATE clause on a merged view if both of the following conditions apply:\n\n- The underlying column of the view is an expression\n- The FOR UPDATE clause applies to a column list\n\nThe following statement succeeds because the underlying column of the view is not an expression:\n\n```sql\nSELECT employee_id FROM (SELECT * FROM employees)\nFOR UPDATE OF employee_id;\n```\n\nThe following statement succeeds because, while the underlying column of the view is an expression, the FOR UPDATE clause does not apply to a column list:\n\n```sql\nSELECT employee_id FROM (SELECT employee_id+1 AS employee_id FROM employees)\nFOR UPDATE;\n```\n\nThe following statement fails because the underlying column of the view is an expression and the FOR UPDATE clause applies to a column list:\n\n```sql\nSELECT employee_id FROM (SELECT employee_id+1 AS employee_id FROM employees)\nFOR UPDATE OF employee_id;\n*\nError at line 2:\nORA-01733: virtual column not allowed here\n```\n\n- Using the FOR UPDATE clause on non-merged views\n\nSince the FOR UPDATE clause is not supported on views, anything that prevents view merging, such as the NO_MERGE hint, parameters that disallow view merging, or something in the query structure that prevents view merging, will result in an ORA-02014 error.\n\nIn the following example, the GROUP BY statement prevents view merging, which causes an error:\n\n```sql\nSELECT avgsal\nFROM (SELECT AVG(salary) AS avgsal FROM employees GROUP BY job_id)\nFOR UPDATE;\nFROM (SELECT AVG(salary) AS avgsal FROM employees GROUP BY job_id)\n*\nERROR at line 2:\nORA-02014: cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.\n```\n\nNote: Due to the complexity of the view merging mechanism, Oracle recommends against using the FOR UPDATE clause on views.\n\nOF ... column\n\nUse the OF ... column clause to lock the select rows only for a particular table or view in a join. The columns in the OF clause only indicate which table or view rows are locked. The specific columns that you specify are not significant. However, you must specify an actual column name, not a column alias. If you omit this clause, then the database locks the selected rows from all the tables in the query.\n\nNOWAIT | WAIT\n\nThe NOWAIT and WAIT clauses let you tell the database how to proceed if the SELECT statement attempts to lock a row that is locked by another user.\n\n- Specify NOWAIT to return control to you immediately if a lock exists.\n- Specify WAIT to instruct the database to wait integer seconds for the row to become available and then return control to you.\n\nIf you specify neither WAIT nor NOWAIT, then the database waits until the row is available and then returns the results of the SELECT statement.\n\nSKIP LOCKED SKIP LOCKED is an alternative way to handle a contending transaction that is locking some rows of interest. Specify SKIP LOCKED to instruct the database to attempt to lock the rows specified by the WHERE clause and to skip any rows that are found to be already locked by another transaction. This feature is designed for use in multiconsumer queue environments, such as Oracle Streams Advanced Queuing. It enables queue consumers to skip rows that are locked by other consumers and obtain unlocked rows without waiting for the other consumers to finish. Oracle recommends that you use the Oracle Streams Advanced Queuing APIs instead of directly using the SKIP LOCKED functionality. Refer to *Oracle Streams Advanced Queuing User’s Guide* for more information.\n\nNote on the WAIT and SKIP LOCKED Clauses\n\nIf you specify WAIT or SKIP LOCKED and the table is locked in exclusive mode, then the database will not return the results of the SELECT statement until the lock on the table is released. In the case of WAIT, the SELECT FOR UPDATE clause is blocked regardless of the wait time specified.\n\nExamples\n\nSubquery Factoring: Example The following statement creates the query names dept_costs and avg_cost for the initial query block containing a join, and then uses the query names in the body of the main query.\n\nWITH\n dept_costs AS (\n SELECT department_name, SUM(salary) dept_total\n FROM employees e, departments d\n WHERE e.department_id = d.department_id\n GROUP BY department_name),\n avg_cost AS (\n SELECT SUM(dept_total)/COUNT(*) avg\n FROM dept_costs)\nSELECT * FROM dept_costs\nWHERE dept_total >\n\n(SELECT avg FROM avg_cost)\nORDER BY department_name;\n\n| DEPARTMENT_NAME | DEPT_TOTAL |\n|-----------------|------------|\n| Sales | 304500 |\n| Shipping | 156400 |\n\n**Recursive Subquery Factoring: Examples**\n\nThe following statement shows the employees who directly or indirectly report to employee 101 and their reporting level.\n\n```sql\nWITH\n reports_to_101 (eid, emp_last, mgr_id, reportLevel) AS\n (\n SELECT employee_id, last_name, manager_id, 0 reportLevel\n FROM employees\n WHERE employee_id = 101\n UNION ALL\n SELECT e.employee_id, e.last_name, e.manager_id, reportLevel+1\n FROM reports_to_101 r, employees e\n WHERE r.eid = e.manager_id\n )\nSELECT eid, emp_last, mgr_id, reportLevel\nFROM reports_to_101\nORDER BY reportLevel, eid;\n```\n\n| EID | EMP_LAST | MGR_ID | REPORTLEVEL |\n|-----|------------|--------|-------------|\n| 101 | Kochhar | 100 | 0 |\n| 108 | Greenberg | 101 | 1 |\n| 200 | Whalen | 101 | 1 |\n| 203 | Mavris | 101 | 1 |\n| 204 | Baer | 101 | 1 |\n| 205 | Higgins | 101 | 1 |\n| 109 | Faviet | 108 | 2 |\n| 110 | Chen | 108 | 2 |\n| 111 | Sciarra | 108 | 2 |\n| 112 | Urman | 108 | 2 |\n| 113 | Popp | 108 | 2 |\n| 206 | Gietz | 205 | 2 |\n\nThe following statement shows employees who directly or indirectly report to employee 101, their reporting level, and their management chain.\n\n```sql\nWITH\n reports_to_101 (eid, emp_last, mgr_id, reportLevel, mgr_list) AS\n (\n SELECT employee_id, last_name, manager_id, 0 reportLevel,\n CAST(manager_id AS VARCHAR2(2000))\n FROM employees\n WHERE employee_id = 101\n UNION ALL\n SELECT e.employee_id, e.last_name, e.manager_id, reportLevel+1,\n CAST(mgr_list || ',' || manager_id AS VARCHAR2(2000))\n FROM reports_to_101 r, employees e\n WHERE r.eid = e.manager_id\n )\nSELECT eid, emp_last, mgr_id, reportLevel, mgr_list\nFROM reports_to_101\nORDER BY reportLevel, eid;\n```\n\nThe following statement shows the employees who directly or indirectly report to employee 101 and their reporting level. It stops at reporting level 1.\n\n```sql\nWITH\n reports_to_101 (eid, emp_last, mgr_id, reportLevel) AS\n (\n SELECT employee_id, last_name, manager_id, 0 reportLevel\n FROM employees\n WHERE employee_id = 101\n UNION ALL\n SELECT e.employee_id, e.last_name, e.manager_id, reportLevel+1\n FROM reports_to_101 r, employees e\n WHERE r.eid = e.manager_id\n )\nSELECT eid, emp_last, mgr_id, reportLevel\nFROM reports_to_101\nWHERE reportLevel <= 1\nORDER BY reportLevel, eid;\n```\n\n| EID | EMP_LAST | MGR_ID | REPORTLEVEL |\n|-----|------------|--------|-------------|\n| 101 | Kochhar | 100 | 0 |\n| 108 | Greenberg | 101 | 1 |\n| 200 | Whalen | 101 | 1 |\n| 203 | Mavris | 101 | 1 |\n| 204 | Baer | 101 | 1 |\n| 205 | Higgins | 101 | 1 |\n| 109 | Faviet | 108 | 2 |\n| 110 | Chen | 108 | 2 |\n| 111 | Sciarra | 108 | 2 |\n| 112 | Urman | 108 | 2 |\n| 113 | Popp | 108 | 2 |\n| 206 | Gietz | 205 | 2 |\n\nThe following statement shows the entire organization, indenting for each level of management.\n\n```sql\nWITH\n org_chart (eid, emp_last, mgr_id, reportLevel, salary, job_id) AS\n (\n SELECT employee_id, last_name, manager_id, 0 reportLevel, salary, job_id\n FROM employees\n WHERE manager_id is null\n UNION ALL\n SELECT e.employee_id, e.last_name, e.manager_id,\n r.reportLevel+1 reportLevel, e.salary, e.job_id\n FROM org_chart r, employees e\n WHERE r.eid = e.manager_id\n )\nSEARCH DEPTH FIRST BY emp_last SET order1\nSELECT lpad(' ',2*reportLevel)||emp_last emp_name, eid, mgr_id, salary, job_id\nFROM org_chart\n```\n\nORDER BY order1;\n\n| EMP_NAME | EID | MGR_ID | SALARY | JOB_ID |\n|-----------|-----|--------|--------|----------|\n| King | 100 | | 24000 | AD_PRES |\n| Cambrault | 148 | 100 | 11000 | SA_MAN |\n| Bates | 172 | 148 | 7300 | SA_REP |\n| Bloom | 169 | 148 | 10000 | SA_REP |\n| Fox | 170 | 148 | 9600 | SA_REP |\n| Kumar | 173 | 148 | 6100 | SA_REP |\n| Ozer | 168 | 148 | 11500 | SA_REP |\n| Smith | 171 | 148 | 7400 | SA_REP |\n| De Haan | 102 | 100 | 17000 | AD_VP |\n| Hunold | 103 | 102 | 9000 | IT_PROG |\n| Austin | 105 | 103 | 4800 | IT_PROG |\n| Ernst | 104 | 103 | 6000 | IT_PROG |\n| Lorentz | 107 | 103 | 4200 | IT_PROG |\n| Pataballa | 106 | 103 | 4800 | IT_PROG |\n| Errazuriz | 147 | 100 | 12000 | SA_MAN |\n| Ande | 166 | 147 | 6400 | SA_REP |\n\nThe following statement shows the entire organization, indenting for each level of management, with each level ordered by hire_date. The value of is_cycle is set to Y for any employee who has the same hire_date as any manager above him in the management chain.\n\nWITH\n dup_hiredate (eid, emp_last, mgr_id, reportLevel, hire_date, job_id) AS\n (\n SELECT employee_id, last_name, manager_id, 0 reportLevel, hire_date, job_id\n FROM employees\n WHERE manager_id is null\n UNION ALL\n SELECT e.employee_id, e.last_name, e.manager_id,\n r.reportLevel+1 reportLevel, e.hire_date, e.job_id\n FROM dup_hiredate r, employees e\n WHERE r.eid = e.manager_id\n )\nSEARCH DEPTH FIRST BY hire_date SET order1\nCYCLE hire_date SET is_cycle TO 'Y' DEFAULT 'N'\nSELECT lpad(' ',2*reportLevel)||emp_last emp_name, eid, mgr_id,\n hire_date, job_id, is_cycle\nFROM dup_hiredate\nORDER BY order1;\n\n| EMP_NAME | EID | MGR_ID | HIRE_DATE | JOB_ID | IS_CYCLE |\n|-----------|-----|--------|---------------|----------|----------|\n| King | 100 | | 17-JUN-03 | AD_PRES | N |\n| De Haan | 102 | 100 | 13-JAN-01 | AD_VP | N |\n| Hunold | 103 | 102 | 03-JAN-06 | IT_PROG | N |\n| Austin | 105 | 103 | 25-JUN-05 | IT_PROG | N |\n| Kochhar | 101 | 100 | 21-SEP-05 | AD_VP | N |\n| Mavris | 203 | 101 | 07-JUN-02 | HR_REP | N |\n| Baer | 204 | 101 | 07-JUN-02 | PR_REP | N |\n| Higgins | 205 | 101 | 07-JUN-02 | AC_MGR | N |\n| Gietz | 206 | 205 | 07-JUN-02 | AC_ACCOUNT| Y |\n| Greenberg | 108 | 101 | 17-AUG-02 | FI_MGR | N |\n| Faviet | 109 | 108 | 16-AUG-02 | FI_ACCOUNT| N |\n\nThe following statement counts the number of employees under each manager.\n\n```sql\nWITH\n emp_count (eid, emp_last, mgr_id, mgrLevel, salary, cnt_employees) AS\n (\n SELECT employee_id, last_name, manager_id, 0 mgrLevel, salary, 0 cnt_employees\n FROM employees\n UNION ALL\n SELECT e.employee_id, e.last_name, e.manager_id,\n r.mgrLevel+1 mgrLevel, e.salary, 1 cnt_employees\n FROM emp_count r, employees e\n WHERE e.employee_id = r.mgr_id\n )\nSEARCH DEPTH FIRST BY emp_last SET order1\nSELECT emp_last, eid, mgr_id, salary, sum(cnt_employees), max(mgrLevel) mgrLevel\nFROM emp_count\nGROUP BY emp_last, eid, mgr_id, salary\nHAVING max(mgrLevel) > 0\nORDER BY mgr_id NULLS FIRST, emp_last;\n```\n\n| EMP_LAST | EID | MGR_ID | SALARY | SUM(CNT_EMPLOYEES) | MGRLEVEL |\n|----------|-----|--------|--------|--------------------|----------|\n| King | 100 | 100 | 24000 | 106 | 3 |\n| Cambrault| 148 | 100 | 11000 | 7 | 2 |\n| De Haan | 102 | 100 | 17000 | 5 | 2 |\n| Errazuriz| 147 | 100 | 12000 | 6 | 1 |\n| Fripp | 121 | 100 | 8200 | 8 | 1 |\n| Hartstein| 201 | 100 | 13000 | 1 | 1 |\n| Kaufling | 122 | 100 | 7900 | 8 | 1 |\n\n**Simple Query Examples**\n\nThe following statement selects rows from the `employees` table with the department number of 30:\n\n```sql\nSELECT *\n FROM employees\n WHERE department_id = 30\n ORDER BY last_name;\n```\n\nThe following statement selects the name, job, salary and department number of all employees except purchasing clerks from department number 30:\n\n```sql\nSELECT last_name, job_id, salary, department_id\n FROM employees\n WHERE NOT (job_id = 'PU_CLERK' AND department_id = 30)\n ORDER BY last_name;\n```\n\nThe following statement selects from subqueries in the `FROM` clause and for each department returns the total employees and salaries as a decimal value of all the departments:\n\n```sql\nSELECT a.department_id \"Department\",\n a.num_emp/b.total_count \"%_Employees\",\n a.sal_sum/b.total_sal \"%_Salary\"\nFROM\n(SELECT department_id, COUNT(*) num_emp, SUM(salary) sal_sum\n FROM employees\n GROUP BY department_id) a,\n(SELECT department_id, COUNT(*) total_count, SUM(salary) total_sal\n FROM employees\n GROUP BY department_id) b;\n```\n\n(SELECT COUNT(*) total_count, SUM(salary) total_sal\n FROM employees) b\nORDER BY a.department_id;\n\n**Selecting from a Partition: Example** You can select rows from a single partition of a partitioned table by specifying the keyword `PARTITION` in the `FROM` clause. This SQL statement assigns an alias for and retrieves rows from the `sales_q2_2000` partition of the sample table `sh.sales`:\n\n```sql\nSELECT * FROM sales PARTITION (sales_q2_2000) s\n WHERE s.amount_sold > 1500\n ORDER BY cust_id, time_id, channel_id;\n```\n\nThe following example selects rows from the `oe.orders` table for orders earlier than a specified date:\n\n```sql\nSELECT * FROM orders\n WHERE order_date < TO_DATE('2006-06-15', 'YYYY-MM-DD');\n```\n\n**Selecting a Sample: Examples** The following query estimates the number of orders in the `oe.orders` table:\n\n```sql\nSELECT COUNT(*) * 10 FROM orders SAMPLE (10);\n```\n\n```\nCOUNT(*)*10\n-----------\n 70\n```\n\nBecause the query returns an estimate, the actual return value may differ from one query to the next.\n\n```sql\nSELECT COUNT(*) * 10 FROM orders SAMPLE (10);\n```\n\n```\nCOUNT(*)*10\n-----------\n 80\n```\n\nThe following query adds a seed value to the preceding query. Oracle Database always returns the same estimate given the same seed value:\n\n```sql\nSELECT COUNT(*) * 10 FROM orders SAMPLE(10) SEED (1);\n```\n\n```\nCOUNT(*)*10\n-----------\n 130\n```\n\n```sql\nSELECT COUNT(*) * 10 FROM orders SAMPLE(10) SEED(4);\n```\n\n```\nCOUNT(*)*10\n-----------\n 120\n```\n\n```sql\nSELECT COUNT(*) * 10 FROM orders SAMPLE(10) SEED (1);\n```\n\n```\nCOUNT(*)*10\n-----------\n 130\n```\n\n**Using Flashback Queries: Example** The following statements show a current value from the sample table `hr.employees` and then change the value. The intervals used\n\nin these examples are very short for demonstration purposes. Time intervals in your own environment are likely to be larger.\n\n```sql\nSELECT salary FROM employees\n WHERE last_name = 'Chung';\n\n SALARY\n --------\n 3800\n\nUPDATE employees SET salary = 4000\n WHERE last_name = 'Chung';\n1 row updated.\n\nSELECT salary FROM employees\n WHERE last_name = 'Chung';\n\n SALARY\n --------\n 4000\n```\n\nTo learn what the value was before the update, you can use the following Flashback Query:\n\n```sql\nSELECT salary FROM employees\n AS OF TIMESTAMP (SYSTIMESTAMP - INTERVAL '1' MINUTE)\n WHERE last_name = 'Chung';\n\n SALARY\n --------\n 3800\n```\n\nTo learn what the values were during a particular time period, you can use a version Flashback Query:\n\n```sql\nSELECT salary FROM employees\n VERSIONS BETWEEN TIMESTAMP\n SYSTIMESTAMP - INTERVAL '10' MINUTE AND\n SYSTIMESTAMP - INTERVAL '1' MINUTE\n WHERE last_name = 'Chung';\n```\n\nTo revert to the earlier value, use the Flashback Query as the subquery of another UPDATE statement:\n\n```sql\nUPDATE employees SET salary =\n (SELECT salary FROM employees\n AS OF TIMESTAMP (SYSTIMESTAMP - INTERVAL '2' MINUTE)\n WHERE last_name = 'Chung')\n WHERE last_name = 'Chung';\n1 row updated.\n\nSELECT salary FROM employees\n WHERE last_name = 'Chung';\n\n SALARY\n --------\n 3800\n```\n\n**Using the GROUP BY Clause: Examples**\n\nTo return the minimum and maximum salaries for each department in the `employees` table, issue the following statement:\n\n```sql\nSELECT department_id, MIN(salary), MAX(salary)\n```\n\nTo return the minimum and maximum salaries for the clerks in each department, issue the following statement:\n\n```sql\nSELECT department_id, MIN(salary), MAX(salary)\n FROM employees\n WHERE job_id = 'PU_CLERK'\n GROUP BY department_id\n ORDER BY department_id;\n```\n\n**Using the GROUP BY CUBE Clause: Example** To return the number of employees and their average yearly salary across all possible combinations of department and job category, issue the following query on the sample tables `hr.employees` and `hr.departments`:\n\n```sql\nSELECT DECODE(GROUPING(department_name), 1, 'All Departments',\n department_name) AS department_name,\n DECODE(GROUPING(job_id), 1, 'All Jobs', job_id) AS job_id,\n COUNT(*) \"Total Empl\", AVG(salary) * 12 \"Average Sal\"\nFROM employees e, departments d\nWHERE d.department_id = e.department_id\nGROUP BY CUBE (department_name, job_id)\nORDER BY department_name, job_id;\n```\n\n| DEPARTMENT_NAME | JOB_ID | Total Empl | Average Sal |\n|-----------------|------------|------------|-------------|\n| Accounting | AC_ACCOUNT | 1 | 99600 |\n| Accounting | AC_MGR | 1 | 144000 |\n| Accounting | All Jobs | 2 | 121800 |\n| Administration | AD_ASST | 1 | 52800 |\n| Shipping | ST_CLERK | 20 | 33420 |\n| Shipping | ST_MAN | 5 | 87360 |\n\n**Using the GROUPING SETS Clause: Example** The following example finds the sum of sales aggregated for three precisely specified groups:\n\n- `(channel_desc, calendar_month_desc, country_id)`\n- `(channel_desc, country_id)`\n- `(calendar_month_desc, country_id)`\n\nWithout the `GROUPING SETS` syntax, you would have to write less efficient queries with more complicated SQL. For example, you could run three separate queries and `UNION` them, or run a query with a `CUBE(channel_desc, calendar_month_desc, country_id)` operation and filter out five of the eight groups it would generate.\n\n```sql\nSELECT channel_desc, calendar_month_desc, co.country_id,\n TO_CHAR(sum(amount_sold), '9,999,999,999') SALES$\nFROM sales, customers, times, channels, countries co\nWHERE sales.time_id=times.time_id\n AND sales.cust_id=customers.cust_id\n AND sales.channel_id= channels.channel_id\n AND customers.country_id = co.country_id\n AND channels.channel_desc IN ('Direct Sales', 'Internet')\n AND times.calendar_month_desc IN ('2000-09', '2000-10')\n AND co.country_iso_code IN ('UK', 'US')\nGROUP BY channel_desc, calendar_month_desc, co.country_id\nUNION\nSELECT channel_desc, co.country_id,\n TO_CHAR(sum(amount_sold), '9,999,999,999') SALES$\nFROM sales, customers, channels, countries co\nWHERE sales.cust_id=customers.cust_id\n AND sales.channel_id= channels.channel_id\n AND customers.country_id = co.country_id\n AND channels.channel_desc IN ('Direct Sales', 'Internet')\n AND co.country_iso_code IN ('UK', 'US')\nGROUP BY channel_desc, co.country_id\nUNION\nSELECT co.country_id,\n TO_CHAR(sum(amount_sold), '9,999,999,999') SALES$\nFROM sales, customers, times, countries co\nWHERE sales.time_id=times.time_id\n AND sales.cust_id=customers.cust_id\n AND customers.country_id = co.country_id\n AND times.calendar_month_desc IN ('2000-09', '2000-10')\n AND co.country_iso_code IN ('UK', 'US')\nGROUP BY co.country_id\nORDER BY channel_desc, calendar_month_desc, co.country_id;\n```\n\nGROUP BY GROUPING SETS(\n (channel_desc, calendar_month_desc, co.country_id),\n (channel_desc, co.country_id),\n (calendar_month_desc, co.country_id) );\n\n| CHANNEL_DESC | CALENDAR | COUNTRY_ID | SALES$ |\n|----------------|----------|------------|--------|\n| Internet | 2000-09 | 52790 | 124,224|\n| Direct Sales | 2000-09 | 52790 | 638,201|\n| Internet | 2000-10 | 52790 | 137,054|\n| Direct Sales | 2000-10 | 52790 | 682,297|\n| | 2000-09 | 52790 | 762,425|\n| | 2000-10 | 52790 | 819,351|\n| Internet | | 52790 | 261,278|\n| Direct Sales | | 52790 | 1,320,497|\n\n**See Also:** The functions [GROUP_ID](#), [GROUPING](#), and [GROUPING_ID](#) on page 5-81 for more information on those functions\n\n**Hierarchical Query Examples** The following query with a CONNECT BY clause defines a hierarchical relationship in which the employee_id value of the parent row is equal to the manager_id value of the child row:\n\n```sql\nSELECT last_name, employee_id, manager_id FROM employees\n CONNECT BY employee_id = manager_id\n ORDER BY last_name;\n```\n\nIn the following CONNECT BY clause, the PRIOR operator applies only to the employee_id value. To evaluate this condition, the database evaluates employee_id values for the parent row and manager_id, salary, and commission_pct values for the child row:\n\n```sql\nSELECT last_name, employee_id, manager_id FROM employees\n CONNECT BY PRIOR employee_id = manager_id\n AND salary > commission_pct\n ORDER BY last_name;\n```\n\nTo qualify as a child row, a row must have a manager_id value equal to the employee_id value of the parent row and it must have a salary value greater than its commission_pct value.\n\n**Using the HAVING Condition: Example** To return the minimum and maximum salaries for the employees in each department whose lowest salary is less than $5,000, issue the next statement:\n\n```sql\nSELECT department_id, MIN(salary), MAX (salary)\n FROM employees\n GROUP BY department_id\n HAVING MIN(salary) < 5000\n ORDER BY department_id;\n```\n\n| DEPARTMENT_ID | MIN(SALARY) | MAX(SALARY) |\n|---------------|-------------|-------------|\n| 10 | 4400 | 4400 |\n| 30 | 2500 | 11000 |\n| 50 | 2100 | 8200 |\n| 60 | 4200 | 9000 |\n\nThe following example uses a correlated subquery in a HAVING clause that eliminates from the result set any departments without managers and managers without departments:\n\n```sql\nSELECT department_id, manager_id\nFROM employees\nGROUP BY department_id, manager_id HAVING (department_id, manager_id) IN\n(SELECT department_id, manager_id FROM employees x\nWHERE x.department_id = employees.department_id)\nORDER BY department_id;\n```\n\n**Using the ORDER BY Clause: Examples**\n\nTo select all purchasing clerk records from employees and order the results by salary in descending order, issue the following statement:\n\n```sql\nSELECT *\nFROM employees\nWHERE job_id = 'PU_CLERK'\nORDER BY salary DESC;\n```\n\nTo select information from employees ordered first by ascending department number and then by descending salary, issue the following statement:\n\n```sql\nSELECT last_name, department_id, salary\nFROM employees\nORDER BY department_id ASC, salary DESC, last_name;\n```\n\nTo select the same information as the previous SELECT and use the positional ORDER BY notation, issue the following statement, which orders by ascending department_id, then descending salary, and finally alphabetically by last_name:\n\n```sql\nSELECT last_name, department_id, salary\nFROM employees\nORDER BY 2 ASC, 3 DESC, 1;\n```\n\n**The MODEL clause: Examples**\n\nThe view created below is based on the sample sh schema and is used by the example that follows.\n\n```sql\nCREATE OR REPLACE VIEW sales_view_ref AS\nSELECT country_name country,\n prod_name prod,\n calendar_year year,\n SUM(amount_sold) sale,\n COUNT(amount_sold) cnt\nFROM sales,times,customers,countries,products\nWHERE sales.time_id = times.time_id\n AND sales.prod_id = products.prod_id\n AND sales.cust_id = customers.cust_id\n AND customers.country_id = countries.country_id\n AND ( customers.country_id = 52779\n OR customers.country_id = 52776 )\n AND ( prod_name = 'Standard Mouse'\n OR prod_name = 'Mouse Pad' )\nGROUP BY country_name,prod_name,calendar_year;\n\nSELECT country, prod, year, sale\nFROM sales_view_ref\nORDER BY country, prod, year;\n```\n\n| COUNTRY | PROD | YEAR | SALE |\n|---------|---------------|------|------|\n| ------- | --------------|------|------|\n\nThe next example creates a multidimensional array from `sales_view_ref` with columns containing country, product, year, and sales. It also:\n\n- Assigns the sum of the sales of the Mouse Pad for years 1999 and 2000 to the sales of the Mouse Pad for year 2001, if a row containing sales of the Mouse Pad for year 2001 exists.\n\n- Assigns the value of sales of the Standard Mouse for year 2001 to sales of the Standard Mouse for year 2002, creating a new row if a row containing sales of the Standard Mouse for year 2002 does not exist.\n\n```sql\nSELECT country, prod, year, s\nFROM sales_view_ref\nMODEL\nPARTITION BY (country)\nDIMENSION BY (prod, year)\nMEASURES (sale s)\nIGNORE NAV\nUNIQUE DIMENSION\nRULES UPSERT SEQUENTIAL ORDER\n(\n s[prod='Mouse Pad', year=2001] =\n s['Mouse Pad', 1999] + s['Mouse Pad', 2000],\n s['Standard Mouse', 2002] = s['Standard Mouse', 2001]\n)\nORDER BY country, prod, year;\n```\n\n| COUNTRY | PROD | YEAR | SALE |\n|---------|---------------|------|--------|\n| France | Mouse Pad | 1998 | 2509.42|\n| France | Mouse Pad | 1999 | 3678.69|\n| France | Mouse Pad | 2000 | 3000.72|\n| France | Mouse Pad | 2001 | 6679.41|\n| France | Standard Mouse| 1998 | 2390.83|\n| France | Standard Mouse| 1999 | 2280.45|\n| France | Standard Mouse| 2000 | 1274.31|\n| France | Standard Mouse| 2001 | 2164.54|\n| France | Standard Mouse| 2002 | 2164.54|\n| Germany | Mouse Pad | 1998 | 5827.87|\n| Germany | Mouse Pad | 1999 | 8346.44|\n| Germany | Mouse Pad | 2000 | 7375.46|\n| Germany | Mouse Pad | 2001 | 15721.9 |\n\nGermany Standard Mouse 1998 7116.11\nGermany Standard Mouse 1999 6263.14\nGermany Standard Mouse 2000 2637.31\nGermany Standard Mouse 2001 6456.13\nGermany Standard Mouse 2002 6456.13\n\n18 rows selected.\n\nThe first rule uses UPDATE behavior because symbolic referencing is used on the left-hand side of the rule. The rows represented by the left-hand side of the rule exist, so the measure columns are updated. If the rows did not exist, then no action would have been taken.\n\nThe second rule uses UPSERT behavior because positional referencing is used on the left-hand side and a single cell is referenced. The rows do not exist, so new rows are inserted and the related measure columns are updated. If the rows did exist, then the measure columns would have been updated.\n\nSee Also: Oracle Database Data Warehousing Guide for an expanded discussion and examples\n\nThe next example uses the same sales_view_ref view and the analytic function SUM to calculate a cumulative sum (csum) of sales per country and per year.\n\n```sql\nSELECT country, year, sale, csum\nFROM\n(SELECT country, year, SUM(sale) sale\n FROM sales_view_ref\n GROUP BY country, year\n)\nMODEL DIMENSION BY (country, year)\nMEASURES (sale, 0 csum)\nRULES (csum[any, any]=\n SUM(sale) OVER (PARTITION BY country\n ORDER BY year\n ROWS UNBOUNDED PRECEDING)\n )\nORDER BY country, year;\n```\n\n| COUNTRY | YEAR | SALE | CSUM |\n|---------|------|--------|---------|\n| France | 1998 | 4900.25| 4900.25 |\n| France | 1999 | 5959.14| 10859.39|\n| France | 2000 | 4275.03| 15134.42|\n| France | 2001 | 5433.63| 20568.05|\n| Germany | 1998 | 12943.98| 12943.98|\n| Germany | 1999 | 14609.58| 27553.56|\n| Germany | 2000 | 10012.77| 37566.33|\n| Germany | 2001 | 15991.21| 53557.54|\n\n8 rows selected.\n\nUsing the FOR UPDATE Clause: Examples The following statement locks rows in the employees table with purchasing clerks located in Oxford, which has location_id 2500, and locks rows in the departments table with departments in Oxford that have purchasing clerks:\n\n```sql\nSELECT e.employee_id, e.salary, e.commission_pct\nFROM employees e, departments d\nWHERE job_id = 'SA_REP'\n```\n\nAND e.department_id = d.department_id\nAND location_id = 2500\nORDER BY e.employee_id\nFOR UPDATE;\n\nThe following statement locks only those rows in the employees table with purchasing clerks located in Oxford. No rows are locked in the departments table:\n\nSELECT e.employee_id, e.salary, e.commission_pct\nFROM employees e JOIN departments d\nUSING (department_id)\nWHERE job_id = 'SA_REP'\nAND location_id = 2500\nORDER BY e.employee_id\nFOR UPDATE OF e.salary;\n\n**Using the WITH CHECK OPTION Clause: Example**\n\nThe following statement is legal even though the third value inserted violates the condition of the subquery where_clause:\n\n```sql\nINSERT INTO (SELECT department_id, department_name, location_id\nFROM departments WHERE location_id < 2000)\nVALUES (9999, 'Entertainment', 2500);\n```\n\nHowever, the following statement is illegal because it contains the WITH CHECK OPTION clause:\n\n```sql\nINSERT INTO (SELECT department_id, department_name, location_id\nFROM departments WHERE location_id < 2000 WITH CHECK OPTION)\nVALUES (9999, 'Entertainment', 2500);\n*\nERROR at line 2:\nORA-01402: view WITH CHECK OPTION where-clause violation\n```\n\n**Using PIVOT and UNPIVOT: Examples**\n\nThe oe.orders table contains information about when an order was placed (order_date), how it was placed (order_mode), and the total amount of the order (order_total), as well as other information. The following example shows how to use the PIVOT clause to pivot order_mode values into columns, aggregating order_total data in the process, to get yearly totals by order mode:\n\n```sql\nCREATE TABLE pivot_table AS\nSELECT * FROM\n(SELECT EXTRACT(YEAR FROM order_date) year, order_mode, order_total FROM orders)\nPIVOT\n(SUM(order_total) FOR order_mode IN ('direct' AS Store, 'online' AS Internet));\n\nSELECT * FROM pivot_table ORDER BY year;\n```\n\n| YEAR | STORE | INTERNET |\n|------|---------|----------|\n| 2004 | 5546.6 | |\n| 2006 | 371895.5| 100056.6 |\n| 2007 | 1274078.8| 1271019.5|\n| 2008 | 252108.3| 393349.4 |\n\nThe UNPIVOT clause lets you rotate specified columns so that the input column headings are output as values of one or more descriptor columns, and the input column values are output as values of one or more measures columns. The first query\n\nthat follows shows that nulls are excluded by default. The second query shows that you can include nulls using the INCLUDE NULLS clause.\n\n```sql\nSELECT * FROM pivot_table\nUNPIVOT (yearly_total FOR order_mode IN (store AS 'direct',\n internet AS 'online'))\nORDER BY year, order_mode;\n\nYEAR ORDER_ YEARLY_TOTAL\n---------- ------ -------------\n2004 direct 5546.6\n2006 direct 371895.5\n2006 online 100056.6\n2007 direct 1274078.8\n2007 online 1271019.5\n2008 direct 252108.3\n2008 online 393349.4\n\n7 rows selected.\n\nSELECT * FROM pivot_table\nUNPIVOT INCLUDE NULLS\n(yearly_total FOR order_mode IN (store AS 'direct', internet AS 'online'))\nORDER BY year, order_mode;\n\nYEAR ORDER_ YEARLY_TOTAL\n---------- ------ -------------\n2004 direct 5546.6\n2004 online\n2006 direct 371895.5\n2006 online 100056.6\n2007 direct 1274078.8\n2007 online 1271019.5\n2008 direct 252108.3\n2008 online 393349.4\n\n8 rows selected.\n```\n\n**Using Join Queries: Examples**\n\nThe following examples show various ways of joining tables in a query. In the first example, an equijoin returns the name and job of each employee and the number and name of the department in which the employee works:\n\n```sql\nSELECT last_name, job_id, departments.department_id, department_name\nFROM employees, departments\nWHERE employees.department_id = departments.department_id\nORDER BY last_name, job_id;\n```\n\n| LAST_NAME | JOB_ID | DEPARTMENT_ID | DEPARTMENT_NAME |\n|-----------|----------|---------------|-----------------|\n| Abel | SA_REP | 80 | Sales |\n| Ande | SA_REP | 80 | Sales |\n| Atkinson | ST_CLERK | 50 | Shipping |\n| Austin | IT_PROG | 60 | IT |\n\nYou must use a join to return this data because employee names and jobs are stored in a different table than department names. Oracle Database combines rows of the two tables according to this join condition:\n\n`employees.department_id = departments.department_id`\n\nThe following equijoin returns the name, job, department number, and department name of all sales managers:\n\n```sql\nSELECT last_name, job_id, departments.department_id, department_name\n FROM employees, departments\n WHERE employees.department_id = departments.department_id\n AND job_id = 'SA_MAN'\n ORDER BY last_name;\n```\n\n| LAST_NAME | JOB_ID | DEPARTMENT_ID | DEPARTMENT_NAME |\n|-----------|--------|--------------|-----------------|\n| Cambrault | SA_MAN | 80 | Sales |\n| Errazuriz | SA_MAN | 80 | Sales |\n| Partners | SA_MAN | 80 | Sales |\n| Russell | SA_MAN | 80 | Sales |\n| Zlotkey | SA_MAN | 80 | Sales |\n\nThis query is identical to the preceding example, except that it uses an additional `where_clause` condition to return only rows with a `job` value of 'SA_MAN'.\n\n**Using Subqueries: Examples**\n\nTo determine who works in the same department as employee 'Lorentz', issue the following statement:\n\n```sql\nSELECT last_name, department_id FROM employees\n WHERE department_id =\n (SELECT department_id FROM employees\n WHERE last_name = 'Lorentz')\n ORDER BY last_name, department_id;\n```\n\nTo give all employees in the `employees` table a 10% raise if they have changed jobs—if they appear in the `job_history` table—issue the following statement:\n\n```sql\nUPDATE employees\n SET salary = salary * 1.1\n WHERE employee_id IN (SELECT employee_id FROM job_history);\n```\n\nTo create a second version of the `departments` table `new_departments`, with only three of the columns of the original table, issue the following statement:\n\n```sql\nCREATE TABLE new_departments\n (department_id, department_name, location_id)\n AS SELECT department_id, department_name, location_id\n FROM departments;\n```\n\n**Using Self Joins: Example**\n\nThe following query uses a self join to return the name of each employee along with the name of the employee's manager. A `WHERE` clause is added to shorten the output.\n\n```sql\nSELECT e1.last_name||' works for '||e2.last_name\n \"Employees and Their Managers\"\n FROM employees e1, employees e2\n WHERE e1.manager_id = e2.employee_id\n AND e1.last_name LIKE 'R%'\n ORDER BY e1.last_name;\n```\n\nEmployees and Their Managers\n------------------------------\nRajs works for Mourgos\nRaphaely works for King\nRogers works for Kaufling\n\nRussell works for King\n\nThe join condition for this query uses the aliases e1 and e2 for the sample table employees:\n\ne1.manager_id = e2.employee_id\n\n**Using Outer Joins: Examples** The following example shows how a partitioned outer join fills data gaps in rows to facilitate analytic function specification and reliable report formatting. The example first creates a small data table to be used in the join:\n\n```sql\nSELECT d.department_id, e.last_name\nFROM departments d LEFT OUTER JOIN employees e\nON d.department_id = e.department_id\nORDER BY d.department_id, e.last_name;\n```\n\nUsers familiar with the traditional Oracle Database outer joins syntax will recognize the same query in this form:\n\n```sql\nSELECT d.department_id, e.last_name\nFROM departments d, employees e\nWHERE d.department_id = e.department_id(+)\nORDER BY d.department_id, e.last_name;\n```\n\nOracle strongly recommends that you use the more flexible `FROM` clause join syntax shown in the former example.\n\nThe left outer join returns all departments, including those without any employees. The same statement with a right outer join returns all employees, including those not yet assigned to a department:\n\n---\n\n**Note:** The employee Zeuss was added to the employees table for these examples, and is not part of the sample data.\n\n---\n\n```sql\nSELECT d.department_id, e.last_name\nFROM departments d RIGHT OUTER JOIN employees e\nON d.department_id = e.department_id\nORDER BY d.department_id, e.last_name;\n```\n\n| DEPARTMENT_ID | LAST_NAME |\n|---------------|-----------|\n| 110 | Gietz |\n| 110 | Higgins |\n| | Grant |\n| | Zeuss |\n\nIt is not clear from this result whether employees Grant and Zeuss have `department_id` NULL, or whether their `department_id` is not in the `departments` table. To determine this requires a full outer join:\n\n```sql\nSELECT d.department_id as d_dept_id, e.department_id as e_dept_id,\n e.last_name\nFROM departments d FULL OUTER JOIN employees e\nON d.department_id = e.department_id\nORDER BY d.department_id, e.last_name;\n```\n\n| D_DEPT_ID | E_DEPT_ID | LAST_NAME |\n|-----------|-----------|-----------|\n| | | |\n\nBecause the column names in this example are the same in both tables in the join, you can also use the common column feature by specifying the USING clause of the join syntax. The output is the same as for the preceding example except that the USING clause coalesces the two matching columns department_id into a single column output:\n\n```sql\nSELECT department_id AS d_e_dept_id, e.last_name\n FROM departments d FULL OUTER JOIN employees e\n USING (department_id)\n ORDER BY department_id, e.last_name;\n```\n\n| D_E_DEPT_ID | LAST_NAME |\n|-------------|-----------|\n| 110 | Higgins |\n| 110 | Gietz |\n| 260 | |\n| 270 | |\n| 999 | Zeuss |\n| | Grant |\n```\n\n**Using Partitioned Outer Joins: Examples**\n\nThe following example shows how a partitioned outer join fills in gaps in rows to facilitate analytic calculation specification and reliable report formatting. The example first creates and populates a simple table to be used in the join:\n\n```sql\nCREATE TABLE inventory (time_id DATE,\n product VARCHAR2(10),\n quantity NUMBER);\n\nINSERT INTO inventory VALUES (TO_DATE('01/04/01', 'DD/MM/YY'), 'bottle', 10);\nINSERT INTO inventory VALUES (TO_DATE('06/04/01', 'DD/MM/YY'), 'bottle', 10);\nINSERT INTO inventory VALUES (TO_DATE('01/04/01', 'DD/MM/YY'), 'can', 10);\nINSERT INTO inventory VALUES (TO_DATE('04/04/01', 'DD/MM/YY'), 'can', 10);\n\nSELECT times.time_id, product, quantity FROM inventory\n PARTITION BY (product)\n RIGHT OUTER JOIN times ON (times.time_id = inventory.time_id)\n WHERE times.time_id BETWEEN TO_DATE('01/04/01', 'DD/MM/YY')\n AND TO_DATE('06/04/01', 'DD/MM/YY')\n ORDER BY 2,1;\n\n| TIME_ID | PRODUCT | QUANTITY |\n|------------|---------|----------|\n| 01-APR-01 | bottle | 10 |\n| 02-APR-01 | bottle | |\n| 03-APR-01 | bottle | |\n| 04-APR-01 | bottle | |\n| 05-APR-01 | bottle | |\n| 06-APR-01 | bottle | 10 |\n```\n\nThe data is now more dense along the time dimension for each partition of the product dimension. However, each of the newly added rows within each partition is null in the quantity column. It is more useful to see the nulls replaced by the preceding non-NULL value in time order. You can achieve this by applying the analytic function LAST_VALUE on top of the query result:\n\n```sql\nSELECT time_id, product, LAST_VALUE(quantity IGNORE NULLS)\n OVER (PARTITION BY product ORDER BY time_id) quantity\nFROM ( SELECT times.time_id, product, quantity\n FROM inventory PARTITION BY (product)\n RIGHT OUTER JOIN times ON (times.time_id = inventory.time_id)\n WHERE times.time_id BETWEEN TO_DATE('01/04/01', 'DD/MM/YY')\n AND TO_DATE('06/04/01', 'DD/MM/YY'))\nORDER BY 2,1;\n```\n\n| TIME_ID | PRODUCT | QUANTITY |\n|-----------|---------|----------|\n| 01-APR-01 | bottle | 10 |\n| 02-APR-01 | bottle | 10 |\n| 03-APR-01 | bottle | 10 |\n| 04-APR-01 | bottle | 10 |\n| 05-APR-01 | bottle | 10 |\n| 06-APR-01 | bottle | 10 |\n| 01-APR-01 | can | 10 |\n| 02-APR-01 | can | 10 |\n| 03-APR-01 | can | 10 |\n| 04-APR-01 | can | 10 |\n| 05-APR-01 | can | 10 |\n| 06-APR-01 | can | 10 |\n\n12 rows selected.\n\n**See Also:** *Oracle Database Data Warehousing Guide* for an expanded discussion on filling gaps in time series calculations and examples of usage\n\n**Using Antijoins: Example** The following example selects a list of employees who are not in a particular set of departments:\n\n```sql\nSELECT * FROM employees\nWHERE department_id NOT IN\n(SELECT department_id FROM departments\n WHERE location_id = 1700)\nORDER BY last_name;\n```\n\n**Using Semijoins: Example** In the following example, only one row needs to be returned from the `departments` table, even though many rows in the `employees` table might match the subquery. If no index has been defined on the `salary` column in `employees`, then a semijoin can be used to improve query performance.\n\n```sql\nSELECT * FROM departments\n```\n\nWHERE EXISTS\n(SELECT * FROM employees\n WHERE departments.department_id = employees.department_id\n AND employees.salary > 2500)\nORDER BY department_name;\n\n**Table Collections: Examples** You can perform DML operations on nested tables only if they are defined as columns of a table. Therefore, when the `query_table_expr_clause` of an INSERT, DELETE, or UPDATE statement is a `table_collection_expression`, the collection expression must be a subquery that uses the TABLE collection expression to select the nested table column of the table. The examples that follow are based on the following scenario:\n\nSuppose the database contains a table `hr_info` with columns `department_id`, `location_id`, and `manager_id`, and a column of nested table type `people` which has `last_name`, `department_id`, and `salary` columns for all the employees of each respective manager:\n\n```sql\nCREATE TYPE people_typ AS OBJECT (\n last_name VARCHAR2(25),\n department_id NUMBER(4),\n salary NUMBER(8,2));\n/\nCREATE TYPE people_tab_typ AS TABLE OF people_typ;\n/\nCREATE TABLE hr_info (\n department_id NUMBER(4),\n location_id NUMBER(4),\n manager_id NUMBER(6),\n people people_tab_typ)\n NESTED TABLE people STORE AS people_stor_tab;\n\nINSERT INTO hr_info VALUES (280, 1800, 999, people_tab_typ());\n```\n\nThe following example inserts into the `people` nested table column of the `hr_info` table for department 280:\n\n```sql\nINSERT INTO TABLE(SELECT h.people FROM hr_info h\n WHERE h.department_id = 280)\n VALUES ('Smith', 280, 1750);\n```\n\nThe next example updates the department 280 `people` nested table:\n\n```sql\nUPDATE TABLE(SELECT h.people FROM hr_info h\n WHERE h.department_id = 280) p\n SET p.salary = p.salary + 100;\n```\n\nThe next example deletes from the department 280 `people` nested table:\n\n```sql\nDELETE TABLE(SELECT h.people FROM hr_info h\n WHERE h.department_id = 280) p\n WHERE p.salary > 1700;\n```\n\n**Collection Unnesting: Examples** To select data from a nested table column, use the TABLE collection expression to treat the nested table as columns of a table. This process is called **collection unnesting**.\n\nYou could get all the rows from `hr_info`, which was created in the preceding example, and all the rows from the `people` nested table column of `hr_info` using the following statement:\n\nSELECT t1.department_id, t2.*\nFROM hr_info t1, TABLE(t1.people) t2\nWHERE t2.department_id = t1.department_id;\n\nNow suppose that people is not a nested table column of hr_info, but is instead a separate table with columns last_name, department_id, address, hiredate, and salary. You can extract the same rows as in the preceding example with this statement:\n\nSELECT t1.department_id, t2.*\nFROM hr_info t1, TABLE(CAST(MULTISET(\n SELECT t3.last_name, t3.department_id, t3.salary\n FROM people t3\n WHERE t3.department_id = t1.department_id)\nAS people_tab_typ)) t2;\n\nFinally, suppose that people is neither a nested table column of table hr_info nor a table itself. Instead, you have created a function people_func that extracts from various sources the name, department, and salary of all employees. You can get the same information as in the preceding examples with the following query:\n\nSELECT t1.department_id, t2.*\nFROM hr_info t1, TABLE(CAST(people_func(...) AS people_tab_typ)) t2;\n\nSee Also: Oracle Database Object-Relational Developer’s Guide for more examples of collection unnesting.\n\nUsing the LEVEL Pseudocolumn: Examples The following statement returns all employees in hierarchical order. The root row is defined to be the employee whose job is AD_VP. The child rows of a parent row are defined to be those who have the employee number of the parent row as their manager number.\n\n```\nSELECT LPAD(' ', 2*(LEVEL-1)) || last_name org_chart,\n employee_id, manager_id, job_id\nFROM employees\nSTART WITH job_id = 'AD_VP'\nCONNECT BY PRIOR employee_id = manager_id;\n```\n\n| ORG_CHART | EMPLOYEE_ID | MANAGER_ID | JOB_ID |\n|-----------|-------------|------------|----------|\n| Kochhar | 101 | 100 | AD_VP |\n| Greenberg | 108 | 101 | FI_MGR |\n| Faviet | 109 | 108 | FI_ACCOUNT |\n| Chen | 110 | 108 | FI_ACCOUNT |\n| Sciarra | 111 | 108 | FI_ACCOUNT |\n| Urman | 112 | 108 | FI_ACCOUNT |\n| Popp | 113 | 108 | FI_ACCOUNT |\n| Whalen | 200 | 101 | AD_ASST |\n| Mavris | 203 | 101 | HR_REP |\n| Baer | 204 | 101 | PR_REP |\n| Higgins | 205 | 101 | AC_MGR |\n| Gietz | 206 | 205 | AC_ACCOUNT |\n| De Haan | 102 | 100 | AD_VP |\n| Hunold | 103 | 102 | IT_PROG |\n| Ernst | 104 | 103 | IT_PROG |\n| Austin | 105 | 103 | IT_PROG |\n| Pataballa | 106 | 103 | IT_PROG |\n| Lorentz | 107 | 103 | IT_PROG |\n\nThe following statement is similar to the previous one, except that it does not select employees with the job FI_MAN.\n\nSELECT LPAD(' ', 2*(LEVEL-1)) || last_name org_chart,\n employee_id, manager_id, job_id\nFROM employees\nWHERE job_id != 'FI_MGR'\nSTART WITH job_id = 'AD_VP'\nCONNECT BY PRIOR employee_id = manager_id;\n\n| ORG_CHART | EMPLOYEE_ID | MANAGER_ID | JOB_ID |\n|-----------|-------------|------------|------------|\n| Kochhar | 101 | | AD_VP |\n| Faviet | 109 | | FI_ACCOUNT |\n| Chen | 110 | | FI_ACCOUNT |\n| Sciarra | 111 | | FI_ACCOUNT |\n| Urman | 112 | | FI_ACCOUNT |\n| Popp | 113 | | FI_ACCOUNT |\n| Whalen | 200 | | AD_ASST |\n| Mavris | 203 | | HR_REP |\n| Baer | 204 | | PR_REP |\n| Higgins | 205 | | AC_MGR |\n| Gietz | 206 | | AC_ACCOUNT |\n| De Haan | 102 | | AD_VP |\n| Hunold | 103 | | IT_PROG |\n| Ernst | 104 | | IT_PROG |\n| Austin | 105 | | IT_PROG |\n| Pataballa | 106 | | IT_PROG |\n| Lorentz | 107 | | IT_PROG |\n\nOracle Database does not return the manager Greenberg, although it does return employees who are managed by Greenberg.\n\nThe following statement is similar to the first one, except that it uses the LEVEL pseudocolumn to select only the first two levels of the management hierarchy:\n\nSELECT LPAD(' ', 2*(LEVEL-1)) || last_name org_chart,\n employee_id, manager_id, job_id\nFROM employees\nSTART WITH job_id = 'AD_PRES'\nCONNECT BY PRIOR employee_id = manager_id AND LEVEL <= 2;\n\n| ORG_CHART | EMPLOYEE_ID | MANAGER_ID | JOB_ID |\n|-----------|-------------|------------|------------|\n| King | 100 | | AD_PRES |\n| Kochhar | 101 | | AD_VP |\n| De Haan | 102 | | AD_VP |\n| Raphaely | 114 | | FU_MAN |\n| Weiss | 120 | | ST_MAN |\n| Fripp | 121 | | ST_MAN |\n| Kaufling | 122 | | ST_MAN |\n| Vollman | 123 | | ST_MAN |\n| Mourgos | 124 | | ST_MAN |\n| Russell | 145 | | SA_MAN |\n| Partners | 146 | | SA_MAN |\n| Errazuriz | 147 | | SA_MAN |\n| Cambrault | 148 | | SA_MAN |\n| Zlotkey | 149 | | SA_MAN |\n| Hartstein | 201 | | MK_MAN |\n\nUsing Distributed Queries: Example This example shows a query that joins the departments table on the local database with the employees table on the remote database:\n\n```sql\nSELECT last_name, department_name\n FROM employees@remote, departments\n WHERE employees.department_id = departments.department_id;\n```\n\nUsing Correlated Subqueries: Examples The following examples show the general syntax of a correlated subquery:\n\n```sql\nSELECT select_list\n FROM table1 t_alias1\n WHERE expr operator\n (SELECT column_list\n FROM table2 t_alias2\n WHERE t_alias1.column\n operator t_alias2.column);\n\nUPDATE table1 t_alias1\n SET column =\n (SELECT expr\n FROM table2 t_alias2\n WHERE t_alias1.column = t_alias2.column);\n\nDELETE FROM table1 t_alias1\n WHERE column operator\n (SELECT expr\n FROM table2 t_alias2\n WHERE t_alias1.column = t_alias2.column);\n```\n\nThe following statement returns data about employees whose salaries exceed their department average. The following statement assigns an alias to employees, the table containing the salary information, and then uses the alias in a correlated subquery:\n\n```sql\nSELECT department_id, last_name, salary\n FROM employees x\n WHERE salary > (SELECT AVG(salary)\n FROM employees\n WHERE x.department_id = department_id)\n ORDER BY department_id;\n```\n\nFor each row of the employees table, the parent query uses the correlated subquery to compute the average salary for members of the same department. The correlated subquery performs the following steps for each row of the employees table:\n\n1. The department_id of the row is determined.\n2. The department_id is then used to evaluate the parent query.\n3. If the salary in that row is greater than the average salary of the departments of that row, then the row is returned.\n\nThe subquery is evaluated once for each row of the employees table.\n\nSelecting from the DUAL Table: Example The following statement returns the current date:\n\n```sql\nSELECT SYSDATE FROM DUAL;\n```\n\nYou could select SYSDATE from the employees table, but the database would return 14 rows of the same SYSDATE, one for every row of the employees table. Selecting from DUAL is more convenient.\n\n**Selecting Sequence Values: Examples**\n\nThe following statement increments the employees_seq sequence and returns the new value:\n\n```sql\nSELECT employees_seq.nextval\nFROM DUAL;\n```\n\nThe following statement selects the current value of employees_seq:\n\n```sql\nSELECT employees_seq.currval\nFROM DUAL;\n```\n\nSET CONSTRAINT[S]\n\nPurpose\n\nUse the SET CONSTRAINTS statement to specify, for a particular transaction, whether a deferrable constraint is checked following each DML statement (IMMEDIATE) or when the transaction is committed (DEFERRED). You can use this statement to set the mode for a list of constraint names or for ALL constraints.\n\nThe SET CONSTRAINTS mode lasts for the duration of the transaction or until another SET CONSTRAINTS statement resets the mode.\n\nNote: You can also use an ALTER SESSION statement with the SET CONSTRAINTS clause to set all deferrable constraints. This is equivalent to making issuing a SET CONSTRAINTS statement at the start of each transaction in the current session.\n\nYou cannot specify this statement inside of a trigger definition.\n\nSET CONSTRAINTS can be a distributed statement. Existing database links that have transactions in process are notified when a SET CONSTRAINTS ALL statement is issued, and new links are notified that it was issued as soon as they start a transaction.\n\nPrerequisites\n\nTo specify when a deferrable constraint is checked, you must have SELECT privilege on the table to which the constraint is applied unless the table is in your schema.\n\nSyntax\n\nset_constraints::=\n\n\\[\n\\text{SET} \\rightarrow \\{\\text{CONSTRAINT} | \\text{CONSTRAINTS}\\} \\rightarrow \\{\\text{constraint} | \\text{ALL}\\} \\rightarrow \\{\\text{IMMEDIATE} | \\text{DEFERRED}\\} \\rightarrow ;\n\\]\n\nSemantics\n\n**constraint**\n\nSpecify the name of one or more integrity constraints.\n\n**ALL**\n\nSpecify ALL to set all deferrable constraints for this transaction.\n\n**IMMEDIATE**\n\nSpecify IMMEDIATE to cause the specified constraints to be checked immediately on execution of each constrained DML statement. Oracle Database first checks any constraints that were deferred earlier in the transaction and then continues immediately checking constraints of any further statements in that transaction, as long as all the checked constraints are consistent and no other SET CONSTRAINTS\n\nstatement is issued. If any constraint fails the check, then an error is signaled. At that point, a COMMIT statement causes the whole transaction to undo.\n\nMaking constraints immediate at the end of a transaction is a way of checking whether COMMIT can succeed. You can avoid unexpected rollbacks by setting constraints to IMMEDIATE as the last statement in a transaction. If any constraint fails the check, you can then correct the error before committing the transaction.\n\n**DEFERRED**\n\nSpecify DEFERRED to indicate that the conditions specified by the deferrable constraint are checked when the transaction is committed.\n\n---\n\n**Note:** You can verify the success of deferrable constraints prior to committing them by issuing a SET CONSTRAINTS ALL IMMEDIATE statement.\n\n---\n\n### Examples\n\n**Setting Constraints: Examples**\n\nThe following statement sets all deferrable constraints in this transaction to be checked immediately following each DML statement:\n\n```sql\nSET CONSTRAINTS ALL IMMEDIATE;\n```\n\nThe following statement checks three deferred constraints when the transaction is committed. This example fails if the constraints were specified to be NOT DEFERRABLE.\n\n```sql\nSET CONSTRAINTS emp_job_nn, emp_salary_min,\n hr.jhist_dept_fk@remote DEFERRED;\n```\n\nSET ROLE\n\nPurpose\n\nWhen a user logs on to Oracle Database, the database enables all privileges granted explicitly to the user and all privileges in the user’s default roles. During the session, the user or an application can use the SET ROLE statement any number of times to enable or disable the roles currently enabled for the session.\n\nYou cannot enable more than 148 user-defined roles at one time.\n\nNote: For most roles, you cannot enable or disable a role unless it was granted to you either directly or through other roles. However, a secure application role can be granted and enabled by its associated PL/SQL package. See the CREATE ROLE semantics for USING package on page 15-59 and Oracle Database Security Guide for information about secure application roles.\n\nYou can see which roles are currently enabled by examining the SESSION_ROLES data dictionary view.\n\nSee Also:\n\n- CREATE ROLE on page 15-58 for information on creating roles\n- ALTER USER on page 13-5 for information on changing a user’s default roles\n- Oracle Database Reference for information on the SESSION_ROLES session parameter\n\nPrerequisites\n\nYou must already have been granted the roles that you name in the SET ROLE statement.\n\nSyntax\n\nset_role::=\n\nSemantics\n\n**role**\n\nSpecify one or more roles to be enabled for the current session. All roles not specified are disabled for the current session or until another `SET ROLE` statement is issued in the current session.\n\nIn the `IDENTIFIED BY password` clause, specify the password for a role. If the role has a password, then you must specify the password to enable the role.\n\n**Restriction on Setting Roles** You cannot specify a role identified globally. Global roles are enabled by default at login, and cannot be reenabled later.\n\n**ALL Clause**\n\nSpecify `ALL` to enable all roles granted to you for the current session except those optionally listed in the `EXCEPT` clause.\n\nRoles listed in the `EXCEPT` clause must be roles granted directly to you. They cannot be roles granted to you through other roles.\n\nIf you list a role in the `EXCEPT` clause that has been granted to you both directly and through another role, then the role remains enabled by virtue of the role to which it has been granted.\n\n**Restrictions on the ALL Clause** The following restrictions apply to the `ALL` clause:\n\n- You cannot use this clause to enable roles with passwords that have been granted directly to you.\n- You cannot use this clause to enable a secure application role, which is a role that can be enabled only by applications using an authorized package. Refer to *Oracle Database Security Guide* for information on creating a secure application role and *Oracle Database 2 Day + Security Guide* for a tutorial.\n- This clause only enables roles that do not require any authentication.\n\n**NONE**\n\nSpecify `NONE` to disable all roles for the current session, including the `DEFAULT` role.\n\n**Examples**\n\n**Setting Roles: Examples** To enable the role `dw_manager` identified by the password `warehouse` for your current session, issue the following statement:\n\n```\nSET ROLE dw_manager IDENTIFIED BY warehouse;\n```\n\nTo enable all roles granted to you for the current session, issue the following statement:\n\n```\nSET ROLE ALL;\n```\n\nTo enable all roles granted to you except `dw_manager`, issue the following statement:\n\n```\nSET ROLE ALL EXCEPT dw_manager;\n```\n\nTo disable all roles granted to you for the current session, issue the following statement:\n\n```\nSET ROLE NONE;\n```\n\nSET TRANSACTION\n\nPurpose\n\nUse the SET TRANSACTION statement to establish the current transaction as read-only or read/write, establish its isolation level, assign it to a specified rollback segment, or assign a name to the transaction.\n\nA transaction implicitly begins with any operation that obtains a TX lock:\n\n- When a statement that modifies data is issued\n- When a SELECT ... FOR UPDATE statement is issued\n- When a transaction is explicitly started with a SET TRANSACTION statement or the DBMS_TRANSACTION package\n\nIssuing either a COMMIT or ROLLBACK statement explicitly ends the current transaction.\n\nThe operations performed by a SET TRANSACTION statement affect only your current transaction, not other users or other transactions. Your transaction ends whenever you issue a COMMIT or ROLLBACK statement. Oracle Database implicitly commits the current transaction before and after executing a data definition language (DDL) statement.\n\nSee Also: COMMIT on page 13-47 and ROLLBACK on page 18-97\n\nPrerequisites\n\nIf you use a SET TRANSACTION statement, then it must be the first statement in your transaction. However, a transaction need not have a SET TRANSACTION statement.\n\nSyntax\n\nset_transaction::=\n\n\\[\n\\begin{align*}\n\\text{SET} & \\rightarrow \\text{TRANSACTION} \\\\\n& \\rightarrow \\{\\text{READ} \\rightarrow \\{\\text{ONLY} \\rightarrow \\text{WRITE}\\} \\\\\n& \\rightarrow \\{\\text{ISOLATION} \\rightarrow \\text{LEVEL} \\rightarrow \\{\\text{SERIALIZABLE} \\rightarrow \\text{READ} \\rightarrow \\text{COMMITTED}\\} \\\\\n& \\rightarrow \\{\\text{USE} \\rightarrow \\text{ROLLBACK} \\rightarrow \\text{SEGMENT} \\rightarrow \\text{rollback\\_segment}\\} \\\\\n& \\rightarrow \\{\\text{NAME} \\rightarrow \\text{string}\\}\n\\end{align*}\n\\]\n\nSemantics\n\nREAD ONLY\n\nThe READ ONLY clause establishes the current transaction as a read-only transaction. This clause established transaction-level read consistency.\n\nAll subsequent queries in that transaction see only changes that were committed before the transaction began. Read-only transactions are useful for reports that run multiple queries against one or more tables while other users update these same tables.\n\nThis clause is not supported for the user SYS. Queries by SYS will return changes made during the transaction even if SYS has set the transaction to be READ ONLY.\n\n**Restriction on Read-only Transactions** Only the following statements are permitted in a read-only transaction:\n\n- Subqueries—SELECT statements without the `for_update_clause`\n- LOCK TABLE\n- SET ROLE\n- ALTER SESSION\n- ALTER SYSTEM\n\n**READ WRITE**\nSpecify READ WRITE to establish the current transaction as a read/write transaction. This clause establishes **statement-level read consistency**, which is the default.\n\n**Restriction on Read/Write Transactions** You cannot toggle between transaction-level and statement-level read consistency in the same transaction.\n\n**ISOLATION LEVEL Clause**\nUse the ISOLATION LEVEL clause to specify how transactions containing database modifications are handled.\n\n- The SERIALIZABLE setting specifies serializable transaction isolation mode as defined in the SQL standard. If a serializable transaction contains data manipulation language (DML) that attempts to update any resource that may have been updated in a transaction uncommitted at the start of the serializable transaction, then the DML statement fails.\n\n- The READ COMMITTED setting is the default Oracle Database transaction behavior. If the transaction contains DML that requires row locks held by another transaction, then the DML statement waits until the row locks are released.\n\n**USE ROLLBACK SEGMENT Clause**\n\nNote: This clause is relevant and valid only if you are using rollback segments for undo. Oracle strongly recommends that you use automatic undo management to handle undo space. If you follow this recommendation and run your database in automatic undo mode, then Oracle Database ignores this clause.\n\nSpecify USE ROLLBACK SEGMENT to assign the current transaction to the specified rollback segment. This clause also implicitly establishes the transaction as a read/write transaction.\n\nParallel DML requires more than one rollback segment. Therefore, if your transaction contains parallel DML operations, then the database ignores this clause.\n\n**NAME Clause**\nUse the NAME clause to assign a name to the current transaction. This clause is especially useful in distributed database environments when you must identify and resolve in-doubt transactions. The string value is limited to 255 bytes.\n\nIf you specify a name for a distributed transaction, then when the transaction commits, the name becomes the commit comment, overriding any comment specified explicitly in the COMMIT statement.\n\n**See Also:** *Oracle Database Concepts* for more information about transaction naming\n\n### Examples\n\n**Setting Transactions: Examples** The following statements could be run at midnight of the last day of every month to count the products and quantities on hand in the Toronto warehouse in the sample Order Entry (oe) schema. This report would not be affected by any other user who might be adding or removing inventory to a different warehouse.\n\n```\nCOMMIT;\n\nSET TRANSACTION READ ONLY NAME 'Toronto';\n\nSELECT product_id, quantity_on_hand FROM inventories\n WHERE warehouse_id = 5\n ORDER BY product_id;\n\nCOMMIT;\n```\n\nThe first COMMIT statement ensures that SET TRANSACTION is the first statement in the transaction. The last COMMIT statement does not actually make permanent any changes to the database. It simply ends the read-only transaction.\n\nTRUNCATE CLUSTER\n\nPurpose\n\nCaution: You cannot roll back a TRUNCATE CLUSTER statement.\n\nUse the TRUNCATE CLUSTER statement to remove all rows from a cluster. By default, Oracle Database also performs the following tasks:\n\n- Deallocates all space used by the removed rows except that specified by the MINEXTENTS storage parameter\n- Sets the NEXT storage parameter to the size of the last extent removed from the segment by the truncation process\n\nRemoving rows with the TRUNCATE statement can be more efficient than dropping and re-creating a cluster. Dropping and re-creating a cluster invalidates dependent objects of the cluster, requires you to regrant object privileges on the cluster, and requires you to re-create the indexes and cluster on the table and respecify its storage parameters. Truncating has none of these effects.\n\nRemoving rows with the TRUNCATE CLUSTER statement can be faster than removing all rows with the DELETE statement, especially if the cluster has numerous indexes and other dependencies.\n\nSee Also:\n- DELETE on page 17-26 and DROP CLUSTER on page 17-36 for information on other ways of dropping data from a cluster\n- TRUNCATE TABLE on page 19-68 for information on truncating a table\n\nPrerequisites\n\nTo truncate a cluster, the cluster must be in your schema or you must have DROP ANY TABLE system privilege.\n\nSee Also: \"Restrictions on Truncating Tables\" on page 19-70\n\nSyntax\n\n```\ntruncate_cluster :=\n TRUNCATE CLUSTER [schema] cluster [DROP | REUSE] STORAGE ;\n```\n\nSemantics\n\n**CLUSTER Clause**\n\nSpecify the schema and name of the cluster to be truncated. You can truncate only an indexed cluster, not a hash cluster. If you omit `schema`, then the database assumes the cluster is in your own schema.\n\nWhen you truncate a cluster, the database also automatically deletes all data in the indexes of the cluster tables.\n\n**STORAGE Clauses**\n\nThe STORAGE clauses let you determine what happens to the space freed by the truncated rows. The DROP STORAGE clause and REUSE STORAGE clause also apply to the space freed by the data deleted from associated indexes.\n\n**DROP STORAGE** Specify DROP STORAGE to deallocate all space from the deleted rows from the cluster except the space allocated by the MINEXTENTS parameter of the cluster. This space can subsequently be used by other objects in the tablespace. Oracle Database also sets the NEXT storage parameter to the size of the last extent removed from the segment in the truncation process. This is the default.\n\n**REUSE STORAGE** Specify REUSE STORAGE to retain the space from the deleted rows allocated to the cluster. Storage values are not reset to the values when the table or cluster was created. This space can subsequently be used only by new data in the cluster resulting from insert or update operations. This clause leaves storage parameters at their current settings.\n\nIf you have specified more than one free list for the object you are truncating, then the REUSE STORAGE clause also removes any mapping of free lists to instances and resets the high-water mark to the beginning of the first extent.\n\n**Examples**\n\n**Truncating a Cluster: Example** The following statement removes all rows from all tables in the personnel cluster, but leaves the freed space allocated to the tables:\n\n```\nTRUNCATE CLUSTER personnel REUSE STORAGE;\n```\n\nThe preceding statement also removes all data from all indexes on the tables in the personnel cluster.\n\nTRUNCATE TABLE\n\nPurpose\n\nCaution: You cannot roll back a TRUNCATE TABLE statement, nor can you use a FLASHBACK TABLE statement to retrieve the contents of a table that has been truncated.\n\nUse the TRUNCATE TABLE statement to remove all rows from a table. By default, Oracle Database also performs the following tasks:\n\n- Deallocates all space used by the removed rows except that specified by the MINEXTENTS storage parameter\n- Sets the NEXT storage parameter to the size of the last extent removed from the segment by the truncation process\n\nRemoving rows with the TRUNCATE TABLE statement can be more efficient than dropping and re-creating a table. Dropping and re-creating a table invalidates dependent objects of the table, requires you to regrant object privileges on the table, and requires you to re-create the indexes, integrity constraints, and triggers on the table and respecify its storage parameters. Truncating has none of these effects.\n\nRemoving rows with the TRUNCATE TABLE statement can be faster than removing all rows with the DELETE statement, especially if the table has numerous triggers, indexes, and other dependencies.\n\nSee Also:\n- DELETE on page 17-26 and DROP TABLE on page 18-5 for information on other ways of removing data from a table\n- TRUNCATE CLUSTER on page 19-66 for information on truncating a cluster\n\nPrerequisites\n\nTo truncate a table, the table must be in your schema or you must have DROP ANY TABLE system privilege.\n\nSee Also: \"Restrictions on Truncating Tables\" on page 19-70\n\nSyntax\n\n`truncate_table ::=`\n\n```\nTRUNCATE TABLE [schema] table\n [ALL | REUSE]\n [PRESERVE | PURGE]\n [MATERIALIZED | VIEW | LOG]\n [STORAGE];\n```\n\nSemantics\n\n**TABLE Clause**\n\nSpecify the schema and name of the table to be truncated. This table cannot be part of a cluster. If you omit `schema`, then Oracle Database assumes the table is in your own schema.\n\n- You can truncate index-organized tables and temporary tables. When you truncate a temporary table, only the rows created during the current session are removed.\n\n- Oracle Database changes the `NEXT` storage parameter of `table` to be the size of the last extent deleted from the segment in the process of truncation.\n\n- Oracle Database also automatically truncates and resets any existing `UNUSABLE` indicators for the following indexes on `table`: range and hash partitions of local indexes and subpartitions of local indexes.\n\n- If `table` is not empty, then the database marks `UNUSABLE` all nonpartitioned indexes and all partitions of global partitioned indexes on the table. However, when the table is truncated, the index is also truncated, and a new high water mark is calculated for the index segment. This operation is equivalent to creating a new segment for the index. Therefore, at the end of the truncate operation, the indexes are once again `USABLE`.\n\n- For a domain index, this statement invokes the appropriate truncate routine to truncate the domain index data.\n\n**See Also:** *Oracle Database Data Cartridge Developer’s Guide* for more information on domain indexes\n\n- If a regular or index-organized table contains LOB columns, then all LOB data and LOB index segments are truncated.\n\n- If `table` is partitioned, then all partitions or subpartitions, as well as the LOB data and LOB index segments for each partition or subpartition, are truncated.\n\nNote: When you truncate a table, Oracle Database automatically removes all data in the table's indexes and any materialized view direct-path INSERT information held in association with the table. This information is independent of any materialized view log. If this direct-path INSERT information is removed, then an incremental refresh of the materialized view may lose data.\n\nRestrictions on Truncating Tables This statement is subject to the following restrictions:\n\n- You cannot individually truncate a table that is part of a cluster. You must either truncate the cluster, delete all rows from the table, or drop and re-create the table.\n\n- You cannot truncate the parent table of an enabled foreign key constraint. You must disable the constraint before truncating the table. An exception is that you can truncate the table if the integrity constraint is self-referential.\n\n- If a domain index is defined on `table`, then neither the index nor any index partitions can be marked IN_PROGRESS.\n\n- You cannot truncate the parent table of a reference-partitioned table. You must first drop the reference-partitioned child table.\n\nMATERIALIZED VIEW LOG Clause\n\nThe `MATERIALIZED VIEW LOG` clause lets you specify whether a materialized view log defined on the table is to be preserved or purged when the table is truncated. This clause permits materialized view master tables to be reorganized through export or import without affecting the ability of primary key materialized views defined on the master to be fast refreshed. To support continued fast refresh of primary key materialized views, the materialized view log must record primary key information.\n\nNote: The keyword `SNAPSHOT` is supported in place of `MATERIALIZED VIEW` for backward compatibility.\n\nPRESERVE Specify `PRESERVE` if any materialized view log should be preserved when the master table is truncated. This is the default.\n\nPURGE Specify `PURGE` if any materialized view log should be purged when the master table is truncated.\n\nSee Also: *Oracle Database Advanced Replication* for more information about materialized view logs and the `TRUNCATE` statement\n\nSTORAGE Clauses\n\nThe `STORAGE` clauses let you determine what happens to the space freed by the truncated rows. The `DROP STORAGE` clause, `DROP ALL STORAGE` clause, and `REUSE STORAGE` clause also apply to the space freed by the data deleted from associated indexes.\n\nDROP STORAGE Specify `DROP STORAGE` to deallocate all space from the deleted rows from the table except the space allocated by the `MINEXTENTS` parameter of the table. This space can subsequently be used by other objects in the tablespace. Oracle Database also sets the `NEXT` storage parameter to the size of the last extent removed from the segment in the truncation process. This setting, which is the default, is useful\n\nfor small and medium-sized objects. The extent management in locally managed tablespace is very fast in these cases, so there is no need to reserve space.\n\n**DROP ALL STORAGE** Specify **DROP ALL STORAGE** to deallocate all space from the deleted rows from the table, including the space allocated by the **MINEXTENTS** parameter. All segments for the table, as well as all segments for its dependent objects, will be deallocated.\n\n**Restrictions on DROP ALL STORAGE** This clause is subject to the same restrictions as described in \"Restrictions on Deferred Segment Creation\" on page 16-33.\n\n---\n\n**Note:** The **DROP ALL STORAGE** clause is available starting with Oracle Database 11g Release 2 (18.104.22.168).\n\n---\n\n**REUSE STORAGE** Specify **REUSE STORAGE** to retain the space from the deleted rows allocated to the table. Storage values are not reset to the values when the table was created. This space can subsequently be used only by new data in the table resulting from insert or update operations. This clause leaves storage parameters at their current settings.\n\nThis setting is useful as an alternative to deleting all rows of a very large table—when the number of rows is very large, the table entails many thousands of extents, and when data is to be reinserted in the future. **TRUNCATE TABLE** with **REUSE STORAGE** performs several orders of magnitude faster than deleting all rows, but has the following drawbacks:\n\n- You cannot roll back a **TRUNCATE TABLE** statement.\n- All cursors are invalidated.\n- You cannot flash back to the state of the table before the truncate operation.\n\nThis clause is not valid for temporary tables. A session becomes unbound from the temporary table when the table is truncated, so the storage is automatically dropped.\n\nIf you have specified more than one free list for the object you are truncating, then the **REUSE STORAGE** clause also removes any mapping of free lists to instances and resets the high-water mark to the beginning of the first extent.\n\n**Examples**\n\n**Truncating a Table: Example** The following statement removes all rows from a hypothetical copy of the sample table `hr.employees` and returns the freed space to the tablespace containing `employees`:\n\n```sql\nTRUNCATE TABLE employees_demo;\n```\n\nThe preceding statement also removes all data from all indexes on `employees` and returns the freed space to the tablespaces containing them.\n\n**Preserving Materialized View Logs After Truncate: Example** The following statements are examples of **TRUNCATE** statements that preserve materialized view logs:\n\n```sql\nTRUNCATE TABLE sales_demo PRESERVE MATERIALIZED VIEW LOG;\n\nTRUNCATE TABLE orders_demo;\n```\n\nUPDATE\n\nPurpose\n\nUse the UPDATE statement to change existing values in a table or in the base table of a view or the master table of a materialized view.\n\nPrerequisites\n\nFor you to update values in a table, the table must be in your own schema or you must have the UPDATE object privilege on the table.\n\nFor you to update values in the base table of a view:\n\n- You must have the UPDATE object privilege on the view, and\n- Whoever owns the schema containing the view must have the UPDATE object privilege on the base table.\n\nThe UPDATE ANY TABLE system privilege also allows you to update values in any table or in the base table of any view.\n\nYou must also have the SELECT object privilege on the object you want to update if:\n\n- The object is on a remote database or\n- The SQL92_SECURITY initialization parameter is set to TRUE and the UPDATE operation references table columns, such as the columns in a where_clause.\n\nSyntax\n\nupdate::=\n\n\\[\\text{UPDATE} \\rightarrow \\text{hint} \\rightarrow \\{\\text{dml\\_table\\_expression\\_clause}\\} \\rightarrow \\{\\text{ONLY} \\rightarrow (\\{\\text{dml\\_table\\_expression\\_clause}\\})\\} \\rightarrow \\{\\text{t\\_alias}\\} \\rightarrow \\{\\text{update\\_set\\_clause}\\} \\rightarrow \\{\\text{where\\_clause}\\} \\rightarrow \\{\\text{returning\\_clause}\\} \\rightarrow \\{\\text{error\\_logging\\_clause}\\} \\rightarrow \\{\\}\\]\n\n(DML_table_expression_clause::= on page 19-72, update_set_clause::= on page 19-73, where_clause::= on page 19-73, returning_clause::= on page 19-73, error_logging_clause::= on page 19-74)\n\nDML_table_expression_clause::=\n\n(partition_extension_clause::= on page 19-73, subquery::= on page 19-5--part of SELECT, subquery_restriction_clause::= on page 19-73, table_collection_expression::= on page 19-73)\n\npartition_extension_clause::=\n\n```\nPARTITION (partition)\nFOR (partition_key_value)\nSUBPARTITION (subpartition)\nFOR (subpartition_key_value)\n```\n\nsubquery_restriction_clause::=\n\n```\nWITH (READ ONLY | CHECK OPTION) CONSTRAINT constraint\n```\n\ntable_collection_expression::=\n\n```\nTABLE (collection_expression)\n```\n\nupdate_set_clause::=\n\n```\nSET (column = subquery | column = expr | column = DEFAULT | VALUE (t_alias) = expr | VALUE (t_alias) = subquery)\n```\n\nwhere_clause::=\n\n```\nWHERE condition\n```\n\nreturning_clause::=\n\n```\nRETURN | RETURNING (expr INTO data_item)\n```\n\nerror_logging_clause ::=\n\nLOG ERRORS INTO schema table (simple_expression) REJECT LIMIT integer | UNLIMITED\n\nSemantics\n\nhint\nSpecify a comment that passes instructions to the optimizer on choosing an execution plan for the statement.\n\nYou can place a parallel hint immediately after the UPDATE keyword to parallelize both the underlying scan and UPDATE operations.\n\nSee Also:\n- \"Hints\" on page 3-73 for the syntax and description of hints\n- Oracle Database Concepts for detailed information about parallel execution\n\nDML_table_expression_clause\nThe ONLY clause applies only to views. Specify ONLY syntax if the view in the UPDATE clause is a view that belongs to a hierarchy and you do not want to update rows from any of its subviews.\n\nSee Also: \"Restrictions on the DML_table_expression_clause\" on page 19-76 and \"Updating a Table: Examples\" on page 19-79\n\nschema\nSpecify the schema containing the object to be updated. If you omit schema, then the database assumes the object is in your own schema.\n\ntable | view | materialized_view | subquery\nSpecify the name of the table, view, materialized view, or the columns returned by a subquery to be updated. Issuing an UPDATE statement against a table fires any UPDATE triggers associated with the table.\n\n- If you specify view, then the database updates the base table of the view. You cannot update a view except with INSTEAD OF triggers if the defining query of the view contains one of the following constructs:\n\nA set operator\nA DISTINCT operator\nAn aggregate or analytic function\nA GROUP BY, ORDER BY, MODEL, CONNECT BY, or START WITH clause\nA collection expression in a SELECT list\nA subquery in a SELECT list\nA subquery designated WITH READ ONLY\n\nJoins, with some exceptions, as documented in *Oracle Database Administrator’s Guide*\n\n- You cannot update more than one base table through a view.\n\n- In addition, if the view was created with the `WITH CHECK OPTION`, then you can update the view only if the resulting data satisfies the view’s defining query.\n\n- If `table` or the base table of `view` contains one or more domain index columns, then this statement executes the appropriate indextype update routine.\n\n- You cannot update rows in a read-only materialized view. If you update rows in a writable materialized view, then the database updates the rows from the underlying container table. However, the updates are overwritten at the next refresh operation. If you update rows in an updatable materialized view that is part of a materialized view group, then the database also updates the corresponding rows in the master table.\n\n**See Also:**\n\n- *Oracle Database Data Cartridge Developer’s Guide* for more information on the indextype update routines\n\n- [CREATE MATERIALIZED VIEW](#) on page 15-3 for information on creating updatable materialized views\n\n**partition_extension_clause**\n\nSpecify the name or partition key value of the partition or subpartition within `table` targeted for updates. You need not specify the partition name when updating values in a partitioned table. However in some cases specifying the partition name can be more efficient than a complicated `where_clause`.\n\n**See Also:** “References to Partitioned Tables and Indexes” on page 3-116 and “Updating a Partition: Example” on page 19-80\n\n**dblink**\n\nSpecify a complete or partial name of a database link to a remote database where the object is located. You can use a database link to update a remote object only if you are using Oracle Database distributed functionality.\n\nIf you omit `dblink`, then the database assumes the object is on the local database.\n\n**See Also:** “References to Objects in Remote Databases” on page 3-114 for information on referring to database links\n\n**subquery_restriction_clause**\n\nUse the `subquery_restriction_clause` to restrict the subquery in one of the following ways:\n\n**WITH READ ONLY** Specify `WITH READ ONLY` to indicate that the table or view cannot be updated.\n\n**WITH CHECK OPTION** Specify `WITH CHECK OPTION` to indicate that Oracle Database prohibits any changes to the table or view that would produce rows that are not included in the subquery. When used in the subquery of a DML statement, you can specify this clause in a subquery in the `FROM` clause but not in subquery in the `WHERE` clause.\n\n**CONSTRAINT constraint** Specify the name of the CHECK OPTION constraint. If you omit this identifier, then Oracle automatically assigns the constraint a name of the form SYS_Cn, where n is an integer that makes the constraint name unique within the database.\n\n*See Also:* \"Using the WITH CHECK OPTION Clause: Example\" on page 19-48\n\n**table_collection_expression**\n\nThe *table_collection_expression* lets you inform Oracle that the value of *collection_expression* should be treated as a table for purposes of query and DML operations. The *collection_expression* can be a subquery, a column, a function, or a collection constructor. Regardless of its form, it must return a collection value—that is, a value whose type is nested table or varray. This process of extracting the elements of a collection is called **collection unnesting**.\n\nThe optional plus (+) is relevant if you are joining the TABLE collection expression with the parent table. The + creates an outer join of the two, so that the query returns rows from the outer table even if the collection expression is null.\n\n---\n\n**Note:** In earlier releases of Oracle, when *collection_expression* was a subquery, *table_collection_expression* was expressed as THE *subquery*. That usage is now deprecated.\n\n---\n\nYou can use a *table_collection_expression* to update rows in one table based on rows from another table. For example, you could roll up four quarterly sales tables into a yearly sales table.\n\n**t_alias**\n\nSpecify a **correlation name** (alias) for the table, view, or subquery to be referenced elsewhere in the statement. This alias is required if the *DML_table_expression_clause* references any object type attributes or object type methods.\n\n*See Also:* \"Correlated Update: Example\" on page 19-80\n\n**Restrictions on the DML_table_expression_clause** This clause is subject to the following restrictions:\n\n- You cannot execute this statement if *table* or the base table of *view* contains any domain indexes marked IN_PROGRESS or FAILED.\n\n- You cannot insert into a partition if any affected index partitions are marked UNUSABLE.\n\n- You cannot specify the *order_by_clause* in the subquery of the *DML_table_expression_clause*.\n\n- If you specify an index, index partition, or index subpartition that has been marked UNUSABLE, then the UPDATE statement will fail unless the SKIP_UNUSABLE_INDEXES session parameter has been set to TRUE.\n\n*See Also:* ALTER SESSION on page 11-45 for information on the SKIP_UNUSABLE_INDEXES session parameter\n\n**update_set_clause**\n\nThe *update_set_clause* lets you set column values.\n\ncolumn\n\nSpecify the name of a column of the object that is to be updated. If you omit a column of the table from the update_set_clause, then the value of that column remains unchanged.\n\nIf column refers to a LOB object attribute, then you must first initialize it with a value of empty or null. You cannot update it with a literal. Also, if you are updating a LOB value using some method other than a direct UPDATE SQL statement, then you must first lock the row containing the LOB. See for_update_clause on page 19-34 for more information.\n\nIf column is a virtual column, you cannot specify it here. Rather, you must update the values from which the virtual column is derived.\n\nIf column is part of the partitioning key of a partitioned table, then UPDATE will fail if you change a value in the column that would move the row to a different partition or subpartition, unless you enable row movement. Refer to the row_movement_clause of CREATE TABLE on page 16-6 or ALTER TABLE on page 12-2.\n\nIn addition, if column is part of the partitioning key of a list-partitioned table, then UPDATE will fail if you specify a value for the column that does not already exist in the partition_key_value list of one of the partitions.\n\nsubquery\n\nSpecify a subquery that returns exactly one row for each row updated.\n\n- If you specify only one column in the update_set_clause, then the subquery can return only one value.\n- If you specify multiple columns in the update_set_clause, then the subquery must return as many values as you have specified columns.\n- If the subquery returns no rows, then the column is assigned a null.\n- If this subquery refers to remote objects, then the UPDATE operation can run in parallel as long as the reference does not loop back to an object on the local database. However, if the subquery in the DML_table_expression_clause refers to any remote objects, then the UPDATE operation will run serially without notification.\n\nYou can use the flashback_query_clause within the subquery to update table with past data. Refer to the flashback_query_clause of SELECT on page 19-17 for more information on this clause.\n\nSee Also:\n\n- SELECT on page 19-4 and \"Using Subqueries\" on page 9-14\n- parallel_clause on page 16-66 in the CREATE TABLE documentation\n\nexpr\n\nSpecify an expression that resolves to the new value assigned to the corresponding column.\n\nSee Also: Chapter 6, \"Expressions\" for the syntax of expr and \"Updating an Object Table: Example\" on page 19-80\n\nDEFAULT Specify DEFAULT to set the column to the value previously specified as the default value for the column. If no default value for the corresponding column has been specified, then the database sets the column to null.\n\nRestriction on Updating to Default Values You cannot specify DEFAULT if you are updating a view.\n\nVALUE Clause\n\nThe VALUE clause lets you specify the entire row of an object table.\n\nRestriction on the VALUE clause You can specify this clause only for an object table.\n\nNote: If you insert string literals into a RAW column, then during subsequent queries, Oracle Database will perform a full table scan rather than using any index that might exist on the RAW column.\n\nSee Also: \"Updating an Object Table: Example\" on page 19-80\n\nwhere_clause\n\nThe where_clause lets you restrict the rows updated to those for which the specified condition is true. If you omit this clause, then the database updates all rows in the table or view. Refer to Chapter 7, \"Conditions\" for the syntax of condition.\n\nThe where_clause determines the rows in which values are updated. If you do not specify the where_clause, then all rows are updated. For each row that satisfies the where_clause, the columns to the left of the equality operator (=) in the update_set_clause are set to the values of the corresponding expressions to the right of the operator. The expressions are evaluated as the row is updated.\n\nreturning_clause\n\nThe returning clause retrieves the rows affected by a DML statement. You can specify this clause for tables and materialized views and for views with a single base table.\n\nWhen operating on a single row, a DML statement with a returning_clause can retrieve column expressions using the affected row, rowid, and REFS to the affected row and store them in host variables or PL/SQL variables.\n\nWhen operating on multiple rows, a DML statement with the returning_clause stores values from expressions, rowids, and REFS involving the affected rows in bind arrays.\n\nexpr Each item in the expr list must be a valid expression syntax.\n\nINTO The INTO clause indicates that the values of the changed rows are to be stored in the variable(s) specified in data_item list.\n\ndata_item Each data_item is a host variable or PL/SQL variable that stores the retrieved expr value.\n\nFor each expression in the RETURNING list, you must specify a corresponding type-compatible PL/SQL variable or host variable in the INTO list.\n\nRestrictions The following restrictions apply to the RETURNING clause:\n\n- The expr is restricted as follows:\n\nFor UPDATE and DELETE statements each expr must be a simple expression or a single-set aggregate function expression. You cannot combine simple expressions and single-set aggregate function expressions in the same returning_clause. For INSERT statements, each expr must be a simple expression. Aggregate functions are not supported in an INSERT statement RETURNING clause.\n\nSingle-set aggregate function expressions cannot include the DISTINCT keyword.\n\n- If the expr list contains a primary key column or other NOT NULL column, then the update statement fails if the table has a BEFORE UPDATE trigger defined on it.\n- You cannot specify the returning_clause for a multitable insert.\n- You cannot use this clause with parallel DML or with remote objects.\n- You cannot retrieve LONG types with this clause.\n- You cannot specify this clause for a view on which an INSTEAD OF trigger has been defined.\n\nSee Also: Oracle Database PL/SQL Language Reference for information on using the BULK COLLECT clause to return multiple values to collection variables\n\nerror_logging_clause\n\nThe error_logging_clause has the same behavior in an UPDATE statement as it does in an INSERT statement. Refer to the INSERT statement error_logging_clause on page 18-65 for more information.\n\nSee Also: \"Inserting Into a Table with Error Logging: Example\" on page 18-66\n\nExamples\n\nUpdating a Table: Examples The following statement gives null commissions to all employees with the job SH_CLERK:\n\n```sql\nUPDATE employees\n SET commission_pct = NULL\nWHERE job_id = 'SH_CLERK';\n```\n\nThe following statement promotes Douglas Grant to manager of Department 20 with a $1,000 raise:\n\n```sql\nUPDATE employees SET\n job_id = 'SA_MAN', salary = salary + 1000, department_id = 120\n WHERE first_name||' '||last_name = 'Douglas Grant';\n```\n\nThe following statement increases the salary of an employee in the employees table on the remote database:\n\n```sql\nUPDATE employees@remote\n SET salary = salary*1.1\nWHERE last_name = 'Baer';\n```\n\nThe next example shows the following syntactic constructs of the UPDATE statement:\n\n- Both forms of the update_set_clause together in a single statement\n\n- A correlated subquery\n- A `where_clause` to limit the updated rows\n\n```sql\nUPDATE employees a\n SET department_id =\n (SELECT department_id\n FROM departments\n WHERE location_id = '2100'),\n (salary, commission_pct) =\n (SELECT 1.1*AVG(salary), 1.5*AVG(commission_pct)\n FROM employees b\n WHERE a.department_id = b.department_id)\nWHERE department_id IN\n (SELECT department_id\n FROM departments\n WHERE location_id = 2900\n OR location_id = 2700);\n```\n\nThe preceding `UPDATE` statement performs the following operations:\n\n- Updates only those employees who work in Geneva or Munich (locations 2900 and 2700)\n- Sets `department_id` for these employees to the `department_id` corresponding to Bombay (location_id 2100)\n- Sets each employee's salary to 1.1 times the average salary of their department\n- Sets each employee's commission to 1.5 times the average commission of their department\n\n**Updating a Partition: Example** The following example updates values in a single partition of the `sales` table:\n\n```sql\nUPDATE sales PARTITION (sales_q1_1999) s\n SET s.promo_id = 494\n WHERE amount_sold > 1000;\n```\n\n**Updating an Object Table: Example** The following statement creates two object tables, `people_demo1` and `people_demo2`, of the `people_typ` object created in \"Table Collections: Examples\" on page 19-54. The example shows how to update a row of `people_demo1` by selecting a row from `people_demo2`:\n\n```sql\nCREATE TABLE people_demo1 OF people_typ;\n\nCREATE TABLE people_demo2 OF people_typ;\n\nUPDATE people_demo1 p SET VALUE(p) =\n (SELECT VALUE(q) FROM people_demo2 q\n WHERE p.department_id = q.department_id)\n WHERE p.department_id = 10;\n```\n\nThe example uses the `VALUE` object reference function in both the `SET` clause and the subquery.\n\n**Correlated Update: Example** For an example that uses a correlated subquery to update nested table rows, refer to \"Table Collections: Examples\" on page 19-54.\n\n**Using the RETURNING Clause During UPDATE: Example** The following example returns values from the updated row and stores the result in PL/SQL variables `bnd1`, `bnd2`, `bnd3`:\n\nThe following example shows that you can specify a single-set aggregate function in the expression of the returning clause:\n\n```sql\nUPDATE employees\n SET salary = salary * 1.1\n WHERE department_id = 100\n RETURNING SUM(salary) INTO :bnd1;\n```\n\nUPDATE\n\nHow to Read Syntax Diagrams\n\nThis appendix describes how to read syntax diagrams.\n\nGraphic Syntax Diagrams\n\nSyntax diagrams are drawings that illustrate valid SQL syntax. To read a diagram, trace it from left to right, in the direction shown by the arrows.\n\nCommands and other keywords appear in UPPERCASE inside rectangles. Type them exactly as shown in the rectangles. Parameters appear in lowercase inside ovals. Variables are used for the parameters. Punctuation, operators, delimiters, and terminators appear inside circles.\n\nIf the syntax diagram has more than one path, then you can choose any path. For example, in the following syntax you can specify either NOPARALLEL or PARALLEL:\n\n```\nparallel_clause::=\n→NOPARALLEL\n→PARALLEL→integer\n```\n\nIf you have the choice of more than one keyword, operator, or parameter, then your options appear in a vertical list. For example, in the following syntax diagram, you can specify one or more of the four parameters in the stack:\n\n```\nphysical_attributes_clause::=\n→PCTFREE→integer\n→PCTUSED→integer\n→INITTRANS→integer\n→storage_clause\n```\n\nThe following table shows parameters that appear in the syntax diagrams and provides examples of the values you might substitute for them in your statements:\n\n| Parameter | Description | Examples |\n|-----------|------------------------------------------------------------------------------|---------------------------|\n| table | The substitution value must be the name of an object of the type specified by the parameter. For a list of all types of objects, see the section, \"Schema Objects\" on page 3-107. | employees |\n| c | The substitution value must be a single character from your database character set. | T |\n| | | s |\n| 'text' | The substitution value must be a text string in single quotation marks. See the syntax description of 'text' in \"Text Literals\" on page 3-45. | 'Employee records' |\n| char | The substitution value must be an expression of data type CHAR or VARCHAR2 or a character literal in single quotation marks. | last_name |\n| | | 'Smith' |\n| condition | The substitution value must be a condition that evaluates to TRUE or FALSE. See the syntax description of condition in Chapter 7, \"Conditions\". | last_name > 'A' |\n| date | The substitution value must be a date constant or an expression of DATE data type. | TO_DATE( |\n| d | | '01-Jan-2002', |\n| | | 'DD-MON-YYYY') |\n| expr | The substitution value can be an expression of any data type as defined in the syntax description of 'expr' in \"About SQL Expressions\" on page 6-1. | salary + 1000 |\n| integer | The substitution value must be an integer as defined by the syntax description of integer in \"Integer Literals\" on page 3-47. | 72 |\n| number | The substitution value must be an expression of NUMBER data type or a number constant as defined in the syntax description of number in \"Numeric Literals\" on page 3-47. | AVG(salary) |\n| m | | 15 * 7 |\n| n | | |\n| raw | The substitution value must be an expression of data type RAW. | HEXTORAW('7D') |\n| subquery | The substitution value must be a SELECT statement that will be used in another SQL statement. See SELECT on page 19-4. | SELECT last_name |\n| | | FROM employees |\n| db_name | The substitution value must be the name of a nondefault database in an embedded SQL program. | sales_db |\n| db_string | The substitution value must be the database identification string for an Oracle Net database connection. For details, see the user's guide for your specific Oracle Net protocol. | — |\n\n**Required Keywords and Parameters**\n\nRequired keywords and parameters can appear singly or in a vertical list of alternatives. Single required keywords and parameters appear on the main path, which is the horizontal line you are currently traveling. In the following example, `library_name` is a required parameter:\n\n**drop_library::=**\n\n```\nDROP LIBRARY <library_name>;\n```\n\nIf there is a library named `HQ_LIB`, then, according to the diagram, the following statement is valid:\n\n```\nDROP LIBRARY hq_lib;\n```\n\nIf multiple keywords or parameters appear in a vertical list that intersects the main path, then one of them is required. You must choose one of the keywords or parameters, but not necessarily the one that appears on the main path. In the following example, you must choose one of the two settings:\n\n**key_compression::=**\n\n```\nCOMPRESS\nNOCOMPRESS\n```\n\n### Optional Keywords and Parameters\n\nIf keywords and parameters appear in a vertical list above the main path, then they are optional. In the following example, instead of traveling down a vertical line, you can continue along the main path:\n\n**deallocate_unused_clause::=**\n\n```\nDEALLOCATE UNUSED KEEP <size_clause>;\n```\n\n**size_clause::=**\n\n```\nK\nM\nG\nT\nP\nE\ninteger\n```\n\nAccording to the diagrams, all of the following statements are valid:\n\n```\nDEALLOCATE UNUSED;\nDEALLOCATE UNUSED KEEP 1000;\nDEALLOCATE UNUSED KEEP 10G;\nDEALLOCATE UNUSED 8T;\n```\n\n### Syntax Loops\n\nLoops let you repeat the syntax within them as many times as you like. In the following example, after choosing one value expression, you can go back repeatedly to choose another, separated by commas.\n\nMultipart Diagrams\n\nRead a multipart diagram as if all the main paths were joined end to end. The following example is a three-part diagram:\n\n```\nalter_java::=\n\n→ ALTER → JAVA → {SOURCE | CLASS} → {schema} → . → {object_name} →\n→ {RESOLVER} → ( → {match_string} → , → {schema_name} → ) → ) → )\n→ {COMPILE | RESOLVE | invoker_rights_clause} → ;\n```\n\nAccording to the diagram, the following statement is valid:\n\n```\nALTER JAVA SOURCE jsource_1 COMPILE;\n```\n\nDatabase Objects\n\nThe names of Oracle identifiers, such as tables and columns, must not exceed 30 characters in length. The first character must be a letter, but the rest can be any combination of letters, numerals, dollar signs ($), pound signs (#), and underscores (_).\n\nHowever, if an Oracle identifier is enclosed by double quotation marks (\"), then it can contain any combination of legal characters, including spaces but excluding quotation marks. Oracle identifiers are not case sensitive except within double quotation marks.\n\nSee Also: \"Database Object Naming Rules\" on page 3-108 for more information\n\nAutomatic and Manual Locking Mechanisms During SQL Operations\n\nThis appendix describes mechanisms that lock data either automatically or as specified by the user during SQL statements. For a general discussion of locking mechanisms in the context of data concurrency and consistency, see *Oracle Database Concepts*.\n\nThis appendix contains the following sections:\n\n- Automatic Locks in DML Operations\n- Automatic Locks in DDL Operations\n- Manual Data Locking\n\n**Automatic Locks in DML Operations**\n\nThe purpose of a DML lock, also called a **data lock**, is to guarantee the integrity of data being accessed concurrently by multiple users. For example, a DML lock can prevent multiple customers from buying the last copy of a book available from an online bookseller. DML locks prevent destructive interference of simultaneous conflicting DML or DDL operations.\n\nDML statements automatically acquire locks at both the table level and the row level. In the sections that follow, the acronym in parentheses after each type of lock or lock mode is the abbreviation used in the Locks Monitor of Oracle Enterprise Manager. Enterprise Manager might display \"TM\" for any table lock, rather than indicate the mode of table lock (such as RS or SRX).\n\nThe types of row and table locks are summarized here. For a more complete discussion of the types of row and table locks, see *Oracle Database Concepts*.\n\n**Row Locks (TX)** A **row lock**, also called a **TX lock**, is a lock on a single row of a table. A transaction acquires a row lock for each row modified by one of the following statements: `INSERT`, `UPDATE`, `DELETE`, `MERGE`, and `SELECT ... FOR UPDATE`. The row lock exists until the transaction commits or rolls back.\n\nWhen a transaction obtains a row lock for a row, the transaction also acquires a table lock for the table in which the row resides. The table lock prevents conflicting DDL operations that would override data changes in a current transaction.\n\n**Table Locks (TM)** A transaction automatically acquires a table lock (**TM lock**) when a table is modified with the following statements: `INSERT`, `UPDATE`, `DELETE`, `MERGE`, and `SELECT ... FOR UPDATE`. These DML operations require table locks to reserve DML access to the table on behalf of a transaction and to prevent DDL operations that\n\nwould conflict with the transaction. You can explicitly obtain a table lock using the\nLOCK TABLE statement, as described in \"Manual Data Locking\" on page B-5.\n\nA table lock can be held in any of the following modes:\n\n- A **row share lock (RS)**, also called a **subshare table lock (SS)**, indicates that the\n transaction holding the lock on the table has locked rows in the table and intends\n to update them. An SS lock is the least restrictive mode of table lock, offering the\n highest degree of concurrency for a table.\n\n- A **row exclusive lock (RX)**, also called a **subexclusive table lock (SX)**, indicates\n that the transaction holding the lock has updated table rows or issued SELECT ... FOR UPDATE. An SX lock allows other transactions to query, insert, update, delete,\n or lock rows concurrently in the same table. Therefore, SX locks allow multiple\n transactions to obtain simultaneous SX and SS locks for the same table.\n\n- A **share table lock (S)** held by one transaction allows other transactions to query\n the table (without using SELECT ... FOR UPDATE) but allows updates only if a\n single transaction holds the share table lock. Multiple transactions may hold a\n share table lock concurrently, so holding this lock is not sufficient to ensure that a\n transaction can modify the table.\n\n- A **share row exclusive table lock (SRX)**, also called a **share-subexclusive table\n lock (SSX)**, is more restrictive than a share table lock. Only one transaction at a\n time can acquire an SSX lock on a given table. An SSX lock held by a transaction\n allows other transactions to query the table (except for SELECT ... FOR UPDATE)\n but not to update the table.\n\n- An **exclusive table lock (X)** is the most restrictive mode of table lock, allowing the\n transaction that holds the lock exclusive write access to the table. Only one\n transaction can obtain an X lock for a table.\n\n**See Also:** \"Manual Data Locking\" on page B-5\n\n### Locks in DML Operations\n\nOracle Database automatically obtains row-level and table-level locks on behalf of\nDML operations. The type of operation determines the locking behavior. Table B–1\nsummarizes the information in this section.\n\n---\n\n**Note:** The implicit SX locks shown for the DML statements in\nTable B–1 can sometimes be exclusive (X) locks for a short time owing\nto side effects from constraints.\n\n---\n\n**Table B–1 Summary of Locks Obtained by DML Statements**\n\n| SQL Statement | Row Locks | Table Lock Mode | RS | RX | S | SRX | X |\n|------------------------|-----------|-----------------|----|----|----|-----|----|\n| SELECT ... FROM table...| — | none | Y | Y | Y | Y | Y |\n| INSERT INTO table... | Yes | SX | Y | Y | N | N | N |\n| UPDATE table... | Yes | SX | Y¹ | Y¹ | N | N | N |\n\n### Locks When Rows Are Queried\n\nA query can be explicit, as in the `SELECT` statement, or implicit, as in most `INSERT`, `MERGE`, `UPDATE`, and `DELETE` statements. The only DML statement that does not necessarily include a query component is an `INSERT` statement with a `VALUES` clause. Because queries only read data, they are the SQL statements least likely to interfere with other SQL statements.\n\nThe following characteristics apply to a query *without* the `FOR UPDATE` clause:\n\n- The query acquires no data locks. Therefore, other transactions can query and update a table being queried, including the specific rows being queried. Because queries without the `FOR UPDATE` clause do not acquire any data locks to block other operations, such queries are often referred to as **nonblocking queries**.\n\n- The query does not have to wait for any data locks to be released. Therefore, the query can always proceed. An exception to this rule is that queries may have to wait for data locks in some very specific cases of pending distributed transactions.\n\n### Locks When Rows Are Modified\n\nSome databases use a lock manager to maintain a list of locks in memory. Oracle Database, in contrast, stores lock information in the data block that contains the locked row. Each row lock affects only a single row.\n\nOracle Database uses a queuing mechanism for acquisition of row locks. If a transaction requires a row lock, and if the row is not already locked, then the transaction acquires a lock in the row’s data block. The transaction itself has an entry in the **interested transaction list (ITL)** section of the block header. Each row modified by this transaction points to a copy of the transaction ID stored in the ITL. Thus, 100 rows in the same block modified by a single transaction require 100 row locks, but all 100 rows reference a single transaction ID.\n\nWhen a transaction ends, the transaction ID remains in the ITL section of the data block header. If a new transaction wants to modify a row, then it uses the transaction ID to determine whether the lock is active. If the lock is active, then the session of the new transaction asks to be notified when the lock is released; otherwise, the new transaction acquires the lock.\n\nThe characteristics of INSERT, UPDATE, DELETE, and SELECT ... FOR UPDATE statements are as follows:\n\n- A transaction containing a DML statement acquires exclusive row locks on the rows modified by the statement. Therefore, other transactions cannot update or delete the locked rows until the locking transaction either commits or rolls back.\n\n- In addition to these row locks, a transaction containing a DML statement that modifies data also requires at least a subexclusive table lock (SX) on the table that contains the affected rows. If the transaction already holds an S, SRX, or X table lock for the table, which are more restrictive than an SX lock, then the SX lock is not needed and is not acquired. If the containing transaction already holds only an SS lock, however, then Oracle Database automatically converts the SS lock to an SX lock.\n\n- A transaction that contains a DML statement does not require row locks on any rows selected by a subquery or an implicit query.\n\nIn the following sample UPDATE statement, the SELECT statement in parentheses is a subquery, whereas the WHERE a > 5 clause is an implicit query:\n\n```\nUPDATE t SET x = ( SELECT y FROM t2 WHERE t2.z = t.z ) WHERE a > 5;\n```\n\nA subquery or implicit query inside a DML statement is guaranteed to be consistent as of the start of the query and does not see the effects of the DML statement of which it forms a part.\n\n- A query in a transaction can see the changes made by previous DML statements in the same transaction, but not the uncommitted changes of other transactions.\n\n**See Also:** *Oracle Database Concepts* for information on locks in foreign keys\n\n### Automatic Locks in DDL Operations\n\nA **data dictionary (DDL) lock** protects the definition of a schema object while it is acted upon or referred to by an ongoing DDL operation. For example, when a user creates a procedure, Oracle Database automatically acquires DDL locks for all schema objects referenced in the procedure definition. The DDL locks prevent these objects from being altered or dropped before procedure compilation is complete.\n\nOracle Database acquires a DDL lock automatically on behalf of any DDL transaction requiring it. Users cannot explicitly request DDL locks. Only individual schema objects that are modified or referenced are locked during DDL operations. The whole data dictionary is never locked.\n\nDDL operations also acquire DML locks on the schema object to be modified.\n\n### Exclusive DDL Locks\n\nAn **exclusive DDL lock** prevents other session from obtaining a DDL or DML lock. Most DDL operations require exclusive DDL locks to prevent destructive interference with other DDL operations that might modify or reference the same schema object. For example, a `DROP TABLE` operation is not allowed to drop a table while an `ALTER TABLE` operation is adding a column to it, and vice versa. However, a query against the table is not blocked.\n\nExclusive DDL locks last for the duration of DDL statement execution and automatic commit. During the acquisition of an exclusive DDL lock, if another DDL lock is\n\nalready held on the schema object by another operation, then the acquisition waits until the older DDL lock is released and then proceeds.\n\n**Share DDL Locks**\n\nA **share DDL lock** for a resource prevents destructive interference with conflicting DDL operations, but allows data concurrency for similar DDL operations.\n\nFor example, when a `CREATE PROCEDURE` statement is run, the containing transaction acquires share DDL locks for all referenced tables. Other transactions can concurrently create procedures that reference the same tables and acquire concurrent share DDL locks on the same tables, but no transaction can acquire an exclusive DDL lock on any referenced table.\n\nA share DDL lock lasts for the duration of DDL statement execution and automatic commit. Thus, a transaction holding a share DDL lock is guaranteed that the definition of the referenced schema object is constant for the duration of the transaction.\n\n**Breakable Parse Locks**\n\nA **parse lock** is held by a SQL statement or PL/SQL program unit for each schema object that it references. Parse locks are acquired so that the associated shared SQL area can be invalidated if a referenced object is altered or dropped. A parse lock is called a **breakable parse lock** because it does not disallow any DDL operation and can be broken to allow conflicting DDL operations.\n\nA **parse lock** is acquired in the shared pool during the parse phase of SQL statement execution. The lock is held as long as the shared SQL area for that statement remains in the shared pool.\n\n**Manual Data Locking**\n\nOracle Database always performs locking automatically to ensure data concurrency, data integrity, and statement-level read consistency. However, you can override the Oracle default locking mechanisms. This can be useful in situations such as the following:\n\n- When your application requires consistent data for the duration of the transaction, not reflecting changes by other transactions, you can achieve transaction-level read consistency by using explicit locking, read-only transactions, serializable transactions, or by overriding default locking.\n\n- When your application requires that a transaction have exclusive access to a resource so that the transaction does not have to wait for other transactions to complete, you can explicitly lock the data for the duration of the transaction.\n\nYou can override automatic locking at two levels:\n\n- **Transaction.** You can override transaction-level locking with the following SQL statements:\n\n - `SET TRANSACTION ISOLATION LEVEL`\n - `LOCK TABLE`\n - `SELECT ... FOR UPDATE`\n\nLocks acquired by these statements are released after the transaction commits or rolls back.\n\nSession. A session can set the required transaction isolate level with an ALTER SESSION SET ISOLATION LEVEL statement.\n\nNote: When overriding Oracle default locking, the database administrator or application developer should ensure that data integrity is guaranteed, data concurrency is acceptable, and deadlocks are not possible or, if possible, are appropriately handled. For more information on these criteria, see Oracle Database Concepts.\n\nThis appendix discusses Oracle's conformance with the SQL:2008 standards. The mandatory portion of SQL:2008 is known as Core SQL:2008 and is found in SQL:2008 Part 2 (Foundation) and Part 11 (Schemata). The Foundation features are analyzed in Annex F of Part 2 in the table \"Feature taxonomy and definition for mandatory features of SQL/Foundation\". The Schemata features are analyzed in Annex E of Part 11 in the table \"Feature taxonomy and definition for mandatory features of SQL/Schemata\".\n\nThis appendix declares Oracle's conformance to the SQL standards established by the American National Standards Institute (ANSI) and the International Organization for Standardization (ISO). (The ANSI and ISO SQL standards are identical.)\n\nThis appendix contains the following sections:\n\n- ANSI Standards\n- ISO Standards\n- Oracle Compliance To Core SQL:2008\n- Oracle Support for Optional Features of SQL/Foundation:2008\n- Oracle Compliance with SQL/CLI:2008\n- Oracle Compliance with SQL/PSM:2008\n- Oracle Compliance with SQL/MED:2008\n- Oracle Compliance with SQL/OLB:2008\n- Oracle Compliance with SQL/JRT:2008\n- Oracle Compliance with SQL/XML:2008\n- Oracle Compliance with FIPS 127-2\n- Oracle Extensions to Standard SQL\n- Oracle Compliance with Older Standards\n- Character Set Support\n\n**ANSI Standards**\n\nThe following documents of the American National Standards Institute (ANSI) relate to SQL:\n\n- ANSI/ISO/IEC 9075-1:2008, Information technology—Database languages—SQL—Part 1: Framework (SQL/Framework)\n\nANSI/ISO/IEC 9075-2:2008, Information technology—Database languages—SQL—Part 2: Foundation (SQL/Foundation)\n\nANSI/ISO/IEC 9075-3:2008, Information technology—Database languages—SQL—Part 3: Call-Level Interface (SQL/CLI)\n\nANSI/ISO/IEC 9075-4:2008, Information technology—Database languages—SQL—Part 4: Persistent Stored Modules (SQL/PSM)\n\nANSI/ISO/IEC 9075-9:2008, Information technology—Database languages—SQL—Part 9: Management of External Data (SQL/MED)\n\nANSI/ISO/IEC 9075-10:2008, Information technology—Database languages—SQL—Part 10: Object Language Bindings (SQL/OLB)\n\nANSI/ISO/IEC 9075-11:2008, Information technology—Database languages—SQL—Part 11: Information and Definition Schemas (SQL/Schemata)\n\nANSI/ISO/IEC 9075-13:2008, Information technology—Database languages—SQL—Part 13: SQL Routines and Types using the Java Programming Language (SQL/JRT)\n\nANSI/ISO/IEC 9075-14:2008, Information technology—Database languages—SQL—Part 14: XML-Related Specifications (SQL/XML)\n\nThese standards are identical to the corresponding ISO standards listed in the next section.\n\nYou can obtain a copy of ANSI standards from this address:\n\nAmerican National Standards Institute\n25 West 43rd Street, fourth floor\nNew York, NY 10036 USA\nTelephone: +1.212.642.4900\nFax: +1.212.398.0023\nWeb site: http://www.ansi.org/\n\nYou can also obtain the standards from their Web site:\n\nhttp://webstore.ansi.org/default.aspx\n\nA subset of ANSI standards, including the SQL standard, are INCITS standards. You can obtain these from the InterNational Committee for Information Technology Standards (INCITS) at:\n\nhttp://www.incits.org/\n\n**ISO Standards**\n\nThe following documents of the International Organization for Standardization (ISO) relate to SQL:\n\n- ISO/IEC 9075-1:2008, Information technology—Database languages—SQL—Part 1: Framework (SQL/Framework)\n- ISO/IEC 9075-2:2008, Information technology—Database languages—SQL—Part 2: Foundation (SQL/Foundation)\n- ISO/IEC 9075-3:2008, Information technology—Database languages—SQL—Part 3: Call-Level Interface (SQL/CLI)\n- ISO/IEC 9075-4:2008, Information technology—Database languages—SQL—Part 4: Persistent Stored Modules (SQL/PSM)\n\nISO/IEC 9075-9:2008, Information technology—Database languages—SQL—Part 9: Management of External Data (SQL/MED)\n\nISO/IEC 9075-10:2008, Information technology—Database languages—SQL—Part 10: Object Language Bindings (SQL/OLB)\n\nISO/IEC 9075-11:2008, Information technology—Database languages—SQL—Part 11: Information and Definition Schemas (SQL/Schemata)\n\nISO/IEC 9075-13:2008, Information technology—Database languages—SQL—Part 13: SQL Routines and Types using the Java Programming Language (SQL/JRT)\n\nISO/IEC 9075-14:2008, Information technology—Database languages—SQL—Part 14: XML-Related Specifications (SQL/XML)\n\nYou can obtain a copy of ISO standards from this address:\n\nInternational Organization for Standardization\n1, ch. de la Voie-Creuse\nCase postale 56\nCH-1211, Geneva 20, Switzerland\nPhone: +41.22.749.0111\nFax: +41.22.733.3430\nWeb site: http://www.iso.org/\n\nor from their Web store:\n\nhttp://www.iso.org/iso/store.htm\n\nOracle Compliance To Core SQL:2008\n\nThe ANSI and ISO SQL standards require conformance claims to state the type of conformance and the implemented facilities. The minimum claim of conformance is called Core SQL:2008 and is defined in Part 2, SQL/Foundation, and Part 11, SQL/Schemata, of the standard. The following products provide full or partial conformance with Core SQL:2008 as described in the tables that follow:\n\n- Oracle Database server\n- Pro*C/C++, release 9.2.0\n- Pro*COBOL, release 9.2.0\n- Pro*Fortran, release 1.8.77\n- SQL Module for Ada (Mod*Ada), release 9.2.0\n- Pro*COBOL 1.8, release 1.8.77\n- Pro*PL/I, release 1.6.28\n- OTT (Oracle Type Translator)\n\nThe SQL standards conformance features can be used either as a guide to portability, or as a guide to functionality. From the standpoint of portability, the user is interested in conformance to both the precise syntax and semantics of the standard feature. From the standpoint of functionality, the user is less concerned about the precise syntax and more concerned with issues of semantics. The tables in this appendix use the following terms regarding support for standard syntax and semantics:\n\n- Full Support: The feature is supported with standard syntax and semantics.\n- Partial Support: Some, but not all, of the standard syntax is supported; whatever is supported has standard semantics.\n\nEnhanced Supported: The standard semantics is supported, but gives functionality that differs from the standard by enhancing it.\n\nEquivalent Support: The standard semantics is supported using non-standard syntax.\n\nSimilar Support: Neither the standard’s syntax nor semantics are supported precisely, but similar functionality is provided.\n\nOracle's support for the features of Core SQL:2008 is listed in Table C–1:\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| E011, Numeric data types | Oracle fully supports this feature. |\n| E021, Character data types | Oracle fully supports these subfeatures: \n - E021-01, CHARACTER data type \n - E021-07, Character concatenation \n - E021-08, UPPER and LOWER functions \n - E021-09, TRIM function \n - E021-10, Implicit casting among character data types \nOracle partially supports these subfeatures: \n - E021-02, CHARACTER VARYING data type (Oracle does not distinguish a zero-length VARCHAR string from NULL) \n - E021-03, Character literals (Oracle regards the zero-length literal '' as being null) \n - E021-12, Character comparison (Oracle’s rules for padding the shorter of two strings to be compared differs from the standard) \nOracle has equivalent functionality for these subfeatures: \n - E021-04, CHARACTER_LENGTH function: use LENGTH function instead \n - E021-05, OCTET_LENGTH function: use LENGTHB function instead \n - E021-06, SUBSTRING function: use SUBSTR function instead \n - E021-11, POSITION function: use INSTR function instead |\n| E031, Identifiers | Oracle supports this feature, with the following exceptions: \n - Oracle does not support the escape sequence to permit a double quote within a quoted identifier \n - A non-quoted identifier may not be equivalent to an Oracle reserved word (the list of Oracle reserved words differs from the standard’s list) \n - A column name may not be ROWID, even as a quoted identifier \nOracle extends this feature as follows: \n - An identifier may be up to 30 characters long \n - A non-quoted identifier may have dollar sign ($) or pound sign (#) |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| E051, Basic query specification | Oracle fully supports the following subfeatures: \n - E051-01, SELECT DISTINCT \n - E051-02, GROUP BY clause \n - E051-04, GROUP BY can contain columns not in SELECT list \n - E051-05, SELECT list items can be renamed \n - E051-06, HAVING clause \n - E051-07, Qualified * in SELECT list \nOracle partially supports the following subfeatures: \n - E051-08, Correlation names in FROM clause (Oracle supports correlation names, but not the optional AS keyword) \nOracle has equivalent functionality for the following subfeature: \n - E051-09, Rename columns in the FROM clause (column names can be renamed in a subquery in the FROM clause) |\n| E061, Basic predicates and search conditions | Oracle fully supports this feature, except that Oracle comparison of character strings differs from the standard as follows: In the standard, two character strings of unequal length are compared by either padding the shorter string with spaces or a fictitious character that is less than all actual characters. The decision on padding is made on the basis of the character set. In Oracle, the decision is based on whether the comparands are of fixed or varying length. |\n| E071, Basic query expressions | Oracle fully supports the following subfeatures: \n - E071-01, UNION DISTINCT table operator \n - E071-02, UNION ALL table operator \n - E071-05, Columns combined by table operators need not have exactly the same type \n - E071-06, table operators in subqueries \nOracle has equivalent functionality for the following subfeature: \n - E071-03, EXCEPT DISTINCT table operator: Use MINUS instead of EXCEPT DISTINCT |\n| E081, Basic privileges | Oracle fully supports all subfeatures of this feature, except E081-09, USAGE privileges. In the standard, the USAGE privilege permits the user to use domains, collations, character sets, transliterations, user-defined types and sequence generators. Oracle does not support domains or transliterations. No privileges are required to access collations and character sets. The Oracle privilege to use a user-defined type is EXECUTE. The Oracle privilege to use a sequence type is SELECT. |\n| E091, Set functions | Oracle fully supports this feature. |\n| E101, Basic data manipulation | Oracle fully supports this feature. |\n| E111, Single row SELECT statement | Oracle fully supports this feature. |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| E121, Basic cursor support | Oracle fully supports the following subfeatures: \n - E121-02, ORDER BY columns need not be in SELECT list \n - E121-03, Value expressions in ORDER BY clause \n - E121-04, OPEN statement \n - E121-06, Positioned UPDATE statement \n - E121-07, Positioned DELETE statement \n - E121-08, CLOSE statement \nOracle provides partial support for the following subfeatures: \n - E121-01, DECLARE CURSOR - fully supported, except for the FOR READ ONLY syntax \n - E121-10 FETCH statement, implicit NEXT - fully supported, except for the noise word FROM \nOracle provides enhanced support for the following subfeature: \n - E121-17, WITH HOLD cursors (in the standard, a cursor is not held through a ROLLBACK, but Oracle does hold through ROLLBACK) |\n| E131, Null value support | Oracle fully supports this feature, with this exception: In Oracle, a null of character type is indistinguishable from a zero-length character string. |\n| E141, Basic integrity constraints | Oracle fully supports this feature. |\n| E151, Transaction support | Oracle fully supports this feature. |\n| E152, Basic SET TRANSACTION statement | Oracle fully supports this feature. |\n| E153, Updatable queries with subqueries | Oracle fully supports this feature. |\n| E161, SQL comments using leading double minus | Oracle fully supports this feature. |\n| E171, SQLSTATE support | Oracle fully supports this feature. |\n| E182, Module language | Oracle supports this feature for Ada only. |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| F021, Basic information schema | Oracle does not have any of the views in this feature. However, Oracle makes the same information available in other metadata views: \n- Instead of TABLES, use ALL_TABLES. \n- Instead of COLUMNS, use ALL_TAB_COLUMNS. \n- Instead of VIEWS, use ALL_VIEWS. \n\nHowever, Oracle’s ALL_VIEWS does not display whether a user view was defined WITH CHECK OPTION or if it is updatable. To see whether a view has WITH CHECK OPTION, use ALL_CONSTRAINTS, with TABLE_NAME equal to the view name and look for CONSTRAINT_TYPE equal to ‘V’. \n- Instead of TABLE_CONSTRAINTS, REFERENTIAL_CONSTRAINTS, and CHECK_CONSTRAINTS, use ALL_CONSTRAINTS. \n\nHowever, Oracle’s ALL_CONSTRAINTS does not display whether a constraint is deferrable or initially deferred. |\n| F031, Basic schema manipulation | Oracle fully supports these subfeatures: \n- F031-01, CREATE TABLE statement to create persistent base tables \n- F031-02, CREATE VIEW statement \n- F031-03, GRANT statement \n\nOracle partially supports this subfeature: \n- F031-04, ALTER TABLE statement: ADD COLUMN clause (Oracle does not support the optional keyword COLUMN in this syntax. Also, Oracle requires the column definition to be enclosed in parentheses, unlike the standard.) \n\nOracle does not support these subfeatures (because Oracle does not support the keyword RESTRICT): \n- F031-13, DROP TABLE statement: RESTRICT clause \n- F031-16, DROP VIEW statement: RESTRICT clause \n- F031-19, REVOKE statement: RESTRICT clause \n\n(Oracle DROP commands enhance the standard by invalidating dependent objects, so that they can be subsequently revalidated without user action, rather than either cascading all drops to dependent objects or prohibiting a drop if there is a dependent object.) |\n| F041, Basic joined table | Oracle fully supports this feature. |\n| F051, Basic date and time | Oracle fully supports this feature, except the following subfeatures are not supported: \n- F051-02, TIME data type \n- F051-07, LOCALTIME |\n| F081, UNION and EXCEPT in views | Oracle fully supports UNION in views. The equivalent in Oracle of the standard’s EXCEPT is called MINUS, which is fully supported in views. |\n| F131, Grouped operations | Oracle fully supports this feature. |\n| F181, Multiple module support | Oracle fully supports this feature. |\n| F201, CAST function | Oracle fully supports this feature. |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| F221, Explicit defaults | Oracle fully supports this feature. |\n| F261, CASE expressions | Oracle fully supports this feature. |\n| F311, Schema definition statement | Oracle fully supports this feature. |\n| F471, Scalar subquery values | Oracle fully supports this feature. |\n| F481, Expanded null predicate | Oracle fully supports this feature. |\n| F501, Feature and conformance views | Oracle does not support this feature. |\n| F812, Basic flagging | Oracle has a flagger, but it flags SQL-92 compliance rather than SQL:2008 compliance. |\n| S011, Distinct types | Distinct types are strongly typed scalar types. A distinct type can be emulated in Oracle using an object type with only one attribute. The standard’s Information Schema view called USER_DEFINED_TYPES is equivalent to Oracle’s metadata view ALL_TYPES. |\n| T321, Basic SQL-invoked routines | Oracle fully supports these subfeatures: \n - T321-03, function invocation \n - T321-04, CALL statement \nOracle supports these subfeatures with syntactic differences: \n - T321-01, user-defined functions with no overloading \n - T321-02, user-defined procedures with no overloading \nThe Oracle syntax for CREATE FUNCTION and CREATE PROCEDURE differs from the standard as follows: \n - In the standard, the mode of a parameter (IN, OUT, or INOUT) comes before the parameter name, whereas in Oracle it comes after the parameter name. \n - The standard uses INOUT, whereas Oracle uses IN OUT. \n - Oracle requires either IS or AS after the return type and before the definition of the routine body, while the standard lacks these keywords. \n - If the routine body is in C (for example), then the standard uses the keywords LANGUAGE C EXTERNAL NAME to name the routine, whereas Oracle uses LANGUAGE C NAME. \n - If the routine body is in SQL, then Oracle uses its proprietary procedural extension called PL/SQL. \nOracle supports the following subfeature in PL/SQL but not in Oracle SQL: \n - T321-05, RETURN statement \nOracle provides equivalent functionality for the following subfeatures: \n - T321-06, ROUTINES view: Use the ALL PROCEDURES metadata view. \n - T321-07, PARAMETERS view: Use the ALL_ARGUMENTS and ALL_METHOD_PARAMS metadata views. |\n\nTable C–1 (Cont.) Oracle Support of Core SQL:2008 Features\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| T631, IN predicate with one list element | Oracle fully supports this feature. |\n\nOracle Support for Optional Features of SQL/Foundation:2008\n\nOracle’s support for optional features of SQL/Foundation:2008 is listed in Table C–2:\n\nTable C–2 Oracle Support for Optional Features of SQL/Foundation:2008\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| B012, Embedded C | Oracle fully supports this feature. |\n| B013, Embedded COBOL | Oracle fully supports this feature. |\n| B014, Embedded Fortran | Oracle fully supports this feature. |\n| B021, Direct SQL | Oracle fully supports this feature, as SQL*Plus. |\n| B031, Basic dynamic SQL | Oracle supports dynamic SQL in two styles, documented in the embedded language manuals as \"Oracle dynamic SQL\" and \"ANSI dynamic SQL.\" ANSI dynamic SQL is an implementation of the standard, with the following restrictions:\n - Oracle supports a subset of the descriptor items.\n - For <input using clause>, Oracle only supports <using input descriptor>.\n - For <output using clause>, Oracle only supports <into descriptor>.\n - Dynamic parameters are indicated by a colon followed by an identifier rather than a question mark.\n\nOracle dynamic SQL is similar to standard dynamic SQL, with the following modifications:\n - Parameters are indicated by a colon followed by an identifier, instead of a question mark.\n - Oracle's DESCRIBE SELECT LIST FOR statement replaces the standard's DESCRIBE OUTPUT.\n - Oracle provides DECLARE STATEMENT if you want to declare a cursor using a dynamic SQL statement physically prior to the PREPARE statement that prepares the dynamic SQL statement. |\n| B032, Extended dynamic SQL | In ANSI dynamic SQL, Oracle only implements the ability to declare global statements and global cursors from this feature; the rest of the feature is not supported.\n\nIn Oracle dynamic SQL, Oracle's DESCRIBE BIND VARIABLES is equivalent to the standard's DESCRIBE INPUT; the rest of this feature is not supported. |\n| B111, Module language Ada | Oracle fully supports this feature. |\n| B122, Routine language C | Oracle supports external routines written in C, though Oracle does not support the standard syntax for creating such routines. |\n| B128, Routine language SQL | Oracle supports routines written in PL/SQL, which is Oracle's equivalent to the standard procedural language SQL/PSM. |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| F032, CASCADE drop behavior | In Oracle, a DROP command invalidates all of the dropped object's dependent objects. Invalidated objects are effectively unusable until the dropped object is redefined in such a way to allow successful recompilation of the invalidated object. |\n| F033, ALTER TABLE statement: DROP COLUMN clause | Oracle provides a DROP COLUMN clause, but without the RESTRICT or CASCADE options found in the standard. |\n| F034, Extended REVOKE statement | Oracle supports the following parts of this feature: \n- F034-01, REVOKE statement performed by other than the owner of a schema object \n- F034-03, REVOKE statement to revoke a privilege that the grantee has WITH GRANT OPTION \nOracle provides equivalent functionality for the following parts of this feature: \n- CASCADE: In Oracle, a REVOKE invalidates all dependent objects, which become effectively unusable until the metadata is changed through subsequent CREATE and GRANT commands enabling the invalidated object to be successfully recompiled. |\n| F052, Intervals and datetime arithmetic | Oracle only supports the INTERVAL YEAR TO MONTH and INTERVAL DAY TO SECOND data types. |\n| F111, Isolations levels other than SERIALIZABLE | In addition to SERIALIZABLE, Oracle supports the READ COMMITTED isolation level. |\n| F121, Basic diagnostics management | Much of the functionality of this feature is provided through the SQLCA in embedded languages. |\n| F191, Referential delete actions | Oracle supports ON DELETE CASCADE and ON DELETE SET NULL. |\n| F200, TRUNCATE TABLE | Oracle fully supports this feature, and extends it by permitting truncation of a table that references itself in a referential integrity constraint. |\n| F231, Privilege tables | Oracle makes this information available in the following metadata views: \n- Instead of TABLE_PRIVILEGES, use ALL_TAB_PRIVS. \n- Instead of COLUMN_PRIVILEGES, use ALL_COL_PRIVS. \n- Oracle does not support USAGE privileges so there is no equivalent to USAGE_PRIVILEGES. |\n| F281, LIKE enhancements | Oracle fully supports this feature. |\n| F291, UNIQUE predicate | The IS A SET condition may be used to test whether a multiset is a set; that is, each row is unique. Thus, the equivalent of UNIQUE <table subquery> is CAST (<table subquery> AS MULTISET) IS A SET |\n| F302, INTERSECT table operator | Oracle supports INTERSECT but not INTERSECT ALL. Syntactically, Oracle differs from the standard in that UNION, INTERSECT, and MINUS have the same precedence. |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| F312, MERGE statement | The Oracle MERGE statement is almost the same as the standard, with these exceptions: \n - Oracle does not support the optional AS keyword before a table alias. \n - Oracle does not support the ability to rename columns of the table specified in the USING clause with a parenthesized list of column names following the table alias. \n - Oracle does not support the <override clause>. |\n| F341, Usage tables | Oracle makes this information available in the views ALL_DEPENDENCIES, DBA_DEPENDENCIES, and USER_DEPENDENCIES. |\n| F381, Extended schema manipulation | Oracle fully supports the following element of this feature: \n - Oracle supports the standard syntax to add a table constraint using ALTER TABLE. \nOracle partially supports the following element of this feature: \n - Oracle supports the standard syntax to drop a table constraint, except that Oracle does not support RESTRICT. \nOracle provides equivalent functionality for the following element of this feature: \n - To alter the default value of a column, use the MODIFY option of ALTER TABLE. \nOracle does not support the following parts of this feature: \n - DROP SCHEMA statement \n - ALTER ROUTINE statement |\n| F382, Alter column data type | Oracle supports this functionality, though with non-standard syntax. |\n| F391, Long identifiers | Oracle supports identifiers up to 30 characters in length. |\n| F393, Unicode escapes in literals | The Oracle UNISTR function supports numeric escape sequences for all Unicode characters. |\n| F394, Optional normal form specification | This feature adds the keywords NFC, NFD, NFKC, and NKD to the NORMALIZE function and the IS NORMAL predicate. Without these keywords, NFC is the default (see Feature T061, UCS support). Oracle supports all four normalization forms, with nonstandard syntax, as follows: \n - For NFC, use COMPOSE \n - For NFD, use DECOMPOSE with the CANONICAL option \n - For NFKD, use DECOMPOSE with the COMPATIBILITY option \n - For NFKC, use DECOMPOSE with the CANONICAL option followed by COMPOSE \nOracle does not support the IS NORMAL predicate. |\n| F401, Extended joined table | Oracle supports FULL outer joins, CROSS joins, and NATURAL joins. |\n| F402, Named column joins for LOBs, arrays and multisets | Oracle supports named column joins for columns whose declared type is nested table. Oracle does not support named column joins for LOBs or arrays. |\n| F403, Partitioned join tables | Oracle supports this feature, except with FULL outer joins. |\n\n| Feature ID, Feature | Support |\n|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| F411, Time zone specification | Oracle fully supports TIMESTAMP WITH TIME ZONE, but does not support TIME WITH TIME ZONE. |\n| F421, National character | Oracle fully supports this feature. |\n| F441, Extended set function support | Oracle supports the following parts of this feature: \n - The ability in the WHERE clause to reference a column that is defined using an aggregate, either in a view or an inline view \n - COUNT without DISTINCT of an expression \n - Aggregates that reference columns that are outer references with respect to the aggregating query |\n| F442, Mixed column references in set functions | Oracle fully supports this feature. |\n| F461, Named character sets | Oracle supports many character sets with Oracle-defined names. Oracle does not support any other aspect of this feature. |\n| F491, Constraint management | Oracle fully supports this feature. |\n| F531, Temporary tables | Oracle supports GLOBAL TEMPORARY tables. |\n| F555, Enhanced seconds precision | Oracle provides enhanced support for this feature, supporting up to 9 places after the decimal point. |\n| F561, Full value expressions | Oracle fully supports this feature. |\n| F571, Truth value tests | Oracle's LNNVL function is equivalent to the standard's IS NOT TRUE predicate. |\n| F591, Derived tables | Oracle supports <derived table>, with the exception of: \n - Oracle does not support the optional AS keyword before a table alias. \n - Oracle does not support <derived column list>. |\n| F641, Row and table constructors | In Oracle, a row constructor may be used in an equality or inequality comparison with another row constructor or with a subquery. Oracle does not support anything else in this feature. |\n| F690, Collation support | Oracle's NLSSORT function may be used to change the collation of character expressions. |\n| F693, SQL-sessions and client module collations | To set a session collation, use ALTER SESSION SET NLS_COMP = 'LINGUISTIC' and also set NLS_SORT to your desired collation. Oracle does not support client module collations. |\n| F695, Translation support | The Oracle CONVERT function can convert between the database character set and the national character set. For other character sets, store the data in the RAW data type and use the PL/SQL package function UTL_RAW.CONVERT. Oracle does not provide the ability to add or drop character set conversions. |\n| F721, Deferrable constraints | Oracle fully supports this feature. |\n| F731, INSERT column privileges | Oracle fully supports this feature. |\n\n| Feature ID, Feature | Support |\n|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| F761, Session management | Oracle provides the following equivalents for elements of this feature: \n - The equivalent to the standard’s `SET SESSION CHARACTERISTICS AS TRANSACTION SERIALIZABLE` is `ALTER SESSION SET ISOLATION_LEVEL = SERIALIZABLE`. \n - The equivalent to the standard’s `SET SCHEMA` is `ALTER SESSION SET CURRENT_SCHEMA`. \n - The equivalent to the standard’s `SET COLLATION` is `ALTER SESSION SET NLS_SORT`. |\n| F771, Connection management | Oracle’s `CONNECT` statement provides the same functionality as the standard’s `CONNECT` statement, though with different syntax. Instead of using the standard’s `SET CONNECTION`, Oracle provides the `AT` clause to indicate which connection a SQL statement should be performed on. Oracle embedded languages let you disconnect from a connection by using the `RELEASE` option of either `COMMIT` or `ROLLBACK`. |\n| F781, Self-referencing operations | Oracle fully supports this feature. |\n| F801, Full set function | Oracle fully supports this feature. |\n| F831, Full cursor update | Oracle supports the combination of `FOR UPDATE` and `ORDER BY` clauses in a query. |\n| F841, LIKE_REGEX predicate | Oracle’s equivalent is `REGEXP_LIKE`. Oracle’s pattern syntax lacks some of the features of the standard’s. Oracle’s match parameter has the same capabilities as the standard’s, though with a few spelling differences. |\n| F842, OCCURRENCES_REGEX function | Oracle’s equivalent is `REGEXP_COUNT`. Oracle’s pattern syntax lacks some of the features of the standard’s. Oracle’s match parameter has the same capabilities as the standard’s, though with a few spelling differences. |\n| F843, POSITION_REGEX function | Oracle’s equivalent is `REGEXP_INSTR`. Oracle’s pattern syntax lacks some of the features of the standard’s. Oracle’s match parameter has the same capabilities as the standard’s, though with a few spelling differences. |\n| F844, SUBSTRING_REGEX function | Oracle’s equivalent is `REGEXP_SUBSTR`. Oracle’s pattern syntax lacks some of the features of the standard’s. Oracle’s match parameter has the same capabilities as the standard’s, though with a few spelling differences. |\n| F845, TRANSLATE_REGEX function | Oracle’s equivalent is `REGEXP_REPLACE`. Oracle’s pattern syntax lacks some of the features of the standard’s. Oracle’s match parameter has the same capabilities as the standard’s, though with a few spelling differences. |\n| S023, Basic structured types | Oracle’s object types are equivalent to structured types in the standard. |\n\n| Feature ID, Feature | Support |\n|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| S024, Enhanced structured types | Oracle’s syntax is non-standard, but provides equivalents for the following: \n - NOT INSTANTIABLE \n - STATIC methods \n - RELATIVE, MAP, and STATE orderings. The keyword in Oracle for RELATIVE orderings is ORDER. There is no keyword for STATE orderings (this is the default, if no other ordering is defined). Unlike the standard, Oracle does not support EQUALS ONLY on non-STATE orderings. (See also Feature S251, User-defined orderings.) \n - SELF AS RESULT in the signature of constructor methods |\n| S025, Final structured types | Oracle’s final object types are equivalent to final structured types in the standard. |\n| S026, Self-referencing structured types | In Oracle, an object type OT may have a reference that references OT. |\n| S041, Basic reference types | Oracle’s reference types are equivalent to reference types in the standard. To dereference a reference, dot notation is used, instead of -> as in the standard. |\n| S043, Enhanced reference types | Oracle supports the following elements of this feature: \n - DEREF operator to return the object referenced by a reference \n - SCOPE clause as a constraint on columns of tables or materialized views \n - Adding and dropping the scope of a column \n - References that are either system-generated or derived from the primary key (but not from any other list of columns, nor from a list of attributes of the type) |\n| S051, Create table of type | Oracle’s object tables are equivalent to tables of structured type in the standard. |\n| S081, Subtables | Oracle supports hierarchies of object views, but not of object base tables. To emulate a hierarchy of base tables, create a hierarchy of views on those base tables. |\n| S091, Array types | Oracle VARRAY types are equivalent to array types in the standard. However, Oracle does not support storage of arrays of LOBs. To access a single element of an array using a subscript, you must use PL/SQL. Oracle supports the following aspects of this feature with nonstandard syntax: \n - To construct an instance of varray type, including an empty array, use the varray type constructor. \n - To unnest a varray in the FROM clause, use the TABLE operator. |\n| S092, Arrays of user-defined types | Oracle supports VARRAYs of object types. |\n| S094, Arrays of reference types | Oracle supports VARRAYs of references. |\n| S095, Array constructors by query | Oracle supports this using CAST (MULTISET (SELECT ...) AS varray_type). The ability to order the elements of the array using ORDER BY is not supported. |\n| S097, Array element assignment | In PL/SQL, you can assign to array elements, using syntax that is similar to the standard (SQL/PSM). |\n\n| Feature ID, Feature | Support |\n|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| S111, ONLY in query expressions | Oracle supports the ONLY clause for view hierarchies; Oracle does not support hierarchies of base tables. |\n| S151, Type predicate | Oracle fully supports this feature. |\n| S161, Subtype treatment | Supported, with a minor syntactic difference: The standard requires parentheses around the referenced type's name; Oracle does not support parentheses in this position. |\n| S162, Subtype treatment for references | The standard requires parentheses around the referenced type's name; Oracle does not support parentheses in this position. |\n| S201, SQL-invoked routines on arrays | PL/SQL provides the ability to pass arrays as parameters and return arrays as the result of functions. Procedures and functions written in C may pass arrays and return arrays as the result of functions using the Oracle Type Translator (OTT). |\n| S202, SQL-invoked routines on multisets | A PL/SQL routine may have nested tables as parameters, and may return a nested table. Routines written in C may pass arrays and return arrays as the result of functions using the Oracle Type Translator. |\n| S232, Array locators | Oracle Type Translator supports descriptors for arrays, which achieve the same purpose as locators. |\n| S233, Multiset locators | Oracle supports locators for nested tables. |\n| S241, Transform functions | The Oracle Type Translator provides the same capability as transforms. |\n| S251, User-defined orderings | Oracle’s object type ordering capabilities correspond to the standard’s capabilities as follows: \n - Oracle’s MAP ordering corresponds to the standard’s ORDER FULL BY MAP ordering. \n - Oracle’s ORDER ordering corresponds to the standard’s ORDER FULL BY RELATIVE ordering. \n - If an Oracle object type has neither MAP nor ORDER declared, then this corresponds to EQUALS ONLY BY STATE in the standard. \n - Oracle does not have unordered object types; you can alter the ordering but you cannot drop it. |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| S271, Basic multiset support | Multisets in the standard are supported as nested table types in Oracle. The Oracle nested table data type based on a scalar type ST is equivalent, in standard terminology, to a multiset of rows having a single field of type ST and named `column_value`. The Oracle nested table type based on an object type is equivalent to a multiset of structured type in the standard.\n\nOracle supports the following elements of this feature on nested tables using the same syntax as the standard has for multisets:\n\n- The CARDINALITY function\n- The SET function\n- The MEMBER predicate\n- The IS A SET predicate\n- The COLLECT aggregate\n\nAll other aspects of this feature are supported with non-standard syntax, as follows:\n\n- To create an empty multiset, denoted `MULTISET[]` in the standard, use an empty constructor of the nested table type.\n- To obtain the sole element of a multiset with one element, denoted `ELEMENT (<multiset value expression>)` in the standard, use a scalar subquery to select the single element from the nested table.\n- To construct a multiset by enumeration, use the constructor of the nested table type.\n- To construct a multiset by query, use `CAST` with a multiset argument, casting to the nested table type.\n- To unnest a multiset, use the `TABLE` operator in the `FROM` clause. |\n| S272, Multisets of user-defined types | Oracle's nested table type permits a multiset of structured types. Oracle does not have distinct types, so a multiset of distinct types is not supported. |\n| S274, Multisets of reference types | A nested table type can have one or more columns of reference type. |\n| S275, Advanced multiset support | Oracle supports the following elements of this feature on nested tables using the same syntax as the standard has for multisets:\n\n- The `MULTISET UNION`, `MULTISET INTERSECTION`, and `MULTISET EXCEPT` operators\n- The `SUBMULTISET` predicate\n- `=` and `< >` predicates\n\nOracle does not support the `FUSION` or `INTERSECTION` aggregates. |\n| S281, Nested collection types | Oracle permits nesting of its collection types (varray and nested table). |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| T041, Basic LOB data type support | Oracle supports the following aspects of this feature: \n- The keywords BLOB, CLOB, and NCLOB \n- Concatenation, UPPER, LOWER, and TRIM on CLOBs \nOracle provides equivalent support for the following aspects of this feature: \n- Use INSTR instead of POSITION. \n- Use LENGTH instead of CHAR_LENGTH. \n- Use SUBSTR instead of SUBSTRING. \nOracle does not support the following aspects of this feature: \n- The keywords BINARY LARGE OBJECT, CHARACTER LARGE OBJECT, and NATIONAL CHARACTER LARGE OBJECT as synonyms for BLOB, CLOB, and NCLOB, respectively \n- <binary string literal> \n- The ability to specify an upper bound on the length of a LOB or CLOB \n- Concatenation of BLOBS |\n| T042, Extended LOB support | Oracle fully supports the following element of this feature: \n- TRIM function on a CLOB argument \nOracle provides equivalent functionality for the following elements of this feature: \n- BLOB and CLOB substring, supported using SUBSTR \n- SIMILAR predicate, supported using REGEXPR_LIKE to perform pattern matching with a Perl-like syntax \nThe following elements of this feature are not supported: \n- Comparison predicates with BLOB or CLOB operands \n- CAST with a BLOB or CLOB operand \n- OVERLAY (This may be emulated using SUBSTR and string concatenation.) \n- LIKE predicate with BLOB or CLOB operands |\n| T051, Row types | Oracle object types can be used in place of the standard's row types. |\n| T061, UCS support | Oracle provides equivalent functionality for the following elements of this feature: \n- Oracle supports the keyword CHAR instead of CHARACTERS, and BYTE instead of OCTETS, in a character data type declaration. \n- The Oracle COMPOSE function is equivalent to the standard's NORMALIZE function. \nOracle does not support the IS NORMALIZED predicate. |\n| T071, BIGINT data type | On many implementations, BIGINT refers to a binary integer type with 64 bits, which supports almost 19 decimal digits. The Oracle NUMBER type supports 39 decimal digits. |\n| T111, Updatable joins, unions and columns | Oracle's updatable join views are a subset of the standard's updatable join capabilities. |\n| T121, WITH (excluding RECURSIVE) in query expression | Oracle fully supports this feature. |\n\n| Feature ID, Feature | Support |\n|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| T122, WITH (excluding RECURSIVE) in subquery | Oracle fully supports this feature. |\n| T131, Recursive query | Oracle supports the use of a WITH clause element that references itself, but without the RECURSIVE keyword. Alternatively, Oracle’s START WITH and CONNECT BY clauses can be used to perform many recursive queries. |\n| T132, Recursive query in subquery | Oracle supports the use of a WITH clause element that references itself, but without the RECURSIVE keyword. Alternatively, Oracle’s START WITH and CONNECT BY clauses can be used to perform many recursive queries. |\n| T141, SIMILAR predicate | Oracle provides REGEXP_LIKE for pattern matching with a Perl-like syntax. |\n| T172, AS subquery clause in table definition | Oracle’s AS subquery feature of CREATE TABLE has substantially the same functionality as the standard, though there are some syntactic differences. |\n| T175, Generated columns | Oracle supports this feature, with the following restrictions: \n - Generated columns are not supported in temporary tables. \n - The data type of a generated column may not be LOB or XML. |\n| T176, Sequence generator support | Oracle’s sequences have the same capabilities as the standard’s, though with different syntax. |\n| T201, Comparable data types for referential constraints | Oracle fully supports this feature. |\n| T211, Basic trigger capability | Oracle’s triggers differ from the standard as follows: \n - Oracle does not provide the optional syntax FOR EACH STATEMENT for the default case, the statement trigger. \n - Oracle does not support OLD TABLE and NEW TABLE; the transition tables specified in the standard (the multiset of before and after images of affected rows) are not available. \n - The trigger body is written in PL/SQL, which is functionally equivalent to the standard’s procedural language PSM, but not the same. \n - In the trigger body, the new and old transition variables are referenced beginning with a colon. \n - Oracle’s row triggers are executed as the row is processed, instead of buffering them and executing all of them after processing all rows. The standard’s semantics are deterministic, but Oracle’s in-flight row triggers are more performant. \n - Oracle’s before-row and before-statement triggers can perform DML statements, which is forbidden in the standard. However, Oracle’s after-row statements cannot perform DML, while it is permitted in the standard. \n - When multiple triggers apply, the standard says they are executed in order of definition. In Oracle the execution order is nondeterministic. \n - Oracle uses the system privileges CREATE TRIGGER and CREATE ANY TRIGGER to regulate creation of triggers, instead of the standard’s TRIGGER privilege, which is a table privilege. |\n\n| Feature ID, Feature | Support |\n|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| T212, Enhanced trigger capability | This feature permits statements triggers, which Oracle supports, as described for feature T211, Basic trigger capability. |\n| T213, INSTEAD OF triggers | Oracle supports INSTEAD OF triggers on views, with syntax and semantics agreeing with the standard except as noted for feature 211, Basic trigger capability. |\n| T241, START TRANSACTION statement | Oracle's SET TRANSACTION statement starts a transaction making it equivalent to the standard's START TRANSACTION rather than the standard's SET TRANSACTION. Oracle's READ ONLY transactions are at SERIALIZABLE isolation level. |\n| T271, Savepoints | Oracle supports this feature, except: \n - Oracle does not support RELEASE SAVEPOINT. \n - Oracle does not support savepoint levels. |\n| T285, Enhanced derived column names | This feature pertains only to derived columns in a SELECT list with no column alias and consisting of a SQL parameter reference. In that case, the column name defaults to the parameter name, the same as in the standard. |\n| T322, Overloading of SQL-invoked functions and procedures | Oracle supports overloading of functions and procedures. However, the rules for handling certain data type combinations are not the same as the standard. For example, the standard permits the coexistence of two functions of the same name differing only in the numeric types of the arguments, whereas Oracle does not permit this. |\n| T323, Explicit security for external routines | The Oracle syntax AUTHID { CURRENT USER | DEFINER } when used when creating an external function, procedure, or package is equivalent to the standard's EXTERNAL SECURITY { DEFINER | INVOKER }. |\n| T324, Explicit security for SQL routines | Oracle's syntax AUTHID { CURRENT USER | DEFINER } when used when creating a PL/SQL function, procedure, or package is equivalent to the standard's SQL SECURITY { DEFINER | INVOKER }. |\n| T325, Qualified SQL parameter reference | PL/SQL supports the use of a routine name to qualify a parameter name. |\n| T326, Table functions | Oracle provides equivalents for the following elements of this feature: \n - <multiset value constructor by query> is supported using CAST (MULTISET (<query expression>) AS <nested table type>) \n - <table function derived table> is supported using the TABLE operator in the FROM clause with a varray or nested table as the argument \n - <collection value expression> is equivalent to an Oracle expression resulting in a varray or nested table \n - <returns table type> is equivalent to a PL/SQL function that returns a nested table |\n| T331, Basic roles | Oracle supports this feature, except for REVOKE ADMIN OPTION FOR <role name>. |\n| T351, Bracketed comments | Oracle fully supports this feature. |\n| T431, Extended grouping capabilities | Oracle fully supports this feature. |\n\n| Feature ID, Feature | Support |\n|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| T432, Nested and concatenated GROUPING SETS | Oracle supports concatenated GROUPING SETS, but not nested GROUPING SETS. |\n| T433, Multiargument function GROUPING | The Oracle GROUP_ID function can be used to conveniently distinguish groups in a grouped query, serving the same purpose as the standard multiargument GROUPING function. |\n| T441, ABS and MOD functions | Oracle supports the ABS function. Oracle's MOD function is similar to the standard, though the behavior is different if the two arguments are of opposite sign. |\n| T471, Result sets return value | PL/SQL ref cursors provide all the functionality of the standard's result set cursors. |\n| T491, LATERAL derived tables | The Oracle TABLE operator in the FROM clause is equivalent to the LATERAL operator in the standard, but only for collection expressions. |\n| T501, Enhanced EXISTS predicate | Oracle fully supports this feature. |\n| T571, Array-returning external SQL-invoked function | Oracle table functions returning a varray can be defined in external programming languages. When declaring such functions in SQL, use the CREATE FUNCTION command with the PIPELINED USING clause. |\n| T572, Multiset-returning external SQL-invoked function | Oracle table functions returning a nested table can be defined in external programming languages. When declaring such functions in SQL, use the CREATE FUNCTION command with the PIPELINED USING clause. In the body of the function, use the OCTTable interface. The function must be invoked within the TABLE operator in the FROM clause. |\n| T581, Regular expressions substring functions | Oracle provides the REGEXP_SUBSTR function to perform substring operations using regular expression matching. |\n| T591, UNIQUE constraints of possibly null columns | Oracle permits a UNIQUE constraint on one or more nullable columns. If the UNIQUE constraint is on a single column, then the semantics are the same as the standard (the constraint permits any number of rows that are null in the designated column). If the UNIQUE constraint is on two or more columns, then the semantics are nonstandard. Oracle permits any number of rows that are null in all the designated columns. Unlike the standard, if a row is non-null in at least one of the designated columns, then another row having the same values in the non-null columns of the constraint is a constraint violation and not permitted. |\n| T611, Elementary OLAP operations | Oracle fully supports this feature. |\n| T612, Advanced OLAP operations | Oracle supports the following elements of this feature: PERCENT_RANK, CUME_DIST, WIDTH_BUCKET, hypothetical set functions, PERCENTILE_CONT, and PERCENTILE_DISC. Oracle does not support the following elements of this feature: \n - window names \n - ROW_NUMBER without an ORDER BY clause |\n| T613, Sampling | Oracle uses the keyword SAMPLE instead of the standard's keyword, TABLESAMPLE. Oracle uses the keyword BLOCK instead of the standard's keyword, SYSTEM. Oracle uses the absence of the keyword BLOCK to indicate a Bernoulli sampling of rows, indicated in the standard by the keyword BERNouLLI. |\n\nTable C–2 (Cont.) Oracle Support for Optional Features of SQL/Foundation:2008\n\n| Feature ID, Feature | Support |\n|--------------------------------------------|-------------------------------------------------------------------------|\n| T621, Enhanced numeric functions | Oracle fully supports this feature, except for the alternate spelling CEILING of the CELL function. |\n| T641, Multiple column assignment | The standard syntax to assign to multiple columns is supported if the assignment source is a subquery. |\n| T652, SQL-dynamic statements in SQL routines.| PL/SQL supports dynamic SQL. |\n| T654, SQL-dynamic statements in external routines | Oracle supports dynamic SQL in embedded C, which may be used to create an external routine. |\n| T655, Cyclically dependent routines | PL/SQL supports recursion. |\n\nOracle Compliance with SQL/CLI:2008\n\nThe Oracle ODBC driver conforms to SQL/CLI:2008.\n\nOracle Compliance with SQL/PSM:2008\n\nOracle PL/SQL provides functionality equivalent to SQL/PSM:2008, with minor syntactic differences, such as the spelling or arrangement of keywords.\n\nOracle Compliance with SQL/MED:2008\n\nOracle does not comply with SQL/MED:2008.\n\nOracle Compliance with SQL/OLB:2008\n\nOracle SQLJ conforms to SQL/OLB:1999 and not yet to SQL/OLB 2008.\n\nOracle Compliance with SQL/JRT:2008\n\nOracle fully supports stored routines and SQL types implemented in Java(TM). Oracle provides equivalent support for the creation and maintenance of such types and procedures. Oracle's capabilities are in general a superset of the functionality defined by the standard.\n\nOracle Compliance with SQL/XML:2008\n\nThe XML data type in the standard is XML. The Oracle equivalent data type is XMLType. A feature of the standard is considered to be fully supported if the only difference between Oracle and the standard is the spelling of the data type name.\n\nTable C–3 describes Oracle's support for the features of SQL/XML:2008.\n\nTable C–3 Oracle Support for Features of SQL/XML:2008\n\n| Feature ID, Feature | Support |\n|---------------------------|-------------------------------------------------------------------------|\n| X010, XML type | Oracle fully supports this feature. |\n| X011, Arrays of XML types | Oracle supports this feature using named array types (in the standard, array types are anonymous) |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| X012, Multisets of XML type | The Oracle equivalent of a multiset of XML type is a nested table with a single column of XML type. |\n| X013, Distinct types of XML | A distinct type can be emulated using an object type with a single attribute. |\n| X014, Attributes of XML type | In Oracle, attributes of object types may be of type XMLType, but the syntax for creating object types is nonstandard. |\n| X016, Persistent XML values | Oracle fully supports this feature. |\n| X020, XML Concatenation | Oracle fully supports this feature. |\n| X025, XMLCast | Oracle provides equivalents for the following elements of this feature: \n- To cast from XML to a scalar type, use EXTRACTVALUE. If the XML value is typed, then the result is in the nearest analog to the XML type, otherwise the result type is VARCHAR(4000). Use CAST to convert to any other scalar type. \n- To cast from a scalar type to XML, pass the scalar value in to XMLQuery and insert it in a document constructor. \nSince Oracle has only one XML type, there is no need to cast from XML to XML. |\n| X031, XMLElement | Oracle fully supports this feature. |\n| X032, XMLForest | Oracle fully supports this feature. |\n| X034, XMLAgg | Oracle fully supports this feature. |\n| X035, XMLAgg: ORDER BY option | Oracle fully supports this feature. |\n| X036, XMLComment | Oracle fully supports this feature. |\n| X036, XMLPi | Oracle fully supports this feature. |\n| X038, XMLText | The Oracle XMLCDATA function may be used to create a text node. |\n| X040, Basic table mapping | Oracle table mappings are available through a Java interface and through a package. Oracle table mappings have been generalized to map queries and not just tables. To map only a table: SELECT * FROM table_name. This provides support for the following elements of this feature: \n- X041, Basic table mapping: null absent \n- X042, Basic table mapping: null as nil \n- X043, Basic table mapping: table as forest \n- X044, Basic table mapping: table as element \n- X045, Basic table mapping: with target namespace \n- X046, Basic table mapping: data mapping \n- X047, Basic table mapping: metadata mapping \n- X049, Basic table mapping: hex encoding \nOracle does not support the following element of this feature: \n- X048, Basic table mapping: base64 encoding |\n| X060, XMLParse: Character string input and CONTENT option | Oracle does not support the {PRESERVE | STRIP} WHITESPACE syntax. The behavior is always STRIP WHITESPACE. |\n\n| Feature ID, Feature | Support |\n|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| X061, XMLParse: Character string input and DOCUMENT option | Oracle does not support the \\{PRESERVE | STRIP\\} WHITESPACE syntax. The behavior is always STRIP WHITESPACE. |\n| X070, XMLSerialize: Character string serialization and CONTENT option | Oracle fully supports this feature. |\n| X071, XMLSerialize: Character string serialization and DOCUMENT option | Oracle fully supports this feature. |\n| X072, XMLSerialize: Character string serialization | Oracle fully supports this feature. |\n| X076, XMLSerialize: VERSION option | Use XMLRoot to set the XML version prior to serialization. |\n| X080, Namespaces in XML publishing | In the Oracle implementation of XMLElement, XMLAttributes are used to define namespaces (XMLNamespaces is not implemented). However, XMLAttributes is not supported for XMLForest. |\n| X086, XML namespace declarations in XMLTable | Oracle fully supports this feature. |\n| X090, XML document predicate | In Oracle, you can test whether an XML value is a document by using the ISFRAGMENT method. |\n| X096, XMLExists | Use EXISTSNODE to evaluate an XPath, returning 1 if a node is found, 0 if not. XQuery expressions other than XPath expressions are not supported. Also, Oracle supports XPath 1.0 expressions (not XPath 2.0, which is a subset of XQuery). |\n| X120, XML parameters in SQL routines | Oracle fully supports this feature. |\n| X121, XML parameters in external routines | Oracle supports XML values passed to external routines using a non-standard interface. |\n| X141, IS VALID predicate: data drive case | The XMLISVALID method is equivalent to the IS VALID predicate, and supports the data-driven case. |\n| X142, IS VALID predicate: ACCORDING TO clause | The XMLISVALID method is equivalent to the IS VALID predicate, and includes the equivalent of the ACCORDING TO clause. |\n| X143, IS VALID predicate: ELEMENT clause | The XMLISVALID method is equivalent to the IS VALID predicate, and includes the equivalent of the ELEMENT clause. |\n| X144, IS VALID predicate: schema location | The XMLISVALID method is equivalent to the IS VALID predicate, and supports the specification of a schema location for a registered XML Schema. |\n| X145, IS VALID predicate outside check constraints | The XMLISVALID method is equivalent to the IS VALID predicate, and may be used outside check constraints. |\n| X151, IS VALID predicate with DOCUMENT option | The XMLISVALID method is equivalent to the IS VALID predicate, and performs validation equivalent to the DOCUMENT clause. (XMLISVALID does not support \"content\" validation.) |\n| X156, IS VALID predicate: optional NAMESPACE with ELEMENT clause | The XMLISVALID method is equivalent to the IS VALID predicate, and may be used to validate against an element in any namespace. |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| X157, IS VALID predicate: NO NAMESPACE with ELEMENT clause | The XMLISVALID method is equivalent to the IS VALID predicate, and may be used to validate against an element in the \"no name\" namespace. |\n| X160, Basic Information Schema for registered XML Schemas | The Oracle static data dictionary view ALL_XML_SCHEMAS provides a list of the registered XML schemas that are accessible to the current user. The ALL_XML_SCHEMAS.SCHEMA_URL column corresponds to the standard XML_SCHEMAS.XML_SCHEMA_LOCATION column. The target namespace of the registered XML Schemas can be learned by examining ALL_XML_SCHEMAS.SCHEMA. Oracle has no equivalents for the other columns of the standard's XML_SCHEMAS. |\n| X161, Advanced Information Schema for registered XML Schemas | Oracle does not have static data dictionary views corresponding to XML_SCHEMA_NAMESPACES and XML_SCHEMA_ELEMENTS in the standard. However, all the information about registered XML Schemas may be learned by examining the actual XML Schema, which is found in the ALL_XML_SCHEMAS.SCHEMA column. This may also be examined to learn whether a registered XML Schema is nondeterministic, and which of its namespaces and elements are nondeterministic. |\n| X191, XML(DOCUMENT(XMLSHEMA)) type | Oracle does not support this syntax. However, a column of a table can be constrained by a registered XML Schema, in which case all values of the column will be of XML(DOCUMENT(XMLSHEMA)) type. |\n| X200, XMLQuery | Oracle fully supports the following elements of this feature: \n- X201, XMLQuery: RETURNING CONTENT \n- X203, XMLQuery: passing a context item \n- X204, XMLQuery: initializing an XQuery variable \nOracle does not support the following elements of this feature: \n- X202, XMLQuery: RETURNING SEQUENCE \n- { NULL | EMPTY } ON EMPTY syntax \n- Mandatory BY { REF | VALUE } in the PASSING clause (Oracle supports only value semantics) |\n| X221, XML passing mechanism BY VALUE | Oracle supports only value semantics, but does not support the explicit BY VALUE clause. |\n| X232, XML(CONTENT(ANY)) type | Oracle does not support this syntax as a type modifier, but the Oracle XMLType supports this data type for transient values. Persistent values are of type XML(DOCUMENT(ANY)), which is a subset of XML(CONTENT(ANY)). |\n| X241, RETURNING CONTENT in XML publishing | Oracle does not support this syntax. In Oracle, the behavior of the publishing functions (XMLAgg, XMLComment, XMLConcat, XMLElement, XMLForest, and XMLPi) is always RETURNING CONTENT. |\n| X251, Persistent XML values of XML(DOCUMENT(UNTYPED)) type | Oracle fully supports this feature. |\n| X252, Persistent values of type XML(DOCUMENT(ANY)) | Oracle fully supports this feature. |\n| X256, Persistent values of XML(DOCUMENT(XMLSHEMA)) type | Oracle fully supports this feature. |\n\n| Feature ID, Feature | Support |\n|---------------------|---------|\n| X260, XML type, ELEMENT clause | Oracle does not support this syntax. However, a column of a table may be constrained by a top-level element in a registered XML Schema. |\n| X262, XML type, optional NAMESPACE with ELEMENT clause | Oracle does not support this syntax. However, a column of a table may be constrained by a top-level element in a namespace other than the target namespace of a registered XML Schema. |\n| X263, XML type: NO NAMESPACE with ELEMENT clause | Oracle does not support this syntax. However, a column of a table may be constrained by a top-level element in the \"no name\" namespace of a registered XML Schema. |\n| X264, XML type: schema location | Oracle does not support this syntax. However, a column of a table may be constrained by a registered XML Schema that is identified by a schema location. |\n| X271, XMLValidate: data driven case | The SCHEMVALIDATE method is equivalent to XMLValidate, and supports the data-driven case. |\n| X272, XMLValidate: ACCORDING TO clause | The SCHEMVALIDATE method is equivalent to XMLValidate, and may be used to specify a particular registered XML Schema. |\n| X273, XMLValidate: ELEMENT clause | The SCHEMVALIDATE method is equivalent to XMLValidate, and may be used to specify a particular element of a particular registered XML Schema. |\n| X274, XMLValidate: schema location | The SCHEMVALIDATE method is equivalent to XMLValidate, and may be used to specify a particular registered XML Schema by its schema location URL. |\n| X281, XMLValidate with DOCUMENT option | The SCHEMVALIDATE method is equivalent to XMLValidate. SCHEMVALIDATE performs validation only of XML documents (not content). |\n| X285, XMLValidate: optional NAMESPACE with ELEMENT clause | The SCHEMVALIDATE method is equivalent to XMLValidate, and may be used to specify a particular element in a namespace other than the target namespace of a particular registered XML Schema. |\n| X286, XMLValidate: NO NAMESPACE with ELEMENT clause | The SCHEMVALIDATE method is equivalent to XMLValidate, and may be used to specify a particular element in the \"no name\" namespace of a particular registered XML Schema. |\n| X300, XMLTable | Oracle does not support reverse axes in the column path expressions. Aside from that restriction, Oracle fully supports the following elements of this feature:\n- X086, XML namespace declarations in XMLTable\n- X302, XMLTable with ordinality column\n- X303, XMLTable: column default option\n- X304, XMLTable: passing a context item\n- X305, XMLTable: initializing an XQuery variable\n\nOracle does not support the following elements of this feature:\n- X301, XMLTable: derived column list option\n- Mandatory BY [REF | VALUE] in the PASSING clause. Oracle supports only BY VALUE semantics currently. |\n\nOracle Compliance with FIPS 127-2\n\nOracle complied fully with last Federal Information Processing Standard (FIPS), which was FIPS PUB 127-2. That standard is no longer published. However, for users whose applications depend on information about the sizes of some database constructs that were defined in FIPS 127-2, the details of our compliance are listed in Table C–4.\n\nTable C–4 Sizing for Database Constructs\n\n| Database Constructs | FIPS | Oracle Database |\n|----------------------------------------------------------|--------|-----------------|\n| Length of an identifier (in bytes) | 18 | 30 |\n| Length of CHARACTER data type (in bytes) | 240 | 2,000 |\n| Decimal precision of NUMERIC data type | 15 | 38 |\n| Decimal precision of DECIMAL data type | 15 | 38 |\n| Decimal precision of INTEGER data type | 9 | 38 |\n| Decimal precision of SMALLINT data type | 4 | 38 |\n| Binary precision of FLOAT data type | 20 | 126 |\n| Binary precision of REAL data type | 20 | 63 |\n| Binary precision of DOUBLE PRECISION data type | 30 | 126 |\n| Columns in a table | 100 | 1,000 |\n| Values in an INSERT statement | 100 | 1,000 |\n| SET clauses in an UPDATE statement (Note 1) | 20 | 1,000 |\n| Length of a row (Note2, Note 3) | 2,000 | 2,000,000 |\n| Columns in a UNIQUE constraint | 6 | 32 |\n| Length of a UNIQUE constraint (Note 2) | 120 | (Note 4) |\n| Length of foreign key column list (Note 2) | 120 | (Note 4) |\n| Columns in a GROUP BY clause | 6 | 255 (Note 5) |\n| Length of GROUP BY column list | 120 | (Note 5) |\n| Sort specifications in ORDER BY clause | 6 | 255 (Note 5) |\n| Length of ORDER BY column list | 120 | (Note 5) |\n| Columns in a referential integrity constraint | 6 | 32 |\n| Tables referenced in a SQL statement | 15 | No limit |\n| Cursors simultaneously open | 10 | (Note 6) |\n| Items in a SELECT list | 100 | 1,000 |\n\n**Note 1:** The number of SET clauses in an UPDATE statement refers to the number items separated by commas following the SET keyword.\n\n**Note 2:** The FIPS PUB defines the length of a collection of columns to be the sum of: twice the number of columns, the length of each character column in bytes, decimal precision plus 1 of each exact numeric column, binary precision divided by 4 plus 1 of each approximate numeric column.\n\n**Note 3:** The Oracle limit for the maximum row length is based on the maximum length of a row containing a LONG value of length 2 gigabytes and 999 VARCHAR2 values, each of length 4000 bytes: \\(2(254) + 231 + (999(4000))\\).\n\nNote 4: The Oracle limit for a UNIQUE key is half the size of an Oracle data block (specified by the initialization parameter DB_BLOCK_SIZE) minus some overhead.\n\nNote 5: Oracle places no limit on the number of columns in a GROUP BY clause or the number of sort specifications in an ORDER BY clause. However, the sum of the sizes of all the expressions in either a GROUP BY clause or an ORDER BY clause is limited to the size of an Oracle data block (specified by the initialization parameter DB_BLOCK_SIZE) minus some overhead.\n\nNote 6: The Oracle limit for the number of cursors simultaneously opened is specified by the initialization parameter OPEN_CURSORS. The maximum value of this parameter depends on the memory available on your operating system and exceeds 100 in all cases.\n\nOracle Extensions to Standard SQL\n\nOracle supports numerous features that extend beyond standard SQL. If you are concerned with the portability of your applications to other implementations of SQL, then use Oracle's FIPS Flagger to help identify the use of Oracle extensions to Entry SQL-92 in your embedded SQL programs. The FIPS Flagger is part of the Oracle precompilers and the SQL*Module compiler. The FIPS Flagger can also be enabled in SQL*Plus by using ALTER SESSION SET FLAGGER = ENTRY. While SQL-92 has been superseded by SQL:2008, there has been no conformance testing authority for any version of SQL since SQL-92; hence, Entry SQL-92 offers you the most assurance of portability.\n\nSee Also: Pro*COBOL Programmer’s Guide and Pro*C/C++ Programmer’s Guide for information on how to use the FIPS Flagger\n\nOracle Compliance with Older Standards\n\nThis release of Oracle Database conforms to SQL:2008, the most recent edition of the SQL standard, as itemized in preceding sections of this appendix. Oracle does not formally claim that this release of the database conforms to SQL-92—and in particular, to SQL-92 Entry Level—or to SQL:1999, because those standards have been superseded by SQL:2008. Some, mostly minor, changes between editions of the SQL standard—both between SQL-92 and SQL:1999 and between SQL:1999 and SQL:2008—might affect applications. The SQL standard, or a reference discussing that standard, can be consulted to determine the details of any incompatibilities that have been introduced. One important source is Annex E of SQL/Foundation:1999 and SQL/Foundation:2008.\n\nIn some cases, this release of Oracle Database might continue to recognize constructs from older editions of SQL. Such recognition is often allowed as a valid vendor extension. It is the general policy of Oracle to keep incompatibilities between versions of the database as few as possible. This policy extends to retention of older forms when that is feasible. In any case, the differences between older SQL and SQL:2008 (as noted above) are relatively inconsequential.\n\nCharacter Set Support\n\nOracle supports most national, international, and vendor-specific encoded character set standards. A complete list of character sets supported by Oracle appears in Oracle Database Globalization Support Guide.\n\nUnicode is a universal encoded character set that lets you store information from any language using a single character set. Unicode is required by modern standards such\n\nas XML, Java, JavaScript, and LDAP. Unicode is compliant with ISO/IEC standard 10646. You can obtain a copy of ISO/IEC standard 10646 from this address:\n\nInternational Organization for Standardization\n1 Rue de Varembé\nCase postale 56\nCH-1211, Geneva 20, Switzerland\nPhone: +41.22.749.0111\nFax: +41.22.733.3430\nWeb site: http://www.iso.ch/\n\nOracle Database complies fully with Unicode 4.0, the fourth and most recent version of the Unicode standard. For up-to-date information on this standard, visit the Web site of the Unicode Consortium:\n\nhttp://www.unicode.org\n\nOracle uses UTF-8 (8-bit) encoding by way of three database character sets, two for ASCII-based platforms (UTF8 and AL32UTF8) and one for EBCDIC platforms (UTFE). If you prefer to implement Unicode support incrementally, then you can store Unicode data in either the UTF-16 or UTF-8 encoding form, in the national character set, for the SQL NCHAR data types (NCHAR, NVARCHAR2, and NCLOB).\n\nSee Also: Oracle Database Globalization Support Guide for details on Oracle character set support\n\nOracle's implementation of regular expressions conforms with the IEEE Portable Operating System Interface (POSIX) regular expression standard and to the Unicode Regular Expression Guidelines of the Unicode Consortium.\n\nThis appendix contains the following sections:\n\n- Multilingual Regular Expression Syntax\n- Regular Expression Operator Multilingual Enhancements\n- Perl-influenced Extensions in Oracle Regular Expressions\n\n**Multilingual Regular Expression Syntax**\n\nTable D–1 lists the full set of operators defined in the POSIX standard Extended Regular Expression (ERE) syntax. Oracle follows the exact syntax and matching semantics for these operators as defined in the POSIX standard for matching ASCII (English language) data. For more complete descriptions of the operators, examples of their use, and Oracle multilingual enhancements of the operators, refer to *Oracle Database Advanced Application Developer’s Guide*. Notes following the table provide more complete descriptions of the operators and their functions, as well as Oracle multilingual enhancements of the operators. Table D–2 summarizes Oracle support for and multilingual enhancement of the POSIX operators.\n\n| Operator | Description |\n|----------|-------------|\n| \\ | The backslash character can have four different meanings depending on the context. It can: |\n| | - Stand for itself |\n| | - Quote the next character |\n| | - Introduce an operator |\n| | - Do nothing |\n| * | Matches zero or more occurrences |\n| + | Matches one or more occurrences |\n| ? | Matches zero or one occurrence |\n| | | Alternation operator for specifying alternative matches |\n| ^ | Matches the beginning of a string by default. In multiline mode, it matches the beginning of any line anywhere within the source string. |\n\n| Operator | Description |\n|----------|-------------|\n| $ | Matches the end of a string by default. In multiline mode, it matches the end of any line anywhere within the source string. |\n| . | Matches any character in the supported character set except NULL. |\n| [ ] | Bracket expression for specifying a matching list that should match any one of the expressions represented in the list. A non-matching list expression begins with a circumflex (^) and specifies a list that matches any character except for the expressions represented in the list. To specify a right bracket (]) in the bracket expression, place it first in the list (after the initial circumflex (^), if any). To specify a hyphen in the bracket expression, place it first in the list (after the initial circumflex (^), if any), last in the list, or as an ending range point in a range expression. |\n| ( ) | Grouping expression, treated as a single subexpression. |\n| {m} | Matches exactly m times. |\n| {m,} | Matches at least m times. |\n| {m,n} | Matches at least m times but no more than n times. |\n| \\n | The backreference expression (n is a digit between 1 and 9) matches the nth subexpression enclosed between '(' and ')' preceding the \\n. |\n| [..] | Specifies one collation element, and can be a multicharacter element (for example, [ch.] in Spanish). |\n| [: :] | Specifies character classes (for example, [:alpha:]). It matches any character within the character class. |\n| [===] | Specifies equivalence classes. For example, [=a=] matches all characters having base letter 'a'. |\n\n### Regular Expression Operator Multilingual Enhancements\n\nWhen applied to multilingual data, Oracle's implementation of the POSIX operators extends beyond the matching capabilities specified in the POSIX standard. Table D–2 shows the relationship of the operators in the context of the POSIX standard.\n\n- The first column lists the supported operators.\n- The second and third columns indicate whether the POSIX standard (Basic Regular Expression—BRE and Extended Regular Expression—ERE, respectively) defines the operator.\n- The fourth column indicates whether Oracle's implementation extends the operator's semantics for handling multilingual data.\n\nOracle lets you enter multibyte characters directly, if you have a direct input method, or you can use functions to compose the multibyte characters. You cannot use the Unicode hexadecimal encoding value of the form '\\xxxx'. Oracle evaluates the characters based on the byte values used to encode the character, not the graphical representation of the character. All accented characters are considered word characters.\n\n| Operator | POSIX BRE syntax | POSIX ERE Syntax | Multilingual Enhancement |\n|----------|------------------|------------------|-------------------------|\n| \\ | Yes | Yes | — |\n\n### Table D–2 (Cont.) POSIX and Multilingual Operator Relationships\n\n| Operator | POSIX BRE syntax | POSIX ERE Syntax | Multilingual Enhancement |\n|----------|------------------|------------------|-------------------------|\n| * | Yes | Yes | — |\n| + | -- | Yes | — |\n| ? | — | Yes | — |\n| | | — | Yes | — |\n| ^ | Yes | Yes | Yes |\n| $ | Yes | Yes | Yes |\n| . | Yes | Yes | Yes |\n| [ ] | Yes | Yes | Yes |\n| ( ) | Yes | Yes | — |\n| {m} | Yes | Yes | — |\n| {m,} | Yes | Yes | — |\n| {m,n} | Yes | Yes | — |\n| \\n | Yes | Yes | Yes |\n| [..] | Yes | Yes | Yes |\n| [::] | Yes | Yes | Yes |\n| [==] | Yes | Yes | Yes |\n\n### Perl-influenced Extensions in Oracle Regular Expressions\n\nOracle Database regular expression functions and conditions accept a number of Perl-influenced operators that are in common use, although not part of the POSIX standard. **Table D–3** lists those operators. For more complete descriptions with examples, refer to *Oracle Database Advanced Application Developer’s Guide*.\n\n#### Table D–3 Perl-influenced Operators in Oracle Regular Expressions\n\n| Operator | Description |\n|----------|-------------|\n| \\d | A digit character. |\n| \\D | A nondigit character. |\n| \\w | A word character. |\n| \\W | A nonword character. |\n| \\s | A whitespace character. |\n| \\S | A non-whitespace character. |\n| \\A | Matches only at the beginning of a string, or before a newline character at the end of a string. |\n| \\Z | Matches only at the end of a string. |\n| *? | Matches the preceding pattern element 0 or more times (nongreedy). |\n\n| Operator | Description |\n|----------|-------------|\n| +? | Matches the preceding pattern element 1 or more times (nongreedy). |\n| ?? | Matches the preceding pattern element 0 or 1 time (nongreedy). |\n| {n}? | Matches the preceding pattern element exactly $n$ times (nongreedy). |\n| {n,}? | Matches the preceding pattern element at least $n$ times (nongreedy). |\n| {n,m}? | Matches the preceding pattern element at least $n$ but not more than $m$ times (nongreedy). |\n\nOracle SQL Reserved Words and Keywords\n\nThis appendix contains the following sections:\n\n- Oracle SQL Reserved Words\n- Oracle SQL Keywords\n\nOracle SQL Reserved Words\n\nThis section lists Oracle SQL reserved words. You cannot use Oracle SQL reserved words as nonquoted identifiers. Quoted identifiers can be reserved words, although this is not recommended.\n\nNote: In addition to the following reserved words, Oracle uses system-generated names beginning with \"SYS_\" for implicitly generated schema objects and subobjects. Oracle discourages you from using this prefix in the names you explicitly provide to your schema objects and subobjects to avoid possible conflict in name resolution.\n\nThe V$RESERVED_WORDS data dictionary view provides additional information on each reserved word, including whether it is always reserved or is reserved only for particular uses. Refer to Oracle Database Reference for more information.\n\nWords followed by an asterisk (*) are also ANSI reserved words.\n\nACCESS\nADD\nALL *\nALTER *\nAND *\nANY *\nAS *\nASC\nAUDIT\nBETWEEN *\nBY *\nCHAR *\nCHECK *\nCLUSTER\nCOLUMN *\nCOLUMN_VALUE (See Note 1 at the end of this list)\nCOMMENT\n\nCOMPRESS\nCONNECT *\nCREATE *\nCURRENT *\nDATE *\nDECIMAL *\nDEFAULT *\nDELETE *\nDESC\nDISTINCT *\nDROP *\nELSE *\nEXCLUSIVE\nEXISTS *\nFILE\nFLOAT *\nFOR *\nFROM *\nGRANT *\nGROUP *\nHAVING *\nIDENTIFIED\nIMMEDIATE\nIN *\nINCREMENT\nINDEX\nINITIAL\nINSERT *\nINTEGER *\nINTERSECT *\nINTO *\nIS *\nLEVEL\nLIKE *\nLOCK\nLONG\nMAXEXTENTS\nMINUS\nMLSLABEL\nMODE\nMODIFY\nNESTED_TABLE_ID (See Note 1 at the end of this list)\nNOAUDIT\nNOCOMPRESS\nNOT *\nNOWAIT\nNULL *\nNUMBER\nOF *\nOFFLINE\nON *\nONLINE\nOPTION\nOR *\nORDER *\n\nPCTFREE\nPRIOR\nPRIVILEGES\nPUBLIC\nRAW\nRENAME\nRESOURCE\nREVOKE *\nROW *\nROWID (See Note 2 at the end of this list)\nROWNUM\nROWS *\nSELECT *\nSESSION\nSET *\nSHARE\nSIZE\nSMALLINT *\nSTART *\nSUCCESSFUL\nSYNONYM\nSYSDATE\nTABLE *\nTHEN *\nTO *\nTRIGGER *\nUID\nUNION *\nUNIQUE *\nUPDATE *\nUSER *\nVALIDATE\nVALUES *\nVARCHAR *\nVARCHAR2\nVIEW\nWHENEVER *\nWHERE *\nWITH *\n\nNote 1: This keyword is only reserved for use as an attribute name.\n\nNote 2: You cannot use the uppercase word ROWID, either quoted or nonquoted, as a column name. However, you can use the uppercase word as a quoted identifier that is not a column name, and you can use the word with one or more lowercase letters (for example, \"Rowid\" or \"rowid\") as any quoted identifier, including a column name.\n\nOracle SQL Keywords\n\nOracle SQL keywords are not reserved. However, Oracle uses them internally in specific ways. Therefore, if you use these words as names for objects and object parts, then your SQL statements may be more difficult to read and may lead to unpredictable results.\n\nYou can obtain a list of keywords by querying the V$RESERVED_WORDS data dictionary view. All keywords in the view that are not listed as always reserved or\n\nreserved for a specific use are Oracle SQL keywords. Refer to *Oracle Database Reference* for more information.\n\nThe body of the *SQL Language Reference* contains examples for almost every reference topic. This appendix contains lengthy examples that are not appropriate in the context of a single SQL statement. These examples are intended to provide uninterrupted the series of steps that you would use to take advantage of particular Oracle functionality. They do not replace the syntax diagrams and semantics found for each individual SQL statement in the body of the reference. Please use the cross-references provided to access additional information, such as privileges required and restrictions, as well as syntax.\n\nThis appendix contains the following sections:\n\n- Using Extensible Indexing\n- Using XML in SQL Statements\n\n**Using Extensible Indexing**\n\nThis section provides examples of the steps entailed in a simple but realistic extensible indexing scenario.\n\nSuppose you want to rank the salaries in the `HR.employees` table and then find those that rank between 10 and 20. You could use the `DENSE_RANK` function, as follows:\n\n```sql\nSELECT last_name, salary FROM\n (SELECT last_name, DENSE_RANK() OVER\n (ORDER BY salary DESC) rank_val, salary FROM employees)\nWHERE rank_val BETWEEN 10 AND 20;\n```\n\n**See Also:** `DENSE_RANK` on page 5-61\n\nThis nested query is somewhat complex, and it requires a full scan of the `employees` table as well as a sort. An alternative would be to use extensible indexing to achieve the same goal. The resulting query will be simpler. The query will require only an index scan and a table access by rowid, and will therefore perform much more efficiently.\n\nThe first step is to create the implementation type `position_im`, including method headers for index definition, maintenance, and creation. Most of the type body uses PL/SQL, which is shown in italics.\n\nThe type must created with the `AUTHID CURRENT_USER` clause because of the `EXECUTE IMMEDIATE` statement inside the function `ODCIINDEXCREATE()`. By default that function runs with the definer rights. When the function is called in the subsequent creation of the domain index, the invoker does not have the same rights.\n\nSee Also:\n\n- CREATE TYPE on page 17-3 and CREATE TYPE BODY on page 17-5\n- Oracle Database Data Cartridge Developer’s Guide for complete information on the ODCI routines in this statement\n\nCREATE OR REPLACE TYPE position_im AUTHID CURRENT_USER AS OBJECT\n(\n curnum NUMBER,\n howmany NUMBER,\n lower_bound NUMBER,\n upper_bound NUMBER,\n /* lower_bound and upper_bound are used for the index-based functional implementation */\n STATIC FUNCTION ODCIGETINTERFACES(ifclist OUT SYS.ODCIOBJECTLIST) RETURN NUMBER,\n STATIC FUNCTION ODCIINDEXCREATE\n (ia SYS.ODCIINDEXINFO, parms VARCHAR2, env SYS.ODCIEnv) RETURN NUMBER,\n STATIC FUNCTION ODCIINDEXTRUNCATE (ia SYS.ODCIINDEXINFO,\n env SYS.ODCIEnv) RETURN NUMBER,\n STATIC FUNCTION ODCIINDEXDROP(ia SYS.ODCIINDEXINFO,\n env SYS.ODCIEnv) RETURN NUMBER,\n STATIC FUNCTION ODCIINDEXINSERT(ia SYS.ODCIINDEXINFO, rid ROWID,\n newval NUMBER, env SYS.ODCIEnv) RETURN NUMBER,\n STATIC FUNCTION ODCIINDEXDELETE(ia SYS.ODCIINDEXINFO, rid ROWID, oldval NUMBER,\n env SYS.ODCIEnv) RETURN NUMBER,\n STATIC FUNCTION ODCIINDEXUPDATE(ia SYS.ODCIINDEXINFO, rid ROWID, oldval NUMBER,\n newval NUMBER, env SYS.ODCIEnv) RETURN NUMBER,\n STATIC FUNCTION ODCIINDEXSTART(STCTX IN OUT position_im, ia SYS.ODCIINDEXINFO,\n op SYS.ODCIPREDINFO, qi SYS.ODCIQUERYINFO,\n strt NUMBER, stop NUMBER, lower_pos NUMBER,\n upper_pos NUMBER, env SYS.ODCIEnv) RETURN NUMBER,\n MEMBER FUNCTION ODCIINDEXFETCH(SELF IN OUT position_im, nrows NUMBER,\n rids OUT SYS.ODCIRIDLIST, env SYS.ODCIEnv)\n RETURN NUMBER,\n MEMBER FUNCTION ODCIINDEXCLOSE(env SYS.ODCIEnv) RETURN NUMBER\n);\n/\n\nCREATE OR REPLACE TYPE BODY position_im\nIS\n STATIC FUNCTION ODCIGETINTERFACES(ifclist OUT SYS.ODCIOBJECTLIST)\n RETURN NUMBER IS\n BEGIN\n ifclist := SYS.ODCIOBJECTLIST(SYS.ODCIOBJECT('SYS','ODCIINDEX2'));\n RETURN ODCICONST.SUCCESS;\n END ODCIGETINTERFACES;\n STATIC FUNCTION ODCIINDEXCREATE (ia SYS.ODCIINDEXINFO, parms VARCHAR2, env SYS.ODCIEnv) RETURN NUMBER\n IS\n stmt VARCHAR2(2000);\n BEGIN\n /* Construct the SQL statement */\n stmt := 'Create Table ' || ia.INDEXSCHEMA || '.' || ia.INDEXNAME ||\n '_STORAGE_TAB' || '(col_val, base_rowid, constraint pk PRIMARY KEY ' ||\n '(col_val, base_rowid)) ORGANIZATION INDEX AS SELECT ' ||\n ia.INDEXCOLS(1).COLNAME || ', ROWID FROM ' ||\n ia.INDEXCOLS(1).TABLESCHEMA || '.' || ia.INDEXCOLS(1).TABLENAME;\n EXECUTE IMMEDIATE stmt;\n\nRETURN ODCICONST.SUCCESS;\nEND;\n\nSTATIC FUNCTION ODCIINDEXDROP(ia SYS.ODCIINDEXINFO, env SYS.ODCIEnv) RETURN NUMBER IS\n stmt VARCHAR2(2000);\nBEGIN\n/* Construct the SQL statement */\n stmt := 'DROP TABLE ' || ia.INDEXSCHEMA || '.' || ia.INDEXNAME ||\n '_STORAGE_TAB';\n/* Execute the statement */\n EXECUTE IMMEDIATE stmt;\n RETURN ODCICONST.SUCCESS;\nEND;\n\nSTATIC FUNCTION ODCIINDEXTRUNCATE(ia SYS.ODCIINDEXINFO, env SYS.ODCIEnv) RETURN NUMBER IS\n stmt VARCHAR2(2000);\nBEGIN\n/* Construct the SQL statement */\n stmt := 'TRUNCATE TABLE ' || ia.INDEXSCHEMA || '.' || ia.INDEXNAME ||\n '_STORAGE_TAB';\n EXECUTE IMMEDIATE stmt;\n RETURN ODCICONST.SUCCESS;\nEND;\n\nSTATIC FUNCTION ODCIINDEXINSERT(ia SYS.ODCIINDEXINFO, rid ROWID,\n newval NUMBER, env SYS.ODCIEnv) RETURN NUMBER IS\n stmt VARCHAR2(2000);\nBEGIN\n/* Construct the SQL statement */\n stmt := 'INSERT INTO ' || ia.INDEXSCHEMA || '.' || ia.INDEXNAME ||\n '_STORAGE_TAB VALUES (''' || newval || ''', ''' || rid || ''')';\n/* Execute the statement */\n EXECUTE IMMEDIATE stmt;\n RETURN ODCICONST.SUCCESS;\nEND;\n\nSTATIC FUNCTION ODCIINDEXDELETE(ia SYS.ODCIINDEXINFO, rid ROWID, oldval NUMBER,\n env SYS.ODCIEnv)\nRETURN NUMBER IS\n stmt VARCHAR2(2000);\nBEGIN\n/* Construct the SQL statement */\n stmt := 'DELETE FROM ' || ia.INDEXSCHEMA || '.' || ia.INDEXNAME ||\n '_STORAGE_TAB WHERE col_val = ''' || oldval || ''' AND base_rowid = ''' || rid || '''';\n/* Execute the statement */\n EXECUTE IMMEDIATE stmt;\n RETURN ODCICONST.SUCCESS;\nEND;\n\nSTATIC FUNCTION ODCIINDEXUPDATE(ia SYS.ODCIINDEXINFO, rid ROWID, oldval NUMBER,\n newval NUMBER, env SYS.ODCIEnv) RETURN NUMBER IS\n stmt VARCHAR2(2000);\nBEGIN\n/* Construct the SQL statement */\n stmt := 'UPDATE ' || ia.INDEXSCHEMA || '.' || ia.INDEXNAME ||\n '_STORAGE_TAB SET col_val = ''' || newval || ''' WHERE f2 = ''' || rid || '''';\n/* Execute the statement */\n EXECUTE IMMEDIATE stmt;\n RETURN ODCICONST.SUCCESS;\nEND;\n\nSTATIC FUNCTION ODCIINDEXSTART(SCTX IN OUT position_im, ia SYS.ODCIINDEXINFO,\n op SYS.ODCIPREDINFO, qi SYS.ODCIQUERYINFO,\n strt NUMBER, stop NUMBER, lower_pos NUMBER,\n upper_pos NUMBER, env SYS.ODCIEnv) RETURN NUMBER IS\n\nrid VARCHAR2(5072);\nstorage_tab_name VARCHAR2(65);\nlower_bound_stmt VARCHAR2(2000);\nupper_bound_stmt VARCHAR2(2000);\nrange_query_stmt VARCHAR2(2000);\nlower_bound NUMBER;\nupper_bound NUMBER;\ncnum INTEGER;\nnrows INTEGER;\n\nBEGIN\n/* Take care of some error cases.\n The only predicates in which position operator can appear are\n op() = 1 OR\n op() = 0 OR\n op() between 0 and 1\n*/\n\n IF (((strt != 1) AND (strt != 0)) OR\n ((stop != 1) AND (stop != 0)) OR\n ((strt = 1) AND (stop = 0))) THEN\n RAISE_APPLICATION_ERROR(-20101,\n 'incorrect predicate for position_between operator');\n END IF;\n IF (lower_pos > upper_pos) THEN\n RAISE_APPLICATION_ERROR(-20101, 'Upper Position must be greater than or\nequal to Lower Position');\n END IF;\n IF (lower_pos <= 0) THEN\n RAISE_APPLICATION_ERROR(-20101, 'Both Positions must be greater than zero');\n END IF;\n storage_tab_name := ia.INDEXSCHEMA || '.' || ia.INDEXNAME ||\n '_STORAGE_TAB';\n upper_bound_stmt := 'Select MIN(col_val) FROM (Select /*+ INDEX_DESC(' ||\n storage_tab_name || ') */ DISTINCT ' ||\n 'col_val FROM ' || storage_tab_name || ' ORDER BY ' ||\n 'col_val DESC) WHERE rownum <= ' || lower_pos;\n EXECUTE IMMEDIATE upper_bound_stmt INTO upper_bound;\n IF (lower_pos != upper_pos) THEN\n lower_bound_stmt := 'Select MIN(col_val) FROM (Select /*+ INDEX_DESC(' ||\n storage_tab_name || ') */ DISTINCT ' ||\n 'col_val FROM ' || storage_tab_name || ' WHERE col_val < ' || upper_bound || ' ORDER BY ' ||\n 'col_val DESC) WHERE rownum <= ' || (upper_pos - lower_pos);\n EXECUTE IMMEDIATE lower_bound_stmt INTO lower_bound;\n ELSE\n lower_bound := upper_bound;\n END IF;\n IF (lower_bound IS NULL) THEN\n lower_bound := upper_bound;\n END IF;\n range_query_stmt := 'Select base_rowid FROM ' || storage_tab_name ||\n ' WHERE col_val BETWEEN ' || lower_bound || ' AND ' ||\n upper_bound;\n cnum := DBMS_SQL.OPEN_CURSOR;\n DBMS_SQL.PARSE(cnum, range_query_stmt, DBMS_SQL.NATIVE);\n/* set context as the cursor number */\n SCTX := position_im(cnum, 0, 0, 0);\n/* return success */\n RETURN ODCICONST.SUCCESS;\n\nThe next step is to create the functional implementation `function_for_position_between` for the operator that will be associated with the indextype. (The PL/SQL blocks are shown in parentheses.)\n\nThis function is for use with an index-based function evaluation. Therefore, it takes an index context and scan context as parameters.\n\n**See Also:**\n\n- *Oracle Database Data Cartridge Developer’s Guide* for information on creating index-based functional implementation\n\n- **CREATE FUNCTION** on page 14-59 and *Oracle Database PL/SQL Language Reference*\n\n```sql\nCREATE OR REPLACE FUNCTION function_for_position_between\n(col NUMBER, lower_pos NUMBER, upper_pos NUMBER,\nindexctx IN SYS.ODCIIndexCtx,\nscanctx IN OUT position_im,\nscanflg IN NUMBER)\nRETURN NUMBER AS\n rid ROWID;\nstorage_tab_name VARCHAR2(65);\n```\n\nlower_bound_stmt VARCHAR2(2000);\nupper_bound_stmt VARCHAR2(2000);\ncol_val_stmt VARCHAR2(2000);\nlower_bound NUMBER;\nupper_bound NUMBER;\ncolumn_value NUMBER;\n\nBEGIN\n IF (indexctx.IndexInfo IS NOT NULL) THEN\n storage_tab_name := indexctx.IndexInfo.INDEXSCHEMA || '.' ||\n indexctx.IndexInfo.INDEXNAME || '_STORAGE_TAB';\n END IF;\n IF (scanctx IS NULL) THEN\n /* This is the first call. Open a cursor for future calls.\n First, do some error checking */\n IF (lower_pos > upper_pos) THEN\n RAISE_APPLICATION_ERROR(-20101,\n 'Upper Position must be greater than or equal to Lower Position');\n END IF;\n IF (lower_pos <= 0) THEN\n RAISE_APPLICATION_ERROR(-20101,\n 'Both Positions must be greater than zero');\n END IF;\n /* Obtain the upper and lower value bounds for the range we're interested in.\n */\n upper_bound_stmt := 'Select MIN(col_val) FROM (Select /*+ INDEX_DESC('' || '\n storage_tab_name || '') */ DISTINCT ' || '\n 'col_val FROM ' || storage_tab_name || ' ORDER BY ' || '\n 'col_val DESC) WHERE rownum <= ' || lower_pos;\n EXECUTE IMMEDIATE upper_bound_stmt INTO upper_bound;\n IF (lower_pos != upper_pos) THEN\n lower_bound_stmt := 'Select MIN(col_val) FROM (Select /*+ INDEX_DESC('' || '\n storage_tab_name || '') */ DISTINCT ' || '\n 'col_val FROM ' || storage_tab_name || '\n WHERE col_val < ' || upper_bound || ' ORDER BY ' || '\n 'col_val DESC) WHERE rownum <= ' || \n (upper_pos - lower_pos);\n EXECUTE IMMEDIATE lower_bound_stmt INTO lower_bound;\n ELSE\n lower_bound := upper_bound;\n END IF;\n IF (lower_bound IS NULL) THEN\n lower_bound := upper_bound;\n END IF;\n /* Store the lower and upper bounds for future function invocations for\n the positions.\n */\n scanctx := position_im(0, 0, lower_bound, upper_bound);\n END IF;\n /* Fetch the column value corresponding to the rowid, and see if it falls\n within the determined range.\n */\n col_val_stmt := 'Select col_val FROM ' || storage_tab_name || '\n WHERE base_rowid = '''' || indexctx.Rid || '''';\n EXECUTE IMMEDIATE col_val_stmt INTO column_value;\n IF (column_value <= scanctx.upper_bound AND\n column_value >= scanctx.lower_bound AND\n scanflg = ODCICONST.RegularCall) THEN\n RETURN 1;\n ELSE\n RETURN 0;\n\nEND IF;\nELSE\n RAISE_APPLICATION_ERROR(-20101, 'A column that has a domain index of' ||\n 'Position indextype must be the first argument');\nEND IF;\nEND;\n/\n\nNext, create the position_between operator, which uses the function_for_position_between function. The operator takes an indexed NUMBER column as the first argument, followed by a NUMBER lower and upper bound as the second and third arguments.\n\nSee Also: CREATE OPERATOR on page 15-34\n\nCREATE OR REPLACE OPERATOR position_between\n BINDING (NUMBER, NUMBER, NUMBER) RETURN NUMBER\n WITH INDEX CONTEXT, SCAN CONTEXT position_im\n USING function_for_position_between;\n\nIn this CREATE OPERATOR statement, the WITH INDEX CONTEXT, SCAN CONTEXT position_im clause is included so that the index context and scan context are passed in to the functional evaluation, which is index based.\n\nNow create the position_indextype indextype for the position_operator:\n\nSee Also: CREATE INDEXTYPE on page 14-87\n\nCREATE INDEXTYPE position_indextype\n FOR position_between(NUMBER, NUMBER, NUMBER)\n USING position_im;\n\nThe operator position_between uses an index-based functional implementation. Therefore, a domain index must be defined on the referenced column so that the index information can be passed into the functional evaluation. So the final step is to create the domain index salary_index using the position_indextype indextype:\n\nSee Also: CREATE INDEX on page 14-61\n\nCREATE INDEX salary_index ON employees(salary)\n INDEXTYPE IS position_indextype;\n\nNow you can use the position_between operator function to rewrite the original query as follows:\n\nSELECT last_name, salary FROM employees\n WHERE position_between(salary, 10, 20)=1\n ORDER BY salary DESC, last_name;\n\n| LAST_NAME | SALARY |\n|-----------|--------|\n| Tucker | 10000 |\n| King | 10000 |\n| Baer | 10000 |\n| Bloom | 10000 |\n| Fox | 9600 |\n| Bernstein | 9500 |\n| Sully | 9500 |\n| Greene | 9500 |\n\nUsing XML in SQL Statements\n\nThis section describes some of the ways you can use XMLType data in the database.\n\nXMLType Tables\n\nThe sample schema oe contains a table warehouses, which contains an XMLType column warehouse_spec. Suppose you want to create a separate table with the warehouse_spec information. The following example creates a very simple XMLType table with one implicit CLOB column:\n\n```sql\nCREATE TABLE xwarehouses OF XMLTYPE;\n```\n\nYou can insert into such a table using XMLType syntax, as shown in the next statement. (The data inserted in this example corresponds to the data in the warehouse_spec column of the sample table oe.warehouses where warehouse_id = 1.)\n\n```sql\nINSERT INTO xwarehouses VALUES\n(xmltype('<?xml version=\"1.0\"?>\n<Warehouse>\n <WarehouseId>1</WarehouseId>\n <WarehouseName>Southlake, Texas</WarehouseName>\n <Building>Owned</Building>\n <Area>25000</Area>\n <Docks>2</Docks>\n <DockType>Rear load</DockType>\n <WaterAccess>true</WaterAccess>\n <RailAccess>N</RailAccess>\n <Parking>Street</Parking>\n <VClearance>10</VClearance>\n</Warehouse>');\n```\n\n**See Also:** Oracle XML DB Developer’s Guide for information on XMLType and its member methods\n\nYou can query this table with the following statement:\n\n```sql\nSELECT e.getClobVal() FROM xwarehouses e;\n```\n\nBecause Oracle implicitly stores the data in a CLOB column, it is subject to all of the restrictions on LOB columns. To avoid these restrictions, create an XMLSchema-based table. The XMLSchema maps the XML elements to their object-relational equivalents. The following example registers an XMLSchema locally. The XMLSchema (xwarehouses.xsd) reflects the same structure as the xwarehouses table.\n\n(XMLSchema declarations use PL/SQL and the DBMS_XMLSCHEMA package, so the example is shown in italics.)\n\n**See Also:** Oracle XML DB Developer’s Guide for information on creating XMLSchemas\n\n```sql\nbegin\n dbms_xmlschema.registerSchema(\n 'http://www.example.com/xwarehouses.xsd',\n '<schema xmlns=\"http://www.w3.org/2001/XMLSchema\"\n targetNamespace=\"http://www.example.com/xwarehouses.xsd\"\n xmlns:who=\"http://www.example.com/xwarehouses.xsd\"\n version=\"1.0\">\n <simpleType name=\"RentalType\">\n <restriction base=\"string\">\n <enumeration value=\"Rented\"/>\n <enumeration value=\"Owned\"/>\n </restriction>\n </simpleType>\n\n <simpleType name=\"ParkingType\">\n <restriction base=\"string\">\n <enumeration value=\"Street\"/>\n <enumeration value=\"Lot\"/>\n </restriction>\n </simpleType>\n\n <element name = \"Warehouse\">\n <complexType>\n <sequence>\n <element name = \"WarehouseId\" type = \"positiveInteger\"/>\n <element name = \"WarehouseName\" type = \"string\"/>\n <element name = \"Building\" type = \"who:RentalType\"/>\n <element name = \"Area\" type = \"positiveInteger\"/>\n <element name = \"Docks\" type = \"positiveInteger\"/>\n <element name = \"DockType\" type = \"string\"/>\n <element name = \"WaterAccess\" type = \"boolean\"/>\n <element name = \"RailAccess\" type = \"boolean\"/>\n <element name = \"Parking\" type = \"who:ParkingType\"/>\n <element name = \"VClearance\" type = \"positiveInteger\"/>\n </sequence>\n </complexType>\n </element>\n </schema>',\n TRUE, TRUE, FALSE, FALSE);\nend;\n/\n```\n\nNow you can create an XMLSchema-based table, as shown in the following example:\n\n```sql\nCREATE TABLE xwarehouses OF XMLTYPE\n XMLSCHEMA \"http://www.example.com/xwarehouses.xsd\"\n ELEMENT \"Warehouse\";\n```\n\nBy default, Oracle stores this as an object-relational table. Therefore, you can insert into it as shown in the example that follows. (The data inserted in this example corresponds to the data in the warehouse_spec column of the sample table oe.warehouses where warehouse_id = 1.)\n\n```sql\nINSERT INTO xwarehouses VALUES(\n```\n\nxmltype.createxml('<?xml version=\"1.0\"?>\n<who:Warehouse xmlns:who=\"http://www.example.com/xwarehouses.xsd\"\nxmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\nxsi:schemaLocation=\"http://www.example.com/xwarehouses.xsd\nhttp://www.example.com/xwarehouses.xsd\">\n <WarehouseId>1</WarehouseId>\n <WarehouseName>Southlake, Texas</WarehouseName>\n <Building>Owned</Building>\n <Area>25000</Area>\n <Docks>2</Docks>\n <DockType>Rear load</DockType>\n <WaterAccess>true</WaterAccess>\n <RailAccess>false</RailAccess>\n <Parking>Street</Parking>\n <VClearance>10</VClearance>\n</who:Warehouse>');\n\n...\n\nYou can define constraints on an XMLSchema-based table. To do so, you use the XMLDATA pseudocolumn to refer to the appropriate attribute within the Warehouse XML element:\n\nALTER TABLE xwarehouses ADD (PRIMARY KEY(XMLDATA.\"WarehouseId\"));\n\nBecause the data in xwarehouses is stored object relationally, Oracle rewrites queries to this XMLType table to go to the underlying storage when possible. Therefore the following queries would use the index created by the primary key constraint in the preceding example:\n\nSELECT * FROM xwarehouses x\nWHERE EXISTSNODEx(VALUE(x), '/Warehouse[WarehouseId=\"1\"]') = 1,\n'xmlns:who=\"http://www.example.com/xwarehouses.xsd') = 1;\n\nSELECT * FROM xwarehouses x\nWHERE EXTRACTVALUE(VALUE(x), '/Warehouse/WarehouseId') = 1,\n'xmlns:who=\"http://www.example.com/xwarehouses.xsd') = 1;\n\nYou can also explicitly create indexes on XMLSchema-based tables, which greatly enhance the performance of subsequent queries. You can create object-relational views on XMLType tables, and you can create XMLType views on object-relational tables.\n\nSee Also:\n- XMLDATA Pseudocolumn on page 2-11 for information on the XMLDATA pseudocolumn\n- \"Creating an XMLType View: Example\" on page 17-25\n- Creating an Index on an XMLType Table: Example on page 14-81\n\nXMLType Columns\nThe sample table oe.warehouses was created with a warehouse_spec column of type XMLType. No storage was specified, so the XMLType column was implicitly stored as a CLOB. The examples in this section create a shortened form of the oe.warehouses table, using two different types of storage.\n\nThe first example creates a table with an XMLType table stored as a CLOB. This table does not require an XMLSchema, so the content structure is not predetermined:\n\nCREATE TABLE xwarehouses (\n warehouse_id NUMBER,\n warehouse_spec XMLTYPE)\n\nThe following example creates a similar table, but stores the XMLType data in an object-relational XMLType column whose structure is determined by the specified XMLSchema:\n\n```sql\nCREATE TABLE xwarehouses (\n warehouse_id NUMBER,\n warehouse_spec XMLTYPE)\nXMLTYPE warehouse_spec STORE AS OBJECT RELATIONAL\n XMLSCHEMA \"http://www.example.com/xwarehouses.xsd\"\n ELEMENT \"Warehouse\";\n```\n\nUsing XML in SQL Statements\n\nSymbols\n\n% (percent) used with LIKE operator, 7-16\n+ (plus sign) in Oracle Automatic Storage Management filenames, 8-32\n\nNumerics\n\n20th century, 3-64\n21st century, 3-64\n3GL functions and procedures, calling, 15-2\n\nA\n\nABORT LOGICAL STANDBY clause\n of ALTER DATABASE, 10-38\nABS function, 5-18\nACCESSED GLOBALLY clause\n of CREATE CONTEXT, 14-10\nACCOUNT LOCK clause\n of ALTER USER. See CREATE USER\n of CREATE USER, 17-12\nACCOUNT UNLOCK clause\n of ALTER USER. See CREATE USER\n of CREATE USER, 17-12\nACOS function, 5-18\nACTIVATE STANDBY DATABASE clause\n of ALTER DATABASE, 10-35\nAD and A.D. datetime format elements, 3-63\nADD clause\n of ALTER DIMENSION, 10-49\n of ALTER INDEXTYPE, 10-98\n of ALTER TABLE, 12-41\n of ALTER VIEW, 13-13\nADD DATAFILE clause\n of ALTER TABLESPACE, 12-95\nADD LOGFILE clause\n of ALTER DATABASE, 10-14\nADD LOGFILE GROUP clause\n of ALTER DATABASE, 10-31\nADD LOGFILE INSTANCE clause\n of ALTER DATABASE, 10-30\nADD LOGFILE MEMBER clause\n of ALTER DATABASE, 10-14, 10-31\nADD LOGFILE THREAD clause\n of ALTER DATABASE, 10-31\nADD OVERFLOW clause\n of ALTER TABLE, 12-39\nADD PARTITION clause\n of ALTER TABLE, 12-63, 12-64\nADD PRIMARY KEY clause\n of ALTER MATERIALIZED VIEW LOG, 11-22\nADD ROWID clause\n of ALTER MATERIALIZED VIEW, 11-22\nADD SUPPLEMENTAL LOG DATA clause\n of ALTER DATABASE, 10-32\nADD SUPPLEMENTAL LOG GROUP clause\n of ALTER TABLE, 12-34\nADD TEMPFILE clause\n of ALTER TABLESPACE, 12-95\nADD VALUES clause\n of ALTER TABLE ... MODIFY\n PARTITION, 12-60, 12-61\nADD_MONTHS function, 5-19\nadding a constraint to a table, 12-54\nADMINISTER ANY SQL TUNING SET system\n privilege, 18-39\nADMINISTER DATABASE TRIGGER system\n privilege, 18-45\nADMINISTER SQL MANAGEMENT OBJECT system\n privilege, 18-40, 18-43\nADMINISTER SQL TUNING SET system\n privilege, 18-39\nADVISE clause\n of ALTER SESSION, 11-46\nADVISOR system privilege, 18-39\naggregate functions, 5-10\nalias\n for a column, 9-2\n for an expressions in a view query, 17-18\n specifying in queries and subqueries, 19-21\nALL clause\n of SELECT, 19-15\n of SET CONSTRAINTS, 19-59\n of SET ROLE, 19-62\nALL EXCEPT clause\n of SET ROLE, 19-62\nALL operator, 7-5\nALL PRIVILEGES clause\n of GRANT, 18-37\n of REVOKE, 18-92\nALL PRIVILEGES shortcut\n\nof AUDIT, 13-30\nALL shortcut\n of AUDIT, 13-30\nALL_COL_COMMENTS data dictionary\n view, 13-45\nALL_INDEXTYPE_COMMENTS data dictionary\n view, 13-45\nALL_MVIEW_COMMENTS data dictionary\n view, 13-45\nALL_OPERATOR_COMMENTS data dictionary\n view, 13-45\nALL_ROWS hint, 3-77\nALL_TAB_COMMENTS data dictionary view, 13-45\nall-column wildcard, 19-15\nALLOCATE EXTENT clause\n of ALTER CLUSTER, 10-6, 10-7\n of ALTER INDEX, 10-84\n of ALTER MATERIALIZED VIEW, 11-7\n of ALTER TABLE, 12-35\nALLOW CORRUPTION clause\n of ALTER DATABASE ... RECOVER, 10-23\nALTER ANY CLUSTER system privilege, 18-40\nALTER ANY CUBE DIMENSION system\n privilege, 18-43\nALTER ANY CUBE system privilege, 18-42\nALTER ANY DIMENSION system privilege, 18-40\nALTER ANY INDEX system privilege, 18-41\nALTER ANY INDEXTYPE system privilege, 18-41\nALTER ANY LIBRARY system privilege, 18-41\nALTER ANY MATERIALIZED VIEW system\n privilege, 18-42\nALTER ANY MINING MODEL system\n privilege, 18-42\nALTER ANY OPERATOR system privilege, 18-43\nALTER ANY OUTLINE system privilege, 18-43\nALTER ANY PROCEDURE system privilege, 18-44\nALTER ANY ROLE system privilege, 18-44\nALTER ANY SEQUENCE system privilege, 18-44\nALTER ANY SQL PROFILE system privilege, 18-40\nALTER ANY TABLE system privilege, 18-45\nALTER ANY TRIGGER system privilege, 18-45\nALTER ANY TYPE system privilege, 18-46\nALTER CLUSTER statement, 10-5\nALTER DATABASE LINK system privilege, 18-40\nALTER DATABASE statement, 10-9\nALTER DATABASE system privilege, 18-40\nALTER DIMENSION statement, 10-48\nALTER DISKGROUP statement, 10-51\nALTER FLASHBACK ARCHIVE statement, 10-74\nALTER FUNCTION statement, 10-77\nALTER INDEX statement, 10-78\nALTER INDEXTYPE statement, 10-97\nALTER JAVA CLASS statement, 10-100\nALTER JAVA SOURCE statement, 10-100\nALTER LIBRARY statement, 11-2\nALTER MATERIALIZED VIEW LOG\n statement, 11-18\nALTER MATERIALIZED VIEW statement, 11-3\nALTER object privilege\n on a mining model, 18-49\n on a sequence, 18-50\n on a table, 18-50\n on an OLAP cube, 18-49\n on an OLAP cube dimension, 18-49\nALTER OPERATOR statement, 11-25\nALTER OUTLINE statement, 11-28\nALTER PACKAGE statement, 11-30\nALTER PROCEDURE statement, 11-31\nALTER PROFILE statement, 11-32\nALTER PROFILE system privilege, 18-44\nALTER PUBLIC DATABASE LINK system\n privilege, 18-40\nALTER RESOURCE COST statement, 11-35\nALTER RESOURCE COST system privilege, 18-44\nALTER ROLE statement, 11-38\nALTER ROLLBACK SEGMENT statement, 11-40\nALTER ROLLBACK SEGMENT system\n privilege, 18-44\nALTER SEQUENCE statement, 11-43\nALTER SESSION statement, 11-45\nALTER SESSION system privilege, 18-44\nALTER SNAPSHOT LOG. See ALTER\n MATERIALIZED VIEW LOG\nALTER SNAPSHOT. See ALTER MATERIALIZED\n VIEW\nALTER SYSTEM statement, 11-58\nALTER SYSTEM system privilege, 18-40\nALTER TABLE statement, 12-2\nALTER TABLESPACE statement, 12-90\nALTER TABLESPACE system privilege, 18-45\nALTER TRIGGER statement, 13-2\nALTER TYPE statement, 13-4\nALTER USER statement, 13-5\nALTER USER system privilege, 18-46\nALTER VIEW statement, 13-12\nalter_external_table clause\n of ALTER TABLE, 12-17\nAM and A.M. datetime format elements, 3-63\nAmerican National Standards Institute (ANSI), C-1\n data types, 3-28\n conversion to Oracle data types, 3-28\n standards, 1-1, C-1\n supported data types, 3-4\nanalytic functions, 5-11\nANALYZE ANY system privilege, 18-46\nANALYZE CLUSTER statement, 13-15\nANALYZE INDEX statement, 13-15\nANALYZE TABLE statement, 13-15\nANCILLARY TO clause\n of CREATE OPERATOR, 15-35\nAND condition, 7-8, 7-9\nAND DATAFILES clause\n of DROP TABLESPACE, 18-11\nANSI. See American National Standards Institute\n (ANSI)\nantijoins, 9-14\nANY operator, 7-5\nAPPEND hint, 3-78\nAPPEND_VALUES hint, 3-78\nAPPENDCHILDXML function, 5-19\n\napplication servers\n allowing connection as user, 13-9\n\napplications\n allowing connection as user, 13-9\n securing, 14-9\n validating, 14-9\n\nARCHIVE LOG clause\n of ALTER SYSTEM, 11-61\n\narchive mode\n specifying, 14-25\n\narchived redo logs\n location, 10-21\n\nARCHIVELOG clause\n of ALTER DATABASE, 10-14, 10-28\n of CREATE CONTROLFILE, 14-16\n of CREATE DATABASE, 14-25\n\narguments\n of operators, 4-1\n\narithmetic\n with DATE values, 3-20\n\narithmetic operators, 4-3\n\nAS source_char clause\n of CREATE JAVA, 14-94\n\nAS subquery clause\n of CREATE MATERIALIZED VIEW, 15-21\n of CREATE TABLE, 16-65\n of CREATE VIEW, 17-20\n\nASC clause\n of CREATE INDEX, 14-72\n\nASCII character set, 3-38\n\nASCII function, 5-20\n\nASCIISTR function, 5-21\n\nASIN function, 5-21\n\nASM_DISKGROUPS initialization parameter\n setting with ALTER SYSTEM, 10-70, 14-44\n\nASM_DISKSTRING initialization parameter\n setting with ALTER SYSTEM, 14-47\n\nASSOCIATE STATISTICS statement, 13-23\n\nasterisk\n all-column wildcard in queries, 19-15\n\nasynchronous commit, 13-48\n\nATAN function, 5-22\n\nATAN2 function, 5-22\n\nATTRIBUTE clause\n of ALTER DIMENSION, 10-49\n of CREATE DIMENSION, 14-38, 14-40\n\nattributes\n adding to a dimension, 10-49\n dropping from a dimension, 10-49\n maximum number of in object type, 16-26\n of dimensions, defining, 14-40\n of disk groups, 10-68, 14-47\n\nAUDIT ANY system privilege, 18-46\n\nAUDIT statement\n locks, B-5\n\nAUDIT SYSTEM system privilege, 18-40\n\nauditing\n options\n for SQL statements, 13-35\n policies\n value-based, 13-27\n\nSQL statements, 13-28\n by a proxy, 13-28\n by a user, 13-28\n on a directory, 13-29\n on a schema, 13-29\n stopping, 18-80\n system privileges, 13-28\n\nAUTHENTICATED BY clause\n of CREATE DATABASE LINK, 14-35\n\nAUTHENTICATED clause\n of ALTER USER, 13-10\n\nAUTHENTICATION REQUIRED clause\n of ALTER USER, 13-10\n\nAUTHID CURRENT_USER clause\n of ALTER JAVA, 10-101\n of CREATE JAVA, 14-92, 14-93\n\nAUTHID DEFINER clause\n of ALTER JAVA, 10-101\n of CREATE JAVA, 14-92, 14-93\n\nAUTOALLOCATE clause\n of CREATE TABLESPACE, 16-88\n\nAUTOEXTEND clause\n of ALTER DATABASE, 10-13\n of CREATE DATABASE, 14-21\n\nautomatic segment-space management, 16-89\n\nautomatic undo mode, 11-40, 14-28\n\nAVG function, 5-23\n\nB\n\nBACKUP ANY TABLE system privilege, 18-45\n\nBACKUP CONTROLFILE clause\n of ALTER DATABASE, 10-15, 10-34\n\nbackups, 10-40\n\nbasic table compression, 16-34\n\nBC and B.C. datetime format elements, 3-63\n\nBECOME USER system privilege, 18-47\n\nBEGIN BACKUP clause\n of ALTER DATABASE, 10-25\n of ALTER TABLESPACE, 12-95\n\nBETWEEN condition, 7-22\n\nBFILE\n data type, 3-26\n locators, 3-26\n\nBFILENAME function, 5-24\n\nBIN_TO_NUM function, 5-25\n\nbinary large objects. See BLOB\n\nbinary operators, 4-2\n\nbinary XML format, 16-49\n\nbinary XML storage, 16-50\n\nBINDING clause\n of CREATE OPERATOR, 15-34\n\nbindings\n adding to an operator, 11-26\n dropping from an operator, 11-27\n\nbit vectors\n converting to numbers, 5-25\n\nBITAND function, 5-26\n\nBITMAP clause\n\nof CREATE INDEX, 14-68\n\nbitmap indexes, 14-68\ncreating join indexes, 14-62\n\nblank padding\nspecifying in format models, 3-65\nsuppressing, 3-66\n\nBLOB data type, 3-26\ntransactional support, 3-26\n\nBLOCKSIZE clause\nof CREATE TABLESPACE, 16-86\n\nbottom-N reporting, 5-61, 5-153, 5-174\n\nbuffer cache\nflushing, 11-65\n\nBUFFER_POOL parameter\nof STORAGE clause, 8-55\n\nBUILD DEFERRED clause\nof CREATE MATERIALIZED VIEW, 15-15\n\nBUILD IMMEDIATE clause\nof CREATE MATERIALIZED VIEW, 15-15\n\nBY ACCESS clause\nof AUDIT, 13-32\n\nBY proxy clause\nof AUDIT, 13-31\n\nBY SESSION clause\nof AUDIT, 13-32\n\nBY user clause\nof AUDIT, 13-31\n\nBYTE character semantics, 3-9\n\nBYTE length semantics, 12-46\n\nC\n\nCACHE clause\nof ALTER MATERIALIZED VIEW, 11-11\nof ALTER MATERIALIZED VIEW LOG, 11-22\nof ALTER TABLE, 16-61\nof CREATE CLUSTER, 14-7\nof CREATE MATERIALIZED VIEW, 15-15\nof CREATE MATERIALIZED VIEW LOG, 15-29\n\nCACHE hint, 3-79\n\nCACHE parameter\nof ALTER SEQUENCE. See CREATE\nSEQUENCE, 11-43\nof CREATE SEQUENCE, 15-68\n\nCACHE READS clause\nof ALTER TABLE, 12-44\nof CREATE TABLE, 16-61\n\ncached cursors\nexecution plan for, 18-20\n\ncall spec. See call specifications\n\ncall specifications\nin procedures, 15-47\n\nCALL statement, 13-40\n\ncalls\nlimiting CPU time for, 15-51\nlimiting data blocks read, 15-52\n\nCARDINALITY function, 5-28\n\nCartesian products, 9-12\n\nCASCADE clause\nof CREATE TABLE, 16-64\nof DROP PROFILE, 17-64\nof DROP USER, 18-16\n\nCASCADE CONSTRAINTS clause\nof DROP CLUSTER, 17-37\nof DROP TABLE, 18-7\nof DROP TABLESPACE, 18-11\nof DROP VIEW, 18-18\nof REVOKE, 18-92\n\nCASE expressions, 6-5\nsearched, 6-5\nsimple, 6-5\n\nCAST function, 5-28\n\nCATSEARCH condition, 7-2\n\nCATSEARCH operator, 4-1\n\nCEIL function, 5-31\n\nchained rows\nlisting, 13-20\nof clusters, 13-18\n\nCHANGE CATEGORY clause\nof ALTER OUTLINE, 11-29\n\nCHANGE NOTIFICATION system privilege, 18-47\n\nCHANGE_DUPKEY_ERROR_INDEX hint, 3-79\n\nCHAR character semantics, 3-9\n\nCHAR data type, 3-9\nconverting to VARCHAR2, 3-56\n\nCHAR length semantics, 12-46\n\ncharacter functions\nreturning character values, 5-4\nreturning number values, 5-5\n\ncharacter large objects. See CLOB\n\ncharacter length semantics, 12-46\n\ncharacter literal. See text\n\ncharacter set\nchanging, 10-39\n\nCHARACTER SET parameter\nof CREATE CONTROLFILE, 14-17\nof CREATE DATABASE, 14-23\n\ncharacter sets\ncommon, 3-37\ndatabase, specifying, 14-23\nmultibyte characters, 3-110\nspecifying for database, 14-23\n\ncharacter strings\ncomparison rules, 3-37\nexact matching, 3-66\nfixed-length, 3-9\nnational character set, 3-9\nvariable-length, 3-10, 3-14\nzero-length, 3-9\n\nCHARTOROWID function, 5-31\n\nCHECK clause\nof constraints, 8-11\nof CREATE TABLE, 16-30\n\ncheck constraints, 8-11\n\nCHECK DATAFILES clause\nof ALTER SYSTEM, 11-63\n\nCHECKPOINT clause\nof ALTER SYSTEM, 11-63\n\ncheckpoints\nforcing, 11-63\n\nCHR function, 5-32\n\nCHUNK clause\n of ALTER TABLE, 12-44\n of CREATE TABLE, 16-44\n\nCLEAR LOGFILE clause\n of ALTER DATABASE, 10-14, 10-29\n\nCLOB data type, 3-26\n transactional support, 3-26\n\nclone databases\n mounting, 10-19\n\nCLOSE DATABASE LINK clause\n of ALTER SESSION, 11-46\n\nCLUSTER clause\n of ANALYZE, 13-18\n of CREATE INDEX, 14-69\n of CREATE TABLE, 16-41\n of TRUNCATE, 19-66\n\nCLUSTER hint, 3-80\n\nCLUSTER_ID function, 5-33\n\nCLUSTER_PROBABILITY function, 5-35\n\nCLUSTER_SET function, 5-36\n\nclusters\n assigning tables to, 16-41\n caching retrieved blocks, 14-7\n cluster indexes, 14-69\n collecting statistics on, 13-18\n creating, 14-2\n\ndeallocating unused extents, 10-6\n\ndegree of parallelism\n changing, 10-6, 10-7\n when creating, 14-6\n\ndropping tables, 17-36\n\nextents, allocating, 10-6, 10-7\n\ngranting system privileges for, 18-40\n\nhash, 14-5\n single-table, 14-6\n sorted, 14-4, 16-27\n\nindexed, 14-5\n\nkey values\n allocating space for, 14-5\n modifying space for, 10-6\n\nmigrated and chained rows in, 13-18, 13-20\n\nmodifying, 10-5\n\nphysical attributes\n changing, 10-5\n specifying, 14-4\n\nreleasing unused space, 10-7\n\nremoving from the database, 17-36\n\nSQL examples, 17-37\n\nstorage attributes\n changing, 10-5\n\nstorage characteristics\n changing, 10-6\n\ntablespace in which created, 14-5\n\nvalidating structure, 13-19\n\nCOALESCE clause\n for partitions, 12-65\n of ALTER INDEX, 10-91\n of ALTER TABLE, 12-39, 12-41, 12-59\n of ALTER TABLESPACE, 12-94\n\nCOALESCE function, 5-38\n as a variety of CASE expression, 5-38\n\nCOALESCE SUBPARTITION clause\n of ALTER TABLE, 12-59\n\nCOLLECT function, 5-39\n\ncollection functions, 5-7\n\ncollection types\n multilevel, 16-48\n\ncollections\n inserting rows into, 18-60\n modifying, 12-52\n modifying retrieval method, 12-10\n nested tables, 3-31\n testing for empty, 7-12\n treating as a table, 18-60, 19-20, 19-74, 19-76\n unnesting, 19-20\n examples, 19-54\n\n varrays, 3-30\n\ncollection-typed values\n converting to data types, 5-28\n\ncolumn expressions, 6-6\n\ncolumn REF constraints, 8-12\n of CREATE TABLE, 16-30\n\ncolumn values\n unpivoting into rows, 19-22\n\nCOLUMN_VALUE pseudocolumn, 2-6\n\ncolumns\n adding, 12-41\n aliases for, 9-2\n altering storage, 12-43\n associating statistics types with, 13-23\n basing an index on, 14-70\n comments on, 13-45\n creating comments about, 13-44\n defining, 16-6\n disassociating statistics types from, 17-34\n dropping from a table, 12-48\n\nLOB\n storage attributes, 12-44\n maximum number of, 16-26\n\nmodifying existing, 12-45\n\nparent-child relationships between, 14-37\n\nproperties, altering, 12-11, 12-43\n\nqualifying names of, 9-2\n\nREF\n describing, 8-12\n renaming, 12-51\n restricting values for, 8-4\n\nspecifying\n as primary key, 8-9\n constraints on, 16-30\n default values, 16-27\n\nstorage properties, 16-41\n\nsubstitutable, identifying type, 5-209\n\nvirtual\n adding to a table, 12-42\n creating, 16-28\n modifying, 12-42\n\nCOLUMNS clause\n of ASSOCIATE STATISTICS, 13-23, 13-24\n\nof DISASSOCIATE STATISTICS, 17-34\n\nCOMMENT ANY MINING MODEL system privilege, 18-42\n\nCOMMENT ANY TABLE system privilege, 18-47\n\nCOMMENT clause\n of COMMIT, 13-48\n\nCOMMENT statement, 13-44\n\ncomments, 3-71\n adding to objects, 13-44\n associating with a transaction, 13-49\n dropping from objects, 13-44\n in SQL statements, 3-71\n on indextypes, 13-45\n on operators, 13-45\n on schema objects, 3-72\n on table columns, 13-45\n on tables, 13-45\n removing from the data dictionary, 13-44\n specifying, 3-71\n viewing, 13-45\n\ncommit\n asynchronous, 13-48\n automatic, 13-47\n\nCOMMIT IN PROCEDURE clause\n of ALTER SESSION, 11-46\n\nCOMMIT statement, 13-47\n\nCOMMIT TO SWITCHOVER clause\n of ALTER DATABASE, 10-36\n\ncomparison conditions, 7-4\n\ncomparison functions, 5-6\n\ncomparison semantics\n of character strings, 3-37\n\nCOMPILE clause\n of ALTER DIMENSION, 10-50\n of ALTER JAVA SOURCE, 10-101\n of ALTER MATERIALIZED VIEW, 11-15\n of ALTER VIEW, 13-14\n of CREATE JAVA, 14-92\n\nCOMPOSE function, 5-40\n\ncomposite foreign keys, 8-10\n\ncomposite partitioning\n range-list, 12-59, 16-59\n when creating a table, 16-22, 16-56\n\ncomposite primary keys, 8-9\n\ncomposite range partitions, 16-56\n\nCOMPOSITE_LIMIT parameter\n of ALTER PROFILE, 11-32\n of CREATE PROFILE, 15-52\n\ncompound conditions, 7-21\n\ncompound expressions, 6-4\n\nCOMPRESS clause\n of ALTER INDEX... REBUILD, 10-88\n of CREATE TABLE, 16-38\n\ncompression\n of index keys, 10-81\n of tables, 16-34\n of tablespaces, 16-34\n\nCONCAT function, 5-40\n\nconcatenation operator, 4-4\n\nconditions\n BETWEEN, 7-22\n comparison, 7-4\n compound, 7-21\n EXISTS, 7-20, 7-22\n floating-point, 7-7\n group comparison, 7-6\n IN, 7-23\n in SQL syntax, 7-1\n interval, 7-22\n IS [NOT] EMPTY, 7-12\n IS ANY, 7-9\n IS OF type, 7-25\n IS PRESENT, 7-10\n LIKE, 7-14\n logical, 7-8\n MEMBER, 7-13\n membership, 7-13, 7-23\n model, 7-9\n multiset, 7-11\n null, 7-19\n pattern matching, 7-14\n range, 7-22\n REGEXP_LIKE, 7-18\n SET, 7-12\n simple comparison, 7-5\n SUBMULTISET, 7-13\n UNDER_PATH, 7-21\n XML, 7-20\n\nCONNECT BY clause\n of queries and subqueries, 19-26\n of SELECT, 9-4, 19-26\n\nCONNECT clause\n of SELECT and subqueries, 19-10\n\nCONNECT THROUGH clause\n of ALTER USER, 13-9\n\nCONNECT 'TO' clause\n of CREATE DATABASE LINK, 14-34\n\nCONNECT_BY_ISCYCLE pseudocolumn, 2-1\n\nCONNECT_BY_ISLEAF pseudocolumn, 2-2\n\nCONNECT_BY_ROOT operator, 4-5\n\nCONNECT_TIME parameter\n of ALTER PROFILE, 11-32\n of ALTER RESOURCE COST, 11-35\n\nconnection qualifier, 3-115\n\nCONSIDER FRESH clause\n of ALTER MATERIALIZED VIEW, 11-15\n\nconstant values. See literals\n\nCONSTRAINT(S) session parameter, 11-51\n\nconstraints\n adding to a table, 12-54\n altering, 12-11\n check, 8-11\n checking\n at end of transaction, 8-14\n at start of transaction, 8-15\n at the end of each DML statement, 8-14\n\ncolumn REF, 8-12\n\ndeferrable, 8-14, 19-59\n enforcing, 11-51\n defining, 8-4, 16-6\n\nfor a table, 16-30\non a column, 16-30\ndisabling, 16-63\nafter table creation, 12-78\ncascading, 16-64\nduring table creation, 16-24\ndropping, 12-11, 12-54, 18-11\nenabling, 16-63\nafter table creation, 12-78\nduring table creation, 16-24\nforeign key, 8-10\nmodifying existing, 12-54\non views\ndropping, 13-13, 18-18\npartitioning referential, 12-54, 16-56\nprimary key, 8-9\nattributes of index, 8-17\nenabling, 16-63\nreferential integrity, 8-10\nrenaming, 12-54\nrestrictions, 8-8\nsetting state for a transaction, 19-59\nstoring rows in violation, 12-72\ntable REF, 8-12\nunique\nattributes of index, 8-17\nenabling, 16-63\n\nCONTAINS condition, 7-2\nCONTAINS operator, 4-1\n\ncontext namespaces\naccessible to instance, 14-10\nassociating with package, 14-9\ninitializing using OCI, 14-10\ninitializing using the LDAP directory, 14-10\nremoving from the database, 17-38\n\ncontexts\ncreating namespaces for, 14-9\ngranting system privileges for, 18-40\n\ncontrol file clauses\nof ALTER DATABASE, 10-15\n\ncontrol files\nallowing reuse, 14-14, 14-22\nbacking up, 10-34\nforce logging mode, 14-17\nre-creating, 14-12\nstandby, creating, 10-33\n\nCONTROLFILE REUSE clause\nof CREATE DATABASE, 14-22\n\nconversion\nfunctions, 5-6\nrules, string to date, 3-68\n\nCONVERT function, 5-41\n\nCORR function, 5-43\nCORR_K function, 5-46\nCORR_S function, 5-45\n\ncorrelated subqueries, 9-14\n\ncorrelation functions\nKendall’s tau-b, 5-44\nPearson’s, 5-43\nSpearman’s rho, 5-44\n\ncorrelation names\nfor base tables of indexes, 14-70\nin DELETE, 17-31\nin SELECT, 19-21\n\nCOS function, 5-46\nCOSH function, 5-47\nCOUNT function, 5-47\nCOVAR_POP function, 5-49\nCOVAR_SAMP function, 5-50\n\nCPU_PER_CALL parameter\nof ALTER PROFILE, 11-32\nof CREATE PROFILE, 15-51\n\nCPU_PER_SESSION parameter\nof ALTER PROFILE, 11-32\nof ALTER RESOURCE COST, 11-35\nof CREATE PROFILE, 15-51\n\nCREATE ANY CLUSTER system privilege, 18-40\nCREATE ANY CONTEXT system privilege, 18-40\nCREATE ANY CUBE BUILD PROCESS system\nprivilege, 18-43\nCREATE ANY CUBE DIMENSION system\nprivilege, 18-43\nCREATE ANY CUBE system privilege, 18-42\nCREATE ANY DIMENSION system privilege, 18-40\nCREATE ANY DIRECTORY system privilege, 18-41\nCREATE ANY INDEX system privilege, 18-41\nCREATE ANY INDEXTYPE system privilege, 18-41\nCREATE ANY JOB system privilege, 18-41\nCREATE ANY LIBRARY system privilege, 18-41\nCREATE ANY MATERIALIZED VIEW system\nprivilege, 18-42\nCREATE ANY MEASURE FOLDER system\nprivilege, 18-43\nCREATE ANY MINING MODEL system\nprivilege, 18-42\nCREATE ANY OPERATOR system privilege, 18-43\nCREATE ANY OUTLINE system privilege, 18-43\nCREATE ANY PROCEDURE system\nprivilege, 18-44\nCREATE ANY SEQUENCE system privilege, 18-44\nCREATE ANY SQL PROFILE system\nprivilege, 18-39\nCREATE ANY SYNONYM system privilege, 18-44\nCREATE ANY TABLE system privilege, 18-45\nCREATE ANY TRIGGER system privilege, 18-45\nCREATE ANY TYPE system privilege, 18-45\nCREATE ANY VIEW system privilege, 18-46\nCREATE CLUSTER statement, 14-2\nCREATE CLUSTER system privilege, 18-40\nCREATE CONTEXT statement, 14-9\nCREATE CONTROLFILE statement, 14-12\nCREATE CUBE BUILD PROCESS system\nprivilege, 18-43\nCREATE CUBE DIMENSION system\nprivilege, 18-43\nCREATE CUBE system privilege, 18-42\nCREATE DATABASE LINK statement, 14-32\nCREATE DATABASE LINK system privilege, 18-40\nCREATE DATABASE statement, 14-19\nCREATE DATAFILE clause\n\nof ALTER DATABASE, 10-12, 10-26\nCREATE DIMENSION statement, 14-37\nCREATE DIMENSION system privilege, 18-40\nCREATE DIRECTORY statement, 14-42\nCREATE DISKGROUP statement, 14-44\nCREATE EXTERNAL JOB system privilege, 18-41\nCREATE FLASHBACK ARCHIVE statement, 14-56\nCREATE FUNCTION statement, 14-59\nCREATE INDEX statement, 14-61\nCREATE INDEXTYPE statement, 14-87\nCREATE INDEXTYPE system privilege, 18-41\nCREATE JAVA statement, 14-91\nCREATE JOB system privilege, 18-41\nCREATE LIBRARY statement, 15-2\nCREATE LIBRARY system privilege, 18-41\nCREATE MATERIALIZED VIEW LOG statement, 15-26\nCREATE MATERIALIZED VIEW statement, 15-3\nCREATE MATERIALIZED VIEW system privilege, 18-42\nCREATE MEASURE FOLDER system privilege, 18-43\nCREATE MINING MODEL system privilege, 18-42\nCREATE OPERATOR statement, 15-34\nCREATE OPERATOR system privilege, 18-43\nCREATE OUTLINE statement, 15-37\nCREATE PACKAGE BODY statement, 15-43\nCREATE PACKAGE statement, 15-41 locks, B-5\nCREATE PFILE statement, 15-45\nCREATE PROCEDURE statement, 15-47 locks, B-5\nCREATE PROCEDURE system privilege, 18-44\nCREATE PROFILE statement, 15-49\nCREATE PROFILE system privilege, 18-44\nCREATE PUBLIC DATABASE LINK system privilege, 18-40\nCREATE PUBLIC SYNONYM system privilege, 18-44\nCREATE RESTORE POINT statement, 15-55\nCREATE ROLE statement, 15-58\nCREATE ROLE system privilege, 18-44\nCREATE ROLLBACK SEGMENT statement, 15-61\nCREATE ROLLBACK SEGMENT system privilege, 18-44\nCREATE SCHEMA statement, 15-64\nCREATE SEQUENCE statement, 15-66\nCREATE SEQUENCE system privilege, 18-44\nCREATE SESSION system privilege, 18-44\nCREATE SPFILE statement, 15-70\nCREATE STANDBY CONTROLFILE clause of ALTER DATABASE, 10-15, 10-33\nCREATE SYNONYM statement, 16-2\nCREATE SYNONYM system privilege, 18-44\nCREATE TABLE statement, 16-6\nCREATE TABLE system privilege, 18-45\nCREATE TABLESPACE statement, 16-81\nCREATE TABLESPACE system privilege, 18-45\nCREATE TRIGGER statement, 16-95\nCREATE TRIGGER system privilege, 18-45\n\nCREATE TYPE BODY statement, 17-5\nCREATE TYPE statement, 17-3\nCREATE TYPE system privilege, 18-45\nCREATE USER statement, 17-7\nCREATE USER system privilege, 18-46\nCREATE VIEW statement, 17-14\nCREATE VIEW system privilege, 18-46\ncross joins, 19-23\nCUBE clause of SELECT statements, 19-27\nCUBE_TABLE function, 5-51\ncubes extracting data, 5-51\nCUME_DIST function, 5-52\ncumulative distributions, 5-52\ncurrency group separators, 3-57\ncurrency symbol ISO, 3-57 local, 3-57 union, 3-58\nCURRENT_DATE function, 5-54\nCURRENT_SCHEMA session parameter, 11-51\nCURRENT_TIMESTAMP function, 5-54\nCURRENT_USER clause of CREATE DATABASE LINK, 14-34\nCURRVAL pseudocolumn, 2-3, 15-66\nCURSOR expressions, 6-7\nCURSOR_SHARING_EXACT hint, 3-80\ncursors cached, 18-20\nCV function, 5-55\nCYCLE parameter of ALTER SEQUENCE. See CREATE SEQUENCE, 11-43 of CREATE SEQUENCE, 15-68\n\nD\n\ndata aggregation composite columns of GROUP BY, 19-28 concatenated grouping sets of GROUP BY, 19-28 grouping sets, 19-28 analyzing a subset, 5-130 caching frequently used, 16-61 independence, 16-2 integrity checking on input, 3-11 locks on, B-1 pivoting, 19-21 retrieving, 9-1 specifying as temporary, 16-25 undo preserving, 12-100, 16-92 unpivoting, 19-22\ndata cartridge functions, 5-17\ndata conversion, 3-40 between character data types, 3-42 implicit\n\ndisadvantages, 3-40\nimplicit versus explicit, 3-40\nwhen performed implicitly, 3-40, 3-42\nwhen specified explicitly, 3-43\n\ndata definition language\nlocks, B-4\n\ndata definition language (DDL)\nstatements, 10-2\nand implicit commit, 10-2\ncausing recompilation, 10-2\nPL/SQL support, 10-2\nstatements requiring exclusive access, 10-2\n\ndata dictionary\nadding comments to, 13-44\nlocks, B-4\n\ndata files\nbringing online, 10-27\nchanging size of, 10-27\ncreating new, 10-26\ndefining for a tablespace, 16-82, 16-83, 16-84\ndefining for the database, 14-22\ndesigning media recovery, 10-20\ndropping, 12-96\nenabling autoextend, 8-35\nend online backup of, 10-27, 12-95\nextending automatically, 8-35\nputting online, 10-27\nrecover damaged, 10-20\nrecovering, 10-22\nre-creating lost or damaged, 10-26\nrenaming, 10-26\nresizing, 10-28\nreusing, 8-35\nsize of, 8-34\nspecifying, 8-29\nfor a tablespace, 16-85\nfor database, 14-29\nsystem generated, 10-26\ntaking offline, 10-27\ntemporary\nshrinking, 12-96\n\ndata manipulation language (DML)\nallowing during indexing, 10-86\noperations\nduring index creation, 14-74\nduring index rebuild, 12-76\nrestricting, 11-67\nparallelizing, 16-62\nretrieving rows affected by, 17-31, 18-62, 19-78\nstatements, 10-2\nPL/SQL support, 10-3\n\ndata mining functions, 5-7\n\ndata types 3-1\n\"Any\" types, 3-31\nANSI-supported, 3-4\nBFILE, 3-26\nBLOB, 3-26\nCHAR, 3-9\ncharacter, 3-8\nCLOB, 3-26\ncomparison rules, 3-37\nconverting to collection-typed values, 5-28\nconverting to other data types, 5-28\nDATE, 3-17\ndatetime, 3-16\ninterval, 3-16\nINTERVAL DAY TO SECOND, 3-20\nINTERVAL YEAR TO MONTH, 3-19\nlength semantics, 3-9\nLONG, 3-14\nLONG RAW, 3-24\nmedia types, 3-35\nNCHAR, 3-9\nNCLOB, 3-27\nNUMBER, 3-10\nNVARCHAR2, 3-9\nOracle-supplied types, 3-31\nRAW, 3-24\nROWID, 3-27\nSDO_TOPO_GEOMETRY, 3-34\nspatial types, 3-34\nTIMESTAMP, 3-18\nTIMESTAMP WITH LOCAL TIME ZONE, 3-19\nTIMESTAMP WITH TIME ZONE, 3-18\nUROWID, 3-28\nuser-defined, 3-30\nVARCHAR, 3-10\nVARCHAR2, 3-10\nXML types, 3-32\n\ndatabase links, 9-16\naltering, 10-46\nclosing, 11-46\ncreating, 3-115, 14-32\ncreating synonyms with, 16-4\ncurrent user, 14-34\ngranting system privileges for, 18-40\nnaming, 3-115\npublic, 14-33\ndropping, 17-40\nreferring to, 3-116\nremoving from the database, 17-40\nshared, 14-33\nsyntax, 3-115\nupdating passwords, 10-46\nusername and password, 3-115\n\ndatabase objects\ndropping, 18-16\nnonschema, 3-107\nschema, 3-107\n\nDatabase Smart Flash Cache, 8-55\n\ndatabase triggers. See triggers\n\ndatabases\naccounts\ncreating, 17-7\nallowing changes to, 11-46\nallowing generation of redo logs, 10-19\nallowing reuse of control files, 14-22\nallowing unlimited resources to users, 15-51\narchive mode, specifying, 14-25\nbeginning backup of, 10-25\n\nblocks\n specifying size, 16-86\ncancel-based recovery, 10-22\n terminating, 10-23\nchange-based recovery, 10-22\nchanging characteristics, 14-12\nchanging global name, 10-40\nchanging name, 14-12, 14-14\ncharacter set, specifying, 14-23\ncommitting to standby status, 10-36\nconnect strings, 3-115\nconsistency-based recovery, 10-22\ncontrolling use, 10-42\ncreate script for, 10-33\ncreating, 14-19\ndata files\n modifying, 10-26\n specifying, 14-29\ndefault edition, setting, 10-38\ndesigning media recovery, 10-20\ndropping, 17-39\nending backup of, 10-25\nerasing all data from, 14-19\nflashing back, 18-24\ngranting system privileges for, 18-40\nin FLASHBACK mode, 10-41\nin FORCE LOGGING mode, 10-29, 14-17, 14-25\ninstances of, 14-23\nlimiting resources for users, 15-49\nlog files\n modifying, 10-28\n specifying, 14-23\nmanaged recovery, 10-12\nmodifying, 10-9\nmounting, 10-19, 14-19\nmoving a subset to a different database, 12-71\nnamespaces, 3-110\nnaming, 10-18\nnational character set, specifying, 14-23\nno-data-loss mode, 10-35\nonline\n adding log files, 10-30\n opening, 10-19, 14-19\n prepare to re-create, 10-33\n preventing changes to, 10-42\n protection mode of, 10-35\n quiesced state, 11-67\n read-only, 10-19\nread/write, 10-19\nreconstructing damaged, 10-20\nrecovering, 10-20, 10-21\nrecovery\n allowing corrupt blocks, 10-23\n testing, 10-22\n with backup control file, 10-22\nre-creating control file for, 14-12\nremote\n accessing, 9-16\n authenticating users to, 14-35\n connecting to, 14-34\n inserting into, 18-60\n service name of, 14-35\n table locks on, 18-73\nresetting\n to an earlier version, 10-9\n restoring earlier version of, 10-41, 12-100, 16-90\nrestricting users to read-only transactions, 10-20\nresuming activity, 11-66\nreturning to a past time, 18-24\nstandby\n adding log files, 10-30\n suspending activity, 11-66\nsystem user passwords, 14-22\ntemp files\n modifying, 10-26\ntime zone\n determining, 5-57\n setting, valid values for, 10-41, 14-30\ntime-based recovery, 10-22\nupgrading, 10-9\nDATAFILE clause\n of CREATE DATABASE, 14-29\nDATAFILE clauses\n of ALTER DATABASE, 10-12, 10-27\nDATAFILE OFFLINE clause\n of ALTER DATABASE, 10-27\nDATAFILE ONLINE clause\n of ALTER DATABASE, 10-27\nDATAFILE RESIZE clause\n of ALTER DATABASE, 10-28\ndatafiles\n dropping, 18-11\n online backup of, 12-95\n online, updating information on, 11-63\nDATAOBJ_TO_PARTITION function, 5-57\nDATE columns\n converting to datetime columns, 12-45\nDATE data type, 3-17\njulian, 3-17\ndate format models, 3-59, 3-61\n long, 3-61\n punctuation in, 3-60\n short, 3-61\n text in, 3-60\ndate functions, 5-5\ndates\n arithmetic, 3-20\n comparison rules, 3-37\ndatetime arithmetic, 3-20\n boundary cases, 11-51\n calculating daylight saving time, 3-22\ndatetime columns\n creating from DATE columns, 12-45\ndatetime data types, 3-16\n daylight saving time, 3-22\ndatetime expressions, 6-8\ndatetime field\n extracting from a datetime or interval value, 5-67\ndatetime format elements, 3-59\n and Globalization Support, 3-63\n\ncapitalization, 3-60\nISO standard, 3-64\nRR, 3-64\nsuffixes, 3-65\n\ndatetime functions, 5-5\ndatetime literals, 3-49\nDAY datetime format element, 3-63\ndaylight saving time, 3-22\nboundary cases, 3-22\ngoing into or coming out of effect, 3-22\n\nDB2 data types, 3-28\nrestrictions on, 3-29\n\nDBA_2PC_PENDING data dictionary view, 11-46\nDBA_COL_COMMENTS data dictionary view, 13-45\nDBA_INDEXTYPE_COMMENTS data dictionary view, 13-45\nDBA_MVIEW_COMMENTS data dictionary view, 13-45\nDBA_OPERATOR_COMMENTS data dictionary view, 13-45\nDBA_ROLLBACK_SEGS data dictionary view, 17-67\nDBA_TAB_COMMENTS data dictionary view, 13-45\n\nDBMS_ROWID package and extended rowids, 3-28\n\nDBTIMEZONE function, 5-57\n\nDDL. See data definition language (DDL)\n\nDEALLOCATE UNUSED clause\nof ALTER CLUSTER, 10-6, 10-7\nof ALTER INDEX, 10-79\nof ALTER TABLE, 12-35\n\nDEBUG ANY PROCEDURE system privilege, 18-40\n\nDEBUG object privilege\non a function, procedure, or package, 18-50\non a table, 18-50\non a view, 18-51\non an object type, 18-49\n\ndebugging\ngranting system privileges for, 18-40\n\ndecimal characters, 3-48\nspecifying, 3-57\n\nDECODE function, 5-57\ndecoding functions, 5-9\n\nDECOMPOSE function, 5-59\n\nDEFAULT clause\nof ALTER TABLE, 12-42\nof CREATE TABLE, 16-27, 16-30\n\nDEFAULT COST clause\nof ASSOCIATE STATISTICS, 13-24, 13-25\n\ndefault index, suppressing, 15-15\n\nDEFAULT profile\nassigning to users, 17-64\n\nDEFAULT ROLE clause\nof ALTER USER, 13-8\n\nDEFAULT SELECTIVITY clause\nof ASSOCIATE STATISTICS, 13-24, 13-25\n\nDEFAULT storage clause\nof ALTER TABLESPACE, 12-93\nof CREATE TABLESPACE, 16-87\n\ndefault tablespace, 14-27\n\nDEFAULT TABLESPACE clause\nof ALTER DATABASE, 10-39\nof ALTER USER, 13-8\nof ALTER USER. See CREATE USER\nof CREATE USER, 17-10\n\ndefault tablespaces\nspecifying for a user, 13-8\n\nDEFAULT TEMPORARY TABLESPACE clause\nof ALTER DATABASE, 10-39\nof CREATE DATABASE, 14-21\n\nDEFERRABLE clause\nof constraints, 8-14\n\ndeferable constraints, 19-59\n\nDEFERRED clause\nof SET CONSTRAINTS, 19-60\n\nDELETE ANY CUBE DIMENSION system privilege, 18-43\n\nDELETE ANY MEASURE FOLDER system privilege, 18-43\n\nDELETE ANY TABLE system privilege, 18-45\n\nDELETE object privilege\non a table, 18-50\non a view, 18-51\non an OLAP cube dimension, 18-49\non an OLAP measures folder, 18-49\n\nDELETE statement, 17-26\nerror logging, 17-32\n\nDELETE STATISTICS clause\nof ANALYZE, 13-21\n\nDELETEXML function, 5-60\n\nDENSE_RANK function, 5-61\n\nDEPTH function, 5-62\n\nDEREF function, 5-63\n\nDESC clause\nof CREATE INDEX, 14-72\n\ndictionaries\ngranting system privileges for, 18-40\n\ndimensional objects\nextracting data, 5-51\n\ndimensions\nattributes\nadding, 10-49\nchanging, 10-48\ndefining, 14-40\ndropping, 10-49\ncompiling invalidated, 10-50\ncreating, 14-37\ndefining levels, 14-37\nexamples, 14-40\nextracting data, 5-51\ngranting system privileges for, 18-40\n\nhierarchies\nadding, 10-49\nchanging, 10-48\ndefining, 14-39\ndropping, 10-49\n\nlevels\nadding, 10-49\n\ndefining, 14-38\ndropping, 10-49\nparent-child hierarchy, 14-38\nremoving from the database, 17-41\n\ndirectories. See directory objects\n\ndirectory objects\nas aliases for operating system directories, 14-42\nauditing, 13-32\ncreating, 14-42\ngranting system privileges for, 18-41\nredefining, 14-43\nremoving from the database, 17-42\n\ndirect-path INSERT, 3-78, 18-54\n\nDISABLE ALL TRIGGERS clause\nof ALTER TABLE, 12-78\n\nDISABLE clause\nof ALTER INDEX, 10-90\nof CREATE TABLE, 16-63\n\nDISABLE DISTRIBUTED RECOVERY clause\nof ALTER SYSTEM, 11-64\n\nDISABLE NOVALIDATE constraint state, 8-16\n\nDISABLE PARALLEL DML clause\nof ALTER SESSION, 11-46\n\nDISABLE QUERY REWRITE clause\nof ALTER MATERIALIZED VIEW, 11-14\nof CREATE MATERIALIZED VIEW, 15-20\n\nDISABLE RESTRICTED SESSION clause\nof ALTER SYSTEM, 11-68\n\nDISABLE RESUMABLE clause\nof ALTER SESSION, 11-48\n\nDISABLE ROW MOVEMENT clause\nof ALTER TABLE, 12-38\nof CREATE TABLE, 16-16, 16-64\n\nDISABLE STORAGE IN ROW clause\nof ALTER TABLE, 12-44\nof CREATE TABLE, 16-43\n\nDISABLE TABLE LOCK clause\nof ALTER TABLE, 12-78\n\nDISABLE VALIDATE constraint state, 8-16\n\nDISASSOCIATE STATISTICS statement, 17-34\n\nDISCONNECT SESSION clause\nof ALTER SYSTEM, 11-63\n\ndisk group files\nchanging permission settings, 10-69\nIntelligent Data Placement, 10-65\nsetting owner or user group, 10-70\n\ndisk groups\naltering, 10-51\ncreating, 14-44\na tablespace in, 16-85\nfailure groups, 10-59, 14-46\nfiles in, 8-32\ndropping, 17-43\nmanaging Oracle ASM volumes, 10-67\nrebalancing, 10-62\nsetting attributes, 10-68, 14-47\nspecifying files in, 8-32\nspecifying files in control files, 14-15\n\ndiskgroup\nOracle ASM, 15-71\n\ndisks\nbringing online, 10-62\nQUORUM, 14-46\nregions, 10-65\nREGULAR, 14-46\ntaking offline, 10-61\n\ndispatcher processes\ncreating additional, 11-73\nterminating, 11-73\n\nDISTINCT clause\nof SELECT, 19-15\n\ndistinct queries, 19-15\n\ndistributed queries, 9-16\nrestrictions on, 9-16\n\ndistribution\nhints for, 3-99\n\nDML. See data manipulation language (DML)\n\ndomain indexes, 14-61, 14-78, 14-87\nand LONG columns, 12-46\nassociating statistics types with, 13-23\ncreating, prerequisites, 14-78\ndetermining user-defined CPU and I/O costs, 18-20\ndisassociating statistics types from, 17-34, 17-50\nexample, F-1\ninvoking drop routines for, 18-6\nlocal partitioned, 14-78\nmodifying, 10-89\nparallelizing creation of, 14-78\nrebuilding, 10-86\nremoving from the database, 17-49\nsystem managed, 14-89\n\ndomain_index_clause\nof CREATE INDEX, 14-64\n\nDOWNGRADE clause\nof ALTER DATABASE, 10-20\n\nDRIVING_SITE hint, 3-80\n\nDROP ANY CLUSTER system privilege, 18-40\nDROP ANY CONTEXT system privilege, 18-40\nDROP ANY CUBE BUILD PROCESS system privilege, 18-43\nDROP ANY CUBE DIMENSION system privilege, 18-43\nDROP ANY CUBE system privilege, 18-42\nDROP ANY DIMENSION system privilege, 18-41\nDROP ANY DIRECTORY system privilege, 18-41\nDROP ANY INDEX system privilege, 18-41\nDROP ANY INDEXTYPE system privilege, 18-41\nDROP ANY LIBRARY system privilege, 18-42\nDROP ANY MATERIALIZED VIEW system privilege, 18-42\nDROP ANY MEASURE FOLDER system privilege, 18-43\nDROP ANY MINING MODEL system privilege, 18-42\nDROP ANY OPERATOR system privilege, 18-43\nDROP ANY OUTLINE system privilege, 18-43\nDROP ANY PROCEDURE system privilege, 18-44\nDROP ANY ROLE system privilege, 18-44\nDROP ANY SEQUENCE system privilege, 18-44\n\nDROP ANY SQL PROFILE system privilege, 18-40\nDROP ANY SYNONYM system privilege, 18-45\nDROP ANY TABLE system privilege, 18-45\nDROP ANY TRIGGER system privilege, 18-45\nDROP ANY TYPE system privilege, 18-46\nDROP ANY VIEW system privilege, 18-46\nDROP clause\n of ALTER DIMENSION, 10-49\n of ALTER INDEXTYPE, 10-98\nDROP CLUSTER statement, 17-36\nDROP COLUMN clause\n of ALTER TABLE, 12-48\nDROP CONSTRAINT clause\n of ALTER TABLE, 12-54\nDROP constraint clause\n of ALTER VIEW, 13-13\nDROP CONTEXT statement, 17-38\nDROP DATABASE LINK statement, 17-40\nDROP DATABASE statement, 17-39\nDROP DIMENSION statement, 17-41\nDROP DIRECTORY statement, 17-42\nDROP DISKGROUP statement, 17-43\nDROP FLASHBACK ARCHIVE statement, 17-46\nDROP FUNCTION statement, 17-47\nDROP INDEX statement, 17-49\nDROP INDEXTYPE statement, 17-51\nDROP JAVA statement, 17-52\nDROP LIBRARY statement, 17-53\nDROP LOGFILE clause\n of ALTER DATABASE, 10-14, 10-31\nDROP LOGFILE MEMBER clause\n of ALTER DATABASE, 10-14, 10-32\nDROP MATERIALIZED VIEW LOG\n statement, 17-56\nDROP MATERIALIZED VIEW statement, 17-54\nDROP OPERATOR statement, 17-58\nDROP OUTLINE statement, 17-59\nDROP PACKAGE BODY statement, 17-61\nDROP PACKAGE statement, 17-61\nDROP PARTITION clause\n of ALTER INDEX, 10-94\n of ALTER TABLE, 12-65\nDROP PRIMARY constraint clause\n of ALTER TABLE, 12-54\nDROP PROCEDURE statement, 17-63\nDROP PROFILE statement, 17-64\nDROP PROFILE system privilege, 18-44\nDROP PUBLIC DATABASE LINK system\n privilege, 18-40\nDROP PUBLIC SYNONYM system privilege, 18-45\nDROP RESTORE POINT statement, 17-65\nDROP ROLE statement, 17-66\nDROP ROLLBACK SEGMENT statement, 17-67\nDROP ROLLBACK SEGMENT system\n privilege, 18-44\nDROP SEQUENCE statement, 18-2\nDROP SUPPLEMENTAL LOG DATA clause\n of ALTER DATABASE, 10-33\nDROP SUPPLEMENTAL LOG GROUP clause\n of ALTER TABLE, 12-34\nDROP SYNONYM statement, 18-3\nDROP TABLE statement, 18-5\nDROP TABLESPACE statement, 18-9\nDROP TABLESPACE system privilege, 18-45\nDROP TRIGGER statement, 18-12\nDROP TYPE BODY statement, 18-15\nDROP TYPE statement, 18-13\nDROP UNIQUE constraint clause\n of ALTER TABLE, 12-54\nDROP USER statement, 18-16\nDROP USER system privilege, 18-46\nDROP VALUES clause\n of ALTER TABLE ... MODIFY\n PARTITION, 12-60, 12-61\nDROP VIEW statement, 18-18\nDUAL dummy table, 3-109, 9-15\nDUMP function, 5-64\nDY datetime format element, 3-63\nDYNAMIC_SAMPLING hint, 3-81\n\nE\nEBCDIC character set, 3-38\neditioning views, 17-17\neditions\n comments on, 13-45\n creating, 14-52\n dropping, 17-45\n granting system privileges for, 18-41\n setting default for database, 10-38\n setting for a session, 11-49\nembedded SQL, 10-3\n precompiler support, 10-3\nEMPTY_BLOB function, 5-65\nEMPTY_CLOB function, 5-65\nENABLE ALL TRIGGERS clause\n of ALTER TABLE, 12-78\nENABLE clause\n of ALTER INDEX, 10-90\n of ALTER TRIGGER, 13-3\n of CREATE TABLE, 16-63\nENABLE DISTRIBUTED RECOVERY clause\n of ALTER SYSTEM, 11-64\nENABLE NOVALIDATE constraint state, 8-16\nENABLE PARALLEL DML clause\n of ALTER SESSION, 11-46\nENABLE QUERY REWRITE clause\n of ALTER MATERIALIZED VIEW, 11-14\n of CREATE MATERIALIZED VIEW, 15-20\nENABLE RESTRICTED SESSION clause\n of ALTER SYSTEM, 11-68\nENABLE RESUMABLE clause\n of ALTER SESSION, 11-48\nENABLE ROW MOVEMENT clause\n of ALTER TABLE, 12-38\n of CREATE TABLE, 16-16, 16-64\nENABLE STORAGE IN ROW clause\n of ALTER TABLE, 12-44\n of CREATE TABLE, 16-43\nENABLE TABLE LOCK clause\n\nof ALTER TABLE, 12-78\nENABLE VALIDATE constraint state, 8-15\nencoding functions, 5-9\nencryption, 16-27\n of tablespaces, 8-56, 16-87\nencryption keys\n generating, 11-69\nEND BACKUP clause\n of ALTER DATABASE, 10-25\n of ALTER DATABASE ... DATAFILE, 10-28\n of ALTER TABLESPACE, 12-95\nenterprise users\n allowing connection as database users, 13-9\nenvironment functions, 5-9\nequality test, 7-5\nequijoins, 9-11\n defining for a dimension, 14-39\nequivalency tests, 7-24\nerror logging\n of DELETE operations, 17-32\n of INSERT operations, 18-65\n of MERGE operations, 18-78\nERROR_ON_OVERLAP_TIME session parameter, 11-51\nEVALUATE operator, 4-1\nEXCEPTIONS INTO clause\n of ALTER TABLE, 12-72\nEXCHANGE PARTITION clause\n of ALTER TABLE, 12-26, 12-71\nEXCHANGE SUBPARTITION clause\n of ALTER TABLE, 12-26, 12-71\nexchanging partitions\n restrictions on, 12-73\nEXCLUDING NEW VALUES clause\n of ALTER MATERIALIZED VIEW LOG, 11-23\n of CREATE MATERIALIZED VIEW LOG, 15-31\nEXCLUSIVE lock mode, 18-74\nexclusive locks\n row locks (TX), B-1\n table locks (TM), B-1\nEXECUTE ANY CLASS system privilege, 18-41\nEXECUTE ANY INDEXTYPE system privilege, 18-41\nEXECUTE ANY LIBRARY system privilege, 18-42\nEXECUTE ANY OPERATOR system privilege, 18-43\nEXECUTE ANY PROCEDURE system privilege, 18-44\nEXECUTE ANY PROGRAM system privilege, 18-41\nEXECUTE ANY TYPE system privilege, 18-46\nEXECUTE object privilege\n on a directory, 18-48\n on a library, 18-49\n on an object type, 18-49\n on an operator, 18-49\nexecution plans\n determining, 18-20\n dropping outlines for, 17-59\n saving, 15-37\nEXEMPT ACCESS POLICY system privilege, 18-47\nEXISTS condition, 7-20, 7-22\nEXISTSNODE function, 5-66\nEXP function, 5-67\nEXPLAIN PLAN statement, 18-20\nexplicit data conversion, 3-40, 3-43\nexpressions\n CASE, 6-5\n changing declared type of, 5-234\n column, 6-6\n comparing, 5-57\n compound, 6-4\n computing with the DUAL table, 9-15\n CURSOR, 6-7\n datetime, 6-8\n in SQL syntax, 6-1\n interval, 6-10\n lists of, 6-16\n model, 6-11\n object access, 6-13\n placeholder, 6-14\n scalar subqueries as, 6-14\n simple, 6-3\n type constructor, 6-14\nextended rowids\n base 64, 3-28\n not directly available, 3-28\nextensible indexing\n example, F-1\nEXTENT MANAGEMENT clause\n of CREATE DATABASE, 14-21\n of CREATE TABLESPACE, 16-83, 16-88\nEXTENT MANAGEMENT DICTIONARY clause\n of CREATE TABLESPACE, 16-88\nEXTENT MANAGEMENT LOCAL clause\n of CREATE DATABASE, 14-25\nextents\n allocating for partitions, 12-35\n allocating for subpartitions, 12-35\n allocating for tables, 12-35\n restricting access by instances, 10-84\n specifying maximum number for an object, 8-53\n specifying number allocated upon object creation, 8-52\n specifying the first for an object, 8-51\n specifying the percentage of size increase, 8-52\n specifying the second for an object, 8-51\nexternal functions, 14-59, 15-47\nexternal LOBs, 3-24\nexternal procedures, 15-47\nexternal tables, 16-37\n access drivers, 16-40\n altering, 12-55\n creating, 16-39\n ORACLE_DATAPUMP access driver, 16-40\n ORACLE_LOADER access driver, 16-40\n restrictions on, 16-40\nexternal users, 15-59, 17-9\nEXTRACT (datetime) function, 5-67\nEXTRACT (XML) function, 5-70\nEXTRACTVALUE function, 5-71\n\nF\n\nFACT hint, 3-81\nFAILED_LOGIN_ATTEMPTS parameter\n of ALTER PROFILE, 11-33\n of CREATE PROFILE, 15-52\nfailure groups\n creating for a disk group, 10-59, 14-46\nFEATURE_ID function, 5-72\nFEATURE_SET function, 5-73\nFEATURE_VALUE function, 5-75\nfiles\n specifying as a redo log file group, 8-29\n specifying as data files, 8-29\n specifying as temp files, 8-29\nFIPS\n compliance, C-26\n flagging, 11-52\nFIRST function, 5-76\nFIRST_ROWS(n) hint, 3-81\nFIRST_VALUE function, 5-78\nFLAGGER session parameter, 11-52\nflash cache, 8-55\nFLASH_CACHE parameter\n of STORAGE clause, 8-55\nFLASHBACK ANY TABLE system privilege, 18-42, 18-45, 18-46\nFLASHBACK ARCHIVE ADMINISTER system\n privilege, 18-41\nFLASHBACK ARCHIVE object privilege, 18-48\nflashback data archives\n creating, 14-56\n dropping, 17-46\n modifying, 10-74\n privileges for, 18-41\n specifying for a table, 12-38, 16-64\nFLASHBACK DATABASE statement, 18-24\nflashback queries, 19-17\n pseudocolumns for, 2-5\n using with inserts, 18-58, 19-77\nFLASHBACK TABLE statement, 18-27\nfloating-point conditions, 7-7\nfloating-point numbers, 3-13\n converting to, 5-214, 5-215\n handling NaN, 5-113\nFLOOR function, 5-80\nFLUSH BUFFER_CACHE clause\n of ALTER SYSTEM, 11-65\nFLUSH REDO clause\n of ALTER SYSTEM, 11-65\nFLUSH SHARED POOL clause\n of ALTER SYSTEM, 11-64\nFM format model modifier, 3-66\nFOR clause\n of CREATE INDEXTYPE, 14-88\n of EXPLAIN PLAN, 18-21, 18-27\nFOR UPDATE clause\n of CREATE MATERIALIZED VIEW, 15-20\n of SELECT, 19-13, 19-34\nFORCE ANY TRANSACTION system\n privilege, 18-47\nFORCE clause\n of COMMIT, 13-49\n of CREATE VIEW, 17-16\n of DISASSOCIATE STATISTICS, 17-35\n of DROP INDEX, 17-50\n of DROP INDEXTYPE, 17-51\n of DROP OPERATOR, 17-58\n of DROP TYPE, 18-14\n of REVOKE, 18-92\n of ROLLBACK, 18-27, 18-98\nFORCE LOGGING clause\n of ALTER DATABASE, 10-29\n of ALTER TABLESPACE, 12-97\n of CREATE CONTROLFILE, 14-17\n of CREATE DATABASE, 14-25\n of CREATE TABLESPACE, 16-87\nFORCE PARALLEL DML clause\n of ALTER SESSION, 11-46\nFORCE TRANSACTION system privilege, 18-47\nforeign key constraints, 8-10\nforeign tables\n rowids of, 3-28\nformat models, 3-55\n changing the return format, 3-67\n date, 3-59\n changing, 3-59\n default format, 3-59\n format elements, 3-59\n maximum length, 3-59\nmodifiers, 3-65\nnumber, 3-56\nnumber, elements of, 3-57\nspecifying, 3-68\nXML, 3-69\nformats\n for dates and numbers. See format models\n of return values from the database, 3-55\n of values stored in the database, 3-55\nfree lists\n specifying for a table, partition, cluster, or\n index, 8-54\n specifying for LOBs, 16-45\nFREELIST GROUPS parameter\n of STORAGE clause, 8-54\nFREELISTS parameter\n of STORAGE clause, 8-53\nFREEPOOLS parameter\n of LOB storage, 16-45\nFROM clause\n of queries, 9-11\nFROM COLUMNS clause\n of DISASSOCIATE STATISTICS, 17-34\nFROM FUNCTIONS clause\n of DISASSOCIATE STATISTICS, 17-34\nFROM INDEXES clause\n of DISASSOCIATE STATISTICS, 17-34\nFROM INDEXTYPES clause\n of DISASSOCIATE STATISTICS, 17-34\nFROM PACKAGES clause\n of DISASSOCIATE STATISTICS, 17-34\n\nFROM TYPES clause\nof DISASSOCIATE STATISTICS, 17-34\nFROM_TZ function, 5-80\nFULL hint, 3-82\nfull outer joins, 19-24\nfunction expressions\n built-in, 6-10\n user-defined, 6-10\nfunction-based indexes, 14-61\n creating, 14-70\n disabling, 10-86, 10-90\n enabling, 10-86, 10-90\n refreshing, 10-38\nfunctions\n See also SQL functions\n3GL calling, 15-2\nassociating statistics types with, 13-23\navoiding run-time compilation, 10-77\nbuilt_in\n as expressions, 6-10\ncalling, 13-40\nchanging the declaration of, 14-60\nchanging the definition of, 14-60\ndefining an index on, 14-70\ndisassociating statistics types from, 17-34\nexecuting, 13-40\nexternal, 14-59, 15-47\ninverse distribution, 5-133, 5-135\nissuing COMMIT or ROLLBACK statements, 11-46\nlinear regression, 5-166\nnaming rules, 3-111\nOLAP, 5-17\nrecompiling invalid, 10-77\nre-creating, 14-60, 14-92\nremoving from the database, 17-47\nstatistics, assigning default cost, 13-24\nstatistics, defining default selectivity, 13-24\nstored, 14-59\nstoring return value of, 13-42\nsynonyms for, 16-2\nuser-defined, 5-270\n as expressions, 6-10\nXML, 5-8\n\nFUNCTIONS clause\nof ASSOCIATE STATISTICS, 13-23, 13-24\nof DISASSOCIATE STATISTICS, 17-34\nFX format model modifier, 3-66\n\nG\ngeneral comparison functions, 5-6\ngeneral recovery clause\n of ALTER DATABASE, 10-11, 10-20\ngeoimaging, 3-34\nglobal indexes. See indexes, globally partitioned\nGLOBAL PARTITION BY HASH clause\n of CREATE INDEX, 14-75\nGLOBAL PARTITION BY RANGE clause\n of CREATE INDEX, 14-65, 14-75\n\nGLOBAL QUERY REWRITE system privilege, 18-42\nGLOBAL TEMPORARY clause\n of CREATE TABLE, 16-25\nglobal users, 15-59, 17-10\nGLOBAL_TOPIC_ENABLED system parameter, 11-72\nglobally partitioned indexes, 14-75, 14-76\nGRANT ANY OBJECT PRIVILEGE system privilege, 18-47\nGRANT ANY PRIVILEGE system privilege, 18-47\nGRANT ANY ROLE system privilege, 18-44\nGRANT clause\n of ALTER USER, 13-9\nGRANT CONNECT THROUGH clause\n of ALTER USER, 13-6, 13-9\nGRANT statement\n locks, B-5\nGRAPHIC data type\n DB2, 3-29\n SQL/DS, 3-29\ngreater than or equal to tests, 7-5\ngreater than tests, 7-5\nGREATEST function, 5-81\nGROUP BY clause\n CUBE extension, 19-27\n identifying duplicate groupings, 5-81\n of SELECT and subqueries, 19-10, 19-27\n ROLLUP extension of, 19-27\ngroup comparison conditions, 7-6\ngroup separator\n specifying, 3-57\nGROUP_ID function, 5-81\nGROUPING function, 5-82\ngrouping sets, 19-28\nGROUPING SETS clause\n of SELECT and subqueries, 19-28\nGROUPING_ID function, 5-83\ngroupings\n filtering out duplicate, 5-81\nGUARD ALL clause\n of ALTER DATABASE, 10-42\nGUARD clause\n of ALTER DATABASE, 10-42\n overriding, 11-46\nGUARD NONE clause\n of ALTER DATABASE, 10-42\nGUARD STANDBY clause\n of ALTER DATABASE, 10-42\n\nH\nhash clusters\n creating, 14-5\n single-table, creating, 14-6\n specifying hash function for, 14-6\nHASH hint, 3-82\nHASH IS clause\n of CREATE CLUSTER, 14-6\nhash partitioning clause\n of CREATE TABLE, 16-24, 16-54\n\nhash partitions\n adding, 12-64\n coalescing, 12-59\n\nHASHKEYS clause\n of CREATE CLUSTER, 14-5\n\nHAVING condition\n of GROUP BY clause, 19-28\n\nheap-organized tables\n creating, 16-6\n\nhexadecimal value\n returning, 3-58\n\nHEXTORAW function, 5-84\n\nhierarchical functions, 5-7\n\nhierarchical queries, 9-3, 19-26\n child rows, 2-2, 9-4\n illustrated, 2-2\n leaf rows, 2-2\n operators in, 4-5\n CONNECT_BY_ROOT, 4-5\n PRIOR, 4-5\n\nordering, 19-33\n\nparent rows, 2-2, 9-4\n\npseudocolumns in, 2-1\n CONNECT_BY_ISCYCLE, 2-1\n CONNECT_BY_ISLEAF, 2-2\n LEVEL, 2-2\n\nretrieving root and node values, 5-200\n\nhierarchical query clause\n of SELECT and subqueries, 19-10\n\nhierarchies\n adding to a dimension, 10-49\n dropping from a dimension, 10-49\n of dimensions, defining, 14-39\n\nHIERARCHY clause\n of CREATE DIMENSION, 14-38, 14-39\n\nhigh water mark\n of clusters, 10-7\n of indexes, 10-84\n of tables, 12-35, 13-17\n\nhints, 9-2\n ALL_ROWS, 3-77\n APPEND, 3-78\n APPEND_VALUES, 3-78\n CACHE, 3-79\n CLUSTER, 3-80\n CURSOR_SHARING_EXACT, 3-80\n DRIVING_SITE, 3-80\n DYNAMIC_SAMPLING, 3-81\n FACT, 3-81\n FIRST_ROWS(n), 3-81\n FULL, 3-82\n HASH, 3-82\n in SQL statements, 3-73\n INDEX, 3-83\n INDEX_ASC, 3-84\n INDEX_COMBINE, 3-84\n INDEX_DESC, 3-85\n INDEX_FFS, 3-85\n INDEX_JOIN, 3-85\n INDEX_SS, 3-86\n INDEX_SS_ASC, 3-86\n INDEX_SS_DESC, 3-87\n LEADING, 3-87\n location syntax, 3-75\n MERGE, 3-87\n MODEL_MIN_ANALYSIS, 3-88\n MONITOR, 3-88\n NO_EXPAND, 3-89\n NO_FACT, 3-89\n NO_INDEX, 3-90\n NO_INDEX_FFS, 3-90\n NO_INDEX_SS, 3-90\n NO_MERGE, 3-91\n NO_MONITOR, 3-91\n NO_PARALLEL, 3-91\n NO_PARALLEL_INDEX, 3-92\n NO_PUSH_PRED, 3-92\n NO_PUSH_SUBQ, 3-92\n NO_PX_JOIN_FILTER, 3-93\n NO_QUERY_TRANSFORMATION, 3-93\n NO_RESULT_CACHE, 3-93\n NO_REWRITE, 3-93\n NO_STAR_TRANSFORMATION, 3-94\n NO_STATEMENT_QUEUING, 3-94\n NO_UNNEST, 3-94\n NO_USE_HASH, 3-94\n NO_USE_MERGE, 3-94\n NO_USE_NL, 3-95\n NO_XML_QUERY_REWRITE, 3-95\n NO_XMLINDEX_REWRITE, 3-95\n NOAPPEND, 3-89\n NOCACHE, 3-89\n NOPARALLEL, 3-91\n NOPARALLEL_INDEX, 3-92\n NOREWRITE, 3-93\n OPT_PARAM, 3-96\n ORDERED, 3-96\n PARALLEL, 3-96\n PARALLEL_INDEX, 3-98\n passing to the optimizer, 19-72\n PQ_DISTRIBUTE, 3-99\n PUSH_PRED, 3-101\n PUSH_SUBQ, 3-101\n PX_JOIN_FILTER, 3-102\n QB_NAME, 3-102\n REWRITE, 3-103\n specifying a query block, 3-75\n STAR_TRANSFORMATION, 3-104\n STATEMENT_QUEUING, 3-104\n syntax, 3-75\n UNNEST, 3-104\n USE_CONCAT, 3-105\n USE_HASH, 3-105\n USE_MERGE, 3-105\n USE_NL, 3-106\n USE_NL_WITH_INDEX, 3-106\n\nhistograms\n creating equiwidth, 5-247\n\nhybrid columnar compression, 16-35\n\nIDENTIFIED BY clause\n of ALTER ROLE. *See* CREATE ROLE\n of CREATE DATABASE LINK, 14-35\n of SET ROLE, 19-62\n\nIDENTIFIED EXTERNALLY clause\n of ALTER ROLE. *See* CREATE ROLE\n of ALTER USER. *See* CREATE USER\n of CREATE ROLE, 15-59\n of CREATE USER, 17-9\n\nIDENTIFIED GLOBALLY clause\n of ALTER ROLE. *See* CREATE ROLE\n of CREATE ROLE, 15-59\n of CREATE USER, 17-10\n\nidentifier functions, 5-9\n\nIDLE_TIME parameter\n of ALTER PROFILE, 11-32\n\nIEEE754\n floating-point arithmetic, 3-13\n Oracle conformance with, 3-13\n\nIGNORE_ROW_ON_DUPKEY_INDEX hint, 3-83\n\nIMMEDIATE clause\n of SET CONSTRAINTS, 19-59\n\nimplicit data conversion, 3-40, 3-42\n\nIN conditions, 7-23\n\nINCLUDING CONTENTS clause\n of DROP TABLESPACE, 18-10\n\nINCLUDING DATAFILES clause\n of ALTER DATABASE TEMPFILE DROP\n clause, 10-28\n\nINCLUDING NEW VALUES clause\n of ALTER MATERIALIZED VIEW LOG, 11-23\n of CREATE MATERIALIZED VIEW LOG, 15-31\n\nINCLUDING TABLES clause\n of DROP CLUSTER, 17-36\n\nincomplete object types, 17-3\n creating, 17-3\n\nINCREMENT BY clause\n of ALTER SEQUENCE. *See* CREATE SEQUENCE\n\nINCREMENT BY parameter\n of CREATE SEQUENCE, 15-67\n\nincremental\n and block change tracking, 10-40\n\nINDEX clause\n of ANALYZE, 13-18\n of CREATE CLUSTER, 14-5\n\nINDEX hint, 3-83\n\nindex keys\n compression, 10-81\n\nINDEX object privilege\n on a table, 18-50\n\nindex partitions\n creating subpartitions, 14-67\n index subpartitions, 14-67\n\nINDEX_ASC hint, 3-84\n\nINDEX_COMBINE hint, 3-84\n\nINDEX_DESC hint, 3-85\n\nINDEX_FFS hint, 3-85\n\nINDEX_JOIN hint, 3-85\n\nINDEX_SS hint, 3-86\n\nINDEX_SS_ASC hint, 3-86\n\nINDEX_SS_DESC hint, 3-87\n\nindexed clusters\n creating, 14-5\n\nindexes, 10-85\n allocating new extents for, 10-84\n application-specific, 14-87\n ascending, 14-72\n based on indextypes, 14-78\n bitmap, 14-68\n bitmap join, 14-79\n B-tree, 14-61\n changing attributes, 10-85\n changing parallelism of, 10-85\n collecting statistics on, 13-18\n on composite-partitioned tables, 14-77\n creating, 14-61\n creating as unusable, 14-80\n creating on a cluster, 14-62\n creating on a table, 14-62\n deallocating unused space from, 10-84\n descending, 14-72\n and query rewrite, 14-72\n as function-based indexes, 14-72\n direct-path inserts, logging, 10-85\n domain, 14-61, 14-78, 14-87\n domain, example, F-1\n dropping index partitions, 17-50\n examples, 14-81\n full fast scans, 3-85\n function-based, 14-61\n creating, 14-70\n global partitioned, creating, 14-65\n globally partitioned, 14-75, 14-76\n updating, 12-75\n granting system privileges for, 18-41\n on hash-partitioned tables, 14-76\n invisible to the optimizer, 10-91, 14-73\n join, bitmap, 14-79\n key compression of, 10-88\n key compression, enabling, 10-86\n keys, eliminating repetition, 10-86\n local domain, 14-78\n locally partitioned, 14-76\n logging rebuild operations, 10-86\n marking as UNUSABLE, 10-90\n merging block contents, 10-86\n merging contents of index blocks, 10-91\n merging contents of index partition blocks, 10-93\n modifying attributes, 10-86\n moving, 10-86\n on clusters, 14-69\n on composite-partitioned tables, creating, 14-67\n on hash-partitioned tables\n creating, 14-67\n on index-organized tables, 14-69\n on list-partitioned tables\n creating, 14-66\n on nested table storage tables, 14-69\n on partitioned tables, 14-69\n\non range-partitioned tables, creating, 14-66\non scalar typed object attributes, 14-69\non table columns, 14-69\non XMLType tables, 14-81\nonline, 14-74\nparallelizing creation of, 14-75\npartitioned, 3-116, 14-61\n user-defined, 14-75\npartitioning, 14-75\npartitions, 14-75\n adding hash, 10-92\n adding new, 10-94\n changing default attributes, 10-92\n changing physical attributes, 10-85\n changing storage characteristics, 10-92\n coalescing hash partitions, 10-94\n deallocating unused space from, 10-84\n dropping, 10-94\n marking UNUSABLE, 10-94, 12-73\n modifying the real characteristics, 10-93\n preventing use of, 10-90\n rebuilding, 10-86\n rebuilding unusable, 12-73\n re-creating, 10-86\n removing, 10-92\n renaming, 10-93\n specifying tablespace for, 10-86, 10-88\n splitting, 10-92, 10-94\npreventing use of, 10-90\npurging from the recycle bin, 18-84\non range-partitioned tables, 14-76\nrebuilding, 10-86\nrebuilding while online, 10-88\nre-creating, 10-86\nremoving from the database, 17-49\nrenaming, 10-86, 10-91\nreverse, 10-86, 10-87, 10-89, 14-73\nspecifying tablespace for, 10-86, 10-88\nstatistics on usage, 10-91\nsubpartitions\n allocating extents for, 10-94\n changing default attributes, 10-92\n changing physical attributes, 10-85\n changing storage characteristics, 10-92\n deallocating unused space from, 10-84, 10-94\n marking UNUSABLE, 10-94\n modifying, 10-86\n moving, 10-86\n preventing use of, 10-90\n rebuilding, 10-86\n re-creating, 10-86\n renaming, 10-93\n specifying tablespace for, 10-86, 10-88\ntablespace containing, 14-72\nunique, 14-68\nunsorted, 14-73\nused to enforce constraints, 12-55, 16-64\nvalidating structure, 13-19\n\nINDEXES clause\nof ASSOCIATE STATISTICS, 13-23, 13-24\nof DISASSOCIATE STATISTICS, 17-34\n\nindex-organized tables\n bitmap indexes on, creating, 16-38\n creating, 16-6\n mapping tables, 12-76\n creating, 16-38\n moving, 12-62\n merging contents of index blocks, 12-41\n modifying, 12-39, 12-40\n moving, 12-76\noverflow segments\n specifying storage, 12-39, 16-55\npartitioned, updating secondary indexes, 10-93\nPCT_ACCESS_DIRECT statistics, 13-17\n\nprimary key indexes\n coalescing, 12-39\n rebuilding, 12-76\n rowids of, 3-28\nsecondary indexes, updating, 10-91\n\nINDEXTYPE clause\n of CREATE INDEX, 14-64, 14-78\n\nindextypes\n adding operators, 10-97\n altering, 10-97\n associating statistics types with, 13-23\n changing implementation type, 10-97\n comments on, 13-45\n creating, 14-87\n disassociating statistics types from, 17-34, 17-51\ndrop routines, invoking, 17-50\ngranting system privileges for, 18-41\nindexes based on, 14-78\ninstances, 14-61\n removing from the database, 17-51\n\nINDEXTYPES clause\n of ASSOCIATE STATISTICS, 13-23, 13-24\n of DISASSOCIATE STATISTICS, 17-34\n\nin-doubt transactions\n forcing, 13-49\n forcing commit of, 13-49\n forcing rollback, 18-27, 18-98\n rolling back, 18-97\n\ninequality test, 7-5\n\nINITCAP function, 5-85\n\nINITIAL parameter\n of STORAGE clause, 8-51\n\ninitialization parameters\n changing session settings, 11-49\n setting using ALTER SESSION, 11-50\n\nINITIALIZED EXTERNALLY clause\n of CREATE CONTEXT, 14-10\n\nINITIALIZED GLOBALLY clause\n of CREATE CONTEXT, 14-10\n\nINITIALLY DEFERRED clause\n of constraints, 8-15\n\nINITIALLY IMMEDIATE clause\n of constraints, 8-15\n\nINITTRANS parameter\n of ALTER CLUSTER, 10-6\n of ALTER INDEX, 10-85\n\nof ALTER MATERIALIZED VIEW LOG, 11-19\nof ALTER TABLE, 12-33\nof CREATE INDEX. See CREATE TABLE\nof CREATE MATERIALIZED VIEW LOG. See CREATE TABLE\nof CREATE MATERIALIZED VIEW. See CREATE TABLE\nof CREATE TABLE, 8-46\n\ninline constraints\n of ALTER TABLE, 12-43\n of CREATE TABLE, 16-30\n\ninline views, 9-14\n\ninner joins, 9-12, 19-24\n\ninner-N reporting, 5-174\n\nINSERT\n direct-path versus conventional, 18-54\nINSERT ANY CUBE DIMENSION system privilege, 18-43\nINSERT ANY MEASURE FOLDER system privilege, 18-43\nINSERT ANY TABLE system privilege, 18-45\nINSERT clause\n of MERGE, 18-76\nINSERT object privilege\n on a table, 18-50\n on a view, 18-51\n on an OLAP cube dimension, 18-49\n on an OLAP measures folder, 18-49\nINSERT statement, 18-54\n append, 3-78\n error logging, 18-65\nINSERTCHILDXML function, 5-85\nINSERTCHILDXMLAFTER function, 5-86\nINSERTCHILDXMLBEFORE function, 5-87\n\ninserts\n and simultaneous update, 18-75\n conditional, 18-63\n conventional, 18-54\n direct-path, 18-54\n multitable, 18-63\n examples, 18-68\n single-table, 18-58\n using MERGE, 18-76\nINSERTXMLAFTER function, 5-88\nINSERTXMLBEFORE function, 5-89\n\ninstance recovery\n continue after interruption, 10-20\n\nINSTANCE session parameter, 11-52\n\ninstances\n making index extents available to, 10-84\n setting parameters for, 11-70\n\nINSTR function, 5-90\nINSTR2 function, 5-90\nINSTR4 function, 5-90\nINSTRB function, 5-90\nINSTRC function, 5-90\n\nintegers\n generating unique, 15-66\n in SQL syntax, 3-47\n precision of, 3-47\n\nsyntax of, 3-47\n\nintegrity constraints. See constraints\n\ninternal LOBs, 3-24\n\nInternational Organization for Standardization (ISO), C-1\n standards, 1-1, C-1\n\nINTERSECT set operator, 4-5, 19-33\n\ninterval\n arithmetic, 3-20\n data types, 3-16\n literals, 3-52\n\ninterval conditions, 7-22\n\nINTERVAL DAY TO SECOND data type, 3-20\n\nINTERVAL expressions, 6-10\n\ninterval partitioning, 12-57, 16-52\n changing the interval, 12-57\n\nINTERVAL YEAR TO MONTH data type, 3-19\n\nINTO clause\n of EXPLAIN PLAN, 18-21\n of INSERT, 18-58\n\nINVALIDATE GLOBAL INDEXES clause\n of ALTER TABLE, 12-75\n\ninverse distribution functions, 5-133, 5-135\n\ninvoker rights\n altering for a Java class, 10-101\n defining for a Java class, 14-92, 14-93\n\nIS [NOT] EMPTY conditions, 7-12\n\nIS ANY condition, 7-9\n\nIS NOT NULL operator, 7-20\n\nIS NULL operator, 7-20\n\nIS OF type condition, 7-25\n\nIS PRESENT condition, 7-10\n\nISO. See International Organization for Standardization (ISO)\n\nISOLATION_LEVEL session parameter, 11-52\n\nITERATION_NUMBER function, 5-91\n\nJ\n\nJava\n class\n creating, 14-91, 14-92\n dropping, 17-52\n resolving, 10-100, 14-92\n Java source schema object\n creating, 14-92\n resource\n creating, 14-91, 14-92\n dropping, 17-52\n schema object\n name resolution of, 14-94\n source\n compiling, 10-100, 14-92\n creating, 14-91\n dropping, 17-52\n\njob scheduler object privileges, 18-41\n\nJOIN clause\n of CREATE DIMENSION, 14-38\n\nJOIN KEY clause\n of ALTER DIMENSION, 10-49\n\nof CREATE DIMENSION, 14-39\n\njoin views\n example, 17-23\n making updatable, 17-21\n modifying, 17-30, 18-59, 19-74\n\njoins, 9-11\n antijoins, 9-14\n conditions\n defining, 9-11\n cross, 19-23\n equijoins, 9-11\n full outer, 19-24\n inner, 9-12, 19-24\n left outer, 19-24\n natural, 19-25\n outer, 9-12\n and data densification, 9-12\n on grouped tables, 9-12\n restrictions, 9-13\n parallel, 3-99\n right outer, 19-24\n self, 9-11\n semijoins, 9-14\n without join conditions, 9-12\n\nJulian dates, 3-17\n\nK\n\nKEEP keyword\n of FIRST function, 5-77\n of LAST function, 5-77\n with aggregate functions, 5-10\n\nkey compression, 16-38\n definition, 10-88\n disabling, 10-88, 14-73\n enabling, 10-86\n of index rebuild, 12-77\n of indexes\n disabling, 10-88\n of index-organized tables, 16-38\n\nkey-preserved tables, 17-21\n\nkeywords, 3-109\n in object names, 3-109\n optional, A-3\n required, A-2\n\nKILL SESSION clause\n of ALTER SYSTEM, 11-64\n\nL\n\nLAG function, 5-93\nlarge object functions, 5-7\nlarge objects. See LOB data types\n\nLAST function, 5-94\nLAST_DAY function, 5-94\nLAST_VALUE function, 5-95\n\nLEAD function, 5-98\nLEADING hint, 3-87\nLEAST function, 5-99\n\nleft outer joins, 19-24\n\nLENGTH function, 5-99\nLENGTH2 function, 5-99\nLENGTH4 function, 5-99\nLENGTHB function, 5-99\nLENGTHC function, 5-99\nless than tests, 7-5\n\nLEVEL clause\n of ALTER DIMENSION, 10-48\n of CREATE DIMENSION, 14-37, 14-38\n\nlevel columns\n specifying default values, 16-30\n\nLEVEL pseudocolumn, 2-2, 19-26\n\nlevels\n adding to a dimension, 10-49\n dropping from a dimension, 10-49\n of dimensions, defining, 14-38\n\nlibraries\n creating, 15-2\n granting system privileges for, 18-41\n re-creating, 15-2\n removing from the database, 17-53\n\nlibrary units. See Java schema objects\n\nLIKE conditions, 7-14\n\nlinear regression functions, 5-166\n\nLIST CHAINED ROWS clause\n of ANALYZE, 13-20\n\nlist partitioning\n adding default partition, 12-64\n adding partitions, 12-64\n adding values, 12-60, 12-61\n creating a default partition, 16-55\n creating partitions, 16-55\n dropping values, 12-60, 12-61\n merging default with nondefault partitions, 12-70\n splitting default partition, 12-67\n\nlist subpartitions\n adding, 12-59\n\nLISTAGG function, 5-100\n\nlisteners\n registering, 11-70\n\nliterals\n datetime, 3-49\n in SQL statements and functions, 3-45\n in SQL syntax, 3-45\n interval, 3-52\n\nLN function, 5-102\n\nLNVL function, 5-102\n\nLOB columns\n adding, 12-41\n compressing, 16-45\n creating from LONG columns, 3-14, 12-46\n deduplication, 16-45\n defining properties\n for materialized views, 15-8\n encrypting, 16-46\n modifying, 12-45\n modifying storage, 12-44\n restricted in joins, 9-11\n restrictions on, 3-25\n storage characteristics of materialized\n\nviews, 11-10\n\nLOB data types, 3-24\nLOB storage clause\nfor partitions, 12-45\nof ALTER MATERIALIZED VIEW, 11-5, 11-10\nof ALTER TABLE, 12-13, 12-44\nof CREATE MATERIALIZED VIEW, 15-8, 15-10,\n15-13, 15-14\nof CREATE TABLE, 16-13, 16-42\n\nLOBs\nattributes, initializing, 3-25\ncolumns\ndifference from LONG and LONG RAW, 3-25\npopulating, 3-25\nexternal, 3-24\ninternal, 3-24\nlocators, 3-25\nlogging attribute, 16-34\nmodifying physical attributes, 12-52\nnumber of bytes manipulated in, 16-44\nsaving old versions, 16-44\nsaving values in a cache, 12-44, 16-61\nspecifying directories for, 14-42\nstorage\nattributes, 16-42\ncharacteristics, 8-46\nin-line, 16-43\ntablespace for\ndefining, 16-33\n\nLOCAL clause\nof CREATE INDEX, 14-66, 14-76\n\nlocal users, 15-59, 17-9\n\nlocale independent, 3-61\n\nlocally managed tablespaces\naltering, 12-93\nstorage attributes, 8-51\n\nlocally partitioned indexes, 14-76\n\nLOCALTIMESTAMP function, 5-103\n\nlocation transparency, 16-2\n\nLOCK ANY TABLE system privilege, 18-45\n\nLOCK TABLE statement, 18-72\n\nlocking, overriding automatic, 18-72\n\nlocks\ndata, B-1\ndictionary, B-4\nrow (TX), B-1\ntable (TM), B-1\n\nlocks. See table locks\n\nlog data\ncollection during update operations, 10-32\n\nlog file clauses\nof ALTER DATABASE, 10-14\n\nlog files\nadding, 10-28\ndropping, 10-28\nmodifying, 10-28\nregistering, 10-36\nrenaming, 10-26\nspecifying for the database, 14-23\n\nLOG function, 5-104\n\nlog groups\nadding, 12-34\ndropping, 12-34\n\nLOGFILE clause\nOF CREATE DATABASE, 14-23\n\nLOGFILE GROUP clause\nof CREATE CONTROLFILE, 14-15\n\nlogging\nand redo log size, 8-39\nspecifying minimal, 8-39\n\nsupplemental\ndropping, 10-33\nsupplemental, adding log groups, 12-34\nsupplemental, dropping log groups, 12-34\n\nLOGGING clause\nof ALTER INDEX, 10-85\nof ALTER MATERIALIZED VIEW, 11-11\nof ALTER MATERIALIZED VIEW LOG, 11-22\nof ALTER TABLE, 12-34\nof ALTER TABLESPACE, 12-97\nof CREATE MATERIALIZED VIEW, 15-13\nof CREATE MATERIALIZED VIEW LOG, 15-29\nof CREATE TABLE, 16-34\nof CREATE TABLESPACE, 16-86\n\nlogical conditions, 7-8\n\nlogical standby database\naborting, 10-38\nactivating, 10-35\nstopping, 10-38\n\nLOGICAL_READS_PER_CALL parameter\nof ALTER PROFILE, 11-32\n\nLOGICAL_READS_PER_SESSION parameter\nof ALTER PROFILE, 11-32\nof ALTER RESOURCE COST, 11-35\n\nLogMiner\nsupplemental logging, 12-34, 16-30\n\nLONG columns\nand domain indexes, 12-46\nconverting to LOB, 3-14, 12-46\nrestrictions on, 3-15\nto store text strings, 3-14\nto store view definitions, 3-14\nwhere referenced from, 3-15\n\nLONG data type, 3-14\nin triggers, 3-15\n\nLONG RAW data type, 3-24\nconverting from CHAR data, 3-24\n\nLONG VARGRAPHIC data type\nDB2, 3-29\nSQL/DS, 3-29\n\nLOWER function, 5-105\n\nLPAD function, 5-105\n\nLTRIM function, 5-106\n\nM\n\nMAKE_REF function, 5-107\n\nMANAGE SCHEDULER system privilege, 18-41\n\nMANAGE TABLESPACE system privilege, 18-45\n\nmanaged recovery\n\nof database, 10-12\nmanaged standby recovery\n as background process, 10-24\n create a logical standby from the physical\n standby, 10-24\n overriding delays, 10-24\n returning control during, 10-24, 10-25\n terminating existing, 10-24, 10-25\nMANAGED STANDBY RECOVERY clause\n of ALTER DATABASE, 10-23\nMAPPING TABLE clause\n of ALTER TABLE, 12-62, 12-76\nmapping tables\n of index-organized tables, 12-76, 16-38\n modifying, 12-40\nmaster databases, 15-3\nmaster tables, 15-3\nMATCHES condition, 7-2\nMATCHES operator, 4-1\nmaterialized join views, 15-26\nmaterialized view logs, 15-26\n creating, 15-26\n excluding new values from, 11-23\n logging changes to, 11-22\n object ID based, 11-23\n parallelizing creation, 15-29\n partition attributes, changing, 11-21\npartitioned, 15-30\nphysical attributes\n changing, 11-21\n specifying, 15-29\npurging, 11-23, 15-32\nremoving from the database, 17-56\nrequired for fast refresh, 15-26\nrowid based, 11-23\nsaving new values in, 11-23\nsaving old values in, 15-31\nstorage attributes\n specifying, 15-29\nmaterialized views, 15-15\n allowing update of, 15-20\n changing from rowid-based to\n primary-key-based, 11-14\n changing to primary-key-based, 11-23\ncomplete refresh, 11-12, 15-17\ncompression of, 11-10, 15-13\nconstraints on, 8-17\ncreating, 15-3\ncreating comments about, 13-44\nfor data warehousing, 15-3\ndegree of parallelism, 11-11, 11-21\n during creation, 15-15\nenabling and disabling query rewrite, 15-20\nexamples, 15-22, 15-32\nfast refresh, 11-12, 15-16, 15-17\nforced refresh, 11-13\ngranting system privileges for, 18-42\nindex characteristics\n changing, 11-10\nindexes that maintain, 15-15\njoin, 15-26\nLOB storage attributes, 11-10\nlogging changes to, 11-11\nmaster table, dropping, 17-55\nobject type, creating, 15-11\npartitions, 11-10\n compression of, 11-10, 15-13\nphysical attributes, 15-13\n changing, 11-10\nprimary key, 15-18\n recording values in master table, 11-22\nquery rewrite\n eligibility for, 8-17\n enabling and disabling, 11-14\nre-creating during refresh, 11-12\nrefresh, 10-38\n after DML on master table, 11-13, 15-17\n mode, changing, 11-12\n on next COMMIT, 11-13, 15-17\n using trusted constraints, 15-19\nrefresh, time, changing, 11-12\nrefreshing, 10-38\nremoving from the database, 17-54\nfor replication, 15-3\nrestricting scope of, 15-12\nretrieving data from, 19-4\nrevalidating, 11-15\nrowid, 15-18\nrowid values\n recording in master table, 11-22\nsaving blocks in a cache, 11-11\nstorage attributes, 15-13\n changing, 11-10\nsubquery, 15-21\nsuppressing creation of default index, 15-15\nsynonyms for, 16-2\nwhen to populate, 15-15\nMAX function, 5-107\nMAXDATAFILES parameter\n of CREATE CONTROLFILE, 14-16\n of CREATE DATABASE, 14-23\nMAXEXTENTS parameter\n of STORAGE clause, 8-53\nMAXINSTANCES parameter\n of CREATE CONTROLFILE, 14-16\n OF CREATE DATABASE, 14-23\nMAXLOGFILES parameter\n of CREATE CONTROLFILE, 14-16\n of CREATE DATABASE, 14-24\nMAXLOGHISTORY parameter\n of CREATE CONTROLFILE, 14-16\n of CREATE DATABASE, 14-24\nMAXLOGMEMBERS parameter\n of CREATE CONTROLFILE, 14-16\n of CREATE DATABASE, 14-24\nMAXSIZE clause\n of ALTER DATABASE, 10-13\nMAXTRANS parameter\n of physical_attributes_clause, 8-46\nMAXVALUE parameter\n\nof ALTER SEQUENCE. *See* CREATE SEQUENCE\n\nof CREATE SEQUENCE, 15-68\n\nmedia recovery\navoid on startup, 10-27\ndesigning, 10-20\ndisabling, 10-25\nfrom specified redo logs, 10-20\nof database, 10-20\nof datafiles, 10-20\nof standby database, 10-20\nof tablespaces, 10-20\nperforming ongoing, 10-23\npreparing for, 10-28\nrestrictions, 10-21\nsustained standby recovery, 10-23\n\nMEDIAN function, 5-109\nmedian values, 5-135\n\nMEMBER conditions, 7-13\nmembership conditions, 7-13, 7-23\n\nMERGE ANY VIEW system privilege, 18-46\n\nMERGE hint, 3-87\n\nMERGE object privilege on a view, 18-51\n\nMERGE PARTITIONS clause\nof ALTER TABLE, 12-70\n\nMERGE statement, 18-75\ndeletes during, 18-77\nerror logging, 18-78\ninserts during, 18-77\nupdates during, 18-77\n\nmerge_insert_clause\nof MERGE, 18-77\n\nmigrated rows\nlisting, 13-20\nof clusters, 13-18\n\nMIN function, 5-111\n\nMINEXTENTS parameter\nof STORAGE clause, 8-52\n\nMINIMIZE RECORDS PER BLOCK clause\nof ALTER TABLE, 12-37\n\nMINIMUM EXTENT clause\nof ALTER TABLESPACE, 12-93\nof CREATE TABLESPACE, 16-86\n\nmining models\nauditing, 13-32\ncomments on, 13-45\n\nMINUS set operator, 4-5, 19-33\n\nMINVALUE parameter\nof ALTER SEQUENCE. *See* CREATE SEQUENCE\nof CREATE SEQUENCE, 15-68\n\nMOD function, 5-112\n\nMODE clause\nof LOCK TABLE, 18-73\n\nMODEL clause\nof SELECT, 19-11, 19-28\n\nmodel conditions, 7-9\nIS ANY, 7-9\nIS PRESENT, 7-10\n\nmodel expression, 6-11\n\nmodel functions, 5-17\n\nMODEL_MIN_ANALYSIS hint, 3-88\n\nMODIFY clause\nof ALTER TABLE, 12-45\n\nMODIFY CONSTRAINT clause\nof ALTER TABLE, 12-11, 12-54\nof ALTER VIEW, 13-13\n\nMODIFY DEFAULT ATTRIBUTES clause\nof ALTER INDEX, 10-82, 10-92\nof ALTER TABLE, 12-56\n\nMODIFY LOB storage clause\nof ALTER MATERIALIZED VIEW, 11-6, 11-10\nof ALTER TABLE, 12-52\n\nMODIFY NESTED TABLE clause\nof ALTER TABLE, 12-10, 12-52\n\nMODIFY PARTITION clause\nof ALTER INDEX, 10-93\nof ALTER MATERIALIZED VIEW, 11-10\nof ALTER TABLE, 12-58\n\nMODIFY scoped_table_ref_constraint clause\nof ALTER MATERIALIZED VIEW, 11-11\n\nMODIFY SUBPARTITION clause\nof ALTER INDEX, 10-83, 10-94\n\nMODIFY VARRAY clause\nof ALTER TABLE, 12-16, 12-53\n\nMON datetime format element, 3-63\n\nMONITOR hint, 3-88\n\nMONITORING USAGE clause\nof ALTER INDEX, 10-91\n\nMONTH datetime format element, 3-63\n\nMONTHS_BETWEEN function, 5-113\n\nMOUNT clause\nof ALTER DATABASE, 10-19\n\nMOVE clause\nof ALTER TABLE, 12-30, 12-76\n\nMOVE ONLINE clause\nof ALTER TABLE, 12-76\n\nMOVE SUBPARTITION clause\nof ALTER TABLE, 12-62\n\nMTS. *See* shared server\n\nmultilevel collections, 16-48\n\nmultiset conditions, 7-11\n\nMULTISET EXCEPT operator, 4-6\n\nMULTISET INTERSECT operator, 4-7\n\nMULTISET keyword\nof CAST function, 5-28\n\nmultiset operators, 4-6\nMULTISET EXCEPT, 4-6\nMULTISET INTERSECT, 4-7\nMULTISET UNION, 4-8\n\nMULTISET UNION operator, 4-8\n\nmultitable inserts, 18-63\nconditional, 18-63\nexamples, 18-68\nunconditional, 18-63\n\nmulti-threaded server. *See* shared server\n\nN\n\nNAME clause\nof SET TRANSACTION, 19-64\n\nNAMED clause\n\nof CREATE JAVA, 14-93\n\nnamespaces\nand object naming rules, 3-110\ndatabase, 3-110\nfor nonschema objects, 3-110\nfor schema objects, 3-110\n\nNANVL function, 5-113\n\nnational character set\nchanging, 10-39\nfixed versus variable width, 3-10\nmultibyte character data, 3-27\nmultibyte character sets, 3-9, 3-10\nvariable-length strings, 3-9\n\nNATIONAL CHARACTER SET parameter\nof CREATE DATABASE, 14-23\n\nnatural joins, 19-25\n\nNCHAR data type, 3-9\n\nNCHR function, 5-114\n\nNCLOB data type, 3-27\ntransactional support of, 3-27\n\nnested subqueries, 9-14\n\nNESTED TABLE clause\nof ALTER TABLE, 12-12, 12-43\nof CREATE TABLE, 16-12, 16-48\n\nnested tables, 3-31, 5-137, 5-179, 7-12\nchanging returned value, 12-52\ncombining, 4-6\ncompared with varrays, 3-40\ncomparison rules, 3-40\ncreating, 17-3\ncreating from existing columns, 5-39\ndefining as index-organized tables, 12-43\ndetermining hierarchy, 7-13\ndropping the body of, 18-15\ndropping the specification of, 18-13\nin materialized views, 15-8, 15-9\nindexing columns of, 14-70\nmodifying, 12-52\nmodifying column properties, 12-12\nmultilevel, 16-48\npartitioned nested table columns, 12-68\nstorage characteristics of, 12-43, 16-48\n\nNEW_TIME function, 5-115\n\nNEXT clause\nof ALTER MATERIALIZED VIEW ...\nREFRESH, 11-13\n\nNEXT parameter\nof STORAGE clause, 8-51\n\nNEXT_DAY function, 5-116\n\nNEXTVAL pseudocolumn, 2-3, 15-66\n\nNLS character functions, 5-5\n\nNLS_CHARSET_DECL_LEN function, 5-116\n\nNLS_CHARSET_ID function, 5-117\n\nNLS_CHARSET_NAME function, 5-117\n\nNLS_DATE_LANGUAGE initialization parameter, 3-64\n\nNLS_INITCAP function, 5-118\n\nNLS_LANGUAGE initialization parameter, 3-64, 9-10\n\nNLS_LENGTH_SEMANTICS initialization parameter overriding, 3-9\n\nNLS_LOWER function, 5-119\n\nNLS_SORT initialization parameter, 9-10\n\nNLS_TERRITORY initialization parameter, 3-64\n\nNLS_UPPER function, 5-119\n\nNLSSORT function, 5-120\n\nNO FORCE LOGGING clause\nof ALTER DATABASE, 10-29\nof ALTER TABLESPACE, 12-97\n\nNO_EXPAND hint, 3-89\n\nNO_FACT hint, 3-89\n\nNO_INDEX hint, 3-90\n\nNO_INDEX_FFS hint, 3-90\n\nNO_INDEX_SS hint, 3-90\n\nNO_MERGE hint, 3-91\n\nNO_MONITOR hint, 3-91\n\nNO_PARALLEL hint, 3-91\n\nNO_PARALLEL_INDEX, 3-92\n\nNO_PUSH_PRED hint, 3-92\n\nNO_PUSH_SUBQ hint, 3-92\n\nNO_PX_JOIN_FILTER hint, 3-93\n\nNO_QUERY_TRANSFORMATION hint, 3-93\n\nNO_RESULT_CACHE hint, 3-93\n\nNO_REWRITE hint, 3-93\n\nNO_STAR_TRANSFORMATION hint, 3-94\n\nNO_STATEMENT_QUEUING hint, 3-94\n\nNO_UNNEST hint, 3-94\n\nNO_USE_HASH hint, 3-94\n\nNO_USE_MERGE hint, 3-94\n\nNO_USE_NL hint, 3-95\n\nNO_XML_QUERY_REWRITE hint, 3-95\n\nNO_XMLINDEX_REWRITE hint, 3-95\n\nNOAPPEND hint, 3-89\n\nNOARCHIVELOG clause\nof ALTER DATABASE, 10-14, 10-29\nof CREATE CONTROLFILE, 14-16\nOF CREATE DATABASE, 10-20, 14-25\n\nNOAUDIT statement, 18-80\n\nlocks, B-5\n\nNOCACHE clause\nof ALTER CLUSTER, 10-7\nof ALTER MATERIALIZED VIEW, 11-11\nof ALTER MATERIALIZED VIEW LOG, 11-22\nof ALTER SEQUENCE. See CREATE SEQUENCE\nof ALTER TABLE, 16-61\nof CREATE CLUSTER, 14-7\nof CREATE MATERIALIZED VIEW, 15-15\nof CREATE MATERIALIZED VIEW LOG, 15-29\nof CREATE SEQUENCE, 15-69\n\nNOCACHE hint, 3-89\n\nNOCOMPRESS clause\nof ALTER INDEX ... REBUILD, 10-88\nof CREATE INDEX, 14-73\nof CREATE TABLE, 16-38\n\nNOCYCLE parameter\nof ALTER SEQUENCE. See CREATE SEQUENCE, 11-43\nof CREATE SEQUENCE, 15-68\n\nNOFORCE clause\nof CREATE JAVA, 14-92\n\nof CREATE VIEW, 17-17\n\nNOLOGGING mode\nand force logging mode, 8-38\nfor nonpartitioned objects, 8-38\nfor partitioned objects, 8-38\n\nNOMAXVALUE parameter\nof ALTER SEQUENCE. See CREATE SEQUENCE\nof CREATE SEQUENCE, 15-68\n\nNOMINIMIZE RECORDS PER BLOCK clause\nof ALTER TABLE, 12-37\n\nNOMINVALUE parameter\nof ALTER SEQUENCE. See CREATE\nSEQUENCE, 11-43\nof CREATE SEQUENCE, 15-68\n\nNOMONITORING USAGE clause\nof ALTER INDEX, 10-91\n\nNONE clause\nof SET ROLE, 19-62\n\nnonempty subsets of, 5-137\n\nnonequivalency tests, 7-24\n\nnonschema objects\nlist of, 3-107\nnamespaces, 3-110\n\nNOORDER parameter\nof ALTER SEQUENCE. See CREATE\nSEQUENCE, 11-43\nof CREATE SEQUENCE, 15-69\n\nNOPARALLEL clause\nof CREATE INDEX, 8-42, 16-62\n\nNOPARALLEL hint, 3-91\n\nNOPARALLEL_INDEX hint, 3-92\n\nNORELY clause\nof constraints, 8-17\n\nNORESETLOGS clause\nof CREATE CONTROLFILE, 14-15\n\nNOREVERSE parameter\nof ALTER INDEX ... REBUILD, 10-87, 10-89\n\nNOREWRITE hint, 3-93\n\nNOROWDEPENDENCIES clause\nof CREATE CLUSTER, 14-7\nof CREATE TABLE, 16-63\n\nNOSORT clause\nof ALTER INDEX, 14-73\n\nNOT condition, 7-8, 7-9\n\nNOT DEFERRABLE clause\nof constraints, 8-14\n\nNOT IDENTIFIED clause\nof ALTER ROLE. See CREATE ROLE\nof CREATE ROLE, 15-59\n\nNOT IN subqueries\nconverting to NOT EXISTS subqueries, 5-102\n\nNOT NULL clause\nof CREATE TABLE, 16-30\n\nNOWAIT clause\nof LOCK TABLE, 18-74\n\nNTH_VALUE function, 5-122\n\nNTILE function, 5-123\n\nnull, 3-70\ndifference from zero, 3-70\nin conditions, 3-71\ntable of, 3-71\nin functions, 5-2\nwith comparison conditions, 3-70\n\nnull conditions, 7-19\n\nNULLIF function, 5-124\nas a form of CASE expression, 5-124\n\nNULL-related functions, 5-9\n\nNUMBER data type, 3-10\nconverting to VARCHAR2, 3-56\nprecision, 3-10\nscale, 3-10\n\nnumber format models, 3-56\n\nnumber functions, 5-3\n\nnumbers\ncomparison rules, 3-37\nfloating-point, 3-10, 3-13\nin SQL syntax, 3-47\nprecision of, 3-48\nspelling out, 3-65\nsyntax of, 3-47\n\nnumeric functions, 5-3\nnumeric precedence, 3-14\n\nNUMTODSINTERVAL function, 5-125\n\nNUMTOYMINTERVAL function, 5-125\n\nNVARCHAR2 data type, 3-9\n\nNVL function, 5-126\n\nNVL2 function, 5-127\n\nO\n\nobject access expressions, 6-13\n\nOBJECT IDENTIFIER clause\nof CREATE TABLE, 16-67\n\nobject identifiers\ncontained in REFs, 3-30\nof object views, 17-19\nprimary key, 16-67\nspecifying, 16-67\nspecifying an index on, 16-68\nsystem-generated, 16-67\n\nobject instances\ntypes of, 7-25\n\nobject privileges\nFLASHBACK ARCHIVE, 18-48\ngranting, 15-58\nmultiple, 15-64\non specific columns, 18-38\non a database object\nrevoking, 18-93\nrevoking, 18-90\nfrom a role, 18-88, 18-92\nfrom a user, 18-88, 18-91\nfrom PUBLIC, 18-92\n\nobject reference functions, 5-17\n\nobject tables\nadding rows to, 18-54\nas part of hierarchy, 16-67\ncreating, 16-8, 16-67\nquerying, 16-67\nsystem-generated column name, 16-67, 16-68,\n\n17-19, 17-21\nupdating to latest version, 12-36\nupgrading, 12-36\n\nobject type columns\ndefining properties\nfor materialized views, 15-8\nin a type hierarchy, 16-41\nmembership in hierarchy, 12-43\nmodifying properties\nfor tables, 12-12, 12-43\nsubstitutability, 12-43\n\nobject type materialized views\ncreating, 15-11\n\nobject types, 3-30\nassociating statistics types with, 13-23\nattributes, 3-118\nin a type hierarchy, 16-41\nmembership in hierarchy, 12-43\nsubstitutability, 12-43\n\nbodies\ncreating, 17-5\nre-creating, 17-6\n\ncomparison rules, 3-39\nMAP function, 3-39\nORDER function, 3-39\n\ncomponents of, 3-30\ncreating, 17-3\n\ndefining member methods of, 17-5\ndisassociating statistics types from, 17-34, 18-13\ndropping the body of, 18-15\ndropping the specification of, 18-13\ngranting system privileges for, 18-45\n\nidentifiers, 2-7\nincomplete, 17-3\nmethods, 3-118\nprivileges on subtypes, 18-38\nreferences to. See REFs\nstatistics types, 13-23\nvalues of, 2-8\n\nobject views, 17-18\nbase tables\nadding rows, 18-54\ncreating, 17-19\ncreating subviews, 17-19\ndefining, 17-14\nquerying, 17-18\n\nOBJECT_ID pseudocolumn, 2-7, 16-67, 16-68, 17-19, 17-21\n\nOBJECT_VALUE pseudocolumn, 2-8\n\nobjects. See object types or database objects\n\nODCIndexInsert method\nindextype support of, 10-98, 14-89\n\nOF clause\nof CREATE VIEW, 17-19\n\nOFFLINE clause\nof ALTER TABLESPACE, 12-98\nof CREATE TABLESPACE, 16-88\n\nOIDINDEX clause\nof CREATE TABLE, 16-68\n\nOIDs. See object identifiers\n\nOLAP functions, 5-17\n\nOLTP table compression, 16-34\n\nON clause\nof CREATE OUTLINE, 15-39\n\nON COMMIT clause\nof CREATE TABLE, 16-31\n\nON COMMIT REFRESH object privilege\non a materialized view, 18-49\n\nON COMMIT REFRESH system privilege, 18-42\n\nON DEFAULT clause\nof AUDIT, 13-32\nof NOAUDIT, 18-82\n\nON DELETE CASCADE clause\nof constraints, 8-11\n\nON DELETE SET NULL clause\nof constraints, 8-11\n\nON DIRECTORY clause\nof AUDIT, 13-32\nof NOAUDIT, 18-82\n\nON MINING MODEL clause\nof AUDIT, 13-32\n\nON object clause\nof NOAUDIT, 18-82\nof REVOKE, 18-93\n\nON PREBUILT TABLE clause\nof CREATE MATERIALIZED VIEW, 15-12\n\nonline backup\nof tablespaces, ending, 12-95\n\nONLINE clause\nof ALTER TABLESPACE, 12-98\nof CREATE INDEX, 14-74\nof CREATE TABLESPACE, 16-88\n\nonline indexes, 14-74\nrebuilding, 12-76\n\nONLINE parameter\nof ALTER INDEX ... REBUILD, 10-88\n\nonline redo logs\nreinitializing, 10-29\n\nOPEN clause\nof ALTER DATABASE, 10-19\n\nOPEN READ ONLY clause\nof ALTER DATABASE, 10-20\n\nOPEN READ WRITE clause\nof ALTER DATABASE, 10-19\n\noperands, 4-1\n\noperating system files\ndropping, 18-11\nremoving, 10-28\n\noperators, 4-1\nadding to indextypes, 10-98\naltering, 11-25\narithmetic, 4-3\nbinary, 4-2\ncomments on, 13-45\nconcatenation, 4-4\nCONNECT_BY_ROOT, 4-5\ndropping from indextypes, 10-98\ngranting system privileges for, 18-43\nMULTISET EXCEPT, 4-6\nMULTISET INTERSECT, 4-7\n\nMULTISET UNION, 4-8\nprecedence, 4-2\nPRIOR, 4-5\nset, 4-5, 19-33\nspecifying implementation of, 15-34\nunary, 4-2\nuser-defined, 4-9\nbinding to a function, 11-26, 15-35\ncompiling, 11-25\ncreating, 15-34\ndropping, 17-58\nhow bindings are implemented, 15-35\nimplementation type, 15-36\nreturn type of binding, 15-35\nOPT_PARAM hint, 3-96\nOPTIMAL parameter\nof STORAGE clause, 8-54\nOR condition, 7-8, 7-9\nOR REPLACE clause\nof CREATE CONTEXT, 14-9\nof CREATE DIRECTORY, 14-43\nof CREATE FUNCTION, 14-60, 14-92\nof CREATE LIBRARY, 15-2\nof CREATE OUTLINE, 15-38\nof CREATE PACKAGE, 15-42\nof CREATE PACKAGE BODY, 15-44\nof CREATE PROCEDURE, 15-48\nof CREATE TRIGGER, 16-95\nof CREATE TYPE, 17-4\nof CREATE TYPE BODY, 17-6\nof CREATE VIEW, 17-16\nORA_DST_AFFECTED function, 5-128\nORA_DST_CONVERT function, 5-129\nORA_DST_ERROR function, 5-129\nORA_HASH function, 5-130\nORA_ROWSCN pseudocolumn, 2-8\nOracle ASM volumes, 10-67\nOracle Automatic Storage Management\nmigrating nodes in a cluster, 11-66\nOracle Call Interface, 1-3\nOracle Expression Filter\nconditions, 7-2\noperators, 4-1\nOracle reserved words, E-1\nOracle Text\nbuilt-in conditions, 7-2\nCATSEARCH, 7-2\nCONTAINS, 7-2\ncreating domain indexes, 14-78\nMATCHES, 7-2\noperators, 4-1\nCATSEARCH, 4-1\nCONTAINS, 4-1\nMATCHES, 4-1\nSCORE, 4-1\nOracle Tools\nsupport of SQL, 1-3\nORDAudio data type, 3-35\nORDDicom data type, 3-35\nORDDoc data type, 3-35\n\nORDER BY clause\nof queries, 9-10\nof SELECT, 9-10, 19-13, 19-33\nwith ROWNUM, 2-10\nORDER clause\nof ALTER SEQUENCE. See CREATE SEQUENCE\nORDER parameter\nof CREATE SEQUENCE, 15-69\nORDER SIBLINGS BY clause\nof SELECT, 19-33\nORDERED hint, 3-96\nORDImage data type, 3-35\nORDImageSignature data type, 3-36\nordinal numbers\nspecifying, 3-65\nspelling out, 3-65\nORDVideo data type, 3-35\nORGANIZATION EXTERNAL clause\nof CREATE TABLE, 16-37, 16-39\nORGANIZATION HEAP clause\nof CREATE TABLE, 16-37\nORGANIZATION INDEX clause\nof CREATE TABLE, 16-37\nouter joins, 9-12\nrestrictions, 9-13\noutlines\nassign to a different category, 11-29\nassigning to a different category, 11-28, 11-30\ncopying, 15-39\ncreating, 15-37\ncreating on statements, 15-39\ndropping from the database, 17-59\nenabling and disabling dynamically, 15-38\nfor use by current session, 15-38\nfor use by PUBLIC, 15-38\ngranting system privileges for, 18-43\nprivate, use by the optimizer, 11-54\nrebuilding, 11-28, 11-30\nrecompiling, 11-29\nrenaming, 11-28, 11-29, 11-30\nreplacing, 15-38\nstoring groups of, 15-39\nuse by the optimizer, 11-72\nuse to generate execution plans, 11-54\nused to generate execution plans, 15-37\nout-of-line constraints\nof CREATE TABLE, 16-30\nOVER clause\nof analytic functions, 5-12\nOVERFLOW clause\nof ALTER INDEX, 10-83\nof ALTER TABLE, 12-39\nof CREATE TABLE, 16-38\n\nP\npackage bodies\ncreating, 15-43\nre-creating, 15-44\nremoving from the database, 17-61\n\npackaged procedures\n dropping, 17-63\n\npackages\n associating statistics types with, 13-23\n creating, 15-41\n disassociating statistics types from, 17-34, 17-61\n redefining, 15-42\n removing from the database, 17-61\n synonyms for, 16-2\n\nPACKAGES clause\n of ASSOCIATE STATISTICS, 13-23, 13-24\n of DISASSOCIATE STATISTICS, 17-34\n\nPARALLEL clause\n of ALTER CLUSTER, 10-6, 10-7\n of ALTER INDEX, 10-85\n of ALTER MATERIALIZED VIEW, 11-7, 11-11\n of ALTER MATERIALIZED VIEW LOG, 11-20, 11-21\n of ALTER TABLE, 12-75\n of CREATE CLUSTER, 14-6\n of CREATE INDEX, 14-75\n of CREATE MATERIALIZED VIEW, 15-11, 15-15\n of CREATE MATERIALIZED VIEW LOG, 15-28, 15-29\n of CREATE TABLE, 16-24, 16-62\n\nparallel execution, 8-41\n hints, 3-96\n of DDL statements, 11-46\n of DML statements, 11-46\n\nPARALLEL hint, 3-96\n\nPARALLEL_INDEX hint, 3-98\n\nparameter files\n creating, 15-45\n from memory, 15-46\n\nparameters\n in syntax\n optional, A-3\n required, A-2\n\nPARAMETERS clause\n of CREATE INDEX, 14-79\n\nPARTITION ... LOB storage clause\n of ALTER TABLE, 12-45\n\nPARTITION BY HASH clause\n of CREATE TABLE, 16-18, 16-54\n\nPARTITION BY LIST clause\n of CREATE TABLE, 16-19, 16-55\n\nPARTITION BY RANGE clause\n of CREATE TABLE, 16-18, 16-52\n\nPARTITION BY REFERENCE clause\n of CREATE TABLE, 16-19, 16-55\n\nPARTITION clause\n of ANALYZE, 13-17\n of CREATE INDEX, 14-76\n of CREATE TABLE, 16-53\n of DELETE, 17-29\n of INSERT, 18-59\n of LOCK TABLE, 18-73\n of UPDATE, 19-75\n\npartitioned indexes, 3-116, 14-61, 14-76\n local, creating, 14-66\n\nuser-defined, 14-75\n\npartitioned index-organized tables\n secondary indexes, updating, 10-93\n\npartitioned tables, 3-116\n\npartition-extended table names\n in DML statements, 3-117\n restrictions on, 3-118\n syntax, 3-117\n\npartitioning\n by hash, 16-18, 16-54\n by list, 16-19, 16-55\n by range, 16-18, 16-52\n by reference, 16-19, 16-55\n\nclauses\n of ALTER INDEX, 10-81\n of ALTER TABLE, 12-56\n\ninterval, 16-52\n\nof materialized view logs, 11-21, 15-30\nof materialized views, 11-10, 15-6, 15-14\n\nrange with interval partitions, 16-52\n\nreferential constraint, 12-54, 16-56\n\nsystem, 16-60\n\npartitions\n adding, 12-56\n adding rows to, 18-54\n allocating extents for, 12-35\n based on literal values, 16-55\n\ncomposite\n specifying, 16-56\n\nconverting into nonpartitioned tables, 12-71\n\ndeallocating unused space from, 12-35\n\ndropping, 12-65\n\nexchanging with tables, 12-26\n\nextents\n allocating for an index, 10-84\n\nhash\n adding, 12-64\n coalescing, 12-65\n specifying, 16-54\n\nindex, 14-75\n\ninserting rows into, 18-59\n\nlist, adding, 12-64\n\nLOB storage characteristics of, 12-45\n\nlocking, 18-72\n\nlogging attribute, 16-34\n\nlogging insert operations, 12-34\n\nmerging, 12-70\n\nmodifying, 12-56, 12-58\n\nphysical attributes\n changing, 12-33\n\nrange\n adding, 12-63\n specifying, 16-52\n\nremoving rows from, 12-66, 17-29\n\nrenaming, 12-66\n\nrevising values in, 19-75\n\nsplitting, 12-67\n\nstorage characteristics, 8-46\n\ntablespace for\n defining, 16-33\n\nPASSWORD EXPIRE clause\n of ALTER USER. *See* CREATE USER\n of CREATE USER, 17-12\n\nPASSWORD_GRACE_TIME parameter\n of ALTER PROFILE, 11-33\n of CREATE PROFILE, 15-53\n\nPASSWORD_LIFE_TIME parameter\n of ALTER PROFILE, 11-33\n of CREATE PROFILE, 15-52\n\nPASSWORD_LOCK_TIME parameter\n of ALTER PROFILE, 11-33\n of CREATE PROFILE, 15-53\n\nPASSWORD_REUSE_MAX parameter\n of ALTER PROFILE, 11-33\n of CREATE PROFILE, 15-52\n\nPASSWORD_REUSE_TIME parameter\n of ALTER PROFILE, 11-33\n of CREATE PROFILE, 15-52\n\nPASSWORD_VERIFY_FUNCTION parameter\n of ALTER PROFILE, 11-33\n of CREATE PROFILE, 15-53\n\npasswords\n expiration of, 17-12\n grace period, 15-52\n guaranteeing complexity, 15-52\n limiting use and reuse, 15-52\n locking, 15-52\n making unavailable, 15-52\n\nparameters\n of CREATE PROFILE, 15-50\n\nspecial characters in, 17-9\n\nPATH function, 5-131\n\nPATH_VIEW, 7-20, 7-21\n\npattern-matching conditions, 7-14\n\nPCT_ACCESS_DIRECT statistics\n for index-organized tables, 13-17\n\nPCTFREE parameter\n of ALTER CLUSTER, 10-6\n of ALTER INDEX, 10-85\n of ALTER MATERIALIZED VIEW LOG, 11-19\n of ALTER TABLE, 12-33\n of CREATE MATERIALIZED VIEW LOG. *See* CREATE TABLE.\n\nof CREATE MATERIALIZED VIEW. *See* CREATE TABLE.\n\nof CREATE TABLE, 8-45\n\nPCTINCREASE parameter\n of STORAGE clause, 8-52\n\nPCTTHRESHOLD parameter\n of CREATE TABLE, 16-38\n\nPCTUSED parameter\n of ALTER CLUSTER, 10-6\n of ALTER INDEX, 10-85\n of ALTER MATERIALIZED VIEW LOG, 11-19\n of ALTER TABLE, 12-33\n of CREATE INDEX. *See* CREATE TABLE\n of CREATE MATERIALIZED VIEW LOG. *See* CREATE TABLE.\n\nof CREATE MATERIALIZED VIEW. *See* CREATE TABLE.\n\nof CREATE TABLE, 8-45\n\nPCTVERSION parameter\n of LOB storage, 16-44\n of LOB storage clause, 12-52\n\nPERCENT_RANK function, 5-131\n\nPERCENTILE_CONT function, 5-133\n\nPERCENTILE_DISC function, 5-135\n\nPERMANENT clause\n of ALTER TABLESPACE, 12-99\n\nphysical attributes clause\n of ALTER CLUSTER, 10-5\n of ALTER INDEX, 10-85\n of ALTER MATERIALIZED VIEW LOG, 11-19\n of ALTER TABLE, 12-33\n of CREATE CLUSTER, 14-3\n of CREATE MATERIALIZED VIEW, 15-7\n of CREATE TABLE, 16-16, 16-33\n\nphysical standby database\n activating, 10-35\n converting to snapshot standby database, 10-38\n\npivot operations, 19-21\n examples, 19-48\n syntax, 19-7\n\nplaceholder expressions, 6-14\n\nplan management\n granting system privileges for, 18-43\n plan stability, 15-37\n\nPLAN_TABLE sample table, 18-20\n\nP.M. datetime format element, 3-63\n\nPM datetime format element, 3-63\n\nPOSIX regular expression standard, D-1\n\nPOWER function, 5-136\n\nPOWERMULTISET function, 5-137\n\nPOWERMULTISET_BY_CARDINALITY function, 5-138\n\nPQ_DISTRIBUTE hint, 3-99\n\nprecedence\n of conditions, 7-3\n of numbers, 3-14\n of operators, 4-2\n\nprecision\n number of digits of, 3-48\n of NUMBER data type, 3-10\n\nprecompilers, 1-3\n\npredefined roles, 18-36\n\nPREDICTION function, 5-139\n\nPREDICTION_BOUNDS function, 5-141\n\nPREDICTION_COST function, 5-142\n\nPREDICTION_DETAILS function, 5-144\n\nPREDICTION_PROBABILITY function, 5-145\n\nPREDICTION_SET function, 5-147\n\nPREPARE TO SWITCHOVER clause\n of ALTER DATABASE, 10-36\n\nPRESENTNNV function, 5-149\n\nPRESENTV function, 5-150\n\npretty-printing of XML output, 5-265\n\nPREVIOUS function, 5-152\n\nprimary database\n converting to physical standby database, 10-38\n\nPRIMARY KEY clause\n\nof constraints, 8-9\nof CREATE TABLE, 16-30\nprimary key constraints, 8-9\nenabling, 16-63\nindex on, 16-64\nprimary keys\ngenerating values for, 15-66\nPRIOR clause\nof hierarchical queries, 9-3\nPRIOR operator, 4-5\nPRIVATE clause\nof CREATE OUTLINE, 15-38\nprivate outlines\nuse by the optimizer, 11-54\nPRIVATE_SGA parameter\nof ALTER PROFILE, 11-32\nof ALTER RESOURCE COST, 11-36\nprivileges\non subtypes of object types, 18-38\nrevoking from a grantee, 18-89\nSee also system privileges or object privileges\nprocedures\n3GL calling, 15-2\ncalling, 13-40\ncreating, 15-47\nexecuting, 13-40\nexternal, 15-47\ngranting system privileges for, 18-44\ninvalidating local objects dependent on, 17-63\nissuing COMMIT or ROLLBACK statements, 11-46\nnaming rules, 3-111\nrecompiling, 11-31\nre-creating, 15-48\nremoving from the database, 17-63\nsynonyms for, 16-2\nPROFILE clause\nof ALTER USER. See CREATE USER\nof CREATE USER, 17-11\nprofiles\nadding resource limits, 11-32\nassigning to a user, 17-11\nchanging resource limits, 11-32\ncreating, 15-49\nexamples, 15-53\ndeassigning from users, 17-64\ndropping resource limits, 11-32\ngranting system privileges for, 18-44\nmodifying, examples, 11-33\nremoving from the database, 17-64\nproxy clause\nof ALTER USER, 13-6, 13-9\npseudocolumns, 2-1\nCOLUMN_VALUE, 2-6\nCONNECT_BY_ISCYCLE, 2-1\nCONNECT_BY_ISLEAF, 2-2\nCURRVAL, 2-3\nflashback queries, 2-5\nin hierarchical queries, 2-1\nLEVEL, 2-2\nNEXTVAL, 2-3\nOBJECT_ID, 2-7, 16-67, 16-68, 17-19, 17-21\nOBJECT_VALUE, 2-8\nORA_ROWSCN, 2-8\nROWID, 2-9\nROWNUM, 2-10\nversion queries, 2-5\nXMLDATA, 2-11\nPUBLIC clause\nof CREATE OUTLINE, 15-38\nof CREATE SYNONYM, 16-3\nof DROP DATABASE LINK, 17-40\npublic database links\ndropping, 17-40\npublic synonyms, 16-3\ndropping, 18-3\nPURGE statement, 18-84\nPUSH_PRED hint, 3-101\nPUSH_SUBQ hint, 3-101\nPX_JOIN_FILTER hint, 3-102\n\nQ\nQB_NAME hint, 3-102\nqueries, 9-1, 19-4\ncomments in, 9-2\ncompound, 9-10\ncorrelated\nleft correlation, 19-20\ndefault locking of, B-3\ndefined, 9-1\ndistributed, 9-16\ngrouping returned rows on a value, 19-27\nhierarchical. See hierarchical queries\nhierarchical, ordering, 19-33\nhints in, 9-2\njoin, 9-11, 19-23\nlocking rows during, 19-34\nmultiple versions of rows, 19-17\nof past data, 19-17\nordering returned rows, 19-33\nouter joins in, 19-20\nreferencing multiple tables, 9-11\nselect lists of, 9-2\nselecting all columns, 19-15\nselecting from a random sample of rows, 19-19\nsorting results, 9-10\nsyntax, 9-1\ntop-level, 9-1\ntop-N, 2-10\nquery rewrite\nand dimensions, 14-37\ndefined, 19-4\nQUERY REWRITE object privilege\non a materialized view, 18-49\nQUERY REWRITE system privilege, 18-42\nQUIESCE RESTRICTED clause\nof ALTER SYSTEM, 11-67\nQUOTA clause\nof ALTER USER. See CREATE USER\n\nrange conditions, 7-22\n\nrange partitioning\nconverting to interval partitioning, 12-57\nrange partitions\nadding, 12-63\ncreating, 16-52\nvalues of, 16-53\n\nRANK function, 5-152\n\nRATIO_TO_REPORT function, 5-154\n\nRAW data type, 3-24\nconverting from CHAR data, 3-24\n\nRAWTOHEX function, 5-155\n\nRAWTONHEX function, 5-156\n\nREAD object privilege\non a materialized directory, 18-48\n\nREAD ONLY clause\nof ALTER TABLESPACE, 12-99\nof ALTER VIEW, 13-14\n\nREAD WRITE clause\nof ALTER TABLESPACE, 12-99\nof ALTER VIEW, 13-14\n\nREBUILD clause\nof ALTER INDEX, 10-86\nof ALTER OUTLINE, 11-29\n\nREBUILD PARTITION clause\nof ALTER INDEX, 10-87\n\nREBUILD SUBPARTITION clause\nof ALTER INDEX, 10-87\n\nREBUILD UNUSABLE LOCAL INDEXES clause\nof ALTER TABLE, 12-73\n\nRECOVER AUTOMATIC clause\nof ALTER DATABASE, 10-21\n\nRECOVER CANCEL clause\nof ALTER DATABASE, 10-11, 10-23\n\nRECOVER clause\nof ALTER DATABASE, 10-20\n\nRECOVER CONTINUE clause\nof ALTER DATABASE, 10-11, 10-23\n\nRECOVER DATABASE clause\nof ALTER DATABASE, 10-11, 10-21\n\nRECOVER DATAFILE clause\nof ALTER DATABASE, 10-11, 10-22\n\nRECOVER LOGFILE clause\nof ALTER DATABASE, 10-11, 10-22\n\nRECOVER MANAGED STANDBY DATABASE\nclause\nof ALTER DATABASE, 10-12\n\nRECOVER TABLESPACE clause\nof ALTER DATABASE, 10-11, 10-22\n\nRECOVERABLE, 10-86, 16-36\nSee also LOGGING clause\n\nrecovery\ndiscarding data, 10-19\ndistributed, enabling, 11-64\ninstance, continue after interruption, 10-20\nmedia, designing, 10-20\nmedia, performing ongoing, 10-23\nof database, 10-11\n\nrecovery clauses\nof ALTER DATABASE, 10-10\n\nrecursive subquery factoring, 19-13\n\nrecycle bin\npurging objects from, 18-84\n\nredo log files\nspecifying, 8-29\nspecifying for a control file, 14-13\n\nredo logs, 10-19\nadding, 10-28, 10-30\napplying to logical standby database, 10-37\narchive location, 11-62\nautomatic archiving, 11-61\nautomatic name generation, 10-20, 10-21\nclearing, 10-28\ndropping, 10-28, 10-31\nenabling and disabling thread, 10-28\nmanual archiving, 11-61\nall, 11-62\nby group number, 11-62\nby SCN, 11-61\ncurrent, 11-62\nnext, 11-62\nwith sequence numbers, 11-61\n\nmembers\nadding to existing groups, 10-31\ndropping, 10-32\nrenaming, 10-26\n\nremove changes from, 10-19\n\nreusing, 8-35\n\nsize of, 8-34\nspecifying, 8-29, 14-23\nfor media recovery, 10-22\nspecifying archive mode, 14-25\nswitching groups, 11-66\n\nREF columns\nrescoping, 11-11\nspecifying, 16-30\nspecifying from table or column, 16-30\n\nREF constraints\ndefining scope, for materialized views, 11-9\nof ALTER TABLE, 12-43\n\nREF function, 5-156\n\nreference partitioning, 16-55\n\nreference-partitioned tables, 12-56\nmaintenance operations, 12-73\n\nREFERENCES clause\nof CREATE TABLE, 16-30\n\nREFERENCES object privilege\non a table, 18-51\non a view, 18-51\n\nreferential integrity constraints, 8-10\n\nREFRESH clause\nof ALTER MATERIALIZED VIEW, 11-9, 11-12\nof CREATE MATERIALIZED VIEW, 15-7\n\nREFRESH COMPLETE clause\nof ALTER MATERIALIZED VIEW, 11-12\nof CREATE MATERIALIZED VIEW, 15-16\n\nREFRESH FAST clause\n of ALTER MATERIALIZED VIEW, 11-12\n of CREATE MATERIALIZED VIEW, 15-16\n\nREFRESH FORCE clause\n of ALTER MATERIALIZED VIEW, 11-13\n of CREATE MATERIALIZED VIEW, 15-16\n\nREFRESH ON COMMIT clause\n of ALTER MATERIALIZED VIEW, 11-13\n of CREATE MATERIALIZED VIEW, 15-16\n\nREFRESH ON DEMAND clause\n of ALTER MATERIALIZED VIEW, 11-13\n of CREATE MATERIALIZED VIEW, 15-16\n\nREFs, 3-30, 8-12\n as containers for object identifiers, 3-30\n dangling, 13-19\n updating, 13-19\n validating, 13-19\n\nREFTOHEX function, 5-157\n\nREGEXP_COUNT function, 5-158\n\nREGEXP_INSTR function, 5-159\n\nREGEXP_LIKE condition, 7-18\n\nREGEXP_REPLACE function, 5-162\n\nREGEXP_SUBSTR function, 5-164\n\nREGISTER clause\n of ALTER SYSTEM, 11-70\n\nREGISTER LOGFILE clause\n of ALTER DATABASE, 10-36\n\nREGR_AVGX function, 5-166\n\nREGR_AVGY function, 5-166\n\nREGR_COUNT function, 5-166\n\nREGR_INTERCEPT function, 5-166\n\nREGR_R2 function, 5-166\n\nREGR_SLOPE function, 5-166\n\nREGR_SXX function, 5-166\n\nREGR_SXY function, 5-166\n\nREGR_SYY function, 5-166\n\nregular expressions\n multilingual syntax, D-1\n operators, multilingual enhancements, D-2\n Oracle support of, D-1\n Perl-influenced operators, D-3\n subexpressions, 5-160, 5-165\n\nrelational tables\n creating, 16-7, 16-25\n\nRELY clause\n of constraints, 8-17\n\nREMAINDER function, 5-170\n\nRENAME clause\n of ALTER INDEX, 10-91\n of ALTER OUTLINE, 11-29\n of ALTER TABLE, 12-38\n of ALTER TABLESPACE, 12-94\n of ALTER TRIGGER, 13-3\n\nRENAME CONSTRAINT clause\n of ALTER TABLE, 12-54\n\nRENAME DATAFILE clause\n of ALTER TABLESPACE, 12-95\n\nRENAME FILE clause\n of ALTER DATABASE, 10-10, 10-26\n\nRENAME GLOBAL_NAME clause\n of ALTER DATABASE, 10-40\n\nRENAME PARTITION clause\n of ALTER INDEX, 10-93\n of ALTER TABLE, 12-66\n\nRENAME statement, 18-86\n\nRENAME SUBPARTITION clause\n of ALTER INDEX, 10-93\n of ALTER TABLE, 12-66\n\nREPLACE function, 5-171\n\nreplication\n row-level dependency tracking, 14-7, 16-63\n\nreserved words, 3-109, E-1\n\nRESET COMPATIBILITY clause\n of ALTER DATABASE, 10-9\n\nreset sequence of, 10-19\n\nRESETLOGS parameter\n of CREATE CONTROLFILE, 14-15\n\nRESOLVE clause\n of ALTER JAVA CLASS, 10-101\n of CREATE JAVA, 14-92\n\nRESOLVER clause\n of ALTER JAVA CLASS, 10-101\n of ALTER JAVA SOURCE, 10-101\n of CREATE JAVA, 14-94\n\nResource Manager, 11-67\n\nresource parameters\n of CREATE PROFILE, 15-50\n\nRESOURCE_VIEW, 7-20, 7-21\n\nresponse time\n optimizing, 3-81\n\nrestore points\n guaranteed, 15-56\n preserved, 15-56\n using\n to flash back a table, 18-29\n to flashback the database, 18-25\n\nRESTRICTED SESSION system privilege, 18-40, 18-44\n\nresult cache, 16-61\n\nRESULT_CACHE hint, 3-102\n\nresumable space allocation, 11-48\n\nRESUMABLE system privilege, 18-47\n\nRESUME clause\n of ALTER SYSTEM, 11-66\n\nRETENTION parameter\n of LOB storage, 16-44\n\nRETRY_ON_ROW_CHANGE hint, 3-103\n\nRETURN clause\n of CREATE OPERATOR, 15-35\n\nRETURNING clause\n of DELETE, 17-31\n of INSERT, 18-56\n of UPDATE, 19-73, 19-74, 19-78\n\nREUSE clause\n of CREATE CONTROLFILE, 14-14\n of file specifications, 8-35\n\nREVERSE clause\n of CREATE INDEX, 14-73\n\nreverse indexes, 14-73\n\nREVERSE parameter\n\nof ALTER INDEX ... REBUILD, 10-87, 10-89\n\nREVOKE clause\n of ALTER USER, 13-9\n\nREVOKE CONNECT THROUGH clause\n of ALTER USER, 13-6, 13-9\n\nREVOKE statement, 18-88\n locks, B-5\n\nREWRITE hint, 3-103\n\nright outer joins, 19-24\n\nroles, 18-36\n authorization\n by a password, 15-59\n by an external service, 15-59\n by the database, 15-59\n by the enterprise directory service, 15-59\n changing, 11-38\n creating, 15-58\n disabling\n for the current session, 19-61, 19-62\n enabling\n for the current session, 19-61, 19-62\n granting, 18-33, 18-36\n system privileges for, 18-44\n to a user, 18-36\n to another role, 18-36\n to PUBLIC, 18-36\n identifying by password, 15-59\n identifying externally, 15-59\n identifying through enterprise directory service, 15-59\n identifying using a package, 15-59\n removing from the database, 17-66\n revoking, 18-88\n from another role, 17-66, 18-91\n from PUBLIC, 18-91\n from users, 17-66, 18-90\n\nrollback segments\n removing from the database, 17-67\n specifying optimal size of, 8-54\n\nrollback segments granting\n system privileges for, 18-44\n\nROLLBACK statement, 18-97\n\nrollback undo, 11-40, 14-28\n\nROLLUP clause\n of SELECT statements, 19-27\n\nROUND (date) function, 5-172\n format models, 5-269\n\nROUND (number) function, 5-172\n\nroutines\n calling, 13-40\n executing, 13-40\n\nrow constructor, 6-16\n\nROW EXCLUSIVE lock mode, 18-74\n\nrow locking, B-1\n\nROW SHARE lock mode, 18-73\n\nrow value constructor, 6-16\n\nrow values\n pivoting into columns, 19-21\n\nROW_NUMBER function, 5-173\n\nROWDEPENDENCIES clause\n\nof CREATE CLUSTER, 14-7\n of CREATE TABLE, 16-63\n\nROWID data type, 3-27\n\nROWID pseudocolumn, 2-9, 3-27, 3-28\n\nrowids, 3-27\n description of, 3-27\n extended\n base 64, 3-28\n not directly available, 3-28\n nonphysical, 3-28\n of foreign tables, 3-28\n of index-organized tables, 3-28\n uses for, 2-9\n\nROWIDTOCHAR function, 5-175\n\nROWIDTONCHAR function, 5-175\n\nrow-level dependency tracking, 14-7, 16-63\n\nrow-level locking, B-1\n\nROWNUM pseudocolumn, 2-10\n\nrows\n adding to a table, 18-54\n allowing movement of between partitions, 16-16\n inserting\n into partitions, 18-59\n into remote databases, 18-60\n into subpartitions, 18-59\n locking, B-1\n locks on, B-1\n movement between partitions, 16-64\n removing\n from a cluster, 19-66, 19-68\n from a table, 19-66, 19-68\n from partitions and subpartitions, 17-29\n from tables and views, 17-26\n selecting in hierarchical order, 9-3\n specifying constraints on, 8-11\n storing if in violation of constraints, 12-72\n\nRPAD function, 5-176\n\nRR datetime format element, 3-64\n\nRTRIM function, 5-177\n\nrun-time compilation\n avoiding, 11-31, 13-12\n\nS\n\nSAMPLE clause\n of SELECT, 19-19\n of SELECT and subqueries, 19-8\n\nSAVEPOINT statement, 19-2\n\nsavepoints\n erasing, 13-47\n rolling back to, 18-97\n specifying, 19-2\n\nscalar subqueries, 6-14\n\nscale\n greater than precision, 3-11\n of NUMBER data type, 3-10\n\nSCHEMA clause\n of CREATE JAVA, 14-93\n\nschema objects, 3-107\n defining default buffer pool for, 8-55\n\ndropping, 18-16\nin other schemas, 3-114\nlist of, 3-107\nname resolution, 3-113\nnamespaces, 3-110\nnaming\nexamples, 3-112\nguidelines, 3-112\nrules, 3-108\nobject types, 3-30\non remote databases, 3-114\npartitioned indexes, 3-116\npartitioned tables, 3-116\nparts of, 3-108\nprotecting location, 16-2\nprotecting owner, 16-2\nproviding alternate names for, 16-2\nreauthorizing, 10-2\nrecompiling, 10-2\nreferring to, 3-112, 11-51\nremote, accessing, 14-32\nvalidating structure, 13-19\n\nschemas\nchanging for a session, 11-51\ncreating, 15-64\ndefinition of, 3-107\nscientific notation, 3-57\n\nSCN_TO_TIMESTAMP function, 5-177\n\nSCOPE FOR clause\nof ALTER MATERIALIZED VIEW, 11-9\nof CREATE MATERIALIZED VIEW, 15-12\n\nSCORE operator, 4-1\n\nSDO_GEOMETRY data type, 3-34\nSDO_GEORaster data type, 3-34\nSDO_TOPO_GEOMETRY data type, 3-34\n\nsecurity\nenforcing, 16-95\n\nsecurity clauses\nof ALTER SYSTEM, 11-68\n\nsegment attributes clause\nof CREATE TABLE, 16-16\n\nSEGMENT MANAGEMENT clause\nof CREATE TABLESPACE, 16-89\n\nsegments\nspace management\nautomatic, 16-89\nmanual, 16-89\nusing bitmaps, 16-89\nusing free lists, 16-89\ntable\ncompacting, 10-84, 11-11, 11-22, 12-35\n\nSELECT ANY CUBE DIMENSION system privilege, 18-43\nSELECT ANY CUBE system privilege, 18-42\nSELECT ANY DICTIONARY system privilege, 18-47\nSELECT ANY MINING MODEL system privilege, 18-42\nSELECT ANY SEQUENCE system privilege, 18-44\nSELECT ANY TABLE system privilege, 18-45\n\nselect lists, 9-2\nordering, 9-10\n\nSELECT object privilege\ngranting on a view, 18-37\non a materialized view, 18-49\non a mining model, 18-49\non a sequence, 18-50\non a table, 18-51\non a view, 18-51\non an OLAP cube, 18-49\non an OLAP cube dimension, 18-49\n\nSELECT statement, 9-1, 19-4\n\nself joins, 9-11\nsemijoins, 9-14\n\nsequences, 2-3, 15-66\naccessing values of, 15-66\nchanging\nthe increment value, 11-43\ncreating, 15-66\ncreating without limit, 15-67\ngranting system privileges for, 18-44\nguarantee consecutive values, 15-69\nhow to use, 2-4\nincrement value, setting, 15-67\nincrementing, 15-66\ninitial value, setting, 15-68\nmaximum value\neliminating, 11-43\nsetting, 15-68\nsetting or changing, 11-43\nminimum value\neliminating, 11-43\nsetting, 15-68\nsetting or changing, 11-43\nnumber of cached values, changing, 11-43\nordering values, 11-43\npreallocating values, 15-68\nrecycling values, 11-43\nremoving from the database, 18-2\nrenaming, 18-86\nrestarting, 18-2\nat a different number, 11-43\nat a predefined limit, 15-67\nvalues, 15-68\nreusing, 15-66\nstopping at a predefined limit, 15-67\nsynonyms for, 16-2\nwhere to use, 2-3\n\nserver parameter files\ncreating, 15-70\nfrom memory, 15-72\n\nserver wallet\nkeys, 11-68\n\nservice name\nof remote database, 14-35\n\nsession control statements, 10-3\nPL/SQL support of, 10-3\n\nsession locks\nreleasing, 11-64\n\nsession parameters\n\nchanging settings, 11-51\nINSTANCE, 11-52\nSESSION_ROLES view, 19-61\n\nsessions\ncalculating resource cost limits, 11-35\nchanging resource cost limits, 11-35\ndisconnecting, 11-63\ngranting system privileges for, 18-44\nlimiting CPU time, 11-35\nlimiting data block reads, 11-35\nlimiting inactive periods, 11-32\nlimiting private SGA space, 11-36\nlimiting resource costs, 11-35\nlimiting total elapsed time, 11-35\nlimiting total resources, 11-32\nmodifying characteristics of, 11-49\nrestricting, 11-67\nrestricting to privileged users, 11-68\nswitching to a different instance, 11-52\nterminating, 11-64\nterminating across instances, 11-64\ntime zone setting, 11-53\n\nSESSIONS_PER_USER parameter\nof ALTER PROFILE, 11-32\n\nSESSIONTIMEZONE function, 5-179\n\nSET clause\nof ALTER SESSION, 11-49\nof ALTER SYSTEM, 11-70\n\nSET conditions, 7-12\n\nSET CONSTRAINT(S) statement, 19-59\n\nSET DANGLING TO NULL clause\nof ANALYZE, 13-19\n\nSET DATABASE clause\nof CREATE CONTROLFILE, 14-14\n\nSET ENCRYPTION KEY clause\nof ALTER SYSTEM, 11-69\n\nSET ENCRYPTION WALLET clause\nof ALTER SYSTEM, 11-68\n\nSET function, 5-179\n\nset operators, 4-5, 19-33\nINTERSECT, 4-5\nMINUS, 4-5\nUNION, 4-5\nUNION ALL, 4-5\n\nSET ROLE statement, 19-61\n\nSET STANDBY DATABASE clause\nof ALTER DATABASE, 10-35\n\nSET STATEMENT_ID clause\nof EXPLAIN PLAN, 18-21\n\nSET TIME_ZONE clause\nof ALTER DATABASE, 10-18, 10-41\nof ALTER SESSION, 11-53\nof CREATE DATABASE, 14-22\n\nSET TRANSACTION statement, 19-63\n\nSET UNUSED clause\nof ALTER TABLE, 12-48\n\nSGA. See system global area (SGA)\n\nSHARE ROW EXCLUSIVE lock mode, 18-74\n\nSHARE UPDATE lock mode, 18-74\n\nSHARED clause\nof CREATE DATABASE LINK, 14-33\n\nshared pool\nflushing, 11-64\n\nshared server\nprocesses\ncreating additional, 11-73\nterminating, 11-73\nsystem parameters, 11-73\n\nshort-circuit evaluation\nDECODE function, 5-58\n\nSHRINK SPACE clause\nof ALTER INDEX, 10-84\nof ALTER MATERIALIZED VIEW, 11-11\nof ALTER MATERIALIZED VIEW LOG, 11-22\nof ALTER TABLE, 12-35\n\nSHUTDOWN clause\nof ALTER SYSTEM, 11-70\n\nSI_AverageColor data type, 3-36\n\nSI_Color data type, 3-36\n\nSI_ColorHistogram data type, 3-36\n\nSI_FeatureList data type, 3-36\n\nSI_PositionalColorHistogram data type, 3-36\n\nSI_StillImage data type, 3-36\n\nSI_Texture data type, 3-36\n\nsiblings\nordering in a hierarchical query, 19-33\n\nSIGN function, 5-180\n\nsimple comparison conditions, 7-5\n\nsimple expressions, 6-3\n\nSIN function, 5-180\n\nSINGLE TABLE clause\nof CREATE CLUSTER, 14-6\n\nsingle-row functions, 5-3\n\nsingle-table insert, 18-58\n\nSINH function, 5-181\n\nSIZE clause\nof ALTER CLUSTER, 10-6\nof CREATE CLUSTER, 14-5\nof file specifications, 8-34\n\nSOME operator, 7-5\n\nSOUNDEX function, 5-181\n\nSP datetime format element suffix, 3-65\n\nspecial characters\nin passwords, 15-53\n\nspelled numbers\nspecifying, 3-65\n\nspfile\nOracle ASM, 15-71\n\nSPLIT PARTITION clause\nof ALTER INDEX, 10-94\nof ALTER TABLE, 12-67\n\nSPTH datetime format element suffix, 3-65\n\nSQL Developer, 1-3\n\nSQL functions, 5-2\nABS, 5-18\nACOS, 5-18\nADD_MONTHS, 5-19\naggregate functions, 5-10\nanalytic functions, 5-11\nAPPENDCHILDXML, 5-19\n\napplied to LOB columns, 5-2\nASCII, 5-20\nASCIIISTR, 5-21\nASIN, 5-21\nATAN, 5-22\nATAN2, 5-22\nAVG, 5-23\nBFILENAME, 5-24\nBIN_TO_NUM, 5-25\nBITAND, 5-26\nCARDINALITY, 5-28\nCAST, 5-28\nCEIL, 5-31\ncharacter functions\n returning character values, 5-4\n returning number values, 5-5\nCHARTOROWID, 5-31\nCHR, 5-32\nCLUSTER_ID, 5-33\nCLUSTER_PROBABILITY, 5-35\nCLUSTER_SET, 5-36\nCOALESCE, 5-38\nCOLLECT, 5-39\ncollection functions, 5-7\nCOMPOSE, 5-40\nCONCAT, 5-40\nconversion functions, 5-6\nCONVERT, 5-41\nCORR, 5-43\nCORR_K, 5-46\nCORR_S, 5-45\nCOS, 5-46\nCOSH, 5-47\nCOUNT, 5-47\nCOVAR_POP, 5-49\nCOVAR_SAMP, 5-50\nCUBE_TABLE, 5-51\nCUME_DIST, 5-52\nCURRRENT_DATE, 5-54\nCURRRENT_TIMESTAMP, 5-54\nCV, 5-55\ndata cartridge functions, 5-17\ndata mining functions, 5-7\nDATAOBJ_TO_PARTITION, 5-57\ndatetime functions, 5-5\nDBTIMEZONE, 5-57\nDECODE, 5-57\nDECOMPOSE, 5-59\nDELETEXML, 5-60\nDENSE_RANK, 5-61\nDEPTH, 5-62\nDEREF, 5-63\nDUMP, 5-64\nEMPTY_BLOB, 5-65\nEMPTY_CLOB, 5-65\nencoding and decoding functions, 5-9\nenvironment and identifier functions, 5-9\nEXISTSNODE, 5-66\nEXP, 5-67\nEXTRACT (datetime), 5-67\nEXTRACT (XML), 5-70\nEXTRACTVALUE, 5-71\nFEATURE_ID, 5-72\nFEATURE_SET, 5-73\nFEATURE_VALUE, 5-75\nFIRST, 5-76\nFIRST_VALUE, 5-78\nFLOOR, 5-80\nFROM_TZ, 5-80\ngeneral comparison functions, 5-6\nGREATEST, 5-81\nGROUP_ID, 5-81\nGROUPING, 5-82\nGROUPING_ID, 5-83\nHEXTORAW, 5-84\nhierarchical functions, 5-7\nINITCAP, 5-85\nINSERTCHILDXML, 5-85\nINSERTCHILDXMLAFTER, 5-86\nINSERTCHILDXMLBEFORE, 5-87\nINSERTXMLAFTER, 5-88\nINSERTXMLBEFORE, 5-89\nINSTR, 5-90\nINSTR2, 5-90\nINSTR4, 5-90\nINSTRB, 5-90\nINSTRC, 5-90\nITERATION_NUMBER, 5-91\nLAG, 5-93\nlarge object functions, 5-7\nLAST, 5-94\nLAST_DAY, 5-94\nLAST_VALUE, 5-95\nLEAD, 5-98\nLEAST, 5-99\nLENGTH, 5-99\nLENGTH2, 5-99\nLENGTH4, 5-99\nLENGTHB, 5-99\nLENGTHC, 5-99\nlinear regression, 5-166\nLISTAGG, 5-100\nLN, 5-102\nLNNVL, 5-102\nLOCALTIMESTAMP, 5-103\nLOG, 5-104\nLOWER, 5-105\nLPAD, 5-105\nLTRIM, 5-106\nMAKE_REF, 5-107\nMAX, 5-107\nMEDIAN, 5-109\nMIN, 5-111\nMOD, 5-112\nmodel functions, 5-17\nMONTHS_BETWEEN, 5-113\nNANVL, 5-113\nNCHR, 5-114\nNEW_TIME, 5-115\nNEXT_DAY, 5-116\n\n| Function | Page |\n|--------------------------------|------|\n| NLS character functions | 5-5 |\n| NLS_CHARSET_DECL_LEN | 5-116|\n| NLS_CHARSET_ID | 5-117|\n| NLS_CHARSET_NAME | 5-117|\n| NLS_INITCAP | 5-118|\n| NLS_LOWER | 5-119|\n| NLS_UPPER | 5-119|\n| NLSSORT | 5-120|\n| NTH_VALUE | 5-122|\n| NTILE | 5-123|\n| NULLIF | 5-124|\n| NULL-related functions | 5-9 |\n| numeric functions | 5-3 |\n| NUMTODSINTERVAL | 5-125|\n| NUMTOYMINTERVAL | 5-125|\n| NVL | 5-126|\n| NVL2 | 5-127|\n| object reference functions | 5-17 |\n| OLAP functions | 5-17 |\n| ORA_DST_AFFECTED | 5-128|\n| ORA_DST_CONVERT | 5-129|\n| ORA_DST_ERROR | 5-129|\n| ORA_HASH | 5-130|\n| PATH | 5-131|\n| PERCENT_RANK | 5-131|\n| PERCENTILE_CONT | 5-133|\n| PERCENTILE_DISC | 5-135|\n| POWER | 5-136|\n| POWERMULTISET | 5-137|\n| POWERMULTISET_BY_CARDINALITY | 5-138|\n| PREDICTION | 5-139|\n| PREDICTION_BOUNDS | 5-141|\n| PREDICTION_COST | 5-142|\n| PREDICTION_DETAILS | 5-144|\n| PREDICTION_PROBABILITY | 5-145|\n| PREDICTION_SET | 5-147|\n| PRESENTNNV | 5-149|\n| PRESENTV | 5-150|\n| PREVIOUS | 5-152|\n| RANK | 5-152|\n| RATIO_TO_REPORT | 5-154|\n| RAWTOHEX | 5-155|\n| RAWTONHEX | 5-156|\n| REF | 5-156|\n| REFTOHEX | 5-157|\n| REGEXP_COUNT | 5-158|\n| REGEXP_INSTR | 5-159|\n| REGEXP_REPLACE | 5-162|\n| REGEXP_SUBSTR | 5-164|\n| REGR_AVGX | 5-166|\n| REGR_AVGY | 5-166|\n| REGR_COUNT | 5-166|\n| REGR_INTERCEPT | 5-166|\n| REGR_R2 | 5-166|\n| REGR_SLOPE | 5-166|\n| REGR_SXX | 5-166|\n| REGR_SXY | 5-166|\n| REGR_SYY | 5-166|\n| REMAINDER | 5-170|\n| REPLACE | 5-171|\n| ROUND (date) | 5-172|\n| ROUND (number) | 5-172|\n| ROW_NUMBER | 5-173|\n| ROWIDTOCHAR | 5-175|\n| ROWIDTONCHAR | 5-175|\n| RPAD | 5-176|\n| RTRIM | 5-177|\n| SCN_TO_TIMESTAMP | 5-177|\n| SESSIONTIMEZONE | 5-179|\n| SET | 5-179|\n| SIGN | 5-180|\n| SIN | 5-180|\n| single-row functions | 5-3 |\n| SINH | 5-181|\n| SOUNDEX | 5-181|\n| SQRT | 5-182|\n| STATS_BINOMIAL_TEST | 5-183|\n| STATS_CROSSTAB | 5-184|\n| STATS_F_TEST | 5-185|\n| STATS_KS_TEST | 5-186|\n| STATS_MODE | 5-187|\n| STATS_MW_TEST | 5-188|\n| STATS_ONE_WAY_ANOVA | 5-189|\n| STATS_T_TEST_INDEP | 5-190, 5-192|\n| STATS_T_TEST_INDEPU | 5-190, 5-192|\n| STATS_T_TEST_ONE | 5-190, 5-191|\n| STATS_T_TEST_PAIRED | 5-190, 5-192|\n| STATS_WSR_TEST | 5-193|\n| STDDEV | 5-194|\n| STDDEV_POP | 5-195|\n| STDDEV_SAMP | 5-196|\n| SUBSTR | 5-198|\n| SUBSTR2 | 5-198|\n| SUBSTR4 | 5-198|\n| SUBSTRB | 5-198|\n| SUBSTRC | 5-198|\n| SUM | 5-199|\n| SYS_CONNECT_BY_PATH | 5-200|\n| SYS_CONTEXT | 5-201|\n| SYS_DBURIGEN | 5-207|\n| SYS_EXTRACT_UTC | 5-208|\n| SYS_GUID | 5-208|\n| SYS_TYPEID | 5-209|\n| SYS_XMLAGG | 5-210|\n| SYS_XMLGEN | 5-210|\n| SYSDATE | 5-211|\n| SYSTIMESTAMP | 5-212|\n| TAN | 5-212|\n| TANH | 5-213|\n| TIMESTAMP_TO_SCN | 5-213|\n| TO_BINARY_DOUBLE | 5-214|\n| TO_BINARY_FLOAT | 5-215|\n| TO_BLOB | 5-216|\n| TO_CHAR (character) | 5-217|\n| TO_CHAR (datetime) | 5-218|\n| TO_CHAR (number) | 5-220|\n| TO_CLOB | 5-221|\n| TO_DATE | 5-222|\n| TO_DSINTERVAL | 5-223|\n| TO_LOB | 5-224|\n\nTO_MULTI_BYTE, 5-225\nTO_NCHAR (character), 5-226\nTO_NCHAR (datetime), 5-226\nTO_NCHAR (number), 5-227\nTO_NCLOB, 5-228\nTO_NUMBER, 5-228\nTO_SINGLE_BYTE, 5-229\nTO_TIMESTAMP, 5-229\nTO_TIMESTAMP_TZ, 5-230\nTO_YMINTERVAL, 5-231\nTRANSLATE, 5-232\nTRANSLATE ... USING, 5-233\nTREAT, 5-234\nTRIM, 5-235\nTRUNC (date), 5-236\nTRUNC (number), 5-237\nt-test, 5-190\nTZ_OFFSET, 5-237\nUID, 5-238\nUNISTR, 5-238\nUPDATEXML, 5-239\nUPPER, 5-240\nUSER, 5-241\nUSERENV, 5-241\nVALUE, 5-242\nVAR_POP, 5-243\nVAR_SAMP, 5-244\nVARIANCE, 5-245\nVSIZE, 5-246\nWIDTH_BUCKET, 5-247\nXML functions, 5-8\nXMLAGG, 5-248\nXMLCAST, 5-249\nXMLCDATA, 5-250\nXMLCOLATTVAL, 5-251\nXMLCOMMENT, 5-251\nXMLCONCAT, 5-252\nXMLEDIFF, 5-253\nXMLEMENT, 5-254\nXML_EXISTS, 5-256\nXMLFOREST, 5-257\nXMLISVALID, 5-258\nXMLPARSE, 5-258\nXMLPATCH, 5-259\nXMLPI, 5-260\nXMLQUERY, 5-261\nXMLROOT, 5-262\nXMLSEQUENCE, 5-263\nXMLSERIALIZE, 5-265\nXMLTABLE, 5-266\nXMLTRANSFORM, 5-268\n\nSQL. See Structured Query Language (SQL)\n\nSQL statements\nALTER FLASHBACK ARCHIVE, 10-74\nauditing\nby access, 13-32\nby proxy, 13-31\nby session, 13-32\nby user, 13-31\nstopping, 18-80\nsuccessful, 13-33\nCREATE FLASHBACK ARCHIVE, 14-56\nDDL, 10-2\ndetermining the execution plan for, 18-20\nDML, 10-2\nDROP FLASHBACK ARCHIVE, 17-46\norganization of, 10-4\nrolling back, 18-97\nsession control, 10-3\nspace allocation, resumable, 11-48\nstorage in the result cache, 16-61\nsuspending and completing, 11-48\nsystem control, 10-3\ntracking the occurrence in a session, 13-27\ntransaction control, 10-3\ntype of, 10-1\nundoing, 18-97\nSQL*Loader inserts, logging, 10-85\nSQL:99 standards, 1-1\nSQL/DS data types, 3-28\nrestrictions on, 3-29\nSQRT function, 5-182\nstandalone procedures\ndropping, 17-63\nstandard SQL, C-1\nOracle extensions to, C-27\nstandby database\nsynchronizing with primary database, 11-48\nstandby databases\nactivating, 10-35\nand Data Guard, 10-38\ncommitting to primary status, 10-36\ncontrolling use, 10-42\nconverting to physical standby, 10-38\ndesigning media recovery, 10-20\nmounting, 10-19\nrecovering, 10-21\nSTAR_TRANSFORMATION hint, 3-104\nSTAR_TRANSFORMATION_ENABLED initialization parameter, 3-104\nSTART LOGICAL STANDBY APPLY clause\nof ALTER DATABASE, 10-37\nSTART WITH clause\nof ALTER MATERIALIZED VIEW ...\nREFRESH, 11-13\nof queries and subqueries, 19-26\nof SELECT and subqueries, 19-10\nSTART WITH parameter\nof CREATE SEQUENCE, 15-68\nstartup_clauses\nof ALTER DATABASE, 10-10\nSTATEMENT_QUEUING hint, 3-104\nstatistics\ncollection during index rebuild, 10-86\ndeleting from the data dictionary, 13-21\nforcing disassociation, 17-35\non index usage, 10-91\non scalar object attributes\ncollecting, 13-15\non schema objects\n\ncollecting, 13-15\ndeleting, 13-15\nuser-defined\ndropping, 17-50, 17-51, 17-61, 18-6, 18-13\n\nstatistics types\nassociating\nwith columns, 13-23\nwith domain indexes, 13-23\nwith functions, 13-23\nwith indextypes, 13-23\nwith object types, 13-23\nwith packages, 13-23\ndisassociating\nfrom columns, 17-34\nfrom domain indexes, 17-34\nfrom functions, 17-34\nfrom indextypes, 17-34\nfrom object types, 17-34\nfrom packages, 17-34\n\nSTATS_BINOMIAL_TEST function, 5-183\nSTATS_CROSSTAB function, 5-184\nSTATS_F_TEST function, 5-185\nSTATS_KS_TEST function, 5-186\nSTATS_MODE function, 5-187\nSTATS_MW_TEST function, 5-188\nSTATS_ONE_WAY_ANOVA function, 5-189\nSTATS_T_TEST_INDEP function, 5-190, 5-192\nSTATS_T_TEST_INDEPU function, 5-190, 5-192\nSTATS_T_TEST_ONE function, 5-190, 5-191\nSTATS_T_TEST_PAIRED function, 5-190, 5-192\nSTATS_WSR_TEST function, 5-193\nSTDDEV function, 5-194\nSTDDEV_POP function, 5-195\nSTDDEV_SAMP function, 5-196\nSTOP LOGICAL STANDBY clause\nof ALTER DATABASE, 10-38\n\nSTORAGE clause\nof ALTER CLUSTER, 10-6\nof ALTER INDEX, 10-85\nof ALTER MATERIALIZED VIEW LOG, 11-19\nof CREATE MATERIALIZED VIEW LOG, 15-28\nof CREATE MATERIALIZED VIEW LOG. See CREATE TABLE\nof CREATE TABLE, 8-46, 16-10\n\nstorage parameters\ndefault, changing, 12-93\nresetting, 19-66, 19-68\n\nSTORE IN clause\nof ALTER TABLE, 12-39, 16-55\n\nstored functions, 14-59\n\nstring literals. See text literals.\n\nstrings\nconverting to ASCII values, 5-21\nconverting to unicode, 5-40\n\nstrings. See text literals.\n\nStructured Query Language (SQL)\ndescription, 1-1\nfunctions, 5-2\nkeywords, A-2\nOracle Tools support of, 1-3\n\nparameters, A-2\nstandards, 1-1, C-1\n\nstatements\ndetermining the cost of, 18-20\nsyntax, 10-4, A-1\n\nstructures\nlocking, B-4\n\nsubexpressions\nof regular expressions, 5-160, 5-165\n\nSUBMULTISET condition, 7-13\n\nSUBPARTITION BY HASH clause\nof CREATE TABLE, 16-22, 16-59\n\nSUBPARTITION BY LIST clause\nof CREATE TABLE, 16-59\n\nSUBPARTITION clause\nof ANALYZE, 13-17\nof DELETE, 17-29\nof INSERT, 18-59\nof LOCK TABLE, 18-73\nof UPDATE, 19-75\n\nsubpartition template\ncreating, 12-57\nreplacing, 12-57\n\nsubpartition-extended table names\nin DML statements, 3-117\nrestrictions on, 3-118\nsyntax, 3-117\n\nsubpartitions\nadding, 12-59\nadding rows to, 18-54\nallocating extents for, 12-35\ncoalescing, 12-59\nconverting into nonpartitioned tables, 12-71\ncreating, 16-22\ncreating a template for, 12-57, 16-58\ndeallocating unused space from, 12-35\nexchanging with tables, 12-26\nhash, 16-59\ninserting rows into, 18-59\nlist, 16-59\nlist, adding, 12-59\nlocking, 18-72\nlogging insert operations, 12-34\nmoving to a different segment, 12-62\n\nphysical attributes\nchanging, 12-33\nremoving rows from, 12-66, 17-29\nrenaming, 12-66\nrevising values in, 19-75\nspecifying, 16-56\ntemplate, creating, 16-58\ntemplate, dropping, 12-57\ntemplate, replacing, 12-57\n\nsubqueries, 9-1, 9-14, 19-4, 19-5\ncontaining subqueries, 9-14\ncorrelated, 9-14\ndefined, 9-1\nextended subquery unnesting, 9-15\ninline views, 9-14\nnested, 9-14\n\nof past data, 19-17\nscalar, 6-14\nto insert table data, 16-65\nunnesting, 9-15\nusing in place of expressions, 6-14\n\nSUBSTR function, 5-198\nSUBSTR2 function, 5-198\nSUBSTR4 function, 5-198\nSUBSTRB function, 5-198\nSUBSTRC function, 5-198\n\nsubtotal values\nderiving, 19-27\n\nsubtypes\ndropping safely, 18-14\n\nSUM function, 5-199\n\nsupplemental logging\nidentification key (full), 10-32\nminimal, 10-32\n\nSUSPEND clause\nof ALTER SYSTEM, 11-66\n\nsustained standby recovery mode, 10-23\n\nSWITCH LOGFILE clause\nof ALTER SYSTEM, 11-66\n\nSYNC WITH PRIMARY\nclause of ALTER SESSION, 11-48\n\nsynonyms\nchanging the definition of, 18-3\ncreating, 16-2\ngranting system privileges for, 18-44\nlocal, 16-4\nprivate, dropping, 18-3\npublic, 16-3\ndropping, 18-3\nremote, 16-4\nremoving from the database, 18-3\nrenaming, 18-86\nsynonyms for, 16-2\n\nsyntax diagrams, A-1\nloops, A-3\nmultipart diagrams, A-4\n\nSYS user\nassigning password for, 14-22\n\nSYS_CONNECT_BY_PATH function, 5-200\n\nSYS_CONTEXT function, 5-201\n\nSYS_DBURIGEN function, 5-207\n\nSYS_EXTRACT_UTC function, 5-208\n\nSYS_GUID function, 5-208\n\nSYS_NC_ROWINFO$ column, 16-68, 17-21\n\nSYS_TYPEID function, 5-209\n\nSYS_XMLAGG function, 5-210\n\nSYS_XMILGEN function, 5-210\n\nSYSAUX clause\nof CREATE DATABASE, 14-26\n\nSYSAUX tablespace\ncreating, 14-26, 16-84\n\nSYSDATE function, 5-211\n\nSYSDBA system privilege, 18-48\n\nSYSOPER system privilege, 18-48\n\nsystem change numbers\nobtaining, 2-8\n\nsystem control statements, 10-3\nPL/SQL support of, 10-3\n\nsystem global area\nflushing, 11-64, 11-65\nupdating, 11-63\n\nsystem parameters\nGLOBAL_TOPIC_ENABLED, 11-72\n\nsystem partitioning, 16-60\n\nsystem privileges\nADMINISTER ANY SQL TUNING SET, 18-39\nADMINISTER DATABASE TRIGGER, 18-45\nADMINISTER SQL MANAGEMENT OBJECT, 18-40, 18-43\nADMINISTER SQL TUNING SET, 18-39\nADVISOR, 18-39\nALTER ANY CLUSTER, 18-40\nALTER ANY CUBE, 18-42\nALTER ANY CUBE DIMENSION, 18-43\nALTER ANY DIMENSION, 18-40\nALTER ANY INDEX, 18-41\nALTER ANY INDEXTYPE, 18-41\nALTER ANY LIBRARY, 18-41\nALTER ANY MATERIALIZED VIEW, 18-42\nALTER ANY MINING MODEL, 18-42\nALTER ANY OPERATOR, 18-43\nALTER ANY OUTLINE, 18-43\nALTER ANY PROCEDURE, 18-44\nALTER ANY ROLE, 18-44\nALTER ANY SEQUENCE, 18-44\nALTER ANY SQL PROFILE, 18-40\nALTER ANY TABLE, 18-45\nALTER ANY TRIGGER, 18-45\nALTER ANY TYPE, 18-46\nALTER DATABASE, 18-40\nALTER DATABASE LINK, 18-40\nALTER PROFILE, 18-44\nALTER PUBLIC DATABASE LINK, 18-40\nALTER RESOURCE COST, 18-44\nALTER ROLLBACK SEGMENT, 18-44\nALTER SESSION, 18-44\nALTER SYSTEM, 18-40\nALTER TABLESPACE, 18-45\nALTER USER, 18-46\nANALYZE ANY, 18-46\nAUDIT ANY, 18-46\nAUDIT SYSTEM, 18-40\nBACKUP ANY TABLE, 18-45\nBECOME USER, 18-47\nCHANGE NOTIFICATION, 18-47\nCOMMENT ANY MINING MODEL, 18-42\nCOMMENT ANY TABLE, 18-47\nCREATE ANY CLUSTER, 18-40\nCREATE ANY CONTEXT, 18-40\nCREATE ANY CUBE, 18-42\nCREATE ANY CUBE BUILD PROCESS, 18-43\nCREATE ANY CUBE DIMENSION, 18-43\nCREATE ANY DIMENSION, 18-40\nCREATE ANY DIRECTORY, 18-41\nCREATE ANY INDEX, 18-41\nCREATE ANY INDEXTYPE, 18-41\n\n| Command | Page |\n|----------------------------------------------|------|\n| CREATE ANY JOB | 18-41|\n| CREATE ANY LIBRARY | 18-41|\n| CREATE ANY MATERIALIZED VIEW | 18-42|\n| CREATE ANY MEASURE FOLDER | 18-43|\n| CREATE ANY MINING MODEL | 18-42|\n| CREATE ANY OPERATOR | 18-43|\n| CREATE ANY OUTLINE | 18-43|\n| CREATE ANY PROCEDURE | 18-44|\n| CREATE ANY SEQUENCE | 18-44|\n| CREATE ANY SQL PROFILE | 18-39|\n| CREATE ANY SYNONYM | 18-44|\n| CREATE ANY TABLE | 18-45|\n| CREATE ANY TRIGGER | 18-45|\n| CREATE ANY TYPE | 18-45|\n| CREATE ANY VIEW | 18-46|\n| CREATE CLUSTER | 18-40|\n| CREATE CUBE | 18-42|\n| CREATE CUBE BUILD PROCESS | 18-43|\n| CREATE CUBE DIMENSION | 18-43|\n| CREATE DATABASE LINK | 18-40|\n| CREATE DIMENSION | 18-40|\n| CREATE EXTERNAL JOB | 18-41|\n| CREATE INDEXTYPE | 18-41|\n| CREATE JOB | 18-41|\n| CREATE LIBRARY | 18-41|\n| CREATE MATERIALIZED VIEW | 18-42|\n| CREATE MEASURE FOLDER | 18-43|\n| CREATE MINING MODEL | 18-42|\n| CREATE OPERATOR | 18-43|\n| CREATE PROCEDURE | 18-44|\n| CREATE PROFILE | 18-44|\n| CREATE PUBLIC DATABASE LINK | 18-40|\n| CREATE PUBLIC SYNONYM | 18-44|\n| CREATE ROLE | 18-44|\n| CREATE ROLLBACK SEGMENT | 18-44|\n| CREATE SEQUENCE | 18-44|\n| CREATE SESSION | 18-44|\n| CREATE SYNONYM | 18-44|\n| CREATE TABLE | 18-45|\n| CREATE TABLESPACE | 18-45|\n| CREATE TRIGGER | 18-45|\n| CREATE TYPE | 18-45|\n| CREATE USER | 18-46|\n| CREATE VIEW | 18-46|\n| DEBUG ANY PROCEDURE | 18-40|\n| DELETE ANY CUBE DIMENSION | 18-43|\n| DELETE ANY MEASURE FOLDER | 18-43|\n| DELETE ANY TABLE | 18-45|\n| DROP ANY CLUSTER | 18-40|\n| DROP ANY CONTEXT | 18-40|\n| DROP ANY CUBE | 18-42|\n| DROP ANY CUBE BUILD PROCESS | 18-43|\n| DROP ANY CUBE DIMENSION | 18-43|\n| DROP ANY DIMENSION | 18-41|\n| DROP ANY DIRECTORY | 18-41|\n| DROP ANY INDEX | 18-41|\n| DROP ANY INDEXTYPE | 18-41|\n| DROP ANY LIBRARY | 18-42|\n| DROP ANY MATERIALIZED VIEW | 18-42|\n| DROP ANY MEASURE FOLDER | 18-43|\n| DROP ANY MINING MODEL | 18-42|\n| DROP ANY OPERATOR | 18-43|\n| DROP ANY OUTLINE | 18-43|\n| DROP ANY PROCEDURE | 18-44|\n| DROP ANY ROLE | 18-44|\n| DROP ANY SEQUENCE | 18-44|\n| DROP ANY SQL PROFILE | 18-40|\n| DROP ANY SYNONYM | 18-45|\n| DROP ANY TABLE | 18-45|\n| DROP ANY TRIGGER | 18-45|\n| DROP ANY TYPE | 18-46|\n| DROP ANY VIEW | 18-46|\n| DROP PROFILE | 18-44|\n| DROP PUBLIC DATABASE LINK | 18-40|\n| DROP PUBLIC SYNONYM | 18-45|\n| DROP ROLLBACK SEGMENT | 18-44|\n| DROP TABLESPACE | 18-45|\n| DROP USER | 18-46|\n| EXECUTE ANY CLASS | 18-41|\n| EXECUTE ANY INDEXTYPE | 18-41|\n| EXECUTE ANY LIBRARY | 18-42|\n| EXECUTE ANY OPERATOR | 18-43|\n| EXECUTE ANY PROCEDURE | 18-44|\n| EXECUTE ANY PROGRAM | 18-41|\n| EXECUTE ANY TYPE | 18-46|\n| EXEMPT ACCESS POLICY | 18-47|\n| FLASHBACK ANY TABLE | 18-42, 18-45, 18-46|\n| FLASHBACK ARCHIVE ADMINISTER | 18-41|\n| for job scheduler tasks | 18-41|\n| for the Advisor framework | 18-39|\n| FORCE ANY TRANSACTION | 18-47|\n| FORCE TRANSACTION | 18-47|\n| GLOBAL QUERY REWRITE | 18-42|\n| GRANT ANY OBJECT PRIVILEGE | 18-47|\n| GRANT ANY PRIVILEGE | 18-47|\n| GRANT ANY ROLE | 18-44|\n| granting | 15-58, 18-33|\n| to a role | 18-35|\n| to a user | 18-35|\n| to PUBLIC | 18-35|\n| INSERT ANY CUBE DIMENSION | 18-43|\n| INSERT ANY MEASURE FOLDER | 18-43|\n| INSERT ANY TABLE | 18-45|\n| list of | 13-27, 18-39|\n| LOCK ANY TABLE | 18-45|\n| MANAGE SCHEDULER | 18-41|\n| MANAGE TABLESPACE | 18-45|\n| MERGE ANY VIEW | 18-46|\n| ON COMMIT REFRESH | 18-42|\n| QUERY REWRITE | 18-42|\n| RESTRICTED SESSION | 18-40, 18-44|\n| RESUMABLE | 18-47|\n| revoking | 18-88|\n| from a role | 18-90|\n| from a user | 18-90|\n| from PUBLIC | 18-90|\n| SELECT ANY CUBE | 18-42|\n| SELECT ANY CUBE DIMENSION | 18-43|\n| SELECT ANY DICTIONARY | 18-47|\n| SELECT ANY MINING MODEL | 18-42|\n\nSELECT ANY SEQUENCE, 18-44\nSELECT ANY TABLE, 18-45\nSYSDBA, 18-48\nSYSOPER, 18-48\nUNDER ANY TYPE, 18-46\nUNDER ANY VIEW, 18-46\nUNLIMITED TABLESPACE, 18-45\nUPDATE ANY CUBE, 18-42\nUPDATE ANY CUBE BUILD PROCESS, 18-43\nUPDATE ANY CUBE DIMENSION, 18-43\nUPDATE ANY TABLE, 18-45\n\nSYSTEM tablespace\n locally managed, 14-25\nSYSTEM user\n assigning password for, 14-22\nSYSTIMESTAMP function, 5-212\n\nT\n\nTABLE clause\n of ANALYZE, 13-17\n of INSERT, 18-60\n of SELECT, 19-20\n of TRUNCATE, 19-69\n of UPDATE, 19-74, 19-76\n\nTABLE collection expression, 19-20\n\ntable compression, 11-10, 12-34, 15-13, 16-34\n basic, 16-34\n during bulk load operations, 16-35\n for archiving data, 16-35\n hybrid columnar, 16-35\n OLTP, 16-34\n\ntable locks\n disabling, 12-78\n duration of, 18-72\n enabling, 12-78\nEXCLUSIVE, 18-73, 18-74\n modes of, 18-73\n on partitions, 18-73\n on remote database, 18-73\n on subpartitions, 18-73\n and queries, 18-72\nROW EXCLUSIVE, 18-73, 18-74\nROW SHARE, 18-73\nSHARE, 18-73\nSHARE ROW EXCLUSIVE, 18-74\nSHARE UPDATE, 18-74\n\ntable partitions\n compression of, 12-34, 16-34\n\ntable REF constraints, 8-12\n of CREATE TABLE, 16-30\n\ntables\n adding a constraint to, 12-54\n adding rows to, 18-54\n aliases, 3-118\n in CREATE INDEX, 14-70\n in DELETE, 17-31\n allocating extents for, 12-35\n assigning to a cluster, 16-41\n changing degree of parallelism on, 12-75\n changing existing values in, 19-72\n collecting statistics on, 13-17\n comments on, 13-45\n compression of, 12-34, 16-34\n creating, 16-6\n multiple, 15-64\n creating comments about, 13-44\n data stored outside database, 16-39\n deallocating unused space from, 12-35\n default physical attributes\n changing, 12-33\n degree of parallelism\n specifying, 16-6\n disassociating statistics types from, 18-6\n dropping\n along with cluster, 17-36\n along with owner, 18-16\n indexes of, 18-6\n partitions of, 18-6\n enabling tracking, 16-64\nexternal, 16-37\n creating, 16-39\n restrictions on, 16-40\nexternally organized, 16-37\n\nflashing back to an earlier version, 18-27\n\ngranting system privileges for, 18-45\n\nheap organized, 16-37\n\nindex-organized, 16-37\n overflow segment for, 16-38\n space in index block, 16-38\n\ninserting rows with a subquery, 16-65\ninserting using the direct-path method, 18-54\n\njoining in a query, 19-23\n\nLOB storage of, 8-46\n\nlocking, 18-72\n\nlogging\n insert operations, 12-34\n table creation, 16-34\n\nmigrated and chained rows in, 13-20\n\nmoving, 12-30\n\nmoving to a new segment, 12-76\n\nmoving, index-organized, 12-76\n\nnested\n storage characteristics, 16-48\n\nobject\n creating, 16-8\n querying, 16-67\n\nof XMLType, creating, 16-68\n\norganization, defining, 16-37\n\nparallel creation of, 16-62\n\nparallelism\n setting default degree, 16-62\n\npartition attributes of, 12-56\n\npartitioning, 3-116, 16-6, 16-51\n allowing rows to move between\n partitions, 12-38\n default attributes of, 12-56\n\nphysical attributes\n changing, 12-33\n\npurging from the recycle bin, 18-84\n\nread-only mode, 12-38\nread/write mode, 12-38\nreference-partitioned, 12-56, 12-73, 16-55\nrelational\n creating, 16-7\nremote, accessing, 14-32\nremoving from the database, 18-5\nremoving rows from, 17-26\nrenaming, 12-38, 18-86\nrestricting\n records in a block, 12-37\nretrieving data from, 19-4\nsaving blocks in a cache, 16-61\nSQL examples, 16-69\nstorage attributes\n defining, 16-6\nstorage characteristics\n defining, 8-46\nstorage properties of, 16-33, 16-41\nsubpartition attributes of, 12-56\nsynonyms for, 16-2\ntablespace for\n defining, 16-6, 16-33\ntemporary\n duration of data, 16-31\n session-specific, 16-25\n transaction specific, 16-25\nunclustering, 17-36\nupdating through views, 17-20\nvalidating structure, 13-19\nXMLType, querying, 16-68\nTABLESPACE clause\nof ALTER INDEX ... REBUILD, 10-88\nof CREATE CLUSTER, 14-5\nof CREATE INDEX, 14-72\nof CREATE MATERIALIZED VIEW, 15-13\nof CREATE MATERIALIZED VIEW LOG, 15-29\nof CREATE TABLE, 16-33\ntablespaces, 12-93\nallocating space for users, 17-11\nallowing write operations on, 12-99\nautomatic segment-space management, 16-89\nbacking up data files, 12-95\nbigfile, 16-84\n database default, 14-26\n default temporary, 14-27\n resizing, 12-93\n undo, 14-28\nbringing online, 12-98, 16-88\ncoalescing free extents, 12-94\nconverting\n from permanent to temporary, 12-99\n from temporary to permanent, 12-99\ncreating, 16-81\ndata files\n adding, 12-95\n renaming, 12-95\ndefault, 10-39\n specifying for a user, 13-8\ndefault permanent, 14-27\ndefault temporary, 10-39\n learning name of, 10-39\ndesigning media recovery, 10-20\ndropping contents, 18-10\nencrypting, 8-56, 16-87\nending online backup, 12-95\nextent size, 16-86\ngranting system privileges for, 18-45\nin FLASHBACK mode, 12-100, 16-90\nin FORCE LOGGING mode, 12-97, 16-87\nlocally managed, 8-51\n altering, 12-93\nlogging attribute, 12-97, 16-86\nmanaging extents of, 16-88\nread only, 12-99\nreconstructing lost or damaged, 10-20, 10-26\nrecovering, 10-20, 10-22\nremoving from the database, 18-9\nrenaming, 12-94\nsize of free extents in, 12-93\nsmallfile, 16-84\n database default, 14-26\n default temporary, 14-27\n undo, 14-28\nspecifying\n data files for, 16-85\n for a table, 16-33\n for a user, 17-10\n for index rebuild, 12-77\ntaking offline, 12-98, 16-88\ntemp files\n adding, 12-95\ntemporary\n creating, 16-90\n defining for the database, 14-21\n shrinking, 12-94\n specifying for a user, 13-8, 17-10\nundo\n altering, 12-93\n creating, 14-28, 16-91\n dropping, 18-10\nTAN function, 5-212\nTANH function, 5-213\ntemp files\n bringing online, 10-28\n defining for a tablespace, 16-82, 16-83, 16-84\n defining for the database, 14-22\n disabling autoextend, 10-28\n dropping, 10-28, 12-96\n enabling autoextend, 8-35, 10-28\n extending automatically, 8-35\n renaming, 10-26\n resizing, 10-28\n reusing, 8-35\n shrinking, 12-96\n size of, 8-34\n specifying, 8-29\n taking offline, 10-28\nTEMPFILE clause\n of ALTER DATABASE, 10-12, 10-28\n\nTEMPORARY clause\n of ALTER TABLESPACE, 12-99\n of CREATE TABLESPACE, 16-90\n\ntemporary tables\n creating, 16-6, 16-25\n session-specific, 16-25\n transaction-specific, 16-25\n\nTEMPORARY TABLESPACE clause\n of ALTER USER, 13-8\n of ALTER USER. See CREATE USER\n of CREATE USER, 17-10\n\ntemporary tablespace groups\n reassigning for a user, 13-8\n specifying for a user, 17-10\n\ntemporary tablespaces\n creating, 16-90\n default, 10-39\n specifying extent management during database creation, 14-21\n specifying for a user, 13-8, 17-10\n\nTEST clause\n of ALTER DATABASE ... RECOVER, 10-22\n\ntesting for a set, 7-12\n\ntext\n date and number formats, 3-55\n literals\n in SQL syntax, 3-45\n properties of CHAR and VARCHAR2 data types, 3-46\n syntax of, 3-46\n\ntext literals\n conversion to database character set, 3-46\n\nTH datetime format element suffix, 3-65\n\nthroughput\n optimizing, 3-77\n\nTHSP datetime format element suffix, 3-65\n\nTIME data type\n DB2, 3-29\n SQL/DS, 3-29\n\ntime format models\n short, 3-58, 3-62\n\ntime zone\n changing time zone data file, 5-128\n converting data to particular, 6-8\n determining for session, 5-179\n formatting, 3-62\n setting for the database, 14-30\n\nTIME_ZONE session parameter, 11-53\n\ntimestamp\n converting to local time zone, 6-8\n\nTIMESTAMP data type, 3-18\n DB2, 3-29\n SQL/DS, 3-29\n\nTIMESTAMP WITH LOCAL TIME ZONE data type, 3-19\n\nTIMESTAMP WITH TIME ZONE data type, 3-18\n\nTIMESTAMP_TO_SCN function, 5-213\n\nTO SAVEPOINT clause\n of ROLLBACK, 18-97\n\nTO_BINARY_DOUBLE function, 5-214\n\nTO_BINARY_FLOAT function, 5-215\n\nTO_BLOB function, 5-216\n\nTO_CHAR (character) function, 5-217\n\nTO_CHAR (datetime) function, 5-218\n format models, 3-59, 3-66\n\nTO_CHAR (number) function, 5-220\n format models, 3-56, 3-66\n\nTO_CLOB function, 5-221\n\nTO_DATE function, 5-222\n format models, 3-59, 3-64, 3-66\n\nTO_DSINTERVAL function, 5-223\n\nTO_LOB function, 5-224\n\nTO_MULTI_BYTE function, 5-225\n\nTO_NCHAR (character) function, 5-226\n\nTO_NCHAR (datetime) function, 5-226\n\nTO_NCHAR (number) function, 5-227\n\nTO_NCLOB function, 5-228\n\nTO_NUMBER function, 5-228\n format models, 3-56\n\nTO_SINGLE_BYTE function, 5-229\n\nTO_TIMESTAMP function, 5-229\n\nTO_TIMESTAMP_TZ function, 5-230\n\nTO_YMINTERVAL function, 5-231\n\ntop-level SQL statements, 13-30\n\ntop-N reporting, 2-10, 5-61, 5-153, 5-174\n\ntracking\n enabling for a table, 12-38, 16-64\n\ntransaction control statements, 10-3\n PL/SQL support of, 10-3\n\ntransactions\n allowing to complete, 11-63\n assigning\n rollback segment to, 19-63\n automatically committing, 13-47\n changes, making permanent, 13-47\n commenting on, 13-48\n distributed, forcing, 11-46\n ending, 13-47\n implicit commit of, 10-2, 10-3\n in-doubt\n committing, 13-47\n forcing, 13-49\n resolving, 19-64\n isolation level, 19-63\n locks, releasing, 13-47\n naming, 19-64\n read-only, 19-63\n read/write, 19-63\n rolling back, 11-64, 18-97\n to a savepoint, 18-97\n savepoints for, 19-2\n\nTRANSLATE ... USING function, 5-233\n\nTRANSLATE function, 5-232\n\ntransparent data encryption, 16-27\n master key, 11-69\n\nTREAT function, 5-234\n\ntriggers\n compiling, 13-2\n creating, 16-95\n database\n\naltering, 13-3\ndropping, 18-12, 18-16\ndisabling, 12-78, 13-2\nenabling, 12-78, 13-2, 13-3, 16-95\ngranting system privileges for, 18-45\nINSTEAD OF\ndropping, 17-16\nre-creating, 16-95\nremoving from the database, 18-12\nrenaming, 13-3\nTRIM function, 5-235\nTRUNC (date) function, 5-236\nformat models, 5-269\nTRUNC (number) function, 5-237\nTRUNCATE PARTITION clause\nof ALTER TABLE, 12-66\nTRUNCATE SUBPARTITION clause\nof ALTER TABLE, 12-66\nTRUNCATE_CLUSTER statement, 19-66\nTRUNCATE_TABLE statement, 19-68\ntype constructor expressions, 6-14\nTYPES clause\nof ASSOCIATE STATISTICS, 13-23, 13-24\nof DISASSOCIATE STATISTICS, 17-34\ntypes. See object types or data types\nTZ_OFFSET function, 5-237\n\nunique constraints\nconditional, 14-83\nenabling, 16-63\nindex on, 16-64\nunique elements of, 5-179\nunique indexes, 14-68\nunique queries, 19-15\nUNISTR function, 5-238\nuniversal rowids. See urowids\nUNLIMITED TABLESPACE system privilege, 18-45\nUNNEST hint, 3-104\nunnesting collections, 19-20\nexamples, 19-54\nunnesting subqueries, 9-15\nunpivot operations, 19-22\nexamples, 19-48\nsyntax, 19-8\nUNQUIESCE clause\nof ALTER SYSTEM, 11-67\nUNRECOVERABLE, 10-86, 16-36\nSee also NOLOGGING clause\nunsorted indexes, 14-73\nUNUSABLE clause\nof ALTER INDEX, 10-90\nUNUSABLE LOCAL INDEXES clause\nof ALTER MATERIALIZED VIEW, 11-10\nof ALTER TABLE, 12-73\nUPDATE ANY CUBE BUILD PROCESS system privilege, 18-43\nUPDATE ANY CUBE DIMENSION system privilege, 18-43\nUPDATE ANY CUBE system privilege, 18-42\nUPDATE ANY TABLE system privilege, 18-45\nUPDATE BLOCK REFERENCES clause\nof ALTER INDEX, 10-91, 10-93\nUPDATE GLOBAL INDEXES clause\nof ALTER TABLE, 12-75\nUPDATE object privilege\non a table, 18-51\non a view, 18-51\non an OLAP cube, 18-49\non an OLAP cube dimension, 18-49\nupdate operations\ncollecting supplemental log data for, 10-32\nUPDATE SET clause\nof MERGE, 18-76\nUPDATE statement, 19-72\nupdates\nand simultaneous insert, 18-75\nusing MERGE, 18-76, 18-77\nUPDATERXML function, 5-239\nUPGRADE clause\nof ALTER DATABASE, 10-20\nof ALTER TABLE, 12-36\nUPPER function, 5-240\nURLs\ngenerating, 5-207\nUROWID data type, 3-28\nurowids\nand foreign tables, 3-28\n\nand index-organized tables, 3-28\n description of, 3-28\n\nUSE_CONCAT hint, 3-105\n\nUSE_HASH hint, 3-105\n\nUSE_MERGE hint, 3-105\n\nUSE_NL hint, 3-106\n\nUSE_NL_WITH_INDEX hint, 3-106\n\nUSE_PRIVATE_OUTLINES session parameter, 11-54\n\nUSE_STORED_OUTLINES session parameter, 11-54, 11-72\n\nUSER function, 5-241\n\nuser groups\n adding or dropping a member, 10-69\n adding to a disk group, 10-69\n dropping from a disk group, 10-69\n\nUSER SYS clause\n of CREATE DATABASE, 14-22\n\nUSER SYSTEM clause\n of CREATE DATABASE, 14-22\n\nUSER_COL_COMMENTS data dictionary view, 13-45\n\nUSER_INDEXTYPE_COMMENTS data dictionary view, 13-45\n\nUSER_MVIEW_COMMENTS data dictionary view, 13-45\n\nUSER_OPERATOR_COMMENTS data dictionary view, 13-45\n\nUSER_TAB_COMMENTS data dictionary view, 13-45\n\nuser-defined functions, 5-270\n name precedence of, 5-271\n naming conventions, 5-271\n\nuser-defined operators, 4-9\n\nuser-defined statistics\n dropping, 17-50, 17-51, 17-61, 18-6, 18-13\n\nuser-defined types, 3-30\n\nUSERENV function, 5-241\n\nusers\n allocating space for, 17-11\n and database links, 14-34\n assigning\n default roles, 13-8\n profiles, 17-11\n authenticating, 13-10\n authenticating to a remote server, 14-35\n changing authentication, 13-10\n creating, 17-7\n default tablespaces for, 13-8, 17-10\n denying access to tables and views, 18-72\n external, 15-59, 17-9\n global, 15-59, 17-10\n granting system privileges for, 18-46\n local, 15-59, 17-9\n locking accounts, 17-12\n operating system\n adding to a disk group, 10-69\n dropping from a disk group, 10-69\n password expiration of, 17-12\n removing from the database, 18-16\n\nSQL examples, 17-12\n temporary tablespaces for, 13-8, 17-10\n\nUSING BFILE clause\n of CREATE JAVA, 14-94\n\nUSING BLOB clause\n of CREATE JAVA, 14-94\n\nUSING clause\n of ALTER INDEXTYPE, 10-98\n of ASSOCIATE STATISTICS, 13-24, 13-25\n of CREATE DATABASE LINK, 14-35\n of CREATE INDEXTYPE, 14-88\n\nUSING CLOB clause\n of CREATE JAVA, 14-94\n\nUSING INDEX clause\n of ALTER MATERIALIZED VIEW, 11-11\n of ALTER TABLE, 12-31\n of constraints, 8-17\n of CREATE MATERIALIZED VIEW, 15-15\n of CREATE TABLE, 16-64\n\nUSING NO INDEX clause\n of CREATE MATERIALIZED VIEW, 15-15\n\nUSING ROLLBACK SEGMENT clause\n of ALTER MATERIALIZED VIEW ...\n REFRESH, 11-14\n of CREATE MATERIALIZED VIEW, 15-19\n\nUTC\n extracting from a datetime value, 5-208\n\nUTC offset\n replacing with time zone region name, 3-52\n\nUTLCHN.SQL script, 13-20\n\nUTLEXPT1.SQL script, 12-72\n\nUTLXPLAN.SQL script, 18-20\n\nV\n\nVALIDATE clause\n of DROP TYPE, 18-14\n\nVALIDATE REF UPDATE clause\n of ANALYZE, 13-19\n\nVALIDATE STRUCTURE clause\n of ANALYZE, 13-19\n\nvalidation\n of clusters, 13-19\n of database objects\n offline, 13-20\n of database objects, online, 13-20\n of indexes, 13-19\n of tables, 13-19\n\nVALUE function, 5-242\n\nVALUES clause\n of CREATE INDEX, 14-76\n of INSERT, 18-61\n\nVALUES LESS THAN clause\n of CREATE TABLE, 16-53\n\nVAR_POP function, 5-243\n\nVAR_SAMP function, 5-244\n\nVARCHAR data type, 3-10\n\nVARCHAR2 data type, 3-10\n converting to NUMBER, 3-56\n\nVARGRAPHIC data type\n\nDB2, 3-29\nSQL/DS, 3-29\n\nVARIANCE function, 5-245\n\nVARRAY clause\nof ALTER TABLE, 12-13\n\nVARRAY column properties\nof ALTER TABLE, 12-13, 12-43\nof CREATE MATERIALIZED VIEW, 15-9\nof CREATE TABLE, 16-12, 16-47\n\nvarrays, 3-30\nchanging returned value, 12-52\ncompared with nested tables, 3-40\ncomparison rules, 3-40\ncreating, 17-3\ndropping the body of, 18-15\ndropping the specification of, 18-13\nmodifying column properties, 12-16\nstorage characteristics, 12-43, 12-53, 16-47\nstoring out of line, 3-31\n\nvarying arrays. See varrays\n\nversion queries\npseudocolumns for, 2-5\n\nview constraints, 8-18, 17-18\nand materialized views, 8-17\ndropping, 18-18\nmodifying, 13-13\n\nviews\nbase tables\nadding rows, 18-54\nchanging\ndefinition, 18-18\nvalues in base tables, 19-72\ncreating\nbefore base tables, 17-16\ncomments about, 13-44\nmultiple, 15-64\ncreating object subviews, 17-19\ndefining, 17-14\ndropping constraints on, 13-13\neditioning, 17-17\ngranting system privileges for, 18-46\nmodifying constraints on, 13-13\nobject, creating, 17-19\nrecompiling, 13-12\nre-creating, 17-16\nremote, accessing, 14-32\nremoving\nfrom the database, 18-18\nrows from the base table of, 17-26\nrenaming, 18-86\nretrieving data from, 19-4\nsubquery of, 17-20\nrestricting, 17-21\nsynonyms for, 16-2\nupdatable, 17-20\nwith joins\nand key-preserved tables, 17-21\nmaking updatable, 17-21\n\nXMLType, 17-21\nXMLType, creating, 17-25\n\nXMLType, querying, 17-21\n\nvirtual columns\nadding to a table, 12-42\ncreating, 16-28\nmodifying, 12-42\n\nVSIZE function, 5-246\n\nW\n\nWHENEVER NOT SUCCESSFUL clause\nof NOAUDIT, 18-82\n\nWHENEVER SUCCESSFUL clause\nof AUDIT sql statements, 13-33\nof NOAUDIT, 18-82\n\nWHERE clause\nof DELETE, 17-30\nof queries and subqueries, 19-25\nof SELECT, 9-4\nof UPDATE, 19-78\n\nWIDTH_BUCKET function, 5-247\n\nWITH ADMIN OPTION clause\nof GRANT, 18-36\n\nWITH CHECK OPTION clause\nof CREATE VIEW, 17-16, 17-21\nof DELETE, 17-29\nof INSERT, 18-61\nof SELECT, 19-8\nof UPDATE, 19-75\n\nWITH GRANT OPTION clause\nof GRANT, 18-38\n\nWITH HIERARCHY OPTION\nof GRANT, 18-38\n\nWITH INDEX CONTEXT clause\nof CREATE OPERATOR, 15-36\n\nWITH OBJECT ID clause\nof CREATE MATERIALIZED VIEW LOG, 15-30\n\nWITH OBJECT IDENTIFIER clause\nof CREATE VIEW, 17-19\n\nWITH OBJECT OID. See WITH OBJECT IDENTIFIER.\n\nWITH PRIMARY KEY clause\nof ALTER MATERIALIZED VIEW, 11-14\nof CREATE MATERIALIZED VIEW ...\nREFRESH, 15-18\nof CREATE MATERIALIZED VIEW LOG, 15-30\n\nWITH READ ONLY clause\nof CREATE VIEW, 17-16, 17-21\nof DELETE, 17-29\nof INSERT, 18-61\nof SELECT, 19-8\nof UPDATE, 19-75\n\nWITH ROWID clause\nof column ref constraints, 8-13\nof CREATE MATERIALIZED VIEW ...\nREFRESH, 15-18\nof CREATE MATERIALIZED VIEW LOG, 15-30\n\nWITH SEQUENCE clause\nof CREATE MATERIALIZED VIEW LOG, 15-30\n\nWRITE clause\nof COMMIT, 13-48\n\nWRITE object privilege\n\non a directory, 18-48\n\nX\n\nXML\n conditions, 7-20\n data\n storage of, 16-49\n database repository\n SQL access to, 7-20, 7-21\n documents\n producing from XML fragments, 5-210\n retrieving from the database, 5-207\n examples, F-8\n format models, 3-69\n fragments, 5-70\n functions, 5-8\nXMLAGG function, 5-248\nXMLCAST function, 5-249\nXMLCDATA function, 5-250\nXMLCOLATTVAL function, 5-251\nXMLCOMMENT function, 5-251\nXMLCONCAT function, 5-252\nXMLDATA pseudocolumn, 2-11\nXMLDIFF function, 5-253\nXMLELEMENT function, 5-254\nXML EXISTS function, 5-256\nXMLFOREST function, 5-257\nXMLGenFormatType object, 3-69\nXMLIndex\n creating, 14-79\n modifying, 10-89\nXMLISVALID function, 5-258\nXMLPARSE function, 5-258\nXMLPATCH function, 5-259\nXMLPI function, 5-260\nXMLQUERY function, 5-261\nXMLROOT function, 5-262\nXMLSchemas\n adding to a table, 16-50\n single and multiple, 16-50\nXMLSEQUENCE function, 5-263\nXMLSERIALIZE function, 5-265\nXMLTABLE function, 5-266\nXMLTRANSFORM function, 5-268\nXMLType columns\n properties of, 12-45, 16-49\n storage of, 16-49\n storing in binary XML format, 16-49\nXMLType storage clause\n of CREATE TABLE, 16-49\nXMLType tables\n creating, 16-68, 16-73\n creating index on, 14-81\nXMLType views, 17-21\n querying, 17-21\n\nIndex-50"},"books_score":{"kind":"number","value":0.5710334777832031,"string":"0.571033"}}},{"rowIdx":8683,"cells":{"content":{"kind":"string","value":"ANNUAL STATEMENT\nFOR THE YEAR ENDED DECEMBER 31, 2021\nOF THE CONDITION AND AFFAIRS OF THE SEPARATE ACCOUNTS OF THE\nANNUTY INVESTORS LIFE INSURANCE COMPANY\n\nNAIC Group Code 0435 (Current) 0384 (Prior) NAIC Company Code 93661 Employer's ID Number 31-1021738\n\nOrganized under the Laws of Ohio State of Domicile or Port of Entry OH\n\nCountry of Domicile United States of America\n\nType of Separate Accounts Insulated [X] Non-Insulated [ ]\n\nIncorporated/Organized 11/13/1981 Commenced Business 12/21/1981\n\nStatutory Home Office 301 East Fourth Street Cincinnati, OH, US 45202\n(Street and Number) (City or Town, State, Country and Zip Code)\n\nMain Administrative Office 301 East Fourth Street Cincinnati, OH, US 45202\n(Street and Number) 513-357-3300\n(City or Town, State, Country and Zip Code) (Area Code) (Telephone Number)\n\nMail Address Post Office Box 5423 Cincinnati, OH, US 45201\n(Street and Number or P.O. Box) (City or Town, State, Country and Zip Code)\n\nPrimary Location of Books and Records 301 East Fourth Street Cincinnati, OH, US 45202\n(Street and Number) 513-357-3300\n(City or Town, State, Country and Zip Code) (Area Code) (Telephone Number)\n\nInternet Website Address www.massmutual.com\n\nStatutory Statement Contact Robert Mayhew Earle II 513-412-1735\n(Name) email@example.com 513-412-1673\n(E-mail Address) (Area Code) (Telephone Number) (FAX Number)\n\nOFFICERS\n\nPresident Mark Francis Muething Treasurer Christopher Patrick Miliano\n\nSecretary John Paul Gruber Appointed Actuary Richard Lee Sutton\n\nOTHER\n\nAdrienne Susan Baglier Michael Robert Fanning # Michael Harrison Haney\n\nBrian Patrick Sponaugle\n\nDIRECTORS OR TRUSTEES\n\nDominic Luscan Blue # Elizabeth Ward Chicares # Susan Marie Cicco #\nGeoffrey James Craddock # Roger William Crandall # Michael Robert Farming #\nPaul Anthony Lapiana # Mark Francis Muething Michael James O'Connor #\nEric William Partlan # Gareth Fielding Ross # Arthur William Wallace III #\n\nState of Ohio SS\nCounty of Hamilton\n\nThe officers of this reporting entity being duly sworn, each depose and say that they are the described officers of said reporting entity, and that on the reporting period stated above, all of the herein described assets were the absolute property of the said reporting entity, free and clear of all liens, claims, encumbrances, except as herein stated, and that this statement, together with related exhibits, schedules and explanations therein contained, annexed or referred to, is a full and true statement of the assets, liabilities and of the condition and affairs of the said reporting entity as of the reporting period stated above, and of its income and deductions therefrom for the period ended, and has been prepared in accordance with the NAIC Annual Statement Instructions and Accounting Practices and Procedures manual except to the extent that: (1) state law may differ; or, (2) that state rules or regulations require differences in results not related to accounting practices and procedures, according to the best of their information, knowledge and belief, respectively. Furthermore, the scope of this attestation by the described officers also includes the related corresponding electronic filing with the NAIC, when required, that is an exact copy (except for formatting differences due to electronic filing) of the enclosed statement. The electronic filing may be requested by various regulators in lieu of or in addition to the enclosed statement.\n\nMark Francis Muething President\nJohn Paul Gruber Secretary\nChristopher Patrick Miliano Treasurer\n\nSubscribed and sworn to before me this day of February 2022\n\nSherri L Barnes\nNotary Public\nState of Ohio\nMy Comm. Expires August 9, 2025\n\n# OFFICERS AND DIRECTORS WHO DID NOT OCCUPY THE INDICATED POSITION IN THE PREVIOUS ANNUAL STATEMENT\n\n## ASSETS\n\n| Description | 1 General Account Basis | 2 Fair Value Basis | 3 Total (Cols. 1 + 2) | 4 Prior Year Total |\n|------------------------------------------------------------------------------|-------------------------|--------------------|----------------------|--------------------|\n| 1. Bonds (Schedule D) | | | | |\n| 2. Stocks (Schedule D): | | | | |\n| 2.1 Preferred stocks | | | | |\n| 2.2 Common stocks | 690,771,210 | | 690,771,210 | 663,544,638 |\n| 3. Mortgage loans on real estate (Schedule B) | | | | |\n| 4. Real estate (Schedule A): | | | | |\n| 4.1 Properties held for the production of income (less $ encumbrances) | | | | |\n| 4.2 Properties held for sale (less $ encumbrances) | | | | |\n| 5. Cash ($ Schedule E - Part 1), and cash equivalents ($ , Schedule E - Part 2) | | | | |\n| 6. Short-term investments (Schedule DA) | | | | |\n| 7. Derivatives (Schedule DB) | | | | |\n| 8. Other invested assets (Schedule BA) | | | | |\n| 9. Securities lending reinvested collateral assets (Schedule DL) | | | | |\n| 10. Aggregate write-ins for invested assets | 0 | 0 | 0 | 0 |\n| 11. Subtotals, cash and invested assets (Lines 1 to 10) | 690,771,210 | 0 | 690,771,210 | 663,544,638 |\n| 12. Investment income due and accrued | | | | |\n| 13. Receivables for securities | | | | |\n| 14. Net adjustment in assets and liabilities due to foreign exchange rates | | | | |\n| 15. Aggregate write-ins for other than invested assets | 0 | 0 | 0 | 0 |\n| 16. Total (Lines 11 to 15) | 690,771,210 | 0 | 690,771,210 | 663,544,638 |\n\n### DETAILS OF WRITE-INS\n\n| Line | Description | 1 General Account Basis | 2 Fair Value Basis | 3 Total (Cols. 1 + 2) | 4 Prior Year Total |\n|------|------------------------------------------------------------------------------|-------------------------|--------------------|----------------------|--------------------|\n| 1001.| | | | | |\n| 1002.| | | | | |\n| 1003.| | | | | |\n| 1098.| Summary of remaining write-ins for Line 10 from overflow page | 0 | 0 | 0 | 0 |\n| 1099.| Totals (Lines 1001 thru 1003 plus 1098)(Line 10 above) | 0 | 0 | 0 | 0 |\n| 1501.| | | | | |\n| 1502.| | | | | |\n| 1503.| | | | | |\n| 1598.| Summary of remaining write-ins for Line 15 from overflow page | 0 | 0 | 0 | 0 |\n| 1599.| Totals (Lines 1501 thru 1503 plus 1598)(Line 15 above) | 0 | 0 | 0 | 0 |\n\n## LIABILITIES AND SURPLUS\n\n| Description | 1 General Account Basis | 2 Fair Value Basis | 3 Total (Cols. 1 + 2) | 4 Prior Year Total |\n|------------------------------------------------------------------------------|-------------------------|--------------------|----------------------|--------------------|\n| 1. Aggregate reserve for life, annuity and accident and health contracts | 690,771,091 | | 690,771,091 | 661,963,244 |\n| (Exhibit 3, Line 9999999, Col. 2) | | | | |\n| 2. Liability for deposit-type contracts (Exhibit 4, Line 9, Col. 1) | | | 0 | 0 |\n| 3. Interest Maintenance Reserve | | | 0 | 0 |\n| 4. Charges for investment management, administration and contract guarantees due or accrued | | | 0 | 0 |\n| 5. Investment expenses due or accrued (Exhibit 1, Line 24) | | | 0 | 0 |\n| 6. Investment taxes, licenses and fees due or accrued, excluding federal income taxes (Exhibit 2, Line 8) | | | 0 | 0 |\n| 7. Federal and foreign income taxes due or accrued (excluding deferred taxes) | | | 0 | 0 |\n| 8. Reserve for future federal income taxes | | | 0 | 0 |\n| 9. Unearned investment income | | | 0 | 0 |\n| 10. Other transfers to general account due or accrued (net) (including $ 119 accrued expense allowances recognized in reserves) | 19 | | 119 | 1,581,394 |\n| 11. Remittances and items not allocated | | | 0 | 0 |\n| 12. Derivatives | | | 0 | 0 |\n| 13. Payable for securities | | | 0 | 0 |\n| 14. Payable for securities lending | | | 0 | 0 |\n| 15. Net adjustment in assets and liabilities due to foreign exchange rates | | | 0 | 0 |\n| 16. Aggregate write-ins for liabilities | 0 | 0 | 0 | 0 |\n| 17. Total liabilities (including $ 119 due or accrued net transfers to or (from) the general account) | 690,771,210 | 0 | 690,771,210 | 663,544,638 |\n| 18. Contributed surplus | | | 0 | 0 |\n| 19. Aggregate write-ins for special surplus funds | 0 | 0 | 0 | 0 |\n| 20. Unassigned funds | | | 0 | 0 |\n| 21. Surplus (Lines 18 through 20) | 0 | 0 | 0 | 0 |\n| 22. Totals | 690,771,210 | 0 | 690,771,210 | 663,544,638 |\n\n### DETAILS OF WRITE-INS\n\n| Line | Description | 1 General Account Basis | 2 Fair Value Basis | 3 Total (Cols. 1 + 2) | 4 Prior Year Total |\n|------|------------------------------------------------------------------------------|-------------------------|--------------------|----------------------|--------------------|\n| 1601.| | | | | |\n| 1602.| | | | | |\n| 1603.| | | | | |\n| 1698.| Summary of remaining write-ins for Line 16 from overflow page | 0 | 0 | 0 | 0 |\n| 1699.| Totals (Lines 1601 thru 1603 plus 1698)(Line 16 above) | 0 | 0 | 0 | 0 |\n| 1901.| | | | | |\n| 1902.| | | | | |\n| 1903.| | | | | |\n| 1998.| Summary of remaining write-ins for Line 19 from overflow page | 0 | 0 | 0 | 0 |\n| 1999.| Totals (Lines 1901 thru 1903 plus 1998)(Line 19 above) | 0 | 0 | 0 | 0 |\n\n## SUMMARY OF OPERATIONS\n\n| Description | 1 Current Year | 2 Prior Year |\n|----------------------------------------------------------------------------|----------------|--------------|\n| **1. Transfers to Separate Accounts:** | | |\n| 1.1 Net premiums and annuity considerations for life and accident and health contracts | 11,913,442 | 14,765,363 |\n| 1.2 Considerations for supplementary contracts with life contingencies | 0 | 0 |\n| 1.3 Aggregate write-ins for other transfers to Separate Accounts | 0 | 0 |\n| 1.4 Totals (Lines 1.1 to 1.3) | 11,913,442 | 14,765,363 |\n| **2. Transfers on account of deposit-type contracts (including $ deposits, less $ withdrawals)** | 0 | 0 |\n| **3. Net investment income and capital gains and losses** | 114,675,371 | 105,170,467 |\n| **4. Aggregate write-ins for other income** | 0 | 0 |\n| **5. Totals (Lines 1.4 to 4)** | 126,588,813 | 119,935,830 |\n\n**DEDUCT:**\n\n| Description | | |\n|----------------------------------------------------------------------------|----------------|--------------|\n| **6. Transfers from the Separate Account on account of contract benefits:** | | |\n| 6.1 Death benefits | 0 | 0 |\n| 6.2 Matured endowments | 0 | 0 |\n| 6.3 Annuity benefits | 0 | 0 |\n| 6.4 Payments on supplementary contracts with life contingencies | 0 | 0 |\n| 6.5 Accident and health benefits | 0 | 0 |\n| 6.6 Surrender benefits and withdrawals for life contracts | 86,860,790 | 65,450,560 |\n| 6.7 Aggregate write-ins for other transfers from Separate Accounts on account of contract benefits | 0 | 0 |\n| **7. Transfers on account of policy loans** | 0 | 0 |\n| **8. Net transfers of reserves from or (to) Separate Accounts** | 3,243,122 | 10,565,427 |\n| **9. Other transfers from the Separate Accounts:** | | |\n| 9.1 Federal and foreign income taxes incurred | 0 | 0 |\n| 9.2 Change in expense allowances recognized in reserves | (1,581,277) | (614,646) |\n| 9.3 Aggregate write-ins for other transfers from Separate Accounts | 0 | 0 |\n| **10. Subtotals (Lines 6.1 to 9.3)** | 88,522,635 | 75,401,341 |\n| **11. Fees associated with charges for investment management, administration and contract guarantees** | 9,258,331 | 8,055,326 |\n| **12. Increase in aggregate reserve for life and accident and health contracts** | 28,807,847 | 36,479,163 |\n| **13. Increase in liability for deposit-type contracts** | 0 | 0 |\n| **14. Increase in reserve for future federal income taxes** | 0 | 0 |\n| **15. Aggregate write-ins for reserves and funds** | 0 | 0 |\n| **16. Totals (Lines 10 to 15)** | 126,588,813 | 119,935,830 |\n| **17. Net gain from operations (including $ unrealized capital gains) (Line 5 minus Line 16)** | 0 | 0 |\n\n### SURPLUS ACCOUNT\n\n| Description | | |\n|----------------------------------------------------------------------------|----------------|--------------|\n| **18. Surplus, December 31, prior year** | 0 | 0 |\n| **19. Net gain from operations (Line 17)** | 0 | 0 |\n| **20. Surplus, beginning or (withdrawn) during year** | 0 | 0 |\n| **21. Change in reserve on account of change in valuation basis, (increase) or decrease** | 0 | 0 |\n| **22. Transfer from Separate Accounts of the change in expense allowances recognized in Line 21** | 0 | 0 |\n| **23. Aggregate write-ins for gains and losses in surplus** | 0 | 0 |\n| **24. Surplus, December 31, current year (Page 3, Line 21)** | 0 | 0 |\n\n### DETAILS OF WRITE-INS\n\n| Description | | |\n|----------------------------------------------------------------------------|----------------|--------------|\n| **01.301.** | | |\n| **01.302.** | | |\n| **01.303.** | | |\n| **01.398. Summary of remaining write-ins for Line 1.3 from overflow page** | 0 | 0 |\n| **01.399. Totals (Lines 01.301 thru 01.303 plus 01.398)(Line 1.3 above)** | 0 | 0 |\n| **0401.** | | |\n| **0402.** | | |\n| **0403.** | | |\n| **0498. Summary of remaining write-ins for Line 4 from overflow page** | 0 | 0 |\n| **0499. Totals (Lines 0401 thru 0403 plus 0498)(Line 4 above)** | 0 | 0 |\n| **06.701.** | | |\n| **06.702.** | | |\n| **06.703.** | | |\n| **06.798. Summary of remaining write-ins for Line 6.7 from overflow page** | 0 | 0 |\n| **06.799. Totals (Lines 06.701 thru 06.703 plus 06.798)(Line 6.7 above)** | 0 | 0 |\n| **09.301.** | | |\n| **09.302.** | | |\n| **09.303.** | | |\n| **09.398. Summary of remaining write-ins for Line 9.3 from overflow page** | 0 | 0 |\n| **09.399. Totals (Lines 09.301 thru 09.303 plus 09.398)(Line 9.3 above)** | 0 | 0 |\n| **1501.** | | |\n| **1502.** | | |\n| **1503.** | | |\n| **1598. Summary of remaining write-ins for Line 15 from overflow page** | 0 | 0 |\n| **1599. Totals (Lines 1501 thru 1503 plus 1598)(Line 15 above)** | 0 | 0 |\n| **2301.** | | |\n| **2302.** | | |\n| **2303.** | | |\n| **2398. Summary of remaining write-ins for Line 23 from overflow page** | 0 | 0 |\n| **2399. Totals (Lines 2301 thru 2303 plus 2398)(Line 23 above)** | 0 | 0 |\n\n## ANNUAL STATEMENT FOR THE YEAR 2021 OF THE SEPARATE ACCOUNTS OF THE ANNUITY INVESTORS LIFE INSURANCE COMPANY\n\n### ANALYSIS OF OPERATIONS BY LINES OF BUSINESS - SUMMARY\n\n| Line | Description | Total | Individual Life | Group Life | Individual Annuities | Group Annuities | Accident and Health | Other Lines of Business |\n|------|-----------------------------------------------------------------------------|-------|-----------------|------------|----------------------|-----------------|---------------------|------------------------|\n| 1 | Transfers to Separate Account | | | | | | | |\n| | 1.1 Net premiums and annuity considerations for life and accident and health contracts | 11,813,442 | XXX | XXX | 10,906,268 | 1,007,174 | XXX | |\n| | 1.2 Considerations for supplementary contracts with life contingencies | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 1.3 Aggregate write-ins for other transfers to Separate Accounts | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 1.4 Totals (Lines 1.1 to 1.3) | 11,813,442 | 0 | 0 | 10,906,268 | 1,007,174 | 0 | 0 |\n| 2 | Transfers to account of deposit-type contracts (including $ deposits less $ withdrawals) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 3 | Net investment income and capital gains and losses | 114,675,371 | 0 | 0 | 94,797,273 | 19,878,098 | 0 | 0 |\n| 4 | Aggregate write-ins for other income | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 5 | Totals (Lines 1.4 to 4) | 126,588,813 | 0 | 0 | 105,703,541 | 20,885,272 | 0 | 0 |\n| DEDUCT: | | | | | | | |\n| 6 | Transfers from the Separate Account on account of contract benefits: | | | | | | | |\n| | 6.1 Death benefits | 0 | 0 | 0 | 0 | 0 | XXX | |\n| | 6.2 Maturity dividends | 0 | 0 | 0 | 0 | 0 | XXX | |\n| | 6.3 Annuity benefits | 0 | XXX | XXX | 0 | 0 | XXX | |\n| | 6.4 Payments on supplementary contracts with life contingencies | 0 | XXX | XXX | 0 | 0 | XXX | |\n| | 6.5 Accident and health benefits | 0 | XXX | XXX | XXX | XXX | XXX | |\n| | 6.6 Surrender benefits and withdrawals for life contracts | 86,860,790 | 68,844,435 | 18,016,355 | 0 | 0 | 0 | 0 |\n| | 6.7 Aggregate write-ins for other transfers from Separate Accounts on account of contract benefits | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 7. Transfers on account of policy loans | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 8. Net increase in reserves (decrease in) Separate Accounts | 3,243,722 | 0 | 0 | 2,247,784 | 995,338 | 0 | 0 |\n| | 9. Other transfers from the Separate Accounts: | | | | | | | |\n| | 9.1 Federal and foreign income taxes incurred | 0 | 0 | 0 | 0 | 0 | XXX | |\n| | 9.2 Change in expense allowances recognized in reserves | 0 | 0 | 0 | 0 | 0 | XXX | |\n| | 9.3 Aggregate write-ins for other transfers from Separate Accounts | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 10 | Subtotals (Lines 8.1 to 9.3) | 88,522,635 | 0 | 0 | 69,510,942 | 19,011,683 | 0 | 0 |\n| 11 | Fees associated with policies such as investment management, administration and contract guarantees | 9,258,331 | 0 | 0 | 7,688,327 | 1,589,004 | 0 | 0 |\n| 12 | Increase in liability reserves for life and accident and health contracts | 28,607,867 | 0 | 0 | 28,523,272 | 284,575 | 0 | 0 |\n| 13 | Increase in liability for deposit-type contracts | 0 | 0 | 0 | 0 | 0 | XXX | |\n| 14 | Increase in reserve for future federal income taxes | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 15 | Aggregate write-ins for reserves and funds | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 16 | Totals (Lines 10 to 15) | 126,588,813 | 0 | 0 | 105,703,541 | 20,885,272 | 0 | 0 |\n| 17 | Net gain from operations (including $ unrealized capital gains) (Line 5 minus Line 16) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 18 | Policies/certificates in force end of year | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\n### DETAILS OF WRITE-INS\n\n| Line | Description | Total | Individual Life | Group Life | Individual Annuities | Group Annuities | Accident and Health | Other Lines of Business |\n|------|-----------------------------------------------------------------------------|-------|-----------------|------------|----------------------|-----------------|---------------------|------------------------|\n| 01301 | | | | | | | | |\n| 01302 | | | | | | | | |\n| 01303 | | | | | | | | |\n| 01398 | Summary of remaining write-ins for Line 1.3 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 01398 | Totals (Lines 01.301 thru 01.303 plus 01.398) (Line 1.3 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 0401 | | | | | | | | |\n| 0402 | | | | | | | | |\n| 0403 | | | | | | | | |\n| 0498 | Summary of remaining write-ins for Line 4 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 0499 | Totals (Lines 0401 thru 0403 plus 0498) (Line 4 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 06701 | | | | | | | | |\n| 06702 | | | | | | | | |\n| 06703 | | | | | | | | |\n| 06798 | Summary of remaining write-ins for Line 6.7 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 06799 | Totals (Lines 06.701 thru 06.703 plus 06.798) (Line 6.7 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 09301 | | | | | | | | |\n| 09302 | | | | | | | | |\n| 09303 | | | | | | | | |\n| 09398 | Summary of remaining write-ins for Line 9.3 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 09399 | Totals (Lines 09.301 thru 09.303 plus 09.398) (Line 9.3 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1501 | | | | | | | | |\n| 1502 | | | | | | | | |\n| 1503 | | | | | | | | |\n| 1598 | Summary of remaining write-ins for Line 15 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1599 | Totals (Lines 1501 thru 1503 plus 1598) (Line 15 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\nAnalysis of Operations by Lines of Business - Individual Life Insurance\n\nNONE\n\nAnalysis of Operations by Lines of Business - Group Life Insurance\n\n## ANALYSIS OF OPERATIONS BY LINES OF BUSINESS - INDIVIDUAL ANNUITIES (a)\n\n| Line | Description | Total | Fixed Annuities | Indexed Annuities | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuitizations) | Other Annuities |\n|------|-----------------------------------------------------------------------------|-------|-----------------|--------------------|-----------------------------------|----------------------------------------|-----------------------------------------------------|-----------------|\n| 1 | Transfers to Separate Accounts: | | | | | | | |\n| | 1.1 Cash and other consideration for annuity contracts | 10,906,388 | XXX | XXX | XXX | XXX | | XXX |\n| | 1.2 Consideration for supplementary contracts with life contingencies | 0 | 0 | 0 | 0 | 0 | | 0 |\n| | 1.3 Aggregate write-ins for other transfers to Separate Accounts | 0 | 0 | 0 | 0 | 0 | | 0 |\n| | 1.4 Totals (Lines 1.1 to 1.3) | 10,906,388 | 0 | 0 | 10,906,388 | 0 | | 0 |\n| 2 | Transfers to account of deposit-type contracts (including $ deposits less $ withdrawals) | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 3 | Net investment income and capital gains and losses | 94,797,273 | 0 | 0 | 94,797,273 | 0 | | 0 |\n| 4 | Net investment income for other income | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 5 | Totals (Lines 1.4 to 4) | 105,703,541 | 0 | 0 | 105,703,541 | 0 | | 0 |\n| | DEDUCT: | | | | | | | |\n| 6 | Transfers from the Separate Account on account of contract benefits: | | | | | | | |\n| | 6.1 Death benefits | 0 | 0 | 0 | 0 | 0 | | 0 |\n| | 6.2 Accidental death benefits | 0 | 0 | 0 | 0 | 0 | | 0 |\n| | 6.3 Annuity benefits | 0 | XXX | XXX | XXX | XXX | | XXX |\n| | 6.4 Payments for supplementary contracts with life contingencies | 0 | XXX | XXX | XXX | XXX | | XXX |\n| | 6.5 Accident and health benefits | 0 | XXX | XXX | XXX | XXX | | XXX |\n| | 6.6 Surrender benefits and withdrawals for life contracts | 68,844,435 | XXX | XXX | XXX | XXX | | XXX |\n| | 6.7 Aggregate write-ins for other transfers from Separate Accounts on account of contract benefits | 0 | 0 | 0 | 0 | 0 | | 0 |\n| | 6.8 Totals (Lines 6.1 to 6.7) | 68,844,435 | 0 | 0 | 68,844,435 | 0 | | 0 |\n| 7 | Transfers on account of reserve loans | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 8 | Net transfer of reserves from or (to) Separate Accounts | 2,247,784 | 0 | 0 | 2,247,784 | 0 | | 0 |\n| 9 | Other transfers from Separate Accounts | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 10 | 1 Federal and foreign income taxes incurred | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 11 | 2 Change in expense allowances recognized in reserves | (1,581,277) | 0 | 0 | (1,581,277) | 0 | | 0 |\n| 12 | 3 Aggregate write-ins for other transfers from Separate Accounts | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 13 | Subtotals (Lines 6.1 to 9.3) | 89,510,942 | 0 | 0 | 89,510,942 | 0 | | 0 |\n| 14 | Fees associated with charges for investment management, administration and contract guarantees | 7,669,337 | 0 | 0 | 7,669,337 | 0 | | 0 |\n| 15 | Increase in aggregate reserves for life and accident and health contracts | 28,383,372 | 0 | 0 | 28,383,372 | 0 | | 0 |\n| 16 | Increase in liability for deposit-type contracts | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 17 | Increase in reserve for future federal income taxes | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 18 | Increase in other reserves and funds | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 19 | Totals (Lines 10 to 15) | 105,703,541 | 0 | 0 | 105,703,541 | 0 | | 0 |\n| 20 | 17 Net gain from operations (including $ unrealized capital gains) (Line 15 minus Line 16) | 0 | 0 | 0 | 0 | 0 | | 0 |\n| 21 | 18 Net change in reserves at end of year | 0 | 0 | 0 | 0 | 0 | | 0 |\n\n### DETAILS OF WRITE-INS\n\n#### 01\n- 01.301\n- 01.302\n- 01.303\n- 01.398 Summary of remaining write-ins for Line 1.3 from overflow page\n- 01.399 Totals (Lines 01.301 thru 01.303 plus 01.398) (Line 1.3 above)\n- 02.01\n- 04.02\n- 04.03\n- 04.98 Summary of remaining write-ins for Line 4 from overflow page\n- 04.99 Totals (Lines 04.01 thru 04.03 plus 04.98) (Line 4 above)\n- 06.701\n- 06.702\n- 06.703\n- 06.798 Summary of remaining write-ins for Line 6.7 from overflow page\n- 06.799 Totals (Lines 06.701 thru 06.703 plus 06.798) (Line 6.7 above)\n- 09.301\n- 09.302\n- 09.303\n- 09.398 Summary of remaining write-ins for Line 9.3 from overflow page\n- 09.399 Totals (Lines 09.301 thru 09.303 plus 09.398) (Line 9.3 above)\n- 15.01\n- 15.02\n- 15.03\n- 15.98 Summary of remaining write-ins for Line 15 from overflow page\n- 15.99 Totals (Lines 15.01 thru 15.03 plus 15.98) (Line 15 above)\n\n(a) Indicate if blocks of business in run-off that comprise less than 5% of premiums and less than 5% of reserve and loans liability are aggregated with material blocks of business and which columns are affected.\n\n## ANNUAL STATEMENT FOR THE YEAR 2021 OF THE SEPARATE ACCOUNTS OF THE ANNUITY INVESTORS LIFE INSURANCE COMPANY\n\n### ANALYSIS OF OPERATIONS BY LINES OF BUSINESS - GROUP ANNUITIES (a)\n\n#### (N/A Fraternal)\n\n| Line | Description | Total | Fixed Annuities | Indexed Annuities | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuitizations) | Other Annuities |\n|------|-----------------------------------------------------------------------------|-------|-----------------|--------------------|-----------------------------------|----------------------------------------|--------------------------------------------------------|-----------------|\n| 1 | Transfers to Separate Accounts: | | | | | | | |\n| | 1.1 Net annuity considerations for annuity contracts | 1,007,174 | XXX | XXX | XXX | XXX | | XXX |\n| | 1.2 Considerations for supplementary contracts with life contingencies | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 1.3 Aggregate write-ins for other transfers to Separate Accounts | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 1.4 Totals (Lines 1.1 to 1.3) | 1,007,174 | 0 | 0 | 1,007,174 | 0 | 0 | 0 |\n| 2 | Transfers on account of deposit-type contracts (including $ deposits less $ withdrawals) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 3 | Net investment income and capital gains and losses | 19,878,098 | 0 | 0 | 19,878,098 | 0 | 0 | 0 |\n| 4 | Net premiums credited for other income | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 5 | Totals (Lines 1.4 to 4) | 20,885,272 | 0 | 0 | 20,885,272 | 0 | 0 | 0 |\n| DEDUCT: | | | | | | | |\n| 6 | Transfers from the Separate Account on account of contract benefits: | | | | | | | |\n| | 6.1 Death benefits | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 6.2 Maturity payments | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 6.3 Surrender benefits | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 6.4 Payments on supplementary contracts with life contingencies | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 6.5 Accident and health benefits | XXX | XXX | XXX | XXX | XXX | XXX | XXX |\n| | 6.6 Transfer benefits and withdrawals for life contracts | 18,016,355 | XXX | XXX | XXX | XXX | XXX | XXX |\n| | 6.7 Aggregate write-ins for other transfers from Separate Accounts on account of contract benefits | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 7. Transfers on account of policy loans (to) Separate Accounts | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 8. Net transfers of reserves (to) Separate Accounts | 995,338 | 0 | 0 | 995,338 | 0 | 0 | 0 |\n| | 9. Other transfers from the Separate Accounts | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 9.1 Federal income tax income recognized | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 9.2 Change in expense allowances recognized in reserves | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| | 9.3 Aggregate write-ins for other transfers from Separate Accounts | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 10 | Totals (Lines 6.1 to 9) | 19,011,692 | 0 | 0 | 19,011,692 | 0 | 0 | 0 |\n| 11 | Fees associated with charges for investment management, administration and contract guarantees | 1,589,004 | 0 | 0 | 1,589,004 | 0 | 0 | 0 |\n| 12 | Increase in aggregate reserve for life and accident and health contracts | 284,575 | 0 | 0 | 284,575 | 0 | 0 | 0 |\n| 13 | Increase in reserve for reserves and funds | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 14 | Increase in reserve for future federal income taxes | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 15 | Aggregate write-ins for reserves and funds | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 16 | Totals (Line 10 minus 15) | 20,885,272 | 0 | 0 | 20,885,272 | 0 | 0 | 0 |\n| 17 | Net gain from operations (including $ unrealized capital gains) (Line 5 minus Line 16) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 18 | Policies/certificates in force end of year | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\n### DETAILS OF WRITE-INS\n\n| Line | Description | Total | Fixed Annuities | Indexed Annuities | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuitizations) | Other Annuities |\n|------|-----------------------------------------------------------------------------|-------|-----------------|--------------------|-----------------------------------|----------------------------------------|--------------------------------------------------------|-----------------|\n| 01301 | | | | | | | | |\n| 01302 | | | | | | | | |\n| 01303 | | | | | | | | |\n| 01398 | Summary of remaining write-ins for Line 1.3 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 01399 | Totals (Lines 01.301 thru 01.303 plus 01.398) (Line 1.3 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\n| Line | Description | Total | Fixed Annuities | Indexed Annuities | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuitizations) | Other Annuities |\n|------|-----------------------------------------------------------------------------|-------|-----------------|--------------------|-----------------------------------|----------------------------------------|--------------------------------------------------------|-----------------|\n| 0401 | | | | | | | | |\n| 0402 | | | | | | | | |\n| 0403 | | | | | | | | |\n| 0498 | Summary of remaining write-ins for Line 4 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 0499 | Totals (Lines 0401 thru 0403 plus 0498) (Line 4 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\n| Line | Description | Total | Fixed Annuities | Indexed Annuities | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuitizations) | Other Annuities |\n|------|-----------------------------------------------------------------------------|-------|-----------------|--------------------|-----------------------------------|----------------------------------------|--------------------------------------------------------|-----------------|\n| 06701 | | | | | | | | |\n| 06702 | | | | | | | | |\n| 06703 | | | | | | | | |\n| 06798 | Summary of remaining write-ins for Line 6.7 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 06799 | Totals (Lines 06.701 thru 06.703 plus 06.798) (Line 6.7 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\n| Line | Description | Total | Fixed Annuities | Indexed Annuities | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuitizations) | Other Annuities |\n|------|-----------------------------------------------------------------------------|-------|-----------------|--------------------|-----------------------------------|----------------------------------------|--------------------------------------------------------|-----------------|\n| 09301 | | | | | | | | |\n| 09302 | | | | | | | | |\n| 09303 | | | | | | | | |\n| 09398 | Summary of remaining write-ins for Line 9.3 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 09399 | Totals (Lines 09.301 thru 09.303 plus 09.398) (Line 9.3 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\n| Line | Description | Total | Fixed Annuities | Indexed Annuities | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuitizations) | Other Annuities |\n|------|-----------------------------------------------------------------------------|-------|-----------------|--------------------|-----------------------------------|----------------------------------------|--------------------------------------------------------|-----------------|\n| 1501 | | | | | | | | |\n| 1502 | | | | | | | | |\n| 1503 | | | | | | | | |\n| 1598 | Summary of remaining write-ins for Line 15 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1599 | Totals (Lines 1501 thru 1503 plus 1598) (Line 15 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\n(a) Indicate if blocks of business in run-off that comprise less than 5% of premiums and less than 5% of reserve and loans liability are aggregated with material blocks of business and which columns are affected.\n\nAnalysis of Operations by Lines of Business - Accident and Health\n\nNONE\n\nAnalysis of Increase in Reserves During the Year - Individual Life Insurance\n\nNONE\n\nAnalysis of Increase in Reserves During the Year - Group Life Insurance\n\n| | 1 Total | 2 Fixed Annuities | 3 Indexed Annuities | Deferred | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuities) | Other Annuities |\n|---|---------|-------------------|---------------------|----------|----------------------------------|--------------------------------------|-------------------------------------------------|----------------|\n| 1. Reserve December 31 of prior year | 548,350,745 | 0 | 0 | 548,350,745 | 0 | 0 | 0 | 0 |\n| 2. Tabular net premiums and considerations | 10,906,268 | | | 10,906,268 | | | | |\n| 3. Increase or (decrease) from investment results after provision for federal income taxes | 94,797,273 | | | 94,797,273 | | | | |\n| 4. Tabular less actual reserve released | 0 | | | 0 | | | | |\n| 5. Increase in reserve on account of change in valuation basis | 0 | | | 0 | | | | |\n| 6. Other increases (net) | 0 | | | 0 | | | | |\n| 7. Totals (Lines 1 to 6) | 654,054,286 | 0 | 0 | 654,054,286 | 0 | 0 | 0 | 0 |\n| 8. Net transfer of reserves from or (to) Separate Accounts | 2,247,784 | | | 2,247,784 | | | | |\n| 9. Tabular cost | 0 | | | 0 | | | | |\n| 10. Reserves released by death | XXX | XXX | XXX | XXX | XXX | XXX | XXX | XXX |\n| 11. Reserves released by other terminations (net) | 68,844,435 | | | 68,844,435 | | | | |\n| 12. Transfers on account of annuity and supplementary contract payments involving life contingencies | 0 | | | 0 | | | | |\n| 13. Charges for investment management, administration and contract guarantees | 7,669,327 | | | 7,669,327 | 0 | 0 | 0 | 0 |\n| 14. Aggregate write-ins for other decreases in reserves | (1,581,277) | 0 | 0 | (1,581,277) | 0 | 0 | 0 | 0 |\n| 15. Total deductions (Lines 8 to 14) | 77,180,269 | 0 | 0 | 77,180,269 | 0 | 0 | 0 | 0 |\n| 16. Reserve December 31 of current year | 576,874,017 | 0 | 0 | 576,874,017 | 0 | 0 | 0 | 0 |\n| **Cash Surrender Values and Policy Loans** | | | | | | | | |\n| 17. CSV ending balance December 31, current year | 569,097,309 | | | 569,097,309 | | | | |\n| 18. Amount available for policy loans based upon line 17 CSV | 565,989,488 | | | 565,989,488 | | | | |\n| **DETAILS OF WRITE-INS** | | | | | | | | |\n| 1401. Change in expense allowance recognized in reserves | (1,581,277) | | | (1,581,277) | | | | |\n| 1402. | | | | | | | | |\n| 1403. | | | | | | | | |\n| 1498. Summary of remaining write-ins for Line 14 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1499. TOTALS (Lines 1401 thru 1403 plus 1498) (Line 14 above) | (1,581,277) | 0 | 0 | (1,581,277) | 0 | 0 | 0 | 0 |\n\n(a) indicate if blocks of business in run-off that comprise less than 5% of premiums and less than 5% of reserve and loans liability are aggregated with material blocks of business and which columns are affected.\n\n| Line | Description | Total | Fixed Annuities | Indexed Annuities | Variable Annuities With Guarantees | Variable Annuities Without Guarantees | Life Contingent Payout (Immediate and Annuitizations) | Other Annuities |\n|------|-----------------------------------------------------------------------------|-------|-----------------|--------------------|-----------------------------------|--------------------------------------|-----------------------------------------------------|-----------------|\n| 1 | Reserve December 31 of prior year | 113,612,499 | 0 | 0 | 113,612,499 | 0 | 0 | 0 |\n| 2 | Tabular net premiums and considerations | 1,007,174 | 0 | 0 | 1,007,174 | 0 | 0 | 0 |\n| 3 | Increase or (decrease) from investment results after provision for federal income taxes | 19,878,098 | 0 | 0 | 19,878,098 | 0 | 0 | 0 |\n| 4 | Tabular less actual reserve released | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 5 | Increase or decrease on account of change in valuation basis | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 6 | Other increases (net) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 7 | Totals (Lines 1 to 6) | 134,497,771 | 0 | 0 | 134,497,771 | 0 | 0 | 0 |\n| 8 | Net transfer of reserves from or (to) Separate Accounts | 995,338 | 0 | 0 | 995,338 | 0 | 0 | 0 |\n| 9 | Tabular cost | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 10 | Reserves released by death | XXX | XXX | XXX | XXX | XXX | XXX | XXX |\n| 11 | Reserves released by other terminations (net) | 18,016,355 | 0 | 0 | 18,016,355 | 0 | 0 | 0 |\n| 12 | Transfers on account of annuity and supplementary contract payments involving life contingencies | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 13 | Charges for investment management, administration and contract guarantees | 1,589,004 | 0 | 0 | 1,589,004 | 0 | 0 | 0 |\n| 14 | Aggregate write-ins for other decreases in reserves | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 15 | Total deductions (Lines 8 to 14) | 20,600,697 | 0 | 0 | 20,600,697 | 0 | 0 | 0 |\n| 16 | Reserve December 31 of current year | 113,897,074 | 0 | 0 | 113,897,074 | 0 | 0 | 0 |\n| | **Cash Surrender Value and Policy Loans** | | | | | | | |\n| 17 | CSV ending balance December 31, current year | 111,881,093 | 0 | 0 | 111,881,093 | 0 | 0 | 0 |\n| 18 | Amount available for policy loans based upon line 17 CSV | 110,925,655 | 0 | 0 | 110,925,655 | 0 | 0 | 0 |\n| | **DETAILS OF WRITE-INS** | | | | | | | |\n| 1401.| | | | | | | | |\n| 1402.| | | | | | | | |\n| 1403.| | | | | | | | |\n| 1498.| Summary of remaining write-ins for Line 14 from overflow page | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1499.| TOTALS (Lines 1401 thru 1403 plus 1498) (Line 14 above) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n\n(a) Indicate if blocks of business in run-off that comprise less than 5% of premiums and less than 5% of reserve and loans liability are aggregated with material blocks of business and which columns are affected.\n\n## ANALYSIS OF RESERVES DURING THE YEAR - ACCIDENT AND HEALTH\n\n| Line | Description | 1 Total | 2 Individual | 3 Group | 4 Medicare Supplement | 5 Vision Only | 6 Dental Only | 7 Federal Employees Health Benefits Plan | 8 Title XVIII Medicare | 9 Title XIX Medicaid | 10 Credit A&H | 11 Disability Income | 12 Long-Term Care | 13 Other Health |\n|------|-----------------------------------------------------------------------------|---------|--------------|---------|-----------------------|---------------|--------------|------------------------------------------|------------------------|---------------------|-----------------|---------------------|------------------|------------------|\n| **ACTIVE LIFE RESERVE** | | | | | | | | | | | | | |\n| 1 | Unearned premium reserves | | | | | | | | | | | | | |\n| 2 | Additional contract reserves (a) | | | | | | | | | | | | | |\n| 3 | Additional actuarial reserves-Asset/Liability analysis | | | | | | | | | | | | | |\n| 4 | Reserve for future contingent benefits | | | | | | | | | | | | | |\n| 5 | Reserve for rate credits | | | | | | | | | | | | | |\n| 6 | Aggregate write-ins for reserves | | | | | | | | | | | | | |\n| 7 | Totals (Gross) | | | | | | | | | | | | | |\n| 8 | Reinsurance ceded | | | | | | | | | | | | | |\n| 9 | Totals (Net) | | | | | | | | | | | | | |\n| **CLAIM RESERVE** | | | | | | | | | | | | | |\n| 10 | Present value of amounts not yet due on claims | | | | | | | | | | | | | |\n| 11 | Additional actuarial reserves-Asset/Liability analysis | | | | | | | | | | | | | |\n| 12 | Reserve for future contingent benefits | | | | | | | | | | | | | |\n| 13 | Aggregate write-ins for reserves | | | | | | | | | | | | | |\n| 14 | Totals (Gross) | | | | | | | | | | | | | |\n| 15 | Reinsurance ceded | | | | | | | | | | | | | |\n| 16 | Totals (Net) | | | | | | | | | | | | | |\n| 17 | TOTAL | | | | | | | | | | | | | |\n| 18 | TOTAL PLUS FUND INTEREST | | | | | | | | | | | | | |\n| **DETAILS OF WRITE-INS** | | | | | | | | | | | | | |\n| 0801 | | | | | | | | | | | | | | |\n| 0802 | | | | | | | | | | | | | | |\n| 0803 | | | | | | | | | | | | | | |\n| 0808 | Summary of remaining write-ins for Line 6 from overflow page | | | | | | | | | | | | | |\n| 0899 | TOTALS (Lines 0801 thru 0803 plus 0808) (Line 6 above) | | | | | | | | | | | | | |\n| 1301 | | | | | | | | | | | | | | |\n| 1302 | | | | | | | | | | | | | | |\n| 1303 | | | | | | | | | | | | | | |\n| 1308 | Summary of remaining write-ins for Line 13 from overflow page | | | | | | | | | | | | | |\n| 1399 | TOTALS (Lines 1301 thru 1303 plus 1308) (Line 13 above) | | | | | | | | | | | | | |\n\n(a) Indicate if blocks of business in run-off that comprise less than 5% of premiums and less than 5% of reserve and loans liability are aggregated with material blocks of business and which columns are affected.\n\n## EXHIBIT OF NET INVESTMENT INCOME\n\n| Description | Collected During Year | Earned During Year |\n|------------------------------------------------------------------------------|-----------------------|--------------------|\n| 1. U.S. Government bonds | (a) | |\n| 1.1 Bonds exempt from U.S. tax | (a) | |\n| 1.2 Other bonds (unaffiliated) | (a) | |\n| 1.3 Bonds of affiliates | (a) | |\n| 2. Preferred stocks (unaffiliated) | (b) | |\n| 2.11 Preferred stocks of affiliates | (b) | |\n| 2.2 Common stocks (unaffiliated) | 41,732,935 | 41,732,935 |\n| 2.21 Common stocks of affiliates | | |\n| 3. Mortgage loans | (c) | |\n| 4. Real estate | (d) | |\n| 5. Contract loans | | |\n| 6. Cash, cash equivalents and short-term investments | (e) | |\n| 7. Derivative instruments | (f) | |\n| 8. Other invested assets | | |\n| 9. Aggregate write-ins for investment income | 0 | 0 |\n| 10. Total gross investment income | 41,732,935 | 41,732,935 |\n| 11. Investment expenses | (g) | |\n| 12. Investment taxes, licenses and fees, excluding federal income taxes | (g) | |\n| 13. Interest expense | (h) | |\n| 14. Depreciation on real estate and other invested assets | | |\n| 15. Aggregate write-ins for deductions from investment income | 0 | 0 |\n| 16. Total deductions (Lines 11 through 15) | 0 | 0 |\n| 17. Net investment income (Line 10 minus Line 16) | 41,732,935 | |\n\n### DETAILS OF WRITE-INS\n\n| Description | Collected During Year | Earned During Year |\n|------------------------------------------------------------------------------|-----------------------|--------------------|\n| 0901. | | |\n| 0902. | | |\n| 0903. | | |\n| 0998. Summary of remaining write-ins for Line 9 from overflow page | 0 | 0 |\n| 0999. Totals (Lines 0901 thru 0903 plus 0998) (Line 9, above) | 0 | 0 |\n\n(a) Includes $ _______ accrual of discount less $ _______ amortization of premium and less $ _______ paid for accrued interest on purchases.\n\n(b) Includes $ _______ accrual of discount less $ _______ amortization of premium and less $ _______ paid for accrued dividends on purchases.\n\n(c) Includes $ _______ accrual of discount less $ _______ amortization of premium and less $ _______ paid for accrued interest on purchases.\n\n(d) Includes $ _______ for company’s occupancy of its own buildings; and excludes $ _______ interest on encumbrances.\n\n(e) Includes $ _______ accrual of discount less $ _______ amortization of premium and less $ _______ paid for accrued interest on purchases.\n\n(f) Includes $ _______ accrual of discount less $ _______ amortization of premium.\n\n(g) Includes $ _______ investment expenses and $ _______ investment taxes, licenses and fees, excluding federal income taxes, attributable to segregated and Separate Accounts.\n\n(h) Includes $ _______ interest on surplus notes and $ _______ interest on capital notes.\n\n(i) Includes $ _______ depreciation on real estate and $ _______ depreciation on other invested assets.\n\n## EXHIBIT OF CAPITAL GAINS (LOSSES)\n\n| Description | 1 | 2 | 3 | 4 | 5 |\n|------------------------------------------------------------------------------|---|---|---|---|---|\n| Realized Gain (Loss) On Sales or Maturity | | | | | |\n| Other Realized Adjustments | | | | | |\n| Total Realized Capital Gain (Loss) (Columns 1 + 2) | | | | | |\n| Change in Unrealized Capital Gain (Loss) | | | | | |\n| Change in Unrealized Foreign Exchange Capital Gain (Loss) | | | | | |\n| 1. U.S. Government bonds | 0 | 0 | 0 | 0 | 0 |\n| 1.1 Bonds exempt from U.S. tax | 0 | 0 | 0 | 0 | 0 |\n| 1.2 Other bonds (unaffiliated) | 0 | 0 | 0 | 0 | 0 |\n| 1.3 Bonds of affiliates | 0 | 0 | 0 | 0 | 0 |\n| 2. Preferred stocks (unaffiliated) | 0 | 0 | 0 | 0 | 0 |\n| 2.11 Preferred stocks of affiliates | 0 | 0 | 0 | 0 | 0 |\n| 2.2 Common stocks (unaffiliated) | 32,930,048 | 0 | 32,930,048 | 40,012,390 | 0 |\n| 2.21 Common stocks of affiliates | 0 | 0 | 0 | 0 | 0 |\n| 3. Mortgage loans | 0 | 0 | 0 | 0 | 0 |\n| 4. Real estate | 0 | 0 | 0 | 0 | 0 |\n| 5. Contract loans | 0 | 0 | 0 | 0 | 0 |\n| 6. Cash, cash equivalents and short-term investments | 0 | 0 | 0 | 0 | 0 |\n| 7. Derivative instruments | 0 | 0 | 0 | 0 | 0 |\n| 8. Other invested assets | 0 | 0 | 0 | 0 | 0 |\n| 9. Aggregate write-ins for capital gains (losses) | 0 | 0 | 0 | 0 | 0 |\n| 10. Total capital gains (losses) | 32,930,048 | 0 | 32,930,048 | 40,012,390 | 0 |\n\n### DETAILS OF WRITE-INS\n\n| Description | 1 | 2 | 3 | 4 | 5 |\n|------------------------------------------------------------------------------|---|---|---|---|---|\n| 0901. | | | | | |\n| 0902. | | | | | |\n| 0903. | | | | | |\n| 0998. Summary of remaining write-ins for Line 9 from overflow page | 0 | 0 | 0 | 0 | 0 |\n| 0999. Totals (Lines 0901 thru 0903 plus 0998) (Line 9, above) | 0 | 0 | 0 | 0 | 0 |\n\nExhibit 1\n\nNONE\n\nExhibit 2\n\n## EXHIBIT 3 - AGGREGATE RESERVE FOR LIFE, ANNUITY AND ACCIDENT AND HEALTH CONTRACTS\n\n| Description of Valuation Basis | Total (a) | Ordinary | Group |\n|-------------------------------|-----------|----------|-------|\n| 0200001: 1994 MGB 6.00% 1996–1997 | 22,180,636 | 15,225,251 | 6,955,385 |\n| 0200002: 1994 MGB 6.00% 1998 | 49,876,111 | 40,773,733 | 9,102,358 |\n| 0200003: 1994 MGB 5.50% 1999 | 86,471,284 | 54,647,085 | 21,737,533 |\n| 0200004: 1994 MGB 5.75% 2000 | 92,575,188 | 84,875,471 | 7,699,717 |\n| 0200005: 1994 MGB 6.00% 2001–2002 | 88,554,641 | 69,271,451 | 19,283,190 |\n| 0200006: 1994 MGB 5.50% 2003 | 20,598,963 | 15,234,928 | 5,364,035 |\n| 0200007: 1994 MGB 5.00% 2004 | 28,707,739 | 22,107,366 | 6,600,373 |\n| 0200008: 1994 MGB 4.75% 2005–2007 | 63,814,129 | 48,786,332 | 15,027,797 |\n| 0200009: 1994 MGB 4.75% 2008 | 46,323,284 | 40,291,994 | 6,111,290 |\n| 0200010: 1994 MGB 5.25% 2009 | 69,359,436 | 63,897,401 | 5,462,035 |\n| 0200011: 1994 MGB 4.75% 2010 | 28,112,267 | 24,113,714 | 3,998,553 |\n| 0200012: 1994 MGB 4.50% 2011 | 26,001,953 | 22,060,818 | 3,941,135 |\n| 0200013: 1994 MGB 4.00% 2012 | 18,744,074 | 17,123,313 | 1,620,761 |\n| 0200014: 1994 MGB 3.75% 2013 | 16,193,454 | 15,567,211 | 626,243 |\n| 0200015: 1994 MGB 3.75% 2014 | 10,438,563 | 10,300,892 | 38,991 |\n| 0200016: 1994 MGB 3.75% 2015 | 8,997,328 | 8,453,888 | 544,040 |\n| 0200017: 1994 MGB 4.00% 2016 | 5,876,343 | 5,436,306 | 440,037 |\n| 0200018: 1994 MGB 3.75% 2017 | 4,059,289 | 3,423,576 | 635,713 |\n| 0200019: 1994 MGB 3.75% 2018 | 2,816,303 | 2,558,643 | 257,660 |\n| 0200020: 1994 MGB 3.75% 2019 | 1,072,550 | 984,446 | 88,104 |\n| 02999999: Annuities Totals | 690,771,091 | 578,874,017 | 112,897,074 |\n\n(a) Included in the above table are amounts of deposit-type contracts that originally contained a mortality risk. Amounts of deposit-type contracts that no longer contain a mortality risk in Column 2 are: Life Insurance $ 0 ; Annuities $ 0 ; Supplementary Contracts with Life Contingencies $ 0 ; Accident and Health Contracts $ 0 ; Miscellaneous Reserves $ 0 .\n\n## EXHIBIT 3 - INTERROGATORIES\n\n1.1 Has the reporting entity ever issued both participating and non-participating variable life insurance contracts? Yes [ ] No [ X ]\n\n2.1 Does the reporting entity at present issue both participating and non-participating variable life insurance contracts? Yes [ ] No [ X ]\n\n2.2 If not, state which kind is issued\n\n3.1 Is any surrender value promised in excess of the reserve as legally computed? Yes [ ] No [ X ] N/A [ ]\n\n3.2 If so, the amount of such excess must be included in surrender values in excess of reserves otherwise required and carried in this schedule. Has this been done? Yes [ ] No [ ] N/A [ X ]\n\nAttach a statement of methods employed in the valuation of variable life insurance contracts issued at, or subsequently subject to, an extra premium or in the valuation of contracts otherwise issued on lives classified as substandard for the plan of contract issued or on special class lives (including paid-up variable life insurance).\n\n## EXHIBIT 3A - CHANGES IN BASIS OF VALUATION DURING THE YEAR\n\n(Including supplementary contracts set up on a basis other than that used to determine benefits)\n\n| Description of Valuation Class | Valuation Basis | Increase in Actuarial Reserve Due to Change |\n|--------------------------------|-----------------|--------------------------------------------|\n| | Changed From | Changed To |\n| | | |\n\n99999999 - Totals (Page 6, Line 5, Analysis of Increase in Reserves)\n\nExhibit 4\n\n## EXHIBIT 5 - RECONCILIATION OF CASH AND INVESTED ASSETS\n\n### DEVELOPMENT OF INCREASE IN CASH\n\n| Description | Amount |\n|------------------------------------------------------------------------------|----------|\n| 1. Transfers to Separate Accounts on account of: | |\n| 1.1 Net premiums and considerations for annuities and supplementary contracts with life contingencies | 11,913,442 |\n| 1.2 Aggregate write-ins for other transfers to Separate Accounts | 0 |\n| 2. Deposits on deposit-type contract funds and other liabilities without life or disability contingencies | 41,732,835 |\n| 3. Investment income | |\n| 4. Consideration on disposal of short-term bonds net of purchases | |\n| 5. Consideration on disposal of investments (excluding short-term bonds) | 101,938,807 |\n| 6. Aggregate write-ins for other increases in funds from operations | 0 |\n| 7. Total (Lines 1 to 6) | 155,585,184 |\n| 8. Cost of investments acquired (excluding short-term bonds) | 56,222,941 |\n| 9. Transfers to Separate Accounts on account of contract benefits: | |\n| 9.1 Death benefits | |\n| 9.2 Matured endowments | |\n| 9.3 Annuity benefits | |\n| 9.4 Supplementary contract benefits with life contingencies | |\n| 9.5 Accident and health benefits | |\n| 9.6 Surrender benefits and withdrawals for life contracts | 86,860,730 |\n| 9.7 Policy loans (net) | |\n| 9.8 Transfers of reserves (net) | 3,243,122 |\n| 9.9 Aggregate write-ins for other transfers from Separate Accounts on account of contract benefits | 0 |\n| 10. Other transfers from Separate Accounts: | |\n| 10.1 General investment funds | |\n| 10.2 Aggregate write-ins for other transfers from Separate Accounts | 0 |\n| 11. Withdrawals on deposit-type contract funds and other liabilities without life or disability contingencies | 0 |\n| 12. Investment expenses (Exhibit 1, Line 25) | |\n| 12.1 Fees associated with investment management, administration and contract guarantees | 9,258,331 |\n| 13. Investment taxes, licenses and fees, excluding federal income taxes (Exhibit 2, Line 9) | |\n| 14. Total (Lines 8 to 13) | 155,585,184 |\n| 15. Funds from operations (Line 7 minus Line 14) | 0 |\n| 16. Surplus contributed or (withdrawn) during year | |\n| 17. Aggregate write-ins for other changes in funds | 0 |\n| 18. Total funds (includes $ net transfers from general account) (Lines 15 to 17) | 0 |\n| 19. Increase in payments for investments acquired, net of receivable for investments sold | |\n| 20. Increase in policy loans | |\n| 21. Aggregate write-ins for other reconciling items | 0 |\n| 22. Increase in cash (Line 18 to 21) | 0 |\n\n### RECONCILIATION BETWEEN YEARS\n\n| Description | Amount |\n|------------------------------------------------------------------------------|----------|\n| 23. Cash and invested assets, December 31st of prior year | 663,544,636 |\n| 24. Increase in cash (Line 22) | 0 |\n| 25. Cost of invested assets acquired | 56,222,941 |\n| 26. Adjusted cost of assets disposed of | 69,008,759 |\n| 27. Increase in policy loans | |\n| 28. Accrual of discount less amortization of premium | |\n| 29. Depreciation of real estate and other invested assets | |\n| 30. Increase in net invested assets | 40,012,350 |\n| 31. Aggregate write-ins for other reconciling items | 0 |\n| 32. Cash and invested assets, December 31st of current year | 680,771,210 |\n\n### DETAILS OF WRITE-INS\n\n| Line | Description | Amount |\n|------|------------------------------------------------------------------------------|----------|\n| 01.201 | | |\n| 01.202 | | |\n| 01.203 | | |\n| 01.298 | Summary of remaining write-ins for Line 1.2 from overflow page | 0 |\n| 01.299 | Totals (Lines 01.201 thru 01.203 plus 01.298) (Line 1.2 above) | 0 |\n| 0601. | | |\n| 0602. | | |\n| 0603. | | |\n| 0698. | Summary of remaining write-ins for Line 6 from overflow page | 0 |\n| 0699. | Totals (Lines 0601 thru 0603 plus 0698) (Line 6 above) | 0 |\n| 09.901 | | |\n| 09.902 | | |\n| 09.903 | | |\n| 09.998 | Summary of remaining write-ins for Line 9.9 from overflow page | 0 |\n| 09.999 | Totals (Lines 09.901 thru 09.903 plus 09.998) (Line 9.9 above) | 0 |\n| 10.201 | | |\n| 10.202 | | |\n| 10.203 | | |\n| 10.298 | Summary of remaining write-ins for Line 10.2 from overflow page | 0 |\n| 10.299 | Totals (Lines 10.201 thru 10.203 plus 10.298) (Line 10.2 above) | 0 |\n| 1701. | | |\n| 1702. | | |\n| 1703. | | |\n| 1798. | Summary of remaining write-ins for Line 17 from overflow page | 0 |\n| 1799. | Totals (Lines 1701 thru 1703 plus 1798) (Line 17 above) | 0 |\n| 2101. | | |\n| 2102. | | |\n| 2103. | | |\n| 2198. | Summary of remaining write-ins for Line 21 from overflow page | 0 |\n| 2199. | Totals (Lines 2101 thru 2103 plus 2198) (Line 21 above) | 0 |\n| 3101. | | |\n| 3102. | | |\n| 3103. | | |\n| 3198. | Summary of remaining write-ins for Line 31 from overflow page | 0 |\n| 3199. | Totals (Lines 3101 thru 3103 plus 3198) (Line 31 above) | 0 |\n\n| Description | Amount | Percent of Total |\n|----------------------------------------------------------------------------|------------|------------------|\n| 1. Aggregate reserve for life, annuity and accident and health contracts (Included in Exhibit 3): | | |\n| 1.1 Life insurance | | 0.0 |\n| 1.2 Annuities | 690,771,210| 100.0 |\n| 1.3 Supplementary contracts with life contingencies | | 0.0 |\n| 1.4 Accident and health | | 0.0 |\n| 1.5 Miscellaneous reserves | | 0.0 |\n| 1.6 Total | 690,771,210| 100.0 |\n| 2. Liability for deposit-type contracts (included in Exhibit 4): | | |\n| 2.1 Guaranteed interest contracts | | 0.0 |\n| 2.2 Annuities certain | | 0.0 |\n| 2.3 Supplemental contracts | | 0.0 |\n| 2.4 Dividend accumulations or refunds | | 0.0 |\n| 2.5 Premium and other deposit funds | | 0.0 |\n| 2.6 Total | 0 | 0.0 |\n| 3. Other liabilities (included in Page 3, Lines 4, 10, 13 & 14) | | 0.0 |\n| 4. Total liabilities associated with guarantees (Lines 1.6 + 2.6 + 3) | 690,771,210| 100.0 |\n| 5. Total liabilities not associated with guarantees | | 0.0 |\n| 6. Total Separate Accounts liabilities (Lines 4 + 5 = Page 3, Line 17) | 690,771,210| 100.0% |\n\n### Product Mix\n\n1.01 Identify the product types in the separate account, quantify the assets associated with those products, indicate if there are any guarantees associated with those products, quantify seed money and quantify other fees and expenses due to the general account. For the products (and related assets) that are not registered with the SEC, identify whether the products are considered private placement variable annuity products or private placement life insurance.\n\n**Note:** A distinct disaggregated product identifier shall be used for each product and shall be used consistently throughout the interrogatory. Disaggregation of reporting shall be such that each product filing or policy form is separately identified. For example, if a company has 5 different separate group annuities, each annuity shall be separately reported. (Companies may eliminate proprietary information however such elimination will require the use of unique reporting identifiers.)\n\nAdditional Required Surplus Amounts is defined as additional or permanent surplus that is required to be retained in the separate account in accordance with state law or regulation. These amounts should not include reinvested separate account investment proceeds that have not been allocated to separate account contract holders.\n\n| 1 | Separate Account Assets | 4 | Guarantees Associated with the Product Yes/No | 5 | Fees and Expenses Due to the General Account | 6 | Additional Required Surplus Amounts | 7 | Not Registered with SEC |\n|---|-------------------------|---|---------------------------------------------|---|---------------------------------------------|---|-----------------------------------|---|------------------------|\n| | Product Identifier | | | | | | | | |\n| 1.01A0001 | Pension Risk Transfer Group Annuities | | | | | | | | |\n| 1.01A9999 | Total Pension Risk Transfer Group Annuities | 0 | XXX | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1.01B0001 | All Other Group Annuities Variable Annuities | 576,874,137 | YES | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1.01C0001 | Registered Index Linked Annuities Individual Annuities | 113,897,073 | YES | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1.01D0001 | All Other Individual Annuities Variable Annuities | 113,897,073 | YES | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1.01E0001 | Life Insurance | | | | | | | | |\n| 1.01F9999 | Total Life Insurance | 0 | XXX | 0 | 0 | 0 | 0 | 0 | 0 |\n| 1.01F9999 | Totals | 680,771,210 | XXX | 0 | 0 | 0 | 0 | 0 | 0 |\n\n1.02 Did the reporting entity remit seed money, other fees and expenses or additional required surplus amounts to the general account during the current year? Yes [ ] No [ X ]\n\n1.03 If yes, provide information on the total gross amount of seed money, other fees and expenses or additional required surplus amounts remitted to the general account during the current year (these amounts should not be reflected in the seed money totals in 1.01):\n\n- 1.031 Seed Money $ ...........................................\n- 1.032 Other Fees and Expenses $ ...........................................\n- 1.033 Additional Required Surplus Amounts $ ...........................................\n\n1.04 Did the reporting entity receive seed money from the general account in the current year? Yes [ ] No [ X ]\n\n1.05 If yes, provide information on the total gross amount of seed money received in the current year; (If amounts were both received and remitted in the current year, include the gross amounts in both 1.051 and 1.051.)\n\n- 1.051 Seed Money Received $ ...........................................\n\n1.06 Does the reporting entity consider any of the seed money reflected in separate accounts to be insulated from the general account? Yes [ ] No [ ] N/A [ X ]\n\n1.07 If yes, provide information on the amount of seed money the reporting entity considers insulated from the general account:\n\n- 1.071 Insulated Seed Money $ ...........................................\n\n1.08 Does the reporting entity have a policy for repatriating seed money or remitting fees and expenses due and additional required surplus amounts to the general account:\n\n| 1.081 Seed Money | Yes [ ] No [ X ] |\n|------------------|-----------------|\n| 1.082 Other Fees and Expenses | Yes [ ] No [ X ] |\n| 1.083 Additional Required Surplus Amounts | Yes [ ] No [ X ] |\n\n1.09 Provide detail on the time duration for which seed money, other fees and expenses due to the general account and additional required surplus amounts have been held in the separate account:\n\n| 1 | 2 | 3 |\n|---|---|---|\n| Seed Money | Fees and Expenses Due to the General Account | Additional Required Surplus Amounts |\n| 1.091 Under 1 Year | | |\n| 1.092 1 Year - 3 Years | | |\n| 1.093 Over 3 Years - 5 Years | | |\n| 1.094 Over 5 Years | | |\n| 1.095 Total | 0 | 0 |\n\n1.10 For seed money, other fees and expenses, and additional required surplus amounts held in the separate account, does the reporting entity invest these funds in accordance with investment directives of the general account:\n\n| 1.101 Seed Money | Yes [ ] No [ X ] N/A [ ] |\n|------------------|-------------------------|\n| 1.102 Other Fees and Expenses | Yes [ ] No [ ] N/A [ ] |\n| 1.103 Additional Required Surplus Amounts | Yes [ ] No [ X ] N/A [ ] |\n\n1.11 If no, does the reporting entity have stated policy and procedure for the investment of seed money, other fees and expenses, and additional required surplus amounts that are retained with the separate account?\n\n| 1.111 Seed Money | Yes [ ] No [ ] N/A [ X ] |\n|------------------|-------------------------|\n| 1.112 Other Fees and Expenses | Yes [ ] No [ ] N/A [ X ] |\n| 1.113 Additional Required Surplus Amounts | Yes [ ] No [ ] N/A [ X ] |\n\nSeparate Account Products with General Account Guarantees\n\n2.1 Does the reporting entity have products with guarantees provided by the general account? Yes [ X ] No [ ]\n\n2.2 Has the separate account collected amounts from the general account within the past five years related to separate account guarantees? Yes [ X ] No [ ]\n\n2.3 If yes, provide detail on these guarantees paid by the general account:\n\n| 1 | 2 |\n|---|---|\n| Year | Amount |\n| 2.301 As of December 31, 2021 | $ 226,381 |\n| 2.302 As of December 31, 2020 | $ 109,397 |\n| 2.303 As of December 31, 2019 | $ 365,933 |\n| 2.304 As of December 31, 2018 | $ 47,181 |\n| 2.305 As of December 31, 2017 | $ 69,255 |\n\n2.4 To compensate the general account for the risk taken, for any separate account products with general account guarantees, does the separate account remit risk charges to the general account related to separate account guarantees? Yes [ X ] No [ ]\n\n2.5 If yes, identify the separate account products with risk charges that are remitted to the general account and whether the risk charge for that product is reviewed and opined upon:\n\n| 1 | 2 | 3 |\n|---|---|---|\n| Product Identifier with Risk Charges | Risk Charge Reviewed and Opined Upon | Name and Title of Individual who Provided Opinion on Risk Charges |\n| 2.5A00001 Pension Risk Transfer Group Annuities | | |\n| 2.5B00001 All Other Group Annuities Variable Annuities | | |\n| 2.5C00001 Registered Index Linked Annuities Individual Annuities | | |\n| 2.5D00001 All Other Individual Annuities Variable Annuities | | |\n| 2.5E00001 Life Insurance | | |\n\n2.6 Provide detail on the risk charges paid to the general account related to separate account guarantees for the past five years.\n\n| 1 Year | 2 Amount |\n|-------------------------|----------|\n| 2.601 As of December 31, 2021 | $ 268,779 |\n| 2.602 As of December 31, 2020 | $ 286,442 |\n| 2.603 As of December 31, 2019 | $ 332,572 |\n| 2.604 As of December 31, 2018 | $ 347,967 |\n| 2.605 As of December 31, 2017 | $ 345,651 |\n\nInvestment Directive of Separate Account Activity\n\n3.1 Does the reporting entity have products classified within the separate account for which the investment directive is not determined by the contract holder? (Situations in which the investments directive mirrors the general account would not be considered determined by the contract holder; however, having the contract holder select an investment direction from multiple options would meet this criteria.) Yes [ ] No [ X ]\n\n3.2 If yes, if these investments would have been included in the general account, would the reporting entity have exceeded the investment limitations imposed on the general account? Yes [ ] No [ ] N/A [ X ]\n\n3.3 Provide detail on the separate account investment portfolio and state investment limitations. (This includes the combined separate account and general investments, excluding separate account assets with investment direction determined by the contract holder):\n\n| 1 Investment Type | 2 State Investment Limitation | 3 Combined Investment (Separate and General Account) |\n|-------------------|-------------------------------|-----------------------------------------------------|\n\nAllocation of Investment Proceeds of Separate Account Activity\n\n4.1 Does the reporting entity have separate account assets in which less than 100% of investment proceeds (net of contract fees and assessments) are attributed to a contract holder? (This should identify any situations where there is a ceiling on investment performance results.) Yes [ ] No [ X ]\n\n4.2 If yes, provide detail on the net investment proceeds that were attributed to the contract holder, transferred to the general account and reinvested within the separate account:\n\n| 1 Product Identifier | 2 Net Investment Proceeds | 3 Attributed to Contract Holder | 4 Transferred to General Account | 5 Reinvested Within the Separate Account |\n|----------------------|---------------------------|---------------------------------|----------------------------------|----------------------------------------|\n| 4.2A00001 Pension Risk Transfer Group Annuities | 0 | 0 | 0 | 0 |\n| 4.2A99999 Total Pension Risk Transfer Group Annuities | 0 | 0 | 0 | 0 |\n| 4.2B00001 All Other Group Annuities | 0 | 0 | 0 | 0 |\n| 4.2B99999 Total All Other Group Annuities | 0 | 0 | 0 | 0 |\n| 4.2C00001 Registered Index Linked Annuities Individual Annuities | 0 | 0 | 0 | 0 |\n| 4.2C99999 Total Registered Index Linked Annuities Individual Annuities | 0 | 0 | 0 | 0 |\n| 4.2D00001 All Other Individual Annuities | 0 | 0 | 0 | 0 |\n| 4.2D99999 Total All Other Individual Annuities | 0 | 0 | 0 | 0 |\n| 4.2E00001 Life Insurance | 0 | 0 | 0 | 0 |\n| 4.2E99999 Total Life Insurance | 0 | 0 | 0 | 0 |\n| Totals | 0 | 0 | 0 | 0 |\n\n4.3 For items reinvested within the Separate Account, does the reporting entity invest these assets in accordance with investment directives of the general account? Yes [ ] No [ ] N/A [ X ]\n\n4.4 If no, does the reporting entity have a stated policy and procedure for the reinvestment of investment proceeds within the separate account? Yes [ ] No [ ] N/A [ X ]\n\n4.5 Did the reinvestment of investment proceeds within the separate account result with the company having a combined investment portfolio that exceeded the state investment limitations imposed on the general account? Yes [ ] No [ ] N/A [ X ]\n\nMeasurement of Separate Account Assets\n\n5.1 Does the reporting entity report all separate account assets at fair value? ................................................................. Yes [ X ] No [ ]\n\n5.2 For items not reported at fair value, does the reporting entity report separate account assets at amortized cost, and/or under different measurement methods?\n\n5.21 Amortized Cost ........................................................................................................................................................................ Yes [ ] No [ X ]\n5.22 Other Measurement Methods .................................................................................................................................................. Yes [ ] No [ X ]\n\n5.3 If other measurement methods are used, provide explanation on these measurement methods.\n\n5.4 Identify the assets measured at fair value, amortized cost or another measurement method and the percentage of separate account assets measured under each measurement method:\n\n| Description | 1 Amount | 2 Percentage |\n|------------------------------|----------|--------------|\n| 5.41 Fair Value | $690,771,210 | 100.0 % |\n| 5.42 Amortized Cost | $ | 0.0 % |\n| 5.43 Other Measurement Methods| $ | 0.0 % |\n\n5.5 For the assets not measured at fair value, provide a comparison of the reported value to current fair value and identify the unrealized gain or loss that would have been recorded if the assets had been reported at fair value:\n\n| 1 Assets Held at Amortized Cost | 2 Fair Value | 3 Unrecorded Unrealized Gain/Loss |\n|---------------------------------|--------------|----------------------------------|\n| 5.51 $ | $ | $ |\n\n| 1 Assets Held at Other Measurement Method | 2 Fair Value | 3 Unrecorded Unrealized Gain/Loss |\n|-------------------------------------------|--------------|----------------------------------|\n| 5.52 $ | $ | $ |\n\nSecurities Lending Transactions Within Separate Accounts\n\n6.1 Does the reporting entity engage in securities lending transactions with separate account assets? .................................................. Yes [ ] No [ X ]\n\n6.2 If yes, does the reporting entity have written policies and procedures for such transactions? .................................................. Yes [ ] No [ ] N/A [ X ]\n\n6.3 Does the reporting entity obtain approval, or otherwise provide notification to contract holders, regarding securities lending transactions that occur with separate account assets? .................................................................................................................. Yes [ ] No [ ] N/A [ X ]\n\n6.4 Are all securities lending transactions reported on balance sheet? .......................................................................................... Yes [ ] No [ ] N/A [ X ]\n\n6.5 Provide a description of the reporting entity's securities lending transaction program, specifically identifying any variations from the securities lending transaction program administered by the general account.\n\n6.6 Provide detail on the current status of separate account transactions by separate account product:\n\n6.61 Amount of any loaned securities within the separate account and the percentage of separate account assets lent\n\n6.611 Amount ........................................................................................................................................................................... $_____________________\n6.612 Percentage ............................................................................................................................................................... %\n\n6.62 Identify whether securities lent are reported at book value or market value\n\n6.621 Book Value .............................................................................................................................................................. $_____________________\n6.622 Market Value .......................................................................................................................................................... $_____________________\n\n6.63 Detail on collateral received:\n\n6.631 Aggregate Amount Collateral Received\n\n6.6311 Open ........................................................................................................................................................................ $_____________________\n6.6312 30 Days or Less .................................................................................................................................................... $_____________________\n6.6313 31 to 60 Days ..................................................................................................................................................... $_____________________\n6.6314 61 to 90 Days ..................................................................................................................................................... $_____________________\n6.6315 Greater than 90 Days ........................................................................................................................................ $_____________________\n6.6316 Total Collateral Received .................................................................................................................................... $_____________________\n\n6.632 The aggregate fair value of all securities acquired from the sale, trade or use of the accepted collateral (reinvested collateral) ................................................................................................................................. $_____________________\n\n6.633 Narrative discussion about sources and uses of collateral: ...........................................................................................................\n\n6.634 Collateral for transactions that extend beyond one year from the reporting date ........................................................................ $_____________________\n\n6.7 For the reporting entity's security lending program state the amount of the following as December 31 of the current year:\n\n6.71 Total fair value of reinvested collateral assets reported on Schedule DL, Parts 1 and 2 (Sum of Schedule DL, Parts 1 and 2, Column 5) ................................................................................................................................. $_____________________\n6.72 Total amortized/carried value of reinvested collateral assets reported on Schedule DL, Parts 1 and 2 (Sum of Schedule DL, Parts 1 and 2, Column 6) ................................................................................................................................. $_____________________\n6.73 Total payable for securities lending reported on the liability page (Page 3, Line 14, Column 3) .................................................. $_____________________\n\nANNUAL STATEMENT FOR THE YEAR 2021 OF THE SEPARATE ACCOUNTS OF THE ANNUITY INVESTORS LIFE INSURANCE COMPANY\n\nGENERAL INTERROGATORIES\n\nFHLB Funding Agreements\n\n7.1 Does the reporting entity report Federal Home Loan Bank (FHLB) funding agreements within the separate account? Yes [ ] No [ X ]\n\n7.2 Provide detail on the elements that support the classification of FHLB funding agreements within the separate account\n\n7.3 Provide detail regarding the FHLB funding agreements classified within the separate account:\n\n| 1 Amount of FHLB Stock Purchased or Owned | 2 Amount of Collateral Pledged to the FHLB | 3 Total Borrowing or Funding Capacity Currently Available | 4 Total Reserves Related to FHLB Agreements |\n|------------------------------------------|-------------------------------------------|-------------------------------------------------|------------------------------------------|\n| $ | $ | $ | $ |\n\n7.4 For funding agreements within the separate account, provide a general description on the nature of the agreement, type of funding (lines of credit, borrowed money, etc) and intended use of funding.\n\nReporting Differences Between GAAP and SAP Financial Statements (This disclosure is applicable to all reporting entities regardless if they file GAAP financial statements)\n\n8.1 Does the reporting entity file GAAP financial statements? Yes [ X ] No [ ]\n\n8.2 In accordance with the different separate account reporting requirements between GAAP (SOP 03-1) and statutory accounting, does the reporting entity have products that are classified within the separate account that were, or would have been if GAAP financial statements had been completed, required to be reported within the general account under GAAP financials? Pursuant to SOP 03-1, all of the following conditions must be met to receive separate account reporting classification under GAAP: Yes [ ] No [ X ] N/A [ ]\n\na. Legal Recognition - The separate account is legally recognized. That is, the separate account is established, approved, and regulated under special rules such as state insurance laws, federal securities laws, or similar foreign laws.\n\nb. Legally Insulated - The separate account assets supporting the contract liabilities are legally insulated from the general account liabilities of the insurance enterprise (that is, the contract holder is not subject to insurer default risk to the extent of the assets held in the separate account).\n\nc. Investment Directive - The insurer must, as a result of contractual, statutory, or regulatory requirements, invest the contract holder’s funds within the separate account as directed by the contract holder in designated investment alternatives or in accordance with specific investment objectives or policies.\n\nd. Investment Performance - All investment performance, net of contract fees and assessments, must as a result of contractual, statutory, or regulatory requirements be passed through to the individual contract holder. Contracts may specify conditions under which there may be a minimum guarantee, but not a ceiling, as a ceiling would prohibit all investment performance from being passed through to the contract holder.\n\n8.3 Identify all separate account products and identify whether each product was classified within a separate account for GAAP reporting purposes. (For non-GAAP filers, this disclosure should reflect whether the GAAP classification would have been the same if GAAP financials had been completed.) For products that were (or would have been) reported differently, identify which SOP 03-1 condition prevented separate account GAAP classification for that particular product.\n\n| 1 Product Identifier | 2 Same as GAAP / Condition that Requires GAAP General Account Reporting |\n|----------------------|------------------------------------------------------------------------|\n| Variable Annuities | Same as GAAP |\n\nInterest Maintenance Reserve\n\nNONE\n\nInterest Maintenance Reserve - Amortization\n\nNONE\n\nAsset Valuation Reserve - Default Component\n\nNONE\n\nAsset Valuation Reserve - Equity Component\n\nNONE\n\nAsset Valuation Reserve - Replications (Synthetic) Assets\n\nNONE\n\nOverflow Page for Write-ins\n\nNONE\n\nSchedule A - Verification - Real Estate\n\nNONE\n\nSchedule B - Verification - Mortgage Loans\n\n### SCHEDULE BA - VERIFICATION BETWEEN YEARS\n\n**Other Long-Term Invested Assets**\n\n1. Book/adjusted carrying value, December 31 of prior year ..................................................................\n\n2. Cost of acquired:\n 2.1 Actual cost at time of acquisition (Part 2, Column 8) ...............................................................\n 2.2 Additional investment made after acquisition (Part 2, Column 9) ...............................................\n\n3. Capitalized deferred interest and other:\n 3.1 Totals, Part 1, Column 16 ...........................................................................................................\n 3.2 Totals, Part 3, Column 12 ...........................................................................................................\n\n4. Accrual of discount ..........................................................................................................................\n\n5. Unrealized valuation increase (decrease):\n 5.1 Totals, Part 1, Column 13 ...........................................................................................................\n 5.2 Totals, Part 3, Column 9 ...........................................................................................................\n\n6. Total gain (loss) on disposals, Part 3, Column 19 ............................................................................\n\n7. Deduct amounts received on disposals, Part 3, Column 16 .............................................................\n\n8. Deduct amortization of premium and depreciation ...........................................................................\n\n9. Total foreign exchange change in book/adjusted carrying value:\n 9.1 Totals, Part 1, Column 17 ...........................................................................................................\n 9.2 Totals, Part 3, Column 14 ...........................................................................................................\n\n10. Deduct current year's other than temporary impairment recognized:\n 10.1 Totals, Part 1, Column 15 ........................................................................................................\n 10.2 Totals, Part 3, Column 11 .........................................................................................................\n\n11. Book/adjusted carrying value at end of current period (Lines 1+2+3+4+5+6-7-8+9-10) ......................\n\n12. Deduct total nonadmitted amounts ................................................................................................\n\n13. Statement value at end of current period (Line 11 minus Line 12) ...................................................\n\n---\n\n### SCHEDULE D - VERIFICATION BETWEEN YEARS\n\n**Bonds and Stocks**\n\n1. Book/adjusted carrying value, December 31 of prior year ................................................................. 663,544,638\n\n2. Cost of bonds and stocks acquired, Part 3, Column 7 .................................................................. 56,222,941\n\n3. Accrual of discount ......................................................................................................................... 0\n\n4. Unrealized valuation increase (decrease):\n 4.1. Part 1, Column 12 .....................................................................................................................\n 4.2. Part 2, Section 1, Column 15 ....................................................................................................\n 4.3. Part 2, Section 2, Column 13 ....................................................................................................\n 4.4. Part 4, Column 11 .................................................................................................................... (26,736,501) 40,012,390\n\n5. Total gain (loss) on disposals, Part 4, Column 19 ........................................................................... 32,930,048\n\n6. Deduction consideration for bonds and stocks disposed of, Part 4, Column 7 .............................. 101,938,807\n\n7. Deduct amortization of premium ..................................................................................................... 0\n\n8. Total foreign exchange change in book/adjusted carrying value:\n 8.1. Part 1, Column 15 .....................................................................................................................\n 8.2. Part 2, Section 1, Column 19 ....................................................................................................\n 8.3. Part 2, Section 2, Column 16 ....................................................................................................\n 8.4. Part 4, Column 15 .................................................................................................................... 0 0 0\n\n9. Deduct current year's other than temporary impairment recognized:\n 9.1. Part 1, Column 14 .....................................................................................................................\n 9.2. Part 2, Section 1, Column 17 ....................................................................................................\n 9.3. Part 2, Section 2, Column 14 ....................................................................................................\n 9.4. Part 4, Column 13 .................................................................................................................... 0 0 0\n\n10. Total investment income recognized as a result of prepayment penalties and/or acceleration fees, Note 5Q, Line 2 ...........................................................................................................................................\n\n11. Book/adjusted carrying value at end of current period (Lines 1+2+3+4+5-6-7+8-9+10) .................. 690,771,210\n\n12. Deduct total nonadmitted amounts ................................................................................................\n\n13. Statement value at end of current period (Line 11 minus Line 12) .................................................. 690,771,210\n\n| Description | 1 Book/Adjusted Carrying Value | 2 Fair Value | 3 Actual Cost | 4 Par Value of Bonds |\n|----------------------------------------------------------------------------|-------------------------------|-------------|--------------|----------------------|\n| **BONDS** | | | | |\n| Governments (Including all obligations guaranteed by governments) | | | | |\n| 1. United States | | | | |\n| 2. Canada | | | | |\n| 3. Other Countries | | | | |\n| 4. Totals | 0 | 0 | 0 | 0 |\n| U.S. States, Territories and Possessions (Direct and guaranteed) | | | | |\n| 5. Totals | | | | |\n| U.S. Political Subdivisions of States, Territories and Possessions (Direct and guaranteed) | | | | |\n| 6. Totals | | | | |\n| U.S. Special Revenue and Special Assessment Obligations and all Non-Guaranteed Obligations of Agencies and Authorities of Governments and their Political Subdivisions | | | | |\n| 7. Totals | | | | |\n| Industrial and Miscellaneous, SVO Identified Funds, Unaffiliated Bank Loans and Hybrid Securities (unaffiliated) | | | | |\n| 8. United States | | | | |\n| 9. Canada | | | | |\n| 10. Other Countries | | | | |\n| 11. Totals | 0 | 0 | 0 | 0 |\n| Parent, Subsidiaries and Affiliates | | | | |\n| 12. Totals | 0 | 0 | 0 | 0 |\n| 13. Total Bonds | 0 | 0 | 0 | 0 |\n| **PREFERRED STOCKS** | | | | |\n| Industrial and Miscellaneous (unaffiliated) | | | | |\n| 14. United States | | | | |\n| 15. Canada | | | | |\n| 16. Other Countries | | | | |\n| 17. Totals | 0 | 0 | 0 | 0 |\n| Parent, Subsidiaries and Affiliates | | | | |\n| 18. Totals | 0 | 0 | 0 | 0 |\n| 19. Total Preferred Stocks | 0 | 0 | 0 | 0 |\n| **COMMON STOCKS** | | | | |\n| Industrial and Miscellaneous (unaffiliated) | | | | |\n| 20. United States | 690,771,210 | 690,771,210 | 500,806,830 | |\n| 21. Canada | | | | |\n| 22. Other Countries | | | | |\n| 23. Totals | 690,771,210 | 690,771,210 | 500,806,830 | |\n| Parent, Subsidiaries and Affiliates | | | | |\n| 24. Totals | 0 | 0 | 0 | 0 |\n| 25. Total Common Stocks | 690,771,210 | 690,771,210 | 500,806,830 | |\n| 26. Total Stocks | 690,771,210 | 690,771,210 | 500,806,830 | |\n| 27. Total Bonds and Stocks | 690,771,210 | 690,771,210 | 500,806,830 | |\n\nSchedule DA - Verification - Short-Term Investments\n\nNONE\n\nSchedule DB - Part A - Verification - Options, Caps, Floors, Collars, Swaps and Forwards\n\nNONE\n\nSchedule DB - Part B - Verification - Futures Contracts\n\nNONE\n\nSchedule DB - Part C - Section 1 - Replication (Synthetic Asset) Transactions (RSATs) Open\n\nNONE\n\nSchedule DB-Part C-Section 2-Reconciliation of Replication (Synthetic Asset) Transactions Open\n\nNONE\n\nSchedule DB - Verification - Book/Adjusted Carrying Value, Fair Value and Potential Exposure of Derivatives\n\nNONE\n\nSchedule E - Part 2 - Verification - Cash Equivalents\n\nNONE\n\nSchedule A - Part 1 - Real Estate Owned\n\nNONE\n\nSchedule A - Part 2 - Real Estate Acquired and Additions Made\n\nNONE\n\nSchedule A - Part 3 - Real Estate Disposed\n\nNONE\n\nSchedule B - Part 1 - Mortgage Loans Owned\n\nNONE\n\nSchedule B - Part 2 - Mortgage Loans Acquired and Additions Made\n\nNONE\n\nSchedule B - Part 3 - Mortgage Loans Disposed, Transferred or Repaid\n\nNONE\n\nSchedule BA - Part 1 - Other Long-Term Invested Assets Owned\n\nSchedule BA - Part 2 - Other Long-Term Invested Assets Acquired and Additions Made\n\nNONE\n\nSchedule BA - Part 3 - Other Long-Term Invested Assets Disposed, Transferred or Repaid\n\nNONE\n\nSchedule D - Part 1 - Long Term Bonds Owned\n\nNONE\n\nSchedule D - Part 2 - Section 1 - Preferred Stocks Owned\n\n| CUSIP Identification | Description | Code | Foreign | Number of Shares | Book/Adjusted Carrying Value | Rate Per Share Used to Obtain Fair Value | Fair Value | Actual Cost | Declared but Unpaid | Amount Received During Year | Nonadmitted Declared But Unpaid | Unrealized Valuation Increase/(Decrease) | Current Year's Other-Than-Temporary Impairment Recognized | Total Change in Book/Adjusted Carrying Value (13 - 14) | Total Foreign Exchange Gain in Book/Adjusted Carrying Value | Date Acquired | NAIC Designation and SVO Administrative Symbol |\n|----------------------|-----------------------------------------------------------------------------|------|---------|------------------|-------------------------------|------------------------------------------|------------|--------------|---------------------|---------------------------------|----------------------------------------|-------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------|-------------------------------------------------|-----------------|-------------------------------------------------|\n| 470121-71-7 | Janus Henderson Series Enterprise Portfolio-Service Shares | | | 93,815,000 | 8,676,993 | 92.48 | 8,676,993 | 6,237,021 | 725,527 | 475,518 | | | | | | | |\n| 470121-86-5 | Janus Henderson Series Forty Portfolio-Institutional Shares | | | 423,884,000 | 26,113,113 | 61.750 | 26,113,113 | 16,729,445 | 2,761,028 | 2,071,459 | | | | | | | |\n| 470121-30-3 | Janus Henderson Series Global Research Portfolio-Institutional Shares | | | 258,796,000 | 18,446,975 | 71.280 | 18,446,975 | 9,612,498 | 889,677 | 1,023,399 | | | | | | | |\n| 470121-66-2 | Janus Henderson Series Global Research Portfolio-Service Shares | | | 2,709,000 | 187,735 | 69.310 | 187,735 | 96,122 | 9,015 | 19,245 | | | | | | | |\n| 470121-70-9 | Janus Henderson Series Overseas Portfolio-Institutional Shares | | | 253,134,000 | 10,861,989 | 42.910 | 10,861,989 | 7,778,010 | 121,256 | 1,167,068 | | | | | | | |\n| 470121-66-7 | Janus Henderson Series Overseas Portfolio-Service Shares | | | 381,119,000 | 15,633,512 | 41.620 | 15,633,512 | 11,086,419 | 156,563 | 1,657,516 | | | | | | | |\n| 470121-10-5 | Janus Henderson Series Research Portfolio-Institutional Shares | | | 279,836,000 | 15,757,584 | 56.310 | 15,757,584 | 9,705,284 | 729,791 | 1,925,859 | | | | | | | |\n| 470121-67-5 | Janus Henderson Series Research Portfolio-Service Shares | | | 99,861,000 | 5,426,429 | 54.340 | 5,426,429 | 3,655,605 | 251,149 | 641,969 | | | | | | | |\n| 61691F-79-7 | Morgan Stanley VIF Core Plus Fixed Income Portfolio-Class I | | | 561,112,000 | 5,874,846 | 10.470 | 5,874,846 | 6,085,793 | 594,664 | (610,027) | | | | | | | |\n| 61691F-86-7 | Morgan Stanley VIF Discovery Portfolio-Class I | | | 423,858,000 | 7,222,549 | 17.040 | 7,222,549 | 7,492,764 | 2,859,955 | (3,786,037) | | | | | | | |\n| 61691F-82-1 | Morgan Stanley VIF U.S. Real Estate Portfolio-Class I | | | 463,110,000 | 10,866,202 | 23.470 | 10,866,202 | 8,431,398 | 189,076 | 2,861,115 | | | | | | | |\n| 841222-86-6 | Neuberger Berman AIT U-I-Cap Growth Portfolio-Administrative | | | 12,033,000 | 433,429 | 36.620 | 433,429 | 305,606 | 49,338 | (1,660) | | | | | | | |\n| 841222-86-3 | Neuberger Berman AIT Sustainable Equity Portfolio-Administrative | | | 78,436,000 | 2,911,553 | 37.120 | 2,911,553 | 2,092,742 | 56,812 | 481,784 | | | | | | | |\n| 86339A-96-4 | PHM20 VIT High Yield Portfolio-Administrative Class | | | 512,847,000 | 4,070,420 | 7.940 | 4,070,420 | 3,939,650 | 173,738 | (33,467) | | | | | | | |\n| 86339A-81-9 | PHM20 VIT Real Return Portfolio-Administrative Class | | | 559,069,000 | 7,821,371 | 13.990 | 7,821,371 | 6,969,334 | 373,230 | 39,638 | | | | | | | |\n| 86339A-85-5 | PHM20 VIT Total Return Portfolio-Administrative | | | 1,662,438,000 | 17,887,637 | 10.760 | 17,887,637 | 18,288,513 | 1,062,460 | (1,277,201) | | | | | | | |\n| 867432-71-4 | Timothy Plan Series Variable Variable Portfolio-Series Variable | | | 45,033,000 | 558,035 | 12.400 | 558,035 | 483,529 | 7,578 | 32,981 | | | | | | | |\n| 867432-73-0 | Timothy Plan Series Variable Variable Portfolio-Series Variable | | | 47,270,000 | 602,330 | 12.585 | 602,330 | 495,076 | 10,705 | 50,383 | | | | | | | |\n| 97200F-86-8 | Vilshire Global Allocation Fund | | | 122,686,000 | 2,828,897 | 23.040 | 2,828,897 | 2,373,382 | 184,030 | 109,075 | | | | | | | |\n| 949999999 | Subtotal - Mutual Funds | | | | | | | | | | | | | | | | |\n| 977999999 | Total Common Stocks | | | | | | | | | | | | | | | | |\n| 969999999 | Total Preferred and Common Stocks | | | | | | | | | | | | | | | | |\n\n1. Line Book/Adjusted Carrying Value by NAIC Designation Category Footnote:\n\n| Number | Description |\n|--------|-------------|\n| 1A | $ |\n| 1B | $ |\n| 1C | $ |\n| 1D | $ |\n| 1E | $ |\n| 1F | $ |\n| 2A | $ |\n| 2B | $ |\n| 2C | $ |\n| 3 | $ |\n| 4 | $ |\n| 5 | $ |\n| 6 | $ |\n| 7 | $ |\n| 8 | $ |\n| 9 | $ |\n| 10 | $ |\n| 11 | $ |\n| 12 | $ |\n| 13 | $ |\n| 14 | $ |\n| 15 | $ |\n| 16 | $ |\n| 17 | $ |\n| 18 | $ |\n\n| 1 CUSIP Identification | 2 Description | 3 Foreign | 4 Date Acquired | 5 Name of Vendor | 6 Number of Shares of Stock | 7 Actual Cost | 8 Par Value | 9 Paid for Accrued Interest and Dividends |\n|------------------------|---------------|-----------|-----------------|-----------------|-----------------------------|--------------|------------|----------------------------------------|\n| 008892-41-6 | Invesco V.I. Main Street Bond Fund-Series I | 10/28/2021 | Invesco Variable Insurance Funds | 12,789,000 | 424,230 | | | |\n| 008892-46-1 | Invesco V.I. Main Street Bond Cap Fund-Series II Share | 10/28/2021 | Invesco Variable Insurance Funds | 19,400,000 | 226,882 | | | |\n| 008892-46-5 | Invesco V.I. Main Street Small Cap Fund - Series II | 10/28/2021 | Invesco Variable Insurance Funds | 14,065,000 | 434,183 | | | |\n| 000031-00-7 | Invesco V.I. Real Cap Equity Fund-Series I Share | 12/31/2021 | Invesco Variable Insurance Funds | 27,310,000 | 640,499 | | | |\n| 000031-00-8 | Invesco V.I. Real Cap Equity Fund-Series II Share | 12/31/2021 | Invesco Variable Insurance Funds | 21,400,000 | 519,127 | | | |\n| 008892-57-2 | Janus Henderson Series Balanced Portfolio-Service Shares | 10/27/2021 | Janus Aspen Series | 11,716,000 | 564,685 | | | |\n| 000031-01-5 | Janus Henderson Series Enterprise Portfolio-Institutional Shares | 10/22/2021 | Janus Aspen Series | 29,300,000 | 2,739,056 | | | |\n| 000031-02-9 | Janus Henderson Series Enterprise Portfolio-Service Shares | 10/22/2021 | Janus Aspen Series | 54,085,000 | 1,080,348 | | | |\n| 471021-40-2 | Janus Henderson Series Forty Portfolio-Institutional Shares | 12/31/2021 | Janus Aspen Series | 56,294,000 | 3,165,975 | | | |\n| 471021-40-3 | Janus Henderson Series Forty Portfolio-Service Shares | 12/31/2021 | Janus Aspen Series | 46,100,000 | 1,012,412 | | | |\n| 471021-20-4 | Janus Henderson Series Global Research Portfolio-Service Shares | 10/20/2021 | Janus Aspen Series | 155,000 | 10,138 | | | |\n| 471021-71-7 | Janus Henderson Series Overseas Portfolio-Institutional Shares | 12/31/2021 | Janus Aspen Series | 5,344,000 | 226,871 | | | |\n| 471021-71-8 | Janus Henderson Series Overseas Portfolio-Service Shares | 12/31/2021 | Janus Aspen Series | 9,420,000 | 384,674 | | | |\n| 471021-30-3 | Janus Henderson Series Research Portfolio-Institutional Shares | 11/02/2021 | Janus Aspen Series | 16,371,000 | 829,712 | | | |\n| 471021-60-2 | Janus Henderson Series Research Portfolio-Service Shares | 10/22/2021 | Janus Aspen Series | 9,195,000 | 462,470 | | | |\n| 471021-60-3 | Janus Henderson Series Research Portfolio-Variable Class | 10/22/2021 | Morgan Stanley Variable Insurance Fund, Inc. | 46,220,000 | 1,441,441 | | | |\n| 471021-66-7 | Morgan Stanley VIF Disciplined Portfolio-Class I | 12/31/2021 | Morgan Stanley Variable Insurance Fund, Inc. | 174,605,000 | 3,658,114 | | | |\n| 471021-66-8 | Morgan Stanley VIF Disciplined Portfolio-Class I | 12/31/2021 | Morgan Stanley Variable Insurance Fund, Inc. | 1,515,000 | 35,895 | | | |\n| 841222-85-6 | Nuveenberg Berman ARI Mid-Cap Growth Portfolio-Class S | 10/22/2021 | Nuveenberg Berman Advisors Management Trust | 1,817,000 | 66,708 | | | |\n| 841222-85-3 | Nuveenberg Berman ARI Sustainable Equity Portfolio-Class S | 12/25/2021 | Nuveenberg Berman Advisors Management Trust | 4,704,000 | 160,300 | | | |\n| 868298-81-0 | PINCO VIT High Yield Portfolio-Administrative Class | 12/31/2021 | PINCO Variable Insurance Trust | 35,289,000 | 354,094 | | | |\n| 868298-81-9 | PINCO VIT Real Return Portfolio-Administrative Class | 12/31/2021 | PINCO Variable Insurance Trust | 42,165,000 | 586,437 | | | |\n| 868298-82-7 | PINCO VIT Total Return Portfolio-Administrative Class | 12/31/2021 | PINCO Variable Insurance Trust | 177,488,000 | 1,699,218 | | | |\n| 355190-42-6 | Rydex Variable Trust | 12/31/2021 | Rydex Variable Trust | 1,129,000 | 176,762 | | | |\n| 867432-71-4 | Timothy Plan Conservative Growth Variable | 12/31/2021 | The Timothy Plan | 1,364,000 | 16,661 | | | |\n| 867432-71-5 | Timothy Plan Growth Variable | 12/31/2021 | The Timothy Plan | 1,360,000 | 17,185 | | | |\n| 97200P-88-8 | Nikshira Global Allocation Fund | 12/30/2021 | Nikshira Variable Insurance Trust | 1,636,000 | 270,323 | | | |\n| 94999999 | Subtotal - Common Stocks - Mutual Funds | 55,721,039 | XXX | 0 | | | | |\n| 979999987 | Total - Common Stocks - Part 3 | 55,721,039 | XXX | 0 | | | | |\n| 979999988 | Total - Common Stocks - Part 5 | 501,382 | XXX | 0 | | | | |\n| 97999999 | Total - Common Stocks | 56,222,421 | XXX | 0 | | | | |\n| 98999999 | Total - Preferred and Common Stocks | 56,222,941 | XXX | 0 | | | | |\n| 99999999 | Totals | 56,222,941 | XXX | 0 | | | | |\n\n| CUSIP Identification | Description | Foreign Disposal Date | Name of Purchaser | Number of Shares of Stock | Consideration | Par Value | Actual Cost | Prior Year Book/Adjusted Carrying Value | Unrealized Valuation Increase/Decrease | Current Year's (Amortization)/Accretion | Total Change in Book/Adjusted Carrying Value | Total Foreign Exchange Gain/Loss on Disposal | Book/Adjusted Carrying Value at Disposal Date | Foreign Exchange Gain (Loss) on Disposal | Realized Gain (Loss) on Disposal | Total Gain (Loss) on Disposal | Bond Interest/Stock Dividends Received During Year | Stated Contractual Maturity Date |\n|----------------------|-------------|-----------------------|-------------------|--------------------------|--------------|-----------|------------|----------------------------------------|----------------------------------------|------------------------------------------|-----------------------------------------------|---------------------------------------------|---------------------------------------------|---------------------------------------------|---------------------------------------------|---------------------------------------------|---------------------------------------------|---------------------------------------------|\n| 83999997 | Total - Bonds - Part 4 | | | | | | | | | | | | | | | | |\n| 83999998 | Total - Bonds - Part 5 | | | | | | | | | | | | | | | | |\n| 83999999 | Total - Bonds | | | | | | | | | | | | | | | | |\n| 89999997 | Total - Preferred Stocks - Part 4 | | | | | | | | | | | | | | | | |\n| 89999998 | Total - Preferred Stocks - Part 5 | | | | | | | | | | | | | | | | |\n| 89999999 | Total - Preferred Stocks | | | | | | | | | | | | | | | | |\n| 01876-54-9 | US-IPS International Value Portfolio-Class B | 12/28/2021 | All Variable Product Series Fund, Inc., American Century Variable Portfolios, Inc. | 4,395,000 | 67,888 | 56,874 | .63,027 | (6,132) | (16,132) | 56,874 | 11,013 | 197 | XXX |\n| 02486-35-4 | American Century VP Capital Appreciation I | 12/29/2021 | American Century Variable Portfolios, Inc. | 80,351,000 | 1,302,404 | 1,168,943 | 1,548,367 | (379,426) | (379,426) | 1,168,943 | 333,461 | 135,812 | XXX |\n| 02486-76-7 | American Century VP Large Company Value Fund-Class I | 12/31/2021 | American Century Variable Portfolios, Inc. | 35,490,000 | 702,448 | 515,363 | 625,074 | (193,711) | (193,711) | 515,363 | 187,086 | 3,613 | XXX |\n| 02486-75-9 | American Century VP Large Company Value Fund-Class II | 12/31/2021 | American Century Variable Portfolios, Inc. | 52,092,000 | 973,096 | 694,661 | 860,565 | (165,904) | (165,904) | 694,661 | 278,434 | 4,125 | XXX |\n| 02486-74-2 | American Century VP Mid Cap Value Fund-Class I | 12/31/2021 | American Century Variable Portfolios, Inc. | 58,015,000 | 1,345,837 | 1,062,770 | 1,191,620 | (128,850) | (128,850) | 1,062,770 | 283,057 | 281,067 | 3,392 |\n| 02486-73-4 | American Century VP Mid Cap Value Fund-Class II | 12/31/2021 | American Century Variable Portfolios, Inc. | 35,131,000 | 827,440 | 653,342 | 722,650 | (69,348) | (69,348) | 653,342 | 174,098 | 2,706 | XXX |\n| 02486-88-2 | American Century VP Ultra Fund-Class I | 12/31/2021 | American Century Variable Portfolios, Inc. | 48,986,000 | 1,386,229 | 763,386 | 1,346,131 | (582,745) | (582,745) | 763,386 | 622,843 | 59,063 | XXX |\n| 02486-85-8 | American Century VP Ultra Fund-Class II | 12/31/2021 | American Century Variable Portfolios, Inc. | 6,088,000 | 164,599 | 111,521 | 162,846 | (51,327) | (51,327) | 111,521 | 52,578 | 11,411 | XXX |\n| 01027-80-3 | AVII Morningstar Balanced ETF Asset Allocation Portfolio-Class II | 12/31/2021 | AVII Morningstar Conservative ETF Asset Allocation Portfolio-Class II | 148,625,000 | 1,769,020 | 1,610,249 | 1,670,540 | (60,291) | (60,291) | 1,610,249 | 158,771 | 6,419 | XXX |\n| 01027-80-7 | AVII Morningstar Growth ETF Asset Allocation Portfolio-Class II | 12/31/2021 | AVII Morningstar Growth ETF Asset Allocation Portfolio-Class II | 42,040,000 | 491,545 | 474,646 | 487,244 | (12,598) | (12,598) | 474,646 | 16,898 | 943 | XXX |\n| 01027-87-8 | AVII Morningstar Income and Growth ETF Asset Allocation Portfolio-Class II | 12/31/2021 | AVII Morningstar Income and Growth ETF Asset Allocation Portfolio-Class II | 235,326,000 | 2,911,002 | 2,229,334 | 2,636,535 | (410,202) | (410,202) | 2,229,334 | 681,668 | 7,511 | XXX |\n| 01027-85-5 | BlackRock VFI Global Allocation V.I. Fund-Class I | 12/31/2021 | BlackRock Variable Investment Trust | 58,943,000 | 671,999 | 642,325 | 649,553 | (7,228) | (7,228) | 642,325 | 29,674 | 1,475 | XXX |\n| 06254-40-5 | BlackRock VFI Global Allocation V.I. Fund-Class II | 12/30/2021 | BlackRock Variable Investment Trust | 37,990,000 | 574,860 | 649,375 | 515,094 | 133,471 | 133,471 | 649,375 | (74,515) | 3,752 | XXX |\n| 06254-77-7 | BlackRock VFI Global Allocation V.I. Fund-Class III | 12/29/2021 | BlackRock Variable Investment Trust | 10,137,000 | 204,146 | 178,165 | 197,577 | (19,412) | (19,412) | 178,165 | 25,981 | 2,165 | XXX |\n| 06254-87-6 | BlackRock VFI High Yield V.I. Fund-Class I | 12/31/2021 | BlackRock Variable Investment Trust | 1,892,000 | 1,892 | 1,892 | 1,892 | 0 | 0 | 1,892 | 0 | 0 | XXX |\n| 06254-10-7 | BlackRock VFI High Yield V.I. Fund-Class II | 12/29/2021 | BlackRock Variable Investment Trust | 22,764,000 | 172,884 | 174,150 | 172,094 | 2,066 | 2,066 | 174,150 | (1,266) | (1,266) | 2,701 |\n| 05897-50-0 | BW Mellon IP High-Div Stock Portfolio-Service Shares | 12/31/2021 | BW Mellon Investment Management, Inc. | 12,335,000 | 282,778 | 243,232 | 244,729 | (1,498) | (1,498) | 243,232 | 39,544 | 2,001 | XXX |\n| 05897-40-9 | BW Mellon IP Technology Growth Portfolio-Service Shares | 12/29/2021 | BW Mellon Investment Management, Inc. | 98,675,000 | 3,553,325 | 1,207,227 | 3,619,407 | (2,412,170) | (2,412,170) | 1,207,227 | 2,346,088 | 310,443 | XXX |\n| 0866-1P-10-5 | BW Mellon Stock Index Fund, Inc.-Initial Shares | 12/31/2021 | BW Mellon Stock Index Fund, Inc. | 129,258,000 | 9,091,838 | 3,196,069 | 8,397,391 | (5,171,320) | (5,171,320) | 3,196,069 | 5,855,770 | 315,464 | XXX |\n| 0866-1P-20-4 | BW Mellon Stock Index Fund, Inc.-Service Shares | 12/31/2021 | BW Mellon Stock Index Fund, Inc. | 68,339,000 | 4,785,255 | 2,119,881 | 4,398,970 | (2,279,090) | (2,279,090) | 2,119,881 | 2,673,375 | 171,110 | XXX |\n| 05586-10-1 | BW Mellon Sustainable U.S. Equity Portfolio, Inc.-Initial Shares | 12/31/2021 | BW Mellon Sustainable U.S. Equity Portfolio, Inc. | 38,298,000 | 2,054,538 | 1,442,257 | 1,898,337 | (414,080) | (414,080) | 1,442,257 | 612,282 | 46,158 | XXX |\n\n| CUSIP Identification | Description | Foreign Disposal Date | Name of Purchaser | Number of Shares of Stock | Consideration | Par Value | Actual Cost | Price/Year Book/Adjusted Carrying Value | Unrealized Valuation Increase/Decrease | Current Year's (Amortization)/Accretion | Change In Book/Adjusted Carrying Value | Total Change in Book/Adjusted Carrying Value | Total Foreign Exchange Gain (Loss) on Disposal | Book/Adjusted Carrying Value at Disposal Date | Foreign Exchange Gain (Loss) on Disposal | Realized Gain (Loss) on Disposal | Total Gain (Loss) on Disposal | Bond Interest/Stock Dividends Received During Year | Stated Contractual Maturity Date |\n|----------------------|-------------|-----------------------|-------------------|--------------------------|--------------|-----------|------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|\n| 641222-85-6 | Neuberger Berman MFT Mid-Cap Growth Portfolio-Class S | 12/31/2021 | Neuberger Berman Advisers Management | 296,000 | 9,140 | 5,700 | $22 | (3,321) | | | | | | | | | | | | |\n| 641222-82-3 | Neuberger Berman MFT Sustainable Equity Portfolio-Class S | 12/29/2021 | Neuberger Berman Advisers Management | 16,628,000 | 576,378 | 435,824 | 511,814 | (75,991) | | | | | | | | | | | | |\n| 66338A-30-4 | PIMCO High Yield Portfolio-Administrative Class | 12/29/2021 | Insurance Trust | 80,773,000 | 644,424 | 640,641 | 648,983 | (6,352) | | | | | | | | | | | | |\n| 66338A-81-9 | PIMCO Variable Rate Portfolio-Administrative Class | 12/29/2021 | Insurance Trust | 97,247,000 | 1,350,683 | 1,245,203 | 1,353,673 | (110,470) | | | | | | | | | | | | |\n| 66339A-40-5 | PIMCO Total Return Portfolio-Administrative Class | 12/29/2021 | Insurance Trust | 242,384,000 | 2,687,656 | 2,714,928 | 2,806,226 | (94,298) | | | | | | | | | | | | |\n| 88743Z-71-4 | Timothy Plan Conservative Growth Variable | 12/30/2021 | The Timothy Plan | 3,472,000 | 116,110 | 111,159 | 110,533 | 806 | | | | | | | | | | | | |\n| 88743Z-72-2 | Timothy Plan Strategic Growth Variable | 12/31/2021 | The Timothy Plan | 12,882,000 | 162,733 | 146,554 | 153,857 | (7,383) | | | | | | | | | | | | |\n| 87203F-86-2 | T. Rowe Price Global Allocation Fund | 12/31/2021 | Insurance Trust | 15,008,000 | 351,107 | 281,696 | 311,522 | (48,826) | | | | | | | | | | | | |\n| 94799999 - Subtotal - Mutual Funds | | | | | | | | | | | | | | | | | | | | | |\n| 94799999 - Subtotal - Common Stocks - Mutual Funds | | | | | | | | | | | | | | | | | | | | | |\n| 97999997, Total - Common Stocks - Part 4 | | | | | | | | | | | | | | | | | | | | | |\n| 97999998, Total - Common Stocks - Part 5 | | | | | | | | | | | | | | | | | | | | | |\n| 97999999, Total - Common Stocks | | | | | | | | | | | | | | | | | | | | | |\n| 98999999, Total - Preferred and Common Stocks | | | | | | | | | | | | | | | | | | | | | |\n| 99999999 - Totals | | | | | | | | | | | | | | | | | | | | | |\n\n| CUSIP Identification | Description | Foreign | Date Acquired | Name of Vendor | Disposal Date | Name of Purchaser | Par Value (Bonds) or Number of Shares (Stock) | Actual Cost | Consideration | Book/Adjusted Carrying Value at Disposal | Unrealized Gain/(Loss)/Accretion | Current Year's Amortization/Impairment Recognized | Change in Book/Adjusted Carrying Value | Total Foreign Exchange Change in Book/Adjusted Carrying Value | Foreign Exchange Gain (Loss) on Disposal | Realized Gain (Loss) on Disposal | Total Gain (Loss) on Disposal | Interest and Dividends Received During Year | Paid for Accrued Interest and Dividends |\n|----------------------|-------------|---------|---------------|----------------|--------------|------------------|---------------------------------------------|-------------|--------------|------------------------------------------|---------------------------------|-------------------------------------------------|---------------------------------|-------------------------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|\n| 83999998 | Total - Bonds | | | | | | | | | | | | | | | | | | |\n| 89999998 | Total - Preferred Stocks | | | | | | | | | | | | | | | | | | |\n| 05599U-30-9 | BNY Mellon VIF Government Money Market | | 12/31/2021 | | 12/28/2021 | BNY Mellon Variable Insurance Funds | 370,269,000 | 370,269 | 370,269 | 370,269 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 0088R-74-0 | Invesco Y.I. Equity and Income Fund - Series I Shares | | 12/31/2021 | | 12/30/2021 | Invesco Variable Insurance Funds | 5,549,000 | 110,910 | 112,770 | 110,910 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 0088R-26-2 | Invesco Managed Volatility Fund - Series II Shares | | 04/20/2021 | | 04/30/2021 | Invesco Variable Insurance Funds | 1,700,000 | 20,703 | 20,779 | 20,703 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |\n| 94999999 | Subtotal - Common Stocks - Mutual Funds | | | | | | | | | | | | | | | | | | |\n| 97999998 | Total - Common Stocks | | | | | | | | | | | | | | | | | | |\n| 98999999 | Total - Preferred and Common Stocks | | | | | | | | | | | | | | | | | | |\n| 99999999 | Totals | | | | | | | | | | | | | | | | | | |\n\nSchedule DA - Part 1 - Short-Term Investments Owned\n\nNONE\n\nSchedule DB - Part A - Section 1 - Options, Caps, Floors, Collars, Swaps and Forwards Open\n\nNONE\n\nSchedule DB - Part A - Section 2 - Options, Caps, Floors, Collars, Swaps and Forwards Terminated\n\nNONE\n\nSchedule DB - Part B - Section 1 - Futures Contracts Open\n\nNONE\n\nSchedule DB - Part B - Section 1B - Brokers with whom cash deposits have been made\n\nNONE\n\nSchedule DB - Part B - Section 2 - Futures Contracts Terminated\n\nNONE\n\nSchedule DB - Part D - Section 1 - Counterparty Exposure for Derivative Instruments Open\n\nNONE\n\nSchedule DB - Part D-Section 2 - Collateral for Derivative Instruments Open - Pledged By\n\nNONE\n\nSchedule DB - Part D-Section 2 - Collateral for Derivative Instruments Open - Pledged To\n\nNONE\n\nSchedule DB - Part E - Derivatives Hedging Variable Annuity Guarantees as of December 31 of Current Year\n\nNONE\n\nSchedule DL - Part 1 - Reinvested Collateral Assets Owned\n\nNONE\n\nSchedule DL - Part 2 - Reinvested Collateral Assets Owned\n\nNONE\n\nSchedule E - Part 1 - Month End Depository Balances\n\nNONE\n\nSchedule E - Part 2 - Cash Equivalents Owned\n\nSchedule E - Part 3 - Special Deposits"},"books_score":{"kind":"number","value":0.9778642654418945,"string":"0.977864"}}},{"rowIdx":8684,"cells":{"content":{"kind":"string","value":"Pan European High Resolution Snow & Ice Monitoring of the Copernicus Land Monitoring Service (CoSIMS)\n\nAtelier Glaciologie | CNES | 25 Juin 2019\n\nSimon Gascoin (Cesbio)\nJoël Dorandeu (Magellium)\n\nCopernicus is a European system for monitoring the Earth. Data is collected by different sources, including Earth observation satellites and in-situ sensors. The data is processed and provides reliable and up-to-date information in six thematic areas: land, marine, atmosphere, climate change, emergency management and security. The land theme is divided into four main components:\n\n- **Global**: Provides a series of biophysical products on the status and evolution of the land surface at global scale at mid and low spatial resolution.\n\n- **Pan-European**: Provides information about the land cover and land use (LC/LU), land cover and land use changes and land cover characteristics.\n\n- **Local**: Focuses on different hotspots, i.e. areas that are prone to specific environmental challenges and problems.\n\n- **Imagery and reference data**: Satellite imagery forms the input for the creation of Copernicus land products. In order to ensure an efficient and effective use of satellite data the Copernicus land monitoring service needs access to in-situ data.\n\nProject Objectives\n\n- The snow and ice service aims at producing high resolution snow and ice products over Europe from Sentinel-2 data.\n\n- The products will contain information on fractional snow cover, permanent snow line and river and lake ice extent.\n\nProject Objectives\n\n- Average fractional snow cover from MODIS snow product (5 km resolution) over EEA-39 countries.\n\n- Sentinel-2 false color image and its Ice Index (NDWI2) image created using ESA SNAP.\n\nProject Objectives\n\n• Main steps:\n - From May 2019 to March 2020: set-up of the service\n - From April 2020 to December 2022: Operational production of High Resolution Snow and Ice products over Europe from Sentinel-2 data\n - Reprocessing of Sentinel-2 data from September 2016 onwards\n\n• Main requirements:\n - operational service: NRT, timeliness, availability, sustainability\n - state-of-the-art service at European Scale\n - fully validated\n - connected to users (needs, validation): friendliness, responsiveness, uptake\n\nConsortium\n\n• Strong Scientific background for a State-of-the-Art Service\n – well-experienced scientific teams able to provide the required scientific advices for setting up, assess, evolve and operate the service\n – strong links to R&D initiatives at national and European levels\n\nConsortium\n\n- Forte implication du CNES dans les phases initiales de montage du consortium:\n - Valorisation des investissements CNES dans le système THEIA\n - Un schéma qui a fait ses preuves: océano (DUACS->CMEMS, HydroWeb->Global Land, THEIA MAJA+LIS -> Land/Pan-European)\n - Agence Spatiale (CNES) qui investit et prépare la R&D + système pré-opérationnel\n - Laboratoire d'excellence scientifique\n - Société privée qui s'engage sur la thématique et la durée: industrialisation, lien scientifique, opérations\n\n- Accompagnement CNES:\n - Support au laboratoire CESBIO\n - Support à Magellium\n\nConsortium\n\nProject Manager\nJ. Dorandeu (Magellium)\n\nContract Manager\nL. Martinez (Magellium)\n\nService Manager, Central Engineering & QA\nM. Ablain (Magellium)\n\nScience leader\nS. Gascoin (Cesbio)\n\nExpert Panel\nA. Kaad (UiO)\nS. Morin (CEN)\n\nIce Products\n\nService Manager\nB. Weinrit (Astri Polska)\n\nDevelopment and integration\nW. Bijak (Astri Polska)\n\nProducts Quality Assessment\nE. Kobrzycka (Astri Polska)\n\nSnow Products\n\nService Manager\nM. Ablain (Magellium)\n\nDevelopment and integration\nG Salgues (Magellium)\n\nProducts Quality Assessment\nS. Gascoin (Cesbio)\n\nProject Objectives\n\n• Transition of precursor services into Copernicus\n – the Copernicus Service benefits from past or current investments\n – National services respectively the Theia Snow Collection in France and the river ice monitoring service in Poland\n\n• Integration within Copernicus Services and National services\n – Global Land Service (CGLOPS-2 - Cryosphere and water)\n – National Services (R&D and prototypes)\n – involvement or interactions with R&D projects (CCi, H2020...).\n\nProject Objectives\n\n- Operational service:\n - Based on already demonstrated operational services at national level. Service to be geographically extended and consolidated (operational requirements)\n - Rigorous project management and technical methodology, building on current and past experiences: project life cycle, phases and corresponding deliverables are proposed following standards successfully demonstrated in other Copernicus Services.\n - Operational Production Environment: DIAS\n - taking benefit of EU investments (DIAS)\n - national infrastructures as backup\n\nProject Tasks\n\nWORK LOGIC\n\n- WP 8000: Project Management\n- WP 1000: NRT production FSC [2020-2022]\n- WP 2000: NRT production PSL [2020-2022]\n- WP 3000: NRT production RLI [2020-2022]\n- WP 5000: Reprocessing production [2017-2019]\n- WP 4000: Data Access\n- WP 6000: Harmonisation\n- WP 7000: User Uptake\n\nTransverse activities\n\n## Project Schedule\n\n| WP-0: Management | 2019 | 2020 | 2021 | 2022 |\n|------------------|------|------|------|------|\n| WP-100: Fractional Snow Cover (FSC) | | | | |\n| WP 1100: ATBD | | | | |\n| WP 1200: Setup | | | | |\n| WP1300: Quality assessment | | | | |\n| WP1400: Production | | | | |\n\n| WP-200: Permanent Snow Line (PSL) | | | | |\n| WP 1100: ATBD | | | | |\n| WP 1200: Setup | | | | |\n| WP1300: Quality assessment | | | | |\n| WP1400: Production | | | | |\n\n| WP-300: River and Lake Ice extent (RI) | | | | |\n| WP 1100: ATBD | | | | |\n| WP 1200: Setup | | | | |\n| WP1300: Quality assessment | | | | |\n| WP1400: Production | | | | |\n\n| WP-400: Data access | | | | |\n| WP 4100: Data access and visualization | | | | |\n| WP 4200: Data Access Statistics | | | | |\n\n| WP-500: Reprocessing (3 years) | | | | |\n| WP5100: FSC & PSL | | | | |\n| WP5200: RI | | | | |\n\n| WP-600: Harmonisation with CLMS global component | | | | |\n| WP6100: Harmonisation | | | | |\n| WP6200: Central Engineering | | | | |\n\n| WP-700: User uptake | | | | |\n| WP7100: Helpdesk | | | | |\n| WP7200: Promotion/Communication | | | | |\n\n**Project Meeting**\n\n- KOM\n- PMP1\n- ORR\n- Use Workshop p1\n- PMP2\n- AOR#1\n- PMP3\n- AOR#2\n- Use Workshop p2\n- PMP4\n- LM\n\nSpecific Contract # 1\n\nWhat we currently do\n\n- Snow cover area from Sentinel-2 and Landsat-8\n- Operational, product released about 2 to 5 days after acquisition\n- Selected mountain regions\n\nWhat we will do for CoSIMS\n\n- Snow cover fraction from Sentinel-2 (10% RMSE)\n- Product released in less than 3 hours after L1C dissemination\n- Pan-European\n\nWhat we currently do\n\n- Snow cover area from Sentinel-2 and Landsat-8\n\nMultitemporal algorithm\n\n\\[ NDSI = \\frac{VIS - MIR}{VIS + MIR} \\]\n\n\\[ NDSI > a \\Rightarrow neige \\]\n\nWhat we will do\n\n- Snow cover fraction from Sentinel-2\n\nMultitemporal algorithm\n\n\\[ NDSI = \\frac{VIS - MIR}{VIS + MIR} \\]\n\n\\[ NDSI > a \\Rightarrow neige \\]\n\n\\[ FSC = f(NDSI) \\]\n\n2017-04-16 zs=1589\nDEM, Cloud, Snow, 2S\n\n2017-05-06 zs=1892\nDEM, Cloud, Snow, 2S\n\n2017-05-16 zs=1993\nDEM, Cloud, Snow, 2S\n\n2017-05-26 zs=2094\nDEM, Cloud, Snow, 2S\n\n2017-06-05 zs=2499\nDEM, Cloud, Snow, 2S\n\n2017-06-15 zs=2397\nDEM, Cloud, Snow, 2S\n\n2017-04-16 2017-05-06 2017-05-16\n2017-05-26 2017-06-05 2017-06-15\n\n- How to establish $FSC = f(NDSI)$?\n\nReference datasets\n- From Kalideos VHR images by supervised classification\n- Publicly available products\n\nTrade-off resolution vs. coverage in reference datasets\n\nArea\n\nPixel size\n\nSatellite imagery\nAirborne campaign\nTerrestrial camera\n\n- How to establish $FSC = f(NDSI)$?\n\n- How to establish $FSC = f(NDSI)$?\n\nWebcam\n\nSource: Tenevia\n\nSentinel-2\n\n• Dealing with forests\n\n\\[ FSC_{On-Ground} = \\frac{FSC_{Top-Of-canopy}}{(1-TCD)} \\]\n\nwith \\( TCD \\): Copernicus High Resolution Layer Tree Cover Density\n\n- Known issues\n https://gitlab.orfeo-toolbox.org/remote_modules/let-it-snow/issues\n\nHigh cold clouds classified as snow\n\n• Unknown issues\n\nHigh latitudes (Sweden, Norway, Finland)\n\n- Low solar illumination\n- Extensive evergreen forest\n\nPermanent snowline\n\nWhat we currently do\nTemporal synthesis of Theia snow products over any period of time\n\n• What we will do for CoSIMS\n Annual synthesis of FSC products\n Extract pixels with snow cover duration > 360 days\n\nWhat we currently do\n\nTemporal synthesis of Theia snow products over any period of time\n\n1) Linear interpolation in the time dimension\n\n2) Summation in the time dimension\n\nPermanent snowline\n\nWhat we currently do\n\nTemporal synthesis of Theia snow products over any period of time\n\nhttp://osr-cesbio.ups-tlse.fr/echangeswww/majadata/simon/snowMaps.html\n\nPermanent snowline\n\nWhat we will do\n\nPermanent snow line extraction\n\nBinarize FSC\n\nCompute annual SCD\n\nExtract pixels with SCD = 365 days\n\nfilter (forest cover and elevation)\n\nPermanent snow line\n\nConclusion\n\n- FSC and PSL code are minor extensions of existing let-it-snow codes\n- Main development is $FSC = f(NDSI)$\n- ATBD and code will be kept open source [https://gitlab.orfeo-toolbox.org/remote_modules/let-it-snow](https://gitlab.orfeo-toolbox.org/remote_modules/let-it-snow)\n- Challenges\n - Specified accuracy of FSC\n - Snow/cloud confusion\n - High latitudes regions"},"books_score":{"kind":"number","value":0.4214784502983093,"string":"0.421478"}}},{"rowIdx":8685,"cells":{"content":{"kind":"string","value":"PRF - Radon Mitigation Fans\n\nAdvancing Ventilation®\n\nRadon is a hazardous, odorless gas that is everywhere! It cannot be seen, tasted or smelled by humans, making it impossible to detect without radon testing. Nearly 1 out of every 15 homes in the U.S. is estimated to have elevated radon levels.\n\n**WHAT IS RADON?**\nRadon comes from the natural radioactive breakdown of uranium in soil, rocks, and waters. As the breakdown happens, the gas moves into the air you breathe. It can affect any building but is most dangerous at home. When radon is trapped in your home the gas can build up to dangerous levels, resulting in health risk, such as lung cancer. The EPA estimates radon is the #1 cause of lung cancer among non-smokers and second leading cause of lung cancer.*\n\n**TESTING FOR RADON**\nRadon testing is the only way to know if you and your family are at risk. Testing is easy and inexpensive; most hardware stores carry radon test kits. EPA recommends you mitigate your home with any radon level above 4 Picocuries per liter (4pCi/L)\n\nReducing radon levels in your home is easy. Find a qualified radon service professional to mitigate your home through your state’s radon office or at the EPA website at [https://www.epa.gov/radon/find-radon-test-kit-or-measurement-and-mitigation-professional](https://www.epa.gov/radon/find-radon-test-kit-or-measurement-and-mitigation-professional).\n\n*For more information about radon risks and solutions visit [https://www.epa.gov/radon](https://www.epa.gov/radon)*\n\n**TYPICAL INSTALLATION**\nA licensed radon mitigator will design the right solution for your home. A radon system works by lowering the air pressure beneath your home using a specially designed radon fan. The fan draws out the radon gas and safely vents it through a pipe above the roof. The fan can be installed on the exterior of the home (Figure 1) or through the interior or garage (Figure 2).\n\nPRF - Radon Mitigation Fans\n\nAPPLICATION\nPRF fans are specifically designed for radon mitigation.\n\nSPECIFICATIONS\n- Duct connections sized for easy fit with standard PVC couplings typically used in radon mitigation applications\n- Totally enclosed air over\n- Fully sealed, high quality plastic housing\n- Large, easily accessible, watertight electrical box for unobstructed wiring process\n- Easily mount on duct pipe or a heavy-duty metal mounting bracket can be used (sold separately)\n- Significantly less expensive than comparable alternatives\n- Thermal overload protection\n- HVI Certified Performance\n- cETLus certified\n- 5-year warranty\n\nPRF PERFORMANCE\n\n| Model | Size | Electrical | Power (W) | Current (A) | RPM | Airflow (CFM) @ Static Pressure (in wc) |\n|---------|------|----------------|-----------|-------------|--------|----------------------------------------|\n| | | | | | | 0.00 | 0.20 | 0.40 | 0.60 | 0.80 | 1.00 |\n| PRF-100 | 4\" | 1/60/120V | 92 | 0.77 | 3080 | 169 | 150 | 133 | 117 | 99 | 82 |\n\nDIMENSIONS\n\nRADON INSTALLATION KITS\nS&P offers convenient kits for easy installation. Kits include two flexible black couplings with stainless steel hose clamps, a U-tube manometer, and radon system labels. The U-tube manometer (PR-M) is available to purchase separately.\n\n| Kit | Used with Model | PVC pipe size |\n|-----------|-----------------|---------------|\n| PRFIK-43 | PRF-100 | 3\" |\n| PRFIK-44 | PRF-100 | 4\" |\n\nAll specifications are subject to change without notice unless approved in submittal by S&P USA.\n\nS&P USA Ventilation Systems, LLC\n6393 Powers Avenue\nJacksonville, FL 32217\nT. 904-731-4711 • F. 904-737-8322\nwww.solerpalau-usa.com\n\nS&P Canada Ventilation Products, Inc.\n6710 Maritz Drive Unit #7\nMississauga, ON L5W 0A1 - Canada\nT. 416-744-1217 • F. 416-744-0887\nwww.solerpalaucanada.com\n\nSoler&Palau\nVentilation Group"},"books_score":{"kind":"number","value":0.40505436062812805,"string":"0.405054"}}},{"rowIdx":8686,"cells":{"content":{"kind":"string","value":"10-fold Islamic Rosette Pattern\n\nSarah Gelsinger Brewer\n@mathemartiste\nmathemartiste.com\n2021\n\nStart by drawing a circle. Your entire motif will fit inside this circle, so make it large.\n\nPlacing your pencil point in the center of your circle and bringing your ruler to your pencil, draw a horizontal line.\n\nKeeping your radius the same as before, place your compass at the intersections of your original circle and horizontal line, and mark the four indicated intersections. Note that these four points, along with the right and left points on the original circle, determine a regular hexagon.\n\nDecrease your compass radius to a little more than half the distance between the top two hexagonal intersections. By drawing intersecting arcs of the same radius from each of the four hexagonal intersections, we find two points that determine the perpendicular bisector of our horizontal diameter.\n\nDraw the vertical line through the two points defined in the last step.\n\nThe right two hexagonal intersections determine the midpoint of the radius.\n\nSet your radius to the distance between the “north” point on your circle and the radius midpoint determined in the last step. Note that if we consider our original circle radius (the height of the highlighted triangle) to be 1, the base of the highlighted triangle is $\\frac{1}{2}$ and the hypotenuse of this right triangle (and what we are now setting our radius to) is the “golden ratio” phi: $\\varphi = \\frac{1+\\sqrt{5}}{2}$.\n\nCentering your compass at the radius midpoint as if to draw an arc that passes through the “north” point on the circle, mark the intersection of that arc with the horizontal line.\n\nCentering the compass at “north” with a radius determined by the intersection with the horizontal determined in the last step, mark the intersections of this arc with the original circle. These two points, along with “north,” determine two sides of a regular pentagon.\n\nWalk the radius used in the last step around to determine the last two vertices of the regular pentagon.\n\nYou don’t need to draw in this pentagon. It is merely highlighted here to show the construction. In the next few steps we will keep the same radius and basically repeat this pentagonal construction three more times (with vertex at south, west, and east) to give us a total of $5 \\times 4 = 20$ radial divisions of our circle.\n\nStarting from the “south” point on your circle and with the same radius, mark the nearest two pentagonal vertices.\n\nWalk your compass around to mark the last two pentagonal vertices. Being careful to omit the “east” and “west” points, as well as the early six-fold divisions, we now have the vertices necessary to construct a regular decagon.\n\nRepeat this same process starting from the “west” point.\n\nAnd again starting with the “east” point.\n\nWhile the twenty-fold divisions could be found later, I find them helpful for ensuring accuracy in my construction. So as to not get confused in the coming steps, take a moment to circle the vertices highlighted here in red.\n\nConnect the indicated vertices. This rectangle will contain our design, and can be used to tile the plane. Now that we have this rectangle drawn in, those initial hexagonal intersections will be reduced to small vertices in the remaining steps of this tutorial.\n\nDraw in the two diagonals of the rectangle.\n\nDraw in the four line segments connecting the midpoints of each side of the rectangle.\n\nNote that this rhombus can also be used to tile this pattern across the plane.\n\nThe next few steps serve to fill in the missing twenty-fold radial divisions at each corner of the rectangle. We achieve this by drawing chords to each of the ten-fold divisions of our original circle. This results in twenty-fold divisions at the corner because we are forming inscribed angles, each of which is half the measure of the intercepted arc. The same arc is equal to a central angle (vertex at the center of our original circle) that intercepts it. Hence, a ten-fold division from the center results in a twenty-fold division at the corner.\n\nAdd the missing three radial divisions at the bottom right.\n\nAdd the missing three radial divisions at the upper left.\n\nAdd the missing three radial divisions at the upper right.\n\nWe won’t need these line segments for a while, but before things get too busy, let’s go ahead and draw in the four line segments at the corners, by connecting the “north” point (pi/2) to the points at pi/10 and 9pi/10 (measuring counterclockwise from the “east” point).\n\nDraw the indicated six lines to complete the twenty-fold divisions at the center.\n\nLocate the intersections highlighted in red, and draw the two indicated horizontal lines. Note that you should have four total intersections to help you line up each one accurately.\n\nFind the intersection of the two radial lines highlighted with red dotted lines. Centering your compass at the top left corner of the rectangle, use this intersection point to set your radius. You can check it against similar intersections in the other three corners before drawing circles at each corner and the center, all with this same radius.\n\nNote the points along each red circle that indicate intersections with radial lines. You may want to circle these to help you keep track of the next few steps.\n\nLocate the intersections at $4\\pi/10$, $6\\pi/10$, $14\\pi/10$ and $16\\pi/10$ on the central circle. Draw the indicated verticals parallel to the original vertical. You should notice a couple other intersections that will help you line these up properly.\n\nWe are going to draw similar pairs of parallels all the way around. These two are on either side of the diagonal. Take care to make sure you are lining up the correct intersections.\n\nDraw two more parallels along the other diagonal.\n\nTwo more parallels, connecting $8\\pi/10$ to 0 and $10\\pi/10$ ($\\pi$) to $18\\pi/10$.\n\nThe last pair connect $10\\pi/10$ to $2\\pi/10$ and $12\\pi/10$ to 0.\n\nLocate these intersections along the rhombus edges, outer circles, and midpoints of those early horizontals that we drew. These six lines almost complete the pattern.\n\nAt this point, we can begin to pick out the pattern. Locate and outline the petals. The regular five-pointed stars should help guide you. Note that the sides of the petals follow the parallel lines we drew.\n\nLocate and outline the central 10-pointed star and the quarter stars in the corners. There are a couple line segments at the corners that we didn’t already have drawn in, but all of the vertices necessary to draw them in are there.\n\nIn order to fill in the last four petals, we need to find the indicated points on the pair of vertical parallels. One way to do this is to transfer the length of the edge of a star by centering the compass at the left vertex of the top center petal and setting the radius to the indicated inner star vertex. This radius can be transferred to the analogous points in the other three indicated locations.\n\nLocate and outline the final four petals. You’re done! 😊\n\nSupplies and Additional Resources\n\nThese are the supplies that I personally use most often in my drawing practice. I am not sponsored or compensated in any way for mentioning these products. I also make no claims that these are the best. Art supplies are very personal.\n\nCompasses:\n\nKeuffel and Esser bow compasses and beam compass (for drawing large circles with high precision)\n\nSmall (79mm drafting radius) Dorapasu compass\n(for drawing very small circles)\n\nKeuffel and Esser drop bow compass\n(for drawing very VERY tiny circles)\n\nFor my students and other beginners, I recommend the [Blick Masterbow](#), which is a sturdy little compass at a bargain.\n\nRulers:\n\nWestcott 12-inch quilting ruler\n(this is especially helpful for ensuring lines are parallel)\n\nAlvin 18-inch scratch-resistant clear acrylic ruler\n\n6-inch stainless steel ruler similar to this one\n(this is what I use in my tiny sketchbook)\n\nAlvin Lettering Guide\n(useful for thickening lines for weaving)\n\nPencils, etc.:\n\nStaedtler Mars Technico lead holder\n\nKoh-I-Noor 2.0mm 6H leads\n(I use these in all of my compasses and my lead holder)\n\nTombow MONO Zero eraser\n\nPentel Hi-Polymer Eraser\n\nPens:\n\nSakura Pigma Micron Graphic Pens in various sizes\n\nPaper:\n\nSpringhill 67lb (147GSM) 11”x17” Vellum Bristol Cover\n\nArches hot press watercolor paper\n\nColors:\n\nWinsor & Newton Cotman Sketcher’s Pocket Box watercolor half pan set\n\nArtify watercolor field sketch watercolor set\n(the brushes that came with this set are the ones I use most often)\n\nMozArt Komorebi metallic watercolor paint set\n\nZebra Midliners\n\nPrismacolor art markers\n\nPrismacolor colored pencils\n\nBooks:\n\nRuler & Compass by Andrew Sutton\n\nArts & Crafts of the Islamic Lands\n\nJay Bonner, Islamic Geometric Patterns\n\nDesigna: Technical Secrets of the Traditional Visual Arts\n\nYouTube channels:\n\nSamira Mian\n\nCon Regla y Compás (Manuel Martinez Vela)\n\nMohamad Aljanabi\n\nKamikyodai (Ricardo Hinojosa)\n\nFacebook Groups with patterns and tutorials:\n\nAlan Adams, Drawing Islamic Geometric Designs\n\nMohamad Aljanabi, Geometric Pattern School\n\nClasses:\n\nArt of Islamic Pattern\n\nPrince’s School of Traditional Arts\n\nMisc:\n\nPattern in Islamic Art (David Wade’s photo archive)\n\nTilingsearch.org (searchable pattern database)\n\nA.J. Lee, Islamic Star Patterns Notes\n\nThe Topkapi Scroll\n\nAbu al-Wafa’ Buzjani, A Book on Those Geometric Constructions Which Are Necessary for a Craftsman"},"books_score":{"kind":"number","value":0.4827086925506592,"string":"0.482709"}}},{"rowIdx":8687,"cells":{"content":{"kind":"string","value":"PROPERTY DESCRIPTION\n\nPrime Development Opportunity: 9.84 acres at the prominent intersection of Covell and Santa Fe, this site enjoys excellent visibility and high traffic volumes. The area is supported by a growing affluent demographic, enhancing its appeal. Whether you envision a single-tenant build-to-suit or a multi-tenant shopping center, this location offers versatile development potential.\n\nOFFERING SUMMARY\n\n| Sale Price: | $2,700,000 |\n|------------------------------|------------|\n| Price Per Usable Square Foot| $6.30/SF |\n| Lot Size: | 9.84 Acres |\n| Zoning | D-O (Suburban Office) |\n\nDEMOGRAPHICS\n\n| | 1 MILE | 3 MILES | 5 MILES |\n|------------------------|--------|---------|---------|\n| Total Households | 1,914 | 25,582 | 56,389 |\n| Total Population | 5,467 | 69,044 | 148,462 |\n| Average HH Income | $135,385 | $127,110 | $133,142 |\n\nLAND - SEC COVELL AND SANTA FE\n\nSEC W COVELL AND N SANTA FE, EDMOND, OK 73003\n\n9.84 Acres\n\nGEORGE WILLIAMS, CCIM\nemail@example.com\nO: 405.239.1270 C: 405.657.7800\n\nPAUL RAVENCRAFT\nfirstname.lastname@example.org\nO: 405.239.1220 C: 405.226.5467\n\nThe information contained herein is from sources deemed reliable. No representation is made to the accuracy herein. Photos herein are the property of their respective owners, and use of them without express written consent of the owner is prohibited.\n\nLAND - SEC COVELL AND SANTA FE\n\nSEC W COVELL AND N SANTA FE, EDMOND, OK 73003\n\nFlood Zone\n\nGEORGE WILLIAMS, CCIM\nemail@example.com\nO: 405.239.1270 C: 405.657.7800\n\nPAUL RAVENCRAFT\nfirstname.lastname@example.org\nO: 405.239.1220 C: 405.226.5467\n\nThe information contained herein is from sources deemed reliable. No representation is made to the accuracy herein. Photos herein are the property of their respective owners, and use of them without express written consent of the owner is prohibited.\n\n## Population\n\n| | 1 MILE | 3 MILES | 5 MILES |\n|------------------------|--------|---------|---------|\n| Total Population | 5,467 | 69,044 | 148,462 |\n| Average Age | 38 | 38 | 38 |\n| Average Age (Male) | 37 | 36 | 37 |\n| Average Age (Female) | 39 | 39 | 39 |\n\n## Households & Income\n\n| | 1 MILE | 3 MILES | 5 MILES |\n|------------------------|-----------|-----------|-----------|\n| Total Households | 1,914 | 25,582 | 56,389 |\n| # of Persons per HH | 2.9 | 2.7 | 2.6 |\n| Average HH Income | $135,385 | $127,110 | $133,142 |\n| Average House Value | $397,670 | $342,982 | $358,804 |\n\nDemographics data derived from AlphaMap\n\n05202024"},"books_score":{"kind":"number","value":0.4710749089717865,"string":"0.471075"}}},{"rowIdx":8688,"cells":{"content":{"kind":"string","value":"PDF Converter for SharePoint - User Guide\n\nMuhimbi Ltd\n\nVersion 11.1\n\nPurpose and audience of document\n\nThis document contains instructions about how to use the PDF Converter for SharePoint on a day by day basis as well as how to create workflows that utilise the PDF Converter.\n\nThe intended audience is any SharePoint user with the need to convert documents to PDF format, apply watermarks or PDF Security as well as power users who create workflows using Nintex and SharePoint Designer or who develop custom software.\n\nDisclaimer\n\n© Muhimbi. All rights reserved. No part of this document may be altered, reproduced or distributed in any form without the expressed written permission of Muhimbi.\n\nThis document was created strictly for information purposes. No guarantee, contractual specification or condition shall be derived from this document unless agreed to in writing. Muhimbi reserves the right to make changes in the products and services described in this document at any time without notice and this document does not represent a commitment on the part of Muhimbi in the future.\n\nWhile Muhimbi uses reasonable efforts to ensure that the information and materials contained in this document are current and accurate, Muhimbi makes no representations or warranties as to the accuracy, reliability or completeness of the information, text, graphics, or other items contained in the document. Muhimbi expressly disclaims liability for any errors or omissions in the materials contained in the document and would welcome feedback as to any possible errors or inaccuracies contained herein.\n\nMuhimbi shall not be liable for any special, indirect, incidental, or consequential damages, including without limitation, lost revenues or lost profits, which may result from the use of these materials. All offers are non-binding and without obligation unless agreed to in writing.\n\n# Contents\n\n1 Introduction 7\n 1.1 Available SharePoint Features 7\n 1.2 Supported document formats 9\n\n2 Converting documents using the SharePoint U.I. 10\n 2.1 Converting a single file 10\n 2.2 Converting an entire folder 11\n 2.3 Converting an entire document library 12\n 2.4 Writing the converted file to a different location 13\n 2.5 Working with the ‘Conversion Results’ screen 15\n\n3 Converting documents via a SharePoint workflow 16\n 3.1 Create and configure the Document Library 16\n 3.2 Create and configure the workflow 16\n 3.3 Testing the workflow 19\n\n4 Converting Documents using Nintex Workflow 20\n\n5 Converting Documents using a K2 workflow 25\n 5.1 Prerequisites 25\n 5.2 Creating the workflow using K2 Studio 25\n 5.2.1 Testing the Workflow 28\n 5.2.2 Troubleshooting 28\n 5.3 Creating the workflow using K2 Designer 29\n 5.3.1 Configuring SmartObjects 29\n 5.3.2 Creating the workflow 30\n 5.3.3 Testing the Workflow 33\n 5.3.4 Troubleshooting 33\n\n6 Converting Documents / web pages using hyperlinks 34\n\n7 Processing documents using Web Services 36\n\n8 Controlling which InfoPath views to Export to PDF 37\n 8.1 Use a special view for exporting to PDF 37\n 8.2 Determine at runtime which views to export 38\n 8.3 View prioritisation rules 38\n\n9 Cross-Converting between document types 39\n 9.1 Cross-Converting file types using SharePoint Designer 40\n 9.2 Cross-Converting file types using Nintex Workflow 41\n 9.3 Cross-Converting file types using a Web Service call 41\n 9.4 Convert InfoPath to MS-Word, Excel, XPS and PDF 42\n\n10 Merging multiple files into a single PDF 46\n 10.1 Merging files Using the SharePoint User Interface 46\n 10.2 Merging files Using a SharePoint Designer workflow 48\n 10.3 Merging files Using a Nintex workflow 51\n 10.4 Merging files Using a K2 workflow 53\n 10.4.1 Prerequisites 53\n 10.4.2 The Merge SmartObject Method 53\n 10.5 Merging files Using a web Service call 55\n\n11 Splitting PDFs into multiple documents 56\n 11.1 Splitting files Using a SharePoint Designer workflow 57\n 11.2 Splitting files Using a web Service call 58\n\n12 Converting HTML and web pages to PDF format 59\n 12.1 Manually converting a web page 59\n 12.2 Converting HTML / web pages using SPD Workflows 60\n 12.3 Converting HTML / web pages using Nintex Workflow 62\n 12.4 Converting HTML / web pages using a Web Service call 64\n 12.5 Inserting Page breaks when converting HTML to PDF 65\n\n13 Applying watermarks to documents 66\n 13.1 Applying Individual watermarks using SPD workflows 66\n 13.1.1 Text watermark 67\n 13.1.2 RTF watermark 67\n 13.1.3 Image watermark 68\n 13.1.4 PDF watermark 68\n 13.1.5 Rectangle watermark 68\n 13.1.6 Line watermark 69\n 13.1.7 Ellipse Watermark 69\n 13.1.8 QR Code Watermark 69\n 13.1.9 Barcode Watermark 70\n 13.2 Applying composite watermarks using SPD workflows 71\n 13.2.1 Watermark element 73\n 13.2.2 Text element 73\n 13.2.3 RTF element 74\n 13.2.4 Image element 75\n 13.2.5 QRCode element 76\n 13.2.6 LinearBarcode element 76\n 13.2.7 PDF element 77\n 13.2.8 Rectangle element 77\n 13.2.9 Line element 78\n 13.2.10 Ellipse element 78\n 13.3 Applying watermarks using Nintex Workflow 79\n 13.4 Applying watermarks using a webservice call 81\n 13.5 Automatically applying watermarks using the SharePoint UI 86\n 13.5.1 Configuring predefined watermarks at the Site Collection level 86\n\n| Section | Page |\n|------------------------------------------------------------------------|------|\n| 13.5.2 Configuring automatic watermarking at the List / library level | 87 |\n| 13.5.3 Merging dynamic data into watermarks | 88 |\n| 13.5.4 Specifying filtering criteria when automatically applying | 88 |\n| watermarks | |\n| 13.5.5 Filtering out system users (e.g. Search indexer) | 90 |\n| 13.5.6 Dealing with watermark errors | 90 |\n| 13.6 Watermarking field names | 92 |\n| 13.7 Embedding field codes in the Text element | 94 |\n| 14 Securing PDF, Word, Excel and PowerPoint Files | 95 |\n| 14.1 Secure files using SharePoint Designer Workflows | 95 |\n| 14.2 Secure Documents using Nintex Workflow | 98 |\n| 14.3 Securing Documents using the SharePoint User Interface | 99 |\n| 15 Carry out OCR (Optical Character Recognition) | 102 |\n| 15.1 Convert Images & Scans to Searchable PDFs | 102 |\n| 15.1.1 OCR files using SharePoint Designer workflows | 103 |\n| 15.1.2 OCR files using Nintex Workflow | 105 |\n| 15.1.3 OCR files using a web Service call | 107 |\n| 15.2 Extract text from image based content | 107 |\n| 15.2.1 Extract text using OCR and SharePoint Designer Workflows | 107 |\n| 15.2.2 Extract text using OCR and Nintex Workflow | 108 |\n| 16 Copying Metadata | 110 |\n| 16.1 Copying Metadata from SharePoint Designer Workflows | 110 |\n| 16.2 Copying Metadata using a Nintex Workflow | 111 |\n| 17 Building a Table Of Contents | 113 |\n| 17.1 Object Model | 113 |\n| 17.2 XML Source Data | 115 |\n| 17.3 XSL Transformation | 116 |\n| 17.4 Testing & Troubleshooting | 120 |\n| 17.5 Generating a TOC from a SharePoint Workflow | 120 |\n| 18 Compressing output files | 121 |\n| 18.1 Object Model | 121 |\n| 18.2 Specifying the options | 122 |\n| 18.3 Compression using Override XML | 123 |\n| 19 Extract Key-Value Pairs | 124 |\n| 19.1 Object Model | 124 |\n| 19.2 Extract Key Value Pairs using SharePoint Designer workflow | 125 |\n| 19.3 Extract Key Value Pairs using Nintex Workflows | 126 |\n| 19.3.1 Extract key-value pairs | 126 |\n| 19.3.2 Extract value for a key | 128 |\n\n| Section | Page |\n|------------------------------------------------------------------------|------|\n| 19.4 Expected Keys | 129 |\n| 19.5 CSV Output Warning | 129 |\n| 20 Extract Text | 130 |\n| 20.1 Object Model | 130 |\n| 20.2 Extract Text from PDF using SharePoint Designer workflow | 130 |\n| 20.3 Extract Text using Nintex workflows | 131 |\n| 21 Troubleshooting & Other common tasks | 133 |\n| 21.1 The PDF Converter functionality is not available | 133 |\n| 21.2 Converting documents takes a very long time | 133 |\n| 21.3 The PDF file does not look exactly the same as the source file | 134 |\n| 21.4 An evaluation message is displayed in the UI and converted documents | 134 |\n| 21.5 InfoPath Forms fail to convert | 134 |\n| 21.6 Converting file formats that are not supported | 134 |\n| 21.7 Nintex Workflow Activities are not working as expected after upgrading | 134 |\n| 21.8 Files uploaded via Windows Explorer do not trigger 'Insert' watermarks | 135 |\n| 21.9 'Watermark on Open' does not show watermarks | 135 |\n| 21.10 Changing the default merge bookmark and sort fields | 135 |\n| Appendix - Web Services Object Model | 136 |\n| Appendix - Merge codes | 137 |\n| Appendix - Override default conversion settings | 139 |\n| Appendix - Specifying path and file names | 150 |\n| Appendix - Watermark field matrix | 153 |\n| Appendix - Relevant articles on the Muhimbi Blog | 154 |\n| Appendix - Licensing | 156 |\n\n1 Introduction\n\nThis document describes how to use the PDF Converter for SharePoint on a day-by-day basis. The intended audience is any SharePoint user with the need to convert documents to PDF format, merge files, extract forms data, OCR images, apply watermarks or PDF security as well as power users who create workflows using Nintex and SharePoint Designer or who develop custom software.\n\nIt is assumed that the audience has some familiarity with SharePoint and have been given the proper privileges to write documents to a SharePoint site.\n\nFrom time to time, you will encounter screenshots of different SharePoint versions in this document. Unless mentioned otherwise usage of the PDF Converter is the same for all supported versions of SharePoint.\n\nPlease note that the functionality described in this document applies to the on-premises (SP2007-2019 & SE) versions of the PDF Converter for SharePoint. The functionality provided by the Online (App Store) based version of the software is largely identical but not always exactly the same. The Online / App Store version can be installed on-premises as well. For details see this blog post.\n\nFor more details about this product please see:\n\n1. Product Information: https://www.muhimbi.com/Products/PDF-Converter-for-SharePoint/\n2. Product Overview: https://www.muhimbi.com/guides/pdf-converter/\n3. Knowledge Base / Frequently Asked Questions: https://www.muhimbi.com/\n4. Release Notes: https://www.muhimbi.com/guides/pdf-converter/sharepoint/release-notes/\n5. Installation & Administration Guide https://www.muhimbi.com/guides/pdf-converter/sharepoint/\n6. Developer Guide: https://www.muhimbi.com/guides/pdf-converter-services/\n7. PDF Converter related content on the Muhimbi Blog: https://www.muhimbi.com/blog/\n\nTo keep on top of the latest news and releases, please subscribe to our blog or twitter feed at https://www.muhimbi.com/contact/.\n\n1.1 Available SharePoint Features\n\n*SharePoint Features* are plug-ins that allow new functionality such as PDF Conversion to be added to a SharePoint environment. Individual Features can be enabled or disabled by Site or Farm Administrators.\n\nThe following SharePoint Features come with the PDF Converter for SharePoint. For further details contact your SharePoint administrator or see section 2.2.3 in the Administration Guide.\n\n| Feature Name | Scope | Enabled |\n|---------------------------------------------------|-----------|---------|\n| Muhimbi.PDFConverter.Farm | Farm | V |\n| Enable the Workflow Activities and the Central Administration Configuration screen. |\n| Muhimbi.PDFConverter | Web App | V |\n| Add 'Convert to PDF' to context menus / ribbons for all site collections in the Web Application. |\n| Muhimbi.PDFConverter.Nintex.WebApp¹ | Web App | - |\n| Add Nintex Workflow actions on systems that have this third party product installed. |\n| Muhimbi.PDFConverter.Watermarker.UI.WebApp | Web App | - |\n| Enable the user interface for the automatic watermarking and security facilities on all site collections in the Web Application. |\n| Muhimbi.PDFConverter.Watermarker.Processor.WebApp | Web App | - |\n| Enable the automatic watermarking and security processing logic on all site collections in the Web Application |\n| Muhimbi.PDFConverter.Convert.Site | Site Coll.| - |\n| Add 'Convert to PDF' to context menus / ribbons for a single site collection. |\n| Muhimbi.PDFConverter.ConvertAndDownload.Site | Site Coll.| - |\n| Add the 'Download as PDF' option to the file's context menu. |\n| Muhimbi.PDFConverter.ConvertWebPage.Site | Site Coll.| - |\n| Add the 'Convert Page to PDF' option to the user's Personal Actions menu. |\n| Muhimbi.PDFConverter.Watermarker.UI.Site | Site Coll.| - |\n| Add the user interface for the automatic watermarking and security facilities to the site collection. |\n| Muhimbi.PDFConverter.API.WebApp | Web App | - |\n| Add K2 Prerequisites, Feature is only present on SharePoint 2007 and not needed by newer SharePoint versions. |\n| Muhimbi.PDFConverter.SP2013_WebFeature | Web | '-' |\n| Enable workflow actions for the optional Workflow Manager part of SharePoint 2013 and later versions. |\n\nThe *Muhimbi.PDFConverter* and *Muhimbi.PDFConverter.Convert.Site* features are identical with the exception of the scope. The *WebApplication* scoped feature is enabled by default and adds PDF Converter options to all site collections in the web application. If you prefer to enable PDF Conversion at the Site Collection level, then make sure the *WebApplication* scoped feature is\n\n---\n\n¹ Due to an issue with Nintex Workflow, please carry out an IISRESET after deactivating this feature.\n\ndisabled. Do not leave both features enabled at the same time to prevent duplicate menu options.\n\nThe same mechanism is used by the `Muhimbi.PDFConverter.Watermarker.UI.WebApp` and `Muhimbi.PDFConverter.Watermarker.UI.Site` Features. Use the ‘WebApp’ version of the Feature to enable it on all site collections. If you just wish to use it on a select number of site collections, then disable it at the Web Application level and enable it at the Site Collection level.\n\nPlease note that certain SharePoint Features have internal dependencies. For example, in order to enable the *Automatic PDF Processing User Interface* Feature at either the Site Collection or Web Application level, the *Automatic PDF Processor* Feature must be enabled first, which must be done at the Web Application level.\n\n### 1.2 Supported document formats\n\nThe PDF Converter for SharePoint supports the most common file formats including MS-Word, Excel, PowerPoint, InfoPath, MSG (email), Visio and Microsoft Publisher. Legacy file formats starting with Office 95 are supported as well as the latest formats used by Office 2019 / 365. Non MS-Office related file types such as HTML, AutoCAD and common image formats are supported as well.\n\nThe PDF Converter also supports output in non-PDF file formats. For details see Chapter 9 *Cross-Converting between document types*.\n\n| Format | Supported | Not Supported |\n|-------------------------|---------------------------------------------------------------------------|----------------------------------------------------|\n| MS-Word | doc, docx, docm, dot, dotx, dotm, rtf, txt, wps, xml, odt, ott, mht, html, htm, wpd | xltx, xltxm, xlt, txt (tab delimited), prn, slk, xlam, xla |\n| Excel | xls, xlsx, xlsm, xlsb, xml, csv, dif, ods, ots | potx, potm, pot, thmx, ppam, ppa |\n| PowerPoint | ppt, pptx, pptm, xml, odp, otp, pps, ppsx, ppsm | |\n| InfoPath | xml, infopathxml | |\n| Publisher | pub | |\n| Email | eml, msg | |\n| Visio & Vector formats | vsd, vdx, vdw, svg, svgz | |\n| HTML & Web pages | html, htm, mht and any url that returns HTML such as .aspx or .jsp. | |\n| Image formats | gif, png, jpg, bmp, tif, tiff | |\n| AutoCAD formats | dwg, dxf | |\n| Postscript | ps, eps | |\n| PDF | pdf, fdf, xfdf, xml | |\n\n---\n\n2 The AutoCAD converter has several automatic recolouring options. For details see *AutoCAD specific switches* in the Administration Guide, subsection *Tuning the Document Conversion Service*.\n\n2 Converting documents using the SharePoint U.I.\n\nThe PDF Converter for SharePoint is a friendly and intuitive application. This chapter describes the available functionality in more detail.\n\n2.1 Converting a single file\n\nTo convert a single file to PDF format, follow the steps outlined below:\n\n1. Navigate to the Document Library and folder the file is located in.\n2. Open the context menu (See screenshot below) and select ‘Convert to PDF’.\n\n3. Review the settings and click the ‘Convert’ button to start the conversion process.\n4. Verify the file has been converted without errors.\n5. Click the ‘Destination Library’ to go to the directory that holds the converted PDF file.\n\nWhen using the PDF Converter in combination with SharePoint 2010 (or later) then a selection of files and folders can be converted / merged by selecting them and choosing *Convert to PDF* in the Ribbon.\n\nIf the `Muheimbi.PDFConverter.ConvertAndDownload.Site` Feature is enabled on a site collection then a *Download as PDF* option is added to both the SharePoint ribbon as well as the file Context Menu.\n\n*Download as PDF* works similar to *Convert to PDF* except that it opens / downloads the PDF file on the local machine rather than saving it to SharePoint.\n\n### 2.2 Converting an entire folder\n\nConverting an entire folder to PDF format works similar to converting a single file:\n\n1. Navigate to the Document Library that contains the folder to convert.\n2. Open the context menu (See screenshot below) and select ‘Convert to PDF’.\n\n3. Specify if you want to convert subfolders as well. Note that this may take a long time depending on how many files are in the folder hierarchy.\n\n4. Review the other settings and click the ‘Convert’ button to start the conversion process.\n\n5. Verify the files have been converted without errors.\n\n6. Click the ‘Destination Library’ to go to the directory that holds the converted PDF files.\n\nAlthough the Convert to PDF function works fine with folders, the Download as PDF feature cannot be used on folders.\n\n2.3 Converting an entire document library\n\nAlthough it is possible to convert an entire document library in one go, it may take a long time to complete, or even time out, if it contains many files. You will automatically receive a warning if there are many files in the library.\n\nConvert the entire document library as follows:\n\n1. Navigate to the root folder of the document library to convert.\n\n2. Select ‘Convert to PDF’ from the Actions menu (SP2007 only, see screenshot below).\n\n3. Specify if you want to convert subfolders as well.\n\n4. Review the other settings and click the ‘Convert’ button to start the conversion process.\n\n5. Verify the files have been converted without errors.\n\n6. Click the ‘Destination Library’ to go to the directory that holds the converted PDF files.\n\nPlease note that this menu option is not available in SharePoint 2010 or later. Select all files and use the ‘Convert to PDF’ option in the Ribbon instead.\n\n2.4 Writing the converted file to a different location\n\nBy default, PDF files are written to the same folder the source files are located in. However, it is possible to specify a different folder, different document library, different site or even a different site collection to write the converted PDF files to.\n\nTo specify a different folder, open the *PDF Conversion* screen and specify the destination folder. When the site is hosted on SharePoint server, rather than the free Foundation server, then a user-friendly *Browse* button is available which allows folders or sites to be selected within the current site collection.\n\n*Browse for a destination folder (Commercial versions of SharePoint only)*\n\nIf the *Browse* button is not available, or the destination folder is located in a different site collection, then the destination path will need to be entered manually. The format is as follows:\n\n1. A folder in the current site collection: *Document Library Name/Folder path*. E.g.,\n - Shared Documents/PDF Files\n\n2. A folder in the different site collection: *Absolute path to Site Collection/Document Library Name/Folder path*\\(^\\text{3}\\). E.g.\n - /sites/Press Office/Shared Documents/PDF Files\n\nFor more details about specifying paths see *Appendix - Specifying path and file names*.\n\n\\(^{3}\\) Please do not include ‘http://’ and the domain name in the absolute path. Absolute paths always start with ‘/’. For details see *Appendix -*.\n\nIf the files are always written to the same directory, then it may be a good idea to click *Remember this path* to automatically default to whatever custom path was last entered. Note that these settings are remembered per user and stored at the Site collection level.\n\nClearing the *Remember this path* checkbox will automatically forget the settings during future conversions.\n\nPlease note that *Document Sets* can be used as a source as well as a destination for PDF Conversion. They work exactly the same as folders.\n\n2.5 Working with the ‘Conversion Results’ screen\n\nThe Conversion Results screen contains functionality to simplify dealing with a large number of converted documents.\n\nThe following features are available:\n\n1. **Filter by column**: Click on the header of the column to filter on and select the value to filter for. For example, select ‘Error’ in the ‘Status’ column to generate an overview of all files that caused an error during the conversion process.\n\n2. **Sort by column**: Click on the header of a column to sort its contents either in Ascending or Descending order. For example, click on the ‘Source Path’ column to group all documents by folder.\n\n3. **Jump to destination folder**: Click the ‘Destination Library’ button to navigate to the folder the PDF file was written to. This is particularly useful when a different destination folder has been specified during the conversion process.\n\n4. **Page through results**: A pager is automatically displayed when more than 100 files have been converted.\n\n3 Converting documents via a SharePoint workflow\n\nThe PDF Converter for SharePoint comes with a number of *Workflow Activities* including one that can be used to convert documents as part of a SharePoint Designer (SPD) workflow. What follows is an example of how to create a simple workflow in SharePoint Designer, which converts a file to PDF format as soon as it has been approved.\n\nThe legacy SharePoint 2007 / 2010 workflow engine is fully supported, as is the optional *Workflow Manager* that comes with SharePoint 2013 and later versions. For details see [this post](#).\n\nBefore you start, make sure the PDF Converter for SharePoint has been installed and you have access to a site collection with the appropriate rights to create workflows. Some basic knowledge about creating and configuring document libraries is assumed.\n\nAnother, even more basic, example can be found [in our Knowledge Base](#).\n\n### 3.1 Create and configure the Document Library\n\n1. Create a document library named *Important Documents*.\n2. Once created, enable *Requires content approval* on the library’s *Settings > Document Library Settings > Versioning Settings* screen.\n3. In the document library, create two folders: *Confidential Proposals* and *Approved PDF Files*.\n\n### 3.2 Create and configure the workflow\n\n1. Start SharePoint Designer and open the site collection that contains the *Important Documents* library.\n2. From the File menu select *New > Workflow*.\n3. On the first screen of the Workflow wizard, specify the following settings:\n a. Name the workflow *Convert Approved documents to PDF Format*.\n b. Select the *Important Documents* list.\n\n \n\n c. When creating a SharePoint Designer Workflow in SharePoint 2013 or later then please select the appropriate *Platform Type*.\n\nd. Select the 2nd and 3rd checkboxes to make sure the workflow is triggered whenever a document is created or (its status) is updated.\n\ne. Click the Next button to proceed.\n\n4. We are now ready to create the workflow. From the ‘Conditions’ menu, select ‘Compare any data source’. This inserts the ‘If value equals value’ condition.\n\n5. Click on the first value followed by the display data binding (fx) button.\n\n6. Select Current Item as the Source and select Approval Status in the field. Click the OK button to continue.\n\n7. Click on the second value and select Approved from the list.\n\nTo avoid that the same workflow is executed on the converted PDF file after the conversion has taken place, we need to specifically exclude pdf files as follows:\n\n1. Add another Compare any data source condition.\n\n2. Click on the first value followed by the display data binding (fx) button.\n\n3. Select Current Item as the Source and select File Type in the Field. Click the OK button to continue.\n\n4. Click equals and change it to not equals.\n\n5. Click on the second value and enter pdf. (Do not prefix the extension with a period ‘.’).\n\nWith the Conditions in place, we can now add the Actions, which is where the magic happens.\n\n1. From the Actions menu, select Convert to PDF. It may be hidden behind the More Actions option.\n\n2. The following action is inserted:\n\n Convert this document to this url using the same file name and include / exclude meta data. Store the converted item details in List ID: Variable: List ID, Item ID: Variable: List Item ID.\n\nLet’s examine what the various options mean:\n\na. **this document**: Specify which document to convert. Select the option and make sure Current Item is selected.\n\nb. **this url**: Specify the location the converted file will be written to. The following options are available:\n\n i. Leave it empty: When no value is specified then the converted document is written to the same folder as the source file.\n\n ii. Site Relative URL\\(^4\\): By specifying a URL relative to the current site, e.g., subsite/shared documents/PDF Files, any folder location in the\n\n---\n\n\\(^4\\) For more details see 2.4 Writing the converted file to a different location.\n\ncurrent site collection can be targeted. **This is the option we want to use so enter ‘Important Documents/Approved PDF Files’**.\n\niii. Web Application relative URL\\(^5\\): Using a URL that is relative to the entire web application, e.g., `/sites/Press Office/Public Documents/To Distribute`, any folder location in any site collection can be targeted.\n\nFor more details see Appendix - Specifying path and file names.\n\nc. **the same file name**: The name of the converted file can be specified here. In our case we’ll leave it empty to make sure we use the same name as the original document.\n\nd. **include / exclude meta data**: In case of sensitive documents, we may want to strip any custom SharePoint columns from the file. Assuming that our document library contains a column *Yearly sales forecast*, we want to select *Exclude*.\n\ne. **Variable: List ID**: A new workflow variable named *List ID* is automatically created. After the file has been converted, this variable will contain the ID of the list the converted file was saved to. This can later be fed into another action in order to manipulate this file further.\n\nf. **Variable: List Item ID**: A new workflow variable named ‘List Item ID’ is automatically created. After the file has been converted, this variable will contain the ID of the item the converted file was saved to. This can later be fed into another action in order to manipulate this file further.\n\n3. Insert a new action named *Log to History List* and enter *File converted*.\n\n4. Insert a new action named *Update List Item* and click [this list](#). We are now going to automatically mark the converted PDF file as approved.\n\n a. From the *List* dropdown select *Important Documents*.\n\n b. Click the *Add* button and set the field to *Approval Status* and the value to *Approved*. Click *OK*. **Please note that behaviour has changed starting with SharePoint 2010. It is no longer possible to set the value of the ‘Approved’ field.**\n\n c. In the *Find the List Item* area set the field to *Important Documents:ID*.\n\n d. Click the *fx* button next to *Value*, specify *Workflow Data* as the Source and set the field to *Variable: List Item ID*. Click *OK*.\n\n e. Click *OK* again to return to the Workflow Designer. It should look like the image below.\n\n---\n\n\\(^5\\) Please do not include ‘http://’ and the domain name in the absolute path. Absolute paths always start with ‘/’. For details see Appendix - .\n\nClick the *Finish* button to activate the workflow.\n\n### 3.3 Testing the workflow\n\nThe workflow can be tested as follows: create or upload an MS-Word file to the *Confidential Proposals* folder. From the context menu select *Approve / Reject* and approve the file.\n\nThis will automatically start the workflow and after a few seconds the Workflow status should change to *Completed* as shown in the screenshot below.\n\nOnce the workflow has completed, you will find the PDF version of the document in the *Approved PDF Files* folder.\n\nIf an error occurs during the execution of the workflow, then have a look at the following:\n\n1. Check the messages on the workflow status screen.\n2. Look in the Windows Event log.\n3. Look in the SharePoint trace log.\n\n4 Converting Documents using Nintex Workflow\n\nThe Muhimbi PDF Converter for SharePoint comes with comprehensive support for all Nintex Workflow versions, currently NW2007 – NW2019.\n\nLet’s illustrate the power of these combined tools using an example that is very difficult to achieve in SharePoint designer: *Act on a set of list items*. In this example a workflow retrieves all files modified during the current day and converts them to PDF. Ideally you would schedule this workflow to run off-peak to batch process all new and modified files.\n\nPlease follow the instructions below or download the complete workflow in NWF format from the Muhimbi Blog at the following address:\n\nhttps://www.muhimbi.com/blog/how-to-use-nintex-workflows-to-convert-to-pdf/\n\nThe finished workflow\n\nPrerequisites\n\nBefore we start building the workflow, please make sure all prerequisites are in place. It is also assumed that the reader has some knowledge of building Workflows using Nintex Workflow.\n\n1. Make sure the PDF Converter for SharePoint version 4.1 (or newer) is installed in line with chapter 2 of the Administration Guide.\n\n2. Naturally Nintex Workflow will need to be installed as well.\n\n3. Make sure the `Muhimbi.PDFConverter.Nintex.WebApp` SharePoint Feature is activated on the relevant Web Application using SharePoint Central Administration.\n\n4. The user (you) will need to have the appropriate privileges to create workflows.\n\nCreating a new workflow\n\nTo get started, create a new workflow, and choose the *blank* template. Make sure the workflow doesn’t start automatically and add the workflow variables listed in the following screenshot.\n\nPlease make sure that the appropriate data types are assigned (They are listed between round brackets behind each variable name). The names are largely self-describing, but some additional information is provided below:\n\n- **Source Item ID**: By default, the item that triggered the workflow is converted to PDF format. However, as we are iterating over multiple items, we need to specify the ID of the item to convert in this variable. In SharePoint 2010 and later select *Integer* as the Type, not *List Item ID*.\n\n- **Source List ID**: The PDF Converter assumes the item that is being converted is located in the same list the workflow is attached to. However, if this is not the case then the ID (a GUID) of the list will need to be\n\nspecified as well. In this example everything is located in the same list, so this variable is not actually used.\n\n- **Source Files**: As we are potentially converting multiple files, we need to define a variable of type *Collection* to hold the list of files we’ll be iterating over.\n\n- **Generated PDF Item ID**: Once a file has been converted to PDF, you may want to carry out additional actions on this new file, for example checking it in. Once converted, the ID of the PDF is automatically stored in this variable. In SharePoint 2010 and later select *Integer* as the Type, not *List Item ID*.\n\n- **Generated PDF List ID**: As the PDF Converter allows files to be written to different document libraries, and even completely different Site Collections, you may want to know the ID of the destination list.\n\n**Adding the workflow actions**\n\nWe are now ready to add the actions to the workflow. Begin by adding a *Query List* action, which will allow us to retrieve all files modified today and store the results in the *Source Files* collection.\n\nPlease fill out the settings for this action as per the screenshot listed above. You may want to add an additional filter rule to check that *Content Type* is not equal to *Folder* or *Document Set*.\n\nContinue by adding the *For Each* action to the workflow. Specify the name of the collection to iterate over and the name of the variable to store the Item’s ID in.\n\nThe next set of actions will all need to be added *inside* the *For Each* action, to make sure they are executed separately for each file in the list.\n\nWe want to make sure that we only invoke the PDF Converter for files that are not already in PDF format, so add a condition and check that the file type equals ‘pdf’ as per the following screenshot.\n\nAdd the *Convert file to PDF* action listed under the *Muhimbi PDF* section to the *No* branch of the condition (type is not pdf). Fill it out as per the left most image in the following screenshot.\n\nThe PDF Converter integrates with all Nintex Workflow versions.\n\nYou may want to leave the *Destination Path* empty, which will write the PDF File to the same location as the source file. For more information about the *Destination Path* or any of the other fields, hover the mouse over the small information icons.\n\nThe workflow is now done. You may want to add some tracking information using the *Log In the History List* action. In our example we use the following 2:\n\n- Last action in the *No* branch:\n - List ID: {WorkflowVariable:Generated PDF List ID} - List Item ID: {WorkflowVariable:Generated PDF Item ID}\n\n- Last action in the *Yes* branch:\n - Already in PDF Format: {WorkflowVariable:Source Item ID}\n\n**Running the workflow**\n\nFinalise the workflow by saving and publishing it, after which it is ready to be executed.\n\nYou can either run the workflow manually or schedule it to run at a time of your choice.\n\nAn example showing how to use the output of one PDF Workflow Action as the input of the next Action [can be found on our blog](#).\n\n5 Converting Documents using a K2 workflow\n\nAs of version 7.3, the Muhimbi PDF Converter for SharePoint provides native support for the K2 workflow engine using K2’s SmartObjects technology. This chapter describes how to create a basic workflow to convert documents to PDF using K2 Studio (See 5.2) as well as K2 Designer (See 5.3).\n\nA note on licensing the Muhimbi PDF Converter for SharePoint when used in combination with K2 blackpearl. Muhimbi’s licensing model is very simple, if a server runs Muhimbi Software in any way shape or form, then it requires a license. Even though the PDF Conversion engine may be installed on a non-K2 server, all K2 Servers run our SmartObjects and therefore require a license. For details, in plain English, about how Muhimbi’s software is licensed, see this Knowledge Base Article.\n\n5.1 Prerequisites\n\nBefore creating the workflow, please make sure Muhimbi’s K2 Integration facilities have been deployed as described in the Administration Guide, Appendix – Deploying K2 Integration facilities. Basic knowledge of creating workflows in K2 Studio / Designer, and having the privileges, is assumed.\n\nThis tutorial was written for SharePoint 2010. Muhimbi’s PDF Converter for SharePoint integrates equally well with other SharePoint versions, but the actual steps for creating K2 workflows differ in each SharePoint version, particularly in SharePoint 2013 and later. Please refer to K2’s tutorials and documentation for your particular environment.\n\n5.2 Creating the workflow using K2 Studio\n\nIn this tutorial we will use K2 Studio to create a basic workflow to convert files to PDF and associate the workflow with a Document Library named Tutorial.\n\n1. Create a new Document Library named Tutorial.\n\n2. Launch K2 Studio and create a new project of type K2 Process using template Blank Process. Save it in a location of your choice.\n\n3. In the workflow editor select Process Wizards in the left-hand pane and drag the SharePoint Events Process onto the design surface.\n\n4. Click Next in the wizard and then, in the Action screen, select the Events for List and Library Items option.\n\n5. On the Connection Settings screen specify the URL of your site collection, browse to the Tutorial Document Library and click Next.\n\n6. In the Events Selection screen select Item Updated. Although we could select the Item Added option as well to automatically convert new documents, that would require additional logic to see if the created type is of type PDF, which complicates this workflow and is beyond the scope of this tutorial. Click Next.\n\n7. This tutorial does not require any of the item’s Metadata, so click Finish to complete the wizard.\n\n8. Using the Event Wizards pane drag the SmartObject Event onto the design surface and click Next on the first screen of the Wizard.\n\n9. Enter *Convert Document* as the *Event Name* and click the ellipses (…) next to *SmartObject Method* to open the Context Browser.\n\n10. In the Context Browser Navigate to the *Environment* (the first) tab and select *SmartObject Server(s) / SmartObject Server / Muhimbi / Muhimbi Document Converter for SharePoint / Single Method / Convert Document* and click the *Add* button followed by the *Next* button.\n\n11. The Input Mapping screen shows the various properties supported by the *Convert Document* SmartObject.\n\n a. **Source URL**: The URL of the document to convert (See Appendix - Specifying path and file names), please make sure that the web application name (http://yourwebapp) IS NOT included in the URL. In this tutorial we are converting the document that started the workflow.\n\n i. Select *Source URL* and click the *Assign* button followed by the *Ellipses* button behind the *Value* field.\n\n ii. In the Context Browser select the *Process/Activity Data* tab (the 3rd one) and navigate to *XML Fields / [Your Project Name] / EventDetails / EventDetails / ListItemRelativeURL*. Click the *Add* button followed by *OK*.\n\n b. **Destination URL**: The optional path and file name of where the converted file will be written to. When left empty the converted file will be saved in the same folder as the source file using the same file name, just with the extension of the specified file type. This field uses the same format and rules as the Source URL field. In this tutorial we’ll\n\nleave this field empty. For details on what locations documents can be converted to and how to specify paths, please see Appendix - Specifying path and file names.\n\nc. **File Type**: The extension of the file type we are converting to. In this case assign the PDF value.\n\nd. **Optional Parameters**: The Muhimbi PDF Converter is a very powerful product that allows many different settings to be specified. It is not feasible to make all of these settings available via individual field mappings, which is why we have developed a special XML syntax to populate these parameters. For this tutorial leave this field empty, you can find more details in Appendix - Override default conversion settings. Please keep in mind that K2 Studio does not provide support for entering line breaks in SmartObject mappings, so we recommend creating this XML in a regular code editor (or Notepad) and copy it from there into the Optional Parameters field.\n\ne. **SharePoint Site URL**: Similar to K2’s other SharePoint SmartObjects and Wizards, you will need to specify the URL of the site collection the workflow is acting on. The steps are identical to specifying the Source Url, just select SiteURL from EventDetails.\n\nf. **Include Meta-Data**: In this example we wish to copy all meta-data available on the source document to the converted document. Please assign Yes to this field.\n\nPlease keep in mind that at the time of writing K2 Does not validate the values specified in YesNo fields, so pay extra attention when filling out this field.\n\nIn this tutorial we are not using the Return Mappings, so click Finish to close the wizard.\n\n12. We need to connect the Workflow Activity to the workflow. On the Design Surface right-click on the *Start* element and drag a line to the newly created activity.\n\n13. Click the *Deploy* button in the *Home* ribbon. Once the *Deploy Project Wizard* is displayed click the *Finish* button.\n\n5.2.1 Testing the Workflow\n\nVerify the workflow is working correctly by uploading an MS-Word (or Excel, MSG, TIFF, PowerPoint, or any of the many other formats we support) into the *Tutorial* Document Library. As we have configured the workflow to only trigger when a document is updated, either open the document and resave it, or update the document properties using the ribbon.\n\nIf all has been configured well and the workflow has been created correctly then, within a few seconds, a PDF copy of the source file should appear in the *Tutorial* library.\n\n5.2.2 Troubleshooting\n\nIf the workflow does not work correctly then either use the *Process Overview* report in *K2 Workspace* to drill down into the workflow, or - and this is what we like to do - insert an *E-Mail* event step before the *Convert Document* step and populate the email with the content of the various lookup fields. Sending an email to the originator makes it easy to verify that the workflow is actually running and get an overview of what is going on without having to dive into the *K2 Workspace Reports*.\n\n5.3 Creating the workflow using K2 Designer\n\nK2 blackpearl comes with a number of different workflow editors. The majority of K2 workflow designers will be most familiar with *K2 Studio*, but *Visual Studio* as well as web-based workflow editors are also available. This section describes how to create a basic workflow to convert documents to PDF using a *K2 Designer* workflow.\n\n5.3.1 Configuring SmartObjects\n\nThe Muhimbi PDF Converter for SharePoint is exposed, in K2, as a series of SmartObjects. By default, SmartObjects are not available for use in *K2 Designer*, an administrator must add them. The steps to do so are as follows:\n\n1. In the relevant Site Collection open *K2 Site Settings*. If this option is not available, then please make sure the relevant *K2 Designer* SharePoint Features have been enabled at the Site Collection and Site Level.\n\n2. Under *K2 Designer for SharePoint Management* select *Configure SmartObject Access*.\n\n3. If *Muhimbi Document Converter for SharePoint* is not already present in the list, click *Add new item*.\n\n4. In the Add SmartObject Window open the Muhimbi Folder and tick the box next to Muhimbi Document Converter for SharePoint.\n\n5. Under Advanced, select the option to Automatically create all methods and click Finish to complete the operation.\n\n5.3.2 Creating the workflow\n\nIn this tutorial we will create a basic workflow to convert files to PDF and associate the workflow with a Document Library. This workflow is similar to the one we built using K2 Studio (See 5.2), but as K2 Designer works slightly differently, we have to jump through some additional hoops.\n\n1. Create a new Document Library named Tutorial2 in a site collection of your choice.\n\n2. In the Tutorial2 Library, select the Library ribbon tab and click K2 Workflow.\n\n3. In the Welcome dialog, assuming it is displayed by default, select the Create a new workflow option.\n\n4. Name the workflow Tutorial2, accept the default settings and, as this tutorial does not need any of the other Wizard screens, click Finish.\n\n5. In order for a SmartObject to be able to convert a document a number of parameters are needed. These parameters (EventDetails.SiteURL and EventDetails.ListItemRelativeURL) are available from the Context Browser.\n\nin *K2 Studio*, but in *K2 Designer* we have to manually create them. The steps are as follows:\n\na. In *K2 Designer* select *File / Configure Workflow Settings / Data Fields*.\n\nb. Click the *Add* button and specify *SiteURL* as the name.\n\nc. Although we could use a complex regular expression to determine this value at run time, let’s keep it simple and specify the URL to the site collection as the Default Value. In our case [http://portal.denallix.com/](http://portal.denallix.com/) *(including the trailing slash!)*.\n\nd. Click *OK* and add another Data Field named *ListItemRelativeURL*.\n\ne. Accept the default settings, click *OK* and *OK* again to close the Data Fields dialog.\n\nf. Hover the mouse over the *Start* line in the designer, a button will appear, click it and confirm the question to add a new step.\n\ng. Select the *Workflow Steps* tab in the ribbon and drag the *Set Data Fields* activity onto the newly created step.\n\nh. We already know the *SiteURL*, but we need to calculate the value of the *ListItemRelativeURL* by taking *Document Context.Document URL* and removing the *SiteURL* from the beginning. This is not difficult, just a bit fiddly.\n\n i. In the Context Browser open *Inline Functions / Text* and drag the *Mid(Text,Start)* on top of *ListItemRelativeURL*.\n\n ii. In the Editor that is opened drag and drop *Document Context / Document URL* onto the *Text* field.\n\n iii. Drag and drop *Inline Functions / Text / Length* onto the Start field.\n\n iv. In the Editor that is opened drag and drop *Data Fields / Site URL* onto the *Text* field.\n\n v. Click *OK* in the various Edit windows and verify that the *Set Data Fields Wizard* looks as per the screenshot below.\n\n vi. Click Finish to continue.\n\n6. With the required data fields in place, select the SmartObjects tab and drag the Convert Document smart object onto the empty workflow container and fill out the fields:\n\na. **Source URL**: The URL of the document to convert. (See Appendix - Specifying path and file names, please make sure that the web application name (http://yourwebapp) IS NOT included. In this tutorial we use the previously calculated data field by dragging Context Browser / Data Fields / ListItemRelativeURL onto the SourceURL field.\n\nb. **SharePoint Site URL**: Similar to K2’s other SharePoint SmartObjects and Wizards, you will need to specify the URL of the site collection the workflow is acting on. The steps are identical to specifying the Source Url, just select SiteURL from Data Fields.\n\nc. **Destination URL**: The optional path and file name of where the converted file will be written to. When left empty the converted file will be saved in the same folder as the source file using the same file name, just with the extension of the specified file type. This field uses the same format and rules as the Source URL field. In this tutorial we’ll leave this field empty. For details see Appendix - Specifying path and file names\n\nd. **File Type**: The extension of the file type we are converting to. In this case assign the PDF value.\n\ne. **Include Meta-Data**: In this example we want to copy all meta-data available on the source document to the converted document. Please accept the default Yes value\n\nf. **Optional Parameters**: The Muhimbi PDF Converter is a very powerful product that allows many different settings to be specified. It is not feasible to make all of these settings available via individual field mappings, which is why we have developed a special XML syntax to populate these parameters. For this tutorial leave this field empty, you can find more details in Appendix - Override default conversion settings. Please keep in mind that K2 Designer does not provide support for entering line breaks in SmartObject mappings, so we recommend creating this XML in a regular code editor (or Notepad) and copy it from there into the Optional Parameters field.\n\nClick *Next* followed by *Finish*, this tutorial does not use the return properties.\n\n7. From the *File* option in the ribbon select the *Deploy* option. Click *Next* (twice) followed by *Finish*.\n\n5.3.3 Testing the Workflow\n\nVerify the workflow is working correctly by uploading an MS-Word file (or Excel, MSG, TIFF, PowerPoint, or any of the many other formats we support) into the *Tutorial2* Document Library and manually starting the workflow on the file. To manually start a workflow, in SharePoint open the context menu for the relevant file and select the *Workflows* option.\n\nIf all has been configured well, and the workflow has been created correctly then - within a few seconds - a PDF copy of the source file should appear in the *Tutorial2* library.\n\n5.3.4 Troubleshooting\n\nIf the workflow does not work correctly then either use the *Process Overview* report in *K2 Workspace* to drill down into the workflow, or - and this is what we like to do - insert a Send E-mail step between the *Set Data Fields* and *Convert Document* steps and populate the email with the content of the various data fields. By sending the email to *Context Browser / Workflow Context / Originator E-mail* it is easy to verify that the workflow is actually running and get an overview of what is going on without having to dive into the *K2 Workspace* Reports.\n\n6 Converting Documents / web pages using hyperlinks\n\nIn addition to generating PDF files manually, via workflows and web service calls, it is also possible to convert documents and web pages by simply invoking a URL. This functionality is particularly helpful if you want to place a link to a PDF copy of a file anywhere in a web page or in a Data View Web Part.\n\nThe latest version of this tutorial is available from the Muhimbi Blog at https://www.muhimbi.com/blog/convert-any-file-to-pdf-format-using-the-data-view-web-part-and-a-simple-hyperlink/\n\nThe URL is made up of the following elements:\n\n__layouts/Muhimbi.PDFConverter/Convert.aspx?Action=ConvertAndDownload&ListId=your_list_id&ItemId=your_item_id&ConversionURL=url_to_convert\n\n- **Action**: The action to carry out. Currently the only supported value is ConvertAndDownload.\n- **ListId**: The ID (GUID) of the list that contains the item to convert.\n- **ItemId**: The ID of the item to convert.\n- **ConversionURL**: A fully qualified URL of the web page to convert.\n\nPlease specify a combination of ListId / ItemId or the ConversionURL. Mixing these parameters is not allowed.\n\nThe best way to illustrate how this can be used is by example. In this example we want to make sure that users cannot see the original source files as we don’t want them to have access to these documents. Instead, they can access each file via a special hyperlink that downloads the document in PDF format.\n\nThis can be achieved in many ways, but in this demonstration, we use SharePoint’s Data View Web Part to automatically generate a list of documents and link each document to the ConvertAndDownload facility. Some familiarity with SharePoint Designer and the DVWP is assumed.\n\nTo implement the solution, carry out the steps below:\n\n1. Make sure you have access to a Site Collection, a Document Library named Shared Documents and a web part page to insert the DVWP on (We use the home page named default.aspx).\n2. Start SharePoint Designer and open the Site Collection to work in.\n3. Open the web page to add the DVWP to, in our case default.aspx.\n4. Select a Web Part Zone to add the DVWP to and choose Insert Data View from the Data View menu.\n5. From the newly opened Data Source Library click the Shared Documents Library and select Show Data.\n\n6. In the newly opened *Data Source Details* tab select *Name* (and any other fields you may be interested in) and choose *Multiple Items View* from the *Insert Selected Fields as…* dropdown menu.\n\n7. Any available documents are automatically listed. Click the name of one of the documents followed by the ‘>’ menu. Change *Format as Text* to *Format as Hyperlink*.\n\n8. The previous action opens the *Edit Hyperlink* screen. Enter the following information in exactly this sequence:\n\n a. **Address:**\n ```\n _layouts/Muhimbi.PDFConverter/Convert.aspx?Action=ConvertAndDownload&ListId={$ListID}&ItemId={@ID}\n ```\n\n b. **Text to display:** `{@FileLeafRef}`\n\n9. After closing the *Edit Hyperlink* screen, you will most likely see an error about the *ListID* variable not being recognised. Choose *Parameters* from the *Data View* menu to automatically create this ListID parameter and immediately close the *Data View Parameters* screen using the *OK* button.\n\nThat is all. Click *Save* in SharePoint Designer and open / refresh the page in your web browser. Click on a document’s link to convert it to PDF format and open it in your browser.\n\n7 Processing documents using Web Services\n\nThe Muhimbi PDF Converter for SharePoint ships with a powerful, yet friendly, web services interface for integration in your own applications. This same web service is leveraged by all of Muhimbi's SharePoint front end facilities so literally all functionality is exposed this way.\n\nFull code samples for converting, watermarking, securing and OCRing documents are out of the scope of this document. However, full details are available at the following resources:\n\n1. Document: [Developer Guide](#)\n2. Blog Post: [Converting Documents using a web service call](#) (.NET)\n3. Blog Post: [Converting Documents using a web service call](#) (Java WSimport)\n4. Blog Post: [Converting Documents using a web service call](#) (Java Axis2)\n5. Blog Post: [Converting Documents using a web service call](#) (VS2005)\n6. Blog Post: [Converting Documents using a web service call](#) (PHP)\n7. Blog Post: [Converting Documents using a web service call](#) (Ruby)\n8. Blog Post: [Watermarking sample](#) (.NET)\n9. Blog Post: [Watermarking sample](#) (Java)\n10. Blog Post: [PDF Merging sample](#) (.NET)\n11. Blog Post: [PDF Merging sample](#) (Java)\n12. Blog Post: [Split PDF sample](#) (.NET)\n13. Blog Post: [OCR Images / scanned files to PDF](#) (.NET)\n14. Blog Post: [OCR Images / scanned files to PDF](#) (Java)\n15. Blog Post: [Convert PDF to PDF/A using a web service call](#).\n16. Blog Post: [Specifying PDF Viewer Preferences](#).\n17. Blog Post: [Set PDF Version, enable Fast Web Views, embed / strip fonts](#).\n18. Blog Post: [Adding a Table Of Contents](#).\n\nMore information and samples can be found [in the Muhimbi Knowledge base](#).\n\n8 Controlling which InfoPath views to Export to PDF\n\nBeing able to select which views to export is very useful as quite often different views are used for exporting a form to PDF. Sometimes using the Print View is good enough, but other times you need to export a different view or multiple views to PDF format. There are even occasions where different views are exported depending on the state of the data entered in the form.\n\nAs always, the best way to illustrate this is by example.\n\nThe latest version of this tutorial is available on the Muhimbi Blog. For details about how to specify the view using a workflow see this blog post.\n\n8.1 Use a special view for exporting to PDF\n\nIn this scenario we have an Employee Review form with the following 3 views:\n\n1. **Data entry view**: A view used for populating data using the InfoPath client or Forms Services. This is the default view.\n\n2. **Print View**: A special view that is optimised for printing to a network laser printer. This is specified as View 1’s Print View.\n\n3. **PDF Export view**: A separate view that is used to export the InfoPath form to PDF format as it contains some information that should only show up in exported PDF files.\n\nAs View 1 is the default view and View 2 is the Print View for View 1, under normal circumstance the 2nd view is used for exporting to PDF. However, we want to use View 3 for this purpose. We can achieve this by starting the name of View 3 with “_MuhimbiView”. The Muhimbi PDF Converter will automatically detect all views that start with this name, export them all and merge them together into a single PDF file. Naturally these views can be hidden from the end user by marking them as such.\n\nThis is a great solution if you know beforehand that you will always be exporting the same view(s) to PDF format.\n\n8.2 Determine at runtime which views to export\n\nThe previous solution, using view names that start with “_MuhimbiView”, works great. However, sometimes you need to export a different view depending on the state of the data.\n\nFor example, our Expense Claim form consists of the following Views:\n\n1. **Data Entry View 1**: Used by the employee to report expenses.\n2. **Data Entry View 2**: Used by the manager to add comments and additional information.\n3. **PDF Export View 1**: The view that is used to export the form to PDF format *before* the manager has reviewed the form.\n4. **PDF Export View 2**: The view that is used to export the form to PDF format *after* the manager has reviewed the form.\n\nWe can implement this by adding a (hidden) text box named “_MuhimbiViews” (case sensitive and using the default ‘my’ namespace) to any of the views and populating it with the name of one or more comma separated view names. The Muhimbi PDF Converter will automatically pick up these names and export them to PDF format. If multiple views are specified, then they are automatically concatenated together.\n\nIn addition to adding the “_MuhimbiViews” text field to the form, all the developer of the form needs to do is add a little bit of logic to the Submit event to specify in the “_MuhimbiViews” field which view name(s) to export.\n\n8.3 View prioritisation rules\n\nTo determine which view or views to export, the Muhimbi PDF Converter uses the following prioritisation rules:\n\n1. When using the web services interface, any *ConversionViews* specified in the *ConverterSpecificSettings* property will be converted. If this property is not set, then the following rules will be used to determine which views to convert to PDF.\n\n2. If a field named “_MuhimbiViews” is found anywhere in the InfoPath form, then the content of this field is used to determine which views to export.\n\n3. If the previous field does not exist, is empty or the specified view name does not exist then the converter looks at all view names that start with “_MuhimbiView”.\n\n4. If none of the previous options apply, then the view marked as the Default View is exported.\n\nRegardless of how a view or views are selected for export, if the selected view has a Print View specified than that view is given priority.\n\nDo not use Muhimbi’s View selection features in combination with InfoPath’s ‘Print multiple views’ facility. The latter is given priority when converting to PDF.\n\nWhen the final PDF file is assembled then all selected views are included first, followed by any *converted attachments*.\n\n9.1 Cross-Converting file types using SharePoint Designer\n\nConverting a document using SharePoint Designer workflows works similar to converting to PDF. The main difference is that for conversion to non-PDF formats the *Convert Document Workflow Activity* is used rather than the *Convert to PDF* one.\n\nAfter adding the new activity to a workflow, the following *Workflow Sentence* is displayed.\n\n```\nConvert this document to this file as a select file type, include / exclude meta data and use these optional parameters.\nStore the converted item details in List ID: Variable: List ID1, Item ID: Variable: List Item ID1\n```\n\nThe workflow sentence is consistent with Muhimbi’s other Workflow Activities and is largely self-describing.\n\n- **This document**: The document to convert. For most workflows selecting *Current Item* will suffice, but some custom scenarios (List or Site workflows) may require the look up of a different item.\n\n- **This File**: An optional filename (and path) to write the converted document to. When not specified, the same name as the document that triggered the workflow will be used, just with a different extension. *Please make sure that the path does not include the host name*, e.g., ‘http://your site/…’. For more details see Appendix - Specifying path and file names.\n\n- **Select file type**: Select the type to convert to from the drop-down menu.\n\n- **Include / exclude meta data**: In case of sensitive documents, you may want to strip any custom SharePoint columns from the file. For example, if your document library contains a column named ‘Yearly sales forecast’ then you may want to select ‘Exclude’.\n\n- **Optional parameters**: See Appendix - Override default conversion settings.\n\n- **Parameter ‘List ID’**: The ID of the list the converted file was written to. This can later in the workflow be used to perform additional tasks on the file such as performing a check-in or out.\n\n- **Parameter ‘List Item IDs’**: At the moment this workflow activity will always generate a single output file. However, in the future it will be possible to generate multiple output files in one go, in which case this parameter will return a string with ‘;’ separated values of the generated item IDs. This list can then be used by other (custom) activities to process the individual files further.\n\nA basic sample workflow is included below, by attaching this workflow to a Forms Library any InfoPath form saved in it will automatically be converted to an MS-Word 2007 file.\n\n```\nIf Current Item:File Type equals xml\n Convert Current Item to this file as a DOCX, Include meta data and use these optional parameters.\n Store the converted item details in List ID: Variable: List ID, Item ID: Variable: List Item ID\n```\n\n9.2 Cross-Converting file types using Nintex Workflow\n\nSimilar to Muhimbi’s other Nintex Workflow activities, the *Convert Document* activity integrates with Nintex Workflow at a deep level. It supports SharePoint 2007-2019, allows errors to be handled and even supports integration with Nintex’ iterators to deal with multiple items and loops.\n\nAs this Workflow Activity is similar to the generic PDF Conversion Activity it is worth looking at the example in Chapter 4 *Converting Documents using Nintex Workflow*. All parameters are identical with the following exceptions:\n\n- **Output Format**: This field is specific to the Convert Document activity and allows the output format to be specified, e.g., *doc*, *xls*, *pdf*, *txt*, *csv*, etc.\n\n- **Optional parameters**: See Appendix - Override default conversion settings.\n\n- **Output Item ID**: The type of this field is *Text* rather than *Item ID*. The reason for this is that a future version of the software may return multiple, comma separated, values for certain actions.\n\nPlease note that you may need to make some small modifications if you intend to convert InfoPath to Excel, HTML or MS-Word. For details see section 9.4 *Convert InfoPath to MS-Word, Excel, XPS and PDF*.\n\n9.3 Cross-Converting file types using a Web Service call\n\nConverting files to non-PDF formats using web service calls works identical to converting files to PDF. The only difference is that the *Format* property on the *ConversionSettings* object must be set to the file type you are converting to. For details see the existing *Convert to PDF* sample code in chapter 7 *Processing documents using Web Services*.\n\n9.4 Convert InfoPath to MS-Word, Excel, XPS and PDF\n\nThe PDF Converter’s cross-conversion facility opens up a whole new world of possibilities such as converting between DOC and DOCX, XLS and XLSX, but more importantly it also supports conversion between completely different document types such as Excel to MS-Word and HTML to Excel.\n\nThis section describes another new conversion type that should be of particular interest to InfoPath users as it is now possible to convert InfoPath forms to MS-Word, Excel and HTML.\n\nConversion to these new formats generally works very well, but there are some limitations due to the nature of these non-PDF based destination formats. Specifically:\n\n1. **Attachments**: When converting an InfoPath form to PDF the software also converts all attachments and merges them into the main PDF. This is possible because you can represent almost any file format in PDF and merge them together. Unfortunately, this is not possible when converting to HTML, MS-Word or Excel.\n\n2. **View Selection**: The software provides a number of ways to specify which view or views to convert (See chapter 8). When converting to PDF it is possible to specify multiple views, which the converter then merges together into a single document. When converting to HTML, MS-Word or Excel it is only possible to convert a single view as these file formats don’t support merging. As a workaround it is possible to create a ‘conversion specific view’ and combine the content of multiple views in it.\n\n Print Views are also ignored when converting to HTML, Word or Excel. Instead, you will need to use Muhimbi’s View Selection facilities if you wish to convert any view other than the default View.\n\n3. **Formatting**: PDF is a very flexible format that allows any content to be placed anywhere on the page. MS-Word, Excel and HTML are not necessarily this flexible. For example, Excel uses a ‘cell-based approach’ to display content. If an InfoPath form is not specifically designed for export to Excel, e.g., it uses nested tables or different column widths across a page, then you may need to optimise your InfoPath form for conversion or create a ‘conversion specific view’.\n\nSome hints and tips related to converting to the various non-PDF formats can be found below.\n\nInfoPath to HTML (MHT)\n\nWhen converting InfoPath to HTML the resulting file is a self-contained MHT file that most modern browsers can display. All information including images, HTML and style sheets are included in this single file.\n\nFrom left to right, the same Form in InfoPath, converted to PDF and converted to HTML\n\nAs this image shows, InfoPath data can be represented in HTML really well, so it is usually not needed to make any changes to the XSN file.\n\nInfoPath to MS-Word\n\nDepending on how an InfoPath form has been designed, some work may be required to make things look better when converting to MS-Word. This is mainly due to the fact that MS-Word does not like dimensions that are expressed in percentages, while it is common in InfoPath to create a table grid and populate that grid with controls that take up 100% of the available cell space.\n\nResults when converted to MS-Word before optimisation (left) and afterwards (right).\n\nLooking at the ‘before optimisation’ conversion results in the image displayed above, there are 2 things that stand out:\n\n1. **Dimension of text fields**: The dimensions of most text fields are not quite right. This can easily be changed by opening the form in InfoPath Designer and changing the width of the various fields from ‘100%’ to the actual dimensions in cm or inches.\n\n2. **Missing ‘year’ in date picker fields**: Due the way the Date Picker is structured internally, modifying its width does not translate properly when displayed in MS-Word. To solve this, change the date picker field to a regular text field either by creating a conversion specific view, or using a display rule.\n\nThe InfoPath to MS-Word facility can generate output in *doc*, *docx*, *rtf*, *txt*, *html* and *odt* formats.\n\nInfoPath to Excel\n\nInfoPath to Excel conversion for existing forms that are not optimised for conversion to Excel are probably the trickiest ones to get right. If the 'look and feel' of the Excel sheet is not important then no change is required. However, if the Excel forms need to 'look good' then you may need to rethink the way the form is designed.\n\nResults when converted to Excel before optimisation (left) and afterwards (right).\n\nLooking at the 'before optimisation' in the image above things don’t look too bad, but clearly it is not the same as the original. The main issues are as follows:\n\n1. **Column Widths**: As Excel uses a cell / grid based approach it is not possible to mix different column widths. The information in the form’s header requires different column width and spans than the columns used in the repeating table further down the page. By changing the horizontally oriented fields in the header to individual rows we no longer have this problem.\n\n2. **Number formats**: Depending on a cell’s content, Excel sometimes tries to be ‘clever’. Most of the time this works great, but in this case a field with value ‘007’ is changed into a ‘7’. This could be fixed by changing the content of the InfoPath field into a formula and concatenating an apostrophe in front of it.\n\nThe InfoPath to Excel facility can generate output in `xls`, `xlsx`, `csv` and `ods` format.\n\n10 Merging multiple files into a single PDF\n\nThe PDF Converter comes with the ability to merge multiple files, PDF or otherwise, into a single PDF file, either manually using SharePoint’s UI, via a SharePoint Designer workflow, a Nintex Workflow or via a Web Service call.\n\nFor details about starting each merged document on an *odd* or *even* page (for the purpose of double sided printing) see [this blog post](#).\n\n### 10.1 Merging files Using the SharePoint User Interface\n\nChapter 2 *Converting documents using the SharePoint U.I.* describes how to convert individual as well as multiple files to PDF format. When multiple input files are selected the default behaviour is to convert all files individually. However, clicking the ‘Merge Files’ option allows the files to be combined into a single PDF file as per the screenshot below.\n\nYou can specify the following options:\n\n- **Select the field to use for bookmarks:** If you wish you can automatically generate a PDF bookmark for each file that is merged. This makes navigating through the PDF file a lot easier. You can select any field defined on the document library or ‘— Empty —’ to skip the bookmarking process. The default field is ‘Title’, which usually contains the most descriptive data.\n\n- **Enabled / disable documents:** For each file you can specify if they should be included in the merged document or not. This can be very useful when selecting an entire folder to convert and merge.\n\nManually change bookmark text: Selecting a field to populate the bookmarks with will automatically generate the text for each file’s bookmark. However, if you wish you can manually change this value to anything you like. Please take into account that any manually entered values will be overwritten if you select a different bookmark field name.\n\nChange sequence of documents: By default, all documents are ordered by modification date, with the oldest one on top. You can change the sequence using the up and down arrows. It is also possible to select the name of the field to sort by, e.g., the creation date.\n\nInclude document bookmarks: Each source document may already have its own bookmarks, e.g., existing PDF Files or MS-Word headings. By default, these are all stripped out, but if you wish you can select to merge the bookmarks as well. For each document they will automatically be moved to sit underneath any custom bookmark name specified for the file.\n\nCopy meta-data source: Specify which file to copy the meta-data from to the generated PDF file.\n\nChange file name: As we are dealing with multiple files, we cannot use the name of the source file to generate the destination file name. For the merged file we default the file name to the name of the folder the files are located in. If the files are in the root folder, then we use the name of the Document Library. You can override the default generated name and select a different folder if needed as well.\n\nFurther operations such as applying watermarks and PDF security can be carried out as a post processing step using simple workflows.\n\nPlease note that the maximum number of files that can be merged is 200. You will automatically receive a warning message when this threshold is exceeded.\n\nFor details about changing the default PDF Bookmark and Sort fields see 21.10 Changing the default merge bookmark and sort fields.\n\n10.2 Merging files Using a SharePoint Designer workflow\n\nIn addition to being able to convert and merge files using the SharePoint user interface it is also possible to automate this activity using a SharePoint Designer Workflow.\n\nIn this section we’ll show how to create a workflow that automatically adds a cover page to a document whenever it is created or updated. If the document is not already in PDF Format, it will convert the file as part of the merging process as well. For a good introduction about using the PDF Converter in combination with SharePoint Designer workflows see chapter 3 *Converting documents via a SharePoint workflow*.\n\nThe SharePoint Designer Workflow Activity is named *Merge Documents into PDF*. After adding it to your workflow you will see the following *Workflow Sentence*.\n\n```\nMerge these documents to this file. Use this field for bookmark generation.\nStore the merged item details in List ID: Variable: List ID, Item ID: Variable: List Item ID\n```\n\nThe following fields are available:\n\n- **These Documents**: This field specifies the list of documents / URLs to merge (and convert if needed). Each file must be specified on a new line and each line may contain three ‘;’ separated values:\n - **File Path**: The path to the file to merge or URL of web page to convert. This may already be a PDF file, but if not – and the file format is supported by the converter – then it will be converted first. The path can be relative to the current site (e.g., *Shared Documents/Some File.docx*) or absolute (e.g., *sites/Finance/Shared Documents/Some Folder/Some file.docx*). SharePoint Designer Workflow Lookups are fully supported, which can be used to dynamically generate the path for the current file, e.g. [%Current Item:URL Path%]. In *SharePoint 2010 (and later)* always use forward slashes in your file path. When specifying a file, please make sure the path does not include the host name, e.g. ‘http://your site/…’. If you wish to convert web pages then the path MUST start with http:// or https://.\n - **Include Bookmarks**: The source file may already include PDF Bookmarks or may be able to generate such bookmarks as part of the conversion process, e.g., an MS-Word file. Specify *true* to copy these bookmarks to the merged PDF file, or *false* to strip out any bookmarks. This value is optional.\n - **Custom Bookmark value**: This field parameter (see below for details) can be overridden using the third parameter. Specify the name of the ‘top level bookmark’ for the file, specify “” to remove the bookmark for this document or don’t specify anything at all to use the value stored in the column referenced by the *this field* parameter. For an example see the exercise below.\n\n• **This File**: An optional filename (and path) to write the merged document to. When not specified, the same name as the document that triggered the workflow will be used with a '.pdf' file extension. Please make sure the path does not include the host name, e.g. 'http://your site/...'. For details see Appendix - Specifying path and file names.\n\n• **This Field**: In a way similar to the User Interface for the merge facility (see 10.1), it is possible to specify a name of the column which contents will be used to populate the PDF Bookmark for the merged document. For example, specifying *name* or *title* makes it very easy to jump between the various sections of the merged PDF file.\n\n• **Start Page (Each Document)**: Control if empty pages are added between documents to make sure each merged document always starts on the right-hand, or left-hand side when printing it double sided.\n\n• **Variable: List ID**: If you wish to carry out further actions on the generated PDF file, e.g., perform a check-in, then you can optionally write the ID of the List the PDF was written to in a workflow variable.\n\n• **Variable: List Item ID**: Similarly, to *List ID*, the Item ID of the generated PDF file can optionally be written to a workflow variable.\n\nLet's create a sample to automatically add a cover page to each document. In this example we will use SharePoint Designer 2010, but the steps for SharePoint Designer 2007 & 2013 are nearly identical.\n\n1. Make sure you have the appropriate privileges to create workflows on a site collection.\n\n2. Create, or navigate to, the Document Library that will be used for this workflow and add a simple MS-Word file named *cover page.docx*. This file can be in any format and, if its content is static, it is recommended to use a PDF file for this purpose so it doesn't need to be converted repeatedly for every merge operation.\n\n3. Open SharePoint Designer, open the relevant Site, create a new workflow, associate it with the Document Library used in step #4 and enable all *Start Options* to make sure the workflow is triggered when an item is created or updated.\n\n4. Add a condition to check that the *type* property of the current item does not equal *pdf*. Otherwise, the workflow will recursively trigger whenever the merged file is written to the same document library.\n\n5. Add the *Merge Documents into PDF* workflow Action and click the *these documents* parameter.\n\n6. Add a line for the location of the cover page, note that our Document Library is named *Automatic Merging*. There is no need to specify the optional *Include Bookmark* and *Custom Bookmark* values, although you can if you wish to.\n\n7. The second file to merge is the one that triggered the workflow. Position the cursor on the 2nd line of the String Builder and click the *Add or Change Lookup* button. Select *Current Item* as the *Data Source* and *URL Path* as the *Field from source*. Click *OK* to close the ‘Lookup for String’ window. We want to include the source document’s bookmarks so enter “;true” at the end of the second line.\n\nYour *String Builder* should now look similar to the screenshot under step #5. Click *OK* to accept the changes.\n\n8. In this example we want the (merged) output file to use the same name and path as the source file that triggered the workflow, so there is no need to change the “this file” parameter.\n\n9. Click the “this field” parameter and select the field you wish to use for the content of the PDF Bookmarks. In this example we’ll select *Name*.\n\nWe are all done, publish the workflow and add an MS-Word file with the content to merge to the Document Library. After a few seconds a PDF file will be created consisting of the cover page and the content. Open the PDF file and use the Bookmark pane to quickly navigate to the start of the 2 documents.\n\n10.3 Merging files Using a Nintex workflow\n\nSimilar to all other Nintex Activities provided by Muhimbi, the *Merging files (and URLs) to PDF* activity integrates with Nintex Workflow at a deep level. It supports SharePoint 2007-2019, allows errors to be handled and even supports integration with Nintex’ iterators to deal with multiple items and loops. For a comprehensive example and details about how to enable the Nintex Workflow integration see Chapter 4. You may also want to look at section 0 for a tutorial about a similar SharePoint Designer workflow activity.\n\nThe fields supported by this Workflow Activity are as follows:\n\n- **Destination Path**: Enter the path to write the merged file to, either:\n - Leave it empty to use the same filename (and path) as the file that triggered the workflow.\n - A relative path to a subsite / document library / folder, e.g., *Shared Documents/Some Folder/Some File.pdf*.\n - An absolute path to a different site collection, e.g., */sites/Finance/Shared Documents/Some Folder/Some File.pdf*. Please make sure the path does not include the host name, e.g., ‘http://your site/…’. For details see *Appendix - Specifying path and file names*.\n\n- **Source Files**: This field specifies the list of documents to merge (and convert if needed). Each file must be specified on a new line and each line may contain three ‘;’ separated values:\n - **File Path**: The path to the file, or URL, to merge. This may already be a PDF file, but if not – and the file format is supported by the converter – then it will be converted first. The path can be relative to the current site (e.g., *Shared Documents/Some File.docx*) or absolute (e.g., */sites/Finance/Shared Documents/Some Folder/Some file.docx*). Nintex Workflow References are fully supported, which can be used to dynamically generated the path for the current\n\nfile, e.g. `{ItemProperty:FileLeafRef}`. Some string manipulation to generate the exact path to the file may be needed. *When specifying a file please make sure the path does not include the host name, e.g. ‘http://your site/…’.* When converting a web page then the path MUST start with http:// or https://.\n\n- **Include Bookmarks:** The source file may already include PDF Bookmarks or may be able to generate such bookmarks as part of the conversion process, e.g., an MS-Word file. Specify `true` to copy these bookmarks to the merged PDF file, or `false` to strip out any bookmarks. This value is optional.\n\n- **Custom Bookmark value:** The *Bookmark* field (see below for details) can be overridden using the third parameter. Specify the content of the ‘top level bookmark’ for the file, specify \"\" to remove the bookmark for this document or don’t specify anything at all to use the value stored in the content specified in the *Bookmark* field.\n\n- **Bookmark:** In a way similar to the User Interface for the merge facility (see 10.1), it is possible to specify a name of the column, or any kind of Nintex Reference, which contents will be used to populate the PDF Bookmark for the merged document. For example, specifying *Name* or *Title* (using the appropriate Nintex Workflow Syntax) makes it very easy to jump between the various sections of the merged PDF file.\n\n- **Start Page (*Each Document*):** Control if empty pages are added between documents to make sure each merged document always starts on the right-hand, or left-hand side when printing it double sided.\n\n- **PDF List ID:** If you wish to carry out further actions on the generated PDF file, e.g., merge additional documents or perform a check-in, then you can optionally write the ID of the List the PDF was written to in a workflow variable of type *String*.\n\n- **PDF List Item ID:** Similarly, to *PDF List ID*, the Item ID of the generated PDF file can optionally be written to a workflow variable of type *Item ID* (in SharePoint 2007) or *Integer* (in SharePoint 2010 and later versions).\n\n- **Source List ID & List Item:** The item that triggered the workflow is merged by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use the same data types as used by *PDF List ID* and *PDF List Item ID*.\n\n- **Error Handling:** Similar to the way some of Nintex’ own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi’s Workflow Activities allow the same. By default, this facility is disabled meaning that any error terminates the workflow.\n\n10.4 Merging files Using a K2 workflow\n\nThis section describes the *Merge Documents* method provided by Muhimbi’s K2 SmartObjects. For a detailed tutorial about how to use the PDF Converter from K2 see sections 5.2 (*K2 Studio*) and 5.3 (*K2 Designer*).\n\n10.4.1 Prerequisites\n\nBefore creating the workflow, please make sure Muhimbi’s K2 Integration facilities have been deployed as described in the Administration Guide, *Appendix – Deploying K2 Integration facilities*. Basic knowledge of creating workflows in K2 Studio / Designer, and having the privileges, is assumed.\n\n*This section was written based on SharePoint 2010. Muhimbi’s PDF Converter for SharePoint integrates equally well with other SharePoint versions, but the actual steps for creating K2 workflows differ in each SharePoint version, particularly in SharePoint 2013 and later. Please refer to K2’s tutorials and documentation for your particular environment.*\n\n10.4.2 The Merge SmartObject Method\n\nThe *Merge Documents* method can be added to a workflow by dragging the standard *K2 SmartObject* Event onto the workflow’s design surface. Use the SmartObject Wizard’s Context Browser to add *Environment tab / SmartObject Server(s) / SmartObject Server / Muhimbi / Muhimbi Document Converter for SharePoint / Methods / Merge Documents into PDF*.\n\n\n\n**Input Mapping**\n\n| Name | Type | Data Type | Required | Value |\n|--------------------|--------|-----------|----------|------------------------------|\n| SharePoint Site URL| Property| Memo | Yes | EventDetails_SiteURL |\n| Bookmark Field | Property| Memo | | Title |\n| Destination URL | Property| Memo | | Tutorial3/Merged.pdf |\n| Source Documents | Property| Memo | Yes | EventDetails_ListItemRelativeUR |\n\nSpecify the input mappings for this SmartObject method. These values are used by the service object before executing the method to pre-filter the results.\n\nThe fields are as follows:\n\n1. **SharePoint Site URL**: Similar to K2’s other SharePoint SmartObjects and Wizards, the URL of the site collection the workflow is acting on must be specified. This value can be hardcoded, but the better solution is to use the Context Browser to select the *Process/Activity Data* tab (the 3rd one) and navigate to *XML Fields / [Your Project Name] / EventDetails / EventURL*.\n\n2. **Bookmark Field**: In a way similar to our User Interface for merging file (See 10.1), it is possible to specify a column name which will be used to populate PDF Bookmarks. For example, specifying *Name* or *Title* makes it very easy to use a PDF Reader’s Bookmarks pane to navigate between the various sections of the merged PDF file.\n\n3. **Destination URL**: The path and file name to write the merged file to. For details about how to specify paths in Muhimbi’s software see *Appendix - Specifying path and file names*.\n\n4. **Source Documents**: This field specifies the list of documents to merge (and convert if needed). As *K2 Studio* does not support line breaks, files are separated using pipes (|) surrounded by a single space, each file may optionally contain three ‘;’ separated values:\n\n a. **File Path**: The path to the file, or URL, to merge. This may already be in PDF format, but if not – and the file format is supported by the converter – then it will be converted first. The path can be relative to the current site (e.g., *Shared Documents/Some File.docx*) or absolute (e.g., */sites/Finance/Shared Documents/Some Folder/Some_file.docx*). *When specifying a file please make sure the path does not include the host name*, e.g., ‘http://your site/…’. *When converting a web page then the path MUST start with http:// or https://*. For details about how to specify paths see *Appendix - Specifying path and file names*.\n\n b. **Include Bookmarks**: The source file may already include PDF Bookmarks or may be able to generate such bookmarks as part of the conversion process, e.g., an MS-Word file. Specify *true* to copy these bookmarks to the merged PDF file, or *false* to strip out any bookmarks. This value is optional.\n\n c. **Custom Bookmark value**: The *Bookmark Field* parameter (see above for details) can be overridden using the third parameter. Specify the content of the ‘top level bookmark’ for the file, specify “” to remove the bookmark for this document or don’t specify anything at all to use the value stored in the content specified in the *Bookmark* parameter.\n\nAlthough a merge list will typically be generated by looping over files using a workflow, the end result passed into the *Source Documents* field will look similar to:\n\n```\nShared Document/file1.docx | Shared Document/file2.pdf | ... etc\n```\n\nOr\n\n```\nSomeLib/file1.docx;true;Introduction | SomeLib/file2.msg;;Summary\n```\n\n10.5 Merging files Using a web Service call\n\nFor a detailed example about how to convert and merge multiple files using Muhimbi’s powerful web services interface see [this Knowledge Base article](#).\n\n11 Splitting PDFs into multiple documents\n\nThe PDF Converter comes with the ability to split PDF files up into multiple files using either a SharePoint Designer workflow or a Web Service call.\n\nThe key features of the PDF splitting facility are as follows:\n\n1. Split a single PDF file into one or more individual PDF files.\n2. Split based on the number of pages or PDF bookmarks.\n3. Automatically generate numbered file names using .NET’s formatting syntax, e.g. ‘split-{0:D3}.pdf’ will use 3 digits for the sequential numbers starting at ‘split-001.pdf’. When splitting by bookmark then an optional {1} parameter can be inserted in the file name to include the name of the bookmark as well.\n4. Can be combined in combination with other actions, e.g., convert & merge.\n\nA note about splitting based on bookmark levels: PDFs store bookmarks at the page level, so it is not clear on what part of the page a heading starts or ends. As a result, an extra page will always be exported for each file split based on bookmark levels.\n\nFor example, let’s assume the following document:\n\n- **Page 1**: Contains chapter 1 and sections 1.1. and 1.2.\n- **Page 2**: Contains the last paragraph of 1.2 and all of chapter 2.\n- **Page 3**: Contains Chapter 3.\n\nWhen splitting this document based on bookmarks using ‘1’ as the batch size then the following files will be created:\n\n- **File 1**: Contains page 1 and 2 as expected.\n- **File 2**: Contains pages 2 and 3 even though Chapter 2 is only really part of page 2. This is because there is no way to know if Chapter 2 runs over into page 3 or not.\n- **File 3**: Contains Chapter 3.\n\n11.1 Splitting files Using a SharePoint Designer workflow\n\nIn this section we’ll show how to use a SharePoint Designer Workflow to automatically split up an existing PDF file into multiple files containing 10 pages each. This is quite a common scenario for organisations that deal with massive documents who frequently split up these kinds of files in batches of 100 pages to keep the files manageable. If your document is using a format other than PDF, then make sure your use our Convert to PDF Workflow Activity first as described in section 3.\n\nThe SharePoint Designer Workflow Activity is named *Split PDF*. After adding it to your workflow you will see the following *Workflow Sentence*.\n\n```\nSplit this document to this file. Split by number of pages / bookmark level using batch size / bookmark level 0. Store the parts' details in List ID: Variable: List ID, Item IDs: Variable: List Item IDs\n```\n\nThe workflow sentence is consistent with our other Workflow Activities and is largely self-describing. The following fields are available:\n\n- **This document**: The document to split up. For most workflows selecting *Current Item* will suffice, but some custom scenarios may require a different item to be looked up. You may also want to check that the *file type* of the document is ‘pdf’ before trying to split it up.\n\n- **This file**: The name and location the split files will be written to are stored in this value. Leave this field empty to use the same folder and file name as the source file, but with sequential numbers added. However, you can optionally specify a path and / or filename template.\n\n - **Path**: Enter a path, including the Document Library and any folder names, to write the split files to. E.g., “shared documents/split files”. You can even specify a different site collection by starting the path with a ‘/’ (never start with ‘http:’!). When just specifying a path, without the file name, then make sure to use a trailing ‘/’.\n\n - **File Name**: The file name can be anything and allows the standard .NET string formatting facilities for numbering, e.g. ‘split-{0:D3}.pdf’ will use 3 digits for the sequential numbers starting at ‘split-001.pdf’. When splitting by bookmark then an optional {1} parameter can be inserted in the file name to include the name of the bookmark as well.\n\n- **Number of pages / bookmark level**: Specify if you wish to split based on the *number of pages* or the *level of the bookmark*.\n\n- **Batch size**: When splitting based on the number of pages then this parameter must be set to the maximum number of pages to include in each split file. When splitting based on the bookmark level then this parameter should contain the ‘depth’ at which to split. E.g., specify ‘1’ to split on top level chapters (Chapter 1, chapter 2, etc.) or a higher number to split at a deeper level (e.g., ‘2’ splits on Chapter 1, 1.1, 1.2, 2, 2.1 etc.)\n\n- **Output Parameter ‘List ID’**: The ID of the list the split files were written to. This can later in the workflow be used to perform additional tasks on the file such as performing a check-in or out.\n\nOutput Parameter ‘List Item IDs’: Unlike our other workflow activities, this parameter will return a string with ‘;’ separated values of the generated item IDs. This list can then be used by other (custom) activities to process the individual files further.\n\nWith all the theory out of the way, let’s create a simple example to split up PDF files in batches of 10 pages.\n\n1. Make sure you have the appropriate privileges to create workflows on a site collection.\n2. Create a new workflow using SharePoint Designer.\n3. Associate the workflow with the library of your choice. Do not tick any of the boxes next to the ‘Automatically start…’ options, we want to start this workflow manually. If you wish to run this workflow automatically then you may want to add an extra column to determine if a file has been split before, similar to the technique used in 14.1 Secure files using SharePoint Designer Workflows.\n4. Design the workflow as per the following screen. In summary it does the following:\n - Check if the file is in PDF format. Otherwise, it cannot be split.\n - The ‘split’ files are written to a folder named ‘Split Files’ so make sure this folder exists. e.g. “Shared Documents/Split Files/spf-{0:D5}.pdf”. You can leave our sample file name or merge the file’s name in using workflow lookups.\n - Log the generated list of Item IDs to the workflow history.\n\nPublish the workflow and create / convert / upload a PDF file in the document library. From the file’s context menu select ‘Workflows’ and run your workflow. Depending on the size of the document the split files will be generated in a matter of seconds.\n\n11.2 Splitting files Using a web Service call\n\nFor a detailed example about how to split PDFs into multiple files using Muhimbi’s powerful web services interface see this Knowledge Base article.\n\n12 Converting HTML and web pages to PDF format\n\nThe PDF Converter comes with the ability to convert HTML fragments as well as entire web pages to PDF format, either manually, via a SharePoint Designer workflow, Nintex Workflow or via a Web Service call. For details about troubleshooting HTML conversions, see:\n\n- [Converting HTML - Empty page / Authentication problems](#)\n- [Solving formatting issues when converting HTML to PDF](#)\n\n12.1 Manually converting a web page\n\nWhen the `Muhimbi.PDFConverter.ConvertWebPage.Site` feature is enabled on a site collection then an option to convert the current web page to PDF format is automatically added to the *Personal Actions* menu.\n\nSelect this option to convert the current page and download it as a PDF file. This is perfect for quickly saving a list or web page as a PDF file.\n\nThe default page size, orientation, margin, scale mode and many other settings can be tweaked in the service's config file. For details see *HTML Specific switches* in the *Administration Guide*, subsection *Tuning the Document Conversion Settings*.\n\n12.2 Converting HTML / web pages using SPD Workflows\n\nThe PDF Converter for SharePoint ships with a separate SharePoint Designer Workflow Activity that allows HTML fragments or web pages to be converted to PDF format. This chapter contains an example of how this functionality can be used to convert a SharePoint list to PDF format. This is only an example; the Workflow Activity can be used to convert any Web Page to PDF format and is not just limited to SharePoint pages\\(^6\\).\n\nThe latest version of this tutorial can be accessed from the Muhimbi Blog at https://www.muhimbi.com/blog/how-to-convert-sharepoint-list-to-pdf-in-sharepoint-designer/.\n\nIn this example we use a simple Tasks list, so open your SharePoint site and create a Tasks lists if one doesn’t already exist.\n\nNext up we need to create a page that displays all items in the list with as little of the SharePoint User Interface around it as possible. We could just use the list’s default view, but that would convert the Quick Launch menu to PDF as well, which doesn’t look very clean. To create a new page without the Quick Launch menu, follow these steps:\n\n1. Navigate to the View All Site Content screen and click the Create button.\n2. In the Web Pages column select Web Part Page.\n3. Name the page PDFTasks.aspx, choose the Full Page, Vertical template and click the Create button.\n4. On the newly created page click Add a Web Part and add the Tasks list.\n5. Click the newly inserted Web Part’s Edit button and select the Modify Shared Web Part option.\n6. Click Edit the current View and select the columns you want to be included in the PDF file. For example, % Complete, Due Data, Start Date and Status. Do not close the screen yet.\n7. Under the Item Limit section set the limit to an appropriately large number. We don’t want to page through the data in batches as we want to include all items in the PDF file.\n8. Click OK to save the changes.\n9. Save the page’s URL as we need it later. E.g. http://moss/sites/Management/FormServerTemplates/PDFTasks.aspx.\n\nThis new page will be used as the underlying layout for the PDF document. Feel free to modify it further in SharePoint designer / JQuery and remove more parts of the SharePoint user interface. You could also consider creating a minimalistic master page and applying that to the new PDFTasks page.\n\n---\n\n\\(^6\\) Please note that the default page size, orientation, margin and scale mode can be set in the Muhimbi Service’s config file. For details see HTML Specific switches in the Administration Guide, subsection Tuning the Document Conversion Settings.\n\nWith the page in place the next thing we need to do is setup the automatic PDF Conversion using a SharePoint Designer workflow. In this example we generate a PDF file whenever the Tasks list is modified. The generated PDF file will be stored in the *Shared Documents* library.\n\nCreate the workflow as follows:\n\n1. Make sure you have the appropriate privileges to create workflows on a site collection.\n2. Create a new workflow using SharePoint Designer.\n3. On the Workflow definition screen associate the workflow with the Tasks list, tick the boxes next to both ‘Automatically start…’ options and proceed to the next screen.\n4. Add the *Convert HTML to PDF* action and click on *this url* and enter the URL to the page that was created in a previous step, e.g., http://moss/sites/Management/FormServerTemplates/PDFTasks.aspx.\n5. Click *this file* and enter the path and file name where the PDF file will be generated, e.g. *Shared Documents/Tasks.pdf*. **Contrary to the *Convert to PDF* activity, the name of the Document Library must be included in the destination path.**\n6. Optionally change the generated page’s orientation from *Portrait* to *Landscape*.\n7. Optionally increase the *Conversion delay* to deal with JavaScript heavy pages, and the *Media Type* to make use of *Print* or *Screen* specific CSS.\n8. The *user name* and *password* fields are optional. By default, the credentials the *Muhimbi Conversion Service* runs under will be used to open the web page. For now, leave it empty.\n9. Click the *Finish* button to save and activate the workflow.\n\nAs a test enter one or more tasks. Every time a task is added or updated a PDF file is written to *Shared Documents/Tasks.pdf*. Open the PDF file to see the results.\n\n### 12.3 Converting HTML / web pages using Nintex Workflow\n\nSimilar to all other Nintex Activities provided by Muhimbi, the *HTML to PDF Conversion* activity integrates with Nintex Workflow at a deep level. It supports SharePoint 2007-2019, allows errors to be handled and even supports integration with Nintex’ iterators to deal with multiple items and loops. For a comprehensive example and details about how to enable the Nintex Workflow integration see chapter 4 *Converting Documents using Nintex Workflow*.\n\nThe fields supported by this Workflow Activity are as follows:\n\n- **Destination Path**: Enter the path to write the converted file to, either:\n - A relative path to a subsite / document library / folder, e.g., *Shared Documents/Some Folder/Some File.pdf*.\n - An absolute path to a different site collection, e.g., /sites/Finance/Shared Documents/Some Folder/Some File.pdf.\n\n*Always use forward slashes (‘/’) in path names.*\n\n- **Source URL / HTML**: Either a fully qualified URL of the page to convert or an HTML fragment.\n\n• **Page Orientation**: Specify if you wish to use *Portrait* or *Landscape* for the generated PDF file.\n\n• **Username**: By default, all pages are requested by the conversion service using the account the service is running under. If that account has no privileges on the requested URL then specify an alternative user name in this field.\n\n• **Password**: The password associated with the optional user name. Please note that any password entered here is displayed in clear text to allow field references to be added.\n\n• **Html Engine**: Specify which HTML conversion engine to use. *Chromium* (the default on most modern systems) generally produces better results, especially with SharePoint 2013 and later, but for some rare scenarios the WebKit option may work better.\n\n• **Authentication**: By default, the Muhimbi PDF Converter attempts to authenticate using standard Web / HTTP / Windows authentication. However, in order to convert SharePoint Online pages, a different authentication type will need to be specified.\n\n• **WebKit Viewport**: Control the ‘virtual browser size’ to improve the rendering of responsive websites. (e.g., distinguish between mobile, tablet and desktop versions of a website)\n\n• **Media Type**: HTML is primarily aimed at displaying information on screen, not on paper. However, modern web pages - including SharePoint - use CSS to define a different look and feel for the screen and the printer. Providing the default ‘WebKit’ based HTML Converter is used, the converter can use Print optimised CSS (the default) or Screen optimised CSS. (The IE based converter always uses the ‘Screen’ option).\n\n• **Conversion Delay**: Modern web pages, including SharePoint 2013 and later, as well as SharePoint Online, use complex methods for rendering pages, often involving JavaScript. Under normal circumstances the Muhimbi Converter will convert HTML to PDF the moment the page has finished loading. However, you may want to add some milliseconds (a value of 1000 is 1 second) to allow all JavaScript to finish executing.\n\n• **PDF List ID**: If you wish to carry out further actions on the generated PDF file, e.g., perform a check-in, then you can optionally write the ID of the List the PDF was written to in a workflow variable of type *String*.\n\n• **PDF List Item ID**: Similarly, to *PDF List ID*, the Item ID of the generated PDF file can optionally be written to a workflow variable of type *Item ID* (in SharePoint 2007) or *Integer* (in SharePoint 2010 and later versions).\n\n• **Error Handling**: Similar to the way some of Nintex’ own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi’s Workflow Activities allow the same. By default, this facility is disabled meaning that any error terminates the workflow.\n\n12.4 Converting HTML / web pages using a Web Service call\n\nHTML to PDF Conversion is accessible via the webservices based interface as well. The latest version of this tutorial is available from the Muhimbi Blog at https://www.muhimbi.com/blog/programmatically-converting-web-html-pages-to-pdf-format/\n\nExample of the original web page (left) and the converted PDF file (right)\n\nListed below is a simple C# example\\(^7\\) of how to carry out a conversion from your own code. The sample code is not complete as it calls into some shared functions from our main C# example to keep things short.\n\nOur existing Java based examples can easily be extended to carry out the same type of conversions.\n\n```csharp\n/// <summary>\n/// Simple sample to convert either a URL or HTML code fragment to PDF format\n/// </summary>\n/// <param name=\"htmlOnly\">A flag indicating if an HTML Code fragment (true)\n/// or URL (false) should be converted.</param>\nprivate void ConvertHTML(bool htmlOnly)\n{\n DocumentConverterServiceClient client = null;\n try\n {\n string sourceFileName = null;\n byte[] sourceFile = null;\n\n client = OpenService(\"http://localhost:41734/Muhimbi.DocumentConverter.WebService/\");\n OpenOptions openOptions = new OpenOptions();\n\n //** Specify optional authentication settings for the web page\n```\n\n---\n\n\\(^7\\) Please note that the default page size, orientation, margin and scale mode can be specified in the ConverterSpecificSettings property or in the Muhimbi Service’s config file. For details see HTML Specific switches in the Administration Guide, subsection Tuning the Document Conversion Settings.\n\nBoth C# and Java based sample code is available from the Windows Start menu as well.\n\n12.5 Inserting Page breaks when converting HTML to PDF\n\nThe Muhimbi PDF Converter supports HTML page breaks using the standard 'page-break-after' CSS syntax. For example:\n\n```html\n<html><body>\n<div style=\"page-break-after:always\">Page 1</div>\n<div style=\"page-break-after:always\">Page 2</div>\n</body></html>\n```\n\n13 Applying watermarks to documents\n\nThe Muhimbi PDF Converter for SharePoint contains a powerful watermarking engine that can be used to add watermarks to Word, Excel, PowerPoint and PDF files, including headers, footers, page numbering and other data. A good overview of watermarking MS-office file formats, as well as some caveats you should be aware of, can be found in this blog post.\n\nMultiple watermarks can be applied to the same page, and watermarks can be applied to page ranges, page intervals or certain page types such as portrait or landscape\\(^8\\). For each watermark it is possible to specify if it should always be displayed or only when printing\\(^8\\).\n\nThis chapter explains how simple and complex watermarks can be applied using SharePoint Designer workflows, Nintex Workflows, using the SharePoint User Interface as well as from your own code by invoking the PDF Converter’s web services interface.\n\nSection 13.6, Watermarking field names, contains an overview of the field names supported by the various watermarks. An overview of which fields are mandatory or optional for each of the possible watermark types as well as the possible values can be found in Appendix - Watermark field matrix.\n\n13.1 Applying Individual watermarks using SPD workflows\n\nThe Muhimbi PDF Converter comes with a number of watermarking related workflow actions for SharePoint Designer.\n\nThese workflow actions allow elements such as text, rectangles, images, PDF files, QR Codes, barcodes as well other shapes to be added to a document either in front of or behind the document’s content.\n\nEach separate watermark workflow action is applied to the document separately. If multiple watermarks need to be applied in one go then please have a look at the separate Composite Watermark described in section 13.2.\n\nThe individual workflow actions are self-describing, but the following elements require special attention:\n\n1. **this document**: The document to apply the watermark to. For most workflows selecting Current Item will suffice, but some scenarios require the lookup of a different item. You may also want to check that the file type of the document is supported (pdf, docx, xlsx, pptx).\n\n2. **this file**: The name and location of the watermarked file. Leave this field empty to overwrite the source file with the watermarked copy. Enter a path, including the Document Library and any folder names, to write the watermarked file to a separate location. E.g. “shared documents/watermarked files/confidential.pdf”\n\n3. **List ID**: The ID of the list the watermarked file was written to. This can later in the workflow be used to perform additional tasks on the file such as a check-in or out.\n\n---\n\n\\(^8\\) If supported by the underlying file format. PDF is the most flexible, some of the Office formats are more restricted.\n\n4. **Item ID**: The ID of the watermarked file. Can be used with the List ID.\n\n### 13.1.1 Text watermark\n\nThis workflow action can be used to apply text to the foreground or background of one or more pages in the document with full control over the font, style, size, and color.\n\nThe SharePoint Designer workflow action is named *Add Text watermark to Document* and the parameters are as follows:\n\nWatermark this document to this file. Add the text content to the Background, position Absolute (at 0, 0), size width x height, rotate 0°, opacity 100%, fill color #000000, line color #000000, line width 0. Apply on pages 0 to 0 every 0 page(s), page type Both. Use font Arial, size 12, style bold italic underline strikethrough, alignment Middle Center, word wrap Word only. Store the converted item details in List ID: Variable: List ID32, Item ID: Variable: List Item ID32.\n\nThe text stored in the content field may contain embedded field codes such as the date or current page number. For details see '13.7 Embedding field codes in the Text element'.\n\nSharePoint Designer lookup variables are also supported, which makes it possible for dynamic information stored in workflow variables, or in the Item’s columns, to be embedded in the watermark.\n\n### 13.1.2 RTF watermark\n\nThe RTF watermark allows simple RTF encoded text to be added as a watermark. This allows more control over the look and feel of individual words in the watermark at the cost of added complexity.\n\nAn example of valid RTF is as follows:\n\n```rtf\n{\\rtf1\\ansi{\\fonttbl\\f0\\fswiss Helvetica;}\\f0\\pard\nThis is some {\\b bold} text.\\par\n}\n```\n\nThe SharePoint Designer workflow action is named *Add RTF watermark to Document* and the parameters are as follows:\n\nWatermark this document to this file. Add rtf rtf_code to the Background position Absolute (at 0, 0), size width x height, rotate 0°, opacity 100%, fill color #ffffff, line color #000000, width 0. Apply on pages 0 to 0 every 0 page(s), page type Both. Store the converted item details in List ID: Variable: List ID31, Item ID: Variable: List Item ID31.\n\nNote that unlike the Text watermark, the RTF watermark does not support embedded field codes. However, SharePoint Designer lookup variables are\n\n---\n\n9 Please note that due to a bug in SharePoint 2010, lookup variables in RTF text may have unexpected side effects. SP2007 works fine.\n\nfully supported to make it possible for dynamic information stored in workflow variables, or in the item’s columns, to be embedded in the watermark.\n\nRTF Watermarks are displayed as plain text when applied to PowerPoint files.\n\n### 13.1.3 Image watermark\n\nUse the Image watermark to add common image types (BMP, JPG, GIF, PNG, TIFF, WMF, EMF / EMF+) as a watermark to a document.\n\nThe SharePoint Designer workflow action is named *Add Image watermark to Document* and the parameters are as follows:\n\nWatermark **this document** to **this file**. Add **image at this path** to the **Background**, position **Absolute** (at **0, 0**), size **width x height**, rotate **0 °**, opacity **100 %**, fill color **#000000**, line color **#000000**, line width **0**. Apply on pages **0** to **0** every **0** page(s) page type **Both**. Store the converted item details in List ID: **Variable: List ID27**, Item ID: **Variable: List Item ID27**\n\nThe *image at this path* parameter expects the full path of the image relative to the current site, e.g. ‘shared documents/images/company_logo.gif’.\n\n### 13.1.4 PDF watermark\n\nExisting PDF files can also be used as a watermark. This could be a dynamic file that is generated from, for example MS-Word, and then converted to PDF using the Muhimbi PDF Converter. Alternatively, this could be a static PDF file that has been generated manually.\n\nThe SharePoint Designer workflow action is named *Add PDF watermark to Document* and the parameters are as follows:\n\nWatermark **this document** to **this file**. Use the 1st page of **pdf file path** as watermark in **Background**, position **Absolute** (at **0, 0**), size **width x height**, rotate **0 °**, opacity **100**. Apply on pages **0** to **0** every **0** page, page type **Both**. Store the converted item details in List ID: **Variable: List ID29**, Item ID: **Variable: List Item ID29**\n\nThe *pdf file path* parameter expects the full path of the PDF name relative to the current site, e.g. ‘shared documents/static watermarks/company_logo.pdf’. Note that PDF based watermarks can only be applied to other PDF documents. It is not possible to apply a PDF Watermark to Office file formats.\n\n### 13.1.5 Rectangle watermark\n\nA simple rectangle can be added as a watermark using the *Add Rectangle to Document* workflow action. The parameters are as follows:\n\n13.1.6 Line watermark\n\nA line can be added as a watermark using the *Add Line to Document* workflow action. The parameters are as follows:\n\nWatermark *this document* to *this file*. Add line to the *Background* position *Absolute*, from *(0, 0)* to *(0, 0)*, rotate *0°*, opacity *100%*, line color *#000000*, line width *1*. Apply on pages *0* to *0* every *0* page(s), page type *Both*. Store the converted item details in List ID: *Variable: List ID28*, Item ID: *Variable: List Item ID28*\n\n13.1.7 Ellipse Watermark\n\nA circle or ellipse can be added as a watermark using the *Add Ellipse to Document* workflow action. The parameters are as follows:\n\nWatermark *this document* to *this file*. Add ellipse to the *Background*, position *Absolute* (at *0, 0*), size *width x height*, rotate *0°*, opacity *100%*, fill color *#000000*, line width *0*. Apply on pages *0* to *0* every *0* page(s), page type *Both*. Store the converted item details in List ID: *Variable: List ID26*, Item ID: *Variable: List Item ID26*\n\n13.1.8 QR Code Watermark\n\nA QR Code can be added as a watermark using the *Add QR Code Watermark to Document* workflow action.\n\nWatermark *this document* to *this file*. Add QR Code for *this content*, version *Auto*, input mode *Binary*, error correction level *Low* to the *Background*, position *Absolute* (at *0, 0*), size *width x height*, rotate *0°*, opacity *100%*, background color *#ffffff*, foreground color *#000000*. Apply on pages *1* to *1* every *1* page(s), page type *Both*.\n\nThe fields are as follows:\n\n- **Content**: The content to embed in the QR code. This will need to match the specified *input mode*.\n- **Version**: Over the years many different QR versions have been introduced. Select the one appropriate to your needs, either *Auto* or *Version01 – Version40*.\n- **Input mode**: Specify the appropriate mode for your content:\n - **Binary**: Any value including text, URLs etc.\n - **AlphaNumeric**: Numbers, (Upper case) characters and SPACE, $, %, *, +, -, ., /, :\n - **Numeric**: Numbers only\n- **Error correction level**: Select the appropriate level for your needs: *Low, Medium, Quartile, High*\n\n13.1.9 Barcode Watermark\n\nA number of different barcode types can be added as a watermark using the *Add Linear Barcode* workflow action.\n\nThe fields, specific to this watermark type, are as follows:\n\n- **Type:** The barcode type including *Codabar*, *Code 11*, Code 32, *Code 39*, *Code 93*, *Code 128* (A/B/C), *GS1-128*.\n\n- **Content:** The content for the barcode, please make sure that the specified content is compatible with the data that may be stored in the selected barcode type.\n\n- **Check digit:** If relevant to the barcode type, calculate and encode the check digit into the barcode.\n\n<watermark\n hPosition=\"left\"\n vPosition=\"top\"\n width=\"200\"\n height=\"200\"\n zOrder=\"-1\"\n rotation=\"-30\"\n opacity=\"15\"\n pageOrientation=\"both\">\n <text\n width=\"200\"\n height=\"200\"\n fillColor=\"#000000\"\n content=\"Insert 'modified by' field using SharePoint Designer\"\n fontFamilyName=\"Times New Roman\"\n fontSize=\"24\"\n fontStyle=\"bold|italic\"\n wordWrap=\"word\"\n />\n</watermark>\n\n<!-- ** Third watermark adds page numbering -->\n<watermark\n hPosition=\"right\"\n vPosition=\"bottom\"\n width=\"100\"\n height=\"40\"\n zOrder=\"1\"\n pageOrientation=\"both\">\n <text\n hPosition=\"left\"\n vPosition=\"top\"\n width=\"100\"\n height=\"40\"\n content=\"Page {PAGE} of {NUMPAGES}\"\n fontFamilyName=\"Arial\"\n fontSize=\"11\"\n hAlign=\"left\"\n vAlign=\"top\"\n />\n</watermark>\n\n</watermarks>\n\n13.2.1 Watermark element\n\nAs the previous example shows, the `watermarks` element may contain multiple `watermark` elements. This `watermark` element again can contain one or more individual shapes such as text and images.\n\nThe watermark element acts as a container that determines where the watermark will be located, on which pages, before or behind the text, opacity, print only, as well as which page orientations the watermark applies to.\n\nThe XML looks as follows\\(^{10}\\).\n\n```xml\n<watermark\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"required\"\n height=\"required\"\n zOrder=\"optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n pageOrientation=\"optional (portrait, landscape, both)\"\n startPage=\"optional\"\n endPage=\"optional\"\n pageInterval=\"optional\"\n pageRange=\"optional\"\n printOnly=\"optional (true, false)\"/>\n```\n\n13.2.2 Text element\n\nThis watermark can be used to apply text to the foreground or background of one or more pages in the target document, with full control over the font, style, size and color.\n\nThe XML looks as follows\\(^{10}\\):\n\n```xml\n<text\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"required\"\n height=\"required\"\n zOrder=\"optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n lineColor=\"optional\"\n lineWidth=\"optional\"\n fillColor=\"optional\"\n content=\"required\"\n fontFamilyName=\"optional\"\n fontSize=\"optional\"\n fontStyle=\"optional (regular, bold, italic, strikeout, underline)\"\n wordWrap=\"optional (none, character, word, wordonly)\"\n hAlign=\"optional (left, center, right, justify)\"\n vAlign=\"optional (top, middle, bottom)\" />\n```\n\n---\n\n\\(^{10}\\) Please omit any attributes marked as *optional* from your code when they are not needed. Leaving them in with the 'optional' text will cause an error.\n\nThe text stored in the `content` attribute may contain embedded field codes such as the date or current page number. For details see 13.7 *Embedding field codes in the Text element*.\n\nWhen a lot of content is anticipated then you may want to remove the `content` attribute and instead place it inside the `text` element, for example:\n\n```xml\n<text\n hPosition=\"optional (absolute, random, left, center, right)\"\n ... rest omitted\n>\n Your content goes here, use a CDATA section if needed.\n</text>\n```\n\nSharePoint Designer lookup variables are also supported, which makes it possible for dynamic information stored in workflow variables, or in the Item’s columns, to be embedded in the watermark.\n\n### 13.2.3 RTF element\n\nThe RTF watermark allows simple RTF encoded text to be added as a watermark. This allows more control over the look and feel of individual words in the watermark at the cost of added complexity.\n\nAn example of valid RTF is as follows:\n\n```rtf\n{\\rtf1\\ansi{\\fonttbl\\f0\\fswiss Helvetica;}\\f0\\pard\nThis is some {\\b bold} text.\\par\n}\n```\n\nThe XML looks as follows\\(^{11}\\).\n\n```xml\n<rtf\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"required\"\n height=\"required\"\n zOrder=\"optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n lineColor=\"optional\"\n lineWidth=\"optional\"\n fillColor=\"optional\"\n rtfData=\"required\"/>\n```\n\n---\n\n\\(^{11}\\) Please omit any attributes marked as *optional* from your code when they are not needed. Leaving them in with the ‘optional’ text will cause an error.\n\nWhen a lot of content is anticipated then you may want to remove the `rtfData` attribute and instead place it inside the `rtf` element, for example:\n\n```xml\n<rtf\n hPosition=\"optional (absolute, random, left, center, right)\"\n ...\n rest omitted\n>\n Your content goes here, use a CDATA section if needed.\n</rtf>\n```\n\nNote that unlike the Text watermark, the RTF watermark does not support embedded field codes. However, SharePoint Designer lookup variables are fully supported to make it possible for dynamic information stored in workflow variables, or in the Item's columns, to be embedded in the watermark.\n\nRTF Watermarks are displayed as plain text when applied to PowerPoint files.\n\n### 13.2.4 Image element\n\nUse the Image watermark to add common image types (BMP, JPG, GIF, PNG, TIFF, WMF, EMF / EMF+) as a watermark to a document.\n\nThe XML looks as follows\\(^{12}\\).\n\n```xml\n<image\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"optional\"\n height=\"optional\"\n zOrder=\"optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n lineColor=\"optional\"\n lineWidth=\"optional\"\n fillColor=\"optional\"\n imagePath=\"required\"/>\n```\n\nThe `image at this path` parameter expects the full path of the image relative to the current site, e.g. 'shared documents/images/company_logo.gif'.\n\n---\n\n\\(^{12}\\) Please omit any attributes marked as `optional` from your code when they are not needed. Leaving them in with the 'optional' text will cause an error.\n\n13.2.5 QRCode element\n\nA range of different QR Codes can be added to documents using watermarks, ideal for embedding the document ID, or any kind of other SharePoint metadata.\n\nThe XML looks as follows\\(^{13}\\):\n\n```xml\n<qrcode\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"optional\"\n height=\"optional\"\n zOrder=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n fillColor=\"#optional\"\n lineColor=\"#optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n text=\"required\"\n errorCorrectionLevel=\"optional (Low, Medium, Quartile, High)\"\n inputMode=\"required (Binary, AlphaNumeric, Numeric)\"\n version=\"optional (Auto, Version01, Version02, Version03\n ... Version40)\" />\n```\n\n13.2.6 LinearBarcode element\n\nA range of different barcodes can be added to documents, ideal for embedding tracking numbers, and other metadata.\n\nThe XML looks as follows\\(^{13}\\):\n\n```xml\n<linearBarcode\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"optional\"\n height=\"optional\"\n zOrder=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n fillColor=\"#optional\"\n lineColor=\"#optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n text=\"required\"\n barcodeType=\"required (Codabar, Code11, Code32, Code39,\n Code39Extended, Code93, Code93Extended, Code128,\n Code128A, Code128B, Code128C, GS1Code128)\"\n omitStartStopSymbols=\"optional\"\n disableCheckDigit=\"optional\"\n showCheckDigit=\"optional\"\n```\n\n---\n\n\\(^{13}\\) Please omit any attributes marked as *optional* from your code when they are not needed. Leaving them in with the 'optional' text will cause an error.\n\n13.2.7 PDF element\n\nExisting PDF files can also be used as a watermark. This could be a dynamic file that is generated from, for example MS-Word, and then converted to PDF using the Muhimbi PDF Converter. Alternatively, this could be a static PDF file that has been generated manually.\n\nThe XML looks as follows\\(^{14}\\):\n\n```xml\n<cpdf\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"optional\"\n height=\"optional\"\n zOrder=\"optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n lineColor=\"optional\"\n lineWidth=\"optional\"\n fillColor=\"optional\"\n pdfFilePath=\"required\"/>\n```\n\nThe `pdf file path` parameter expects the full path of the PDF name relative to the current site, e.g. 'shared documents/static watermarks/company_logo.pdf'.\n\nNote that PDF based watermarks can only be applied to other PDF documents. It is not possible to apply a PDF Watermark to Office file formats.\n\n13.2.8 Rectangle element\n\nA simple rectangle can be added as a watermark. The XML looks as follows\\(^{14}\\).\n\n```xml\n<rectangle\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"required\"\n height=\"required\"\n zOrder=\"optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n ...\n```\n\n---\n\n\\(^{14}\\) Please omit any attributes marked as `optional` from your code when they are not needed. Leaving them in with the 'optional' text will cause an error.\n\n13.2.9 Line element\n\nA line can be added as a watermark. The XML looks as follows\\(^{15}\\).\n\n```xml\n<line\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"required\"\n y=\"required\"\n endX=\"required\"\n endY=\"required\"\n zOrder=\"optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n lineColor=\"optional\"\n lineWidth=\"optional\"/>\n```\n\n13.2.10 Ellipse element\n\nA circle or ellipse can be added as a watermark\\(^{15}\\).\n\n```xml\n<ellipse\n hPosition=\"optional (absolute, random, left, center, right)\"\n vPosition=\"optional (absolute, random, top, middle, bottom)\"\n x=\"optional\"\n y=\"optional\"\n width=\"required\"\n height=\"required\"\n zOrder=\"optional\"\n scaleMode=\"optional (absolute, exactFit, maintainaspectratio)\"\n scaleX=\"optional\"\n scaleY=\"optional\"\n rotation=\"optional\"\n opacity=\"optional\"\n lineColor=\"optional\"\n lineWidth=\"optional\"\n fillColor=\"optional\"/>\n```\n\n---\n\n\\(^{15}\\) Please omit any attributes marked as *optional* from your code when they are not needed. Leaving them in with the 'optional' text will cause an error.\n\n13.3 Applying watermarks using Nintex Workflow\n\nSimilar to all other Nintex Activities provided by Muhimbi, the *Watermark Document* activity integrates with Nintex Workflow at a deep level. It supports SharePoint 2007-2019, allows errors to be handled and even supports integration with Nintex’ iterators to deal with multiple items and loops. For a comprehensive example and details about how to enable the Nintex Workflow integration see chapter 4 *Converting Documents using Nintex Workflow*.\n\nThe fields supported by this Workflow Activity are as follows:\n\n- **Destination Path**: Enter the path to write the watermarked file to, either:\n - Leave it empty to use the same filename (and path) as the file that triggered the workflow.\n - A file name, without the full path, to write a differently named file to the same location as the source file.\n - A relative path to a subsite / document library / folder, e.g., *Shared Documents/Some Folder/Some File.pdf*.\n - An absolute path to a different site collection, e.g., */sites/Finance/Shared Documents/Some Folder/Some File.pdf*. Please\n\nmake sure the path does not include the host name, e.g., ‘http://your site/…’. For details see Appendix - Specifying path and file names.\n\n- **Watermark type**: A number of different watermark types are supported. Unlike our individual SharePoint Designer workflow activities, all watermark types have been rolled up into a single Nintex Activity. The functionality is largely the same so have a look at section 13.1 for more details. The following watermark types are supported.\n\n - **Text**: Add a text-based watermark with full control over the font type, size, style, rotation and field codes such as {PAGE}. For details about field codes see Appendix - Merge codes\n - **PDF**: Add the first page of another PDF file as the watermark.(Not supported in Office file types)\n - **QR Code**: Add a QR Code as the watermark. For details about the various fields see 13.1.8 QR Code Watermark.\n - **Linear Barcode**: Add a barcode watermark. For details about the various fields see 13.1.9 Barcode Watermark.\n - **Image**: Use a BMP, JPG, GIF, PNG, TIFF, WMF or EMF / EMF+ file as a watermark.\n - **RTF**: Use RTF based text as a watermark.\n - **Ellipse**: Add an ellipse based watermark.\n - **Line**: Add a line based watermark.\n - **Composite**: For complex watermarks, or watermarks consisting of multiple elements such as line AND text AND images, use the Composite Watermark in combination with our XML based watermarking syntax. For details see section 13.2 Applying composite watermarks using SPD workflows.\n\n- **Display**: Either display the watermark Always, or only When Printing. (When supported by target file format)\n\n- **PDF List ID**: If you wish to carry out further actions on the watermarked file, e.g., send it by email or perform a check-in, then you can optionally write the ID of the List the file was written to in a workflow variable of type String.\n\n- **PDF List Item ID**: Similarly, to PDF List ID, the Item ID of the watermarked file can optionally be written to a workflow variable of type Item ID (in SharePoint 2007) or Integer (in SharePoint 2010 and later versions).\n\n- **Source List ID & List Item**: The item that triggered the workflow is watermarked by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use the same data types as used by PDF List ID and PDF List Item ID.\n\n- **Error Handling**: Similar to the way some of Nintex’ own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi’s Workflow Activities allow the same. By default, this facility is disabled meaning that any error terminates the workflow.\n\n13.4 Applying watermarks using a webservice call\n\nThe C# sample below shows how to decorate a document with the following watermarks:\n\n1. The word ‘Confidential’ in the background of the cover page.\n2. Page numbers in the right-hand side of the footer on all even pages.\n3. Page numbers in the left-hand side of the footer on all odd pages.\n\nThe sample code expects the path of the PDF file on the command line. If the path is omitted, then the first MS-Word file found in the current directory will be used.\n\nFollow the steps described below to create the sample watermarking application.\n\n1. Create a new Visual Studio C# Console application named Watermarking.\n2. Add a Service Reference to the following URL and specify ConversionService as the namespace\n\n http://localhost:41734/Muhimbi.DocumentConverter.WebService/?wsdl\n\n3. Paste the following code into Program.cs.\n\n```csharp\nusing System;\nusing System.Collections.Generic;\nusing System.Diagnostics;\nusing System.IO;\nusing System.ServiceModel;\nusing Watermarking.ConversionService;\n\nnamespace Watermarking\n{\n class Program\n {\n // ** The URL where the Web Service is located. Amend host name if needed.\n static string SERVICE_URL = \"http://localhost:41734/Muhimbi.DocumentConverter.WebService/\";\n\n static void Main(string[] args)\n {\n // ** The input file - the original MS-Word document that needs to be converted.\n string inputFilePath = args.Length > 0 ? args[0] : \"C:\\\\temp\\\\important.docx\";\n\n // ** The output file - the converted MS-Word document that contains the watermarks.\n string outputFilePath = \"C:\\\\temp\\\\watermarked.docx\";\n\n // ** The URL where the Web Service is located. Amend host name if needed.\n string serviceUrl = SERVICE_URL;\n\n // ** The service reference\n using (var client = new ConversionServiceClient(serviceUrl))\n {\n // ** The conversion request\n var request = new ConversionRequest\n {\n InputFile = inputFilePath,\n OutputFile = outputFilePath,\n WatermarkSettings = new WatermarkSettings\n {\n Confidential = true,\n PageNumbers = new PageNumberSettings\n {\n EvenPages = new PageNumberSetting { Side = PageNumberSide.Right, Position = PageNumberPosition.Footer },\n OddPages = new PageNumberSetting { Side = PageNumberSide.Left, Position = PageNumberPosition.Footer }\n }\n }\n };\n\n // ** Convert the document\n var result = client.Convert(request);\n\n // ** Print the result\n Console.WriteLine($\"Conversion result: {result.Status}\");\n }\n }\n }\n}\n```\n\n{\n DocumentConverterServiceClient client = null;\n\n try\n {\n // ** Determine the source file and read it into a byte array.\n string sourceFileName = null;\n if (args.Length == 0)\n {\n string[] sourceFiles = Directory.GetFiles(\n Directory.GetCurrentDirectory(), \"*.doc\");\n if (sourceFiles.Length > 0)\n sourceFileName = sourceFiles[0];\n else\n {\n Console.WriteLine(\"Please specify a document to convert and watermark.\");\n Console.ReadKey();\n return;\n }\n }\n else\n sourceFileName = args[0];\n\n byte[] sourceFile = File.ReadAllBytes(sourceFileName);\n\n // ** Open the service and configure the bindings\n client = OpenService(SERVICE_URL);\n\n //** Set the absolute minimum open options\n OpenOptions openOptions = new OpenOptions();\n openOptions.OriginalFileName = Path.GetFileName(sourceFileName);\n openOptions.FileExtension = Path.GetExtension(sourceFileName);\n\n // ** Set the absolute minimum conversion settings.\n ConversionSettings conversionSettings = new ConversionSettings();\n conversionSettings.Fidelity = ConversionFidelities.Full;\n conversionSettings.Quality = ConversionQuality.OptimizeForPrint;\n\n // ** Get the list of watermarks to apply.\n conversionSettings.Watermarks = CreateWatermarks();\n\n // ** Carry out the conversion.\n Console.WriteLine(\"Converting file \" + sourceFileName);\n byte[] convFile = client.Convert(sourceFile, openOptions, conversionSettings);\n\n // ** Write the converted file back to the file system with a PDF extension.\n string destinationFileName = Path.GetDirectoryName(sourceFileName) + @\"\\\\\" +\n Path.GetFileNameWithoutExtension(sourceFileName) + \".\" + conversionSettings.Format;\n using (FileStream fs = File.Create(destinationFileName))\n {\n fs.Write(convFile, 0, convFile.Length);\n fs.Close();\n }\n\n Console.WriteLine(\"File converted to \" + destinationFileName);\n\n // ** Open the generated PDF file in a PDF Reader\n Process.Start(destinationFileName);\n }\n catch (FaultException<WebServiceFaultException> ex)\n {\n Console.WriteLine(\"FaultException occurred: ExceptionType: \" +\n ex.Detail.ExceptionType.ToString());\n }\n catch (Exception ex)\n {\n Console.WriteLine(ex.ToString());\n }\n finally\n {\n\nCloseService(client);\n }\n Console.ReadKey();\n }\n\n /// <summary>\n /// Create the watermarks.\n /// </summary>\n /// <returns>An array of watermarks to apply</returns>\n public static Watermark[] CreateWatermarks()\n {\n List<Watermark> watermarks = new List<Watermark>();\n\n // ** Specify the default settings for properties\n Defaults wmDefaults = new Defaults();\n wmDefaults.FillColor = \"#000000\";\n wmDefaults.LineColor = \"#000000\";\n wmDefaults.FontFamilyName = \"Arial\";\n wmDefaults.FontSize = \"10\";\n\n // ***************** 'Confidential' Text *****************\n\n // ** 'Confidential' watermark for front page\n Watermark confidential = new Watermark();\n confidential.Defaults = wmDefaults;\n confidential.StartPage = 1;\n confidential.EndPage = 1;\n confidential.Rotation = \"-45\";\n confidential.Width = \"500\";\n confidential.Height = \"500\";\n confidential.HPosition = HPosition.Center;\n confidential.VPosition = VPosition.Middle;\n confidential.ZOrder = -1;\n\n // ** Create a new Text element that goes inside the watermark\n Text cfText = new Text();\n cfText.Content = \"Confidential\";\n cfText.FontSize = \"40\";\n cfText.Width = \"500\";\n cfText.Height = \"500\";\n cfText.Transparency = \"0.10\";\n\n // ** And add it to the list of watermark elements.\n confidential.Elements = new Element[] { cfText };\n\n // ** And add the watermark to the list of watermarks\n watermarks.Add(confidential);\n\n // ***************** Watermark for Odd pages *****************\n\n Watermark oddPages = new Watermark();\n oddPages.Defaults = wmDefaults;\n oddPages.StartPage = 3;\n oddPages.PageInterval = 2;\n oddPages.Width = \"600\";\n oddPages.Height = \"50\";\n oddPages.HPosition = HPosition.Right;\n oddPages.VPosition = VPosition.Bottom;\n\n // ** Add a horizontal line\n Line line = new Line();\n line.X = \"1\";\n line.Y = \"1\";\n line.EndX = \"600\";\n line.EndY = \"1\";\n line.Width = \"5\";\n\n // ** Add a page counter\n Text oddText = new Text();\n oddText.Content = \"Page: {PAGE} of {NUMPAGES}\";\n\noddText.Width = \"100\";\noddText.Height = \"20\";\noddText.X = \"475\";\noddText.Y = \"15\";\noddText.LineWidth = \"-1\";\noddText.FontStyle = FontStyle.Regular;\noddText.HAlign = HAlign.Right;\n\n// ** And add it to the list of watermark elements\noddPages.Elements = new Element[] { line, oddText };\n\n// ** And add the watermark to the list of watermarks\nwatermarks.Add(oddPages);\n\n// **************** Watermark for Even pages ****************\n\nWatermark evenPages = new Watermark();\nevenPages.Defaults = wmDefaults;\nevenPages.StartPage = 2;\nevenPages.PageInterval = 2;\nevenPages.Width = \"600\";\nevenPages.Height = \"50\";\nevenPages.HPosition = HPosition.Left;\nevenPages.VPosition = VPosition.Bottom;\n\n// ** No need to create an additional line, re-use the previous one\n\n// ** Add a page counter\nText evenText = new Text();\nevenText.Content = \"Page: {PAGE} of {NUMPAGES}\";\nevenText.Width = \"100\";\nevenText.Height = \"20\";\nevenText.X = \"25\";\nevenText.Y = \"15\";\nevenText.LineWidth = \"-1\";\nevenText.FontStyle = FontStyle.Regular;\nevenText.HAlign = HAlign.Left;\n\n// ** And add it to the list of watermark elements\nevenPages.Elements = new Element[] { line, evenText };\n\n// ** And add the watermark to the list of watermarks\nwatermarks.Add(evenPages);\n\nreturn watermarks.ToArray();\n}\n\n/// <summary>\n/// Configure the Bindings, endpoints and open the service using the specified address.\n/// </summary>\n/// <returns>An instance of the Web Service.</returns>\npublic static DocumentConverterServiceClient OpenService(string address)\n{\n DocumentConverterServiceClient client = null;\n\n try\n {\n BasicHttpBinding binding = new BasicHttpBinding();\n // ** Use standard Windows Security\n binding.Security.Mode = BasicHttpSecurityMode.TransportCredentialOnly;\n binding.Security.Transport.ClientCredentialType =\n HttpClientCredentialType.Windows;\n // ** Increase the client Timeout to deal with (very) long running requests.\n binding.SendTimeout = TimeSpan.FromMinutes(30);\n binding.ReceiveTimeout = TimeSpan.FromMinutes(30);\n // ** Set the maximum document size to 50MB\n binding.MaxReceivedMessageSize = 50 * 1024 * 1024;\n binding.ReaderQuotas.MaxArrayLength = 50 * 1024 * 1024;\n binding.ReaderQuotas.MaxStringContentLength = 50 * 1024 * 1024;\n\n4. Make sure the output folder contains an MS-Word file.\n\n5. Compile and execute the application.\n\n13.5 Automatically applying watermarks using the SharePoint UI\n\nAlthough applying watermarks programmatically or via a SharePoint Workflow can be very powerful, not everyone is a programmer, and many people may not actually have the relevant workflow tools such as SharePoint Designer installed on their system.\n\nFortunately, the PDF Converter for SharePoint allows watermarks to be applied using the standard SharePoint user interface. This powerful functionality allows watermarks to be applied to Documents and List Item attachments, and even supports the application of custom, user specific watermarks, when a document is opened, something that cannot be achieved by any other means.\n\nPlease note that by default the SharePoint screens associated with this watermarking facility are disabled. They can be activated by enabling the *Muhimbi PDF Converter - Automatic Document Processing User Interface Feature* at either the Web Application or Site Collection level (but not both).\n\n13.5.1 Configuring predefined watermarks at the Site Collection level\n\nTo allow the same watermarks to be shared between multiple lists and libraries, the system allows default watermarks to be specified at the Site Collection level using the *Site Actions / Watermarking Settings* screen.\n\n*Specifying ‘default watermarks’ does not automatically enable watermarking on a Library, that must be enabled separately, see 13.5.2.*\n\nA different default watermark can be specified for Insert, Update and Open watermarking events. It is even possible to lock down the look and feel of the watermarks to prevent them from being changed at the list or library level.\n\n13.5.2 Configuring automatic watermarking at the List / library level\n\nEven though default watermarks can be configured at the Site Collection level, the actual automatic watermarking must be enabled at the individual List or Library level. The relevant screen, Watermarking settings, can be opened from the List or Library’s settings screen.\n\nThe Settings screen allows automatic watermarking to be enabled for Insert\\(^{16}\\), Update and Open events. Each event type can use a separate watermark and selection filter (see 13.5.4). Different watermark types can be selected including Text, RTF, Image, PDF and Composite ones (see 13.2).\n\n---\n\n\\(^{16}\\) Due to limitations in SharePoint 2007, automatic watermarking for Insert and Update events are not supported on Document Libraries. They are supported on Lists and in SharePoint 2010. Use Workflows as an alternative (see 13.1)\n\n13.5.3 Merging dynamic data into watermarks\n\nThe watermarking framework provided by the PDF Converter for SharePoint comes with a powerful set of *merge codes* that allow dynamic data to be ‘merged in’ at run-time. For example:\n\n```\nPDF Opened by '{REMOTE_USER}' on '{LONG_DATE}' from IP '{REMOTE_ADDR}'\n```\n\nWhich results in the following watermark:\n\n```\nPDF Opened by 'MUHIMBIjeroen.ritmeijer' on '15 April 2011' from IP '192.168.1.248'\n```\n\nMerge codes are not exclusive to the ‘watermark on open’ functionality, there are several other ways that watermarks can be applied, for example using workflows (See 13.1) or web services (see 13.4). However, field codes are not always available for a particular interface as, for example, the web service has no knowledge about anything that happens in SharePoint, and workflows are not always associated with an HTTP Context. For a full overview of the available merge codes see Appendix - Merge codes.\n\n13.5.4 Specifying filtering criteria when automatically applying watermarks\n\nSimilar to the way SharePoint views can be filtered to only display certain list items, Muhimbi’s automatic watermarking facility allows filters to be created that determine which documents should be watermarked automatically, and which should not. The possibilities are endless, but some obvious examples are as follows:\n\n- Apply watermarks to *draft* documents, but not to *approved* documents.\n- Always apply watermarks to a document created by a user from a particular domain or authentication provider (e.g., FBA)\n- Watermark a document, based on the current date, for embargoed documents.\n- Enable watermarks on all documents with ‘Confidential’ in the Title.\n- Apply watermarks to *minor versions* (e.g., 1.3) of a document, but not to *major versions* (e.g. 2.0).\n- Only apply watermarks to certain content types.\n\nFortunately, this powerful functionality is very easy to use. Each watermarking section comes with a separate Filter that contains the following fields:\n\n- **Apply Filter**: A simple check box that allows filtering to be toggled. When disabled, watermarks are automatically added to all documents.\n\n- **Field List**: A list of fields that can be used to apply filters on e.g., Title, Author, Content Type, etc. This is a ‘sanitised’ list similar to the one displayed in SharePoint’s own View filter. Nonsensical ‘for internal use only’ fields are automatically stripped out.\n\n- **Comparison Type**: Specify the kind of comparison to use, e.g., ‘is equal to’, ‘is greater than’, ‘contains’, ‘begins with’ etc.\n\n- **Comparison Value**: The value(s) to compare the selected field with. Full details are provided below.\n\nIt is in the Comparison Value field where things become interesting as all comparisons take the underlying type of the column into account. All common data types are supported, specifically:\n\n- **Boolean**: True: True, Yes, -1, 1 and False, No, 0 as False.\n\n- **Currency**: Allows currency comparisons. Please use numbers only, do not specify the currency symbol.\n\n- **DateTime**: Allows date and time fields to be compared. Enter [Today] (including the square brackets) to compare a date field to the current date, e.g. to apply watermarks to documents modified today. Similarly [Now] can be used to compare a field with the current date and time.\n\n- **Lookup**: Compare lookup fields, including lookups that may contain multiple values.\n\n- **User**: Compares fields that contain a reference to a user account, e.g., the Modified By field. Filters of this type expect a value recognised by the underlying Authentication Provider. This will usually be in the ‘domain\\user_name’ format, but could also be ‘fbaprovdername:username’. Enter [me] (including the square brackets) to evaluate the field against the current user. This allows, for example, watermarks to be added to all documents not created by the current user.\n\n- **Single and Multiple choice fields**: Allows single and multiple values to be matched, particularly useful with the ‘contains’ comparison type. Examples and details are provided below.\n\n- **Numerical fields**: Carries out numerical comparisons.\n\n- **URL**: Can compare fields of type URL.\n\n- **Text**: Any text field or custom field type that uses a text-based representation.\n\nSome additional notes of interest:\n\n- All comparisons are case insensitive.\n- The filter for the ‘Version’ field accepts the `[MajorVersion]` and `[MinorVersion]` values to distinguish between a major (1.0, 2.0) and minor (1.1, 1.2, 2.2) versions. It also allows a specific version number to be specified.\n- When filtering multiple choice / multi select fields you can specify multiple values. For example:\n - \"Brett;Ben\" Contains \"Ben\" = True\n - \"Brett;Jeroen;Ben\" Contains \"Brett;Ben\" = True\n - \"Brett;Jeroen\" Contains \"Brett;Ben\" = False\n - \"Brett;Jeroen\" is equal to \"Jeroen;Brett\" = True (The sequence in which values are specified does not matter)\n- If a field is deleted from a list after it has been specified in a filter, then the filter will always equate to `false` resulting in the watermark not being applied.\n- It is not possible to specify a Filter for Insert events on a Document Library as the fields do not contain any values at this time. This is not a problem for inserting documents attached to a list.\n- When comparing fields that contain both Date and Time elements (e.g., the Modified Date) against such values as `[Today]` then please consider that the value represented by `[Today]` does not include a time element. Therefore 'Created Date = [Today]' will never evaluate to true unless it is midnight. Instead use 'Created Date >= [Today]'. For Date fields that don’t include the Time element, e.g. a birthday, this will not be a problem.\n\n### 13.5.5 Filtering out system users (e.g. Search indexer)\n\nWhen using the *Watermark On Open* facility on a list or library, watermarks are applied every time a file is opened, which is exactly what is expected. However, these watermarks are also applied when the SharePoint Search Indexer opens these files. This places excessive load on the system (bulk indexing results in bulk watermarking), so it is recommended to exclude certain accounts from the automatic watermarker.\n\nStarting with version 8.4 of the Muhimbi PDF Converter, a *PDF real-time settings* screen is available from the *Site Actions* menu. Enter a list of accounts to exclude, the *System account* is excluded by default.\n\n### 13.5.6 Dealing with watermark errors\n\nAutomatically watermarking documents works great, but in the real world you always have to cater for the worst possible situation. In some situations,\n\nwatermarks cannot be applied, either because the document is encrypted, corrupt, or an unexpected error occurs, e.g. a temporary network error.\n\nDepending on your exact requirements, you need to define how the system should behave under exceptional circumstances. Should the user still be given access to the document, even though watermarks could not be added, or should access to the document be blocked?\n\nStarting with version 10.0 of the Muhimbi PDF Converter, a *Real-time settings* screen is available from the *Site Actions* menu. Use this screen to specify if access to the document should be blocked in case of an error, or if the unprocessed (pre-watermarked) document should be passed to the user.\n\n**Opening PDF files**\n\nSpecify how to handle exceptional circumstances when files are opened from a list or library where watermarks or security settings are applied the moment a file is opened. This information can also be specified in bulk using PowerShell.\n\nFor details about how to apply Security to these dynamically watermarked files, see 14.3 *Securing Documents using the SharePoint User Interface*.\n\n13.6 Watermarking field names\n\nRegardless of the method chosen to apply watermarks, you will be presented with various watermarking options such as *EndPage*, *PageInterval*, *PageOrientation* etc. This section explains what each of these names mean.\n\nAn overview of which fields are mandatory or optional for each of the possible watermark types as well as the possible values can be found in Appendix - Watermark field matrix.\n\n| Name | Description |\n|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| EndPage | The last page the watermark applies to. Defaults to the last page. Use negative values to count from the back of the document (e.g. -1 is last page, -2 is second to last page). |\n| EndSection | For MS-Word, the index of the last section this watermark applies to. It is not possible to target individual pages in MS-Word files. |\n| EndX | The 2\\textsuperscript{nd} X-coordinate for the Line watermark. |\n| EndY | The 2\\textsuperscript{nd} Y-coordinate for the Line watermark. |\n| FillColor | The color of the element's fill in \\#rrggb\\textit{b} or \\#aarrggb\\textit{b} format where \\textit{aa} represents the alpha / transparency. |\n| FontFamilyName | The name of the font to use. When the font is not found the system will throw an exception. |\n| FontSize | The size of the font. |\n| FontStyle | The style of the text. Multiple values can be combined. |\n| HAlign | Horizontal alignment of text stored in a Text element. |\n| Height | The height of the element. Note that this field is of type string to allow the unit of measure to be specified (future version). |\n| HPosition | The horizontal position of the element. |\n| LineColor | The color of the element's line in \\#rrggb\\textit{b} or \\#aarrggb\\textit{b} format where \\textit{aa} represents the alpha / transparency. |\n| LineWidth | The width of the element's line. Note that this field is of type string to allow the unit of measure to be specified (future version). |\n| Opacity | The Opacity of the element. Note that workflow watermarks use Opacity whereas direct web service calls use the opposite term Transparency. |\n| PageInterval | The page interval that determines if a watermark should be applied to the current page number, e.g. '2' to apply the watermark to every other page. |\n| PageOrientation | Specifies what page orientation the watermark applies to: Portrait, Landscape or Both. |\n| PageRange | An optional string representation of the range of pages |\n\n\\textsuperscript{17} Only supported by PDF and PPTX\n\n| Property | Description |\n|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| PageType | In case of MS-Word, the kinds of header the watermark applies to *Default*, *First* or *Even*, providing these options have been set for the section header. These values can be combined, so *First + Even* is possible. |\n| PrintOnly\\(^{18}\\) | Boolean value indicating if the watermark should always be displayed (False) or only when printing (True). |\n| Rotation | The rotation to apply to the element in degrees. Note that this field is of type *string* to allow the system to determine if it has been specified or not. |\n| ScaleMode | The behaviour to use when scaling the element, e.g., maintain Aspect Ratio or ExactFit. |\n| ScaleX | The horizontal scaling to apply to the element, where 1 is the original size. Any number between 0 and 1 reduces the size whereas any number above 1 increases the size. Note that this field is of type *string* to allow different scaling units to be specified in a future version. |\n| ScaleY | The vertical scaling to apply to the element, where 1 is the original size. Any number between 0 and 1 reduces the size whereas any number above 1 increases the size. Note that this field is of type *string* to allow different scaling units to be specified in a future version. |\n| SectionRange | For MS-Word, an optional string representation of the range of sections the watermark applies to. For example, “1,3,7,10-15”. If specified, this is in addition to the values stored in the StartSection and EndSection properties. |\n| StartPage\\(^{17}\\) | The first page of the document the watermark applies to. Defaults to the first page. Use negative values to count from the back of the document (e.g -1 is last page, -2 is second to last page) |\n| StartSection | In case of MS-Word, the index of the first section this watermark applies to. |\n| Transparency | The element’s transparency where 1 means *opaque* and 0 is completely transparent. Note that workflow watermarks use *Opacity* whereas direct web service calls use the opposite term *Transparency*. |\n| VAlign | Vertical alignment of text stored in a *Text* element. |\n| VPosition | The vertical position of the element. |\n| Width | The width of the element. Note that this field is of type *string* to allow the unit of measure to be specified (future version). |\n| WordWrap | The word wrapping behaviour of text stored in a *Text* element. |\n\n\\(^{18}\\) PDF Only\n\n| Element | Description |\n|---------|-------------|\n| X | The x-coordinate of the element. Note that this field is of type *string* to allow the unit of measure to be specified (future version). |\n| Y | The y-coordinate of the element. Note that this field is of type *string* to allow the unit of measure to be specified (future version). |\n| ZOrder | For the watermark, not for individual elements, a negative or 0 z-order means that the watermark will be displayed behind the content of the document. A positive value will display the watermark on top of the content. |\n\n### 13.7 Embedding field codes in the Text element\n\nThe *Text* element allows field codes to be embedded, for example the *number of pages* or the *current date*. This makes it very simple to use watermarks to automatically generate headers and footers on each page, while taking orientation and page interval (Odd / Even pages) into account.\n\nFor full details see Appendix - Merge codes.\n\n14 Securing PDF, Word, Excel and PowerPoint Files\n\n14.1 Secure files using SharePoint Designer Workflows\n\nThe PDF Converter comes with a SharePoint Designer Workflow Activity that allows security settings such as the Open Password, Owner Password and document restrictions such as Printing\\(^{19}\\) and Content Copying to be applied from a friendly SharePoint Designer workflow.\n\nThe latest version of this chapter is available on-line at the following address:\n\nhttps://www.muhimbi.com/blog/securing-pdf-files-using-sharepoint-designer-workflows/\n\nThe best way to show how this works is by example. What follows is a walkthrough of how to create a SharePoint Designer Workflow to automatically apply security settings to any new or modified PDF file in a Document Library. In this example we use SharePoint Designer 2010, but it works just as well in other SharePoint Designer versions.\n\nBefore we begin, let’s have a look at the options provided by the Secure Document workflow activity.\n\nSecure this document to this file. New open password: password, new owner password: password, disable: Print|HighResolutionPrint|ContentCopy|Annotations|FormFields|ContentAccessibility|DocumentAssembly. Store the changed item details in List ID: Variable: List ID, Item ID: Variable: List Item ID.\n\nIn typical Muhimbi fashion, the workflow sentence is consistent with our other Workflow Activities, and is largely self-describing.\n\n1. **this document**: The document to apply the security settings to. For most workflows selecting Current Item will suffice, but some custom scenarios may require the lookup of a different item. You may also want to check that the file type of the document is ‘pdf’ before trying to apply security.\n\n2. **this file**: The name and location of the secured file. Leave this field empty to overwrite the source file with the secured copy. Enter a path, including the Document Library and any folder names, to write the secured file to a separate location. E.g., “shared documents/secured files/confidential.pdf”. You can even specify a different site collection, see Appendix - Specifying path and file names.\n\n3. **open password**: When specified, anyone who wants to open the PDF file will need to enter this password.\n\n4. **owner password**: When specified, anyone who wants to change the security settings on the PDF file will need to enter this password.\n\n5. **disable options**: One or more restrictions to apply to the PDF file, separated by a pipe ‘|’ character. By default, it applies all restrictions (Print|HighResolutionPrint|ContentCopy|Annotations|FormFields|ContentAccessibility|DocumentAssembly), but any combination is allowed. Enter the\n\n---\n\n\\(^{19}\\) The PDF Format supports all functionality. Word, Excel and PowerPoint support a subset.\n\nword *Nothing* to not apply any restrictions. In order to activate these settings, you must supply an owner password.\n\n6. **List ID**: The ID of the list the secured file was written to. This can later in the workflow be used to perform additional tasks on the file such as a check-in or out.\n\n7. **Item ID**: The ID of the secured file. Can be used with the List ID.\n\nCreate the workflow as follows:\n\n1. Download and install the Muhimbi PDF Converter for SharePoint.\n2. Make sure you have the appropriate privileges to create workflows on a site collection.\n3. Create a new workflow using SharePoint Designer.\n4. Associate the workflow with the library of your choice, tick the boxes next to both ‘Automatically start…’ options and proceed to the next screen.\n5. Because we are running the workflow when PDF files are created as well as modified, a new Yes/No column named *Secured* will need to be added to the document library using a default value of *No*. This way we can mark\n\na document as *secured* and stop workflows from recursively triggering. Alternatively, if files are secured in place, you can decide to just trigger the workflow when new files are added.\n\n6. Design the workflow as per the following screen. In summary it does the following:\n\n1. Check if the file is in PDF format. Otherwise, security cannot be applied.\n2. Check if the file has already been secured. If it has then it doesn’t need to be secured again.\n3. The PDF File is secured in place. Both Open and Owner passwords are applied, and all restrictions are set.\n4. The file is marked as *Secured* so the workflow doesn’t repeatedly run.\n5. A status message is written to the workflow history.\n\n```\nIf Current Item:File Type equals pdf\nand Current Item:Secured equals No\n\nSecure Current Item to this file. New open password: Muhimbi1, new owner password: Muhimbi2,\ndisable: Print|HighResolutionPrint|ContentCopy|Annotations|FormFields|ContentAccessibility|DocumentAssembly.\nStore the changed item details in List ID: Variable: List ID, Item ID: Variable: List Item ID.\n\nthen Set Secured to Yes\nthen Log Item ID: [%Variable: List Item ID%] to the workflow history list\n```\n\nPublish the workflow and create / convert / upload a new PDF file in the Document Library. After a few seconds the workflow column will change to *Completed*, indicating that the file has been secured successfully.\n\n14.2 Secure Documents using Nintex Workflow\n\nSimilar to all other Nintex Activities provided by Muhimbi, the *Secure PDF* activity integrates with Nintex Workflow at a deep level. It supports SharePoint 2007-2019, allows errors to be handled and even supports integration with Nintex’ iterators to deal with multiple items and loops. For a comprehensive example and details about how to enable the Nintex Workflow integration see chapter 4 *Converting Documents using Nintex Workflow*. You may also want to look at section 14.1 for a tutorial about using a similar Workflow Activity in SharePoint Designer Workflows.\n\nThe fields supported by this Workflow Activity are as follows:\n\n- **Destination Path**: Enter the path to write the secured file to, either:\n - Leave it empty to use the same filename (and path) as the file that triggered the workflow.\n - A file name, without the full path, to write a differently named file to the same location as the source file.\n - A relative path to a subsite / document library / folder, e.g. *Shared Documents/Some Folder/Some File.pdf*.\n - An absolute path to a different site collection, e.g. */sites/Finance/Shared Documents/Some Folder/Some File.pdf*. Please make sure the path does not include the host name, e.g. ‘http://your site/…’.\n\nFor details see Appendix - Specifying path and file names.\n\n• **Open Password**: An optional password that the user must enter in order to open the document. *Please note that any password entered here is displayed in clear text to allow Nintex field references to be added.*\n\n• **Owner Password**: An optional password that the user must enter in order to change the PDF restrictions. When specifying PDF Restrictions then this password must be set. *Please note that any password entered here is displayed in clear text to allow Nintex field references to be added.*\n\n• **Individual PDF Restrictions**: Select the individual restrictions such as Disable Printing or Disable Content Copying.\n\n• **PDF List ID**: If you wish to carry out further actions on the secured document, e.g. send it by email or perform a check-in, then you can optionally write the ID of the List the file was written to in a workflow variable of type *String*.\n\n• **PDF List Item ID**: Similarly to **PDF List ID**, the Item ID of the secured file can optionally be written to a workflow variable of type *Item ID* (in SharePoint 2007) or *Integer* (in SharePoint 2010 and later versions).\n\n• **Source List ID & List Item**: The item that triggered the workflow is secured by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use the same data types as used by **PDF List ID** and **PDF List Item ID**.\n\n• **Error Handling**: Similar to the way some of Nintex’ own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi’s Workflow Activities allow the same. By default this facility is disabled meaning that any error terminates the workflow.\n\n### 14.3 Securing Documents using the SharePoint User Interface\n\nSection 13.5 *Automatically applying watermarks using the SharePoint UI* explains how user-specific watermarks can be added the moment a file is downloaded or accessed. This works well, but as watermarks cannot be applied to secured documents these files will need to be secured after watermarks have been added.\n\nThe facility explained in this section can be used for exactly that purpose. The latest version of this section, including user feedback, can be found [on the Muhimbi Blog](#). Additional details about securing Office files [can be found here](#).\n\nThe key features are as follows:\n\n- Apply security to Word, Excel, PowerPoint and PDF Files.\n- Apply security after user specific watermarks have been applied.\n- Apply typical PDF Security including Open Password, Owner Password, Prevent Printing, Prevent Copy, Prevent Document assembly, etc.\n- Allow filters to be specified and only apply security when a condition is met, e.g. a Status field is set to Approved, or the user that is accessing the document is in a specific group.\n- Apply security to files in Document Libraries as well as files attached to individual list items.\n- Works on all SharePoint 2007 and later versions.\n\nLet’s work through an example to show how easy it is to set this up.\n\n1. By default the Secure / Watermark on open facility is disabled so use SharePoint Central Administration to enable the *Muhimbi PDF Converter - Automatic Document Processor* Feature at the relevant Web Application. Note that this is a Web Application Scoped Feature, not a Farm or Site Collection scoped one. You also need to enable the *Muhimbi PDF Converter - Automatic Document Processing User Interface* Feature at either the Web Application Level (to enable the screen on all Site Collections) or at the individual Site Collection level.\n\n2. Once enabled, a new menu named *Security settings* can be found in the *Site Actions / Site Settings* screen as well as the *List Settings* screen on each individual List and Document Library. Default security settings can optionally be specified at the Site Collection level, which can then be inherited at the individual List or Library Level, which is displayed in the following screen.\n\n3. As can be seen in the screenshot there are also options to enable security during *Insert* and *Update* events. However, the focus of this example is to *Secure On Open*. In this screenshot we have specified both an *Open* and an *Owner Password*. The *Owner Password* must be set when any of the *PDF Security Options* are selected, the *Open Password* is optional.\n\n4. In the same screenshot we have also specified a filter to only secure documents when the person opening the file is in the *Test Visitors* SharePoint group. Please note that you can only use SharePoint Group names, not Windows Group names.\n\nThat is all there is to it. When a PDF or Office file is opened from the Document Library, and the user opening it is a member of the *Test Visitors* group, then security will be applied automatically to the file without modifying the original in the List or Document Library.\n\nPlease note that securing files this way is a *real-time* action and adds some overhead. If there is no need to apply security in combination with user specific watermarks, or based on a user specific filter, then we recommend applying security using a *SharePoint Designer Workflow* (See 14.1) or *Nintex* Workflow (See 14.2) the moment a file is created or modified.\n\nUse the *Filtering out system users (e.g. Search indexer)* facility, described in section 13.5.5 to skip processing for certain accounts.\n\n15 Carry out OCR (Optical Character Recognition)\n\nThe Muhimbi PDF Converter for SharePoint provides support for Optical Character Recognition (OCR), which can be used to convert image-based content such as scans or faxes into fully searchable and indexable PDFs. In addition, it can be used to recognise text and extract content from these images and use it for further processing. This can be useful to retrieve invoice numbers or other textual content from documents that conform to a particular template.\n\nPlease note that you need a PDF Converter Professional add-on license in addition to a valid PDF Converter for SharePoint or PDF Converter Services License in order to use this functionality.\n\n15.1 Convert Images & Scans to Searchable PDFs\n\nOne of the more popular questions the Muhimbi support desk receives is about converted PDF files being searchable by users and indexable by search engines. The answer to that question has always been Yes …… providing the source document consists of real text such as MS-Word, Excel, MSG, EML, HTML and most of the other file formats we support.\n\nThe story is quite different when the source file is a scanned document, which just contains a picture of the text. Generally, search engines do not understand these image based files and will simply skip them.\n\nThe solution is to OCR these documents, a process that recognises text and places it in a hidden layer. The resulting document still looks identical to the original file, but search engines and PDF readers are intelligent enough to retrieve the text. The processed documents are fully searchable and content can even be copied to the clipboard for pasting in other applications.\n\nAs of version 7.1 the PDF Converter supports the use of OCR to process Image based files and generate searchable PDFs.\n\nThe key features are as follows:\n\n- Server based solution, accessible via a modern Web Service interface (Java, C#, Ruby, PHP etc)\n- Integrates with SharePoint Designer and Nintex workflows.\n- Convert image-based files such as TIFF, Scanned PDF, PNG, JPG, BMP, GIF to searchable PDFs.\n- Support for multiple languages (Arabic, Danish, German, English, Dutch, Finnish, French, Hebrew, Hungarian, Italian, Norwegian, Portuguese, Spanish and Swedish).\n- Additional languages and custom fonts can be added by customers and third parties.\n- Fully integrated with the conversion pipeline allowing a single web service call to Convert, OCR, Watermark, Merge and Secure documents.\n- Whitelist / Blacklist certain characters. For example, limit recognition to numbers by white-listing 1234567890. This prevents, for example, a 0 (zero) to be recognised as the letter o or O.\n- Integrate with 3rd party OCR Engines such as PrimeOCR.\n\nAlthough very powerful, OCR has its limitations. If the source material is of poor quality (a lot of noise, scratches, low resolution or unusual fonts) then text will most likely not be recognised with a high level of accuracy. However, when the scans use 300dpi and the font size is not smaller than 10pt, then the results are generally very good.\n\n### 15.1.1 OCR files using SharePoint Designer workflows\n\nIt is possible to carry out OCR using our standard Convert Document workflow activity, but that requires knowledge of our XML syntax, which - although powerful - is less than user friendly. To make life easier we have created a separate Workflow Activity named Convert to OCRed PDF. This is what it looks like.\n\nConvert and OCR this document to this file, include / exclude meta data, in English using Slow but accurate performance. Whitelist all characters, do not use pagination, only OCR these regions. Store the converted item details in List ID: Variable: List ID, Item ID: Variable: List Item ID\n\nThe workflow sentence is consistent with the other Muhimbi Workflow Activities and largely self-describing:\n\n1. **this document**: The source document to Convert and OCR. For most workflows selecting Current Item will suffice, but some scenarios may require the look up of a different item.\n2. **this file**: The name and location to write the generated file to. Leave this field empty to use the same location and name as the source file. Please\n\nnote that if your source file is already in PDF format then leaving this field empty will overwrite it. For details about how to specify paths to different libraries / site collections see Appendix - Specifying path and file names.\n\n3. **include / exclude meta data**: Control if the source file's SharePoint metadata is copied to the destination file.\n\n4. **OCR language**: The language the source document is written in. It defaults to English, but we currently support Arabic, Danish, German, English, Dutch, Finnish, French, Hebrew, Hungarian, Italian, Norwegian, Portuguese, Spanish and Swedish.\n\n5. **OCR Performance**: Specify the performance / accuracy of the OCR engine. It is recommended to leave this on the default *Slow but accurate* setting.\n\n6. **Whitelist / Blacklist**: Control which characters are recognised. For example, limit recognition to numbers by whitelisting 1234567890. This prevents, for example, a 0 (zero) to be recognised as the letter o or O.\n\n7. **Pagination**: In some specific cases a single image spans multiple pages. Enable *pagination* for those cases.\n\n8. **Regions**: By default, the entire page is OCRed. To limit OCR to certain parts of a page, e.g., a header and/or footer, you can specify one or more regions using our XML syntax. Have a look at this [blog post](#), but only use the part that starts with (and includes) `<Regions> ...</Regions>`.\n\n9. **List ID**: The ID of the list the processed file was written to. This can later in the workflow be used to perform additional tasks on the file such as a check-in or out.\n\n10. **Item ID**: The ID of the processed file. Can be used with the List ID.\n\n15.1.2 OCR files using Nintex Workflow\n\nIt is possible to carry out OCR using our standard *Convert Document* workflow activity, but that requires knowledge of our [XML syntax](#), which - although powerful - is less than user friendly. To make life easier we have created a separate Workflow Activity named *Convert to OCRed PDF*. It is compatible with Nintex Workflow 2007-2019 and this is what it looks like.\n\nProcessed files are written to the same directory as the source file using the same file name. If needed specify an alternative location or name below.\n\n| Field | Description |\n|------------------------|-----------------------------------------------------------------------------|\n| Destination Path | The destination path for the processed file |\n| Output File Name | The output file name for the processed file |\n| Meta data | Include or exclude metadata |\n| Language | The language of the document |\n| Performance | The performance level of the OCR process |\n| Blacklist/whitelist | None, Blacklist, Whitelist |\n| Characters | The characters to be recognized |\n| Use pagination | Use pagination |\n\nLimit the area to OCR to one or more specific regions. Enclose with `<Regions>...</Regions>`.\n\nIf you wish to carry out further operations on the generated file, e.g. a check-in, then please store the ID of the generated file in workflow variables.\n\n| Field | Description |\n|------------------------|-----------------------------------------------------------------------------|\n| Output List ID | The output list ID |\n| Output Item ID | The output item ID |\n| Source List ID | The source list ID |\n| Source List Item | The source list item |\n\nThe item that triggered the workflow is processed by default. You can optionally specify the ID of a different item below using workflow variables.\n\nFor a comprehensive example and details about how to enable the Nintex Workflow integration see chapter 4 *Converting Documents using Nintex Workflow*.\n\nThe fields supported by this Workflow Activity are as follows:\n\n1. **Destination Path**: The location to write the generated file to. Leave this field empty to use the same location as the source file. For details about how to specify paths to different libraries / site collections see *Appendix - Specifying path and file names*.\n\n2. **Output File Name**: The name of the generated file. Leave this field empty to use the same name as the source file. Please note that if your source file is already in PDF format, and the Destination Path is the same as the Source Path, then leaving this field empty will overwrite it.\n\n3. **Meta data**: Control if the source file’s SharePoint meta-data is copied to the destination file.\n\n4. **Language**: The language the source document is written in. It defaults to English, but we support *Arabic*, *Danish*, *German*, *English*, *Dutch*, *Finnish*, *French*, *Hebrew*, *Hungarian*, *Italian*, *Norwegian*, *Portuguese*, *Spanish* and *Swedish*.\n\n5. **Performance**: Specify the performance / accuracy of the OCR engine. It is recommended to leave this on the default *Slow but accurate* setting.\n\n6. **Whitelist / Blacklist**: Control which characters are recognised. For example, limit recognition to numbers by whitelisting 1234567890. This prevents, for example, a 0 (zero) to be recognised as the letter o or O.\n\n7. **Pagination**: In some specific cases a single image spans multiple pages. Enable *pagination* for those cases.\n\n8. **Regions**: By default, the entire page is OCRed. To limit OCR to certain parts of a page, e.g., a header and/or footer, you can specify one or more regions using our XML syntax. Have a look at this [blog post](#), but only use the part that starts with (and includes) `<Regions> ... </Regions>`.\n\n9. **Output List ID**: If you wish to carry out further actions on the generated file, e.g., send it by email or perform a check-in, then you can optionally store the ID of the List the file was written to in a workflow variable of type *String*.\n\n10. **PDF List Item ID**: Similarly, to *Output List ID*, the Item ID of the generated file can optionally be stored in a workflow variable of type *Item ID* (in SharePoint 2007) or *Integer* (in SharePoint 2010 and later versions).\n\n11. **Source List ID & List Item**: The item that triggered the workflow is processed by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use the same data types as used by *Output List ID* and *Output List Item ID*.\n\n12. **Error Handling**: Similar to the way some of Nintex’ own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi’s Workflow Activities allow the same. By default, this facility is disabled meaning that any error terminates the workflow.\n\n15.1.3 OCR files using a web Service call\n\nFor a detailed example about how to use the Web Services interface to carry out OCR and generate fully searchable and indexable PDF files see [this Knowledge Base article](#).\n\n15.2 Extract text from image based content\n\nA new OCR related facility has been added to the product with the introduction of version 7.2. This new facility allows text on (part of) a page to be recognised and returned to the workflow for further processing.\n\nA common use for this is to extract a particular area of text from documents that all use a common template or layout. For example, if a reference number can always be found at the top right corner of scanned documents, then that text can be extracted and stored in a SharePoint column from where it can be included in searches or be used in further workflow steps.\n\n15.2.1 Extract text using OCR and SharePoint Designer Workflows\n\nOnce the PDF Converter is installed you will find a number of new Workflow Activities in SharePoint Designer. One of these activities is named *Extract Text using OCR* and looks as follows.\n\n```\nExtract text from [this document](#) using OCR in [English](#) using [Slow but accurate](#) performance. Whitelist [all](#) characters, do not use pagination, only ORC region at [x, y](#), size [width x height](#) on page [all](#). Store the result in [Variable: result](#).\n```\n\nThe workflow sentence is consistent with the other Muhimbi Workflow Activities and largely self-describing:\n\n1. **this document**: The source document to OCR and extract text from. For most workflows selecting *Current Item* will suffice, but some scenarios may require the look up of a different item.\n\n2. **OCR language**: The language the source document is written in. It defaults to English, but we support *Arabic, Danish, German, English, Dutch, Finnish, French, Hebrew, Hungarian, Italian, Norwegian, Portuguese, Spanish and Swedish*.\n\n3. **OCR Performance**: Specify the performance / accuracy of the OCR engine. It is recommended to leave this on the default *Slow but accurate* setting.\n\n4. **Whitelist / Blacklist**: Control which characters are recognised. For example, limit recognition to numbers by whitelisting 1234567890. This prevents, for example, a 0 (zero) to be recognised as the letter o or O.\n\n5. **Pagination**: In some specific cases a single image spans multiple pages. Enable *pagination* for those cases.\n\n6. **Region**: Specify the \\(x\\), \\(y\\), *width* and *height* of the region to retrieve text from. The unit of measure (UOM) is *pt*, 1/72\\(^{nd}\\) of an inch. When extracting text from non-PDF files, e.g., a TIFF or PNG, then please take into account that internally the image is first converted to PDF, which may add margins around the image but guarantees that a single – unified - UOM is used across all file formats. If you are not sure how internal conversion affects the dimensions of your image or scan, then use our software to convert the file to PDF and open it in a PDF reader.\n\n7. **Page**: By default, text is extracted from all pages and concatenated. To extract the text from a specific page, specify the page number in this field.\n\n8. **Result**: The recognised text will be stored in this variable (type String).\n\n### 15.2.2 Extract text using OCR and Nintex Workflow\n\nThe new *Extract text using OCR* activity is compatible with Nintex Workflow 2007 and later versions.\n\nFor a comprehensive example and details about how to enable the Nintex Workflow integration see chapter 4 *Converting Documents using Nintex Workflow*.\n\nThe fields supported by this Workflow Activity are as follows:\n\n1. **Language**: The language the source document is written in. It defaults to English, but we support Arabic, Danish, German, English, Dutch, Finnish, French, Hebrew, Hungarian, Italian, Norwegian, Portuguese, Spanish and Swedish.\n\n2. **Performance**: Specify the performance / accuracy of the OCR engine. It is recommended to leave this on the default *Slow but accurate* setting.\n\n3. **Whitelist / Blacklist**: Control which characters are recognised. For example, limit recognition to numbers by whitelisting 1234567890. This prevents, for example, a 0 (zero) to be recognised as the letter o or O.\n\n4. **Pagination**: In some specific cases a single image spans multiple pages. Enable *pagination* for those cases.\n\n5. **Region**: Specify the $x$, $y$, width and height of the region to retrieve text from. The unit of measure (UOM) is pt, 1/72$^{nd}$ of an inch. When extracting text from non-PDF files, e.g., a TIFF or PNG, then please take into account that internally the image is first converted to PDF, which may add margins around the image but guarantees that a single - unified - UOM is used across all file formats. If you are not sure how internal conversion affects the dimensions of your image or scan, then use our software to convert the file to PDF and open it in a PDF reader.\n\n6. **Page Number**: By default, text is extracted from all pages and concatenated. To extract the text from a specific page, specify the page number in this field.\n\n7. **Output Text**: The recognised text will be stored in this variable (type String).\n\n8. **Source List ID & List Item**: The item that triggered the workflow is processed by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use data type *string* for the List ID workflow variable. For the Item ID use type *Item ID* (in SharePoint 2007) or *Integer* (in SharePoint 2010 and later versions)\n\n9. **Error Handling**: Similar to the way some of Nintex’ own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi’s Workflow Activities allow the same. By default, this facility is disabled meaning that any error terminates the workflow.\n\n16 Copying Metadata\n\nSome of the product’s Workflow Activities and conversion screens provide the ability to copy-meta as part of the conversion process. This works well, but it is an ‘all or nothing’ approach.\n\nTo provide users with a more flexible way of copying meta-data, and setting an item’s content type, we provide a separate SharePoint Designer and Nintex Workflow Activity to deal with this kind of operation.\n\nThe high-level functionality is as follows:\n\n- Standalone Workflow Activity that can be used in combination with any of Muhimbi’s Workflow Activities, or without them.\n- Copy all meta-data or only selected fields.\n- Copy meta-data to files in different folders or site collections.\n- Change the content type to either the source file’s, destination file’s, the default content type for the library or a specific named content type.\n- Copy content of *Author*, *Created* and *Modified* fields by explicitly specifying these field names. This information is not copied when the default ‘copy all fields’ option is enabled. It is not possible to copy the *Editor* field as that is always overwritten by the workflow.\n\n16.1 Copying Metadata from SharePoint Designer Workflows\n\nTo insert the *Copy Meta-Data* Activity into a workflow, click the *Action* button in the SharePoint Designer Workflow editor and select *Copy Meta Data*. This inserts the following workflow sentence.\n\n```\nCopy meta data from this document to this file (optionally copy only these fields: all fields). Set content type to {source}. Store the target item details in List ID: Variable: List ID1, Item ID: Variable: List Item ID1\n```\n\nThe parameters are largely self-describing and use the same format as the other Workflow Activities.\n\n- **This document**: The source document to copy the meta-data from. For most workflows selecting *Current Item* will suffice, but some custom scenarios (e.g., Site workflows) may require the look up of a different item.\n\n- **This File**: The path and file name to copy the meta-data to. *Please make sure that the path does not include the host name, e.g., 'http://your site/...'. For more details see Appendix – Specifying path and file names.*\n\n- **Fields**: By default, the content of all fields is copied to the destination file. However, if you wish to copy only specific fields then the field names can be specified in this list. You can separate fields using line breaks, ‘,’ or ‘;’ and you can use both *internal* and *display* field names.\n\n• **Content type**: While copying meta-data you have full control over the content type of the destination file. The following options can be specified:\n\n o *(source)*: The content type of the source file is copied to the destination file. *Please include the round brackets.*\n\n o *(target)*: The content type of the destination file is not modified and remains what it was before the copy operation. *Please include the round brackets.*\n\n o *(default)*: The default content type for the document library is applied to the destination file. *Please include the round brackets.*\n\n o **Name of Content type**: The destination file is set to a specific, named, content type. *Please do not use round brackets around the name of the content type.*\n\n• **Parameter ‘List ID’**: The ID of the file the meta-data was copied to. This can later in the workflow be used to perform additional tasks on the file such as performing a check-in or out.\n\n• **Parameter ‘List Item ID’**: The ID of the list that holds the file that the meta-data was copied to.\n\n### 16.2 Copying Metadata using a Nintex Workflow\n\nFor a full example of how to use Muhimbi’s Workflow Activities using Nintex Workflow see Chapter 4 *Converting Documents using Nintex Workflow*. The fields supported by this Workflow Activity are as follows:\n\n- **Target Path**: Enter the path of the target file to copy meta-data to, either:\n - Leave empty to use the same directory as the source file.\n - A relative path to a sub site / document library / folder.\n\nAn absolute path to a different site collection.\n\nPlease make sure the path does not include the host name, e.g., 'http://your site/...'. For more details see Appendix - Specifying path and file names.\n\n- **Target File Name**: The name of the file to copy the meta-data to. Leave empty to use the source file, which can be useful if you just wish to set the content type of a file.\n\n- **Copy these fields**: By default, the content of all fields is copied to the destination file. However, if you wish to copy only specific fields then the field names can be specified in this list. You can separate fields using line breaks, ',' or ';', and you can use both *internal* and *display* field names.\n\n- **Set Content type**: While copying meta-data you have full control over the content type of the destination file. The following options can be specified:\n\n - *(source)*: The content type of the source file is copied to the destination file. Please include the round brackets.\n\n - *(target)*: The content type of the destination file is not modified and remains what it was before the copy operation. Please include the round brackets.\n\n - *(default)*: The default content type for the document library is applied to the destination file. Please include the round brackets.\n\n - **Name of Content type**: The destination file is set to a specific, named, content type. Please do not use round brackets around the name of the content type.\n\n- **Out List ID**: If you wish to carry out further actions on the target file, e.g., perform a check-in, then you can optionally write the ID of the List that holds the target file to a workflow variable of type *String*.\n\n- **Out List Item ID**: Similarly, to Out List ID, the Item ID of the target file can optionally be written to a workflow variable of type *Item ID* (in SharePoint 2007) or *Integer* (in SharePoint 2010 and later versions).\n\n- **Source List ID & List Item**: The item that triggered the workflow is used as the source item by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use the same data types as used by Out List ID and Out List Item ID.\n\n- **Error Handling**: Similar to the way some of Nintex' own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi's Workflow Activities allow the same. By default, this facility is disabled meaning that any error terminates the workflow.\n\n17 Building a Table Of Contents\n\nOne of the more popular features provided by the PDF Converter is the ability to convert and merge multiple documents into a single PDF, all in one operation (See chapter 10 for details). Although this facility works very well, and even includes the ability to generate PDF bookmarks to aid with navigation inside the merged document, a common request is to add a full Table of Contents (TOC) to the merged document as well.\n\nIn this chapter the focus is on generating a TOC via our API (See our separate Developer Guide). However, if you wish to use this functionality from a SharePoint Workflow, then please continue reading as well. We might have to get a little bit technical, but once you’re familiar with the concepts, you can use our XML based workflow syntax – as described in Appendix - Override default conversion settings - to generate a table of contents from SharePoint Designer, Nintex and K2 based workflows.\n\nA copy of this chapter can also be found on our Blog.\n\n17.1 Object Model\n\nThe classes relevant to dealing with TOCs are as follows:\n\n- **MergeSettings**: When merging multiple files and generating a single table of contents, follow the normal procedure for merging files (sample code) and populate the `MergeSettings.TOCSettings` property as per the sample code below.\n\n- **ConversionSettings**: To generate a table of contents for a single document (so not as part of a merge operation), follow the normal procedure for converting or processing a single file (sample code) and populate `ConversionSettings.TOCSettings` as per the sample code below.\n\n- **TOCSettings**: All settings related to the generation of the TOC can be found in this class. The available properties are as follows:\n\n - **Bookmark**: The TOC itself can have its own PDF bookmark to aid with navigation. Specify the text in this property.\n\n - **Location**: TOCs can be added to the Front or Back of the document. Enter the relevant option here.\n\nMinimumEntries: For certain, simple, documents that only have one or 2 bookmarks, it may not make sense to add a table of contents. Use this property to specify the minimum number of entries before a TOC is generated. The default value is '0', which will always create a TOC regardless of the number of entries.\n\nPageMargins: Page margins in the format set out below. It defaults to a uniform half inch margin.\n\n\"#{dim}\" - for a uniform margin or\n\"#{dim},#{dim},#{dim},#{dim}\" - for individual margins\n\nwhere\n- # is numeric value\n- {dim} is dimension. Either empty (meaning inches) or \"mm\", \"in\", \"in.\", \"inch\" or \"inches\".\n\nPageOrientation: The orientation used by the TOC. Portrait, Landscape or Default. The Default option uses the same orientation as the page following (or preceding) the TOC depending on the value specified in Location.\n\nPaperSize: A named paper size such as A4 or Letter (See MSDN) or a custom size in \"{width}{dim}{sep}{height}{dim}\" format where:\n\n- {width} and {height} are numerical values (please use a colon ':' as the decimal separator).\n- {dim} is the dimension which can be 'mm', 'in.' or 'inches'. (It defaults to inches when nothing is specified)\n- {sep} separates the width and the height, either 'by', comma (,) or the letter 'x' Example: \"8.5 in. by 6 in.\"\n\nProperties: Optional properties to pass to the XSL template for display or processing purposes. For details see below.\n\nTemplate: The XSL template (See 17.3) to use for formatting purposes. This can either be a string containing all the XSL, a path local to the server running the conversion service - to the location of the XSL file, or a URL to the XSL file on a web (or SharePoint) server.\n\n- NameValuePair: A single value that can be passed into the XSL using TOCSettings.Properties.\n\n- TOCLocation: Used by TOCSettings.Location to determine where the TOC should go.\n\n- BookmarkGenerationOption: As explained in XML Source Data (17.2), the TOC system is based on the content and structure of PDF Bookmarks. It is therefore essential that during the conversion of the source documents ConversionSettings.GenerateBookmarks is set to Automatic.\n\nBased on the previously described list of classes and properties, adding a TOC may sound complex, but nothing could be further from the truth. The easiest way to get started is to take our sample code, add the following code and then pass `tocSettings` into either `ConversionSettings.TOCSettings` or `MergeSettings.TOCSettings`.\n\n```csharp\n// ** Create any custom properties that need to be passed into the TOC.\nNameValuePair[] properties = new NameValuePair[2];\nproperties[0] = new NameValuePair() { Name = \"title\", Value = \"Development Guide\" };\nproperties[1] = new NameValuePair() { Name = \"status\", Value = \"Draft\" };\n\n// ** Specify the various TOCSettings\nTOCSettings tocSettings = new TOCSettings\n{\n MinimumEntries = 0,\n Bookmark = \"Table Of Contents\",\n Location = TOCLocation.Front,\n Properties = properties,\n Template = @\"C:\\templates\\toc.xsl\",\n};\n\n// ** Pass the TOC Settings into the conversion\nconversionSettings.TOCSettings = tocSettings;\n```\n\nYou are not limited to our sample code, but it is a good starting point. It is even possible to pass the `tocSettings` to both `ConversionSettings.TOCSettings` AND `MergeSettings.TOCSettings` to generate TOCs for each individual document in a merge operation, and then add an overall TOC for the entire merged document.\n\nThe big question is what to specify in the `Template` property. Read on for details.\n\n### 17.2 XML Source Data\n\nTo determine what entries to include in the TOC, the conversion service looks at the Bookmarks present in the PDF file. If the source file is not already in PDF format, it will be converted to PDF and – where possible – generate PDF bookmarks based on the internal structure of the document. For example, when converting an MS-Word file the various headings determine the structure of the PDF Bookmarks.\n\nAlthough in most cases it is not important for our customers to have any knowledge about the internals of the Muhimbi Conversion Service, in this particular case - and by design - it is. Internally, an XML document is generated that represents the content and structure of the PDF Bookmarks, this XML document is then transformed using XSL into HTML. It is this HTML – the language that underpins every website on the internet – that determines the formatting of the TOC. Developers have full control over the XSL, providing an enormous amount of flexibility.\n\nLet's take our Administration Guide as an example. When converted to PDF a set of nested PDF bookmarks are created, which internally generates the following XML (truncated as it is several pages long).\n\nThe generated XML is fairly straightforward, with a number of nested `topic` elements making up the structure. Each element has a descriptive `title` attribute, a `level` attribute (which matches the nesting level), a `page` attribute containing the page number, and a target attribute which is used for internal processing purposes (this example shows [GUID] as it is not relevant).\n\nPlease note: All page numbers in the TOC reflect the physical page number of that page in the generated PDF, including the addition of the TOC page itself. If the source document(s) already display page numbers, then these may no longer be the same as the page number listed in the TOC or their actual page number in the generated PDF. If you wish to change the page numbers displayed in the footer of a document, then please use our watermarking facilities (see chapter 13).\n\nThe list of `topic` elements is followed by a `properties` section. This section, and its contents, consists of a number of optional values that may have been passed into the request. This allows, for example, the addition of information to the TOC to display the document's status, author, title, or any other kind of information. In this example we are passing in the title of the document.\n\n### 17.3 XSL Transformation\n\nAlthough the XML document's content may differ between requests, the structure is always the same. As a result, we can use the [XSL industry standard](#) to convert the XML into an attractive-looking HTML document. Although XSL may look daunting to the uninitiated, the following sample ([download](#)) is a good starting point and can be amended to suit your particular needs (or used as is).\n\n```xml\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<xsl:stylesheet version=\"1.0\"\n xmlns:xsl=\"http://www.w3.org/1999/XSL/Transform\"\n xmlns:msxsl=\"urn:schemas-microsoft-com:xslt\"\n exclude-result-prefixes=\"msxsl\">\n\n <xsl:output method=\"html\" indent=\"yes\"/>\n\n <xsl:template match=\"/toc\">\n <html>\n <head>\n <style type=\"text/css\">\n ul.toc\n```\n\n14 {\n15 margin: 0;\n16 padding: 0;\n17 list-style: none;\n18 }\n19 ol.toc\n20 {\n21 margin: 0;\n22 padding: 0;\n23 margin-left: 10px;\n24 list-style: none;\n25 }\n26 ul.toc li\n27 {\n28 clear: both;\n29 overflow: hidden;\n30 }\n31 ol.toc li\n32 {\n33 overflow: hidden;\n34 }\n35 span.title\n36 {\n37 float: left;\n38 padding-right: 4px;\n39 }\n40 span.page\n41 {\n42 float: right;\n43 padding-left: 4px;\n44 }\n45 span.dots\n46 {\n47 font-size: 0px;\n48 width: 100%;\n49 border-bottom: 2px dotted black;\n50 }\n51 a.toc\n52 {\n53 text-decoration: none;\n54 color: #000;\n55 }\n56 </style>\n57 </head>\n58 <body>\n59 <h1>\n60 <xsl:value-of select=\"properties/property[@name='title']\"/>\n61 </h1>\n62 <br/>\n63 <br/>\n64 <xsl:apply-templates/>\n65 </body>\n66 </html>\n67 </xsl:template>\n68 <xsl:template match=\"topics\">\n69 <ul class=\"toc\">\n70 <xsl:apply-templates/>\n71 </ul>\n72 </xsl:template>\n73 <!-- Empty template so properties are not appearing -->\n74 <xsl:template match=\"properties\"></xsl:template>\n75 <xsl:template match=\"topic[@level='0 ' ]\">\n76 <li>\n77 <xsl:element name=\"a\">\n78 <xsl:attribute name=\"href\">\n79 <xsl:value-of select=\"@target\"/>\n80 </xsl:attribute>\n81 <xsl:attribute name=\"class\">toc</xsl:attribute>\n\nAlthough this is a standard XSL file, the following sections are of particular interest:\n\n- **Lines 12-56**: Standard HTML CSS style sheet which controls the look of the generated HTML.\n\n- **Line 60**: Insert a custom *property* passed into the conversion request. In our example the document’s title.\n\n- **Line 76**: An empty template for the *properties* element to prevent this information from being displayed as a plain list.\n\n- **Lines 78-97**: XSL template for generating HTML associated with all *Level 0* topics. If you wish to control the generated HTML for a specific level, then copy the `topic[@level='0']` template and change the level number to match to appropriate nesting level.\n\n- **Lines 99-118**: XSL Template for all topic levels that do not have an explicit template defined.\n\nIf your experience with XML and XSL is limited, then we recommend using the XSL sample provided above. As can be seen in the following screenshot, the results look very good.\n\nAdministration Guide - Contents\n\n1 Introduction .................................................................................................................. 8\n 1.1 Relevant articles on the Muhimbi Blog ................................................................. 9\n 1.2 Prerequisites ........................................................................................................... 10\n 1.3 Solution architecture ............................................................................................. 11\n\n2 Deployment .................................................................................................................. 12\n 2.1 Quick start .............................................................................................................. 12\n 2.1.1 Starting the Windows Service ....................................................................... 12\n 2.1.2 Installing the SharePoint Front End & Workflow actions ......................... 13\n 2.2 Detailed Installation instructions .......................................................................... 14\n 2.2.1 Installing the Windows Service ..................................................................... 14\n 2.2.2 Installing the SharePoint Front End ............................................................... 15\n 2.2.3 Feature Activation / Deactivation .................................................................. 16\n 2.2.4 Installing the License ...................................................................................... 17\n 2.3 Post Installation configuration ............................................................................... 18\n 2.3.1 Enabling converters / Specifying location of Conversion Service ............ 18\n 2.3.2 Tuning the Document Conversion service .................................................... 19\n 2.4 Un-installation ....................................................................................................... 32\n 2.4.1 Un-installing the Document converter service ............................................. 32\n 2.4.2 Un-installing the SharePoint Front End via the command line ................ 32\n 2.4.3 Un-installing the SharePoint Front End via Central Administration .......... 33\n 2.5 Upgrading from a previous version ....................................................................... 33\n\n3 Troubleshooting & Other common tasks .................................................................. 35\n 3.1 Windows Event Log ............................................................................................... 35\n 3.2 SharePoint Trace Log ............................................................................................ 35\n 3.3 Document Converter Trace Log ............................................................................. 36\n 3.4 SharePoint audit log ............................................................................................... 36\n 3.5 Common issues & Errors ...................................................................................... 36\n 3.5.1 Your account is not allowed to deploy SharePoint Solutions .................... 36\n 3.5.2 Errors on newly added servers ....................................................................... 36\n 3.5.3 An evaluation message is displayed in the UI and converted documents .... 37\n 3.5.4 ‘Unknown Error’ or ‘resource object no found’ ........................................... 38\n 3.5.5 Documents using non standard fonts (e.g. Japanese) are not converted properly / The fonts in the destination document are not correct ................................................................. 39\n 3.5.6 Error messages related to printer drivers or the printer spooler are logged .... 39\n 3.5.7 The PDF Converter functionality is not visible in a Document Library ........ 40\n 3.5.8 Problems converting InfoPath forms without a shared XSN file .................. 40\n 3.5.9 The ‘Convert to PDF’ context menu is displayed twice ............................... 41\n 3.5.10 InfoPath forms using Ink controls fail to convert ........................................ 41\n 3.5.11 Error 403 (Forbidden) when converting InfoPath forms ............................ 41\n 3.5.12 InfoPath files are converted using an old version of the XSN template ....... 41\n 3.5.13 Nintex Workflow Activities are not working as expected after upgrading .... 42\n 3.5.14 Event Manager error after uninstallation ..................................................... 42\n 3.5.15 Files uploaded via Windows Explorer do not trigger ‘Insert’ watermarks .... 42\n 3.5.16 ‘Watermark on Open’ does not show watermarks ..................................... 42\n 3.5.17 Problems with HTML to PDF Conversion of SharePoint 2010 pages .......... 43\n 3.5.18 Changing the default bookmark and sort fields when merging files ............ 43\n 3.5.19 Deploying the Conversion Service on Windows Server 2012 and later ........ 43\n\n17.4 Testing & Troubleshooting\n\nAlthough it is only a basic application, the PDF Converter comes with a handy Diagnostics Tool (including full source code) to test the TOC facility. While this might be merely a handy test tool, not the official user interface for the TOC facility, it can be incredibly helpful in quickly testing various XSL template designs before integrating them into your solution.\n\nTo test the XSL and TOC output, enable the Table of Content as per the screenshot above, modify the XSL template if needed, specify any optional properties, select a file or folder in the WS Convert tab and choose either the Convert or Merge button.\n\n17.5 Generating a TOC from a SharePoint Workflow\n\nThe previous sections explain the underlying TOC mechanism in detail, but the example uses the Muhimbi API, which is of little use to SharePoint Workflow developers. For an example about how to apply the same concept, but generate the TOC from a SharePoint Workflow, see the relevant example in Appendix - Override default conversion settings.\n\n18 Compressing output files\n\nAs of version 10.3, PDF Converter can make use of the Hyper Compression option. This can reduce the size of the output files by removing unwanted items (annotations, blank pages, JavaScript), downscaling images and using improved image compression techniques.\n\nHyper Compression, also known as Mixed Raster Content (MRC), is an image compression benefiting from image segmentation methods. It is particularly useful for images containing text and continuous-tone graphics.\n\n18.1 Object Model\n\nThe classes relevant to dealing with compressing files are as follows:\n\nOther objects (such as OpenOptions) may be relevant to your use case.\n\n## 18.2 Specifying the options\n\nThe following options are available:\n\n| Option | Description |\n|-------------------------------|-----------------------------------------------------------------------------|\n| RemoveAnnotations* | Remove annotations |\n| RemoveBlankPages* | Remove blank pages |\n| RemoveBookmarks* | Remove bookmarks |\n| RemoveEmbeddedFiles* | Remove embedded files |\n| RemoveFormFields* | Remove form fields |\n| RemoveHyperlinks* | Remove hyperlinks |\n| RemoveJavaScript* | Remove JavaScript |\n| RemoveMetadata* | Remove XMP metadata |\n| RemovePage-thumbnails* | Remove page thumbnails |\n| PackFonts* | Pack the PDF’s fonts to reduce their size. |\n| PackDocument* | Pack the PDF to reduce its size. |\n| RecompressImages* | Recompress the PDF’s images |\n| EnableMRC* | MRC (Hyper Compression) engine will be used for compressing the PDF contents. |\n| DownscaleResolutionMRC* | Resolution (DPI) for downscaling the background layer by the MRC engine. Default is 200 |\n| PreserveSmoothing* | MRC engine will preserve smoothing between different layers. |\n| ImageQuality | Image quality to be used for the compression of the images from the PDF: |\n| DownscaleImages* | Images from the PDF will be downscaled to the following resolution (DPI) |\n| DownscaleResolution | Resolution used to downscale images. Default 150. |\n| EnableColorDetection* | Color detection will be performed on the images from the PDF. |\n| EnableCharRepair* | Character repairing will be performed during bitonal conversion. |\n| EnableJPEG2000* | Use JPEG2000 compression scheme to compress color images |\n| EnableJBIG2* | Use JBIG2 compression scheme to compress bitonal images. |\n| JBIG2PMSThreshold | Threshold value for the JBIG2 encoder pattern matching and substitution. Range 0 to 100, any number lower than 100 may lead to lossy compression. Default is 85 |\n\n* Tri-state: Default/True/False. Values ARE case sensitive.\n\n18.3 Compression using Override XML\n\nThe following Override XML undertakes compression only. The CompressionSettings node can be added to an existing ConversionSettings node to combine all other operations available via Override XML.\n\n```xml\n<Override>\n <ConversionSettings>\n <CompressionSettings>\n <RemoveAnnotations>Default</RemoveAnnotations>\n <RemoveBlankPages>Default</RemoveBlankPages>\n <RemoveBookmarks>Default</RemoveBookmarks>\n <RemoveEmbeddedFiles>Default</RemoveEmbeddedFiles>\n <RemoveFormFields>Default</RemoveFormFields>\n <RemoveJavaScript>Default</RemoveJavaScript>\n <RemoveMetadata>Default</RemoveMetadata>\n <RemovePageThumbnails>Default</RemovePageThumbnails>\n <PackFonts>Default</PackFonts>\n <PackDocument>Default</PackDocument>\n <RecompressImages>Default</RecompressImages>\n <EnableMRC>Default</EnableMRC>\n <PreserveSmoothing>Default</PreserveSmoothing>\n <DownscaleImages>Default</DownscaleImages>\n <EnableColorDetection>Default</EnableColorDetection>\n <EnableCharRepair>Default</EnableCharRepair>\n <EnableJPEG2000>Default</EnableJPEG2000>\n <EnableJBIG2>Default</EnableJBIG2>\n <JBIG2PMSThreshold>85</JBIG2PMSThreshold>\n <DownscaleResolution>150</DownscaleResolution>\n <DownscaleResolutionMRC>150</DownscaleResolutionMRC>\n <ImageQuality>ImageQualityDefault</ImageQuality>\n </CompressionSettings>\n </ConversionSettings>\n</Override>\n```\n\nPlease note that you need a PDF Converter Professional add-on license in addition to a valid PDF Converter Services or PDF Converter for SharePoint License to use this functionality.\n\n19 Extract Key-Value Pairs\n\nAs of version 11.1 PDF Converter can extract information about key-value pairs in pdf document. The information can be extracted as:\n\n- XML (eXtensible Markup Language)\n- JSON (JavaScript Object Notation)\n- CSV (Comma Separated Values)\n\nAdditional information can be included such as Key and/or Value Bounding Box, Page Number, Confidence, and Data Type.\n\n19.1 Object Model\n\n19.2 Extract Key Value Pairs using SharePoint Designer workflow\n\nOnce a version of PDF Converter greater than 11.1 has been installed you will find a number of new Workflow Activities in SharePoint Designer. This will include **Extract Key-Value Pairs from a PDF**. The workflow sentence is consistent with other Muhimbi Workflow Activities.\n\nExtract Key-Value pairs from [this document](#) to [this url](#), [the same file name](#) output format JSON/XML/CSV, with expected keys [Expected Keys](#) over page range [page range](#), in [English](#) language(s) with confidence threshold [75%](#) at DPI [300](#). Trim symbols [Yes/No](#) and autorotate [Yes/No](#). Store the converted item details in List ID: [Variable: List ID](#), Item ID: [Variable: List Item ID](#)\n\n- **This document**: Specify which document to convert. Select the option and make sure **Current Item** is selected.\n- **This url**: Specify the location the converted file will be written to. The following options are available:\n - Leave it empty: When no value is specified then the converted document is written to the same folder as the source file.\n - Site Relative URL: By specifying a URL relative to the current site, e.g., `/subsite/shared_documents/PDF_Files`, any folder location in the current site collection can be targeted.\n - Web Application relative URL: Using a URL that is relative to the entire web application, e.g., `/sites/Press_Office/Public_Documents/To_Distribute`, any folder location in any site collection can be targeted.\n- **The same file name**: The name of the converted file can be specified here. In our case we’ll leave it empty to make sure we use the same name as the original document.\n- **JSON/XML/CSV**: Select the desired output format.\n- **Expected Keys**: Add expected keys JSON here, see 19.4 – Expected Keys. Leave empty to retrieve all possible discovered data.\n- **Page range**: Select range of pages for extraction, use an asterisk for all pages.\n- **English (language)**: Enter the languages to use. Multiple languages can be used – concatenate with the + symbol – i.e. eng+fra\n- **75% (confidence threshold)**: Confidence threshold for data to be extracted.\n- **300 (DPI)**: DPI for OCR processing.\n- **Yes/No (trim symbols)**: Trim leading/trailing symbols from the values.\n- **Yes/No (autorotate)**: Automatically rotate the page\n- **Variable: List ID**: A new workflow variable named List ID is automatically created. After the file has been converted, this variable will contain the ID of the list the converted file was saved to. This can later be fed into another action in order to manipulate this file further.\n- **Variable: List Item ID**: A new workflow variable named ‘List Item ID’ is automatically created. After the file has been converted, this variable will\n\ncontain the ID of the item the converted file was saved to. This can later be fed into another action in order to manipulate this file further.\n\n19.3 Extract Key Value Pairs using Nintex Workflows\n\nPDF Converter 11.1 and above comes with an additional set of Nintex Workflow Actions. Two of them – *Extract key-value pairs* and *Extract value for a key* – provides the functionality to extract meaningful, structured information from a PDF document or image. Leveraging AI, ML, and adaptive layout understanding, you can automatically extract information such as phone numbers, IBANs, credit cards, names, and email addresses.\n\n19.3.1 Extract key-value pairs\n\nThe *Extract key-value pairs* Nintex Workflow action is designed to extract multiple key-value pairs from a PDF document. Like the matching SharePoint Designer workflow, it is possible to retrieve everything Muhimbi’s data engine can find or just a subset.\n\n- **Destination Path**: Enter the path of the destination file to save extracted data into, either:\n - Leave empty to use the same directory as the source file.\n - A relative path to a sub site / document library / folder.\n\nAn absolute path to a different site collection.\n\nPlease make sure the path does not include the host name, e.g., 'http://your site/...'. For more details see Appendix - Specifying path and file names.\n\n- **Output File Name**: The name of the file to save the extracted data into. Leave empty to use the source file.\n\n- **Output Format**: The output data can be stored in an XML, JSON or a plain CSV file.\n\n- **Expected Keys**: Add the expected keys JSON here, see Expected Keys. Leave empty to retrieve all possible discovered data.\n\n- **Page Range**: Select range of pages for extraction, use an asterisk for all pages.\n\n- **Language**: Languages to use (multiple languages can be used – concatenate with the + symbol – i.e. eng+fra)\n\n- **OCR resolution (DPI)**: DPI for OCR processing.\n\n- **Confidence threshold**: Confidence threshold for data to be extracted.\n\n- **Trim symbols**: Trim leading/trailing symbols from the values.\n\n- **Autorotate**: Automatically rotate the page.\n\n- **Out List ID**: If you wish to carry out further actions on the target file, e.g., perform a check-in, then you can optionally write the ID of the List that holds the target file to a workflow variable of type String.\n\n- **Out List Item ID**: Similarly, to Out List ID, the item ID of the target file can optionally be written to a workflow variable of type Item ID (in SharePoint 2007) or Integer (in SharePoint 2010 and later versions).\n\n- **Source List ID & List Item**: The item that triggered the workflow is used as the source item by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use the same data types as used by Out List ID and Out List Item ID.\n\n**Error Handling**: Similar to the way some of Nintex’ own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi’s Workflow Activities allow the same. By default, this facility is disabled meaning that any error terminates the workflow.\n\n19.3.2 Extract value for a key\n\nThe *Extract value for a key* Nintex Workflow action is designed to retrieve one single value for the given key from a PDF document.\n\n- **Key**: Enter the key you would like to retrieve the value for. List its synonyms on subsequent lines. For example\n - “Invoice number”\n - Invoice no.\n - Inv no”\n\n- **Page Range**: Select range of pages for extraction, use an asterisk for all pages.\n\n- **Language**: Languages to use (multiple languages can be used – concatenate with the + symbol – i.e. eng+fra)\n\n- **OCR resolution (DPI)**: DPI for OCR processing.\n\n- **Confidence threshold**: Confidence threshold for data to be extracted.\n\n- **Trim symbols**: Trim leading/trailing symbols from the values.\n\n- **Autorotate**: Automatically rotate the page.\n\n- **Output Value**: The recognized value will be stored in this variable (type String)\n\n- **Source List ID & List Item**: The item that triggered the workflow is used as the source item by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use the same data types as used by Out List ID and Out List Item ID.\n\n19.4 Expected Keys\n\nThe user uses JSON text to declare Expected Keys. These specific keys will be added to the output file if a value is found. Synonyms can also be declared for each Expected Key, so that a match for any of the synonyms will be counted as a match for the Expected Key.\n\nAn example is below. For example, we have used total and invoice number as the expected keys. grand total is a synonym for ‘total’, and there are two synonyms for invoice number in invoice no and inv no.\n\n[\n {\n \"expectedKey\": \"total\",\n \"synonyms\": [\"grand total\"]\n },\n {\n \"expectedKey\": \"invoice number\",\n \"synonyms\": [\"invoice no\", \"inv no\"]\n }\n]\n\n19.5 CSV Output Warning\n\nCSV is a format commonly used by spreadsheet programs. These programs commonly transform numerical data or formula, and will save these transformations, overwriting the original data. To prevent these transformations, we add an apostrophe to the start of any possible transformations. e.g. the phone number +44 115 496 0999 will appear as ‘+44 115 496 0999 in the CSV only. The transformations are listed below.\n\n- Formula - these are generally for values that begin with +, -, =, or @, we add an apostrophe at the beginning for the CSV output. This prevents the CSV from producing unintended formulas and functions from these values.\n\n- Dates/Times – this covers many cases of date and time formats, as data can often be mistaken as a date or time, and then irreversibly transformed.\n\n- Long Numbers – this covers numbers that are 11 digits or longer, as they are transformed to decimal notation We recommend removing the apostrophes when extracting the data. This only affects CSV output, so it may be easier to extract data from the other formats if possible.\n\n20 Extract Text\n\nAs of version 11.1 PDF Converter can extract searchable text from a PDF document without OCR.\n\n20.1 Object Model\n\n20.2 Extract Text from PDF using SharePoint Designer workflow\n\nOnce a version of PDF Converter greater than 11.1 has been installed you will find a number of new Workflow Activities in SharePoint Designer. This will include *Extract text from PDF*.\n\nThe workflow sentence is consistent with other Muhimbi Workflow Activities.\n\n- **This document**: Specify which document to convert. Select the option and make sure *Current Item* is selected.\n- **This url**: Specify the location the converted file will be written to. The following options are available:\n - Leave it empty: When no value is specified then the converted document is written to the same folder as the source file.\n - Site Relative URL: By specifying a URL relative to the current site, e.g., `subsite/shared documents/PDF Files`, any folder location in the current site collection can be targeted.\n - Web Application relative URL: Using a URL that is relative to the entire web application, e.g., `/sites/Press Office/Public Documents/To Distribute`, any folder location in any site collection can be targeted.\n- **The same file name**: The name of the converted file can be specified here. In our case we’ll leave it empty to make sure we use the same name as the original document.\n\n• **Page range**: Select range of pages for extraction, use an asterisk for all pages.\n\n• **Page separator (if any)**: Text to show as page separator.\n\n• **Top/bottom**: Place the page separator text at the top or bottom of the page.\n\n• **Include/exclude (meta data)**: Control if the source file’s SharePoint metadata is copied to the destination file.\n\n• **Variable: List ID**: A new workflow variable named *List ID* is automatically created. After the file has been converted, this variable will contain the ID of the list the converted file was saved to. This can later be fed into another action in order to manipulate this file further.\n\n• **Variable: List Item ID**: A new workflow variable named ‘List Item ID’ is automatically created. After the file has been converted, this variable will contain the ID of the item the converted file was saved to. This can later be fed into another action in order to manipulate this file further.\n\n### 20.3 Extract Text using Nintex workflows\n\nPDF Converter 11.1 and above comes with an additional set of Nintex Workflow Actions. The *Extract text from PDF document* workflow action can be used to extract textual information from PDF documents.\n\n- **Destination Path**: Enter the path of the destination file to save extracted data into, either:\n - Leave empty to use the same directory as the source file.\n - A relative path to a sub site / document library / folder.\n\nAn absolute path to a different site collection.\n\nPlease make sure the path does not include the host name, e.g., 'http://your site/...'. For more details see Appendix - Specifying path and file names.\n\n- **Output File Name**: The name of the file to save the extracted data into. Leave empty to use the source file.\n\n- **Page Range**: Select range of pages for extraction, use an asterisk for all pages.\n\n- **Page Separator**: Text to show as page separator.\n\n- **Separator Placement**: You have the option to place page separator at the top or the bottom of the page.\n\n- **Meta data**: Control if the source file’s SharePoint meta-data is copied to the destination file.\n\n- **Out List ID**: If you wish to carry out further actions on the target file, e.g., perform a check-in, then you can optionally write the ID of the List that holds the target file to a workflow variable of type *String*.\n\n- **Out List Item ID**: Similarly, to Out List ID, the Item ID of the target file can optionally be written to a workflow variable of type *Item ID* (in SharePoint 2007) or *Integer* (in SharePoint 2010 and later versions).\n\n- **Source List ID & List Item**: The item that triggered the workflow is used as the source item by default. You can optionally specify the ID of a different List and List Item using workflow variables. Please use the same data types as used by Out List ID and Out List Item ID.\n\n**Error Handling**: Similar to the way some of Nintex’ own Workflow Activities allow errors to be captured and evaluated by subsequent actions, all of Muhimbi’s Workflow Activities allow the same. By default, this facility is disabled meaning that any error terminates the workflow.\n\n21 Troubleshooting & Other common tasks\n\nAlthough the PDF Converter is a user friendly, robust and intuitive application, some questions may arise during the day-to-day operation of the software. This section provides some pointers to answer common questions.\n\nIf you still have questions after reading this chapter then please check out the links in chapter 1 *Introduction* as well as our [comprehensive Knowledge Base](#).\n\n### 21.1 The PDF Converter functionality is not available\n\nWhen the PDF Conversion functionality is not displayed on a file’s context menu, or in the Actions menu of the document library, then this may be due to the following:\n\n1. The PDF Converter has either not been installed on the server or has not been activated.\n\n Please ask your SharePoint administrator to enable the *Muhimbi PDF Converter* on your Web Application.\n\n2. The PDF Converter has been installed, but you are using a non-standard Document or Forms Library.\n\n Please ask your SharePoint administrator to consult section 3.5.5 of the PDF Converter Administration Guide.\n\n### 21.2 Converting documents takes a very long time\n\nIn general, the PDF Converter is a very fast application. However, depending on the size and complexity of the documents that are being converted, the conversion process may take some time.\n\nWhen converting multiple large documents in one go, you may want to consider converting them in batches as the maximum processing time – via the SharePoint user interface – is 30 minutes, after which an error will be displayed.\n\n21.3 The PDF file does not look exactly the same as the source file\n\nAlthough the PDF Converter for SharePoint converts documents with very high fidelity and reliability, there are some situations that may cause the converted documents to look different from the source files. The main reasons for this are as follows:\n\n1. One or more fonts used by the document are not installed on the Document Conversion Server. Ask your Administrator to install the correct fonts.\n\n2. The spacing of the characters in InfoPath documents doesn’t look correct. Unfortunately, InfoPath does not deal well with certain fonts, even when these fonts have been installed on the server. Try using a different font or create a separate InfoPath Print View.\n\n21.4 An evaluation message is displayed in the UI and converted documents\n\nWhen an evaluation message is displayed on each screen and in each converted document then something may be wrong with your license or your license has not been installed. Please contact your SharePoint administrator who will be able to find additional information in the Administration Guide for this product.\n\n21.5 InfoPath Forms fail to convert\n\nWhen InfoPath documents fail to convert then please contact your SharePoint administrator and ask him to consult section 3.5 in the Administration Guide.\n\n21.6 Converting file formats that are not supported\n\nThe PDF Converter supports a large number of source file formats. Support for additional formats can be added by following the instructions in the Administration Guide under Appendix - Creating Custom Converters.\n\n21.7 Nintex Workflow Activities are not working as expected after upgrading\n\nIf you encounter any Nintex Workflow related issues after upgrading to a new version of the Muhimbi PDF Converter for SharePoint then make sure the client side browser cache is cleared. If problems persist then please ask your SharePoint Administrator to review section 3.5.13 in the Administration Guide.\n\nAlso make sure the Muhimbi Nintex Workflow Feature is enabled on the relevant Web Application.\n\n21.8 Files uploaded via Windows Explorer do not trigger ‘Insert’ watermarks\n\nWhen using the watermarking facilities to automatically apply a watermark when a new file is uploaded then the appropriate event is not triggered by SharePoint 2010 when uploading the file using Windows File Explorer. This is related to a bug in SharePoint, the *Update* event is triggered instead.\n\nAs a workaround either make sure all files are uploaded using the web browser or apply watermarks to new files using a SharePoint Designer Workflow, Visual Studio Workflow or Nintex Workflow.\n\n21.9 ‘Watermark on Open’ does not show watermarks\n\nIf the *Watermark on Open* facility is used and watermarks do not show up when opening a PDF file then please check the following:\n\n1. If the PDF File was previously opened by a user before this facility was enabled, the browser may cache the previous version of the document. To solve this problem clear the browser cache.\n\n2. The Web Application scoped Feature named ‘Muhimbi PDF Converter - Automatic Document Processor’ must be enabled. For details please ask your SharePoint administrator to enable the appropriate feature as described in section 2.2.3 of the Administration Guide.\n\n21.10 Changing the default merge bookmark and sort fields\n\nThe PDF Converter ships with a powerful facility that allows multiple files to be merged together. It even allows fields to be selected to sort files by and to use as PDF bookmarks. However, the default options (sort by *Modified*, use *Title* as PDF bookmark) may not be suitable for your purposes. For details on how to change this behaviour see section 3.5.18 in the Administration Guide.\n\nAppendix - Web Services Object Model\n\nAlthough the Object Model exposed by the web service is easy to understand, the system provides very powerful functionality, including watermarking, merging and fine-grained control over how PDF files are generated.\n\nAs outlined in the image below, the web service contains 5 main methods:\n\n- **Convert**: Convert the file in the `sourceFile` byte array using the specified `openOptions` and `conversionSettings`. The generated PDF or XPS file is returned as a byte array as well.\n\n- **ExtractKeyValuePairs**: Extract Key-Value Pairs from the PDF document, with or without OCR, including the option to extract certain expected keys (with synonyms).\n\n- **ExtractText**: Extract text from a PDF file\n\n- **GetConfiguration**: Retrieve information about which converters are supported and the associated file extensions. Consider calling this service once to retrieve a list of valid file extensions and check if a file is supported before it is submitted to the web service. This will prevent a lot of redundant traffic resulting in increased scalability.\n\n- **GetDiagnostics**: Run a diagnostics test that carries out an internal end-to-end test for each specified converter type. Call this method to check if the service and all prerequisites have been deployed correctly.\n\nThe `ApplySecurity`, `ApplyWatermark` and `ProcessChanges` methods are identical at this moment in time and are provided for convenience only. They all take the same parameters as the `Convert` method, but they can act on PDF files only and basically apply whatever combination of Watermarks, Security Settings and other information is provided. The WSDL can be found at the following location. Change `localhost` to the actual host name if the MDCS is located on a different machine.\n\nhttp://localhost:41734/Muhimbi.DocumentConverter.WebService/?wsdl\n\nA full discussion of the entire object model is out of the scope of this document. For full details see the [PDF Converter Services User & Developer Guide](#).\n\n## Appendix - Merge codes\n\n| Field Name | Description | Web Service | Workflows | WM on Open | WM on Insert<sup>20</sup> | WM on Update<sup>20</sup> |\n|---------------------|-----------------------------------------------------------------------------|-------------|-----------|------------|--------------------------|--------------------------|\n| (LONG_DATE) | Long version of the date, e.g. 18 April 2011. | V | V | V | V | V |\n| (LONG_TIME) | Long version of the current time, e.g. 12:35:48. | V | V | V | V | V |\n| (DATE) | Short version of the date, e.g. 7/03/2011. | V | V | V | V | V |\n| (/TIME) | Short version of the current time, e.g. 12:35. | V | V | V | V | V |\n| (/PAGE) | The number of the current page in the PDF or PPTX file. This value is | V | V | V | V | V |\n| | automatically updated for every page. (Not supported for DOCX and XLSX) | | | | | |\n| (NUMPAGES) | The number of pages in the PDF or PPTX file. | V | V | V | V | V |\n| Any column name | Any SharePoint column / field defined on the list such as {Title}, | | | | Using workflow fields | V |\n| | {Author}. Please use (case sensitive) internal field names. A full list can | | | | | (Lists only) |\n| | be found at https://aarebrot.net/blog/2008/07/frodes-awesome-list-of-sharepoint-column-field-ids-for-sharepoint-2007/ | | | | | |\n| {HTTP_HOST} | Returns the name of the Web server. This may or may not be the same as | | | | V | |\n| | SERVER_NAME depending on type of name resolution you are using on your Web | | | | | |\n| | server (IP address, host header). | | | | | |\n| {HTTP_REFERER} | Returns a string that contains the URL of the page that referred the | | | | V | |\n| | request to the current page using an HTML <A> tag. Note that the URL is | | | | | |\n| | the one that the user typed into the browser address bar, which may not | | | | | |\n| | include the name of a default document. | | | | | |\n| {HTTP_URL} | Returns the raw, encoded URL, for example, /vdir/default.asp?querystring. | | | | V | |\n| {HTTP_USER_AGENT} | Returns a string describing the browser that sent the request. | | | | V | |\n| {LOGON_USER} | The Windows account that the user is impersonating while connected to your | | | | V | |\n| | Web server. Use REMOTE_USER to view the raw user name that is contained in | | | | | |\n| | the request header. | | | | | |\n| {REMOTE_ADDR} | The IP address of the remote host (identifying the user) that is making the| | | | V | |\n| | request. | | | | | |\n| {REMOTE_HOST} | The name of the host that is making the request. If the server does not | | | | V | |\n| | have this information, it will set REMOTE_ADDR and leave this empty. | | | | | |\n| {REMOTE_USER} | The name of the user as it is derived from the authorization header sent by | | | | V | |\n| | the client, before the user name is mapped to a Windows account. If you | | | | | |\n| | have an authentication filter installed on your Web server that maps | | | | | |\n| | incoming users to accounts, use LOGON_USER to view the mapped user name. | | | | | |\n| {SERVER_NAME} | The server's host name, DNS alias, or IP address as it would appear in self-referencing URLs. | | | | V | |\n| {URL} | Gives the base portion of the URL, without any querystring or extra path | | | | V | |\n| | information, for example, /vdir/default.asp. | | | | | |\n\n---\n\n<sup>20</sup> Due to limitations in SharePoint 2007, automatic watermarking for Insert and Update events are not supported on Document Libraries. They are supported on Lists and in SharePoint 2010. Use Workflows as an alternative (see 13.1)\n\n| Field Name | Description | Web Service | Workflows | WM on Open | WM on Insert<sup>20</sup> | WM on Update<sup>20</sup> |\n|---------------|--------------------------------------------------|-------------|-----------|------------|--------------------------|--------------------------|\n| {USER_NAME} | The user’s name, if available (requires 7.2+). | | | V | | |\n| {USER_EMAIL} | The user’s email, if available (requires 8.0+). | | | V | | |\n\nAppendix - Override default conversion settings\n\nThe Muhimbi PDF Converter for SharePoint is based on an extremely flexible central conversion engine. This engine supports many more options than can realistically be displayed in the limited space available in a SharePoint Designer or Nintex Workflow Activity. As a result, the software defaults to the most common options.\n\nAlthough it has always been possible to override these default settings (See the Administration Guide, section 2.3.2), those changes are global and affect all operations across the SharePoint Farm. To improve this situation version 6.1 introduces a new facility that allows the default settings to be overridden on a request-by-request basis.\n\nThe Convert Document workflow activity (See chapter 9 Cross-Converting between document types) has been extended and the previously reserved Optional Parameters field can now be used to specify 'override settings' using XML based syntax.\n\nAlthough very powerful, the XML syntax and possible values for each XML Element may not immediately be obvious to all users. For full information see the class diagrams and details of the OpenOptions and ConversionSettings classes in the Developer Guide.\n\nThe latest version of this Appendix can be found [in this blog post](#).\n\nThe values that can be overridden are as follows.\n\n```xml\n<Override>\n <OpenOptions>\n <AllowExternalConnections>false</AllowExternalConnections>\n <AllowMacros>None</AllowMacros>\n <FileExtension></FileExtension>\n <OriginalFileName></OriginalFileName>\n <UserName></UserName>\n <Password></Password>\n <RefreshContent>true</RefreshContent>\n </OpenOptions>\n\n <ConversionSettings>\n <ConverterSpecificSettings type=\"ConverterSpecificSettings_WordProcessing\">\n <ProcessDocumentTemplate>false</ProcessDocumentTemplate>\n <RevisionsAndCommentsMarkupMode>InLine</RevisionsAndCommentsMarkupMode>\n <RevisionsAndCommentsDisplayMode>Original</RevisionsAndCommentsDisplayMode>\n </ConverterSpecificSettings>\n\n <OutputFormatSpecificSettings type=\"OutputFormatSpecificSettings_PDF\">\n <FastWebView>false</FastWebView>\n <EmbedAllFonts>false</EmbedAllFonts>\n <SubsetFonts>false</SubsetFonts>\n <PostProcessFile>false</PostProcessFile>\n <ViewerPreferences>\n <CenterWindow>true</CenterWindow>\n <NavigationPane>Bookmarks</NavigationPane>\n </ViewerPreferences>\n </OutputFormatSpecificSettings>\n </ConversionSettings>\n</Override>\n```\n\n<OCRSettings>\n <Language>English</Language>\n <Performance>Slow</Performance>\n <Paginate>true</Paginate>\n <WhiteList></WhiteList>\n <BlackList></BlackList>\n <Regions>\n <OCRRegion>\n <X>100</X>\n <Y>100</Y>\n <Width>200</Width>\n <Height>50</Height>\n <StartPage>0</StartPage>\n <EndPage>0</EndPage>\n <PageInterval>1</PageInterval>\n <PageRange></PageRange>\n </OCRRegion>\n </Regions>\n</OCRSettings>\n\n<CompressionSettings>\n <RemoveAnnotations>Default</RemoveAnnotations>\n <RemoveBlankPages>Default</RemoveBlankPages>\n <RemoveBookmarks>Default</RemoveBookmarks>\n <RemoveEmbeddedFiles>Default</RemoveEmbeddedFiles>\n <RemoveFormFields>Default</RemoveFormFields>\n <RemoveJavaScript>Default</RemoveJavaScript>\n <RemoveMetadata>Default</RemoveMetadata>\n <RemovePageThumbnails>Default</RemovePageThumbnails>\n <PackFonts>Default</PackFonts>\n <PackDocument>Default</PackDocument>\n <RecompressImages>Default</RecompressImages>\n <EnableMRC>Default</EnableMRC>\n <PreserveSmoothing>Default</PreserveSmoothing>\n <DownscaleImages>Default</DownscaleImages>\n <EnableColorDetection>Default</EnableColorDetection>\n <EnableCharRepair>Default</EnableCharRepair>\n <EnableJPEG2000>Default</EnableJPEG2000>\n <EnableJBIG2>Default</EnableJBIG2>\n <JBIG2PMSThreshold>85</JBIG2PMSThreshold>\n <DownscaleResolution>150</DownscaleResolution>\n <DownscaleResolutionMRC>150</DownscaleResolutionMRC>\n <ImageQuality>ImageQualityDefault</ImageQuality>\n</CompressionSettings>\n\n<StartPage>1</StartPage>\n<EndPage>1</EndPage>\n<Fidelity>High</Fidelity>\n<Format>PDF</Format>\n<GenerateBookmarks>Disabled</GenerateBookmarks>\n<OpenPassword></OpenPassword>\n<OwnerPassword></OwnerPassword>\n<SecurityOptions>DisableContentAccessibility</SecurityOptions>\n<PageOrientation>Default</PageOrientation>\n<PDFProfile>PDF_A1B</PDFProfile>\n<Quality>OptimizeForPrint</Quality>\n<Range>VisibleDocuments</Range>\n<TOCSettings>...</TOCSettings>\n\n</ConversionSettings>\n\n</Override>\n\nPlease note:\n\n- When entering values only specify those fields you want to override, leave all other fields completely out (don’t just provide empty values, delete the entire line. (See the examples below)\n\n- All values are case sensitive.\n\n- **Boolean values (true / false) need to be in all lowercase.**\n\n- There is no need to specify the name of the enumeration, e.g. in `RevisionsAndCommentsMarkupMode`\n\n- In the `ConverterSpecificSettings` element you must specify the ‘type’ attribute to specify the exact type.\n\n- When specifying multiple values, e.g. in the `SecurityOptions` element, then please separate these options using a blank space.\n\n- The `OutputFormatSpecificSettings` property requires version 7.0 of the PDF Converter or newer.\n\n- The `TOCSettings` property requires version 7.3 of the PDF Converter or newer.\n\nA number of examples are provided below.\n\n**Make output format dynamic**\n\nIf a workflow must have the ability to convert to different file formats, depending on a workflow parameter or column value, then you cannot use the normal drop down menu to pre-select the output format. Instead specify the following XML, position the cursor after `<Format>` and add a reference to the field that holds the *output format*, e.g. XLS, PDF, DOCX etc.\n\n```xml\n<Override>\n <ConversionSettings>\n <Format></Format>\n </ConversionSettings>\n</Override>\n```\n\n**Convert MS-Word files with different revision tracking options**\n\nMS-Word files support *revision tracking*, which is ideal for visualising what has changed in a document. By default the PDF Converter displays the *Final* version of the document and doesn’t show the individual revisions. However, in some situations you may want to display these revisions and control how they are displayed (in-line or in balloons).\n\nThe XML to override these settings is as follows\n\n```xml\n<Override>\n <ConversionSettings>\n <ConverterSpecificSettings type=\"ConverterSpecificSettings_WordProcessing\">\n <ProcessDocumentTemplate>true</ProcessDocumentTemplate>\n <RevisionsAndCommentsMarkupMode>InLine</RevisionsAndCommentsMarkupMode>\n <RevisionsAndCommentsDisplayMode>OriginalShowingMarkup</RevisionsAndCommentsDisplayMode>\n </ConverterSpecificSettings>\n </ConversionSettings>\n</Override>\n```\n\nThe possible values for `RevisionsAndCommentsMarkupMode` are:\n\n- **InLine**: Show all revisions Inline.\n- **Balloon**: Show all revisions in balloons.\n- **Mixed**: Show only comments and formatting in balloons.\n\nThe possible values for `RevisionsAndCommentsDisplayMode` are:\n\n- **FinalShowingMarkup**: Show the document with all proposed changes highlighted.\n- **Final**: Show the document with all proposed changes included.\n- **OriginalShowingMarkup**: Show the original document with all proposed changes highlighted.\n- **Original**: Show the document before any changes were made.\n\nSimpleMarkup: Shows the final document in simple mark-up, with revisions incorporated, but with no mark-up visible.\n\nTrim page numbers when converting to PDF\n\nIn some situations you may not be interested in all pages of the converted file, e.g. you only want to convert the cover page (Page 1). To achieve this just set the StartPage and EndPage to 1 as follows:\n\n```xml\n<Override>\n <ConversionSettings>\n <StartPage>1</StartPage>\n <EndPage>1</EndPage>\n </ConversionSettings>\n</Override>\n```\n\nWhen the start or end page should not be limited, specify 0 inside the element or remove the element. Do not include empty elements, e.g. `<EndPage></EndPage>`, as this does not represent a valid number. For example, to start conversion at the second page, and include all pages to the very last page, use the following:\n\n```xml\n<Override>\n <ConversionSettings>\n <StartPage>2</StartPage>\n </ConversionSettings>\n</Override>\n```\n\nSpecify ‘open’ passwords for secured documents\n\nIf your MS-Word files have been saved using a password then these files cannot be converted. However, if the password is known then it can be specified as follows.\n\n```xml\n<Override>\n <OpenOptions>\n <Password></Password>\n </OpenOptions>\n</Override>\n```\n\nDisable refreshing of content\n\nBy default the PDF Converter refreshes all content in an MS-Word file, e.g. embedded fields, table of contents, smart parts, etc. If this is not desired then specify the following XML:\n\n```xml\n<Override>\n <OpenOptions>\n <RefreshContent>false</RefreshContent>\n </OpenOptions>\n</Override>\n```\n\nSpecify PDF profile, e.g. PDF/A or a specific PDF Version\n\nThe PDF Converter provides full support for PDF/A output (See Administration Guide), however if you want to use it from workflows it is an all or nothing approach using a flag in the configuration file. To control PDF/A on a request by request basis either use our Web Services Interface or the following XML:\n\n```xml\n<Override>\n <ConversionSettings>\n <!-- Set the output profile -->\n <PDFProfile>PDF_A1b</PDFProfile>\n <!-- Force post processing -->\n <OutputFormatSpecificSettings type=\"OutputFormatSpecificSettings_PDF\">\n <FastWebView>false</FastWebView>\n <EmbedAllFonts>true</EmbedAllFonts>\n <SubsetFonts>false</SubsetFonts>\n <PostProcessFile>true</PostProcessFile>\n </OutputFormatSpecificSettings>\n </ConversionSettings>\n</Override>\n```\n\nThis will make sure that all converted files conform to the PDF/A standard. However, if the source file is already in PDF format, and needs converting to PDF/A, then the SkipPDFFiles setting will need to be disabled first.\n\nThe PDFProfile element supports the following values, please note that the use of this functionality requires a Muhimbi PDF Converter Professional license.\n\n- **PDF_A1B**: Use the PDF/A1b standard for long term archiving.\n- **PDF_A2B**: Use the PDF/A2b standard for long term archiving.\n- **PDF_A3B**: Use the PDF/A3b standard for long term archiving.\n- **PDF_A3U**: Use the PDF/A3u standard (experimental).\n- **PDF_1_1**: PDF 1.1 output (Compatible with Acrobat 2.0 (1994) and later).\n- **PDF_1_2**: PDF 1.2 output (Compatible with Acrobat 3.0 (1996) and later).\n- **PDF_1_3**: PDF 1.3 output (Compatible with Acrobat 4.0 (2000) and later).\n- **PDF_1_4**: PDF 1.4 output (Compatible with Acrobat 5.0 (2001) and later).\n- **PDF_1_5**: PDF 1.5 output (Compatible with Acrobat 6.0 (2003) and later).\n- **PDF_1_6**: PDF 1.6 output (Compatible with Acrobat 7.0 (2005) and later).\n- **PDF_1_7**: PDF 1.7 output (Compatible with Acrobat 8.0 (2006) and later).\n\nChange conversion range\n\nSome document formats such as Excel and PowerPoint allow sheets to be hidden. By default the PDF Converter converts all Visible Sheets / Slides, but perhaps you are only interested in the Active / Selected spreadsheet. This can be controlled using the following XML:\n\n```xml\n<Override>\n <ConversionSettings>\n <Range></Range>\n </ConversionSettings>\n</Override>\n```\n\nThe possible values for `Range` are:\n\n- **VisibleDocuments**: Skips, in case of Excel and PowerPoint, any hidden tabs or slides.\n- **AllDocuments**: Export all tabs or slides in a workspace.\n- **ActiveDocuments**: Exports, in case of Excel, the selected tabs.\n\nSpecify Converter Specific Settings\n\nQuite a few of our converters support settings that are specific to that particular file format. For an example see the Revision Tracking example above. Although enhancements are made all the time, at the time of writing the following Converter Specific Settings are available.\n\n- ConverterSpecificSettings_Cad\n- ConverterSpecificSettings_CommandLineConverter\n- ConverterSpecificSettings_HTML\n- ConverterSpecificSettings_Image\n- ConverterSpecificSettings_InfoPath\n- ConverterSpecificSettings_MSG\n- ConverterSpecificSettings_PDF\n- ConverterSpecificSettings_Presentations\n- ConverterSpecificSettings_Spreadsheets\n- ConverterSpecificSettings_TIFF\n- ConverterSpecificSettings_WordProcessing\n\nFor more detail see the Class Diagrams in the Developer Guide.\n\nSpecify Viewer Preferences\n\nThe PDF Converter allows *PDF Viewer Preferences* to be specified, e.g. Center the PDF Reader Window, Hide the Menu and Toolbars, display the bookmarks pane, etc. For full details see this [blog post](#).\n\nAn example that shows how to set these preferences is provided below. Naturally it can be combined with the other ‘overrides’ discussed previously.\n\n```xml\n<Override>\n <ConversionSettings>\n <OutputFormatSpecificSettings type=\"OutputFormatSpecificSettings_PDF\">\n <FastWebView>false</FastWebView>\n <EmbedAllFonts>false</EmbedAllFonts>\n <SubsetFonts>false</SubsetFonts>\n <PostProcessFile>false</PostProcessFile>\n <ViewerPreferences>\n <CenterWindow>true</CenterWindow>\n <NavigationPane>Bookmarks</NavigationPane>\n <DisplayTitle>false</DisplayTitle>\n <FitWindow>false</FitWindow>\n <HideMenubar>false</HideMenubar>\n <HideToolbar>false</HideToolbar>\n <HideWindowUI>false</HideWindowUI>\n <PageLayout>SinglePage</PageLayout>\n <HideEmptyNavigationPane>false</HideEmptyNavigationPane>\n <PageScalingMode>Default</PageScalingMode>\n <FullScreen>false</FullScreen>\n </ViewerPreferences>\n </OutputFormatSpecificSettings>\n </ConversionSettings>\n</Override>\n```\n\nControl Font Embedding, PDF Version, PDF Fast Web View\n\nAs of version 7.0 a number of facilities have been added to the PDF Converter Professional add-on license. These features allow fonts to be embedded / stripped, Fast Web View (Linearisation) to be enabled and the PDF Version to be changed (anything between PDF 1.1 and 1.7, including PDF/A1b, 2b and 3b). For details see [this blog post](#).\n\nAn example that shows how to specify these new features using the XML based override syntax can be found below. Please make sure that `PostProcessFile` is set to `true` in order to pick up these settings.\n\n```xml\n<Override>\n <ConversionSettings>\n <OutputFormatSpecificSettings type=\"OutputFormatSpecificSettings_PDF\">\n <FastWebView>true</FastWebView>\n <EmbedAllFonts>true</EmbedAllFonts>\n <SubsetFonts>false</SubsetFonts>\n <PostProcessFile>true</PostProcessFile>\n </OutputFormatSpecificSettings>\n </ConversionSettings>\n</Override>\n```\n\nSpecifying which InfoPath views to convert\n\nAs mentioned in the MS-Word revision tracking example above, it is possible to specify Converter Specific Settings. In this example we’ll show how to use this facility to specify which InfoPath views to convert. The same can be achieved at design time or by setting workflow variables, but the example provided below allows view names to be specified at run-time and only requires a single workflow step.\n\nLet’s have a look at the code needed for doing the same via our Web Services based object model (sample code is C#, other languages follow the same structure).\n\n```csharp\nConverterSpecificSettings_InfoPath csc =\n new ConverterSpecificSettings_InfoPath();\ncsc.ConversionViews = new InfoPathView[2];\ncsc.ConversionViews[0] = new InfoPathView();\ncsc.ConversionViews[0].Name = \"NAME-OF-VIEW1\";\ncsc.ConversionViews[1] = new InfoPathView();\ncsc.ConversionViews[1].Name = \"NAME-OF-VIEW2\";\n// ** As we are overriding settings, we need to override ALL of them\ncsc.ConvertAttachments = true;\ncsc.AutoTrustForms = false;\ncsc.ProcessFullTrustForms = true;\ncsc.StripDataObjects = true;\ncsc.StripDotNETCode = true;\nconversionSettings.ConverterSpecificSettings = csc;\n```\n\nWhat is important to realise is that when specifying ConverterSpecificSettings, it is essential that ALL values are specified as fields that are not will be initialised to their default value. The default value for a boolean field is ‘false’, which in this example would mean that attachments are not converted and InfoPath Data Objects are not stripped. Change these values in line with your needs, but unless you are 100% sure what each value means, keep them as specified in this example.\n\nWhen serialising the code into XML we get the following:\n\n```xml\n<Override>\n <ConversionSettings>\n <ConverterSpecificSettings type=\"ConverterSpecificSettings_InfoPath\">\n <ConversionViews>\n <InfoPathView>\n <Name>NAME-OF-VIEW1</Name>\n </InfoPathView>\n <InfoPathView>\n <Name>NAME-OF-VIEW2</Name>\n </InfoPathView>\n </ConversionViews>\n <!-- ** As we are overriding settings, we need to override ALL -->\n <ConvertAttachments>true</ConvertAttachments>\n <AutoTrustForms>true</AutoTrustForms>\n <ProcessFullTrustForms>true</ProcessFullTrustForms>\n <StripDataObjects>true</StripDataObjects>\n <StripDotNETCode>true</StripDotNETCode>\n </ConverterSpecificSettings>\n </ConversionSettings>\n</Override>\n```\n\nCarrying out OCR processing during conversion\n\nAs of version 7.1 the Muhimbi PDF Converter supports the use of OCR (Optical Character Recognition) during the conversion process. This can be used to convert an image into a searchable PDF or make bitmap based PDFs (scanned PDFs) searchable and indexable. For details see chapter 15 Carry out OCR (Optical Character Recognition).\n\nStarting with version 7.2 the PDF Converter includes dedicated OCR Workflow Actions. However, if you are running an older version of the software, or you have a good reason to carry out OCR using the Convert Document Workflow Activity, then specify OCR settings using the XML syntax described below.\n\nImage files can be converted into searchable PDFs using the syntax below. When converting image based PDFs into searchable PDFs the syntax is the same, however the SkipPDFFiles setting will need to be disabled and the PDF Pass-through converter needs to be enabled in our Central Admin screen.\n\nPlease note that for use in a Production environment, the OCR facilities require a PDF Converter Professional add-on license.\n\n```xml\n<Override>\n <ConversionSettings>\n <OCRSettings>\n <Language>English</Language>\n <Performance>Slow</Performance>\n <Paginate>true</Paginate>\n <Whitelist></Whitelist>\n <Blacklist></Blacklist>\n <Regions>\n <OCRRegion>\n <X>100</X><Y>100</Y><Width>200</Width><Height>50</Height>\n <StartPage>0</StartPage><EndPage>0</EndPage>\n <PageInterval>1</PageInterval><PageRange></PageRange>\n </OCRRegion>\n </Regions>\n </OCRSettings>\n </ConversionSettings>\n</Override>\n```\n\nThe Regions element can be removed unless you wish to OCR only a certain part of the page or specific pages. When specifying OCRRegions the StartPage, EndPage, PageInterval and PageRange elements are optional.\n\nThe unit of measure for all coordinates is pt (Points, 1/72 inch).\n\nGenerate a table of contents\n\nAs of version 7.3 the Muhimbi PDF Converter comes with a brilliant new facility to generate tables of content for individual conversions as well as merge operations. Chapter 17 describes the basics and, although it is a little bit ‘technical’, explains how the underlying system works as well as a XSL based sample template.\n\nLet’s have a look at a typical example.\n\n```xml\n<Override>\n <ConversionSettings>\n <TOCSettings>\n <MinimumEntries>0</MinimumEntries>\n <Bookmark>Table Of Contents</Bookmark>\n <Location>Front</Location>\n <Properties>\n <NameValuePair>\n <Name>title</Name>\n <Value>Custom Title</Value>\n </NameValuePair>\n </Properties>\n <Template>http://YourServer/SomeSiteCollection/SomeDocLib/TOC.xsl</Template>\n </TOCSettings>\n </ConversionSettings>\n</Override>\n```\n\nThis XML is similar to the C# sample code in Chapter 17, which also provides details about the various properties such as `MinimumEntries` and `Location`. The recommended approach is to upload the XSL template to a SharePoint document library and specifying its location in the `Template` element.\n\nIf you wish to merge a number of documents AND add a table of contents for the entire - merged - PDF then this can be achieved as follows:\n\n1. (Convert) and merge multiple files into a single PDF using the *Merge Documents into PDF* workflow activity (See the various examples in chapter 10).\n\n2. Process the generated PDF by passing it into the *Convert Document* workflow activity and specifying `TOCSettings` using the XML override syntax.\n\nThe XML ‘overriding’ facility works in SharePoint Designer Workflows (See 9.1), K2 (See 5) as well as Nintex Workflows (See 9.2).\n\nAppendix - Specifying path and file names\n\nRegardless of the operation carried out by the Muhimbi PDF Converter, input and/or output file names, including paths, need to be specified. Although this has been made as intuitive as possible, we still get questions about it from time to time. We hope to clarify the situation in this Appendix. The latest version of this Appendix can be found online at https://www.muhimbi.com/blog/specifying-paths-and-file-names-when-using-the-pdf-converter-for-sharepoint/.\n\nTarget the same directory / use the same file name as the source file\n\nIf you wish to read from or write to the same location as the source file that is being processed, e.g. you are using a SharePoint Designer workflow to automatically convert files to PDF, then leave the path empty. This works for all situations with the exception of the HTML to PDF Conversion as that is not necessarily associated with a source file (it can convert URLs as well).\n\nIf you wish to use the same name for the target file as the source file then there is no need to specify a file name, the system will generate the name for you. When converting files to PDF the files’ extension will automatically be updated to ‘PDF’, however when the source file is a PDF (e.g. when applying PDF Security) then omitting the file name and path will overwrite the source file. This may be desired, but keep it in mind.\n\nTarget a (sub) folder in the current Document Library\n\nIf you wish to specify a (sub) folder in the same Document Library as the source file then you must specify the Document Library name as well as the path to the folder. Just specifying the folder name will not work. For example, to convert a file to the ‘Archives/PDFs’ folder in the Shared Documents library, specify:\n\nShared Documents/Archives/PDFs/\n\nMake sure you use a trailing slash as that is used in some cases to resolve potentially conflicting file and folder names. Please do not start the path with a slash in this particular case.\n\nTarget a different Document Library\n\nTo specify a location in a different Document Library in the current Site, specify the name of the Document Library followed by any folders. E.g. if your workflow activity is operating on a file in the Shared Documents library, but you want to write the generated file to the PDF folder in the Archive Document Library then specify the following as the path:\n\nArchive/PDF/\n\nMake sure you use a trailing slash when specifying folders as that is used in some cases to resolve potentially conflicting file and folder names.\n\nTarget a Sub Site\n\nSharePoint Site Collections can contain multiple Sub Sites. To write a file to a location in a Sub Site specify the name of that Sub Site followed by the name of the Document Library followed by any folder names. For example if the current workflow is acting on a file in the root web of a Site Collection and you wish to write it to the PDFs folder in the Paid Document Library in the Invoices Sub Site specify the following path:\n\nInvoices/Paid/PDFs/\n\nMake sure you use a trailing slash when specifying folders as that is used in some cases to resolve potentially conflicting file and folder names.\n\nTo target a Sub Site ‘next’ to the current site, use an absolute path. For details see Targeting a different Site Collection below. Please note that ‘traditional’ relative path notation such as ‘../..’ is not supported.\n\nTarget a different Site Collection\n\nIn order to read from or write to a file in a different site collection you have to use an absolute path starting with ‘/’. For example if a PDF Conversion workflow is running in the Accounting Site collection and the generated PDF file should be written to the Archiving site collection in the PDFs folder in the Accounting Document Library, use the following path:\n\n/Archiving/Accounting/PDFs/\n\nIf all your Site Collections live under ‘/sites/’ then this will need to be reflected in the path, e.g.:\n\n/sites/Archiving/Accounting/PDFs/\n\nPlease do not start absolute paths with http://YourWebApplication/, always start absolute paths with a slash.\n\nTargeting historical files\n\nAs of version 6.0 it is possible to specify specific versions in a file’s history for Merge and Watermark (elements) operations. The syntax is similar to what is described above, for example:\n\nSpecify a document in the same document library (named Automatic Merging):\n\n_vti_history/1536/Automatic Merging/End Page.docx\n\nSpecify a document in a different document library:\n\n_vti_history/1024/Shared Documents/Subfolder/End Page.docx\n\nSpecify a document in a sub-site of the current web:\n\nSubSite/AnotherSubSite/_vti_history/1024/Shared Documents/Empty.pdf\n\nSpecify a document in a different site collection or in a sub web next to the current web:\n\n/sites/PDFTest/_vti_history/512/Shared Documents/introduction.pdf\n\nTarget a different Web Application\n\nAs there are clear security boundaries between SharePoint Web Applications it is not possible to exchange files between them. If this is required then you will need to use a third party Workflow Activity or use Nintex Workflow.\n\nCreating dynamic paths / file names\n\nAll of Muhimbi’s SharePoint Designer and Nintex Workflow activities allow lookup variables to be used in order to generate dynamic paths. For example, in order to make a workflow generic, the name of a source or target File / Library / Folder can be determined at run-time.\n\nFor Nintex Workflow use the ‘Insert Reference’ button\n\nIn SharePoint Designer use the ‘Add Lookup’ button\n\nSome final, generic, hints and tips:\n\n- Never start a path with `http://YourWebApplication/`. Start absolute paths with a ‘/’.\n\n- Some activities support templates in the output file name, e.g. to automatically generate file names when splitting PDFs. For details see chapter 11 Splitting PDFs into multiple documents.\n\n- Although you can use forward (/) as well as back (\\\\) slashes, make it a habit to use forward slashes as SharePoint Designer 2010 (and later) workflows do not always deal well with back slashes.\n\n- No matter where you read from or write to, your user must have access to the location that is being specified.\n\n## Appendix - Watermark field matrix\n\n| Field | Watermark | Text | Pdf | Rtf | Image | Ellipse | Rectangle | Line |\n|----------------|-----------|-------|-------|-------|-------|----------|-----------|------|\n| hPosition | o | o | o | o | o | o | o | o |\n| vPosition | o | o | o | o | o | o | o | o |\n| x | o | o | o | o | o | o | o | m |\n| y | o | o | o | o | o | o | o | m |\n| width | m | m | o | m | o | m | m | - |\n| height | m | m | o | m | o | m | m | - |\n| zOrder | o | o | o | o | o | o | o | o |\n| scaleMode | o | o | o | o | o | o | o | o |\n| scaleX | o | o | o | o | o | o | o | o |\n| scaleY | o | o | o | o | o | o | o | o |\n| rotation | o | o | o | o | o | o | o | o |\n| opacity | o | o | o | o | o | o | o | o |\n| lineColor | - | o | o | o | o | o | o | o |\n| lineWidth | - | o | o | o | o | o | o | o |\n| fillColor | - | o | o | o | o | o | o | - |\n| pageOrientation| o | - | - | - | - | - | - | - |\n| startPage | o | - | - | - | - | - | - | - |\n| endPage | o | - | - | - | - | - | - | - |\n| pageInterval | o | - | - | - | - | - | - | - |\n| pageRange | o | - | - | - | - | - | - | - |\n| content | - | m | - | - | - | - | - | - |\n| fontFamilyName | - | o | - | - | - | - | - | - |\n| fontSize | - | o | - | - | - | - | - | - |\n| fontStyle | - | o | - | - | - | - | - | - |\n| wordWrap | - | o | - | - | - | - | - | - |\n| hAlign | - | o | - | - | - | - | - | - |\n| vAlign | - | o | - | - | - | - | - | - |\n| pdfFilePath | - | - | m | - | - | - | - | - |\n| rtfData | - | - | - | m | - | - | - | - |\n| imageFilePath | - | - | - | - | m | - | - | - |\n| endX | - | - | - | - | - | - | - | m |\n| endY | - | - | - | - | - | - | - | m |\n\n### default available values / remarks\n\n| Field | Values |\n|----------------|---------------------------------------------|\n| hPosition | absolute, random, left, center, right |\n| vPosition | absolute, random, top, middle, bottom |\n| x | number as string |\n| y | number as string |\n| width | number as string |\n| height | number as string |\n| zOrder | int as string, <1 means background, >=1 means foreground |\n| scaleMode | absolute, absolute, exactFit, maintainaspectratio |\n| scaleX | number as string, 1 means 100% |\n| scaleY | number as string, 1 means 100% |\n| rotation | number as string, in degrees |\n| opacity | number as string, [0-100] |\n| lineColor | #ff000000 either #aarrggb or #rrggb hex color |\n| lineWidth | 0 or 1 1 for lines 0 for everything else |\n| fillColor | #ff000000 either #aarrggb or #rrggb hex color |\n| pageOrientation| both, portrait, landscape, both |\n| startPage | 0 will default to the first page |\n| endPage | 0 will default to last page |\n| pageInterval | 0 will default to every page |\n| pageRange | null comma separated list of page numbers or intervals (1-5,7) |\n| content | the text to display |\n| fontFamilyName | Arial name of a font |\n| fontSize | 12 positive number as string |\n| fontStyle | regular, bold, italic, strikeout, underline |\n| wordWrap | wordonly, none, character, word, wordonly |\n| hAlign | center, left, center, right, justify |\n| vAlign | middle, top, middle, bottom |\n| pdfFilePath | path to the watermark pdf file |\n| rtfData | the rtf source as string |\n| imageFilePath | path to the watermark image file |\n| endX | number as string |\n| endY | number as string |\n\n**o** optional \n**m** mandatory\n\nAppendix - Relevant articles on the Muhimbi Blog\n\nThe Muhimbi Blog is updated frequently with new articles related to this product. The following posts are relevant to readers of this User Guide.\n\n- Using the PDF Converter from a SharePoint Designer workflow\n- Convert and merge multiple PDF files using a SharePoint Designer workflow\n- Using the SharePoint Workflow Manager to Convert documents to PDF\n- Using the PDF Converter in combination with SharePoint Online / Office 365\n- Installing The PDF Converter APP in SP2013 & SP2016 (on-premise)\n- Converting multiple SharePoint files to PDF Format using Nintex Workflow\n- Convert to non-PDF formats using Nintex Workflow\n- Watermark PDFs using Nintex Workflow\n- Secure PDFs using Nintex Workflow\n- Convert and Merge PDFs using Nintex Workflow\n- Convert HTML to PDF using Nintex Workflow\n- Copy Meta-Data and set content types using Nintex Workflow\n- Extract PDF Forms Data (PDF, XFDF, XML) using SharePoint or C#, Java, PHP\n- Combining multiple Nintex Workflow Activities into a sequence\n- Copy Meta-Data and set content types using a SharePoint Designer Workflow\n- Convert SharePoint documents to PDF using K2 workflows\n- Watermarking features of the Muhimbi PDF Converter for SharePoint\n- Applying user specific watermarks when a PDF document is opened\n- Apply User Specific PDF Security when a document is opened in SharePoint\n- Convert and merge files to PDF using the SharePoint User Interface\n- PDF/A Support in the Muhimbi PDF Converter Services & SharePoint\n- OCR Facilities provided by Muhimbi's server based PDF Conversion products\n- OCR Scans and Images using SharePoint Designer Workflows\n- OCR Scans and Images using Nintex Workflow\n- Extract text from scanned content using OCR and SharePoint Designer Workflows\n- Extract text from scanned content using OCR and Nintex Workflow\n- OCR Scans and Images using a Web Services based Interface (WSImport)\n- OCR Scans and Images using a Web Services based Interface (.NET)\n- Merging dynamic data into watermarks using the PDF Converter for SharePoint\n- Specifying filtering criteria when automatically applying watermarks in SharePoint\n- Inserting SharePoint List data into a PDF document using a workflow\n- Configure PDF Security from a SharePoint Designer Workflow\n- Splitting PDF Files using a SharePoint workflow\n- Splitting PDF Files using the PDF Converter Web Service (.NET)\n- Converting and merging multiple files using Web Services (.NET)\n- Convert files to PDF Format from Java using Web Services (WSImport)\n- Convert files to PDF Format from Java using Web Services (Axis2)\n\n- Convert files to PDF Format from PHP using a Web Services based interface\n- Convert files to PDF Format from Ruby using a Web Services based interface\n- Set PDF Version, enable Fast Web Views, embed / strip fonts\n- Specifying PDF Viewer Preferences\n- Automatically convert files to PDF using an e-mail enabled Document Library\n- Batch print InfoPath Forms using the PDF Converter for SharePoint\n- Convert InfoPath to MS-Word, Excel, XPS and PDF\n- Cross-Convert document types (xls to xlsx, doc to docx)\n- Converting InfoPath forms including all attachments to a single PDF file\n- Controlling which views to export to PDF format in InfoPath\n- Using SharePoint Forms Services to convert InfoPath forms to PDF format\n- Dealing with hyperlinks when converting InfoPath files to PDF format\n- Programmatically Convert SharePoint HTML pages to PDF format\n- Convert HTML pages to PDF format using the SharePoint User Interface\n- Converting SharePoint Lists to PDF format using a SharePoint Designer Workflow\n- Converting AutoCAD (DXF, DWG) files to PDF\n- Using Third Party CAD Converters with the Muhimbi PDF Converter\n- Converting TIFF files to PDF\n- Converting Outlook MSG files to PDF including attachments\n- Converting files to PDF Format using a Web Services based interface (.NET)\n- Converting files to PDF Format using a Web Services based interface (Java)\n- Invoking the PDF Converter Web Service from Visual Studio 2005 using vb.net\n- Converting PDF files to PDF/A1b using a Web Services based interface\n- Adding custom Converters to Muhimbi's range of PDF Conversion products\n- Embedding SharePoint Document IDs in PDF files and generating Short URLs\n- Specifying paths and file names when using the PDF Converter for SharePoint\n- Muhimbi PDF Converter Deployment scenarios\n- Send rich emails with attachments from a SharePoint Designer Workflow\n- Create Shortened ('TinyURL') links from your SharePoint Workflow\n- SharePoint Designer workflows trigger before properties are set\n- Troubleshooting steps for the PDF Converter for SharePoint\n- Troubleshooting InfoPath to PDF Conversion / Document Converter Architecture\n- Performance metrics for the Muhimbi PDF Converter\n- Adding the PDF Converter to non standard Document and Form Libraries\n- Tuning SharePoint's workflow engine\n\nAppendix - Licensing\n\nAll Muhimbi products are licensed in a way that allows maximum flexibility. Please familiarise yourself with the licensing agreement, particularly section 3 – Grant of License, before purchasing our software.\n\nMuhimbi's software is licensed on a per-server basis. This means that a license is required for every Production and Disaster Recovery server that runs our software. This means all Web Front End servers, all Application Servers participating in workflows (how to determine this) and all servers running the conversion service. Any K2 Workflow Servers that have our K2 integration facilities installed require a license as well.\n\nFor details see:\n\n1. License Agreement.\n2. Details about pricing & licensing.\n\nIn summary we support the following license types.\n\n1. **Free evaluation version**: If the software is installed without a license then you are using the evaluation version. The software is fully functional without any time limits, but an evaluation message will be displayed on most screens, in the workflow history and in any generated document. It is not permitted to use the evaluation version in production environments. Support is provided using any of the means in the Support area on our website.\n\n2. **Basic License**: Starter edition for SharePoint farms consisting of a single combined WFE / App server.\n\n3. **Small Farm License**: Covers a single SharePoint farm consisting of up to 3 servers with support for load balancing and redundancy.\n\n4. **Enterprise License**: Covers an unlimited number of SharePoint Farms, Servers and Users in a single legal entity.\n\n5. **OEM License**: If you wish to bundle our software with your own solution and redistribute it to 3rd parties then you require an OEM License. Please read the details in the Software License Agreement for more information.\n\n Note that you are not allowed to use our Products to develop derived works that offer similar functionality as the Product or expose the features of the Product for use by an unlicensed third party unless agreed with Muhimbi. From a licensing perspective embedding our software in a SAAS based solution is considered redistributing our software and requires an OEM license.\n\nPlease note that some older license types have been discontinued. However, these are still valid for those customers that have purchased them in the past. Please see the License Agreement for details about these old style licenses.\n\n*The PDF Converter for SharePoint license is limited to use from SharePoint environments only. If you wish to invoke the PDF Conversion Service from a non-SharePoint based environment, e.g. Java, .NET or any other Web*\n\nServices capable system then you will need to purchase a license for the PDF Converter Services, which is a separate product.\n\nThe PDF Converter Professional license is an add-on that adds additional functionality to either the PDF Converter for SharePoint or the PDF Converter Services. This functionality, e.g. PDF/A post-processing and OCR, is usually associated with more complex environments and has therefore been separated from the main product. Please note that the PDF Converter Professional is a license that must be applied alongside a valid license of the PDF Converter for SharePoint or PDF Converter services. A separate download of the Professional version of the software is not needed, the license unlocks all functionality."},"books_score":{"kind":"number","value":0.413257896900177,"string":"0.413258"}}},{"rowIdx":8689,"cells":{"content":{"kind":"string","value":"Mini PCI Express Multiport Serial Board Series User Manual\n\nVersion 1.0, December 2022\n\nwww.moxa.com/products\n\n© 2022 Moxa Inc. All rights reserved.\n\nThe software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement.\n\n**Copyright Notice**\n\n© 2022 Moxa Inc. All rights reserved.\n\n**Trademarks**\n\nThe MOXA logo is a registered trademark of Moxa Inc.\nAll other trademarks or registered marks in this manual belong to their respective manufacturers.\n\n**Disclaimer**\n\n- Information in this document is subject to change without notice and does not represent a commitment on the part of Moxa.\n- Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time.\n- Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use.\n- This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication.\n\n**Technical Support Contact Information**\n\nwww.moxa.com/support\n\n# Table of Contents\n\n1. **Introduction** .................................................................................................................. 5 \n - Overview .......................................................................................................................... 5 \n - Mini PCI Express Solution ......................................................................................... 5 \n - ADDC™ (Automatic Data Direction Control) for RS-485 ........................................... 5 \n - Operating System Support ............................................................................................ 5 \n - Moxa Serial Comm Tool ............................................................................................... 6 \n - Applications ..................................................................................................................... 6 \n - Features .......................................................................................................................... 6 \n - Package Checklist .......................................................................................................... 6 \n - Installation Flowchart ..................................................................................................... 7 \n\n2. **Hardware Installation** .................................................................................................. 8 \n - Hardware Installation Procedure ...................................................................................... 8 \n - Mini PCIe Boards Dimension .......................................................................................... 10 \n - CP-102N-T Dimensions ............................................................................................... 10 \n - CP-102N-I-T Dimensions ............................................................................................ 11 \n - CP-132N-T Dimensions ............................................................................................... 11 \n - CP-132N-I-T Dimensions ............................................................................................ 12 \n - CP-104N-T Dimensions ............................................................................................... 12 \n - CP-104N-I-T Dimensions ............................................................................................ 13 \n - CP-134N-I-T Dimensions ............................................................................................ 14 \n - CP-114N-T Dimensions ............................................................................................... 15 \n\n3. **Software Installation** .................................................................................................. 16 \n - Windows Driver .............................................................................................................. 16 \n - Windows 7/8 /8.1/10/11, Server 2008 R2/2012/2012 R2/ 2016 (x64)/2019/2022 .......... 17 \n - Linux Driver(32-bit/64-bit) .......................................................................................... 32 \n\n4. **Serial Programming Tools** .......................................................................................... 34 \n - Moxa PComm .................................................................................................................. 34 \n - Installing PComm ........................................................................................................ 34 \n - PComm Programming Library ...................................................................................... 34 \n - Utilities .......................................................................................................................... 35 \n - Diagnostics (for Moxa boards only) ............................................................................. 35 \n - Monitor ....................................................................................................................... 36 \n - Terminal Emulator ...................................................................................................... 37 \n - ViewCom ..................................................................................................................... 38 \n\n5. **Programming Guide** ................................................................................................... 39 \n - Relative Product List ..................................................................................................... 39 \n - PCI Configuration for Moxa Board ............................................................................... 39 \n - UART Register Structure for MUE250, MUE450, and MUE850 Chips ......................... 40 \n - For Baudrate Settings ................................................................................................... 41 \n - Moxa Board PCI Device ID List .................................................................................... 42 \n - UART Datasheet ............................................................................................................ 42 \n\n6. **Pin Assignments** ........................................................................................................ 43 \n - Mini PCIe Board Accessories Table ............................................................................... 43 \n - CP-102N-T .................................................................................................................... 43 \n - Female Wafer to DB9 Connector Pin Assignments .................................................. 43 \n - CP-102N-I-T .................................................................................................................. 44 \n - Female Wafer to DB9 Connector Pin Assignments .................................................. 44 \n - CP-132N-T .................................................................................................................... 44 \n - Female Wafer to DB9 Connector Pin Assignments .................................................. 44 \n - CP-132N-I-T .................................................................................................................. 45 \n - Female Wafer to DB9 Connector Pin Assignments .................................................. 45 \n - CP-104N-T .................................................................................................................... 46 \n - Female Wafer to DB9 Connector Pin Assignments .................................................. 46 \n - CP-104N-I-T .................................................................................................................. 47 \n - Board Side Pin Assignment ....................................................................................... 47 \n - Device Side Pin Assignment ....................................................................................... 47 \n - CP-134N-I-T .................................................................................................................. 48 \n - Board Side Pin Assignment ....................................................................................... 48\n\nDevice Side Pin Assignment ................................................................. 48\nCP-114N-T ......................................................................................... 49\nBoard Side Pin Assignment ............................................................... 49\nDevice Side Pin Assignment ............................................................... 49\n\n7. Troubleshooting ........................................................................... 50\n\nMoxa’s Mini PCI Express serial boards meet the new slot standard for expansion boards and work with any Mini PCI Express slots. The boards have multiple RS-232/422/485 serial ports to connect data acquisition equipment and other serial devices to a PC.\n\n**Overview**\n\nMoxa’s new Mini PCI Express Multiport Serial Boards family fulfills a customized expansion need and provides a faster response to market. It includes isolated and non-isolated RS-232/422/485 communication cards for a variety of applications and users, such as industrial automation system manufacturers, system integrators, and industrial PC makers.\n\n**Mini PCI Express Solution**\n\nAll mini PCIe Serial Boards feature high performance 16C950 compatible UARTs. Available in 4-port and 2-port versions, they are compatible with all popular operating systems, supports data rates of up to 921.6 kbps, and have 128-byte transmit and receive FIFOs. All mini PCIe serial cards operate in wide temperatures, ranging from -40 to 85°C. In addition, the packaging of all mini PCIe serial cards include door brackets, allowing the board to be installed in Moxa IPC Expansion slots.\n\n**ADDC™ (Automatic Data Direction Control) for RS-485**\n\nRS-485 uses differential data transmission over two wires to transmit data from one station to another and allows multiple transmitters and receivers to be used on the same data line. RS-485 uses half-duplex transmission, meaning transmission and reception share the same data channels. Hence, only one transmitter can be active at any given time.\n\nMoxa’s serial boards have a built-in circuitry to switch transmitters on and off automatically. We call this form of switching Automatic Data Direction Control (ADDC®). ADDC® is much easier to implement than the traditional handshaking method that uses the RTS signal.\n\n\n\n**Operating System Support**\n\nThe Mini PCI Express boards are compatible with all major industrial platforms, including Windows and Linux. Moxa device drivers are provided for smoother installation, configuration, and performance.\n\nVisit Moxa’s website at [www.moxa.com](http://www.moxa.com) to download the latest drivers and user’s manuals for all of Moxa’s products.\n\nMoxa Serial Comm Tool\n\nFor application development, Moxa provides an easy-to-use serial communication library called PComm that runs under Windows operation system. Use this library to develop your own applications with Visual Basic, Visual C++, Borland Delphi, to name a few. Utilities such as View Com, Data Scope, Monitor, Terminal Emulator, and Diagnostics are included to make it easier to debug, monitor communication status, provide terminal emulation, and transfer files.\n\nApplications\n\nThe Mini PCI Express boards are suitable for many different applications, including:\n\n- Internet/Intranet Connections\n- Remote Access\n- Multi-user Applications\n- Industrial Automation\n- Office Automation\n- Telecommunications\n- PC-based Vending Machines and Kiosks\n- POS (Point-of-Sale) Systems\n\nFeatures\n\nThe Mini PCI Express boards have the following outstanding features:\n\n- Supports Mini PCI Express interface\n- Small size for compact-sized or Din-rail PCs\n- 128-byte FIFO and on-chip H/W, S/W flow control\n- 50 bps to 921.6 kbps transmission speed\n- Drivers are provided for Windows and Linux\n\nPackage Checklist\n\n- 1 Moxa Mini PCI Express multi serial board (CP-104N-I-T, CP-134N-I-T, CP-114N-T models have the main board and I/O boards)\n- 1 Moxa DB bracket\n- Internal connection cable (25 cm)\n- Documentation\n- Quick installation guide (printed)\n- Warranty card\n\nNOTE\n\nThe cable type and number of DB brackets might differ from different product models. Notify your sales representative if any of the above items are missing or damaged.\n\nThe following flowchart provides a summary of the procedure you should follow to install the Mini PCI Express boards, and it provides references to chapters with more detailed information:\n\n1. Install the boards in PCI Express expansion slots. \n Chapter 2, Hardware Installation\n\n2. Install the drivers and configure the boards and ports. \n Chapter 3, Software Installation\n\n3. Connect the serial devices to the PCI Express board’s serial ports. \n Chapter 6, Pin Assignments\n\n4. Restart the system and check the driver initialization status. \n Chapter 3, Software Installation\n\n5. Develop and run your serial communication applications \n Chapter 5, Serial Programming Tools\n\n2. Hardware Installation\n\nIn this chapter, we show the dimensions diagrams for all the boards in the Mini PCI Express Series and describe the hardware installation procedure. Since the BIOS automatically assigns the PCI Express board’s IRQ number and I/O addresses, you must plug in the board before installing the driver (driver installation is discussed in Chapter 3).\n\nHardware Installation Procedure\n\nThe Mini PCI Express board must be plugged into the PC before installing the driver. The following steps show how to install the Moxa Mini PCI express cards.\n\n1. Find the Mini PCIe slot in your computer.\n2. Insert the Mini PCIe multiport serial board and lock the screws.\n3. Unscrew to remove the blank expansion plate. (We use Moxa V2406C as an example.)\n\nFor the models (CP-102N-T, CP-102N-I-T, CP-132N-T, CP-132N-I-T, CP-104N-T) without I/O boards.\n\n4. Unscrew the hexagonal copper pillars on the cable (DB9 Connector) and use them to connect the provided cables with the bracket.\n\n5. Insert the plate through the blank expansion slot and lock the screws.\n\n6. Connect the Mini PCIe multiport serial board with the cables.\n\nFor the models (CP-104N-I-T, CP-134N-I-T, CP-114N-T) with I/O boards.\n\n4. Unscrew the hexagonal copper pillars on the I/O board and lock the I/O board with the bracket.\n\n5. Insert the I/O board with the bracket through the blank plate hole and lock the screws.\n\n6. Connect the I/O board to the Mini PCIe multiport serial board with the serial cables.\n\nMini PCIE Boards Dimension\n\nMini PCI express serial boards series is included in the following models.\n\n| Model | Ports | Bus | Chip |\n|-------------|-------|------|--------|\n| CP-102N-T | 2 | PCIe | MUE850 |\n| CP-102N-I-T | 2 | PCIe | MUE850 |\n| CP-132N-T | 2 | PCIe | MUE850 |\n| CP-132N-I-T | 2 | PCIe | MUE850 |\n| CP-104N-T | 4 | PCIe | MUE850 |\n| CP-104N-I-T | 4 | PCIe | MUE850 |\n| CP-134N-I-T | 4 | PCIe | MUE850 |\n| CP-114N-T | 4 | PCIe | MUE850 |\n\nThe following content is showing the models’ dimension.\n\n**CP-102N-T Dimensions**\n\nUnit: mm\n\n\n\nCP-102N-I-T Dimensions\n\nUnit: mm\n\nCP-132N-T Dimensions\n\nUnit: mm\n\nCP-132N-I-T Dimensions\n\nUnit: mm\n\nCP-104N-T Dimensions\n\nUnit: mm\n\nCP-104N-I-T Dimensions\n\nMainboard Dimensions (Mini PCIe)\n\nUnit: mm\n\nI/O Board Dimensions\n\nUnit: mm\n\nCP-134N-I-T Dimensions\n\nMainboard Dimensions (Mini PCIe)\n\nUnit: mm\n\nI/O Board Dimensions\n\nUnit: mm\n\nCP-114N-T Dimensions\n\nMainboard Dimensions (Mini PCIe)\n\nUnit: mm\n\nI/O Board Dimensions\n\nUnit: mm\n\nIn this chapter, we give installation, configuration, and update/removal procedures for the driver for Windows and Linux, proceeding with the software installation. Complete the hardware installation discussed in the previous chapter, \"Hardware Installation.\"\n\nRefer to the next chapter, \"Serial Programming Tools,\" for information about developing your own serial programming applications.\n\n**NOTE**\n\nYou can download the drivers from the Moxa website.\n\n### Windows Driver\n\nMoxa provides drivers that allow you to use the Mini PCI Express Series serial boards for various Windows platforms, such as Windows 7/8/8.1/10/11.\n\nThe overall procedure for installing the Windows drivers for the PCI Express boards is summarized in the flowchart on the right.\n\n- **Plug the Mini PCI Express board into an empty PCI Express slot.** See the **Hardware Installation** chapter for details.\n- **Turn on your PC.** Windows will automatically detect the board.\n- **Driver already installed?**\n - **Yes:** The Mini PCI Express board and ports are ready to use.\n - **No:** Install the driver that you can download from the Moxa website. See the **Installing the Driver** subsection in this chapter for detailed instructions.\n - **Configure the board’s ports.** See the **Configuring the Ports** subsection in this chapter for detailed instructions.\n - **Check the status of Moxa’s multiport serial boards.** See the **Checking the Status** subsection in this chapter for detailed instructions.\n - **The Mini PCI Express board and ports are ready to use.**\n\nThis section includes the following topics:\n\n- Installing the Driver\n- Configuring the Ports\n- Checking the Status\n- Removing the Driver\n- Uninstalling the Driver\n\nWe will take Window 10 as an example. Its procedure is similar to the other Windows platforms regarding installing, configuring, checking the port status, removing, or uninstalling the Mini PCI Express cards.\n\n**Installing the Driver**\n\nIn this section, we describe how to install the Mini PCI Express cards for the first time with Windows 10. First, make sure that you have already plugged the board or boards into the system’s Mini PCI Express slot(s).\n\nSecond, you may download the drivers at [www.moxa.com](http://www.moxa.com). Based on the OS type, choose the corresponding driver.\n\nFollow the following procedures to install the driver.\n\n1. Double-click the installation file that you download from the Moxa website.\n2. The Setup Wizard will open. Click **Next** to install the driver.\n\n3. Please read the license agreement. If you agree, please click **Next** to move on.\n\n4. Click **Next** to install the driver in the indicated folder or click the **Browse...** button to locate a different folder.\n\n5. Select the component (tools) you want to install. These tools are useful for configuration, monitoring, and troubleshooting. We would recommend you install it (choose the full installation). However, if you would like to install it later, please uncheck the box in front of the tools. Click **Next** when you are ready to continue.\n\n6. This page shows the tools that will be installed on your computer. Click **Install** and continue the installation process.\n\n7. Please wait until the installation is completed.\n\n8. This page will show all the applications that you have installed. Click **Next** to continue the installation process.\n\n9. On this page, you can check the serial card default port basic configuration here. You can also click the **Scan** button to refresh this page. Click **Next** to continue the install process.\n\n10. This is the final page for the installation process. It shows two ways to do further device configuration. One directs to the multiport serial adapters on the device manager page; the other use the ViewCom tool that you have installed. Click **Finish** to complete the installation process.\n\nConfiguring the Ports\n\nAfter the driver has been installed, use the Device Manager to configure the serial port of your Mini PCI Express cards (the CP-114N-T will be used as an example). In this section, we describe how to access MOXA Smartio/Industio Window Driver and guide through the configuration of serial ports.\n\nAccessing MOXA Smartio/Industio Window Driver\n\nExpand the Multi-port serial adapters tab, right click Moxa CP-114N Series, and then click Properties to open the board’s configuration panel. Please see the following section for more detailed information for the configuration of the Mini PCIe port.\n\nConfiguring Serial Port\n\nYou can set all parameters in the driver properties page’s configuration sheet. Here is an introduction to this page.\n\n1. FAQ:\n\nClick the FAQ button, which will open the FAQ document. If you encounter problems, please check this document before you reached out technical support.\n\n2. Overview:\n\nIn this section, it shows the port parameters such as COM Number, TX and RX FIFO level, and Termination Resistor. The following are the description of this parameters.\n\n- **Port Number and COM No.**\n You will need to set up all the ports of the board with the desired \"COM number\", which should not conflict with other COM numbers in use.\n\n- **RX and TX FIFO**\n - Rx FIFO Level\n - Low - Disables FIFO, resulting in decreased latency, and low throughput.\n - High - Results in high throughput, but with increased latency. *(Default)*\n - Tx FIFO Level\n - Low - Disables FIFO (recommended when the attached serial device has a small buffer, or slow transmission speed).\n - High - Results in high throughput. *(Default)*\n\n- **Interface**\n This column shows the interface of serial ports. You can change the interface by clicking the Port Setting button and making the changes in \"Port Setting\" dialog box. For the RS-232/422/485 serial boards, the interface default setting is RS-232. For the RS-422/485 serial boards, the interface default setting is RS-485 2W.\n\n- **Termination Resistor**\n You may need to enable the termination resistor in the long communication distance.\n - Enable (120 ohm)\n - Disable (Default)\n\n3. Port Setting:\n\nClick this button, which will open the port setting window for you to configure the serial ports.\n\nPort Number/Auto Enumerating COM Number\n\nSelect a COM number for the port from the Port Number drop-down list. You could also type the port number in the text column to quickly get the target port.\n\nSelect the Auto Enumerating COM Number option to map subsequent ports automatically. The port numbers will be assigned in sequence. For example, if COM 1 is assigned to Port 1, then COM 2 (if not already occupied) will be assigned to Port 2, etc.\n\nBasic Settings (Rx, TX FIFO, Interface)\n\nRX and TX FIFO\n\n1. Select an Rx FIFO Trigger from the Rx FIFO Level drop-down list. Rx FIFO trigger levels of High, Middle, and Low are available, with the default set at High (120 bytes).\n - Low - Disables FIFO, resulting in decreased latency and low throughput.\n - High - Results in high throughput but with increased latency. *(Default)*\n\n2. Select a Tx FIFO Level from the Tx FIFO Level drop-down list. Tx FIFO Levels of High, Middle, and Low are available, with the default set at High (128 bytes).\n - Low - Disables FIFO (recommended when the attached serial device has a small buffer, or slow transmission speed).\n - High - Results in high throughput. *(Default)*\n\nTX/RX FIFO Size\n\n| | TX FIFO (Byte) | RX FIFO (Byte) |\n|----------------|---------------|---------------|\n| High (Default) | 128 | 120 |\n| Middle | 64 | 60 |\n| Low | 1 | 1 |\n\nIf you are using CP-132N-T, CP-132N-I-T, CP-134N-I-T, or CP-114N-T, select **Interface** from the dropdown list (RS-232, RS-422, RS-485-2W, or RS-485-4W).\n\nCheck the **Set the change to all ports** option to apply the just defined configuration (Interface and Bias Settings).\n\nClick **Save** to apply the port settings and click **OK** in the Property window to finish the port settings procedure.\n\n4. VM-compatible:\n\nClick this button to get the information summary of this port. Click **OK** to close this window.\n\n5. Port info:\n\nTick this setting to ignore PCI capability if this board has an transmission issue on the virtual machine.\n\n**Bias Resistor Setting**\n\nThe termination resistor (120Ω, Enable, or Disable) and pull high/low resistor will be set by the DIP switch on the main board (CP-132N-T, CP-132-I-T). For the models CP-114N-T and CP-134N-I-T, you can find the DIP switch on the I/O boards. The default setting of the resistors is disable termination resistor and use 150 kohm. If you connect serial cables with a long range, we recommend you enable the 120-ohm termination resistor and set the pull high/low at 1 kohm. Otherwise, please keep it in the default setting so that the serial device continues to work as normal.\n\n| | On | OFF (Default) |\n|---|----------------------------------------------------------------------|----------------------------------------------------|\n| SW1| Enable 120-ohm termination resistor | Disable termination resistor |\n| SW2| 1K-ohm pull-high/low resistors | 150K-ohm Pull-high/low resistors |\n| SW3| Reserved for future feature | |\n| SW4| Reserved for future feature | |\n\nChecking the Status\n\nThe PCComm Diagnostic program is a useful tool for checking the status of Moxa’s multiport serial boards. The program can be used to test internal and external IRQ, TxD/RxD, UART, CTS/RTS, DTR/DSR, etc. Use this program to ensure that your Moxa boards and ports are working properly.\n\nGo to start the program, click **The Windows icon** and find **the PCComm Diagnostic Program**. If you just install it, the program will be shown on the recently added group. The program Default installation location will be C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Moxa. You could also go to the location and launch the program directly.\n\nOr, you can click the search icon and search the **PCComm Diagnostic** program, and then launch this program.\n\nIf the serial board is installed successfully, you will see the installed serial device shown on the Board Status window.\n\n**Removing the Driver**\n\n1. Open the Device Manager and put the cursor over MOXA CP-114N Series (Mini PCI Express Bus) under Multi-port serial adapters. Right-click and select the **Uninstall** option.\n\n2. Select **Delete the driver software for this device** and click **OK** to proceed with uninstalling the board.\n\n---\n\n**Uninstalling the Driver**\n\nThe MSB driver may be removed through Add/Remove Programs in the Windows Control Panel. Open the Control Panel and click **Uninstall a program**.\n\nClick **Uninstall** next to MOXA Smartio/Industio Windows Driver VerX.XX\n\nClick **Uninstall** next to MOXA Smartio/Industio Windows Driver VerX.XX\n\nAre you sure you want to completely remove MOXA Smartio/Industio Windows Driver and all of its components?\n\nWait until the driver has been uninstalled.\n\n**Linux Driver (32-bit/64-bit)**\n\nMoxa provides drivers that allow you to use the following serial boards for Linux.\n\n**Mini PCI Express Boards:** CP-102N-T, CP-102N-I-T, CP-132N-T, CP-132N-I-T, CP-104N-T, CP-104N-I-T, CP-134N-I-T, CP-114N-T\n\n**NOTE**\n\nThe following procedure shows how to install the CP-114N-T driver for Linux.\n\nExecute the following commands from the Linux prompt:\n\n1. `#cd /`\n ```\n #mkdir moxa\n #cd moxa\n #cp /<driver directory>/driv_linux_smart_<version>_build_<build_date>.tgz .\n #tar -zxvf driv_linux_smart_<version>_build_<build_date>.tgz\n ```\n2. `#cd mxser`\n ```\n #make clean; make install\n ```\n3. `#cd /moxa/mxser/driver`\n ```\n #./msmknod\n ```\n4. `#modprobe mxupcie`\n\n5. Use the Moxa Port Configuration Tool to set CP-100N Series Interface for the MUE series.\n\n Usage: `muestty <operation> device`\n\n Device: The MUE series device node\n\n Operation:\n - `-h` Help\n - `-g` Get interface and terminator type\n - `-i intf` Set interface type with options below\n\n | intf | Description |\n |-------|----------------------|\n | RS232 | RS-232 mode |\n | RS422 | RS-422 mode |\n | RS4852W | RS-485 2-wire mode |\n | RS4854W | RS-485 4-wire mode |\n\nFor example\n\nTo set the CP-100N Series interface\n\n# muestty -i RS422 /dev/ttyMUE2\n\n6. Use the Moxa diagnostics utility to verify the driver status:\n\n # cd /moxa/mxser/utility/diag\n # ./msdiag\n\n7. Use the Moxa terminal utility to test the tty ports:\n\n # cd /moxa/mxser/utility/term\n # ./msterm\n\nMoxa provides an easy-to-use yet powerful serial programming library as well as utilities for communication troubleshooting for Windows platforms. The following sections provide details about the installation, the library, and the utilities for various platforms.\n\n**Moxa PComm**\n\nPComm, a professional serial communication tool for PCs, is a software package that runs under Windows NT95/98/2000/XP/2003/Vista/2008/7(x86 and x64)/8/8.1/10/11. PComm provides:\n\n- A powerful serial communication library that simplifies serial programming tasks for most popular programming languages. The serial communication library is useful for developing applications for data communications, remote access, data acquisition, and industrial control for Windows NT95/98/2000/XP/2003/Vista/2008/7(x86 and x64), and is a simpler programming solution compared to the more complex Windows Win32 COMM API.\n- Useful utilities such as diagnostics, monitor, and terminal emulator.\n- Illustrative sample programs.\n- Comprehensive online documentation.\n\n**Installing PComm**\n\nTo install PComm, you could download the installation file on the Moxa website or review Chapter 3, \"Software Installation\", to install it while you are installing the mini PCIe Serial Card driver. Note that the PComm diagnostics and monitor utilities are for Moxa boards only. To use these utilities, you must have a Moxa board and the appropriate Windows (NT/95/98/2000/XP/2003/Vista/2008/7(x86 and x64)/8/8.1/10/11 device driver installed in your system. See Chapter 3, \"Software Installation\", for instructions on how to install the drivers.\n\nAfter installing PComm, click the search icon and search the PComm program and then the **PComm Lite group** to select from the list of utilities and documents.\n\n**PComm Programming Library**\n\nThe serial communication library helps you develop serial communication programs for any COM port that complies with the Microsoft Win32 API. This library facilitates the implementation of multiprocesses, multithread serial communication programs, and greatly reduces the time required to develop applications.\n\nFor a complete description of the library functions and sample programs for Visual C++, Visual Basic, and Delphi, check the help file and the sample programs in the PComm directory.\n\nUtilities\n\nIn this section, we provide brief descriptions of each utility. For more information about these utilities, read the online help from the Documentation.\n\nDiagnostics (for Moxa boards only)\n\nThis convenient diagnostics program, which only works with Moxa boards and ports, provides internal and external testing of IRQ, TxD/RxD, UART, CTS/RTS, DTR/DSR, DTR/DCD, etc. The diagnostics program allows the user to check both the hardware and software functions. To run the diagnostics program, click the search icon and search the **PComm Diagnostic** program and then launch this program.\n\nA typical test report for a Moxa board is as follows:\n\nMonitor\n\nThis useful port status monitoring program allows you to monitor data transmission of selected Moxa COM ports.\n\nTo run the Monitor program, click the search icon and search the **PComm Monitor** program and then launch this program.\n\nThe program monitors data transmission/reception throughput and communication line status, with data updated and displayed on the screen at regular time intervals. Click a specific port to see a graph of the current communication parameters and status of that port.\n\nTerminal Emulator\n\nUse Terminal Emulator to connect to your PC’s serial ports to check if the data is transmitted correctly.\n\nTo run Terminal Emulator, click the search icon and search the **PComm Terminal Emulator** program and then launch this program.\n\nTerminal Emulator features multi-windows and supports VT100 and ANSI terminal types. You can transfer data interactively, send patterns periodically, and transfer files using ASCII, XMODEM, YMODEM, ZMODEM, and KERMIT protocols.\n\nViewCom\n\nViewCom is a useful tool to easily see your Moxa serial board status. ViewCom is also a shortcut to the serial boards parameter configuration page. You don’t need to go to “device manager” and find the serial boards name, which is a complicated process.\n\nViewCom has many useful features.\n\n1. Clicking the ViewCom icon will lead you to the device manager page for monitoring and configuring your devices, including Moxa Serial Boards.\n\n2. Hold your cursor on the ViewCom icon, and it will show the Moxa serial boards you have installed.\n\n3. Right-click on the ViewCom icon.\n\nYou can choose a Moxa multi-port serial board and go to the serial boards parameter configuration page directly.\n\nIf you want to develop your own driver, no matter whether on a Windows or Linux platform, the Moxa Smartio/Industio Programming Guide is a useful instruction. The following topics are covered in this chapter:\n\n**Relative Product List**\n\n- **IRQ * 1**\n- **I/O:**\n - UART register: 64 bytes (8 bytes / port * 8port) for MU860\n 4096 bytes (512 bytes / port * 8port) for MUE250/450/850\n - IRQ Vector register: 16 bytes (only 1 byte used)\n\n**PCI Configuration for Moxa Board**\n\nA. MOXA Vendor ID = 0x1393\n\nB. Device ID = (Please see Moxa Board PCI Device ID List section)\n\nC. Hardware resource on Device Configuration Register of PCI configuration space\n\n| Resource Name | Chip | Address Offset | Size |\n|-------------------------------|--------------------|----------------|--------|\n| IRQ | All | 0x3C | |\n| IRQ Vector Address | MU860 | 0x1C | BAR3 |\n| | | | 16 bytes |\n| UART register (I/O Base Address) | MU860 | 0x18 | BAR2 |\n| | | | 64 bytes |\n| UART register (Memory Base Address) | MUE250, MUE450, MUE850 | 0x14 | BAR1 |\n| | | | 4096 bytes |\n| Vector Base Address | MUE250, MUE450, MUE850 | 0x18 | BAR2 |\n| | | | 16 bytes |\n\n| Byte Offset | 0-7 | 8-15 | 16-23 | 24-31 |\n|-------------|-----|------|-------|-------|\n| 00h | Vender ID | | Device ID |\n| 04h | Command | | Status |\n| 08h | ... | | |\n| 0Ch | ... | | |\n| 10h | BAR0 | | |\n| 14h | BAR1 | | |\n| 18h | BAR2 | | |\n| 1Ch | BAR3 | | |\n| ... | ... | | |\n| 3Ch | Interrupt Line | Interrupt Pin | Reserved |\n\n**NOTE**\n\nMini PCIe multi-ports serial board use MUE850.\n\n**NOTE**\n\nFor MUE250, MUE450, and MUE850 Chips Only: Memory mode is recommended for these chips to access UART. To use memory mode, the driver must access the memory base address, which is located at BAR1.\n\nUART Register Structure for MUE250, MUE450, and MUE850 Chips\n\nThere are 512 bytes for each UART register and 0x200 offset between each port. However, there is one exception: for the models that are 4-port boards, such as CP-104EL-A, CP-114EL, CP-114EL-I, and CP-134EL-A, the offset of the fourth UART register is 0xE00.\n\n**NOTE**\n\nFor a detailed description of the UART register, please see the UART Datasheet section.\n\n**UART register address = I/O base address + (port-1) * 0x200**\n\nFor example, if the base address is 0x200:\n\nThe first port’s UART register’s I/O address is 0x200 + (1-1) * 0x200 = 0x200 \nThe first register’s I/O address is 0x200, \nThe second register’s I/O address is 0x201, ....\n\nThe second port’s UART register’s I/O address is 0x200 + (2-1) * 0x200 = 0x400 \nThe first register’s I/O register is 0x400, \nThe second register’s I/O register is 0x401, ....\n\nControl Serial Interface and Termination Resistor for MUE Chips\n\nFor Moxa boards that use MUE250, MUE450, and MUE850 chips, BAR2, which allocates 16 bytes, is the vector base address that can be used to control serial interfaces and termination resistors, according to the following table.\n\n| Offset | Bit | Port # | Parameters |\n|--------|---------|--------|-------------------------------------------------|\n| 0x4 | [3..0] | 1 | |\n| | [7..4] | 2 | |\n| 0x5 | [3..0] | 3 | 0x0 : RS-232 |\n| | [7..4] | 4 | 0x1 : RS-422 |\n| 0x6 | [3..0] | 5 | 0xF : RS-485 2W |\n| | [7..4] | 6 | 0xB : RS-485 4W |\n| 0x7 | [3..0] | 7 | |\n| | [7..4] | 8 | |\n| 0x8 | [7..0] | [8..1] | GPIO – Input |\n| 0x9 | [7..0] | [8..1] | GPIO direction configuration |\n| | | | 0 : Set GPIO direction to input |\n| | | | 1 : Set GPIO direction to output |\n| 0xA | [7..0] | [8..1] | GPIO – Output (Termination Resistor) |\n| | | | 0 : Low (0 Ohm) |\n| | | | 1 : High (120 Ohm) |\n\nEspecially, the interfaces of 4-port models, such as CP-114EL and CP-114EL-I, use the following offset to set the interface of port 4.\n\n| Offset | Bit | Port # | Parameters |\n|--------|---------|--------|-------------------------------------------------|\n| 0x4 | [3..0] | 1 | |\n| | [7..4] | 2 | |\n| 0x5 | [3..0] | 3 | 0x0 : RS-232 |\n| | [7..4] | – | 0x1 : RS-422 |\n| 0x6 | [3..0] | – | 0xF : RS-485 2W |\n| | [7..4] | – | 0xB : RS-485 4W |\n| 0x7 | [3..0] | 4 | |\n\nFor Baudrate Settings\n\nFor General PC Com Port: \\( \\text{CLK} = 1.8432\\text{MHz} \\)\n\\[ \\text{Div} = \\frac{\\text{CLK}}{(\\text{Baud} \\times 16)} \\]\n\nBut for Moxa Board: \\( \\text{CLK} = 14.7456\\text{MHz} \\)\n\\[ \\text{Div} = \\frac{\\text{CLK}}{(\\text{Baud} \\times 16)} \\]\n\n## Moxa Board PCI Device ID List\n\n| Model | Ports | Bus | Chip | Max Baud | Vendor ID | Device ID |\n|----------------|-------|-------|----------|-----------|-----------|-----------|\n| CP-102N-T | 2 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1027 |\n| CP-102N-I-T | 2 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1027 |\n| CP-132N-T | 2 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1323 |\n| CP-132N-I-T | 2 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1323 |\n| CP-104N-T | 4 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1046 |\n| CP-104N-I-T | 4 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1046 |\n| CP-134N-I-T | 4 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1343 |\n| CP-114N-T | 4 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1145 |\n| CP-102U | 2 | UPCI | MU860 | 921.6k | 0x1393 | 0x1022 |\n| CP-102UL | 2 | UPCI | MU860 | 921.6k | 0x1393 | 0x1021 |\n| CP-132UL | 2 | UPCI | MU860 | 921.6k | 0x1393 | 0x1321 |\n| CP-132UL-I | 2 | UPCI | MU860 | 921.6k | 0x1393 | 0x1321 |\n| CP-102E | 2 | PCIe | MUE250 | 921.6k | 0x1393 | 0x1024 |\n| CP-102EL | 2 | PCIe | MUE250 | 921.6k | 0x1393 | 0x1025 |\n| CP-132EL | 2 | PCIe | MUE250 | 921.6k | 0x1393 | 0x1322 |\n| CP-132EL-I | 2 | PCIe | MUE250 | 921.6k | 0x1393 | 0x1322 |\n| CP-104UL | 4 | UPCI | MU860 | 921.6k | 0x1393 | 0x1041 |\n| CP-104JU | 4 | UPCI | MU860 | 921.6k | 0x1393 | 0x1042 |\n| CP-114UL | 4 | UPCI | MU860 | 921.6k | 0x1393 | 0x1143 |\n| CP-114UL-I | 4 | UPCI | MU860 | 921.6k | 0x1393 | 0x1143 |\n| CP-134U | 4 | UPCI | MU860 | 921.6k | 0x1393 | 0x1340 |\n| CP-134U-I | 4 | UPCI | MU860 | 921.6k | 0x1393 | 0x1340 |\n| CP-104EL-A | 4 | PCIe | MUE450 | 921.6k | 0x1393 | 0x1045 |\n| CP-114EL | 4 | PCIe | MUE450 | 921.6k | 0x1393 | 0x1144 |\n| CP-114EL-I | 4 | PCIe | MUE450 | 921.6k | 0x1393 | 0x1144 |\n| CP-134EL-A | 4 | PCIe | MUE450 | 921.6k | 0x1393 | 0x1342 |\n| CB-114 | 4 | PC/104-Plus | MU860 | 921.6k | 0x1393 | 0x1142 |\n| CB-134I | 4 | PC/104-Plus | MU860 | 921.6k | 0x1393 | 0x1341 |\n| CP-118U | 8 | UPCI | MU860 | 921.6k | 0x1393 | 0x1180 |\n| CP-118U-I | 8 | UPCI | MU860 | 921.6k | 0x1393 | 0x1180 |\n| CP-138U | 8 | UPCI | MU860 | 921.6k | 0x1393 | 0x1380 |\n| CP-138U-I | 8 | UPCI | MU860 | 921.6k | 0x1393 | 0x1380 |\n| CP-168U | 8 | UPCI | MU860 | 921.6k | 0x1393 | 0x1681 |\n| CP-116E-A(A) | 8 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1160 |\n| CP-116E-A(B) | 8 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1161 |\n| CP-118EL-A | 8 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1182 |\n| CP-118F-A-I | 8 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1183 |\n| CP-138E-A-I | 8 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1381 |\n| CP-168EL-A | 8 | PCIe | MUE850 | 921.6k | 0x1393 | 0x1683 |\n| CB-108 | 8 | PC/104-Plus | MU860 | 921.6k | 0x1393 | 0x1080 |\n\n## UART Datasheet\n\nMoxa’s chips are compatible with the following chips. For more details about UART register description, please refer to the links below.\n\n| UART | Port | Datasheet |\n|--------|------|-----------------|\n| MU-860 | 2-8 | TL16C550C |\n| MUE-250| 2 | P17C9X7952 |\n| MUE-450| 4 | P17C9X7954 |\n| MUE-850| 8 | P17C9X7958 |\n\n## 6. Pin Assignments\n\n### Mini PCIe Board Accessories Table\n\n#### Internal Connection Accessories\n\n| Model | Description | Suitable models |\n|------------------------|-----------------------------------------------------------------------------|-----------------|\n| CBL-M9HSF1x10H-15-01 | 10-pin female wafer to 1 DB9 male serial cable, 15 cm | CP-102N-I-T |\n| | | CP-132N-I-T |\n| CBL-M9HSF1x10H-15-02 | 10-pin female wafer to 1 DB9 male serial cable, 15 cm | CP-102N-T |\n| | | CP-132N-T |\n| CBL-M9x2HSF2x10H-15 | 20-pin female wafer to 2 DB9 male serial cables, 15 cm | CP-104N-T |\n| CBL-HSF2x10-15 | 20-pin female wafer to 20-pin female serial cable, 15 cm | CP-104N-I-T |\n| | | CP-134N-I-T |\n| | | CP-114N-T |\n\n### CP-102N-T\n\nThe CP-102N-T 2-port RS-232 Mini PCI Express serial board has two male wafer connectors on the board, with a 10-pin female wafer connector connected to the DB9 male connector via cables.\n\n#### Female Wafer to DB9 Connector Pin Assignments\n\n| Female wafer Pin | DB9 Male Pin | RS-232 |\n|------------------|--------------|--------|\n| 9 | 1 | DCD |\n| 8 | 2 | RxD |\n| 7 | 3 | TxD |\n| 6 | 4 | DTR |\n| 10 | 5 | GND |\n| 3 | 6 | DSR |\n| 2 | 7 | RTS |\n| 1 | 8 | CTS |\n| – | 9 | – |\n\nCP-102N-I-T\n\nThe CP-102N-T 2-port RS-232 Mini PCI Express serial board has two male wafer connectors on the board, with 10-pin female wafer connector connected to the DB9 male connector via cables.\n\nFemale Wafer to DB9 Connector Pin Assignments\n\n| Female wafer Pin | DB9 Male Pin | RS-232 |\n|------------------|--------------|----------|\n| 2 | 1 | DCD |\n| 4 | 2 | RxD |\n| 6 | 3 | TxD |\n| 8 | 4 | DTR |\n| 9 | 5 | GND |\n| 3 | 6 | DSR |\n| 5 | 7 | RTS |\n| 7 | 8 | CTS |\n| – | 9 | – |\n\nCP-132N-T\n\nThe CP-132N-T 2-port RS-422/485 Mini PCI Express serial board supports RS-422, 4-wire RS-485, and 2-wire RS-485. It has two male wafer connectors on the board, with a 10-pin female wafer connector connected to the DB9 male connector via cables.\n\nFemale Wafer to DB9 Connector Pin Assignments\n\n| Female wafer Pin | DB9 Male Pin | RS-422/RS-485-4W | RS-485-2W |\n|------------------|--------------|------------------|-----------|\n| 9 | 1 | TxD-(A) | – |\n| 8 | 2 | TxD+(B) | – |\n| 7 | 3 | RxD+(B) | Data+(B) |\n| 6 | 4 | RxD-(A) | Data-(A) |\n| 10 | 5 | GND | GND |\n| 3 | 6 | – | – |\n| 2 | 7 | – | – |\n| 1 | 8 | – | – |\n| – | 9 | – | – |\n\nThe CP-132N-I-T 2-port RS-422/485 Mini PCI Express serial board supports RS-422, 4-wire RS-485, and 2-wire RS-485. It has two male wafer connectors on the board, with a 10-pin female wafer connector connected to the DB9 male connector via cables.\n\n**Female Wafer to DB9 Connector Pin Assignments**\n\n| Female wafer Pin | DB9 Male Pin | RS-422/RS-485-4W | RS-485-2W |\n|------------------|--------------|------------------|-----------|\n| 2 | 1 | TxD-(A) | - |\n| 4 | 2 | TxD+(B) | - |\n| 6 | 3 | RxD+(B) | Data+(B) |\n| 8 | 4 | RxD-(A) | Data-(A) |\n| 9 | 5 | GND | GND |\n| 3 | 6 | - | - |\n| 5 | 7 | - | - |\n| 7 | 8 | - | - |\n| - | 9 | - | - |\n\nThe CP-104N-T 4-port RS-232 Mini PCI Express serial board supports RS-232 interface. It has two male wafer connectors on the board, with a 20-pin female wafer connector connected to the DB9 male connector via cables.\n\n**Female Wafer to DB9 Connector Pin Assignments**\n\n| Female Wafer Pin | Port 1 DB9 Male Pin | RS-232 | Female Wafer Pin | Port 2 DB9 Male Pin | RS-232 |\n|------------------|---------------------|----------|------------------|---------------------|----------|\n| 17 | 1 | DCD1 | 18 | 1 | DCD2 |\n| 13 | 2 | RxD1 | 14 | 2 | RxD2 |\n| 9 | 3 | TxD1 | 10 | 3 | TxD2 |\n| 5 | 4 | DTR1 | 6 | 4 | DTR2 |\n| 3 | 5 | GND1 | 4 | 5 | GND2 |\n| 16 | 6 | DSR1 | 16 | 6 | DSR2 |\n| 11 | 7 | RTS1 | 12 | 7 | RTS2 |\n| 7 | 8 | CTS1 | 8 | 8 | CTS2 |\n| – | 9 | – | – | 9 | – |\n\nThe CP-104N-I-T 4-port RS-232 Mini PCI Express serial board supports RS-232 interface. It has two male wafer connectors on the board, with a 20-pin female wafer connector connected to the I/O board via cables.\n\n**Board Side Pin Assignment**\n\n| Main Board Side Female Wafer Pin | I/O Board Side Female Wafer Pin | Main Board Side Female Wafer Pin | I/O Board Side Female Wafer Pin |\n|----------------------------------|---------------------------------|----------------------------------|---------------------------------|\n| 1 | 2 | 11 | 12 |\n| 2 | 1 | 12 | 11 |\n| 3 | 4 | 13 | 14 |\n| 4 | 3 | 14 | 13 |\n| 5 | 6 | 15 | 16 |\n| 6 | 5 | 16 | 15 |\n| 7 | 8 | 17 | 18 |\n| 8 | 7 | 18 | 17 |\n| 9 | 10 | 19 | 20 |\n| 10 | 9 | 20 | 10 |\n\n**Device Side Pin Assignment**\n\n| DB9 Male Pin | RS-232 |\n|--------------|--------|\n| 1 | DCD |\n| 2 | RxD |\n| 3 | TxD |\n| 4 | DTR |\n| 5 | GND |\n| 6 | DSR |\n| 7 | RTS |\n| 8 | CTS |\n| 9 | – |\n\nThe CP-134N-I-T 4-port RS-422/485 Mini PCI Express serial board supports RS-422/485 interface. It has two male wafer connectors on the board, with a 20-pin female wafer connector connected to the I/O board via cables.\n\n**Board Side Pin Assignment**\n\n| Main Board Side Female Wafer Pin | I/O Board Side Female Wafer Pin | Main Board Side Female Wafer Pin | I/O Board Side Female Wafer Pin |\n|----------------------------------|---------------------------------|----------------------------------|---------------------------------|\n| 1 | 2 | 11 | 12 |\n| 2 | 1 | 12 | 11 |\n| 3 | 4 | 13 | 14 |\n| 4 | 3 | 14 | 13 |\n| 5 | 6 | 15 | 16 |\n| 6 | 5 | 16 | 15 |\n| 7 | 8 | 17 | 18 |\n| 8 | 7 | 18 | 17 |\n| 9 | 10 | 19 | 20 |\n| 10 | 9 | 20 | 10 |\n\n**Device Side Pin Assignment**\n\n| DB9 Male Pin | RS-422/RS-485-4W | RS-485-2W |\n|--------------|------------------|-----------|\n| 1 | TxD-(A) | – |\n| 2 | TxD+(B) | – |\n| 3 | RxD+(B) | Data+(B) |\n| 4 | RxD-(A) | Data-(A) |\n| 5 | GND | GND |\n| 6 | – | – |\n| 7 | – | – |\n| 8 | – | – |\n| 9 | – | – |\n\n## CP-114N-T\n\n### Board Side Pin Assignment\n\n| Main Board Side Female Wafer Pin | I/O Board Side female Wafer Pin | Main Board Side Female Wafer Pin | I/O Board Side Female Wafer Pin |\n|----------------------------------|---------------------------------|----------------------------------|---------------------------------|\n| 1 | 2 | 11 | 12 |\n| 2 | 1 | 12 | 11 |\n| 3 | 4 | 13 | 14 |\n| 4 | 3 | 14 | 13 |\n| 5 | 6 | 15 | 16 |\n| 6 | 5 | 16 | 15 |\n| 7 | 8 | 17 | 18 |\n| 8 | 7 | 18 | 17 |\n| 9 | 10 | 19 | 20 |\n| 10 | 9 | 20 | 10 |\n\n### Device Side Pin Assignment\n\n| DB9 Male Pin | RS-232 | RS-422/RS-485-4W | RS-485-2W |\n|--------------|--------|-----------------|-----------|\n| 1 | DCD | TxD-(A) | – |\n| 2 | RxD | TxD-(B) | – |\n| 3 | TxD | RxD-(B) | Data+(B) |\n| 4 | DTR | RxD-(A) | Data-(A) |\n| 5 | GND | GND | GND |\n| 6 | DSR | – | – |\n| 7 | RTS | – | – |\n| 8 | CTS | – | – |\n| 9 | – | – | – |\n\nIn this chapter, we discuss the common PCI Express Series problems and possible solutions. If you still have problems after reading this chapter, contact your dealer or Moxa for help, or use the Problem Report Form at the end of this manual to report problems to your dealer.\n\n1. **The Moxa PCI Express board cannot be detected by the Moxa driver while installing the driver.**\n\n **Hardware causes and solutions:**\n \n a. Express slot. It is possible that a slot has malfunctioned. In this case, try other slots until you find one that works.\n \n b. The motherboard does not have an available IRQ for the PCI Express board. In this case, enter the BIOS and make sure there is an available IRQ under PCI/PnP settings.\n\n2. **The Moxa PCI Express board and driver are activated but cannot transfer (transmit/receive) data.**\n\n **Hardware Causes and Solutions:**\n \n a. Make sure the cable wiring is connected correctly. Refer to Chapter 6, “Pin Assignments”, for correct cable connections.\n \n b. The cable or the board could be defective. Try other ports, cables, or boards to verify this, or use the PCComm Diagnostic utility to test the Moxa board and port conditions. If the Diagnostic program reports an error, replace the faulty components.\n\n **Software Causes and Solutions:**\n \n a. PCI Express Series boards will check the line status (CTS) before transmitting data if the RTS/CTS flow control feature is set to Enable in the configuration or application program. Refer to the “Connection Cables and Cable Wiring” chapter for proper wiring diagrams; then, check the line status of the suspected port, using the diagnostics LED indicators on the mini tester.\n \n b. The board control application may not be written correctly according to the corresponding API of the operating system. To check this problem, run another application that you know is correct, or use the utilities provided by Moxa (such as PCComm Terminal emulator that runs under the Windows platform)."},"books_score":{"kind":"number","value":0.7620320320129395,"string":"0.762032"}}},{"rowIdx":8690,"cells":{"content":{"kind":"string","value":"WILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\nPUBLIC HEARINGS AND REGULAR MEETING AGENDA\nSeptember 5, 2019\n\nAugust 28, 2019\n\nBoard of Supervisors\nWildBlue Community Development District\n\nDear Board Members:\n\nThe Board of Supervisors of the WildBlue Community Development District will hold multiple Public Hearings and a Regular Meeting on September 5, 2019 at 11:00 a.m., at Barraco and Associates, 2271 McGregor Boulevard, Suite 100, Fort Myers, Florida 33901. The agenda is as follows:\n\n1. Call to Order/Roll Call\n\n2. Public Comments\n\n3. Public Hearing on the Adoption of the Fiscal Year 2019/2020 Budget\n A. Affidavit/Proof of Publication\n B. Consideration of Resolution 2019-10, Relating to the Annual Appropriations and Adopting the Budgets for the Fiscal Year Beginning October 1, 2019, and Ending September 30, 2020; Authorizing Budget Amendments; and Providing an Effective Date\n\n4. Public Hearing to Hear Comments and Objections on the Imposition of Maintenance and Operation Assessments to Fund the Budget for Fiscal Year 2019/2020, Pursuant to Florida Law\n A. Affidavit of Publication\n B. Mailed Notice(s) to Property Owner(s)\n C. Consideration of Resolution 2019-11, Making a Determination of Benefit and Imposing Special Assessments for Fiscal Year 2019/2020; Providing for the Collection and Enforcement of Special Assessments, Including But Not Limited to Penalties and Interest Thereon; Certifying an Assessment Roll; Providing for Amendments to the Assessment Roll; Providing a Severability Clause; and Providing an Effective Date\n\n5. Presentation of the Audited Annual Financial Report for the Fiscal Year Ended September 30, 2018, Prepared by Berger, Toombs, Elam, Gaines & Frank\n\n6. Consideration of Resolution 2019-12, Accepting the Audited Annual Financial Report for the Fiscal Year Ended September 30, 2018\n\n7. Consideration of Resolution 2019-13, Designating Dates, Times and Locations for Regular Meetings of the Board of Supervisors of the District for Fiscal Year 2019/2020 and Providing for an Effective Date\n\n8. Consideration of Resolution 2019-14, Confirming and Approving the Sale of the Wildblue Community Development District Special Assessment Bonds, Series 2019; Ratifying, Confirming and Approving the Actions of The Chairman, Vice Chairman, Treasurer, Secretary, Assistant Secretaries and all District Staff Regarding the Sale and Closing of the Wildblue Community Development District Special Assessment Bonds, Series 2019; Determining Such Actions as Being in Accordance With the Authorization Granted By the Board; Providing a Severability Clause; and Providing an Effective Date\n\n9. Consideration of Disclosure of Public Financing and Maintenance of Improvements to Real Property\n\n10. Ratification of Solitude Lake Management, LLC, Agreements\n A. Lake Maintenance Agreement\n B. Addendum 1 to Lake Maintenance Agreement\n\n11. Consideration of Second Amendment to Solitude Lake Management, LLC, Lake Maintenance Agreement\n\n12. Approval of Unaudited Financial Statements as of July 31, 2019\n\n13. Consideration of June 6, 2019 Regular Meeting Minutes\n\n14. Staff Reports\n A. District Counsel: Hopping, Green & Sams, P.A.\n B. District Engineer: Barraco and Associates, Inc.\n C. District Manager: Wrathell, Hunt and Associates, LLC\n\n15. Board Members’ Comments/Requests\n\n16. Public Comments\n\n17. Adjournment\n\nI look forward to seeing all of you at the upcoming meeting. In the meantime, if you should have any questions or concerns, please do not hesitate to contact me directly at 561-719-8675.\n\nSincerely,\n\nCraig Wrathell\nDistrict Manager\n\nFOR BOARD MEMBERS AND STAFF TO ATTEND BY TELEPHONE\nCALL-IN NUMBER: 1-888-354-0094\nCONFERENCE ID: 2144145\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n3A\n\nSTATE OF WISCONSIN COUNTY OF BROWN:\nBefore the undersigned authority personally appeared said legal clerk, who on oath says that he or she is a Legal Assistant of the News-Press, a daily newspaper published at Fort Myers in Lee County, Florida; that the attached copy of advertisement, being a Legal Ad in the matter of\n\n0000972845\n\nIn the Twentieth Judicial Circuit Court was published in said newspaper in the issues of:\n\n08/14/19, 08/21/19\n\nAffiant further says that the said News-Press is a paper of general circulation daily in Lee, Charlotte, Collier, Glades and Hendry Counties and published at Fort Myers, in said Lee County, Florida, and that the said newspaper has heretofore been continuously published in said Lee County, Florida each day and has been entered as periodicals matter at the post office in Fort Myers, in said Lee County, Florida, for a period of one year next preceding the first publication of the attached copy of advertisement; and affiant further says that he or she has never paid nor promised any person, firm or corporation any discount, rebate, commission or refund for the purpose of securing this advertisement for publication in the said newspaper.\n\nSworn to and Subscribed before me this 21st of August 2019.\n\nLegal Clerk\n\nNotary Public State of Wisconsin County of Brown\n\nMy commission expires\n\nWILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\nNOTICE OF PUBLIC HEARING TO CONSIDER THE ADOPTION OF THE FISCAL YEAR 2019/2020 BUDGET; NOTICE OF PUBLIC HEARING TO CONSIDER THE ADOPTION OF OPERATIONS AND MAINTENANCE SPECIAL ASSESSMENTS, ADOPTION OF AN ASSESSMENT ROLL, AND THE LEVY, COLLECTION, AND ENFORCEMENT OF THE SAME; AND NOTICE OF REGULAR BOARD OF SUPERVISORS’ MEETING.\n\nUpcoming Public Hearings, and Regular Meeting\n\nThe Board of Supervisors (“Board”) for the Wildblue Community Development District (“District”) will hold the following two public hearings and a regular meeting:\n\nDATE: September 5, 2019\nTIME: 11:00 A.M.\nLOCATION: Hartness & Associates,\n 2271 McGregor Blvd., Suite 100\n Fort Myers, FL 33901\n\nThe first public hearing is being held pursuant to Chapter 197, Florida Statutes, to receive public comment and objections on the District’s proposed budget (“Proposed Budget”) for the fiscal year beginning October 1, 2019 and ending September 30, 2020 (“Fiscal Year 2019/2020”). The second public hearing is being held pursuant to Chapters 196 and 197, Florida Statutes, to consider the imposition of operations and maintenance special assessments (“O&M Assessments”) upon the lands located within the District, to fund the Proposed Budget for Fiscal Year 2019/2020; to consider the adoption of an assessment roll; and, to provide for the levy, collection, and enforcement of assessments at the conclusion of the hearings, the District will adopt, or may adopt, a budget and levy O&M Assessments as finally approved by the Board. A Board meeting of the District will also be held where the Board may consider any other District business.\n\nDescription of Assessments\n\nThe District imposes O&M Assessments on benefited property within the District for the purpose of funding the District’s general administrative, operations, and maintenance budget. A geographic depiction of the property potentially subject to the proposed O&M Assessments is identified in the map attached hereto. The table below shows the schedule of the proposed O&M Assessments, which are subject to change at the hearing:\n\n| Land Use | Total # of Units / Acres | EAU Factor | Proposed Annual O&M Assessment (including collection costs / early payment discounts) |\n|---------------------------|--------------------------|------------|----------------------------------------------------------------------------------|\n| Residential Unit | 374 | 1 | $364.81 |\n| Undeveloped Land - Liened | 68.97 | 1.2904 | $728.84 |\n| Undeveloped Land - Public | 43.36 | 3.5518 | $2,006.07 |\n| Undeveloped Land - SDWID | 26.04 | 2.1593 | $1,214.51 |\n\nThe proposed O&M Assessments as stated include collection costs and/or early payment discounts, which Lee County’s “Collection Policy” states that are to be collected by the County tax collector, with the exception provided in Section 197.36(2)(a), Florida Statutes, the base amount shall serve as the “maximum rate” authorized by law for O&M assessments, such that no assessment hearing shall be held or notice provided in such years unless the assessments are proposed to be increased above the maximum rate. Section 197.36(2)(a), Florida Statutes, is noted. Note that the O&M Assessments do not include any drainage assessments previously levied by the District and due to be collected for Fiscal Year 2019/2020.\n\nFor Fiscal Year 2019/2020, the District intends to have the County tax collector collect the assessments imposed on certain developed property, and will directly collect the assessments imposed on undeveloped property between properties by sending out a bill directly, or direct billing. It is important to point out that missed billings may result in a late fee, or a certificate to be issued against the property which may result in the loss of title, or for direct billed assessments, may result in a foreclosure action, which also may result in a loss of title. The District’s decision to collect assessments on the tax roll or by direct billing does not preclude the District from later electing to collect those or other assessments in a different manner at a future time.\n\nAdditional Provisions\n\nThe public hearings and meeting are open to the public and will be conducted in accordance with the provisions of Florida law. A copy of the Proposed Budget, proposed assessment roll, and the agenda for the public hearing will be available at the office of the District Manager, located at 2300 Glades Road, Suite 410W, Boca Raton, Florida 33431, (877) 276-0889 (“District Manager’s Office”), during normal business hours. The public hearings and meeting may be continued to a date, time, and place to be specified on the record at the hearings or meeting. There may be occasions when staff or board members may participate by speaker telephone.\n\nAny person requiring special accommodations at this meeting because of a disability or physical impairment should contact the District Manager’s Office at least forty-eight (48) hours prior to the date of the public hearing or speech impaired, please contact the Florida Relay Service by dialing 5-1-1 or 1-800-955-8771 (TTY) / 1-800-955-8770 (Voice), for aid in contacting the District Manager’s Office.\n\nPlease note that all affected property owners have the right to appear at the public hearings and meeting, and may also file written objections with the District Manager’s Office within twenty days of publication of this notice. Each person who decides to appeal any decision made by the Board with respect to any matter considered at the public hearings or meeting is advised to personally attend a record of proceedings; and thus accordingly, the person may need to ensure that a verbatim record of the proceedings is made, including the testimony and evidence upon which such appeal is to be based.\n\nDistrict Manager\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n3B\n\nRESOLUTION 2019-10\n\nTHE ANNUAL APPROPRIATION RESOLUTION OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT (“DISTRICT”) RELATING TO THE ANNUAL APPROPRIATIONS AND ADOPTING THE BUDGETS FOR THE FISCAL YEAR BEGINNING OCTOBER 1, 2019, AND ENDING SEPTEMBER 30, 2020; AUTHORIZING BUDGET AMENDMENTS; AND PROVIDING AN EFFECTIVE DATE.\n\nWHEREAS, the District Manager has, prior to the fifteenth (15th) day in June, 2019, submitted to the Board of Supervisors (“Board”) of the WildBlue Community Development District (“District”) proposed budgets (“Proposed Budget”) for the fiscal year beginning October 1, 2019 and ending September 30, 2020 (“Fiscal Year 2019/2020”) along with an explanatory and complete financial plan for each fund of the District, pursuant to the provisions of Section 190.008(2)(a), Florida Statutes; and\n\nWHEREAS, at least sixty (60) days prior to the adoption of the Proposed Budget, the District filed a copy of the Proposed Budget with the local governing authorities having jurisdiction over the area included in the District pursuant to the provisions of Section 190.008(2)(b), Florida Statutes; and\n\nWHEREAS, the Board set a public hearing thereon and caused notice of such public hearing to be given by publication pursuant to Section 190.008(2)(a), Florida Statutes; and\n\nWHEREAS, the District Manager posted the Proposed Budget on the District’s website at least two days before the public hearing; and\n\nWHEREAS, Section 190.008(2)(a), Florida Statutes, requires that, prior to October 1st of each year, the Board, by passage of the Annual Appropriation Resolution, shall adopt a budget for the ensuing fiscal year and appropriate such sums of money as the Board deems necessary to defray all expenditures of the District during the ensuing fiscal year; and\n\nWHEREAS, the District Manager has prepared a Proposed Budget, whereby the budget shall project the cash receipts and disbursements anticipated during a given time period, including reserves for contingencies for emergency or other unanticipated expenditures during the fiscal year.\n\nNOW, THEREFORE, BE IT RESOLVED BY THE BOARD OF SUPERVISORS OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT:\n\nSECTION 1. BUDGET\n\na. The Board has reviewed the Proposed Budget, a copy of which is on file with the office of the District Manager and at the District’s Local Records Office, and hereby approves certain amendments thereto, as shown in Section 2 below.\n\nb. The Proposed Budget, attached hereto as Exhibit “A,” as amended by the Board, is hereby adopted in accordance with the provisions of Section 190.008(2)(a), Florida Statutes (“Adopted Budget”), and incorporated herein by reference; provided, however, that the comparative figures contained in the Adopted Budget may be subsequently revised as deemed necessary by the District Manager to reflect actual revenues and expenditures.\n\nc. The Adopted Budget, as amended, shall be maintained in the office of the District Manager and at the District’s Local Records Office and identified as “The Budget for the WildBlue Community Development District for the Fiscal Year Ending September 30, 2020.”\n\nd. The Adopted Budget shall be posted by the District Manager on the District’s official website within thirty (30) days after adoption and shall remain on the website for at least 2 years.\n\nSECTION 2. APPROPRIATIONS\n\nThere is hereby appropriated out of the revenues of the District, for Fiscal Year 2019/2020, the sum of $1,778,662 to be raised by the levy of assessments and/or otherwise, which sum is deemed by the Board to be necessary to defray all expenditures of the District during said budget year, to be divided and appropriated in the following fashion:\n\n| Fund | Amount |\n|-------------------------------|------------|\n| TOTAL GENERAL FUND | $377,165 |\n| DEBT SERVICE FUND -SERIES 2019| $1,401,497 |\n| TOTAL ALL FUNDS | $1,778,662 |\n\nSECTION 3. BUDGET AMENDMENTS\n\nPursuant to Section 189.016, Florida Statutes, the District at any time within Fiscal Year 2019/2020 or within 60 days following the end of the Fiscal Year 2019/2020 may amend its Adopted Budget for that fiscal year as follows:\n\na. The Board may authorize an increase or decrease in line item appropriations within a fund by motion recorded in the minutes if the total appropriations of the fund do not increase.\n\nb. The District Manager or Treasurer may authorize an increase or decrease in line item appropriations within a fund if the total appropriations of the fund do not increase and if the aggregate change in the original appropriation item does not exceed $10,000 or 10% of the original appropriation.\n\nc. By resolution, the Board may increase any appropriation item and/or fund to reflect receipt of any additional unbudgeted monies and make the corresponding change to appropriations or the unappropriated balance.\n\nd. Any other budget amendments shall be adopted by resolution and consistent with Florida law.\n\nThe District Manager or Treasurer must establish administrative procedures to ensure that any budget amendments are in compliance with this Section 3 and Section 189.016, *Florida Statutes*, among other applicable laws. Among other procedures, the District Manager or Treasurer must ensure that any amendments to budget under subparagraphs c. and d. above are posted on the District’s website within 5 days after adoption and remain on the website for at least 2 years.\n\n**SECTION 4. EFFECTIVE DATE.** This Resolution shall take effect immediately upon adoption.\n\n**PASSED AND ADOPTED THIS 5th DAY OF SEPTEMBER, 2019.**\n\nATTEST: WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n_________________________________________ By: ________________________________\nSecretary/Assistant Secretary Its: ________________________________________\n\nExhibit “A”\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\nPROPOSED BUDGET\nFISCAL YEAR 2020\nUPDATED JUNE 27, 2019\n\n| Description | Page Number(s) |\n|-------------------------------------------------|----------------|\n| General Fund Budget | 1 - 2 |\n| Definitions of General Fund Expenditures | 3 - 4 |\n| Debt Service Fund Budget - Series 2019 | 5 |\n| Amortization Schedule - Series 2019 | 6 - 7 |\n| Assessment Summary | 8 |\n\n## WILDBLUE COMMUNITY DEVELOPMENT DISTRICT GENERAL FUND BUDGET\n\n### REVENUES\n\n| Description | Adopted Budget FY 2019 | Actual through 3/31/2019 | Projected through 9/30/2019 | Total Actual & Projected | Proposed Budget FY 2020 |\n|--------------------------------------------------|------------------------|--------------------------|----------------------------|--------------------------|-------------------------|\n| Assessment levy: on-roll - gross | $ - | $ - | $ - | $ - | $ 211,239 |\n| Allowable discounts (4%) | - | - | - | - | (8,450) |\n| Assessment levy: on-roll - net | - | $ - | $ - | $ - | 202,789 |\n| Assessment levy: off-roll | - | - | - | - | 161,376 |\n| Landowner contribution | 95,275 | 45,779 | 42,948 | 88,727 | - |\n| Interlocal agreement - Vista Blue | - | - | - | - | 13,000 |\n| **Total revenues** | 95,275 | 45,779 | 42,948 | 88,727 | 377,165 |\n\n### EXPENDITURES\n\n#### Professional & administrative\n\n| Description | Adopted Budget FY 2019 | Actual through 3/31/2019 | Projected through 9/30/2019 | Total Actual & Projected | Proposed Budget FY 2020 |\n|--------------------------------------------------|------------------------|--------------------------|----------------------------|--------------------------|-------------------------|\n| Management/accounting/recording | 48,000 | 24,000 | 24,000 | 48,000 | 48,000 |\n| Legal | 20,000 | 4,802 | 15,198 | 20,000 | 20,000 |\n| Boundary amendment | - | 2,842 | 2,200 | 5,042 | - |\n| Boundary amendment petition filling fee | - | 15,000 | - | 15,000 | - |\n| Engineering | 4,000 | 3,266 | 1,500 | 4,766 | 4,000 |\n| Audit** | 5,500 | - | 3,500 | 3,500 | 5,500 |\n| Arbitrage rebate calculation** | 750 | - | - | 750 | - |\n| Dissemination agent* | 1,000 | - | 250 | 250 | 1,000 |\n| Trustee* | 6,500 | - | - | 6,500 | - |\n| Telephone | 200 | 100 | 100 | 200 | 200 |\n| Postage | 500 | 32 | 100 | 132 | 500 |\n| Printing & binding | 500 | 250 | 250 | 500 | 500 |\n| Legal advertising | 1,200 | 4,766 | 500 | 5,266 | 1,200 |\n| Annual special district fee | 175 | 175 | - | 175 | 175 |\n| Insurance | 5,500 | 5,000 | - | 5,000 | 5,500 |\n| Contingencies/bank charges | 500 | 155 | 345 | 500 | 500 |\n| Website | | | | | |\n| Hosting | 650 | 635 | - | 635 | 705 |\n| ADA compliance | 300 | 139 | - | 139 | 200 |\n| **Total professional & administrative** | 95,275 | 61,162 | 47,943 | 109,105 | 95,230 |\n\n#### Field operations\n\n| Description | Adopted Budget FY 2019 | Actual through 3/31/2019 | Projected through 9/30/2019 | Total Actual & Projected | Proposed Budget FY 2020 |\n|--------------------------------------------------|------------------------|--------------------------|----------------------------|--------------------------|-------------------------|\n| Field management | - | - | - | - | 10,000 |\n| Aquatic maintenance | - | - | - | - | 65,000 |\n| Conservation area maintenance | - | - | - | - | 77,000 |\n| Conservation area monitoring & reporting | - | - | - | - | 43,000 |\n| Water level and quality reporting | - | - | - | - | 26,000 |\n| Littoral plant replacements | - | - | - | - | 10,000 |\n| Conservation area fence review/repairs | - | - | - | - | 10,000 |\n| Aeration operating supplies | - | - | - | - | 5,000 |\n| Contingencies | - | - | - | - | 20,000 |\n| Shoreline/seawall repair and replacements | - | - | - | - | 25,000 |\n| **Total field operations** | - | - | - | - | 281,000 |\n\n| | Adopted Budget FY 2019 | Actual through 3/31/2019 | Projected through 9/30/2019 | Total Actual & Projected | Proposed Budget FY 2020 |\n|--------------------------------|------------------------|--------------------------|----------------------------|-------------------------|------------------------|\n| Other fees and charges | | | | | |\n| Property appraiser | - | - | - | - | 374 |\n| Tax collector | - | - | - | - | 561 |\n| Total other fees and charges | - | - | - | - | 935 |\n| Total expenditures | 95,275 | 61,162 | 47,943 | 109,105 | 377,165 |\n| Excess/(deficiency) of revenues over/(under) expenditures | - | (15,383) | (4,995) | (20,378) | - |\n| Fund balance - beginning (unaudited) | - | 20,378 | 4,995 | 20,378 | - |\n| Fund balance - ending (projected) | $ - | $ 4,995 | $ - | $ - | $ - |\n\n* These items will be realized when bonds are issued\n** These items will be realized the year after the issuance of bonds.\n\n## EXPENDITURES\n\n### Professional & administrative\n\n**Management/accounting/recording**\n\n$48,000\n\n*Wrathell, Hunt and Associates, LLC (WHA)*, specializes in managing community development districts by combining the knowledge, skills and experience of a team of professionals to ensure compliance with all of the District's governmental requirements. WHA develops financing programs, administers the issuance of tax exempt bond financings, operates and maintains the assets of the community.\n\n**Legal**\n\n20,000\n\nGeneral counsel and legal representation, which includes issues relating to public finance, public bidding, rulemaking, open meetings, public records, real property dedications, conveyances and contracts.\n\n**Engineering**\n\n4,000\n\nThe District's Engineer will provide construction and consulting services, to assist the District in crafting sustainable solutions to address the long term interests of the community while recognizing the needs of government, the environment and maintenance of the District's facilities.\n\n**Audit**\n\n5,500\n\nStatutorily required for the District to undertake an independent examination of its books, records and accounting procedures.\n\n**Arbitrage rebate calculation**\n\n750\n\nTo ensure the District's compliance with all tax regulations, annual computations are necessary to calculate the arbitrage rebate liability.\n\n**Dissemination agent**\n\n1,000\n\nThe District must annually disseminate financial information in order to comply with the requirements of Rule 15c2-12 under the Securities Exchange Act of 1934. Wrathell, Hunt & Associates serves as dissemination agent.\n\n**Trustee**\n\n6,500\n\nAnnual fee for the service provided by trustee, paying agent and registrar.\n\n**Telephone**\n\n200\n\nTelephone and fax machine.\n\n**Postage**\n\n500\n\nMailing of agenda packages, overnight deliveries, correspondence, etc.\n\n**Printing & binding**\n\n500\n\nLetterhead, envelopes, copies, agenda packages, etc.\n\n**Legal advertising**\n\n1,200\n\nThe District advertises for monthly meetings, special meetings, public hearings, public bids, etc.\n\n### EXPENDITURES (continued)\n\n**Annual special district fee**\n\n175\n\nAnnual fee paid to the Florida Department of Economic Opportunity.\n\n**Insurance**\n\n5,500\n\nThe District will obtain public officials and general liability insurance.\n\n**Contingencies/bank charges**\n\n500\n\nBank charges and other miscellaneous expenses incurred during the year.\n\n**Website**\n\n705\n\n**Hosting**\n\n200\n\n**ADA compliance**\n\nTotal professional and admin\n\n95,230\n\n## Field operations\n\n| Description | Amount |\n|------------------------------------------------------------------------------|---------|\n| Field management | 10,000 |\n| Aquatic maintenance | 65,000 |\n| Conservation area maintenance | 77,000 |\n| Conservation area monitoring and reporting | 43,000 |\n| Water level and quality reporting | 26,000 |\n| Littoral plant replacements | 10,000 |\n| Conservation area fence review/repairs | 10,000 |\n| Aeration operating supplies | 5,000 |\n| Contingencies | 20,000 |\n| Shoreline/seawall repair and replacements | 25,000 |\n\n**Total field operations**: $281,000\n\n## Other fees and charges\n\n| Description | Amount |\n|----------------------|--------|\n| Property appraiser | 374 |\n| Tax collector | 561 |\n\n**Total other fees and charges**: $935\n\n**Total expenditures**: $377,165\n\n## WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n### DEBT SERVICE FUND BUDGET - SERIES 2019\n\n#### FISCAL YEAR 2020\n\n| | Adopted Budget FY 2019 | Actual through 3/31/2019 | Projected through 9/30/2019 | Total Revenue & Expenditures | Proposed Budget FY 2020 |\n|--------------------------|------------------------|--------------------------|-----------------------------|------------------------------|-------------------------|\n| **REVENUES** | | | | | |\n| Special assessment - on-roll | $ - | $ - | $ - | $ 844,344 | (33,774) |\n| Allowable discounts (4%) | | | | | |\n| Assessment levy: net | | $ - | $ - | $ 810,570 | |\n| Special assessment: off-roll | - | - | - | 497,325 | 582,050 |\n| **Total revenues** | | | | 497,325 | 1,392,620 |\n\n| **EXPENDITURES** | | | | | |\n| Debt service | | | | | |\n| Principal | - | - | - | - | 415,000 |\n| Interest | - | - | - | - | 986,497 |\n| **Total debt service** | - | - | - | - | 1,401,497 |\n| Other fees & charges | | | | | |\n| Costs of issuance | - | - | 247,193 | 247,193 | - |\n| Underwriter's discount | - | - | 469,400 | 469,400 | - |\n| **Total other fees & charges** | - | - | 716,593 | 716,593 | - |\n| **Total expenditures** | - | - | 716,593 | 716,593 | 1,401,497 |\n| Excess/(deficiency) of revenues over/(under) expenditures | - | - | (716,593) | (219,268) | (8,877) |\n\n| **OTHER FINANCING SOURCES/(USES)** | | | | | |\n| Bond proceeds | - | - | 1,458,729 | 1,458,729 | - |\n| Original issue discount | - | - | (46,667) | (46,667) | - |\n| **Total other financing sources/(uses)** | - | - | 1,412,062 | 1,412,062 | - |\n\n| Fund balance: | | | | | |\n| Net increase/(decrease) in fund balance | - | - | 695,469 | 1,192,794 | (8,877) |\n| Beginning fund balance (unaudited) | - | - | - | - | 1,192,794 |\n| Ending fund balance (projected) | $ - | $ - | $ 695,469 | $ 1,192,794 | $ 1,183,917 |\n\n| Use of fund balance: | | | | | |\n| Debt service reserve account balance (required) | - | - | (695,469) | (481,909) | |\n| Principal and Interest expense - December 15, 2020 | - | - | - | - | |\n| Projected fund balance surplus/(deficit) as of September 30, 2020 | $ - | $ - | $ 6,539 | $ - | |\n\n| Date | Principal | Coupon Rate | Interest | Debt Service | Bond Balance |\n|------------|------------|-------------|------------|--------------|--------------|\n| 06/12/19 | | | | | 23,470,000.00|\n| 12/15/19 | | | 497,324.74 | 497,324.74 | 23,470,000.00|\n| 06/15/20 | 415,000.00 | 3.500% | 489,171.88 | 904,171.88 | 23,055,000.00|\n| 12/15/20 | | | 481,909.38 | 481,909.38 | 23,055,000.00|\n| 06/15/21 | 430,000.00 | 3.500% | 481,909.38 | 911,909.38 | 22,625,000.00|\n| 12/15/21 | | | 474,384.38 | 474,384.38 | 22,625,000.00|\n| 06/15/22 | 445,000.00 | 3.500% | 474,384.38 | 919,384.38 | 22,180,000.00|\n| 12/15/22 | | | 466,596.88 | 466,596.88 | 22,180,000.00|\n| 06/15/23 | 465,000.00 | 3.500% | 466,596.88 | 931,596.88 | 21,715,000.00|\n| 12/15/23 | | | 458,459.38 | 458,459.38 | 21,715,000.00|\n| 06/15/24 | 480,000.00 | 3.500% | 458,459.38 | 938,459.38 | 21,235,000.00|\n| 12/15/24 | | | 450,059.38 | 450,059.38 | 21,235,000.00|\n| 06/15/25 | 500,000.00 | 3.750% | 450,059.38 | 950,059.38 | 20,735,000.00|\n| 12/15/25 | | | 440,684.38 | 440,684.38 | 20,735,000.00|\n| 06/15/26 | 515,000.00 | 3.750% | 440,684.38 | 955,684.38 | 20,220,000.00|\n| 12/15/26 | | | 431,028.13 | 431,028.13 | 20,220,000.00|\n| 06/15/27 | 535,000.00 | 3.750% | 431,028.13 | 966,028.13 | 19,685,000.00|\n| 12/15/27 | | | 420,996.88 | 420,996.88 | 19,685,000.00|\n| 06/15/28 | 555,000.00 | 3.750% | 420,996.88 | 975,996.88 | 19,130,000.00|\n| 12/15/28 | | | 410,590.63 | 410,590.63 | 19,130,000.00|\n| 06/15/29 | 580,000.00 | 3.750% | 410,590.63 | 990,590.63 | 18,550,000.00|\n| 12/15/29 | | | 399,715.63 | 399,715.63 | 18,550,000.00|\n| 06/15/30 | 600,000.00 | 3.750% | 399,715.63 | 999,715.63 | 17,950,000.00|\n| 12/15/30 | | | 388,465.63 | 388,465.63 | 17,950,000.00|\n| 06/15/31 | 625,000.00 | 4.250% | 388,465.63 | 1,013,465.63 | 17,325,000.00|\n| 12/15/31 | | | 375,184.38 | 375,184.38 | 17,325,000.00|\n| 06/15/32 | 650,000.00 | 4.250% | 375,184.38 | 1,025,184.38 | 16,675,000.00|\n| 12/15/32 | | | 361,371.88 | 361,371.88 | 16,675,000.00|\n| 06/15/33 | 680,000.00 | 4.250% | 361,371.88 | 1,041,371.88 | 15,995,000.00|\n| 12/15/33 | | | 346,921.88 | 346,921.88 | 15,995,000.00|\n| 06/15/34 | 710,000.00 | 4.250% | 346,921.88 | 1,056,921.88 | 15,285,000.00|\n| 12/15/34 | | | 331,834.38 | 331,834.38 | 15,285,000.00|\n| 06/15/35 | 740,000.00 | 4.250% | 331,834.38 | 1,071,834.38 | 14,545,000.00|\n| 12/15/35 | | | 316,109.38 | 316,109.38 | 14,545,000.00|\n| 06/15/36 | 775,000.00 | 4.250% | 316,109.38 | 1,091,109.38 | 13,770,000.00|\n| 12/15/36 | | | 299,640.63 | 299,640.63 | 13,770,000.00|\n| 06/15/37 | 805,000.00 | 4.250% | 299,640.63 | 1,104,640.63 | 12,965,000.00|\n| 12/15/37 | | | 282,534.38 | 282,534.38 | 12,965,000.00|\n| 06/15/38 | 840,000.00 | 4.250% | 282,534.38 | 1,122,534.38 | 12,125,000.00|\n| 12/15/38 | | | 264,684.38 | 264,684.38 | 12,125,000.00|\n| 06/15/39 | 880,000.00 | 4.250% | 264,684.38 | 1,144,684.38 | 11,245,000.00|\n| 12/15/39 | | | 245,984.38 | 245,984.38 | 11,245,000.00|\n| 06/15/40 | 915,000.00 | 4.375% | 245,984.38 | 1,160,984.38 | 10,330,000.00|\n| 12/15/40 | | | 225,968.75 | 225,968.75 | 10,330,000.00|\n| 06/15/41 | 960,000.00 | 4.375% | 225,968.75 | 1,185,968.75 | 9,370,000.00|\n| 12/15/41 | | | 204,968.75 | 204,968.75 | 9,370,000.00|\n| 06/15/42 | 1,000,000.00 | 4.375% | 204,968.75 | 1,204,968.75 | 8,370,000.00|\n| 12/15/42 | | | 183,093.75 | 183,093.75 | 8,370,000.00|\n| 06/15/43 | 1,045,000.00 | 4.375% | 183,093.75 | 1,228,093.75 | 7,325,000.00|\n\n| Date | Principal | Coupon Rate | Interest | Debt Service | Bond Balance |\n|------------|-------------|-------------|-----------|--------------|--------------|\n| 12/15/43 | | | | | 7,325,000.00 |\n| 06/15/44 | 1,090,000.00 | 4.375% | 160,234.38 | 1,250,234.38 | 6,235,000.00 |\n| 12/15/44 | | | 136,390.63 | 136,390.63 | 6,235,000.00 |\n| 06/15/45 | 1,140,000.00 | 4.375% | 136,390.63 | 1,276,390.63 | 5,095,000.00 |\n| 12/15/45 | | | 111,453.13 | 111,453.13 | 5,095,000.00 |\n| 06/15/46 | 1,190,000.00 | 4.375% | 111,453.13 | 1,301,453.13 | 3,905,000.00 |\n| 12/15/46 | | | 85,421.88 | 85,421.88 | 3,905,000.00 |\n| 06/15/47 | 1,245,000.00 | 4.375% | 85,421.88 | 1,330,421.88 | 2,660,000.00 |\n| 12/15/47 | | | 58,187.50 | 58,187.50 | 2,660,000.00 |\n| 06/15/48 | 1,300,000.00 | 4.375% | 58,187.50 | 1,358,187.50 | 1,360,000.00 |\n| 12/15/48 | | | 29,750.00 | 29,750.00 | 1,360,000.00 |\n| 06/15/49 | 1,360,000.00 | 4.375% | 29,750.00 | 1,389,750.00 | - |\n\nTotal: 23,470,000.00 18,671,746.86 42,141,746.86\n\n## On-Roll Assessments\n\n| Product | Units | FY 2020 O&M Assessment per Unit | FY 2020 DS Assessment per Unit | FY 2020 Total Assessment per Unit | FY 2019 Total Assessment per Unit |\n|---------|-------|---------------------------------|-------------------------------|----------------------------------|----------------------------------|\n| SF 52' | 31 | $564.81 | $1,513.08 | $2,077.89 | n/a |\n| SF 66' | 44 | $564.81 | $1,920.43 | $2,485.24 | n/a |\n| SF 72' | 27 | $564.81 | $2,095.01 | $2,659.82 | n/a |\n| SF 75' | 180 | $564.81 | $2,182.30 | $2,747.11 | n/a |\n| SF 85' | 46 | $564.81 | $2,473.26 | $3,038.07 | n/a |\n| SF 102' | 34 | $564.81 | $2,967.89 | $3,532.70 | n/a |\n| SF 140' | 12 | $564.81 | $4,073.55 | $4,638.36 | n/a |\n| **Total** | **374** | | | | |\n\n## Off-Roll Assessments\n\n| Product | Units | FY 2020 O&M Assessment per Unit | FY 2020 DS Assessment per Unit | FY 2020 Total Assessment per Unit | FY 2019 Total Assessment per Unit |\n|---------|-------|---------------------------------|-------------------------------|----------------------------------|----------------------------------|\n| SF 52' | 69 | $539.72 | $1,452.56 | $1,992.28 | n/a |\n| SF 66' | 51 | $539.72 | $1,843.61 | $2,383.33 | n/a |\n| SF 72' | 34 | $539.72 | $2,011.21 | $2,550.93 | n/a |\n| SF 75' | 89 | $539.72 | $2,095.01 | $2,634.73 | n/a |\n| SF 85' | 56 | $539.72 | $2,374.33 | $2,914.05 | n/a |\n| SF 102' | - | $539.72 | $2,849.17 | $3,388.89 | n/a |\n| SF 140' | - | $539.72 | $3,910.61 | $4,450.33 | n/a |\n| **Total** | **299** | | | | |\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n4A\n\nSTATE OF WISCONSIN COUNTY OF BROWN:\nBefore the undersigned authority personally appeared said legal clerk, who on oath says that he or she is a Legal Assistant of the News-Press, a daily newspaper published at Fort Myers in Lee County, Florida; that the attached copy of advertisement, being a Legal Ad in the matter of\n\n0000972845\n\nIn the Twentieth Judicial Circuit Court was published in said newspaper in the issues of:\n\n08/14/19, 08/21/19\n\nAffiant further says that the said News-Press is a paper of general circulation daily in Lee, Charlotte, Collier, Glades and Hendry Counties and published at Fort Myers, in said Lee County, Florida, and that the said newspaper has heretofore been continuously published in said Lee County, Florida each day and has been entered as periodicals matter at the post office in Fort Myers, in said Lee County, Florida, for a period of one year next preceding the first publication of the attached copy of advertisement; and affiant further says that he or she has never paid nor promised any person, firm or corporation any discount, rebate, commission or refund for the purpose of securing this advertisement for publication in the said newspaper.\n\nSworn to and Subscribed before me this 21st of August 2019.\n\nLegal Clerk\n\nNotary Public State of Wisconsin County of Brown\n\nMy commission expires\n\nWILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\nNOTICE OF PUBLIC HEARING TO CONSIDER THE ADOPTION OF THE FISCAL YEAR 2019/2020 BUDGET; NOTICE OF PUBLIC HEARING TO CONSIDER THE ADOPTION OF OPERATIONS AND MAINTENANCE SPECIAL ASSESSMENTS, ADOPTION OF AN ASSESSMENT ROLL, AND THE LEVY, COLLECTION, AND ENFORCEMENT OF THE SAME; AND NOTICE OF REGULAR BOARD OF SUPERVISORS’ MEETING.\n\nUpcoming Public Hearings, and Regular Meeting\n\nThe Board of Supervisors (“Board”) for the Wildblue Community Development District (“District”) will hold the following two public hearings and a regular meeting:\n\nDATE: September 5, 2019\nTIME: 11:00 A.M.\nLOCATION: Hartness & Associates,\n 2271 McGregor Blvd., Suite 100\n Fort Myers, FL 33901\n\nThe first public hearing is being held pursuant to Chapter 197, Florida Statutes, to receive public comment and objections on the District’s proposed budget (“Proposed Budget”) for the fiscal year beginning October 1, 2019 and ending September 30, 2020 (“Fiscal Year 2019/2020”). The second public hearing is being held pursuant to Chapters 196 and 197, Florida Statutes, to consider the imposition of operations and maintenance special assessments (“O&M Assessments”) upon the lands located within the District, to fund the Proposed Budget for Fiscal Year 2019/2020; to consider the adoption of an assessment roll; and, to provide for the levy, collection, and enforcement of assessments at the conclusion of the hearings, the District will adopt, or may adopt, a budget and levy O&M Assessments as finally approved by the Board. A Board meeting of the District will also be held where the Board may consider any other District business.\n\nDescription of Assessments\n\nThe District imposes O&M Assessments on benefited property within the District for the purpose of funding the District’s general administrative, operations, and maintenance budget. A geographic depiction of the property potentially subject to the proposed O&M Assessments is identified in the map attached hereto. The table below shows the schedule of the proposed O&M Assessments, which are subject to change at the hearing:\n\n| Land Use | Total # of Units / Acres | EAU Factor | Proposed Annual O&M Assessment (including collection costs / early payment discounts) |\n|---------------------------|--------------------------|------------|----------------------------------------------------------------------------------|\n| Residential Unit | 374 | 1 | $364.81 |\n| Undeveloped Land - Liened | 68.97 | 1.2904 | $728.84 |\n| Undeveloped Land - Public | 43.36 | 3.5518 | $2,006.07 |\n| Undeveloped Land - SDWID | 26.04 | 2.1593 | $1,214.51 |\n\nThe proposed O&M Assessments as stated include collection costs and/or early payment discounts, which Lee County’s “Collection Policy” states that are to be collected by the County tax collector, with the exception provided in Section 197.36(2)(a), Florida Statutes, the base amount shall serve as the “maximum rate” authorized by law for O&M assessments, such that no assessment hearing shall be held or notice provided in such years unless the assessments are proposed to be increased above the maximum rate. Section 197.36(2)(a), Florida Statutes, is noted. Note that the O&M Assessments do not include any drainage assessments previously levied by the District and due to be collected for Fiscal Year 2019/2020.\n\nFor Fiscal Year 2019/2020, the District intends to have the County tax collector collect the assessments imposed on certain developed property, and will directly collect the assessments imposed on undeveloped property between properties by sending out a bill directly, or direct billing. It is important to point out that missed billings may result in a late fee, or a certificate to be issued against the property which may result in the loss of title, or for direct billed assessments, may result in a foreclosure action, which also may result in a loss of title. The District’s decision to collect assessments on the tax roll or by direct billing does not preclude the District from later electing to collect those or other assessments in a different manner at a future time.\n\nAdditional Provisions\n\nThe public hearings and meeting are open to the public and will be conducted in accordance with the provisions of Florida law. A copy of the Proposed Budget, proposed assessment roll, and the agenda for the public hearing will be available at the office of the District Manager, located at 2300 Glades Road, Suite 410W, Boca Raton, Florida 33431, (877) 276-0889 (“District Manager’s Office”), during normal business hours. The public hearings and meeting may be continued to a date, time, and place to be specified on the record at the hearings or meeting. There may be occasions when staff or board members may participate by speaker telephone.\n\nAny person requiring special accommodations at this meeting because of a disability or physical impairment should contact the District Manager’s Office at least forty-eight (48) hours prior to the date of the public hearing or speech impaired, please contact the Florida Relay Service by dialing 5-1-1 or 1-800-955-8771 (TTY) / 1-800-955-8770 (Voice), for aid in contacting the District Manager’s Office.\n\nPlease note that all affected property owners have the right to appear at the public hearings and meeting, and may also file written objections with the District Manager’s Office within twenty days of publication of this notice. Each person who decides to appeal any decision made by the Board with respect to any matter considered at the public hearings or meeting is advised to personally attend a record of proceedings; and thus accordingly, the person may need to ensure that a verbatim record of the proceedings is made, including the testimony and evidence upon which such appeal is to be based.\n\nDistrict Manager\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n4B\n\nSTATE OF FLORIDA\n\nCOUNTY OF PALM BEACH\n\nAFFIDAVIT OF MAILING\n\nBEFORE ME, the undersigned authority, this day personally appeared Michal Szymonowicz, who by me first being duly sworn and deposed says:\n\n1. I am over eighteen (18) years of age and am competent to testify as to the matters contained herein. I have personal knowledge of the matters stated herein.\n\n2. I, Michal Szymonowicz, am employed by Wrathell, Hunt and Associates, LLC, and, in the course of that employment, serve as Assessment Consultant for the WildBlue Community Development District.\n\n3. Among other things, my duties include preparing and transmitting correspondence relating to the WildBlue Community Development District.\n\n4. I do hereby certify that on August 6, 2019, and in the regular course of business, I caused letters, in the forms attached hereto as Exhibit A, to be sent notifying affected landowner(s) in the WildBlue Community Development District of their rights under Chapters 170, 190, and 197, Florida Statutes, with respect to the District’s anticipated imposition of operations and maintenance assessments. I further certify that the letters were sent to the addressees identified in Exhibit B and in the manner identified in Exhibit A.\n\n5. I have personal knowledge of having sent the letters to the addressees, and those records are kept in the course of the regular business activity for my office.\n\nFURTHER AFFIANT SAYETH NOT.\n\nBy: Michal Szymonowicz\n\nSWORN AND SUBSCRIBED before me this 6th day of August 2019, by Michal Szymonowicz, for Wrathell, Hunt and Associates, LLC, who is [ ] personally known to me or [ ] has provided ________________ as identification, and who did __ / did not √ take an oath.\n\nDaphne Gilleyard\nNOTARY PUBLIC\nSTATE OF FLORIDA\nComm# FF899542\nExpires 8/20/2019\n\nPrint Name: Daphne Gilleyard\nNotary Public, State of Florida\nCommission No.: FF899542\nMy Commission Expires: 8/20/2019\n\nEXHIBIT A: Mailed Notice\nEXHIBIT B: List of Addressees\n\nExhibit A\n\nAugust 6, 2019\n\nXXX\nXXX\nXXX\nPARCEL ID:\n\nRE: WildBlue Community Development District\nFiscal Year 2019/2020 Budget and O&M Assessments\n\nDear Property Owner:\n\nPursuant to Chapters 190 and 197, Florida Statutes, the WildBlue Community Development District (“District”) will be holding two public hearings and a Board of Supervisors’ (“Board”) meeting for the purpose of adopting the District’s proposed budget (“Proposed Budget”) for the fiscal year beginning October 1, 2019 and ending September 30, 2020 (“Fiscal Year 2019/2020”) and levying operations and maintenance assessments (“O&M Assessments”) to fund the Proposed Budget for Fiscal Year 2019/2020, on September 5, 2019, at 10:00 a.m., at the offices of Barraco and Associates, 2271 McGregor Boulevard, Suite 100, Fort Myers, Florida 33901. The District is a special purpose unit of local government established under Chapter 190, Florida Statutes, for the purposes of providing infrastructure and services to your community. The proposed O&M Assessments information for your property is set forth in Exhibit A.\n\nThe public hearings and meeting are open to the public and will be conducted in accordance with Florida law. A copy of the Proposed Budget, assessment roll and the agenda for the hearings and meeting may be obtained by contacting Wrathell, Hunt and Associates, LLC, 2300 Glades Road, Suite 410W, Boca Raton, Florida 33431, Ph: (561) 571-0010 (“District Manager’s Office”). The public hearings and meeting may be continued to a date, time, and place to be specified on the record. There may be occasions when staff or board members may participate by speaker telephone. Any person requiring special accommodations because of a disability or physical impairment should contact the District Manager’s Office at least forty-eight (48) hours prior to the meeting. If you are hearing or speech impaired, please contact the Florida Relay Service by dialing 7-1-1, or 1-800-955-8771 (TTY) / 1-800-955-8770 (Voice), for aid in contacting the District Manager’s Office.\n\nPlease note that all affected property owners have the right to appear and comment at the public hearings and meeting, and may also file written objections with the District Manager’s Office within twenty (20) days of issuance of this notice. Each person who decides to appeal any decision made by the Board with respect to any matter considered at the public hearings or meeting is advised that person will need a record of proceedings and that accordingly, the person may need to ensure that a verbatim record of the proceedings is made, including the testimony and evidence upon which such appeal is to be based.\n\nIf you have any questions, please do not hesitate to contact the District Manager’s Office.\n\nSincerely,\n\nCraig Wrathell\nDistrict Manager\n\nEXHIBIT A\n\nSummary of O&M Assessments\n\n1. **Proposed Budget / Total Revenue.** For all O&M Assessments levied to fund the Proposed Budget for Fiscal Year 2019/2020, the District expects to collect no more than $131,013 in gross revenue.\n\n2. **Unit of Measurement.** The O&M Assessments are allocated on a per acre basis for undeveloped property and on an Equivalent Assessment Unit (“EAU”) basis for platted lots. Your property is classified as one (1) Residential Lot.\n\n3. **Schedule of O&M Assessments:**\n\n| Land Use | Total # of Units / Acres | EAU Factor | Proposed Annual O&M Assessment (including collection costs / early payment discounts) |\n|---------------------------|--------------------------|------------|----------------------------------------------------------------------------------------|\n| Residential Unit | 374 | 1 | $564.81 |\n| Undeveloped Land - Lennar | 68.97 | 1.2904 | $728.84 |\n| Undeveloped Land - Pulte | 43.36 | 3.5518 | $2,006.07 |\n| Undeveloped Land - SDWD | 26.04 | 2.1503 | $1,214.51 |\n\n4. **Proposed O&M Assessments for Your Property.**\n\n| Current Annual O&M Assessment (October 1, 2018 – September 30, 2019) | Proposed Annual O&M Assessment (October 1, 2019 – September 30, 2020) | Change in Annual Dollar Amount |\n|-----------------------------------------------------------------------|------------------------------------------------------------------------|-------------------------------|\n| $0.00 (District operations were funded via Developer contribution) | $564.81 | $564.81 |\n\nNote that the O&M Assessments do not include any debt service assessments previously levied by the District and due to be collected for Fiscal Year 2019/2020. Moreover, pursuant to Section 197.3632(4), *Florida Statutes*, the lien amount shall serve as the “maximum rate” authorized by law for operation and maintenance assessments, such that no assessment hearing shall be held or notice provided in future years unless the assessments are proposed to be increased or another criterion within Section 197.3632(4) is met.\n\n5. **Collection.** By operation of law, the District’s assessments each year constitute a lien against benefitted property located within the District just as do each year’s property taxes. For Fiscal Year 2019-2020, the District intends to have the County Tax Collector collect the assessments imposed on certain developed property and will directly collect the assessments imposed on the remaining benefitted property by sending out a bill prior to, or during, November 2019. For delinquent assessments that were initially directly billed by the District, the District may initiate a foreclosure action or may place the delinquent assessments on the next year’s county tax bill.\n\nIT IS IMPORTANT TO PAY YOUR ASSESSMENT BECAUSE FAILURE TO PAY WILL CAUSE A TAX CERTIFICATE TO BE ISSUED AGAINST THE PROPERTY WHICH MAY RESULT IN LOSS OF TITLE, OR FOR DIRECT BILLED ASSESSMENTS, MAY RESULT IN A FORECLOSURE ACTION, WHICH ALSO MAY RESULT IN A LOSS OF TITLE. The District’s decision to collect assessments on the tax roll or by direct billing does not preclude the District from later electing to collect those or other assessments in a different manner at a future time.\n\n6. **Hearing Information.** The public hearings and meeting are open to the public and will be conducted in accordance with Florida law. A copy of the proposed agenda and other documents for the hearings and meeting may be obtained by contacting the District Manager at c/o Wrathell, Hunt and Associates, LLC, 2300 Glades Road, Suite 410W, Boca Raton, Florida 33431, (561) 571-0010, or visiting [http://www.eastbonitabeachroadcdd.net](http://www.eastbonitabeachroadcdd.net). The public hearings and meeting may be continued to a date, time, and place to be specified on the record. There may be occasions when staff or board members may participate by speaker telephone. Any person requiring special accommodations because of a disability or physical impairment should contact the District Manager at least forty-eight (48) hours prior to the meeting. If you are hearing or speech impaired, please contact the Florida Relay Service by dialing 7-1-1, or 1-800-955-8771 (TTY) / 1-800-955-8770 (Voice), for aid in contacting the District Manager. Please note that all affected property owners have the right to appear and comment at the public hearings and meeting and may also file written objections with the District Manager within twenty (20) days of issuance of this notice. Each person who decides to appeal any decision made by the Board with respect to any matter considered at the public hearings or meeting is advised that person will need a record of proceedings and that accordingly, the person may need to ensure that a verbatim record of the proceedings is made, including the testimony and evidence upon which such appeal is to be based.\n\nExhibit B\n\n| Company Name | Address |\n|----------------------|----------------------------------------------|\n| LENNAR HOMES, LLC | 10481 SIX MILE CYPRESS PKWY, FORT MYERS FL, 33966 |\n| PULTE HOME COMPANY LLC | 24311 WALDEN CENTER DR STE 300, BONITA SPRINGS FL, 34134 |\n| SDWB, LLC | 2639 PROFESSIONAL CIRCLE STE 101, NAPLES FL, 34119 |\n| SDWB LLC | 12800 UNIVERSITY DR, SUITE 275, FORT MYERS FL, 33907 |\n| SD WILDBLUE, LLC | 2639 PROFESSIONAL CIRCLE, SUITE 10, NAPLES FL, 34119 |\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n4C\n\nA RESOLUTION OF THE BOARD OF SUPERVISORS OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT MAKING A DETERMINATION OF BENEFIT AND IMPOSING SPECIAL ASSESSMENTS FOR FISCAL YEAR 2019/2020; PROVIDING FOR THE COLLECTION AND ENFORCEMENT OF SPECIAL ASSESSMENTS, INCLUDING BUT NOT LIMITED TO PENALTIES AND INTEREST THEREON; CERTIFYING AN ASSESSMENT ROLL; PROVIDING FOR AMENDMENTS TO THE ASSESSMENT ROLL; PROVIDING A SEVERABILITY CLAUSE; AND PROVIDING AN EFFECTIVE DATE.\n\nWHEREAS, the WildBlue Community Development District (“District”) is a local unit of special-purpose government established pursuant to Chapter 190, Florida Statutes, for the purpose of providing, operating and maintaining infrastructure improvements, facilities and services to the lands within the District; and\n\nWHEREAS, the District is located in Lee County, Florida (“County”); and\n\nWHEREAS, the District has constructed or acquired various infrastructure improvements and provides certain services in accordance with the District’s adopted capital improvement plan and Chapter 190, Florida Statutes; and\n\nWHEREAS, the Board of Supervisors (“Board”) of the District hereby determines to undertake various operations and maintenance and other activities described in the District’s budget (“Adopted Budget”) for the fiscal year beginning October 1, 2019 and ending September 30, 2020 (“Fiscal Year 2019/2020”), attached hereto as Exhibit “A;” and\n\nWHEREAS, the District must obtain sufficient funds to provide for the operation and maintenance of the services and facilities provided by the District as described in the Adopted Budget; and\n\nWHEREAS, the provision of such services, facilities, and operations is a benefit to lands within the District; and\n\nWHEREAS, Chapter 190, Florida Statutes, provides that the District may impose special assessments on benefitted lands within the District; and\n\nWHEREAS, it is in the best interests of the District to proceed with the imposition of the special assessments for operations and maintenance in the amount set forth in the Adopted Budget; and\n\nWHEREAS, the District has previously levied an assessment for debt service, which the District desires to collect for Fiscal Year 2019/2020; and\n\nWHEREAS, Chapter 197, Florida Statutes, provides a mechanism pursuant to which such special assessments may be placed on the tax roll and collected by the local tax collector (“Uniform Method”), and the District has previously authorized the use of the Uniform Method\n\nby, among other things, entering into agreements with the Property Appraiser and Tax Collector of the County for that purpose; and\n\nWHEREAS, it is in the best interests of the District to adopt the assessment roll (\"Assessment Roll\") attached to this Resolution as Exhibit \"B,\" and to certify the portion of the Assessment Roll related to certain developed property (\"Tax Roll Property\") to the County Tax Collector pursuant to the Uniform Method and to directly collect the portion of the Assessment Roll relating to the remaining property (\"Direct Collect Property\"), all as set forth in Exhibit \"B;\" and\n\nWHEREAS, it is in the best interests of the District to permit the District Manager to amend the Assessment Roll adopted herein, including that portion certified to the County Tax Collector by this Resolution, as the Property Appraiser updates the property roll for the County, for such time as authorized by Florida law.\n\nNOW, THEREFORE, BE IT RESOLVED BY THE BOARD OF SUPERVISORS OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT:\n\nSECTION 1. BENEFIT & ALLOCATION FINDINGS. The provision of the services, facilities, and operations as described in Exhibit \"A\" confers a special and peculiar benefit to the lands within the District, which benefit exceeds or equals the cost of the assessments. The allocation of the assessments to the specially benefitted lands is shown in Exhibits \"A\" and \"B,\" and is hereby found to be fair and reasonable.\n\nSECTION 2. ASSESSMENT IMPOSITION. Pursuant to Chapters 190 and 197, Florida Statutes, and using the procedures authorized by Florida law for the levy and collection of special assessments, a special assessment for operation and maintenance is hereby imposed and levied on benefitted lands within the District and in accordance with Exhibits \"A\" and \"B.\" The lien of the special assessments for operations and maintenance imposed and levied by this Resolution shall be effective upon passage of this Resolution. Moreover, pursuant to Section 197.3632(4), Florida Statutes, the lien amount shall serve as the “maximum rate” authorized by law for operation and maintenance assessments.\n\nSECTION 3. COLLECTION AND ENFORCEMENT; PENALTIES; INTEREST.\n\nA. Tax Roll Assessments. The operations and maintenance special assessments and previously levied debt service special assessments imposed on the Tax Roll Property shall be collected at the same time and in the same manner as County taxes in accordance with the Uniform Method, as set forth in Exhibits \"A\" and \"B.\"\n\nB. Direct Bill Assessments. The operations and maintenance special assessments and previously levied debt service special assessments imposed on the Direct Collect Property shall be collected directly by the District in accordance with Florida law, as set forth in Exhibits \"A\" and \"B.\" Assessments directly collected by the District are due in full on December 1, 2019; provided, however, that, to the\n\nextent permitted by law, the assessments due may be paid in several partial, deferred payments and according to the following schedule: 50% due no later than December 1, 2019, 25% due no later than February 1, 2020 and 25% due no later than May 1, 2020. In the event that an assessment payment is not made in accordance with the schedule stated above, the whole assessment – including any remaining partial, deferred payments for Fiscal Year 2019/2020, shall immediately become due and payable; shall accrue interest, penalties in the amount of one percent (1%) per month, and all costs of collection and enforcement; and shall either be enforced pursuant to a foreclosure action, or, at the District’s sole discretion, collected pursuant to the Uniform Method on a future tax bill, which amount may include penalties, interest, and costs of collection and enforcement. Any prejudgment interest on delinquent assessments shall accrue at the rate of any bonds secured by the assessments, or at the statutory prejudgment interest rate, as applicable. In the event an assessment subject to direct collection by the District shall be delinquent, the District Manager and District Counsel, without further authorization by the Board, may initiate foreclosure proceedings pursuant to Chapter 170, Florida Statutes, or other applicable law to collect and enforce the whole assessment, as set forth herein.\n\nC. **Future Collection Methods.** The decision to collect special assessments by any particular method – e.g., on the tax roll or by direct bill – does not mean that such method will be used to collect special assessments in future years, and the District reserves the right in its sole discretion to select collection methods in any given year, regardless of past practices.\n\n**SECTION 4.** **Assessment Roll.** The Assessment Roll, attached to this Resolution as Exhibit “B,” is hereby certified for collection. That portion of the Assessment Roll which includes the Tax Roll Property is hereby certified to the County Tax Collector and shall be collected by the County Tax Collector in the same manner and time as County taxes. The proceeds therefrom shall be paid to the District.\n\n**SECTION 5.** **Assessment Roll Amendment.** The District Manager shall keep apprised of all updates made to the County property roll by the Property Appraiser after the date of this Resolution, and shall amend the Assessment Roll in accordance with any such updates, for such time as authorized by Florida law, to the County property roll. After any amendment of the Assessment Roll, the District Manager shall file the updates in the District records.\n\n**SECTION 6.** **Severability.** The invalidity or unenforceability of any one or more provisions of this Resolution shall not affect the validity or enforceability of the remaining portions of this Resolution, or any part thereof.\n\n**SECTION 7.** **Effective Date.** This Resolution shall take effect upon the passage and adoption of this Resolution by the Board.\n\nPASSED AND ADOPTED this 5th day of September, 2019.\n\nATTEST: WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n___________________________________________ By:______________________________\nSecretary / Assistant Secretary\n\n___________________________________________ lts:______________________________\n\nExhibit A: Budget\nExhibit B: Assessment Roll (Uniform Method)\nAssessment Roll (Direct Collect)\n\nExhibit A: Budget\n\nExhibit B: Assessment Roll (Uniform Method)\nAssessment Roll (Direct Collect)\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n5\n\nBoard of Supervisors\nWildBlue Community Development District\nLee County, Florida\n\nWe are pleased to provide the following information related to our audit of WildBlue Community Development District for the 11 months ended September 30, 2018 to assist you in your oversight responsibility of the financial reporting process of the District.\n\nOur responsibility under the auditing standards has been described to you in our engagement letter dated May 22, 2019.\n\nManagement is responsible for the appropriateness of the accounting policies used by the District. During the year, no significant new accounting policies were adopted nor were there any changes in the existing accounting policies.\n\nWe did not discuss with Management, any significant or unusual transactions nor did we discuss any alternative treatments available under generally accepted accounting policies during the current audit period.\n\nAny audit adjustments provided by Management or communicated to Management have been reported to and agreed upon by Management. If you would like a detailed listing of all audit adjustments for the current period, please contact us.\n\nWe did not encounter any immaterial uncorrected misstatements during the course of our audit.\n\nThere are no disagreements with Management over the application of significant accounting principles, the basis for judgments made by Management on any significant matters, the scope of the audit or significant disclosures to be included in the financial statements.\n\nWe are not aware of any consultations Management had with other accountants about accounting or auditing matters.\n\nThere were no significant issues that were discussed during the course of the audit.\n\nWe did not encounter any difficulties in dealing with Management during the audit process.\n\nManagement has made certain written representations to us as part of the audit process. Please contact us if you would like a copy of those representations.\n\nThis letter is intended solely for the information and use of the Board and Management and is not intended to be and should not be used by anyone other than the intended parties. Please contact J. W. Gaines should you have any questions concerning this letter. We greatly appreciate the opportunity to be of service to WildBlue Community Development District.\n\nBerger, Toombs, Elam, Gaines & Frank\nFort Pierce, Florida\n\nJune 17, 2019\n\nWildBlue Community Development District\n\nANNUAL FINANCIAL REPORT\n\nSeptember 30, 2018\n\n# WildBlue Community Development District\n\n## ANNUAL FINANCIAL REPORT\n\n**September 30, 2018**\n\n### TABLE OF CONTENTS\n\n| Section | Page Number |\n|------------------------------------------------------------------------|-------------|\n| REPORT OF INDEPENDENT AUDITORS | 1-2 |\n| MANAGEMENT’S DISCUSSION AND ANALYSIS | 3-7 |\n| BASIC FINANCIAL STATEMENTS: | |\n| Government-wide Financial Statements: | |\n| Statement of Net Position | 8 |\n| Statement of Activities | 9 |\n| Fund Financial Statements: | |\n| Balance Sheet – Governmental Funds | 10 |\n| Reconciliation of Total Governmental Fund Balances to Net Position of | 11 |\n| Governmental Activities | |\n| Statement of Revenues, Expenditures and Changes in Fund Balances – | 12 |\n| Governmental Funds | |\n| Reconciliation of the Statement of Revenues, Expenditures and Changes | 13 |\n| in Fund Balances of Governmental Funds to the Statement of Activities | |\n| Statement of Revenues, Expenditures and Changes in Fund Balances – | 14 |\n| Budget and Actual – General Fund | |\n| Notes to Financial Statements | 15-20 |\n| INDEPENDENT AUDITOR’S REPORT ON INTERNAL CONTROL OVER FINANCIAL | 21-22 |\n| REPORTING AND ON COMPLIANCE AND OTHER MATTERS BASED ON AN AUDIT OF | |\n| FINANCIAL STATEMENTS PERFORMED IN ACCORDANCE WITH GOVERNMENT AUDITING | |\n| STANDARDS | |\n| MANAGEMENT LETTER | 23-24 |\n\nREPORT OF INDEPENDENT AUDITOR’S\n\nTo the Board of Supervisors\nWildBlue Community Development District\nLee County, Florida\n\nReport on the Financial Statements\n\nWe have audited the accompanying financial statements of WildBlue Community Development District as of and for the 11 months ended September 30, 2018, and related notes to the financial statements, which collectively comprise the District’s basic financial statements as listed in the table of contents.\n\nManagement’s Responsibility for the Financial Statements\n\nManagement is responsible for the preparation and fair presentation of these financial statements in accordance with accounting principles generally accepted in the United States of America; this includes the design, implementation, and maintenance of internal control relevant to the preparation and fair presentation of financial statements that are free from material misstatement, whether due to fraud or error.\n\nAuditor’s Responsibility\n\nOur responsibility is to express an opinion on these financial statements based on our audit. We conducted our audit in accordance with auditing standards generally accepted in the United States of America and the standards applicable to financial audits contained in Government Accounting Standards, issued by the Comptroller General of the United States. Those standards require that we plan and perform the audit to obtain reasonable assurance about whether the financial statements are free from material misstatement.\n\nAn audit involves performing procedures to obtain audit evidence about the amounts and disclosures in the financial statements. The procedures selected depend on the auditor’s judgment, including the assessment of the risks of material misstatement of the financial statements, whether due to fraud or error. In making those risk assessments, the auditor considers internal control relevant to the entity’s preparation and fair presentation of the financial statements in order to design audit procedures that are appropriate in the circumstances, but not for the purpose of expressing an opinion on the effectiveness of the entity’s internal control. Accordingly, we express no such opinion. An audit also includes evaluating the appropriateness of accounting policies used and the reasonableness of significant accounting estimates made by management, as well as evaluating the overall presentation of the financial statements.\n\nWe believe that the audit evidence we have obtained is sufficient and appropriate to provide a basis for our audit opinion.\n\nTo the Board of Supervisors\nWildBlue Community Development District\n\nOpinion\n\nIn our opinion, the basic financial statements referred to above present fairly, in all material respects, the financial position of the governmental activities, and each major fund of WildBlue Community Development District as of September 30, 2018, and the respective changes in financial position and the budgetary comparison for the General Fund for the 11 months then ended in conformity with accounting principles generally accepted in the United States of America.\n\nOther Matters\n\nManagement’s Discussion and Analysis\n\nAccounting principles generally accepted in the United States of America require that the management’s discussion and analysis be presented to supplement the basic financial statements. Such information, although not a part of the basic financial statements, is required by the Governmental Accounting Standards Board who considers it to be an essential part of financial reporting for placing the basic financial statements in an appropriate operational, economical or historical context. We have applied certain limited procedures to the required supplementary information in accordance with auditing standards generally accepted in the United States of America, which consisted principally of inquiries of management about the methods of preparing the information and comparing the information for consistency with management’s responses to our inquiries, the basic financial statements, and other knowledge we obtained during our audit of the basic financial statements. We do not express an opinion or provide any assurance on the information because the limited procedures do not provide us with the sufficient evidence to express an opinion or provide any assurance.\n\nOther Reporting Required by Government Auditing Standards\n\nIn accordance with Government Auditing Standards, we have also issued a report dated June 17, 2019 on our consideration of the District’s internal control over financial reporting and on our tests of its compliance with certain provisions of laws, regulations and contracts.\n\nThe purpose of that report is to describe the scope of our testing of internal control over financial reporting and compliance and the results of that testing, and not to provide an opinion on internal control over financial reporting or on compliance. That report is an integral part of an audit performed in accordance with Government Auditing Standards in considering WildBlue Community Development District’s internal control over financial reporting and compliance.\n\nBerger, Toombs, Elam, Gaines & Frank\nCertified Public Accountants PL\nFort Pierce, Florida\n\nJune 17, 2019\n\nManagement’s discussion and analysis of WildBlue Community Development District’s (the “District”) financial performance provides an objective and easily readable analysis of the District’s financial activities. The analysis provides summary financial information for the District and should be read in conjunction with the District’s financial statements.\n\nOVERVIEW OF THE FINANCIAL STATEMENTS\n\nThe District’s basic financial statements comprise three components; 1) Government-wide financial statements, 2) Fund financial statements, and 3) Notes to financial statements. The Government-wide financial statements present an overall picture of the District’s financial position and results of operations. The Fund financial statements present financial information for the District’s major funds. The Notes to financial statements provide additional information concerning the District’s finances.\n\nThe Government-wide financial statements are the statement of net position and the statement of activities. These statements use accounting methods similar to those used by private-sector companies. Emphasis is placed on the net position of governmental activities and the change in net position. Governmental activities are primarily supported by special assessments.\n\nThe statement of net position presents information on all assets and liabilities of the District, with the difference between assets and liabilities reported as net position. Net position is reported in three categories; 1) net investment in capital assets, 2) restricted, and 3) unrestricted. Assets, liabilities, and net position are reported for all Governmental activities.\n\nThe statement of activities presents information on all revenues and expenses of the District and the change in net position. Expenses are reported by major function and program revenues relating to those functions are reported, providing the net cost of all functions provided by the District. To assist in understanding the District’s operations, expenses have been reported as governmental activities. Governmental activities financed by the District include general government and physical environment.\n\nFund financial statements present financial information for governmental funds. These statements provide financial information for the major funds of the District. Governmental fund financial statements provide information on the current assets and liabilities of the funds, changes in current financial resources (revenues and expenditures), and current available resources.\n\nOVERVIEW OF THE FINANCIAL STATEMENTS (CONTINUED)\n\nFund financial statements include a balance sheet and a statement of revenues, expenditures and changes in fund balances for all governmental funds. A statement of revenues, expenditures, and changes in fund balances – budget and actual is provided for the District’s General Fund. Fund financial statements provide more detailed information about the District’s activities. Individual funds are established by the District to track revenues that are restricted to certain uses or to comply with legal requirements.\n\nThe government-wide financial statements and the fund financial statements provide different pictures of the District. The government-wide financial statements provide an overall picture of the District's financial standing. These statements are comparable to private-sector companies and give a good understanding of the District’s overall financial health and how the District paid for the various activities, or functions, provided by the District. All assets of the District, including buildings and improvements, and infrastructure are reported in the statement of net position. All liabilities, including principal outstanding on bonds are included. The statement of activities includes depreciation on all long lived assets of the District, but transactions between the different functions of the District have been eliminated in order to avoid “doubling up” the revenues and expenses. The fund financial statements provide a picture of the major funds of the District. In the case of governmental activities, outlays for long lived assets are reported as expenditures and long-term liabilities, such as general obligation bonds, are not included in the fund financial statements. To provide a link from the fund financial statements to the government-wide financial statements, reconciliations are provided from the fund financial statements to the government-wide financial statements.\n\nNotes to financial statements provide additional detail concerning the financial activities and financial balances of the District. Additional information about the accounting practices of the District, investments of the District, capital assets and long-term debt are some of the items included in the notes to financial statements.\n\nFinancial Highlights\n\nThe following are the highlights of financial activity for the 11 months ended September 30, 2018.\n\n♦ The District’s liabilities exceeded assets by $(25,764) (net position).\n\n♦ Governmental activities revenues totaled $71,326, while governmental activities expenses totaled $97,090.\n\nOVERVIEW OF THE FINANCIAL STATEMENTS (CONTINUED)\n\nFinancial Analysis of the District\n\nThe following schedule provides a summary of the assets, liabilities and net position of the District and is presented by category for comparison purposes.\n\nNet Position\n\n| Governmental Activities | 2018 |\n|-------------------------|------|\n| Current assets | $ 21,023 |\n| Current liabilities | 46,787 |\n| Net Position | |\n| Unrestricted | (25,764) |\n| Total Net Position | $ (25,764) |\n\nThis is the first year of operations for the District.\n\nOVERVIEW OF THE FINANCIAL STATEMENTS (CONTINUED)\n\nFinancial Analysis of the District (Continued)\n\nThe following schedule provides a summary of the changes in net position of the District and is presented by category for comparison purposes.\n\n| Change In Net Position | Governmental Activities |\n|------------------------|-------------------------|\n| | 2018 |\n| Program Revenues | |\n| Operating contributions| $71,326 |\n| Expenses | |\n| General government | 97,090 |\n| Change in Net Position | (25,764) |\n| Net Position - Beginning of Period | - |\n| Net Position - End of Period | $(25,764) |\n\nThis is the first year of operations for the District.\n\nGeneral Fund Budgetary Highlights\n\nActual expenditures were less than the final budget because there were lower insurance, trustee fees and legal fees expenditures than anticipated.\n\nThere were no amendments to the September 30, 2018 budget.\n\nEconomic Factors and Next Year’s Budget\n\nThe District issued Public Improvement Fee Bonds, Series 2019 sometime in the next fiscal year to finance the costs of certain improvements within and without the District.\n\nOVERVIEW OF THE FINANCIAL STATEMENTS (CONTINUED)\n\nRequest for Information\n\nThe financial report is designed to provide a general overview of WildBlue Community Development District's finances for all those with an interest. Questions concerning any of the information provided in this report or requests for additional information should be addressed to the WildBlue Community Development District’s Finance Department at 2300 Glades Road, Suite 410W, Boca Raton, Florida 33431.\n\nWildBlue Community Development District\nSTATEMENT OF NET POSITION\nSeptember 30, 2018\n\n| ASSETS | Governmental Activities |\n|---------------------------------------------|------------------------|\n| Current Assets | |\n| Cash | $5,743 |\n| Due from developer | 15,280 |\n| Total Current Assets | 21,023 |\n\n| LIABILITIES | Governmental Activities |\n|---------------------------------------------|------------------------|\n| Current Liabilities | |\n| Accounts payable and accrued expenses | 14,999 |\n| Due to developer | 6,000 |\n| Note payable-developer | 25,788 |\n| Total Current Liabilities | 46,787 |\n\n| NET POSITION | Governmental Activities |\n|---------------------------------------------|------------------------|\n| Unrestricted | $(25,764) |\n\nSee accompanying notes to financial statements.\n\nWildBlue Community Development District\nSTATEMENT OF ACTIVITIES\nFor the 11 Months Ended September 30, 2018\n\n| Functions/Programs | Expenses | Program Revenues | Net (Expenses) Revenues and Changes in Net Position |\n|------------------------------------|------------|------------------|-----------------------------------------------------|\n| Governmental Activities | | | |\n| General government | $(97,090) | $71,326 | $(25,764) |\n\nChange in Net Position: $(25,764)\n\nNet Position - November 9, 2017: -\nNet Position - September 30, 2018: $(25,764)\n\nSee accompanying notes to financial statements.\n\nWildBlue Community Development District\nBALANCE SHEET\nGOVERNMENTAL FUNDS\nSeptember 30, 2018\n\n| ASSETS | General | Debt Service | Capital Projects | Total Governmental Funds |\n|--------|---------|--------------|------------------|--------------------------|\n| Cash | $5,743 | - | - | $5,743 |\n| Due from developer | $14,635 | $215 | $430 | $15,280 |\n| **Total Assets** | **$20,378** | **$215** | **$430** | **$21,023** |\n\n| LIABILITIES AND FUND BALANCES | General | Debt Service | Capital Projects | Total Governmental Funds |\n|-------------------------------|---------|--------------|------------------|--------------------------|\n| **LIABILITIES** | | | | |\n| Accounts payable and accrued expenses | $14,354 | $215 | $430 | $14,999 |\n| Due to developer | $6,000 | - | - | $6,000 |\n| **Total Liabilities** | **$20,354** | **$215** | **$430** | **$20,999** |\n| **FUND BALANCES** | | | | |\n| Unassigned | $24 | - | - | $24 |\n| **Total Liabilities and Fund Balances** | **$20,378** | **$215** | **$430** | **$21,023** |\n\nSee accompanying notes to financial statements.\n\nWildBlue Community Development District\n\nRECONCILIATION OF TOTAL GOVERNMENTAL FUND BALANCES\nTO NET POSITION OF GOVERNMENTAL ACTIVITIES\nSeptember 30, 2018\n\nTotal Governmental Fund Balances $ 24\n\nAmounts reported for governmental activities in the Statement of Net Position are different because:\n\nA developer advance was recognized as an other financing source at the fund level, however it increases liabilities at the government-wide level. (25,788)\n\nNet Position of Governmental Activities $ (25,764)\n\nSee accompanying notes to financial statements.\n\nWildBlue Community Development District\nSTATEMENT OF REVENUES, EXPENDITURES AND CHANGES IN FUND BALANCES – GOVERNMENTAL FUNDS\nFor the 11 Months Ended September 30, 2018\n\n| | General | Debt Service | Capital Projects | Total Governmental Funds |\n|--------------------------------|---------|--------------|------------------|--------------------------|\n| **Revenues** | | | | |\n| Developer contributions | $71,326 | $- | $- | $71,326 |\n| **Expenditures** | | | | |\n| Current | | | | |\n| General government | 71,302 | - | 430 | 71,732 |\n| Debt service | | 25,358 | - | 25,358 |\n| Other debt service | - | - | - | - |\n| **Total Expenditures** | 71,302 | 25,358 | 430 | 97,090 |\n| **Excess of revenues over/(under) Expenditures** | 24 | (25,358) | (430) | (25,764) |\n| **Other Financing Sources/(Uses)** | | | | |\n| Developer advance | - | 25,358 | 430 | 25,788 |\n| **Net change in fund balances**| 24 | - | - | 24 |\n| Fund Balances - November 9, 2017 | - | - | - | - |\n| Fund Balances - September 30, 2018 | $24 | $- | $- | $24 |\n\nSee accompanying notes to financial statements.\n\nWildBlue Community Development District\n\nRECONCILIATION OF THE STATEMENT\nOF REVENUES, EXPENDITURES\nAND CHANGES IN FUND BALANCES OF GOVERNMENTAL FUNDS\nTO THE STATEMENT OF ACTIVITIES\nFor the 11 Months Ended September 30, 2018\n\nNet Change in Fund Balances - Total Governmental Funds $ 24\n\nAmounts reported for governmental activities in the Statement of Activities are different because:\n\nAt the fund level, an advance from the developer is recognized as an other financing source, however, the advance increases a liability at the government-wide level.\n\n$(25,788)\n\nChange in Net Position of Governmental Activities $(25,764)\n\nSee accompanying notes to financial statements.\n\nWildBlue Community Development District\nSTATEMENT OF REVENUES, EXPENDITURES AND CHANGES IN FUND BALANCES – BUDGET AND ACTUAL – GENERAL FUND\nFor the 11 Months Ended September 30, 2018\n\n| | Original Budget | Final Budget | Actual | Variance with Final Budget Positive (Negative) |\n|--------------------------------|-----------------|--------------|----------|-----------------------------------------------|\n| Revenues | | | | |\n| Developer contributions | $90,225 | $90,225 | $71,326 | $(18,899) |\n| Expenditures | | | | |\n| Current | | | | |\n| General government | 90,225 | 90,225 | 71,302 | 18,923 |\n| Net Change in Fund Balances | - | - | 24 | 24 |\n| Fund Balances - November 9, 2017| - | - | - | - |\n| Fund Balances - September 30, 2018| $- | $- | $24 | $24 |\n\nSee accompanying notes to financial statements.\n\nNOTE A – SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES\n\nThe financial statements of the District have been prepared in conformity with generally accepted accounting principles (GAAP) as applied to governmental units. The Governmental Accounting Standards Board (GASB) is the accepted standard-setting body for establishing governmental accounting and financial reporting principles. The District's more significant accounting policies are described below.\n\n1. Reporting Entity\n\nThe District was established on November 9, 2017, pursuant to the Uniform Community Development District Act of 1980, Chapter 190, Florida Statutes, as amended (the \"Act\"), and by Ordinance 17-17 of Lee County, Florida, as a Community Development District. The District was established for the purposes of financing and managing the acquisition, construction, maintenance and operation of the infrastructure necessary for community development within its jurisdiction. The District is authorized to issue bonds for the purpose, among others, of financing, funding, planning, establishing, acquiring, constructing district roads, landscaping, and other basic infrastructure projects within or outside the boundaries of the WildBlue Community Development District. The District is governed by a five member Board of Supervisors. All the Supervisors are employed by the Developer. The District operates within the criteria established by Chapter 190.\n\nAs required by GAAP, these financial statements present the WildBlue Community Development District (the primary government) as a stand-alone government. The reporting entity for the District includes all functions of government in which the District's Board exercises oversight responsibility including, but not limited to, financial interdependency, selection of governing authority, designation of management, significant ability to influence operations and accountability for fiscal matters.\n\nBased upon the application of the above-mentioned criteria as set forth in Governmental Accounting Standards Board, The Financial Reporting Entity, the District has identified no component units.\n\n2. Measurement Focus and Basis of Accounting\n\nThe basic financial statements of the District are composed of the following:\n\n- Government-wide financial statements\n- Fund financial statements\n- Notes to financial statements\n\nNOTE A – SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES (CONTINUED)\n\n2. Measurement Focus and Basis of Accounting (Continued)\n\na. Government-wide Financial Statements\n\nGovernment-wide financial statements report all non-fiduciary information about the reporting government as a whole. These statements include all the governmental activities of the primary government. The effect of interfund activity has been removed from these statements.\n\nGovernmental activities are supported by special assessments and interest. Program revenues are netted with program expenses in the statement of activities to present the net cost of each program.\n\nAmounts paid to acquire capital assets are capitalized as assets, rather than reported as an expenditure. Proceeds of long-term debt are recorded as liabilities in the government-wide financial statements, rather than as an other financing source.\n\nAmounts paid to reduce long-term indebtedness of the reporting government are reported as a reduction of the related liability, rather than as an expenditure.\n\nb. Fund Financial Statements\n\nThe underlying accounting system of the District is organized and operated on the basis of separate funds, each of which is considered to be a separate accounting entity. The operations of each fund are accounted for with a separate set of self-balancing accounts that comprise its assets, liabilities, fund equity, revenues and expenditures or expenses, as appropriate. Governmental resources are allocated to and accounted for in individual funds based upon the purposes for which they are to be spent and the means by which spending activities are controlled.\n\nFund financial statements for the primary government’s governmental funds are presented after the government-wide financial statements. These statements display information about major funds individually.\n\nNOTE A – SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES (CONTINUED)\n\n2. Measurement Focus and Basis of Accounting (Continued)\n\nb. Fund Financial Statements (Continued)\n\nGovernmental Funds\n\nThe District classifies fund balance according to Governmental Accounting Standards Board Statement 54 – Fund Balance Reporting and Governmental Fund Type Definitions. The Statement requires the fund balance for governmental funds to be reported in classifications that comprise a hierarchy based primarily on the extent to which the government is bound to honor constraints on the specific purposes for which amounts in those funds can be spent.\n\nThe District has various policies governing the fund balance classifications.\n\nNonspendable Fund Balance – This classification consists of amounts that cannot be spent because they are either not in spendable form or are legally or contractually required to be maintained intact.\n\nRestricted Fund Balance – This classification includes amounts that can be spent only for specific purposes stipulated by constitution, external resource providers, or through enabling legislation.\n\nAssigned Fund Balance – This classification consists of the Board of Supervisors’ intent to be used for specific purposes, but are neither restricted nor committed. The assigned fund balances can also be assigned by the District’s management company.\n\nUnassigned Fund Balance – This classification is the residual classification for the government’s general fund and includes all spendable amounts not contained in the other classifications. Unassigned fund balance is considered to be utilized first when an expenditure is incurred for purposes for which amounts in any of those unrestricted fund balance classifications could be used.\n\nFund Balance Spending Hierarchy – For all governmental funds except special revenue funds, when restricted, committed, assigned, and unassigned fund balances are combined in a fund, qualified expenditures are paid first from restricted or committed fund balance, as appropriate, then assigned and finally unassigned fund balances.\n\n2. Measurement Focus and Basis of Accounting (Continued)\n\nb. Fund Financial Statements (Continued)\n\nGovernmental Funds (Continued)\n\nGovernmental fund financial statements are reported using the current financial resources measurement focus and the modified accrual basis of accounting. Revenues are considered to be available when they are collected within the current period or soon thereafter to pay liabilities of the current period. For this purpose, the District considers revenues to be available if they are collected within 60 days of the end of the current fiscal period.\n\nExpenditures generally are recorded when a liability is incurred, as under accrual accounting. Interest associated with the current fiscal period is considered to be an accrual item and so has been recognized as revenue of the current fiscal period.\n\nUnder the current financial resources measurement focus, only current assets and current liabilities are generally included on the balance sheet. The reported fund balance is considered to be a measure of “available spendable resources”.\n\nGovernmental fund operating statements present increases (revenues and other financing sources) and decreases (expenditures and other financing uses) in net current assets. Accordingly, they are said to present a summary of sources and uses of “available spendable resources” during a period.\n\nBecause of their spending measurement focus, expenditure recognition for governmental fund types excludes amounts represented by non-current liabilities. Since they do not affect net current assets, such long-term amounts are not recognized as governmental fund type expenditures or fund liabilities.\n\nAmounts expended to acquire capital assets are recorded as expenditures in the year that resources are expended, rather than as fund assets. The proceeds of long-term debt are recorded as an other financing source rather than as a fund liability.\n\nDebt service expenditures are recorded only when payment is due.\n\n3. Basis of Presentation\n\na. Governmental Major Funds\n\nGeneral Fund – The General Fund is the District’s primary operating fund. It accounts for all financial resources of the general government, except those required to be accounted for in another fund.\n\n3. Basis of Presentation (Continued)\n\na. Governmental Major Funds (Continued)\n\n Debt Service Fund – The Debt Service Fund accounts for the certain preliminary costs associated with the issuance of new debt.\n\n Capital Projects Fund – The Capital Projects Fund accounts for the construction of infrastructure improvements within the District.\n\nb. Non-current Governmental Assets/Liabilities\n\n GASB Statement 34 requires that non-current governmental assets, such as land and improvements, and non-current governmental liabilities, such as general obligation bonds and due to developer be reported in the governmental activities column in the government-wide Statement of Net Position.\n\n4. Assets, Liabilities, and Net Position or Equity\n\na. Cash and Investments\n\n Florida Statutes require state and local governmental units to deposit monies with financial institutions classified as \"Qualified Public Depositories,\" a multiple financial institution pool whereby groups of securities pledged by the various financial institutions provide common collateral from their deposits of public funds. This pool is provided as additional insurance to the federal depository insurance and allows for additional assessments against the member institutions, providing full insurance for public deposits.\n\n The District is authorized to invest in those financial instruments as established by Section 218.415, Florida Statutes. The authorized investments consist of:\n\n 1. Direct obligations of the United States Treasury;\n 2. The Local Government Surplus Funds Trust or any intergovernmental investment pool authorized pursuant to the Florida Interlocal Cooperative Act of 1969;\n 3. Interest-bearing time deposits or savings accounts in authorized qualified public depositories;\n 4. Securities and Exchange Commission, registered money market funds with the highest credit quality rating from a nationally recognized rating agency\n\n The District currently has no investments.\n\nNOTE A – SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES (CONTINUED)\n\n4. Assets, Liabilities, and Net Position or Equity (Continued)\n\na. Cash and Investments (Continued)\n\nCash equivalents include time deposits and all highly liquid debt instruments with original maturities of three months or less and held in a qualified public depository as defined by Section 280.02, Florida Statutes.\n\nb. Budgets\n\nBudgets are prepared and adopted after public hearings for the governmental funds, pursuant to Chapter 190, Florida Statutes. The District utilizes the same basis of accounting for budgets as it does for revenues and expenditures in its various funds. The legal level of budgetary control is at the fund level. All budgeted appropriations lapse at year end. A formal budget is adopted for the general fund. As a result, deficits in the budget columns of the accompanying financial statements may occur.\n\nNOTE B – RELATED PARTY TRANSACTIONS\n\nAll voting members of the Board of Supervisors are employed by the Developer or a related entity. The District received $71,326 in contributions from the Developer for the 11 months ended September 30, 2018. Additionally, the District has $6,000 due to the developer and a note payable of $25,788.\n\nNOTE C – ECONOMIC DEPENDENCY\n\nThe Developer owns a significant portion of land within the District. The District’s activity is dependent upon the continued involvement of the Developer, the loss of which could have a material adverse effect on the District’s operations.\n\nNOTE D – RISK MANAGEMENT\n\nThe District is exposed to various risks of loss related to torts; theft of, damage to and destruction of assets; errors and omissions; and natural disasters for which the government carries commercial insurance. The District has not filed any claims under this commercial coverage.\n\nNOTE E – MANAGEMENT COMPANY\n\nThe District has contracted with a management company to perform management advisory services, which include financial and accounting advisory services. Certain employees of the management company also serve as officers (Board appointed non-voting positions) of the District. Under the agreement, the District compensates the management company for management, accounting, financial reporting, and other administrative costs.\n\nINDEPENDENT AUDITOR’S REPORT ON INTERNAL CONTROL OVER FINANCIAL REPORTING AND ON COMPLIANCE AND OTHER MATTERS BASED ON AN AUDIT OF FINANCIAL STATEMENTS PERFORMED IN ACCORDANCE WITH GOVERNMENT AUDITING STANDARDS\n\nTo the Board of Supervisors\nWildBlue Community Development District\nLee County, Florida\n\nWe have audited, in accordance with the auditing standards generally accepted in the United States of America and the standards applicable to financial audits contained in Government Auditing Standards issued by the Comptroller General of the United States, the financial statements of WildBlue Community Development District, as of and for the 11 months ended September 30, 2018, and the related notes to the financial statements, and have issued our report thereon dated June 17, 2019.\n\nInternal Control Over Financial Reporting\n\nIn planning and performing our audit, we considered WildBlue Community Development District’s internal control over financial reporting to determine the audit procedures that are appropriate in the circumstances for the purpose of expressing our opinions on the financial statements, but not for the purpose of expressing an opinion on the effectiveness of WildBlue Community Development District’s internal control. Accordingly, we do not express an opinion on the effectiveness of WildBlue Community Development District’s internal control over financial reporting.\n\nA deficiency in internal control exists when the design or operation of a control does not allow management or employees, in the normal course of performing their assigned functions, to prevent, or detect and correct misstatements on a timely basis. A material weakness is a deficiency, or combination of deficiencies, in internal control, such that there is a reasonable possibility that a material misstatement of the entity’s financial statements will not be prevented, or detected and corrected on a timely basis. A significant deficiency is a deficiency, or a combination of deficiencies, in internal control that is less severe than a material weakness, yet important enough to merit attention by those charged with governance.\n\nOur consideration of internal control over financial reporting was for the limited purpose described in the first paragraph of this section and was not designed to identify all deficiencies in internal control that might be material weaknesses or significant deficiencies. Given these limitations, during our audit we did not identify any deficiencies in internal control that we consider to be material weaknesses. However, material weaknesses may exist that have not been identified.\n\nCompliance and Other Matters\n\nAs part of obtaining reasonable assurance about whether WildBlue Community Development District's financial statements are free of material misstatement, we performed tests of its compliance with certain provisions of laws, regulations, contracts, and grant agreements, noncompliance with which could have a direct and material effect on the determination of financial statement amounts. However, providing an opinion on compliance with those provisions was not an objective of our audit, and accordingly, we do not express such an opinion. The results of our tests disclosed no instances of noncompliance or other matters that are required to be reported under Government Auditing Standards.\n\nPurpose of this Report\n\nThe purpose of this report is solely to describe the scope of our testing of internal control and compliance and the results of that testing, and not to provide an opinion on the effectiveness of the entity's internal control or on compliance. This report is an integral part of an audit performed in accordance with Government Auditing Standards in considering the entity's internal control and compliance. Accordingly, this communication is not suitable for any other purpose.\n\nBerger, Toombs, Elam, Gaines & Frank\nCertified Public Accountants\nFort Pierce, Florida\n\nJune 17, 2019\n\nTo the Board of Supervisors\nWildBlue Community Development District\nLee County, Florida\n\nReport on the Financial Statements\n\nWe have audited the financial statements of the WildBlue Community Development District as of and for the 11 months ended September 30, 2018, and have issued our report thereon dated June 17, 2019.\n\nAuditor’s Responsibility\n\nWe conducted our audit in accordance with auditing standards generally accepted in the United States; the standards applicable to financial audits contained in Government Auditing Standards, issued by the Comptroller General of the United States and Chapter 10.550, Rules of the Florida Auditor General.\n\nOther Reporting Requirements\n\nWe have issued our Independent Auditor’s Report on Internal Control over Financial Reporting and on Compliance and Other Matters Based on an Audit of Financial Statements Performed in Accordance with Government Auditing Standards and our Independent Auditor’s Report on an examination conducted in accordance with AICPA Professionals Standards, AT-C Section 315 regarding compliance requirements in accordance with Chapter 10.550, Rules of the Auditor General. Disclosures in that report, which is dated June 17, 2019, should be considered in conjunction with this management letter.\n\nPrior Audit Findings\n\nSection 10.554(1)(i)1., Rules of the Auditor General, requires that we determine whether or not corrective actions have been made to address findings and recommendations made in the preceding financial audit report. This is the initial period of operations for the District.\n\nFinancial Condition and Management\n\nSection 10.554(1)(i)5.a. and 10.556(7), Rules of the Auditor General, requires us to apply appropriate procedures and communicate the results of our determination as to whether or not WildBlue Community Development District has met one or more of the conditions described in Section 218.503(1), Florida Statutes, and to identify the specific conditions met. In connection with our audit, we determined that the WildBlue Community Development District did not meet any of the conditions described in Section 218.503(1), Florida Statutes.\n\nPursuant to Sections 10.554(1)(i)5.c. and 10.556(8), Rules of the Auditor General, we applied financial conditions assessment procedures as of September 30, 2018 for the WildBlue Community Development District. It is management’s responsibility to monitor the WildBlue Community Development District’s financial condition; our financial condition assessment was based in part on the representations made by management and the review of the financial information provided by the same.\n\nTo the Board of Supervisors\nWildBlue Community Development District\n\nSection 10.554(1)(i)2., Rules of the Auditor General, requires that we communicate any recommendations to improve financial management. In connection with our audit, we did not have any such recommendations.\n\n**Additional Matters**\n\nSection 10.554(1)(i)3., Rules of the Auditor General, requires us to communicate noncompliance with provisions of contracts or grant agreements, or abuse, that have occurred, or are likely to have occurred, that have an effect on the financial statements that is less than material but which warrants the attention of those charged with governance. In connection with our audit, we noted no such findings.\n\n**Purpose of this Letter**\n\nOur management letter is intended solely for the information and use of the Legislative Auditing Committee, members of the Florida Senate and the Florida House of Representatives, the Florida Auditor General, Federal and other granting agencies, the Board of Supervisors, and applicable management, and is not intended to be and should not be used by anyone other than these specified parties.\n\nBerger, Toombs, Elam, Gaines & Frank\nCertified Public Accountants PL\nFort Pierce, Florida\n\nJune 17, 2019\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n6\n\nRESOLUTION 2019-12\n\nA RESOLUTION OF THE BOARD OF SUPERVISORS OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT HEREBY ACCEPTING THE AUDITED FINANCIAL REPORT FOR THE FISCAL YEAR ENDED SEPTEMBER 30, 2018\n\nWHEREAS, the District’s Auditor, Berger, Toombs, Elam, Gaines & Frank, has heretofore prepared and submitted to the Board, for accepting, the District’s Audited Financial Statements for Fiscal Year 2018;\n\nNOW, THEREFORE BE IT RESOLVED BY THE BOARD OF SUPERVISORS OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT;\n\n1. The Audited Financial Report for Fiscal Year 2018, heretofore submitted to the Board, is hereby accepted for Fiscal Year 2018, for the period ending September 30, 2018; and\n\n2. A verified copy of said Audited Financial Report for Fiscal Year 2018 shall be attached hereto as an exhibit to this Resolution, in the District’s “Official Record of Proceedings”.\n\nPASSED AND ADOPTED this _____ day of ____________________, 2019.\n\nWILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n_____________________________ ________________________________\nSecretary/Assistant Secretary Chair/Vice Chair, Board of Supervisors\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n7\n\nRESOLUTION 2019-13\n\nA RESOLUTION OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT DESIGNATING DATES, TIMES AND LOCATIONS FOR REGULAR MEETINGS OF THE BOARD OF SUPERVISORS OF THE DISTRICT FOR FISCAL YEAR 2019/2020 AND PROVIDING FOR AN EFFECTIVE DATE\n\nWHEREAS, the WildBlue Community Development District (“District”) is a local unit of special-purpose government created and existing pursuant to Chapter 190, Florida Statutes, being situated entirely within Lee County, Florida; and\n\nWHEREAS, the Board of Supervisors of the District (“Board”) is statutorily authorized to exercise the powers granted to the District; and\n\nWHEREAS, all meetings of the Board shall be open to the public and governed by the provisions of Chapter 286, Florida Statutes; and\n\nWHEREAS, the Board is statutorily required to file annually, with the local governing authority and the Florida Department of Economic Opportunity, a schedule of its regular meetings.\n\nNOW, THEREFORE, BE IT RESOLVED BY THE BOARD OF SUPERVISORS OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT:\n\nSECTION 1. ADOPTING REGULAR MEETING SCHEDULE. Regular meetings of the District’s Board shall be held during Fiscal Year 2019/2020 as provided on the schedule attached hereto as Exhibit A.\n\nSECTION 2. FILING REQUIREMENT. In accordance with Section 189.015(1), Florida Statutes, the District’s Secretary is hereby directed to file a schedule of the District’s regular meetings annually with Lee County and the Florida Department of Economic Opportunity.\n\nSECTION 3. EFFECTIVE DATE. This Resolution shall take effect immediately upon adoption.\n\nPASSED AND ADOPTED this _______ day of ________________, 2019.\n\nAttest: WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n__________________________ ____________________________\nSecretary/Assistant Secretary Chair/Vice Chair, Board of Supervisors\n\n| DATE | POTENTIAL DISCUSSION/FOCUS | TIME |\n|--------------------|----------------------------|--------|\n| October 3, 2019 | Regular Meeting | 11:00 AM |\n| November 7, 2019 | Regular Meeting | 11:00 AM |\n| December 5, 2019 | Regular Meeting | 11:00 AM |\n| January 2, 2020 | Regular Meeting | 11:00 AM |\n| February 6, 2020 | Regular Meeting | 11:00 AM |\n| March 5, 2020 | Regular Meeting | 11:00 AM |\n| April 2, 2020 | Regular Meeting | 11:00 AM |\n| May 7, 2020 | Regular Meeting | 11:00 AM |\n| June 4, 2020 | Regular Meeting | 11:00 AM |\n| July 2, 2020 | Public Hearing & Regular Meeting | 11:00 AM |\n| August 6, 2020 | Regular Meeting | 11:00 AM |\n| September 3, 2020 | Public Hearing & Regular Meeting | 11:00 AM |\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n8\n\nA RESOLUTION OF THE BOARD OF SUPERVISORS OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT RATIFYING, CONFIRMING AND APPROVING THE SALE OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT SPECIAL ASSESSMENT BONDS, SERIES 2019; RATIFYING, CONFIRMING AND APPROVING THE ACTIONS OF THE CHAIRMAN, VICE CHAIRMAN, TREASURER, SECRETARY, ASSISTANT SECRETARIES AND ALL DISTRICT STAFF REGARDING THE SALE AND CLOSING OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT SPECIAL ASSESSMENT BONDS, SERIES 2019; DETERMINING SUCH ACTIONS AS BEING IN ACCORDANCE WITH THE AUTHORIZATION GRANTED BY THE BOARD; PROVIDING A SEVERABILITY CLAUSE; AND PROVIDING AN EFFECTIVE DATE.\n\nWHEREAS, the WildBlue Community Development District (the “District”), is a local unit of special-purpose government created and existing pursuant to Chapter 190, Florida Statutes, being situated in Lee County; and\n\nWHEREAS, the District previously adopted resolutions authorizing the issuance and the negotiated sale of bonds within the scope of Chapter 190, Florida Statutes, including its $23,470,000 Special Assessment Bonds, Series 2019 (the “Series 2019 Bonds”); and\n\nWHEREAS, the District has closed on the sale of the Series 2019 Bonds; and\n\nWHEREAS, as prerequisites to the issuance of the Series 2019 Bonds, the Chairman, Vice Chairman, Treasurer, Assistant Secretaries and District Staff, including the District Manager, District Financial Advisor, District Engineer, Bond Counsel and District Counsel, were required to execute and deliver various documents (the “Closing Documents”); and\n\nWHEREAS, the District desires to ratify, confirm, and approve all actions of the District Chairman, Vice Chairman, Treasurer, Assistant Secretaries, and District Staff in closing the sale of the Series 2019 Bonds.\n\nNOW, THEREFORE, BE IT RESOLVED BY THE BOARD OF SUPERVISORS OF THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT:\n\nSECTION 1. The sale, issuance, and closing of the Series 2019 Bonds is in the best interests of the District.\n\nSECTION 2. The issuance and sale of the Series 2019 Bonds, the adoption of resolutions relating to such bonds, and all actions taken in the furtherance of the closing on such bonds, are hereby declared and affirmed as being in the best interests of the District and are hereby ratified, approved, and confirmed.\n\nSECTION 3. The actions of the Chairman, Vice Chairman, Treasurer, Secretary, Assistant Secretaries, and all District Staff in finalizing the closing and issuance of the Series 2019 Bonds, including the execution and delivery of the Closing Documents, and such other certifications or other documents required for the closing on the Series 2019 Bonds, are determined to be in accordance with the prior authorizations of the Board and are hereby ratified, approved, and confirmed in all respects.\n\nSECTION 4. If any provision of this Resolution is held to be illegal or invalid, the other provisions shall remain in full force and effect.\n\nSECTION 5. This Resolution shall become effective upon its passage and shall remain in effect unless rescinded or repealed.\n\nPASSED AND ADOPTED this 5th day of September, 2019.\n\nATTEST:\n\nWILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n_____________________________ ________________________________\nSecretary/Assistant Secretary Chair/Vice Chair, Board of Supervisors\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n9\n\nDISCLOSURE OF PUBLIC FINANCING AND MAINTENANCE OF IMPROVEMENTS TO REAL PROPERTY UNDERTAKEN BY THE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\nBoard of Supervisors¹\n\nWildBlue Community Development District\n\nRussell Smith\nChairman\n\nChris Hasty\nVice Chairman\n\nDavid Caldwell\nAssistant Secretary\n\nBarry Ernst\nAssistant Secretary\n\nChris Johnson\nAssistant Secretary\n\nWrathell, Hunt and Associates, LLC\n2300 Glades Road, Suite 410W\nBoca Raton, Florida 33431\n\nDistrict records are on file at the offices of Wrathell, Hunt and Associates, LLC and are available for public inspection upon request during normal business hours.\n\n¹ This list reflects the composition of the Board of Supervisors as of June 1, 2019. For a current list of Board Members, please contact the District Manager’s office.\n\n# TABLE OF CONTENTS\n\nIntroduction ........................................................................................................................................... 3\n\nWhat is the District and how is it governed? .................................................................................. 4\n\nWhat infrastructure improvements does the District provide and how are the improvements paid for? ............................................................................................................................................................................. 5\n\nAssessments, Fees and Charges ......................................................................................................... 7\n\nMethod of Collection ............................................................................................................................ 8\n\nINTRODUCTION\n\nThe WildBlue Community Development District (“District”) is a local unit of special-purpose government created pursuant to and existing under the provisions of Chapter 190, Florida Statutes. Under Florida law, community development districts are required to take affirmative steps to provide for the full disclosure of information relating to the public financing and maintenance of improvements to real property undertaken by such districts. Unlike city and county governments, the District has only certain limited powers and responsibilities. These powers and responsibilities include, for example, construction and/or acquisition of drainage and surface water management systems, onsite roadways, onsite utilities, offsite utility and roadway improvements, and environmental restoration and mitigation. Additionally, it is anticipated that the District will be responsible for the maintenance of the surface water management system onsite roadways, irrigation and landscaping.\n\nDISCLOSURE OF PUBLIC FINANCING AND MAINTENANCE\nOF IMPROVEMENTS TO REAL PROPERTY UNDERTAKEN BY\nTHE WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\nUnder Florida law, community development districts are required to take affirmative steps to provide for the full disclosure of information relating to the public financing and maintenance of improvements to real property undertaken by such districts. The law specifically provides that this information shall be made available to all persons currently residing within the District and to all prospective District residents. The following information describing the WildBlue Community Development District and the assessments, fees and charges that may be levied within the District to pay for certain community infrastructure is provided to fulfill this statutory requirement.\n\nWhat is the District and how is it governed?\n\nThe District is an independent special taxing district, created pursuant to and existing under the provisions of Chapter 190, Florida Statutes (the “Act”), and established by Ordinance 17-17 enacted by the Board of County Commissioners of Lee County, Florida, effective as of November 9, 2017, and amended by Ordinance 19-12, effective June 19, 2019. The District encompasses approximately 2,352.08 acres located entirely within the boundaries of Lee County, Florida. As a local unit of special-purpose government, the District provides an alternative means for planning, financing, constructing, operating and maintaining various public improvements and community facilities within its jurisdiction.\n\nThe District is governed by a five-member Board of Supervisors (the “Board”), the members of which must be residents of the State and citizens of the United States. Board members were elected on an at-large basis by the owners of property within the District, each landowner being entitled to one vote for each acre of land with fractions thereof rounded upward to the nearest whole number. Elections are then held every two years in November. Commencing when both (i) six years after the initial appointment of Supervisors have passed and (ii) the District has attained a minimum of two hundred and fifty (250) qualified electors, Supervisors whose terms are expiring will begin to be elected by qualified electors of the District. A “qualified elector” in this instance is any person at least eighteen (18) years of age who is a citizen of the United States, a legal resident of Florida and of the District, and who is also registered with the Supervisor of Elections to vote in Lee County. Notwithstanding the foregoing, if at any time the Board proposes to exercise its ad valorem taxing power, it shall, prior to the exercise of such power, call an election at which all members of the Board shall be elected by qualified electors of the District.\n\nBoard meetings are noticed in a local newspaper and conducted in a public forum in which public participation is permitted. Consistent with Florida’s public records laws, the records of the District are available for public inspection during normal business hours. Elected members of the Board are similarly bound by the State’s open meetings law and are generally subject to the same disclosure requirements as other elected officials under the State’s ethics laws.\n\nWhat infrastructure improvements does the District provide and how are the improvements paid for?\n\nThe District is comprised of approximately 2,352.08 acres located entirely within Lee County, Florida. The legal description of the lands encompassed within the District is attached hereto as Exhibit A. The public infrastructure necessary to support the District’s development program includes, but is not limited to: drainage and surface water management systems, onsite roadways, onsite utilities, offsite utility and roadway improvements, and environmental restoration and mitigation. These infrastructure improvements are more fully detailed below.\n\nTo plan the infrastructure improvements necessary for the District, the District adopted a Master Engineer’s Report dated March 7, 2019, which details all of the improvements contemplated for the completion of the infrastructure of the District (the “Capital Improvement Plan”). Copies of the Capital Improvement Plan are available for review at the District’s office.\n\nThese public infrastructure improvements have been or will be funded by the District’s sale of bonds. On April 2, 2018, the Circuit Court of the State of Florida, in and for Lee County, Florida, entered a Final Judgment validating the District’s ability to issue an aggregate principal amount not to exceed $46,760,000 in Special Assessment Bonds for the funding of the Capital Improvement Plan.\n\nOn June 12, 2019, the District issued a series of special assessment bonds for the purposes of financing a portion of the costs of the construction and acquisition of the Capital Improvement Plan. On that date, the District issued its WildBlue Community Development District Special Assessment Bonds, Series 2019, in the amount of $23,470,000 (the “Series 2019 Bonds”).\n\nDrainage Surface Water Management System\n\nA total of approximately 181 acres of wet detention lakes is proposed to be constructed within the District. The surface water management lakes will be excavated to size and depth requirements of the South Florida Water Management District (“SFWMD”). The water management system will consist of excavated surface water lakes, culverts, inlets and stormwater control structures, and consists of eight (8) separate basins, each directing runoff to specified lakes for treatment and attenuation prior to discharge. Treated stormwater will subsequently be released through various control structures located in each wet detention lake, discharging into preserve area and the adjacent slough systems. Existing lakes, WildBlue Lake North and WildBlue Lake South, will serve dual purposes as recreation and water management lakes, accepting discharge exiting the Stewart Cypress Slough during a 100-year rain event. The benefit of these discharge points is two-fold: they provide a positive outfall for the wet detention lakes, as well as hydration to the preserve areas. The surface water management system has been designed in accordance with SFWMD regulations that set minimum criteria for water quality treatment and flood protection. The surface water management areas are designated to attenuate the 25-year, 3-day rainfall event. A sediment and erosion control plan will be prepared and implemented for the entirety of the project.\n\nOn-Site Roadways\n\nDistrict funded on-site roadways will consist of public roadways located from Corkscrew Road to the guardhouse and from Alico Road to the guardhouse. All roadways within the guardhouses will be privately funded, operated and maintained. Construction of the public roadways will consist of stabilized subgrade, limerock, asphalt (initial lift and final lift), signing and striping. Roadways are designed in accordance with Florida Department of Transportation (“FDOT”) and Lee County requirements, and will include security features, landscaping, irrigation, master electrical, street lighting and sidewalks. Landscaping and irrigation, perimeter berms and entrance features will be owned and maintained by the District. Existing native vegetation will be preserved and incorporated into the landscape plan where possible, and will consist of sod, annual flowers, shrubs, groundcover, littoral plants and trees. A total of approximately 4,860 linear feet of public roadway will be constructed and maintained by the District.\n\nOn-Site Utilities\n\nDistrict funded utilities will consist of water, wastewater and irrigation systems. These systems will be designed and constructed in accordance with Lee County Utilities (“LCU”), Florida Department of Environmental Protection (“FDEP”) and Lee County Department of Health (“LCDOH”) standards, as applicable. The turnover of completed water and sanitary sewer utilities by the District to LCU will take place upon completion of construction of these facilities. LCU will also act as the supplier of water to the water distribution systems, as well as the collector of the wastewater from the wastewater collection system. On-site potable water facilities will include transmission and distribution lines, along with the necessary valves, fire hydrants and water services to individual buildings and parcels. It is currently estimated to include approximately 62,000 linear feet of watermain will be constructed. On-site wastewater facilities will include individual sewer services, force mains and six (6) sanitary lift stations. Four (4) lift stations will serve northern portions of the District and two (2) will serve the southern portion of the District. One (1) left station in each general location will serve as the master lift station, to which the others will discharge sewage. Each master lift station will pump to offsite LCU infrastructure. The project is anticipated to require approximately 36,000 linear feet of gravity and sanitary sewer, approximately 20,000 linear feet of force main and six (6) lift stations. On-site irrigation facilities will include distribution lines, along with necessary appurtenances, and is estimated to require approximately 47,000 linear feet of irrigation main and two (2) pump stations. The District will own, operate and maintain the irrigation system.\n\nOffsite Utility and Roadway Improvements\n\nOffsite utility improvements include sanitary sewer transmission mains within the Lee County Alico Road and Corkscrew Road rights-of-way to serve the development and improve the current LCU system. Offsite roadway improvements include construction of auxiliary lanes to manage increased traffic flows and enhance safety. Auxiliary lanes serving the District are proposed to be added at the entrances and exits on Corkscrew Road and Alico Road. Included as part of the offsite roadway improvements, landscaping and irrigation adjacent to offsite roadways, but within the District boundary, will be owned and maintained by the District.\n\nOwnership and maintenance of all offsite improvements, with the exception of District-owned and maintained landscape and irrigation, will be conveyed to Lee County upon completion and certification, as applicable.\n\n**Environmental Restoration and Mitigation**\n\nEnvironmental consideration influenced the design of the project to reduce or eliminate direct and secondary impacts, as well as preserve and restore the hydrologic ecological integrity to the greatest extent possible with the design parameters. Restoration and mitigation efforts will also satisfy SFWMD, U.S. Army Corps of Engineers (“ACOE”) and Lee County zoning requirements and specifications. Proposed preservation and restoration activities are anticipated to provide a net benefit to water quality and as such, enhance aquatic vegetation and wildlife habitat. These restoration activities will also reestablish and revitalize wetland flow ways. A wetland mitigation plan has also been devised to enhance wetland functions. Based on a Uniform Mitigation Assessment Methodology Analysis performed on the site, the functional loss associated with development impacts is significantly exceeded by the increased wetland functionality resulting from implementation of the proposed on-site mitigation plan.\n\n**Assessments, Fees and Charges**\n\nThe costs of acquisition or construction of a portion of these infrastructure improvements have been financed by the District through the sale of the Series 2019 Bonds. The annual debt service payments, including interest due thereon, are payable solely from and secured by the levy of non-ad valorem or special assessments against lands within the District which benefit from the construction, acquisition, establishment and operation of the District’s improvements. The annual debt service obligations of the District which must be defrayed by annual assessments upon each parcel of land or platted lot will depend upon the type of property purchased. The current maximum annual debt service assessment levels for property within the District for the Series 2019 Bonds (the “Series 2019 Debt Service Assessments”) may be obtained from the District Manager. Interested persons are encouraged to contact the District Manager for information regarding special assessments on a particular lot or parcel of lands. A copy of the District’s assessment methodology and assessment roll are available for review at the District’s office.\n\nThe Series 2019 Debt Service Assessments exclude any operations and maintenance assessments (“O&M Assessments”) which may be determined and calculated annually by the District’s Board of Supervisors and are levied against benefitted lands in the District.\n\nA detailed description of all costs and allocations which result in the formulation of the Series 2019 Debt Service Assessments and the O&M Assessments is available for public inspection upon request.\n\nThe Capital Improvement Plan and financing plan of the District infrastructure as presented herein reflect the District’s current intentions, and the District expressly reserves the right in its sole discretion to change those plans at any time. Additionally, the District may undertake the construction, reconstruction, acquisition, or installation of future improvements\n\nand facilities, which may be financed by bonds, notes, or other methods authorized by Chapter 190, Florida Statutes.\n\n**Method of Collection**\n\nThe District’s Series 2019 Debt Service Assessments and/or O&M Assessments may appear on that portion of the annual real estate tax notice entitled “non-ad valorem assessments,” and to the extent that it is, will be collected by the Lee County Tax Collector in the same manner as county ad valorem taxes. Each property owner must pay both ad valorem and non-ad valorem assessments at the same time. Property owners will, however, be entitled to the same discounts as provided for ad valorem taxes. As with any tax notice, if all taxes and assessments due are not paid within the prescribed time limit, the tax collector is required to sell tax certificates which, if not timely redeemed, may result in the loss of title to the property. The District may also elect to collect the assessment directly.\n\nThis description of the District’s operation, services and financing structure is intended to provide assistance to landowners and purchasers concerning the important role that the District plays in providing infrastructure improvements essential to the use and development of this community. If you have any questions or would simply like additional information about the District, please write to the District Manager at: WildBlue Community Development District, 2300 Glades Road, Suite 410W, Boca Raton, Florida 33431 or call (561) 571-0010.\n\nThe information provided herein is a good faith effort to accurately and fully disclose information regarding the public financing and maintenance of improvements to real property undertaken by the District and should only be relied upon as such. The information contained herein is, and can only be, a status summary of the District’s public financing and maintenance activities and is subject to supplementation and clarification from the actual documents and other sources from which this information is derived. In addition, the information contained herein may be subject to change over time, in the due course of the District’s activities and in accordance with Florida law. Prospective and current residents and other members of the public should seek confirmation and/or additional information from the District Manager’s office with regard to any questions or points of interest raised by the information presented herein.\n\nIN WITNESS WHEREOF, this Disclosure of Public Financing and Maintenance of Improvements to Real Property Undertaken has been executed as of the ______ day of ________________, 2019, and recorded in the Official Records of Lee County, Florida.\n\nWILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\nBy: Russell Smith, Chairman\n\nWitness\n\nPrint Name\n\nSTATE OF FLORIDA\nCOUNTY OF ____________\n\nThe foregoing instrument was acknowledged before me this ______ day of ________________, 2019, by Russell Smith, Chairman of the WildBlue Community Development District, who is personally known to me or who has produced ________________________ as identification, and did [ ] or did not [ ] take the oath.\n\nNotary Public, State of Florida\n\nPrint Name:\nCommission No.:\nMy Commission Expires:\n\nDESCRIPTION\n\nParcel in\nSections 7, 8, 17, 18, 19 and 20, Township 46 South, Range 26 East,\nLee County, Florida\n\nA tract or parcel of land lying in Sections 7, 8, 17, 18, 19 and 20, Township 46 South, Range 26 East, Lee County, Florida, said tract or parcel of land being more particularly described as follows:\n\nBeginning at the East Quarter corner of said Section 8 run S01°05'07\"E along the East line of the Southeast Quarter (SE 1/4) of said Section 8 for 1,329.41 feet to an intersection with the Northerly line of a Conservation Easement, Mitigation Area I, as described in a deed recorded in Instrument No. 2017000016507, Lee County Records; thence run along the Northerly and Westerly line of said Conservation Easement, Mitigation Area I, the following Thirty-nine (39) courses: N89°50'10\"W for 195.70 feet; S66°37'31\"E for 49.62 feet; S83°38'09\"E for 22.96 feet; S48°29'06\"E for 13.24 feet; S48°08'34\"E for 24.32 feet; S34°26'57\"E for 33.44 feet; S17°41'48\"E for 41.05 feet; S13°06'47\"E for 78.87 feet; S07°40'58\"E for 36.50 feet; S01°24'58\"W for 131.72 feet; S04°00'44\"W for 273.74 feet; S20°33'55\"W for 25.70 feet; S18°26'36\"W for 28.54 feet; S07°41'59\"W for 28.08 feet; S03°16'19\"E for 26.36 feet; S09°14'04\"E for 60.95 feet; S01°04'53\"E for 39.86 feet; S10°05'08\"W for 68.74 feet; S26°31'25\"W for 45.80 feet; S52°26'42\"W for 37.01 feet; S75°43'32\"W for 85.39 feet; S78°28'46\"W for 265.05 feet; S72°50'46\"W for 53.54 feet; S52°30'34\"W for 40.77 feet; S36°53'00\"W for 45.13 feet; S14°52'58\"W for 49.80 feet; S08°15'23\"W for 178.87 feet; S05°03'55\"W for 281.19 feet; S09°22'36\"W for 153.74 feet to a point on a non-tangent curve; Southeasterly along an arc of a curve to the right of radius 455.02 feet (delta 33°42'17\") (chord bearing S22°57'46\"E) (chord 263.83 feet) for 267.67 feet to a point of tangency; S06°06'37'E for 149.55 feet to a point of curvature; Southerly along an arc of a curve to the left of radius 720.04 feet (delta 13°54'51\") (chord bearing S13°04'05\"E) (chord 174.43 feet) for 174.86 feet to a point of tangency; S20°01'29\"E for 389.67 feet to a point on a non-tangent curve; Southerly along an arc of a curve to the right of radius 455.02 feet (delta 17°17'31\") (chord bearing S11°22'43\"E) (chord 136.81 feet) for 137.33 feet; S02°45'17\"E along a non-tangent line for 132.64 feet to a point of curvature; Southerly along an arc of a curve to the left of radius 345.02 feet (delta 21°30'26\") (chord bearing S15°30'30\"E) (chord 128.75 feet) for 129.51 feet to a point of reverse curvature; Southerly along an arc of a curve to the right of radius 85.00 feet (delta 29°24'23\") (chord bearing S09°33'31\"E) (chord 43.15 feet) for 43.63 feet; S03°42'13\"E along a non-tangent line for 182.20 feet and S11°59'27\"W for 523.10 feet; thence run N88°00'00\"W for 104.87 feet; thence run N01°17'04\"E for 327.99 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 125.00 feet (delta 28°25'07\") (chord bearing N12°55'29\"W) (chord 61.37 feet) for 62.00 feet to a point of tangency; thence run N27°08'03\"W for 227.36 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 175.00 feet (delta 31°05'54\") (chord bearing N11°35'06\"W) (chord 93.82 feet) for 94.98 feet to a point of tangency; thence run N03°57'51\"E for 117.42 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 125.00 feet (delta 23°50'58\") (chord bearing N07°57'39\"W) (chord 51.66 feet) for 52.03 feet to a point of tangency; thence run N19°53'08\"W for 455.82 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 675.00 feet (delta 09°49'13\") (chord bearing N14°58'31\"W) (chord 115.55 feet) for 115.69 feet to a point of tangency; thence run N10°03'55\"W for 444.30 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the left of radius 75.00 feet (delta 76°13'50\") (chord bearing N48°10'50\"W) (chord 92.59 feet) for 99.79 feet to a point of tangency; thence run\n\nDESCRIPTION (CONTINUED)\n\nN86°17'44\"W for 107.75 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the right of radius 25.00 feet (delta 74°32'44\") (chord bearing N49°01'22\"W) (chord 30.28 feet) for 32.53 feet to a point of reverse curvature; thence run Northwesterly along an arc of a curve to the left of radius 75.00 feet (delta 74°04'54\") (chord bearing N48°47'27\"W) (chord 90.36 feet) for 96.97 feet to a point of tangency; thence run N85°49'54\"W for 703.33 feet; thence run S87°15'28\"W for 133.97 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the right of radius 25.00 feet (delta 110°21'05\") (chord bearing N37°33'59\"W) (chord 41.05 feet) for 48.15 feet to a point of tangency; thence run N17°36'33\"E for 31.78 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 225.00 feet (delta 16°16'07\") (chord bearing N09°28'30\"E) (chord 63.67 feet) for 63.89 feet to a point of tangency; thence run N01°20'26\"E for 281.53 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the left of radius 75.00 feet (delta 87°55'32\") (chord bearing N42°37'20\"W) (chord 104.13 feet) for 115.09 feet to a point of tangency; thence run N86°35'06\"W for 782.57 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the right of radius 25.00 feet (delta 85°47'00\") (chord bearing N43°41'36\"W) (chord 34.03 feet) for 37.43 feet to a point of tangency; thence run N00°48'06\"W for 462.06 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 25.00 feet (delta 91°17'38\") (chord bearing N44°50'43\"E) (chord 35.75 feet) for 39.83 feet to a point of tangency; thence run S89°30'28\"E for 143.88 feet; thence run N88°41'11\"E for 66.04 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 55.00 feet (delta 84°54'26\") (chord bearing N46°13'58\"E) (chord 74.25 feet) for 81.51 feet to a point of tangency; thence run N03°46'44\"E for 115.28 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 1,025.00 feet (delta 06°22'00\") (chord bearing N00°35'45\"E) (chord 113.84 feet) for 113.90 feet to a point of tangency; thence run N02°35'16\"W for 145.50 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 125.00 feet (delta 35°11'54\") (chord bearing N20°11'12\"W) (chord 75.59 feet) for 76.79 feet to a point of tangency; thence run N37°47'09\"W for 140.60 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the left of radius 75.00 feet (delta 48°24'27\") (chord bearing N61°59'23\"W) (chord 61.50 feet) for 63.37 feet to a point of tangency; thence run N86°11'36\"W for 343.76 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the right of radius 25.00 feet (delta 40°44'26\") (chord bearing N65°49'23\"W) (chord 17.40 feet) for 17.78 feet to a point of reverse curvature; thence run Northwesterly along an arc of a curve to the left of radius 75.00 feet (delta 39°03'54\") (chord bearing N64°59'07\"W) (chord 50.15 feet) for 51.14 feet to a point of tangency; thence run N84°31'04\"W for 264.21 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 75.00 feet (delta 66°43'13\") (chord bearing S62°07'19\"W) (chord 82.48 feet) for 87.34 feet to a point of tangency; thence run S28°45'43\"W for 143.26 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 175.00 feet (delta 30°44'54\") (chord bearing S44°08'10\"W) (chord 92.79 feet) for 93.92 feet to a point of tangency; thence run S59°30'38\"W for 133.65 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 125.00 feet (delta 40°20'35\") (chord bearing S39°20'20\"W) (chord 86.21 feet) for 88.02 feet to a point of tangency; thence run S10°10'02\"W for 2.70 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the left of radius 75.00 feet (delta 110°16'00\") (chord bearing S35°57'58\"E) (chord 123.07 feet) for 144.34 feet to a point of reverse curvature; thence run Southeasterly along an arc of a curve to the right of radius 15.00 feet (delta 86°56'34\") (chord bearing S47°37'40\"E) (chord 20.64 feet) for 22.76 feet to a point of tangency; thence run S04°09'23\"E for 65.44 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the left of radius 55.00 feet (delta\n\nDESCRIPTION (CONTINUED)\n\n$81^\\circ 50'30''$ (chord bearing $S45^\\circ 04'38''E$) (chord 72.05 feet) for 78.56 feet to a point of reverse curvature; thence run Southeasterly along an arc of a curve to the right of radius 25.00 feet (delta $94^\\circ 47'54''$) (chord bearing $S38^\\circ 35'56''E$) (chord 36.80 feet) for 41.36 feet to a point of reverse curvature; thence run Southerly along an arc of a curve to the left of radius 2,025.00 feet (delta $04^\\circ 45'08''$) (chord bearing $S06^\\circ 25'26''W$) (chord 167.91 feet) for 167.96 feet to a point of tangency; thence run $S04^\\circ 02'52''W$ for 83.35 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 25.00 feet (delta $80^\\circ 29'14''$) (chord bearing $S44^\\circ 17'29''W$) (chord 32.30 feet) for 35.12 feet to a point of tangency; thence run $S84^\\circ 32'06''W$ for 43.22 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the right of radius 25.00 feet (delta $79^\\circ 30'00''$) (chord bearing $N55^\\circ 42'54''W$) (chord 31.97 feet) for 34.69 feet to a point of reverse curvature; thence run Northwesterly along an arc of a curve to the left of radius 105.00 feet (delta $75^\\circ 14'50''$) (chord bearing $N53^\\circ 35'19''W$) (chord 128.20 feet) for 137.90 feet to a point of tangency; thence run $S88^\\circ 47'16''W$ for 62.79 feet to a point of curvature; thence run Westerly along an arc of a curve to the right of radius 9,975.00 feet (delta $04^\\circ 35'00''$) (chord bearing $N88^\\circ 55'14''W$) (chord 797.75 feet) for 797.96 feet to a point of tangency; thence run $N86^\\circ 37'44''W$ for 38.69 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 105.00 feet (delta $62^\\circ 46'57''$) (chord bearing $S61^\\circ 58'48''W$) (chord 109.38 feet) for 115.06 feet t to a point of reverse curvature; thence run Southwesterly along an arc of a curve to the right of radius 55.00 feet (delta $59^\\circ 24'41''$) (chord bearing $S60^\\circ 17'40''W$) (chord 54.51 feet) for 57.03 feet to a point of tangency; thence run $N90^\\circ 00'00''W$ for 238.27 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 85.00 feet (delta $70^\\circ 22'36''$) (chord bearing $S54^\\circ 48'42''W$) (chord 97.97 feet) for 104.41 feet to a point of tangency; thence run $S19^\\circ 37'24''W$ for 311.22 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 975.00 feet (delta $14^\\circ 30'43''$) (chord bearing $S26^\\circ 52'45''W$) (chord 246.29 feet) for 246.95 feet to a point of tangency; thence run $S34^\\circ 08'07''W$ for 337.12 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 975.00 feet (delta $19^\\circ 37'52''$) (chord bearing $S43^\\circ 57'03''W$) (chord 332.43 feet) for 334.06 feet to a point of tangency; thence run $S53^\\circ 45'59''W$ for 1,244.08 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 525.00 feet (delta $38^\\circ 16'07''$) (chord bearing $S34^\\circ 37'56''W$) (chord 344.17 feet) for 350.65 feet to a point of tangency; thence run $S15^\\circ 29'52''W$ for 405.98 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 25.00 feet (delta $83^\\circ 55'54''$) (chord bearing $S57^\\circ 27'49''W$) (chord 33.43 feet) for 36.62 feet to a point of tangency; thence run $N86^\\circ 34'14''W$ for 34.34 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 55.00 feet (delta $81^\\circ 39'24''$) (chord bearing $S58^\\circ 36'04''W$) (chord 71.92 feet) for 78.38 feet to a point of tangency; thence run $S17^\\circ 46'23''W$ for 90.68 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the left of radius 100.00 feet (delta $81^\\circ 42'16''$) (chord bearing $S23^\\circ 04'45''E$) (chord 130.82 feet) for 142.60 feet to a point of tangency; thence run $S63^\\circ 55'53''E$ for 880.47 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 100.00 feet (delta $10^\\circ 42'04''$) (chord bearing $S73^\\circ 46'55''E$) (chord 34.22 feet) for 34.38 feet to a point of reverse curvature; thence run Southeasterly along an arc of a curve to the right of radius 275.00 feet (delta $43^\\circ 39'00''$) (chord bearing $S61^\\circ 48'27''E$) (chord 204.47 feet) for 209.50 feet to a point of tangency; thence run $S39^\\circ 58'57''E$ for 16.19 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 75.00 feet (delta $31^\\circ 02'23''$) (chord bearing $S24^\\circ 27'46''E$) (chord 40.14 feet) for 40.63 feet to a point of compound curvature; thence run Southerly along an arc of a curve to the right of radius 175.00 feet (delta $37^\\circ 44'43''$) (chord bearing $S09^\\circ 55'48''W$) (chord 113.21 feet) for 115.29 feet to a point of tangency; thence run $S28^\\circ 48'09''W$ for 43.26\n\nDESCRIPTION (CONTINUED)\n\nfeet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 225.00 feet (delta 26°23'45\") (chord bearing S42°00'02\"W) (chord 102.74 feet) for 103.66 feet to a point of tangency; thence run S55°11'54\"W for 52.99 feet to a point of curvature; thence run Westerly along an arc of a curve to the right of radius 475.00 feet (delta 81°20'53\") (chord bearing N84°07'39\"W) (chord 619.17 feet) for 674.40 feet to a point of tangency; thence run N43°27'13\"W for 184.25 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the left of radius 325.00 feet (delta 26°39'57\") (chord bearing N56°47'11\"W) (chord 149.90 feet) for 151.26 feet to a point of tangency; thence run N70°07'10\"W for 82.71 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 55.00 feet (delta 89°25'20\") (chord bearing S65°10'10\"W) (chord 77.39 feet) for 85.84 feet to a point of tangency; thence run S20°27'30\"W for 149.12 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 35.00 feet (delta 78°58'38\") (chord bearing S59°56'49\"W) (chord 44.51 feet) for 48.24 feet to a point of tangency; thence run N80°33'52\"W for 76.95 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 55.00 feet (delta 73°28'14\") (chord bearing S62°42'01\"W) (chord 65.79 feet) for 70.53 feet to a point of tangency; thence run S25°57'54\"W for 719.51 feet to a point of curvature; thence run Westerly along an arc of a curve to the right of radius 35.00 feet (delta 89°05'54\") (chord bearing S70°30'51\"W) (chord 49.11 feet) for 54.43 feet to a point of reverse curvature; thence run Westerly along an arc of a curve to the left of radius 45.00 feet (delta 77°53'32\") (chord bearing S76°07'02\"W) (chord 56.57 feet) for 61.18 feet to a point of tangency; thence run S37°10'16\"W for 317.27 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 35.00 feet (delta 55°50'05\") (chord bearing S65°05'19\"W) (chord 32.77 feet) for 34.11 feet to a point of reverse curvature; thence run Southwesterly along an arc of a curve to the left of radius 75.00 feet (delta 51°38'09\") (chord bearing S67°11'17\"W) (chord 65.33 feet) for 67.59 feet to a point of tangency; thence run S41°22'13\"W for 463.38 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 125.00 feet (delta 38°33'50\") (chord bearing S22°05'17\"W) (chord 82.55 feet) for 84.13 feet to a point of tangency; thence run S02°48'22\"W for 115.05 feet to a point of curvature; thence run Southeastery along an arc of a curve to the left of radius 40.00 feet (delta 89°43'03\") (chord bearing S42°03'09\"E) (chord 56.43 feet) for 62.63 feet to a point of tangency; thence run S86°54'41\"E for 300.04 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 115.00 feet (delta 47°56'53\") (chord bearing N69°06'53\"E) (chord 93.45 feet) for 96.24 feet to a point of reverse curvature; thence run Easterly along an arc of a curve to the right of radius 50.00 feet (delta 53°36'02\") (chord bearing N71°56'27\"E) (chord 45.09 feet) for 46.78 feet to a point of tangency; thence run S81°15'32\"E for 538.83 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 2,025.00 feet (delta 04°08'08\") (chord bearing S83°19'36\"E) (chord 146.14 feet) for 146.17 feet to a point of tangency; thence run S85°23'41\"E for 296.12 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 175.00 feet (delta 17°19'21\") (chord bearing N85°56'39\"E) (chord 52.71 feet) for 52.91 feet to a point of reverse curvature; thence run Easterly along an arc of a curve to the right of radius 225.00 feet (delta 19°32'48\") (chord bearing N87°03'23\"E) (chord 76.39 feet) for 76.76 feet to a point of tangency; thence run S83°10'13\"E for 512.33 feet to a point of curvature; thence run Easterly along an arc of a curve to the right of radius 1,475.00 feet (delta 05°45'32\") (chord bearing S80°17'28\"E) (chord 148.19 feet) for 148.25 feet to a point of tangency; thence run S77°24'42\"E for 220.11 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 125.00 feet (delta 23°59'07\") (chord bearing S89°24'15\"E) (chord 51.95 feet) for 52.33 feet to a point of reverse curvature; thence run Easterly along an arc of a curve to the right of radius 125.00 feet (delta 24°18'51\") (chord\n\nbearing S89°14'23\"E (chord 52.65 feet) for 53.04 feet to a point of tangency; thence run S77°04'58\"E for 182.20 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 375.00 feet (delta 21°55'47\") (chord bearing S88°02'52\"E) (chord 142.66 feet) for 143.53 feet to a point of reverse curvature; thence run Easterly along an arc of a curve to the right of radius 325.00 feet (delta 15°53'40\") (chord bearing N88°56'05\"E) (chord 89.87 feet) for 90.16 feet to a point of tangency; thence run S83°07'05\"E for 525.38 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 67.00 feet (delta 128°31'46\") (chord bearing N32°37'02\"E) (chord 120.71 feet) for 150.30 feet to a point of tangency; thence run N31°38'51\"W for 54.90 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the right of radius 975.00 feet (delta 15°05'48\") (chord bearing N24°05'57\"W) (chord 256.16 feet) for 256.90 feet to a point of tangency; thence run N16°33'03\"W for 273.87 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 75.00 feet (delta 53°50'18\") (chord bearing N10°22'06\"E) (chord 67.91 feet) for 70.47 feet to a point of tangency; thence run N37°17'15\"E for 385.52 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 75.00 feet (delta 26°05'30\") (chord bearing N50°20'00\"E) (chord 33.86 feet) for 34.15 feet to a point of tangency; thence run N63°22'45\"E for 95.98 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 95.00 feet (delta 59°20'24\") (chord bearing N33°42'32\"E) (chord 94.05 feet) for 98.39 feet to a point of tangency; thence run No4°02'20\"E for 17.62 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 825.00 feet (delta 09°37'11\") (chord bearing No0°46'15\"W) (chord 138.35 feet) for 138.51 feet to a point of tangency; thence run No5°34'51\"W for 96.94 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 1,025.00 feet (delta 08°31'33\") (chord bearing No9°50'37\"W) (chord 152.38 feet) for 152.52 feet to a point of tangency; thence run N14°06'23\"W for 137.47 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 75.00 feet (delta 29°57'54\") (chord bearing No0°52'34\"E) (chord 38.78 feet) for 39.22 feet to a point of tangency; thence run N15°51'31\"E for 540.62 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 75.00 feet (delta 80°17'48\") (chord bearing N56°00'24\"E) (chord 96.72 feet) for 105.11 feet to a point of tangency; thence run S83°50'42\"E for 516.23 feet to a point of curvature; thence run Easterly along an arc of a curve to the right of radius 775.00 feet (delta 23°20'01\") (chord bearing S72°10'41\"E) (chord 313.44 feet) for 315.62 feet to a point of tangency; thence run S60°30'41\"E for 250.77 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 175.00 feet (delta 54°45'50\") (chord bearing S33°07'46\"E) (chord 160.97 feet) for 167.27 feet to a point of tangency; thence run So5°44'51\"E for 315.52 feet to a point of curvature; thence run Southerly along an arc of a curve to the right of radius 125.00 feet (delta 31°40'54\") (chord bearing S10°05'36\"W) (chord 68.24 feet) for 69.12 feet to a point of tangency; thence run S25°56'03\"W for 194.92 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 1,025.00 feet (delta 08°19'04\") (chord bearing S21°46'31\"W) (chord 148.67 feet) for 148.80 feet to a point of tangency; thence run S17°36'59\"W for 19.12 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 75.00 feet (delta 43°12'25\") (chord bearing S39°13'12\"W) (chord 55.23 feet) for 56.56 feet to a point of tangency; thence run S60°49'24\"W for 511.56 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 55.00 feet (delta 100°29'06\") (chord bearing S10°34'51\"W) (chord 84.56 feet) for 96.46 feet to a point of tangency; thence run S39°39'41\"E for 191.03 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 55.00 feet (delta 64°09'20\") (chord bearing S71°44'21\"E) (chord 58.42 feet) for 61.58 feet to a point of tangency; thence run N76°10'58\"E for 103.98 feet; thence run S22°06'17\"W for 384.89 feet to\n\nDESCRIPTION (CONTINUED)\n\na point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 175.00 feet (delta 25°20'50\") (chord bearing S34°46'42\"W) (chord 76.79 feet) for 77.42 feet to a point of tangency; thence run S47°27'07\"W for 160.73 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 1,525.00 feet (delta 10°29'23\") (chord bearing S42°12'25\"W) (chord 278.81 feet) for 279.20 feet to a point of tangency; thence run S36°57'44\"W for 225.13 feet; thence run S59°57'40\"E for 651.72 feet; thence run S62°28'13\"E for 513.06 feet; thence run S84°09'06\"E for 109.77 feet to the Westerly most corner of a Conservation Easement, Mitigation Area J-5, as described in a deed recorded in Instrument No. 2017000016508, Lee County Records; thence run S72°20'38\"W for 199.78 feet to the Northerly most corner of a Conservation Easement, Mitigation Area J-4, as described in a deed recorded in Instrument No. 2017000016508, Lee County Records; thence run N59°00'09\"W for 220.11 feet; thence run N60°18'15\"W for 1,043.19 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 55.00 feet (delta 107°14'59\") (chord bearing S66°04'15\"W) (chord 88.57 feet) for 102.95 feet to a point of tangency; thence run S12°26'46\"W for 331.68 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 45.00 feet (delta 59°51'09\") (chord bearing S42°22'21\"W) (chord 44.90 feet) for 47.01 to a point of reverse curvature; thence run Southwesterly along an arc of a curve to the left of radius 55.00 feet (delta 53°17'32\") (chord bearing S45°39'09\"W) (chord 49.33 feet) for 51.16 feet to a point of tangency; thence run S10°00'23\"W for 41.52 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 605.00 feet (delta 05°26'26\") (chord bearing S16°17'10\"W) (chord 57.43 feet) for 57.45 feet; thence run N88°58'18\"W along a non-tangent line for 20.47 feet to a point on a non-tangent curve; thence run Southerly along an arc of a curve to the left of radius 625.00 feet (delta 13°24'44\") (chord bearing S06°27'09\"W) (chord 145.97 feet) for 146.31 feet to a point of tangency; thence run S00°15'14\"E for 248.25 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 125.00 feet (delta 32°46'30\") (chord bearing S16°38'28\"E) (chord 70.53 feet) for 71.50 feet to a point of tangency; thence run S33°01'43\"E for 116.53 feet to a point of curvature; thence run Southerly along an arc of a curve to the right of radius 75.00 feet (delta 37°11'42\") (chord bearing S14°25'52\"E) (chord 47.84 feet) for 48.69 feet to a point of tangency; thence run S04°09'59\"W for 95.83 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 825.00 feet (delta 14°12'12\") (chord bearing S02°56'07\"E) (chord 203.99 feet) for 204.51 feet to a point of tangency; thence run S10°02'13\"E for 639.07 feet to a point of curvature; thence run Southerly along an arc of a curve to the right of radius 1,475.00 feet (delta 09°48'35\") (chord bearing S05°07'55\"E) (chord 252.23 feet) for 252.54 feet to a point of tangency; thence run S00°13'37\"E for 330.01 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 5.00 feet (delta 89°47'59\") (chord bearing S44°40'22\"W) (chord 7.06 feet) for 7.84 feet to a point of tangency; thence run S89°34'22\"W for 177.62 feet to a point of curvature; thence run Westerly along an arc of a curve to the left of radius 1,525.00 feet (delta 06°47'39\") (chord bearing S86°10'32\"W) (chord 180.73 feet) for 180.83 feet to a point of tangency; thence run S82°46'43\"W for 328.63 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 175.00 feet (delta 104°09'44\") (chord bearing S30°41'51\"W) (chord 276.11 feet) for 318.15 feet to a point of tangency; thence run S21°23'01\"E for 360.35 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the left of radius 1,525.00 feet (delta 06°00'16\") (chord bearing S24°23'09\"E) (chord 159.74 feet) for 159.82 feet to a point of tangency; thence run S27°23'17'E for 421.97 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the left of radius 105.00 feet (delta 65°32'07\") (chord bearing S60°09'21\"E) (chord 113.66 feet) for 120.10 feet to a point of tangency; thence run N87°04'36\"E for 460.68 feet to a point of curvature; thence run\n\nDESCRIPTION (CONTINUED)\n\nEasterly along an arc of a curve to the left of radius 1,525.00 feet (delta 05°19'50\") (chord bearing N84°24'41\"E) (chord 141.83 feet) for 141.88 feet to a point of tangency; thence run N81°44'46\"E for 504.82 feet; thence run S00°00'00\"W for 36.63 feet to an intersection with the Northerly line of a Conservation Easement, Mitigation Area J-4, as described in a deed recorded in Instrument No. 2017000016508, Lee County Records; thence run along the Northerly and Westerly line of said Conservation Easement, Mitigation Area J-4, the following Fifty-one (51) course: S46°03'15\"W for 16.27 feet to a point on a non-tangent curve; thence run Southerly along an arc of a curve to the left of radius 80.90 feet (delta 52°50'29\") (chord bearing S08°53'23\"W) (chord 72.00 feet) for 74.61 feet; S02°55'07'E along a non-tangent line for 102.47 feet to a point on a non-tangent curve; Southerly along an arc of a curve to the right of radius 75.00 feet (delta 77°33'35\") (chord bearing S02°39'53\"E) (chord 93.95 feet) for 101.53 feet; S03°08'31\"E along a non-tangent line for 104.95 feet to a point on a non-tangent curve; Southwesterly along an arc of a curve to the right of radius 50.76 feet (delta 93°09'07\") (chord bearing S41°28'44\"W) (chord 73.73 feet) for 82.52 feet; S85°47'25\"W along a non-tangent line for 6.49 feet; S86°58'15\"W for 43.64 feet to a point on a non-tangent curve; Southerly along an arc of a curve to the right of radius 85.21 feet (delta 39°41'56\") (chord bearing S14°36'12\"E) (chord 57.87 feet) for 59.04 feet to a point on a non-tangent curve; Southwesterly along an arc of a curve to the right of radius 112.81 feet (delta 88°31'59\") (chord bearing S49°03'14\"W) (chord 157.48 feet) for 174.31 feet to a point of tangency; N86°40'46\"W for 37.88 feet to a point on a non-tangent curve; Westerly along an arc of a curve to the left of radius 384.67 feet (delta 04°25'40\") (chord bearing N88°23'26\"W) (chord 29.72 feet) for 29.73 feet to a point on a non-tangent curve; Westerly along an arc of a curve to the left of radius 467.46 feet (delta 14°35'09\") (chord bearing S85°08'57\"W) (chord 118.68 feet) for 119.00 feet to a point on a non-tangent curve; Westerly along an arc of a curve to the left of radius 527.77 feet (delta 07°26'29\") (chord bearing S73°23'57\"W) (chord 68.50 feet) for 68.55 feet to a point on a non-tangent curve; Westerly along an arc of a curve to the right of radius 1,303.55 feet (delta 05°34'29\") (chord bearing S71°24'02\"W) (chord 126.78 feet) for 126.83 feet to a point on a non-tangent curve; Westerly along an arc of a curve to the right of radius 157.51 feet (delta 19°00'00\") (chord bearing S80°11'21\"W) (chord 51.99 feet) for 52.23 feet to a point on a non-tangent curve; Westerly along an arc of a curve to the left of radius 8,453.34 feet (delta 06°37'21\") (chord bearing S83°13'56\"W) (chord 91.83 feet) for 91.83 feet to a point of reverse curvature; Westerly along an arc of a curve to the right of radius 1,196.95 feet (delta 11°08'03\") (chord bearing S88°29'17\"W) (chord 232.23 feet) for 232.60 feet to a point of compound curvature; Westerly along an arc of a curve to the right of radius 704.33 feet (delta 20°08'59\") (chord bearing N75°52'12\"W) (chord 246.43 feet) for 247.70 feet to a point of compound curvature; Northwesterly along an arc of a curve to the right of radius 1,365.10 feet (delta 06°26'16\") (chord bearing N62°34'34\"W) (chord 153.31 feet) for 153.39 feet to a point of compound curvature; Northwesterly along an arc of a curve to the right of radius 291.89 feet (delta 34°24'15\") (chord bearing N42°09'19\"W) (chord 172.65 feet) for 175.27 feet to a point on a non-tangent curve; Northerly along an arc of a curve to the right of radius 71.65 feet (delta 17°49'54\") (chord bearing N19°41'07\"W) (chord 22.21 feet) for 22.30 feet to a point on a non-tangent curve; Northerly along an arc of a curve to the right of radius 59.61 feet (delta 76°31'16\") (chord bearing N18°46'44\"E) (chord 73.82 feet) for 79.61 feet to a point on a non-tangent curve; Northwesterly along an arc of a curve to the right of radius 905.05 feet (delta 15°01'45\") (chord bearing N42°33'41\"W) (chord 236.72 feet) for 237.40 feet to a point on a non-tangent curve; Southwesterly along an arc of a curve to the right of radius 77.61 feet (delta 37°04'17\") (chord bearing S47°08'32\"W) (chord 49.34 feet) for 50.21 feet to a point on a non-tangent curve; Westerly along an arc of a curve to the right of radius 135.38 feet (delta 25°04'58\") (chord bearing N84°06'43\"W) (chord 58.79 feet) for 59.27 feet to a point of\n\nDESCRIPTION (CONTINUED)\n\ncompound curvature; Northwesterly along an arc of a curve to the right of radius 467.73 feet (delta $14^\\circ07'02\"$) (chord bearing N$64^\\circ30'43\"$W) (chord 114.95 feet) for 115.25 feet to a point of compound curvature; Northwesterly along an arc of a curve to the right of radius 194.05 feet (delta $17^\\circ03'31\"$) (chord bearing N$48^\\circ55'26\"$W) (chord 57.56 feet) for 57.78 feet to a point of compound curvature; Northwesterly along an arc of a curve to the right of radius 16,554.26 feet (delta $00^\\circ13'19\"$) (chord bearing N$40^\\circ17'01\"$W) (chord 64.10 feet) for 64.10 feet to a point on a non-tangent curve; Northwesterly along an arc of a curve to the left of radius 132.08 feet (delta $24^\\circ43'54\"$) (chord bearing N$52^\\circ32'19\"$W) (chord 56.57 feet) for 57.01 feet to a point on a non-tangent curve; Northwesterly along an arc of a curve to the right of radius 150.72 feet (delta $30^\\circ38'47\"$) (chord bearing N$49^\\circ34'52\"$W) (chord 79.66 feet) for 80.62 feet to a point on a non-tangent curve; Northwesterly along an arc of a curve to the right of radius 134.41 feet (delta $07^\\circ39'36\"$) (chord bearing N$31^\\circ18'22\"$W) (chord 17.96 feet) for 17.97 feet to a point of reverse curvature and Westerly along an arc of a curve to the left of radius 50.00 feet (delta $114^\\circ09'39\"$) (chord bearing N$84^\\circ33'23\"$W) (chord 83.95 feet) for 99.63 feet to a point of compound curvature; Southwesterly along an arc of a curve to the left of radius 1,275.06 feet (delta $25^\\circ06'21\"$) (chord bearing S$25^\\circ48'37\"$W) (chord 554.25 feet) for 558.71 feet to a point on a non-tangent curve; Southerly along an arc of a curve to the left of radius 582.03 feet (delta $36^\\circ50'51\"$) (chord bearing S$08^\\circ02'26\"$E) (chord 367.84 feet) for 374.31 feet; N$67^\\circ07'20\"$E along a non-tangent line for 63.59 feet to a point on a non-tangent curve; Easterly along an arc of a curve to the right of radius 166.29 feet (delta $41^\\circ54'05\"$) (chord bearing N$83^\\circ27'38\"$E) (chord 118.92 feet) for 121.61 feet to a point on a non-tangent curve; Southeasterly along an arc of a curve to the right of radius 169.46 feet (delta $31^\\circ20'40\"$) (chord bearing S$65^\\circ43'41\"$E) (chord 91.55 feet) for 92.70 feet to a point on a non-tangent curve; Southeasterly along an arc of a curve to the right of radius 589.08 feet (delta $11^\\circ13'22\"$) (chord bearing S$55^\\circ02'06\"$E) (chord 115.20 feet) for 115.39 feet to a point on a non-tangent curve; Southeasterly along an arc of a curve to the left of radius 1,146.62 feet (delta $07^\\circ21'35\"$) (chord bearing S$53^\\circ05'55\"$E) (chord 147.18 feet) for 147.29 feet; S$88^\\circ47'21\"$E along a non-tangent line for 30.00 feet; S$65^\\circ12'42\"$E for 36.23 feet; S$66^\\circ23'56\"$E for 36.80 feet to a point on a non-tangent curve; Easterly along an arc of a curve to the right of radius 262.16 feet (delta $07^\\circ13'22\"$) (chord bearing S$67^\\circ11'09\"$E) (chord 33.03 feet) for 33.05 feet to a point of compound curvature; Southeasterly along an arc of a curve to the right of radius 1,872.88 feet (delta $04^\\circ37'23\"$) (chord bearing S$61^\\circ15'46\"$E) (chord 151.08 feet) for 151.12 feet to a point on a non-tangent curve; Southeasterly along an arc of a curve to the left of radius 124.47 feet (delta $08^\\circ59'25\"$) (chord bearing S$54^\\circ36'32\"$E) (chord 19.51 feet) for 19.53 feet to a point on a non-tangent curve; Southeasterly along an arc of a curve to the right of radius 173.75 feet (delta $32^\\circ30'29\"$) (chord bearing S$43^\\circ13'27\"$E) (chord 97.26 feet) for 98.58 feet; S$28^\\circ20'22\"$E along a non-tangent line for 129.11 feet to a point of curvature; Southeasterly along an arc of a curve to the left of radius 238.65 feet (delta $69^\\circ24'28\"$) (chord bearing S$63^\\circ02'36\"$E) (chord 271.74 feet) for 289.09 feet to a point of reverse curvature; Southeasterly along an arc of a curve to the right of radius 108.13 feet (delta $71^\\circ09'33\"$) (chord bearing S$62^\\circ10'04\"$E) (chord 125.83 feet) for 134.30 feet and S$29^\\circ26'44\"$E along a non-tangent line for 143.97 feet to an intersection with the Northerly right of way line of Corkscrew Road, Parcel 102A, as described in a deed recorded in Instrument No. 2008000174785, Lee County Records; thence run S$61^\\circ47'02\"$W along said Northerly right of way line of said Corkscrew Road for 815.21 feet to an intersection with the South line of the Southeast Quarter (SE 1/4) of said Section 19; thence run S$89^\\circ22'06\"$W along said South line for 1,649.44 feet; thence run N$04^\\circ16'08\"$E for 2,407.17 feet to an intersection with the Southeasterly line of a Conservation Easement, Mitigation Area E1, as described in a deed recorded in Instrument No. 2017000016504, Lee County Records; thence run S$73^\\circ15'13\"$W along said Southeasterly line for 2,634.49 feet to an intersection with\n\nDESCRIPTION (CONTINUED)\n\nthe East line of a Right of Way Agreement (Florida Power and Light Co.) as described in a deed recorded in Official Records Book 730, at Page 622, Lee County Records; thence run along the East line of said right of way the following three (3) courses: Noo°48'32\"W for 978.84 feet; Noo°49'48\"W for 2,639.95 feet and Noo°51'06\"W for 887.98 feet to an intersection with the North line of the South 890.43 feet of said Section 18; thence run S89°23'53\"W along said North line for 235.00 feet to an intersection with the West line of a Right of Way Agreement (Florida Power and Light Co.) as described in a deed recorded in Official Records Book 221, at Page 191, Lee County Records; thence run along West line of said right of way agreement the following two (2) courses: Noo°51'06\"W for 1,919.98 feet and Noo°50'43\"W for 2,725.01 feet to an intersection with the Southerly line of lands as described in a deed recorded in Instrument No. 2016000186921, Lee County Records; thence run along the Southerly and Easterly line of said lands the following ten (10) courses: N89°09'13\"E for 352.34 feet; S49°04'56\"E for 32.52 feet; S56°00'04\"E for 671.83 feet; S78°37'05\"E for 581.11 feet; N43°48'39\"E for 800.04 feet; N22°12'13\"E for 426.32 feet; N69°23'30\"E for 468.43 feet; N43°48'39\"E for 3,780.99 feet; No3°42'39\"W for 1,427.62 feet and No1°00'27\"W for 223.26 feet to an intersection with the Southerly right of way line of Alico Road, (100 feet wide right of way), as described in a deed recorded in Official Records Book 399, at Page 334, Lee County Records; thence run N88°59'30\"E along said Southerly right of way line for 4,905.16 feet to an intersection with the East line of the Northeast Quarter (NE 1/4) of said Section 8; thence run So1°05'11\"E along said East line for 2,311.30 feet to the POINT OF BEGINNING.\n\nContaining 1,563.17 acres, more or less.\n\nAND\n\nA tract or parcel of land being a portion of Tract \"F-1\" of the record plat of \"WILDBLUE PHASE 2\", recorded in Instrument No. 2018000070231, of the Public Records of Lee County, Florida, lying in Sections 7, 8, 17, 18, and 20, Township 46 South, Range 26 East, Lee County, Florida, said tract or parcel of land being more particularly described as follows:\n\nCommencing at the Northeast corner of said Section 17 run Soo°53'19\"E along the East line of the Northeast Quarter (NE 1/4) of said Section 17 for 2,517.42 feet; thence run S89°06'41\"W for 484.63 feet to an intersection with the Southerly line of said Tract \"F-1\" and the POINT OF BEGINNING.\n\nFrom said Point of Beginning run along the Southerly and Easterly line of said Tract \"F-1\" the following Sixty-five (65) courses: Southerly along an arc of a curve to the right of radius 54.00 feet (delta 17°14'33\") (chord bearing So4°20'42\"W) (chord 16.19 feet) for 16.25 feet to a point of compound curvature; Southwesterly along an arc of a curve to the right of radius 69.50 feet (delta 27°17'04\") (chord bearing S26°36'30\"W) (chord 32.79 feet) for 33.10 feet to a point of tangency; S40°15'02\"W for 11.61 feet; S47°09'59\"W for 9.43 feet to a point of curvature; Westerly along an arc of a curve to the right of radius 80.48 feet (delta 57°38'58\") (chord bearing S75°59'27\"W) (chord 77.60 feet) for 80.97 feet to a point of tangency; N75°11'04\"W for 26.46 feet to a point of curvature; Westerly along an arc of a curve to the left of radius 4.00 feet (delta 69°43'11\") (chord bearing S69°57'21\"W) (chord 4.57 feet) for 4.87 feet to a point of tangency; S35°05'45\"W for 12.61 feet; Southwesterly along an arc of a curve to the right of radius 85.00 feet (delta 14°44'01\") (chord bearing S42°27'46\"W) (chord 21.80 feet) for 21.86 feet to a point of compound curvature; Southwesterly along an arc of a curve to the right of radius 60.00 feet (delta 29°05'31\") (chord bearing S64°22'32\"W) (chord 30.14 feet) for 30.47 feet to a point of compound curvature; Westerly along an arc of a curve to the right of radius 91.00 feet (delta 23°17'41\") (chord bearing N89°25'53\"W) (chord 36.75 feet) for 37.00 feet to a\n\nDESCRIPTION (CONTINUED)\n\npoint of tangency; N77°47'02\"W for 23.24 feet to a point of curvature; Westerly along an arc of a curve to the left of radius 231.01 feet (delta 14°51'06\") (chord bearing N85°12'35\"W) (chord 59.71 feet) for 59.88 feet to a point of curvature; Westerly along an arc of a curve to the left of radius 431.02 feet (delta 07°14'06\") (chord bearing S83°44'49\"W) (chord 54.39 feet) for 54.43 feet to a point of tangency; S80°07'46\"W for 18.24 feet; So4°15'30\"W for 23.26 feet to a point of curvature; Southerly along an arc of a curve to the right of radius 90.00 feet (delta 31°25'49\") (chord bearing S19°58'24\"W) (chord 48.76 feet) for 49.37 feet to a point of compound curvature; Southwesterly along an arc of a curve to the right of radius 75.00 feet (delta 25°30'21\") (chord bearing S48°26'29\"W) (chord 33.11 feet) for 33.39 feet to a point of compound curvature; Westerly along an arc of a curve to the right of radius 152.01 feet (delta 28°15'16\") (chord bearing S75°19'18\"W) (chord 74.20 feet) for 74.96 feet to a point of tangency; S89°26'56\"W for 43.36 feet; N87°46'59\"W for 127.76 feet to a point of curvature; Westerly along an arc of a curve to the left of radius 2,280.12 feet (delta 05°14'29\") (chord bearing S89°35'47\"W) (chord 208.51 feet) for 208.58 feet to a point of tangency; S86°58'33\"W for 102.56 feet to a point of curvature; Westerly along an arc of a curve to the right of radius 1,234.06 feet (delta 10°26'01\") (chord bearing N87°48'27\"W) (chord 224.41 feet) for 224.72 feet to a point of tangency; N82°35'27\"W for 254.90 feet to a point of curvature; Westerly along an arc of a curve to the left of radius 746.04 feet (delta 12°20'46\") (chord bearing N88°45'50\"W) (chord 160.45 feet) for 160.76 feet to a point of tangency; S85°03'47\"W for 108.35 feet to a point of curvature; Westerly along an arc of a curve to the right of radius 245.01 feet (delta 41°29'11\") (chord bearing N74°11'37\"W) (chord 173.56 feet) for 177.41 feet to a point of tangency; N53°27'01\"W for 33.08 feet to a point of curvature; Northwesterly along an arc of a curve to the left of radius 50.00 feet (delta 12°30'15\") (chord bearing N59°42'09\"W) (chord 10.89 feet) for 10.91 feet to a point of compound curvature; Westerly along an arc of a curve to the left of radius 12.00 feet (delta 31°23'41\") (chord bearing N81°39'07\"W) (chord 6.49 feet) for 6.58 feet to a point of compound curvature; Westerly along an arc of a curve to the left of radius 83.00 feet (delta 15°50'02\") (chord bearing S74°44'02\"W) (chord 22.87 feet) for 22.94 feet to a point of tangency; S66°49'01\"W for 42.16 feet to a point of curvature; Westerly along an arc of a curve to the right of radius 214.01 feet (delta 05°51'06\") (chord bearing S69°44'34\"W) (chord 21.85 feet) for 21.86 feet to a point of compound curvature; Westerly along an arc of a curve to the right of radius 200.01 feet (delta 15°17'56\") (chord bearing S80°19'05\"W) (chord 53.25 feet) for 53.41 feet to a point of compound curvature; Westerly along an arc of a curve to the right of radius 271.01 feet (delta 11°36'04\") (chord bearing N86°13'55\"W) (chord 54.78 feet) for 54.87 feet to a point of tangency; N80°25'53\"W for 49.47 feet to a point of curvature; Westerly along an arc of a curve to the left of radius 397.02 feet (delta 05°14'27\") (chord bearing N83°03'06\"W) (chord 36.30 feet) for 36.32 feet; So2°35'22\"W along a non-tangent line for 134.38 feet to a point of curvature; Southerly along an arc of a curve to the right of radius 708.04 feet (delta 17°36'37\") (chord bearing S11°23'40\"W) (chord 216.76 feet) for 217.62 feet to a point of tangency; S20°11'59\"W for 174.31 feet; S15°33'29\"W for 259.20 feet to a point of curvature; Southerly along an arc of a curve to the left of radius 1,198.06 feet (delta 08°17'34\") (chord bearing S11°24'42\"W) (chord 173.25 feet) for 173.40 feet to a point of tangency; So7°15'55\"W for 10.21 feet to a point of curvature; Southerly along an arc of a curve to the left of radius 498.03 feet (delta 25°44'02\") (chord bearing So5°36'06\"E) (chord 221.81 feet) for 223.68 feet; S10°27'01\"E along a non-tangent line for 76.52 feet; S15°41'48\"E for 77.51 feet to a point of curvature; Southerly along an arc of a curve to the right of radius 450.02 feet (delta 40°53'13\") (chord bearing So4°44'49\"W) (chord 314.37 feet) for 321.14 feet to a point of tangency; S25°11'26\"W for 71.56 feet; S19°51'16\"W for 31.29 feet to a point of curvature; Southerly along an arc of a curve to the left of radius 73.00 feet (delta 40°27'08\") (chord bearing Soo°22'18\"E) (chord 50.48 feet) for\n\nDESCRIPTION (CONTINUED)\n\n51.54 feet to a point of tangency; S20°35'52\"E for 36.71 feet to a point of curvature; Southerly along an arc of a curve to the right of radius 214.01 feet (delta 35°30'11\") (chord bearing S02°50'46\"E) (chord 130.50 feet) for 132.61 feet to a point of tangency; S14°54'20\"W for 170.77 feet to a point of curvature; Southwesterly along an arc of a curve to the right of radius 464.02 feet (delta 33°21'16\") (chord bearing S31°34'58\"W) (chord 266.33 feet) for 270.13 feet to a point of tangency; S48°15'36\"W for 186.88 feet; Southwesterly along an arc of a curve to the left of radius 89.00 feet (delta 44°30'24\") (chord bearing S26°00'24\"W) (chord 67.41 feet) for 69.14 feet to a point of tangency; S03°45'12\"W for 89.70 feet; Southerly along an arc of a curve to the right of radius 246.01 feet (delta 28°40'30\") (chord bearing S18°05'26\"W) (chord 121.84 feet) for 123.12 feet to a point of tangency; S32°25'41\"W for 64.13 feet; Southwesterly along an arc of a curve to the left of radius 220.01 feet (delta 14°13'54\") (chord bearing S25°18'44\"W) (chord 54.51 feet) for 54.65 feet to a point of tangency; S18°11'47\"W for 46.81 feet; Southwesterly along an arc of a curve to the right of radius 273.51 feet (delta 35°16'31\") (chord bearing S35°55'02\"W) (chord 165.75 feet) for 168.39 feet to a point of tangency; S53°28'18\"W for 108.17 feet to a point of curvature and Southwesterly along an arc of a curve to the left of radius 217.01 feet (delta 16°34'44\") (chord bearing S45°10'56\"W) (chord 62.57 feet) for 62.79 feet to the Westerly most corner of said Conservation Easement, Mitigation Area J-5; thence run N84°09'06\"W along a non-tangent line for 109.77 feet; thence run N62°28'13\"W for 513.06 feet; thence run N59°57'40\"W for 651.72 feet; thence run N36°57'44\"E for 225.13 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 1,525.00 feet (delta 10°29'23\") (chord bearing N42°12'25\"E) (chord 278.81 feet) for 279.20 feet to a point of tangency; thence run N47°27'07\"E for 160.73 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 175.00 feet (delta 25°20'50\") (chord bearing N34°46'42\"E) (chord 76.79 feet) for 77.42 feet to a point of tangency; thence run N22°06'17\"E for 384.89 feet; thence run S76°10'58\"W for 103.98 feet to a point of curvature; thence run Westerly along an arc of a curve to the right of radius 55.00 feet (delta 64°09'20\") (chord bearing N71°44'21\"W) (chord 58.42 feet) for 61.58 feet to a point of tangency; thence run N39°39'41\"W for 191.03 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 55.00 feet (delta 100°29'06\") (chord bearing N10°34'51\"E) (chord 84.56 feet) for 96.46 feet to a point of tangency; thence run N60°49'24\"E for 511.56 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 75.00 feet (delta 43°12'25\") (chord bearing N39°13'12\"E) (chord 55.23 feet) for 56.56 feet to a point of tangency; thence run N17°36'59\"E for 19.12 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 1,025.00 feet (delta 08°19'04\") (chord bearing N21°46'31\"E) (chord 148.67 feet) for 148.80 feet to a point of tangency; thence run N25°56'03\"E for 194.92 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 125.00 feet (delta 31°40'54\") (chord bearing N10°05'36\"E) (chord 68.24 feet) for 69.12 feet to a point of tangency; thence run N05°44'51\"W for 315.52 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the left of radius 175.00 feet (delta 54°45'50\") (chord bearing N33°07'46\"W) (chord 160.97 feet) for 167.27 feet to a point of tangency; thence run N60°30'41\"W for 250.77 feet to a point of curvature; thence run Westerly along an arc of a curve to the left of radius 775.00 feet (delta 23°20'01\") (chord bearing N72°10'41\"W) (chord 313.44 feet) for 315.62 feet to a point of tangency; thence run N83°50'42\"W for 516.23 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 75.00 feet (delta 80°17'48\") (chord bearing S56°00'24\"W) (chord 96.72 feet) for 105.11 feet to a point of tangency; thence run S15°51'31\"W for 540.62 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 75.00 feet (delta 29°57'54\") (chord bearing S00°52'34\"W) (chord 38.78 feet) for 39.22 feet to a point of tangency; thence run S14°06'23\"E for 137.47 feet to a\n\nDESCRIPTION (CONTINUED)\n\npoint of curvature; thence run Southerly along an arc of a curve to the right of radius 1,025.00 feet (delta 08°31'33\") (chord bearing S09°50'37\"E) (chord 152.38 feet) for 152.52 feet to a point of tangency; thence run S05°34'51\"E for 96.94 feet to a point of curvature; thence run Southerly along an arc of a curve to the right of radius 825.00 feet (delta 09°37'11\") (chord bearing S00°46'15\"E) (chord 138.35 feet) for 138.51 feet to a point of tangency; thence run S04°02'20\"W for 17.62 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 95.00 feet (delta 59°20'24\") (chord bearing S33°42'32\"W) (chord 94.05 feet) for 98.39 feet to a point of tangency; thence run S63°22'45\"W for 95.98 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 75.00 feet (delta 26°05'30\") (chord bearing S50°20'00\"W) (chord 33.86 feet) for 34.15 feet to a point of tangency; thence run S37°17'15\"W for 385.52 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 75.00 feet (delta 53°50'18\") (chord bearing S10°22'06\"W) (chord 67.91 feet) for 70.47 feet to a point of tangency; thence run S16°33'03\"E for 273.87 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the left of radius 975.00 feet (delta 15°05'48\") (chord bearing S24°05'57\"E) (chord 256.16 feet) for 256.90 feet to a point of tangency; thence run S31°38'51\"E for 54.90 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 67.00 feet (delta 128°31'46\") (chord bearing S32°37'02\"W) (chord 120.71 feet) for 150.30 feet to a point of tangency; thence run N83°07'05\"W for 525.38 feet to a point of curvature; thence run Westerly along an arc of a curve to the left of radius 325.00 feet (delta 15°53'40\") (chord bearing S88°56'05\"W) (chord 89.87 feet) for 90.16 feet to a point of reverse curvature; thence run Westerly along an arc of a curve to the right of radius 375.00 feet (delta 21°55'47\") (chord bearing N88°02'52\"W) (chord 142.66 feet) for 143.53 feet to a point of tangency; thence run N77°04'58\"W for 182.20 feet to a point of curvature; thence run Westerly along an arc of a curve to the left of radius 125.00 feet (delta 24°18'51\") (chord bearing N89°14'23\"W) (chord 52.65 feet) for 53.04 feet to a point of reverse curvature; thence run Westerly along an arc of a curve to the right of radius 125.00 feet (delta 23°59'07\") (chord bearing N89°24'15\"W) (chord 51.95 feet) for 52.33 feet to a point of tangency; thence run N77°24'42\"W for 220.11 feet to a point of curvature; thence run Westerly along an arc of a curve to the left of radius 1,475.00 feet (delta 05°45'32\") (chord bearing N80°17'28\"W) (chord 148.19 feet) for 148.25 feet to a point of tangency; thence run N83°10'13\"W for 512.33 feet to a point of curvature; thence run Westerly along an arc of a curve to the left of radius 225.00 feet (delta 19°32'48\") (chord bearing S87°03'23\"W) (chord 76.39 feet) for 76.76 feet to a point of reverse curvature; thence run Westerly along an arc of a curve to the right of radius 175.00 feet (delta 17°19'21\") (chord bearing S85°56'39\"W) (chord 52.71 feet) for 52.91 feet to a point of tangency; thence run N85°23'41\"W for 296.12 feet to a point of curvature; thence run Westerly along an arc of a curve to the right of radius 2,025.00 feet (delta 04°08'08\") (chord bearing N83°19'36\"W) (chord 146.14 feet) for 146.17 feet to a point of tangency; thence run N81°15'32\"W for 538.83 feet to a point of curvature; thence run Westerly along an arc of a curve to the left of radius 50.00 feet (delta 53°36'02\") (chord bearing S71°56'27\"W) (chord 45.09 feet) for 46.78 feet to a point of reverse curvature; thence run Westerly along an arc of a curve to the right of radius 115.00 feet (delta 47°56'53\") (chord bearing S69°06'53\"W) (chord 93.45 feet) for 96.24 feet to a point of tangency; thence run N86°54'41\"W for 300.04 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the right of radius 40.00 feet (delta 89°43'03\") (chord bearing N42°03'09\"W) (chord 56.43 feet) for 62.63 feet to a point of tangency; thence run N02°48'22\"E for 115.05 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 125.00 feet (delta 38°33'50\") (chord bearing N22°05'17\"E) (chord 82.55 feet) for 84.13 feet to a point of tangency; thence run N41°22'13\"E for 463.38 feet to a point of curvature; thence run Northeastery along an arc of a curve to the right of radius\n\nDESCRIPTION (CONTINUED)\n\n75.00 feet (delta 51°38'09\") (chord bearing N67°11'17\"E) (chord 65.33 feet) for 67.59 feet to a point of reverse curvature; thence run Northeasterly along an arc of a curve to the left of radius 35.00 feet (delta 55°50'05\") (chord bearing N65°05'19\"E) (chord 32.77 feet) for 34.11 feet to a point of tangency; thence run N37°10'16\"E for 317.27 feet to a point of curvature; thence run Easterly along an arc of a curve to the right of radius 45.00 feet (delta 77°53'32\") (chord bearing N76°07'02\"E) (chord 56.57 feet) for 61.18 feet to a point of reverse curvature; thence run Easterly along an arc of a curve to the left of radius 35.00 feet (delta 89°05'54\") (chord bearing N70°30'51\"E) (chord 49.11 feet) for 54.43 feet to a point of tangency; thence run N25°57'54\"E for 719.51 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 55.00 feet (delta 73°28'14\") (chord bearing N62°42'01\"E) (chord 65.79 feet) for 70.53 feet to a point of tangency; thence run S80°33'52\"E for 76.95 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 35.00 feet (delta 78°58'38\") (chord bearing N59°56'49\") (chord 44.51 feet) for 48.24 feet to a point of tangency; thence run N20°27'30\"E for 149.12 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 55.00 feet (delta 89°25'20\") (chord bearing N65°10'10\"E) (chord 77.39 feet) for 85.84 feet to a point of tangency; thence run S70°07'10\"E for 82.71 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 325.00 feet (delta 26°39'57\") (chord bearing S56°47'11\"E) (chord 149.90 feet) for 151.26 feet to a point of tangency; thence run S43°27'13\"E for 184.25 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 475.00 feet (delta 81°20'53\") (chord bearing S84°07'39\"E) (chord 619.17 feet) for 674.40 feet to a point of tangency; thence run N55°11'54\"E for 52.99 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 225.00 feet (delta 26°23'45\") (chord bearing N42°00'02\"E) (chord 102.74 feet) for 103.66 feet to a point of tangency; thence run N28°48'09\"E for 43.26 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 175.00 feet (delta 37°44'43\") (chord bearing N09°55'48\"E) (chord 113.21 feet) for 115.29 feet to a point of compound curvature; thence run Northwesternly along an arc of a curve to the left of radius 75.00 feet (delta 31°02'23\") (chord bearing N24°27'46\"W) (chord 40.14 feet) for 40.63 feet to a point of tangency; thence run N39°58'57\"W for 16.19 feet to a point of curvature; thence run Northwesternly along an arc of a curve to the left of radius 275.00 feet (delta 43°39'00\") (chord bearing N61°48'27\"W) (chord 204.47 feet) for 209.50 feet to a point of reverse curvature; thence run Westerly along an arc of a curve to the right of radius 100.00 feet (delta 19°42'04\") (chord bearing N72°46'55\"W) (chord 34.22 feet) for 34.38 feet to a point of tangency; thence run N63°55'53\"W for 880.47 feet to a point of curvature; thence run Northwesternly along an arc of a curve to the right of radius 100.00 feet (delta 81°42'16\") (chord bearing N23°04'45\"W) (chord 130.82 feet) for 142.60 feet to a point of tangency; thence run N17°46'23\"E for 90.68 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 55.00 feet (delta 81°39'24\") (chord bearing N58°36'04\"E) (chord 71.92 feet) for 78.38 feet to a point of tangency; thence run S80°34'14\"E for 34.34 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 25.00 feet (delta 83°55'54\") (chord bearing N57°27'49\"E) (chord 33.43 feet) for 36.62 feet to a point of tangency; thence run N15°29'52\"E for 405.98 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 525.00 feet (delta 38°16'07\") (chord bearing N34°37'56\"E) (chord 344.17 feet) for 350.65 feet to a point of tangency; thence run N53°45'59\"E for 1,244.08 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 975.00 feet (delta 19°37'52\") (chord bearing N43°57'03\"E) (chord 332.43 feet) for 334.06 feet to a point of tangency; thence run N34°08'07\"E for 337.12 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the left of radius 975.00 feet (delta 14°30'43\") (chord\n\nDESCRIPTION (CONTINUED)\n\nbearing N26°52'45\"E (chord 246.29 feet) for 246.95 feet to a point of tangency; thence run N19°37'24\"E for 311.22 feet to a point of curvature; thence run Northeastery along an arc of a curve to the right of radius 85.00 feet (delta 70°22'36\") (chord bearing N54°48'42\"E) (chord 97.97 feet) for 104.41 feet to a point of tangency; thence run N90°00'00\"E for 238.27 feet to a point of curvature; thence run Northeastery along an arc of a curve to the left of radius 55.00 feet (delta 59°24'41\") (chord bearing N60°17'40\"E) (chord 54.51 feet) for 57.03 feet to a point of reverse curvature; thence run Northeastery along an arc of a curve to the right of radius 105.00 feet (delta 62°46'57\") (chord bearing N61°58'48\"E) (chord 109.38 feet) for 115.06 feet to a point of tangency; thence run S86°37'44\"E for 38.69 feet to a point of curvature; thence run Easterly along an arc of a curve to the left of radius 9,975.00 feet (delta 04°35'00\") (chord bearing S88°55'14\"E) (chord 797.75 feet) for 797.96 feet to a point of tangency; thence run N88°47'16\"E for 62.79 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 105.00 feet (delta 75°14'50\") (chord bearing S53°35'19\"E) (chord 128.20 feet) for 137.90 feet to a point of reverse curvature; thence run Southeasterly along an arc of a curve to the left of radius 25.00 feet (delta 79°30'00\") (chord bearing S55°42'54\"E) (chord 31.97 feet) for 34.69 feet to a point of tangency; thence run N84°32'06\"E for 43.22 feet to a point of curvature; thence run Northeastery along an arc of a curve to the left of radius 25.00 feet (delta 80°29'14\") (chord bearing N44°17'29\"E) (chord 32.30 feet) for 35.12 feet to a point of tangency; thence run N04°02'52\"E for 83.35 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 2,025.00 feet (delta 04°45'08\") (chord bearing N06°25'26\"E) (chord 167.91 feet) for 167.96 feet to a point of reverse curvature; thence run Northwesterly along an arc of a curve to the left of radius 25.00 feet (delta 94°47'54\") (chord bearing N38°35'56\"W) (chord 36.80 feet) for 41.36 feet to a point of reverse curvature; thence run Northwesterly along an arc of a curve to the right of radius 55.00 feet (delta 81°50'30\") (chord bearing N45°04'38\"W) (chord 72.05 feet) for 78.56 feet to a point of tangency; thence run N04°09'23\"W for 65.44 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the left of radius 15.00 feet (delta 86°56'34\") (chord bearing N47°37'40\"W) (chord 20.64 feet) for 22.76 feet to a point of reverse curvature; thence run Northwesterly along an arc of a curve to the right of radius 75.00 feet (delta 110°16'00\") (chord bearing N35°57'58\"W) (chord 123.07 feet) for 144.34 feet to a point of tangency; thence run N19°10'02\"E for 2.70 feet to a point of curvature; thence run Northeastery along an arc of a curve to the right of radius 125.00 feet (delta 40°26'35\") (chord bearing N39°20'20\"E) (chord 86.21 feet) for 88.02 feet to a point of tangency; thence run N59°30'38\"E for 133.65 feet to a point of curvature; thence run Northeastery along an arc of a curve to the left of radius 175.00 feet (delta 30°44'54\") (chord bearing N44°08'10\"E) (chord 92.79 feet) for 93.92 feet to a point of tangency; thence run N28°45'43\"E for 143.26 feet to a point of curvature; thence run Northeastery along an arc of a curve to the right of radius 75.00 feet (delta 66°43'13\") (chord bearing N62°07'19\"E) (chord 82.48 feet) for 87.34 feet to a point of tangency; thence run S84°31'04\"E for 264.21 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 75.00 feet (delta 39°03'54\") (chord bearing S64°59'07\"E) (chord 50.15 feet) for 51.14 feet to a point of reverse curvature; thence run Southeasterly along an arc of a curve to the left of radius 25.00 feet (delta 40°44'26\") (chord bearing S65°49'23\"E) (chord 17.40 feet) for 17.78 feet to a point of tangency; thence run S86°11'36\"E for 343.76 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 75.00 feet (delta 48°24'27\") (chord bearing S61°59'23\"E) (chord 61.50 feet) for 63.37 feet to a point of tangency; thence run S37°47'09\"E for 140.60 feet to a point of curvature; thence run Southerly along an arc of a curve to the right of radius 125.00 feet (delta 35°11'54\") (chord bearing S20°11'12\"E) (chord 75.59 feet) for 76.79 feet to a point of tangency; thence run S02°35'15\"E for 145.50 feet to a point of curvature; thence run\n\nDESCRIPTION (CONTINUED)\n\nSoutherly along an arc of a curve to the right of radius 1,025.00 feet (delta $06^\\circ 22' 00''$) (chord bearing $S00^\\circ 35' 45''W$) (chord 113.84 feet) for 113.90 feet to a point of tangency; thence run $S03^\\circ 46' 44''W$ for 115.28 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the right of radius 55.00 feet (delta $84^\\circ 54' 26''$) (chord bearing $S46^\\circ 13' 58''W$) (chord 74.25 feet) for 81.51 feet to a point of tangency; thence run $S88^\\circ 41' 11''W$ for 66.04 feet; thence run $N89^\\circ 30' 28''W$ for 143.88 feet to a point of curvature; thence run Southwesterly along an arc of a curve to the left of radius 25.00 feet (delta $91^\\circ 17' 38''$) (chord bearing $S44^\\circ 50' 43''W$) (chord 35.75 feet) for 39.83 feet to a point of tangency; thence run $S00^\\circ 48' 06''E$ for 462.06 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the left of radius 25.00 feet (delta $85^\\circ 47' 00''$) (chord bearing $S43^\\circ 41' 36''E$) (chord 34.03 feet) for 37.43 feet to a point of tangency; thence run $S86^\\circ 35' 06''E$ for 782.57 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 75.00 feet (delta $87^\\circ 55' 32''$) (chord bearing $S42^\\circ 37' 20''E$) (chord 104.13 feet) for 115.09 feet to a point of tangency; thence run $S01^\\circ 20' 26''W$ for 281.53 feet to a point of curvature; thence run Southerly along an arc of a curve to the right of radius 225.00 feet (delta $16^\\circ 16' 07''$) (chord bearing $S00^\\circ 28' 30''W$) (chord 63.67 feet) for 63.89 feet to a point of tangency; thence run $S17^\\circ 36' 33''W$ for 31.78 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the left of radius 25.00 feet (delta $110^\\circ 21' 05''$) (chord bearing $S37^\\circ 33' 59''E$) (chord 41.05 feet) for 48.15 feet to a point of tangency; thence run $N87^\\circ 15' 28''E$ for 133.97 feet; thence run $S85^\\circ 49' 54''E$ for 703.33 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 75.00 feet (delta $74^\\circ 04' 54''$) (chord bearing $S48^\\circ 47' 27''E$) (chord 90.36 feet) for 96.97 feet to a point of reverse curvature; thence run Southeasterly along an arc of a curve to the left of radius 25.00 feet (delta $74^\\circ 32' 44''$) (chord bearing $S49^\\circ 01' 22''E$) (chord 30.28 feet) for 32.53 feet to a point of tangency; thence run $S86^\\circ 17' 44''E$ for 107.75 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 75.00 feet (delta $76^\\circ 13' 50''$) (chord bearing $S48^\\circ 10' 50''E$) (chord 92.59 feet) for 99.79 feet to a point of tangency; thence run $S10^\\circ 03' 55''E$ for 444.30 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 675.00 feet (delta $09^\\circ 49' 13''$) (chord bearing $S14^\\circ 58' 31''E$) (chord 115.55 feet) for 115.69 feet to a point of tangency; thence run $S19^\\circ 53' 08''E$ for 455.82 feet to a point of curvature; thence run Southerly along an arc of a curve to the right of radius 125.00 feet (delta $23^\\circ 50' 58''$) (chord bearing $S07^\\circ 57' 39''E$) (chord 51.66 feet) for 52.03 feet to a point of tangency; thence run $S03^\\circ 57' 51''W$ for 117.42 feet to a point of curvature; thence run Southerly along an arc of a curve to the left of radius 175.00 feet (delta $31^\\circ 05' 54''$) (chord bearing $S11^\\circ 35' 06''E$) (chord 93.82 feet) for 94.98 feet to a point of tangency; thence run $S27^\\circ 08' 03''E$ for 227.36 feet to a point of curvature; thence run Southerly along an arc of a curve to the right of radius 125.00 feet (delta $28^\\circ 25' 07''$) (chord bearing $S12^\\circ 55' 29''E$) (chord 61.37 feet) for 62.00 feet to a point of tangency; thence run $S01^\\circ 17' 04''W$ for 327.99 feet; thence run $S88^\\circ 00' 00''E$ for 104.87 feet to the POINT OF BEGINNING.\n\nContaining 595.31 acres, more or less.\n\nAND\n\nA tract or parcel of land lying in Sections 17, 19 and 20, Township 46 South, Range 26 East, Lee County, Florida, said tract or parcel of land being more particularly described as follows:\n\nCommencing at the Northwest corner of said Section 20 run N89°23'44\"E along the North line of the Northwest Quarter (NW 1/4) of said Section 20 for 1,463.12 feet; thence run $S00^\\circ 36'16''E$ for 174.81 feet to an intersection with the Westerly line of a Conservation\n\nDESCRIPTION (CONTINUED)\n\nEasement, Mitigation Area J-4, as described in a deed recorded in Instrument No. 2017000016508, Lee County Records and the POINT OF BEGINNING.\n\nFrom said Point of Beginning run along the Westerly line of said Conservation Easement the following twenty-five (25) courses: Westerly along an arc of a curve to the left of radius 461.02 feet (delta 19°30′28″) (chord bearing S75°59′52″W) (chord 156.21 feet) for 156.97 feet to a point on a non-tangent curve; Southwesterly along an arc of a curve to the right of radius 542.03 feet (delta 11°50′56″) (chord bearing S42°36′34″W) (chord 111.89 feet) for 112.09 feet to a point of tangency; S48°32′02″W for 119.72 feet to a point of curvature; Southwesterly along an arc of a curve to the left of radius 206.01 feet (delta 36°27′42″) (chord bearing S30°18′11″W) (chord 128.90 feet) for 131.10 feet to a point of reverse curvature; Southerly along an arc of a curve to the right of radius 1,200.06 feet (delta 10°42′23″) (chord bearing S17°25′31″W) (chord 223.92 feet) for 224.25 feet to a point of reverse curvature; Southerly along an arc of a curve to the left of radius 100.01 feet (delta 53°26′27″) (chord bearing S03°56′30″E) (chord 89.93 feet) for 93.28 feet to a point of reverse curvature; Southerly along an arc of a curve to the right of radius 705.04 feet (delta 20°18′48″) (chord bearing S20°30′20″E) (chord 248.65 feet) for 249.96 feet to a point of reverse curvature; Southerly along an arc of a curve to the left of radius 253.01 feet (delta 17°56′10″) (chord bearing S19°19′00″E) (chord 78.88 feet) for 79.20 feet to a point of reverse curvature; Southerly along an arc of a curve to the right of radius 377.02 feet (delta 14°45′52″) (chord bearing S20°54′10″E) (chord 96.88 feet) for 97.15 feet to a point of reverse curvature; Southerly along an arc of a curve to the left of radius 644.03 feet (delta 09°27′55″) (chord bearing S18°15′11″E) (chord 106.27 feet) for 106.40 feet to a point of reverse curvature; Southerly along an arc of a curve to the right of radius 330.02 feet (delta 34°11′43″) (chord bearing S05°53′17″E) (chord 194.05 feet) for 196.96 feet to a point of tangency; S11°12′34″W for 132.64 feet to a point of curvature; Southerly along an arc of a curve to the left of radius 329.02 feet (delta 27°19′47″) (chord bearing S02°27′19″E) (chord 155.45 feet) for 156.94 feet to a point of tangency; S16°07′12″E for 146.33 feet to a point of curvature; Southerly along an arc of a curve to the right of radius 210.01 feet (delta 61°03′58″) (chord bearing S14°24′47″W) (chord 213.39 feet) for 223.83 feet to a point of tangency; S44°56′45″W for 80.91 feet to a point of curvature; Southerly along an arc of a curve to the left of radius 98.00 feet (delta 49°16′20″) (chord bearing S20°18′35″W) (chord 81.71 feet) for 84.28 feet to a point of tangency; S04°19′35″E for 155.86 feet to a point of curvature; Southerly along an arc of a curve to the left of radius 177.01 feet (delta 23°32′41″) (chord bearing S16°05′55″E) (chord 72.23 feet) for 72.74 feet to a point of tangency; S27°52′16″E for 71.27 feet to a point of curvature; Southerly along an arc of a curve to the right of radius 415.02 feet (delta 17°30′47″) (chord bearing S19°06′52″E) (chord 126.36 feet) for 126.86 feet to a point on a non-tangent curve; Southeastealy along an arc of a curve to the right of radius 122.01 feet (delta 115°19′45″) (chord bearing S52°22′14″E) (chord 206.17 feet) for 245.58 feet to a point of compound curvature; Southerly along an arc of a curve to the right of radius 774.04 feet (delta 17°53′30″) (chord bearing S14°14′24″W) (chord 240.73 feet) for 241.71 feet to a point of tangency; S23°11′09″W for 89.60 feet to a point on a non-tangent curve and Southwesterly along an arc of a curve to the right of radius 437.33 feet (delta 39°18′27″) (chord bearing S42°34′44″W) (chord 294.18 feet) for 300.03 feet; thence run N00°00′00″E along a non-tangent line for 32.17 feet; thence run S81°44′46″W for 504.82 feet to a point of curvature; thence run Westerly along an arc of a curve to the right of radius 1,525.00 feet (delta 05°19′50″) (chord bearing S84°24′41″W) (chord 141.83 feet) for 141.88 feet to a point of tangency; thence run S87°04′36″W for 460.68 feet to a point of curvature; thence run Northwesterly along an arc of a curve to the right of radius 105.00 feet (delta 65°32′07″) (chord bearing N60°09′21″W) (chord 113.66 feet) for 120.10 feet to a point of tangency; thence run N27°23′17″W for 421.97 feet to a point of curvature; thence run Northwesterly along an\n\nDESCRIPTION (CONTINUED)\n\narc of a curve to the right of radius 1,525.00 feet (delta 06°00'16\") (chord bearing N24°23'09\"W) (chord 159.74 feet) for 159.82 feet to a point of tangency; thence run N21°23'01\"W for 360.35 feet to a point of curvature; thence run Northeastery along an arc of a curve to the right of radius 175.00 feet (delta 104°09'44\") (chord bearing N36°41'51\"E) (chord 276.11 feet) for 318.15 feet to a point of tangency; thence run N82°46'43\"E for 328.63 feet to a point of curvature; thence run Easterly along an arc of a curve to the right of radius 1,525.00 feet (delta 06°47'39\") (chord bearing N86°10'32\"E) (chord 180.73 feet) for 180.83 feet to a point of tangency; thence run N89°34'22\"E for 177.62 feet to a point of curvature; thence run Northeastery along an arc of a curve to the left of radius 5.00 feet (delta 89°47'59\") (chord bearing N44°40'22\"E) (chord 7.06 feet) for 7.84 feet to a point of tangency; thence run N00°13'37\"W for 330.01 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 1,475.00 feet (delta 09°48'35\") (chord bearing N05°07'55\"W) (chord 252.23 feet) for 252.54 feet to a point of tangency; thence run N10°02'13\"W for 639.07 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 825.00 feet (delta 14°12'12\") (chord bearing N02°56'07\"W) (chord 203.99 feet) for 204.51 feet to a point of tangency; thence run N04°09'59\"E for 95.83 feet to a point of curvature; thence run Northerly along an arc of a curve to the left of radius 75.00 feet (delta 37°11'42\") (chord bearing N14°25'52\"W) (chord 47.84 feet) for 48.69 feet to a point of tangency; thence run N33°01'43\"W for 116.53 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 125.00 feet (delta 32°46'30\") (chord bearing N16°38'28\"W) (chord 70.53 feet) for 71.50 feet to a point of tangency; thence run N00°15'14\"W for 248.25 feet to a point of curvature; thence run Northerly along an arc of a curve to the right of radius 625.00 feet (delta 13°24'44\") (chord bearing N06°27'09\"E) (chord 145.97 feet) for 146.31 feet; thence run S88°58'18\"E along a non-tangent line for 20.47 feet to a point on a non-tangent curve; thence run Northerly along an arc of a curve to the right of radius 605.00 feet (delta 05°26'26\") (chord bearing N16°17'10\"E) (chord 57.43 feet) for 57.45 feet to a point of tangency; thence run N19°00'23\"E for 41.52 feet to a point of curvature; thence run Northeastery along an arc of a curve to the right of radius 55.00 feet (delta 53°17'32\") (chord bearing N45°39'09\"E) (chord 49.33 feet) for 51.16 feet to a point of reverse curvature; thence run Northeastery along an arc of a curve to the left of radius 45.00 feet (delta 59°51'09\") (chord bearing N42°22'21\"E) (chord 44.90 feet) for 47.01 feet to a point of tangency; thence run N12°26'46\"E for 331.68 feet to a point of curvature; thence run Northeastery along an arc of a curve to the right of radius 55.00 feet (delta 107°14'59\") (chord bearing N66°04'15\"E) (chord 88.57 feet) for 102.95 feet to a point of tangency; thence run S60°18'15\"E for 1,043.19 feet; thence run S59°00'09\"E for 220.11 feet to the POINT OF BEGINNING.\n\nContaining 96.06 acres, more or less.\n\nAND\n\nA tract or parcel of land lying in Section 19, Township 46 South, Range 26 East, Lee County, Florida, said tract or parcel of land being more particularly described as follows:\n\nCommencing at Southeast corner of said Section 19 run S89°22'06\"W along the South line of the Southeast Quarter (SE 1/4) of said Section 19 for 2,360.36 feet to the POINT OF BEGINNING.\n\nFrom said Point of Beginning continue S89°22'06\"W along said South line for 277.60 feet to the Southwest corner of said Fraction; thence run S89°21'58\"W along the South line of the Southwest Quarter (SW 1/4) of said Section 19 for 2,042.57 feet to an intersection with the East line of a Right of Way Agreement (Florida Power and Light Co.) as described in a deed\n\nDESCRIPTION (CONTINUED)\n\nrecorded in Official Records Book 730, at Page 622, Lee County Records; thence run N00°48'32\"W along said East line for 100.00 feet to the Southwest corner of lands described in a deed recorded in Official Records Book 3442, at Page 1430, Lee County Records; thence run along the Southerly, Easterly and Northerly line of said lands the following three (3) courses: N89°21'58\"E for 466.69 feet; N00°48'32\"W for 466.69 feet and S89°21'58\"W for 466.69 feet to an intersection with said East line of the Right of Way Agreement (Florida Power and Light Co.) as described in a deed recorded in Official Records Book 730, at Page 622, Lee County Records; thence run N00°48'32\"W along said East line for 1,100.54 feet to an intersection with the Southeasterly line of a Conservation Easement, Mitigation Area E1, as described in a deed recorded in Instrument No. 2017000016504, Lee County Records; thence run N73°15'13\"E along said Southeasterly line for 2,634.49 feet; thence run S04°16'08\"W along the Westerly line of said Conservation Easement and continuing along the Southerly prolongation thereof for 2,407.17 feet to the POINT OF BEGINNING.\n\nContaining 107.35 acres, more or less.\n\nLESS AND EXCEPT:\n\nA tract or parcel of land being a portion of Tract \"F-2\" of the record plat of \"WILDBLUE PHASE 2\", recorded in Instrument No. 2018000070231, of the Public Records of Lee County, Florida, lying in Section 19, Township 46 South, Range 26 East, Lee County, Florida, said tract or parcel of land being more particularly described as follows:\n\nCommencing at the Southerly Most corner of said Tract \"F-2\" run N89°22'06\"E along the South line of said Tract \"F-2\", also being the South line of the Southeast Quarter (SE 1/4) of said Section 19 for 928.83 feet and the POINT OF BEGINNING.\n\nFrom said Point of Beginning run N06°37'54\"W for 423.47 feet to a point of curvature; thence run Northeasterly along an arc of a curve to the right of radius 50.00 feet (delta 90°00'00\") (chord bearing N44°22'06\"E) (chord 70.71 feet) for 78.54 feet to a point of tangency; thence run N89°22'06\"E for 286.01 feet; thence run N35°20'54\"E for 249.64 feet to a point on a non-tangent curve; thence run Southeasterly along an arc of a curve to the left of radius 1,045.00 feet (delta 00°32'07\") (chord bearing S58°06'32\"E) (chord 9.76 feet) for 9.76 feet to a point of tangency; thence run S58°22'36\"E for 63.70 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 355.00 feet (delta 22°27'53\") (chord bearing S47°08'39\"E) (chord 138.30 feet) for 139.19 feet to a point of compound curvature; thence run Southeasterly along an arc of a curve to the right of radius 655.00 feet (delta 07°41'45\") (chord bearing S32°03'51\"E) (chord 87.91 feet) for 87.98 feet to a point of tangency; thence run S28°12'58\"E for 102.80 feet; thence run N61°47'02\"E for 21.00 feet to a point of curvature; thence run Easterly along an arc of a curve to the right of radius 21.00 feet (delta 90°00'00\") (chord bearing S73°12'58\"E) (chord 29.70 feet) for 32.99 feet to a point of tangency; thence run S28°2'58\"E for 295.65 feet to a point of curvature; thence run Southeasterly along an arc of a curve to the right of radius 36.00 feet (delta 11°46'38\") (chord bearing S22°19'39\"E) (chord 7.39 feet) for 7.40 feet to an intersection with the Northerly right of way line of Corkscrew Road, Parcel 102A, as described in a deed recorded in Instrument No. 2008000174785, Lee County Records; thence run S61°47'02\"W along said Northerly right of way line for 230.77 feet to an intersection with said South line of the Southeast Quarter (SE 1/4) of Section 19; thence run S89°22'06\"W along said the South line for 720.61 feet to the POINT OF BEGINNING.\n\nContaining 9.81 acres, more or less.\n\nDESCRIPTION (CONTINUED)\n\nNet area is 2,352.08 acres, more or less.\n\nBearings hereinabove mentioned are State Plane for the Florida West Zone (1983/NSRS 2007) and are based on the East line of the Southeast Quarter (SE 1/4) of said Section 8 to bear S01°05'07\"E.\n\nScott A. Wheeler (For The Firm)\nProfessional Surveyor and Mapper\nFlorida Certificate No. 5949\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n10A\n\nCONTRACT\nWILDBLUE Lake Maintenance agreement\n\nTHIS AGREEMENT, made and entered into this 14 day of March 2019, by and between Solitude Lake Management, with an address of 3482 Ironbridge Blvd, Unit 2; Fort Myers, FL 33916; (hereinafter “Contractor”) and the Wildblue Community Development District, a community development district established pursuant to Chapter 190, Florida Statutes, with an address 9220 Bonita Beach Road, suite 214; Bonita springs, FL 34135 (hereinafter the “District”)\n\nWHEREAS, the District solicited proposals for Lake maintenance services and as more specifically outlined in Exhibits “A” and “B” (hereinafter referred to as the “work”) and,\n\nWHEREAS, Contractor has represented to the District that Contractor possesses all of the necessary licenses, skill, knowledge, expertise, equipment and personnel necessary to competently perform and complete the work; and,\n\nWHEREAS, Contractor has represented to the District that Contractor has reviewed the work and is aware of and knowledgeable as to the conditions and has based its proposal thereon.\n\nNOW THEREFORE, for and in consideration of the premises, the terms, conditions and representations contained herein, and for other good and valuable consideration Contractor and the District agree as follows:\n\n1. The above and foregoing are true and correct.\n\n2. Contractor will supply all equipment, materials, labor and expertise necessary to perform the work and as more specifically depicted on the attached Exhibits \"A\" and \"B\",\n\n3. By the execution of this Agreement, it is agreed that Contractor will be performing professional services as an independent contractor and will not be subject to the control of the Owner as to the means and method of performance of the services, except as hereinafter noted with regard to authority to bind or obligate the Owner in performance of the services.\n\n4. The term of this agreement shall be effective commencing April 1, 2019 and shall have an initial term of 12 months ending March 31, 2020. Agreement may be extended for an additional one-year option.\n\n5. Payment Terms – Contractor shall submit an invoice, by the 10th of each month for work satisfactorily completed during the prior month. District shall process payment within 30 days of receipt of invoice.\n\n6. Within three (3) days of the date of execution of this Agreement, Contractor shall furnish District with Certificates of Workers Compensation, General Liability and vehicle policy limits, as follows:\n\nA. Commercial General Liability: Coverage shall have minimum limits of $1,000,000 Per Occurrence, Combined Single Limit for Bodily Injury Liability and Property Damage Liability. This shall include Premises and Operations; Independent Managers; Products and Completed Operations and Contractual Liability.\n\nB. Workers’ Compensation: Insurance covering all employees meeting Statutory Limits in compliance with the applicable state and federal laws.\n\nThe coverage must include Employers’ Liability with a minimum limit of $1,000,000 for each accident.\n\nCurrent, valid insurance policies meeting the requirement herein identified shall be maintained by Contractor during the duration of this Agreement. There shall be a thirty (30) day written notification to District in the event of cancellation or modification of any insurance coverage. The District shall be listed as the Certificate Holder and included as an Additional Insured on the Comprehensive General Liability Policy, and Contractor shall have the insurance carriers deliver copies of such Certificate(s) to the District.\n\n7. Contractor shall defend at its cost and expense and shall indemnify and hold harmless the District and all of its agents, attorneys and employees from and against all liability, claims, demands, losses and expenses, including reasonable attorney’s fees arising out of, or resulting from the performance of work under this Contract, or failure to comply with the terms of this contract, or is caused in whole or in part by any negligent act or omission of Contractor or anyone directly or indirectly employed by Contractor or anyone for whose acts Contractor may be liable, regardless of whether it is caused in part by a party indemnified hereunder or by the negligence of the District. Each of the indemnities given by the Contractor herein and elsewhere in the Contract Documents, is given in consideration of the first $100.00 of the Contract sum, as well as other good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged by Contractor.\n\n8. This Contract and work may not be assigned by Contractor without the express prior written approval of the District, which approval may be withheld in the sole discretion of the District.\n\n9. Contract may be terminated by either party with 30 days written notice without cause and by the District immediately with cause. In the event of termination the Contractor shall be entitled payment for costs incurred to date of termination.\n\n10. The District shall have the right to unilaterally cancel the Contract for refusal by Contractor to allow public access to all documents, papers, letters, or other materials subject to the provisions of Chapter 119, F.S. and made or received by the Contractor in conjunction with the Contract.\n\nContractor agrees to comply with Florida’s public records laws, specifically to:\n\n(a) Keep and maintain public records that ordinarily and necessarily would be required by the District in order to perform the service.\n\n(b) Provide the public with access to public records on the same terms and conditions that the District would provide the records and at a cost that does not exceed the cost provided in this chapter or as otherwise provided by law.\n\n(c) Ensure that public records that are exempt or confidential and exempt from public records disclosure requirements are not disclosed except as authorized by law.\n\n(d) Meet all requirements for retaining public records and transfer, at no cost, to the District all public records in possession of Contractor upon termination of the contract and destroy any duplicate public records that are exempt or confidential and exempt from public records disclosure requirements. All records stored electronically must be provided to the District in a format that is compatible with the information technology systems of the District.\n\n(e) IF CONTRACTOR HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119, FLORIDA STATUTES, TO THE CONTRACTOR’S DUTY TO PROVIDE PUBLIC RECORDS RELATING TO THIS CONTRACT, CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT (561) 571-0010 OR AT firstname.lastname@example.org OR BY MAIL AT 2300 GLADES ROAD SUITE 410W; BOCA RATON, FL 33431\n\n11. Contractor shall perform all work in strict compliance with all applicable statutes, rules, laws, ordinances and regulations.\n\n12. Unless a contract between Contractor and any subcontractor provides otherwise, the provisions of Section 287.0585, F.S. shall apply as to late payments by Contractor to subcontractors.\n\n13. Contractor shall pay all subcontractors, sub-subcontractors, materialmen and suppliers in accordance with the provisions of Section 255.001, F.S..\n\n14. Contractor warrants and certifies to the District that neither Contractor nor any affiliate of Contractor have been convicted of a public entity crime as such is defined in Section 287.133, F.S.\n\n15. Contractor warrants that Contractor has not employed or retained any company of person, other than a bona fide employee working solely for Contractor to solicit or secure this agreement and that Contractor has not\n\npaid or agreed to pay any person, company, corporation, individual, or firm, other than a bona fide employee working solely for Contractor any fee, commission, percentage, gift or other consideration contingent upon or resulting from the award of this agreement.\n\n16. Venue and jurisdiction for any litigation arising out of this agreement shall be in the state court of appropriate jurisdiction in Lee County, Florida\n\nWITNESS\n\n[Signature]\n\nWILDBLUE COMMUNITY DEVELOPMENT\nDISTRICT\nBy: [Signature]\nTitle: MGR\n\nWITNESS\n\n[Signature]\n\nAs to Contractor:\nBy: [Signature]\nTitle: WILLIAM R. KURTH\nDirector of Lake Mgt., FL\n\nSCOPE OF WORK - The contractor shall furnish all labor, materials, supervision, equipment, supplies, tools, services, and all other necessary incidentals required to perform complete maintenance of water management areas as detailed below.\n\nEXISTING FACILITIES\n\nExhibit “B” is a map showing the locations to be maintained by this contract.\n\nDETAILED SPECIFICATIONS\n\n1. General.\n\nWork under this section includes furnishing all labor, supplies, equipment and materials, and performing all operations connected with the completion of required water management areas maintenance, monitoring of area ponds, Conservations and dry detention areas as depicted within Exhibits “A”, the size and locations of which shall be independently verified by Contractor.\n\n- The aquatic weed control program includes the mechanical removal or spraying of water management areas, as designated in Exhibit “A” accompanying this specification. These operations are for the removal of water hyacinths, cattails, broadleaf weeds grasses, torpedo grass, Hydrilla, Bull Rush, Thalia and other noxious or invasive weeds, including bottom rooted aquatic weeds that are unsightly or may impede the flow of water in the lakes, flow ways and dry detention areas.\n\n- Algae is an ongoing problem and will be treated accordingly to District satisfaction as well as the aquatics mentioned above.\n\n- Aquatic weeds mentioned above shall occupy no more than 1% of any lake or dry detention area at any one time. Noxious plants are defined as any water borne plant that will, if not managed properly through chemical or mechanical means, over take the desirable aquatic plants causing an unbalance of the waterway ecology system.\n\n- All non-beneficial & invasive lake bank grasses and weeds, including torpedo grass, will be controlled from the water bodies current water’s edge into the water body or dry detention area during all times of the year.\n\n- Hydrilla, bladderwort, coontail, chara and other matting type aquatic plants shall be treated or removed immediately upon identification in the water body, either on the surface or below it.\n\n- The Contractor is required to make, at minimum, weekly visits to the site to insure the success of the Aquatic Weed Control Program. The Contractor shall make such additional site visits as required by the District to treat the District's Water Management System. Required additional visits shall be made within 24 hours of request from the Districts Resident Project Representative.\n\n2. **Littoral Zone Maintenance.**\n\nThe Contractor will remove weeds, exotics and other nuisance vegetation from littoral zones. Additionally, these same weeds will be removed below the water level around the perimeters of the lakes, flow ways and dry detention areas as noted within Exhibit “A”. However, beneficial and \"attractive\" plant species should be allowed to develop in these shelves, pond banks and dry detention areas. The Contractor will discuss with the District which species should be removed and which should be retained.\n\n3. **Miscellaneous Requirements.**\n\n- The Contractor shall use only approved chemicals and methods. In the event a chemical or method is banned by a governing agency in the State of Florida, or the Federal Government, during the term of the contract, the Contractor shall continue work using other approved chemicals or methods.\n\n- All weeds removed by physical or mechanical means shall be hauled away and shall be disposed off-site by the Contractor, unless otherwise arranged.\n\n- The Contractor shall use due care to avoid damage to adjacent lawns and shrubbery. The rate of application of chemicals shall be limited to avoid fish kills and unnecessary impacts to non-weedy or desirable wetland vegetation.\n\n- The Contractor will make sure that nuisance aquatic vegetation is removed from all equipment prior to entry into ponds to preclude introduction of the weeds into other ponds.\n\n- Trash and other foreign debris will be removed from each pond and mitigation area on at least a bi-weekly basis.\n\n4. **Reports.**\n\nThe Contractor shall mail or email to the District, after each treatment, a report indicating the water management areas treated, chemicals used, condition of weed growth, number of men on the job site, and a summary of all agency required activities within mitigation areas.\n\n5. **Tools, Plants and Equipment.**\n\nIf at any time before the commencement or during the progress of the work, the equipment appears to the District to be insufficient, inefficient or inappropriate to secure the quality of work required, or the proper rate of progress, the District may order the Contractor to increase their efficiency, to improve the character, to augment their number or substitute new equipment, as the case may be, and the Contractor shall conform to such order; the failure of the District to demand such increase of efficiency shall not relieve the Contractor of his obligation to secure the quality of work and the rate of progress necessary to complete the work within the time required by the contract and to the satisfaction of the District.\n\n6. **Acceptance of Finished Work.**\n\nAs needed, the District will make final inspection of the work covered by this contract when it is completed monthly.\n\nANNUAL POND MANAGEMENT CONTRACT\n\nPROPERTY NAME: Wild Blue\nCONTRACT TERM: April 1st, 2019 to March 31st, 2020\nSUBMITTED TO: Chuck Adams #239-464-7114 email@example.com\nSUBMITTED BY: Jeff Moding\nSPECIFICATIONS: Lake Management for Two Lakes approximately 655.55 Acres\n\nVisual Inspections:\n1. Contractor will perform a visual inspection of the pond(s) during each visit to the site. The inspections shall include the following:\n - Water levels\n - Water clarity or quality\n - Beneficial Aquatic Vegetation\n - Nuisance, Invasive, or Exotic Aquatic Vegetation\n - Algae\n - Erosion\n - Issues with shoreline and bank stabilization measures such as rip rap stone, bulkheads, retaining walls, etc.\n - Mosquito breeding conditions and habitat\n - Trash and debris\n\nPond Aquatic Weed Control:\n1. Pond(s) will be inspected on a four (4) times per month basis.\n2. Any growth of undesirable aquatic weeds and vegetation found in the pond(s) with each inspection shall be treated and controlled through the application of aquatic herbicides and aquatic surfactants as required to control the specific varieties of aquatic weeds and vegetation found in the pond(s) at the time of application.\n3. Invasive and unwanted submersed and floating vegetation will be treated and controlled preventatively and curatively each spring and early summer through the use of systemic herbicides at the rate appropriate for control of the target species. Application rates will be designed to allow for selective control of unwanted species while allowing for desirable species of submersed and emergent wetland plants to prosper.\n\nCompetitively Sensitive & Proprietary Materials – The information contained herein is the intellectual property of SOLitude Lake Management. Recipient may not disclose to any outside party any proprietary information, processes, or pricing contained in this document or any of its attachments without the prior written consent of SOLitude Lake Management. This document is provided to the recipient in good faith and it shall be the responsibility of the recipient to keep the information contained herein confidential.\n\nShoreline Aquatic Weed Control:\n1. Shoreline areas will be inspected on a four (4) times per month basis.\n2. Any growth of cattails, phragmites, or other unwanted shoreline vegetation found within the pond areas shall be treated and controlled through the application of aquatic herbicides and aquatic surfactants as required for control of the plants present at time of application.\n3. Any growth of unwanted plants or weeds growing in areas where stone has been installed for bank stabilization and erosion control shall be treated and controlled through the application of aquatic herbicides and aquatic surfactants as required to control the unwanted growth present at the time of application.\n\nWater Quality Monitoring:\n1. Pond water samples will be taken and tested one (1) per year for the following parameters:\n - Temperature\n - Dissolved Oxygen\n - pH\nThe results of the tests along with recommendations and analysis of the results will be provided to the client in a written report following each testing period.\n\nAny data collected that needs immediate action to resolve an issue will be brought to the client’s attention at once.\n\nPond Algae Control:\n1. Pond(s) will be inspected on a four (4) times per month basis.\n2. Any algae found in the pond(s) with each inspection shall be treated and controlled through the application of algaecides, aquatic herbicides, and aquatic surfactants as needed for control of the algae present at the time of service.\n\nTrash Removal:\n1. Trash and light debris will be removed from the pond(s) with each service and disposed off site. Any large item or debris that is not easily and reasonably removable by one person during the routine visit will be removed with the client’s approval for an additional fee. Routine trash and debris removal services are for the pond areas only, and do not include any trash or debris removal from the surrounding terrestrial (dry land) areas.\n\nPermitting:\n\n1. SOLitude staff will not be responsible for the following:\n a. Obtaining any Federal, state, or local permits required to perform any work specified in this contract where applicable.\n b. Attending any public hearings or meetings with regulators as required in support of the permitting process.\n c. Filing of any notices or year-end reports with the appropriate agency as required by any related permit.\n d. Notifying the client of any restrictions or special conditions put on the site with respect to any permit received, where applicable.\n\nClient Responsibilities:\n\n1. Client will be responsible for the following:\n a. Providing information required for the permit application process upon request.\n b. Providing Certified Abutters List for abutter notification where required.\n c. Perform any public filings or recordings with any agency or commission associated with the permitting process, if required.\n d. Compliance with any Order of Conditions or other special requirements or conditions required by the local municipality.\n e. Compliance and enforcement of temporary water-use restrictions where applicable.\n\nService Reporting:\n\n1. Client will be provided with a monthly service report detailing all of the work performed as part of this contract.\n\nGeneral:\n\n1. Contractor is a licensed pesticide applicator in the state in which service is to be provided.\n2. Individual Applicators are Certified Pesticide Applicators in Aquatics, Public Health, Forestry, Right of Way, and Turf/Ornamental as required in the state in which service is to be provided.\n3. Contractor is a SePRO Preferred Applicator and dedicated Steward of Water. Each individual applicator has been trained and educated in the water quality testing and analysis required for site specific water quality management prescriptions and utilizes an integrated approach that encompasses all aspects of ecologically balanced management. Each applicator has received extensive training in the proper selection, use, and application of all aquatic herbicides, algaecides, adjuvants, and water quality enhancement products necessary to properly treat our clients’ lakes and ponds as part of an overall integrated pest management program.\n\nCompetitively Sensitive & Proprietary Materials – The information contained herein is the intellectual property of SOLitude Lake Management. Recipient may not disclose to any outside party any proprietary information, processes, or pricing contained in this document or any of its attachments without the prior written consent of SOLitude Lake Management. This document is provided to the recipient in good faith and it shall be the responsibility of the recipient to keep the information contained herein confidential.\n\n4. Contractor guarantees that all products used for treatment are EPA registered and labeled as appropriate and safe for use in lakes, ponds, and other aquatic sites, and are being applied in a manner consistent with their labeling.\n\n5. All pesticide applications made directly to the water or along the shoreline for the control of algae, aquatic weeds, or other aquatic pests as specified in this contract will meet or exceed all of the contractor’s legal regulatory requirements as set forth by the EPA and related state agencies for NPDES and FIFRA. Contractor will perform treatments that are consistent with NPDES compliance standards as applicable in and determined by the specific state in which treatments are made. All staff will be fully trained to perform all applications in compliance with all federal, state, and local law.\n\n6. Contractor will furnish personnel, equipment, boats, materials, and other items required to provide the foregoing at his expense.\n\n7. Contractor will maintain general liability and workman’s compensation insurance.\n\n8. Client understands and acknowledges that there are irrigation restrictions associated with many of the products used to treat their ponds. The client is responsible for notifying the contractor in advance of the contract signing and the start of the contract treatment if they utilize any of the water in their ponds for irrigation purposes. The client accepts full responsibility for any issues that may arise from the irrigation of turf, ornamentals, trees, crops, or any other plants as a result of treated water being used by the client for irrigation without the consent or knowledge of the contractor.\n\n9. Although there is rarely direct fish toxicity with the products used for treatment when applied at the labeled rate, any time there is an extreme infestation of algae and aquatic weeds, there is a risk of dissolved oxygen drops as a result of large masses of algae and aquatic weeds dying and decomposing simultaneously. This risk is most severe in times of extremely hot weather and warm water temperatures, as these are the conditions during which dissolved oxygen levels are naturally at their lowest levels. Often ponds will experience natural fish kills under these conditions even if no treatment is performed. Every effort, to include the method and timing of application, the choice of products, and the skill and training of the applicators is made to avoid such problems. This risk is especially mitigated by the use of systemic herbicides wherever possible, which results in a very slow steady control of the target weed species. However, the client understands and accepts that there is always a slight risk of the occurrence of adverse conditions outside the control of the contractor that will result in the death of some fish and other aquatic life. The client also understands and accepts that similar risks would remain if the algae or submerged invasive vegetation present in the pond goes uncontrolled, as it will over time interfere with the health and wellbeing of the existing fish population. The client agrees to hold the contractor harmless for any issues with fish or other aquatic life which occur as described above or are otherwise outside the direct control of the contractor, unless there is willful negligence on the part of the contractor.\n\n10. Contractor shall be reimbursed by the client for any non-routine expenses, administrative fees, compliance fees, or any other similar expense that are incurred.\n\nas a result of requirements placed on the contractor by the client that are not covered specifically by the written specifications of this contract.\n\n11. The term of this agreement is for a period of twelve (12) months, with payment to be made in twelve (12) equal monthly payments due by the last day of each month. As a courtesy, the client will be invoiced on the first day of each month, reminding them that a contract payment is due by the end of that same month. The client is obligated to pay each monthly contract payment per the terms of this contract, without any obligation on the part of the contractor to invoice or send any other sort of reminder or notice. The Annual Contract Price is based on the total value of services to be provided over a period of twelve (12) months. For the convenience of the client, we offer Monthly Contract Pricing that is simply an even twelve (12) month amortization of the Annual Contract Price. Due to the seasonality of these services, and the disproportionate amount of time and materials dedicated to providing these services during some times of the year as compared to others, based on the season, weather patterns, and other natural factors, the amount billed and paid to date is not necessarily equivalent to the amount of work performed to date.\n\n12. Contract will automatically renew annually at the end of the contract period for subsequent one (1) year terms, with a three percent (3%) escalation in the Annual Contract Price and Additional Enhancements each year, under the same terms, specifications, and conditions as set forth by this contract, unless either party gives written notice of cancellation thirty (30) days prior to the termination date of this contract, or subsequent renewal contracts.\n\n13. The client agrees to pay penalties and interest in the amount of 2% per month for all past due invoices and related account balances in excess of 30 days past due from the due date as specified by the contract and as stated on the relevant invoice presented to the client.\n\n14. The client covenants and agrees to pay reasonable attorney’s fees and all other related costs and expenses of SOLitude Lake Management® for collection of past due invoices and account balances and for any other actions required to remedy a material breach of this contract.\n\nCONTRACT PRICE: $18,500.00 Annual\n$1541.66 Monthly for twelve (12) months\n\nAPPROVED:\n\nSOLitude Lake Management®\n\nWild Blue\n\n(Authorized Client Signature)\n\n(Print Name and Title)\n\n(Date)\n\nThe Stewards of Water\n\nCompetitively Sensitive & Proprietary Materials – The information contained herein is the intellectual property of SOLitude Lake Management. Recipient may not disclose to any outside party any proprietary information, processes, or pricing contained in this document or any of its attachments without the prior written consent of SOLitude Lake Management. This document is provided to the recipient in good faith and it shall be the responsibility of the recipient to keep the information contained herein confidential.\n\n3842 Ironbridge Blvd, Unit #2, Fort Myers, FL 33916 | 888.480.LAKE (5253) | SOLITUDELAKEMANAGEMENT.COM\n\n| Lake ID | Annual Cost | Monthly Cost |\n|----------|--------------|--------------|\n| North Lake | $12,500.00 | $1,041.66 |\n| South Lake | $6,000.00 | $500.00 |\n\n**Future**\n\n| Lake ID | Annual Cost | Monthly Cost |\n|---------|-------------|--------------|\n| A-1 | | |\n| A-2 | | |\n| B-1 | | |\n| C-1 | | |\n| C-2 | | |\n| C-3 | | |\n| E-1 | | |\n| F-1 | | |\n| G-1 | | |\n| G-2 | | |\n| G-3 | | |\n| H-1 | | |\n| H-2 | | |\n| H-4 | | |\n\nEXHIBIT 'B'\n\nCERTIFICATE OF LIABILITY INSURANCE\n\nTHIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFER NO RIGHTS UPON THE CERTIFICATE HOLDER. THIS CERTIFICATE DOES NOT AFFIRMATIVELY OR NEGATIVELY AMEND, EXTEND OR ALTER THE COVERAGE AFFORDED BY THE POLICIES BELOW. THIS CERTIFICATE OF INSURANCE DOES NOT CONSTITUTE A CONTRACT BETWEEN THE ISSUING INSURER(S), AUTHORIZED REPRESENTATIVE OR PRODUCER, AND THE CERTIFICATE HOLDER.\n\nIMPORTANT: If the certificate holder is an ADDITIONAL INSURED, the policy(ies) must have ADDITIONAL INSURED provisions or be endorsed. IF SUBROGATION IS WAIVED, subject to the terms and conditions of the policy, certain policies may require an endorsement. A statement on this certificate does not confer rights to the certificate holder in lieu of such endorsement(s).\n\n| PRODUCER | 1-404-439-8000 |\n| --- | --- |\n| Integro USA Inc. | Certificates Atlanta |\n| dba Integro Insurance Brokers | PHONE (A/C No.): 404-439-8000 |\n| 200 Glenridge Point Parkway | FAX (A/C No.): 404-439-8001 |\n| Suite 400 | E-MAIL: firstname.lastname@example.org |\n| Atlanta, GA 30342 | ADDRESS: |\n| INSURED | INSURER(S) AFFORDING COVERAGE | NAIC # |\n| SOLITUDE LAKE MANAGEMENT, LLC | INSURER A: ACE AMER INS CO | 22667 |\n| RENTOKIL NORTH AMERICA, INC. (REN475) | INSURER B: OLD REPUBLIC INS CO | 24147 |\n| 1320 BROOKWOOD DR. STE H | INSURER C: ACE PROP & CAS INS CO | 20699 |\n| LITTLE ROCK, AR 72202-1412 | INSURER D: ZURICH AMER INS CO | 16535 |\n| | INSURER E: | |\n| | INSURER F: | |\n\nCOVERAGES\n\nCERTIFICATE NUMBER: 55662231\n\nREVISION NUMBER:\n\nTHIS IS TO CERTIFY THAT THE POLICIES OF INSURANCE LISTED BELOW HAVE BEEN ISSUED TO THE INSURED NAMED ABOVE FOR THE POLICY PERIOD INDICATED. NOTWITHSTANDING ANY REQUIREMENT, TERM OR CONDITION OF ANY CONTRACT OR OTHER DOCUMENT WITH RESPECT TO WHICH THIS CERTIFICATE MAY BE ISSUED OR MAY PERTAIN, THE INSURANCE AFFORDED BY THE POLICIES DESCRIBED HEREIN IS SUBJECT TO ALL THE TERMS, EXCLUSIONS AND CONDITIONS OF SUCH POLICIES. LIMITS SHOWN MAY HAVE BEEN REDUCED BY PAID CLAIMS.\n\n| INSUR LTR | TYPE OF INSURANCE | ADD'L INS'D W/D | POLICY NUMBER | POLICY EFF (MM/DD/YYYY) | POLICY EXP (MM/DD/YYYY) | LIMITS |\n| --- | --- | --- | --- | --- | --- | --- |\n| A | COMMERCIAL GENERAL LIABILITY | X | OGLG27240331 | 10/01/18 | 10/01/19 | EACH OCCURRENCE $5,000,000 |\n| | CLAIMS-MADE | X | OCCUR | DAMAGE TO RENTED PREMISES (Ea occurrence) $5,000,000 |\n| | GEN'L AGGREGATE LIMIT APPLIES PER: | | | MED EXP (Any one person) $5,000 |\n| | POLICY | X | PROJECT | PERSONAL & ADV INJURY $5,000,000 |\n| | LOC | | | GENERAL AGGREGATE $5,000,000 |\n| | PRODUCTS - COMP/OP AGG | | | $5,000,000 |\n| | OTHER: | | | $ |\n| B | AUTOMOBILE LIABILITY | | MWTB314124 | 10/01/18 | 10/01/19 | COMBINED SINGLE LIMIT (Ea accident) $2,000,000 |\n| | ANY AUTO | | | BODILY INJURY (Per person) $ |\n| | OWNED AUTOS ONLY | | | BODILY INJURY (Per accident) $ |\n| | HIRED AUTOS ONLY | | | PROPERTY DAMAGE (Per accident) $ |\n| | SCHEDULED AUTOS | | | |\n| | NON-OWNED AUTOS ONLY | | | |\n| C | UMBRELLA LIAB | X | XOOG27239420 | 10/01/18 | 10/01/19 | EACH OCCURRENCE $5,000,000 |\n| | EXCESS LIAB | | | AGGREGATE $5,000,000 |\n| | DED | RETENTIONS 10,000 | | | $ |\n| B | WORKERS COMPENSATION AND EMPLOYERS' LIABILITY | Y/N | MWC314123 | 10/01/18 | 10/01/19 | X PER STATUTE | OTH-ER |\n| | ANY PROPRIETOR/PARTNER/EXECUTIVE OFFICER/MEMBER EXCLUDED? (Mandatory for NH) | N | | E.L. EACH ACCIDENT $2,000,000 |\n| | If yes, describe under DESCRIPTION OF OPERATIONS below | | | E.L. DISEASE - EA EMPLOYEE $2,000,000 |\n| | | | | E.L. DISEASE - POLICY LIMIT $2,000,000 |\n| D | Crime/Client Coverage | | CRM015168301 | 10/01/18 | 10/01/19 | Limit 1,000,000 |\n\nDESCRIPTION OF OPERATIONS / LOCATIONS / VEHICLES (ACORD 101, Additional Remarks Schedule, may be attached if more space is required)\n\nCERTIFICATE HOLDER\n\nWildblue CDD\n\n9220 Bonita Beach Road, Suite 214\nBonita Springs, FL 34135\n\nUSA\n\nCANCELLATION\n\nSHOULD ANY OF THE ABOVE DESCRIBED POLICIES BE CANCELLED BEFORE THE EXPIRATION DATE THEREOF, NOTICE WILL BE DELIVERED IN ACCORDANCE WITH THE POLICY PROVISIONS.\n\nAUTHORIZED REPRESENTATIVE\n\n© 1988-2015 ACORD CORPORATION. All rights reserved.\n\nCERTIFICATE OF INSURANCE – PUBLIC AND PRODUCTS LIABILITY\n\nThis is to certify that a policy of insurance as described below has been issued to the Policyholder and the coverage thereby is as follows:-\n\n| THE INSURED | Rentokil Initial Plc and Subsidiary Companies |\n|-----------------------------|-----------------------------------------------|\n| CERTIFICATE HOLDER | Rentokil North America Inc |\n| POLICY NUMBER | UKCAIC75338 |\n| TYPE OF INSURANCE | Public & Products Liability |\n| THE COMPANY | Chubb European Group Ltd |\n| PERIOD OF INDEMNITY | 1st October 2018 to 30th September 2019 both days inclusive LST |\n| LIMIT OF LIABILITY | Professional Indemnity Liability USD1,000,000 any one occurrence and in the annual aggregate |\n\nNothing herein contained shall in any way be held or construed to vary alter or waive any of the terms conditions or provisions of the Policy.\n\nSigned for and on behalf of the Company\n\nChubb European Group SE\n31st August 2018\n\nTHE POLICY DOCUMENT IS ONLY SUMMARISED BY THIS CERTIFICATE FOR FULL INFORMATION REFER TO THE POLICY\n\n**Request for Taxpayer Identification Number and Certification**\n\nGo to [www.irs.gov/FormW9](http://www.irs.gov/FormW9) for instructions and the latest information.\n\nGive Form to the requester. Do not send to the IRS.\n\n| 1 | Name (as shown on your income tax return). Name is required on this line; do not leave this line blank. |\n|---|---|\n| Solitude Lake Management LLC |\n\n| 2 | Business name/disregarded entity name, if different from above |\n|---|---|\n| |\n\n| 3 | Check appropriate box for federal tax classification of the person whose name is entered on line 1. Check only one of the following seven boxes. |\n|---|---|\n| □ Individual/sole proprietor or single-member LLC | □ C Corporation | □ S Corporation | □ Partnership | □ Trust/estate |\n\n| 4 | Exemptions (codes apply only to certain entities, not individuals; see Instructions on page 3): |\n|---|---|\n| Exempt payee code (if any) | N/A |\n| Exemption from FATCA reporting code (if any) | N/A |\n\n| 5 | Address (number, street, and apt. or suite no.) See Instructions. |\n|---|---|\n| 1320 Brookwood Drive, Suite H |\n\n| 6 | City, state, and ZIP code |\n|---|---|\n| Little Rock, AR 72202 |\n\n| 7 | List account number(s) here (optional) |\n\n**Part I Taxpayer Identification Number (TIN)**\n\nEnter your TIN in the appropriate box. The TIN provided must match the name given on line 1 to avoid backup withholding. For individuals, this is generally your social security number (SSN). However, for a resident alien, sole proprietor, or disregarded entity, see the instructions for Part I, later. For other entities, it is your employer identification number (EIN). If you do not have a number, see How to get a TIN, later.\n\nNote: If the account is in more than one name, see the instructions for line 1. Also see What Name and Number To Give the Requester for guidelines on whose number to enter.\n\n| Social security number |\n|---|\n| - - |\n\nOR\n\n| Employer identification number |\n|---|\n| 5 4 - 1 9 4 0 1 1 0 |\n\n**Part II Certification**\n\nUnder penalties of perjury, I certify that:\n\n1. The number shown on this form is my correct taxpayer identification number (or I am waiting for a number to be issued to me); and\n2. I am not subject to backup withholding because: (a) I am exempt from backup withholding, or (b) I have not been notified by the Internal Revenue Service (IRS) that I am subject to backup withholding as a result of a failure to report all interest or dividends, or (c) the IRS has notified me that I am no longer subject to backup withholding; and\n3. I am a U.S. citizen or other U.S. person (defined below); and\n4. The FATCA code(s) entered on this form (if any) indicating that I am exempt from FATCA reporting is correct.\n\nCertification Instructions. You must cross out item 2 above if you have been notified by the IRS that you are currently subject to backup withholding because you have failed to report all interest and dividends on your tax return. For real estate transactions, item 2 does not apply. For mortgage interest paid, acquisition or abandonment of secured property, cancellation of debt, contributions to an individual retirement arrangement (IRA), and generally, payments other than interest and dividends, you are not required to sign the certification, but you must provide your correct TIN. See the instructions for Part II, later.\n\nSign Here\n\nSignature of U.S. person\n\nDate\n\n---\n\n**General Instructions**\n\nSection references are to the Internal Revenue Code unless otherwise noted.\n\nFuture developments. For the latest information about developments related to Form W-9 and its instructions, such as legislation enacted after they were published, go to [www.irs.gov/FormW9](http://www.irs.gov/FormW9).\n\n**Purpose of Form**\n\nAn individual or entity (Form W-9 requester) who is required to file an information return with the IRS must obtain your correct taxpayer identification number (TIN) which may be your social security number (SSN), individual taxpayer identification number (ITIN), adoption taxpayer identification number (ATIN), or employer identification number (EIN), to report on an information return the amount paid to you, or other amount reportable on an information return. Examples of information returns include, but are not limited to, the following:\n\n- Form 1099-INT (interest earned or paid)\n- Form 1099-DIV (dividends, including those from stocks or mutual funds)\n- Form 1099-MISC (various types of income, prizes, awards, or gross proceeds)\n- Form 1099-B (stock or mutual fund sales and certain other transactions by brokers)\n- Form 1099-S (proceeds from real estate transactions)\n- Form 1099-K (merchant card and third party network transactions)\n- Form 1098 (home mortgage interest), 1098-E (student loan interest), 1098-T (tuition)\n- Form 1099-C (canceled debt)\n- Form 1099-A (acquisition or abandonment of secured property)\n\nUse Form W-9 only if you are a U.S. person (including a resident alien), to provide your correct TIN.\n\nIf you do not return Form W-9 to the requester with a TIN, you might be subject to backup withholding. See What Is backup withholding, later.\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n10B\n\n| Lake ID | Annual Cost | Monthly Cost |\n|---------|--------------|--------------|\n| North Lake | $12,500.00 | $1,041.66 |\n| South Lake | $6,000.00 | $500.00 |\n\n**Future**\n\n| Lake ID | Annual Cost | Monthly Cost |\n|---------|--------------|--------------|\n| A-1 | | |\n| A-2 | | |\n| B-1 | | |\n| C-1 | | |\n| C-2 | | |\n| C-3 | | |\n| E-1 | | |\n| F-1 | 5,922.96 | 493.58 |\n| G-1 | 2575.44 | 214.62 |\n| G-2 | 2071.56 | 172.63 |\n| G-3 | 2070.72 | 172.56 |\n| H-1 | 957.72 | 79.81 |\n| H-2 | 3374.16 | 281.18 |\n| H-4 | 2335.44 | 194.62 |\n| Initial clean | 1995.00 | |\n\n$21,303.00\n\n$39,803.00 Amended Total\n\n**Owner**\n\n[Signature]\n\n4-30-19\n\n**Contractor**\n\n[Signature]\n\n4-30-19\n\nALL OTHER TERMS AND CONDITIONS OF THIS CONTRACT REMAIN IN FULL FORCE AND EFFECT.\n\nPROPERTY NAME: Wild Blue\nCONTRACT DATE: Master Contract\nSUBMITTED TO: Chuck Adams #239-464-7114\nSUBMITTED BY: Jeff Moding\nSPECIFICATIONS: This document serves as an addendum to the previously executed Lake Maintenance Contract. The price indicated in this contract shall be billed in addition to the regular monthly invoice amount and shall renew with the same terms and for the same time period as the existing contract.\n\n7-Additional Lakes, F-1, G-1, G-2, G-3, H-1, H2 and H-4\n\nCONTRACT PRICE:\n$1995.00 Start-up\n$1609.00 Monthly for twelve (12) months\n$21,303.00 Total Annual\n\nAPPROVED:\n\n[Signature]\n(Authorized Signature)\n\n(Print Name and Title)\n\nWild Blue\n\n4.30.19\n\nCompetitively Sensitive & Proprietary Materials – The information contained herein is the intellectual property of SŌLitude Lake Management. Recipient may not disclose to any outside party any proprietary information, processes, or pricing contained in this document or any of its attachments without the prior written consent of SŌLitude Lake Management. This document is provided to the recipient in good faith and it shall be the responsibility of the recipient to keep the information contained herein confidential.\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n11\n\nSECOND AMENDMENT TO THE LAKE MAINTENANCE AGREEMENT BETWEEN WILDBLUE COMMUNITY DEVELOPMENT DISTRICT AND SOLITUDE LAKE MANAGEMENT, LLC\n\nTHIS SECOND AMENDMENT (the “Amendment”), dated ____________, 2019, provides additional terms related to that certain CONTRACT WILDBLUE Lake Maintenance Agreement (the “Agreement”), dated March 19, 2019, as amended May 1, 2019, by and between:\n\nWILDBLUE COMMUNITY DEVELOPMENT DISTRICT, a local unit of special-purpose government established pursuant to Chapter 190, Florida Statutes, being situated in Lee County, Florida, with a mailing address of c/o Wrathell, Hunt & Associates, LLC, 2300 Glades Road, Suite 410W, Boca Raton, Florida 33431 (the “District”); and\n\nSOLITUDE LAKE MANAGEMENT, LLC, a Virginia limited liability company with a mailing address of 3842 Ironbridge Blvd., Unit 2, Fort Myers, Florida 33916 (the “Contractor,” and collectively with the District, the “Parties”).\n\nSECTION 1. LIMITATIONS ON GOVERNMENTAL LIABILITY. Nothing in the Agreement shall be deemed as a waiver of immunity or limits of liability of the District beyond any statutory limited waiver of immunity or limits of liability which may have been adopted by the Florida Legislature in Section 768.28, Florida Statutes, or other statute, and nothing in the Agreement shall inure to the benefit of any third party for the purpose of allowing any claim which would otherwise be barred under the Doctrine of Sovereign Immunity or by operation of law.\n\nSECTION 2. ENFORCEMENT OF AGREEMENT. A default by either Party under the Agreement shall entitle the other party to all remedies available at law or in equity. In the event that either the District or the Contractor is required to enforce the Agreement by court proceedings or otherwise, then the prevailing Party shall be entitled to recover all fees and costs incurred, including reasonable attorneys’ fees and costs for trial, alternative dispute resolution, or appellate proceedings.\n\nSECTION 3. FINAL AGREEMENT. This Amendment, together with the Agreement, the amendment dated May 1, 2019, and such other amendments as may be executed from time to time, represents the entire understanding between the District and the Contractor.\n\n[SIGNATURES ON FOLLOWING PAGE]\n\nIN WITNESS WHEREOF, the Parties hereto have caused this Amendment to be executed the day and year first above written.\n\nWILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n__________________________________________\nBy: _______________________________________\n □ Chairperson\n □ Vice Chairperson\n\nSOLITUDE LAKE MANAGEMENT, LLC\n\n__________________________________________\nBy: _______________________________________\nIts: _______________________________________\nDate: _____________________________________\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n12\n\nWILDBLUE COMMUNITY DEVELOPMENT DISTRICT\nFINANCIAL STATEMENTS\nUNAUDITED\nJULY 31, 2019\n\n# WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n## BALANCE SHEET\n### GOVERNMENTAL FUNDS\n#### JULY 31, 2019\n\n| ASSETS | General Fund | Debt Service Fund | Capital Projects Fund | Total Governmental Funds |\n|--------|--------------|-------------------|-----------------------|--------------------------|\n| Cash | $5,643 | $- | $- | $5,643 |\n| Investments | | | | |\n| Reserve | - | 696,184 | - | 696,184 |\n| Construction | - | - | 22,033,931 | 22,033,931 |\n| Cost of issuance | - | 3,906 | - | 3,906 |\n| Undeposited funds | 19,421 | - | - | 19,421 |\n| Due from Landowner | 13,051 | - | - | 13,051 |\n| Due from general fund | - | 645 | - | 645 |\n| **Total assets** | **$38,115** | **$700,735** | **$22,033,931** | **$22,772,781** |\n\n| LIABILITIES AND FUND BALANCES | General Fund | Debt Service Fund | Capital Projects Fund | Total Governmental Funds |\n|-------------------------------|--------------|-------------------|-----------------------|--------------------------|\n| Liabilities: | | | | |\n| Accounts payable | $31,470 | $645 | $- | $32,115 |\n| Due to Developer | - | 49,052 | 3,580 | 52,632 |\n| Due to debt service fund | 645 | - | - | 645 |\n| Landowner advance | 6,000 | - | - | 6,000 |\n| **Total liabilities** | **$38,115** | **$49,697** | **$3,580** | **$91,392** |\n\n| DEFERRED INFLOWS OF RESOURCES | General Fund | Debt Service Fund | Capital Projects Fund | Total Governmental Funds |\n|--------------------------------|--------------|-------------------|-----------------------|--------------------------|\n| Deferred receipts | 13,051 | - | - | 13,051 |\n| **Total deferred inflows of resources** | **13,051** | **-** | **-** | **13,051** |\n\n| Fund balances: | General Fund | Debt Service Fund | Capital Projects Fund | Total Governmental Funds |\n|--------------------------------|--------------|-------------------|-----------------------|--------------------------|\n| Restricted for: | | | | |\n| Debt service | - | 651,038 | - | 651,038 |\n| Capital projects | - | - | 22,030,351 | 22,030,351 |\n| Unassigned | (13,051) | - | - | (13,051) |\n| **Total fund balances** | (13,051) | 651,038 | 22,030,351 | 22,668,338 |\n\n| Total liabilities, deferred inflows of resources and fund balances | General Fund | Debt Service Fund | Capital Projects Fund | Total Governmental Funds |\n|---------------------------------------------------------------------|--------------|-------------------|-----------------------|--------------------------|\n| $38,115 | $700,735 | $22,033,931 | $22,772,781 | |\n\n## WILDBLUE COMMUNITY DEVELOPMENT DISTRICT GENERAL FUND\n\n### STATEMENT OF REVENUES, EXPENDITURES, AND CHANGES IN FUND BALANCES FOR THE PERIOD ENDED JULY 31, 2019\n\n| REVENUES | Current Month | Year to Date | Budget | % of Budget |\n|----------|---------------|--------------|--------|-------------|\n| Landowner contribution | $38,339 | $99,476 | $95,275 | 104% |\n| **Total revenues** | $38,339 | $99,476 | $95,275 | 104% |\n\n### EXPENDITURES\n\n#### Professional & administrative\n\n| Item | Current Month | Year to Date | Budget | % of Budget |\n|------|---------------|--------------|--------|-------------|\n| Management/accounting/recording | 4,000 | 40,000 | 48,000 | 83% |\n| Legal | 566 | 8,218 | 20,000 | 41% |\n| Boundary amendment | 1,751 | 5,780 | - | N/A |\n| Boundary amendment petition filling fee | - | 15,000 | - | N/A |\n| Engineering | - | 15,198 | 4,000 | 380% |\n| Audit** | 3,500 | 3,500 | 5,500 | 64% |\n| Arbitrage rebate calculation** | - | - | 750 | 0% |\n| Dissemination agent* | - | - | 1,000 | 0% |\n| Trustee* | - | - | 6,500 | 0% |\n| Telephone | 17 | 166 | 200 | 83% |\n| Postage | - | 74 | 500 | 15% |\n| Printing & binding | 42 | 417 | 500 | 83% |\n| Legal advertising | - | 5,004 | 1,200 | 417% |\n| Annual special district fee | - | 175 | 175 | 100% |\n| Insurance | - | 5,000 | 5,500 | 91% |\n| Contingencies/bank charges | 23 | 256 | 500 | 51% |\n| Website maintenance | Hosting | - | 635 | 98% |\n| ADA compliance | - | 139 | 300 | 46% |\n| **Total professional & administrative** | 9,899 | 99,562 | 95,275 | 104% |\n\n#### Field operations\n\n| Item | Current Month | Year to Date | Budget | % of Budget |\n|------|---------------|--------------|--------|-------------|\n| Lake & pond maintenance | 3,151 | 12,989 | - | N/A |\n| **Total field operations** | 3,151 | 12,989 | - | N/A |\n| **Total expenditures** | 13,050 | 112,551 | 95,275 | 118% |\n\nExcess/(deficiency) of revenues over/(under) expenditures | 25,289 | (13,075) | - |\n\nFund balances - beginning | (38,340) | 24 | - |\nFund balances - ending | $(13,051) | $(13,051) | $- |\n\n* These items will be realized when bonds are issued\n** These items will be realized the year after the issuance of bonds.\n\n## WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n### STATEMENT OF REVENUES, EXPENDITURES, AND CHANGES IN FUND BALANCES\n\n#### DEBT SERVICE FUND\n\n**FOR THE PERIOD ENDED JULY 31, 2019**\n\n| | Current Month | Year To Date |\n|--------------------------------|---------------|--------------|\n| **REVENUES** | | |\n| Interest | $722 | $722 |\n| Total revenues | $722 | $722 |\n| **EXPENDITURES** | | |\n| Debt service | | |\n| Cost of issuance | - | 266,987 |\n| Underwriter's discount | - | 469,400 |\n| Original issue discount | - | 46,667 |\n| Total debt service | - | 783,054 |\n| Excess/(deficiency) of revenues over/(under) expenditures | 722 | (782,332) |\n\n| **OTHER FINANCING SOURCES/(USES)** | | |\n| Bond proceeds | - | 1,458,728 |\n| Total other financing sources | - | 1,458,728 |\n| Net change in fund balances | 722 | 676,396 |\n| Fund balances - beginning | 650,316 | (25,358) |\n| Fund balances - ending | $651,038 | $651,038 |\n\n## WILDBLUE COMMUNITY DEVELOPMENT DISTRICT\n\n### STATEMENT OF REVENUES, EXPENDITURES, AND CHANGES IN FUND BALANCES\n\n#### CAPITAL PROJECTS FUND\n\n**FOR THE PERIOD ENDED JULY 31, 2019**\n\n| | Current Month | Year To Date |\n|--------------------------------|---------------|--------------|\n| **REVENUES** | | |\n| Interest | $22,660 | $22,660 |\n| Total revenues | $22,660 | $22,660 |\n| **EXPENDITURES** | | |\n| Capital outlay | - | 3,150 |\n| Total expenditures | - | 3,150 |\n| Excess/(deficiency) of revenues over/(under) expenditures | 22,660 | 19,510 |\n| **OTHER FINANCING SOURCES/(USES)** | | |\n| Bond proceeds | - | 22,011,271 |\n| Total other financing sources/(uses) | - | 22,011,271 |\n| Net change in fund balances | 22,660 | 22,030,781 |\n| Fund balances - beginning | 22,007,691 | (430) |\n| Fund balances - ending | $22,030,351 | $22,030,351 |\n\nWILDBLUE\nCOMMUNITY DEVELOPMENT DISTRICT\n\n13\n\nThe Board of Supervisors of the WildBlue Community Development District held a Regular Meeting on June 6, 2019 at 10:00 a.m., at Barraco and Associates, 2271 McGregor Boulevard, Suite 100, Fort Myers, Florida 33901.\n\nPresent at the meeting were:\n\nRussell Smith Chair\nChristopher Hasty Vice Chair\nBarry Ernst Assistant Secretary\nChris Johnson Assistant Secretary\nDavid Caldwell Assistant Secretary\n\nAlso present were:\n\nCraig Wrathell District Manager\nCindy Cerbone Wrathell, Hunt and Associates, LLC\nLisa Dao Wrathell, Hunt and Associates, LLC\nJonathan Johnson District Counsel\nCarl Barraco District Engineer\nDarin McMurray Lennar\nAmanda Kumar US Bank\nCourtney Wilson Bond Counsel - Greenberg Traurig, P.A.\nPaul Milford Public\n\nFIRST ORDER OF BUSINESS Call to Order/Roll Call\n\nMr. Wrathell called the meeting to order at 10:00 a.m. All Supervisors were present, in person.\n\nSECOND ORDER OF BUSINESS Public Comments\n\nMr. Paul Milford, a resident of a neighborhood to the northeast of the CDD, discussed an email he sent regarding a proposed zoning change to a property approximately 2,000’ from the northeast corner of the CDD. A hearing was scheduled for June 12th at 1:00 p.m., to change\n\nthe zoning from agricultural to utilities, which could allow a 75’ tall waste transfer/holding facility and a hazardous waste drop off site. The facility would have a 100’ tall exhaust stack and a water treatment facility with an injection well. He expressed his concern for the property values, as the proposed facility and associated traffic would be unsightly and inconvenient.\n\nMr. Wrathell thanked Mr. Milford and stated the email was forwarded to Mr. Smith and Mr. Caldwell and the District Engineer would continue monitoring the situation.\n\nTHIRD ORDER OF BUSINESS\n\nUpdate: Boundary Amendment\n\nDistrict Counsel stated the public hearing on this matter was scheduled for 9:00 a.m., on the Lee County Commission’s July 18th agenda; the exact time would be determined that day.\n\nFOURTH ORDER OF BUSINESS\n\nConsideration of Resolution 2019-08, Approving Proposed Budget for Fiscal Year 2019/2020 and Setting a Public Hearing Thereon Pursuant to Florida Law; Addressing Transmittal, Posting and Publication Requirements; Addressing Severability; and Providing an Effective Date\n\nMr. Wrathell presented Resolution 2019-08. He reviewed the proposed Fiscal Year 2020 budget, including line item increases, decreases and adjustments, compared to the Fiscal Year 2019 budget, and assessments. The number of units assessed on roll would increase as properties are platted; necessary adjustments would be made before adoption of the budget.\n\nDiscussion ensued regarding the new Field Operations portion of the proposed Fiscal Year 2020 budget, which was not in the Fiscal Year 2019 budget. An interlocal agreement with Vista Blue would be drafted with the goal of cost-sharing the $26,000 “Water level and quality reporting” expense line item, which would save the District $13,000.\n\nA Board Member asked whether funds budgeted for “Shoreline/seawall repair and replacements” could carry over to Fiscal Year 2021, if not utilized in Fiscal Year 2020. Mr. Wrathell replied affirmatively; it would fall to fund balance. The District must begin building reserve funds in order to fund October, November and December expenses as assessment\n\nrevenues are not usually received until December. Discussion ensued regarding whether to adjust “Aquatic maintenance” to include aerators and lake management for the large lake being dug in the southwestern area or if the installation should be a capital expense, rather than a maintenance expense and details such as the need for electric for the 107-acre parcel. Mr. Wrathell stated he would work with Staff and the District Engineer and adjust, as necessary.\n\nMr. Wrathell reviewed the Debt Service Fund Budget for the soon-to-be-issued bonds and stated the first two payments would be made on December 15, 2019 and June 15, 2020.\n\nOn MOTION by Mr. Smith and seconded by Mr. Ernst, with all in favor, Resolution 2019-08, Approving Proposed Budget for Fiscal Year 2019/2020, as amended, as necessary, and Setting a Public Hearing Thereon Pursuant to Florida Law for September 5th 2019 at 10:00 a.m., at the office of Barraco and Associates, 2271 McGregor Boulevard, Suite 100, Fort Myers, Florida 33901; Addressing Transmittal, Posting and Publication Requirements; Addressing Severability; and Providing an Effective Date, was adopted.\n\nFIFTH ORDER OF BUSINESS\n\nPresentation: Final Supplemental Special Assessment Methodology Report (for informational purposes)\n\nMr. Wrathell presented the Final Supplemental Special Assessment Methodology Report dated May 23, 2019.\n\nDistrict Counsel: Craig, I would just ask you to confirm, I think it’s certainly in the report, but just in summary, that the improvements in the Engineer’s Report, in your professional opinion, provide a special and peculiar benefit to the land, and that the assessments as described in here are fairly and reasonably allocated.\n\nMr. Wrathell: Yes.\n\nSIXTH ORDER OF BUSINESS\n\nConsideration of Resolution 2019-09, Setting Forth the Specific Terms of the District’s Special Assessment Bonds, Series 2019; Making Certain Findings and Confirming and Adopting an Engineer’s Report and an Assessment Report;\n\nConfirming the Maximum Assessment Lien Securing Series 2019 Bonds; Addressing the Allocation and Collection of the Assessments Securing the Series 2019 Bonds; Addressing True-Up Payments; Providing for the Supplementation of the Improvement Lien Book; Providing for the Recording of a Notice of Assessments; Providing for Conflicts, Severability and an Effective Date\n\nMr. Wrathell presented Resolution 2019-09 and read the title.\n\nDistrict Counsel reviewed the Resolution, which is the final step prior to pre-closing.\n\nDiscussion of the Methodology Report resumed. Mr. Smith asked where the use of infrastructure donations by the Developer to lower assessments could be found in the Methodology. Upon examination of the figures it was determined that, rather than utilizing developer contributions to lower assessments, assessments were calculated based on the Equivalent Residential Unit (ERU) benefit allocation of $30 per front foot.\n\nMr. Hasty asked if specifically identifying that the Developer is contributing $12 million to lower debt assessments would preclude the District from issuing additional bonds for some of the infrastructure work, versus the District simply issuing $22 million to $24 million in bonds. District Counsel stated he doubted whether bonds could be issued for improvements that were developer-funded. Mr. Wrathell stated he did not believe developer contributions were used to reduce assessments further than the ERU calculation provided and, if so, another bond issuance would not be precluded. District Counsel stated that a footnote could be added to Table 5, of the Final Supplemental Assessment Methodology Report, as follows:\n\n\"*To the extent not needed for developer contribution, the District reserves the right to issue bonds for future series.*\n\nMr. Wrathell stated, to his knowledge there was no distinction as to what improvements would be funded.\n\nOn MOTION by Mr. Smith and seconded by Mr. Hasty, with all in favor, Resolution 2019-09, Setting Forth the Specific Terms of the District’s Special Assessment Bonds, Series 2019; Making Certain Findings and Confirming and Adopting an Engineer’s Report and an Assessment Report, as amended to include the footnote to Table 5 of the Final Supplemental Special Assessment Methodology Report, as suggested by District Counsel; Confirming the Maximum Assessment Lien Securing Series 2019 Bonds; Addressing the Allocation and Collection of the Assessments Securing the Series 2019 Bonds; Addressing True-Up Payments; Providing for the Supplementation of the Improvement Lien Book; Providing for the Recording of a Notice of Assessments; Providing for Conflicts, Severability and an Effective Date, was adopted.\n\nSEVENTH ORDER OF BUSINESS\n\nAcceptance of Unaudited Financial Statements as of April 30, 2019\n\nMr. Wrathell presented the Unaudited Financial Statements as of April 30, 2019. The District Engineer would submit requisitions for reimbursement of advance funding for eligible expenses, as permitted by the bond funding agreement. In response to a Board Member’s question, Mr. Wrathell stated that the Board did not need to meet to approve requisitions; the approved documents allow the requisition process to proceed. District Counsel concurred and stated because it was identified in Engineer’s Report and the acquisition agreement. Mr. Wrathell stated that the District Engineer would prepare reimbursement requisitions, Staff would review and verify it and, once reviewed, Staff would forward requisitions to the Trustee.\n\nOn MOTION by Mr. Ernst and seconded by Mr. Caldwell, with all in favor, the Unaudited Financial Statements as of April 30, 2019, were accepted.\n\nEIGHTH ORDER OF BUSINESS\n\nConsideration of March 7, 2019 Regular Meeting Minutes\n\nMr. Wrathell presented the March 7, 2019 Regular Meeting Minutes.\n\nOn MOTION by Mr. Caldwell and seconded by Mr. Ernst, with all in favor, the March 7, 2019 Regular Meeting Minutes, as presented, were approved.\n\nNINTH ORDER OF BUSINESS\n\nA. District Counsel: *Hopping Green & Sams, P.A.*\n\nThere being no report, the next item followed.\n\nB. District Engineer: *Barraco and Associates, Inc.*\n\nMr. Barraco stated that construction was proceeding well and in accordance with documents. A draft of the first pay requisition was prepared and would be disseminated.\n\nC. District Manager: *Wrathell, Hunt and Associates, LLC*\n\ni. **0** Registered Voters in District as of April 15, 2019\n\nThere were no registered voters residing within the District as of April 15, 2019.\n\nii. **NEXT MEETING:** August 1, 2019 at 11:00 A.M.\n\nThe next meeting will be held on August 1, 2019 at 11:00 a.m.\n\nTENTH ORDER OF BUSINESS\n\nBoard Members’ Comments/Requests\n\nThere being no Board Member comments or requests, the next item followed.\n\nELEVENTH ORDER OF BUSINESS\n\nPublic Comments\n\nThere being no public comments, the next item followed.\n\nTWELFTH ORDER OF BUSINESS\n\nAdjournment\n\nThere being nothing further to discuss, the meeting adjourned.\n\nOn MOTION by Mr. Smith and seconded by Mr. Ernst, with all in favor, the meeting adjourned at 10:41 a.m.\n\nSecretary/Assistant Secretary\n\nChair/Vice Chair"},"books_score":{"kind":"number","value":0.5700951218605042,"string":"0.570095"}}},{"rowIdx":8691,"cells":{"content":{"kind":"string","value":"Kingsbrook Jewish Medical Center\nRutland Nursing Home\nNursing Education, Practice and Research\n\n2016 Mandatory Yearly Retraining\n\nRevised December 2015\n(Includes Infection Control Addendum)\n\nSelf-Learning Package\n\nNext Review Date: December 2016\n\nORGANIZATIONAL TRAINING AND EDUCATION\n\nThis Mandatory Retraining Self-Learning Package was developed by the Department of Staff Development in conjunction with Nursing Departments, both Acute and Long Term Care, Human Resource Department, Infection Control Department, Facilities Management, Pharmacy Department, Respiratory Department, Employee’s Health Services, Patient Relations, Nursing Quality Initiative Department, Food and Nutrition Services, Physical Medicine and Rehabilitation Department, Department of Case Management, Safety/Security Department, Emergency Management and Risk Management.\n\nThese modules are mandated by the following Regulatory Agencies:\n\nNYS Department of Health (NYS DOH)\n\nOccupational Safety and Health Administration (OSHA)\n\nThe Joint Commission (TJC)\n\nDirections:\n\nA competency exam is located at the end of each chapter. The “Personnel Codes/Training Requirements” page identifies those sections/chapters which must be completed.\n\nPlace your answers on the answer sheet which is inserted in the Self Learning Package.\n\nSign, include your title and date both sides of the sheet and return to your Manager.\n\n## Personnel Codes/Training Requirements\n\n| Code #1 Non-Union | Code #2 KMSA | Code #3 CIR | Code #4 NYSNA | Code #5 SEIU/1199 |\n|-------------------|--------------|-------------|--------------|------------------|\n| Executive | Medical Staff| Interns and Residents | Staff Nurse | Clerical |\n| Department Head | Physician | Fellows | House Nurse | Service/Maintenance |\n| Managerial/Secretarial | Associate Director | House Staff | UP/DP | Professional |\n| Clerical | Assistant Director | Physician | Case Manager | Technical |\n| Director/Medical Services | Coordinator | Dentist | Instructors | Business Office |\n| Professional | | Coordinator | Clinical Specialist | Clerical |\n| Technical | | | Nurse | LPNs |\n| | | | Anesthetist | CNA/PCTs |\n| | | | Nurse Practitioner | Unit Clerks |\n\n### Required to Complete the Following:\n\n| Chapter | Topic | Code 1 | Code 2 | Code 3 | Code 4 | Code 5 |\n|---------|--------------------------------------------|--------|--------|--------|--------|--------|\n| 1 | Safety | | | | | |\n| A. Fire | X | X | X | X | X | X |\n| B. Electrical | X | X | X | X | X | X |\n| C. Disaster | X | X | X | X | X | X |\n| D. Equipment Management | | | | | | |\n| 1. Crash Cart | X | X | X | X | | |\n| 2. Defibrillator | X | X | X | X | | |\n| E. Environmental Safety | X | X | X | X | X | X |\n| F. Security | X | X | X | X | X | X |\n| 2 | Hazard Communication / Body Mechanics | X | X | X | X | X |\n| 3 | Infection Control/Bio-Terrorism | X | X | X | X | X |\n| 4 | Patient/Resident Rights | | | | | |\n| A. Mission Statement | X | X | X | X | X | X |\n| B. Advanced Directives | X | X | X | X | X | X |\n| C. Latex Allergies | X | X | X | X | X | X |\n| D. Pain Management | X | X | X | X | X | X |\n| E. Customer Service | X | X | X | X | X | X |\n| 5 | Risk Management | | | | | |\n| A. Incident/Occurrence Reporting | X | X | X | X | X | X |\n| B. Risk Management | X | X | X | X | X | X |\n| C. Documentation | X | X | X | X | X | X |\n| D. Professional Misconduct | X | X | X | X | X | X |\n| E. HIV Confidentiality | | | | | | |\n| F. Sentinel Events/Patient Safety | X | X | X | X | X | X |\n| H. New York Patient Occurrence Reporting and Tracking | X | X | X | X | X |\n| I. Bio-Ethics Committee | X | X | X | X | X | X |\n| J. Organ Donation | X | X | X | X | X | X |\n| 6 | Corporate Compliance** | X | X | X | X | X |\n| 7 | Domestic Violence/Victims of Abuse | X | X | X | X | X |\n| 8 | Restraints/Seclusion | X | X | X | X | X |\n| 9 | Patient/Family Education/Cultural/Religious Practices | X | X | X | X | X |\n| 10 | Quality Assessment/Improvement, | X | X | X | X | X |\n| 11 | Human Resource Policies/Age-Specific Issues | X | X | X | X | X |\n| 12 | Cultural Competence & Awareness | X | X | X | X | X |\n| 13 | Information Security | X | X | X | X | X |\n| 14 | Emergency Management | X | X | X | X | X |\n\n**Module is online as computer based test**\n\n# Table of Contents\n\n## Chapter 1: Safety\n\n| Section | Page |\n|------------------------------------------------------------------------|------|\n| Purpose | 9 |\n| Objectives | 9 |\n| Emergency Situation Codes | 10 |\n| Part 1A: Fire | 11 |\n| Fire Plan and Procedures | 11 |\n| Fire Response | 12 |\n| Evacuation Procedures | 12 |\n| Operation of a Fire Extinguisher | 13 |\n| Portable Fire Extinguishers | 14 |\n| Oxygen Safety | 14 |\n| Part 1B: Electrical Safety | 15 |\n| Electrical Shock | 15 |\n| Common Hazards | 15 |\n| Precautions for Preventing Electric Shock | 15 |\n| In Case of Accident | 15 |\n| TJC and Electrical Safety | 16 |\n| Cellular Telephones and Radio Transmitters | 16 |\n| Part 1C: Disaster Plan | 16 |\n| Definition and Classification of Disasters | 16 |\n| Disaster Alert | 16 |\n| Internal Disaster Plan | 16 |\n| Part 1D: Equipment Management | 16 |\n| Crash Cart/Box Checklist | 16 |\n| Defibrillator Safety and Maintenance | 17 |\n| Part 1E: Environmental Safety | 17 |\n| Dietary/Pantry Refrigerators | 17 |\n| Temperature Ranges | 17 |\n| Out-of-Range Temperatures | 17 |\n| References | 18 |\n| Part 1F: Security | 18 |\n| Code Orange (Patient/Resident Elopement) | 19 |\n| Code Orange (Patient/Resident Elopement) | 22 |\n\n## Competency Exam: Chapter 1\n\n| Section | Page |\n|------------------------------------------------------------------------|------|\n| Safety | 24 |\n\n## Chapter 2: Hazard Communication/Body Mechanics\n\n| Section | Page |\n|------------------------------------------------------------------------|------|\n| Purpose | 27 |\n| Objectives | 27 |\n| Hazard Communication | 28 |\n| Occupational Safety and Health Administration | 29 |\n| Employee Rights Under the OSHA Standard | 29 |\n| Body Mechanics | 29 |\n| Introducing Ergonomics | 29 |\n| Additional Safety Strategies | 30 |\n| What to Do If You Forget to “Think Back” | 30 |\n| Physical Therapy Corner: Protecting your Back | 31 |\n\n## Competency Exam: Chapter 2\n\n| Section | Page |\n|------------------------------------------------------------------------|------|\n| Hazard Communication / Body Mechanics | 35 |\n\nChapter 3: Infection Control/ Bio-Terrorism Management\n\nPurpose .......................................................................................................................... 36\nObjectives ..................................................................................................................... 36\nHand Washing/Hand Hygiene .................................................................................... 37\n Waterless alcohol hand sanitizer .............................................................................. 37\n Standard/Universal Precautions ............................................................................... 37\n Seven Things Every Employee Needs to Know About Needle Sticks and Other Exposures to Blood or Body Fluid ................................................................. 39\n Infection Control Measures for Patient/Resident Requiring Isolation Precautions ... 40\nKJMC Infection Control Department: Isolation/Precaution Guidelines Summary ........... 51\nDoor Stop Sign ............................................................................................................. 54\nHepatitis B .................................................................................................................... 54\n Hepatitis Transmission ............................................................................................. 55\nRegulated Medical Waste ............................................................................................ 55\n Human Pathological Wastes .................................................................................... 55\nTuberculosis ................................................................................................................ 55\nFacepiece Respirators .................................................................................................. 57\n Fitting Instructions for 3M Filtering Facepiece Respirators .................................... 57\n Fitting Instructions for 3M Adjustable Strap Valved Filtering Facepiece Respirators 59\nKJMC Infection Control Department Infectious Waste Disposal Guidelines .................. 61\nSharps ........................................................................................................................... 62\nRecognition and Management of Terrorism ............................................................... 63\nKJMC Infection Control Department: Isolation/Precaution Guidelines for Bioterrorism Agents ........................................................................................................... 65\n\nCompetency Exam: Chapter 3\n\nInfection Control/Terrorism Management ..................................................................... 67\n\nChapter 4:\n\nPatient/Resident Rights\n\nPurpose .......................................................................................................................... 68\nObjectives ..................................................................................................................... 68\nKJMC/RNH Mission Statement .................................................................................. 69\nPatients’ Bill of Rights ................................................................................................ 69\nYour Rights as a Nursing Facility Resident ............................................................... 70\nKJMC/RNH Advance Directive Policy ....................................................................... 73\nPlanning in Advance for Your Medical Treatment ..................................................... 73\n Your Right to Decide About Treatment .................................................................... 73\n Planning In Advance ................................................................................................. 73\n Deciding About Cardiopulmonary Resuscitation .................................................... 74\n Deciding about CPR: Do-Not-Resuscitate (DNR) Orders: A Guide for Patients and Families ........................................................................................................... 74\n Appointing your Health Care Agent New York State’s Proxy Law ....................... 77\nAbout the Health Care Proxy ....................................................................................... 79\n Filling Out the Proxy Form ....................................................................................... 80\n Health Care Proxy ..................................................................................................... 83\n Surrogate Decisions ................................................................................................. 83\n Do Not Resuscitate (DNR) Orders .......................................................................... 83\n Policy ....................................................................................................................... 84\n Responsibility .......................................................................................................... 85\n Process .................................................................................................................... 85\n Sample Pain Rating Scales ...................................................................................... 86\nFacts About Latex Allergies ......................................................................................... 87\nCustomer Services ...................................................................................................... 88\n HOSPITALity House Rules ....................................................................................... 88\nFall Prevention ............................................................................................................. 88\n\nChapter 5: Risk Management\n\nPurpose ......................................................................................................................... 92\nObjectives ..................................................................................................................... 92\nPart 5A: Incidence/Occurrence Reporting ................................................................. 93\nPart 5B: Risk Management .......................................................................................... 94\nPart 5C: Documentation\n General Tips for Good Documentation .................................................................... 94\nPart 5D: Professional Misconduct .............................................................................. 95\nPart 5E: HIV Confidentiality\n Confidentiality ........................................................................................................... 96\n Confidentiality and Disclosure .................................................................................. 96\nPart 5F: Sentinel Event Policy/Patient Safety ............................................................ 96\nPart 5G: New York State Patient Occurrence Reporting and Tracking System (NYSPO\nRTS) ............................................................................................................................ 97\nPart 5H: Bioethics Committee\n Purpose ....................................................................................................................... 99\n Consultation .............................................................................................................. 99\n Education .................................................................................................................. 100\nPart 5I: Organ Donation\n The Health Care Professional’s Role in Donation .................................................. 100\n Eyes: The Transplant Almost Anyone Can Donate ................................................ 101\n\nCompetency Test: Chapter 5\n\nRisk Management ........................................................................................................ 103\n\nChapter 6: Corporate Compliance\n\nPurpose ......................................................................................................................... 105\nObjectives ..................................................................................................................... 105\nCorporate Compliance ................................................................................................ 106\n Quality of Care .......................................................................................................... 106\n COMPLIANCE WITH LAWS/REGULATIONS ...................................................... 107\n CONFLICTS OF INTEREST ..................................................................................... 107\n BILLING AND CODING INTEGRITY ....................................................................... 108\n RESPECTFUL ENVIRONMENT ............................................................................... 108\n HUMAN RESOURCES ............................................................................................... 109\n SAFEGUARDING MEDICAL CENTER ASSETS .................................................. 110\n ENVIRONMENTAL CONSIDERATIONS ................................................................. 110\n EMPLOYEE ISSUES AND CONCERNS .................................................................. 110\n Deficit Reduction Act / “Whistleblowers” ............................................................... 111\n HIPAA (Health Insurance Portability and Accountability Act) .................................. 111\n\nCompetency Test: Chapter 6\n\nCorporate Compliance ................................................................................................ 117\n\nChapter 7: Domestic Violence / Victims of Abuse\n\nPurpose ......................................................................................................................... 118\nObjectives ..................................................................................................................... 118\nDefinition of Domestic/Family Violence ..................................................................... 119\nCharacteristics of the Abuser and the Abusive Relationship ....................................... 119\nWhy Adult Victims Stay ............................................................................................... 120\nForms of Abuse ............................................................................................................ 120\nThe Physical Exam ...................................................................................................... 121\n Abuse and Mistreatment Recognition Chart ............................................................ 121\nIntervention Strategies for the Adult Victim ............................................................... 123\n\nValidate Your Concern ................................................................. 123\nSuggested Questions ............................................................... 123\nQuestions to Avoid ................................................................. 123\nEmpower the Survivor of Abuse .............................................. 123\nEmergency Housing ............................................................... 124\nCounseling ............................................................................. 124\nLegal Action .......................................................................... 124\nGuidelines for Reporting Cases of Child Abuse / Maltreatment .... 125\nHotline Numbers ..................................................................... 125\n\nCompetency Exam: Chapter 7 .................................................. 127\nDomestic Violence/Victims of Abuse ........................................ 127\n\nChapter 8: Restraints/Seclusion ............................................... 128\nPurpose .................................................................................. 128\nObjectives .............................................................................. 128\nPreventing and Managing Crisis in the Agitated Patient ............ 129\nRestraints .............................................................................. 129\n Assessment .......................................................................... 129\n Definition ........................................................................... 130\n Highlights of the Conditions and Guidelines for Use .............. 131\n\nCompetency Exam: Chapter 8 .................................................. 133\nRestraint/Seclusion .................................................................. 133\n\nChapter 9: Patient/Resident and Family Education – Cultural and Religious Practices ........................................ 134\nPurpose .................................................................................. 134\nObjectives .............................................................................. 134\nPatient/Resident Education ..................................................... 135\n Evaluation of Patient/Resident and Family Education ............ 136\n Follow-up on Education ....................................................... 136\n Educational Resources ....................................................... 136\n Settings for Education ......................................................... 136\nCultural and Religious Practices of KJMC Patient Populations .... 137\nDefinitions ............................................................................ 139\n\nCompetency Exam: Chapter 9 .................................................. 144\nPatient/Resident Education – Cultural and Religious Practices .... 144\n\nChapter 10: Quality Assessment/Improvement, Sentinel Events 145\nPurpose .................................................................................. 145\nObjectives .............................................................................. 145\nContinuous Quality Improvement ............................................. 146\n Definition ........................................................................... 146\n Objectives .......................................................................... 146\n Approach and Methodology ............................................... 147\n Standard ............................................................................. 147\n Standard of Care .................................................................. 147\n Standard of Practice ............................................................ 147\n Indicators ............................................................................ 147\nQuality Management/Nursing Quality Initiative Locations .......... 148\n Nursing Quality Initiative (NQI) ........................................... 148\nSentinel Events ....................................................................... 148\n\nChapter 11: Human Resources Policies/Age-Specific Issues\n\nPurpose .......................................................................................................................... 151\nObjectives ..................................................................................................................... 151\nHuman Resources Policy and Procedure Manual ......................................................... 152\nVideotape Content Review ............................................................................................ 169\n Introduction .............................................................................................................. 169\n Barriers to Communication ....................................................................................... 169\n Neonates: Birth to 26 Days ..................................................................................... 169\n Infants/Toddlers: 0-3 Years ..................................................................................... 170\n Young Children: 4-6 Years ...................................................................................... 170\n Older Children: 7-12 Years ...................................................................................... 171\n Adolescents: 13-20 Years ....................................................................................... 171\n Young Adults: 21-39 Years ..................................................................................... 172\n Middle Adults: 40-64 Years ..................................................................................... 173\n Older Adults: 65-79 Years ....................................................................................... 173\n Adults 80 and Older .................................................................................................. 174\nConclusion ..................................................................................................................... 174\nNeeds of the Elderly ..................................................................................................... 174\n Nutritional/G/I System ............................................................................................. 175\n Skin, Hair, Nails ....................................................................................................... 175\n Eyes and Vision ........................................................................................................ 176\n Ears and Hearing ...................................................................................................... 176\n Respiratory System ................................................................................................... 176\n Cardiovascular System ............................................................................................. 176\n Renal System ............................................................................................................ 176\n Reproductive System ............................................................................................... 177\n Neurological System ............................................................................................... 177\n Musculoskeletal System ........................................................................................... 177\n Immune System ........................................................................................................ 177\n Endocrine System .................................................................................................... 177\n Psychological Transitions .......................................................................................... 177\n\nCompetency Exam: Chapter 11\n\nHuman Resources Policies/Age-Specific Issues .......................................................... 178\n\nChapter 12: Cultural Competence & Awareness\n\nPurpose ......................................................................................................................... 179\nObjectives ..................................................................................................................... 179\nIntroduction: ............................................................................................................... 180\nDefinitions: ................................................................................................................ 180\n Ethnicity .................................................................................................................. 180\n Culture ..................................................................................................................... 180\n Diversity .................................................................................................................. 180\n Generalizations/Stereotypes .................................................................................... 180\n Values ...................................................................................................................... 180\nWhat is Cultural Competency? .................................................................................... 181\nCultural Competency at KJMC results in: .................................................................... 181\nThe Importance of Cultural Competence ..................................................................... 181\nPopulation in the US ..................................................................................................... 181\nPopulation in the Brooklyn ........................................................................................... 181\nAccording to the 2010 Census, 35.7% of the population was non-Hispanic White,\n31.9% non-Hispanic Black or African American, 10.4% non-Hispanic Asian, 0.4%\nfrom some other race (non-Hispanic) and 1.6% of two or more races (non-Hispanic).\n\n19.8% of Brooklyn’s population was of Hispanic, Latino, or Spanish origin (they may be of any race). ................................................................. 181\n\nHealth Disparities .............................................................................. 182\n\nRegulatory Requirements .................................................................. 182\n\nComponents of Cultural Competence .................................................. 182\n\nThe Iceberg Theory of Culture ............................................................. 183\n\nCommunicating Effectively ................................................................. 183\n\nLanguage barriers and miscommunication are often cited as barriers to healthcare. Not surprisingly, it has been found that a major contributing factor in healthcare litigation comes as a result of communication problems. Two aspects of communication are speech (Verbal) and body language (non-verbal). Both of which are equally important when engaged in face to face contact. .................................................................................. 183\n\nOther Considerations for Providing Culturally Competent Care ............ 184\n\nU.S. & Cultural Health Care Values Grid ............................................. 185\n\nConclusion ......................................................................................... 186\n\nCultural competence can positively affect the quality of patient care by reducing delays in seeking medical care and improving the use of limited services. Culturally competent providers may also facilitate better communication and understanding between patients and providers. The result then would be better diagnoses, development of appropriate treatment plans and improved adherence to treatment plans by patients. Therefore, culturally competent interventions may help to promote more positive health outcomes and satisfied patients and families. ....................................................................................... 186\n\nCompetency Exam: Chapter 12 .......................................................... 187\n\nCultural Competence & Awareness ..................................................... 187\n\nChapter 13: Information Security .......................................................... 188\n\nInformation Security is Everyone’s Responsibility! ........................... 188\n\nInformation Security .......................................................................... 188\n\nWhat is confidentiality? ..................................................................... 189\n\nInformation Security .......................................................................... 190\n\nPassword Management ....................................................................... 193\n\nCompetency Exam: Chapter 13 .......................................................... 196\n\nInformation Security .......................................................................... 196\n\nChapter 14: Emergency Management .................................................. 197\n\nCompetency Exam: Chapter 14 .......................................................... 200\n\nEmergency Management ................................................................... 200\n\nChapter 15: National Patient Safety Goals ........................................... 202\n\nNational Patient Safety Goals for 2016 ............................................... 202\n\nCompetency Exam: Chapter 15 .......................................................... 204\n\nChapter 1: Safety\n\nPurpose\n\nThis module was designed to review the actions and responsibilities of nursing personnel as it relates to fire, electrical safety and disaster.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. Recall the actions to be taken if a fire occurs\n2. Identify the Local Fire Alarm Station Number for your work area\n3. State the RACE procedure, i.e., the four steps to take in the event of a fire on a patient care unit\n4. Describe the PASS procedure for discharging a fire extinguisher\n5. State the three classifications of fire extinguishers and their use\n6. Identify actions to take in the event of a disaster and describe procedures for maintenance of electrical equipment\n7. Complete the competency exam\n\n## Emergency Situation Codes\n\n| Emergency Situation | Code |\n|----------------------------------------------------------|-------------------------------------------|\n| Cardiac Arrest | Code 99 – Dial 555 |\n| Sepsis | Code 33 |\n| Therapeutic Hypothermia | Code Ice |\n| Fire/Smoke | Doctor Red – Pull nearest fire alarm, then dial 555 |\n| Rescue -- Remove any person in immediate danger | |\n| Alarm – Sound alarm at nearest alarm box | |\n| Confine – Close all doors and windows | |\n| Extinguish/Evacuate – Use fire extinguisher | |\n| Potential or actual physical harm in acute care | Assist 13 – Dial 555 |\n| Potential or Actual Physical Harm in LTC | Code Plaid – Dial 777 |\n| Change in patient’s condition/Medical Distress | Code 66 (Recognition & Response Team) |\n| Stroke Code | Code 717 |\n| Need for Limited Assistance, i.e., flood from broken pipe| Limited Assist 10 – Dial 555 |\n| Missing child – girl | Code Pink – Dial 555 |\n| Missing child – boy | Code Blue – Dial 555 |\n| Controlling entrance/exits for medical reasons (Nuclear/Biological/Chemical type incidents) | Code Medical Seal |\n| Disaster Code | You will hear fire alarm bells ring “2222.” All disaster team leaders will respond to the command center (Lefrak Building, 1st floor) for further instructions |\n| Missing/Eloped Patient/Resident | Code Orange |\n| Active Shooter | Code Silver |\n| Emergency/Fire in ventilation Unit in Rutland nursing Home. | Code Purple |\n\n### New Neurological Deficit\n\n1. RN staff member notifies resident on duty STAT\n2. RN administers oxygen at 2 liters/min., maintains clear airway and begins assessment using the Neurological Flow Sheet (see policy, “Neurological Assessment,” in Nursing P&P Manual)\n3. On instructions from resident, the nurse will dial 717 and say “Code 717”\n4. RN staff member pages Radiology Technician using stroke pager (operator has pager number). RN and MD transfers patient to Cat Scan\n5. RN staff members [from out-patient departments] should notify the Emergency department charge nurse for urgent transport of stroke patient to the Emergency Department. All in-patient units will notify the Critical care charge nurse\n6. RN staff member notifies ADN/designee\n\nPart 1A: Fire\n\nFire Plan and Procedures\n\nThe fire plan is intended to provide a basic guide for actions to be taken in the event of smoke or fire. The cornerstone of this plan is the notion that the first person to see or suspect a fire should transmit a fire alarm immediately. Neither permission nor approval is ever necessary.\n\nIf you smell smoke or the smoke detector sounds, dial 555 and give the location. When the fire alarm sounds 10-1 (smoke alarm) and 10-2 (water flow alarm). This requires that you listen to the fire bell system to determine the location of the alarm.\n\nRACE Procedure\n\n- **REMOVE** those who may be in immediate danger from smoke and fire!\n\n Rationale: It is most important to separate people from the fire. Therefore, it is necessary to remove the patients or any other person from the room that is on fire as a first step (see patient evacuation techniques).\n\n- **ALERT** others by calling “Doctor Red” aloud and pull the alarm (located on each stairwell on every level). Also dial 555 on any house phone. Once patients are removed, turn off oxygen if in use.\n\n Rationale: KJMC’s fire plan, in compliance with New York City fire codes, requires the person who first observes a fire to pull the manual fire alarm. This does several things. First, it alerts all within the hospital that a fire emergency exists and permits others to determine the location of the fire by counting the tones. Second, it notifies the Quick Response Team of the location of the fire so they can respond to the area and provide assistance. It also tells the Quick Response Team where to bring the fire department when they arrive. Third, it summons the New York City Fire Department to the hospital automatically.\n\n- **CONFINE** the fire by closing the doors to the room.\n\n Rationale: Closing the doors contains the spread of fire, smoke and heat. Place wet linens at base of door to prevent smoke from contaminating the corridor. Toxic smoke can be more dangerous than the flame itself. A closed door creates a fire-rated barrier between you and the fire because it confines the fire in a “compartment.”\n\n For instance, if a fire is in a patient’s room, closing the door to the room will contain the fire in the room for about one hour.\n\n **NOTE:** The converse is also true. A patient is protected inside his or her room from a fire outside the room for about an hour when the room door is closed. Closed corridor fire doors are added protection to confinement.\n\n- **EVACUATE** the surrounding area, along a horizontal axis to a safe corridor refuge location. If horizontal evacuation is not possible, evacuate vertically via fire stairs.\n\n Rationale: For inpatient areas the general order of patient evacuation is:\n\n - Ambulatory\n - Those who need assistance\n - The critically ill\n\n Someone should stay with the patients in the safe corridor refuge area to render care as needed and to prevent them from panicking.\n\n Elevators should not be used for evacuation. Patients should be evacuated horizontally to another area.\n\nOR\n\n- **EXTINGUISH**: use the fire extinguishers (ABC types) located throughout our facilities to **PASS** – Pull, Aim, Squeeze, Sweep\n\n**Fire Response**\n\nIn the event of a fire, the following steps should be taken:\n\n1. The source of the fire should be located\n2. All doors in the immediate area should be closed to minimize access of smoke\n3. Activate the closest manual pull station (this will alert the fire department)\n4. The Operator should be contacted via ext. 555; give the location of the fire including building, floor and closest stairway\n5. Dr. Red will be announced by the Operator\n\nIf the fire is in a controlled area and can be extinguished, the PASS system will be implemented:\n\n- **Pull** pin\n- **Aim** nozzle at base of fire\n- **Squeeze** handle to discharge content\n- **Sweep** in side-to-side motion\n\nIn the event of evacuation the stairway is the only means of egress. Never use the elevators. Once the fire is under control the “all clear” signal will be announced by the operator.\n\n**Evacuation Procedures**\n\nWhen patient evacuation is necessary follow these methods of moving them:\n\n**Horizontal Evacuation**\n\n1. Move patients who are closest to the danger first.\n2. Children should be handled like adults.\n3. Start moving **ambulatory** patients toward the nearest and safest protected area. Assign one employee to follow in the rear of each patient group. **Do not leave ambulatory patients without guidance** – this will minimize the potential for panic.\n4. Move wheelchair patients to a safe area on the same floor. Return chairs for additional patients.\n5. Move helpless patients via stretchers. If stretchers are unavailable, use the cradle drop method to place a patient on a blanket that has been set on the floor. Then pull the patient out along the floor to a safe location. If blankets are unavailable, use sheets (double-folded) or bedspreads to drag patients to safety.\n\n**Vertical Evacuation**\n\n1. Lead ambulatory patients up or down the nearest and safest protected exits/stairway. Refuge should normally be found one floor below the disaster or fire. However, if time permits, evacuate patients two floors downward. In all situations, patients should be evacuated by means of fire exits, **not elevators**!\n2. Non-ambulatory and helpless patients should be moved down stairways by means of emergency personnel carries. The recommended stairway or fire escape carries are the two-man swing carry or the three-man and four-man blanket carries.\n\nNon-Ambulatory Patient Evacuation: Two Person Technique\n\n1. Remove top sheet/blanket from the bed\n2. Loosen bottom sheet around mattress\n3. Roll both sides of the bottom sheet parallel to patient’s arms and legs\n4. On one side of bed, position one nurse at the head and another nurse at the feet of the patient. In sequence grab both sides of rolled sheet and lift patient to edge of bed.\n5. Holding onto the rolled sheet edges, the nurse positioned at the feet lowers the patient’s legs over the edge of the bed. Then the nurse at the patient’s head lowers the patient’s shoulders onto nurses’ thighs. (The nurse at this position bends her knees using her thighs as a slide, so the patient is eased down from the bed and slides onto the floor.)\n6. Once the patient is on the floor, the nurse at the feet releases the sheet and the nurse at the head position drags the patient to an area of refuge.\n\nNon-Ambulatory Patient Evacuation – One Person Technique\n\n1. Remove top sheet/blanket from the bed\n2. Loosen bottom sheet around mattress\n3. Wrap the patient’s legs with the sheet, mummify the leg area\n4. Roll both sides of sheet parallel to patients’ arms and head\n5. Slide patient to edge of bed and lower legs over the edge\n6. Hold onto both rolled sheet edges and slide the patient’s shoulders onto nurse’s thighs (the nurse bends her knees using her thighs as a slide so the patient is eased down from the bed) and slides the patient onto the floor\n7. Once the patient is on the floor, the nurse drags the patient to an area of refuge\n\nOperation of a Fire Extinguisher\n\nThere are four basic steps to operating a portable fire extinguisher. An easy way to remember the procedure is to think of the word “PASS.”\n\n- **Pull** the pin: Hold the extinguisher with the nozzle pointing away from you. Release the locking mechanism (in most cases this means pulling out the pin located below the trigger).\n\n- **Aim** the nozzle: Point the extinguisher nozzle at the base of the fire, the lowest point of the fire nearest you. Extinguishers are designed to be operated in an upright position; avoid cradling or holding at an angle.\n\n- **Squeeze** the handle: Squeeze the trigger slowly and evenly to release the extinguishing agent.\n\n- **Sweep** side to side: Sweep the nozzle from side to side to extinguish the fire. As the fire closest to you goes out, you may move closer to the fire and continue the sweeping motion until the fire is extinguished.\n\nEven after the fire appears to be extinguished, watch the area until help arrives. If the fire breaks out again and you have not fully discharged the extinguisher, repeat the process. If you cannot extinguish the fire completely or perceive you cannot extinguish the fire, leave the area immediately, closing the door as you leave.\n\nPortable Fire Extinguishers\n\nClassification of Fire Extinguishers\n\n- “Class A” fires involve “ordinary combustibles” such as wood, paper, linen, mattresses and waste containers.\n\n- “Class B” fires involve flammable liquids such as oils, greases, chemicals, flammable gasses and plastics.\n\n- “Class C” fires involve electrical equipment, appliances, medical equipment, electrical wiring, fuse boxes or circuit breakers. This indicates that the extinguisher can be used on electrical equipment without receiving an electric shock.\n\nIf all three symbols (A, B and C) are shown, the extinguisher is rated for use in all types of fires.\n\nHowever, a red slash through any of the classification symbols tells you an extinguisher can be dangerous if it is used on that type of fire. In this example, the extinguisher could be used on ordinary combustibles and flammable liquids fires, but not for electrical equipment fires.\n\nOxygen Safety\n\nOxygen itself does not burn but its presence will support combustion and allow materials to burn that would not ordinarily burn at room temperature. Since oxygen and fuel (any combustible material) is always present, the best means to reduce fire hazards is the elimination of the source of ignition. Therefore, the following safety precautions should be observed when using oxygen:\n\n1. Electrical equipment should be plugged in and running before oxygen flow is started.\n\n2. All oxygen connections should be checked to be sure they are tight and not leaking.\n\n3. Alcohol, ether or flammable liquid must not be used in the vicinity of oxygen use.\n\n4. Avoid dropping clothing or linens onto oxygen lines, cylinders or equipment, since fabrics saturated with oxygen ignite easily.\n\n5. Any source of ignition must not be allowed into an area where oxygen is used, e.g., electrical equipment which arcs or sparks, sparking toys in a pediatric area.\n\n6. Enforce KJMC’s no smoking policy at all times. A fire caused by lighting a cigarette in the presence of oxygen-enriched materials (such as sheets, blankets, etc.) could immediately engulf the patient.\n\n7. When possible, oxygen should be discontinued during the defibrillation of a patient.\n\n8. Oxygen cylinders must be secured upright in stands or on a dolly when not in use.\n\n9. If the wall oxygen system or a portable oxygen tank is leaking, page Respiratory as soon as possible. DO NOT use the oxygen.\n\n10. If oxygen is leaking in a patient’s room or storage area, DO NOT disconnect or turn on any electrical equipment – this will help avoid any potential ignition source.\n\n11. The fire department will make the decision to turn off the oxygen to patient rooms; the KJMC designee (nurse, respiratory tech, etc.) will turn off the oxygen as instructed by the fire department, being aware of where the zone valve(s) are located on the unit.\n\n**Part 1B: Electrical Safety**\n\n**Electrical Shock**\n\n- **ELECTRICAL SHOCK** occurs when a source of voltage is present on the case and/or a power cord of a piece of equipment due to malfunction.\n\n- A **MACROSHOCK** is caused by exposed wires, a defective electrical plug or power cord or an internal electrical short.\n\n- A **MICROSHOCK** is caused by a relatively small current on the metal case or connector of the instrument due to equipment design and not necessarily indicating malfunction. Patients vulnerable to microshock include: patients with moist or wet skin, small children, sick adults and patients in a wet environment.\n\nYou can protect patients by ensuring that equipment has three-wire power cords and three-pronged plugs.\n\n**Common Hazards**\n\n- Patients’ Personal Equipment: Patients may not use their own equipment unless it has been checked by the Biomedical Engineering Department.\n\n- Unapproved Extension Cords: Avoid use of extension cords at all times. If an extension cord must be used, ensure that it has been checked by the Biomedical Engineering Department.\n\n- Two to Three-Pronged Adapters: These “cheaters” are prohibited at KJMC. Their use causes elimination of the ground wire in the power plug, increasing the probability of being electrocuted.\n\n- Faulty Equipment: If you have reason to believe that a piece of equipment is faulty, immediately attach a BioMed Service Requisition form and call the Biomedical Engineering Department for service.\n\n**Precautions for Preventing Electric Shock**\n\n1. Close monitoring of all common hazards\n2. Check for signs of liquid spillage\n3. Use three-pronged electrical plugs only\n4. Check for the presence of the Biomedical Engineering safety tag\n5. Become thoroughly familiar with the procedures for proper use of equipment\n\n**In Case of Accident**\n\n1. Unplug the faulty equipment\n2. Render help to the electrocuted person\n3. Call Biomedical Engineering for assistance\n4. Safely rescue and revive the victim\n\nTJC and Electrical Safety\n\nAccording to TJC, every piece of medical equipment (patient and non-patient-related) should undergo a safety check at least annually. A record of these checks should be kept by the user and by Biomedical Engineering.\n\nCellular Telephones and Radio Transmitters\n\nIn order to ensure patient safety and eliminate the possibility of radio frequency (RF) interference with clinical equipment, KJMC will not allow the use of cellular telephones and will control the use of radio transmitters.\n\nTwo-way radios are not to be used within three feet of active patient monitors. A two-way radio may be used to receive, but not to transmit, from an area with active patient monitors (including transport monitors).\n\nPart 1C: Disaster Plan\n\nDefinition and Classification of Disasters\n\nA disaster is defined as an abnormal patient load, resulting from a common cause, admitted to Emergency Services and requiring staff and resources beyond that usually available at Emergency Services at that time.\n\nDisasters are classified as follows:\n\n- **External Disaster**: Disasters occurring outside of KJMC facilities such as a disaster may result from such events as a building or bridge collapse, an airline crash, a major subway or bus accident or a major fire.\n\n- **Internal Disaster**: Disasters occurring inside KJMC facilities such as an in-hospital fire, bomb threat or major utility failure.\n\nDisaster Alert\n\nIn the event of an External Disaster, the KJMC operator will make announcements via the overhead page system.\n\nThe fire alarm will sound “2222.”\n\nInternal Disaster Plan\n\nIn an Internal Disaster situation, patients will be triaged at the site of the disaster and then accompanied by a physician or nurse to the Emergency Department or Ambulatory Care area where treatment will continue.\n\nPart 1D: Equipment Management\n\nCrash Cart/Box Checklist\n\nOn every shift, the nurse uses the crash cart/box checklist to document the integrity of the lock on the crash cart. Every shift, the nurse ensures that:\n\n1. The crash cart is present\n2. The crash cart is locked\n3. The equipment stated on the sheet is indeed present\n4. The defibrillator is functionally checked with the plug out\n\nIn the event that the crash cart is used, the date of use is noted on the checklist. Immediately after use, the cart must be replaced with a fresh cart from Central Supply. The emergency drug boxes are returned to pharmacy for exchange.\n\n**Defibrillator Safety and Maintenance**\n\nThe RN, LPN and physician are responsible for safe operation and maintenance of the cardiac defibrillator.\n\nThe operational checks are performed with the plug out at the beginning of each shift following manufacturer’s guidelines. The checks are documented as part of the crash cart checklist.\n\nThe physician or nurse with Automatic External Defibrillator (AED) on the unit will defibrillate the patient. Only the physician may cardiovert, pace patients and use “paddle” mode to defibrillate the patient.\n\nStaff and patient safety is imperative during the defibrillation process:\n\n1. Staff must report frayed wires\n2. Patient’s chest must be dry\n3. The floor must be dry\n4. Staff must stand well away from the patient’s bed or electrodes\n5. The person defibrillating must clearly announce, “Stand Clear!”\n6. The oxygen source must be removed\n\nAfter use, with the power off and unit unplugged, the defibrillator paddles must be cleaned with a damp cloth.\n\nOperational malfunction of the unit must be reported immediately to Biomedical Engineering and the unit must be returned to Central Supply for exchange.\n\n---\n\n**Part 1E: Environmental Safety**\n\n**Dietary/Pantry Refrigerators**\n\nThe Food and Nutrition Services Department will check and record temperatures on the Nursing Unit pantry refrigerators using the Temperature Log Sheet on a daily basis. The Facilities and Nursing departments will be contacted whenever a temperature is above $41^\\circ$ F. All foods will be discarded if this should occur.\n\n**Temperature Ranges**\n\nTemperatures are checked daily.\n\n| Equipment | Acceptable Temperature Range |\n|----------------------------|------------------------------|\n| Pantry/Dietary Refrigerators | $41^\\circ$ or below |\n| Medication Refrigerators | $36^\\circ – 45^\\circ$ F |\n| Refrigerator for Blood in the OR | $40^\\circ – 44^\\circ$ F |\n\n**Out-of-Range Temperatures**\n\n- The pantry refrigerator temperature, when out of range, will be reported immediately to the Facilities Department.\n- Refrigerators for Blood in the OR, when out of range, will be reported immediately to the Engineering Department. Engineering notifies the Blood Bank whenever the temperature increases or decreases.\n\nLaboratory employees should refer to the KJMC Policies and Procedures for laboratories for information on lab refrigerator temperature ranges and reporting requirements.\n\n**References**\n\n“Blood Bank in OR,” December 1999.\n\n“Pantry Refrigeration Temperature Checks,” November 2001.\n\n“Refrigerators on Nursing Units,” April 2002, Nursing Policy and Procedure Manual.\n\n**Part 1F: Security**\n\nThe security procedures for KJMC/RNH are as follows:\n\n1. A visible security presence in the hospital helps to reduce crime and increase the feeling of security on the part of patients, visitors and staff.\n\n2. Patrol buildings and property to identify and document potential or actual problems.\n\n3. Limit access to grounds, buildings and sensitive areas by enforcement of staff identification. Picture ID cards must be worn or displayed at all times.\n\n4. Identification of visitors will be accomplished by requiring sign-in and by issuance of passes that must be worn on visitors’ outermost layer of clothing.\n\n5. Lockdown of all exits and entrances occurs from 6:00 p.m. to 6:00 a.m., Monday through Friday. All entrances are manned by a security officer and work with a buzzer system during these times. This is also a precaution against patient/resident elopement.\n\n6. Security Incident Reports are prepared for the following situations:\n - Property damage\n - Personal injury (other than employee or patient)\n - Breach of security\n - Safety or fire hazards\n - Violation of KJMC’s policies\n - Criminal acts by an individual\n - Theft of property\n - Acts of violence\n - Investigations by outside agencies (law enforcement agencies, OSHA, etc.)\n\n7. Infant/child abduction plan:\n - Dial 555\n - Code blue for a boy; code pink for a girl\n - Notify security IMMEDIATELY!\n\nThe Security Department will work closely with the local police and fire departments to make the facility a safer place.\n\nOBJECTIVE:\nTo provide an immediate and effective response to an active shooter event on the Kingsbrook Jewish Medical Center facilities or its grounds.\n\nPURPOSE:\n\nThis policy outlines recommendations for staff members to follow during an Active Shooter (Code Silver) event within The Kingsbrook Jewish Medical Center facilities or its grounds. This policy is consistent with the recommendations published by the United States Department of Homeland Security and is in keeping with other Kingsbrook Jewish Medical Center policies surrounding high risk security events. Active Shooter situations are unpredictable and may evolve quickly (often over within 10 to 15 minutes). This policy provides general response guidance for staff members. Immediate deployment of law enforcement is required to stop the shooting and victim harm. Directions provided by law enforcement, upon arrival, should be followed exactly.\n\nDEFINITIONS:\n\nA. Active Shooter - An **active shooter** is defined as\n\n\"...an armed person who has used deadly physical force on other persons and continues to do so while having unrestricted access to additional victims.\"\n\n[1] The definition includes so-called \"snipers,\" but not usually suicide bombers. **Active shooters** have caused a paradigm shift in law enforcement training and tactics, especially as these persons do not necessarily expect to escape or even survive these situations.\n\nB. Hostage - A **hostage** is a person or entity which is held by a captor.\n\nC. Code Silver-When used in this policy the term \"Code Silver\" means an individual or multiple people actively engaged in killing or attempting to kill people in a confined and populated area.\n\nPOLICY:\n\nIt is the policy of Kingsbrook Jewish Medical Center to provide a safe, caring and compassionate environment for all whom enter our facilities. In order to preserve life and address the reality of an active shooter event, these guidelines have been established to guide our response to this event to maximize survivability.\n\nPROCEDURES:\n\nThe intent of most active shooters is to harm or kill as many people as quickly as possible. In order to save lives, the New York City Police Department will initiate an immediate response.\n\nActive shooters do not take hostages.\n\n1. Upon discovery of an active shooter situation, notify: **Telecommunications at Extension 0** (Internal) and (718)604-5000(External). They will conduct an overhead announcement of a Code Silver and location. If possible, call 911.\n\n2. Upon hearing a \"Code Silver\" overhead page; employees shall **Shelter in place**. If possible, barricade door and/or hide. **DO NOT** go to the area specified in \"Code Silver\".\n\n3. Safety/Security will institute a **Lockdown** of the Hospital. No one shall enter the building unless they are a member of the Police Department or Law Enforcement agency involved in the incident.\n\n4. Safety & Security Officers will meet and guide New York City Police officers as appropriate. The goal of law enforcement is to locate, isolate, and neutralize the shooter as quickly as possible to prevent additional deaths or injuries.\n\n5. Safety & Security Officers will attempt to track the active shooter using CCTV and Panic alarms being activated or phone calls being received by Telecommunications.\n\n**Clinical/Medical Staff Response in Patient Care areas-Shelter in Place**\n\n1. Clinical/Medical staff and support staff in patient care areas will remain calm and calm the fears of patients and visitors.\n\n2. Clinical/Medical Staff will suspend all discharges, non-urgent medical procedures, and other non-urgent patient movement during the incident.\n\n3. Clinical/Medical Staff, patients, and visitors will be directed to patient rooms or other adjacent rooms, close the door and attempt to barricade the doors.\n\n4. If possible, consider locating into the bathroom and locking the door, stay as low to floor as possible and remain quiet and still.\n\n5. Do not flee from the area or leave the facility unless instructed to do so by law enforcement or to protect oneself from imminent danger.\n\n6. If Clinical/Medical staff can safely call Telecommunications (718)604-5000 using a cell phone, or phone (to call 911) from the area where they are concealed they should do so and provide the following information:\n\n a. **Description of suspect and possible location.**\n\n b. **Number and types of weapons.**\n\n c. **Suspect's direction of travel.**\n\n d. **Location and condition of any victims.**\n\n e. When calling 911, if possible leave the line open if you cannot speak or if you leave the area. This gives law enforcement \"open listening\" to the area.\n\n7. An \"All Clear\" Code Silver will be announced overhead when the situation has been resolved. All Clear announcement will only be authorized after a **face to face** meeting from New York City Police and the Hospital Incident Commander to the Hospital Telecommunications Operator is conducted.\n\n8. Take action against the active shooter. As a last resort, and only when your life is in imminent danger, attempt to disrupt and/or incapacitate the active shooter by:\n\n a. Acting as aggressively as possible against him/her.\n\n b. Throwing items and improvising weapons.\n\n c. Yelling.\n\n d. Committing to your actions.\n\n**Non-Clinical Staff Response in Non-Clinical Areas, physicians, and others-Shelter in Place**\n\n1. Non-Clinical/Medical staff and support staff should remain calm, and calm the fears of others.\n\n2. Non-clinical staff, patients, students, contractors, vendors, and others should immediately proceed to areas that can be locked.\n\n3. Individuals are to stay as close to the floor as possible, using office furniture available as cover.\n\n4. Individuals should remain quiet and still. Silence your cell phone or pager.\n\n5. Individuals will remain behind closed or locked doors until rescued by New York City Police or they hear an \"all clear\" Code Silver announced overhead.\n\n6. Do not flee from the area or leave the facility unless instructed to do so by New York City Police or to protect oneself from imminent danger.\n\n7. If Staff can safely call Telecommunications (718)604-5000 using a cell phone, or phone (to call 911) from the area where they are concealed they should do so and provide the following information:\n\n a. **Description of suspect and possible location**\n \n b. **Number and types of weapons**\n \n c. **Suspect's direction of travel**\n \n d. **Location and condition of any victims**\n \n e. When calling 911, if possible leave the line open if you cannot speak or if you leave the area. This gives law enforcement \"open listening\" to the area\n\n8. An \"All Clear\" Code Silver will be announced overhead when the situation has been resolved. All Clear announcement will only be authorized after a **face to face** meeting from New York City Police or the Hospital Incident Commander to the Hospital Telecommunications Operator is conducted.\n\n9. Take action against the active shooter. As a last resort, and only when your life is in imminent danger, attempt to disrupt and/or incapacitate the active shooter by:\n\n a. Acting as aggressively as possible against him/her.\n \n b. Throwing items and improvising weapons.\n \n c. Yelling.\n \n d. Committing to your actions.\n\n**Evacuation:**\nA partial or full evacuation may be ordered based on the situation specifics, and when it is deemed safe to do so. The order to evacuate will be given by the following individuals; The Hospital Incident Commander or a Law Enforcement Officer. **Staff is reminded to keep their hands above their heads, free of objects and open palms facing the responding agency members.**\n\n**Administration:**\n1. Institute the Hospital Incident Command System (HICS) as soon as possible in the administration board room 1 (**If safe to do so**).\n2. HICS team to alert triage team on possible number of injuries.\n\n**Safety/Security Response**\n\n**Main Campus**\n\n1. Safety/Security will immediately respond in a safe manner to contain and/or isolate the suspect(s) within the area that the call came from, if possible.\n\n2. Safety/Security will only set up an interior perimeter. They will then wait for New York City Police to arrive and take over the situation in coordination with the Safety/Security Department.\n\n3. Safety/Security will immediately call the Administrator on Call, the Director of Safety & Security and Nursing Supervisor and advise them of the situation. Based upon the situation at hand, a recall of all off duty Safety and Security officers may be completed.\n\n4. Safety/Security will meet with New York City Police to assist in guiding them to the scene. New York City Police will take over the incident.\n\n5. Safety/Security will give New York City Police THE Kingsbrook Jewish Medical Center \"Go Kit\" Containing: 6 Activated All Access Cards; Complete Set of Hospital Life Safety Drawings; Thumb Drive containing Life Safety Drawings and 2 Portable Radios on Safety/Security Channel. Go Kit is located in Command Center. Backup Go Kit located in Safety/Security office.\n\n6. Negotiations with the suspect(s) will not be conducted by members of Safety/Security or the hospital.\n\n7. At the conclusion of the Code Silver, security will complete an incident report.\n\n**Hospital Incident Command System:**\n\nThe nature and duration of a Code Silver may preclude the activation of the Hospital Incident Command System (HICS) during the event. However, as soon as the active shooter is neutralized, the HICS will be activated and the Hospital Command Center opened to address the after-action issues.\n\n**Post Event Activity**\n\n1. The HICS team shall focus on the following items during the Recovery phase:\n a. Patient and Staff accountability\n b. Facility Perimeter Control & Media Access\n c. Damage Assessment & Repair\n d. Cleanup\n e. Incident Debriefing\n\n2. The Director of Safety & Security will conduct a critique of any Code Silver event and include New York City Police to evaluate the Code Silver response, policy and procedure, and other issues.\n\n3. An After Action Report (AAR) will be completed by the Director of Emergency Management.\n\n**Training:**\n\nAll staff shall receive in-service training on this policy as soon as possible after implementation, at time of employment and at annual refresher training.\n\n**Critical Incident Stress Management:**\n\nThe Incident Commander will ensure that the Critical Incident Stress Debriefing Team is notified to provide with the necessary intervention related to psychological trauma of the event, within 48 to 72 hours.\n\n**Code Orange (Patient/Resident Elopement)**\n\n**Patient/Resident Elopement:**\nThe first step in elopement prevention is to identify patients/residents who may be at risk to wander or elope. Elopement risks are generally greatest in the first 72 hours following admission. It is important, therefore, to recognize those characteristics that can be used to identify a resident as a risk to wander or elope during the initial assessment. All clinical and Security Officers will be competenced on the Administrative policy on Elopement.\n\nA missing patient/resident can be a significant loss exposure as well as an emotional event for staff and family. Being prepared to respond to a missing patient/resident emergency is as important as preparing for other emergencies. Kingsbrook Jewish Medical Center has protocols in place and is committed to providing appropriate staff training so that\n\nreacting to this form of emergency will be efficient, orderly and effective. All employees have a role in safeguarding wandering/elope patients/residents and should be familiar with the medical center’s Elopement policy, as is necessary. Regardless of your role at the medical center, all employees need to understand the following rules for safeguarding our patients/residents:\n\n**In the event a patient with a yellow gown or wanderer is found outside of the assigned unit/floor:**\nAny staff member who observes a non-escorted, confused or previously identified wandering acute patient (Yellow Gowned)/resident attempting to leave the premises or wandering will engage the patient/resident in order to determine the individual’s appropriate unit/floor. Should the attempt fail to find their appropriate unit of origin, the staff member shall obtain assistance by dialing 555 and calling a CODE ORANGE.\n\nOther staff members in the immediate vicinity should be commandeered to assist in the management of the patient. Staff members are not to leave the patient/resident alone for any reason and should make every effort to hand off the wanderer/elopee to another coworker before making the 555 code orange call.\n\n**When a Patient/Resident is determined to be missing:**\nWhen a Patient/Resident is determined to be missing from their assigned unit/floor, Security must be notified by calling ext. 5708. Security should be provided with:\na. Clinical risk status of patient/resident, e.g. whether any psychiatric, unstable medical illness or communicable disease concerns\nb. A description of the physical characteristics of the patient/resident. Security may request staff to identify patient through review of the videotape\nc. Description of clothing patient/resident was wearing when last seen\nd. When and where the patient/resident was last seen.\n\nWhen a Patient/Resident is determined to be missing, the Nursing Supervisor, Administrator on Duty should be notified immediately. The Nursing Supervisor will ensure that the elopement is communicated to the *patient’s attending* physician. The Administrator on Duty, in conjunction with Nursing Administration, determines if the Incident Command Center should be activated. The Nursing Supervisor and Security Supervisor will collaborate to determine whether NYPD needs to be notified.\n\n## Competency Exam: Chapter 1\n\n### Safety\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. When reporting a fire, what number should you dial? | a. 1500 |\n| | b. 1600 |\n| | c. 555 |\n| | d. None of the above |\n| 2. When reporting a fire to the KJMC operator, which of the following examples would be an appropriate statement? | a. “Help, there is a fire in 813.” |\n| | b. “Dr. Yellowstone in SICU” |\n| | c. “Dr. Red,” and then provide the location |\n| | d. “Code 909 in 513” |\n| 3. The proper sequence of actions to follow when responding to a fire safety emergency are: | a. Run, announce, cry, evacuate |\n| | b. Alarm, confine, rescue, extinguish |\n| | c. Rescue, alarm, confine, extinguish |\n| | d. Call, alarm, extinguish, rescue |\n| 4. Once a fire is reported, it is then safe to use elevators. | a. True |\n| | b. False |\n| 5. What electrical hazards should be reported immediately? | a. Malfunctioning electrical equipment |\n| | b. Sparks coming from junction boxes |\n| | c. Exposed or frayed wires |\n| | d. All of the above |\n| 6. Once a crash cart is opened, it is returned to Central Supply | a. True |\n| | b. False |\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 7. Examples of an External Disaster are: a major subway or bus accident, a building collapse and a multiple car accident. | a. True |\n| | b. False |\n| 8. Which is the correct order to evacuate hospitalized patients? | a. Bedridden, ambulatory, wheelchair patients |\n| | b. Helpless, wheelchair, ambulatory patients |\n| | c. Ambulatory, bedridden, helpless patients |\n| | d. Ambulatory, wheelchair, helpless patients |\n| 9. Class B fire extinguishers are used for fires with: | a. Wood, paper, linen, mattresses |\n| | b. Oil, grease, chemicals |\n| | c. Electrical equipment and wiring |\n| | d. Wood, oil and electrical wiring |\n| 10. Operational checks for the defibrillator are performed every shift | a. With the plug in |\n| | b. With the plug out |\n| | c. With the plug in and out|\n| | d. With the battery pack removed |\n| 11. Temperatures for refrigerators on the unit should be checked: | a. Monthly |\n| | b. Weekly |\n| | c. Daily |\n| 12. The overhead page/announcement of an “Active Shooter” will be: | a. Code Black |\n| | b. Code Orange |\n| | c. Code Silver |\n| 13. The intent of most active shooters is to: | a. Frighten but not harm you |\n| | b. Harm or kill as many people as possible |\n| 14. Upon hearing a “Code Silver” on the overhead page | a. Stand still and wait for further direction |\n\n| Question | Select the correct response: |\n|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|\n| employees shall: | b. Go to the area specified in “Code Silver” \nc. Shelter in place |\n| 15. Clinical and medical staff, patients and visitors in Patient Care areas will: | a. Be directed to patient rooms or other adjacent rooms, close the door and attempt to barricade the doors \nb. Continue to perform non-urgent medical procedures and non-urgent patient movement during the incident |\n| 16. As a last resort (when your life is in imminent danger) to take action against the active shooter, attempt to disrupt and/or incapacitate the active shooter by: | a. Acting passively and attempt to calmly talk to the shooter \nb. Acting as aggressively as possible, yell, throw items and improvise weapons |\n| 17. You will know it is safe when: | a. An “All Clear” is announced overhead \nb. After ten (10) minutes of total silence |\n| 18. If I do not have a role in providing direct patient at the medical center I have a role to play in preventing confused or wandering patients/residents safety. | a. True \nb. False |\n| 19. If I see a confused or yellow gowned patient unescorted by a staff member, I should approach them, determine their unit of origin and dial 555 code orange and state my location. | a. True \nb. False |\n\nChapter 2: Hazard Communication/Body Mechanics\n\nPurpose\n\nThis module was designed to review the policy and procedures of hazard communication and the principles of proper body mechanics / injury prevention with nursing personnel.\n\nObjectives\n\nAt the completion of this module, the learner will:\n\n1. Know how to obtain information on chemical hazards in the work area\n2. Know what an SDS is and where it can be located\n3. Know the purpose of the OSHA Hazard Communication Standard\n4. Understand the policy/procedures for chemo spills State the principles of proper body mechanics\n5. Demonstrate correct posture\n6. Explain how to use proper body mechanics while lifting or moving patients and objects\n7. Identify healthy strategies that improve the chances of avoiding injury\n8. Identify steps to take in the event of an injury\n9. Complete the competency exam\n\nHazard Communication\n\n1. What is hazard communication?\n Hazard communication is a way for an employee to get information about chemical hazards in the workplace. Hazard communication books are located on all units. These books contain chemical inventory lists and a hazard communication plan explaining what to do if anything happens.\n\n2. What are hazardous materials?\n Hazardous materials are substances that are potentially dangerous to your health.\n\n3. Why do you need to know about chemical hazards?\n - For your protection – to prevent injuries and illness\n - For your safety – some substances can cause fire and serious injuries\n - For your health – some substances can cause serious health problems\n\n4. Types of hazardous material:\n - Infectious substances\n - Radioactive materials\n - Toxic chemicals\n - Flammable liquids and medical gasses\n\n5. How do you get information on chemical hazards?\n Read container labels. Report any torn or illegible labels to your supervisor. Labels not only identify chemicals but also have hazard statements, e.g., warnings, precautions, antidotes, fire/spill/leak instructions, handling and storage instructions, notes to physician.\n\n Consult the Safety Data Sheet (SDS). SDSs are provided by the manufacturer for each product they sell or produce. Every chemical used at KJMC has an associated SDS which provides background health and safety information.\n\n SDS Manuals contain an SDS for all potentially hazardous materials used in your work area. The complete SDS Manuals are found at the Security Main Desk.\n\n SDSs contain the following information:\n - Composition, treatment and antidote\n - Manufacturer’s address and telephone number\n - Instructions on storage, boiling point, melting point, etc.\n\n Protect yourself against hazards in the workplace. Educate yourself by reviewing SDSs and by reading warning labels.\n\n6. What can I do to protect myself?\n - Practice safe work habits, i.e., wash hands after contact with each patient and after removing gloves\n - Avoid overstuffing the sharps containers\n - Never recap needles\n - Gloves must be worn when performing FSBS (finger stick blood sugar) tests on patients\n - If there is a hazardous material spill, corner off the area and call Housekeeping\n - If there is a Chemo spill, corner off the area and refer to Nursing Policy and Procedure Manual, “Chemotherapy Handling and Disposal of Chemotherapy Agents”\n - The Poison Control Number is: 212-POISONS (212-764-7667) or 212-340-4494\n\nOccupational Safety and Health Administration\n\nThe Occupational Safety and Health Administration (OSHA) is the federal agency that sets guidelines for actions to protect everyone from occupational hazards.\n\nEmployee Rights Under the OSHA Standard\n\nThe purpose of the OSHA Hazard Communication Standard is to ensure that you understand the hazards of the chemicals you work with and that you know how to safely use them. Under this standard you have the following rights:\n\n1. The right to request in writing and obtain information on hazardous chemicals you come in contact with\n2. The right to be informed of the hazardous chemicals used in your work area\n3. The right of access to the Medical Center’s written hazard communication program\n4. The right to file a complaint with OSHA if you believe that you have been discriminated against by exercising your rights under this law\n\nBody Mechanics\n\nIntroducing Ergonomics\n\nIn general, ergonomics is the study of work practices with the intention of designing or adapting the work to meet the capabilities and limitations of the worker. It is an applied science concerned with how people interact with their environment. Ergonomic risk factors are conditions of a job that contribute to the risk of work-related injury.\n\nYou are at risk for back pain if you:\n\n1. Are employed in a job that requires frequent bending and lifting\n2. Keep your knees stiff and bend your back when lifting\n3. Stretch, reach or twist your body when lifting\n4. Are in a hurry and off balance when lifting and moving heavy objects\n5. Are overweight or out of shape\n6. Slouch when standing or sitting\n7. Do not exercise regularly\n8. Have stressful living or work habits\n9. Smoke\n10. Have poor nutrition\n11. Do not get enough rest\n\nResearch has shown that back injuries occur as a result of cumulative stress of the back. A single incident usually does not cause back injury. The following table outlines some of the risk factors and specific interventions you must use to reduce your chance of injury. Make a conscious effort to incorporate these strategies into your daily work practice to avoid cumulative back trauma.\n\n| Risk Factor | Possible Intervention |\n|-------------------------------------------------|----------------------------------------------------------------------------------------|\n| Lifting or moving heavy or asymmetrical objects | • Size up the load. If you feel something is too bulky or heavy to lift alone, you need to help. \n• Allow the patient to assist you if he/she is able. Give him/her instructions on how and when to move. \n• Women lifting as part of a team, it is important to avoid jerky or unexpected movements. Choose one person to be the leader and to give instructions. Count “one, two, three, lift.” \n• The body can push twice as much weight as it can pull, so push an object whenever possible. Use slide boards and pull sheets to assist in moving patient. |\n| Bending at the waist | • Maximize use of adjustable height features of electric beds. \n• Squat down, bending your knees and hips. \n• Keep your abdominal muscle firm; maintain the natural curve of the spine. Even when not lifting, squat down and don’t bend, e.g., to look in a drawer, to insert an IV, etc. |\n| Working at extended reach for long periods of time | • Place objects that are frequently needed closer to you, e.g., while doing a dressing/procedure. \n• Use step stools with a wide base of support. |\n| Twisting at the waist, especially while lifting | • Do not try to get an object off an overhead shelf by reaching or twisting your torso. \n• Use a ladder or step stool to bring your center of gravity up toward the object. \n• Take time to prepare for lifts. |\n\n**Additional Safety Strategies**\n\n1. Maintain an appropriate weight. Obesity places continuous tremendous strain on the lower back\n2. Keep in shape. Regular exercise improves your chances of avoiding injury\n3. Maintain correct posture whether you are sitting or standing\n4. Wear low-heeled, rubber-soled shoes\n5. When sitting for a prolonged period of time, remember to stand up and stretch every 20 minutes\n6. Learn stretching and strengthening exercises and stress reduction techniques\n7. Use the techniques discussed in this module at home while performing your activities of daily living (i.e., do not bend over sink while brushing teeth or twist torso to unload dishwasher, etc.)\n8. Always ask for help when needed\n\n**What to Do If You Forget to “Think Back”**\n\nIf you injure yourself while at work notify your Head Nurse, Nurse Manager or Supervisor and/or AND. The Nurse Manager or Supervisor should supply you with an Employee Incident Report and if medical intervention is required, direct you to the Employee Health Services during the day or the Emergency Department during evening, night and weekend hours.\n\n**Employees are responsible for reporting an on-the-job injury to their supervisor within 24 hours of the injury.**\n\nPhysical Therapy Corner: Protecting your Back\n\nCreating and maintaining good posture decreases your risk of developing back problems. Achieving comfortable, good posture will provide a functional range of movement that will allow you to perform daily activities safely.\n\nEven if your back feels OK at the movement, you may be straining it if you:\n\n1. Have poor posture.\n2. Move your body incorrectly.\n3. Are out of shape or overweight.\n\nAll of these strains add up until one day a simple act like bending over can bring on back pain.\n\nWhen correctly aligned the back has three curves. It curves in (forward) at your neck (1), out in the chest region (2), and in again in the lower back (3). These curves help distribute pressure evenly throughout the vertebrae and discs.\n\nBody mechanics is defined as the way in which you move your body and back. Good body mechanics includes lifting loads close to your body to reduce strain on your back and maintaining your three natural curves to keep your back in balance.\n\n**Keys to Proper Lifting**\n\n1. Stand close to the object to be lifted.\n2. Spread your feet wide apart to straddle the object.\n3. Squat, bending your knees and hips, keeping your back in proper alignment.\n4. Contract your stomach muscles.\n5. Lift by using the work of your leg muscles, not your back.\n6. When lifting with another person, one person should say when to lift, walk and unload.\n7. Do not twist as you lift. Instead, pivot with your hips and shoulders in line and shift your weight.\n8. Mentally prepare, by planning what you are going to do.\n\nKeys to Pushing and Pulling Objects\n\n1. Push, don’t pull, whenever possible.\n2. Stay close to the object.\n3. Do not lean forward.\n4. Use both arms and tighten your stomach muscles.\n5. Never push or pull with a bent back.\n\nKeys to Prolonged Standing\n\n1. Change position often.\n2. Wear comfortable shoes and stand on a soft surface.\n3. Bring your work to a comfortable level; do not bend over it.\n4. Rest one leg on a stool to reduce stress on the back.\n\nKeys to Sitting\n\n1. Sit in a chair that supports your lower back. If the chair does not support your back sufficiently, you can place a lumbar cushion (which can be bought at your local pharmacy) at the level of your low back, for added support.\n\n2. Position your chair so that your knees are at least as high as your hips when feet are flat on the floor.\n\n3. Your desktop should be slightly above your waist.\n\n4. Sit close to your work, do not lean over it.\n\n5. Do not slump over while sitting.\n\n6. Take frequent breaks to get up and stretch.\n\n**Keys to Bending and Leaning**\n\n1. Let your legs do the work.\n\n2. Stand with your feet shoulder length apart, one foot ahead of the other.\n\n3. Contract your stomach muscles.\n\n4. To lower your upper body, bend with your knees and hips, keeping your back in proper alignment. Rest one knee on the floor for extra support if needed.\n\n**Keys to Doing Repetitive Movements**\n\n1. Keep loads small if possible.\n\n2. Tighten your stomach muscles before lifting.\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. You should read the label and also look for the biohazard symbol before handling any chemicals. | a. True \nb. False |\n| 2. OSHA stands for Occupational Safety and Health Administration | a. True \nb. False |\n| 3. You should recap all needles before putting them in the sharp container. | a. True \nb. False |\n| 4. If there was a chemotherapy spill in your area the nurse would refer to the Nursing Policy and Procedure Manual under “Chemotherapy: Handling and Disposing of Chemo Agents.” | a. True \nb. False |\n| 5. SDS stands for Safety Data Sheets. | a. True \nb. False |\n| 6. Which steps are necessary for anyone who works with hazardous materials to do in order to maintain their safety? | a. Be aware of the information contained in the SDS \nb. Be aware if any substance or chemical that you may be exposed to while working on your units \nc. Seek medical treatment for any accidental hazardous material exposure \nd. All of the above |\n| 7. The three general concepts that relate to strategies of specific body mechanics are posture, center of gravity and proper muscle use. | a. True \nb. False |\n| 8. When lifting or moving heavy or asymmetrical objects you should: | a. Size up the load. If you feel something is too bulky or heavy to lift alone, you need to get help. \nb. Lift or move any object regardless of the size by yourself. \nc. Lift or move the object with jerky and unexpected movements. |\n| 9. If you hurt your back, you should fill out an Employee Incident Report. | a. True \nb. False |\n| 10. When lifting you should do the following: | a. Do not try to get an object off an overhead shelf by reaching or twisting your torso. \nb. Use a ladder or step stool to bring your center of gravity up toward the object. \nc. Take time to prepare for lifts. \nd. Do not change direction by twisting at the waist. \ne. All of the above. |\n| 11. When lifting you should tighten: | a. Your back muscles \nb. Your leg muscles \nc. Your stomach muscles \nd. Your arm muscles |\n| 12. When lifting you should keep objects close to your body and lift using your leg muscles. | a. True \nb. False |\n\nChapter 3: Infection Control/ Bio-Terrorism Management\n\nPurpose\n\nThis module was designed to provide written rules, regulations and procedures for specific precautions to prevent and control the spread of infection.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. State the principles of proper hand washing\n2. Define Standard/Universal Precautions\n3. Define blood and body fluid exposure\n4. List the steps necessary in the management of blood and body fluid exposure\n5. Describe the communication procedure used to identify that a patient is on Isolation Precautions\n6. Define Contact Precautions\n7. Identify the signs and symptoms of Hepatitis B\n8. Describe the process of Hepatitis B transmission\n9. Describe the Hepatitis B Vaccination Program\n10. Define Airborne Precautions\n11. List the patients who are at high risk for the development of tuberculosis\n12. State when Airborne Precautions may be discontinued\n13. Identify the purpose and frequency of PPD testing\n14. Define Droplet Precautions\n15. State when Droplet Precautions should be used\n16. Identify where to obtain information on caring for a patient exposed to terrorism\n\nHand Washing/Hand Hygiene\n\nHand washing is defined as vigorous, brief rubbing together of all surfaces of lathered hands, followed by rinsing under water. Hand washing with soap is the mechanical removal of dirt and microbes through friction.\n\nThe Center for Disease Control recommends a 15-20 second hand wash to remove most transient or temporary contaminants from the skin.\n\nAlways wash your hands:\n\n1. Before and after patient contact\n2. Before and after touching wounds\n3. After contact with any mucous membranes (eyes, nose, mouth), blood or body fluids, secretion or excretions\n4. After removing gloves\n\nYou should always wash your hands before preparing food, after using the bathroom, before you leave your unit for breaks and at the end of your shift.\n\nWaterless alcohol hand sanitizer\n\nAlcohol based waterless hand sanitizer has been designated by the Center for Disease Control (CDC) as a highly effective germicidal product for use in sanitizing the hands before and after patient contact and after removing gloves. Is designated for use on hands, which are not visibly soiled with blood or body fluid. For hands, which are visibly soiled, soap and water should be used to clean hands before applying waterless sanitizer.\n\nWaterless hand sanitizer dispensers are located in all patient/resident care areas in both KJMC and RNH. They are mounted on the wall near the exit of patient rooms and are also located in various other areas where hand hygiene is performed.\n\nThe performance of hand hygiene after patient contact is very important in preventing the spread of infections. Please use soap and water, or waterless hand sanitizer before and after each direct patient contact. Observational monitoring of staff compliance, to assure that this is occurring, is ongoing in all areas of the Medical Center.\n\nInstructions for use\n\n1. Apply to hands, which are not visibly soiled\n2. If hands are visibly soiled, wash with soap and water before using waterless hand sanitizer\n3. Rub palms of hands together to distribute sanitizer to all parts of the hand including under and around fingernails\n4. Allow to air dry. Do not wash off with water\n\nStandard/Universal Precautions\n\nThe concept of Standard/Universal Precautions is a set of guidelines recommended by the U.S. Centers for Disease Control. Standard/Universal Precautions are designed to reduce the risk of transmission of microorganisms from both recognized and unrecognized sources of infections in hospitals. Standard/Universal Precautions apply to (1) blood, (2) all body fluids, secretions, and excretions (except sweat), regardless of whether they contain visible blood, (3) non-intact skin, and (4) mucous membranes.\n\nKJMC mandates that you apply Standard/Universal Precautions in the care of all patients regardless of their diagnosis.\n\nThe term Standard/Universal Precautions is used by OSHA.\n\nStandard/Universal Precautions means you must always:\n\n1. WEAR GLOVES when your hands may come in contact with blood, body fluids or mucous membranes. For example, put on gloves when drawing blood, starting or handling an IV, doing finger sticks, suctioning (whether oral or nasal), handling contaminated instruments, cleaning blood or body fluid spills, handling soiled linen or waste, and in all other situations where contact with blood or body fluids may occur. GLOVES MUST BE CHANGED AND HAND HYGIENE PERFORMED BETWEEN EACH NEW PATIENT CONTACT.\n\n2. WEAR GOWNS/APRONS when your skin or clothing may be soiled by blood or body fluids. Use the impervious gown if splashing or large quantities of blood are present or anticipated. For example, wear a gown during endoscopies, intubations, hemodialysis and all surgical procedures.\n\n3. USE MASK/EYEWEAR if there is a possibility that you may be splashed, sprayed or splattered with blood or body fluids. Eyewear includes goggles, safety glasses or eyeglasses. Face protection is provided by wearing a face shield, or eyewear and mask worn together.\n\n4. PERFORM HAND HYGIENE IMMEDIATELY after taking off your gloves. Hands and other skin surfaces should be washed immediately and thoroughly if contaminated with blood or other body fluids. Gloves are not a substitute for hand washing. REMEMBER TO WASH YOUR HANDS AFTER ALL PATIENT CONTACT.\n\n5. MANAGE SKIN CONDITIONS by reporting to Employee Health Services (EHS) for evaluation and by using gloves and contact precautions if you have cuts, abraded skin, chapped hands, or dermatitis. If you have weeping dermatitis or open wounds that are draining, you should refrain from all direct patient care and from handling patient care equipment until the condition is resolved.\n\n6. PREVENT INJURIES by disposing of sharps immediately after use. Place all needles, syringes and scalpel blades and other sharps only in designated puncture-resistant sharp containers.\n\nNEVER RECAP NEEDLES. Prevent injury to yourself and others by never leaving sharps on bedside tables, in your clothing pockets or in mattresses, linen or garbage cans. Correct coworkers who dispose of sharps inappropriately.\n\n7. REPORT EXPOSURES IMMEDIATELY to your supervisor and EHS. All treatment of an exposed person is provided by EHS during clinical hours. On holidays and all other times, treatment of an exposed person is provided in the Emergency Department. An Incident Report documenting the exposure must be completed. If initial treatment is done in the ED, follow up will be done by EHS.\n\nA BLOOD/BODY FLUID EXPOSURE is defined as:\n\n- A needle stick or sharps puncture wound\n\n- An open cut, burn or abrasion contaminated by body fluids or tissues (blood, blood products, bloody fluids, semen, cerebrospinal fluid, amniotic fluid, pleural fluid, peritoneal fluid, pericardial fluid or any other body fluid or tissue contaminated with blood)\n\n- A blood or body fluid splash to mucous membranes (e.g., eye, nose or mouth) with such materials.\n\nFor a needle stick or body fluid exposure you should follow the Procedures for Evaluation and Treatment of Occupational Exposure to Blood or Body Fluids. Some highlights are:\n\nClean the wound with soap and water or flush mucous membranes with water/saline\n\nReport the incident to your supervisor immediately\n\nThe employee is required to complete and submit an Incident Report\n\nThe employee must report to EHS as soon after an incident as possible. When EHS is closed the employee must report to the Emergency Department immediately and follow up in the EHS on the next working day. If the EHS is closed, the ER Department will provide a temporary supply of anti-HIV drugs\n\nIf you are stuck with a needle from an unidentifiable source and the blood or body fluid is still available call Infection Control to arrange for the testing of the fluid\n\nIf you are stuck with a needle from a known person, the source will be asked to sign an informed consent to have HIV testing performed. Informed consent is mandated by New York State law. In the EHS Department there will be a counselor available to discuss this issue with the person who is the source of the needle.\n\nYour treatment will include evaluation of your Hepatitis B surface antibody. You may be offered treatment for Hepatitis B exposure and Tetanus\n\nYou may be offered HIV prophylaxis. EHS will provide counseling. Pharmacy will provide medication counseling\n\nAll exposed persons will receive counseling by the clinician at the time of initial visit to discuss the nature and severity of the exposure, treatments available, HIV testing, confidentiality, deferment of blood donation, safe sex practices and prevention of further workplace exposure\n\nAll medical and other hospital records pertaining to the exposed person’s exposure will be kept confidential in accordance with applicable New York State law. All “HIV-Related Information” must have stringent confidentiality. Testing for the antibody mandates the strictest confidence both for you and the source of your exposure.\n\nYou will be given an Health Care provider’s written opinion. The employee will be provided with a copy of the evaluating health care provider’s opinion within 15 days of the completion of the evaluation of an exposure report.\n\nSeven Things Every Employee Needs to Know About Needle Sticks and Other Exposures to Blood or Body Fluid\n\n1. What is an exposure to blood or body fluid and how do they occur?\n\nThe most common way an exposure occurs is through a patient’s blood or body fluid being introduced into your body through a blood or body fluid contaminated needle stick or laceration. This is known as a “percutaneous exposure.”\n\n2. Is “percutaneous exposure” the only way someone can be exposed?\n\nOther exposures occur when blood or body fluids contact a mucous membrane such as those in the mouth, nose or eyes or through contact with non-intact skin (skin with cuts, open sores, chapping or dermatitis). Bites that break the skin are another potential source of transmission. If a large blood spill occurs in intact skin, this may also require assessment and follow-up.\n\n3. Why do I need to be concerned about “exposure” to blood or body fluid?\n\nBlood and body fluid may be infected with blood borne pathogens, microorganisms (viruses and bacteria) that live in the blood of infected people and may be transmitted to others following an exposure to infected blood or body fluid.\n\n4. What are some blood-borne pathogens?\n\nHIV (human immunodeficiency virus) that causes AIDS and Hepatitis B and C, which cause Hepatitis, a liver disease, are the most common blood borne pathogens. However, some other infections can also be transmitted in this manner. Infections with blood borne pathogens can lead to serious illness.\n\n5. If I am exposed to blood or body fluid will I become sick?\n\nYour risk of becoming ill following an exposure depends on a number of things:\n\n- If the individual’s blood, to which you have been exposed, has no blood borne pathogens then you have **no risk** of transmission\n\n- Exposure to the blood or body fluid of an individual with AIDS has an approximately 1 in 250 risk of transmission. Exposure to Hepatitis C has a transmission risk of about 1 in 60 and for Hepatitis B the risk is 1 in 35 (for example, for every 35 people who are exposed to blood or body fluid of a person who has Hepatitis B, one person will become ill with the disease).\n\n6. Can I take a vaccine to prevent illness by blood borne pathogens?\n\nHepatitis B is the most common blood borne pathogen and the most contagious. There is currently a safe and effective vaccine available to protect you from Hepatitis B. Ask your doctor or EHS for details.\n\n7. What should I do if I have an exposure to blood or body fluid?\n\n- If you have a percutaneous exposure, wash needle stick or laceration site with soap and running water for several minutes. If the wound is bleeding freely, allow it to bleed for several minutes. Do not force bleeding by squeezing the site of the puncture.\n\n- If the exposure occurs due to a splash of blood or body fluid into the eyes or mouth, rinse under running water for several minutes\n\n- It is very important to be seen by a physician as soon as possible (within less than two hours following exposure)\n\n- Tell your supervisor of the exposure and report without delay to EHS (Monday through Thursday, 9:00 a.m. – 5:00 p.m.; Friday, 9:00 a.m. – 2:00 p.m.). At all other times report to the Emergency Room for follow-up, counseling, testing and treatment\n\n- There are drug treatments that have been shown to greatly reduce the risk of acquiring AIDS if taken after an exposure but treatment must begin quickly for the drugs to be effective. The New York State Department of Health recommends that treatment begin within 1-2 hours after exposure for maximum effectiveness. However, the treatment may still be effective up to 36 hours after exposure.\n\n**Infection Control Measures for Patient/Resident Requiring Isolation Precautions**\n\n**Contact Precautions**\n\nPersonal protective equipment required to prevent spread of microorganisms by the contact route include gloves and gown. Add eye protection if splashing of blood or body fluids is anticipated. Gloves should be removed before leaving the room. Always wash hands after removal of gloves. Examples of microorganisms spread by the contact route are C difficile, VRE and MRSA.\n\nDroplet Precautions\n\nPatients and residents on droplet precautions require similar protective equipment as a person on contact precautions with the addition of a regular surgical mask for contact within a three-foot radius of the patient. Consider all fomites within the three-foot radius as potentially contaminated. Remove all protective equipment before leaving the room and wash hands.\n\nExamples of microorganisms spread by the droplet route include H. influenza and Mycoplasma as well as Acinetobacter and possible MRSA (in respiratory tract). The patient on droplet precautions should be transported for essential purposes only. **Clean gown and mask patient with surgical mask during transport.**\n\nStandard Precautions\n\nAll patients and residents are considered to potentially harbor infectious microorganisms or blood borne pathogens. Therefore, barrier items such as gloves, gown and mask are used to prevent contact with blood or body fluids.\n\nAirborne Precautions in Acute Care\n\nApplies to patients known or suspected to be infected with epidemiologically important pathogens that can be transmitted by airborne route. Examples include Measles, Tuberculosis (AFB) and Varicella.\n\nAll staff entering the negative pressure room must wear a N-95 mask. Patients must be in a private room with negative pressure and HEPA filtration with the door closed at all times.\n\nThe patient should be transported for essential purposes only. Use a surgical mask on patients during transport.\n\nCLEAN-UP OF SPILLS OF BLOOD AND OTHER POTENTIALLY INFECTIOUS MATERIALS\n\nAny employee may at times be required to assist in the cleanup or containment of spills of blood body fluid or other potentially infectious materials. The following procedure should be followed.\n\n**Procedure 1**\n\n1. Don gloves. Also use gown, mask and goggles or eye shield if splashing is possible.\n2. Isolate the area of the spill to prevent traffic flow through area.\n3. Cover spill with a solution of 1:10 freshly prepared bleach.\n4. Allow disinfectant to act for 10 minutes\n5. Use absorbent paper towels or other absorbing material to clean spill\n6. If broken glass is present do not touch with hands - use broom and dust pan to remove glass after disinfection and discard into sharps container.\n7. Discard towels or absorbent containing spilled material in red bag waste\n8. Discard gloves, gown and other protective equipment in regular trash unless saturated with blood or body fluid (which would require discard in red bag waste)\n9. Wash hands with soap and water after removing personal protective equipment or use alcohol based hand sanitizer.\n10. Call building services to sanitize area\n\n**Procedure 2**\n\n1. Isolate the area of spill to prevent traffic through area\n2. Notify building services of spill\n3. Building services will assign staff to clean up spill\n\nCOMMUNITY SHARPS DISPOSAL PROGRAM\n\nKingsbrook Jewish Medical Center/Rutland Nursing Home has a community sharps disposal program that complies with New York State Department of Health Chapter 438 laws of 1993.\n\nPeople in the community may dispose of their sharps/containers anonymously by placing them in our community sharps/needle disposal unit. Employees are not to handle sharps from the community; people wanting to dispose of sharps are instructed to place their sharps/containers in the community needle box disposal unit.\n\n**LOCATION:** The community sharps disposal container is located at the entrance to the emergency room located on Winthrop Ave between East 49th street and Schenectady Avenue.\n\n**TIME:** Members of the community may drop off their sharps 7 days per week, 24 hours per day\n\nCARBAPENEM RESISTANT KLEBSIELLA (CRE)\n\n**Background:** Some *Klebsiella* bacteria (Gram negative rods) have become highly resistant to antibiotics. When bacteria such as *Klebsiella pneumoniae* or E coli produce an enzyme known as a carbapenemase, then the class of antibiotics called carbapenems (i.e. imipenem, meropenem, ertapenem) will not work to kill the bacteria and treat the infection. These bacteria are know by the general term CRE, which stands for carbapenem-resistant Enterobacteriaceae. Unfortunately, carbapenem antibiotics often are the last line of defense against Gram-negative infections that are resistant to other antibiotics. Infections caused by these bacteria can be difficult to treat because fewer antibiotics are effective against them.\n\nGeneral Information: *Klebsiella* is a type of bacteria that can cause different types of healthcare-associated infections, including pneumonia, bloodstream infections, urinary tract infections wound or surgical site infections, and meningitis. Increasingly, *Klebsiella* bacteria have developed antimicrobial resistance, most recently to the class of antibiotics known as carbapenems.\n\nIn healthcare settings, *Klebsiella* infections commonly occur among sick patients who are receiving treatment for other conditions. Patients whose care requires devices like ventilators, intravenous or Foley catheters, and patients who are taking long courses of certain antibiotics are most at risk for *Klebsiella* infections. Healthy people usually do not get *Klebsiella* infections.\n\n**How Klebsiella bacteria are spread:** To get a *Klebsiella* infection, a person must be exposed to the bacteria. For example, *Klebsiella* must enter the respiratory tract to cause pneumoniae, or the blood to cause a bloodstream infection.\n\nIn healthcare settings, *Klebsiella* bacteria can be spread through person-to-person contact (for example, from patient to patient via the contaminated hands of healthcare personnel, or other persons) or, less commonly, by contamination of the environment. The bacteria are not spread through the air.\n\nPatients in healthcare settings also may be exposed to *Klebsiella* when they are on ventilators, or have intravenous catheters or wounds (caused by injury or surgery). Unfortunately, these medical tools and conditions may allow *Klebsiella* to enter the body and cause infection.\n\n**Preventing Klebsiella from spreading:** To prevent spreading *Klebsiella* infections between patients, healthcare personnel must follow specific infection control precautions. These precautions may include strict adherence to hand hygiene and wearing gowns and gloves when they enter rooms where patients with *Klebsiella*-related illnesses are housed. Healthcare facilities also must follow strict cleaning procedures to prevent the spread of *Klebsiella*.\n\n**CENTRAL LINE ASSOCIATED INFECTIONS (CLABS)**\n\nA “central line” or “central catheter” is a tube that is placed into a patient’s large vein, usually in the neck, chest, arm, or groin. The catheter is often used to draw blood, or give fluids or medications. It may be left in place for several weeks. A bloodstream infection can occur when bacteria or other germs travel down a “central line” and enter the blood. If you develop a catheter-associated bloodstream infection you may become ill with fevers and chills or the skin around the catheter may become sore and red.\n\n**CLOSTRIDIUM DIFFICILE INFECTIONS**\n\n*What is Clostridium difficile infection?*\n\n*Clostridium difficile* [pronounced Klo-STRID-ee-um dif-uh-SEEL], also known as “C. diff” [See-dif], is a germ that can cause diarrhea. Most cases of *C. diff* infection occur in patients taking antibiotics. The most common symptoms of a *C. diff* infection include:\n\n- Watery diarrhea\n- Fever\n- Loss of appetite\n- Nausea\n- Belly pain and tenderness\n\n*Who is most likely to get C. diff infection?*\n\nThe elderly and people with certain medical problems have the greatest chance of getting *C. diff*. *C. diff* spores can live outside the human body for a very long time and may be found on things in the environment such as bed linens, bed rails, bathroom fixtures, and medical equipment. *C. diff* infection can spread from person-to-person on contaminated equipment and on the hands of doctors, nurses, other healthcare providers and visitors.\n\n**MRSA INFECTIONS: METHICILLIN RESISTANT STAPH AUREUS**\n\n*What is MRSA?*\n\n*Staphylococcus aureus* (pronounced staff-ill-oh-KOK-us AW-ree-us), or “*Staph*” is a very common germ that about 1 out of every 3 people have on their skin or in their nose. This germ does not cause any problems for most people who\n\nhave it on their skin. But sometimes it can cause serious infections such as skin or wound infections, pneumonia, or infections of the blood.\n\nAntibiotics are given to kill Staph germs when they cause infections. Some *Staph* are resistant, meaning they cannot be killed by some antibiotics.\n\n*Methicillin-resistant Staphylococcus aureus* or “MRSA” is a type of *Staph* that is resistant to some of the antibiotics that are often used to treat *Staph* infections.\n\n**Who is most likely to get an MRSA infection?**\nIn the hospital, people who are more likely to get an MRSA infection are people who:\n\n- have other health conditions making them sick\n- have been in the hospital or a nursing home\n- have been treated with antibiotics.\n\nPeople who are healthy and who have not been in the hospital or a nursing home can also get MRSA infections. These infections usually involve the skin.\n\n### SURGICAL SITE INFECTIONS\n\n**What is a Surgical Site Infection (SSI)?**\nA surgical site infection is an infection that occurs after surgery in the part of the body where the surgery took place. Most patients who have surgery do not develop an infection. However, infections develop in about 1 to 3 out of every 100 patients who have surgery. Some of the common symptoms of a surgical site infection are:\n\n- Redness and pain around the area where you had surgery\n- Drainage of cloudy fluid from your surgical wound\n- Fever\n\n**Can SSIs be treated?**\nYes. Most surgical site infections can be treated with antibiotics. The antibiotic given to you depends on the bacteria (germs) causing the infection. Sometimes patients with SSIs also need another surgery to treat the infection.\n\n**What are some of the things that hospitals are doing to prevent SSIs?**\nTo prevent SSIs, doctors, nurses, and other healthcare providers:\n\n- Clean their hands and arms up to their elbows with an antiseptic agent just before the surgery.\n- Clean their hands with soap and water or an alcohol-based hand rub before and after caring for each patient.\n- May remove some of your hair immediately before your surgery using electric clippers if the hair is in the same area where the procedure will occur. They should not shave you with a razor.\n- Wear special hair covers, masks, gowns, and gloves during surgery to keep the surgery area clean.\n- Give you antibiotics before your surgery starts. In most cases, you should get antibiotics within 60 minutes before the surgery starts and the antibiotics should be stopped within 24 hours after surgery.\n- Clean the skin at the site of your surgery with a special soap that kills germs.\n\n### CATHETER ASSOCIATED URINARY TRACT INFECTIONS\n\n**What is “catheter-associated urinary tract infection”?**\nA urinary tract infection (also called “UTI”) is an infection in the urinary system, which includes the bladder (which stores the urine) and the kidneys (which filter the blood to make urine). Germs (for example, bacteria or yeasts) do not normally live in these areas; but if germs are introduced, an infection can occur.\n\nIf you have a urinary catheter, germs can travel along the catheter and cause an infection in your bladder or your kidney; in that case it is called a catheter-associated urinary tract infection (or “CA-UTI”).\n\n**What is a urinary catheter?**\nA urinary catheter is a thin tube placed in the bladder to drain urine. Urine drains through the tube into a bag that collects the urine. A urinary catheter may be used:\n\n- If you are not able to urinate on your own\n- To measure the amount of urine that you make, for example, during intensive care\n- During and after some types of surgery\n- During some tests of the kidneys and bladder\n\nPeople with urinary catheters have a much higher chance of getting a urinary tract infection than people who don’t have a catheter.\n\nHow do I get a catheter-associated urinary tract infection (CA-UTI)?\nIf germs enter the urinary tract, they may cause an infection. Many of the germs that cause a catheter-associated urinary tract infection are common germs found in your intestines that do not usually cause an infection there. Germs can enter the urinary tract when the catheter is being put in or while the catheter remains in the bladder.\n\nWhat are the symptoms of a urinary tract infection?\nSome of the common symptoms of a urinary tract infection are:\n• Burning or pain in the lower abdomen (that is, below the stomach)\n• Fever\n• Bloody urine may be a sign of infection, but is also caused by other problems\n• Burning during urination or an increase in the frequency of urination after the catheter is removed.\n\nSometimes people with catheter-associated urinary tract infections do not have these symptoms of infection.\n\nCan catheter-associated urinary tract infections be treated?\nYes, most catheter-associated urinary tract infections can be treated with antibiotics and removal or change of the catheter. Your doctor will determine which antibiotic is best for you.\n\nDONNING AND DOFFING OF PERSONAL PROTECTIVE EQUIPMENT (PPE)\nThe type of PPE used will vary based on the level of precautions required; e.g., Standard, Contact, Droplet or Airborne precautions.\n\nUSE SAFE WORK PRACTICES TO PROTECT YOURSELF AND LIMIT THE SPREAD OF CONTAMINATION.\nKeep hands away from face. Limit surfaces touched. Change gloves when torn or heavily contaminated. Perform hand hygiene after removing gloves.\n\nSEQUENCE FOR DONNING PERSONAL PROTECTIVE EQUIPMENT (PPE)\nDon PPE in the following order: gown>mask>goggles> gloves\n\n1. GOWN:\nPut on gown before entering patient room\nFully cover torso from neck to knees, arms to end of wrists, and wrap around the back.\nFasten in back of neck and waist\n\n2. MASK OR RESPIRATOR:\nPut on mask or respirator before entering patient room\nSecure ties or elastic bands at middle of head and neck.\nFit flexible band to nose bridge.\nFit snug to face and below chin.\nFit-check respirator (N-95)\n\n3. GOGGLES OR FACE SHIELD:\nPlace over face and eyes and adjust to fit\n\n4. GLOVES:\n • Extend to cover wrist of isolation gown\n\nSEQUENCE FOR REMOVING PERSONAL PROTECTIVE EQUIPMENT (PPE)\nRemove PPE in the following order: Gloves>goggles>gown>mask\n\n1. GLOVES:\n • Outside of gloves is contaminated!\n • Grasp outside of glove with opposite gloved hand; peel off.\n • Hold removed glove in gloved hand.\n • Slide fingers of ungloved hand under remaining glove at wrist.\n • Peel glove off over first glove.\n • Discard gloves in waste container\n\n2. GOGGLES OR FACE SHIELD:\n - Outside of goggles or face shield is contaminated!\n - To remove, handle by head band or ear pieces.\n - Place in designated receptacle for reprocessing or in waste container\n\n3. GOWN:\n - Gown front and sleeves are contaminated!\n - Unfasten ties.\n - Pull away from neck and shoulders, touching inside of gown only.\n - Turn gown inside out.\n - Fold or roll into a bundle and discard.\n\n4. MASK OR RESPIRATOR:\n - Front of mask/respirator is contaminated —DO NOT TOUCH!\n - Grasp bottom, then top ties or elastics and remove.\n - Discard in waste container\n - Except for respirator, remove PPE at doorway or in anteroom.\n - Remove respirator after leaving patient room and closing door.\n\nRef: CDC sequence for donning and doffing PPE\n\nSEQUENCE FOR DONNING PERSONAL PROTECTIVE EQUIPMENT (PPE)\n\nThe type of PPE used will vary based on the level of precautions required; e.g., Standard and Contact, Droplet or Airborne Infection Isolation.\n\n1. GOWN\n- Fully cover torso from neck to knees, arms to end of wrists, and wrap around the back\n- Fasten in back of neck and waist\n\n2. MASK OR RESPIRATOR\n- Secure ties or elastic bands at middle of head and neck\n- Fit flexible band to nose bridge\n- Fit snug to face and below chin\n- Fit-check respirator\n\n3. GOGGLES OR FACE SHIELD\n- Place over face and eyes and adjust to fit\n\n4. GLOVES\n- Extend to cover wrist of isolation gown\n\nUSE SAFE WORK PRACTICES TO PROTECT YOURSELF AND LIMIT THE SPREAD OF CONTAMINATION\n- Keep hands away from face\n- Limit surfaces touched\n- Change gloves when torn or heavily contaminated\n- Perform hand hygiene\n\nSEQUENCE FOR REMOVING PERSONAL PROTECTIVE EQUIPMENT (PPE)\n\nExcept for respirator, remove PPE at doorway or in anteroom. Remove respirator after leaving patient room and closing door.\n\n1. GLOVES\n- Outside of gloves is contaminated!\n- Grasp outside of glove with opposite gloved hand; peel off\n- Hold outside of glove in gloved hand\n- Slide fingers of ungloved hand under remaining glove or wrist\n- Peel glove off over first glove\n- Discard gloves in waste container\n\n2. GOGGLES OR FACE SHIELD\n- Outside of goggles or face shield is contaminated!\n- To remove, handle by head band or ear loops\n- Place in designated receptacle for reprocessing or in waste container\n\n3. GOWN\n- Gown front and sleeves are contaminated!\n- Unfasten ties\n- Pull away from neck and shoulders, touching inside of gown only\n- Turn gown inside out\n- Fold or roll into a bundle and discard\n\n4. MASK OR RESPIRATOR\n- Front of mask/respirator is contaminated — DO NOT TOUCH!\n- Grasp bottom, then top ties or elastics and remove\n- Discard in waste container\n\nPERFORM HAND HYGIENE IMMEDIATELY AFTER REMOVING ALL PPE\n\nSECUENCIA PARA PONERSE EL EQUIPO DE PROTECCIÓN PERSONAL (PPE)\n\nEl tipo de PPE que se debe utilizar depende del nivel de precaución que sea necesario; por ejemplo, equipo Estándar y de Contacto o de Aislamiento de infecciones transportadas por gotas o por aire.\n\n1. BATA\n- Cubra con la bata todo el torso desde el cuello hasta las rodillas, (las mangas hasta la muñeca y déjelas abiertas para la exposición).\n- Atésela por detrás a lo altura del cuello y la cintura\n\n2. MÁSCARA O RESPIRADOR\n- Asegúrese las correas o la banda elástica en la mitad de la cabeza y en el cuello\n- Ajuste la banda flexible en el puente de la nariz\n- Acomódelos en la cara y por debajo del mentón\n- Verifique el ajuste del respirador\n\n3. GAFAS PROTECTORAS O CARETAS\n- Colóquelas sobre la cara y los ojos y ajustelas\n\n4. GUANTES\n- Extienda los guantes para que cubran la parte del pulso en la bata de aislamiento\n\nUTILICE PRÁCTICAS DE TRABAJO SEGURAS PARA PROTEGERSE USTED MISMO Y LIMITAR LA PROPAGACIÓN DE LA CONTAMINACIÓN\n- Mantenga las manos alejadas de la cara\n- Límite el contacto con superficies\n- Cambie los guantes si se rompen o están demasiado contaminados\n- Realice la higiene de las manos\n\nSECUENCIA PARA QUITARSE EL EQUIPO DE PROTECCIÓN PERSONAL (PPE)\n\nCon la excepción del respirador, quitese el PPE en lo estrecho de la puerta o en el antecámara, antes de entrar, después de salir de la habitación del paciente y de cerrar la puerta.\n\n1. GUANTES\n- ¿El exterior de los guantes está contaminado?\n- Agarre la parte exterior del guante con la mano contraria en la que todavía tiene puesto el guante y quite el guante\n- Sostenga el guante que se quitó con la mano asegurándose\n- Doble los dedos de la mano sin guante por debajo del otro guante que no se ha quitado todavía o a lo alrededor de la muñeca\n- Quitese el guante de mano que acabé cubriendo el primer guante\n- Arroje los guantes en el recipiente de desechos\n\n2. GAFAS PROTECTORAS O CARETA\n- ¿El exterior de las gafas protectoras o de la careta está contaminado?\n- Para quitarlas, agarrelas por la parte de la banda de los ojos o de las correas de los ojos\n- Colóquelas en el recipiente designado para reprocessar materiales o de materiales de deshecho\n\n3. BATA\n- ¿La parte delantera de la bata y las mangas están contaminadas?\n- Desate los cordones\n- Girando solamente el interior de la bata, pásela por encima del cuello y de los hombros\n- Voltee la bata al revés\n- Doblela o enrollala y desechela\n\n4. MÁSCARA O RESPIRADOR\n- La parte delantera de la mascarilla o respirador está contaminada — ¡NO TOQUE!\n- Primero agarre la parte de abajo, luego los cordones o banda elástica de arriba y por último quitese la máscara o respirador\n- Arrojelo en el recipiente de desechos\n\nEFFECTUE LA HIGIENE DE LAS MANOS INMEDIATAMENTE DESPUÉS DE QUITARSE CUALQUIER EQUIPO DE PROTECCIÓN PERSONAL\n\nGLUCOMETER CLEANING AND DISINFECTION BETWEEN PATIENT AND RESIDENT USE\n\nThe use of shared Glucometers between patients and Residents may be associated with risk of cross infection if not properly cleaned/disinfected between each patient/resident use. Use clean disposable gloves for cleaning and discard between each use.\n\n1. Glucometer must be cleaned and disinfected between each patient or resident use.\n2. Don gloves to remove bleach wipe from canister\n3. Use a moist, 1:10 Clorox germicidal wipe (1:10 bleach) to clean the external surface of the Glucometer.\n4. Use a second moist Clorox germicidal wipe (1:10 Bleach) to disinfect the surface of the Glucometer\n5. The disinfectant must remain on the surface of the Glucometer for at least one minute to assure adequate disinfection time to kill viruses and bacteria.\n6. If the Glucometer is still damp after one minute the Glucometer it may be dried with a clean tissue before use on the next patient\n7. Discard gloves and wipe in regular trash can.\n\nNYS Hepatitis C Testing Law\n\nRationale: Persons born between 1945 and 1965 are five times more likely to be infected with hepatitis C (HCV). The prevalence is 3.25% among the 1945-1965 birth cohort vs. 0.88% among individuals outside of the birth cohort.\n\nThe benefits of early HCV diagnosis and care include:\n\n1. Reduce risk of transmission to others\n2. Early clinical evaluation and ongoing monitoring and treatment\n3. Treatment response decreases as liver disease progresses\n4. Measures can be taken to protect liver from further harm\n a. Vaccination against Hep A and Hep B\n b. Counseling to decrease alcohol consumption\n\nKey provisions of NYS Hepatitis C testing law\n\nBeginning on January 1st 2014 a hepatitis C screening test is to be offered to every individual born between 1945 and 1965 for:\n\n- Inpatients of a hospital\n- Individuals receiving primary care services (including family medicine, general pediatrics, primary care, internal medicine, primary care obstetrics or primary care gynecology) in the outpatient department of a hospital\n- Individuals in a freestanding diagnostic or treatment center\n- From a physician, physician assistant or nurse practitioner providing primary care regardless of setting type.\n\nThe offer for testing must be culturally and linguistically appropriate.\n\nIf an individual accepts the offer and the screening test is reactive, the health care provider must offer the individual follow-up health care or refer the individual to a health care provider who can provide follow-up health care.\n\nSAFE INJECTION PRACTICES\n\nInjection safety (or safe injection practices): A set of measures taken to perform injections in an optimally safe manner for patients, healthcare personnel, and others. A safe injection does not harm the recipient, does not expose the provider to any avoidable risks and does not result in waste that is dangerous for the community. Injection safety includes practices intended to prevent transmission of bloodborne pathogens between one patient and another, or between a healthcare worker and a patient, and also to prevent harms such as needlestick injuries.\n\nSafe injection practices and procedures designed to prevent disease transmission from patient to patient and from healthcare workers to patient.\n\n1. Maintain aseptic technique throughout all aspects of injection preparation and administration\n\na. Medications should be drawn up in a designated \"clean\" medication area that is not adjacent to areas where potentially contaminated items are placed.\n\nb. Use a new sterile syringe and needle to draw up medications while preventing contact between the injection materials and the non-sterile environment.\n\nc. Ensure proper hand hygiene before handling medications.\n\nd. If a medication vial has already been opened, the rubber septum should be disinfected with alcohol prior to piercing it.\n\ne. Never leave a needle or other device (e.g. “spikes”) inserted into a medication vial septum or IV bag/bottle for multiple uses. This provides a direct route for microorganisms to enter the vial and contaminate the fluid.\n\nf. Medication vials should be discarded upon expiration or any time there are concerns regarding the sterility of the medication.\n\ng. Never administer medications from the same syringe to more than one patient, even if the needle is changed.\n\nh. Never use the same syringe or needle to administer IV medications to more than one patient, even if the medication is administered into the IV tubing, regardless of the distance from the IV insertion site.\n\ni. All of the infusion components from the infusate to the patient's catheter are a single interconnected unit.\n\nj. All of the components are directly or indirectly exposed to the patient's blood and cannot be used for another patient.\n\nk. Syringes and needles that intersect through any port in the IV system also become contaminated and cannot be used for another patient or used to re-enter a non-patient specific multi-dose vial.\n\nl. Separation from the patient's IV by distance, gravity and/or positive infusion pressure does not ensure that small amounts of blood are not present in these items.\n\nm. Never enter a vial with a syringe or needle that has been used for a patient if the same medication vial might be used for another patient.\n\nn. Dedicate vials of medication to a single patient.\n\no. Medications packaged as single-use must never be used for more than one patient:\n 1. Never combine leftover contents for later use;\n 2. Medications packaged as multi-use should be assigned to a single patient whenever possible\n 3. Never use bags or bottles of intravenous solution as a common source of supply for more than one patient.\n\np. Never use peripheral capillary blood monitoring devices packaged as single-patient use on more than one patient:\n a. Restrict use of peripheral capillary blood sampling devices to individual patients.\n b. Never reuse lancets. Consider selecting single-use lancets that permanently retract upon puncture.\n\n**STORAGE OF CLEAN MEDICAL SUPPLIES AND EQUIPMENT**\n\n**STORAGE OF MEDICAL EQUIPMENT**\n\nClean medical supplies must be stored in a manner which protects them from contamination. The following guidelines pertain to the storage of all clean medical supplies.\n\n1. Store clean medical supplies in clean utility rooms, supply rooms or other designated clean areas.\n2. No clean supplies or equipment are to be stored in the soiled utility room.\n3. Do not store clean supplies under sinks or in cabinets under sinks.\n4. Do not store clean supplies on any counter within 2 feet of a sink or other source of water.\n5. Do not store supplies under areas of leaking water or in areas with damaged or missing ceiling tiles.\n\nDo not store clean supplies in boxes on floors.\n\nDo not store excess quantities of clean supplies in the patient’s rooms. When the patient is discharged, all supplies remaining in the room must be removed and discarded.\n\nIf the outer packaging of clean supplies is damaged, torn, soiled or shows signs of water damage the product should be discarded.\n\nDo not store clean and soiled items together or in same room.\n\nAreas/rooms used to store clean medical supplies should be kept clean and free of clutter and debris.\n\nThe bottom wire shelves used to store supplies should be covered with plastic to protect supplies.\n\nNo storage of outer shipping boxes in clean storage areas. Contents must be removed from outer shipping boxes for storage.\n\n**CLEAN MEDICAL EQUIPMENT**\n\nClean medical equipment must be identified as clean by the presence of an outer covering or wrapping which protects the equipment from contamination.\n\nThe outer covering may consist of an overwrap, if the item comes from central processing, or the item may be covered with a clean clear plastic bag which identifies the product as cleaned/sanitized, and also prevents recontamination by soiling from the environment or by contact with hands or respiratory secretions in the course of casual contact with the item. Clear plastic bags are typically used to identify and protect cleaned commodes, IV poles, portable HEPA filters and other equipment cleaned and sanitized by building services.\n\nClean medical equipment must be stored in a manner which protects them from contamination. The following guidelines pertain to the storage of all clean medical equipment\n\n1. Store clean medical Equipment in clean utility rooms, supply rooms or other designated clean areas.\n2. No clean medical equipment is to be stored in the soiled utility room\n3. Do not store clean equipment under sinks or in cabinets under sinks\n4. Do not store clean equipment on any counter within 2 feet of a sink or other source of water.\n5. Do not store clean medical equipment under areas of leaking water or in areas with damaged or missing ceiling tiles\n6. If the outer covering of clean medical equipment is damaged, torn, or shows signs of water damage the product should be reprocessed\n7. Do not store clean medical equipment in a room used to store dirty equipment or supplies.\n8. Areas/rooms used to store clean medical Equipment should be kept clean and free of clutter and debris.\n\n**VISITORS INFECTION CONTROL POLICY**\n\n**Objective:** To reduce the risk of transmission of infections between patients/residents and visitors.\n\n**Note:** If the visitor is ill with a cough, fever, rash, sore throat, vomiting or diarrhea, visits should be postponed until the visitor is no longer ill.\n\nVisitors include family members, friends, volunteers and any other persons or groups who enter patient/resident care areas.\n\n(a) Visitors to the facility are required to conform to facility policies and procedures when visiting patients/residents. This includes visitors compliance with all indicated procedures when a patient/resident is under any type of infection precautions. The facility provides essential information and instruction as necessary.\n\n(b) Visitors should consult nurse before entering patient room where “STOP” sign is posted at the patient/resident door or over the bed. The nurse will guide the visitor as to what type of personal protective equipment is required and other instructions before interacting with patient/resident.\n\n(c) Hand hygiene should be performed before and after the visit.\n\n(e) If a family member desires to provide care for the patient/resident, such as bathing or feeding, the same infection control techniques are required, of the assisting family members, as is required of hospital care personnel.\n\n(f) The KJMC/RNH may restrict visitors to the facility as a whole or to specific patient/resident or group of patients/residents. Reasons may be epidemics in the community, increased susceptibility of the patients/residents to infectious diseases, or other conditions.\n\n(g) Visitors should not bring food to patients/residents unless specific permission has been given and arrangements have been made for safe storage, if necessary.\n\n(h) No live plant or flower’s are allowed for immuno-compromised patients.\n\n## KJMC Infection Control Department: Isolation/Precaution Guidelines Summary\n\n| Mode of Transmission | Standard Precaution | Airborne Precaution | Droplet Precaution | Contact Precaution |\n|----------------------|---------------------|---------------------|--------------------|--------------------|\n| **Disease Examples** | All patients at ALL time regardless of patient diagnosis | Herpes Zoster ((Disseminated or immunocompromised host) Chicken pox (Varicella) Tuberculosis Measles | H. Infuenzae-b Neisseria Meningitis MDR S. pneumoniae Mycoplasma Pneumonia Diphtheria Pertussis Strep. Pharyngitis (gp A) Viral infections MRSA and/or antibiotic resistant Acinetobacter in sputum of pts with active cough or those requiring suctioning | MRSA VRE C. difficile M.D.R gram negative rods Enteric pathogens Multi drug resistant infections of decubitus ulcers and wounds (uncovered only) Scabies Pediculosis Herpes Zoster (also see airborne precautions for special cases) |\n| **Private Room/MD Order** | No | Yes Mandatory Place in negative pressure room. If not available, provide private room with HEPA filter. Transfer to negative pressure room when available Keep door closed | Yes if available. If no private room available cohort with patient infected at same site with same organism if possible. If cohoiting is not possible place patient with roommate who has no tubes, indwelling catheters, or skin problems. Maintain at least 3 feet of separation between pts. Door may be kept open | Yes if available If no private room available, cohort with patient infected with same organism at same site If cohoiting not possible place patient with roommate who has no tubes, indwelling catheters, or skin problems. Maintain 3 feet separation between pts. Door may be kept open |\n| **Linen** | No special precaution | No special precaution | No special precaution | No special precaution |\n| **Dietary Service** | No special precaution | No special precaution | No special precaution | No special precaution |\n| **Special Air Flow** | No | Yes Negative pressure room with 8-12 air exchanges per hr. | No | No |\n| **Glove** | If handling body fluids, mucous membrane or non-intact skin | If handling body fluids mucous membrane or non-Intact skin | If handling body fluids, mucous membrane or non-intact skin | If handling body fluids, mucous membrane or non-intact skin |\n\n| | Standard Precaution | Airborne Precaution | Droplet Precaution | Contact Precaution |\n|--------------------------|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|\n| Mask | If splashing or aerosolization likely | Yes. Particulate Filter Respirator (N-95 Mask). Face fit testing required before use. Contact supervisor for fit testing. | Yes. For use within a 3 foot radius of patient | If splashing or aerosolization likely |\n| Goggles, Face Shields | If splashing likely | If splashing likely | If splashing likely | If splashing likely |\n| Gown | If clothing likely to be soiled | If clothing likely to be soiled | If clothing likely be soiled or if clothing will have substantial contact with the patient or environment | If clothing likely be soiled or if clothing will have substantial contact with the patient or environment |\n| Hand Washing | Before and after patient contact, after removing gloves and handling potentially contaminated articles, | Before and after patient contact, after removing gloves and handling potentially contaminated articles, | Before and after patient contact, after removing gloves and handling potentially contaminated articles, | Before and after patient contact, after removing gloves and handling potentially contaminated articles, |\n| Needles/Syringes and Other Sharps | Used needle should not be recapped or bent. Place in sharp disposal container at the point of use | Used needle should not be recapped or bent. Place in sharp disposal container at the point of use | Used needle should not be recapped or bent. Place in sharp disposal container at the point of use | Used needle should not be recapped or bent. Place in sharp disposal container at the point of use |\n| Transporting Patients | No special precaution | Clean gown and mask on patient during transport | Clean gown and mask patient during transport | No special precautions. |\n| Specimen Transport | Place specimen in biohazard bags at point of collection for lab transport | Place specimen in biohazard bags at point of collection for lab transport | Place specimen in biohazard bags at point of collection for lab transport | Place specimen in biohazard bags at point of collection for lab transport |\n| Housekeeping | Routine cleaning procedure | Routine cleaning procedure | Routine cleaning procedure | Routine cleaning procedure |\n| Sign at Door | No sign | Stop sign | Stop sign | Stop sign |\n\nDoor Stop Sign\n\n[Placed outside patient’s room. Used to instruct personnel and visitors regarding use of appropriate protective equipment.]\n\nHEPATITIS B IS A BLOODBORNE PATHOGEN.\n\nHepatitis is an inflammation of the liver. It can be caused by a wide variety of agents including medications, alcohol, toxic or poisonous substances and infectious agents such as viruses. Signs and symptoms are:\n\n- Fever: an increase in body temperature\n- Jaundice: yellowing of the skin and sclera (white part of the eye)\n- Hepatomegaly: an enlargement of the liver\n- Malaise: feeling tired and listless\n\n• Dark colored urine\n• Joint pain\n\n**Hepatitis Transmission**\n\nTransmission of Hepatitis B can occur after a needle stick or sharp injury; a splash or spray of blood or body fluids to the eyes, nose or mouth; unprotected sex with an infected partner; and from an infected mother to the baby. A patient may have Hepatitis B and not have signs or symptoms of the disease and/or not know that he or she is infected with the disease.\n\nIn the hospital, we break the chain of infection for Hepatitis B by following Standard/Universal Precautions, proper handling and disposal of sharps and the Hepatitis B Vaccination Program.\n\nThe Hepatitis B vaccine is a non-infectious, yeast-based vaccine. It is not made from blood or plasma. It is a series of three injections given in the deltoid muscle at three separate visits to EHS. The vaccine is available free of charge to employees of KJMC. More than 90% of those who are vaccinated will develop immunity to Hepatitis B. To ensure immunity, it is important for individuals to receive all three injections. At this point, it is unclear how long the immunity lasts, so booster shots may be required at some point in the future. It is recommended that an individual titer or presence of antibodies to Hepatitis B be checked approximately four to six weeks after the third injection. Any employee who wishes to receive the Hepatitis B vaccine should call EHS to set an appointment.\n\nOSHA’s blood borne pathogen regulations require that any employee who may have occupational exposure to blood or potentially infectious material must show proof of immunity, receive the Hepatitis B vaccine or sign a refusal form in EHS. If you refuse the vaccine and sign the declination form, you may elect to receive the vaccine at a later date should you change your mind.\n\n**Regulated Medical Waste**\n\nAccording the Centers for Disease Control (CDC) and OSHA, Universal/Standard Precautions refers to an infection control system that assumes that any direct contact with a patient, particularly their body fluids, has the potential for transmitting disease. This system resulted from the heightened awareness and concern over the potential risk of transmitting HIV and HBV to healthcare providers. Therefore, Universal/Standard Precautions is a system designed to ensure the safety of the individual healthcare provider.\n\nThe critical factor for determining if material used in patient care should be considered as regulated medical waste are: (1) direct contact with any of the fluids identified by OSHA as being possible sources of transmission of infectious agents, and (2) the quantities of these fluids. OSHA has described semen, vaginal secretions, pleural fluid, synovial fluid, pericardial fluid, amniotic fluid, saliva in dental procedures, and any other fluid visibly contaminated with blood. Conversely, feces, urine and vomitus are not included unless they contain visible blood.\n\n**Human Pathological Wastes**\n\nThis waste includes tissue, organs and body parts, body fluids that are removed during surgery, autopsy or other medical procedures or specimens of body fluids and their containers, and discarded materials saturated with such body fluids other than urine.\n\n**Tuberculosis**\n\nTuberculosis (TB) is responsible for over three million deaths per year worldwide. It is approximated that 1.75 billion people are infected with Mycobacterium Tuberculosis. In New York City, TB cases rose steadily from 1979 to 1992. Factors that contributed to the increase included the HIV epidemic, increased immigration from areas of the world where TB is common, a weakening of the public health structure in the 1970s and 1980s, and social conditions such as homelessness, crowding and incarceration. In 1993 there was a 15% decrease in the number of cases of TB in the United States, the first significant decline in fifteen years. In 1994 a decrease in the number of New York City cases\n\noccurred. One of the measures that contributed to the decrease was improved infection control practices limiting the spread of TB in hospitals.\n\n**What are we doing to deal with this organism? How can you protect yourself and effectively break the chain of infection? First we need to identify who may have TB.**\n\nThere are some patients who are at a higher risk than normal for developing TB. These include homeless persons, intravenous drug users, persons who are HIV positive, immigrants from endemic areas, persons from the prison system, immunosuppressed persons and anyone with a history of TB. All patients considered at high risk for TB must be evaluated by Infection Control.\n\n**Any person in a high risk group with pulmonary symptoms must be isolated.**\n\nThe pulmonary symptoms that should be observed for are:\n\n1. Cough\n2. Pleuritic chest pain – typically sharp pain upon inspiration\n3. Blood in sputum – any blood in sputum should be evaluated\n4. Weight loss\n5. Night sweats\n6. Fever\n\nAll patients admitted must be evaluated by the nursing staff regarding any past history of TB or a positive PPD (intradermal skin test for TB), any exposure to TB in their home or workplace, or membership in any of the high-risk groups.\n\n**TB is transmitted when someone with active Pulmonary or Laryngeal TB sneezes or coughs. That is why it is important that Airborne Precautions are followed when someone is a suspected or confirmed TB case. (See attachment for information on proper placement of the PFN 95 mask.)**\n\nAssuming the potential or actual person with TB has been identified and kept on Airborne Precautions, what else can we do to break the chain of infection? First, you must be aware of your own risk of exposure. Staff is tested at least yearly with PPD skin testing. After exposure to TB has been identified, all staff are evaluated, except for those who are already tested every six months. EHS must evaluate your PPD. You cannot self-report nor can you have a nurse who is not in EHS, the Emergency Department or Urgent Care must evaluate your PPD. PPDs may also be read by accredited MDs or RNs on a limited basis as defined by EHS. It is the “induration” or swelling and hardness of the site that is evaluated and measured, not the redness. Always follow up with EHS. PPD placement, when done annually, corresponds to the annual health survey. Check with you Head Nurse, Nurse Manager, AND or EHS for the dates and times. If you have received the BCG vaccine in the past, you must still be tested for exposure to TB with a PPD. Prior BCG vaccination is not a contraindication for PPD testing. Some staff members do, with exposure to TB, convert to having a positive PPD. This does not mean that the converter has active TB. However, the converter will need a chest X-ray for further evaluation. Also, the medication INH (Isoniazid) may be prescribed to decrease the chance that TB will develop. It is recommended that this medication be taken for a period of six months to one year. Once someone has converted, PPD testing is no longer done.\n\nIt is important to remember the signs and symptoms of TB. If you are experiencing a cough, night sweats, bloody sputum or any of the symptoms mentioned above, please see EHS to be evaluated. It is much safer for you, your fellow workers, your family and your patients to be cautious.\n\nFacepiece Respirators\n\nFitting Instructions for 3M Filtering Facepiece Respirators\n\n1. Place the respirator over your nose and mouth. Be sure the metal nose clip is on top. With models 8210 or 07048, prestretch the straps before wearing.\n\n2. Pull the top strap over your head until it rests on the crown of your head above your ears.\n\n3. Pull the bottom strap over your head until it rests just below your ears.\n\n4. Using both hands, starting at the top, mold the metal nose clip around your nose to achieve a secure seal.\n\n**Check the Seal**\n\nCheck the seal of your filtering facepiece respirator each time you don the respirator.\n\n**Positive Pressure User Seal Check**\n\nFor non-valved respirators, place both hands completely over the respirator and *exhale*. The respirator should bulge slightly. If air leaks between the face and faceseal of the respirator, reposition it and readjust the nose clip for a more secure seal. If you cannot achieve a proper seal, *do not* enter the contaminated area. See your supervisor.\n\n**Negative Pressure User Seal Check**\n\nFor valved respirators, place both hands over the respirator and *inhale* sharply. The respirator should collapse slightly. If air leaks between the face and faceseal of the respirator, reposition it and readjust the nose clip for a more secure seal. If you cannot achieve a proper seal, *do not* enter the contaminated area. See your supervisor.\n\nFitting Instructions for 3M Adjustable Strap Valved Filtering Facepiece Respirators\n\n1. Place the respirator over your nose and mouth. Be sure the metal nose clip is on top.\n\n2. Pull the bottom strap over your head until it rests below the ears at the back of your neck.\n\n3. Pull the top strap over your head until it rests on the crown of your head above your ears.\n\n4. Without removing the respirator, adjust the straps until the respirator is secure. To tighten the respirator, gently pull the ends of both straps. To loosen the respirator, press on the back side of the buckle.\n\n5. Using both hands starting at the top, mold the metal nose clip around your nose to achieve a secure seal.\n\n**Check the Seal**\n\nCheck the seal of your adjustable strap valved filtering facepiece respirator each time you don the respirator.\n\nPlace both hands over the respirator and *inhale* sharply. The respirator should collapse slightly. If air leaks between the face and faceseal of the respirator, reposition it and adjust the nose clip for a more secure seal. If you cannot achieve a proper seal, *do not* enter the contaminated area. See your supervisor.\n\n## KJMC Infection Control Department Infectious Waste Disposal Guidelines\n\n| Item | Place in Sharp Container | Place in Red Bag | Place in Clear Bag |\n|-------------------------------------------|--------------------------|------------------|--------------------|\n| Needles | X | | |\n| Lancets | X | | |\n| Sutures | X | | |\n| Scalps | X | | |\n| Scissors | X | | |\n| Specimen tube used/unused | X | | |\n| Broken glass | X | | |\n| IV catheters | X | | |\n| Drainage receptacle | | X | |\n| Dressings/bandage saturated with blood | | X | |\n| Foley catheter/bags with blood | | X | |\n| Blood bags | | X | |\n| Hemodialysis tubing | | X | |\n| IV lines & bags with visible blood | | X | |\n| Ventilator tubing saturated with secretions | | X | |\n| Diapers saturated with body fluids or blood | | X | |\n| PPE used for respiratory isolation | | | X |\n| PPE | | | X |\n| Packaging and boxes | | | X |\n| Plates, cups, utensils | | | X |\n| Tissues and paper towels | | | X |\n| Disposable food trays | | | X |\n\nSharps\n\nThis waste includes but is not limited to discarded unused sharps and sharps used in animal or human patient care, medical research or clinical or pharmaceutical laboratories, hypodermic, intravenous or other medical needles, hypodermic or intravenous syringes to which a needle or other sharp is still attached, Pasteur pipettes, scalpel blades or blood vials. This category also includes any other type of broken or unbroken glass in contact with infectious agents.\n\nThe single most important aspect to sharps which gives rise to fear and apprehension is their inherent ability to cause puncture wounds and/or lacerations which may create a portal of entry for infectious agents. Although syringes with attached needles are the classic example of sharps, other items used in the delivery of healthcare or in research and which have come in contact with infectious agents, e.g., glass or rigid plastic culture tubes, flasks, beakers, etc., must also be considered as sharps and be disposed of accordingly.\n\nOne point needs to be clarified. No attempt should ever be made to remove the needle from the barrel of the syringe. To do so would only increase the opportunity for needle stick injury. The total unit should be placed in a sharps container and disposed of as regulated medical waste. In those instances, however, where only the barrel of the unit is utilized, the barrel can be disposed of as solid waste, provided it did not come into contact with infectious agents.\n\nRecognition and Management of Terrorism\n\nTen Critical Steps for Handling Possible Bioterrorist Events\n\n1. **Maintain an index of suspicion.**\n In an otherwise healthy population, some associations are very suggestive, especially when seen in clusters, high numbers, or unusual presentations.\n\n | Hemorrhage | Plague |\n |------------|--------|\n | Flaccid Paralysis | Botulism |\n | Purpura | Viral Hemorrhagic Fevers (VHF) |\n | Wide mediastinum | Anthrax |\n | Centripetal* rash | Smallpox |\n | *Rash more abundant on face and extremities |\n\n2. **Protect yourself and your patients.**\n Use appropriate personal protection equipment (PPE). For smallpox, triage and evaluate patient in an isolation room; wear an appropriate respirator (N-95 or higher).\n\n3. **Adequately assess the patient.**\n Review and assess the patient’s history. Also, ask:\n - Are others ill?\n - Were there any unusual events?\n - Was there a possible contaminated food item?\n - Was there vector exposure?\n\n Perform a physical examination with special attention to the respiratory system, nervous system, skin condition, and hematologic and vascular status.\n\n4. **Decontaminate as appropriate.**\n Do not use bleach on exposed people. Soap, water and shampoo are perfectly adequate for all biological and most chemical agents. Chemically contaminated clothes should be removed and discarded safely. Biologically contaminated clothes can be laundered with soap, water and, perhaps, bleach.\n\n5. **Establish a diagnosis.**\n Think clinically and epidemiologically: always send specimens for culture.\n\n | Symptoms (individuals) | Possible Diagnosis |\n |-------------------------|--------------------|\n | Pulmonary | Anthrax, tularemia, plague, staph enterotoxin B (SEB) |\n | Neurovascular | Botulism, Venezuelan equine encephalitis (VEE) |\n | Bleeding/purpura | VHF, ricin, plague (late) |\n | Rash (various types) | VHF, T2 mycotoxin, smallpox, plague |\n | Flu-like symptoms | Varies |\n\n | Symptoms (symptoms (large numbers)) | Possible Diagnosis |\n |-------------------------------------|--------------------|\n | Pulmonary | SEB, mustard, Lewisite, phosgene, cyanide |\n | Neurologic | Nerve gases, cyanide |\n\n | Delayed Symptoms (large numbers) | Possible Diagnosis |\n |----------------------------------|--------------------|\n | Pulmonary | Biological agents, mustard, phosgene |\n | Neurologic | Botulism, VEE, other encephalitis |\n\n6. **Render prompt treatment.**\n Doxycycline can be used to treat virtually everything (except virals or toxins) while awaiting lab results. Inhalational anthrax should be treated with two or more antibiotics, including doxycycline or ciprofloxacin plus one or more other antibiotics. Observe pediatric precautions as appropriate. Prophylaxis (antibiotics and/or vaccines) should be administered according to public health recommendations.\n\n7. **Provide good infection control.**\n Recommended isolation precautions (in addition to standard precautions) for biologic agents include:\n\n | Anthrax: | Contact precautions for cutaneous anthrax |\n | Pneumatic Plague: | Droplet precautions and contact precautions if draining buboes present |\n | Smallpox: | Airborne and contact precautions |\n | Tularemia: | Contact precautions if lesions present |\n | Viral Hemorrhagic Fevers: | Contact precautions; airborne precautions especially in late stages |\n\n8. **Alert the proper authorities.**\n\n | Agency | Telephone Number |\n |--------|------------------|\n | FBI | 518-665-7551 (Albany) |\n | | 212-384-1000 (New York City) |\n | | 716-856-7800 (Buffalo) |\n | Municipal Police/County Sheriff | ____________________________ |\n | New York State Police | ____________________________ |\n | County Health Department | ____________________________ |\n | New York State Health Department | 518-473-4436 (days) 518-465-9720 (after hours) |\n | Local Emergency Medical Services Unit | ____________________________ |\n | Local Hospitals | ____________________________ |\n | Centers for Disease Control and Prevention Wadsworth Laboratory | 770-488-7100 |\n | | 518-474-2821 (days) 518-465-9720 (after hours) |\n\n9. **Assist in the epidemiologic investigations so as to determine who may be at risk.**\n\n10. **Know and spread this information.**\n\n---\n\nSteps in an epidemiologic investigation:\n- Count cases;\n- Relate to the at-risk population;\n- Make comparisons;\n- Develop hypotheses;\n- Test hypotheses;\n- Make inferences;\n- Conduct studies;\n- Interpret and evaluate.\n\nAdapted with kind permission from a lecture by Dr. Ned Gieslak, Colonel, US Army\n\nNew York State Department of Health\nBureau of Communicable Disease Control\n\nMore information on how to recognize and manage a patient exposed to terrorism can be obtained from a Self-Learning Package distributed by the Nursing Education Department, Leviton 201 or from a video that can be borrowed from the KJMC Medical Library.\n\nThe Self-Learning Package is recommended for all department heads, managers, supervisors and coordinators as well as all nurses.\n\n## KJMC Infection Control Department: Isolation/Precaution Guidelines for Bioterrorism Agents\n\n| Mode of Transmission | Standard Precaution | Airborne Precaution | Droplet Precaution | Contact Precaution |\n|----------------------|---------------------|---------------------|--------------------|--------------------|\n| Anthrax (pulmonary) | Contact with patient blood/body fluids | Airborne | Droplet | Direct patient contact/contact with patient environment |\n| Botulism | | | | |\n| Tularemia | | | | |\n| Viral Encephalitis | | | | |\n\n| Bioterrorism Agent | Anthrax (Cutaneous) | Smallpox (Also see Airborne) | Cholera | Ebola (VHF) (Also see Airborne) |\n|----------------------|---------------------|-------------------------------|---------|---------------------------------|\n| | | | | |\n\n| Private Room/MD Order | No | Yes Mandatory | Yes if available. If no private room available cohort with patient infected with same organism. Door may be kept open | Yes if available If not, cohort with patient infected with same organism. |\n|-----------------------|----|---------------|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|\n\n| Linen | No special precaution | Place linen in red bag and decontaminate by autoclaving | Place linen in red bag and decontaminate by autoclaving | Decontaminate for Smallpox and Ebola. No special precautions needed for Anthrax and Cholera |\n|-------|-----------------------|----------------------------------------------------------|----------------------------------------------------------|------------------------------------------------------------------------------------------|\n\n| Dietary Service | No special precaution | Disposable dishes and utensils | No special precaution | No special precaution except for Smallpox and Ebola. For Smallpox and Ebola (VHF) see Airborne requirements. |\n|-----------------|-----------------------|---------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------|\n\n| Special Air Flow | No | Yes Negative pressure room with 8-12 air exchanges per hr. | No | No |\n|------------------|----|-----------------------------------------------------------|----|----|\n\n| Glove | If handling body fluids, mucous membrane or non-intact skin | If handling body fluids mucous membrane or non-intact skin | If handling body fluids, mucous membrane or non-intact skin | If handling body fluids, mucous membrane or non-intact skin |\n|-------|-------------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------|\n\n| Mask | If splashing or aerosolization likely | Yes. Particulate Filter Respirator (N-100 Mask). Face fit testing is required before use. Contact supervisor for fit testing. | Yes. Mask for use within a 3 foot radius of patient | If splashing or aerosolization likely |\n|------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|--------------------------------------|\n\n| Goggles, Face Shields | If splashing likely | If splashing likely | If splashing likely | If splashing likely |\n|-----------------------|---------------------|---------------------|---------------------|---------------------|\n\n| Gown | If clothing likely to be soiled | Protective gown | If clothing likely be soiled or if clothing will have substantial contact with the patient or the environment | If clothing likely be soiled or if clothing will have substantial contact with the patient or the environment |\n|------|---------------------------------|-----------------|-------------------------------------------------------------|-------------------------------------------------------------|\n\n| Procedure | Standard Precaution | Airborne Precaution | Droplet Precaution | Contact Precaution |\n|----------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|\n| Hand Washing | Before and after patient contact, after removing gloves and handling potentially | Before and after patient contact, after removing gloves and handling potentially | Before and after patient contact, after removing gloves and after handling | Before and after patient contact, after removing gloves and after handling |\n| | contaminated articles. | contaminated articles | contaminated articles | potentially contaminated articles, |\n| Needles/Syringes and Other | Used needle should not be recapped or bent. Place in sharp disposal container at | Used needle should not be recapped or bent. Place in sharp disposal container at | Used needle should not be recapped or bent. Place in sharp disposal container at | Used needle should not be recapped or bent. Place in sharp disposal container at |\n| Sharps | the point of use. | the point of use | the point of use | the point of use |\n| Transporting Patients | No special precaution | LIMIT TRANSPORT UNLESS ABSOLUTELY NECESSARY. Clean gown and mask on patient during | Clean gown and mask patient during transport | No special precautions EXCEPT FOR SMALLPOX AND EBOLA (See Airborne) |\n| | | transport | | |\n| Specimen Transport | Specimen to be placed in clear plastic biohazard labeled bags at the point of | Specimen to be placed in clear plastic biohazard labeled bags at the point of | Specimen to be placed in clear plastic biohazard labeled bags at the point of | Specimen to be placed in clear plastic biohazard labeled bags at the point of |\n| | collection for transport to lab. | collection for transport to lab. | collection for transport to lab. | collection for transport to lab. |\n| Housekeeping | Routine cleaning procedure | Routine cleaning procedure | Routine cleaning procedure | Routine cleaning procedure |\n| Sign at Door | No sign | Stop sign | Stop sign | Stop sign |\n\n© Steven Brooks, Ph.D. 1/2002\n\n## Competency Exam: Chapter 3\n\n### Infection Control/Terrorism Management\n\n| Questions | Select the correct response: |\n|---------------------------------------------------------------------------|------------------------------------------------------------------|\n| 1. The single most important way to prevent the spread of infection is to:| Wash your hands \nWear gloves \nWear a mask \nAll of the above |\n| 2. For how long is it recommended that you wash your hands? | a. 10–15 seconds (the time it takes to say a children's nursery rhyme) \nb. 3 minutes \nc. 5 minutes \nd. None of the above |\n| 3. Which of the following must you do if you are injured by a contaminated needle? | a. Wash the area with soap and water \nb. Report the incident to your supervisor \nc. Seek an evaluation as soon as possible at Employee Health Services (EHS) \nd. All of the above |\n| 4. Standard/Universal Precautions must be used when caring for: | a. A patient with cancer \nb. A patient with TB \nc. All patients \nd. Patients that are HIV positive |\n| 5. When a patient is on Contact Precaution: | a. Gloves should be worn if handling body fluids \nb. Upon entering the room, a gown should be worn if you anticipate that clothing will have substantial contact with the patient or patient environment \nc. The N-95 Mask should be worn before entering the room \nd. A and B |\n| 6. When a patient is on Airborne Precautions: | a. Patients must be private rooms with the door closed \nb. You must wear the hospital-mandated mask N95 \nc. Special dietary tray precautions \nd. A and B |\n| 7. When a patient is on Droplet Precautions you should do all except: | a. Wear a surgical mask when working within eight feet of the patient \nb. Use a surgical mask on the patient during transport \nc. Patient may be in a private room \nd. Patients may be cohorted with another patient with the same organism at the same site. |\n| 8. Hepatitis B can be transmitted through a blood splash to the eye. | a. True \nb. False |\n| 9. More information regarding how to recognize and handle patients exposed to terrorism can be obtained from a Self Learning Nursing Package distributed by the Nursing Education Department L201. | a. True \nb. False |\n| 10. When transferring a patient on precautions off your unit, it is your responsibility to notify the receiving unit. | a. True \nb. False |\n| 11. Which of the following items belong in the red bag garbage: | a. IV tubing with IV bag that has no blood \nb. IV tubing from a blood transfusion \nc. Needle and syringe \nd. Dry used dressings |\n| 12. Scalpels, pipettes and blood vials are disposed of in red bag waste. | a. True \nb. False |\n\nChapter 4:\nPatient/Resident Rights\n\nPurpose\n\nThis module was designed to review KJMC’s policies as they relate to patient and resident rights.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. Define Patient/Resident Rights\n2. Relate KJMC’s Mission Statement\n3. Identify and understand the three types of advance directives\n4. Complete the competency exam\n\nKJMC/RNH Mission Statement\n\nHistory\nKingsbrook Jewish Medical Center, founded in 1925 on Judaic tradition and rooted in the ethics of healing and devoted service, is dedicated to caring for all people regardless of religion, race, national origin or the ability to pay. A not-for-profit multi-specialty teaching hospital, it provides the most advanced medical treatment and excellence in both acute and long-term patient care.\n\nVision\nTo be distinguished as a premier hospital and trusted partner that advances the well-being of the individuals, families and communities we serve.\n\nMission\nTo partner with our culturally diverse communities to provide a continuum of outstanding health care services to individuals and families through a caring and trustworthy staff.\n\nValues\nCompassion\nRespect\nEthics\nExcellence\nDedication\n\nPatients’ Bill of Rights¹\n\nAs a patient in a hospital in New York State, you have the right, consistent with law, to:\n\n1. Understand and use these rights. If for any reason you do not understand or you need help, the hospital MUST provide assistance, including an interpreter.\n\n2. Receive treatment without discrimination as to race, color, religion, sex, national origin, disability, sexual orientation or source of payment.\n\n3. Receive considerate and respectful care in a clean and safe environment free of unnecessary restraints.\n\n4. Receive emergency care if you need it.\n\n5. Be informed of the name and position of the doctor who will be in charge of your care in the hospital.\n\n6. Know the names, positions and functions of any hospital staff involved in your care and refuse their treatment, examination or observation.\n\n7. A no smoking room.\n\n8. Receive complete information about your diagnosis, treatment and prognosis.\n\n9. Receive all the information that you need to give informed consent for any proposed procedure or treatment. This information shall include the possible risks and benefits of the procedure or treatment.\n\n¹ Public Health Law (PHL) 2803(1)(g) Patients’ Rights, 10NYCRR, 405.7, 405.7(a)(1), 405.7(a)(2)\n\n10. Receive all the information you need to give informed consent for an order not to resuscitate. You also have the right to designate an individual to give this consent for you if you are too ill to do so. If you would like additional information, please ask for a copy of the pamphlet \"Do Not Resuscitate Orders -- A Guide for Patients and Families.\"\n\n11. Refuse treatment and be told what effect this may have on your health.\n\n12. Refuse to take part in research. In deciding whether or not to participate, you have the right to a full explanation.\n\n13. Privacy while in the hospital and confidentiality of all information and records regarding your care.\n\n14. Participate in all decisions about your treatment and discharge from the hospital. The hospital must provide you with a written discharge plan and written description of how you can appeal your discharge.\n\n15. Review your medical record without charge. Obtain a copy of your medical record for which the hospital can charge a reasonable fee. You cannot be denied a copy solely because you cannot afford to pay.\n\n16. Receive an itemized bill and explanation of all charges.\n\n17. Complain without fear of reprisals about the care and services you are receiving and to have the hospital respond to you and if you request it, a written response. If you are not satisfied with the hospital's response, you can complain to the New York State Health Department. The hospital must provide you with the Health Department telephone number.\n\n18. Authorize those family members and other adults who will be given priority to visit consistent with your ability to receive visitors.\n\n19. Make known your wishes in regard to anatomical gifts. You may document your wishes in your health care proxy or on a donor card, available from the hospital.\n\n---\n\n**Your Rights as a Nursing Facility Resident**\n\n*These Rights are Required by State and Federal Law*\n\n**Privacy and Respect**\n\nIt is your right to:\n\n- Receive a copy of your rights and facility regulations prior to or at the time of admission to the facility;\n- Be informed of your rights, and the rules and regulations of the facility;\n- Be informed both orally and in writing of your rights in a language that you can understand;\n- Exercise your rights as a citizen of your state and the United States;\n- Exercise civil and religious liberties;\n- Talk to or write to anyone in or outside of the facility;\n- Be treated as a person with respect, dignity and consideration;\n- Receive services considering your special needs;\n- Receive prompt response to all reasonable requests;\n- Keep your personal and medical records private, and refuse to allow anyone to see these records without your written permission;\n- Get an advance notice about a change in room or roommate and to be told why such a change is needed.\n\nActivities\n\nIt is your right to:\n\n- Plan your daily activities;\n- Take part in various activities at the facility.\n\nMedical Care and Treatment\n\nIt is your right to:\n\n- Receive adequate, appropriate health care and appropriate protective and supportive services;\n- Be present and participate in your care plan;\n- Formulate an advance directive which must be compiled with by the facility;\n- Be told in a language you understand about your medical problems and total health condition;\n- Choose your own physician;\n- Give yourself certain medications under certain conditions;\n- Be told in advance about any change in treatment or care;\n- Refuse treatment offered to you by your physician;\n- Refuse to participate in experimental research.\n\nWork\n\nIt is your right to:\n\n- Not perform work;\n- Receive a wage if you desire for any work you do.\n\nPersonal Possessions\n\nIt is your right to:\n\n- Have your own clothing and possessions.\n\nFreedom from Abuse and Restraints\n\nIt is your right to:\n\n- Be free from discrimination, punishment or denial of privileges and any physical, mental or sexual abuse;\n- Be free from abuse, scolding or punishment within the facility;\n- Not to be tied in any chair or bed, or held by a tray unless a physician states in writing that you need to be for your own safety or in an emergency;\n- Be free of mental, physical or psychosocial abuse, and of restraints not ordered by your physician and not documented as medically necessary;\n- Be free of drugs and physical restraints for the purpose of discipline or convenience of the facility.\n\nFreedom of Association and Communication in Privacy\n\nIt is your right to:\n\n- If married, share the room with your spouse if both of you agree to it, and to visit privately with your spouse;\n\n• Visit privately outside the facility with anyone of your choice;\n• Have visitors at the facility in a timely manner at reasonable hours;\n• Make phone calls to anybody as long as you pay for them;\n• Send and receive mail unopened;\n• Meet with and belong to any church or social group;\n• Meet with other residents and resident groups within the facility;\n• See the findings of State and Federal inspections;\n• Talk to State inspectors and Ombudsmen in private.\n\n**Financial Affairs**\n\nIt is your right to:\n\n• Be told of all services available and all costs, including those charges covered or not covered under Medicare or Medicaid, the basic per diem rate, and items or services you request, which are not covered by Medicare or Medicaid;\n• Manage your personal affairs, or of this is delegated in writing, to receive a written quarterly statement upon request;\n• Be told if you are entitled to Medicare or Medicaid;\n• Not charge your personal funds for any item or service paid by Medicare or Medicaid or not requested by you;\n\n**Admission, Transfer and Discharge**\n\nIt is your right to:\n\n• Be treated without discrimination regardless of source of payment to the facility;\n• Not be required to give up your rights to Medicare or Medicaid;\n• Be informed of the bed hold policy for temporary absences from the facility;\n• Be transferred or discharged only after reasonable notice is given and only for medical reasons, the welfare of other residents, or for nonpayment. You may not be transferred or discharged from a Title XIX (Medicaid) certified facility because the source of payment for care is changed;\n• Refuse to transfer to another room under certain conditions.\n\n**Grievances and Complaints**\n\nIt is your right to:\n\n• Make complaints or suggestions without fear of punishment or coercion of any sort;\n• Appeal to the State or Federal survey agency if your problems or complaints are not solved to your satisfaction.\n\n| Resident’s Name | Date |\n|-----------------|------|\n| Resident’s Signature | Date |\n| Legal Rep’s Name | Date |\n| Legal Rep’s Signature | Date |\n\nKJMC/RNH Advance Directive Policy\n\nKingsbrook Jewish Medical Center (KJMC) and Rutland Nursing Home (RNH) remain committed to the service of patients and residents and their health care needs and wishes. The institution’s policy respects the right of each patient and resident to make voluntary and informed decisions to accept, reject or choose alternative courses of medical and/or surgical treatment, including decisions regarding life sustaining treatment.\n\nIn recognition of the right to make healthcare decisions, KJMC and RNH provide information and literature about Advance Directives to permit patients and residents to understand their rights to formulate and the methods for creating an Advance Directive.\n\nBe assured, as caregivers, your comfort and well-being will remain your concern.\n\nShould you choose not to receive life-sustaining treatments, we will comply with your wishes in accordance with the prevailing law and the policy of the institution.\n\nReissued: 2/24/93\nRevised: 5/12/00\n\nPlanning in Advance for Your Medical Treatment\n\nYour Right to Decide About Treatment\n\nAdults in New York State have the right to accept or refuse medical treatment, including life-sustaining treatment. Our Constitution and state laws protect this right. This means that you have the right to request or consent to treatment, to refuse treatment before it has started and to have treatment stopped once it has begun.\n\nPlanning In Advance\n\nSometimes because of illness or injury people are unable to talk to a doctor and decide about treatment for themselves. You may wish to plan in advance to make sure that your wishes about treatment will be followed if you become unable to decide for yourself for a short or long time period. If you don’t plan ahead, family members or other people close to you may not be allowed to make decisions for you and follow your wishes.\n\nIn New York State, appointing someone you can trust to decide about treatment if you become unable to decide for yourself is the best way to protect your treatment wishes and concerns. You have the right to appoint someone by filling out a form called a Health Care Proxy. A copy of the form and information about the Health Care Proxy are available from your health care provider.\n\nIf you have no one you can appoint to decide for you, or do not want to appoint someone, you can also give specific instructions about treatment in advance. Those instructions can be written, and are often referred to as a Living Will.\n\nYou should understand that general instructions about refusing treatment, even if written down, may not be effective. Your instructions must clearly cover the treatment decisions that must be made. For example, if you just write down that you do not want “heroic measures,” the instructions may not be specific enough. You should say the kind of treatment that you do not want, such as a respirator or chemotherapy, and describe the medical condition when you would refuse the treatment, such as when you are terminally ill or permanently unconscious.\n\nwith no hope of recovering. You can also give instructions orally by discussing your treatment wishes with your doctor, family members or others close to you.\n\nPutting things in writing is safer than simply speaking to people, but neither method is as effective as appointing someone to decide for you. It is often hard for people to know in advance what will happen to them or what their medical needs will be in the future. If you choose someone to make decisions for you, that person can talk to your doctor and make decisions that they believe you would have wanted or that are best for you, when needed.\n\nIf you appoint someone and also leave instructions about treatment in a Living Will, in the space provided on the Health Care Proxy form itself, or in some other manner, the person you select could use these instructions as guidance to make the right decision for you.\n\n**Deciding About Cardiopulmonary Resuscitation**\n\nYour right to decide about treatment also includes the right to decide about cardiopulmonary resuscitation (CPR). CPR is emergency treatment to restart the heart and lungs when your breathing or circulation stops.\n\nSometimes doctors and patients decide in advance that CPR should not be provided, and the doctor gives the medical staff an order not to resuscitate (DNR) order. If your physical or mental condition prevents you from deciding about CPR, someone you appoint, your family members or surrogate can decide for you.\n\nPatients are provided with the description of state law prepared by the State Health Department entitled \"Planning in Advance For Your Medical Treatment\"; the publication, \"Appointing Your Health Care Agent New York State's Proxy Law,\" which contains a sample (usable) health care proxy form; and a summary of the hospital's policy regarding the implementation of these rights. 10NYCRR, 400.21 (d) (1) (i, ii, iii)\n\n**Deciding about CPR: Do-Not-Resuscitate (DNR) Orders: A Guide for Patients and Families**\n\n*What do CPR and DNR orders mean?*\n\nCPR cardiopulmonary resuscitation refers to the medical procedures used to restart a patient's heart and breathing when the patient suffers heart failure. CPR may involve simple efforts such as mouth-to-mouth resuscitation and external chest compression. Advanced CPR may involve electric shock, insertion of a tube to open the patient's airway, injection of medication into the heart and in extreme cases, open chest heart massage.\n\nA do-not-resuscitate (DNR) order tells medical professionals not to perform CPR. This means that doctors, nurses and emergency medical personnel will not attempt emergency CPR if the patient's breathing or heartbeat stops.\n\nDNR orders may be written for patients in a hospital or nursing home, or for patients at home. Hospital DNR orders tell the medical staff not to resuscitate the patient if cardiac arrest occurs. If the patient is in a nursing home or at home, a DNR order tells the staff and emergency medical personnel not to perform emergency resuscitation and not to transfer the patient to a hospital for CPR.\n\n*Why are DNR orders issued?*\n\nCPR, when successful, restores heartbeat and breathing and allows a patient to resume his/her previous lifestyle. The success of CPR depends on the patient's overall medical condition. Age alone does not determine whether CPR will be successful, although illnesses and frailties that go along with age often make CPR less successful.\n\nWhen patients are seriously ill or terminally ill, CPR may not work or may only partially work, leaving the patient brain-damaged or in a worse medical state than before the heart stopped. In these cases, some patients prefer to be cared for without aggressive efforts at resuscitation.\n\nCan I request a DNR order?\n\nYes. All adult patients can request a DNR order. If you are sick and unable to tell your doctor that you want a DNR order written, a family member or surrogate can decide for you.\n\nIs my right to request or receive other treatment affected by a DNR order?\n\nNo. A DNR order is only a decision about CPR and does not relate to any other treatment.\n\nAre DNR orders ethically acceptable?\n\nIt is widely recognized by health care professionals, clergy, lawyers and others that DNR orders are medically and ethically appropriate under certain circumstances. For some patients, CPR offers more burdens than benefits, and may be against the patient's wishes.\n\nIs my consent required for a DNR order?\n\nYour doctor must speak to you before entering a DNR order if you are able to decide, unless your doctor believes that discussing CPR with you would cause you severe harm. In an emergency, it is assumed that all patients would consent to CPR. However, if a doctor decides that CPR will not work, it is not provided.\n\nHow can I make my wishes about DNR known?\n\nDuring hospitalization, an adult patient may consent to a DNR order orally or in writing, if two adult witnesses are present. When consent is given orally, one of the witnesses must be a physician affiliated with the hospital. Prior to hospitalization, consent must be in writing in the presence of two adult witnesses. In addition, the Health Care Proxy Law allows you to appoint someone you trust to make decisions about CPR and other treatments if you become unable to decide for yourself.\n\nBefore deciding about CPR, you should speak with your doctor about your overall health and the benefits and burdens CPR would provide for you. A full and early discussion between you and your doctor will assure that your wishes will be known.\n\nIf I request a DNR order, must my doctor honor my wishes?\n\nIf you don't want CPR and you request a DNR order, your doctor must follow your wishes or:\n\n- transfer your care to another doctor who will follow your wishes; or\n- begin a process to settle the dispute if you are in a hospital or nursing home.\n\nIf the dispute is not resolved within 72 hours, your doctor must enter the order or transfer you to the care of another doctor.\n\nIf I am not able to decide about CPR for myself, who will decide?\n\nFirst, two doctors must determine that you are unable to decide about CPR. You will be told of this determination and have the right to object.\n\nIf you become unable to decide about CPR, and you did not tell your doctor or others about your wishes in advance, a DNR order can be written with the consent of the person highest on the following list:\n\n- your health care agent the person chosen by you to make health care decisions under New York's Health Care Proxy Law (if you have appointed one);\n- a court appointed guardian (if there is one);\n- your closest relative (spouse, child, parent, sibling);\n- a close friend.\n\nHow can I select someone to decide for me?\n\nThe Health Care Proxy Law allows adults to select someone they trust to make health care decisions for them when they are no longer able to do so themselves, including decisions about CPR. You can name someone by filling out a health care proxy form.\n\nUnder what circumstances can a family member or close friend decide that a DNR order should be written?\n\nA family member or close friend can consent to a DNR order only when you are unable to decide for yourself and you have not appointed a health care agent to decide for you. Your family member or friend/surrogate can consent to a DNR order when:\n\n- you are terminally ill; or\n- you are permanently unconscious; or\n- CPR will not work (would be medically futile); or\n- CPR would impose an extraordinary burden on you given your medical condition and the expected outcome of CPR.\n\nAnyone deciding for you must base the decision on your wishes, including your religious and moral beliefs, or if your wishes are not known, on your best interests.\n\nWhat if members of my family disagree?\n\nIn a hospital or nursing home, your family can ask that the disagreement be mediated. Your doctor can request mediation if he or she is aware of any disagreement among your family members.\n\nWhat if I lose the ability to make decisions about CPR and do not have anyone who can decide for me?\n\nA DNR order can be written if two doctors decide that CPR would not work or if a court approves of the DNR order. It would be best if you discussed your wishes about CPR with your doctor in advance.\n\nWho can consent to a DNR order for children?\n\nA DNR order can be entered for a child with the consent of the child’s parent or guardian. If the child is old enough to understand and decide about CPR, the child’s consent is also required for a DNR order.\n\nWhat happens if I change my mind after a DNR order has been written?\n\nYou or anyone who consents to a DNR order for you can revoke consent for the order by telling your doctor, nurses or others of the decision.\n\nWhat happens to a DNR order if I am transferred from a nursing home to a hospital or vice versa?\n\nThe DNR order will continue until a doctor examines you and decides whether the order should remain or be canceled. If the doctor decides to cancel the DNR order, you or anyone who decided for you will be told and can ask that the DNR order be entered again.\n\nIf I am at home with a nonhospital DNR order, what happens if a family member or friend panics and calls an ambulance to resuscitate me?\n\nIf you have a nonhospital DNR order and family members show it to emergency personnel, they will not try to resuscitate you or take you to a hospital emergency room for CPR.\n\nWhat happens to my DNR order if I am transferred from a hospital or nursing home to home care?\n\nThe order issued for you in a hospital or nursing home will not apply at home. You, your health care agent or family member must specifically consent to a nonhospital DNR order. If you leave a hospital or nursing home without a nonhospital DNR order, a DNR order can be issued by a doctor for you at home.\n\nPatients are provided with information developed by the State Health Department that describes the Do-Not-Resuscitate law. It must also be furnished to each member of the hospital’s staff involved in the provision of medical care, and it must be posted in a public place in each hospital.\n\nAppointing your Health Care Agent New York State’s Proxy Law\n\nA law called the New York Health Care Proxy Law allows you to appoint someone you trust – for example, a family member or close friend – to decide about treatment if you lose the ability to decide for yourself. You can do this by using a Health Care Proxy form like the one inside, to appoint your “health care agent.”\n\nThis law gives you the power to make sure that health care professionals follow your wishes. Your agent can also decide how your wishes apply as your medical condition changes. Hospitals, doctors and other health care providers must follow your agent’s decisions as if they were your own.\n\nYou can give the person you select, your health care agent, as little or as much authority as you want. You can allow your agent to decide about all health care or only certain treatments. You may also give your agent instructions that he or she has to follow.\n\nWhy should I choose a health care agent?\n\nIf you become too sick to make health care decisions, someone else must decide for you. Health care professionals often look to family members for guidance. But family members are not allowed to decide to stop treatment, even when they believe that is what you would choose or what is best for you under the circumstances. Appointing an agent lets you control your medical treatment by:\n\n- allowing your agent to stop treatment when he or she decides that is what you would want or what is best for you under the circumstances;\n- choosing one family member to decide about treatment because you think that person would make the best decisions or because you want to avoid conflict or confusion about who should decide; and\n- choosing someone outside your family to decide about treatment because no one in your family is available or because you prefer that someone other than a family member decide about your health care.\n\nHow can I appoint a health care agent?\n\nAll competent adults can appoint a health care agent by signing a form called a Health Care Proxy. You don’t need a lawyer, just two adult witnesses. You can use the form printed here, but you don’t have to.\n\nWhen would my health care agent begin to make treatment decisions for me?\n\nYour health care agent would begin to make treatment decisions after doctors decide that you are not able to make health care decisions. As long as you are able to make treatment decisions for yourself, you will have the right to do so.\n\nWhat decisions can my health care agent make?\n\nUnless you limit your health care agent’s authority, your agent will be able to make any treatment decision that you could have made if you were able to decide for yourself. Your agent can agree that you should receive treatment, choose among different treatments and decide that treatments should not be provided, in accord with your wishes and interests.\n\nHow will my health care agent make decisions?\n\nYou can write instructions on the proxy form. Your agent must follow your oral and written instructions, as well as your moral and religious beliefs. If your agent does not know your wishes or beliefs, your agent is legally required to act in your best interests.\n\nWho will pay attention to my agent?\n\nAll hospitals, doctors and other health care facilities are legally required to honor the decisions by your agent. If a hospital objects to some treatment options (such as removing certain treatment) they must tell you or your agent IN ADVANCE.\n\nWhat if my health care agent is not available when decisions must be made?\n\nYou can appoint an alternate agent to decide for you if your health care agent is not available or able to act when decisions must be made. Otherwise, health care providers will make treatment decisions for you that follow instructions you gave while you were still able to do so. Any instructions that you write on your Health Care Proxy form will guide health care providers under these circumstances.\n\nWhat if I change my mind?\n\nIt is easy to cancel the proxy, to change the person you have chosen as your health care agent or to change any treatment instructions you have written on your Health Care Proxy form. Just fill out a new form. In addition, you can require that the Health Care Proxy expire on a specified date or if certain events occur. Otherwise, the Health Care Proxy will be valid indefinitely. If you have named your spouse as your health care agent and you later become divorced or legally separated, your former spouse can no longer be your agent by law, unless you state otherwise. If you would like your former spouse to remain your agent, you may note this on your current form and date it or complete a new form naming your former spouse.\n\nCan my health care agent be legally liable for decisions made on my behalf?\n\nNo. Your health care agent will not be liable for treatment decisions made in good faith on your behalf. Also, he or she cannot be held liable for costs of your care, just because he or she is your agent.\n\nIs a health care proxy the same as a living will?\n\nNo. A living will is a document that provides specific instructions about health care treatment. It is generally used to declare wishes to refuse life-sustaining treatment under certain circumstances.\n\nIn contrast, the health care proxy allows you to choose someone you trust to make treatment decisions on your behalf. Unlike a living will, a health care proxy does not require that you know in advance all the decisions that may arise. Instead, your health care agent can interpret your wishes as medical circumstances change and can make decisions you could not have known would have to be made. The health care proxy is just as useful for decisions to receive treatment as it is for decisions to stop treatment. If you complete a Health Care Proxy form, but also have a living will, the living will provides instructions for your health care agent, and will guide his or her decisions.\n\nWhere should I keep the proxy form after it is signed?\n\nGive a copy to your agent, your doctor and any other family members or close friends you want. You can also keep a copy in your wallet or purse or with other important papers.\n\nAppointing a health care agent is a serious decision. Make sure you talk about it with your family, close friends and your doctor.\n\nDo it in advance, not just when you are planning to enter the hospital.\n\nFilling out a health care proxy is voluntary. No one can require you to do so.\n\nThe Health Care Proxy Law took effect January 1991; forms signed before that date are valid.\n\nEach patient is provided with a Health Care Proxy form and information about that form (developed by the State Health Department). Hospitals must also provide this form and information to each member of the hospital’s staff. This information must also be posted in a public place in each hospital.\n\n[New York State's Proxy Law; Public Health Law 2994 (effective January 18, 1991)]\n\nAbout the Health Care Proxy\n\nThis is an important legal form. Before signing this form, you should understand the following facts:\n\n1. This form gives the person you choose as your agent the authority to make all health care decisions for you, except to the extent you say otherwise in this form. \"Health care\" means any treatment, service or procedure to diagnose or treat your physical or mental condition.\n\n2. Unless you say otherwise, your agent will be allowed to make all health care decisions for you, including decisions to remove or provide life-sustaining treatment.\n\n3. Unless your agent knows your wishes about artificial nutrition and hydration (nourishment and water provided by a feeding tube), he or she will not be allowed to refuse or consent to those measures for you.\n\n4. Your agent will start making decisions for you when doctors decide that you are not able to make health care decisions for yourself.\n\nYou may write on this form any information about treatment that you do not desire and/or those treatments that you want to make sure you receive. Your agent must follow your instructions (oral and written) when making decisions for you.\n\nIf you want to give your agent written instructions, do so right on the form. For example, you could say:\n\n- If I become terminally ill, I do/don't want to receive the following treatments: [insert treatments].\n- If I am in a coma or unconscious, with no hope of recovery, then I do/don't want [insert options].\n- If I have brain damage or a brain disease that makes me unable to recognize people or speak and there is no hope that my condition will improve, I do/don't want [insert options].\n- I have discussed with my agent my wishes about ____________ and I want my agent to make all decisions about these measures.\n\nExamples of medical treatments about which you may wish to give your agent special instructions are listed below. This is not a complete list of the treatments about which you may leave instructions.\n\n- artificial respiration\n- artificial nutrition and hydration (nourishment and water provided by feeding tube)\n- cardiopulmonary resuscitation (CPR)\n- antipsychotic medication\n- electric shock therapy\n- antibiotics\n- psychosurgery\n- dialysis\n- transplantation\n- blood transfusions\n- abortion\n- sterilization\n\nTalk about choosing an agent with your family and/or close friends. You should discuss this form with a doctor or another health care professional, such as a nurse or social worker, before you sign it to make sure that you understand the types of decisions that may be made for you. You may also wish to give your doctor a signed copy. YOU DO NOT NEED A LAWYER TO FILL OUT THIS FORM.\n\nYou can choose any adult (over 18), including a family member, or close friend, to be your agent. If you select a doctor as your agent, he or she may have to choose between acting as your agent or as your attending doctor; a physician cannot do both at the same time. Also, if you are a patient or resident of a hospital, nursing home or mental hygiene facility, there are special restrictions about naming someone who works for that facility as your agent. You should ask staff at the facility to explain those restrictions.\n\nYou should tell the person you choose that he or she will be your health care agent. You should discuss your health care wishes and this form with your agent. Be sure to give him or her a signed copy. Your agent cannot be sued for health care decisions made in good faith.\n\nEven after you have signed this form, you have the right to make health care decisions for yourself as long as you are able to do so, and treatment cannot be given to you or stopped if you object. You can cancel the control given to your agent by telling him or her or your health care provider orally or in writing.\n\n**Filling Out the Proxy Form**\n\n- **Item (1):** Write your name and the name, home address and telephone number of the person you are selecting as your agent.\n\n- **Item (2):** You may write the name, home address and telephone number of an alternate agent.\n\n- **Item (3):** This form will remain valid indefinitely unless you set an expiration date or condition for its expiration. This section is optional and should be filled in only if you want the health care proxy to expire.\n\n- **Item (4):** If you have special instructions for your agent, you should write them here. Also, if you wish to limit your agent’s authority in any way, you should say so here. If you do not state any limitations, your agent will be allowed to make all health care decisions that you could have made, including the decision to consent to or refuse life-sustaining treatment. You may also state your wishes about organ or tissue donation(s).\n\n- **Item (5):** You must date and sign the proxy. If you are unable to sign yourself, you may direct someone else to sign in your presence. Be sure to include your address.\n\nTwo witnesses at least 18 years of age must sign your proxy. The person who is appointed agent or alternate agent cannot sign as a witness.\n\nHealth Care Proxy\n\n(1) I, ___________________________________________________________\n\nhereby appoint\n\n______________________________________________________________\n\n(name, home address and telephone number)\n\n______________________________________________________________\n\nAs my health care agent to make any and all health care decisions for me, except to the extent that I state otherwise. This proxy shall take effect only when and if I become unable to make my own health care decisions.\n\n(2) Optional: Alternate Agent\n\nIf the person I appoint is unable, unwilling or unavailable to act as my health care agent, I hereby appoint\n\n______________________________________________________________\n\n(name, home address and telephone number)\n\n______________________________________________________________\n\nas my health care agent to make any and all health care decisions for me, except to the extent that I state otherwise.\n\n(3) Unless I revoke it or state an expiration date or circumstances under which it will expire, this proxy shall remain in effect indefinitely. (Optional: If you want this proxy to expire, state the date or conditions here.) This proxy shall expire (specify date or conditions):\n\n______________________________________________________________\n\n______________________________________________________________\n\n(4) Optional: I direct my health care agent to make health care decisions according to my wishes and limitations, as he or she knows or as stated below. (If you want to limit your agent’s authority to make health care decisions for you or to give specific instructions, you may state your wishes or limitations here.) I direct my health care agent to make health care decisions in accordance with the following limitations and/or instructions (attach additional pages as necessary):\n\n______________________________________________________________\n\n______________________________________________________________\n\nIn order for your agent to make health care decisions for you about artificial nutrition and hydration (nourishment and water provided by feeding tube and intravenous line), your agent must reasonably know your wishes. You can either tell your agent what your wishes are or include them in this section. See instructions for sample language that you could use if you choose to include your wishes on this form, including your wishes about artificial nutrition.\n\n(5) **Your Identification (please print)**\n\nYour Name ____________________________________________________________\n\nYour Signature __________________________ Date _________________\n\nYour Address _______________________________________________________\n\n(6) **Optional: Organ and/or Tissue Donation**\n\nI hereby make an anatomical gift, to be effective upon my death, of: (check any that apply)\n\n- [ ] Any needed organs and/or tissues\n- [ ] The following organs and/or tissues ____________________________________________________________\n ____________________________________________________________\n- [ ] Limitations ____________________________________________________________\n\nIf you do not state your wishes or instructions about organ and/or tissue donation on this form, it will not be taken to mean that you do not wish to make a donation or prevent a person, who is otherwise authorized by law, to consent to a donation on your behalf.\n\nYour Signature __________________________ Date __________________________\n\n(7) **Statement by Witnesses** *(Witnesses must be 18 years of age or older and cannot be the health care agent or alternate.)*\n\nI declare that the person who signed this document is personally known to me and appears to be of sound mind and acting of his or her own free will. He or she signed (or asked another to sign for him or her) this document in my presence.\n\nDate __________________________ Date __________________________\n\nName of Witness 1 __________________________ Name of Witness 2 __________________________\n\n(print) __________________________ (print) __________________________\n\nSignature __________________________ Signature __________________________\n\nAddress __________________________ Address __________________________\n\nHealth Care Proxy\n\nProxy is as useful for decisions to RECEIVE treatment as it is for decisions to STOP treatment.\n\nIf a Health Care Proxy form is completed and the patient also has a living will, the living will provides clear instructions for the Health Care Agent that will guide his/her decisions regarding care.\n\nA patient’s wishes regarding artificial hydration and nutrition must be specified on the proxy form. The form may indicate that the proxy knows the patient’s wishes and that the proxy may make decisions regarding artificial nutrition or hydration on his/her behalf.\n\nFilling out a Health Care Proxy is voluntary. No one can require a patient to do so.\n\nThe patient may cancel the proxy, change his/her mind about their current proxy, or change any treatment instruction by filling out a new proxy form.\n\nThe patient may require that the Health Care Proxy expire on a specific date or if certain events occur. If no stipulations are made, the proxy is valid indefinitely.\n\nIf a spouse is the Health Care Agent, and the couple becomes legally separated or divorced, the appointment is automatically canceled.\n\nA nurse can witness the signature of a designated Health Care Agent proxy, but THE NURSE CANNOT BE A HEALTH CARE AGENT OF A PATIENT IN THE HOSPITAL.\n\nSurrogate Decisions\n\nWho is the surrogate?\n\n1. Health Care Agent or proxy\n2. The “surrogate list”\n a. Court-appointed “committee of the person”\n b. A person chosen by others on the surrogate list\n c. Immediate family – spouse, adult children, parents, siblings\n d. Close friends\n e. Family or friends who are healthcare professionals\n\nIf the patient has a proxy, the form must be placed on the patient’s medical record in the appropriate section.\n\nIf the patient reports that he or she has appointed a Health Care Proxy, but the form is not available at the time of admission, the nurse must document on the Initial Assessment Form that a Health Care Proxy exists, noting the name and phone number of the proxy, if available. It is the responsibility of the nursing staff to follow up with the patient and/or family to obtain the signed Proxy Form.\n\nDo Not Resuscitate (DNR) Orders\n\nIt is the policy of KJMC to act affirmatively to support and sustain the life of all patients, including persons who suffer from an irreversible terminal disease and to respect the dignity of all individuals. All patients are provided equitable access to resuscitation without regard to age, category of illness or financial or social circumstances.\n\nBefore obtaining the consent (of the patient or surrogate) to a DNR order, THE ATTENDING PHYSICIAN must provide the patient/surrogate with information about the medical diagnosis, prognosis and the reasonable foreseeable risks and benefits of CPR for the patient, as well as the consequences of the DNR order.\n\nForegoing Life-Sustaining Treatment/Issuing DNR Orders\n\nTo forego life-sustaining treatment or issuing DNR orders, two conditions must be met:\n\n1. The treatment will place an excessive burden on the patient\n2. At least one of the following:\n a. The patient is terminally ill (death within six months)\n b. The patient is permanently unconscious\n c. It is in keeping with the patient’s wishes or is in the patient’s best interest\n d. It is ordered by the court\n\nTypes of DNR Forms\n\n1. State of New York Department of Health non-hospital order for DNR (DOH-3474) – NON-HOSPITAL DNR IS VALID AND SHALL REMAIN IN EFFECT UNTIL THE ATTENDING PHYSICIAN FIRST EXAMINES THE PATIENT THEN DECIDES WHETHER TO ISSUE AN ORDER TO\n a. Continue the DNR, or\n b. Cancel the DNR\n\nAll forms have to be completely filled out and signed by the ATTENDING PHYSICIAN AND WITNESS and/or CONCURRING PHYSICIAN, as applicable.\n\nThe attending should enter a note on the progress notes regarding the discussion and the patient’s condition.\n\nReview of DNR Orders\n\n1. Acute – level care patients – Reviewed by the ATTENDING PHYSICIAN EVERY 7 DAYS (or more often if there is a change in the patient’s condition; the MD must document the review in the patient’s chart).\n2. Long-term care – Each time the patient is required to be seen by the physician but at least every 30 days.\n\nIt is the policy of KJMC to honor decisions made by patients receiving medical care, including decisions to accept or refuse medical or surgical treatments and to honor the advance directives of patients, including living wills, health care proxies and oral statements, to the full extent permitted by law. Copies of KJMC’s Health Care Proxy Policy, DNR Policy and the Policy on Oral and Written Advance Directives are available. KJMC encourages each patient or family member to discuss these issues with the patient’s attending physician. When difficult treatment decisions must be made, patients, families, physicians and any member of the healthcare team may seek the advice of the Hospital Ethics Committee.\n\nColored Identification Bands\n\nColored Identification Bands and colored dots on Patient’s Medical Records Binder indicate the following:\n1. Yellow ID band – Patient has falls risk\n2. Purple band or dot - DNR ordered\n3. Blue dot - Patient has DNI ordered\n4. Red ID band - Patient has allergies\n\nPolicy\n\nThe obligation to participate in the management of pain and relieve a patient’s suffering is an integral part of the role of the physician and nurse. The importance of pain management is\n\nfurther increased when benefits for the patient are realized such as mobilization and shortened hospital stay, as well as patient satisfaction.\n\n**Responsibility**\n\nThe nurse is to assess a patient’s level of pain, as outlined in the following procedure and work actively with the members of the departments of Medicine, Surgery and Anesthesiology to devise an appropriate plan of care. The nurse participates in carrying out that plan of care and evaluating its effectiveness.\n\nRecognize that pain assessment is considered the fifth vital sign that the patient report of pain will be believed and that effective pain management will be given.\n\nOnce an intervention is done for pain relief, reevaluation is done to judge the effectiveness of the intervention.\n\n**Process**\n\n**Step 1**\n\nRecognize the existence of pain\n\n**Step 2**\n\nExplore the subjective component of pain\n\n*Rationale*\n\nPain is a highly complex, individualized and subjective human experience. This step is perhaps the most important step of the process.\n\n*Process:*\n\n1. Detect the level and location of pain. Pain is either deep or superficial and always has a location. However, chronic pain patients may have difficulty localizing the pain.\n\n2. Question the character of pain or sensation. “What does your pain feel like?” *i.e.*, dull, sharp, piercing, boring, achy, shooting, burning.\n\n3. Question the character of pain (mild, severe). This is best accomplished by a pain rating scale. Use patient/resident’s words, *e.g.*, stabbing, aching, burning, sharp. Several pain rating scales are helpful. The Faces Pain Rating Scales are helpful with pediatrics/elderly non-verbal patients. Some examples follow this section.\n\n4. Explore what makes the pain better, what makes it worse and does it radiate.\n\n5. How often does it occur? When does it occur and what is the duration?\n\n6. What causes or what relieves it?\n\n7. Does it interfere with sleep? Appetite? Walking? Mood?\n\n8. If the patient/resident cannot talk, observe for signs of pain, *e.g.*, grimaces, moans, agitation, yelling when touched or dressing.\n\n**Step 3**\n\nObserve the objective parameters\n\n*Remember, with chronic pain objective parameters are often unreliable indications because the body learns to adapt to the painful stimuli. Patient, therefore, may need a pain consultation to help alleviate or learn to adjust to living in pain.*\n\nStep 4\n\nDetermine the meaning of pain for the individual.\n\nThings to consider:\n\n1. For what reason does the patient feel he/she is experiencing pain?\n2. What is the individual’s understanding of pain?\n\nStep 5\n\nExplore the influencing factors. Consider:\n\n1. Physical status\n2. Environment\n3. Age, sex, socio-cultural group\n4. Personality type\n5. Psychological status\n\nStep 6\n\nAlert the physician when the medication has not helped the patient’s pain.\n\nSource: Excerpts from “Pain Assessment Guidelines,” Nursing Policy and Procedure Manual\n\nSample Pain Rating Scales\n\n| Numerical Pain Scale |\n|----------------------|\n| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |\n| No Pain | Worst Pain Imaginable |\n\nFaces/Numeral Pain Measurement Tool – Faces Measurement Tool for Pts.: ♦ 3 to 10 years ♦ elderly or ♦ with a language barrier. Use the Numeric Measurement Tool for patients > 10 years\n\nNo Pain 2 4 6 8 10\n\n• FLACC Behavioral Pain Scale – (F) Faces, (L) Legs, (A) Activity, (C) Cry, (C) Consolability – is for patients who are:\n ♦ non-verbal ♦ under 3 years old ♦ mentally challenged or ♦ have a decreased LOC. Measure each of the five FLACC Scale categories scoring from 0 – 2, by circling the FLACC score that correlates with the patient’s demonstrated behavior and add the total score (which ranges from 0 – 10).\n\n| Categories | Score 0 | Score 1 | Score 2 |\n|------------------|-------------------------------------------------------------------------|-------------------------------------------------------------------------|-------------------------------------------------------------------------|\n| FACE | No particular expression or smile | Occasional grimace or frown, withdrawn, disinterested | Frequent to constant frown, quivering chin, clenched jaw |\n| LEGS | Normal position or relaxed | Uneasy, restless, tense | Kicking or legs drawn up |\n| ACTIVITY | Lying quietly, normal position, moves easily | Squirming, shifting back and forth tense | Arched, rigid or jerking |\n| CRY | No cry (awake or asleep) | Moans or whimpers; occasional complaint | Crying steadily, screams or sobs, frequent complaints |\n| CONSOLABILITY | Content, relaxed | Reassured by occasional touching, hugging or being talked to distractible | Difficult to console or comfort |\n\n**Facts About Latex Allergies**\n\nLatex is a natural elastic product that can cause an allergic reaction ranging from a mild reaction to a life-threatening emergency.\n\nMild reactions:\n\n- Rash\n- Hives\n- Cold symptoms\n- Itchiness\n\nLife-threatening reactions:\n\n- Wheeze\n- Lump in throat\n- Difficulty breathing\n- Change in vital signs\n\nAll reactions are to be reported, evaluated and treated immediately.\n\nCustomer Services\n\nWe recognize that a patient’s recovery is aided by sympathetic surroundings and that admissions and outpatient visits to our medical center are affected by interpersonal relationships and by the image we project.\n\nIt is the responsibility of all employees, physicians, agency personnel and students to ensure that his or her behavior, attitude and actions are at all times consistent with the standards as described in the HOSPITALity House Rules.\n\nHOSPITALity House Rules\n\nAPPRECIATE: Say a genuine thanks. Enjoy your coworkers and being part of the team. Keep focused on what is positive about each member.\n\nLISTEN: When someone speaks up, complains or confronts, listen and don’t be defensive.\n\nSHOW RESPECT: Treat coworkers with dignity, empathy and professionalism, no matter what their job. None of us is better than anyone else.\n\nPITCH IN: Accept and do with energy even if it’s not your job. Help each other and you help your customers.\n\nBE PRODUCTIVE: Concentrate on your work and produce results. Enable coworkers to do the same.\n\nRECOGNIZE EVERY INDIVIDUAL: There’s always a person behind the position. Break the ice. Be warm and friendly. Make eye contact. Express words of concern.\n\nFOLLOW THROUGH: Meet deadlines and keep promises. Everything you do effects someone else. Earn people’s trust and confidence.\n\nACT AND LOOK PROFESSIONAL: You shape our image.\n\nATTEND TO DETAILS: Quality and accuracy in your work reflects on all of us.\n\nTAKE RESPONSIBILITY FOR MAKING OUR MEDICAL CENTER WORK BETTER: Initiate improvements, make suggestions, identify problems and implement solutions. Remember that good enough never is.\n\nSTRETCH TO SERVE THE CUSTOMERS: Internal or external, go the extra mile. Without customers we have no medical center.\n\nFall Prevention\n\nThe following can be incorporated into patient/resident education.\n\nFALLS ARE THE NUMBER ONE REASON FOR UNNECESSARILY PROLONGED STAYS!\n\nMost of you will require assistance at some point to get out of bed and to walk, especially to and from the bathroom. This environment is different than your home. These are some tips to make your stay a safe one. We encourage you to ask us for help.\n\n- Be sure you know how to use the call switch. When you call, someone will respond as soon as possible, but it may not be immediate in non-emergency situations. Try not to wait until the last minute to ask for help in going to the bathroom.\n\n- You are not bothering us by using the call switch, we are happy to help. When someone responds to your call over the intercom, please let them know what you need.\n\nYou must call for help to get up at any time that you feel weak, dizzy or lightheaded. Do not try to get up by yourself.\n\nIf the family has released restraints during a visit, the family is asked to tell a nurse before they leave the unit.\n\nBe sure to wear slippers, shoes or sneakers with non-skid soles at any time that you get out of bed, even for short distances.\n\nTake your time when standing from the bed or chair. Plant your feet firmly, push up with your arms and rise slowly.\n\nDo not lean on bedside tables, IV poles or other rolling objects.\n\nSecure loose clothing and medical equipment when walking.\n\nUse the call switch in the bathroom if you become weak or need assistance back to the bed or chair. After pulling the emergency switch in the bathroom, stay in the sitting position until help arrives.\n\nAsk to have objects such as your bedside table, telephone and call switch within your easy reach.\n\nPlease have your family bring your glasses, contact lenses, hearing aids, braces or other assistive devices into the hospital. Please wear all assistive devices that you wore before admission.\n\nYOUR COOPERATION IS ESSENTIAL. YOUR SAFETY IS OUR FIRST CONCERN!\n\n## Competency Exam: Chapter 4\n\n### Patient/Resident Rights\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. There are three types of Advance Directives: living will, health care proxy and DNR. | a. True \nb. False |\n| 2. Patient's requests regarding hydration and nutrition must be specified on the proxy form. | a. True \nb. False |\n| 3. A nurse can witness the signature of a designated health care agent. | a. True \nb. False |\n| 4. The patient and the resident have a right to refuse right to privacy and to know the names, position and function of hospital staff. | a. True \nb. False |\n| 5. Which statement about Advance Directives is true? | a. An Advance Directive is written or oral instructions to the MD and other healthcare professionals outlining the type of medical care desired by the patient in the event the patient is incapable of making their own healthcare decisions. \nb. Advance Directives are documents which need to be drawn up by a lawyer prior to admission. \nc. Do Not Resuscitate orders are reordered daily. \nd. All of the above. |\n| 6. KJMC’s mission is to promote quality healthcare in a caring environment to a diverse population in a cost-effective manner. | a. True \nb. False |\n| 7. Which of the following are considered part of the HOSPITALity House Rules? | a. Prompt mail delivery to all departments. \nb. Lifting heavy objects without hurting your back. \nc. Hand washing \nd. Serving all customers with a smile, keeping promises, listening, showing respect and keeping patients informed. |\n| 8. Patients with latex allergy may have symptoms of mild rash, hives, wheezing and difficulty breathing. | a. True \nb. False |\n| 9. The patient and the resident have a right to a smoke-free environment at KJMC and at RNH. | a. True \nb. False |\n| 10. The patient and the resident have a right to complain without fear of reprisal. | a. True \nb. False |\n\nChapter 5: Risk Management\n\nPurpose\n\nThis module was designed to review the laws that impact on the Department of Patient Care Services and the key elements of the Risk Management Program.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. Define an Occurrence/Incident\n2. Explain the process for filling out an Incident Report\n3. Define Professional Misconduct\n4. Document accurately in the patient’s medical record\n5. Identify elements of the Risk Management Program\n6. Understand confidentiality\n7. Complete the competency exam\n\nPart 5A: Incidence/Occurrence Reporting\n\nDefinition: An Incident/Occurrence is an unexpected event that resulted in or could have resulted in an injury or other loss to patient, visitor or volunteer.\n\nReasons for Completing Incident Reports:\n\n1. Provides documentation of incident\n2. To refresh memory\n3. Regulatory requirement of TJC and the New York State Department of Health\n4. Insurance/claims management\n5. Continuous Quality Improvement (CQI)\n\nComplete an Occurrence Report for all:\n\n1. Patients\n2. Visitors\n3. Attending Physicians\n4. Volunteers\n\nOccurrence Reports:\n\n1. Are not punitive in nature\n2. Are not kept in employees’ personnel files\n3. Are quality control monitors which identify problems, thus assisting the risk manager and the nursing staff to promote quality patient care in a safe environment\n\nMedical Safety Device Act of 1991:\n\n1. All medical facilities are required to report and document any medical device-related incident/event to the FDA and device manufacturer.\n2. The Risk Management Department is to be notified as soon as possible so that all appropriate documentation can be completed.\n\nGeneral rules for completing an Incident Report:\n\n1. Be objective\n2. Be concise\n3. Write legibly\n4. Do not complain about staffing problems or personal conflict\n5. Fill in completely\n6. Notify ADN, Clinical Nurse Managers or Nursing Coordinators\n7. Never make a copy\n8. Never write “Incident Report filled out” in the medical record; document everything that occurred in the medical record\n9. Never place the Incident Report on the patient’s medical record\n10. Never write words like “error,” “inadvertent,” “wrong,” “careless,” “mistake,” etc. in relation to an occurrence\n11. DO NOT use the Occurrence Report to explain away error. Document exactly what happened.\n\nPart 5B: Risk Management\n\nDefinition of Risk Management:\n\n1. A scientific approach to the problem of dealing with the risks faced by individuals and businesses\n2. A systematic approach to the prevention of malpractice claims\n\nGoals of Risk Management:\n\n1. Preventing injuries\n2. Protecting human and other resources\n3. Protecting financial assets\n4. Loss prevention through risk identification and risk analysis\n5. Loss reduction by claims management\n6. Monitoring and evaluation through risk identification and risk analysis\n\nRole of the risk manager:\n\n1. Risk identification: Troubleshoot problems and assist in development of patient care programs, e.g., volunteer feeder, early ambulation\n2. Risk analysis and control: Follows up on occurrences (e.g., equipment failure protocol), ensures safety of patient and staff (e.g., fall prevention program), tracks occurrences\n3. Consultation for medical/legal issues which arise during day-to-day activities (e.g., discharge planning, Advance Directives, consent issues)\n\nPart 5C: Documentation\n\nThe medical record is a legal record that provides a medical history which then becomes a guide for treatment and a document used for insurance reimbursement.\n\nGeneral Tips for Good Documentation\n\nDO:\n\n1. Take credit for all that you do. Remember if it is not documented, it is not done (even if you did it)\n2. Keep your documentation simple and concise\n3. Use the correct terminology – be professional\n4. Make sure your spelling, grammar and punctuation is correct\n5. Write legibly\n6. Use hospital-approved abbreviations. Do not make up your own. *e.g.*, MOD is NOT an acceptable abbreviation\n7. Date, time and sign all documentation\n8. Cross out all blank spaces in your documentation\n9. Be objective; provide just the facts – don’t give your opinion\n10. Make your documentation relevant. Show appropriate care given. If the patient is admitted with pneumonia, writing that he has a crooked little toe is irrelevant except if it is bleeding or if something is wrong with it. Be sure to document sputum, cough, breath sounds, shortness of breath, etc.\n\n11. When consultations are requested, address all recommendations in your record\n\n**DON'T:**\n\n1. Be ambiguous – write exactly what you mean\n2. Be redundant – you need to write it only once. Remember, the graphics check-off is sufficient. Documentation does not have to be in narrative form\n3. Libel – be careful what you write. It may come back to haunt you. Example: never write, “Pt. is a drug addict.” You may, however, write, “Pt. states, ‘I am a drug addict.’”\n4. Document “attending aware.” Instead, write “Dr. Green notified (or ‘informed’) at 5:00 p.m.”\n5. Cross out or use white out when you have made an error. Place one single line through the error, date and initial.\n6. Write “Paged Dr. Green” three times but he didn’t answer. He does this all the time.” Instead, write, “Attending paged at 3:00 p.m., 3:15 p.m. and 3:20 p.m., without a reply. Senior Surgical Resident paged at 3:22 p.m., also without a reply. Mr. Kent, DON, notified of situation at 3:30 p.m.” Use your chain of command to follow up on the incident.\n\n**Part 5D: Professional Misconduct**\n\nLicensed professionals must meet certain standards of conduct established by the Legislature and Regents.\n\nThe Office of Professional Discipline is responsible for enforcement of these rules and regulations.\n\nProfessional misconduct goes beyond acts committed during the practice of the profession to certain acts committed in the practitioner’s personal life.\n\nExamples of Professional Misconduct are as follows:\n\n1. Gross incompetence, gross negligence on a particular occasion or on more than one occasion\n2. Abandonment, abuse, neglect or harassment or patient\n3. Practice by unlicensed person or practicing the profession while license is suspended\n4. Permitting, aiding and abetting an unlicensed person to perform activities requiring a license\n5. Practice beyond authorized scope of profession\n6. Refusal to provide professional service on the basis of a client’s racial, religious, national or cultural background\n7. Practice of profession while the ability to practice is impaired by alcohol, drugs or physical or mental disability\n8. Criminal conviction\n9. Failure to follow Infection Guidelines – Standard Precautions\n10. Fraudulent or deceitful practice by licensed professional\n\nPart 5E: HIV Confidentiality\n\nConfidentiality\n\nOn February 1, 1989 a law was passed in New York State to provide rules for handling AIDS-related information and to encourage people who are at risk to be tested for HIV (Human Immunodeficiency Virus), the virus that causes AIDS.\n\nThe basic elements of the law are as follows:\n\n1. Patients must sign a special consent form before they can be tested for HIV\n2. Counseling must be provided to patients before and after being tested for HIV\n3. This counseling should include, among other things, information regarding anti-discrimination laws and information on ways to prevent the spread of HIV\n4. Patients must be offered the option to test anonymously for HIV\n5. Insurance companies must inform individuals if they are planning to base any part of their coverage on a test for HIV\n6. Insurance companies must obtain written consent before they can request that someone be tested for HIV\n\nConfidentiality and Disclosure\n\n1. In order to provide appropriate care and treatment, healthcare providers must record HIV/AIDS-related information in the patient’s medical record\n2. Healthcare providers must have policies and procedures in place to guarantee that all HIV/AIDS-related information remains confidential\n3. A physician may request that a patient who has tested positive for HIV inform his or her contacts. If the patient is unwilling, the physician has the authority to advise those contacts that they may be at risk. However, the identify of the patient must remain confidential\n\nThe New York Civil Practice Laws and rules state that a person authorized to practice registered professional nursing and licensed practical nursing (among others) shall not be allowed to disclose any information which was acquired while in a professional capacity with a patient and which was necessary to that professional relationship, unless the patient waives the privilege.\n\nA breach of the HIV confidentiality law carries with it a criminal penalty. It is considered a misdemeanor. Violation of the law may result in the imposition of a personal fine of $10,000.\n\nPart 5F: Sentinel Event Policy/Patient Safety\n\nThe Joint Commission on Accreditation of Healthcare Organizations (TJC) launched its new Sentinel Event policy on April 1, 1998. The policy applies to all accredited organizations and encourages facilities to voluntarily report any serious incident qualified as a sentinel event within five business days of its occurrence or of learning of its occurrence. THE TJC DEFINES A SENTINEL EVENT AS AN UNEXPECTED OCCURRENCE INVOLVING THE DEATH OR SERIOUS PHYSICAL OR PSYCHOLOGICAL INJURY OR THE RISK THEREOF.\n\nThe following events are deemed Sentinel Events that must be reported to the TJC:\n\n1. Medication error which results in patient death, paralysis, coma or other major permanent loss of function\n\n2. Falls which result in patient death or major permanent loss of function\n\n3. Any intrapartum maternal death\n\n4. Any perinatal death unrelated to congenital condition in an infant having a birth weight greater than 2500 grams\n\n5. Surgery on the wrong patient or wrong body part\n\n6. Patient suicide, including suicides following treatment\n\n7. Patient elopement resulting in a temporally-related death (suicide or homicide) or major permanent loss of function\n\n8. Hemolytic transfusion reaction\n\n9. Infant abduction\n\n10. Infant discharged to the wrong family\n\n11. Rape (by another patient or staff member)\n\nEvery Sentinel Event undergoes the process of Root Cause Analysis. This is a process for identifying the most basic causal factors that underlie the variation in performance that contributed to the Sentinel Event.\n\n**Part 5G: New York State Patient Occurrence Reporting and Tracking System (NYSPORTS)**\n\nAs an Article 28 facility, as defined by the New York Public Health Law, we are required to track and report to the Department of Health all “occurrences.” An occurrence is an unintended and undesirable development in an individual patient’s condition which occurs in a hospital. The purpose of identifying these occurrences is to identify any trends which may be developing so that corrective actions may be put into place, thus allowing us to improve patient care and reduce the risk of harm to patients.\n\nSome occurrences are serious enough to require individual case review. Because they are rare occurrences, they are “tracked at the region or state level with the expectation that when viewed in conjunction with similar issues from other hospitals, opportunities for improvement can be developed.”\n\n## 2011 NYPORTS Reportable Codes Requiring a Root Cause Analysis (LEVEL 1)\n\n| Category/Code | Description |\n|---------------|-------------|\n| 108 | Medication error associated with a serious injury \nUse detail code 915 with subcode: RX |\n| 109 | Medication error associated with a near-death event \nUse detail code 915 with subcode: RX |\n| 110 | Medication error associated with a patient death \nUse detail code 915 with subcode: RX |\n| 701 | Patient or staff death or serious injury associated with a burn incurred from any source in the course of a patient care process in a healthcare setting |\n| 902 | Specific patient transfers from D&TC’s to a hospital (D&TC’s code only) |\n| 911 | Surgery or other invasive procedure performed on the wrong site \nAdd appropriate subcode: \nDIG: Wrong digit \nLEV: Wrong level \nSID: Wrong side \nSIT: Wrong site \nSurgery or other invasive procedure performed on the wrong patient \nPAT: Wrong patient \nWrong surgical or other invasive procedure performed on a patient \nOTH: Wrong procedure |\n| 913 | Unintended retention of a foreign object in a patient after surgery or other invasive procedure |\n| 915 | Patient death and/or serious injury: \nAdd appropriate subcode: \nPatient death or serious injury associated with a fall while being cared for in a healthcare setting \nFAL: Fall related death or serious injury \nMaternal death or serious injury associated with labor or delivery while being cared for in a healthcare setting \nMAT: Maternal death or serious injury \nDeath or serious injury of a neonate associated with labor and delivery \nNEO: Neonatal or stillborn death or serious injury \nPatient death or serious injury associated with a medication error. \nRx: Death or serious injury associated with a medication error \nIntra-operative or immediately post-operative/post-procedure death in a ASA class 1 or ASA class 1E patient \nSUR: surgical death |\n| 921 | Death or serious injury of a patient or staff member resulting from physical assault (i.e., battery) that occurs within or on the grounds of a healthcare setting. |\n| 922 | Patient suicide, attempted suicide or self-harm that results in serious injury while being cared for in a healthcare setting |\n| 923 | Patient death or serious injury associated with patient elopement (disappearance) |\n| 938 | Patient death or serious injury associated with the use or function of a device in patient care in which the device is used or functions other than as intended |\n\n| Category/Code | Description |\n|--------------|-------------|\n| 961 | Abduction of a patient of any age |\n| 962 | Discharge or release of a patient of any age, who is unable to make decisions, to other than an authorized person |\n| 963 | Sexual abuse/sexual assault on a patient or staff member within or on the grounds of a healthcare facility |\n\n### 2011 NYPORTS Reportable Codes Not Requiring a Root Cause Analysis (LEVEL 2)\n\n| Category/Code | Description |\n|---------------|-------------|\n| 914 | Misadministration of radiation or radioactive material including the misadministration of contrast media |\n| 931 | Strike by hospital staff |\n| 932 | External disaster outside the control of the hospital which effects facility operation |\n| 933 | Termination of any services vital to the continued safe operation of the hospital or to the health and safety of its patients and personnel |\n| 934 | Poisoning occurring within the hospital |\n| 935 | Hospital fire or other internal disaster disrupting patient care or causing harm to patients or staff |\n| 937 | Malfunction of equipment during treatment or diagnosis or a defective product which has the potential for adversely affecting patients or hospital personnel |\n\nEffective July 2011\n\n---\n\n**Part 5H: Bioethics Committee**\n\n**Purpose**\n\nThe purpose of the Ethics Committee is to address any ethical issues by promoting and facilitating communication and sharing of information so mutual understanding between healthcare providers and receivers is achieved.\n\n**Consultation**\n\nConsultation is available to deal with biomedical ethical issues on behalf of patient, family and healthcare providers. The consultation team provides a forum through which:\n\n1. Disputes involving Advance Directives including DNR orders, Health Care Proxies, living wills, etc. will be mediated by the Committee or designee thereof.\n2. Assessments will be made of written and oral Advance Directives, other than DNR and Health Care Proxies, to ascertain whether the “clear and convincing evidence” standards are met.\n3. The rights of patients, family and health team members are clarified.\n4. Issues are discussed, clarified and mediated.\n5. Support is offered to involved decision makers.\n\nThe request for a consultation can be made by the patient/family or healthcare provider by calling Risk Management, ext. 5229, or Patient Relations, ext. 5333. On evenings, nights, weekends and holidays, a consultation request is made by contacting the Administrator on duty, beeper 232 or calling the operator to be connected to the Administrator on duty.\n\nIf an ethical issue/dilemma arises which must be handled immediately, the Ethics Committee has a subcommittee that can be contacted on a 24-hour basis. The team consists of:\n\n1. Director, Pastoral Care\n2. Director, Risk Management\n\n3. Director, Nursing Services\n4. Director, Patient Relations\n5. Medical Director\n6. Director, Social Services\n\nThree team members can provide consultation, when necessary, to patient/family and/or a healthcare provider.\n\nConsultation forms are completed by Patient Relations or Risk Management and are maintained in the Department of Patient Relations. Reference to the cases presented is made in the Committee minutes.\n\n**Education**\n\nThe Committee will provide education to patients, families, healthcare professionals and the community by sponsoring lectures and distributing written educational material.\n\n---\n\n**Part 5I: Organ Donation**\n\n**The Health Care Professional's Role in Donation**\n\nWhile the list of those awaiting life-saving organs grows daily, the number of donors has not changed significantly over the past several years. We are asking for the health care professional’s vital assistance in helping close this gap and increase donation.\n\n**You Can Help By:**\n\n- Understanding that organ donors are not only young trauma victims, but increasingly come from a pool of older patients (50 plus) who suffer brain death from anoxic injury or cerebral vascular events. There is no significant difference in kidney function in transplanted kidneys over the age of sixty as compared to younger kidneys. **Chronological age does not rule out a donor.**\n\n- Knowing that many of the conditions that had previously contraindicated donation, such as hypertension or diabetes, are no longer considered automatic rule-outs, rather they are evaluated on a case by case basis. **The only absolute contraindications to donation are HIV disease, metastatic cancer or active hepatitis.**\n\n- Recognizing that families who are kept well informed of the patient’s condition, who have a clear understanding of brain death before they are approached about donation, and who are approached in a sensitive manner are statistically more likely to donate. **Approaching a family in a sensitive, timely manner can increase the chance that a family will consent to donation.**\n\n**Please do not approach families about donation without the presence of a Family Counselor from New York Organ Donor Network.**\n\n- Understanding that donation can be as meaningful for a donor family as for the transplant recipients. By referring a potential donor, you ensure the family’s right to make a decision about donation. **It is the family’s legal and moral right to make the decision about donation.**\n\n- Referring every potential case to *New York Organ Donor Network* as early as possible in the brain death protocol. This allows time for us to evaluate for suitability, support the staff, and assist with family approach. Call *New York Organ Donor Network* at 1-800-GIFT-NY (1-800-443-8469).\n\nEnsuring that all potential donors are recognized and referred to the *New York Organ Donor Network* is a crucial role for the health care professional. *Many lives can be saved by your intervention.*\n\n**Eyes: The Transplant Almost Anyone Can Donate**\n\nThe Eye-Bank for Sight Restoration, Inc.\n120 Wall Street\nNew York, NY 10005-3902\n(212) 742-9000; Fax (212) 269-3139\n\n- Donated eyes are used primarily for cornea transplants that restore sight to people who suffer from corneal blindness. The cornea is the clear, dime sized tissue which covers the front of the eye. If the cornea becomes clouded through disease or injury, vision is impaired and sometimes lost entirely.\n\n- The only substitute for a human cornea is another human cornea donated at death by someone who thus leaves a living legacy.\n\n- The cornea was the first successful human transplant, with several cases reported as far back as the early 1900s. With the establishment of The Eye Bank for Sight Restoration in 1944 and widespread publicity about cornea transplants, donor eye tissue procedures were performed. Recipients can go from being legally blind to seeing well – sometimes without the need for corrective lenses. The procedure has a 50 to 90 percent success rate, depending on the injury or disease involved.\n\n- More than 40,000 cornea transplants are performed annually in the United States, with about 1,500 of them taking place in the metropolitan New York area.\n\n- Polls show that 84 percent of Americans approve of organ transplantation and 73 percent would want to donate their eyes at death. Yet a shortage still exists because pledged donors forget to tell their families of their wishes and hospitals often fail to bring up the subject. Unlike vascular organs, the eyes can be donated up to 12 hours following death, long after solid organ donations are no longer possible.\n\n- Almost anyone can donate his or her eyes. Donors can be from ages one through 75 for transplantation. After age 75, the eyes may still be donated for medical education and research. People who have poor vision and wear glasses, or who have had previous eye diseases or surgery can still donate, since these conditions may not affect the cornea. Even cancer patients can be eye donors. There is never a charge to the donor family. Eye donations are approved by every major religion and generally such a donation does not rule out an open casket nor delay funeral arrangements. Eyes donated to The Eye Bank that are not medically suitable for transplant are used for medical research and education.\n\n- Anyone wishing to be an eye donor can do so by signing a uniform donor card, checking off the form on the back of the New York State driver's license or signing an eye donor pledge card from The Eye Bank for Sight Restoration, 120 Wall Street, New York, NY 10005-3902, 212-742-9000. Next of kin can donate a deceased family member's eyes by signing a consent form.\n\n**Important:** *If you wish to be an eye donor, tell your family*\n\nRevised December 2015\n\nChapter 5: Risk Management · 102\n\n## Competency Test: Chapter 5\n\n### Risk Management\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. An Occurrence/Incident is defined as the following. | |\n| a. Unexpected event which results or could have resulted in an injury or other loss |\n| b. Employee accident |\n| c. Hospital holiday |\n| d. Snow day |\n| 2. You complete an Incident Report for the following persons: patients, visitors, attending physicians, volunteers | |\n| a. True |\n| b. False |\n| 3. Examples of Occurrence/Incidents are medication errors and falls sustained in the hospital | |\n| a. True |\n| b. False |\n| 4. Some of the goals of Risk Management are preventing injuries, protecting human and other resources, identifying and investigating risks. | |\n| a. True |\n| b. False |\n| 5. Examples of Professional Misconduct are: | |\n| a. Violating a patient's confidentiality |\n| b. Non-compliance with accepted infection control practices |\n| c. Non-compliance with the healthcare facility’s policies and procedures |\n| d. All of the above |\n| 6. The following should be documented: | |\n| a. Signs and symptoms |\n| b. Treatment/response to treatment |\n| c. Education |\n| d. All of the above |\n| 7. Civil and criminal penalties may be brought against anyone who violates the AIDS Confidentiality Law | |\n| a. True |\n| b. False |\n\nChapter 6: Corporate Compliance\n\nPurpose\n\nThis module was designed to review the corporate compliance program.\n\n*Compliance computer based training is required by all employees*\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. Define corporate compliance\n2. Describe the compliance process\n3. Identify actions to take for suspected fraud and abuse\n4. Recall the basic procedures for assistance under EMTALA\n5. Complete the competency exam.\n\nCorporate Compliance\n\nKingsbrook Jewish Medical Center and Rutland Nursing Home (referred to collectively as “KJMC”), are proud of their long tradition of ethical and responsible conduct. KJMC is committed to conducting its business lawfully and ethically. Each member of the Board of Trustees, each officer, Medical-Dental staff member, each employee and affiliate of KJMC is expected to adhere to this high standard whenever he or she acts on behalf of KJMC, whether dealing with other employees, with patients and their families, with vendors, with regulators, or with the general public. Violations of legal or ethical requirements jeopardize the welfare of KJMC, its employees and patients, and the community it serves.\n\nAccordingly, the Board of Trustees has reviewed and approved a Corporate Compliance Program. A key component of the Program is the Code of Conduct (Code), which is intended as a guide for the conduct of all people affiliated with KJMC. This Code provides guidance on how to resolve questions regarding legal and ethical issues, and establishes a mechanism for reporting possible violations of law or ethical principles within KJMC.\n\nSuccess of the Compliance Program depends on the continuous support of all people affiliated with KJMC. KJMC is committed to providing quality cost effective care to a culturally diverse community. We must work together in upholding the Code to ensure that we continue to be a vibrant provider of healthcare to our community.\n\nThe Code of Conduct establishes the general standards, policies and procedures with which all must comply. Each employee, medical/dental staff member, officer and trustee is required to read, understand and fully comply with the standards established by the Code of Conduct. Copies of the full Corporate Compliance Program are available in the Department of Human Resources and in the office of the Corporate Compliance Officer.\n\nIt is expected that you will ensure that all of the duties you perform on behalf of KJMC will comply with applicable laws, regulations and policies. In addition, you are expected to report to your supervisor, the Compliance Officer or the Compliance Hotline suspected or known violations of the Corporate Compliance Program. It is KJMC’s policy that no adverse action or retribution will be taken against any employee reporting in good faith a suspected violation.\n\nIf you have any questions regarding the Corporate Compliance Program or the Code of Conduct, you should speak with your supervisor, a department head or the Compliance Officer.\n\nQuality of Care\n\nKJMC’s mission is to provide a continuum of outstanding health care services to a culturally diverse community. It is our vision to be distinguished as a premier hospital and trusted partner that advances the well being of individuals, families and communities we serve. All members of the KJMC family, to include Trustees, employees, physicians, consultants and contractors:\n\n• Shall comply with KJMC policies and applicable federal, state and local laws governing patient/resident care, including but not limited to patient/resident rights, patient/resident complaints, and the confidentiality of patient/resident records and information.\n\n• Shall comply with the Emergency Medical Treatment and Labor Act (EMTALA) in providing medical screening examinations and emergency medical treatment to all patients, regardless of the patient’s ability to pay.\n\n• Shall not discriminate based on a patient’s/resident’s race, age, sex, religion, national origin, physical or mental disability, sexual orientation, diagnosis or ability to pay.\n\n• Shall ensure that all patients/residents admitted to our facilities shall receive the same quality of care regardless of insurance coverage or payer source.\n\nCOMPLIANCE WITH LAWS/REGULATIONS\n\nKJMC strives to comply with all of the rules and regulations governing the healthcare industry. All members of the KJMC family, to include Trustees, employees, physicians, consultants and contractors:\n\n• Are required to obey all federal, state and local laws and government regulations pertaining to KJMC.\n\n• Are expected to be familiar with the basic legal requirements that are relevant to his or her duties.\n\n• Are expected to comply with licensure and certification requirements associated with the performance of their job or duties, in accordance with applicable federal, state and local laws.\n\n• Shall comply with KJMC’s departmental, administrative and human resources policies and procedures.\n\n• Shall comply with KJMC policies, applicable federal, state and city law governing patient care including but not limited to patient/resident rights, patient/resident complaints, and the confidentiality of patient/resident records and information.\n\n• Shall refrain from offering or receiving kickbacks or improper inducements to influence KJMC’s decisions regarding purchases of health care services or supplies or regarding patient referrals.\n\n• Shall comply with the Health Insurance Portability and Accountability Act (HIPAA) in protecting against the misuse or disclosure of patients’ health information.\n\n• Any employee who violates the Code of Conduct will be subject to disciplinary action, which may include termination of employment and possibly criminal prosecution. Any Medical-Dental Staff Member who violates the Code of Conduct may be subject to loss of clinical privileges. Any Trustee who violates the Code of Conduct will be subject to expulsion from the Board of Trustees. Compliance with the Code of Conduct will be addressed in the performance evaluations of all KJMC employees.\n\n• All employees of KJMC are expected to report any possible violation of law or ethical standards in accordance with the procedure set forth in this Corporate Compliance Program.\n\nCONFLICTS OF INTEREST\n\nAll members of the KJMC family, to include Trustees, employees, physicians, consultants and contractors, are expected to be loyal to KJMC, to avoid using his or her position for personal gain and to comply with the conflict of interest policy. Generally speaking, a conflict of interest exists when an obligation or situation resulting from an individual’s personal activities or financial affairs may adversely influence his or her judgment in the performance of his or her duty to KJMC.\n\n• It is the policy of KJMC that KJMC will not enter into business arrangements with companies in which a Trustee or employee, or a close relative of a Trustee or employee has an ownership interest or financial relationship.\n\nIt is the policy of KJMC that a Trustee or employee may not work for or provide services to a KJMC supplier during the course of their employment with KJMC. In the event that a Trustee or employee wishes to work for or provide services to a KJMC supplier, the Trustee or employee must first disclose the nature of the proposed arrangement to the CEO and obtain the CEO’s documented approval, in consultation with the CCO.\n\n- It is KJMC’s policy that no Trustee or employee may have an ownership interest in or a financial relationship with:\n - A consultant of KJMC\n - A non-publicly traded company that is a supplier of KJMC\n - A competitor of KJMC\n\nA Trustee or employee is never to accept anything of value from someone doing business with KJMC if the gratuity is offered or appears to be offered in exchange for any type of advantage or favorable treatment. No gift or gratuity in any form may be accepted by a Trustee or employee or any family member of a trustee or employee unless the gift is a commonly distributed item of modest value. Gifts with an estimated value of over $100 from one individual or organization during the course of the year must be reported to the CCO.\n\n**BILLING AND CODING INTEGRITY**\n\nKJMC and its professional staff provide a wide range of services to patients. It is crucial that billing statements to patients and third-party payors accurately reflect the services actually provided, who performed the services, and the correct charges for those services.\n\n- No employee shall submit a bill or claim for reimbursement for a more complex service or item than the service or item provided.\n- Bills or claims for reimbursement must accurately reflect the rules of third-party payors regarding bundling of certain services.\n- No duplicate or separate bill shall be submitted for outpatient services provided within the DRG window for inpatient admissions.\n- Claims shall only be submitted for services that are medically necessary and actually rendered.\n- No employee shall ever bill Medicare as a primary payor when he or she is aware that other types of insurance are available.\n- KJMC staff and KJMC’s external auditors must guard against submission of inflated or inaccurate cost reports.\n- Credit balances may occur when overpayments are made to KJMC. Employees shall report the existence of the balance to Medicare.\n\n**RESPECTFUL ENVIRONMENT**\n\nSafe and competent patient care requires effective communication, collaboration and collegiality by and among all Kingsbrook Affiliates. Thus, all Kingsbrook Affiliates are expected to treat others with respect, courtesy, and dignity, and shall conduct themselves in a professional and cooperative manner, refraining from disruptive behavior and inappropriate conduct. Examples of disruptive behavior and inappropriate conduct which are not acceptable on Kingsbrook premises, include, but are not limited to:\n\n- threatening or abusive language directed at other Kingsbrook Affiliates, or at patients, family members, or other visitors (e.g., belittling, berating,\n\nand/or non-constructive criticism that intimidates, undermines confidence, or implies incompetence);\n\n• degrading or demeaning comments regarding other Kingsbrook Affiliates, patients, family members, or other visitors;\n\n• profanity or similarly offensive language while speaking with or in front of other Kingsbrook Affiliates, patients, family members, or other visitors;\n\n• inappropriate physical contact with another individual that is threatening or intimidating;\n\n• derogatory comments about the quality of care being provided by Kingsbrook, another Kingsbrook Affiliate, or any other individual which comments are made outside of appropriate administrative and/or Medical Staff channels;\n\n• inappropriate medical record entries impugning the quality of care being provided by Kingsbrook, or any other Kingsbrook Affiliate;\n\n• \"sexual harassment,\" which includes any verbal and/or physical conduct of a sexual nature that is unwelcome and offensive to those individuals who are subjected to it or who witness and is affected by it, including, without limitation:\n\n ▪ Verbal harassment through innuendoes, epithets, derogatory slurs, off-color jokes, propositions, graphic commentaries, threats, and/or suggestive or insulting sounds;\n\n ▪ Visual or Non-Verbal harassment through derogatory posters, cartoons, or drawings; suggestive objects or pictures; leering; and/or obscene gestures;\n\n ▪ Physical harassment through unwanted physical contact, including touching, interference with an individual's normal work movement, and/or assault; and\n\n ▪ Other: making or threatening retaliation as a result of an individual's negative response to harassing conduct.\n\nKingsbrook promulgates policies, procedures, rules and regulations to ensure its safe, compliant and effective operation, and the quality of care it delivers. Thus refusal to abide by this Code of Conduct; administrative, departmental and other policies and procedures; and the Medical Staff Bylaws, Rules and Regulations, which relate to the Kingsbrook Affiliates' relationship with Kingsbrook (including, but not limited to, those requirements regarding emergency call issues, response times, medical record keeping, patient care responsibilities, and unwillingness to work cooperatively and harmoniously with others) constitutes unacceptable disruptive and inappropriate behavior.\n\n**HUMAN RESOURCES**\n\nAll employment at KJMC is based on individual merit, personal qualifications and the ability of the applicant to perform the job. KJMC recognizes that everyone, regardless of job classification, belongs to a knowledgeable and skilled health care team which contributes to patient care.\n\n• KJMC does not discriminate in any employment decisions on the basis of race, creed, color, national origin, ancestry, gender, age, disability, marital status, sexual orientation, alienage or citizenship.\n\n• KJMC provides a work environment that enables everyone to work with security and dignity, free from unwelcome, insulting, degrading or exploitive treatment or harassment.\n\n• KJMC encourages and supports a working environment that is free of illegal drugs or alcohol.\n\n• KJMC hires only qualified individuals with proper expertise, license and experience. Qualifications are verified before offering employment.\n\n• KJMC shall not employ or contract with an individual or entity that has been excluded from participation in the Medicare, Medicaid, or any other federally funded healthcare program.\n\n**SAFEGUARDING MEDICAL CENTER ASSETS**\n\nIt is the responsibility of all members of the KJMC family to maintain the integrity of KJMC’s assets, including financial records, equipment, information and data, and facilities against loss, theft and misuse.\n\n• Employees may never participate in the misstatement of KJMC’s accounts.\n\n• Employees may not remove KJMC property from the premises unless prior approval has been obtained.\n\n• Employees are required to safeguard access to data, systems and other proprietary assets. It is essential that all members of the KJMC family properly utilize and protect passwords, and take other necessary precautions to guard against access to information.\n\n• Where an employee is responsible for acquiring and disposing of assets, such employee must be careful to stay within the limits of his or her authority.\n\n**ENVIRONMENTAL CONSIDERATIONS**\n\nKJMC is committed to the provision of a safe, functional and effective environment in which health, safety, privacy and comfort of patients, employees and visitors are the first priority.\n\n• Supervisors and managers, with the assistance of the Safety Officer, are responsible for developing programs to identify, eliminate or minimize any hazards to health and safety in accordance with applicable law.\n\n• Any practice or condition thought to be unsafe must be reported to the Safety Officer immediately.\n\n• All hazardous and infectious waste must be stored, handled and disposed of in accordance with federal, state and local regulations. Any instances of noncompliance must be reported to the Safety Officer.\n\n• KJMC maintains a smoke-free environment. Patients and residents may smoke only in designated smoke areas.\n\n**EMPLOYEE ISSUES AND CONCERNS**\n\nThe success of the Compliance Program depends on maintaining open and effective channels of communication. Employees must be willing to identify and report problems and issues, especially those with regulatory implication. The management team at KJMC is prepared to address issues as they are identified. Managers are encouraged to maintain an open door policy so that employees may refer issues without fear of reprisal.\n\n• If you become aware of an activity that you think may be problematic, or if you have questions about the Code of Conduct or Compliance Program,\n\nplease contact your supervisor immediately. If you are not comfortable doing that, contact the Compliance Officer.\n\n- For additional guidance regarding KJMC policies and procedures, the appropriate manuals should be consulted.\n\n- It is the obligation of all members of the KJMC family to report to the Compliance Officer conduct he or she reasonably believes to be criminal in nature or a violation of this Program.\n\n- Retaliation against a member of the KJMC family for reporting something he or she sincerely believes may be a violation, or for participating in good faith in an investigation of misconduct, is prohibited. Acts of retaliation should be reported immediately and appropriate actions will be taken.\n\n**Deficit Reduction Act / “Whistleblowers”**\n\nOn February 8, 2005, President Bush signed into law the Deficit Reduction Act (the \"DRA\"). Among the most noteworthy provisions included in the DRA is a provision that requires employee education about the False Claims Act (\"FCA\") and applicable laws that protect, and even reward, employees who act as whistleblowers. Kingsbrook prohibits the knowing submission of a false claim for payment from a federally or State funded health care program. Such a submission is a violation of Federal and State law and can result in significant administrative and civil penalties under the Federal False Claims Act, a Federal statute that allows private persons to help reduce fraud against the United States government. To assist Kingsbrook in meeting its legal and ethical obligations, any employee who reasonably suspects or is aware of the preparation or submission of a false claim or report or any other potential fraud, waste, or abuse related to a Federally or State funded health care program is required to report such information to his/her supervisor or Kingsbrook’s compliance officer. Any employee of Kingsbrook who reports such information will have the right and opportunity to do so anonymously and will be protected against retaliation for coming forward with such information both under Kingsbrook’s internal compliance policies and procedures and Federal and State law. However, Kingsbrook retains the right to take appropriate action against an employee who has participated in a violation of Federal or State law or hospital policy. As an organization, Kingsbrook commits itself to investigate any suspicions of fraud, waste, or abuse swiftly and thoroughly and requires all employees to assist in such investigations. If an employee believes that Kingsbrook is not responding to his or her report within a reasonable period of time, the employee shall bring these concerns about Kingsbrook’s perceived inaction to Kingsbrook’s compliance officer. Failure to report and disclose or assist in an investigation of fraud and abuse is a breach of the employee’s obligations to Kingsbrook and may result in disciplinary action.\n\n**HIPAA (Health Insurance Portability and Accountability Act)**\n\n**I. What is HIPAA?**\n\nFederal mandated legislation to protect the patient’s information. It concerns itself with how health care organizations receive, use, handle, store, share, and protect the patient’s health information.\n\n**II. Examples of Protected Health Information**\n\nA. Patient’s prescription’s for medication \nB. Audiotape with detailed patient results on it \nC. Computer file with names and addresses of patients \nD. Hallway and elevator conversations among doctors and nurses\n\nIII. Purpose of HIPAA\n\nA. Insures the patient’s privacy\nB. Secures and protects the patient’s health information\n\nIV. Definitions\n\nA. Protected health information that includes any information that:\n - Relates to the health of an individual\n - Can be used to identify the individual\n - Can be oral or written format of the past, present or future physical or mental health of the individual\n\nB. Security – technical, administrative, and procedural controls on storage and access of data\n\nC. Privacy – protecting the rights of the individual who is the subject of the data, i.e. the “subject individual”\n\nD. Notice – Inform individuals of the types of information maintained and about how it is used and disclosed\n\nE. Choice – Individual must agree to uses and disclosures of information that pertains to him/her\n\nF. Amendment – Individuals that are allowed to inspect information and to correct errors\n\nG. Disclosure Accounting – Individuals have a right to know about disclosures\n\nH. Enforcement – Complaints to be investigated and corrective action taken if information is misused\n\nI. Authentication – Knowing the identity of a computer system user\n\nJ. Access Control – Managing the ability of individual users to access, i.e. read, write, delete, etc.\n\nK. Audit – Tracking significant system events\n\nV. Responsibilities of Those Exposed to Patient’s Health Information\n\nA. Protect the privacy rights of all individuals\nB. Safeguard information entrusted to you\nC. Understand and follow established procedures\nD. Report potential problems immediately\nE. Know when you’re dealing with PHI\nF. Be aware of your surroundings when discussing PHI\nG. Make it your business to understand the wishes of the subject individual\nH. Know the identity of the person to whom you are speaking\n\nVI. How Do You Protect and Secure the Patient’s Health Information?\n\nA. Practice a “clean desk policy”\nB. Ensure that locks are locked\nC. Do not share passwords\nD. Know who is looking over your shoulder\n\nE. Log-off before walking away from your computer\n\nF. Report potential problems immediately\n 1. Do not “look away” from unauthorized uses and disclosures of PHI\n 2. Let your immediate supervisor, HIPAA Official, or Corporate Compliance Officer know if you suspect someone else is using your ID or inappropriately using or disclosing PHI\n 3. Beware of “tech support” requests received by phone or e-mail\n 4. No one should EVER ask for your password. If asked for your password, notify your immediate supervisor, HIPAA Official, or Corporate Compliance Officer.\n\nVII. Ten Ways Your Computer Password Can Be Stolen\n 1. Lucky guess\n 2. Exhaustive search\n 3. Common password list\n 4. Crack encrypted password\n 5. “Sniff” transmitted password\n 6. “Shoulder surfing”\n 7. Find recorded password\n 8. Login screen spoof\n 9. Impersonate tech support\n 10. Snatch initial password before it is changed\n\nVIII. Penalties for Non-Compliance\n A. $100.00 fine per day for each unmet standard (Up to $25,000 per person, per year, per standard)\n B. $50,000.00 fine + one year in prison for improper disclosure of health information\n C. $100,000.00 fine + five years in prison for obtaining health information under false pretenses\n D. $250,000.00 fine + ten years in prison for using health information for personal gain\n\nIX. Additional Information\n • HIPAA Statute and Regulations:\n http://aspe.os.dhhs.gov/admnsimp/index.htm\n • HIPAA News and Resources:\n http://www.hipaadvisory.com/\n • Health Privacy Research:\n http://healthprivacy.org/\n • Security Advisory Links:\n http://timberlinetechnologies.com/advisory.html\n • Security Resource Links:\n http://timberlinetechnologies.com/tech/html\n\nEMERGENCY MEDICAL TREATMENT AND ACTIVE LABOR ACT (EMTALA)\n\nThe Emergency Medical Treatment and Active labor Act (EMTALA) is a federal law which is commonly known as the “anti-dumping” law. EMTALA governs when and how a patient may be:\n\n1. refused treatment; or\n2. transferred from one hospital to another when he or she is in an unstable medical condition\n\nEMTALA applies to virtually all hospitals in the United States.\n\nEMTALA requires all patients presenting to the Emergency Room receive a medical screening examination to determine whether an emergency medical condition exists, and if so, to receive stabilizing treatment, and if necessary, be transferred to a more appropriate facility. The care cannot be delayed by questions about methods of payment or insurance coverage. Emergency Departments must also post signs that notify patients and visitors about their rights to be examined and receive treatment.\n\nIf an individual who is not a hospital patient comes elsewhere on hospital property, an EMTALA obligation on the part of the hospital may be triggered if:\n\n1. the individual requests examination or treatment for an emergency medical condition; or\n2. if the average person would believe that the individual is suffering from an emergency medical condition\n\nThe term “hospital property” means the entire hospital campus including the parking lot, sidewalk and driveway or any building owned by the hospital that is within 250 yards of the hospital.\n\nAn appropriate medical screening examination is an examination that goes beyond the initial triage, utilizing (as appropriate) ancillary services, to determine if an emergency medical condition exists. Any physician or other qualified medical person approved by the Board of Trustees may perform a medical screening examination; however, a physician must assume responsibility for screening examination performed by non-physicians.\n\nAn emergency medical condition is a medical condition manifesting itself by acute symptoms of sufficient severity, such that the absence of immediate medical attention could reasonably be expected to result in:\n\n1. Placing a patient’s health in jeopardy\n2. Serious impairment to any bodily functions.\n3. Serious dysfunction of any bodily organ or part\n\nA pregnant woman who presents to the ED in active labor must be admitted and treated until delivery is completed, unless a transfer is appropriate under the statute.\n\nIf after a medical screening examination, it is determined that the patient requires transfer to another facility, the following must be performed before transfer:\n\n1. Stabilization of the patient within the capability of the facility.\n2. An accepting facility that has the necessary services needed to treat the patient\n3. Obtain consent for transfer from the patient or a representative authorized to act on the patient’s behalf\n4. The treating physician certifies that the medical risks of transferring the patient are outweighed by the medical benefits of the transfer\n5. Transfer by qualified personnel and transportation equipment, as required\n6. Copies of pertinent medical records to accompany the patient to the accepting facility.\n\nA patient or person authorized to act on the patient’s behalf may refuse a medical screening examination, treatment or a consent for transfer after the hospital has informed them of the risks and benefits of the medical screening examination, treatment or transfer. The hospital must take all reasonable steps to obtain a written informed refusal. The medical record must contain a description of the examination and/or treatment that is being refused.\n\nThe Emergency Department is required to maintain a central log of all patients who present for a medical screening examination and treatment. The log must include whether the patient:\n\n- Refused treatment\n- Were treated and released\n- Were transferred to another facility\n- Were admitted to the hospital\n- Discharged\n\nA hospital which negligently violates EMTALA may be subject to a civil monetary penalty up to $50,000 per violation.\n\n## Competency Test: Chapter 6\n\n### Corporate Compliance\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. Corporate compliance is the responsibility of: | |\n| a. The Compliance Officer | |\n| b. Administration | |\n| c. Everyone affiliated with Kingsbrook | |\n| d. The Board of Trustees | |\n| 2. The quality of patient care is not a major compliance issue. | |\n| a. True | |\n| b. False | |\n| 3. It is acceptable to receive gifts from vendors and patients. | |\n| a. True | |\n| b. False | |\n| 4. Employees may discard equipment that is either old or obsolete. | |\n| a. True | |\n| b. False | |\n| 5. Employees may be terminated for making a referral to the Compliance Office. | |\n| a. True | |\n| b. False | |\n| 6. Employees may choose not to participate in compliance investigations.| |\n| a. True | |\n| b. False | |\n| 7. Whistleblowers have no protection against retaliation. | |\n| a. True | |\n| b. False | |\n| 8. The False Claims Act only applies if the employee received a benefit from the claim submitted | |\n| a. True | |\n| b. False | |\n| 9. Patients have no right to control the use of their protected health information | |\n| a. True | |\n| b. False | |\n| 10. A patient who presents to the ED with a medical complaint can be denied a medical screening examination if they are unable to pay or fail to show proof of insurance. | |\n| a. True | |\n| b. False | |\n| 11. Since Kingsbrook does not have obstetrical services, Kingsbrook does not have to examine a woman who presents in active labor. | |\n| a. True | |\n| b. False | |\n| 12. EMTALA does not apply to patients who are in the parking lot. | |\n| a. True | |\n| b. False | |\n\nChapter 7: Domestic Violence / Victims of Abuse\n\nPurpose\n\nThis module was designed to establish organization-wide criteria for the identification and assessment of potential victims of alleged or suspected domestic violence and to ensure that healthcare is provided to victims of domestic violence with respect and understanding of the patient’s need for privacy and compassion.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n6. Describe characteristics of the abuser and the abusive relationship\n7. Recognize the forms of abuse\n8. Identify signs and symptoms of abuse in adults, children and the elderly\n9. Describe the effective intervention for the abused child, adult and elder\n10. Describe the legal requirements for reporting child abuse\n11. Complete the competency exam.\n\nDefinition of Domestic/Family Violence\n\nIn this context, family violence and domestic violence are used interchangeably. Most definitions of domestic violence describe it as a pattern of behavior involving the physical, sexual and psychological abuse of one family member by another.\n\nNew York State defines the word “family” as including various intimate relationships between:\n\n1. Legally married spouses\n2. Separated and divorced couples\n3. Unmarried couples\n4. Same-gender couples\n5. Parents\n6. Children\n7. Elderly persons\n\nCharacteristics of the Abuser and the Abusive Relationship\n\nThere are common characteristics which can help us better understand the mechanism behind an abusive relationship. As is true for the victims, the abusers have no special appearance for which to be observant. We see these people every day. Although no one can be certain why an individual would be abusive, there are some commonalities among abusive/violent personalities.\n\nBattering has, for the most part, been found to be a learned behavior. The batterer often learns from his/her childhood experiences as a victim or onlooker that it is effective to respond to an intimate partner, a relative or a child abusively or violently when he/she is feeling emotions such as stress, anger or frustration. Caution must be exercised when trying to understand the batterer’s history of an event so that the factors do not become excuses for the behavior. THERE IS NO EXCUSE FOR ABUSING ANOTHER HUMAN BEING.\n\nListed below are high-risk factors which may exacerbate a person’s tendencies to behave abusively.\n\n1. Drug/alcohol addiction (often associated, but not causative)\n2. History of abuse or neglect as a child\n3. Unrealistic expectations of child development\n4. Adolescent parents\n5. Absence of extended family or social support\n6. A “special” child, e.g., sick, handicapped, behavioral difficulties\n7. Environmental stress (economic difficulty, illness, unemployment, poor housing conditions, overcrowding)\n\nIn the clinical setting, there are behavioral clues which may be noted in all types of abusers. The abuser may:\n\n1. Be overly aggressive in seeking assistance for the victim\n2. Stay close to the patient and resist all efforts to be separated from the partner when anyone else is present so that the truth about the cause of battering cannot be\n\nOften the patient may be nervous during the initial history taking for fear that the truth may inadvertently be told.\n\n3. Attempt to answer questions directed to the patient in order to assure a cohesive and believable story\n\nSocietal expectations seem to have contributed to what the norm is for families as caregivers of their elderly family members. The expectation is that they administer care with little outside assistance, despite the fact that the population of individuals over 75 has been shown to be the most vulnerable to physical, mental and financial crisis. The elder abuser is characteristically a kind and caring family member who provides the majority of care to the elder, but is overwhelmed by the extent of care required. Consequently, mixed emotions and enormous stress accompany a risky abusive situation for the elderly. The denial of both the caregiver and elder plays a big part in influencing decisions about care outside the home. In many cases, the elder may not admit to being abused for reasons such as fear of losing the caregiver or of suffering an increase in the abuse.\n\n**Why Adult Victims Stay**\n\nIn looking at why victims stay it is important to remain aware that abuse has a repetitive pattern and that over time, this pattern changes into violent acts followed by little to no apologies or retribution. The victim eventually loses hope, feels that there is nowhere to turn, and chooses to stay, but FEELS TRAPPED. Efforts are made by the victim to “manage” the relationship, limit the violence and protect oneself and, if present, the children. As a result, adult and elderly victims stay in the abusive relationship for many reasons. Some of these reasons are:\n\n1. Fear: depression, characteristics of post-traumatic stress disorder, shock (similar to disaster victims)\n2. Lack of money or resources\n3. Lack of education/job skills\n4. Lack of housing; limited use of telephone\n5. Emotional ties to the abuser: lack of outside relationships, fear of retaliation\n6. Religious/cultural: view of woman’s role in marriage\n7. Tradition reinforces the abused person to stay\n8. Alienation/isolation from family members: fear of disclosing, inability of family members to intervene, fear of being demeaned or blamed\n9. Perception that there is no help\n10. Inadequate day care\n11. Family needs: especially the need of the children to have their father around\n12. Fear of losing custody of the children\n13. Discouragement of divorce\n14. Fear of isolation or abandonment in an institution should the elder agree to leave home\n\n**Forms of Abuse**\n\nPower and control may be evident in many forms of abuse and is not specific to one type of victim. At the heart of every battering relationship is an imbalance of power which is used to control the relationship. Abusive behaviors reinforce the power imbalance. The abuser learns that coercion and domination are effective in controlling the relationship. In fact, control and\n\nThe Physical Exam\n\nIn looking at the physical indicators of abuse, you should be observant for injuries which are inconsistent with the mechanism or cause described in the history, as well as the developmental stage of the individual. Signs and symptoms related to physical abuse, sexual abuse and maltreatment of all types of victims are listed on the following pages and may guide you in the recognition of potential incidents of abuse and maltreatment.\n\nAbuse and Mistreatment Recognition Chart\n\nFor All Types of Victims\n\n| Physical Abuse | Maltreatment | Sexual Abuse |\n|-------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------|\n| Unexplained skin lesions, soft tissue swelling, abrasions, hematomas or bruising on various parts of the body in different stages of healing | Failure to thrive, dehydration, malnourishment, if not attributable to medical cause | Sexual assault in a non-consenting adult |\n| Lesions in different body areas reportedly from the same injury | Obvious serious medical/physical problems for which medical care has not been sought | Pain, itching or injuries in genital area in a child or non-consenting adult |\n| Lesions that have distinctive patterns, for example an injury inflicted by a belt buckle, extension cord, wire hanger, radiator form, iron, rope | Lack of supervision or lack of medical care, i.e., illness not followed | Bruises or bleeding in perineal area |\n| Unexplained burns, such as cigar/cigarette burns occurring on hands, feet, back or buttocks that are reportedly secondary to accidental immersion in hot water, e.g., glove or stacking pattern | Poor hygiene, i.e., encrusted dirt, lice, smell of urine or feces, inappropriate clothing | Difficulty sitting or walking |\n| Injuries which occur on central areas of the body such as the head, face, neck, chest, abdomen and genitals | Fatigue, listlessness, consistent hunger | Pregnancy |\n| Evidence on exam of old fractures such as spiral fractures | Ingestion/overdose | Unwillingness to allow physical exam, to participate in classes or use locker rooms, etc. |\n| Unexplained bite marks | Anti-social behavior, inappropriate behavior | Genital discharge, stains or blood on underclothing, torn underclothes |\n| Verbalization of the victim that the injury was caused by a significant other or unknown party | Overly fearful behavior | Fear of person or intense dislike about being left alone with someone |\n| | Extremes of behavior | Poor peer relationships |\n| | | Withdrawal from usual activities |\n| | | Presence of sexually transmitted diseases |\n\n### Specific Signs and Symptoms for Adult, Child and Elder Abuse\n\n| Child | Physical Abuse | Maltreatment | Sexual Abuse |\n|-------|--------------------------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------|\n| | Parents give a story that is not consistent with clinical findings | Suicide attempts or gestures | Sexually transmitted disease in a child |\n| | Reluctance of parents to give information about particular injury | Conduct disorders, i.e., fighting in school, etc. | |\n| | Child is inappropriately wary of adult contacts | Habit disorders, i.e., rocking, sucking fingers | |\n| | Child is frightened of parents | Neurotic behaviors, speech disorders, sleep problems | |\n| | Multiple visits to various hospitals and health facilities | Psychoneurotic reactions, phobias, hysterical reactions | |\n| | Use of hospital facilities in evening and night shifts | | |\n| | Parents respond inappropriately to the severity of the injury | | |\n\n**Long-Term Effects of Child Abuse/Maltreatment**\n\nLong-term effects of this type of abuse may include post-traumatic syndrome, suicidal behavior, psychiatric illness, problems with relationships and/or sexual dysfunction and increased risk for abusing their own children. In addition, the family unit is a powerful educator and plays a critical role in the child’s understanding of acceptable behaviors. Children learn that violence is an effective way to “get what you want” and that it is an acceptable part of loving. It is clear that children suffer a great deal of stress from growing up in an abusive environment. The manifestation of that stress is what we see in their behavior patterns and emotional reactions, such as grief, guilt, constant anxiety, fear or embarrassment.\n\n### Adult\n\n**Physical or Emotional Abuse**\n\n- Attributes obvious abuse-type injuries as being caused by an “accident prone” state\n- Low self-esteem\n- Complaints of pain without tissue injury\n- Suicidal ideation or suicide attempts\n- Multiple, subtle, non-specific and/or vague complaints such as headaches, musculoskeletal complaints, malaise, insomnia, chest pain, hyperventilation or GI disorders\n\n### Elder\n\n| Maltreatment | Sexual Abuse |\n|------------------------------------------------------------------------------|-------------------------------------------------------------------------------|\n| Physical deterioration without underlying pathology | Sexually-transmitted disease in an adult without mental capacity (i.e., would not have been able to consent to sexual relations) |\n| Contractures and decubiti which seen unreasonable in light of the person’s overall presentations | |\n| Dehydration and malnutrition | |\n| Urine burns and excoriation | |\n\nIntervention Strategies for the Adult Victim\n\nThe professional interventions on the following pages are appropriate for all adult victims of domestic violence. The following steps can be used as guidelines for helping an adult victim of abuse. Provide privacy and confidentiality. An individual accompanying the victim who does not appear to be supportive should be asked to wait outside until the patient is examined. Keep in mind that the act of simply addressing the violence is an acknowledgement that the violence is wrong and that there is a way out. Many victims are relieved by the opportunity to share the truth. Please share with the victim of abuse that feelings of hurt, anger and the desire from change are normal and that all information is confidential.\n\nValidate Your Concern\n\n1. Identify the indicators\n2. Ask open-ended questions that do not require more than a yes/no answer; use works like “how?” or “can you describe?”\n3. Listen\n\nSuggested Questions\n\nQuestions that might be asked include:\n\n1. Many patients tell me they have been hurt by someone close to them. Could this be happening to you?\n2. I noticed that you have a number of bruises. Could you tell me how they happened?\n3. Have there been times during your relationship when you have had physical fights?\n4. Have you ever been in a relationship where you have been hit, punched, kicked or hurt in any way? Are you in such a relationship now?\n5. Does your partner ever call you names or put you down?\n\nQuestions to Avoid\n\nAvoid such questions as:\n\n1. Those which ask the victim to explain the batterer’s behavior\n2. Those that begin with “why,” especially those that ask the victim to explain his/her actions or lack of action or suggest that the victim would have the power to control the rage of their abusive and angry partner. The implication is that he/she is somehow responsible for the abuse. The batterer is the only person responsible for the battering behavior.\n\nEmpower the Survivor of Abuse\n\nOffer resources and information such as alternatives and options. By doing this, you will have supported the patient’s independence and autonomy as a decision maker. You have helped the patient to recognize his/her own strengths and resources as a survivor.\n\n1. The Domestic Violence Hotline – The New York City hotline number is 212-577-7777 or 800-621-4673. This may be the first and the most important step the\n\nvictim takes in initiating change. Please assist him/her in facilitating this action. The patient may make this call directly from the hospital if desired. The individuals who answer the phone – 24 hours a day – have experience providing information and emotional support to hundreds of victims. They can provide information on available community resources.\n\n2. **Brochures** – There are a variety of printed materials on domestic violence that are available. You may be able to obtain some of these from the Department of Social Work or the Emergency Department.\n\n3. **Community Resources Overview** – Emergency housing, counseling, legal action and photography are four areas in which victims may need assistance. Hotline counselors are able to make referrals in all of these areas.\n\n4. **Compliance with Chapter 271 of the Laws of 1997** – All maternity and prenatal patients served on an inpatient or outpatient basis by the Medical Center will receive a booklet entitled, “Know Your Rights as a Hospital Patient” which includes the Victim’s Rights Notice and the Notice for Prenatal and Maternity Patients.\n\n5. **Residents and their family are given a Resident Admission Information package.**\n\n### Emergency Housing\n\nEmergency housing, such as shelters and safe home networks, can offer the following services:\n\n1. Safe, temporary living space\n2. Food and clothing\n3. Transportation\n4. Advocacy to court\n5. Welfare and healthcare\n6. Child care and assistance with other alternative housing options\n\n### Counseling\n\nCounseling is the critical focus of care and the nurse can be a strong advocate of its value. The victims’ service programs can make appropriate referrals for the victim and offer services that are available in the community.\n\n### Legal Action\n\nLegal action may be necessary to minimize continued harm and accelerate change. Domestic violence is one of the major reasons police are called to homes. Police in many communities are now able to make arrests based on their own discretion as to probably cause. **Understand that when the patient is an adult, involvement of the police is always the adult victim’s choice;** this allows the victim to have as much control over care received as possible.\n\n- The notification of Protective Services for Adults (PSA) at 212-630-1853. They will send a caseworker to the house, in some cases with a psychiatrist, to evaluate the situation and speak with the suspected victim. The psychiatrist becomes involved when there is a need to declare mental competency. PSA will, in turn, make appropriate referral for community and legal services. Anyone may call PSA including neighbors and home care services.\n\n- Protection of the individual from a physical safety standpoint through hospital admission if indicated or law enforcement involvement if this is what the competent person desires.\n\nNew York State has a mandatory reporting law for nursing home patients, residents of adult homes or patients with home attendants if the suspected abuser is a healthcare provider. Call the New York State Department of Health at 212-613-4842.\n\n**Guidelines for Reporting Cases of Child Abuse / Maltreatment**\n\nGuidelines for reporting child abuse/maltreatment can be found in the KJMC Administration Manual. All cases of suspected or disclosed child abuse, including sexual abuse, must be reported to the Child Abuse Coordinator who, at KJMC, is the Pediatric Social Worker.\n\n1. Monday through Friday, the Social Workers are available on-site from 9:00 a.m. to 5:00 p.m.\n2. There is a social worker available from 9:00 a.m. to 5:00 p.m. on either Saturday or Sunday.\n3. At all other times, the Nursing Supervisor should be consulted (beeper # 232)\n\nAny case requiring a CPS report to the State Central Registry (800-342-3720) will be made by the KJMC social worker. The social worker will complete a DSS 2221-A form and forward a copy to the appropriate Administration for Children’s Services (ACS) field office.\n\nIn addition to the New York State Registry, you may contact the Bureau of Special Squad Office that uses a program called “Prompt Response.” This program has been developed to assure, the greatest extent possible, that specially trained law enforcement staff are expeditiously notified of a case in which there is a very strong suspicion of and/or actual evidence of physical or sexual abuse trauma inflicted upon a child under 11 years of age.\n\nRemember: As a healthcare professional in the State of New York, you are mandated by law to report suspected child abuse while operating in a professional capacity.\n\nAny person who is required to make such a report and willfully fails to do so, is guilty of a Class A Misdemeanor and shall be civilly liable for damages caused by such failure. Any person who makes a report in good faith has immunity from any civil or criminal liability that may result.\n\nThe parent or guardian should be informed of the intent to file a report with ACS. When possible, a social worker should be present at this time.\n\nA child who is reported as a victim of suspected child abuse or maltreatment CANNOT be discharged without the approval of ACS. The social worker will act as a liaison with ACS, making appropriate discharge plans in collaboration with the interdisciplinary team and ACS.\n\nDomestic violence is a problem that affects not only our patients, but healthcare personnel as well. Recognizing what is safe and secure for both our patients and us is essential.\n\n**Hotline Numbers**\n\n| Service | Number(s) |\n|----------------------------------------------|----------------------------|\n| New York State Child Abuse Hotline | 800-635-1522 |\n| | 800-342-3720 |\n| Victim Services Agency Hotline | 212-577-7777 |\n| | 800-621-4673 |\n| National Organization for Victim Assistance (NOVA) | 800-TRY NOVA |\n| Protective Services for Adults (PSA), Central Intake | 212-630-1853 |\n\n## Competency Exam: Chapter 7\n\n### Domestic Violence/Victims of Abuse\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. Characteristics which exacerbate a person’s tendencies to behave | a. True |\n| abusively could include drug/alcohol addiction, history of abuse or | b. False |\n| neglect as a child, unrealistic expectations of child development and| |\n| adolescent parents. | |\n| 2. Abuse could be physical, sexual, psychological and emotional | a. True |\n| | b. False |\n| 3. In looking at the physical indicators of abuse, you should be | a. True |\n| observant for injuries which are inconsistent with the mechanism | b. False |\n| or cause described in the history. | |\n| 4. Sexual abuse could be indicated by pain, itching or injuries in | a. True |\n| the genital area in a child or non-consenting adult. | b. False |\n| 5. Physical abuse could be indicated by injuries which occur on central| a. True |\n| areas of the body such as the head, face, neck, chest, abdomen and | b. False |\n| genitals. | |\n| 6. In the State of New York, you are required by law to report | a. True |\n| suspected child abuse while operating in a professional capacity. | b. False |\n| All cases of suspected or disclosed child abuse including sexual | |\n| abuse must be reported to the appropriate Social Worker for that | |\n| patient care area. | |\n| 7. One can empower the survivor of abuse by offering resources and | a. True |\n| information such as the Domestic Violence Hotline number, brochures | b. False |\n| on domestic violence and a community resources overview. | |\n| 8. When the patient is an adult, involving the police is always the | a. True |\n| adult victim’s choice. | b. False |\n| 9. Abuse does not occur in the elderly person | a. True |\n| | b. False |\n| 10. All of the following are considered acceptable methods of | a. Asking the suspected |\n| obtaining an accurate history EXCEPT: | abuser to stay in the room |\n| | during the interview of |\n| | the victim |\n| | b. Speaking to the |\n| | caretaker separately from |\n| | the victim |\n| | c. Using a non-judgmental,|\n| | non-threatening approach |\n| | d. Speaking to the patient|\n\nChapter 8: Preventing and Managing Crisis in the Agitated Patient (Including Restraint/Seclusion)\n\nPurpose\n\nThis module was designed to establish organization-wide criteria to minimize the use of restraint or to use the very least non-restrictive alternative whenever possible to protect the patient's and resident's rights and dignity and to allow them independent functioning to the extent possible.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. Identify and manage potential risk factors of dangerous patient behavior as well as methods to prevent such behaviors from escalating\n2. Identify, develop and promote preventive strategies for the use of less restrictive and non-restrictive alternatives to restraints\n3. List safe and effective alternatives to manage different patient and resident behaviors\n4. Identify the potential dangers associated with restraint use\n5. List the areas of assessment during monitoring of the patient and resident in restraint\n6. State the required time limits on restraint orders\n7. Identify the requirements for a restraint order\n8. Complete the competency exam\n\nPreventing and Managing Crisis in the Agitated Patient (including Restraint/Seclusion)\n\nA crisis is an event that becomes (or is expected to become) an unstable and dangerous situation affecting an individual or group. For us, this means that there is some concern in the environment about safety of our patients, staff, visitors or others.\n\nThis chapter deals with preventing and managing crisis for the agitated patient. It includes information on restraint and seclusion. However, we note here that the best way to handle a crisis is to prevent it! Although this is not always possible, this is our first choice when we come upon an event that we perceive might become unstable or dangerous.\n\nPeople become agitated when their needs are not met. This is always what we need to think about when someone is agitated. Is there something we can assist them with? Are they comfortable? Are they in pain? Frightened? Identifying and addressing unmet needs is our first step. Sometimes, this is all that is needed.\n\nSometimes, people come into our hospital and become agitated unrelated to unmet needs. They may have a mental illness which causes them to have different thoughts not based in reality, and/or might be under the influence of a substance. Though their agitation might also be due to unmet needs (and we should address them in these people as well), we realize different modalities might be needed for these individuals.\n\nHow do we know that a patient is becoming agitated? Many times, there are behavioral cues that may include, but are not limited to: pacing, fidgeting, yelling, cursing, name calling, posturing, and sweating (not related to physiological issue).\n\nThe remainder of this module deals with the continued management of agitated patients, including the safe use of restraint and seclusion.\n\nRestraints\n\nAssessment\n\nThe hospital staff should be alert in their assessment of the patient to identify manifestations expressed by the patient which may indicate a potential management problem.\n\nPatient Observation\n\nIf the patient’s behavior is demonstrating agitation, restlessness, mood changes, increased anxiety, becoming argumentative or abusive, the staff must address this situation as quickly as possible to diffuse it. IT CANNOT BE IGNORED.\n\nSuggested Strategies\n\n1. Give them personal space\n2. If the person does not speak English, get an interpreter\n3. Attempt to find out what is bothering the person; does information need clarification?\n4. Try to meet their needs (i.e., have the family visit, have a physician speak to patient face-to-face)\n5. Attempt to assess the patient’s physical and emotional status for possible causes – does the patient feel frightened or threatened? If there a history of violence or anger? Is there a metabolic problem such as hypoglycemia, hypopoxia or reaction to sleeping medications?\n\nBehavioral Hints for Dealing with an Agitated Patient/Resident\n\n1. See the patient/resident first\n2. Remove other patients/residents from the immediate area\n3. Do not see the patient/resident alone\n\n4. Do not get blocked in; leave an exit\n\n5. Sit when the patient/resident sits; stand when the patient stands; never tower over the patient/resident or let him/her tower over you\n\n6. Stand to the side of the patient/resident, not directly in front of the patient. This minimizes the amount of body surface area and is less confrontational\n\n7. Move slowly, keep hands visible to patient\n\n8. Be aware of your own body language, stay calm\n\n9. Speak clearly, calmly, and use simple terms; be concise\n\n10. Listen to the patient and look at the patient\n\n11. Acknowledge and validate patient feelings\n - Do not argue\n - Do not respond in an angry or hostile tone\n - Do not take the situation personally; do not threaten the patient\n\n**Definition**\n\nRESTRAINT is any physical or mechanical method used to restrict a person’s freedom of movement, physical activity or normal access to his/her body. Restraint may be used to control activities and/or prevent a patient from causing serious physical harm to himself/herself and/or others. It may be applied only if alternative and/or less restrictive or non-restrictive techniques have been clinically determined to be inappropriate or insufficient to avoid such injury.\n\nHealthcare professionals cite the following clinical indications for restraints may include but are not limited to:\n\n1. Attempted suicide or other physical self-injurious acts\n2. Physically assaultive or combative behavior\n3. Extreme agitation and restlessness\n4. Destruction of property with intent to harm self or others\n5. Interference with or removal of medical devices/continuance of treatment\n6. Intentional or uncontrolled movements and actions that place the patient at risk for falling\n\nALTERNATIVES – Less restrictive or non-restrictive safe and effective alternatives to the use of restraints should be explored and used first whenever possible such as, but not limited to, the following:\n\n1. Increased staff contact\n2. Verbal intervention to calm and/or support the patient and diffuse the situation\n3. Change in the patient’s environment/removal of patient from stimuli\n4. Reality orientation – active listening, diversified activities\n5. Limit setting\n6. Negotiating options, e.g., “shall we go over there?”\n7. Family at bedside\n8. Volunteer to sit at bedside as a “buddy”\n9. Instituting fall prevention policy (for example, leaving the light on during the night shift; offering bedpan/urinal or assistance getting to the bathroom)\n\nThe least restrictive device should always be utilized when restraint is necessary. Restraint devices include:\n\n1. Limb restraints\n2. Vest restraint\n3. Geri-chair with table\n4. Mitts\n5. Side rails\n6. Arm boards\n\n**Highlights of the Conditions and Guidelines for Use**\n\n1. Restraints must be ordered by a physician, except in an emergency. If an emergency situation (immediate danger to self or others) exists and a physician is not immediately available, restraint may be applied/initiated only by, or under the supervision and the direction of, the registered nurse. The physician will evaluate the patient and write an order within one hour.\n\n2. The physician will be called immediately. A record is to be kept of the time of the call and the name of the person contacted. This information shall be documented in the patient’s medical record, as well as an assessment of the patient’s behavior or condition prior to initiation of restraint.\n\n3. Pending the arrival of the physician, the patient/resident must be kept under constant supervision as warranted by the patient’s/resident’s physical condition and emotional state.\n\n4. To ascertain that the use of a restraint is justified, a physician must conduct a clinical/personal assessment of the patient before writing an order authorizing the use of a restraint. The assessment must be documented in the patient’s medical record.\n\n5. Each written order for a restraint must be written on the “Physician’s Orders for Restraint” form and must include the following:\n - An assessment\n - Reason for use\n - Type of restraint to be used\n - Specify the time limit of the restraint\n - Date and time limit of order\n - Physician’s signature and beeper number\n\n6. The order for restraint must be renewed at least every 24 hours.\n\n7. The plan for using a restraint must be consistent with the Patient/Resident Bill of Rights in accordance with the law in New York State.\n\n8. Patient/resident family education should include an explanation for the need for a restraint to prevent misinterpretation and to ensure cooperation. Encourage patient and the family to verbalize their fears/concerns and to provide emotional support.\n\n9. No PRN orders for restraints may be written. Telephone or verbal orders for restraint are not permitted.\n\n10. Upon restraint application, the registered nurse must immediately assess and monitor the patient’s condition regarding, but not limited to, the following:\n - Meals – nutrition, hydration: document Q2h\n - Bathing\n - Use of toilet\n\n• Skin integrity – monitor Q 30 minutes\n• Respiratory status\n• Circulatory status\n• Proper fit/application of restraint – restraint release / ROM: document Q2h\n• Assessment and release of restraints – Q2h\n• Maintenance of proper body alignment\n• Adequate exercise\n• Any changes in physical or mental status\n• Any teaching done or reinforced\n\n11. A means of communication (in tap or call bell) must be available at all times.\n\n12. While restrained the following monitoring parameters will apply:\n\n| Type | Observation: Direct Face - to - Face | Assessment / Release Time by RN Only |\n|-----------------------|-------------------------------------|--------------------------------------|\n| Vest Jacket | Every 30 minutes | Every 2 hours |\n| 1 – 2 Limb | Every 30 minutes | Every 2 hours |\n| 4 Point | Every 15 minutes | Every 2 hours |\n| Seclusion (psychiatry only) | Every 15 minutes | Up to 2 hours |\n| Camisole (psychiatry only) | Every 15 minutes | Up to 2 hours |\n\n13. Documentation: All monitoring will be documented on the flowsheet for monitoring/assessment of a patient in restraint. **Documentation on flowsheet begins when restraints are initiated**\n\n## Competency Exam: Chapter 8\n\n### Restraint/Seclusion\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. Which of these are behavioral hints for dealing with an agitated | a) Don’t argue |\n| patient? | b) Don’t respond in any |\n| | angry or hostile tone |\n| | c) Don’t take the situation|\n| | personally |\n| | d) All of the above |\n| 2. Which of the following are preventive strategies for the user of the| a) Give the person space |\n| least restrictive alternative to restraints? | b) Institute the Fall |\n| | Prevention Protocol |\n| | c) If the person does not |\n| | speak English get an |\n| | interpreter |\n| | d) All of the above |\n| 3. Which of the following are potential dangers associated with restraint use? | a) Constipation |\n| | b) Pressure ulcers |\n| | c) Loss of dignity |\n| | d) All of the above |\n| 4. Restraint application requires careful patient assessment in order | a) True |\n| not to violate patient rights and dignity. | b) False |\n| 5. It is required to explain the purpose and necessity of the restraints| a) True |\n| to the patient and family. | b) False |\n| 6. When a patient has his/her restraints released, toileting, food and | a) True |\n| fluid also need to be offered. | b) False |\n| 7. PRN orders for Restraints are acceptable over the weekend. | a) True |\n| | b) False |\n| 8. The nurse can take a phone order to place a patient in restraint. | a) True |\n| | b) False |\n| 9. Restraint orders include the following: an assessment, reason for | a) True |\n| use, type of restraint to be used; specification of the time limit | b) False |\n| on the restraint; date and time of the order; physician’s signature.| |\n| 10. The patient in a wrist restraint must be released every two hours. | a) True |\n| | b) False |\n\nChapter 9: Patient/Resident and Family Education – Cultural and Religious Practices\n\nPurpose\n\nThis module was designed to acquaint staff with the methods and resources available to provide patient and family education.\n\n*Chapter 11 provides more information on cultural competence*.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. Define who \"family\" is\n2. Define goals of patient and family teaching\n3. State the components of an educational assessment\n4. Identify four educational resources\n5. Complete the competency exam\n\nPatient/Resident Education\n\nPatient/resident education should begin upon entry into the healthcare system and continue through the continuum of care following discharge. It is important for family members to be involved in the patient’s care and receive education specific to the patient’s healthcare needs.\n\nEducation is interdisciplinary and includes the patient, the resident and the family. “Family” is defined as the person(s) who plays a significant role in the patient’s life. This may include an individual (s) not legally related to the patient but who has been identified as playing a significant role. This person(s) is often referred to as a surrogate decision maker if authorized to make care decisions for a patient should the patient lose decision making capacity.\n\nPatient education is a patient’s right as well as a professional responsibility. The hospital is required to assist the patient and family in gaining the knowledge and skills needed to meet the patient’s ongoing healthcare needs. This must be provided in a way that is understandable to the patient and/or family. Establish an environment that encourages patients and families to ask questions, learn and participate in decision making and care.\n\nThe learning needs assessment must include:\n\n1. Cultural and religious and/or spiritual practices, emotional barriers, desire and motivation to learn, physical and cognitive limitations, language barriers, age-related issues, reading, visual and hearing issues, and the financial implications of care choices.\n\n2. Readiness to learn\n\n3. Preferences of the learner\n\n4. Specification of the translator if one is necessary. Barriers must be further discussed in the progress record\n\nWhen patient education is multi-disciplinary, for example the physician, nurse and physical therapist, it should be interdisciplinary. That is, coordinated among the various disciplines involved. It is very important to discuss the teaching plan with the patient and family to identify their educational needs.\n\nThe goals of patient/family education are to:\n\n1. Promote interactive communication between patients/residents and providers\n\n2. Improve patient/resident understanding of their health status, options for treatment and the anticipated risks and benefits of treatment\n\n3. Encourage patient/resident participation in decision making about care\n\n4. Increase the likelihood that patients will follow their therapeutic plans of care\n\n5. Maximize patient/resident ability to cope with his or her health status\n\n6. Enhance the patient/resident’s participation in continuing care\n\n7. Promote health lifestyles\n\n8. Inform the patient/resident about his or her financial responsibility for treatment when known\n\nPsychosocial, spiritual and cultural values also affect patients’ responses to care and their willingness to participate actively in their care and education. Recognizing the impact these values have we support our patients’ involvement in their care and the educational process. We make every effort to ensure this education process supports ongoing interaction between patients and staff.\n\nSpecific educational instruction to patients/residents and their families regarding the patient’s healthcare needs must include, if applicable:\n\n1. The safe and effective use of medication\n\n2. The safe and effective use of medical equipment\n\n3. Instruction on potential drug/food interactions and counseling on nutrition and modified diets\n\n4. Instruction in rehabilitation techniques to facilitate adaptation to and/or functional independence in the environment\n\n5. Access to available community resources\n\n6. When and how to obtain further medical treatment if needed\n\n7. The responsibilities of the patient and family regarding the patient’s ongoing healthcare needs, giving them the knowledge and skills they need to carry out their responsibilities\n\n8. With due regard for privacy, the hospital teaches and helps patients maintain good standards of personal hygiene and grooming including bathing, brushing teeth, caring for hair and nails and using the toilet\n\n**Evaluation of Patient/Resident and Family Education**\n\nThe patient/resident and family can be evaluated on their understanding of the education provided through “return demonstration and verbalizing understanding” of the subject matter. The patient/resident and family’s satisfactory learning outcome as applicable to a specific item/topic is documented in the patient’s medical record. The healthcare provider must number, date and sign on the Patient/Family Education Form in the applicable area upon observation of a satisfactory return demonstration or upon verbalization of understanding evidenced, for example by restatement or correct response to questioning.\n\n**Follow-up on Education**\n\nIn some situations further education is necessary such as re-teaching material reinforcing the material and/or repeating demonstrations of skills. Documentation of this reinforcement is necessary in the patient/resident’s Medical Record.\n\n**Educational Resources**\n\nEducational resources for patient/resident and family teaching include:\n\n1. One-on-one teaching\n2. Pamphlets\n3. Audiotape\n4. Large print\n5. Health education library\n6. Videotapes\n\n**Settings for Education**\n\nEducation will be provided in the following circumstances/settings:\n\n1. Inpatient\n2. Ambulatory care\n3. Pre-operational\n4. Emergency Department\n\n## Cultural and Religious Practices of KJMC Patient Populations\n\n| Religion | Diet | Health Practices | Death Practices | Organ Transplant Beliefs |\n|---------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|\n| Judaism (Orthodox) | Kosher Diet (No pork, shell fish or dairy products served with meat). During religious holidays, diet restrictions may include additional food products. | Sabbath observances may directly impact routine procedures, such as restricting use of the call bell and any other use of electrical equipment. *(For complete description, see handout entitled “Cultural and Religious Practices of the Jewish People”)* Daily prayers and rituals should not be interfered with. | It is believed that the spirit leaves the body at the time of death. Jewish law requires that the body not be left alone. The body is to be buried as soon as possible. | Autopsy is not allowed unless required by law. All body parts must be returned for burial. Organ donation is acceptable if it will save the life of another human being. |\n| Roman Catholic | Not required to adhere to specific dietary practices except during Lent (period between Ash Wednesday and Easter Sunday; some may abstain from meat every Friday). | May request priest to perform the Sacrament of the Sick when seriously ill or near death. | At the time of death, family may request the priest to pray with them. | Not permitted after death. May donate organs, e.g., kidney, while living, provided that the loss of an organ does not deprive donor of life. Clergy may be requested to authorize donation. |\n| Protestants (Lutheran, Methodist, Baptists, Presbyterians, Episcopalians) | *Baptists*: No alcohol; some may not use coffee or tea. *Presbyterians*: May abstain from meat every Friday. ** No other restrictions. ** | May request communion during hospitalization. *Lutherans*: Often request anointing and/or a blessing. *Baptists*: May practice healing by laying of the hands. | At the time of death, family members may request a minister to anoint, pray or perform religious rites. | All denominations usually favor organ transplant or donation, provided that the donor’s life is not endangered and the recipient will improve or extend his/her life. |\n| Adventists (Seventh Day Adventists) | Abstain from tea and coffee. Many groups prohibit eating of meat. | Many believe that the taking of narcotics violates the body as a temple of the Holy Spirit. May take communion. Some believe in divine healing, anoint with oil and use prayer during illness. | Believe that the dead will sleep until the return of Jesus Christ, at which time final rewards and punishments will be given. | The individual and family have the right to receive or to donate those organs that will restore any of the senses, e.g., eyes, or those that will prolong life profitability, e.g., kidney or heart. |\n| Jehovah’s Witnesses | Do not eat anything to which blood has been added. May eat animal flesh from which blood has been drained. | Absolutely opposed to blood transfusion, although individuals can sometimes be persuade din emergencies. | No last rites; do not recognize sacraments as such. | No definitive statement available on transplantation. Beliefs will have to be discussed and explored on an individual basis at time of death. |\n\n| Religion | Diet | Health Practices | Death Practices | Organ Transplant Beliefs |\n|--------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|\n| Islamic (Muslim/Moslem) | All pork products are forbidden. Daylight fasting is practiced during Ramadan (the 9th month of the Muhammadan year). | Faith healing is not acceptable unless the psychological condition of the patient is deteriorating. Then it is done only for the patient's morale. | Patient should confess and as for forgiveness before death. Family should be present to wash and prepare the body and turn it to face Mecca. Only relatives and friends may touch the body. | Unless required by law, there should be no post mortem and no body parts should be removed for transplant or another reason. |\n| Greek Orthodox (Christian) | Church prescribes avoidance of meat and sometimes dairy products on Wednesdays, Fridays and during Lent. Members who are hospitalized are not required to adhere if fasting interferes with medical treatments or affects patient's medical condition. | Ordained priest or church deacon may be called to administer Holy Communion while patient is hospitalized. Some patients may also request the sacrament of Holy Unction which may be conducted by the priest in the hospital room. | Last rites are the administration of the Sacrament of Holy Communion. | Organ transplants are acceptable from one human to another. However the life of the donor is considered to be of equal importance and should never be compromised. |\n| Black Muslims | Prohibit alcoholic beverages, pork and some foods traditional among American Blacks, including corn bread and collard greens. | Faith healing is not acceptable and should not be practiced during illness. Do not indulge in activities, e.g., sleeping, more than is necessary for health. | Carefully prescribed procedure for washing and shrouding the body and performing funeral rites. | General adherence to Muslim tenets described above. However, individuals and family members may be approached for organ donation at time of death. |\n| Pentecostal (Also known as Apostolic or Holiness) | Some members abstain from alcohol, tobacco and may refuse to eat pork products. | No prohibition of blood transfusions or medical care. Believe in possibility of divine healing through prayer an that all illness is from the devil; doctors assists, but healing is through Jesus. Pray for divine intervention in health matters. | No last rites; anointing with oil may be practiced. May take Holy Communion. | No prohibition against organ transplant/donation. Relatives and/or friend should be approached regarding organ donation at time of death, as appropriate. |\n| Hindu | Many dietary restrictions that conform to individual sect doctrine. Patient should be questioned when admitted. | Some conditions such as loss of a limb represent \"sins\" committed in a previous life. Accept most modern medical practices. Do not believe in artificial insemination because sterility reflects divine will. | Prescribed rites followed at time of death. Priest will pour water into mouth after death; family will wash the body. Bodies are cremated. | No specific prohibition against organ donation or transplant. Family should be approached regarding donation at time of death, as appropriate. |\n\nDefinitions\n\n**Ac¹culturation**\n\nThe process of adopting the social traits and patterns of another culture, generally the dominant culture.\n\n**Assimilation**\n\nThe process of social and cultural adaptation and absorption of a minority group into the dominant culture. The forms of assimilation are as follows:\n\n1. **Acculturation**: involves adapting or borrowing aspects of another culture such as dress or speech.\n\n2. **Identification**: exists when members of an ethnic group share a perception of nationhood, e.g., \"I am an American.\"\n\n3. **Civic**: involves members of an ethnic group who no longer make special claims on the political system based on the special needs of their particular ethnic group. This usually occurs when an ethnic group achieves an important measure of political power.\n\n4. **Marital**: exists when members of two racial or ethnic groups live together as man and wife.\n\n**Beliefs**\n\nThose things that are thought to be true.\n\n**Bicultural**\n\nAdjective describing a person who has adopted the values and lifestyles of two cultures.\n\n**Burning (Poua)**\n\nA form of folk healing practiced among some Asian populations, particularly Mien and Cambodians. It is a treatment of last resort and is used for the treatment of pain and failure to thrive. It appears as vertical rows of asymmetrical, superficial, burns of approximately ¼ inch on the front or back of the body, including the neck. Or, a single burn may be seen in the center of the forehead. The joints will be burned when attempting to treat failure to thrive. The treatment is performed using a type of grass that has been dried, dipped in melted port lard, ignited, then applied to the area of the body requiring treatment. Poua is generally performed by a healer, but may be done by any experienced adult. Parents may not be aware that performing this treatment on children is illegal in the United States.\n\n**Coining/Coin Rubbing (Cao gio)**\n\nA form of folk healing commonly practiced among some Asian populations which involves rubbing the body with a coin. The coin is sometimes heated or oiled. The rubbing produces red welts on the skin, superficial ecchymosis, and nonpainful areas with petechiae. These areas should not be mistaken for signs of abuse or signs of a specific disease process. The coining procedure is usually carried out on the rib area and/or on the front and back of the body. The treatment may also be applied on the tracheal area, along both sides of the spine, and along the inner aspects of the upper arms. The belief is that rubbing the coin against the skin draws illness out of the body of the individual and that the red welts will appear only on those individuals who are ill. Coining is done to treat illnesses such as colds, vomiting, headache, pain and heat exhaustion. The practice is more common among Vietnamese, Chinese,\n\nCopyright: 12/95\nJ.D. Andrews, RN\n\nMien, Cambodians and Laotians. Parents may not be aware that performing this treatment on children is illegal in the United States.\n\n**Cultural Imposition**\n\nThe practice of imposing one's cultural beliefs upon others with the belief that they are best or superior.\n\n**Culture**\n\nThe learned, shared, and transmitted values, beliefs, and practices of a particular group that guide thinking, actions, behaviors, interactions with others, emotional reactions to daily living and one's world view.\n\n**Cupping (Ventouse)**\n\nA form of folk healing commonly practiced among Asians, Latin Americans and some Europeans. It involves heating a glass and placing it on the ill person's body. The vacuum created under the glass causes the skin to rise, leaving red marks on the skin of approximately 2\" in diameter. The marks from cupping will typically be seen along the left and right sides of the chest, abdomen, and back. Or, a single mark may be seen on the forehead. This treatment is generally performed only on adults. Cupping is done in an effort to equalize \"hot\" and \"cold\" body imbalances and to draw out evil spirits that are causing the illness.\n\n**Dominant Culture**\n\nThe culture of the dominant group within a society. It is not necessary that the dominant culture have the majority of the population. In the United States, people of Anglo-European ancestry – white Anglo-Saxon Protestants (WASPs) make up the dominant group. However, they comprise only approximately 1/3 of the population of the United States. The critical difference related to dominant cultures is power – not numbers.\n\n**Ethnic Group**\n\nA group of people who share cultural, racial, linguistic, and social heritage.\n\n**Ethnocentrism**\n\nThe belief that one's own ethnic group, way of life, beliefs, values, etc., are superior to others.\n\n**Evil Eye (mal ojo)**\n\nA belief of some persons from Asia, Central America, the Middle East, Mexico, Africa. The specific and associated practices may vary. However, the general concept is that one puts an evil spirit on a person by looking at the victim, causing the victim to become ill. The motive for placing the evil spirit on another person is generally envy. The concept is based on the idea that there is a limited amount of good things in the world, such as intelligence, beauty, wealth. If one person possesses one of these assets, other persons have less of the asset. Therefore, envy warrants giving the \"evil eye\" to the person who has the asset, to cause illness. Some cultures believe that compliments cause the evil eye and have ways of neutralizing its effects.\n\n**Family of Orientation**\n\nParents, siblings, and the individual\n\n**Family of Procreation**\n\nSpouse, children, and the individual\n\nCopyright: 12/95\nJ.D. Andrews, RN\n\nFolk Medicine\n\nPractices within a cultural or ethnic group aimed at curing illnesses.\n\nGeophagy\n\nThe eating of clay or dirt. Seen more commonly among African Americans, Africans and Arab Americans.\n\nHot and Cold Health Concept\n\nA health concept based on the ancient Greek concept of the four body humors: yellow bile, black bile, phlegm and blood. A balance of these humors equates to health. The treatment of disease is accomplished through restoring the body’s humoral balance through the addition or subtraction of substances that effect each of these humors. Disease conditions, foods, herbs, beverages, and medications are classified as hot or cold depending on their effect, not their physical temperature. Each cultural group defines what it believes to be hot and cold. The concept is found among Asians, Japanese, Blacks, Hispanics, Arabs, Muslim and Caribbean cultures.\n\nKosher Dietary Laws\n\nKosher Dietary Laws are based on humaneness and practical reasons associated with health. The laws forbid eating pork and shellfish, and nonkosher red meat and poultry. Nonkosher meat is considered any meat obtained from an animal that was not killed with a single blow and not by strangulation. More than one blow to kill an animal is considered cruel because of the pain and suffering experience by the animal between the first and final blows. Strangulation of an animal allows time for release of hormones that can be harmful to consumers of the meat. Red meat must come from animals that chew their cud and have cloven hoofs. A fish consumed must be of the type having fins and scales. Meat and dairy products cannot be eaten during the same meal; pots, utensils, plates cannot be used for both. Foods categorized as *parve* may be eaten with milk or meat dishes and include eggs, fruit, vegetables and nuts.\n\nMinority\n\nA group or people who are singled out from others within a society in which they live, because of cultural characteristics, for unequal or different treatment. The members of the group regard themselves as objects of collective discrimination and exclusion form full participation in society life.\n\nPica\n\nThe craving and eating of non-food items such as Argo starch. Seen more commonly among African Americans during pregnancy. It is believed that these non-foods help to build blood or keep an unborn baby’s skin clean.\n\nPinching (Bat gio)\n\nA form of folk healing practiced among some Asian populations, particularly H’mong, Mien, Laotian, Vietnamese and Cambodians. It consists of pinching any area of the body, sometimes followed by pricking the area with a sharp needle. Conditions treated by pinching include localized pain, fever, coughs, poor appetite, dizziness, fainting and blurred vision. It is practiced on children over 10 years of age and on adults. Any adult may perform this treatment.\n\nRace\n\nA group of people related by common descent of heredity who have similar physical characteristics such as skin color, facial form, eye shape, etc.\n\nRacism\n\nThe belief that race determines human capacities and that some races are superior to others.\n\nStereotype\n\nTo label all persons of a cultural, ethnic, or racial group based on the assumption that all persons within that particular group share the same similarities, beliefs, and values.\n\nSubculture\n\nA large group of persons with shared characteristics, who are part of a larger culture that does not share those characteristics. The group's characteristics distinguish them from the larger culture and are thought of as a subgroup of the primary culture.\n\nTime Orientation\n\nHow an individual or group of individuals behave in relation to the ordering of time: past, present and future. Only among the American middle and upper-class population, is time so highly valued. In many cultures, individuals' lives are not ordered by schedules, clocks, watches, etc. **Present-oriented** persons generally do not value strict schedules. They perceive time as flexible. Present activities are generally more important than future or past activities. May be late for scheduled appointments, place little value on preventive health care practices, and resist rigid hospital schedules because the present moment in time is what is imports. **Future-oriented** persons generally \"live by the clock and calendar\". Many of these individuals mold their current behavior based on future goals and plans. **Past-oriented** individuals place great value on traditions and beliefs. They may be very hesitant to consent to new medical treatments.\n\nValues\n\nPersonal standards of what is good or useful in relationship to oneself and to others.\n\nYin/Yang Health Concept\n\nA Chinese concept of health. It is believed that the forces of nature are balanced to produce harmony. The yin force represents the female aspect of nature. It is believed to be the negative pole and encompasses darkness, cold, and emptiness. The yang force represents the male aspect of nature. It is believed to be the positive pole and encompasses fullness, light, and warmth. An imbalance of the yin and yang forces produces illness – and indication of disharmony. Therefore, illness is not thought of as an intrusion, but a natural part of the life cycle. Illness is thought to be inevitable; perfect health is not the goal. Yin and yang are assigned to certain diseases, health conditions, and body organs as indicated below. The inside of the body and the front of the body is yin. The surface of the body and the back of the body is yang. Yin stores the vital strength of life. Yang protects the body from outside forces.\n\n| Health Condition/Disease | Organs |\n|--------------------------|--------|\n| Cancer | Kidney |\n| Lactation | Liver |\n| Menstruation | Lungs |\n| Postpartum period | Spleen |\n| Pregnancy | Heart |\n| Shivering | |\n| Wasting | |\n| Constipation | Bladder|\n| Hangover | Gallbladder |\n| Hypertension | Intestines |\n| Infection | Stomach |\n| Sore Throat | |\n| Toothache | |\n| Upset Stomach | |\n| Venereal Disease | |\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. An educational assessment must include the following: barriers to learning, readiness to learn, preferences of the learner | a. True |\n| | b. False |\n| 2. Healthcare practices vary from one culture and religion to another. | a. True |\n| | b. False |\n| 3. One goal of patient/resident and family education is to encourage patient participation in decisions regarding their care. | a. True |\n| | b. False |\n| 4. Patient/resident education is a patient’s right as well as a professional responsibility. | a. True |\n| | b. False |\n| 5. Educational resources include one-to-one teaching, videotapes, pamphlets and the health education library. | a. True |\n| | b. False |\n\nChapter 10: Quality Assessment/Improvement, Sentinel Events\n\nPurpose\n\nThis module was designed to review the quality assessment/improvement and corporate compliance program.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. Define \"quality assessment and improvement\"\n2. Distinguish between Standard of Care and Standard of Practice\n3. Identify reporting mechanisms and initiate actions\n4. Identify who belongs to the QI team\n5. Employee is aware of HIPAA regulations and requirements\n6. Complete the competency exam.\n\nContinuous Quality Improvement\n\nDefinition\n\nAt KJMC, Continuous quality Improvement is a systematic organization-wide approach for improvement that involves measurement and evaluation of the quality and appropriateness of patient/resident care, the identification of opportunities for improving care and the identification or problems that impact on patient/resident care and clinical performance.\n\nThe Board of Trustees, the Executive Committee of the KJMC and the KJMC Administration are committed to promoting the quality of patient/resident care and assuring that services rendered are achieved by requiring and supporting the establishment and maintenance of this program.\n\nThe Continuous Quality Improvement program will uphold KJMC’s mission of commitment to service to our community by providing high quality, cost-effective and appropriate services, promoting patient satisfaction and improving health and treating diseases in an environment of excellence in a respectful, caring manner within a safe hospital environment.\n\nObjectives\n\n1. To objectively, systematically and continuously measure and improve the quality and appropriateness of patient care and services\n\n2. To assure that care provided is of a high level of quality; to measure performance in terms of efficacy, appropriateness, availability, timeliness, effectiveness and continuity of services as well as safety and efficiency of services\n\n3. To coordinate all performance improvement activities into a well-organized, integrated plan to improve patient/resident care and service\n\n4. To prioritize KJMC’s improvement activities. The structure of the QA/CQI Committee is designed to facilitate the collection, analysis and reporting of data by prioritizing projects based in the following areas:\n\n a. Quality patient care\n b. Physician satisfaction\n c. Patient satisfaction\n d. Employee satisfaction\n e. Environment of care\n\n5. To validate CQI efforts by encouragement rather than discouragement, and\n\n a. Include Measurable outcomes\n b. Define problems in ways that are amenable to solution\n c. Allocate resources for measurement and problem-solving which add value to the organization\n\n6. To provide information regarding findings, conclusions and recommendations top Administration, Executive Committee and the Board of Trustees\n\nApproach and Methodology\n\nEach department, service and team will accomplish the goals and objectives of the organizational performance improvement process by using the PDCA model adopted by KJMC. This model provides a framework for continuous quality improvement (CQI).\n\n- Plan the Improvement\n- Do the improvement to the Process\n- Check the Results\n- Act to hold the gain and continue to improve the process\n\nStandard\n\nThe “standard” is an agreed-upon level of excellence.\n\nStandard of Care\n\nThe “standard of care” addresses the quality of nursing care that patients/residents can expect to receive from the nursing staff and reflects the scope of care provided by each hospital unit. This involves assessment, diagnosis, outcome identification, planning, implementation and evaluation. For example:\n\n1. The patient/resident will be free from infection, phlebitis or inflammation as a result of IV therapy\n2. The patient/resident will correctly demonstrate his or her skill with insulin injection\n\nStandard of Practice\n\nThe Nursing Policies & Procedures located on every unit. For example,\n\n1. The nurse will take vital signs every 15 minutes\n2. The nurse will change the dressing BID\n3. The nurse will assess the patient/resident’s comfort level to determine if he or she is experiencing pain\n\nThe Nursing Department recognizes the vital role it plays in the provision of quality patient care. In order to achieve quality patient/resident care, we also recognize that we must work collaboratively with those services in the organization that also provide patient care.\n\nIndicators\n\nAn integrated standard of care or practice is used to gather data for evaluation of the quality of care. For example:\n\n1. **High-volume indicators** – refers to quantities, for example:\n - Number of admissions\n - Number of falls\n - Number of medication errors\n2. **High-risk indicators** – describes those activities that place the patient at risk, for example:\n - Risk of infection\n\nb. Safety\n\n3. **Problems prone indicators** – any issue that warrants ongoing monitoring due to the potential for clinical impact, for example:\n a. Patient/resident falls\n b. Pressure ulcers\n\n4. **Thresholds** – for evaluation, the threshold is a pre-established level of performance applied to series of patient care activities being monitored, for example:\n a. Medication – 100%\n b. Documentation – 90-95% compliance\n\n**Quality Management/Nursing Quality Initiative Locations**\n\n1. The hospital QM office is located in the Leviton building, 3rd floor, ext. 5789\n\n2. All Nursing Quality Initiative is reported through Elaine Moses, Nursing Office, 2nd floor, ext. 5262\n\n**Nursing Quality Initiative (NQI)**\n\nChairperson: Elaine C. Moses, RN\n\nEvery Patient Care Unit has a NQI representative (and an alternate). They are selected by the Assistant Directors.\n\nThe NQI Committee:\n\n1. Uses the principles of Continuous Quality Improvement (CQI)\n2. Meets monthly\n3. Collects and analyzes data (*e.g.*, medication errors or potential errors and patient outcomes)\n4. Discusses management issues (*e.g.*, glucometer machines, fall rates, restraint issues)\n5. Uses “Plan, Do, Check, Act” as the primary method for achieving and sustaining performance improvement\n\nThe NQI representative will share all pertinent information with the general staff members on her unit, after each committee meeting.\n\nThe NQI Committee revises the Department Quality Improvement Plan on an annual basis. The Plan is approved by the Vice President of Nursing Services.\n\nPatient outcomes are used on a department and unit level. Data is the basis in which we can identify and evaluate performance improvement activities.\n\n**Sentinel Events**\n\nA Sentinel Event is an unexpected occurrence or risk of occurrence involving death or serious physical or psychological injury. This may include:\n\n1. The loss of limb or permanent function\n2. Infant abduction\n3. Infant discharged to the wrong family\n\n4. Rape\n\n5. Hemolytic transfusion reactions\n\n6. Surgery on the wrong patient or wrong body part\n\nEvery Sentinel Event needs to undergo an intensive assessment called “Root Cause Analysis,” identifying the most basic causal factors contributing to the event. By studying the process, it is important to redesign the process so as to minimize the likelihood of recurrence due to the same primary cause in the future.\n\nAny medical inquiries concerning Sentinel Events shall be coordinated by the Department of Quality Management after communicating with the Office of Legal Affairs.\n\nWhenever any member of KJMC’s staff becomes aware of any occurrence which may become a Sentinel Event, that person should immediately contact Risk Management. When the Department is next open, the event must be immediately reported to the Administrator on Call. He or she must notify the Medical Director the next business day.\n\nKJMC will undergo an intensive investigation involving Risk Management, Directors and Quality Improvement Committees for all involved departments. Events requiring multidisciplinary review will be referred to the QI Committee. The process and results of the investigation will involve peer review, as necessary. All Sentinel Events, corresponding Root Cause Analyses and plans of corrective action are reported through the QI Committee to the Executive Committee. Staff involved in policy changes must be in-serviced as necessary.\n\n## Competency Exam: Chapter 10\n\n### Quality Assessment/Improvement\n\n| Question | Select the correct response: |\n|--------------------------------------------------------------------------|-----------------------------|\n| 1. QA/CQI is a method to assure quality care on an ongoing basis. | a. True |\n| | b. False |\n| 2. Indicators can be high volume, high risk and/or problem-prone standard of care or practice. | a. True |\n| | b. False |\n| 3. Interdisciplinary CQI projects are: | a. Another audit by the internal revenue service |\n| | b. A customer-focused, quality-driven philosophy that relies on each member of an organization to build quality into every step of service |\n| | c. A term used to solve problems that concern you only |\n| | d. Another shopping mall scheduled to open in January 2010 |\n| 4. All nursing staff are required to know the quality indicators that are being monitored hospital-wide as well as on their unit. | a. True |\n| | b. False |\n| 5. The primary method for achieving and sustaining performance improvement at KJMC is called: | a. FORK |\n| | b. HELP |\n| | c. PDCA |\n| | d. NBA |\n\nChapter 11: Human Resources Policies/Age-Specific Issues\n\nPurpose\n\nThis module was designed to review KJMC's Human Resources Policies and Procedures and to identify differences of various age groups.\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. State KJMC guidelines on:\n a. Rules of Conduct\n b. Absenteeism and lateness\n c. Sexual harassment\n\n2. State how to address the needs of a 4-6 year old as well as an elderly patient\n\nPOLICY:\nCommon sense, good judgment, and regard for the rights and interests of both Kingsbrook Jewish Medical Center and one's co-workers will ensure the well-being of the patients entrusted to our care. In a hospital, particularly, we expect employees to adhere to high standards of personal conduct at all times.\n\nThe importance of this matter necessitates that Kingsbrook Jewish Medical Center establish rules of conduct for all employees and that Management staff take disciplinary action which may include discharge-against any employee for any act of misconduct, including but not limited to those listed below. (See Discipline Policy)\n\nThe rules of conduct outlined below are issued in coordination with our compliance program and supplement any rules promulgated as part of the compliance program.\n\nA. Rules of Conduct:\n\n1. Falsification of employment records or other Kingsbrook Jewish Medical Center records including time reports.\n\n2. Unauthorized absence from post of duty during regularly scheduled tour of duty.\n\n3. Loitering, loafing, or sleeping while on duty; loitering or returning to the work area or other enclosed areas while off duty.\n\n4. Failure or refusal to follow the instructions of a Supervisor including refusal to accept job assignment.\n\n5. Use of vile, intemperate or abusive language, or acting in a disrespectful manner to any employee, Manager, patient, or visitor.\n\n6. Immoral or illegal conduct.\n\nUse, or unauthorized possession of intoxicating beverages or narcotics on premises, or reporting to work under the influence of intoxicants or narcotics.\n\nRules of Conduct\n\n7. Threatening, intimidating or coercing another employee by word or action.\n\n8. Fighting, horseplay, or other disorderly conduct on Kingsbrook Jewish Medical Center premises.\n\n9. Possession of a weapon on Kingsbrook Jewish Medical Center premises.\n\n10. Gambling, or conducting games of chance, or possession of gambling devices on Kingsbrook Jewish Medical Center premises.\n\n11. Creating or contributing to unsafe or unsanitary conditions by failure to comply with established safety or sanitation practices.\n\n12. Smoking in unauthorized areas.\n\n14. Unauthorized posting or removal of notices in Kingsbrook Jewish Medical Center.\n\n15. Unauthorized possession, use copying, or reading of KJMC or disclosure of information contained in such records to unauthorized persons.\n\n16. Theft, fraud, misappropriation, or unauthorized possession or use of property belonging to KJMC or to any employee, patient, or visitor.\n\n17. Negligent or deliberate destruction or misuse of property belonging to Kingsbrook Jewish Medical Center, another employee, patient or visitor.\n\n18. Excessive and/or unexcused absence or tardiness.\n\n19. Accepting or soliciting tips or gratuities.\n\n20. Disregard of one's appearance, uniforms, dress or personal hygiene.\n\n21. Any willful act or conduct detrimental to patient care or to KJMC operations.\n\nRules of Conduct\n\n22. Violation of any rule or regulation of the Medical Center.\n\n23. Failure to render a personal service to any patient, if such service is within the normal and usual scope of the employee's duties, or is required by reason of an emergency relating to the patient.\n\n24. Inducing another employee to commit any breach of the foregoing rules and regulations.\n\n25. Violation of the any Medical Center policy contained in this or any other manual outlining duties, responsibilities or conduct including the \"No Solicitation and Distribution Policy\" and the \"Nepotism Policy\".\n\nSexual Harassment\n\nPOLICY:\n\nIt is the policy of Kingsbrook Jewish Medical Center, in accordance with applicable law, to provide a workplace free from sexual harassment. Kingsbrook Jewish Medical Center strongly disapproves of offensive or inappropriate sexual behavior at work; thus, all employees must avoid any action or conduct which could be viewed as sexual harassment. Sexual harassment can be divided into two categories:\n\n1. \"Quid pro quo\" - Occurs when a supervisor or other management representative threatens the loss of employment benefits or threatens other unfavorable working conditions for refusing sexual advances, or promises rewards for responding favorably. Employment benefits would include salary, opportunities for promotion, performance evaluations, etc.\n\n2. Hostile Environment - Occurs when inappropriate conduct unreasonably interferes with an employee's job performance or creates an intimidating or offensive working environment. Such conduct can include unwanted physical contact or offensive language, jokes and comments of a sexual nature.\n\nPROCEDURE:\n\nAny employee who complains of sexual harassment at work may use and is encouraged to use the following grievance procedure.*\n\n1. Any employee who believes he or she has been the subject of sexual harassment should report the alleged act immediately to the Human Resources Department.\n\n2. The complaint will be promptly and thoroughly investigated in a professional and confidential manner.\n\nSexual Harassment\n\n3. Depending on the findings of the investigation, appropriate corrective action, including disciplinary measures up to and including discharge, will be taken to remedy all violations of Kingsbrook Jewish Medical Center’s policy against sexual harassment.\n\n4. In the event that either employee does not agree with the findings of the investigation, the employee may request the Administrator or his/her designee (Corporate Officer) to review the decision. The decision of the Vice President shall be final and binding.\n\nThere will be no retaliation against any employee for invoking or participating in the grievance procedure or for making a complaint of sexual harassment.\n\n*If for some reason the employee's more comfortable in reporting the claimed sexual harassment to some other Kingsbrook Jewish Medical Center representative, he/she should do so. Such a complaint will be treated in the same professional and confidential manner as one made in accordance with the procedure outlined below.\n\nAbsenteeism and Lateness\n\nPOLICY:\n\n1. All employees are expected to report to work as scheduled and to work their scheduled hours and required overtime. Employees will be charged with an absence occurrence when they fail to report for their scheduled work hours.\n\n2. All employees are expected to report to work and be ready to begin work at the scheduled start of their shift and will be considered late to work if this does not occur. Employees will be late and charged with a partial absence when they report to work more than seven minutes past their scheduled starting time, and staff nurses will be docked for lateness if they report more than fifteen minutes past the start of their shift. Non-exempt employees will be docked a portion of their pay for each lateness occurrence according to the guidelines listed below.\n\nPROCEDURE\n\n1. Absences due to sickness and/or injury shall be charged as an occurrence, regardless of whether or not sick time is paid. Absences of several days duration will be treated as one occurrence. Absences which will not result in an occurrence charge include those involving jury or military duty and authorized paid leave (excluding sick time). The hospital has the right to require employees to submit a doctor's note to verify a claim of illness and/or injury.\n\n2. Employees must notify their manager in advance when possible, according to departmental guidelines, of their inability to report for work as scheduled. In no event should an employee notify their manager later than 30 minutes after their starting time. Managers will maintain written records of employees' absences and lateness, which will include the reasons given by employees for missing work.\n\n3. Employees who are absent without notifying their supervisor are subject to termination for job abandonment.\n\nAbsenteeism and Lateness\n\n4. Employees who display frequent lateness and/or absence will be subject to progressive discipline in accordance with hospital policy. Supervisors will provide counseling at each step of this progressive procedure, indicating what the next step will be in the event the problem is not corrected.\n\nIn dealing with attendance problems, the hospital will consider the facts and circumstances of each particular case, including the employee’s overall attendance and performance records, reasons for missing work and prospects for future improvement.\n\n5. In addition to the above, non-exempt employees who are late are subject to being docked a portion of their salary as follows:\n\n- 0 - 7 minutes late - No docked pay\n- 8 - 22 minutes late - 15 minutes docked\n- 23 - 37 minutes late - 30 minutes docked\n- 38 - 52 minutes late - 45 minutes docked\n- 53 - 60 minutes late - 60 minutes docked\n\nStaff Nurse:\n\n- 0 - 15 minutes late - No docked pay\n- 16 - 45 minutes late - 30 minutes docked\n- 46 - 75 minutes late - 60 minutes docked\n\n6. Executive, Administrative, and Professional Employees are salaried and therefore, are not to be docked for lateness or early leaves. Attendance records should be maintained for all categories of salaried employees and attendance problems are to be handled by progressive discipline. Exempt classifications of employees who receive a premium for work performed beyond their normally scheduled work week are not to be docked for late arrivals or early leaves consistent with this section.\n\nSubstance Abuse\n\nPOLICY:\n\n1. The unauthorized use, possession, selling or purchasing of illegal drugs, controlled substances or alcohol on the premises or any property of Kingsbrook Jewish Medical Center at any time is strictly prohibited. Reporting to work or working under the influence of alcohol, an illegal drug or controlled substance is strictly prohibited. Violators will be subject to immediate disciplinary action, up to and including termination of employment.\n\n2. Any employee who must use a prescription drug that causes adverse side effects (e.g., drowsiness or impaired reflexes or reaction time) should inform his/her manager that he/she is taking such medication on the advice of a physician. In addition, the employee is responsible for informing his/her manager of the possible effects of the drug on performance and expected duration of use.\n\n3. Kingsbrook Jewish Medical Center is committed to assisting employees with alcohol and substance abuse problems by referral to the appropriate rehabilitation and counseling service.\n\nPROCEDURE:\n\n1. An employee who appears to be impaired will be interviewed by his/her manager in order to determine whether or not an alternate reason exists for the employee's performance. The Human Resources Department is to be notified immediately of the problem.\n\n2. Managers are to notify the Human Resources Department of an employee who has a history of alcohol or substance abuse. The employee will be advised of the Employee Assistance Program and referred to the appropriate rehabilitation and counseling services.\n\n3. If an employee notifies a supervisor of the use of a prescription drug with potential adverse side effects, the supervisor is to notify the Personnel Department who will discuss the matter with the Personnel Health Service physician, if necessary, and advise the supervisor if the employee should be temporarily reassigned, if possible, or temporarily relieved of duty.\n\n4. An employee who appears to be impaired (without a satisfactory explanation) is to be immediately referred to Personnel Health Service (or the Emergency Room after hours) when the manager has \"reasonable evidence\" that the employee may be impaired. It will be the responsibility of the physician to perform a medical evaluation to determine if the employee is impaired and the extent of impairment. No employee will be tested or accused of alcohol or substance abuse at any time by his/her manager.\n\n5. The manager will be notified if the physician determines that the employee is impaired and appropriate action will be taken after consultation with the Human Resources Department. In arriving at the action to be taken, the employee's past work history, length of service, performance reviews, prior disciplinary record and the success or failure of prior rehabilitative attempts will be considered.\n\n6. A leave of absence may be granted to an employee requesting assistance for alcohol or substance abuse for the first time (in accordance with Human Resources Policies or Collective Bargaining Agreements) provided that the employee has not been given notice of termination nor been suspended, subject to termination.\n\n7. Incidents of impairment involving certain licensed employees will be reported to the New State Department of Education, in accordance with applicable laws and regulations.\n\nDrug-Free Workplace\n\nPOLICY:\n\n1. Illegal drugs in the workplace are a danger to us all. They impair safety and health, promote crime, lower productivity and quality and undermine public confidence in the reputation of the Medical Center. Accordingly, all locations of the Kingsbrook Jewish Medical Center are declared to be drug-free workplaces.\n\nAll employees are absolutely prohibited from unlawfully manufacturing, distributing, dispensing, possessing, or using controlled substances in the workplace. The following is a partial list of controlled substances. A complete listing of controlled substances is available in the Personnel Department.\n\n- Narcotics (heroin, morphine, etc.)\n- Cannabis (marijuana, hashish)\n- Stimulants (cocaine, crack, non-prescription diet pills, etc.)\n- Depressants (tranquilizers)\n- Hallucinogens (PCP, LSD, etc.)\n\nAny employee violating the above policy is subject to discipline (up to and including termination for the first offense).\n\n2. Employees have the right to know the dangers of drug abuse in the workplace, the Medical Center's policy about them and what help is available to combat drug abuse problems. The Medical Center will institute an education program for all employees on the dangers of drug abuse in the workplace. To assist employees in overcoming drug abuse problems, the Medical Center may offer the following rehabilitative help:\n\n- Medical benefits for substance abuse treatment to eligible employees;\n- Information about community resources for assessment and treatment;\n- Counseling program;\n- Employee Assistance Program.\n\n3. Any employee convicted of a violation of criminal drug statute in the Medical Center must inform the Human Resources Director of such conviction (including pleas of guilty and nolo contendere) within five days of the conviction occurring. Failure to so inform the Medical Center subjects the employee to disciplinary action, up to and including termination for the first offense. By law, the Medical Center will notify the federal contracting officer (if applicable) within ten (10) days of receiving such notice.\n\n4. The Medical Center reserves the right to offer employees convicted of violating a criminal drug statute in the workplace participation in an approved rehabilitative or drug abuse assistance program as an alternative to discipline. If such a program is offered, and accepted by the employee, then the employee must satisfactorily participate in the program as a condition of continued employment.\n\n5. All applicants for employment will be required to take a pre-employment physical examination. Applicants whose examinations and interviews, combined with general reference and background checks, indicate present drug abuse, will not be hired.\n\nALL EMPLOYEES ARE ASKED TO ACKNOWLEDGE THAT THEY HAVE READ THE ABOVE POLICY AND AGREE TO ABIDE BY IT IN ALL RESPECTS. BY LAW, THIS ACKNOWLEDGEMENT AND AGREEMENT ARE REQUIRED AS A CONDITION OF CONTINUED EMPLOYMENT.\n\nPlease refer any questions regarding this policy to the Human Resources department.\n\nPOLICY:\n\nKingsbrook Jewish Medical Center is committed to the prompt and confidential investigation of suspected defalcation, misappropriations and similar irregularities. Management is responsible for being aware of exposures or symptoms of exposures in their respective areas of responsibility and, for detecting suspected wrongdoing.\n\nPROCEDURE:\n\n1. Defalcations, misappropriations and other irregularities are defined, as follows:\n a. any dishonest or fraudulent act;\n b. forgery or alteration of checks, time sheets, payroll, personnel documents, contracts and other similar type documents;\n c. any misappropriation of funds, securities, supplies or any other assets;\n d. any irregularity in the handling or reporting of money transactions;\n e. disappearance of furniture, fixtures and equipment; and,\n f. any other similar or related irregularity, including an act of bribery, extortion, collusion or embezzlement.\n\n2. An employee who suspects, has knowledge of or has reason to believe that an impropriety has occurred should first notify the Kingsbrook Jewish Medical Center Assistant Vice President of Human Resources and/or the appropriate Vice President. All communication will be kept in strict confidence.\n\nMisappropriation of Funds and Irregularities\n\n3. Based on information received from the employee, the Assistant Vice President of Human Resources and/or the appropriate Vice President to the President will take such action as deemed appropriate.\n\n4. Employees who suspect any misappropriation or wrongdoing should not: (a) contact the individual(s) suspected of impropriety; or (b) discuss the circumstances of the situation unless specifically directed by the individual(s) and/or department(s) responsible for conducting the investigation.\n\n5. In order to avoid damaging the reputations of innocent persons initially suspected of wrongful conduct, and in order to protect the Medical Center from potential civil liability, the results of investigations will not be disclosed or discussed with anyone other than authorized representatives of law enforcement and/or regulatory agencies, and only those persons associated with Kingsbrook Jewish Medical Center who have a legitimate need to know such results in order to perform their duties and responsibilities.\n\nSmoking\n\nPOLICY:\n\nKingbrook Jewish Medical Center is committed to a smoke free environment. As a health care provider it is the responsibility of the Medical Center to promote good health on behalf of our staff, patients and visitors. To the end, most facilities of the Medical Center are completely smoke free.\n\nPROCEDURE:\n\n1. Smoking is prohibited in most enclosed areas of the Medical Center. To ensure ease of ingress and egress, smokers will not be permitted to congregate for the purpose of smoking at entrances and exits to these facilities.\n\n2. The sale of smoking materials is prohibited on Medical Center premises.\n\n3. Discussion of the smoking policy will be included in the new employee orientation program for all employees.\n\nUse of Hospital Property and Services\n\nPOLICY:\n\nEmployees are not allowed to appropriate or borrow hospital property for their personal use without written approval from their immediate Manager and a signed release from the Security Department. In those cases where approval is granted, the employee shall be responsible for ensuring that the property is returned promptly and in good working condition. Replacement or reimbursement for lost or damaged property shall be the responsibility of the employee. An employee who removes any hospital property without the required approvals and forms will be subject to termination of employment.\n\nEmployees are not allowed to prescribe medical treatment or tests for themselves or co-workers. All employees must go to Employee Health Service for authorization to obtain laboratory tests, x-rays, drugs, etc., or present a properly completed private physician's order for lab tests, x-rays or prescription drugs.\n\nPROCEDURE:\n\n1. An employee wishing to remove hospital property from hospital premises shall first obtain written permission from his/her immediate supervisor.\n\n2. The employee shall then obtain a release form from the Security Department prior to removing the property from hospital premises.\n\nWeapons Possession\n\nPOLICY:\n\nIn an effort to provide a safe environment for our employees in which to work, it is the policy of KJMC that the possession of firearms, explosives, or other weapons on company property or knowingly permitting another employee to do so is strictly prohibited.\n\nThis policy applies to all KJMC property and includes the carrying of such devices in vehicles parked on company property.\n\nAlthough New York State may permit citizens to carry weapons, KJMC policy governs the conduct of its employees while at work or on company property.\n\nPROCEDURE:\n\n1. Exemptions to this policy must be submitted, in writing, to the Director of Security who shall review the request and make a recommendation to the Chief Operating Officer who has the authority to approve or deny the request.\n\nStaff Rights Relative to Patient Care\n\nPOLICY:\n\nIt is the policy of the Medical Center to consider requests by employees not to participate in an aspect of patient care when such requests are based on cultural values and/or religious beliefs. However, in no event will a patient’s care be negatively affected as a result of requests of this nature.\n\nPROCEDURE:\n\n1. An employee may request not to participate in an aspect of care (including treatment) where there is a perceived conflict with the employee’s cultural values or religious beliefs.\n\n2. The employee must put the request in writing to his/her Department Head detailing the reasons for the request.\n\n3. The Department Head will review the written request, in collaboration with Administration, Human Resources and other Kingsbrook Jewish Medical Center personnel as appropriate, and render a written decision either approving or disapproving the request.\n\n4. If the request is approved, the delivery of patient care will not be compromised and will be provided by either supervisory or other appropriate staff as determined by the respective Department Head.\n\n5. The following aspects of patient care which could possibly conflict with staff members, cultural values or religious beliefs include:\n - Blood Transfusions\n - Removal of a patient from life support\n - Withholding nutrients from a patient\n\nIn the event that one of the above aspects of patient care arises, the supervisor should anticipate the need and arrange for alternate methods of providing the care without interruption, in accordance with the procedure listed above.\n\nVideotape Content Review\n\nReview the material presented in the videotape by studying the next few pages.\n\nIntroduction\n\nAs healthcare workers we offer our care and our experience to people at all stages of life, from infants to older adults. They are all individuals with their own feelings and abilities, but they grow and develop in similar ways. At each stage in life there are certain qualities and needs that are shared, and by understanding what these are, we can provide better, more appropriate care at each stage. Age specific-competencies address the different needs people have at different ages.\n\nBy incorporating age-specific considerations with each patient, you help identify and provide the care that particular patient needs at that time of life; you help the patient become an active partner in health decisions.\n\nAge-specific competencies have also become a major focus of the Joint Commission on Accreditation of Healthcare Organizations (TJC). Healthcare staff need to be trained on how the age of each patient can impact assessment, delivery of care, and health education needs for the patient. There may be special health considerations to be aware of at each stage of life, and the TJC feels all healthcare staff should understand and apply these age-specific considerations. Being able to apply age-specific care often depends on using age-appropriate communication skills to understand the patient's needs. We will address this issue first.\n\nBarriers to Communication\n\nAt just about any age there may be barriers to communication that you should look for. Give the person your full attention and observe closely. You may not be able to fully do away with any barriers you find, but you can be aware of them and minimize them.\n\nYou should assess the patient's primary language and whether communication might be clearer if you brought in a translator. Check for any speech or hearing impairments, and check whether any confusion or depression might be a sign of physical or mental illness. Find out if the patient is under stress or worried if healthcare decisions might affect their schooling, job or family.\n\nWith children and adults, check if there are any apparent learning disabilities and if the person appears to understand instructions at an age-appropriate level. Be aware of cultural differences and how eye contact and gestures that seem ordinary to you might be misinterpreted. Some people from Asian cultures, for example, are much less comfortable with being touched than those from other cultures. Make an effort to understand the patient's family structure and support system, and try to incorporate family caregivers into treatment suggestions. Clear communication with the patient can be the key to providing age-specific care.\n\nNeonates: Birth to 26 Days\n\nAge-specific care begins at the beginning: with neonates. The first 28 days of life are a time when the neonate's body functions, such as digestion, temperature regulation and sleeping, become established. Neonates can focus on faces, smile in response to a smile and lift their heads. Neonates are in a state of total dependency. The startle or Moro reflex is one of several reflexes neonates are born with to help cope with life outside the womb.\n\nNormal reflexes such as grasping, gagging and startling are key healthcare issues for the neonate. Other important concerns are for good APGAR scores, age-appropriate vital signs (temperature, pulse and respiration), steady weight gain, and in some cases, blood glucose levels.\n\nAge-Specific Care for Neonates\n\nAlways handle the neonate in a gentle, comforting and soothing manner. Avoid over-stimulation. Speak to the neonate in a soft, comforting voice. Help parents learn proper child care skills, including feeding, diapering and bathing. Be sure parents understand a neonate has immature heat regulation and needs to be kept warm.\n\nWith changes in the healthcare system, neonates are going home earlier these days and sometimes with potential healthcare problems that haven't been identified. New parents should be taught about issues of jaundice, breast feeding and nutrition, cord care, fevers and avoid sleeping positions associated with Sudden Infant Death Syndrome.\n\nHelp parents understand the importance of safety devices such as car seats. In most states, they are required by law. The current standard is to use a child seat in the back seat of the car and fasten it in place with both the lap and shoulder belt.\n\nInfants/Toddlers: 0-3 Years\n\nInfants and toddlers are in a period of rapid growth and learning. They explore the world through direct sensory contact; by tasting, touching, looking, listening and smelling. And they progress in their efforts to communicate, moving from crying, through babbling to using simple words. They are very dependent, but are beginning to develop a separate self.\n\nKey emotional and health and safety issues at this age are to foster good child-parent bonds, keep immunizations and checkups on schedule, and help parents ensure a safe environment for playing and sleep.\n\nAge-Specific Care for Infants\n\nWhen infants and toddlers are brought in, ask the parents how feeding is progressing, ask if the infant seems to be developing motor skills normally, and if they have noticed any hearing or vision problems. Remind the parents that children develop at different speeds and if the infant seems slow to crawl or walk, remind them it may be perfectly normal.\n\nLook for and ask the parents about any signs of colds or flu and remind the parents that these conditions are very common, especially among children who attend daycare. Handwashing as a way to prevent disease transmission should be emphasized to children, and parents should be aware of its importance for themselves and anyone providing care.\n\nCheck the toddler's teeth and help the parents understand the essentials of basic tooth care, even for one or two teeth. You will probably see the infant or toddler before any dentist does.\n\nEncourage the child to communicate, and encourage hugging, cuddling and touch by staff and parents. All this will promote health bonds and good parenting. Be aware of the problem of \"stranger anxiety\" and try to limit the number of staff workers assigned to each infant. Always speak to the infant before a touch to avoid startling the infant.\n\nKeep a safe environment, as well as helping parents learn how to care for the child safely at home.\n\nThere are many safety tips such as supporting an infant's head that may not be obvious to all parents, especially new parents.\n\nYoung Children: 4-6 Years\n\nNext we will discuss some of the common characteristics of young children from about ages 4 to 6. This is a period where growth slows a little but motor skills increase, and children learn many new skills including things like dressing and toilet-training.\n\nTheir minds begin to use symbols and they play with imagination and fears and stores. They identify with their parents but grow more independent, and begin to become sensitive to others' feelings.\n\nKey emotional and health and safety issues at this age are for praise and clear rules to provide a secure set of boundaries, to keep immunizations and checkups on schedule, and learn healthy habits for nutrition and grooming. In addition parents may need help teaching about safety equipment, such as\n\nbike helmets and elbow and knee pads for skateboarding. Match safety and pool safety can also be issues.\n\n**Age-Specific Care for Young Children**\n\nThe healthcare worker should work to involve both parents and children in healthcare choices. Always explain what you are going to do in a firm and direct way before you start. Don’t lie to the child about whether something will hurt, but reassure them that it won’t hurt for long.\n\nInjury and disease can be very upsetting to children. Children at this age ten to weave fantasies, so a minor would may suggest that the whole limb is about to fall off. Explain healthcare issues clearly and reassure the child. Explain grooming and hygiene issues and point out to the parents that it’s not just to look good, but an important infection control technique. And try to allow the child to make some reasonable choices, too. This will foster a growing sense of independence. It is important to incorporate the child’s home routines as much as possible.\n\nUse toys and games to help teach the child and reduce fear of health issues. Use talking, singing, and distractions like colorful stickers to divert attention from frightening procedures. Encourage the child to ask questions, talk about feelings, and play with other children to encourage both growing independence and social skills.\n\n**Older Children: 7-12 Years**\n\nNow we will discuss some of the common characteristics of older children from about ages 7 to 12. This is a period where growth continues slowly until there is a spurt at puberty. Children this age became mentally active, eager learners and love to share their knowledge. They learn about cause-and-effect, and they perfect their reading and writing and learn math skills.\n\nWhile they are developing a greater sense of self, there is also a great need to fit in with their peers. School activities become very important and they may start negotiation with their parents for greater independence.\n\n*Key emotional and health and safety issues* at this age are to learn to feel competent and useful, to continue immunizations and check-ups, and to begin to learn honest information about alcohol, drugs and sexuality. It is also time to begin learning playground safety habits and how to resolve conflicts peacefully.\n\n**Age-Specific Care for Older Children**\n\nAt this age vital signs approach the norms of adult parameters. Some questions may arise about the development of secondary sexual characteristics and should be dealt with honestly. The healthcare worker should explain procedures in straightforward terms, using correct terminology, and invite the child to make some healthcare choices. If equipment is needed, allow the child to explore the equipment ahead of time. You should allow longer training and teaching sessions. Provide privacy if necessary, and build into your teaching rewards and praise.\n\nDo your best to guide the child toward healthy lifestyle and safety choices. Habits formed at this age may last a lifetime. It’s not too soon to begin to discuss exercise and nutrition and maintaining a healthy lifestyle. And help the parents talk to the child about crucial issues of peer pressure around smoking, sexuality and all kinds of substance abuse. It can be very hard for parents to know how to initiate these discussions and an outside authority such as a healthcare worker can be a big help in getting the ball rolling.\n\n**Adolescents: 13-20 Years**\n\nNow we will discuss some of the common characteristics of adolescents from about ages 13 to 20. This is a period where growth spurts upward and the body transforms into an adult, sexually mature body, and physical appearance becomes increasingly important.\n\nAt this age adolescents are able to entertain complex moral thinking, and they begin to make up their own minds and choose their own values. Adolescents need to balance developing their own identity with the need for very close relationships. Peer groups can come into conflict with family demands, and it can become a time of challenging authority.\n\nKey emotional and health and safety issues at adolescence are for privacy and respect, and to find ways to foster teamwork. Checkups should continue and adolescents must learn about sexual responsibility, and ways to resist vastly increased temptations to substance abuse. Risk-taking, particularly in driving and risky sports needs to be addressed, and adolescents should be helped to learn ways to peacefully handle violent situations.\n\nAge-Specific Care for Adolescents\n\nAt adolescence, you should begin looking for signs of common adolescent health problems such as nutritional disorders, obesity, anorexia, bulimia, acne problems, STDs, substance abuse, pregnancy and any stress-related problems. This is a stress-filled age. Reassure adolescents about the normality of the changes they are going through. When working with adolescents, remember their self-consciousness about their bodies and provide for privacy.\n\nThe healthcare worker should begin treating the adolescent as an adult and avoid authoritarian approaches. Talk directly to the adolescent, not through the parents. Always explain why something is being done. Be considerate of how any treatment may affect the adolescent’s appearance and relationships, because these are very sensitive issues at this stage. Encourage questions about their fears. And respect any expressed or implied religious or cultural beliefs.\n\nAdolescents with family histories of genetic-related diseases, such as cardiovascular disease, diabetes, or sickle cell trait, should be screened as appropriate. Adolescent girls should be taught breast self-examination. And boys should be taught testicular self-examination. Peak age for testicular cancer is 20-35.\n\nGuide the teen-age toward positive lifestyle choices, and pay particular attention to misinformation that is common at this age and help correct it. Realize that there may be some resistance to taking advice from an adult. Encourage the teen and parents and peers to have open communication on any issues of concern. As an outside authority, you can often play a powerful role in opening up channels of communication.\n\nYoung Adults: 21-39 Years\n\nNow we will discuss some of the common characteristics of young adults from about ages 21 to 39. This is an age when young people finally reach physical and sexual maturity, and nutritional needs shift away from growth toward maintenance of a healthy body.\n\nYoung adults are still acquiring the new skills that will help them at home and at work. They are seeking closeness and partnership. And they are making decisions that may last all their lives on careers, communities and starting a family.\n\nKey emotional and health and safety issues for young adults are for support and honesty and respect for their personal values. They need to have regular health checkups and updated immunizations. They should be encouraged to pursue healthy lifestyles, including good nutrition, exercise and weight control. There is a need to begin to be aware of long term health-risks for issues like attention to safety hazards at home and at work.\n\nAge-Specific Care for Young Adults\n\nYoung adults need to be monitored for STDs. Testicular and breast self-exam should be taught and encouraged. Discuss questions of stress in their lives as this can be a time of great changes, marriage, beginning families, starting new jobs.\n\nThe healthcare worker should encourage young adults in making positive fitness and health care choices. Help the young adults recognize the new reality of their time and financial commitments to family, career and community. Explore the impact of hospitalization or illness on the patient’s job or family. This is a time when most couples become parents and they need help considering the long-term commitments and challenges this brings. They may also need help with family planning and prenatal information.\n\nExplain the specifics of a healthy physical workout, including warm-up and stretching exercises, and if necessary explain proper nutrition and diet to encourage a healthy lifestyle. Explain risk factors and signs to watch for chronic conditions such as heart disease because young adults often feel invulnerable and tend to ignore or deny early signs of disease.\n\nMiddle Adults: 40-64 Years\n\nNow we will discuss some of the common characteristics of middle adults from about ages 40 to 64. Adults of this age have had tremendous life experiences and continue to use them to learn and create and solve problems. They often reach a point where priorities are reevaluated and new decisions are made about their lives to stay productive and avoid feelings of being stuck in a rut in life. Many start to think of retirement and start to plan for it. Some may begin to develop chronic health problems and women experience the life changes of menopause.\n\nKey emotional and health and safety issues for middle adults are to focus on strengths and keep a hopeful attitude. Checkups and preventive exams must continue to address age-related issues and monitor any risks, and immunizations should be updated. Women, for example, should be encouraged to continue having breast exams even after menopause. Some middle adults need to be made aware of age-related changes in their senses, such as reduced visual and auditory acuteness and slower reflexes and how this may affect activities such as driving.\n\nAge-Specific Care for Middle Adults\n\nMiddle adults should be screened for chronic conditions that often develop at this age, such as diabetes, prostate disorders and breast cancer. Women should be counseled about menopause issues, such as taking estrogen or methods of minimizing the risks of osteoporosis.\n\nThe healthcare worker should encourage middle adults to express freely any worries about the future, and encourage them to plan for a healthy and active retirement. Be sure to acknowledge their abilities and contributions throughout life. This can be a time of mid-life crisis when some people begin to doubt themselves and their contributions and they need encouragement. Some may need specific psychiatric interventions so be alert for signs of depression or other mental illness.\n\nBe alert for any worries they have about their children or older parents. This is an age where many become the “sandwich generation”, caring for both older and younger family members at the same time. This can also be a positive stage of life, with more time available to fulfill lifelong dreams of travel and leisure, and to pursue new interests or volunteer work that had been put off.\n\nOlder Adults: 65-79 Years\n\nNow we will discuss some of the common characteristics of older adults from about ages 65 to 79. An older adult continues to be an active learner and thinker and can now pass on skills and wisdom to other generations.\n\nThere is some decline in physical abilities and senses that needs attention. Often new roles will be taken on, such as grandparent or the return to single life after the death of a husband or wife. There is a tendency now to review one’s life, and to find new balances between independence and dependence.\n\nKey emotional and health and safety issues for older adults are to remain respected and prevent isolation. Aspects of aging need to be accepted and extra effort made to remain active. Nutritional needs are changing and there are still needs for regular checkups, breast and prostate exams, and immunizations, particularly against influenza which can be much more serious at later ages. It’s important to promote physical, mental and social activities and guard against depression. Home safety needs attention, especially guarding against falls, and changes in skills may make driving risks much greater.\n\nAge-Specific Care for Older Adults\n\nStay alert for signs and components of the more common chronic conditions at this age, such as arthritis, hypertension, hearing impairment, and heart disease, and conduct regular screening for these conditions. Also be alert for digestive and esophageal problems such as reflux, and bladder and bowel problems, which become more common at this age. The healthcare worker should encourage the older adults to express freely their feelings about their accomplishments in life, but also their feelings of loss and grief. As they age, they will lose friends and family and grief counseling can be very important.\n\nOften medication use, with multiple medications, can become quite complicated, and it is important to help an older adult work out a manageable schedule. Explain any procedure using appropriate terms. Provide for warmth if necessary because of the possibility of decreased heat regulation. Be alert for the development of any impairments that may inhibit mobility or activities of daily living.\n\nAnd also point out ways to make the environment safer, such as removing slick throw rugs. You should also suggest practical ways of dealing with any impairments that exist, but do not assume impairments exist just because of age. Offer contacts to support services. To keep an older adult busy and engaged, you can encourage social activities with peers or volunteer activity to give something back to the community. The sense of giving back and staying active can make all the difference in a person's outlook at this age.\n\n**Adults 80 and Older**\n\nLast we will discuss some of the common characteristics of adults 80 or older. There is no reason to think a person this age is in mental decline. Some great writers and artists continued to create until well past this age. While you should be alert for signs of confusion, they may just signal an illness or depression that might be treatable. Many people this age begin to accept that the end of life is approaching and begin to prepare for it.\n\n*Key emotional and health and safety issues* for adults over 80 are to encourage expression of feelings and thoughts, encourage humor and stay positive to help prevent depression. Health should be monitored closely, and proper nutrition, exercise, and healthy rest and avoidance of stress should all be encouraged. Immunizations should be updated, particularly against influenza which can be more serious, even life-threatening, for older adults. The environment should be monitored to prevent any hazards, particularly falls which can be devastating at this age. Safety grips, ramps and similar aids may become crucial at this age, either at home or in a nursing home.\n\n**Age-Specific Are for Adults 80 and Over**\n\nThere is an increased risk of chronic illnesses and major health problems that need to be watched. The healthcare worker should encourage as much independent living in older adults as possible. Physical, mental and social activities should be encouraged. An active mind and a sense of humor can often support a person's spirits.\n\nMedications for those over 80 can become even more complicated and may require you to work out very detailed plans. You may need to include helps like color-coding and timed reminders to help the person follow the schedule. Encourage healthy eating and adequate fluid intake. Be alert to the fact that changes in tastes or ability to chew may result in decreased intake. You may need to monitor bowel function daily. It is important to avoid treating an older adult like a child. Almost anyone will sense and resent being patronized.\n\nSupport any end-of-life decisions, offering access to appropriate information such as advance directives, and encourage the preparation of trusts and living wills. Offer any assistive devices that can keep the person adept at his own activities of daily living, and make sure he has access to all necessary safety ramps and other equipment. The more independence the person can maintain, the better the quality of life.\n\n**Conclusion**\n\nPeople grow and learn and change all their lives. Each person is an individual with his or her own special needs and feelings, and thoughts and dislikes. But we all share the human condition, too, and there is so much that we share with one another at every step of the journey.\n\nThis program has been a guideline for the age-specific competencies that will help you work with patients at all stages of their life. It will help you learn what you can offer them at just that moment in their journey when they need it most.\n\n**Needs of the Elderly**\n\nAs people age, the body goes through both physiological and biological changes. This process although a natural one, is often described as a series of losses and thought of in a negative light. Society regards aging as a series of negative events that we must tolerate. Also we often talk about aging and disease in the same breath. Our culture is very youth-oriented and we perceive older adults as senile, sick and unable to be independent and autonomous.\n\nOld age has been divided into three categories:\n\n1. Young old – ages 65-74\n2. Middle old – ages 75-84\n3. Old old – ages 85 and older\n\nThe fastest growing segment of the older population is over age 75. Those who require help are called the frail elderly. Of older adults aged 75-84, only about 25% need help with daily activities. Of those aged 85 and older, nearly one-half need help with daily activities.\n\nThe frail elderly have some of the following characteristics:\n\n1. Poor mental and physical health\n2. Low socio-economic status\n3. Predominantly female\n4. Possibly isolated living conditions\n5. More and longer hospital stays\n6. More money spent on drugs and healthcare\n7. More visits to the doctor\n8. More use of nursing home beds than hospital beds\n\nThere are gradual changes in body function that happen in the aging process:\n\n**Nutritional/G/I System**\n\n1. Reduced calorie needs\n2. Diminished activity and lowered energy requirements\n3. Decreased renal function, susceptibility to dehydration\n4. Diminished enzyme activity and gastric secretions\n5. Diminished absorption of calcium and vitamins\n6. Decreased salivary flow\n7. Diminished sense of taste\n8. Decreased appetite\n9. Diminished intestinal mobility that can cause constipation\n10. Brittle teeth\n11. Decreased biting force\n12. Diminished gag reflex\n13. Decreased anal sphincter tone\n\n**Skin, Hair, Nails**\n\n1. Decreased collagen and elastin (wrinkles)\n2. Decreased healing time\n3. Dry mucous membranes\n4. Diminished sweat gland output, making body temperature more difficult to control\n\n5. Thinning hair (facial hair may increase)\n6. Brittle nails, discoloration of nails\n7. Dry, harsh skin\n\n**Eyes and Vision**\n1. Loss of visual acuity\n2. Loose eyelids\n3. Decrease in tears\n4. Smaller pupil decreases the amount of light that reaches the retina\n5. Thickness of the sclera\n6. Impaired color vision\n7. Predisposition to glaucoma and cataracts\n\n**Ears and Hearing**\n1. Hearing loss (mostly in the high-pitch range)\n\n**Respiratory System**\n1. Tracheal deviations\n2. Decreased pulmonary function and lung capacity\n3. Degeneration of lung tissue\n4. Decreased elasticity of lungs\n5. Reduction in pulmonary fluids increases risk of infection\n\n**Cardiovascular System**\n1. Change in size of heart\n2. Reduced cardiac output\n3. Thickened heart valves and ventricular wall\n4. Arrhythmias and bradycardias\n5. Dilation of veins, decreased coronary artery blood flow\n6. Decreased ability of the heart to respond to stress and exercise\n\n**Renal System**\n1. Impaired clearance of drugs\n2. Reduced bladder size\n3. Decreased renal blood flow\n4. Weakened bladder muscles\n5. Urinary frequency\n6. Fluctuations in sodium levels\n7. Increase in BUN levels\n\nReproductive System\n\n1. Organ atrophy\n2. Declining hormone levels\n3. Emotional changes\n\nNeurological System\n\n1. Degenerative changes to neurons\n2. Slowed down nerve transmission causing sluggish reactions to stimuli\n3. Decreased brain cells\n4. Less effective body temperature regulation\n5. Pain threshold increases\n6. Decrease in stage III and IV sleep\n7. Frequent awakenings\n\nMusculoskeletal System\n\n1. Diminished body mass, bone mineral contents\n2. Decreasing height due to spinal curvatures and narrowing of intervertebral spaces\n3. Decreased bone mass and muscle mass\n4. Thickening of synovial fluid in joints\n5. Poor balance and gait\n\nImmune System\n\n1. Decreased antibody response\n2. More susceptible to infection\n\nEndocrine System\n\n1. Decreased ability to tolerate stress\n2. Diminished glucose tolerance\n3. Hormonal changes\n\nPsychological Transitions\n\n1. Role changes\n2. Retirement\n3. Multiple losses\n4. Loneliness\n5. Depression and suicide\n6. Fear of death\n\n## Competency Exam: Chapter 11\n\n### Human Resources Policies/Age-Specific Issues\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. A KJMC employee can refuse to accept a job assignment if he or she thinks she is working too hard. | a. True \nb. False |\n| 2. A KJMC employee is prohibited from manufacturing, distributing, dispensing, possessing or using controlled substances in the workplace. | a. True \nb. False |\n| 3. You can take all of the following steps to ensure your compliance with the Equal Opportunity Guidelines prohibiting sexual harassment on the job EXCEPT: | a. Avoid unwelcome jokes in the workplace \nb. Treat your coworkers with respect and dignity at all times \nc. Be conscious of verbal and physical contact at all times. \nd. Ignore sexual harassment advances |\n| 4. Always over-stimulate and speak to the neonate with a loud voice | a. True \nb. False |\n| 5. Signs of cold or flu are very common in infants/toddlers | a. True \nb. False |\n| 6. You should be firm, direct and explain what you are doing when caring for children 4-6 years old. | a. True \nb. False |\n| 7. Peer pressure and development of secondary sexual characteristics are important aspects for discussion for children 7-12 years old. | a. True \nb. False |\n| 8. When taking care of adolescents, the healthcare worker should use authoritarian approaches and talk to the adolescent’s parent directly. | a. True \nb. False |\n| 9. It is very important for middle adults to suppress all worries about the future. | a. True \nb. False |\n| 10. Although there is some decline in physical abilities, older adults are active learners and thinkers. | a. True \nb. False |\n| 11. All persons 80 and older are in mental decline. Physical, mental and social activities should not be encouraged. | a. True \nb. False |\n\nChapter 12: Cultural Competence & Awareness\n\nPurpose\n\nThis module was designed for healthcare professionals to understand diversity in the workplace and the methods for providing appropriate culturally-sensitive care.\n\n*This chapter expands on cultural items discussed in chapter 9*\n\nObjectives\n\nAt the completion of this module, the learner will be able to:\n\n1. Differentiate between cultural diversity and cultural competence.\n2. Understand cultural competency and awareness at KJMC.\n3. Define terms related to culturally appropriate healthcare.\n4. Realize the impact of globalization on healthcare & in the workplace.\n5. Consider their personal cultural orientation.\n6. Identify ways in which culture impacts patient care.\n7. Consider impacts of culture on effective communication.\n8. Learn how to manage cultural variances.\n9. Measure their cultural competency and awareness.\n10. Review considerations for building culturally competent skills.\n\nIntroduction:\n\nQuality care for patients from other cultures requires that healthcare professionals become culturally competent. Although specific knowledge of each culture is an unrealistic goal for healthcare providers, being culturally competent involves knowledge of certain basic assumptions, expectations and appropriate behaviors associated with each culture.\n\nDefinitions:\n\nEthnicity\n\nBelonging to, or distinctive of a particular racial, national, cultural or language division of mankind.\n\nCulture\n\nA “common values, beliefs, traits, traditions and/or language that are learned and shared by members of a group.” It is a predominant force that shapes behavior, values and institutions. Culture colors the internal lenses through which people view the world and how they relate to it. As a result, culture and language have a significant effect on how patients access and respond to healthcare services.\n\nCultural competence\n\nAn experiential understanding and acceptance of the beliefs, values and ethics of others as well as the demonstrated skills necessary to work with and serve diverse individuals and groups. Becoming culturally competent is a developmental process that is born of a commitment to provide quality services to all. This involves self-awareness, awareness and respect for the beliefs, values and ethics of other cultures as well as the skills necessary for delivering services and working with diverse individuals and groups.\n\nDiversity\n\nDiversity includes distinctions such as culture, race, religion, ethnicity, gender, language and any observed differences that are common to a group of individuals. Diversity is also reflected in the cultures that are involved in a clinical encounter.\n\nGeneralizations/Stereotypes\n\nStereotypes and generalizations are both words that involve the act of making extensive assumptions or arriving at broad conclusions from particular instances or facts. The difference is that in stereotyping, one accepts common beliefs regarding a group and makes Culturally Competent Care no attempt to learn more about an individual. Stereotyping is then an ending point. Generalization, however, indicates common trends that provide a starting point for learning about another culture.\n\nValues\n\nValues can be characterized as “the most distinctive property or defining characteristic of an individual. Values are things we hold as important. They have also been described as needs, personality types, motivations, goals, utilities, attitudes, and interests.”\n\nWhat is Cultural Competency?\n\nCultural Competency at KJMC results in:\n\n- Staff who deliver service excellence\n- Satisfied and informed customers and patients\n- Customers and patients more likely to follow care instructions because they know that someone understands them and cares about them\n- A success marker of KJMC\n- KJMC becoming *THE* organization of customer choice\n- Reduction in health disparities due to enhanced customer/provider rapport\n- Improved customer/patient health literacy\n\nThe Importance of Cultural Competence\n\nAdvances in technology and travel as well as immigration policies within the United States have contributed to the presence of a wide variety of cultures and ethnic groups in America. As a result, healthcare providers are faced with the challenging task of providing quality care for a very multicultural group of patients with diverse needs and expectations.\n\nPopulation in the US\n\nThirty-six percent of the American population is non-Caucasians of various races or ethnic origins (US Census Bureau, 2010). The two largest segments of this non-white population are the Hispanic/Latino and African American/Black. It is estimated that there will be an increase from 268 million (1995) to 394 million nonwhite people living in the US in 2050. Approximately 90% of this increase will be a combination of Asian Americans, African Americans, and Hispanic Americans (US Census Bureau, 2000).\n\nPopulation in the Brooklyn\n\nAccording to the 2010 Census, 35.7% of the population was non-Hispanic White, 31.9% non-Hispanic Black or African American, 10.4% non-Hispanic Asian, 0.4% from some other race (non-Hispanic) and 1.6% of two or more races (non-Hispanic). 19.8% of Brooklyn’s population was of Hispanic, Latino, or Spanish origin (they may be of any race).\n\nThe primary service area for Kingsbrook was consolidated to reflect our most immediate communities and those areas that utilize our facility at a higher rate.\n\n| Area Code | Age Group | Percentage |\n|-----------|-----------|------------|\n| 11203 | 0-17 | 26.9% |\n| | 18-24 | 62.2% |\n| | 25-44 | 31% |\n| | 45-64 | 19% |\n| | 65+ | 9% |\n\n**RACE DEMOGRAPHICS**\n\n- Black Non-Hispanic: 76.6%\n- Hispanic: 10.0%\n- White Non-Hispanic: 7.8%\n- Asian Non-Hispanic: 1.9%\n- All Others: 3.7%\n\n**ECONOMIC PROFILE**\n\n- Over 100K: 12.7%\n- 75-100K: 9.9%\n- 50-75K: 17.0%\n- 25-50K: 23.8%\n- 25K: 34.1%\n\nHealth Disparities\n\nTremendous economic, social, and political factors prevent many new immigrants from assimilating into the American mainstream as former generations did. As a result, culture and language often become overwhelming barriers in education, politics and particularly in healthcare. Public healthcare policies and education are focusing on finding ways to lower those barriers because there has been consistent research showing the negative impact of ethnicity on clinical outcomes.\n\nRecognizing that culture and language are vital factors in how healthcare services are delivered and received, the Agency for Healthcare Research and Quality (AHRQ) points to the importance of addressing language barriers and improving the cultural proficiency of the healthcare system to eliminate racial and ethnic disparities in health.\n\nRegulatory Requirements\n\nLaws that dictate the provision of culturally competent care have been enacted by the government. Major regulatory agencies have also established mandates regarding culturally competent care for the healthcare industry.\n\nThe Culturally and Linguistically Appropriate Services Standards (CLAS) in healthcare guidelines issued by the Office of Minority Health of the Department of Human Services (Federal Register, Dec. 22, 2000) strongly promotes:\n\na. Cultural competence through language assistance services at no cost to ensure meaningful and timely access.\n\nb. Workforce diversity to match the populations in the service areas and training for all providers on how to work effectively with these diverse populations.\n\nMedicaid/Medicare, The Joint Commission (TJC), and ADA support standards that requires cultural and linguistic competence to provide effective communication for each patient served, education materials, and referral processes that take into account culture and language.\n\nIn compliance with CLAS, many healthcare institutions are beginning to develop internal programs that support provision of culturally sensitive and appropriate patient care to meet the needs of the community.\n\nComponents of Cultural Competence\n\nCultural Competence includes three major areas: Awareness, Knowledge and Skill.\n\nAwareness\n\nAwareness starts with self-reflection that includes the ability to learn about one’s own view of things, identify one’s background and perceive reasons for acting in a particular manner. It is imperative that each person defines his/her own frame of reference before attempting to relate to those of colleagues and patients/families.\n\nKnowledge\n\nKnowledge is the first step in guaranteeing improvement in patient care. In the absence of correct information about patients’ backgrounds, it is less likely that the provider’s jobs will be adequately performed from the customer’s perspective. Healthcare providers must have a basic understanding regarding the main cultural and ethnic groups within their service area and how these groups view and relate to healthcare providers. Acquiring knowledge of the groups’ dietary preferences, religious-based prohibitions and family dynamics, especially in relation to the decision making process, should be an initial step toward providing culturally sensitive care.\n\nSkill\n\nSkill involves not only sensitivity but also effectiveness in accommodating differences in others. One very important skill that healthcare workers need to master is that of communication—since a significant portion of the U.S. population’s native language is non-English. Kingsbrook Jewish Medical Center provides interpreter services to its patients and their families whose native language is not English. The medical center ensures that qualified on-site interpreters are competency via the Interpreter’s Manual and Code of Conduct, August 2012.\n\nThe Iceberg Theory of Culture\n\nThere are several models of culture represented as an iceberg. The iceberg depicts the areas of culture that we can see manifest in the physical sense such as \"visible\" elements that include things such as music, dress, dance, architecture, language, food, gestures, greetings, behaviors, etc. They are shown as cultural characteristics above the water line - the tip of the iceberg.\n\n\"Hidden culture\"; the habits, assumptions, understandings, values, judgments... that we know but do not or cannot articulate, are depicted as hidden on the bottom side of the iceberg, the invisible side. When thinking about culture, the bottom of the iceberg will include things such as religious beliefs, worldviews, rules of relationships, and approaches to the family, motivations - things which cannot be seen.\n\nCommunicating Effectively\n\nLanguage barriers and miscommunication are often cited as barriers to healthcare. Not surprisingly, it has been found that a major contributing factor in healthcare litigation comes as a result of communication problems. Two aspects of communication are speech (Verbal) and body language (non-verbal). Both of which are equally important when engaged in face to face contact.\n\nVerbal\n\nWhen faced with others with limited English, for instance, the skillful healthcare provider may speak slowly in simple sentence structures and providers who speak other languages may need to make a special effort to clearly and carefully enunciate words when addressing those who may not be familiar with certain foreign accents.\n\nIt is the law for healthcare providers to have trained interpreters available for persons with limited understanding of English. Compliance requires taking every reasonable step to provide services and information in the appropriate languages persons with limited understanding of English so that they are well informed and able to participate in their care.\n\nNon-verbal\n\nNonverbal communication, such as eye contact or lack of it, gestures, tone and volume of voice, touch, humor, or social distance from another person when speaking to him or her are equally important. It is crucial for healthcare providers to pay attention to nonverbal cues and to understand their importance, thus preventing unintended miscommunication of information to patients and other members of the healthcare team.\n\nOther Considerations for Providing Culturally Competent Care\n\nProviding culturally competent care is possible. Cultural competence implies more than awareness and sensitivity by the healthcare provider. Being culturally competent ranges from simply assisting patients to find their way around the facility to adequate communication so that patients give meaningful consent to services provided and that discharge instructions are clearly explained and understood.\n\nPain Experience\n\nA good understanding diverse cultural perspective on pain requires sensitivity, cultural awareness, knowledge and respect. Regardless of culture, one must be aware that pain is subjective. Assessment and evaluation of pain begins with the initial assessment/contact of the patient. When creating a pain management plan of care, it should ideally include the patient’s own language, cultural beliefs, and attitudes. Patients must be questioned in depth, and be given a scale to use to describe their pain.\n\nFamily Dynamics\n\nAn individual may be familiar with the way his own family “does things” but may fail to recognize that other families, especially those of other cultures, do things very differently. It is important for healthcare providers to recognize and honor how each family functions according to its culture.\n\nFood & Nutrition\n\nA person’s culture or religion may affect the types of food that are unacceptable or preferred during illness. In some cultures, the temperature of the food is important. Hot foods are regarded as helpful for some conditions and cold foods helpful for others.\n\nSome persons of the Jewish faith eat only kosher foods, which require special preparation, preclude mixing certain foods together, and prohibit consumption of specific foods such as pork. Therefore, if a healthcare provider discovers that a Jewish patient was given pork chops in error, the entire meal must be removed. Merely removing the pork chops from the plate and replacing it with beef would be unacceptable to this patient.\n\nIn all cases, healthcare providers must ask patients if they have any special dietary needs and convey these needs to the Food and Nutrition/Dietary Department of the institution. Patients will then more likely be served meals that are in accordance with their prescribed dietary order and also appropriate to their culture and religion.\n\nDeath and Dying\n\nAn individual’s cultural, spiritual and/or religious beliefs can affect how he or she approaches death and the grieving process. Individuals who feel that their state of mind at the time of death is important to their spiritual wellbeing after death may approach death in a particular way. Others who believe that death is part of God’s plan, or that death may be the result of “punishment” for wrong doing, may respond in a different way during their final days. Individuals from a\n\nculture that believes that death in a specific situation is not natural may see their impending death in another light and respond in yet a different manner.\n\nFor many cultures, there are specific rituals or practices that are important when death is near or has occurred. Some of these may be related to a particular religion or to spiritual practices of the family. For instance, some Jewish families believe that the dying person should not be left alone. A person of the opposite sex must not touch the body of a deceased person of the Orthodox sect of Judaism. The family may require that someone of their faith stay with the body until burial. For persons of Orthodox Judaism, burial needs to take place within 24 hours of death, but the body is not to be moved on the Jewish Sabbath (from sundown Friday to sundown Saturday).\n\n**Grief**\n\nFamily members and friends may display many different expressions of grief when a patient dies. One must be careful not to misinterpret or be judgmental of these individuals’ manner of grieving when it is different from what one is accustomed to seeing. In some cultures, grieving may be very expressive, with loud wailing or screaming, falling onto the floor, or rocking the body back and forward. Some cultures feel that the more expressive their grief is, the greater will be the respect and love given to the deceased person. Individuals of other cultures believe that only through intense acts of grieving can the grief and pain be moved out of them.\n\n---\n\n**U.S. & Cultural Health Care Values Grid**\n\n*Cultural values such as sense of self and space, communication and language, dress and appearance, etc., impact our cultural world-views. On the grid below, circle one square that contains characteristics that best describe your cultural world-view in each of the ten categories.*\n\n| Aspects of Culture | US Healthcare Culture | Other Cultures |\n|--------------------|-----------------------|---------------|\n| 1. Sense of self and space | • Informal \n• Handshake | • Formal \n• Hugs, bows, handshakes |\n| 2. Communication and language | • Explicit, direct communication \n• Emphasis on content – meaning found in words | • Implicit, indirect communication \n• Emphasis on context – meaning found around words |\n| 3. Dress and appearance | • “Dress for success” ideal \n• Wide range in accepted dress \n• More casual | • Dress seen as a sign of position, wealth, and prestige \n• Religious rules \n• More formal |\n| 4. Food and eating habits | • Eating as a necessity – fast food | • Dining as a social experience \n• Religious rules |\n| 5. Time and time consciousness | • Linear; exact time consciousness \n• Value on promptness \n• Time = money | • Elastic and relative time consciousness \n• Time spent on enjoyment of relationships |\n| 6. Relationships, family, and friends | • Focus on nuclear family \n• Responsibility for self \n• Value on youth; age seen as a handicap | • Focus on extended family \n• Loyalty and responsibility to family \n• Age gives status and respect |\n| 7. Values and norms | • Individual orientation \n• Independence \n• Preference for direct confrontation of conflict \n• Emphasis on task | • Group orientation \n• Conformity \n• Preference for harmony \n• Emphasis on relationships |\n| 8. Beliefs and attitudes | • Egalitarian \n• Challenges authority \n• Gender equity \n• Behavior and actions affect and determine the future | • Hierarchical \n• Respect for authority and social order \n• Different roles for men and women \n• Fate controls and predetermines the future |\n\nRevised December 2015\n\n## Conclusion\n\nCultural competence can positively affect the quality of patient care by reducing delays in seeking medical care and improving the use of limited services. Culturally competent providers may also facilitate better communication and understanding between patients and providers. The result then would be better diagnoses, development of appropriate treatment plans and improved adherence to treatment plans by patients. Therefore, culturally competent interventions may help to promote more positive health outcomes and satisfied patients and families.\n\nProviding culturally competent care is possible. Cultural competence implies more than awareness and sensitivity by the healthcare provider. Being culturally competent ranges from simply assisting patients to find their way around the facility to adequate communication so that patients give meaningful consent to services provided and that discharge instructions are clearly explained and understood.\n\n## Competency Exam: Chapter 12\n\n### Cultural Competence & Awareness\n\n| Question | Select the correct response: |\n|-------------------------------------------------------------------------|-----------------------------|\n| 1. Diversity | |\n| a. Relates only to people of different cultures | |\n| b. Is defined as “observed differences that are common to a group” | |\n| c. Is not a factor in healthcare and does not apply in the hospital setting | |\n| d. Does not occur among people of the same culture | |\n| 2. Which of the following statements regarding being culturally competent is true? | |\n| a. As long as you are a medically skilled healthcare provider, you will be culturally competent. | |\n| b. Only healthcare providers who are members of a minority group can truly be culturally sensitive and are on the way to becoming culturally competent. | |\n| c. Healthcare providers who are committed to providing quality services for all patients have most likely started the process for becoming culturally competent. | |\n| d. Practicing Healthcare providers who complete and accredited college course in world cultures are culturally competent. | |\n| 3. Regarding the provision of culturally competent care, enforcement of Title VII & the Civil Rights Act of 1964 means that hospitals and other federal funded providers must: | |\n| a. Provide healthcare for all patients with limited English proficiency at a reasonable cost. | |\n| b. Employ at least one (1) interpreter/translator for every 1000 clients served/year. | |\n| c. Have a certain number of beds reserved for the minority patients. | |\n| d. Prohibits discrimination as it affects patients with limited English proficiency. | |\n| 4. Culture may be defined “as common values, beliefs, traits, traditions and/or language that are learned and shared by members of a group” | |\n| a. True | |\n| b. False | |\n| 5. In caring for diverse populations, observing and celebrating differences are adequate for the provision of culturally competent care. | |\n| a. True | |\n| b. False | |\n| 6. Similar to individual cultures, healthcare providers and healthcare systems have distinct cultures. | |\n| a. True | |\n| b. False | |\n| 7. Components of culturally competent care include: | |\n| a. Language, Law, Efficiency | |\n| b. Demographics, Economy, Dimensions of care | |\n| c. Policies, Procedures, Education | |\n| d. Awareness, knowledge, Skills | |\n| 8. In providing culturally competent care, one of the most important skills that the healthcare provider needs to become proficient in is: | |\n| a. Communication | |\n| b. Rapport | |\n| c. Empathy | |\n| d. Teaching | |\n\nChapter 13: Information Security\n\nPurpose:\nThis module is designed to provide written guidelines for the use of computers, email, and the creation, storage, and transmission of electronic Protected Health Information.\n\nObjectives:\nAt the end of this module the learner will be able to:\n\n1. Explain the importance of information security, in general\n2. Define confidentiality, availability, and integrity; how they relate to information security in general.\n3. Briefly discuss the reasons for increased need for security policies and procedures and information security.\n4. Briefly discuss the importance of physical security precautions to protect information security.\n5. Identify examples of appropriate physical security practices for computers.\n6. Briefly discuss some of the risks that are shared by computers connected to networks\n7. Discuss the importance of protecting passwords and logon IDs\n8. Briefly describe e-mail vulnerabilities and identify ways to avoid risks to network and information security.\n\nInformation Security is Everyone’s Responsibility!\n\nThe Value of Information\n\nHow do you put a price tag on information security? Think about the value of your family’s sensitive information, such as medical records, bank balances, credit card information, and social security numbers.\n\nInformation also has tremendous value to organizations of all types. In fact, information is the lifeblood of many organizations.\n\nSensitive and proprietary information in all its forms needs to be protected and secured from all types of threats. Billions of dollars, reputations, and the very existence of some organizations are at stake.\n\nInformation Security\n\nWhy protect information?\nIn health care, the accuracy and completeness of information is critical.\n\nIncomplete or inaccurate health care information can lead to misdiagnoses, improper treatment, and other potentially life-threatening situations!\n\n**Forms of information**\n\nSensitive and proprietary information can exist in many physical forms, such as documents, books, photos, drawings, recordings, or speech.\n\nIt can also exist in electronic form, as data within information systems and networks.\n\nSome examples of physical forms of information that need to be protected and secured are\n\n- Any proprietary organizational information,\n- Copyrighted or licensed software, or\n- Any sensitive information, such as identifiable health data, financial data, trade secrets, employee data, and customer data that is on paper, disk, tape, or CD.\n- Information Systems and\n- Information in Electronic Form\n\nSome examples of electronic information and information systems that need to be secured are:\n\n- Data networks and data storage devices,\n- Switched networks and voice networks,\n- Web sites,\n- Virtual Private Networks (VPNs), and\n- All proprietary and sensitive information that travels in and out of these networks.\n\nIn order to be efficient and competitive, organizations depend on the smooth flow of information from any location at any time.\n\nAs our world becomes more dependent on e-commerce, e-health initiatives, and other types of electronic transactions, the amount of sensitive information that is stored and processed electronically grows every day. This is driving the need for information security legislation and security policies and procedures. Information security has never been more important!\n\n**Information Security: The Goal**\n\nThe goal of information security is to protect information against the loss of confidentiality, integrity, and availability.\n\n**What is confidentiality?**\n\nConfidentiality ensures that sensitive information, such as protected health information or financial data, is not made available or disclosed to any unauthorized individuals, entities, or processes.\n\n**What are the threats to confidentiality?**\n\nConfidentiality is no longer guaranteed if internal organizational matters are discussed with outsiders or disclosed carelessly, if confidential documents are treated in a careless manner, or if information systems and networks lack adequate protection.\n\n**Tips:**\n\n- **Do:** Make sure you remove confidential information from your desk or work area when you leave your work area for any length of time.\n- **Don’t:** Leave confidential information where others can read it; for example in conference rooms, lunch areas, or copy rooms.\n- **Do:** Use envelopes marked Confidential when sending sensitive information.\n\n• **Do**: Designate confidential material with the appropriate header or footer such as \"Confidential,\" \"Strictly Confidential,\" or \"Internal Use Only.\"\n• **Don’t**: Put materials containing confidential information in regular trash receptacles.\n• **Do**: Dispose of sensitive documents in appropriate receptacles or shred them.\n• **Do**: Erase white boards or chalk boards containing confidential information when finished with them.\n\n**What is availability?**\nAvailability is the state of being accessible and usable upon demand by an authorized individual or entity.\n\n**What are the threats to availability?**\n\nAvailability of information and information systems can be impaired by technical malfunctions, computer viruses, improper system operation, misfiling, damage due to environmental factors, or the careless handling of paper documents or data media such as disks, CDs, or tapes.\n\n**Some ways to protect availability:**\n• **Do**: Follow Kingsbrook security policies and procedures regarding virus scanning, software updates, file backup, data storage, and data disposal.\n• **Do**: Handle and store paper documents, disks, CDs, and tapes carefully.\n• **Don’t**: Store or use paper documents, CDs, disks, tapes, laptop computers, or keyboards near liquids or where extreme temperatures or other environmental factors could be a problem.\n\n**What is integrity?**\nIntegrity is the assurance that information or data has not been altered or destroyed in an unauthorized manner.\n\n**What are the threats to integrity?**\nIntegrity of information is damaged if information is deliberately or accidentally corrupted during storage or transmission as a result of technical defects, computer viruses, carelessness of the user, or other factors.\n\n**Some ways to protect integrity:**\n• **Do**: Follow Kingsbrook security policies and procedures regarding network access, log-off, virus scanning, software updates, file backup, data storage, and data disposal.\n• **Do**: Handle and store computers, disks, CDs, and tapes carefully.\n\n**Information Security**\n\nWhat is security? Isn’t it identical to privacy or confidentiality? Although the terms “security,” “privacy,” and “confidentiality” are often used interchangeably, they do actually mean different things.\n\n- **Security**: relates to the safeguards that protect the management of the confidential information, and the means by which it is accessed\n- **Privacy** – refers to individuals’ right to have their confidential information secured and to understand the circumstances under which it will be shared with others\n- **Confidentiality** - Through defined policies and procedures, confidentiality ties security and privacy together to ensure that whatever security measures have been established do indeed protect privacy as it has been defined\n\nThe distinctions are important. While you can secure information without making it private, you cannot protect privacy - confidentiality - without appropriate security.\n\n**Summary:**\n- The goal of information security is to protect confidentiality, availability, and integrity. This is also the goal of the HIPAA security standards.\n- The HIPAA security standards protect and secure protected health information (PHI).\n\n• Security, privacy and confidentiality mean different things. You cannot protect privacy or confidentiality without appropriate security.\n\n• The HIPAA security standards are designed to protect and secure protected health information while still permitting health care providers, health care clearinghouses, and health plans to access and use the information as needed.\n\n**Physical Security**\n\nInformation security really begins when you start your workday. Locks on doors, employee IDs, security guards, visitor badges, and other physical security measures and facility access controls help to protect us in the workplace. They also help us to protect the security of our information when they are used correctly.\n\nIdeally, the physical security best practices presented in this course should become part of your daily workflow, as natural to you as locking your front door when you leave your home.\n\n**Blueprint for Physical Security**\n\nEach workplace is unique, but all workplaces have physical and information security challenges.\n\nLocks, ID cards, and other types of access controls can be installed to limit security risks. But these security measures are only effective if we all use them properly. Let's look at some physical security best practices that you can adopt as part of your workflow.\n\n**General Physical Security**\n\n• You must wear your badge at all times while on the grounds of the hospital or its facilities.\n\n• Wear your badge with your picture facing out.\n\n• Protect your employee ID badge and don't let others use your badge.\n\n• Watch out for \"tailgaters\" at building entrances! Tailgaters are unauthorized individuals who try to gain access to the building by following a badged employee through the entrance. If in doubt, ask to see a badge.\n\n• Keep doors to sensitive areas locked. Protect your keys.\n\n• If you are concerned about your safety or notice suspicious activity, call the facility's Security Department.\n\n• All visitors must go through the main entrance of the building and register with the Security Desk.\n\n• Visitors should be met at the reception area and escorted by an employee at all times during their visit.\n\n• Visitors are also required to wear a \"Visitor\" badge and keep it visible at all times.\n\n• Do not allow visitors in unsecured areas\n\n• Lock workrooms, filing rooms, and operating areas - if unattended.\n\n• Lock all desk drawers and filing cabinets that contain confidential information, and keep the keys in a safe place.\n\n• After meetings, make sure all flipcharts, overhead transparencies, and notes are removed from the meeting room. Erase all whiteboards.\n\n• Ensure that outsiders cannot eavesdrop on discussions of confidential information, whether in hallways or on conference calls.\n\n• Media such as CD ROMS, diskettes, and print-based documents should be handled carefully and protected from environmental damage, as well as other types of damage, loss, and destruction.\n\n• Make sure all media is clearly labeled and filed correctly.\n\n• Keep media in a locked area if it contains confidential information.\n\n• Do not give documents, CDs, or other media to outsiders unless you check with your supervisor. A signed nondisclosure agreement may be required.\n\n• Computers that contain sensitive, confidential, or protected health information should be located away from public view.\n\n• If you need to work with confidential information in a public area, turn the computer screen away from public view.\n\n• Log off your computer if you will be away from your work area, or use automatic logoff features.\n\n• Use password-protected screensavers on your computer\n• Be sure to back up your work frequently. Follow Kingsbrook policies on data backup, storage, and retention.\n• If you use a laptop computer at work, keep it locked down when you are away from your desk. When traveling with a laptop, keep it with you at all times.\n\n**Summary:**\n• When used correctly, physical security measures and facility access controls help us to protect the security of our information.\n• All confidential and protected health information in any form must be secured against improper access, damage of all types, loss, and destruction.\n• All media that contain confidential information must be stored in locked areas or cabinets and disposed of properly.\n• Computers that contain confidential, sensitive, or protected health information should be located away from public access and view.\n\n**Networks**\nComputers empower us to access, create, edit, compare, and otherwise manipulate vast amounts of information for our business purposes.\n\nWhen we connect our computer to a network of other computers, we gain access to much more information flowing through the network - we increase our power! But we also greatly increase our information security risk.\n\nEach computer on the network is a potential security risk to the other computers on the network system. For instance, if an unauthorized individual gains access to one computer while it is connected to the network, that intruder could potentially steal or misuse information intended only for computers connected to the network.\n\nAnd that's not the only security risk...\n\nRisks that are shared by computers connected to a network include the:\n• risk of exposure to infection by malicious software code such as viruses, worms, and Trojans;\n• risk that proprietary, sensitive, or protected health information (PHI) could be exposed to unauthorized individuals; and\n• risk that sensitive information could be altered, damaged, or destroyed.\n\n**Logon IDs**\nTo protect and secure sensitive information, such as protected health information (PHI), on computers and computer networks, organizations often grant each employee access only to the information and applications that a specific employee needs to perform his or her job. In addition, a unique name or number (a logon or user ID) is assigned to each employee with computer or network access so the employee can be identified on the computer or computer network. If you are assigned a logon ID, protect it. Do not share it with anyone else.\n\n**Monitoring Logon Attempts**\nThere are special tools available that organizations can use to monitor logon attempts. This allows organizations to keep logs or records that can help detect when intruders try to access the system.\n\n**Logoff Procedures**\n\nIn addition to protecting your logon ID, it is important to follow Kingsbrook’s logoff procedures when you end your workday. In fact, if you leave your computer and work area for any length of time without logging off, you could potentially risk your system and network security. Password protected screensavers and automatic logoff are sometimes used to provide an additional level of security.\n\n**Encryption of Sensitive Information**\nEncryption makes information impossible to read without the proper tools. It is often used when storing strictly confidential, sensitive, or protected health information (PHI) on computer systems and transmitting it across networks. Follow Kingsbrook’s policies on encrypting sensitive data.\n\n**Summary:**\nComputer and computer network access controls such as logon IDs, authentication, firewalls, and logon monitoring are important ways to safeguard information on computers and computer networks. Logon IDs are key to network access control and should not be shared. Follow Kingsbrook’s policies and procedures regarding logon IDs, logoff procedures, and encryption of sensitive information to safeguard network security.\n\n---\n\n**Password Management**\n\n**Passwords: Keep them Strong and Silent!**\nYour password to the computer network is the most vulnerable break-in point for potential intruders or hackers.\n\nIt is vitally important that you choose your password carefully and protect it at all times. This may be the single most important contribution you can make to the security of your institution’s computer systems and network.\n\n**Security Fact:**\nPassword cracking has become very sophisticated. There are hacker programs that can guess an average of 40% of all passwords on a computer network.\n\n**Tips to Protect your Password**\n- **Do:** Choose your password yourself and ensure that only you know your password.\n- **Don’t:** Write your password down and don’t post it on your computer. (If you must have a record of your passwords, ensure that these records can only be accessed by you.)\n- **Do:** Ensure that your password cannot be easily guessed by a password cracker.\n- **Do:** Change your password frequently. If it is stolen, the time frame for unauthorized access would be limited.\n\n**Tips for Creating a Strong Password**\nThe trick is to create a password that is both difficult to guess and easy to remember. Here are some tips to help you create a strong password.\n\n- **Do:** Make your password at least eight characters in length and use upper and lower case letters, numbers, and special characters.\n - Example: Jane’s phone number is 3792. She uses a combination of the letters of her name, special characters, and her phone number. Her password is j3a*7N&9e2. (Do not use this actual example.)\n- **Don’t:** Choose words that could be found in any dictionary, whether English or any other language.\n- **Don’t:** Simply reverse the spelling of a dictionary word.\n- **Do:** Combine several short words with special characters or numbers (e.g., g0*Fish$), or use acronyms from phrases you will remember.\n\n• **Don’t**: Use a name or word associated with you in any way unless you scramble the letters (first, last, middle, wife’s, pet’s, favorite celebrity’s name, occupation).\n• **Don’t**: Use passwords that are either all numbers or all letters.\n• **Don’t**: Use a password that you have read on a password protection checklist.\n• **Don’t**: Reuse old passwords when you need to change a password, even if it was used a long time ago.\n\n**Summary:**\n• Passwords are the most vulnerable break-in points to your computer for potential intruders or hackers.\n• It is vitally important to choose a strong password yourself, and to protect your password at all times.\n• Never reveal your password to anyone.\n• Remember: You want your password to be the strong, silent type!\n\n**Malware**\nConnecting an unprotected computer to a computer network is like an unvaccinated person walking into a room full of strangers infected with the measles. Without virus protection, your computer is at risk of malicious software infection!\n\nUnprotected computers on networks, e-mail attachments, and unapproved software can be potential sources of infection. But these are not the only ways computers can be infected. Every time you open a file from someone else on a floppy disk, you could potentially expose your system to infection!\n\nBe Safe, Not Sorry:\n\nViruses, worms, and Trojans can destroy protected health information or other sensitive data, or expose it to intruders. It is vitally important to keep your virus scanning and virus protection software active and up-to-date.\n\nComputer security experts warn that malicious software is becoming more damaging and is spreading more quickly.\n\n**What you can do to protect your system…**\n• Ensure that your virus protection software is current and active. Apply updates and patches when directed by Information Systems.\n• Do not open files or e-mail attachments from anyone you do not know and trust.\n• Check all files received electronically for computer viruses.\n• Check files for computer viruses before you store them on networks or mail them out.\n• If your system behaves differently, and you suspect the presence of a virus, report it to the appropriate contact Information Systems.\n\n**E-mail**\nE-mail presents some special vulnerabilities and dangers. All e-mail exists on at least three servers: the sender’s server, the receiver’s server, and the server that transmits the e-mail. This exposure adds more risk to the security and confidentiality of e-mail.\n\nE-mail is also a potent source of viruses, which are often embedded in attachments.\n\n**E-mail Tips**\n• **Do**: Be extremely wary when you receive an e-mail attachment. Even if the subject line is intriguing, or sounds official, do not open it unless you are expecting it and you are sure it is virus-free.\n• **Don’t**: Open any attachments that seem suspicious.\n• **Do**: Adhere to Kingsbrook’s policies on sending and receiving e-mail attachments. E-mail attachments can become quite large and take up space on servers.\n\n• **Do:** Be careful when you receive e-mail alerts warning of viruses. Do not send the alerts to anyone. Check with your system administrator before taking any action.\n\n• **Don’t:** Send confidential or proprietary information in e-mail without designating it as \"Confidential.\"\n\n• **Do:** Encrypt all e-mail that contains protected health information (PHI).\n\n**Don’t be the Weak link**\n\nBe skeptical. If you are not absolutely sure a request for information is valid, verify the identity of the requester. If the request is by telephone, ask for a telephone number and call the person back.\n\nE-mail requests for information should be handled very cautiously. Always carefully examine the e-mail address of the requester to be certain that it originates from a trusted person in Kingsbrook. If you are unsure about the validity of any request, contact your supervisor.\n\nSome types of requests should always be treated with suspicion. For instance, it is very unusual for anyone to ask you for your password or request that you make changes to your computer system. Requests like these should always be verified with your supervisor or Kingsbrook’s Information Security department.\n\nRemember: there are people who make a lot of money by stealing information. Corporate spies and identity thieves are real threats to information security! Use common sense, and take precautions.\n\nIn the Physical Security unit of this course, you learned about the importance of facility access controls. Keep your employee ID, keys, and computer systems secure. Don’t lend your employee ID to anyone!\n\nBe careful when you discuss confidential matters. Always follow Kingsbrook’s policies when you access, handle, and dispose of sensitive and confidential information in all its forms.\n\nAs you learned in the Network Security unit of this course, you should keep your passwords to your computer system strong and silent! Don’t allow anyone else to use your password. When you log on to your system, make sure no one sees you type your password. Watch out for shoulder surfers!\n\nSince unapproved software and e-mail attachments can be entry points for malicious code, don’t install software unless it is approved by Kingsbrook, and be wary of opening e-mail attachments. To guard against infection, keep your virus scanning software up-to-date.\n\nReport suspicious activities to your supervisor or the appropriate department. It’s better to be safe than sorry.\n\nNever underestimate the role you play in Kingsbrook’s security plan. You can be the strongest link in the information security chain!\n\n| Question | Select the correct response |\n|-------------------------------------------------------------------------|----------------------------|\n| 1. The goal of information security is to protect confidentiality, integrity, and availability. | a. True \nb. False |\n| 2. When you shred sensitive documents to dispose of them, you protect | a. Availability. \nb. Integrity. \nc. Confidentiality. |\n| 3. The HIPAA security standards are designed to protect and secure which of the following types of information? | a. Protected health information \nb. Confidential banking information \nc. Trade secrets |\n| 4. When a meeting has ended, you should make sure all flipcharts, overhead transparencies, and notes that contain confidential information are removed from the meeting room. | a. True \nb. False |\n| 5. John’s workplace has a policy that he log off his computer network when he leaves his work area for any period of time. John is in a hurry and just wants to leave for a moment to get a coffee. Should he log off? | a. Yes \nb. No |\n| 6. Which of the following is not a desirable characteristic of a strong password? | a. It is at least eight characters long. \nb. It contains special characters, numbers, and letters. \nc. It is difficult to guess. \nd. It contains all numbers. |\n| 7. Computer viruses are a big nuisance, but they don’t do much damage. | a. True \nb. False |\n| 8. If an e-mail contains protected health information (PHI), it should be encrypted. | a. True \nb. False |\n\nChapter 14: Emergency Management\n\nPurpose:\nEmergency Management is the discipline of identifying hazards and risks, from both natural and man-made disasters, and the subsequent development of plans and strategies to lessen the impact of these disasters, guide response, and aid in recovery. This module is designed to ensure staff familiarity with the written guidelines for Emergency Management specifically created for Kingsbrook Jewish Medical Center (KJMC) and Rutland Nursing Home (RNH).\n\nObjectives:\nAt the end of this module the learner will be able to:\n\n1. Identify emergency situations and initiate the emergency response.\n2. Know how to react to emergencies and help patients, visitors, residents, and co-workers.\n3. Understand the policies and procedures of Emergency Management at KJMC/RNH.\n\nKey Points of Emergency Management\nIn the event of an emergency – whether it’s external, such as severe weather conditions (blizzard, hurricane, etc) or internal (fire, active shooter, etc), it’s important to:\n\n- Remain calm.\n- Ensure the safety of yourself and those around you.\n- Alert the facility to the emergency.\n- Follow protocol.\n\nDisaster Code\nIf you are reporting an emergency, and after ensuring the safety of yourself and those around you, call the operator and have them announce the Disaster Code:\n\n2-2-2-2\n\nThe Operator will announce the Disaster Code via overhead page, which will alert the entire Medical Center that there is an emergency that requires everyone’s attention and full cooperation. Announcement of the Disaster Code activates the Emergency Operations Plan (EOP).\n\nProtocol\n\nDuring a disaster response all employees shall:\n\n- Take immediate and appropriate action to protect life and conserve property.\n- If the emergency is a fire or hazardous materials situation, follow RACE/Fire protocol.\n- Stay calm and assist patients and others who may be within the event area.\n- End all non-emergent phone calls.\n- Avoid using telephones or elevators.\n- Notify your Supervisor or the Administrator on Duty and: describe the nature, extent and source of the notification of the disaster.\n- If it is an event that is external to KJMC: are we expecting patients/victims, and if so, how many?\n- Wear your Hospital ID conspicuously and clearly on outermost garment.\n- Continue working in your usual area until otherwise instructed by a Supervisor or Administrator.\n- Follow instructions of the Department Supervisor or appropriate Administrator.\n- Avoid going to disaster treatment areas unless requested to do so by Supervisor.\n- Refer to this Emergency Operations Plan for additional information.\n\nDuring a disaster response Senior Administrative staff shall:\n\n- Take immediate and appropriate action to protect life and conserve property.\n- Assume the role of Incident Commander and open the Command Center.\n- Assess the situation.\n- Inform the Operator as per policy.\n- Read Activation of the Emergency Operations Plan.\n- Assign staff to specific, necessary HICS positions.\n- Follow your Job Action Sheet.\n\nEmergency Operations Plan (EOP)\n\nThe Emergency Operations Plan (EOP) has been developed as a resource guide for use at KJMC/RNH in the event of an internal or external disaster affecting the environment of care. It was developed to enable response to any type of emergency and it called an All-Hazards plan. The EOP is a living document and updated annually as part of our ongoing preparedness activities.\n\nThe plan addresses the four phases of Emergency Management activities:\n\n- Mitigation\n- Preparedness\n- Response\n- Recovery\n\nA copy of the EOP is kept in the Emergency Command Center (ECC), The Emergency Department (ED), the Security Department, and is available as a PDF via a link from the homepage of the hospital intranet.\n\nEmergency Command Center (ECC)\n\nThe Emergency Command Center (ECC) is located in Room 318 on the third floor of the Katz Building. The ECC can be reached at extension 5455, or via e-mail firstname.lastname@example.org. An alternative location for the ECC is the Lillian Minkin Ballroom located in the Leviton building.\n\nHospital Incident Command System (HICS)\n\nKJMC follows has the national standard Hospital Incident Command System (HICS) chain of command. Similar to a table of organization, this command structure clearly defines roles, responsibilities, and the reporting structure for the incident response. The HICS structure is led by the Incident Commander (IC), and is a scalable and flexible system.\n\nNote that although the average staff member is not on the HICS table of organization, though all staff are expected to be familiar with the HICS system. Individual staff report separately to their respective departmental supervisors, managers, directors, or chiefs.\n\nKJMC recognizes four Activation Levels of HICS. The level of response is decided by the IC.\n\n- Level 1 is an Alert/Notify response.\n- Level 2 is a response to an event anticipated to have minor impact on the facility.\n- Level 3 is a response to an event anticipated to have moderate impact on the facility.\n- Level 4 is a response to an event anticipated to have major impact on the facility.\n\n**National Incident Management System (NIMS)**\n\nThe National Incident Management System (NIMS) has been developed and is promulgated by the Federal Emergency Management Agency (FEMA). The purpose of the system is to enable hospitals and allied agencies to seamlessly integrate and coordinate their response to a disaster. All staff members are encouraged to learn more about NIMS and HICS by taking the self-guided Independent Study courses offered online by FEMA’s Emergency Management Institute.\n\n**Everbridge Mass Notification System**\n\nEverbridge is a Mass Notification ring-down system utilized by KJMC/RNH to enable communication with employee in the event of a natural disaster or emergency. Everbridge enables System Administrators to send notifications to individuals or groups using lists, locations, and visual intelligence. This comprehensive notification system keeps everyone informed during the course of the response.\n\nAll staff members are strongly encouraged to provide their updated contact information (including personal cell phone number and e-mail) and sign up with Everbridge Mass Notification System by following the link below:\n\n- [https://member.everbridge.net/index/1772417038942659](https://member.everbridge.net/index/1772417038942659)\n\nA user name and a unique password must be created.\n\n- Once you’ve created a user name and password log into Everbridge using this link:\n - [https://manager.everbridge.net/login](https://manager.everbridge.net/login)\n- During an emergency activation it is imperative to pay attention to Everbridge notifications, and respond affirmatively upon receipt of a message.\n\n**Conclusion:** Disasters are inevitable at times and while some can not be prevented, preparedness is critical to survival. During a disaster all staff must end all non-essential calls and activities. Return to their department and report to their unit leader. Have their identification badge displayed clearly and lastly avoid use of elevators as they may needed for patient/residents transport and supplies. Staff Members should be aware and know who their section chief and leader is, and comprehend their EOP (Emergency Operations Plan), which is located in the Policy Manager online.\n\n| Question | Select the correct response |\n|----------|---------------------------|\n| 1. Emergency Management is: | A. The management of the hospital’s Emergency Department (ED). \nB. The act of taking over for your Supervisor in the event they are unable to fulfill their work obligations. \nC. The discipline of identifying hazards and risks, from both natural and man-made disasters, and the subsequent development of plans and strategies to lessen the impact of these disasters, guide response, and aid in recovery. \nD. More an art than a science, and primarily involves thinking on your feet. |\n| 2. The KJMC/RNH Disaster Code is: | A. 2-2-2-2 \nB. 9-9-9-9 \nC. 1-2-3-4 \nD. 0-0-0-0 |\n| 3. When responding to an emergency you should: | A. Always take the elevators, because they’re faster than the stairs. \nB. Remove your ID badge to protect against identity theft. \nC. Report immediately to the Command Center. \nD. Continue working in your usual area until otherwise instructed by a Supervisor or Administrator. |\n| 4. The Emergency Operations Plan (EOP) is: | A. A living document that is updated annually as part of our ongoing preparedness activities. \nB. A living document that is updated every three years as part of our Joint Commission preparations. \nC. Only available to Senior Administration. \nD. Developed by The Federal Emergency Management Agency, and is standard for all hospitals. |\n| 5. The Elements of Emergency Management are: | A. Identification, Reaction, Protection & Rebuilding \nB. Development, Mitigation, Reaction & Conservation \nC. Preparedness, Preservation, Protection & Recovery \nD. Mitigation, Preparedness, Response & Recovery |\n| 6. The HICS system: | A. Stands for Healthcare Involvement Coordinating Standards. \nB. Is a rigid hierarchy. \nC. Is led by the Senior Administrator (SA). \nD. Is a scalable and flexible system. |\n\n| Question | Options |\n|-------------------------------------------------------------------------|-------------------------------------------------------------------------|\n| 7. The top of the chain of command, as defined by the HICS Structure is: | A. The Emergency Preparedness Coordinator \nB. The Incident Commander \nC. The Chairman of Emergency Medicine \nD. The Hospital Safety Officer |\n| 8. The Command Center is located: | A. In the Administrative Suite of the Emergency Department (ED). \nB. Wherever the Incident Commander is at the time. \nC. On the third floor of the Katz building in Room 318. \nD. In a hardened bunker beneath the cafeteria. |\n| 9. KJMC/RNH recognizes how many Levels of Activation? | A. Three \nB. Four \nC. Seven \nD. Ten |\n| 10. NIMS stands for: | A. National Incident Management System \nB. National Interagency Medical Structure \nC. Necessary Integrated Municipal Systems \nD. New Improved Mutual Safeguards |\n\nChapter 15: National Patient Safety Goals\n\nPurpose:\nThis module is designed to provide written guidelines for National Patient Safety Goals for Kingsbrook Jewish Medical Center and Rutland Nursing Home.\n\nObjectives:\nAt the end of this module the learner will be able to:\n\nUnderstand the National Patient Safety Goals for Kingsbrook Jewish Medical Center and Rutland Nursing Home\n\nThe Joint Commission Program for National Patient Safety Goals (NPSG) began in 2002. NPSG were established to help organizations address specific areas of concern as regards patient safety. Every year safety goals are distributed nationally. Some goals are new, and some goals are goals repeated from previous years. Why are goals posted annually? It is because the Joint Commission consults with a panel of widely recognized experts on safety who advises them on emerging patient safety issues. This Patient Safety Advisory Group, comprised of nurses, physicians, pharmacists, risk managers, and other professionals, work with the Joint Commission to identify critical issues and trends of concern regarding patient safety. Sentinel events and other investigations regarding emerging safety concerns coalesce into the emergency of the annual goals.\n\nNATIONAL PATIENT SAFETY GOALS FOR 2016\n\n- **Improve the Accuracy of Patient Identification**\n Use at least two ways to identify the patient. Commonly, we use name and date of birth for identification. This is always done to make sure each patient gets the correct medication and treatment. Of special concern is making sure patients receive the correct blood products.\n\n- **Improve the effectiveness of communication among caregivers**\n Handoff is given to oncoming staff in a comprehensive way, identifying important information about the patient and updated information about care. All people involved in handoff must pay close attention as this is a critical part of patient care. Assure that all important test results are given to the right person at the right time.\n\n- **Improve the safety of using medications**\n All medications must be labeled. Medications which are transferred to a syringe must have the syringe labeled with the medication. Special care should be given to medications that are blood thinners. Record and pass along correct information about patient medications. Comparing current medications to the medications patients take at home is critical to patient safety (medication reconciliation). Assure the patients know which medications they must take upon discharge and/or after their visit.\n\n- **Reduce the harm associated with clinical alarm systems**\n Ensure that alarms on medical equipment are heard and responded to in a timely manner.\n\n- **Reduce the risk of health care associated infections**\n Use handwashing guidelines as per hospital policy. Be vigilant with infection prevention in central lines (CLBABS) and urinary catheters (CAUTI)\n\n• The hospital identifies safety risks inherent in its patient population\n Identify patients at high risk for suicide and intervene immediately and appropriately.\n\n• University Protocol for preventing wrong site, wrong procedure, and wrong person surgery.\n Assure the correct surgery is done on the correct patient and at the correct place on the person’s body, mark the correct place on the body where the surgery is being done, “TIME OUT” (pause!) before the surgery to review that you have the right patient, right site, and right procedure.\n\n| Question | Select the correct response |\n|-------------------------------------------------------------------------|----------------------------|\n| 1. National Patient Safety Goals are the same every year. | a. True |\n| | b. False |\n| 2. National Patient Safety Goals are written after consideration of sentinel events and other critical issues and trends regarding safety. | a. True |\n| | b. False |\n| 3. National Patient Safety Goals are written by a random group of patients who are worried about safety. | a. True |\n| | b. False |\n| 4. One of the national patient safety goals is to reduce the risk of health care associated infections and reduce harm associated with clinical alarm management. | a. True |\n| | b. False |\n\nThis page intentionally left blank."},"books_score":{"kind":"number","value":0.5116035342216492,"string":"0.511604"}}},{"rowIdx":8692,"cells":{"content":{"kind":"string","value":"Acquisition Master Class\n\nReader Revenue MASTER CLASS ACQUISITION\n\nAugust 2020\n\nmather:\n\nMather specializes in applied analytics.\n\n10:1 RETURN ON INVESTMENT\n\nOur typical client engagement provides a 10-to-1 return on investment. We increase revenue yield and reduce risks from pricing actions.\n\n$6B+ REVENUE MANAGEMENT\n\nWe provide customer analytics and yield management for over 200 clients with $6 billion in combined annual revenue and 30 million customers.\n\n200 CLIENTS IN DIVERSE INDUSTRIES\n\nMather works with organizations in several industries to help them adapt their business models to digital disruption.\n\n18 YEARS EXPERIENCE & TURNKEY CONSULTING\n\nFounded in 2002 with offices in North America and Europe. Our consulting services include extensive reporting with A/B testing and model validation. We are fully GDPR, CCPA compliant and SOC2 audited.\n\nIn the most recent 30-day period, explicitly tagged COVID-19 content that appears on the path to conversion has declined to 42% vs. a high of 80% during the April period.\n\nCOVID-19 articles produced has stabilized in the last 60 days at 16% of all articles from a high of 46% during the April period.\n\nThe impact of COVID-19 content on path to conversion and engagement mirrors the pattern of new COVID-19 cases in the United States.\n\nNew conversion growth is past its peak and slowly trending down towards March levels.\n\nThere continues to be relative growth in subscriptions compared to February.\n\nFanatic and Known users have stabilized since May, suggesting an overall growth in engaged and high propensity users.\n\nThe number of users hitting the paywall is only 4% higher than February levels, suggesting non-paywall channels are key for subscription growth.\n\nThe Conversion Rate is improved from the influx of Fanatic users as well, making the paywall more effective.\n\nKEY METRICS BY AUDIENCE TYPE\n\nThough the aggregate volume of New Users grew significantly throughout March-April, the proportion of New Users has remained around 80%.\n\nThe aggregate volume of Fanatic Users grew significantly throughout March-April, and proportion of Fanatics has grown. The proportion has been declining since the April peak.\n\nThe aggregate volume of Known Users has grown and stabilized since March and the proportion of Known Users is hovering closer to 2% in recent months.\n\n| % of New Users vs. All Users | % of Fanatics vs. All Users | % of Known Users vs. All Users |\n|-----------------------------|----------------------------|-------------------------------|\n| 6/16-7/15 | 3.57% | 1.86% |\n| 5/17-6/15 | 3.41% | 1.74% |\n| 4/17-5/16 | 3.74% | 1.99% |\n| 3/18-4/16 | 4.05% | 1.52% |\n| 2/17-3/17 | 3.34% | 1.54% |\n| 1/17-2/16 | 3.12% | 1.67% |\n\nmather:\n\nKEY METRICS FOR SUBSCRIPTION GROWTH\n\nThe Conversion Ratio measures all conversions vs. all users. The conversion ratio peaked in April-May though is still higher than the start of the year.\n\nHitting the paywall includes all types (meter, subscriber only, hardwall). The proportion of paywall hits has declined, likely due to “free” COVID-19 content and one-time users.\n\nThe Conversion rate is exclusive to the paywall channel (no voluntary or email). The conversion rate peaked in April-May though is still higher than the start of the year.\n\n| Total Conversion Ratio | % |\n|------------------------|---|\n| 6/16-7/15 | 0.039% |\n| 5/17-6/15 | 0.041% |\n| 4/17-5/16 | 0.053% |\n| 3/18-4/16 | 0.052% |\n| 2/17-3/17 | 0.033% |\n| 1/17-2/16 | 0.023% |\n\n| % of Users Hitting the Paywall | % |\n|--------------------------------|---|\n| 6/16-7/15 | 7.81% |\n| 5/17-6/15 | 7.50% |\n| 4/17-5/16 | 6.91% |\n| 3/18-4/16 | 7.17% |\n| 2/17-3/17 | 8.31% |\n| 1/17-2/16 | 8.63% |\n\n| Paywall Conversion Rate | % |\n|-------------------------|---|\n| 6/16-7/15 | 0.19% |\n| 5/17-6/15 | 0.24% |\n| 4/17-5/16 | 0.32% |\n| 3/18-4/16 | 0.30% |\n| 2/17-3/17 | 0.16% |\n| 1/17-2/16 | 0.10% |\n\nCONCEPTS WE WANT TO SHARE TODAY\n\n- PRICING OPTIMIZATION & PRICE ELASTICITY OVER TIME\n- DIGITAL AUDIENCE ENGAGEMENT SEGMENTS\n- LIMITATIONS OF ANALYTICS ON UNKNOWN USERS\n- DYNAMIC METER PATTERN RECOMMENDATIONS\n- TACTICS TO GROW DIGITAL SUBSCRIPTIONS\n\nPrice elasticity differs greatly by tenure level.\n\n| SUB. YEAR | PRICE STOPS | PRICE ELASTICITY |\n|-----------|-------------|------------------|\n| 0-1 | 4.3% | -0.9 |\n| 1-2 | 2.2% | -0.4 |\n| 2-3 | 1.3% | -0.3 |\n| 3-4 | 1.3% | -0.3 |\n| 4-5 | 0.9% | -0.2 |\n| 5-6 | 0.5% | -0.1 |\n\n- BAU target subs received 5% increase\n- Holdout subs received no increase\n- Differences in total stops due to price change\n\nSimilar findings are true with Digital Engagement, Income levels and Age groups.\n\nOffer pricing balances quality and quantity:\n\n- Higher prices attract fewer customers with less churn\n- Lower prices attract more customers with higher churn\n\nOptimal prices maximize total expected operating margins\n\nMather uses predicted customer retention and conversion rates to find optimal prices\n\nPRICE ELASTICITY BENCHMARKS BY MONTHLY PRICES\n\nMSRP and Price Elasticity Benchmarks\n\nMonthly MSRP\n\nElasticity\n\nmather:\n\n| Segment | % of Audience | All Users | Page Views | Article Page Views | Unique Days | Visits Per User | Time Per Visit | Scroll Depth | Ad Revenue | % of Ad Revenue | % Known Users | Cookies Per Known User |\n|------------------|---------------|------------|------------|-------------------|-------------|-----------------|----------------|--------------|------------|---------------------|---------------|------------------------|\n| Fanatics | 2.0% | 89,978 | 32.4 | 14.9 | 5.1 | 13.9 | 5:33 | 54% | $0.72 | 27.2% | 4.07% | 1.71 |\n| Enthusiasts | 4.0% | 181,331 | 8.2 | 5.6 | 1.8 | 4.4 | 5:50 | 49% | $0.18 | 13.7% | 0.44% | 1.1 |\n| Stable Users | 6.9% | 310,245 | 4.1 | 3 | 1.1 | 2.3 | 4:53 | 49% | $0.09 | 11.7% | 0.17% | 1.04 |\n| Dabblers | 12.2% | 549,557 | 2.4 | 1.9 | 0.9 | 1.5 | 4:35 | 48% | $0.06 | 13.8% | 0.05% | 1.03 |\n| Flybys | 44.0% | 1,979,735 | 1.2 | 1.1 | 0.6 | 1 | 2:15 | 42% | $0.03 | 24.9% | 0.01% | 1 |\n| Non-Engaged | 30.9% | 1,392,588 | 1 | 0.8 | 1 | 1 | 0:00 | 0.02% | $0.02 | 8.8% | 0.00% | 1 |\n\n*All users are based on unique visitors*\n\n| | FANATICS | ENTHUSIASTS | STABLE USERS | DABBLERS | FLYBYS | NON-ENGAGED |\n|------------------------|-----------|-------------|--------------|----------|----------|-------------|\n| % OF AUDIENCE | 2.0% | 4.0% | 6.9% | 12.2% | 44.0% | 30.9% |\n| ALL USERS | 89,978 | 181,331 | 310,245 | 549,557 | 1,979,735| 1,392,588 |\n| PROPENSITY TO SUBSCRIBE| 0.200% | 0.067% | 0.033% | 0.017% | 0.008% | 0.000% |\n| CONVERSIONS FROM METER | 169 | 91 | 53 | 15 | 0 | 0 |\n| ADV REV PER PAGE | $0.022 | $0.022 | $0.022 | $0.025 | $0.025 | $0.015 |\n| MISCATORIZED USER PCT | 0.05% | 0.05% | 0.20% | 0.8% | 25.0% | n/a |\n| MISCATORIZED USER NUM | 45 | 91 | 620 | 4,396 | 494,934 | n/a |\n| CONV RATE OF MISCATORIZED USERS | 0.04% | 0.04% | 0.04% | 0.04% | 0.04% | n/a |\n| CONV OF MISCATORIZED USERS | 0.0 | 0.0 | 0.3 | 2 | 217 | n/a |\n| TOTAL CONVERSIONS | **169** | 91 | 53 | 17 | **217** | |\n\nmather:\n\nDYNAMIC PAYWALL RECOMMENDATION\n\nMather recommends a rainbow-like pattern of access, with a tight paywall on the ends of the engagement spectrum and more content offered to the medium-engaged user segments.\n\nSample* recommendations by Audience Segment\n\n- Fanatics: 2 articles\n- Enthusiasts: 4 articles\n- Repeat Low-Engagement (groups 1-4): 11 articles\n- First-Time Users: 2 articles\n\n* Note: these results will differ by product\n\nRead Mather’s White Paper\nResearch highlights 7 digital subscription best practices\n\nTACTICAL RECOMMENDATIONS\n\n- Long-term subscriptions\n- Extended promotional terms\n- Increase the share of premium content\n- Adopt an organizational structure to maximize digital subscriptions\n- Reduce friction in the checkout process\n\nmather:\n\nEngagement Master Class\n\nReader Revenue MASTER CLASS ENGAGEMENT\n\nSeptember 2020\n\nmather:\n\nMather specializes in applied analytics.\n\n10:1 RETURN ON INVESTMENT\n\nOur typical client engagement provides a 10-to-1 return on investment. We increase revenue yield and reduce risks from pricing actions.\n\n$6B+ REVENUE MANAGEMENT\n\nWe provide customer analytics and yield management for over 200 clients with $6 billion in combined annual revenue and 30 million customers.\n\n200 CLIENTS IN DIVERSE INDUSTRIES\n\nMather works with organizations in several industries to help them adapt their business models to digital disruption.\n\n18 YEARS EXPERIENCE & TURNKEY CONSULTING\n\nFounded in 2002 with offices in North America and Europe. Our consulting services include extensive reporting with A/B testing and model validation. We are fully GDPR, CCPA compliant and SOC2 audited.\n\nPublishers often leverage a composite digital engagement index, composed of five different variables measuring intensity, frequency, recency, and breadth of digital content consumption.\n\nA composite index allows for use of several different types of digital engagement metrics without negative effects of multicollinearity.\n\nCONCEPTS WE WANT TO SHARE TODAY\n\nDIGITAL AUDIENCE ENGAGEMENT SEGMENTS\n\nTHE VALUE OF KNOWING A READER\n\nCHANGES IN ENGAGEMENT PREDICT CHURN\n\nPRICING OPTIMIZATION & PRICE ELASTICITY BY ENGAGEMENT LEVEL\n\n| AVG. PER USER PER MONTH | FLYBYS | STABLE USERS | ENTHUSIASTS | FANATICS |\n|------------------------|---------|--------------|-------------|----------|\n| ALL USERS | 6.9M | 595K | 340K | 167K |\n| PAGEVIEWS | 1.4 | 7.0 | 14.4 | 100.7 |\n| ARTICLE PAGEVIEWS | 0.9 | 2.6 | 4.4 | 27.2 |\n| VISITS | 1.1 | 2.6 | 5.0 | 26.2 |\n| TIME PER VISIT | 02:17 | 06:57 | 07:40 | 06:41 |\n| SCROLL DEPTH | 28% | 50% | 52% | 62% |\n| AD REVENUE | $0.01 | $0.05 | $0.12 | $1.08 |\n| UNIQUE DAYS | 1.1 | 2.1 | 3.6 | 9.5 |\n| % KNOWN USERS | 0% | 2% | 5% | 38% |\n| CONVERSION RATE | 0.00% | 0.22% | 0.28% | 0.73% |\n\nThe growth in volume of Fanatic users is the primary driver of the spike in conversions observed during March – June 2020.\n\nFanatic volume grew over 3X and the proportion of total Fanatics grew by 2X, impacting total conversions 2X vs. 2019.\n\nThe conversion ratio for all users (0.04%) stayed consistent while the Fanatic conversion ratio declined (1.4% in 2019; 0.77% in 2020).\n\nThe proportion of Conversions from the Fanatic segment declined slightly YOY (64% in 2019; 58% in 2020).\n\nKNOWN READERS MUCH MORE LIKELY TO SUBSCRIBE\n\nUser Segments and Conversion Probability:\nLarge Publisher with Registration Wall\n\n- All Users: 0.015%\n- High Propensity Segment: 0.061%\n- Known User Segment: 0.063%\n\nMachine Learning Model Feature Influence:\nLarge Publisher with Registration Wall\n\n- Known User: 20%\n- Time Per Visit: 14%\n- Page Views: 12%\n- Visits: 9%\n- Article Page Views: 9%\n- Avg Depth: 8%\n- Avg Velocity (Pixels Per Second): 7%\n- Avg Breadth: 7%\n- Unique Days: 5%\n- Hard Modal Count: 3%\n- Desktop: 2%\n- Morning: 1%\n- Weekday: 1%\n- Local: 1%\n- Paywall Encountered in Prior Visit: 0%\n\nRegistered users are moderately engaged, but subscribed users are most engaged.\n\nMather recommends considering engagement during pricing decisions. You may consider excluding “sleepers” from price changes if they have zero engagement for long periods of time.\n\nSample* pricing recommendations by Audience Segment\n\n- Fanatics & Enthusiasts: Regular renewal price change\n- Stable & Dabblers: Moderated renewal price change\n- Not Engaged: No price increase\n\n*Note: these results will differ by product\n\nRead Mather’s White Paper\nDigital Subscriber Price Optimization\n\nFull price digital subscriptions tend to have the highest engagement, while print + digital and promotional digital-only subscriptions have lower.\n\nCHURN MODEL RESULTS – ENGAGEMENT\n\nSample Regression Output\nEngagement levels have significant effect on subscriber retention\n\nSales channels attract customers with different levels of engagement:\n\n- **Direct sales** to customers that go to the subscription page directly are most engaged.\n- **Metered customers** have next highest engagement.\n- **Premium/restricted content sales** have the lowest engagement.\n\nRetention of these customers reflects their engagement levels at time of the subscription purchase.\n\nChallenge – increase engagement following the sale, particularly those from premium content.\n\nTACTICAL RECOMMENDATIONS\n\n- Convert anonymous visitors to known readers\n- Segment audience by engagement for acquisition and engagement\n- Consider engagement levels when adjusting subscription prices\n- Trigger retention campaigns when engagement falls below historical pattern\n\nmather:\n\nRetention Master Class\n\nReader Revenue MASTER CLASS RETENTION\n\nNovember 2020\n\nmather: matthereconomics.com\n\nMather specializes in applied analytics.\n\n10:1 RETURN ON INVESTMENT\n\nOur typical client engagement provides a 10-to-1 return on investment. We increase revenue yield and reduce risks from pricing actions.\n\n$6B+ REVENUE MANAGEMENT\n\nWe provide customer analytics and yield management for over 200 clients with $6 billion in combined annual revenue and 30 million customers.\n\n200 CLIENTS IN DIVERSE INDUSTRIES\n\nMather works with organizations in several industries to help them adapt their business models to digital disruption.\n\n18 YEARS EXPERIENCE & TURNKEY CONSULTING\n\nFounded in 2002 with offices in North America and Europe. Our consulting services include extensive reporting with A/B testing and model validation. We are fully GDPR, CCPA compliant and SOC2 audited.\n\nCONCEPTS WE WANT TO SHARE TODAY\n\nPRICING OPTIMIZATION & PRICE ELASTICITY\n\nCHURN PROPENSITY MODELING\n\nRETENTION CAMPAIGN TACTICS\n\nDEMAND CURVE\n\nObserved Prices and Quantities – vs. Demand Curve\n\nWeekly price/issue\n\nSubscribers\n\n€0.00 €2.00 €4.00 €6.00 €8.00 €10.00 €12.00 €14.00 €16.00\n\n0 10,000 20,000 30,000 40,000 50,000 60,000\n\nmather:\n\nRENEWAL PRICE ELASTICITY\n\nElasticity = % (change in quantity) / % (change in price)\n\n- Assume 5,000 active subscribers\n- Assume a 15% change in price\n- Assume 250 subscribers stopped\n- $250 \\div 5,000 = 5\\%$ stops\n- $5\\% \\div 15\\% = -0.33$ elasticity\n\nRETENTION EXAMPLE\n\nPoint A:\nCustomer status prior to a renewal price increase\n\nPoint B vs. C:\nThe expected retention probability per customer with and without a price increase\n\nEach subscriber has an overall churn risk and price elasticity.\n\n-0.30 Mean Elasticity\n-0.28 Median Elasticity\n\nMBP applies a higher price increase on customers with lower price elasticity.\n\n*Average variable price increase is still 15%*\n\nPrice elasticity differs greatly by tenure level.\n\n| TENURE YEAR | PRICE STOPS | PRICE ELASTICITY |\n|-------------|-------------|------------------|\n| 0-1 | 9.3% | -1.9 |\n| 1-2 | 2.2% | -0.4 |\n| 2-3 | 1.3% | -0.3 |\n| 3-4 | 1.3% | -0.3 |\n| 4-5 | 0.9% | -0.2 |\n| 5-6 | 0.5% | -0.1 |\n\n- BAU target subs received a renewal price increase\n- Holdout subs received no increase\n- Differences in total stops due to price change\n\nSimilar findings are true with Digital Engagement, Income levels and Age groups.\n\nMARKET BASED PRICING (MBP)\n\nMBP – APPLICATION OPTIONS\n\nIncreasing pricing intelligence and flexibility increases yield.\n\nAnalytics can identify customers with high or low sensitivity to price.\n\nMore accurate targeting improves performance and efficiency.\n\nTradeoffs between complexity and yield can be measured.\n\nYield from price increases\n\nPrice differentiation\n\nProduct pricing\n\nData for analysis:\n- Product history\n- Market data\n- Macroeconomic\n- Marginal costs\n\nSegment pricing\n\nData for analysis:\n- Segment characteristics\n- Group behavior\n- Geographic data\n- + Product data\n\nIndividual pricing\n\nData for analysis:\n- Account history\n- Engagement\n- Demographics\n- + Segment data\n\nThe return on a **targeted** 10% price increase vs. an **across-the-board** 10% price increase to 100,000 subscribers:\n\n### Subscribers\n\n| Subscriber: | 100,000 |\n|-------------|---------|\n| Monthly price: | $50 |\n| Monthly rev: | $5 million |\n| Annual rev: | $60 million |\n\nAverage increase: 10%\nGross incr. rev/Mos: $500,000\nGross incr. rev/Yr: $6 million\n\n### Across the Board\n\n| Avg. ren. price elasticity: | -0.4 |\n|-----------------------------|------|\n| Lost subs from pricing: | -4,000 |\n| Lost monthly revenue: | -$240K |\n| Lost annual revenue: | -$2.64M |\n\nRemaining subs: 96,000\nPrice per month: $55\nAnnual revenue: $63.36M\nNet yield on increase: $3.36M\nYield percentage: 56%\n\n### Targeted Pricing\n\n| Reduction in price stops: | 50% |\n|---------------------------|-----|\n| Lost subs from pricing: | -2,000 |\n| Lost monthly revenue: | -$120K |\n| Lost annual revenue: | -$1.32M |\n\nRemaining subs: 98,000\nPrice per month: $55\nAnnual revenue: $64.68\nNet yield on increase: $4.68M\nYield percentage: 78%\n\n### Revenue Yield\n\nTargeted pricing reduces pricing-related subscriber and revenue loss while improving revenue yield for this pricing action by\n\n$120,000/month or $1,320,000/year & 20% better yield\n\nMarket Based Pricing helps to stabilize customer revenue over the long term.\n\nDeclining customer volumes in disrupted services can be offset by targeted rate adjustments.\n\nRevenue stabilization provides an extended runway to invest and grow new products.\n\nCHURN MODELING\n\nmather:\n\nART & SCIENCE OF CHURN MODELING\n\nChurn modeling calculates the likelihood that an individual will discontinue services due to a specific event.\n\nOnce we’ve answered who is likely to churn, the question then becomes what can be done about it?\n\nCommon characteristics of successful initiatives driven by churn scores:\n\n- Personalized to individual customers\n- Measured accurately (A/B tests, metrics reporting)\n- Implemented soon after churn signal observed\n- Authentic and effective messaging copy and creative\n\nA positive coefficient indicates a contribution to increased churn risk, while a negative coefficient indicates contribution to decreased churn risk.\n\n| Base Variable | Variable Description | Variable | failure | Restricted failure | Unrestricted failure |\n|---------------|----------------------|----------|---------|--------------------|----------------------|\n| Weekly Price | wp | wp | -0.0235*** | -0.0281*** |\n| Increase Amount | wpsp | wpsp | 0.000469 | 0.00695*** |\n| nonEZpay | Ezpay | _EZpay_1 | -0.454*** | -0.386*** |\n| Vol | DM | _source_2 | source==DM | 0.591*** | 0.502*** |\n| | EVENTS | _source_3 | source==EVENTS | 0.629*** | 0.565*** |\n| | FSI | _source_4 | source==FSI | 0.551*** | 0.465*** |\n| | OTM | _source_5 | source==OTM | 0.472*** | 0.368*** |\n| | OTHER | _source_6 | source==Other | 0.968*** | 0.817*** |\n| | TV | _source_7 | source==TV | 0.782*** | 0.706*** |\n| | WEB | _source_8 | source==WEB | 0.441*** | 0.436*** |\n| | WEB_NYTD | _source_9 | source==WEB_NYTD | 2.308*** | 1.943*** |\n| | WEB_Other | _source_10 | source==WEB_Other | 1.313*** | 1.281*** |\n| | WEB_PDSRCH | _source_11 | source==WEB_PDSRCH | 2.024*** | 1.730*** |\n| | WEB_REGIEMAIL | _source_12 | source==WEB_REGIEMAIL | 2.051*** | 1.639*** |\n| | WEB_SOCIAL | _source_13 | source==WEB_SOCIAL | 2.680*** | 2.408*** |\n| | Failures in the trailing 28 | fail_last_28_1 | -0.000621*** |\n| | Starts in the trailing quarter | starts_last_q | 0.0000110*** |\n| | Individual avg Comps versus Zip avg | sub_zip_comp_28_2 | 0.000491*** |\n| Dig Eng. Score = 1 | use_bucket=2 | use_bucket=2 | 0.0435** | -0.264*** |\n| Dig Eng. Score = 2 | use_bucket=3 | use_bucket=3 | -0.254*** | -0.316*** |\n| Dig Eng. Score = 3 | use_bucket=4 | use_bucket=4 | -0.302*** | -0.382** |\n| Dig Eng. Score = 4 | use_bucket=5 | use_bucket=5 | -0.324*** | -0.408*** |\n| Dig Eng. Score = 5 | use_bucket=6 | use_bucket=6 | -0.382*** | -0.415*** |\n\nChurn risk decreases with increased subscription rates\n\nSource==WEB show the highest churn risk, voluntary lowest\n\nGreater number of starts in trailing quarter increases churn risk\n\nChurn risk decreases with higher levels of digital engagement\n\nThe chart shows the influence of individual variables on the churn score.\n\nOut of all variables, the 52-week term length has the largest contribution to decreasing churn risk, and the WEB_SOCIAL start source is largest contribution to increasing churn risk.\n\nActual stop rates are tracked, along with predicted risk, to validate the model.\n\nStop rates often spike in the upper 10-20% of the Predicted Churn Score. 10-20% has a higher stop rate.\n\nThese pockets are often where the largest percentage reduction in churn rates can be obtained with application.\n\nCHURN CASE STUDIES\n\nTest: $10 gift card issued upon receipt of payment (high churn/high CLV, $10.50/wk).\n\nResults: Short lived positive impact on retention that disappears over several renewals.\n\nInsight: Gifts do little to reinforce brand value on core subscribers.\n\nTest: Greeting card sent at time of expiration (high churn/high CLV - $10.50/wk)\n\nResults: Short and long term positive retention impact\n\nInsight: Messages that reinforce brand value have positive effects on core subs\n\nTest: Greeting card or value letter sent at expire (high churn/mid CLV - $3.75/wk)\n\nResults: Both messages had positive retention impacts, value letter outperforms\n\nInsight: Highlighting importance of journalism reinforces value to subscriber\n\nResults: Value letter and greeting cards showed the largest positive retention impact. Merchandise and gift cards did not improve retention.\n\nInsight: High Cost Incentives are not necessarily the most effective.\n\nIMPACT BY CHURN GROUP\n\nAggregated Retention Impact by Churn Group\n\nResults: Retention improvements positively correlated with churn risk\n\nInsight: Highest ROIs observed on subs with highest estimated churn risk\n\nSales channels attract customers with different levels of engagement:\n\n- **Direct sales** to customers that go to the subscription page directly are most engaged.\n- **Metered customers** have next highest engagement.\n- **Premium/restricted content sales** have the lowest engagement.\n\nRetention of these customers reflects their engagement levels at time of the subscription purchase.\n\nChallenge – increase engagement following the sale, particularly those from premium content.\n\nACCOLADES\n\nBy Matt Lindsay, President\n\nLearn how to make data work for you, grow valuable relationships, and empathize with your customers.\n\nThe book is available in English, Dutch, and German and offered on Amazon.com\n\nBIGGIES GLOBAL AWARDS 2019\n\n1st PLACE\nExcellence in Data Strategy\nTransformative Economics of Content\n\n1st PLACE\nExcellence in Predictive Analytics\nMake Your Paywall an Intelligent Paywall™\n\nMay 2019 | San Francisco\n\nBIGGIES LONDON 2018 Awards\n\nAWARD of EXCELLENCE\nData-Driven Business Process Efficiency\nSales Intelligence Platform\n\nAWARD of EXCELLENCE\nData Strategy\nSales Intelligence Platform\n\nNovember 2018 | London\n\nBIGGIES GLOBAL AWARDS 2018\n\n1st PLACE\nExcellence in Data-Driven Technology\nListener™ Intelligent Paywall™\n\nAWARD of EXCELLENCE\nCreativity in a Data-Driven Project\nAdvertising Rate Calculator Dashboard\n\nMay 2018 | New York City\n\nFollow up questions?\n\nReach out to Matt at email@example.com\n\nUSA\n1215 Hightower Trail\nBuilding A, Suite 100\nAtlanta, GA 30350\n\nEUROPE\nBasisweg 30\n1043 AP\nAmsterdam, Netherlands\n\n770.993.4111\nmathereconomics.com"},"books_score":{"kind":"number","value":0.5379947423934937,"string":"0.537995"}}},{"rowIdx":8693,"cells":{"content":{"kind":"string","value":"Sensitive and accurate peptide identification with Mascot Percolator\n\nMarkus Brosch\nemail@example.com\n\nTerminology: FPR, FDR, PEP\n\nL. Käll, J. D. Storey, M. J. MacCoss, W. S. Noble, *J Proteome Res* 7, **29** (2008).\nL. Käll, J. D. Storey, M. J. MacCoss, W. S. Noble, *J Proteome Res* 7, **40** (2008).\nM. Brosch, J. Choudhary, in *Scoring and validation of tandem MS peptide identification methods*, Eds. (Humana Press, 2009).\n\nTerminology: FDR & PEP\n\nFrequency\n\nScore\n\nTotal PSMs\nIncorrect PSMs\nCorrect PSMs\n\nFPR = B/(B+B')\nFDR = B/A = (Σ PEP_i)/A\nPEP = b/a\n\nL. Käll, J. D. Storey, M. J. MacCoss, W. S. Noble, *J Proteome Res* 7, 29 (2008).\nL. Käll, J. D. Storey, M. J. MacCoss, W. S. Noble, *J Proteome Res* 7, 40 (2008).\nM. Brosch, J. Choudhary, in Scoring and validation of tandem MS peptide identification methods, Eds. (Humana Press, 2009).\n\nTerminology: FDR vs q-value\n\nAccepted peptide-spectrum matches\n\nFDR / q-value\n\nJ. D. Storey, R. Tibshirani, Proc Natl Acad Sci U S A 100, 9440 (2003).\nFigure: L. Käll, J. D. Storey, M. J. MacCoss, W. S. Noble, J Proteome Res 7, 29 (2008).\n\nTarget / Decoy database searching\n\nDensity\n\nScore cutoff\n\nCorrect PSMs\n\nIncorrect PSMs\n\nTarget/Decoy concept: R. E. Moore, M. K. Young, T. D. Lee, J Am Soc Mass Spectrom 13, 378 (2002).\n\nTarget / Decoy database searching\n\nL. Käll, J. D. Storey, M. J. MacCoss, W. S. Noble, *J Proteome Res* 7, 29 (2008).\n\nAccurate q-values (FDR) and PEPs\n\nq-value or PEP\n\nMascot Score\n\nThink FDR!\n\nqvality software package: L. Käll, J. D. Storey, W. S. Noble, *Bioinformatics* 24, i42 (2008).\n\nMascot score\n\nMascot score = $-10 \\log_{10}(P)$\n\n$P = 10^{-(\\text{Mascot score} / 10)}$\n\nExample:\nA 1% probability that the peptide spectrum match is a random event would translate into a Mascot score of 20.\n\n‘Theoretical’\n\nMIT\nMascot Identity Threshold\n\nMIT = $-10 \\log_{10}(P)$\n\nExample:\nIf there are 5000 precursor matches, a 1 in a 20 chance of getting a false positive match is a probability of $P = 1 / (20 \\times 5000 \\times n)$\n\nhttp://www.matrixscience.com/pdf/optimization.pdf\nhttp://www.matrixscience.com/pdf/2005WKSHP4.pdf\n\n‘Empirical’\n\nMHT\nMascot Homology Threshold\n\nnumber of entries\n\nscore\n\nWednesday, 10 June 2009\n\nSemi-supervised learning for peptide identification from shotgun proteomics datasets\n\nLukas Käll¹, Jesse D Canterbury¹, Jason Weston², William Stafford Noble¹,³ & Michael J MacCoss¹\n\n- Good news: convincing method\n- Bad news: only available for Sequest\n- Good news: command line interface with generic input and output formats, so we can extend it for use with Mascot\n\nSupport Vector Machine\n\nFigure: http://en.wikipedia.org/wiki/Support_vector_machine\n\nPercolator\n\nKäll, L., Canterbury, J. D., Weston, J., Noble, W. S., & MacCoss, M. J. (2007). *Nature Methods*\n\nMascot Percolator\n\nMascot Parser\n\nTarget Protein Database\n\nTarget PSMs\n\nDecoy PSMs\n\nFeature Calculator\n\nTarget Features\n\nDecoy Features\n\nPercolator\n\nFDR Filter\n\nClassifier\n\nSVM\n\nScored PSMs\n\nInitial scoring function: Mascot score\n\nMascot Auto-Decoy function\n\nM. Brosch, L. Yu, T. Hubbard, J. Choudhary, *J Proteome Res* (2009).\n\nMascot Percolator Features\n\n(a) Peptide Matching Scores (Mascot score, Peptide score [1])\n(b) Peptide properties (mass, charge, mc, var mods)\n(c) Delta mass, absolute delta mass, delta mass accounting for incorrect peak detection ($^{13}$C)\n(d) Fragment delta mass, absolute fragment delta mass\n(e) Total intensity, matched intensity, relative matched intensity\n(f) Fraction of ions matched (per ion series)\n(g) Sequence coverage (per ion series)\n(h) Intensity matched (per ion series)\n(i) Retention time where available (see talk by Lukas Käll, WOE 3:10 pm)\n\n[1] S. A. Beausoleil, J. Villen, S. A. Gerber, J. Rush, S. P. Gygi, *Nat Biotechnol* **24**, 1285 (2006).\n\nMascot Percolator\n\nMascot Parser\n\nTarget Protein Database\n\nTarget PSMs\n\nDecoy PSMs\n\nFeature Calculator\n\nTarget Features\n\nDecoy Features\n\nPercolator\n\nFDR Filter\n\nClassifier\n\nSVM\n\nScored PSMs\n\nInitial scoring function: Mascot score\n\nMascot Auto-Decoy function\n\nM. Brosch, L. Yu, T. Hubbard, J. Choudhary, *J Proteome Res* (2009).\n\nMascot score vs Percolator PEPs\n\nMascot vs Percolator score density\n\n-10log10(PEP)\n\nMascot score vs PEP\n\nArbitrary score\n\nMascot score\n\nWednesday, 10 June 2009\n\nROC comparison\n\nNumber of estimated correct PSMs\n\nq-value\n\nMP\nMHT\nMIT\n\nThink FDR\n\nM. Brosch, L. Yu, T. Hubbard, J. Choudhary, *J Proteome Res* (2009).\n\nMascot vs Sequest Percolator\n\nNumber of estimated correct PSMs\n\nq-value\n\n- Mascot Percolator\n- Sequest Percolator\n\nAll of Peptide Atlas Mouse\n\n% increase of PSMs with MP over MHT, MIT, MScore at 1% q-value\n\nMHT MIT MScore\n\nEvaluate q-value accuracy\n\nFDR evaluation (MP v1.08 + P v1.09)\n\nStandard error negligible\n\n- LTQ\n- LTQ–FT 200 ppm\n- LTQ–FT 50 ppm\n- LTQ–FT 20 ppm\n- LTQ–FT Ultra\n\nWednesday, 10 June 2009\n\nMascot Percolator software package\n\n• Simple command line interface:\n\n```\njava -cp MascotPercolator.jar cli.MascotPercolator\n -target 11083\n -decoy 11084\n -out 11083-11084\n -rankdelta 1\n -newDat\n```\n\n• Tested with Mascot 2.2; limited experience with versions <= 2.1\n• Runtime: 10-150 spectra per second\n• Memory requirements typically 1-2 GB for up to 100k spectra.\n Largest Mascot search processed was 350k spectra which required 6GB of memory.\n\nDistributing Mascot Percolator Jobs\n\nDB server ↔ MP server\n\nStatus page\n\nActive nodes\n\n| # | host | status | user description |\n|----|------------|--------|------------------------------------------------------|\n| 1 | mascot 1-10| idle | |\n| 2 | mascot 1-08| idle | |\n| 3 | mascot 1-09| idle | |\n| 4 | mascot 1-07| idle | |\n\nRegistered nodes\n\nLog\n\n| id | target decoy | status | user description | result file prefix | spectra | psm (qval<1E) | pps | protein c support |\n|-----|--------------|--------|------------------------------------------------------|--------------------|---------|---------------|-----|------------------|\n| 563 | 12928 12927 | done | nrb8 GA_PeptideAtlas_all_RBC_membrane.mgf evni target | 12928-12927 | 46994 | 2661 | 0.907 | false |\n| 563 | 12923 12924 | done | nrb8 GA_PeptideAtlas_all_MouseLiver_Cryo.mgf evni | 12923-12924 | 17227 | 6067 | 0.612 | false |\n| 562 | 12922 12919 | done | nrb8 GA_PeptideAtlas_all_Placenta_NUC_Triton.mgf evni target | 12922-12919 | 129186 | 5633 | 0.933 | false |\n| 561 | 12921 12920 | done | nrb8 GA_PeptideAtlas_all_MouseLiver_Nuc.mgf evni | 12921-12920 | 17655 | 5722 | 0.933 | false |\n| 560 | 12918 12917 | done | nrb8 GA_PeptideAtlas_all_Placenta_NUC.mgf evni target | 12918-12917 | 156172 | 214 | 0.933 | false |\n| 559 | 12905 12906 | done | nrb8 GA_PeptideAtlas_all_Liver_NUC.mgf evni target | 12905-12906 | 35597 | 423 | 0.933 | false |\n| 558 | 12913 12912 | done | nrb8 GA_PeptideAtlas_all_Placenta_micro.mgf evni target | 12913-12912 | 121967 | 1381 | 0.933 | false |\n| 557 | 12913 12914 | done | nrb8 GA_PeptideAtlas_all_Placenta_micro_Triton.mgf evni target | 12913-12914 | 74951 | 6451 | 0.933 | false |\n| 556 | 12895 12896 | done | nrb8 GA_PeptideAtlas_all_Lung_NE.mgf evni target | 12895-12896 | 189902 | 14825 | 0.903 | false |\n| 547 | 12870 12872 | done | nrb8 GA_PeptideAtlas_all_Liver_NUC.mgf evni target | 12870-12872 | 186619 | 12996 | 0.91 | false |\n| 546 | 12865 12866 | done | nrb8 GA_PeptideAtlas_all_Liver_Micro.mgf evni target | 12865-12866 | 215183 | 16915 | 0.91 | false |\n| 545 | 12860 12862 | done | nrb8 GA_PeptideAtlas_all_Liver_Cryo.mgf evni target | 12860-12862 | 213270 | 19148 | 0.92 | false |\n| 538 | 12815 12817 | done | nrb8 GA_Internal_WTNE01Nco2-4b_PT_merged evni | 12815-12817 | 151654 | 33714 | 0.708 | false |\n| 534 | 12812 12813 | done | nrb8 GA_PeptideAtlas_nuclear/20040921-24-evni target | 12812-12813 | 39314 | 818 | 0.97 | false |\n| 533 | 12809 12810 | done | nrb8 GA_PeptideAtlas_nuclear/20040921-24-evni target | 12809-12810 | 39408 | 686 | 0.975 | false |\n\nSubmit Job\n\nfile info, parameters info, statistics\n\nAcknowledgements\n\n- Lukas Käll (Stockholm University) WOE 3:10 pm\n- Erik Deutsch (Institute of Systems Biology)\n- Jyoti Choudhary & Tim Hubbard (Sanger)\n- Members of team 17 and 119, in particular Lu Yu (Sanger)\n- Matrix Science\n- Wellcome Trust for funding\n\nLukas Käll - WOE 3:10 pm\n\nMarkus Brosch - MPB 063 - firstname.lastname@example.org\n\nMascot Percolator Website:\n\nhttp://www.sanger.ac.uk/Software/analysis/MascotPercolator/\n\nhttp://tinyurl.com/mascotpercolator/"},"books_score":{"kind":"number","value":0.9545634388923645,"string":"0.954563"}}},{"rowIdx":8694,"cells":{"content":{"kind":"string","value":"Devices for occluding a patient's ascending aorta and delivering oxygenated blood to the patient\n\nA device (2) for delivering oxygenated blood and occluding the ascending aorta is provided. The device (2) has a blood flow lumen (12) with a movable portion (18). The movable portion (18) is movable from a position contained within a body (4) of the device (2) to a position which extends outwardly from the device (2). The movable portion (18) is made of a tube of flexible material and everts when moving to the extended position.\n\n| Category | Citation of document with indication, where appropriate, of relevant passages | Relevant to claim | CLASSIFICATION OF THE APPLICATION (Int.Cl.7) |\n|----------|-----------------------------------------------------------------------------|------------------|--------------------------------------------|\n| X | US 6 090 096 A (ST GOAR FREDERICK G ET AL.) 18 July 2000 (2000-07-18) * column 12, line 11 - line 33; figure 11 * --- | 1,2,6-10 | A61M1/36 A61B17/12 |\n| A | EP 1 025 876 A (CONVERGENZA AG) 9 August 2000 (2000-08-09) * column 4, line 23 - column 5, line 40 * --- | 1-6 | |\n| X | US 6 090 097 A (PASTRONE GIOVANNI ET AL.) 18 July 2000 (2000-07-18) * column 14, line 66 - column 17, line 35; figures 1,3 * --- | 1-3,5-10 | |\n| X | WO 99/37202 A (HEARTPORT INC) 29 July 1999 (1999-07-29) * page 14, line 8 - page 16, line 15; figures 8,23,33-35 * --- | 1,2,6-10 | |\n| A | EP 1 060 758 A (MEDTRONIC INC) 20 December 2000 (2000-12-20) * column 5, line 10 - column 7, line 20 * --- | 1,2,5-10 | TECHNICAL FIELDS SEARCHED (Int.Cl.7) |\n| X | US 6 176 851 B1 (MAAHS TRACY D ET AL.) 23 January 2001 (2001-01-23) * column 14, line 23 - line 61; figure 18 * --- | 11,12 | A61M |\n| X | US 6 086 557 A (MOREJOHN DWIGHT P ET AL.) 11 July 2000 (2000-07-11) * figure 1 * --- | 11,12 | |\n\nThe present search report has been drawn up for all claims\n\nPlace of search: THE HAGUE \nDate of completion of the search: 14 April 2004 \nExaminer: Kroeders, M\n\nCATEGORY OF CITED DOCUMENTS\nX: particularly relevant if taken alone\nY: particularly relevant if combined with another document of the same category\nA: technological background\nO: non-written disclosure\nP: intermediate document\nT: theory or principle underlying the invention\nE: earlier patent document, but published on, or after the filing date\nD: document cited in the application\nL: document cited for other reasons\n& : member of the same patent family, corresponding document\n\nCLAIMS INCURRING FEES\n\nThe present European patent application comprised at the time of filing more than ten claims.\n\n☐ Only part of the claims have been paid within the prescribed time limit. The present European search report has been drawn up for the first ten claims and for those claims for which claims fees have been paid, namely claim(s):\n\n☐ No claims fees have been paid within the prescribed time limit. The present European search report has been drawn up for the first ten claims.\n\nLACK OF UNITY OF INVENTION\n\nThe Search Division considers that the present European patent application does not comply with the requirements of unity of invention and relates to several inventions or groups of inventions, namely:\n\nsee sheet B\n\n☒ All further search fees have been paid within the fixed time limit. The present European search report has been drawn up for all claims.\n\n☐ As all searchable claims could be searched without effort justifying an additional fee, the Search Division did not invite payment of any additional fee.\n\n☐ Only part of the further search fees have been paid within the fixed time limit. The present European search report has been drawn up for those parts of the European patent application which relate to the inventions in respect of which search fees have been paid, namely claims:\n\n☐ None of the further search fees have been paid within the fixed time limit. The present European search report has been drawn up for those parts of the European patent application which relate to the invention first mentioned in the claims, namely claims:\n\nThe Search Division considers that the present European patent application does not comply with the requirements of unity of invention and relates to several inventions or groups of inventions, namely:\n\n1. Claims: 1-10\n\nDevice for occluding a patient’s ascending aorta and delivering oxygenated blood to the patient, comprising:\n A) a body\n B) an expandable member\n C) a blood flow lumen with a portion movable relative to the body\n\n2. Claims: 11, 12\n\nDevice for occluding a patient’s ascending aorta, comprising:\n A) an L-shaped catheter\n B) an expandable member\n D) a mounting ring with indicator for the direction of catheter (A)\n\n## ANNEX TO THE EUROPEAN SEARCH REPORT\n\nON EUROPEAN PATENT APPLICATION NO. EP 02 25 2590\n\nThis annex lists the patent family members relating to the patent documents cited in the above-mentioned European search report. The members are not contained in the European Patent Office EDP file on. The European Patent Office is in no way liable for these particulars which are merely given for the purpose of information.\n\n14-04-2004\n\n| Patent document cited in search report | Publication date | Patent family member(s) | Publication date |\n|---------------------------------------|------------------|-------------------------|------------------|\n| US 6090096 A | 18-07-2000 | AU 744554 B2 | 28-02-2002 |\n| | | AU 7151198 A | 13-11-1998 |\n| | | CA 2288906 A1 | 29-10-1998 |\n| | | EP 1011782 A1 | 28-06-2000 |\n| | | WO 9847558 A1 | 29-10-1998 |\n| EP 1025876 A | 09-08-2000 | DE 19904896 A1 | 10-08-2000 |\n| | | EP 1025876 A2 | 09-08-2000 |\n| | | JP 2000229127 A | 22-08-2000 |\n| US 6090097 A | 18-07-2000 | US 6231544 B1 | 15-05-2001 |\n| | | US 6589264 B1 | 08-07-2003 |\n| | | US 6592546 B1 | 15-07-2003 |\n| | | US 2002077596 A1 | 20-06-2002 |\n| | | US 6176851 B1 | 23-01-2001 |\n| | | US 6217548 B1 | 17-04-2001 |\n| | | US 2004064092 A1 | 01-04-2004 |\n| | | US 2001001114 A1 | 10-05-2001 |\n| | | US 6048331 A | 11-04-2000 |\n| | | AU 3122197 A | 05-12-1997 |\n| | | CA 2254831 A1 | 20-11-1997 |\n| | | EP 0897288 A1 | 24-02-1999 |\n| | | WO 9742879 A1 | 20-11-1997 |\n| WO 9937202 A | 29-07-1999 | US 6159178 A | 12-12-2000 |\n| | | AU 752773 B2 | 26-09-2002 |\n| | | AU 2334599 A | 09-08-1999 |\n| | | CA 2284752 A1 | 29-07-1999 |\n| | | EP 0983015 A2 | 08-03-2000 |\n| | | WO 9937202 A2 | 29-07-1999 |\n| | | US 2001041858 A1 | 15-11-2001 |\n| | | US 2002128597 A1 | 12-09-2002 |\n| | | US 2002151870 A1 | 17-10-2002 |\n| | | US 2001056260 A1 | 27-12-2001 |\n| | | US 6589206 B1 | 08-07-2003 |\n| | | US 2002072708 A1 | 13-06-2002 |\n| EP 1060758 A | 20-12-2000 | EP 1060758 A1 | 20-12-2000 |\n| US 6176851 B1 | 23-01-2001 | US 6048331 A | 11-04-2000 |\n| | | US 6231544 B1 | 15-05-2001 |\n| | | US 2002077596 A1 | 20-06-2002 |\n| | | US 6217548 B1 | 17-04-2001 |\n| | | US 2004064092 A1 | 01-04-2004 |\n| | | US 2001001114 A1 | 10-05-2001 |\n| | | AU 742149 B2 | 20-12-2001 |\n\nFor more details about this annex: see Official Journal of the European Patent Office, No. 12/82\n\nThis annex lists the patent family members relating to the patent documents cited in the above-mentioned European search report. The members are as contained in the European Patent Office EDP file on. The European Patent Office is in no way liable for these particulars which are merely given for the purpose of information.\n\n| Patent document cited in search report | Publication date | Patent family member(s) | Publication date |\n|---------------------------------------|------------------|-------------------------|------------------|\n| US 6176851 B1 | | AU 1829199 A | 05–07–1999 |\n| | | CA 2315172 A1 | 24–06–1999 |\n| | | EP 1039943 A1 | 04–10–2000 |\n| | | WO 9930766 A1 | 24–06–1999 |\n| | | US 6090097 A | 18–07–2000 |\n| | | US 6592546 B1 | 15–07–2003 |\n| | | US 6589264 B1 | 08–07–2003 |\n| | | AU 3122197 A | 05–12–1997 |\n| | | CA 2254831 A1 | 20–11–1997 |\n| | | EP 0897288 A1 | 24–02–1999 |\n| | | WO 9742879 A1 | 20–11–1997 |\n\nUS 6086557 A 11–07–2000 NONE\n\nFor more details about this annex: see Official Journal of the European Patent Office, No. 12/82"},"books_score":{"kind":"number","value":0.6254692673683167,"string":"0.625469"}}},{"rowIdx":8695,"cells":{"content":{"kind":"string","value":"MTM800\nTETRA 車載台對講機\n功能使用手冊\n\n| 章節 | 頁碼 |\n|------|------|\n| 一般資訊 | 1 |\n| 安全資訊 | 1 |\n| 廢棄處置資訊 | 1 |\n| 版權資訊 | 2 |\n| 特定產品資訊 | 2 |\n| 圖示慣例 | 3 |\n| 開始之前 | 4 |\n| 如何使用本手冊 | 4 |\n| 控制項與指示燈 | 5 |\n| 螢幕顯示 | 7 |\n| LED 狀態指示燈 | 9 |\n| 開機/關機 | 10 |\n| 按鍵概觀 | 12 |\n| 首頁模式畫面 | 17 |\n| 時間與日期 | 17 |\n| 對講機停用/啓用 | 18 |\n| 對講機永久停用 | 18 |\n| 撥出電話 | 18 |\n| VOX 控制 | 19 |\n| 接聽來電 | 19 |\n| 忙線用戶搶佔 (BUP) | 19 |\n| 優先通話 (PPC) | 20 |\n| 廣播呼叫 | 21 |\n| 環場收聽 (AL) | 22 |\n| 取消來電 | 22 |\n| 使用通話中功能 | 22 |\n| 隱密模式 | 23 |\n| 單站集群服務 | 23 |\n| 調低螢幕亮度 | 24 |\n| 調整音量 | 24 |\n| 啓動/關閉聲音和指示燈提示 | 24 |\n| 封包資料 | 25 |\n| 保養您的 MTM800 | 25 |\n\n| 章節 | 頁碼 |\n|------|------|\n| TMO 群組呼叫 | 26 |\n| 一般說明 | 26 |\n| 選擇通話群組 | 27 |\n| 在通話中/接聽來電時變更通話群組 | 30 |\n| 選擇範圍 | 31 |\n| 啓動/停用掃瞄 | 31 |\n| 進行群組呼叫 | 31 |\n| 接聽群組呼叫 | 32 |\n| 傳輸抑制 | 34 |\n| 動態指定群組號碼 (DGNA) | 35 |\n| DMO 群組呼叫 | 37 |\n| 一般說明 | 37 |\n| 選擇通話群組 | 37 |\n| 在通話中/接聽來電時變更通話群組 | 37 |\n| 從 TMO 切換至 DMO 或從 DMO 切換至 TMO | 38 |\n| 閘道/中繼器選擇 | 38 |\n| 進行 DMO 群組呼叫（MS 對 MS） | 41 |\n| 透過閘道進行 DMO 群組呼叫 | 41 |\n| 透過中繼器進行 DMO 群組呼叫 | 42 |\n| 透過閘道和中繼器進行 DMO 群組呼叫 | 42 |\n| 接聽 DMO 群組呼叫 | 43 |\n| DMO 私人通話 | 44 |\n| 接聽緊急群組呼叫 | 44 |\n| 私人通話 | 45 |\n| 一般說明 | 45 |\n| 進入私人模式 | 45 |\n| 輸入私人號碼 | 46 |\n| 在 TMO 中撥打私人通話 | 47 |\n| 在 TMO 中撥打私人全雙工通話 | 47 |\n| 在 TMO 中接聽私人通話 | 47 |\n| 在 TMO 中接聽私人全雙工通話 | 48 |\n| 在 DMO 中撥打私人通話 | 48 |\n| 撥號時有來電 | 49 |\n| 撥打私人 PPC（優先呼叫） | 49 |\n| 通話佇列 | 50 |\n\n電話與 PABX 通話 ........................................... 51\n一般說明 .................................................. 51\n撥打電話或 PABX 通話 .................................... 51\n撥號時有來電 ............................................. 53\n接聽電話或 PABX 通話 .................................... 54\n\n緊急情況模式 .............................................. 55\n一般說明 .................................................. 55\n進入 TMO 或 DMO .......................................... 56\n進入或退出緊急模式 ....................................... 56\n靜音緊急呼叫 .............................................. 57\n變更範圍或通話群組 ....................................... 57\nTMO 中的緊急呼叫 ......................................... 57\nDMO 中的緊急呼叫 ......................................... 60\n\nGPS 定位服務 .............................................. 61\n一般說明 .................................................. 61\n增強 GPS 效能 .............................................. 62\nGPS 啓用/停用 .............................................. 62\n進入 GPS 定位服務 ......................................... 63\n\n功能表 ..................................................... 65\n進入功能表選項 ............................................. 65\n退出功能表選項 ............................................. 65\n退出功能表 .................................................. 65\n功能表選項清單 ............................................. 66\n訊息 ....................................................... 68\n電話簿 ..................................................... 68\n保密 ....................................................... 71\n設定 ....................................................... 75\n本機號碼 ................................................... 82\n網絡 ....................................................... 82\n掃瞄 ....................................................... 84\n通話記錄 ................................................... 87\n地點定位 ................................................... 88\n封包資料 ................................................... 88\n\n| 章節 | 頁碼 |\n|------|------|\n| 訊息 | 90 |\n| 一般說明 | 90 |\n| 進入訊息子功能表 | 90 |\n| 傳送狀態訊息 | 91 |\n| 使用收件箱 | 92 |\n| 傳送文字訊息 | 94 |\n| 疑難排解 | 99 |\n| 鈴聲 | 102 |\n| 索引 | 105 |\n| 快速參考指南 | 109 |\n\nMOTOROLA 和 M 造型標誌均已向美國專利商標局註冊。所有其他產品或服務的名字均為各自所有者的資產。\n\n© 2007 – 2008 摩托羅拉公司\n版權所有\n\n一般資訊\n\n安全資訊\n\n在使用這些產品之前，請先閱讀本對講機隨附的產品安全與 RF 能量暴露手冊（摩托羅拉出版品編號 6866537D37（適用於歐洲、中東和非洲）或 6804112J96/6804113J25（適用於亞太地區））中的操作說明以策安全。\n\n這些配件僅供職業用途，以符合 ICNIRP RF 能量暴露限制。在使用這些產品之前，請先閱讀對講機的產品安全與 RF 能量暴露手冊中所包含的 RF 能量注意事項以及操作指示，以確保遵循 RF 能量暴露限制。\n\n請將本使用手冊及產品安全與 RF 能量暴露手冊妥善保存，若將配件交由他人使用，應一併提供這些手冊。\n\n廢棄處置資訊\n\n歐盟的電器及電子產品廢棄物處理指令 (WEEE) 規定銷入歐盟國家的產品（或某些情況下，在外包裝上）必須加上垃圾桶打叉的標籤。依照 WEEE 指令的定義，這個垃圾桶打叉的標籤表示歐盟國家的客戶及使用者不應將電器及電子設備或配件當成家庭廢棄物處理。\n\n歐盟國家的客戶及使用者應與當地設備供應商代理或維修中心聯絡，以取得有關當地廢棄物回收系統的相關資訊。\n\n版權資訊\n\n本手冊中所述的摩托羅拉產品可能包含具摩托羅拉版權的電腦程式，儲存於半導體記憶體或其他媒體中。美國和其他國家的法律承認並保護摩托羅拉對擁有版權的電腦程式享有專有權，包括但不限於以任何形式複製或重製具有版權的電腦程式。因此，在沒有獲得摩托羅拉公司明確的書面許可條件下，不得以任何方式對此使用手冊描述的摩托羅拉產品中包含的任何具有摩托羅拉版權的電腦程式進行複製、重製、還原工程或散佈。此外，購買摩托羅拉的產品並不能視為是直接或者暗示，獲得摩托羅拉的版權許可、專利或者專利申請，惟在產品銷售中依法規定為一般非專屬版權的授權除外。\n\n特定產品資訊\n\n- 最大 RF 功率 3 瓦特\n- 最大揚聲器負載 4 歐姆下 10 瓦特\n- 天線阻抗 50 歐姆\n- 周圍溫度範圍 -30 °C 到 +60 °C\n\n警告 如果本對講機在使用中，其表面溫度最高可達 70 °C。\n請勿觸碰高溫表面\n\n- 操作時間 持續 / 間歇\n\n注意 一般而言，對講機的傳輸和接收時間（操作循環時間）由通訊系統決定。本對講機具有溫度控制保護機制，在超載（超出系統規定於高溫下長時間使用）時溫度控制保護會切斷 RF 輸出功率，因而使對講機的涵蓋範圍變小。\n\n圖示慣例\n\n本文件旨在提供讀者更易懂的視覺提示。說明文件中使用以下圖示。以下說明這些圖示的相關意義。\n\n「警告」標語加上安全圖示表示若未遵照該資訊指示，可能會導致死亡或嚴重人員傷害，或對產品造成嚴重損害。\n\n「小心」標語加上安全圖示表示若未遵照該資訊指示，可能會導致輕度或中度人員傷害，或對產品造成嚴重損害。\n\n「小心」標語可能會單獨使用（未加上安全圖示），表示會有與產品無關的受損或傷害風險。\n\n「注意」則包含比其前段文字更重要的資訊，例如例外或事先具備的條件。此外，也會告知讀者其他相關資訊的位置，提醒讀者如何完成動作（例如，當該動作不是目前程序的一部分時），或告知讀者某項資訊在畫面上的位置。「注意」並無相關的警告等級。\n\n開始之前\n\n恭喜您購買摩托羅拉 MTM800。增強的 TETRA 功能以及最新技術可協助您與所有工作和個人連絡人隨時保持連絡。\n您可以使用英文、簡體中文、繁體中文或您服務供應商定義的語言來操作 MTM800。出廠預設設定為英文。如需更多資訊，請參閱第 76 頁的「設定螢幕的使用語言」。\n\n如何使用本手冊\n\n本手冊說明 MTM800 的出廠設定與預設功能。\n您的服務供應商或機構可能已針對您個人的需求自訂 MTM800 對講機，以最佳化對講機的使用。請洽詢您的服務供應商或機構，以瞭解其自訂與本手冊說明之間的差別。本手冊使用下列特殊標記來凸顯某些資訊或項目：\n\n| 範例 | 說明 |\n|------|------|\n| Mode 或者是 | 使用按鍵符號或粗體快捷鍵功能來表示按鍵動作。 |\n| Menu 2 2 1 | 把文數字鍵設為進入所需子功能表的捷徑。在本例中，請依序（而非同時）按下 Menu 2 abc 1 !。 |\n| 2 電話簿 | 反白文字表示您的選擇。 |\n| 狀態已傳送 | MTM800 螢幕中顯示的資訊會以特殊字體表示。 |\n| 注意 | 「注意」中包含與該項目功能相關的其他資訊。 |\n| 6 <用戶定義> | 指示您服務供應商設定的提示訊息。 |\n\n控制項與指示燈\n\n1. 開/關按鈕\n2. LED 指示燈\n 紅色、橘色、綠色\n3. 顯示圖示\n4. 文數字顯示\n5. 文數字鍵盤\n6. 背光鍵\n7. 功能鍵\n8. 外部警報鍵\n9. 功能表鍵\n10. 傳送/結束鍵\n11. 快捷鍵\n12. 導覽鍵\n 上、下、左、右\n13. 模式鍵\n14. 緊急鍵\n15. 麥克風接頭\n16. 音量旋鈕\n17. PTT\n18. 麥克風\n\n| 項目 | 說明 |\n|------|------|\n| 1 | **開/關按鈕** \n將 MTM800 開機或關機。（請參閱第 10 頁。） |\n| 2 | **LED 指示燈** \n指出服務狀態。（請參閱第 9 頁。） |\n| 3 | **顯示圖示** \n顯示其他資訊和 MTM800 狀態。（請參閱第 7 頁。） |\n| 4 | **文數字顯示** \n背光檢視最多 4 行字或數字（每行最多 16 個字元或數字）。 |\n| 5 | **文數字鍵盤** \n輸入數字和字母字元。（請參閱第 14 頁）。這些按鍵的功能由服務供應商設定。（請參閱第 16 頁。） |\n| 6 | **背光鍵** \n降低和提高對講機的背光亮度（4 種亮度選擇）。 \n（請參閱第 24 頁。） |\n| 7 | **功能鍵** \n這些按鍵的功能由服務供應商設定。（請參閱第 16 頁。） |\n| 8 | **外部警報鍵** \n用來啓用或停用外部警報功能（聲音和指示燈）。 \n（請參閱第 24 頁。） |\n| 9 | **功能表鍵** \n按下此鍵即可顯示功能表選項。使用導覽鍵來捲動。 \n（請參閱第 13 頁。） |\n| 10 | **傳送/結束鍵** \n按下此鍵即可撥打全雙工通話、傳送文字和狀態訊息，以及結束電話通話、PABX 通話、全雙工以及半雙工私人通話。 |\n| 11 | **快捷鍵** \n按下此鍵即可選擇出現在螢幕上第 4 行中位於向左或向右鍵上方的選項。（請參閱第 13 頁。） |\n| 12 | **導覽鍵** \n按下此鍵即可在選項和清單（例如訊息或電話簿清單）中向上或向下移動。 |\n\n| 項目 | 說明 |\n|------|------|\n| 13 | 模式鍵 \n選擇電話、PABX、私人或群組模式。（請參閱第 12 頁。） |\n| 14 | 緊急鍵 \n啓動緊急模式並傳送緊急通報。（請參閱第 13 頁。） |\n| 15 | 麥克風接頭 \n配備 PTT 的掌上型或桌上型麥克風或電話手機接頭。 |\n| 16 | 音量旋鈕 \n調整音量。（請參閱第 24 頁。） |\n| 17 | 通話按鈕 (PTT) \n按下此按鈕即可： \n• 傳送群組呼叫、私人通話或緊急呼叫。 \n• 傳送狀態訊息。 |\n| 18 | 麥克風 \n在通訊期間對麥克風說話。 |\n\n**螢幕顯示**\n\n**顯示圖示清單**\n\n當啓動 MTM800 後，螢幕上會出現圖示以指出以下情況：\n\n| 圖示 | 說明 |\n|------|------|\n|  | 訊號強度 (TMO) \n在撥打之前可讓您檢查訊號強度。5 列表示訊號最強。 \n在訊號微弱的地區可能無法發送或接收通話或訊息。 \n天線圖示閃爍表示已超出涵蓋範圍。移到收訊較佳的地區然後再重試撥號。 \n在直通模式群組呼叫期間不會出現此圖示。 |\n|  | 訊號強度 (DMO) \n指出接收到直通模式群組呼叫。 |\n|  | 直通模式 \n當對講機在直通模式時，就會顯示此圖示。 |\n\n| 圖示 | 說明 |\n|------|------|\n|  | DMO 閘道 \n表示您選擇使用閘道撥號。此圖示分為 3 種狀態： \n持續顯示 — 當對講機與閘道同步（即，當對講機接收到出現訊號）。 \n閃爍顯示 — 當對講機未與閘道同步或正在附接。 \n無圖示 — 在對講機之間以及對講機對中繼器呼叫期間。 |\n|  | DMO 中繼器 \n當在 DMO 選取中繼器選項時，就會顯示此狀態圖示。 \n此圖示分為 3 種狀態： \n持續顯示 — 當對講機已偵測到中繼器（即，當對講機接收到出現訊號）。 \n閃爍顯示 — 當對講機未偵測到中繼器或正在附接。 \n無圖示 — 在對講機之間以及對講機對閘道呼叫期間。 |\n|  | 未讀取的訊息 \n指出收件箱中有未讀取的訊息。 |\n|  | 收到新訊息 \n如果對講機目前有進行中的活動，將不會自動開啓您的收件箱。此圖示會持續顯示以提示您收件箱中有新訊息。 |\n|  | 外部警報 \n當啓動外部警報（聲音和指示燈）時顯示。 |\n|  | 私人通話來電 \n當有私人通話來電時會閃爍顯示。如果您接受或拒絕來電或撥號失敗，此圖示將會消失。 |\n|  | 來電 \n當接收到來電時會閃爍。 |\n|  | 緊急呼叫 \n當 MTM800 在緊急模式時，就會顯示此圖示。當有緊急群組呼叫來電時，此圖示會閃爍。 |\n|  | 優先掃瞄（包含優先監視點） \n指出掃瞄已啓動。 |\n|  | 數據已連接 \n當 MTM800 已成功連接至外部裝置（筆記型電腦或桌上型電腦），準備好傳輸資料時，就會顯示此狀態圖示。 |\n|  | 接收/傳輸資料 \n此圖示指出目前正在進行資料傳輸。 |\n\n指出揚聲器啓動/關閉\n\n注意 揚聲器啓動/關閉指示僅適用於群組模式。\n\n當設定使用電話聽筒配件時，會通話群組行會反白顯示（請參閱第 81 頁）。\n- 如果通話群組行反白顯示，所有來電都會透過聽筒接聽。\n- 如果通話群組未反白顯示，任何來電的聲音都會透過外部揚聲器傳出。\n您可透過揚聲器啓動/關閉可編程按鈕來選擇使用聽筒或揚聲器接聽。\n\n顯示長號碼\n\n數字後的 3 個點表示下頁中有接續的內容（例如，在電話簿）。\n如果您撥打長號碼，每輸入一個新數字都會使顯示的號碼向左移動一位數。\n\n顯示長篇文字訊息\n\n文字訊息後顯示的箭頭表示下頁中有接續的內容（例如，在閱讀郵件訊息時）。按下即可讀取下一頁，然後再次按下即可返回上一頁。\n\nLED 狀態指示燈\n\nLED 指示燈可用來顯示 MTM800 的各種狀態。\n\n| 指示燈 | 狀態 |\n|--------|------------|\n| 持續綠燈 | 使用中 |\n| 閃爍綠燈 | 在服務範圍 |\n| 持續紅燈 | 不在服務範圍 |\n| 閃爍紅燈 | 連接至網路/進入 DMO |\n\n| 指示燈 | 狀態 |\n|--------|------|\n| 持續橘燈 | 在服務範圍中傳輸抑制 (TXI)/在 DMO 中頻道忙線 |\n| 先持續亮起然後閃爍橘色 | 來電 |\n| 無指示燈 | 關機 |\n\n**開機/關機**\n\n若要開機：\n\n- 按下 **開/關** 按鈕。\n- 如果已將 MTM800 設為點火感應，當車輛的點火裝置作動時，對講機將會自動開機。\n- 如果將緊急腳開關連接至配件接頭，且您的服務供應商已啓用了緊急開機功能，則每當按下緊急開關時，MTM800 將會以緊急模式開機（請參閱第 55 頁的「緊急情況模式」）。螢幕上將會出現一組圖示和方塊。（請參閱第 7 頁的「顯示圖示清單」。）然後您的 MTM800 將會執行自我檢查和系統註冊例行常式。當 MTM800 向系統註冊時，螢幕會顯示其他訊息。\n\n在成功註冊後，MTM800 就可開始使用。\n\n若要關機：\n\n- 再次按下 **開/關** 按鈕。\n- 如果透過點火裝置啓動而將對講機開機，則可透過點火裝置或按住 **開/關** 按鈕將對講機關機。\n\n您將會看到「關機」訊息。\n\n**注意** 如果已啓動隱密模式，則當對講機開機和關機時都不會顯示訊息或發出提示音。（請參閱第 23 頁的「隱密模式」。）\n\n解除安裝對講機\n\n選項 1：\n在中斷連接 13.2V 主電源與對講機之前：\n1) 關閉對講機。\n2) 在放開對講機的關機開關後，至少等待 4 秒。\n 中斷連接 13.2V 主電源。\n\n選項 2：\n關閉主電源但不將對講機關機。\n\n解除鎖定 MTM800\n\n您可在開機後將 MTM800 鎖定。若要解除鎖定，請參閱第 72 頁的「如何將 MTM800 解除封鎖」。\n\n選擇您的網路\n\n在開始操作 MTM800 之前，您可以選擇 MTM800 要註冊的網路。若需詳細資訊，請參閱第 82 頁的「網路」。\n\n啓動傳輸抑制時開機\n\n如果在傳輸抑制啓動下對講機已關機（請參閱第 83 頁的「設定傳輸抑制 (TXI) 模式」），則 TXI 模式仍會維持啓動狀態。\n\n當在 TXI 模式啓動下將對講機開機，會詢問用戶是否要離開 TXI 模式。\n\n如果您要停用 TXI 模式 – 例如，如果您離開建議使用 TXI 模式的無線電射頻 (RF) 敏感地區，請按下是快捷鍵（請參閱第 13 頁的「快捷鍵」）。如果 MTM800 之前處在集群模式 (TMO)，則會向網路註冊。\n\n如果按下是，且對講機之前在 TXI 和直通模式中，則對講機會退出 TXI 模式但仍留在直通模式中。\n\n如果對講機之前已在 TXI 啓動下進入集群模式，按下否會將對講機關機。\n\n如果按下否，且對講機之前在 TXI 和直通模式中，則對講機會留在 TXI 模式和直通模式中。\n\n按鍵概觀\n\n模式鍵\n\nMTM800 在集群模式操作 (TMO) 下會提供 4 種主要通話模式：\n\n- 群組模式 — 傳送和接收群組呼叫。\n- 私人模式 — 傳送和接收私人通話。\n- 電話模式 — 傳送和接收電話通話。\n- PABX 模式 — 傳送和接收本端（辦公室）分機通話。\n\n注意 只在當您的服務供應商已啓用此功能時，才會顯示 PABX 模式。\n\n如果您的服務供應商已設定此功能，則當 MTM800 在另一個模式或在功能表中於數秒內無活動時，就會回到群組模式。\n\n群組模式適用於\n\n- 在集群模式操作 (TMO) 中，透過系統涵蓋範圍內的基礎設施服務來使用 MTM800，或\n- 在直通模式操作 (DMO) 中，不需透過基礎設施服務即可使用 MTM800。\n\n注意 在 DMO 模式中操作時，可直接透過對講機天線與接收方對講機天線進行通訊，不需透過基地台或無線電塔。因此，其涵蓋範圍主要取決於車輛的位置。兩用戶之間的任何阻礙（山丘、大樓等）都會讓 TETRA 對講機的使用範圍縮小。您可將車輛駛至另一個地點或較高的地點，以提高涵蓋範圍。\n\n對講機在 DMO 中可透過閘道裝置與集群系統通訊（反之亦然）。若要使用該功能，請在對講機中啓用閘道選項（請參閱第 38 頁的「閘道/中繼器選擇」）。\n\n注意 在 DMO 模式中只能撥打群組和緊急群組呼叫。\n\n反覆按下 Mode，即可循環選擇群組、私人、電話和 PABX 模式。當 MTM800 在使用中，螢幕看起來會和下列電話、群組、私人和 PABX 模式的預設開始畫面類似。\n\n模式開始畫面範例：\n\n範圍 1\n群組 1\n狀態 選項\n\nMode 私人模式\n狀態 abc\n\nMode 話機模式\n狀態 abc\n\nMode PABX 模式\n狀態 abc\n\n快捷鍵\n\n按下即可選擇出現在螢幕上向左或向右鍵上方的選項。在本例中，會在快捷鍵上方顯示 abc。按下即可進入電話簿。在本使用手冊中，此動作稱為「按下 abc」。\n\n功能表鍵\n\n按下即可進入主功能表層級架構（當沒有進行中的活動）。MTM800 功能表可讓您控制 MTM800 設定。功能表會以層級架構排列。請參閱第 66 頁的「功能表選項清單」。功能表選項提供更詳細的選項清單，稱為子功能表。\n\n以下範例說明如何檢查電話簿中的可用記憶體。上個選項會出現在螢幕的第一行，讓您知道有多少可用的選項。\n\n緊急鍵\n\n在任意模式下按下鍵即可進入緊急模式中。此模式可讓您傳送緊急通報以及撥打緊急群組呼叫。\n\n注意 緊急模式適用於集群模式和直通模式操作。緊急通報僅適用於集群模式操作。緊急通報將會傳送給調度員（如果您的服務供應商已設定此功能）。\n\n注意 按下緊急鍵所需的時間預設為 0.5 秒。可由您的服務供應商設定此時間值。\n\n但是，即使當 MTM800 以 PIN 保護鎖定時，您仍可接收或傳送緊急呼叫。\n\n**文數字鍵盤**\n\n使用鍵盤進行撥號、將號碼輸入電話簿或建立 SDS（簡短資料服務）訊息，或單鍵撥號。\n\n**輸入號碼**\n\n若要將號碼輸入電話簿，請按下對應數字鍵。\n\n**輸入文字（字母和數字）**\n\n若要將別名輸入電話簿或在訊息中輸入文字時，按下標示所需字元的按鍵，按一下會輸入按鍵上的第一個字元、按兩二下會輸入第二個字元，以此類推。按鍵上有其他字元（請參閱第 15 頁）。\n\n**編輯文字**\n\n| 若要 ... | 動作 |\n|---------|------|\n| 將游標向右移動一個字元 | 按下 ，按下另一個按鍵或等待一小段時間 |\n| 將游標從文字結尾移至開頭位置 | 按住 |\n| 將游標向左移動一個字元 | 按下 |\n| 將游標左側的第一個字元刪除 | 按下清除 |\n| 刪除整段文字 | 按住清除 |\n| 結束編輯 | 按下清除 |\n\n**別名（名稱）**\n\n別名是您可指派至已儲存的電話和私人號碼（或 ID）的選用名稱。\n\n別名中可包含最多 14 個字元，可由字母、數字或空格組成。在記憶體清單中捲動時會顯示別名。別名也可用於從記憶體清單中擷取號碼。\n\n以下範例畫面說明來電者私人號碼的顯示方式。\n\n私人模式使用中\n180 或者 私人模式使用中\nSimon\n\n私人 ID\n無別名 ID 別名 (姓名)\n\n可用字元\n\n按下適當按鍵即可顯示下表中列出的字元。\n各鍵最上行會顯示大寫字元，而下行則會顯示小寫字元。\n按住 # 即可切換大小寫。\n\n可用字元清單：\n\n| 按鍵 | 文數字 |\n|------|--------|\n| 1 | ; ? ! 0 1 @ ' \" - ( ) / : _ ; + & % × * = < > € £ $ ¥ € [ ] { } \\ ^ ¿ ñ $ # |\n| 2 | A B C 2 Ä À Â Æ Ç |\n| | a b c 2 ä à â æ ç |\n| 3 | D E F 3 È É Ê Ë |\n| | d e f 3 è é ê ë |\n| 4 | G H I 4 Î Ï |\n| | g h i 4 î ï |\n| 5 | J K L 5 |\n| | j k l 5 |\n| 6 | M N O 6 Ö Ô Õ Ñ |\n| | m n o 6 ö ô õ ñ |\n| 7 | P Q R S 7 |\n| | p q r s 7 |\n| 8 | T U V 8 Ü Û Ó Ú |\n| | t u v 8 ü û ó ú |\n| 9 | W X Y Z 9 |\n| | w x y z 9 |\n\n| 按鍵 | 文數字 |\n|------|--------|\n| | 空格 * / % |\n| 0 | 0 + - |\n| # | # = < > |\n\n**可編程按鍵**\n\nMTM800 支援單鍵功能，可透過按住數字鍵或三個功能鍵（F1 到 F3）中的一個鍵來選擇/啓動常用的功能。您的服務供應商應會對數字和選項鍵設定相關功能。鍵盤上的所有數字鍵均是可編程的。下表列出可程式設定的功能以及在特定 MTM800 狀態/模式下的可用情況。有關這些功能的詳細資訊，請參閱本使用手冊的相關章節：\n\n| 功能 | 說明 |\n|------|------|\n| 通話群組開關 | 切換至特定通話群組 |\n| 目前/上個切換通話群組 | 切換至上一個通話群組（即使操作模式不同） |\n| 通話群組掃瞄 | 啓用/停用通話群組掃瞄功能（僅限 TMO） |\n| 回到首頁 | 使 MTM800 回到群組模式 |\n| DMO/TMO | 在 DMO 和 TMO 模式之間切換 |\n| 狀態訊息 | 傳送指定狀態訊息至指定位址（僅限 TMO） |\n| 啓動/關閉揚聲器 | 將聲音透過電話聽筒或揚聲器傳出 |\n| 文字訊息範本 | 傳送預先定義/用戶定義範本至指定位址（僅限 TMO） |\n| 通話撥號（私人、電話、PABX） | 撥號給電話簿中預先定義的連絡人（僅限 TMO） |\n| 傳輸抑制 (TXI) | 在啓動和停用 TXI 模式之間切換 |\n| 隱密模式 | 啓動/關閉隱密模式 |\n| 時間與日期 | 顯示時間和日期 |\n\n注意 如果單鍵功能已啓用，則會停用單鍵撥號功能（請參閱第 52 頁）。\n\n若要使用單鍵功能：\n\n- 從任意模式中，按住所需數字鍵約數秒。\n- MTM800 將會根據設定的功能顯示號碼或功能和動作。\n\n單鍵私人通話功能由服務供應商設定。\n\n1. 如果它已設為單工，則撥出的私人通話也會是單工。\n2. 如果它已設為雙工，則在 中撥出的私人通話也會是雙工，而在 DMO 中撥打上一個群組呼叫起始方的號碼則會是單工。\n3. 如果它已設為雙工，則在 中撥出的私人通話也會是雙工，而在 DMO 中若需要使用電話簿索引則無法撥出。\n\n首頁模式畫面\n\n您的 MTM800 提供一項讓服務供應商可傳送特殊文字訊息至您 MTM800 螢幕的功能。\n\n在按下任意鍵後會顯示此訊息數秒。\n\n如果您的服務供應商已設定此功能，MTM800 將會顯示內建首頁模式畫面，直到接收到新訊息。\n\n範圍 1\n<HomeModeDispTxt>\n\n注意 此功能可當成對用戶的特殊提醒訊息。通常包括呼號，或工作調度員參考編號，或火車班次或公車路線編號。新訊息可透過無線方式更新。\n\n時間與日期\n\n如果您的服務供應商已設定此功能，您就可以按下相關單鍵按鈕來檢查時間和日期。\n\n檢查功能表選項以確定服務供應商是否提供您自行設定時間和日期的功能。\n\n對講機停用/啓用\n\nMTM800 提供一項當對講機遭竊或遺失時可讓服務供應商透過無線方式暫時停用對講機的功能。\n\n當 MTM800 停用時，將無法發話或接聽來電。\n\n當 MTM800 停用時，將會顯示以下空白畫面。\n\nMTM800 看起來有如已關機。\n\n當對講機停用時，如果您嘗試將 MTM800 開機，其反應就會如上所述。\n\n在找回您的 MTM800 後，服務供應商就可重新啓用它。\n\n在 MTM800 重新啓用後，您就可回復正常操作。\n\n對講機永久停用\n\nMTM800 提供一項當對講機遭竊或遺失時可讓服務供應商永久停用對講機的功能。當 MTM800 被永久停用時，將無法操作。\n\n在永久停用後，服務供應商就無法重新啓用 MTM800。\n\n建議您只有當您認為無法找回對講機時，才永久停用您的 MTM800。\n\n撥出電話\n\n您可依所在模式中撥打電話：\n\n- 按下 即可撥號，然後按下 即可結束通話。\n- 按住 PTT 即可說話，而放開 PTT 即可收聽。\n\n若要撥出號碼，請進入所需模式（群組、私人、電話或 PABX）然後再依照下頁所述的方式撥號。\n\n有關特定模式中撥打方式的詳細資訊，請參閱本手冊中的相關模式章節。\n\n由於不同用戶可在不同模式中使用同一個號碼（如果已設定），在使用鍵盤輸入號碼時，請確定在正確的模式中撥號。在撥號時按下 會將鍵入的號碼帶入下個模式。\n\nVOX 控制\n\nVOX（語音操作傳輸）功能可讓使用者以免持狀態傳送語音。在進行全雙工私人通話且電話通話使用掌上型麥克風時，對講機會自動偵測到音訊。\n\n注意 只有當您的服務供應商設定此功能後才能使用。\n如果此功能已停用，按下 PTT 即可開始傳輸。\n\n接聽來電\n\nMTM800 將會自動切換至來電的模式。在來電結束後，螢幕會自動返回收到來電之前的模式。\n\n注意 在私人、電話和 PABX 模式中，如果接收到非緊急 TMO 或 DMO 群組呼叫時，MTM800 會留在目前的模式。您可接聽呼叫，但螢幕仍會維持不變。\n\n視您在鈴聲功能表選項（請參閱第 79 頁）中的設定而定，當有來電時 MTM800 將會提示您。\n在編輯訊息時，將會提示您有群組/緊急群組/廣播群組呼叫（如果您的服務供應商已設定此功能）。\n\n忙線用戶搶佔 (BUP)\n\n注意 只有當您的服務供應商設定此功能後才能使用。\n\n當您通話中（私人、電話、PABX）若主控台操作員或系統調度員想要呼叫您時，就會啓動 BUP 功能來中斷並搶佔您的通話。\n\n注意 BUP 呼叫也會搶佔進行中的撥號。但是此進行中的撥號必須為私人、電話或 PABX 通話。\n\n然後在通話搶佔成功後，主控台操作員也會在預定期間內嘗試與您建立私人通話。\n\n注意 在通話搶佔成功後於預定期間內（在 BUP 等候狀態）只允許進行緊急呼叫。\n\n優先通話 (PPC)\n\n當您急需與在非緊急語音通話中的對講機用戶通話時，優先通話就十分有用。\n\n優先通話 (PPC) 可以是緊急群組呼叫或私人 PPC（半雙工或全雙工通話）。\n\n此功能可讓您中斷進行中的低優先性通話，並接聽高優先性的來電。\n\n服務供應商會設定 PPC 的優先順序。緊急呼叫具有最高優先性。\n\n若要撥打 PPC，請參閱本使用手冊中的「緊急模式」與「私人模式」章節。\n\nMTM800 將會透過揚聲器或電話聽筒接聽，視使用的 PPC 來電接聽設定而定。\n\n注意 有關通話提示，請參閱鈴聲功能表中選項中的設定（第 79 頁）。\n\n以下就接聽 PPC 提供相關說明。\n\n在下列畫面中，<任意> 使用中是指任一種非緊急語音通話：群組、私人、電話或 PABX。\n\n在通話期間接聽緊急群組呼叫\n\nMTM800 會接聽緊急群組呼叫，中斷進行中的非緊急語音通話，然後連接緊急群組呼叫。\n\n在通話中接聽私人 PPC\n\n如果您的服務供應商已設定此功能，MTM800 會接聽 PPC，中斷進行中的非緊急低優先性語音通話，然後連接高優先性的通話。\n\n優先性較低或相同的 PPC 則會被掛斷而不提示接聽方，並會被列入未接來電清單。\n\n具緊急呼叫優先性的 PPC 通話則會螢幕上顯示為「緊急呼叫」（而非「優先」）。\n\n**接收到半雙工私人 PPC**\n\n![Diagram showing private priority call process]\n\n**接收到全雙工私人 PPC**\n\n![Diagram showing full-duplex private priority call process]\n\n**廣播呼叫**\n\n廣播呼叫（又稱為站台呼叫）為主控台操作員（或調度員）向位於一或多個站台的所有對講機用戶進行的高優先性群組呼叫。對講機已設定為監聽廣播呼叫，但是使用者無法回覆呼叫。\n\n您可依照正常廣播呼叫或緊急廣播呼叫的方式接聽。\n\n廣播呼叫會搶佔目前進行中具有相同（或較低）呼叫優先性的群組呼叫。\n\n有關在廣播呼叫中選擇通話群組的資訊，請參閱第 27 頁的「選擇通話群組」。有關在廣播呼叫中變更範圍的資訊，請參閱第 30 頁的「在通話中/接聽來電時變更通話群組」。\n\n環場收聽 (AL)\n\n此功能（如果您的服務供應商已啓用）可讓主控台操作員（或調度員）與特定 MTM800 建立特殊呼叫，以監聽當地附近的語音活動。建立此呼叫時並不會對受影響的 MTM800 發出提示，而且進行中的低優先性通話或封包資料傳輸可能會被搶佔。\n\n在接受呼叫後，MTM800 會進行半雙工私人通話傳輸，不需用戶進行任何操作，也不會對用戶發出提示。當用戶撥打語音通話並正常使用對講機時，環場收聽呼叫應會自動結束。\n\n取消來電\n\n在所有模式下（群組模式除外），在通話中如果您要取消來電，請按下拒絕。通話號碼將會轉送至未接來電清單。\n\n使用通話中功能\n\n注意：通話中功能僅適用於當使用電話聽筒接聽時（請參閱第 81 頁的「設定配件」）。\n\n啟動/關閉揚聲器\n\n從掛夾底座拿起電話聽筒將會停用揚聲器並且只能透過聽筒接聽。\n\n1. 若要啟動外部揚聲器，請按下揚聲器。\n 當揚聲器啓動時，揚聲器快捷鍵會閃爍。\n\n2. 若要停用外部揚聲器，請按下揚聲器。\n 此時揚聲器快捷鍵將會停止閃爍。\n\n使用功能鍵（手持機上的 F1 或 F2 鍵）可能會連帶啓動/關閉外部揚聲器（如果您的服務供應商已設定此功能）。\n\n將麥克風設為靜音/取消靜音\n\n在電話、PABX 或全雙工私人通話期間，使用靜音功能以：\n\n- 暫停交談而不會被對方聽到您的聲音\n- 將您所在地區的背景噪音降至最低\n\n1. 按下靜音。當靜音功能啓動時，「靜音」快捷鍵會閃爍。麥克風設為靜音。您會聽到傳入的聲音，但是對方無法聽到您 MTM800 傳送的任何聲音。\n\n2. 若要談話，請再次按下靜音。此時，「靜音」快捷鍵將會停止閃爍。麥克風設為啓動。\n\n隱密模式\n\n如果您的服務供應商已設定此功能，隱密模式可讓您完全關閉 MTM800 的所有視覺和音效提示和通知。此功能可讓 MTM800 即使在安靜的黑暗環境中，也不會被注意到。\n\n進入隱密模式：\n\n- 按下隱密模式單鍵按鈕（如果已由您的服務供應商程式設定），或\n- 在保密功能表中選擇隱密模式（請參閱第 74 頁）。\n\n單站集群服務\n\n此模式又稱為 Fallback 模式，當站台與網路中心控制器之間的連結中斷時，可讓同一站台的多部對講機進行通訊。對講機會自動進入和退出單站集群服務（即是返回系統服務）。\n\n進入單站集群服務\n\n當 MTM800 接收到來自系統的單站集群服務通知時，會發生以下情況：\n\n- MTM800 會發出提示音。\n- 螢幕會顯示「單站集群服務」訊息。\n- 在進入單站集群服務模式時，所有進行中的通話均會中斷。\n\n如果您的服務供應商已設定此功能，會定時重複此訊息/提示以提醒您對講機仍在單站集群服務模式中。\n\n當 MTM800 在單站集群服務模式時，可使用以下功能：\n\n- 註冊\n- 附加\n- 群組呼叫\n\n• 緊急群組呼叫\n• 緊急通報\n\n**退出單站集群服務**\n\n當與中央網路控制器重新建立連結時，MTM800 會退出單站集群服務，並會發生以下情況：\n\n- MTM800 會發出提示音。\n- 在單站集群服務期間，將會中斷進行中的通話。\n\n**調低螢幕亮度**\n\n如果背光設為手動（請參閱第 77 頁的「設定背光」），則提供 4 種螢幕背光亮度等級。若要變更背光亮度，請按下 \\( \\# \\)。\n\n**注意** 您無法在電話或 PABX 模式以及文字編輯中調低亮度，因為在這些模式中背光鍵 \\( \\# \\) 會用來輸入 # 號及/或當成 Shift 鍵。\n\n**調整音量**\n\n若要提高音量，以順時針方向轉動開/關音量旋鈕。\n\n若要降低音量，以逆時針方向轉動開/關音量旋鈕。\n\n**啓動/關閉聲音和指示燈提示**\n\n當您離開車輛並希望當收到重要訊息（例如私人通話）時獲得通知，則可使用聲音和指示燈提示。\n\n**注意** 若要使用聲音和指示燈提示功能，您必須在車上安裝 GKN6272 配件。\n\n如果已預先設定外部警報功能，則當有來電時車輛照明會啓動並發出提示聲通知您。\n\n若要啓動或關閉聲音和指示燈，請按下 \\( * \\)。\n\n**注意** 您必須關閉點火裝置才能使用聲音和指示燈提示。聲音和指示燈功能無法在電話或 PABX 模式以及文字編輯中操作，因為在這些模式中 \\( * \\) 鍵會用來輸入 * 號。\n\n封包資料\n\n封包資料 (PD) 服務可讓您在 TETRA 系統中使用網際網路通訊協定 (IP) 傳輸資料。請洽詢您的服務供應商以瞭解此功能是否可用。\n\n注意 若要透過無線方式從標準電腦傳輸資料，請使用功能正常的數據纜線 GMKN1022 連接電腦和 MTM800。您的服務供應商必須在您的電腦上安裝額外的應用程式。\n\n如果您的服務供應商已安裝多槽封包資料 (MSPD) 服務，則可以使用此服務來加速傳輸（請參閱第 88 頁的「封包資料」）。\n\n保養您的 MTM800\n\n清潔您的 MTM800 時，請使用沾溼或防靜電的軟布。請勿使用乾布或會釋放靜電的軟布。\n\nTMO 群組呼叫\n\n一般說明\n\n群組呼叫是指您和所選通話群組中其他人之間的通訊。參與者可以加入（逾時加入）並離開進行中的群組呼叫。通話群組是指預先定義的一組可參與及/或啓動群組呼叫的用戶，由服務供應商設定。\n\n通話群組在螢幕上會以姓名或號碼顯示（例如：業務、服務、電子技師，通話群組 10）。\n\n通話群組可依範圍分組。每個範圍最多可包含 16 個通話群組。為方便使用，MTM800 還提供以下功能：\n\n- 執行通話群組別名的文數字搜尋。\n- 使用導覽鍵在通話群組清單中捲動。\n- 撥打通話群組（由您的服務供應商設定）。\n- 將您的最愛通話群組組織至我的群組範圍中（由服務供應商設定）。\n\n通話群組可能會組織至掃瞄清單中（由服務供應商或您自行透過功能表進行設定）。當您啓動其中一個掃瞄清單時，MTM800 將會繼續監視選取通話群組的活動。\n\n藉由指派優先性至掃瞄清單中定義的通話群組，您就可接聽優先性高於目前進行中通話的通話。若需掃瞄的詳細資訊，請參閱第 84 頁。\n\n當對講機在待機或接聽來電時，您可啓動通話群組、範圍或掃瞄選擇。\n\n若要在通話中撥打給另一個群組，請執行以下操作以便在目前的通話中說話：\n\n1. 退出選擇畫面。\n2. 按下 PTT 然後開始說話。\n\n在選擇畫面上按下 PTT 即可切換至新的群組並開始撥號。\n\n每個通話群組都會有一個要監視的相關公告通話群組 (ATG)（如果服務供應商已設定此功能）。\n\nATG 為特殊的群組，會連結至多個通話群組並具有最高的優先等級，因此可向所有這些通話群組進行廣播通話。\n\n當選取 ATG 後，就不會顯示掃瞄圖示。MTM800 會監視 ATG 掃瞄清單而非選取的掃瞄清單。ATG 掃瞄清單包含所有與選取 ATG 相關的通話群組。您的服務供應商應建議哪些通話群組與公告通話群組關聯。\n\nMTM800 將會隨時監視 ATG 掃瞄清單中的群組呼叫。若要進行公告呼叫，您必須先選擇服務供應商建議的公告通話群組，否則，您將只能在接收到公告通話群組時才能參與。\n\n您無法對 ATG 掃瞄清單啓用和停用通話群組掃瞄。\n\n**選擇通話群組**\n\n您可以使用下列其中一種方式來選擇通話群組：\n\n- 導覽鍵\n- 字母搜尋功能\n- 數字鍵輸入（如果已設定）\n- 最愛群組（如果已設定）\n\n有關在通話群組範圍中捲動的設定，請參閱第 31 頁的「選擇範圍」中的注意事項。\n\n**使用導覽鍵**\n\n您的服務供應商將 MTM800 設為僅顯示可選取的通話群組。使用導覽鍵在所需通話群組中捲動，然後按下確認。有關在通話群組範圍中捲動的設定，請參閱以下「選擇範圍」一節中的注意事項。\n\n使用字母搜尋\n\n1. 在群組模式中，按下選項。\n\n2. 選擇 abc 以使用字母搜尋通話群組。\n\n3. 您現在已進入通話群組字母搜尋畫面。輸入文數字，然後 MTM800 會開始搜尋以該字母為首的第一個通話群組別名。使用導覽鍵在相鄰的別名間進行捲動。在本範例中已輸入「a」。\n\n4. 按下確認以選擇所需的通話群組，或按下 PTT 以選擇並對新群組撥號。\n\n使用數字鍵\n\n當對講機在群組模式中而且並未進行傳輸（即，待機或正在接聽來電）時，您可使用鍵盤輸入記憶位置號碼，以撥打給任一群組。此功能稱為通話群組記憶位置撥號。此記憶位置號碼已在終端預先設定。\n\n您也可以檢視某個群組的記憶位置號碼（如果有的話）。\n\n檢查附加群組的記憶位置號碼\n\n1. 在群組模式中，按下選項。\n\n2. 選擇 5 檢視記憶位置號碼來檢視通話群組的記憶位置號碼。\n\n3. 在本範例中，「1」是記憶位置號碼。按下返回以回到附加群組畫面。\n\n捲動檢視記憶位置號碼（僅限待機模式）\n\n1. 在群組模式中，按下導覽鍵即可捲動至所需通話群組。\n\n2. 按下 Menu。\n\n3. 選擇 1 檢視記憶位置號碼來檢視通話群組的記憶位置號碼。\n\n4. 在本範例中，「2」是記憶位置號碼。按下返回以回到附加群組畫面。\n\n撥打記憶位置號碼\n\n1. 輸入數字（例如「2」）。\n\n2. 按下尋找或 *#。\n\n3. 按下選擇即可附加新群組，或按下 PTT 以附加並通話。\n\n最愛群組\n\n此功能可讓您將最愛群組儲存在稱為我的群組的特殊範圍中。儲存的群組可以是 TMO 或 DMO。\n\n若要進行儲存，您可以\n- 從群組模式畫面，或\n- 從我的群組功能表選項。\n\n從群組模式畫面新增群組\n\n1. 在群組模式畫面中，捲動至所需群組，然後按下選項。\n\n2. 選擇 4 新增至我的群組。對講機會顯示通話群組別名已新增的訊息，然後返回待機狀態。\n\n從我的群組功能表選項新增群組\n請參閱第 70 頁的「我的群組」。\n\n從我的群組範圍中選擇群組\n請參閱第 70 頁的「我的群組」。\n\n在通話中/接聽來電時變更通話群組\n在接聽來電或通話進行期間，您仍可以選擇群組資料夾。\n\n接聽來電時選擇群組\n如果您在選擇群組時收到非緊急來電，當您接聽來電時 MTM800 螢幕將會維持不變。\n在選擇群組期間，您無法檢視來電方的資訊。\n\n注意 當接收到緊急呼叫時，MTM800 會中止選擇並切換至群組模式然後顯示「緊急電話使用中」。\n\n在通話中選擇群組\n如果在話中開始選擇群組，則「使用中群組」或「緊急呼叫使用中」畫面將會消失。\n\n選擇範圍\n\n若要選擇範圍：\n\n1. 在群組模式中，按下選項，然後按下範圍。\n2. 使用導覽鍵在範圍間捲動。\n3. 按下確認以選擇該範圍（或按住 PTT 即可在新範圍中撥號）。\n\n注意 服務供應商可能會將範圍捲動設定為：\n- 在範圍中捲動 — 在通話群組捲動時若已達到範圍結尾時，再捲動就會重新開啓該範圍的通話群組清單。\n- 捲動至下個範圍 — 在通話群組捲動時若已達到範圍結尾時，再捲動就會切換至下個範圍中的通話群組清單。\n\n啟動/停用掃瞄\n\n請參閱第 84 頁的「設定通話群組掃瞄」。\n\n進行群組呼叫\n\n1. 按下 Mode 直到螢幕上已出現群組模式。在本範例中，「範圍 10」是上次選取的範圍，而「通話群組 1」則為上次選取的通話群組。\n\n如果您按下選項，則可以選擇 1 abc、2 範圍或 3 掃瞄中（請參閱第 33 頁的「在啓動掃瞄功能下接聽群組呼叫」）。\n\n2. 如果出現您要撥號的通話群組，請按住 PTT。等待「通話允許」音（如果已設定），然後對麥克風說話。放開 PTT 即可收聽。\n\n3. 若要撥號的通話群組未顯示，按下導覽鍵即可在通話群組間捲動。按下確認即可選擇通話群組。按下 PTT 即可在新通話群組中撥號。\n\n4. 如果顯示的不是所需的範圍，請按下選項，然後再按下範圍。使用方向鍵在範圍間捲動。若要取消範圍捲動，請按下返回。\n\n按下確認以選擇該範圍（或 PTT 即可在新範圍中撥號）。在新範圍中撥號給此範圍中上次選取的通話群組。\n\n在開始進行撥號時，在所選通話群組中所有已開機的成員都可接收到此傳輸。\n\n注意 當您不在所選群組的正常服務涵蓋範圍時，就會出現「無群組」訊息。此時您必須選取在您工作地點中有效的新通話群組。\n\n接聽群組呼叫\n\n除非 MTM800 正在進行通話，否則將會自動切換至群組模式並接收傳輸。若要回覆呼叫，只要按住 PTT 即可。\n\nMTM800 會顯示群組名稱以及來電者的私人號碼或姓名（別名）（如果之前已儲存在您的電話簿中）。若接收到來自最愛群組的呼叫，對講機將會顯示「我的群組」範圍以及該群組的別名。\n\n以下範例畫面說明來電者私人號碼 (ID 7712) 的顯示方式。\n\n| 範圍 1 | ID: 7712 | ID: David |\n|--------|----------|-----------|\n| 通話群組 1 | 通話群組 1 | 通話群組 1 |\n| 狀態 | 狀態 | 狀態 |\n| 無別名和私人號碼 | 私人號碼無別名 | 私人號碼使用別名 |\n\n注意 有關來電提示，請參閱鈴聲功能表中選項中的設定（第 79 頁）。\n\n注意 當接收到群組呼叫時，MTM800 會發出「新群組呼叫」音。（如果您的服務供應商已設定此功能）。\n\n在關閉掃瞄功能下接聽群組呼叫\n\n您僅能接聽來自選取的通話群組或相關的 ATG 的群組呼叫。\n\n在待機模式中接聽群組呼叫\n\n在自動模式切換中，您可在任意模式下接聽群組呼叫。MTM800 將會自動切換至群組模式並接收傳輸。\n\n在群組呼叫期間接收另一通群組呼叫\n\n視服務供應商對來電的設定而定，來電可能會：\n\n- 強制您接聽，並中斷進行中的呼叫（如果來電的優先性高於進行中的呼叫）。\n 或者\n- 顯示您有呼叫（如果來電的優先性高於進行中的呼叫）。\n > 若要接受來電，按下加入。\n > 若要取消來電，按下結束。\n\n在啓動掃瞄功能下接聽群組呼叫\n\n在掃瞄功能啓動下，您可接聽來自所設定掃瞄清單的群組呼叫，還可接聽來自所選通話群組或相關 ATG 的群組呼叫。\n\n接聽掃瞄呼叫和接聽相關 ATG 或在掃瞄關閉下接聽選擇呼叫（請參閱上頁）相同，除了以下差別之外：\n\n- 在待機模式中接聽來電的螢幕不同，如圖所示。\n- MTM800 會發出提示音，相關說明請參閱下列注意事項。\n\n注意 當接收到高優先性群組呼叫時，MTM800 會發出「高優先性群組呼叫」音。（如果您的服務供應商已設定此功能）。\n\n注意 當接收到來自掃瞄清單（非高優先性群組）的群組呼叫時，MTM800 會發出「新群組呼叫」音。（如果您的服務供應商已設定此功能）。\n\n接聽緊急群組呼叫\n\n若需詳細資訊，請參閱第 20 頁。\n\n接收廣播呼叫\n\n若需詳細資訊，請參閱第 21 頁。\n\n傳輸抑制\n\n用戶必須先啓動傳輸抑制 (TXI) 模式，再進入對無線電射頻 (RF) 敏感地區，例如醫院或可能發生爆炸的環境；在此類地區可能會由於傳輸無線電而有危害安全之虞。\n\n注意 只有在 TXI 模式已啓動或中斷對講機電源時才能抑制 MTM800 的無線電波。\n\n只能在群組模式中啓動傳輸抑制。在傳輸抑制模式中，對講機在緊急群組呼叫以外的任何情況下均不會進行傳輸。即使 MTM800 在 TXI 模式中仍可啓動緊急群組呼叫。\n\n所有會造成傳輸，例如向網路註冊、變更通話群組或範圍、傳送訊息、按下 PTT 等的對講機功能和按鍵都會停用。在此情況下，螢幕會顯示「不允許在 TXI 模式」而且對講機會發出「傳輸抑制」提示音。\n\n當進入無安全之虞的地方時（例如離開對無線電射頻 (RF) 敏感地區），即可停用傳輸抑制模式，而對講機也會回到正常操作。有關設定 TXI 模式的說明，請參閱第 83 頁的「設定傳輸抑制 (TXI) 模式」。\n\n注意 若要啓動或停用 TXI 模式，您可使用其中一個可編程鍵（如果您的服務供應商已設定）。您必須按住鍵一段預設時間（由您的服務供應商設定此時間值）。\n\n啓動傳輸抑制時會持續亮起橘色 LED 並在兩畫面之間閃爍：\n\n動態指定群組號碼 (DGNA)\n\nDGNA 為網路營運商或授權使用者以無線方式動態分配新的通話群組或更新現有通話群組，以選取對講機。使用支援性服務訊息 (SS-DGNA)，網路營運商可命令您的對講機新增通話群組至現有的通話群組，或將通話群組從清單刪除。可藉由傳輸資料至您的 MTM800 以完成此項操作。\n\n注意 您的服務供應商可將某些通話群組歸在一個超群組之下，並以 DGNA 形式將它傳送至您的 MTM800。在此情況下，您將可以參與超群組中所有群組的通話。\n\n接收 DGNA 並顯示通知訊息\n\n當接收到 DGNA 而且您的服務供應商已設定 DGNA 通知時，您會聽到提示音並會顯示訊息（「正在設定項目 ...」），然後會顯示新的指派。\n\n如果您的服務供應商未設定 DGNA 通知功能，則只有當 DGNA 已變更選取群組時才會聽到提示音。\n\n1. 若要檢視新增/刪除的通話群組詳細資訊，請按下查看。您可使用 鍵在清單中捲動。\n2. 若要回到之前的模式，請按下返回。\n3. 若要選擇 DGNA 群組，請按下選擇。或使用導覽鍵捲動至另一個群組，然後按下選擇。\n\n注意 在您退出 DGNA 通知畫面後，選擇鍵會消失。若要選擇剛加入的群組，請參閱第 27 頁。\n\n如果已設定，剛加入的群組也會成爲剛選取的通話群組。\n\n如果群組已取消指派，則不會變更群組或已將對講機關機再開機，則對講機將會回到其之前的通話群組。\n\n如果在捲動時接收到 DGNA，將會出現訊息指出「通話群組清單已更新」。\n\n螢幕將在幾秒後會回到最初的 DGNA 螢幕，並指出此項更新。\n\n如果收到「刪除所有通話群組」指派的 DGNA 訊息，MTM800 將會顯示下列訊息：\n\n接收 DGNA 但不顯示通知訊息\n\n如果您的服務供應商未設定 DGNA 通知功能，則只有當 DGNA 已變更選取群組時才會聽到提示音和通知訊息。\n\nDGNA 自動選擇群組\n\n如果您的服務供應商已設定 DGNA 自動選擇功能，當對講機接收到 DGNA 訊息時，對講機將會自動將通話群組設為選取群組。\n\n按鈕/腳踏開關\n\n此功能讓使用者按下緊急按鈕/腳踏開關即可傳送預先定義的狀態訊息。您無法使用 TMO 緊急模式、緊急通報和撥打 TMO 緊急群組/私人通話。\n\n設定訊息位址與傳送：\n\n- 可由服務供應商預先定義此位址，如果未預先定義，則將會傳送至目前選取的群組\n- 如果未選取群組，則會將訊息傳送至保留位址\n- 即使使用者目前正在使用服務，仍會傳送訊息\n\n指示訊息視服務供應商而定。可停用狀態訊息的顯示提示/提示音。\n\n當對講機已使用 PIN 碼鎖定，使用者仍可按下緊急按鈕/腳踏開關傳送訊息。如果對講機不在服務範圍，使用者只會看到操作失敗的訊息。\n\nDMO 群組呼叫\n\n一般說明\n\n在 DMO（直通模式操作）中，MTM800 可不需搭配您服務供應商的基礎設施使用。\n\n直通模式可讓相同通話群組中的對講機之間進行通訊。\n\n注意 在 DMO 中，您只能進行群組呼叫、緊急群組呼叫和私人半雙工呼叫。\n\n您可接收的呼叫包括：\n\n- 來自選取的通話群組。\n- 來自通話範圍內的其他使用者（如果服務供應商已設定）。這稱為 InterMNI（行動網路識別）呼叫。\n- 從開放群組。（開放群組是所有 DMO 群組所屬的超群組（super-group））。\n\n當您開始進行呼叫時，選取通話群組中已開機以及列於群組用戶身份（由服務供應商設定）的成員都會收到此項傳輸。如果對講機中已啓用閘道選項，則在 DMO 中，MTM800 可與集群系統（反之亦然）通訊。\n\n若要增強對講機的 DMO 涵蓋範圍，如果已在對講機中啓用了中繼器選項，則 DMO 群組可連結至中繼器。此外，還可使用 GW + Rep（閘道和中繼器）通訊模式。\n\n當將對講機設為 DMO 時如果傳輸抑制已啓動，則會停用 PTT。您僅能接聽。有關傳輸抑制的詳細資訊，請參閱第 34 頁。當傳輸抑制已啓動時，允許進行 DMO 通話群組選擇。\n\n選擇通話群組\n\n請參閱第 27 頁的「選擇通話群組」。\n\n在通話中/接聽來電時變更通話群組\n\n請參閱第 30 頁的「在通話中/接聽來電時變更通話群組」。\n\n從 TMO 切換至 DMO 或從 DMO 切換至 TMO\n\n依下列一種方式進入 TMO 或 DMO：\n\n- 若要從 TMO 切換至 DMO，請按下 Menu 622。\n- 若要從 DMO 切換至 TMO，請按下 Menu 621。\n- 按下 TMO/DMO 單鍵按鈕（如果已由您的服務供應商設定）。\n\n開道/中繼器選擇\n\n使用 DMO 設定子功能表來設定開道和中繼器選項。\n\n1. 在 DMO 中按下選項以進入選項功能表：\n\n **DMO 選項子功能表**\n\n | 1 abc | 1 MS–MS | 1 自動 |\n |-------|---------|-------|\n | 2 範圍| 2 開道 | 2 特定 |\n | 3 設定| 3 中繼器 | |\n | 4 新增至我的群組 | 4 GW + Rep | 1 自動 |\n | 5 檢視記憶位置號碼 | | 2 特定 |\n\n2. 捲動至 3 設定，然後按下確認。\n\n選擇 DMO 群組呼叫（MS 對 MS）\n\n若要從開道或中繼器模式變更至 MS–MS 模式（DMO 對講機之間的呼叫）：\n\n1. 按下選項，捲動至 3 設定然後按下確認。\n2. 捲動至 1 MS–MS，然後按下確認。\n 以下訊息會顯示數秒：\n 「將使用 MS–MS」。\n\n透過開道選擇 DMO 群組呼叫\n\n在 DMO 模式中，請繼續下列步驟選擇開道，為選取的通話群組設定透過開道進行呼叫：\n\n1. 按下選項，捲動至 3 設定然後按下確認。\n\n2. 捲動至 2 閘道，然後按下確認。\n\n3. 螢幕將顯示上次的閘道選擇方式。使用導覽鍵在選項中捲動選擇，然後按下確認：\n\n自動 — MTM800 將會使用該通話群組第一個可用的閘道。選取該選項時，閘道圖示將會閃爍。\n\n特定 — MTM800 只能使用採用該通話群組指定閘道位址的閘道。\n\n選擇「特定」時，將會顯示下列其中一項：\n\n- 選取的閘道位址（例如：1022）、服務供應商預先設定或您之前使用鍵盤自行輸入的閘道位址。按下確認以使用目前的位址，或透過鍵盤輸入新的位址，然後按下確認。選取該閘道時，閘道圖示將會閃爍。\n\n- 「無」表示尚未為該通話群組選取閘道。透過鍵盤輸入位址，然後按下確認。選取該閘道時，閘道圖示將會閃爍。\n\n當 MTM800 傳測到有適用的閘道時，閘道圖示會持續顯示。\n\n透過中繼器選擇 DMO 群組呼叫\n\n在 DMO 模式中，請繼續下列步驟選擇中繼器選項，為選取的通話群組設定透過中繼器進行呼叫：\n\n1. 按下選項，使用導覽鍵捲動至 3 設定然後按下確認。\n2. 捲動至 3 中繼器，然後按下確認。\n\n3. MTM800 將會使用該通話群組第一個可用的中繼器。選取該選項時，中繼器圖示將會閃爍。\n\n當 MTM800 傳測到適用中繼器的出現訊號時，中繼器圖示將會持續顯示。\n\n透過閘道和中繼器選擇 DMO 群組呼叫\n\n在 DMO 模式中，請繼續下列步驟選擇閘道和中繼器選項，為選取的通話群組設定透過閘道或中繼器（優先透過閘道）進行呼叫：\n\n1. 按下選項，捲動至 3 設定然後按下確認。\n2. 捲動至 4 GW + Rep，然後按下確認。\n3. 螢幕會顯示上個「GW + Rep.」類型選擇。使用導覽鍵在選項中捲動選擇，然後按下確認：\n\n自動 — MTM800 將會使用該通話群組第一個可用的閘道。選取該選項時，閘道圖示和中繼器圖示將會閃爍。\n\n特定 — MTM800 只能使用採用該通話群組指定閘道位址的閘道。\n\n選擇「特定」時，將會顯示下列其中一項：\n\n- 選取的閘道位址（例如：1022）、服務供應商預先設定或您之前使用鍵盤自行輸入的閘道位址。按下確認以使用目前的位址，或透過鍵盤輸入新的位址，然後按下確認。選取該閘道時，閘道和中繼器圖示將會閃爍。\n\n- 「無」表示尚未為該通話群組選取閘道。透過鍵盤輸入位址，然後按下確認。選取該閘道時，閘道和中繼器圖示將會閃爍。\n\n當 MTM800 偵測到適當的閘道及/或中繼器時，閘道及/或中繼器圖示會持續顯示。\n\n進行 DMO 群組呼叫（MS 對 MS）\n\n1. 按下 Mode 直到螢幕上已出現群組模式。\n\n2. 按下 Menu 6 2 2 （另請參閱第 83 頁）。若要變更範圍和通話群組，請參閱第 31 頁的「進行群組呼叫」的步驟 3 和 4。\n\n3. 如果出現所需的通話群組和範圍，請按下 PTT。等待「通話允許」音（如果已設定），然後對麥克風說話。放開 PTT 即可收聽。\n\n若要變更通話群組和範圍，請參閱「群組模式」一節，第 27 頁。\n\n注意 若要快速變更操作模式，您可使用其中一個可編程鍵（如果您的服務供應商已設定）。\n\n透過閘道進行 DMO 群組呼叫\n\n1. 在 DMO 中，依第 38 頁的「透過閘道選擇 DMO 群組呼叫」中所述選擇閘道。\n\n2. 對選取的通話群組進行呼叫：\n\n- 如果在閘道無法使用時按下 PTT，將會不透過閘道進行 DMO 呼叫。閘道圖示將會消失。\n- 如果在閘道可用時按下 PTT，但是閘道卻拒絕此呼叫，則 MTM800 將會發出提示音並顯示下列畫面，通知您透過閘道的呼叫已中止，而且對講機將自動不透過閘道進行呼叫。閘道圖示將會消失。\n- 如果在閘道可用時按下 PTT，將會透過閘道進行 DMO 呼叫。閘道圖示將會持續顯示。\n\n透過中繼器進行 DMO 群組呼叫\n\n1. 在 DMO 中，依第 39 頁的「透過中繼器選擇 DMO 群組呼叫」中所述選擇中繼器選項。\n\n2. 對選取的通話群組進行呼叫：\n\n - 如果在中繼器無法使用時按下 PTT，將會不透過中繼器進行 DMO 呼叫。中繼器圖示將會消失。\n - 如果在中繼器可用時按下 PTT，但是中繼器卻拒絕此呼叫，則 MTM800 將會發出提示音並顯示下列畫面，通知您將不透過中繼器進行呼叫。中繼器圖示將會消失。\n - 如果在中繼器可用時按下 PTT，將會透過中繼器進行 DMO 呼叫。中繼器圖示將會持續顯示。\n\n透過開道和中繼器進行 DMO 群組呼叫\n\n1. 在 DMO 中，依第 40 頁的「透過開道和中繼器選擇 DMO 群組呼叫」中所述選擇開道和中繼器選項。\n\n2. 對選取的通話群組進行呼叫：\n\n - 如果在開道和中繼器均無法使用時按下 PTT，將會不透過開道和中繼器進行 DMO 呼叫。開道和中繼器圖示將會消失。\n - 如果在開道和中繼器均可用時按下 PTT，但是開道拒絕了此呼叫，則會嘗試透過中繼器進行呼叫。\n > 如果呼叫成功，MTM800 將會顯示「中繼器呼叫」訊息，並會透過中繼器進行呼叫。開道圖示將會消失。\n > 如果呼叫不成功，MTM800 將會顯示「MS – MS 直通模式」訊息，並會進行對講機之間的呼叫。開道和中繼器圖示將會消失。\n\n• 如果在開道和中繼器均可用時按下 PTT，則會嘗透過開道進行呼叫。\n\n> 如果成功，則 MTM800 將會透過開道進行 DMO 呼叫。開道圖示將會持續顯示。中繼器圖示將會消失。\n> 如果與開道同步不成功，則會嘗試透過中繼器進行呼叫。\n> 如果呼叫成功，MTM800 將會顯示「中繼器呼叫」訊息，並會透過中繼器進行呼叫。開道圖示將會消失，而中繼器圖示將會持續顯示。\n> 如果呼叫不成功，MTM800 將會顯示「MS – MS 直通模式」訊息，並會進行對講機之間的呼叫。開道和中繼器圖示將會消失。\n\n注意：如果選取了開道和中繼器模式，且其中一個裝置無法使用，則會依照該裝置未選取時的情況進行呼叫。\n\n範例：當開道可用但是中繼器無法使用時，在嘗試透過開道進行呼叫失敗後，會立即回到 MS – MS 模式，並顯示「MS – MS 直通模式」訊息。\n\n接聽 DMO 群組呼叫\n\n只有當 MTM800 在 DMO 中，才能接聽 DMO 群組呼叫。\n\nMTM800 將會顯示來電者的私人號碼或別名，以及通話群組名稱。\n\n以下範例畫面說明來電者身份的顯示方式。\n\n注意：有關通話提示，請參閱鈴聲功能表中選項中的設定（第 79 頁）。\n\n接聽 DMO 群組呼叫 (MS – MS)\n\nDMO 範圍 1\nDMO 通話群組 1 選項\n\nID:124\nDMO 通話群組 1 選項\n\nID:David\nDMO 通話群組 1 選項\n\n無別名和私人 ID\n不含別名的私人 ID\n含別名的私人 ID\n\n接聽 DMO 群組呼叫（透過開道/中繼器）\n\nDMO 範圍 1\nDMO 通話群組 1 選項\n\nID:124\nDMO 通話群組 1 選項\n\nID:David\nDMO 通話群組 1 選項\n\n無別名和私人 ID\n不含別名的私人 ID\n含別名的私人 ID\n（例如透過開道）\n（例如透過開道）\n（例如透過中繼器）\n\n會依據進行中的呼叫類型（開道或中繼器）顯示開道或中繼器圖示。\n\n注意\n\n- 如果選取 MS 對 MS 模式，且對講機透過中繼器接收到呼叫時，將會顯示中繼器圖示（如果服務供應商已啓用了中繼器模式，否則將不會接受此呼叫）。\n- 如果選取了開道模式但是開道無法使用時，當有開道來電時，開道圖示將會持續顯示。\n\nDMO 私人通話\n\n如果服務供應商已設定此功能，則可以在 DMO 中撥打和接聽私人通話。\n\n不過，雖然開道及/或中繼器選項已啓動，卻無法用於 DMO 私人通話。DMO 私人通話是兩部 TETRA 對講機 (MS – MS) 之間的直接通訊。\n\n若需詳細資訊，請參閱第 48 頁的「在 DMO 中撥打私人通話」。\n\n接聽緊急群組呼叫\n\n若需詳細資訊，請參閱第 60 頁的「DMO 中的緊急呼叫」。\n\n私人通話\n\n一般說明\n\n私人通話（又稱為點對點或個別通話）是指兩人之間的通話。其他的對講機無法收聽此對話。\n\n此類通話可以是\n\n- 在 TMO 中進行的全雙工通話（如果系統許可），或\n- 在 TMO 或 DMO 中進行的半雙工通話。\n\n在全雙工通話中，通話雙方可同時說話，而在半雙工通話時，一次僅能有一方說話。\n\n注意 如果您的服務供應商已限制存取電話簿，則可能無法建立新連絡人、編輯現有連絡人或撥打不在電話簿中的號碼。\n\n進入私人模式\n\n若要進入私人模式，反覆按下 Mode 直到螢幕上出現私人模式。\n\n在本範例中，8008801 是上次撥出或已撥打的對講機私人號碼。畫面會顯示無別名，因為它不是預設在私人號碼清單中的號碼。如果您希望撥號給此人，請按下 PTT。\n\n如果顯示的不是您要撥號的對象，請依下列其中一種方式輸入其他私人號碼：\n\n- 上次撥出的號碼，\n- 直接輸入，\n- 簡碼撥號，\n- 在清單中捲動，或\n- 字母搜尋。\n\n按下返回即可回到私人模式畫面。\n\n有關在對無線電射頻 (RF) 敏感地區操作 MTM800 的資訊，請參閱第 34 頁的「傳輸抑制」。\n\n注意 若傳輸抑制已啓動，當有私人通話來電就會發出提示，但是您無法接聽來電。\n\n輸入私人號碼\n\n上次撥出的號碼\n\n當對講機進入私人待機模式時，將會顯示上次撥出的號碼。按下 PTT 即可撥打此號碼。\n\n直接輸入\n\n1. 輸入私人號碼。如果輸入的號碼已預先儲存在私人電話簿中，則 MTM800 會為您找到此號碼。\n2. 若要將此號碼儲存在電話簿中，請按下儲存並依照提示進行（請參閱第 68 頁的「更新私人電話簿」）。\n\n簡碼撥號\n\n如果您的服務供應商已設定此功能，簡碼撥號功能可讓您在撥號只需撥打該連絡人的部分號碼。MTM800 將會自動完成剩下的號碼，並根據您對講機的身份以無線方式傳送。\n\n例如：\n\n1. 撥打 456（而非完整號碼 4282456）。\n2. 若要進行通話，按下 PTT。\n3. 若要掛斷，請按下。\n\n清單捲動\n\n若要在號碼和姓名清單中向後或向前捲動，請按下 或 。\n\n字母搜尋\n\n字母搜尋讓您只要輸入此號碼相關姓名（或別名）的第一個字母即可快速找到儲存的私人號碼。\n\n1. 按下 abc。\n2. 按下您要在預先儲存清單中搜尋的姓名第一個字母的對應數字鍵（在本例中為 3 def 鍵）。\n\n注意 如果無以該字母為首的儲存名稱，MTM800 會自動依字母順序進一步搜尋，直到找到下個名稱。如果在清單中找到多個以該字母為首的名稱，則可使用捲動鍵來檢視其他名稱。\n\n在 TMO 中撥打私人通話\n\n1. 輸入要撥打號碼。\n2. 按下再放開 PTT。您會聽到鈴聲。等待對方接聽您的來電。\n3. 按住 PTT 即可說話，而放開 PTT 即可收聽。\n4. 若要結束通話，請按下 。如果對方結束通話，則會顯示「通話結束」訊息。\n\n在 TMO 中撥打私人全雙工通話\n\n1. 輸入要撥打號碼。\n2. 按下再放開 。在成功撥號後，您將會聽到鈴聲。等待對方接聽您的來電。\n3. 若要結束通話，請再次按下 。如果對方結束通話，則會顯示「通話結束」訊息。\n\n在 TMO 中接聽私人通話\n\n1. MTM800 會自動切換至私人模式並開始響鈴。螢幕會顯示來電者的身份。\n2. 若要回覆來電，只要按下 PTT 即可。\n3. 若要結束或取消來電，按下 。螢幕會自動返回收到來電之前的模式。\n\n如果對方結束通話，則會顯示「通話結束」訊息。\n\n注意 有關通話提示，請參閱鈴聲功能表中選項中的設定（第 79 頁）。\n\n在 TMO 中接聽私人全雙工通話\n\n1. MTM800 會自動切換至私人模式並開始響鈴。螢幕會顯示來電者的身份。\n2. 若要接聽來電，請按下 或鍵盤上的任意鍵（如果您的經銷商已設定此功能）。\n3. 若要結束或取消來電，按下 。螢幕會自動返回收到來電之前的模式。\n\n如果對方結束通話，則會顯示「通話結束」訊息。\n\n注意 有關通話提示，請參閱鈴聲功能表中選項中的設定（第 79 頁）。\n\n在 DMO 中撥打私人通話\n\n如果服務供應商已設定此功能，則可以在 DMO 中撥打和接聽私人通話。只有當 MTM800 在 DMO 中，才能撥打或接聽 DMO 私人通話。\n\n注意 不支援透過 DMO 中繼器及/或 DMO 開道進行私人通話。\n\n發話和收話方應在同一個通話群組。\n\n撥打 DMO 私人通話\n\n1. 若要進入私人模式，反覆按下 直到螢幕上出現「私人模式」。\n2. 依第 46 頁的「輸入私人號碼」中所述輸入號碼。\n3. 按住 PTT。等待通話允許音（如果已設定）後再說話，然後放開 PTT 收聽對方答話。\n\n4. 在經過預先設定的時間後，或當您按下 时，通話即告結束。\n\n注意 在 DMO 中，撥打私人通話時不會檢查出現訊號。也就是說，當您撥號時並不確定對方是否可接聽。\n\n接聽 DMO 私人通話\n\n當接收到 DMO 私人通話時，不需對方接聽就會立即進行通話。\n\n1. 按下 PTT 即可開始進行交談。\n2. 在經過預先設定的時間後，或當您按下 时，通話即告結束。\n\n注意 如果對方按下 ，將會暫停 DMO 私人通話一段時間，若發話方仍在傳輸中，則會再度加入通話。\n\n撥號時有來電\n\n如果撥號時收到來電，當您接聽來電時 MTM800 將會留在目前的模式中，而且螢幕將會維持不變。仍可在目前螢幕上繼續撥號。\n\n注意 當接收到緊急呼叫時，MTM800 會中止撥號並切換至群組模式然後顯示「緊急電話使用中」。\n\n撥打私人 PPC（優先呼叫）\n\n注意 只有當您的服務供應商設定此功能後才能使用。\n\n1. 輸入私人號碼然後按下 PTT 或 。\n2. 如果螢幕顯示對方在忙線中，請按 是以中止進行中的通話。\n3. 您會聽到鈴聲。等待對方接聽您的來電。\n4. 以一般半雙工或全雙工私人通話形式繼續進行通話。\n\n通話佇列\n\n在建立通話時若無可用的基礎設施資源，或在重選細胞期間正在通話中，通話將會排入佇列。MTM800 將會在佇列中維持一段預設時間。如果在這段期間內有可用資源，將會繼續進行通話。如果在經過一段時間後仍無可用資源，MTM800 將會結束通話。\n\n電話與 PABX 通話\n\n一般說明\n\n電話模式可讓您撥打固定線路電話號碼或行動電話號碼。在本文件中，我們以「電話號碼」指稱此類號碼。\n\n專用自動交換分機 (PABX) 模式可讓您撥打本端（辦公室）分機號碼（如果您的服務供應商已啓用此模式）。這兩種模式都提供相同的撥號功能。\n\n有關在對無線電射頻 (RF) 敏感地區操作 MTM800 的資訊，請參閱第 34 頁的「傳輸抑制」。\n\n注意 若傳輸抑制已啓動，當有電話或 PABX 來電就會發出提示，但是您無法接聽來電。\n\n注意 如果您的服務供應商已限制存取電話簿，則可能無法建立新連絡人、編輯現有連絡人或撥打不在電話簿中的號碼。\n\n撥打電話或 PABX 通話\n\n1. 按下 Mode 直到螢幕上已出現電話模式。如果需要 PABX 通話，請再按一下 Mode 鍵。PABX 模式會出現在螢幕上。\n\n2. 在變更至電話/PABX 模式後將會在螢幕上顯示上次撥出的號碼。在本範例中，上次撥出的電話號碼是 039694040。\n\n3. 如果您希望撥號給此人，請按下 。\n\n4. 若要掛斷，請再次按下 。\n如果顯示的不是您要撥號的對象，請依下列其中一種方式輸入其他號碼：\n- 上次撥出的號碼，\n- 直接撥號，\n- 記憶位置撥號，\n- 單鍵撥號，\n\n• 在清單中捲動，或\n• 字母搜尋。\n\n按下返回即可回到模式畫面。\n\n上次撥出的號碼\n\n當未顯示任何號碼時，按下 將會進入上次撥出的電話與私人通話號碼清單。\n\n1. 若要在清單中向後或向前捲動，請按下 或 。\n2. 若要撥打電話，請按下 。\n3. 若要掛斷，請再次按下 。\n\n直接撥號\n\n1. 使用鍵盤撥打完整電話號碼。\n2. 若要將此號碼儲存在電話簿中，請按下 儲存 並依照提示進行。\n3. 若要撥號，請按下 。\n4. 若要掛斷，請再次按下 。\n\n記憶位置撥號\n\n記憶位置撥號功能可讓您最多使用 2 位數字來撥打號碼，而不需撥打完整號碼。記憶位置號碼是指電話簿中的項目位置。\n\n1. 輸入預先設定的記憶位置號碼（例如：5）然後按下 。\n2. 若要撥號，請按下 。\n3. 若要掛斷，請再次按下 。\n\n單鍵撥號\n\n單鍵撥號功能可讓您以按住一個數字鍵 (2 - 9) 的方式撥號。此號碼是指電話簿中的項目位置 (2 - 9)。\n\n1. 按住所需數字鍵約數秒。MTM800 將會顯示該號碼然後撥號。\n2. 若要掛斷，請按下 。\n\n注意 如果單鍵功能已啓用，則會停用單鍵撥號功能（請參閱第 16 頁）。\n\n清單捲動\n\n1. 若要在號碼和姓名清單中向後或向前捲動，請按下 或 。\n2. 若要撥號，請按下 。\n3. 若要掛斷，請再次按下 。\n\n字母搜尋\n\n字母搜尋讓您只要輸入此號碼相關姓名（或別名）的第一個字母即可快速找到儲存的號碼。\n\n1. 按下 abc 。\n2. 按下您要在預先儲存清單中搜尋的姓名第一個字母的對應數字鍵（在本例中為 3 def ）。\n\n注意 如果無以該字母為首的儲存名稱，MTM800 會依字母順序進一步搜尋，直到找到下個名稱。如果在清單中找到多個以該字母為首的名稱，則可使用捲動鍵來檢視其他名稱。\n\n3. 若要撥號，請按下 。\n4. 若要掛斷，請再次按下 。\n\nDTMF 通話中撥號\n\n如果您的服務供應商已設定此功能，DTMF 可讓您在通話中與自動應答裝置（例如語音信箱或答錄機）通訊。\n\n在通話中，按下按鍵 0 – 9、*、#。按下時，按鍵將會發出按鍵音並會在畫面上顯示輸入的數字。\n\n撥號時有來電\n\n請參閱第 49 頁的「撥號時有來電」。\n\n接聽電話或 PABX 通話\n\n1. MTM800 會自動切換至電話模式並開始響鈴。\n2. 若要接聽來電，請按下 或任意鍵（不包括開機/關機）。\n3. 若要結束或取消來電，按下結束。螢幕會自動返回收到來電之前的模式。\n\n如果對方結束通話，則會顯示「通話結束」訊息。\n\n注意 有關通話提示，請參閱鈴聲功能表中選項中的設定（第 79 頁）。\n\n一般說明\n\n在集群模式 (TMO) 中，您可向調度員傳送緊急通報並撥打和接收緊急群組呼叫或私人通話。當對講機在 TMO 中時可接聽對選取群組、相關 ATG（公告通話群組）或掃瞄群組進行的緊急群組呼叫。如果 ATG 是目前選取的群組，則對講機將可接聽到對此 ATG 相關群組進行的緊急群組呼叫。（有關 ATG 的資訊，請參閱第 26 頁。）MTM800 也可以讓您撥打緊急群組呼叫而不需按住 PTT（緊急麥克風功能）。\n\n在直通模式 (DMO) 中，您可撥打和接收緊急群組呼叫。\n\n您的服務供應商可設定\n\n- 緊急群組呼叫，\n- 緊急私人通話（如果基礎設施支援此功能），\n- 緊急通報，\n- 緊急麥克風功能，以及\n- 緊急模式指示。\n\n當從 TMO 切換至 DMO 時對講機仍會處於緊急模式中。當從 DMO 切換至 TMO 時，如果可在 TMO 中使用緊急模式，則對講機也會處於緊急模式中。\n\n在系統中會對緊急呼叫分配緊急優先性。\n\n如果 MTM800 在作用中並已附加至任意通話群組時，就會啓用這些功能。\n\n緊急群組呼叫可設為非戰術 (non-tactical) 或戰術 (tactical)：\n\n- 您可對服務供應商指定的通話群組進行非戰術呼叫。在進行呼叫時此群組可能會與對講機畫面上顯示的群組不同。在退出非戰術緊急模式後，對講機將會附加至進行非戰術呼叫之前選取的群組。在非戰術緊急模式中時，您將無法切換通話群組。\n\n在非戰術緊急模式中並不會受到 DGNA 訊息的影響，只有在退出非戰術緊急模式時才會受到影響。\n\n• 您可對目前選取的通話群組進行戰術呼叫。\n\n注意 有關通話提示，請參閱鈴聲功能表中選項中的設定（第 79 頁）。\n\n進入 TMO 或 DMO\n\n依下列一種方式進入 TMO 或 DMO：\n\n• 按下 Menu 621 (TMO)\n• 按下 Menu 622 (DMO)\n• 按下 TMO/DMO 單鍵按鈕（如果已由您的服務供應商設定）\n\n進入或退出緊急模式\n\n若要從任意模式中進入緊急模式，請按下 △。\n\n注意 當在 TMO 中進入緊急模式時，MTM800 將會自動將緊急通報傳送給調度員（如果您的服務供應商已設定此功能）。\n\n對講機會退出緊急模式並在下列情況中會切換至群組模式：\n\n• 按住返回。\n• 對講機會附加至非戰術 (non-tactical) 群組。\n• 系統基礎設施會卸除選取的非戰術 (non-tactical) 群組。\n\n注意 按下緊急鍵所需的時間預設為 0.5 秒。可由您的服務供應商設定此時間值。\n\n注意 按下緊急鍵後，即使已啓用傳輸抑制功能，仍會使對講機立即進行傳輸。\n\n進入緊急模式時，對講機應已離開對無線電射頻 (RF) 敏感地區！\n\n注意 當按下緊急鍵 △ 時，MTM800 會中斷環場收聽通話。\n\n靜音緊急呼叫\n\n注意 此功能可由您的服務供應商啓用/停用。\n\n靜音緊急呼叫模式是一種緊急服務，在任何緊急呼叫操作下，不會針對待機狀態發出提示音或顯示提示。在此模式下，只有使用者才知道對講機處於緊急呼叫模式並可傳送緊急呼叫通報。\n當使用者退出緊急呼叫後，將會恢復所有設定。\n若要退出靜音緊急呼叫模式，使用者需要按下退出快捷鍵。\n\n變更範圍或通話群組\n\n如果緊急群組呼叫已設為「戰術」，則您可以選擇顯示以外的通話群組，按下導覽鍵然後再按下確認。\n若要變更範圍，請按下選項，然後依第 31 頁的「進行群組呼叫」中所述的步驟進行。\n\nTMO 中的緊急呼叫\n\n傳送緊急通報\n\nMTM800 將會傳送緊急通報（如果您的服務供應商已設定此功能）：\n\n- 在進入緊急模式時自動傳送。\n- 當 MTM800 在緊急模式中時按下。\n- 如果在緊急模式中變更群組。\n\n螢幕會顯示下列一個傳送報告：\n\n- 警告已傳送\n- 警告傳送失敗\n\n在這兩種情況下，螢幕都會在數秒內返回緊急模式主畫面。\n由於在 DMO 中並不傳送確認，所以「警告已傳送」訊息確認僅會傳送警報。\n\n或者 – 如果您的服務供應商已設定此功能 – 在以下情況中 MTM800 將會傳送緊急通報：\n\n- 如果之前不曾進入緊急模式時，按下緊急鍵/腳踏開關。\n - 其他緊急服務（例如啓動 TMO 緊急模式或進行緊急私人通話，若基礎設施支援的話）將無法使用。\n - 傳送緊急通報時不會顯示提示訊息或發出提示音。\n\n注意 當使用者在「單站集群服務」區時，某些系統不支援緊急通報功能。（請參閱第 23 頁。）\n\n進行緊急群組呼叫\n\n在緊急模式中，若要撥打或接聽呼叫：\n\n1. 按住 PTT。\n2. 等待通話允許音（如果已設定）後再說話。\n3. 放開 PTT 收聽。\n\n注意 按下緊急鍵後，MTM800 將會進入 TMO 模式（如果您的服務供應商已設定此功能）。對講機會附加至預先定義的通話群組，並開始進行緊急群組呼叫。如果預先定義的通話群組無效，對講機會附加至上次選取的通話群組。\n\n緊急麥克風功能\n\n如果服務供應商已在您的 MTM800 中設定了緊急麥克風功能，您不需按住 PTT 就可以進行緊急群組呼叫。\n\n在進入緊急模式時會出現以下情況：\n\n1. MTM800 將會自動傳送緊急通報給調度員（如果已由您的服務供應商設定）。\n2. 您會聽到通話允許音。\n3. 將會出現下列典型畫面：\n 麥克風會持續啓動一段時間（由您的服務供應商決定並設定）。\n\n在緊急麥克風啓動期間已逾期，或您在緊急麥克風啓動期間按下 PTT，或是按下結束：將會出現「緊急麥克風結束」訊息，然後對講機會回到緊急模式。緊急麥克風功能會停用，而 PTT 操作會回到正常模式。若要繼續，請再次按下。\n\n如果群組的其他成員已取得通話許可，則您會聽到「已接收到緊急呼叫」提示音。如果您的服務供應商已設定此功能，則 MTM800 將會自動再次嘗試取得通話許可，並將顯示「等待麥克風」訊息。\n\n注意 在此等待期間，MTM800 麥克風將不會啓動，直到再次顯示「緊急麥克風啓動」訊息。\n\n接聽緊急群組呼叫\n\n當對講機在 TMO 中時可接聽對選取群組、相關 ATG（公告通話群組）或掃瞄群組進行的緊急群組呼叫。如果 ATG 是目前選取的群組，則對講機將可接聽到對此 ATG 相關群組進行的緊急群組呼叫。（有關 ATG 的資訊，請參閱第 27 頁。）\n\n當 MTM800 接收到呼叫時，螢幕將會顯示來電者的身份。如果螢幕在待機下，將會顯示「緊急電話使用中」。\n\n如果在進入緊急模式時，MTM800 接收到緊急呼叫，而且您的服務供應商已啓用了緊急麥克風功能，則會顯示「等待麥克風」訊息。MTM800 將會嘗試取得通話許可。\n\n注意 踩下緊急腳開關即可將 MTM800 在緊急麥克風模式下開機（請參閱第 10 頁的「開機/關機」）：如果麥克風/PTT 組件已連接至對講機前側的插槽而且已安裝外部麥克風/PTT 組件，則外部麥克風將會開啓。\n\nDMO 中的緊急呼叫\n\n您可對群組進行緊急群組呼叫。\n\n您可接收到來自選取通話群組（如果您的服務供應商已設定）以及來自通話範圍內的其他使用者或開放群組的呼叫。（開放群組是所有 DMO 群組所屬的超群組 (super-group) ）。\n\n您可透過閘道或中繼器進行緊急呼叫。有關閘道和中繼器設定，請參閱第 38 頁的「閘道/中繼器選擇」。\n\n進行緊急群組呼叫\n\n若要進行或接聽呼叫：\n\n1. 按住 \\(\\triangle\\) 鍵即可進入緊急模式。\n2. 按住 PTT。\n3. 等待通話允許音（如果已設定）後再說話。\n4. 放開 PTT 收聽。\n\n接聽緊急群組呼叫\n\n螢幕會顯示緊急電話使用中，並以私人號碼或別名顯示來電者的身份。如果螢幕在待機下，將會顯示「緊急電話使用中」。\n\nGPS 定位服務\n\n一般說明\n\n對講機的 GPS 定位功能會從環繞地球的全球定位系統 (GPS) 衛星擷取資訊，來判斷對講機的大致地理位置。此位置資訊的可用性和精確性（及所需的計算時間）取決於您使用對講機的環境。\n\n例如，在室內、涵蓋位置、高樓之間或在其他無法清楚看到天空的情況下，通常很難取得 GPS 定位。\n\n請參閱「重要 – 謹記事項」。\n\nGPS 定位服務可在多方面協助您的調度員或同事，例如更有效率地部署資源或當您要求緊急服務時找到您對講機的位置。\n\n對講機可設為在對講機螢幕上顯示位置資訊，或以無線方式傳送位置資訊給調度員，以顯示在控制中心（請洽詢服務供應商有關您的對講機組態設定）。\n\n重要 – 謹記事項\n\n當無法從多個衛星取得適當的訊號時（通常是因爲您的 GPS 天線所在位置無法看到開闊天空），您的對講機的 GPS 功能將沒有作用。此類情況包括但不限於：\n\n- 在地下地點\n- 在隧道或車庫內\n- 在任何其他金屬或水泥屋頂或結構之下\n- 靠近功率強大的無線電或電視塔\n- 當 GPS 天線被蓋住時（例如，以手或其他物體）或面向地面\n- 在溫度超出對講機操作限制範圍過大的環境\n\n即使在此種情況下仍可計算位置資訊，所需的時間可能會較長。因此，在任何緊急呼叫中，請隨時向您的調度員報告您的位置。此外，請注意即使可從多個衛星取得充足的訊號，您的 GPS 功能也只能提供大致位置，通常與您實際位置相差 20 - 100 公尺。\n\n**增強 GPS 效能**\n\n有時對講機的 GPS 功能可能無法成功完成位置計算。此時會出現訊息指出對講機無法取得充份的衛星訊號。為使對講機的定位能力提升到最大，請依循以下準則：\n\n- 當對講機與開闊天空之間無遮蔽時，最能充份發揮 GPS 功能。可能的話，請移至戶外，離開離高樓和綠蔭。\n- 將車輛駛至接收訊號良好的地方，讓天線可無阻礙地接收到衛星訊號。GPS 衛星的訊號會傳輸至位於對講機天線中的 GPS 天線。請勿以手指或其他物體蓋住天線。\n- 請留在網路涵蓋範圍地區。視您的服務供應商而定，網路將會為對講機提供資訊以協助您更快更精確判斷您的位置。\n\n**GPS 啓用/停用 (Menu 9 2)**\n\n1. 從主功能表，按下 Menu 9 地點 – 2 介面。目前的選擇（開/關）會反白顯示。螢幕會顯示：\n \n 開 — 啓動定位服務\n \n 關 — 關閉定位服務\n\n2. 捲動至所需的選擇然後按下設定。\n\n如果 GPS 已啓用，但是對講機尚未與 GPS 衛星同步，則會出現以下待機畫面：\n\n進入 GPS 定位服務 (Menu 9)\n\n若要進入 GPS 子功能表，按下 Menu – 9 地點。\n\n位置 — 提供實際的定位資訊。\n介面 — 讓您啓用/停用 GPS 定位服務。\n計算位置的預估精確度僅為概估值，可能會與報告的大致定位資訊的實際精確度相差甚大。\n\n注意\n- 差異程度取決於您服務供應商設定的 GPS 組態設定。\n- GPS 定位功能表的可用性取決於對講機的組態設定，請洽詢您的服務供應商以取得更多資訊。\n\n檢視您的位置 (Menu 9 1)\n\n1. 從主功能表，按下 Menu – 9 地點 – 1 位置。\n2. 此畫面會顯示下列有關您上次計算位置的資訊（如果有的話）：\n UTC — 上次計算位置時的時間。\n LAT — 緯度，以度、分和秒表示。\n LNG — 經度，以度、分和秒表示。\n SAT — 計算位置時使用的衛星個數。一般而言，衛星個數更多，計算的結果就更精確。\n3. 捲動以檢視整個畫面。\n\n若要再次計算您的位置，請按下更新。您的對講機可能需要幾分鐘的時間來判斷您的位置。在此期間，您的對講機通常會出現訊息：\n\n顯示衛星不足，或\n顯示資料不足。\n\n有關取得最佳定位計算結果的秘訣，請參閱第 62 頁的「增強 GPS 效能」。\n\n位置畫面會顯示更新資訊。若要取消之前完成的定位計算：\n\n- 按下返回以回到上一個畫面。\n\n每次對講機計算的大致位置後，會將最新的位置資訊儲存在您的對講機中，即使對講機關機仍會保留此項資訊。在下次檢視位置畫面時，將會看到此項資訊。\n\n在嘗試判斷您的位置時，如果接收到對講機通話或提示時，位置畫面將會消失，但是您的對講機仍會嘗試判斷您的位置。如果計算成功，當下次檢視位置畫面時，將會顯示新的定位資訊。\n\n進入功能表選項\n\n在通話期間您可進入功能表選項。如果您在檢視功能表時要撥號，對講機將會退出功能表。\n\n使用捲動方式\n\n1. 從任意模式，按下 Menu 即可進入功能表。\n2. 若要捲動至所需的選項（例如 2 電話簿）然後按下 Menu 或 ▶。\n3. 若要進入該選項，按下確認。\n 如果子功能表包含更詳細的子功能功能表項目集，如下例所示，重複步驟 2 和 3。\n\n使用功能捷徑\n\n您可將選項旁的號碼當成功能捷徑，以進入所需的子功能表。\n\n1. 在任意模式中，按下 Menu。\n2. 輸入所需選項的對應數字。\n 例如，若要進入 2 電話簿 – 1 私人 – 4 記憶體使用量，則可按下 Menu 然後依序鍵入選項號碼 214。\n\n退出功能表選項\n\n若要退出此功能表或子功能表，請按下返回或 ▶。\n\n退出功能表\n\n從任意功能表選項按住返回。螢幕會返回進入功能表之前的模式。\n\n注意 如果您的服務供應商已啓用此功能，當偵測到經過一段預設時間無按鍵時，功能表就會逾時。\n\n功能表選項清單\n\n1 訊息\n 1 傳送狀態\n 2 收件箱\n 3 傳送訊息\n 1 新增\n 2 範本\n 3 預先定義\n\n2 電話簿\n 1 私人\n 1 新增 ID/新增電話/新增分機\n 2 字母順序\n 3 依位置\n 4 記憶體使用量\n 2 電話\n 3 PABX\n 4 我的群組\n 1 選擇\n 2 查看\n 3 新增群組\n 1 新增 TMO\n 4 移除群組\n 2 新增 DMO\n 5 全部移除\n\n3 保密\n 1 鍵盤鎖定\n 2 PIN 保護\n 1 開\n 2 關\n 3 更換密碼\n 4 空中加密\n 5 K 值有效性\n 6 TMSCK 值有效性\n 7 直通保密碼有效性\n 8 隱密模式\n 1 開\n 2 關\n 9 直通保密碼\n\n4 設定\n 1 鈴聲\n 1 鈴聲類型\n 1 雙工 < 9 類型 >\n 2 單工 < 9 類型 >\n 2 按鍵音\n 1 開\n 2 關\n 3 所有鈴聲\n 1 開\n 2 關\n 4 通話允許\n 1 無鈴聲\n 2 短鈴聲\n 3 標準鈴聲\n 5 週期警告\n 1 警告\n 2 週期\n 2 語言\n 1 English\n 2 簡體中文\n 3 繁體中文\n 4 < 用戶定義 >\n 3 數據設定\n 1 僅話音\n 2 僅數據\n 3 選擇話音數據\n 4 背光\n 1 手動\n 2 半自動\n 3 自動\n 4 停用\n 5 到 6:請參閱下一頁\n\n| 功能表選項清單（續上頁） |\n|------------------------|\n| 4 設定（續上頁） |\n| 5 時間與日期 |\n| 1 顯示 |\n| 2 設定 |\n| 3 時差設定 |\n| 4 時間顯示格式 |\n| 5 日期顯示格式 |\n| 6 配備型態 |\n| 1 標準音 |\n| 2 手持機 |\n| 3 外掛 |\n| 4 外部與標準 |\n| 5 本機號碼 |\n| 1 私人號碼 |\n| 2 電話號碼 |\n| 6 網絡 |\n| 1 網絡選擇 |\n| 1 僅原登記網絡 |\n| 2 選擇網絡 |\n| 2 操作模式 |\n| 1 集群模式 |\n| 2 直通模式 |\n| 3 TXI 模式 |\n| 1 啓動 |\n| 2 停用 |\n| 7 掃瞄 |\n| 1 掃瞄中 |\n| 2 使用中的清單 |\n| 3 掃瞄清單 |\n| < 40 個清單 > |\n| 1 新增群組 |\n| 2 查看清單 |\n| 3 編輯清單 |\n| 4 重新命名 |\n| 5 清除清單 |\n| 8 通話記錄 |\n| 1 所有撥出 |\n| 2 所有來電 |\n| 3 未接來電 |\n| 9 更多 ... |\n| 1 地點 |\n| 1 位置 |\n| 2 介面 |\n| 2 封包資料 |\n| 1 已傳送 |\n| 2 已接收 |\n| 3 頻寬 |\n| 4 加密 |\n\n有些功能表編號可能和此處列出的不同。因為您的服務供應商可能會啓用/停用某些選項，所以會使實際的功能表索引編號有所出入。\n\n訊息（Menu 1）\n\n請參閱第 90 頁的「訊息」以取得詳細資訊。\n\n電話簿（Menu 2）\n\n若要進入電話簿子功能表，請按下 Menu – 2 電話簿。\n\n- 此子功能表可讓您新增、搜尋、編輯或清除私人、電話和 PABX 電話簿中的記錄。\n\n注意 更新私人通話電話簿的方式和更新電話通話與 PABX 通話電話簿的方式相同。當使用功能捷徑進入相關功能表時，請確定使用第 66 頁功能表選項清單上的正確編號順序。\n\n注意 如果您的服務供應商已設定此功能，則無法新增或編輯或撥打電話簿中的記錄項目，或撥打不在電話簿中的號碼。您將無法使用新增、編輯和刪除電話簿中連絡人等功能表項目。\n\n- 選擇、檢視、新增或移除最愛群組。\n\n更新私人通話電話簿（Menu 2 1）\n\n若要進入私人子功能表，按下 Menu – 2 電話簿 – 1 私人。\n\n此子功能表可讓您編輯私人通話電話簿。\n\n新增號碼（Menu 2 1 1）\n\n若要進入子功能表，\n\n按下 Menu – 2 電話簿 – 1 私人 – 1 新增 ID。\n\n注意 1 新增 ID 會變更為 1 新增電話或 1 新增分機，視您要編輯的電話簿而定。\n\n1. 按下增加。MTM800 將會提示您新增項目至現有清單中。此項目包含號碼、姓名和位置。請先輸入號碼和姓名。\n2. 按下確認以確認輸入。然後選擇此項目在清單中的儲存位置。\n3. 第一個可用的空位置（如果有的話）會建議為儲存該項目的預設位置。您可以在位置清單中捲動選擇其他位置，或鍵入位置號碼。如果該位置已使用，則會提示您是否要覆寫儲存在該位置的現有項目。\n4. 當成功儲存項目後，螢幕會在數秒內回到新增項目畫面。\n\n依字母順序搜尋電話簿 (Menu 2 1 2) 或依位置 (Menu 2 1 3)\n\n1. 若要進入子功能表，\n 按下 Menu – 2 電話簿 – 1 私人然後 2 字母順序或 3 依位置。\n2. 按下尋找。在依字母順序排列的清單中捲動（或是在預先儲存清單中鍵入您要搜尋的姓名第一個字母）。或者，在依位置排列的清單中捲動（或鍵入位置號碼）。\n 在找到號碼後，按下 PTT 即可開始撥號。\n3. 按下選項並捲動至您的選擇：\n - 編輯項目。建議使用原始位置為儲存已編輯項目的預設位置。\n 若要選擇其他位置，請在位置清單中捲動選擇其他位置，或鍵入位置號碼。如果該位置已使用，則會提示您是否要覆寫儲存在現有位置的項目。\n 當成功儲存位置後，螢幕會回到清單畫面。\n - 清除項目。螢幕會回到清單畫面。\n\n記憶體使用量 (Menu 2 1 4)\n\n若要進入子功能表，\n按下 Menu – 2 電話簿 – 1 私人 – 4 記憶體使用量。\n此畫面會顯示目前還有多少記憶體空間可用來新增項目至電話簿。\n\n我的群組（Menu 2 4）\n\n在此功能表中，選擇 2 電話簿 - 4 我的群組。此子功能表可讓您編輯您的最愛群組清單。\n\n進入我的群組（Menu 2 4 1）\n\n1. 在此功能表中，選擇 2 電話簿 - 4 我的群組 - 1 選擇。我的群組會顯示為選取的範圍別名。您現在可以在最愛群組清單中捲動瀏覽。按下確認即可選擇。\n\n注意 我的群組範圍會列為最後一個範圍。因此，在我的群組範圍中捲動到最後一個群組之後，再往下捲動就會回到第一個有效範圍。\n\n當選擇「我的群組」而目前的 DMO/TMO 模式中尚無群組時，則可能會強制您從 DMO 切換至 TMO 或從 TMO 切換至 DMO。在此情況下，將會提示您接受模式變更。\n\n檢視我的群組（Menu 2 4 2）\n\n1. 在此功能表中，選擇 2 電話簿 - 4 我的群組 - 2 查看。\n2. 在最愛群組清單中捲動。\n\n新增群組至我的群組（Menu 2 4 3）\n\n1. 在此功能表中，選擇 2 電話簿 - 4 我的群組 - 3 新增群組。\n2. 選擇以下其中一項：\n\n 新增 TMO — 您可以選擇任一 TMO 範圍/群組。\n\n 新增 DMO — 您可以選擇任一 DMO 範圍/群組。\n\n將群組從我的群組中刪除（Menu 2 4 4）\n\n1. 在此功能表中，選擇 2 電話簿 - 4 我的群組 - 4 移除群組。\n2. 選擇您要移除的群組。在「移除？」畫面中，選擇是 以確認移除。\n\n將所有群組從我的群組中刪除（Menu 2 4 5）\n\n1. 在此功能表中，選擇 2 電話簿 – 4 我的群組 – 5 全部移除。\n2. 在「移除？」提示畫面中，選擇是 以確認移除。\n\n保密（Menu 3）\n\n若要進入保密子功能表，請選擇 3 保密。\n\n將鍵盤鎖定/解鎖（Menu 3 1）\n\n為防止不慎按下按鍵：\n\n1. 從功能表，選擇 1 鍵盤鎖定。除了開/關按鈕以外的所有按鍵均會鎖定。\n\n注意 當鍵盤鎖定時若有來電，您仍可使用 PTT、和拒絕。\n\n2. 若要將鍵盤解除鎖定，請按下 Menu 3 1。\n\n注意 緊急鍵不會鎖定。進入緊急模式將會解除鎖定所有按鍵。\n\nPIN 保護（Menu 3 2）\n\n您的服務供應商已設定網路存取保護：\n\n無網路操作存取權限 — 您只能傳送或接聽緊急呼叫。在下次開機時裝置鎖定將會生效。\n\n若要保護網路操作存取：\n\n1. 按下 Menu – 3 保密 – 2 PIN 保護。\n2. 選擇 1 開即可設定保護功能（或 2 關以取消保護功能）。\n3. 在密碼？提示下，輸入 4 位數密碼（出廠設定為 0000）。為避免 PIN 遭洩露，輸入時會顯示星號而非密碼數字。按下確認。螢幕會顯示下列其中一個訊息：\n\n本機已被鎖 — 您輸入正確的密碼。螢幕會返回保密子功能表，並顯示作用中的設定：1 開。\n\n本機已解鎖 — 您輸入正確的密碼。螢幕會返回保密子功能表，並顯示作用中的設定：2 開。\n\n若要在開機後將 MTM800 解除鎖定，請在出現提示時輸入密碼。MTM800 會進入預設的首頁畫面。\n\n如果您輸入錯誤的密碼，將會出現下列訊息：\n\n輸入錯誤的密碼 — 提示您重試。在連續 3 次輸入失敗後，MTM800 將會被封鎖。\n\n如何將 MTM800 解除封鎖\n\n螢幕會顯示「本機已封鎖」。當 MTM800 已封鎖時，您就無法傳送或接聽通話。您只能輸入密碼或是將 MTM800 關機。\n\n若要將 MTM800 解除封鎖，請輸入 PUK（個人解鎖金鑰）。PUK 為 8 位數主密碼，可向服務供應商索取。\n\n在成功輸入 PUK 後，將會提示您更換您忘記的 PIN 密碼。\n\n在新密碼？提示下，輸入 4 位數密碼，並重複此密碼以確認。如果密碼不符，將會提示您再次輸入直到新密碼已被接受。\n\n更換密碼 (Menu 3 3)\n\n注意 標準出廠鎖定密碼是「0000」。\n\n若要變更 PIN 密碼：\n\n1. 捲動至 3 更換密碼，然後按下確認。\n2. 在舊密碼？提示下，輸入 4 位數密碼。\n - 如果在驗證時舊密碼不符，螢幕會顯示「輸入錯誤密碼」訊息，並回到保密子功能表。\n - 如果輸入的密碼符合舊密碼，螢幕會提示您輸入新的 4 位數密碼並重複輸入此密碼以確認。如果確認密碼與新密碼不符，螢幕會提示您重新輸入新密碼。\n3. 在接受新密碼後，螢幕會返回保密子功能表。\n\n空中加密啓動/關閉 (Menu 3 4)\n\n若要進入子功能表，請按下 Menu – 3 保密 – 4 空中加密。\n此子功能表可讓您檢視空中加密啓動/關閉狀態。\n通話加密可為您和系統之間提供服務保密。\n如果加密已啓用而您接收到未加密的通話，MTM800 將會顯示「直通（無保密）」訊息。\n\n注意 您無法從功能表手動停用空中加密（如果已啓用）。此功能表項目僅會指出當時空中加密是否已啓用。\n\n注意 空中加密功能是否啓用僅能由您的服務供應商決定。\n\n空中加密金鑰刪除\n\n請洽詢您的服務供應商以瞭解對講機是否隨附空中介面加密金鑰。\n您可使用鍵盤依序進行以下輸入，將空中介面加密金鑰從對講機刪除：**00##\n\n小心 使用此功能將會停用對講機，而必須由您的服務供應商將它重新啓用。\n\nK 值有效性 (Menu 3 5)\n\n在功能表中，選擇 3 保密 – 5 K 值有效性。\nK（金鑰）是基礎設施在系統中用來驗證 MTM800 的秘密金鑰。它是驗證的一部分，可為您的 MTM800 和系統之間提供服務保密。\n若要驗證 K 值的有效性，請按下確認。螢幕會顯示下列其中一個訊息：\nK 值有效 — 基礎設施可驗證您的 MTM800。\nK 值無效 — 基礎設施無法驗證您的 MTM800。請洽詢您的服務供應商以還原您 MTM800 的 K 值。\n\nTMSCK 值有效性？（Menu 3 6）\n\n在功能表中，選擇 3 保密 – 6 TMSCK 值有效性？\n\nSCK（靜態加密金鑰）是基礎設施在系統中用來加密通話和資料的秘密金鑰。空中介面加密服務可為您的 MTM800 和系統之間提供服務保密。您的 MTM800 在交運時應已設定一組 SCK。\n\n若要驗證 TMO 的 SCK 值是否有效，請按下確認。螢幕會顯示下列其中一個訊息：\n\n- **TMSCK 值有效** — 您的 MTM800 可在 TMO 中使用加密操作。\n- **TMSCK 值無效** — 您的 MTM800 無法在 TMO 中使用加密操作。請洽詢您的服務供應商以還原您 MTM800 的 SCK 值。\n\n直通保密碼有效性？（Menu 3 7）\n\n在功能表中，選擇 3 保密 – 7 直通保密碼有效性？\n\nSCK（靜態加密金鑰）是基礎設施在系統中用來加密通話和資料的秘密金鑰。空中介面加密服務可為您的 MTM800 和系統之間提供服務保密。您的 MTM800 在交運時應已設定一組 SCK。\n\n若要驗證 DMO 的 SCK 值是否有效，請按下確認。螢幕會顯示下列其中一個訊息：\n\n- **直通保密碼有效** — 您的 MTM800 可在 DMO 中使用加密操作。\n- **直通保密碼已失效** — 您的 MTM800 無法在 DMO 中使用加密操作。請洽詢您的服務供應商以還原您 MTM800 的 SCK 值。\n\n隱密模式（Menu 3 8）\n\n從主功能表，選擇 3 保密 – 8 隱密模式。\n\n**將隱密模式設為啓動**\n\n選擇開。所有鈴聲都會設為關，而且會立即停用背光和 LED。\n\n注意 音訊會透過外部揚聲器傳出，直到揚聲器關閉。在隱密模式中，建議您使用例如電話聽筒。\n\n將隱密模式設為關閉\n\n選擇關。會還原所有鈴聲和背光設定。LED 將會啓用而且會顯示「隱密模式關」。\n\n直通保密碼 (Menu 3 9)\n\n在功能表中，選擇 3 保密 – 9 直通保密碼。\n當您選擇此選項時，將會顯示「密鑰版本」。\n空中介面加密服務可為在直通模式下操作的 MTM800 和其他對講機或對講機群組提供服務保密。\n您可變更目前的密鑰（如果您的服務供應商允許變更密鑰的操作）。\n若要變更密鑰（如果不在通話中），選擇下一個。螢幕會顯示以下訊息：新密鑰 ...\n- 選擇是 以變更密鑰。螢幕會出現「啟動新密鑰」。\n- 選擇否 即會離開密鑰。螢幕會出現「密鑰版本」。\n\n設定 (Menu 4)\n\n若要進入子功能表，按下 Menu – 4 設定 – 確認。\n此子功能表可讓您變更 MTM800 組態：按鍵音、語言、鈴聲類型、時間、日期或數據設置。\n\n設定鈴聲類型 (Menu 4 1)\n\n此選項可讓您設定來電的鈴聲類型。您的 MTM800 針對雙工和單工呼叫提供 9 種可選擇鈴聲類型。\n\n1. 按下 Menu – 4 設定 – 1 鈴聲類型 – 1 雙工或 2 單工。\n2. 捲動至所需類型然後按下設定。螢幕會顯示您的新選擇。\n 您會立即聽到新鈴聲類型播放數秒。如有需要，請轉動音量旋鈕以調整音量。\n\n設定螢幕的使用語言 (Menu 4 2)\n\n在設定功能表中，選擇 2 語言。\n螢幕上會顯示目前使用的語言。您可以使用英文、簡體中文、繁體中文或您服務供應商定義的語言來操作 MTM800。出廠預設設定為英文。\n捲動至所需語言然後按下設定。螢幕會顯示選取的語言約數秒。\n\n設定數據模式 (Menu 4 3)\n\n您可將 MTM800 連接至外部裝置（例如筆記型電腦或桌上型電腦）。MTM800 將可以與外部裝置之間傳輸和接收資料。外部裝置上必須執行符合 TETRA 標準的應用程式。\n在設定功能表中，選擇 3 數據設置。\n螢幕上會顯示目前的設定：\n\n僅話音 — MTM800 只能接收和傳送語音通話。\n僅數據 — 把 MTM800 當成數據機使用。MTM800 將會拒絕接收和傳送語音通話（緊急呼叫除外）、狀態和文字訊息。\n選擇話音數據 — 把 MTM800 當成數據機使用，但是語音通話的優先性高於數據通話，所以會中斷數據通話。\n捲動至所需設定然後按下設定。\n\n在僅數據和選擇話音數據模式中，當您將 MTM800 連接至外部裝置而且 MTM800 準備進行資料傳輸時，就會顯示「數據已連接」圖示。此資料傳輸/接收圖示指出目前正在進行資料傳輸。\n\n當 MTM800 處於下列其中一種狀態時，MTM800 會結束環場收聽 (AL) 通話，並關閉麥克風：\n\n- 進入不在服務範圍\n- 建立外送封包資料通話\n\n若要退出資料模式，請返回 3 數據設置然後選擇僅話音。\n\nMTM800 會自動回到語音通訊，但是在「僅數據」模式除外。\n\n注意 資料服務僅適用於 TMO。在 TXI 模式中會封鎖資料服務。\n\n設定背光 (Menu 4 4)\n\n在設定功能表中，選擇 4 背光。\n\n此選項可讓您進行 MTM800 的背光設定（另請參閱第 24 頁的「調低螢幕亮度」）。\n\nMTM800 提供 4 種背光設定：\n\n手動 (Menu 4 4 1)\n按下 即可在 4 種亮度等級之間變更背光亮度。\n\n半自動 (Menu 4 4 2)\n按下 即可啓動或關閉背光。按下其他鍵無法啓動背光。背光會持續亮起，直到您按下 將背光關閉，或是直到預設計時器逾時。\n\n自動 (Menu 4 4 3)\n按任意鍵即可啓動背光。背光會持續亮起，直到您按下 將背光關閉，或是直到預設計時器逾時。\n\n停用 (Menu 4 4 4)\n停用背光功能。\n\n設定時間與日期功能 (Menu 4 5)\n\n在設定功能表中，選擇 5 時間與日期。\n此子功能表可讓您控制顯示的時間與日期。\n\n時間與日期顯示設定 (Menu 4 5 1)\n在設定功能表中，選擇 5 時間與日期，然後選擇 1 顯示。\n螢幕上會顯示目前的設定：\n\n1. 時間與日期 — MTM800 會顯示時間與日期。\n2. 時間 — MTM800 僅會顯示時間。日期顯示格式選項會停用。\n3. 日期 — MTM800 僅會顯示日期。時間顯示格式選項會停用。\n4. 關 — MTM800 不會顯示時間或日期。時間顯示格式和日期顯示格式選項已停用。\n\n捲動至所需設定然後按下設定。按下返回以退出。\n\n注意 基礎設施會同步時間與日期。當不在基礎設施訊號範圍時，您可手動設定值。\n\n設定時間與日期 (Menu 4 5 2)\n若要設定時間及/或日期：\n\n1. 進入設定功能表。\n2. 選擇時間與日期，然後按下確認。\n3. 選擇設定，然後按下確認。\n使用導覽鍵或是文數字鍵的 2（向上）、8（向下）、4（向左）、6（向右）鍵來輸入時間，然後按下設定。按下返回以退出。\n\n設定時差 (Menu 4 5 3)\n若要設定當地時間時差：\n\n1. 進入設定功能表。\n2. 選擇時間與日期，然後按下確認。\n3. 選擇時差設定，然後按下確認。\n\n使用導覽鍵或是文數字鍵的 2（向上）、8（向下）、4（向左）、6（向右）鍵來輸入時差，然後按下設定。按下返回以退出。\n\n注意 您可以每 15 分鐘為間隔來調整時差值，最多往前或往後調整 14 個小時。\n\n設定時間格式 (Menu 4 5 4)\n\n若要在 24 小時制和 12 小時制之間切換時間顯示格式：\n\n1. 進入設定功能表。\n2. 選擇時間與日期，然後按下確認。\n3. 選擇時間顯示格式，然後按下確認。\n\n選擇所需設定，然後按下設定。按下返回以退出。\n\n設定日期格式 (Menu 4 5 5)\n\n若要在 DD/MM/YY、MM/DD/YY 和 DD-MON-YY 之間切換顯示日期格式：\n\n1. 進入設定功能表。\n2. 選擇時間與日期，然後按下確認。\n3. 選擇日期顯示格式，然後按下確認。\n\n選擇所需設定，然後按下設定。按下返回以退出。\n\n設定鈴聲 (Menu 4 6)\n\n在設定功能表中，選擇 6 鈴聲。\n\n此子功能表可讓您啓動/停用按鍵音以及其他用於 MTM800 的鈴聲。\n\n捲動至所需設定然後按下設定。\n\n螢幕上會顯示目前的設定。當設為開時，MTM800 將會在每次按鍵時發出提示音。當設為關時，MTM800 將會關閉鍵盤音。\n\n有關鈴聲的詳細清單，請參閱第 102 頁的「鈴聲」。\n\n設定按鍵音 (Menu 461)\n若要啓動/停用每次按鍵時發出的按鍵音：\n1. 進入設定功能表。\n2. 選擇鈴聲，然後選擇按鍵音，然後按下確認。\n3. 使用導覽鍵在設定之間捲動。\n4. 選擇所需設定，按下設定，或按下返回即可退出。\n\n設定所有鈴聲 (Menu 462)\n若要啓動/停用所有鈴聲（按鍵音和 MTM800 使用的其他動作提示音）：\n1. 進入設定功能表。\n2. 選擇鈴聲，然後選擇所有鈴聲，然後按下確認。\n3. 使用導覽鍵在設定之間捲動。\n4. 選擇所需設定，按下設定，或按下返回即可退出。\n\n設定通話允許音 (Menu 463)\n您有 3 種鈴聲設定：\n無鈴聲 — 按下 PTT 時不會發出提示音\n短鈴聲 — 按下 PTT 時會發出短促的提示音\n標準鈴聲 — 按下 PTT 時會發出出廠設定的提示音\n若要變更您的通話允許音設定：\n1. 進入設定功能表。\n2. 選擇鈴聲，然後選擇通話允許，然後按下確認。\n3. 使用導覽鍵在設定之間捲動。\n4. 選擇所需設定，按下設定，或按下返回即可退出。\n\n設定週期警告 (Menu 4 6 4)\n\n週期警告會提示未接來電和未讀訊息。每次提示時，就會發出未讀訊息音並亮起琥珀色 LED。此功能可由使用者停用 / 啓用。\n\n1. 進入設置功能表。\n2. 選擇鈴聲，然後選擇週期警告，再按下確認。\n3. 選擇警告，然後選擇所需設定，再按下設定以選擇，或按下返回以退出。\n\n使用者也可以設定發出警告的間隔時間。\n\n1. 進入設置功能表。\n2. 選擇鈴聲，然後選擇週期警告，再按下確認。\n 選擇週期，然後選擇所需設定，再按下設定以選擇，或按下返回以退出。\n\n設定配件 (Menu 4 7)\n\n在設定功能表，選擇 7 配備型態。\n\n您可以選擇以下其中一個選項：\n\n標準 — 如果已連接掌上型麥克風和外部揚聲器，請選擇此選項。\n\n手持機 — 如果已連接電話聽筒，請選擇此選項。\n\n外掛 — 如果已連接外部麥克風和外部揚聲器，請選擇此選項。\n\n外部與標準 — 如果要將外部麥克風設為預設（除非按下 PTT），則選擇此選項。\n\n注意 MS/CPS 使用者必須設定配件才能使用它們。\n\n本機號碼（Menu 5）\n\n使用此功能即可隨時檢視您的私人或電話號碼。\n\n檢視私人或電話號碼（Menu 51 或 Menu 52）\n\n若要進入子功能表，\n按下 Menu – 5 本機號碼然後選擇 1 私人號碼或 2 電話號碼。\n\n您無法修改顯示的私人號碼。\n若要修改顯示的電話號碼，請按下設定。\n新電話號碼不會修改系統中的 MTM800 號碼。\n\n網絡（Menu 6）\n\n若要進入子功能表，請按下 Menu – 6 網絡。\n此子功能表可讓您選擇 MTM800 要註冊的網路，以及其所操作模式。\n\n選擇您的網路（Menu 61）\n\n此子功能表可讓您選擇對講機要註冊的網路。\n\n選擇僅原登記網路註冊（Menu 611）\n\n若要進入子功能表，按下\nMenu – 6 網絡 – 1 網絡選擇 – 1 僅原登記網路。\n\n選擇此選項可讓 MTM800 僅識別允許網路清單上的第一個網路並向該網路註冊。\n\n使用選擇網路選項註冊（Menu 612）\n\n若要進入子功能表，\n按下 Menu – 6 網絡 – 1 網絡選擇 – 2 選擇網路。\n如果您的服務供應商已設定此功能，此選項可讓您從允許網路清單手動選擇 MTM800 要註冊的網路。\n將顯示允許網路清單。\n\n捲動至所需網路然後按下設定。\n螢幕會顯示「XXX 已選取」。XXX 代表選取的網路名稱。\n在經過數秒後，螢幕就會回到網絡子功能表。\n\n注意 由您的服務供應商來確保允許您的對講機身份向清單中的其他網路註冊。某些通話群組可能無法用於其他網路。\n\n設定操作模式 (Menu 6 2)\n\n若要進入子功能表，\n按下 Menu – 6 網絡 – 2 操作模式。\n此子功能表可讓您選擇 MTM800 的操作模式。\n若要設定您的操作模式：\n\n- 選擇 2 直通模式或 1 集群模式，然後按下確認。\n\n注意 如果對講機處於傳輸抑制模式，則無法從直通模式切換至集群模式。\n\n注意 若要快速變更操作模式，您可使用其中一個可編程鍵（如果您的服務供應商已設定）。\n\n設定傳輸抑制 (TXI) 模式 (Menu 6 3)\n\n若要進入子功能表，\n按下 Menu – 6 網絡 – 3 TXI 模式。\n在進入禁止進行傳輸的地區（例如醫院或可能發生爆炸的環境）之前，請務必設定此模式。\n若要啓動 TXI 模式：\n\n- 選擇 1 啓動，然後按下確認。\n對講機將會發出「傳輸抑制」提示音。螢幕會在通話群組名稱和 TXI 模式訊息之間閃爍，然後會持續亮起橘色 LED，表示已啓動 TXI 模式。\n\n注意 在 TXI 模式中，將會封鎖所有會造成傳輸的功能表選項，而且無法變更通話群組。\n\n若要停用 TXI 模式，例如在離開禁止傳輸的地方之後：\n\n- 選擇 2 停用，然後按下確認。\n對講機會發出「傳輸抑制」提示音並回到群組模式或直通模式（如果上次選取的模式為直通模式）。\n\n掃瞄 (Menu 7)\n\n若要進入子功能表，請按下 Menu – 7 掃瞄。\n這個子功能表可讓您啓動/停用掃瞄，檢視作用中的掃瞄清單以及編輯掃瞄清單。\n\n注意 在 TXI 模式中無法啓用或停用通話群組掃瞄。\n\n設定通話群組掃瞄 (Menu 7 1)\n\n若要進入子功能表，按下 Menu – 7 掃瞄 – 1 掃瞄中。\n此子功能表可讓您啓動/停用掃瞄 MTM800 中預先定義的通話群組清單。當掃瞄功能啓動時，MTM800 將會加入來自掃瞄清單中定義的通話群組之通話群組呼叫。\n捲動至所需設定然後按下確定。如果它已設為關，畫面將會顯示以下狀態：\n\n當設為開，畫面將會顯示以下狀態：\n- 上次選取的掃瞄清單，或\n- 掃瞄清單中的第一個清單。\n如果顯示的不是所需的清單，請在掃瞄清單中捲動，然後按下設定。\n若要變更選擇：\n- 選擇 Menu – 7 掃瞄 – 1 掃瞄中 – 1 選擇清單，\n或者\n- 進入群組模式然後選擇選項 – 掃瞄 – 1 選擇清單。\n\n會出現訊息指出所有掃瞄清單都是空的。\n選擇 3 掃瞄清單以加入掃瞄清單。請參閱第 85 頁。\n當設為關時，掃瞄功能會停用。\n在完成設定後，螢幕會回到掃瞄子功能表或群組模式。\n若要檢視使用中的掃瞄清單及其通話群組狀態，請參閱下節。\n\n檢視使用中的掃瞄清單 (Menu 7 2)\n\n若要進入子功能表，\n按下 Menu – 7 掃瞄 – 2 使用中的清單。\n此子功能表可讓您檢視使用中的清單。\n螢幕會顯示下列其中一個狀態：\n• 有一個已選取但不在使用中的清單。掃瞄已關閉。\n• 沒有已選取的使用中清單。掃瞄已關閉。\n• 有一個已選取且已在使用中的清單。掃瞄功能已啓動。\n若要檢視通話群組狀態（使用中或不在使用中）優先性（如果已預先設定），按下查看，然後在通話群組之間捲動。\n\n編輯掃瞄清單 (Menu 7 3)\n\n若要進入子功能表，請按下 Menu – 7 掃瞄 – 3 掃瞄清單。\n此畫面可讓您在掃瞄清單之間捲動，依清單來檢視使用的通話群組號碼。\n若要編輯/檢視掃瞄清單的內容，請按下選項並捲動至您的選擇。\n按下確認即可選擇以下其中一個選項：\n\n1. 新增通話群組至選取的掃瞄清單。每個新增的通話群組（包括一個最愛群組）都有一個專屬範圍、名稱或號碼以及優先性（如果已預先設定）。\n • 若要選擇一個範圍，請在範圍清單中捲動。如果某一範圍中的所有通話群組均已在選取掃瞄清單中，則該範圍將不會顯示在此範圍清單中。按下確認即可選擇範圍。\n\n• 若要選擇通話群組，請從選取範圍的通話群組清單中捲動瀏覽。此清單會顯示未列於選取掃瞄清單中的通話群組。按下確認。\n• 若要設定群組的優先性，請在優先性清單中捲動瀏覽：高、中或低。\n\n來自高優先性通話群組的來電將會中斷優先性較低的進行中通話。\n來自中/低優先性通話群組的來電將不會中斷進行中的通話。\n\n2. 使用捲動方式查看使用中掃瞄清單的內容（範圍、通話群組和優先性（如果已預先設定））。\n\n3. 編輯掃瞄清單通話群組。捲動至所需的選擇然後按下選項。捲動至以下其中一個選項：\n • 若要將通話群組從選取的掃瞄清單中移除，選擇 1 移除群組然後按下確認。將會出現提示您移除選取的通話群組。經過數秒後，螢幕將會顯示選取掃瞄清單中的下列通話群組。\n • 若要變更通話群組優先性，選擇 2 優先順序然後按下確認。捲動至所需的優先性然後按下確認。在數秒後，螢幕會顯示選取通話群組的新設定。\n\n4. 若要重新命名使用中的掃瞄清單，請輸入新名稱（別名），然後按下確認。螢幕上會顯示新設定。\n\n5. 若要將所有通話群組從選取的掃瞄清單中清除，請按下是。螢幕會提示您將所有通話群組從選取的掃瞄清單移除。在數秒後，螢幕會顯示選取掃瞄清單的新設定。\n\n通話記錄 (Menu 8)\n\n您可檢視所有通話記錄：\n\n- 所有撥出\n- 所有來電 — 您已接聽的來電\n- 未接來電 — MTM800 已接到但未接聽的來電或拒絕的來電。\n\n每個通話清單最多可包含所有模式（電話、PABX 或私人）的 10 組號碼，而上次的通話則會列於清單的最上方。如有需要，會刪除舊通話記錄以儲存新通話記錄。撥打多次的號碼只會列在清單中一次。\n\n在接收到未接來電通知時，MTM800 將會顯示未接來電清單。在通話中若接到來電，該號碼會列於未接來電清單。在通話結束後，將會自動出現未接來電清單。\n\n1. 從功能表，選擇 8 通話記錄。\n2. 捲動至所需記錄然後按下確認。\n3. 在通話清單中捲動瀏覽。選擇清除即可將記錄項目從清單中移除。如有需要，可進入相關內容功能表將不含姓名的號碼儲存在電話簿。請參閱第 68 頁的「電話簿」。\n\n4. 您可以透過通話記錄中的項目撥打電話、PABX 或私人通話，視您在清單中選取的項目而定。\n\n注意 如果您的服務供應商已限制存取電話簿，則可能無法撥打不在電話簿中的號碼。\n\n5. 在結束通話後，MTM800 將會回到所有來電/未接來電/所有撥出清單，其中顯示號碼並讓您刪除號碼或將號碼儲存在電話簿中。\n\n地點定位 (Menu 91)\n\n請參閱第 61 頁的「GPS 定位服務」以取得詳細資訊。\n\n封包資料 (Menu 92)\n\n此子功能表可顯示與封包資料連線相關的統計數據。如果您的服務供應商已啓用多槽封包資料服務 (Multi Slot Packet Data Service)，則會顯示下列資訊：\n\n- 已傳送的資料量，\n- 已接收的資料量，\n- 資料階段作業的頻寬，\n- 資料加密狀態。\n\n注意 資料服務僅適用於 TMO。資料選項必須設為選擇話音數據或僅數據。（請參閱第 76 頁的「設定數據模式」）。\n\n檢視已傳送的資料統計數據 (Menu 921)\n\n1. 在封包資料子功能表中選擇 1 已傳送。\n2. 將會顯示自目前封包資料啓動後已傳送的 KB 數。\n3. 按下更多。資料流量會顯示在第二個畫面中：\n 9 kbps（例如）— 啓動的封包資料階段作業。\n 無 — 待命的封包資料階段作業。\n\n檢視已接收的資料統計數據 (Menu 922)\n\n1. 在封包資料子功能表中選擇 2 已接收。\n2. 將會顯示自目前封包資料啓動後已接收的 KB 數。\n\n3. 按下更多。資料流量會顯示在第二個畫面中：\n\n9 kbps（例如）— 啓動的封包資料階段作業。\n無 — 待命的封包資料階段作業。\n\n檢視頻寬狀態 (Menu 9 2 3)\n\n頻寬百分比代表在資料階段作業期間分配的時槽（「信道」）數。\n\n1. 在封包資料子功能表中選擇 3 頻寬。\n2. 顯示頻寬百分比：\n\n75%（例如）— 啓動的封包資料階段作業。\n無 — 待命的封包資料階段作業。\n\n注意\n\n您的服務供應商已將可分配的時槽個數上限設定為 1、2、3 或 4。頻寬百分比使用百分比的形式表示可能的時槽個數（1、2、3 或 4）。\n\n範例：\n\n如果可能分配的時槽為 4 個中的 2 個，則會顯示 50%。\n如果可能分配的時槽為 4 個中的 4 個，則會顯示 100%。\n如果可能分配的時槽為 1 個中的 1 個，則會顯示 100%。\n\n檢視加密狀態 (Menu 9 2 4)\n\n1. 在封包資料子功能表中選擇 4 加密。\n2. 將會顯示進行中封包資料階段作業的加密狀態：\n\n- 加密\n- 未加密（無加密）\n\n訊息\n\n一般說明\n\n訊息功能可讓您\n\n- 傳送狀態訊息。\n- 傳送簡訊（任意文字或依據使用者定義或預先定義的範本），以及\n- 接收文字訊息。\n\n狀態是一個數字，對應於您群組可識別的清單中預先設定的訊息。文字訊息是最多包含 140 個字元的簡短文字。\n\n注意 如果您的服務供應商已設定此功能，則只能將訊息傳送至儲存在電話簿中的私人號碼。\n\n進入訊息子功能表\n\n若要進入子功能表，請按下 Menu – 1 訊息。\n\n此子功能表可讓您\n\n- 傳送狀態訊息，\n- 讀取文字訊息，以及\n- 傳送文字訊息。\n\n捲動至您的選擇然後按下確認以進入下個螢幕。\n\n注意 當 MTM800 在訊息子功能表中仍可接聽來電。\n\n注意\n- 您無法在 TXI 模式中傳送狀態或文字訊息。\n- 在 DMO 期間，您無法在通話中傳送狀態或文字訊息。\n\n當收到新訊息時，螢幕上會閃爍 圖示（當您進入收件箱時此圖示會停止閃爍）。\n\n注意 當對講機在通話中收到新訊息時，MTM800 將會發出「收到新郵件」提示音（如果您的服務供應商已設定此功能）。\n\nMTM800 將會自動進入收件箱，而且 圖示將會停止閃爍。\n\n傳送狀態訊息 (Menu 11)\n\n1. 切換至您想要傳送狀態訊息的通話群組。\n2. 從任意模式中按下狀態，或是選擇 Menu – 1 訊息 – 1 傳送狀態 – 確認。\n3. 在本例中，午餐是上次傳送的狀態訊息。若要傳送不同的狀態訊息，請在預先定義的狀態清單中選擇，或鍵入狀態編號。若要停止捲動，請按下取消。狀態訊息會自動顯示在螢幕上。\n\n注意 此外還可從狀態子功能表，在使用者狀態範圍中鍵入一組 5 位數的狀態號碼。\n\n4. 按下 PTT 或 ，或相關單鍵數字鍵即可傳送該狀態訊息。如果您的服務供應商已啓用目標狀態功能，在狀態傳送畫面中將會額外出現一個傳送至快捷鍵。按下傳送至即可選擇要將您的狀態傳送為私人通訊或群組呼叫。\n\n若要輸入私人通話的位址，您可鍵入收件人號碼或在號碼清單中捲動，或按下 abc 以搜尋電話簿。若要傳送為群組呼叫，則可選擇附加範圍中的通話群組，然後按下 PTT 以傳送狀態訊息。\n\n螢幕會顯示下列一個傳送報告：\n\n狀態已傳送 — 螢幕會退出狀態模式。\n狀態失敗 — 螢幕會在幾秒內回到上個畫面。\n\n注意 請等到顯示傳送報告後再傳送新的狀態。\n如果您從忙碌通話群組進入狀態功能表，將會暫停音訊傳輸以便傳送您的狀態訊息。\n\n注意 如果接收到緊急群組呼叫，對講機會立即加入該新緊急呼叫。\n\n注意 如果您的服務供應商已設定此功能，則只能將狀態訊息傳送給電話簿中的私人號碼。\n\n使用收件箱 (Menu 12)\n\n收件箱清單包含新的或舊的已接收文字訊息。收件箱清單最多可容納 20 則訊息。\n\n若要進入收件箱，按下 Menu – 1 訊息 – 2 收件箱。\n\n清單的狀態將會顯示數秒：\n\n- 收到新訊息，且清單已滿 — 按下確認以確認。\n- 收到新訊息 — 按下任意鍵或等候數秒。螢幕會顯示收到的訊息。\n- 沒有新或舊的短訊息 — 畫面將會在數秒內返回上一個畫面。\n\n新訊息\n\n螢幕會顯示收到的訊息：其號碼、狀態（新/舊）、寄件人以及第一行文字訊息。\n\n按下以下其中一個按鍵：\n\n- 按下導覽鍵即可在文字訊息之間捲動。\n- 選擇讀取即可讀取完整訊息。讀取現有文字訊息後，其訊息狀態將會從新變更為舊。\n- 按下導覽鍵即可在超過一行的訊息內容中捲動（結尾會出現箭頭，表示下頁中有接續的內容）。\n\n在讀取訊息後，您可選擇選項，然後選擇以下其中一個選項：\n\n- 捲動至清除然後按下確認即可清除訊息。螢幕會顯示下則訊息（如果有的話）或訊息子功能表。\n- 選擇儲存然後按下確認即可將訊息當成範本儲存在範本清單中。\n- 捲動至轉寄，然後按下確認即可進入編輯模式。舊訊息內文會當成預設訊息。按下 PTT 或 即可撥號。輸入收件人的號碼然後按下 PTT 或 即可傳送。\n\n• 滾動至回覆，然後按下確認即可進入編輯模式。舊訊息內文會當成預設訊息，而訊息發送方則為收件人。按下 PTT 或 ，即可撥號給訊息發送方。\n\n按下返回即可回到上一個畫面。\n已讀的訊息會保留在收件箱中。\n新文字訊息將會立即顯示。如果此為未讀取訊息，則重新進入收件箱可檢視最新訊息。\n\n處理舊訊息\n\n捲動至其中一則舊文字訊息。\n\n按下選項並捲動至您的選擇：\n\n1. 捲動至讀取然後按下確認，即可顯示選取的舊訊息。\n\n在讀取訊息後，您可選擇選項，然後選擇以下其中一個選項：\n\n• 捲動至清除然後按下確認即可清除訊息。當螢幕顯示「訊息已清除」時，表示已將目前訊息從收件箱中刪除。螢幕會顯示下則訊息（如果有的話）或訊息子功能表。\n\n• 選擇儲存然後按下確認即可將訊息當成範本儲存在範本清單中。\n\n• 捲動至轉寄，然後按下確認即可進入編輯模式。舊訊息內文會當成預設訊息，而預設的訊息發送方則為收件人。按下 PTT 或 即可撥號。輸入收件人的號碼然後按下 PTT 或 即可傳送。\n\n• 捲動至回覆，然後按下確認即可進入編輯模式。舊訊息\n\n內文會當成預設訊息，而預設的訊息發送方則為收件人。\n按下 PTT 或 ，即可撥號給訊息發送方。\n\n2. 捲動至清除然後按下確認即可清除訊息。\n3. 捲動至全部清除然後按下確認即可顯示下列訊息：\n - 選擇是 以清除收件箱中的所有訊息。\n - 按下否 即可回到上一個畫面。\n\n接收文字訊息\n\n當接收到新訊息時，螢幕上會閃爍 圖示。當您進入收件箱時，此圖示就會停止閃爍。\n\n如果 MTM800 無進行中的活動，則會自動進入收件箱。\n\n注意 有關訊息提示的資訊，請參閱鈴聲功能表中選項中的設定（第 79 頁）。\n\n注意 如果您的服務供應商已啓用 PTT 電話回覆功能，則按下 PTT 將會顯示一個清單，其中列出訊息發送方（別名或號碼）以及該則文字訊息中找到的所有號碼。然後就可以從中選擇要撥打的人。否則，PTT 將會連接至目前選取的通話群組。\n\n注意 如果您的服務供應商已設定此功能，則只能回電給儲存在電話簿中的號碼。\n\n傳送文字訊息 (Menu 13)\n\n此功能可讓您傳送新訊息、傳送使用用戶定義範本建立的訊息，或傳送使用預先定義範本建立的訊息。\n\n預先定義的範本會由您的服務供應商設定在 MTM800 中。用戶定義的範本則是指您選擇儲存在 MTM800 記憶體中的收件箱訊息或送件箱訊息。用戶定義範本也可以設定在 MTM800 中。\n\n您在傳送訊息之前可以先進行訊息編輯。當對講機待機或在群組/緊急/廣播呼叫（如果已設定）期間，您可以傳送訊息。\n\n如果已設定此功能，則當您加入群組/緊急/廣播呼叫或當呼叫結束時，會出現訊息提示。\n\n注意 在 DMO 中，會使用附加至目前通話群組的頻率傳送文字訊息。在傳送訊息之前，確定您已選取所需的通話群組。有關選擇群組的詳細資訊，請參閱第 27 頁的「選擇通話群組」。\n\n在文字訊息編輯之前或編輯期間接收群組/緊急/廣播呼叫\n\n在接聽來電時您可以在通話中開始編輯訊息。\n或者您可以開始編輯訊息，在編輯訊息期間接聽來電。\n在編輯訊息期間若要接聽來電，請按下 PTT。\n\n在群組呼叫期間傳送文字訊息（如果已設定）\n\n按下 。可能會出現以下一種情況：\n\n- 如果在開始編輯訊息之前進行呼叫 — 對講機會離開呼叫並傳送訊息。如果該呼叫仍在進行中，則對講機將會重新加入呼叫。\n- 如果在開始編輯訊息之後進行呼叫 — 對講機會離開呼叫並傳送訊息。對講機將會回到編輯模式。\n- 如果在開始編輯訊息之前或之後進行呼叫 — 對講機將會在呼叫中傳送訊息。\n\n在緊急/廣播呼叫（如果已設定）期間傳送文字訊息\n\n按下 。可能會出現以下一種情況：\n\n- 如果在開始編輯訊息之前進行呼叫。對講機會離開呼叫並傳送訊息。對講機將會回到編輯模式。\n- 如果在開始編輯訊息之後進行呼叫。對講機將會在呼叫中傳送訊息。\n\n在文字訊息編輯期間接收私人/電話/PABX 通話\n\n將會自動中斷訊息編輯，並在通話後回到訊息編輯。\n\n進入送件箱\n\n按下 Menu – 1 訊息 – 3 傳送訊息。\n\n將會出現傳送訊息子功能表。\n\n編輯、儲存和傳送新訊息\n\n1. 捲動至 1 新增，然後按下確認。將會開啓空白畫面。您可以使用鍵盤鍵入/編輯訊息。請參閱第 14 頁的「編輯文字」。\n\n2. 按下選項並捲動至您的選擇：\n\n - 捲動至傳送，然後按下確認。\n \n - 如果您的服務供應商已設定此功能，則您可以選擇傳送訊息給私人號碼或通話群組。\n \n - 否則請在電話簿中捲動選擇郵件收件人（請參閱第 69 頁）或直接輸入收件人。\n\n按下傳送或 PTT 或 以傳送訊息。螢幕會顯示下列一個傳送報告：\n\n訊息已傳送 — 指出訊息已成功傳送並已接收。\n\n訊息失敗 — 對方未收到訊息。\n\n- 捲動至儲存並按下確認即可將您的訊息加入範本清單（指定給該訊息的數字為最小可用的數字—在本例中是範本號碼 3）。\n\n注意\n\n如果您的服務供應商提供此功能，就可以從忙碌通話群組編寫和傳送文字訊息。當編輯新訊息或範本時將會暫停群組音效。在此期間，您可接收新的緊急呼叫。在接收到緊急呼叫時將會中止訊息編輯。如果接收到新的私人/電話通話，則會在通話結束後回到訊息編輯。\n\n傳送、編輯和清除用戶定義範本\n\n用戶定義的郵件範本是指已接收、新建、傳送或設定並儲存在範本清單中的訊息，可以用來傳送訊息。\n\n1. 捲動至 2 範本，然後按下確認。範本清單中的第一個範本會出現。\n\n注意 範本編號不一定要連續。\n\n2. 使用導覽鍵在範本清單中捲動，然後選擇所需的範本。\n\n3. 按下選項並捲動至您的選擇：\n - 捲動至傳送，然後按下確認。\n - 請在電話簿中捲動選擇郵件收件人（請參閱第 69 頁）或直接輸入收件人。\n - 按下 PTT 以傳送訊息。\n 螢幕會顯示下列一個傳送報告：\n 訊息已傳送 — 指出訊息已成功傳送並已接收。\n 訊息失敗 — 對方未收到訊息。\n - 捲動至編輯並按下確認即可依需要編輯範本中的訊息。\n - 捲動至清除然後按下確認即可清除目前的範本。\n\n傳送和編輯預先定義範本\n\n預先定義的郵件範本是指由您服務供應商在 MTM800 中設定的範本。您可以對預先定義範本進行有限的編輯操作並傳送它，但是您無法儲存編輯過的範本或將它從範本清單中刪除。\n\n1. 捲動至 3 預先定義，然後按下確認。\n 將會顯示預先定義範本清單中的第一個範本（如果無預先定義範本，則會顯示「無預先定義」訊息）。\n\n2. 使用導覽鍵在範本清單中捲動，然後選擇所需的範本（在本範例中，會顯示註冊訊息）。\n\n注意 預先定義的訊息只能從編輯畫面傳送。\n\n3. 按下編輯。此訊息會出現在預先定義的訊息編輯器中。\n\n4. 輸入您的訊息。\n - 若要將游標向前移動 – 按下 。\n - 若要將游標向後移動 – 按下 。\n - 按下清除即可將游標左側的第一個字元刪除。\n\n注意 您的服務供應商在設定時也會定義預先定義訊息位址，您無法變更它。\n\n5. 按下 PTT 或 ，或相關單鍵數字鍵即可傳送訊息。螢幕會顯示下列一個傳送報告：\n 訊息已傳送 — 指出訊息已成功傳送並已接收。\n 訊息失敗 — 對方未收到訊息。\n\n在傳送訊息後，MTM800 將會回到預先定義範本選擇畫面。\n\n注意 當 MTM800 在等待訊息確認時，您將無法傳送下一則訊息。\n\n當 MTM800 閃爍顯示下列訊息時：\n\n| 訊息 | 訊息說明 |\n|--------------------|-------------------------------------------------------------------------|\n| ...... 模式清單是空的 | 未在捲動清單中設定項目。請鍵入項目。 |\n| ....-已接收 | 接收到呼叫但未回接聽或已拒絕。 |\n| 附件失敗 | 對講機無法附加通話群組。請嘗試其他通話群組。 |\n| 認證失敗 | 對講機無法向認證系統註冊（例如，認證金鑰不正確或對講機已停用認證）。 |\n| 通話已取消 | 頻道故障。請稍後重試。 |\n| 通話結束 | 頻道故障。請稍後重試。撥打的對講機已結束通話。 |\n| 通話已阻塞 | 頻道已優先使用。 |\n| 緊急麥克風結束 | 緊急麥克風計時器會自動逾時，或用戶已按下 PTT 按鈕以取消緊急麥克風功能。 |\n| 緊急麥克風啓動 | 緊急麥克風功能已啓動，對講機會自動傳輸免持緊急音訊。 |\n| 空白項目 | 您撥打的記憶位置號碼不存在，或此號碼存在但是此群組無法選取。 |\n| 裝置故障錯誤 … | 自我測試已失敗。已偵測到對講機發生操作故障。請記下錯誤編號。將對講機關機並連絡客服。 |\n| 群組已存在 | 您嘗試新增的群組已在我的群組範圍中。 |\n| 群組模式無群組 | 檢查選取的群組，而且未選取「無群組」。如果選取了正確的群組，則可能是附加作業失敗。對講機已從目前的通話群組卸除。請等待對講機再次附加目前通話群組。 |\n| 無效的 ID | 輸入的號碼無效。 |\n| 無項目 | 允許進行緊急呼叫、緊急通報和行動性操作（例如附加群組）。其他所有來電或撥出通話以及資料服務均已封鎖。 |\n| 有限服務 | 尚未附加掃瞄清單中的所有通話群組。 |\n| 已附加部份清單 | 掃瞄清單已作用，但是尚未將所有通話群組附加至清單。 |\n| 訊息已傳送 | 郵件已成功傳送。 |\n| 訊息失敗 | 郵件傳送失敗。 |\n| 我的群組是空的 | 當我的群組範圍時空的，您無法檢視/刪除群組。 |\n\n| 訊息 | 訊息說明 |\n|--------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 我的群組已滿 | 您無法新增群組至我的群組範圍，因為資料夾包含的群組數已達允許上限。 |\n| 網路故障 | 網路問題。請稍後再重試。 |\n| 無回應 | 對方未接聽。 |\n| 無項目 | 電話簿清單是空的。 |\n| 無群組 | • 當您不在所選通話群組的正常涵蓋範圍時會顯示此訊息。此時您必須選取在您工作地點中有效的新通話群組。 \n • 指出最愛群組已從我的群組範圍中移除。 |\n| 無 GPS 訊號 | 請檢查 GPS 天線已正確安裝，而且天線可無阻礙地接收到衛星訊號。 |\n| 無新或舊訊息 | 收件箱是空的。 |\n| 沒有服務 | 對講機超出涵蓋範圍。 |\n| 不允許撥號 | 您無法撥打未列在電話簿中的號碼 – 如果已由您的服務供應商設定。 |\n| 不允許傳輸 | • 放開 PTT 然後再重試。 \n • 您無法傳送文字訊息或狀態訊息至未列在電話簿中的號碼 – 如果已由您的服務供應商設定。 |\n| 僅單一項目 | 在捲動清單中僅有一個設定的項目。 |\n| 過熱 | 對講機將自動關機。維持關機約 5 分鐘。 |\n| 對方忙線 | 撥打的對講機在忙線中。 |\n| 對方不在系統內 | 撥打的對講機不在涵蓋範圍。請稍後再重試。撥打的對講機已關機。請稍後再重試。 |\n| 請重試 | MTM800 無法撥號。 |\n| 請稍候連接中 | 開機期間或網路重新連接時顯示的訊息。 |\n| 註冊失敗 | 對講機無法向系統註冊。請稍後再重試。請聯絡您的服務供應商。 |\n| 服務被拒 | 無效的號碼。請洽詢服務供應商。 |\n| 無可用服務 | 在目前網路上無法使用此項服務。 |\n| 服務已限制 | 服務供應商已限制此項服務，或您尚未購買此項服務。 |\n| 單一通話群組 | 在捲動清單中僅有一個設定的項目。 |\n| 通話群組 ... 已新增 | 群組名稱已新增至最愛的通話群組範圍。 |\n| 請稍後重試 | 要求的服務暫時無法使用。 |\n| 裝置已停用 | 請洽詢服務供應商。 |\n\n| 訊息 | 訊息說明 |\n|------------|------------------------------------------------------------------------|\n| 裝置正常警告 ... | 自我測試發生錯誤。已偵測到對講機發生輕微故障。對講機仍可正常運作。若再次發生此錯誤，請記下此錯誤代碼並洽詢服務供應商。 |\n| 裝置未附加 | 無法將對講機附加至系統。可能是未在系統中定義此通話群組。請嘗試其他群組。 |\n| 等待麥克風 | 緊急麥克風功能已啓動，但是已對相同通話群組的另一個緊急呼叫提供頻道傳送許可。此時對講機的麥克風沒有作用，但是對講機將會在經過預先定義的時間後自動嘗試取得通話許可。 |\n\n| 說明 | 類型 | 重複 |\n|----------------------------------------------------------------------|------|------------|\n| **待機** | | |\n| • 返回首頁畫面 | □ | 一次 |\n| • 當旋鈕捲動功能計時器已達逾時時間，就會返回旋鈕音量調整功能 | □ | 一次 |\n| • 返回涵蓋範圍 | □ | 一次 |\n| • 返回完整服務 | □ | 一次 |\n| 清除以傳送 | □ | 一次 |\n| 按鍵無效 | ▼ | 一次 |\n| • 按鍵有效 | □ | 一次 |\n| • MTM800 開機時自我測試失敗 | □ | 一次 |\n| • 從不在服務範圍進入服務範圍 | □ | 一次 |\n| **通話中** | | |\n| • 通話清除警告 | ▼ | 一次 |\n| • 通話已修改 | ▼ | 一次 |\n| 當有待接來電或私人通話時，發出通話待接音 | ▼ ▼ | 每 6 秒一次，直到通話結束 |\n| 已數據連接或中斷數據連接。 | □ | 一次 |\n| 按下 PTT 時發出通話允許音 | ▼ ▼ ▼ | 一次（標準提示音） |\n| | ▼ | 一次（短提示音） |\n| 按下 PTT 時允許不透過閘道通話。此提示音表示閘道無法使用。 | □ □ □ | 兩次 |\n| | ▼ | 一次 |\n\n| 說明 | 類型 | 重複 |\n|----------------------------------------------------------------------|------------|--------------------|\n| • 禁止通話<br>• 系統忙碌<br>• 逾時計時器已達逾時時間<br>• 要通話的 MTM800 不在系統內或忙線中 | [低音] | 直到放開 PTT |\n| 由於網路的關係，通話中斷或失敗 | [低音] | 一次 |\n| 撥號錯誤 | | 無鈴聲 |\n| 進入 DMO（直通模式） | [高音] | 一次 |\n| 退出 DMO | [低音] [低音] [低音] | 一次 |\n| 本端站台中繼 — 進入/退出 | [高音] | 一次 |\n| 電話答鈴（傳送） | [低音] [低音] | 每 3 秒一次，直到對方接聽或通話被拒 |\n| 電話忙線 | [低音] [低音] | 每 0.5 秒一次 |\n| 狀態訊息已傳送至調度員或傳送失敗。 | [高音] [高音] | 兩次 |\n\n### 來電\n\n| 說明 | 類型 | 重複 |\n|----------------------------------------------------------------------|------------|--------------------|\n| 調度員已確認狀態訊息 | [高音] [高音] [高音] [高音] | 四次 |\n| 您的 MTM800 未透過閘道接收到群組呼叫（僅設定） | [高音] [高音] [低音] | 一次 |\n| 接收到高優先性群組呼叫 | [高音] [高音] [高音] | 一次 |\n| 已傳送或接收到緊急通報 | [高音] [高音] | 兩次 |\n| 緊急通報失敗 | [高音] [高音] [高音] | 四次 |\n| 已接收到緊急呼叫 | [高音] [高音] [高音] | 一次 |\n| 電話鈴聲，全雙工私人通話（接收） | 依鈴聲類型子功能表中的設定而定 | 直到您接聽或拒絕通話 |\n\n| 說明 | 類型 | 重複 |\n|-----------------------------|------------|------------------------------------------|\n| 接聽私人通話 | 依鈴聲類型子功能表中的設定而定 | 直到您接聽或拒絕通話 |\n| 私人通話答鈴 | [ ] [ ] [ ] [ ] | 直到接聽來電 |\n| 半雙工私人優先通話 (PPC) 鈴聲 | [ ] [ ] [ ] [ ] | 每 4 秒一次，直到接聽或拒絕通話 |\n| 全雙工私人 PPC 鈴聲 | [ ] [ ] [ ] [ ] | 每 4 秒一次，直到接聽或拒絕通話 |\n| 有限服務 | [ ] [ ] [ ] [ ] | 在進入有限服務區域時會響一次 |\n| 收到新郵件 | [ ] [ ] [ ] [ ] | 兩次 |\n| 新群組呼叫 | [ ] [ ] [ ] [ ] | 一次 |\n\n### 一般說明\n\n| 說明 | 類型 | 重複 |\n|-----------------------------|------------|------------------------------------------|\n| 音量設定（聽筒、鍵盤、揚聲器） | [ ] [ ] [ ] [ ] | 連續 |\n| 音量設定（鈴聲） | [ ] [ ] [ ] [ ] | 在設定音量時 |\n| 傳輸抑制 (TXI) | [ ] [ ] [ ] [ ] | 一次 |\n| 旋鈕音 | [ ] [ ] [ ] [ ] | 一次，當從清單控制切換至音量控制時 |\n| 電量不足提示 | [ ] [ ] [ ] [ ] | 重複 |\n| DTMF (0-9, #, *)，在通話期間 | DTMF [ ] [ ] [ ] [ ] | 連續，直到使用者放開按鍵 |\n\n### GPS\n\n| 說明 | 類型 | 重複 |\n|-----------------------------|------------|------------------------------------------|\n| GPS 在涵蓋範圍內 | [ ] [ ] [ ] [ ] | 一次 |\n| GPS 超出涵蓋範圍 | [ ] [ ] [ ] [ ] | 一次 |\n\n**注意** 您的服務商可針對未接來電和未讀訊息設定定期提示音。\n\nA\nAL（環場收聽）22, 56\nATG（公告通話群組）26\n\nB\nBUP（忙線用戶搶佔）19\n\nD\nDGNA（動態指定群組號碼）35\nDMO\n緊急呼叫60\nDMO（直通模式操作）12, 37\nDTMF\n通話中撥號53\nDTMF（雙音多頻）53\n\nG\nGPS啓用/停用62\nGPS（全球定位系統）61\nGW（閘道）37\n\nI\nInterMNI呼叫37\nIP（網際網路通訊協定）25\n\nK\nK（金鑰）73\n\nP\nPABX（自動專用交換分機）51\nPD（封包資料）25\nPIN（個人識別碼）71\nPPC（優先通話）20\nPUK（個人解鎖金鑰）72\n\nS\nSCK（靜態加密金鑰）74\n\nT\nTMO（集群模式操作）12\nTXI（傳輸抑制）34\n\n三畫\n上次撥出的號碼46\n\n四畫\n中繼器37, 39\n公告呼叫27\n公告通話群組26\n反白顯示9\n文數字按鍵\n文字編輯14\n輸入文字14\n輸入數字14\n日期\n設定78, 79\n單鍵16\n顯示設定78\n\n五畫\n加密73\n空中加密73\n功能表13, 65\n功能表選項65\n清單66, 67\n功能捷徑65\n功能表和子功能表4\n半雙工通話45\n可用字元15\n本端站台集群23\n未接來電87\n未接來電記錄87\n目標狀態91\n\n六畫\n全球定位系統 (GPS) 61\n全雙工通話 45\n多槽封包資料 (MSPD) 服務 25\n忙線用戶搶佔 19\n自動專用交換分機 51\n\n七畫\n別名 14\n私人半雙工通話 47\n私人全雙工通話 45\n私人通話 45\n接聽 47\n私人號碼 14\n字母搜尋 47\n直接輸入 46\n清單捲動 46\n進入 46\n檢視 82\n\n八畫\n取消靜音 22\n所有來電記錄 87\n所有撥出記錄 87\n狀態訊息\n傳送 91\n直接群組呼叫\n接聽 43\n進行 41\n直通保密碼 75\n空中加密\n金鑰刪除 73\n空中加密金鑰刪除 73\n非戰術呼叫 55\n\n九畫\n亮度, 螢幕亮度 24\n封包資料 (PD) 服務 25\n背光\n亮度 24\n設定 77\n鍵 6\n\n十畫\n時差\n設定 78\n時間\n設定 78, 79\n單鍵 16\n顯示設定 78\n時間與日期 17\n記憶位置號碼 28\n記憶位置撥號 52\n訊息 90\n文字 92\n文字訊息 90\n回覆 94\n狀態 91\n狀態訊息 90\n清除 93\n轉寄 93\n\n十一畫\n動態指定群組號碼 35\n密碼 72\n接聽來電 19\n掃瞄\n清單 84\n掃瞄清單 26\n啓動/關閉揚聲器 22\n清潔您的對講機 25\n通話允許音 80\n通話佇列 50\n通話群組 26\n記憶位置號碼 28\n變更 27\n麥克風\n靜音/取消靜音 22\n麥克風靜音/取消靜音 22\n\n| 十二畫 | 電話簿 |\n|--------|--------|\n| 單站集群服務 23 | 私人通話電話簿 68 |\n| 退出 24 | 依字母順序 69 |\n| 進入 23 | 依位置搜尋 69 |\n| 單鍵 | 記憶體使用量 69 |\n| 日期 16 | 新增號碼 68 |\n| 時間 16 | 電話通話電話簿 68 |\n| 隱密模式 16 | |\n\n| 十四畫 | 圖示 |\n|--------|------|\n| 提示 | DMO 中繼器 8 |\n| 聲音和指示燈 24 | DMO 閘道 8 |\n| 最愛通話群組 26, 29, 85 | 外部警報 8 |\n| 開放群組 37 | 未讀取的訊息 8 |\n| 開機/關機 10 | 收到新訊息 8 |\n| 集群模式操作 (TMO) 12 | 私人通話來電 8 |\n| 直通模式 7 | 訊號強度 DMO 7 |\n| 訊號強度 TMO 7 | 接收/傳輸資料 8 |\n| 掃瞄 8 | 電話通話 8 |\n| 緊急呼叫 8 | 數據已連接 8 |\n| 箭頭 9 | 對講機停用/啓用 18 |\n| 緊急通報 55 | 緊急麥克風 58 |\n| 傳送 57 | 緊急麥克風 (Hot Mic) 55, 58 |\n| 緊急群組呼叫 55 | 緊急腳開關 10 |\n| 在 DMO 中接收 60 | 網絡 82 |\n| 在 DMO 中進行 60 | 網際網路通訊協定 (IP) 25 |\n| 接聽 59 | 語言 |\n| 進行 58 | 顯示語言 76 |\n\n十五畫\n撥出\n 已撥號碼清單 87\n撥打號碼 18\n數據設置 76\n標記 4\n範本 90\n 用戶定義 97\n 預先定義 97\n範圍 26\n 選擇 31\n\n十六畫\n戰術呼叫 56\n靜音 22\n頻寬 89\n\n十七畫\n優先呼叫 20\n優先性 85\n優先順序 86\n環場收聽 (AL) 22, 56, 77\n鍵\n 功能表 13\n 可編程功能 16\n 快捷鍵 13\n 背光 6\n 緊急呼叫 13\n鍵盤\n 鎖定 71\n隱密模式 10, 23\n 單鍵 16\n點火感應 10\n\n十八畫\n簡碼撥號 46\n鎖定鍵盤 71\n\n二十三畫\n顯示\n 長文字訊息 9\n 長號碼 9\n\nMTM800 Mobile Reference Guide\n\n**MTM800**\n車載台對講機\n快速參考指南\n\n### 撥打電話/PABX 通話\n\n按下 `Mode` 以選擇電話或 PABX\n\n- 按下 `PTT`\n- 撥號或自電話簿中選擇\n- 鈴聲響起\n- 對方接聽\n- 說話並收聽\n- 按下 `PTT` 以結束通話\n\n### 撥打 DMO 私人通話\n\n按下 `Mode` 以選擇私人\n\n- 按下並按住 `PTT`\n- 按下 `Menu` 622\n- 提示音響起（如果已設定）\n- 對方接聽\n- 說話\n- 放開 `PTT` 以收聽\n- 按下 `PTT` 以結束通話\n\n### 撥打 TMO 私人通話\n\n按下 `Mode` 以選擇私人\n\n- 按下並按住 `PTT`\n- 撥號或自電話簿中選擇\n- 提示音響起（如果已設定）\n- 對方接聽\n- 說話並收聽\n- 按下 `PTT` 以結束通話\n\n### 進行 TMO 群組呼叫\n\n按下 `Mode` 以選擇群組\n\n- 選擇範圍！按下再按下通話群組\n- 許可音響起\n- 說話\n- 放開 `PTT` 以收聽\n\n### 進行 DMO 群組呼叫\n\n# Contents\n\n## General Information ........................................ 1\n- Safety Information ........................................ 1\n- Disposal Information ...................................... 1\n- Copyright Information .................................... 2\n- Product Specific Information ............................. 2\n- Icon Conventions .......................................... 3\n\n## Getting Started ........................................... 4\n- How to Use this Guide .................................... 4\n- Controls and Indicators .................................. 5\n- The Display ................................................ 7\n- LED Status Indicators ..................................... 10\n- Powering On/Off ........................................... 10\n- Key Overview .............................................. 12\n- Home Mode Display ....................................... 18\n- Time & Date ............................................... 19\n- Terminal Disable/Enable .................................. 19\n- Terminal Permanent Disable ............................... 20\n- Making Calls .............................................. 20\n- VOX Control ................................................ 21\n- Receiving Calls ........................................... 21\n- Busy User Pre-emption (BUP) ................................ 21\n- Pre-emptive Calling (PPC) ................................ 22\n- Broadcast Call ............................................. 23\n- Ambience Listening (AL) ................................... 24\n- Cancelling an Incoming Call ............................... 24\n- Using In-call Features .................................... 25\n- Covert Mode ................................................ 25\n- Local Area Service ......................................... 26\n- Dimming the Display ....................................... 27\n- Adjusting the Volume ...................................... 27\n- Horn & Lights Alarm On/Off ................................ 27\n- Packet Data ................................................ 28\n- Looking after your MTM800 ................................. 28\n\nTMO Group Call .................................................. 29\n\nGeneral .............................................................. 29\nSelecting a Talkgroup ........................................... 30\nChanging a Talkgroup during/on receiving a call .......... 34\nSelecting a Range .................................................. 34\nActivating/Deactivating Scanning ............................. 34\nMaking a Group Call ............................................. 35\nReceiving a Group Call ......................................... 36\nTransmit Inhibit .................................................... 38\nDynamic Group Number Assignment (DGNA) .................. 39\n\nDMO Group Call .................................................. 42\n\nGeneral .............................................................. 42\nSelecting a Talkgroup ........................................... 43\nChanging a Talkgroup during/on Receiving a Call .......... 43\nSwitching from TMO to DMO or from DMO to TMO ........ 43\nGateway/Repeater Selection ................................... 43\nMaking a DMO Group Call (MS to MS) ........................ 46\nMaking a DMO Group Call via Gateway ....................... 47\nMaking a DMO Group Call via Repeater ...................... 47\nMaking a DMO Group Call via Gateway and Repeater ....... 48\nReceiving a DMO Group Call ................................... 49\nDMO Private Call ................................................ 50\nReceiving an Emergency Group Call .......................... 50\n\nPrivate Call ....................................................... 51\n\nGeneral .............................................................. 51\nEntering Private Mode .......................................... 51\nEntering the Private Number ................................... 52\nMaking a Private Call in TMO ................................. 53\nMaking a Private Full-Duplex Call in TMO .................. 53\nReceiving a Private Call in TMO ............................. 54\nReceiving a Private Full-Duplex Call in TMO ............... 54\nPrivate Call in DMO ............................................. 55\nDialling on Receiving a Call ................................... 56\nMaking a Private PPC (Pre-emptive Priority Call) .......... 56\nCall Queuing ....................................................... 56\n\nPhone and PABX Calls ........................................ 57\nGeneral ......................................................... 57\nMaking a Phone or PABX Call ............................... 57\nDialling on receiving a call ................................. 60\nAnswering a Phone or PABX Call .......................... 60\n\nEmergency Mode .............................................. 61\nGeneral ......................................................... 61\nEntering TMO or DMO ....................................... 62\nEntering or Exiting Emergency Mode ....................... 62\nInvisible Emergency .......................................... 63\nChanging Range or Talkgroup ............................... 63\nEmergency in TMO ........................................... 63\nEmergency in DMO ........................................... 66\n\nGPS Location Service ....................................... 68\nGeneral ......................................................... 68\nEnhancing GPS Performance ................................. 69\nGPS Enable/Disable .......................................... 70\nEntering GPS Location Service ............................. 70\n\nThe Menu ..................................................... 72\nEntering the Menu Options ................................. 72\nExiting the Menu Options .................................... 72\nExiting the Menu ............................................. 72\nList of Menu Options ........................................ 73\nMessages ...................................................... 75\nAddress Book .................................................. 75\nSecurity ......................................................... 79\nSetup ............................................................ 84\nOwn Number ................................................... 90\nNetwork ......................................................... 91\nScan ............................................................. 93\nRecent Calls .................................................... 96\nLocation ......................................................... 97\nPacket Data ..................................................... 97\n\n| Section | Page |\n|-------------------------------|------|\n| Messages | 99 |\n| General | 99 |\n| Entering the Messages Sub-menu| 99 |\n| Sending a Status Message | 100 |\n| Using the Inbox | 101 |\n| Sending a Text Message | 104 |\n| What to do if... | 109 |\n| Tones | 112 |\n| Index | 115 |\n| Quick Reference Guide | 119 |\n\nMOTOROLA and the stylized M Logo are registered in the U.S. Patent and Trademark Office. All other product or service names are the property of their respective owners.\n\n© 2007 – 2008 by Motorola, Inc.\nAll rights reserved.\n\nGeneral Information\n\nSafety Information\n\nCAUTION Before using these products, read the operating instructions for safe usage contained in the Product Safety and RF Exposure booklet (Motorola Publication part number 6866537D37 for Europe, Middle East and Africa or 6804112J96/6804113J25 for Asia and Pacific) enclosed with your terminal.\n\nThe accessories are restricted to occupational use only to satisfy ICNIRP RF energy exposure requirements. Before using the products, read the RF energy awareness information and operating instructions in the Product Safety and RF Exposure booklet to ensure compliance with RF energy exposure limits.\n\nKeep this User Guide and the Product Safety and RF Exposure booklet in a safe place and make it available to other operators, and in case, that the accessories are passed on to other people.\n\nDisposal Information\n\nThe European Union's Waste of Electrical and Electronic Equipment (WEEE) directive requires that products sold into EU countries must have the crossed out trashbin label on the product (or the package in some cases). As defined by the WEEE directive, this cross-out trashbin label means that customers and end-users in EU countries should not dispose of electronic and electrical equipment or accessories in household waste.\n\nCustomers or end-users in EU countries should contact their local equipment supplier representative or service centre for information about the waste collection system in their country.\n\nCopyright Information\n\nThe Motorola products described in this manual may include copyrighted Motorola computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyrighted computer programs including, but not limited to, the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Motorola computer programs contained in the Motorola products described in this manual may not be copied, reproduced, modified, reverse-engineered, or distributed in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the normal non-exclusive license to use that arises by operation of law in the sale of a product.\n\nProduct Specific Information\n\n- Max RF Power 3 Watts\n- Max. Speaker Load 10 Watts at 4 Ohms\n- Antenna Impedance 50 Ohms\n- Ambient Temperature Range -30 °C to +60 °C\n\n![WARNING]\n\nIf the terminal is in service the surface temperature can rise up to 70 °C.\nDo not touch the hot surface\n\nOperating Time\n\nContinuous / Intermittent\n\n**NOTE**\nIn general, the terminal transmit and receive time (operating cycle time) is determined by the communication system. On overload, respectively on extensive use beyond the systems specifications at high ambient temperatures, the terminal is protected by its thermal control, which cuts down the RF output power, thus reducing the terminal coverage range.\n\n**Icon Conventions**\n\nThe document set is designed to give the reader more visual cues. The following graphic icons are used throughout the documentation set. These icons and their associated meanings are described below.\n\n**WARNING**\nThe signal word Warning with the associated safety icon implies information that, if disregarded, could result in death or serious injury, or serious product damage.\n\n**CAUTION**\nThe signal word Caution with the associated safety icon implies information that, if disregarded, may result in minor or moderate injury, or serious product damage.\n\nThe signal word Caution may be used without the safety icon to state potential damage or injury that is not related to the product.\n\n**NOTE**\nNotes contain information more important than the surrounding text, such as exceptions or preconditions. They also refer the reader elsewhere for additional information, remind the reader how to complete an action (when it’s not part of the current procedure, for instance), or tell the reader where something is located on the screen. There is no warning level associated with a Note.\n\nGetting Started\n\nCongratulations on your purchase of the Motorola MTM800. Enhanced TETRA features and state-of-the-art technology help to keep you in constant touch with all of your work and personal contacts.\n\nYou can operate your MTM800 in English, Simplified Chinese, Traditional Chinese, or in a language defined by your Service Provider. The default setting from factory is English. For more information, please see “Setting the Display’s Working Language” on page 84.\n\nHow to Use this Guide\n\nThis guide describes the MTM800 features as setup and pre-programmed at the factory.\n\nYour Service Provider or your organisation may have customised your MTM800 to optimise its use for your individual needs. Check with your Service Provider or organisation to find out the differences from this guide. Throughout the text in this publication, you will notice the following special notations used to highlight certain information or items:\n\n| Example | Description |\n|---------|-------------|\n| Mode or Yes | Key presses are shown as a key symbol or in bold print for soft key functions. |\n| Menu 2 2 1 | Use alphanumeric keys as shortcuts to reach the required sub-menus. In this example, press Menu 2 abc 2 abc 1 ! in sequence, not simultaneously. |\n| 2 Addr. Book | Highlighted text indicates the selection. |\n| Status Sent | Information appearing on the MTM800 display are shown in special print. |\n| NOTE | A Note contains additional information which is relevant to the item feature. |\n| 6 <User Defined> | Indicates a prompt or message configured by your Service Provider |\n\nControls and Indicators\n\n1. Power On/Off Pushbutton\n2. LED indicators, red, orange, green\n3. Display Icons\n4. Alphanumeric Display\n5. Alphanumeric Keypad\n6. Backlight\n7. Function Keys\n8. External Alarm\n9. Menu Key\n10. Send/End Key\n11. Soft Keys\n12. Navigation Keys Up, Down, Left, Right\n13. Mode Key\n14. Emergency Key\n15. Microphone Connector\n16. Volume Knob\n17. PTT Button\n18. Microphone\n\n| Item | Description |\n|------|-------------|\n| 1) | **On/Off Pushbutton** \nTurns the MTM800 on and off. (See page 10.) |\n| 2) | **LED Indicators** \nIndicate the service state. (See page 10.) |\n| 3) | **Display Icons** \nShow additional information and MTM800 status. (See page 7.) |\n| 4) | **Alphanumeric Display** \nBacklit view of up to 4 lines of characters or digits (up to 16 characters or digits per line). |\n| 5) | **Alphanumeric Keypad** \nEnter numbers and alphabetic characters. (See page 14.). The function of these keys is programmable by the Service Provider. (See page 17.) |\n| 6) | **Backlight Key** \nDims and intensifies the radio’s backlight (four intensity options). (See page 27.) |\n| 7) | **Function Keys** \nThe function of these keys is programmable by the Service Provider. (See page 17.) |\n| 8) | **External Alarm Key** \nUsed to activate and deactivate the External Alarm (Horn & Lights). (See page 27.) |\n| 9) | **Menu Key** \nPress to bring up menu options. Use navigation keys to scroll. (See page 14.) |\n| 10) | **Send/End Key** \nPress to initiate full duplex calls, send text and status messages, and to end phone calls, PABX calls, full duplex and half-duplex private calls. |\n| 11) | **Soft Keys** \nPress to select the option that appears directly above the left or right key on the fourth line of the display. (See page 13.) |\n| 12) | **Navigation Keys** \nPress to move up or down through options and lists, such as message or phone address book lists. |\n\n| Item | Description |\n|------|-------------|\n| 13) | **Mode Key** \nSelect the Phone, PABX, Private, or Group mode. (See page 12.) |\n| 14) | **Emergency Key** \nInitiates Emergency mode and sends Emergency Alarms. (See page 14.) |\n| 15) | **Microphone Connector** \nConnector for a Fist or Desk microphone with PTT button, or the Telephone Style handset. |\n| 16) | **Volume Knob** \nAdjusts the volume level. (See page 27.) |\n| 17) | **Push-To-Talk Button (PTT)** \nPress to: \n• Send a Group, Private, or Emergency Call. \n• Send a status message. |\n| 18) | **Microphone** \nSpeak into this during communications. |\n\n### The Display\n\n#### List of Display Icons\n\nAfter you turn on your MTM800, icons appear along the top of the display to indicate the following conditions:\n\n| Icon | Description |\n|------|-------------|\n|  | **Signal Strength (TMO)** \nAllows you to check signal strength before proceeding with a call. Five bars indicate the strongest signal. Calls and messages may not be sent or received in weak signal areas. A blinking antenna shows out of coverage. Move to a location that indicates better coverage and reattempt the call. The icon is not shown in Direct Mode Group Call |\n|  | **Signal Strength (DMO)** \nIndicates an incoming Direct Mode Group Call. |\n|  | **Direct Mode** \nDisplayed when the terminal is in Direct mode. |\n\n| Icon | Description |\n|------|-------------|\n|  | **DMO Gateway** \nIndicates that you selected to work with a gateway. This icon has three states: \n**Solid** — while the terminal is synchronised with the gateway (i.e., when the terminal receives a valid presence signal). \n**Blinking** — while the terminal is not synchronised with the gateway or during attachment. \n**No icon** — during a terminal to terminal and repeater call. |\n|  | **DMO Repeater** \nDisplayed when the repeater option in DMO is selected. This icon has three states: \n**Solid** — while the terminal has detected the repeater (i.e., when the terminal receives a presence signal). \n**Blinking** — while the terminal has not detected the repeater or during attachment. \n**No icon** — during a terminal to terminal and gateway call. |\n|  | **Unread Message** \nIndicates that you have unread message in your Inbox. |\n|  | **New Message Received** \nYour Inbox could not open automatically due to an ongoing activity. The icon remains displayed to remind you of new messages in your Inbox. |\n|  | **External Alarm** \nDisplayed when External Alarm (“Horn & Lights”) is enabled. |\n|  | **Incoming Private Call** \nBlinks to indicate an incoming Private Call. The icon extinguishes if you accept or reject the incoming call or if the call setup fails. |\n|  | **Phone Call** \nBlinks when a Phone Call is received. |\n|  | **Emergency** \nAppears while the MTM800 is in Emergency mode. The icon blinks to indicate an incoming Emergency Group Call. |\n|  | **Priority Scan (with Priority Monitor Dot)** \nIndicates scanning is activated. |\n\n| Icon | Description |\n|------|-------------|\n| ![Icon] | Data Connected \nDisplayed when the MTM800 is successfully connected to the external device (laptop or desktop PC) and ready for data transfer. |\n| ![Icon] | Receiving/Transmitting Data \nThe icon indicates that data transfer is currently taking place. |\n\n**Indicating Loudspeaker On/Off**\n\n*NOTE* The Loudspeaker On/Off indication is only available in Group Mode.\n\nAn inverted talkgroup line is used when the Telephone Style Handset accessory is configured (See page 90).\n\n- If the Talkgroup line is displayed inverse, any incoming call is received through the earpiece of the handset.\n- If the Talkgroup line is not inverted, any incoming audio is received through the external loudspeaker.\n\nThe selection of handset earpiece or loudspeaker is via “Speaker On/Off” programmable buttons.\n\n**Displaying Long Numbers**\n\nThree dots after the number indicate that it continues on the next page (for example, in the address book).\n\nIf you dial a long number, each new digit entered will shift the displayed number left by one digit.\n\n**Displaying Long Text Messages**\n\nAn arrow after the text message indicate that it continues on the next page (for example, when reading a mail message). Press \\( \\text{Next} \\) to read the next page, and \\( \\text{Prev} \\) to return to the previous page.\n\nLED Status Indicators\n\nThe LED indicators show the in-service status of your MTM800.\n\n| Indicator | Status |\n|----------------------------|------------------------------------------------------------------------|\n| GREEN: Solid | In use |\n| GREEN: Blinking | In service |\n| RED: Solid | Out of service |\n| RED: Blinking | Connecting to a network / Entering DMO |\n| ORANGE: Solid | Transmit Inhibit (TXI) in service / Channel busy in DMO |\n| First solid then blinking ORANGE | Incoming call |\n| No indication | Switched off |\n\nPowering On/Off\n\nTo power on:\n- Press the **On/Off** pushbutton.\n- If the MTM800 is configured with ignition sense, the radio will automatically turn on whenever the vehicle ignition is turned on.\n- If an Emergency Foot Switch is connected to the accessory connector and “Emergency with wake up” is enabled by your Service Provider, the MTM800 automatically turns on in Emergency Mode whenever the Emergency Switch is pressed (see “Emergency Mode” on page 61).\n\nA set of icons and squares will appear on your display. (See “List of Display Icons” on page 7.) Then your MTM800 performs a self-check and system registration routine. The display shows additional information while the MTM800 is registering on the system.\n\nAfter successful registration, the MTM800 will be in service.\n\nTo power off:\n\n- Press the On/Off pushbutton again.\n- If the radio is powered on via the ignition, it can be turned off via the ignition or the On/Off pushbutton.\n\nYou will see the Powering Off message.\n\n**NOTE**\nThe terminal powers On and Off without visible and audible notification if Covert Mode is activated. (Refer to “Covert Mode” on page 25.)\n\n### Uninstalling the Radio\n\n**CAUTION**\n\n**OPTION 1:**\nBefore disconnecting the 13.2V main power supply from the radio:\n1) Switch off the radio.\n2) Wait for a minimum of 4 seconds after the radio Off Switch is released.\n Disconnect the 13.2V main power supply.\n\n**OPTION 2:**\nTurn off the main power supply WITHOUT switching OFF the radio.\n\n### Unlocking the MTM800\n\nYour MTM800 may be locked at power up. To unlock, see “Locking/Unlocking the Keypad” on page 79.\n\n### Selecting Your Network\n\nBefore you start operating your MTM800, you can select the network you want your MTM800 to be registered to. For detailed information, see “Network” on page 91.\n\n### Powering On with activated Transmit Inhibit\n\nIf the terminal has been powered Off with activated Transmit Inhibit (see “Setting Transmit Inhibit (TXI) Mode” on page 92) the TXI Mode remains active.\n\nWhen powering On with activated TXI Mode the user will be asked whether to leave the TXI Mode or not.\n\nPress the **Yes** soft key (see “The Soft Keys” on page 13) if you want to deactivate the TXI Mode – e.g. if you have left the RF sensitive area where the TXI Mode was recommended. If the MTM800 was previously used in Trunked Mode (TMO), it will register to the network.\n\nIf you press **Yes**, and the terminal was previously used in TXI and Direct Mode, it will exit TXI Mode and remain in Direct Mode.\n\nIf the terminal was previously in Trunked Mode with TXI enabled, pressing **No** will power off the terminal.\n\nIf you press **No**, and the terminal was previously used in TXI and Direct Mode, it will remain in TXI and Direct Mode.\n\n### Key Overview\n\n#### The Mode Key\n\nThe MTM800 has four major call modes when operating in Trunked Mode Operation (TMO):\n\n- **Group mode** — to send and receive Group Calls.\n- **Private mode** — to send and receive Private Calls.\n- **Phone mode** — to send and receive Phone Calls.\n- **PABX mode** — to send and receive local (office) extension numbers calls.\n\n**NOTE**\n\n*PABX mode will only be displayed if enabled by your Service Provider*\n\nIf configured by your Service Provider, Group mode is the home mode to which the MTM800 returns automatically when there is no activity for a few seconds in another mode or in the menu.\n\nGroup mode can operate either in\n\n- In **Trunked Mode Operation (TMO)** the MTM800 is used with the infrastructure services within system coverage, or\n- In **Direct Mode Operation (DMO)** the MTM800 is used without infrastructure services required.\n\nWhile operating in DMO mode the propagation travels directly from the transmitting terminal antenna to the receiving terminal antenna, with no assistance from any base station or tower. Therefore, the range is critically dependent on the position of the vehicle. Any obstructions (hills, buildings, etc.) between the TETRA terminal users will further decrease the range. Conversely, moving the vehicle to another or higher location may improve the range.\n\nA terminal in DMO can communicate with the trunking system (and vice-versa) through a gateway device. To use that feature, please enable the gateway option in your terminal (see “Gateway/Repeater Selection” on page 43).\n\n**NOTE**\n\n*It is only possible to place group and emergency group calls in DMO.*\n\nTo cycle through the Group, Private, Phone, and PABX modes, press **Mode** successively.\n\nYour display appears similar to the following default start screens for the Phone, Group, Private, and PABX modes when your MTM800 is in service.\n\n**Examples of Mode Start Screens:**\n\nThe Soft Keys\n\nPress **●** to select the option that appears in the screen directly above the left or right soft key. In this example, **abc** is displayed above the key. Pressing **●** enters the address book. In the user guide, this action is described as “press abc”.\n\nThe Menu Key\n\nPress (Menu) to enter the main menu hierarchy (when there is no on-going activity). The MTM800 menus allow you to control your MTM800 settings. Menus are organised in a hierarchy. See “List of Menu Options” on page 73. The menu options provide access to a further list of options called a sub-menu.\n\nThe example below shows how to check the available free memory in the address book. The last option appears in the first line of the display, letting you know how many options are available.\n\nThe Emergency Key\n\nThe Emergency mode, that you can start from any mode by pressing the (⚠️) key, enables you to send Emergency Alarms and initiate Emergency Group Calls.\n\n**NOTE** *Emergency mode is available in Trunked Mode and Direct Mode Operations. Emergency Alarm is a feature of Trunked Mode Operation only. The Emergency Alarm will be sent to the dispatcher (if configured by your Service Provider).* \n\n**NOTE** *The required time you need to press the Emergency key is by default set to 0.5 seconds. The time can be configured by your Service Provider.*\n\nHowever, you will be able to receive or transmit emergency calls even when the MTM800 is locked with pin protect.\n\nThe Alphanumeric Keypad\n\nUse the keypad for dialling, entering numbers into the address book, or creating SDS (Short Data Service) messages, or for one-touch dialling.\n\nEntering Numbers\n\nTo enter a number in the address book, press the corresponding number key.\n\nEntering Text (Letters and Digits)\n\nTo enter alias text in an address book or text in messages, press the key labelled with the desired character, once for the first character, twice for the second, and so on. The key has additional characters (see page 16).\n\nEditing the Text\n\n| To... | Action |\n|--------------------------------------------|---------------------------------------------|\n| Move the cursor one character to the right | Press \\( \\text{D} \\), press a new key, or wait for a short time |\n| Move the cursor from the end of the text to its beginning | Press and hold \\( \\text{D} \\) |\n| Move the cursor to a character on the left | Press \\( \\text{C} \\) |\n| Delete a character left to the cursor position | Press Clear |\n| Delete the whole text | Press and hold Clear |\n| Quit editing | Press Clear |\n\nAliases (Names)\n\nAliases are optional names that you can assign to stored phone and private numbers (or IDs).\n\nAliases can be up to 14 characters in length and may consist of letters, numbers, or spaces.\n\nAliases are displayed during memory list scrolling. Aliases are also used to retrieve numbers from your memory list.\n\nThe following screens show examples of how the caller’s private number can be displayed.\n\nPrivate ID without alias\n\nID alias (name)\n\n**Available Characters**\n\nPress the appropriate keys to display the characters listed in the table below.\n\nThe top line for each key shows the upper case characters, and the lower line shows the lower case.\n\nPress and hold \\( \\# \\) to toggle between upper and lower case.\n\n**List of Available Characters:**\n\n| Key | Alphanumerics |\n|-----|---------------|\n| 1 | , ? ! 0 1 @ \" - ( ) / : _ ; + & % × * = < > € £ $ ¥ ₱ [ ] { } \\ ~ ^ ¿ i § # |\n| 2 | A B C 2 Ä À Â Æ Ç a b c 2 ä à â æ ç |\n| 3 | D E F 3 È É Ë Ê ê d e f 3 è é ë ê |\n| 4 | G H I 4 Î Ï Ì g h i 4 î ï ì |\n| 5 | J K L 5 j k l 5 |\n| 6 | M N O 6 Ö Ô Õ Ò Ñ m n o 6 ö ô õ ò ñ |\n| 7 | P Q R S 7 p q r s 7 |\n\n### Alphanumerics\n\n| Key | Alphanumerics |\n|-----|---------------|\n| 8 | T U V 8 Ü Ù Ú |\n| | t u v 8 ü ù ú |\n| 9 | W X Y Z 9 |\n| | w x y z 9 |\n| * | Space * / % |\n| 0 | 0 + - |\n| # | # = < > |\n\n### Programmable Keys\n\nYour MTM800 supports the one-touch feature that allows you to select/activate commonly used features by pressing and holding a numeric key or one of the three function keys F1 to F3. Your Service Provider should program the numeric and option keys with the relevant features. All the numeric keys on the keypad are programmable. The following table lists the programmable features and their availability in specific MTM800 states/modes. For detailed information on the features, see the relevant section in the user guide:\n\n| Feature | Description |\n|--------------------------------|-----------------------------------------------------------------------------|\n| Talkgroup Switch | Switch to a specific talkgroup |\n| Current/Last Switch Talkgroup | Switches to the previous talkgroup (even if the operation mode was different) |\n| Talkgroup Scan | Enables/disables the Talkgroup Scan function. (TMO only) |\n| Home Revert | Puts the MTM800 back into Group mode |\n| DMO/TMO | Toggles between DMO and TMO modes. |\n| Status Message | Sends a dedicated status message to a dedicated address. (TMO only) |\n| Speaker on/off | Directs voice audio to the earpiece of the telephone style handset or to the loudspeaker. |\n\n| Feature | Description |\n|-------------------------------|-----------------------------------------------------------------------------|\n| Text Message Template | Sends a predefined/user defined template to a dedicated address. (TMO only) |\n| Call Dial (Private, Phone, PABX) | Initiates a call to a predefined entry in the address book. (TMO only) |\n| Transmit Inhibit (TXI) | Toggles between activated and deactivated TXI mode. |\n| Covert Mode | Toggles on/off covert mode |\n| Time & Date | Shows time and date. |\n\n**NOTE**\n\n*If the one-touch feature is enabled, one-touch dial is disabled (see page 59).* \n\nTo use the one-touch feature:\n\n- From any mode, press and hold the required numeric key for a few seconds.\n- Your MTM800 will display the number or function and act according to the programmed feature.\n\nOne-touch Private Call is set by the Service Provider.\n\n1. If it is set to **Simplex**, then outgoing Private Call is Simplex too.\n2. If it is set to **Duplex**, then outgoing Private Call can be duplex in TMO, Simplex in DMO with the last Group Call Originator number.\n3. If it is set to **Duplex**, then outgoing Private Call can be duplex in TMO and cannot be initiated in DMO when the phone book index is required.\n\n**Home Mode Display**\n\nYour MTM800 is provided with a feature that allows your Service Provider to send special text messages to your MTM800 display.\n\nThe message is displayed several seconds after any key press.\n\nIf configured by your Service Provider, your MTM800 will display an internal Home Mode Display until another message is received.\n\n**NOTE** This feature is used as a special reminder message to the user. Typically this would consist of a call sign, or work dispatch reference number, or even for a train run number or bus route number. New messages can be updated “over the air”.\n\n**Time & Date**\n\nIf your Service Provider configured this feature, you can check time and date, by pressing relevant one-touch button.\n\nCheck in the menu options whether the Service Provider has given you the capability of customising time and date settings.\n\n**Terminal Disable/Enable**\n\nYour MTM800 is provided with a feature that allows your Service Provider to disable it temporarily (in case it is stolen or lost) wireless.\n\nDuring the time your MTM800 is disabled, no calls can be initiated or received.\n\nWhile your MTM800 is disabled, it will display the following blank screen.\n\nYour MTM800 will act like it is turned off.\n\nIf you try to turn your MTM800 on when it is disabled it will operate as described above.\n\nIf your MTM800 is found, your Service Provider can re-enable it. After your MTM800 is re-enabled, you may resume normal operation.\n\nTerminal Permanent Disable\n\nYour MTM800 is provided with a feature that allows your Service Provider to disable it permanently in case it is stolen or lost. When your MTM800 is disabled permanently, it becomes inoperable.\n\nAfter a Permanent Disable the MTM800 can not be re-enabled by your Service Provider.\n\nYou are recommended to disable your MTM800 permanently only when you do not expect the terminal to be recoverable any more.\n\nMaking Calls\n\nYou are ready to place the call as required for the mode you are in:\n\n- press \\( \\text{📞} \\) to initiate the call and \\( \\text{📞} \\) to end the call.\n- press and hold the PTT while talking, and release the PTT while listening.\n\nTo dial a number for an outgoing call, enter the required mode (Group, Private, Phone, or PABX) and use one of the methods described on the following pages.\n\nFor more details on mode specific dialling methods, see the relevant mode section in this guide.\n\nSince the same numbers can be used in different modes for various subscribers (if configured), be sure to make the calls from the correct mode when entering a number through the keypad. Pressing \\( \\text{Mode} \\) while dialling a number will carry the number typed to the next mode.\n\nVOX Control\n\nVOX (Voice Operating Transmission) allows the user to transmit voice in a hands-free condition. It detects audio automatically when full duplex private call and telephone call use the fist microphone.\n\n**NOTE** This feature is only available if set up by your Service Provider. If it is disabled, transmission can start upon pressing PTT.\n\nReceiving Calls\n\nThe MTM800 will automatically switch to the mode of the incoming call. After the incoming call ends, the display returns automatically to the mode it was in before the incoming call arrived.\n\n**NOTE** In Private, Phone and PABX modes on receiving not Emergency TMO or DMO group call the MTM800 stays in the current mode. You can hear the call and the display remains unchanged.\n\nYour MTM800 will alert you of an incoming call depending on the setting you selected in Tones menu option (see page 88). During message editing, you will be alerted of an incoming Group/Emergency Group/Broadcast Group Call if configured by your Service Provider.\n\nBusy User Pre-emption (BUP)\n\n**NOTE** This feature is only available if set up by your Service Provider.\n\nA console operator, or dispatcher in the system might wish to call you while you are in an on-going call (Private, Phone, PABX). The console operator will activate the BUP feature to interrupt and pre-empt your call.\n\n**NOTE** BUP Invocation also pre-empts a call in process of being set up. The call in setup must be a private, phone or PABX call.\n\nThe console operator will then try to set up a private call with you, within a pre-determined period of time after successful call pre-emption.\n\n**NOTE** Only emergency calls are allowed within a pre-determined period of time after successful call pre-emption (during BUP wait state).\n\n### Pre-emptive Calling (PPC)\n\nPre-emptive calling is particularly useful when you need to speak urgently with a user whose terminal is busy in a non-emergency voice call.\n\nA Pre-emptive Priority call (PPC) is either an Emergency Group Call or a Private PPC (half-duplex or full-duplex call). The feature allows to disconnect the on-going lower priority call to connect to the incoming higher priority call.\n\nThe Service Provider configures the priority of the PPC. Its highest priority is emergency priority.\n\nTo place a PPC, see the Emergency mode and Private mode sections in the user guide.\n\nThe MTM800 will receive the call via loudspeaker or earpiece of the telephone style handset, according to the setting used when the PPC is received.\n\n**NOTE** For call alert, see settings in the Tones menu option (page 88).\n\nReceiving a PPC is explained in the following paragraphs. In the following screens <Any> in Use refers to any of the non-emergency voice calls: Group, Private, Phone, or PABX.\n\nReceiving an Emergency Group Call during a Call\n\nThe MTM800 receives the Emergency Group Call, drops the on-going non-emergency voice call, and connects to the Emergency Group Call.\n\nReceiving a Private PPC during a Call\n\nIf configured by your Service Provider, the MTM800 receives the PPC, drops the on-going, non-emergency, lower priority voice call, and connects to the higher priority private call.\n\nA PPC with lower or equal priority, will be dropped without any indication to the called user and will enter the missed call list.\n\nA PPC with emergency call priority will be displayed on the screen as “Emergency” (instead of “Priority”).\n\nHalf-duplex Private PPC Received\n\nFull-duplex Private PPC Received\n\nBroadcast Call\n\nThe Broadcast Group Call (also called Site Wide Call) is a high-priority group call from the console operator (or dispatcher) to all terminal users located at one or more\n\nsites. The terminals are configured to monitor a Broadcast Call, but the users cannot talk back.\n\nThe call can be received as normal broadcast call or emergency broadcast Call.\n\nThe Broadcast Call pre-empts an on-going Group Call that has the same (or lower) call priority.\n\nFor selecting a talkgroup during a broadcast call, see “Selecting a Talkgroup” on page 30. For changing range during a broadcast call see “Changing a Talkgroup during/on receiving a call” on page 34.\n\n**Ambience Listening (AL)**\n\nThis feature, if enabled by your Service Provider, allows a console operator or dispatcher to establish a special call with a specific MTM800 to monitor voice activity in the local vicinity. The call is setup without any indication to the affected MTM800, and any lower priority ongoing voice call or packet data transfer may be pre-empted.\n\nAfter accepting the call, the MTM800 transmits in a half-duplex Private call without any action from or indication to the user. The Ambience Listening call shall automatically end when the user initiates any voice call and uses the terminal normally.\n\n**Cancelling an Incoming Call**\n\nIn all modes (except Group), if you wish to cancel a call during an active call, press **Reject**. The call number will be forwarded to the Missed Call list.\n\nUsing In-call Features\n\n**NOTE** The in-call features are only available when using the Telephone Style Handset (see “Setting Accessory” on page 90).\n\n**Switching the Loudspeaker On/Off**\n\nPicking the Telephone Style Handset from the hang-up cup will disconnect the loudspeaker and the receive audio will only be heard in the earpiece of the handset.\n\n1. To activate the external loudspeaker, press **Spkr**. The **Spkr** soft key is blinking when active.\n\n2. To de-activate the external loudspeaker, press **Spkr**. The **Spkr** soft key is no longer blinking.\n\nWith the functional button (F1 or F2 on the handset) the external speaker may additionally be switched on/off (if programmed by your Service Provider)\n\n**Muting/Unmuting the Microphone**\n\nDuring a Phone, PABX, or private Full-Duplex Call, use the mute feature to:\n\n- hold conversation without being heard by the caller.\n- silence possible background noise in your area\n\n1. Press **Mute**. The ‘Mute’ soft key is blinking when active. The microphone is muted. You can hear the incoming audio, but the caller cannot hear any speech coming from your MTM800.\n\n2. To speak, press **Mute** again. The ‘Mute’ soft key is no longer blinking. The microphone is on.\n\n**Covert Mode**\n\nIf configured by your Service Provider the Covert Mode gives to you the ability to completely shut down all visible and audible MTM800 alerts and notifications. This feature makes\n\nthe MTM800 effectively unnoticeable even in a silent and dark environment.\n\nTo Enter the Covert Mode:\n\n- Press the Cover Mode one-touch button (if programmed by your Service Provider), or\n- Select Covert Mode in the Security menu (refer to page 83).\n\n**Local Area Service**\n\nThis mode, which is also called Fallback Mode, allows more than one user from the same site to communicate when the link between the site and network central controller fails. Entering and exiting Local Area Service (that is, returning to System Wide Services) is done automatically.\n\n**Entering Local Area Service**\n\nWhen the MTM800 receives a Local Area Service indication from the system, the following occurs:\n\n- the MTM800 sounds a tone\n- the display shows the “Local Area Service” message.\n- any call in progress is dropped upon entering Local Area Service mode.\n\nIf configured by your service provider, this message/alert will periodically repeat to remind you the terminal is still operating in Local Area Service mode.\n\nThe following features are available while the MTM800 is in Local Area Service:\n\n- Registration\n- Attachment\n- Group Call\n- Emergency Group Call\n- Emergency Alarm\n\nExiting Local Area Service\n\nWhen the link with the central network controller is re-established, the MTM800 exits Local Area Service and the following occurs:\n\n- the MTM800 sounds a tone.\n- any call in progress during Local Area Service is dropped.\n\nDimming the Display\n\nIf the backlight is set to Manual (see “Setting Backlight” on page 85), there are four levels of display backlight intensity. To change the backlight intensity, press \\( \\# \\).\n\n**NOTE** The intensity cannot be dimmed in Phone or PABX Mode and text editing, where the Backlight key \\( \\# \\) is used to enter a # sign and/or as a Shift key.\n\nAdjusting the Volume\n\nTo increase the volume, turn the On/Off-Volume knob clockwise.\n\nTo decrease the volume, turn the On/Off-Volume knob counter-clockwise.\n\nHorn & Lights Alarm On/Off\n\nUse the Horn & Lights Alarm when you leave your car and want to be alerted if an important message arrives (Private Call, for example).\n\n**NOTE** In order to operate the Horn & Lights Alarm, you must install the GKN6272 accessory in your vehicle.\n\nIf the External Alarm function is pre-programmed, the car lights turn on and an alarm sounds to inform you of the incoming call.\n\nTo turn the Horn & Lights Alarm on or off, press \\(\\text{(*)}\\).\n\n**NOTE** The ignition must be off for the Horn & Lights Alarm to work. The Horn & Lights Alarm cannot be operated in Phone or PABX Mode and text editing, where the \\(\\text{(*)}\\) key is used to enter an * sign.\n\n**Packet Data**\n\nThe Packet Data (PD) Service allows you to transfer data in a TETRA system using the Internet Protocol (IP). Check with your Service Provider for the availability of this feature.\n\n**NOTE** For transferring data from a standard computer over the air connect the computer via the Active Data Cable GMKN1022 with your MTM800. Your Service Provider has to setup additional applications on your computer.\n\nIf set up by your Service Provider it is possible to accelerate the transmission by using the Multi Slot Packet Data (MSPD) Service (refer to “Packet Data” on page 97).\n\n**Looking after your MTM800**\n\nTo clean your MTM800, use a moistened or antistatic cloth. Do NOT use a dry or electrostatically charged cloth.\n\nGeneral\n\nA Group Call is an instant communication between you and others in a talkgroup that you select. Participants may join (late entry) and leave an on-going Group Call. A **talkgroup** is a predefined set of subscribers enabled to participate in and/or invoke a Group Call and set up by your Service Provider.\n\nTalkgroups appear on your display as names or numbers (for example: Sales, Service, Electricians, Talkgrp10).\n\nThe Talkgroups are divided into **ranges**. Each range may contain up to 16 talkgroups.\n\nFor ease of use, your MTM800 also provides the ability to:\n\n- Perform an alphabetical search of the talkgroup aliases.\n- Scroll through the entire talkgroup list using the navigation key.\n- Dial a talkgroup (set up by your Service Provider).\n- Organise your favourite talkgroups into one range called My Groups (set up by your Service Provider).\n\nYour talkgroups may be organized into **scan lists** (set up by your Service Provider, or by yourself through the Menu). When you activate one of these scan lists, your MTM800 will continuously monitor the activities of the selected talkgroups.\n\nBy assigning priorities to the talkgroups defined in the scan list, you will be capable of accepting calls that have higher **priority** than the on-going call. For detailed information on scanning, see page 93.\n\nYou can start talkgroup, range, or scanning selection when the terminal is in idle mode or receiving a call.\n\nWhile being in a call and dialling another group simultaneously, do the following to talk in the current call:\n\n1. Exit selection screen.\n2. Press PTT and start talking.\n\nPressing PTT on selection screen switches to a new group and starts a call.\n\nEach talkgroup may have one associated Announcement Talkgroup (ATG) that it monitors (If set up by your Service Provider).\n\nAn ATG is a special group which is linked to a number of talkgroups and has the highest priority level, thus enabling broadcast of the call to all these talkgroups.\n\nWhen an ATG is selected, the scanning icon is not displayed. The MTM800 monitors the ATG scan list instead of the selected scan list. The ATG scan list contains all the talkgroups associated with a selected ATG. Your Service Provider should advise what talkgroups are associated with which Announcement Talkgroup.\n\nYour MTM800 will always monitor the group calls in the ATG scan list. To place an Announcement Call, you must first select the specified Announcement Talkgroup as advised by your Service Provider, otherwise you will only be able to participate when an Announcement Talkgroup is received.\n\nActivation and deactivation of talkgroup scanning has no effect on the ATG scan list.\n\n**Selecting a Talkgroup**\n\nYou can select a talkgroup in one of the following ways, by using the:\n\n- navigation keys\n- alphabetical search feature\n- numeric keypad entry (if configured)\n- favourite groups (if configured)\n\nFor talkgroup range scrolling configuration, see note in “Selecting a Range” on page 34.\n\nUsing the Navigation Key\n\nYour Service Provider configures the MTM800 to display only selectable talkgroups. Press the navigation key to scroll to the required talkgroup and press Ok. For talkgroup range scrolling configuration, see note in “Selecting a Range” below.\n\nUsing Alphabetical Search\n\n1. In Group Mode, press Optns.\n\n2. Select abc for talkgroup alpha search.\n\n3. You are now at the talkgroup alpha search screen. Enter an alphanumeric digit, and the MTM800 starts searching for the first Talkgroup alias, that starts with that character. Use the navigation key to scroll to adjacent aliases. In this example “a” is entered.\n\n4. Select the desired talkgroup by pressing Ok, or press PTT to select and start a call on the new group.\n\nUsing the Numeric Keypad\n\nWhen the terminal is in group mode and not transmitting (i.e., idle or receiving a call), you can dial a group by entering its speed number via the keypad. This feature is called Talkgroup Speed Dialling. The speed number is pre-configured in the terminal.\n\nYou can also view a speed number attributed to a group, if it exists.\n\nViewing the speed number of an attached group\n\n1. In Group Mode, press Optns.\n\n2. Select 5 View Speed# to view the talkgroup speed number.\n\n3. In this example “1” is the speed number. Press Back to return to the attached group screen.\n\nViewing the speed number while in scroll (idle mode only)\n\n1. In Group Mode, press the navigation key to scroll to the required talkgroup.\n\n2. Press Menu.\n\n3. Select 1 View Speed# to view the talkgroup speed number.\n\n4. In this example “2” is the speed number. Press Back to return to the attached group screen.\n\nDialling a speed number\n\n1. Enter a number (for example: “2”).\n\n2. Press Find or \\( \\text{PTT} \\).\n\n3. Press Select to attach the new group, or press PTT to attach and call.\n\nFavourite Groups\n\nThis feature allows you to store a favourite group in a special range called My Groups. A stored group may be TMO or DMO.\n\nYou can do the storing\n- from the group mode screen, or\n- from the My Groups menu option.\n\nAdding a Group from the Group Mode Screen\n\n1. In the group mode screen scroll to the required group and press Optns.\n\n2. Select 4 Add To MyGrp. The terminal displays the talkgroup alias added message and then returns to idle state.\n\nAdding a Group from the My Groups menu option\n\nSee “My Groups” on page 77.\n\nSelecting a Group from the My Groups Range\n\nSee “My Groups” on page 77.\n\nChanging a Talkgroup during/on receiving a call\n\nYou can select a group folder without an interruption on receiving and during a call.\n\nSelecting a group on receiving a call\n\nIf you select a group and a non-Emergency call is incoming, MTM800 display remains unchanged while you hear the call. During the selection you cannot see calling party information.\n\nNOTE When an Emergency Call is received, then selecting is aborted, the MTM800 switches to the group mode and Emgcy In Use display appears.\n\nSelecting a group during a call\n\nIf you start selecting a group during a call, Group In Use or Emgcy In Use display disappears.\n\nSelecting a Range\n\nTo select a range:\n\n1. In Group Mode, press Optns, followed by Range.\n2. Use the navigation key to scroll through the ranges.\n3. Press Ok to select the range (or press and hold PTT to start the call in the new range).\n\nNOTE The Service provider can configure range scrolling to:\n- Stay in range — when the range end is reached during talkgroup scrolling, further scrolling restarts the range talkgroup list.\n- Scroll to next range — when the range end is reached during talkgroup scrolling, further scrolling switches to the talkgroup list in the next range.\n\nActivating/Deactivating Scanning\n\nSee “Setting Talkgroup Scanning” on page 93.\n\nMaking a Group Call\n\n1. Press Mode until Group Mode appears on your display. In this example, “Range 10” is the last selected range and “Talkgroup 1” is the last selected talkgroup.\n\n If you press Optns, you have the option to select 1 abc, 2 Range, or 3 Scanning (see “Receiving a Group Call with Scan On” on page 37).\n\n2. If this is the talkgroup you wish to call, press and hold the PTT. Wait for the “Talk permit” tone (if configured) and then speak into the microphone. Release the PTT button to listen.\n\n3. To call a talkgroup other than the one shown, press a navigation key to scroll through the talkgroups. Press Ok to select the talkgroup. Press PTT to start the call in the new talkgroup.\n\n4. To select a range other than the one shown, press Optns and then Range. Use the arrow keys to scroll through the ranges. To cancel range scrolling, press Back.\n\n Press Ok to select the range (or PTT to start the call in the new range). The call is set up in the new range and last selected talkgroup in this range.\n\nWhen you start a call, the members of the selected talkgroup who have their terminals turned on, will receive the transmission.\n\n**NOTE**\n\nThe ‘No Group’ message is displayed when you are out of the normal coverage area of your selected talkgroup. If so, select a new talkgroup that is valid for your working location.\n\nReceiving a Group Call\n\nUnless it is engaged in an active call, your MTM800 will automatically switch to Group Mode and receive the transmission. To answer the call, press and hold PTT.\n\nYour MTM800 shows the Group Name, and the caller’s private number or name (alias) if previously stored in your address book. In case a favourite talkgroup is received, the terminal will display the “My Groups” range and group alias.\n\nThe following screens show examples of how the caller’s private number (ID 7712) is displayed.\n\nWithout alias and Private number\n\nID: 7712 Talkgroup 1 Status\n\nPrivate number without alias\n\nID: David Talkgroup 1 Status\n\nPrivate number with alias\n\n**NOTE** For incoming call alert, see settings in the Tones menu option (page 88).\n\n**NOTE** When receiving a Group Call, your MTM800 will sound a “New Group Call” tone (if configured by your Service Provider).\n\nReceiving a Group Call with Scan Off\n\nYou can receive a group call from the selected talkgroup or from the associated ATG only.\n\n**Receiving a Group Call in Idle Mode**\n\nIn Automatic Mode Switch you can receive a Group Call in any mode. Your MTM800 will automatically switch into Group mode and receive the transmission.\n\n**Receiving a Group Call during an On-going Group Call**\n\nDepending on how the Service Provider has configured incoming calls, the incoming call will either be:\n\n- Forced upon you and will interrupt the on-going call (if the incoming call has higher priority than the on-going call).\n\nor\n\n- Presented to you (if it has higher priority than the on-going call).\n > To accept the call, press **Join**.\n > To cancel the call, press **End**.\n\n**Receiving a Group Call with Scan On**\n\nWith Scan On, you can receive a group call from the scan list you set up, in addition to receiving a group call from the selected talkgroup or from the associated ATG.\n\nReceiving the scan call functions as receiving an associated ATG or selected call in scan off (see previous page), except for the following:\n\n- The display is different when receiving the call in idle mode, as shown here.\n- The MTM800 sounds a tone as explained in the note below.\n\n**NOTE**\n\n*When receiving a High Priority Group Call, your MTM800 will sound a “High Priority Group Call” tone (if configured by your Service Provider).* \n\n*When receiving a Group Call from your scan list, which is not from a high priority group, your MTM800 will sound “New Group Call” tone (if configured by your Service Provider).* \n\n**Receiving an Emergency Group Call**\n\nFor detailed information, see page 23.\n\n**Receiving a Broadcast Call**\n\nFor detailed information, see page 23.\n\nTransmit Inhibit\n\nThe Transmit Inhibit (TXI) Mode can be activated by the user before he enters RF sensitive areas, e.g. in hospitals or in potentially explosive areas, where safety can be jeopardized due to terminal transmission radiation.\n\n**NOTE** Radiation of the MTM800 is only suppressed if the TXI Mode is activated or the terminal is separated from its power supply.\n\nTransmit Inhibit can only be activated in Group Mode. In Transmit Inhibit Mode the terminal will not transmit under any circumstances, except for the Emergency Group Call, which can be initiated even if the MTM800 is in TXI Mode.\n\nAll terminal functions and keys which cause transmission, e.g. registration to the network, change of talkgroup or range, sending messages, pressing PTT, etc. are disabled. In this case the display shows “Not Allowed In TXI Mode” and the terminal sounds the “Transmit Inhibit” tone.\n\nWhen no danger to safety exists anymore (for instance if the user leaves the RF sensitive area) the Transmit Inhibit mode can be deactivated and the terminal returns to normal operation.\n\nSetting the TXI Mode is described in “Setting Transmit Inhibit (TXI) Mode” on page 92.\n\n**NOTE** To activate or deactivate the TXI Mode you can use one of the programmable keys (if set up by your Service Provider). You must press and hold the key for a pre-set time as configured by your Service Provider.\n\nActivated Transmit Inhibit is indicated by the solid orange LED and changing between the two displays:\n\nDynamic Group Number Assignment (DGNA)\n\nDGNA provides the ability for a network operator or authorised user to dynamically allocate new, or update existing talkgroups to selected terminals over the air interface. Using supplementary services messages (SS-DGNA), the network operator can command the terminal to add talkgroups to the existing talkgroups list, or to delete talkgroups from the list. This operation is performed by transmitting the data into your MTM800.\n\n**NOTE** Your Service Provider can gather some Talkgroups under one Super-group and transmit it to your MTM800 as a DGNA. In such a case, you will be able to participate in calls to/from all the groups in the Super-group.\n\n**DGNA Reception with Notification Message**\n\nWhen a DGNA is received and DGNA notification was configured by your Service Provider, you will get a tone indication and notification message (“Programming Entries...”), and then a display of the new assignments.\n\nIf DGNA notification was not configured by your Service Provider, you will only get a tone indication and only if a selected group was changed by the DGNA.\n\n1. To view the added/deleted talkgroups details press **View**. You may scroll through the list using the keys.\n\n2. To return to the initial Mode display press **Back**.\n\n3. To select the DGNA group, press **Select**. Or scroll to another group using the navigation key, and press **Select**.\n\n**NOTE** Once you exit the DGNA notification screen, the Select key disappears. To select one of the newly added groups, see page 30.\n\nIf configured, a newly added group will also become the newly selected talkgroup.\n\nIf this group is de-assigned, and no group changes or power cycling have occurred, the terminal will revert to its previous talkgroup.\n\nIf a new DGNA is received during scrolling, you will receive a message, indicating that the list of talkgroups was updated.\n\nAfter a few seconds the display returns to the initial DGNA display detailing the update.\n\nIf the DGNA received is an all “Talkgroups delete” assignment, your MTM800 will display the following:\n\n**DGNA Reception without Notification Message**\n\nIf DGNA notification was not configured by your Service Provider, you will get a tone indication and notification message only and only if a selected group was changed by the DGNA.\n\n**DGNA Auto Select Group**\n\nIf DGNA Auto Select was configured by your Service Provider, whenever a DGNA message is received by your terminal, the talkgroup will automatically be made the selected group by your terminal.\n\n**Button/Footswitch**\n\nThis feature allows the user to send a predefined status message by pressing the Emergency button/footswitch. TMO Emergency mode, Emergency Alarm and initiating a TMO Emergency Group/Private Call is unavailable.\n\nMessage addressing and sending:\n\n- address can be predefined by Service Provider if not it will be send to currently selected group\n- if no group selected, the message is sent to the reserved address\n- the message is sent even if the user is involved in an active service\n\nIndication depend on Service Provider. Visible/audible can be disabled for the status message.\n\nWhen the radio is PIN locked the user can still press the Emergency button/footswitch to send the message. If the radio is out of service the user will only see indication that operation failed.\n\nDMO Group Call\n\nGeneral\n\nIn DMO (Direct Mode Operation) the MTM800 can be used without your Service Provider’s infrastructure.\n\nDirect Mode allows communication among terminals in which the same talkgroup is selected.\n\n**NOTE** In DMO it is only possible to place Group Calls, Emergency Group Calls and Private Half-duplex Calls.\n\nYou can receive a call:\n\n- From the selected talkgroup\n- From other users within talkback range (if configured by your Service Provider). This is called an InterMNI (Mobile Network identity) call.\n- From an open group. (An open group is a super-group to which all DMO groups belong.)\n\nWhen you start a call, the members of the selected talkgroup who have their units turned on, and are within the group subscriber identity (as configured by the Service Provider), will receive the transmission.\n\nIn DMO the MTM800 can communicate with the trunking system (and vice-versa) if the **Gateway** option is enabled in the terminal.\n\nTo enhance the terminal’s DMO coverage area the DMO group can link to a repeater if the **Repeater** option is enabled in the terminal. Additionally the **GW + Rep** (gateway and repeater) communication mode can be used.\n\nIf Transmit Inhibit is activated while the terminal is set to DMO, the PTT is disabled. You can only listen. For detailed information on Transmit Inhibit, see page 38. DMO Talkgroup selection is allowed when Transmit Inhibit is activated.\n\nSelecting a Talkgroup\n\nSee “Selecting a Talkgroup” on page 30.\n\nChanging a Talkgroup during/on Receiving a Call\n\nSee “Changing a Talkgroup during/on receiving a call” on page 34.\n\nSwitching from TMO to DMO or from DMO to TMO\n\nEnter TMO or DMO in one of the following ways:\n\n- To switch from TMO to DMO press Menu 6 2 2.\n- To switch from DMO to TMO press Menu 6 2 1.\n- Press the dedicated TMO/DMO one-touch button (configured by your Service Provider).\n\nGateway/Repeater Selection\n\nUse the DMO Config sub-menu for setting the Gateway and Repeater options.\n\n1. Press Optns to enter the options menu in DMO:\n\n **DMO Options Sub-menu**\n\n - 1 abc\n - 2 Range\n - 3 Config\n - 4 Add to MyGrp\n - 5 View Speed#\n\n - 1 MS – MS\n - 2 Gateway\n - 3 Repeater\n - 4 GW + Rep\n\n - 1 Automatic\n - 2 Specific\n\n2. Scroll to 3 Config, and press Ok.\n\nSelecting DMO Group Call MS to MS\n\nTo change from gateway or repeater mode to MS – MS mode (DMO terminal to terminal call):\n\n1. Press Optns, scroll to 3 Config, and press Ok.\n\n2. Scroll to 1 MS – MS and press Ok. The following message will be displayed for a few seconds: **MS – MS Will Be Used**.\n\nSelecting DMO Group Call via Gateway\n\nWhile in DMO, proceed as follows to choose a gateway to set up a call via Gateway for the selected talkgroup:\n\n1. Press Optns, scroll to 3 Config, and press Ok.\n\n2. Scroll to 2 Gateway and press Ok.\n\n3. The display shows the last gateway selection method. Use the navigation key to scroll to your selection and press Ok:\n\n - **Automatic** — the MTM800 will use the first available gateway for that talkgroup. The Gateway icon will blink upon selecting that option.\n\n - **Specific** — the MTM800 will use only the gateway with the specified Gateway address for that talkgroup.\n\nUpon selecting “Specific”, you will see one of the following displays:\n\n- The selected gateway address (e.g.: 1022), pre-programmed by your Service Provider or previously entered by yourself via the keypad. Press Ok to use the current address, or enter a new address via the keypad, and press Ok. The Gateway icon will blink upon selecting the gateway.\n\n• “None”, indicating that no gateway was selected for that talkgroup. Enter an address via the keypad, and press **Ok**. The Gateway icon will blink upon selecting the gateway.\n\nWhen the MTM800 detects the suitable gateway, the Gateway icon will turn solid.\n\n**Selecting DMO Group Call via Repeater**\n\nWhile in DMO, proceed as follows to choose the Repeater option to set up a call via Repeater for the selected talkgroup:\n\n1. Press **Optns**, use the navigation keys to scroll to 3 Config. and press **Ok**.\n\n2. Scroll to 3 Repeater and press **Ok**.\n\n3. The MTM800 will use the first available repeater for that talkgroup. The repeater icon will blink upon selecting that option.\n\nWhen the MTM800 detects the proper repeater presence signal, the Repeater icon will turn solid.\n\n**Selecting DMO Group Call via Gateway and Repeater**\n\nWhile in DMO, proceed as follows to choose the Gateway and Repeater option to set up a call via Gateway or Repeater (Gateway preferred) for the selected talkgroup.\n\n1. Press **Optns**, scroll to 3 Config. and press **Ok**.\n\n2. Scroll to 4 GW + Rep and press **Ok**.\n\n3. The display shows the last “GW + Rep.” type selection. Use the navigation key to scroll to your selection and press **Ok**:\n\n - **Automatic** — the MTM800 will use the first available gateway for that talkgroup. The Gateway icon and the repeater icon will blink upon selecting that option.\n\nSpecific — the MTM800 will use only the gateway with the specified Gateway address for that talkgroup.\n\nUpon selecting “Specific”, you will see one of the following displays:\n\n- The selected gateway address (e.g.: 1022), pre-programmed by your Service Provider or previously entered by yourself via the keypad. Press Ok to use the current address, or enter a new address via the keypad, and press Ok. The gateway and repeater icons will blink upon selecting the gateway.\n\n- “None”, indicating that no gateway was selected for that talkgroup. Enter an address via the keypad, and press Ok. The Gateway and Repeater icons will blink upon selecting the gateway.\n\nWhen the MTM800 detects the appropriate gateway and/or the Repeater, the Gateway and/or Repeater icons will turn solid, respectively.\n\n**Making a DMO Group Call (MS to MS)**\n\n1. Press Mode until the Group Mode appears on your display.\n\n2. Press Menu 6 2 2 (see also page 92). To change range and talkgroup, see steps 3 and 4 of “Making a Group Call” on page 35.\n\n3. If this is the desired talkgroup and range, press the PTT button. Wait for the “Talk permit” tone (if configured) and then speak into the microphone. Release the PTT button to listen.\n\nTo change talkgroup and range, see the Group Mode section, page 30.\n\n**NOTE** To change the Operating Mode quickly you can use one of the programmable keys (if set up by your Service Provider).\n\n### Making a DMO Group Call via Gateway\n\n1. While in DMO, choose a gateway as described in “Selecting DMO Group Call via Gateway” on page 44.\n2. Place the call for the selected talkgroup:\n - If you press PTT while the gateway is not available, you will start a DMO call without gateway. The Gateway icon will disappear.\n - If you press PTT while the selected gateway is available, but the call is rejected by the gateway, your MTM800 will sound a tone and display the following screen, informing you that the call via Gateway was aborted and that the terminal will automatically proceed to initiate a DMO call without gateway. The Gateway icon will disappear.\n - If you press PTT while the gateway is available, you will start a DMO call with gateway. The Gateway icon will turn solid.\n\n### Making a DMO Group Call via Repeater\n\n1. While in DMO, choose the Repeater option as described in “Selecting DMO Group Call via Repeater” on page 45.\n2. Place the call for the selected talkgroup:\n - If you press PTT while the repeater is not available, you will start a DMO call without repeater. The Repeater icon will disappear.\n - If you press PTT while the selected repeater is available, but the call is rejected by the repeater your MTM800 will sound a tone and display the following screen, informing you that the call will be setup without repeater. The Repeater icon will disappear.\n\n- If you press PTT while the repeater is available, you will start a DMO call with repeater. The Repeater icon will be solid.\n\n**Making a DMO Group Call via Gateway and Repeater**\n\n1. While in DMO, choose the Gateway and Repeater option as described in “Selecting DMO Group Call via Gateway and Repeater” on page 45.\n\n2. Place the call for the selected talkgroup:\n - If you press PTT while both gateway and repeater are *not available*, you will start a DMO call without gateway and repeater. The Gateway and Repeater icons will disappear.\n - If you press PTT while both gateway and repeater are *available*, but the call is rejected by the gateway, a repeater call will be attempted.\n > If it is *successful* your MTM800 will display the message **Repeater Call** and a call via repeater will proceed. The Gateway icon will disappear.\n > If it is *not successful* your MTM800 will display the message **MS – MS Call** and a terminal to terminal call will proceed. The Gateway and Repeater icons will disappear.\n - If you press PTT while both gateway and repeater are *available*, a gateway call will be attempted.\n > If it is *successful* your MTM800 will start a DMO call with gateway. The Gateway icon will be solid. The Repeater icon will disappear.\n > If synchronising with a gateway is *not successful* a repeater call will be attempted.\n > If it is *successful* your MTM800 will display the message **Repeater Call** and a repeater call will proceed.\n\nThe Gateway icon will disappear and the Repeater icons will be solid.\n\n> If it is not successful your MTM800 will display the message MS – MS Call and a terminal to terminal call will proceed. The Gateway and Repeater icons will disappear.\n\n**NOTE**\n\nIf Gateway and Repeater mode is selected, and if one of the devices is not available, the call setup is proceeding as if this device was not selected.\n\n*Example:* In case of the Gateway is available and the Repeater is not available, after an unsuccessful Gateway call attempt the call falls back to MS – MS mode immediately with the MS – MS call message.\n\n**Receiving a DMO Group Call**\n\nYou can receive a DMO Group Call only when your MTM800 is in DMO.\n\nYour MTM800 will display the caller’s private number or alias and the talkgroup name.\n\nThe following screens show examples of how the caller’s identity can be displayed.\n\n**NOTE**\n\nFor call alert, see settings in the Tones menu option (page 88).\n\n**Receiving a DMO Group Call (MS – MS)**\n\n- **DMO Range1**\n - **DMO TG1**\n - **Optns**\n- **ID:124**\n - **DMO TG1**\n - **Optns**\n- **ID:David**\n - **DMO TG1**\n - **Optns**\n\nWithout alias and private ID\n\nPrivate ID without alias\n\nPrivate ID with alias\n\nReceiving a DMO Group Call (via Gateway / Repeater)\n\nThe Gateway or the Repeater icons are displayed accordingly to the ongoing call type (Gateway or Repeater).\n\n**NOTE**\n- If MS to MS mode is selected, and the terminal receives a call via repeater, the Repeater icon will be shown (if the repeater mode is enabled by the Service Provider, otherwise the call will not be accepted).\n- If Gateway mode is selected but a gateway is not available, The Gateway icon will be solid in case of an incoming gateway call.\n\n**DMO Private Call**\n\nIf configured by your Service Provider it is possible to make and receive a Private Call in DMO.\n\nHowever the Gateway and/or Repeater options are activated they are not used for a DMO Private Call. The DMO Private Call will be a direct communication between two TETRA terminals (MS – MS).\n\nFor detailed information, see “Private Call in DMO” on page 55.\n\n**Receiving an Emergency Group Call**\n\nFor detailed information, see “Emergency in DMO” on page 66.\n\nPrivate Call\n\nGeneral\n\nA Private Call, also called Point to Point or individual call, is a call between two individuals. No other terminal can hear the conversation.\n\nThis call can be a\n\n- full-duplex call (if the system allows) in TMO, or\n- a half-duplex call in TMO or DMO.\n\nIn a full-duplex call, both participants can speak at the same time, while only one person can speak at a time during a half-duplex call.\n\n**NOTE** If your Service Provider has restricted access to the Address Book, it might not be possible to create a new contact, edit existing contacts or dial up a number which is not in the Address Book.\n\nEntering Private Mode\n\nTo enter the Private Mode press until Private Mode appears on the display.\n\nIn this example, 8008801 is the private number of the last calling or called terminal. No alias is displayed since it is not pre-programmed in the private number list. If this is the person you wish to call, press the PTT.\n\nIf you wish to talk to a person other than the one shown, you can enter another private number in one of the following ways:\n\n- last number called,\n- direct entry,\n- short number dial,\n- list scroll, or\n- alphabetic search.\n\nPress Back to return to the Private Mode display.\n\nOperating with MTM800 in RF sensitive areas, see “Transmit Inhibit” on page 38.\n\n**NOTE** While Transmit Inhibit is activated, an incoming Private Call is indicated, but it is not possible to answer the call.\n\n### Entering the Private Number\n\n#### Last Number Called\n\nThe last number called appears the moment the terminal enters private idle mode. Press **PTT** to call this number.\n\n#### Direct Entry\n\n1. Enter the private number. If the number entered is in the pre-stored private address book, the MTM800 will find it for you.\n\n2. To save the number in the address book, press **Save** and follow the prompts (see “Updating the Private Address Book” on page 75).\n\n#### Short Number Dial\n\nIf set up by your Service Provider, Short Dial allows you to dial part of the full number of the person you wish to call. Your MTM800 will automatically complete the number and send it over the air based on your own terminal’s identity.\n\nFor example:\n\n1. Dial 456 (instead of 4282456, the full number).\n2. To place the call, press the **PTT**.\n3. To hang up, press \\( \\text{📞} \\).\n\n#### List Scroll\n\nTo scroll back or forward through the stored list of numbers and names, press \\( \\text{⬅️} \\) or \\( \\text{➡️} \\).\n\nAlphabetic Search\n\nAlphabetic search allows you to locate a stored private number quickly by entering the first letter of the name (or alias) associated with it.\n\n1. Press abc.\n2. Press the numeric key with the first letter of the name you are searching in the pre-stored list (key 3 def in this example).\n\n**NOTE** If no name is stored under a letter, the MTM800 automatically searches forward, alphabetically, until the next name is found. If more than one name in the list begins with the same letter, use the scroll keys to view other names.\n\nMaking a Private Call in TMO\n\n1. Enter the number of the person you wish to call.\n2. Press and release the PTT button. You will hear a ringing tone. Wait for the called person to answer your call.\n3. Press and hold PTT when talking, and release the PTT when listening.\n4. To end the call, press . If the called person ends the call, the Call Ended message is displayed.\n\nMaking a Private Full-Duplex Call in TMO\n\n1. Enter the number of the person you wish to call.\n2. Press and release . Once the call is successfully initiated, you will hear a ringing tone. Wait for the called person to answer your call.\n3. To end the call, press again. If the called person ends the call, the Call Ended message is displayed.\n\nReceiving a Private Call in TMO\n\n1. The MTM800 automatically switches to Private mode and starts ringing. The display shows the caller’s identity.\n\n2. To answer the incoming call, press PTT.\n\n3. To end or cancel the call, press . The display returns automatically to the mode it was before the incoming call arrived.\n\nIf the called person ends the call, the Call Ended message is displayed.\n\nNOTE For call alert, see settings in the Tones menu option (page 88).\n\nReceiving a Private Full-Duplex Call in TMO\n\n1. The MTM800 automatically switches to Private Mode and starts ringing. The display shows the caller’s identity.\n\n2. To answer the incoming call, press or any key on the keypad (if configured by your dealer).\n\n3. To end or cancel the call, press . The display returns automatically to the mode it was in before the incoming call arrived.\n\nIf the called person ends the call, the Call Ended message is displayed.\n\nNOTE For call alert, see settings in the Tones menu option (page 88).\n\nPrivate Call in DMO\n\nIf configured by your Service Provider it is possible to make and receive a Private Call in DMO. You can make or receive a DMO Private Call only when your MTM800 is in DMO.\n\n**NOTE** *Private Calls via DMO Repeater and/or DMO Gateway are not supported.*\n\nThe calling and called party shall be on the same talkgroup.\n\n**Making a DMO Private Call**\n\n1. To enter the Private Mode press until **Private Mode** appears on the display.\n\n2. Enter a number like described in “Entering the Private Number” on page 52.\n\n3. Press and hold **PTT**. Wait for the talk permit tone (if configured) before talking, and release the **PTT** when listening.\n\n4. The call ends after a pre-programmed time, or if you press .\n\n**NOTE** *There is no presence check for Private Calls in DMO. This means you don’t know whether the called party is available when you starts the call.*\n\n**Receiving a DMO Private Call**\n\nWhen a DMO Private Call is received, the call is started immediately without need to accept it by the called party.\n\n1. Press **PTT** to talk back and start talking.\n\n2. The call ends after a pre-programmed time, or if you press .\n\n**NOTE** *If the called party presses the DMO private call is suspended for a specified time and in case the calling party is still transmitting the call is joined again.*\n\nDialling on Receiving a Call\n\nIf you dial and a call is incoming, the MTM800 stays in current mode and the display remains unchanged while you hear the call. Dialling continues on current display.\n\n**NOTE** When an Emergency Call is received, then dialling is aborted, the MTM800 switches to the group mode and Emgcy In Use display appears.\n\nMaking a Private PPC (Pre-emptive Priority Call)\n\n**NOTE** This feature is only available if set up by your Service Provider.\n\n1. Enter the private number and press PTT or .\n2. If the display shows the called user is busy, press Yes to interrupt the on-going call.\n3. You will hear a ringing tone. Wait for the called person to answer your call.\n4. Continue the call as in a regular half-duplex or full-duplex Private Call.\n\nCall Queuing\n\nWhen there are no available infrastructure resources for a call while in a setup phase, or while in an active call during cell re-selection, the call will be queued. The MTM800 will remain in queue for a pre-programmed period of time. If the resources become available, the call will proceed. If there are no resources after a certain period of time, the MTM800 will end the call.\n\nGeneral\n\nThe Phone Mode allows you to call a landline telephone number or a cellular mobile phone number. In this publication we use “phone number” when referring to these numbers.\n\nThe Private Automatic Branch Exchange (PABX) Mode allows you to call local (office) extension numbers, if this mode has been activated by your Service Provider.\n\nBoth modes have the same dialling features.\n\nFor operating with MTM800 in RF sensitive areas, see “Transmit Inhibit” on page 38.\n\n**NOTE** While Transmit Inhibit is activated, an incoming Phone or PABX Call is indicated, but it is not possible to answer the call.\n\n**NOTE** If your Service Provider has restricted access to the Address Book, it might not be possible to create a new contact, edit existing contacts or dial up a number which is not in the Address Book.\n\nMaking a Phone or PABX Call\n\n1. Press **Mode** until Phone Mode appears on your display.\n If a PABX call is required, press **Mode** key again. PABX Mode appears on your display.\n\n2. Last dialled number is presented on your display just after changing to Phone/PABX Mode.\n In this example, 039694040 is the last dialled phone number.\n\n3. If this is the person you wish to call, press **Call**.\n\n4. To hang up, press **Call** again.\n\nIf you wish to talk to a person other than the one shown, you can enter another number in one of the following ways:\n\n- last number redial,\n- direct dial,\n- speed dial,\n- one-touch dial,\n- list scroll, or\n- alphabetic search.\n\nPress Back to return to the mode display.\n\n**Last Number Redial**\n\nWhen no number is displayed, pressing will enter the list of last dialled Phone and Private numbers.\n\n1. To scroll backwards or forwards through the list, press or .\n2. To place the Phone call, press .\n3. To hang up, press again.\n\n**Direct Dial**\n\n1. Dial the full phone number using the keypad.\n2. To save the number in the address book, press Save and follow the prompts.\n3. To place the call, press .\n4. To hang up, press again.\n\n**Speed Dial**\n\nSpeed dial allows you to dial a shortened number of up to two digits instead of the full number. The speed dial number is the location of an entry in the address book.\n\n1. Enter the pre-programmed speed dial number (for example: 5) and press .\n2. To place the call, press .\n3. To hang up, press again.\n\nOne-touch Dial\n\nOne-touch dialling allows you to place a call by pressing and holding one of the numeric keys (2 to 9). The number is the location of an entry (2 to 9) in the address book.\n\n1. Press and hold the required numeric key for a few seconds. Your MTM800 will display the number and dial it.\n\n2. To hang up, press \\( \\text{📞} \\).\n\n**NOTE**\n\n*If the one-touch feature is enabled, one-touch dial is disabled (see page 17).* \n\nList Scroll\n\n1. To scroll backwards or forwards through the stored list of numbers and names, press \\( \\text{▶} \\) or \\( \\text{◀} \\).\n\n2. To place the call, press \\( \\text{📞} \\).\n\n3. To hang up, press \\( \\text{📞} \\) again.\n\nAlphabetic Search\n\nAlphabetic search allows you to locate a stored number quickly by entering the first letter of the name (or alias) associated with it.\n\n1. Press \\( \\text{abc} \\).\n\n2. Press the numeric key with the first letter of the name you are searching in the pre-stored list (\\( \\text{3 def} \\) in this example).\n\n**NOTE**\n\n*If no name is stored under a letter, the MTM800 searches forward, alphabetically, until the next name is found. If more than one name in the list begins with the same letter, use the scroll keys to view other names.*\n\n3. To place the call, press \\( \\text{📞} \\).\n\n4. To hang up, press \\( \\text{📞} \\) again.\n\nDTMF Overdial\n\nIf set up by your Service Provider, DTMF allows you to communicate with an automated answering device (for example, the voice mail or answering machine) during an ongoing call.\n\nWhile in an ongoing call, press the keys 0 to 9, *, #. When pressed, the key will sound a tone and the entered digit will be displayed on the screen.\n\nPhone In Use\n12345*#67890\n\nDialling on receiving a call\n\nSee “Dialling on Receiving a Call” on page 56.\n\nAnswering a Phone or PABX Call\n\n1. The MTM800 automatically switches to Phone Mode and starts ringing.\n\n2. To answer the incoming call, press or any key (except Power On/Off).\n\n3. To end or cancel the call, press End. The display returns automatically to the mode it was before the incoming call arrived.\n\nIf the called person ends the call, the Call Ended message is displayed.\n\nNOTE For call alert, see settings in the Tones menu option (page 88).\n\nEmergency Mode\n\nGeneral\n\nIn Trunked Mode (TMO) you can send an Emergency Alarm to the dispatcher and you can initiate and receive an Emergency Group or Private Call. A terminal in TMO receives an Emergency Group Call to the selected group associated ATG (Announcement Talkgroup), or scanned group. If the ATG is the currently selected group, the terminal will receive the Emergency Group Call to the group associated with this ATG. (For information on the ATG, see page 29.) Your MTM800 may also enable you to make an Emergency Group Call without the need to press and hold the PTT (Hot Microphone feature).\n\nIn Direct Mode (DMO) you can initiate and receive an Emergency Group Call.\n\nYour Service Provider may configure\n\n- the Emergency Group Call,\n- the Emergency Private Call (if supported by the infrastructure),\n- the Emergency Alarm,\n- the Hot Microphone feature, and\n- the Emergency Mode indication.\n\nThe terminal stays in Emergency mode when switching from TMO to DMO. The Emergency mode is also kept while switching from DMO to TMO if Emergency mode is available in TMO.\n\nThe calls will get emergency priority in the system.\n\nThese features are active if the MTM800 is in service and attached to any talkgroup.\n\nAn Emergency Group Call is configured as non-tactical or tactical:\n\n- A non-tactical call initiates on a talkgroup designated by your Service Provider. The group might be different than\n\nthe one displayed on the terminal screen when starting the call. After exiting from non-tactical emergency mode the terminal will be attached to the group that was selected before initiating the non-tactical call. When in non-tactical emergency mode, you will not be able to switch talkgroups. DGNA messages have no impact during non-tactical emergency mode but only after exiting the non-tactical emergency mode.\n\n- A **tactical** call initiates on the currently selected talkgroup.\n\n**NOTE**\n\n*For call alert, see settings in the Tones menu option (page 88).* \n\n**Entering TMO or DMO**\n\nEnter TMO or DMO in one of the following ways:\n\n- Press **Menu** 621 (TMO)\n- Press **Menu** 622 (DMO)\n- Press the dedicated TMO/DMO one-touch button (configured by your Service Provider).\n\n**Entering or Exiting Emergency Mode**\n\nTo enter Emergency Mode from any mode, press **△**.\n\n**NOTE**\n\n*Upon entering Emergency Mode in TMO, the MTM800 will automatically send an Emergency Alarm to the dispatcher (if configured by your Service Provider).* \n\nThe terminal exits Emergency mode and switches to Group mode in one of the following cases:\n\n- You press and hold **Back**.\n- The terminal fails to attach to a non-tactical group.\n- The system infrastructure detaches the selected non-tactical group.\n\n**NOTE**\n\n*The required time you need to press the Emergency key is by default set to 0.5 seconds. The time can be configured by your Service Provider.*\n\nPressing the Emergency Key even if Transmit Inhibit is activated causes immediately the terminal to radiate. When entering the Emergency Mode the terminal should not be within the RF sensitive area any longer!\n\nThe MTM800 interrupts the Ambience Listening call when you press the Emergency key.\n\n**Invisible Emergency**\n\nThis feature can be enabled/disabled by your Service Provider.\n\nInvisible Emergency mode is a type of emergency services that provides no audible indications and the display corresponds to the idle state for any Emergency operations. In this mode, only the user knows that the radio is in the Emergency mode and sends out Emergency alarm. All the settings are restored when the user exits the Emergency mode. To exit Invisible Emergency mode, the user needs to press the softkey labelled Exit.\n\n**Changing Range or Talkgroup**\n\nIf the Emergency Group Call is configured to “tactical”, you can select a talkgroup other than the one displayed, press a navigation key and then Ok. To change the range press Optns, and proceed as explained in “Making a Group Call” on page 35.\n\n**Emergency in TMO**\n\n**Sending an Emergency Alarm**\n\nYour MTM800 will send an Emergency Alarm (if configured by your Service Provider):\n\n- Automatically, upon entering Emergency Mode\n- If you press while the MTM800 is in Emergency Mode.\n- If you change group while in Emergency Mode.\n\nThe screen will show one of the following delivery reports:\n\n- **Alarm Sent**\n- **Alarm Failed**\n\nIn both cases, the screen returns within a few seconds to the main screen of the Emergency mode.\n\nDue to there being no delivery confirmation while in DMO, the **Alarm Sent** information confirms only the sending of the alarm.\n\n*Or* – if configured by your Service Provider – your MTM800 will send an Emergency Alarm:\n\n- If you press the Emergency button/footswitch without entering Emergency Mode before.\n - Other Emergency services such as starting TMO Emergency Mode or initiating Emergency Private Call (if supported by the infrastructure) will be unavailable.\n - No visible and audio indication on sending Emergency Alarm will be done.\n\n**NOTE** *Some systems do not support the Emergency Alarm feature when the user is in a “Local Area Service” area.* (See page 26.)\n\n**Making an Emergency Group Call**\n\nTo initiate or answer a call while in Emergency mode:\n\n1. Press and hold **PTT**\n2. Wait for the talk permit tone (if configured) and talk.\n3. Release **PTT** to listen.\n\n**NOTE** *Your MTM800 enters TMO by pressing the **Emergency** button (if configured by your Service Provider). The terminal attaches to the predefined talkgroup and starts the Emergency Group Call. If the predefined talkgroup is invalid the terminal attaches to the last selected talkgroup.*\n\nHot Microphone Feature\n\nIf the Hot Microphone feature was programmed into your MTM800 by your Service Provider, you can make an Emergency Group Call without the need to press and hold the PTT.\n\nThe following will happen upon entering Emergency mode:\n\n1. The MTM800 will automatically send an Emergency Alarm to the dispatcher (if configured by your Service Provider).\n2. A talk permit tone will be heard.\n3. The following typical display will appear:\n The microphone will stay open for a time period determined and programmed by your Service Provider.\n\nAfter the Hot Microphone time period expires, or if you press PTT during the Hot Microphone period, or if you press End: the Emgcy Mic Ended message will be displayed, and the terminal reverts back to Emergency Mode. The Hot Microphone feature is now disabled and PTT operation reverts back to normal.\n\nTo resume, press again.\n\nIf talk permit is granted to another member of the group, an “Emergency call received” tone will be heard.\n\nIf configured by your service provider, your MTM800 will automatically attempt to get talk permit again and the Wait For Mic message will be displayed.\n\n**NOTE** During this pending time the MTM800 microphone is not active until the Emgcy Mic On message is displayed again.\n\nReceiving an Emergency Group Call\n\nA terminal in TMO receives an Emergency Group Call to the selected group or associated ATG (Announcement Talkgroup), or scanned group. If the ATG is the currently selected group, the terminal will receive the Emergency\n\nGroup Call to the group associated with this ATG. (For information on the ATG, see page 30.)\n\nWhen the MTM800 receives the call, the display will show the caller’s identity. If the display is idle, it will show **Emrgncy In Use**.\n\nIf upon entering Emergency mode your MTM800 receives an emergency call, and Hot Microphone was enabled by your Service Provider, the **Wait For Mic** message will be displayed. Your MTM800 will attempt to get a talk permit.\n\n**NOTE** *In Emergency Hot Microphone Mode with powering on the MTM800 by pressing the emergency foot switch (see “Powering On/Off” on page 10): If a microphone/PTT set is connected to the terminal front socket and an external microphone/PTT set is installed the external microphone is opened.*\n\n**Emergency in DMO**\n\nYou can initiate an Emergency Group Call to a group.\n\nYou can receive a call from the selected talkgroup, and (if configured by your Service Provider) from other users within talkback range or from an open group. (An open group is a super-group to which all DMO groups belong.)\n\nEmergency calls can be placed via gateway and repeater. For gateway and repeater settings, see “Gateway/Repeater Selection” on page 43.\n\n**Making an Emergency Group Call**\n\nTo initiate or answer a call:\n\n1. Enter emergency mode by pressing and holding the key.\n2. Press and hold PTT.\n3. Wait for the talk permit tone (if configured) and talk.\n4. Release PTT to listen.\n\nReceiving an Emergency Group Call\n\nThe display shows the caller’s identity as a private number or an alias. If the display is idle, it will show Emrgncy-In Use.\n\nGPS Location Service\n\nGeneral\n\nYour terminal’s GPS Location feature uses information from Global Positioning System (GPS) satellites orbiting the earth to determine the approximate geographical location of your terminal. The availability and accuracy of this location information (and the amount of time that it takes to calculate it) will vary depending on the environment in which you are using the terminal.\n\nFor example, GPS location fixes are often difficult to obtain indoors, in covered locations, between high buildings, or in other situations where you have not established a clear broad view of the sky.\n\nSee “IMPORTANT – Things to Keep in Mind”.\n\nThe GPS location Service can assist your Dispatcher or Colleagues in many ways such as more efficient deployment of resources or locating your terminal if you trigger your emergency service.\n\nThe terminal can be configured to display location information on the terminal’s display or to send it over the air to your dispatcher where it can be displayed in control center (Please check with your Service Provider on the configuration of your terminal).\n\nIMPORTANT – Things to Keep in Mind\n\nWhere adequate signals from multiple satellites are not available (usually because your GPS antenna cannot establish a view of a wide area of open sky), the GPS feature of your terminal WILL NOT WORK. Such situations include but are not limited to:\n\n- In underground locations\n- Inside of tunnels or parking garages\n- Under any other metal or concrete roof or structure\n- Near a powerful radio or television tower\n\n• When your GPS antenna is covered (for example, by your hand or other object) or facing the ground\n• In temperature extremes outside the operating limits of your terminal\n\nEven where location information can be calculated in such situations, it may take much longer to do so. Therefore, in any emergency call, always report the location to your dispatcher.\n\nFurthermore, please note that even where adequate signals from multiple satellites are available, your GPS feature will only provide an approximate location, often within 20 – 100 meters from your actual location.\n\n**Enhancing GPS Performance**\n\nSometimes the GPS feature of your terminal may be unable to complete a location calculation successfully. You will see a message indicating that your terminal cannot see enough visible satellites.\n\nTo maximize the ability of your terminal to determine a location fix please note the following guidelines:\n\n• The GPS feature works best where there is nothing between your terminal and a large amount of open sky. If possible, go outside, away from tall buildings and foliage.\n• Position your vehicle to enhance reception, giving the antenna clear access to satellite signals. Signals from GPS satellites are transmitted to your GPS antenna, which is in your terminal antenna. Do not cover the antenna area with your fingers or anything else.\n• Stay in network coverage. Depending on who your service provider is, the network will provide your terminal with information that helps determine your location more quickly and accurately.\n\nGPS Enable/Disable (Menu 9 2)\n\n1. From the main menu, press Menu 9 Location – 2 Interface. The current selection (On/Off) is highlighted. The display shows:\n - On — Location Service On\n - Off — Location Service Off\n\n2. Scroll to your selection and press Set.\n\nIf GPS is enabled but the radio is not synchronized to the GPS satellites the following idle screen is displayed:\n\nEntering GPS Location Service (Menu 9)\n\nTo enter the GPS sub-menu, press Menu – 9 Location.\n\nPosition — provides the actual position information.\n\nInterface — allows you to enable/disable the GPS location service.\n\nThis estimate of accuracy of the calculated location is only a very rough estimate and may vary substantially from the actual accuracy of the approximate location information reported.\n\nNOTE\n- The variation will vary in accordance to the GPS Configuration set by your Service Provider.\n- The availability of the GPS Location menus is dependent on your terminal configuration, please contact your Service Provider for further details.\n\nViewing Your Position (Menu 9 1)\n\n1. From the main menu, press Menu – 9 Location – 1 Position.\n\n2. This displays the following information about the last time your location was calculated (if available):\n - UTC — The time the location was last calculated.\n\nLAT — The latitude expressed in degrees, minutes, and seconds.\n\nLNG — The longitude expressed in degrees, minutes, and seconds.\n\nSAT — The number of satellites used to calculate the location. In general, more satellites make for better accuracy.\n\n3. Scroll to view the entire screen.\n\nTo calculate your location again, press Update. It may take your terminal several minutes to complete the process of determining your location. During this time, a message usually appears on your terminal's display stating:\n\nInsufficient Visible Satellites, or\n\nInsufficient Visible Data.\n\nFor tips on getting the best location calculation, see “Enhancing GPS Performance” on page 69.\n\nThe Position screen displays the updated information. To cancel a location calculation before it is completed:\n\n- Press Back to return to the previous screen.\n\nEach time approximate location of your terminal is calculated, the latest location information is stored in your terminal and remains there even when your terminal is powered off. You will see this information the next time you view the Position screen.\n\nIf you received a terminal call or alert while attempting to determine your location, the Position screen will disappear, but your terminal will continue attempting to determine its location. If it is successful, the new location information will be displayed the next time you view the Position screen.\n\nThe Menu\n\nEntering the Menu Options\n\nYou can enter the menu options during a call. If you are viewing a menu when a new call starts, the terminal will exit the menu.\n\nBy Scrolling\n\n1. From any mode, press Menu to enter the Menu.\n2. To scroll to the required option (such as 2 Addr. Book), press Menu or .\n3. To enter the option, press Ok.\n\nIf the sub-menu contains a further set of sub-menus as in the example below, repeat steps 2 and 3.\n\nBy Shortcut\n\nYou can use the number next to the option as a shortcut to access the required sub-menu.\n\n1. From any mode, press Menu.\n2. Key the number of the required option.\n\nFor example, to reach 2 Address Book – 1 Private – 4 Mem Usage, press Menu and key the option numbers 2 1 4.\n\nExiting the Menu Options\n\nTo exit the menu or sub-menu, press Back or .\n\nExiting the Menu\n\nPress and hold Back from any menu option. The display returns to the mode previous to entering the Menu.\n\nNOTE If enabled by your Service Provider, the menu could time out if no keypresses are detected for a preset period of time.\n\nList of Menu Options\n\n1 Messages\n - 1 Send Sts\n - 2 Inbox\n - 3 Send Msg\n - 1 New\n - 2 Templates\n - 3 Predefined\n\n2 Addr. Book\n - 1 Private\n - 2 Phone\n - 3 PABX\n - 1 Add ID / Add Phone / Add Ext\n - 2 abc Order\n - 3 By Loc’t’n\n - 4 Mem Usage\n - 4 My Groups\n - 1 Select\n - 2 View\n - 3 Add Group\n - 1 Add TMO\n - 4 Remove Grp\n - 2 Add DMO\n - 5 Remove All\n\n3 Security\n - 1 Keylock\n - 2 PIN Protect\n - 1 On\n - 2 Off\n - 3 Change Code\n - 4 AirEncrypt\n - 5 K Validity\n - 6 TMSCK Valid\n - 7 DMSCK Valid\n - 8 Covert Mode\n - 1 On\n - 2 Off\n - 9 DMO SCK\n\n4 Setup\n - 1 Tones\n - 1 Ring Style\n - 1 Duplex <9 styles>\n - 2 Simplex\n - 2 Keypad Tone\n - 1 On <9 styles>\n - 2 Off\n - 3 All Tones\n - 1 On\n - 2 Off\n - 4 Talk Permit\n - 1 No Tone\n - 2 Short Tone\n - 3 Normal Tone\n - 5 Periodic Alert\n - 1 Alert\n - 2 Period\n - 2 Language\n - 1 English\n - 2 简体中文\n - 3 繁體中文\n - 4 <User Defined>\n - 3 Data Setup\n - 1 Voice Only\n - 2 Data Only\n - 3 Voice&Data\n - 4 Backlight\n - 1 Manual\n - 2 Semi-auto\n - 3 Auto\n - 4 Disable\n - 5 to 6: see next page\n\n| 4 Setup (cont’d) | 5 Time & Date | 1 Display | 1 Time & Date |\n|------------------|--------------|-----------|---------------|\n| | 2 Set | | 2 Time Only |\n| | 3 Time Offset| | 3 Date Only |\n| | 4 Format Time| | 4 Off |\n| | 5 Format Date| | |\n| | 6 Acc’ry Type| | |\n| | | 1 Standard | |\n| | | 2 Handset | |\n| | | 3 External | |\n| | | 4 External & Std | |\n| 5 Own Number | 1 Private Num| | |\n| | 2 Phone Num | | |\n| 6 Networks | 1 Networks Sel| | 1 Home Only |\n| | 2 Oper. Mode | | 2 Select Net |\n| | | 1 Trunk Mode| |\n| | | 2 DirectMode| |\n| | 3 TXI Mode | | 1 Activate |\n| | | | 2 Deactivate |\n| 7 Scan | 1 Scanning | | 1 On/Off |\n| | 2 Active List| | 2 Select List |\n| | 3 Scan Lists | | |\n| | <40 lists> | | |\n| 8 Recent Call | 1 Dialed | | 1 Add Group |\n| | 2 Received | | 2 View List |\n| | 3 Missed | | 3 Edit List |\n| 9 More … | 1 Location | | 4 Rename |\n| | 2 Packet Data| | 5 Clear List |\n| | | 1 Position | |\n| | | 2 Interface | 1 On |\n| | | | 2 Off |\n| | | 1 Sent | |\n| | | 2 Received | |\n| | | 3 Bandwidth| |\n| | | 4 Encryption| |\n\nIt is possible that some menu numbers are than the listed. Some options can be enabled/disabled by your Service Provider which can cause the exact menu index numbers to vary.\n\n**Messages (Menu 1)**\n\nRefer to “Messages” on page 99 for details.\n\n**Address Book (Menu 2)**\n\nTo enter the Address Book sub-menu, press Menu – 2 Addr. Book.\n\n- This sub-menu allows you to add, search, edit, or erase entries in the private, phone and PABX address books.\n\n**NOTE**\n\nUpdating your private call Address Book is done in the same way as updating the phone Address Book and the PABX Address Book. When using shortcuts to reach the relevant sub-menus, be sure to use the correct digit sequences referenced in the list of menu options on page 73.\n\n**NOTE**\n\nIf set up by your Service Provider, it is not possible to create or edit an Address Book entry or to dial a number which is not in the Address Book. The menu items for creating, editing, and deleting contacts in the Address Books are not available.\n\n- Select, view, add, or remove favourite groups.\n\n**Updating the Private Call Address Book (Menu 2 1)**\n\nTo enter the Private sub-menu, press Menu – 2 Addr. Book – 1 Private.\n\nThis sub-menu allows you to edit your private call address book.\n\nAdding a Number (Menu 2 1 1)\n\nTo enter the sub-menu, press Menu – 2 Addr. Book – 1 Private – 1 Add ID.\n\nNOTE\n\n1 Add ID changes to 1 Add Phone or to 1 Add Ext. depending on the address book edited.\n\n1. Press Add. The MTM800 will prompt you to add an entry to the existing list. The entry is composed of a number, name, and location. First enter the number and name.\n\n2. Press Ok to confirm. Then select the location of the entry in the list.\n\n3. The first empty location (if any) is suggested as the default location for storing the entry. You can select another location either by scrolling through the list of locations or by typing the location number. If a location is already used, you will be prompted to overwrite the existing entry started in that location.\n\n4. When the entry is successfully stored, the display returns to the entry adding screen within a few seconds.\n\nSearching the Address Book Alphabetically (Menu 2 1 2)\nor by Location (Menu 2 1 3)\n\n1. To enter the sub-menu, press Menu – 2 Addr. Book – 1 Private and 2 abc Order or 3 By Locat’n.\n\n2. Press Find. Scroll through the list alphabetically (or type the first letter of the name you are searching in the pre-stored list). Alternatively, scroll through the list by location (or type the location number).\n\nAfter finding a number, press PTT to start a call.\n\n3. Press Optns and scroll to your selection:\n - Edit the entry. The original location is suggested as the default location for storing the edited entry.\n To select another location, scroll through the list of locations or type the location number. If a location is already used, you will be prompted to overwrite the existing location.\n\nWhen the location is successfully stored, the screen returns to the list display.\n\n- **Erase** the entry. The screen returns to the list display.\n\n**Memory Usage** (Menu 2 1 4)\n\nTo enter the sub-menu, press Menu – 2 Addr. Book – 1 Private – 4 Mem Usage.\n\nThis screen shows how much memory is left to add new entries to the address book.\n\n**My Groups** (Menu 2 4)\n\nOnce in the menu, select 2 Addr. Book – 4 My Groups.\n\nThis sub-menu allows you to edit your favourite group list.\n\n**Entering My Group** (Menu 2 4 1)\n\n1. Once in the menu, select 2 Addr. Book – 4 My Groups – 1 Select.\n\n My Groups is displayed as the selected range alias. You can now scroll through the favourite group list. Press Ok to select.\n\n **NOTE**\n\n *My Groups range is situated after the last range. Scrolling past the last group in the My Groups range will therefore bring you back to the first valid range.*\n\nWhen selecting “My Groups” and no groups exist from the current DMO/TMO mode, you may be forced to switch to DMO from TMO or TMO from DMO. In this case you will be prompted to accept the mode change.\n\nViewing My Group (Menu 2 4 2)\n\n1. Once in the menu, select 2 Addr. Book – 4 My Groups – 2 View.\n2. Scroll through the favourite group list.\n\nAdding a Group to My Groups (Menu 2 4 3)\n\n1. Once in the menu, select 2 Addr. Book – 4 My Groups – 3 Add Group.\n2. Select one of the following:\n - **Add TMO** — You may choose any TMO Range/Group.\n - **Add DMO** — You may choose any DMO Range/Group.\n\nRemoving a Group from My Groups (Menu 2 4 4)\n\n1. Once in the menu, select 2 Addr. Book – 4 My Groups – 4 Remove Grp.\n2. Select the group you wish to remove. In the “Remove?” prompt screen, select Yes to confirm removal.\n\nRemoving All Groups from My Groups (Menu 2 4 5)\n\n1. Once in the menu, select 2 Addr. Book – 4 My Groups – 5 Remove All.\n2. In the Remove? prompt screen, select Yes to confirm removal.\n\nSecurity (Menu 3)\n\nTo enter the Security sub-menu select 3 Security.\n\nLocking/Unlocking the Keypad (Menu 3 1)\n\nTo prevent accidental key presses:\n\n1. From the menu, select 1 Keylock. All keys are locked except the On/Off key.\n\n **NOTE** When there is an incoming call and the keypad is locked, you can still use PTT, and Reject.\n\n2. To unlock the keypad, press Menu 3 1.\n\n **NOTE** The Emergency Key is not locked. Entering Emergency Mode, unlocks all keys.\n\nPIN Protect (Menu 3 2)\n\nNetwork access protection is configured by your Service Provider:\n\nNo access to network operation — you can only send or receive Emergency Calls. Unit lock takes effect at the next power on.\n\nTo protect access to network operation:\n\n1. Press Menu – 3 Security – 2 PIN Protect.\n2. Select 1 On to set the protection (or 2 Off to cancel it).\n3. At the Code? prompt enter the 4-digit code (factory setting is “0000”). To avoid disclosure of the PIN, asterisks are displayed instead of the code digits. Press Ok. The display will show one of the following messages:\n\n **Unit Locked** — you entered the correct code. The display returns to the Security sub-menu and shows the active setting: 1 On.\n\n **Unit Unlocked** — you entered the correct code. The display returns to the Security sub-menu and shows the active setting: 2 Off.\n\nTo unlock the MTM800 after powering on, enter the code at the prompt. The MTM800 enters the default home mode.\n\nIf you fail to enter the correct code, the following message will be displayed:\n\nIncorrect Code Entered — You are prompted to try again. After failing three times, your MTM800 will be blocked.\n\n**How to unblock the MTM800**\n\nThe display shows **Unit Blocked**. When your MTM800 is blocked, you cannot send or receive calls. You can only enter a code or power off the MTM800.\n\nTo unblock the MTM800, enter the PUK (Personal Unblocking Key). The PUK is an eight-digit master code to be obtained from your Service Provider.\n\nAfter entering the PUK successfully, you will be prompted to replace the forgotten PIN code.\n\nAt the **New Code?** prompt, enter the new 4-digit code, and repeat the code to confirm. If the code does not match, you will be prompted to enter it again until the new code message is accepted.\n\n**Change Code (Menu 3 3)**\n\n*NOTE* The standard factory lock code is “0000”.\n\nTo change the PIN code:\n\n1. Scroll to **3 Change Code** and press **Ok**.\n2. At the **Old Code?** prompt, enter the 4-digit code.\n - If the old code does not match at verification, the display shows the Incorrect Code Entered message and returns to the Security sub-menu.\n - If the entered code matches the old code, the display prompts you to enter a new 4-digit code and to repeat it for confirmation. If the confirmation code does not match the new code, the display prompts you to re-enter the new code.\n\n3. When the new code is accepted, the display returns to the Security sub-menu.\n\n**Air Encryption On/Off (Menu 3 4)**\n\nTo enter the sub-menu, press Menu – 3 Security – 4 AirEncrypt.\n\nThis sub-menu allows you to view air encryption On/Off state. Call encryption provides service confidentiality between you and the system.\n\nIf encryption is on and you receive a clear call (i.e. unencrypted), the MTM800 will display a Call Isn’t Encrypt message.\n\n**NOTE** You cannot manually disable Air Encryption (if enabled) from the menu. This menu item only indicates if Air Encryption is enabled at that moment.\n\n**NOTE** The Air Encryption feature is ONLY enabled depending on your Service Provider.\n\n**Air Encryption Key Deletion**\n\nPlease check with your Service Provider whether the terminal is provided with air interface encryption keys.\n\nYou can delete the air interface encryption keys from the terminal by entering the following sequence from the keypad: **00##\n\n**CAUTION** Using this feature will disable the terminal, and your Service Provider will need to re-enable the terminal.\n\n**K Validity (Menu 3 5)**\n\nOnce in the menu, select 3 Security – 5 K Validity.\n\nK (Key) is a secret key the infrastructure uses to authenticate the MTM800 in the system. It is part of the authentication that provides service confidentiality between your MTM800 and the system.\n\nTo verify K validity, press **Ok**. The display will show one of the following messages:\n\n- **K is Valid** — the infrastructure can authenticate your MTM800.\n- **K is Invalid** — the infrastructure shall not authenticate your MTM800. Please call your Service Provider to restore K to your MTM800.\n\n**TMSCK Valid? (Menu 3 6)**\n\nOnce in the menu, select 3 Security – 6 TMSCK Valid?\n\nSCK (Static Cipher Key) is a secret key the infrastructure uses to encrypt call and data in the system. Air interface encryption provides service confidentiality between your MTM800 and the system. Your MTM800 should be provided with a set of SCKs.\n\nTo verify SCK validity for TMO, press **Ok**. The display will show one of the following messages:\n\n- **TMSCK is Valid** — your MTM800 can work encrypted in TMO.\n- **TMSCK is Invalid** — your MTM800 cannot work encrypted in TMO. Please call your Service Provider to restore SCKs to your MTM800.\n\n**DMSCK Valid? (Menu 3 7)**\n\nOnce in the menu, select 3 Security – 7 DMSCK Valid?\n\nSCK (Static Cipher Key) is a secret key the infrastructure uses to encrypt call and data in the system. Air interface encryption provides service confidentiality between your MTM800 and the system. Your MTM800 should be provided with a set of SCKs.\n\nTo verify SCK validity for DMO, press **Ok**. The display will show one of the following messages:\n\n- **DMSCK is Valid** — your MTM800 can work encrypted in DMO.\n\nDMSCK is Invalid — your MTM800 cannot work encrypted in DMO. Please call your Service Provider to restore SCKs to your MTM800.\n\n**Covert Mode (Menu 3 8)**\n\nFrom the main menu, select 3 Security – 8 Covert Mode.\n\n**Set Covert Mode to On**\n\nSelect **On**. All tones are set to off, and the backlight and the LED are disabled immediately.\n\n![Menu Options]\n\n*The audio is further more routed to the external loudspeaker until the loudspeaker is switched off. It is recommended to use e.g. a Telephone Style Handset in Covert Mode.*\n\n**Set Covert Mode to Off**\n\nSelect **Off**. All settings for tones and backlight are restored. The LED is enabled and the message *Covert Mode Off* is shown.\n\n**DMO SCK (Menu 3 9)**\n\nOnce in the menu, select 3 Security – 9 DMO SCK.\n\n**Key version** is displayed when you select the option.\n\nAir Interface encryption provides service confidentiality between your MTM800 operating in Direct Mode and another terminal or a group of terminals operating in Direct Mode.\n\nYou can change the current key, if the key change operation is allowed by your Service Provider.\n\nTo change the key, if not in a call, select **Next**. The display will show the following message: *Change to version*...\n\n- Select **Yes** to change the key. *Key version changed* display will appear.\n- Select **No** to leave the key. *Key version* display will appear.\n\nSetup (Menu 4)\n\nTo enter the sub-menu, press Menu – 4 Setup – Ok.\n\nThis sub-menu allows you to change your MTM800 configuration: key tones, language, ring style, time, date or data setup.\n\nSetting the Ring Style (Menu 4 1)\n\nThis option allows you to set the incoming call ring style. Your MTM800 features nine selectable ring styles for Duplex and Simplex calls:\n\n1. Press Menu – 4 Setup – 1 Ring Style – 1 Duplex or 2 Simplex – Ok.\n\n2. Scroll to the desired style, and press Set. The display shows your new selection. You will hear the new ring style immediately for a few seconds. If necessary, turn the Volume knob to adjust the volume.\n\nSetting the Display’s Working Language (Menu 4 2)\n\nOnce in the Setup menu, select 2 Language. The display shows the current language used. You can customize your MTM800 to operate in English, Simplified Chinese, Traditional Chinese, or in a language defined by your Service Provider. The default setting from factory is English.\n\nScroll to the desired language and press Set. The display shows the selected language for a few seconds.\n\nSetting Up Data Mode (Menu 4 3)\n\nYou can connect the MTM800 to an external device (such as a laptop or desktop PC). The MTM800 will then be capable of transmitting and receiving data from the external device. The\n\nexternal device must run an application complying with the TETRA standards.\n\nOnce in the Setup menu, select 3 Data Setup.\n\nThe display shows the current setting:\n\nVoice Only — The MTM800 will receive and transmit voice calls only.\n\nData Only — The MTM800 acts as a modem. The MTM800 will reject incoming and outgoing voice calls, except for emergency calls, status and text messages.\n\nVoice&Data — The MTM800 acts as a modem but voice calls will have priority over data calls and will interrupt them.\n\nScroll to the desired setting and press Set.\n\nIn Data Only and in Voice&Data modes, the “Data Connected” icon is displayed after you have connected the MTM800 to the external device and the MTM800 is ready for data transfer. The Data Transmit/Receive icon indicates that data transfer is currently taking place.\n\nThe MTM800 ends the Ambience Listening (AL) call and the microphone is closed when the MTM800 is in one of the following states:\n\n- Entering the out-of-service area\n- Outgoing packet data call setup\n\nTo exit data mode, return to 3 Data Setup and select Voice Only. The MTM800 returns automatically to Voice communication, except when in Data Only Mode.\n\n**NOTE**\n\n*Data services are available only in TMO. Data Services are blocked in TXI Mode.*\n\n**Setting Backlight (Menu 4 4)**\n\nOnce in the Setup menu, select 4 Backlight.\n\nThis option allows you to configure your MTM800’s backlight setting (see also “Dimming the Display” on page 27).\n\nYour MTM800 has 4 backlight settings:\n\n**Manual (Menu 4 4 1)**\nPress # to change the backlight intensity in four steps.\n\n**Semi-Auto (Menu 4 4 2)**\nPress # to turn on or turn off the backlight. Any other key press does not turn the backlight on. The backlight remains on until you press the # to turn it off, or a pre-programmed timer runs out.\n\n**Auto (Menu 4 4 3)**\nAny key press turns the backlight on. The backlight remains on until you press # to turn it off, or a pre-programmed timer runs out.\n\n**Disable (Menu 4 4 4)**\nThe backlight feature is disabled.\n\n**Setting Time & Date Features (Menu 4 5)**\nOnce in the Setup menu, select 5 Time&Date.\nThis sub-menu allows you to control the displayed time and date.\n\n**Time&Date Display Settings (Menu 4 5 1)**\nOnce in the Setup menu, select 5 Time&Date, and then 1 Display.\nThe display shows the current setting:\n1. **Time&Date** — The MTM800 displays time and date.\n2. **Time Only** — The MTM800 displays time only. **Format Date** option is disabled.\n3. **Date Only** — The MTM800 displays date only. **Format Time** option is disabled.\n\n4. **Off** — The MTM800 does not display time nor date. Format Time and Format Date options are disabled.\n\nScroll to the desired setting and press Set. Press Back to exit.\n\n**NOTE** *Time and date are synchronized by the infrastructure. When not within the infrastructure signal range you can set the values manually.*\n\n**Setting Time and Date (Menu 4 5 2)**\n\nTo set time and/or date:\n\n1. Enter the Setup menu.\n2. Select Time&Date, and press Ok.\n3. Select Set, and press Ok.\n\nEnter time using navigation keys or 2(Up), 8(Down), 4(Left), 6(Right) keys from the alphanumeric keypad and press Set. Press Back to exit.\n\n**Setting Offset (Menu 4 5 3)**\n\nTo set local time offset:\n\n1. Enter the Setup menu.\n2. Select Time&Date, and press Ok.\n3. Select Time Offset, and press Ok.\n\nEnter offset value using navigation keys or 2(Up), 8(Down), 4(Left), 6(Right) keys from the alphanumeric keypad and press Set. Press Back to exit.\n\n**NOTE** *You can adjust the offset value, with 15 minute steps, up to 14 hours ahead or behind.*\n\n**Setting Time Format (Menu 4 5 4)**\n\nTo change displayed time format between 24-hour scale and 12-hour scale:\n\n1. Enter the Setup menu.\n2. Select Time&Date, and press Ok.\n3. Select Format Time, and press Ok.\n\nChoose required setting and press Set. Press Back to exit.\n\nSetting Date Format (Menu 4 5 5)\n\nTo change displayed date format between DD/MM/YY, MM/DD/YY and DD-MON-YY:\n\n1. Enter the Setup menu.\n2. Select Time&Date, and press Ok.\n3. Select Format Date, and press Ok.\n\nChoose required setting and press Set. Press Back to exit.\n\nSetting Tones (Menu 4 6)\n\nOnce in the Setup menu, select 6 Tone\n\nThis sub-menu allows you to activate/deactivate the keypad tones and other tones used in the MTM800.\n\nScroll to the desired setting and press Set.\n\nThe display shows the current setting. When set to On, the MTM800 will sound a tone at every key press. When set to Off, the MTM800 will mute the keypad tone.\n\nFor a detailed list of tones, see “Tones” on page 112.\n\nSetting Keypad Tone (Menu 4 6 1)\n\nTo activate/deactivate keypad tone at every key press:\n\n1. Enter the Setup menu.\n2. Select Tones, followed by Keypad Tone, and press Ok.\n3. Scroll through the settings by using the navigation keys.\n4. Choose required setting, and press Set, or press Back to exit.\n\nSetting All Tones (Menu 4 6 2)\n\nTo activate/deactivate all tones (keypad tone and other activity tones used in your MTM800):\n\n1. Enter the Setup menu.\n2. Select Tones, followed by All Tones, and press Ok.\n\n3. Scroll through the settings by using the navigation keys.\n\n4. Choose required setting, and press Set, or press Back to exit.\n\n**Setting Talk Permit Tone (Menu 4 6 3)**\n\nThere are 3 tone settings:\n\n- **No Tone** — no tone heard upon pressing the PTT\n- **Short Tone** — a short tone heard upon pressing the PTT\n- **Normal Tone** — the factory-default tone heard pressing the PTT\n\nTo change your Talk Permit Tone settings:\n\n1. Enter the Setup menu.\n2. Select Tones, followed by Talk Permit, and press Ok.\n3. Scroll through the settings by using the navigation keys.\n4. Choose required setting, and press Set, or press Back to exit.\n\n**Setting Periodic Alert (Menu 4 6 4)**\n\nPeriodic alert indicates the missed calls and the unread messages. For each indication the unread message tone is played with the amber LED color. This feature can be disabled/enabled by the user.\n\n1. Enter the Setup menu.\n2. Select Tones, followed by Periodic Alert, and press Ok.\n3. Select Alert and choose required setting, and press Set to select, or press Back to exit.\n\nThe user can also set the time between the indications.\n\n1. Enter the Setup menu.\n2. Select Tones, followed by Periodic Alert, and press Ok.\n\nSelect Period and choose required setting, and press Set to select, or press Back to exit.\n\n**Setting Accessory (Menu 4 7)**\n\nOnce in the Setup menu, select 7 Acc’ry Type. You can select one of the following options:\n\n- **Standard** — Select this if a Fist Microphone and an external speaker are connected.\n- **Handset** — Select this if a Telephone Style Handset is connected.\n- **External** — Select this if an external microphone and an external speaker are connected.\n- **External & Std** — Select this option if the external mic is to be default one unless PTT is pressed.\n\n**NOTE** Accessories has to be configured by MS/CPS user in order to use them.\n\n**Own Number (Menu 5)**\n\nUse this feature to view your own private or phone number at any time.\n\n**Viewing Private or Phone Number (Menu 5 1 or Menu 5 2)**\n\nTo enter the sub-menu, press Menu – 5 Own Number and afterwards 1 PrivateNum or 2 Phone Num. The displayed private number cannot be modified. To modify the displayed phone number, press Set. The new phone number does not modify the MTM800 number in the system.\n\nNetwork (Menu 6)\n\nTo enter the sub-menu, press Menu – 6 Networks.\n\nThis sub-menu allows you to select the network your MTM800 will be registered to, and what mode it operates on.\n\nSelecting Your Network (Menu 6 1)\n\nThis sub-menu allows you to select the network your terminal will be registered to.\n\nSelecting Home Only Network Registration (Menu 6 1 1)\n\nTo enter the sub-menu, press Menu – 6 Networks – 1 Networks Sel – 1 Home Only.\n\nSelecting this option causes your MTM800 to recognise the first network on the allowed Network List only and to register to it.\n\nUsing the Select Net Option Registration (Menu 6 1 2)\n\nTo enter the sub-menu, press Menu – 6 Networks – 1 Networks Sel – 2 Select Net.\n\nIf configured by your service provider, this option allows you to select manually the network from the allowed Network List you want your MTM800 to be registered to.\n\nThe list of the allowed networks is displayed.\n\nScroll to the desired network and press Set.\n\nThe display shows XXX Selected. The XXX stands for the name of the network selected.\n\nAfter a few seconds the display returns to the Network submenu.\n\nNOTE\n\nIt is up to your service provider to ensure your own terminal identity is allowed to register on other networks in your list. Some talkgroups may not be available on other networks.\n\nSetting Operating Mode (Menu 6 2)\n\nTo enter the sub-menu, press Menu – 6 Networks – 2 Oper. Mode.\n\nThis sub-menu allows you to select the mode your MTM800 will be operating on.\n\nTo set up your operating mode:\n\n- Select 2 DirectMode, or 1 Trunk Mode, and press Ok.\n\n**NOTE** It is not possible to switch from Direct Mode to Trunk Mode, if the terminal is in Transmit Inhibit Mode.\n\n**NOTE** To change the Operation Mode quickly you can use one of the programmable keys (if set up by your Service Provider).\n\nSetting Transmit Inhibit (TXI) Mode (Menu 6 3)\n\nTo enter the sub-menu, press Menu – 6 Networks – 3 TXI Mode.\n\nThis mode should always be set before entering areas where transmission is prohibited, e.g. in hospitals or in potentially explosive areas.\n\nTo activate the TXI Mode:\n\n- Select 1 Activate, and press Ok.\n\nThe terminal will sound the “Transmit Inhibit” tone. The display blinks between the Talkgroup name and the message TXI Mode, and the solid orange LED indicates the TXI Mode.\n\n**NOTE** All menu options which cause transmitting are blocked in TXI Mode. It is not possible to change the Talkgroup.\n\nTo deactivate the TXI Mode, e.g. after you have left the area where transmission is prohibited:\n\n- Select 2 Deactivate, and press Ok.\n\nThe terminal sounds the “Transmit Inhibit” tone and returns back to Group Mode or Direct Mode, if Direct Mode was the last selected mode.\n\nScan (Menu 7)\n\nTo enter the sub-menu, press Menu – 7 Scan.\n\nThis sub-menu allows you to activate/deactivate scanning, view the active scan list, and edit the scan lists.\n\nNOTE It is not possible to enable or disable Talkgroup scanning in TXI Mode.\n\nSetting Talkgroup Scanning (Menu 7 1)\n\nTo enter the sub-menu, press Menu – 7 Scan – 1 Scanning.\n\nThis sub-menu allows you to activate/deactivate the scanning of a list of predefined talkgroups programmed in the MTM800. The MTM800 will join any talkgroup call as long as this talkgroup is defined in the scan list and scan is turned on.\n\nScroll to the desired setting and press Ok. If it is set to Off, display shows the following state:\n\nWhen set to On, the display shows the following state:\n- The last selected scan list, or\n- the first list in the scan lists.\n\nTo select a list other than the one shown, scroll through the scan lists and press Set.\n\nTo change your selection:\n- Select Menu – 7 Scan – 1 Scanning – 1 SelectList,\nor\n- Enter Group mode and select Optns – Scan – 1 SelectList.\n\nA message indicating that all scan lists are empty.\n\nSelect 3 Scan Lists to fill the scan list(s). See page 94.\n\nWhen set to Off, scanning is deactivated.\n\nAfter completing the settings, the display returns either to the Scan sub-menu or to Group mode.\n\nTo view the active scan list and its talkgroup status, see section below.\n\n**Viewing the Active Scan List (Menu 7 2)**\n\nTo enter the sub-menu, press Menu – 7 Scan – 2 Active List.\n\nThis sub-menu allows you to view the active scan list.\n\nThe display will show one of the following statuses:\n\n- There is a selected, inactive scan list. Scanning is off.\n- There is no selected scan list. Scanning is off.\n- There is a selected, active scan list. Scanning is on.\n\nTo see the talkgroup status (active or not active) and priority (if pre-programmed), press View, and scroll through the talkgroups.\n\n**Editing Scan Lists (Menu 7 3)**\n\nTo enter the sub-menu, press Menu – 7 Scan – 3 ScanLists.\n\nThe display allows you to scroll through the scan lists to see the number of talkgroups used per list.\n\nTo edit/view the contents of a scan list, press Optns and scroll to your selection.\n\nPress Ok to select one of the following options:\n\n1. **Add** a talkgroup to the selected scan list.\n Every added talkgroup (including a favourite group) comes with its range, its name or number, and its priority (if pre-programmed).\n\n - To select a range, scroll through the range list. The list does not show ranges whose talkgroups are fully used in the selected scan list. Press Ok to select a range.\n\n• To select a talkgroup, scroll through the talkgroup list within the selected range. The list shows talkgroups that are not in the selected scan list. Press **Ok**.\n\n• To set a priority to a talkgroup, scroll through the priority list: high, medium, or low.\n\nA call from a high priority talkgroup and with a higher priority than the on-going call will interrupt it.\n\nA call from a medium/low priority talkgroup will not interrupt the on-going call.\n\n2. **View** the contents of the active scan list (range, talkgroup, and priority if pre-programmed) by scrolling through it.\n\n3. **Edit** the scan list talkgroups. Scroll to your selection and press **Optns**. Scroll to one of the following options:\n\n • To **Remove** a talkgroup from the selected scan list, select 1 **Remove Grp** and press **Ok**. You will be prompted to remove the selected talkgroup. After a few seconds, the display shows the following talkgroup in the selected scan list.\n\n • To change the talkgroup **Priority**, select 2 **Priority** and press **Ok**. Scroll to the selected priority and press **Ok**. After a few seconds, the display shows the new setting of the selected talkgroup.\n\n4. To **Rename** the active scan list, enter a new name (alias) and press **Ok**. The display shows the new setting.\n\n5. To **Clear** all talkgroups from the selected scan list, press **Yes**. You will be prompted to remove all talkgroups from the selected scan list. After a few seconds, the display shows the new setting of the selected scan list.\n\nRecent Calls (Menu 8)\n\nYou can view the history of all calls:\n\n- Dialled Calls\n- Received Calls — calls you answered\n- Missed Calls — calls received but not answered, or rejected by the MTM800.\n\nEach list of calls may contain up to 10 numbers for all modes (Phone, PABX, or Private), the more recent call being at the top of the list. Old calls are deleted to make room for new ones, if necessary. A number dialled more than once, will appear only once in the list.\n\nUpon receiving a missed call notification, the MTM800 will display the Missed Calls list.\n\nWhen a call is received during an active call, the number is written to the Missed Calls list. This list will be invoked automatically at the end of the call.\n\n1. From the menu, select 8 Recent Calls.\n2. Scroll to the desired history and press Ok.\n3. Scroll through the list of calls. Select Erase to remove an entry from the list. If required, enter the context sensitive menu to save numbers without names in the address book. See “Address Book” on page 75.\n\n4. You can make a Phone, PABX, or Private Call from the entry, depending on the entry you are selecting in the list.\n\n *If your Service Provider has restricted access to the Address Book, it might not be possible to dial up a number which is not in the Address Book.*\n\n5. After completing the call, the MTM800 will return to the Received/Missed/Dialled list, displaying the called number and allowing you to delete or save the number in the address book.\n\nLocation (Menu 9 1)\n\nRefer to “GPS Location Service” on page 68 for details.\n\nPacket Data (Menu 9 2)\n\nThis sub-menu allows you to display statistical values related to a packet data connection. If Multi Slot Packet Data Service is enabled by your Service Provider the screens present the following information:\n\n- Amount of sent data,\n- Amount of received data,\n- Bandwidth of the data session\n- Data encryption status.\n\n**NOTE**\n\n*Data services are only available in TMO. The data option must be set to Voice&Data or Data Only. (Refer to “Setting Up Data Mode” on page 84).*.\n\nViewing Sent Data Statistics (Menu 9 2 1)\n\n1. Select 1 Sent in the Packet Data sub-menu.\n2. The number of KBytes sent since current packet data activation is displayed.\n3. Press More. The throughput is shown in the second screen:\n - 9 kbps (e.g.) — active packet data session.\n - N.A. — standby packet data session.\n\nViewing Received Data Statistics (Menu 9 2 2)\n\n1. Select 2 Received in the Packet Data sub-menu.\n2. The number of KBytes received since current packet data activation is displayed.\n\n3. Press More. The throughput is shown in the second screen:\n\n9 kbps (e.g.) — active packet data session.\nN.A. — standby packet data session.\n\nViewing Bandwidth Status (Menu 9 2 3)\n\nThe bandwidth percentage represents the number of allocated time slots (“channels”) during the data session.\n\n1. Select 3 Bandwidth in the Packet Data sub-menu.\n2. The bandwidth percentage is shown:\n\n75% (e.g.) — active packet data session,\nN.A. — standby packet data session.\n\nNOTE\n\nYour Service Provider has set the maximal number of time slots to allocate to 1, 2, 3, or 4. The bandwidth percentage refers to the possible number of slots (1, 2, 3, or 4) as 100%.\n\nExample:\n50% is displayed, if 2 of 4 possible slots are allocated.\n100% is displayed, if 4 of 4 possible slots are allocated.\n100% is displayed, if 1 of 1 possible slot is allocated.\n\nViewing Encryption Status (Menu 9 2 4)\n\n1. Select 4 Encryption in the Packet Data sub-menu.\n2. The encryption state of the ongoing packet data session is displayed:\n\n- Encrypted\n- Not Encrypted (clear)\n\nMessages\n\nGeneral\n\nThe messaging feature lets you\n\n- send status messages,\n- send short text messages (free text or according to user defined or predefined templates), and\n- receive text messages.\n\nA status is a number corresponding to a pre-programmed message in a list your group recognises. A text message is a short text containing up to 140 characters.\n\n**NOTE** If configured by your Service Provider, it is only possible to send a message to a private number that is stored in the Address Book.\n\nEntering the Messages Sub-menu\n\nTo enter the sub-menu, press Menu – 1 Messages.\n\nThe sub-menu allows you to\n\n- send status messages,\n- read text messages, and\n- send text messages.\n\nScroll to your selection and press Ok to access the next display.\n\n**NOTE** Your MTM800 can receive calls while in the Messages submenu.\n\n**NOTE**\n\n- It is not possible to send a status or text message in TXI Mode.\n- It is not possible to send a status or text message during a call in DMO\n\nWhen a new message arrives, the icon blinks on your display (the icon stops blinking when you enter the Inbox).\n\n**NOTE** If configured by your Service Provider, the MTM800 sounds the “New Mail Received” alert tone if a new message is received whilst your terminal is engaged in a call.\n\nYour MTM800 will enter the Inbox automatically and the icon will not blink.\n\n**Sending a Status Message (Menu 1 1)**\n\n1. Switch to the desired talkgroup, to which you want to send a status message.\n\n2. Press **Status** from any mode, or select Menu – 1 Messages – 1 Send Sts – Ok.\n\n3. In this example, Lunch is the last sent status. To send a different status, scroll to your selection in the list of pre-programmed statuses, or key the status number. To stop scrolling press Cancl. The status message will automatically be displayed on the screen.\n\n From the status sub-menu it is also possible to type a valid 5 digit status number in the user status range.\n\n4. Press **PTT** or or the relevant one-touch numeric key to send the status message.\n\n If your Service Provider has enabled the Targeted Status feature you will see an additional SendTo softkey on the status sending display. Pressing SendTo gives you an option of sending your status as a private call or as a group call.\n\n To enter the address for a private call, either key in the recipients number or scroll through the list of numbers, or press abc to search the address book. For a group call, select the talkgroup within the attached range, then press PTT to send the status message.\n\n The display will show one of the following delivery reports:\n\n - **Status Sent** — the screen exits the status mode.\n - **Sts Failed** — the screen returns within a few seconds to the previous display.\n\nWait for the delivery report before sending a new status.\n\nIf you enter the status menu from a busy talkgroup, the audio is momentarily suspended to allow transmission of your status message.\n\nIf an emergency group call is received the terminal will immediately join that new emergency call.\n\nIf set up by your Service Provider it is not possible to send a status message to a private number that is not in the Address Book.\n\nUsing the Inbox (Menu 1 2)\n\nThe Inbox list contains new or old incoming text messages. The Inbox list can contain up to 20 messages at any time.\n\nTo enter the Inbox, press Menu – 1 Messages – 2 Inbox.\n\nThe status of the list is displayed for a few seconds:\n\n- New message(s) arrived, and the list is full — press Ok to confirm.\n- New message(s) arrived — press any key or wait for a few seconds. The display shows the incoming message.\n- No New or Old Messages — the screen returns to the previous display within a few seconds.\n\nNew Messages\n\nThe display shows the incoming message: its number, state (New/Old), sender, and the first line of the text message.\n\nPress one of the following keys:\n\n- The navigation keys to scroll quickly through text messages.\n- Select Read to read the entire message. Reading an existing text message changes its state from New to Old.\n- The navigation keys to scroll through the content of a message that is longer than one display line (An arrow at the end indicates that the message continues).\n\nAfter reading the message, you can select **Optns** and then one of the following options:\n\n- Scroll to **Erase** and press **Ok** to erase the message. The display shows the next message (if any) or the Messages sub-menu.\n\n- Scroll to **Store** and press **Ok** to store the message as a template in the Template List.\n\n- Scroll to **Forward** and press **Ok** to invoke the Edit Mode. The old message body serves as the default message. Press PTT or to initiate a call. Enter the recipient’s number and press PTT or to send.\n\n- Scroll to **Reply** and press **Ok** to invoke the Edit Mode. The old message body serves as the default message and the message originator is the destination. Press PTT or to initiate a call to the message originator.\n\nPress **Back** to return to the previous display.\n\nThe read message is kept in the Inbox.\n\nA new text message will be displayed immediately. If this message is unread, further new messages can be viewed by re-entering the Inbox.\n\n**Handling Old Messages**\n\nScroll to one of the old text messages.\n\nPress **Optns** and scroll to your selection:\n\n1. Scroll to **Read** and press **Ok**, to display the selected old message.\n\nAfter reading the message, you can select **Optns** and then one of the following options:\n\n• Scroll to **Erase** and press **Ok** to erase the message. When the display shows **Message Erased**, the current message is deleted from the Inbox. The display shows the next message (if any) or the Messages sub-menu.\n\n• Scroll to **Store** and press **Ok** to store the message as a template in the Template List.\n\n• Scroll to **Forward** and press **Ok** to invoke the Edit Mode. The old message body serves as the default message and the message originator is the destination default. Press **PTT** or to initiate a call. Enter the recipient’s number and press **PTT** or to send.\n\n• Scroll to **Reply** and press **Ok** to invoke the Edit Mode. The old message body serves as the default message and the message originator is the destination default. Press **PTT** or to initiate a call to the message originator.\n\n2. Scroll to **Erase** and press **Ok** to erase the message.\n\n3. Scroll to **EraseAll** and press **Ok**, the following message appears:\n • Select **Yes** to erase all messages in the Inbox.\n • Select **No** to return to previous display.\n\n**Receiving Text Messages**\n\nWhen a new message arrives, the icon blinks on your display. The icon stops blinking when you enter the Inbox. If there is no on-going activity in your MTM800, it will enter the Inbox automatically.\n\n**NOTE** For message alert, see settings in the Tones menu option (page 88).\n\nIf your service provider has enabled the PTT Callback feature, then pressing PTT a list containing the message originator (alias or number) and ALL the numbers found in the text message is displayed. Then it is possible to initiate a call to the selected one. Otherwise, PTT will be directed to the currently selected talkgroup.\n\nIf configured by your Service Provider it is not possible to call back to a number that is not in the Address Book.\n\n**Sending a Text Message** (*Menu* 1 3)\n\nThis feature allows you to send new messages, send messages based on user defined templates or send messages based on predefined templates.\n\nThe predefined templates are programmed into your MTM800 by your Service Provider. The user defined templates are Inbox messages or, new Outbox messages that you choose to store in your MTM800 memory. User defined messages may also be programmed into your MTM800.\n\nYou are allowed to edit your messages before sending them. You can send a message when the terminal is idle or during a Group/Emergency/Broadcast Call (if configured).\n\nIf configured, a message will alert you of an incoming Group/Emergency/Broadcast call, of your joining it, or of its end.\n\nIn DMO text messages are sent on frequency attached to the current talkgroup. Make sure you selected desired talkgroup before sending a message. For selecting group details see “Selecting a Talkgroup” on page 30.\n\n**Receiving a Group/Emergency/Broadcast Call before or during text message editing**\n\nYou can be in a call and start message editing while listening to the call.\n\nOr you can start message editing, receive a call and listen to the call while editing the message.\n\nTo join a call received during message editing, press PTT.\n\nSending a text message during a Group Call (if configured)\n\nPress \\( \\text{📞} \\). One of the following might occur:\n\n- The call started before message editing began — The terminal will leave the call and send the message. If the call is still active, the terminal will re-join it.\n- The call started after message editing began — The terminal will leave the call and send the message. The terminal will return to edit mode.\n- The call started before or after message editing began — The terminal will send the message while staying in the call.\n\nSending a text message during Emergency/Broadcast Call (if configured)\n\nPress \\( \\text{📞} \\). One of the following might occur:\n\n- The call started before message editing began. The terminal will leave the call and send the message. The terminal will return to edit mode.\n- The call started after message editing began. The terminal will send the message while staying in the call.\n\nReceiving a Private/Phone/PABX Call during text message editing\n\nMessage editing is automatically interrupted and restored after that call.\n\nEntering the Outbox\n\nPress \\( \\text{Menu} \\) – 1 Messages – 3 Send Msg.\n\nThe Send Msg sub-menu is displayed.\n\nEditing, Storing, and Sending a New Message\n\n1. Scroll to 1 New and press Ok. An empty screen will open. You are allowed to type/edit your message using the keypad. Refer to “Editing the Text” on page 15.\n\n2. Press Optns and scroll to your selection:\n\n- Scroll to Send and press Ok.\n\n- If set up by your Service Provider you have the option to send the message to a private number or a talkgroup.\n\n- Otherwise select the mail recipient of your choice by scrolling through the address list (see page 76) or enter the address directly.\n\nPress Send or PTT or to send the message. The display will show one of the following delivery reports:\n\nMessage Delivered — to indicate that the message was successfully sent and received.\n\nMessage Failed — the message was not received.\n\n- Scroll to Store and press Ok to add your message to the Template List (the number assigned to the message is the lowest free number – in this case template number 3).\n\n**NOTE**\n\nIf provisioned by your Service Provider, it may be possible to compose and send text messages from a busy talkgroup. The group audio will be suspended when a new message or template is being edited. During this time it is possible to receive a new emergency call and message editing will be aborted. If a new private/telephone call is received the message will be restored after that call completes.\n\n**Sending, Editing, and Erasing a User Defined Template**\n\nThe user defined mail templates are received, new, sent, or programmed messages that are stored in the Templates List and may be re-stored for sending.\n\n1. Scroll to 2 Templates and press Ok. The first template in the Template List is displayed.\n\n**NOTE**\n\nIt is possible that the templates numbers are not consecutive.\n\n2. Scroll through the Templates List using the navigation keys and choose the required template.\n\n3. Press Optns and scroll to your selection:\n - Scroll to Send and press Ok.\n - Select the mail recipient of your choice by scrolling through the address list (see page 76) or enter the address directly.\n - Press PTT to send the message.\n The display will show one of the following delivery reports:\n - Message Delivered — to indicate that the message was successfully sent and received.\n - Message Failed — the message was not received.\n - Scroll to Edit and press Ok to edit the message in the template for your needs.\n - Scroll to Erase and press Ok to erase the current template.\n\nSending and Editing a Predefined Template\n\nPredefined mail templates are templates that are programmed into your MTM800 by your Service Provider. You are allowed to perform limited edit operations of the predefined template and to send it, but you will not be able to store the edited template or erase it from the Templates List.\n\n1. Scroll to 3 Predefined and press Ok.\n The first template in the Predefined Template List is displayed (if no predefined template exist, the message No Predefined will be displayed).\n\n2. Scroll through the Templates List using the navigation keys and choose the required template (in the example, a registration message is displayed).\n\nA predefined message can only be sent from the Edit screen.\n\n3. Press Edit. The message is now in the predefined message editor.\n\n4. Enter your message.\n\n- To move the cursor forward – press .\n- To move the cursor backward – press .\n- Press Clear to delete the character to the left of the cursor.\n\nA predefined message address is also defined by your Service Provider during programming and cannot be changed.\n\n5. Press PTT or or the relevant one-touch numeric key to send the message. The display will show one of the following delivery reports:\n\n Message Delivered — to indicate that the message was successfully sent and received.\n\n Message Failed — the message was not received.\n\nAfter sending the message, your MTM800 will return to the predefined template selection screen.\n\nYou will not be able to send another message while your MTM800 is awaiting message acknowledge.\n\n| Messages | Message Description |\n|---------------------------|--------------------------------------------------------------------------------------|\n| ..... Mode List Empty | There are no programmed entries in the scrolling list. Type the entry. |\n| ...-Rcvd | Call received but not answered, or rejected. |\n| Attachment Failed | The terminal could not perform talkgroup attachment. Try another talkgroup. |\n| Authenticate Failure | The terminal could not register on an Authenticated system (for example, the |\n| | Authentication key is incorrect, or Authentication is disabled in the terminal). |\n| Call Cancelled | Faulty channel. Please try later. |\n| Call Ended | Faulty channel. Please try later. Called terminal ended the call. |\n| Call Preempted | Channel being used for priority. |\n| Emgcy Mic Ended | The Hot Microphone timer has automatically expired, or the user has pressed the PTT |\n| | button to cancel the Hot Microphone feature. |\n| Emgcy Mic On | The Hot Microphone feature is active, and the terminal is automatically transmitting |\n| | hands free emergency audio. |\n| Empty Entry | The speed number you dialled does not exist, or the number exists but the group is |\n| | non-selectable. |\n| Faulty Unit Error... | Self-test failed. An operational fault has been detected with your terminal. Record |\n| | the error number. Turn your terminal off and contact service. |\n| Group already exists | The group you are attempting to add already exists in the My Groups range. |\n| Group Mode No Group | Check group selected, and not “No Group” selected. If correct group selected, |\n| | attachment failed. Terminal detached from current talkgroup. Please wait until the |\n| | terminal attaches again to the current talkgroup. |\n| Invalid ID No Entry | The entered number is not valid. |\n| Limited Service | Emergency Calls, Emergency Alarms and mobility operations (e.g.: group attachment) |\n| | are allowed. All other incoming and outgoing call and data services are blocked. |\n| List not Attached | All talkgroups in the scan list are not attached. |\n\n| Messages | Message Description |\n|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|\n| List Partially Attached | The scan list is active, but not all talkgroups are attached to it. |\n| Message Delivered | Mail successfully delivered. |\n| Message Failed | Mail delivery failure. |\n| My Groups is empty | You cannot view/delete groups when the My Groups range is empty. |\n| My Groups is full | You are not allowed to add a group to the My Groups range as it already contains the maximum allowed number of groups. |\n| Network Trouble | Network problems. Please try again later. |\n| No Answer | The called party does not answer. |\n| No Entries | Empty address book list. |\n| No Group | • Displayed when you are out of the normal coverage area of your selected talkgroup. Please select a new talkgroup that is valid for your working location. \n • Indicates a favourite group was removed from the My Groups range. |\n| No GPS Signal | Please check that the GPS antenna is properly connected and sufficient visibility of satellite is available. |\n| No New or Old Messages | The Inbox is empty. |\n| No Service | The terminal is out of coverage. |\n| Not Allowed To Start Call | You are not allowed to dial a number which is not in the Address Book – if set up by your Service Provider. |\n| Not Allowed To Transmit | • Release PTT and try again later. \n • You are not allowed to send a text message or a status message to a number which is not in the Address Book – if set up by your Service Provider. |\n| Only One Entry | There is only one programmed entry in the scrolling list. |\n| Overheating | The terminal will automatically turn off. Keep it turned off for five minutes. |\n| Party Busy | The called terminal is busy. |\n| Party Not Available | The called terminal is out-of-range. Please try again later. The called terminal is turned off. Please try again later. |\n| Please Try Again | The MTM800 could not place the call. |\n| Please Wait Connecting | A message during startup, or network reconnection. |\n\n| Messages | Message Description |\n|---------------------------|--------------------------------------------------------------------------------------|\n| Registration Failure | The terminal could not register within the system. Please try again later. Please |\n| | contact your Service Provider. |\n| Service Denied | Invalid number. Call your Service Provider. |\n| Service Not Available | This service is not available on the current network. |\n| Service Restricted | This service has been restricted by your Service Provider or it has not been |\n| | purchased. |\n| Single Talkgrp | There is only one programmed entry in the scrolling list. |\n| Talkgroup … Added | Group name added to the favourite talkgroup range. |\n| Try Again Later | The requested service is temporarily unavailable. |\n| Unit Disabled | Check with Service Provider. |\n| Unit is OK Warn… | Self-test error. A minor fault has been detected with your terminal. The terminal |\n| | is still fully operative. Should this error recur, note the error code and contact |\n| | service. |\n| Unit Not Attached | The terminal could not attach to the system. The talkgroup may not be defined in the |\n| | system. Please try another group. |\n| Wait For Mic | The Hot Microphone feature is active, but the channel transmit grant has been given |\n| | to another Emergency Call on the same talkgroup. The terminal microphone is not |\n| | active during this time, but the terminal will automatically try to regain talk |\n| | permit after a predetermined time. |\n\n## Tones\n\n| Description | Type | Repeated |\n|------------------------------------------------------------------------------|-----------------------|-------------------|\n| **Idle** | | |\n| • Back to Home display | | |\n| • Back to Rotary volume use when Rotary scroll timer expires | | |\n| • Back to coverage | | |\n| • Back to full service | | |\n| Clear to send | | Once |\n| Bad key press | | Once |\n| • Good key press | | Once |\n| • MTM800 self-test fails at power up | | |\n| • From out-of-service to in-service | | |\n| **In Call** | | |\n| • Call clear warning | | Once |\n| • Call modified | | |\n| Call waiting tone while Phone or Private Call are pending | | Every 6 seconds, until a call is terminated |\n| Data Connected or Data Disconnected. | | Once |\n| Talk Permit sounds upon pressing the PTT. | | Once (Normal Tone) |\n| | | Once (Short Tone) |\n| Talk Permit without gateway sounds upon pressing PTT. The tone indicates the gateway is no longer available. | | Twice |\n| | | Once |\n\n| Description | Type | Repeated |\n|----------------------------------------------------------------------------|-----------------------|-----------------------------------------------|\n| • Talk Prohibit | Low Tone | Until you release the PTT |\n| • System busy | | |\n| • Time-out timer expire | | |\n| • Called MTM800 not available or busy. | | |\n| Call disconnected or failed due to network | Low Tone | Once |\n| Wrong number dialled. | | No tone |\n| DMO (Direct Mode) Entering | High Tone | Once |\n| DMO Exiting | Low Tone Low Tone Low Tone | Once |\n| Local site trunking — Entering/Exiting | High Tone | Once |\n| Phone ring back (sending) | Low Tone Low Tone | Every three seconds, until the called user |\n| | | answers or call is rejected |\n| Phone busy | Low Tone Low Tone | Every 0.5 seconds |\n| Status message sent to the dispatcher or failed. | High Tone High Tone | Twice |\n\n**Incoming Calls**\n\n| Description | Type | Repeated |\n|----------------------------------------------------------------------------|-----------------------|-----------------------------------------------|\n| Status message acknowledged by the dispatcher. | High Tone High Tone High Tone High Tone | Four times |\n| Your MTM800 received a Group Call without gateway. (setup only) | High Tone High Tone Low Tone | Once |\n| High Priority Group Call received | High Tone High Tone High Tone High Tone | Once |\n| Emergency Alarm sent or received | High Tone High Tone | Twice |\n| Emergency Alarm failed | High Tone High Tone High Tone High Tone | Four times |\n| Emergency Call received | High Tone High Tone High Tone | Once |\n| Phone ring, Full-duplex Private Call (reception) | According to the Ring Style sub-menu setting. | Until you answer or the call is rejected |\n\n| Description | Type | Repeated |\n|-------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------|\n| Private Call received | According to the Ring Style sub-menu setting. | Until you answer or the call is rejected |\n| Private Call ringing to the caller | | Until the call is answered |\n| Half-duplex Private Preemptive Priority Call (PPC) ring. | | Every 4 seconds until the call is answered or rejected |\n| Full-duplex Private PPC ring. | | Every 4 seconds until the call is answered or rejected |\n| Limited Service | | Once upon entering limited service |\n| New Mail Received | | Twice |\n| New Group Call | | Once |\n\n**General**\n\n| Description | Type | Repeated |\n|-------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------|\n| Volume setting (earpiece, keypad, speaker) | | Continuous |\n| Volume setting (Ringer) | | While setting the volume |\n| Transmit Inhibit (TXI) | | Once |\n| Rotary knob tone | | Once, when toggling from List to Volume |\n| Low battery alert | | Repeated |\n| DTMF (0-9, #, *) during the call | DTMF | Continuous, until the user releases the key |\n\n**GPS**\n\n| Description | Type | Repeated |\n|-------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------|\n| GPS in coverage | | Once |\n| GPS out of coverage | | Once |\n\n**NOTE** For the missed calls and unread messages, your Service Provider can set up periodic tone.\n\nA\n\naddress book\n adding a number 76\n memory usage 77\n phone address book 75\n private address book 75\n searching alphabetically 76\n searching by location 76\n\nair encryption\n key deletion 81\n\nair encryption key deletion 81\n\nAL (ambience listening) 24, 63\n\nalarm\n horn & light 27\n\nalias 15\n\nalphanumeric key\n entering numbers 15\n entering text 15\n text editing 15\n\nambience listening (AL) 24, 63, 85\n\nannouncement call 30\n\nannouncement talkgroup 30\n\nATG (announcement talkgroup) 30\n\navailable characters 16\n\nB\n\nbacklight\n intensity 27\n key 6\n setting 85\n\nbandwidth 98\n\nBUP (busy user pre-emption) 21\n\nbusy user pre-emption 21\n\nC\n\ncall queuing 56\n\ncleaning your radio 28\n\ncode 80\n\ncovert mode 11, 25\n\none-touch 18\n\nD\n\ndata setup 84\n\ndate\n display settings 86\n one-touch 18\n setting 87, 88\n\nDGNA (dynamic group number assignment) 39\n\ndialled call history 96\n\ndialling\n last dialled number list 96\n\ndirect group call\n making 46\n receiving 49\n\ndirect mode operation (DMO) 12\n\ndisplay\n long numbers 9\n long text message 9\n\nDMO\n emergency 66\n\nDMO (direct mode operation) 12, 42\n\nDMO SCK 83\n\nDTMF\n overdial 60\n\nDTMF (dual-tone multifrequency) 59\n\ndynamic group number assignment 39\n\nE\n\nemergency alarm 61\n sending 63\n\nemergency foot switch 10\n\nemergency group call 61\n\nmaking 64\nmaking in DMO 66\nreceiving 65\nreceiving in DMO 67\n\nencryption 81\nair encryption 81\n\nF\nfavourite talkgroup 29, 33, 94\nfull-duplex call 51\n\nG\ngateway 42, 44, 47\nglobal positioning system (GPS) 68\nGPS (global positioning system) 68\nGPS enable/disable 70\ngroup call\n making 35\n receiving 36\nGW (gateway) 42\n\nH\nhalf-duplex call 51\nhome mode display 18\nHot Mic 65\nhot microphone (Hot Mic) 61, 65\n\nI\nicons\n arrow 9\n data connected 9\n direct mode 7\n DMO gateway 8\n DMO repeater 8\n emergency 8\n external alarm 8\nincoming private call 8\nnew message received 8\nphone call 8\nreceiving/transmitting data 9\nscan 8\nsignal strength DMO 7\nsignal strength TMO 7\nunread message 8\nignition sense 10\nintensity, display intensity 27\nInterMNI call 42\ninternet protocol (IP) 28\ninverted 9\nIP (internet protocol) 28\n\nK\nK (key) 81\nkey\n backlight 6\n emergency 14\n menu 14\n programmable function 17\n soft key 13\nkeypad\n locking 79\n\nL\nlanguage\n display language 84\nlast number redial 52\nlocal area service 26\n entering 26\n exiting 27\nlocal site trunking 26\nlocking the keypad 79\nloudspeaker on/off 25\n\nM\nmenu 14, 72\nmenu option 72\n list 73, 74\nmessage 99\n erase 103\n forward 103\n reply 103\nstatus message 99\ntext 101\ntext message 99\n\nmessages\n status 100\n\nmicrophone\n muting/unmuting 25\nmicrophone mute/unmute 25\nmissed call history 96\nmissed calls 96\nMSPD (multi slot packet data) 28\nmulti slot packet data (MSPD)\n service 28\nmute 25\n\nN\nnetwork 91\nnon-tactical call 61\nnotation 4\nnumber dialling 20\n\nO\noffset\n setting 87\none-touch\n covert mode 18\n date 18\n time 18\none-touch feature 17\nopen group 42\n\nP\nPABX (private automatic branch exchange) 57\npacket data (PD) service 28\nPD (packet data) 28\nphone call\n alphabetic search 59\n answering 60\n direct dial 58\n last number redial 58\n list scroll 59\n making 57\n speed dial 58\nphone mode 57\nphone number 15, 57\n viewing and modifying 90\nphone or private number\n editing 90\nPIN (personal identification number) 79\npowering on/off 10\nPPC (pre-emptive priority call) 22\npre-emptive priority call 22\npriority 94, 95\nprivate automatic branch\n exchange 57\nprivate call 51\n receiving 54\nprivate full-duplex call 51\nprivate half-duplex call 53\nprivate number 15\n alphabetic search 53\n direct entry 52\n entering 52\n list scroll 52\n viewing 90\nPUK (personal unblocking key) 80\n\nR\nrange 29\n selecting 34\nreceived call history 96\nreceiving calls 21\nrepeater 42, 45\nring style 84\n\nS\nscan\n list 93\nscan list 29\nSCK (static cipher key) 82\nshort number dial 52\nshortcut 72\n menu and sub-menu 4\nspeed dial 58\n\nspeed number 31\nstatus message\n sending 100\n\nT\ntactical call 62\ntalk permit tone 89\ntalkgroup 29\n change 30\n speed number 31\ntargeted status 100\ntemplate 99\n predefined 107\n user defined 106\nterminal disable/enable 19\nthroughput 97\ntime\n display settings 86\n one-touch 18\n setting 87, 88\ntime&date 19\nTMO (trunked mode operation) 12\ntone\n setting 88\ntransmit inhibit (TXI) 11, 38\ntrunked mode operation (TMO) 12\nTXI (transmit inhibit) 38\n\nU\nunmute 25\n\nV\nvolume\n adjusting 27\n\n## Making a Phone/PABX Call\n\n1. Press `Mode` to select **Phone or PABX**.\n2. Dial No. or select from address book.\n3. Press `PTT` to place call.\n4. Ringing sounds.\n5. Called user answers.\n6. Talk and listen.\n7. Press `PTT` to terminate call.\n\n## Making a DMO Private Call\n\n1. Press `Mode` to select **Private**.\n2. Press and hold `PTT`.\n3. Release `PTT` to listen.\n4. A tone sounds (if configured).\n5. Called user answers.\n6. Talk.\n7. Press `PTT` to terminate call.\n\n## Making a TMO Private Call\n\n1. Press `Mode` to select **Private**.\n2. Dial No. or select from address book.\n3. Ringing sounds.\n4. Called user answers.\n5. Press `PTT`.\n6. Press and release `PTT`.\n\n## Making a TMO Group Call\n\n1. Press `Mode` to select **Group**.\n2. Select Range / Talkgroup.\n3. Press and hold `PTT`.\n4. Grant tone sounds.\n5. Talk.\n6. Release `PTT` to listen.\n\nMaking a TMO Emergency Group Call\n\nPress and hold \\( \\text{Emergency Alarm} \\). Emergency Alarm is sent automatically.\n\nWhile in Emergency Mode, press and hold PTT to talk. If using Hot Mic feature, wait for the Emergency Mic On message to be displayed, and talk without pressing PTT.\n\nTo exit Emergency Mode press and hold Back.\n\nAnswering a Call\n\nYour MTM800 switches to the mode of the incoming call and starts ringing. To answer the call,\n\n- press \\( \\text{PTT} \\) for a Phone or PABX call\n- press \\( \\text{PTT} \\) and \\( \\text{Menu} \\) 12 for a TMO call\n\nSending a New Message\n\nPress Optns and select Send or enter number\n\nWrite message\n\nPress Optns and select Send or enter number\n\nPTT\n\nSending a User defined Message\n\nSelect 2 Templates Press Ok\n\nScroll through templates and select one\n\nPress Optns and select Send or enter address\n\nPTT\n\nSending a Predefined Message\n\nSelect Scroll through\n\nPTT\n\nHandling Old Messages\n\nPress Ok Scroll messages Select Optns Read / Erase / Erase All\n\nLast Number Redial\n\nIn Private Mode, press PTT to call the last called number.\n\nIn Phone/PABX mode, press \\( \\text{Menu} \\) 12 to display last called number, or a list of last called numbers. If list present, scroll to desired number. Press PTT to call. For more details see the Menu Messages section in the User Guide.\n\nMOTOROLA\n\nwww.motorola.com/tetra"},"books_score":{"kind":"number","value":0.40382131934165955,"string":"0.403821"}}},{"rowIdx":8696,"cells":{"content":{"kind":"string","value":"MODEL MC12PH\nCONCRETE MIXER\n(HONDA GX340UT2QA2/GX340UT2QAP2\nGASOLINE ENGINES)\n\nRevision #4 (08/03/23)\n\nTo find the latest revision of this publication, visit our website at: www.multiquip.com\n\nTHIS MANUAL MUST ACCOMPANY THE EQUIPMENT AT ALL TIMES.\n\nPROPOSITION 65 WARNING\n\nWARNING\nCANCER & REPRODUCTIVE HARM\nwww.P65Warnings.ca.gov\n\nP/N 38707\n\nSILICOSIS WARNING\n\nGrinding/cutting/drilling of masonry, concrete, metal and other materials with silica in their composition may give off dust or mists containing crystalline silica. Silica is a basic component of sand, quartz, brick clay, granite and numerous other minerals and rocks. Repeated and/or substantial inhalation of airborne crystalline silica can cause serious or fatal respiratory diseases, including silicosis. In addition, California and some other authorities have listed respirable crystalline silica as a substance known to cause cancer. When cutting such materials, always follow the respiratory precautions mentioned above.\n\nRESPIRATORY HAZARDS\n\nGrinding/cutting/drilling of masonry, concrete, metal and other materials can generate dust, mists and fumes containing chemicals known to cause serious or fatal injury or illness, such as respiratory disease, cancer, birth defects or other reproductive harm. If you are unfamiliar with the risks associated with the particular process and/or material being cut or the composition of the tool being used, review the material safety data sheet and/or consult your employer, the material manufacturer/supplier, governmental agencies such as OSHA and NIOSH and other sources on hazardous materials. California and some other authorities, for instance, have published lists of substances known to cause cancer, reproductive toxicity, or other harmful effects.\n\nControl dust, mist and fumes at the source where possible. In this regard use good work practices and follow the recommendations of the manufacturers or suppliers, OSHA/NIOSH, and occupational and trade associations. Water should be used for dust suppression when wet cutting is feasible. When the hazards from inhalation of dust, mists and fumes cannot be eliminated, the operator and any bystanders should always wear a respirator approved by NIOSH/MSHA for the materials being used.\n\n# TABLE OF CONTENTS\n\n## MC12PH Concrete Mixer\n\n- Fuel and Chemical Exposure Warnings ........................................ 2\n- Silicosis/Respiratory Warnings .................................................. 3\n- Table of Contents ........................................................................... 4\n- Training Checklist ......................................................................... 5\n- Safety Information ........................................................................ 6–11\n- Specifications/Dimensions ............................................................ 12\n- Engine Specifications ..................................................................... 13\n- General Information ...................................................................... 14\n- Basic Components ......................................................................... 15\n- Engine Components ....................................................................... 16\n- Towing Guidelines ......................................................................... 17\n- Safety Chain Connection ............................................................... 18\n- Inspection ..................................................................................... 19–20\n- Start-Up ......................................................................................... 21\n- Start-Up/Operation ....................................................................... 22\n- Operation ...................................................................................... 23\n- Maintenance (Engine) .................................................................... 24–29\n- Troubleshooting ............................................................................ 30–31\n- Explanation of Code in Remarks Column .................................... 32\n- Suggested Spare Parts ................................................................... 33\n\n## Component Drawings\n\n- Nameplate and Decals Assembly .................................................. 34–35\n- Drum Assembly ............................................................................. 36–37\n- Frame Assembly ............................................................................ 38–39\n- Axle Assembly ............................................................................... 40–41\n- Cabinet Assembly .......................................................................... 42–43\n- Mounting Plate Assembly ............................................................. 44–45\n\n## Honda GX340UT2QA2/QAP2 Gasoline Engines\n\n- Recoil Starter Assembly ............................................................... 46–47\n- Fan Cover Assembly ...................................................................... 48–49\n- Carburetor Assembly ..................................................................... 50–51\n- Air Cleaner Assembly .................................................................... 52–53\n- Muffler Assembly .......................................................................... 54–55\n- Fuel Tank Assembly ....................................................................... 56–57\n- Flywheel Assembly ........................................................................ 58–59\n- Cylinder Head Assembly .............................................................. 60–61\n- Ignition Coil Assembly ................................................................... 62–63\n- Control Assembly .......................................................................... 64–65\n- Cylinder Barrel Assembly ............................................................. 66–67\n- Crankcase Cover Assembly ........................................................... 68–69\n- Crankshaft Assembly ..................................................................... 70–71\n- Piston Assembly ............................................................................ 72–73\n- Camshaft Assembly ....................................................................... 74–75\n- Label Assembly ............................................................................. 76–77\n\n**NOTICE**\n\nSpecifications and part numbers are subject to change without notice.\n\n| No, | Description | OK? | Date |\n|-----|-------------------------------------------------|-----|------|\n| 1 | Read operation manual completely. | | |\n| 2 | Machine layout, location of components, checking of engine oil levels. | | |\n| 3 | Fuel system, refueling procedure. | | |\n| 4 | Operation of controls (machine not running). | | |\n| 5 | Safety controls, safety stop switch operation. | | |\n| 6 | Emergency stop procedures. | | |\n| 7 | Machine transport and storage. | | |\n\nDo not operate or service the equipment before reading the entire manual. Safety precautions should be followed at all times when operating this equipment. Failure to read and understand the safety messages and operating instructions could result in injury to yourself and others.\n\n**SAFETY MESSAGES**\n\nThe four safety messages shown below will inform you about potential hazards that could injure you or others. The safety messages specifically address the level of exposure to the operator and are preceded by one of four words: **DANGER**, **WARNING**, **CAUTION** or **NOTICE**.\n\n**SAFETY SYMBOLS**\n\n- **DANGER**\n Indicates a hazardous situation which, if not avoided, **WILL** result in **DEATH** or **SERIOUS INJURY**.\n\n- **WARNING**\n Indicates a hazardous situation which, if not avoided, **COULD** result in **DEATH** or **SERIOUS INJURY**.\n\n- **CAUTION**\n Indicates a hazardous situation which, if not avoided, **COULD** result in **MINOR** or **MODERATE INJURY**.\n\n- **NOTICE**\n Addresses practices not related to personal injury.\n\nPotential hazards associated with the operation of this equipment will be referenced with hazard symbols which may appear throughout this manual in conjunction with safety messages.\n\n| Symbol | Safety Hazard |\n|--------|--------------------------------|\n| ![Symbol] | Lethal Exhaust Gas Hazards |\n| ![Symbol] | Explosive Fuel Hazards |\n| ![Symbol] | Burn Hazards |\n| ![Symbol] | Rotating Parts Hazards |\n\nGENERAL SAFETY\n\n**CAUTION**\n\n- **NEVER** operate this equipment without proper protective clothing, shatterproof glasses, respiratory protection, hearing protection, steel-toed boots and other protective devices required by the job or city and state regulations.\n\n- Avoid wearing jewelry or loose-fitting clothes that may snag on the controls or moving parts as this can cause serious injury.\n\n- **NEVER** operate this equipment when not feeling well due to fatigue, illness or when on medication.\n\n- **NEVER** operate this equipment under the influence of drugs or alcohol.\n\n- **ALWAYS** clear the work area of any debris, tools, etc. that would constitute a hazard while the equipment is in operation.\n\n- **ALWAYS** check the equipment for loosened threads or bolts before starting.\n\n- **DO NOT** use the equipment for any purpose other than its intended purposes or applications.\n\n**NOTICE**\n\n- This equipment should only be operated by trained and qualified personnel 18 years of age or older.\n\n- Whenever necessary, replace nameplate, operation and safety decals when they become difficult to read.\n\n- Manufacturer does not assume responsibility for any accident due to equipment modifications. Unauthorized equipment modification will void all warranties.\n\n- **NEVER** use accessories or attachments that are not recommended by Multiquip for this equipment. Damage to the equipment and/or injury to the user may result.\n\n- **ALWAYS** know the location of the nearest fire extinguisher.\n\n- **ALWAYS** know the location of the nearest first aid kit.\n\n- **ALWAYS** know the location of the nearest phone or keep a phone on the job site. Also, know the phone numbers of the nearest ambulance, doctor and fire department. This information will be invaluable in the case of an emergency.\n\nMIXER SAFETY\n\n**DANGER**\n\n- **NEVER** operate the equipment in an explosive atmosphere or near combustible materials. An explosion or fire could result causing severe bodily harm or even death.\n\n- **DO NOT** mix flammable or explosive substances.\n\n**WARNING**\n\n- **NEVER** place your hands inside the drum while starting or operating this equipment.\n\n- **NEVER** disconnect any emergency or safety devices. These devices are intended for operator safety. Disconnection of these devices can cause severe injury, bodily harm or even death. Disconnection of any of these devices will void all warranties.\n\n- Before operating the mixer, ensure that the safety grate is in position and correctly fitted.\n\n**CAUTION**\n\n- **NEVER** lubricate components or attempt service on a running machine.\n\n**NOTICE**\n\n- **ALWAYS** keep the machine in proper running condition.\n\n- **ALWAYS** ensure the mixer is on level ground before mixing.\n\n- Fix damage to the machine and replace any broken parts immediately.\n\n- **DO NOT** tip the mixer onto the drum mouth when the drum is rotating.\n\n- Ensure the drum is rotating while filling and emptying the drum.\n\n- **ALWAYS** store equipment properly when it is not being used. Equipment should be stored in a clean, dry location out of the reach of children and unauthorized personnel.\n\n- **ALWAYS** make sure the mixer is clean of dried materials. **DO NOT** allow material to build up inside the drum. Keep the drum, frame and wheels clean. Excess debris can fall off on the highway and/or build up on the frame and wheels, creating an unbalanced condition leading to premature metal fatigue.\n\n---\n\n**ENGINE SAFETY (GASOLINE MODELS ONLY)**\n\n**DANGER**\n\n- Engine fuel exhaust gases contain poisonous carbon monoxide. This gas is colorless and odorless, and can cause death if inhaled.\n\n- The engine of this equipment requires an adequate free flow of cooling air. **NEVER** operate this equipment in any enclosed or narrow area where the free flow of air is restricted. If the air flow is restricted it will cause injury to people and property and serious damage to the equipment or engine.\n\n**WARNING**\n\n- **DO NOT** place hands or fingers inside the engine compartment when the engine is running.\n\n- **NEVER** operate the engine with heat shields or guards removed.\n\n- Keep fingers, hands, hair and clothing away from all moving parts to prevent injury.\n\n- **DO NOT** remove the engine oil drain plug while the engine is hot. Hot oil will gush out of the oil tank and severely scald any persons in the general area of the mixer.\n\n**CAUTION**\n\n- **NEVER** touch the hot exhaust manifold, muffler or cylinder. Allow these parts to cool before servicing the equipment.\n\n- Make certain the operator knows how to and is capable of turning the engine OFF in case of an emergency.\n\n**NOTICE**\n\n- **NEVER** run the engine without an air filter or with a dirty air filter. Severe engine damage may occur. Service the air filter frequently to prevent engine malfunction.\n\n- **NEVER** tamper with the factory settings of the engine or engine governor. Damage to the engine or equipment can result if operating in speed ranges above the maximum allowable.\n\nFUEL SAFETY (GASOLINE MODELS ONLY)\n\n**DANGER**\n- **DO NOT** start the engine near spilled fuel or combustible fluids. Fuel is extremely flammable and its vapors can cause an explosion if ignited.\n- **ALWAYS** refuel in a well-ventilated area, away from sparks and open flames.\n- **ALWAYS** use extreme caution when working with flammable liquids.\n- **DO NOT** fill the fuel tank while the engine is running or hot.\n- **DO NOT** overfill the tank, since spilled fuel can ignite if it comes into contact with hot engine parts or sparks from the ignition system.\n- Store fuel in appropriate containers, in well-ventilated areas and away from sparks and flames.\n- **NEVER** use fuel as a cleaning agent.\n- **DO NOT** smoke around or near the equipment. Fire or explosion could result from fuel vapors or if fuel is spilled on a hot engine.\n\n**GENERATOR SAFETY**\n\nIf using a generator to power the mixer, refer to the applicable generator manual safety information section.\n\n**ELECTRIC MOTOR SAFETY (ELECTRIC MODELS ONLY)**\n\n**NOTICE**\n- Operate the electric motor only at the specified voltage indicated on the nameplate.\n- **DO NOT** spray water onto the electric motor.\n- **ALWAYS** disconnect the AC power plug from the power source before moving the mixer.\n- **ALWAYS** make sure the ON/OFF switch on the electric motor is in the OFF position when not in use and before inserting the mixer’s power plug into an AC receptacle.\n\n**Power Cord/Cable Safety**\n\n**DANGER**\n- **NEVER** let power cords or cables lay in water.\n- **NEVER** use damaged or worn cables or cords when connecting the equipment to a generator. Inspect the insulation for cuts.\n- **NEVER** grab or touch a live power cord or cable with wet hands. The possibility exists of electrical shock, electrocution or death.\n- Make sure power cables are securely connected. Incorrect connections may cause electrical shock and damage to the mixer.\n\n**CAUTION**\n- Ensure that cables and cords will not be tripped over or trapped underneath the mixer.\n\n**NOTICE**\n- **ALWAYS** make certain that the proper power or extension cord has been selected for the job.\n\n**TRANSPORTING SAFETY**\n\n**CAUTION**\n- **NEVER** allow any person or animal to stand underneath the equipment while lifting.\n\n**NOTICE**\n- **ALWAYS** make sure forklift forks are inserted as far as possible into the pockets (if applicable) when lifting the mixer.\n- **ALWAYS** shut down the engine before transporting.\n- **NEVER** lift the equipment while the engine is running.\n- Tighten the fuel tank cap securely and close the fuel cock to prevent fuel from spilling.\n- **DO NOT** lift the machine to unnecessary heights.\n- **ALWAYS** tie down equipment during transport by securing the equipment with rope.\n- **NEVER** tip the engine to extreme angles during lifting as this may cause oil to gravitate into the cylinder head, making the engine difficult to start.\n\nTOWING SAFETY\n\n**CAUTION**\n\n- In addition to meeting Department of Transportation (DOT) safety towing regulations, check your local county or state safety towing regulations before towing the mixer.\n\n- In order to reduce the possibility of an accident while transporting the mixer on public roads, **ALWAYS** make sure the towing vehicle is mechanically sound and in good operating condition.\n\n- **ALWAYS** shut down the engine before transporting and place the fuel valve in the OFF position.\n\n- **ALWAYS** inspect the hitch and coupling for wear. **NEVER** tow a mixer with defective hitches, couplings, chains, etc.\n\n- Check the tire air pressure on both towing vehicle and mixer. *Mixer tires should be inflated to 50 psi cold.* Also check the tire tread wear on the vehicle and mixer.\n\n- **ALWAYS** make sure the mixer is equipped with a safety chain.\n\n- **ALWAYS** properly attach the mixer’s safety chains to the towing vehicle.\n\n- The maximum speed for highway towing is **55 MPH** unless posted otherwise. Recommended off-road towing is not to exceed **15 MPH** or less depending on type of terrain.\n\n- Avoid sudden stops and starts. These can cause skidding or jackknifing. Smooth, gradual starts and stops will improve towing.\n\n- Avoid sharp turns to prevent rolling.\n\n- The mixer should be adjusted to a level position at all times when towing.\n\n- Raise and lock the mixer wheel stand in the UP position when towing.\n\n- Place chock blocks underneath the mixer wheels to prevent rolling while parked.\n\nENVIRONMENTAL SAFETY/DECOMMISSIONING\n\n**NOTICE**\n\nDecommissioning is a controlled process used to safely retire a piece of equipment that is no longer serviceable. If the equipment poses an unacceptable and unrepairable safety risk due to wear or damage or is no longer cost effective to maintain (beyond life-cycle reliability) and is to be decommissioned (demolition and dismantlement), follow the rules below.\n\n- **DO NOT** pour waste or oil directly onto the ground, down a drain or into any water source.\n\n- Contact your country’s Department of Public Works or a recycling agency in your area and arrange for proper disposal of any electrical components, waste or oil associated with this equipment.\n\n- When the life cycle of this equipment is over, remove the battery (if equipped) and bring it to an appropriate facility for lead reclamation. Use safety precautions when handling batteries that contain sulfuric acid.\n\n- When the life cycle of this equipment is over, it is recommended that the mixer frame and all other metal parts be sent to a recycling center.\n\nMetal recycling involves the collection of metal from discarded products and its transformation into raw materials to use in manufacturing a new product.\n\nRecyclers and manufacturers alike promote the process of recycling metal. Using a metal recycling center promotes energy cost savings.\n\nEMISSIONS INFORMATION\n\nNOTICE\n\nThe gasoline engine used in this equipment has been designed to reduce harmful levels of carbon monoxide (CO), hydrocarbons (HC) and nitrogen oxides (NOx) contained in gasoline exhaust emissions.\n\nThis engine has been certified to meet US EPA evaporative emissions requirements in the installed configuration.\n\nAttempting to modify or make adjustments to the engine emission system by unauthorized personnel without proper training could damage the equipment or create an unsafe condition.\n\nAdditionally, modifying the fuel system may adversely affect evaporative emissions, resulting in fines or other penalties.\n\nEmission Control Label\n\nThe emission control label is an integral part of the emission system and is strictly controlled by regulation(s).\n\nThe label must remain with the engine for its entire life.\n\nIf a replacement emission label is needed, please contact your authorized engine distributor.\n\n## SPECIFICATIONS/DIMENSIONS\n\n### Table 1. MC12PH Concrete Mixer Specifications\n\n| Specification | Measurement |\n|--------------------------------|----------------------|\n| Height (A) | 67.5 in. (1,460.5 mm)|\n| Width (B) | 56 in. (1,422.4 mm) |\n| Length (C) | 83 in. (2,108.2 mm) |\n| Maximum Mixing Capacity | 12 cu. ft. (339.8 liters) |\n| Drum Opening | 20 in. (508 mm) |\n| Bag Capacity | 1.5 ~ 2 bags |\n| Weight | 1,000 lbs. (543.59 Kg)|\n\n### Table 2. MC12PH Noise\n\n| Model | MC12PH |\n|----------------|--------|\n| Guaranteed ISO 11201:2010 Based Sound Pressure Level at Operator Station in dB(A) | TBD |\n\n**NOTES:**\n\n1. Sound Pressure and Power Levels are “A” weighted Measures per ISO 226:2003 (ANSI S1.4-1981). They are measured with the operating condition of the machine which generates the most repeatable but highest values of the sound levels. Under normal circumstances, the sound level will vary depending on the condition of the material being worked upon.\n\n### Table 3. Engine Specifications/Dimensions\n\n| Model | GX340UT2QA2/GX340UT2QAP2 |\n|------------------------|--------------------------|\n| **Type** | Air cooled 4-stroke OHV petrol engine, 25° inclined cylinder, horizontal shaft, cast iron sleeve |\n| **Bore X Stroke** | 3.2 in. X 2.5 in. (88 mm x 64 mm) |\n| **Displacement** | 389 cm³ |\n| **Max. Output** | 10.7 H.P. (7.9 kW) @ 3600 RPM |\n| **Continuous Rated Power** | 5.6 kW (7.5 HP)/3,000 rpm \n6.3 kW (8.4 HP)/3,600 rpm |\n| **Max. Net Torque** | 26.4 Nm/2.69 kgfm/2,500 rpm |\n| **Ignition System** | Digital CDI with variable ignition timing |\n| **Fuel Tank Capacity** | 1.61 U.S. Gallons (Approx. 6.1 Liters) |\n| **Fuel** | Unleaded Gasoline |\n| **Lube Oil Capacity** | 1.06 qt. (1.1 liters) |\n| **Oil Type** | 4-Stroke API, SF or SG \nSAE 10W-30 General Use |\n| **Speed Control Method** | Centrifugal Flyweight Type |\n| **Cooling System** | Forced Air |\n| **Starting Method** | Recoil Start |\n| **Spark Plug Type** | BPR6ES NGK |\n| **Spark Plug Gap** | 0.028-0.031 in. (0.70 - 0.80 mm) |\n| **Dimension (L x W x H)** | 16.0 x 18.1 X 17.6 in. \n(406 X 460 X 448 mm) |\n| **Dry Net Weight** | 69.9 lbs (31.7 Kg.) |\n\nAPPLICATION\n\nThis mixer is intended only for the production of concrete. The mixer must be used for its intended purpose and is not suitable for the mixing of flammable or explosive substances. The mixer must not be used in an explosive atmosphere.\n\nPOWER PLANTS\n\nThe Multiquip MC12PH mixer is powered by a 10.7 HP, air-cooled, 4-stroke gasoline engine. Refer to Table 3 to for specific engine.\n\nHARDWARE\n\nCheck all hardware on the mixer before starting. Periodically inspect all hardware. Loose hardware can contribute to early component failure and poor performance. Use Table 4 as general guideline when the torquing of mixer hardware is required. Remember to keep all mixer hardware components tight.\n\n| Hardware Diameter | Torque (ft-lbs) |\n|-------------------|----------------|\n| 5/16-inch x 18 | 14 |\n| 3/8-inch x 16 | 24 |\n| 3/8-inch x 24 | 37 |\n| 1/2-inch x 13 | 39 |\n| 1/2-inch x 13 (Grade 8) | 90 |\n\nENGINE MAINTENANCE\n\nFor basic engine maintenance, refer to the engine maintenance section in this manual. For more detailed engine maintenance, refer to the Honda Engine Owner's manual furnished with the engine.\n\n1. **Plastic Mixing Drum** — The Multiquip MC12PH uses a 12 cu. ft *plastic* mixing drum. This drum is to be used for mixing of concrete. Always clean the drum after each use. **DO NOT** use this mixing drum for the mixing of *volatile or hot liquids*.\n\n2. **Dump Latch** — To rotate the mixing drum, this latch must be in the up position. To lock the drum, place the latch in the down position.\n\n3. **Dump Gear Guard** — **NEVER** operate the mixer with this guard removed. Its purpose is to prevent dirt and debris from entering the dump gear. In addition operator clothing could become entangled in the dump gear, causing severe injury and bodily harm.\n\n4. **Handwheel** — Turn this wheel clockwise or counterclockwise to rotate the mixing drum. Remember the dump latch must be in the *up position* in order for the mixing drum to be rotated.\n\n5. **Safety Chain** — This mixer uses a 3/16-inch thick, 72 inches long zinc-plated safety chain. **ALWAYS** connect the safety chain when towing.\n\n6. **Tow Bar** — This mixer uses various towing bars, please reference the frame assembly drawing and parts list in this manual to determine which tow bar meets your requirements.\n\n7. **Cantilever Suspension** — This mixer uses a cantilever type suspension. Check the mounting hardware for bolt hole elongation and tightness. See maintenance section of this manual for recommended maintenance.\n\n8. **Chock Blocks** — Place these blocks (not included as part of the mixer package) under each mixer wheel to prevent rolling, when mixer is not connected to the towing vehicle.\n\n9. **Tires Ply** — The tire ply (layers) number is rated in letters. This mixer uses 13-inch 2-ply tires. Replace with only recommended type tires.\n\n10. **ON/OFF Switch** — This switch is located on the side of the mixer frame. When activated it will shut down the engine. Pull out when starting the engine.\n\n11. **Cabinet/Latch** — Encloses engine and electric motor. **NEVER** run mixer with cabinet removed. Use latches to secure engine compartment cabinet.\n\n12. **Mixing Blades** — Used for the mixing of concrete. When blades show signs of wear, replace the blades.\n\nINITIAL SERVICING\n\nThe engine (Figure 3) must be checked for proper lubrication and filled with fuel prior to operation. Refer to the manufacturer's engine manual for instructions and details of operation and servicing.\n\n1. **Fuel Filler Cap** – Remove this cap to add unleaded gasoline to the fuel tank. Make sure cap is tightened securely. **DO NOT** over fill.\n\n **DANGER**\n\n Add fuel to the tank only when the engine is stopped and has had an opportunity to cool down. In the event of a fuel spill, **DO NOT** attempt to start the engine until the fuel residue has been completely wiped up and the area surrounding the engine is dry.\n\n2. **Throttle Lever** – Used to adjust engine RPM speed. This lever is connected to the throttle lever cable located on the handle bars. Reference throttle cable installation procedure in this manual.\n\n3. **Recoil Starter (pull rope)** – Manual-starting method. Pull the starter grip until resistance is felt, then pull briskly and smoothly.\n\n4. **Fuel Valve Lever** – **OPEN** to let fuel flow, **CLOSE** to stop the flow of fuel.\n\n5. **Choke Lever** – Used in the starting of a cold engine, or in cold weather conditions. The choke enriches the fuel mixture.\n\n6. **Air Cleaner** – Prevents dirt and other debris from entering the fuel system. Remove wing-nut on top of air filter canister to gain access to filter element.\n\n **NOTICE**\n\n Operating the engine without an air filter, with a damaged air filter, or a filter in need of replacement will allow dirt to enter the engine, causing rapid engine wear.\n\n7. **Spark Plug** – Provides spark to the ignition system. Set spark plug gap according to engine manufacturer’s instructions. Clean spark plug once a week.\n\n8. **Muffler** – Used to reduce noise and emissions. **NEVER** touch when hot!\n\n9. **Fuel Tank** – Fill with unleaded gasoline. Refer to Table 3 for fuel tank capacity. For additional information refer to Honda engine owner’s manual.\n\n10. **Dipstick/Oil Filler Cap** – Remove this cap to determine if the engine oil is low. Add oil through this filler port as recommended in Table 5.\n\n11. **Oil Drain Plug** – Remove this plug to remove oil from the engine’s crankcase.\n\n12. **Engine ON/OFF Switch** – **ON** position permits engine starting, **OFF** position stops engine operation.\n\nTOWING SAFETY PRECAUTIONS\n\n**CAUTION**\n\nCheck with your county or state safety towing regulations department before towing your mixer.\n\nTo reduce the possibility of an accident while transporting the mixer on public roads, always make sure that the mixer towing components and the towing vehicle are in good operating condition and both units are mechanically sound.\n\nThe following list of suggestions should be used when towing the mixer:\n\n- Make sure that the hitch and coupling of the towing vehicle are rated equal to, or greater than the trailer \"gross vehicle weight rating\" (GVWR).\n- **ALWAYS** inspect the hitch and coupling for wear. **NEVER** tow the mixer with defective hitches, couplings, chains etc.\n- **CHECK** the tire air pressure on both the towing vehicle and the trailer. Also check the tire tread wear on both vehicles.\n- **ALWAYS** make sure the mixer is equipped with a \"Safety Chain.\"\n- **ALWAYS** attach trailer's safety chain to the frame of towing vehicle.\n- **ALWAYS** make sure that the towing vehicle's directional, backup, and brake lights are working properly.\n- Remember in most cases the maximum speed unless otherwise posted for highway towing is 45 MPH, however before towing your mixer, check your local state, and county vehicle towing requirements. Recommended off-road towing is not to exceed **10 MPH** or less depending on type of terrain.\n- Place **chocked blocks** underneath wheels to prevent **rolling**, while parked, if disconnected from towing vehicle.\n- Inflate tires to correct pressure, inspect tires for cuts, and excessive wear. See Table 16 (Tire Wear Troubleshooting).\n- When towing of the mixer is required, place the drum in the up position (mouth facing upwards).\n\n**ALWAYS** make sure that the fuel valve lever is in the OFF position (gasoline models only).\n\n- Check wheel mounting lug nuts with a torque wrench. Torque wheel lug nuts as described in the maintenance section of this manual.\n- Check tightness of U-clamp nuts, torque suspension hardware as referenced in the maintenance section of this manual.\n- Avoid sudden stops and starts. This can cause skidding, or jackknifing. Smooth, gradual starts and stops will improve gas milage.\n- Avoid sharp turns to prevent rolling.\n\n**CAUTION**\n\nIf the mixer tow bar is deformed or damaged replace entire tow bar. **NEVER** tow the mixer with a defective tow bar. There exist the possibility of the trailer separating from the towing vehicle.\n\n**TOW BAR TO VEHICLE (COUPLER ONLY)**\n\n1. Check the vehicle hitch ball, and mixer's coupler for signs of wear or damage. Replace any parts that are worn or damaged before towing.\n2. Use only a 2-inch ball diameter (towing vehicle), this will match the mixer's 2-inch coupler. Use of any other ball diameter will create an extremely dangerous condition which can result in separation of the coupler and ball or ball failure.\n3. After tow bar has been connected to mixer (see next page), attach mixer's coupler to the hitch ball on the towing vehicle securely and make sure the lock lever is in the down position (locked).\n\n**MIXER TOW BAR VEHICLE (PINTLE AND LOOP)**\n\n1. Make sure the bumper on the towing vehicle is equipped to handle either a pintle or loop type tow bar configuration.\n2. After tow bar has been connected to mixer (see next page), secure either type of tow bar to the towing vehicle, following state and county towing regulations.\n3. As a minimum, use a 1/2-inch bolt and nylock nut grade 5 when securing either tow bar to the towing vehicle.\n\nCAUTION\n\nNEVER tow the mixer with the safety chain removed. The safety chain is intended to prevent complete separation of the mixer from the towing vehicle in the event of a tow bar failure.\n\nTOW BAR TO MIXER CONNECTION\n\nReference Figure A for the installation of the safety chain.\n\n1. Insert the tow bar through the round opening at the bottom of the mixer stand.\n\n Align the hole on the tow bar with the hole on the mixer frame, and insert 1/2-inch bolt through tow bar and frame. Secure tow bar to frame with 1/2-inch nylock nut. Tighten to 40 ft.-lbs.\n\n2. Route the safety chain through the holes just above the tow bar, located on each side of the mixer stand.\n\n Loop the chain together and place under the tow bar. Secure the loop with the connector link.\n\n3. Extend the safety chain along the length of the tow bar, looping it through the tow bar's connector link. Remove any excess chain slack.\n\n4. Connect the free end of (connector link) the safety chain to the towing vehicle. Remember it is critical that the length of the chain be properly adjusted, to prevent the draw bar and the front of the mixer stand from dropping to the ground (contact) in the event the draw bar becomes disconnected from the towing vehicle.\n\nCAUTION\n\nDO NOT tow or lift the mixer unless the mixing drum is completely empty.\n\nCAUTION\n\nUse a lifting device to lift tow bar onto vehicle coupler. If lifting device is not available, have 2 persons of similar height lift the tow bar. When lifting, do not attempt to lift by bending forward. Bend hips and knees to squat down to your load, keep it close to your body, and straighten your legs to lift.\n\nBEFORE STARTING\n\n1. Read all safety instructions at the beginning of manual.\n2. Clean the unit, removing dirt and dust, particularly the engine cooling air inlet, carburetor and air cleaner.\n3. Check the air filter for dirt and dust. If air filter is dirty, replace air filter with a new one as required.\n4. Check carburetor for external dirt and dust. Clean with dry compressed air.\n5. Check fastening nuts and bolts for tightness.\n\n**CAUTION**\n\nALWAYS wear approved eye and hearing protection while operating the mixer.\n\n**CAUTION**\n\nNEVER place hands or feet inside the engine guard cover while the engine is running. ALWAYS shut the engine down before performing any kind of maintenance service on the mixer.\n\nENGINE OIL CHECK\n\n1. To check the engine oil level, place the unit on secure level ground with the engine stopped.\n2. Remove the filler dipstick from the engine oil filler hole (Figure 4) and wipe it clean.\n\n\n\n**Figure 4. Engine Oil Dipstick (Removal)**\n\n3. Insert and remove the dipstick without screwing it into the filler neck. Check the oil level shown on the dipstick.\n4. If the oil level is low (Figure 5), fill to the edge of the oil filler hole with the recommended oil type (Table 5). Maximum oil capacity is 2.33 pints (1.09 liters).\n\n**NOTICE**\n\nReference engine manufacturer’s manual for specific servicing instructions.\n\n\n\n**Figure 5. Engine Oil Dipstick (Oil Level)**\n\n| Season | Temperature | Oil Type |\n|------------|---------------|----------------|\n| Summer | 25°C or Higher| SAE 10W-30 |\n| Spring/Fall| 25°C ~ 10°C | SAE 10W-30/20 |\n| Winter | 0°C or Lower | SAE 10W-10 |\n\nFUEL CHECK\n\n**DANGER**\n\nMotor fuels are highly flammable and can be dangerous if mishandled. DO NOT smoke while refueling. DO NOT attempt to refuel the mixer if the engine is hot or running.\n\n1. Remove the gasoline cap located on top of fuel tank.\n2. Visually inspect to see if fuel level is low. If fuel is low, replenish with unleaded fuel.\n3. When refueling, be sure to use a strainer for filtration. DO NOT top-off fuel. Wipe up any spilled fuel immediately.\n\nBLADE CHECK\n\nCheck for worn blades.\n\nIf using a plastic drum, replace the blades using the part numbers referenced in the parts section of this manual.\n\nV-BELT CHECK\n\nVisually examine the V-belt (Figure 6) and determine if it is full of tiny cracks, frayed, has pieces of rubber missing, is peeling or otherwise damaged.\n\nAlso, examine the belt and determine if it is *oil soaked* or \"glazed\" (hard shiny appearance on the sides of the belt). Either of these two conditions can cause the belt to run hot, which can weaken it and increase the danger of it breaking.\n\nIf the V-belt exhibits any of the above wear conditions replace the V-belt immediately.\n\n\n\nSTART/STOP SWITCH\n\nThis unit has been equipped with a start/stop switch (Figure 7), which should be tested every time the unit is started.\n\n\n\nThis section is intended to assist the operator with the initial start-up of the unit. It is extremely important that this section be read carefully before attempting to use the mixer in the field. **DO NOT** use your mixer until this section is thoroughly understood.\n\n**WARNING**\n\nFailure to understand the operation of the mixer could result in severe damage to the mixer or personal injury. Reference Figure 2 for the location of any components referenced in this manual.\n\n**CAUTION**\n\n**NEVER** operate the mixer in a confined area or enclosed area structure that does not provide ample free flow of air.\n\nThe following steps outline the procedure for starting the engine.\n\n1. Move the fuel shut-off lever (Figure 8) to the ON position.\n\n2. To start a cold engine, move the choke lever (Figure 9) to the CLOSED position.\n\n3. Move the throttle lever (Figure 10) away from the slow position, about 1/3 of the way toward the fast position.\n\n4. Turn the engine switch (Figure 11) to the ON position.\n\n5. Located at the rear of the mixer frame is the main **start/stop** button (Figure 12). Pull this button outward to start the engine.\n\n6. Pull the starter grip (Figure 13) lightly until you feel resistance, then pull briskly. Return the starter grip gently.\n\n**CAUTION**\n\nNEVER stand in front or behind the mixing drum while it is being placed in the dump position. Stay clear of the mixing drum while it is being positioned.\n\n2. As the drum rotates, use a shovel (Figure 15) to place the cement mix inside the drum, add water as required. Be careful to only place the tip of the shovel inside the drum.\n\n**OPERATION**\n\n1. To position the drum, make sure the mixer is placed on firm level ground, then pull up on the dump latch (Figure 14) and turn the hand wheel until the drum is at the desired position. Once the drum is at the desired position, pull down on the dump latch to lock the drum in position.\n\n3. Placing the shovel all the way inside the drum (Figure 16) will cause the shovel to strike the blades. This condition will make the shovel rotate, and could cause injury to personnel. NEVER place hands inside the mixing drum while it is rotating.\n\nSTOPPING THE MIXER\n\n1. Push the main start/stop switch (Figure 17) inward to stop the engine.\n\n \n\n Figure 17. Start/Stop Button (Stop Position)\n\n2. Place fuel shut-off lever in the OFF position.\n\n3. Clean drum of all debris and foreign matter.\n\nUse Table 6 as a general maintenance guideline when servicing your engine. For more detail engine maintenance information, refer to the engine owner’s manual supplied with your engine.\n\n| DESCRIPTION (3) | OPERATION | BEFORE | FIRST MONTH OR 10 HRS. | EVERY 3 MONTHS OR 25 HRS. | EVERY 6 MONTHS OR 50 HRS. | EVERY YEAR OR 100 HRS. | EVERY 2 YEARS OR 200 HRS. |\n|--------------------------|-----------------|--------|------------------------|---------------------------|---------------------------|------------------------|---------------------------|\n| Engine Oil | Check | X | | | | | |\n| | Change | | X | | | | |\n| Air Cleaner | Check | X | | | | | |\n| | Change | | | X (1) | | | |\n| All Nuts and Bolts | Re-tighten if necessary | X | | | | | |\n| Spark Plugs | Check/Clean | | | | | X | |\n| | Replace | | | | | | X |\n| Cooling Fins | Check | | | | | X | |\n| Spark Arrester | Clean | | | | | | X |\n| Fuel Tank | Clean | | | | | | X |\n| Fuel Filter | Check | | | | | | X |\n| Idle Speed | Check/Adjust | | | | | | X (2) |\n| Valve Clearance | Check/Adjust | | | | | | X (2) |\n| Fuel Lines | Check | | | | | Every 2 years (replace if necessary) (2) |\n\n(1) Service more frequently when used in DUSTY areas.\n\n(2) These items should be serviced by your service dealer, unless you have the proper tools and are mechanically proficient. Refer to the HONDA Shop Manual for service procedures.\n\n(3) For commercial use, log hours of operation to determine proper maintenance intervals.\n\nMAINTENANCE\n\nPerform the scheduled maintenance procedures as defined by Table 6 and below:\n\nDAILY\n\n- Thoroughly remove dirt and oil from the engine and control area. Clean or replace the air cleaner elements as necessary. Check and retighten all fasteners as necessary. Check the gearbox for oil leaks. Repair or replace as needed.\n\nWEEKLY\n\n- Remove the fuel filter cap and clean the inside of the fuel tank.\n- Remove or clean the filter at the bottom of the tank.\n- Remove and clean the spark plug (Figure 18), then adjust the spark gap to 0.024 ~ 0.028 inch (0.6~0.7 mm). This unit has electronic ignition, which requires no adjustments.\n\nENGINE OIL\n\n1. Drain the engine oil when the oil is warm as shown in Figure 19.\n2. Remove the oil drain bolt and sealing washer and allow the oil to drain into a suitable container.\n3. Replace engine oil with recommended type oil as listed in Table 5. For engine oil capacity, see Table 3 (Engine Specifications). DO NOT overfill.\n4. Install drain bolt with sealing washer and tighten securely.\n\nENGINE AIR CLEANER\n\n1. Remove the air cleaner cover and foam filter element as shown in Figure 20.\n2. Tap the paper filter element (Figure 20) several times on a hard surface to remove dirt, or blow compressed air [not exceeding 30 psi (207 kPa, 2.1 kgf/cm²)] through the filter element from the air cleaner case side. NEVER brush off dirt. Brushing will force dirt into the fibers. Replace the paper filter element if it is excessively dirty.\n3. Clean foam element in warm, soapy water or nonflammable solvent. Rinse and dry thoroughly. Dip the element in clean engine oil and completely squeeze out the excess oil from the element before installing.\n\n**DANGER**\n\nDO NOT use gasoline as a cleaning solvent to avoid creating the risk of fire or an explosion.\n\nBALL SOCKET AND CLAMP FACE MAINTENANCE\n\n1. If the towing vehicle is equipped with a ball socket, smear socket periodically with multi-purpose grease. This will keep the ball socket well lubricated.\n\n2. Periodically oil pivot points and clamp face surfaces of coupler with SAE 30 WT. motor oil.\n\n3. When parking or storing your mixer. Keep the coupler off the ground so dirt will not build up in the ball socket.\n\nGREASE FITTINGS (ZERK) MAINTENANCE (MIXER)\n\nThere are grease fittings (Figure 21) that will require lubrication. Lubricate these fittings once a month. Use lithium base grease, grade No.1.\n\nWHEEL BEARINGS\n\n1. After every 3 months of operation, remove the hub dust cap and inspect the wheel bearings (Figure 22). Once a year, or when required, disassemble the wheel hubs remove the old grease and repack the bearings forcing grease between rollers, cone and cage with a good grade of high speed wheel bearing grease (never use grease heavier than 265 A.S.T.M. penetration (\"No. 2.\").\n\n\n\n**Figure 22. Wheel Hub and Bearings**\n\n2. Fill the wheel hub (Figure 22) with grease to the inside diameter of the outer races and also fill the hub grease cap. Reassemble the hub and mount the wheel. Then tighten the adjusting nut, at the same time turn the wheel in both directions, until there is a slight bind to be sure all the bearing surfaces are in contact.\n\nThen back-off the adjusting nut 1/6 to 1/4 turn or to the nearest locking hole or sufficiently to allow the wheel to rotate freely within limits of .001\" to .010\" end play. Lock the nut at this position. Install the cotter pin and dust cap, and tighten all hardware.\n\nMIXER CLEANING\n\n1. For thorough mix and longer drum life, always wash drum out after each use.\n\n2. **NEVER!** pour or spray water over the engine or electric motor.\n\n**Tires/Wheels/Lug Nuts**\n\nTires and wheels are a very important and critical components of the trailer. When specifying or replacing the trailer wheels it is important the wheels, tires, and axle are properly matched.\n\n**WARNING**\n\nDO NOT attempt to repair or modify a wheel. DO NOT install an inter-tube to correct a leak through the rim. If the rim is cracked, the air pressure in the inter-tube may cause pieces of the rim to explode (break-off) with great force and can cause serious eye or bodily injury.\n\n**Tires Wear/Inflation**\n\nTire inflation pressure is the most important factor in tire life. Pressure should be checked cold before operation. DO NOT bleed air from tires when they are hot. Check inflation pressure weekly during use to insure the maximum tire life and tread wear.\n\n**WARNING**\n\nALWAYS wear safety glasses when removing or installing force fitted parts. Failure to comply may result in serious injury.\n\nTable 7 (Tire Wear Troubleshooting) will help pinpoint the cause of tire wear.\n\n| Wear Pattern | Cause | Solution |\n|--------------|------------------------|-----------------------------------------------|\n| Center Wear | Over Inflation | Adjust pressure to particular load per tire |\n| | | manufacturer |\n| Edge Wear | Under Inflation | Adjust pressure to particular load per tire |\n| | | manufacturer |\n| Side Wear | Loss of chamber or | Make sure load does not exceed axle rating. |\n| | | Align wheels |\n| Toe Wear | Incorrect toe-in | Align wheels |\n| Out of balance | | Check bearing adjustment and balance tires. |\n\nMC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23) — PAGE 27\n\nSuspension\n\nThe cantilever suspension springs and associated components (Figure 23) should be visually inspected every 6,000 miles for signs of excessive wear, elongation of bolt holes, and loosening of fasteners. Replace all damaged parts (suspension) immediately. Torque locknut securing U-clamp to spring leaf between 45 and 50 ft.-lbs.\n\n**NOTICE**\n\nNEVER use an pneumatic air gun to tighten wheel lug nuts.\n\n3. After first road use, retorque all lug nuts in sequence. Check all wheel lug nuts periodically.\n\n---\n\n**Lug Nut Torque Requirements**\n\nIt is extremely important to apply and maintain proper wheel mounting torque. Be sure to use only the fasteners matched to the cone angle of the wheel. Proper procedure for attachment of the wheels is as follows:\n\n1. Start all wheel lug nuts by hand.\n2. Torque all lug nuts in sequence. See Figure 24. **DO NOT** torque the wheel lug nuts all the way down. Tighten each lug nut in 3 separate passes as defined by Figure 24.\n\n| Wheel Size | First Pass FT-LBS | Second Pass FT-LBS | Third Pass FT-LBS |\n|------------|-------------------|--------------------|-------------------|\n| 12\" | 20-25 | 35-40 | 50-65 |\n| 13\" | 20-25 | 35-40 | 50-65 |\n| 14\" | 20-25 | 50-60 | 90-120 |\n| 15\" | 20-25 | 50-60 | 90-120 |\n| 16\" | 20-25 | 50-60 | 90-120 |\n\n---\n\n**Figure 23. Suspension Components**\n\n**Figure 24. Lug Nuts Tightening Sequence**\n\nMIXER STORAGE\n\nFor storage of the mixer for over 30 days, the following is recommended:\n\n- Drain the fuel tank completely, or add STA-BIL to the fuel.\n- Run the engine until the fuel is completely consumed.\n- Completely drain used oil from the engine crankcase and fill with fresh clean oil, then follow the procedures described in the engine manual for engine storage.\n- Clean the entire mixer and engine compartment.\n- Place the mixing drum in the down position (mouth facing downward).\n- Cover the mixer and place it in a clean dry area that is protected from harsh elements.\n\n| Symptom | Possible Problem | Solution |\n|------------------------------------------------------------------------|------------------------------------------------------|--------------------------------------------------------------------------|\n| Difficult to start, fuel is available, but no spark at spark plug. | Spark plug bridging? | Check gap, insulation or replace spark plug. |\n| | Carbon deposit on spark plug? | Clean or replace spark plug. |\n| | Short circuit due to deficient spark plug insulation?| Check spark plug insulation, replace if worn. |\n| | Improper spark plug gap? | Set to proper gap. |\n| | Fuel reaching carburetor? | Check fuel line. |\n| | Water in fuel tank? | Flush or replace fuel tank. |\n| | Fuel filter clogged? | Replace fuel filter. |\n| | Stuck carburetor? | Check float mechanism. |\n| | Spark plug is red? | Check transistor ignition unit. |\n| | Spark plug is bluish white? | If insufficient compression, repair or replace engine. If injected air leaking, correct leak. If carburetor jets clogged, clean carburetor. |\n| | No spark present at tip of spark plug? | Check transistor ignition unit is broken, and replace defective unit. Check if voltage cord cracked or broken and replace. Check if spark plug if fouled and replace. |\n| | No oil? | Add oil as required. |\n| | Oil pressure alarm lamp blinks upon starting? | Check automatic shutdown circuit, \"oil sensor\". (if applicable) |\n| Difficult to start, fuel is available, and spark is present at the spark plug. | ON/OFF switch is shorted? | Check switch wiring, replace switch. |\n| | Ignition coil defective? | Replace ignition coil. |\n| | Improper spark gap, points dirty? | Set correct spark gap and clean points. |\n| | Condenser insulation worn or short circuiting? | Replace condenser. |\n| | Spark plug wire broken or short circuiting? | Replace defective spark plug wiring. |\n| Difficult to start, fuel is available, spark is present and compression is normal. | Wrong fuel type? | Flush fuel system, and replace with correct type of fuel. |\n| | Water or dust in fuel system? | Flush fuel system. |\n| | Air cleaner dirty? | Clean or replace air cleaner. |\n| | Choke open? | Close choke. |\n| Difficult to start, fuel is available, spark is present and compression is low. | Suction/exhaust valve stuck or protruded? | Reseat valves. |\n| | Piston ring and/or cylinder worn? | Replace piston rings and/or piston. |\n| | Cylinder head and/or spark plug not tightened properly? | Torque cylinder head bolts and spark plug. |\n| | Head gasket and/or spark plug gasket damaged? | Replace head and spark plug gaskets. |\n| No fuel present at carburetor. | No fuel in fuel tank? | Fill with correct type of fuel. |\n| | Fuel cock does not open properly? | Apply lubricant to loosen fuel cock lever, replace if necessary. |\n| | Fuel filter/lines clogged? | Replace fuel filter. |\n| | Fuel tank cap breather hole clogged? | Clean or replace fuel tank cap. |\n| | Air in fuel line? | Bleed fuel line. |\n\n| Symptom | Possible Problem | Solution |\n|------------------------------------------------------------------------|------------------------------------------------------|--------------------------------------------------------------------------|\n| Weak in power, compression is proper and does not misfire. | Air cleaner dirty? | Clean or replace air cleaner. |\n| | Improper level in carburetor? | Check float adjustment, rebuild carburetor. |\n| | Defective spark plug? | Clean or replace spark plug. |\n| | Improper spark plug? | Set to proper gap. |\n| Weak in power, compression is proper but misfires. | Water in fuel system? | Flush fuel system and replace with correct type of fuel. |\n| | Dirty spark plug? | Clean or replace spark plug. |\n| | Ignition coil defective? | Replace ignition coil. |\n| Engine overheats. | Spark plug heat value incorrect? | Replace with correct type of spark plug. |\n| | Wrong type of fuel? | Replace with correct type of fuel. |\n| | Cooling fins dirty? | Clean cooling fins. |\n| | Intake air restricted? | Clear intake of dirt and debris. Replace air cleaner elements as |\n| | | necessary. |\n| | Oil level too low or too high? | Adjust oil to proper level. |\n| Rotational speed fluctuates. | Governor adjusted incorrectly? | Adjust governor. |\n| | Governor spring defective? | Replace governor spring. |\n| | Fuel flow restricted? | Check entire fuel system for leaks or clogs. |\n| Recoil starter malfunctions. (if applicable) | Recoil mechanism clogged with dust and dirt? | Clean recoil assembly with soap and water. |\n| | Spiral spring loose? | Replace spiral spring. |\n| Starter malfunctions. | Loose, damaged wiring? | Ensure tight, clean connections on battery and starter. |\n| | Battery insufficiently charged? | Recharge or replace battery. |\n| | Starter damaged or internally shorted? | Replace starter. |\n| Burns too much fuel. | Over-accumulation of exhaust products? | Check and clean valves. Check muffler and replace if necessary. |\n| | Wrong spark plug? | Replace spark plug with manufacturer’s suggested type. |\n| Exhaust color is continuously “white”. | Lubricating oil is wrong viscosity? | Replace lubricating oil with correct viscosity. |\n| | Worn rings? | Replace rings. |\n| Exhaust color is continuously “black”. | Air cleaner clogged? | Clean or replace air cleaner. |\n| | Choke valve set to incorrect position? | Adjust choke valve to correct position. |\n| | Carburetor defective, seal on carburetor broken? | Replace carburetor or seal. |\n| | Poor carburetor adjustment, engine runs too rich? | Adjust carburetor. |\n| Will not start, no power with key “ON”. (if applicable) | ON/OFF device not activated ON? | Turn on ON/OFF device. |\n| | Battery disconnected or discharged? | Check cable connections. Charge or replace battery. |\n| | Ignition switch/wiring defective? | Replace ignition switch. Check wiring. |\n\nEXPLANATION OF CODE IN REMARKS COLUMN\n\nThe following section explains the different symbols and remarks used in the Parts section of this manual. Use the help numbers found on the back page of the manual if there are any questions.\n\n**NOTICE**\n\nThe contents and part numbers listed in the parts section are subject to change **without notice**. Multiquip does not guarantee the availability of the parts listed.\n\n### SAMPLE PARTS LIST\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|----------|-----------------|------|----------------------------------------------|\n| 1 | 12345 | BOLT | 1 | INCLUDES ITEMS W/% |\n| 2% | | WASHER, 1/4 IN | | NOT SOLD SEPARATELY |\n| 2% | 12347 | WASHER, 3/8 IN | 1 | MQ-45T ONLY |\n| 3 | 12348 | HOSE | A/R | MAKE LOCALLY |\n| 4 | 12349 | BEARING | 1 | S/N 2345B AND ABOVE |\n\n### NO. Column\n\n**Unique Symbols** — All items with same unique symbol (@, #, +, %, or >) in the number column belong to the same assembly or kit, which is indicated by a note in the “Remarks” column.\n\n**Duplicate Item Numbers** — Duplicate numbers indicate multiple part numbers, which are in effect for the same general item, such as different size saw blade guards in use or a part that has been updated on newer versions of the same machine.\n\n**NOTICE**\n\nWhen ordering a part that has more than one item number listed, check the remarks column for help in determining the proper part to order.\n\n### PART NO. Column\n\n**Numbers Used** — Part numbers can be indicated by a number, a blank entry, or TBD.\n\nTBD (To Be Determined) is generally used to show a part that has not been assigned a formal part number at the time of publication.\n\nA blank entry generally indicates that the item is not sold separately or is not sold by Multiquip. Other entries will be clarified in the “Remarks” Column.\n\n### QTY. Column\n\n**Numbers Used** — Item quantity can be indicated by a number, a blank entry, or A/R.\n\nA/R (As Required) is generally used for hoses or other parts that are sold in bulk and cut to length.\n\nA blank entry generally indicates that the item is not sold separately. Other entries will be clarified in the “Remarks” Column.\n\n### REMARKS Column\n\nSome of the most common notes found in the “Remarks” Column are listed below. Other additional notes needed to describe the item can also be shown.\n\n**Assembly/Kit** — All items on the parts list with the same unique symbol will be included when this item is purchased.\n\nIndicated by:\n\n“INCLUDES ITEMS W/(unique symbol)”\n\n**Serial Number Break** — Used to list an effective serial number range where a particular part is used.\n\nIndicated by:\n\n“S/N XXXXX AND BELOW”\n“S/N XXXX AND ABOVE”\n“S/N XXXX TO S/N XXX”\n\n**Specific Model Number Use** — Indicates that the part is used only with the specific model number or model number variant listed. It can also be used to show a part is NOT used on a specific model or model number variant.\n\nIndicated by:\n\n“XXXXX ONLY”\n“NOT USED ON XXXX”\n\n“Make/Obtain Locally” — Indicates that the part can be purchased at any hardware shop or made out of available items. Examples include battery cables, shims, and certain washers and nuts.\n\n“Not Sold Separately” — Indicates that an item cannot be purchased as a separate item and is either part of an assembly/kit that can be purchased, or is not available for sale through Multiquip.\n\n## SUGGESTED SPARE PARTS\n\n### MC12PH CONCRETE MIXER\n1 to 3 units\n\n| Qty. | P/N | Description |\n|------|-----------|---------------------------|\n| 4 | 521458 | V-BELT |\n| 1 | 29173-001 | STOP SWITCH W/GAS ENGINE |\n| 2 | 491010 | LATCH SET |\n| 1 | 803270 | O-RING |\n| 2 | EM914288 | SEAL, AXLE |\n| 4 | EM903012 | BEARING CLIP |\n| 4 | EM903113 | BEARING CONE |\n| 2 | 3469 | DUST CAP, AXLE |\n\n### GX340UT2QA2/GX340UT2QAP2 ENGINES\n1 to 3 units\n\n| Qty. | P/N | Description |\n|------|----------------------|--------------------------------------------------|\n| 3 | 17210ZE2515 | ELEMENT, AIR CLEANER |\n| 3 | 9807956846 | SPARK PLUG, BPR6ES |\n| 1 | 28462ZV7003 | ROPE, RECOIL STARTER |\n| 1 | 17620Z4H030 | CAP, FUEL TANK, CHROME |\n| 1 | 17672Z4H000 | FILTER, FUEL |\n\n**NOTICE**\n\nPart numbers on this Suggested Spare Parts list may supersede/replace the part numbers shown in the following parts lists.\n\nNAMEPLATE AND DECALS ASSY.\n\nSAFETY INSTRUCTIONS\n\n1. Read owner’s manual before operating.\n2. Keep operator head and extremities clear of moving parts at all times.\n3. Make sure all safety devices are in place and functioning properly.\n4. Make sure engine is turned off and all power sources are disconnected before cleaning the machine.\n5. Keep children and pets away from.\n6. Do not operate machine in an enclosed area or near open flame.\n7. Never leave machine unattended when running.\n8. Always stop engine and allow engine to completely cool before leaving it unattended.\n\nWARNING\n\nTo protect life, read MQ’s user’s manual before operating equipment.\n\nSome safety rules, guards and covers may be removed for easier operation. Reinstall before inspection or maintenance.\n\nOperating guard must not be used.\n\nThis machine is operated by qualified personnel only. Just for mixing as needed.\n\nCAUTION\n\nINSPECT BEFORE TOWING\n- TIGHTNESS OF WHEEL NUTS\n- TIRE PRESSURE\n\n1. Use manufacturer’s recommended torque values when tightening wheel lug nuts.\n2. Use manufacturer’s recommended tire pressure values when inflating tires. DO NOT exceed recommended tire pressure.\n\nCAUTION\n\nDRUM LOCK POSITIONING\nSEE OPERATION MANUAL FOR PROPER DRUM LOCK POSITIONING\n\nLOCK PIN\nREPRESENTS LOCK PIN\nDRUM STOP BLOCK\nREPRESENTS DRUM STOP BLOCK\n\nDANGER\n\nGases are highly flammable.\nDo not use around or near the equipment.\nFire or explosion could result from fuel vapors or fumes in electrical or magnetic field.\n\nCAUTION\n\nINSPECT BEFORE TOWING\n- TIGHTNESS OF WHEEL NUTS\n- TIRE PRESSURE\n\n1. Use manufacturer’s recommended torque values when tightening wheel lug nuts.\n2. Use manufacturer’s recommended tire pressure values when inflating tires. DO NOT exceed recommended tire pressure.\n\nNOTE:\n\nSAME POSITION ON OPPOSITE SIDE OF CABINET.\n\n| NO | PART NO. | PART NAME | QTY. | REMARKS |\n|----|-----------|------------------------------------------------|------|--------------------------------|\n| 1 | 512910 | MQ MULTIQUIP LOGO | 3 | |\n| 2 | 520935 | DECAL, SAFETY INSTRUCTIONS | 1 | |\n| 3 | 521229 | DECAL, WARNING READ MANUAL | 2 | |\n| 4 | 521232 | DECAL, TOWING INSTRUCTIONS | 2 | |\n| 5 | 521231 | DECAL, DRUM LOCK POSITION | 1 | |\n| 6 | 13118 | DECAL, POWDER COATED | 1 | |\n| 7 | | NAMEPLATE | 1 | CONTACT MQ PARTS DEPT. |\n| 8 | 491757 | POP RIVET | 2 | |\n| 9 | 521228 | DECAL, DANGER NO SMOKING | 2 | |\n| 10 | 948630 | DECAL, PUSH TO STOP | 1 | |\n| 11 | 518524 | DECAL, ISO 9001:2000, EXPORT | 1 | |\n\nDRUM ASSY.\n\nPAGE 36 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|------------|------------------------------------------------|------|--------------------------------|\n| 2$ | 802294 | SUPPORT SPIDER | 1 | |\n| 4$ | 802803 | KING PIN | 1 | |\n| 6$ | 803269 | BEARING, BARREL | 2 | |\n| 10$ | 521573 | OIL SEAL | 1 | |\n| 125 | 504447 | WASHER | 1 | |\n| 14$ | 516678C | NUT, KING PIN | 1 | |\n| 16$ | EM924006 | PIN, COTTER | 1 | REPLACES P/N 491690 |\n| 18$ | 803270 | O-RING, BARREL | 1 | |\n| 20$ | 803267 | CAP, BARREL | 1 | |\n| 22$ | 802291 | BARREL, 12 CF PLASTIC | 1 | |\n| 24$ | 803076 | GUARD, BARREL | 4 | |\n| 26$ | 490166 | BOLT, HEX 3/8\" X 3-1/2\", G5 | 4 | |\n| 28$ | 803181 | BLADE, STEEL | 4 | |\n| 30$ | 512193 | WASHER FLAT 3/8\" LARGE | 4 | |\n| 32$ | EM969013 | NUT, HEX 3/8\" NC | 8 | REPLACES P/N 492583 |\n| 34$ | EM963057 | BOLT, 3/8\" | 4 | REPLACES P/N 492313 |\n| 36$ | 3019092 | WASHER, FLAT 3/8\" | 4 | REPLACES P/N 492598 |\n| 38$ | EM969013 | NUT, HEX 3/8\" | 4 | REPLACES P/N 492583 |\n| 40$ | 804161 | GUARD, BARREL CENTER | 1 | |\n| 44$ | 3019092 | WASHER, FLAT 3/8\" | 2 | REPLACES P/N 492598 |\n| 46$ | EM969013 | NUT, HEX 3/8\" | 2 | REPLACES P/N 492583 |\n| 48$ | 802799 | RING GEAR | 1 | |\n| 50$ | 492396 | SCREW, HEX, 1/2\" NC X 2\" G5 | 4 | |\n| 52$ | 6109170 | WASHER, FLAT 1/2\" | 8 | REPLACES P/N 504322 |\n| 54$ | 492584 | NUT, LOCK 1/2\" | 8 | |\n| 56$ | 803503 | SHIM, PLASTIC #14 | 8 | |\n| 58$ | 803504 | SHIM, PLASTIC #16 | 8 | |\n| 60$ | 492397 | SCREW, HEX, 1/2\" NC X 2-1/2\" G5 | 4 | |\n| 62$ | 492388 | SCREW, HEX, 3/8\" NC X 3-1/4\" G5 | 4 | |\n| 65 | 803356 | DRUM BEARING BRACKET | 1 | |\n| 66 | EM963692 | BOLT 1/2\" UNC X 1-1/2\" | 2 | REPLACES P/N 492394 |\n| 67 | 492584 | NUT, LOCK 1/2\" | 2 | |\n| 68 | 802286 | YOKE | 1 | |\n| 69 | 803396 | JACKSHAFT | 1 | |\n| 70 | 803631 | BEARING, JACKSHAFT | 4 | |\n| 71 | EM926036 | RING RETAINING | 1 | REPLACES P/N 490962 |\n| 72 | 803344 | PINION GEAR | 1 | |\n| 73 | 500246 | KEY SQUARE | 1 | |\n| 74 | 492468 | SCREW SET 5/16\" | 2 | |\n| 75 | EM916001 | FITTING GREASE, 1/8\" NPT | 2 | REPLACES P/N 491698 |\n| 76 | 491008 | CAP, GREASE FITTING | 2 | |\n| 77 | 07037-024 | NUT, HEX 1-1/2-12 | 1 | REPLACES P/N 492579 |\n| 78 | 492491 | SCREW SET | 1 | |\n| 79 | 803635 | BEARING SUPP. BRKT/GR. PROTECTOR | 1 | |\n| 80 | EM512618 | BOLT, ALLEN 1/2\" X 2\" | 4 | REPLACES P/N 512618 |\n| 81 | 492589 | NUT, 1/2\" | 4 | |\n\nFRAME ASSY.\n\nA OPTIONAL TOW BARS\n\nCHAIN & LINK KIT\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|------------|----------------------------------|------|----------------------------------------------|\n| 2 | 803346 | FRAME | 1 | |\n| 4 | 490895 | DUMP LATCH | 1 | |\n| 6 | 803350 | DUMP GEAR | 1 | |\n| 8 | 514723 | SHAFT HANDWHEEL | 1 | |\n| 10 | 803640 | DUMP WHEEL | 1 | |\n| 12 | 490961 | RING RETAINING | 1 | |\n| 14 | 514245 | GUARD GEAR | 1 | |\n| 16 | EM916001 | FITTING GREASE | 2 | REPLACES P/N 491698 |\n| 18 | 491008 | FITTING PROTECTOR | 2 | |\n| 20 | 492395 | BOLT, G5 | 1 | |\n| 22 | 492584 | NUT, LOCK 1/2\" | 1 | |\n| 24 | EM963055 | BOLT, 3/8\" | 3 | REPLACES P/N 492373 |\n| 25$ | 01004 | CONNECTOR LINK | 1 | |\n| 26 | 0166 A | WASHER, LOCK 3/8\" | 3 | REPLACES P/N 492624 |\n| 28 | 492278 | BOLT, HEAD ROUND 1/4\" NC 3/8\" G2 | 4 | |\n| 29$ | 516580 | CLEVIS SAFETY HOOK, 1/4\" | 1 | |\n| 30 | 3103160 | WASHER, LOCK 3/16\" | 4 | REPLACES P/N 492621 |\n| 32 | 492410 | BOLT, 5/8\" NC X 2-1/2\" G5 | 2 | |\n| 34 | EM923348 | WASHER, LOCK 5/8\" | 2 | REPLACES P/N 492627 |\n| 35 | HBC-1 | BALL HITCH 2\" | 1 | CONTACT UNIT SALES |\n| 36 | HLC-1 | LOOP HITCH | 1 | CONTACT UNIT SALES |\n| 37 | HPC-1 | PIN HITCH 1\" | 1 | CONTACT UNIT SALES |\n| 38 | 13363KIT | CHAIN AND LINK KIT | 1 | INCLUDES ITEMS W/$ |\n\nAXLE ASSY.\n\nPAGE 40 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|------------|------------------------------------------------|------|--------------------------------|\n| 2 | 803393 | AXLE | 1 | |\n| 4 | 3018 | SPRING, LEAF | 2 | |\n| 6 | EM963692 | BOLT, 1/2\" UNCX1-1/2\" | 4 | REPLACES P/N 492394 |\n| 8 | 492584 | NUT, LOCK 1/2\" | 10 | |\n| 9$ | EM914288 | OIL SEAL | 2 | |\n| 10 | 3028 | U-BOLT | 2 | |\n| 11$ | EM903113 | BEARING CONE | 4 | |\n| 12 | EM941306A | HUB ASSY., 4-BOLT | 2 | INCLUDES ITEMS W/$ |\n| 13$ | EM903012 | BEARING CUP | 4 | |\n| 14 | 511159 | WASHER, FLAT, .087\" THICKNESS | 2 | |\n| 16 | 501299 | WASHER, FLAT, .135\" THICKNESS | 2 | |\n| 18 | 8164 | NUT, CASTLE 1\" DIA. 20 | 2 | REPLACES P/N 502246 |\n| 19 | 8115 | LUG NUTS | 8 | |\n| 20 | EM924008 | PIN, COTTER 1/8\"X1-1/2\" | 2 | REPLACES P/N 491688 |\n| 21 | 3469 | DUST CAP | 2 | |\n| 22 | 516476 | WHEEL/TIRE ASSY. 4-HOLE | 2 | |\n| 24 | 514810 | BASE PLATE, ENGINE | 1 | |\n| 26 | EM963692 | BOLT, 1/2\"UNCX1-1/2\" | 4 | REPLACES P/N 492394 |\n| 28 | 6109170 | WASHER, FLAT 1/2\" | 8 | REPLACES P/N 492600 |\n| 30 | 492584 | NUT, LOCK 1/2\" DIA. NC | 4 | |\n| 32 | 3043 | BOLT, 1/2\" X 6\" G5 | 2 | REPLACES P/N 510721 |\n| 34 | 3076 | SPRING, AXLE | 2 | |\n\nCABINET ASSY.\n\nPAGE 42 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|------------|----------------------------------|------|--------------------------|\n| 10 | 803502 | ENGINE, COVER | 1 | |\n| 20 | EM963610 | CAP, SCREW | 6 | REPLACES P/N 492375 |\n| 30 | 3019092 | WASHER, FLAT 3/8\" | 12 | REPLACES P/N 492598 |\n| 40 | EM969013 | NUT, HEX 3/8\" NC | 6 | REPLACES P/N 492583 |\n| 50 | 491010 | LATCH ASSY., COMPLETE | 2 | |\n| 60 | 512881 | RIVET | 10 | REPLACES P/N 503723 |\n| 70 | EM505186 | CUSHION RUBBER | 4 | REPLACES P/N 505186 |\n| 80 | 510573 | ENGINE, CABLE HARNESS | 1 | |\n| 90 | 29174-001 | BUTTON, STOP | 1 | |\n| 100 | 29173-001 | SWITCH, STOP | 1 | |\n\nMOUNTING PLATE ASSY.\n\nPAGE 44 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|------------|----------------------------------|------|----------------------------------------------|\n| 2 | 520232 | DRIVEN PULLEY | 1 | |\n| 4 | EM502644 | KEY, JACKSHAFT | 1 | |\n| 6 | 492468 | SCREW SET 5/16\" | 2 | REPLACES P/N 492476 |\n| 8 | 519940 | PULLEY | 1 | |\n| 10 | 492468 | SCREW SET 5/16\" | 1 | |\n| 12 | 521458 | V-BELT BX58 | 2 | |\n| 14 | 492378 | HHCS, G5 | 4 | |\n| 16 | 3019092 | WASHER FLAT 3/8\" | 8 | REPLACES P/N 492598 |\n| 18 | 0166 A | WASHER LOCK 3/8\" DIA | 4 | REPLACES P/N 492624 |\n| 20 | 1456 | NUT HEX 3/8\" | 4 | REPLACES P/N 492554 |\n| 22 | 1388 | ENG., HONDA 11HP, GX340UT2QA2/QAP2 | 1 | |\n\nRECOIL STARTER ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|----------------|-----------------------------------------------|------|-------------------------------------------------------------------------|\n| 1 | 28400Z5T305ZB | STARTER ASSY., RECOIL, BLK | 1 | INCLUDES ITEMS W/# |\n| | | | | REPLACES P/N 28400Z5T003ZB |\n| 2# | 28410ZE3W01ZB | CASE COMP., RECOIL STARTER, NH1, BLK | 1 | |\n| 3# | 28421ZE3W01 | PULLEY, RECOIL STARTER | 1 | |\n| 4# | 28422ZE2W01 | RATCHET, STARTER | 2 | |\n| 5# | 28441ZE2W01 | SPRING, FRICTION | 1 | |\n| 6# | 28442ZE2W01 | SPRING, STARTER RETURN | 1 | |\n| 7# | 28443ZE2W01 | SPRING, RATCHET | 2 | |\n| 8# | 28444ZE2W01 | RETAINER, SPRING | 1 | |\n| 10# | 28462ZV7003 | ROPE, RECOIL STARTER | 1 | REPLACES P/N 28462ZE3W01 |\n| 11# | 90004ZE2W01 | SCREW, CENTER | 1 | |\n| 12 | 90008ZE2003 | BOLT, FLANGE, 6X10 | 3 | |\n| 13# | 28461Z5T305 | GRIP, STARTER | 1 | |\n| 14# | 28463Z5T003 | GRIP, REINFORCEMENT | 1 | |\n\nFAN COVER ASSY.\n\n1 2 3 6 6 10 11\n\nPAGE 48 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|----------------|-----------------------------------------------|------|---------|\n| 1 | 16731ZE2003 | CLIP, TUBE | 1 | |\n| 2 | 19610Z5T000ZB | COVER COMP., FAN, NH1, BLACK | 1 | |\n| 3 | 19631Z5T000 | SHROUD | 1 | |\n| 6 | 90013883000 | BOLT, FLANGE, 6X12 | 6 | |\n| 10 | 35120Z5T003 | SWITCH ASSY., ENGINE STOP | 1 | |\n| 11 | 90004Z5T000 | SCREW, TAPPING, 3X6 | 2 | |\n\nCARBURETOR ASSY.\n\nNOTICE\n\nGasket Set, item 1 included with items 6, 7, 13, 22, 27 and 36.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|-----------------------------------------------|------|----------------------------------------------|\n| 1# | 16010ZE2812 | GASKET SET | 1 | |\n| 2# | 16011ZA0931 | VALVE SET, FLOAT | 1 | |\n| 3# | 16013ZA0931 | FLOAT SET | 1 | |\n| 4# | 16015ZT901 | CHAMBER SET, FLOAT | 1 | |\n| 5# | 16016ZH7W01 | SCREW SET, PILOT | 1 | |\n| 6# | 16024ZT901 | SCREW SET, DRAIN | 1 | |\n| 7# | 16028ZT901 | SCREW SET | 1 | |\n| 8# | 16044ZE3811 | CHOKE SET | 1 | |\n| 9 | 16100Z8T911 | CARBURETOR ASSY. (BE80M A) | 1 | INCLUDES ITEMS WITH # |\n| 10# | 16124ZE0005 | SCREW, THROTTLE STOP | 1 | |\n| 11# | 16166Z8T911 | NOZZLE, MAIN | 1 | |\n| 12# | 16172ZE3W10 | COLLAR, SETTING | 1 | |\n| 13 | 16955Z83000 | PACKING, FUEL STRAINER CUP | 1 | REPLACES P/N 16173001004 |\n| 14 | 16211Z8T000 | INSULATOR, CARBURETOR | 1 | |\n| 15 | 16220ZA0702 | SPACER COMP., CARBURETOR | 1 | |\n| 16 | 16221Z8T000 | PACKING, CARBURETOR | 1 | |\n| 17 | 16212Z5T000 | PACKING, CARBURETOR INSULATOR | 2 | |\n| 18 | 16610ZE1000 | LEVER COMP., CHOKE (STD.) | 1 | INCLUDES ITEMS W/$ |\n| 19# | 16953ZE1812 | LEVER, COCK | 1 | |\n| 20# | 16954ZE1812 | PLATE, LEVER SETTING | 1 | |\n| 21# | 16956ZE1811 | SPRING, COCK LEVER | 1 | |\n| 22# | 16957ZE1812 | PACKING, FUEL COCK | 1 | |\n| 23# | 16967ZE0811 | CUP, FUEL STRAINER | 1 | |\n| 24# | 93500030060H | SCREW, PAN, 3X6 | 2 | REPLACES P/N 93500030061H |\n| 25$ | 94305Z0122 | PIN, SPRING, 2X12 | 1 | |\n| 26# | 99101ZH80900 | JET, MAIN, #90 | 1 | |\n| 26# | 99101ZH80950 | JET, MAIN, #95 | 1 | |\n| 26# | 99101ZH80980 | JET, MAIN, #98 | 1 | |\n| 27# | 99204ZE00380 | JET SET, PILOT, #38 | 1 | |\n| 36# | 16141ZOS003 | WASHER, FLAT | 1 | GX340UT2QAP2 |\n| 37# | 16959ZT901 | FILTER, CUP | 1 | |\n\nAIR CLEANER ASSY.\n\n1. Filter Element\n2. Base\n3. Cover\n4. Cap\n5. Gasket\n6. Bolt\n7. Washer\n8. Housing\n9. Gasket\n10. Nut\n11. Cap\n12. Washer\n13. Bolt\n14. Washer\n\nPAGE 52 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|----------------------------------|------|----------------------------------------------|\n| 1 | 17210ZE2515 | ELEMENT, AIR CLEANER | 1 | INCLUDES ITEMS W/# |\n| 2# | 17218ZE3505 | FILTER, OUTER | 1 | REPLACES P/N 17218ZE3000 |\n| 3 | 17231ZT000 | COVER, AIR CLEANER CASE | 1 | |\n| 4# | 17232891000 | GROMMET, AIR CLEANER | 1 | |\n| 5 | 17235ZT000 | NOSE, SILENCER | 1 | |\n| 6% | 17238ZE2310 | COLLAR, AIR CLEANER | 2 | |\n| 7% | 17239ZE1000 | COLLAR B, AIR CLEANER | 1 | |\n| 8 | 17410ZT000 | ELBOW COMP., AIR CLEANER | 1 | INCLUDES ITEMS W/% |\n| 9 | 17417ZT000 | PACKING, AIR CLEANER CASE | 1 | |\n| 10 | 90009Z1C000 | BOLT-WASHER, 6X22 | 1 | |\n| 11 | 90202ZZE000 | NUT, AIR CLEANER COVER | 1 | |\n| 12 | 90325044000 | NUT, TOOL BOX SETTING | 1 | |\n| 13 | 9405006000 | NUT, FLANGE, 6MM | 2 | |\n\nMUFFLER ASSY.\n\nPAGE 54 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|----------------------------------|------|---------|\n| 1 | 18310Z5T000 | MUFFLER COMP. | 1 | |\n| 2 | 18320Z5T000 | PROTECTOR COMP., MUFFLER | 1 | |\n| 3 | 18205Z5T000 | PROTECTOR, EX. PIPE | 1 | |\n| 5 | 18331ZE3811 | CAP, MUFFLER | 1 | |\n| 6 | 18331Z5T000 | PIPE, EX. | 1 | |\n| 7 | 18333ZF6W01 | GASKET, EX. PIPE | 1 | |\n| 9 | 18350Z5T800 | ARRESTER COMP., SPARK | 1 | |\n| 10 | 18381ZE2W10 | GASKET, MUFFLER (ARRESTER) | 1 | |\n| 12 | 90006ZE2000 | SCREW, TAPPING, 6X10 | 1 | |\n| 13 | 90013883000 | BOLT, FLANGE, 6X12 | 1 | |\n| 14 | 90050ZE1000 | SCREW, TAPPING, 5X8 | 8 | |\n| 15 | 90055ZE1000 | SCREW, TAPPING, 4X6 | 3 | |\n| 16 | 9405008000 | NUT, FLANGE, 8MM | 5 | |\n\nFUEL TANK ASSY.\n\n1. Hose\n2. Nut\n3. Washer\n4. Bolt\n5. Gasket\n6. Cap\n7. O-ring\n8. Washer\n9. Hose\n10. Bolt\n11. Washer\n12. Gasket\n13. Cap\n14. Washer\n15. Bolt\n16. Washer\n17. Gasket\n18. Cap\n19. Washer\n20. Bolt\n21. Cap\n22. Gasket\n23. Cap\n24. Washer\n25. Bolt\n26. Washer\n27. Cap\n\nPAGE 56 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|----------------|-----------------------------------------------|------|----------------------------------------------|\n| 1 | 16854ZH8000 | RUBBER, SUPPORTER (107 MM) | 1 | |\n| 2 | 16955ZE1010 | JOINT, FUEL TANK | 1 | |\n| 5 # | 17631Z0T801 | PACKING, FUEL FILL. CAP | 1 | |\n| 7 | 91353671003 | O-RING, 14MM | 1 | REPLACES P/N 91353671004 |\n| 8 | 9405008000 | NUT, FLANGE, 8MM | 2 | |\n| 9 | 91424Z5T003 | TUBE, FUEL, 4.5X235 | 1 | |\n| 11 | 957010802500 | BOLT, FLANGE, 8X25 | 2 | |\n| 12 | 950024080008 | CLAMP, TUBE | 2 | |\n| 21 | 17620Z4H030 | CAP COMP., FUEL FILL. (CHROME PLT.) | 1 | INCLUDES ITEM W/# |\n| 22 | 17672Z4H000 | FILTER, FUEL | 1 | |\n| 27 | 17510Z5T000ZA | TANK COMP., FUEL, WHITE | 1 | |\n\nFLYWHEEL ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|-----------------------------------------------|------|--------------------------|\n| 1 | 19511ZE3000 | FAN, COOLING | 1 | |\n| 2 | 28450ZE3W11 | PULLEY COMP., STARTER | 1 | |\n| 4 | 31110Z5T000 | FLYWHEEL COMP. | 1 | |\n| 7 | 90201ZE3790 | NUT, SPECIAL, 16MM | 1 | |\n| 8 | 90741ZE2000 | KEY, SPECIAL WOODRUFF, 25X18 | 1 | |\n\nCYLINDER HEAD ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|----------------|-----------------------------------------------|------|--------------------------------|\n| 1 | 12210Z5T406 | HEAD COMP., CYLINDER | 1 | INCLUDES ITEMS W/# |\n| 2# | 12204ZE2306 | GUIDE, IN. VALVE (O.S.) | 1 | |\n| 3# | 12205ZE2305 | GUIDE, EX. VALVE (O.S.) | 1 | |\n| 4# | 12216ZE2300 | CLIP, VALVE GUIDE | 1 | |\n| 5 | 12251Z5T003 | GASKET, CYLINDER HEAD | 1 | |\n| 6 | 12310ZE2020 | COVER COMP., HEAD | 1 | |\n| 7 | 12391ZE2020 | PACKING, HEAD COVER | 1 | |\n| 8 | 90014Z5T000 | BOLT, HEAD COVER | 1 | |\n| 9 | 90042ZE2000 | BOLT, STUD, 8X123 | 2 | |\n| 10 | 90441ZE2010 | WASHER COMP., HEAD COVER | 1 | |\n| 11 | 92900080320E | BOLT, STUD, 8X32 | 2 | |\n| 12 | 9430112200 | DOWEL PIN, 12X20 | 2 | |\n| 14 | 957011008000 | BOLT, FLANGE, 10X80 | 4 | |\n| 15 | 9807956846 | PLUG, SPARK (BPR5ES) | 1 | REPLACES P/N 9807956876 |\n| 15 | 9807955855 | PLUG, SPARK (W16EPR-U) | 1 | |\n| 17 | 12357Z5T020 | TUBE, BREather | 1 | |\n\nIGNITION COIL ASSY.\n\n18 4 10 10\n\nPAGE 62 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|----------------------------------|------|---------|\n| 2 | 30700Z1C811 | CAP ASSY., NOISE SUPPRESSOR | 1 | |\n| 4 | 31512ZE2000 | GROMMET, CORD | 1 | |\n| 10 | 90015883000 | BOLT, FLANGE, 6X28 | 2 | |\n| 12 | 90684ZA0601 | CLIP, HARNESS | 1 | |\n| 18 | 30500Z5T003 | COIL ASSY., IGNITION | 1 | |\n\nCONTROL ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|-----------------------------------------------|------|----------------------------------------------|\n| 1 | 16551ZE3000 | ARM, GOVERNOR | 1 | |\n| 2 | 16555ZE3000 | ROD, GOVERNOR | 1 | |\n| 3 | 16561ZE3000 | SPRING, GOVERNOR (L=145.0MM) | 1 | |\n| 4 | 16562ZE3000 | SPRING, THROTTLE RETURN | 1 | |\n| 6 | 16500Z5T810 | CONTROL ASSY. (REMOTE) | 1 | INCLUDES ITEMS W/# |\n| 8# | 16571ZE2W00 | LEVER, CONTROL | 1 | |\n| 9# | 16574ZE1000 | SPRING, LEVER | 1 | |\n| 10# | 16575ZE2W00 | WASHER, CONTROL LEVER | 1 | |\n| 11# | 16576891000 | HOLDER, CABLE | 1 | |\n| 12# | 16578ZE1000 | SPACER, CONTROL LEVER | 1 | |\n| 13# | 16580Z5T000 | BASE COMP., CONTROL | 1 | |\n| 14# | 16584883300 | SPRING, CONTROL ADJUSTING | 1 | |\n| 15# | 16592883310 | SPRING, CABLE RETURN | 1 | |\n| 17 | 90013883000 | BOLT, FLANGE, 6X12 | 2 | |\n| 18 | 90015Z5T000 | BOLT, GOVERNOR ARM | 1 | |\n| 20# | 90114SA0000 | NUT, SELFLOCK, 6MM | 1 | |\n| 21# | 0202005T125 | SCREW, PAN, 5X16 | 1 | REPLACES P/N 93500050160A |\n| 22# | 93500050280A | SCREW, PAN, 5X32 | 1 | |\n| 24 | 9405006000 | NUT, FLANGE, 6MM | 1 | |\n\nCYLINDER BARREL ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|----------------|-----------------------------------------------|------|----------------------------------------------|\n| 1 | 12000Z5T407 | BARREL ASSY., CYLINDER | 1 | INCLUDES ITEMS W/# |\n| 3 | 16541ZE3010 | SHAFT, GOVERNOR ARM | 1 | |\n| 6 | 90131896650 | BOLT, DRAIN PLUG, 12X15 | 2 | REPLACES P/N 90131883000 |\n| 7 | 90446KE1000 | WASHER, 8.2X17X0.8 | 1 | |\n| 8# | 91201Z1C003 | OIL SEAL, 35X52X8 | 1 | |\n| 9 | 91353671003 | ORING, 14MM | 1 | REPLACES P/N 91353671004 |\n| 10 | 9405010000 | NUT, FLANGE, 10MM | 1 | |\n| 11 | 031112230 | WASHER, DRAIN PLUG, 12MM | 2 | REPLACES P/N 9410912000 |\n| 12 | 9425110000 | PIN, LOCK, 10MM | 1 | |\n| 13 | 957010601200 | BOLT, FLANGE, 6X12 | 2 | |\n| 14# | 96100-6202000 | BEARING, RADIAL BALL, 6202 | 1 | |\n| 16 | 35480ZF6003 | SWITCH ASSY., OIL LEVEL | 1 | |\n\nCRANKCASE COVER ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|----------------|-----------------------------------------------|------|--------------------------------|\n| 1 | 11381Z5T000 | PACKING, CASE COVER | 1 | |\n| 2 | 11300Z1C600 | COVER ASSY., CRANKCASE | 1 | INCLUDES ITEMS W/# |\n| 3 | 15600Z0T820 | CAP ASSY., OIL FILLER | 1 | INCLUDES ITEMS W/% |\n| 4 | 15600Z1C000 | CAP ASSY., OIL FILLER | 1 | INCLUDES ITEMS W/$ |\n| 5%$ | 15625Z0T800 | PACKING, OIL FILLER CAP | 2 | |\n| 6# | 16510ZE3000 | GOVERNOR ASSY. | 1 | INCLUDES ITEMS W/@ |\n| 7#@ | 16511ZE8000 | WEIGHT, GOVERNOR | 2 | |\n| 8#@ | 16512ZE3000 | HOLDER, GOVERNOR WEIGHT | 1 | |\n| 9#@ | 16513ZE2000 | PIN, GOVERNOR WEIGHT | 2 | |\n| 10# | 16531ZOA000 | SLIDER, GOVERNOR | 1 | |\n| 11# | 90602ZE1000 | CLIP, GOVERNOR HOLDER | 1 | |\n| 12 | 90701HC4000 | DOWEL PIN, 8X12 | 2 | |\n| 13# | 91201Z1C003 | OIL SEAL, 35X52X8 | 1 | |\n| 14# | 58176 | WASHER, FLAT 6MM | 1 | REPLACES P/N 9410106800 |\n| 15 | 957010804000 | BOLT, FLANGE, 8X40 | 7 | |\n| 16# | 961006202000 | BEARING, RADIAL BALL, 6202 | 1 | |\n| 17# | 961006207000 | BEARING, RADIAL BALL, 6206 | 1 | |\n\nCRANKSHAFT ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|----------------------------|------|-----------------------|\n| 2 | 13310ZF6W12 | CRANKSHAFT COMP. | 1 | INCLUDES ITEM W/# |\n| 6 | 13351ZE3010 | WEIGHT, BALANCER | 1 | |\n| 7 | 90745ZE2600 | KEY, 6.3X6.3X43 | 1 | |\n| 8# | 91001ZF6013 | BEARING, RADIAL BALL | 1 | |\n\nPISTON ASSY.\n\n1 6 2 3 4 5 5\n\nPAGE 72 — MC12PH CONCRETE MIXER • OPERATION AND PARTS MANUAL — REV. #4 (08/03/23)\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|-----------------------------------------------|------|----------------------------------------------|\n| 1 | 13010Z5K004 | RING SET, PISTON (STD.) | 1 | |\n| 1 | 13011Z5K004 | RING SET, PISTON (0.25) | 1 | |\n| 1 | 13012Z5K004 | RING SET, PISTON (0.50) | 1 | |\n| 1 | 13013Z5K004 | RING SET, PISTON (0.75) | 1 | |\n| 2 | 13101Z5T800 | PISTON (STD.) | 1 | |\n| 2 | 13102Z5T800 | PISTON (0.25) | 1 | |\n| 2 | 13103Z5T800 | PISTON (0.50) | 1 | |\n| 2 | 13104Z5T800 | PISTON (0.75) | 1 | |\n| 3 | 13111Z5T000 | PIN, PISTON | 1 | |\n| 4 | 13200Z1C000 | ROD ASSY., CONNECTING (STD.) | 1 | INCLUDES ITEMS W/# |\n| 4 | 13200Z1C305 | ROD ASSY., CONNECTING (0.25 UNDER SIZE) | 1 | INCLUDES ITEMS W/# |\n| 5# | 90001ZE8000 | BOLT, CONNECTING ROD | 2 | |\n| 6 | 90601ZE3000 | CLIP, PISTON PIN, 18MM | 2 | |\n\nCAMSHAFT ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|----------------|----------------------------------|------|--------------------------|\n| 1 | 12209ZE8003 | SEAL, VALVE STEM | 1 | |\n| 2 | 14100Z5K810 | CAMSHAFT ASSY | 1 | INCLUDES ITEMS W/# |\n| 3 | 14410Z1C000 | ROD, PUSH | 2 | |\n| 4 | 14431ZE2010 | ARM, VALVE ROCKER | 2 | |\n| 5 | 14441ZE2000 | LIFTER, VALVE | 2 | |\n| 6 | 14451ZE1013 | PIVOT, ROCKER ARM | 2 | |\n| 7# | 14568ZE1000 | SPRING, WEIGHT RETURN | 1 | |\n| 8 | 14711Z5T000 | VALVE, IN. | 1 | |\n| 9 | 14721Z5T000 | VALVE, EX. | 1 | |\n| 10 | 14751Z1C000 | SPRING, VALVE | 2 | |\n| 11 | 14771Z8S000 | RETAINER, IN. VALVE SPRING | 1 | |\n| 12 | 14771Z8S000 | RETAINER, IN. VALVE SPRING | 1 | |\n| 13 | 14775ZE2010 | SEAT, VALVE SPRING | 1 | |\n| 15 | 14791Z1D000 | GUIDE, PUSH ROD | 1 | |\n| 16 | 90012ZE0010 | BOLT, PIVOT, 8MM | 2 | |\n| 17 | 90206ZE1000 | NUT, PIVOT ADJUSTING | 2 | |\n| 19# | 14100Z5K910 | CAMSHAFT COMP. | 1 | |\n\nLABEL ASSY.\n\n| NO. | PART NO. | PART NAME | QTY. | REMARKS |\n|-----|--------------|----------------------------|------|---------|\n| 1 | 87521Z8T000 | EMBLEM (GX340) | 1 | |\n| 2 | 87532ZH7000 | MARK, THROTTLE INDICATION | 1 | |\n| 3 | 87528Z5T000 | MARK, CHOKE | 1 | |\n| 4 | 87519Z4H000 | MARK, OPERATOR CAUTION | 1 | |\n| 5 | 87539Z0J000 | MARK, EX, CAUTION | 1 | |\n| 6 | 87516Z4H010 | MARK, OPERATOR CAUTION | 1 | |\n| 7 | 87539Z0J800 | MARK, EX. CAUTION | 1 | |\n\nOPERATION AND PARTS MANUAL\n\nHERE’S HOW TO GET HELP\nPLEASE HAVE THE MODEL AND SERIAL NUMBER ON-HAND WHEN CALLING\n\nUNITED STATES\nMultiquip Inc.\n(310) 537-3700\n6141 Katella Avenue Suite 200\nCypress, CA 90630\nE-MAIL: firstname.lastname@example.org\nWEBSITE: www.multiquip.com\n\nCANADA\nMultiquip\n(450) 625-2244\n4110 Industriel Boul.\nLaval, Quebec, Canada H7L 6V3\nE-MAIL: email@example.com\n\nUNITED KINGDOM\nMultiquip (UK) Limited Head Office\n0161 339 2223\nUnit 2, Northpoint Industrial Estate, Globe Lane,\nDukinfield, Cheshire SK16 4UJ\nE-MAIL: firstname.lastname@example.org\n\n© COPYRIGHT 2023, MULTQUIP INC.\n\nMultiquip Inc., the MQ logo are registered trademarks of Multiquip Inc. and may not be used, reproduced, or altered without written permission. All other trademarks are the property of their respective owners and used with permission.\n\nThis manual MUST accompany the equipment at all times. This manual is considered a permanent part of the equipment and should remain with the unit if resold.\n\nThe information and specifications included in this publication were in effect at the time of approval for printing. Illustrations, descriptions, references and technical data contained in this manual are for guidance only and may not be considered as binding. Multiquip Inc. reserves the right to discontinue or change specifications, design or the information published in this publication at any time without notice and without incurring any obligations."},"books_score":{"kind":"number","value":0.676671028137207,"string":"0.676671"}}},{"rowIdx":8697,"cells":{"content":{"kind":"string","value":"Sub-national electricity and gas consumption statistics\n\nRegion, Local Authority, middle and lower layer super output area\n\n22 December 2015\n\nStatistician Responsible: Greg Haigh\n\nAny enquiries regarding this publication should be sent to us at:\nfirstname.lastname@example.org.\n\n© Crown copyright 2015\nURN 15D/549\n\nYou may re-use this information (not including logos) free of charge in any format or medium, under the terms of the Open Government Licence.\n\nTo view this licence, visit www.nationalarchives.gov.uk/doc/open-government-licence/\nor write to the Information Policy Team, The National Archives, Kew, London TW9 4DU,\nor email: email@example.com.\n\n# Contents\n\nExecutive summary ........................................................................................................ 4\n\n1. Introduction .................................................................................................................. 5\n 1.1 Background ............................................................................................................. 5\n 1.2 Users ....................................................................................................................... 5\n\n2. Electricity .................................................................................................................... 6\n 2.1 Total electricity consumption ............................................................................... 6\n 2.2 Domestic electricity consumption ......................................................................... 10\n 2.3 Non-domestic electricity consumption ................................................................... 15\n\n3. Gas .............................................................................................................................. 20\n 3.1 Total gas consumption ........................................................................................... 20\n 3.2 Domestic gas consumption .................................................................................... 23\n 3.3 Non-domestic gas consumption ............................................................................. 27\n 3.4 Number of households not connected to the gas grid ......................................... 31\n\n4. Super output area estimates ....................................................................................... 34\n 4.1 Background ............................................................................................................. 34\n 4.2 Published datasets ................................................................................................ 34\n Lower layer super output area (LSOA) and Data zones (DZs) .............................. 35\n Estimates of households not connected to the gas network at LSOA/IGZ level .... 35\n\n5. Comparison with other sources .................................................................................. 36\n 5.1 Electricity .............................................................................................................. 36\n\n6. Developments and future plans ................................................................................ 39\n 6.1 Developments during the year .............................................................................. 39\n 6.2 Future plans .......................................................................................................... 39\n\nAnnex A: Highest and lowest local authority averages, 2014 ........................................ 41\nAnnex B: Sub-national consumption publications ....................................................... 43\nAnnex C: Tools available to analyse sub-national consumption statistics ..................... 44\nAnnex D: An illustration of LSOA areas within an MSOA ............................................ 45\n\nExecutive summary\n\nThis publication provides estimates of annual electricity and gas consumption below national level. Latest estimates are for 2014.\n\nBetween 2005 and 2014 electricity consumption in Great Britain has fallen eight per cent, with the largest decline in the North East (down 17 per cent) and the smallest in London, (down 0.1 per cent). The most recent data shows this diversion accelerating, with consumption in 2014 compared to 2013 falling 2.5 per cent in the North East, and rising 2.3 per cent in London. This pattern was evident in both the domestic and non-domestic sectors.\n\nGas consumption has also fallen, with mean consumption down 30.4 per cent in 2014 compared to 2005. However, unlike for electricity, the pictures for the domestic and non-domestic sectors are very different. The overall fall in gas demand has been driven by the domestic sector where all regions have seen similar declines, between 27 per cent (London) and 34 per cent (Wales). Meanwhile, this fall was partially offset by the non-domestic sector, where mean consumption increased nine per cent between 2005 and 2014. Within this, over the same time period there were large differences between the regions; the West Midlands saw a rise of 17 per cent, contrasted by a 15 per cent fall in the North East.\n\nIn 2014, the North East had the lowest proportion of properties that were not connected to the gas grid (3.0 per cent), while the South West has the highest (19 per cent). The proportion of properties off the gas grid in the South West did, however, decrease by 1.2 percentage points compared to 2013.\n\n1. Introduction\n\n1.1 Background\n\nThis document provides commentary on DECC’s sub-national estimates of electricity and gas consumption for Great Britain. Estimates are based on meter point data provided by the electricity and gas industries from their administrative systems. The most recent estimates are provisional estimates for 2014.\n\nEstimates are published from domestic and non-domestic users and broken down by Region/Devolved Administration\\(^1\\) (referred to as regions for the rest of this document) and local authority. Middle layer super output area (intermediate geography zone in Scotland) and lower layer super output area (England and Wales, domestic, only) estimates for 2014 will be published on 28 January 2016, and made available here: https://www.gov.uk/government/collections/sub-national-electricity-consumption-data (for electricity) and https://www.gov.uk/government/collections/sub-national-gas-consumption-data (for gas).\n\nFor full details on the methodology, assumptions and data interpretation relating to these statistics, please refer to the Methodology and Guidance document available here: https://www.gov.uk/government/publications/regional-energy-data-guidance-note. Readers are highly advised to familiarise themselves with the material in the booklet before using the data.\n\nFor national estimates of domestic consumption Table 3.07 of ECUK\\(^2\\) should be used. Breakdowns of consumption by property attributes and household/business characteristics are available through the National Energy Efficiency Data-Framework (NEED)\\(^3\\).\n\nMore information on the changes and future planned developments are outlined in section 6 of this report.\n\n1.2 Users\n\nThe most significant use of the sub-national consumption data is by Local Authorities and devolved administrations, other external users including academics and industry. Most commonly data have been used for targeting, to examine trends over time, or assess the effectiveness of carbon reduction and energy efficiency policies and initiatives.\n\nInternally, data are used by DECC policy colleagues and other analysts to inform policy development and help with monitoring and evaluation of DECC policies. The meter point gas and electricity data collected for sub-national consumption outputs are also used in NEED.\n\nFeedback from users of these data is welcomed. If you have any comments or queries please send these to firstname.lastname@example.org.\n\n---\n\n\\(^1\\) A region refers to areas previously known as Government Office Regions (GORs), which were the primary statistical subdivision of England in which the Government Offices for the region fulfilled their role. They closed on 31 March 2011 and have remained a static geography used for statistical reporting since then. Further information is available in section 1.2 of the Sub-national methodology and guidance booklet.\n\n\\(^2\\) https://www.gov.uk/government/statistics/energy-consumption-in-the-uk.\n\n\\(^3\\) https://www.gov.uk/government/collections/national-energy-efficiency-data-need-framework.\n\n2. Electricity\n\nThe data analysed in this document are based on the aggregation of Meter Point Administration Number (MPAN) readings throughout Great Britain obtained as part of DECC’s annual meter point electricity data collection exercise. The estimates presented for 2014 are provisional and cover the industry defined years:\n\n- Electricity non-half hourly\\(^4\\) - 1 February 2014 to 31 January 2015;\n- Electricity half hourly\\(^5\\) - 1 January 2014 to 31 December 2014\n\nThis section looks at electricity consumption by consuming sector (i.e. domestic and non-domestic), and geographic area (region and local authority).\n\nAnnual data for 2005 to 2014 can be found here: [https://www.gov.uk/government/collections/sub-national-electricity-consumption-data](https://www.gov.uk/government/collections/sub-national-electricity-consumption-data).\n\n2.1 Total electricity consumption\n\nDuring 2014, the total annual electricity consumption in Great Britain was 295,320 GWh (via 30.0 million meters), 1.8 per cent higher than consumption in 2013 (289,893 GWh)\\(^6\\).\n\nThe number of electricity meters increased in 335 of the 380 local authorities between 2013 and 2014, whilst only 250 local authorities had an increase in total annual consumption. The number of meters in an area can change as new properties are built and old properties demolished. For example, between 2012 and 2013, the number of meters in the Newham Borough of London increased by three per cent (approximately 3,200 meters). This was primarily a result of new properties being built in the Olympic Park.\n\nAssigning a meter to an area within the sub-national electricity consumption statistics is dependent upon accurate address information for each meter. If there is no accurate address information then meters are assigned as ‘Unallocated’\\(^7\\). This will have an impact on the estimates provided for some areas. During the analysis of the 2014 electricity consumption data, DECC identified approximately 0.4 per cent of electricity meters as unallocated in 2014 compared to 0.2 per cent in 2013. However, in terms of annual electricity consumption this represents 11.0 per cent, an increase of 9.3 percentage points on 2013 (1.7 per cent). The impact of the unallocated consumption resulted in large variations at regional and local authority level for total annual electricity consumption but more specifically for non-domestic than domestic meters. DECC are currently investigating this data issue. In the meantime, we have temporarily resolved this issue by setting the unallocated non-domestic count and consumption in 2014 equivalent to 2013. The difference between the unallocated non-domestic count and consumption in 2013 and 2014 has then been proportionally allocated across all regions and local authorities. The geographical variations seen between 2013 and 2014 are now in line with previous years.\n\n---\n\n\\(^4\\) A non-half hourly (NHH) meter is generally used for domestic or smaller non-domestic supplies. Reading of NHH meters is normally done manually.\n\n\\(^5\\) A half hourly (HH) meter is generally used for larger non-domestic supplies. A reading is automatically taken every half hour and relayed to the supplier.\n\n\\(^6\\) Sub-national estimates for total electricity consumption differ slightly from electricity consumption estimates included in Chapter 5 of the Digest of UK Energy Statistics (DUKES). For further information about the differences in electricity consumption estimates between the sub-national statistics and DUKES/ECUK, please refer to the Methodology and Guidance document available here: [https://www.gov.uk/government/publications/regional-energy-data-guidance-note](https://www.gov.uk/government/publications/regional-energy-data-guidance-note).\n\n\\(^7\\) ‘Unallocated’ meters are meters with insufficient address information to assign their consumption to a geographical area.\n\nFollowing successful reconciliation with the electricity industry, we intend to publish revisions of the provisional statistics on 28 January 2016.\n\nThe changes in electricity consumption in Great Britain between 2013 and 2014 are summarised in Table 1 below. The table shows that there has been an increase in the number of meters for all regions. This is consistent with the gradual increase seen each year since 2005.\n\nChanges in total electricity consumption between 2013 and 2014 are more varied, ranging from a 4.4 per cent increase in total consumption in the West Midlands to a 2.5 per cent decrease in the North East. In Great Britain as a whole, there was an overall increase in consumption of 1.8 per cent. Changes in total consumption levels are usually driven by changes in the non-domestic sector given that it represents 63 per cent of total consumption (in 2014) and tends to be more changeable than domestic consumption.\n\n**Table 1: Electricity consumption in Great Britain by region, 2013 and 2014**\n\n| Region | 2013 Total annual electricity consumption (GWh) | Number of meters (thousand) | 2014 Total annual electricity consumption (GWh) | Number of meters (thousand) | Percentage Change in total annual electricity consumption (%) | Number of meters (thousand) |\n|-------------------------------|-------------------------------------------------|-----------------------------|-------------------------------------------------|-----------------------------|-------------------------------------------------------------|-----------------------------|\n| East Midlands | 21,113 | 2,162 | 21,479 | 2,166 | 1.7% | 0.2% |\n| East of England | 26,756 | 2,791 | 26,969 | 2,798 | 0.8% | 0.2% |\n| London | 40,478 | 3,837 | 41,402 | 3,847 | 2.3% | 0.3% |\n| North East | 11,869 | 1,280 | 11,575 | 1,281 | -2.5% | 0.1% |\n| North West | 32,168 | 3,389 | 32,611 | 3,399 | 1.4% | 0.3% |\n| South East | 38,802 | 4,086 | 38,183 | 4,095 | -1.6% | 0.2% |\n| South West | 24,277 | 2,707 | 25,262 | 2,718 | 4.1% | 0.4% |\n| West Midlands | 24,492 | 2,584 | 25,568 | 2,591 | 4.4% | 0.3% |\n| Yorkshire and the Humber | 23,686 | 2,528 | 23,940 | 2,531 | 1.1% | 0.1% |\n| **England** | **243,640** | **25,363** | **246,991** | **25,426** | **1.4%** | **0.2%** |\n| Wales | 15,546 | 1,510 | 16,451 | 1,516 | 5.8% | 0.4% |\n| Scotland | 25,873 | 2,979 | 26,831 | 2,978 | 3.7% | 0.0% |\n| Unallocated | 4,917 | 73 | 5,047 | 128 | 2.6% | 75.6% |\n| **Great Britain** | **289,976** | **29,925** | **295,320** | **30,047** | **1.8%** | **0.4%** |\n\nChart 1 shows the change in total electricity consumption since 2005 (when the sub-national time series started), taking 2005 as the baseline (2005=100). It can be observed that every region follows a similar decreasing trend, despite seeing an increase in consumption between 2013 and 2014. The largest percentage change, between 2005 and 2014, was seen in the North East where consumption decreased by 17.0 per cent from 13,897 GWh to 11,575 GWh. The smallest reduction in consumption was observed in London, where consumption decreased just 0.1 per cent over the period.\n\nChart 1: Change in electricity consumption over time by region (2005 = 100)\n\nIndex: 2005 = 100\n\nTotal Electricity Consumption:\nPercentage change between 2005 and 2014\n\n-0.1% London\n-8% Great Britain\n-17% North East\n\nMap 1: Total annual electricity consumption by local authority, 2014\n\nGWh\n- Less than 500\n- 500 to 750\n- 750 to 1000\n- 1000 to 1250\n- 1250 to 4000\n\nGreater London\n\nTotal electricity consumption can be split between the domestic and non-domestic sectors based on the meter profile assigned by the electricity industry. The non-domestic sector consumes a much higher proportion of total electricity for all regions across Great Britain (Chart 2) despite the non-domestic sector having a significantly lower number of meters. Of the 30.0 million meters in operation in 2014, 27.6 million meters were in the domestic sector and 2.4 million were in the non-domestic sector.\n\n**Chart 2: Distribution of domestic and non-domestic electricity consumption by region, 2014**\n\n| Region | Domestic | Non-domestic |\n|-------------------------|----------|--------------|\n| East Midlands | 36% | 64% |\n| East of England | 41% | 59% |\n| London | 32% | 68% |\n| North East | 35% | 65% |\n| North West | 37% | 63% |\n| South East | 42% | 58% |\n| South West | 41% | 59% |\n| West Midlands | 37% | 63% |\n| Yorkshire and the Humber| 36% | 64% |\n| Wales | 32% | 68% |\n| Scotland | 40% | 60% |\n| Great Britain | 37% | 63% |\n\nAcross Great Britain, 37 per cent of electricity is estimated to be consumed in the domestic sector, and 63 per cent by the non-domestic sector (compared with 92 per cent of meters in the domestic sector and 8 per cent in the non-domestic sector). However, the split varies across the regions of Great Britain. Domestic consumption accounted for 32 per cent of total electricity consumption in Wales and 42 per cent in the South East. The variation is even more marked across local authorities. For example non-domestic consumption makes up more than 80 per cent of total electricity consumption in six local authorities (City of London, Westminster, Neath Port Talbot, Tower Hamlets, Rutland and Camden) and as little as 34 per cent in one local authority (East Renfrewshire). The distribution depends on local factors, such as the type of industry/service, the mix of properties and the extent to which electricity is used for heating.\n\n### 2.2 Domestic electricity consumption\n\n#### Total domestic consumption\n\nTotal domestic electricity consumption in Great Britain in 2014, was estimated to be 109,170 GWh, 0.7 per cent higher than in 2013 (108,420 GWh). The South East consumed 14.8 per cent of this total, whilst the North East used 3.8 per cent. Factors influencing total domestic electricity consumption include the population/number of households in a region and the fuel mix used to meet domestic energy demands (for example, households without access to gas are likely to use more electricity for heating).\n\nAverage domestic consumption\n\nMean annual domestic electricity consumption per meter in Great Britain was 3,954 kWh and the median was 3,188 kWh, a difference of 24.0 per cent. The difference in the mean and median is more pronounced for electricity than for gas because of the variety of ways electricity is used in homes (for example, some properties use electricity for heating and others do not, while the majority of homes with a gas connection use gas for heating).\n\nMean consumption per meter in 2014 was 0.4 per cent higher than in 2013 (3,940 kWh) and the median electricity consumption was very similar to the 2013 value of 3,206 kWh.\n\nThe North East had the lowest mean and median domestic consumption, 3,418 kWh and 2,901 kWh respectively, whilst the South East had the highest mean and median domestic consumption, 4,294 kWh and 3,418 kWh respectively. Table 2 shows the mean and median domestic consumption per meter in each region in 2014, it also includes the same figures broken down for standard and Economy 7 meters (more details in the following section).\n\nTable 2: Average domestic electricity consumption per meter by region, 2014\n\n| | All domestic meters | Standard domestic meters | Economy-7 meters |\n|----------------------|---------------------|--------------------------|------------------|\n| | Mean domestic | Median domestic | Percentage | Mean domestic | Median domestic | Percentage |\n| | consumption (kWh) | consumption (kWh) | of domestic | consumption (kWh) | consumption (kWh) | of domestic |\n| | | | meters | | | meters |\n| East Midlands | 3,681 | 3,150 | 2,005 | 3,556 | 3,004 | 64% |\n| East of England | 4,284 | 3,395 | 2,577 | 3,880 | 3,208 | 69% |\n| London | 3,828 | 2,982 | 3,449 | 3,632 | 2,872 | 86% |\n| North East | 3,418 | 2,901 | 1,198 | 3,303 | 2,870 | 94% |\n| North West | 3,809 | 3,185 | 3,158 | 3,625 | 3,115 | 92% |\n| South East | 4,294 | 3,418 | 3,761 | 4,012 | 3,274 | 81% |\n| South West | 4,209 | 3,330 | 2,467 | 3,781 | 3,140 | 84% |\n| West Midlands | 3,988 | 3,288 | 2,392 | 3,734 | 3,176 | 83% |\n| Yorkshire and the Humber | 3,929 | 3,287 | 2,349 | 3,631 | 2,923 | 92% |\n| England | 3,976 | 3,203 | 23,357 | 3,703 | 3,082 | 83% |\n| Wales | 3,735 | 3,097 | 1,389 | 3,509 | 3,023 | 93% |\n| Scotland | 3,915 | 3,134 | 2,760 | 3,602 | 3,043 | 83% |\n| Unallocated\\(^1\\) | 2,962 | 2,240 | 105 | 2,876 | 2,203 | 93% |\n| Great Britain | 3,954 | 3,188 | 27,611 | 3,679 | 3,072 | 83% |\n\nMean domestic electricity consumption per meter in Great Britain has decreased by 14.1 per cent between 2005 and 2014. Over the same period, regional reductions in domestic electricity consumption varied between 10.4 per cent in London to 17.9 per cent in the West Midlands. There are a number of factors which may have contributed to these reductions in consumption, including; weather conditions, energy efficiency improvements\\(^8\\), such as increased levels of insulation, new boilers and more energy efficient appliances; increased prices\\(^9\\); the recession; changes in the building stock; and household composition. It should also be noted that 2005, the earliest point for this analysis, is where DUKES also represents a peak in domestic electricity consumption to date\\(^10\\).\n\n---\n\n\\(^8\\) The energy efficiency of the housing stock improved between 2005 and 2013, the average SAP rating of a dwelling increased by 11.0 points from 49.0 to 60.0. The SAP rating is a measure of the overall energy efficiency of the dwelling. Table 13: English Housing Survey Headline Report 2013-14: https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/469213/English_Housing_Survey_Headline_Report_2013-14.pdf.\n\n\\(^9\\) Between 2005 and 2013, domestic electricity prices contained in Quarterly Energy Prices show an increase of 81.4 per cent (50 per cent in real terms) which is likely to have influenced demand. ‘Quarterly Energy Prices’ can be accessed here: https://www.gov.uk/government/statistics/quarterly-energy-prices-september-2015.\n\n\\(^10\\) See Table 5.1 of DUKES: https://www.gov.uk/government/statistics/electricity-chapter-5-digest-of-united-kingdom-energy-statistics-dukes.\n\nIn the map below, known as a cartogram, the size of each local authority area has been adjusted according to its population. This can help interpretation as it prevents densely populated areas being underrepresented. For example, London accounts for 15 per cent England’s population, but only 1.2 per cent of land area; the cartogram expands the area of London to account for this.\n\n**Map 2: Mean domestic electricity consumption per meter by local authority, 2014**\n\n| kWh | Description |\n|--------------|---------------------------|\n| Greater than 4,500 | Greater than 4,500 |\n| 4,250 to 4,500 | 4,250 to 4,500 |\n| 4,000 to 4250 | 4,000 to 4250 |\n| 3,750 to 4,000 | 3,750 to 4,000 |\n| 3,500 to 3,750 | 3,500 to 3,750 |\n| Less than 3,500 | Less than 3,500 |\n\nChart 3 shows the decrease in average domestic consumption by region, between 2005 and 2014. However, between 2013 and 2014, all but two regions saw an increase in mean domestic consumption per meter with Scotland showing the largest increase of 1.6 per cent. The North East and Wales were the only two regions which saw slight decreases in average consumption between 2013 and 2014.\n\n**Chart 3: Change in mean domestic electricity consumption per meter, 2005 and 2014**\n\nOrdinary domestic and Economy 7 consumption\n\nMean consumption for customers with standard domestic meters was 3,679 kWh (median consumption was 3,072 kWh), compared to 5,333 kWh for households with an Economy 7 meter\\(^{11}\\) (median consumption was 4,088 kWh). Households with an Economy 7 meter are more likely to use electricity to heat their homes and therefore typically have higher consumption as well as a greater range of consumption. The region with the highest mean consumption per Economy 7 meter in 2014 was the South West (6,541 kWh mean and 5,486 kWh median) followed closely by Wales (mean 6,538 kWh and median 5,151 kWh) whilst the East Midlands had the lowest average per Economy 7 meter (4,456 kWh mean and 3,457 median). It should be noted that not all customers who have an Economy 7 meter will be on an Economy 7 tariff. However, customers with an ordinary domestic meter cannot be on an Economy 7 tariff. In some instances electricity used for heating purposes will not be consumed off-peak.\n\nThe distribution between households with ordinary standard domestic meters and Economy 7 meters at regional level in Great Britain is shown in Chart 4 below. For Great Britain, 78 per cent\n\n---\n\n\\(^{11}\\) An Economy 7 meter allows a property to have a two rate tariff if the household chooses to, usually differentiating payment by peak and (cheaper) off-peak consumption. In the majority of cases, Economy 7 meters still measure all of a household’s consumption (that is, the total of its ordinary and Economy 7 consumption) through a single meter.\n\nof total domestic consumption was attributed to ordinary domestic meters and 22 per cent to Economy 7 meters. However, across Great Britain the ratio between ordinary domestic and Economy 7 varied from a 91:9 per cent split in the North East, to a 59:41 per cent split in the East Midlands.\n\n**Chart 4: Distribution of total domestic electricity consumption by profile, 2014**\n\n| Region | Standard (%) | Economy 7 (%) |\n|-------------------------|--------------|---------------|\n| East Midlands | 59% | 41% |\n| East of England | 62% | 38% |\n| London | 82% | 18% |\n| North East | 91% | 9% |\n| North West | 88% | 12% |\n| South East | 76% | 24% |\n| South West | 76% | 24% |\n| West Midlands | 77% | 23% |\n| Yorkshire and the Humber| 88% | 12% |\n| Wales | 87% | 13% |\n| Scotland | 77% | 23% |\n| Great Britain | 78% | 22% |\n\nChart 5 shows box plots illustrating the distribution of domestic consumption for Economy 7 meters, standard meters, and all domestic meters in Great Britain. It is clear that the spread of consumption is much larger for Economy 7 meters, with an interquartile range of 4,996 kWh and 4,706 kWh in 2013 and 2014 respectively; compared with standard meters, which had an interquartile range of around 2,660 kWh, in both 2013 and 2014.\n\nChart 5 also shows that for Economy 7 meters, there was a general reduction in consumption of electricity in 2014, when compared with 2013, whereas there was 1.3 per cent increase in standard meters. In 2013, the mean annual consumption for Economy 7 meters was 5,274 kWh and the median value was 4,131 kWh. In 2014 the mean annual electricity consumption was reduced to 5,333 kWh and the median decreased to 4,088 kWh.\n\n2.3 Non-domestic electricity consumption\n\nTotal non-domestic consumption\n\nIn 2014 total non-domestic electricity consumption in Great Britain was 186,150 GWh, which was 2.5 per cent higher than non-domestic consumption in 2013 (181,556 GWh). However, since 2005, non-domestic electricity consumption has decreased in Great Britain, falling by 7.3 per cent (200,889 GWh).\n\nAverage non-domestic consumption\n\nIn 2014, the mean annual non-domestic electricity consumption per meter, in Great Britain, was 76,402 kWh and the median was 8,614 kWh, with total non-domestic electricity consumption of 186,150 GWh. Average consumption for non-domestic customers remained within one per cent of mean consumption in 2013 (75,520 kWh), with total non-domestic consumption 2.5 per cent higher than in 2013 (181,556 GWh).\n\nAt a local authority level, high average non-domestic consumption can occur where there are a small number of very high consumers which dominate the area (e.g. Neath Port Talbot, Wales) or a more consistently relatively high consuming non-domestic population (e.g. City of London). The mean consumption is also highly influenced by a relatively small number of very high consuming meters, which can result in big differences between mean and median consumption in this sector. This is seen in areas like Neath Port Talbot, Redcar and Cleveland where the mean is more than 25 times the median. The City of London had the highest median annual non-domestic consumption of 20.2 MWh, whereas Hammersmith and Fulham had the smallest median annual non-domestic consumption of 3.6 MWh.\n\nThe Isles of Scilly (21.5 MWh) had the lowest average non-domestic consumption per meter in 2014. This low level of non-domestic consumption reflects the rural characteristic of the area and the few commercial/heavy industrial properties.\n\nThe North East had the largest percentage decrease (20.2 per cent) in average non-domestic consumption between 2005 and 2014. London was the only region with an increase over this period (8.2 per cent, see Chart 6). Between 2005 and 2014 the average non-domestic consumption per meter for Great Britain decreased by 7.0 per cent. The energy efficiency of buildings and economic recession will have had an impact on consumption and this will have varied between regions.\n\n**Chart 6: Average non-domestic electricity consumption for selected regions, 2005 to 2014**\n\nIt is important to recognise that when making comparisons between years at local authority level, total and average consumption levels are influenced by changes to establishments in a local authority. This could be because of relocations, new industrial or commercial establishments opening or the closure or downsizing of existing businesses. The impact of these changes on totals and averages is highly dependent on the size of the business. The rate of change of average consumption will be impacted by these factors, particularly since 2008.\n\ngiven the recent recession. Weather conditions have a smaller impact on non-domestic consumption than on household use as less of the energy is used for heating.\n\nTable 3 shows the average (mean and median) non-domestic electricity consumption per meter in each region.\n\n**Table 3: Average non-domestic electricity consumption per meter by region, 2014**\n\n| Region | Mean consumption (kWh) | Median consumption (kWh) | Number of non-domestic meters (thousand) |\n|-------------------------------|------------------------|--------------------------|-----------------------------------------|\n| East Midlands | 85,069 | 10,305 | 161 |\n| East of England | 72,315 | 9,449 | 220 |\n| London | 70,809 | 6,632 | 398 |\n| North East | 90,810 | 9,059 | 82 |\n| North West | 85,494 | 9,724 | 241 |\n| South East | 66,008 | 8,462 | 334 |\n| South West | 59,084 | 7,422 | 252 |\n| West Midlands | 80,557 | 9,291 | 199 |\n| Yorkshire and the Humber | 84,102 | 9,467 | 182 |\n| **England** | **74,488** | **8,532** | **2,069** |\n| Wales | 89,095 | 7,893 | 126 |\n| Scotland | 73,712 | 9,660 | 217 |\n| Unallocated¹ | 201,441 | 11,475 | 24 |\n| **Great Britain** | **76,402** | **8,614** | **2,436** |\n\n**Distribution of non-domestic consumption**\n\nChart 7 provides more information about how mean non-domestic consumption for each local authority varies within region. The box plot shows the minimum, the upper and lower quartile and the median values for the mean electricity consumption in LAs within each region. The maximum is also shown where it is below 200,000 kWh. In two regions (London and Wales) the highest mean non-domestic electricity consumption are greater than 200,000 kWh, but are not shown in the chart to allow for a clearer comparison of the other statistics.\n\nThe analysis of the electricity meter point data shows that the overall trend in consumption at a national level has continued to follow a general downward trend over the last few years, but has seen an increase between 2013 and 2014, of 1.8 per cent to 295,320 GWh. There are large variations in consumption levels and changes over time at a more local level. These can be seen in more detail in the accompanying data tables at: https://www.gov.uk/government/collections/sub-national-electricity-consumption-data\n\n3. Gas\n\nThe data analysed in this document are based on the aggregation of Meter Point Reference Number (MPRN) readings throughout Great Britain obtained as part of DECC’s annual meter point gas data exercise. The estimates for 2014 cover the gas year between 1 October 2013 and 30 September 2014 and are supplied to DECC as weather corrected data. Estimates presented for 2014 are provisional.\n\nIn the domestic sector, gas consumption is predominately used for heating purposes and as a result usage is driven by external temperatures and weather conditions. The weather correction factor enables comparisons of gas use over time, controlling for weather changes. An overview of the weather correction process is available here: https://www.gov.uk/government/publications/overview-of-weather-correction-of-gas-industry-consumption-data.\n\nThis section looks at gas consumption by consuming sector (i.e. domestic and non-domestic), and geographic area (region and local authority). To distinguish if a meter reading is domestic or non-domestic, the gas industry cut-off point of 73,200 kWh has been used – that is, if a meter consumes less than 73,200 kWh it is defined as a domestic meter, and non-domestic if it consumes 73,200 kWh or more.\n\nThe published gas statistics can be found here: https://www.gov.uk/government/collections/sub-national-gas-consumption-data.\n\n3.1 Total gas consumption\n\nDuring 2014, the total annual gas consumption in Great Britain was 495,661 GWh (via 23,505,486 meters), 0.6 per cent lower than consumption in 2013 (498,402 GWh). As gas data are weather corrected, this represents a decrease irrespective of weather conditions in the year.\n\nTotal consumption decreased in 297 local authority areas whereas the total number of gas meters increased in 302 out of the 376\\(^{12}\\) local authorities between 2012 and 2013. The number of meters in an area can change as new properties are built and old properties demolished. In addition, assigning a meter to an area within the sub-national gas consumption statistics is also dependent upon the address information for each meter. Improvements in address information may allow more meters to be matched to the correct geographic area rather than remaining ‘Unallocated’\\(^{13}\\). This means that an increase in the number of meters in an area may reflect better postcode allocation, rather than an actual increase in the number of meters within the year.\n\nThe changes in gas consumption and number of meters in Great Britain between 2013 and 2014 are shown for each region in Table 4 below. The table shows that there has been an increase in the number of meters for all regions. This is consistent with the gradual increase seen each year since 2005.\n\n---\n\n\\(^{12}\\) The local authorities of Eilean Siar (Western Isles), Orkney Islands, Shetland Islands and Isles of Scilly do not have access to gas.\n\n\\(^{13}\\) ‘Unallocated’ meters are meters with insufficient address information to assign their consumption to a geographical area.\n\nThere has been a decrease in total consumption of gas across the majority of regions of Great Britain between 2013 and 2014, ranging from a 0.5 per cent decrease in the East of England to 3.3 per cent decrease in the North East. In Great Britain as a whole, there was an overall decrease in consumption of 0.6 per cent.\n\nIn 2014, the City of London (London) had the highest local authority mean gas consumption at 234,341 kWh compared with Torridge (South West) with the lowest mean gas consumption at 12,485 kWh.\n\nMap 4: Total annual gas consumption, by local authority, 2014\n\nGWh\n- Less than 750\n- 750 to 1000\n- 1000 to 250\n- 1251 to 1500\n- Greater than 1500\n\nGreater London\n\n3.2 Domestic gas consumption\n\nAverage domestic gas consumption\n\nThe mean and median annual gas consumption per domestic meter in 2014 were 13,246 kWh and 11,788 kWh respectively, with a total domestic gas consumption of 307,832 GWh. Both mean and total consumption were lower than in 2013 by 3.2 and 2.5 per cent respectively\\(^{14}\\).\n\nTable 5 shows the average (mean) domestic gas consumption per meter, the total number of domestic meters, total domestic consumption for each region and the median domestic consumption in 2014.\n\n**Table 5: Mean domestic gas consumption per meter by region, 2014**\n\n| Region | Number of domestic meters (thousands) | Total domestic consumption (GWh) | Mean domestic consumption (kWh) | Median domestic consumption (kWh) |\n|-------------------------------|--------------------------------------|----------------------------------|---------------------------------|----------------------------------|\n| East Midlands | 1,759 | 23,774 | 13,513 | 12,291 |\n| East of England | 2,056 | 27,576 | 13,411 | 11,953 |\n| London | 3,015 | 39,850 | 13,218 | 11,314 |\n| North East | 1,096 | 14,790 | 13,489 | 12,388 |\n| North West | 2,893 | 37,508 | 12,966 | 11,648 |\n| South East | 3,188 | 43,539 | 13,655 | 11,952 |\n| South West | 1,840 | 21,639 | 11,763 | 10,348 |\n| West Midlands | 2,102 | 27,872 | 13,263 | 12,033 |\n| Yorkshire and the Humber | 2,115 | 28,898 | 13,663 | 12,318 |\n| **England** | **20,064** | **265,445** | **13,230** | **11,774** |\n| Wales | 1,118 | 14,002 | 12,527 | 11,421 |\n| Scotland | 1,986 | 27,549 | 13,872 | 12,260 |\n| Unallocated\\(^1\\) | 72 | 837 | 11,640 | 10,127 |\n| **Great Britain** | **23,239** | **307,832** | **13,246** | **11,788** |\n\n\\(^1\\) A small number of meters in Great Britain, cannot be described as being in a specific area (0.3 per cent). These meters are therefore categorised as 'Unallocated'.\n\nScotland had the highest mean domestic consumption with 13,872 kWh per meter (median consumption of 11,952 kWh), with the South West having the lowest at 11,763 kWh per meter.\n\nIn terms of total domestic gas consumption for Great Britain, the South East consumed 14.1 per cent of all domestic gas, followed by London (13.0 per cent) and the North West (12.2 per cent). The North East and Wales consumed the least; 4.8 and 4.5 per cent respectively.\n\nMap 5, shows average (mean) domestic gas consumption per meter by local authority in 2014. South Bucks (South East) had the highest mean gas consumption in 2014 at 19,562 kWh compared with the lowest in Tower Hamlets (London) at 7,822 kWh.\n\n---\n\n\\(^{14}\\) The sub-national data is weather corrected, however unadjusted domestic gas consumption estimates are available in Table 3.07 of Energy Consumption in the UK (ECUK): [https://www.gov.uk/government/collections/energy-consumption-in-the-uk](https://www.gov.uk/government/collections/energy-consumption-in-the-uk). Estimates in Table 3.07 show a decrease in overall domestic consumption between 2013 and 2014 (from 342,501 GWh to 278,101 GWh) and average consumption (from 15,373 kWh to 12,404 kWh).\n\nGas\n\nIn the map below, known as a cartogram, the size of each local authority area has been adjusted according to its population. This can help interpretation as it prevents densely populated areas being underrepresented. For example, London accounts for 15 per cent England’s population, but only 1.2 per cent of land area; the cartogram expands the area of London to account for this.\n\n**Map 5: Average domestic gas consumption per meter by local authority, 2014**\n\nMean domestic gas consumption per meter in Great Britain decreased by 30.4 per cent between 2005 and 2014. There are a number of factors which may have contributed to the reductions in consumption, including; weather conditions, energy efficiency improvements\\(^{15}\\),\n\n---\n\n\\(^{15}\\) The energy efficiency of the housing stock improved between 2005 and 2013, the average SAP rating of a dwelling increased by 11.0 points from 49.0 to 60.0. The SAP rating is a measure of the overall energy efficiency of the dwelling. Table 13: English Housing Survey Headline Report 2013-14; https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/469213/English_Housing_Survey_Headline_Report_2013-14.pdf.\n\nsuch as increased levels of insulation, new boilers and more energy efficient appliances; increased prices\\(^{16}\\) and the recession; and changes in the building stock and household composition.\n\nChart 8 shows the decrease in average domestic gas consumption per meter point between 2005 and 2014 at regional level. Mean domestic consumption in 2014 was lower than 2013 in all regions; with the largest decrease occurring in the North West (a reduction of 602 kWh, or 4.4 per cent), and the smallest in the West Midlands (327 kWh, or 2.4 per cent).\n\n**Chart 8: Decrease in average domestic consumption per meter point between 2005 and 2014, and between 2013 and 2014**\n\nChart 9 shows the mean domestic gas consumption per meter for Scotland, the South West and Great Britain between 2005 and 2014. These regions have been selected as they had the highest and lowest average domestic gas consumption for each of the seven years. The average consumption for all other regions in Great Britain was between the lines shown for Scotland and the South West and all regions followed a similar trend.\n\n---\n\n\\(^{16}\\) Between 2005 and 2014, domestic electricity prices contained in Quarterly Energy Prices show an increase of 86.2 per cent (51.4 per cent in real terms) which is likely to have influenced demand. ‘Quarterly Energy Prices’ can be accessed here: [https://www.gov.uk/government/collections/quarterly-energy-prices](https://www.gov.uk/government/collections/quarterly-energy-prices).\n\nDistribution of domestic consumption\n\nChart 10 shows a series of box plots illustrating the distribution of average domestic gas consumption for local authorities within each region as well as a box plot for Great Britain. These have been calculated based on average (mean) consumption for each local authority within each region. The spread (inter-quartile range) between the upper (Q3) and lower (Q1) quartiles (that is, the middle 50 per cent of the data), of average domestic gas consumption in local authorities was greatest in the South East (a difference of 3,246 kWh per meter), whereas the inter-quartile range for the North East was 737 kWh as indicated by the shorter box; however the number of points represented by each plot varies, for instance the South East covers 67 local authorities, whereas the North East covers just 12 local authorities.\n\nThe whiskers in the chart represent the highest and lowest mean in each region. The local authority with minimum average domestic consumption varies within each region from 9,110 kWh (Tower Hamlets) in London to 12,616 kWh (South Tyneside) in the North East. The largest average domestic consumption per meter varies from 13,762 kWh (Merthyr Tydfil) in Wales to 19,562 kWh (South Bucks) in the South East.\n\n3.3 Non-domestic gas consumption\n\nTotal non-domestic consumption\n\nIn 2014, total non-domestic annual gas consumption in Great Britain was 187,829 GWh (via 266,077 meters), 2.8 per cent higher than consumption in 2013 (182,746 GWh).\n\nNon-domestic consumption increased in 152 local authority areas\\(^{17}\\) between 2013 and 2014. The total number of gas meters increased in 141 local authorities between 2013 and 2014.\n\n---\n\n\\(^{17}\\) The local authorities of Eilean Siar (Western Isles), Orkney Islands, Shetland Islands and Isles of Scilly are not included in the sub-national gas consumption datasets due to limitations in access to gas.\n\nAverage non-domestic consumption\n\nAverage annual non-domestic gas consumption per meter was 705,920 kWh in 2014, 5.3 per cent higher than in 2013 (670,216 kWh).\n\nTable 6 shows the average (mean) non-domestic gas consumption per meter and total non-domestic consumption in each of the regions. The North West was responsible for 14 per cent of all non-domestic gas consumption compared to the North East and Wales which consumed 4.4 and 4.9 per cent respectively. Yorkshire and the Humber, Wales and Scotland had the highest average non-domestic consumptions, reflecting the mix of industry in the regions, and\n\nthe greater use of gas for industrial purposes. The South East and London are more service sector orientated and had the lowest mean non-domestic consumption in 2014.\n\n**Table 6: Average non-domestic gas consumption per meter and total non-domestic gas consumption by region, 2014**\n\n| Region | Number of non-domestic meters (thousands) | Total non-domestic consumption (GWh) | Average non-domestic consumption (kWh) |\n|-------------------------------|------------------------------------------|--------------------------------------|---------------------------------------|\n| East Midlands | 19 | 14,130 | 758,535 |\n| East of England | 22 | 15,838 | 714,334 |\n| London | 42 | 21,309 | 511,108 |\n| North East | 11 | 8,323 | 733,018 |\n| North West | 31 | 26,257 | 855,748 |\n| South East | 39 | 18,750 | 478,169 |\n| South West | 19 | 11,688 | 604,677 |\n| West Midlands | 23 | 17,339 | 739,140 |\n| Yorkshire and the Humber | 24 | 22,847 | 960,758 |\n| **England** | **230** | **156,481** | **679,440** |\n| Wales | 11 | 9,287 | 884,357 |\n| Scotland | 24 | 20,501 | 862,904 |\n| Unallocated¹ | 2 | 1,561 | 1,034,178 |\n| **Great Britain** | **266** | **187,829** | **705,920** |\n\n¹ A small number of meters in Great Britain, cannot be described as being in a specific area (0.8 per cent). These meters are therefore categorised as ‘Unallocated’.\n\nChart 11 shows the trends in mean non-domestic gas consumption for Yorkshire and the Humber, Wales, London and the South East, and Great Britain as a whole. In comparison to domestic gas consumption, different trends can be seen for the average annual non-domestic gas consumption between 2005 and 2014 and also between 2013 and 2014.\n\nBetween 2013 and 2014 the North East was the only region that saw a reduction in average consumption per non-domestic gas meter (0.6 per cent). The region with the greatest increase in average consumption was the South West, with a 12.5 per cent increase.\n\nAt a local authority level, King’s Lynn and West Norfolk (East England) had the highest mean gas consumption in 2014 at 5,465,794 kWh compared with 204,191 kWh in Tandridge (South East), which had the lowest mean.\n\nDistribution of non-domestic consumption\n\nChart 12 shows a box plot displaying aspects of the distribution of average non-domestic gas consumption for local authorities for each of the regions, as well as one for local authorities in Great Britain as a whole. For each region, the box plot shows the minimum average (mean) non-domestic gas consumption, the upper and lower quartile and the median average gas consumption. The maximum average non-domestic gas consumption values have been included, however due to the magnitude of a small number of these, many of these continue beyond the chart shown below – these have been excluded to provide a clearer view of the rest of the distribution.\n\nFrom the chart it can be seen that the inter-quartile range of average gas consumption in local authorities was greatest in the North West (622 MWh), whereas the North East had the smallest spread (203 MWh) of average non-domestic gas consumption per local authority, reflecting the difference and similarities in businesses in the areas respectively. The degree of variability between regions is much greater for non-domestic consumption than domestic.\n\n3.4 Number of households not connected to the gas grid\n\nBackground\n\nThere is no definitive source of information on households that are off the gas grid. However, DECC has produced estimates of the number of households without gas based on the difference between the number of gas meters in each area, as set out earlier in this document, and the number of households in each area\\(^{18}\\). These estimates were published for the first time in December 2013.\n\nThe published data does not allow the identification of specific households within an area which are off the gas grid, but do allow small geographic areas which have few or no gas meters to be identified. However there are a number of limitations which should be considered when using these estimates:\n\n- Each gas meter is assigned as domestic or non-domestic based on the gas industry threshold of 73,200kWh, with all meters with consumption below 73,200 kWh assumed to be domestic. This means a number of smaller commercial/industrial consumers are allocated as domestic and therefore estimates of the number of households without gas are an underestimate of the true number. The impact of this assumption on estimates will vary by area.\n\n---\n\n\\(^{18}\\) For the purposes of this work household estimates are taken from the 2011 census to allow consistency with the LSOA and MSOA estimates.\n\nSome meters cannot be allocated to a local authority due to insufficient or incomplete address information\\(^{19}\\). Approximately 0.3 per cent of domestic meters could not be allocated to a local authority in 2014.\n\n- In some cases incorrect address information may mean meters are allocated to the wrong area. The number of meters which are incorrectly allocated will vary by area.\n- In this dataset, there is no differentiation between properties which do not have a gas meter because they are in an area which is off the gas grid and those which are in an area on the gas grid but have a property which is not connected to it (such as inner city blocks of flats).\n- For these estimates it is assumed that each property always has one gas meter. Occasionally a property may have more than one gas meter, which would again mean the estimates provided are an underestimate of the true value.\n- Data refer to the data collection during 2014 and therefore does not include any changes which may have occurred since 2014.\n\n**Estimates of households not connected to the gas grid**\n\nBearing in mind the limitations outlined above, Table 7 below shows the estimated proportion and number of households that are not connected to the gas network in each region of Great Britain.\n\nApproximately 10 per cent of households in Great Britain are not connected to the gas grid; however the proportions vary across each region. The South West and Scotland had the highest proportion of properties without a gas meter (18.8 per cent and 16.3 per cent respectively). The North East and North West have the lowest with 3 and 3.9 per cent of households not connected to the gas network.\n\n**Table 7: Estimated proportion of households not connected to the gas network using 2011 Census data, by region (2014)**\n\n| Region | Number of domestic gas meters (thousands) | Number of households as in 2011 Census (thousands) | Estimated proportion of \"off gas\" households | Estimated number of \"off gas\" households (thousands) |\n|-------------------------------|------------------------------------------|----------------------------------------------------|---------------------------------------------|-----------------------------------------------------|\n| East Midlands | 1,759 | 1,896 | 7.2% | 136 |\n| East England | 2,056 | 2,423 | 15.1% | 367 |\n| London | 3,015 | 3,266 | 7.7% | 251 |\n| North East | 1,096 | 1,130 | 3.0% | 33 |\n| North West | 2,893 | 3,010 | 3.9% | 117 |\n| South East | 3,188 | 3,555 | 10.3% | 367 |\n| South West | 1,840 | 2,265 | 18.8% | 425 |\n| West Midlands | 2,102 | 2,295 | 8.4% | 193 |\n| Yorkshire and the Humber | 2,115 | 2,224 | 4.9% | 109 |\n| **England** | **20,064** | **22,063** | **9.1%** | **1,999** |\n| Wales | 1,118 | 1,303 | 14.2% | 185 |\n| Scotland | 1,986 | 2,373 | 16.3% | 387 |\n| Unallocated\\(^1\\) | 72 | - | - | - |\n| **Great Britain** | **23,239** | **25,739** | **9.7%** | **2,499** |\n\n\\(^1\\) A small number of meters, in Great Britain, cannot be described as being in a specific area (0.3 per cent). These meters are therefore categorised as 'Unallocated'.\n\n\\(^{19}\\) These meters are included in the overall estimates for Great Britain, but are aggregated in the 'Unallocated' row in the sub-national statistics outputs.\n\nMap 7 shows how the proportion of properties without a gas meter varies across local authorities in Great Britain.\n\n**Map 7: Percentage of meters that are off the gas grid by local authority, 2014**\n\nEstimates for local authority (2014 data) have been published at: [https://www.gov.uk/government/collections/sub-national-gas-consumption-data](https://www.gov.uk/government/collections/sub-national-gas-consumption-data).\n\nEstimates for lower level super output area (2014 data) will also be available from this link from 28 January 2016.\n\nDECC have also published an interactive map which displays the distance of off gas properties from the gas network using information on the location of off gas properties and the location of the gas network infrastructure. The map can be accessed here: [https://www.nongasmap.org.uk/](https://www.nongasmap.org.uk/)\n\n4. Super output area estimates\n\n4.1 Background\n\nGas and electricity consumption data are also available at lower layer super output area (LSOA) and middle layer super output area (MSOA). These are statistical geographies developed for the Census (England and Wales) and designed to improve the reporting of small area statistics. They are built up from groups of output areas\\(^{20}\\). Data for Scotland are also published for intermediate geographies (equivalent to MSOAs). DECC is also looking at the potential to publish estimates for Scottish Data Zones (equivalent to LSOAs) in future.\n\nThere are 34,753 LSOAs in England and Wales with a minimum population of 1,000 (or around 400 households). MSOAs are formed from groupings of LSOAs\\(^{21}\\) and there are 7,201 MSOAs in England and Wales, with a minimum population of 5,000 people (or 2,000 households). The intermediate geography zones (IGZ) used in Scotland are aggregations of data zones within local authorities and are slightly smaller than MSOAs, containing between 2,500 and 6,000 people\\(^{22}\\).\n\nGas and electricity estimates for 2011 and later are based on 2011 Census geographies. Data prior to 2011 are based on the 2001 Census boundaries\\(^{23}\\). Estimates for 2014 will be published on 28 January 2016 and can be accessed at: [https://www.gov.uk/government/collections/sub-national-electricity-consumption-data](https://www.gov.uk/government/collections/sub-national-electricity-consumption-data) (electricity) and [https://www.gov.uk/government/collections/sub-national-gas-consumption-data](https://www.gov.uk/government/collections/sub-national-gas-consumption-data) (gas).\n\n4.2 Published datasets\n\nMiddle layer super output area (MSOA) and intermediate geography zone (IGZ)\n\nThe MSOA/IGZ datasets include annual consumption (in kWh), the number of meters and the average consumption per meter (in kWh) for each MSOA/IGZ in Great Britain\\(^{24}\\). Local authority codes and names are also provided.\n\nThe published spreadsheets cover the following four sectors:\n\n1. **Domestic gas estimates** - A domestic gas user is defined as a user with an annual consumption of less than 73,200 kWh, which is the gas industry cut-off point for domestic users. It is recognised that this level of consumption will include some non-domestic users.\n2. **Domestic electricity estimates** – including a split by domestic ordinary and Economy 7 meters.\n3. **Non-domestic gas estimates** - A non-domestic user is defined as a user with an annual consumption of 73,200 kWh or more.\n\n---\n\n\\(^{20}\\) Output Areas are built from clusters of adjacent unit postcodes. They were designed to have similar population sizes and be as socially homogenous as possible based on tenure of household and dwelling type (homogeneity was not used as a factor in Scotland).\n\n\\(^{21}\\) For an illustration of LSOAs within an MSOA please see Annex D.\n\n\\(^{22}\\) Further information about England and Wales or Scotland’s statistical geographies can accessed at:\n\n[http://www.ons.gov.uk/ons/guide-method/geography/beginner-s-guide/census/super-output-areas--soas-/index.html](http://www.ons.gov.uk/ons/guide-method/geography/beginner-s-guide/census/super-output-areas--soas-/index.html)\n\n[http://www.scotland.gov.uk/Publications/2005/02/20697/52626](http://www.scotland.gov.uk/Publications/2005/02/20697/52626).\n\n\\(^{23}\\) Conversion files for 2001 to 2011 Census boundary codes are available at the following links:\n\n[Lower_layer_super_output_areas_(2001)_to_lower_layer_super_output_areas_(2011)_to_local_authority_districts_(2011)_E+W_lookup.zip](http://www.ons.gov.uk/ons/guide-method/geography/beginner-s-guide/census/super-output-areas--soas-/index.html)\n\nand [Middle_layer_super_output_areas_(2001)_to_middle_layer_super_output_areas_(2011)_to_local_authority_districts_(2011)_E-W_lookup.zip](http://www.ons.gov.uk/ons/guide-method/geography/beginner-s-guide/census/super-output-areas--soas-/index.html)\n\n\\(^{24}\\) Some MSOA/IGZ areas may not have access to gas and these areas will have a zero consumption within the sub-national gas consumption datasets. Further information about households with limited access to gas can be found in Section 3.4 of this factsheet.\n\n4. **Non-domestic electricity estimates** – The data at MSOA level excludes half hourly meters. This is to avoid data disclosure issues, as these consumers are generally very large energy users and the potential risk of disclosure is high if they are included in the low level datasets. The spreadsheet does contain half-hourly consumption values at a local authority level.\n\n**Lower layer super output area (LSOA) and Data zones (DZs)**\n\nSimilar to MSOA spreadsheets, the LSOA spreadsheets also publish annual consumption (kWh), the number of meters and average consumption for domestic consumers (again split by standard tariff and Economy 7 tariff for electricity) in each LSOA in England and Wales.\n\nThe two available datasets at an LSOA level are:\n\n1. **Domestic gas estimates**; and\n2. **Domestic electricity estimates**.\n\nDue to disclosure, DECC are only able to publish the gas and electricity LSOA consumption data for domestic consumers in England and Wales. The LSOA dataset does not contain information for the following:\n\n- **Non-domestic consumption** - Due to the small size of these geographical areas, the majority of LSOAs would have such a small number of non-domestic consumers that the non-domestic consumption would be disclosive and would have to be aggregated. Since the non-domestic consumption is available at an MSOA level, DECC took the decision that publishing LSOA level data after aggregation would not add much value for users.\n\n- **Scotland** - The gas and electricity consumption data at a Data Zone (DZ) level is currently not available for Scotland as the 6,505 Data Zones each have a minimum population of 500 and publishing at a lower level would risk breaching disclosure agreements (particularly for gas). However DECC is investigating the value of publishing these data even with a high proportion of merged areas.\n\n**Estimates of households not connected to the gas network at LSOA/IGZ level**\n\nAlso available at an LSOA level are estimates of households not connected to the gas network. These can be accessed here: [https://www.gov.uk/government/collections/sub-national-gas-consumption-data](https://www.gov.uk/government/collections/sub-national-gas-consumption-data).\n\nThese estimates are based on the same methodology as used for the Local Authority estimates, but with population estimates taken from the 2011 Census. Limitations with the data outlined in section 3.4 will be accentuated in these smaller geographic areas.\n\n5. Comparison with other sources\n\n5.1 Electricity\n\nEstimated total electricity consumption from the meter point data differs from Chapter 5 of the Digest of UK Energy Statistics (DUKES) as DUKES data are based on sales information collected from two separate annual surveys, one of major power producers and one of electricity suppliers\\(^{25}\\). It is recommended for DUKES data to be used for headline analysis, and sub-national data to be used for regional analysis.\n\nTable 8 below compares the total consumption based on meter points to the corresponding DUKES total.\n\n**Table 8: Comparison with published UK statistics for 2014**\n\n| Total final consumption (UK) | GWh |\n|-----------------------------|-----|\n| Great Britain total consumption from meter point data | |\n| Domestic | 109,170 |\n| Non-domestic | 186,150 |\n| | 295,320 |\n| Implied UK total consumption | |\n| Great Britain total consumption (above) | 295,320 |\n| Plus Northern Ireland\\(^1\\) | 7,807 |\n| Plus Sales direct from high voltage lines (based on Ofgem data)\\(^2\\) | 3,879 |\n| Implied UK sales of electricity | 307,006 |\n| DUKES total UK sales (DUKES 2015 Table 5.4) | 291,101 |\n| Statistical difference | -15,905 |\n\n\\(^1\\) Northern Ireland data are based on data for electricity distributed provided by Northern Ireland Electricity.\n\n\\(^2\\) Based on estimates provided by Ofgem.\n\nAfter taking into account consumption not included in the sub-national estimates (total consumption for Northern Ireland and sales from high voltage lines) there was a statistical difference of 15,905 GWh, -5 per cent of total UK sales reported in DUKES.\n\nOne of the main factors behind this difference is that the non-half hourly data covers the period from the start of February 2014 to the end of January 2015 and not the calendar year 2014 as covered by DUKES. Some of this difference may also be explained by the fact that approximately 20 per cent of the data in the sub-national exercise are based on estimated rather than actual meter readings, and some further meters will have been estimated by suppliers. Therefore the sub-national totals may not reflect the full scale of changes in consumption between years.\n\nA comparison with the average annual consumption per household published in *Energy Consumption in the UK* (ECUK) Table 3.07 (and based on data from DUKES Table 1.1.5) also shows that the trend over time is consistent for the two sources, see Chart 13.\n\n\\(^{25}\\) Detailed electricity figures available in DUKES can be accessed here: [https://www.gov.uk/government/organisations/department-of-energy-climate-change/series/electricity-statistics](https://www.gov.uk/government/organisations/department-of-energy-climate-change/series/electricity-statistics).\n\n5.2 Gas\n\nDECC publish estimates of gas consumption in other sources, which can be used to derive estimates of average domestic gas consumption as published in ECUK Table 3.07 (derived from DUKES Table 1.1.5). Table 9 below contains estimates between 2008 and 2014. These sources include:\n\nWeather correction factors and temperature adjustments can cause variability between the estimates and Table 9 below also contain data for average external temperatures during the heating season (defined as January to March and October to December), for both calendar years and the gas year (October to March).\n\nTable 9: Average domestic gas consumption (kWh) and heating season external temperatures (Celsius), 2008 to 2014\n\n| | 2008 | 2009 | 2010 | 2011 | 2012 | 2013 | 2014 |\n|----------------------|--------|--------|--------|--------|--------|--------|--------|\n| **ECUK 3.07**<sup>1</sup> (UK, Calendar year, non-weather corrected basis) | 16,546 | 15,767 | 17,774 | 13,252 | 15,551 | 15,373 | 12,404 |\n| **ECUK 3.07**<sup>1</sup> (UK, Calendar year, weather corrected basis) | 16,967 | 16,214 | 15,573 | 14,968 | 15,488 | 14,728 | 14,263 |\n| **Sub-national statistics** (October [y-1] to September, weather corrected basis) | 16,906 | 15,383 | 15,156 | 14,205 | 14,076 | 13,680 | 13,246 |\n| **Average Temperature**<sup>2</sup> (January to March, October to December) | 6.4 | 6.3 | 4.3 | 7.5 | 6.6 | 5.9 | 7.6 |\n| **Average Temperature**<sup>2</sup> (October [y-1] to March) | 6.9 | 5.9 | 5.6 | 5.4 | 7.7 | 5.2 | 7.5 |\n\n<sup>1</sup> Table 3.07, *Energy Consumption in the UK* ([https://www.gov.uk/government/statistics/energy-consumption-in-the-uk](https://www.gov.uk/government/statistics/energy-consumption-in-the-uk))\n\n<sup>2</sup> Table 7.1: *Average temperatures and deviations from the long term mean* ([https://www.gov.uk/government/statistics/energy-trends-section-7-weather](https://www.gov.uk/government/statistics/energy-trends-section-7-weather))\n\nThe table shows that – in broad terms – the data series are consistent, which provides reassurances to users of the sub-national data provided here.\n\nThere are differences in average temperature depending upon whether the calendar or gas year is used. Based on the heating season associated with the gas year, 2014 had the highest average temperature of any year shown in the table. As the sub-national estimates are weather corrected the impact of the temperature on household consumption should be eliminated from the time series. The impact of temperature on average consumption can be seen more clearly when comparing the ECUK non-weather corrected data with the calendar year temperature. The lowest average temperature (4.3) occurs in 2010 the same year as the highest average consumption (17,800 kWh).\n\n6. Developments and future plans\n\n6.1 Developments during the year\n\nBased on the previous feedback received from users we have continued to make changes to the suite of sub-national electricity and gas consumption statistics. The changes made are summarised below:\n\n- **Publication of MSOA and LSOA estimates in January 2016**\n \n Previously, LA estimates have been published in December and MSOA and LSOA estimates the following March. For 2013 consumption, MSOA and LSOA estimates were published on 29 January 2015, bringing the release date forward by two months. The 2014 MSOA and LSOA statistics will be published on 28 January 2016.\n\n- **Postcode level electricity and gas consumption statistics.**\n\n At the end of March 2015, DECC published 2013 experimental statistics on domestic gas and electricity consumption at postcode level. These can be found on here [https://www.gov.uk/government/collections/sub-national-electricity-consumption-data](https://www.gov.uk/government/collections/sub-national-electricity-consumption-data) (electricity) and [https://www.gov.uk/government/collections/sub-national-gas-consumption-data](https://www.gov.uk/government/collections/sub-national-gas-consumption-data) (gas). If you have any feedback on these statistics, please contact us at the email address given below, since this will determine whether this becomes part of the longer term regular publications.\n\n- **Interactive Off-gas map**\n\n DECC recently completed analysis with AWS and Kiln to underpin a map showing properties off the gas grid. The map helps to identify the location of off-gas grid properties, their distances from the gas network and the typical characteristics of properties within that area. The map can be accessed here [https://www.nongasmap.org.uk/](https://www.nongasmap.org.uk/).\n\n- **Cartogram Maps**\n\n DECC have also developed some cartogram maps to display average domestic electricity and gas consumption. The size of each local authority area has been adjusted according to its population (map 2 and map 5). This can help interpretation as it prevents densely populated areas being underrepresented. For example, London accounts for 15 per cent England’s population, but only 1.2 per cent of land area; the cartogram expands the area of London to account for this.\n\n6.2 Future plans\n\n- **Electricity and gas consumption data published by 10 kWh bandings.**\n\n A dataset showing number of electricity and gas meters in each 10kWh band has previously been supplied to Ofgem to support its review of typical domestic consumption values.\\(^{26}\\) Given DECC’s awareness of the interest in the distribution of consumption by a wider group of users it is intended that this dataset will be created again for 2013 and 2014 consumption and published on the DECC website.\n\n---\n\n\\(^{26}\\) The Review of typical domestic consumption values (Ofgem) can be accessed here: [https://www.ofgem.gov.uk/ofgem-publications/74735/tdcv-review-consultation.pdf](https://www.ofgem.gov.uk/ofgem-publications/74735/tdcv-review-consultation.pdf)\n\nGas and Electricity Infographics\n\nIn line with the publication of the 2014 MSOA and LSOA estimates, DECC will also be publishing a set of infographics to aid user understanding of the sub-national consumption estimates. If you have comments or feedback on these outputs, please contact us on the email address below.\n\nIf you have comments or feedback regarding any of the above proposals or any additional comments/suggestions, these can be sent to: email@example.com.\n\nWe periodically update our users relating to publication releases and changes made to datasets. If you are interested in being added to the sub-national statistics mailing list, please send a request to the email address above.\n\n## Annex A: Highest and lowest local authority averages, 2014\n\n### Electricity 2014, domestic and non-domestic highest and lowest consuming local authorities\n\n| Local Authority | Domestic | | | |\n|----------------------------------|----------|----------|----------|----------|\n| | Number of MPANs (thousands) | Sales (GWh) | Averages domestic consumption (KWh) |\n| Northumberland UA | 151 | 578 | 3,832 |\n| South Tyneside | 70 | 221 | 3,140 |\n| NORTH EAST | 1,198 | 4,096 | 3,418 |\n| Eden | 25 | 127 | 5,140 |\n| Barrow-in-Furness | 33 | 113 | 3,411 |\n| NORTH WEST | 3,158 | 12,029 | 3,809 |\n| Ryedale | 25 | 112 | 4,497 |\n| Kingston upon Hull, City of UA | 118 | 393 | 3,316 |\n| YORKSHIRE AND THE HUMBER | 2,349 | 8,642 | 3,679 |\n| Daventry | 34 | 166 | 4,902 |\n| Chesterfield | 49 | 162 | 3,328 |\n| EAST MIDLANDS | 2,005 | 7,783 | 3,881 |\n| Stratford-on-Avon | 55 | 274 | 5,035 |\n| Stoke-on-Trent UA | 112 | 385 | 3,434 |\n| WEST MIDLANDS | 2,392 | 9,540 | 3,988 |\n| Uttlesford | 34 | 175 | 5,105 |\n| Norwich | 64 | 207 | 3,208 |\n| EAST ENGLAND | 2,577 | 11,042 | 4,284 |\n| Barnet | 144 | 634 | 4,410 |\n| Islington | 101 | 325 | 3,208 |\n| LONDON | 3,449 | 13,201 | 3,828 |\n| South Bucks | 28 | 149 | 5,286 |\n| Portsmouth UA | 90 | 322 | 3,591 |\n| SOUTH EAST | 3,761 | 16,149 | 4,294 |\n| Isles of Scilly UA | 1 | 8 | 6,610 |\n| Weymouth and Portland | 32 | 113 | 3,565 |\n| SOUTH WEST | 2,467 | 10,383 | 4,209 |\n| Ceredigion | 33 | 162 | 4,855 |\n| Blaenau Gwent | 32 | 105 | 3,263 |\n| WALES | 1,389 | 5,189 | 3,735 |\n| Shetland Islands | 17 | 103 | 5,946 |\n| Glasgow City | 329 | 1,068 | 3,251 |\n| SCOTLAND | 2,760 | 10,805 | 3,915 |\n| Unallocated | 105 | 310 | 2,962 |\n| GREAT BRITAIN | 27,611 | 109,170 | 3,954 |\n\n| Local Authority | Non-domestic | | | |\n|----------------------------------|--------------|----------|----------|----------|\n| | Number of MPANs (thousands) | Sales (GWh) | Averages non-domestic consumption (KWh) |\n| Redcar and Cleveland UA | 4 | 859 | 231,281 |\n| Darlington | 4 | 201 | 56,848 |\n| NORTH EAST | 82 | 7,479 | 90,810 |\n| Knowsley | 3 | 551 | 191,278 |\n| Copeland | 3 | 120 | 43,569 |\n| NORTH WEST | 241 | 20,582 | 85,494 |\n| North Lincolnshire UA | 6 | 961 | 160,146 |\n| Craven | 4 | 155 | 42,582 |\n| YORKSHIRE AND THE HUMBER | 182 | 15,298 | 84,102 |\n| Rutland | 2 | 315 | 175,205 |\n| Rushcliffe | 3 | 158 | 48,616 |\n| EAST MIDLANDS | 161 | 13,696 | 85,069 |\n| Telford and Wrekin | 5 | 921 | 168,512 |\n| Malvern Hills | 3 | 153 | 44,854 |\n| WEST MIDLANDS | 199 | 16,028 | 80,557 |\n| Thurrock, UA | 4 | 653 | 149,357 |\n| Tendring | 5 | 218 | 40,466 |\n| EAST ENGLAND | 220 | 15,927 | 72,315 |\n| City of London | 7 | 2,304 | 343,603 |\n| Lewisham | 16 | 523 | 33,573 |\n| LONDON | 398 | 28,201 | 70,809 |\n| Slough UA | 4 | 662 | 148,847 |\n| Rother | 5 | 144 | 31,468 |\n| SOUTH EAST | 334 | 22,034 | 66,008 |\n| Swindon UA | 6 | 802 | 132,583 |\n| Torridge | 5 | 141 | 30,998 |\n| SOUTH WEST | 252 | 14,879 | 59,084 |\n| Neath Port Talbot | 4 | 1,527 | 373,519 |\n| Powys | 11 | 386 | 35,275 |\n| WALES | 126 | 11,262 | 89,095 |\n| West Lothian | 5 | 588 | 111,421 |\n| Orkney Islands | 2 | 68 | 29,542 |\n| SCOTLAND | 217 | 16,026 | 73,712 |\n| Unallocated | 24 | 4,737 | 201,441 |\n| GREAT BRITAIN | 2,436 | 186,150 | 76,402 |\n\n## Gas 2014, domestic and non-domestic highest and lowest consuming local authorities\n\n| Local Authority | Domestic | | | |\n|----------------------------------|----------|----------|----------|----------|\n| | Number of MPANs (thousands) | Sales (GWh) | Averages domestic consumption (KWh) |\n| Northumberland UA | 118 | 1,648 | 14,018 |\n| Middlesbrough UA | 58 | 751 | 12,921 |\n| NORTH EAST | 1,096 | 14,790 | 13,489 |\n| Ribble Valley | 21 | 318 | 15,511 |\n| Knowsley | 63 | 704 | 11,231 |\n| NORTH WEST | 2,893 | 37,508 | 12,966 |\n| Harrogate | 57 | 899 | 15,821 |\n| Kingston upon Hull, City of UA | 111 | 1,278 | 11,473 |\n| YORKSHIRE AND THE HUMBER | 2,115 | 28,898 | 13,663 |\n| Rushcliffe | 44 | 694 | 15,798 |\n| Lincoln | 41 | 479 | 11,781 |\n| EAST MIDLANDS | 1,759 | 23,774 | 13,513 |\n| Bromsgrove | 36 | 561 | 15,477 |\n| Worcester | 40 | 469 | 11,654 |\n| WEST MIDLANDS | 2,102 | 27,872 | 13,263 |\n| Three Rivers | 34 | 577 | 17,075 |\n| Norwich | 58 | 633 | 10,874 |\n| EAST OF ENGLAND | 2,056 | 27,576 | 13,411 |\n| Harrow | 82 | 1,405 | 17,049 |\n| Tower Hamlets | 77 | 704 | 9,110 |\n| LONDON | 3,015 | 39,850 | 13,218 |\n| South Bucks | 26 | 502 | 19,562 |\n| Portsmouth UA | 79 | 825 | 10,488 |\n| SOUTH EAST | 3,188 | 43,539 | 13,655 |\n| East Dorset | 33 | 494 | 14,818 |\n| Plymouth UA | 107 | 1,030 | 9,662 |\n| SOUTH WEST | 1,840 | 21,639 | 11,763 |\n| Merthyr Tydfil | 26 | 358 | 13,762 |\n| Gwynedd | 30 | 333 | 11,194 |\n| WALES | 1,118 | 14,002 | 12,527 |\n| East Renfrewshire | 34 | 640 | 18,570 |\n| Glasgow City | 248 | 2,829 | 11,427 |\n| SCOTLAND | 1,986 | 27,549 | 13,872 |\n| Unallocated | 72 | 837 | 11,640 |\n| GREAT BRITAIN | 23,239 | 307,832 | 13,246 |\n\n| Local Authority | Non-domestic | | | |\n|----------------------------------|--------------|----------|----------|----------|\n| | Number of MPANs (thousands) | Sales (GWh) | Averages non-domestic consumption (KWh) |\n| Darlington UA | 0.49 | 988 | 776,812 |\n| South Tyneside | 0.59 | 345 | 570,769 |\n| NORTH EAST | 11.36 | 8,323 | 733,018 |\n| Eden | 0.14 | 251 | 962,201 |\n| Copeland | 0.23 | 636 | 1,489,861|\n| NORTH WEST | 30.68 | 26,257 | 855,748 |\n| Selby | 0.20 | 469 | 503,076 |\n| Craven | 0.29 | 1,058 | 867,036 |\n| YORKSHIRE AND THE HUMBER | 23.78 | 22,847 | 960,758 |\n| Corby | 0.34 | 554 | 1,310,534|\n| Qadby and Wigston | 0.30 | 351 | 731,062 |\n| EAST MIDLANDS | 18.63 | 14,130 | 758,535 |\n| Stoke-on-Trent UA | 1.10 | 130 | 302,925 |\n| Malvern Hills | 0.27 | 222 | 471,899 |\n| WEST MIDLANDS | 23.46 | 17,339 | 739,140 |\n| King’s Lynn and West Norfolk | 0.40 | 128 | 258,558 |\n| Three Rivers | 0.50 | 497 | 642,995 |\n| EAST OF ENGLAND | 22.17 | 15,838 | 714,334 |\n| Bexley | 0.63 | 377 | 421,784 |\n| Barnet | 2.06 | 731 | 591,189 |\n| LONDON | 41.69 | 21,309 | 511,108 |\n| Gravesham | 0.25 | 319 | 498,553 |\n| Tandridge | 0.54 | 397 | 492,879 |\n| SOUTH EAST | 39.21 | 18,750 | 478,169 |\n| West Somerset | 0.08 | 62 | 238,226 |\n| East Dorset | 0.26 | 436 | 526,948 |\n| SOUTH WEST | 19.33 | 11,688 | 604,677 |\n| Wrexham | 0.47 | 125 | 563,432 |\n| Conwy | 0.56 | 175 | 398,627 |\n| WALES | 10.50 | 9,287 | 884,357 |\n| Moray | 0.38 | 97 | 260,618 |\n| East Renfrewshire | 0.37 | 2,504 | 706,881 |\n| SCOTLAND | 23.76 | 20,501 | 862,904 |\n| Unallocated | 1.51 | 1,561 | 1,034,178|\n| GREAT BRITAIN | 266.08 | 187,829 | 705,920 |\n\nAnnex B: Sub-national consumption publications\n\nThis factsheet is part of a series of sub-national factsheets and datasets. Before using any of the datasets, it is highly advised to refer to the related chapter in the Sub-national methodology and guidance booklet: https://www.gov.uk/government/publications/regional-energy-data-guidance-note.\n\nElectricity consumption statistics\n\n- Electricity consumption statistics, including local authority level and super output area (Great Britain) and experimental local authority statistics for Northern Ireland: https://www.gov.uk/government/collections/sub-national-electricity-consumption-data.\n\nGas consumption statistics and estimates of household not connected to the gas network\n\n- Gas consumption statistics at local authority level super output area (Great Britain): https://www.gov.uk/government/organisations/department-of-energy-climate-change/series/sub-national-gas-consumption-data.\n\nRoad transport consumption statistics\n\n- Road transport consumption statistics at local authority level (United Kingdom): https://www.gov.uk/government/collections/road-transport-consumption-at-regional-and-local-level.\n\nResidual fuel (non-electricity, non-gas, non-road transport fuels) consumption statistics\n\n- Residual fuel consumption statistics at local authority level (United Kingdom): https://www.gov.uk/government/organisations/department-of-energy-climate-change/series/sub-national-consumption-of-other-fuels.\n\nTotal final energy consumption statistics\n\n- Total final energy consumption statistics at local authority level (Great Britain): https://www.gov.uk/government/organisations/department-of-energy-climate-change/series/total-final-energy-consumption-at-sub-national-level.\n\nAnnex C: Tools available to analyse sub-national consumption statistics\n\nDECC has published tools to aid the user to further explore the data:\n\n1. **Sub-national electricity and gas consumption statistics analytical tool**\n This tool has been created for analysing electricity and gas consumption at the local authority level, and has been produced to help local authorities and other regional bodies use DECC’s sub-national gas and electricity data to better understand changes in consumption over time. The tool allows for three distinct types of analysis:\n - Analysis of individual local authority data in comparison to its respective regional average and the Great Britain average;\n - Comparison between a selected local authority and five additional local authorities;\n - Change between all local authorities in Great Britain.\n\n The tool can be accessed at: [https://www.gov.uk/government/collections/analytical-tools](https://www.gov.uk/government/collections/analytical-tools).\n\n2. **Look-up spreadsheets**\n The look-up spreadsheets are published alongside the SOA datasets, and are aimed at users interested in which SOA codes are included in a local authority, or for users who would like to determine which NUTS4 corresponds to which local authority. The spreadsheet also collates annual consumption (kWh), the number of meters and average consumption (kWh) for each SOA, or LA of interest.\n\n The MSOA and LSOA look-up spreadsheets can be found alongside the latest published data available via this page: [https://www.gov.uk/government/collections/sub-national-electricity-consumption-data](https://www.gov.uk/government/collections/sub-national-electricity-consumption-data) (electricity) and [https://www.gov.uk/government/organisations/department-of-energy-climate-change/series/sub-national-gas-consumption-data](https://www.gov.uk/government/organisations/department-of-energy-climate-change/series/sub-national-gas-consumption-data) (gas)\n\nAnnex D: An illustration of LSOA areas within an MSOA\n\nThe map below shows an example of LSOA areas within an MSOA in the local authority of Crawley. The black outline represents the MSOA and the individual codes represent LSOA areas within this MSOA.\n\nFor further information about locating SOA codes of interest, please refer to Annex A of the Methodology and guidance booklet available online:\n\nhttps://www.gov.uk/government/publications/regional-energy-data-guidance-note.\n\n© Crown copyright 2015\n\nDepartment of Energy & Climate Change\n\n3 Whitehall Place\nLondon SW1A 2AW\n\nwww.gov.uk/decc\n\n15D/549"},"books_score":{"kind":"number","value":0.41671404242515564,"string":"0.416714"}}},{"rowIdx":8698,"cells":{"content":{"kind":"string","value":"DWS GROUP – Q3 2021 RESULTS\n\nOctober 27, 2021\n\nCONTINUED STRONG BUSINESS MOMENTUM\n\nRecord results in Q3, underpinning strong client engagement\n\nRECAP: PHASE TWO\n\n- Invest into transformation for further efficiency and targeted growth\n\nFY 2020\n\n- Differentiated leadership: ESG, Passive, high margin strategies\n- Take active role in M&A activities\n\nKEY ACHIEVEMENTS Q3 2021\n\nFinancials\n\n- Net inflows of €12bn overall (positive Active, Passive & Alternatives); September net flows of €5bn reflecting strong ongoing client engagement\n- Adj. CIR improved to record low of 59.2%\n- Adj. PbT of €271m at record high level reflecting higher revenues driven by record AUM\n\nDifferentiated leadership\n\n- ESG: €5bn net flows into ESG products¹, became one of the signatories to the \"UK Stewardship Code 2020\"²\n- Passive: strong net flows of €7bn, #2 in European ETP³ flows & AuM\n- High margin strategies: attracted net flows, with continued flows into flagship fund DWS Concept Kaldemorgen\n- M&A activities: partnership with BlackFin Capital Partners, acquisition of minority stake in UK-based retiretech provider Smart Pension\n\nTRANSFORM, GROW AND LEAD\n\n¹ See Cautionary Statement for ESG classification explanation ² Issued by DWS Investments UK Limited (DWS UK) ³ Source: ETFGI\n\nQ3 2021 KEY FINANCIAL HIGHLIGHTS\n\nStrong revenue generation supports profit growth\n\n– Strong quarter with record adjusted profit before tax of €271m driven by record AuM\n\n– Adjusted cost income ratio decreased further to 59.2% in Q3\n\n– Net flows of €12bn and €10bn ex Cash in Q3 in line with our medium-term target, including €5bn net flows into ESG products\n\nFINANCIAL PERFORMANCE SNAPSHOT – Q3 2021\n\nStrong business momentum continues\n\nAUM (€BN)\n\nNet flows (€bn)\n- Q3-20: 10.5\n- Q2-21: 19.7\n- Q3-21: 12.0\n\nNet flows ex Cash (€bn)\n- Q3-20: 6.2\n- Q2-21: 14.2\n- Q3-21: 10.0\n\nAdjusted Revenues (€M)\n\nManagement fee margin (bps)\n- Q3-20: 27.8\n- Q2-21: 28.1\n- Q3-21: 27.6\n\nAdjusted Costs (€M)\n\nAdjusted CIR (%)\n- Q3-20: 61.4\n- Q2-21: 60.6\n- Q3-21: 59.2\n\nAdjusted Profit before Tax (€M)\n\n- Q3-20: 215\n- Q2-21: 247\n- Q3-21: 271\n\nNote: Throughout this presentation totals may not sum due to rounding differences\n\nMARKET ENVIRONMENT\n\nFavourable €/$ exchange rate development supports AuM growth in Q3\n\nEQUITIES (%)\n\n- S-DAX\n- DAX\n- MSCI World\n- Eurostoxx 50\n\nFX (€/$)\n\nVOLATILITY (VIX INDEX)\n\nINTEREST RATES, YIELD (%)\n\n10Y Bund\n10Y Treasury\nBarclays Global Aggregate\n30Y Euro Swap\n\nSource: Bloomberg\n\nDWS Group\nInvestor Relations\nQ3 2021 results\nOctober 27, 2021\n\nAUM DEVELOPMENT\n\nDWS’ AuM level continues to increase reaching record level\n\nAUM DEVELOPMENT DETAIL (€BN)\n\n- FY 2020: 793\n - Net flows: 1\n - FX: 13\n - Market impact: 13\n - Other: 1\n - Total: 820\n\n- Q1 2021: 820\n - Net flows: 20\n - FX: (3)\n - Market impact: 22\n - Other: 0\n - Total: 859\n\n- Q2 2021: 859\n - Net flows: 12\n - FX: 8\n - Market impact: 0\n - Other: 1\n - Total: 880\n\nQ3 HIGHLIGHTS\n\nAuM increased by €21bn to €880bn in Q3\n- Main drivers have been net flows and favourable €/$ exchange rate development\n\n1 Represents FX impact from non-Euro denominated products; excludes performance impact from FX\n\n## Q3 2021 NET FLOWS\n\n**Strong net flows driven by targeted asset classes and ESG**\n\n### NET FLOWS BREAKDOWN\n\n| By asset class (€bn) | Q3-20 | Q2-21 | Q3-21 |\n|----------------------|-------|-------|-------|\n| Active Equity | (1.1) | (0.3) | (0.6) |\n| Active Multi Asset | (1.2) | 2.0 | 1.1 |\n| Active SQI¹ | (1.0) | 1.1 | 0.7 |\n| Active Fixed Income | 2.5 | 1.7 | 0.8 |\n| Passive | 6.3 | 7.9 | 6.6 |\n| Alternatives | 0.8 | 1.8 | 1.4 |\n| **Total ex Cash** | 6.2 | 14.2 | 10.0 |\n| **Cash** | 4.3 | 5.4 | 1.9 |\n| **Total** | 10.5 | 19.7 | 12.0 |\n\n### AUM BY ASSET CLASS\n\n- Passive: 25%\n- Active Multi Asset: 8%\n- Cash: 9%\n- Active Equity: 12%\n- Active Fixed Income: 26%\n- Active SQI¹: 9%\n- Alternatives: 12%\n\n### AUM BY REGION & CLIENT TYPE\n\n- Germany: 44%\n- APAC: 5%\n- Americas: 25%\n- EMEA (ex Germany): 26%\n- Institutional: 55%\n- Retail: 45%\n\n### Q3 HIGHLIGHTS\n\n- Net flows of €12bn in Q3 including €5bn of net flows into ESG products\n- 66% of net flows came from retail distribution channels\n- September with €5bn net flows reflecting strong client engagement\n- Passive continued strong inflows into ETFs as well as institutional mandates\n- Alternatives primarily driven by inflows into US and German Liquid Real Asset funds\n- Multi Asset with continued inflows into Concept Kaldemorgen as well as strong institutional demand\n- Equity outflows affected by uncertainties around economic outlook as well as flagship fund performance, but strong flows into ESG products\n\n---\n\n¹ Systematic and Quantitative Investments\n\nPOSITIVE CONTRIBUTION OF NEW FUND LAUNCHES\n\nNew funds attract strong net flows in Passive, Alternatives & ESG products\n\nCUMULATIVE FLOWS OF NEW FUNDS SINCE IPO (IN €BN)\n\nOverall management fee margin of new funds (bps) ~40\n\nCumulative flows by asset class as of Q3 2021\n\n€37.3n\n\nActive Fixed Income 7%\nActive Equity 5%\nActive SQI 1%\nActive Multi Asset 9%\n\nPassive 57%\nAlternatives 20%\n\nDec-19 Dec-20 Mar-21 Jun-21 Sep-21\n\nTotal cumulative net flows\nNon-ESG products\nESG products¹\n\nQ4 2021 FUND LAUNCHES PIPELINE² EXAMPLES\n\n– DWS Invest ESG NextGen Consumer Equity\n\n– Xtrackers ESG Global Government Bond UCITS ETF\n\nCOMMENTARY\n\n– Focus on SFDR fund conversion\n– Strong fund launch pipeline for 2022\n\nNote: Not all DWS products and services are offered in all jurisdictions and availability is subject to local regulatory restrictions and requirements\n¹ See Cautionary Statement for ESG classification explanation\n² Subject to demand assessments, approvals and successful transaction execution\n\nManagement fees continue to increase reaching highest level since IPO\n\n**ADJUSTED REVENUES (€M)**\n\n- **Other revenues**\n- **Performance and transaction fees**\n- **Management fees and other recurring revenues**\n\n| Quarter | Other revenues | Performance and transaction fees | Management fees and other recurring revenues |\n|---------|----------------|----------------------------------|---------------------------------------------|\n| Q3-20 | 27.8 | 15 | 523 |\n| Q2-21 | 28.1 | 19 | 584 |\n| Q3-21 | 27.6 | 23 | 608 |\n\n**EoP¹** \n- Q3-20: 759 \n- Q2-21: 859 \n- Q3-21: 880 \n\n**Avg²** \n- Q3-20: 750 \n- Q2-21: 835 \n- Q3-21: 873 \n\n**Management fee margin (bps)** \n- Q3-20: 27.8 \n- Q2-21: 28.1 \n- Q3-21: 27.6 \n\n**AuM (€bn)** \n- Q3-20: xx \n- Q2-21: xx \n- Q3-21: xx \n\n---\n\n**Q3 HIGHLIGHTS**\n\n- Total adjusted revenues increased 6% q-o-q to €664m\n- Management fees and other recurring revenues increased 4% q-o-q primarily due to favorable markets as well as positive net flows\n- Performance and transaction fees increased 45% q-o-q due to higher transaction fees\n- Other revenues supported by strong Harvest contribution and investment income\n\n---\n\n¹ End of period \n² Monthly average\n\nCOST DEVELOPMENT\n\nAdjusted cost base includes investments into growth & one-off cost items\n\nADJUSTED COSTS (€M)¹\n\n- Adjusted Compensation & Benefits\n- Adjusted General & Administrative Expenses\n\nQ3 HIGHLIGHTS\n\n- Total adjusted costs of €393m, up 4% q-o-q\n- Adjusted compensation & benefits decreased by 7% due to lower variable compensation\n- Adjusted general & administrative expenses increased due to investments into growth, non-recurring items as well as higher marketing & travel expenses\n- Adjusted cost base excludes €9m of investments into our infrastructure platform transformation\n\n1 Non-interest expenses adjusted for severance payments, restructuring activities, transformation charges and litigation\n\nCONCLUSION & FINANCIAL OUTLOOK 2022\n\nStrong performance, supportive markets and transformation progress accelerates YTD momentum\n\nCONCLUSION\n\nStrong performance\n\n- Strong net flows into targeted growth areas with increased demand for ESG products\n- Adjusted CIR improved further\n- Strong 3 and 5 year investment outperformance at 77% and 82% respectively\n\nStrategic priorities\n\n- Further investments into growth and transformation projects\n\nFINANCIAL OUTLOOK 2022\n\n- We expect the adjusted CIR to be in the low 60s% next year\n- Net flow target of >4% on average in the medium-term reiterated\n- Management fully committed to deliver on all aspirations for Phase two\n\nOUTLOOK\n\nDefined focus topics to expedite our transformation and achieve our ambition\n\nCONTINUE TO DELIVER...\n\nONGOING PROFITABILITY\n– Ensure transformational progress and operational strength, highlighted by high AuM and net flow levels\n\nADJUSTED COST-INCOME-RATIO\n– Follow clear path to sustainable adjusted CIR of 60% in 2024\n\nKEEP ESG COMMITMENT\n– Continue to attract and meet demand for existing and new ESG products\n\n…WHILE CONCENTRATING ON DEFINED FOCUS TOPICS\n\n– Continued execution of stand-alone AM with dedicated infrastructure platform\n\n– Further delivery of ESG capabilities to clients, external commitments (e.g. NZAM¹) and embedding of ESG into corporate DNA\n\n– Continued focus on organic growth in Passive\n\n– Further growth in high margin areas, e.g. thematic active and illiquid strategies\n\n– Expansion of partnerships to capture growth opportunities (esp. in APAC)\n\n– Execution of global brand partnership to raise awareness and visibility, and underpin growth strategy in key global markets\n\n¹ Net Zero Asset Managers initiative\n\nAppendix\n\nNEW TARGETS AND ASPIRATION\n\nReflecting our growth and profitability ambitions\n\nASPIRATION\n\nLEADING EUROPEAN ASSET MANAGER WITH GLOBAL REACH\n\nMEDIUM-TERM TARGETS¹ TO 2024\n\nAdj. CIR of 60%\n\nNet flows² >4%\n\n¹ Depending on market circumstances and €/$ FX rate\n² 2 % of BoP AuM on average in the medium-term\n\n## DWS DETAILED FINANCIALS\n\n### PROFIT & LOSS STATEMENT AND KEY PERFORMANCE INDICATORS (€M, UNLESS STATED OTHERWISE)\n\n| Profit & Loss | Q3 2021 | Q2 2021 | Q3 2020 |\n|----------------------------------------------------|---------|---------|---------|\n| Management fees and other recurring revenues | 608 | 584 | 523 |\n| Performance and transaction fees | 27 | 19 | 20 |\n| Other revenues | 29 | 23 | 15 |\n| **Net revenues** | 664 | 625 | 558 |\n| Revenue adjustments | - | - | - |\n| **Adjusted revenues** | 664 | 625 | 558 |\n| Adjusted Compensation & Benefits | 183 | 196 | 167 |\n| Adjusted General & administrative expenses | 210 | 183 | 175 |\n| **Adjusted cost base (excl. transformation charges)** | 393 | 379 | 342 |\n| Severance & Restructuring | 4 | 1 | 3 |\n| Transformation charges | 9 | 7 | (0) |\n| Other cost adjustments | 0 | 1 | (1) |\n| **Total noninterest expenses** | 405 | 387 | 345 |\n| **Profit before tax** | 259 | 239 | 213 |\n| **Adjusted profit before tax (excl. transformation charges)** | 271 | 247 | 215 |\n| **Net income** | 182 | 172 | 151 |\n\n| Other Key Performance Measures | | | |\n|----------------------------------------------------|---------|---------|---------|\n| **Reported CIR** | 61.1% | 61.9% | 61.9% |\n| **Adjusted CIR (excl. transformation charges)** | 59.2% | 60.6% | 61.4% |\n| FTE (#) | 3,394 | 3,342 | 3,290 |\n| AuM (in €bn) | 880 | 859 | 759 |\n| Net flows (in €bn) | 12.0 | 19.7 | 10.5 |\n| Net flows (% of BoP AuM – annualized) | 5.5% | 9.6% | 5.6% |\n| Management fee margin (bps - annualized) | 27.6 | 28.1 | 27.8 |\n\n| 9M 2021 vs Q2 2021 | 9M 2020 | Q3 2021 vs Q2 2021 | Q3 2021 vs Q3 2020 | 9M 2021 vs 9M 2020 |\n|--------------------|---------|---------------------|---------------------|---------------------|\n| 4% | 16% | 10% | 6% | 19% | 18% |\n| 45% | 38% | 50% | 26% | 94% | N/M |\n| 6% | 19% | 18% | (7)% | 9% | 12% |\n| 15% | 20% | 8% | 5% | 17% | 10% |\n| 580% | 18% | (64)% | 32% | N/M | N/M |\n| 32% | N/M | N/M | 10% | 26% | 31% |\n| 6% | 20% | 32% | 61.8% | 65.9% | (0.8)ppt |\n| 2% | 3% | 3% | 60.1% | 64.3% | (1.4)ppt |\n| 2% | 16% | 16% | 5.5% | 2.9% | (0.8)ppt |\n| 27.9 | 28.3 | 27.9 | 28.3 | 28.3 | (4.1)ppt |\n\n## RECONCILIATION FROM IFRS TO ECONOMIC VIEW\n\n### BALANCE SHEET AS OF SEPTEMBER 30, 2021 (€BN)\n\n| Assets | IFRS consolidated | Consolidated Funds | DB Vita | Held for Sale | Economic View |\n|---------------------------------------------|-------------------|--------------------|---------|---------------|---------------|\n| Cash and bank balances | 2,163 | | | | 2,163 |\n| Financial assets at FVPL | 3,452 | 1,284 | 557 | | 1,611 |\n| Financial assets at OCI | 167 | | | | 167 |\n| Other investments | 353 | | | | 353 |\n| Property and equipment | 144 | | | | 144 |\n| Tax assets | 162 | | | | 162 |\n| Intangible assets | 3,603 | | | | 3,603 |\n| Other assets | 1,225 | | 559 | | 666 |\n| **Total assets** | **11,268** | **1,284** | **557** | **559** | **8,868** |\n\n| Liabilities | IFRS consolidated | Consolidated Funds | DB Vita | Held for Sale | Economic View |\n|---------------------------------------------|-------------------|--------------------|---------|---------------|---------------|\n| Other short-term borrowings | 76 | | | | 76 |\n| Tax liabilities | 280 | | | | 280 |\n| Financial liabilities at FVPL | 747 | 557 | | | 189 |\n| Other liabilities | 3,065 | 1,284 | 559 | | 1,222 |\n| **Total liabilities** | **4,167** | **1,284** | **557** | **559** | **1,767** |\n\n| Equity | | | | | |\n|---------------------------------------------|-------------------|--------------------|---------|---------------|---------------|\n| **Total liabilities and equities** | **11,268** | **1,284** | **557** | **559** | **8,868** |\n\n### HIGHLIGHTS\n\n€2.4bn adjustments comprise:\n\n1. **Consolidated Funds (€1.3bn)**\n - DWS reports individual assets and liabilities of mainly guaranteed funds that it controls under IFRS 10\n - Fund assets and P&L still belong solely to the investors, not DWS\n - DWS does not consolidate where third party investors hold > 50% of units\n\n2. **DB Vita (€0.6bn)**\n - Investment contract related financial assets held to back unit linked contracts offered by DB Vita S.A. (which is our specialist entity for unit-linked insurance products)\n - Offset with financial liabilities due to investors holding the unit linked insurance contracts\n\n3. **Held for sale (€0.6bn)**\n - Assets and liabilities related to the transfer of our digital investment platform into a joint venture as long-term strategic partnership with DWS maintaining a stake of 30 percent only\n - The transaction is still subject to the approval of the relevant authorities and closing of the transaction is expected for the second half of 2022\n\n## Historical Net Flows and AUM Development\n\n### IN €BN\n\n#### Net flows by asset class\n\n| Asset Class | FY 2019 | Q1 2020 | Q2 2020 | Q3 2020 | Q4 2020 | FY 2020 | Q1 2021 | Q2 2021 | Q3 2021 |\n|----------------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|\n| Active Equity | (1.6) | 1.7 | 1.0 | (1.1) | 0.2 | 1.8 | 0.1 | (0.3) | (0.6) |\n| Active Multi Asset | 7.2 | (0.7) | (0.6) | (1.2) | 0.8 | (1.8) | (0.5) | 2.0 | 1.1 |\n| Active SQI | 1.5 | (1.5) | (0.2) | (1.0) | (0.4) | (3.1) | 0.6 | 1.1 | 0.7 |\n| Active Fixed Income | (7.8) | (5.1) | (4.4) | 2.5 | 0.1 | (6.8) | 1.0 | 1.7 | 0.8 |\n| Active Cash | (2.5) | 3.6 | 6.3 | 4.3 | 5.3 | 19.5 | (8.6) | 5.4 | 1.9 |\n| Passive | 19.1 | (2.0) | 6.5 | 6.3 | 5.9 | 16.6 | 7.4 | 7.9 | 6.6 |\n| Alternatives | 10.2 | 1.5 | 0.0 | 0.8 | 1.7 | 4.0 | 1.0 | 1.8 | 1.4 |\n| **DWS Group** | 26.1 | (2.5) | 8.7 | 10.5 | 13.6 | 30.3 | 1.0 | 19.7 | 12.0 |\n\n#### AuM by asset class\n\n| Asset Class | FY 2019 | Q1 2020 | Q2 2020 | Q3 2020 | Q4 2020 | FY 2020 | Q1 2021 | Q2 2021 | Q3 2021 |\n|----------------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|\n| Active Equity | 96 | 79 | 91 | 91 | 97 | 97 | 105 | 110 | 110 |\n| Active Multi Asset | 58 | 53 | 55 | 55 | 59 | 59 | 60 | 64 | 67 |\n| Active SQI | 71 | 63 | 66 | 67 | 69 | 69 | 71 | 74 | 75 |\n| Active Fixed Income | 234 | 217 | 219 | 221 | 220 | 220 | 221 | 223 | 225 |\n| Active Cash | 57 | 64 | 69 | 71 | 75 | 75 | 68 | 73 | 76 |\n| Passive | 156 | 133 | 154 | 161 | 179 | 179 | 197 | 213 | 221 |\n| Alternatives | 96 | 91 | 92 | 92 | 93 | 93 | 99 | 103 | 107 |\n| **DWS Group** | 767 | 700 | 745 | 759 | 793 | 793 | 820 | 859 | 880 |\n\n#### Net flows by region\n\n| Region | FY 2019 | Q1 2020 | Q2 2020 | Q3 2020 | Q4 2020 | FY 2020 | Q1 2021 | Q2 2021 | Q3 2021 |\n|----------------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|\n| Americas | 3.5 | 1.8 | (2.5) | 8.0 | 1.6 | 8.8 | (3.3) | 5.5 | 4.5 |\n| EMEA excl. GY | 6.5 | (2.0) | 9.5 | (2.1) | 6.7 | 12.1 | (0.9) | 4.1 | 3.7 |\n| Germany (GY) | 13.6 | (0.9) | 0.9 | 3.0 | 4.5 | 7.5 | 3.9 | 9.9 | 4.3 |\n| Asia Pacific | 2.4 | (1.2) | 0.7 | 1.6 | 0.8 | 1.9 | 1.3 | 0.2 | (0.5) |\n| **DWS Group** | 26.1 | (2.5) | 8.7 | 10.5 | 13.6 | 30.3 | 1.0 | 19.7 | 12.0 |\n\n#### AuM by region\n\n| Region | FY 2019 | Q1 2020 | Q2 2020 | Q3 2020 | Q4 2020 | FY 2020 | Q1 2021 | Q2 2021 | Q3 2021 |\n|----------------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|\n| Americas | 199 | 194 | 195 | 199 | 198 | 198 | 203 | 211 | 220 |\n| EMEA excl. GY | 191 | 168 | 202 | 192 | 206 | 206 | 211 | 221 | 227 |\n| Germany (GY) | 335 | 302 | 308 | 328 | 346 | 346 | 361 | 380 | 386 |\n| Asia Pacific | 41 | 37 | 40 | 41 | 43 | 43 | 46 | 47 | 46 |\n| **DWS Group** | 767 | 700 | 745 | 759 | 793 | 793 | 820 | 859 | 880 |\n\n#### Net flows by client channel\n\n| Client Channel | FY 2019 | Q1 2020 | Q2 2020 | Q3 2020 | Q4 2020 | FY 2020 | Q1 2021 | Q2 2021 | Q3 2021 |\n|----------------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|\n| Retail | 5.1 | (0.4) | 5.0 | 2.1 | 4.7 | 11.4 | 5.1 | 11.2 | 7.9 |\n| Institutional | 21.0 | (2.1) | 3.7 | 8.5 | 8.9 | 18.9 | (4.1) | 8.5 | 4.1 |\n| **DWS Group** | 26.1 | (2.5) | 8.7 | 10.5 | 13.6 | 30.3 | 1.0 | 19.7 | 12.0 |\n\n#### AuM by client channel\n\n| Client Channel | FY 2019 | Q1 2020 | Q2 2020 | Q3 2020 | Q4 2020 | FY 2020 | Q1 2021 | Q2 2021 | Q3 2021 |\n|----------------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|\n| Retail | 335 | 292 | 319 | 325 | 343 | 343 | 363 | 386 | 396 |\n| Institutional | 433 | 408 | 426 | 434 | 449 | 449 | 457 | 473 | 484 |\n| **DWS Group** | 767 | 700 | 745 | 759 | 793 | 793 | 820 | 859 | 880 |\n\n#### Total net flows\n\n| Component | FY 2019 | Q1 2020 | Q2 2020 | Q3 2020 | Q4 2020 | FY 2020 | Q1 2021 | Q2 2021 | Q3 2021 |\n|----------------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|\n| Total net flows | 26.1 | (2.5) | 8.7 | 10.5 | 13.6 | 30.3 | 1.0 | 19.7 | 12.0 |\n| FX impact | 6.9 | 5.2 | (6.9) | (12.6) | (11.7) | (26.1) | 12.8 | (3.3) | 7.9 |\n| Performance | 75.1 | (66.0) | 43.2 | 15.0 | 31.6 | 23.7 | 13.5 | 21.9 | 0.9 |\n| Other | (2.8) | (4.1) | (0.1) | 1.5 | (0.0) | (2.8) | 0.6 | 0.4 | (0.2) |\n| **Total change in AuM** | 105.2 | (67.4) | 44.8 | 14.3 | 33.4 | 25.1 | 27.9 | 38.8 | 20.6 |\n\n1 Systematic and Quantitative Investments\n\n## Q3 2021 DETAILED INVESTMENT OUTPERFORMANCE\n\n| All figures in %¹ | 1Y | 3Y | 5Y |\n|-------------------|------|------|------|\n| **Active Retail** | | | |\n| Equity | 42% | 77% | 80% |\n| Multi Asset² | 21% | 21% | 21% |\n| SQI² | 24% | 38% | 35% |\n| Fixed Income | 90% | 96% | 98% |\n| Cash² | 100% | 100% | 100% |\n| **Total** | 56% | 80% | 83% |\n| **Active Institutional** | | | |\n| Equity² | 60% | 73% | 74% |\n| Multi Asset | 75% | 64% | 64% |\n| SQI | 70% | 78% | 76% |\n| Fixed Income | 70% | 78% | 86% |\n| Cash² | 89% | 40% | 100% |\n| **Total** | 71% | 75% | 83% |\n| **Active Total** | | | |\n| Equity | 44% | 76% | 79% |\n| Multi Asset | 71% | 61% | 60% |\n| SQI | 61% | 71% | 71% |\n| Fixed Income | 73% | 81% | 88% |\n| Cash | 94% | 67% | 100% |\n| **Total** | 66% | 77% | 83% |\n| **Alternatives** | | | |\n| Direct Real Estate| 36% | 84% | 86% |\n| Liquid Real Assets| 98% | 79% | 79% |\n| Other Alternatives²| 100% | 44% | 44% |\n| **Total** | 70% | 75% | 75% |\n\n**Total DWS**\n\n| | 1Y | 3Y | 5Y |\n|------------------|------|------|------|\n| | 66% | 77% | 82% |\n\n¹ Aggregate asset-weighted gross outperformance of Active and Alternatives products that have benchmark spreads (gross and net) available over respective periods (Active and Liquid Real Assets as of Sep 30, 2021, Direct Real Estate and Other Alternatives as of Jun 30, 2021) \n² <10bn AuM with BM and hence ratios not representative\n\n## CONTACT DETAILS\n\n### INVESTOR RELATIONS\n\n| Name | Email Address | Email Address | Tel: |\n|---------------|--------------------------------------|--------------------------------------|-----------------------|\n| Oliver Flade | email@example.com | firstname.lastname@example.org | +49(69)910-63072 |\n| Jana Zubatenko| email@example.com | firstname.lastname@example.org | +49(69)910-33834 |\n| Maneli Farsi | email@example.com | firstname.lastname@example.org | +49(69)910-41049 |\n\nCAUTIONARY STATEMENTS\n\nThis presentation contains forward-looking statements. Forward-looking statements are statements that are not historical facts; they include statements about our beliefs and expectations and the assumptions underlying them. These statements are based on plans, estimates and projections as they are currently available to the management of DWS Group GmbH & Co. KGaA. Forward-looking statements therefore speak only as of the date they are made, and we undertake no obligation to update publicly any of them in light of new information or future events.\n\nBy their very nature, forward-looking statements involve risks and uncertainties. A number of important factors could therefore cause actual results to differ materially from those contained in any forward-looking statement. Such factors include the conditions in the financial markets in Germany, in Europe, in the United States and elsewhere from which we derive a substantial portion of our revenues and in which we hold a substantial portion of our assets, the development of asset prices and market volatility, the implementation of our strategic initiatives, the reliability of our risk management policies, procedures and methods, and other risks.\n\nSFDR came into effect on March 10, 2021. It creates a comprehensive reporting framework for financial products and entities. It introduces specific disclosure requirements for products that promote social or environmental characteristics (Article 8) or have sustainable investment as their objective (Article 9), as well as a general disclosure requirement in relation to the integration of sustainability risks with other products (Article 6). The SFDR together with the Taxonomy Regulation, the proposed Corporate Sustainability Reporting Directive and the amended MiFiD II and Insurance Distribution Directive, are expected to create a coherent sustainable finance framework that will translate the EU climate and environmental objectives into transparent criteria for specific economic activities for investment purposes. We have therefore introduced an ESG Product Classification Framework that is designed to comply with SFDR for products within its scope. We have classified such products accordingly as Article 6, 8 and 9 and we consider all Article 8 and 9 products as ESG. For products outside the scope of SFDR (principally originating in the US and Asia Pacific), the ESG Product Classification Framework applies the Global Sustainable Investment Alliance (GSIA) General Industry Standards and Guidelines to institutional products, while retail products are classified in line with the SFDR-based DWS ESG Conversion Framework. Products that comply with these GSIA standards are also classified as ESG. We will continue to develop and refine our ESG Product Classification Framework in accordance with evolving regulation and industry standards. The aforementioned definitions apply to the entire presentation.\n\nThis document contains alternative performance measures (APMs). For a description of these APMs, please refer to the Q3 2021 Financial Data Supplement, which is accompanying this presentation and available at https://group.dws.com/ir/reports-and-events/financial-results/. Copies of the financial report are readily available upon request or can be downloaded from https://group.dws.com/ir/reports-and-events."},"books_score":{"kind":"number","value":0.8988164663314819,"string":"0.898816"}}},{"rowIdx":8699,"cells":{"content":{"kind":"string","value":"Tian Ma 65-m Radio Telescope\n\n天马望远镜\nTian Ma Telescope\n\nZhiqiang SHEN (ShAO)\nOn behalf of the Shanghai 65m RT Team\n\nThe 3rd China-U.S. Workshop on Radio Astronomy Science and Technology: Emerging Opportunities\n(May 19-21, 2014, Green Bank, West Virginia, USA)\n\nShanghai 65m Radio Telescope\n\n- 65-m in diameter, fully steerable radio telescope\n- Active surface system installed\n- Covering 1 - 50 GHz with 8 bands\n - L(1.6GHz), S/X(2.3/8.4GHz)\n - C(5GHz), Ku(15GHz), K(22GHz)\n - Ka(30GHz), Q(43GHz)\n- General-purpose (radio astronomy, single-dish, VLBI, geodynamics)\n\nFunding Agencies:\n- Chinese Academy of Sciences (CAS)\n- Shanghai Municipality\n- Chinese Lunar Exploration Project\n\n• 2008: funded; contract to CETC54 for the antenna construction\n\n• 2009: complete design (international review panel); start manufacturing; foundation laying ceremony on December 29\n\n• 2010-11: site construction started on March 19, 2010; foundation completed; antenna construction (wheel-on-track, BUS, alidade, panels, …); active surface system (contract, design, fabrication, installation of actuators)\n\n• 2012-13: L/S/X and C band Rxs in place; first light on October 26, 2012 & inauguration 2 days later; start commissioning; got named (天马); participation in the Chinese Lunar Mission (ChangE); DIBAS installed & tested\n\n• 2014-15: on-site system testing; science observations at L/S/C/X bands; active surface tested; Ku/K/Ka/Q band commissioning; project accomplished\n\nTelescope Specs\n\n- Frequency coverage: 1 ~ 50 GHz\n- Primary reflector adjustable with 1104 actuators\n- Surface accuracy (nominal):\n - 0.6mm RMS (without active surface) -> 0.53mm RMS\n - 0.3mm RMS (with active surface)\n- Aperture Efficiency:\n - L/S/C > 60%, X > 55%, Ku > 40%, K > 20%\n - Ka > 50%, Q > 45% (with active surface)\n- Pointing accuracy:\n - 3 arcsec (wind < 4m/s) [c.f. beam ~ 22 arcsec @43 GHz]\n - 10 arcsec (wind < 10m/s)\n - 30 arcsec (wind < 20m/s) -> 14”\n- Elevation limits: 5~90 degree\n- Slew rates: 0.5 degree/s (azimuth), 0.3 degree/s (elevation)\n\nPrimary & Secondary Reflectors\n\n**Primary**\n\n- 1008 aluminum panels - 14 rings\n- Measured RMS of individual panels:\n - 0.1mm (1-12 rings)\n - 0.13mm (13-14 rings)\n\n**Secondary**\n\n- 25 aluminum honeycomb panels – 3 rings\n- Measured RMS of individual panels: 50 µm\n- Overall RMS: 0.1 mm\n\n• Compensate (repeatable) gravitational deformations, to maintain the nominal shape of the primary reflector (to improve the efficiency at high freq)\n• Work on the USA GBT 100-m and Italy Noto 32-m (SRT 64-m)\n\nActive Surface Control System\n\nThe Actuators (1104)\n\n± 0.015mm/30mm\n0.36mm/s\n≤ 13kg\n-10 ~ 60°C\n20 yrs\n\nAntenna Microwave Optics\n\n- Antenna Style: Shaped Cassegrain\n- Main reflector: 65m\n- Sub reflector: 6.5m\n- Primary focal ratio (F/D): 0.32\n- Half-angle subtended by primary: 76 degree\n- Half-angle subtended by secondary: 13 degree\n\nL-Band Optics\n\n- L-band feed off focus mount\n- Sub reflector $3.5^\\circ$ rotated for observation\n- Beam offset 0.065 degree\n- Antenna efficiency 55%\n- First secondary lobes 18 dB under main\n\nL-Band Feed Horn\n\nReceiver cabin\n\nL band\n\n| Band | \"L\" | \"S\" | \"C\" | \"X\" | \"Ku\" | \"K\" | \"Ka\" | \"Q\" |\n|------|------|------|------|------|------|------|------|------|\n| Wavelength (cm) | 21/18 | 13 | 6/5 | 3.6 | 2/2.5 | 1.3 | 0.9 | 0.7 |\n| Freq range (GHz) | 1.25-1.75 | 2.2-2.4 | 4-8 | 8.2-9.0 | 12-18 | 18.0-26.5 | 30-34 | 35-50 |\n| Freq low (GHz) | 1.25 | 2.2 | 4 | 8.2 | 12 | 18 | 30 | 35 |\n| Freq high (GHz) | 1.75 | 2.4 | 8 | 9 | 18 | 26.5 | 34 | 50 |\n| BW (GHz) | 0.5 | 0.2 | 4 | 0.8 | 6 | 8.5 | 4 | 15 |\n| BW/CF (%) | 33 | 9 | 67 | 9 | 40 | 38 | 13 | 35 |\n| Freq high/low | 1.4 | 1.1 | 2.0 | 1.1 | 1.5 | 1.5 | 1.1 | 1.4 |\n| FWHP@CF (\"\") | 647.4 | 422.2 | 161.8 | 112.9 | 64.7 | 43.6 | 30.3 | 22.8 |\n| T(Sky) (K) | 12 | 12 | 10 | 10 | 12 | 25 | 13 | 26 |\n| T(Rx) (K) | 14 | 21 | 12 | 22 | 15 | 35 | 30 | 40 |\n| T(Sys) (K) | 26 | 33 | 22 | 32 | 27 | 60 | 43 | 66 |\n| Efficiency | 55% | 60% | 60% | 55% | 55% | 50% | 50% | 50% |\n| DPFU (K/Jy) | 0.66 | 0.72 | 0.72 | 0.66 | 0.66 | 0.60 | 0.60 | 0.60 |\n| SEFD (Jy) | 39 | 46 | 30 | 48 | 41 | 100 | 72 | 110 |\n| Sensitivity (mJy) | 0.142 | 0.165 | 0.110 | 0.175 | 0.147 | 0.360 | 0.258 | 0.396 |\n| Sensitivity (mJy) | 0.072 | 0.132 | 0.020 | 0.070 | 0.022 | 0.044 | 0.046 | 0.037 |\n| Feed Type | Compact | Conical | Conical | Conical | Conical | Conical | Conical | Conical |\n| Polarization | Lin & Circ | Dual Circ | Dual Circ | Dual Circ | Dual Circ | Dual Circ | Dual Circ | Dual Circ |\n| Refrigerator | 1020 | 1020 | 350 | 1020 | 350 | 1020 | 1020 | 350 |\n| Structure | Single Pixel | Dual Band | Single Pixel | Dual Band | Single Pixel | Dual Pixels | Dual Band | Dual Pixels |\n| Status | Installed May 2013 | Installed Dec 2012 | Installed May 2013 | Installed Dec 2012 | Building Sep 2014 | Building Oct 2015 | Building Dec 2014 | Building Dec 2015 |\n\n1) Tsky is EVLA value.\n2) Trx is maximum value.\n\nopportunity for mJy science\n\nL-band receiver\n\nFeatures\n\n- 500MHz BW\n- Self made cooled OMT & LNA\n- Φ270 mm microwave & vacuum window\n- Linear & circular polarization\n\nElevation Angle = 90°\n\nSystem Noise Temperature [K]\n\nFrequency [MHz]\n\nS/X-band receiver\n\nFeatures\n\n- Dual band & dual polarization\n- Self made X-band cooled polarizer\n- S-band HTS filter\n- Tcal, 50% & 5% Tsys, periodically switching mode\n- MTBF 10000h, MTTR 6h\n- Astronomy & geodesy research applications\n\nS band HTS filter & LNA\n\nC-band receiver\n\n• Features\n • Upgraded VLBA structure\n • 4-8GHz BW, 5cm and 6cm observation\n\n\n\n- **T(Rx) - Old VLBA**\n- **T(Rx) - Current EVLA**\n- **T(Rx) - Upgraded VLBA**\n\nKu-band receiver\n\n• Features\n\n• WR62 waveguide band, 12-18GHz\n• Trx<15K including feed and radom\n\n(2-pixel) K-band receiver\n\nFeatures\n\n- WR42 waveguide band, 18-26.5GHz\n- Dual-beam nodding observation\n- Cooled feed horn Phase shifter\n\nMaximum 110mm beam offset\nMaximum 4% aperture efficiency loss at CF\n\nK-band dual-pixel receiver farfield simulation (Beam A offset -110 mm / Beam B offset 0 mm)\n\nbeam space = 137.66\"\npixel space = 110 mm\n\nK-band dual-pixel receiver farfield simulation (Beam A offset -55 mm / Beam B +55 mm)\n\nbeam space = 139.82\"\npixel space = 110 mm\n\nK-band mounting structure\n\nNRAO C 4–8GHz\nCETC C 4.5–7GHz\n\nS/X Phase Center\nSpare\n\n260\n68 Ant\n\nφ130\nφ500\nφ192\nK\n\n16\n\nX/Ka-band receiver\n\nFeatures\n\n- Dual band & dual polarization\n- Self made Ka-band cooled LNA\n- Cooled dual band polarizer\n- Astronomy & geodesy research applications\n\nKa-band LNA\n\nReceiver block diagram\n\nMeasurement results at 300K\n\nS-parameters (dB) vs. Frequency (GHz)\n\nNoise temperature (K) vs. Frequency (GHz)\n\n(2-pixel) Q-band receiver\n\nMicrowave Optics Simulation Results\n\n| Feed Spacing (mm) | Beam Spacing (arcsec) | Unit of HPBW | Remarks |\n|-------------------|-----------------------|--------------|---------|\n| Single Pixel | 27.4 | 1 | |\n| 60 | 86.4 | 3.2 | |\n| 70 | 100 | 3.7 | Our Choice |\n| 80 | 113.8 | 4.2 | |\n| 100 | 144 | 5.3 | |\n| 120 | 172.8 | 6.3 | |\n| 140 | 198 | 7.2 | |\n\nDIBAS: DIgital BACkend System\n\n- An updated version of the NRAO-VEGAS (Versatile GBT Astronomical Spectrometer), customized with the addition of NRAO-GUPPI (Green Bank Ultimate Pulsar Processing Instrument)\n\n- Support two types of observing modes\n\n - **Spectral line modes**: support 29 modes, including wideband up to 16,384 channels, narrowband up to 524,288 channels and sub-band modes (higher spectral-resolution over multiple narrow bands (sub-bands) within the sampled bandwidth)\n\n - **Pulsar modes**: support the incoherent/coherent search and pulsar timing modes.\n\n## DIBAS Spectrometer Specs\n\n| Mode Name | Number of Spectral Windows/Pol | Bandwidth of Spectral Window (MHz) | Number of channels per Spectral window per Pol | Spectral resolution (KHz) | Minimum int time \\(^b\\) (msec) | Max Data rate \\(^a\\) (MB/sec) | Data rate supported by software \\(^c\\) (MB/sec) | Max Data rate from 8 spec (GB/sec) |\n|--------------------|---------------------------------|-----------------------------------|------------------------------------------------|---------------------------|-------------------------------|-------------------------------|---------------------------------------------|----------------------------------|\n| **Single Sub-band mode** | | | | | | | | |\n| Mode 1 (H1K/HBW) | 1 | 1250 | 1024 | 1465 | 0.5 | 32 | 32 | 0.3 |\n| Mode 2 (H16K/HBW) | 1 | 1250 | 16384 | 92 | 1.4 | 188 | 32 | 1.5 |\n| Mode 3 (H16K/HBW) | 1 | 850 | 16384 | 61 | 2.0 | 131 | 32 | 1.1 |\n| Mode 4 (L1/LBW1) | 1 | 187.5 | 32768 | 5.7 | 10 | 50 | 32 | 0.4 |\n| Mode 5 (L1/LBW1) | 1 | 187.5 | 65536 | 2.9 | 20 | 50 | 32 | 0.4 |\n| Mode 6 (L1/LBW1) | 1 | 187.5 | 131072 | 1.4 | 30 | 67 | 32 | 0.5 |\n| Mode 7 (L1/LBW1) | 1 | 100 | 32768 | 3.1 | 10 | 50 | 32 | 0.4 |\n| Mode 8 (L1/LBW1) | 1 | 100 | 65536 | 1.5 | 20 | 50 | 32 | 0.4 |\n| Mode 9 (L1/LBW1) | 1 | 100 | 131072 | 0.8 | 30 | 67 | 32 | 0.5 |\n| Mode 10 (L8/LBW1) | 1 | 23.44 | 32768 | 0.7 | 5 | 100 | 32 | 0.8 |\n| Mode 11 (L8/LBW1) | 1 | 23.44 | 65536 | 0.4 | 10 | 100 | 32 | 0.8 |\n| Mode 12 (L8/LBW1) | 1 | 23.44 | 131072 | 0.2 | 30 | 67 | 32 | 0.5 |\n| Mode 13 (L8/LBW1) | 1 | 23.44 | 262144 | 0.1 | 40 | 134 | 32 | 1.1 |\n| Mode 14 (L8/LBW1) | 1 | 23.44 | 524288 | 0.05 | 75 | 267 | 32 | 2.1 |\n| Mode 15 (L8/LBW1) | 1 | 11.72 | 32768 | 0.4 | 5 | 100 | 32 | 0.8 |\n| Mode 16 (L8/LBW1) | 1 | 11.72 | 65536 | 0.2 | 10 | 100 | 32 | 0.8 |\n| Mode 17 (L8/LBW1) | 1 | 11.72 | 131072 | 0.1 | 30 | 67 | 32 | 0.5 |\n| Mode 18 (L8/LBW1) | 1 | 11.72 | 262144 | 0.05 | 40 | 134 | 32 | 1.1 |\n| Mode 19 (L8/LBW1) | 1 | 11.72 | 524288 | 0.02 | 75 | 267 | 32 | 2.1 |\n| **8 Sub-band modes** \\(^d\\) | | | | | | | | |\n| Mode 20 (L8/LBW8) | 8 | 23.44 | 4096 | 5.7 | 5 | 100 | 32 | 0.8 |\n| Mode 21 (L8/LBW8) | 8 | 23.44 | 8192 | 2.9 | 10 | 100 | 32 | 0.8 |\n| Mode 22 (L8/LBW8) | 8 | 23.44 | 16384 | 1.4 | 30 | 67 | 32 | 0.5 |\n| Mode 23 (L8/LBW8) | 8 | 23.44 | 32768 | 0.7 | 40 | 100 | 32 | 0.8 |\n| Mode 24 (L8/LBW8) | 8 | 23.44 | 65536 | 0.4 | 75 | 107 | 32 | 0.9 |\n| Mode 25 (L8/LBW8) | 8 | 15.625 | 4096 | 3.8 | 7 | 71 | 32 | 0.6 |\n| Mode 26 (L8/LBW8) | 8 | 15.625 | 8192 | 1.9 | 14 | 71 | 32 | 0.6 |\n| Mode 27 (L8/LBW8) | 8 | 15.625 | 16384 | 0.95 | 40 | 50 | 32 | 0.4 |\n| Mode 28 (L8/LBW8) | 8 | 15.625 | 32768 | 0.48 | 55 | 72 | 32 | 0.6 |\n| Mode 29 (L8/LBW8) | 8 | 15.625 | 65536 | 0.24 | 100 | 80 | 32 | 0.6 |\n\n\\(^a\\) Maximum data rate is calculated for recording full polarization and all channels at the minimum integration period. Each spectral value is represented by 4 bytes.\n\n\\(^b\\) The integration per switching state should be \\(\\geq\\) the minimum integration. For example, if an observation uses 2 switching states, then the minimum integration will be 2 times the value listed in table.\n\n\\(^c\\) The specified rate is for one spectrometer.\n\n\\(^d\\) For modes 20 to 24 the subbands can be placed within the baseband bandwidth of 1500 MHz (usable frequency range 150 MHz to 1400 MHz) and for modes 25 to 29 the subbands can be placed within 1000 MHz (usable frequency range 150 MHz to 950 MHz).\n\n| 观测模式 | 子带数目 | 子带带宽 (MHz) | 子带通道数 | 频率分辨率 (kHz) | 速度分辨率 (km/s) |\n|---------|---------|---------------|------------|-----------------|------------------|\n| | | | | | Q 波段 @ 43 GHz | K 波段 @ 22 GHz | C 波段 @ 6.7 GHz | L 波段 @ 1.7 GHz |\n| 1 | 1 | 1500 | 1024 | 1465 | 10.2 | 20.0 | 65.6 | 258.5 |\n| 2 | 1 | 1500 | 16384 | 92 | 0.64 | 1.25 | 4.1 | 16.2 |\n| 3 | 1 | 1000 | 16384 | 61 | 0.43 | 0.83 | 2.7 | 10.8 |\n| 4 | 1 | 187.5 | 32768 | 5.7 | 0.04 | 0.08 | 0.26 | 1.01 |\n| 5 | 1 | 187.5 | 65536 | 2.9 | 0.02 | 0.04 | 0.13 | 0.51 |\n| 6 | 1 | 187.5 | 131072 | 1.4 | 0.01 | 0.02 | 0.06 | 0.25 |\n| 7 | 1 | 100 | 32768 | 3.1 | 0.02 | 0.04 | 0.14 | 0.55 |\n| 8 | 1 | 100 | 65536 | 1.5 | 0.01 | 0.02 | 0.07 | 0.26 |\n| 9 | 1 | 100 | 131072 | 0.8 | 0.006 | 0.01 | 0.036 | 0.14 |\n| 10 | 1 | 23.44 | 32768 | 0.7 | 0.005 | 0.01 | 0.031 | 0.124 |\n| 11 | 1 | 23.44 | 65536 | 0.4 | 0.003 | 0.0055 | 0.018 | 0.07 |\n| 12 | 1 | 23.44 | 13172 | 0.2 | 0.0014 | 0.0027 | 0.009 | 0.035 |\n| 13 | 1 | 23.44 | 262144 | 0.1 | 0.0007 | 0.0014 | 0.0045 | 0.018 |\n| 14 | 1 | 23.44 | 524288 | 0.05 | 0.00035 | 0.00068 | 0.0022 | 0.009 |\n| 15 | 1 | 11.72 | 32768 | 0.4 | 0.003 | 0.0055 | 0.018 | 0.07 |\n\n| 观测模式 | 子带数目 | 子带带宽 (MHz) | 子带通道数 | 频率分辨率 (kHz) | 速度分辨率 (km/s) |\n|---------|---------|---------------|------------|-----------------|------------------|\n| | | | | | Q 波段 @ 43 GHz | K 波段 @ 22 GHz | C 波段 @ 6.7 GHz | L 波段 @ 1.7 GHz |\n| 16 | 1 | 11.72 | 65536 | 0.2 | 0.0014 | 0.0027 | 0.009 | 0.035 |\n| 17 | 1 | 11.72 | 131072 | 0.1 | 0.0007 | 0.0014 | 0.0045 | 0.018 |\n| 18 | 1 | 11.72 | 262144 | 0.05 | 0.00035 | 0.00068 | 0.0022 | 0.009 |\n| 19 | 1 | 11.72 | 524288 | 0.02 | 0.00014 | 0.00027 | 0.0009 | 0.0035 |\n| 20 | 8 | 23.44 | 4096 | 5.7 | 0.04 | 0.08 | 0.26 | 1.01 |\n| 21 | 8 | 23.44 | 8192 | 2.9 | 0.02 | 0.04 | 0.13 | 0.51 |\n| 22 | 8 | 23.44 | 16384 | 1.4 | 0.01 | 0.02 | 0.06 | 0.25 |\n| 23 | 8 | 23.44 | 32768 | 0.7 | 0.005 | 0.01 | 0.031 | 0.124 |\n| 24 | 8 | 23.44 | 65536 | 0.4 | 0.003 | 0.0055 | 0.018 | 0.07 |\n| 25 | 8 | 15.625 | 4096 | 3.8 | 0.027 | 0.052 | 0.17 | 0.67 |\n| 26 | 8 | 15.625 | 8192 | 1.9 | 0.013 | 0.026 | 0.085 | 0.34 |\n| 27 | 8 | 15.625 | 16384 | 0.95 | 0.007 | 0.013 | 0.043 | 0.17 |\n| 28 | 8 | 15.625 | 32768 | 0.48 | 0.0033 | 0.0065 | 0.021 | 0.085 |\n| 29 | 8 | 15.625 | 65536 | 0.24 | 0.0017 | 0.0033 | 0.011 | 0.042 |\n\nDIBAS pulsar observing modes\n\n| Averaging | Folding |\n|-----------|---------|\n| **Incoherent** | **Coherent** |\n| Incoherent search mode | Coherent search mode |\n| Applications: | Applications: |\n| - Pulsar searches! | - Multi-pulsar systems |\n| - Single-pulse studies | (Globular clusters, etc) |\n| - General spectroscopy | - High time resolution |\n| Incoherent fold mode | Coherent fold mode |\n| Applications: | Applications: |\n| - Search follow-up | - MSP timing |\n| - “Slow” pulsar timing | - High pulse phase resolution |\n| - Polarimetry | - Polarimetry |\n\nScheduling of pulsar observations\n\nSchedule File\n\nEnd of File?\n\nScan information\n\nDIBAS setup\n\nTelescope Track\n\nReady?\n\nOn source?\n\nStart recording\n\nScan finished?\n\nEnd\n\n| # | NAME | RAJ (hms) | DECI (dms) | DM (cm^-3 pc) | BAND (L,S,C,X) | MODE (PSR_mode_NCH_BW) | Length (s) |\n|---|------------|-----------|------------|---------------|----------------|-------------------------|------------|\n| 1 | J0006+1834 | 00:06:04.8| +18:34:59 | 12.00 | L | PSR_COFOLD_2048_1000 | 600 |\n\nFirst light on October 26, 2012\n\nW3(OH): Shanghai 65m Radio Telescope 2012-OCT-26\n\nW3(OH)\n200sec\n\nPower (dBm)\n\nRadio Frequency (MHz)\n\nFringe detected on 65m-25m (Nov. 28, 2012)\n\n===Baseline Cross Phase===\n\nS.Interval 300 NFFT Avg. 64\nBandWidth(M) 4 Nf 512\nInt.Tim 1.04857 FFTPag 286\nBBC Freq,\n01#2208.8; 02#2208.8;\n\nProcessing FILE 2 201233034900_3C2\nWriting data... 338.93s\n\nSheshan 65m RT\nSheshan VLBI Center\nSheshan 25m RT\n\n2.4 KM 6.1 KM 4 KM\n\nOn Dec 1-3, 2012, SH65 joined the OD of CE-2 with the 3 other VLBI stations (Ur25, Km40 and Sh25).\n\nOne year later, during the CE-3 landing mission (2013Dec - 2014Jan), TM telescope has done an excellent job!\n\ntesting results in January 2013 with the PDFB system\n\nemail@example.com, Ob: S-band, $t_{\\text{int}} \\sim 3$min\n\nfirstname.lastname@example.org, Ob: S-band, $t_{\\text{int}} \\sim 18$min\n\nMSP(16ms)\n\nDM=370, Ob: S-band, $t_{\\text{int}} \\sim 15$min\n\nemail@example.com, Ob: X-band, $t_{\\text{int}} \\sim 5$min\n\nTesting observations\n\nFirst light from W3(OH)\n\nHI 21 cm line\n\nVLBI fringes with the GBT\n\nSignals from the CE-2\n\nms pulsar profile\n\nThe TianMa Telescope\n\nShanghai 65m RT\n\nMulti beam system (2-beam at K- and Q-band)\n(+ simultaneous observations of multiple lines)\n\nL band Rx\nC band Rx\nS band Rx\nX band Rx\nKu band Rx\nKa band Rx\nQ band Rx (2-beam)\nK band Rx (2-beam)\n\nVLBI terminal (CDAS) + correlator\n\nGeneral-purpose (DIBAS)\n\nContinuum, line and pulsar + multi-beam\n\nUsers\n\nScience with the TianMa 65m RT\n\n- VLBI\n- Single-dish\n - Line (maser)\n - Pulsar\n - Continuum\n\nScience with the 65m RT\n\n• Astrometry\n – Celestial reference frame\n – High-accuracy astrometry, space tracking & navigation\n\n• Astrophysics\n – High-resolution polarization-sensitive VLBI Observations\n • AGN and Jets\n • B-field in cluster of galaxies\n • Pol’n of galactic masers\n – Galactic and Extra-galactic masers\n • Physics of (high-mass) star formation\n • Structure, evolution of Galaxy and dark matter\n • Large scale structure (cosmological distance)\n – Survey/Search of spectral line emission\n • Molecular lines in Galaxy\n • Magamasers\n – High-z CO observations\n – Radio stars and variables\n – …\n\nSpectral line\n\nhigh sensitivity, wide frequency coverage\nSuitable for spectral line observations.\n\n- Discovery of new lines (masers)\n- Search for some important line emissions, such as high-z CO (bw=4MHz, T=20hr, sigma=0.2 mJy@22GHz, or, 0.9mJy @ 43 GHz)\n- Multiple-line observation towards SFRs\n- Deep K-band Galactic Plane Survey\n\n| 分子 | 静止频率（GHz） |\n|------------|--------------------------------|\n| 氢（HI） | 1.420 |\n| 羟基（OH） | 1.612, 1.665, 1.667, 1.721, 4.766, 6.035, 13.434 |\n| CH | 3.335, 3.263, 3.335, 3.349 |\n| 甲醛（H₂CO）| 4.830, 14.488, 28.974, 48.284 |\n| 氦（³He⁺） | 8.665 |\n| CS | 11.119, 22.344, 33.751, 43.981 |\n| 甲醇（CH₃OH）| 6.669, 12.179, 25.018 |\n| SO | 13.044, 30.002, 36.201, 44.1, 48.4, 62.932, 66.035, 86.094 |\n| C₃H₂ | 18.343, 13.0, 30.086, 41.830, 36.218, 2, 21.6, 46.7, 51.8, 85.293 |\n| 氰基乙炔（HCCCN）| 9.097, 18.198, 27.296, 36.394, 45.490 |\n| 水（H₂O） | 22.235, 183.310 |\n| 氨（NH₃） | 23.694, 23.723, 23.870 |\n| 一氧化硅（SiO）| 42.820, 42.880, 43.122, 43.424, 85.640, 86.243, 86.846 |\n| 一硫化碳（CS）| 48.991, 97.981, 146.969, 244.936, 342.883 |\n| 一氧化碳（CO）| 109.782, 110.201, 112.359, 115.271, 230.538, 345.796 |\n\nFREQUENCY (GHz)\n\n| Name | Species | Transition | Frequency (MHz) | Reference |\n|---------------------|-----------|--------------------|-----------------|----------------------------|\n| Hydroxyl | OH | $^2\\Pi_{3/2}, J = 3/2$ | 1665.4018(2)a | Weinreb et al. 1963 |\n| Ammonia | NH$_3$ | (1, 1) | 23694.4955(1)b | Cheung et al. 1968 |\n| Formaldehyde | H$_2$CO | $1_{11} - 1_{10}$ | 4829.660(1)b | Snyder et al. 1969 |\n| Water | H$_2$O | $6_{16} - 5_{23}$ | 22235.08(2)b | Cheung et al. 1969 |\n| Methyl alcohol | CH$_3$OH | $1^+ - 1^-$ | 834.267(2) | Ball et al. 1970 |\n| Formic acid | HCOOH | $1_{11} - 1_{10}$ | 1638.804(1) | Zuckerman et al. 1971 |\n| | | $2_{11} - 2_{12}$ | 4916.319(3) | GWi & Churchwell 1975 |\n| Formamide | NH$_2$CHO | $1_{11} - 1_{11}$ | 1539.58(2)c | Palmer et al. 1971 |\n| | | $2_{11} - 2_{12}$ | 4618.55(2)c | Rubin et al. 1971 |\n| Cyanoacetylene | HC$_3$N | 1 – 0 | 9098.6537(3)e | Turner 1971 |\n| | H$_{13}$C$_3$N | 1 – 0 | ~ 9060d | Gardner & GWi 1975a |\n| | H$_{12}^{13}$C$_3$N | 1 – 0 | ~ 9000d | Churchwell et al. 1977 |\n| Acetaldehyde | CH$_3$CHO | $1_{10} - 1_{11}$ | 1065.075(5) | Ball et al. 1971 |\n| Methylidene | CH | $^2\\Pi_{1/2}, J = 1/2$ | 3263.788(10)e | Rydbeck et al. 1973 |\n| Thioformaldehyde | H$_2$CS | $2_{11} - 2_{12}$ | 3139.38(3) | Sinclair et al. 1973 |\n| Methanimine | CH$_2$NH | $1_{10} - 1_{11}$ | 5290.31(4) | Godfrey et al. 1973 |\n| Methylamine | CH$_2$NH$_2$ | $2_{02} - 1_{10}$ | 8776.2(1)f | Fourikis et al. 1974 |\n| Vinyl cyanide | H$_2$CCHCN | $2_{11} - 2_{12}$ | 1371.8262(1) | Gardner & GWi 1975b |\n| Methyl formate | HCOOCH$_3$-A | $1_{10} - 1_{11}$ | 1610.2445(7) | Brown et al. 1975 |\n| | | HCOOCH$_3$-E $1_{10} - 1_{11}$ | 1610.91(10) | Churchwell & GWi 1975 |\n| Dimethyl ether | (CH$_3$)$_2$O | $2_{02} - 1_{11}$ | 9119.668(15)c | GWi & Gardner 1976 |\n| Cyanodiacetylene | HC$_5$N | 4 – 3 | 10650.650(4) | Avery et al. 1976 |\n| | | 2 – 1 | 5325.328(2) | Gardner & GWi 1978 |\n\npulsar — an important target\n\n- Survey at C-band\n- Join the Pulsar timing observations\n - There are 3 major GW detectors: space-based (LISA), ground-based (LIGO) and, pulsar timing arrays\n- Pulsar Astrometry\n- ......\n\nMore testing work ongoing\n\n- pointing\n- OTF\n- Active surface control system (hologrammetry, photogrammetry)\n- ...\n\nNRAO/GBT visit: (July 17- August 1, 2013);\n\nHardware arrived: September 9, 2013\n\nNRAO engineers visit: Mid-October 2013\n\nThanks for your attention!"},"books_score":{"kind":"number","value":0.9555971026420593,"string":"0.955597"}}}],"truncated":false,"partial":true},"paginationData":{"pageIndex":86,"numItemsPerPage":100,"numTotalItems":85090,"offset":8600,"length":100}},"jwt":"eyJhbGciOiJFZERTQSIsImtpZCI6IjVHZDBvd0g5MTM2eDZjc1FvbE1zcktNWUZoRVFoUm5PVVVybEpjOUhaUEEifQ.eyJyZWFkIjp0cnVlLCJwZXJtaXNzaW9ucyI6eyJyZXBvLmNvbnRlbnQucmVhZCI6dHJ1ZX0sImlhdCI6MTc4NzE0OTc5NywianRpIjoiZjZiMmRkMzYtYjRmMC00NzY4LTkzZTYtMmU4YmVkMDVlYjg2Iiwic3ViIjoiL2RhdGFzZXRzL2thaXplbjkvYm9va3BkZnNfc2FtcGxlIiwiZXhwIjoxNzg3MTUzMzk3LCJpc3MiOiJodHRwczovL2h1Z2dpbmdmYWNlLmNvIn0.LgkkT7zyK1fcKPShxL5o4bx5w8NbX_xKU8IQ5XQ8HAvWqU6f9-NLBkEowBa-R2kJycCVGwwZQbiChpNZ98o3Dw","displayUrls":true,"splitSizeSummaries":[{"config":"default","split":"train","numRows":85090,"numBytesParquet":1979326621}]},"discussionsStats":{"closed":0,"open":1,"total":1},"fullWidth":true,"hasGatedAccess":true,"hasFullAccess":true,"isEmbedded":false,"savedQueries":{"community":[],"user":[]}}">
content string | books_score float64 |
|---|---|
2019
ANNUAL REPORT
MORE INFORMATION ABOUT BETSSON IS AVAILABLE AT WWW.BETSSONAB.COM
The following is a list of the most important and commonly used terms in the field of computer science, organized by category.
### Algorithms
- **Algorithm**: A step-by-step procedure to solve a problem or perform a task.
- **Big O ... | 0.38642 |
Product Description:
The MaxLite Slim Flood Light family delivers high performance in a small and price-effective package. All versions are available for a variety of mounting applications - 1/2" threaded knuckle, yoke and slipfitter. Many models are CCT and Wattage selectable and include a photocell. A 3-pin NEMA twis... | 0.653337 |
EXPERIENCE & QUALITY
SW SWATHER
SW SWATHER
Multiple coupling options:
- **Front** part of tractor (with rear hydraulic unit or front PTO)
- **Rear** part of tractor (reversible driving position)
- Combine harvester
- Forage harvester
Possibility of use in a multitude of crops: grass, alfalfa, lentils, oats, clover... | 0.479118 |
September 30, 2014
Dr. Charles Regan
Minnesota Pollution Control Agency
520 Lafayette Road North
St. Paul, MN 55155
Dear Dr. Regan:
RE: Hydrology and Water-Quality Calibration and Validation of Minnesota River Watershed Model Applications
Please review the following methodology and results for hydrologic and... | 0.994827 |
Introduction
The EDS-4012 Series is a range of 12-port managed Fast Ethernet switches with the option for four 1 Gbps fiber-optic uplink ports. This Series also offers models with four 10/100BaseT(X) 802.3af (PoE), 802.3at (PoE+), and 802.3bt-compliant Ethernet PoE port options to connect high-bandwidth PoE devices.
... | 0.394872 |
4A Series (75 Ω) for TV camera applications
For video applications LEMO offers a range of dedicated connectors adapted to US standards. Especially conceived to connect Triax television cameras to their control equipment, the 4A Series connectors are widely used by the most important manufacturers of professional video... | 0.823909 |
Built to POWER.
Electric Products
2020 Catalog
Oldcastle Infrastructure™
A CRH COMPANY
CARSON®
A NAME YOU TRUST. DURABILITY YOU EXPECT.
Carson® high-density polyethylene (HDPE) enclosures deliver reliable, chemical and water resistant performance and install with ease. The Carson® brand offers a wide variety of si... | 0.99217 |
warm summery sultry cooked
balmy boiling blazed
blazing sweltering piping heated
roasting scorching sizzling
intense raging sharp spicy
violent angry fierce peppery
passionate pungent
Which words would be most useful to describe your noun?
What order would the words come in from most powerful to weake... | 0.419883 |
Q2 2023 EARNINGS CALL
Constantin Baack, CEO
Moritz Fuhrmann, CFO
AGENDA
1. Q2 2023 in Review
2. Market Update
3. Company Outlook
HIGHLIGHTS
1 Q2 2023 FINANCIALS
» Strong results with high utilization and continuation of low-leverage strategy
» Profit for the period of USD 101.5m and USD 0.15/share recurring divide... | 0.840362 |
KLINGERSIL® C-4300 - universal soft gasket material.
Consisting of aramid fibers bonded with NBR, this universal high-pressure gasket material is resistant to hot water, steam, oils, hydrocarbons and other chemicals. It provides increased plant safety for a wide range of applications.
**Basis composition** Aramid fi... | 0.924638 |
5 EASY STEPS TO PUSH-ON JOINT ASSEMBLY
DO IT RIGHT – WATER TIGHT!
A displaced or rolled gasket creating water loss in a ductile iron pipeline is one of the most common errors that occurs during joint assembly. To avoid displacing or rolling a gasket and to ensure proper joint assembly, be sure to follow these 5 easy ... | 0.663246 |
| Color | ID | Material Type |
|---------------------|---------------------|-----------------|
| Alaska Gray | LPNLMALAGRY924 | Marble |
| Arctic White | LPNLQARCWHI924 | Quartzite |
| California Gold | LPNLSCALGLD924 | Slate |... | 0.992058 |
MC Next 2023
Getting Started Guide
Trademarks
Tradenames and trademarks of some companies and products have been used in this manual. These names are used in an editorial fashion, with no intention of infringement of the trademark.
Copyrights
© 2023. All rights reserved. No part of this manual may copied, photocop... | 0.529312 |
SOGEFI
STAR CONFERENCE 2018
Milano – March 27-28th, 2018
Laurent HEBENSTREIT - Chief Executive Officer
Yann ALBRAND - Chief Financial Officer
Stefano Canu - Investor Relations
Agenda
1 Full Year 2017 Results
2 Technology
3 Profitable and Sustainable Growth Strategy
2017 Highlights
- Revenues up by 6.2% at €1.672... | 0.446469 |
Thank you for purchasing this SHARP product.
To obtain the best performance from this product please read this manual carefully. It will guide you in operating your SHARP product.
MD-X5 MD/CD stereo consisting of
MD-X5 MD/CD stereo
CF-X5 2 way speaker system.
CONTENTS
| Section |... | 0.429156 |
Fellin Park Appendix
Chapter 7: Fellin Park Appendix
Ouray Fellin Park Meeting with Stakeholders - March 11, 2016
The general purpose of meeting was to set goals and solicit input on the park’s program so that design alternatives could be drafted. The information for Fellin Park improvements will be summarized into ... | 0.57193 |
Roll Call
Approval of Agenda
Announcements
Recognition of Community & Guests
Consent Agenda
Disbursements
Special Event Permit: Friends of NFSIS
Staff Reports
Town Administrator’s Report
Finance/Treasurer Report
New Business
Resolution 2023-03: Appointment of Town Clerk
Discussion of Town Policy Related to Employ... | 0.349828 |
Information and Job Aids for Early Childhood Care, Stimulation and Education
RESOURCE COMPENDIUM FOR INTEGRATION OF EARLY CHILDHOOD DEVELOPMENT INTO PROGRAMS FOR CHILDREN ORPHANED OR MADE VULNERABLE BY HIV (OVC)
This publication is made possible by the generous support of the American people through the United States... | 0.59109 |
Overview
The MA 08 Advanced Series are quarter-turn electric industrial service actuators delivering up to 708”lbs torque in 24vac/vdc or 92~265vac models, and available in 2 position (Open/Close), Floating (Open/Close/Jog) or Modulating (4-20mA default or 2-10vdc) control schemes. The Advanced model eliminates the ne... | 0.573647 |
Introducing the ACT® Label
A Pathway to Greener Laboratory Choices
About the Label:
Our commitment to sustainability has been a core value at USA Scientific for decades. We take all facets of improving global health seriously. From our 100% wind-powered TipOne® production facility in Connecticut to our dedication to... | 0.496377 |
Market Colour
Global equity markets plunged for the second day following the sell-off in US stocks, with the Dow Jones posting its biggest one-day loss in more than six years. Most of the selling in US markets accelerated in the final hours of trading as the VIX more than doubled to its highest in 2 years. In the shor... | 0.57307 |
VITG implements a three-tier information security and privacy policy framework consisting of:
- **Policy** – establishes organizational wide requirements
- **Standards/guidelines** – provides implementation options and risk based control tailoring and
- **Procedures** – utilizes checklists, templates, and step-by-step... | 0.385181 |
This manual is intended to meet the Manufacturer’s Instructions as required by the American National Standards Institute (ANSI) Z359 and should be used as part of an employee training program as required by the Occupational Safety and Health Administration (OSHA).
# Table of Contents
1.0 Warnings and Important Inform... | 0.435834 |
Our advanced series SL23 units are DC input power supplies for HeNe lasers up to 15mW. These power supplies include all the benefits of our standard units - long life, maximum output and greater than 75% efficiency - with the addition of an active filter to reduce current ripple and noise. Additional heat sinking is no... | 0.80141 |
Fasteners Pricing Guide
## Accessories
| Item | Page |
|-------------------------------------------|------|
| Drill Bits | 2 |
| Sockets | 2 |
| Screw and Pop Rivet Guns | 3 |
| #12 Diameter... | 0.374442 |
Roll Call
Work Session
Work Session on Short Term Rentals and Accessory Dwelling Units
Adjournment
This session will be live-streamed on the Town of Paonia’s YouTube channel but no minutes will be taken.
Find the live stream here: https://www.youtube.com/channel/UC2mZDPKrwEAf5T-x3Camtow
The Public is welcome and e... | 0.397721 |
Teach with Trash
Tissue Box Science
By PreKinders.com
For directions, visit this link:
http://www.prekinders.com/tissue-box-science
Graphic credits:
Clipart.com
ScrappinDoodles.com
Teacherspayteachers.com/Store/Zip-a-dee-doo-dah-Designs
pinecone shell rock
stick leaf flower
© PreKinders.com
crayon
scissors
... | 0.330189 |
FANUC AC SERVO MOTOR $\alpha i$ series
FANUC AC SERVO MOTOR $\beta i$ series
FANUC LINEAR MOTOR $LiS$ series
FANUC SYNCHRONOUS
BUILT-IN SERVO MOTOR $DiS$ series
PARAMETER MANUAL
B-65270EN/06
No part of this manual may be reproduced in any form.
All specifications and designs are subject to change without notice.
T... | 0.772958 |
CARIBBEAN INTERNATIONAL BOAT SHOW
San Juan EDITION
May 3-5, 2024
Safe Harbor San Juan
Pier 9, Old San Juan
Exhibitor’s Proposal
We are thrilled to extend an invitation for your participation in the 13th Caribbean International Boat Show, the largest and most prestigious Boat Show in the Caribbean, now in our new and... | 0.853985 |
Test Report
Airtightness test of the vapour control layer including connections
System "Procheck Adapt"
Manufacturer:
Proctorgroup
Airtightness system: Surface sealing
Darmstadt 07.04.2020
Passive House Institute GmbH
Rheinstr. 44/46
64291 Darmstadt, Germany
www.passiv.de
1. Introduction
Airtightness across the... | 0.675869 |
## Official Basketball Box Score -- Game Totals -- Final Statistics
**Greenfield vs Loretto**
03/08/19 4:30 PM at Murphy Center (Murfreesboro, Tenn.)
### Greenfield 55 • 29-6
| # | Player | Total FG-FGA | 3-Ptr FG-FGA | FT-FTA | Off Def Tot | PF TP | A TO Blk Stl | Min |
|---|-----------------|------------... | 0.973824 |
Manual on
Use of Public Right-of-Way
Standard Approach Policy
Local Highway Technical Assistance Council
3330 Grace Street
Boise, ID 83703
208-344-0565/1-800-259-6841
www.lhtac.org
PREFACE
This document is one of several produced by the Local Highway Technical Assistance Council, (LHTAC) in an attempt to assist the ... | 0.324652 |
Introducing the all-new 3 Series Coupe for 2007 – giving more power to the Sports Coupe concept.
3 Series Coupe
Product Ordering Guide
Confidential information for use by authorized BMW centers. Please note: Images shown are low resolution. Due to color printer capabilities, colors shown may not print out accurately.... | 0.416514 |
Water Resources Research Report
Conflict Resolution Support System
A Software for the Resolution of Conflicts in Water Resource Management
By:
K. D. W. Nandalal
and
Slobodan P. Simonovic
Report No: 044
Date: June 2003
ISSN: (print) 1913-3200; (online) 1913-3219;
ISBN: (print) 978-0-7714-2618-6; (online) 978-0-7714-... | 0.468482 |
Feel the difference.
Two Striper®
AN ABRASIVE TECHNOLOGY BRAND
Ultra-Premium Diamond Burs
Introducing
Two Striper® BLACK
Super Coarse Diamonds providing rapid cutting and optimal performance.
Two Striper® Bulk Packs
30 of your favorite Two Striper® shapes available in economic packs of 50.
Distributed by premier®... | 0.903023 |
EHL-10
Intel® Elkhart Lake Processor based Mini ITX Motherboard
Features
- CPU: Intel Elkhart Lake Celeron and Pentium processors
- Memory: Single channel SO-DIMM DDR4 up to 32GB
- Display: Intel UHD Graphics display via HDMI, DP, LVDS/eDP
- Ethernet: 10/100/1000 Mbps
- Storage: M.2 for SSD, SATA3.0
- Expansion: M.2 ... | 0.563803 |
Finding Social Media ROI
Andrew Spoeth
Director, Digital Marketing
CA Technologies
September 2016
2006: “We need to be on social media.”
2016: “We need to do social media well.”
Q. What can social media do for a brand?
Social Media can mean many different things to different parts of the organization but we gener... | 0.404498 |
Optimum method for determine the percent of depreciation in the productivity machines & equipment: Applied study
Ryad Jamal WAHAB¹ & Abdulazez Bashar HASEEB²
Keywords
Depreciation, Depreciation Methods, Depreciation factors, Classification of Depreciation.
Abstract
This search aimed to try make comparative between v... | 0.643004 |
Glossary I: QCard/QScreen/Handheld QED-Forth Functions
This Glossary provides detailed descriptions of all of the library routines, called “Words” in FORTH, provided in the QED-Forth firmware on the QCard, QScreen Controller, and QED Handheld. These products carry a firmware version number of the form V4.4x, where x i... | 0.752548 |
European Technical Approval ETA-08/0105
English translation prepared by DIBt - Original version in German language
| Handelsbezeichnung | Injektionssystem Hilti HIT-RE 500 für Bewehrungsanschluss |
|-------------------|----------------------------------------------------------|
| Trade name | Injection System ... | 0.795708 |
POWERTEX
Permanent Lifting Magnet PLM
User Manual
These instructions contain all the information required for safe and optimum use of the lifting magnet. Read the instructions carefully and follow the directions. Keep the instruction in a safe place close to the workplace.
On delivery check that the magnet is undam... | 0.810986 |
Solar Hot Water Overview
Washington DC Office Building
April, 2017
Solar Hot Water Concepts - Introduction
Three Building Blocks of Solar Thermal
- **Solar Collectors** – 4’x8’ or 4’x10’
- Each Solar Collector is rated by the International Energy Agency at 2 to 2.5 KW-thermal.
- Each Solar Collector Reduces CO2... | 0.327443 |
VDV Scout™ Pro Series
VDV SCOUT™ PRO LT / VDV SCOUT™ PRO
TESTS VOICE, DATA & VIDEO CONNECTIONS
KLEIN TOOLS®
VDV Scout™ Pro Series
- Tests continuity on voice, data and video connections.
**MEASURES CABLE LENGTH**
- VDV Scout™ Pro LT only
- Feet or Meters
- Simultaneous testing of video and data cables saves time... | 0.841238 |
Heavy metals and their impact on surface waters of the Mantaro river basin, Junin, Peru
Abstract
In the Mantaro river basin, located in Central Peru, an agricultural activity developed, even supplying the capital of Peru. An intense mining activity took place in the headwaters of this basin, and the La Oroya Metallur... | 0.482532 |
Establishing Blended Learning Environment in Online Learning Mathematics for University Students.
Asia Majeed, PhD Student, OISE, University of Toronto.
Abstract
The purpose of this study is to explore the possibilities that online learning and teaching offer for learning mathematics for university undergraduate stu... | 0.448042 |
MODELS HREB-C, HREB-P & HRED-C
Hooded Propeller Roof Exhaust Fans
Advancing Ventilation
**MODEL FEATURES**
- Exhaust air to over 90,000 CFM up to 1” w.g.
- Belt drives permit easy performance adjustments when needed
- Direct drive units have low sound levels and quiet operation
- Reversible blades available
- cULus ... | 0.921214 |
Armenia, Azerbaijan Hold Another Summit on Karabakh
Azeri FM Sees ‘Certain Progress’ in Conflict Settlement
MOSCOW -- The leaders of Armenia and Azerbaijan held a meeting for more than three hours in Russian capital Moscow last Friday in the latest round of internationally mediated negotiations over the disputed Nag... | 0.415583 |
スマイル いちねん祭
おかげさまで1年(^^)Vスマイルなイベント開催します♪
ハロウィーン由英語イベント
～Let's say Trick or Treat～
スマイルおなじみ(^^♪なおみせんせいとハロウィーンをえいごで楽しんじゃおう❤️
10:00〜10:40 参加費：500円
（付き添いの方は無料） ☆定員20名
☆対象：幼児〜小学生
門川尚美せんせい（パーククレセント）
キッストランポリン教室♪
ミニトランポリンに挑戦！！運動大好きごあつまれ〜!(^^)!
11:00〜11:40 参加費：500円（レンタルトランポリン+500円） ☆定員：10名☆対象：小学生
講師：武貞 梢せんせい（ミボリンダイエット協会）
... | 0.354839 |
Mindfulness Moment
CASSANDRA VIETEN, PHD
ACTING DIRECTOR, CENTER FOR MINDFULNESS
DIRECTOR OF RESEARCH
ARTHUR C. CLARKE CENTER FOR HUMAN IMAGINATION
UNIVERSITY OF CALIFORNIA, SAN DIEGO
Plumeria
The plumeria is a tropical flower that is known for its beautiful and fragrant blooms. It is often used in lei making and i... | 0.337869 |
Industrial Hose
Coupled Hose Assemblies
Call Toll Free: 1-866-711-4673
International:+1-727-342-5086
Time is money. And we are saving you both.
At Continental ContiTech, constant innovation and improvement is our industry standard. And we know that innovation is not always about high-tech, scientific inventions. Som... | 0.899144 |
Work Planned for the Period 14th August to 20th August 2023
Construction work for Moray West Offshore Wind Farm commenced on the 6th February 2023.
The key aim of the Weekly Notice of Operations is to give a global view of activities and vessels involved. Questions regarding the operations will be welcome preferably ... | 0.698445 |
AN INTEGRATED MODEL FOR EXTENDING BRAND BASED ON FUZZY ARAS AND ANP METHODS
Mahmoud Zamani\textsuperscript{1}, Arefeh Rabbani\textsuperscript{2}, Abdolreza Yazdani-Chamzini\textsuperscript{3}, Zenonas Turskis\textsuperscript{4}
\textsuperscript{1,2}Young Researchers Club, Central Tehran Branch, Islamic Azad Universit... | 0.353165 |
After months of investigation, police from Interpol swooped down on an international drug syndicate operating out of Antwerp, Belgium. The syndicate had been smuggling drugs from Kenya, Uganda, and Tanzania into the port of Antwerp for distribution throughout Europe. Smuggling had netted the syndicate millions of dolla... | 0.501807 |
mavi
ANNUAL REPORT 2020
ANNUAL REPORT 2020
## CONTENTS
| Section | Page |
|------------------------------------------------------------------------|------|
| 01. Key Financial Metrics 2020 | 3 |
| 02. Chairman... | 0.407004 |
Digital Transmission Content Protection 2 (DTCP2) Specification Volume 1 (Informational Version)
Intel Corporation
Maxell, Ltd.
Panasonic Holdings Corporation
Sony Group Corporation
Toshiba Corporation
Revision 1.0.4
October 25, 2022
Notice
THIS DOCUMENT IS PROVIDED "AS IS" WITH NO WARRANTIES WHATSOEVER, INCLUDING ... | 0.393363 |
CAT 793C HAUL TRUCK
ALL LED OPTION
ABL 2500 SERIES LED3000
www.MatrixTeam.com
The 2500 Series ABL (5”x5”) Halogen work lamps have long been the OE standard for a wide variety of heavy equipment. ABL proudly launches the new ABL LED3000 series. The ABL LED3000 has the same current draw as a HID Ballast work lamp (40... | 0.38344 |
RF ENERGY EXPOSURE AND
Frequency Chart
Radio Control Buttons and Display
Installing the Batteries
1. Remove the battery cover by sliding it in the direction shown.
2. Insert the batteries into the battery compartment, making sure that they are installed correctly.
3. Plug the micro USB cable into the micro USB ... | 0.710287 |
G2300
DUTCH QUALITY BRAND
WWW.TOBROCO-GIANT.COM
## TECHNICAL DATA
| TYPE | G2300 HD | G2300 X-TRA HD |
|-----------------------|----------------|----------------|
| Service weight 1 | 2,300 kg | 2,350 kg |
| Lifting capacity | 1,650 kg | 2,200 kg |
| Tipping ... | 0.386048 |
Design, construction and evaluation of a distributed 48 V inverter for a mild hybrid vehicle
Master's thesis in Electric Power Engineering
Carl Tisell
Usman Tariq
Department of Electrical Engineering
CHALMERS UNIVERSITY OF TECHNOLOGY
Gothenburg, Sweden 2018
Design, construction and evaluation of a distributed 48 V ... | 0.460782 |
2D Desktop Barcode Scanner
Full Manual
V2.7.06
| Connection Method | 4 |
|-------------------|---|
| Enable/Disable Configuration barcode | 4 |
| Version No. | 4 |
| Factory Default Setting | 4 |
| Product User Configuration | 5 |
| Data Interface | 5 |
| USB Keyboard Layout | 6 |
| RS232 Interface Configuration | 1... | 0.740576 |
An action-packed new series based on the worlds of
CLASH OF CLANS + CLASH ROYALE
from superstar graphic novelist GENE LUEN YANG!
ALSO AVAILABLE:
KOSKA REEVES™
1/6 SCALE MINI-BUST
COMING FALL 2023
WWW.GENTLEGIANTLTD.COM/STAR-WARS
starwars.com
© & ™ Lucasfilm Ltd.
Gentle Giant is a registered trademark of 3D Syste... | 0.964873 |
Metalworking Saw Blades
Standard, Custom and Cold Saw Blades
With a base of solid experience, the latest in technological advancements and a focus on the needs of the customer, NAP Gladu surpasses its goal of providing more than just a cutting tool. We are your application engineers, engineering department, problem so... | 0.937672 |
Wind Design of Timber Panelized Roof Structures
2012 International Building Code (IBC) Edition
Developed for WoodWorks by
Brian Vandenburg, PE, SE
President
The Structures Group Southwest
John W. Lawson, PE, SE
Consulting Structural Engineer and Assistant Professor in Architectural Engineering
California Polytechni... | 0.646545 |
| Category | Item | Price |
|---------------|-----------------------|-------|
| Fresh Juices | Orange Juice | 50 |
| | Pineapple Juice | |
| | Mango Juice | |
| | Watermelon Juice | |
| Smoothies | M... | 0.767968 |
Mark Scheme (Results)
January 2018
Pearson Edexcel International GCSE in Further Pure Mathematics (4PM0) Paper 01
Edexcel and BTEC Qualifications
Edexcel and BTEC qualifications come from Pearson, the world’s leading learning company. We provide a wide range of qualifications including academic, vocational, occupati... | 0.321072 |
INSTALLATION AND OPERATION MANUAL
90-Series
TR90:
Painted Case
Low Voltage Controls
Line Cord
TR90G:
Galvanized Case
Line Voltage
No Line Cord
WARNING
RISK OF FIRE, ELECTRIC SHOCK, OR INJURY. OBSERVE ALL CODES AND THE FOLLOWING:
1. Before servicing or cleaning the unit, unplug the unit line cord or shut off power... | 0.727737 |
where sky and sea meet.
and beyond.
company presentation
FY2020
SOMEC
This document has been prepared by SOMEc S.p.A. (the ‘Company’) solely for the purposes of this presentation. This document may not be reproduced or distributed in whole or in part by any other person with any way than the Company. The Company tak... | 0.593508 |
DYMO®
LabelManager® 420P
User Guide
Copyright
© 2015 Newell Rubbermaid Europe, LLC. All rights reserved. Rev. 7/19
No part of this document may be reproduced or transmitted in any form or by any means or translated into another language without the prior written consent of Newell Rubbermaid Europe, LLC.
Trademarks
... | 0.697546 |
Bibliometric Keyword Analysis across Seventeen Years (2000–2016) of *Intelligence* Articles
Bryan Pesta $^{1,*}$, John Fuerst $^2$ and Emil O. W. Kirkegaard $^2$
1 Department of Management, Cleveland State University, Cleveland, OH 44115, USA
2 The Ulster Institute for Social Research, London AL2 1AB, UK; email@examp... | 0.314534 |
Korea Country Report
Ho Kang
October 2014
| Substrate/Plant type | Number of plants | Production* (GWh/year) |
|------------------------------|------------------|------------------------|
| Sewage sludge | 38 | 969 |
| Biowaste (co-digestion) | 16 ... | 0.403182 |
Programming & Control Manual
DMR PC 6-50
V1
Motor Power Company s.r.l.
Via Leonardo Da Vinci, 4
42024 Castelnovo Sotto Reggio Emilia - Italia
Tel. +39 0522 682711 – Fax +39 0522 683552
firstname.lastname@example.org – motorpower.com
Cap. Soc. 250.000,00€ i.v. – R.E.A. di RE 175521
Iscr.Reg.Impr. di RE n.01308390358 ... | 0.760565 |
Parts Manual
Vermeer/ McLaughlin
V500 Vacuum Machine
Part #E850500
(SERIAL #5D/5D091708257 - 5DE012909296)
© 2008 by McLaughlin Group, Inc. 082508
All rights reserved. No part of this manual may be reproduced in any form, or by any means without prior written permission of McLaughlin Group, Inc.
# Table of Contents
... | 0.602732 |
Bigtincan Holdings
1H FY24 Results
Bigtincan Holdings Limited
ASX:BTH
28th Feb 2024
1H FY24 Highlights
Financial
- **Positive EBITDA**
- $1.9m EBITDA up 136% over PcP
- **Strong Unit Economics**
- 88% Gross Margin
- Operating Leverage improvement
- S&M+R&D = 69% of revenue
- **Business Adjustments**
- ... | 0.401535 |
NOTICE OF REGULAR MEETING
SNOHOMISH CITY COUNCIL
in the George Gilbertson Boardroom
1601 Avenue D
TUESDAY
February 6, 2018
6:00 p.m.
AGENDA
Estimated time
6:00 1. CALL TO ORDER
a. Pledge of Allegiance
b. Roll Call
2. APPROVE AGENDA contents and order
3. APPROVE MINUTES of the meeting of January 16, 2018 (P... | 0.540997 |
Datasheet
FS9922-DMM3
Integrated Circuits of 4,000 Counts
Auto-ranging Digital Multimeter with Bar Graph
This manual contains new product information. Fortune Semiconductor Corporation reserves the rights to modify the product specification without further notice. No liability is assumed by Fortune Semiconductor Cor... | 0.944802 |
Rethinking Access Control and Authentication for the Home Internet of Things (IoT)
Weijia He, Maximilian Golla, Roshni Padhi, Jordan Ofek, Markus Dürmuth, Earlence Fernandes, Blase Ur
Back to the Future Part II - Universal Pictures - cnn.com
CNET Smart Apartment - cnet.com
From Single User to Multi User
Single Use... | 0.805095 |
CABLE EQUIPEMENTS
Brochure October 2022
CABLE HANDLING
COILING MACHINES
AUTOMATIC CABLE REELS
CABLE PROTECTION
WIRING - CABLE DRAW
## Cable Handling
### Cable Drum Unwinders
| Model | Essential Feature | Code | Max Weight (kg) | Cable Drums Ø (mm) | Max Width... | 0.960069 |
Considerations for Limiting and Preventing Microbial Contamination in Whole Grain Cereal Based Products
Dr. Andreia Bianchini
The Food Processing Center
Food Science and Technology Department
University of Nebraska - Lincoln
Why Worry About Safety?
- Foodborne diseases/outbreaks
- Worldwide over 1 billion cases oc... | 0.876869 |
COMPANY PRESENTATION
YEAR 2006
TEAM WORKING GLOBAL THINKING
South Europe Midcap Events
Paris, 29-30 March, 2007
WORLD’S LEADERSHIP ON TWO KEY VEHICLES TECHNOLOGIES
ENGINE FILTRATION SYSTEMS
FLEXIBLE COMPONENTS FOR SUSPENSION
FILTRATION SYSTEMS
MARKET STRENGTHS
- EUROPEAN LEADER ON THE EUROPEAN INDEPENDENT AFTE... | 0.586397 |
OPEN OPPORTUNITIES
PAPER | PACKAGING | SOLUTIONS
Smurfit Kappa
From the production line through to the consumer, packaging can make a difference: through new ideas it has the potential to shape the way you do business.
The images in this report are from video case studies on our company microsite.
For more informa... | 0.450947 |
Understanding disaster preparedness and resilience in Canterbury: results of interviews, focus groups and a questionnaire survey
J.S. Becker
GNS Science Report 2010/50
August 2010
Becker, J.S. 2010. Understanding disaster preparedness and resilience in Canterbury: results of interviews, focus groups and a questionna... | 0.807717 |
INTERIM REPORT
QUARTER ONE
FOR THE MONTH ENDED
MARCH 31, 2024
# CONTENTS
**MANAGEMENT’S DISCUSSION AND ANALYSIS ("MD&A")** .......................................................... 1
HIGHLIGHTS ......................................................................................................................... | 0.548166 |
Oracle® Database
SQL Language Reference
11g Release 2 (11.2)
E17118-03
August 2010
Oracle Database SQL Language Reference, 11g Release 2 (11.2)
E17118-03
Copyright © 1996, 2010, Oracle and/or its affiliates. All rights reserved.
Primary Authors: Diana Lorentz, Mary Beth Roeser
Contributors: Sundeep Abraham, Angel... | 0.571033 |
ANNUAL STATEMENT
FOR THE YEAR ENDED DECEMBER 31, 2021
OF THE CONDITION AND AFFAIRS OF THE SEPARATE ACCOUNTS OF THE
ANNUTY INVESTORS LIFE INSURANCE COMPANY
NAIC Group Code 0435 (Current) 0384 (Prior) NAIC Company Code 93661 Employer's ID Number 31-1021738
Organized under the Laws of Ohio State of Domicile or Port of E... | 0.977864 |
Pan European High Resolution Snow & Ice Monitoring of the Copernicus Land Monitoring Service (CoSIMS)
Atelier Glaciologie | CNES | 25 Juin 2019
Simon Gascoin (Cesbio)
Joël Dorandeu (Magellium)
Copernicus is a European system for monitoring the Earth. Data is collected by different sources, including Earth observatio... | 0.421478 |
PRF - Radon Mitigation Fans
Advancing Ventilation®
Radon is a hazardous, odorless gas that is everywhere! It cannot be seen, tasted or smelled by humans, making it impossible to detect without radon testing. Nearly 1 out of every 15 homes in the U.S. is estimated to have elevated radon levels.
**WHAT IS RADON?**
Rad... | 0.405054 |
10-fold Islamic Rosette Pattern
Sarah Gelsinger Brewer
@mathemartiste
mathemartiste.com
2021
Start by drawing a circle. Your entire motif will fit inside this circle, so make it large.
Placing your pencil point in the center of your circle and bringing your ruler to your pencil, draw a horizontal line.
Keeping your... | 0.482709 |
PROPERTY DESCRIPTION
Prime Development Opportunity: 9.84 acres at the prominent intersection of Covell and Santa Fe, this site enjoys excellent visibility and high traffic volumes. The area is supported by a growing affluent demographic, enhancing its appeal. Whether you envision a single-tenant build-to-suit or a mul... | 0.471075 |
PDF Converter for SharePoint - User Guide
Muhimbi Ltd
Version 11.1
Purpose and audience of document
This document contains instructions about how to use the PDF Converter for SharePoint on a day by day basis as well as how to create workflows that utilise the PDF Converter.
The intended audience is any SharePoint ... | 0.413258 |
Mini PCI Express Multiport Serial Board Series User Manual
Version 1.0, December 2022
www.moxa.com/products
© 2022 Moxa Inc. All rights reserved.
The software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement.
**Copyright Notice**
©... | 0.762032 |
WILDBLUE
COMMUNITY DEVELOPMENT DISTRICT
PUBLIC HEARINGS AND REGULAR MEETING AGENDA
September 5, 2019
August 28, 2019
Board of Supervisors
WildBlue Community Development District
Dear Board Members:
The Board of Supervisors of the WildBlue Community Development District will hold multiple Public Hearings and a Regul... | 0.570095 |
Kingsbrook Jewish Medical Center
Rutland Nursing Home
Nursing Education, Practice and Research
2016 Mandatory Yearly Retraining
Revised December 2015
(Includes Infection Control Addendum)
Self-Learning Package
Next Review Date: December 2016
ORGANIZATIONAL TRAINING AND EDUCATION
This Mandatory Retraining Self-Lea... | 0.511604 |
Acquisition Master Class
Reader Revenue MASTER CLASS ACQUISITION
August 2020
mather:
Mather specializes in applied analytics.
10:1 RETURN ON INVESTMENT
Our typical client engagement provides a 10-to-1 return on investment. We increase revenue yield and reduce risks from pricing actions.
$6B+ REVENUE MANAGEMENT
... | 0.537995 |
Sensitive and accurate peptide identification with Mascot Percolator
Markus Brosch
email@example.com
Terminology: FPR, FDR, PEP
L. Käll, J. D. Storey, M. J. MacCoss, W. S. Noble, *J Proteome Res* 7, **29** (2008).
L. Käll, J. D. Storey, M. J. MacCoss, W. S. Noble, *J Proteome Res* 7, **40** (2008).
M. Brosch, J. Cho... | 0.954563 |
Devices for occluding a patient's ascending aorta and delivering oxygenated blood to the patient
A device (2) for delivering oxygenated blood and occluding the ascending aorta is provided. The device (2) has a blood flow lumen (12) with a movable portion (18). The movable portion (18) is movable from a position contai... | 0.625469 |
MTM800
TETRA 車載台對講機
功能使用手冊
| 章節 | 頁碼 |
|------|------|
| 一般資訊 | 1 |
| 安全資訊 | 1 |
| 廢棄處置資訊 | 1 |
| 版權資訊 | 2 |
| 特定產品資訊 | 2 |
| 圖示慣例 | 3 |
| 開始之前 | 4 |
| 如何使用本手冊 | 4 |
| 控制項與指示燈 | 5 |
| 螢幕顯示 | 7 |
| LED 狀態指示燈 | 9 |
| 開機/關機 | 10 |
| 按鍵概觀 | 12 |
| 首頁模式畫面 | 17 |
| 時間與日期 | 17 |
| 對講機... | 0.403821 |
MODEL MC12PH
CONCRETE MIXER
(HONDA GX340UT2QA2/GX340UT2QAP2
GASOLINE ENGINES)
Revision #4 (08/03/23)
To find the latest revision of this publication, visit our website at: www.multiquip.com
THIS MANUAL MUST ACCOMPANY THE EQUIPMENT AT ALL TIMES.
PROPOSITION 65 WARNING
WARNING
CANCER & REPRODUCTIVE HARM
www.P65Warni... | 0.676671 |
Sub-national electricity and gas consumption statistics
Region, Local Authority, middle and lower layer super output area
22 December 2015
Statistician Responsible: Greg Haigh
Any enquiries regarding this publication should be sent to us at:
firstname.lastname@example.org.
© Crown copyright 2015
URN 15D/549
You m... | 0.416714 |
DWS GROUP – Q3 2021 RESULTS
October 27, 2021
CONTINUED STRONG BUSINESS MOMENTUM
Record results in Q3, underpinning strong client engagement
RECAP: PHASE TWO
- Invest into transformation for further efficiency and targeted growth
FY 2020
- Differentiated leadership: ESG, Passive, high margin strategies
- Take act... | 0.898816 |
Tian Ma 65-m Radio Telescope
天马望远镜
Tian Ma Telescope
Zhiqiang SHEN (ShAO)
On behalf of the Shanghai 65m RT Team
The 3rd China-U.S. Workshop on Radio Astronomy Science and Technology: Emerging Opportunities
(May 19-21, 2014, Green Bank, West Virginia, USA)
Shanghai 65m Radio Telescope
- 65-m in diameter, fully stee... | 0.955597 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.