|
Q. What is a hub?
A. In the context of e-business, a hub usually refers to a central repository or private exchange. It
is a Web-based solution that makes it easy for trading partners to exchange the data necessary to
negotiate and complete transactions.
Q. What is iHub?
A. iHub, meaning information hub, is a multi-PIP scenario being developed by the iHub Focus Process
Team (FPT). Enabling emerging business models, iHub is a supply chain management solution for any
company -- usable by a private or public repository in which data is gathered and distributed for
cross-supply-chain visibility and/or decision support.
Q. What is the iHub FPT and what are its deliverables?
A. Comprised of representatives from several RosettaNet Partner companies, the iHub FPT is identifying
a set of PIPs for a hub, to enable real-time exchange of common information used in day-to-day
supply chain management.
The iHub FPT is evaluating RosettaNet standards to determine alignment, validating standards
through implementation in team member companies, and proposing enhancements to standards, such as
alteration in PIP size and design, to support implementation in the iHub scenario. Upon approval by
RosettaNet's Executive Board, the FPT will drive the implementation of iHub in RosettaNet Partner
companies.
Q. Is the iHub FPT following RosettaNet methodology?
A. Yes, the iHub FPT is following RosettaNet methodology in all its actions, including the evaluation
and validation of existing RosettaNet standards and the request for changes and development of new
standards.
Q. What is eHub?
A. Cisco Systems’ eHub is a specific instance of an iHub. Cisco Systems designed eHub to gain
greater visibility into, and more effectively manage, its extended, global supply chain. eHub has
served as an early proof of concept for the iHub business model.
Q. How were iHub requirements developed?
A. Cisco Systems held initial summit meetings with trading partners to review and gather input for
eHub requirements. Subsequently, Cisco Systems conducted partner site visits, including detailed
business reviews and data analyses. Business processes and supporting data were revised based on
this input. In late 2000, RosettaNet formed the iHub FPT and has since held a series of iHub
working sessions with representatives from a broad range of RosettaNet Partner companies. The eHub
draft requirements and iHub business model were tested and evaluated by Partners and converted into
iHub requirements.
Q. How many RosettaNet requirements have been identified to support the iHub multi-PIP scenario?
A. Currently, the iHub FPT has identified 15 requirements of RosettaNet PIPs to support the iHub
business model.
Q. Are the PIPs in the iHub scenario different than other RosettaNet PIPs?
A. No, the iHub FPT leveraged existing PIPs and standards to create the iHub multi-PIP scenario.
Q. What PIPs are leveraged by iHub?
A. The PIP requirements currently identified by the iHub FPT
include:
PIP 0C1: Hub Data Synchronization
PIP 2A12: Distribute Product Master
PIP 2C7: Request Bill of Material
PIP 2C8: Notify of Bill of Material
PIP 3A6: Distribute Order Status
PIP 3A13: Notify of Standard Purchase Order
PIP 3A14: Nofiy of Planned Purchase Order
PIP 3B2: Notify of Advance Shipment
PIP 3B11: Notify of Shipping Order
PIP 3B12: Request/Confirm Shipping Order
PIP 3B13: Notify of Shipment Confirmation
PIP 3B14: Request/Confirm Shipping Order Cancellation
PIP 3B18: Shipping Documents
PIP 4A1: Notify of Stratgic Forecast
PIP 4A5: Notify of Forecast Reply
PIP 4B2: Notify of Shipment Receipt
PIP 4C1: Distribute Inventory Report
PIP 7B1: Distribute Work in Process
Q. The iHub FPT requested modifications to existing PIPs. Were these changes requested to support needs specific to Cisco Systems?
A. No, all modifications requested by the iHub FPT were based on pre-existing gaps in PIPs; they were
not specific to Cisco Systems.
Q. Is the iHub model changing cardinality in any PIPs?
Q. What is the expected scope of an iHub, in terms of the number of participating trading partners and data flow?
A. The scope of an iHub depends on the business processes it is supporting.
Q. Is iHub a plug-and-play solution?
A. No, proprietary processing is required at the hub host back-end systems for decision support and
analysis.
Q. Is iHub a push model, pull model or both?
A. iHub can be a push model and pull model, depending on how it is implemented.
Q. Is the data push into iHub time-driven, event-driven or both?
A. iHub can be time- and/or event-driven, depending on how it is implemented.
Q. Must iHub focus exclusively on an iHub owner's buy-side? What about the sell-side?
A. iHub can focus on the buy- and sell-side, depending on how it is implemented.
Q. Are there action expectations on the part of iHub participants that lead to commitments and/or transactions?
A. Requirements for data acknowledgement and other actions are based on how a particular iHub is
configured by its owner. For example, alerts may be generated by the iHub owner and sent to the
relevant trading partners for action, based on predefined business processes. The alerts generated,
and the way they are generated, is proprietary to each iHub implemented.
Q. What alerts are generated and how are they generated by an iHub?
A. Each iHub owner determines how each iHub works, the alerts it generates and the way those alerts
are generated. This is considered the realm of private processes, and therefore has not been
defined within the scope of work of the iHub FPT.
Q. How do you communicate "no change?" Do you have to generate and transmit data in a particular way to identify synchronization?
A. This is part of the process inside an iHub owner's firewall, which RosettaNet does not to address.
Q. What if a trading partner does not want to share data with certain supply chain partners, such as competitors, using iHub?
A. The partner agreement between an iHub owner and its partners can define the level of security and
restrict the use of data.
Q. Can trading partners require data that is optional in a PIP?
A. Yes, an iHub owner can require trading partners to provide a particular data item listed as
optional in a PIP; this is done via the trading partner agreement.
Q. Is iHub only intended for large original equipment manufacturers?
A. No, the iHub scenario can be scaled to meet the needs of companies of various sizes, using as few
or as many PIP combinations as desired.
Q. What is iHub’s value proposition versus implementation/ongoing costs?
A. Trading partners must determine the expected return on investment for the specific iHub.
Q. What is the difference between iHub and an e-commerce datamart?
A. iHub is comprised of RosettaNet standards and implementation enables companies to realize the
associated benefits.
|
