UNDP/New York, NY (NEW YORK)
Lead Software Developer for Project Information Management System (PIMS 3)
Location : Home-based with three mission travels to Istanbul, Turkey
Application Deadline : 03-Apr-16 (Midnight New York, USA)
Time left : 3d 14h 32m
Type of Contract : Individual Contract
Post Level : International Consultant
Languages Required :
English
Starting Date :
(date when the selected candidate is expected to start) 20-May-2016
Duration of Initial Contract : 220 working days over 12 months
REFER A FRIEND APPLY NOW
Background
UNDP recognizes that the growing risks and impacts of climate change and the accompanying loss of ecosystem services requires the world to urgently invest in a new green development paradigm. Based in UNDP's Bureau for Policy and Programme Support, the UNDP-Global Environmental Finance Unit helps developing countries make green, low emission and climate resilient development not only possible, but also economically attractive. To achieve this, it works closely with UNDP country offices to help countries develop and implement programmes and projects which advance their capacity to put in place the right mix of regulatory and financial incentives, remove institutional and policy barriers, and create enabling environments that attract and drive private sector investment into green development.
The UNDP-GEF Unit assists partner countries to develop and implement programmes and projects that combine and sequence resources from a wide range of global environment and climate funds, financial mechanisms, and instruments including, but not limited to: the GEF managed family of vertical funds such as the GEF Trust Fund, the Special Climate Change Fund, and the Least Developed Countries Fund; the Adaptation Fund; and the Green Climate Fund.
Currently data and documents are stored and accessed through a variety of largely independent end-user and server based databases located both in Headquarters (New York) and five regional centres. These are not currently linked to the UNDP corporate applications.
Duties and Responsibilities
Objective:
The overall objective of this assignment is to finalize the development of the Project Information Management System (PIMS 3) including:
Establishment of clean, modular, open source platform built upon a modern Application Framework to allow fast and clean development;
Migration of all implemented and usable functionality onto that platform;
Completion of the remaining modules, feature requests, upgrades and changes on that platform;
Creation of new modules and functions as well as system maintenance;
Coordination of the workflow of all elements of system development, including the inputs of other software developers involved in the project, to deliver all outputs in a timely and efficient manner.
The Lead Software Developer will be expected to work with the UNDP Task Managers, other Software Developers, the PIMS administrator and others involved in the project to deliver the required outputs in an efficient and timely manner. The consultant will be responsible for all aspects of the delivery of the platform as well as for providing high-level management direction and coordination to the team. The consultant will also oversee both business and technical delivery aspects of the project, from establishing the foundation of the project through to the deployment of the solution.
Some components of PIMS3 are completed and functioning, while other components are developed but not yet implemented and others are still in the design phase. The current state of development and expected tasks that are required to finish PIMS3 are summarized in the sections below.
The consultant will report to the UNDP-GEF Results Management and Evaluation Advisor. Delivery of outputs will be overseen by the PIMS 3 Steering Group. The consultant will be expected to present regularly progress updates to the PIMS 3 Steering Group and obtain their clearance for strategic programming and project decisions.
Outputs:
Output 1: System Architecture & Environment Consolidation:
PIMS3 is large scale system with an underlying database model consisting of 305 relational tables (though approximately one third of them might be historical and not needed). 149 tables are already populated with user inputs that exceed 100 rows and there are more than 300 custom source files in the system. Current implementation needs to be improved to allow straightforward system maintenance and extensibility. The main goal of this output is the establishment of a clean, modular, open source platform built upon modern Application Framework to allow fast and efficient development. A Version Control System must also be implemented to allow easy source code change tracking, maintenance of development, as well as production environment and backups of source code.
PIMS 3 is built upon the following software and libraries: PHP version 5.6, MySQL Community Server GPL v. 5.6, jQuery, jQuery UI & ThemeRoller, Wijmo Open, jqGrid, phpExcel, phpWord. PIMS 3 is currently hosted by an external server provider. The software system is hosted on a Windows Enterprise 2008 Server and is managed using the Parallels Plesk Panel 10.4 software and Windows remote desk access.
As there is already a lot of functionality developed, it must be migrated to a new and improved modular, open source platform. It will be necessary to fully decipher the underlying database model, perform all the necessary database model consolidation, clean-ups, security upgrades, and migrate application business logic code. Some of the consolidation and migration work described here also falls under the related modules, mainly Milestones and Finance, described below.
Tasks:
After internal meetings with task manager in Istanbul, provide written overview of the key specifications of this output and refine timelines before commencing work (Proposed timeframe: by 30 May 2016).
Architecture framework developed and implemented, and related software development, security measures and migration completed and presented to UNDP-GEF (Proposed timeframe: by May 2016-May 2017).
Incorporate feedback and finalise upgrades (Proposed timeframe: May 2016-May 2017).
Deliverables:
Implementation of a well-designed, well-chosen Application Framework using a clean, modular, open source platform to allow for more efficient software development;
Migration of existing database model and all its well-designed parts (including project library, diary, collection of projects);
Migration and implementation of administration for all the necessary base entities (some of these may fall under outputs described below);
Installation of supportive tools Version Control Software (including possibly issue tracking software);
Moving existing source code under version control system, determination of which version would become a base (Pims3 or Pims3dev), removing of all duplicated old files;
Verification of basic mail server setup and functionality;
Develop uniform way of querying, filtering and modifying data;
Upgrade system security; incorporate automatic information security measures in application control framework;
Advise on implementation of an automated backup system to the current application server;
Comprehensive technical documentation to be maintained during the whole development cycle.
Timeframe: May 2016-May 2017 (noting that deliverables in other outputs related to the above may be required to be completed sooner).
Output 2: Milestones:
Milestones are steps or events in the project cycle that are activated, tracked and triggered within PIMS3. The milestone engine is a key component of PIMS 3 because it unites several other modules in the system.
There are more than 50 currently identified milestones in line with the UNDP-GEF project cycle and their steps are well-documented. Although the number of milestones is large, many of them might seem similar to each other from a software development point of view, thus it would be required to design a proper model to reflect all the real world requirements into extensible and flexible software components. It is also necessary to prepare a solid architecture that would allow easy further extension, modification and introduction of new milestones into the UNDP-GEF project lifecycle. Moreover, additional sources of funds might be implemented over time that would require specific (or modified) set of milestones.
In most cases, milestones are represented by a set of input fields of varying type (textual, single values referencing other related entities, dates and numerical inputs). They might be entered by different user roles, with different user access levels. Later they might be subject for review; some dates and numerical inputs would need to be reflected (e.g. financial analysis reports or reports aimed at project state monitoring). All changes to the data must be logged. Current implementation already allows a unified approach to data processing in some ways (e.g. there is project library which aggregates all project files that are uploaded into the system over time, however, there is problem with interconnection of individually developed parts into one consistent unit). Some milestones might also require processing of exported files from third party data sources, mainly in the form of bulk excel exports, as integration based on Web Services and remote API is not an option.
Milestones can have different pre-conditions and post-conditions (e.g. tracked project might not be able to proceed to the next milestone until previous milestone is not completed properly, or completion of certain milestone might trigger some actions – e.g. mail notifications, etc.). There may be up to ten different project cycles depending on the source of fund and project type. An example of a project lifecycle is illustrated as follows: Project idea – Idea confirmed for UNDP pipeline (entry to PIMS3) – Project document technically cleared by PTA - GEF CEO approval – Project document technically and financially cleared for DOA issuance – DOA signed – Project document signed – ASL issued – Project under implementation (monitoring, reporting, evaluation) – Project closure – Project impact.
Data entry requirements are linked to user and system generated steps and deadlines linked to the project cycle (called milestones) and UNDP-GEF business processes. Details of milestone requirements will be provided.
Tasks:
After internal meeting with task manager in Istanbul, provide written overview of the key specifications of this module and re-fine timeframe before commencing programming. (Proposed timeframe: by 30 May 2016);
Programme test version 1 for testing with UNDP-GEF (Proposed timeframe: by July 2016);
Revise and programme test version 2 for testing with UNDP-GEF staff (Proposed timeframe: by August 2016);
Incorporate feedback and finalize milestones, milestone data migration and milestone admin interface (Proposed timeframe: by September 2016).
Deliverables:
Finalize the milestones in the following project tabs: project library, project diary, milestones tab and registry with in-coming e-mails; streamline milestone steps to maximize efficiency and ease of data entry;
Finalize administrative management interface to allow for adjustments to functions and settings and to add/delete milestones as needed;
Migrate relevant data from existing database;
Undertake and verify test data imports and test all functions with key users;
Support test roll-out and make programming adjustments as necessary;
Support full roll-out.
Timeframe: May – September 2016.
Output 3: Finance:
Many tasks related to finance requirements have been already implemented. As they might be dependent on the new system architecture and milestone engine, which are yet to be developed, refining this part of the system would be required, particularly to maximize the efficiency of the related milestone steps. The most important data inputs for Finance part are currently two dialogues (budget and fees dialogue). There are currently two available financial reports based on entered data. As this functionality was not fully developed, its refactoring and completion would be required. Some additional improvements of the database model to reflect project structure would be required (e.g. modify how project components can be joined (grouped together) via Umbrellas, etc.).
The most pertinent activities in the financial module include:
Fee entry management;
Budget entries management;
Umbrella management;
Management of other related entities without more complex application logics (Sources of Funds, countries, Implementing Agencies);
Import of data from Atlas (UNDP ERP). This involves monthly upload of up to 6 Excel sheets (40,000; 40,000; 100,000; 150,000; 1000; 2000 rows);
Management of master fees;
Verification of master fees (performed during various milestones).
The tasks related to global system administration (e.g. Sources of Funds management, countries management, management of Implementing Agencies) are subject to change over time.
Tasks:
After internal meetings with task manager in Istanbul, provide written overview of the key specifications of this module and refine timelines before commencing programming (Proposed timeframe: by 30 May 2016);
Programme test version 1 for testing with UNDP-GEF staff (Proposed timeframe: by September 2016);
Revise, migrate data and prepare test version 2 for testing with UNDP-GEF staff (Proposed timeframe: by October 2016);
Incorporate feedback and finalise finance modules in PIMS 3 (Proposed timeframe: by November 2016).
Deliverables:
Ensure the relevant financial data entered by the user during the project cycle is displayed at the Finance tab;
Make final programming adjustments to the finance tab, finalize budget dialogue and fee dialogue at the finance tab;
Make final programming adjustments to the project delivery tab. This involves features to upload Excel sheets and display the data by Project, Country, Source of Fund, etc;
Make final programming adjustments to the CO fee allocation tab;
Make final programming adjustments to the trustee commitment tab;
Allow the user to link PIMS3 projects and components of projects (create umbrellas);
Import Finance Data from existing Excel database (5000 rows x 150 columns);
Finalize the merger of separate fee tracking system into PIMS 3 to manage, view and report on fees disbursed to Country Offices (Master Fee module);
Add finance reporting features;
Finalize administrative management interface to allow for adjustments to functions and settings;
Allow user management of other related entities (Sources of Funds, countries, Implementing Agencies;
Undertake and verify test data imports and test all functions with key users;
Support test roll-out and make programming adjustments as necessary;
Support full roll-out.
Timeframe: May – November 2016.
Output 4: Overall Coordination and Project Workflow Management:
The Lead Software Developer is expected to coordinate the workflow of all elements of system development, including the inputs of other software developers involved in the project, to deliver all outputs in a timely and efficient manner. Coordination functions will also include:
Lead and implement a project management methodology, document and manage workflow procedures and responsibilities at each stage, including testing and roll-out;
Coordinate search, reporting and dashboard and other system elements developed by other programmers;
Improve format, function and design of the system (update system components and features relating to format, functionality, design and overall user experience);
Develop procedures for standard system back-ups;
Coordinate with PIMS administrator on application server administration, advise PIMS Administrator on updating reference data functions, maintenance for importing and harmonizing Finance tables and developing new import processes;
Present monthly (or as needed) progress updates to the PIMS3 Steering Group and obtain their clearance for strategic PIMS 3 programming decisions.
For each request, the selected consultant will:
Confirm receipt of the notification of the maintenance or assistance problem sent from the UNDP-GEF Directorate;
Within 24 hours, respond to the UNDP-GEF Directorate with the following: Initial estimate of the scope of the issue and initial estimate of the time it will take to solve the issue;
Resolve the issue;
Once resolved, provide the UNDP-GEF Directorate with the following: Final report on the scope of the issue or problem and what action, if any, will be undertaken to avoid a repetition, and final report on the time taken to solve the issue or problem.
Timeframe: Duration of contract.
Payment terms:
Output One: System Architecture & Environment Consolidation, May 2016-May 2017– 10%;
Output Two: Milestones, May-September 2016 – 35%;
Output Three: Finance, May-November 2016 – 35%;
Output Four: Overall Coordination and Project Workflow Management, May 2016-May 2017 – 20%
Key performance indicators:
Successful and timely delivery of each output as per timeframe listed above.
Working arrangements:
The consultant will work from home with three mission travels to Istanbul;
Estimated level of effort: Up to 220 days;
The consultant will report minimum weekly to the Task Manager and the RBM and Evaluation Advisor;
The Consultant will be given access to information necessary for execution of the tasks;
The Consultant will provide her/his own working station (e.g. laptop, internet, phone, printer,) and must have access to a reliable Internet connection;
The consultant is required to have all of the equipment, software packages and necessary licenses to execute this assignment;
Irrespective of his/her location, the consultant is expected to be available for consultations and be in reliable email contact between 10:00AM - 6:00PM (UTC+2:00) Eastern European Time zone (Istanbul);
Payments will be made upon submission of a certification of payment form, and acceptance and confirmation by the RBM and Evaluation Advisor on satisfactory delivery of services and outputs.
Travel:
Up to three missions of five days each to Istanbul may be required during the duration of the contract;
Any necessary missions must be approved in advance and in writing by the RBM and Evaluation Advisor;
The Advanced and Basic Security in the Field II courses must be successfully completed prior to commencement of travel;
Consultants are responsible for obtaining any visas needed in connection with travel with the necessary support from UNDP;
Individual Consultants are responsible for ensuring they have vaccinations/inoculations when travelling to certain countries, as designated by the UN Medical Director;
The Consultant is required to comply with the UN security directives set forth under https://dss.un.org/dssweb/.
The consultant will be responsible for making his/her own mission travel arrangement in line with UNDP travel policies;
All related travel expenses will be reimbursed as per UNDP rules and regulations for consultants. Costs for airfares, terminal expenses, and living allowances should not be included in financial proposal.
Competencies
Corporate Competencies:
Demonstrates integrity by modelling the UN's values and ethical standards;
Promotes the vision, mission, and strategic goals of UNDP;
Displays cultural, gender, religion, race, nationality and age sensitivity and adaptability;
Treats all people fairly without favoritism.
Functional Competencies:
Job Knowledge/Technical Expertise:
Understands and applies fundamental concepts and principles of a professional discipline or technical speciality relating to the position;
Strives to keep job knowledge up-to-date through self-directed study and other means of learning;
Solid understanding of the web development process, including the concepts of user experience, user interface design principles and conceptual design;
Eye for design and attention to detail;
Experience in project management with a track record of delivering at or ahead of deadlines.
Client Orientation and Professionalism:
Researches potential solutions to internal and external client needs and reports back in a timely manner;
Organizes and prioritizes work schedules to meet client needs and deadlines;
Anticipates client needs and addresses them promptly;
Generates new ideas and approaches.
Required Skills and Experience
Education:
Certificate in computer sciences, web resources development, web design, programming or other closely related field (max 3 points);
Bachelor's degree in computer sciences, web resources development, web design, programming or other closely related field is an advantage (max. 2 points).
Experience:
More than 5 years of experience in software architecture design and implementation of robust Web 2.0 information systems (projects of large scale - database model larger than 200 relational entities, more than 200 domain dependent classes, more than 5 different user roles) (max. 3 points);
Experience with real time high availability systems and business critical systems strongly desired (max. 2 points);
Excellent knowledge of design and implementation on relational database level - excellent knowledge of SQL (stored procedures, triggers, data integrity and consistency, transactional safe data manipulation) (max. 3 points);
Experience with integration of autonomous information systems (REST / SOAP web services, integration based on manual import of batch files) (max. 2 points);
Rich experiences with any robust modern Web 2.0 PHP Application Framework (e.g. Yii2, Symphony2, Laravel, Zend2 etc.) (max. 3 points);
Experience with other relevant libraries and web technologies, such as HTML5, CSS3, jQuery, PHPOffice, experience with latest trends in Dependency Injection (max. 3 points);
Experience with mail processing (both sending of mails via SMTP as well as processing of mail inbox) (max. 3 points);
Experience with modern software development supportive tools such as distributed Version Control Systems – e.g. Git, or MercurialHg (max. 3 points);
Experience with test driven development and automated source code testing frameworks are desirable. (max. 3 points).
Language Requirements:
Excellent oral and written communication skills in English language (max.5 points).
Evaluation Method:
Only those applications which are responsive and compliant will be considered and evaluated;
Offers will be evaluated based on Combined Scoring method where the technical criteria will be weighted at 70% and the financial offer will be weighted at 30%;
The technical criteria (education, experience, language [max. 35 points], proposed methodology [max. 35 points], and interview [max. 30]) will be based on maximum 100 points;
Only the top 5 candidates scoring 49 points or higher from the review of education, experience, language and proposed methodology will be considered for interview;
Applicants obtaining 70% of the combined total technical points (education, experience, languages, methodology and interview) will be deemed technically qualified and considered for financial evaluation;
Financial score (max 100 points) shall be computed as a ratio of the proposal being evaluated and the lowest priced proposal of those technically qualified;
The financial proposal shall specify an all-inclusive lump sum fee. In order to assist the requesting unit in the comparison of financial proposals, the financial proposal must additionally include a breakdown of this fee (including all foreseeable expenses to carry out the assignment). All costs for mission travel (round trip economy fare tickets, terminals, etc.) should not be included in financial proposal.;
Applicant receiving the Highest Combined Score and has accepted UNDP's General Terms and Conditions will be awarded the contract.
Documentation to be submitted:
Applicants must submit a duly completed and signed UNDP Personal History form (P11) to be downloaded from the below link;
Explanation why the applicant considers himself/herself the most suitable for the assignment;
Proposed methodology how the applicant will approach and complete the assignment with responses to the following questions: What project management methodology would you propose for this project? Please describe why it is the most suitable approach and briefly outline your experience with the methodology (max 2 pages); and PIMS 3 requires a new, clean, modular, open source platform built upon a modern application framework to allow fast and efficient development. Briefly describe what application framework you would move PIMS 3 to and the reasons this framework is the most suitable (max 3 pages);
Applicants must reply to the mandatory questions asked by the system when submitting the application.
Kindly note you can upload only one document to this application (scan all documents in one single PDF file to attach).
UNDP Personal History form (P11) required of all applicants:
http://www.undp.org/...1_Personal_history_form.doc.
General Conditions of Contract for the ICs:
http://www.undp.org/...%20General%20Conditions.pdf.
UNDP is committed to achieving workforce diversity in terms of gender, nationality and culture. Individuals from minority groups, indigenous groups and persons with disabilities are equally encouraged to apply. All applications will be treated with the strictest confidence.
All candidates should apply at:
https://jobs.undp.org/..._job.cfm?cur_job_id=64924
Apply To Job