DePaul University Networks and Telecom Group J. Kristoff Request for Comments: 1 N&T/R&D Category: Best Current Practice January, 2002 Class: Public Revision: 1.0 Charter of the Research & Design (R&D) Team Status of this Memo This memo specifies a DePaul University Networks and Telecom Best Current Practices for the DePaul University community and requests discussion and suggestion for improvements. Distribution of this memo is unlimited Copyright Notice Copyright (C) DePaul University (2002). All rights reserved. Abstract This DPUNET-RFC documents the mission, composition, roles and organization of the Research & Design Team. Kristoff Best Current Practice [Page 1] DPUNET-RFC 1 R&D Charter January 2002 Table of Contents 1. Mission.....................................................2 2. Membership and Organization.................................2 2.1. Team Leader...............................................2 2.2. Engineer..................................................3 2.3. Other Participants........................................3 2.4. Liasons within Networks and Telecom.......................3 2.4.1. Projects................................................3 2.4.2. Operations..............................................3 2.4.3. Security................................................4 2.5. External Relationships....................................4 2.6. Openness and Confidentiality..............................4 3. Team Goals..................................................4 3.1. Technology Research.......................................4 3.2. Network Design............................................4 3.3. Standards Development.....................................4 3.4. Long Term Planning........................................5 3.5. Pilot Projects............................................5 3.6. New Initiatives...........................................5 3.7. Education and Training....................................5 3.8. Industry Participation....................................5 3.9. Technical Point of Contact for Networks and Telecom.......5 4.0. Work Selection Criteria...................................6 Acknowledgments................................................6 References.....................................................6 Security Considerations........................................6 Editor's Address...............................................6 1. Mission The Research & Design (R&D) team helps to provide network architecture direction in support of DePaul University's mission of education, community service and research. The R&D team helps to enable a network environment that anticipates the needs and exceeds the expectations of its users. 2. Membership and Organization The R&D team consists of a team leader and one or more engineers. Others may participate in the R&D team efforts on an as-needed basis. Generally participants will come from within the Networks and Telecom (N&T) group, but people from other groups or other organizations may be invited to participate, usually to assist on a specific project. 2.1. Team Leader The R&D team leader is responsible for general oversight of the R&D team. There must be a single R&D team leader at any one time. The team leader is the interface to other groups within Networks and Telecom, the management team within the Information Services Division and external constituents. The R&D team leader job description is defined in [HR-RDMGR]. Kristoff Best Current Practice [Page 2] DPUNET-RFC 1 R&D Charter January 2002 2.2. Engineer An R&D engineer is a full-time participant in the R&D team led by an R&D team leader. The R&D engineer job description is defined in [HR-RDENG]. 2.3. Other Participants The R&D team often draws upon resources from other groups within the Networks and Telecom group, other areas within the University or even from outside institutions and organizations. The R&D team encourages participants from other areas, which help provide greater insight and expertise than is available within the R&D team. Participants outside of the R&D team may report to the R&D team leader or to a designated R&D engineer for guidance as necessary. Regardless of the relationship with the R&D team, each participant is expected to operate under the principles and guidelines outlined in this charter. 2.4. Liasons within Networks and Telecom The Networks and Telecom group is currently divided into four major areas. 1) Research & Design, 2) Projects, 3) Operations and 4) Security. The Operations area is further divided into a) Infrastructure and b) Services. Positive relationships with each of these groups will help determine the success of the R&D team. 2.4.1. Projects The R&D team will often initiate new services to be deployed within the DePaul University environment. The Projects team leads the install of new services so it is essential that the R&D team works with the Projects team to create the initial deployment plan. The R&D team must provide guidance on overall configuration and operation for any new initiative. Standards documentation and training should accompany any new initiative. The R&D team may participate in the deployment of any new service. The R&D team provides guidance on deployment and operational issues with any new service led by the Projects team. 2.4.2. Operations The operational teams are the link to the end users. The operational teams therefore have a great deal of insight into the needs and expectations of end users. R&D relies upon the operational teams to provide feedback into areas that require R&D focus. The R&D team also relies upon the operational teams to identify weaknesses with current support of services. The R&D team should work with the operational teams to develop enhanced services, management techniques or tools to make the operations job easier and more efficient. Kristoff Best Current Practice [Page 3] DPUNET-RFC 1 R&D Charter January 2002 2.4.3. Security The R&D team often develops new techniques and strategies involving internetwork security services. The security team uses the R&D team to help develop new security services for the University. The R&D team also provides overall network architecture direction that may influence the security team's services. 2.5. External Relationships The R&D team often acts as representative for the Networks and Telecom Group, Information Services or the entire University. Relationships with entities outside of the R&D team are kept as informal as possible. 2.6. Openness and Confidentiality The work of the R&D team is generally open to the DePaul community and outside entities. The R&D team may on occasion decide not to make its work publicly available due to security or privacy issues. Any member of the Networks and Telecom group is welcome and encouraged to attend the informal team meetings. Others are generally welcome providing proper notice and invitation. In some cases, the R&D team may have non-disclosure agreements (NDAs) with outside entities. In these cases, the entire R&D team and its participants must abide by the NDAs at all times. The R&D team leader should be responsible for the administration of all NDAs. 3. Team Goals This section outlines a number of the core goals or functions of the R&D team. The team may work on tasks outside of these core goals, but they should generally be avoided. 3.1. Technology Research The R&D team performs basic and applied research on technologies and methods that fall within the scope of the Networks and Telecom group. This function may often not result in enhancements or new services. Rather, this function is assumed to be beneficial simply for the sake of learning, understanding and exploring. 3.2. Network Design The R&D team provides overall network architecture guidance for the Networks and Telecom group. New or changing services that affect the architecture of the network must be verified by the R&D team before planning and testing begins. 3.3. Standards Development The R&D team leads the development of Networks and Telecom standards. These standards provide guidance for the community within and outside the Networks and Telecom group. The standards must be in writing and should be made publicly available. Kristoff Best Current Practice [Page 4] DPUNET-RFC 1 R&D Charter January 2002 3.4. Long Term Planning The R&D team assists the management team for Networks and Telecom and other groups within DePaul University to set long term plans involving internetworking technology. The R&D team may also set its own long term plans and goals. Long term plans and goals should be reviewed by other teams within Networks and Telecom. 3.5. Pilot Projects The R&D team leads pilot projects on new technology, new initiatives or enhanced services. Pilot projects are the vehicle used by the R&D team to test services outside the R&D environment. Administration and support of the new services is the sole responsibility of the R&D team. For pilot projects to become a supported service, the R&D team must enlist the help of the Projects Team within Networks and Telecom for transition. 3.6. New Initiatives The R&D team may develop new services to roll out to a group or the University. New initiatives that are to become standard services for the Networks and Telecom group must be properly transitioned into the Projects or Operations Teams. The R&D team must plan, document and train Networks and Telecom staff on any new initiatives. The liaison team(s) must fully acknowledge that a transition from R&D to operations has been completed. The R&D team must assist and support new initiatives until operational teams have signed off on the transition. 3.6. Education and Training The R&D team should provide education and training for its team members, the Networks and Telecom Group, the University community and outside entities on topics of interest. The R&D team may often build up expert knowledge in various areas. This knowledge should be shared as widely as possible. The R&D team should also regularly attend avenues that offer the team member a chance to learn. 3.8. Industry Participation The R&D team should participate in industry groups, mailing lists, conferences, external research projects and other avenues to expand their network of contacts and ideas. R&D team members are also encouraged to provide leadership in these functions as appropriate. 3.9. Technical Point of Contact for Networks and Telecom Vendors, industry consortia, research organizations and other external entities often require a technical point of contact (POC) for the Networks and Telecom group. The R&D team leader should be the POC on behalf of the Networks and Telecom group, particularly with external institutions and organizations. Kristoff Best Current Practice [Page 5] DPUNET-RFC 1 R&D Charter January 2002 4.0. Work Selection Criteria The R&D team must weigh in balance a number of conflicting strains on available resources with which to apply to the team goals as mentioned above. Selecting the priority of team goals should be done by the R&D team lead and that person's upper management. Acknowledgments Thanks to all those within the Networks and Telecom group for their ideas and support. References [HR-RDMGR] Network & Telecom Research and Design Manager job description, DePaul University Human Resources Department, July 2001. [HR-RDENG] Network & Telecom Research and Design Engineer job description, DePaul University Human Resources Department, November 2001. Security Considerations This memo does not raise any known security threats. Editor's Address John Kristoff Research & Design, Networks and Telecom DePaul University 1 East Jackson Boulevard Chicago, IL 60604 USA Phone: +01 312 362-5878 EMail: jtk@depaul.edu Kristoff Best Current Practice [Page 6]