ࡱ> `  bjbj 4 F   ( fffz8V|҉<zZ:T|$hRf> > T|-$,,,J> T(f|,,,Tf| cqs,<Z,zf 3 , Zzzzzzzzzzz> > > > > >  Preliminary Recommendation from the Deans Website Subcommittee The committee was given a three-part charge: 1. How do we balance consistency, functionality, and marketing goals? 2. How do we establish a balance between consistency and creativity? 3. How do we assure websites are accurate and current? We have conducted our meetings concurrently with the meetings of the Presidents Ad Hoc Website Review committee and members of our committee are also members of that committee. At our first meeting each of the members of the committee was given an opportunity to discuss their own concerns about our website. Among the issues/concerns that we noted/shared/discussed were the following: Design/attractiveness Difficulties in use/navigation Incorrect and out of date entries Colors that do not represent ɫӰ Lack of time, money, staff, training. Important items are buried on our site ɫӰ research profile is missing Home page is too cluttered/complicated Site is not focused to particular audiences Site does not enhance ɫӰ image. Needs to be simple but elegant. Technology programs information is buried Need to focus on prospective/student and family Too many web maintainers are self-trained and do not have enough time Search engine is unworkable. Template restrains creativity. Faculty employment opportunities/other jobs hard to locate. Over the course of four more meetings, with active participation from all who were able to attend, the committee has reached the following conclusions. Central to our deliberation and underlying our recommendations is the clear need for additional resources in support of an enhanced approach to website design and maintenance. If money and or human capital were no object, our conversation would no doubt have taken a different tack. That said, and in pursuit of accuracy, consistency, currency, and functionality, we recommend the creation of a central content management system such as that marketed by Microsoft (see attached webpage), featuring a common interface, and designed for dynamic updating from existing data. Basic data (catalog, directory information, departmental, division, and/or program mission, etc.) will appear in a common format and will be updated automatically. Gonzaga University has adopted such a site. (We recommend most specifically and forcefully that our common interface does not dominate the page, and that it clearly reflect our institutional identity) The issue of creativity will be addressed where desired by establishing links imbedded in the central managed site that lead to exhibit sites. These sites will connect with the CCMS in such a way that central data specific to the exhibit can be summoned without the user having to leave the site. While we believe that exhibit sites must allow maximum freedom, we also believe that there is value in minimal brand identification and we recommend a watermark approach to all official pages. The idea, first broached in the ad hoc committee meetings is a HUB or Zone concept, one that presents as clear and seamless a path for the user as possible. It is imperative that there be ongoing dialogue and clear direction from publications and/or any other entity charged with establishing and maintaining the universitys image in terms of this effort. In addition, there must be staff assigned to provide training and assistance in website construction and design, assure ADA compliance, and exhibit owners must be provided tools (Dreamweaver, FrontPage, etc.) to help to assure that they are attractive, informative and of professional quality. Links to individual sites may be a desired feature of these exhibits. Links to personal homepages may appear on these sites. Where they do, some disclaimer may be necessary. Marketability demands user focused and friendly websites. Browse functions must be non-hierarchical and should be organized to minimize multiple page digging. Our decisions must take into account the plug-ins and other enhancements users may need to view our pages, and the psychological and or economic barriers that may be raised by them. In order to be most responsible to multiple audiences/markets, we also believe that serious consideration must be given to portal technology so that we can mass-personalize our websites. Finally, it is our recommendation that website review be conducted on a continuous basis, with major strategic review at least every third year. Respectfully submitted Michael J. Hood  Gonzaga University Implements Content Management Server to Create a Visually Consistent Web Site Published: November 2002 Gonzaga University wanted to restructure its Web site so it delivered a consistent message and would be easier to manage than its current site. To achieve this vision, Gonzaga implemented Microsoft Content Management Server and was able to reorganize and restructure its entire Web site without hiring additional staff to its Desktop Support Services department. Now, Gonzagas Web site delivers a consistent message across all departments and activities and empowers the right people to publish content, thus freeing up the Desktop Support Services team to focus its efforts on developing complex, mission-critical applications. Situation Located in Spokane, Washington, Gonzaga University is a private, four-year, Jesuit university. Its educational philosophy aims to educate the whole personmind, body, and spiritthrough an integration of science and art, faith and reason, action and contemplation. Like many academic institutions, each school or department at Gonzaga University values its independence. From a technology perspective, this includes having the freedom to develop and customize tools that fit the specific needs of each academic department. The importance of this independence was visibly apparent on Gonzagas Web site. Every schoolfrom business to education to lawhad its own Web site that resided on its own Web server. In addition, a main university Web site included information about the College of Arts and Sciences, as well as other content, such as admissions, alumni, and athletics information. Chris Gill, Director of Desktop Support Services at Gonzaga, and his small team of one full-time employee and several student employees were responsible for maintaining the universitys primary Web site, which was hosted on Microsoft Windows 2000 Server with its built-in Web server, Microsoft Internet Information Services 5 (IIS). However, the team was not in charge of managing the content. Instead, independent Web designers or other student employees would develop the content, structure, and design; then the Desktop Support Services team would post this content to the Web site. A similar process occurred when information was posted to any of the individual schools Web sites, such as the School of Business or Law. Unfortunately, because most of the information was formatted differently, without interrelationships or a common theme among the university schools, departments, and organizations, the result was a mix of Web sites that had no consistency. Explains Gill, One of the problems with our process was that no one who was creating the content stayed around long enough to maintain it. Therefore, this orphaned content would languish on a site, available for any site visitor to access whether it was current or not. This was beginning to create some credibility issues with Gonzagas Web site. Gonzaga knew that a Web site can be a mission-critical tool for a university. In presenting university information to a broad spectrum of people, a good Web site is a vital medium through which to reach and market to prospective and current students, and alumni. Gonzaga knew that the site had to be more audience-centric and become a positive, useful, and beneficial tool for its audience. Accomplishing this goal would require a solution that would allow a convergence of each independent Web site into one global site, enable its limited available resources to maintain a consistent look and functionality across the entire Web site, and empower the people with the right knowledge, such as department heads, to become content managers. Solution Gonzaga contracted Aurora Consulting Group, a Pacific Northwest-based company that offers high-quality, state-of-the-art information technology solutions to mid-size businesses, to implement a content management server solution. In a short time, Gonzaga and Aurora were able to build and deploy a content-rich Web site that integrates perfectly with Gonzagas existing network structure: IIS, Microsoft SQL ServerTM, and Microsoft Internet Explorer 6. With Microsoft Content Management Server, we were able to turn Gonzagas Web site into a rich, dynamic information center that provides an excellent resource for students, faculty, and the community, explains Beth Britt, Chief Executive Officer (CEO) and President of Aurora Consulting Group. Gonzaga had two criteria for the project: The solution must allow the university to maintain central control of the visual aspects of the Web site, and it must provide a simple, distributed way to add content. Both goals were achieved with Microsoft Content Management Server. Centralizing Visual Control The deployment team developed templates for departments to use when posting information. Featuring a consistent design and navigation scheme, the templates facilitate adherence to publishing standards and university branding without diminishing the flexibility of the publishing environment. Empowering Content Managers Bottlenecks often occur when posting content to a Web site is the responsibility of a Webmaster. Gonzaga wanted to streamline the posting process by empowering people to create and post their own content. Posting information is easy with Content Management Server, and content managers are not required to have Web-developing skills such as knowledge of HTML or ColdFusion. Instead, Content Management Server roles are used to identify who can publish or create content for the Web site. At Gonzaga, about 150 content managers, such as a faculty member or department head who is familiar with the content to be posted, are assigned to an author, editor, or dual author/editor role. Authors can create or edit content for the Web site, and editors approve and post content to the Web site. Aurora also completed some additional customization that makes adding a department to or removing a department from the Web site as easy as selecting a check box. Aurora also created a university calendar that departments can use to quickly and easily post upcoming events. Benefits Today, Gonzagas Web site has evolved from a complex mix of 15,000 Web pages, many of which contained outdated information, to a streamlined collection of pages, each of which has a solid purpose and provides helpful information for its intended audience. In addition, Gonzagas Web site is easy to manage, has a consistent look and functionality, and helps increase the visibility of Gonzaga Universitysomething that was only made possible with Microsoft Content Management Server. Explains Britt, Gonzaga has a huge amount of content on its Web site, which internal and external resources are pointing to. But without the simple posting methods enabled by Content Management Server, creating and maintaining this complex site would have been impossible. Improved Web Site That Is Easy to Build and Manage The Content Management Server solution allows for a significant increase in the number of content managers who can contribute information to the Web site, from approximately 40 people to almost 150 people. It also enables the Desktop Support Services team to rebuild and redesign Gonzagas Web site without increasing staff because most content site management is in the hands of people who know the content best. This transfer of power significantly reduces the workload of the Desktop Support Services team, enabling them to concentrate on developing new or customized applications that will integrate with Content Management Server. For example, the group is currently working on an application that will enable continuing education students to register for classes online. Using Gonzagas content course management system, the application will track these enrollees and will track their grades and transcripts in its central system. Instead of spending time changing words on a page, fixing dead links, and changing out graphics, our department is now developing applications that have broader appeal and usefulness, and are more mission critical in nature, says Gill. Improved Web Site with Consistent Look and Message Using templates, Gills team easily created a consistent look and functionality across the site. Now, a single interface puts forth a unified message about Gonzaga University to current students, prospective students, and alumni. The complicated interface was created by separating the graphic design and navigation components from the content development component. Gonzaga overlays its Web structure on top of content in a way that separates the two, both physically and logically, and places control of those elements in the hands of those who are most qualified for the task. Enhanced Web Site with Improved Visibility of Gonzaga University Since deploying its solution in July 2002, Gonzaga has seen a remarkable increase in the number of hits to its site. For example, in September 2001 the average number of hits per day to the site was 67,136. However, in September 2002, this number grew dramatically to 264,094. In addition, the number of pages viewed per day has doubled from 20,657 in September 2001 to 42,978 in September 2002, and the average visit length has extended from an estimated 9 minutes to an estimated 12 minutes. This increase in traffic suggests that the universitys Web site is more accessible, being used more and assures Gonzaga that more people are learning about what it stands for, in a unified vision. Not only is the Web site attracting more visitors, but it is also providing many ways to distribute information. Explains Joe Poss, Associate Director of Major Gifts for the university, The new Web site is allowing us to communicate with our audiences in ways we never even dreamed possible just a few years ago. With Content Management Server, we can change our Web site every day, from anywhere in the world, keeping it constantly fresh and current. One group this will benefit is Gonzagas alumni base, which is growing aggressively, and expecting more dynamic, electronic communication. Poss explains plans to use the Web site to enhance a reunion in the summer of 2003 for members of the universitys Gonzaga-in-Florence program. We plan to update the site on a daily basis with pictures from Florence, so that Florence alums who cant travel to Italy can still feel like they are a part of the reunion. Everyone is excited about the possibilities were beginning to see to reunite the university and its alumni. Moving forward, Gonzaga is excited about the possibility of expanding its Content Management Server solution to create intranets and portals that continue to encourage community building for faculty, staff, students, and alumni. Weve taken an organically structured Web site and fine-tuned it into a very structured, organized, drill-down system that encourages visitors not only to look across the breadth of information that we have, but also to explore deeply into the site, explains Gill. Using Content Management Server, weve accomplished a complete redesign and restructure of our Web site, and I didnt have to hire new staff or increase my budget to manage the site. The value that Content Management Server provides Gonzaga will become strikingly apparent over time.  For More Information For more information about Microsoft products and services, call the Microsoft Sales Information Center at (800) 426-9400. In Canada, call the Microsoft Canada Information Centre at (877) 568-2495. Customers who are deaf or hard-of-hearing can reach Microsoft text telephone (TTY/TDD) services at (800) 892-5234 in the United States or (905) 568-9641 in Canada. Outside the 50 United States and Canada, please contact your local Microsoft subsidiary. To access information using the World Wide Web, go to: http://www.microsoft.com/ For more information about Gonzaga University, call (800) 322-2584 or visit the Web site at: http://www.gonzaga.edu/ 2002 Microsoft Corporation. All rights reserved. This case study is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. NEW DIRECTIONS FOR INSTITUTIONAL RESEARCH, no. 113, Spring 2002 Wiley Periodicals, Inc. 37 3 Building Portals for Higher Education Richard A. Pickett, William B. Hamre This chapter explores the underlying purposes and architecture for the use of portal technology as the keystone for knowledge management systems in higher education. The discussion of portal technology is exemplified by Santa Barbara City Colleges development of portal strategies and processes to support the colleges Intranet. There are many definitions of a portal. Gartner Group includes four basic components in its definition of a portal: connection, content, commerce, and community (Yanosky, 2000). Santa Barbara City College has developed the following working definition for its knowledge management project: A portal is a personalized collection of information, content, and services. Personalization is a key to a successful knowledge management implementation, as it provides access to targeted information based on individual roles and responsibilities within the institution. The collection of disparate content into a well-structured personal portal page is also an important element of success in the design and implementation of a portal. Finally, the portal must provide more than simple access to data. It must provide the search, navigation, analytical, and communication tools necessary for members of the institutions community to do their work in a collaborative manner. Santa Barbara City Colleges Project Redesign and Portal Development For the past six years, Santa Barbara City College has undertaken a systematic and wide-ranging assessment of institutional effectiveness and reengineering of college business practices in its Project Redesign initiative (Rudy, 1996). The college has approached the development of its college Intranet from the perspective of implementing many of the recommendations of the Portals are the first killer applications of knowledge management due to their versatility, broad technical and functional capabilities, and ease of use. Well-designed portals allow institutions to create and implement the knowledge management strategy of their choice. This chapter presents the elements, components, and processes involved in setting and maintaining portals. It uses Santa Barbara City College as a case study of a portal implementation with the purpose of supporting knowledge management, and it underscores the role played and benefits gained by institutional research and the college as a result. 38 KNOWLEDGE MANAGEMENT redesign teams. Recent developments in portal technologies and tools have allowed the institution to design and develop Intranet applications to meet the objectives of Project Redesign and provide a framework for knowledge management within the institution. The institutions key goals for its Intranet portal include the following: Improve access to college information Improve understanding and use of college information Improve institutional decision making Improve collaboration and communication among college departments The college has identified a number of key components that must be in place within its knowledge management framework for the institution to achieve these goals. Of primary importance is the development of a decision support system to support and enhance the operational, evaluation, research, and planning functions within the institution. A second key area is document management. All college policies, procedures, reports, meeting agendas and minutes, and key college publications will be included within the knowledge management portal. Electronic forms and workflow capabilities are essential to support the improvement and automation of Santa Barbara City College business processes. More effective mechanisms for Web content development and administration are also important components of the knowledge management project. Expanded use of college e-mail alerts and notifications, as well as structures for increasing college communications, are objectives of the project. Finally, database security and management provide the technical infrastructure to implement a robust and secure knowledge management system. The college Intranet portal project is a joint initiative of the information resources division and the office of institutional assessment, research, and planning. The development of decision support information is at the heart of this project. As such, the role of the office of institutional assessment, research, and planning is critical to the success of the portal project. The college cabinet and college planning council provide overall project leadership and direction. Key decisions must be made regarding information architecture, analytical tools, and access security. The information systems development team and the office of institutional assessment, research, and planning should make these decisions jointly. Lack of cooperation, planning, and skills development between these entities will place such projects at risk. Institutional researchers must become core members of the institutions Web development team during the design, development, and deployment of a campus Intranet portal. What Is a Portal? As we all know the Internet has become an integrated component of our work and personal lives. The number of Web hosts has grown from 1.3 million in 1993 to over a hundred million at the beginning of 2001 (Internet BUILDING PORTALS FOR HIGHER EDUCATION 39 Software Consortium, Internet Domain Survey, 2001). These hosts generate approximately one billion URLs (Universal Resource Locators). Gartner Group estimates that by 2003 more than 90 percent of government entities will deploy one or more portals to serve their constituencies (Di Maio, 2001). As discussed in Chapter One, we are being inundated with a growing amount of information, a situation that creates a strong need to find a method of organizing the information that is pertinent for our interests and responsibilities. Portals provide such organization. Ryland (2000) points out the importance of effective knowledge navigation, and finds us at the very early stages of understanding how to manage and navigate through the huge volumes of information and knowledge being made available through the World Wide Web on the Internet. Web portals are one of the most popular topics of discussion in technology today. With so much written on portals one would assume that a common definition would be available. Frequently we find that these defi- nitions do not synchronize with each other. Some people see this as a problem; we see this as an opportunity. In fact, that is the beauty of a portal, each person can have his or her own definition. A definition of a basic portal is rather simple: a gateway to network-accessible resources (Intranet, Extranet, and Internet). A simple Web page could fit this definition, as could a complex site composed of thousands of Web pages. Some of the early portals were quite simple, offering their visitors a static view of content from a small number of sources. As our user communities have become aware of the Internet, their expectation of a usable and acceptable Web portal has risen. No longer are people satisfied to use a generic portal that is designed to meet the lowest common denominator of all of the target audiences. Today there is an increased need for personal portals. A personal portal is one that is personalized and potentially customizable for a particular individual. These portals should be dynamic, providing each individual user with their own view of the information resources that is current. Commercial examples of portals include my.oracle.com, my.yahoo.com, excite.com, and many others. Individual organizations are increasingly building their own corporate portals for both Internet and Intranet use. This chapter provides information on how colleges and universities can build and benefit from these portals and more specifically how they can assist institutional research efforts. Why Are Portals Useful? There is one major reason for portals, efficiency. Portals help make more efficient use of an individuals time, one of the most important organizational resources. With the ever-increasing glut of data, it is essential to provide an organizations constituencies with focused information that can facilitate better decision making. Moore (2001) points out the importance of integration of applications, rather than a simple collection of content, 40 KNOWLEDGE MANAGEMENT within the portal. A portal will never provide a person with all of their informational needs. An organization can create a gateway, however, that should provide a significant amount of core information. Again, personalization of portal content is an important element in making the campus Intranet useful to a broad set of constituents. Borck (2001) points out the emerging importance of context personalization for personalized portal applications, based on factors such as a users current task, time of day, accessing device, bandwidth, and location. Importance to Institutional Research A great deal of organizational information is stored, in various forms, in the data that are collected through the daily operations of a college or university. In some cases it is important to provide immediate access to the data in order to make short-term decisions, in other cases information is aggregated, verified, and summarized to provide a longer-term perspective. One of the challenges for offices of institutional research is the development of methods to deliver this information to those individuals and offices that can benefit most. Frequently this information is filed away or published in formats that are not conducive to frequent, broad, and immediate dissemination. A Web portal can increase the distribution of this information dramatically and can do so in a secure manner. Using a personalized and focused design, information that previously was difficult to access can be published in a Business Intelligence Portal (BIP). Frequently, Web sites are designed to provide only a static view of information; an effective institutional portal can integrate dynamic query and display of data, thereby greatly increasing the utilization of critical knowledge for institutional decision making. Portal Architecture A Web site, or portal, consists of several hardware and software components that perform the functions of servicing the users requests and assembling the necessary information for delivery through a Web browser. Many of these components share the term server, whether they consist of computer software or hardware. The software components can reside either on separate hardware servers or be colocated on a single device. The hardware architecture decision is usually determined based upon the projected demands on the Web site. A well-designed Web site should be able to accommodate growth and provide for flexibility in hardware configuration as the needs of the organization change. Typically a Web site consists of the following software components: Web server File system or database Application server BUILDING PORTALS FOR HIGHER EDUCATION 41 Figure 3.1 provides a high-level overview of the portal architecture. The Web server provides the initial connection link between the users Web browser (Netscape Communicator, Microsoft Internet Explorer) and the Web pages using the Hypertext Transfer Protocol (HTTP) or the secure version of HTTPHTTPS. When the Web server receives the request for a page, it determines the appropriate service to provide that information. If the requested page contains static information, such as text or graphics, the information may simply be retrieved from the servers file system. In many cases, the information will reside in multiple locations, requiring the Web server to send additional requests to the remote content providers. After the information is collected, the Web server will send the completed information back to the requesting user. Database ServerFile System Application Server Web Server Direct request for data Requested data returned Execute Program(Java, CGI Bin, Perl) Requested data returned Data request from program Requested data returned to program Generated Web page and components (HTML, Java, Javascript, etc.) HTTP/HTTPS Request Figure 3.1. Portal Architecture 42 KNOWLEDGE MANAGEMENT Frequently Web pages contain additional functionality such as searching, calculations, and other actions. The application server (which can be an integral component of the Web server) provides these functions with the capability to execute these requests. The applications could be designed in Java, C, Perl, or a variety of other languages. The application server also can manage the authentication and authorization functions for those sites that require secure access. Web sites increasingly store only a limited portion of their information as static pages. The majority of portal Web pages are dynamicthe pages do not exist until a user requests them. These dynamic pages are composed of various components that may exist at different locations, both internal and external to an organization. The components are assembled based upon the specific request and then delivered via the Web server to the users. In conjunction with a single user sign-on and interface, this architecture allows the personalization of content through the collection and presentation of multiple portal components: applications, services, tools, and data. Santa Barbara City College Portal Functionality and Framework The institution must have a well-defined portal architecture and toolset before successful planning and implementation can begin. Santa Barbara City College has identified four major components of our portal strategy: decision support and data warehousing, document management, Web site management, and content communications. Figure 3.2 provides an overview of Santa Barbara City Colleges portal components and architecture. This section describes these components in detail and discusses the specific technologies that Santa Barbara City College is using to implement portal technology in relation to its knowledge management initiative. Key software tools within Santa Barbara City Colleges portal implementation include WebCT for courseware development and delivery, Campus Pipeline for student Web access, iPlanet for messaging and calendar services, Oracle Portal for Intranet development, and Oracle Database and Applications for electronic forms and workflow. The selection of specific vendor tools must be undertaken with an eye toward the integration of multiple tools into an overall campus architecture. For Santa Barbara City College, the recent integration of WebCT and Campus Pipeline into a single sign-on, session management, and course framework was a significant step forward in providing a user-friendly and intuitive framework for our students. In building their campus portals, institutions have used different vendors and tools successfully. Chapter Six provides additional information regarding some of the available options. Santa Barbara City Colleges selection of portal toolsets has been conditioned largely by the selection by faculty of the WebCT product for instructional courseware development and delivery and on the selection of Oracle Applications for campus administrative systems. BUILDING PORTALS FOR HIGHER EDUCATION 43 Decision Support A key goal of any knowledge management implementation must be to structure information to assist in college decision making. While executive information systems have been components of many campus administrative information systems, the advent of portal technology offers several new capabilities. By far the most important of these is the ability to personalize the content of the decision support system based on user responsibilities and individual preferences. At Santa Barbara City College, the initial focus of decision support activities has been to support academic program review, college planning and resource rankings, institutional effectiveness assessment, and accreditation. Roueche, Ely, and Roueche (2001) point out the importance of such Decision Support Data Warehouse Components Standard Reports Ad Hoc Queries Analytical Tools Examples Grade Distribution Faculty Workload FTES Report Course Enrollments Document Management Components Search Engine Web Viewer Format Translation Folder Technology Content Repository Context Engine Document Check Out Version Control Examples Policies & Procedures Agendas & Minutes Newsletters Web Site Management Components Page Templates Navigation Bars Object Library Web Page Wizards Examples Departmental Pages Content Communications Components E-Mail Electronic Forms Workflow Threaded Discussions Chat Examples On-line Courses Supplemental Resources SBCC Portal A Personalized Collection of Meaningful Content, Services, and Tools Staff Faculty Student Alumni Community Database Repository Security & Authorization Personalization Figure 3.2. Santa Barbara City College Portal Framework 44 KNOWLEDGE MANAGEMENT institutional assessment in describing the Community College of Denvers pursuit of excellence. Common measures of institutional effectiveness are used for many of these purposes. Measures of successful course completions, faculty load, and productivity are used on an institutional basis in its annual assessment of institutional effectiveness. The academic senate and college planning council use these same measures at the departmental level to make decisions concerning the ranking of new faculty positions. Division deans and department chairs use these same measures during the evaluation of individual faculty members. Effective use of information to support these multiple purposes requires several capabilities. Access to data must be controlled by the role or responsibilities of individuals within the organization. Specifically, institutional policy decisions concerning access to departmental and individual faculty data must be supported by the database application. In addition, it must be easy for users to navigate through the various levels of organizational hierarchies through drill down and roll up capabilities. Flexibility also must be provided in the availability of analytical tools to support the personalization of the decision support system, as individuals use and analyze data in many different ways. The decision support function of the institutional knowledge management system is a primary responsibility of the office of institutional assessment, research, and planning at Santa Barbara City College. This responsibility includes guiding the institutional discussions of appropriate measures to be used, designing data warehouse structures, developing standard reports and query templates, as well as training college faculty and management to use the tools and information effectively in support of their respective roles. It was a very deliberate decision by the college to place these functions within this office. There were several reasons for this decision. First, the college needed a central department to coordinate the design and development of the institutions decision support systems. The institutional research function has a collegewide perspective of information structures, reporting, and use. Second, the institutional research function has the technical expertise to use data management and analytical tools effectively. Finally, and perhaps most important, the office is charged with defining the implications for college practice from all research studies and data analyses conducted on campus. Research and analysis are of very limited use to the institution unless they are constantly applied to determine how the institution can improve the quality and responsiveness of its operations and services. At Santa Barbara City College, this pivotal role is assigned to the office of institutional assessment, research, and planning. This responsibility places very broad demands on this office: database design, data analysis, policy development, and technology planning and implementation. Some offices of institutional research may be reluctant to undertake these broadened areas of responsibilities. This expanded role for the institutional BUILDING PORTALS FOR HIGHER EDUCATION 45 research function is, however, a natural outcome of increased institutional focus on data driven decision making and accountability. These added responsibilities also place additional demands on the ability of the institutional research office to recruit, train, and retain staff conversant in research methodologies, analytical tools, Web development, databases, and higher education policy. Document Management College policies, procedures, and operational processes must be stored and retrieved easily. This requirement poses many organizational and technical challenges for the designers of institutional knowledge management systems. Support for document management is an essential component of knowledge management. The use of structured, hierarchical document storage taxonomies versus unstructured search capabilities is a key design decision for institutions. Santa Barbara City College chose to emphasize the latter approach due to reduced maintenance costs and increased flexibility for information access. For this approach to be successful, however, the search engine must be able to conduct full-text searches of archived documents, rather than relying on key words, abstracts, or titles. While these capabilities are now part of all desktop operating systems, the extension to all campus policies, procedures, and official documents requires a very robust and efficient search mechanism to deal with the hundreds of institutional documents contained on the college Intranet (or in the college Intranet environment). Establishing standards for document storage and viewing formats also presents challenges for institutions. Santa Barbara City College made the decision to provide browser-based access to all documents contained in the knowledge management database or repository. Early on, this meant conversion of documents to HTML and centralized posting of documents by our Web development department. With the implementation of the Oracle Portal product technology, the process for storage and retrieval of documents has been much improved. Files are stored in the database in their native formats (Word, Excel, PDF [portable document format], HTML [hypertext mark-up language], and so forth) but are viewed through a Web browser without required plug-ins due to on the fly translation of these file formats to HTML. This capability saves much time in file creation and maintenance within the college Intranet system. These stored documents also can be accessed directly by users from the database in their native formats. Understanding the context of key word search results is another design component of document management. This component includes having an efficient weighting system for prioritizing search results. Along with the weighting algorithm, the Oracle Portal, using the integrated Oracle Text capability, develops themes and gists for each document stored in the document management repository. The thematic analysis is based upon an 46 KNOWLEDGE MANAGEMENT extensible thesaurus. The listing of themes outlines the central concepts presented in each document so that one can navigate quickly to the desired area. Gists present summary statements in narrative form of the key themes within each document. These capabilities assist users in understanding the context and content of documents contained within the knowledge management database, and are made possible through the use of a linguistics engine that is part of the Oracle Portal environment. Document versioning, end-dating, archiving, access control, and security are also important elements of document management capabilities that are a product of using a database for storage of documents within a knowledge management system. These document management capabilities allow for rapid and efficient navigation of the institutions policies, procedures, and publications. A student or faculty member with questions concerning campus policies on grading can simply enter grading into the search engine and rapidly retrieve all Intranet documents containing the term. The individual can then navigate quickly internally within the documents to find specific highlighted references to grading. Themes from these documents, such as academic probation or grade point average, are also referenced to provide users with more refined choices for viewing. Campus directory information is another good example of the deployment to this technology. An on-line directory provides up-to-the-minute listings of college personnel and directory information that can be accessed easily by first name, last name, building, department, or other directory attributes. Prior to the development of the college Intranet, these document management features were nonexistent at Santa Barbara City College. The function of storage and retention of documents was highly decentralized, with many differing departmental policies, tools, and practices. College standardization of these elements within the Intranet project has led to a far more comprehensive, useful, and powerful repository of campus electronic documents. This framework is an ideal way for offices of institutional research to make their publications available to their campus community. Adding research reports and publications to the document repository is easy to do. Once in the repository, for example, a study on the effectiveness of on-line instruction will be returned in the search results on queries for grading, retention, technology, and many other terms. This leads to greater dissemination and use of institutional research reports. Web Content Development and Management Web site content creation and management present a specialized case of document management functionality. Decentralization of Web content development and posting was a key objective for Santa Barbara City Colleges knowledge management Intranet application. The college had experienced great difficulty in training and support in HTML and FTP (file transfer protocol) for departmental Web developers. In addition, the BUILDING PORTALS FOR HIGHER EDUCATION 47 enforcement of design and navigation standards within departmental development proved problematic. These problems required that all Web content be routed to the Web development group to provide quality assurance and final posting to the college Web site. This process simply was not sustainable for the development and maintenance of the colleges knowledge management Web site. The Oracle Portal technology provides end-user tools for the construction and maintenance of Web pages through a Web browser interface. Since these elements are stored directly into the portal database, there is no need for separate file transfer processes. The use of any such tool necessarily constrains page structure and functionality to some extent. For Santa Barbara City College, however, the significant gains in departmental Web development productivity have been well worth such constraints. Dynamic Web page deployment is a key to the personalization of knowledge management systems. This requires that the individuals view of a Web page be built on the fly according to specific user roles, preferences, and access to information. Harris and Caldwell (2000) point out the need for compelling technology to support effective knowledge management systems. This move away from static, uniform HTML pages places significantly increased reliance and importance on the database capabilities of the institution. Individual user responsibilities, security, and preferences must be maintained in data structures that can support the rapid collection, assembly, and deployment of individual Web pages. This component-based approach to Web site construction allows for the re-use of templates, graphics, documents, and applications throughout the Web site. Decentralization of Santa Barbara City College Web site content development and management is a major objective for our Intranet portal project. Our previous model for Web site maintenance had departmental Web page developers preparing content and then transferring that content to a holding area for review and posting by the colleges Web development team (consisting of one Web master and one Web developer). This centralized approach provided quality assurance and standards review of pages before posting, but at great cost in terms of productivity of our Web development staff. In the new model, departmental content developers are given the ability to construct pages based on approved templates and using a central library of Web objects. Review of a Web page before posting has shifted from the Web development group to the departmental manager, who focuses on the accuracy and completeness of the page content. This direction is intended to provide more time for limited Web development resources to work on more technical issues, such as systems integration and security. These Web content capabilities allow the office of institutional assessment, research, and planning to design, develop, and maintain a Web-based content area for research studies, reports, ad hoc queries, and analytical tools. The look and feel of the institutional research site can be customized within the institutions standard departmental page templates and tools. The 48 KNOWLEDGE MANAGEMENT use of development wizards allows institutional researchers to develop Web-based delivery without requiring them to become experts in HTML, XML, or Java. This self-sufficiency for the offices of institutional research is a real benefit to those departments constantly trying to battle for information resource support with other college operating units. Again, the institutional research office must be viewed as an integral part of the colleges Web development team if campus objectives on improved decision making are to be realized. Content Communications Knowledge Management systems present opportunities for the automation of college forms and workflow to restructure institutional business processes. While most institutions have deployed Web technology to present electronic forms to the college community, far fewer have undertaken a systematic and rigorous management of their business processes with automated workflow engines. There are several reasons for this relatively slow adoption of workflow technology. First, institutions must invest the time and resources to document existing business processes in a consistent structure and methodology. This is a time-consuming and labor-intensive process. Santa Barbara City College spent three years using more than thirty project teams to document key business processes targeted for redesign through business process reengineering. The college experienced great dif- ficulty in freeing key staff members to participate in these redesign sessions. A second roadblock to workflow automation has been the relative immaturity of the technology itself. Workflow tools have begun to deepen in product capabilities and simplify in terms of ease of use. Investment in workflow technology at the current time, however, means training of technology staff in the sometimes arcane use of workflow tools. The industry is still a long way away from providing simple end-user tools for automating and managing college workflow processes. A final reason for the slow adoption of workflow technology is the continuing maintenance and support needed to keep these systems current with changes in institutional process over time. Once the systems have been developed via workflow technology, revisions to college processes must be re-implemented by using the workflow engine. Given these limitations, why would higher education institutions adopt processing strategies of electronic forms and automated workflow? The reasons are many. Most important, these technologies allow for the potential for saving much time and effort in the conduct of institutional business processes. Forms implemented in knowledge management systems can be routed simultaneously to multiple individuals for review and approval. In addition, college business rules for edit checks and calculations and institutional rules for routing and approval of documents can be enforced systematically without relying on the knowledge of the initiator on how to process the document. Capturing and storing process workflows and business rules also insulate the institution from the loss of key personnel who maintain the knowledge of proper procedures in their heads. As discussed in Chapter One, far too often we bemoan the loss of key college staff and the institutional knowledge and history they take with them. The discipline and rigor associated with mapping institutional business processes and workflows also provide a wonderful opportunity for reexamining current business practices and procedures. The implementation of portal technology is key to the successful implementation of a streamlined workflow process. Hayward (2000) notes the importance of conceiving of knowledge management as not the implementation of a technology; rather, it is a multidiscipline approach that integrates business strategy, cultural values, and work processes. The individuals portal page becomes the central point of collection of tasks and activities from many different systems. A faculty member, for example, can receive class lists and rosters, initiate student drops, submit grades, initiate requisitions, conduct campus library searches, and analyze departmental performance data all from the same portal framework. Although the systems integration work of a portal implementation is a major undertaking, the rewards are substantial for end users in terms of ease of use. Collaboration tools such as e-mail, discussion groups, chat, Web conferencing, workflow, alerts, and document sharing are essential components of the portal framework. These tools provide synchronous and asynchronous methods of communication and resource sharing among individuals and various constituencies of the college community. Integration of these various tools within the portal framework can be very challenging from a technical perspective, but is essential to realizing the time and resource saving potential of the institutional portal. Identification of Communities A first step in the definition of a campus portal is the identification of communities of interest to be served by the portal. What are the groups on campus that need to communicate and to have access to similar kinds of information? Once these communities are defined, the institution can begin planning the specific set of documents, information, forms, and services to be made available to each group. At Santa Barbara City College we have used the college Web committee to define these communities of interest, and then have used the college cabinet for the review and approval of these portal communities and services. Toolset Evaluation As discussed in Chapter Six, there are many portal providers and toolsets available to institutions of higher education, and many different approaches can be taken. Individual decisions by institutions are conditioned by many factors, including the following: current technology environment, technical expertise available at the institution, level of staffing for development BUILDING PORTALS FOR HIGHER EDUCATION 49 and support, and project funding to name a few. At Santa Barbara City College, for example, our choice of Campus Pipeline as a student portal framework was influenced significantly by its partnership with WebCT to integrate the instructional content development and delivery mechanisms of WebCT into the portal framework of Campus Pipeline under a single sign-on and authentication process. As we had committed previously to WebCT as our institutional toolset for instructional content management, portal vendor integration with WebCT loomed large in our decision process. Likewise, our selection of Oracles Portal product for college Intranet development was influenced by our preexisting campus licensing agreement for Oracle database and applications development products (Portal is an integral component of Oracles Internet Application Server product) and our use of Oracle applications for the colleges administrative systems. Regardless of the unique institutional circumstances, there are some important considerations that are common across institutions in terms of portal toolset selection. The Gartner Group has identified five criteria for institutional evaluation of portal framework products: robust search across all structured and unstructured repositories, taxonomy support, content management and aggregation, personalization, and application integration and development (Phifer and Zastrocky, 2000). Data Warehouse Design The development of an effective decision support system for the college is a primary objective of Santa Barbara City Colleges portal project. Previous institutional efforts in this area have not been successful due to several factors. First, development and maintenance resources have been limited to grant funding and were not sustainable by ongoing staff due to other systems development and maintenance tasks. Second, the use and navigation of client-based analytical tools were viewed as too cumbersome by campus managers. Third, and perhaps most important, managers lacked the time necessary to do detailed analysis of data provided in the data warehouse. These lessons learned by Santa Barbara City College in previous projects helped provide design objectives for the decision support functionality within the campus Intranet portal project. Key measures need to be identified for each person or role using the portal. These measures will facilitate the personalization of the portal. The elements and level of detail that are needed by the president are significantly different from those of the vice presidents, deans, and department chairs. We need to create a customized executive dashboard for each of these roles within the institution. This dashboard needs to reflect information that is current and relevant to the decisions being made in each role. During registration, for example, department chairs and deans are monitoring course enrollments in order to make decisions on adding or canceling course sections. Both of these roles need to be able to view enrollment datadepartment 50 KNOWLEDGE MANAGEMENT chairs for their specific department and deans for all departments within their area. Easy access to this structured set of data is important for timely and effective decision making during registration. While many other individuals within the institution are interested in such course enrollment data and should be able to query such information, it would not appear on their dashboard for action. Individual faculty members, for example, may want to save a query of course enrollments in their classes as an object on their portal page. Such personalized extension of the portal page is an important element of the success and usefulness of the portal application. As noted previously, the focus of Santa Barbara City Colleges data warehousing strategy is to support institutional assessment, planning, resource allocation, and departmental program review activities. By design, there are many common measures that are used across these areas. Student course completion rates, grade distributions, faculty workload and productivity, full-time equivalent students, and full-time to part-time faculty ratios are examples of measures that serve many planning and evaluation purposes. Careful attention must be paid to the levels of aggregation, related variables, and security of these data in the data warehouse design. At Santa Barbara City College, the director of institutional assessment, research, and planning has the responsibility for the design and development of the data warehouse model, with assistance as needed from the information resources division in terms of data development and transformation. The college cabinet members work directly with the office of institutional assessment, research, and planning in defining the key measures of effectiveness to be used in their areas of responsibility. Security Design Access to specific pages, content, data elements, and levels of detail ideally is controlled by security measures within the portal database of users, responsibilities, and items. An individual user may have multiple responsibilities. Design considerations must be made to determine whether all elements of the multiple responsibilities will be displayed on the individual portal page, distributed to multiple pages based on responsibilities, or controlled by forcing a single responsibility to be selected at any one time. Another key element of portal security is the development of a single signon and authentication mechanism. Much of the ease of use within a portal framework disappears if users are required to log in to multiple applications within the portal. Security planning also must consider what access will be provided to users exclusively within the campus Intranet environment and what elements will be made available to portal users through Internet access. Although the goal for Santa Barbara City College is clearly anytime, anywhere access to campus information, product licensing and campus network security may often dictate limitation to access only while on campus. BUILDING PORTALS FOR HIGHER EDUCATION 51 Availability and Support Another key planning dimension is to assess the need for ongoing support and sustainability of the portal environment. This operational planning has several components. First, support and maintenance of portal hardware and software must be considered. Any components of the portal framework that are made available over the Internet must be supported on a 7 by 24 by 365 basis. There is no excused downtime, no set hours of operation, and no patience for system failures. At Santa Barbara City College, this lesson was learned quickly as we developed our Online College offerings. In the first year of operation of the Online College, with a very limited number of courses offered, the off-hour demands on our Web master and user support staff were tremendous. During the second year of operation, the Online College contracted with a local Internet service provider for hardware, operating system, and help-desk support for the seventy courses offered. In the third year of operation, we contracted with Sprint Corporations Web Hosting Services to add the Campus Pipeline student portal server to the WebCT server hosting the Online College course content for more than a hundred courses. This year the college is adding an iPlanet messaging and calendaring server to the student portal, and also adding firewall security at the hosted site to serve in conjunction with the existing campus firewall. This portal framework will serve more than 130 course offerings and five thousand students. Whereas Sprint is providing around-the-clock support for the hardware, operating system, and network connectivity, the database and application level support are still the responsibility of, and managed by, the college. Training No portal implementation can achieve success without proper training of the college community on the structure, navigation, tools, content, and uses of the Intranet site. At Santa Barbara City College this training component includes presentations by the office of institutional assessment, research, and planning, the faculty resource center, the staff resource center, and the information resources division. The role of the office of institutional assessment, research, and planning is essential, in that it provides campus training on data structures, ad hoc query capabilities, analytical tools, and reporting. We have found that the most successful training is tied directly to the job requirements of the individual or group to be trained. Generic vendor training on a particular analysis tool, for example, is rarely sustainable when individuals return to their desks, because there is no structure for the immediate use and reinforcement of the training in a real-life situation. Our training modules have had far more success when designed around a departmental-specific analysis or task to be accomplished. 52 KNOWLEDGE MANAGEMENT Project Staffing The design, development, and implementation of a campus Intranet portal are significant undertakings for any institution. Both the time and resources that need to be committed to the project are precious commodities within higher education institutions. The challenges are particularly acute for community colleges and smaller four-year institutions that often lack the technology infrastructure and support mechanisms required for large-scale technology deployments. As in most human endeavors, however, good people working together in a focused way can accomplish much. At Santa Barbara City College the Intranet development team consisted of the following roles: project manager (one), institutional researcher (one), Web developer (one), database administrator (one), functional specialists (six), and trainers (two). This core development team worked to develop the initial prototype of the college Intranet portal presented to the college cabinet and management team. The group then began to fill in content for the production version of the portal. We brought in additional Web content developers from departmental staff as each new area was added to the production version of the portal. Just-in-time training was provided to the content developers in order for them to be ready to maintain content on an ongoing basis. The office of institutional assessment, research, and planning provided training to academic deans in decision-support tools and data. The working group developed the initial prototype in a month, whereas the additional specification of the production portal was a three-month project. We are now in a year-long project to complete the campus Intranet portal content and to move the service into ongoing maintenance and support. Campus Portal Planning and Implementation When beginning the implementation of a portal one of the most important considerations is to understand that the institution must have a long-term commitment to the project. A portal, by its dynamic nature, is never finished. As technology and the needs of the organization and individuals change, the portal must morph to meet the new demands. A portal that does not have this flexibility (and dedication to ongoing support and maintenance) is doomed. Like any major technology project, a significant institutional investment in planning and design of the institutions portal is an important first step toward a successful implementation. Conclusion There are a few points from the chapter that deserve to be reinforced in conclusion. First, the development of systems, content, and processes for personalized content delivery is essential for a successful implementation of an BUILDING PORTALS FOR HIGHER EDUCATION 53 institutional portal. This objective should drive decisions concerning design, content, format, and tools to be used within the portal framework. The portal must be relevant and rewarding to individuals in their respective roles within the organization. Second, decentralization of Web content development and maintenance is a key objective for ongoing sustainability and support of an institutional portal. This is especially important for community colleges and smaller four-year institutions, and can be achieved through the development and training of departmental staff on institutional templates and resource libraries, stored in a central database repository. A formal training program for departmental Web developers is also a key success factor in this area. Third, the use of robust search engines provides a far more effective vehicle for document retrieval and management that relying on the navigation of hierarchical file folders or organizational taxonomies. Rapid full-text search and weighting of all documents (regardless of type) provide the most sustainable, flexible, and useful retrieval capabilities. Finally, in a publication targeted to institutional researchers, a chapter written by institutional chief technology officers may be suspect. We would like to reiterate, however, our vision of the central role played by institutional research within the development of higher education portals. At Santa Barbara City College, the office of institutional assessment, research, and planning is driving the design and development of the institutional portal to implement a new decision-support system. We have pointed out the significantly expanded role this has meant for the institutional research function within the college in terms of database design, policy development, Web content development, training, and technology infrastructure planning. This expansion of responsibilities may be viewed skeptically by some in the profession but is a rather natural outcome of placing improved institutional decision making at the heart of higher education Intranet portal strategies. References Borck, J. R. Next-Generation Portals, 2001. [http://iwsun4.infoworld.com/articles/op/xml/01 /06/11/010611opborck.xml]. Di Maio, A. Why Todays Government Portals Are Irrelevant. Stamford, Conn.: Gartner Group, January 2001. Harris, K., and Caldwell, F. Knowledge Management Scenario: The Enterprise and Beyond. Paper presented at the Gartner Symposium ITXPO, Orlando, Fla., October 1116, 2000. Hayward, S. Choosing Wisely: Technology for Knowledge Management. Paper presented at the Gartner Symposium ITXPO, Orlando, Fla., October 1116, 2000. Internet Software Consortium. Internet Domain Survey, January 2001. [http://www.isc.org /ds/WWW-200101/index.html]. Moore, C. Portal Power, 2001. [http://iwsun4.infoworld.com/articles/fe/xml/01/06/11 /010611feknowledge.xml]. Phifer, G., and Zastrocky, M. Best Practices in Deploying Institution-Wide Portals. Stamford, Conn.: Gartner Group, August 2, 2000. 54 KNOWLEDGE MANAGEMENT Roueche, J. E., Ely, E. E., and Roueche, S. D. Challenges of the Heart: Pursuing Excellence at the Community College of Denver. Community College Journal, Dec.Jan. 2001, pp. 3034. Rudy, J. Campus Profile: Santa Barbara City College. CAUSE/EFFECT, Winter 1996, 19(4), 3235. Ryland, J. N. Technology and the Future of the Community College. New Expeditions, Issues Paper No. 10. Washington, D.C.: American Association of Community Colleges, 2000. Yanosky, R. Higher Education Enterprise Portals: Profiles of an Emerging Provider Class. Stamford, Conn.: Gartner Group, March 3, 2000. RICHARD PICKETT is executive director of technical marketing at Oracle Corporation. WILLIAM HAMRE is vice president of the information resource division at Santa Barbara City College. BUILDING PORTALS FOR HIGHER EDUCATION 55  See attached Microsoft Case Study Gonzaga University Implements Content Management Server  Go to  HYPERLINK "http://www.gonzaga.edu/default.htm" http://www.gonzaga.edu/default.htm  Go to  HYPERLINK "https://gwired.gwu.edu/adm/apply/app_online.html" https://gwired.gwu.edu/adm/apply/app_online.html. Scroll to bottom left of page.  Software must be reviewed annually to maintain currency and aptness.  Go to George Washington University  HYPERLINK "http://www.gwu.edu/" http://www.gwu.edu/  See attached article Building Portals for Higher Education. .       Microsoft Content Management Server Customer Solution Solution Overview Customer Profile Gonzaga University is a private, four-year comprehensive university. Founded in 1887, Gonzaga enrolls about 5,300 students in 92 undergraduate and 22 graduate programs. Business Situation Gonzagas Web site ( HYPERLINK "http://www.gonzaga.edu" www.gonzaga.edu) was a complex mix of Web pages with no solid structure and an inefficient method of posting or updating content. The university needed a simple and cost-effective solution that would transfer the content creation role to faculty members and department heads, while making the visual design of the Web site consistent. Solution Gonzaga implemented a Microsoft Content Management Server solution and completely redesigned and restructured its Web site in six months. Benefits Easy-to-manage Web site Broadly distributed content management Increased visibility to the outside world Completely redesigned Web site without adding additional staff Newly created Web site with a consistent look and message Software and Services Microsoft Windows 2000 Server with Internet Information Services 5.0 Microsoft SQL ServerTM 7.0 and SQL Server 2000 Microsoft Content Management Server 2001 Microsoft Internet Explorer 6 Partners Aurora Consulting Group, Inc. With Microsoft Content Management Server, we were able to turn Gonzagas Web site into a rich, dynamic information center that provides an excellent resource for students, faculty, and the community. Beth Britt Chief Executive Officer (CEO) and President Aurora Consulting Group, Inc. Using Content Management Server, weve accomplished a complete redesign and restructure of our Web site, and I didnt have to hire new staff or increase my budget to manage the site. The value that Content Management Server provides Gonzaga will become strikingly apparent over time. Chris Gill Director of Desktop Support Services Gonzaga University The .NET Enterprise Servers are Microsofts comprehensive family of server applications for building, deploying, and managing next-generation, integrated applications and Web experiences. Designed with mission-critical performance in mind, the .NET Enterprise Servers provide fast time-to-market as well as scalability, reliability, and manageability for the global, Web-enabled enterprise. They have been built from the ground up for interoperability using open Web standards such as Extensible Markup Language (XML). The .NET Enterprise Servers enable a distributed computing model for the Internet, based on Internet protocols and standards in order to revolutionize the way computers talk to one another. For more information about Microsoft Content Management Server, go to:  HYPERLINK "http://www.microsoft.com/cmserver/" http://www.microsoft.com/cmserver/. $*?@A7  S   ?Iێێtl^SSSh8dhq>3CJaJjhg0JCJUaJhgCJaJh8dhmCJaJhwh}hB*CJaJphh8dh|CJaJhwB*CJaJphh4_=h4_=B*CJaJphh4_=B*CJaJphh4_=CJaJhjCJaJh8dhjCJaJh8dh}hCJaJh}hhjh(5 h75hjh}h5 @Ano6 7 p q  7 ] : e 7$8$H$gd4_=4z   T U  4567878 7$8$H$gdG 7$8$H$gdw 7$8$H$gd4_=cqy13&2358Źť~vnvnvfnfnfnfnvfhCJaJhwCJaJh4_=CJaJ!jh8dh70JCJUaJh8dh8dCJaJh8dh;CJaJh8dhjCJaJhw5CJaJh8dh75CJaJh8dhm5CJaJ!jh8dhj0JCJUaJhgCJaJh8dhq>3CJaJh8dh|CJaJ&>Mjpr ,}~678'(⮣tlttd\h8dCJaJh;CJaJh4_=CJaJh8dhjCJaJhHnCJaJ!jh8dh70JCJUaJh8dh7CJaJh8dhmCJaJh8dh;CJaJjhXcu0JCJUaJhCJaJh8dh4_=CJaJhA8CJaJh8dh8dCJaJh8dhCJaJhCJaJ$(ALQwy15lo!!$!%!#¬zzzzzzzztgtgthgihCJ ^JaJ h^J hhjhB*UphhhB*CJphj *hB*CJUph+jhB*CJU_HmHnHphujhCJU hCJ hCJhgCJaJhCJaJhCJaJhHnCJaJh8dCJaJ&82 Y%@(I( *5+K,g,--011345~789gdcgdcgdc  Jgdc J gdc##Y%Z%I(()) *5+---1145999<T<U<i<?CFFF!FHHqIrIlJmJpJqJJJJĻ񲤟ݘ݊xfxfxf#hB*CJ OJQJ^JaJ ph#hB*CJ OJQJ^JaJ phjhUmHnHu hBh h>*jh>*CJU_Hh1h^Jhveh^J hveh h\^JhXuzhCJ aJ hjhU_HmHnHu h^Jh?jh^J(99<U< ?@ CCFFFFFF F!F"F7FMHHHHqIlJJ 7$8$H$gdG JxgdcgdcJJJJJJJK*PoPQQTTTUT^T_TiT^^__________ɷɂm[I[Iɂ[I[I[I[I#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph)h6B*CJOJQJ]^JaJph#hB*CJOJQJ^JaJph!h6B*OJQJ]^Jph#hB*CJ$OJQJ^JaJ$ph#hB*CJ\OJQJ^JaJ\ph#hB*CJOJQJ^JaJph#hB*CJ OJQJ^JaJ ph#hB*CJ OJQJ^JaJ phJJJKaKKK>LaLLL2MzMMNbNNN;OOO"P*P\PoPP QSQQ 7$8$H$gdGQQ)RpRRR3SvSSSv?vHvyyyzzzzzzz{vششؐ~lWش)h5B*CJOJQJ\^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph)h6B*CJOJQJ]^JaJph"_)`o``aJaaa-bybb c*cucccMddd+etee f+flffgIgg 7$8$H$gdGgg*hXhhh9i}iiiiDjjj$knkkk*llllmImmmm$nsnn 7$8$H$gdGn o[ooo:pppq@qqqrfrrrr?ssstettt0uyuuuu 7$8$H$gdGu v"vKvvvwfwwwFxxx+yxyyyyyy$zϚ"mǛۛ&q 7$8$H$gdG*+12;Ǜۛelpv9۱ܱq"$<L ɷɢɢɷɷɷɷɷɷ)h6B*CJOJQJ]^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph@W2~Ǟa;ʠY5Ģ Z1x 7$8$H$gdGPݥ?զ kGѨhCͪcIh 7$8$H$gdGh?ҭbC9ðK۱Sܲ+u 7$8$H$gdGJ1uNݶ*lMҸc8Ⱥb 7$8$H$gdG-z Z7*{˿]c8} 7$8$H$gdG^4bDdC_: 7$8$H$gdG_9\4~ T7 M!jX 7$8$H$gdG)uPqf%kCb; 7$8$H$gdGZ;`C^iM7v 7$8$H$gdG $t`QJ0y V9<L 7$8$H$gdGL7|X9} X7_< 7$8$H$gdG 7WXabl}Z  %E#H v V a n    ɷɷ۷ɷɷɢɢɢɢɐ{{{{{)h6B*CJOJQJ]^JaJph#hB*CJOJQJ^JaJph)h6B*CJOJQJ]^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph0dAjF>#qS; 7$8$H$gdGTl}\9R6[8~ 7$8$H$gdGZf@gnQ/y[ 7$8$H$gdG@ m   J   % p   J V a   , A    B 7$8$H$gdGNgU u O01234 7$8$H$gdG )] OPWX_#$-01234۴۴۴۴۴۟xtieh}hh8dhCJaJh#hB*CJOJQJ^JaJph)h6B*CJOJQJ]^JaJph)h6B*CJOJQJ]^JaJph)h6B*CJOJQJ]^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph#hB*CJOJQJ^JaJph&456BWXu689:jklnp¾£¾ʆtkʎʎhyph0JjhU hhjhUh7jh70JU h,Hhjhyph,H0Jjh,HU h,Hh,Hh,Hjh,HUhhjjhj0JU h6hh6hmhhgjhg0JU&  !45678NOtvwyz{}~Ӹ۱ۜxtltltltltd`hjhUjh-+ Uh-+ #hB*CJ$OJQJ^JaJ$ph#hB*CJOJQJ^JaJph)hhB*CJOJQJ^JaJph hh7hyph0Jj:hU hhjhUhh7jh70JUhHnhXcujhXcu0JU%7wyz|}3( 7$8$H$gd34\^&()-;@i67F 󲧞zztm h#Lh hCJ hOJQJ^JhUmhCJ ha\AhCJ aJ haJhUmhaJhUmhCJ aJ hUmhh@hCJ aJ hCJ OJQJ^Jh)Ih0JjBhUjhU h5CJ hjhU*34=  ^gdcO EƀZj^gdcgdc! !-]-^<{aO EƀZj^gdcO EƀZj^gdc{Aj}gdcgdcgdcgdc#gdc"#gdcO EƀZj^gdc#678  nh`$$d&dC$NPgdc$$d&dNPU$$d&dC$EƀSf&NPgdcgdcgdc F G w x y          h}hhc h^Jhh#Lh5h5Gh0JjCh5GhU h5Ghjh5GhU       d`21h:p8d/ =!"#$% n^]=r7Y}rWKPNG  IHDRBT2PLTEġNJ9CaDiu^*KU1R]Lu<`lAfr9^i"CM}Hnz#+ezJp} *35YdlT}WZ\ #XPy4>3VagnvqrYtV%FO-NXijۆoFkw09NwS|OxxQz /PZKr'HR?I7[fLsKt/OZ'GQޫ8\h?coiW xd7%tRNS8KgbKGDHq cmPPJCmp0712Hs\'IDATx^ [6 Ȯ# ("l"( "ˆzToo{GVuKUedVfuV_\y$Ȉ̻""##1 3[=ïV_L-(c sxp1 s&~ny\Q9tqhev|ĕˇs 狇gĀiCbnT 7O@mrˍϝONY?E҅Na֍ w`N@Ū<8w}Mӧ m1KgqHA+GcQ7V?CK;RU֓?jZ, X/g/$<,X(uv~}Ņ6wXy泍Ob.9~U˃?EE;<$K FaO=XUP~ ~ϝuB9-8`yMsv Rή{,"l)ٚ/?X)F{w^,R3XGsW)WL_A}mhX1`1`Eejo+X7F5 *"XnhCd|L0<V4XV!CzXDeK֠*?ՖtcQ4HmBŚ)Bb}|ru+ 6"ek #6K *dHbuv3""oUGjob]b(D]6b!ѣ:}bտ44%ìH| Xfj(XgݼM nl=,(*LD<,TY^,'XPNr+Z2X5 <#~q<`Y=l& <yr0iuL5UȐ ƏE.őÑǟ*/  n30lQ'^#@ 뗒t ">QV*dHeiuv"wva0 ^7"VZ#`BhC*"43 T,"B_I2=.++4`ʌB>8VMpM!]0*RRVEtR/ 4”ІבTtQH+ca2:chܻ2v9Šw.ޫxO i}EP(AbeXEŊFe$#< Dd|Fmi2Yα 61 rkXX3iJ0 *A 'Ił wR"0 -I&zH78,P_8X6W DzAbU_ljj ^*Yb=TEHڐRmVԢo"PTb *dHI:ɺ 2@͛M!޴=ssX@,RMdz ^ mEGXEa˾Yxy?7:r`1`g),LCUQhzb%  *X"WrJvwubU,f7K )]9҇";V!C*K7~ 5HU#m{zq1k/kI:zY^wbІT۝R"xT(zg!ΛFNor@BTVggpYteFUu~wXXXHW;2vn'Ƨʕŋͳ&<*btdiM,#!DtiVcÛEEEw!BuGdߙ%"ˌxbYD,}3z`!T?&CĀb;M=^|becq+:X^vt~v1S o* nwF!9bYXd%:kJGX!UG*v#60|42/ xJm/./ZضR9#BXw9 T/+(zԪK鼎a9o?ló,Q=[ RXݟt1fŅkP|F̱#0 ͔>@TG KGFj#ʽurT,+٩Q{QheaaKFY=!h_x. K$skf&mLG 7LڐV%>oX?@T XAHBtu!Lb *<{;ceynSRĪYX:@,xKj&^V5A*lBRZ)_v jzbY <TxeXg7a~?6[ lXhqn;REE:VyBʲ qS8 M5bHgܶslpkxJZ<{¹ ,+Ëe'%!V$*UȐJ!mл;@,<L VMn UV.T#m{sNwIŚuB\xCepB;~,뒉p,T,>F5, cN&+Ul7KԱJFE!RQm@XbQտkK PLAQI=LlH9Gq`* Xҏ"m6m"}!7bYq:c!yd/]^\I:X'X>GIŚ:ֻ|"LBJ*\v׋BK %a K|^8oZ HnXJ'֖~I5 ϻQBcONN.,map,^*_߻STҲ6b]G/7QXH U2 WޔD !ٍ`Ē.PAӟ?g[' F!A0Vd!P*?>t o#<ַ&Xx ; =7eq}mUǑ솾wwD=ީc]PQ0 cpS(^\On,(LC*kU";ϗX Ұ5)EDzݬQhL2Q~K٫2`;FK|cݱ\?4RLF!܌npc͋4V20 ߑr{xQʁha-?m"T?O*9;Ëe~`F,:du;?_nsyXȍ%n SUc29f(m[RWWpع*|0[w/+3ɌMhI&["|48BZޱh=XC*1>Ə"ˉmHUݾF{ H SVJ?@y8Eq"G< 1 X}oΑMH$cS/܊1X 041aO"樍UȐbuv< RJo0 "8 f7iׄfѡTCz"4,%kxL-?;P^a‰EPH/}ݍ"VI/ô<9, ! XqPm;EcXinb=:CŪO@/T- *n ~".!)7i(I2( Ё7Xb2)C)N4 RBnhX#=+ρX@, c@4rQT,,YP n٪xl8M( 6a&42(|m^&`| Y_8k? CeXDl1hX7Quc ŀEBo=ɱmo4k qMHQ7&ɱU&`Q9b| XMtg  ~6D + #6 ]sɆ+a޹s{]ĉxOFcXS^Ѕ:&&&^ Z]_o}xO+o% (‰3mBܴ|շJl  X2sbkKJ%M 0 ܹ\<+hXxo:BGfG )Df,Ӫjy111;=;;r"~mUw ؄8qbեv v7vQhϽ\'$ɴXrD|=NC&db ;б?{P,B։vrcM>pG+8Uz[ Рfg}%kPNKy݄ѪN6!J؄X@t6.Ԇ,[M *dHɵ:I~ˋ+D(|~A1BB,r;ny6$Unϔn2=阘Z[[h* ,`sV7Li5̽DQXGN@22MIw,ck[`q.~iȐΰNX%B)Dx'rZ}ljB52 X@ Dno=F]/ұWGC{{{צ_^)y , S{(%`,(72{2`=a\3JMdcyNF!;p2 e}"T⦐o<'#bM7OLSe '%텞҇g緆Z Q% Xu5Q)Eb4wUF$,ɴu^=`sk*T,Qgб9@z(v(JQ)G]57r>wI$M/!ꅍOk7JGz.LVuL/`M @`먠݈Mh84`Bb1! &VgX-el`MIv}wbE#wU2Vhl\D6X X,hd:c$ :V9eG(NoBXI;qSEjq᫧/zWyckdo-Sx(#K X&Th$.|e 26II]Ȑ`.M2X\u,c(ʨ@,qSZ 9ޟxLE)`=Naq1nv: xV+on=U 'l| knNzn/P LrXrʹ-;_T }Xyê-}HHU~bTC~$bMFa1xGˏ ֱrĎ Ě! 7U/ʁ?b<~bʕXX Wp=ua( xP&McVg7~H>mUT"?SB V%nT{E,R&;'$~B;{Z +ۊH `R` J h {_XaKA> M0Z3qM`䥽}E 5 |PwG=`QbGOh]֭:a_eW2Pa)4U#&eɅgX=0ޗ 7uQ|~Ԭ~; !sUX)JRp#Xd~bE?AŚ%L|wwY'ƦW+Q*E5 ^zdӜXu)(*k; `y,>,}]%u4:J() dM.V8R誰XU(qm>\ Ly% Ƅ5\P=P3, bvE[JSj@OR")j(| mjuv%RlW(bQ;AB1IX"KxXXEf 7jkoT +.i79txrulzo(\ù͗pOB:~  +ˮdۘl`y1c*dH):9NTFV b`)[ MBm0@$<Ȼ؄ڿWUBa.Ų* ؋ۤb ]sgpObPmA զ뛻tzcNSH5GEx XKHh80kis "Upnguvc;7IQTU SJ9JW#ĚG:({=:CŢ8͗ן={v% kʟe|4'؇x|:6vUJO27e*NRMS_2_ Up;53+Qy6$±PB#Wbpq`6͹꥖{%'. 26Յ,˒Q)Mr]ڀL%UGW6* :>!ПF3Π4,]GzᲹ4\|bc1B.] v`Ytz6Fvj5EJ*$ZϠh^%b8W3a43T3DuTԎ BEXR),~r˚$=0~o]nX,huĠ(E8Z㦗惆,ml(+!ٵNɒCaT@M>wx񃆵',j b7"j@נc=q#F${zT~ɓ'Od}~6w/.ChҺv}',=dטe%qi d č}X>(NTG3 x"{}ߔo,,% *Vʊ=FYyt׋ϡu :M٥沢HNs^- Ep VH )IħD 4Wf&XVṷή|j0r*J%2ЛTce2UD}utղ"2&#M6miY-+Դ,3pzJ#ĺ~XVUVTT[=TYjr3`E#Uqo, 7,, ְ4,0WHabJXz)gQ?Fum>?hY^,/y~wsЩK +*7R/Z61`l\68Ll "!V7*b`Ǜ@d(3r7&|6xBԢ_kĞڭPʖkb!jX (Z?lm//k^>|R_Bê=%m4ʣ-`EgZ5ʤ{욻u$LWNw6!JϿ2[Z\poy>XHN C#OÍOCP:H*BWj^V߿7q屎7r(zcBò $#ݼ &KDDbXG}ή~.R9L,c VM B`~\5:TGܥ{7cζ}4|*8يUN ?N6]Y_\>1xɄXX9Uw\|Āe22:6Wl-]8&)cjN __?E)|E>/!64s@+ȏ'; OKXKPe2yQQ:ݺ1W۲_߲te5YLniXRl伅f!7 X ^Gn0$`Ӥsc BQ  JK)6!j'~ՎMW ȿpĒ0qY8\QD ʚ~$[i `߳x,*ʃA,PAB—Q ˻'z*D-J}%l PJ]( IN zVH#RBVgw,b7;պ7M(rc! X=QqU'HkZJzfBHȢ}{X j~,3^*n*I_S=xf`ZQ,vUa007b`TBTVgv,7:/`)TZ\b0ύɅ|d. o;2$SaT*z}66pOXoۆ^ {0Y5bA@gGjYk< S/:f$ Q|sT3B˰9$eHBOoqc)3׏t0LK🿮tivBQ(7H6!AK~N[wTk5UbQAZ޿N aT, $G+&=`Ec,ڸv=hEg]#7։Uiue)7=y@Nuy*L??Af>oiYV|p:$,*S3gb=ٸT=65;F JbdZC1{f7ְx =n|@n#HǺ0 X+.6!֡|J :O:^",@ȹE-'bMegD[sW3kC{vXs|j~7qj^<'-OuӅQ(BwWf#TfWu g]ә(6==S7%BRVt.T~qad"lBALŋf g P9R@ 7dy@⿻bvQb]E:>g5(;[_RYdVB`s[ ЭnXHE1H*aQ-B* p^% N,=3^e!=0M;(^lF9zX4"`@pCXoo'Щ%I⧺д &m*E2xr|Vg7~,x"7Pƽ 3@,Xـ*_ VaQ~ϖ8  ;GJE^E8#2Xu ݝoC9v~Su) 90`SBTVg7|,i/ t7T,AǶJ<cXnBw>*+X,@ɢE~ũ wGu'=ӧOo"Z^n! N,Οz;)/#hr_QuwK?`BSxe0A oq}d2['rE4NYZ0  Q'}Nyk G55 {?%BNj[ XsUjLk绎4^# ~J:*j}<(6A!HFiyx لV!C*t<"/Ƣg"(tb +m(pbvDn,8QgUT@ZHhՁ**: ـ28e%G:3|3ajrs˹KРEE)aZ^ڸ40{8>qΉGQ Q XHc @_SF> ֓#;.WiO&*nwzHG{(xo\Vxua2PPLyщ9 u xgx~FubuAƚ3H3D,&UȐKפ ȍ5h,8&"J{},zCz3J[x[b}V\cfs 0D(Ј3H.`qf5׆Oa ;l5;;;8Kka(2HΓxBXG8E_Q˩`Je!y ET,]D"ݽ BU!-S_U,ՙհ0ZSFirZĀJ<հ"=VHT7!* "J"17LMOQMM, xxX, 7:[Өm rz2 z}ZO^(TW[} KXaiSo#2 dt2 5 2Bm\a$% MtY)N} tE9* G0"6Ag*Enڥb`Q}i V't-]U! OyxKSt,N") %6$/o%cEƀ^cFL odDBf|)$zO VRx/Ib4@Y֠[ 9z߅B#̠:EJ^ObeĴ_.Zwg)IU lX;1`*ƕrȎE64kli\]G:vnDxPHC7&Gf"ĂY u u! eWO:JwNT* !+(Tq0R{]x ;(Ieؼ*Fev )vKeQ,rc6BlEmPk>$Ee*YAKH'Je2JE E-ݝ{G8tUH(/l|cIO X9D,XKN gzw ($phǥ%JNp.CA(9GZpkP_]]w#%BNhƫA\ L1z|!. m|NkwK4fXx"s?a \VHްq]fDzm)HUQp$壴|N|H`A"S:2+"ƅXm[2#z:,cbIQ4ѣA8rc!!TXF}򆊨*J.td]p` hhE9%kwz򉒊%Inw]NI+PM|X4d4K+WxyCl!ZvWXʶt Tf!U!=ȺVɀ+(Y]O]rr|nxkYd*=ɗ2ŝi@2yX;ĀbX:d SBE؉8TM*\#α ૄvE`%.Y(57Gpiv?=ҙvJSelI+wPb2QM^u5vDbzxg 7/'JT e: ˇ CUTķ9ȢJ.b!ֳb|\Zxb@y$_;BGwMMhX}KC2X?r}T] n/"}φVD,|}( x'l 8i](Px]xP<|e7:#Bj0 FD2:+(KAaE@DQ ,.ڭ;EiC9JPЩ';1 8מFY@H'r ɝHGyiPR& HF-kJ0[QHU#ߥ-,OmhH'biHiԥ9ŎJO:M(- X.dXבO1giiiv$ jי/|y(3LN~e)DnCEB,Omj( R!!pZ%O=l;m'j zjX %bX!Vw񧈃GZDE8eS;8wFa X.L <FUl $DPލlΕ߇֓)z^NWW)wj@QGŢ渟- VlN7KzNX ($Q 12K`="=Vi{fs EL:} \pY8{$6p-x8  C[;KX>5jl4hf%\Vw*@ܶ!-66QDbs(;˗ϐ]dkB'_qW"O|nqF# /wD-by:ߩA3(m q a!rsMLFK\EZE1CN6 G XBsAx HeلN&ܡo*Ao0T,5 .R\@źjj drac{ `dSJ_+ɠ*aX(v  }޹ ;PlQD\E(O 2 ##x ݴEu}0<NGMJ&8V0ڧ,}%Ў z ^՜ٽ@Ej R+挼1Gn<}esjCY(pqyY$c(4] -ZUBJXO:{EQd;%Rq]Tb=ARSu)E~qWe8{I&safXQoAJNmൻTO:|FEAQFm~mӝOg@3uwGR=C@,sxezG UK",|U#GT؟>* X%}nX{CqnJ=5gTT֭6Xv-?O`WQdj Ҵ\rXp#* <%=;QTcPA" n)/gsu 8uI&m9ɷXX*Vթ ~M+kKQ@'r)T, G莊*^ t,[t*ل8xehRozcE Xo\΅ Dc/'ځZSD$8n# tT;wbrS/Xb"ƀ}%cքp2n~B'1 x!?"QT,z|w.. 8y=?Na ݓ)a6O +I ,]C_ 2rJPpT8 EwPA ;OMQ2ÚV2j]PV[wd$cKd[j|OI3z x"-'\DNO~XD4 ~r-l+}Oe1$*2)β| _PS" z)K%2T,19M]8+kb KWe~+f2ط}cGuhO](zO*ֿW6c>{߿Y]`I t%6[y=VUGnŢhP(԰&&2 "(BLvqsD 'Q|Kc$mS:VXf +Y\Fg L͜#:XrQ~uYQ}QBT7=9NJ2 #g{QhfUD/37eM|dP;0ozXTL9@WQEO~P;QhT(b0;ņ%ea21 ם@)dR,'1=FS`YP$3740U|Wxչv66MW~q +xT뺵{})%j IƶQhp)UU,/!9T C.\rR;$ ͢6D”# Tph r?#VX>wpJ N+N^@T'W֊fd(BEЧbw!Ƣri*Qj#ɄcOq,6!(tydrPv? JX(ڌ:js5XToaѤ* QkkQ26Bd36` HQ]fF} +xeLBf֑EwT>%rPB,d} (lI6tMe@jMN y)7QE % u`s"St/05*9"?d`ـԝAr;`?V e׽ enIڅ?JQBXOhfk*kF]T" Qh$_sXnƩ3O%;bKJ S2v0P,R!F4]4b=əܪ)W=պcU;Gao6)DsةBB>K$$8ytJx5ƏPu.Q9&HPGSRaaB[ .ue9 rY'Rn aIi2Nfd=ңX]Oa)<)!dalN(4@D&`)te!1H9l1'1w*9rtN TzѕtID,.Q!ٖiS "ӱ8Rm ])"S&6 +BtCZб8+3 ! wdѡ*J~[ucKbndePS2<[P P2IfqOF~-;1O=Y2nP Yi ^3]~%c(dtl͆!j7.yXh\*tX\5Ѩ$<Ʋ SbYVx ъ-[+s`zweuRF,s(& yR[E'P 3I*VYf䌇wra7 5 #!F.)i#!\+˴h{nm3#V'+,&K 5+8DB0LZ~WI@cJ&l3dCNȀc{vgۈW6 3$fFC0O LZRم7V%TI QXX d1JiA41gFD/Lb~g2ebSabĬ_h^&/yԤsv|10vr3ZIcE% 5KC; L2Qd6B,5;]ʮ%p`O o_!\.;YĀE,,LcĄ9CjukQXZ.?Y9wn#H,R}":J=n&JhC--}#'Po8³3{_!~zT0+?WSe1`es4L Oj<}8#B^lbu8>1b1`1bp ,}b b Ic@ X:\9ĀǓ9Át9s '+'l'9s@1`p-s @N8VNOs bZ'@́p =4@ĀõÓ9@ X9a{1b1`1bp ,}b b Ic@ X:\9ĀǓ9Át9s '+'l'9s@1`p-s @N8VNOs bZ'@́p =4@ĀõÓ9@ X9a{3{QDtfit$e.TT* n|V\f~V_ji $zJ7׼e{Vp9ݤr6+Ȓ΀Z}*# 2ѵ0K +l|fLiyRŭqifY:/Xt$Y%U# PF؆OL֩_2T\6Ye=2Xb[2b3KX:|IJct3.'B L̏CJ%m X ek l s3p,muFs6WB22}rK@\|e liԸIcvonŀŔ [̥7cؔ Hl8uLni r' 30k̬kp7M:ay]?YE8`X\ʎ $K7.yR9IĀ5KP޳ Me&=wI :ڇP (GŠ^f~( dl?h-D:}~,lLALSPђONH6Ø >K7`X^kUcioLj5^ADEʐx  2sm@U\s{{Eih*  6XҥJS>!R[s+,tՙ '2ΓB4Jm#-~B٣f dK|F8I ԙMGkN/"ۦ-Zҙ ~ +/Rx%?l'$KBT<9{&}V5"tfi R`F/wut%mFYҐgo '4,Vv( wKI#ѓjP/+TxrCg&Vp|p:%7,o 'do>`sX/!4FeF *uC7|>Բت^tXJ y44f}M r ~y ;=_4(SAKǔ3MxZ)彴9MpKh x$Z0ã1 pIg64EQM&x]a aHy/mXO'e[͑C鐦Ǐc錐qT(I;]Q[HS4X1el2 Xl-n?ae tfi@RK`ex5 ;ŧUf\3kX_]Y 'ҙ ~ Ȩw,6Lar,ǀNҏҿqM"Y,Ro XRvA֤RqI(X\Qd"SVO[FOt~,<%CfڱƸv!"$T!0U<$ kX%Hcn9[McMf!7qVQ&wSv& FjVJ_8̓L.&ob1Yd *Pȃ"^iXڀ X s+MR9TN `~d`3Y$C岈ؓs1&ӔEPNn-"h ߇cl X_5<@)~ɚI d^'`I>rIerZKHj@BLke &ӋF郞 hF6`yX-gŧ ?~rD,6cdGRɆ*$[.bY7r,bsO/.+\}]4|KKic7P%<;% z}~E(-S B,.qv!@h`c$*Z LNvEDn[2اf`PeRc|R"hYϜbqF6[tWdxȲ.I2Zj)zud`B}AY K~U .Uaz l6ϒ#!ed+fH+̞hD<=VߒVpbs@K7^KtLmodxq[#\y!nLT,6y쏻ҪUؙ{2KeU9MO$}UV,?kOpǞ6uElJ$Z/y 9KհxKXF%hj=B!gǐ <WoTnyekJdm4bMΈj(dHRi@xX{"Z Kz:9w>+S[&¨ųY5Xڨ͙Xũ!G,dl|(ox' LEs2\H 6lBP*NoٲQV,`mLM ـʼ-+y$(@Ș'_%#ReG(-La${Hw5ZY%cU"23sI%;s2_<(hRIA*i`~n,i` _?u5~Y[!K{i>O,y ωԢ( Y09,?tcΰs X萐'ke1uDqcDzRyVʶcȒzIߡzeS1b8~t4Rx6J 3c M(GvK"wvjIENDB`DyK #http://www.gonzaga.edu/default.htmyK Fhttp://www.gonzaga.edu/default.htm9DyK 1https://gwired.gwu.edu/adm/apply/app_online.htmlyK bhttps://gwired.gwu.edu/adm/apply/app_online.htmlDyK http://www.gwu.edu/yK (http://www.gwu.edu/DdYL  C (AGULOGOVbvw*xFFURCnJw*xFFUPNG  IHDRbKGD݊ cmPPJCmp0712OmIDATxn#})RNzƃ|+D +bXX]}0~l112y$ӌ۴`zWUwW5I žm?w7g|6߻}&s<`{"v}O50=>=0駱>dٰ̓00#ϲ=^'2ӲG8ӘKc𴳳ۈ6yΟ<@\cO.z6ßmw>z.>s0t3tFsQ\wG Đmf֙dM"aygn0M=$8\?adhHd& 3LP@##|i (15:2f==¦&[ MWhXlH~+H3S"2g9JB\:69wohgjBxO"cթ1?KMKHF7yd2?MW=S$Z CL2WyqC)^@d&3&<6~'UfwO.T6h&ed0_uú9vI_$挰 .Nbť<5dvSf 41v*2w%qs\hN!Gs,`v^cx3Ed>3_OmP0\*LߝəLՙ1Df[ `#ؐN˞ynNXgp2MÚpV \4kb3̛mϗ6sɘ<\7Uj&2'LYp׋kjC$^:CÚR 2/(؂ T6U @Oa@x:-)J#OZ̤o`IƔԀ9!шμ/(sc!l4loh͞1W#r&/ɽ3Sd:2ڛ_:Ceb0dޔy;(ߠ"C!%,1=ڙHc tͪS\ב7 6Dɬ9D3?CZ#~k*LB 6!03+ذ`dI\X`2g 98N eV $Sgf5Y*ccDc{o]=ó뺛MQV)C떬H fB&6]?m̘Dvnj_ZWLf03ud:2l0345yz|Z3歱EScCF9`Y i1jVktLϼl |[4m}"Ȓ edlcL_I"M]]bWoed\HkXl}CI9[361vhgçAJMj0| oxj~`؜F`952}Yk|}q_jDbAjolg4Q\Vm48n,oUb_M65$6b8Podfug$hdkN/fդx`4GkǥLJj\ycs2_1dv= "T^2ǩd I l:6X:DjTsnS\uZgm1$2yLq?ajojypj!חo iv|sF6ݘIZl7K=yRlW.S#svZ`Hl$Lg`7rT0,KR99TaS P[ .5z!(:XVt|@jrv& F*%j~1 o=X@ }]kW}\n ahXEf?|ufiX\^]s<5Z=`8:;jL)~:mq4oFư.[a u)ʝª˛jn`5u4``y̑%'w0/\kE[>̗-:~ )ZϗR|$WЍ!L\9`haޚ+| әBZ)T€buV'`Ss 3mAC\3|P|UotX,Jꕛn`hȐ_J]A] 9Ld*χx$-!`N3C,l[b.JK|6w?+U!@ k3g1`r4TθkLTg+*_<32^s{P0vnxcYĭ \3 Tig,&<57WN}8i!!VOuGC\&q冦H,qnʡt=!YWYPbVfAk3Xl ?X%e76S`YL}ƙ[&`g SnlJvߥ{WEf#fM Faht3+05X \4?wߤwFy~qkTf yln30 SbS\1HSi^Pjc B2yalpJ uZ?.a9 >):~6_>IENDB`-Dd X  c 4ACon_Mgtb(-SYb,9(g -Yn,SYb,9(g PNG  IHDRg[gAMA|Q pHYs.#.#x?v,IDATx^]*~ WA*W *Ы@_*0W UW Hꞻkm`េOKB? 9LCcEă={I7O7EI7*5O~=#%޻W-x~R'ˎهAOYO!t3ޣ|v:&*,lbFYr\CWyV{*RS!G§Qֲ?ɟ8س)YYf>h*&#˙̛fXCqYJ~F? cu*p73VkS#ֺb.w3hY@15.ѯf&uLVeI:zI[IUy:y^ƶܶ6pvTe6g|"fUROzUB=oBVc6-o/~ Iē=@$wG H8^O:YzX.eqq5jH B eeM|VZJ?u ]{Ҁ3K%md!n!M/wcd kdSNͥ1rH»рu[Y-ۆ.pU+Q#?XC0)}xaj':օ0S2S? ɪwN~&atТ:@COºq~QR/,)Y@0g Jp?u5v#T!dLRۿ7'ȕ0fOuG (8Č!1 =ï'cu9m׀3_+E-a=?DwSG/X٘}mXo+x7$Cb yPq.iX؟&@Rjfe²P% {Y%PcZ5)xqxW@2'ݕ@8/:!zi!3MPK:$ C&%{>$2d ^[ 3%{_c&5m{9"s^  r.V7,ip$ &yǶhL| M]dJnqSgy2=d`UJWLb)t"ށ$?p&E OD1'>@&_" b*aPAu4{\T0'>eG lϼA u0 8(3mAC-yce1RdxX0&e*Ӆr "PXv.ц[kueG/%.f 1YʲiⳏETBΪp-2-E!;E*薪O%Jʤ='B$MST2>m zޡ7&JH&5hLU#gXِazer@bpVm69Vio4A`ћP}-?Q YΖ _-z38Ѳ rc9_;̼I+:tW YK#o?hwmXxoaw/Ϊ5ܵNCO=q3⼱z5$z⬙l[yJ e; YkChx t@yZך}za}'?q :E}$ӳ".G’“+>A; b_,xժxp yX!4#"Mڰ˻PS1v]Y+r阂2FbJeVx8s/P"PVr*%oPSS&%}͚(I0䊶ԗDq+Wn1_Lrږw3|7HpHM\{,でG{|o6.Bѳr(`OY:h%*GȷS=*7ى|/ l4Agz$2T2}X$lZ㖵f&qr[Nb=0Q1(A$S+8N~ RƯFl[7CR=p~rRR9 ;*>YMWxN4ТA1rL(I S> ml'kZCuf?j~W7}5lLI܀ajDח>&eNrՇZtڴ-Ʃcc4OK fqX0߲P=#-Ґ G Ձ_wgxEZ +d'~A/3@oűHlƬL؞-Ƨ=0#8oC wتP$'G^*tobm2DuYچp5[[d͚d$D7L߅zsV@H4u5fk91#lTŨ~'%@p=JH-xCȴSp5;Y M鐙E>m"Ig]d^ZAVöH ׊PgxN^Ɩ֔ZAM]=TʾP f.Un/?JT58ӐԮSن騺VfqwԂ{%~}*3l[kg :+zc74[GXٷgFd읬3_Im=53OsG߈~NttT ;mG ? |cgTXOGɲ{Gm;;}U;-yHǜ;wkN{T\-?쩥yᅨ;Auwmì_9]qeuej_b')gJeZ ƅ]9@J nr.I%բɍ }"-Zm[?iQ׾81=|EuY4rCp75AsvmK hqt{Hgc[<-qp?h^Q^83\ 8;a9)JO%!~,eq*)U_FQeYujEq:y)"7xMo.d;r񠰂]`!:Zu;[,8;_랠W} .OCVjkTt-݂Ӑ]Mp,ou*Oể<țLa_+}rY|ߦTgRaqV #7Dmpր3tvJ@ַY3a͙?omp >.Ά-%72*9߱&D.,ٖ Mnе#&eS72mfgr"vO{~vpBpe?ά;|[_rM^l^YFzJb'9U#60 L7s#9r' k\ !owA[?y} Ppz:΀ϼQ^Ҷe 1luZs;tdHWI)dДqvַOP Z gJ gju|ІMx ̀83J؍L¾h{M!ـ'oJZF>ƙ݊>TmbJ5Xs,"o(ӚGz D"21a}Npf|t\-5w9Qo4_.gz}qkC8^H:QɤK8Fc3Eh)ƷG 2mD86e<;<~YkPkjΞ ˍD%9 m ߭~JxXU[g[UsgņGV@/Nk{G9:vQݯ.:QzC#~z=2}k ݕ83wn3}-ߥ}Qns\Q9~'Mĸgf{f6SS-w{g-8u}%EsHS#]]f"k~iu(C^^m꬧9'Erc}c67->֦c yFq 8i ~B>wo sn(Xv&^UgRiƛh;n3TqANOPw~_+Y3C@r~3r#S /gӊLja(WƏgnl [ViP[irfvw kVwr={=#є@UNW⦕.ig SGgE5u јiߥu%qK,YNHp,XjDrY&aOeɪ@Ew[ -s"xxR4/dR]T1N ;/J5]řU*B:|Krr(.M Rd$,q !MQ%*$mZ[ԅC xYSY=C/׽;s/Aӿ/ht+$w}u$r]\f%]yimL{dk}cRmE:A[3q"5-'7HRIܥJ 8ÀAMDQli|C o4EXO j45(PdNQ+]b!le'|}͞ g\ҳ3ozhI5aw99cO ƙtg1?Є]A0ѿm1JHwedD4a~D](&Y?k&Q]lٔYtd&1&#θMy\&^  y7\"(Wg&8s6| ͖\yX{#{&O=O ȶs%z%cf{BO qp;2 b,`L΁hl-Y[I .,ݚ1sq,#3u\_ë80ZݧPÚ-DKgt9pVR%c8v2#vn՛άtNq_) #xgC[K:hFi'Ƒgf_xЭ .!1ѫB K7wR٧瀳6Aՙm $a>nY[?rA0~Њ3]W`Y EYU}-lq0u̩$5>tV "x< >K 5i `0i7/y@@dy˚: V3ʁ~Y7ΜOsd9 Y+R.*V0 ?jߔm&$Wúa}SIWG!T,{L39 EPǶ *#/5OZMI̲XĦ It ߂޵]آh=NIێ-Ȋ4ZNXe%d]]˲j!X҂V654"ɸ5B2i'&X-RRG{'i.d4έԾ0!bNuj2yR Y"l/r&PSSw6zZ|I4U}8)+o8M[{Z_ndɭ[ykZP.ǭl=߀3n6 UHȭn,kHe飺]M0ԛLvt54:gm-vMj-aG%'>1m.Aٺ"z0jf:Zofa={8 jˊK0˸~5^d~:p A-: 38 8kmD(^5QB&ϚgtKDpMtU{LO-€3N* (ex,/L[r1cNXUًT(:K"O'ѰN)9PwH!POS6\˒!Yjv_Q8\‹Y!Ux¢fD.,>\[gG{6om߶[m޴]s.ME@l15}CÌ1jÞ%6Cg;2pQN`*'1JRD)SJqo-j9O/{$J 8S'Z \P SK_OOO8]VPn?#bх5y&?HA )hUjb#NobcF#Ֆ:vMUe3h8*n)m}jEuUۺZ-&xz(4X0ݔF:fXyr.F. Hiߘ2ךRsܡ: ge1ZP)M8C.p9АU9C#N>hQi:ԎgniNIbdk#]gg&&Ql 74вC瀳.iMcKvs"/ڗoۀ3[H--Kw㌟ 694Z hmfHK;&g]8ks- ;:䔱44ȣ8W5G&>ѰĎ@$"g54UÙY7ܴܳgZJA9!;n7$F P3 ڣ[jmj<2b䧭ϡ# k>pt^g˦9ثۨtqΆY[x98ʼn~;gRdxw7ѹl4d  <îlQLйdPiYVe!i-6Ѣ̳VF8bd))'p֦td~328P2bJN(\a8c&̙\CR;lWIENDB`DyK www.gonzaga.eduyK 0http://www.gonzaga.edu/DyK #http://www.microsoft.com/cmserver/yK Fhttp://www.microsoft.com/cmserver/&@@@ NormalCJ_HaJmH sH tH V@V  Heading 1$P@&56OJQJ^J_H aJX@X  Heading 3$<<@&5CJOJQJ^J_H aJf@f  Heading 4$$@&a$'5B*CJEHOJQJ\_H aJphDA@D Default Paragraph FontRiR  Table Normal4 l4a (k(No List>@> j Footnote TextCJaJ@&@@ jFootnote ReferenceH*6U@6 ,H Hyperlink >*B*phFV@!F FollowedHyperlink >*B* phDZ@2D  Plain TextCJOJQJ^JaJOB Solution Headline 2# !6$%>+]^"5>*OJQJ^J_H mH sH tH O  Solution body# !6$%>+]^)B*CJOJQJ^J_H mH phsH tH O Solution Headline 1%$ !6$%>+hx]ha$B*OJQJ^J_H aJph\OQr\ Solution bullet# & F ^`NON Body no indentx` B*phbOb  Body textd`%B*CJOJQJ_H mH phsH tH FOF legaleze Jd<CJ^J\O\ Quoteed8-B*CJOJQJ^J_H aJmH phsH tH XOX Quote dh(6B*OJQJ^J_H mH phsH tH xOx Intro9 ld$d &d N P 56CJOJQJ_H aJ\OQ\ Company Headlineh5CJ$OJQJ^J_H aJHOH  Company Nameh`CJ^JFOF Date Published d^J@@@ Header ! ! CJ_H aJbOq"b Solution product name" & FDp^D`p_HVOq2V Solution Headline 3# & F^5OB Product messagingj$dC&#$$d%d&d'd+D/NOPQ B*aJph2B@R2  Body Text%x ~\[EH?,N ?,N  @Ano67pq7]:eTU   4 5 6 7 8 7882Y@ I "5#K$g$%%())+,-~/0114U4 78 ;;>>>>>> >!>">7>M@@@@qAlBBBBCaCCC>DaDDD2EzEEFbFFF;GGG"H*H\HoHH ISIII)JpJJJ3KvKKKϒ"mǓۓ&qW2~ǖa;ʘY5Ě Z1xPݝ?՞ kGѠhC͢cIh?ҥbC9èK۩Sܪ+uJ1uNݮ*lMҰc8Ȳb-z Z7*{˷]θc8}Ǻ^4ϼbDоdC_:_9\4~ T7 M!jX)uPqf%kCb;Z;`C^iM7v $t`QJ0y V9<L7|X9} X7_<dAjF>#qS;Tl}\9R6[8~Zf@gnQ/y[@mJ%p JVa,ABNgU  u   O     0 1 2 3 4     7 w y z | }                  34=<{Aj}#678y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y0y000 00000000000(00(000000(0000(00(00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000y00y00y00y00y00y00y0000E@0y00@0y00@0y00@0y00y00000y0 0y080y0000000!00000 0 0 0 0 00#0"0"0"0"00#00y0!"00000y0'(;00000y0-.\$0$0$00000y0y0 (#J_v 4F   9JQvX_gnu{܍hL3{   d6HXXX4Zj   XXl  ,b$]=r7Y}rWK^4@ N(  N  3  N  3  Z  S  N  3  H  #  b  3 #"  h  3 3"`    S JA, clrlogo%20transparent"`B S  ?Y1>qAa)@ t1 ta)t|*+t+L*L!^ t  %(J't@"""T""ԫ"T""Ԫ""T"""ԩ""T""Ԩ""T""ԧ""T""Ԧ##T##ԥ##T##Ԥ# #T # #ԣ # #T##Ԣ##T##ԡ##T##Ԡ##T##4##"####V #!#L#"#t##$#%#4 &#"'# (#t )# *#t!+#4!,#!-#t".#4"/#;0#!1#D2#3#!4#5#6#|57#l8#9#D:#;#,#<#T=#>#Բ?#,@#DA#B#C#4#D#E#t6F#DG#,H#,I#6J#6K#tL#M#,N#lO#4P#tQ##R##S#T#, U# #V#L#W#X#<Y#Z#T[#\#@]#>v?v???????h@h@p@AACCDDEE!E&E*H*H8H=HHHHHhKhKvKvK{KQQQQGcGcvwvwww6x6xDxDxIxyy,y1yyyyyOzOz]zbz||$|}}}}OO]bӅzzaaotѤѤߤ^^lqXXf**8=yyVV^c22@E"'ddkbbkqgg|       * @          ##+      !"#$%&'()*+,-./0213458679<:;=@>?ADBCEFGIHJMKLNOPSQRTUVXWY\Z[]`^_adbcegfhkijlomnpsqrtvuwzxy{~|}?JJ((e)e)s2~2~2I4T4T43:3:E:E:e:e:>>????????o@z@z@AACD D D E%E-E-E7HACDBEFGIHJLMKNOPRSQTUVXWY[\Z]_`^acdbegfhjkilnomprsqtvuwyzx{}~|9*urn:schemas-microsoft-com:office:smarttagsState8%*urn:schemas-microsoft-com:office:smarttagsdate=*urn:schemas-microsoft-com:office:smarttags PlaceType=*urn:schemas-microsoft-com:office:smarttags PlaceName9*urn:schemas-microsoft-com:office:smarttagsplace8*urn:schemas-microsoft-com:office:smarttagsCityB*urn:schemas-microsoft-com:office:smarttagscountry-region h 10112200038DayMonthYear%%% CCE EXXXXZZ[[[\$e)e|llrrzzzzL|Q|>~C~ŁЁׁ!pu4;FK6; afgmw #* !   4 X _    k  5 y  7\9S_ d ^o (3 4    k  5 y z z | | } }        3333333333  {{q y 3 > M p r  ,,6'(ALQ!>">@@lB2 4 k u     k l n p       6 N w          A#6884    k  5 y z z | | } }        s}LG^`OJ QJ o(hH ^`OJQJo(o   ^ `OJ QJ o( ` ` ^` `OJQJo( 00^0`OJQJo(o ^`OJ QJ o( ^`OJQJo( ^`OJQJo(o pp^p`OJ QJ o(s}L        @.-+ |q>34_=,HYgHnXcumA8 h;(5dwG78dcmj}h' A[@-,P@UnknownAuthor Gz Times New Roman5Symbol3& z ArialGBerkeley-MediumEBerkeley-BlackGBerkeley-ItalicCBerkeley-BookCBerkeley-Bold?5 z Courier New;Wingdings"1hTT.'S'S!4d  2qHP ?5d2EDraft Preliminary Recommendation from the Deans Website SubcommitteeDadATS Root Entry F0i:@ Data D1Table"WordDocumentm the Deans 1$Mr. Christopher G. Bennett cbennett$Mr. Christopher G. Bennett cbennettArchived ACPAC FileArchived ACPAC File՜.+,D՜.+,`  (HT  HDraft Preliminary Recommendation from the Deans Website Subcommittee Title@H     , 8DLdT\ _PID_HLINKSEktContentID64EktContentLanguageEktFolderId64 EktQuickLinkRoot Entry FZ<=s Data D1Table"WordDocumentSummaryInformation(DocumentSummaryInformation8 CompObjq2Draft Preliminary Recommendation from the Deans 1$cbennett Mr. Christopher G. Bennett$cbennett Mr. Christopher G. Bennett՜.+,D՜.+,`  (HT  HDraft Preliminary Recommendation from the Deans Website Subcommittee Title$,     (4<Dt| _PID_HLINKSEktContentID64EktContentLanguageEktFolderId64 EktQuickLinkEktContentTypeEktFolderName EktCmsPath EktExpiryType EktDateCreated EktDateModified EktTaxCategory EktCmsSizeEktSearchableEktEDescriptionekttaxonomyenabledEktShowEventsATm)http://www.gwu.edu/'\1https://gwired.gwu.edu/adm/apply/app_online.htmlu4#http://www.gonzaga.edu/default.htm<w#http://www.microsoft.com/cmserver/h2http://www.gonzaga.edu/LX ;DownloadAsset.aspx?id=88140e@/s@pN3s2Archived ACPAC File EktContentTypeEktFolderName EktCmsPath EktExpiryType EktDateCreated EktDateModified EktTaxCategory EktCmsSizeEktSearchableEktEDescriptionekttaxonomyenabledEktShowEvents EktInPermATm)http://www.gwu.edu/'\1https://gwired.gwu.edu/adm/apply/app_online.htmlu4#http://www.gonzaga.edu/default.htm<w#http://www.microsoft.com/cmserver/h2http://www.gonzaga.edu/LX ;DownloadAsset.aspx?id=88140e@/s@pN3s2 Summary Archived ACPAC FEktTaxCategoryileArchived ACPAC File#  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Root Entry FG)=s Data D1Table"WordDocumentSummaryInformation(DocumentSummaryInformation8 CompObjq * !"#$%&'()+,  FMicrosoft Office Word Document MSWordDocWord.Document.89qOh+'0 l<l x @F#@t iT@s@s'S2Draft Preliminary Recommendation fro