VENDOR INFORMATION FOR RFP 3462 Vendor Provide all requested information in the space provided next to each numbered question. The information provided in Sections V1 through V6 shall be used for development of the contract; Type or print responses; and Include this Vendor Information Sheet in Section III of the Technical Proposal. V1 Company Name V2 Street Address V3 City, State, ZIP V4 Telephone Number Area Code: Number: Extension: V5 Facsimile Number Area Code: Number: Extension: V6 Toll Free Number Area Code: Number: Extension: V7 Contact Person for Questions / Contract Negotiations, including address if different than above Name: Address: Email Address: V8 Telephone Number for Contact Person Area Code: Number: Extension: V9 Facsimile Number for Contact Person Area Code: Number: Extension: V10 Name of Individual Authorized to Bind the Organization Name: Title: Signature (Individual shall be legally authorized to bind the vendor per NRS 333.337)
Quality Assurance (QA) The Program will procure the services of a QA contractor before the Implementation Contractor begins work. The QA contractor will be independent of the Implementation Contractor and will work with and report to the Program’s Project Management Team to develop a quality management plan, monitor project tasks and activities, and report on deviations from the approved project management plan. The Program’s staff will work with the QA contractor to ensure that the project conforms to the approved schedule and that deliverables maintain the high quality expected. The QA contractor will begin work no less than sixty (60) days before the start of the project to establish the Program’s quality assurance standards and processes. STANDARD PROJECT PROCESSES AND PROCEDURES The Program will use a range of management processes and procedures to ensure its successful completion. The PMO contractor will prepare the basic planning documents to govern the conduct of the project including: Organizational change management plan; Risk management plan; Scope management plan; Project schedule management plan; Cost management plan; Staffing management plan; Communication management plan; Change control and issue management plan; and Project control procedures. The Implementation Contractor is expected to follow these processes and procedures unless otherwise stated. The project procedures will include the following standard components: Weekly Project Schedule Reporting and Management The Implementation Contractor will develop an initial project schedule, including placeholder tasks for the Program Project Management Team as well as the QA contractor. The schedule will be reviewed and approved according to the Deliverable Approval Plan. Based on the Implementation Contractor’s approved schedule, the Project Director will work with the project team, including the Implementation Contractor, to finalize a comprehensive schedule as early as possible. In accordance with the Project Schedule Management Plan, all project participants, including the Implementation Contractor’s project manager, will update the schedule each week with the status of their tasks. The Program, PMO, QA, and the Implementation Contractor’s project management teams will meet weekly to review the project schedule and adjust resources as needed to maintain the project schedule and ensure development of a
Quality Control Specialist Clerical 2 5 Elko Program Area Office – Child Support Enforcement 1020 Ruby Vista Dr. #101 Elko, NV 89101 Supervisor Case Manager Clerical 1 3 1 Nevada Intergovernmental Initiating Office – Child Support Enforcement 1900 E. Flamingo Rd., Suite 115 Las NV 89119 Field Operations Manager Quality Control Specialists Office Manager FSS II Supervisor FSS III Clerical 1 2 1 6 2 12 4 Reno Program Area Office – Support Enforcement 300 E. 2nd St., Ste 1200 Reno, NV Office Manager Supervisor Case Manager Clerical 1 4 36 8 State Collection and Disbursement Unit 1470 College Parkway Carson City, NV 89706 Chief II 1 State Collection and Disbursement Unit 1900 E Flamingo Rd. Suite 115 Las Vegas, NV 89119 Manager Management Analyst Supervisor Clerical 1 2 2 9 Churchill County District Attorney 165 North Ada St. Fallon, NV Coordinator Case Manager Clerical Attorney 1 4 1 1 County District Attorney Family Support Division 1900 E. Flamingo Rd., Suite 100 Las Vegas, NV 89119 Director Assistant Director Unit Administrators Supervisors Case Managers Clerical – Clerks Financial Office Staff IT Staff Attorney Investigation/Process Server 1 1 5 30 102 78 3 12 11 9 Douglas County District Attorney 1038 Buckeye Road Minden, NV 89423 Coordinator Caseworker Attorney 1 3 1 Elko County District Attorney 540 Court Street, Second Floor Elko, NV 89801 Program Manager Case Manager Clerical Attorney 1 4 2 1 Humboldt County District Attorney 20 E. 5th St. Winnemucca, NV Coordinator Case Manager Clerical Attorney 1 3 1 1 Lyon County District Attorney 31 S. Main St. Coordinator 1
Yerington, NV 89447 Case Manager Clerical Attorney 3 1 1 Mineral County District Attorney 166 E Street Hawthorne, NV 89415 Coordinator Case Manager 1 1 Nye County District Attorney 101 Radar Road Tonopah, NV Coordinator Case Manager 1 5 Pershing County District Attorney 535 Western Avenue Lovelock, NV 89419 Coordinator Caseworker 1 1 Washoe County District Attorney 1 Sierra Street, 4th Floor Reno, NV 89520 Program Manager Assistant Manager Supervisor Case Manager Clerical Legal Secretary Training IT Staff Attorney Investigations 1 1 4 18 2 9 1 3 3 2 CURRENT COMPUTING ENVIRONMENT DESCRIPTION NAME Database Management Systems DB2 for ZOS 10.1 UDB 10+ for Distributed Environment Computing Platform AIX V7.2/Windows 2012/ Z/OS/ESX6, SLES11+ Network TCP/IP, WAN, Cisco, F5 Storage 110 Terabyte Application Infrastructure JAVA, Spring MVC framework, J2EE, CICS, Enterprise Generation Language (EGL) Security Novell Access Gateway 4.x / E- DIR / IDM, Active Directory Utilities Business Objects XIR2 Adobe Forms V5+ WebSphere Application Server on AIX WebSphere Process Server WebSphere Business Monitor WebSphere Decision Server WebSphere Decision Center WebSphere Enterprise Service Bus WebSphere MQ FileNet P8 Environment Erwin Data Modeler Source Code Management Perforce
System Requirements and Design – defining the technical approach, developing the functional and technical detailed system designs, and evaluating the donor code base. Development/Modification/Conversion of System Software Code – developing, modifying, and converting child support system software; and installing operations hardware and software. Data Conversion – planning for the legacy conversion, converting the data, and testing the data conversion. Testing and Acceptance – testing the hardware and software (e.g., system testing, integration testing, “smoke testing”, and regression testing; performance and load testing; and user acceptance testing). Ensure data is production quality in all environments. All production data must be masked and cleansed in environments. Non-production environment must be of sufficient capacity, with enough data to ensure that testing will expose production level issues. Training – training operational readiness, end users, and site support staff. System Implementation – converting data for rollouts, decommissioning the child support portion of NOMADS (the old system), and rolling out the pilot region and all regions. Initial Maintenance and Operation – maintaining and operating the system during system warranty. System Certification – planning and preparing for federal system certification. Transition for Maintenance – training state technical and help desk staff for long-term maintenance and operation of the new system. Project Closeout – planning for project closeout to ensure all artifacts are archived, vendors are released, and accounts are settled. SYSTEM REQUIREMENTS VENDOR RESPONSE TO SYSTEM REQUIREMENTS The Implementation Contractor will prepare the RTM deliverable to document each of the baseline requirements, the changes that adjusted or expanded the requirements, the system components that implemented each requirement and the that verified them. The Implementation Contractor will maintain the RTM on an ongoing basis. The QA contractor will review the RTM on a periodic basis to ensure that all entries conform to project requirements. The Implementation Contractor will purchase the RTM software tool, subject to the Program’s approval of the tool. The Program’s staff, the PMO contractor, and the QA contractor will have copies of this tool so they can read and review the RTM. Functional designs, technical designs, test case development, code construction and unit testing, test execution, and training materials will address all requirements.
If you are unable to access contract form, please contact Nevada Purchasing at for an emailed copy. ATTACHMENT D – INSURANCE SCHEDULE FOR RFP 3462 Vendors shall review the Insurance Schedule, as this will be the schedule used for the scope of work identified within the RFP. To open the document, double click on the icon. If you are unable to access the above inserted file once you have doubled clicked on the icon, please contact Nevada State Purchasing at for an emailed copy.