Well, that was a different discussion. While it does seem that the IT group was able to solve the problem that Jamie had you don't have a warm and fuzzy feeling that they will be able to do the same for your little group. That isn't to say that they won't. Just as Jamie pointed out you'll never know until you ask. But you feel that this would be something that you'll let Molly ask up the chain. Jamie was doing a support for the company management for a company-wide data collection and retention. That task had a good bit of overall company exposure. So you can see why she didn't have too many problems getting the IT group to help support this.
But the requirement for your group to store the information on your customers is different. And this task might not warrant the high overhead for the IT group.
But the fact that there wouldn't be an additional cost is a good point. And the fact that you'd end up getting the data structure and elements that you are looking for is good. This is similar to the discussion you had with Dan. Then it was more of a localized/locally shared Access program and this is a centralized ORACLE approach but some of the same points come out in each.
The above section covers some of the key lessons noted after the interview with Matt. If you have any insights in this approach or any other thoughts that you feel would enhance the lessons above remember that the built-in comments system is there for you.
Before we go to the next page take out a piece of paper and your favorite writing instrument (you should be seeing a pattern here) and see how many pros and cons that you can come up with regarding this approach.
When you have listed your pros and cons continue to our pros and cons list.
No comments:
Post a Comment