1. ©1995-2002 i2 Technologies, Inc. PROPRIETARY SCM Subsystem and ODS Section 03

2. ©1995-2002 i2 Technologies, Inc. PROPRIETARY SCM Subsystem and ODS  The Objectives of this section are to:  Give an overview of the SCM subsystem and the Operational Data Store  Describe technology and ways to load the ODS  Define basic SCM building blocks and terms  Provide an understanding on modeling for TmAPI based solution  Describe InstanceFilter and UserArea in TmAPI

3. ©1995-2002 i2 Technologies, Inc. PROPRIETARY SCM Subsystem and Operational Data Store Concepts and Definitions

4. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Subsystems Planning Sub-system SCM Collaboration Sub-system CRM Design Source Sub-system SRM ERP Sub-system (SAP) ODS Explore Role based Common User Interface Legacy Sub-system (OS390) OMx IMx ETL-Bulk Data Transfer (back) Bus Common Integration Services … Transactional Platform Firewall … Public Interne t Content/FreightMatrix Exchanges TMOCN Trading Partners Enterprise Messaging (front) Bus Work flow Each subsystem is a logically complete set of functionality Subsystems have adapters that expose “services” interface All subsystems have a well defined and complete interface to front and backbus

5. ©1995-2002 i2 Technologies, Inc. PROPRIETARY SCM Subsystem and ODS  A subsystem encompasses a set of products with their own persistent storage, the Operational Data Store (ODS).  The ODS is used for persistence and to form a logically and functionally complete group within the SCM Subsystem.  The ODS is designed to be a single source of planning data for i2 planning applications within SCM, and also to provide integration among these applications.  ODS is a physical data-schema, which  Enables data-persistence in a database for memory-resident engines  Contains integration entities for SCM

6. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ODS and ODS Services WORKFLOWMGMT ODS ERP ODS Loader Read Service Write Service SCP Instance Filter ROI Adapter/AppMgr FP Adapter/AppMgr TmAPI

7. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ODS Services  ODS Services  ODS Loader Service  To load data into the ODS  Read and Write Services  To read data from the ODS to the Application Engine  To write data from Application Engine to the ODS  Instance Filter Service  Instance filtering service for control of data flow to applications

8. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ODS  Logical and Physical Schemas are different  Any changes to the ODS schema will be hidden from the user  The complicated and changing ODS schema will be transparent to the users/customers  No direct manipulation of data in ODS  You have to go through ODS Service – ODS Loader TmAPI ODS Service ODS Schema

9. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Creating the ODS Schema  In order to load data in ODS we need to first create the ODS schema in a RDBMS.  For class we have Oracle 8.1.7 installed for this purpose.  The script which creates the ODS schema is located in  D:\i2\ODS\6.0\DDL  Depending on your Database Type, i.e. Oracle, DB2 etc. you will find scripts to create the ODS schema for your corresponding database.

10. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Exercise 0: Creating the ODS Schema Lab  In this exercise students will be introduced to the creation of the ODS Schema using SQL in Oracle.

11. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Operational Data Store Loading/Importing to ODS

12. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ODS Loader  The ODS Loader is a tool that enables loading the Operational Data Store with data.  Data is received by the ODS Loader in the TMAPI format.  TmAPI data is mapped to the ODS format and inserted into ODS.  ODS Loader uses surrogate keys to setup relationships within the database.  Mapping from TMAPI to ODS records involves:  looking up the surrogate keys based on the incoming TMAPI data.  Adding the surrogate keys to the TMAPI data to create a ODS record.

13. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ODS Loader Files  The ODS Loader Files are located in: D:\i2\scm_ce\6.0\Infrastructure\OperationalDataStore\ods_default\c onfig odsConfig.xml odsServicesConfig.xml

14. ©1995-2002 i2 Technologies, Inc. PROPRIETARY odsConfig.xml  Parameters that can be set in the configuration file:  Database Parameters ods jdbc:oracle:thin:@localhost:1521:training

15. ©1995-2002 i2 Technologies, Inc. PROPRIETARY odsServicesConfig.xml  Import Directory Path to the input files D:/i2/scm_ce/6.0/ods_data/sample_integrated_dataset  Log Directory Path to the log files ${ODS_INSTANCE_PATH}/log/loader_error.log  Directory Path to the input files that had errors ${ODS_INSTANCE_PATH}/log/bad

16. ©1995-2002 i2 Technologies, Inc. PROPRIETARY odsServicesConfig.xml, cont.  Import File Option Parameters:  Delimiter Option:  You can specify the delimiter that you will be using in your flat files.  We will be using the “,” delimiter.  ReadFieldsFromFirstLine Option:  If “TRUE”  ODS Loader will read the first line, header-line, to identify the fields to be imported into ODS.  The fields in the header-line have to match the logical schema field names.  The header-line is not case-sensitive.  If “FALSE”  There should be no header or comment line.  You will have to specify each field for each table that should be imported into ODS with the appropriate sequence number.  You can NOT selectively apply True and False option to different tables.

17. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Date Formats supported by ODS Loader  The following date formats are supported by the Loader.  MM/DD/YY [hh:mm:ss]  Example: 01/01/02 00:00:00 or 01/01/02 are valid using this format. Months, dates and years that are single digits have to be padded with a '0' to the left as in the example above. If hh:mm:ss is left blank then the default time assumed is 00:00:00. The time zone assumed is the time zone of the machine on which the loader is executed.  MM/DD/YYYY [hh:mm:ss]  Example: 01/01/2002 00:00:00 or 01/01/2002 are valid using this format. Months and dates that are single digits have to be padded with a '0' to the left as in the example above. If hh:mm:ss is left blank then the default time assumed is 00:00:00.  YYYY-MM-DD [hh:mm:ss][TimeZone]  Where [TimeZone] - to indicate the time zone of the date time specified.  The time zone assumed is the time zone of the machine on which the loader is executed.

18. ©1995-2002 i2 Technologies, Inc. PROPRIETARY TmAPI Modeling Concepts and SCM Modeling

19. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Some Basic TMAPI Terminology  Site  The physical location of the items/resources in the supply chain.  Item  An Item models a kind of material, part, component, subassembly, assembly, or good which has particular characteristics that define how it can be built, stored, processed, or used.  Flow  These are the flows to the item that are produced or consumed by the Operation.  Buffer  A Buffer models the management of the flow of interchangable Items. Buffer handles most of the material/inventory planning functionality.

20. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Some Basic Terminology, cont.  Operation  An Operation models a process, activity, or action that transforms or moves Items. This results in a flow into, out of, or between buffers. Operations may require Resources with specific Skills, modeled by Loads. Those Resources model the capacity to perform Operations. Flows model the flow of Items to and from Buffers that result from Operations.  Routing  A routing operation has a sequence of sub-operations  Resource  A Resource models the capacity to perform Operations. This includes machines, tools, fixtures, labor, trucks, molds, dies, masks, and other things that are used by Operations in causing Flow between Buffers. It also includes storage space, containers, racks, and other things that are used to hold Items within Buffers or during Operations.

21. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Some Basic Terminology, cont.  BOM  Bill of material - how a product may be assembled, produced, or procured.  BOMComponents  The Components consumed by the BOM  BOD  Bill of Distribution – how a product may be distributed from different physical sites to other physical sites, for example to warehouses, distribution centers etc.  ItemBomRouting  A BOM, Routing, Operations and Resources linked together in a site to produce an item

22. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Basic Constructs Resource Item A triangle represents an item. It is always drawn within a site. A reverse triangle represents a resource.

23. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Flows 1/1-9/1 6/1-9/1 1/1-6/1 This represents an AND. This represents a date-effective AND. The 2 effective ranges are: 1/1-6/1 : Both the top arrows are effective in this range. 6/1-9/1: The top and the bottom arrows are effective in this range.

24. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Flows 2 3 1 This represents an OR. Note, the dotted line together with the solid line represents an OR. A solid line is assumed to be the primary. One can have multiple dotted lines to represent multiple ORs. This represents an AND. One component in the AND has 2 alternates. The alternates are represented as OR with the specified priorities.

25. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Operations and Routings This represents an operation. It always is drawn within a Routing. This represents a routing. A routing will contain operations linked together by arrows. Operation Operation 1 Operation 2 Routing

26. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Sites This represents a Site. A site contains routings, items and resources. Site

27. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ItemBomRouting with Alternates This diagram represents ItemBomRouting. Item1 is produced using BOM 1 and Routing 1. Routing 1 has 2 operations Operation 1 & Operation 2. Operation 1 can use 2 resources Resource 1 or Alt Res 1. Operation 2 uses Resource 2. Items 2&3 are consumed by Operation 1. Item 4 is an alternate to Item 3. Operation 1 Operation 2 Resource 2 Resource 1 Alt Res 1 Item 1 Item 4 Item 3 Item 2 Routing 1 Bom 1 Site 1

28. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ItemBomRouting with Group Substitution This diagram represents ItemBomRouting. Item1 is produced using BOM1 and Routing1. Routing1 has 2 operations Operation 1 and Operation 2. Operation 1 can use 2 resources Resource 1 or Alt Res 1. Operation 2 uses Resource 2. Items 2&3 are consumed by Operation 1. Item 4 is an alternate to Items 2&3. Item 5 is an alternate to Item 4. Note priorities can be mentioned on the arrows. If no priorities are mentioned then it is assumed that the solid arrow is the primary. Operation 1 Operation 2 Resource 2 Resource 1 Alt Res 1 Item 1 Item 4 Item 3 Item 2 Routing 1 Bom 1 Site 1 Item 5

29. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ItemBomRouting with BomComponent Effectivities This diagram represents ItemBomRouting. Item1 is produced using BOM1 and Rtg1. Rtg1 has 2 operations -op1&op2. Op1 can use 2 resources res1 or altres1. Op2 uses res2. The BOM components are Item1, Item2 and Item3. However not all are effective simultaneously. From 1/1-6/1 Item2 and Item3 are used. From 6/1-9/1 Item2 and Item4 are used. Operation 1 Operation 2 Resource 2 Resource 1 Alt Res 1 Item 1 Item 4 Item 3 Item 2 Routing 1 Bom 1 Site 1 1/1-9/1 1/1-6/1 6/1-9/1

30. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Documentation  Each exercise requires you to study the task at hand using the TmAPI Modeling Manual  Go to D:\i2\docs\ce  Double click on home.htm  Click on Supply Planning -> Operation Planning -> Master Planning  Click on the *.pdf SCP with SCP withTmAPI Modeling Guide

31. ©1995-2002 i2 Technologies, Inc. PROPRIETARY TmAPI Modeling Manual

32. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Modeling Exercises  Each exercise will have 2 sections  Hands-on  You will be required to populate the appropriate files with data. The physical files with the header have been provided.  Self-study  Some files with data already populated have been given to you. Please review these and refer to the TmAPI modeling manual  You will be expected to load the dataset for each exercise into ODS using the ODS Loader.

33. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Notes  Location of the directory for the exercises – Contains the files to be modified  Located under D:/local/Exercise /  The solution to the corresponding exercise is located under the SOLN directory D:/local/Exercise /Soln

34. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Top Level Modeling Relationship

35. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Top Level Modeling Constructs  The following information is required to create the Top Level Models in TmAPI:  EnterpriseMaster  SupplyChainMaster  OrganisationMaster  SiteMaster  OrganisationSiteRelationship  PlanMaster  ItemMaster  ItemSiteMaster

36. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Exercise 1A: Top Level Models Lab  In this exercise, students will be introduced to the Top Level Entities in TmAPI. Students will use the TmAPI modeling manual to create the Top Level Scenario data files.

37. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Bill of Material Models Relationships

38. ©1995-2002 i2 Technologies, Inc. PROPRIETARY BOM with simple alternate Constructs  You need to fill up the information for the following  BOMHeader  BOMComponents  BOMComponentsAlternate

39. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Exercise 1B: Bill of Material with Simple Alternates Lab  In this exercise, students will be introduced to the concept of BOM (Bill of Materials) entities. Students will use the TmAPI modeling manual to create the BOM and work on simple alternates.

40. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Bill of Material Models Relationships

41. ©1995-2002 i2 Technologies, Inc. PROPRIETARY BOM with alternates (Group Substitution)  You need to fill up the information for the following  BOMHeader  BOMComponents  BOMComponentsAlternate

42. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Exercise 1C: Bill of Material Lab  In this exercise, students will be introduced to the concept of BOM (Bill of Materials) group substitution of alternate parts. Students will use the TmAPI modeling manual to understand this BOM Group Substitution concept.

43. ©1995-2002 i2 Technologies, Inc. PROPRIETARY ItemBomRouting Relationships

44. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Routings, Operations and Resources – Schema Relationships  Alternate resources can be specified for a primary or an additional resource  Additional resources can be specified for a primary or an alternate resources

45. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Routings, Operations and Resources – Constructs  You need to fill up the information for the following  RoutingHeader  RoutingOperation  ItemBOMRouting  WorkCenterMaster  WorkCenterDetail  ResourceMaster  OperationResource  OperationResourceAlternate

46. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Exercise 1D: ItemBomRouting Lab  In this exercise, students will be introduced to the concept of Routing, Operations, IBR (Item BOM Routing) and Resources entities. Students will use the TmAPI modeling manual to facilitate and understanding and create the necessary datasets.

47. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Bill of Distribution Relationships

48. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Bill Of Distribution Constructs  You need to fill up the information for the following  BODHeader  BODDetail  TransportMode

49. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Exercise 1E: Bill of Distribution Lab  In this exercise, students will be introduced to the concept of BOD (Bill of Distribution) entities. Students will use the TmAPI modeling manual to create the BOD.

50. ©1995-2002 i2 Technologies, Inc. PROPRIETARY TmAPI Instance Filters and User Defined Fields

51. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Data Filtering - Instance Filter Overview  During your implementation you may have multiple planning engines, some of which may even have multiple instances.  It becomes important to identify particular data entities in the ODS to belong to or in some cases to be shared by particular application instances.  In TMAPI filtering data for an application instance is defined using InstanceCriteria Service in ODS.  Instance Filter identifies data which is unique to an instance or shared by multiple instances on the basis of particular criteria.  The criteria are specified in terms of psuedo SQL for each instance of an application.  InstanceMaster and InstanceCriteria are tables in TmAPI.

52. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Instance Filter  How is the user going to use Instance Filter Service?  User identifies all application instances that will be implemented for the project.  InstanceMaster Table  User specifies filter criteria for top level entities.  InstanceCriteria Table  The criteria will be propagated to the child tables.  Separate criteria can be specified on child tables.  This will override the criteria for top level entities.  User runs the Instance Filter criteria utility.  Engine_ID fields will have been set by the InstanceFilter utility.

53. ©1995-2002 i2 Technologies, Inc. PROPRIETARY The Instance Filter Service  The InstanceFilter Service requires the InstanceMaster and InstanceCriteria tables to be loaded into the ODS so that the it can apply the criteria to the records.  InstanceMaster defines  INSTANCEID  Unique name of the instance  BITPOSITION  Unique position value for the instance. Maximum value allowed is 92. Thus users can at a maximum have 92 instances  APPLICATIONNAME  Application used for this instance For example: FP, SCP, DF, DP, PC, DC etc.  It is desired to have the list of entities used by an application defined in the ApplicationEntityMap.dat file located in D:\i2\scm_ce\6.0\Infrastructure\OperationalDataStore\ods_default\config\system _config

54. ©1995-2002 i2 Technologies, Inc. PROPRIETARY The Instance Filter Service, cont.  InstanceCriteria  Defines the filter criteria for each entity a particular INSTANCE reads  There are Two filter types, FILTERTYPE:  Filter  Join  The Criteria, or FilterStatement, contains the “where” clause in SQL for the corresponding FILTERTYPE, i.e. FILTER or/and JOIN clause.  If there is no criteria defined in InstanceCriteria for an instanceid then all the records will be selected.  A criterion is automatically applied to the child tables.  The user can also define additional criterion for any child entity.

55. ©1995-2002 i2 Technologies, Inc. PROPRIETARY The Instance Filter Service, cont. How does the InstanceFilter Service compute the Engine_ID? Bit Position: This field is used for calculating the Engine_Id that is associated with a specific engine.

56. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Exercise 2: Instance Filter Lab  In this exercise, students will be introduced to data filtering in ODS using the InstanceFilter Service.

57. ©1995-2002 i2 Technologies, Inc. PROPRIETARY USERAREA  The USERAREA enables user/customer specific fields in ODS by allowing simple extensions of the schema.  It is used to bring in additional information into the i2 world which could potentially be used in a manual decision-making /communication process.

58. ©1995-2002 i2 Technologies, Inc. PROPRIETARY Exercise 3: User Defined Fields Lab  This exercise provides an understanding on how to create User Defined Fields and how to update Data for these new fields into ODS.