Month: October 2017

If you site is integrated with Microsoft Dynamics SL and Spitfire Compliance Tracking has been checked in ICTool. then out of compliance items will also affect AP Vouchers. If the

Compliance from Vendor If both a Vendor document and related Commitment (or CCO) document include a Compliance item of the same type, the Vendor can provide compliance to the Commitment.

When a Compliance item with the Notify option triggers an out-of-compliance signal, a Compliance Notification document is created through an automatic workflow script. Based on routing rules and Contact setup,

The Compliance Log lists all compliances being tracked in your projects. You can filter the report. To open the Compliance Log: Click Site Menu | Report Browser. From the Report

Setup of Compliance tracking and notification requires the use of various Manage and System Admin tools and features of sfPMS. Steps Involved Step 1: Prepare Gather information. Step 2: Use

Before establishing compliance tracking in sfPMS, you’ll need to gather the following information: What Compliance types does your company track? Which of these Compliance types are required and which are

Assuming you use different types of commitments (subcontracts and vendors, you may need to set up these subtypes in sfPMS if subtypes were not already configured during implementation. Vendor Subtypes

A Compliance type defines the type of compliance requirement needed in your project (ex: General Liability Insurance, Workman’s Comp Insurance, etc.). Compliance types can be set up as required or

If you want a Compliance Notification document to be routed to a specific person whenever a requirement is out of compliance, you’ll need to activate the Compliance Notification Doc Type.