Contents Introduction XMLTABLE Overview Missing elements Generating rows for a subset of the data Handling multiple values per cell Nonexistent paths XMLTABLE with Namespaces Summary Acknowledgements Downloadable resources Related topics Comments XMLTABLE by example Part 1 Retrieving XML data in relational format Harness the power of this useful SQLXML function in DB2 Matthias Nicola and Vitor Rodrigues Published on August 30 2007 XMLTABLE Overview To understand this article you should be familiar with the pureXML support in DB2 and with the basics of querying XML data in DB2 If you do not understand these topics please see the Resources section of this article for a list of helpful articles on this subject XMLTABLE is an SQLXML function that evaluates an XQuery expression and returns the result as a relational table While XQuery expressions always return sequences of XML nodes XMLTABLE returns this sequence as a set of rows in relational format The returned table can contain columns of any SQL type including the XML type Figure 1 XMLTABLE overview Like any SQLXML function XMLTABLE is embedded in an SQL statement The evaluation of an XMLTABLE function returns a rowset where each column has an SQL data type This means it is a table function not a scalar function To learn about the XMLTABLE function in more detail view the following sample table which contains two rows with one XML document per row Listing 1 is an example of a simple XMLTABLE statement Listing 1 Sample table and data 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 dept bldg 101 employee id 901 name first John first last Doe last name office 344 office salary currency USD 55000 salary employee employee id 902 name first Peter first Pan name office 216 office phone 9054165004 phone employee dept dept bldg 114 employee id 903 name first Mary first Jones name office 415 office phone 9054036112 phone phone 6475044546 phone salary currency USD 64000 salary employee dept Listing 2 is an example of a simple XMLTABLE statement Listing 2 A simple XMLTABLE example 1 2 3 4 5 6 7 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d empID INTEGER PATH id firstname VARCHAR20 PATH namefirst lastname VARCHAR25 PATH namelast AS X Running this query in DB2 returns the following result 1 2 3 4 5 empID firstname lastname 901 John Doe 902 Peter Pan 903 Mary Jones Curious about how that works The XMLTABLE function is used in the FROM clause of the SELECT statement together with the table emp that it operates on The XMLTABLE function is implicitly joined with the table emp and applied to each of its rows The XMLTABLE function contains one rowgenerating XQuery expression and in the COLUMNS clause one or multiple columngenerating expressions In Listing 1 the rowgenerating expression is the XPath ddeptemployee The passing clause defines that the variable d refers to the XML column doc of the table emp The rowgenerating expression is applied to each XML document in the XML column and produces one or multiple employee elements subtrees per document The output of the XMLTABLE function contains one row for each employee element Hence the output produced by the rowgenerating XQuery expression determines the cardinality of the result set of the SELECT statement The COLUMNS clause is used to transform XML data into relational data Each of the entries in this clause defines a column with a column name and a SQL data type In the example above the returned rows have 3 columns named empID firstname and lastname of data type Integer Varchar20 and Varchar25 respectively The values for each column are extracted from the employee elements which are produced by the rowgenerating XQuery expression and cast to the SQL data types For example the path namefirst is applied to each employee element to obtain the value for the column firstname The rowgenerating expression provides the context for the columngenerating expressions In other words you can typically append the columngenerating expressions to the rowgenerating expression to get an intuitive idea of what a given XMLTABLE function returns in its columns Be aware that the path expressions in the COLUMNS clause must not return more than one item per row If a path expression returns a sequence of two or more items the XMLTABLE execution will typically fail as it is not possible to convert a sequence of XML values into an atomic SQL value This scenario is discussed later in the article The result set of the XMLTABLE query can be treated like any SQL table You can query and manipulate it much like you use regular rowsets or views Instead of using the passing column as clause you can specify the data input to the XMLTABLE function with the db2fnxmlcolumn or db2fnsqlquery functions DB2 LUW only For example above can also be written as shown in Listing 3 to produce the same result Listing 3 A different notation for Listing 1 1 2 3 4 5 6 7 SELECT X FROM XMLTABLE db2fnxmlcolumnEMPDOCdeptemployee empID INTEGER PATH id firstname VARCHAR20 PATH namefirst lastname VARCHAR25 PATH namelast AS X Missing elements XML data can contain optional elements that are not present in all of your documents For example in Listing 1 employee Peter Pan does not have a salary element since its not a required data field in our sample scenario Its easy to deal with that because the XMLTABLE function simply produces null values for missing elements so you can write XMLTABLE queries as if the salary element was always present Listing 4 illustrates this Listing 4 An extension of Listing 2 to also produce a salary column 1 2 3 4 5 6 7 8 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d empID INTEGER PATH id firstname VARCHAR20 PATH namefirst lastname VARCHAR25 PATH namelast salary INTEGER PATH salary AS X This query returns the following result where the salary column in the returned relational table has a null value for employee Peter Pan 1 2 3 4 5 empID firstname lastname salary 901 John Doe 55000 902 Peter Pan 903 Mary Jones 64000 If you want a value other than null to appear for missing elements such as the number zero you can define a default value that is returned in case the expected element is missing This is shown in Listing 5 which returns 0 as the salary for Peter Pan Note that the default value must match the target data type of the column Since salary is mapped to an integer column the default value must be an integer Listing 5 Using a default value in the columngenerating expression for salary 1 2 3 4 5 6 7 8 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d empID INTEGER PATH id firstname VARCHAR20 PATH namefirst lastname VARCHAR25 PATH namelast salary INTEGER default 0 PATH salary AS X Generating rows for a subset of the data Often you want to produce rows only for a subset of the employees based on some filtering predicate An easy solution is to add a WHERE clause with an XMLEXISTS predicate to your query See the Resources section of this document for articles related to this topic Another solution is to use filtering predicates in the rowgenerating expression of the XMLTABLE function Say you need to produce rows only for employees in building 114 You can add a corresponding predicate to any of the queries above which returns only a single row for Mary Jones who is the only employee in building 114 Listing 6 illustrates adding a rowfiltering predicate to Listing 6 Adding a rowfiltering predicate to Listing 1 1 2 3 4 5 6 7 8 SELECT X FROM emp XMLTABLE ddept strong bldg114 strong employee passing doc as d empID INTEGER PATH id firstname VARCHAR20 PATH namefirst lastname VARCHAR25 PATH namelast salary INTEGER default 0 PATH salary AS X Handling multiple values per cell As mentioned earlier the path expressions in the COLUMNS clause must not produce more than one item per row In the sample documents in Listing 1 notice that the employee Mary Jones has two phone numbers If you need to query this data and return a relational table with each employees name and phone number the query you would write might look like this Listing 7 Extracting XML data into relational 1 2 3 4 5 6 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d first VARCHAR25 PATH namefirst last VARCHAR25 PATH namelast phone VARCHAR12 PATH phone AS X For the sample documents that are used in this article this query fails it produces the following error message SQL16003N An expression of data type item item can not be used when the data type VARCHAR_12 is expected in the context This message means that the query is trying to cast an XML sequence of multiple items to a single Varchar value A value of data type item item means the value is an item followed by one or more additional items In simpler terms this means that the value is a sequence of two or more items This happens because the path expression phone returns two phone elements for the employee Mary Jones Next the article describes five options that help you avoid receiving this error Return only one of multiple phone numbers Return a list of multiple phone numbers in a single Varchar value Return a list of multiple phone numbers as an XML type Return multiple phone columns Return one row per phone number Each of these options has its benefits so you can decide which one to use based on your needs Return only one of multiple elements One way to deal with this issue is to return only one of the multiple phone numbers If you need summarized information for each employee having just one phone number may be enough Returning only one occurrence of the phone element can be done with a positional predicate in the XPath expression for the column phone as shown in Listing 8 Listing 8 Returning the first occurrence of phone element for each employee 1 2 3 4 5 6 7 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d first VARCHAR25 PATH namefirst last VARCHAR25 PATH namelast phone VARCHAR12 PATH phone strong 1 strong AS X Square brackets in XPath are used to specify predicates To obtain the first phone element for an employee use a positional predicate written either as 1 or fnposition1 The former notation 1 is an abbreviated version of the latter Listing 7 returns the following result set 1 2 3 4 5 6 7 first last phone John Doe Peter Pan 9054165004 Mary Jones 9054036112 3 records selected Return a list of multiple values in a single Varchar If you need to return all phone numbers you can list them within a single column Since VARCHAR12 is too small for multiple phone numbers the SQL type for the returned column needs to be changed Use VARCHAR100 here which allows you to produce multiple phone numbers separated by a comma as in Listing 9 Listing 9 Listing all the phone numbers from a single employee 1 2 3 4 5 6 7 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d first VARCHAR25 PATH namefirst last VARCHAR25 PATH namelast phone VARCHAR100 PATH strong fnstringjoinphonetext strong AS X For the sample data this query returns 1 2 3 4 5 6 7 first last phone John Doe Peter Pan 9054165004 Mary Jones 90540361126475044546 3 records selected The phone column contains the two phone numbers listed for employee Mary Jones The function fnstringjoin links these values and requires two parameters a sequence of string values and a separator character In this example the two parameters are the sequence of the phone elements text nodes and the character Return multiple elements as an XML sequence Another option to return multiple phone numbers for a single employee is to return an XML sequence of phone elements as Listing 10 illustrates To achieve this the generated phone column needs to be of type XML which allows you to return any XML value as the result of the XPath expression This value can be an atomic value or a sequence Listing 10 Returning all the phone elements as an XML sequence 1 2 3 4 5 6 7 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d first VARCHAR5 PATH namefirst last VARCHAR5 PATH namelast phone strong XML strong PATH phone AS X This query returns one row per employee with their phone numbers in an XML sequence in the XML column phone 1 2 3 4 5 6 first last phone John Doe Peter Pan phone 9054165004 phone Mary Jones phone 9054036112 phone phone 6475044546 phone 3 records selected The XML value returned in the phone column for Mary Jones is not a wellformed XML document since there is no single root element This value can still be processed in DB2 but you wont be able to insert it into an XML column or parse it with an XML parser in your application If you need to produce wellformed XML documents you can wrap the sequence of phone elements in new root element for example by changing the path expression in the columns clause to phonesphonephones Return multiple phone columns Combining multiple phone numbers into a single Varchar or XML value may require additional code in your application to use the individual numbers If you prefer to return each phone number as a separate Varchar value you can do this by producing a fixed number of phone columns Listing 11 uses positional predicates to return phone numbers in two columns Listing 11 Returning multiple phone columns 1 2 3 4 5 6 7 8 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d first VARCHAR25 PATH namefirst last VARCHAR25 PATH namelast phone VARCHAR12 PATH strong phone1 strong phone2 VARCHAR12 PATH strong phone2 strong AS X The output for the query in Listing 10 is 1 2 3 4 5 6 7 first last phone phone2 John Doe Peter Pan 9054165004 Mary Jones 9054036112 6475044546 3 records selected An obvious drawback to this approach is that a variable number of items is being mapped to a fixed number of columns An employee may have more phone numbers than anticipated Others may have less which results in null values But if every employee has exactly one office phone and one cell phone then producing two columns with corresponding names is very useful Return one row per phone number Instead of returning the phone numbers in separate columns you can also use XMLTABLE to return them in separate rows In this case you need to return one row per phone number instead of one row per employee This may result in repeated information in the columns for the first and last names Listing 12 shows what happens when you change the rowgenerating XPath expression in the XMLTABLE function to create a relational row per phone number Listing 12 Producing one row per phone number 1 2 3 4 5 6 7 SELECT X FROM emp XMLTABLE ddeptemployee strong phone strong passing doc as d first VARCHAR5 PATH namefirst last VARCHAR5 PATH namelast phone VARCHAR12 PATH AS X As compared to the previous queries Listing 11 uses different XPath both in the rowgenerating and columngenerating expressions As the context is now a phone element and not an employee element the XPath expressions in the COLUMNS clause have changed accordingly The paths for first and last name begin with a parent step because name is a sibling of phone The result of this query contains two relational rows for employee Mary Jones each with one of her phone numbers 1 2 3 4 5 6 7 first last phone Peter Pan 9054165004 Mary Jones 9054036112 Mary Jones 6475044546 3 records selected Nonexistent paths You probably wonder why Listing 11 didnt return a row for employee John Doe What happened is that the rowgenerating expression in Listing 11 iterates over all the phone elements in the documents and there is no phone element for the employee John Doe As a result the employee element for John Doe is never processed If unnoticed this could be a problem creating an incomplete employee list To avoid this a row must be generated for each employee even if the employee does not have a phone element A possible solution is to produce a row for the name element a sibling of phone whenever a phone element is not present Do this with the following commaseparated list of expressions phone fnnotphonename The results of both expressions are combined into a single sequence But in this case one of the two expressions always produces an empty result If an employee has one or more phone elements this produces all of these phone elements If the document has no phone element then and only then the name element is returned The fnnot function avoids duplicate rows for those employees which have a name and a phone This is shown in Listing 13 Listing 13 Producing rows for phone numbers or names 1 2 3 4 5 6 7 SELECT X FROM emp XMLTABLE ddeptemployee strong phonefnnotphonename strong passing doc as d first VARCHAR5 PATH namefirst last VARCHAR5 PATH namelast phone VARCHAR12 PATH strong phone strong AS X Listing 12 generates rows not only for phone elements but also for name elements when no phone element is present If an employee has several phone numbers the query returns one row per phone number If an employee has no phone number it returns only one row for that employee without phone information 1 2 3 4 5 6 7 8 first last phone John Doe Peter Pan 9054165004 Mary Jones 9054036112 Mary Jones 6475044546 4 records selected XMLTABLE with Namespaces XML namespaces are a W3C XML standard for providing uniquely named elements and attributes in an XML document XML documents may contain elements and attributes from different vocabularies but have the same name By giving a namespace to each vocabulary the ambiguity is resolved between identical element or attribute names All pureXML features in DB2 9 support XML namespaces such as SQLXML XQuery XML indexes and XML schema handling For more information on querying XML data with namespaces see Resources In XML documents you declare XML namespaces with the reserved attribute xmlns whose value must contain an Universal Resource Identifier URI URIs are used as identifiers they typically look like a URL but they dont have to point to an existing web page A namespace declaration can also contain a prefix used to identify elements and attributes Below is an example of a namespace declaration with and without prefix 1 2 3 xmlns strong ibm strong httpwwwibmcomxmltable xmlns httpwwwibmcomxmltable To demonstrate the use of namespaces with XMLTABLE a sample document is added to Listing 1 Unlike the other documents introduced in Listing 1 at the beginning of this article this new document contains a namespace declaration with the prefix ibm Listing 14 Sample document containing a namespace declaration with a prefix 1 2 3 4 5 6 7 8 9 10 11 ibmdept bldg 123 xmlnsibm httpwwwibmcomxmltable ibmemployee id 144 ibmname ibmfirst James ibmfirst ibmlast Bond ibmlast ibmname ibmoffice 007 ibmoffice ibmphone 9050071007 ibmphone ibmsalary currency USD 77007 ibmsalary ibmemployee ibmdept Execute the query in Listing 1 again and check the output Executing this query in DB2 produces the following output 1 2 3 4 5 empID firstname lastname 901 John Doe 902 Peter Pan 903 Mary Jones As you can see the information about employee James Bond is not returned The reason is that references only the element names that have no namespace In order to return all the employees in the database you can use the wildcard for the namespace prefix in the path expressions in Listing 15 This causes all elements to be considered regardless of namespaces because this wildcard matches any namespace including no namespace Listing 15 Using a wildcard to match all namespaces 1 2 3 4 5 6 7 SELECT X FROM emp XMLTABLE ddeptemployee passing doc as d empID INTEGER PATH id firstname VARCHAR20 PATH namefirst lastname VARCHAR25 PATH namelast AS X As a result of using wildcards to match all namespaces in the documents all employees are returned 1 2 3 4 5 6 7 8 empID firstname lastname 901 John Doe 902 Peter Pan 903 Mary Jones 144 James Bond 4 records selected For this specific data the namespace wildcard for the attribute id was not strictly necessary The reason is that the id attribute employee James Bond has no namespace Attributes never inherit namespaces from their element and also never assume the default namespace So unless the attribute name has a prefix it doesnt belong to any namespace The use of the wildcard expression is the simplest way to return all employees regardless of namespace Next see how you can return only the information for the employees in the ibm namespace There are two ways to specify the namespace in an XQuery or XPath expression this can be done by declaring a default namespace declaring a namespace prefix Declaring a default namespace When all the elements you want to query belong to the same namespace declaring a default namespace can be the simplest way to write your queries You just need to declare the default namespace in the beginning of your XQuery expression and after that all elements and attribute names you reference are tied to that namespace This is shown in Listing 16 Listing 16 Using default namespace declaration 1 2 3 4 5 6 7 8 9 10 SELECT X FROM emp XMLTABLE strong declare default element namespace httpwwwibmcomxmltable strong ddeptemployee passing doc as d empID INTEGER PATH id firstname VARCHAR20 PATH strong declare default element namespace httpwwwibmcomxmltable strong namefirst lastname VARCHAR25 PATH strong declare default element namespace httpwwwibmcomxmltable strong namelast AS X Using the namespace declarations allows you to filter the employees from the namespace ibm The output from Listing 15 is the following 1 2 3 4 5 EMPID FIRSTNAME LASTNAME 144 James Bond 1 records selected Please note that the columngenerating expressions do not inherit the namespace declaration from the rowgenerating expression Each columngenerating expression is a separate XQuery and needs its own namespace declaration These namespace declarations may differ from each other for example if your document contains multiple namespace Often there is only one namespace in which case it would be convenient to declare a single namespace for all expressions in the XMLTABLE function This can be achieved by using the function XMLNAMESPACES This function allows you to declare a default namespace andor several namespace prefixes inside XMLTABLE and other SQLXML functions The advantage of using the XMLNAMESPACES function is that the declared namespaces are global for all expressions in the XMLTABLE context so all the XQuery expressions will be aware of these namespaces declarations and repeated namespace declarations are not required Lets rewrite Listing 16 using the XMLNAMESPACES function Listing 17 Using XMLNAMESPACES to declare the default namespace 1 2 3 4 5 6 7 8 SELECT X FROM emp XMLTABLE strong XMLNAMESPACESDEFAULT httpwwwibmcomxmltable strong ddeptemployee passing doc as d empID INTEGER PATH id firstname VARCHAR20 PATH namefirst lastname VARCHAR25 PATH namelast AS X The default namespace declared by the XMLNAMESPACES function applies to both the rowgenerating expression and all the columngenerating expressions This way only one namespace declaration is needed for all XQuery expressions in an XMLTABLE function The result of Listing 17 is exactly the same as for Listing 16 Declaring a namespace prefix While a default namespace is a common solution when only one namespace is present in your documents you need a different approach if your documents contain multiple namespaces Using a default namespace only allows you to select elements and attributes from that namespace and using a wildcard selects elements and attributes from all namespaces If you want to select elements and attributes from multiple specific namespaces then using namespace prefixes is your best option Unless you use the XMLNAMESPACES function the namespaces prefixes need to be declared for every expression But just like for default namespaces you can use the XMLNAMESPACES function to avoid repeated namespace declarations Listing 18 shows how to declare a namespace prefix in the XMLTABLE function Listing 18 Using the XMLNAMESPACES function to declare a namespace prefix 1 2 3 4 5 6 7 8 SELECT X FROM emp XMLTABLE XMLNAMESPACEShttpwwwibmcomxmltable as ibm dibmdeptibmemployee passing doc as d empID INTEGER PATH id firstname VARCHAR20 PATH ibmnameibmfirst lastname VARCHAR25 PATH ibmnameibmlast AS X As expected Listing 17 returns the same result as Listing 16 1 2 3 4 5 EMPID FIRSTNAME LASTNAME 144 James Bond 1 records selected Summary In this first part of our 2part series on XMLTABLE you have learned how to use XMLTABLE to retrieve XML data in relational format how to deal with repeating or missing XML elements and nonexisting paths and how to handle namespaces in the XMLTABLE function This gives you a powerful range of capabilities for querying your XML data in DB2 LUW and DB2zOS In part 2 of this series learn about common XMLTABLE usage scenarios such as shredding XML into relational tables splitting large documents into smaller ones and relational views over XML data Acknowledgements Thanks to Cindy Saracco for her review and helpful comments on this paper Downloadable resources PDF of this content Comments or register to add and subscribe to comments Subscribe me to comment notifications Newest Oldest Popular 23 May 2017 BVC Hi I have the below input xml I need to fetch the PartyTypeCode tc for the Party based on the below condition Fetch the RelatedObjectID for which RelationRelationRoleCode tc54 The value got from RelatedObjectID should be substituted for the id attribute of the Party tag and the corresponding PartyTypeCode tc should be retrieved In our case RelatedObjectID will translate to Client and the Party idClient1 should be searched and the PartyTypeCode tc value of 2 should be retrieved TXLife TXLifeRequest OLifE Party idClient1 PartyTypeCode tc2ORGPartyTypeCode Party Party idContact1 PartyTypeCode tc1PERSONPartyTypeCode Person FirstNameDanaFirstName Person Party Relation Relation idRelation3 OriginatingObjectIDHolding1 RelatedObjectIDClient1 RelatedObjectType 29 Aug 2016 patelinc Hi This is Hemant Patel I would like to know if there is any issue parsing big XML file 10 MB if yes then what should be the resolution Does IBM 5733XT2 XML tools kit help 18 Apr 2013 MatthiasNicola Hi Tinkurnthanks for your comment I believe your are referring to Listing 11 in this article Actually this query is fully compliant with the XQuery and SQLXML standards and it works just fine in DB2 rnrnIf an Oracle database returns the message that this query contains an unsupportted XQuery operation ORA19110 you might want to check with Oracle support or try DB2 instead rnrnI dont know for sure but I suspect that the parent axxis in namefirst is the unsupported operation This operation is fully supported in DB2rnrnThanksrnrnMatthias 18 Apr 2013 Tinku981 HinnGreat article and thanks for clarifying XMLTable in such detail nnFrom your article the following query is giving error on Oracle 10G version 102020nnSELECT X nFROM test_emp nXMLTABLE deptemployeephone passing doc n COLUMNS n firstname VARCHAR20 PATH namefirstn lastname VARCHAR25 PATH namelastn phone1 VARCHAR240 PATH n AS XnnError ORA19110 unsupported XQuery expressionnnCan you please correct itnnThanksnTinku

O O B O O O O O O O O O O O O O O O O O O B O O O O O O O O O B O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O B O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O B O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O B O O B I O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O B I O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O


Using IBMLinkServiceLink IBMLinkServiceLink is a set of online electronic services available to customers Some of these services are available to you free of charge as a part of the SoftwareXcel basic contract Some of these services are available for an additional fee as part of the optional SoftwareXcel Extended contract Contact your local IBM marketing branch office for more information on SoftwareXcel contracts and services Using the IBM Support Center

O O O O O O O B I I O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O B O O O O O O O O


Making Your Support Needs A Priority Together At Pfizer Oncology Together we know that finding ways to save on your medicine can be overwhelming But it may be easier if youre able to research options together We can help you understand your insurance and identify what financial support may be available We can also help connect you to a specialty pharmacy to fill your IBRANCE prescription To get started just give us a call at 18449IBRANCE Commercially Insured Medicare Or Government Insured Uninsured Commercially Insured Resources for eligible commercial private employer and state health insurance marketplace patients CoPay Assistance Eligible commercially insured patients may pay as little as 0 per month for IBRANCE Enrollment is simple with no income requirements forms or faxing Limits terms and conditions apply Patients are not eligible to use this card if they are enrolled in a state or federally funded insurance program including but not limited to Medicare Medicaid TRICARE Veterans Affairs health care a state prescription drug assistance program or the Government Health Insurance Plan available in Puerto Rico Patients may receive up to 25000 in savings annually The offer will be accepted only at participating pharmacies This offer is not health insurance No membership fees apply Pfizer reserves the right to rescind revoke or amend this offer without notice For any questions please call 18777445675 visit PfizerOncologyTogethercomterms or write Pfizer Oncology Together CoPay Savings Program 2250 Perimeter Park Drive Suite 300 Morrisville NC 27560 Data current as of June 2018 To Get Started FOR LIVE PERSONALIZED SUPPORT Call 18449IBRANCE MondayFriday 8 AM 8 PM ET A diagnosis of MBC takes support Were here to help ACCESS PATIENT CAREGIVER RESOURCES Terms and Conditions By using this copay card you acknowledge that you currently meet the eligibility criteria and will comply with the Terms and Conditions described below Patients are not eligible to use this card if they are enrolled in a state or federally funded insurance program including but not limited to Medicare Medicaid TRICARE Veteran Affairs health care a state prescription drug assistance program or the Government Health Insurance Plan available in Puerto Rico formerly known as La Reforma de Salud Patient must have private insurance Offer is not valid for cashpaying patients With this card eligible patients will pay a 0 copay per eligible monthly prescription subject to a maximum amount of 25000 per calendar year The amount of any benefit is the difference between your copay and 0 After the annual maximum of 25000 is reached you will be responsible for the remaining monthly outofpocket costs This card may not be redeemed more than once per 30 days This copay card is not valid when the entire cost of your prescription drug is eligible to be reimbursed by your private insurance plan or other private health or pharmacy benefit programs You must deduct the value of this copay card from any reimbursement request submitted to your insurance plan either directly by you or on your behalf You are responsible for reporting use of the copay card to any private insurer health plan or other third party who pays for or reimburses any part of the prescription filled using the copay card as may be required You should not use the copay card if your insurer or health plan prohibits use of manufacturer copay cards You must be 18 years of age or older to redeem the copay card This copay card is not valid where prohibited by law Card can not be combined with any other savings free trial or similar offer for the specified prescription Card will be accepted only at participating pharmacies This card is not health insurance Offer good only in the US and Puerto Rico Card is limited to 1 per person during this offering period and is not transferable No other purchase is necessary Data related to your redemption of the copay card may be collected analyzed and shared with Pfizer for market research and other purposes related to assessing Pfizers programs Data shared with Pfizer will be aggregated and deidentified it will be combined with data related to other copay card redemptions and will not identify you Pfizer reserves the right to rescind revoke or amend this offer without notice Offer expires 12312020 If your pharmacy does not participate you may be able to submit a request for a rebate in connection with this offer Mail a copy of the patients pharmacy receipt indicating patient name name of medication purchased price paid and date purchased along with a copy of the patients Pfizer Oncology Together CoPay Savings Card to Pfizer Oncology Together CoPay Savings Program 2250 Perimeter Park Drive Suite 300 Morrisville NC 27560

O O O O O O O O B I I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I I O O O O B I I O O O O O O O O O O O O

pfizer oncology together
financial support
ibrance


INTERNATIONAL CIVIL AVIATION ENGLISH ASSOCIATION ENGLISH THE LANGUAGE OF THE SKIES CONFERENCE TOKYO 2019 Exploring the Aviation English training needs of abinitio pilots and air traffic controllers ramp and aircraft maintenance personnel An exchange on achievements challenges and solutions WHEN 8 10 May 2019 WHERE Hotel The Manhattan Chiba Tokyo Japan ICAEA will hold a 25day conference in Tokyo in May 2019 generously hosted by All Nippon Airways ANA This conference will explore the Aviation English language training needs of abinitio pilots and ATCOs as they prepare for and undergo training to enter the industry ground support staff working on the apron and movement area aircraft maintenance personnel engaged in all aspects of MRO operations and offer an exchange of experience of the considerations challenges and solutions when providing language training to these groups of personnel The conference will include Plenary Presentations QA Panels interactive Panel Presentations practical Workshops and networking and social opportunities SEE CALL FOR PAPERS DEADLINE 31 Dec 2018 SEE EVENT INFORMATION SEE CONFERENCE FLYER ICAO LPR TEST DESIGN GUIDELINES WORKSHOPS Assisting CAAs and test developers improve ICAO LPR testing standards Are there concerns that the tests used in your region are not of the same standard Are there difficulties in selecting developing and monitoring the quality of tests What can be done to improve standardisation equivalence and confidence in different tests ICAO LPR Test Design Guidelines Workshops Using the Test Design Guidelines ICAO LPR Test Design Guidelines A number of features are critical to the overall effectiveness validity and fairness of an ICAO LPR test ICAEAs Test Design Guidelines examine these areas in detail and how each plays a vital role in how well a test aligns with the objectives of the LPRs and best practices in specificpurpose language assessment Workshops Using the Test Design Guidelines ICAEA is scheduling a series of events for licensing authority personnel and test developers to introduce and provide practical help how to apply the Test Design Guidelines Each 25day workshop will examine the contents of the Guidelines in detail look at case studies and provide opportunities for participants to share experiences Europe Luxembourg Asia Thailand Americas Argentina FURTHER INFORMATION Register your interest Workshop ICAEA Daytona Beach 2018 CONFERENCE ERAU DAYTONA BEACH 2018 Building on the ICAO LPRs Communication as a Human Factor New Perspectives on Aviation English Training and Testing WHEN 9 11 May 2018 WHERE EmbryRiddle University Daytona Beach Florida USA hosted by This conference explored issues beyond the ICAO Language Proficiency Requirements LPRs including incorporating communication strategies into best practices for training and testing the effect of language and culture on communication as a human factor considerations for future policy developments in language and communication ICAEA MEMBERS SEE PRESENTATIONS SEE PROGRAMME SEE GALLERY JOIN ICAEA TODAY 600 members worldwide ICAEA Membership is free INFORMATION ICAEAs 2018 Conference was hosted by EmbryRiddle Aeronautical University at its campus in Daytona Beach Florida The event featured Plenary Presentations QA Panels interactive Panel Presentations practical Workshops and more informal Poster Sessions More than 120 people from 35 countries attended including representatives from airlines FTOs ANSPs CAAs universities and training and testing providers ICAEA would like to sincerely thank ERAU for its generous support of the event and all the presenters and attendees for sharing their expertise and experience as our field enters a new phase of development SUPPORTING THE USE OF ENGLISH FOR AVIATION SAFETY Our Aims Our Activities Who we are Awareness To raise awareness of the role of English in aviation safety service quality and industry efficiency Events Organise an annual program of regional forums and practical interactive workshops NonProfit Established in Europe 1991 as a worldwide nonpartisan nonprofit association Best Practice To promote best practices in ELP training and testing in all sectors of the aviation industry Representation Attend industry conferences to provide input on ELP standards and recommended practices Board Managed and overseen by a volunteer Board of industry and language experts Cooperation To provide a noncommercial platform for the sharing of expertise experience and news Projects Support projects that harmonise accepted global standards in ELP training and testing 600 registered Members operations training linguistics from 80 countries PAST EVENTS Would your organisation like to host an ICAEA event Workshop Dubrovnik 2017 hosted by Croatia Control Ltd Workshop The Azores 2016 cohosted by APPLA and Azores Airlines Forum Istanbul 2015 hosted by Turkish Aviation Academy Workshop Buenos Aires 2014 cohosted by ANAC and CIPE Show your support for aviation safety by helping ICAEA promote English language standards within the industry Contact us at eventsicaeaaero MEMBERSHIP Join 600 registered Members from 80 countries worldwide ICAEA invites aviation professionals and other industry stakeholders to join us in promoting best practices in the use training and testing of English in civil aviation Member Professions Operational Personnel Pilots ATCOs Cabin Crew Maintenance Personnel Regulators other SMEs ELP Professionals Researchers Test Materials Developers Examiners Raters Trainers Training Managers ICAEA Membership is

O O O O O O O O O O O B O O O O B I I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O B O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O B O O O O O O O O O O O O O O O O O B I I O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O B O O O O B O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O

icaea
conference
aviation english training


Intermediate Course Share this page About the Course Eligibility Registration Syllabus Students ICAI Cloud Campus BoS Knowledge Portal BoS Announcements At a Glance CA Course eSahaayataa Examinations eServices Members Know Rules Regulations PostQualification Courses Generously Contribute to CABF Know the CPE Hours credit status eSahaayataa Examinations Empanelment eServices Become Examiner with ICAI Other Imp Links Employers Understand benefits that you getRegister as an employer Upload Jobs Training AssignmentsReview CVsShortlist ApplicationsSearch for Professional Assistance Resources Download Standards View Notifications Look up Guidance Notes Interpretations Digital Learning Hub Centralized Distribution System Find Publications Free Download Publications Publications Visit the ICAI Digital Library Committee Pages Other Useful Links Events View Committee Events Look up CPE Events in my location Sign up for an Event Report on an Event Photo Gallery

B I O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O O O O O O O O O O O O O O O O O O O O O O O O O


ICD10CM Codes M00M99 Diseases of the musculoskeletal system and connective tissue M95M95 Other disorders of the musculoskeletal system and connective tissue M95 Other acquired deformities of musculoskeletal system and connective tissue 20182019 ICD10CM Diagnosis Code M9512 Cauliflower ear left ear 2016 2017 2018 2019 BillableSpecific Code M9512 is a billablespecific ICD10CM code that can be used to indicate a diagnosis for reimbursement purposes The 20182019 edition of ICD10CM M9512 became effective on October 1 2018 This is the American ICD10CM version of M9512 other international versions of ICD10 M9512 may differ The following codes above M9512 contain annotation backreferences that may be applicable to M9512 M00M99 Diseases of the musculoskeletal system and connective tissue M95 Other acquired deformities of musculoskeletal system and connective tissue M951 Cauliflower ear Approximate Synonyms Left cauliflower ear ICD10CM M9512 is grouped within Diagnostic Related Groups MSDRG v 360 154 Other ear nose mouth and throat diagnoses with mcc 155 Other ear nose mouth and throat diagnoses with cc 156 Other ear nose mouth and throat diagnoses without ccmcc Convert M9512 to ICD9CM Code History 2016 effective 1012015 New code first year of nondraft ICD10CM 2017 effective 1012016 No change 2018 effective 1012017 No change 2019 effective 1012018 No change Reimbursement claims with a date of service on or after October 1 2015 require the use of ICD10CM codes

O O O O O B I I O O O O O O O B I I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O


Home Detail of Insights Technology Disruptive Innovation in the Tourism Industry 10 07 2017 Entrepreneurship Innovation Smart Society Strategy Technology tweet Not all innovation is technological Although digital transformation has reached the tourism industry in earnest and is gradually changing jobs and customer relations it is important to understand that technology is not an end but a means and that tourism is an individual experience often shared on and offline Not all innovations are specifically sought sometimes they arise in response to a problem or need Sixty years ago the manager of a busy hotel realized it was time for breakfast and none of the staff responsible for serving it had come to work He decided to place a long table in the hall and lay out everything the guests needed to serve themselves hence the breakfast buffet was born It may not have been a technological solution but it was certainly an innovation In short to be innovative an action must mark a milestone such as Opening a new market Creating a new product Modifying an existing product Improving a production method Finding a new source of supply Creating a new form of organization Technology Transforming Jobs and Relations We live in a time of transformation a time of change in which many questions that once had simple answers have become difficult even as other questions are arising for the first time One question that is no longer simple is that of occupation Myriad new positions have emerged in response to new jobs and ways of working CMO CEO COO CFO etc Soon we will have space debris managers virtual habitat designers biohackers and even designers of human parts for 3D printing At a time when robotics and artificial intelligence are posing new challenges it is also worth asking how many of the jobs today considered normal and necessary are likely to be automated or replaced by new technologies Not all innovations are specifically sought sometimes they arise in response to a problem or need In the world of tourism one issue that has been simplified is travelling itself The sharing economy has given rise to platforms such as BlaBlaCar which has undergone exponential growth in services profits and number of users In this context we need to consider how humans are evolving in the context of a society deeply impacted by technology and at the same time how we the business world and consequently markets all work One key to understanding this whole change is that technology permeates the reasoning and experiential part of the brain much more powerfully and markedly in the new generations In the current era of digital evolution generations understand their environment and the tourism experience differently some people live in the moment interacting with all five senses at an individual level others share it with their close friends and family and still others do all that and also share it on social media in real time This reality is increasingly present Our thinking may be linear but technology and the incorporation of these habits by younger generations are exponential In a linear approach if you take one step you advance one yard if you take two you advance two yards and so on successively until you have taken fifty steps and advanced fifty yards Technology on the other hand presents us with a different reality like Moores Law it works exponentially Thus if you take one step you advance one yard if you take two steps you advance two yards but if you take a third step you will travel twice the distance as in the previous step Machine Learning Machine learning offers a new way of understanding business management The huge data and information repository we have today ie big data allows us to intelligently predict what will happen tomorrow and to access that information In other words in addition to information based on the forecasts of our hotel or businesss computer system we can access reliable information on what will happen in the future the number of reservations that will be cancelled the number of no shows we can expect and other variables that will help us adequately meet our human resource needs streamline management and deliver a technology based work methodology that uses past information to predict future events For the tourism industry big data can be very interesting from a macro perspective but it is less so at the micro level While the macro approach can provide massive amounts of information with regard to aspects such as tourist flows ultimately we are talking about individual companies which need functional information to help them make business decisions Machine learning takes the massive information available today polishes it and uses it to predict the future and meet the companys objectives In the case of hotels data are extracted from three sources the property management system or PMS hotel management software Machine learning takes the massive information available today polishes it and uses it to predict the future and meet the companys objectives WiFi Analytics and Geolocation Technology Another factor that will undoubtedly have one of the largest impacts on the tourism experience is the rise of the Internet of Things and the digitalization of places The driving force behind this reality is currently smartphones We have reached a point where before leaving home we check to make sure we have three things our wallet our house keys and our phone This shift in habits has opened up an interesting field of work in technology and innovation giving rise to solutions such as positioning beacons and beacons that can be used to identify mobile phones and thus their owners with a certain ease The next step is to use mobile apps to contact users at given points thereby generating an interaction with a place hotel leisure area city museum etc Thus it is possible to determine how much time a customer will have to wait to be served or how many have left because of the wait This information can then be used to reorganize and streamline management increasing the return and improving the service It will likewise be possible to monitor production processes in order to organize and distribute tasks more efficiently based on need For instance it will be possible to monitor a hotel cleaning process so that it can be analyzed with the same precision as a factory production line determining the actual cleaning times flows paths Apps vs Bots In the current mobile environment virtually all businesses seek to have their own app Consequently users often download apps only to delete them one or two days later In light of this reality it is important to consider why users should download a hotels app if they are only going to stay for a few nights To make it worth their while hotels should focus on value seeking additional services that encourage guests to download their app and use it with some frequency so as to establish a bond with the guest and generate a new way to increase guest However in todays fastpaced world game changers can happen overnight as when Facebook opened its Messenger platform to chatbots Because such a large percentage of people have the Facebook app on their phone the social networks decision prompted many companies to develop intelligent information systems to deliver information to customers through these bots allowing them to cover some of the services provided by many standalone apps developed especially for customers with considerably more agility These chatbots which imitate human behavior are also more likely to be used because they work with the Facebook app which customers already check daily Of course whether to use a system based on an app or a bot depends on the type of business the service being provided and the type of customer a company is seeking to serve Above all it depends on the type of people who will be overseeing the activity of these types of applications This in turn gives rise to new professions new tasks and activities that will give rise to new jobs see Chart 2 As a result of these realities not only are products changing and improving but markets and organizations are changing too The mobile startup generation is seeing exponential growth in users and revenue The next step is the Internet of Things which will surely usher in a disruptive change in how companies grow and develop The Pentagrowth Report by Ideas for Change identified five laws of growth for these new companies Connect with people situations and things Collect the smaller the effort an organization has to make to build its available inventory the bigger its growth potential Empower integrate users into the companys business processes Enable develop tools that others can use in the companys environment to create overall value Share to create a community loyal to the resource created by the company The next step is the Internet of Things which will surely usher in a disruptive change in how companies grow and develop Companies grow in relation to these laws based on what might be called the generative principles of exponential growth Reach Interaction and Resilience The Reach principle correlates the Share and Connect levers with user growth rates The organizations potential reach depends on the number of people situations and things connected through the networks on which it operates and the number of value units that users can freely share with others The Interaction principle is the result of the correlation between the Collect and Empower levers ie the number of value units included in the inventory and the number of roles that users can play Finally an organizations Resilience depends on the number of business partners that have developed their commercial offerings and lifestyles based on its standards and market and the number of people who feel a sense of shared ownership of its open resources When we analyze these levers and principles in relation to some of the most disruptive companies in the tourism industry such as Airbnb or Uber we find that they owe their initial edge to their community their exponential growth in terms of connected users These users establish different roles by incorporating their own assets such as their apartment or car into the companys centralized and intermediated offering Thus in addition to being users they become sales associates service managers and influencers all based on an enormous network undergoing exponential growth driven by user feedback Rodrigo Martínez CEO of Hotel Servicers and Professor at IE Business School IE Insights Keep reading Insights Wanted Digital Leaders In this conversation Cristina Álvarez and Borja González del Regueral discuss the indepth reflection process 11 12 2018 Strategy Talent Technology Insights Human Resources Point of Contention or Opportunity in a New Environment By Cristina Simón People management an essential function for companies is now done in a VUCA environment 29 11 2018 Competitiveness Growth Strategy Talent Insights On disruption With Patrick Stal Head of Marketing EMEA at Uber 27 11 2018 Competitiveness Growth Entrepreneurship Innovation Insights The Design of Spaces in Successful Organizations Lola Hoya converses with William Gaber about the advantages of efficient design in organizations 21 11 2018 Strategy Talent Insights On Artificial Intelligence With Stéphane Canu Professor at the INSA Rouen Normandie 19 11 2018 Innovation Technology Insights Intergenerational Entrepreneurship Rejuvenating Family Business By Enrique Ogliastri The new generations tasked with leading family businesses must surpass a major hurdle coming up 16 11 2018 Competitiveness Growth Entrepreneurship Innovation Strategy

O O O O O B I O O B I O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O