Technical Proposal Defense

1. 1

2. 2
Overview of C-Net Infotech
19+
years
Operating since 1998
125+
e-Gov projects delivered
55,000+
Trained officials
300+
Pan India team of FTEs
Certifications :
 CMMi – (Maturity Level 5)
 ISO 9001 : 2015
 ISO 27001 : 2013
 ISO 2000 : 2011
GLOBAL
TECHNOLOGY
OFFICE
Migration &
Modernization
Centers of Excellence
Open Source
M& I/ EAI
Microsoft
Java
Data
Architecture
Performance Security
Architecture
Portals & Content
Mgmt
Usability
RFID

3. 5
C-Net’s Service Portfolio
 Digital Transformation
 All Channel Experience
 Big Data & Analytics
 Corporate & Digital Operations
 CIO Advisory Services
 Governance & Digital
Organization
 Executive Leadership &
Change
CONSULTING SERVICES
 Application Consulting
 Package Based Application
Services
 Application Development &
Integration / Custom Software
Development (CSD)
 Next generation AM services
 Application Lifecycle Services
(AD&M)
 Mobile Solutions
 Enterprise Cloud Services
 XaaS and Internet of Things
Software Quality Management &
Testing
 Business Information
Management
 Big Data & Analytics
 Business Process Management
 Partner solutions
APPLICATION
SERVICES
INFRASTRUCTURE
SERVICES
 Infrastructure Transformation
Services (ITS)
 Platform Delivery Services (PDS)
 Multi-Sourced Services Integration
(SI / SIAM)
 Service Management
 Cloud Management Unit (CMU) –
Platform & Brokering
 SkySight
 ITO User Run Services (e.g.,
Workplace)
 ITO Data Run Services
 Backbone Services (Network &
Data Center)
 Security Services
BUSINESS PROCESS
OUTSORCING
 Finance and Accounting
 Supply Chain Management
 Business Analytics
 Demand Driven Insight – CPRD
 SMARTCare – Utilities
 Participations – Media &
Entertainment
 ECM – Manufacturing
 Claims Processing – Insurance
PROFESSIONAL
SERVICES
 Application Services
 Product Engineering Services
 Infrastructure Transformation /
Cloud
 Testing & Quality Assurance
 Cyber-security
 Mobile solutions
 Business Intelligence & Analytics

4. 6
C-Net’s Product Portfolio
e-KEM
[ Educational
Knowledge Enterprise
Management System]
Vehicle Tracking
Management Solution
[VTMS]
Construction
Management Solution
(CETI)
Employee Work and
Performance
Management
[EWPM ]
Mobi RMA
[ Resource
Management
Application ]
Document
Management System
[DMS]
Inventory
Management System
Bid Management
System
Warehouse
Management System

5. 8
Key Government Clients
01 RajCOMP Info Services Limited (RISL), Jaipur (Rajasthan)
02
Rural Electrification Corporation Limited, New Delhi
03
04
Madhya Pradesh State Electronics Development Corporation Ltd.,
State IT Centre, Bhopal
Department of Urban Development, UT Administration of Daman and Diu &
Dadra and Nagar Haveli
05
06
Department of Information Technology & Communication,
Government of Rajasthan
Urban Administration and Development Department (UADD),
GoMP, Bhopal (MP)
07 Indira Gandhi National Centre for the Arts, New Delhi

6. 9
Key Government Clients
08 National Informatics Centre, New Delhi
09
National Highways Authority of India, New Delhi.
10
11
Jabalpur Municipal Corporation
M. P. Text Book Corporation, Pustak Bhawan, Bhopal
12
13
Centre for Research and Industrial Staff Performance, Bhopal
Guwahati Municipal Corporation
14 Bhopal Municipal Corporation, Bhopal

7. 10
Key Government Clients
15 Directorate of Estates, Bhopal. Govt. of MP
16
Madhya Pradesh Housing Board, Bhopal
17
18
M.P. State Livestock & Poultry Development, Bhopal (MP)
NHDC Limited, Indira Sagar Power Station, Khandwa (MP)
19
20
Building Materials & Technology Promotion Council, Ministry of
Housing & Urban Poverty Alleviation, Govt. of India, New Delhi
MP Khadi & Village Industries Board, Bhopal
21 Municipal Council Pandhurna, District-Chhindwara (MP)

8. 11
Key Government Clients
22 M.P. State Civil Supplies Corporation Limited, Bhopal
23
Reserve Bank of India, Bhopal
24
25
Bharat Heavy Electricals Limited (BHEL) Bhopal
Indian Naval Ship Maintenance Authority
26 Department of Registration, Excise and Prohibition, Government of Bihar
27
Dharamshala Municipal Corporation
I
28 Industrial Development Corporation, Odisha

9. 12
Awards & Recognition

10. 14
Similar Experience
SR. PROJECT ‘S
1 Development, Customization, Integration and Implementation of End to End ERP Solution at IDCO, Bhubaneshwar
2 Implementation of e-Nagarpalika (Online ULB services Under Public Service Guarantee Act) for Dharamshala Municipal
Corporation Himachal Pradesh.
3 Computerization of Madhya Pradesh Text Book Corporation
4 Development, implementation & maintenance of web based software solutions for Guwahati Municipal Corporation.
5 Design, Development ,Implementation and Maintenance of Integrated Raj e-panchayat application for Government of Rajasthan
6 Computerization of Madhya Pradesh Housing Board
7 Support for Implementation & Maintenance of Web based Management Information System for Jabalpur Municipal Corporation
8 Design ,Development and Implementation of Web Based Urban Sector Management Information System (USMIS) for Urban
Administration and Development Department (UADD) of the Government of Madhya Pradesh
9 Design, Development and Implementation of a fully integrated online Automated Building Plan Approval System (ABPAS) for
Municipal Corporations (MCs) under Urban Administration and Development Department (UADD) of the Government of Madhya
Pradesh
10 Design, development and implementation etc. of online monitoring etc. for Directorate of Estates

11. Domain Experience in Education Sector

12. Domain Experience in Education Sector

13. 17
Understanding of Project

14. 18
Understanding Project Scope
CNET understands that there is an existing PMS system in use currently by EDCIL with almost 80% same functionalities listed in the tender. Both PMSS & Academic MIS
together makes a core PMS system currently used at EDCIL. The main challenges faced in current system are due to its rigidness when it comes to enhancing the current
system. It takes lots of time duration, effort and cost to do even simplest of changes such as adding a new field on existing screens.
Main Objectives of PMSS are:
• Provide full visibility into procurement processes, enhance compliance & reporting and streamline
the administrative process.
• Reduce variance in procurement processing at each step and ensure adherence to World Bank
guidelines by following below norms
• By capturing end-to-end procurement process flow to standardize the procurement
• Provide information on specifications of items, maintain database of manufacturers/ suppliers.
• Generate advertisement details, Standard Bidding Documents (SBDs), Bid Evaluation Report
(BER), Purchase Order (PO), payment details etc.
• Provide contract management functions like identifying contract milestones (warranty period,
performance guarantee, delivery schedule etc.), review supplier performance etc.
• Meet MIS requirements for documentation/ report generation requirements of all the users
Plan Approve Procure GRN Payment
Desired PMSS Flow
Procurements Methods
1. Shopping- goods
2. Shopping –Works
3. Direct Contracting
4. National Competitive Bidding-NCB
5. International Competitive Bidding-ICB
6. Limited Competitive Bidding-LIB
7. Quality and Cost Based Selection (QCBS)
8. Fixed Budget Selection (FBS)
9. Least Cost method (LCS)
10. Consultant Qualification Based Selection (CQS)
11. Single Source Selection

15. 19
Development Modules in Scope
Main Objectives of Academic MIS are:
• Provide a web-based management information system to NPIU to track, monitor and evaluate the academic performance in the Project.
• It shall track implementation of key project inputs, outputs, outcomes, and impact corresponding to the project activities through various performance indicators
developed for the project.
• It shall generate MIS reports depicting the specified data in qualitative and quantitative forms. Generate comparative analysis report with respect to baseline data.
• Through web-based MIS a large amount of information on academic processes, practices and project implementation can be collected easily from each institution for
effective monitoring of the project implementation.
BI Analytics and Reporting
The dashboards are required for the three entities of PMSS which are Institutes, SPFU, NPIU for monitoring and review purpose. Dashboards should cover all the major
activities within the PMSS as it may be defined by the user department during the development of the application.
Other Requirements:
1. Both PMSS and Academic MIS to be accessible thru SSO (Single Sign on) logins.
2. data available in current system has to be migrated to new system
3. Hierarchical and role based access control
4. A module to raise a request and provide the feedback should be a part of the PMSS application
5. Respective entities should be able to configure the respective details in PMSS. It should include the user management as well

16. 20
Warranty and Operations & Maintenance (To be crisped)
CNET will provide Free of Cost 1 year warranty of the application to ensure
that software is running smoothly during this period. CNET will be responsible
for following activities during this period
 A comprehensive warranty applicable on PMS for a period of 12 months
from the date of Go-Live.
 To make sure that the developed PMS system is in full conformity with the
specifications and operating properly and safely. All recent design
improvements in system shall be made available.
 CNET further warrants / provides warranty under this Contract shall be
free from all encumbrances and defects/faults arising from design,
material, manufacture or workmanship.
 CNET will provide maintenance support to address, but not limited to, all
user queries, bug fixes, enhancements, incorporation of new requirements
owing to legal, statutory and policy changes, configuration changes,
customizations, patch updates, database administration, security, periodic
user trainings
Below are the major activities to be performed by CNET during the Operation &
Maintenance Phase:
Issue Resolution/Troubleshooting/Technical Support to Users:
 Playing the role of Single Point of Contact for all system issues & bugs reported by
users.
 Provide continuous, consistent support work 8*6 and the team will be available for full
work day from Monday to Saturday and accessible on Sundays and holidays for any
coordination
 Coordinate and resolve all issues immediately.
 Ensuring low system downtime and communication with all users.
Development Support during O&M:
 Managing & supervising all further enhancements, minor modifications being made to
the system, including integration etc.
 Contribute in design and structural changes during enhancements along with effective
coordination with all stakeholders to ensure smooth implementation.
 Performing timely UAT & system audits, communicating and addressing issues & bugs
with developers.
 Support in user training, documentation, user manual creation etc.

17. 21
Approach & Methodology

18. 22
TOGAF Architecture Development Method (Vikas to compress in to 1 slide)
For the successful execution of PMS, CNET proposes a blend of strong architectural as well as design principles, which are highlighted specifically for EDCIL-PMS
requirements. Further, CNET proposes a strong and robust Logical, Solution, and Technical architecture, which are detailed out in the following sections.
Key Architecture Principles
Proposed solution architecture for both the applications is based on the following
methodology in conformance with TOGAF Architecture Development Method.
• Identify system context and role-players (both human and systems/applications)
who will be interacting with the system.
• Develop functional architecture and identify key system building blocks based
on the Functional and Non-Functional Requirements of the system. Identify
major application modules, functional components and common components
• Develop logical architecture outlining the major interactions across different
functions/ applications within as well as external systems.
• Define high level solution implementation (in other words, technical
architecture) with major technology components
• Describe solution implementation of the major applications/solution building
blocks realizing through architecturally significant usage scenarios
Adherence to Layered Architecture Principles
Separation of concerns – Break the application into distinct features
that have minimum overlap in functionality.
Single Responsibility Principle – Each component or a module
should be responsible for only a specific feature or functionality. The
demarcation is done clearly be depicting each module as individual
components governed by the controller layer and a boundary layer
by means of SOA framework which acts like a facade.
Principle of least knowledge – A component or an object should not
know about internal details of other components or objects. Every
component will be having internal binding which is cohesion and
there will be too less bondage among different components which
eliminates coupling.
Don’t Repeat Yourself (DRY) – There should be only one component
providing a specific functionality.

19. 23
TOGAF Architecture Development Method (Vikas to compress in to 1
slide)
Focus on Non-Functional Requirements
Performance
The following design considerations will be applied to meet the
performance requirements laid out in the RFP:
 Proper capacity planning
 Minimize server round trips
 Pool shared resources
 Process independent tasks concurrently
Scalability and Availability
 Application Server - Application will be deployed in a load balancing
and clustered environment to support scalability and to ensure
maximum availability within data center. Different Virtual machines will
be created and aggregated for striation of requests to the application
server by means of proper VMs.
 Database Server –Database Clustering will be used for high availability.
 BCP –The hosting solution proposed has provision for setting up a
disaster recovery environment to support business continuity.
Extensibility
Layered architecture ensures that, for future requirement additions,
changes in one layer will have no or least changes in other layers. The
architecture envisaged for this is meant for extensibility as much as
possible, as it is following Lean SOA principles
System Integration
 Message Content Validation
 Design for Reusability
 Self-documenting Services
 Support for Multiple Versions of Services
 Cross Cutting Concerns
 Filtering of Sensitive Information
Security
 Vulnerability Assessment – Threat modelling will be applied at design
time to ensure that top 10 OWASP security vulnerabilities are
assessed
 Compliance – Security testing tools will be used to detect and
address security vulnerabilities
 Data Security – Transport level data security will be addressed using
SSL and SFTP
 Data Integrity –PKI will be implemented to meet the customer
compliance requirements

20. 24
TOGAF Architecture Development Method (Vikas to compress in to 1
slide)
Architecture
The architecture is visualized in a modular fashion where the separation of concerns is given top priority and the binding between modules
designed in a cohesive way. It follows LEAN SOA architecture where the entity, controller and boundary are clearly depicted.
Authentication & Authorization:
The authentication layer that is designed here is used only by a
presentation layer on the same tier within a trusted boundary. It is not
exposed to business layer at all. The authorization layer is built in such a
way that the authorization code and business processing code for the same
component are not mixed at all. Here we will be using LDAP based
authentication and authorization.
Presentation Logic Components:
Presentation Logic here is the application code that defines the logical
behavior and structure of the application in a way that is independent of
any specific user interfacing implementation. When implementing the
separated presentation pattern, the presentation logic components will
include presenter, presentation model and view model components. It will
also include components that encapsulate the data from the business layer
which can be easily consumable.
Application Components (Business, Services and
Integration Components):
This layer implements the core functionality of the system and encapsulates the
relevant business logic of application. It consists of components some of which
may expose service interfaces that other caller can use. They store data values
and expose them through properties which contain business data used by the
application.
Data Components:
The data components here expose generic interfaces that the components in
business layer can consume. There are two kinds of data that is possible here
– Transactional data and analytical data. The centralization of common data
access takes place here which makes the application to configure and
maintain. Here an object relational mapping framework like Hibernate is
being used to implement data access components automatically, reducing
amount of data access code that a developer must write

21. 25
Solution Architecture
The high-level solution architecture
and its components from logical,
physical, data and interoperability
viewpoints are –
 Authentication Layer ( LDAP )
 Presentation Layer (Java with Spring)
 Integration ( API / Web Services)
 Application DB (Maria DB)
 MIS/BI (Maria DB)

22. 26
Technology Stack Mapping
CNET is proposing below technology stack which is totally open source based stack, adhering the GOI guidelines from GOI:

23. 27
IT Infrastructure Suggestions for EDCIL

24. 28
Deployment Architecture

25. 29
Software Development Approach

26. Configuration Tables - + 10% - 20% Additional Fields
Transactional –
Header Tables - +
10% – 20% Extra
Fields
Transactional – Line
Item Tables + 10% -
20% Additional
Fields
Multi Purpose – Audit
Trail Tables
Reporting Tables – For
Faster Timings and Quick
Development of New
Reports
User Interface Screens – Flexible Tab Based Design to Accommodate
Additional Fields w/o disturbing the Existing Layouts
Source Code
Objects
– OOPS Concept
– Dedicated Place
Holder for
Additional Code to
Accommodate
Fields Added to
Minimize
Enhancement Roll
Out Duration
API’s
Application High Level Architectural for easy customizations

27. 31
Backup & Restoration Approach --- ????? To be kept Y/N
CNET backup and recovery strategy and approach focus on to eliminate customer backup window, accelerate system recovery and efficient disaster
recovery. Including the older disk and tape based backup strategy, we have adopted and built an efficient and strong snapshot and image based backup
recovery approach for faster backup and restoration. It helps:
Based on customer solution and requirement, some of the best backup
and recovery approach we choose are as below to help customer to meet
RTO and RPO requirements:
 Snapshot and Image Level Backup
 Replication
 Source Side De-duplication
 Full Backup
 Incremental Backup
 Incremental Forever Backup
 Differential Backup
 CDP (Continuous Data Protection)
Some of our high-level considerations to choose a best approach for backup
and recovery from all existing strategies are:
 Understand policies regarding storing and moving backup tapes offsite.
Incremental backups are a bad idea in that case
 Understand Service level agreements in regard to RTO and RPO
 Understand different types of backup supported by backup application
 Understand replication strategy and available bandwidth
 Understand all available backup infrastructures
 Differentiate applications in three categories - High Critical, Medium Critical and
Low Critical

28. 32
Testing – Process (To be chkd with the Tech Bid)

29. 33
Testing Approach
CNET assures to EDCIL-PMS through its “Total Quality” solution which is built on Industry standard test process in accordance with TMMi framework. In this
engagement, our approach would be derived from the solution where the focus based on the designing of test cases to cover 100 % functionality and uncovering
critical defects during the test execution.
Our Approach mechanism consists of the following
 Test Planning Approach
 Assessment
 Test Design
 Test execution and Defect Management
 Test Reporting
We follow stringent SIT execution process and the defects that are
identified may also trace back to the requirements and triggers change
requires. This could be a continuous process during the SIT life cycle
that starts with analysing/ Understanding of end to end HTMS.
Integration Testing also covers the Usability Testing, Configuration
Testing, Documentation Testing and Procedure Testing

30. 34
Proposed Team Structure

31. 35
1 2 3 4 5 6 7 8 9 10 11 12 N Total
Project Manager 1 1 1 1 1 5
Solution Architect 1 1 1 1 1 5
Busines Analyst 1 1 0.5 0.5 3
UI Designer 1 1 1 3
Senior Developer Java 1 1 1 1 1 5
Developer Java 2 2 2 2 2 10
Senior Developer Angular JS 1 1 1 1 1 5
Developer Angular JS 1 1 1 1 1 5
BI developer 2 2 2 2 2 10
Tester 2 2 2 2 8
Database Administrator 1 1 1 1 1 5
Training & Change Management
Expert
2 2 2 2 8
Warranty 24 24
O&M Support 0 36 36
Total 12 16 16 15 14 0 0 0 0 0 0 0 0 72
Total - Warranty &
O&M - = No*12 =
Months
Name of Staff Staff input in the form of BAR CHART Total staff
month
Year 1 = Y1 =
No*12 =
Months
Y1+18
Months - =
No*18 =
Months
Resource Deployment Sheet

32. 36
Overall Compliance Scope
Scope Component Description Compliance
PMS Project Management System Yes
PMSS Procurement Management Support System Yes
Academic MIS
MIS concerning Institutions related to the improvement in Quality of their education,
Project Status reports etc Yes
Integration API’s for PFMS Yes
Training and Change
Management Training and Change Management for PMS and Academic MIS Yes
2 Years Operation and
Maintenance post one
year Warranty
2 Years Operation and Maintenance post one year Warranty as per SLA described in
Tender Yes

33. 37
Program Delivery

34. 38
Colloborative Development Methodology

35. 42
Change Management Process

36. 43
Training & Capacity Building

37. 44
Approach - Training & Capacity Building
Consider the goals of your organization In order to conduct effective training Sessions, CNET will keep in mind the
objectives
mission and vision statement of EDCIL-PMS
department Identify the benefits for trainees
Outline the skills, information, and certifications that participants will gain
by undergoing the training
Recognize desired outcomes. Include specific outcomes EDCIL-PMS wanted the training to achieve. These
should be more
specific than the overall goals of the training
Outline the training structure Include methods CNET will use in training
Establish a time frame Establish a timeline for making all preparations
Training on Technical Aspects of Application
“Train-the-Trainer” Approach for EDCIL
Capacity Building
18+Years, 125+ e-Governance projects , 55,000 trained officials.

38. 45
Training & Capacity Building
Modes of Training:
 Class Room Based
 Online – Help – O&M
 Computer based Training
Training Materials:
o Instructor Guide
o Quick Reference Guide (QRG)
o Facilitator Slides
o Cheat Sheets / Ready reckoner /
Delta Updates
Training Duration and Batch Size:
As agreed between Client and C-Net
Target Audience:
o Application End Users
o Technical Personals
o Core Users
o Admin Users

39. Training Material Development Approach
Study Existing Material
Conduct Survey on
Existing Training
Material
Short Listing the
improvement Points
Design New Template
Develop Training Material
Conduct Trainings
Approval
from EDCIL
Approval from
EDCIL
Y
Y
N
N Continuous
Improvement

40. Knowledge Management System
Meta Data
Data Management
Meta Data Management
Structured
Data
Unstructured
Data
Knowledge
Capture
Create
Manage
Access
Review
Publish
Distribute
Store
Security
Users

41. 48
Training & Capacity Building- Lead Profile
• Over 8 year time span, successfully managed 10+ IT related programs for the Govt Projects.
• Possess extensive knowledge of course development, instructional design and recourse coordination
• Expertise in developing web-based instructional materials and teaching aids
• Proficient in delivering effective classroom training sessions
• Highly skilled in creating user guides and troubleshooting technical manuals
• Possess excellent presentation and teaching skills
• Ability to develop and lead technical training program sessions
• Ability to generate technical concepts in a clear and precise manner
• Extensive knowledge of operating systems like Microsoft Office XP/2007/ NT/ Vista and Linux
• Familiar with Applications like MS Project, Abode, MS Office Suite, Photoshop, Illustrator and MS Live
• Meeting
• Knowledge of programming languages like C++, C, UNIX, HTML and XML
• In-depth knowledge of database concepts namely MYSQL, Sybase, MS Access, Oracle and SQL Server
• Familiar with hardware tools like servers, printers, VoIP, networking and telecommunications devices
• Strong Ability to drive HR processes and to deliver high quality HR services in a fast paced, high change environment
• Function as a strategic partner by linking all the HR strategies with business strategy.
• Human Resource activities which include, Employee Care, Career Path for employees, Policies and
• processes, statutory compliance and Data Management.
• Responsible for handling the employee Grievances, R&R activities, Attrition management, RCA,
• Training and development, Administration, Manpower Management, Personnel Management, Team Management, Strategic HRM & Statutory Compliance.

42. 49
Timeline

43. 50
Timeline
Sr. Milestone
Deliverable
(Reports/ Documents & Deliverables)
Timeline
(in weeks)
1
Execution of Agreement &
Kick-off
• Agreement
• Project Plan
• Team allocation
T1
2
SRS Preparation and submission for
Approval
• Submission of SRS with approval.
• Submission of FRS with approval.
• Submission of Solution Architecture.
• System Design Document (SDD)
T1+8
3 Approval of SRS by the authority Approved copy of SRS T2=T1+9
4
Design, development of Application
software and Mobile app
• LLD & HLD
•Testing Methodology including test cases, test
plan and Test Results
T2+20
5 Application Audit and Testing • Security testing report. T2+24

44. 51
Timeline
Sr. Milestone
Deliverable
(Reports/ Documents & Deliverables)
Timeline
(in weeks)
6
User Acceptance Test, Training and
Go-Live
• Installation Manuals
• User manual (Role wise) with visual help kits
• UAT report
• Training Completion certificate to all Nominated
employees.
• Trainees Feedback
• Commissioning Certificate.
• FAT (Final acceptance test of the software
application) report.
T3=T2+28
7 Operation & Maintenance Support
T4=T3+1
year

45. 52
Risk & Mitigation Plan

46. 53
Risk Management Methodology
C-Net follows Risk Management methodology that covers processes for Risk Identification, Risk
Analysis, Risk Monitoring and Control.
• Risk Identification - Risk identification involves the identification of potential Risks
and documenting the characteristics of each risk.
• Risk Analysis - Risk Analysis presents a quantification of risks presented as a
summary table with detailed information on the significance and impact of each risk
• Risk Monitoring and Control - Risk Monitoring and Control provides the risk
management techniques for each risk. Risks are managed by any of the following
techniques:
• Avoid or eliminate the risk
• Mitigate the risk
• Accept or control the risk

47. 54
Risk Management Architecture
Identify New Risks
Study impact to
previously identified
risks
Adapt defined
response
Publish regular
reports
Add or eliminate
risk
Plan for
contingency
Create risk
mitigation strategy
Accept/Control the
risk
Identify source of risk
Evaluate probability
of occurrence
Establish severity of
impact
Document possible
response
Classify risk Identify risk strategy
Establish
communication
mechanism
Review Process
Risk Monitoring and Control
Risk response Planning
Risk Assessment
Risk Planning and Identification

48. 55
Risk Management Function
Function Description
Identify Search for and locate risks before they become problems.
Analyze
Transform risk data into decision-making information. Evaluate impact, probability, and timeframe,
classify risks, and prioritize risks.
Plan
Translate risk information into decisions and mitigating actions (both present and future) and
implement those actions.
Track Monitor risk indicators and mitigation or contingency actions.
Control Correct for deviations from the risk mitigation plans.
Communicate
Provide information and feedback internal & external to the project on the risk activities, current
risks, and emerging risks.
Communication will happen throughout all the functions of risk management.

49. 57