CLOSED: Design a web application for online registration and collection of Sweetened Beverage Tax

Sweetened Beverage Tax Project

Statement of Work

City of Philadelphia

Department of Revenue

 

INTRODUCTION

In June 2016, the City of Philadelphia became the first major city in the nation to pass an ordinance to collect tax on Sweetened Beverages. Starting January 1, 2017, the City of Philadelphia will impose a 1.5 cents per ounce tax on the supply of sweetened beverages to retail dealers (example: regular and diet sodas, teas). The tax is also levied on syrups and concentrates used to make sweetened drinks. The liability for payment of the tax is on the registered distributor (a person who supplies sweetened beverages to a dealer) of Sweetened Beverages. In certain cases, a dealer may obtain a waiver to purchase sweetened beverages from an unregistered distributor, but in these cases, the dealer must register, file, and pay the tax themselves. The tax will be due the 15th of each month for the prior month.

 

OBJECTIVES

Facilitate collection of the Sweetened Beverage Tax (SBT) from businesses that are covered by the SBT ordinance. Provide an easy to use web portal to register the business and pay the SBT.

SCOPE OF WORK

Design a web application that will enable the business owners to register their sweetened beverage business with the City. Access to the web portal should be controlled by proper authentication such as login user id and password. The web application should be developed using Microsoft .NET technologies and the front end of the application should communicate with the backend which is an ADABAS database, using the middleware provided by the City. The application should calculate the tax amount based on some input values and accept payment of the tax online. The taxpayer should be able to pay the tax monthly. In addition to the aforementioned work, the selected vendor should perform detailed requirements analysis, prepare requirements document, prepare data-flow/systems diagram(s), prepare test plan(s), and prepare user-friendly training document(s).

TASKS

  1. Detailed requirements analysis
  2. Design registration webpage
  3. Design login page
  4. Design data input page and display calculated tax amount
  5. Present payment page and accept paymentDesign a page to present the tax due and accept payment
  6. Provide printable/downloadable receipt as PDF on the payment web page and email the same to the email address provided by the taxpayer at the time of registration.
  7. Prepare test plans and conduct unit testing and integration testing of all components

 

 

DELIVERABLES and Time Frame

  1. Requirements document – 5 days from start the project
  2. Test web application – 20 Days from start of the project
  3. Production ready web application – 30 days from start of the project
  4. System documentation including architectural diagram and data flow diagrams- 35 days from start of the project
  5. User guide/training document – 35 days from start of the project

 

INSTRUCTIONS FOR SUBMISSION

 Your proposal should include a short description of your qualifications, experience with similar projects, an overview of your firm or organization, and a brief description of your solution. You may include high level architectural diagrams of the proposed solution and URLs for any online examples you may have. Please email all documents to kurian.chirackel@phila.gov. Your submissions must be received on or before 08/04/2016 08/12/2016. Late submissions will not be considered. Please limit the size of the proposal document to a maximum of 12 pages.

QUESTIONS

Please post any questions as a comment below this solicitation on bigideasphl.com so that additional information provided in any Q&A will be available for all potential submitters to review. Any questions sent via email will be directed back to the comment section below the solicitation on bigideasphl.com.

 

Posted in Web Design
19 comments on “CLOSED: Design a web application for online registration and collection of Sweetened Beverage Tax
  1. When does the City anticipate issuing a Notification of Award to the selected vendor?

    When does the City anticipate issuing a Notice to Proceed to the selected vendor?

    Will there be a lag time be between the Notification of Award and the Notice to Proceed? If so, what is the anticipated lag duration?

    Thank you in advance for your time and consideration of this request.

    • K. Chirackel says:

      When does the City anticipate issuing a Notification of Award to the selected vendor?
      With in five days after vendor selection.
      When does the City anticipate issuing a Notice to Proceed to the selected vendor?
      Within a week after conformation of the contract.

      Will there be a lag time be between the Notification of Award and the Notice to Proceed? If so, what is the anticipated lag duration?
      Yes. Normally, two to three weeks.
      Thank you in advance for your time and consideration of this request.

  2. nianus says:

    Hello Kurian,

    we have a few questions in order to prepare our response:

    Are you currently utilizing this site http://www.phila.gov/Revenue/payments/agreements/Pages/default.aspx for the web application design (E-file/E-pay) system or will you be utilizing another portal for this project?

    Are the users already registered through another system or database or are they all being freshly registered through this project?

    Also is the timeline an estimate or is it a strict guideline?

    • K. Chirackel says:

      1. We may have link to the new web application from ‘http://www.phila.gov/Revenue/payments/’. Other than that, it is a standalone application and in that sense its site is its own portal.
      2. SBT is a new tax and the tax payers will be registering through the new application. Some of them may be in the City’s database for payment of other taxes.
      3. The timeline is an estimate, and is the desired timeline.

  3. lns243 says:

    Q. What forms of payment must the app accept?
    Q. What level of support is required after the app and training have been delivered?
    Q. What platform will the app be hosted on, AWS?

    • K. Chirackel says:

      Q. What forms of payment must the app accept?
      Credit cards and debit cards
      Q. What level of support is required after the app and training have been delivered?
      Ongoing post implementation support is not part of this contract.
      Q. What platform will the app be hosted on, AWS?
      Application will be hosted by the City using IIS. No AWS. (Amazon Web Services)

  4. clearyt1 says:

    Is the chosen vendor providing an environment to facilitate payment direct to the city, or will the vendor collect the actual payment?

  5. Respectfully, your response to the previous question directly contradicts Task 5 outlined in the RFP, which we have relied on to develop our proposal and teaming arrangement.

    “5. Present payment page and accept payment.”

    • K. Chirackel says:

      Please see the correction on task 5
      5. Design a page to present and accept payment.

      • K. Chirackel says:

        Please note that Task 5 was revised from “Present payment page and accept payment.” to “Design a page to present and accept payment.”
        Also, please note that the deadline for submission was changed from 08/04/2016 to 08/12/2016

  6. Respectfully, in typical contract administration, responses to questions provide clarification rather than contradict or completely change the meaning or content of a work task.

    Quite frankly, any proposal that does not include an ePay gateway which ‘accepts payment’ cannot fulfill the requirements of the initial Scope of Work.

    We will be submitting a proposal based on the original Scope of Work that was posted.

    We respectfully request, to ensure a fair and impartial bidding environment, that the City consider proposals that utilize a third-party ePay gateway as well as those which utilize the City’s current ePay gateway.

    • K. Chirackel says:

      City has a third-party ePay processing vendor. Access to that vendor’s payment processing system will be provided to you by the City. There was no change in the scope of work; just clarification. The application should have webpage(s) that presents the amount to be paid and when a button such as ‘Pay Now’ is pushed, the customer will be directed to the ePay vendor’s webpage. After successful payment, the control comes back to the application’s page. More details on this is part of the detailed requirements analysis that is one of the tasks for selected vendor.

  7. Genome Digital says:

    A few questions

    // Exactly what information will need to be collected from distributors, or from dealers. (EIN? Addresses? etc)

    // What is the process interacting with your middleware — is it a RESTful, SOAP, etc based software?

    // Will there need to be multiple permission levels built into the City login side of this application.

    Thank you.

    • K. Chirackel says:

      1. Exactly what information will need to be collected from distributors, or from dealers. (EIN? Addresses? etc)
      This will be clear only after the detailed requirements analysis. It is one of the tasks for the selected vendor. EIN and address will definitely a part of the data collected.
      2. What is the process interacting with your middleware — is it a RESTful, SOAP, etc based software?
      SOAP
      3. Will there need to be multiple permission levels built into the City login side of this application
      No.

Leave a Reply