Importance of Management System

Passive Stormwater Management Systems Greener Alternatives to Active Rainwater Collection Systems

Although rainwater collection systems facilitate sustainable living by means of reducing a household's reliance on water service providers, it may not be as practical when implemented on a larger context. Stormwater collection for an entire community requires years of planning and construction to effectively set an adequately functional rainwater management system in place. Several personnel must be tapped to construct the various well placed catchment areas, dependable conveyance mechanisms, massive storage facilities, efficient distribution mechanisms, and most importantly, effective purification facilities.

Not too many communities have the financial capacity to install rainwater collection systems. As such, they opt for traditional methods when handling stormwater—the construction of sewage systems, floodgates, dams, and other methods of preventing rainwater from becoming stagnant or eliminating it altogether. Fortunately, there is a natural approach to managing stormwater without setting up elaborate mechanisms and maintaining expensive facilities. Passive stormwater management systems collect and divert rainwater to sustain landscaped areas.

Passive stormwater management systems make use of various methods to channel rainwater into areas where "green" water levels need regulation. Passive stormwater management systems could use swales, microbasins, rain gardens, French drains, permeable pavements, and curb and road grading design to effectively divert rainwater to areas where it is needed most. A passive rainwater collection system emulates the natural hydrological cycle, which could efficiently support vegetation, augment groundwater recharge, and reduce erosion and flooding.

Microbasins are miniature catchment areas where small amounts of rainwater could be collected. Differently, storm water systems with swales divert rainwater from buildings. Swales' sloping configuration diverts rainwater from low to medium downpours. French drains and rain gardens facilitate quick collection of stormwater, especially during heavy downpours. French drains lead rainwater to several storage tanks while rain gardens collect stormwater and channel them into a central storage unit.

Storm water systems with permeable pavements allow rainwater to pass right through them, expediting rainwater collection. The diverted stormwater is transferred to sand or gravel sub-base layers which ultimately lead to natural soil layers. Parking lots can be designed to have various grading elements to channel rainwater into landscaped areas. Stormwater can be directed to flow right into depressed areas where it can enter and subsequently seep into exposed natural soil.

However, these stormwater best management practices could only do so much to protect areas from stormwater. Ironically, their cost-effectiveness may come with a heavy price. The amount of maintenance needed by such systems may discourage some individuals from setting them in place. As such, low impact development experts suggest that the installation of active stormwater collection mechanisms could augment the efficacy of passive rainwater collection systems. These mechanisms include multi-level tanks that could provide extra storage and much needed purification for collected stormwater.

PMI PDU Courses Need to Contain Information on Tools for Cost Management

PMI pdu courses need to contain information on tools for cost management.  At this point, the project manager should have a list of the resources and the cost needed to complete the activities.  In this section, the use of various tools and techniques will help the project manager determine the budget for his or her project.  This budget will serve as the baseline for measuring project performance in the area of cost control.  The following tools and techniques are ways to determine the budget by analyzing the resources, work package activities, planned, and unplanned risks. To earn PMI pdus the student should understand the following:

Cost Aggregation

The cost estimates for each work package is consolidated as indicated by the work breakdown structure.  The higher-level structures allow for assigning cost accounts to each component, which in the end will represent the budget for entire project. PMI PDU courses should include cost aggregation.

Reserve Analysis

The cost of managing risk and changes to scope are factored into the budget.  Contingency reserves are funds reserved for planned risks identified on the risk register.  On the other hand, management reserves are funds set aside for unplanned changes to the scope and cost of the project.  While Management reserves are include in the total project budget, they are not included in the project baseline, nor is it included in the earned value calculations discussed later in the course.  To earn PMI PDUs the student should demonstrate understanding of this.

Expert judgment

Expert judgment relies on the expertise of an individual or group that has extensive knowledge, skill, training, etc for a particular activity being performed.  The expert is able to help determine the budget and may come from the following areas as resources:

- Other project teams in the organization
- External consultants
- Stakeholders
- Professional associations
- Groups within an industry

Historical Relationships

A project manager may use historical relationships resulting from parametric or analogous calculations that produced a mathematical model that can be used to predict project costs.  An example of this is the price per square feet to build a home. PMI PDU courses should include the following:  The reliability of the model depends on the following factors:

- The information used to create the model is accurate
- The model parameters are easily quantifiable
- The mathematical model is easily applied to projects of any size and scale

Projects Operations Management Exposed (POME) Beats RUP, PMI, PRINCE2, MSF, ANCSPM, PMA+

Why POME to be considered? The current situation is that there is no one globally accepted body of knowledge of project management. Each main professional association has a vested interest in maintaining its own body of knowledge, as each case has involved such a big investment in, and commitment to, subsequent certification processes. It is therefore difficult to envisage any situation that might prompt professional associations to voluntarily cooperate to develop a global body of knowledge to which they would commit themselves. Nonetheless, there have been many Global Forums since the mid-1990s, often in association with major project management conferences, which indicates a wide recognition that a globally recognized body of knowledge would be highly desirable. One particular initiative was the coming together of a small group of internationally recognized experts to initiate workshops, beginning in 1998, to work towards a global body of project management knowledge. This group, known as OLCI (Operational Level Coordination Initiative) has recognized that one single document cannot realistically capture the entire body of project management knowledge, particularly emerging practices such as in managing "soft" projects (e.g., some organizational change projects), cutting edge research work, unpublished materials, and implicit as well as explicit knowledge and practice. Rather, there has emerged a shared recognition that the various guides and standards represent different and enriching views of selected aspects of the same overall body of knowledge. Among project managers in the Europe, Prince2, Project Management methodology, particularly in the financial industry, is the standard., the PMP also is the most respected credential in USA of It seems as though there are five major players in the project management methodology arena; PMI, Prince2, Microsoft's Solution Framework (MSF), Siemens( PMA+), ANCSPM and IBM's Rational Unified Process (RUP) are the heavyweights and although they are interwoven of each exist, we could use these as a baseline for comparison but make a stern position on reinforcing the concepts, which POME Provides. I think it is important to consider that unless you are working at the organization that gave birth to the methodology, no organization will find one of these methodologies to be "plug and play". If you are working at IBM you will in fact follow RUP from start to finish - but there is only one IBM. If you work at Microsoft, the MSF will be your Bible. I have found that each has unique tools to offer and personally like to make a mash up of them all on more complex projects. IBM's Rational Unifed Process (RUP) was designed specifically for software projects, RUP was designed with iterations as specified by what was first called Rational Software and later became part of IBM. The Rational Unified Process is still very well respected and useful within software engineering. Within RUP's Construction phase, you will find iterations. This is because it is designed for an organization that utilizes such as an Agile, Spiral, or Fountain development lifecycle. The Microsoft Solution Framework originated from Microsoft's own Best Practices, aimed to help Microsoft Project Managers and developers work with Microsoft tools and projects. It was designed with software in mind, and contains specific entities that are traceable throughout the lifecycle of a project. With the MSF, the software development lifecycle is closely mapped to the project management methodology. They don't have project phases. They have project tracks. Its an important distinction, indicative of the MSF philosophy, and appealing to me. Still, for simplicity's sake, let's call them Phases for now. PMI's methodology states very early in their master text, called The Project Management Book of Knowledge that the processes detailed within the book are not a methodology in and of themselves. Rather, PMI is not a methodology. It is just a toolkit and a framework for executing projects and covers everything from various stags in the project. It lays out a tremendous amount of tools, processes, and sub processes, but it was designed to be customized. The Prince2 project management methodology found root in the United Kingdom's standards for IT development and has spread throughout Europe to become the most popular project management methodology among IT professionals. Prince2 is very focused on Project Cases and Project Analysis. It may be partly because it arose from a government standard, but Prince2 enjoys particular popularity within the financial industry. Oddly enough, Prince2 has been deemed a good PM Approach towards MSF projects. I read this. I kind of get it, but not really. Siemens PMA+ evolves around building and industrial sector Projects, emphasizing on the detailed documentation and process orientation biased. It would be wholesome in various construction Projects, rather than the research Projects. Australian National Competency Standards for Project Management(ANCSPM) made Several factors combined to lead AIPM to develop competency standards, including a recognition that the possession of knowledge about a subject does not necessarily mean competence in applying that knowledge in practice. The Australian Government was also very influential, through its Department of Employment, Education, and Training, which very actively promoted the development of national competency standards for the professions. The elements of competency are expressed in action words, such as determine, guide, conduct, implement, assess outcomes, and the like. So I identified few major PM methodologies that been obsolete/ prevalent, but not limited: - RUP - PMI - Prince2 - MSF - PMA+ - ANCSPM But the POME (PROJECT OPERATIONS MANAGEMENT-----EXPOSED), which am illustrated/ illustrating would be the vital basic concepts oriented and the tunneling through the Process orientations in the Projects and its pertinent Operations. After going through the POME, it would be very agile to adopt any of the above methodologies or the others, as your base becomes resurfaced and knows what the entire real environment requires and demands. It is of holy pragmatically approach. Believe me, after you study this Book, you would be more confident and would know from minute to macro level of any project, I made this book for Projects Operations Team, who are working unknowingly. I like to make that unknowing process, which we been using in our daily life in to a streamlined and acquainted process. I made research for this book, since six years for future Project Leaders. The purpose of this POME is to help both our project leaders, and new employees who will be managing projects to start and implement a successful project. This Project Management Users Manual will act as a roadmap to accomplish this goal. Projects are committed to deliver its on time, within the budgeted cost and meeting or exceeding customer expectations with in the guidelines. It is essential that there be a consistent approach to doing projects, a standard set of tools and templates in documenting what is done, guidelines in the use of these tools, and a control process to support the Project Management Team in meeting its objectives. The purpose of this POME handbook is to document this process. "THE PAST CAN NOT BE CHANGED. THE FUTURE IS YET IN YOUR POWER." Yes, it is indeed true; POME facilitates to make your future planning more and more better in Projects and Operations. Its destiny, to have a copy of POME. The Projects and Operations Management--- Exposed(POME), is of to be a uniform reference system for handling Macro, medium and small Project solution business from the Pre Offer stage to the final handover stage inclusive of warrant, defects liability and maintenance period. Assumptions for POME - The various formats have been designed to contain the maximum necessary information for daily operations life in relevance to the Projects life cycle.. - The Standard Procedures are to be used as a reference point at any specified the same. - Regular reviews for all projects are to be done using POC (Percentage of Completion) and finance monthly reports. - It defines the tasks, authorization and responsibilities of all employees related to Bid preparation, order execution, procurement, and other related activities. The POME is made for all the executives, who in turn directly and indirectly dealt with the Projects and Operations. - The purpose of this guideline is to define the tasks and deliverables of Project Management / Controlling in the Projects business in order to strengthen the Project and Operations Controlling. - The intention of the guideline is to ensure, that all projects team gets acquainted with the in depth concepts in a planned common manner to ensure that all project execution issues and risks are under control and supports the common understanding in terms of terminology. - This guideline is applicable for all system & solution business in different sectors especially Building and Industrial sectors and also, protracted even to Information technology, Entertainment Projects. It is incredible that most organizations do not understand their fully absorbed costs and profits by customers and Clients. Most are stuck in the paradigm of products, projects and gross margins. Overheads, indirect trading, compliances, legal matters, intellectual property and other factors are not understood and neither are the true drivers of cost and revenue. Activities (direct and indirect) should be the focal point of Projects and Operations decisions. They drive costs, incur revenue and are consumed by the objects (projects/products/services) that are offered to customers. Organizations which understand this and use it to their advantage will have tremendous advantage over those who do not.... —anonymous