App_D_(TO_Process)_ _App_E_(Labor_Categories).docx

APPENDIX D

TASK ORDER REQUIREMENTS

1.0 NEW TASK ORDER REQUIREMENTS. The following parameters apply to T/Os solicited and awarded under this ID/IQ contract.

1.1 Government Requests for T/O Proposals.

1.1.1 Government Notification to Contractors.

1.1.1.1 When the Government has a TO requirement, the CO will issue a Request for Proposal (RFP) to all Contractors in the applicable (Full and Open (F&O) or Small Business (SB)) competition pool. Any T/O with an annual estimated value at or below $1M will be set-aside for award in the SB competition pool, unless the CO determines, based on (use language below) that the SB primes cannot adequately support the requirement or that adequate competition will not occur at the T/O level. For T/Os with an annual estimated value above $1M, the CO will conduct an analysis, based on T/O requirements, to determine if two or more small business concerns are capable of performing the work, consider all of the implications of a set aside at the time, to include SB activity, saturation of the SB Competition Pool, scope and complexity of the work and the current environment, and make a decision as to whether or not the T/O should be set-aside. There will be no specific socio-economic set aside other than the SB set-aside competition pool.

1.1.1.2 The Government will notify the Contractor of new T/O requirements via e-mail. The notification will include a PWS and any other documents pertinent to the T/O requirement. The Government may provide advance notice to Contractors of upcoming T/O requirements via a “Heads-up Memo” which will include attached draft PWSs, anticipated RFP release dates, and performance start dates, when feasible.

1.1.1.3 Notification of a new T/O requirement does not obligate the Government to award the T/O, nor does it authorize the Contractor to perform any work. The Government will not send a final notification of or award a new T/O requirement without a certified funding document. If the Government does not have adequate funding, the Government will notify the contractor(s) of the TO RFP cancellation.

1.1.2 T/O RFP Content. As a standard, T/O RFPs will include the following:

1.1.2.1 TO Number. Usually a 4-digit number that will become part of the T/O contract number upon award.

1.1.2.2 Task Name. Customer identified name that should easily distinguish the T/O effort from other T/O efforts.

1.1.2.3 Anticipated TO Performance Start Date. The T/O performance start date is driven by pre-established milestones that as a standard, allow approximately 30 days between contract award and performance start. There may be occasions where mission-critical requirements mandate a shorter acquisition timeline resulting in as little as one (1) day between TO award and TO performance start. In those cases, or for T/Os that require OCONUS in country performance, the T/O PWS will include a mobilization period or, at the very least, provide consideration for vacancies at T/O start commiserate with the timeline associated with getting resources in place to perform.

1.1.2.4 Attachments. All T/O RFPs will include a draft PWS and Evaluation Methodology Description and Criteria, to include a Cost/Price proposal template. Other attachments may include a sample Past Performance Questionnaire (PPQ) and/or draft DD Form 254, Department of Defense Contract Security Classification Specification, and Visitors’ Group Security Agreement (VGSA), as applicable.

1.1.2.5 Source Selection Methodology. The source selection methodology will be specified in the T/O RFP and provide details related to each factor / subfactor, as applicable, in compliance with current FAR, Defense FAR Supplement (DFARS) and AFFARS guidance. Current methodologies include:

1.1.2.5.1 Trade-Off. The Government will evaluate and trade-off among Technical, Past Performance, and Cost/Price factors, as specified in the T/O RFP and in accordance with DoD Source Selection Procedures.

1.1.2.5.2 Lowest Price Technically Acceptable (LPTA). The Government will evaluate Technical acceptability and Past Performance (if utilized) on a pass/fail basis, and Cost/Price, as specified in the T/O RFP and in accordance with DoD Source Selection Procedures.

1.1.2.6 New or Existing Requirement. The Government will state whether the requirement under solicitation is new work or if it is a recompetition for existing work. If it is a recompete for existing work, the Government will provide the contract number and name of the Contractor performing the work.

1.1.2.7 Contract Type. The Government will specify the type of contract required so ID/IQ Contractors can propose accordingly. T/O contract type options include:

1.1.2.7.1 Firm Fixed Price (FFP) - CLIN XX01. The FFP contract type will be utilized for reasonably well-defined and well-quantified requirements where actual historical pricing information exists in order for the CO to deem the price fair and reasonable. The Government will use the applicable labor categories and pre-negotiated rates to determine the Independent Government Estimate (IGE) for each FFP requirement; however, these will not be provided in the solicitation or necessarily expected in an offeror’s proposal. FFP contracts will be negotiated at the T/O level, with the IGE, pre-established rates, and price actuals of historical work performed serving as the basis for negotiation and comparison prior to award.

1.1.2.7.2 Firm Fixed Price Level of Effort (FFP LOE) Term – CLIN XX02. Per FAR 16.207, this contract type will be used for task orders when work can only be stated in general terms and the contractor must provide a specified level of effort, over a stated period of time. Payment is based on the effort expended rather than on the results achieved. FFP LOE will be used when the desired work cannot otherwise be clearly defined; or the required level of effort may be defined, but the quantities associated with that work may not exist. In all cases, the required level of effort will be identified and agreed upon prior to performance start based on reasonable assurance that the intended result cannot be achieved by expending less than the stipulated effort. FFP LOE Task Orders will normally utilize pre-determined hours (typically based on 1920 hours/year) for CONUS work and days for OCONUS work.

1.1.2.7.3 Fixed Price Incentive (FPI) Firm – CLIN XX03.

1.1.2.7.4 Fixed Price Incentive (FPI) Successive – CLIN XX04. This

1.1.2.7.5 Firm Fixed Price Level of Effort (FFP LOE) Completion – CLIN XX05. Per FAR 16.207, this contract type will be used for task orders when work can only be stated in general terms and the contractor must provide a specified level of effort, over a stated period of time. Payment is based on the effort expended rather than on the results achieved. FFP LOE will be used when the desired work cannot otherwise be clearly defined; or the required level of effort may be defined, but the quantities associated with that work may not exist. In all cases, the required level of effort will be identified and agreed upon prior to performance start based on reasonable assurance that the intended result cannot be achieved by expending less than the stipulated effort. FFP LOE Task Orders will normally utilize pre-determined hours (typically based on 1920 hours/year) for CONUS work and days for OCONUS work.

1.1.2.7.6 Cost Reimbursable (CR) – CLIN XX06.

1.1.2.7.7 Cost Plus Incentive Fee (CPIF) – CLIN XX07.

1.1.2.7.8 Cost Plus Award Fee (CPAF) – CLIN XX08.

1.1.2.7.9 Cost Plus Fixed Fee (CPFF) – CLIN XX09. The CPFF contract type will be utilized for requirements lacking well-defined or well-quantified requirements or where historical pricing information does exist or for new capabilities / technologies. Depending on the complexity of the requirement, the TO CO will make the final determination on the details of an adequate accounting system or when a purchasing system may be required. CPFF contracts will be negotiated at the TO level, with the IGCE and pre-established rates serving as basis for negotiation and comparison prior to award.

1.1.2.7.10 CPFF Level of Effort (CPFF LOE) – CLIN XX10.

1.1.2.8 Travel Estimate. If travel is predicted for the T/O requirement, the Government may: provide a travel materials estimate, which primes shall use in T/O proposals; provide anticipated locations of travel when the Government cannot reasonably predict the frequency and length of travel required, with a ‘Not to Exceed’ amount for the T/O; state that travel is required to support the effort and base awarded travel on the awardee’s proposed approach. The Government may take alternate approaches to those listed here, but will provide the information available at the time of solicitation and endeavor to provide as much information as possible for each T/O requirement.

1.1.2.9 Materials Estimate. If materials are predicted for the T/O requirement, the Government may: provide a materials estimate, which primes shall use in T/O proposals; provide the materials necessary for completion of the T/O requirement and base awarded materials on the awardee’s proposed costs/prices; or provide the anticipated end state of the requirement and base awarded travel on the awardee’s proposed approach. The Government may take alternate approaches to those listed here, but will provide the information available at the time of solicitation and endeavor to provide as much information as possible for each T/O requirement.

1.1.2.10 OCONUS and Overseas Requirements. The T/O RFP will state whether any OCONUS work is required, in whole or as a portion of any T/O requirement.

1.1.2.11 Contractor Personnel Requirements. The Government may specify the number of contractor personnel required and/or those deemed “Key” to performance of the T/O requirement.

1.1.2.12 Proposal Delivery. The Government will specify how and where to deliver proposals; e-mail is the required delivery method, unless otherwise specified in the Government’s notification.

1.1.2.13 Proposal Due Date and Time. The Government will specify the exact due date and time for all T/O proposals. The Government standard will be 10 business days from RFP release to proposal due date. Mission critical requirements may require fewer days. Consideration will be given to the timing of the Heads-Up Memo and accuracy of the documentation at the time of its release. More importantly, the proposal due date will be a reflection of the requirement’s dollar value, complexity and uniqueness, such that the Government thoroughly considers these dynamics when determining proposal response time and subsequently, the proposal due date (i.e., higher dollar value, more complex/unique requirements will result in longer response times (more time from RFP release to proposal due date)).

1.1.2.14 Deadline for Any Inquiries or Concerns Regarding the T/O RFP. The Government will also provide a deadline for addressing any inquiries or concerns regarding the T/O RFP. This gives the Government time to react to and inform offerors of any changes prior to the final proposal due date, or extend the proposal due date should it become necessary.

1.1.2.15 No-Bid Statement. If a prime in the competition pool applicable to the T/O RFP elects not to submit a proposal for a T/O requirement, that Contractor shall submit a “no bid” statement to the CO, as specified in the TO solicitation, on or before the T/O proposal due date. The Contractor shall provide its rationale for not bidding in the “no bid” statement.

1.1.2.16 Cost/Price Proposal Format. Each T/O RFP will specify the format in which offerors will submit cost/price proposals. The level of detail required will be prescribed in the T/O RFP. See Section B, Table B-1, Pricing Table description and Section H, paragraph H-10(d) and (e) of the ID/IQ contract for details.

1.1.2.17 Basis of Award. T/O proposals may contain language such as, “Offerors are cautioned to strictly comply with all instructions within this solicitation to ensure submission of a complete proposal. Failure to furnish a complete proposal at the time of proposal submission may result in an unacceptable proposal that the Government eliminates from consideration for award. The Government will not accept any changes to offerors’ proposals after the closing date of this solicitation (see FAR 15.208 for further information regarding late proposals). The Government may make a final determination as to whether the offeror’s proposal is acceptable or unacceptable solely on the basis of the initial proposal submitted. Accordingly, offerors are advised to submit initial proposals that are fully and clearly acceptable without additional information. Offerors’ proposals shall demonstrate a comprehensive understanding of the nature and scope of work required. The Government will not search for data to cure problems or address inconsistencies in an offeror’s proposal.”

1.1.3 Post RFP Communication. Once a T/O RFP is released, all communications with the Government shall only be made through the CO who signed the TO RFP letter, unless otherwise specified. This restriction will remain in place until award is made.

1.2 Contractor T/O Proposal Requirements.

1.2.1 Contractors electing to compete for a T/O requirement shall submit T/O proposals in the timeframe specified in the RFP (see FAR 15.208 for further information regarding late proposals). If a T/O proposal does not reach the Government on time, the burden of proof lies with the Contractor to show that delays were out of its control (e.g., post office did not meet advertised delivery date/time, Government server issues affected receipt of T/O proposal sent via e-mail, etc.). The CO will consider late T/O proposals on a case-by-case basis.

1.2.2 Contractors proposing on a T/O requirement shall address OCI as part of T/O proposal submissions in accordance with the Section H, paragraph H-3 of the ID/IQ contract. Unmitigated OCI issue(s) may result in ineligibility for award.

1.2.3 Proposals should strictly comply with all instructions in the T/O RFP and ensure submission of a complete proposal as the Government may make a final determination as to whether the offeror’s proposal is awardable based solely on the initial proposal. Accordingly, offerors are advised to submit initial proposals that are fully and clearly acceptable without additional information. Offerors’ proposals shall demonstrate a comprehensive understanding of the nature and scope of work required. The Government will not search for data to cure problems or address inconsistencies in an offeror’s proposal.

1.2.4 Proposals shall be clear, concise, and shall include sufficient detail for effective evaluation. Proposals should not simply rephrase or restate the Government’s requirements; rather, they shall provide convincing rationale to address how the Contractor intends to meet T/O requirements. Contractors shall assume that the Government has no prior knowledge of their facilities, personnel and experience as the Government will base evaluation solely on information presented in the T/O proposal. Therefore, proposals shall be orderly, sufficiently documented, and easy to understand, which will allow for a thorough, efficient and fair evaluation.

1.2.5 Proposals shall include all of the information requested in the T/O RFP and its attachments and shall be submitted in the format and within the page limitations specified in the T/O RFP. Failure to include all information requested may adversely affect the evaluation and result in removal from consideration for award. A complete proposal shall consist of a separate volume for each of the factors applicable to the source selection methodology (see paragraph 6.1.2.5).

1.2.6 Technical Proposal.

1.2.6.1 The Technical proposal shall be specific, detailed, and complete to clearly and fully demonstrate that offerors have a thorough understanding of requirements. Statements that offerors understand, can, or will comply with the PWS (including referenced AF publications, etc.); statements paraphrasing the PWS or parts thereof (including applicable AF publications, etc.); statements referencing previous work without an explanation of the approach that will be utilized for the requirement; and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered unacceptable. Offerors should note that data submitted prior to the proposal submission will not be considered in the Government’s evaluation; therefore, such data should not be relied upon or incorporated in the Technical proposal by reference.

1.2.6.2 Where labor is included in a requirement, offerors shall include a qualification summary for proposed personnel/positions as specified in the T/O RFP. Additionally, proposed labor categories shall appropriately compliment the capabilities identified in the T/O PWS.

1.2.6.3 The Contractor shall clearly identify any key personnel, whether Government-identified or Contractor-proposed, in the technical proposal.

1.2.7 Past Performance Proposal. Offerors shall provide the minimum number of past performance references specified in the T/O RFP substantiating the offeror’s ability to perform the new T/O requirement.

1.2.7.1 Recency. References should meet the recency criteria established in the T/O RFP. If a reference is not recent (does not have active performance in the specified period as defined in the T/O RFP), it will be rated as such and will not be considered as part of the past performance evaluation.

1.2.7.2 Relevancy. Offerors shall describe how each reference is relevant to the requirement in accordance with the relevancy definitions established in the T/O RFP. Relevancy will most often focus on one or more of the following: similarity in service/support, size, location, complexity, dollar value, contract type and degree of subcontracting/teaming. However, offerors should note that their assessment of relevancy has no bearing on the Government’s assessment of relevancy as a result of the source selection process.

1.2.7.3 Performance. Offerors are cautioned to provide references that demonstrate positive and successful performance of previous or ongoing requirements. Even in cases of less than satisfactory past performance, the Government will look at how the Contractor responded to and recovered from those issues.

1.2.8 Cost/Price. The Cost/Price proposal shall contain a complete T/O Cost/Price Proposal, using the template provided by the Government with the T/O RFP (see basic TO template at Attachment 1). Cost/Price proposals shall include the following, as specified in the TO RFP:

1.2.8.1 Direct labor. The Cost/Price proposal shall include the Contractor’s proposed labor category(ies) deemed appropriate to meet the requirement. These shall be the labor categories that meet the specifications (to include years of experience) of the T/O requirement and not labor categories with parameters that exceed those requirements in order to get to a higher rate. Each proposed labor category shall include number of personnel per labor category, hours (CONUS), rates, total labor cost for each proposed labor category, and total overall labor cost for each performance period. This information should tie directly to the approach proposed in the technical proposal. The labor rates proposed and awarded at the ID/IQ level against the established labor categories (Appendix E) will serve as the maximum allowable rates (ceiling) for all fixed price type T/O contracts. These maximum allowable rates can be discounted at the T/O level. If T/O performance crosses ID/IQ performance years, payment for the portions of performance in each performance year will not exceed those years’ applicable rates. All cost type T/O contracts will be negotiated at the T/O level, with the pre-established rates serving as the basis for negotiations. Contractors may propose alternate labor categories and rates, but must fully justify the new category(ies) and rate(s). It is up to the Government whether or not the alternately proposed areas will be deemed acceptable.

1.2.8.2 For all T/Os, the Contractor’s cost/price proposal prices shall include a breakout of the cost elements associated with any proposed capabilities.

1.2.8.3 Indirect rates shall be applied as applicable to the requirement.

1.2.8.4 Any backup documentation requested in the T/O RFP or later by the CO.

1.2.8.5 Adequate Accounting System. For cost contracts, proposals shall provide evidence of an accounting system that can adequately track, segregate, accumulate and report incurred costs for each CLIN, as applicable, per FAR 16.301-3. Failure to maintain an adequate accounting system for cost type T/Os may be basis for removal from competition at the TO level.

1.2.8.6 Approved Purchasing System. An approved purchasing system may be required for T/Os based on the complexity, dollar value and subcontracting involvement of the T/O requirement. When this is the case, the T/O RFP will document the requirement, and proposals shall provide evidence of an approved purchasing system capable of supporting cost type contracts per FAR Part 44.

1.2.8.7 Other information, as required by the TO RFP.

1.2.9 Limitations on Subcontracting. Small Business primes shall be in compliance with FAR 52.219-14, Limitations on Subcontracting.

1.3 Key Evaluation Parameters.

1.3.1 Guidance. The Government will evaluate proposals as specified in each T/O RFP and in compliance with the latest DoD Source Selection Procedures and Air Force Federal Acquisition Regulation Supplement 5315.3.

1.3.2 Establishing the TO Evaluation Pool. The Government may reduce the pool of offerors eligible for evaluation at the T/O level of purposes of efficiency. The methodology for doing so will be specified in the T/O RFP. An example would be to only evaluate the three lowest priced proposals for the applicable requirement, in addition to any proposals within 10% of the average of the three lowest priced proposals. Once an evaluation pool is established, evaluation will proceed based on the source selection methodology selected and identified in the T/O RFP.

1.3.3 Technical. Contractors’ TO proposals shall demonstrate a comprehensive understanding of the nature and scope of work required. The Government will not search for data to cure problems or address inconsistencies in offerors’ T/O proposals. The Government also will not evaluate proposals based on what is known or perceived about the contractor and will only evaluate the information provided in the proposal. A T/O proposal that merely reiterates or promises to accomplish the requirements of the PWS will be considered unacceptable. All Technical proposals will address Organizational Conflict of Interest per Section H, paragraph H-3 of the ID/IQ contract. The Government reserves the right to incorporate all or parts of the Contractor’s proposal into the resulting T/O, but will include only the portions of the T/O proposal that are of benefit to the Government, contributed to the award decision (such as qualifications of proposed personnel), and/or are negotiated with the Contractor for inclusion.

Labor categories that exceed the requirements may appear to be an attempt to get higher pay for the personnel…

1.3.3.1 Technical Pass/Fail (LPTA). Each subfactor will be evaluated on a pass/fail basis and assigned a rating based on whether the T/O proposal meets the basic PWS requirements and standards, and satisfactorily addresses the subfactor evaluation criteria identified in the T/O RFP. Extra credit will not be assigned for exceeding the pass/fail subfactor criteria. A rating of “Acceptable” or “Unacceptable” will be assigned for each Technical subfactor. A rating of “Acceptable” will be required in all subfactors to be eligible for award.

1.3.3.2 Technical (Trade-off). As with LPTA, each subfactor will be evaluated and assigned a rating specified in the T/O RFP based on whether the T/O proposal meets the basic PWS requirements and standards, and satisfactorily addresses the subfactor evaluation criteria identified in the T/O RFP. Proposed capabilities that exceed subfactor criteria may be a basis for a trade-off decision. A rating of “Acceptable” or the minimum acceptable rating specified in the T/O RFP will be required in all subfactors to be eligible for award.

1.3.4 Past Performance.

1.3.4.1 Determination of Responsibility. Even though the assessment of Past Performance is separate and distinct from Determination of Responsibility required by FAR Part 9, any past performance references provided in the Past Performance Volume may be used to support the Determination of Responsibility.

1.3.4.2 Other Sources. The Government may utilize references other than those identified by Contractors proposing on a T/O requirement in evaluation of Past Performance. While the Government may elect to consider data obtained from other sources, the burden of providing accurate and complete, recent and relevant past performance references that demonstrate the ability to perform a T/O requirement rests with each offeror.

1.3.4.3 Past Performance Pass/Fail (LPTA). The Past Performance factor will be evaluated on a pass/fail basis and assigned a rating based on whether the proposed references meet the recency, relevancy and performance criteria in demonstrating the offeror’s ability to meet T/O requirements. A rating of “Acceptable” or “Unacceptable” will be assigned at the Past Performance factor level. A rating of “Acceptable” will be required to be eligible for award.

1.3.4.4 Integrated Performance Confidence Assessment. For FTO source selection methodologies, each offeror on a T/O requirement will receive one integrated performance confidence assessment rating at the Past Performance factor level per the guidance referenced in paragraph 6.4.1. This rating will represent the Government’s confidence in the Contractor’s ability to perform on the T/O requirement.

1.3.4.5 Adverse Past Performance. Adverse past performance is defined as any past performance information with a less than satisfactory rating on any evaluation aspect or any unfavorable comments received from sources without a formal rating system. When a Contractor’s relevant performance record indicates performance problems, the Government will consider the number and severity of the problems and the appropriateness and effectiveness of any actual corrective actions taken (not just planned or promised). The Government may review more recent contracts or performance evaluations to ensure corrective actions have been implemented and to evaluate their effectiveness. In accordance with FAR 15.306(b), Communications must be held with any Contractor who would be excluded from competition because of adverse past performance, unless the Contractor has previously had the opportunity to comment on such information.

1.3.4.6 Contractors without a record of relevant past performance or for whom information on past performance is not available will not be evaluated favorably or unfavorably on past performance and, as a result, will receive a commensurate rating for the Past Performance factor.

1.3.5 Cost/Price.

1.3.5.1 The Government intends to award T/Os with fair and reasonable costs/prices that provide reasonable fees/profit to Contractor’s for their risk. The Government will establish an estimate before soliciting for each T/O, with the estimate serving as an initial baseline against which to measure proposed costs/prices. A price analysis and cost analysis will be conducted in accordance with FAR 15.404-1, as applicable to the T/O requirement. Price reasonableness will be determined based on a comparison of offerors’ total overall evaluated prices, which consist of all labor and travel and/or material with associated indirect rates, as applicable for the basic T/O contract period and any options.

1.3.5.2 The Government will evaluate proposed prices to determine whether prices are consistent with the skill sets required for the work to be performed, reflect a clear understanding of the TO requirement, and are consistent with the various aspects of the TO proposal.

1.3.5.3 Comparison of proposed prices received in response to a T/O RFP is the preferred and intended cost/price analysis technique. Other techniques and procedures, if deemed necessary, may be used to ensure a fair and reasonable price and realistic cost, to include, but not limited to, the following: comparison of previously proposed costs/prices and previous Government and commercial contract costs/prices with current proposed costs/prices for the same or similar service/items; comparison with competitive market prices of similar indexes; GSA Schedule(s) or Department of Labor wage/salary indexes; or comparison of proposed prices with the independent Government estimate.

1.3.5.4 Unrealistically or exceptionally low proposed prices or unrealistic costs, initially or subsequently, may be grounds for eliminating a T/O proposal from competition either on the basis that the Contractor does not understand the requirement or the Contractor has provided an unrealistic proposal.

1.3.5.5 The Government will analyze offers to determine whether they are unbalanced with respect to cost/price. An example of an unbalanced offer would be proposed labor rates that are significantly less than or significantly overstated in relation to the proposed rates for other labor categories (either of the offeror’s proposal or the same labor categories as proposed by other offerors). The Government may also consider an offer unbalanced if there is a significant difference between proposed labor rates in the same labor category between option periods or the proposed prices from year to year are above what would be considered a reasonable adjustment for inflation. Offers that are determined unbalanced may be rejected.

1.4 T/O Award.

1.4.1 If no offer is determined acceptable, the Government will notify the Contractor(s) of T/O RFP cancellation.

1.4.2 The CO may issue a written notice, citing the funding line of accounting, when funds are available, but a modification cannot be completed in time for continuation of performance. This alternative will only be used in extraordinary circumstances, and not as a standard way of conducting business.

1.4.3 The Contractor is not authorized to commence task performance prior to the issuance of the T/O award documents or a written notice to proceed from the CO.

1.4.4 The COR will be highly qualified, fully trained and officially appointed in writing by the CO. The Government will provide a copy of the appointment letter to the Contractor for signature as part of the award documentation.

1.5 Task Order Requirements. Contractors can expect the following, as a standard, in T/Os issued under this ID/IQ contract (NOTE: in all cases, the T/O requirement document will specify the T/O requirements related to each of the following areas for performance under that T/O; the following is provided for guidance purposes only, unless otherwise specified):

1.5.1 Requirement Documents. T/Os requirements may be captured in a SOO (initially), SOW or PWS, depending on the requirement and the Government’s ability to define that requirement in performance based terms. The PWS will be the desired requirements document. SOWs may be more common on the UMMC requirements. The requirements document may also include the expected period of performance (base period and any option periods).

1.5.2 Task Order Objective / Scope. This section will strategically describe the work to be performed / desired end state and locations.

1.5.3 Performance Requirements. This section will specifically describe the work to be performed and/or desired end state. It will include the base requirement and any performance options. This section will also cover the following, as applicable (see note at PWS paragraph 6.5 above).

1.5.3.1 Task Leads. The Government may specify or the Contractor may propose a T/O Task Lead, or similar title, to perform overall management of the T/O, including personnel, planning and execution (task priorities, short notice suspenses, operational constraints, and management of other impacts), T/O QC efforts, direction, coordination and reviews necessary to ensure successful T/O cost/schedule/performance. In the absence of a specified T/O Lead, the Contractor shall ensure these activities are properly conducted and appropriately monitored to ensure successful T/O performance.

1.5.3.2 Delivery Expectations.

1.5.3.2.1 The requirement document will specify any delivery location(s) (POD) and points of contact (POC) for delivery, as applicable. As a standard, the Government will expect single delivery to specified PODs. However, the Government also expects the most cost effective approach to delivery and that storage costs do not accrue due to delays in procuring one or more items.

1.5.3.2.2 As a standard, the Government expects all equipment, materials, vehicles, boats, etc. to be new / latest model year, of good quality and durability accordingly to commercially accepted quality standards, and accompanied by quality documentation. See PWS paragraph 2.4.2 and subparagraphs.

1.5.3.3 Life Support / Security. As a standard, the Contractor will be responsible for providing life support services (lodging, air and ground transportation) and security for personnel performing in country, unless otherwise specified in the T/O requirement.

1.5.3.4 Warranty Information / Operations Manuals. As a standard, for delivery of materials, equipment, vehicles, boats, etc., the Government will expect warranties and OEM operations manuals at the time of delivery and often in languages other than English. The Government expects that Contractors will minimize translation costs by requesting documents in the specified language(s) from the OEM.

1.5.3.5 Brand Name Only Items. As a standard, T/O requirement documents will specify any brand name items. The Government’s intent is that brand name only requirements will only be required when interoperability, safety, security or environmental issues impact the ability to provide anything other than a specified brand name item.

1.5.3.6 Travel.

1.5.3.6.1 The T/O requirement document may specify travel details or the Government may expect that Contractors will propose the required travel based on the Contractor’s technical approach in lieu of the Government specifying travel details. Regardless, as a standard, all travel shall be pre-approved by the PM/COR (see PWS paragraph 2.4.1 and subparagraphs).

1.5.3.6.2 In all cases, the Contractor shall ensure that all requirements for foreign travel, as specified in the DoD Foreign Clearance Guide (https://www.fcg.pentagon.mil), are met prior to traveling to work locations OCONUS (see PWS paragraph 2.1.3 and 4.3.4.7). As part of Foreign Clearance Guidance compliance, some countries currently require medical and/or emergency evaluation from that country. This is currently the case in Tajikistan. Proof of Medical Evacuation insurance is required for all personnel performing work in Tajikistan. As of 8 July 2013, Embassy policy MI 13-06 requires all Temporary Duty (TDY) personnel to provide proof of $150,000 of MEDEVAC insurance prior to travel approval. This is based on the historical cost of urgent MEDEVAC from Dushanbe (typically by International SOS). This policy has been vetted by Department of State and DoD, and is clearly outlined (with a link to the Post Policy) in the Foreign Clearance Guide -- Section III, Para A-1 (Country Clearance Requirements) for Tajikistan. While this may change during the ID/IQ ordering period and performance periods for T/Os issued under this ID/IQ, it is an example of why it’s critical that Contractors fully comply with the Foreign Clearance Guidance related to each country of performance.

1.5.3.7 Defense Base Act (DBA) Insurance. Contractors shall provide DBA insurance for all Contractor personnel performing OCONUS, unless otherwise specified in the T/O requirement document.

1.5.3.8 Value Added Tax (VAT), Customs, Duties. The Contractor shall be responsible for all associated taxes (e.g., VAT), duties and customs fees, and other related charges for each country of performance if a waiver or an exemption is not available. The T/O requirement document may specify any known waivers or exemptions and associated country processes.

1.5.3.9 Arms Export Control Act and ITAR. The Contractor shall be responsible for all aspects of export compliance, including compliance with the Arms Export Control Act and ITAR (see PWS paragraph XXX). Designated ITAR controlled articles shall be controlled by the Contractor and marked at the vendor level and shipped to POD with all documentation ready for USG review.

1.5.3.10 Technical Assistance Agreements (TAA). The Contractor shall ensure the appropriate TAAs and/or applicable export licenses are in place before conducting any activity under a T/O that requires such approval and documentation.

1.5.3.11 Meetings.

1.5.3.11.1 As a standard, to T/O requirement document will specify any meetings (kick-off or other) required in performance of the T/O requirement (see PWS paragraphs 2.2.6.2, 2.2.7.2 and 2.3.7).

1.5.3.11.2 At Government or Contractor request, the Contractor shall also participate in T/O status meetings (or any other T/O-related meeting) to formally or informally discuss or review the Contractor’s efforts and progress toward T/O completion. Regardless of whether or not a specific meeting time is established, the Government expects the Contractor to inform the PM and COR, in a timely fashion, of any problems with contract execution and proposed solutions.

1.5.3.12 Deliverables. The T/O requirement document will, as a standard, specify the T/O deliverables to include a description of each deliverable, the PWS reference, due date(s) / time(s), and/or delivery location.

1.5.3.13 Services Summary / QASP. Each T/O requirement document will most likely include a T/O specific Services Summary and QASP (or T/O surveillance plan), which the Government will utilize to monitor the Contractor’s T/O performance (see PWS paragraph 3.5 and subparagraphs).

1.5.3.14 Government Furnished Items. The Contractor shall ensure accurate control and accountability of all GFP (see PWS paragraph 5.0 and subparagraphs), Materials (GFM), Equipment (GFE), Information (GFI), and any other Government furnished items.

1.5.3.15 Contractor Furnished Supplies and Services. Except for those items or services specifically stated in the TO as Government furnished, the Contractor shall furnish the required supplies and services needed to perform each T/O requirement.

1.5.3.16 Transition / Mobilization. The T/O requirement document may require a transition or mobilization period to initiate in-country support at specified locations. When applicable, the T/O requirement document would provide details of a transition or mobilization period. Such a period would likely include: staffing, country clearance process, VISAs, completion of any required TAA or licensing requirements, training, Individual Replacement Deployment Operations (IRDO), etc.

1.5.3.17 Human Rights Vetting Requirements. While Human Rights Vetting is a Government responsibility, the Contractor may be required to ensure any personnel who will or may interact with US Government personnel are properly vetted and maintain appropriate documentation.

APPENDIX E

LABOR CATEGORY DESCRIPTIONS

2.0 LABOR CATEGORIES.

2.1 General.

2.1.1 This document specifies the required minimum levels of education and experience for Contractor employees provided under the labor categories listed below. There may also be a requirement that the individual possess a specified security clearance in addition to the requirements listed below.

2.1.2 The categories listed below are the Government’s best estimate of the labor categories that will be required for T/O performance throughout the life of the ID/IQ contract. There is no guarantee that requirements will exist for all categories listed and that some categories may not be utilized during the performance of the contract.

2.1.3 T/O PWSs will describe the type of support needed. However, for each task, the Contractor shall propose the labor categories, levels and skill mix deemed most appropriate to accomplish T/O requirements. If a Contractor proposes a labor category with higher rates that exceed T/O PWS requirements, the Contractor runs the risk of being determined unreasonable, inconsistent with the T/O requirement, and therefore unawardable.

2.1.4 The Government reserves the right to create/identify new labor categories during the course of the ID/IQ contract to meet unforeseen mission requirements or as part of a T/O RFP. Additionally, if a Contractor determines that a labor category does not exist to meet a T/O requirement, the Contractor may propose alternate labor categories and rates, but must fully justify the new category(ies) and rate(s). It is up to the Government whether or not the alternately proposed labor category(ies) and rate(s) will be deemed acceptable. Any new labor categories will be negotiated separately.

2.2 Performance Levels. The following provide general guidelines for each of the established performance levels. These serve as a frame of reference. Contractors shall adhere to the specifications in Table 5 – Labor Categories.

2.2.1 Junior / Apprentice. This performance level indicates that the proposed individual / capability meets a basic competency for performance of the specified labor category with anywhere from no experience to three (3) years of experience.

2.2.2 Experienced / Journeyman. This performance level indicates that the proposed individual / capability meets any specified educational requirement with anywhere from three (3) to ten (10) years of experience related to the functional area defined in the T/O requirement. The “Experienced” level typically performs work independently and may supervise or manage a small number of junior / apprentice level personnel.

2.2.3 Senior / Expert. This performance level indicates that the proposed individual / capability meets any specified educational requirement, in addition to:

· Over 10 years of experience specific to the performance area(s) defined in the T/O requirement

· Work that involves high-visibility or mission critical aspects of the T/O requirement

· Ability to perform all functional duties independently

· Ability to oversee, supervise or manage the efforts of multiple less experienced / junior staff or all staff assigned to a particular functional area

2.3 Experience in Lieu of Education. Table 5 - Labor Categories, provides the minimum degree and /or experience requirements for each labor category. When a degree is specified, the Government will not accept a lower level degree. When a Contractor proposes a higher level degree than the minimum (or no degree requirement is stipulated) the following apply:

2.3.1 An Associate’s Degree may be substituted for one (1) year of experience, e.g., a 15 year experience requirement may be satisfied by an Associate’s Degree and 14 years of experience.

2.3.2 A Bachelor’s Degree may be substituted for four (4) years of experience, e.g. a 15 year experience requirement may be satisfied by a Bachelor’s Degree and 11 years of experience.

2.3.3 A Master’s Degree may be substituted for five (5) years of experience, e.g. a 15 year experience requirement may be satisfied by a Master’s Degree and 10 years of experience.

2.3.4 When there is no experience listed in the table in lieu of an educational requirement, the minimum degree listed is required. No experience substitute for a degree will be accepted.

Solicitation No. FA4890-10-R-0001

CN&GT

OPERATIONS AND LOGISTICS ID/IQ PWS

Solicitation No. FA4890-14-R-0023

CN&GT Operations and Logistics Support ID/IQ PWS

Table 5 – Labor Category Descriptions

3-6 years of experience in BOTH Program Management AND the functional area identified in the T/O

6 to 14 years of experience in BOTH Program Management AND the functional area identified in the T/O

15 or more years of experience in BOTH Program Management AND the functional area identified in the T/O

3-6 years of experience in BOTH project management applications AND the functional area identified in the T/O

6 to 14 years of experience in BOTH project management applications AND the functional area identified in the T/O

15 or more years of experience in BOTH project management applications AND the functional area identified in the T/O

1-4 years of experience in BOTH the technical area(s) of expertise required by the T/O AND organizing and managing technical facets of the specified area(s)

4-14 years of experience in BOTH the technical area(s) of expertise required by the T/O AND organizing and managing technical facets of the specified area(s)

15 or more years of experience in BOTH the technical area(s) of expertise required by the T/O AND organizing and managing technical facets of the specified area(s)

1-4 years of experience in BOTH the areas of expertise required by the T/O or related discipline AND with regulations, manuals, technical orders, standards, and industry publications related to logistics support

4-14 years of experience in BOTH the area of expertise required by the T/O or related discipline AND with regulations, manuals, technical orders, standards, and industry publications related to logistics support

15 or more years of experience in BOTH the area of expertise required by T/O AND with regulations, manuals, technical orders, standards, and industry publications related to logistics support

1-4 years of experience in specific functional area identified in the T/O requirement

7-14 years of experience in functional area identified in the T/O requirement

15 or more years of experience in the specific area of expertise required by the T/O

Demonstrated investigative, verbal and writing skills AND 1-4 years of experience in BOTH the area of expertise required by the T/O or related discipline AND working independently or as a group member while addressing T/O requirements