Google Map API portal
Budget: $10 – $10,000 USD
Please share interest and Qualification to share more details. Here is an overview
1.1 SYSTEM DESCRIPTION:
This is a web application that enables users to manage properties and track their maintenance status. For the remainder of the document, we will refer to it as SYSTEM. Property Managers, Contractors, and Engineers can generate status reports, invite contractors for quotes, and engineering drawings evaluations. The system caters to various user classes, including System Administrators, Users (Property Managers,. contractors, Engineers), Managers, Companies, and Users. The system is inspired by many products including ProSiteAudit , SpotOnSiteApp ,IPave ,SnapInspect ,GoCanvas ,PropertyIntel: Aspire SW ,Happyco- Buildum ,Planswift.
The SYSTEM provides numerous distinct value propositions including unlimited issues to report, with creative interface and map annotations, ability to include videos in the audit report, mapping to existing inspection industry standards, robust reselling capabilities. Further, the system is excelling in its integration capabilities with other systems, data portability, and ease of reconstructing the audit reports to make the reports platform independent.
User Classes and Characteristics mapping:
User Administration Dashboard: Enhance functionalities for System Administrators, Companies, and Managers to manage user accounts, view usage statistics, and handle payments.
Annotation Dashboard: Ensure it caters to the specific needs of Property Managers, Contractors, and Engineers for managing properties and engineering drawings evaluations.
Pricing and Reports Dashboards: Provide functionalities for Users, Companies, and Managers to subscribe to service packages, make payments, and view reports and usage statistics.
1.1.1 BUSINESS LOGIC LAYER:
This is in a layer accessible via dashboards to apply business logic:
a. Users Administration dashboard Manages registrations, logins, usages
b. Annotation dashboard: To track annotation activities (shapes/status/location/company)
c. Communication dashboard: to track communications with engineers, contractors, subcontractors, and users.
d. Pricing dashboard: to create new pricing for different users/ actions: Pricing interface for determining the cost per activity, where each activity is equal to credits, where each credit is equal to one dollar. PHASE 3
e. Reporting dashboard: To generate ad-hoc and new reports for current and future APIs.
1.1.2 APPLICATION LAYER
a. Users Administration module: To create/edit/delete system users.
b. Annotation module to add pins, zones, lines, double-colored circles to highlight the severity and type to a map and associate images/videos/audios/ using both Google APIs., and Bing API
c. Communication module to send issues to contractors by property manager, to send RFQ to subcontractors, and to send assignments to team members.
d. Pricing module where every action is equal to a set number of credits, with an interface to adjust the credit for each action.
e. Reporting module, to include longitude/ latitude of each area, along with images. Videos (2 minutes ) and audio notes to be accessible online, as well as backend access of content with filtering and aggregation capabilities for each resource, user, action, report item and report.
f. ETL module to integrate with other APIs and to extract data and map them back and forth.
g. RFP module to generate requests for proposals.
1.1.3 INITIAL SITE MAP
USER ADMINISTRATION DASHBOARD
├── LOGIN PAGE
├── FORGOT PASSWORD
├── COMPANY REGISTRATION
├── SUB ACCOUNT PAGE
└── USER REGISTRATION PAGE
ANNOTATION DASHBOARD
├── UPLOAD FILES
├── LOCATION/INVENTORY PAGE
├── MANAGE SITES PAGE
└── AUDIT ISSUES PAGE
PRICING DASHBOARD
├── PRICING DASHBOARD
├── PAYMENT
├── BACKGROUND SERVICE
└── CREDIT HISTORY
REPORTS DASHBOARD
├── REPORTS HOME PAGE
├── TRANSACTION REPORT
├── METERING REPORT
└── HEAT MAP
COMMUNICATION DASHBOARD
├── EMAIL TEMPLATE PAGE
├── INVITATION TEMPLATE PAGE
└── INCOMING AUDIT LINKS PAGE
1.2 PROPOSAL SUBMISSION GUIDELINES
• Submission Method: Proposals should be submitted electronically
• Proposal Format: Proposals should be submitted in PDF format.
• Required Documentation: Proposals should include a detailed project plan over 5 phases, a cost estimate, and examples of previous similar work.
Phase 1: Basic user login, Mapping annotation, basic reports, simple payment processing.
Phase 2: User Management Module with Company (Accounts), Account Managers and users, improved communication, and associated reports.
Phase 3: Detailed payment processing, credit mapping, promotion and discounts and associated reports
Phase 4: ETL capabilities with other systems and opening APIs and associated reports.
Phase 5:RFQ and estimation modules ( details to be determined) and associated reports.
1.3 PROJECT TIMELINE
• Start Date: ASAP
• End Date: 30 days from the start date (PHASE 1)
• Key Milestones: To be determined based on the vendor’s proposal based on the required 5 phases.
• Critical Dates: Proposals are due no later than 10 days from RFP receipt.
1.4 BUDGET
• Budget Range: The budget for this project is flexible and will depend on the proposed solution and associated costs.
• Payment Terms: Payment terms and schedule will be negotiated with the selected vendor.
1.5 VENDOR QUALIFICATIONS AND EXPERIENCE
• Vendors should have proven experience in developing web-based property management systems, with a portfolio of similar projects completed in the past. Relevant certifications and compliance with industry standards are also expected.
1.6 EVALUATION CRITERIA
• Proposals will be evaluated based on the vendor’s experience, proposed solution, UX drafts, project plan, cost, and adherence to the RFP requirements.
1.7 TERMS AND CONDITIONS
• The selected vendor will be required to enter a contract with SYSTEM, agreeing to all terms and conditions outlined in the RFP and the subsequent agreement as work for hire. This is a long-term outsourcing project, with expected ongoing support and maintenance.
1.8 CONTACT INFORMATION
• For any questions or clarifications regarding this RFP, please contact Dr. Ahmed Gomaa, ahgomaa@gmail..com
1.9 UX DESIGN
• Vendors are expected to propose an innovative, cross-platform UX/UI design, ensuring an intuitive and user-friendly experience.
1.10 QUALITY ASSURANCE AND TESTING
• The vendor is expected to conduct comprehensive quality assurance and testing, including unit, integration, and user acceptance testing, to ensure the reliability and performance of the system.
• Code must be approved by SYSTEM staff.
1.11 TRAINING AND DOCUMENTATION
• The selected vendor will be required to provide comprehensive training to SYSTEM staff and users to ensure proper use of the system.
• Detailed documentation, including user manuals and system administration guides, must be provided.
• The documentation should be clear, concise, and easily accessible to users of different technical backgrounds.
1.1 SYSTEM DESCRIPTION:
This is a web application that enables users to manage properties and track their maintenance status. For the remainder of the document, we will refer to it as SYSTEM. Property Managers, Contractors, and Engineers can generate status reports, invite contractors for quotes, and engineering drawings evaluations. The system caters to various user classes, including System Administrators, Users (Property Managers,. contractors, Engineers), Managers, Companies, and Users. The system is inspired by many products including ProSiteAudit , SpotOnSiteApp ,IPave ,SnapInspect ,GoCanvas ,PropertyIntel: Aspire SW ,Happyco- Buildum ,Planswift.
The SYSTEM provides numerous distinct value propositions including unlimited issues to report, with creative interface and map annotations, ability to include videos in the audit report, mapping to existing inspection industry standards, robust reselling capabilities. Further, the system is excelling in its integration capabilities with other systems, data portability, and ease of reconstructing the audit reports to make the reports platform independent.
User Classes and Characteristics mapping:
User Administration Dashboard: Enhance functionalities for System Administrators, Companies, and Managers to manage user accounts, view usage statistics, and handle payments.
Annotation Dashboard: Ensure it caters to the specific needs of Property Managers, Contractors, and Engineers for managing properties and engineering drawings evaluations.
Pricing and Reports Dashboards: Provide functionalities for Users, Companies, and Managers to subscribe to service packages, make payments, and view reports and usage statistics.
1.1.1 BUSINESS LOGIC LAYER:
This is in a layer accessible via dashboards to apply business logic:
a. Users Administration dashboard Manages registrations, logins, usages
b. Annotation dashboard: To track annotation activities (shapes/status/location/company)
c. Communication dashboard: to track communications with engineers, contractors, subcontractors, and users.
d. Pricing dashboard: to create new pricing for different users/ actions: Pricing interface for determining the cost per activity, where each activity is equal to credits, where each credit is equal to one dollar. PHASE 3
e. Reporting dashboard: To generate ad-hoc and new reports for current and future APIs.
1.1.2 APPLICATION LAYER
a. Users Administration module: To create/edit/delete system users.
b. Annotation module to add pins, zones, lines, double-colored circles to highlight the severity and type to a map and associate images/videos/audios/ using both Google APIs., and Bing API
c. Communication module to send issues to contractors by property manager, to send RFQ to subcontractors, and to send assignments to team members.
d. Pricing module where every action is equal to a set number of credits, with an interface to adjust the credit for each action.
e. Reporting module, to include longitude/ latitude of each area, along with images. Videos (2 minutes ) and audio notes to be accessible online, as well as backend access of content with filtering and aggregation capabilities for each resource, user, action, report item and report.
f. ETL module to integrate with other APIs and to extract data and map them back and forth.
g. RFP module to generate requests for proposals.
1.1.3 INITIAL SITE MAP
USER ADMINISTRATION DASHBOARD
├── LOGIN PAGE
├── FORGOT PASSWORD
├── COMPANY REGISTRATION
├── SUB ACCOUNT PAGE
└── USER REGISTRATION PAGE
ANNOTATION DASHBOARD
├── UPLOAD FILES
├── LOCATION/INVENTORY PAGE
├── MANAGE SITES PAGE
└── AUDIT ISSUES PAGE
PRICING DASHBOARD
├── PRICING DASHBOARD
├── PAYMENT
├── BACKGROUND SERVICE
└── CREDIT HISTORY
REPORTS DASHBOARD
├── REPORTS HOME PAGE
├── TRANSACTION REPORT
├── METERING REPORT
└── HEAT MAP
COMMUNICATION DASHBOARD
├── EMAIL TEMPLATE PAGE
├── INVITATION TEMPLATE PAGE
└── INCOMING AUDIT LINKS PAGE
1.2 PROPOSAL SUBMISSION GUIDELINES
• Submission Method: Proposals should be submitted electronically
• Proposal Format: Proposals should be submitted in PDF format.
• Required Documentation: Proposals should include a detailed project plan over 5 phases, a cost estimate, and examples of previous similar work.
Phase 1: Basic user login, Mapping annotation, basic reports, simple payment processing.
Phase 2: User Management Module with Company (Accounts), Account Managers and users, improved communication, and associated reports.
Phase 3: Detailed payment processing, credit mapping, promotion and discounts and associated reports
Phase 4: ETL capabilities with other systems and opening APIs and associated reports.
Phase 5:RFQ and estimation modules ( details to be determined) and associated reports.
1.3 PROJECT TIMELINE
• Start Date: ASAP
• End Date: 30 days from the start date (PHASE 1)
• Key Milestones: To be determined based on the vendor’s proposal based on the required 5 phases.
• Critical Dates: Proposals are due no later than 10 days from RFP receipt.
1.4 BUDGET
• Budget Range: The budget for this project is flexible and will depend on the proposed solution and associated costs.
• Payment Terms: Payment terms and schedule will be negotiated with the selected vendor.
1.5 VENDOR QUALIFICATIONS AND EXPERIENCE
• Vendors should have proven experience in developing web-based property management systems, with a portfolio of similar projects completed in the past. Relevant certifications and compliance with industry standards are also expected.
1.6 EVALUATION CRITERIA
• Proposals will be evaluated based on the vendor’s experience, proposed solution, UX drafts, project plan, cost, and adherence to the RFP requirements.
1.7 TERMS AND CONDITIONS
• The selected vendor will be required to enter a contract with SYSTEM, agreeing to all terms and conditions outlined in the RFP and the subsequent agreement as work for hire. This is a long-term outsourcing project, with expected ongoing support and maintenance.
1.8 CONTACT INFORMATION
• For any questions or clarifications regarding this RFP, please contact Dr. Ahmed Gomaa, ahgomaa@gmail..com
1.9 UX DESIGN
• Vendors are expected to propose an innovative, cross-platform UX/UI design, ensuring an intuitive and user-friendly experience.
1.10 QUALITY ASSURANCE AND TESTING
• The vendor is expected to conduct comprehensive quality assurance and testing, including unit, integration, and user acceptance testing, to ensure the reliability and performance of the system.
• Code must be approved by SYSTEM staff.
1.11 TRAINING AND DOCUMENTATION
• The selected vendor will be required to provide comprehensive training to SYSTEM staff and users to ensure proper use of the system.
• Detailed documentation, including user manuals and system administration guides, must be provided.
• The documentation should be clear, concise, and easily accessible to users of different technical backgrounds.