Jump to content
The Wifcon Forums and Blogs


  • Content Count

  • Joined

  • Last visited

Everything posted by Confused1102

  1. Thank you all for your inputs. I thought the topic would bring up some good discussion and I appreciate the perspectives shared.
  2. Thats not what it says, it says, 'such as' which imply it's an example of a specific source.
  3. You are correct, I am looking for opinions and I think you characterized our different perceptions of the text correctly. Obviously, we both think 'my [our] interpretation better meets the reasonable and prudent person standard.' I appreciate your opinion. I look forward to hearing/seeing what others think as well.
  4. C Culham; I read the sentence as 1) through another Government agency or 2) from a specific source. So it doesn't change my thinking. ji20874; who says an EDWOSB isn't a specific source? Do you have a definition for the term?
  5. Scenario: You're doing an EDWOSB Sole Source award via 10 United States Code 2304(c)(5), as implemented by FAR 6.302-5: Authorized or Required by Statute using EDWOSB Program,15 U.S.C. 637(m), as implemented by FAR 19.1506(a). Assume all requirements of 19.1506(a) are satisfied. Are you required to post a synopsis required by FAR 5.201(b)? Excpetion at FAR 5.202(a) "The proposed contract action is expressly authorized or required by a statute to be made through another Government agency, including acquisitions from the Small Business Administration (SBA) using the authority of section 8(a) of the Small Business Act (but see 5.205(f)), or from a specific source such as a workshop for the blind under the rules of the Committee for the Purchase from the Blind and Other Severely Disabled;" My thought is No, you don't need to post the synopsis because you are making an award authorized by statute from a specific source (an EDWOSB). But I feel the wording of 5.202(a)(4) isn't exactly clearly. Wanted to see what others thought of this sitaution. If my interpertation is accurate, then this would apply to EDWOSB, WOSB, SDVOSB, and HUBZone.
  6. I think it's a great idea! And echoing what Vern already said, it will show how cumbersome DoD statutory/regulatory/policy is for a working professional. I don't envy the person tasked with compiling or maintaining the tool. As you build the tool, parts you have already consolidated are going to be updated as you are compiling other parts (i.e. assuming you work by part in numerical succession, as you are compiling Part 15, DFARS Part 5 will be updated). 1. Yes, I would use such a tool if it were user friendly. In my opinion this would mean having the tool web based, similar to the Air Force Hill FAR site, with the FAR Parts listed on the side of the screen while viewing the content in the center of the screen and able to scroll through an entire part without having to click on each individual subpart (like acquisition.gov). Although not entirely necessary it could have links to the actual regulations on the top; similar to how the Air Force site allows you to switch between FAR, DFARS, NMCARS, AFARS, etc. 2. I think shading is sufficient for distinguishing between the different regulations, and it is useful to have regulation cited on the left, otherwise a reader would need to refer back to some legend every the used the tool if they were not a frequent user. 3. To make the tool more useful, do you plan to incorporate clauses? Or a clause matrix? While the matrix isn't full proof, it is a tool to help start looking at clauses for RFP's, exporting it to excel makes it even more useful. I think a consolidated clause matrix across the regulations would be a powerful tool, although possibly a separate project from your current endeavor.
  • Create New...