50 Degree Difference

The Bay Area is an amazing place; well known for its microclimates. Clarise and I have had reason to leave the Coastside several times this past week to travel around the Bay. What we've been seeing are temperature changes of up to 50 degrees Fahrenheit. Hot, sunny and dry at 105F in Los Gatos or north Bay to cold, damp and foggy at 55F by the intersection of Skyline and Hickey near Pacifica. Not once, but twice this week, and within the span of the hour it took to drive from one place or the other to Pacifica.

The fog has been amazing as well. Most days this past week, there was still fog hanging around at 6 am, but gone by 7 am, and returning between 2 and 4 pm. But yesterday, it returned only briefly, for about an half-hour, and it is bright, sunny and over 75F, here today in Moss Beach.

OSBI Book Status

The Open Source Business Intelligence Book, as originally conceived, is dead. Despite the transparency of the blogosphere, we don't feel the need to go into the details as to why. The Open Source Business Intelligence research project, blog, wiki and lens, will continue, and improve, without the distractions and roadblocks posed by the book project.

We do want to share some of the things that we have learned during our year long attempt to have our book published.

The traditional process of publishing a book doesn't serve the needs of the technology industry. Joe Wikert, in his "A Book Publisher's Blog", discusses many of the issues. A simple summary would be that it simply takes too long; by the time a book is accepted and published, it is, in many cases, out of date.

One lesson that keeps coming up over the years, is that every partnership, every business arrangement must be in writing, with as many details and contingencies thought out as is humanly possible. Until everyone is willing to put things in writing, you aren't doing business.

Some large publishing houses are hopeful that eBooks will be the answer for their technical book sales woes. But as long as the model is the traditional publishing model, the problems aren't addressed. Whether the end product is a static eBook or a static physical book, books sales will continue to slide.

Our frustrations with attempting to use traditional methods, and our learning experience with online publishing platforms, as well as our use of various eBook systems is causing us to reconsider our formulation of the TeleInterActive Press, with its blogs, podcasts, wikis, surveys, CMS and document management systems. What would other authors want? What do consumers need? How must the publishing industry change? How will all of this come together into a viable new publishing model to make technical publications relevant, immediate, easily updated and convenient?

We'll see as we continue to develop the OSBI wiki, this blog and related lens, surveys, and total content/document management, all in the context of researching other book topics.

Meri^enda

We've been rethinking our podcasting strategy and hardware - mostly due to the poor sound quality of our previous podcasts. We also realize that we want to podcast on more than just open source topics, so "Open Source Conversations from the Open Source Café doesn't cut it.

Merienda in Tagalog [via Spain] and Merenda in Italian, mean snack or the small dishes that make up the snack, such as might be served in an Enoteca. Podcasts are very much the same, a small dish for the mind, to be taken in hand, and consumed on the run, or savored as you while away the time at your favorite wine bar, enoteca, caré or caffé. So, Meri^enda will be the name and tag for our podcasts going forward.

We did some web research, received recommendations from friends who are podcasting, and advice from Mike at Manor Music, Inc. and have begun investing in some podcasting gear [Note that links go to our Amazon store].

This gives us the capability to record directly to MP3, for quick podcasts from the field, the ability to do higher quality recordings, to roam around an audience, and even to record off the phone or skype or computer. We have some podcast plans for the summer, so keep a look out for Meri^enda. Enjoy.

Oh So Cold

I just stopped for gas near the top of Skyline by Hickey. The wind is blowing the fog in thick, cold streams of mist. As it was warm with a bit of sun when I left Moss Beach this morning, I wore a short sleeved shirt. I'm so cold.

Warm tea, that's the ticket. Did I mention I was cold?

Forward and Backward Pass in Time Management

There are two terms related to Critical Path that one may encounter. These are the terms Forward Pass and Backward Pass. These terms are related to ways of determining the early or late start [forward pass] or early or late finish [backward pass] for an activity.

Forward pass is a technique to move forward through a diagram to calculate activity duration. Backward pass is its opposite.

Early Start (ES) and Early Finish (EF) use the forward pass technique.

To determine the Early Start of an activity, factor in all its dependencies and see its earliest start date.

Consider the following simple diagram (durations are in weeks):
Simple Network Diagram of Forward Backward Pass example
Click to view original size

The Early Start (ES) for Activity B is 4. Why? B comes after A. A starts on week 1 and finishes on week 3. So the earliest that B can start is week 4. For simplicity, I think of it as: The duration of preceding activity + 1

The Early Finish (EF) is the earliest calculated time an activity can end. To calculate Early Finish, (ES for the activity + Activity Duration) - 1. From the diagram above, we can compute the EF of activity B as [(4 + 3) - 1] = 6. Hence, the EF for Activity B is 6.

Late Start (LS) and Late Finish(LF) use the backward pass technique. You can think of backward pass as calculating backward to see how much an activity may slide without affecting the finish date.

Late Start (LS) is the latest time an activity may begin without delaying the project duration. The simplest way one can compute the LS is adding the float to the activity Early Start. Using the simple diagram above, we know that Activity B is on the critical path, hence has a float of zero. Also, Activity B's ES = 4. Hence, LS = (0 + 4) or 4. Note that if an activity has a float of zero, ES and LS will be the same. &#59;)

Late Finish (LF) latest time an activity may be completedwithout delaying the project duration. One can compute LF by LF =(Activity's LS + Activity Duration) - 1. So the LF of Activity B = (4 + 3) - 1 = 6. Note that since activity B has a zero float, EF = LF.

:idea: For memory trigger, if the float of the activity is zero, the two starts (ES and LS) and the two finish (EF and LF) are the same. Hence, If float of activity is zero, ES = LS and EF = LF.

November 2019
Mon Tue Wed Thu Fri Sat Sun
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30  
 << <   > >>
The TeleInterActive Press is a collection of blogs by Clarise Z. Doval Santos and Joseph A. di Paolantonio, covering the Internet of Things, Data Management and Analytics, and other topics for business and pleasure. 37.540686772871 -122.516149406889

Search

Categories

The TeleInterActive Lifestyle

Yackity Blog Blog

The Cynosural Blog

Open Source Solutions

DataArchon

The TeleInterActive Press

  XML Feeds

Mindmaps

Our current thinking on sensor analytics ecosystems (SAE) bringing together critical solution spaces best addressed by Internet of Things (IoT) and advances in Data Management and Analytics (DMA) is updated frequently. The following links to a static, scaleable vector graphic of the mindmap.

Recent Posts

powered by b2evolution