[30] in iswork
Re: Request for server for IS Operational Plan Alive!
daemon@ATHENA.MIT.EDU (Peter B. Kelley)
Fri Mar 24 09:42:17 2000
Message-Id: <200003241442.JAA17962@melbourne-city-street.MIT.EDU>
Date: Fri, 24 Mar 2000 09:43:48 -0500
To: Tim McGovern <tjm@mit.edu>
From: "Peter B. Kelley" <kelley@MIT.EDU>
Cc: rar@mit.edu, iswork@mit.edu
In-Reply-To: <v04020a00b50126ef6845@[18.152.1.21]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Tim,
This sounds really good, and of course smaller is easier.... I'll work on
it for you and see what we can put together.
--Pete
At 09:12 AM 03/24/2000 -0500, Tim McGovern wrote:
>Peter -- Sorry to hear we've missed the FY2000 window, but not surprised.
>I will try to gather some of the metrics you asked for from the team.
>
>I like the idea of going with a smaller server. Since this new service
>will supplant the current Project DB service on UTAH, we figured that a
>machine of roughly that size/power was going to be appropriate, but I
>suspect UTAH was generously overconfigured. Also, If we can get a smaller
>machine fitted out for our purposes, after we've migrated the current PDB
>information, we could probably consider UTAH itself in our upgrade plans.
>How does this sound to you?
>
>Thanks for your prompt reply,
>Tim
>
>At 10:47 PM -0500 3/23/00, Peter B. Kelley wrote:
>>Tim,
>>
>>We anticipated your needing a server and have added it to our list of
>>purchases to be acquired. Unfortunately, the last review of equipment
>>purchases has this particular server targeted for the FY2001 budget cycle,
>>not because of scheduling, simply because of budgetary constraints. The
>>best I can say right now is that we'll review the current equipment
>>allocations and targeted applications and try to make some adjustments to
>>accommodate your request. I will get back to you on this.
>>
>>In the meantime, perhaps you can help us out on the configuration side,
>>with an estimate of disk resources, and anticipated hits per day. Also,
>>would it be possible to bring this application up initially on a small
>>server with later migration to something like an E250 as hardware becomes
>>available?
>>
>>Thanks,
>>
>>--Pete
>>
>>
>>At 03:50 PM 3/23/00 -0500, Tim McGovern wrote:
>>>Peter,
>>>
>>>This is a request for server hardware for the project named above.
>>>
>>>You probably saw my mail of Feb 17 to infosys (included below), summarizing
>>>the fact that ITLT approved the Delivery work recommendations for making
>>>the IS Operational Plan Alive.
>>>
>>>As part of that effort, we will be needing a server that will support the
>>>web server, java servlets, and Oracle backend database to achieve our
>>>goals. From conversations with Miki, we think that the overall power and
>>>capacity requirements are consistent with what we're using for the Project
>>>Database today -- SPARC Enterprise 250, I think.
>>>
>>>This project is sponsored by Jim Bruce, who has asked us to be in
>>>production by the end of June of this year, as we head into the new fiscal
>>>year. Therefore, we need to get hardware up and running pretty quickly.
>>>Can you please let us know when your group could provide us with the
>>>hardware. Miki will be glad to install the web server and database
>>>components, if your folks can get the hardware, os and kerberos support
>>>installed.
>>>
>>>I look forward to hearing from you...
>>>
>>>Tim
>>>
>>>-----
>>>
>>>>Date: Thu, 17 Feb 2000 14:56:24 -0500
>>>>To: infosys@MIT.EDU
>>>>From: Tim McGovern <tjm@MIT.EDU>
>>>>Subject: Project Update: IS Operational Plan Alive! Moves from Discovery
>>>>to Delivery
>>>>Cc:
>>>>Bcc: tjm@MIT.EDU
>>>>X-Attachments:
>>>>
>>>>To: All Information Systems Staff
>>>>
>>>>Good afternoon, everyone,
>>>>
>>>>On behalf of Greg Anderson and Bob Ferrara, I am very pleased to announce
>>>>the transition of the IS Operational Plan Alive! work from I/T Discovery
>>>>to I/T Delivery. This project has been underway since November, 1999, and
>>>>its recommendations were accepted by ITLT last week.
>>>>
>>>> Notebook: http://mit.edu/is/discovery/iswork/
>>>> Final report: (http://mit.edu/is/discovery/iswork/report.html)
>>>>
>>>>This project was asked to explore what would be required to keep the IS
>>>>Operational Plan Alive. The results of that inquiry are that there are
>>>>two different, but connected, parts to the answer: 1) evolve existing
>>>>behavior at many levels of the organization vis-a-vis the communication of
>>>>information about the work we're doing, and 2) develop a tool, a simple
>>>>but extensible design, that can manage information about IS work, and
>>>>provide staff with an easy way to review, comment, extend and apply that
>>>>information.
>>>>
>>>>As this work moves into I/T Delivery, we want to create a team that will
>>>>accomplish both aspects of the work outlined above. We are looking for
>>>>folks from around IS who have a strong interest in participating in this
>>>>exciting effort, and who have one or more of these skills:
>>>>
>>>> Organizational behavior, diagnosis, evolution and development
>>>> Web-based application user interface design
>>>> Web service, Oracle rdbms and UNIX system setup & administration
>>>> Java servlet application design and development
>>>> Web-based help and documentation design and development
>>>> Data migration
>>>>
>>>>The time commitments needed are relatively small, but to be of maximal
>>>>effect, we'd like to identify the whole team before we begin planning the
>>>>work. Our working target for completion of the work is June of this year.
>>>>If you have an interest in this work, and would be available during the
>>>>timeframe above, please drop a message to <tjm@mit.edu>.
>>>>
>>>>The Executive Sponsor for this work is Jim Bruce, with tactical direction
>>>>provided by Bob Ferrara and Bill Hogue. ITLT will be the final gate on
>>>>the transition of the work into Service and Support.
>>>>
>>>>The team's success criterion will be to dovetail the adjustments to the
>>>>organizational issues identified and the development of a tool to support
>>>>those adjustments. As the team's work unfolds, we ask for your
>>>>cooperation, input, and assistance.
>>>>
>>>
>
