Purpose of Procurement Schedules in Felix

Felix Procurement schedules help plan, track, and manage sourcing activities across projects. They provide visibility into packages, timelines, and RFQ progress, ensuring alignment with project milestones. 

The structure of a Procurement Schedule 

• Packages: Each package represents a scope of work or goods/services to be sourced. 

• Columns: Include key details such as:
  - Package Name
  - Status
  - RFQ Linked
  - Vendor Recipients
  - Key Dates (planned vs. actual) 

• Filters: Use filters for project, status, or owner for quick navigation. 

Creating a Procurement Schedule 

• Navigate to Projects > Procurement Schedule. 
  
  

• Create using a Template or start from scratch

• Add packages manually or import via CSV template for bulk creation. 

• Ensure:
  1. Accurate package names
  2. Correct planned dates
  3. Assign package owners for accountability 

Linking RFQs to Packages 

• From the schedule, create RFQs directly linked to packages. 

Benefits: 

• Maintains traceability between RFQ and project scope. 

• Pre-fills details from the package into the RFQ for efficiency. 

Updating & Tracking Progress 

• Update status as packages move through stages: 

• Planned → RFQ Issued → Awarded → Complete 

• Use actual dates to compare against planned dates for performance tracking. 

• Add comments for context on delays or changes. 

Best Practice Tips 

• Start early: Populate the schedule during project planning. 

• Keep it current: Update regularly to reflect real-time progress. 

• Use consistent naming conventions: For packages and RFQs. 

• Leverage filters and views: For quick reporting and oversight. 

• Audit schedules periodically: Ensure alignment with project timelines. 

Reporting & Analysis 

• Export schedules for reporting or integrate with reporting platforms such as PowerBi

• Use schedule data to identify bottlenecks and improve future planning. 

Quick Checklist 

• [  ] Create packages with accurate details. 

• [  ] Create RFQs from packages for traceability and avoid linking later. 

• [  ] Update status and dates regularly. 

• [  ] Review schedule for delays and risks. 

• [  ] Export for reporting when needed.