• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About formerfed

  • Rank
    Gold Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

12,214 profile views
  1. If you have confidence in the government estimate, why not? I would tell each company that the government desires paying no more than $98,000 and what's their best price.
  2. The first question I would ask the technical office is the reason for the "how" to prescriptive elements. If something needs accomplished in a set way, make that part of the "constraints" section of the SOO. In other words you say "these are the objectives of the acquisition, however certain items listed as constraints need complied with." For example security reasons or interfacing with another project may require work to be performed a certain way.
  3. It doesn't make sense. I'm guessing the original intent got lost someplace along the way
  4. I worked at an Army location where all awards had to result from contracts prepared from scratch. Contracts couldn't be a simple unilateral acceptance of offers and everything was done via SF26 signed by both parties. If a solution resulted in a contractor selection, the pertinent parts of the proposal along with the essential parts of the SOW were put into the contract. Then the contractor was called in and the CO went over all the language as well as all the clauses with the contractor. The contractor and the CO essentially agreed to everything the contractor is required to do in clear terms. A lot of work but well worth it in most instances.
  5. Excellent advice! OP, you are a contractor and an employee of that company. If things aren't going right, you raise the issue within your company. Your boss tells you what to do. It really shouldn't matter to you what the BPA says. That's something your employer deals with.
  6. Competing objectives pretty much sums up a lot about government buying. Its confusing when you try and sort through it all. Pick just one like socio-economic and it's puzzling on its own. If I have a requirement that can be met by women owned, veteran owned, minority owned business, etc., which do I pick? From a high level, category management makes sense. Have the agency with the most expertise and knowledge do the consolidated buying. But if I truly consolidate and leverage the buying power to get the most favorable pricing, I likely will exclude small businesses. I also likely will award to a very few number of sources at the expense of spreading buisness to many companies. So a handful of companies reap rewards which many other companies are injured. At the same time this concept probably hurts individual agencies and their programs because it takes away preferences and unique but needed features of products and services. There's a cost associated with "one size fits all." What would be nice is for the government to eliminate these conflicts.
  7. Since this is a $500,000 action using simplified acquisition procedures, I wouldn't necessarily consider the quote technically unacceptable. I could go back and ask why parts weren't included. The vendor could simply revise the quote and we've home free.
  8. He could but just imagine all the pushback - intelligence agencies saying national security is dependent upon their contractors, defense saying only certain large businesses are capable and their requirements are so unique it will drive up costs for other agencies, Homeland Security saying they need flexibility only companies familiar with them can provide. It goes on and on. Every agency says they are unique. Cabinet Secretaries can't even make their components share the same data centers.
  9. Don, They certainly could be used together. But I'm think if past performance was done in the manner described, agencies could get to award quicker and less effort for both industry and the government. From what I gather this process involves multiple awards initially. Each contractor performs for a certain period of time, delivers their products, the government evaluates and makes a selection decision. That involves a lot of time and expense for everyone. My thinking is could the government through the past performance process gain enough information and insight about the offerors to make a selection without the prototypes? I believe they could assuming the work is the typical IT development.
  10. Category management is just another name for something that's practiced a lot, particularly in the private sector with large corporations. Its just a twist on strategic sourcing. Regardless, the big question is why should the government be duplicating contracting efforts for the same things many times over. Of course there are lots of good reasons. Then there are lots of reasons why they shouldn't. If you look at buying practices across the government for the same commodity, there are good results from very experienced buyers and there are horrible results from others. So why not have the best buyers contract on behalf of the entire government and really leverage the buying power? A lot of duplication and waste exist right now and without good reason. I heard one agency say they won't use GSA Schedules because their management evaluates the contracting office and their need for staffing resources on the volume and complexity of work they do. A GSA Schedule order gets a fraction of weight compared to them doing their own contract. Many other agencies say GSA Schedules won't allow them to negotiate their own special terms and conditions on task orders, which isn't true. So many existing ways to save money and time are in place now but aren't used such as GWACS, GSA Schedules, other agency contracts using interagency agreements, etc. In order for this concept to work, agencies need to be forced to use the sources. More importantly agencies will have to relinquish some of their existing flexibilities to buy items unique to them or those that simply reflect personal preferences. I remember a firearms manufacturer at a conference saying that the non-military section of the government uses 22 makes/models of handguns. Probably most important, agencies need to give up control over the management of their needs and spending. That's an uphill battle and I don't see the Administration willing to do battle to win.
  11. This also isn't a whole lot different than negotiating varying profit/fee percentages with contract types. A contract may contain multiple CLIN with varying contract types. Based on associated risks by CLIN, you would expect different profit rates.
  12. I've noticed several new attempts to speed up awards and reduce time and effort required by both government and industry. Here's one example. I highlighted this one because of the attention Anne Rung gave. Essentially HHS used a streamlined process to select a contractor for IT development work. The contracts office initially faced a 26 page SOW and looked for something quicker because "they were clearly headed down the path of a traditional six-month procurement likely resulting in the selection of a contractor with the best written proposal." What they came up with is a process fairly typical for Agile where a limited number of sources get selected for prototype development. Then a selection for long term development is made based on the prototype results. Since there are multiple ways to quickly reduce the number of potential sources, it looks like the real problem needing solved is how do you know which source is really the most capable? Seeing actual prototype results rather than just reading a proposal is an easy answer but is that conclusive? I'm wondering if more effective use of past performance is a better solution. I don't mean the more typical means of sending out email questionnaires or canned phone call questions to references and checking PPIRS. I'm thinking doing comprehensive research and finding the most relevant customers. Once located, go through a fact finding process which may include site visits and seeing how well the offerors delivered on their promises. In the case of IT, the questions are do the products do everything intended, are the users satisfied, was the work performed within budget, were user long term needs truly accommodated (this is a very important consideration with Agile), etc. What do you think?
  13. By the time a contracting office or contracting officer is involved, hopefully the agency's acquisition process has worked through a strategy where the need is met by a contract. Suddenly deciding a requirement gets done through a grant or cooperative agreement sounds strange like the agency doesn't know what they are doing. In order words the program need is X. The acquisition process should decide upfront what method is best to satisfy X - is it a grant, a cooperative agreement, another agency, in-house, a contract, etc.? I think Don is bringing up the right points.
  14. There's a lot of generalization about Contract Specialists positions in the government that's just not true. Actually a lot of variation exists. Some contract specialists work in a narrow and specialized field in their agency. DoD has many. It takes a long time and lots of training and experience to become proficient. Other contract specialists are more like gloried clerks and spent a lot of their days doing administrative tasks. Still others get caught up in lots of other duties like doing IT support, liaison with finance and budgeting, interfacing with industry and particularly small businesses, and the like. In some places, contracting is viewed by program offices as barrier to getting what they want. In other places some, but not all, of the contracting staff are viewed as valuable assets. Those people know the agency programs and can provide advice and assistance in making acquisition work for them. To get there individuals have to work hard and demonstrate their value by showing professionalism, good communication skills, exhibiting critical thinking and providing solutions to program needs. The key to finding the right job is getting started. You need to get your foot in the door through some means like an entry level position or an intern program. Just having status will open up lots of doors. The one unique thing about the government is you can switch jobs and it doesn't look bad on your resume. In fact many people at the senior management level like to see employees in contracting with a board range of experience. I think a JD degree is great. The only issue you might face is reluctance by the selecting official - most of us in contracting are way too familiar with the legal response that "you can't do that" rather than "here's the way to get that done." So in an interview, my suggestion is stress how you like to find the optimal solutions. Good luck!
  15. I think there are at least a couple reasons to disclose amounts. One is the solicitation doesn't provide enough information for offerors to understand the full effort. Another is you don't have enough money for what is apparently needed for everything. So you tell everyone what you do have and try to get the most for your budget.