Www.emarketplace.state.pa.us
REQUEST FOR PROPOSALS FOR
Enterprise Application Development
ISSUING OFFICE
Commonwealth of PA, Department of Environmental Protection
Bureau of Information Technology
RFP NUMBER
6100025289
DATE OF ISSUANCE
06/12/2013
REQUEST FOR PROPOSALS FOR
Enterprise Application Development- 6100025289
TABLE OF CONTENTS
CALENDAR OF EVENTS page iii
Part I—GENERAL INFORMATION page 1
Part II—PROPOSAL REQUIREMENTS page 10
Part III—CRITERIA FOR SELECTION page 15
Part IV—WORK STATEMENT page 20
APPENDIX A, IT STANDARD CONTRACT TERMS AND CONDITIONS
APPENDIX B, DOMESTIC WORKFORCE UTILIZATION CERTIFICATION
APPENDIX C, COST SUBMITTAL
APPENDIX D, PROPOSAL COVER SHEET
APPENDIX E, ARCHITECTURAL DIAGRAMS
APPENDIX F, SCENARIO RESPONSE TEMPLATE
APPENDIX G, APPLICATION INVENTORY
APPENDIX H, PROJECT DASHBOARD SAMPLE
CALENDAR OF EVENTS
The Commonwealth will make every effort to adhere to the following schedule:
|Activity |Responsibility |Date |
|Deadline to submit Questions via email to wmcdade@ |Potential Offerors |07/01/2013 |
| | |12:00pm |
|Pre-proposal Conference—Location. |Issuing Office/Potential |06/26/2013 |
|400 Market Street RCSOB 10TH Flr Conference Room |Offerors |1:30pm |
|Harrisburg PA, 17101 | | |
|Answers to Potential Offeror questions posted to the DGS website |Issuing Office |07/08/2013 |
|(emarketplace.state.pa.us) no later than this date. | |2:00pm |
|Please monitor website (emarketplace.state.pa.us) for all communications regarding |Potential Offerors |Ongoing |
|the RFP. | | |
|Sealed proposal must be received by the Issuing Office at 400 Market Street 15th Flr |Offerors |07/23/2013 |
|RCSOB Harrisburg, PA 17101 | |2:00pm |
PART I
GENERAL INFORMATION
Purpose. This request for proposals (RFP) provides to those interested in submitting proposals for the subject procurement (“Offerors”) sufficient information to enable them to prepare and submit proposals for the Department of Environmental Protection’s (DEP) consideration on behalf of the Commonwealth of Pennsylvania (“Commonwealth”) to satisfy a need for its Enterprise Application Development (EAD) (“Project”).
Issuing Office. The Department of Environmental Protection (“Issuing Office”) has issued this RFP on behalf of the Commonwealth. The sole point of contact in the Commonwealth for this RFP shall be Bill McDade 400 Market St, Harrisburg, PA 17101 wmcdade@, the Issuing Officer for this RFP. Please refer all inquiries to the Issuing Officer.
Scope. This RFP contains instructions governing the requested proposals, including the requirements for the information and material to be included; a description of the service to be provided; requirements which Offerors must meet to be eligible for consideration; general evaluation criteria; and other requirements specific to this RFP.
Problem Statement. DEP’s Bureau of Information Technology (BIT) is seeking technical service support for its Enterprise Application Development (EAD). These services are required to support the various program areas within DEP which include Air, Water, Waste, Mining, Radiation, Oil & Gas, etc. The EAD is to support the core business processes such as, Permitting, Licensing, Certification, Inspection, Compliance, Lab Sampling, Bonding and Forfeitures, Monitoring, Drilling, and other business areas within the Agency. The services required include project scoping, business analysis, requirements gathering, design, coding, unit and system testing, production rollout, and post-production support.
DEP currently supports various technologies including Microsoft ASP and .Net 3.5 and 4.0 frameworks, SQL Server Reporting Services, Java, Oracle Forms/Reports version 11G, SQL, PL/SQL, and geospatial using the ESRI products. DEP supports over 200 applications, many of which are integrated with the above mentioned technologies. Additional detail is provided in Part IV of this RFP. Please reference Appendix E for architectural diagrams.
Type of Contract. It is proposed that if the Issuing Office enters into a Time and Materials contract as a result of this RFP, it will be a Single Award Contract containing the Standard Contract Terms and Conditions as shown in Appendix A. The Issuing Office, in its sole discretion, may undertake negotiations with Offerors whose proposals, in the judgment of the Issuing Office, show them to be qualified, responsible and capable of performing the Project.
Rejection of Proposals. The Issuing Office reserves the right, in its sole and complete discretion, to reject any proposal received as a result of this RFP.
Incurring Costs. The Issuing Office is not liable for any costs the Offeror incurs in preparation and submission of its proposal, in participating in the RFP process or in anticipation of award of the contract.
Pre-proposal Conference. The Issuing Office will hold a Pre-proposal conference as specified in the Calendar of Events. The purpose of this conference is to provide opportunity for clarification of the RFP. Offerors should forward all questions to the Issuing Office in accordance with Part I, Section I-9 to ensure adequate time for analysis before the Issuing Office provides an answer. Offerors may also ask questions at the conference. In view of the limited facilities available for the conference, Offerors should limit their representation to two (2) individuals per Offeror. The Pre-proposal conference is for information only. Any answers furnished during the conference will not be official until they have been verified, in writing, by the Issuing Office. All questions and written answers will be posted on the Department of General Services’ (DGS) website as an addendum to, and shall become part of, this RFP. Attendance at the Pre-proposal Conference is Mandatory. “Failure to attend the Pre-proposal conference shall disqualify an offeror from consideration for the contract to be awarded from this RFP, and its proposal will be returned unopened.”
Questions & Answers. If an Offeror has any questions regarding this RFP, the Offeror must submit the questions by email (with the subject line “RFP 6100025289 Question”) to the Issuing Officer named in Part I, Section I-2 of the RFP. If the Offeror has questions, they must be submitted via email no later than the date indicated on the Calendar of Events. The Offeror shall not attempt to contact the Issuing Officer by any other means. The Issuing Officer shall post the answers to the questions on the DGS website by the date stated on the Calendar of Events. An Offeror who submits a question after the deadline date for receipt of questions indicated on the Calendar of Events assumes the risk that its proposal will not be responsive or competitive because the Commonwealth is not able to respond before the proposal receipt date or in sufficient time for the Offeror to prepare a responsive or competitive proposal. When submitted after the deadline date for receipt of questions indicated on the Calendar of Events, the Issuing Officer may respond to questions of an administrative nature by directing the questioning Offeror to specific provisions in the RFP. To the extent that the Issuing Office decides to respond to a non-administrative question after the deadline date for receipt of questions indicated on the Calendar of Events, the answer must be provided to all Offerors through an addendum.
All questions and responses as posted on the DGS website are considered as an addendum to, and part of, this RFP in accordance with RFP Part I, Section I-10. Each Offeror shall be responsible to monitor the DGS website for new or revised RFP information. The Issuing Office shall not be bound by any verbal information nor shall it be bound by any written information that is not either contained within the RFP or formally issued as an addendum by the Issuing Office. The Issuing Office does not consider questions to be a protest of the specifications or of the solicitation. The required protest process for Commonwealth procurements is described on the DGS website
Addenda to the RFP. If the Issuing Office deems it necessary to revise any part of this RFP before the proposal response date, the Issuing Office will post an addendum to the DGS website at emarketplace.state.pa.us. It is the Offeror’s responsibility to periodically check the website for any new information or addenda to the RFP. Answers to the questions asked during the Questions & Answers period also will be posted to the website as an addendum to the RFP.
Response Date. To be considered for selection, hard copies of proposals must arrive at the Issuing Office on or before the time and date specified in the RFP Calendar of Events. The Issuing Office will not accept proposals via email or facsimile transmission. Offerors who send proposals by mail or other delivery service should allow sufficient delivery time to ensure timely receipt of their proposals. If, due to inclement weather, natural disaster, or any other cause, the Commonwealth office location to which proposals are to be returned is closed on the proposal response date, the deadline for submission will be automatically extended until the next Commonwealth business day on which the office is open, unless the Issuing Office otherwise notifies Offerors. The hour for submission of proposals shall remain the same. The Issuing Office will reject, unopened, any late proposals.
Proposals. To be considered, Offerors should submit a complete response to this RFP to the Issuing Office, using the format provided in Part II, providing six (6) paper copies of the Technical Submittal and one (1) paper copy of the Cost Submittal and two (2) paper copies of the Small Diverse Business (SDB) participation submittal. In addition to the paper copies of the proposal, Offerors shall submit two complete and exact copies of the entire proposal (Technical, Cost and SDB submittals, along with all requested documents) on CD-ROM or Flash drive in Microsoft Office or Microsoft Office-compatible format. The electronic copy must be a mirror image of the paper copy and any spreadsheets must be in Microsoft Excel. The Offerors may not lock or protect any cells or tabs. Offerors should ensure that there is no costing information in the technical submittal. Offerors should not reiterate technical information in the cost submittal. The CD or Flash drive should clearly identify the Offeror and include the name and version number of the virus scanning software that was used to scan the CD or Flash drive before it was submitted. The Offeror shall make no other distribution of its proposal to any other Offeror or Commonwealth official or Commonwealth consultant. Each proposal page should be numbered for ease of reference. An official authorized to bind the Offeror to its provisions must sign the proposal. If the official signs the Proposal Cover Sheet (Appendix D to this RFP) and the Proposal Cover Sheet is attached to the Offeror’s proposal, the requirement will be met. For this RFP, the proposal must remain valid for 120 days or until a contract is fully executed. If the Issuing Office selects the Offeror’s proposal for award, the contents of the selected Offeror’s proposal will become, except to the extent the contents are changed through Best and Final Offers or negotiations, contractual obligations.
Each Offeror submitting a proposal specifically waives any right to withdraw or modify it, except that the Offeror may withdraw its proposal by written notice received at the Issuing Office’s address for proposal delivery prior to the exact hour and date specified for proposal receipt. An Offeror or its authorized representative may withdraw its proposal in person prior to the exact hour and date set for proposal receipt, provided the withdrawing person provides appropriate identification and signs a receipt for the proposal. An Offeror may modify its submitted proposal prior to the exact hour and date set for proposal receipt only by submitting a new sealed proposal or sealed modification which complies with the RFP requirements.
Small Diverse Business Information. The Issuing Office encourages participation by small diverse businesses as prime contractors, and encourages all prime contractors to make a significant commitment to use small diverse businesses as subcontractors and suppliers.
A Small Diverse Business is a DGS-verified minority-owned business, woman-owned business, veteran-owned business or service-disabled veteran-owned business.
A small business is a business in the United States which is independently owned, not dominant in its field of operation, employs no more than 100 full-time or full-time equivalent employees, and earns less than $7 million in gross annual revenues for building design, $20 million in gross annual revenues for sales and services and $25 million in gross annual revenues for those businesses in the information technology sales or service business.
Questions regarding this Program can be directed to:
Department of General Services
Bureau of Small Business Opportunities
Room 611, North Office Building
Harrisburg, PA 17125
Phone: (717) 783-3119
Fax: (717) 787-7052
Email: gs-bsbo@
Website: dgs.state.pa.us
The Department’s directory of BSBO-verified minority, women, veteran and service disabled veteran-owned businesses can be accessed from: Searching for Small Diverse Businesses.
I-14. Economy of Preparation. Offerors should prepare proposals simply and economically, providing a straightforward, concise description of the Offeror’s ability to meet the requirements of the RFP. Offeror’s proposals should not exceed 250 pages, of single spaced 12 point font. Additionally, each resume provided by Offeror is not to exceed 4 pages of single spaced 10 point font.
I-15. Alternate Proposals. The Issuing Office has identified the basic approach to meeting its requirements, allowing Offerors to be creative and propose their best solution to meeting these requirements. The Issuing Office will not accept alternate proposals.
I-16. Discussions for Clarification. Offerors may be required to make an oral or written clarification of their proposals to the Issuing Office to ensure thorough mutual understanding and Offeror responsiveness to the solicitation requirements. The Issuing Office will initiate requests for clarification. Clarifications may occur at any stage of the evaluation and selection process prior to contract execution.
I-17. Prime Contractor Responsibilities. The contract will require the selected Offeror to assume responsibility for all services offered in its proposal whether it produces them itself or by subcontract. The Issuing Office will consider the selected Offeror to be the sole point of contact with regard to contractual matters.
I-18. Proposal Contents
A. Confidential Information. The Commonwealth is not requesting, and does not require, confidential proprietary information or trade secrets to be included as part of Offerors’ submissions in order to evaluate proposals submitted in response to this RFP. Accordingly, except as provided herein, Offerors should not label proposal submissions as confidential or proprietary or trade secret protected. Any Offeror who determines that it must divulge such information as part of its proposal must submit the signed written statement described in subsection c. below and must additionally provide a redacted version of its proposal, which removes only the confidential proprietary information and trade secrets, for required public disclosure purposes.
B. Commonwealth Use. All material submitted with the proposal shall be considered the property of the Commonwealth of Pennsylvania and may be returned only at the Issuing Office’s option. The Commonwealth has the right to use any or all ideas not protected by intellectual property rights that are presented in any proposal regardless of whether the proposal becomes part of a contract. Notwithstanding any Offeror copyright designations contained on proposals, the Commonwealth shall have the right to make copies and distribute proposals internally and to comply with public record or other disclosure requirements under the provisions of any Commonwealth or United States statute or regulation, or rule or order of any court of competent jurisdiction.
C. Public Disclosure. After the award of a contract pursuant to this RFP, all proposal submissions are subject to disclosure in response to a request for public records made under the Pennsylvania Right-to-Know-Law, 65 P.S. § 67.101, et seq. If a proposal submission contains confidential proprietary information or trade secrets, a signed written statement to this effect must be provided with the submission in accordance with 65 P.S. § 67.707(b) for the information to be considered exempt under 65 P.S. § 67.708(b)(11) from public records requests. If financial capability information is submitted in response to Part II of this RFP such financial capability information is exempt from public records disclosure under 65 P.S. § 67.708(b)(26).
I-19. Best and Final Offers
A. While not required, the Issuing Office reserves the right to conduct discussions with Offerors for the purpose of obtaining “best and final offers.” To obtain best and final offers from Offerors, the Issuing Office may do one or more of the following, in any combination and order:
1. Schedule oral presentations;
2. Request revised proposals;
3. Conduct a reverse online auction; and
4. Enter into pre-selection negotiations.
B. The following Offerors will not be invited by the Issuing Office to submit a Best and Final Offer:
1. Those Offerors, which the Issuing Office has determined to be not responsible or whose proposals the Issuing Office has determined to be not responsive.
2. Those Offerors, which the Issuing Office has determined in accordance with Part III, Section III-5, from the submitted and gathered financial and other information, do not possess the financial capability, experience or qualifications to assure good faith performance of the contract.
3. Those Offerors whose score for their technical submittal of the proposal is less than 70% of the total amount of technical points allotted to the technical criterion.
The issuing office may further limit participation in the best and final offers process to those remaining responsible offerors which the Issuing Office has, within its discretion, determined to be within the top competitive range of responsive proposals.
C. The Evaluation Criteria found in Part III, Section III-4, shall also be used to evaluate the Best and Final offers.
D. Price reductions offered through any reverse online auction shall have no effect upon the Offeror’s Technical Submittal. Dollar commitments to Small Diverse Businesses can be reduced only in the same percentage as the percent reduction in the total price offered through any reverse online auction or negotiations.
I-20. News Releases. Offerors shall not issue news releases, Internet postings, advertisements or any other public communications pertaining to this Project without prior written approval of the Issuing Office, and then only in coordination with the Issuing Office.
I-21. Restriction of Contact. From the issue date of this RFP until the Issuing Office selects a proposal for award, the Issuing Officer is the sole point of contact concerning this RFP. Any violation of this condition may be cause for the Issuing Office to reject the offending Offeror’s proposal. If the Issuing Office later discovers that the Offeror has engaged in any violations of this condition, the Issuing Office may reject the offending Offeror’s proposal or rescind its contract award. Offerors must agree not to distribute any part of their proposals beyond the Issuing Office. An Offeror who shares information contained in its proposal with other Commonwealth personnel and/or competing Offeror personnel may be disqualified.
I-22. Issuing Office Participation. Offerors shall provide all services, supplies, and other support necessary to complete the identified work, except as otherwise provided in this Part I, Section I-22. DEP shall provide to the selected Offeror, office space in the Rachel Carson State Office Building, 400 Market Street, Harrisburg, Pennsylvania. The selected Offeror will be required to provide all workstations/laptops needed for specified tasks. Vendor owned equipment will be required to meet all Commonwealth and Agency security, development, network, and workstation standards and will be subject to a security scan. Over the period of the contract the Offeror is required to maintain equipment via upgrades and/or replacements to stay current with Commonwealth standard equipment. DEP will be responsible to provide all development software to perform the required tasks. The Offeror will be responsible to provide necessary licenses for the Windows Operating System (currently Windows 7) and all necessary Office Productivity software. The Offeror is expected to provide technical training to staff on an ongoing basis in order to keep their personnel current with new technologies and trends, especially those being considered and utilized at DEP. When able, DEP may provide training to Offeror personnel, however, this should not be expected.
I-23. Term of Contract. The term of the contract will commence on the Effective Date and will end June 30, 2015. There will be three (3) one-year renewal terms, which may be exercised at the Commonwealth’s sole option. The Issuing Office will fix the Effective Date after the contract has been fully executed by the selected Offeror and by the Commonwealth and all approvals required by Commonwealth contracting procedures have been obtained. The selected Offeror shall not start the performance of any work prior to the Effective Date of the contract and the Commonwealth shall not be liable to pay the selected Offeror for any service or work performed or expenses incurred before the Effective Date of the contract.
I-24. Offeror’s Representations and Authorizations. By submitting its proposal, each Offeror understands, represents, and acknowledges that:
A. All of the Offeror’s information and representations in the proposal are material and important, and the Issuing Office may rely upon the contents of the proposal in awarding the contract(s). The Commonwealth shall treat any misstatement, omission or misrepresentation as fraudulent concealment of the true facts relating to the Proposal submission, punishable pursuant to 18 Pa. C.S. § 4904.
B. The Offeror has arrived at the price(s) and amounts in its proposal independently and without consultation, communication, or agreement with any other Offeror or potential offeror.
C. The Offeror has not disclosed the price(s), the amount of the proposal, nor the approximate price(s) or amount(s) of its proposal to any other firm or person who is an Offeror or potential offeror for this RFP, and the Offeror shall not disclose any of these items on or before the proposal submission deadline specified in the Calendar of Events of this RFP.
D. The Offeror has not attempted, nor will it attempt, to induce any firm or person to refrain from submitting a proposal on this contract, or to submit a proposal higher than this proposal, or to submit any intentionally high or noncompetitive proposal or other form of complementary proposal.
E. The Offeror makes its proposal in good faith and not pursuant to any agreement or discussion with, or inducement from, any firm or person to submit a complementary or other noncompetitive proposal.
F. To the best knowledge of the person signing the proposal for the Offeror, the Offeror, its affiliates, subsidiaries, officers, directors, and employees are not currently under investigation by any governmental agency and have not in the last four years been convicted or found liable for any act prohibited by State or Federal law in any jurisdiction, involving conspiracy or collusion with respect to bidding or proposing on any public contract, except as the Offeror has disclosed in its proposal.
G. To the best of the knowledge of the person signing the proposal for the Offeror and except as the Offeror has otherwise disclosed in its proposal, the Offeror has no outstanding, delinquent obligations to the Commonwealth including, but not limited to, any state tax liability not being contested on appeal or other obligation of the Offeror that is owed to the Commonwealth.
H. The Offeror is not currently under suspension or debarment by the Commonwealth, any other state or the federal government, and if the Offeror cannot so certify, then it shall submit along with its proposal a written explanation of why it cannot make such certification.
I. The Offeror has not made, under separate contract with the Issuing Office, any recommendations to the Issuing Office concerning the need for the services described in its proposal or the specifications for the services described in the proposal.
J. Each Offeror, by submitting its proposal, authorizes Commonwealth agencies to release to the Commonwealth information concerning the Offeror's Pennsylvania taxes, unemployment compensation and workers’ compensation liabilities.
K. Until the selected Offeror receives a fully executed and approved written contract from the Issuing Office, there is no legal and valid contract, in law or in equity, and the Offeror shall not begin to perform.
I-25. Notification of Selection
A. Contract Negotiations. The Issuing Office will notify all Offerors in writing of the Offeror selected for contract negotiations after the Issuing Office has determined, taking into consideration all of the evaluation factors, the proposal that is the most advantageous to the Issuing Office.
B. Award. Offerors whose proposals are not selected will be notified when contract negotiations have been successfully completed and the Issuing Office has received the final negotiated contract signed by the selected Offeror.
I-26. Debriefing Conferences. Upon notification of award, Offerors whose proposals were not selected will be given the opportunity to be debriefed. The Issuing Office will schedule the debriefing at a mutually agreeable time. The debriefing will not compare the Offeror with other Offerors, other than the position of the Offeror’s proposal in relation to all other Offeror proposals. An Offeror’s exercise of the opportunity to be debriefed does not constitute nor toll the time for filing a protest (See Section I-27 of this RFP).
I-27. RFP Protest Procedure. The procedures for RFP protests can be found in the Commonwealth Procurement Code at 62 P.S. §1711.1, “Protests of Solicitations or Awards”.
I-28. Use of Electronic Versions of this RFP. This RFP is being made available by electronic means. If an Offeror electronically accepts the RFP, the Offeror acknowledges and accepts full responsibility to insure that no changes are made to the RFP. In the event of a conflict between a version of the RFP in the Offeror’s possession and the Issuing Office’s version of the RFP, the Issuing Office’s version shall govern.
I-29. Information Technology Bulletins.
This RFP is subject to the Information Technology Bulletins (ITB’s) issued by the Office of Administration, Office for Information Technology (OA-OIT). ITB’s may be found at
All proposals must be submitted on the basis that all ITBs are applicable to this procurement. It is the responsibility of the Offeror to read and be familiar with the ITBs. Notwithstanding the foregoing, if the Offeror believes that any ITB is not applicable to this procurement, it must list all such ITBs in its technical submittal, and explain why it believes the ITB is not applicable. The Issuing Office may, in its sole discretion, accept or reject any request that an ITB not be considered to be applicable to the procurement. The Offeror’s failure to list an ITB will result in its waiving its right to do so later, unless the Issuing Office, in its sole discretion, determines that it would be in the best interest of the Commonwealth to waive the pertinent ITB.
PART II
PROPOSAL REQUIREMENTS
Offerors must submit their proposals in the format, including heading descriptions, outlined below. To be considered, the proposal must respond to all requirements in this part of the RFP. Offerors should provide any other information thought to be relevant, but not applicable to the enumerated categories, as an appendix to the Proposal. All cost data relating to this proposal and all Small Diverse Business cost data should be kept separate from and not included in the Technical Submittal. Each Proposal shall consist of the following three separately sealed submittals:
• Technical Submittal, which shall be a response to RFP Part II, Sections II-1 through
II-5;
• Small Diverse Business participation submittal, in response to RFP Part II, Section II-6; and
• Cost Submittal, in response to RFP Part II, Section II-7.
The Issuing Office reserves the right to request additional information which, in the Issuing Office’s opinion, is necessary to assure that the Offeror’s competence, number of qualified employees, business organization, and financial resources are adequate to perform according to the RFP.
The Issuing Office may make investigations as deemed necessary to determine the ability of the Offeror to perform the Project, and the Offeror shall furnish to the Issuing Office all requested information and data. The Issuing Office reserves the right to reject any proposal if the evidence submitted by, or investigation of, such Offeror fails to satisfy the Issuing Office that such Offeror is properly qualified to carry out the obligations of the RFP and to complete the Project as specified.
II-1. Statement of the Problem. State in succinct terms your understanding of the problem presented or the service required by this RFP.
II-2. Management Summary. Include a narrative description of the proposed effort and a list of the items to be delivered or services to be provided.
II-3. Work Plan. Describe in narrative form your technical plan for accomplishing the work. Use the task descriptions in Part IV of this RFP as your reference point. Modifications of the task descriptions are permitted; however, reasons for changes should be fully explained. Indicate the number of person hours allocated to each task. Include a Program Evaluation and Review Technique (PERT) or similar type display, time related, showing each event. If more than one approach is apparent, comment on why you chose this approach.
II-4. Prior Experience
Include experience in supplying similar programming services projects of similar size and scope to this RFP. Experience shown should be work done by individuals who will be assigned to this project as well as that of your company. Studies or projects referred to must be identified and the name of the customer shown, including the name, address, and telephone number of the responsible official of the customer, company, or agency who may be contacted. Offerors must include at least three (3) Customer references. One (1) reference must not be associated with the Commonwealth. Note: Prior experience with environmental applications and models is considered an essential requirement for all proposals and should be clearly articulated in your response.
II-5. Personnel. Include the number of executive and professional personnel, analysts, auditors, researchers, programmers, consultants, clerical, etc., who will be engaged in the work. Show where these personnel will be physically located during the time they are engaged in the Project. For key personnel (Oracle developers, Business Analysts, eGovernment developers, and Microsoft Developers, include the employee’s name and, through a resume or similar document, the Project personnel’s education and experience in Oracle Forms/Reports (10G and above) development, eGovernment/eBusiness development, and Microsoft (.Net and ) development. Studies or projects referred to should be identified and the name of the customer shown including the name, address and telephone number of the responsible official of the customer, company or agency who may be contacted. Indicate the responsibilities each individual will have in this Project and how long each has been with your company. Identify by name any subcontractors you intend to use and the services they will perform. DEP must approve personnel assigned to work on projects based on the recommendation of the selected Offeror’s Team Manager. All Offeror’s staff will be located on-site, full time (1875 hours per calendar year) at the DEP location (RCSOB) in Harrisburg, PA.
For the purpose of this RFP, personnel are those Offeror’s or Subcontractor personnel that are assigned to roles or responsibilities necessary to the success of this project effort. Upon award of a contract, the Offeror’s personnel must be designated by name and the Offeror shall submit a resume of each person’s experience and qualifications. In addition, the Offeror shall submit individually signed Letters of Commitment for all personnel, stating each person’s intention to work on this project at the start of the contract for a period of 6 months or DEP’s discretion. Personnel replacements shall be governed by the requirements noted below.
Offerors may not make changes to Personnel without receiving written agreement of the PA DEP Contract Manager. Staffing changes will come under the heading of a “substitution” or a “replacement”. A “substitution” is defined as an individual temporarily filling-in for a permanent resource. A “replacement” is defined as an individual permanently replacing an already assigned resource. The replacement may be done for various reasons including but not limited to death, loss of employment, long-term sickness, subcontract default or retirement. If either a substitution or a replacement occurs, the Offeror must provide resumes for alternate resources within five (5) business days of the notification. Any substitute or replacement staff for positions must have qualified background and qualified experience.
Upon commencement of the project, all personnel shall be available for a minimum period of 6 months, or an agreed to timeframe by Offeror and DEP Contract Manager.
DEP has the right to reject or terminate any personnel assigned to this project if it is deemed by DEP that performance is substandard, performance standards are not being met as outlined in Table 1 under IV-6. Service Level Agreements/Performance Metrics, or the Commonwealth of DEP policy or law has been violated.
Regardless of any objections set out in its proposal, the Offeror must submit its proposal, including the cost proposal, on the basis of the terms and conditions set out in Appendix A. The Issuing Office will reject any proposal that is conditioned on the negotiation of the terms and conditions set out in Appendix A or to other provisions of the RFP as specifically identified above.
II-6. Small Diverse Business Participation Submittal
A. To receive credit for being a Small Diverse Business or for subcontracting with a Small Diverse Business (including purchasing supplies and/or services through a purchase agreement), an Offeror must include proof of Small Diverse Business qualification in the Small Diverse Business participation submittal of the proposal, as indicated below:
A small Diverse Business verified by BSBO as a Small Diverse Business must provide a photocopy of their verification letter.
B. In addition to the above verification letter, the Offeror must include in the Small Diverse Business participation submittal of the proposal the following information:
1. All Offerors must include a numerical percentage which represents the total percentage of the work (as a percentage of the total cost in the Cost Submittal) to be performed by the Offeror and not by subcontractors and suppliers.
2. All Offerors must include a numerical percentage which represents the total percentage of the total cost in the Cost Submittal that the Offeror commits to paying to Small Diverse Businesses (SDBs) as subcontractors. To support its total percentage SDB subcontractor commitment, Offeror must also include:
a) The percentage and dollar amount of each subcontract commitment to a Small Diverse Business;
b) The name of each Small Diverse Business. The Offeror will not receive credit for stating that after the contract is awarded it will find a Small Diverse Business.
c) The services or supplies each Small Diverse Business will provide, including the timeframe for providing the services or supplies.
d) The location where each Small Diverse Business will perform services.
e) The timeframe for each Small Diverse Business to provide or deliver the goods or services.
f) A signed subcontract or letter of intent for each Small Diverse Business. The subcontract or letter of intent must identify the specific work, goods or services the Small Diverse Business will perform and how the work, goods or services relates to the project.
g) The name, address and telephone number of the primary contact person for each Small Diverse Business.
3. The total percentages and each SDB subcontractor commitment will become contractual obligations once the contract is fully executed.
4. The name and telephone number of the Offeror’s project (contact) person for the Small Diverse Business information.
B. The Offeror is required to submit two copies of its Small Diverse Business participation submittal. The submittal shall be clearly identified as Small Diverse Business information and sealed in its own envelope, separate from the remainder of the proposal.
C. A Small Diverse Business can be included as a subcontractor with as many prime contractors as it chooses in separate proposals.
D. An Offeror that qualifies as a Small Diverse Business and submits a proposal as a prime contractor is not prohibited from being included as a subcontractor in separate proposals submitted by other Offerors.
II-7. Cost Submittal. The information requested in this Part II, Section II-7 shall constitute the Cost Submittal. The Cost Submittal shall be placed in a separate sealed envelope within the sealed proposal, separated from the technical submittal. The total proposed cost shall be broken down into the following components using Appendix C. Offerors should not include any assumptions in their cost submittals. If the Offeror includes assumptions in its cost submittal, the Issuing Office may reject the proposal. Offerors should direct in writing to the Issuing Office pursuant to Part I, Section I-9, of this RFP any questions about whether a cost or other component is included or applies. All Offerors will then have the benefit of the Issuing Office’s written answer so that all proposals are submitted on the same basis.
A. Direct Labor Costs. Itemize to show the following for each category of personnel with a different hourly rate:
1. Category (e.g., partner, project manager, analyst, senior auditor, research associate).
2. Estimated hours.
3. Rate per hour.
4. Total cost for each category and for all direct labor costs.
B. Labor Overhead. Specify what is included and rate used.
C. Travel and Subsistence. Itemize transportation, lodging and meals per diem costs separately. Travel and subsistence costs must conform with the requirements of the most current version of Commonwealth Management Directive 230.10, Travel and Subsistence Allowances. The Issuing Office may accept higher rates normally paid by an Offeror, if those rates were approved by the Offeror’s officials and published prior to submitting this proposal to the Issuing Office.
D. Consultant Costs. Itemize as in (a) above.
E. Subcontract Costs. Itemize as in (a) above.
F. Cost of Supplies and Materials. Itemize.
G. Other Direct Costs. Itemize.
H. General Overhead Costs. Overhead includes two major categories of cost, operations overhead and general and administrative overhead. Operations overhead includes costs that are not 100% attributable to the service being completed, but are generally associated with the recurring management or support of the service. General and administrative overhead includes salaries, equipment and other costs related to headquarters management external to the service, but in support of the activity being completed. Specify what specific items are included and the rates used.
I. Total Cost.
The Issuing Office will reimburse the selected Offeror for work satisfactorily performed after execution of a written contract and the start of the contract term, in accordance with contract requirements, and only after the Issuing Office has issued a notice to proceed. The RFP quantities herein are estimated only and may increase or decrease depending on the needs of the DEP. Contractor shall be paid at the unit price bid on this RFP.
II-8. Domestic Workforce Utilization Certification. Complete and sign the Domestic Workforce Utilization Certification contained in Appendix B of this RFP. Offerors who seek consideration for this criterion must submit in hardcopy the signed Domestic Workforce Utilization Certification Form in the same sealed envelope with the Technical Submittal.
PART III
CRITERIA FOR SELECTION
III-1. Mandatory Responsiveness Requirements. To be eligible for selection, a proposal must be:
A. Timely received from an Offeror; and
B. Properly signed by the Offeror.
III-2. Technical Nonconforming Proposals. The two (2) Mandatory Responsiveness Requirements set forth in Section III-1 above (A-B) are the only RFP requirements that the Commonwealth will consider to be non-waivable. The Issuing Office reserves the right, in its sole discretion, to (1) waive any other technical or immaterial nonconformities in an Offeror’s proposal, (2) allow the Offeror to cure the nonconformity, or (3) consider the nonconformity in the scoring of the Offeror’s proposal.
III-3. Evaluation. The Issuing Office has selected a committee of qualified personnel to review and evaluate timely submitted proposals. Independent of the committee, Bureau of Small Business Opportunities (BSBO) will evaluate the Small Diverse Business participation submittal and provide the Issuing Office with a rating for this component of each proposal. The Issuing Office will notify in writing of its selection for negotiation the responsible Offeror whose proposal is determined to be the most advantageous to the Commonwealth as determined by the Issuing Office after taking into consideration all of the evaluation factors.
III-4. Evaluation Criteria. The following criteria will be used in evaluating each proposal:
A. Technical: The Issuing Office has established the weight for the Technical criterion for this RFP as 50 % of the total points. Evaluation will be based upon the following in order of importance:
a. Personnel Qualifications. This refers to the competence of professional personnel who would be assigned to the job by the Offeror. Qualifications of professional personnel will be measured by experience and education, with particular reference to experience on studies/services similar to that described in the RFP and related to environmental experience. The final Technical scores are determined by giving the maximum number of technical points available to the proposal with the highest raw technical score.
b. Soundness of Approach. This rating requires an evaluation of the Offeror’s proposed approach to solving your specific problem or providing a specific service. It involves an overall evaluation of the entire proposal in relation to the problems. The approach to addressing the scenarios should be reflected here.
c. Understanding the Problem. This refers to the Offeror’s understanding of the agency needs that generated the RFP, of the agency’s objectives in asking for the services or undertaking the study, and of the nature and scope of the work involved.
d. Offeror Qualifications. This refers to the ability of the Offeror to meet the terms of the RFP, especially the time constraint and the quality, relevancy, and recency of studies and projects completed by the Offeror. This also includes the Offeror’s financial ability to undertake a project of this size.
e. Available Facilities. Does the Offeror have any physical facilities, such as local office space, that may be a significant factor in the performance of the contract? Are the facilities conveniently located and staffed? The remaining proposals are rated by applying the Technical Scoring Formula set forth at the
following webpage: scoring formulas overview/20124
B. Cost: The Issuing Office has established the weight for the Cost criterion for this RFP as 30% of the total points. The cost criterion is rated by giving the proposal with the lowest total cost the maximum number of Cost points available. The remaining proposals are rated by applying the Cost Formula set forth at the following webpage: 124
C. Small Diverse Business Participation:
BSBO has established the weight for the Small Diverse Business (SDB) participation criterion for this RFP as 20 % of the total points. Each SDB participation submittal will be rated for its approach to enhancing the utilization of SDBs in accordance with the below-listed priority ranking and subject to the following requirements:
1. A business submitting a proposal as a prime contractor must perform 60% of the total contract value to receive points for this criterion under any priority ranking.
2. To receive credit for an SDB subcontracting commitment, the SDB subcontractor must perform at least fifty percent (50%) of the work subcontracted to it.
3. A significant subcontracting commitment is a minimum of five percent (5%) of the total contract value.
4. A subcontracting commitment less than five percent (5%) of the total contract value is considered nominal and will receive reduced or no additional SDB points depending on the priority ranking.
Priority Rank 1: Proposals submitted by SDBs as prime offerors will receive 150 points. In addition, SDB prime offerors that have significant subcontracting commitments to additional SDBs may receive up to an additional 50 points (200 points total available).
Subcontracting commitments to additional SDBs are evaluated based on the proposal offering the highest total percentage SDB subcontracting commitment. All other Offerors will be scored in proportion to the highest total percentage SDB subcontracting commitment within this ranking. See formula below.
Priority Rank 2: Proposals submitted by SDBs as prime contractors, with no or nominal subcontracting commitments to additional SDBs, will receive 150 points.
Priority Rank 3: Proposals submitted by non-small diverse businesses as prime contractors, with significant subcontracting commitments to SDBs, will receive up to 100 points. Proposals submitted with nominal subcontracting commitments to SDBs will receive points equal to the percentage level of their total SDB subcontracting commitment.
SDB subcontracting commitments are evaluated based on the proposal offering the highest total percentage SDB subcontracting commitment. All other Offerors will be scored in proportion to the highest total percentage SDB subcontracting commitment within this ranking. See formula below.
Priority Rank 4: Proposals by non-small diverse businesses as prime contractors with no SDB subcontracting commitments shall receive no points under this criterion.
To the extent that there are multiple SDB Participation submittals in Priority Rank 1 and/or Priority Rank 3 that offer significant subcontracting commitments to SDBs, the proposal offering the highest total percentage SDB subcontracting commitment shall receive the highest score (or additional points) available in that Priority Rank category and the other proposal(s) in that category shall be scored in proportion to the highest total percentage SDB subcontracting commitment. Proportional scoring is determined by applying the following formula:
SDB % Being Scored x Points/Additional = Awarded/Additional
Highest % SDB Commitment Points Available* SDB Points
Priority Rank 1 = 50 Additional Points Available
Priority Rank 3 = 100 Total Points Available
Please refer to the following webpage for an illustrative chart which shows SDB scoring based on a hypothetical situation in which the Commonwealth receives proposals for each Priority Rank:
D. Domestic Workforce Utilization: Any points received for the Domestic Workforce Utilization criterion are bonus points in addition to the total points for this RFP. The maximum amount of bonus points available for this criterion is 3% of the total points for this RFP.
To the extent permitted by the laws and treaties of the United States, each proposal will be scored for its commitment to use domestic workforce in the fulfillment of the contract. Maximum consideration will be given to those Offerors who will perform the contracted direct labor exclusively within the geographical boundaries of the United States or within the geographical boundaries of a country that is a party to the World Trade Organization Government Procurement Agreement. Those who propose to perform a portion of the direct labor outside of the United States and not within the geographical boundaries of a party to the World Trade Organization Government Procurement Agreement will receive a correspondingly smaller score for this criterion. See the following webpage for the Domestic Workforce Utilization Formula:
. Offerors who seek consideration for this criterion must submit in hardcopy the signed Domestic Workforce Utilization Certification Form in the same sealed envelope with the Technical Submittal. The certification will be included as a contractual obligation when the contract is executed.
III-5. Offeror Responsibility. To be responsible, an Offeror must submit a responsive proposal and possess the capability to fully perform the contract requirements in all respects and the integrity and reliability to assure good faith performance of the contract.
In order for an Offeror to be considered responsible for this RFP and therefore eligible for selection for best and final offers or selection for contract negotiations:
A. The total score for the technical submittal of the Offeror’s proposal must be greater than or equal to 70% of the available technical points; and
B. The Offeror’s financial information must demonstrate that the Offeror possesses the financial capability to assure good faith performance of the contract. The Issuing Office will review the Offeror’s previous three financial statements, any additional information received from the Offeror, and any other publicly-available financial information concerning the Offeror, and assess each Offeror’s financial capacity based on calculating and analyzing various financial ratios, and comparison with industry standards and trends.
An Offeror which fails to demonstrate sufficient financial capability to assure good faith performance of the contract as specified herein may be considered by the Issuing Office, in its sole discretion, for Best and Final Offers or contract negotiation contingent upon such Offeror providing contract performance security for the first contract year cost proposed by the Offeror in a form acceptable to the Issuing Office. Based on the financial condition of the Offeror, the Issuing Office may require a certified or bank (cashier’s) check, letter of credit, or a performance bond conditioned upon the faithful performance of the contract by the Offeror. The required performance security must be issued or executed by a bank or surety company authorized to do business in the Commonwealth. The cost of the required performance security will be the sole responsibility of the Offeror and cannot increase the Offeror’s cost proposal or the contract cost to the Commonwealth.
Further, the Issuing Office will award a contract only to an Offeror determined to be responsible in accordance with the most current version of Commonwealth Management Directive 215.9, Contractor Responsibility Program.
III-6. Final Ranking and Award.
A. After any best and final offer process conducted, the Issuing Office will combine the evaluation committee’s final technical scores, BSBO’s final small diverse business participation scores, the final cost scores, and (when applicable) the domestic workforce utilization scores, in accordance with the relative weights assigned to these areas as set forth in this Part.
B. The Issuing Office will rank responsible offerors according to the total overall score assigned to each, in descending order.
C. The Issuing Office must select for contract negotiations the offeror with the highest overall score; PROVIDED, HOWEVER, THAT AN AWARD WILL NOT BE MADE TO AN OFFEROR WHOSE PROPOSAL RECEIVED THE LOWEST TECHNICAL SCORE AND HAD THE LOWEST COST SCORE OF THE RESPONSIVE PROPOSALS RECEIVED FROM RESPONSIBLE OFFERORS. IN THE EVENT SUCH A PROPOSAL ACHIEVES THE HIGHEST OVERALL SCORE, IT SHALL BE ELIMINATED FROM CONSIDERATION AND AWARD SHALL BE MADE TO THE OFFEROR WITH THE NEXT HIGHEST OVERALL SCORE.
D. The Issuing Office has the discretion to reject all proposals or cancel the request for proposals, at any time prior to the time a contract is fully executed, when it is in the best interests of the Commonwealth. The reasons for the rejection or cancellation shall be made part of the contract file.
PART IV
WORK STATEMENT
Objectives.
A. General. The DEP Bureau of Information Technology (BIT) is seeking technical service support for its Enterprise Application Development (EAD). The EAD encompasses varied development tools, many DEP business processes and includes multiple servers and configurations, as well as multiple security models. There exists several hundred application systems in DEP’s EAD. These systems vary between legacy standalone, legacy enterprise, new development projects and recently released standalone and integrated applications. The EAD enables DEP to protect and improve the quality of air, water and the environment for the health and safety of the citizens of the Commonwealth. The EAD was developed and is maintained to support the core business processes of DEP, several that are utilized by PA citizens and business partners. Some core areas include, but are not limited to:
1) Permitting, licensing and certification;
2) Inspection and compliance activities;
3) Testing of samples and other laboratory activities;
4) Insuring of personal property for mine subsidence;
5) Training and education;
6) Bonding and forfeiture activities;
7) Monitoring projects for reclamation construction projects and contracts;
8) Providing assistance for pollution prevention and energy efficiencies;
9) Planning and executing environmental programs;
10) Planning and executing environmental operations, such as clean-ups;
11) Emergency response;
12) Distributing and administering grants and subsidies;
13) Implementing and operating enterprise information technology infrastructure, custom software, and Internet web sites in support of core business processes and the resulting data;
14) Tracking and reporting on Oil & Gas activities, including Marcellus Shale permits, gas production, etc.;
15) Remediation.
B. Specific. BIT has defined its internal processes to support DEP’s goals, objectives, and environmental results via established standards and Standard Operating Procedures (SOPs), as well as following various ITBs issued by the Office of Administration. To properly execute the processes and functions within BIT, additional technical resources are required to complement the various employee teams. These teams utilize Oracle, Microsoft, Geospatial, and Java technologies to support the EAD. DEP’s EAD consists of software applications that are integrated within a product platform and among various platforms. Each technical team requires assistance for similar services as listed below:
1) Project Management Support;
2) Business Analyst Support;
3) Scoping documents and impact studies support;
4) Integration strategy support;
5) Requirements definition support;
6) Business Specification design and writing;
7) Technical Specification design and writing;
8) Database design support;
9) Coding support;
10) Unit, modular, system, and enterprise testing support;
11) Implementation support;
12) Trends and analysis and reporting support; and
13) Knowledge transfer.
C. Nature and Scope of the Project. This project is seeking information technology resources to assist the DEP in accomplishing its business objectives and Information Technology (IT) projects that impact the EAD. IT projects are requested by DEP employees to support:
1) Environmental support services;
2) Air Quality;
3) Water Quality protection;
4) Water supply management;
5) Municipal and residual waste;
6) Hazardous waste;
7) Land Recycling program;
8) Regulation of mining and industrial minerals;
9) Radiation protection;
10) Waterways engineering;
11) Watershed Conservation;
12) Oil and Gas Management;
13) Energy and technology development; and
14) Labs and sampling.
Approved technology projects and approved BIT Request For Services (RFSs) projects are assigned via Remedy for development by following both Waterfall and Agile development standards, as well as GOA’s Information Technology Bulletins and strategic initiatives. As standards and strategic initiatives change throughout the life of this contract, both DEP BIT and Offerer are expected to embrace the new direction. The technology projects affect DEP’s Central Office, Laboratory, 6 regional offices, 20 district offices, and 6 district mining offices. Travel to collect information for task and deliverables may be required. It is not expected that travel would occur more than ten (10) times per calendar year and overnight travel would not occur more than two (2) times per calendar year.
D. Infrastructure. DEP utilizes applications servers located at both the Enterprise Data Center (EDC) and the Data Power House (DPH) to run its applications. The application servers are running on a combination of Windows Server 2003, Windows Server 2008, and Windows Server 2000R2 virtual servers running on VMWare hosts. Those virtual servers use Oracle Fusion Middleware and Microsoft IIS to power DEP’s applications.
DEP utilizes a set of Oracle 11gR2 databases running on a virtual Oracle Enterprise Linux server and housed at the Data Powerhouse to provide the majority of its backend database processing, although smaller applications may utilize Microsoft’s SQL Server database rather than the enterprise Oracle databases.
DEP utilizes three environment types for both its internal and external applications: development, staging, and production. Each of these environments contains both middle-tier application servers (Oracle Fusion Middleware or Microsoft IIS 7) and the back-end database servers (Oracle or SQL Server). Applications are built on the development servers, tested on the staging servers, and deployed to the production servers. There also exist a Quality Assurance and a Training database utilizing Oracle 11gR2 for the enterprise testing and training.
DEP’s major internal enterprise applications are built using Oracle Forms and Reports 11g and run on a series of Oracle Fusion Middleware servers. These applications use DEP’s corporate Oracle database as their repository. Non-enterprise (and generally smaller), internal applications use a combination of Java running on Oracle Fusion Middleware servers and .NET running on Microsoft IIS 7 servers. These smaller applications use a combination of DEP’s corporate Oracle databases and local SQL Server databases to house their data. Relevant data stored in these repositories is loaded into DEP’s main corporate repository on a regular basis.
DEP’s major external, secure applications are built using Java and run on a set of Oracle Fusion Middleware servers collectively known as the DEP GreenPort. The DEP GreenPort uses Oracle’s Oracle Internet Directory (OID) as its LDAP server allowing a single sign-on mechanism to be used across its various applications. The DEP GreenPort applications use an Oracle database as their back-end repository. Relevant data stored in this repository is loaded into DEP’s main corporate repository on a regular basis.
DEP also has a set of external applications built using Microsoft .NET and running on Microsoft IIS servers. These applications store their data in either Oracle or SQL Server databases. Relevant data stored in these repositories is loaded into DEP’s main corporate repository on a daily basis.
IV-2. Requirements. IT projects can be requested by any DEP employee. A project initiator works with a supporting DEP System Coordinator to complete a Remedy ticket notated as a Request for Service (RFS). Resources provided through this contract will be assigned project tasks and deliverables through the RFS process. On any given day, approximately 100 IT projects are active and require appropriate deliverables. While deliverables can vary per project due to size, complexity, and methodology chosen, deliverables are required for all IT projects including enhancements, maintenance activities, upgrades, and software ‘bug’ fixes to existing applications and/or systems. All contracted resources will work on BIT technical teams and report to identified BIT team leaders, the Contract Manager or the CIO. Tasks are assigned with expected milestones, deliverables, and delivery dates in a Project Management Plan (PMP). DEP reserves the right to request the replacement of personnel if assigned milestones are not met or performance issues are not addressed promptly in DEP’s sole judgment. PMPs are updated biweekly or as agreed to by BIT team leaders, the Contract Manager, or the CIO. The PMPs should clearly identify the percentage of a task completed and any issues for management review.
At a minimum, the selected Offeror should be prepared to develop and support the environments as described in this RFP. The following is a brief description of what DEP views as the required level of support and expertise to properly deliver and support the known projects and to support the business areas and processes outlined in this RFP.
In order to provide the highest level of service and support to the DEP users and program areas, DEP is requesting an on-site comprehensive and experienced application development and support team with a minimal verifiable experience as follows:
1) Senior Developer for eGovernment
a. 20+ years of relevant experience
b. 4 year degree or equivalent technical study or advanced degree
c. Project Management experience
d. Oracle Database (11G and prior)
e. Oracle Application Server
f. SQL*Plus
g. PL/SQL
h. Java, including STRUTS and Enterprise Server Beans
i. Javascript
j. HTML
k. Developer
l. Entity Relationship Modeling
m. TOAD (or equivalent)
n. Web Services
o. Microsoft Team Foundation Server experience a plus
p. Experience developing environmental systems is required
2) Developer for eGovernment
a. 3-5 years of relevant experience
b. 4 year degree or equivalent technical study or advanced degree
c. Oracle Database (11G and prior)
d. Oracle Application Server
e. SQL*Plus
f. PL/SQL
g. Java, including STRUTS
h. Javascript
i. HTML
j. jDeveloper
k. Entity Relationship Modeling
l. TOAD (or equivalent)
m. Web Services
n. Microsoft Team Foundation Server experience is a plus
o. Experience developing environmental systems is a plus
3) Senior Oracle Developer
a. 20+ years of relevant experience
b. 4 year degree or equivalent technical study or advanced degree
c. Project Management Experience
d. Oracle Database (11G and prior)
e. SQL*Plus
f. PL/SQL
g. Oracle Developer Suite
h. TOAD (or equivalent)
i. Entity Relationship Modeling
j. Experience in creating web services
k. Microsoft Team Foundation Server experience a plus
l. Experience developing environmental systems is required
4) Oracle Developer
a. 10+ years of relevant experience
b. 4 year degree or equivalent technical study or advanced degree
c. Oracle Database (11G and prior)
d. SQL*Plus
e. PL/SQL
f. Oracle Developer Suite
g. TOAD (or equivalent)
h. Entity Relationship Modeling
i. Web services a plus
j. Microsoft Team Foundation Server experience a plus
k. Experience developing environmental systems is required
5) Senior Microsoft Developer
a. 20+ years of relevant experience
b. 4 year degree or equivalent technical study or advanced degree
c. Project Management Experience
d. Microsoft SQL Server Database (2012 and prior)
e. Microsoft Internet Information Server (IIS)
f. Microsoft Team Foundation Server
g. Silverlight
h. SQL (SQL server-based)
i. TransactSQL (T-SQL)
j. Visual
k.
l. VBScript
m. HTML5
n. Microsoft Visual Studio
o. Experience in creating web services
p. Microsoft SQL Reporting Services
q. Entity Relationship Modeling
r. Experience developing environmental systems is required
6) Microsoft Developer
a. 5+ years of relevant experience
b. 4 year degree or equivalent technical study or advanced degree
c. Project Management Experience
d. Microsoft SQL Server Database (2012 and prior)
e. Microsoft Internet Information Server (IIS)
f. Microsoft Team Foundation Server
g. Silverlight
h. SQL (SQL server-based)
i. TransactSQL (T-SQL)
j. Visual
k.
l. VBScript
m. HTML5
n. Microsoft Visual Studio
o. Knowledge of web services a plus
p. Microsoft SQL Reporting Services
q. Entity Relationship Modeling
r. Experience developing environmental systems is a plus
7) Project Manager/Business Analyst
a. 10+ years of relevant experience
b. Experience leading teams of varying sizes for developing IT systems
c. Must possess outstanding communication skills for portraying expectations, negotiating, and resolving issues to all stakeholders (management, end-users, IT staff, etc)
d. Experience with Microsoft Project or similar Project Management tool required
e. Experience conducting Facilitated Workshops for requirements analysis
f. Knowledge of formal requirements gathering methodologies
g. Experience developing Business Requirements
h. Experience developing Functional requirements
i. Experience developing User (stakeholder) requirements
j. Experience developing Quality-of-service (non-functional) requirements
k. Experience developing Report Specifications
l. Experience developing Requirements Traceability Matrix
m. Creates test models for product test and release control (plans, data, and scripts).
n. Conducts structured walk-throughs
o. Executes assembly or product tests.
p. Communicates accurate and useful status updates.
q. Able to work in a team environment
r. Strong organization and writing skills. Experienced developing graphic representations of complex business processes.
s. Experience developing environmental systems is a plus
This on-site project team will report directly to the appropriate DEP Contract Managers, who in turn report to the Application Development Division Chief. The applications development and support teams are responsible for all migrations/upgrades to the new Oracle architecture, new development in all areas of web, including Oracle, Java, and Microsoft, as described in this RFP, as well as for enhancements, maintenance and support of production applications including the migration and development of new portal systems within DEP, and future applications once deployed.
It is required that the team consist of experienced professionals, with full development life cycle support experience in order to deliver and support each of the DEP applications to the respective program areas. The following is a list of the skills and functional expertise necessary for the team of developers/analysts for this RFP.
1) Planning and Project Start Up
2) Research for New Development Projects (Feasibility Studies and Analysis)
3) Requirements Gathering from Users
4) Development of Functional and Technical Specifications
5) Architecture Planning, Design and Development
6) Analysis and Design
7) Application Development (Programming)
8) Application Testing & Integration
9) Quality Assurance
10) Pilot & User Acceptance (prior to final implementation)
11) Implementation Services and 3rd Party Software Tools
12) Final implementation & Acceptance/Sign-off
13) System Documentation
14) Enhancements to Current Applications and Systems Repositories
15) Application Maintenance and Support Services
16) Knowledge Transfer
DEP estimates needing the following number of position types to properly work on the known projects. Note: as new projects are initiated and existing projects are completed, the number of required positions, along with position types, may change. At no time will there be more than 25 total support staff on this contract. The original number and type of personnel required at the start of the project, and that should be reflected in the cost proposal to be attached separately by the Offeror’s response are described below.
Senior eGovernment Developer 1
eGovernment Developer 2
Senior Oracle Developer 4
Oracle Developer 5
Senior Microsoft Developer 2
Microsoft Developer 5
Project Manager/Business Analyst 1
_____________
20
IV-3. Operational Considerations. Typical business hours for the DEP are 7:30 AM – 5:00 PM, Monday through Friday, with the exception of Commonwealth holidays. Offeror must schedule all project meetings with Commonwealth employees during their normal business hours. All requests that would require Commonwealth project staff and Program staff to work beyond normal business hours must be approved by the DEP Contract Manager prior to the work being carried out. Any internal Company meetings that the Offeror deems necessary/required as part of Offeror company policy/process should be held outside of the typical business hours as outlined above. The selected vendor may be required to assist during scheduled releases and be required to work partial evening shifts and/or weekends. The vendor will be notified of these required tasks at least one week prior to the event. In emergency situations where a production problem needs to be resolved as soon as possible, it may not be possible to supply a week notice to work additional hours. These situations will be handled on a case by case basis between the DEP Contract Manager and the Offeror representative. Currently, scheduled releases occur the 1st and 3rd Wednesday of the month. In all cases, DEP will be invoiced for the normal hourly rate of the position participating in ‘off-hour’ work.
No vendor staff will work more than 41.5 hours/week unless previously approved in writing by the Contract Manager. No vendor staff is to start their work day after 9:00 AM unless previously approved in writing by the Contract Manager or the Team Lead. A standard work day will be 7.5 hours and a standard work week will be 37.5 hours. A standard work year is not to exceed 1875 hours unless previously approved in writing by the Contract Manager.
IV-4 Scenarios The following scenarios delineate three (3) projects that have been evaluated by the senior management staff of BIT and have been approved by the Contract Manager to proceed. These projects represent the type of work that will be required under this RFP and as such are being used to evaluate RFP responses, specifically as it relates to the Offeror understanding the problem, their approach, recommended resources, and technical solution. These three scenarios should NOT be viewed as the only projects that may be performed as part of this RFP.
• For each of the scenarios listed below, provide a response by using Appendix F as the template
• Diagrams have been provided in Appendix E – Architectural Diagrams, to demonstrate the existing DEP enterprise architecture
Scenario #1: Chapter 105 rewrite from existing Forms application to a Web based solution
The Department of Environmental Protection (DEP) currently accepts permit applications for the Water Resource Management (WRM) department’s Water Obstruction and Encroachment (WOB) program. These Chapter 105 permits grant an applicant the right to construct, operate, maintain, modify, enlarge or abandon a water obstruction or encroachment.
The Environment, Facility, Application, Compliance Tracking System (eFACTS), DEPs enterprise system, was modified to accept these joint Chapter 105 permits electronically. The project streamlined the submittal and review process for both the Chapter 105 permit holder, such as the Pennsylvania Department of Transportation (PennDOT), and for DEP. Specifically, through an electronic submittal of the general and detailed application data, along with the necessary attachments such as Hydraulics and Hydrology (H&H) files, the handling of paper between agencies was eliminated, data entry and validation time reduced, and quality checks created. The Submitter is now able to extract data from existing systems such as the Joint Permit Application (JPA) at PennDOT, enter additional data into simple Oracle forms, attach relevant documents, and send the package electronically to DEP via an XML transfer utilizing DEP’s Network Node.
DEP receives electronically submitted permit information into eFACTS, avoiding manual data entry time and potential for errors, and thus expediting the review and approval process. Joint Permit Review Agencies (JPRAs), such as the United States Army Corp of Engineers (ACOE), are notified of the application and given the opportunity to review and comment electronically as well. Throughout the process, notifications are sent between PennDOT and DEP, including notification of issuance. The application also supports the electronic submittal of updated attachments as necessary. Finally, the application provides notification of processing status and final action for permits (final disposition of the authorization) electronically from DEP to PennDOT. With the statewide initiative to upgrade the bridge infrastructure throughout Pennsylvania, the joint permit numbers have gone up. There are approximately 625 Chapter 105 type permits completed each year.
While this system has provided benefits to PennDOT, DEP, the ACOE and the submitters, the technical solution and flow of data is overly complex and involves multiple technologies (PennDOT’s JPA system, DEP’s Network Node, Oracle Forms utilized at PennDOT for entering DEP related data, XML cleansing scripts, XML transfers and various status notifications). DEP is interested in working with PennDOT to streamline the process, simplify the technical solution, and provide instantaneous status messaging by eliminating the Oracle Forms piece (utilized for entering DEP-related data), improve on the messaging between PennDOT and DEP by utilizing services or other, and removing the XML transfer piece and replacing with a Web based application. Below is a list of the major steps (not all) in the process that currently occur:
• A PennDOT user enters relevant data into its JPA system that may have attachments
• A PennDOT user enters the required, DEP specific data using an Oracle Forms application
• The combined data from the JPA and Oracle Forms system is extracted into an XML file and received in DEP via the Network Node. The process removes any attached documents from the XML
• Another process will parse the XML and populate tables and remerge the attachments with the data in a public facing, Oracle database. The PennDOT related data and the DEP related data are stored in two separate Oracle schemas. If any failures, data validations issues, or missing data is identified, the XML data will be sent back to PennDOT
• If the above process is successful, DEP will pull the above information into an internal Staging area for internal users to review and process. If the reviewer rejects the data (fails the review), another process writes a record back to the public facing, Oracle database. This will trigger a nightly job to generate a new XML file to be sent back to PennDOT with notifications. If successful, data is moved into DEP’s Production database, eFACTS, and notifications are sent to PennDOT
• There are additional statuses that may occur, requiring notifications back and forth between PennDOT and DEP
• There is a nightly refresh to the public facing, Oracle database from the internal Oracle enterprise database
Goal: This application needs to be streamlined, and be implemented with a better technical solution containing fewer components. Current support of this application is difficult. Software updates, such as, Oracle’s RBDMS, Java Runtime Engines, XML, and browser versioning is a constant issue, especially coordinating between the two agencies. Please provide a solution for handling the complexity, interaction, notifications, data storage, and reporting of the Chapter 105 Joint Permits by utilizing the template in Appendix F.
Scenario #2: Oil & Gas Predrilling Baseline Water Sampling
An Oil & Gas well operator that conducts drilling activities in the state of Pennsylvania and wishes to preserve its defense under section 208(d)(1) of the Act (58 P. S. §601.208 (d)(1)) that the pollution of a water supply existed prior to initial drilling activities, or alterations of an existing well, must conduct a predrilling survey in accordance with this section. A copy of the predrilling survey must be provided to DEP and the landowner or water purveyor within 10 business days of the receipt of the results from the lab.
Operators who conduct a predrilling survey must use a State Regulatory Agency (SRA) certified laboratory using USEPA SW-846 methods to analyze the water samples. Along with water samples, an operator will provide a field report explaining the sampling methods, locational information for each sampling site, site pictures and chain of custody documentation. Currently this is a voluntary action on behalf of an Oil & Gas Operator, however, future legislation may require all operators who conduct drilling activities to submit predrilling baseline water samples to DEP.
Business Requirements:
There will need to be a secure public facing web application that interacts with the backend Oracle database, eFACTS. Operators will need to submit the required documentation per 25 PA Code Chapter 78 § 78.52 under a registered Oil and Gas Operator number (OGO#) and associate the submission to an eFACTS Site. The web application should offer the ability for an operator to not only submit, but also view historical submission associated to their OGO#.
Operators will need to be able to submit dates to include DEP Submission Date, Sampling Date, Lab Analysis Result Receipt Date, Landowner or Water Purveyor Notification Date and Landowner/Water Purveyor Denied Access Certified Mail Date. The dates will be transferred nightly into eFACTS under the Site selected by the operator.
Operators will need to be able to submit Location (NAD83 datum) and metadata such as accuracy and elevation for each sample submitted. Operators will need to be able to submit laboratory analysis of sampling data according to USEPA SW-846 methods.
The collected lab analysis data and documentation will need to be stored in an Oracle database that allows DEP Inspectors to view the data based on locational information and/or Permit #. DEP Inspectors will need predrilling data available while onsite. Inspectors will need the location of each sample, lab analysis associated to the location, and any supporting documentation. This information should be available in a mobile format and represented spatially.
The web application should allow for public searches based on a location and provide any data associated to the area.
Goal: DEP has a need to implement an application that meets the above requirements and interfaces with its enterprise-system, eFACTS. Please provide a solution for this implementation by utilizing the template in Appendix F.
Scenario #3: Emergency Response and Complaint Submittal Application
The Complaints Tracking System (CTS) constitutes one of the major components of the process used by DEP to record, track and report complaint-related data received by the Department from any person, agency, or organization. A complaint is an instance of communication to DEP by individuals or groups describing an alleged event, an emergency requiring a response, an incident, a wrong doing or concern which is perceived as hazardous to life or the environment and/or believed to violate environmental law or laws.
The basic workflow for tracking complaints is triggered by a complainant (individual or group) reporting an environmental hazard or violation to DEP. This will result in the creation of a complaint record consisting of the date the complaint was received and details about the reported incident. Information about complainants and responsible parties (individuals or groups responsible for the incident) may or may not be recorded at this time since, and in many cases, complainants do not wish to identify themselves or the source responsible for the alleged violations is not known.
Once the complaint record has been created, the DEP Service Representative taking the call, assigns the complaint to the appropriate Program(s) for further action. Acknowledgement letters, providing details of the complaint and proposed actions to be taken by DEP, may be generated and sent out to the complainants (if known).
Coordination logic exists to maintain consistency between a complaint and details relating to it, such as incident details, responsible party/owner details, program(s) the complaint has been assigned to, investigations performed and actions taken to enforce compliance and how the complaint was resolved. Form letters can be generated as needed during the process. Complaint/Inquiry information may also be updated or deleted through this screen.
CTS is currently an Oracle 11G database and uses Oracle 11G Forms/Reports. It contains 11 screens and approximately 25 reports. Note, some of the reports were written in Oracle Reports and others in SQL Server Reporting Services (SSRS). The system is linked to eFACTS inspections and sub facility records.
Currently all emergency and complaint related incidents are received in DEP via phone call, at which time, a DEP representative will input the above data items to create a ‘complaint’ record. DEP is looking to enhance this process by developing a web based and/or mobile application enabling the public to generate a complaint record while on location at the area of concern. Ideally, locational data and photos could be included with the complaint record.
Goal:
Create a user-friendly external system for incidents to be reported more quickly, more accurately, and be directed to the proper DEP location to investigate. This effort is not to re-write the existing Oracle Forms based system, but to be an interface and enhancement to it.
Please provide a solution for enhancing the Complaints Tracking System. Utilize the template in Appendix F as appropriate.
IV-5. Tasks.
There exists various types and complexity of projects within DEP. Some projects include various levels of maintenance of legacy systems and those listed in the application inventory of Appendix G. Others may be comprised of new program area requests for completely new application systems. In each case, a team lead and the Contract Manager will determine the development methodology to utilize (Waterfall versus Agile), including the tasks to be incorporated. In general, a scoping of work will occur followed by analysis and the gathering of detailed requirements. Technical specifications are required to dictate the new/additional coding that must occur. The new applications or code piece will be tested, documented and moved into a staging environment for where a full system test will be performed. The testing may be performed by DEP staff, the Offeror staff, or other vendor staff contracted with DEP. Once an application is deemed ready, the new code and related scripts, data files, security, tables, etc. will be moved to the Production environment. Signatures of approval will be required at various stages throughout a project. In most cases, applications will be released into the Production environment following scheduled releases.
Below is a list of key tasks and related deliverables that are generally required for a project utilizing the Waterfall methodology. Contracted resources may be assigned any task below as determined by the BIT Team Lead or the Contract Manager:
1. Project Strategy Tasks
a. Identify objectives, priorities and critical success factors
b. Document end-user needs, organizational direction and constraints
c. Define and quantify system scope
d. Obtain management and end-user consensus and commitment
e. Establish a common set of business terms
f. Identify and analyze primary data entities
g. Define primary business units, end-user groups and locations
h. Develop a high level entity relationship model
i. Create a plan for proceeding
j. Establish a key stakeholder/user group
k. Establish a steering committee for issue resolution
l. Conduct scoping meetings
Deliverables:
a) Project management Plan/GANTT chart
b) Project Charter/Scoping document
c) Entity Relationship Diagram (optional)
d) Impact Analysis
e) Strategy Studies
f) Resource Assessment
g) Communications Plan
h) Meeting agendas
i) Project cost estimates
j) Project Status Report formats
k) Project Issue Log
2. Project Planning/Analysis Tasks
a. Create a fully attributed entity model
b. Identify preliminary data volumes, transaction frequencies, performance requirements, and estimated database sizing
c. Identify user types and security requirements
d. Define data conversion requirements if applicable
e. Define operational needs such as backup/recovery, auditing, controls, etc
f. Define user acceptance criteria
g. Define initial production transition needs such as training, data conversion, supply/equipment needs, etc
h. Clearly identify all assumptions and constraints
i. Conduct detailed analysis meetings and obtain end-user consensus
Deliverables:
a) Updated Project management Plan/GANTT chart
b) Functional Requirements Document (business/technical)
c) Fully attributed Entity Relationship Diagram/model
d) Constraints and Assumptions
e) Transition plan for Data Conversion (if applicable)
f) Data Element Dictionary updated
g) Security Architecture
3. System Design
a. Define system architecture
b. Create physical and logical database design
c. Develop detailed module/program specifications
d. Define detailed database sizing and storage parameters
e. Design data conversion and data clean-up scripts
f. Identify and define manual processes and procedures
g. Work with other assigned vendor staff to create end-user training plan
h. Work with other assigned vendor staff to develop draft user guides
i. Work with other assigned vendor staff to develop system test plan
j. Develop transition plan for installation, acceptance, and cut-over
Deliverables:
a) Detailed Design Document
b) System Test Plan
c) Transition Plan
4. Build/Coding
a. Ensure operational hardware/software are installed and functional
b. Develop system programs/modules
c. Perform module, integration and system level testing
d. Construct production database
e. Develop data conversion scripts
f. Perform walk-throughs/demonstrations with key stakeholders
g. Refine transition plan
Deliverables: (Note: many deliverables will be done in conjunction with other on- site vendor)
a) Completed and tested modules
b) Fully tested system
c) End-user and operations documentation
5. Transition: (Note: many deliverables will be done in conjunction with other on-site vendor)
a. Perform data conversion and data clean-up
b. Install production database and perform production data loading
c. Deliver end-user and operations documentation
d. Train end-users and other relevant staff
e. Perform acceptance testing
f. Implement help desk support
Deliverables:
a) Installed, operational and accepted system
b) Completed and approved documentation
c) Operations procedures
d) Implemented Change Review and problem reporting procedures
6. Production
a. Produce backup and recovery processes
b. Establish change control and problem reporting processes
c. Monitor and tune application software and database
d. Provide user account access with proper security levels
e. Train end users (to be done by other on-site vendor)
Deliverables:
a) Completed Production documentation
b) Scheduled performance reports
c) Completed, operational system
d) Lessons learned document
e) Technical cross training with BIT staff (if applicable)
In addition to the Waterfall Methodology for developing application system, DEP has begun utilizing more modern development techniques, such as Agile Development.
It should be noted that DEP is fairly ‘green’ to the Agile development methodology. While some projects have taken on a hybrid of Waterfall and Agile techniques, true Agile development is very immature at DEP. As such, Offerors are encouraged to recommend an Agile approach based on industry standards for projects where appropriate. As part of any recommendation, it should be made clear the required tasks, steps, workflow, documentation, etc, that a successful Agile development methodology should utilize.
IV-6. Service Level Agreements/Performance Metrics:
There exist few Service Level Agreements (SLAs) and performance metrics at DEP for application maintenance and new development. Offerors are encouraged to recommend an approach for service standards based on industry standards and best practices (please reference industry standards and best practices if utilized). However, at a minimum, the following performance standards must be followed throughout the life of this contract unless exceptions are approved in writing by the Contract Manager.
Table 1
|Service Level Agreements – Application Maintenance |
|Description |Metric |Target |Review Frequency |
|Staff Attendance |85% availability |Within 1 day |Daily |
|Restore Appl service. Includes code, database, and data |Restoration Time |Within 2 hrs of |Bi-Weekly |
|fixes, etc | |diagnosis. May refine | |
| | |based on issue | |
|Document root cause of incident |Report completion |Within 2 days of |Bi-Weekly |
| | |incident resolution | |
|Communicate periodic status updates during incident |Intervals until |Hourly updates |Monthly |
|response |resolution | | |
|Releases are implemented on time per the planned schedule|Implementation date |90% |Monthly |
|Limited # of post-implementation failures due to |Post-Impl defects or| ................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- new york state pa license verification
- ny state pa license verification
- mylicense state pa us renewal
- washington state pa license verification
- health state pa us vital records
- pa direct file state pa us
- secretary of state pa llc
- ems health state pa us ems portal
- ems health state pa us registry
- ny state pa license
- pa epatch state pa us
- webmail state pa us outlook