Table of Contents - New York State Office of Information ...



Attachment 19: Technical Proposal FormsWhen completing the Technical Proposal Content, DO NOT include any pricing information and include the following information in the order enumerated below.Table of ContentsUse the following Table of Contents that reflects the areas identified in Technical Proposal. The Table of Contents should identify each major section of the Proposal, along with its initial-page number. When done entering information within this document, place your cursor within the table of contents below and press F9 to automatically update. TOC \o "1-2" \h \z \u Table of Contents PAGEREF _Toc528829035 \h 1Part 1 – Planning Documentation PAGEREF _Toc528829036 \h 2Part 2 – Staffing Plan PAGEREF _Toc528829037 \h 3Staffing Plan PAGEREF _Toc528829038 \h 3Roles and Responsibilities PAGEREF _Toc528829039 \h 3Part 3 – Tool Set, Architecture, Design, and Methodologies PAGEREF _Toc528829040 \h 4Part 4 - Previous work Experience PAGEREF _Toc528829041 \h 5Corporate/Business Background of Primary Bidder PAGEREF _Toc528829042 \h 5Corporate/Business Background of Subcontractor PAGEREF _Toc528829043 \h 5Previous Work Experience PAGEREF _Toc528829044 \h 6History of working with proposed subcontractor PAGEREF _Toc528829045 \h 9Part 1 – Planning DocumentationProject Management Methodology The bidder must supply a detailed project schedule and a detailed description of their proposed project management approach with sample deliverables. (specified in Section 3.5) The approach must include but is not limited to:Status reportsProject schedule managementProject task list managementQuality Assurance reporting for functional and non-functional defectsAll Planning documentation described in the planning deliverableProject Schedule The bidder must submit a high-level schedule that list out all deliverables and indicates the timeline to complete all deliverables within the timeline provided as Exhibit 1.Knowledge Transfer and TrainingThe bidder must fully describe and demonstrate how it will address the knowledge transfer and training requirements for the state staff assigned to the engagement. (specified in Section 3.6) Part 2 – Staffing PlanIn this section of the Technical Proposal, please provide information for all non-key personnel, as key personnel are addressed in Attachment 18 – Key Personnel Forms. Bidders should demonstrate that proposed staff have the necessary knowledge and demonstrated ability to provide the services required by this RFP. ITS reserves the right to reject any personnel proposed by Bidder and will review and approve any substitutions in staff from those proposed by the Bidder in its Proposal. Limit response to 1 page per person. (specified in Section 3.4)Staffing Plan Person Name: Proposed Role:Professional associations, certifications, and degrees:Number of years of relevant experience in the proposed role:Description of relevant experience:Roles and Responsibilities Bidder must submit with their proposal, proposed RACI diagrams that clearly defines the key personnel roles for all activities in scope of the engagement.Part 3 – Tool Set, Architecture, Design, and Methodologies Bill of Materials for Solution Architecture Itemized list of system components, software, and hardware required to implement the platforms and tools for the system integration and data migration to prepare for the DMV COTS solutions. (specified in Section 3.7.1.1)Architecture and Design System and data architecture which includes the conceptual solution architecture, data architecture, design approach, and methodologies. Describes in detail the major components of the system and depicts their relationships, connections, and interfaces. (specified in Section 3.7.1.1)System Integration Methodology The strategy for system integration will be to remediate, develop, and perform all testing of services that will be needed for integration with the core DMV COTS system in parallel with the phased system implementation. Wherever possible, the System Integration services will be proactively designed, constructed, and tested prior to final integration with the core DMV COTS system. (specified in Section 3.1)Data Quality Methodology The strategy for Data Quality for this engagement will be to stage, transform, clean/remediate, and publish data needed for the core DMV COTS system. The initial staging will capture the in-scope data for examination prior to transformation to additional stages for profiling, remediation, publication and implementation. (specified in Section 3.2)Quality Assurance Methodology The overall QA approach will place emphasis on a shift-left test type strategy, with emphasis on unit, component, and API/Service layer tests. The planning must provide a continuous testing capability to limit manual testing and leverage test automation, including the automation of API test scripts. Model-based testing of executable requirements, architecture, and design models must be included as a strategy for the QA solution. Final testing will involve the integration of services and data, with validation of all functionality impacted by the changes. (specified in Section 3.3)Part 4 - Previous work Experience The Technical Proposal must demonstrate to ITS that the Bidder has experience delivering services similar in scale and scope to the engagement described in this RFP. Complete the Bidder’s Experience form below to describe its company background and past experience in the Technical Proposal. Limit response to 25 pages.Corporate/Business Background of Primary BidderCompany ProfileDescription of the company’s corporate profile core businessService OfferingsDescription of serviceYears the Service has been providedCorporate/Business Background of Subcontractorcopy and complete this section for each subcontractor proposedSubcontractor Firm/Company InformationFirm NameFirm AddressParent CompanyAffiliatesOther Locations/Branches (if any)Subcontractor’s Primary ContactName, TitleAddressEmail AddressTelephone NumberSubcontractor ProfileDescription of the company’s corporate profile core businessService OfferingsDescription of serviceYears the Service has been providedPrevious Work Experience The Bidder shall describe its previous experience that qualifies the Bidder to provide the Services. Within the last five years, the Bidder must have completed at least three previous public or private sector projects with the total of these three projects being at?least $15M, resourced within the continental United States, which must be fully complete (i.e., in the warranty period or later), where the Bidder successfully implemented a modernization project focused on system integration and must have included at least one of the following:Remediation of?mainframe legacy applications by creating/migrating to service-oriented architecture solutionsData migration of data from VSAM to relational databasesMainframe to .NET based systems (specified in Section 2.1)Engagement 1 DescriptionEngagement Conducted By (Bidder/Subcontractor Company Name)Start DateEnd DateName of ClientNature of Client’s businessDescription of services ProvidedNumber and type of staff involvedEngagement results and benefits delivered to the clientEngagement budgetSize and complexity of engagement, including the number of sites and users within the Continental USList of Subcontractors and their dutiesEngagement 2 DescriptionEngagement Conducted By(Bidder/Subcontractor Company Name)Start DateEnd DateName of ClientNature of Client’s businessDescription of services ProvidedNumber and type of staff involvedEngagement results and benefits delivered to the clientEngagement budgetSize and complexity of engagement, including the number of sites and users within the Continental USList of Subcontractors and their dutiesEngagement 3 DescriptionEngagement Conducted By(Bidder/Subcontractor Company Name)Start DateEnd DateName of ClientNature of Client’s businessDescription of services ProvidedNumber and type of staff involvedEngagement results and benefits delivered to the clientEngagement budgetSize and complexity of engagement, including the number of sites and users within the Continental USList of Subcontractors and their dutiesIf sub-contractors are part of the Bidder’s Proposal, prior engagement descriptions may include engagements conducted by the subcontractor(s). The description of Bidder's prior experience shall include information about its history working with the proposed subcontractors (e.g., nature of relationship, number of engagements worked together, duration of engagements, budget of engagement, percent split between firms).History of working with proposed subcontractorNumber of engagements worked together: Engagement 1 - Describenature of relationshipStart DateEnd DateEngagement budgetPercent budget split between firmsEngagement 2 - Describenature of relationshipStart DateEnd DateEngagement budgetPercent budget split between firmsEngagement 3 - Describenature of relationshipStart DateEnd DateEngagement budgetPercent budget split between firms ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download