Section_L.pdf

UNCLASSIFIED

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents

1.0 Program Structure and Objectives

The objective of the United States Air Force (USAF) Special Access Program (SAP) Security Support Services (SSS) contract is to assist the USAF cognizant security authority in oversight of enhanced national security objectives supporting USAF SAP interests. This objective is accomplished through active and integrated security operations, processes, mechanisms, and management. This support shall provide multi-disciplinary security support, including specialized analytical/program protection support, while being responsive and flexible to dynamic SAP security situations.

In addition, the contractor is required to provide a proactive management structure that shall continuously evaluate and implement opportunities for improving recruitment and retention goals. These improvements shall enhance overall service delivery while realizing efficiencies.

To motivate improved performance, provide timely feedback, and emphasize key areas of management concern in critical areas, the contract will contain an incentive fee clause that will focus on the following factors:

• Staffing

• Security Incidents

• Special Interest Items

Access to the incentive fee pool can only be obtained after the corresponding cost and vacancy control gate criteria are met.

The Government intends to award multiple, Indefinite Delivery Indefinite Quantity (IDIQ) awards. These awards will be Cost-Plus-Fixed-Fee contracts with cost reimbursement for Other Direct Costs (ODCs), for work described in the Performance Work Statement (PWS) and attachments to this solicitation.

The Government also intends to award multiple Task Orders (TOs) to one (1) or more awardees from the resultant IDIQ contracts.

The Government reserves the right to award less than the anticipated number of IDIQ contracts and/or task orders if offers received do not meet the Government requirements.

2.0 General Instructions

(a) Offeror’s proposals (unless otherwise specified means both the basic contract proposal and TO proposals) shall include all data and information requested by this Instruction to Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with requirements as stated in the PWS, Contract Data Requirements List (CDRL), Model Contract, and other attachments listed in Section J. Non-conformance with instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and substantiation of the validity of stated claims. The proposal shall not simply rephrase or restate Government requirements; instead it shall provide convincing rationale to address how the Offeror intends to meet the requirements. Offerors shall assume the Government has no prior knowledge of their structure, capabilities, or experience, and will base its evaluation on information presented in the Offeror’s proposal. Cost and/or price impacts cited in the Technical Volume shall be captured, identified, and accurately reflected in the Cost/Price Volume.

(c) Elaborate brochures or documentation, detailed art work, or other embellishments are unnecessary and are not desired.

(d) The proposal acceptance period is specified in Section A of the contract/solicitation;

the Offeror shall make a clear statement that the proposal is valid through the specified date.

(e) Upon receipt, all proposals become government property, and subsequent to award, all copies, except those required for official purposes, shall be destroyed. Additionally, in accordance with FAR Subpart 4.8, Government Contract Files, the Government will retain one copy of all unsuccessful proposals.

(f) Non-Government Advisors: Non-Government advisors will not be used for this source selection effort.

(g) The Government reserves the right to not award a contract at all, depending on the quality of proposals, availability of funding, and continued existence of the requirement.

(h) The Government may elect to award to only one Offeror should all other Offerors not meet the minimum criteria for award (Technically Acceptable, Low Risk, Acceptable Small Business Plan).

2.1 General Information

2.1.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Offerors must address any questions or concerns to the CO. Unclassified requests for clarification may be sent to the CO at the physical and/or email addresses located in Section A of the contract/solicitation. Classified requests for clarification shall be coordinated by phone at the number located in Section A of the contract/solicitation.

2.1.2 Debriefings

The CO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505 and/or FAR 15.506. Offerors excluded from the competitive range may request a pre-award debriefing, or they may request a delay of the debriefing until after award; Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.503 (b).

2.1.3 Discrepancies

If an Offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the CO in writing with supporting rationale, as well as the remedies the Offeror is asking the CO to consider as they relate to the specific error or omission. The CO will make the final determination for discrepancy determination and potential corrective actions, if any. Offerors are reminded that the Government intends to award this effort based on the initial proposal, as received, without discussion.

2.1.4 Electronic Reference Documents

All documentation provided with the RFP will be provided in an electronic format. Any and all reference material identified in the PWS may be found at applicable publishing website. The Government will not provide copies of these publications unless the Offeror is prohibited from accessing the publishing websites.

2.1.5 Communications

Exchanges of source selection information between Government and Offerors will be controlled by the CO. All comments and questions must be submitted IN WRITING. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject Line. In order to facilitate sending and receiving of encrypted emails, Offerors must use Microsoft Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information).

Otherwise, source selection information will be transmitted via secure fax, United States Postal Service, FedEx, or via an Offeror’s representative.

2.1.6 Terminology Guidance

Throughout the source selection the Government will utilize the terms contract award, basic contract award, basic contract, base contract award, base contract, and contract interchangeably to refer to the basic IDIQ contract. References to the TOs will always include the term Task Order or TO. A TO Suite is a group of one or more TO awarded to a single Offeror.

2.2 Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 below). Titles and contents of the volumes shall adhere to requirements of Table 2.2. Volumes identified in the table shall be separately bound in individual three-ring, loose-leaf binders.

Binders for Volumes I & II may be combined. The contents of each proposal volume are described in the ITO Paragraph as noted in the following table:

Table 2.2 - Proposal Organization

VOLUME ITO Para.

Number VOLUME TITLE COPIES

(Electronic/Hard)

PAGE

LIMIT

I 3.0 Executive Summary 1/1 4

II

4.0 Technical Approach

1/2

4.6.1 Tab 1: Program

Management Plan 25

4.4.2 & 4.6.3

Tab 2: Resumes and Letters of Intent No Limit

4.4.3 Tab 3: Professional Employee Compensation Plan

1/2 20

III 5.0 Cost/Price 1/2 No Limit

IV 6.0

Contract Documentation (Completed Sections A-K & Subcontracting Plan)

1/2 No Limit

*Electronic copies of all volumes may be submitted together on a single CD/DVD; however, two (2) sets of media shall be submitted.

2.2.1 Page Limitations

Page limitations shall be treated as maximums and are identified in Table 2.2, above. Page limitations exclude the title page, cover sheets, table of contents, tabs, L-1 Resumes, letters of intent, glossary of abbreviations and acronyms, subcontractor/teaming partner consent letter, L- 4 Unburdened Labor Rate Matrix, and L-3 Cross-Reference Matrix. When both sides of a sheet display printed material, it shall be counted as two (2) pages. If the government elects to open discussions, page limitations may also be placed on responses to Evaluation Notices (EN(s)).

The specified page limits for EN responses will be identified in the letters forwarding the EN(s) to the Offerors. If proposal or EN page limitations are exceeded, excess pages will not be read or considered in the evaluation of the proposal and excess pages will be removed from the back of the proposal volume and destroyed by the CO.

2.2.1.1. Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. Proposals shall use both sides of a sheet and shall be counted as two pages with the exception of foldouts which shall be printed on one side and shall count as one page. Partial pages count as a full page for page limitation purposes. Duplexing shall be done by using the print on long side format. Page size shall be 8.5 by 11 inches, not including foldouts. Font shall be Times New Roman single spaced and text size shall be no less than 12-point, except for items identified in

2.2.1.1 (b). Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume using the “Page x of y” format. These page size and format restrictions shall also apply to EN responses.

(b) Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layouts, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and shall count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than:

Art: 10-point Tables: 10-point Titles: 10-point, bold

These limitations apply to both electronic and hard copy proposals. No pen-and-ink changes are allowed.

(c) Typesetting, font compression, and other techniques to reduce character size or spacing are not permitted, and shall be considered a deliberate attempt to circumvent page limitations. As a result, Offeror’s proposal may be removed from the competition and receive no further consideration.

2.2.2 Cost or Pricing Related Data

All cost or pricing data shall be addressed in the Cost/Price Proposal and Contract Documentation Volumes. Cost information and work hour estimates may only be used in other volumes as appropriate for presenting rationale for alternatives and trade-off decisions.

Cost or price information shall be submitted using appropriate Microsoft Office Excel version applications. Do not use the Macintosh version of these programs. Numerical pricing data shall be submitted using Microsoft Excel 2010 (or earlier version).

2.2.3 Classified Information

Where classified information is required in your response, it shall be provided as a classified supplement and bound in a classified addendum. Each entry in the classified addendum shall reference the proposal volume, page number, and paragraph number to which it applies.

Similarly, a reference shall be placed in the unclassified volume where the classified insert applies, giving the page and paragraph numbers within the addendum where it can be found.

Binding shall conform to the same directions as those given in this ITO for unclassified portions. The classified addendum shall be separately bound with an applicable security designation color cover, conforming to the DD Form 254 and the Security Classification Guide provided in this solicitation. Pages in a classified addendum will be included in the page count for the applicable volume.

The Offeror shall be financially responsible for damage(s) caused by incorrectly classifying or marking classified information that subsequently contaminates a government network.

2.2.4 Table of Contents, Cross-Reference Matrix, and Indexing Each volume shall contain a detailed table of contents and include a listing of the section titles, subsection titles, paragraph, and subparagraph titles. Page numbers for each title must be indicated. Tab indexing shall be used to identify sections.

Each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Evaluators may utilize information across factors and subfactors to confirm consistency and compatibility throughout the Offeror’s proposal (e.g., the proposed Subfactor 3 staffing shall not contradict what is proposed in the Subfactor 2 Contractor Program Management Office (CPMO)).

The Offeror shall fill out the Solicitation Cross-Reference Matrix at Attachment L-3 of this ITO indicating the proposal reference information as it relates to the ITO, PWS Paragraphs, Contract Line Item Number(s) (CLINs), evaluation criteria, and CDRL references found therein.

Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

2.2.5 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. All acronyms shall be defined at first use within a document. Glossaries do not count against the page limitations for their respective volumes.

2.2.6 Binding and Labeling

Each volume of the proposal (Volume I & II may be combined) shall be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open without pages becoming torn or unbound. When lying in the flat open position, the binding shall be sufficient to allow easy turning of pages without pages being torn, mangled, or unbound due to binding.

Hole reinforcements are encouraged for large volumes to prevent pages from falling out.

Staples shall not be used. A cover sheet shall be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror’s name. The same identifying data shall be placed on the spine and outside cover of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), “Restriction on disclosure and use of data,” and FAR 3.104- 4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Tab indexing shall be used to identify every section within each volume.

2.3 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. All electronic copies must be submitted on Compact Disk (CD) or Digital Video Disk (DVD). For electronic copies, indicate on each CD and jewel case, the Offeror name, classification, volume number, and title. The offer shall use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. Offerors shall use proper heading format to allow ease of navigation within each document. The Offeror shall submit all Volumes in electronic format, using write-protected CDs or DVDs. Each volume shall be in a different directory on the CD. Submitted files shall not be in any compressed format (e.g. .zip).

Electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2010, MS Office Excel 2010 and MS Office Power Point 2010, as applicable (do not use Apple/Mac versions of these programs). There shall be no licensing or other limitations that would inhibit creation of additional electronic copies if necessary. If there are any discrepancies between hard copies and electronic copies of a proposal, the electronic copies will be used for evaluation. Use of Universal Serial Bus (USB) storage devices are not authorized.

Offerors shall submit both hard and electronic copies to satisfy delivery requirements. Offerors shall virus scan all electronic submittals prior to submission and mark each CD and jewel case with a certification that it has been scanned for and is free from all viruses, malware, and tracking software. All open secessions shall be closed on the CD prior to delivery. Offerors shall remove or disable macros and external links, but retain all computational functionality and embedded formulas.

2.3.1 File Naming Conventions

The files shall be named in an unambiguous manner using plain text language to facilitate evaluator’s ease of understanding. File names should begin with the security classification of the file. Offerors shall insert the corresponding file name in the footer of each document. All media must be labeled as follows:

• Offeror Name

• Program Name

• Solicitation Number

• Date of Proposal Submission

• Proposal Volume Number and Name

• Classification Level (Unclassified media must be marked “Unclassified”)

• Disc/CD Number (e.g. “1 of 3”)

Subcontractor media submissions, if provided, shall be labeled with the same information listed above, and shall also include the name of the prime Offeror.

2.3.2 Multimedia and Graphics

Offerors shall not embed sound or video files into their proposal volumes. The evaluation system does not have the capability to read such files.

Graphics that are embedded into volumes shall be kept as simple as possible. Complex graphics take much longer for the system to display, which can impede scrolling through the document.

Scanned images shall be avoided.

2.3.3 Hyperlinks

The table of contents, including heading(s) and sub-heading(s), of the electronic proposal shall be hyperlinked to the corresponding material within each proposal volume such that “clicking” the mouse on an item in the table of contents will take the reader to the corresponding section within the body of the proposal volume. Any reference in the volume that refers the reader to another location within the volume shall be hyperlinked in the same manner.

2.4 Proposal Delivery Schedule

All proposal information shall be delivered not later than 3:00 PM, Mountain Daylight Savings Time “MDST” on October 4, 2019 to the address indicated below. Offerors who do not meet the following delivery deadlines may be excluded from the competition and their proposals may not be accepted.

2.4.1 Distribution

The "original" proposal shall be identified for all submittals. Proposals shall be mailed or hand carried to the CO as defined below.

Offerors shall submit both hard and electronic copies to satisfy delivery requirements.

2.4.1.1 Mailed Proposals

Address the outer envelope or wrapping of the offer to the following address:

AFTC/SMO

ATTN: Robert Maughan 6082 Fir Avenue, Bldg. 1232 Hill AFB, UT 84056

Offerors are responsible for ensuring mailed proposals containing classified information are packaged and mailed in accordance with applicable procedures/regulations.

Failure to mark submissions accordingly could cause the Offeror’s proposal to be misdirected and received at the required destination after the stated deadline. Misaddressed proposals shall be considered not received. At delivery, the Offeror shall indicate the proposal is source selection sensitive and for official use only, and shall be handled accordingly during the source selection process.

2.4.1.2 Hand-Delivered Proposals

Proposals may be hand-delivered during normal business hours. Offerors shall call Mr. Robert Maughan at (801) 586-6529 (non-secure) at least 48 hours, two business days, in advance to arrange for drop-off at the appropriate facility. The Government may further restrict proposal delivery and receipt to certain day/time periods. It is the responsibility of the Offeror to obtain any necessary security approvals to hand-carry and deliver the proposal as necessary. The Government assumes no responsibility for late delivery caused by inadequate coordination on the part of the Offeror. Offerors shall ensure all couriers of classified information have the appropriate training and hand-carry certification credentials. Proposals shall not be submitted by facsimile.

Note: Do not distribute proposal information in response to this RFP to any other person or agency without the written permission of the CO listed above.

3.0 Volume I - Executive Summary

The Executive Summary shall present an overview of the Offeror’s proposal. An effective Executive Summary shall function as a proposal roadmap and help the Government evaluator understand the Offeror’s overall approach to satisfying the requirements of the RFP. The Executive Summary shall highlight proposal capabilities that make the Offeror uniquely qualified to perform the effort. The Executive Summary is for informational purposes only and will not be evaluated by the source selection team.

3.1 Narrative Summary

The narrative summary of the entire Offeror’s proposal shall be concise, to include highlighting any key or unique features, excluding cost/price. Salient features shall tie in with Section M Evaluation Factors/Subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.2 Table of Contents

The Executive Summary shall include a master table of contents of the entire proposal.

4.0 Volume II - Technical Volume

4.1 General

The Technical Volume shall be specific and complete. Legibility, clarity, and coherence are important. Your responses will be evaluated against Technical Subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2 Cross Reference Matrix

The Offeror shall complete the cross reference matrix for their proposal using the template provided in L-3 – Cross Reference Matrix. If this matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over this matrix. Additionally, to the extent this matrix discloses details as to the extent or manner by which the Government intends to evaluate Offeror’s proposals for award, Section L references in the matrix are for information purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of Section M of the solicitation.

4.3 Format and Specific Content

4.3.1 Technical Capability

In the Technical Volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor. Offerors should clearly specify which technical capabilities are unique to an individual TO or Suite of TOs.

4.3.2 Technical Volume Organization

Volume II shall be titled “Technical Volume”. The Technical Volume shall be organized as follows:

(1) Table of Contents

(2) List of Tables and Drawings

(3) Glossary

(4) Cross Reference Matrix

(5) Subfactor One – Transition

(6) Subfactor Two – Contractor Program Management Office (CPMO)

(7) Subfactor Three – Staffing

Technical Volume Attachments are separate appendices numbered as follows:

(Tab 1) Program Management Plan (PMP) (Tab 2) Workload Distribution Matrix (Tab 3) Key Personnel Resumes and Letters of Intent (L-1) (Tab 4) Unburdened Labor Rate Matrix (L-4)

4.4 Technical Subfactors

4.4.1 Subfactor One – Transition

The Offeror shall submit a Transition Plan that meets PWS 2.2.1 requirement (see CDRL *006 for formatting and content) for both incoming transition and outgoing transition. The Transition Plan shall include a complete, annotated outline of the content as defined in the CDRL that will accomplish the transition in time for complete initial performance of any and all potential TOs.

The incoming plan shall include:

- Timeline for bringing all personnel onto the TO, meeting administration, security, and job related preparation requirements.

o Qualified key personnel available and ready upon start of transition.

o Non-key personnel available and ready by start of performance of any and all potential TOs.

- Plan to assume responsibility for each task at all locations required by TOs.

- Identify efforts made to ensure no degradation or break in service throughout transition periods.

- Management approach to monitor and control the transition.

- Approach for communicating the status of transition to customer(s).

- Approach for identifying and managing transition risks and issues.

- Contingency plan to address identified risks.

- Detailed Integrated Master Schedule of key transition events.

The Offeror shall describe the outgoing plan to transfer responsibility for each PWS requirement from the incumbent contract/TO to a new TO, to include monitoring and controlling transition activities, and key transition events to ensure continuity of work to the new TO. The plan shall include:

- Executable timeline for transitioning personnel off of the TO and meeting administration, security, and job related preparation requirements. Plan to transfer responsibility for tasks at all required locations.

- Efforts made to ensure no degradation or break in service throughout transition periods.

- Management approach to monitor and control the transition.

- Approach for communicating the status of transition to the customer.

- Approach for identifying and managing transition risks and issues.

- Contingency plan to address identified risks.

- Detailed Integrated Master Schedule of key transition events.

Situation(s) shall include identification of relevant factors that contributed to success and provides a rationale for measures taken to achieve them.

4.4.2 Subfactor Two – Contractor Program Management Office (CPMO) Offerors shall explain their Program Management Approach (PMA). Provide clear and realistic supporting rationale and explanation(s). Within the PMA Offerors shall address the following:

1. Organizational Structure Provide a detailed top to bottom organizational structure for the entire SSS enterprise, including any and all TOs, to include interrelationships between all entities. PMA shall allow for scalability should the offer be awarded one or more TOs. The organizational structure shall also include the number of personnel, skill mix, and labor hours that would apply to any and all applicable TO mixes.

2. Organizational Narrative Offerors shall include a descriptive narrative of the organizational structure with supporting rationale for the number of personnel, skill mix, and labor hours.

3. Program Management Oversight Describe how the program manager(s) will maintain visibility, quality, and control over all potential TO combinations. This description shall also include oversight of subcontracted workload.

4. Key Leadership/Management Identify all key leadership and/or management positions included in the PMA. For each individual identified, the Offeror shall provide: 1) rationale for the position being designated as key, 2) roles and responsibilities of the position, 3) minimum qualifications (education and expertise) for each position, and 4) resumes for all identified key personnel. For all positions identified as key the Offeror shall submit a resume and letter of commitment in from the individual in Tab 3 stating that they will perform in the assigned position for at least the transition period and first year of contract performance. Submittal shall demonstrate that these key personnel currently hold, or can obtain necessary security clearances in time for transition.

4.4.3 Subfactor Three – Staffing

Offerors shall describe in detail their approach to staffing all required positions (PWS 1.2.2 and Attachment VI), with the assumptions and rationale for the approach.

Offerors shall present the following staffing elements:

SAP Personnel Management

- Submit a Program Management Plan (PMP) as Tab 1 in accordance with CDRL *005 and Section L, 4.6.1, which demonstrates an understanding of global SAP personnel management, SAP-specific security personnel requirements, position disciplines, and PMP updates described in PWS 3.1.

- Describe in your staffing approach a logical, complete and effective staffing profile that outlines planning, selection, processing, and placement of personnel, ensuring all personnel meet PWS qualification requirements.

- Describe your approach for obtaining the requisite security clearances for initial and sustained staffing.

- The Offeror shall describe the concept of how your team, including subcontractors and partners, will fulfill workload requirements. This shall be identified in the Workload Distribution Matrix, submitted as Tab 2. The submission shall include positions identified in PWS, Attachment VI. All proposed personnel shall be identified by payee, position number and location with proposed prime or subcontractor assignments. The matrix shall also include proposed labor and positions for all management positions internal to the Offeror.

- Describe the concept for meeting complete staffing requirements as identified in PWS 5.1.2.

- Describe an executable approach to staff requirements in foreign countries that considers policies, procedures, timelines, and constraints affecting this stationing. This approach shall demonstrate an understanding of OCONUS staffing and present alternative methods for meeting requirements in the event of extended in-country processing delays.

Recruitment/Retention Offerors shall:

- Describe effective strategies and concepts necessary to ensure adequate recruitment of personnel to fill vacated SAP positions or newly identified SAP positions with cleared, qualified personnel as defined by PWS 5.1.2. These strategies and concepts shall be provided for initial staffing, PWS 5.1.1 and complete staffing, PWS 5.1.2.

- Include a direct labor price list for filling any and all positions and locations (this is not intended to be a cost volume, but a comprehensive direct labor list for each individual skill set and location).

- The Offeror shall submit a Professional Employee Compensation Plan (in accordance with FAR 52.222-46) for employees who will work under the contract (to include teammates and subcontractors) setting forth salaries and fringe benefits proposed, including supporting information used in establishing the total compensation structure.

In presenting the compensation plan attention should be given to geographic considerations, diversity of work, and expertise required to provide a high quality and stable workforce. For teammates and subcontracts, the Offeror may provide a benefits summary only.

- The PECP shall include details regarding wages/salaries, tangible fringe benefits and other forms of compensation/motivation, including employer/employee cost sharing arrangements or benefits that will be used to recruit and retain high-quality employees.

Address proposed plans for benefits, such as sick leave, health insurance, employee saving plans, vacation, education, and/or other competitive fringe benefits.

- The Offeror shall submit applicable unburdened direct annual salaries that will actually be paid to the employees as compensation. The Offeror shall detail the base labor rate, fringe, all other burdens, and profit/fee contained in labor rates to facilitate comparisons for those who are proposed to work under this contract. The Offeror shall provide the basis for these rates/benefits and provide evidence that they will be able to attract and retain the requisite work force to perform this effort.

- Each proposed subcontractor shall submit to the prime Offeror a separate PECP meeting the requirements of FAR 52.222-46. If there are concerns sharing these plans with the prime Offeror, the subcontractor may submit their plan in a sealed package to the prime Offeror, which will only be opened by the Government. The prime Offeror shall submit its completed L-4 Price Matrix as well as all proposed subcontractor PECPs as part of its proposal submission. The Government will not accept direct submission from any subcontractor. Subcontractor PECPs are counted towards the Offeror’s total page count.

Offeror’s are responsible to verify its total PECP page count.

Recruiting Program The Offeror shall:

- Describe a recruiting program that demonstrates the Offeror is able to bring in qualified new employees to replace departing employees and meet increased contract requirements.

- Describe a recruiting program that will recruit highly skilled, low density/high demand personnel.

Timely Hiring Offerors shall:

Describe a comprehensive and effective plan for timely hiring of SAP personnel as defined in PWS 5.1.4. Also include the entire hiring cycle, to include realistic times necessary for security clearances and placement. Hiring cycle, in this instance, is defined as the time from executed contract modification to the time the personnel are cleared, in-place, and performing the work.

Retention Offerors shall:

- Describe an executable approach that demonstrates an ability to meet retention requirements as defined in PWS 5.1.7.

- Describe an approach that demonstrates an ability to retain highly skilled, low density/high demand personnel.

4.5 Technical Capability Risk Assessment

The Offeror shall address the technical risk, or lack thereof, associated with the following aspects of the proposed technical approach:

- Potential for disruption of schedule

- Increased costs

- Degradation of performance

- Need for increased government oversight

Classify each risk in accordance with DoD Source Selection Procedures, Technical Risk Rating Table 4.5, which is excerpted below.

- Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance.

- Describe the impact of each identified risk in terms of its potential to interfere with or prevent successful accomplishment of other contract requirements.

- Propose a realistic risk mitigation plan for identified risks that will eliminate or mitigate risk. Identify and classify any new risks introduced by such risk mitigation.

4.6 Technical Volume Attachments

4.6.1 Program Management Plan (PMP) – Tab 1

Submit a PMP (see PWS 3.1 and CDRL *005). This shall include a complete, annotated outline of the content as defined in the CDRL. Select and fully develop sections from the Data Item Description associated with CDRL *005 that demonstrates an implementation approach to the global SAP management, SAP specific security personnel requirements, position disciplines, and staffing required for this effort. Provide detail regarding your schedule of events and activities, tasks and deliverables, control policies and procedures, management processes, and technical management processes. The submittal shall include, as a minimum, the following:

- Contractor Management Structure - The Offeror shall describe the contractor management structure, management staff, and subcontractor management.

- Subcontractor Management - The Offeror shall describe how they propose to manage and interact with any/all subcontractor(s) and/or consultant(s).

- Communications - The Offeror shall describe how they will maintain effective communications with the customer to promote transparency and openness for better performance.

- Program Reviews and Reporting - The Offeror shall describe how they will conduct program management reviews, and how it will prepare and deliver program reporting information (PWS 3.2).

- Financial Reporting - The Offeror shall describe how they will provide a Cost/Schedule Status Report (CDRL *001) to enable the Government to understand the status of cost and labor hours in performing the contract (PWS 10).

- Training - The Offeror shall describe how they will ensure that personnel are properly and thoroughly trained to perform their duties, and how personnel are provided additional training as necessary to remain professionally current (PWS 3.4, 3.8 and 5.1.3). The Offeror shall also describe how this information will be recorded and reported in CDRL *009.

- Ad Hoc and Surge Support - The Offeror shall describe how they will support rapid and flexible responses to enterprise SAP security requirements and short term surge tasking.

Table 4.5 - TECHNICAL RISK RATINGS

Rating Description

Low Has little potential to cause disruption of schedule, increased cost or degradation of performance. Normal contractor effort and normal Government monitoring will likely be able to overcome any difficulties.

Moderate Can potentially cause disruption of schedule, increased cost or degradation of performance. Special contractor emphasis and close Government monitoring will likely be able to overcome difficulties.

High Is likely to cause significant disruption of schedule, increased cost or degradation of performance. Is unlikely to overcome any difficulties, even with special contractor emphasis and close Government monitoring.

4.6.2 Workload Distribution Matrix – Tab 2

The Offeror shall complete a Workload Distribution Matrix as Tab 2 identifying all proposed personnel for each individual TO identified by position number, labor category, and location with proposed prime or subcontractor assignments. The matrix shall also include proposed labor and positions for all management positions (key personnel) internal to the Offeror.

4.6.3 Resumes and Letters of Intent (LOI) – Tab 3

The Offeror shall submit resumes for all key personnel. Resumes shall be submitted in the format provided in L-1 – Resumes Template. Program manager(s) resume shall demonstrate minimum required qualifications and experience to manage this type of workload.

Additionally, the Offeror shall submit LOI for all key personnel who are not already employees of the prime or subcontractor(s). This letter shall be signed by the person named and an authorized representative of the Offeror or subcontractor.

4.6.4 Unburdened Labor Rate Matrix – Tab 4

The Offeror shall submit unburdened labor rates in the format provided in L-4 – Unburdened Labor Rate Matrix.

5.0 Volume III - Cost/Price

Intentionally Blank - Reserved

6.0 Volume IV - Contract Documentation

6.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The "original" copy shall be clearly marked under separate cover and shall be provided without any punched holes. The Offeror’s proposal shall include a signed copy of the Model Contract, with the following information filled in (Sections A through K).

6.1.1 Section A - Solicitation/Contract Form

Completion of Blocks 11 and 13, and signature and date for Block 27 of the Standard Form (SF) 1447, are required. Signature by the Offeror on the SF 1447 constitutes an offer, which the Government may accept.

6.1.2 Section B - Supplies or Services and Costs/Prices

Pricing information for the basic contract shall be submitted in accordance with Section 5.0.

6.1.3 Section I - Contract Clauses

Fill in all Section I clauses that need to be completed.

6.1.4 Section J – List of Attachments

Offeror shall fill in Labor Category/Rate Table to be attached to the basic contract

6.1.5 Section K - Representations, Certifications, and other Statements of Offerors Offeror shall complete all representations, certifications, acknowledgements, and statements.

6.2 Exceptions to Terms and Conditions

Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken.

Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 6.2.

Table 6.2 - Solicitation Exceptions

Solicitation Document Page/Paragraph Requirement/Portion Rationale

PWS, Model Contract, CDRL, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

6.3 Responsibility Information

6.3.1 Business Systems

The Offeror shall provide evidence of Government approval in accordance with clause 252.242- 7005, Contractor Business Systems, for the following business systems:

- Accounting System The Offeror shall indicate whether it has a Government approved accounting system and if so, provide evidence of such approval. Also, identify any deviations from the Offeror’s standard procedures in preparing this proposal. In the even the Offeror does not have an approved system, the Offeror shall submit a completed Standard Form (SF) 1408 for a potential pre-award survey. The SF 1408 and instructions to complete the SF 1408 can be found at the following links:

http://www.dcaa.mil/preaward_survey_of_prospective_contractor_accounting _system_checklist.pdf and http://www.gsa.gov.portal/forms/download/115778.

- Estimating System The Offeror shall indicate whether it has a Government approved estimating system and if so, provide evidence of such approval. If the Offeror does not have an approved estimating system, the Offeror shall provide evidence that it has taken action to obtain approval or re-approval of its estimating system. The Offeror shall identify any deviations from standard estimating procedures in preparing the Cost/Price Volume

- Purchasing System The Offeror shall indicate whether it has a Government approved purchasing system and if so, provide evidence of such approval. If the Offeror does not have an approved purchasing system, the Offeror shall provide evidence that it has taken action to obtain approval or re-approval of its purchasing system. The Offeror shall identify any deviations from standard purchasing procedures in preparing the Cost/Price Volume.

6.3.2 If the Offeror is other than a small business, the Offeror shall submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9 that also identifies and specifies the extent of Offeror’s commitment to the participation of SB, HBCU, and MI, whether as joint venture members, teaming arrangement partners, or subcontractors. If the Offeror is submitting an individual contract plan, the plan must separately address subcontracting with SB, Veteran-Owned Small Business (VOSB), Service-Disabled Veteran Owned Small Business (SDVOSB), HUB Zone, Small Disadvantaged Business (SDB), and Women Owned Small Business (WOSB) concerns with a separate part for the basic contract and separate part for each option (if any). The plan shall be included in and made a part of the resultant contract. If applicable, submit a copy of your approved Master Plan. In the event the Offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, The Small Business Subcontracting Program--Statutory Requirements, the Offeror must submit the information that identifies and specifies the extent of their commitment to the participation of SB, VOSB, SDVOB, HUB Zone, SDB, and WOSB. These targets will be provided in the Small Business Subcontracting Plan in accordance with FAR 52.219-9, and submitted under Volume V, Contract Documentation. Failure to submit and negotiate the subcontracting plan shall make the Offeror ineligible for award of a contract.

6.3.3 Post Award Security. Offerors are required to maintain or have the proper personnel and physical security clearances in place for Post Award administrative matters (i.e., protest of award) in accordance with the DD form 254. The personnel security clearance level required is Top Secret (TS), current within the past six (6) years.

Additionally, personnel will need to undergo separate access adjudication procedures beyond basic security clearance requirements. All personnel will be required to meet requirements listed in DoDM 52.05.07, Vol 2. If an Offeror does not proved evidence that it has an appropriate post award administration SAPF prior to award, the Offeror shall be determined non-responsible. The Offeror shall also obtain required personnel security clearances for all team members who are expected to require post award access to classified proposal information (maximum of TBD personnel, which cannot be part of the Offeror’s proposal team, per Offeror), or the Offeror shall be determined non-responsible.

6.4 Other Information Required

6.4.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

6.4.2 Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO) at DCMA.

6.4.3 Company/Division Address, Identifying Codes, and Applicable Designations Provide the company/division's full mail address, county, facility code, CAGE Code, Data Universal Numbering System (DUNS) Number, Tax Identification Number (TIN), and size of business (large or small). This same information shall be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

6.4.4 Attachments to the Model Contract

The Offeror shall provide the following as attachments to the model contract:

7.0 Small Disadvantaged Business (SDB) Participation Program - Targets Pursuant to the requirements of FAR 52.219-24, each Offeror must provide, with its offer, targets, expressed as dollars and percentages of total contract value, for SDB participation in any of the North American Industry Classification System (NAICS) Industry Subsectors as determined by the Department of Commerce. NAICS codes and titles are posted at:

http://www.census.gov/epcd/naics02/naicod02.htm. The targets may provide for participation by a prime contractor, joint venture partner, teaming arrangement member, or subcontractor;

however, the targets for subcontractors must be listed separately.

8.0 Small Business Subcontracting Plan - Participation of Small Businesses (SB), Historically Black Colleges and Universities (HBCU), or Minority Institutions (MI)

9.0 Government Furnished Property (GFP) and/or Base Support Requirements The Government will not provide any GFP for any element of this effort. Government support will be as defined in PWS 7.

10.0 Labor Agreements

The Offeror shall include labor agreements enforceable under the resulting contract, if applicable, and the area of coverage for such agreements.

11.0 Section L Attachments

The following templates and forms are attached:

L-1 – Resumes Template L-2 – Labor Price/Cost Template L-3 – Cross Reference Matrix L-4 – Unburdened Labor Rate Matrix

11.1 L-1 – Resumes Template

Major:

A. PERSONAL INFORMATION

Full name: {enter legal full first, middle, and last name } Place of Birth:

B. CLEARANCES

Year: Degree: Major:

Granting Institution:

C. EDUCATION

Organization in Receipt of Request:

Clearance Held: Last BI Date: Polygraph Date:

Granting Organization:

Clearance Pending: Request Submittal Date:

Granting Institution:

Year: Degree: Major:

Granting Institution:

Year: Degree:

Additional Technical and Specialty Training Name: Date: Duration:

Name: Date: Duration:

Description of Current Project:

Name: Date: Duration:

D. PROPOSED POSITION

E. EMPLOYMENT HISTORY AND EXPERIENCE

Postion Title:

Proposed FTE Percentage Proposed Labor Category:

Contract Project Role (CWBS Assigned Area):

Current Employee or Contingency Hire?

Proposed Start Date:

{enter start date } to Present {enter Company Name & Location } Postion Title:

Relevant Skills:

Description of Current Project:

Description of Role on Current Project:

{enter start date } to Present {enter Company Name & Location } Postion Title:

Relevant Skills:

Description of Current Project:

Description of Role on Current Project:

{enter start date } to Present {enter…