Architectural Review Board
The Architectural Review Board (ARB) identifies projects that require architectural direction and ensures that the right expertise provides advice on the proper solution. The ARB makes all final decisions on architectural strategy and approach for Bridges projects. Projects requiring oversight include those that utilize new technologies or methods that have not yet been proven in a Bridges production environment as well as projects that propose continuing outmoded or deprecated technologies and approaches. This board is staffed by a core group of four strategic/technical managers including the PeopleSoft Implementation Officer (PIO), Bridges Associate Director, Infrastructure Manager and Development Manager. Additional input is sought by the ARB on a proposal by proposal basis.
The PeopleSoft Implementation Officer has a key role in the ARB. The PIO provides necessary high-level insight to architectural decisions by taking into account the business needs of the University in addition to a broad understanding of technical implementations and interactions between Bridges, its customers and other service providers. The PIO provides the drafts and/or outlines of architectural strategy that the ARB can use as a guide in its recommendations. The Bridges associate director is focused on Bridges strategic projects and initiatives and is responsible for bringing strategic issues to the ARB. The associate director will facilitate these meetings, coordinate expert assistance on projects and help the group reach its decisions. While the Bridges director may not be directly involved in the ARB, he/she approves all final decisions (especially where budget is concerned).
The project charters that have been selected by the ARB for oversight will be assigned an ARB core team member to act as liaison with the project team. The liaison will have the responsibility for ensuring that the ARB is kept current on all key project decisions so the ARB can adequately provide support.
Current ARB Members
PeopleSoft Implementation Officer (PIO):
Mike Conlon
Bridges Associate Director:
Dave Gruber
Infrastructure Manager:
Chris Easley
Development Manager:
Jim Freymann
Papers
Architectural Recommendation for the Interface of Campus
Community and the UF Directory [05 July 2007]
Asynchronous messaging with robust message handlers at three steps in the
transport path – mainframe, hub and PeopleSoft – is recommended
for synchronizing Campus Community data with the UF Directory. Work is needed
to identify the population to be synched. Additional work is needed to identify
message handling software for the mainframe that would support the proposed
architecture for this and future projects.
Contact
Please contact the ARB Liaison, Dave Gruber, at (352) 273-1014 for additional information or assistance.
