In a highly collaborative environment such as an academic institution, the existence of a ubiquitous common repository for file based storage, retrieval and sharing is a necessity. This Institutional File Space (IFS) needs to implement such storage in a manner that is fully compatible with all the supported platforms in use at the University.

Here's the quick and dirty FAQ for the IFS project

Q: What is it?
A: Quite simply, the IFS project hopes to design file space that adequately serves the needs of all the University supported clients.

Q: What are the benefits of it?
A: The main benefit will be a closer match between the file service and the clients that use it (i.e. Unix will continue to use AFS primarily and PC's and Macs will be able to use CIFS against a file service that will honor their mandatory locking requirements)

Q: When will it be ready?
A: A pilot is projected for spring/summer with a roll into production for August 1, 2001.

Q: Who will it affect?
A: It will affect only those that would choose to migrate to the new IFS. AFS and all the existing infrastructure, policies and procedures supporting it will remain.

With the help of OIT's Strategic Consultants and others, two charters have been drafted that will define two different modes of input into the project. The formation of these groups (the Stakeholders and Technical Interest groups) is a means of coordinating and facilitating input for the project by providing focus. Everyone has valid input, but without providing a channel for that input, I could spend way too much time trying to coordinate, collate, check and double check each suggestion to see if that is what the majority on campus wants, needs, etc... To that end, I hope everyone understands the need for such official groups to exist (at least for me).

Stakeholders Group
This group will be primarily asked if a proposed solution meets their needs. At various stages in the project, this group will be asked for a sign off. In other words, "so far, the project is addressing (or has addressed) our (my) needs." The degree to which it does or does not fulfill that stage's requirements are to be addressed in meetings held and led by this group's leader (Tom Laughner, OIT/CCR). This group will not make design decisions. This group defines functionality, not specification.

Technical Interest Group
This group will be an advisory technical design group. This group should comprise the expertise in the various technological areas that will be touched, or addressed, in the design of the solution. The role here, specifically, is to focus the vast diversity of technical expertise available in the design, build and then test phases of the project. I will be leading this group (as project manager).

I have been given a list of people who have already spent a great deal of time (some time ago!) putting together the FR documents. I sincerely appreciate the effort that was put forward and can only hope that I can finally apply some substance to the project to reflect that work. I understand that there is a great number of people interested in being involved with the project and I hope to harness that energy, but at the same time, it can be very difficult to manage everyone's input if it is presented in an unorganized raw fashion. Hopefully, the formation of these groups will eliminate the discontinuity so that information flow is facilitated. That said, the OIT Strategic Consultants along with Tom Laughner will be identifying the Stakeholder Group members. If you have any questions about this group and/or if your area is represented, please ask your SC. Don't know who that is? Check here.

In the Technical Interest Group Charter, I have brainstormed a quick list of technical areas that I could think of that need to be covered. I ask anyone who feels that they can contribute to technical design decision discussions, and who think they may be of value on the IFS-TIG, to please email me <krowland@nd.edu>. I still plan to use the listserv and the project home page as a global communication tool for discussion and status, but I would like to officially convene some meetings with group members to get the specific technical details nailed down. That way, updates to the global campus will have some substance behind them as well as a group of people (and not just me!) who can address questions, comments, etc... about the project.