Jump to content
The Wifcon Forums and Blogs

Recommended Posts

Good Afternoon,

I do not have a lot of experience reviewing acquisition requirements packages. However, it is a new skill that I am eager to develop. Specifically, I am looking for advice on reviewing a SOW and QASP.

Any advice that could be given reviewing these documents will be tremendously appreciated.

 

Thank You

 

Link to post
Share on other sites

Read the SOW.  After reading it, do you understand what the contractor has to do during performance?  If YES, that's good.  If NO, it might need to be re-written.

Generally, QASPs are prepared by the Government but are not incorporated into the contract.  The QASP is for use by Government personnel.  The Government may change the QASP any day of the week without contract modification.

Link to post
Share on other sites

 An idea if you have not explored it yet.   A tool was developed by several agencies a while back to provide help and guidance on Performance Based Acquisitions.  There are different versions out there on the internet now.  Search the internet for "7 steps to performance based acquisition" and you will find it along with other results that might help you in developing your own review skills.

Here is one - https://www.dau.edu/cop/pm/DAU Sponsored Documents/Seven Steps to Performance Based Acquistion.pdf

 

Link to post
Share on other sites

ji20874 gave some good general advice. Just to add I typically look for indicators that the PWS (or SOW if you prefer) is not requiring the contractor to perform inherently governmental functions (FAR Subpart 7.5), or personal services (FAR Subpart 37.104). I have many years of experience reviewing these documents.  In my experience you need to have some analytical skills, critical reading skills, and common sense. One example that comes to mind is a PWS for IT support services that I reviewed where the contractor was tasked to "monitor the networks for security issues". That was all that specific task required. My feedback to the requiring activity was, and what do you want the contractor to do if they detect issues? Are they just supposed to monitor, do you want them to correct the issues, report the issue to the Government, what?  In my personal experience a good review takes a special skill set, most 1102's I have worked with either do not have this skill set, or are too busy to do a comprehensive review of these documents.  Your mileage may vary.

Link to post
Share on other sites

jtolli brings up good points and highlights an example of common problems.  One reason I like use of SOOs instead or PWS or SOW is you just describe outcomes.  In this case the government describes security needs at a high level.  You can also add constraints on what you don’t want.  Then let industry propose solutions and associated PWSs based upon their unique approach.  How well they address issues is part of the evaluation.

Link to post
Share on other sites

I agree with all information/sources provided thus far. 

Wanted to add another resource that I found helpful early in my career. Management Concepts published a book called "How to Write a Statement of Work." The author is Peter S. Cole. It provides a macro view (not agency/industry specific) for the elements of a PWS, SOW, SOO, and many other things. 

There are several editions out there (I think the 6th was the last one). I have the 5th edition and originally picked a used version for like $40.

Great resource for me. 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...