Loading...
HomeMy WebLinkAbout39-02 RESOLUTION2 of 10 a CITY OF FAYICITEVILLI: WEB SITE Co, IRAcr • L Change(s) to the Project Design Document after approval by CLIENT. 2of10 (5) CLIENT agrees to provide to IFWORLD with all data, specifications, and information, including text, graphic content, and any media which is to be included in CLIENT's web site by IFWORLD within a reasonable time after and in no event more than seventy-five (75) days from the date of signing this Agreement. (6) CLIENT understands and agrees that work will not commence until IFWORLD, in its sole discretion, determines that it has received data, specifications, and information, including text, graphic content, and any media from CLIENT sufficient for it to undertake the Design Project. (7) Should CLIENT fail to provide the data, specifications, and information, including text, graphic content, and any media, required pursuant to Paragraph five (5), IFWORLD shall have the right to declare the entire amount due IFWORLD under this agreement immediately due and payable. In that event, IFWORLD shall be under no obligation to complete its performance contemplated hereunder until such balance is paid in full and CLIENT has furnished such data, specifications, and information, including text, graphic content, and any media, sufficient, as determined in IFWORLD's sole discretion, for IFWORLD to complete the Project Design. (8) CLIENT agrees that publication of the web site will not occur until IFWORLD has been paid in full under the Design and Implementation Schedule and Budget and written authorization from CLIENT has been received by 1FWORLD. GENERAI, CONDITIONS: (9) IFWORLD retains the right to suspend any given Schedule due to the delay by or tardiness on the part of CLIENT when IFWORLD must await a necessary approval by CLIENT at a step or stage of the process before continuing. In that event, IFWORLD will resume work as soon as practicable after CLIENT'S response has been received. (10) Except for IFWORLD Proprietary Software as set forth in paragraph 14, all other materials, and products, and modifications developed or prepared by IFWORLD under this agreement, including without limitation to forms, images and text viewable on the Internet, any HTML elements relating thereto, and software, including the Deliverables and any Updates thereto, are the property of the CLIENT and all right and title and interest therein shall vest in CLIENT and shall be deemed to be a "work made for hire" under the United States copyright law and made in the course of this Agreement. CLIENT acknowledges IFWORLD to be the author of such web site but will limit the identification to HTML, remark codes embedded in the Page Source of the Home Page. .17 IIS/JS(D INC 3 of 10 t CITY OF FAYETFEVILLE Mill SITF CONTRACT • 3of10 (1 I) The IFWORLD Proprietary Software as set forth in paragraph 14 is and shall remain the property of IFWORLD. IFWORI,D grants to CLIENT a perpetual, irrevocable, non-exclusive, license for CLIENT or its agents to use and copy for backup purposes the IFWORLD Proprietary Software in conjunction with the operation and maintenance of the CLIENT Site. (12) CLIENT represents and covenants that it is the owner, assignee, or licensee of all elements of the web site supplied by it to IFWORLD, including text, graphics, photos, designs, trademarks, or other artwork or materials, or has otherwise been granted perniission to utilize the same by the owner or owners thereof, and agrees to indemnify and hold harmless IFWORLD from any and all claims or suits arising from the use of such elements furnished by the CLIENT, such to include reasonable attorney fees incurred by IFWORLD in defending itself and pursuing performance of this provision from CLIENT. (13) IFWORLD agrees and acknowledges that CLIENT retains exclusive rights of title and ownership over all copyrights, trademarks, or other proprietary rights associated with, pertaining or referring to, or otherwise representative of THE CITY OF FAYETTEV ILLE, its committees, departments, divisions, governing body, or other officials; including but not limited to any and all color schemes, diagrams, drawings, graphic designs, insignia, letter or number tents, logos, mottos, photographs, seals, sketches, ctc., which might be or are subject to the intellectual property rights of CLIENT. If so requested, 1FWORLD will include such mutually agreed upon forms of notice on the website to protect copyrights, trademarks and other proprietary infomtation. (14) CLIENT agrees and acknowledges that IFWORLD retains the exclusive rights of title and ownership over all IFWORLD Proprietary Software which includes all PHP Coding, Java Script and Database Structure utilized in the building, operation, maintenance of the website and remains the exclusive rights of title and ownership of IFWORLD. (15) Except for the express warranty provided to the City of Fayetteville in paragraph (17), IFWORLD makes no further warranties, express or implied. IFWORLD Inc. makes NO WARRANTY OF MERCHANTABILITY and NO WARRANTY OF FITNFSS (16) If IFWORLD Inc. is found liable for breaching its warranty in paragraph (17), the damages awarded against IFWORLD Inc. may not exceed the total amount paid by the City of Fayetteville to IFWORLD Inc. pursuant to this contract. (17) The Warranty covers the following terms and conditions for a period of one year from the time the web site is published live. IFWORLD Inc. (Warrantor) warrants to the City of Fayetteville (Warrantee) that the products and services provided to the Warrantee pursuant to any agreement for the City of Fayetteville Web Site, to include all programming code, and software, shall be free of defects for the type of goods and services provided. In the event of a defect, malfunction, or other failure of the product not caused by any misuse or damage to the product while in the possession of the Warrantee, or not caused by changes to software, database structure, technical configuration or operations of the Warrantee, Warrantor shall repair or replace such product within a reasonable time of notice of such problem, all at Warrantor's sole 1t vrpe iD 'vC 4 of 10 • CITY of FAYETTEVILLE WEB SITE COST RAC I' • cost and expense. This warranty specifically covers labor, and service. 4 of 10 (18) This agreement and the continuing obligations set forth herein shall survive and continue beyond the payment of the monies due hereunder from CLIENT to 'WORLD and the construction of the web site by IFWORLD, and such continuing obligations may be enforced by either party against the other should a breach of such occur or be imminent. (19) To the extent that any provision herein might he declared invalid or unenforceable by a Court of competent jurisdiction, the remainder of this agreement shall remain in full force and effect, including the continuing obligations hereunder. (20) This agreement shall, regardless of where executed, be interpreted, construed and enforced in accordance with and subject to the laws of the State of Arkansas, and venue for any action hereunder shall lie in Washington County, Arkansas. (21) The documents which comprise this contract between the CLIENT and IFWORLD consist of this contract and the following documents, which are incorporated herein by reference as if set forth word for word: a. Bid form identified as REQUEST FOR PROPOSALS (RFP 10-01) issued September 21, 2001, for web site development and hosting assistance with all specifications, conditions, and requirements included therein; b. IFWORLD'S proposal and all supporting documents and correspondence submitted by IFWORLD on or about October 19, 2001, in response to the REQUEST FOR PROPOSALS (RFP 10-01) issued September 21, 2001. (22) THIS AGREEMENT constitutes the complete agreement between the parties hereto for the services covered herein, superceding any and all prior communications and agreements between the parties with respect to these services, and shall be construed and interpreted as a separate agreement from any and all other agreements which might now, or later, exist between the parties, UNLESS it he incorporated by specific reference into such other agreements. This IF wUe ID INC 5 of 10 a Cin of I:AYH-IFVILLE WEB SITE CONTRACT • 5 of 10 agreement shall not be binding upon IFWORLD until accepted by a Corporate Representative other than the signing sales representative. WITNESS OUR hands on the date first above written: CLIENT ca Authorized Binding signature Title: By Date -3// 3 IFWORLD Mat Authorized Binding signature Title it'S' r1 .7e4nrt'/JVe44445 ACCEPTED by IFWORLD Inc on the date first above written. IIWOR :D INC G of 10 • CITY OF FAN trrr, II. u: WEB Sin: CONTRACT Appendix A Project Process DESIGN STAGE Establish every element of every page (visually and textually): • 1. Site Map: Gof10 Design Team develops the site map based on the project requirements (i.e. Requirements Document section of the Design Contract that lists the functional requirements of the project) and project research to plan site structure and organization. 2. Schematics Document: • Design Team visually describes each page with simple schematics following the outline of the site map. 3. Functional Specification Document: Design Team develops the functional specification document by describing how each page functions, closely following the schematics document. The contents of this document arc as follows: • A full textual description of the site including all design, functional, and textual details of every page. • The final implementation schedule and budget. • Content appendix. • Script and textual Storyboard appendix for animations or movies. 4. Graphic Design Comps: Graphic Design develops comprehensive graphic designs using the functional specification as a guide. Graphic Design also creates visual storyboards for any animation or movie content. 5. Design Specifications Document: Design Team creates a style guide outlining all design specifications that are to be followed throughout the Implementation Stage. (j7 IWO@ J INC 7 of 10 aGin' oFFAY rrEvIIF.WEB SireCONTRACT 6. Project Design Document: Project Design Document is compiled, consisting of: • 7of10 • Site Map • Schematics Document • Functional Specification Document including finalized versions of the content and script and textual storyboard appendices • Graphic Desigm Comps including storyboards • Design Specifications Document Project Design Document is delivered, fulfilling the Design Contract. IMPLEMENTATION STAGE Project design is executed: 7. Project Implementation: Design Team carries out project implementation, closely following the project design document. 8. Walk-through: A walk-through of the site is done to review it, making sure that expectations are met, and any adjustments to the site are brought to attention of IFWORLD by CLIENT. 9. Publish Site: Site goes live. 10. Wrap-up: Wrap-up meeting to review the project. Feedback is given on the project and the project process what worked and what didn't. IFWORLD will present Site Maintenance Plan for CI.IENT's consideration. $ of 10 iii Ci FY OF F,svr::-r::v:LLE W1113 SI rr. Coxi it,u:r Appendix B Project Requirements 8 of ID Terminology Note: The Content Management System we have outlined divides each page into different parts and is perfect for the type of system that has been requested. The names of these parts are used throughout the feature descriptions below. For easy reference, the following are definitions of each part Persistent Areas • Piece (or pieces) of a page that are static throughout the site While the individual persistent piece might change slightly (e.g. an expanding navigation for secondary level pages'), the piece is seen on every page of the site. The page elements that this usually includes are the page header. footer, and navigation. Content Areas - If an element on a page is not one of the Persistent Areas. then it is considered one of the Content Areas of that page. It is the piece (or pieces) of a page that 'mikes that page unique to the site. It usually has dynamic content and/or a varied layout. Each content area is created from a page type. Page Types Defines which content types are displayed and where they are located within the content area. Content Types - The basic building block of a page. The individual elements within a content area. Ecanples: copy. lists, pictures. links, forms Core Features Overall Layout and Design The creation and development of all page elements, which are persistent across the entire site. This includes, but is not limited to. the page header, footer and navigation. Emphasis is placed on ease of use and consistency of layout and user interface. The navigation and site structure will be extensively evaluated, focusing on maximizing the user's ability to find the information they are looking for. Layout and Design of Page Types fhe creation and development of all content areas within each pace throughout the site. Each page type listed below is designed once and then registered with the Content Management System so it can be used multiple times throughout the site. Listed below are the foreseen page types for this project: • Main Page • Top Level Page • Site Map • Search Results Page • News Ileadlines Page • News Story Page Secondary Level Pages: • General Copy • General Copy with Image 9 of 10 _ Cin OF FAYIn-rEVII.LE WEB SITE CONTRACT • Multiple Sectioned Document (Reports) • Copy with Archive List • Calendar - Calendar View • Calendar - Events List View • Description & Contact Information • Mailing List Subscription Form • PDF Display • Large Image, and Description • Large Image With Linked Image Map • Multiple Images and Descriptions • Form • Bullcted List • Numbered List • Tabled List • FAQ • 9of10 Note: These page types cover every type of page that was listed in the REP. This goes above and beyond the requested three variations of level two pages because of efficiency, usability, and necessity. Because the projected pages have not been finalized. the above list is subject to change. (23 — 30 page types) Site Search The Site Search performs a keyword search throughout the content of the entire site. Advanced searching methods will also he used for searches of narrower scope and greater complexity. Content Management System The Content Management System handles the placing of content types (copy, calendars, forms, lists, photographs, etc.) into a predetermined page type (listed in Layout and Design of Page Types above) through the administrative section of the website. The Content Management System has the following features: Content / Mailing List Management Features • Navigation Management • Content Preview Before Publishing Live • Content Change History • Graphic File Upload • PDF File Upload • Administrative User Management • Assigned Permission Levels II WOR 10 INC • 10 of 10 CITY OF FAY r:TTTtvn.t.e WEB SIFE CONTRACT Aer Optional Features: Navigation Evaluation • 10 of 10 IFWORLD will conduct a concentrated effort to review the needs of all possible users of the web site and design a web site and navigation scheme that best facilitates an intuitive, consistent, and informative experience. Each page of the proposed navigation will be evaluated along these lines to examine its necessity, placement, and need for improvement. All Events Calendar An Al! Events Calendar that would show the city events across all departments. This calendar is a virtual aggregate of the other calendars and will not have an administrative section. Page Type Builder This is a module for the Content Management System that allows administrators the ability to create new page types. This lets an administrator layout a new type of page and save it so that it can be used throughout the site. IF WORID INC F 0. March 11, 2002 IFWORLD, Inc. ATTN• Ms Shara Fisher 4058 N. College Avenue, Suite 250 Fayetteville, AR 72703 Dear IFWORLD, Inc.: Thank you for agreeing to provide us a one-year warranty in paragraph 17. However, in the rush, paragraph 15 was left in your proposed contract. This paragraph is contradictory to the warranty paragraph (17) in that paragraph (15) states: IFWORLD MAKES NO WARRANTIES, EXPRESS OR IMPLIED .. " In order to provide ONLY the warranty given in paragraph (17) and excluding other implied warranties your paragraph (15) could say: "(15) Except for the express warranty provided to the City of Fayetteville in paragraph (17), IFWORLD makes no further warranties, express or implied. IFWORLD, Inc. makes NO WARRANTY OF MERCHANTABILITY and NO WARRANTY OF FITNESS." I had informed our representative that paragraph 16 was unacceptable and had to be deleted. If you wish to limit your • • possible exposure if you breach your warranty in paragraph (17), then I will recommend the Mayor sign your contract with the following language in paragraph 16 "(16) If IFWORLD, Inc. is found liable for breaching its warranty in paragraph (17), the damages awarded against IFWORLD, Inc may not exceed the total amount paid by the City of Fayetteville to IFWORLD, Inc. pursuant to this contract." As currently written, your paragraph (16) would allow you to accept full payment from us, do nothing at all, and keep 95% of the contract price. Obviously, you would not act in such a manner, but as City Attorney, I cannot allow us to forfeit our right to require contractors to fulfill their contracts with the City. Please correct paragraphs (15) and (16) and return for the Mayor's signature. KW/lh cc: Dan Coody, Mayor Kevin Springer, Budget Analyst With kindest regards, Kit Williams Fayetteville City Attorney • 1of10 • CRY OF FAYETTEVILLE WEB SMi CONTRACT • 1of1O As 31-4 WEB SITE DESIGN & CONSTRUCTION AGREEMENT ORIGINAL THIS AGREEMENT is made and entered into this 5th day of March, 2002 by and betw en IFWORLD INC. (hereafter "IFWORLD") and THE CITY OF FAYETTEVILLE ereafter "CLIENT"), subject to the terms and conditions more specifically set forth herein DESIGN STAGE (1) NT wishes to engage IFWORLD and IFWORLD agrees to p orm the services which are reaso ble and necessary to create a website for CLIENT in acco I ance with the Project Requireme set forth in Appendix B, attached hereto and made p. hereof (2) CLIENT agr- < to pay and IFWORLD agrees to accept the .tal sum of the Core Features and the initialed op 'nal items below as consideration for th-. ervices to be performed in the Design & Implementa on stages as set forth in Appendix Core Features Design & Im. ementation $85 .80 The total sum of the Core Featuris to be payable a• follows: $ "'Nothing*" upon signing this A eement (3) PAYMENT. Professional Services Fees incurred on a time and material basis. If cha RFP are needed, a change order signed by Services provided in excess of the hours s The Remaining Balance of the Impleme and payable upon presentation of the w Design will be invoiced monthly for services as to the hours for Professional Services stated in ies will be required. Any Professional charged at the unit price stated in the RFP. e billed to CLIENT immediately due th p ed will ation Cost t site. (4) CLIENT agrees that any of the fol owing actions must be . uthorized by CLIENT, acknowledges that the same will cau e a change in both the co and time -frame for the Project Design and Implementation, and a_. ees to pay for any increased •..sts, to be billed as set forth above, due to the following action a. Change(s) to the Project Requ ements after signing this Agreement. b. Change(s) to the Site Map . ` er approval by CLIENT. c. Change(s) to the Schemaf s Document after approval by CLIENT. d. Change(s) to the Functi. al Specifications Document after approval by CLIEN e. Change(s) to the Grap I is Design Comps after approval by CLIENT. IIWOIID INC 2of10 CRY OFFAYEIIhVII.IF WEB SITE CONTRACT • f. Change(s) to the Project Design Document after approval by CLIENT. 2 of 10 (5) CLIENT agrees to provide to IFWORLD with all data, specifications, and information, including text, graphic content, and any media which is to be included in CLIENT's web site by IFWORLD within a reasonable time after and in no event more than seventy-five (75) days from the date of signing this Agreement. (6) CLIENT understands and agrees that work will not commence until IFWORLD, in its sole discretion, determines that it has received data, specifications, and information, including text, graphic content, and any media from CLIENT sufficient for it to undertake the Design Project. (7) Should CLIENT fail to provide the data, specifications, and information, including text, graphic content, and any media, required pursuant to Paragraph five (5), IFWORLD shall have the right to declare the entire amount due IFWORLD under this agreement immediately due and payable. In that event, IFWORLD shall be under no obligation to complete its performance contemplated hereunder until such balance is paid in full and CLIENT has furnished such data, specifications, and information, including text, graphic content, and any media, sufficient, as determined in IFWORLD's sole discretion, for IFWORLD to complete the Project Design. (8) CLIENT agrees that publication of the web site will not occur until IFWORLD has been paid in full under the Design and Implementation Schedule and Budget and written authorization from CLIENT has been received by IFWORLD. GENERAL CONDITIONS: (9) IFWORLD retains the right to suspend any given Schedule due to the delay by or tardiness on the part of CLIENT when IFWORLD must await a necessary approval by CLIENT at a step or stage of the process before continuing. In that event, IFWORLD will resume work as soon as practicable after CLIENT'S response has been received. (10) Except for IFWORLD Proprietary Software as set forth in paragraph 14, all other materials, and products, and modifications developed or prepared by IFWORLD under this agreement, including without limitation to forms, images and text viewable on the Internet, any HTML elements relating thereto, and software, including the Deliverables and any Updates thereto, are the property of the CLIENT and all right and title and interest therein shall vest in CLIENT and shall be deemed to be a "work made for hire" under the United States copynght law and made in the course of this Agreement. CLIENT acknowledges IFWORLD to be the author of such web site but will limit the identification to HTML remark codes embedded in the Page Source of the Home Page. f IIWOIID INC 4of10 • CRY OF FAYETTEVILLE WEB SITE CONTRACT • 4of10 (16) NOTWITHSTANDING THE FOREGOING PARAGRAPH, IN THE EVENT THAT IFWORLD SHOULD BE HELD LIABLE TO CLIENT OR THIRD PARTIES RELATED TO THE USE OR INABILITY TO USE THE WEB SITE OF CLIENT, THEN AND IN THAT EVENT RECOVERABLE DAMAGES, IF ANY, SHALL BE LIMITED TO THE ACTUAL INJURY SUFFERED BY CLIENT OR THIRD PARTY, PROVED TO A REASONABLE CERTAINTY, OR FIVE PERCENT (5%) OF THE TOTAL AMOUNT PAW HEREUNDER, WHICHEVER IS THE LESSER AMOUNT. (17) This agreement and the continuing obligations set forth herein shall survive and continue beyond the payment of the monies due hereunder from CLIENT to IFWORLD and the construction of the web site by IFWORLD, and such continuing obligations may be enforced by either party against the other should a breach of such occur or be imminent. (18) To the extent that any provision herein might be declared invalid or unenforceable by a Court of competent jurisdiction, the remainder of this agreement shall remain in full force and effect, including the continuing obligations hereunder. (19) This agreement shall, regardless of where executed, be interpreted, construed and enforced in accordance with and subject to the laws of the State of Arkansas, and venue for any action hereunder shall lie in Washington County, Arkansas. (20) The documents which comprise this contract between the CLIENT and IFWORLD consist of this contract and the following documents, which are incorporated herein by reference as if set forth word for word: a. Bid form identified as REQUEST FOR PROPOSALS (RFP 10-01) issued September 21, 2001, for web site development and hosting assistance with all specifications, conditions, and requirements included therein; b. IFWORLD'S proposal and all supporting documents and correspondence submitted by IFWORLD on or about October 19, 2001, in response to the REQUEST FOR PROPOSALS (RFP 10-01) issued September 21, 2001. • I Ift01ID INC 5 of 10 • CRY OF FAmI l tunas WEB SITE CONrRACr • • 5of10 (21) THIS AGREEMENT constitutes the complete agreement between the parties hereto for the services covered herein, superceding any and all prior communications and agreements between the parties with respect to these services, and shall be construed and interpreted as a separate agreement from any and all other agreements which might now, or later, exist between the parties, UNLESS it be incorporated by specific reference into such other agreements. This agreement shall not be binding upon IFWORLD until accepted by a Corporate Representative other than the signing sales representative. WITNESS OUR hands on the date first above written: CLIENT IFWORLD A)/?. A Authorized Binding signature Authorized�Binding/gnature Title: Title <ze7 NI M By By - sit .. Date Da y/Iy/py 44 . ACCEPTED by IFWORLD Inc on the date first above written. IFWOIIID INC 6ofI0 • CITY OF FAYh I I hVIUJ: Wu SrIR CONTRACT • Appendix A Project Process DESIGN STAGE Establish every element of every page (visually and textually): 1. Site Map: 6of10 Design Team develops the site map based on the project requirements (i.e. Requirements Document section of the Design Contract that lists the functional requirements of the project) and project research to plan site structure and organization. 2. Schematics Document: Design Team visually describes each page with simple schematics following the outline of the site map. 3. Functional Specification Document: Design Team develops the functional specification document by describing how each page functions, closely following the schematics document. The contents of this document are as follows: • A full textual description of the site including all design, functional, and textual details of every page. • The final implementation schedule and budget. • Content appendix. • Script and textual storyboard appendix for animations or movies. 4. Graphic Design Comps: Graphic Design develops comprehensive graphic designs using the functional specification as a guide. Graphic Design also creates visual storyboards for any animation or movie content. 5. Design Specifications Document: Design Team creates a style guide outlining all design specifications that are to be followed throughout the Implementation Stage. �f IIWOIID INC 7 of 10 • Crry OF FAYFRE vi l E WES SITE CONTRACT • 7 of 10 6. Project Design Document: Project Design Document is compiled, consisting of: • Site Map • Schematics Document • Functional Specification Document including finalized versions of the content and script and textual storyboard appendices • Graphic Design Comps including storyboards • Design Specifications Document Project Design Document is delivered, fulfilling the Design Contract. IMPLEMENTATION STAGE Project design is executed: 7. Project Implementation: Design Team carries out project implementation, closely following the project design document. 8. Walk-through: A walk-through of the site is done to review it, making sure that expectations are met, and any adjustments to the site are brought to attention of IFWORLD by CLIENT. 9. Publish Site: Site goes live. 10. Wrap-up: Wrap-up meeting to review the project. Feedback is given on the project and the project process what worked and what didn't. IFWORLD will present Site Maintenance Plan for CLIENT's consideration. IIWOIIID INC 8of10 • CRY OF FAYNITEVn E WEB Smi CONTRACT • 8 0110 Appendix 13 Project Requirements Terminology Note: The Content Management System we have outlined divides each page into different parts and is perfect for the type of system that has been requested. The names of these parts are used throughout the feature descriptions below. For easy reference, the following are definitions of each part: Persistent Areas - Piece (or pieces) of a page that are static throughout the site. While the individual persistent piece might change slightly (e.g. an expanding navigation for secondary level pages), the piece is seen on every page of the site. The page elements that this usually includes are the page header, footer, and navigation. Content Areas - /fan element on a page is not one of the Persistent Areas, then it is considered one of the Content Areas of that page. It is the piece (or pieces) of a page that makes that page unique to the site. It usually has dynamic content and/or a vaned layout. Each content area is created from a page type. Page Types - Defines which content types are displayed and where they are located within the content area. Content Types - The basic building block ofa page. The individual elements within a content area. Examples: copy, lists, pictures, links, forms Core Features Overall Layout and Design The creation and development of all page elements which are persistent across the entire site. This includes, but is not limited to, the page header, footer and navigation. Emphasis is placed on ease of use and consistency of layout and user interfact. The navigation and site structure will be extensively evaluated, focusing on maximizing the user's ability to find the information they are looking for. Layout and Design of Page Types The creation and development of all content areas within each page throughout the site. Each page type listed below is designed once and then registered with the Content Management System so it can be used multiple times throughout the sitc. Listed below arc the foreseen page types for this project: • Main Page • Top Level Page • Site Map • Search Results Page • News Headlines Page • News Story Page Secondary Level Pages: • General Copy • General Copy with Image • .7 IIWORLD INC 9 of 10 • Crry of FAYF.TibviUB WEB Sm.. CONTRACT • • Multiple Sectioned Document (Reports) • Copy with Archive List • Calendar - Calendar View • Calendar - Events List View • Description & Contact Information • Mailing List Subscription Form • PDF Display • Large Image and Description • Large Image With Linked Image Map • Multiple Images and Descriptions • Form • Bulleted List • Numbered List • Tabled List • FAQ 9of10 Note: These page types cover every type of page that was listed in the REP. This goes above and beyond the requested three variations of level two pages because of efficiency usability, and necessity. Because the projected pages have not been finalized, the above list is subject to change. (23 - 30 page types) Site Search The Site Search performs a keyword search throughout the content of the entire site. Advanced searching . methods will also be used for searches of narrower scope and greater complexity. Content Management System The Content Management System handles the placing of content types (copy, calendars, forms, lists, photographs, etc.) into a predetermined page type (listed in Layout and Design of Page Types above) through the administrative section of the website. The Content Management System has the following features: Content / Mailing List Management Features • Navigation Management • Content Preview Before Publishing Live • Content Change History • Graphic File Upload • PDF File Upload • Administrative Uscr Management • Assigned Permission Levels .7 IIWORID INC 10 of 10 Optional Features: Navigation Evaluation • CITY OFFxrr:rn:vn.iWEB SITE CONTRACT • 10 of 10 IFWORLD will conduct a concentrated effort to review the needs of all possible users of the web site and design a web site and navigation scheme that best facilitates an intuitive, consistent, and informative experience. Each page of the proposed navigation will be evaluated along these lines to examine its necessity, placement, and need for improvement. All Events Calendar An All Events Calendar that would show the city events across all departments. This calendar is a virtual aggregate of the other calendars and will not have an administrative section. Page Type Builder This is a module for the Content Management System that allows administrators the ability to create new page types. This lets an administrator layout a new type of page and save it so that it can be used throughout the site. 4 IFWOILD INC IFWORLD INC City of Fayetteville Website Schedule ,L Design Milestones Design Start: ........ .....lvlarch 5, 2001 Site Map Finalized:.........................................March 21, 2001 Schematics Finalized:.....................................April 15, 2002 Functional Spec Finalized:..............................May 7, 2002 Graphic Iesigri Comps:..................................May 22, 2002 Design Completion:........................................June 13, 2002 Implementation Schedule Estimated Implementation Milestones Implementation Start:..... . . . . . . . . . . . . .......... . . . . .Jtine 14, 2002 Overall Layout Completed: ..............................June 19, 2002 Page Types Completed:...................................July 3, 2002 Content Management System Completed : .....................................................July 17, 2002 Site Search Completed:..... ............. ............. . . ..July 23, 2002 Site Published Live:........................................August 7, 2002 While testing and debugging of the site is a constant effort, two weeks have been set aside for specific concentration on testing and debugging. This will occur between the completion of the site search and the date to go live (July 23 - August 7). Maintenance policy and procedures can also be developed during this time frame because they are independent from the testing and debugging process. User training and assistance can begin after the Content Management System is completed (approx. July 17, 2002). Iof10 I of 10 • CrrY OF FAYETIEvn I R W® Sim Cow RACrn • WEB SITE DESIGN & CONSTRUCTION AGREEMENT ORIGINAL THIS AGREEMENT is made and entered into this 50 day of March, 2002 by and between IFWORLD INC. (hereafter "IFWORLD") and THE CITY OF FAYETTEVILLE (hereafter "CLIENIM3, subject to the terms and conditions more specifically set forth herein. DESIGN ST. (1) CLIENT wishes\o engage IFWORLD and IFWORLD agrees to 9fform the services which are reasonable and ne sary to create a website for CLIENT in acc,fdance with the Project Requirements set forth i Appendix B, attached hereto and made art hereof. (2) CLIENT agrees to pay IFWORLD agrees to accept a total sum of the Core Features and the initialed optional item below as consideration fo the services to be performed in the Design & Implementation stage as set forth in Appen x A. Core Features Design & Implementh ion.........../ $85.680 The total sum of the Core Features is to'be pdable as follows: $ "'Nothing"' upon signing this Agreement (3) PAYMENT. Professional Serv' es Fees for esign will be invoiced monthly for services as incurred on a time and material b sis. If changes t the hours for Professional Services stated in RFP are needed, a change/ordeigned by both part s will be required. Any Professional Services provided in excee hours stated will b charged at the unit price stated in the RFP. The Remaining Balance oplementation Cost to a billed to CLIENT immediately due and payable upon present the web"site. (4) CLIENT agrees tha any of the following actions must t acknowledges that th same will cause a change in both the Design and Implem Cation, and agrees to pay for any incrc above, due to the fqllowing actions: a. Change(s) to fife Project Requirements after signing this b. Change(s) to the Site Map after approval by CLIENT. horized by CLIENT, and time -frame for the Project costs, to be billed as set forth c. Change(s) to the Schematics Document after approval by CLIENT. d. Change(s) to the Functional Specifications Document after approval by CLIENT. e. Change(s) to the Graphic Design Comps after approval by CLIENT. I IFWORID INC 2o1 10 CrryoeFAvnm;vn.LEWEBSrrhCONIaAcr • 2of10 f. Change(s) to the Project Design Document after approval by CLIENT (5) CLIENT agrees to provide to IFWORLD with all data, specifications, and information, including text, graphic content, and any media which is to be included in CLIENT's web site by IFWORLD within a reasonable time after and in no event more than seventy-five (75) days from the date of signing this Agreement. (6) CLIENT understands and agrees that work will not commence until IFWORLD, in its sole discretion, determines that it has received data, specifications, and information, including text, graphic content, and any media from CLIENT sufficient for it to undertake the Design Project. (7) Should CLIENT fail to provide the data, specifications, and information, including text, graphic content, and any media, required pursuant to Paragraph five (5), IFWORLD shall have the right to declare the entire amount due IFWORLD under this agreement immediately due and payable. In that event, IFWORLD shall be under no obligation to complete its performance contemplated hereunder until such balance is paid in full and CLIENT has furnished such data, specifications, and information, including text, graphic content, and any media, sufficient, as determined in IFWORLD's sole discretion, for IFWORLD to complete the Project Design. (8) CLIENT agrees that publication of the web site will not occur until IFWORLD has been paid in full under the Design and Implementation Schedule and Budget and written authorization from CLIENT has been received by IFWORLD. GENERAL CONDITIONS: (9) IFWORLD retains the right to suspend any given Schedule due to the delay by or tardiness on the part of CLIENT when IFWORLD must await a necessary approval by CLIENT at a step or stage of the process before continuing. In that event, IFWORLD will resume work as soon as practicable after CLIENTS response has been received. (10) Except for IFWORLD Proprietary Software as set forth in paragraph 14, all other materials, and products, and modifications developed or prepared by IFWORLD under this agreement, including without limitation to forms, images and text viewable on the Internet, any HTML elements relating thereto, and software, including the Deliverables and any Updates thereto, are the property of the CLIENT and all right and title and interest therein shall vest in CLIENT and shall be deemed to be a "work made for hire" under the United States copyright law and made in the course of this Agreement. CLIENT acknowledges IFWORLD to be the author of such web site but will limit the identification to HTML remark codes embedded in the Page Source of the Home Page. T i,WOlLD INC 3 of 10 • CrrYOFFAYFTIEVILLE WEBSnECONfRACT • 3 of l0 (11) The IFWORLD Proprietary Software as set forth in paragraph 14 is and shall remain the property of IFWORLD. IFWORLD grants to CLIENT a perpetual, irrevocable, non-exclusive, license for CLIENT or its agents to use and copy for backup purposes the IFWORLD Proprietary Software in conjunction with the operation and maintenance of the CLIENT Site. (12) CLIENT represents and covenants that it is the owner, assignee, or licensee of all elements of the web site supplied by it to IFWORLD, including text, graphics, photos, designs, trademarks, or other artwork or materials, or has otherwise been granted permission to utilize the same by the owner or owners thereof, and agrees to indemnify and hold harmless IFWORLD from any and all claims or suits arising from the use of such elements furnished by the CLIENT, such to include reasonable attorney fees incurred by IFWORLD in defending itself and pursuing performance of this provision from CLIENT. (13) IFWORLD agrees and acknowledges that CLIENT retains exclusive rights of title and ownership over all copyrights, trademarks, or other proprietary rights associated with, pertaining or referring to, or otherwise representative of T14E CITY OF FAYETTEVILLE, its committees, departments, divisions, governing body, or other officials; including but not limited to any and all color schemes, diagrams, drawings, graphic designs, insignia, letter or number fonts, logos, mottos, photographs, seals, sketches, etc., which might be or are subject to the intellectual property rights of CLIENT. If so requested, IFWORLD will include such mutually agreed upon forms of notice on the website to protect copyrights, trademarks and other proprietary information. (14) CLIENT agrees and acknowledges that IFWORLD retains the exclusive rights of title and ownership over all IFWORLD Proprietary Software which includes all PHP Coding, Java Script and Database Structure utilized in the building, operation, maintenance of the website and remains the exclusive rights of title and ownership of IFWORLD. (15) IFWORLD MAKES NO WARRANTIES, EXPRESS OR IMPLIED, CONCERNING THE COMPLETED WEB SITE AS ACCEPTED BY CLIENT, AND CLIENT EXPRESSLY BY SIGNATURE HEREON AND ACCEPTANCE OF THE WEB SITE AS CONTEMPLATED HEREIN DOES HEREBY RELEASE AND FOREVER DISCHARGE IFWORLD, ITS EMPLOYEES, OFFICERS, ASSIGNS AND RELATED ENTITIES OF AND FROM ANY AND ALL LIABILITY ARISING FROM THE USE BY CLIENT OF THE WEB SITE AS CONSTRUCTED BY IFWORLD UNLESS EXPRESSLY SET FORTH AND ADOPTED HEREIN, IFWORLD MAKES NO WARRANTIES OF ANY TYPE OR NATURE, INCLUDING EXPRESS WARRANTIES, IMPLIED WARRANTIES, WARRANTIES OF FITNESS, AND WARRANTIES OF MERCHANTABILITY, CONCERNING THE PERFORMANCE OF ITS SERVICE PURSUANT TO THIS AGREEMENT. NEITHER IFWORLD, ITS EMPLOYEES, OFFICERS, DIRECTORS OR AGENTS SHALL BE LIABLE TO CLIENT OR ANY THIRD PARTIES FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR INABILITY TO USE, THIS SERVICE. IT irWOIID INC 4 of 10 • CrTY of FAYETIEvt.LE WEB SHE COMRACT • 4 of 10 (16) NOTWITHSTANDING THE FOREGOING PARAGRAPH, IN THE EVENT THAT IFWORLD SHOULD BE HELD LIABLE TO CLIENT OR THIRD PARTIES RELATED TO THE USE OR INABILITY TO USE THE WEB SITE OF CLIENT, THEN AND IN THAT EVENT RECOVERABLE DAMAGES, IF ANY, SHALL BE LIMITED TO THE ACTUAL INJURY SUFFERED BY CLIENT OR THIRD PARTY, PROVED TO A REASONABLE CERTAINTY, OR FIVE PERCENT (5%) OF THE TOTAL AMOUNT PAID HEREUNDER, WHICHEVER IS THE LESSER AMOUNT. (17) This agreement and the continuing obligations set forth herein shall survive and continue beyond the payment of the monies due hereunder from CLIENT to IFWORLD and the construction of the web site by IFWORLD, and such continuing obligations may be enforced by either party against the other should a breach of such occur or be imminent. (18) To the extent that any provision herein might be declared invalid or unenforceable by a Court of competent jurisdiction, the remainder of this agreement shall remain in full force and effect, including the continuing obligations hereunder. (19) This agreement shall, regardless of where executed, be interpreted, construed and enforced in accordance with and subject to the laws of the State of Arkansas, and venue for any action hereunder shall lie in Washington County, Arkansas. (20) The documents which comprise this contract between the CLIENT and IFWORLD consist of this contract and the following documents, which are incorporated herein by reference as if set forth word for word: a. Bid form identified as REQUEST FOR PROPOSALS (RFP 10-01) issued September 21, 2001, for web site development and hosting assistance with all specifications, conditions, and requirements included therein; b. [F WORLD'S proposal and all supporting documents and correspondence submitted by IFWORLD on or about October 19, 2001, in response to the REQUEST FOR PROPOSALS (RFP 10-01) issued September 21, 2001. T If WOAD INC 5 of 10 • CITY CW FAYF.TIEVILLE WEB SITE Cownc cr • 5of10 (21) THIS AGREEMENT constitutes the complete agreement between the parties hereto for the services covered herein, superceding any and all prior communications and agreements between the parties with respect to these services, and shall be construed and interpreted as a separate agreement from any and all other agreements which might now, or later, exist between the parties, UNLESS it be incorporated by specific reference into such other agreements. This agreement shall not be binding upon IF WORLD until accepted by a Corporate Representative other than the signing sales representative. WITNESS OUR hands on the date first above written: CLIENT Authorized Binding signature Title: By_ Date 1 • • s �� �. y.�.1 i:t t L, i'A ail ACCEPTED by II first above written. I IIWORLD INC on the date 6 of 10 • Crry of FAYETIEvn I c WFB Srrm CONTRACT • 6 of 10 Appendix A Project Process DESIGN STAGE Establish every element of every page (visually and textually): 1. Site Map: Design Team develops the site map based on the project requirements (i.e. Requirements Document section of the Design Contract that lists the functional requirements of the project) and project research to plan site structure and organization. 2. Schematics Document: Design Team visually describes each page with simple schematics following the outline of the site map. 3. Functional Specification Document: Design Team develops the functional specification document by describing how each page functions, closely following the schematics document. The contents of this document are as follows: • A full textual description of the site including all design, functional, and textual details of every page. • The final implementation schedule and budget. • Content appendix. • Script and textual storyboard appendix for animations or movies. 4. Graphic Design Comps: Graphic Design develops comprehensive graphic designs using the functional specification as a guide. Graphic Design also creates visual storyboards for any animation or movie content. S. Design Specifications Document: Design Team creates a style guide outlining all design specifications that are to be followed throughout the Implementation Stage. If uwo*4o INC 7 of l0 • Crrr of FAYETTEvn.ui Wan SnE CowrRAcr • 7 of l0 6. Project Design Document: Project Design Document is compiled, consisting of: • Site Map • Schematics Document • Functional Specification Document including finalized versions of the content and script and textual storyboard appendices • Graphic Design Comps including storyboards • Design Specifications Document Project Design Document is delivered, fulfilling the Design Contract. IMPLEMENTATION STAGE Project design is executed: 7. Project Implementation: • Design Team carries out project implementation, closely following the project design document. 8. Walk-through: A walk-through of the site is done to review it, making sure that expectations are met, and any adjustments to the site are brought to attention of IFWORLD by CLIENT. 9. Publish Site: Site goes live. 10. Wrap-up: Wrap-up meeting to review the project. Feedback is given on the project and the project process what worked and what didn't. IFWORLD will present Site Maintenance Plan for CLIENTS consideration. IfWOIID INC R of 10 • CRY of FAYEITEVIwii WFn Srm Count cT 8 of 10 Appendix B Project Requirements T erminolozy Note: The Content Management System we have outlined divides each page into different parts and is perfect for the type of system that has been requested. The names of these parts are used throughout the feature descriptions below. For easy reference, the following are definitions of each part: Persistent Areas - Piece (or pieces) ofa page that are static throughout the site. While the individual persistent piece might change slightly (e.g. an expanding navigation for secondary level pages), the piece is seen on every page of the site. The page elements that this usually includes are the page header, footer, and navigation. Content Areas - If an element on a page is not one of the Persistent Areas, then it is considered one of the Content Areas of that page. It is the piece (or pieces) of a page that makes that page unique to the site. It usually has dynamic content and/or a varied layout. Each content area is created from a page type. Page Types -- Defines which content types are displayed and where they are located within the content area. Content Types The basic building block ofa page. The individual elements within a content area. Examples: copy, lists, pictures, links, forms • Core Features Overall Layout and Design The creation and development of all page elements which arc persistent across the entire site. This includes, but is not limited to, the page header, footer and navigation. Emphasis is placed on case of use and consistency of layout and user interface. The navigation and site structure will be extensively evaluated, focusing on maximizing the user's ability to find the information they are looking for. Layout and Design of Page Types The creation and development of all content areas within each page throughout the site. Each page type listed below is designed once and then registered with the Content Management System so it can be used multiple times throughout the site. Listed below are the foreseen page types for this project: • Main Page • Top Level Page • Site Map • Search Results Page • News Headlines Page • News Story Page Secondary Level Pages: • General Copy • General Copy with Image I IFWO2LD INC 9of10CITY0FI'AYErIEVn1EWEBSn5CowRA(T • 9of10 • Multiple Sectioned Document (Reports) • Copy with Archive List • Calendar - Calendar View • Calendar - Events List View • Description & Contact Information • Mailing List Subscription Form • PDF Display • Large Image and Description • Large Image With Linked Image Map • Multiple Images and Descriptions • Form • Bulleted List • Numbered List • Tabled List • FAQ Note: These page types cover every type of page that was listed in the REP. This goes above and beyond the requested three variations of level two pages because of efficiency. usability, and necessity. Because the projected pages have not been finalized, the above list is subject to change. (23 30 page types) Site Search The Site Search performs a keyword search throughout the content of the entire site. Advanced searching methods will also be used for searches of narrower scope and greater complexity. Content Management System The Content Management System handles the placing of content types (copy, calendars, forms, lists, photographs, etc.) into a predetermined page type (listed in Layout and Design of Page Types above) through the administrative section of the website. The Content Management System has the following features: Content / Mailing List Management Features • Navigation Management • Content Preview Before Publishing Live • Content Change History • Graphic File Upload • PDF File Upload • Administrative User Management • Assigned Permission Levels T IFWOILD INC 10 of 10 • CRY OF FAYETTrmLLE WEB Sm5 ComRACr • l0 of 10 Optional Features: Navigation Evaluation IFWORLD will conduct a concentrated effort to review the needs of all possible users of the web site and design a web site and navigation scheme that best facilitates an intuitive, consistent, and informative experience. Each page of the proposed navigation will be evaluated along these lines to examine its necessity, placement, and need for improvement. All Events Calendar An All Events Calendar that would show the city events across all departments. This calendar is a virtual aggregate of the other calendars and will not have an administrative section. Paae Tvoe Builder This is a module for the Content Management System that allows administrators the ability to 11 create new page types. This lets an administrator layout a new type of page and save it so that it can be used throughout the site. I IIWORID INC • • IFWORLD INC City of Fayetteville Website Schedule Design Schedule Design Milestones Design Start:..................................................March 5, 2001 Site Map Finalized:.........................................March 21, 2001 Schematics Finalized:.....................................April 15, 2002 Functional Spec Finalized: ..............................May 7, 2002 Graphic Design Comps:..................................May 22, 2002 Design Completion:........................................June 13, 2002 Implementation Schedule Estimated Implementation Milestones Implementation Start: ................................Ji.ine 14, 2002 Overall Layout Completed: ..............................June 19, 2002 Page Types Completed:...................................July 3, 2002 Content Management System Completed :.....................................................July 17, 2002 Site Search Completed:............... ....................July 23, 2002 Site Published Live:........................................August 7, 2002 While testing and debugging of the site is a constant effort, two weeks have been set aside for specific concentration on testing and debugging. This will occur between the completion of the site search and the date to go live (July 23 - August 7). Maintenance policy and procedures can also be developed during this time frame because they are independent from the testing and debugging process. User training and assistance can begin after the Content Management System is completed (approx. July 17, 2002). IFWORLD INC DU IHTIUfl CGwU1Hl CGMtw 'Purchasing Division City of Fayetteville 113 West Mountain Street Fayetteville AR. 72701 Greetings, Both Interface Computer Center and Southwestern Bell would like to express our appreciation to the City of Fayetteville for allowing us the occasion to present our proposal for the upcoming website. We are thrilled to offer our combined years of experience, skills and expertise back to the community that helped shaped them. SWB and Interface have worked diligently to assemble the desires of the City into a strategic plan for one seamless Integrated solution. Building upon one another's' strengths, we have forged an alliance that provides the City with the best qualities of both companies. Based•in Fayetteville, Interface Computer Center has led the way for many years providing high -end web solutions for clients throughout the state while concentrating •'.'` on Northwest Arkansas. Southwestern Bell stands as a pillar of the comfnunicationt industry both locally and abroad by providing clients with innovative, reliable _?t technologies through a host of options that: are unmatched in the state. ;' The ideas, budget andprocess: by which 'we'hope to the current site: are submitted here for.your review. We are committed to working in a dose EPatzrsh.Ip: ,:.with the City to meet and exceed the guidelines of the REP. If there is any vaguenes's :•-.or concerns that arise, we welcome the 'opportunity' to.make ourselves available; to ,clarity those points. - Again, we thank you for the time and consideration put forth in regardsto our proposal. Both Interface and SWB are excited at the prospect of working closer together in this common vision we share for the future online presence of the City of Fayetteville. Share Fisher Sales Manager IFWORLD INC. D.B.A. Interface Computer Center VENDOR RESPONSE Interface Computer Center, a Division of IFWORLD INC., and Southwestern Bell will systematically respond to each numbered paragraph as requested in paragraphs 1 and 2 of SECTION IV. The chosen format and outline of responses in this proposal follows the layout scheme of the RFP to aid the City in making a side -by -side comparison. Note: Questions quoted from the City RFP are in italics. SECTION LB We require that each proposer provide us with a review of our current web site, other government and private sites outlining the specific approach and strategy the proposer recommends we pursue. The city of Fayetteville's current site does not seem to best represent what the City and community have to offer. The Declaration of Attributes outlined below, by way of • implication, best summarizes what the current site could benefit from. Because this bid is made public, we have limited the extent of our comments in this document that are considered, proprietary. However, it is our intent after bid acceptance to fully review the current site, and work with the City to develop a strategy and a systematic.. approach of implementation. SECTION II.A Web Site Development Assistance Items 1-13 The RFP proposes the development of a city website with the objectives of targeting the needs of City employees, residents, local business and visitors while providing an attractive marketing venue for relocating individuals and industry. The following responses (1-12) are what Interface refers to as the Declaration of Attributes'. These statements best define our understanding of what the City of Fayetteville ultimately desires. Declaration of Attributes The website will undoubtedly rank among the great technological achievements of public relations that the City of Fayetteville has undertaken. The city website will be a shining star in the online presence of Northwest Arkansas. It will come to stand as a measure of excellence by which other cities and sites are compared. 1. To create a scalable site -architecture... • That incorporates the best aspects of the current site; Page: 1 of 27 Last printed: 10/19/2001 11:26 AM • That permits additional features and functionality for future phases; • That is technically superior to and pleasingly different from Scottsdale's and Blacksburg's city websites. 2. To'create an innovative design -layout and navigation... • That reflects the mores and ethos of the community: • That is exciting, warm and affable to visitors near and abroad: • That strongly embodies the stylization as displayed in Appendix E of the RFP. 3. To build aflexible lexible site architecture • That facilitates effortless revision; • That provides high reliability and strong stability for low maintenance; • That makes use of expert programming and storage methods that provide real-time page rendering, low latency, and above all, simplicity. 4. To provide a content management system.. • That allows for a decentralized scheme of revision and updates. • That tracks page and content changes and allows reversion to previous versions on a case -by -case basis. • That is intuitively developed to make learning quick and painless. • That selected City staff will be instructed on the use thereof. 5. To build an agile site architecture... • That will seamlessly integrate future e -commerce function. • That anticipates future expansion and facilitates new development. 6. To create a site interface... • That employs the most appropriately advanced technology, yet remains as transparent as possible to the attention of the visitor. • That provides a pleasant user experience to the widest relevant range of connection speeds and browser types. • That avoids the use of plug -ins as a general rule:but, • in appropriate situations, makes use of some plug -ins, yet provides an alternative method to obtain the same content. 7. To provide a search module... • That allows visitors to search the content of the entire site. • That provides helpful querying methods to better refine search results. • That will make use of the powerful content indexing module of the content management system to vastly accelerate queries and eliminate redundant programming there by reducing programming costs. Page: 2 of 27 Last printed: 10/19/2001 11:26 AM 8. To perform an initial search engine submittal... • That will make use of embedded meta -tags on every page. • A historically successful marketing tactic will be offered as an option to the City after a bid acceptance. All details of our process, however, will remain our secret until the City is a valued client. 9. To provide automatic subscriber mailing lists... • That will be created from a custom -programmed module built into the administration portion of the City's site. • That will permit City employees to create, customize and edit mailing lists without limit. 10. To create a calendar... • That will be made from a custom -programmed module built into the administration side of the City's site. That will allow permitted City employees, by department, to quickly create, edit and remove items on a calendar or the whole calendar itself. That as an optional feature can display all events from all departments on one master calendar, viewable as a list of events or by a traditional calendar view. 11. To provide the design and coding of 3 variations of level two pages to be provided as templates forfuture departmental web pages. 12. An inventory of the web pages requested on the web site is provided on the pages labeled Appendix H - "Web Site Needs Assessment" The inventory listing is subject to change and is to be used only to evaluate the size of the project The items addressed with this proposal pertain only to PHASE 1. If any of the items in PHASE 2 or 3 can be accomplished in this proposal, please specify If the cost is included or fit will be additional. An exhaustive study of Appendix H has been completed. Every section, feature and function was categorized by page type, content type and function type then organized into a plan of execution. In paragraph 12 it is asked if any PHASE 2 or PHASE 3 items can be accomplished within PHASE 1, and if so, how much extra. Please Know that Interface Computer Center is planning to build for the City of Fayetteville one of the most dynamic and powerful website publishing engines possible. The concept, as it is suggested here in our proposal, will allow anyone with access to create expansions immediately and easily. The publishing engine will worry about fonts, colors, alignment, look, re- arrangement of the navigation, updating the search engine index, writing of the HTML, placement of meta -tags, etc. Therefore, the City has an endless possibility of expansion so long as no new content types or page types are required. With this in mind, any PHASE 2 or PHASE 3 item that does not introduce a new content or page -type may be created freely in the proposed PHASE 1. If a PHASE 2 or 3 item does require a Page: 3 of 27 Last printed: 10/19/2001 11:26 AM new content or page type (such as a billing system or an address lookup module), it would need to be created by Interface as a new type and would be easily integrated into the site. Dynamic page types such as an online billing system or an address -lookup are what Interface classifies as a "module"; an item that requires a special set of stand-alone programming scripts to operate a function. Several modules are listed in PHASES 2 and 3 and mentioned in the above paragraph. Outlining these modules alone generates such a plethora of unanswered questions that bidding them within the confines of this proposal and at such an early stage becomes almost academic. It is of commendable prudence on the part of the City that these items were placed as continuing evolutions of. and separate from, PHASE 1. It can be assured that though these modules are complex, they are all well within the capabilities of our talented team of individuals. In addition, all mentioned PHASE 2 and 3 modules could seamlessly and economically be added with no revision to Interface's currently proposed programming architecture. 13. Upon completion of the contract, the City will take ownership of the website. All content and media accessible through the public website will become the property of the City. The City will be solely responsible for the maintenance of the content and will have unlimited license to use the content management and other programmed administrative tasks to accomplish this. SECTION II.B Web Site Maintenance Items 1-1 1. The method that will be employed in the event revisions are needed will be as follows: • Revision request is submitted to Interface. • The revision is evaluated in terms of the type of work involved and the required amount of hours to complete it (usually within 24 hours). • The hourly rate multiplied by the number of estimated hours will equal the proposed cost (Cost=Rate•Tlrne). • General Rate S110/hr. • Graphic Design, Layout, Copy Editing $1 10/hr. • Database programming, Flash programming, scripting S150/hr. • The minimum increment is 1 hour with 15 minute increments after the first full hour in a billing period. • The City will then be notified of a cost and time schedule (usually within 24 hours). • When the proposal for the revision is approved, it will immediately be given to the project manager for execution. Page: 4 0( 27 Last printed: 10/19/2001 11:26 AM The average turnaround time for most minor revisions is less than 48 hours. However, the time frames for larger items will be calculated based on the total number of hours multiplied by a six hour day. Please know that this is a rule of thumb and not necessarily a "formula'. Other factors such as current work loads, weather and holidays on occasion have affected turnaround times. If the revision is time sensitive, rigorous efforts will be made to accommodate it. SECTION II.C Web Site Hosting Capability Items 1-15 1. Network topology: how direct is your connection to the Internet backbone? Each SBC point of presence (POP) is a fully independent network, each having its own autonomous connections to Tier 1 national backbone providers. Our network design assures over 40 percent excess capacity. We purposely overbuild our network to ensure the smooth and efficient transmission of our customers' data traffic. SBC maintains connections to dual, Tier 1 national backbone providers to ensure redundant connections to our customers' data. Our Points of Presence (POP's) are built using only the best -of -breed components from the most qualified manufacturers in the networking business. Each POP is equipped with high-powered battery backup along with diesel generator capability in the event of an extended power outage. 2. Bandwidth what kind of Internet connections do you offer for hosting (Le. T-1, T-3. OC-3. DS -S, etc..) Please explain your cost structure for bandwidth allocation and also how you determine usage. Our Internet Data Center is fed by Dual OC 12's from redundant carriers, and we don't limit the amount of bandwidth your server can use, hence our high speed Internet connectivity. Initial connection to the Internet switch is a 10 Mb Ethernet Connection Page: 5 of 27 Last printed: 10/19/2001 11:26 AM 3. Server types: please explain the different hosting options you provide (i.e. shared dedicated, co -location, etc.?) SBC offers Shared Hosting, Dedicated Hosting and Co -location. Dedicated Hosting packages and Co -location packages are available in both packaged as well as custom solutions. 4. Scalability: how quickly can you provide the City with more processing power, storage space, and bandwidth? Timeframes for upgrades are typically 2-4 business days for standard offerings of processors, RAM, hard drives and IP addresses. In some cases, due to part availability issues, the timeframe may be longer. 5. Data Transfer please explain the types of accesses available to clients (i.e. F7'P, Telnet etc.) Customers have access to their server via PC Anywhere (Windows ) or SSH (Unix) clients that are loaded on the server. Customers may also use other types of access such as FTP and Telnet) 6. Reliability: please explain your reliability and uptime guarantees. SBC bacxs its Dedicated Hosting product with a commitment and focus on operational excellence and reliability. This commitment is backed by a network uptime guarantee of 99.9%. If a server falls to respond to our ICMP (Ping)- by SBC, our technicians pro- actively engage in diagnostic activities to isolate and resolve difficulties. For every full one (1) full hour of core network downtime recorded at SBC's Internet Data Center (IDC), SBC will credit a client's account the value of one day of service (excluding scheduled maintenance times and customer requested downtimes). 7. Technical Support what are your operating howl for live human technical support (Le. 24/7/365.) Also, what methods are available for contact (Le. phone, a -mail, web, fax) Technical Support is available to all customers 24/7/365. Customers can reach technical support via a toll -free number or e-mail. Page: 6 of 27 Last printed: 10/19/2001 11:26 AM 8. Redundancy: what do you make redundant - servers, entire machine•rooms? While our Dedicated Hosting Servers are not redundant themselves, the Data Center in which all of SBC's Dedicated Hosting Servers are held, have built into it fully redundant network access ports with diverse paths that terminate on separate switches, dual preferential commercial power feeds with redundant parallel commercial transformers, redundant feeds to separate Power Distribution Units to ensure clean conditioned power, redundant Uninterruptible Power Supply with battery backup to guarantee against power outages, and 4 Caterpillar back-up generators with 72 hours of on -site fuel with guaranteed re -fueling contracts. The SBC IDCs are built with N+ 1 redundancy of every system (excluding individual servers), and as such, we guarantee 100 percent uptime without the need for "unplanned" maintenance of facility systems. Network, Power, HVAC, Fire Protection and Security have all been implemented with N+1 redundancy. 9. Security and backups: please explain methods used and backup frequency. Site Security Understanding the critical nature of client equipment. SBC monitors the Internet Data Centers 24 hours a day, 7 days a week and provides multi -tiered security systems. The IDCs have limited secure access points, bullet -resistant materials at the entrance, and minimal windows throughout the facility. In addition, SBC strictly regulates and monitors access. A client's equipment is stored in an area that only the client and authorized SBC IDC personnel can access. SBC controls access to the equipment floor through biometric palm scanners and card key access control. The card reader has a proximity sensor that only opens the cabinet to which it is pre-programmed. Continuous monitoring cameras (24x7 CCTV) are located throughout the facility, including bubble cameras in the ceiling and monitoring at all entry/exit points. Motion sensors are placed throughout the building and even under the raised floor to prevent tampering with cable and power trays. When a motion sensor is activated, an alarm and camera will record the event. High -definition resolution and backlight -compensating security cameras are present throughout the co -location floor. Additionally. SBC Internet Data Center personnel maintain 24 -hour digital recordings and 90 -day digital video storage. Security personnel are on -site 24x7x365. All surveillance videotapes are kept onsite for 90 days All cable runs are below the raised floor. A grid of motion sensors that alarm in the NOC protects the raised -floor crawl space. Ability to segregate agency access from other agencies - Customers network is separated through the use of Virtual Local Area Networks (ULAN). By utilizing this technology, SBC IDC customers are located on their own network segment. Other Page: 7 of 27 Last printed: 10/19/2001 11:26 AM customers hosted in the IDC do not have physical or logical access to the VLAN platform. Server Security Operations - back-ups, log monitoring: SBC uses the latest in tape backup and restore technology for customers to provide a dedicated, scalable system for effectively safeguarding your mission -critical data, 24 x 7, ensuring continued business operations so you have protection against data loss due to accident or other failures through Automated Backup Services. SBC's Automated Tape Back-up service is used with Dedicated Web Hosting, allowing hosting customers to back-up data, files and systems in an economical and flexible fashion. The service offers you management of important data and backup process for individual files, or file systems, databases, and applications. Automated Tape Back-up allows you to set parameters, such as how much and when, to back up your data in secure environment. Entire systems can be chosen for backup as well as the more critical elements of those systems as specified by you, including databases, applications and log files. The Automated Tape Backup system is designed for performance in the network with a separate 'back-up" network used, generally from a second Ethernet port on the web hosting servers. The separate backup network goes to a Sun server to cache the data before writing to the AIT-2 tape. Server security from Internet Traffic is offered by Netscreen - Screen OS 2.6. 10. Relationships with backbone network providers and Web consultants. Ease of adds/moves/changes. - SBC has the ability to work with most backbone providers like Sprint, AT&T. Williams, etc. 11. Productivity, experience, expertise, and training of support staf. SBC considers the specific staff skill sets to be proprietary information. However, the SBC Internet Data Centers are staffed with an on -site, highly skilled, diverse support team 24 hours a day, 7 days a week. All Network Operations Center (NOC) personnel hold industry certification from Cisco (CCNA, CCNP, and CCIE). Microsoft (MSCE). and Sun (Solaris/Unix). The NOC staff proactively monitors management of customer space, power, temperature, and bandwidth. Additionally, the staff provides centralized monitoring of UPS. AC power, PDU, HVAC, temperature, humidity, security, fire prevention, and overall network operation. A minimum of two NOC engineers is on staff 24x7x365. • Tier 1: 3 years' industry experience and CCNA certification • Tier 2: 5 years' industry experience and CCNP certification • Tier 3: 7-10 years' industry experience and CCIE-level, pursuit of CCIE certification is required Page: 8 of 27 Last printed: 10/19/2001 11:26 AM 12. Please List and explain the type of programming tools, databases, and applets you make available. Interface Computer Center does not make available any of the afore mentioned items outside of what is intrinsically built into the product that would build for the City. 13. Statistical reports: what reporting software do you provide (Le. webtrends, wusage, etc.) for web traffic statistics? What kind of reports are available and how are they accessible? Managed Monitoring Basic Is one of the many Enhanced Services we offer our Internet Data Center (IDC) customers. This service provides you with reports on the health of your web -hosting or co -location services at the IDC. The reports are generated and e - mailed out, per your request, on a monthly basis for the prior month. These reports provide you with the ability to monitor the status of your services, which may include transport and data traffic, firewall status, tape back-up, and/or load balancing services, and the status of the general IDC Environmental Health. With this information, you can track and plan for your network needs. 14. Outsourcing needs: provide an objective assessment of the Web services the City should keep in-house and the ones It should out -source. There are a great many factors that are left unaddressed in this question that make it difficult to render an informed and appropriate response. From a purely financial perspective, both the hosting and building of a web site such as the caliber mentioned in this document should be outsourced. Given the sheer complexity and enormity of the project, it is best suited to a dedicated resource: individuals whose technical expertise lie in the field. In addition, the rate of change and standard wages commanded in the industry as a whole, make it cost prohibitive to all but the largest entities that benefit from massive economies of scale. Tasks such as copy writing/editing and static content updates ate items that the City should consider keeping in-house. These tasks are most time consuming and are best executed by those that are most knowledgeable about the content. Logistically and financially speaking, web hosting in the majority of circumstances is best left to professional entities that can offer the expertise, reliability and cost -savings that arise from specialization. Page: 9 of 27 Last printed: 10/19/2001 11:26 AM 15. Your track record: indicate your company history, how long you've been in the Web hosting business, and the financial stability of your company. The WebHosting.Com portfolio of hosting products and services is brought to you by SBC Communications Inc., a global communications leader. Through its subsidiaries' trusted brands -- Southwestern Bell, Ameritech, Pacific Bell, Nevada Bell, SNET. SBC Telecom, and Sterling Commerce Inc. -- and world -class network, SBC and its affiliated companies provide a full range of voice, data, networking and eBusiness services, including local and long-distance voice, high-speed Internet access and data transport, voice and data network integration, software and process integration. Web site and application hosting, eMarketplace development, paging and messaging, as well as cable and satellite television, security services, and directory advertising and publishing. In the United States, the company currently has 61.3 million access lines and is undertaking a national expansion program that will bring SBC service to the nation's top 50 markets. SBC has a 60 percent equity interest in Cingular Wireless, its joint venture with BellSouth, which serves 19.7 million wireless customers. Internationally, SBC has telecommunications investments in more than 20 countries and has annual revenues that rank It among the largest Fortune 500 companies. We are one of the world's largest international Web hosting operators. We have registered more than 100,000 domain names on behalf of the tens of thousands of businesses who host their Web sites on our network. Our portfolio of professional services and our proprietary hosting platform technology enable our customers to efficiently manage and scale their Web presence and applications. Our customer base will continue to expand as packaged offerings combining SBC's hosting services and technology with our high-speed data transport, network integration and advanced eBusiness services are offered to the 3 million business customers served by SBC. The scalability of SBC's infrastructure and operational controls is a proven and decisive competitive advantage. Our architecture can be scaled and clustered based on client needs for shared or dedicated hosting. For each of our WebHosting.Com service offerings, a back -end RAID5-based network file system enables clients to share their data securely and reliably between multiple nodes. A centralized, SQL -based authentication scheme allows for quick replication of database changes to all nodes across the cluster and for easy data recovery in the event of failure. SBC's data backup and storage methods allow for quick recovery in the form of hourly, daily, weekly and monthly files in case of data loss. On the front-end, WLBS and Zeus clustering technology combined with hardware front-end redundancy through load balancing products help guarantee clients exceptional performance and service levels. In today's always -on world, a company's Web site is critical to its ability to compete and succeed. At SBC, we recognize our mission -critical role. Our top priority is to provide high -quality, reliable services and top-notch customer service to all customers. We are pleased that this dedication has been recognized by our selection as a founding charter member of the Web Host Guild -- an industry quality control association. Page: 10 of 27 Last printed: 10/19/2001 11:26 AM 1 • • SECTION III General Requirements For Proposing Items 1-8 1-8. Both SBC and Interface Computer Center have read, understood, and will comply with paragraphs 1-8. 6. Both SBC and Interface Computer Center have attached evidence of insurance in Addendum 1. 7. Both SBC and Interface Computer Center have attached certification of independence in Addendum 2. SECTION IV Specific Requirements For Proposal Items 1-7 1-7. Both SBC and Interface Computer Center have read, and understood, and will comply with paragraphs 1-7. SECTION V Terms And Conditions Items 1-11 1. For the design and implementation of PHASE 1 (as defined in the RFP) of the website; a not -to -exceed amount of $99,000 has been established. This figure excludes optional features. 2-11. Both SBC and Interface Computer Center have read, understood, and will comply, with paragraphs 2-11. SECTION VI Warranty :• T.r.•r--. Both SBC and Interface Computer Center have read, understood, and comply. Page: 11 of 27 Last printed: 10/ 19/2001 11:26 AM SECTION VII Clarification Of RFP Both Paragraphs Both SBC and Interface Computer Center have read, understood, and comply. SECTION VIII Sample Contracts Paragraph A Sample Contract for Web Design from Interface Computer Center can be found as Addendum item number 3. SECTION IX Firm's Schedule No comment I SECTION X Standard Terms & Conditions Items 1-27 Both SBC and Interface Computer Center have read, understood, and comply with paragraphs 1-27. SECTION XI Vendor Response Section Items 2-6 XL2 Summary Items A -B A. Please describe why yourfum is interested in this project Page: 12 of 27 Last printed: 10/19/2001 11:26 AM SBC wishes to participate in the webhosting portion of this project because of our ability to support the City of Fayetteville and offer a Supreme Webhosting solution that will be reliable, efficient and cost effective for the city. Interface Computer Center's interest in winning this project is motivated by the love we have for what we do. A fantastic opportunity such as this, which allows our specialized set of talents to contribute to such an important project for our City does not come often. We are as excited as the City must be at the possibility of producing such an incredibly powerful online presence as outlined in the RFP. B. Please describe your understanding of the project with outlined approach and implementation methods. Interface'sbest and most concise response to this request is our Declaration of Attributes which is found in the preceding SECTION ILA. After the website development stage. SBC will provision the chosen server package in SBC's Internet Data Center and make testing arrangements with the necessary parties. SBC will then work with the City of Fayetteville and Interface Computer Center to obtain correct DNS Information and make the necessary changes to bring the website live. XI.3 Statement Of Work Items A. C -E (B follows) A. Please give a description of the. development process including a listing of project stages and milestones. C. Please describe the plan for meeting with City staff members including strategy for gaining design consensus. D. Please describe the plan for quality control and testing. E. Please describe the plan for final and draft delivery methods. Over the past seven years Interface Computer Center has developed a set of steps by which all websites are built. This process is the culmination of our effort to help bring clear direction and decrease risk for both parties and lower overall project cost while offering an unprecedented level of value. In the next few paragraphs we will explain these steps in more detail. Page: 13 of 27 Last printed: 10/19/2001 11:26 AM The first six steps, known as the Design Stage, are unique in that they build the website on paper with no detail left out. This is similar to the same way an architect renders a building in the form of a blueprint before the shovel ever breaks ground. This stage, so often overlooked, is absolutely essential in maintaining budget and scheduling goals. This stage lays out the position of every element which allows both parties to come to an exact consensus on what will be built, how it will function, its appearance and even the cost down to the dollar. With the Design Sage complete, the final four steps, or the Implementation Stage, will carry the design out to the last detail. Each section will have been laid out, and the site will materialize with mechanical precision. Tasks will be accomplished daily, evaluated for consistency, and then summarized for the client in a weekly or bi-weekly progress report. As implementation comes to a conclusion, a walk-through of the site will be scheduled to verify that all expectations have been met. At this point, web hosting services will be finalized as the site is prepared to go live. A wrap-up meeting will conclude the process. Outlined for your approval below is the above stated process including a further description of each step. Desian Phase The Site Map The Design Team develops a detailed map of.the websites' link structure and organization based on the project requirements as outlined in the RFP. Priority will be placed on attaining a structure that expresses a natural flow of information in the manner it might be viewed by potential guests to the site. The City will review the site map giving detailed and written feedback. Changes will then be made as necessary until the site map has consensus and signed approval. 2. Schematics Document The Design Team will decide on the methods of navigation, link placement, and graphical user interface for each page type and project requirement (i.e. calendars, maps, etc.). while closely following the site map this written information will be gathered into what is called the schematics document? Emphasis will be placed highly on intuitive navigation and visual consistency among elements that will further enhance the guests' online experience. The City will review the schematics document giving detailed and written feedback. Changes will then be made as necessary until the Schematics Document has consensus and signed approval. 3. Functional Specification Document Heavily utilizing the Site Map and Schematics Document, the Design Team will focus on defining the programming logic that will be required to enable the desired functions of each page type and project requirement. In addition, Page: 14 of 27 Last printed: 10/19/2001 11:26 AM the team will provide the City with more accurate figures for the amount of time required for implementation and the anticipated day of completion for PHASE 1. The City will again have the opportunity to review the Schematics Document giving detailed written feedback. Changes will be made as necessary until the document has consensus and signed approval. 4. Graphic Design Comps The Graphic Design Team, in close partnership with the City, will develop mockups that shall pioneer the visual styling of the new site. These mocks will showcase the solutions to merge traits such as simplicity with stunning elegance. The City will have the opportunity to critique the Design Comps, giving written feedback. Changes will be made as necessary until the Design Comps have the consensus of relevant parties and signed approval. 5. Design Specifications Document The Design Team will create a style guide that outlines all design specifications (e.g. text styles, logo use, image uniformity guidelines, colors, etc.) that are to be followed throughout the Implementation Stage. This allows multiple designers and programmers to work on a project with uniformity and consistency. Most importantly, it gives the City a guideline for maintaining a consistent design in future content revisions. The City will again have the opportunity to critique the Design Specification Document, giving written feedback. Changes will be made as necessary until the document has the consensus and signed approval. 6. Project Design Document This Document is the culmination and reason for all of the effort put forth up to now. This document consists of finalized versions of the following: • Site Map • Schematics Document • Functional Specification Document • Graphic Design Comps • Design Specifications Document This is the master blueprint that contains detailed descriptions of all the project's requirements, ending the Design Phase. Implementation Phase Project Implementation The Design Team carries out project implementation, closely following the Project Design Document. Over the years we have witnessed several web design firms fail in large part because of their over -emphasis on, and haste to implement this step. When building web sites on the scale of this project, the importance of having a project design document as developed in the previously mentioned 6 steps can't be emphasized enough. It MUST exist or the project Is fated to exceed both the budget and the schedule. Page: 15 of 27 Last printed: 10/19/2001 11:26 AM I C 2. Walk-through A walk-through of the site will be done with the City to review it, making sure that expectations are met. Minor adjustments may be made and the site will be transfered to a public domain server. At this time SBC will assume their contractual services to host the site. 3. Publish Site Site goes live and a final review of the live site is done with the City. 4. Wrap-up A wrap-up meeting will be held to review the project. Feedback is given on the project and the project process - what worked and what didn't. And the final step....Throw a Birthday Party for the new and improved City Web site. Note Because of the nature of website programming and design, each step in the process is cumulative and plays a significant role in each subsequent task Therefore, significant alterations made to any one of the steps after it has been completed will likely cause a change in the project schedule and budget. B. Please give a breakdown of project costs and details. Core and Optional Site Feature Description & Costs Terminology Note: The Content Management System we have outlined divides each page into different parts and is perfect for the type of system that has been requested. The names of these parts are used throughout the feature descriptions below. For easy reference, the following are definitions of each part: Persistent Areas - Piece (or pieces) of a page that is static throughout the site. While the individual persistent piece might change slightly (e.g. an expanding navigation for secondary level pages). the piece is seen on every page of the site. The page elements that this usually includes are the page header, footer, and navigation. Content Areas - If an element on a page is not one of the Persistent Areas, then it is considered one of the Content Areas of that page. It is the piece (or pieces) of a page that makes that page unique to the site. It usually has dynamic content and/or a varied layout. Each content area is created from a page type. Page Types - Defines which content types are displayed and where they are located within the content area. Content Types - The basic building block of a page. The individual elements within a content area. Examples: copy, lists, pictures, links, forms Core Features Page: 16 of 27 Last printed: 10/19/2001 11:26 AM Overall Layout and Design This is the creation and development of all page elements which are persistent across the entire site. This includes, but is not limited to, the page header, footer and navigation. Emphasis is placed on ease of use and consistency of layout and user interface. The navigation and site structure will be extensively evaluated, focusing on maximizing the user's ability to find the information they are looking for. HTML.............................................................. 18 hours S 1,980 Layout and Design of Page Types This is the creation and development of all content areas within each page throughout the site. Each page type listed below is designed once and then registered with the Content Management System so it can be used multiple times throughout the site. Listed below are the foreseen page types for this project: • Main Page • Top Level Page • Site Map • Search Results Page • News Headlines Page • News Story Page Secondary Level Pages: • General Copy • General Copy with Image • Multiple Sectioned Document (Reports) • Copy with Archive List • Calendar - Calendar View • Calendar - Events List View • Description & Contact Information • Mailing List Subscription Form • PDF Display • Large Image and Description • Large Image With Linked Image Map • Multiple Images and Descriptions • Form • Bulleted List • Numbered List • Tabled List • FAQ Note: These page types cover every type of page that was listed in the RFP. This goes above and beyond the requested three variations of level two pages because of efficiency, usability, and necessity. Because the projected pages have not been finalized, the above list is subject to change. 23 - 30 page types Page: 17 of 27 Last printed: 10/19/2001 11:26 AM 0 HTML.............................................................. 60 hours 56.600 Site Search The Site Search performs a keyword search throughout the content of the entire site. Advanced searching methods will also be used for searches of narrower scope and greater complexity. HTML.............................................................. 3 hours 8330 Programming .................................................. 18 hours S2,700 Content Management Systems The Content Management System handles the placing of content types (copy, calendars, forms, lists, photographs, etc.) into a predetermined page type (listed in Layout and Design of Page Types above) through the administrative section of the website. The Content Management System has the following features: Content / Mailing List Management Features • Navigation Management • Content Preview Before Publishing Live • Content Change History • Graphic File Upload • PDF File Upload • Administrative User Management • Assigned Permission Levels Content Management System: HTML.............................................................. Content Management ...................................... 24 66 hours hours S2.640 $9.900 Navigation Management ................................. 24 hours 83,600 Mailing List Management ............................... 12 hours $1,800 Content Preview ............................................ 12 hours 81,800 Content Change History ................................. 16 hours 82,400 Graphic Upload............................................. 4 hours $600 PDF Upload.................................................. 4 hours $600 User Management......................................... 4 hours $600 Testing and Debugging Graphic Design ............................................... 18 hours S 1.980 Programming .................................................. 24 hours 83,600 Training Project Management........................................ 12 hours 81,320 Page: 18 of 27 Last printed: 10/19/2001 11:26 AM Implementation Total .................................319 hours $42,450 Core Features Design Project Preparation.......................................... Site Map .......................................................... Schematics Document .................................... Functional Specifications ................................ Graphic Design Comps.................................... Design Specifications ...................................... Project Design Document ................................ 4 hours 44 hours 92 hours 162 hours 42 hours 11 hours 38 hours 8440 64,840 $1 C), 1 2() $17,820 84,620 $1,210 $4,180 Design Total................................................393 hours $43,230 TOTALS Core Features RFP Core Features Design............................................................. 393 hours S43,230 Implementation ............................................... 319 hours $42, 450 Total...........................................................712 hours $85,680 Not to Exceed 599,000 (excludes optional items) Optional Features: We are concerned with the current proposed navigation scheme. It is our opinion that there may be an improved method to organize the site links to best target several types of users at once. However, at the request of the RFP, we have been diligent to bid all items "as is" so that the proposals from different vendors might be compared equitably. Therefore we have placed our usual navigation evaluation step as an option below. Navigation Evaluation We will conduct a concentrated effort to review the needs of all possible users of the website and design a website and navigation scheme that best facilitates an intuitive, consistent, and informative experience. Each page of the proposed navigation will be evaluated along these lines to examine its necessity, placement, and need for improvement. Adding this Navigation Evaluation optional feature will lengthen the design timeline by approximately six working days. Navigation Evaluation Design............................................................. 72 hours 87,920 Page: 19 of 27 Last printed: 10/19/2001 11:26 AM All Events Calendar An AU Event Calendar that would show the city events across all departments. This calendar is a virtual aggregate of the other calendars and will not have an administrative section. Adding the AU Events Calendar optional feature will not significantly affect any dates. All Events Calendar Design............................................................. 2 hours 8220 Implementation ............................................... 3 hours S450 Page Type Builder This is a module for the Content Management System that allows administrators the ability to create new page types. This lets an administrator layout a new type of page and save it so that it can be used throughout the site. Adding the Page Type Builder optional feature will lengthen the design timeline by approximately seven working days. Page Type Builder Design............................................................. 50 hours S5,500 Implementation ............................................... 70 hours $9,700 Fayetteville.org in order safeguard this domain name for exclusive use in our region. Interface had the foresight to secure Fayetteville.org in July of 1996. We feel this short and simple name would be an excellent compliment to the proposed site: We are excited to offer as option, the full and unlimited use of Fayetteville.org. For the use of the Domain ............................... $200/mo. Design Schedule Design Milestones Design Start December 5, 2001 Site Map Finalized:.......................................... December 21, 2001 Schematics Finalized :..................................... January 14, 2002 Functional Spec Finalized :.............................. February 7, 2002 Graphic Design Comps :........................ ......... .. February 22. 2002 Design Completion:......................................... March 13. 2002 Implementation Schedule Estimated Implementation Milestones Implementation Start March 14, 2002 Overall Layout Completed ....................... ........ March 19, 2002 Negotiable Page: 20 of 27 Last printed: 10/19/2001 11:26 AM Page Types Completed :.................................... April 3, 2002 Content Management System Completed:...................................................... April 17, 2002 Site Search Completed: ................................... April 23, 2002 Site Published lave :......................................... May 7, 2002 While testing and debugging of the site is a constant effort, two weeks have been set aside for specific concentration on testing and debugging. This will occur between the completion of the site search and the date to go live (April 23 - May 7). Maintenance policy and procedures can also be developed during this time frame because they are independent from the testing and debugging process. User training and assistance can begin after the Content Management System is completed (approx. April 17, 2002). Note: All dates are subject to change with respect to timely feedback from the City of Fayetteville and Interface's workload during the decision process. Quick feedback will shorten the project's duration, while delayed feedback will lengthen the project's duration. XI.4 Experience Items A -D A. Please elaborate on the type and nature of your company, including background information, other lines of business, areas of operation, and any other information that might help us to understand your qualy1cations to deliver the services Identified in this RFP. Under the Southwestern Bell, Ameritech, Pacific Bell. Nevada Bell, Sterling Commerce, Cingular Wireless, Prodigy and SNET brands, SBC Communications Inc. offers a wide variety of telecommunications products and services to fit almost any need. In addition, under the SBC brand, the company is expanding nationally into 30 top markets outside of its traditional service region. Serving more than 87.3 million voice grade equivalent lines and 10.3 million wireless subscribers, we offer an expansive range of products and services, including voice and data telephone services; local and long-distance wireless communications; Internet access; telecommunications equipment: security systems; voice mail; and directory advertising. Interface Computer Center is a technology solutions company whose goal is to provide a reliable "one -stop -shopping' solution to the needs of the business industry of Northwest Arkansas. We provide networking development, maintenance and re - engineering capabilities as well as website development, hosting & ISP, Intranets and custom software programming. Page: 21 of 27 Last printed: 10/19/2001 11:26 AM Over the past 7 years Interface has'made it a working philosophy to be the best, not •necessarily the biggest. By preserving a highly selective hiring process, promoting employee camaraderie, and providing an energized yet low -stress corporate culture, Interface is able to attract and retain the loyalties of quality individuals who make our company a success. Our engineers allocate 1/5 of their work week to continuing education and the absorption of new technologies to maintain the highest standards of competency. Our managers constantly refine our processes and maintain accountability so that clients can rely on promises made. Sometimes our methodology causes us to be more expensive, but Interface has learned by observation that nothing can be more costly than not doing the job right the first time. Our ten step process backs our proposal with what all clients want; knowledge. assurance and a 7 year history of success. B. Outline your experience as a web site developer, including years in business, areas of operation, and other pertinent information. Interface Computer Center first opened its doors in 1994 and has since become the oldest Internet solutions provider in the state, still in operation with its original owners. The founders, being graduates of the University of Arkansas at Fayetteville's Engineering Department and long residents of Fayetteville. have been committed to the growth of the city from the beginning. As recognition of this and their fervor to succeed, the founders in 1999 became the recipients of the United States Small Business Young Entrepreneur award for the 5 -state region. In 1996. Interface recognized the need of the city to develop an online destination that provided useful information to citizens and promoted the city externally. In response and without financial motivation, www.favetteville.cornwas developed. This site which currently averages 6.000 unique visitors a month has become a popular community portal and information source for out-of-state visitors. For the past 8 years, Interface has steadily and reliably proven the ability to deliver innovative web solutions and award -winning websites to hundreds of clients ranging from the Fortune 500 to local venues. C. Outline your experience as a web site hosting company fif applicable), including years in business, areas of operation, and other pertinent information. SBC's ability to build fully redundant (N+1) Internet Data Centers comes from its experience with providing voice and data lines to our service areas. Under SBC Communications, we service Southwestern Bell, Ameritech, Pacific Bell, Nevada Bell and Southern New England Telephone territories. SBC has been operating secure, fault -tolerant data centers called central offices.for over 100 years. In addition, we own and operate over 100 internal company data centers. 1.100. If you include our Central Offices. Our service for WebHosting is World Wide. Currently we have 2 Internet Data Centers in the United States and are planning the buildout of 4 more, strategically positioned throughout the Unites States. Page: 22 of 27 Last printed: 10/19/2001 11:26 AM Please also see "Platinum IDC" labeled as Item number 3 of the Addendum. D. Please provide the reswnes of the professional and key staff anticipated to be utilized on the project On the part of Web hosting, the engineers that will work with the City of Fayetteville for implementation will meet the requirements for our Level 1 Engineering staff and the appropriate requirements for Database lookup application. The resumes of the key staff members for Interface Computer Center will be included as item number 5 in the Addendum. XI.4 Products Items A -B A. Please provide afull overview of the products and technologies that your company currently will be utilizing. Concerning Web Hosting Please see Addendum 6. "IDC Product Summart" Interface Computer Center employs the most advanced, efficient products for design and implementation of all projects. Our graphic designers use Adobe Photoshop, Macromedia Dreamweaver, and Macromedia Flash to create mocks, graphics, page layouts, page creation and animation. Our programmers use PHP for programming and the latest version of the MySQL for database. These technologies are by far the best for server -side scripting and lightning quick database access, respectively. Their highly adaptable language and open source availability make them compatible yet far superior in many respects to their off the shelf counterparts. Our development web server uses the Linux OS, Apache Web Server, and CVS (Concurrent Versions System), which is used to track all versions and changes to the website and uphold data integrity. For testing across multiple browsers, we use many different versions of Microsoft Internet Explorer, Netscape Navigator, and a few smaller vendors' browsers. In addition, we make extensive use of project management software to supervise all of our projects. which allow us to track every aspect of an ongoing project including the two most important items: schedule and budget. B. Explain your company's ability to upgrade the services requested by issuer and any future capabilities your company is considering. Page: 23 of 27 Last printed: 10/19/200111:26 AM Timeframes for upgrades are typically 2-4 business days for standard offerings of processors, RAM, hard drives and IP addresses. In some cases, due to part availability issues, the timeframe may be longer. XI.5 Vendor Refrences Items A -B A. Vendors must supply with the bid at least three (3) reference accounts (including persons to contact and telephone numbers) in the United States. The reference accounts must have services similar to those bid under this RFP. The services must have been developed and maintained by the bidderfor at least ninety (90) days. Include the following information for each reference: • Company Name • Business Address • Name of Contact • Title of Contact • Telephone Number of Contact • E -Mail Address of Contact • Duration of project. • Description of solutions implemented for project. • Details of software and hardware used for project. • The Purchasing Official reserves the right to request or obtain additional information. • The City may, at its option, contact other known Vendor customers for references. Web Hosting Reference Accounts American First www.amerifirst.orc contactus@amerfirst.org 800-290-1112 PC Corp Dedicated Hosting Package The Beck Group www. necxgroup.com 1700 Pacific Avenue Dallas, TX 75701 Admin@beckgroup.com (214) 965-1100 Custom Dedicated Hosting Package Ancient Faces www.ancientfaces.com 65 Washington Street Santa Clara, CA 95050 Page: 24 of 27 Last printed: 10/19/2001 11:26 AM Afchelp@ancientfaces.com PC Pro Dedicated Hosting Package Web Design Reference Accounts Leggett & Platt Aluminum Group I. Pace Industries, Inc. One Mcllroy Plaza. Fayetteville, AR 72701 / PO Box 309, Fayetteville, AR 72702 John McCutcheon VP Marketing & Sales 501-443-1455 mccutcheonj@pacethdustries.com Duration of project legaluminum.com - Interface designed the original site with revisions and maintenance ongoing since September 1997. There have been numerous upgrades to the site with the most recent full revision of site between November, 2000 and October, 2001. Client has a main corporate site and 20 daughter sites for individual plants. Description of soiutions implemented for protect The client needed an interactive site with each individual plant having a daughter site under the main site where potential clients can find the information needed and request a quote: Another portion of the site is a secure internal system for transferring large files between clients and the plants that need files to develop a requested part. Details of software and hardware used for project Various design, programming and HTML editing software was used to create site and daughter sites. including DreamWeaver and PHP. The site is hosted on Linux servers running RedHat Linux with Apache, MySQL. and PHP. Daisy Outdoor Products 400 West Stribling Drive, Rogers, AR 72756 Joe Murfin VP Marketing 501-636-1200 jmurfn@daisy.com Duration of project Daisy.com- Interface designed the original site with revisions and maintenance ongoing since 1996. There have been numerous upgrades to the site with the most recent full revision completed November, 2000. There are monthly updates. Description of solutions implemented for project The client needed a site to educate customers and potential customers about their business, product and product safety that is easily upgraded. Details of software and hardware used for project Various design, programming and HTML editing software was used to create site and daughter sites, including DreamWeaver and PHP. The site is hosted on Linux servers running RedHat Linux with Apache, MySQL. and PHP. Page: 25 of 27 Last printed: 10/19/2001 11:26 AM • C] Arkansas Capital Corporation 225 South Pulaski Street Little Rock, Arkansas 72201-1925 Sam Walls (C.O.O.)/ Tonya Brown (Director of I.T.) (800) 216-7237 swalls@arcapital.com / tbrown@arcapital.com Duration of project arcapital.com December through August, 2001 for Phase 1. Description of solutions implemented for project One of the primary missions of this website is to relay the content in a manner that enables any user access to the information while at the same time providing a sense of solidity and security through the website's design. Details of software and hardware used for project Various design, programming and HTML editing software was used to create site and daughter sites, including DreamWeaver and PHP. The site is hosted on Linux servers running RedHat Linux with Apache. MySQL, and PHP. B. Vendors shall also provide the URL's of a minimum of 6 sites that the vendor has developed and designed for non -vendor owned clients in the past 24 months. For each site referenced, please indicate the scope of the work provided, time frame for development, and the approximate costs involved Please reference Addendum item number 6. XI.6 Scope Of Services Item A A. Please address all the questions and requirements outlined in SECTION II. "Scope of Services." This has been complied with in SECTION II of this proposal. SECTION XII Selection Methodology Both SBC and Interface Computer Center have read and understand. SECTION XIII Technical Requirements Page: 26 of 27 Last printed: 10/19/2001 11:26 AM Arkansas Capital Corporation ' 225 South Pulaski Street Little Rock, Arkansas 72201-1925 Sam Walls (C.O.O.)/ Tonya Brown (Director of I.T.) (800) 216-7237 swalls@arcapital.com / tbrown@arcapital.com Duration of project arcapital.com December through August, 2001 for Phase 1. Description of solutions trnplemented for project: One of the primary missions of this website is to relay the content in a manner that enables any user access to the information while at the same time providing a sense of solidity and security through the website's design. Details of software and hardware used for project Various design, programming and HTML editing software was used to create site and daughter sites, including DreamWeaver and PHP. The site is hosted on Linux servers running RedHat Linux with Apache, MySQL, and PHP. B. Vendors shall also provide the URL's of a minimum of 6 sites that the vendor has developed and designed for non -vendor owned clients in the past 24 months. For each site referenced, please indicate the scope of the work provided time frame for development, and the approximate costs involved. Please reference Addendum item number 6. XI.6 Scope Of Services Item A A. Please address all the questions and requirements outlined in SEMON II. "Scope of Services." This has been complied with in SECTION II of this proposal. SECTION XII Selection Methodology Both SBC and Interface Computer Center have read and understand. SECTION XIII Technical Requirements Both SBC and Interface Computer Center have read, understood, and complied. Page: 26 of 26 Last printed: 10/19/2001 11:30 AM a RESOLUTION NO. 39-02 A RESOLUTION TO APPROVE A CONTRACT WITH IFWORLD, INC. FOR WEB -SITE DESIGN AND CONSTRUCTION FOR S99,000.00 BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF FAYETTEVILLE, ARKANSAS: Section 1. That the City Council of the City of Fayetteville. Arkansas approves the Contract with IFWORLD, Inc. in the amount of $85,680.00 with a contingent amount of $13,320.00 and authorizes the Mayor to sign this Contract attached as Exhibit A. PASSED and APPROVED this the 5th day of March, 2002. APPROVED: A By: i DAN COODY, Ma r ather Woodruff, City Cle I of 10 • CITY OF FAYETTEVILLE WEB SITE COYIRACT I of 10 O65.39 oz WEB SITE DESIGN & CONSTRUCTION AGREEMENT THIS AGREEMENT is made and entered into this 5L day of March, 2002 by and between IFWORLD INC. (hereafter "IFWORLD") and THE CITY OF FAYETTEVILLE (hereafter "CLIENT"), subject to the terms and conditions more specifically set forth herein. DESIGN STAGE. (1) CLIENT wishes to engage IFWORLD and IFWORLD agrees to perform the services which are reasonable and necessary to create a website for CLIENT in accordance with the Project Requirements set forth in Appendix B, attached hereto and made part hereof. (2) CLIENT agrees to pay and IFWORLD agrees to accept the total sum of the Core Features and the initialed optional items below as consideration for the services to he performed in the Design & Implementation stages as set forth in Appendix A. Core Features Design & Implementation............ $85,680 The total sum of the Core Features is to be payable as follows: S ***Nothing*** upon signing this Agreement (3) PAYMENT. Professional Services Fees for Design will he invoiced monthly for services as incurred on a time and material basis. If changes to the hours for Professional Services stated in REP are needed, a change order signed by both parties will be required. Any Professional Services provided in excess of the hours stated will be charged at the unit price stated in the RIP. The Remaining Balance of the Implementation Cost to be billed to CLIENT immediately due and payable upon presentation of the website. (4) CLIENT agrees that any of the following actions must be authorized by CLIENT, acknowledges that the same will cause a change in both the cost and time -frame for the Project Design and Implementation, and agrees to pay for any increased costs, to he billed as set forth above, due to the following actions: a. Change(s) to the Project Requirements after signing this Agreement. b. Change(s) to the Site Map after approval by CLIENT. c. Change(s) to the Schematics Document after approval by CLIENT. d. Change(s) to the Functional Specifications Document after approval by CLIENT. c. Change(s) to the Graphic Design Comps after approval by CLIENT. WORLD INC FROM : MCNAIR & ASSOC FAX NO. 5015218617 Oct. 11 2001 04:58-'M Pt iO71SIDWfY3 ACORD CERTIFICATE OF LIABILITY INSURANCE I,7zoo1 PROC'Xe* (501)521-7800 FAX (SO1)S21-8617 THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS NO RIGHTS UPON THE CERTIFICATE McNair & Associates HOLDER. THIS CERTIFICATE DOES NOT AMEND. EXTEND OR P.O. Box 819 ALTER THE COVERAGE AFFORDED BY THE POLICIES BELOW. 201 N. East Ave. INSURERS AFFORDING COVERAGE Fayetteville, AR 72702-0819 LN54.flb I@,ANC, .Is,acaTransportation insurance Co DEA INTERFACE COMPUTER CENTER I,s- t: 4058 NORTH COLLEGE AVE., SUITE 250 vauNca c: FAYETTEVILLE• AR. 72703 unamty ,� •. ,.� -, - © •.. -�. ,. • , I. " I. 1• ® 11.1 L11 ... .®. _. . . ■■ �•- ,. 111 111 . • � •...�• 111 111 .. • - .•• .• I1.IS,rI111 111 ?L JL(. tIjl - r• ii. 1 1 1 1' 1' 11 •.. ..-. 111 111 I CITY OF FAYETTEVILLE . PEccY via • PURClusnlG MANAGER 113 WEST MOUNTAIN STREET FAYETTEVILLLE, AR 72701 ACORO 255 (T7) SNOUID ANY OP THe ABOVe O'-C-'•GD POLICES BE CYNCE l a D•PDM TNe OOIRATION DATE TNGReaP. THE INUNO COMPANY VALL GMDGAVOR TO MAR i= DAYS w ,I IIOTICG TO TIp CC t, o4.ATR NO1LQ Iu1D TO 7MR LOT, BUT FA'IIIRf TO MM. S{RJI NOQC• tML I&r IN) ••fl$' N OR W4fY • Villanova ( ce INFORMATION PAGE Insurer: VILLANOVA INSURANCE COMPANY 111 E. Kilbourn Avenue, Suite 1150 Milwaukee, WI 53202• (Carrier Code: 36935) Ph: -(407) 788-1717 The. Insured: Interface Computer Center Ifworld, Inc. dba Mailing Address: 530 N. College, Bldg. C Fayetteville, AR 72701 Other workplaces not shown above: NO OTHER WORKPLACES FOR THIS POLICY RENEWAL AGREEMENT Producer: Agent// 1618 Farris Insurance Agency Inc PO Box 345 Springdale, AR 72765 Carrier Policy 0: WC31509643 Carrier Prior Policy #: WC21509643 File //: 750001509643101 Type of Business: Corporation Fein: 710758691 Risk ID: 2. The policy period is from 12:01 a.m. on 6/02/2001 to 12:01 a.m. on 6/02/2002 at the insured's mailing address. 3. A. Workers Compensation Insurance: Part One of the policy applies to the Workers Compensation Law of the states listed here: 0 B. Employers Liability Insurance: Part Two of the policy applies to work in each state listed in Item 3.A. The limits of our liability under Part Two are: Bodily Injury by Accident $ 500.000 each accident Bodily Injury by Disease $ 500.000 policy limit Bodily Injury by Disease $ 500.000 each employee C. Other States Insurance: D. This policy includes these endorsements and schedules: WC000000A(04/92) WC000308(04/84) WC000414(07/90) WC030601A(04/92) 4. The premium for this policy will be determined by our Manuals of Rules, Classifications, Rates and Rating Plans. All information required below is subject to verification and change by audit. Classifications Code Premium Basis Rate Per Estimated No. Total Estimated $100 of Annual Annual Remuneration Remuneration Premium SEE SCHEDULE OF OPERATIONS Total Estimated Annual Premium $ Minimum Premium $ Expense Constant $ MM Printed on: April 11, 2001 Countersigned by/ 1,_I acs J .Q �i • IFWORLD• INC DBA INTERFACE COMPUTER CENTER Leaders of Tomorrows Technology -One Corponts Square, Suits 250 ♦059 N. College October 12, 2001 Fayettevill& AR 72201 nttpl/wa.ifwosld.cam Telephone: (501)592-5100 Facsimile: (501)592-5599 City of Fayetteville 113 West Mountain Street Fayetteville, AR 72701 I hereby certify that IFWORLD, Inc. DBA Interface Computer Center is a corporation that is independent of the City of Fayetteville, the City's elected officials, and the. City's employees. s-i IFWORLD, Inc. DBA Interface Computer Center • • i i i i ADDENDUM 4. INTERFACE COMPUTER CENTER SAMPLE CONTRACT WEB SITE DESIGN & CONSTRUCTION AGREEMENT THIS AGREEMENT is made and entered into this _ day of , 20_, by and between IFWORLD INC. (hereafter "IFWORLD") and (hereafter "CLIENT"), subject to the terms and conditions more specifically set forth herein. (1) IFWORLD has developed a two -stage process for the Design and the Implementation of a web site as more fully set forth on Appendix A, entitled "Project Process," attached hereto and made part hereof. Stage One is the Design Stage which results In the creation of the "Project Design Document" that includes the descriptions necessary to the Initial planning, developing, programming, and building of CLIENT's web site. Stage Two is the Implementation Stage, which involves the implementation of the project design and results in the creation of the CLIENT's "Web Site." DESIGN STAGE. (2) The parties agree that the Design Stage consists of five (5) sequential steps, as set forth in Appendix A, culminating in the "Project Design Document." The parties agree that CLIENT's approval of each step must be received before IFWORLD undertakes the following step. (3) CLIENT wishes to engage IFWORLD and IFWORLD agrees to perform the services which are reasonable and necessary to create a Project Design Document for CLIENT in accordance with the Project Requirements set forth in Appendix B, attached hereto and made part hereof. (4) CLIENT agrees to pay and IFWORLD agrees to accept the total sum of $ as consideration for the services to be performed in the Design Stage, said sum to be payable as follows: $ Upon signing this Agreement REMAINING BALANCE To be billed to CLIENT in monthly invoices over the anticipated time schedule allowed for the project, with the entire remaining balance immediately due and payable upon presentation of the Project Design Document. (5) CLIENT agrees that any of the following actions must be authorized by CLIENT, acknowledges that the same will cause a change in both the cost and time -frame for the Project Design, and agrees to pay for any increased costs, to be billed as set forth above, due to the following actions: Change(s) to the Project Requirements after signing this Agreement. b. Change(s) to the Site Map after approval by CLIENT. Change(s) to the Schematics Document after approval by CLIENT. Change(s) to the Functional Specifications Document after approval by CLIENT. e. Change(s) to the Graphic Design Comps after approval by CLIENT. Change(s) to the Project Design Document after approval by CLIENT. (6) CLIENT agrees to provide to IFWORLD with all data, specifications, and information, including text, graphic content, and any media which is to be included in CLIENT's web site within a reasonable time after and in no event more than thirty (30) days from the date of signing this Agreement. (7) CLIENT understands and agrees that work will not commence until IFWORLD, in its sole discretion, determines that it has received data, specifications, and information, including text, graphic content, and any media from CLIENT sufficient for it to undertake the Design Project. (8) Should CLIENT fail to provide the data, specifications, and information, including text, graphic content, and any media, required pursuant to Paragraph Six (6), IFWORLD Inc shall have the right to declare the entire amount due IFWORLD under this agreement immediately due and payable. In that event, IFWORLD shall be under no obligation to complete its performance contemplated hereunder until such balance is paid in full and CLIENT has furnished such data, specifications, and information, including text, graphic content, and any media, sufficient, as determined in IFWORLD's sole discretion, for IFWORLD to complete the Project Design. (9) Upon the completion of the Project Design and upon CLIENT's payment of all outstanding design fees, IFWORLD will provide CLIENT with a Project Design Document. At completion of the Project Design and upon receipt of full payment of outstanding design fees, IFWORLD will also furnish CLIENT with an Implementation Schedule and Budget for the Implementation Stage. All verbal, written, or implied costs for the Implementation Stage other than what is specified in the Implementation Schedule and Budget are mere estimates and are not binding on IFWORLD or CLIENT. CLIENT will have the option to approve the Implementation Schedule and Budget to order to proceed with the Implementation Stage. ' IMPLEMENTATION STAGE (10) If the Implementation Schedule and Budget is acceptable, it shall be approved in writing by CLIENT, shall be attached to this Agreement as Addendum 1 and become part hereof, and shall be subject to the terms and conditions set forth herein. In the event CLIENT approves the Implementation Schedule and Budget, CLIENT agrees to pay and IFWORLD agrees to accept the total sum set forth in the Implementation Schedule and Budget for the creation of CLIENT's web site as specified in the approved Project Design Document. (11) CLIENT agrees that any changes to the approved Project Design Document must be authorized by CLIENT, acknowledges that the same will cause a change in both the anticipated schedule and cost for the Implementation Stage, and agrees to pay IFWORLD for any increase in cost above that specified in the Implementation Schedule and Budget, Addendum 1 hereto. (12) CLIENT agrees that publication of the web site will not occur until IFWORLD has been paid in full under the Implementation Schedule and Budget. GENERAL CONDITIONS: (13) IFWORLD retains the right to suspend any given Schedule due to the delay by or tardiness on the part of CLIENT when IFWORLD must await a necessary approval by CLIENT at a step or stage of the process before continuing. In that event, IFWORLD Inc will resume work as soon as practicable after CLIENT's response has been received. (14) CLIENT acknowledges that the web page constructed by IFWORLD Inc contains designs, formatting, programming and other materials constituting intellectual property of IFWORLD Inc, and hereby waives and relinquishes any rights CLIENT may have in and to such intellectual property, and further agrees that said web page in its final form may have thereon such logos or other identification as to indicate IFWORLD Inc to be the author of such web page, and further, may include a link to the home page of IFWORLD Inc on the World Wide Web. CLIENT agrees that, regardless of where published or hosted, such logos, identification and/or links will not be removed from the web page. By including such on the web page of CLIENT, IFWORLD Inc does not grant CLIENT any license with respect to the use by CLIENT of any trademarks, copyrights, proprietary information or intellectual properties of IFWORLD (15) CLIENT agrees and acknowledges that IFWORLD will retain rights and title to any and all text, graphics, photos, designs, trademarks or other artwork that might be or is subject to the intellectual property rights of IFWORLD, and, absent the express written consent of IFWORLD, CLIENT agrees and acknowledges that it will not copy, transfer, modify or publicly display such works beyond the publication on the internet of the finished web page as contemplated by this agreement. (16) CLIENT represents and covenants that it is the owner, assignee, or licensee of all elements of the web page supplied by it to IFWORLD Inc, including text, graphics, photos, designs, trademarks, or other artwork or materials, or has otherwise been granted permission to utilize the same by the owner or owners thereof, and agrees to indemnify and hold harmless IFWORLD from any and all claims or suits arising from the use of such elements furnished by the CLIENT, such to include reasonable attorney fees incurred by IFWORLD in defending itself and pursuing performance of this provision from CLIENT. (17) CLIENT hereby grants to IFWORLD a limited license to utilize any of the CLIENT's trademarks, copyrighted material or proprietary information in the construction of CLIENT's web page and as requested by CLIENT. If so requested, IFWORLD will include such mutually agreed upon forms of notice on the web page to protect copyrights, trademarks and other proprietary information. (18) IFWORLD MAKES NO WARRANTIES, EXPRESS OR IMPLIED, CONCERNING THE COMPLETED WEB PAGE AS ACCEPTED BY CLIENT, AND CLIENT EXPRESSLY BY SIGNATURE HEREON AND ACCEPTANCE OF THE WEB PAGE AS CONTEMPLATED HEREIN DOES HEREBY RELEASE AND FOREVER DISCHARGE IFWORLD INC, ITS EMPLOYEES, OFFICERS, ASSIGNS AND RELATED ENTITIES OF AND FROM ANY AND ALL LIABILITY ARISING FROM THE -USE BY CLIENT OF THE WEB PAGE AS CONSTRUCTED BY IFWORLD UNLESS EXPRESSLY SET FORTH AND ADOPTED HEREIN, IFWORLD INC MAKES NO WARRANTIES OF ANY TYPE OR NATURE, INCLUDING EXPRESS WARRANTIES, IMPLIED WARRANTIES, WARRANTIES OF FITNESS, AND WARRANTIES OF MERCHANTABILITY, CONCERNING THE PERFORMANCE OF ITS SERVICE PURSUANT TO THIS AGREEMENT. NEITHER IFWORLD INC, ITS EMPLOYEES, OFFICERS, DIRECTORS OR AGENTS SHALL BE LIABLE TO CLIENT OR ANY THIRD PARTIES FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR INABILITY TO USE, THIS SERVICE. (19) NOTWITHSTANDING THE FOREGOING PARAGRAPH, IN THE EVENT THAT IFWORLD INC SHOULD BE HELD LIABLE TO CLIENT OR THIRD PARTIES RELATED TO THE USE OR INABILITY TO USE THE WEB PAGE OF CLIENT, THEN AND IN THAT EVENT RECOVERABLE DAMAGES, IF ANY, SHALL BE LIMITED TO THE ACTUAL INJURY SUFFERED BY CLIENT OR THIRD PARTY, PROVED TO A REASONABLE CERTAINTY, OR FIVE PERCENT (5%) OF THE TOTAL AMOUNT PAID HEREUNDER, WHICHEVER IS THE LESSER AMOUNT. (20) This agreement and the continuing obligations set forth herein shall survive and continue beyond the payment of the monies due hereunder from CLIENT to IFWORLD and the construction of the web page by IFWORLD, and such continuing obligations may be enforced by either party against the other should a breach of such occur or be imminent. (21) To the extent that any provision herein might be declared invalid or unenforceable by a Court of competent jurisdiction, the remainder of this agreement shall remain in full force and effect, including the continuing obligations hereunder. (22) This agreement shall, regardless of where executed, be interpreted, construed and enforced in accordance with and subject to the laws of the State of Arkansas, and venue for any action hereunder shall lie in Washington County, Arkansas. THIS AGREEMENT constitutes the complete agreement between the parties hereto for the services covered herein, superceding any and all prior communications and agreements between the parties with respect to these services, and shall be construed and interpreted as a separate agreement from any and all other agreements which might now, or later, exist between the parties, UNLESS it be incorporated by specific reference into such other agreements. This agreement shall not be binding upon IFWORLD until accepted by a Corporate Representative other than the signing sales representative. WITNESS OUR hands on the date first above written: IFWORLD INC. CLIENT By Sales Representative (Name of Corporate Representative or Individual If not a business entity ACCEPTED by IFWORLD Inc on the date first above written. --IFWORLD INC. Corporate Representative Title ADDENDUM 5. INTERFACE COMPUTER CENTER RESUMES SHARA FISHER shara@ifworld.com 4058 N College, Suite 250 a Fayetteville, Arkansas 72703 •'(501) 582-5599, fax (501) 582-5599 EXPERIENCE 1997 —Current IFWORLD Inc. Fayetteville, AR din Interface Computer Center Sales Manager • Increased sales from $600,000 to almost $1.5 million. • Handled all levels of accounts throughout the years, currently land and maintain major accounts while achieving over 80% client retainage. • Train and lead sales representatives to sell our various services and products. • Project -manage three out of four divisions to ensure teams are working efficiently and profitably — the fourth division, Web Development, is project -managed by another individual in which the sales department works closely with to ensure sales is supporting the department in the best way to benefit their team. • Introduced new procedures for the web development team that increased development staff production by a great margin — since that time, the team has modified those and installed their own procedures that are even more effective and keep projects within budgets and timelines under the current leadership of their project manager. 1995-1997 Chocolates Turin, S.A. de C.V., US Division Fayetteville, AR National Sales Manager • Worked with VP of Sales to introduce a new product line to the US from Mexico. • Interviewed, hired and managed over 20 brokerage firms. • Researched and learned alcohol laws for all 50 states as they pertain to confectionery in order to develop a sales and distribution plan for each state (if legal). Produced effective trade show presentations that increased brokerage sales. • Worked with home office in Mexico City to develop distribution plans. • Researched stores, distributors and brokers to find demand for product. EDUCATION 1991-1997, Current University of Arkansas at Fayetteville Fayetteville, AR • B.S.B.A., Accounting — 6 hours lacking, will graduate May 2002. • Took leave from the University lacking 12 hours to train and commit the time necessary for current position at IFWORLD Inc. INTERESTS Junior League of Northwest Arkansas, American Heart Association — Golf Committee Chair, playing golf, gardening, reading. JEREMY LAYN E W EATH ERS Experience Lead Programmer present IFWORLD April 1999 I began my tenure at IFWORLD as a web designer working with static pages utilizing the HTML 3.2 spec. During the first six months I began work on dynamic sites and, in October of 1999, was promoted to Lead Programmer. I am currently active in consulting clients, developing technical design documents for both human interface and application functionality, and building sites based on those technical designs. Volunteer Consultant & Web Developer Mission Data International Mission Data International operates ShortTermMissions.com, a site dedicated to helping people find and prepare for all types of mission trips across the world. I am working with the full-time staff to design and implement a complete overhaul of their existing site. Developer PHPUb PHPLib is an open -source (GPL licensed) development framework for web applications written in PHP. In addition to minor fixes and improvements to the API, I am currently working on a completely integrated error handling, tracking and reporting system. present May 2001 present July 2001 Freelance Extranet Developer February 2001 Cutco Australia October 2000 Cutco Australia is a direct sales organization with offices in New South Wales, Victoria and Western Australia. I developed a web -based application for managing recruitment and training of new sales reps. Adjunct Instructor of Communications John Brown University August 1999 I taught introductory web design as part of the digital media program and digital photography as part of the journalism program. I was responsible for both classroom instruction and developing the course curriculum. December 2000 Online Editor February 1999 The Mac Report June 1998 The Mac Report was a weekly magazine devoted to using the Macintosh platform in application development, education, enterprise, entertainment, Internet, and print media applications. I managed the Internet servers, maintained the website, and occasionally wrote for the publication. Vice President of Administration December 1998 Twin Media Group April 1997 Twin Media Group was a digital media firm located in Siloam Springs, Ark. focused on producing content for CD-ROM, video, the Internet, and print media. In addition to my role as co-founder and business administrator, I worked as a member of the production team and managed all Internet servers. During 20 months of operation we produced half a dozen videos, a dozen CD-ROM productions, and 30 websites. Education Bachelor of Arts John Brown University Philosophy Spring 1997 Fall 1993 My foremost goal, whether in my professional career or in my private life, is to learn. I do not seek the accumulation of raw knowledge, but the strengthening of my mind that comes from reflecting upon and analyzing knowledge and experience. In the implementation of every project that I encounter, I look for at least 2 or 3 ways in which I can substantially improve my methods and apply higher -level theory than in my previous project. My main areas of concentration are the end user experience, data control and code quality. End User Experience • Mike tasks easier, quicker, more intuitive • Create standard, backwards -compatible pages • Eliminate cryptic errors Data Control • Check data often and redundantly • Distrust all input • Exercise excessive paranoia Code Quality • Reduce unnecessary complexity • Generalize objects and methods • Enhance and expand useful complexity Skills I use the following on a daily basis in creating web applications: • Hyper Text Markup Language for web page structure and layout (5+ yrs); • JavaScript for client -side browser scripting (q+ yrs); • Cascading Style Sheets for consistent web page presentation and layout (2+ yrs) • PHP Hypertext Preprocessor for server -side building of dynamic web pages (2+ yrs); and • Structured Query Language for database integration (2+ yrs). • • BRIAN S. SAGE 307 Sw 0 STREET BENTONVILLE AR 72712 BRIAN a@IFWORLD.COM (501) 582-5100 1997-1998 Argon Design Siloam Springs, AR General Partner/Entrepreneur Argon Design began in my college dorm room and evolved into the full-time entrepreneurial effort of three good friends upon graduation. After the summer following graduation, we dissolved our company, as we realized our need for more experience and larger clients. Nevertheless, I have had a heart for small start-up environments ever since, and the experience was something I will always remember. 1998.1999 Tyson Corporate Communications Springdale, AR Graphic Designer/Illustrator • Chief Designer: Food Service Today Newsletter • Produced video, Web design, print design, 3D animations, even promotions design. Illustrations, meeting planning and decorating. • Achievements: Established archive protocol, assisted streamlining departmental job tracking system, Chief Designer. Tyson Logo and Trademark Standards Guide. • Annual Salary: $23,700.00=628,000.oO 1999-Pvae5BNT IFWorld. Inc. Fayeaeville, AR Lead Web Designer • Worked closely with many clients as Lead Designer and Project Manager for multimedia and reference Web sites. • Some Clients Include: Daisy M. Co., DRS sec, United Industries. Arkansas Capital Corporation Group, and Pace Industries. • woo Awards: Addy award and local 4% -scar review for Daisy.com site design; Webmascer Award for Daisy.com, ArtisanBridge.com. • Annual Salary: $31,wo.00=$33,300.Oo FORMAL EDUCATION 1994.1998 John Brown University Siloam Springs, AR as.: Graphic Design; Minor: Business Administration • Residence Hall Association Promotional Director. • Student Website Manager. • Art Director, entrepreneur, founding member. Student Yearbook, 1996-1997. • Art Director: SIFB multimedia presentation (international competition top to),1998 • Art Director, Ad Supervisor, Webmascer: Student Yearbook toot -2002 Webster University Fayetteville, AR PBasuszNc: Masters Degree Business Administration • Business Information Systems Project Manager. • Student Leader Among Peers. • Cl A FEW WEBSITES • WWW.ARCAPITAL.COM • • WWW.CAMPOZARK.COM • WWW.PACEINDUSTRIES.COM • WWW.DAISY.COM • WWW.DRSLLC.COM PROFICIENCIES THAT MATTER • WWW.IFWORLD.COM • WWW.STADIUMSTORES.COM • WWW.OZARKAIRCRAFrSYSTEMS.COM • WWW.COPPERFAB.COM • WWW.ULTRABOARD.COM • Project Leadership ■ Flash 5 • Web Site Planning • HTML /JavaScript/DHTML • User Interface Design • Adobe Photoshop 6 • Web/Interactive Graphics • Freehand/Illustrator 9 • Business Process and Planning • Quark xPress • Corporate Identity • Adobe Premiere 6 • Illustration and Photo -Manipulation • ;D Studio MAX 4 • Interactive CD Projects • Ms Word, Excel & PowerPoint • 3D Modeling • Ms Project • Presentation Graphics REFERENCES INTERESTS • Tony Toth (501) 646-9274 General Manager, CopperFab, Inc. Former Freelance Contract • Stuart Sage (501) 636-5776 General Manager, Jotto Desk. Inc. Former Project Manager • Joel Sawyer (913) a6a-3900 Project Manager, Youthfront. Kansas City Former Business Partner I am currently persueing a Masters in Business Administration degree, and In addition to my formal education, I am an avid reader. I love to read books related to personal growth, business theory, leadership, finance, ethics, and a few adventure novels now -and -again. Among my favorite authors are: Peter Lynch, Stephen Hawking, Robert T. Kiyosaki, J. R. It Tolkien, and Steven Covey. My favorite projects are anything involving the Web and new or electronic media, corporate identity, and typography. Personally I enjoy poetry, computer• hardware, anything in a museum, music, and challenging & intelligent discussions about anything. BRIAN SAGE 2 Gregory T. Billingsley • greg@ifworld.com • EDUCATIO Bachelor of Science in Computer Systems Engineering University of Arkansas December 1998 GPA: 3.6/ 4.0 EMPLOYMENT AND CLASS PROJECTS Aug 99 - Present: IFWORLD Inc. Fayetteville, AR Fayetteville, AR June 01 - Present: Project Manager Responsible for every working aspect of all projects that flow through the Internet Client Services (ICS) division. Lead the ICS team in designing internet, intranet, and extranet sites. Created and implemented a new process for handling projects and managing their schedule and budget. Aug 99 - June 01: Computer Systems Engineer Programmed a variety of internet sites for both clients of ICS and internal projects. Project topics include, but are not limited to, e -commerce, auction, gaming, content management, and job search/post. Responsible for large improvements in coding methods and libraries. Jan 99 - May99: Software Development HEBCO, Inc. Springdale, AR Helped start up a new branch of Hebco, Inc. Worked on developing new technologies and researching new methods of operation. Also responsible for marketing and working on existing contracts. Fall 1998: Computer Architecture Semester Group Project Created a MIPS pipelined processing unit. Includes incorporation of instruction control unit, forwarding unit, and hazard detection unit. Simulated with Mentor Graphics. Spring 1998 — Fall 1998: Senior Design Project Designed and implemented a flight simulator from scratch using MFC and OpenGL. Responsible for all dynamic elements including flight physics algorithms and rotational/translational matrices. Also incorporated the Microsoft Force Feedback Joystick. Summer 1996: Research and Development HEBCO, Inc. Oklahoma City, OK Developed and tested custom software applications and documentation relating to OCR and OCR proofing for a technical government contractor using Visual C++. Devised new process to implement software and significantly increase production. Summer 1995: Software Development HEBCO, Inc. Iionors Oklahoma City, OK Developed a complete suite of scanning programs using Image Basic and Visual Basic that scan, manipulate, and save images in various image formats. • Member, Golden Key Honor Society (National Honor Society) • Member; Gamma Beta Phi (University Honor Society) • University Scholar (Four-year full scholarship) Computer Experience • • Platforms • Linux • Windows • Unix Computer Languages/Protocols • PHP • MySQL • HTML • Javascript • Java • C/C++ • Visual Basic • OpenGL • Intel x86 Assembly Language • Motorola 68000 Assembly Language • MIPS Assembly Language CLIENT REFERENCES 1. LEGGETT & PLATT ALUMINUM GROUP URL: legaluminum.com Scope: Design/ Programming/Implementation/ Maintenance Duration: 9 months Approx. Budget: $ lxx,xxx 2. DAISY MANUFACTURING URL: Daisy.com Scope: Design/ Programming/ Implementation/ Maintenance Duration: On -going Approx. Budget: $lxx,xxx 3. UNITED INDUSTRIES URL: Mountingboards.com & Ultraboard.com Scope: Design/ Programming/ Implementation/ Maintenance Duration: 6 months Approx. Budget: Sxx,xxx 4. ARKANSAS CAPITAL CORPORATION URL: ARcapital.com Scope: Design/ Programming/ Implementation/ Maintenance Duration: 13 months Approx. Budget: Slxx,xxx 5. TATE HEALTH CARE URL: TateHealthcare.corn Scope: Design/ Programming/ Implementation/ Maintenance Duration: 8 months Approx. Budget: Sxx,xxx 6. DIVERSIFIED RETAIL SOLUTIONS URL: drsllc.com Scope: Design/ Programming/ Implementation/ Maintenance Duration: 2 months Approx. Budget: Sxx,xxx APPENDIX A PROPOSER GUARANTEES The proposer certifies it can and will provide and make available, at a minimum, all services set forth in Section M. "Scope of Services." .. Signature Name (typed): Shara Fisher, Title: Sales Manager Firm: IFWORLD INC. D.B.A. Interface Computer Center Date: 10-19-01 APPENDIX B PROPOSER WARRANTIES A. Proposer warrants that it is willing and able to comply with State of Arkansas laws with respect to foreign (non -state of Arkansas) corporations. B. Proposer warrants that it is willing and able to obtain an errors and omissions insurance policy providing a prudent amount of coverage for the willful or negligent acts, or omissions of any officers, employees or agents thereof. C. Proposer warrants that it will not delegate or subcontract its responsibilities under an agreement without the express prior written permission of the City of Fayetteville. D. Proposer warrants that all information provided by it in connection with this proposal is true and accurate. Signature Name (typed):_Shara Title: Sales Firm: IFWORLD INC. D.B.A. Interface Computer Center Date: 10-19-01 S • t _ A U l APPENDIX C. SCHEDULE OF FEES AND EXPENSES (WEB DEVELOPMENT) r APPENDIX C SCHEDULE OF FEES AND EXPENSES For 2001 Web Site Development and Maintenance Web Site Development: Proposed Quoted Hourly Hours Rates Total Partners $ $ Managers $ $ Supervisory $ $ Staff $ $ Other (specify):_Design 393 $ 110/hr $ 43,230 Other (specify):_Implementation_ 319 $ 110 & 150/hr $ 42,450 Other (specify):All Optional Features $ $ Total all-inclusive maximum price $ 85,680 Web Site Updating & Maintenance: Proposed Quoted Hourly Hours Rates Total Hourly Update - Staff $ 110/hr Multiple Hours Rate - Staff FAYETTEILLE • THE CITY OF FAYETTEVILLE, ARKANSAS DEPARTMENTAL CORRESPONDENCE TO: Fayetteville City Council THRU: Dan Coody, Mayor Ted H. Webber, Administrative Services Director FROM: Budget & Research �7 DATE: February 12, 2002 SUBJECT: Web Site Design & Construction Contract - IFWORLD Attached is a Web Site Design & Construction contract with IFWORLD that will provide the City with Web Site Design & Construction services. The following information contained in this memo describes the background, benefits, and costs of this project. Background: In 1996, the ALADDIN project was developed between the University of Arkansas and community members with an interest in improving access to the information that affects our daily lives: politics, education,environment, and more by making it available online through the Internet. The City chose to place its web site on the University of Arkansas' server. This has greatly benefitted the City for the last several years. Unfortunately, the need for an increased web site presence has led us to out source our web design services. A major overhaul of the web site was initiated in 1998 by in-house personnel to meet the current needs of the citizens of Fayetteville. The web site was limited in the amount of information it contained due to space limitations on the server and the unavailability of web design resources. City staff began investigating in 1999 the benefits the City would get through a more pronounced presence on the Internet. By the first quarter of 2000, the City received its first direct connection to the Internet by acquiring all line into the City Administration Building. In addition, a new domain name was acquired for future web site use (http://www.ci.fayetteville.ar.us). In early 2001, an ad -hoc committee, made up of City Staff and citizens, was formed to determine the services and information that should be available via the City's web site. The committee focused its attention on the Web site's design, the content provided, and other areas such as e -commerce that may be included on the site. One of the items accomplished by the committee was the development of a Strategic Plan for On -Line Services. This Strategic Plan will serve as a "road map" to guide City staff in the development and maintenance of the City's web site. In addition to the Strategic Plan, the committee chose a website nickname that would be easy to remember by everyone. The domain name that was chosen is (http://www.accessfayetteville.org). During the later part of 2001, a selection committee was formed to review Request for Proposals (RFPs) for Web Site Design & Hosting Services. The selection committee was made up of City Staff, ad -hoc web committee Chair Kevin McDonald, and Alderman Bob Davis. Fifteen proposals were sent out with seven responses received. The committee selected IF WORLD, Inc. for the Web Site Design and Southwestern Bell Communications (SBC) for the Web Hosting. The committee felt that these companies are the best at meeting the needs of the City of Fayetteville. Features & Benefits: Today the City's Internet site is composed almost entirely of static web pages. Current staff has done a good job in bringing it to the point it is today, but the City is interested in building an Internet web site that is not only informative but affords the citizens the opportunity to have meaningful access to a full array of government services. The City of Fayetteville is committed to building a world class web site that is designed upon the ease of use from the viewpoint of the citizens and City staff. It is City Staff's opinion that our current web site navigates much like a hierarchical organizational chart, forcing the citizen to understand how government works in order to navigate to the appropriate area to find the information or service they are seeking. The City's new web site will be of an innovative design that will allow visitors to find the information they need without understanding how the government works. The City wants to make their visit to our web site an easy one. The following is a list of basic ways in which the City's web site will share information over the Internet: • The web site will provide general information in text form to citizens, businesses, visitors, students, and others. Our web site will give citizens an alternative source of information, accessible when phones arc busy or when the offices are closed. The value of this type of Internet use is difficult to estimate. For example, a hit on a particular page might represent an avoided contact with City staff members. However, many people will visit our web site out of curiosity or for an educational purpose, and might not call or write if the Internet were not available. • Citizens and businesses provide information to our web site. Instead of traveling to City offices or mailing in a paper form, citizens who enter the data directly into the City's database, using an Internet form, help us achieve savings in several areas: the cost of data entry, distribution and processing of forms, supplies such as paper and pens, printing, and maintaining office waiting areas. Citizens also benefit from quicker service, reduced travel time, and lower mailing costs. S Businesses provide database, computer files, and business records to our web site. With the evolution of electronic government services, we can expect to see major growth in the electronic delivery of items such as construction and land development plans, business tax records, and other records kept by consultants and contract workers, as well as computer records submitted as part of a service contract or as part of bid and award processes. The City's web site provides search information to citizens. Citizens can query City databases over the Internet and can receive a customized subset of the data. One major advantage to this use of the Internet, is that once the querying system has been set up, the City needs to do nothing else —beyond normal maintenance of the source database —to create up-to-date information that citizens can access over the Internet. • The City's web site provides alert information to citizens, or citizens provide it to the City. Alert information demands a high degree of assurance that it has been brought to the attention to the receiver. Alert information has traditionally been provided through postcards, newsletters, or newspaper articles. Targeted Internet e-mail makes it possible for the City to provide similar alert functions to specific groups of people (e.g. Neighborhood Groups). Project Costs: The cost of the Web Design & Construction services contract with IFWORLD will be $85,680. The description of the costs are outlined in the table below. Although the initial contract is $85,680, City Staff is requesting project contingency approval to increase the annual contract up to $99,000, if necessary. Cost increases may be necessary during the project due to unforeseen changes in the scope of work that will benefit the entire project. In addition, City Staff is requesting a bid waiver be granted to IFWORLD for any future work to the Web Site. It would not be feasible for any other vendor to make modifications to the proprietary software that IFWORLD has developed. Description Hours Amount Core Features Design: Project Preparation 4 S 440.00 Site Map 44 4,840.00 Schematics Document 92 10,120.00 Functional Specifications 162 17,820.00 Graphic Design Comps 42 4,620.00 Design Specifications 1 I 1,210.00 Project Design Document 38 4,180.00 Implementation: Overall Layout and Design 18 1,980.00 Layout and Design of Page Types 60 6,600.00 Description Hours Amount Site Search 21 3,030.00 Content Management Systems 90 12,540.00 Programming 76 11,400.00 Testing & Debugging 42 5,580.00 Training 12 1,320.00 TOTAL 712 $ 85,680.00 Schedule of Desi ng & Implementation Milestones (Tentative): The design and implementation schedule shows the time frame associated with the construction of the City's website. All dates are subject to change with respect to timely feedback from the City of Fayetteville and IFWORLD's workload during the decision process. Design Phase: Design Start .................................................... March 6,2001 Site Map Finalized .............................................. March 21, 2001 Schematics Finalized ............................................. April 15, 2002 Functional Spec Finalized .......................................... May 7, 2002 Graphic Design Comps ........................................... May 22, 2002 Design Completion .............................................. June 13, 2002 Implementation Phase: Implementation Start ............................................. June 14, 2002 Overall Layout Completed ......................................... June 19, 2002 Page Types Completed .............................................. July 3, 2002 Content Management System Completed .............................. July 17, 2002 Site Search Completed ............................................. July 23, 2002 Site Published Live ............................................. August7,2002 Conclusion: City Staff recommends that City Council approve the contract and bid waiver for Web Design and Construction services to IFWORLD. If you have any questions concerning this agenda item, please contact Kevin Springer at 575-8226. Thank you for your consideration in this matter. • STAFF REVIEW FORM X AGENDA REQUEST CONTRACT REVIEW GRANT REVIEW For the Fayetteville City Council meeting of March 5, 2002 FROM: Kevin Springer Budget & Research Administrative Svcs. Name Division - Department ACTION REQUIRED: Contract approval with IFWORLD Inc. for Web -Site Design & Construction services. The amount of the contract is $85,680 with a project contingency of $13,320 (15.5%) being requested for a total contract price of $99,000. A—bt alarm regffeste� fr-enre updates €rem IFWORLD mG. to tk r r , s ,.- COST TO CITY: $85,680.00 Cost of this Request 4470-9470-5315-00 Account Number 02084-1 Project Number BUDGES VIEW: dge Manager Purchasing Officer $ 99,000.00 WebSite Design Category/Project Budget 0.00 Funds Used To Date $ 99,000.00 Remaining Balance Category/Project Name Other Capital Program Name Sales Tax Fund X Budgeted Item Budget Adjustment Attached /' �ov Administrative Services Director LEASE REVIEW: GRANTING AGHN Y: �7t Internal uditor 2 Dat ADA Coordinator Date Grant Coordinator D to Ok Date Date STAFF RECOMMENDATION: Staff recommends approval of the contract and Bid Waiver with IFWORLD. Division Head Date Cross Reference Department Director Date Ad - istratiVe selVl es Di ctor Date ayor Date El ns&nf Ne Pvsines,Lr New Item: Yes No Prev Ord/Res U: Orig Contract Date: Orig Contract Number STAFF REVIEW FORM - Page 2 Description Web Site Design & Construction - IFWORLD Meeting Date March 5, 2002 Comments: Budget Manager Accounting Manager City Attorney Purchasing Officer ADA Coordinator Internal Auditor Grants Coordinator Reference Comments: FAYETTEVItLE THE CITY OF FAYETTEVILLE. ARKANSAS DEPARTMENTAL CORRESPONDEN To: Kevin Springer, Budget & Research From: Heather Woodruff, City Clerk Date: March 7, 2002 Please find attached a copy of Resolution No. 39-02 approving a contract with IF WORLD, INC. for Web Site Design and Construction services. I returning one (1) original contract to you. The second original will be microfilmed and filed with the City Clerk cc: Nancy Smith, Internal Auditor Steve Davis, Budget Manager FAYETTEVItLE THE CITY OF FAYETTEVILLE. ARKANSAS DEPARTMENTAL CORRESPONDENCE To: Kevin Springer, Budget & Research From: Heather Woodruff, City Clerk Date: April 9, 2002 Please find attached a copy of Resolution No. 39-02 approving a contract with IFWORLD, INC. for web -site design and construction. The original will be microfilmed and filed with the City Clerk. cc: Nancy Smith, Internal Audit Note: On March 18, 2002, Kevin was given two (2) originals of the agreement and a copy of the resolution. 010 03 update Document Reference Date RES 3052002 Enter Keywords....... City. of Fayetteville 3/19/2002 lindex Maintenance • 15:35:47 Itei Action Ref. Taken Brief Description 39-02 WEB -SITE DESIGN - - - - - - - - - - - - - - - - - - - - - - - - - - - - : RES. 39-02 File Reference #......: Security class........: Expiration Date.......: Date for cont/Referred: Name Referred to......: CONTRACT IFWORLD. INC. WEB -SITE DESIGN DESIGN CONSTRUCTION 99.000.00 WEBSITE MICROFILM Retention Type: **** Active *** Cmdl-Return Cmd8-Retention Cmd4-Delete Cmd3-End Press 'ENTER' to Continue Cmd5-Abstract Yes No (c) 1986-1992 Munimetrix Systems Corp. I NAME OF FILE: Resolution No. 39-02 CROSS REFERENCE: 03/05/02 Resolution No. 39-02 03/05/02 Exhibit "A" (Web -Site Design & Construction Agreement)(IFWORLD, INC.) 03/11/02 Letter to Shara Fisher, IFWORLD, INC., from Kit Williams, City Attorney Appendix A Appendix B Appendix C 02/12/02 Memo to City Council thru Mayor Coody and Ted Webber, Admin. Services Director 03/05/02 Staff Review Form 03/07/02 Memo to Kevin Springer, Budget & Research, from Heather Woodruff, City Clerk 04/09/02 Memo to Kevin Springer, Budget & Research, from Heather Woodruff, City Clerk X - j n AccessFayettevi I le. o rg Quote to Modify WebSite by IFWORLD Inc. Add Feedback Form Anonymous Optional Feedback From IFWORLD would add a form to AccessFayetteviIle.org's site to allow users a place to anonymously provide feedback. The user would have the option to include their information in the case they would like to be contacted. The form would email the results to a specified email address (to be supplied by the City of Fayetteville). Estimate Graphic Design - 1 hour - $110 Programming - 2 hours - $300 Total Feedback Form Estimate - $410 Add Mayor's Subsection to the Kids' Main Section • Mayor's Subsection IFWORLD would add a subsection to the Kids' Section for the Mayor to add content. The color would be different, but complementary to the subsections already in the system. Estimate Graphic Design - 3 hours - $330 Total Kids' Section Subsection Estimate - $330 CLIENT iIFWORLD b�tni Authorized Bin ng Srgna Auth orized Auorized Binding Signature Title City of Fayetteville, Me or Title Sales Manager By Dan Coody By Shara Fisher Date 02/24/2004 Date 02/10/04 • j •. AccessFayettevi I le. org Quote to Modify Website by IFWORLD Inc. Move Search Moving search to go under Quick Links on all pages. Estimate Graphic Design - 1 hour - $110 Programming - .5 hour - $75 Total Move Search Estimate - $185 • • DY Date d Authorized Binding Signature Title Sales Manager By Shara Fisher Date 05/04/04 • STAFF REVIEW FORM AGENDA REQUEST CONTRACT REVIEW GRANT REVIEW For the Fayetteville City Council meeting of FROM: Lesa Brosch I.T. ZT • aid oN ��Zz/a2 Pis 39-az.i 11O lG G/or/d MICROF� Admin. Services Name Division Department ACTION REQUIRED: Approve $ 7500.00 change order to IF World for additional functions to the website COST TO CITY: $ 7500.00 4470-9470-5315.00 Aunt Nunter Website Design '. 1. 'r'ELI Capital Improvement Pmpam Name 02084 $ 12400.00 Capital Improvement jII - S.. .5 ' •-i' ::... . ... • V / I �.. •I -• ... :. •.. 1 I t� 1 '� • e VL'...y. •JL.- •�3•. �N. • rE Cross Reference New Item: Yes No Prev Ord/Res #: Ong Contract Date: Ong Contract Number Mesa Brosch - Administrative Functional Specification.pdf Page 1 • Access Fayetteville Administrative Functional Specification Prepared by IFVIORLD Inc Jur*4uqS 2002. Table of Contents • 1 Home 2 2 Content Management 4 3 Assets 14 4 Calendar 24 5 Melting Lists 27 6 Groups 30 7 Users 34 Appendices 36 Op 1S8/121W Page1d Q • Luse Brosch - Administrative Functional Specification.pdf ..-Page • • Admnistran veFunctional Specification Access Fayetteville The home page Is an overview of the user's interaction with various parts of the adman isirative site. The page is broken into the following areas: messages from other users; actions awaiting the tout approval; user's actions awaiting an other user% approval; and account Information. Afl sections are always displayed, even if empty — approval sections are subject to permissionts. Maauges This section fists a0 receded messages. The 6dl message is shown wth the sending tact name QNxd wth their emal address for respon ding), and the subject. Messages are sorted oldest fist (the fist cannot be resorted). A Ink below the message list allows access to the message graveyard. For Approval This section lets al actions requiring the approval at the user's level. The fist displays the object, the action, the time of the action, and th e user that performed the action. Each row is ltd to the appropriate prov!w/approve page. Awaiting Approval This section Isis al actions performed by the user that require approval at a higher led. The IS displays the object, the action, as the U me of the action. Each row is timed to the appropriate edit page. Account This section IderdfKs the user by name and Isis the usert grotp/level associations. The number of days since the password was last Banged and the number of days until the next required password large are both shown. • Actions 1.1 Kill Message This script removes the message from the messages lit 1.2 Message Graveyard This page fists al Idled messages displaying sender's name (Irked), subject, and message. 1.3 Change Password This page allows the user to large hs password. The old password must be entered aM the new password must be entered twice. The password must be at kart 6 characters, must contain numerals, lower case leders aM upper a se letters, and must not be the same as the old password. The password must be Barged at least once every 90 days; a reminder emal Is sent to the user 7 days before the password emres. If the password is rot changed wt*' 90 days, the account will be lod¢d aM a new password will reed to be generated by an adminslo tor. Name Ptg &recess Otned Ndes KII Me%age Message IDoes snot cascade Approve Item Approval Action Does not cascade View Item SSu dacd Item Does not cascade Change Password Does not cascade Ui4atS8/12/m2 Page2ar 42 • I Lase Brosch - Administrative Functional Soecification.pdf Page 3 I • Administrab ve Functional Specification Access Fayetteville 1.4 Logout This script destroys the user's atAherttkatlon token aM sends the browser to the login page. • Up"edWWW Page3d 42 • CI Adminstrau ve Functional Specification 2 Content Management Access Fayetteville This page dspkys a tree of all documents owned by groups to which the user belongs. The document tree s cogapsible in the manner of the Macintosh Rader% list mode. Each doamert In the tree has an Icon denoting the document type, a publish fag, the document title, usage flags, and moddkatbn flags. The publish flags a capaal'P'. The 'P' Is greyed out if the document is rot published. If a Ume-0ased publishing has been set, a dolt appears h the lower comer of the flag. Usage flags display if the document has been linked to by other documents (D), otter documents as a related it (R), calendar everts (E), and/or subscribers (S). The usage flags appear in a bracketed list after to document tide (e.g. Are Department [P2, El]). The modifications frogs are for unapproocd charges—aeate, edit, more, and kIQ A colored border strrotrds unapproved pttdsh and modification flags (separate colors indicate the approval lewd needed — editor, supervsor, or adminstrator). Links below the doctanert tree alows acres to the document c rrency and graveyard Document Types: The available types are: Standard, Arrive, Quick Urik, and Emergency Message. An archive document is a document in which the page of the documents expected to change while everything else (title, location, modules, etc.) remains constant. Wien the arcihve action Is titillated, the current page is ardt ed and a new, blank page is created. Both the archive action and the new page content are approved at the same time — there can be no archive action urdl the page is replaced. • Quick Lnk (QL) doamerts are doomeros that do not appear within the normal hierarchal navigation of the public websde — they are only accesstfe trough the "Quick Lies' box. The 'Quick Unls" document at the first lvd of the site tree Is a blank document designed only as a hddtig place for to QL category pages. Al) of to c ildren of the first level "Quick LtnitY document are attomaticaoy QL type documents. Dray one level of document an e>dst below the first level "Quick Ural document. An Emergency Message (EN) doatnert s also separate from the normal hierarchical navigation. Wen an EM doaanent Is published, a banner will appear at to top of every page of the pubic ste containing the doctrnerd%ti tile, desalption, and a lit to to doamert. For this reason, EM doamerts an arty be pubishted with both a start and end date. EM documents must evdst at the Post kveI of to websbe. Actions Name Re Selection Other Notes New Document Doc inert Info Document Move m Up Down To... Select.. Document Does not cascade Modules Document .p, r1 Page4of at m • Administrati ve Functional Specification Access Fayetteville Edit Page Document Preview rg Content Modules FPaqe Document Usage Document Document must have a usage T le Pstfeh Document Archive Document Doc mert must be an ardrve type K9 Document Document Approval Docunert Document must have uupprooed changes History Document 2.1 Document Into The document it corskis of a name, type, archival lifetime (arctive document types oily), desavUon, optbnal start and end dates, grou p ownership (if sac belongs to more than one group), document obsolescence, a Rag for admi thladthie approval, and site placement (new documents only). If this is a new document page, saving the doamerl it will automatically refresh to 2.6 Ed Page. Docuoent names must be input wIt* the cape of the Immediate parent document — a doc mere may not have a chid document that shares its name or the name of any other dhid doc meris. A standard type document can be changed to an archive and, as long ash special criteria are met, to an emergency message. Emergency message documents can always be converted to stasard or ardlve. Ardtise documents can only be converted If no pages have • yet been ardhhed. The site placement is only available through the document Info page when aeattq a document. Users belonging to more than one group must specify group ownership — thx ownerst p is handled automatically for users belonging to only one group. Any user may assign administrative approval, but only an admmshative supervisor may remove t. Data Usage: The name determtes the doc mertt URL The name ant the description appear on the parent page. The type determines what special ftncsonafty, if any, s available m the document (as its children if applicable). The start and eM dates are preset changes of the pttblshed state of the docunert. (The end date does not affect the ardlal state of documents.) The archival He time is between I and 7 years with fair -year Itervas; the setting determines how brig ardlved pages are loept after they have been replaced. The document obsolescence is the length of time after which the content should be updated or reevakrated — before the document reaches obsolescence, a remi rider emad will be sent to the owning group's role accoutt. The doameit obsolescence is anywhere between 1 day and 1 year ant can be expressed in terms of days, weeks or mortis. 2.2 Quick Slide Document This sat moves a document up, down, in or out one place on to doamert tree. 2.3 Quick Jump Document This dialogue box moves a document up or down to a user -specified position on the document tree. The movement is limited to matrran the same parent doamert. Page5d 42 r L I C 6 • Administrab ve Functional Specification Access Fayetteville 2A Move Document This page moves a document to any positon within the editable doament tree. Any parert and position an be dnsen. Actium Name Pq lection Place Under Docutiert Pface Before Doamert Play After Doament 2.5 Module Content This page flcs each sidebar content mod We — alendar, mailing list, and related links — Owing what modLde term are to be displayed with the doament, and Ifdnose module items cascade to the doamnerI cascade from the doamert or are only displayed on that page. The headers for each c mnit modue are tmked to the folmvig placement pages. 2.5.1 Place Calendar(s) This page displays al calendars owned by the docurnert% owning grotp with publish flags. Each calendar has deddoxes for placement on the doament and for cascading down the bee. Calendars cascading from a higher doctarert are marked appropriatey. The docijimerift 'calendar' is a coley n of even s from al placed calendars — the everts are not separated by calendar when displayed on the public site. 2.5.2 Place Mailing List(s) • See 25.1 Place Calmdar(s). 2.5.3 Place Related Link(s) See 2.5.1 Place Calendar(s). This page stows a ftiy expanded site tree with the exception of the current document and is dvldren. 2.6 Edit Page This page displays each page element with is type and attributes. PHP code is printed out — at) other page elements are rendered as they disp lay on the foul page. Cliddng an element type/attnbute Istng selects that element for editing. Actions Name Nit Selection Owed Noll" New Page Bement m Heading Paragraph Link Table List Form Asset Portfolio HTML snricLhIPIsI • Paye6d 4 C • Admirtstrat oe Functional Specification Access Fayetteville PIiP Edit Page Bement Move m Page Bement Does not cascade Up Down To... Selea.. Align m Page Bement Does not cascade Let Center R l t Delete Page Bement 2.6.1 Head Ii This page abws the tteadtg text and style to be entered. Styles: 1-6.) 2.6.2 Paragraph This page allows the paragraph ted and style to be entered. Styles: Normal; Qtntatlmt; and Pill Quote. 2.6.3 Link This page creates a Mk, eater to a manthy entered URL or to a document selected from the site tree. Optional led before and after the brtic can be entered. If silting to a document wahin the sae, a dtedmox Mows showing that doai mert's desaVtIon bebw the name ar flit. Manually entered URLs are not automadcaly verified. • 2.6.4 Table This page displays the table as t wi appear on the ste. IrdMdtal columns can be seceded for moving, aligning, or deletbtg. Individual rows ca n be selected for edrong, moving, or dektitg. Actions eme Ns &Y on Othed Notes Edit Info Edit Columns Add Columns Edit Rows Add Rows See 2.6.4.6 Add Rows Edit Row Row Move Does not cascade Up Down Row Left R'ht Column To... Cokann or Row Align N Left Center Cokmn or Row Does ntot asade v • Pageld Q Brosch - • • Admnisbab ve Funcbanal Specification Access Fayetteville R'ht Delete Column or Row 2.6.4.1 Table Into This page sets the table style, specifies wh ether it wi contain cokann headers and/or row headers, and allows the table data to be uploaded as a comma -separated text file. An example of each table style is provided. Wien orating a new table, settling the cumber of columns w0 also be available. If a file Is riot uploaded, the page will refresh to 2.6.42 Edit Columns and from there to 2.6.4.5 Edit Rows. 2.6.42 Edit Cokmne This page sets the altmn headers (optiorel) and the alignment of each wkmn. 2.6.4.3 Md Columns This dialogue box flows additional columns to be added to the end of the table. After adding the coitanrs, the page is refreshed to the Edit Columns page. 2.6.4.4 Align CoiunN Row This script aligns the data in the selected column or row left, right, or ce ter. 2.6.4.5 Edit Rows This page enters the data for 10 table rows at a time. After saving each set of 10 rows, the page continues on to the next set of rows; afte r all rows are saved, the page refreshes to the man Table page. Links are provided for browsing between sets of rows. Leaving ail wkmrs for a row blank deletes that row, but the row cumbers are mat tairxd until readhig the Edit Table page. 2.6.4.6 Add Rows This script adds additional rows to the end of th e table. This script is only access0le from the Edit Table page and only Mal available rows have been used. After adding the rows, the page is refreshed to the appropriate Edit Rows page. 2.6.4.7 Edit Row This page enters the data for a single table row. 2.8.4.8 Quick Slide CohanV Row This script slides the selected column left or right or the selected row u p or down. 2.6.4.9 Quick Jump CoivataV Row This dialogue box moves the selected column or row to the specified (rhumbered) location in the table. 2.6.4.10 Delete ColunilRow This script deletes the selected column or row from the table. 2.6.5 List This page displeys the list as it wil appear on th editing, moving, or deletig. Actions e site. Individual list dens can be selected for Name Reo, Selection Other! Notes Edit T , Administrat ve Functional Specification Access Fayetteville Edit Items Add Items See 2.6.4.6 Add Rows Edit Item Item Move Does rot cascade Up Down Item In Ott To... Item F be item in nested list Delete Item 2.6.5.1 List Type This page sets the fist type. If there arc no terns in the Ifst, all options am avaIable; otherwise, only similar types (all ordered and unordered are smear, definition and Q&A are similar) are available. ynften creating a new Use, the page wit refresh to 2.6.5.2 Edit Items. Types Flat Ordered — items nmbered 1-n Flat Unordered — items in a bulleted list Nested Ordered — an outline form with the levels Upper Roman (I, IL..), Upper Aihabet (A. 8...), Arabic (1, 2...), IDwer Alphabet (a, b...), Lower Roman (i, ■..) folowed by repeating levels of Bullet (•), Circle ( 0), Square ( c) Nested Unordered — an ottlbne form with repe ating levels of Bullet Crclle, and Square Glossary —terms (bold) followed bydefWtlons (normal) Q&A — questions (bob) followed by answers (ronnnal text on new true) • 2.6.5.2 Edit Iters See 2.6.4.5 Edit Rows. In a rested lit, Nan item with children 6 deleted by beig left blank and the d children are not deleted, they are attached to the previous item at the parent level. If no previous item exists at the parents level, they are at moved to occupy the parentis position, displacing any later items at that level 2.6.5.3 Add Items See 2.6.4.6 Add Rows. 2.6.5A Edit Item This page enters the datum/data for a single item. 2.6.5.5 Qudok Slide I tern This script sides the selected Rem tp or down (at list types), in or out (rested kiss). 2.6.5.6 Quick Juup I tern This dialogue box moves the selected Item to the sped(kd (numbered) baton in the S. In a nested list, the movement is limited to keep the item under Is curer parent item. 2.6.5.7 Move Item See 2.4 Mow Doc meet Only available for rested lss. 2.6.69 Delete Item This script deletes the sScted item from the fist. • Lest Brosch - • Adminstrau veFtatcuonal Specification 2.6.6 Form This page shows the form% recipient (email addr ess) and Sets the fain elements with label, type, vakie We and required flag. The Ist art be sorted. Actions Name IY Selection Other! Notes Recipient new Field rEdit Field Mow tip Up Down To... Field Does rot Cascade Delete Field Access Fayetteville 2.6.6.1 Edit Recipient This page sets th recipient for dx form. The recipient ms be a valid email address — proper ftrmattr� at a domain cortafl g a valid W record. Wen creating a new form, the page wig refresh to "New Form Feld". 2.6.6.2 Edit Field This page defies each field in the form. The la6N, type (short tad, long MA, nlantur, email address, drop-downS, radio list, and dteddtox), and whether the field is required are set If the type 6 a drop -down lst or radio16t, a sect ion appears for atatng the available value lst. The list section consists of the folbwing: a text ar ea for the list osef; a select allows separating the fist Dy a comma';, semicolon';', or pi pe'j'; and a deddaox for sorting the hlems alphabetically. 2.6.6.3 Was Slide Field This script sides the selected flea up or down in tie form. 2.6.64 OuickJrmnp Field This dialogue box moves the selected field to the specified (nunkered) location in de form. 2.6.6.5 Delete Field This script deletes the selected field from the form. 2.5.7 Asset Actions Name Wq.S.Iecdon Sekcd Asset Asset Bads to Page 2.5.7.1 Back to Page This script arts the selection Bag set in 2. „ • 6.7 Asset and wet sin the user to 2.6 Edit Page. Page lOd 42 • • Admnistrati ve Functional Specification 2.9.8 Portfolio See 2.6.7 Asset. The Position Portfolio an only group that owns the Posdan Portk1 . Actions Access Fayetteville be placed In a document owned by the same Name Iq Selection Sled Portfolio PortfSb BadtoP e 2.6.8.1 Back to Page See Errort Reteretce source not found. Enort Reference source not found 2.6.9 HTML Snippet This page enters raw HTML to display on the page. 2.6.10 PHP Snippet This page enters PHP code to excite on tine page. 2.6.11 Quick Slide Page Element See 2.6.63 Quick Slide Field. 2.6.12 btu lick Jurry Page Element See 2.6.6.4 QuidcJunp Fied. 2.6.13 Align Page Element See 2.6.4.4 Align Column. 2.6.14 Delete Page Element This script deletes the selected element from the page. 2.7 Preview Content This page straws tine docmerts cnrlesl Dbck as it would be seen on the public site. 2.8 Review Modules This page shows the position and content of the document's modules as they wound be seen on the pubic site. 2.9 Review Full Page This popup page stews the entire page as it current ly edsts as O It were beng viewed from the public site. 2.10 Document Usage This page displays items that Ink to the current docrierit — calendar everts or other documents as an line irk or as a related link Related fruit age displays whether the related IDik cascades from Ue document. Tte section header for the related tht Is biked to the foiowing edit page. Pagelld 42 Lesa Brosch - Administrative • Admnistrao ve Functional Specification Access Fayetteville 2.10.1 Related Link This page stows a fully expanded site be (doctor ents that the user has permission to modify are bold) with cutest publish Rags. Each doamettt on which the doamert is placed as a related ink is marked as placed and documents to wttkh the related link cascades are marked as cascaded. Clicking an unmarked document marks that document as placed and al chldren documents as cascaded. Clidatg t document again removes the cascade from all children documents. Clicking the doamert a third tine remotes the placement from the document Clddng a cascaded document (or an tn-ca caded document whose parent is marked or cascaded) toggles the cascading for that daament and as children. The submit button at the bottom of the page must be cldxd in order to save changes to the placements and cascades. The difference between this page and 2.53 Place Related Unk(s) will be well doc merted. 2.11 Toggle Publbh It, II tl 2.12 Aroldve Document This script pushes the document into the archive. This is only available for documents w*hn archive sections that do not cortan any current nodifirabors. 2.13 Kill Docuunmt This script marls the document to be kited — th at is, to be completely removed from the she Dee. The document history is preserved. r1 LI 9 2.14 Doouorant Approval This page consists of three parts — the arre rt modiftatbns, the approval form, and the re)ecbon form. The page is ort y available when one or more modification has occurred since the last revision. The user rust preview the enemy modified document before approvi g. The omit mod fiatbre section isidentical to the document history since the latest revision. If the approval process has already been started, the tedual description of the area changes Is displayed here as wel. If a revision of the docu mint is aunty published, a comparison link s provided to 2.15.1 View Doc ment. If the approval process has rot been started, a description of the curt changes must be entered (regardless of pennissors) — this is not a dupbcate of the mods atbrs list, but details of what and why. In addition to the change description, which is for Internal use only, a public comment must be entered for all changes to the docu morn after h Is Post publishhed. This pubic comment will be sera to all users who have subscribed to the doc ment. The change description cannot be modified once the approv al process has begun, but the public comment can be modified at any poht in the approval proms• A orator can arty submtt the lunges for editorial con t ol. An edtor approves the aura lunges, forwarding the document on for su pe rvtsor approval A supervisor approves the changes, updating the publc she or forwarding it on for admbhstrative approval. An adminstraor approves the lunges, updatng the public site. Page12d 42 Lesa Brosch - • LJ • Admmisuav ve Functional Specification The rejection form has a message box to explain why the changes were rejected. Access Fayetteville 2.14.1 Approve Changes This script flags the charges as approved at the current user's level. If another level of approval is needed, a message is sent to the appropriate user (s). If not, the "Update Public Ste" script is run. 2.14.2 Update Public Site This script saves the changes as a new revision and brings the pubic ste — both files and database — up to date with that revIWM 2.14.3 Reject Changes This script sends the rejection message to a I users InvoW in the approval proars and removes all approval flags from the document. 2.16 Document History This page displays a hat of all actions performed on the document (rCSual edit actions are grouped by day — e.g. for a new document, adding each page element is grouped Into the document creation). The hat shows the date of the change, the user and a comment or description of each action (comments for nevi stns, programmatic description for all other actions). The ist cannot be sorted by comment Actions Name Re Selection View Docment Approved Revision Revert Approved Revision 2.15.1 V lew Document This popsy page displays the hill docialent as t was parsed into HTML at the time that the revision was anted (approved). (This may result in broken it)) 2.15.2 Revert Document This wept reverts the document to a preNas revision. 2.16 Doownent Currency This page displays We lady expanded site tree stowing each docttnertt obsolescence, last modified (approved) date, and the days left tittr obsolescence. 2.17 Document Graveyard This page hats al Wed doamerts, where they we re bated n the ste, when they were lolled, who Idled them. The hat cannot be sorted by bafbn. Page 13d 42 Lesa Brosch - C1 • • r L Administati ve Functional Specifi cab on Access Fayetteville The man assets page is the rti g point for browsing assets and portfolos. The page breala the Wee man types — image, PDF, and clipping — In o assets and portfoios and dsplays the number of Items in each. The poSK ors port folio is Isted below the other portfolios. 3.1 I mages This page fists the images that the user an edt Rag, name, group ownershp, usabiliy, and modifl thxmbnaq she (both pboel dimersbns and Ale document, and/or portfaios) appear anmediat pushed down to avoid overlap. and/or use. The image IM displays the publish cation Rags. W m an Usage is selected, Its she), and usage as (nmber of tippings, e?y below the Ism the rest of the 19 s Publish sorting is pualsted, awaking puthed approval, awaiting "Wished approval and umptaPshed. Modification sorting is in the order of new, edged, and Idled — each of these are s&L-ordered by awaiting adminstative approval awaiting supervsor approval, awaking edtor approval and it approval process started. A Ir* below the image ht allows access to the graveyard. Asst Ions Name Rag Selection New Image Edit Image Preview Image Usage Image Toggle Publish Image Kill Image Approval Image History Image 3.1.1 Edit Image This page edts the name, uploaded image Sc, caption (opbonao, group ownership (U the user has asset rights under multiple groups), and usability (the owning grow or sty -vide). On a new image, the submit script forwards on to the edit page. GQs and IPEGs of any size an be wbaded — if the images too large to At n the page (450 x 300) a smaller image wi be seated that fits within those boudarim In addition, a portfolio thumbnail (100 x 150) and an adndn Ist thxmbrai (50x50) will be seated for everyimage. 3.1.2 Review Image This page dsplays the Image n k5 three possble displays on the public site: as partof a porWbo, on a cash page, and ti she (ifappbable). 3.1.3 I make Usage See 2.10 Document Usage. This page Iss the C Ippings, docunerts, and portfolios in which the image is used. Each Isting will be Inked to the appropriate edt page if the user has appropriate pennssiors. Pagel4d 4 Lesa Brosch - Administrative • L • Administrao ve Functional Specifican on 3.1.4 Toggle) mage Publish See 2.11 Toggle Publish. 3.1.5 Kill Image This Script deletes the selected Image. Access Fayetteville 3.1.6 1 mage Approval See 2.14 Document Approval. There art no puD k comments (only appbcable to docunerm). Mein the approval process K Irtmated, an emal notice of the pending change is sent to the role accounts of any groups that have hduded the Image h their content (pages, portfobs, and/or dCphs). 3.1.6.1 Accept Changes See 2.14.1 Approve Changes. 3.1.6.2 Update Public Site See 2.14.2 Update Public Site. 3.1.6.3 Reject Changes See 2.14.3 Reject Changes. 3.1.7 History See 2.15 Document History. Actions Nime Selection View Image Approved Revision Revert Approved Revision 3.1.7.1 V lbw Image Displays 3.12 Preview Image as it appeared for the selected revision. 3.1.72 Revert Image See 2.15.2 Revert Document. 3.1.8 Image Graveyard This page Ras al laced Images showhg name, date Idled, who Wiled them, and former group ownership. 3.2 POFs See 3.1 Images. The PDF list dips Ut p modification rags. Sekahg a PDF deplays ks de possth calendar evert usage). Actions h rag, name, group ownership, usabi0y, and satptlon, file size, and usage stats (PDFs have Name Req.Selection Otter/Niles New PD F Edit PDF Preview PDF Opens the PDF h a new window Usage PDF Page l5d 4 Brosch - Ir Admirvstrati veFunctonal Specification Access Fayetteville ToQQIe Publish PDF Kill PDF Approval PDF History PDF 32.1 Edit POF This page edits the name, uploaded PDF file, description (opal), gip owrierstrp, and usabi@y. On a new PDF, the submit saps forwards on to the edit page. 31.2 PDF Usage See 3.1.3 Image Usage. 3.2.3 Toggle POF Publish See 2.11 Toggle PWlbh. 3Z4 Kill PDF See 3.1.5 K® Image. 32.5 POF Approval See 3.1.6 Image Approval 32.5.1 Accept Changes See 2.14.1 Approve Charges. 32.52 Update Public Site • See 2.14.2 Update Putlc Ste. 31.5.3 Reject Changes See 2.14.3 Reject Charges. 32.6 History See 2.15 Document History. Actions Name Pleq. Selection Other/Notes Vkw PDF Appivved Revision Opers the PDF in a new wt dow Revert Approved Re'lsbn 32.6.1 Revert PDF See 2.15.2 Revert Doc mert. 3.2.7 POF Graveyard See 3.1.8 Image Graveyard. 3.3 Clippings See 3.2 PDFs. Selecting a dipptg displays the usage scats. Actions Name Re 9ekctIon .I:lPliv] • It�7LT. aF�] C • Admstrab ve Functional Specification New C OwnerslIp Clippir Edit CIippir Preview ClIppir Usage Clippirq Toqgle Polish Ch ' Kill CI' i Approval Cllppirc History Clipplr� Access Fayetteville EdUng a ripping is e ectly lie editing a document/page with the added requirement that a clippi g annot be placed as an asset (or as part of a portfolio) into Iself. The editing pages/sets used are &finally dermal to the foiowtg pages (including all sutyages): 2.1 Document Info; 2.6 Edt Page; 2.7 Preview Cont ert; 3.1.3 Image Usage; 2.11 Toggle Publsh; 2.13 Kill Document through 2.152 Revert Document; and 2.17 Document Graveyard. 3.3.1 EditClipplrg I nfo This page sets the rame, group ownettEp, and submit script forwards on to the edit page. 3A I mage Portfolio See 3.1 Images. The portfolio lit displays the and modihatdn flags. Selecting a portfolio dip usage at Letinnt Name a Select on New Portfolio Edit Portfolio Preview Portfolio Usage Portfolio TogQle PLMsh Portfolio Kill Portfolio Approval Portfolio History Portfolio 3.4.1 Edlt I me Portfolio lit page fists the rouges in the portfolio, di Images art listed in their placed order. !wf inn. usability for the ripping. On a new dipping, the publish flag, name, group ownership, taabiHy, lays the cumber of items bide portfoio and Its splaying the name, thumbnail, aptgn and stre. Name Raq.Se4dlon Otitar/Ndes Edit Info Add Imaqe Move 1D Image Does not cascade Up Down To.., Page 17d 42 Lesa Brosch -Administrative Functional Specification.pdf __ _ Page 18 • Adm iistrab ve Functional Specification Access Fayetteville Remo I Image 3.4.1.1 Edlt Info See 33.1 Edit CYpprg Info. 3.4.1.2 Add Image See 2.6.7 Asset. Only allows image assets to be selected. Actions Name etrg Selection Stied Image Asset 3.4.1.3 Chdok Slide I mage See 2.6.63 Quick 511e Held. 3.4.1.4 QudckJunry I mage See 2.6.6.4 Quick lump fr. 3.4.1.5 Remove Image This script removes the image from the portfolio. 3A.2 Preview I mage Portfolio This page displays the portfolio just as it w6 appear in a page. The image thumbrtads are arranged in a table with options below each wage. Each Image/caption par is Ir"d to a pop- up window cmfaini g the Image, Caption and description (Harry). The popwp widow alludes nod/prevbts It to browse Utr ugh Vte portfolio. • 3A.3 Image Portfolio Usage See 3.1.3 Image Usage. 3A.4 Toggle I mage Portfolio Publish See 2.11 Toggle Pubkh. 3A.5 Kill Image Portfolio See 3.1.5 KU) Image. 3A.6 Image Portfolio Approval See 3.1.6 Image Approval 3.4.6.1 Accept Changes See 2.14.1 Approve Changes. 34.6.2 Update Public Site See 2.14.2 Update Public Site. 34.6.3 Reject Changes See 2.14.3 Reject Changes. 3A.7 Image Portfolio History See 2.15 Doaanert history. upde eE wr71@ Page lad 42 • • • Admastrati ve Functional Sp ecifi Can on 3.4.8 Image Portfolio Graveyard See 3.1.8 Image Graveyard. 3.6 POF Portftllo See 3.4 Image Portfolio. Action Name P!g Selection New Portfolio Edit Portfolio Preview Portfolio Usage Portfolio TogIe Publish Portfolio Kil Portfolio Approval Portfolio History Portfolio Access Fayetteville 3.5.1 Edlt PDF Portfolio See 3.4.1 Edit Image Portfolio. PDFS are listed wit h name, Post 40 characters of the description, and see. Name a Seecuon Ot*r Noes Edit Irdo Add PDF Move m Up Down To... PDF Does not cascade Remove PDF 3.5.1.1 Edlt Info See 33.1 Edt Clipping Info. 3.5.1.2 Add POF See 2.6.7 Asset. Only alows PDF assets to be selected. Actions Name Ne Selection Select PDF Asset 3.5.1.3 Wlok Slide PDF See 2.6.63 Quick Slide Field. 3.5.1.4 Gtdck Jung POF See 2.6.6.4 Quick Junp Field. 3.5.1.6 Rennve PDF This script removes the PDF from the portfolio. Page 19d @ Lesa Brosch - Administrative Functional Specification.pdf Page 20 • Administrao ve Functional Specification Access Fayetteville 3.5.2 Preview POP Portfolio This page dsplays the portfob Just as t will appear In a page. The PDFs are listed m order wth name and description. At the end of the ist is a button art Drs to download Acrobat Reader. 3.6.3 PDF Portfolio Usage See 3.1.3 Image Usage. 3.5.4 Toggle PDF Portfolio Publish See 2.11 Toggle Publish. 3.5.6 Kill POF Portfolio See 3.1.5 KB Image. 3.6.6 POP Portfolio Approval See 3.1.6 Image Approval. . 3.5.8.1 Accept Changes See 2.14.1 Approve Changes. 3.6.8.2 Update Public Site See 2.14.2 Update Public Site. 3.5.8.3 Reject Changes See 2.14.3 Reject Charges. •. 3.6.7 PDF Portfolio History See 2.15 Document History. 3.5.8 POP Portfolio Graveyard See 3.1.8 Image Graveyard. 3.6 Clipping Portfolio See 3.4 Image Portfolio. Actions Name Req. Selection New Portfolio Edit Portfolio Preview Portfolio Usage Portfolio Toqle Publish Portfolio KiD Portfolio Approval Portfolio History Portfolio 3.6.1 Edit Clipping Portfolio See 3.4.1 Edt Image Portfolio. Clippings are listed by name. • =1 Lesa Brosch - Administrative Functional Specification.odf Page 21 • Admmistran ve Functional Specification Actions Name Ileg &lectlon Otixr/Natal Edit IMo Add Ci Move 6? Up Down To... Clipping Does not cascade Remove Cli I 3.6.1.1 Edit Into See 33.1 Edft Clipping lit. 3.6.12 Add Clipping See 2.6.7 Asset. Oily allows dipping assets to be selected. Actions Name I4 Selection SSectCppt Asset Access Fayetteville 3.6.1.3 Quick Slide Clipping See 2.6.63 Qtddc Side Field. 3.6.14 Quick Jtanp Clipping See 2.6.6.4 Qtdckktmp Field. 3.6.1.5 Renove Clipping • This script removes the c bppbg from the portfolio. 3.6.2 PreviewCllpping Portfolio This page dsplays the portfolio just as t will appear in a page. Each dipping s displayed In order as a block element. 3.6.3 CUppIng Portfolio Usage See 3.1.3 Image Usage. 3.6.4 ToggleCDppint Portfolio Publish See 2.11 Toggle Pah. 3.6.5 Kill Clipping Portfolio See 3.1.5 Ka Image. 3.6.6 Clipping Portfolio Approval See 3.1.6 Image Approval. 3.6.6.1 Accept Changes See 2.14.1 Approve Changes. 3.6.6.2 Update Public Site See 2.14.2 Update pubic Ste. Pill• CI Page21S 42 I Less Brosch - Administrative Functional Specification.pdf Page 22 • CI • • Admwtistrati vel'unctional Specification 3.8.6.3 Reject Changes See 2.14.3 Reject Changes. 3.8.7 Clipping Portfolio History See 2.15 Document History. 3.6.8 Clipping Portfolio Graveyard See 3.1.8 Image Graveyard. 3.7 Position Portfolio This page lists the uploaded positions displaying name and order. 3.7.1 Position Portfolio Ownership This page sett the group ownership for the postion portfolio. 3.7.2 Upload Positions This page aim the positions to be uploaded in a comma -separated text ffe. earinn ci•Ma Access Fayetteville 1 1 1 .r iill. .._ r. 1 r1 11 1 �� 1 X1911 1r 1 p 1.i application , .I. 1.1 11 ry flThFIlllkler 1 r1 r • I11 . 4.d : -.' _l•_14-1! 1 ILu911 JII - 11 p I �I •r: r.!!-! 1 •nMi, uIcSIIflE4.nnstrla1 IiiTt1lr 1114. ift.III.I lIINd liii n1.'. 1114. IlflhILlIl1W 1. 1�. n 1 1 n 1liii. 1 - 1 3.7.3 Preview Position Portfolio This page displays the portfolio just as t wdl appear in a page. Each postion s dsplayed in order as a bbck element. 3.7.4 Position Portfolio Approval See 2.14 Document Approval. There are no pub is comments (ordy appiable to documents). Pare2d Q Lesa Brosch - Administrative Functional Specification.pdf Page 23 AdminiWao ve Functional Specification Access Fayetteville 3.7.4.1 Accept Changes See 2.14.1 Approve Charges. 3.7.4.2 Update Public Site See 2.14.2 Update Pttec Site. 3.7.4.3 Reject Changes See 2.14.3 Reject Changes. 3.7.5 Position Portfolio History See 2.15 Document History. • tpenmelwW P.xna 42 . Lesa Brosch Administrative Functional Specification.pdf Page 24 • Administrati veFunctional Specdication 4 Calendar Access Fayetteville This page lists the calendars that the user ca n ed. The list displays the publish flag, name, number of events in the future, group ownershp, and modification flags. Actions 4.1 Ownership See 3.7.1 position Portfolio Ownership. 4.2 Site Placement See 2.10.1 Related Palk. 4.3 Upload Events This page alli events to be uploaded in ether a commaseparated text file or a tipped file containing a commasepaated text fie and all attached PDFs. If the user has permission to • modify more than one calendar, a fist of al available calendars will be shown with dtedthoxis to select which caleMars'evenls are benup bailed (by default al calendars are selected). After the upload form is sent, the uigtre IDs for al future everts in the selected calendars are colleted in a let (for later use) and to (leis a zipped (if applicable). The comma -separated text fie is read and each event a compared byes ei�orted (Groupwse) name to the let of selected calendars. If everts are uploaded for an odstlrg calendar other than the selected calendars, they will be ignored. If events are uploaded for a new calendar (again based on the exported name from Grocgwse), the caked ar is created and thte usert first group (aiphabetcally) with calendar creation access is given ownership of the calendar. If the user belongs to more than one group with calendar creation permisions, a message is glen in the co, A a bon reminding tie user to double4teck the group ownership. If the event contains a Inc to a PDF, the uploaded PDF s compared with exttsg PDF assets (by hD5 dxdatam). If the PDF does not abeady et n the database, it is created as a new asset and approved for calendar use orty. After al events are processed afl uploaded files are deleted. As each event is processed, It unique ID saved in a fist — afte r all everts are processed, the processed list is compared with the 1st collected at the beginning of to upload and any events in to original Ise not found in to processed 1st are deleted. Event Fields —. ,t ,u : .. r ., .o Page24d 42 • Administrative • Admwstrab ve Functional Specification Access Fayetteville :11 1 '' 1 1 11 . ..� h . 11: 1:11 sit !1 [ 1 ! [ I. I. e 1 11 1 I. I. 1_11 • •.1 1 .' 1. . • 1 , UIi11i �r. 1L11 tF 69[ [h111 1 _ r. I • • 1. 1 1 1' .-•• iii., 1 iii • .1 1 1 1 1 1 • •11 11 1 Iy.1 1 1 ' • 1 1 1. 1 .1 , 1 11 1 1 •� 1-1 1 1.1 1 1 1 1. 1 • 1 I. ® 11.11 IL• •2 1 f. • L.11 1111 1 �• 1 1 l 1 I. ' 1ucrnru'ni 1 .. • _ 1. _I .w 1 1. ... 1 11 S 4A Prevlew This page displays the calendar as d wil appear in the popup window on the public site. 4.5 Calendar Usage • See 3.13 Image Usage. 4.8 Toggle Calendar Publish See 2.11 Toggle Putkh. 4.7 Kill Calendar See 3.1.5 Ki Image. 4.8 Calendar Approval See 3.7.4 Position Portfoio Approval. 4.8.1 Accept Changes See 2.14.1 Approve Changes. 4.8.2 Update Public Site See 2.14.2 Update Public Ste. 4.8.3 Reject Changes See 2.14.3 Reject Changes. 4.9 Calendar History See 2.15 Document 1l story. Page25d 42 I Lesa Brosch - Administrative Functional Soecification.odt Pape 26 I Admnistrati eeFunctional Specification 4.10 Calendar Graveyard See 3.1.8 Image Graveyard. • • Access Fayetteville Pape26d 42 C1 Administrati ve Functional Specification A Irik below the let allows access to the graveyard. A.tlem Nurse vie Selection New list Edit Info IM Ste Pbamerd List Messages Ust TXQIePLLI&1 list Kill Ust Approval Ust History List 5.1 Edit List I nfo This page alows the lets name, desaption, and group ownership to be edited. 5.2 Site Placement See 2.10.1 Related link Access Fayetteville • 5.3 Messages This page fists all messages sent to the Ist. Trte Ist shows date sent, sut)ect, number of subscribers who received the mesage, and modification gags. A Ink below the message Ist allows access to the graveyard. A."..... Name Nit Selection Other/Notes New Message t9 Ted Doamert Asset Edit Info Message Meat be tarvena Edit a Message Mt at be wisest Preview Message Kl Mustbe u nsertt Approval Message History sage 6.3.1 Edtt Message I nfo This page abws editing the type of message (text, document, or asset), the date the message should be sent (left dank for automatically upon approval), and the group ownershp • epe27d 42 Less Brosch - Administrative Functional Specification.pdf Page 28 LJ • • Administrati veFuncoonal Specification 5.3.2 Ed It Text Message This page has a form for entering the sttject and body of a message. 5.3.3 Select Message Document See 2.10.1 Related Lit Only one pt fished document can be selected. The tide of the document is the subject of Cne message. Actions Name IR Seketion Select D e Document 5.3.4 Select Message Asset See 2.6.7 Asset. Does rat allow asset editing — stbjea of the message. Actions Access Fayetteville selection only. The name of the asset is the Name Fag Selection Select Asset Asset 5.3.5 Preview Message Displays the message as t will/did appear in an email along wth the bask message headers (to, from, and sttject). 5.3.6 KIll Message See 3.1.5 KB Image. 5.3.7 Message Approval See 3.7.4 Poston PorffiIr Approval. 5.3.7.1 Accept Changes See 2.14.1 Approve Changes. If the regtdred appr oval is met, the "Send Message"script is nn. 5.3.72 Send Message See 2.14.2 Update Pttlk Sae. The message s sent to the lst%aIDsaibers. 5.3.7.3 Reject Changes See 2.14.3 Reject Changes. 5.3.8 Message History See 2.15 Docunent History. 1 Name Ne Selection View Ftsaqe Approved Revision Revert Approved Re vision 6.3.8.1 V law Message See 3.1.7.1 View Image. .m..mr:,nml Admirmtiati ve Factional Specification Access Fayetteville 5.3.8.2 Revert Message See 2.15.2 Revert Doc merd. 5.3.9 Message Graveyard See 3.1.8 Image Graveyard. 5.4 toggle List Publish See 2.11 Toggle Pibfsh. 5.5 Kill List See 3.1.5 Ka Image. 6.6 List Approval See 3.7.4 Position Portfolio Approval. 5.8.1 Accept Changes See 2.14.1 Approve Charges. 5.6.2 Update Public Site See 2.14.2 Update Public Ste. 5.8.3 Reject Changes See 2.143 Reject Charges. 5.7 List History • See 2.15 Document History. 5.8 List Graveyard See 3.1.8 Image Graveyard. 11M, T • I:'1 ld4 • Page29d 42 Functional Admnstrat ve Functional Specification Access Fayetteville 6 Groups This page t4s al the groups by name wth the role email address fir the group, whiner al module levels have been filled, and moddlation flags. The admttistrathe supervisors group and the ter/group maintenance group are both fated separately blow the regular grotgs. A trek below the grog 1st allows at.'cess to the graveyard. Action Name Ne Selection New Gro Edit Grot� Users W Ownership m Comers Assets Calendars u sus Grow Ki1 Group Approval Gioup History ClouD 6.1 Edit Group This page allows settbg a group's name and role emal addres. 6.2 Group Users This page bits Use group's users with each user "s module/level permissions for that group. Name Ib lection Omer/Niles Add User Edit Permissions User N/A for Administrative Supenon 6.2.1 Add User See 2.6.7 Asset. 6.2.2 Edit Pensisslons This page edits a si gle group member". Each content module is fisted separately wet a checldiox for each level: Creator; Edtor; and supervisor. The'Usc/Group fr interianoegroup has sdectioru for Uve group art user modules. 6.2.3 Remove User This apt removes the user from Ute group. 6.3 Document Ownership This page displays the fully expanded site tree group is identified at the top of the block divided into bloda of own ent*. The owning UpartMa/U/@ Papejod 4 Adminstrati ve Functional Specification Actions • LI . 6.3.1 Change Document Ownership This page allows setting the owning group of a page arid whether the owners"p st" cascade. 6.4 Asset Ownership See 3 Assets The position portfolio is lied separately with townmtg group. 6A.1 I mage Ownership This page Psis a0 images by name, thunbnail (not sortable), and owning group. Actions Name hieq. Selection Chore Owrer Image Access Fayetteville OA.2 PDF Ownership Thti page Bus all PDFs by name, the first 40 characters of the description (not sortable), and owning group. Actions Name nes Selection CPwrte Owner pop 6.4.3 Clipping Ownership This page Ists at dppiys by name aM owning group. Actions Name nae Selection Char�e Owner Ci 6.4.4 Image Portfolio Ownership See 6.4.3 Copping 0wnershp. Actions 6.4.5 POP Portfolio Ownership See 6.4.3 Clipping OwnershO. Actions Name Ne Selection Charge Owner PDF Portfolio Page3ld 4 I Less Brosch - Administrative Functional Speclfication.odf Pane 32, Admintistrati ve Functional Specification 6A.6 Clipping Portfolio Ownership See 6.43 CBpptrg Ownership. Aetlnns Nam. Ns Selection Chame Owner Upping portfolio 6A.7 Change Asset/ Portfolio Ownership This page allows setting the owreq group of an asset/portf lc. 6.5 Calendar Ownership See 6.43 Capping Ownastp. Actions Name hie Selection Cram Owner Calendar 6.5.1 Change Calendar Ownership See 6.4.7 Change Asset/Portfolb Ownership. 6.6 List Ownership See 6.4.3 Clipp'mg Ownership. Actions tth'iiz,rair;1 6.6.1 Change List Ownenhip See 6.4.7 Change Asset/PortftW Ownership. 6.7 Kill Grob See 3.1.5 Ki Image. A group arolot be Idled if t has owns any active objects. 6.8 Group Approval See 3.7.4 position Porffibo Approval. Access Fayetteville 6.8.1 Accept Changes See 2.14.1 Approve Changes. If the required approv al is met the "Sate Revision" script is run. 6.8.2 Save Revision Th'6 sat saves the changes as a new revision. 6.8.3 Reject Change See 2.14.3 Reject Charges. 6.9 Group History See 2.15 Doacnent History. Updated 8/12a Page32d 4 Functional Admnstrati ve Functional Specification 6.10 Group Graveyard See 3.1.8 Image Graveyard. Access Fayetteville Updated IIIWM Vage33 d Admtrxtrab veFurxtonal Specification 7 Users Access Fayetteville This page lists all users with real name, group memberslYps, a locked flag, and modification flags. The bdaed flag may identify a password seamy lock, a password etpiration lock, a manual admi.Ystrative bdk, or no kick The password security lock reskdls from multple irxorrect login attempts within a set amour t of time (1 hour). The password apkation lock rat from a user not charging his/her password within the IM ne of the previous password (90 days). The adnNnistrative lock prevents a user from loggng in. A Ink below the use ka allows access to the graveyard. Actions Name Reg Selection New User Edit User Toggle lack User Kill IUser Approval User History User 7.1 Edit User This page displays the full user information ar al group/level memberstips. Clddrg a group name selects that group. m±¢ I 7.1.1 Edit Info This page edits the users full name, email address, and isername. The superuser can set a hag determining whether the user is allowed to enter raw HTML The user must have a creator or editor level wthin the concert or asset modules for the setting to be useful. 7.1.2 Edit Permkslons See 61.2 Edit Permissions. On'Add Group", tte group is set by a select Iist of al groups of which the user is not currency a member. If th e "Admtative Supervisor" group is selected, the moduk/level pemiissSs disappear. If the "U ser/Group Malrsterance"group is selected, the content pemisbns are replaced with group and user module permissions. 7.1.3 Remove Croup This script removes the user's permissions for the selected group. 7.2 Toggle Look This scrpt disables any lord of lock or enables an administrative lock. In the case of a security or expiration lock, a new password is generated and emalled to the user. updateEwW@ Page3ad 42 I.L Bros -Administrative Fundional Specification.pdf Page 35; Administati ve Functional Specification Access Fayetteville 7.3 Kill User See 3.1.5 Ka Image. 7A User Approval See 3.7.4 Posdbn Portfolio Approval. 7.4.1 Accept Changes See 69.1 Accept Changes. 1.4.2 Save Revision See 69.2 Save RevMon. 7.4.3 Reject Changes See 2.14.3 Reject Changes. 7.5 User History See 2.15 Downers History. 7.6 User Graveyard See 3.1.8 Image Graveyard. uwars6nLat Page35d Q Lesa Brosch - Administrative Functional Specification.pdf Page 36.1 Admirestati ve Functortal Specifi cat on Appendix A Glossary Access Fayetteville Tam Definition Uupe Action Modification of one or more objects (common actions Permissions / are Create, Move, Edt, Pubfsh, Delete, Kill, Approve) History Action Modification of ore or more objects as allowed by the User Interface adminctrathe she (e.g. New Doormat, Set Related lftts, Kill Message) — each action has an action bcdton and one or more pages and/or scrips Approve Accept flanges to an object and save a new revision — if the object is published, the changes wdl be pushed to the puublic site Asset A piece of con tent managed separately from a particular page. This allow's it to be shared across multiple pages. Clipping An asset type that can contain any page elements inddng other assets and portfolios (as long as its not recursively placed in itself) Delete Permanently remove the object — only items without an individual [history can be deleted Doamert A complete web page including headers, navigation page content, and module cant" Graveyard A list of k1led objet Group A c*cttn of users and owned objects Item An entry in a list — throughout the admit ste. Iles of objects are often in sortable tables Item A sink h entry that has its own nuanber/buba or lkt Editor consists of a term/delinbon or gtestion/arswer pair Ka Remove an object from the worfdng area — Ic led objects can be accessed though the appropriate graveyard ltvel One or more object types and the actions that can be performed on the type(s) — dented levels are Creator, Editor art Suyervisor Module Custom cement apart from the (prmary) page content Object A discrete module ekmert such as an asset, calendar evert, doc mert, mailing ist or portfobo Object Type A class of module element (asset, portfoho, document, mailing It, calendar, calendar evert, user account group —a page element such as a table is not separable from the other page elements and hs not an object type) Updated8/t7/W Page.t6d 44 E C Administrab ve Functional Specification Access Fayetteville Page The body content of a document Content Management Page A web page, issfly Consisting of at least one list or AdmirttsUa9ve form, toed to manage the public site Ste Page Bement A block level place of page content — most elements correspond to stnxttral HTML entities (e.g. leading, paragraph, table, list) arough they may contain additional martap PHP PHP Hypertext Preprocessor— an open source web and database savvy programming language toed to bold the pubic and admirtstrathe sites Portfobo A collection of assets alows for custom grotving of separately managed assets on the page. Many pages can share a portfobo. Pt>nlshed An aortae of a document specifying that it sttotid be avalable through the pitbc see (opposite of Unpublish d) Script A piece of admhinrathe code that performs an action without user interaction (e.g. Move Doctsnent Up, Delete List Item) 5t�ertaer The special user who has al keels of al groups User A person with access to the site User Accourt A users atttnri:ation, contact information, and grotp/level associations Username A tset's accart name (not user's name) — must be matched with a correct password to access the site. The iser ame is never displayed on the ste. User's Name A taer's real name (e.g. Greg Bilugs ey) — this B displayed (admit see ordy) when referring to the user. Lwraiall2/W Page37d 44 Administrab ve Functional Specification Access Fayetteville ADDendix B: User Interface .Less Brosch Administrative Functional Specation pdf Page 38' Administrati ve Functional Specification Appendix B: User Interface Access Fayetteville B.1 Page Layout The administration pages contain the f Iowhg pieces: page title, main navigation, content area, and action list. B.2 Main Navigation The navigation appears as a horizontal Ire of lb is Just under the page title at the top of the page. A htk etdsts thread' major module as wdl as the home page and togging out. hMtn the mouse is positioned over a Ink, one or more addi tonal Irds pop up bebw k. The navigation s the only way to move between sections and big out I. Home A. Charge Password 1I. content A. Doc inert currency III. Assets A. Images 1. Portfolios B. PDFs 1. Portfolios C. Clippings 1. Portfolios D. Positions Portfalb IV. Calendars V. Lists VI. Groups VII. Users VIII. Lngout B.3 List & Sorting Most columnar Isis can be sorted by their cola inns; in some Cases most, bit not al, cokanns an be used to sort the lst. The cement sorted column and sort order are ideri iflvd by the Madntosh Finder's sort pyramd - a triangle co rsstlrg of three spaced bars - ntd to the column header. Clddng the currtrtty sorted cokmnt header toggles the sort between asandcg and descending order. CkI4T any other column trader sorts the VA on that colimn wth the cohmn's debut sort order (most col mns default to ascending values, some date columns default to descerdi g valets). BA Feedback Confirmation or error messages are shown fo! w'ag every an. In addabn, error messages are shown if a program error occurs (e.g. cannot access database) or if data integrity decks fal (e.g. attempting to view a ronttdste t object or approving an object that has ate* been approved} Both types of messages report the spec dk object ("a liy by module and/or type as well as name or ID) and action. Nhen an error is encountered, the svpt attempts to validate as much other data as possible, alowirg mat ipt error messages to be displayed (e.g. the name was empty and the email address was Exorrect) and eliminating mutple attempts to correct the nput. li Lesa Brosch - Administrative Functional Soecification.Ddf Paste 39.1 Admvxtrab ve Fuxtonal Specification Access Fayetteville B.5 Actions Actions buttons (or simply actions) art only ava Mble when the selected object meets atan dteria. An object must be selected in the content area before most actions are enabled. Creation actions do not operate on any (c rren tly) existing object and are always available. other actions (e.g. editing a tablet *) uae an object selection from a previous page (h the case, the 'Edt Page' page). As ddhrent objects on a page are sekdM, the enabled actions wi charge to matdn the current state of the selected object. In most cash, only two sets of action terns are available at a the — the actions for the crud scope are shown Post and the parent scope actions are shown below. Wen editing a paragraph within a page, both the page and document actions are available; when Sting a fist wi"n a page, the fist and page actions are available, but the document Mors disappear. The only e>aeption is when placing an asset — in that case, seka/pmce and cancel placement actions remain at the op of the action area and the two action set rule is enforced until any Sting Is finished. Ui atSe/v/R Page79d 44 Lesa Brosch - Administrative Functional Specification.pdf Page 40 Admirvstrati ve Functional Specification Access Fayetteville Appendix C Site Security C.t Users Each person who has acres to the administrative ste has a unque user account. The user ecwat provIdes basic access to the ste — the user must supply a valid u semame/pass ord. pairto enter the ste. Both the usemame and password are considered se aet The userrume s only used during the login procedure — the user% fill names displayed when refentg to the user (e.g. ban Items hstory). The only people with acces to a user's usemame are the Individual user art those users with admt'Kitattve control over users. The passwords always hidden when entered though the browser art encrypted before being sent to the server. Once on the server, the password is only stored inks encrypted form. C2 Pemrssloss Penmisiors are detenmbxd by a user's level with n a Wedrk module and group. For instance, in order to ante an image for use in the F re Department page, the user must have the folowng: teed — creator; Module — Assets; Group — Fire. Each user can belong to arty nmtber of groups and hold mudtple levels wthn each group. C.2.1 Groups Um are orgart eel into groups in order to simplify content owrtersfdp and access. C22 Modules The major modules allow access to differestt t ypes of Information. The modules are Content Management, Assets, Calendars, Mailing LWh Groups, and Users. C.2.3 Levels The levels are creator, edtor, supervisor, admirtsfrator, and superuser. The creator creates and edits objnxs. The edtor edits content and approves the techikal quality of the object (e.g. spefng, grammar, etc.). The supervisor approves the appropriateness of the object. These three levels — creator, editor, and supervisor— are duplicated across every major ste module allown 9 control riot onty over the level of control a user has, but also the type of content over which that control tdsts. ) The admnstrMor approves potentially sensitive nfomtation art coordinates large content updates; admnstrator access Is defined by membership An the Administrative supergroup. The supenser an perform al actions available wtfln the admt rate sue (except entering NIP code (ixo a doc inert or clipping — that per ision must be manually entered in the database). IntMdtal group/module)level memberships are superfluous for a supenser. ucdatedwWw PageCDd 44 Admmistraa veFunctional Specification Appendix D: Administrative Process The admWstrative process Is the same across a arid ptAfshed. Step Role Iritate charge Creator Submit for approval Creator Edit tern Editor Approve lunge Edtor Approve or reject lunge Supervisor Approve or reject lunge Admrabator Accept ani publish tern Software Access Fayetteville I major modules - teens are created, approved, The example below lists the rl1r tal steps that could be rnofved in placing a new document on the ste. 1. Creator starts a new document a. Name and location dnsen b. Page content entered i. Headings, paragrapts, and a stnrt list U. Upload a photo and placet in the page C. Preview page d. Add mailing lit module Item e. Preview modules and ful page f. Submit for approval L Enter change description ii. Notice sent to editors 2. Edtor reviews doomert a. Preview b. Sit page content - fix a typo and a misspelled name c. Approve i. Notice sent to supervisors 3. Supervisor reviews doc ment a. Preview b. Reject - tone is too flippant I. Notice sent toedtor 4. Editor revews document a. Preview b. Edit convent C. Preview d. Approve L Nooce sect tosupervisors 5. Supervisor reviews UDdalsw/ILOZ Page4ld 44 Admnstrati vefurxvonal Specification a. Preview b. Approve i. Docunertt published Access Fayetteville Upaatea B/17/@ Page42d 44 Lesa- Brosch - Administrative Functional Specification.pdf Page 431 Administrate ve Functional Specification Access Fayetteville Appendix E: User Access E.1 Login The login form (sdsername and pass ord) appears when a user first regtests a page wthn the administrative ste or when the user's login has expired (1 hou- of it ct vty). If three unsumessA login attempts ocaa within one hour on a partlaiar accnint, t wig be biked and will need to be unlocked (with a new password) by an ade .tuc. The navigation 6 not displayed on this page. E2 Browser Fequkrements In order to bgn, the sdser must have cookies enabled and as the sae using SSL (Serve Sodmts Layer). In order to Wbe the user I iterfac e features of she site, the user must be usbng Microsoft Internet Explorer 5.5 or greater with )avaSaipt enabled. Wasted B/= Page V d 44 Administrab ve Fuxt'onal Specification Appendix F: Manual Access Fayetteville The manual is accessed through a framed page consisting of a navigation pane and a content pane. Navigation Para The navigation pane has two modes — table of cortvt and search. The table of concerts mode woria jtat W the ste tree foud h the content admirastration. The search modes a stn -framed page with a search box (one text str i g, no Boolean operators) at the top and a saosable results kg blow. The rest page displays the search string, number of resit and the resubs it Th e results (St displays the relevance ranldrg, tat, and up to three excerpts from the do ctanert indudirg words in the search string. In both modes, clang a document title displays that doamert h the content pane. Content Pans The content pane consists of the docunent hid e, navigation, doctmert body, related Fits, and a dtrp6ate of the navigation. The navigation consists of a previous link contai ntng the title of the previous docunent aligned to the left and a next ink containing the the of the next doaanert aligned to the rght. Next and previous relationships are based on the otahe of the martual she tree. Any related Inc wIR be dsptayed In a let of li donmert titles. Page4ed 44 IFWORLD INC Expanded Features Addendum & Approval for Continuation An Expanded feature is an item that is not part of the proper functioning of a core feature or a specified requirement in the RFP. Rather it is a feature that was born in the Design Phase and has been deemed useful or beneficial enough to be included in the site but is of substantial enough build time to require extra hours added to for it. • Calendar Builder Feature and its associated portion of the publishing system • Bread Crumb Trail Feature • Quick Links and its associated portion of the publishing system • Related Links List Feature and its associated section of the publishing system • Block -Level Portfolio (asset grouping) and its related administration section • Form Builder instead of form templates • Page Type Builder instead of page templates • Emergency Page Feature and its associated section of the publishing system • Clippings Feature • Printer Friendly Pop-up Feature Cost 39 Hours at the agreed upon programrrting rate of $150 per hour to be added to the contract price. 15 Hours at the agreed upon standard HTML rate of $110 per hour to be added to the contract price. Accepted By: Date: Authorizing Signature Approval for continuation The signature below is the acceptance of the, • Administrative Site Map • Administrative Functional Specifications Document • Public Functional Specifications Document and the approval to proceed with the implementation phase of these documents. Authorizing Signature