\documentstyle[11pt,fancyheadings,fullpage]{article}

\title{Houghton Mifflin\\
World Wide Web\\
Server Proposal}
\author{net.Genesis Corporation}

\pagestyle{fancy}
\lhead{{\bf PROPOSAL}}
\rhead{Houghton Mifflin}
\lfoot{}
\cfoot{}
\rfoot{{\em net.Genesis} Corporation}

\setlength{\parskip}{.1in}
\setlength{\parindent}{0em}

\begin{document}
\maketitle
\newpage
\tableofcontents
\newpage
\pagenumbering{arabic}
\section{Introduction/Background}

The following is an in-depth proposal for the complete development and implementation of the Houghton Mifflin College Division World Wide Web system.


\subsection{Company Information}


{\em net.Genesis} Corporation ({\em net.Genesis}) is a newly formed, highly motivated company devoted to effectively integrating Internet-based services into a wide range of corporate structures.  {\em net.Genesis}' primary focus lies in the World Wide Web (WWW) and NCSA Mosaic, its most prominent navigational application.  We specialize in developing advanced modular systems for companies seriously interested in conducting business on the Internet.
\par
The World Wide Web has shown itself to be the first commercially exploitable Internet-based resource.  The Web's power, manifested in its ease of use and hypermedia capabilites, can be uniquely harnessed to address the specific business needs of individual clients.  Web-based systems provide an intriguing and profitable forum for advertising and sales throughout the rapidly expanding on-line community.   These systems, implemented on a global scale, will augment existing markets as well as help create entirely new markets.     
\par
{\em net.Genesis} plans to be a major force in the growth and development of the Internet and the proposed National Information Infrastructure.  Our goal is to develop innovative, tightly integrated WWW systems which provide corporations with an unprecedented level of market specificity, customer tracking, and system flexibility.  {\em net.Genesis} is characterized by its sensitivity to the Internet culture, its responsiveness to new technology, and, most importantly, its undivided attention to their client's business environment and business needs.

\par
Although {\em net.Genesis} is currently holding informal discussions with several other potential clients, Houghton Mifflin would be {\em net.Genesis}'s first major client.  We believe this will establish an ongoing, special relationship with Houghton Mifflin that will be greatly beneficial to both companies in the future.
\par
In considering {\em net.Genesis}, the strength of our individual members should be noted.  The {\em net.Genesis} team has the technological skills to provide world-class service, close proximity to the forefront of research in on-line areas (especially ongoing involvement in the MIT Media Lab and Laboratory for Computer Science), and a deep motivational commitment to excellence.  We have exhibited our abilities in our {\em net.Genesis} demonstrations and through various WWW projects including the MIT SIPB system.  {\em net.Genesis} strives to be a world-class corporation which is dedicated to serving its customers by understanding their business environment and business needs.
 



\subsection{Corporation Structure}

{\em net.Genesis} currently consists of five members:  Rajat Bhargava, CEO; Matthew Cutler, President; Craig Wisneski, Director of New Media; Matthew Gray, Principal Software Architect; and George Hadjiyiannis, Principal Hardware Architect.  The small number of individuals involved allows {\em net.Genesis} to be an extremely efficient, mobile, responsive, and directed corporation capable of delivering high-quality systems to exact customer specifications.
\par
\begin{itemize}
\item{Rajat Bhargava, CEO}, is responsible for extensive business and management operations while still significantly contributing to all technical aspects of the business.  He has previously done engineering work for Intel and plans to obtain a M.S. in Electrical Engineering/Computer Science (EECS) in June 1995.

\item{Matthew Cutler, President}, provides business direction and an extensive computer background that mainly encompasses system administration, design, and application-based support. He has served as a network adminstrator for Aetna Life \& Casulaty and plans to receive a B.S. in Mechanical Engineering from MIT in June 1995.

\item{Craig Wisneski, Director of New Media}, promotes future business and market direction and is involved in technological design with a humanistic approach.  He has done engineering work for Motorola and is currently doing research in the MIT Media Lab.  He plans to obtain an M.S. in Media Arts \& Sciences from MIT in June 1998.  

\item{Matthew Gray, Principal Software Architect}, is the director of our technological efforts in software/coding development.  He set-up and currently maintains the MIT Student Information Processing Board (SIPB) WWW Server and has also done extensive work for the MIT Media Lab.  He is the author of the World Wide Web Wanderer, the first program to provide accurate information on the total number of Web sites available around the world.  His data and presence is widely known and respected in the Internet community.  He plans to obtain a B.S. in Physics from MIT in June 1995.

\item{George Hadjiyiannis, Principal Hardware Architect}, is the director of our technological efforts in hardware development.  He has done extensive work for the MIT Laboratory for Computer Science in a variety of fields including advanced supercomputing.  He holds a B.S. in EECS from MIT and plans to obtain an M.S. from MIT in EECS in January 1995.
\end{itemize}

\subsection{Staffing and Resource Access/Availibility}

\subsubsection{Staffing and Task Allocation}

For the proposed Houghton Mifflin World Wide Web server, each of the various aspects of the project will have a principal coordinator.  Additionally, each member will be involved in several, if not all, other project components.  George Hadijiyiannis will be responsible for hardware implementation; Matthew Gray will be responsible for software implementation; Craig Wisneski will be responsible for technology transfer including documentation and training; Matthew Cutler will be responsible for project coordination and serve as corporate liason; and Rajat Bhargava will be responsible for overall administration.
\par
{\em net.Genesis} is actively recruiting capable, motivated, and well-positioned individuals to add to its roster.  Web server operators with a demonstrated ability to develop innovative WWW systems with practical applications are currently targeted as potential {\em net.Genesis} employees.  Our positioning at MIT allows us access to many of the most intelligent, enthusiastic people in this emerging field.


\subsubsection{Resource Access}

{\em net.Genesis} has access to many technological resources including workstations, computer graphics labs,  and a variety of personal computers.   In addition, our members maintain high profiles on the net in order to keep abreast of new developments, monitor general trends and start new ones.
\par
Because of {\em net.Genesis}'s unique position in relation to the forefront of research and development of network technology, our team has access to some of the leading researchers in the field.  This advantage will be translated into more cutting-edge product for our clients.  {\em net.Genesis} members have close ties to leaders in sever al highly influential MIT research laboratories incluing the Media Lab the the Laboratory for Computer Science.


\newpage
\section{Proposal Introduction}
\subsection{General Background}
The Internet, a world-wide system of over 30,000 computer networks, is widely acknowledged as the precursor to the National Information Superhighway.  Currently, well over 25 million users, with access to over 2.2 million computers, access the Internet with unprecedented frequency.  The approximate user breakdown is as follows: 55\% business, 35\% educational, and 10\% government.  
\par
Internet users, whose overall ranks are growing by an estimated 10\% per month, are increasingly turning to World Wide Web and Mosaic as the preferred means for navigation of the net.  The World Wide Web, or WWW, is the first widely available electronic means for distributing multimedia documents (including images, audio, and video) over the net.  The WWW includes the hypertext transfer protocol (HTTP), and the documents are written in the hypertext markup language (HTML).  The Web's growth has been explosive; WWW traffic has been increasing at a rate of 3000\% per month and the number of Web servers increased six fold in the second half of 1993 alone.  One of the keys to the WWW's massive popularity has been Mosaic, a WWW navigator application updated and distributed freely by the National Center for Supercomputing Applications (NCSA).  Mosaic provides a user-friendly front-end for travelling within the net, and handles hypermedia elements (large images, audio, and video) via a host of specialized external viewers which are optimized for handling hypermedia elements.
\par
The combination of widespread availibility, power, and ease of use make the WWW ideal for commercial applications.  Potential consumer uses include, but certainly is not limited to, general information distribution (such as catalogs), product demonstrations, just in time production techniques, multimedia presentations, online ordering, and virtual shopping malls.  The rapidly growing market which comprises the Web is diverse, wide spread, young (average of approximately 26), and highly educated.  At present, the only large corporations which distribute commercial information via WWW servers are largely technology based companies (including Apple, DEC, IBM, Lockheed, and Novell).  In order for companies to avoid paying licensing fees for the WWW server software, they must provide a secondary means of electronic access to the WWW information (such as gopher or FTP).

\subsection{Acknowledgement of Need}

Houghton Mifflin's College Division is ideally situated to exploit the Internet and WWW to its maximum potential.  By providing a comprehensive WWW-based information system, the College Division stands to directly address the 35\% share of net users involved in higher education.  Additionally, Houghton-Mifflin's publishing products are clearly portable to the user friendly, multimedia-based distribution network provided by the Web.
\par
The benefits of such a system are numerous:
\begin{itemize}
\item{}tightly controlled, inexpensive advertising: accessible globally
\item{}complete information on available texts: up to entire text; supplementary information in any format
\item{}targetting professors: able to access system 24 hrs/day; low (no) pressure browsing, instantly recieve desired textbook samples; complex searches on specific subjects; quick responses from sales representatives
\item{}direct feedback from customers via imbedded email
\item{}relieve pressure on sales representatives: higher efficiency; additional link to customers
\item{}reduced costs: fewer mailings catalogs, and samples; smaller inventories
\item{}possibility of creating on-demand custom texts
\item{}Early participants viewed as technological leader
\end{itemize}


\subsection{System Purpose}
The purpose of the WWW server proposed by {\em net.Genesis} for Houghton Mifflin's College Division is:
\begin{itemize}
\item{}To increase the effectiveness of Houghton Mifflin's current marketing efforts by providing an additional distribution channel for brochures and product information.
\item{}To gather valuable market information.
\item{}To make a more direct connection between customers, sales reps, marketing managers, and sponsors.
\item{}To increase Houghton Mifflin's visibility and attract desirable authors through a demonstrated commitment to technology.
\item{}To enhance Houghton Mifflin's position among publisheres in the US college market.
\end{itemize}

\newpage
\section{Proposed System Design and Implementation Issues}
\subsection{Recommendations on Proposed System Design}

{\em net.Genesis} has reveiwed the proposed Product Description as specified in the RFP and can implement
 this system in the time-frame outlined in Section V. When referring to the system proposed in the RFP, t
he corresponding page number in RFP Appendix A appears in brackets.

\subsubsection{The College Division Home Page} The College Division Home Page is the first page the usersees, and, therefore, is the most important page of the system.  The design as specified in the RFP could
 benefit by the addition of one item:  a link on the Houghton Mifflin College Division title logo that po
ints to more information about the College Division.  This link would include information about the Colle
ge Division's history, mission, and possibly a FAQ (listing of Frequently Asked Questions).

\subsubsection{Catalog}

The first page of the Catalog [2-3] has a linked index of various disciplines.  The top of this page is a
n excellent place to implement a keyword search.  After clicking on 'search for a specific book', the user would see a search form that can freely search the entire database.  Potential searches would include any boolean combination of title, author, subject, and keyword.  When a query is submitted, the user willreceive listings of the different matches to the search and be provided with links to the corresponding information.
\par
After choosing a specific discipline, the user is presented with a more specific list of subjects withinthe desired discipline [4].  Here, the user should again have the option to conduct a search.  Also, here
 and throughout the entire system, we propose the addition of another 'action icon' that will take the user back one level.  For example, here, the 'back' icon would take the user from the specific discipline page [4] to the Catalog [2-3].  This is proposed for the user's convenience, for some versions of Mosaic do not have easy access to the 'Back' function.
\par
After choosing a specific discipline, the user will see the resulting list of titles in that area [5].  This title list could potentially be very large.  Therefore, the system shoudl have the 'action icons' atthe top of the page.  The 'back' icon should accordingly be among these icons.  Also, the option for a database search would be presented.

\subsection*{General Issues related to the online catalog}

\paragraph{Entry of book information into the server}  Updating the contents of the catalog can be accomplished in two ways:
\begin{itemize}
\item{}Enter the majority of the necessary server information (all data pertaining to a specific text) in
to the database to allow a custom converter to read the contents of the database and automatically update
 the HTTP server as necessary.

\item{}Preferred: Enter all necessary data on a new text into a custom application to be licensed from {\em net.Genesis}.  The custom application automatically updates the HTTP server.
\end{itemize}

\paragraph{Use of Multimedia}

Distribution of video in the form of MPEG files is proposed but caution is advised.  Quality of MPEG file
s can be low depending on the contents and the method used to obtain them.  Since the impression createdby low quality video is generally assumed to reflect the nature of the server, caution should be exercise
d in selecting and preparing these video files.  Note also that MPEG players are not real-time synchroniz
ed, meaning that a 1 minute video clip on a medium performance workstation will run much slower (and be u
npleasing) on an average PC and much faster on a high-end engineering workstation.  Furthermore, MPEG fil
es tend to be large, especially if they are of high quality.  An MPEG file lasting 1 minute played at its
 intended speed occupy over 1.7MB of memory.  Transfer of many of such files simultaneously would resultin saturation of the partial T1 outgoing line.  Problems are also created when such large volumes of data
 are transferred over low speed lines on the client's side.  A 1.7MB file transferred over a 56Kb/s linewould take approximately 9 minutes to download.  We therefore recommend that a sequence of smaller MPEG f
iles is implemented, as opposed to a single large file.
\par
Distribution of audio is more straightforward. Audio players are real-time synchronous, and while the size of high quality files is still large, they are  smaller than MPEGs of corresponding time. A 1 minute au
dio file would take on the order of 2.5 minutes to transfer over a 56Kb/s line.

\paragraph{Order Forms}

Currently, the secure encryption of data within Mosaic is problematic.  This applies specifically to sens
itive financial information, such as user credit card numbers.  Adequate security requires the use of a public key encryption algorithm.  The only widely available is encryption application is PGP, which uses the RSA algorythm.  Unfortunately, the Federal goverment has imposed a restriction on the export of this software.  Furthermore, use of PGP would be inconvenient to system users. The issue of data security is aprimary concern for the entire on-line community.  A great deal of research is currently occuring in this area.  The following  are net.Genesis' present proposed solutions:
\par
\begin{itemize}
\item{}Give the option to the user to not use any protection. Thousands of users perform unprotected remote login procedures on a daily basis. During such a procedure the username and password is transmitted over the net without  protection. Retrieving such information from the net is sufficiently hard that most users are not overly concerned about security risks.

\item{}Use PGP software to encrypt the credit card information. If PGP is not available at the current site, confirm the location of the site and allow the client computer to download the software from the Houghton Miflin site. This is inconvenient and might require client PGP installation by the site administrator (as opposed to the client user).

\item{}Submit the order form without any credit card information. When the order form is received a sales representative would call the user to confirm the order and obtain the necessary credit card information. This scenario requires a call for every submitted order form.

\item{}Preferred method: have the user submit a request for a Houghton Mifflin ordering account before an order can be submitted. This would involve a sales representative calling the user back to obtain a credit card number, an e-mail address, and then issue a unique account number to the user. From then on, theuser inputs the account number (and not a credit card number) when placing orders. Any order made to a particular account would automatically mail the order back the the user's predefined e-mail address.  In this scenario, in the event that an account number is stolen (electronically or by other means), the original client will immediately receive notice of false orders being placed to his account.
\end{itemize}
Any of the above security strategies can be implemented by {\em net.Genesis}.

\paragraph{Comment Card} The Comment Card will send a pre-formatted form to the Houghton Miflin server, which will in turn automatically mail it to the appropriate sales representatives as well as archive the comments.

\paragraph{Software Demonstrations} The Software Demonstrations would run on the Houghton Mifflin server.  {\em net.Genesis} can provide such functionality during the initial implemenation, but, due to server load considerations, it is recommended to defer this feature until the system has expanded to more than asingle server.

\paragraph{Conferencing} The Conferencing area of the system would provide an interactive ``chat'' room (or rooms) where users could talk with textbook authors and representatives from Houghton Mifflin. {\em net.Genesis} presently possesses software for on-line conferencing that would be modified for use by Houghton Mifflin.

\paragraph{News Service} We recommend that the News Service be based on a mailing-list system.  This configuration would allow full control of access to this service; all clients would have read access to its contents, but Houghton Mifflin would dictate who updates and revises the service.  An archiving system could be set up for such a service.  {\em net.Genesis} can also implement other newservice structures.


\subsubsection{Newsletter}

The Newsletter is perhaps the most interesting part of the system for users not specifically interested in texts.  The page provides useful links to high-interest information regarding the server, Houghton Mifflin College Division, and Education.  The Special Bonus concept is an exciting way to attract users to the system, but we advise extreme care in selecting the shareware/freeware to be distributed through this potentially very popular item. Also, we would include another 'action icon' (similar to those in the catalog) that will take the user back one level.  Here, the icon would take the user back to the Home Page.

\subsubsection{Internet Resources}
The Internet Resources is a useful mirror of information contained elsewhere.  We want the Houghton Miflin College Division WWW system to be viewed as a complete educational resource publically available on the Web.  Through including links to as many other related systems as possible (which perhaps also provide links back), the system will become tightly integrated with existing educational information sites.

\subsubsection{How To Use This Server}
This page provides a simple ``how to navigate the system'' instructions list along with a general outline of the system layout.  Important among these are the directions to disable the automatic loading of in-l
ine images, which greatly affects the response time of Mosaic clients running at low (less than 56 Kb/s)speeds.
\par

\subsection{Additional Feedback Mechanisms}

Houghton Mifflin will be able to obtain extensive marketing information.  {\em net.Genesis} will providecustom logging software to log accesses of users to the system.  The logging software will compile data on the number of accesses, location of users, and specific sites the user accessed.  This software will provide key information summarizing exactly how, when, and by whom the system is accessed.  This summary data will reveal general system trends, thus illustrating potential marketing directions as well as indirect suggestions for improving the system.  For example, if many professors from a single school are accessing the server in a relatively short period of time, the sales representative in that region would be sent that information and respond accordingly.  Additionally, if a single book (or type of book) is being heavily accessed, then the marketing and sales staffs might decide to further push that text with other means of advertising.
\par
The logging software provided by {\em net.Genesis} is the exclusive property of {\em net.Genesis} and will remain so.  Houghton Mifflin will be given a derivative license to the modifications made to the {\em net.Genesis} logging software.

\subsection{Technology Transfer}

{\em net.Genesis} will provide extensive documentation regarding all work completed.  This will provide smooth technology transfer to Houghton Mifflin's staff.  Documentation will be provided for all key implementation phases.  The documentation will be generated by the individual responsible for each task, and then reviewed by {\em net.Genesis} staff.  The resulting documentation will then be transferred to the appropriate Houghton Mifflin staff for thorough revie .  Documentation will be generated and reviewed throughout the project's duration.  In addition, several major documents will serve as key milestones for the project. net.Genesis acknowledges that comprhensive documentation will be vital to transferring system maintenance to the Houghton Mifflin technical staff.
\par
Training will also be an integral aspect of the {\em net.Genesis} implementation.  {\em net.Genesis} will provide extensive training in all system aspects, including both technical and non-technical staff.  Training will be conducted early in the project on the Server setup and HTTP installation.  The training sessions will be conducted by Matthew Gray and George Hadjiyiannis.  The training session will primarily befor technical staff who will be involved in maintaining the system's hardware.
\par
Further training for the technical staff will be done nearer to the end of the project.  The topics to be covered include the customized software that will have been written for Houghton Mifflin.  If desired by the technical staff, Matthew Gray will provide an introductory seesion in PERL.  Also, net.Genesis willprovide a  session describing the complete system and the design choices made by the team.  Again, the bulk of the technical training will be done by Matthew Gray and George Hadjiyiannis.  Rajat Bhargava will also helping with this training.
\par
Non-technical training will be held in two different sessions during the project period.  Early in the project a basic class teaching HTML coding will be held.  This will teach non-technical staff how to create basic WWW pages.  The second training session, scheduled for week 9 of the project, will review maintaining and updating the complete working system.  At this training session users will be introduced to the system and its functionality.  An integral part of this training session will be the feedback from the attendees concerning ease of use, visual appeal, etc.  Craig Wisneski will be project coordinator for the training of non-technical staff
\par
{\em net.Genesis} deisres to keep the training training sessions two way; we believe that we can learn agreat deal about our implementation from the trainees as well as teach them a great deal about the subject matter.  The feedback from the training sessions be critical to improving the overall system look and feel.

\subsection{Server Set-up Implementation}

\subsubsection{Hardware Configuration}

{\em net.Genesis} proposes the current implementation to consist of a single SS5/70 Sparc unit. The unitwill be equipped with a 15" color monitor (for setup and control purposes), a DB25 Ethernet interface, 64 MB DRAM (to increase performance), 535MB SCSI interface as a local disk, two external 1.05GB SCSI disksfor the server data, tape backup unit for nightly backups and a UPS (uninterrupted power supply) to protect from power brownouts. The unit will be connected through a partial or full T1 connection to the Internet. It is recommended that this connection be kept distinct from the connection that Houghton Mifflin already uses for the rest of their system for two reasons:
\begin{itemize}
\item{Security:} If the server unit is compromised it will not affect the rest of the system.

\item{Load isolation:} The server connection is likely to become  very heavily loaded on occasion. To avoid slowing net access for the whole of Houghton Mifflin's system, it would be beneficial to keep this asa separate connection. Access to the rest of Houghton Mifflin's network will occur by indirecting through the Internet.
\end{itemize}
A fractional T1 is recommended for the following reasons (at 384 Kb/s):
\begin{itemize}
\item{}The server's capacity will be limited mostly by the ability to transmit data to the net. This will be especially true if heavy use of images, video and audio is made. T1 has more capacity than most other options

\item{Expandability:} A fractional T1 is a relatively low cost alternative to a full T1. As server demand rises, more bandwidth can be purchased with minimal additional costs to support the increased demand. This expansion can be done quickly and without much effort until the demand for bandwidth exceeds the maximum for T1. At 1.5Mb/s, the full T1 bandwidth is projected to outlast the unit serving it.
\end{itemize}
\par
Finally, the unit configuration was selected for the following reasons:
\begin{itemize}
\item{}The SS5/70 is the most cost effective high-end engineering workstation in its class. It performs only marginally lower than a SPARC 10 and costs substantially less.

\item{Flexibility:} The combination of a UNIX type operating system and large number of peripherals makes the SS5/70 a very flexible station. Compatibility with any UNIX applications is easy to achieve and thelarge line of SUN peripherals makes it possible to adapt the system to the client's precise needs. It also has available a number of upgrade options, such as a full expansion to a SPARC 20 machine.

\item{Many useful built-in features:} it comes with a standard SCSI hard disk of 535MB which can easily be used to contain all the system files, software, applications, and user accounts. The SCSI interface can also be used to connect to external disks to increase the capacity to that required to hold all the catalog information.

\item{}The extra memory is considered necessary for performance reasons. The server will be transferringlarge amounts of data to and from the hard disks. To make this process efficient, a large memory size isrequired.

\item{External disks:} The capacity of the internal SCSI drive is insufficient to hold the vast volume of data required for the catalog. These will be stored on two external SCSI disks of a total of four timesthe capacity of the internal disk. These are projected to be of sufficient capacity for at least 2 years. Due to the small physical size of the SS5/70 it will not be possible to use internal instead of external disks.

\item{Tape Backup unit:} the system as described above will be capable to back up the contents of its hard disks over the network to any existing tape unit. However, given the fact that the filesystem for the server will be much larger than the filesystem used for the rest of the system, it is preferable to either move that unit to the server or purchase a new one. Backups are necessary to guarantee that the system will survive!

\item{UPS:} Power in large buildings is usually not reliable enough for vital computer systems systems. Many small power outages (on the order of a few seconds) occur regularly. A UPS will guarantee that the server will survive such outages.
\end{itemize}

\subsubsection{Software Configuration}

The basic platform of software over which the server will be built will be the Solaris Operating System and the Sun INS networking software.  On the platform, {\em net.Genesis} will install FTP and Gopher servers and the HTTP server.  More custom software will be installed to allow the services to be provided by the HTTP server.  Some this software will be licensed from {\em net.Genesis}.  Software in this category includes, but is not limited to, the conferencing software, the HTML editors, the HTML converters, auto-reply systems, and logging software.  The remaining software will be tailored on site to interface betweenthe licensed software and the existing Houghton Mifflin systems.  All software will be designed in independent modules facilitating easy expansion and modification should the need arise.  On-line documentationwill be provided for most of the software and will be incorporated into existing on-line documentation.


\newpage
\section{Implementation \& Deliverables}
An itemized list of tasks, divided by phases, has been included as Appendix A.

\subsection{Requirements Document}

Upon initiation of the project, one of the first tasks {\em net.Genesis} will undertake is the development of a requirements document.  The document, to be co-produced with key Houghton Mifflin participants in the project, will specify the exact definition of the system to be developed by {\em net.Genesis}.  The definition will specify deliverables and milestones for the project.  The requirements document will be signed by key executives from both parties.  Upon completion of the document {\em net.Genesis} reserves the right to reevaluate the price structure should the definition of the project change from the RFP/Proposal until then.  However, only a timetable change of greater than 10\% will warrant a material change in the price.


\subsection{Project Phases}

\subsubsection*{Server Setup Phase}

A workstation will be obtained and configured on site.  All necessary software will be installed, including NFS, the web server, and necessary UNIX utilities.
A file system for the HTTP server data (mostly the catalog
information) will be created. At the same time, accounts for the
Houghton Mifflin technical staff and the {\em net.Genesis} staff will be
created and access to the unit over the network will be provided (for
testing purposes). An NFS mount point connecting the unit's file
system to that of the rest of the Houghton Mifflin system (including
the database) will be established.
\par
\vspace{.1in}
{\bf Deliverables}
\begin{itemize}
\item{Server configured}
\item{Web server} and other software installed
\item{Accounts Created} 
\item{NFS mount point established}
\end{itemize}
\subsubsection*{Software Creation and Book Catalog Phase}

We will evaluate Houghton Mifflin's existing database and will implement necessary software to convert the available online information into hypertext format for use on the Web server.  A hypertext document heierarchy will be established for the book catalog and implemented in the conversion software.  A search engine interface to the book catalog will be implemented including an interface via the Web server.  Any further documents and pages to be presented on the Web server will be converted to HTML.  Additionally, log analysis software will be provided to examine server usage patterns and growth and conferencing software will be provided to allow MUD-like interaction on the system.  Full documentation on all conversion software will be provided.
\par
\vspace{.1in}
{\bf Deliverables}
\begin{itemize}
\item{Software package} for conversion from native DB format to HTML documents
\item{Software package} for easy modularization of hypertext documents
\item{Licencse} for log anylsis and conferencing software
\item{Search engine software}
\item{Complete conversion to HTML} of all necessary documents for the Web server
\item{Complete documentation}
\end{itemize}

\subsubsection*{Technical Training Phase}

Full training of technical staff will provided in all areas required for Web server maintenance, including server internal software, HTML and HTTP specifications, and all conversion software being provided.  Specific technical training will be
provided for the licensed software including modifications. Also,
training in the techniques and programming languages used to create
the custom software (software developed on site) can be included.
Reasonable technical knowledge and familiarity with basic programming
techniques and languages will be assumed.
\par
\vspace{.1in}
{\bf Deliverables}
\begin{itemize}
\item{Technical Staff Training Seminars}
\item{Technical Staff documentation}
\end{itemize}

\subsubsection*{Non-Technical Training Phase}

Non-technical staff will be familiarized with usage of the web server, performing updates on existing documents, and in the basics of writing  hypertext documents.  Use of application programs for catalog update, conferencing software, and other related systems will be covered. Also, the basics of HTML can be overviewed.

\par
\vspace{.1in}
{\bf Deliverables}
\begin{itemize}
\item{Non Technical Staff Training Seminars}
\item{Non Technical Documentation}
\end{itemize}

\subsubsection*{Support Phase}

{\em net.Genesis} will be providing support after the completion of the
project. After product release, pointers will be established to the
server from a variety of locations such as USENET groups, other HTTP
sites, marketing information and other publicly accessible sites. This will make the server widely known. {\em net.Genesis}
will also provide maintenance service which will include, but not be
limited to, help on modifications, expansion, repairs and upgrades.
Such service is included in the current contract for a period of 3
months up to a maximum of 200 hours.

\vspace{.1in}
{\bf Deliverables}
\begin{itemize}
\item{Publication of Server Location}
\item{Assistance on Modifications, Expansion, Upgrades and Repairs}
\end{itemize}


\subsection{Gantt Chart}
Key Milestones as listed are:
\begin{itemize}
\item{}Requirements Document
\item{}Fully Configured Server (including HTTP installation)
\item{}Training of Technical Staff in Server Internal Software and HTTP
\item{}Specifications Document for Book Catalog System
\item{}Fully Functional HTML Converters
\item{}Fully Functional Search Engine
\item{}Customized Log Analysis and Conferencing Software
\item{}Operational Server with Book Catalog and Features
\item{}Completion of Feedback and Updating of Server and Catalog
\item{}Operational FTP/Gopher Mirror Sites
\item{}Final Release of WWW Server
\end{itemize}
\newpage
\section{Intellectual Property Rights}

\subsection{Rights to Project Information/Classified Material}

All reports, documents, instruments, data, or material which are received by {\em net.Genesis} from Houghton Mifflin or developed by {\em net.Genesis} in connection to the services provided under this agreement, except those under derivative license, are, and will continue to be, the property of Houghton Mifflin and will not be divulged, distributed or released to any third party without the consent of Houghton Mifflin except as may be required by order of any Court of competent jurisdiction.  All software material and documentation created by {\em net.Genesis} prior to work in conjunction with Houghton Mifflin will continue to be the exclusive rights of the creator, {\em net.Genesis}.  Houghton Mifflin shall be granted a derivative license for modifications done at Houghton Mifflin while using software code priorly developed by {\em net.Genesis}.  The derivative license will allow Houghton Mifflin the use and modification of the derivative software.  Under no circumstances !
may Houghton Mifflin divulge, dist
ribute, or release the derivative work to any third party without the express written consent of {\em net.Genesis}.

\subsection{Software Provided as Derivative License to Houghton Mifflin}
\begin{itemize}
\item{}Log Analysis Software
\item{}Conferencing Software
\item{}Proprietary Search Engines
\item{}Automated Reply
\item{}Custom HTML Converters/Editors
\item{}WWW Server Utility Routines
\item{}Order Form Processing
\end{itemize}


\newpage
\section{Pricing}

\subsection{{\em net.Genesis} Corporation Costs}

\subsubsection{Contractor Costs}

Based upon the complexity and time required to implement the system proposed by {\em net.Genesis} to Houghton Mifflin, the final cost has been determined to be \$129,600.  {\em net.Genesis} recognizes the factthat Houghton Mifflin is our first customer and would like the price to reflect this fact.  We have provided Houghton Mifflin with a 20\% discount off of our projected rate of \$162,000.  Furthermore, the payment schedule has been defined to reward {\em net.Genesis} upon completion of key milestones.  This helps to minimize Houghton Mifflin's financial risks and also gives {\em net.Genesis} the incentive to provide a world class product on schedule.  The total cost for the system as proposed in this document, subject to review by the Requirements document, will be \$129,600.  The above price is subject to change pending outcome of the Requirements document.  Changes affecting the timetable in a material way will render the above figure void.
\par
\vspace{.2in}
\begin{tabular}{ll}
Total Cost of {\em net.Genesis} Contract Work&                  \$162,000\\
Less Houghton Mifflin Discount (20\%)&                  (\$32,400)\\
Total Cost&                     \$129,600\\
\end{tabular}
\par
\vspace{.2in}
Costs are based upon 50 man-hour work weeks for the life of the project (10 weeks).  200 man-hours of support of the system over a 3 month period beginning upon completion of the total project is included in the total cost the system over a 3 month period of time is included in the total cost.  If support beyond 200 man hours is desired additional charges of \$60/man-hour will be charged.  Further support options are outlined in the Support section below.
\par
{\bf Total Costs Include:}
\begin{itemize}
\item{}Comprehensive review of requirements and specifications
\item{}Server setup and integration
\item{}HTTP installation
\item{}FTP/Gopher installation
\item{}Lifetime licence for {\em net.Genesis} proprietary software
\begin{itemize}
\item{}HTML Editors/Converters
\item{}Conferencing software
\item{}Log Analysis software
\item{}Order form processing
\end{itemize}
\item{}Creation of custom World Wide Web pages
\item{}Integration of audio/video/graphic design into WWW pages
\item{}Training
\item{}Complete documentation of system
\item{}Technology transfer
\item{}Support and maintenance
\end{itemize}
\subsubsection{Itemized Cost by Phases}

\begin{tabular}{ll}
Initial Phase& \$13,900\\
Requirements Document\\
Server Setup and Test\\
Server Integration with LAN\\
HTTP Installation\\
Full Documentation\\
\\
Book Catalog Phase 1&    \$28,900\\
Evaluation/Planning/Design of System\\
Specification/Creation/Testing of Custom HTML Converters\\
Full Documentation\\
\\
Book Catalog Phase 2&    \$33,800\\
Spec/Creation/Test of\\
Search Engine/Conferencing/Log Analysis\\
Creation of Pages\\
Conversion and Quality Control of Data\\
Full Documentation\\
\\
Book Catalog Phase 3&    \$27,520\\
Brining server on-line\\
Feedback and updating of Server/Pages\\
FTP/Gopher Mirror Sites\\
Final Release of Server\\
Full Documentation\\
\\
Training&                \$15,880\\
Technical Training\\
Non-Technical Training\
\\
Support and Maintanence& \$9,600\\
200 man-hours of support\\
and maintenance for 3 months\\

\end{tabular}

\subsubsection{Training Costs}

On site training costs for the duration of the project have been included in the total cost.  Training during the project will include Houghton Mifflin's technical and non-technical staff.  Any off-site training is subject to additional contractor charges.  Expenses such as air travel, hotel, rental car, etc. will be paid by Houghton Mifflin if off-site training is requested.

\subsubsection{Support and Maintenance}
 After the 3 month support period has expired, Houghton Mifflin can obtain a service contract for the duration of 1 year for \$17,500.  The service contract will entitle Houghton Mifflin to 20 man-hours of support per month.  Additional service can be purchased on an hourly basis.  Phone/email correspandance willbe charged fees of \$70/man-hour.  On site support will be charged at \$100/man-hour.
{\em net.Genesis} fully understands that system downtime translates directly into compromised business oppurtunities, whether those be actual lost orders or loss of customer satisfaction.  Accordingly, {\em net.Genesis} pledges to provide complete, prompt service whenever it should be necessary.

\subsection{Project Fees and Expenses}

Project Costs above include only direct contractor fees.  Not included in the fees are any expenses {\em net.Genesis} incurs during the course of the project related to the project.  These may include, but arenot limited to, workstation rental, outside contract work regarding conversion of data, the procurement of any necessary documentation, and phone, mail, fax, copying exclusively related to the Houghton Mifflinproject.  Houghton Mifflin will be responsible for reimbursing {\em net.Genesis} for all direct project e
xpenses incurred to {\em net.Genesis}.

\subsection{Changes to Requirements Document during Project}

Changes made after the requirements document has been signed by both parties will be subject to additional charges.

\subsection{Hardware And Software Costs}

\begin{tabular}{ll}
{\bf Hardware Costs} & \\
SS5/70 SPARC workstation\\
(15" color monitor, CG3 Video Frame Buffer,\\
 16MB DRAM, 535MB SCSI Hard Disk)&      \$3,995\\
Additional 48MB DRAM&                           \$3,450\\
2x1.05GB SCSI External Expansion Disks&         \$2,500\\
5.0GB 4mm Tape Desktop Backup Unit&             \$1,600\\
\vspace{.1in}
Uninterruptible Power Supply&                   \$300\\
{\bf Software Costs}& \\
Solaris 2.3 Multi-user license&                 \$300\\
C compiler&                                     free\\
FTP/GOPHER&                                     free\\
{\em net.Genesis} software (derivative license)&                        included in contract\\
\end{tabular}

\subsection{Net connection Costs}

A full or partial T1 connection is recommended with the vendor providing nameservice:
\par
\begin{tabular}{llll}
Bandwidth&       Annual Fee&      Com. Routing&    Installation\\
\\
128 Kb/s&        \$12,550&                \$3,000&         \$14,950\\
384 Kb/s&        \$15,850&                \$3,500&         \$14,950\\
768 Kb/s&        \$20,800&                \$4,500&         \$14,950\\
T1(1.54 Mb/s)&   \$27,400&                \$6,500&         \$14,950\\
\end{tabular}

Installation costs may vary depending on how much of the installation the client is willing to do for themselves.

\subsection{Payment Schedule}

Payments to {\em net.Genesis} shall be payable in installments according to key milestones in the implementation process.  Final dates will be determined upon completion of the Requirements Document, which will be signed by key executives of both companies.

\begin{tabular}{lll}
Project Launch&                  20\%&    \$25,920\\
\\
Milestone 1&                     10\%&    \$12,960\\
Requirements Document& \\
Server Setup& \\
Training for Server/HTTP& \\
\\
Milestone 2&                     10\%&    \$12,960\\
Creation of periphery pages& \\
Creation of custom editors (tested)& \\
\\
Milestone 3&                     30\%&    \$38,880\\
Completion of all pages& \\
Completion of search engine, conference feature,\\
logging software, usenet group access& \\
Bring WWW Server up and on line\\
(ready for internal introduction)& \\
\\
Milestone 4&                     30\%&    \$38,880\\
FTP/Gopher Mirror Sites& \\
Final Release (to net)& \\
\\
Total & & \$129,600\\
\end{tabular}

Terms will be as follows.  Invoices will be delivered to Houghton Mifflin upon the completion of the milestones outlined in this document and specified in the requirements document.  Houghton Mifflin will have30 days to submit payment.  A finance charge to 1.5\% per month will be applied to all overdue invoices.

\subsection{Termination}

The contract may be terminated by Houghton Mifflin, with or without cause, immediately upon written notice and the payment of a termination fee of 20\% of total project fees or the remaining amount of the total project fee, whichever is the lesser.  The remaining project fee is equal to the total agreed project fee less outstanding and paid invoices.  Expenses will be paid as incurred separate from project fees.

\newpage
\appendix
\section{Itemization of Tasks}


\subsection{Server Set-up}

\begin{itemize}
\item{}Obtain workstation and internet connection
\item{}Determine logistical questions about server
\item{}Determine optimal integration scheme with Houghton Mifflin LAN
\item{}Determine adequate level of security for different phases of implentation
\item{}Configure of OS
\item{}Configure of file system
\item{}Create unix accounts
\item{}Install of NFS software (and integration with current LAN)
\item{}Install of logical partitions and logical disks
\item{}Install internet access
\item{}Install LAN access
\item{}Install HTTP
\item{}Install other binaries
\item{}Testing of server (security)
\item{}Full Documentation
\end{itemize}

\subsection{Software Creation/Book Catalog Phase}

\begin{itemize}
\item{}Evaluate Houghton Mifflin's current database 
\item{}Evaluate file formats
\item{}Evaluate state of audio/video
\item{}Find high quality quicktime to MPEG converter
\item{}Evaluate graphic design needs
\item{}Evaluate Lotus Notes email system for Replies
\item{}Determine security features necessary
\item{}Determine file structure
\item{}Determine search engine features
\item{}Determine process of conversion of audio/video files 
\item{}Quality control process for audio/video
\item{}Determine necessary editors/converters and write specification
\item{}Create custom HTML converters
\item{}Convert audio/video files
\item{}Quality control
\item{}Create GIFs
\item{}Create icons from graphic design work
\item{}Create actual book pages
\item{}Create periphery pages
\item{}Create main menu pages
\item{}Create search engine
\item{}Create conference feature
\item{}Create usenet functionality
\item{}Create logging programs
\item{}Test all converters
\item{}Exhaustive tests to ensure correct conversion
\item{}Test pages, search engine
\item{}Test from remote sites
\item{}Full documentation
\item{}Feedback from Houghton Mifflin
\end{itemize}

\subsection{Technical Training}

\begin{itemize}
\item{}Documentation management
\item{}Creation of training materials for mini-courses
\item{}Training sessions
\item{}HTML
\item{}HTTP
\item{}Server setup and mantainance
\item{}Script/Converter
\end{itemize}

\subsection{Non-Technical Training}


\begin{itemize}
\item{}Development of Training Materials for Mini Courses
\item{}HTML
\item{}Updating System
\item{}Use of System
\end{itemize}

\subsection{Support}

\begin{itemize}
\item{}Hel Houghton Mifflin technical and non-technical staff with questions and problems regarding work completed by {\em net.Genesis}
\item{}Product release
\begin{itemize}
\item{Internet} announcements
\item{Usenet} announcements
\item{}Incorporation into Marketing Information
\end{itemize}
\end{itemize}

\section{Resumes}
\end{document}

