[153] in magellan
Re: Minutes: 23 April 1999 meeting
daemon@ATHENA.MIT.EDU (Mike Barker)
Mon Apr 26 08:10:33 1999
Message-Id: <4.1.19990425181231.00a08ae0@po11.mit.edu>
Message-Id: <4.1.19990425181231.00a08ae0@po11.mit.edu>
Date: Mon, 26 Apr 1999 07:30:00 -0400
To: magellan@MIT.EDU, delivery@MIT.EDU, integration-ptl@MIT.EDU
From: Mike Barker <mbarker@MIT.EDU>
In-Reply-To: <kr89Z=Jz0001M3Zkdg@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Some corrections and amendments...
At 04:01 PM 4/23/99 +0000, Bill Cattey wrote:
:)DETAIL:
:)
:)1. New initiatives for FY2000 Budget:
:)
:)FY2000 budget is flat. But we need a heads-up on new initiatives that
:)are going to come along through the year.
I don't think this was stated, nor do I consider it as a very good summary
of what I thought we were doing.
I.e., I thought we were trying to identify new initiatives for the FY2000
timeframe, specifically to support the May 7 ITLT off-site which is going to
deal with planning for that period.
:)ITLT Identified one-time-only items:
These were not one-time-only items. They are the major FY2000 items
identified by ITLT.
:) W92
:) Increased RCC Expenditures
:) Software Costs
:) Oracle changes
:) Y2K
:) Network capacity expenditures
A critical question posed by ITLT is how to take the Five Year Plan
initiatives and the current work as shown in the project database and
provide a bridge between the current work and the work of the future.
Greg passed out a handout consisting of the 5YP matrix and a printout
of the project database list.
<clip>
:)Project Management -- aggregate, make consistent across MIT
I don't believe I made the point strongly enough in the meeting -- first
let's make our approach consistent within IS. I strongly believe we are not
being as effective as possible due to the distributed approach being taken.
And as Bob commented, yes, I am advocating for a Project Support Office, at
least functionally.
:) Web Services
This was specifically the likelihood of providing centralized web services
(or web business service, as some like to call it) as an IS service.
:)Technology Transfer (scale, reusabiliti, install, upgrades)
As I understood it, we were not going to use the buzzword "technology
transfer" for this. You identified it as something closer to being industry
evangelists for the Athena approach to certain issues, such as scaling,
serial reusability, installation, and upgrade.
<clip>
:) User Interface of Athena -- example: desktop.
There was another point, concerning the additional costs needed to deal with
shortening time cycles for business recovery.
There was also reference to the possibility of added costs for business
recovery due to losing E40 as an alternate center, and to the potential loss
of RLE causing us to go to COMDISCO.
:) 2. Project Database Update:
There were two questions in regard to this.
First, it seems as if we are reducing the functionality for Unix users
because they do not have an easy way to produce web pages.
Unix needs to get a good html editor, or other support for web work.
Second, there was a question of how will we let people in projects (in other
processes, etc.) know about the expected usage of the project db.
Realistically, Mike is going to have to go to a bunch of meetings.
:) 3) Developing the "Buy" process:
:) Bob handed out draft of project announcement to revise the published
:) Delivery process model to better describe the "Buy" aspect of
:) Delivery.
Bob indicated that there is no pressure to hurry this, so he expects to take
some time and get the project leader right for the team.
There was a comment that it is not always Buy vs. Build, sometimes it needs
to be Buy AND Build, but that we need to be careful when Building not to
destroy the ability to upgrade, etc. of what we have built. We need to
build around, rather than through.
:) Warning for Survey
Let's get it right. The warning concerned the fact that we have no adequate
method of providing bulk distribution of information (e.g., tell all the
undergrads something), but we are being pushed to try to do something. More
than the particulars of the current case, I wanted to remind this group that
this is an issue that comes up regularly, and we do not currently have any
way to meet the desires.
Warning: There is no bulk distribution method right now. So don't promise it.
:) Wade's Walk -- In memory of Steve Neiterman.
:) A couple folks had an idea to do this, and are now asking if
:) people are interested.
I suspect this will be very cryptic for those who weren't at the meeting.
The basic idea is to set a date and time, and have anyone who wants to walk
along a set course. They have investigated what it will take to have the
official permits, etc. and are now asking to see if there is sufficient
interest to move ahead with this.
<clip>
:) Next Meeting
5/28, I believe?
"This requires ... that we work to create at MIT an atmosphere of civility,
collegiality, and mutual respect - one that stimulates and supports all of our
faculty, students and staff." Charles Vest, Jan. 12, 1994
