18 April 2005

IBF: An interesting data-transfer model

IBF is a system to transfer data between your big computers and your desktop applications. Be neat if the same type of integration was available within a single desktop: Moving files, data, instructions in and out of an aggregator, as opposed to requiring links to read the data elsewhere.

I blogged about custom feeds for custom software; and an aggregator within an aggregator.

Wouldn't it be neat if there were some transparent tools that took the products from IBF, and seamlessly created automatic feeds; and there were also mechanisms that monitored the outputs of the IBF platforms to create custom search tools, tags, and organizing systems?


Links


Basics

IBF 1.5 code walkthrough. Information Bridge Framework.

Technorati links.

Contextual information.

IBF was beta May 2004; originally there were smart tags associated with IBF; For those of you who despise XML, you're in luck: No XML required.

Sample industry use

Here another view of the business end: What the legal community needs and how they approach document formatting issues.

Pharmaceutical industry using IBF.

Sample demo: here


This demo could be improved if it did the following:

  • Focused on the data transfer, and how it connects the back-end with the front-end
  • Tailored the focus to show how time will get saved
  • Highlight for management how workers will better respond to management queries
  • Contrast [a] the existing IT architectures provide with [b] what IBF could offer to a firm
  • Show case when IBF would be too complicated to introduce; is there an optimal size firm or IT architecture where IBF would do great, and below a threshold it is not cost effective?
  • Highlight was current processes, errors, or approaches to data transfer are streamlined, made more efficient, and why the IBF investment has a return in terms of more effective response-time to the clients' needs [not our own company, but the outside firm we're trying to assist with a project].

    The current demo looks great; but it doesn't capture the essence of IBF: Connecting big computers with the desktop. The only reason I could follow the graphics was that I knew what IBF was; but if you're trying to use this demo to convince someone that IBF is the way to go ... despite the color, it does nothing to clarify the benefits.

    Overall, I felt like the demo does more to showcase the self-evidently spectacular graphics-design features of the demo, but does little to highlight the product benefits for the client. I recommend redoing the demo and focus more on the top-level payoffs in terms of funding, efficiencies, time saved, cost reduction, and ensure the IBF-related features are clearly contrasted with something that is more complicated, slower, and less efficient.

    But don't skew your data. If there are times when IBF won't work or be as effective than something less dynamic, say so. I want to know when IBF really is worth the investment, and I want to know that you know there are limitations. If you try to sell me IBF without discussing the negatives I'm more likely to not listen to your recommendations and analysis.

    Update

    Maybe this might be another attempt at an IBF demo.
  • IBF is a system to transfer data between your big computers and your desktop applications. Be neat if the same type of integration was available within a single desktop: Moving files, data, instructions in and out of an aggregator, as opposed to requiring links to read the data elsewhere.

    I blogged about custom feeds for custom software; and an aggregator within an aggregator.

    Wouldn't it be neat if there were some transparent tools that took the products from IBF, and seamlessly created automatic feeds; and there were also mechanisms that monitored the outputs of the IBF platforms to create custom search tools, tags, and organizing systems?


    Links


    Basics

    IBF 1.5 code walkthrough. Information Bridge Framework.

    Technorati links.

    Contextual information.

    IBF was beta May 2004; originally there were smart tags associated with IBF; For those of you who despise XML, you're in luck: No XML required.

    Sample industry use

    Here another view of the business end: What the legal community needs and how they approach document formatting issues.

    Pharmaceutical industry using IBF.

    Sample demo: here


    This demo could be improved if it did the following:

  • Focused on the data transfer, and how it connects the back-end with the front-end
  • Tailored the focus to show how time will get saved
  • Highlight for management how workers will better respond to management queries
  • Contrast [a] the existing IT architectures provide with [b] what IBF could offer to a firm
  • Show case when IBF would be too complicated to introduce; is there an optimal size firm or IT architecture where IBF would do great, and below a threshold it is not cost effective?
  • Highlight was current processes, errors, or approaches to data transfer are streamlined, made more efficient, and why the IBF investment has a return in terms of more effective response-time to the clients' needs [not our own company, but the outside firm we're trying to assist with a project].

    The current demo looks great; but it doesn't capture the essence of IBF: Connecting big computers with the desktop. The only reason I could follow the graphics was that I knew what IBF was; but if you're trying to use this demo to convince someone that IBF is the way to go ... despite the color, it does nothing to clarify the benefits.

    Overall, I felt like the demo does more to showcase the self-evidently spectacular graphics-design features of the demo, but does little to highlight the product benefits for the client. I recommend redoing the demo and focus more on the top-level payoffs in terms of funding, efficiencies, time saved, cost reduction, and ensure the IBF-related features are clearly contrasted with something that is more complicated, slower, and less efficient.

    But don't skew your data. If there are times when IBF won't work or be as effective than something less dynamic, say so. I want to know when IBF really is worth the investment, and I want to know that you know there are limitations. If you try to sell me IBF without discussing the negatives I'm more likely to not listen to your recommendations and analysis.

    Update

    Maybe this might be another attempt at an IBF demo.
  • " />