Urban Outfitters will require direct SQL access to the databases. Service provider will furnish an Entity Relationship Diagram (ERD) for the database after implementation. In addition, updated versions will be provided as changes are made to the solution over time. The allocation system will support a multi-brand implementation (currently Urban Outfitters, Anthropologie, and Free People) which maintains a master merchandise view that supports enterprise-wide reporting and analysis, but that allows brand-level analysis and maintains privacy between brands where appropriate. A brand’s own audience should be its primary view into the database, but sales data from other brands should still be available for comparison, analysis, and selection. For example, Free People may want to use the sales history for a similar tank top that was carried by Anthropologie as the sales basis for the allocation of the Free People tank top. The system will be constructed to easily support expansion of the data model to include new data elements as well as additional brands in the future. 1.4.2 Historical Data Conversion Assumptions: The following highlights the general guidelines and assumptions that will be followed in the conversion of historical sales data from Island Pacific to the new allocation system. HISTORICAL DATA CONVERSION ASSUMPTIONS No formal database will be migrated, but rather a host of different source system historical data elements will be extracted and loaded to build tables in the allocation database. Approximately 2 years of daily history will be converted to the line item detail level for retail sales (currently planned to take data starting from 6/1/2008 to present). UOI may adjust this date forward depending on the system implementation timeline. 18 months of merchandise and assortment plan data will be converted and imported (currently planned to take data starting from 12/1/2008 to present). UOI may adjust this date forward depending on the implementation timeline. It should be assumed that no unique purchase key exists (for distros). A purchase order ID is provided by the order management system (IP), but because of duplication issues where PO numbers are reused, PO records should not be considered unique. Other keys such as PO receipt date and vendor ID will be available. Data transformations may be required to establish unique consistent keys during the historical load of data. All historical customer records loaded will have the agreed-upon data validation rules applied to them prior to loading.
Urban Outfitters will require direct SQL access to the databases. Service provider will furnish an Entity Relationship Diagram (ERD) for the database after implementation. In addition, updated versions will be provided as changes are made to the solution over time. The allocation system will support a multi-brand implementation (currently Urban Outfitters, Anthropologie, and Free People) which maintains a master merchandise view that supports enterprise-wide reporting and analysis, but that allows brand-level analysis and maintains privacy between brands where appropriate. A brand’s own audience should be its primary view into the database, but sales data from other brands should still be available for comparison, analysis, and selection. For example, Free People may want to use the sales history for a similar tank top that was carried by Anthropologie as the sales basis for the allocation of the Free People tank top. The system will be constructed to easily support expansion of the data model to include new data elements as well as additional brands in the future. 1.4.2 Historical Data Conversion Assumptions: The following highlights the general guidelines and assumptions that will be followed in the conversion of historical sales data from Island Pacific to the new allocation system. HISTORICAL DATA CONVERSION ASSUMPTIONS No formal database will be migrated, but rather a host of different source system historical data elements will be extracted and loaded to build tables in the allocation database. Approximately 2 years of daily history will be converted to the line item detail level for retail sales (currently planned to take data starting from 6/1/2008 to present). UOI may adjust this date forward depending on the system implementation timeline. 18 months of merchandise and assortment plan data will be converted and imported (currently planned to take data starting from 12/1/2008 to present). UOI may adjust this date forward depending on the implementation timeline. It should be assumed that no unique purchase key exists (for distros). A purchase order ID is provided by the order management system (IP), but because of duplication issues where PO numbers are reused, PO records should not be considered unique. Other keys such as PO receipt date and vendor ID will be available. Data transformations may be required to establish unique consistent keys during the historical load of data. All historical customer records loaded will have the agreed-upon data validation rules applied to them prior to loading.
artifact4.docx