it product genetics & inventoriable simplicity

Advanced Design & Cure for the Unrealized Promise of IT in the Product Distribution Enterprise {PDE} Sector

The Aggregate Bicameral Core Op System Model

IT Product Genetics & Inventoriable Simplicity

David Goran [email protected]

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDiBASKETTM PDMANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDMANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PD

Unique Process ~ Unique Functionality ~ Unique Interface

Unique Model ~ Unique Paradigm

CURE NOT TREATMENT

DAVID GORAN SHEDLACK 2005 Do Not Copy - Unauthorized Distribution Prohibited

©

1

CONTENTS

Unrealized Promise………………………………….

2

Focus………………………………………………...

3

Systemic Problem……………………………………

5

Cure Not Treatment…....……………………………

7

Core Op Centric Architecture………………………..

9

Advanced Metric.…………………………................

12

Product Genetics...…………………………………...

15

Aggregate Dynamics…………………………………

17

BPDMTM Efficiency………………………..................

20

BGUITM Simplicity …………………………………..

26

iBTM IP………………………………………………..

28

MANUFACTURING

PDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDiBASKETTM PDMANUFACTURING

PDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDMANUFACTURING

PDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDiBASKET BICAMERALTM

… unrealized promise ...

“ leaner, lighter, more efficient operations ”

In the last 30 years Product Distribution Enterprises have implemented Conventional Information Systems (ERP, MRP…) to facilitate or improve operational management.

Directly attributable improvements in efficiency or realized profits have been minimal at best. Indeed, real profit (%Net) has often decreased while related operational costs have soared!

Why?

In the last 30 years Product Distribution Enterprises have implemented Information Management Systems (ERP, MRP…) to facilitate and improve operational management.

Directly attributable improvements in efficiency or realized profits have been minimal at best. Indeed, real profit (%Net) has often decreased while related operational costs have soared!

Why?

“ ….. bad data costs ….. ”

“Executives know that bad data costs the CPG and retail industry an estimated $40 billion a year.”

“Many organizations have endeavored to address the challenges of achieving and maintaining a

single version of the truth with item information.”

“……. few have gone about it the right way (simply treating the problem not eliminating its cause),

preferring to invest in external data synchronization (and/or data integration) and ignoring the much

more difficult task of laying the (strategically permanent) groundwork and internal infrastructure for

supporting good product information.”

“Sending the right item information out and receiving clean data in return is the objective of the

industry mandate around global data synchronization.”

“However, clean data comes from within …..”

Copyright 2005, the Yankee Group. All rights reserved.Reproduced with permission

T H E

G R O U P


©

2


©

3

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDiBASKET BICAMERALTMFocus

Any Enterprise That Produces Or Sources And Markets Any Product

Product Distribution Enterprise (PDE)

WHOLESALEtypePDE

Products Sourced

CONVERTINGtypePDE

Products Produced

RETAILtypePDE

Products Sourced

MANUFACTURINGtypePDE

Products Produced COMMONCORE

OPERATIONS

DEFINEProduct Introduction & Identifier Establishment

TRACKProduct Search & Select

TRANSACTProduct Acquisition & Sale

REPORTProduct Inventory Status

PDE

©

4


All

Product Distribution Enterprises employing an implemented information management system share a common requirement that the system provide functionality for the management of these particular Core Operations (Core Op).

A Systemic Problemand principal source of the unrealized promise of IT in the Product Distribution Enterprise Sector is directly traced to the

Product Definition (PDef) &

Operational Product Information Management (OPIM) functionality mechanisms as found in most currently implemented PDE information systems.


©

5

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDSystemic Problem


©

6

Bad product data does not simply happen … it must be created!

Product Definition (PDef) and Operational Product Information Management (OPIM) provided to Product Distribution Enterprise (PDE) through current information systems are effective.

They are not efficient!

The nature of this problem is ‘internal of process’ and not ‘external of technology’.

Therefore, notwithstanding the current positive activity in such bundled external technologies as RFID, Data Synchronizationand Data Integration which are often put forward as solutions, this cost/loss factor will persist and grow dramatically absentintroduction of a new, advanced and strategically focused ‘internal process’ system model that is both effective and efficient!

The iBasketTM Aggregate Bicameral Core Op System presents such a model!

As early as 2002 an A.T. Kearney study established that over $40 billion annually are wasted due to Bad Product Data.Findings confirmed the source to be how enterprise products are defined and operationally managed in the system.

3.5 percent of total sales are lost annually due to supply chain information inefficiencies. 30 percent of the item information found in product distributors catalogs is incorrect,

with each error costing $60 to $80 dollars. 25 minutes per SKU is spent each year to cleanse product information. 60 percent of all invoices contain errors. 43 percent of all invoice errors result in deductions being paid by the manufacturers. because the process of rolling out new product information is so slow, it takes an

average of four weeks for product distributors to update their systems with it. global product distributors handle thousands - perhaps millions of SKUs, of which 35

percent are changed annually.

~ OPIM

Product Definition & Operational Product Information Management

PDef


©

7

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDiBASKET BICAMERALTMCure Not Treatment

iBasketTM Bicameral

introduces uniquely flexible core op centric architecture.

delivers more efficient less complex product definition functionality.

replaces manually executed with system generated processes.

reduces all product master data creation and storage costs by 90%.

significantly reduces operational user entry requirements.

dynamically provides system maintained product data granularity.

auto-generates product variation identifiers (item, ver, SKU).

enables a less complex yet more efficient user interface.

improves productivity and eliminates errors.

sharply increases same sales operating profits.

iBasketTM Bicameral

Core Operations Management System

Product Distribution Enterprise

Representing a major paradigm shift in Product Distribution Enterprise IT the iBasketTM Bicameral System delivers a uniquely more efficient less operationally complex product data information management.

By design all product data creation & requisite data storage is reduced by 90% as compared to current legacy systems. Massive losses sustained as a result of the ever increasing level of errors in product-related data retrieval are eliminated.

is a fundamental solution that reverses this reality using far fewer resources than are currently used to create it!

iBasketTM Bicameral

Bad product data being created in the Product Distribution Enterprise Sector globally

is directly responsible for costs and losses that are enormous and growing!

A strategic Expert System, introducing unique process,its primary focus is the required Core Operational functionalities of a Product Distribution Enterprise

taking in Product Definition, Tracking, Transaction and activity/status Reporting.

iBasketTM Bicameral is uniformly applicable across the entire Product Distribution Enterprise Sector … Manufacturing, Converting, Wholesale and Retail Product Distribution.

The elimination of excessive sustained losses derived from understandably error prone users required to work within ‘too complex’ current system models is but one of many iBasketTM paid dividends.

The iBasketTM Bicameral System does more than simply store product data. It creates and delivers product data intelligently!


©

8

CURE NOT TREATMENT

Unique Process ~ Unique Functionality ~ Unique Interface

Unique Model ~ Unique Paradigm


©

9

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDiBASKET BICAMERALTMCore Op Centric Architecture


©

I.FINANCIALS

II.OTHER

SRM

POS

BPM

EAM

BI

BOM

LOG

MPL

EPCMMS

EPM

MRPCPM

HRM

CRM

PLM

I.FINANCIALS

II.OTHER

SRM

POS

BPM

EAM

BI

BOM

LOG

MPL

EPCMMS

EPM

MRPCPM

HRM

CRM

PLM

MANUFACTURINGPDE

Products Produced

WHOLESALEPDE

Products Sourced

I.FINANCIALS

II.OTHER

SRM

POS

BPM

EAM

BI

BOM

LOG

MPL

EPCMMS

EPM

MRPCPM

HRM

CRM

PLM

I.FINANCIALS

II.OTHER

SRM

POS

BPM

EAM

BI

BOM

LOG

MPL

EPCMMS

EPM

MRPCPM

HRM

CRM

PLM

RFID

PIM

PPMMRPII

SCM

WMS RFID

PIM

PPMMRPII

SCM

WMS

RFID

PIM

PPMMRPII

SCM

WMSRFID

PIM

PPMMRPII

SCM

WMS

RETAILPDE

Products Sourced

CONVERTINGPDE

Products Produced

10

Current Information Management Systems Architecture Emphasizes Financials Functionality at the System Center

The 2 section architecture of current information system ‘constructs’ provides no unique section as such to Core Op functionality.

FINANCIALS functionality is formed in a first section I OTHER functionality (all other) is then randomly formed in a second section II

This ‘financials-centric’ format has resulted in disparate and complex systems being provided to the PDE Sector that have proven to be both inefficient and costly as regards to overall system Core Op and GUI functionality.

Current


©

11

iBasketTM Bicameral Architecture Places Core Op Functionality at the System Center

EAM MRPII

PPMRFID

EPM

BOM

HRMCPM

EPMPL

CRM

FINANCIALSIII.

II.TYPE SPECIFIC

&/or

ELECTIVE

PIM

SCM

BI

WMS

LOG

MRP

PLM

SRM

POS

CMMS

BPM

CORE OP

DEFINEProduct Introduction & Identifier Establishment

TRACKProduct Search & Select

TRANSACTProduct Acquisition & Sale

REPORTProduct Inventory Status

I.

RETAILPDE

Products Sourced

WHOLESALEPDE

Products Sourced

MANUFACTURINGPDE

Products Produced

CONVERTINGPDE

Products Produced

Original 3 section architecture of the iBasketTM Bicameral ‘construct’ provides an additional section of functionality. CORE OP functionality is formed in this new first section I PDE TYPE-SPECIFIC &/or ELECTIVE functionality is formed in a peripheral second section II FINANCIALS functionality is repositioned and formed in a binding third section III

This ‘core op-centric’ format assures delivery of a less complex ‘Universal to PDE’ applicable solution whose ‘construct’ brings a uniquely efficient performance metric to all aspects of OPIM (Operational Product Information Management) functionality.

iBasketTM


©

12

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBASKETTM PDAdvanced Metric


©

13

CurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystems


Current

Designed and built around a singular Individualized product definition (PDef) data format the Operational Product Information Management construct of Current Information Systems produces an inefficientoperational Product Data Management Performance Metric, one which results in higher than necessary costs, an ever

increasing rate of errors and an extensive requisite investment in add-on corrective product data Integration.

Product Data Management Performance Metric

PROC

ESS

STOR

AGE

EXTRACT

INTEGRATIONCOSTS

INPUT

INDIVIDUALIZED

PRODUCT

DATA

MANAGEMENT

Effective NOT Efficient!

Current Systems is

product data INPUT Maximized product data PROCESS Minimized product data STORAGE Maximized product data EXTRACT Complex product data INTEGRATION COST Extensive

Individualized Product Definition

Data Format


©

14

Product Data Management Performance Metric

Designed and built around an original Aggregated to Individualized product definition (PDef) data format the Operational Product Information Management construct of the iBasketTM Bicameral System produces a uniquelyefficient operational Product Data Management Performance Metric which delivers greatly reduced costs, eliminatesthe currently ever increasing rate of errors and requires NO investment in add-on corrective product data Integration.

iBasketTM

Bicameral iBasketTM Bicameral iBasketTM Bicameral iBasketTM Bicameral iBasketTM Bicameral iBasketTM Bicameral iBasketTM Bicameral iBasketTM Bicameral iBasketTM Bicameral iBasketTM Bicameral


Effective AND Efficient!

iBasketTM System is

product data INPUT Minimized product data PROCESS Maximized product data STORAGE Minimized product data EXTRACT Simplified product data INTEGRATION COST Nil

PROC

ESS

STOR

AGE

INPUT

AGGREGATED

PRODUCT

DATA

MANAGEMENT

EXTRACT

dynamic

>>>

Dynamically Allocated Individualized

Product Definition Data Format

Assigned iBasketTM

Aggregated Product Definition

Data Format


©

15

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

Product Genetics


©

16

The harmonization of two (2) Product Definition Formats

Aggregated & Individualized

both operating simultaneously within the same system with the system uniquely designed and configured to functionally optimize use of the two (2) formats.

The user first introduces a singularly-referenced Aggregated Format of the product definition into the system. The system subsequently, operationally, dynamically and temporarily generates each corresponding and singularly-

referenced Individualized Format, then tracks and manages it, and permanently record-retains it as required.

BPDMTM

BICAMERAL PRODUCT DEFINITION MECHANISM TM

Product Definition Form ‹› Product Definition Substance

Each variation of the same product is ‘a’ product … but not the ‘whole’ product!

To realize the primary Core Op functionality of Product Definition with minimum user input and maximumsystem processing, iBasketTM Bicameral uniquely and simultaneously employs two (2) Product Definition Formats …

Aggregated (a ‘collection of’ all of the ‘enterprise determined available’ product related attribute values)

& Individualized

(a ‘selection from’ all of the ‘enterprise determined available’ product related attribute values) A unique Bicameral Product Definition MechanismTM or BPDMTM

enables operational product data delivery in either of these two Product Definition Formats and requires only one tenth the operational resources current systems take in their delivery of just one.

Singularly-referenced, aggregated, configurable and transactable data element structures referred to as iBasketsTM constitute the Product Definition Substance.

The Bicameral Product Definition MechanismTM (BPDMTM) through which these iBasketsTM

are generated constitutes the Product Definition Form. iBasketsTM are individually assigned and each uniquely represents one product (all variations of) in the system.

The iBasketTM data element structures and the BPDMTM are original to the iBasketTM Bicameral System. Both technologies are applicable to all Product Distribution Enterprise (PDE) types and all product types.

In iBasketTM

PRODUCT is defined as being an Aggregate of Items … an Aggregate of its ‘enterprise determined available’ variations. ITEM is defined as being an Individual product variation.

All products have characteristics (Name, Description, Source, Measure, Attributes …) Attribute type characteristics consist of two (2) elements:

Attribute Family (AttF) - the attribute group name identified (e.g. Color) Attribute Values (AttV) - the ‘enterprise determined available’ & selectable group values (e.g. Red, White, Blue …)

When one or more product-assigned Attribute Families are assigned ‘enterprise determined available’ selectable Attribute Values providing for variations of the product,

the ‘whole’ product or PRODUCT in the iBasketTM Bicameral System is effectively the Aggregate

of all those variations of the product as ‘enterprise determined available’.

Product Genetics


©

17

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

Aggregate Dynamics


©

18

Effective NOT Efficient!

In Current Information System (ERP, MRP…) data sets the codes and identifiers of each of the ‘enterprise determined available’ variations

of the same ‘whole’ product are always pre-allocated … manually!

Current Information Systems (ERP, MRP …) make no distinction between ‘whole’ product and product ‘variation’.If at all, the terms are seen functionally as being synonymous. They are both simply ‘products’.

Singular even simply Primary use of this Individualized model has produced Current Information Systems (ERP, MRP …) for the PDE Sector that though effective in meeting the granularity requirement, are certainly not efficient as to how!

They are costly to operate and their complex constructs are a principal source of substantial and increasing enterprise loss due to operational errors - both human and system derived.

Additionally, this construct requires that the user not only create but also operationally work exclusively with the unique pre-allocated tracking reference (identifier) assigned each ‘enterprise determined available’ variation of the

same ‘whole’ enterprise product. Any Product Distribution Enterprise employing a current information system must support the extremely high

fixed costs in human resources consumed by this extensive, complex and user-generated back end product data modeling/entry/extract process, as well as the staggering level of investment in product data storage it entails.

This lack of distinction and the universal requirement to insure full product data granularity has seencurrent information systems effectively limit initial and too often sole operational product definition within the system to

individual ‘enterprise determined available’ product variations only … this referred to as Individualized format! Such a design construct requires exponential amounts of very detailed, costly to enter product data

be introduced into both the process and the system … most often user introduced!

The primary often singular use of an Individualized format in current information system constructs assures that thesesystems will continue to be inherently complex and time consuming as regards functionality and operational user interface.

The requirement to feed large recurring volumes of complex product data into an equally complex data model renders operational efficiency very low and the incidence of human error excessively high!

Manual Allocation

Current

Effective AND Efficient!

In iBasketTM Bicameral System data setsthe codes and identifiers of each of the ‘enterprise determined available’ variations of the same ‘whole’ product are always dynamically allocated … by the system!

As an Item identifier, the permanent or ‘at rest’ state of a Full Granular Reference Number (FGR#) within the iBasketTM Bicameral System, is always that of data elements and values governed by an operational analytical rules format based on sequence and

reference and included within the singular representative iBasketTM of each ‘whole’ enterprise product. This unique data model employing a recursive function-like approach in managing the unique iBasketTM data element

structures within the iBasketTM Bicameral System is fundamentally different from current information systems in that the required unique Item identifier, the Full Granular Reference Number (FGR#), is generated last not first, is generated dynamically, temporarily and operationally by the system and not manually and before hand by the user, and that although the singularly

entered re-selectable ‘ingredients’ for each Individual product variation (Item) of each ‘whole’ enterprise product are always ‘in the system’, these Individual product variation (Item) identifiers are only ever system-allocated, singularly-referenced

and permanently record retained in and by the system as and when ‘enterprise-determined’ operationally required.

Each ‘whole’ enterprise product in iBasketTM Bicameral is introduced into the system through its assignment ofone unique Aggregate … one configurable and transactable data element structure referred to as an iBasketTM.

A number of defined iBasketTM Types corresponds to an equal number of defined Product Types. These include … Basic type, Assembly type, Simple Package type and Diverse Package type.

Any possible ‘whole’ enterprise product can be ascribed to at least one of the paired iBasketTM/Product Types.

Each assigned iBasketTM data element structure uniquely representing one ‘whole’ enterprise product (all variations of)and referenced by one unique iB# identifier functions as a single data repository for elements representative of all the

defining characteristics of the ‘whole’ enterprise product, including all ‘selectable’ defining characteristics. In iBasketTM Bicameral it is always the system through its Bicameral Product Definition MechanismTM or BPDMTM

that dynamically allocates one unique identifier to each variation of the same ‘whole’ enterprise product; this referred to as a Full Granular Reference Number or FGR#.

Operationally, the Attribute characteristics of each ‘whole’ enterprise product are first observed then particularly associated with that product as Attribute Families (AttF) each including ‘enterprise determined available’ Attribute Values (AttV). As each ‘whole’ enterprise product is introduced into the system, data element values representing the associated

Attribute Family and Attribute Value data are aggregated in its assigned iBasketTM construct applying analytical rules of sequence and reference.

The iBASKETTM Bicameral System is designed and configured to execute certain unique definitive algorithms. Any operational selection of Attribute Values from Attribute Families associated with a particular ‘whole’ enterprise product

and included in its representative iBasketTM activates a system executed definitive algorithm, temporarily defining one particular variation of the product and dynamically generating its one unique Full Granular Reference Number (FGR#)

identifying that particular variation of that particular ‘whole’ enterprise product..

Dynamic Allocation

iBasketTM


©

19


©

20

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

BPDMTM Efficiency


©

21



The uniquely functioning Bicameral Product Definition Mechanism or BPDMTM of the iBasketTM Bicameral System advances Product Definition (PDef) mechanics & Product Definition (PDef) required user resources

from the ‘effectively complex’ of Current Information Systems to the ‘simply efficient’ of the iBasketTM Bicameral System.This is illustrated in the comparative tables below & the referenced Figs. A, B, C & D which follow.

Contrast DYNAMIC SYSTEM ALLOCATIONAGGREGATED TO INDIVIDUALIZED FORMAT

PRELIMINARY MANUAL ALLOCATIONSINGULAR INDIVIDUALIZED FORMAT

Definition ProductCurrent with iBasketTM with

ENTERPRISE DETERMINED AVAILABLE PRODUCT VARIATIONS

in Current in iBasketTM

Fig. D ~ p.25Fig. C ~ p.24

23,295,346,138,839,199,198,608,359,424 …

838,632,460,998,211,171,149,900,939,264 …

REQ’D USER ENTRIES

476

23,295,346,138,839,199,198,608,359,424 … REQ’D USER TRACKED IDENTIFIERS

1

ASSEMBLY PRODUCT TYPE E.G.VEHICULAR LIGHTBAR

36

432

REQ’D USER ENTRIES

22

36 REQ’D USER TRACKED IDENTIFIERS

1

BASIC PRODUCT TYPE E.G.UNIFORM TROUSER

ENTERPRISE DETERMINED AVAILABLE PRODUCT VARIATIONS

in Current in iBasketTM

Fig. B ~ p.23Fig. A ~ p.22

BICAMERAL PRODUCT DEFINITION MECHANISMBPDMTM


©

22

432Required User Entries

36USER TRACKEDProduct - Item - SKUVariation Identifiers

Current Information Systems

Tracking Reference Product No. / Item No. / SKU No.

Product Attribute

Characteristic Color

Product Attribute

Characteristic Waist

Product Attribute

Characteristic Inseam

100001 Blue 30 Short

100002 Blue 30 Regular 100003 Blue 30 Long 100004 Blue 30 X-long 100005 Blue 32 Short 100006 Blue 32 Regular 100007 Blue 32 Long 100008 Blue 32 X-long 100009 Blue 34 Short 100010 Blue 34 Regular 100011 Blue 34 Long 100012 Blue 34 X-long 100013 Red 30 Short 100014 Red 30 Regular 100015 Red 30 Long 100016 Red 30 X-long 100017 Red 32 Short 100018 Red 32 Regular 100019 Red 32 Long 100020 Red 32 X-long 100021 Red 34 Short 100022 Red 34 Regular 100023 Red 34 Long 100024 Red 34 X-long 100025 Tan 30 Short 100026 Tan 30 Regular 100027 Tan 30 Long 100028 Tan 30 X-long 100029 Tan 32 Short 100030 Tan 32 Regular 100031 Tan 32 Long 100032 Tan 32 X-long 100033 Tan 34 Short 100034 Tan 34 Regular 100035 Tan 34 Long 100036 Tan 34 X-long

Required User Entries = # Variations x (# Attribute Characteristics + # Non-Attribute Characteristics)

determined available in 3 color values x 3 waist values x 4 inseam values

UNIFORM TROUSER PRODUCT

36

providing for

unique variations

BASIC PRODUCT TYPE

CurrentInformation Systems

User EntriesRequire 432To Define

Individually Identified Product - Item - SKU Variations

USER GENERATED / TRACKED / MANAGED36

Name36 x

Source36 x

Category36 x

Buy Cost36 x

Description36 x

Source Reference36 x

Unit Measure36 x

Sell Price ...36 x

36 36 3636

Fig. A

iB#

iBASKETTM

Identifier

AttF 1 Color

{3AttV}

AttF 2 Waist

{3AttV}

AttF 3 Inseam

{4AttV}

36 Operationally Dynamic

System Generated / Tracked / Managed

FGR#

(Full Granular Reference Numbers)

B-AUP-339841 1 Blue 1 30 1 Short BAUP339841-1/1/1 B-AUP-339841 1 Blue 1 30 2 Regular BAUP339841-1/2/2 B-AUP-339841 1 Blue 1 30 3 Long BAUP339841-1/1/3 B-AUP-339841 1 Blue 1 30 4 X-long BAUP339841-1/1/4 B-AUP-339841 1 Blue 2 32 1 Short BAUP339841-1/2/1 B-AUP-339841 1 Blue 2 32 2 Regular BAUP339841-1/2/2 B-AUP-339841 1 Blue 2 32 3 Long BAUP339841-1/2/3 B-AUP-339841 1 Blue 2 32 4 X-long BAUP339841-1/2/4 B-AUP-339841 1 Blue 3 34 1 Short BAUP339841-1/3/1 B-AUP-339841 1 Blue 3 34 2 Regular BAUP339841-1/3/2 B-AUP-339841 1 Blue 3 34 3 Long BAUP339841-1/3/3 B-AUP-339841 1 Blue 3 34 4 X-long BAUP339841-1/3/4 B-AUP-339841 2 Red 1 30 1 Short BAUP339841-2/1/1 B-AUP-339841 2 Red 1 30 2 Regular BAUP339841-2/1/2 B-AUP-339841 2 Red 1 30 3 Long BAUP339841-2/1/3 B-AUP-339841 2 Red 1 30 4 X-long BAUP339841-2/1/4 B-AUP-339841 2 Red 2 32 1 Short BAUP339841-2/2/1 B-AUP-339841 2 Red 2 32 2 Regular BAUP339841-2/2/2 B-AUP-339841 2 Red 2 32 3 Long BAUP339841-2/2/3 B-AUP-339841 2 Red 2 32 4 X-long BAUP339841-2/2/4 B-AUP-339841 2 Red 3 34 1 Short BAUP339841-2/3/1 B-AUP-339841 2 Red 3 34 2 Regular BAUP339841-2/3/2 B-AUP-339841 2 Red 3 34 3 Long BAUP339841-2/3/3 B-AUP-339841 2 Red 3 34 4 X-long BAUP339841-2/3/4 B-AUP-339841 3 Tan 1 30 1 Short BAUP339841-3/1/1 B-AUP-339841 3 Tan 1 30 2 Regular BAUP339841-3/1/2 B-AUP-339841 3 Tan 1 30 3 Long BAUP339841-3/1/3 B-AUP-339841 3 Tan 1 30 4 X-long BAUP339841-3/1/4 B-AUP-339841 3 Tan 2 32 1 Short BAUP339841-3/2/1 B-AUP-339841 3 Tan 2 32 2 Regular BAUP339841-3/2/2 B-AUP-339841 3 Tan 2 32 3 Long BAUP339841-3/2/3 B-AUP-339841 3 Tan 2 32 4 X-long BAUP339841-3/2/4 B-AUP-339841 3 Tan 3 34 1 Short BAUP339841-3/3/1 B-AUP-339841 3 Tan 3 34 2 Regular BAUP339841-3/3/2 B-AUP-339841 3 Tan 3 34 3 Long BAUP339841-3/3/3 B-AUP-339841 3 Tan 3 34 4 X-long

BAUP339841-3/3/4

Required User Entries = # Attribute Values + # Attribute Family Characteristics + # Non-Attribute Family Characteristics

22Required User Entries

1USER TRACKEDSingular iB# Identified iBasketTM

determined available in 3 color values x 3 waist values x 4 inseam values

UNIFORM TROUSER PRODUCT

36

providing for

unique variations

BASIC PRODUCT TYPE iBasketTM

Bicameral

User EntriesRequires 22To Define

Singular iB# Identified Aggregated Configurable Transactable iBasketTM

USER GENERATED / TRACKED / MANAGED1

Name1 x

Source1 x

Category1 x

Buy Cost1 x

Description1 x

Source Reference1 x

Unit Measure1 x

Sell Price ...1 x

1 4 54

Which Provides For

Fig. B


©

23


©

24

POWER SUPPLY

DR

IVER

SID

EPASSEN

GER

SIDE

FRONT

OUTER LENS # 1 2 3 4 5 6 7

OUTER LENS # 15 14 13 12 11 10 9

END CAPLENS #

16

END CAPLENS #

8

BA C

D

EFGHI

J

available in

VEHICULAR LIGHTBAR PRODUCT

Current Information Systems Tracking Reference - Product No. / Item No. / SKU No.

Description

Source Reference

Unit Measure

Sell Price ...

Non-Attribute Characteristics

Name

Source

Category

Buy Cost

23,295,346,138,839,199,198,608,359,424 ...providing for unique variations

x

x

=

=

=

>

>

>

1 of 6 lens color option values in each of 16 {1-16} Position Attribute Characteristics

1 of 34 lighting option values in each of 10 {A-J} Position Attribute Characteristics

4 values of Width Attribute Characteristic 41

3410

616

4

2,064,377,754,059,776

2,821,109,907,456

To Define

User EntriesRequire 838,632,460,998,211,171,149,900,939,264 ...

CurrentInformation Systems

Current Information Systems User Required Entries = # Variations x (# Attribute Characteristics + # Non-Attribute Characteristics)

USER GENERATED / TRACKED / MANAGED

Individually Identified Product - Item - SKU Variations

23,295,346,138,839,199,198,608,359,424 ...

23,295,346,138,839,199,198,608,359,424 x 27 9 ...( )+

ASSEMBLY PRODUCT TYPE

Fig. C

POWER SUPPLY

DR

IVER

SID

EPASSEN

GER

SIDE

FRONT

OUTER LENS # 1 2 3 4 5 6 7

OUTER LENS # 15 14 13 12 11 10 9

END CAPLENS #

16

END CAPLENS #

8

BA C

D

EFGHI

J

available in

VEHICULAR LIGHTBAR PRODUCT

iB#

Description

Source Reference

Unit Measure

Sell Price ...

Non-Attribute Characteristics

Name

Source

Category

Buy Cost

23,295,346,138,839,199,198,608,359,424 ...providing for unique variations

x

x

=

=

=

>

>

>

1 of 6 lens color option values in each of 16 {1-16} Position Attribute Characteristics

1 of 34 lighting option values in each of 10 {A-J} Position Attribute Characteristics

4 values of Width Attribute Characteristic 41

3410

616

4

2,064,377,754,059,776

2,821,109,907,456

To Define

User EntriesRequires 476 ...

iBasketTM

Bicameral

USER GENERATED / TRACKED / MANAGED

Singular iB# Identified Aggregated Configurable Transactable iBasketTM

1

23,295,346,138,839,199,198,608,359,424 ...Operationally Dynamic System Generated / Tracked / Managed FGR# (Full Granular Reference Numbers)

Which Provides For

iBasketTM Bicameral User Entries = # Attribute Values (AttV) + # Attribute Family (AttF) Characteristics + # Non-Attribute Family (AttF) Characteristics440 27 9 ...++

ASSEMBLY PRODUCT TYPE


©

25

Fig. D


©

26

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

BGUITM Simplicity


©

27



It is this unique capability which provides huge cost savings at the ‘back end’.

It is this unique capability which enables a less complex more intuitive user interface and eliminates the incidence of and excessive losses from human errors at the ‘front end’.

It is this unique capability which enables dramatic reductions in product data storage and removes the need for extensive investments in ‘data integration’ projects and the like that this storage requires.

It is this unique iBasketTM Bicameral ‘internal process’ system model that assures substantial increased profits by enabling an enterprise to operationally …

remove complexity … eliminate errors … and create efficiency …

simply!

Current Information System GUI’s facilitate only the latter!

BICAMERAL GRAPHICAL USER INTERFACEBGUITM

Building upon its embedded technology of the Bicameral Product Definition MechanismTM (BPDMTM) and the representative configurable transactable data element structures (iBasketsTM) that this produces,

the iBasketTM System is extended and delivers a simpler more efficient graphical user interface … a Bicameral Graphical User InterfaceTM or BGUITM

Ubiquitous acceptance and the elemental use of an Individualized product definition format has produced a user driven single state (configured only) high volume product data storage model.

Accordingly current system GUI’s are operationally complex, functionally inflexible and productively inefficient.

The BGUITM in turn affords a simpler more efficient Operational Product Information Management facilitating Core Op functionality in two simultaneously deliverable product definition formats …

Aggregated & Individualized

CORE OP User Executed

TRACK product by

INDIVIDUALIZED VARIATION ONLY

VARIATIONS AGGREGATE &/or INDIVIDUALIZED VARIATION

TRANSACT product by



REPORT product by



with Current with iBasketTM

Uniquely providing system wide Operational Product Information Management dynamically and simultaneously in both an Aggregated & Individualized format is in part what differentiates iBasketTM Bicameral from Current Information Systems.

Introduction of the unique Aggregated to Individualized product definition format into iBasketTM Bicameral has produced a system driven dual state (configured & unconfigured) low volume product data storage model

whose unique graphical user interface is operationally less complex, more flexible and highly efficient.


©

28

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE


WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

MANUFACTURINGPDE

WHOLESALEPDE

CONVERTINGPDE

RETAILPDE

iBTM IP


©

29

http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&r=1&f=G&l=50&s1=7447647.PN.&OS=PN/7447647&RS=PN/7447647

UNITED STATES PATENTPatent No.: US 7,447,647 B1

Original IT mechanisms, data element structures and other embodiments forming critical foundations of the iBasketTM Aggregate Bicameral Core Op System are described, represented in and protected by

United States Patent; Patent No.: US 7,447,647 B1.

Published patent available for viewing at www.uspto.gov (Direct access link as below)

it product genetics & inventoriable simplicity

Technology