Session Number: 8A

1
Internet Supply Chain Management ECT 481
Winter 2006
Session Number 8A

• Session Date May 15, 2006
• Session Outline
• Administrative Items
• Session Topics Future Considerations
• SCM Trends Potential High Impact Technology
• Real-time Enterprise
• M-commerce Wireless Technology
• RFID
• J2EE/.NET Comparisons Web Services

2
Operational Trend Real-Time Enterprises
Data Processing
Internet
Real Time
(Still Happening)

• Weeks
• Batch
• Megabytes
• Punch Cards
• Few People

• Days
• Request/Reply
• Terabytes
• Human
• Many People

• Minutes
• Automated
• Exabytes
• Event Driven
• Beyond People

3
Changing the Ways of Working
Internet
Real Time
Linear Business Processes
Web of Business Processes

• Triggered by Physical Events in the Real World
• Many Starting Points
• Automated, Interdependent Processes

• Human Intervention Required
• Limited by Submit or Go Button

4
Wireless Technology Mobile Ecommerce

• Wireless technology turns e-business into mobile
  ecommerce and, ultimately, m-business, or mobile
  e-business
• M-commerce is defined as the ability to purchase
  good anywhere through a wireless Internet-enabled
  device.  Primary mobile communication exists
  through web-enabled wireless phones. 
• Current applications
• Conduct online transactions
• Make purchases
• Trade stocks
• Send e-mail
• Future applications
• A wireless office, where computers, phones and
  other office equipment are all networked without
  cables

5
M-commerce vs. Traditional Ecommerce

• Compare to traditional web
• Smaller screens
• Low bandwidth
• Monochrome vs. Color
• Character vs. Bit modes
• Font control
• Limited local memory
• Limited data entry capabilities
• Mini browser features
• Phones vs. PDAs vs. new form factors

6
M-commerce Weaknesses

• History tells us tech companies are far too eager
  to proclaim a revolution. However, history shows
  that a huge new market does not just show up
  overnight.
• It takes years for consumers to catch on to a new
  technological development.
• Tech companies entering into the market have no
  idea what kind of business model they should
  follow.
• Is a consumer really going to pick up their cell
  phone and want to hear a commercial advertising
  Pepsi?
• Wireless Application  Protocol (WAP) is required
  with all web-enabled wireless devices but it has
  several significant limitations.
• Adoption of m-commerce cannot justify the costs
  that go into producing web-enabled wireless
  devices.

7
Obstacles for m-Business Adoption

• One of the challenges is to discover just how
  consumers might be inclined to use wireless
  devices for shopping. 
• Wireless service is not universally available or
  reliable and still relatively expensive.
• Limited bandwidth restricts the amount of data
  that can be sent over the wireless network.
• Wireless devices have significantly smaller
  memory capacity and less powerful processors than
  desktop computers.
• Application development and security standards
  still evolving.

8
M-commerce B2B Services

• Industry vertical applications
• Deliveries (UPS, FedEx)
• Construction site supplies
• Agricultural sensors
• Insurance adjustors
• Government inspectors
• Real Estate
• Equipment management
• Incorporating XML
• Replacing EDI

9
Wireless Technology and Devices

• Wireless development
• First-generation wireless technology was the
  cellular phone
• Second generation wireless technology, which
  includes digital cellular phones, is currently in
  use worldwide
• Third generation, or 3G technology will enable
  wireless devices to send and receive data as much
  as seven times faster than a standard 56K modem
• Wireless devices
• Personal digital assistants (PDAs), Palm OS
• Digital cellular phones (WAP Phones)
• Two-way pagers (RIM)
• MS Windows CE/Pocket PC
• RFID

10
Wireless Internet Access

• Code Division Multiple Access (CDMA)
• Each transmission is assigned a specific channel,
  giving the transmission the benefit of the entire
  bandwidth within that channel and reducing the
  possibility that a connection will be broken
• Able to assign each transmission on the network a
  unique code to ensure security
• Global System for Mobile Communications (GSM)
• Uses Time Division Multiple Access (TDMA) which
  takes multiple calls and assigns each call to a
  different time slot on the same radio frequency,
  eg. Short message service (SMS)

11
Wireless Hype Cycle
Source Gartner
12
WAP

• Wireless Application Protocol (WAP)
• Developed by Nokia, Ericsson, Motorola, etc.
• A set of communication protocols designed to
  enable different kinds of wireless devices to
  communicate and access the Internet
• Designed to standardize development across
  different wireless technologies worldwide
• Intended primarily for Internet-enabled digital
  phones, pagers and other handheld devices
• Uses Web sites specifically designed for wireless
  handheld devices that have small screens and
  low-bandwidth constraints

13
WML

• Wireless Markup Language (WML)
• The scripting language used to create Web content
  to be delivered to wireless handheld devices,
  based on XML
• Removes unnecessary content from Web pages
• WML tags are used to mark up a Web page to
  specify how the page should be formatted on a
  wireless device
• WML works with the WAP to deliver the content
• Similar to HTML, but it does not require input
  devices
• Microbrowsers
• Designed with limited bandwidth and limited
  memory requirements
• Access the Web via the wireless Internet

14
WAP and WML Integration

• How wireless Internet works
• A WAP gateway, which acts as a proxy server,
  receives the request, translates it and sends it
  to the appropriate Internet server
• Server responds by sending the requested WML
  document
• The WAP gateway parses this document's WML (i.e.,
  it analyzes the WML document, checking it for
  correctness) and sends the proper text to the
  digital phone
• Key Terminology
• Deck
• A WML document
• Card
• Consists of one user interaction, providing the
  WML browser with a small, self-contained document
  for browsing

15
Future of Wireless Internet

• Decreasing cost and size of wireless phones and
  mobile devices
• Improving technology
• Increasing number of devices made wireless
• Increased venture capitalist interest in wireless
  technology

16
Challenges Real Time Enterprises
Analyze
Access
the data and events in real-time to provide
business intelligence and business activity
monitoring for continuous process improvement.
the information any time, anywhere by all the
appropriate people, applications and business
process.
Manage
the explosion of data and events in a single
source of truth that is scalable, reliable, and
secure.
Respond
Capture
to events and information automatically and allow
for people to manage by exception.
appropriate, filtered information from a variety
different readers and sensors.
17
Enter RFID A Passive Tag
18
Real Time Business
retail supply chain
RFID-TaggedInventory and Readers
19
What is RFID?

• Radio frequency identification (RFID) is an
  automatic data capture (ADC) technology that
  comprises small data-carrying tokens ('tags'),
  and fixed or mobile scanners ('readers').
• Tags are attached to or embedded in objects to be
  identified.
• Tags typically are based on a custom designed
  silicon integrated circuit.
• Readers may be installed at locations where data
  capture is required, and may also be in the form
  of portable readers.
• Captured data from tags transferred between
  distributed readers and a host environment via
  wire or wireless serial communications links.
• Readers and tags use low power radio frequency
  (RF) signals.
• Through the application of RFID, items may be
  tracked automatically and without human
  intervention resulting in
• Reduced cycle time
• Improved info data integrity.
• Hybrid solutions being developed to include RFID,
  1D and 2D bar code technologies.
• RFID is projected as a core component enabling
  retailers to efficiently track consignments and
  items from manufacturers, through distribution
  channels to the retail store. Think SCM!
• Opportunities include military logistics, parcel
  and postal service logistics, transportation
  fleet management and corporate asset control.

20
Why is RFID Hot Now?
A Convergence of Developments
Technology/Standards Enablement
Business Process Evolution
Falling RFID Tag Costs
Supply Chain Collaboration
Global Numbering (EPC) and Catalogs (UCCNet)
Ubiquitous Connectivity
XML Messaging
VMI and Consignment
Broad-Based RFID Market Interest
EPC Electronic Product Code VMI -
Vendor managed inventory
21
Supply Chain Challenges
22
RFID Proposed Solution Value

• More detailed information
• Improves forecasts, reduces stock outs
• Fast reaction to business change
• Real-time information reduces obsoletes, excess
  inventory
• Automation increases accuracy
• Fewer transaction and shipping errors
• Decrease Costs
• Pinpoint process break downs Minimize products
  pulled back for recalls
• Greater security
• Reduces shrinkage, anti-counterfeit

23
Managing Expectations RFID ROI ?

• Labor costs about 0.0025 a second (in US)
• Need to save 4 seconds for each 1 cent of tag
  cost (2 minutes?)
• Favors repetitive processes and/or unstructured
  environments
• Supply Chain Mandates favor the Retailer
• But may be required to avoid penalties and to
  learn
• Additional (legal) pressures help business case
• High risk / Highly regulated industries will lead
  (e.g. FDA)
• Brand protection, authentication,
• Closed-loop applications still highly relevant
• Maintenance, Internal movements, WIP Processes,
• Asset tagging may require mix of technologies
• True value lies in Supply Chain or Process
  visibility
• May need to push infrastructure out to trading
  partners
• Need to leverage information to create strategic
  relationships

24
J2EE .Net Comparison
25
Java vs .Net Solutions

• Both multi-tiered, similar computing technologies
• Both support standards
• .NET based on proprietary standard developed and
  maintained by Microsoft.
• J2EE based on open standard developed and
  maintained by Sun and many other vendors
• Both offer different tools ways to achieve the
  same goal.
• A lot of parallelism can be seen.
• Very difficult to compare and qualify the
  comparison because each has its own advantages
  disadvantages.

26
Microsoft .NET - What is it ?

• Comprehensive family of products
• Built on Industry and Internet Standards
• Provide for each aspect of developing, managing,
  and using XML Services

27
J2EE (Java 2 Enterprise Edition) - What is it ?

• Defines standard for developing multi-tier
  enterprise applications
• Simplifies enterprise applications by
• Basing them on standardized, modular components
• Providing a complete set of services to those
  components
• Handling many details of application behavior
  automatically, without complex programming

28
Basis of comparison

• Objective measurements
• Lines of code
• Development tools
• Documentation
• Infrastructure
• Performance
• Architectural pattern
• Security
• Price
• Development time

• Subjective measurements
• Developer satisfaction
• End-user satisfaction

29
Comparing the stacks
Enterprise solutions
Third party extensions
Extensions Phoenix, Tiles, Java Faces
PP blocks
Struts
ASP.Net
JSP
Servlets
Visual Studio.net
Java
JDBC
ADO.NET
J2EE Class Library
Base Class Library
Java runtime
CLR
J2EE App Servers WebSphere, Weblogic, Tomcat,
etc.
JMS
Apache
Win32, Unix, Linux
30
Support for Web Services

• Both platforms support Web Services.
• XML Web Services built into .NET and are part of
  Visual Studio.NET.
• Java Web Services Developer Pack (JWSDP) as well
  as vendor specific tools.
• Microsoft has a tad bit more proprietary flavor
  to its support for web services.
• Speed-to-market advantage goes to .NET over J2EE.

31
What about mobile?

• Web Services are fine as n-tier applications with
  UI provided through browser, but
• On mobile devices WAP hasnt really caught on.
• Even iMode hasnt caught on in Europe.
• Renewed Thin/Thick client discussion.
• Java applications on Mobile devices are
  reasonably successful.
• Now Microsoft is moving fast into the field with
  .Net Compact Framework.

32
Development tools and Documentation

• Server-side is well supported by both Java and
  .NET IDEs.
• On the client-side .NET IDEs benefit from the
  fact that .NET CF is so close to .NET.
• With Java there are separate IDEs for desktop and
  mobile application development.
• Compatibility problems between Java vendors.
• Java IDEs tend to be slow!
• C is a richer/more complex language than Java.
• Both Java and .NET have well documented API.
• Web service documentation.
• .NET MSDN.
• Java Google.
• Support for encryption of web services.
• .Net CF HTTPS and SOAP extensions.
• J2ME HTTPS, but only in CDC MIDP 2.0.

33
Choosing between Java and .Net

• The ultimate choice usually depends not on
  technical superiority, but on
• cultural/religious/political preferences.
• Skill set of your developers.
• Customer preference.
• Vendor relations.
• You are most likely to be developing in both
  environments for the foreseeable future.
• Gartner Group 30 of all enterprise
  applications will have both J2EE and .Net code.
• Often IIS in front of J2EE infrastructure.
• Interoperability issues.
• Look out for The third way.
• Linux, Apache, MySQL, PhP,
• Look out for disruptive technologies.

34
Customers View

• Not really concerned about Portability.
• Concerned about Interoperability if development
  is in-house.
• VERY concerned about Cost and Time.
• Wants a Return On Investment (ROI).

35
The future of Java and .Net

• The two frameworks are becoming more and more
  alike.
• However
• .Net is Microsofts core strategy.
• .Net will be part of OS in the next generation of
  Windows.
• Lots of innovation in Longhorn Avalon, INDOGO,
  WinFS.
• Is Java in Suns core strategy?
• Java 1.5 SE is very close to C 2.0/.Net CLR.
• Sun Java Studio Creator somewhat close to VS.Net.
• Some talk of JVM as multi-language platform.
• Sun in Java as Open Source battle with IBM.

36
Next Session Highlights

• Project Presentation Logistics
• Final Exam