Issue: Extensive data collection requirements via the Federal Acquisition Regulation combined with an explosion in data reporting for agency specific procurement programs and the Federal Strategic Sourcing Initiative (FSSI). These data reporting requirements are increasing costs and risks for contractors across the federal procurement enterprise. Costs that are ultimately borne by customer agencies through higher prices ...more »
1. Reporting and Compliance
Question 1: What reporting or other compliance requirements are most burdensome and why?
Question 2: How would you streamline reporting and compliance requirements? (please cite or describe specific examples if you can)
Question 3: What other compliance information are you providing to the federal government outside the procurement process that could be used to reduce duplication?
Issue: Reform the MAS Pricing Policies. Specifically, eliminate the Price Reduction Clause (PRC), GSAR Clause 552.238-75. The current MAS pricing policies do not reflect current practices in the commercial market place. The pricing policies are inconsistent with the statutory and regulatory mandates for competition at the order level. The increased transactional and contract administration costs for compliance with ...more »
Issue: The overly complex, burdensome ordering procedures for the establishment of Blanket Purchase Agreements (BPAs) under the GSA Schedules program. Specifically the preference for multiple award BPAs over single award BPAs. The strong preference of multiple award BPAs undermines the ability of customer agencies to achieve best value outcomes using the GSA Schedules program. It essentially limits the tools in the ...more »
Issue: Intellectual property rights as currently set forth in GSA Schedule contracts are unclear, cumbersome and unduly burdensome for contractors. The End User License Agreement (EULA) requirements remain unclear in IT Schedule 70. As such, each license agreement must be reviewed by the contracting officer and legal counsel. Recommendation: A basic set of terms should be developed that identify the key requirements ...more »
there are increased requirements for reporting and compliance that are not reimbursed by the Government but require contractors to develop tracking and reporting systems and have dedicated resources to maintaining the system and information for reporting. CDM is an excellent example of this.
Issue: Restrictive experience requirements under the GSA Schedule program. For example, under IT Schedule 70 a company must have been in business for at least two years to be eligible for a contract. The GSA Schedule experience requirements limit access to new, innovation companies providing cutting edge technologies. It is an unnecessary barrier to entry to the federal market place. Recommendation: Eliminate ...more »
Over the last decade, the number of laws, regulations and provisions that apply to commercial item have dramatically increased. For example, in 1996 under 52.212-5(b) there were 17 provisions of law or executive orders identified as applicable to commercial item contracts. In 2012, the number has climbed to 51. The resulting explosion of statutes and regulations applicable to commercial item contracting increases ...more »
This clause creates significant training, monitoring and reporting requirements for organizations selling to the private sector and government. Eliminating the requirement would save internal efforts, which can be extensive depending on the organization.
Each site visited has unique registration, password requirements and required company data. Cumbersome and redundant. While it is understandable that agencies are different and data base information is not shared, some intra agency information is not shared from one platform to the next. There needs to be a Clearing House for each Agency and from there a sharing agreement between agencies.
FAR needs updated so that the contractor community does not have to submit numerous copies of forms such as an assignment of claims, novation agreement or change of name agreement. With going electronic, paperless, and electronic signatures, duplicate copies shouldn't be required.
Government reporting systems have a tendency to grow over time without an overall design or architecture. As a consequence they can quickly become an alphabet soup of acronyms, with indecpherable connections and frustratingly different methods and rules of entry and extraction. A good example of this is the confusing jumble of systems that make up the government's past performance/integrity system. Suggest that systems ...more »
The government (and the taxpayer) could be best served if procurement officials modernize their processes for managing and tracking procurement data. Why ’reengineer paperwork’ when the trend is to go paperless? I get the point—I’m just being a bit whimsical. The meaning of the message really: How can we improve our processes, decisions, and trust if we don’t have a piece of paper validating what we are doing? There are ...more »