IT Product Genetics & Inventoriable Simplicity

IT Product Genetics & Inventoriable Simplicity

The Aggregate Bicameral Core Op System Model

MANUFACTURI
MANUFACTURI
NG
iBASKETTM PD
WHOLESALE
WHOLESALE TM CONVERTING
CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE

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

CURE NOT TREATMENT
Unique Process ~ Unique Functionality ~ Unique Interface

Unique Model ~ Unique Paradigm

David Goran Shedlack
always123@earthlink.net

DAVID GORAN SHEDLACK ©2005
Do Not Copy - Unauthorized Distribution Prohibited

1

MANUFACTURI
MANUFACTURI
NG
NG
iBASKETTM PD
WHOLESALE TM
iBASKET BICAMERALTM
CONVERTING RETAIL
RETAIL
PDE
PDE PDE
PDE PDE
PDE
PDE
PDE

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


2

… unrealized promise ...
“ leaner, lighter, more efficient operations ”

In the last 30 years Product Distribution Enterprises have implemented
In the last 30 years Product Distribution Enterprises have implemented
Information Management Systems (ERP, MRP… to facilitate or improve operational management.
Conventional InformationSystems (ERP, MRP…) )to facilitate and improve operational management.
Directly attributable improvements in efficiency or realized profits have been minimal at best.
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!
Indeed, real profit (%Net) has often decreased while related operational costs have soared!
Why?
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 …..”

T H E

G R O U P
Copyright 2005, the Yankee Group. All rights reserved.
Reproduced with permission


3

MANUFACTURI
MANUFACTURI
NG iBASKETFocus PD TM
iBASKETTM CONVERTING
WHOLESALE
BICAMERAL RETAIL
RETAIL
PDE PDE PDE PDE
PDE


4

PDE

Product Distribution Enterprise
(PDE)

Any Enterprise That Produces Or Sources And Markets Any Product

MANUFACTURING WHOLESALE
type type
PDE PDE

Products Produced COMMON Products Sourced
CORE
OPERATIONS
DEFINE
Product Introduction & Identifier Establishment
TRACK
Product Search & Select
TRANSACT
Product Acquisition & Sale
REPORT
Product Inventory Status

CONVERTING RETAIL
type type
PDE PDE

Products Produced Products Sourced

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 Problem
and 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

MANUFACTURI
MANUFACTURI
NG
iBASKETTM PD
Systemic Problem
WHOLESALE CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE


6

PDef ~ OPIM

Product Definition & Operational Product Information Management

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!

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.

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 Synchronization
and Data Integration which are often put forward as solutions, this cost/loss factor will persist and grow dramatically absent
introduction 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!


7

MANUFACTURI
MANUFACTURI
NG
iBASKETTM PD
Cure
iBASKET BICAMERAL
WHOLESALE Not Treatment TM
CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE


8

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.

Bad product data being created in the Product Distribution Enterprise Sector globally
is directly responsible for costs and losses that are enormous and growing!
iBasketTM Bicameral
is a fundamental solution that reverses this reality using far fewer resources than are currently used to create it!

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!

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.

CURE NOT TREATMENT
Unique Process ~ Unique Functionality ~ Unique Interface
Unique Model ~ Unique Paradigm


9

MANUFACTURI
WHOLESALE Centric TM PD TM
Core iBASKETTM CONVERTING
MANUFACTURI
NG iBASKET BICAMERAL
WHOLESALE Op Architecture
CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE

10

Current

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

PDE PDE


HRM HRM
MRP MRP
CPM CPM
EPM EPM
EP CRM EP CRM
CMMS CMMS

BOM EAM BOM EAM
PLM PLM
I. SRM I. SRM
MPL FINANCIALS MPL FINANCIALS
POS POS
LOG LOG
BI BI
BPM BPM

PPM PPM
MRPII WMS RFID MRPII WMS RFID
II. II.
SCM
OTHER PIM SCM OTHER PIM

CONVERTING RETAIL
PDE PDE


HRM HRM
MRP MRP
CPM CPM

EPM EPM
EP CRM EP CRM
CMMS CMMS

BOM EAM BOM EAM
PLM PLM
I. SRM
I. SRM
MPL FINANCIALS MPL FINANCIALS
POS POS
LOG LOG
BI BI
BPM BPM
PPM PPM
MRP II WMS RFID MRP II WMS RFID
II. II.
SCM OTHER PIM
SCM OTHER PIM

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.

11

iBasketTM

iBasketTM Bicameral Architecture Places Core Op Functionality at the System Center

PDE PDE


CONVERTING RETAIL
PDE PDE


III.
FINANCIALS

BOM
CPM
HRM
MPL
EP
CRM

LOG I. CMMS
CORE OP
WMS DEFINE PLM
Product Introduction & Identifier Establishment

MRP
TRACK
Product Search & Select SRM
TRANSACT
BI Product Acquisition & Sale POS
SCM REPORT
Product Inventory Status
BPM
PIM
EPM
EAM
MRPII
II. RFID
PPM TYPE SPECIFIC
&/or
ELECTIVE

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.


12

MANUFACTURI
MANUFACTURI
NG
iBASKETTM PD
WHOLESALE
Advanced Metric
CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE

DAVID GORAN SHEDLACK © 2005

13

CurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystemsCurrentSystems

Current

Product Data Management Performance Metric

Designed and built around a singular Individualized product definition (PDef) data format
the Operational Product Information Management construct of Current Information Systems produces an inefficient
operational Product Data Management Performance Metric, one which results in higher than necessary costs, an ever
P increasing rate of errors and an extensive requisite investment in add-on corrective product data Integration.
R
O
D
U
C
T I
N
D
D I
A E
V
I X
T I
N T
D
A U
P R INTEGRATION
U A COSTS
A
T C
M L
E

T
G
A

I
A
R

SS
O

Z
ST

CE

N E
O
R

A D
P

G
E
M
E
N
T

Individualized
Product Definition
Data Format

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

Effective NOT Efficient!


14

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

iBasketTM

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 uniquely
efficient operational Product Data Management Performance Metric which delivers greatly reduced costs, eliminates
P the currently ever increasing rate of errors and requires NO investment in add-on corrective product data Integration.
R
O
D
U
C
T
A
E

D
G

G
A

E
R

A
SS
O

G d
ST

X
CE

I
T R y
O

N T
R

n
E
P

A G
P R a >>>
U A m
A i
T C
M T
T
c
E
A D
N
A
G
E
M
E
N
T

Assigned iBasketTM Dynamically Allocated
Aggregated Individualized
Product Definition Product Definition
Data Format Data Format

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

Effective AND Efficient!


15

MANUFACTURI
MANUFACTURI
NG iBASKETTM PD
WHOLESALE
WHOLESALEProduct Genetics
CONVERTING
CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE


16

Product Genetics

Product Definition Form ‹› Product Definition Substance

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

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’.

To realize the primary Core Op functionality of Product Definition with minimum user input and maximum
system 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.

BICAMERAL PRODUCT DEFINITION MECHANISM TM
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.

BPDM TM


17

MANUFACTURI
MANUFACTURI
NG iBASKETTM PD
Aggregate Dynamics
WHOLESALE
WHOLESALE CONVERTING
CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE


18

Current

Manual Allocation

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’.

This lack of distinction and the universal requirement to insure full product data granularity has seen
current 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!

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.

The primary often singular use of an Individualized format in current information system constructs assures that these
systems 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!

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.

Effective NOT Efficient!


19

iBasketTM

Dynamic Allocation

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

Each ‘whole’ enterprise product in iBasketTM Bicameral is introduced into the system through its assignment of
one 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)
a nd 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..

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.

Effective AND Efficient!


20

MANUFACTURI
MANUFACTURI
NG iBASKETTM PD
BPDMTM Efficiency
WHOLESALE
WHOLESALE CONVERTING
CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE


21


BICAMERAL PRODUCT DEFINITION MECHANISM
BPDMTM

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.

BASIC PRODUCT TYPE E.G.
UNIFORM TROUSER
Fig. A ~ p.22 Fig. B ~ p.23
ENTERPRISE DETERMINED AVAILABLE PRODUCT VARIATIONS

in Current 36 in iBasketTM

432 REQ’D USER ENTRIES 22

36 REQ’D USER TRACKED IDENTIFIERS 1

Current with iBasketTM with
PRELIMINARY MANUAL ALLOCATION Contrast
Product Definition DYNAMIC SYSTEM ALLOCATION
SINGULAR INDIVIDUALIZED FORMAT AGGREGATED TO INDIVIDUALIZED FORMAT

ASSEMBLY PRODUCT TYPE E.G.
VEHICULAR LIGHTBAR
Fig. C ~ p.24 Fig. D ~ p.25
ENTERPRISE DETERMINED AVAILABLE PRODUCT VARIATIONS

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

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



22

Current Fig.
Information Systems
UNIF
BAS
IC P
RO A
dete ORM DUC
Require 432 User Entries rmin
ed a
vaila TRO
USE
TT
YPE
ble i R PR
n3c
To Define prov olor ODU
iding valu
es x CT
for 3 wa
36 USER GENERATED / TRACKED / MANAGED
36
ist v
alue
s x4i
nsea
uniq m valu
Individually Identified Product - Item - SKU Variations ue varia es
tions
Required User Entries = # Variations x (# Attribute Characteristics + # Non-Attribute Characteristics)

Product Product Product
Current Information Systems
Attribute Attribute Attribute
Tracking Reference
Characteristic Characteristic Characteristic
Product No. / Item No. / SKU No. Color Waist Inseam
100001 Blue 30 Short
100002 Blue 30 Regular
100003 Blue 30 Long
100004 Blue 30 X-long
100007 Blue 32 Long
100011 Blue 34 Long
100013 Red 30 Short
100014 Red 30 Regular
100015 Red 30 Long
100016 Red 30 X-long
100017 Red 32 Short
100019 Red 32 Long
100021 Red 34 Short
100023 Red 34 Long
100025 Tan 30 Short
100026 Tan 30 Regular
100027 Tan 30 Long
100028 Tan 30 X-long
100029 Tan 32 Short
100031 Tan 32 Long
100032 Tan 32 X-long
100033 Tan 34 Short
100035 Tan 34 Long
100036 Tan 34 X-long 432
Required
36 36 36 36 User En
tr ies
36 x Name 36 x Description 36
USER T
RACKED
36 x Source 36 x Source Reference Product
- Item - S
Variation KU
36 x Category 36 x Unit Measure Identifie
rs
36 x Buy Cost 36 x Sell Price ...


23

PE
iBasketTM Fig.
T TY

BAS
IC PRO
DUC
ODU
CT
valu
es
Bicameral
B
R PR seam
USE es x
4 in Requires 22 User Entries
TRO valu
ORM aist tions
UNIF sx3
w
varia
or v alue un ique To Define
e in
3 col
avai
labl 36 1 USER GENERATED / TRACKED / MANAGED
ed
rmin or
d e te ing f
p rovid Singular iB# Identified Aggregated Configurable Transactable iBasketTM
Required User Entries = # Attribute Values + # Attribute Family Characteristics + # Non-Attribute Family Characteristics Which Provides For

36
Operationally Dynamic
iB# AttF 1 AttF 2 AttF 3 System
iBASKETTM Color Waist Inseam Generated / Tracked / Managed
Identifier {3AttV} {3AttV} {4AttV} 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 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 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
1 4 4 5
22
1 x Name 1 x Description Required U
ser Entries
1 x Source 1 x Source Reference
1
1 x Category 1 x Unit Measure USER T
Singular iB# RACKED
Identified iB
1 x Buy Cost 1 x Sell Price ... asketTM


24

Fig.
C
ASSEMBLY PRODUCT TYPE

OUTER LENS # 1 2 3 4 5 6 7

FRONT

PASSENGER SIDE
A B C
DRIVER SIDE

POWER SUPPLY
J D

I H G F E
16 8
END CAP END CAP
LENS # LENS #

OUTER LENS # 15 14 13 12 11 10 9

VEHICULAR LIGHTBAR PRODUCT

available in

4 values of Width Attribute Characteristic > 41 = 4
x
1 of 34 lighting option values in each of 10 {A-J} Position Attribute Characteristics > 3410 = 2,064,377,754,059,776
x
1 of 6 lens color option values in each of 16 {1-16} Position Attribute Characteristics > 616 = 2,821,109,907,456

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

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

Name Description

Source Source Reference

Category Unit Measure

Buy Cost Sell Price ...

Current
Information Systems

Require 838,632,460,998,211,171,149,900,939,264 ... User Entries
Current Information Systems User Required Entries = # Variations x (# Attribute Characteristics + # Non-Attribute Characteristics)
23,295,346,138,839,199,198,608,359,424 x ( 27 + 9 ... )

To Define

23,295,346,138,839,199,198,608,359,424 ...
USER GENERATED / TRACKED / MANAGED

Individually Identified Product - Item - SKU Variations


25

Fig.
ASSEMBLY PRODUCT TYPE D
OUTER LENS # 1 2 3 4 5 6 7

FRONT

PASSENGER SIDE
A B C
DRIVER SIDE

POWER SUPPLY
J D

I H G F E
16 8
END CAP END CAP
LENS # LENS #

OUTER LENS # 15 14 13 12 11 10 9

VEHICULAR LIGHTBAR PRODUCT

available in

4 values of Width Attribute Characteristic > 41 = 4
x
1 of 34 lighting option values in each of 10 {A-J} Position Attribute Characteristics > 3410 = 2,064,377,754,059,776
x
1 of 6 lens color option values in each of 16 {1-16} Position Attribute Characteristics > 616 = 2,821,109,907,456

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

Non-Attribute Characteristics
iB#

Name Description

Source Source Reference

Category Unit Measure

Buy Cost Sell Price ...

iBasketTM
Bicameral

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

To Define

1
USER GENERATED / TRACKED / MANAGED

Singular iB# Identified Aggregated Configurable Transactable iBasketTM

Which Provides For

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


26

MANUFACTURI
MANUFACTURI
NG iBASKETTM PD
WHOLESALE
WHOLESALEBGUITM Simplicity
CONVERTING
CONVERTING RETAIL
RETAIL
PDE PDE PDE PDE
PDE


27


BICAMERAL GRAPHICAL USER INTERFACE
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.

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.

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

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
Current Information System GUI’s facilitate only the latter!

CORE OP with Current with iBasketTM
User Executed

TRACK product by
INDIVIDUALIZED VARIATION ONLY VARIATIONS AGGREGATE &/or INDIVIDUALIZED VARIATION
TRANSACT product by
REPORT product by

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.

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!


IT Product Genetics & Inventoriable Simplicity

IT Product Genetics & Inventoriable Simplicity

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie IT Product Genetics & Inventoriable Simplicity

Ähnlich wie IT Product Genetics & Inventoriable Simplicity (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

IT Product Genetics & Inventoriable Simplicity