There is no infrastructure on CPAN to really model an organisation. What you can do is either do as MQSeries did and create the "MQ Engineering Group" account, and hope that the administrator of that account does not leave the company without handing over the credentials. The alternative would be to have contributors sign up on CPAN individually and hand them co-maintainership.

The "group account" approach has the advantage of keeping the administration of the account simple, but creates a bottleneck for releases etc. where those credentials are needed.

The "comaintainer approach" has the advantage of allowing all comaintainers to release versions of the modules even across organisations, at the cost of needing more maintenance to add or remove comaintainership status.

Personally, I only have experience with the comaintainership approach in private settings and so far it has worked well enough.