本文发表在 rolia.net 枫下论坛Good day,
Just a quick note- to see if you or your referral may be qualified, interested and available for a contract 4 months with the Ministry of Government Services -iServe
We have received a tough order from iSERV for a Service Desk Consolidation Integration PM
This is a position for a PM specialist in Biztalk & ITSM! - who ideallyas prior PUBLIC SECTOR experience in this role .
Start November and ends March 31st.?Rate is up to $88/hr
Please forward updated resumes, 3 references and a profile by Tuesday October 5th by 3pm.
Thanks!!!
Below you'll find an excerpt from the attached RFP document and skills matrix form (to be completed?by the qualified party applying to this RFP):
RFS#????????????? ITSM 462 0506 HI-010
Client:???????????? Ministry of Government Services iSERV Ontario Division
????
Role:????????????????????Service Desk Consolidation Integration PM
Client:???????????????????Branch:???OCCTO, ITSM & Change Management Branch
Location:???????????????? 155 University Avenue
Project Name:?????????????u> Service Desk Consolidation
Computing Environment:?????Win 9.x/NT; Windows 2K; XP
Project Start Date:?????????? November 1, 2005
Project End Date:?????????? March 31, 2006Environment:??/span>????????
?/p>
BACKGROUND INFORMATION
The ITSM enabling technology strategy for the OPS is being implemented with the Service Desk Consolidation (SDC) project. The ITSM program includes both the ITSM Standards and Tools Project and SDC. SDC was recently integrated into the ITSM Enterprise Program Office (EPO) to ensure alignment of enabling technology with ITSM OPS Standards.
SDC implements an enterprise ITSM Tool (CIT) to automate ITSM Processes, consistent with a Terminology Reference Model (TRM), to enable delivery of service management, measurement, and reporting capabilities end-to-end across the IT Service Chain.
SDC provides a single, OPS-wide technology solution to manage incident and change information for IT Infrastructure Services and eventually Utility Infrastructure Management Services (UIMS). In addition SDC requires mandatory consolidation of all service desk technologies into a single ITSM technology provider / solution set.
Prior integration work has produced a working point-to-point integration tool that has been activated (the Pilot integration ), using BizTalk 2004, between iSERV (internal infrastructure service provider) and the Justice Cluster (Justice sector Ministry I&IT service provider) enables the exchange of incident information.
The Pilot confirmed the use of BizTalk as a suitable message broker for ITSM information exchange. Justice and iSERV prepared and licensed production and development environments that are active today.
The Pilot Bridge, a point solution (fixed providers), has been in production since November 2004 with limited issues. The pilot XML schemas have been labeled version 1.0 . Please note that Justice used the same bridge architecture, with parallel orchestrations and schemas (modified and referred to as 1.1) to activate a production bridge with an external service provider not associated with the pilot iSERV / Justice exchange.
Since the pilot was implemented new schemas have been developed, but have not been released to production, as they would require orchestration modifications and are better suited for a true hub/spoke model. An initial step in finalizing the schemas (version 1.2) has occurred. ?/span>It is anticipated that minor business review for Service Request provisioning, a classification of Incidents, will be required (proposed version 1.3).
A third-party vendor who provided an assessment of the architecture, and made recommendations for using the BizTalk Business Rules Engine (BRE) and the Trading Partner capabilities of BizTalk to enable future integration partnerships audited the Pilot. These recommendations have not been implemented or tested between Justice and iSERV.
The Common ITSM Technology (CIT) is an OLTP system based on BMC Remedy and will serve as the hub data repository for exchanged incidents with either external providers or internal stakeholders.
The continuing work to build on the pilot integration work to deliver an enterprise integration hub has been divided into four phases of work. The plan calls for:
Phase 1 Integration Hub Readiness
Develop a production ready enterprise integration solution with the existing service chain partners activated.
Phase 2 Integration Hub Activation
Activate the hub for Utility Infrastructure Management Services (UIMS) and one or more external solution providers (candidates are desktop management and integrated network provider).
Phase 3 Cluster Activations
Activate the clusters permitting clusters to exchange incidents with horizontal providers (UIMS and CCAS) and with CIT for dispatch to external service providers.
Phase 4 Legacy Retirement
Deactivation of the HP Bluestone Bridge and retirement of legacy bridges following closure of all outstanding incidents (new and old bridges are to run in parallel until this occurs).
CLIENTS REQUIREMENTS
Purpose
A Service Desk Consolidation (SDC) Integration Project Manager /Leader is required to ensure seamless conduct of activities of the Integration Development team through the three phases planned for this fiscal and integrate them with the initiatives planned for CIT (reporting solution, service categorization framework implementation, Utility Infrastructure Management Services horizontal service requirements).
The resource will also provide tactical planning and direction for the CIT Service Delivery Manager as it relates to the Integration Project primarily in the area of testing strategies, commissioning strategies and the establishment of the pre-Production environment and staging area with the CIT infrastructure. Previous investments and collateral developed in the Integration pilot will be leveraged.
Requirement
This RFS requires a Project Manager / Leader (role 1 level 2), for a maximum of 90 days effort with OLTP Integration knowledge and extensive ITSM process experience to extend a pilot ITSM solution into an enterprise solution. The resource will manage project deliverables to timelines and budget, own the project plan and schedule and provide a single point of contact to the SDC Project Team and Client / Partner Transition Project Sponsors. In addition this resource will act as a pseudo-Client for development and delivery of the CIT Reporting Solution, the implementation of the Service Categorization Framework for UIMS and management of the CIT infrastructure upgrades to be undertaken by iSERV.
Scope (please address each point with your experience below);
The scope of the work required to satisfy Phase 1 entails developing an enterprise integration hub to comply with requirements, some of which are outlined below.
Define and implement enterprise integration architecture, including collateral suitable for OPS Architecture Review (Contextual, Conceptual, Logical and Physical views of the architecture, based on Zachman EA framework)
Design hub-spoke architecture, with CIT as the core incident repository. CIT will serve future business intelligence by centralizing incident exchange data.
Align the enterprise integration architecture with OPS Support Model framework (Virtual Single Point of Contact) to enable key business communication requirements and allow for true end-to-end service management
Review the updated XML Schemas and make changes if necessary to include any additional data values to support Service Request incident exchange.
Implement incident management schemas and update as required to enable hub-spoke model.
The production architecture (and infrastructure) will initially be based on a single physical BizTalk server implementation for the hub, but a logical path for expanding to more servers will be required for both capacity and availability planning purposes (i.e. address business continuity plans at some future date).
Test the bridge orchestrations with Justice who manages an interim BizTalk environment to confirm logic is valid.
Plan deployment activities and architecture considerations where appropriate to allow for a partner to have more than one bridge orchestration running.
Define an architecture that allows for further process integration to occur (these additional processes are out of scope for this project phase). This could be separate orchestrations because previous orchestrations are not likely completely transferable. There may be some error handling aspects that should be kept separate and used across all processes regardless of the exchange type.
Document all architecture and operation procedures to ensure successful knowledge transfer to internal OPS staff.
SDC Integration Project Manager
The SCD Integration Project Manager is required to provide coordination of the Integration project team and to assess and provide input to the requirements for the planned RFI. Areas of focus will be:
the Reporting Solution;
the implementation of the Service Categorization Framework for the OPS within CIT;
the assessment and definition of the Service-based requirements for the tool driven by UIMS; and
direction of the iSERV resources charged with implementing updates to the iSERV CIT Solution blue print.
The work will be orchestrated and directed by the ITSM Project Director who will articulate the project vision setting the direction for the project, establish the project outcomes, and define the work package requirements for the team in collaboration with the ITSM Integration SME and the BizTalk Architect. Once underway the ITSM Project Director will attend weekly status reporting and respond to questions about direction / scope.
Deliverables:
The SDC Integration Project manager will develop and maintain the following deliverables:
?span style="font:7pt 'Times New Roman'">???? Develop a detailed project schedule highlighting major milestones and any external dependencies
Provide the Project Sponsor and SDC Service Owner with regular Status and Reports
Develop strategies/approaches as required to address project issues
Manage assigned team to complete scheduled tasks and deliverables
Align activities and work plans to other linked projects (i.e. UIMS
With time permitting the SDC Integration Project Manager will conduct other related assignments as required. These assignments may include: quality improvement initiatives and / or knowledge transfer to an incoming replacement resource.
Beyond Scope of Services and Deliverables - The following activities are not within the scope of this Statement of Work:
Out of Scope- Phase I Enterprise Integration:
?span style="font:7pt 'Times New Roman'">???? An ability to integrate a non-CIT user to an external service provider, and
?span style="font:7pt 'Times New Roman'">???? Support for other ITSM processes (Change, Service Level Management) from an integration perspective.
For those replying - we'll need your latest CV, 3 References, and your response(qualifications)?to the responsabilities for the "In-Scope"roles & activities.(with your name at the top!) and your consulting rate for an hourly fee-for-service contract.
Your help and time greatly appreciated.
Your call and referrals - welcome, always!
David R. Smith
Personally celebrating 20 years; Helping Corporate Leaders & Winners Continue to Succeed
>>> Specializing in Enterprise Project Management and E-PMO expertise <<<
????????????(LinkedIn; see who we know in common!), & connected by PLAXO (www.plaxo.com)
GSI International Consulting Group
"Your Project's Success is Our Measure of Achievement"?br>?/span>????Direct Line: (416) 777-2517?- Monday to Friday 7:30am- 7:30pm
?/span>????Mobile: (416) 768-2527 - call forwarded to this number when out of office.
o??? Main Tel:? (416) 777-2525 ext. 255
o??? Fax:?(416) 777-2547 (Attention Line)
?/font>55 University Avenue, Suite 1601, Toronto, Canada?M5J 2H7
dsmith@gsigroup.com? www.gsigroup.com
This message is intended only for the use of the intended recipients and it may be privileged and confidential.?更多精彩文章及讨论，请光临枫下论坛 rolia.net
Just a quick note- to see if you or your referral may be qualified, interested and available for a contract 4 months with the Ministry of Government Services -iServe
We have received a tough order from iSERV for a Service Desk Consolidation Integration PM
This is a position for a PM specialist in Biztalk & ITSM! - who ideallyas prior PUBLIC SECTOR experience in this role .
Start November and ends March 31st.?Rate is up to $88/hr
Please forward updated resumes, 3 references and a profile by Tuesday October 5th by 3pm.
Thanks!!!
Below you'll find an excerpt from the attached RFP document and skills matrix form (to be completed?by the qualified party applying to this RFP):
RFS#????????????? ITSM 462 0506 HI-010
Client:???????????? Ministry of Government Services iSERV Ontario Division
????
Role:????????????????????Service Desk Consolidation Integration PM
Client:???????????????????Branch:???OCCTO, ITSM & Change Management Branch
Location:???????????????? 155 University Avenue
Project Name:?????????????u> Service Desk Consolidation
Computing Environment:?????Win 9.x/NT; Windows 2K; XP
Project Start Date:?????????? November 1, 2005
Project End Date:?????????? March 31, 2006Environment:??/span>????????
?/p>
BACKGROUND INFORMATION
The ITSM enabling technology strategy for the OPS is being implemented with the Service Desk Consolidation (SDC) project. The ITSM program includes both the ITSM Standards and Tools Project and SDC. SDC was recently integrated into the ITSM Enterprise Program Office (EPO) to ensure alignment of enabling technology with ITSM OPS Standards.
SDC implements an enterprise ITSM Tool (CIT) to automate ITSM Processes, consistent with a Terminology Reference Model (TRM), to enable delivery of service management, measurement, and reporting capabilities end-to-end across the IT Service Chain.
SDC provides a single, OPS-wide technology solution to manage incident and change information for IT Infrastructure Services and eventually Utility Infrastructure Management Services (UIMS). In addition SDC requires mandatory consolidation of all service desk technologies into a single ITSM technology provider / solution set.
Prior integration work has produced a working point-to-point integration tool that has been activated (the Pilot integration ), using BizTalk 2004, between iSERV (internal infrastructure service provider) and the Justice Cluster (Justice sector Ministry I&IT service provider) enables the exchange of incident information.
The Pilot confirmed the use of BizTalk as a suitable message broker for ITSM information exchange. Justice and iSERV prepared and licensed production and development environments that are active today.
The Pilot Bridge, a point solution (fixed providers), has been in production since November 2004 with limited issues. The pilot XML schemas have been labeled version 1.0 . Please note that Justice used the same bridge architecture, with parallel orchestrations and schemas (modified and referred to as 1.1) to activate a production bridge with an external service provider not associated with the pilot iSERV / Justice exchange.
Since the pilot was implemented new schemas have been developed, but have not been released to production, as they would require orchestration modifications and are better suited for a true hub/spoke model. An initial step in finalizing the schemas (version 1.2) has occurred. ?/span>It is anticipated that minor business review for Service Request provisioning, a classification of Incidents, will be required (proposed version 1.3).
A third-party vendor who provided an assessment of the architecture, and made recommendations for using the BizTalk Business Rules Engine (BRE) and the Trading Partner capabilities of BizTalk to enable future integration partnerships audited the Pilot. These recommendations have not been implemented or tested between Justice and iSERV.
The Common ITSM Technology (CIT) is an OLTP system based on BMC Remedy and will serve as the hub data repository for exchanged incidents with either external providers or internal stakeholders.
The continuing work to build on the pilot integration work to deliver an enterprise integration hub has been divided into four phases of work. The plan calls for:
Phase 1 Integration Hub Readiness
Develop a production ready enterprise integration solution with the existing service chain partners activated.
Phase 2 Integration Hub Activation
Activate the hub for Utility Infrastructure Management Services (UIMS) and one or more external solution providers (candidates are desktop management and integrated network provider).
Phase 3 Cluster Activations
Activate the clusters permitting clusters to exchange incidents with horizontal providers (UIMS and CCAS) and with CIT for dispatch to external service providers.
Phase 4 Legacy Retirement
Deactivation of the HP Bluestone Bridge and retirement of legacy bridges following closure of all outstanding incidents (new and old bridges are to run in parallel until this occurs).
CLIENTS REQUIREMENTS
Purpose
A Service Desk Consolidation (SDC) Integration Project Manager /Leader is required to ensure seamless conduct of activities of the Integration Development team through the three phases planned for this fiscal and integrate them with the initiatives planned for CIT (reporting solution, service categorization framework implementation, Utility Infrastructure Management Services horizontal service requirements).
The resource will also provide tactical planning and direction for the CIT Service Delivery Manager as it relates to the Integration Project primarily in the area of testing strategies, commissioning strategies and the establishment of the pre-Production environment and staging area with the CIT infrastructure. Previous investments and collateral developed in the Integration pilot will be leveraged.
Requirement
This RFS requires a Project Manager / Leader (role 1 level 2), for a maximum of 90 days effort with OLTP Integration knowledge and extensive ITSM process experience to extend a pilot ITSM solution into an enterprise solution. The resource will manage project deliverables to timelines and budget, own the project plan and schedule and provide a single point of contact to the SDC Project Team and Client / Partner Transition Project Sponsors. In addition this resource will act as a pseudo-Client for development and delivery of the CIT Reporting Solution, the implementation of the Service Categorization Framework for UIMS and management of the CIT infrastructure upgrades to be undertaken by iSERV.
Scope (please address each point with your experience below);
The scope of the work required to satisfy Phase 1 entails developing an enterprise integration hub to comply with requirements, some of which are outlined below.
Define and implement enterprise integration architecture, including collateral suitable for OPS Architecture Review (Contextual, Conceptual, Logical and Physical views of the architecture, based on Zachman EA framework)
Design hub-spoke architecture, with CIT as the core incident repository. CIT will serve future business intelligence by centralizing incident exchange data.
Align the enterprise integration architecture with OPS Support Model framework (Virtual Single Point of Contact) to enable key business communication requirements and allow for true end-to-end service management
Review the updated XML Schemas and make changes if necessary to include any additional data values to support Service Request incident exchange.
Implement incident management schemas and update as required to enable hub-spoke model.
The production architecture (and infrastructure) will initially be based on a single physical BizTalk server implementation for the hub, but a logical path for expanding to more servers will be required for both capacity and availability planning purposes (i.e. address business continuity plans at some future date).
Test the bridge orchestrations with Justice who manages an interim BizTalk environment to confirm logic is valid.
Plan deployment activities and architecture considerations where appropriate to allow for a partner to have more than one bridge orchestration running.
Define an architecture that allows for further process integration to occur (these additional processes are out of scope for this project phase). This could be separate orchestrations because previous orchestrations are not likely completely transferable. There may be some error handling aspects that should be kept separate and used across all processes regardless of the exchange type.
Document all architecture and operation procedures to ensure successful knowledge transfer to internal OPS staff.
SDC Integration Project Manager
The SCD Integration Project Manager is required to provide coordination of the Integration project team and to assess and provide input to the requirements for the planned RFI. Areas of focus will be:
the Reporting Solution;
the implementation of the Service Categorization Framework for the OPS within CIT;
the assessment and definition of the Service-based requirements for the tool driven by UIMS; and
direction of the iSERV resources charged with implementing updates to the iSERV CIT Solution blue print.
The work will be orchestrated and directed by the ITSM Project Director who will articulate the project vision setting the direction for the project, establish the project outcomes, and define the work package requirements for the team in collaboration with the ITSM Integration SME and the BizTalk Architect. Once underway the ITSM Project Director will attend weekly status reporting and respond to questions about direction / scope.
Deliverables:
The SDC Integration Project manager will develop and maintain the following deliverables:
?span style="font:7pt 'Times New Roman'">???? Develop a detailed project schedule highlighting major milestones and any external dependencies
Provide the Project Sponsor and SDC Service Owner with regular Status and Reports
Develop strategies/approaches as required to address project issues
Manage assigned team to complete scheduled tasks and deliverables
Align activities and work plans to other linked projects (i.e. UIMS
With time permitting the SDC Integration Project Manager will conduct other related assignments as required. These assignments may include: quality improvement initiatives and / or knowledge transfer to an incoming replacement resource.
Beyond Scope of Services and Deliverables - The following activities are not within the scope of this Statement of Work:
Out of Scope- Phase I Enterprise Integration:
?span style="font:7pt 'Times New Roman'">???? An ability to integrate a non-CIT user to an external service provider, and
?span style="font:7pt 'Times New Roman'">???? Support for other ITSM processes (Change, Service Level Management) from an integration perspective.
For those replying - we'll need your latest CV, 3 References, and your response(qualifications)?to the responsabilities for the "In-Scope"roles & activities.(with your name at the top!) and your consulting rate for an hourly fee-for-service contract.
Your help and time greatly appreciated.
Your call and referrals - welcome, always!
David R. Smith
Personally celebrating 20 years; Helping Corporate Leaders & Winners Continue to Succeed
>>> Specializing in Enterprise Project Management and E-PMO expertise <<<
????????????(LinkedIn; see who we know in common!), & connected by PLAXO (www.plaxo.com)
GSI International Consulting Group
"Your Project's Success is Our Measure of Achievement"?br>?/span>????Direct Line: (416) 777-2517?- Monday to Friday 7:30am- 7:30pm
?/span>????Mobile: (416) 768-2527 - call forwarded to this number when out of office.
o??? Main Tel:? (416) 777-2525 ext. 255
o??? Fax:?(416) 777-2547 (Attention Line)
?/font>55 University Avenue, Suite 1601, Toronto, Canada?M5J 2H7
dsmith@gsigroup.com? www.gsigroup.com
This message is intended only for the use of the intended recipients and it may be privileged and confidential.?更多精彩文章及讨论，请光临枫下论坛 rolia.net