invitiation to negotiate for the florida …...c. web services to native sdks d. cross platform...

50
(1) INVITIATION TO NEGOTIATE FOR THE FLORIDA HOUSE OF REPRESENTATIVES ____________ TABLET/MOBILE PHONE APPLICATION DEVELOPMENT AND SERVICES ITN 2012-1 Proposals to be opened by the Florida House of Representatives House Administration-Purchasing Office 402 S Monroe St, Suite 1201 The Capitol Tallahassee, Florida 32399-1400 At 4:00 o‟clock p.m. EST, Friday, 31, August, 2012 NAME OF PROPOSER _____________________________________________________________ ADDRESS________________________________________________________________________ CITY ____________________________________________________________________________ SIGNATURE______________________________________________________________________ (Owner or Authorized Corporate Officer) _____________________________________________________________________ (Printed or Typed Name) F.E.I.D._________________________________ DATE____________________________ TELEPHONE NUMBER_(_____)________________________________

Upload: others

Post on 03-Jun-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(1)

INVITIATION TO NEGOTIATE

FOR

THE FLORIDA HOUSE OF REPRESENTATIVES

____________

TABLET/MOBILE PHONE APPLICATION DEVELOPMENT AND

SERVICES

ITN 2012-1

Proposals to be opened by the

Florida House of Representatives

House Administration-Purchasing Office

402 S Monroe St, Suite 1201 The Capitol

Tallahassee, Florida 32399-1400

At 4:00 o‟clock p.m. EST, Friday, 31, August, 2012

NAME OF PROPOSER _____________________________________________________________

ADDRESS________________________________________________________________________

CITY ____________________________________________________________________________

SIGNATURE______________________________________________________________________

(Owner or Authorized Corporate Officer)

_____________________________________________________________________

(Printed or Typed Name)

F.E.I.D._________________________________ DATE____________________________

TELEPHONE NUMBER_(_____)________________________________

Page 2: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(2)

PURPOSE. The Florida House of Representatives of the State of Florida (House) is seeking a

qualified and responsible Vendor(s) to provide proposals and pricing for the development and near-

term support of a Business to Consumer (B2C) application that will run on the Apple iPAD and

iPHONE devices (iOS), and potentially Android Mobile Phones and tablets (7 inch and 10 inch

screens). This ITN is merely a mechanism to review the organizational capabilities of interested

parties and to select potential contractor candidates from the information provided in response to the

invitation.

BACKGROUND. The Florida House of Representatives‟ current use and support for any mobile

phone and/or tablet applications is limited to a mobile phone presentation of the House‟s web site

(MyFloridaHouse - MFHMobile). There is no other infrastructure, development/support skill set,

and/or applications which specifically leverage the capabilities and interfaces available with

iOS/android mobile phones and tablets. The House desires to develop an application that not only

enhances public access and participation in the legislative process but takes advantage of the

innovative capabilities and abilities of the various user interfaces provided by these consumer driven

devices.

.

CONTRACTOR QUALIFICATIONS. Through this ITN, the House intends to identify and

negotiate a contract with a Vendor(s) which has the following basic characteristics:

1. Organization Maturity. Demonstrated expertise, experience, and success in delivering

robust mobile applications across iPHONE, iPAD, and/or Android portable devices. A

stable pool of resources able to deliver well thought out application designs, ease-of-use,

and functionality -- economically and in a timely manner. A company proven to be

innovative.

2. Minimum Capabilities. The organization must be able to design, construct, help to deploy,

and provide production support to the delivered mobile application within a September start

date and 01 February delivery window. Provide examples of previous B2C application

successes, provide in-depth clarification as to its development and project management

methodologies and capabilities, and support/service-life cycles. Ability to develop using:

a. REST technology

b. HTML 5

c. Web Services to Native SDKs

d. Cross Platform Mobile development

e. Native APIs

Ability to support on-site or hybrid staffing models.

Attachment “A” PROPOSED SCREENSHOTS is provided to give the perspective Vendor

an idea of the application being requested. It is not a complete representation but does

provide the look and feel, as well as the type of information being requested by the

application and the various navigation conventions envisioned. This is by no means meant

Page 3: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(3)

to limit any innovation and/or insight into the production of this application you believe

would be beneficial.

3. Performance Assurance and Customer References. The organization must be able to assure

a certain level of performance. It is the House‟s expectation and indeed would be a

condition of any contract resulting from this process that the Vendor(s) would be required

to provide „results‟ rather than „effort‟. Results would be primarily documented through

satisfaction within the end-user community of services, support, and positive resolutions

provided.

Note: Provide at least three references in the development of similar Apps. (see

requirements in Contractor Questionnaire)

COMMUNICATIONS. Upon receipt of this ITN, all Vendor communications concerning the ITN

must be directed to the ITN Coordinator identified herein. Unauthorized contact regarding the ITN

with other House employees or House Members may result in disqualification to propose on this ITN.

Any oral communications will be considered unofficial and non-binding by the House. Vendor should

communicate only in writing by fax, mail or email.

ITN COORDINATOR. Upon receipt of this ITN, all Vendor communications concerning this ITN,

including but not limited to, the “NOTIFICATION OF INTENT” and the “QUESTIONS” must be

directed to the ITN Coordinator of the House Purchasing Office listed below. Vendors should reply

only in writing (hand-delivered, fax or e-mail) to the following:

Jeff Armstrong

Florida House of Representatives

House Administration Purchasing Office, Suite 1201

402 S Monroe Street

Tallahassee, FL 32399-1300

FAX (850) 410-0098

[email protected]

QUESTIONS. Questions for additional information or clarification may be submitted in writing (by

hand-delivery, fax or e-mail) to the ITN Coordinator, mailto:and received no later than August 17,

2012.

All questions should be addressed as follows:

QUESTIONS ITN2012 -1

TABLET/MOBILE PHONE APPLICATION DEVELOPMENT

Page 4: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(4)

On August 22, 2012, all questions with responses will be emailed to all Vendors.

NOTIFICATION OF INTENT. The NOTIFICATION OF INTENT (Attachment “C”) must be

completed and submitted by mail, hand-delivery, faxed or e-mailed to the ITN Coordinatormailto:

specified below, and received by 4:00pm, August 27, 2012. Notifications received after this date/time

will not be considered.

QUESTIONNAIRE. Vendor(s) interested in providing services to the House as part of this ITN, must

complete, in its entirety, the attached Vendor‟s Questionnaire. Vendors may also attach additional

information which serves to illustrate to the House the capabilities of the Vendor. The total package

includes answers to the Questionnaire and any additional information provided.

ECONOMY OF PROPOSAL. Each Proposal shall be prepared simply and economically, providing

straightforward, concise delineation of Vendor‟s capabilities to satisfy the requirements of this ITN.

Fancy bindings, colored displays, and promotional materials are not required. Emphasis on each

Proposal must be on completeness and clarity of content. To expedite the evaluation of Proposals, it is

essential that Vendors follow the format and instructions contained herein.

COST & SCHEDULE INFORMATION SHEET. When submitting their ITN RESPONSE,

Vendors must include an estimated cost and how the cost was derived for work required under this

request. Also the Vendor will provide a high-level proposed schedule. Work would include

development of App, deployment, and ongoing support.

Cost and schedule information is to be included in a separately sealed envelope

(Attachment E). Cost is not to be noted/defined anywhere in the Vendor’s

proposal. The envelope should be addressed to the ITN Coordinator.

SELECTION. The House will review the qualifications of Vendor(s) that respond to this ITN based

on the information provided in the Questionnaire and supporting documentation. Responses will be

evaluated, from what the House deems to be the most qualified to the least. “Most qualified‟ will be

determined using the following considerations –

Contractor Qualifications (see CONTRACTOR QUALIFICATIONS).

Ability to and level at meeting requirements listed in the contractors questionnaire and

as informed by proposed application screenshots found in APPENDIX A.

How the organization addresses the „assurances‟ of performance required and customer

references. (see CONTRACTOR QUALIFICATIONS).

Cost and Schedule information (see COST & SCHEDULE INFORMATION

SHEET).

The House will then set up a meeting with the highest evaluated Vendor and commence negotiations

relative to specific scope of services, timetables for implementation and cost. If negotiations are

unsuccessful, the House will contact the next highest evaluated organization to commence negotiations

with it. The House may seek separate Vendors and award separate contracts for iOS and Android

Page 5: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(5)

application development. The process of selection and negotiation will proceed as follows (except for

the DUE DATE for responses, all dates are approximations):

ACTION RESPONSIBLE

PARTY

DUE DATE

1. ITN Released to Organization(s) House 08/13/2012

2. Submit questions on ITN to House Organization 08/17/2012

3. Respond to all organizations to all

questions received.

House 08/22/2012

4. Submit Notification of Intent Organization 08/27/2012

5. Completion/submittal of

Questionnaire to House

Organization(s) 08/31/2012

6. Complete Review & evaluation of

responses.

House 09/05/2012

7. Complete negotiations

(scope/pricing/scheduling)

House & Highest-

Evaluated Respondent

09/13/2012

8. Contract execution House & Highest-

Evaluated Respondent

TBD

The House reserves the right to reject any and all proposals and to waive any

minor technicalities where it is determined to be in the best interest of the House.

CONTRACT NEGOTIATION. A notice will be sent to all Vendors detailing the House‟s decision

and the top-evaluated organization will be invited to negotiate contract terms. It is essential that the

person assigned by the chosen Vendor has the authority to bind the Vendor to all terms and conditions

of the negotiated contract. The House does not intend to negotiate with a person or persons who then

have to present those terms to another party for approval. The House‟s negotiator will have full

authority to make decisions on terms and conditions of service. The contract terms will include but not

limited to, acceptable timelines, services and costs.

SUBMITTAL OF QUESTIONNAIRES. Completed questionnaires shall be submitted to –

The Florida House of Representatives

House Administration/Purchasing Office

420 South Monroe Street, Suite 1201

Tallahassee, FL 32399

ATTN: Jeff Armstrong

The DEADLINE for submitting Questionnaires is 4:00 PM, EDT, Friday, 31 August, 2012. It is the

Vendor‟s responsibility to ensure timely submission; late submittals will not be considered.

Responses must be limited to ten (10) pages or less.

Page 6: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(6)

The following attachments must be completed in their entirety and submitted with the proposal:

These will not be included in your page count of the proposal.

Attachment “A” PROPOSED SCREENSHOTS

Attachment “B” NOTIFICATION OF INTENT

Attachment “C” DISCLOSURE INFORMATION

Attachment “D” NON-COLLUSION STATEMENT

Attachment “E” COST & SCHEDULE INFORMATION SHEET

Page 7: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(7)

Florida House of Representatives. ______________

Invitation to Negotiate

For

Tablet/Mobile Phone Application Development and Services

______________

CONTRACTOR QUESTIONNAIRE

Interested organizations will complete this Questionnaire, in its entirety, and may attach any additional

information that provides the House with pertinent facts about your company‟s ability to perform

within the parameters established in this ITN.

Indicate “yes” or “no” if the organization can meet the requirement. If “yes” is indicated, provide

detailed explanation of how the organization will meet the requirement. All Mandatory requirements

must be satisfied for qualification. Inability to satisfy Important requirements items, while not

immediately disqualifying, will be heavily considered in the evaluation.

Name of the Organization:

Organization’s Mailing Address:

Name of Contact Person:

Contact Person’s Voice Phone Number:

Contact Person’s FAX Number:

Contact Person’s Email Address:

Page 8: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(8)

CONTRACTOR QUESTIONNAIRE

Page 2 of 2

REQ TYPE REQ # REQUIREMENT RESPONSE

(Y/N)

COMMENTS

Mandatory 1 Develop mobile applications for

public.

Mandatory 2 Develop application functionality

as envisioned in the attached wire

diagrams (see attachment C) for

Apple iPAD and iPHONE devices

(iOS).

Mandatory 3 Application will provide On

Demand content update

Mandatory 4 Development will leverage an

industry standard cross platform

tool/framework.

Mandatory 5 Developed application will

connect to the House Leagis

dbase.

Mandatory 6 Developed application will use

internally (House IT) maintained

security standards and

infrastructure.

Mandatory 7 U/I will have House branding.

Mandatory 8 Developed application will

leverage an internally (House IT)

developed Web service to connect

to the House Leagis dbase.

Important 9 Develop application functionality

as envisioned in the attached

screenshots(see attachment A) for

Android mobile phones and tablets

(7 inch and 10 inch screens).

Important 10 Application will leverage REST.

Important 11 Developed application will use

HTML5.

Important 12 Technical development and

support skill knowledge transfer

will take place to designated

House IT programmer/support

staff.

Important 13 Use of standard code development

tools for U/I to posture for

migration to additional mobile

platforms as needed (i.e. Windows

7 Mobile, RIM, Symbian).

Important 14 Developed applications will have

Page 9: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(9)

“Push notification” availability

Important 15 Developed application will have

support for Social Media

(Facebook, twitter, video

streaming, e-mail).

Informational 16 Standardized Software

Development Methodology.

Informational 17 Preferred Security

Model/Infrastructure.

Informational 18 Preferred test environment and

ability to leverage client test

environment.

Informational 19 Provided testing and deployment

services.

Informational 20 Marketing suggestions to promote

App

Informational 21 Frequency of App update to app

store

Informational 22 Any Content Restriction outside

CONUS

Informational 23 Ability to maintain ongoing App

support and life-cycle

maintenance.

Informational 24 Process for Registering App.

Informational 25 Development environment to be

used including all hardware and

tools necessary to develop the

proposed application.

Informational 26 Ability to support developed

applications at all levels (i.e. Help

desk to development)

Informational 27 Capacity to gather usage metrics.

Informational 28 Listing of mobile iOS and Android

APPS developed and implemented

in the past year.

NOTE: In addition to their responses to these questions, organizations may submit whatever

additional information they feel will demonstrate their qualifications to handle this project.

Page 10: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(10)

ATTACHMENT “A”

PROPOSED SCREENSHOTS

The following screenshots are the property of the Florida House of Representatives and may not be

used in whole in part without the prior approval of the Florida House of Representatives.

Page 11: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(11)

Slide 1

iPAD SCREENSHOTS

Proposed

The following screenshots and narration (some proposed requirements) describe the basic look and feel, workflow, and functionality of the envisioned Florida House of Representatives iPAD application (MyFloridaHouseApp). These screenshots, and proposed requirements, are not all inclusive and meant solely to provide the potential Vendor with information when responding to the ITN Vendor Questionnaire. Proposed Requirement(s) • Selecting the displayed App Icon will navigate to the Main Cover Page (page #2 see

01_Main_Cover). NOTE: User Interface naming conventions utilized naming conventions found at: https://developer.apple.com/library/ios/#documentation/UserExperience/Conceptual/MobileHIG

Page 12: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(12)

Slide 2

01_Main_Cover

2. The application will present a common look and feel throughout the “App”. Leverage the provided screenshots in this attachment for guidance. 3. The application Icon will open to the provided MyFloridaHouseApp page (see page # 2, 01_Main_Cover). 4. A Quick Search bar will be accessible at the top of each screen. Typed search terms, if selected, will navigate the user to the appropriate App page. 5. Six icons will be provided on the “Tab Bar” as follows: Members; Committees; Calendars; Bills; Streams; 411 as displayed on 01_Main_Cover. This tab bar will be visible at all times and on each page accessed. 6. Selection of the “Member” icon on the tab bar will navigate to the Member Navigation page (see page# 3). • Selection of the “Committee” icon on the tab bar will navigate to the Committee Directory page

(see page#10) • Selection of the “Calendars” icon on the tab bar will navigate to the Legislative Calendar page (see

page# 18) • Selection of the “Bills” icon on the tab bar will navigate to the Bill Search page (see page# 23) 10.Selection of the “Streams” icon on the tab bar will navigate to the Streaming Video page (see page# 29) 11.Selection of the “411” icon on the tab bar will navigate to the 411 page (see page# 31)

Page 13: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(13)

Slide 3

02_Memberflow_Main

12. The Quick Search bar, accessible at the top of this screen, will, when the “row reorder” element is selected, provide a “Content View” which displays member names (by default member names alphabetically) and which allows member selection by district number. (see page# 4, “03 Memberflow_AlphaList”). 13. The Quick Search bar, accessible at the top of this screen, will, when the “search icon” is selected, navigate to the appropriate App page. (see page # 5, “03a SearchbarDemo). 14. On the Member Navigation page, member pictures are displayed and can be flicked right to left or left to right. Member name, party affiliation (i.e. R, D, or I), and District number are displayed below each picture in focus. If a member picture is not available an icon with text “No Photo Available” is displayed; however member information continues to be displayed below the icon. 15. A slide bar is available to allow fast forward or rapid reverse selection of member pictures. Member name, party affiliation (i.e. R, D, or I), and District number continues to be displayed during this action.

Page 14: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(14)

Slide 4

03_Memberflow_AlphaList

16. The Quick Search bar, accessible at the top of this screen, will, when the “row reorder” element is selected, provide a “Content View” which displays member names (by default member names alphabetical) and which allows member selection by district number. 17. Once a name or district number is selected the App will navigate to the appropriate member main page.

Page 15: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(15)

Slide 5

03a_SearchbarDemo

18. The Quick Search bar, accessible at the top of this screen, will, when the “search icon” is selected, navigate to the appropriate App page; in this case ADKINS.. (see page # 6 “04 Member MainClick” for an example of the Main Member page).

Page 16: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(16)

Slide 6

04_Member_MainClick

19. The main member page will display a “Member Gallery” which provides member pictures that can be flicked right to left or left to right. 20. Subtext about the focused picture is displayed below each picture and changes as new pictures are selected. 21. The member “Content View” will display information as indicated and ordered in the screen shot (see 04_Member_MainClick). 22. Selection of the e-mail address “detail disclosure” button allows the user to e-mail the selected member. 23. Selection of the Address and telephone “detail disclosure” buttons are not defined and could be removed. One thought was to have the address disclosure button bring up a map to the member district office. 24. Selection of the Committee Membership “detail disclosure” button navigates the user to the member’s committee page (see page #7, 04a MemberCommittee). 25. Selection of the Biographical Information “detail disclosure” button navigates the user to the member’s biographical information page (see page #8, 04a MemberCommittee). 26. Selection of the Bills on House Calendar “detail disclosure” button navigates the user to an undefined page which would provide a list of member bills and the calendar they are assigned to. 27. Selection of the Bills on Committee Agenda “detail disclosure” button navigates the user to an undefined page which would provide a list of member bills and the committee agenda’s they are assigned to. 28. Selection of the Votes “detail disclosure” button navigates the user to an undefined page which would provide a list of member bills and their vote record on each bill. 29. Selection of the Staff “detail disclosure” button navigates the user to the member staff page (see page #9, 06 Member_Staff_View).

Page 17: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(17)

Slide 7

04a_MemberCommittees

30. When the user navigates to the MemberCommittees page they are presented a “Table View” of committees and/or subcommittees which the member sits on. Next to each listing is a “detail disclosure” button. 31. Selection of the “detail disclosure” button beside each committee/subcommittee navigates the user to the Committee Details Members page (see page# 13, 09_CommitteeDetails_Members). 32. The member “Content View” is also presented as indicated in the screenshot (page # 8, see 05_Member_BioView).

Page 18: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(18)

Slide 8

05_Member_BioView

33. When the user navigates to the Member Biography View page biographical information is displayed as shown is the screenshot. 34. The member “Content View” is also presented as indicated in the screen shot (see 05_Member_BioView).

Page 19: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(19)

Slide 9

06_Member_Staff_View

35. When the user navigates to the Member Staff View page staff information is displayed in a table as shown is the screenshot. 36. Selection of the “details disclosure” button next to each e-mail address allows the user to e-mail the selected person. 37. The member “Content View” is also presented as indicated in the screenshot (see 06_Member_Staff_View).

Page 20: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(20)

Slide 10

07_CommitteeNav

38. The main member page will display a “Member Gallery” which provides committee iconic pictures that can be flicked right to left or left to right. 39. Subtext under the committee in focus displays the full committee name. 40. The Quick Search bar, accessible at the top of this screen, will, when the “row reorder” element is selected, provide a “Content View” which displays committee names (by default committee names alphabetical) and which allows selection by committee and subcommittee. (see page # 11, 07a_CommitteeSidebarNav).

Page 21: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(21)

Slide 11

07a_CommitteeSidebarNav

41. Once a committee is selected the App will navigate to the appropriate committee detail page. (see 08_CommitteeDetails).

Page 22: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(22)

Slide 12

09_CommitteeDetails_Members

42. The Committee Details page will display a “Committee Directory” which provides committee icons that can be flicked right to left or left to right. 43. Subtext identifying the focused committee is displayed below the icon and changes as new icons are selected. 44. The individual committee “Content View” will display information as indicated and ordered in the screenshot see (08_CommitteeDetails). 45. Selection of the Address and telephone “detail disclosure” buttons are not defined and could be removed. 46. Selection of the Subcommittee “detail disclosure” buttons navigate to a Subcommittee Details that is not yet defined but envisioned to duplicate information and functionality available on its parent Committee Details page. 47. Selection of the Members “detail disclosure” buttons changes the “Gallery View” to a “Table View” as indicated on page # 13, (see screenshot 09_CommitteeDetails_Members). The individual committee (or subcommittee) “Content View” remains unchanged. 48. Selection of the Staff “detail disclosure buttons” changes the “Gallery View” to a “Table View” as indicated on page # 14, (see screenshot 10_CommitteeDetails_Staff). The individual committee (or subcommittee) “Content View” remains unchanged. 49. Selection of the Meeting Notices “detail disclosure” buttons changes the “Gallery View” to a “Table View” as indicated on page # 15, (see screenshot 11_Subcommittee_Details_Notice). The individual committee (or subcommittee) “Content View” remains unchanged. 50. Selection of the Sponsored Bills “detail disclosure” buttons changes the “Gallery View” to a “Table View” as indicated on page # 16, (see screenshot 12_Committee_SponsoredBills). The individual committee (or subcommittee) “Content View” remains unchanged.

Page 23: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(23)

Slide 13

09_CommitteeDetails_Members

51. When the user navigates to the Committee Details Members page committee/subcommittee membership is displayed in a table as shown is the screenshot (see 09_CommitteeDetials_Members). 52. Selection of the “details disclosure” button next to each e-mail address allows the user to e-mail the selected person. 53. Selection of the “details disclosure” button next to each telephone number is not defined and could be removed. 54. The member “Content View” continues to be presented as indicated in the screenshot (see 09_CommitteeDetails_Members).

Page 24: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(24)

Slide 14

10_CommitteeDetails_Staff

55. When the user navigates to the Committee Details Staff page committee/subcommittee staff details are displayed in a table as shown is the screen shot (see 10_CommitteeDetails_Staff). 56. Selection of the “detail disclosure” buttons beside each staff name allows the user to send email the selected staffer. 57. Selection of the “detail disclosure” button next to the telephone number is undefined and could be removed.

Page 25: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(25)

Slide 15

11_Subcommittee_Details_Notice

58. When the user navigates to a Subcommittee (or Committee) Details Notice page committee/subcommittee meeting notice details are displayed in a table as shown is the screen shot (see 11_SubcommitteeDetails_Notice). 59. Selection of the “detail disclosure” buttons beside each Bill allows the user to view a PDF of the selected Bill. 60. Selection of the “detail disclosure” button next to End Date and Time is undefined and could be removed. 61. A bottom table row will display special instructions pertaining to Bill and Amendment filing per the current adopted House Rules. 62. The member “Content View” continues to be presented as indicated in the screenshot (see 09_CommitteeDetails_Members).

Page 26: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(26)

Slide 16

12_Committee_SponsoredBills

63. When the user navigates to a Committee Sponsor Bills page committee/subcommittee sponsored bill details are displayed in a table as shown is the screenshot (see 12_Committee_SponsoredBills). 64. Selection of the “Information Icon” beside each sponsored bill allows the user to view details of the selected Bill (see page # 17, 15a_BillInfoDemo). 65. Selection of the “Vote Icon” beside each sponsored bill allows the user to view the vote record for that sponsored bill. 66. A bottom table row under each sponsored bill displays the latest bill status for that bill. 67. The member “Content View” continues to be presented as indicated in the screenshot (see 12_Committee_SponsoredBills).

Page 27: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(27)

Slide 17

15a_BillInfoDemo

68. Functional details of the view are undefined but it is currently envisioned it will provide information in a similar manner to the web page from which it is derived and or serve up the web page itself.

Page 28: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(28)

Slide 18

13_Calendarflow_Selection

69. The Legislative Calendar page will display a “Calendar Gallery” which provides calendar iconic pictures that can be flicked right to left or left to right. Subtext under the calendar in focus displays the calendar name. 70. The Quick Search bar, accessible at the top of this screen, will, when the “row reorder” element is selected, provide a “Content View” which displays a table listing of calendar names (by default committee names alphabetical) (see page # 19, 14_Calendarflow_Sidebar). 71. A slide bar is available to allow fast forward or rapid reverse selection of calendar icons. Calendar name continues to be displayed during this action.

Page 29: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(29)

Slide 19

14_Calendarflow_Sidebar

15_Calendar_ChamberCalBillView

72. Selection of the “details disclosure” button next to Chamber Calendar navigates the user to the Calendar Chamber Bill View on page # 20, (see 15_Calendar_ChamberCalBillView). 73. Selection of the “details disclosure” button next to Committee Calendars navigates the user to the Calendar Chamber Bill View on page # 21, (see 15b_Calendar_CommitteeCalendar). 74. Selection of the “details disclosure button” next to Events Calendar navigates the user to the Calendar Chamber Bill View on page # 22, (see 15a_Calendar_CommitteeCalendar).

Page 30: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(30)

Slide 20

15_Calendar_ChamberCalBillView

75. Selection of the Chamber Calendar Bill view provides a “table view” of available Chamber Calendars. Calendars are ordered per the current House Rules. 76. Each Bill listed on its’ assigned calendar will provide a table with information categorized as indicated in the provided screenshot (see 15_Calendar_ChamberCalBillView). 77. If selected, the “Information” icon will provide information on the selected bill as depicted on Page # 17, (see 15a_BillInfoDemo). 78. If selected the “Vote” icon next to “Amendment” will display the vote record for that amendment. 79. If selected the “Vote” icon next to “Final Passage” will display the vote record for the final Bill as passed. 80. If the Bill has not yet passed “Final Passage” will not display.

Page 31: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(31)

Slide 21

15b_CommitteeCalendar

81. Selection of the Committee Calendar Bill view provides a “table view” of scheduled committee meetings. Committee meetings are ordered alphabetically and provide information as indicated in the provided screen shot (see 15_Calendar_ChamberCalBillView). 82. Each committee meeting listed will provide information categorized as indicated in the provided screenshot. 83. Selection of the “detail disclosure” button next to each scheduled committee meeting will provide the use access to the Committee packet. 84. Below the Committee Meeting table view is a “Bills On Agenda” table view. 85. Each Bill listed will provide information categorized as indicated in the provided screen shot (see 15_Calendar_ChamberCalBillView). 86. If selected, the “details disclosure” button next to each Bill will navigate the user to the Bill information as depicted on Page # 17, (see 15a_BillInfoDemo).

Page 32: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(32)

Slide 22

16_EventsCalendar

87. Selection of the Events Calendar Bill view provides a “table view” of scheduled events. Events are ordered alphabetically and provide information as indicated in the provided screen shot (see 16_EventsCalendar). 88. Events are displayed by “Events Today” or Events later this Week. There is no other functionality defined currently.

Page 33: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(33)

Slide 23

17_Billflow_Nav

89. The Bill Search page will display a “Bill Search Gallery” which provides Bill iconic pictures that can be flicked right to left or left to right. Subtext under the icon in focus displays the category of Bills being searched name. 90. The Quick Search bar, accessible at the top of this screen’s “row reorder” element is not yet defined. 91. A slide bar is available to allow fast forward or rapid reverse selection of calendar icons. Search category title continues to be displayed during this action. 92. If the “Filed Bills” icon is selected the user is navigated to the Bills Range Slider page. See page # 24, (see 18_Bills_RangeSlider). 93. If the “Bill By Sponsor” icon is selected the user is navigated to the Bills By Sponsor page. See page # 25, (see 18a_BillsbySponsor_MemeberAlph). 94. If the “Bill By Type” icon is selected the user is navigated to the Bills By Type page. See page # 26, (see 18b_BillsbyType). 95. If the “Bill In Committee” icon is selected the user is navigated to the Bills in Committee Details page. See page # 27, (see 19_Bills_inCommittee_Detail). 96. If the “Bill In Committee” icon is selected the user is navigated to the Bills in Committee Details page. See page # 28, (see 19a_Bills_inChamber).

Page 34: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(34)

Slide 24

18_Bills_RangeSlider

97. A “Content View” is provided which allows the selection of Bill Number, Sponsor, or Bill Type. 98. If the Bill Number “detail disclosure” button is selected a “Bill Range” picker is displayed. 99. Selection of a “Bill Range” will result in a table view below the picker which list the Bills in numeric order displaying the information presented in the screen shot (see 18_Bills_RangerSlider). 100. Selection of the “details disclosure” button next to any bill will navigate the user to the Bill Information Demo page (see page # 17, 15a_BillInfoDemo.

Page 35: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(35)

Slide 25

18a_BillsbySponsor_MemberAlpha

101. A “Content View” is provided which allows the selection of Bill Sponsor Alphabetically (default display) or by Committee. 102. Selection of a name displays a “Table View” as shown in the screen shot (see page # 25, 18a_BillsbySponsor_MemberAlpha). 103. The “Table View” provides the Bills sponsored by the selected member as displayed in the screenshot. 104. The selection of the “Information” icon beside each bill navigates the user to the Bill Information Demo page (see page # 17, 15a_BillInfoDemo. 105. The selection of the “Vote” icon beside each bill displays the vote record for the selected bill. 106. Selection of “Committee” in the “Content View” displays a list of committee and sub-committees (alphabetically). 107. Selection of a committee name displays a “Table View” which provides the Bills sponsored by the selected committee (or subcommittee). 108. The selection of the “Information” icon beside each bill navigates the user to the Bill Information Demo page (see page # 17, 15a_BillInfoDemo. 109. The selection of the “Vote” icon beside each bill displays the vote record for the selected bill.

Page 36: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(36)

Slide 26

18b_BillsbyType

110. A “Content View” is provided which allows the selection of Bill Type as listed on page # 26, (see 18b_BillsbyType). 111. If a selected Bill Type “detail disclosure” button is selected a “Bill Range” picker is displayed. 112. Selection of a “Bill Range” will result in a table view below the picker which list the Bills in numeric order displaying the information presented in the screen shot (see 18b_BillsbyType). 113. Selection of the “details disclosure” button next to any bill will navigate the user to the Bill Information Demo page (see page # 17, 15a_BillInfoDemo.

Page 37: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(37)

Slide 27

19_Bills_inCommittee_Detail

114. A “Content View” is provided which allows the selection of Bills in Committee as listed on page # 27, (see 19_Bills_inCommittee_Detail). 115. Selection of the “details disclosure” button next to “Today” provides a “Table View” of information as displayed in the provided screen shot. It is the default view when accessing the page. 116. The top section displays meetings for “Today” (in alphabetical order). 117. The lower section displays a list of Bills on Agenda for that day and the information as displayed in the screenshot. 118. Selection of the “details disclosure” button next to “Tomorrow” provides a “Table View” of information as displayed in the provided screen shot for tomorrows scheduled committee/subcommittee meetings. 119. The top section displays meetings for “Tomorrow” (in alphabetical order). 120. The lower section displays a list of Bills on Agenda for tomorrow and the information as displayed in the screenshot. 121. Selection of the “details disclosure” button next to “Next Week” provides a “Table View” of information as displayed in the provided screen shot for next weeks’ scheduled committee/subcommittee meetings. 122. The top section displays meetings for “Next Week” (in alphabetical order). 123. The lower section displays a list of Bills on Agenda for next week and the information as displayed in the screenshot. 124. Selection of the “details disclosure” button next to any bill will navigate the user to the Bill Information Demo page (see page # 17, 15a_BillInfoDemo.

Page 38: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(38)

Slide 28

19a_Bills_inChamber

125. A “Content View” is provided which allows the selection of Bills in Chamber as listed on page # 28, (see 19a_Bills_inChamber). 126. Selection of the “details disclosure” button next to “Today” provides a “Table View” of information as displayed in the provided screenshot. It is the default view when accessing the page. 127. Selection of the “details disclosure” button next to “Tomorrow” or “Next Week” will provide a similar “Table View” but for Session scheduled tomorrow or next week. 128. Each Bill listed on its’ assigned calendar will provide a table with information categorized as indicated in the provided screenshot (see 19a_Bills_inChamber). 129. If selected, the “Information” icon will provide information on the selected bill as depicted on Page # 17, (see 15a_BillInfoDemo). 130. If selected the “Vote” icon next to “Amendment” will display the vote record for that amendment. 131. If selected the “Vote” icon next to “Final Passage” will display the vote record for the final Bill as passed. 132. If the Bill has not yet passed “Final Passage” will not display.

Page 39: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(39)

Slide 29

20_Streams_Coverflow

133. The Legislative Streaming Video page will display a “Streaming Video Gallery” which provides video streaming thumbnails that can be flicked right to left or left to right. Subtext under the video in focus displays the video name. 134. The Quick Search bar, accessible at the top of this screen, will, when the “row reorder” element is selected, provide a “Content View” which displays a video streaming schedule and video archive list. The lists are chronological. 135. A slide bar is available to allow fast forward or rapid reverse selection of video thumbnails. The video name continues to be displayed during this action.

Page 40: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(40)

Slide 30

21_Streams_Schedule

136. A “Content View” is provided which displays video streams scheduled for the day. The list of video streams will be displayed in chronological order unless the House is in Session (in Chamber). 137. If the House is in Session the information “House in Session – LIVE” will always be displayed at the top of the video stream schedule list. 138. Selection of the “details disclosure” button next to “House in Session – LIVE” or the associated video stream thumbnail on the “Video Streaming Gallery” will activate the users player to display the selected video stream. 139. Archives for each Session (Chamber meeting) will be available for a given Session or Special Session. Selection of the “details disclosure” button next to any listed archive will activate the users player to display the selected video stream.

Page 41: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(41)

Slide 31

22_411_CoverflowMain

140. The Legislative 411 page will display a “Publication Gallery” which provides pictorial icon representations of the documents available to the App that can be flicked right to left or left to right. Subtext under the pictorial icon in focus displays the publication name. 141. The Quick Search bar, accessible at the top of this screen, will, when the “row reorder” element is selected, provide a “Content View” which displays a list of publication categories and publications available to the App. 142. A slide bar is available to allow fast forward or rapid reverse selection of publications. The publication name continues to be displayed during this action.

Page 42: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(42)

Slide 32

23_411_Coverflow

143. A “Content View” is provided which displays publication categories and publications as provided for in the screen shot (see page #32, 23_411_Coverflow). 144. Selection of the “details disclosure” button beside each publication will replace the “Gallery View” with the selected publication view. 145. Selection of the “Gallery View” icon will replace the “Gallery View” with the selected publication view. 146. A slide bar is available to allow fast forward or rapid reverse selection of video thumbnails. The video name continues to be displayed during this action. NOTE: While content of the publications has been defined and is available, App presentation has not. Several ideas (examples) are found on pages 33 through 35.

Page 43: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(43)

Slide 33

24_411_OfficeDirectory

Example of Leadership Directory Content: 147. When the Leadership Directory is selected a “Content View” exposes the sections of the Directory. 148. If the “detail disclosure” button next to each section is selected then a “Table View” provides predetermined information as displayed in the provided screen shot (see page # 33 24_411_OfficeDirectory). 149. Selection of any “detail disclosure” buttons next to staff names enables the user to send an e-mail to the selected staff member. 150. “Detail disclosure” buttons next to addresses and/or phone numbers are currently undefined and may be removed.

Page 44: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(44)

Slide 34

25_411_ClerkStaffDetail

Example of Administrative Directory Content: 151. When the Administrative Directory is selected a “Content View” exposes the sections of the Directory. 152. If the “detail disclosure” button next to each section is selected then a “Table View” provides predetermined information as displayed in the provided screen shot (see page # 34 25_411_ClerkStaffDetail). 153. Selection of any “detail disclosure” buttons next to staff names enables the user to send an e-mail to the selected staff member. 154. “Detail disclosure” buttons next to addresses and/or phone numbers are currently undefined and may be removed.

Page 45: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(45)

Slide 35

26_411_StaffDirectory_Alpha

Example of Administrative Directory Content: 155. Selection of the Staff Directory provides a “Content View” that enables the selection of staff alphabetically or by committee/Office. Default view is alphabetically. Note: Further functionality is currently undefined.

Page 46: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(46)

Slide 36

END screenshots

Page 47: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(47)

ATTACHMENT “B”

THE FLORIDA HOUSE OF REPRESENTATIVES

NOTIFICATION OF INTENT

TABLET/MOBILE PHONE APPLICATION DEVELOPMENT AND

SERVICES

Jeff Armstrong House of Representatives Purchasing Office 402 S. Monroe St., Suite 1201 Tallahassee, FL 32399 Fax Number: (850) 410-0098 Telephone Number: (850) 487-1377 Dear Mr. Armstrong:

This will provide you with written notification of our Intent to submit a response for the:

Tablet/Mobile Phone Application Development and Services ITN Vendor Name: _______________________________________________________________ Vendor Address: _____________________________________________________________________________ _____________________________________________________________________________ _____________________________________________________________________________ Telephone Number: ___________________________________________________________ Fax Number: _________________________________________________________________ Contact Person: _______________________________________________________________ E-Mail Address: _______________________________________________________________

Page 48: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(48)

ATTACHMENT “C”

THE FLORIDA HOUSE OF REPRESENTATIVES

DISCLOSURE INFORMATION

Upon reasonable inquiry, the Contractor discloses, on the lines below:

1) That the following identified owner, officer, director, employee, agent or lobbyist who is/was a

current or former member, officer or employee of the Florida Legislature or any of its units and was,

is, or will be significantly involved in preparing or approving this contract, representing the interests of

the Contractor regarding this ITN, or doing the work covered under this ITN.

2) That the following identified current or former member or employee of the Florida Legislature

owns, directly or indirectly, an interest of five percent (5%) or more of the total assets or capital stock

in the company.

Name:______________________________ Title:_________________________

Name:______________________________ Title:_________________________

Name:______________________________ Title:_________________________

If none, check here ________

Name of Contractor:___________________________________________

By:________________________________________________________

(Manual)

By:________________________________________________________

(Typed)

Title or Position:_____________________________________________

Telephone: ________________________ Date:__________________

Page 49: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(49)

ATTACHMENT “D”

NON-COLLUSION STATEMENT

I certify that this ITN response is made without prior understanding, agreement, or connection with

any corporation, firm or person submitting a bid for the same materials, supplies, or equipment, and is

in all respects fair and without collusion or fraud. I agree to abide by all conditions of this ITN and

certify that I am authorized to sign this ITN for the represented Vendor and that the Vendor is in

compliance with all requirements of the Invitation to Negotiate including, but not limited to,

certification requirements. In submitting a response to an agency of the State of Florida, the Vendor

offers and agrees that, upon the ITN‟s acceptance, the Vendor is deemed to have sold, assigned, and

transferred to the State of Florida all rights, title, and interest in and to all causes of action it may now

or hereafter acquire under the Antitrust laws of the United States and the State of Florida relating to the

particular commodities or services purchased or acquired by the State of Florida or political

subdivision thereof.

VENDOR NAME_______________________________________________________

SIGNATURE__________________________________________________________

(Owner or Authorized Corporate Officer)

__________________________________________________________

(Printed or typed name)

Page 50: INVITIATION TO NEGOTIATE FOR THE FLORIDA …...c. Web Services to Native SDKs d. Cross Platform Mobile development e. Native APIs Ability to support on-site or hybrid staffing models

(50)

ATTACHMENT “E”

THE FLORIDA HOUSE OF REPRESENTATIVES

TABLET/MOBILE PHONE APPLICATION DEVELOPMENT AND

SERVICES

COST & SCHEDULE INFORMATION SHEET

(Separate Sealed Envelope)