Showing posts with label management capability. Show all posts
Showing posts with label management capability. Show all posts

Friday, December 9, 2011

Item Design Patterns

Item Design Patterns
Most emerging or advanced technology hardware devices rely upon the IOS + features therefore the automatic defaults to no recognition until the software components are delivered.
  • Hardware device - when the device sold has been structured in a transaction with another add on feature. 
  • Exceptions; a case where the hardware and software have different shipment schedules.
  • Assume the device isn't valued alone and requires the software in this scenario their is no value for recognition of revenue the answer is "no". 

Item Offer Voice of the Customer

Voice of the Customer
  • A customer measures the supplier (your organization is the customers supplier) quality or value in the effort it takes to do business with a supplier.  
  • Does the supplier use basic identifiers that do not force me to change or add items to my purchasing system?  

Item Templates

Item Templates
Some people refer to these as the product family setup features. If not careful-you might end up with many items you never use. 

The process impacts are huge.  The ability to work with your suppliers; higher threats of abuse based on the obvious maturity in your business processes. 


Purpose of item templates in Real World stakeholders views
To enable item logic re-use and generic standards to meet the criteria of classification systems consistently.

Using Quantified Measurement Systems
  • In volume driven organizations you will see the item described in the item identifier name or Product ID
    • Think for a moment about the way you have a dollar bill
      • If every-time you put the dollar in your pocket you were unable to see it except in a handful of pennies.  Every time you wanted a dollar from your pocket book or wallet a hundred pennies would be the reality for you.  
      • As a result the many steps and touches become higher threats for defects.  
        • Measuring and using a percentage has simply taken the dollar and broken it into 100 times the threat.  
          • You had a single defect in a way you could address
          • You know have a hundred that say your okay and no one will address because it's far too complex. 
    • Think of the way more impacts any person in this analogy
      • You have to place each penny into a piggy bank; many times I drop a few.
      • You have to count each penny individually; I often get distracted and have to restart again.  
    • If every penny was to be placed into 100 banks; you would have the same problem with higher effort.  
      • Often people use this approach without revealing that they could have had a single defect without 100 movements into many piggy banks.  
      • Many people think this approach makes sense. 
 Qualified measurement systems
    • Design with the abstraction of design patterns; before performing root cause to understand the norms try not to assume that the experts have the ability to see beyond their own work flows
      • Especially if they are on the receiving end of the penny scenario.  
      • Understand the object design patterns; 
        • Think of a pivot table; large amounts of data can become larger simply by placing data in a certain position.
        • Use the pivot table to reduce the many into common patterns.
      • The template isn't changing the value in the field of the template change.
      • What patterns exist in technology offers?
        • Apply high, medium, and low indicators to assign your external risk reporting assignment in the template of your items.  
        • Try one per class based on your SEC reporting.  
          • One for cost and one for revenue. 
            • High
              • New-High
              • aka New Business Models
              • aka Competitive Advantage
              • aka Higher Resource Skills
              • aka Higher risk
              • aka not fitting in your current system
              • aka intellectual property 
              • aka high controls
              • aka higher touches fewer outside the norm
            • Medium 
              • Advanced - Medium
              • aka mature in market with increasing value
              • aka harder to ship complete
              • aka higher cost
              • aka begins to shift to channels in program or a single offer special training.
            • Low 
              • Core/Foundation - Low
 In closing let's see how this template applied to our items in an offer translates into our highway analogy.  
  • High - Slow lane on the highway
  • Medium - Middle lane on the highway
  • Low-fast lane or commuter lane with partners
Any organization anywhere in the world.  

Atomic Items

Atomic Items

In most ERP systems you will have the setup of the items, in the item master.
  • An atomic item has value if the item can be sold and the item has been factored in one of the organizations current markets.   
  • The item must be considered a value for a customer party and generic items are resold through your channels models.  
  • Test the validity of the item as an ala carte item when the channel partners may be qualified to sell or have been trained and certified to sell an atomic item.  
Applied Item Template
  • Assigns the revenue treatment defaults
  • Applies the rule for use in transactions as the reference information based on the point in time of the transaction record. 

Generic Object Types

Test
  • Can you find value in a power cord without the device?  
  • Can you use the cables on an existing device when built for a specific device family?  

Universal or Generic Objects
  • Objects are typically known as hard bundles or unstructured items-the items cannot be unstructured.  
  • Objects should default the power and communication requirements based on the end country mapped to the location code segment 2 in many financial management capabilities.  
  • Objects are considered unstructured items, they cannot be decomposed from a device with an intent to have value. 
  • Objects are not revenue generating types and therefore have no value in the item master.  
  • Objects are defaults on the BOM of the device.  
  • Objects are not going to influence the pricing on an offer when a single price is used for the presentation of a system or bundle.   
  • Objects never change the margin calculation on the system or bundles.  

Object Parts
  • Maintenance contract items are not in the item master.
  • Objects may be sold as a parts in maintenance contract models. 


Example Hardware Objects
  • Power cords, cables and similar universal with local requirements 
  • Objects are included in the price of a device.

Example Software Objects
  • Objects are a fundamental part of the use of a device, internal operating software (IOS) of the type without any features.  
  • A license for the IOS download capability isn't an actual paper or product for a shipment to receive into inventory, rather the HOW an entitled user acquires the software systematically.  
  • Objects of the IOS types are NOT add on features rather the basic software allowing the device to register a warranty and allow connectivity with other devices.