Narrative:

Aircraft X was descending on the ROKNN1 arrival into cgf; which allows the aircraft to cross roknn between 17;000 and 10;000 feet. Aircraft Y was level at 15;000 feet on course from cmh to ZZZ via bonzz. I turned aircraft Y to a 080 heading to maintain separation between the two aircraft but it was not enough and lateral separation was 4.92 miles according to the conflict alert. Aircraft Y was east of the roknn waypoint at this time. Prior to this happening; a [third aircraft] called VFR near the barber intersection. Through several transmissions; I finally determined it was an aircraft looking to do parachute operations near barber. Standard procedure is that these aircraft file with akron approach; akron works them in their airspace until transferring the data block and radio communications to the bsv sector. This did not occur today. The pilot said he contacted akron approach and the controller advised that he contact me. There was no flight plan in the system. This situation added to the complexity of the work session. More training would have been preferred with respect to the huge changes made to cleveland approach airspace from metroplex. I feel like I am learning while I am working; but [it] is very uncomfortable.

Google
 

Original NASA ASRS Text

Title: ZOB Center Controller reported separation was lost between two aircraft in the Akron area. Airspace changes related to Metroplex design were cited as contributing.

Narrative: Aircraft X was descending on the ROKNN1 arrival into CGF; which allows the aircraft to cross ROKNN between 17;000 and 10;000 feet. Aircraft Y was level at 15;000 feet on course from CMH to ZZZ via BONZZ. I turned Aircraft Y to a 080 heading to maintain separation between the two aircraft but it was not enough and lateral separation was 4.92 miles according to the conflict alert. Aircraft Y was east of the ROKNN waypoint at this time. Prior to this happening; a [third aircraft] called VFR near the Barber intersection. Through several transmissions; I finally determined it was an aircraft looking to do parachute operations near Barber. Standard procedure is that these aircraft file with Akron Approach; Akron works them in their airspace until transferring the data block and radio communications to the BSV sector. This did not occur today. The pilot said he contacted Akron Approach and the controller advised that he contact me. There was no flight plan in the system. This situation added to the complexity of the work session. More training would have been preferred with respect to the huge changes made to Cleveland Approach airspace from Metroplex. I feel like I am learning while I am working; but [it] is very uncomfortable.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.