ANNEXURE-3-Specifications.pdf
PDF 154 KB Posted
- Solicitation number
- SF30-A00002-AMENDMENT
- Issued by
-
Department of State
About this file
This document is a set of technical specifications for the construction of a Police Facility at the U.S. Embassy in New Delhi. It covers general requirements for the contractor, including coordination of all work phases, inspection and acceptance of materials and workmanship, adherence to manufacturer instructions, and protection of completed work. Key deliverables and staffing requirements are outlined, such as a 90-day work schedule, a Project Manager with at least 5 years' experience, and a Safety Coordinator. The document also specifies procedures for RFIs, weekly coordination meetings, field engineering, and protection of existing structures and vegetation.
The document further details requirements for the project schedule, including an Initial Project Execution Schedule (IPES), a Baseline Project Execution Schedule (BPES), and monthly PES updates that track actual progress and forecast future work. It mandates resource and cost loading, and outlines submittal requirements for the schedules. The government will review and approve the schedules, which must use Oracle Primavera or Microsoft Project software. Payment approval will be based on verified monthly progress, with a procurement log tracking the status of major items.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| ANNEXURE-4-DEL_Police Facilities Narrative.pdf | ||
| SF30-A00002.pdf | ||
| ANNEXURE-2-Safety Measures.pdf | ||
| ANNEXURE-1-Responses to Contractor Questions.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Police Facility at U.S. Embassy New Delhi
Division One Specifications for "Project Execution and Coordination"
Construction Execution and Coordination
1. General Requirements:
• - Contractor to coordinate all phases of work
• - Inspect materials and workmanship, reject defective items
• - Install per manufacturer's instructions
• - Protect completed work
2. Deliverables that are required for Notice to Proceed (NTP):
3. Limited Notice to Proceed (LNTP) Requirements:
• - Submit 90-day schedule of work leading up to full NTP
4. On-Site Staff Requirements:
• - Project Manager: Minimum 5 years’ experience
• - Safety Coordinator
5. Local Regulations:
• - Contractor shall adhere to all applicable local regulations
6. Pre-Construction Conference:
• - Agenda to include:
o a) Review of plans and requirements o b) Security and material delivery procedures o c) Personnel assignments o d) Communication procedures o e) Record minutes by contractor
7. RFI Procedures:
• - Submit RFIs via email to Contracting Officer's Representative (COR)
8. Weekly Coordination Meeting:
• - Contractor to record and distribute meeting minutes
9. Field Engineering:
• - Establish property lines and benchmarks
• - Confirm existing utility locations
• - Monitor adjacent structures
10. Protection:
• - Protect structures and vegetation as shown on drawings.
Scheduling Requirements
PART 1: GENERAL
1.01 SUMMARY
This section provides guidelines for the development of a simplified resource-loaded schedule with a schedule of values for the project. The project schedule must be submitted in Microsoft Project and include a Gant chart.
1.02 PURPOSE
The Project Execution Schedule (PES) aims to:
• - Provide a comprehensive execution plan.
• - Coordinate all project activities.
• - Record and report actual progress.
• - Forecast completion dates.
• - Facilitate progress payments.
PART 2: SCHEDULE DEVELOPMENT
• 2.01 INITIAL PROJECT EXECUTION SCHEDULE (IPES)
o - Submit IPES within 30 days of contract award.
o - IPES must include tasks, milestones, and be cost-loaded.
• 2.02 BASELINE PROJECT EXECUTION SCHEDULE (BPES)
o - Submit BPES before receiving the Notice to Proceed (NTP).
o - BPES must be fully cost-loaded and resource-loaded.
o - Ensure all tasks and milestones are detailed.
• 2.03 PROJECT EXECUTION SCHEDULE (PES) UPDATES
o - Monthly updates are required.
o - Include actual progress data and forecast future work.
o - Submit printed copies and digital files.
• 2.04 REQUIRED ACTIVITIES AND MILESTONES
o - Contract award.
o - Notice to Proceed (NTP).
o - Substantial completion.
o - Final project completion.
o - Major deliverables and procurement tasks.
PART 3: RESOURCE AND COST LOADING
• 3.01 RESOURCE LOADING
o - Define and quantify all resources for each activity.
o - Labor: Quantify by labor-day units.
o - Equipment: Quantify by day units.
o - Materials: Define and quantify as applicable.
• 3.02 COST LOADING
o - Assign costs to all cost-bearing activities.
o - Ensure the total budgeted cost matches the contract amount.
o - Avoid front-end cost loading.
PART 4: SUBMITTALS
• 4.01 SUBMITTAL REQUIREMENTS
o - Submit schedules in accordance with the contract documents.
o - Include narrative reports, procurement logs, and progress charts.
o - Provide both printed copies and digital files on CDs and via email.
• 4.02 REVIEW PROCESS
o - The government will review and approve the submitted schedules.
o - Corrections or additional information may be requested.
PART 5: SOFTWARE AND TOOLS
• 5.01 SCHEDULING SOFTWARE
o - Use Oracle Primavera, or Microsoft Project.
o - Maintain project-specific settings and avoid global settings.
PART 6: PAYMENT APPLICATION
• 6.01 PAYMENT APPROVAL
o - Approval based on verified progress each month.
o – Contractor to include a schedule update every month.
• - 6.02 PROCUREMENT LOG
o - Include all major procurement items in the schedule.
o - Track each item's status from order to arrival on-site.
File details come from the government source that posted it. Updated .