CompuServe Thread

#IN MEMORIUM…ODE TO CBM

3 messages in this thread
#68233From: Jim VentolaMay 18, 1987 12:22 AM
Especially, do you worry that the FCC is so busy pursuing a conservative social agenda that its work of supervising the free market is getting shorte shrift than usual. Why should it take more than a week for the FCC to approve a product? Can't they hire more technicians to test the stuff? Regards, Jim
#68247From: E. J. Lippert IIMay 18, 1987 2:03 AM
Jim: First, the FCC doesn't test anything! The responsibility for testing is up to the manufacturer. We must test and re-test until our products pass, then, and only then, do we submit the proper paper work (which includes the test data from a certified testing facility) to the FCC for their formal approval. The FCC's task is that of paper shuffeling only. Second, I personally have seen perfectly filled out forms and test reports take 117 days to be returned as approved. Third, the FCC claims tight budgets restrict their preformance. They say that they have so many areas to police (from commercial T.V. to CB Radio) that they just can't do it all on the budget allowed, and FCC Part 15 Type B approvals are not the highest priority. Well, I could go on, but I think you get the idea. RED TAPE MAX. E.J. Lippert II C Ltd. – (316) 267-6322
#68261From: MICHAEL DAUGHERTYMay 18, 1987 7:32 AM
Ed, So, going back to our critical path charts, we see that a significant task in releasing a new product is the FCC approval task. Now, going back to my basic systems analysis courses, which I had as an undergraduate, we can see that ALL tasks within a critical path analysis may not impact the release date of a product, only the "longest" paths effect the release time. Sorry to say it, but if they would have talked to you, they would have realized that 117 days was possible! Strangely enough, people get tired of promises pretty quick, and they get tired of "pipe dreams" when it comes to purchase even quicker. Mike