MUNDAUS GROUP

1. MUNDAUS GROUP PROPOSAL PROCESS

2. Proposal Pipeline

3. Understanding the Pipeline • Mundanus Group manages an online web-based data system which allows access by members to upload, review and comment on intended projects. • The pipeline is intended to outline an internal process for the management of proposals from idea to review through acceptance and proposal preparation. • A simplified overview breaks down the process.

4. Defining Symbols Acceptance Input Data Files Validate Filter Web Data Base Proposal Review Award Acceptance Process Output

5. Inputs and Outputs • Web-Based Central Data System • General Files For Upload • Proposal Documentation

6. System Processes • Review the Data • Validate Capability • Acceptance of Project • Filter Responsibilities

7. Breaking Down the Pipeline • Sourcing Projects • Uploading to Database • Reviewing by Management • Acceptance as Target • Ensuring Capture of Consortia • Appointing Responsibilities • Collecting Data • Creating the Proposal

8. Input Web Based Data Storage for Mundanus | Various levels of authorization will exist for members and consortia partners. Review | Documentation and files will be reviewed by Members and Consortia Partners as required. Files and Project Information| All documentation should be input in to the database. A preliminary acceptance can be created at this point before entering the pipeline. Input | All details reference the project after uploaded to Database enters the proposal pipeline.

9. Member Acceptance Acceptance of Project | Members must accept the project and then confirm with Consortia Partners their acceptance. Validate | After acceptance by Members and Consortia Partners another validation must be done again to finalize acceptance and move to proposal process Validate| Initial validation shall take place internally within the Board of Directors. Here Members will reconfirm if the project is achievable and level of commitment.

10. Output Database | All Members will upload their portion of the proposal responsibility. Here it will be compiled and completed with final review. Filtering Responsibility| This is the longest process which includes creating responsibility for each Member and appointing a Leader for the Project. Responsibilities will be given to each Consortia Group e.g. ten percent Design created by nominated subcontractor. Pricing completed by JV Partner etc. Review | A review of the final proposal will be conducted and approved by the Project Leader for submittal. Proposal | All sections of the proposal are uploaded to the database and compiled for submittal.

11. Review and Approval Roles Completed Member Acceptance Consortia Acceptance Roles Accepted No Yes No Yes No Yes No Yes Redefine Consortia Review and Approval Define Consortia Define Roles Rebuild No Yes

12. Proposal Management All proposal information is collected after filtering responsibilities – Define Roles. Data is collected and compiled.

13. Proposal Review Members Input Data Proposal is Reviewed by Members Data is Compiled Project Leader Final Approval Project is Reorganized for Approval

14. Reorganizing for Approval Information is Broken Down Final Approval is Obtained Sections are Updated as Needed Each Section is Reviewed By Members

15. Proposal Hierarchy Each project proposal will have a final approval by the Members. The Project Leader will give the final review and authorize submittal. Certain project proposals may require Subject Matter Experts or Consultants (SME may be a financial institute as well). Therefore final approval is given to Mundanus Project Leader.

16. Tiers of Hierarchy PPL SME MEM PAR SUB CON

17. Completing the Pipeline

18. Beyond the Pipeline Each project and its corresponding proposal has specific requirements and additions to and deletions from the pipeline are anticipated. The basis of data flow is outlined here and shall be broken down further per process.