Mainframe Developer

Vendor Minimum Experience Requirements

• The SOW Vendor must meet or exceed the following minimum experience requirements at the time of the SOW response submission and for the duration of the SOW:
• 5+ years’ supporting and maintaining CA-Gen applications.

Vendor Resource(s) Experience Requirements

The SOW Vendor shall include the following team members/resource(s) to administer and perform the contract requirements:

Leadership Team:

• 5+ years’ experience in each of the following: Cobol, CA-Gen, DB2, Web Focus, Batch, ASP, .Net Web Services, Business Analysis, System and Unit Testing.
• 5+ years’ experience working with the FAMIS application is preferred.

Working Team:

• 5+ years’ experience in each of the following: Cobol, CA-Gen, DB2, Web Focus, Batch, ASP, .Net Web Services, Business Analysis, System and Unit Testing.

• 2+ years’ experience working with the FAMIS application is preferred.

• The SOW Vendor resource(s) must report to the ITSD Project or Resource Manager or designee, who will provide resource(s) with sufficient knowledge to perform the work.

• Vendor resource(s) are expected to conduct themselves in a professional manner and dress in a professional manner.

• The SOW Vendor must provide resumes for all of the SOW Vendor’s resource(s) being assigned to the project for the review and acceptance by the State. The SOW Vendor’s resource(s) assigned to the project are subject to the approval or rejection by the State. If there would be a need to replace the resource(s) by the SOW Vendor, any subsequent proposed resource(s) may be interviewed by the State prior to acceptance.

• The Vendor’s resource(s) schedule and location for on-site or off-site work must be agreed upon by the SOW Vendor’s Project Manager, ITSD Project/Resource Manager and the Customer Product Owner.

• No out-of-state travel is required on the part of the State or the SOW Vendor resource(s) for completion of this project.

Performance Requirements

• ITSD DSS expects that the contracted support staff shall provide 50% of the total FAMIS maintenance and application support.
• ITSD DSS shall provide the awarded contractor a 15-day notice before the vendor is responsible for additional FAMIS maintenance and application support. After the 15-day notice, the vendor shall have 5 business days to submit qualified resource resumes for ITSD DSS review and approval.
• ITSD DSS shall have 10 business days to approve additional resources. ITDS DSS shall work with the contractor to ensure that the proposed resources have the required skill set.
• Vendor responses must include a resource utilization plan including the number of resources allocated to the project. The response must also address the vendor’s approach to increase resources to meet the additional capacity requirements.
• The contractor will report to the ITSD DSS Resource Manager and provide contract staff with sufficient knowledge and skills to resolve issues classified as “Critical”, “Major” and “Minor/Trivial” and provide maintenance and support for the FAMIS application, and all associated processes and systems currently being supported by the ITSD DSS FAMIS team.
• Contract staff must have experience maintaining and support DSS processes and functionality similar to what exists in FAMIS.
• The expectations of the contracted developer(s) include collaborate with business users (SMEs) to gather requirements and develop application code, ensuring code matches specifications and coding standards, performs unit/system test, prepare code for production implementation.
• Vendor responses must also include their approach to handling each of the issue classifications.
• All work will be prioritized by the ITSD DSS Resource manager and DSS FSD. The ITSD DSS Resource Manager or designee in coordination with FAMIS management will authorize and assign all issue/problem work to be performed.
• The ITSD DSS Resource Manager or his/her designee will make the appropriate resource assignments to complete the work. Work on these issues/problems will commence within a designated time frame based on the priority and category.
• Each deliverable/problem report assigned under this SOW shall be documented in JIRA and shall require a description/cause of the problem, the resolution to the problem, what was done to correct it, and updated documentation.
• The consultant is required to maintain a status in JIRA every Friday by noon, 12:00 p.m. that indicates the project status.
• All maintenance and support work outside of normal work hours (Monday – Friday 8:00 a.m. – 5:00 p.m.) must have prior approval from the ITSD DSS Resource Manager.
• The State shall be invoiced on a monthly basis for the actual cost incurred (i.e. hours not to exceed the SOW total) for each maintenance and support issue/problem where worked hours were logged during the month and accepted by ITSD DSS.

Reporting Requirements

• The SOW Vendor must provide weekly status reporting on the services being provided to the State of Missouri using the ITSD Status Report template. The SOW Vendor shall provide overall project percent complete, items for management attention, action items, project decisions made, risks, out of scope work identified, and track change request items. Current percent complete must be reported for all deliverables and payment milestones.
• The ITSD Project Deliverable Acceptance Form (PDAF) must be used for deliverable acceptance. Items may require a deliverable review meeting wherein the SOW Vendor walks through the deliverable with the ITSD and agency staff, followed by revisions as required, and finally, with a request for approval and associated payment per the SOW.

Technical Environment Requirements

• Depending upon the agency preference, either State owned Microsoft ADO or JIRA shall be used to record, track and resolve issues, bugs and defects.
• The SOW Vendor must have all necessary licenses to provide IT services in conjunction with the award of this SOW. SOW Vendor shall purchase/supply and maintain the required licenses (per developer) for all development tools for the duration of the project, unless specifically indicated by the SOW.