AMENDMENT_0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to:

1. Provide answ ers to vendor questions regarding the solicitation.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 20

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 30-Jul-2014

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X H98210-14-R-0030

X 9B. DATED (SEE ITEM 11)

23-Jul-2014

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

30-Jul-2014

CODE

DEFENSE HUMAN RESOURCES ACTIVITY

4800 MARK CENTER DRIVE,

SUITE 07G12

ALEXANDRIA VA 22350-1300

H98210 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

H98210-14-R-0030

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been added by full text:

QUESTIONS AND ANSWERS

Solicitation Questions

Q1. Is there an incumbent contractor? If yes, is the incumbent eligible to bid?

A1: GTW Consultants & Associates, LLC; Not relevant to the solicitation.

Q2. If there is no incumbent how is this support currently being provided?

A2: See A1

Q3. The RFP does not address transition, if there is existing staff, is the government going to allot some period of time to handle staff and support transition from the incumbent or even ramping up for a new contract?

A3: There will be approximately 2 to 4 weeks overlap of services.

Q4. Can the Government provide workload or staffing data by Task Order One tasks that will allow offeror’s to determine the staffing level and LOE needed to support DHRA?

A4: There are 2 FTEs currently performing.

Q5. Does this contract fall under SCA guidelines since it is primarily administrative in nature?

A5: The Service Contract Act does not apply to this acquisition.

Q6. Can the Government provide clarifications regarding personnel qualifications, facilities and small business participation?

a. Does personnel qualifications relate to the Offeror’s ability to recruit and retain staff?

b. Since the staff will be working on government site what specifically is the government requiring for facilities? There is no requirement for facilities.

c. Since this is a woman-owned small business set-aside is the prime expected to have a small business plan? NO A6:

a. Since there is not a PWS reference associated with the questions, we can’t determine in what context these questions are being asked.

b. Attachment A will be revised to remove the word facilities.

c. No.

Q7. Please advise if a Contractor can use contracts where they have performed work as a sub-contractor to support the past performance requirement.

A7: Yes. Work as a sub-contractor can be used.

Q8. Please clarify how the Government wishes travel expenses to be handled for this proposal?

Which of the following is the Government’s desire?

a. Offerors shall build all travel costs into the single price for each seminar?

b. Offerors shall estimate all travel costs and include on a separate line in the schedule.

The yield a “not to exceed” line item in the contract?

c. Offerors shall not include any travel costs in their proposal and will be reimbursed for actuals based on FTR.

A8: There are no Travel requirements for this effort.

Q9. How many full-time-equivalent (FTE) personnel are assigned to this contract currently?

A9. This information will not be provided.

Q10. Is there a page limit for the past performance section and quality control plan or are these part of the 30 page technical response?

A10. The past performance requirement is separate. The Quality Control Plan is an element of the Criteria for the Technical Factor and is included in the 30 page limitation under Volume II.

Q11. Is the task proposal (limited to 20 pages) part of the 30 page technical proposal limit or is it in addition to the 30 pages allocated to the technical proposal?

A11. No. The Task Order page limitation is separate.

Q12. Please confirm the Government is requesting a CD Rom for Volume III only. The instructions do not specifically request a CD delivery for Vol I and Vol II

A12. Offerors shall submit a CD Rom for Volumes I and II in addition to the requested number of hard copies as stated in the instructions.

Q13. How many individuals are currently working in administrative support, and what are their job titles?

A13. See A4.

Q14. How many individuals are currently working in management support, and what are their job titles?

A14. None

Q15. Original FBO Solicitation announcement was for Woman-Owned Small Business but RFP document states simply Small Business. Should this be classified as Woman-Owned Small Business?

A15. Refer to Solicitation Amendment 0001.

Q16. Instructions for Volume II define page limits for Technical and Task Order with one PPRQ per reference. No indication of page limitations for the Quality Control Plan. Wan we use out standard QC Plan which is about 20 pages?

A16. See A10 Q17. Instructions for Volume III ask for a price proposal for the task and that it be annotated to the PWS. Are you asking for two price proposals with the task order price proposal defined by labor category and hours assigned to each subtask?

A17. Yes.

Q18. There are two major components of the PWS: Administrative Support and Management/Program Analyst and the technical volume should address technical approach, risk, management approach, personnel qualifications, facilities, small business participation and others. However, you’re asking us to provide a technical proposal addressing Task Order 1, which means we are going to be stating pretty much the same thing as the tasks that are in Task Order 1. Would you be willing to eliminate one of them?

A18. No. Offerors should respond to the Base PWS for the Requirements Contract and to the Task Order One PWS.

Q19. Is there an estimate of the number of personnel required to support each CLIN?

A19. Offerors should propose the number of personnel to fulfill the PWS requirements.

Q20. Are resume(s) required with the proposal? If so, for which position(s)?

A20. No, as long as Element B is fully addressed.

Q21. If resumes are required, are these to be example resumes or the resumes of the people we will use upon award?

A21. See A20.

Q22. We cannot tell the magnitude of this effort (either at the overall contract level or Task Order One level). Since there is no workload data, there is no way for a bidder to gauge the magnitude of the requirement (i.e., could be 100 hrs/yr, could be 40,000 hrs/yr).

1. How many FTEs are anticipated on the total contract per year?

2. How many FTEs are anticipated on Task Order One per year?

A22. See A4

Q23. Section 5, post award conference minutes is stated as due “Within 3 business days of post award”. Should this read “Within 3 business days of post award conference”?

A23. Yes

Q24. Attachment A, 4.1.5. How many conference rooms and calendars need to be managed?

A24. Two conference rooms and at least 4 calendars.

Q25. Attachment A, 4.1.16. How many packages are expected to be formatted each day?

A25. Approximately two packages per day.

Q26. Shall the option years be priced to only include TO1 effort with a possible rate escalation?

A26. Labor categories and loaded rates for base plus options should be provided.

Q27. What is the volume for training classes and personnel that need to be tracked?

A27. There are approximately 5 mandatory trainings taken by employees.

Q28. Are the tasks outlined in Task Order One (Attachment C) being currently completed under a current contract and if so what SCA labor categories and levels are being utilized?

A28. See A1 and A5

Q29. Is there a page limitation for the Quality Control Plan which must be submitted within Volume II – Technical (Page 16 of the RFP, Section B).

A29. See A10

Q30. Please provide volume/numbers for the following tasks outlined in Attachment C Task Order One:

a. Volume of ingoing and outgoing mail per month (4.1.4)

b. Number of Conference Rooms and conference events requiring support per month

(4.1.5).

c. Number of working groups and focus groups events requiring support per month

(4.1.13).

d. Volume of incoming and outgoing packages through the Department’s tracking system (4.1.16).

A30.

a. Approximately 40 a month in total for both ingoing and outgoing mail.

b. See A25

c. Approximately 1 to 2 working groups a week for the analyst requirement.

d. SEE A30a.

Q31. What is the current count of full-time staff providing Administrative Support and Management/Program Analyst support?

A31. See A4

Q32. What are the current labor categories and estimated number of labor hours?

A32. See A4

Q33. Since this has been set aside for WOSB, is the incumbent eligible to bid?

A33. See A1

Q34. What is the current full-time equivalent personnel count supporting this effort and task order? What is the Government’s expected personnel count required to support this effort and task order?

A34. See A4

Q35. Please provide weekly and/or monthly workload data for the task order requirement. It isn’t possible to calculate the number of personnel required without knowing the volume of the work to be performed for each requirement.

A35. See A25 and A30

Q36. Is this a task order contract and if yes, is this a single or multiple-award contract?

A36. This is a Requirements Contract. It is a single-award contract.

Q37. If a task order contract, are the prices which are to be submitted with the labor categories not-to-exceed ceiling prices or firm fixed prices for the base and option years?

A37. Firm fixed prices.

Q38. Please confirm that CLIN pricing (SF 1449 continuation sheet) is not required as the level of effort for the work is not defined.

A38. See A26

Q39. What needs to be included in the labor category pricing, besides the labor categories?

Hourly rate only for each category or breakdown of costs? Should it be in Excel format?

A39. See A26

Q40. How should the pricing be provided for the Task Order? Are the labor categories supposed to be rolled up into a monthly fee per the CLIN structure or presented as hourly rates per category?

A40. See A26

Q41. How many administrative staff people are required?

A41. See A4

Q42. Is there a specific clearance required other than a cursory background check (Confidential, Secret, TS)?

A42. See Section 7.0 of the PWS.

Q43. Page 16 of 48 Section B refers to the items to be included in Volume II as i through v. The list concludes at item iv. Is there an Item v?

A43. No. There is no v.

Q44. Page 16 of 48 Section B refers to a page count of 30 single-sided pages in item i (Technical Proposal). Item ii (Task Order One) refers to a page count of 20 pages for a total of 50 pages for Volume II. Is this correct?

A44. Yes

Q45. Are the Past Performance References and the Quality Control Plan included in the page count for Volume II?

A45. See A10

Q46. Is the minimum for past performance references 3 or is it up to 3-5?

A46. See “B” Volume II of Instructions to Offerors.

Q47. The FBO announcement on the FBO website states that questions will be received until 11:00am on July 29. Page 15 of 48 of the solicitation (Instructions to Offerors, Item 2) states that questions will be received until 11:00am Eastern, Friday, July 29. Please confirm the due date of the questions.

A47. Questions will be received until 11:00am on Tuesday, July 29, 2014.

Q48. Page 15 of 48 of the solicitation (Instructions to Offerors, Item 3) states that “All proposal submissions in response to this solicitation must be received no later than 02:00 PM Eastern on Wednesday, August 7, 2014.” August 7 is a Thursday. Please confirm the due date of the proposal.

A48. Proposal submissions are due no later than 02:00pm Eastern on Thursday, August 7, Q49. Will you accept past performance that was obtained as a sub-contractor?

A49. See A7

Q50. How many positions are required for each labor category? What are the labor hours assigned to each position?

A50. See A4

Q51. Are there a number of task orders under this contract with varied expiration dates, or do all start/end at the same time?

A51. Periods of Performance will vary.

Q52. Will the government want a bidder to place an onsite Project Manager for this work or can one of the staff members take a “Lead” role for tasks associated with contract administration?

A52. A “Lead” role would be sufficient for the purposes of this task.

Q53. What are the historical labor categories and hours required under this contract?

A53. See A4

Q54. Will bidders be responsible for providing any office equipment or consumable supplies for use by the administrative staff?

A54. No.

Q55. What was the last award dollar amount for this same effort?

A55. This work was part of a larger requirement. Therefore, this information is not available.

Q56. The PWS indicates that the procured services will support various policy program offices, including identification card policy (Common Access Card) and combatting trafficking in persons? What is the type and LOE of management support as it relates to these policy program offices?

A56

Q57. Attachment C (Task Order One), 4.2.12, makes reference to section 11.0 of the PWS. Can the government provide section 11.0 of the PWS?

A57. The PWS will be revised to reflect Section 11.0.

Q58. The PWS provides that the contractor shall provide all personnel and management necessary to provide required on-site support services. Has the government identified any personnel or management as Key Personnel? If so, does the government wish offerors to provide resumes for any such Key Personnel?

A58. There are no key personnel identified.

Q59. Does the government anticipate that the provision of on-site support services will require an on-site Program Manager or an on-site Program Management Office (PMO)?

A59. See A52

Q60. If the government anticipates the need for an on-site, contractor PMO, does the government anticipate that such a PMO would benefit from the use of Government Furnished Equipment (GFE)?

A60. See A59

Q61. Will on-site personnel and management benefit from GFE?

A61. See Section 8.0 of PWS

Q62. What is the government’s anticipated LOE as it relates to Attachment C (Task Order One)? Will personnel and management performing Task Order One be entitled to Federal Holidays?

A62. See A4. DHRA offices are closed on Federal Holidays.

Q63. With respect to Attachment C (Task Order One), does the government anticipate dedicated administrative support for each of DHRA HQ GC, HR, and PPS, or is the LOE such that dedicated administrative support is not required?

A63. See A4

Q64. With respect to Attachment C (Task Order One), section 2.0 provides that services will include analyst support to further execute the DHRA Privacy Program, and policy program offices, including Common Access Card and combatting trafficking in persons. What is the type and LOE of Task Order One management support as it relates to these policy program offices?

A64. See A56

Q65. With respect to Attachment C (Task Order One), does the government anticipate dedicated administrative support for each of the DHRA Director and DHRA Deputy Director, or is the anticipated LOE for this support such that dedicated personnel are not required?

A65. See A4

Q66. Attachment C (Task Order One), section 4.1.1 provides that administrative personnel will be required to both ensure coverage of the front desk and monitor visitors. Does the government anticipate the availability of government personnel to cover the front desk when contractor personnel are monitoring visitors?

A66. The front desk is located in a manner that will allow for the monitoring of visitors concurrently.

Q67. On Page 47 - PWS 4.2.12 says “Implement the DHRA Privacy Program (section 11.0 of PWS).” There is no Section 11 of the PWS. What section should this be?

A67. See A57

The following have been modified:

ADDENDUM TO 52.212-1

INSTRUCTIONS TO OFFERORS

OFFERORS SHOULD NOTE THE FOLLOWING IMPORTANT INFORMATION

REGARDING PROPOSAL SUBMISSION:

1. SAM: Any Offeror that submits a proposal in response to this solicitation must be registered in the System for Award Management (SAM), in accordance with FAR Clause 52.232-33 and DFARS Clauses 252.201-7000 and 252.204-7004 Alt A, prior to contract award. Registration information can be found at: https://www.sam.gov/portal/public/SAM/.

2. Communication: Solicitation information and amendments will be posted to the Federal Business Opportunities website at www.fbo.gov. Offerors may email written questions requesting clarification of the Request for Proposal (RFP) to the Contract Specialist, Michael White, at: michael.l.white36.civ@mail.mil. No information concerning this solicitation or https://www.sam.gov/portal/public/SAM/ http://www.fbo.gov/ requests for clarification will be provided in response to telephone calls. Questions will be received up to 11:00 AM Eastern on Tuesday, July 29, 2014. Questions received after this time and date may not be answered.

3. Proposal Submissions: All proposal submissions in response to this solicitation must be received no later than 02:00 PM Eastern on Thursday, August 7, 2014. No electronic submissions will be accepted. Submit proposals to the address below:

DHRA PSO

Attn: Michael White Solicitation No. H98210-14-R-0030 4800 Mark Center Drive, Suite 07G12 Alexandria, VA 22350

NOTE: If hand delivering proposal, contact the Contract Specialist via email at least two business days prior to the due date for delivery instructions.

Proposal: Proposals shall be submitted in three separate volumes as follows:

A. VOLUME I – Business: Offerors shall submit one hard copy of Volume I. This volume shall include:

i. Signed copy of the Standard Form 1449, with blocks 17 and 30 completed.

ii. Signed copy of the Standard Form 30 of any amendments issued against this RFP.

iii. Offeror’s DUNS number, Cage Code, and Tax ID number.

iv. Completed Representations and Certifications of Offeror (FAR Clause 52.212-3 Alt I).

v. All fill-in clauses that require an offeror’s response.

B. VOLUME II – Technical: Offerors shall submit one original and three hard copies of

Volume II. This volume shall include items i-v below.

i. Technical Proposal: This section shall address the technical requirements of the base Performance Work Statement (PWS) and Evaluation Factors (Attachment A). The total page count for this volume shall not exceed 30 single-sided pages.

ii. Task Order One: Attached to this solicitation is a task order (Attachment C) of work to be completed under 4.0 of the Task Order PWS. Offerors shall submit a technical proposal addressing the requirements of the Task Order at Attachment C. The task proposal shall not exceed 20 pages.

iii. Past Performance References: Offerors shall submit 3 to 5 relevant and recent past performance references utilizing the Past Performance Relevancy Questionnaire (PPRQ) at Attachment B. Complete and submit one PPRQ per reference.

iv. Quality Control Plan (QCP). Offerors shall provide a Plan in accordance with the

PWS.

C. VOLUME III – Price Proposal: Offerors shall submit one hard copy and one CD- ROM of Volume III. This volume shall include

i. Offerors shall provide the labor categories proposed for completing the tasks of this requirement, for the Base and all Option Periods. Each labor category proposed for this contract shall be clearly defined.

ii. Task Order Pricing: Offerors shall submit a price proposal for the task and be annotated to the corresponding attachment (Attachment C). Pricing for each CLIN shall include labor categories and hours.

iii. A completed Schedule for the Base and all Option years. The Schedule shall reflect per unit pricing by CLIN. All items listed in the Schedule must have a price, or be marked “NSP” for “Not Separately Priced” or “NC” for “No Charge.”

ATTACHMENT A

EVALUATION FACTORS

1.0. INTRODUCTION.

1.1. The Government will evaluate all proposals in accordance with the factors and criteria established in the Source Selection Plan (SSP) and in this Request for Proposal (RFP). The criteria provide the basis upon which each evaluation will be based, are established before receipt of the proposals, and are intended to ensure that the evaluation will be a structured process employing equitable measures. Proposals will be evaluated and a contract awarded under the Best Value Continuum approach, to the responsible Offeror whose offer is considered the most advantageous to the Government, price and other factors considered.

1.2. The Government intends to evaluate proposals and make award without discussions. The Government reserves the right to conduct discussions if the Contracting Officer later determines discussions to be necessary.

1.3 Offerors are cautioned that “parroting” of the PWS with a statement of intent to perform does not reflect understanding of the requirement or capability to perform.

2.0. EVALUATION FACTORS

2.1. Technical.

2.1.1. The purpose of the technical factor is to assess the offeror’s proposed approach, as detailed in its proposal, to satisfy the Government’s requirements. There are many aspects which may affect an offeror’s ability to meet the solicitation requirements to include technical approach, risk, management approach, personnel qualifications, small business participation and others. The evaluation of risk is related to the technical assessment.

2.1.2. Risk assesses the degree to which the offeror’s proposed technical approach for the requirements of the solicitation may cause disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Risk will be assessed as one aspect of the technical factor rating.

2.1.3. Any proposal receiving a rating of “Unacceptable” is deemed to have a risk that is so high that award cannot be made against the proposal and the proposal will not be further evaluated.

2.2. Past Performance.

2.2.1. The Past Performance Evaluation results in an assessment of the offeror’s probability of meeting the solicitation requirements, based on past performance information. The Performance Confidence Assessment rating is assessed as an overall factor after evaluating aspects of the offeror’s recent past performance, focusing on performance that is relevant to the technical factors and cost or price.

2.2.2. Recency refers to the state or quality of being current. The more recent the contract, the greater the likelihood that the offeror has the capacity to perform in a like manner. Information regarding contract performance that is recent and has a logical connection with the matter under consideration indicates relevancy.

3.0. EVALUATION FACTOR CRITERIA

3.1. Criteria for Technical Factor

Element A: Technical Approach and Methodology

By addressing each portion of the PWS, proposals shall describe the offeror's understanding of the requirement, assessment of the objectives to be accomplished, methodology for accomplishing the requirement.

Element B: Project Management Plan

The proposal shall describe the offeror’s approach for providing complete program management support that will fully integrate, manage, control, and document all phases of the contract requirements. Proposals shall describe the project management and staffing plans and demonstrate the offeror’s approach for providing the corporate resources necessary to ensure and maintain service quality levels, staffing levels, training and risk management.

Element C: Quality Control Plan

The proposal shall describe the Offeror's approach for instituting and maintaining a capability to ensure the quality and integrity of services/products, including at least: (1) management and task controls to assure work will be completed as required; (2) contingency plans for identifying and correcting problems; (3) and steps that would be taken to assure timely delivery of quality products.

Element D: Task Order One

The Government will evaluate the offeror’s Task proposal technical approach for completeness, specificity, clarity, and to determine the offeror’s understanding of, and ability to successfully accomplish, the requirements of the Task PWS.

3.2. Criteria for Past Performance Factor Confidence Assessment The Government will conduct a performance confidence assessment based upon the past performance of the offerors performing major or critical aspects of the requirement as it relates to the probability of successfully performing the solicitation requirements.

3.2.1. The Government will consider each offeror’s demonstrated, current, relevant record of performance in supplying products and services that meet the contract’s requirement. Contracts completed within the last five years are generally considered recent. This can vary by the requirement; for example, recent for IT services could be within past two years since technology changes rapidly. Three to five years may be suitable for analytical analyses/reports.]

3.2.2. In conducting the performance risk evaluation, the Government may use data provided by the offeror and data obtained from other sources it considers current and accurate, including the Past Performance Information Retrieval System (PPIRS).

3.3. Criteria for Price Factor. The Government anticipates that adequate price competition will establish a fair and reasonable price. However, if the Government does not receive adequate price competition, it will evaluate price proposals to ensure price reasonableness of the services being provided to the Government, considering the specific terms and conditions and relevant commercial practices.

4.0. ORDER OF IMPORTANCE.

4.1. Proposals will be evaluated based on best value to the Government using the trade-off approach. For this solicitation, factors are listed below in descending order of importance.

Price will be evaluated separately and will not be scored.

1. Technical

2. Past Performance

3. Price

4.2. Technical and Past Performance, when combined, are significantly more important than cost or price;

5.0. RATING METHODS

5.1. Technical Factor: One of the following ratings will be assigned:

TECHNICAL RATINGS

Rating Definition Outstanding The proposal exceeds stated requirements, as reflected through an innovative, comprehensive, outstanding approach. The response is complete in terms of the basic content and level of information the Government seeks for evaluation. There is a high probability of success and minimal risk that this Offeror would fail to meet the quantity, quality, and schedule requirements. Minor weaknesses, if any, need not be corrected to make award.

Acceptable The proposal meets the stated requirements. The response is considered complete in terms of the basic content and level of information the Government seeks for evaluation. There is a reasonable probability of success and little risk that this Offeror would fail to meet the quantity, quality, and schedule requirements. Minor weaknesses, if any, may not need to be corrected to make award.

Marginal The proposal does not clearly meet the requirements and has not demonstrated an adequate approach and understanding of the requirements.

The proposal has one or more weaknesses which are not offset by strengths.

Risk of unsuccessful performance is high.

Unacceptable The proposal fails to meet the stated requirements. The response is considered deficient in terms of basic content and level of information the Government seeks for evaluation. The degree of risk is so high that an award cannot be made against the proposal. Any proposal receiving this rating will not be further evaluated.

5.2. Past Performance Factor – Relevancy and Confidence Assessment:

5.2.1. One of the following Relevancy ratings will be assigned:

PAST PERFORMANCE RELEVANCY RATINGS

Rating Definition Very Relevant Present/past performance effort involved essentially the same magnitude of effort and complexities this solicitation requires.

Relevant Present/past performance effort involved much of the magnitude of effort and complexities this solicitation requires.

Somewhat Relevant

Present/past performance effort involved some of the magnitude of effort and complexities this solicitation requires.

Not Relevant Present/past performance effort did not involve any of the magnitude of effort and complexities this solicitation requires.

5.2.2. The combination of relevancy and recency, and performance documented by the information collected by the Government, results in the selection of a performance confidence assessment as outlined below.

PERFORMANCE CONFIDENCE ASSESSMENTS

Rating Description Substantial Confidence

Based on the offeror’s performance record, the Government has a high expectation that the offeror will successfully perform the required effort.

Satisfactory Confidence

Based on the offeror’s performance record, the Government has an expectation that the offeror will successfully perform the required effort.

Limited Confidence

Based on the offeror’s performance record, the Government has a low expectation that the offeror will successfully perform the required effort.

No Confidence Based on the offeror’s performance record, the Government has no expectation that the offeror will successfully perform the required effort.

Unknown Confidence

No relevant performance record is available or the offeror’s performance record is so sparse that no meaningful confidence assessment rating can be reasonably assigned.

5.3. Price Factor: Price proposals will not be rated.

PERFORMANCE WORK STATEMENT

Defense Human Resources Activity Administrative and Management Support Services

1. INTRODUCTION

The Defense Human Resources Activity (DHRA) Headquarters (HQ), requires administrative and management support to meet requirements specifically within its various offices including the DHRA HQ General Counsel (GC), Business Enterprise & Human Capital Office (BEHCO), and Policy and Program Support (PPS) team.

2.0 BACKGROUND

As established by DoD Directive 5100.87, “Department of Defense Human Resources Activity,” DHRA supports policy development performing cutting-edge research and expert analysis, supports readiness and departmental reengineering efforts, manages the largest automated personnel data repositories in the world, prepares tomorrow’s leaders through robust developmental programs, supports recruiting and retaining the best and brightest, and delivers both benefits and critical services to warfighters and their families. This effort enables DHRA HQ and its components to consolidate like efforts.

These services will support various offices within DHRA HQ to better meet its mission requirements, including: overall administrative support, analyst support to further execute the DHRA Privacy Program, and policy program offices, including identification card policy (Common Access Card) and combatting trafficking in persons.

3.0 SCOPE

The contractor shall provide all personnel and management necessary to provide required on-site support services to the Defense Human Resources Activity, Headquarters, to further execute the DHRA Privacy Program, policy program offices, including identification card policy (Common Access Card), combatting trafficking in persons, and performing administrative support for various DHRA leaders and staff, including the DHRA Director, Deputy Director and General Counsel (GC) as detailed within this PWS.

4.0 Administrative Support

4.1 Duties include general administrative support such as preparing a variety of correspondence, reports, presentations, disseminating information, managing reception areas, ensuring front desk coverage, managing and processing incoming and outgoing mail, maintaining conference room and management calendars, office supply inventory and visitor parking requests.

4.1.1 Records Management: Records Management Services include on-site services, organizing paper or electronic files in any work area and tracking them electronically, information and document indexing, scanning, labeling, bar coding, and filing

4.2 Management/Program Analyst Support

4.2.1 The Contractor shall provide analyst support to DHRA’s Privacy Program. Functions include evaluation of technical and privacy program related policies and procedures;

comprehensive research regarding current DoD and Federal Privacy-related policies and regulations and applicable laws and statutes; communicating program requirements;

participating in and organizing various working and decision-making groups and committees;

and coordinating the updates of applicable DHRA policy and operational program management offices.

4.3 Participate in a Post-Award Conference.

4.3.1 This meeting shall provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting shall provide the opportunity to discuss technical, management and security issues. The Post Award Conference will aid both the Government and Contractor in achieving a clear and mutual understanding of all requirements, and identify and resolve any potential issues. The Contractor shall be prepared to discuss any items requiring clarification and gather information as necessary to support each deliverable. The Contractor shall provide a written summary of the Post-Award Conference.

5.0 DELIVERABLES

Deliverable PWS Ref. Delivery Date Post Award Conference 4.3.1 Within 5 days after contract award.

Deliverable PWS Ref. Delivery Date Post Award Conference Minutes 4.3.1 Within 3 business days of post award.

Contractor Manpower Reporting 6.0 NLT Octorber 31st

6.0 CONTRACTOR MANPOWER REPORTING

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for DHRA via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil

7.0 SECURITY

Contractor and all Contractor personnel with access to or responsibility for nonpublic Government data under this contract shall comply with DoD Directive 8500.1- Cybersecurity, DoD Instruction 8500.2 Information Assurance (IA) Implementation, DoD Directive 5400.11 DoD Privacy Program, DoD 6025.18-R DoD Health Information Privacy Regulation, DoD 5200.2-R Personnel Security Program, and Homeland Security Presidential Directive (HSPD) 12.

7.1 Contractor shall establish appropriate administrative, technical, and physical safeguards to protect any and all nonpublic Government data to ensure the confidentiality, integrity, and availability of government data.

7.2 Contractor personnel with access to or responsibility for nonpublic Government data under this contract must comply with HSPD-12 Personal Identity Verification (PIV) issuance requirements, known as the Common Access Card (CAC) for DHRA and must:

7.2.1 Be CAC or PIV ready prior to reporting for work. At minimum all Contractor personnel must obtain/maintain a favorable FBI National Criminal History Check (fingerprint check), two forms of identity proofed identification (I-9 document), and submit a National Agency Check with inquiries (NAC-I) vetting package for processing.

7.2.2 Be citizens of the United States.

7.2.3 Maintain favorable FBI National Criminal History checks and ensure completion and successful adjudication of a NAC-I as required for Federal employment.

http://www.ecmra.mil/ http://www.ecmra.mil/

7.2.4 If at any time, any Contractor person requiring a CAC is unable to obtain/maintain an adjudicated NAC-I, the Contractor shall immediately notify the DHRA HQ Contracting Officer Representative (COR) to coordinate removal of such a person from work under this contract.

7.3 The Contractor shall report immediately to the DHRA HQ Privacy Office and secondly to the COR discovery of any Privacy breach.

8.0 GOVERNMENT FURNISHED PROPERTY/EQUIPMENT/INFORMATION

(GFP/GFE/GFI)

The Government will provide contractor personnel with workstations, government facilities and equipment as well as workspace in the DHRA HQ office in Alexandria, VA.

9.0 QUALITY CONTROL

The contractor shall implement and maintain a Quality Control Plan (QCP) to ensure work performed conforms to the scope of work and meets the requirements under this PWS. The QCP shall, at a minimum provide a method for performing inspections; identifying, correcting and preventing problems/defective service; addressing customer complaints, and improving the quality of services over the life of the contract.

10.0 QUALITY ASSURANCE

10.1 The Government reserves the right to perform inspections and surveillance to evaluate the Contractor’s compliance to the contract terms and performance of the requirements in the PWS. The Government will make every effort to ensure that the surveillance methods described below are conducted in an objective, fair, and consistent manner.

10.2 Periodic Surveillance. This action occurs when the COR or other Government official observes a deficiency. Examples include evidence from accidents, incidents, or delays.

Regardless of where in the line-of-duty the COR observes contractual procedures not being followed, he/she has an obligation to document and report the deficiency to the Contracting Officer.

10.3 Customer Complaint Surveillance. This action is instituted when the COR receives a complaint from a stakeholder regarding contractor service. The COR will obtain the complaint in writing and then conduct an investigation to determine its validity. If the complaint is deemed valid, the COR will immediately notify the contracting Officer for action. The COR will notify both the Contract Manager and the complainant of the Government’s response to their complaint.

10.4 Contract Discrepancy Report (CDR). In the event of unsatisfactory contractor performance, the COR or CO will issue a CDR that will explain the circumstances and findings concerning the incomplete or unsatisfactory service. The contractor shall acknowledge receipt of the CDR and respond in writing as to how he/she shall correct the unacceptable performance and avoid a recurrence. The Government will review the contractor's corrective action response to determine acceptability and will use any completed CDR as part of an overall evaluation of Contractor performance when determining present or future contractual actions.

11.0 APPLICABLE DOCUMENTS

Document Web link DHRA Privacy Program http://www.dhra.mil/webfiles/docs/Privacy/DHRA_Pr ivacy_Program.pdf

(End of Summary of Changes)