• US Citizen

• Green Card

• EAD (OPT/CPT/GC/H4)

• H1B Work Permit

• Corp-Corp

• Consulting/Contract

• UG :- - Not Required

• PG :- - Not Required

• No of position :- ( 1 )

• Post :- 23rd Aug 2022

 The mainframe system is written primarily in COBOL. SDAT is looking to convert this system into a modern programming language, such as JAVA or C++ and move to a cloud-based platform. 

 Following tasks need to be accomplished 1. Inspect and analyze the converted code for its likeness between old and new languages. 2. Review the quality of the converted code and its readability. 3. Learn the requirements of the deployment for the converted code. (Third party components will be included, if applicable) 4. Learn the requirements of maintenance and support of the new coding language.  Learn the requirements of the resources for the complete mainframe migration project. 6. Learn the costs and timelines in relation to the mainframe migration project. 7. Convert the entire mainframe and create a production environment. 8. Test production throughout each phase. For Part One of the project, the most qualified vendor must perform the following on the Service of Process subsystem: 1. Implement automated conversion of COBOL programs to a modern programming language, using appropriate toolkits where possible, and manually convert code where the toolkit cannot automatically convert. 2. Show the consumption of data from an input file and verification on a cloud platform through accessing tables from a DB2 instance. 3. Confirm the output on the cloud platform is the same as the mainframe application, through automated and manual inspection and comparison. 4. Engage with SDAT to host strategizing sessions themed around SDAT needs. 5. Engage with the SDAT IT team to capture all source code provided and make it ready for the Assessment tools. 6. Construct a list of requirements, applications and database dependencies, user groups, and data to be assessed. 7. Detail the prospective state of the cloud environment required to promote SDAT’s requirements, including: Identity Access Management, Clustering Strategy, Cloud Storage buckets, billing, and operations. 8. Display the Technical Design Document with the recommended architecture along with the project closeout document. 9. The MBES “Service of Process” subsystem provides a alternative mechanism for citizens to serve business entities in Maryland. If an entity is unresponsive to regular service, the State can step-in and act as the recipient and will make additional attempts to serve the entity. This involves a small fee to the requestor, and is sufficient for legal purposes. For Part Two of the project, after SDAT provides a Notice to Proceed, the most qualified vendor must perform the following: 1. Convert old code COBOL to the new programming language; 2. Mirror functionality of 3rd party utilities; 3. Take data from the mainframe, convert, and load into a SDAT-prescribed database, connected via the new platform; 4. Test to provide correctness of conversion; 5. Run scheduled batch processes that replicate existing z/OS schedulers; 6. Train SDAT IT personnel (up to three workshops) on a schedule package implemented by the vendor; 7. Execute a full performance review, measuring Maryland Business Entity System (MBES) mainframe against the new cloud platform; 8. Enhance the new code and present sizing recommendations for the new cloud platform; and, 9. Provide integration with the ideal cloud solution to set up the batch jobs.