220 likes | 443 Views
USRP MiMOSA Users Workshop Amman, Jordan 25-28 January 2010. Introduction to MAU. ITSC Strategy & Structure MAU Overview & Structure MAU Project Portfolio MAU 2009 Year in Review MAU 2010 Goals Project Schedule. ITSC Strategy.
E N D
Introduction to MAU • ITSC Strategy & Structure • MAU Overview & Structure • MAU Project Portfolio • MAU 2009 Year in Review • MAU 2010 Goals • Project Schedule
ITSC Strategy • Internal prioritization and process improvement along with business units • Support to the large IT based components within projects implemented for IOM’s donors • Explore opportunities to interface with systems of major external stakeholders wherein data exchange forms an important key to efficient service delivery • IT management to play a direct role in leading change initiatives to support, enable and drive the technology challenges faced by the organization.
ITSC Goals & Objectives 2009-2012 • Continue to deliver IT services that enables effectiveness of IOM operations • Implement IT based process improvements • Enhance the efficient use of ERP and other corporate applications • Align business and IT strategies and plans to establish priority areas • Enhance systems to support the processing of Migrant services • Promote the use of Information/Intelligence for planning and decision making
Migrant Applications Unit (MAU) • MAU is responsible for the design, development, and implementation of global data base systems to facilitate IOM Headquarters and Field Missions to process, deliver, and monitor activities and services provided to migrants. • In conjunction with ITC Helpdesk, MAU also has a dedicated support team that works in two shifts providing coverage from 9am – 11pm (PST) Monday to Friday.
Goals of Migrant Applications Unit • Streamline & integrate delivery of multiple IOM Services to migrants • Maximize efficiency & draw upon IOM operational expertise • Design & develop common features for Headquarters, Field Missions, & Donors • Establish framework for Governance to guide future development that meet IOM needs
General Functions • Document functional requirements and translate them into technical solutions that support activities & services provided to migrants • Extensive testing prior to production release • Maintenance and support of global applications • Issue tracking to improve performance & meet the needs of IOM stakeholders, users, and donors
Information Flow Overview Operational services with financial impact: transportation HR Migrant Activities: Med, CO, AVR, Training, Movement Finance Migrant Registration Procurement / Assets PRISM MiMOSA iGATOR Organizational Data Warehouse Partner Agencies, Donors, External Stakeholders PRM : WRAPs UNHCR : Project Profile CDC UNJSPF, ICSC • EC, Donor Reporting 10
MAU Project Portfolio • CDC Interface • CDR MFTS • Confluence • iGATOR • LTI/LTS • MAU Projects Helpdesk T1, T2, T3 Support • MiMOSA • RMI • SIMA • SQL Reporting Services • UKTB • WRAPS Interface
Goal #1 MiMOSA Web Ver. 1.0 • To complete the design, development, User Acceptance Test, pilot release and roll out plan for the technical upgrade of MiMOSA to a web platform with: • defined Project Structure of Stakeholders & Business Process Experts • minimal down time for application users, data consumers, and external interface partners, • optimization of data base, • improvement in the user interface, • increased data validation between and across modules, • off line replication mode for missions with poor infrastructure
Goal #2 Customer Relations • To improve customer relations with the user community through timely • Information sharing on MAU project statuses • Notification of the status of bug reports and change requests • Updating the MiMOSA Web Site to be a source of information relevant to the user community and stakeholders
Goal #3 Quality Assurance • To ensure MAU projects are delivered with high-quality in accordance with industry standard and best practices • Identify resources required to test and control the quality of our applications • Identify standard Functional & Non-Functional testing requirements for production releases • Fill the position for a Quality Assurance Team Leader • Identify and apply standard QA Process • Introduce QA Tools to QA team like load runners for performance and web load testing
Goal #4 Automation of Processes • To work closely with the business community to continue to automate manual processes for operations • Automate US PoE embarkation schedule based on date of arrival and departure to final destination • WRAPS Interface Phase 2 for eDEP and eCOA to minimize OPE/RPC manual data entry • IOM/CDC Interface Phase III ePDMS & eSMC forms • WRAPS Interface Phase 2.5 for MIF in XML format to import photos & cross-reference cases to minimize duplicate data entry and provide common data set for USRP Med & Ops
New Project Initiatives • MHD Lab Data Base - TBD • MAU Web Site - In progress • MiMOSA User Training Curriculum - TBD • CDR Data Archiving & Clean Up - TBD • MAU Footprints Phase II - In progress
Collaboration to Succeed SOP/ Compliance Technology Quality Assurance