Pat met with Rich Murphy to continue coordination of the Service Catalog and the Service Portfolio. We reviewed the following:
- status of the Service Catalog RFP: still in Q&A with vendors, final award TBD
- feedback from senior staff on Service Catalog/web site current taxonomy: limited feedback received and incorporated
- Portfolio definitions: category, Service and solution
- draft Portfolio entry as illustration of taxonomy and definitions referenced above
- Service Catalog would like to consume information from Portfolio:
- create view (flag) customer facing Services and solutions in Portfolio OR
- run query for same
- Service Catalog would like to consume information from Portfolio:
- Portfolio technology options based on requirements document
- drupal as most desirable option to implement the Portfolio?
- Web Services would not be able to build this with current resources
- looking at about 6 month window before this work could start
- do we need architect to help with workflow?
- if we build it prior to Web Services offering, then we would be responsible for ongoing maintenance and support
- DCAD may be possibility
- would need to explore with Jeff if he has expertise to build and maintain
- Web Services would not be able to build this with current resources
- what about SharePoint as an option?
- we know this is on the horizon, but no resources currently available
- new technology for IS&T
- unclear as to what the support model would be
- what about an Oracle database with a front end (form)?
- Web Services could build in 3-4 months
- would also need DM resource to create physical data model
- drupal as most desirable option to implement the Portfolio?
This will be provided, in addition to previous technology discussion Service Portfolio Technology February 17, 2011 and the requirements documentation (download requirements here), to Marilyn as an update on 2/25. All this will also be reviewed by the Releaseball Core at the next team meeting on 3/3/11, and at the Sponsor meeting on 3/7/11.