Final_ TO_02_Det_5_Bomber_Test_Division.docx
DOCX document 47 KB Posted
- Attached to
- OPERATIONAL TEST AND EVALUATION SERVICES (OTES) Federal contract opportunity
- Solicitation number
- FA7046-11-R-0003
About this file
FINAL TASK ORDER 2
View the file
Other files for this federal contract opportunity
Show all 50
OPERATIONAL TEST AND EVALUATION SERVICES (OTES) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Task Order 0002
OPERATIONAL TEST & EVALUATION (OT&E) TEST PROGRAM
TECHNICAL & SCIENTIFIC SERVICES
FOR THE BOMBER TEST OPERATIONS DIVISION (BTO)
22 Sep 11
1.0 SCOPE
This effort shall be conducted pursuant to the provisions of the Operational Test and Evaluation Services (OTES) contract Performance Work Statement (PWS), paragraph 3. The objective of this task order is to provide engineering technical services in the areas of OT&E concepts, planning, executing, and reporting for all of the programs under the Air Force Operational Test & Evaluation (AFOTEC) Detachment 5 Bomber Test Operations Division (BTO). Specifically, the contractor shall review and provide recommendations on systems requirements documents; provide input during systems design and development; identify test capabilities requirements and shortfalls; develop mission task breakdown; refine test concepts and designs; identify test support resources needs (facilities, instrumentation, and personnel); provide technical expertise to develop the Test and Evaluation Master Plan (TEMP); develop test and evaluation plans; create detailed test procedures; participate in test team deployments; prepare data management and analysis plans; collect and compile evaluation data; provide technical input for operational impact assessments; and submit inputs to operational test and evaluation (OT&E) reports and briefings.
1.1 BACKGROUND
The Detachment 5 BTO is tasked with operationally testing and evaluating bomber weapon systems during all phases of program acquisition. The results of these evaluations are used by the Air Force to support systems acquisition milestone decisions and provide system users performance data on new systems being employed for their mission. The Detachment 5 BTO is tasked to plan, conduct, and report on effectiveness, suitability, and mission capability to meet user’s operational requirements. The division supports multiple programs at Edwards AFB, CA and various deployed locations during weapon system OT&E.
BTO’s programs are primarily focused on multi-million dollar, acquisition category (ACAT) I aircraft modernization programs, but also include ACAT II and ACAT III programs, which typically are prerequisites for ACAT I programs. The major command customer is Air Combat Command (ACC). Currently, the B-1 programs are focused on the new combat communication/data link delivery and aircrew displays. These programs include the Fully Integrated Data Link (FIDL) and Common Link Integration Processing (CLIP). The B-2 efforts are focused on avionics modernization and communication/data link integration. These programs include: Defensive Management System (DMS) and Extremely High Frequency (EHF). B-52 programs are focused on upgrading the entire fleet with modern avionics and communication capabilities. These programs include: Combat Network Communications Technology (CONECT), Extremely High Frequency (EHF) and Strategic Radar Replacement (SR2).
Table 1.0 provides the current understanding of major BTO products for scoping proposals. Actual dates, programs, and events are subject to change. Additional BTO programs are expected during the period of performance of this task order.
Table 1.0. Current Bomber Programs
B1
FIDL
| CLIP |
| B-2 |
DMS
B-2
EHF
| B-52 CONECT |
| B-52 |
EHF
B-52
SR2
| PID/SOC |
| May 10 |
| May 08 |
| Jul 10 |
| Aug 08 |
| May 10 |
| Mar 10 |
| Dec 10 |
| Tasking Order |
| May 10 |
| May 08 |
| Jul 10 |
| Aug 08 |
| May 10 |
| Mar 10 |
| Dec 10 |
Technical Review
Test Concept Briefing
Initial Test Design & Plan (OT&E/OA)
| OA/OUE DMAP & Plan |
| May 09 |
| May 09 |
| Jul 16 |
| Sep 10 |
| Jul 11 |
| Apr 17 |
| Feb 16 |
| OA/OUE Final Report |
| Aug 10 |
| Aug 10 |
| Jan 17 |
| Aug 11 |
| May 12 |
| Jan 18 |
| May 17 |
| Test Readiness Briefing |
| May 11 |
| May 11 |
| OT&E DMAP |
| Apr 11 |
| Apr 11 |
| Apr 17 |
| Dec 11 |
| Sep 12 |
| Oct 18 |
| Mar 17 |
| OT&E Plan |
| Apr 11 |
| Apr 11 |
| Apr 17 |
| Dec 11 |
| Sep 12 |
| Oct 18 |
| Mar 17 |
| OT&E Plan Briefing |
| Apr 11 |
| Apr 11 |
| Apr 17 |
| Dec 11 |
| Sep 12 |
| Oct 18 |
| Mar 17 |
| OT&E Report |
| Oct 11 |
| Oct 11 |
| Apr 18 |
| Aug 12 |
| Aug 13 |
| Aug 19 |
| Jan 18 |
| OT&E Report Brief |
| Oct 11 |
| Oct 11 |
| Apr 18 |
| Aug 12 |
| Aug 13 |
| Aug 19 |
| Jan 18 |
Project Closeout
2.0 APPLICABLE DOCUMENTS
In addition to the test and evaluation guidance contained in the Performance Work Statement (PWS), Section 2.0, the following documents are applicable to this task order. Documents will be made available.
| 2.1 | Program Documentation |
| 2.1.1 | Operational Requirements Documents (ORD) |
| 2.1.2 | Test and Evaluation Master Plans (TEMP) |
| 2.1.3 | Capability Production Document (CPD) |
| 2.1.4 | Capability Development Documents (CDD) |
| 2.1.5 | Concept of Operations (CONOPS) |
| 2.2 | Tests and Evaluation Documentation |
| 2.2.1 | Evaluation Frameworks (EF) |
| 2.2.2 | Operational Assessment Plans |
| 2.2.3 | Operational Test and Evaluation Plans |
| 2.2.4 | Test Concepts |
| 2.2.5 | Initial Test Design (ITD) Briefings and Documents |
3.0 PERFORMANCE REQUIREMENTS – applicable to the basic effort and all options, if exercised.
3.1 Management. The contractor shall provide a management structure to accomplish this task order in compliance with the provisions in Section 3.1 of the PWS. (A001, A003, A004, A005)
3.2 Test Capabilities. (A004, A005, A015, A017, A018, A021, B001-B014) The contractor shall:
3.2.1 Perform analysis of test capabilities. Activities include: identifying test capability requirements, documenting existing test capabilities, identifying shortfalls, performing trade-off analyses, and recommending approaches to solve issues.
3.2.2 Identify, develop, modify, validate, and/or verify modeling and simulation tools such as test support tools that simulate real world entities by means of computer models, hardware-in-the-loop simulators, human-in-the-loop simulators, test range facilities and simulators, installed system test facilities, and distributed interactive simulations.
3.2.3 Develop accreditation packages. Develop verification, validation, and accreditation (VV&A) plans. Prepare VV&A reports and briefings.
3.2.4 Maintain configuration management of developed and modified tools.
3.2.5 Train government personnel in the operation, interpretation of outputs, and maintenance of contractor-developed test tools, such as computer software, applications, instrumentation, and models and simulations. Provide Information Technology (IT) Special Access Program (SAP) test support.
3.2.6 Identify, develop, and/or apply analytical techniques, methodologies, and tools for OT&E.
3.2.7 Identify, develop, integrate, and/or specify state of the art instrumentation, recent breakthroughs in simulation hardware for ranges (live and virtual), and creative ways to use constructive simulations to answer operational questions. This knowledge would cover a range of technical fields such as aerodynamics, electronic warfare, modeling and simulation, software development and maintenance, and the space environment.
3.3 Test Planning. (A004, A007, A008-A013, A015, A017, A018, B001-B014) The contractor shall:
3.3.1 Develop test concepts. Refine test concepts and designs. Support program, technical, and test readiness reviews.
3.3.2 Develop test documentation such as T&E plans, execution documents, and test and evaluation master plans (Sections 4&5) that address operational effectiveness, operational suitability, OIA for OT&E, and assessment objectives.
3.3.3 Develop Joint T&E plans.
3.3.4 Review test and evaluation considerations and document feedback for AFOTEC on program documents. Review test planning documentation for technical adequacy.
3.3.5 Review and comment on Program/T&E documentation.
3.3.6 Refine Critical Operational Issues, objectives, and measures.
3.3.7 Develop Measures of Effectiveness (MOE) and Measures of Suitability (MOS).
3.3.8 Develop Data Management and Analysis Plans (DMAP), test procedures, evaluation methodologies, analysis methods, and schedules. Provide multimedia data file management and archiving. Assure configuration control of any software codes used by or in support of the evaluation activity.
3.3.9 Develop operational test scenarios.
3.3.10 Identify candidate operational exercise participation opportunities. Perform site surveys on potential test sites, and prepare site preparation requirements such as defining site-specific installation, integration, preparation of environmental permit plans, and integration of AFOTEC equipment with equipment available from other agencies or host areas. Provide environmental health and safety planning support for test programs addressing occupational health, and environmental concerns.
3.3.11 Develop and/or operate and maintain the required automated data collection/reduction systems. Develop requirements, and refine and implement plans for appropriate test facilities/ranges and identify improvements necessary to create a realistic environment.
3.3.12 Identify test resource requirements, and prepare/update test resource plans. Provide logistic planning in support of AFOTEC.
3.3.13 Define instrumentation requirements, propose instrumentation solutions, and develop instrumentation to collect and store data.
3.4 Test Execution. (A004, A010, A008-A013, A017, A018) The contractor shall:
3.4.1 Provide field operations support such as deployment/redeployment, tracking, requesting/scheduling of all resources, and overseeing general field test operations needed to achieve stated test objectives. Provide field equipment support such as identifying/preparing test equipment and calibrating test instrumentation and site support equipment with onsite equipment and power.
3.4.2 Provide test site surveys and perform site preparation such as defining site-specific installation, integration, preparation of environmental permit plans, and integration of AFOTEC equipment with equipment available from other agencies or host areas. Provide airspace/range management support such as providing airspace management support for air vehicles and ground vehicles tests, assessments, and field evaluation activities both within the continental United States (CONUS) and overseas.
3.4.3 Provide safety support such as ground, flight, and environmental protection support in compliance with safety, occupational health, and environmental concerns/regulations.
3.4.4 Provide field communications and frequency management support such as the installation, testing, and operation of communication equipment and data links. Provide test execution oversight and ensure test safety.
3.4.5 Provide computer operation support such as system design, analysis of alternative equipment designs, integration of equipment, and equipment upgrades. Accomplish electronic data transfer. Execute approved data management and analysis plans. Conduct system software validation and verification. Run computer models and simulations and analyze/characterize the resulting output.
3.4.6 Develop and deliver T&E briefings and debriefings. Review and update T&E documentation.
3.5 Test Evaluation. (A004, A017) The contractor shall:
3.5.1 Compile, review, and analyze test data.
3.5.2 Evaluate the results of data analysis.
3.5.3 Identify the impact of lost data.
3.5.4 Support a comprehensive correlation of test results to the mission decomposition. Determine effectiveness and suitability and assess the operational impact of that system.
3.6 Test Reporting. (A004, A010, A008-A013, A018) The contractor shall prepare:
3.6.1 Final reports from evaluation/assessment activities.
3.6.2 Test documentation for inclusion in T&E reports.
3.6.3 Briefings as a part of the report coordination process.
3.6.4 Lessons learned and historical reports.
4.0 Surveillance Matrix
Table 0.1 Surveillance Matrix
Performance Objective PWS Ref
Performance Threshold Method of Assessment
| Item 1: Provide responsive Task Order/team management including quick response to contingencies, to include timely and accurate task order document and report requirements, customer interaction and feedback, contributions to meetings and reviews, and task order modifications and change orders. |
| All |
| Clear, consistent, and timely written and verbal communication (i.e., returns phone calls, emails or other communication attempts within 24 hours) with no customer complaints. Unsatisfactory performance must be resolved within 5 working days |
| Customer Complaint as validated by COR and PCO |
| Item 2: The Contractor must effectively monitor funding on each individual Task Order and effectively control the expenditures of all Other Direct Costs (ODCs). |
| 3.1.1 |
| Actual task order expenditures shall be within 10% (COR determined) of approved projected budget. Meets task order schedule requirements. |
| Monthly Status and/or Funds and Man-Hours Expenditure Reports |
| Item 3: The Contractor must be responsive to Government requirements, ensure PWS compliant performance, provide prompt identification and resolution of problems, effectively communicate concerns with the COR and meet the delivery schedule required in the Contract Data Requirements List (CDRL). |
| All |
| Within each task order, no more than one late document per month and no more than three total customer complaints, to include timely CDRL delivery, per assessment period. Unsatisfactory performance must be resolved within 5 working days |
| Customer Complaint as validated by COR and PCO |
| Item 4: Comply with applicable portions of the DD Form 254 for Task Order requirements. |
| All |
| Compliance is mandatory; no failures to meet security requirements are acceptable. Each security violation must be resolved to the government's satisfaction within 3 working days. |
| Customer Complaint as validated by COR and PCO |
Item 5: Overall Quality of Performance:
Contractor must efficiently perform all PWS tasks, including those requiring contributions to meetings and reviews.
| All |
| Contractor receives no more than three formal discrepancy reports per year from all task orders of failure to meet PWS requirements, listed in the above items per assessment period. |
| Customer Complaint as validated by COR and PCO |
Item 6: AFOTEC Safety Requirements: Contractors shall ensure their employees and subcontractors comply with all applicable OSHA standards, identify and mitigate hazards, and report pertinent facts regarding mishaps involving damage or injury. Contractors will cooperate in any safety investigation, to include toxicology testing.
| 7.6 |
| Compliance is mandatory; Contractor must meet minimum OSHA requirements. Per quarter, contractor must have zero willful OSHA violations; zero serious violations; no more than 2 other than serious violations (“violations” is defined in OSHA standards). |
Each OSHA violation must be resolved to the government’s satisfaction within 3 working days, except imminent danger situations which must be mitigated or resolved and reported immediately.
Incidents as reported in Status Reports, or violations reported to/observed by customer or COR.
5.0 SCHEDULE, DATA ITEMS, AND OTHER DELIVERABLES
5.1 Government Furnished Property (GFP)/Government Furnished Information (GFI). The government will provide working spaces, computer workstations, support equipment, special test and analysis equipment and software, and administrative equipment for personnel at Det 5, Edwards AFB, CA. The contractor is not required to maintain this equipment.
Contractor personnel may drive (driver must possess and carry a valid and current State driver’s license) and be a passenger in government vehicles supporting efforts described in this task order.
5.2. Travel Requirements
Travel will be required for a variety of tasks called out in this task order. All travel shall be coordinated with the COR no later than one week, prior to departure. Additionally, during OT&E execution, the contractor will be required to travel to the OT&E execution location for the duration of the OT&E. The travel ceiling for this task order, inclusive of all indirect costs and fee, is $250K per year.
5.3 Transition
It is anticipated that some important work will be in progress through the phase-in and phase-out periods of this contract. Interruptions or delays to the work would impact the mission. It is essential that attention be given to minimizing any interruption; therefore, the contract must provide for maximum cooperation between successor and incumbent, while also insuring that no work receives inadequate attention during phase-in/phase-out. The contractor shall plan for the transfer of work control, delineating the method for processing and assigning tasks, during phase-in/phase-out.
5.3.1 Phase-In. As a successor, the OTES contractor shall insure a smooth transition with the incumbent Engineering and Technical Services (ETS) contractor(s) during the phase-in period. There will be no Phase-in if the successor contractor subcontracts to an ETS incumbent. The contractor shall develop plans for assumption of awarded task orders. The contractor must provide an orderly transition of work acceptance and accomplishment such that any impact to a program is minimized. The phase-in time period is 30 days and is the first month of the 12-month period of performance for the basic effort.
5.4 Deliverables.
Technical Data: All documents shall be marked with: Export Control Warning: WARNING- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. . Classified deliverables shall be marked in accordance with Executive Order 13526, DoD 5200.1-R, DoDM 5200.01 Vol 3-8, DoDI 5210.02, AFI 31-401, AFI 31-407, and ISSO Marking Classification Handbook. Disseminate in accordance with provisions of DoD Directive 5230.25.
Delivery shall be made by electronic means compatible with AFOTEC software. All reports shall meet Det 5 standards for structure and content. The contractor shall provide the following reports to:
| Det 5 AFOTEC/DMS | Det 5 AFOTEC/BTO | |
| 192 E. Yeager Blvd. | 192 E. Yeager Blvd. | |
| Edwards AFB, CA 93524-6835 | Edwards AFB, CA 93524-6835 |
5.4.1 Funds and Manpower Expenditure Report (A001) – Contractor format acceptable, but must be approved by AFOTEC/A-7K, A-7R and COR, first submission only. Reports are due the tenth day after end of each calendar month reporting period.
5.4.2 Status Reports (A002) – Reports shall provide status per work breakdown structure level 2 programs. Det 5 AFOTEC/DMS copy shall cover all task orders assigned to Det 5. Reports are due the tenth day after end of each calendar month reporting period. During test execution, the contractor shall support submittal of daily status reports, as test situations require.
5.4.3 Conference Minutes (A003) - A summary of all interchanges shall be documented in Conference Report or Trip Report and submitted to the COR within five working days following such interchange.
5.4.4 Data Accession List (A004) - A listing of all documents produced shall be provided. The listing may be provided as attachment to Status Reports (A003).
5.4.5 DoD Architecture Framework Document (A005) – Strategic scope/cost activities shall include delivery of Necessary Condition Charts and schedules. For each program assigned under this task order, the evaluation framework (a living document) shall be updated as needed, at least annually.
5.4.6 Site Preparation Requirements and Installation Plan (A006) – During test planning, the Contractor shall submit documents identifying requirements and activation plans to prepare for test execution.
5.4.7 Environmental and Safety Permits, Plans, and Reports (A007-A012) – During test planning, test execution, and test reporting, identify, plan, report, and obtain permits, as required, for all environmental, safety, and mishap requirements. Draft is due when permit (A007) is applied for. Final is due 10 calendar days after permit is received.
5.4.8 Presentation Material (A014) – During test planning, execution, and reporting, various briefings are required to Division, Detachment, AFOTEC, MAJCOM, Air Staff, and DoD organizations. Briefings will use the standard AFOTEC templates available on the AFOTEC SharePoint and include content as directed in the briefing guides also available on the AFOTEC SharePoint. For each program assigned under this task order, the contractor shall annually review the TEMP and provide comments to the COR. Draft is due 10 duty days before the presentation is scheduled. Final is due 3 duty days prior to the presentation.
5.4.9 Scientific and Technical Reports (A016) – During test planning the contractor may be required to submit technical reports on factors related to test planning to support test planning options. During test reporting, contractors shall provide data analysis for inclusion into the final report. In both cases, contractor format is acceptable. Test plans; DMAPs, test reports, and miscellaneous technical reports will be submitted to the COR using the current version of reporting writing software in use in the Division. All submitted test plans and reports will be reviewed and approved through the normal AFOTEC test planning and reporting process. Reproduction copies are not required. Super Quick Look flash reports shall be submitted within 24 hours of test event, and Quick Look flash reports shall be submitted within 48 hours of test event. The final report is due 45 days after test event.
5.4.10 Scientific and Technical Reports. (A017) – Generally, AFOTEC reviews documents requiring a Comment Resolution Matrix about eight times a year.
Completed at the end of each test activity (OA, IOT&E, FOT&E, etc.), 30 days after report has been submitted. Test resource plans are reviewed on a semi-annual basis. Contractor shall review and provide inputs to the COR, current as of date of submittal. Additionally, test resource plan reviews will include an overall Division level review to ensure summation of test resource plans within the Division cover Division needs. Detailed test procedures shall be developed and documented in conjunction with test planning activities. Procedures are required prior to the Test Readiness Review. Draft is due 15 days after final test event. Final is due 45 days after test event.
5.4.11 Accreditation Package (A018-A021) – The Contractor shall submit an Accreditation Package with the Reliability/Maintainability/Availability Model developed for programs. The draft is due 30 prior to Test Readiness Review (TRR). Final is due at the TRR.
5.4.12 Validation Report (A020) - The Contractor shall submit a validation report with the Reliability/Maintainability/Availability Model developed for programs. The draft is due 30 prior to Test Readiness Review (TRR). Final is due at the TRR.
5.4.13 Software Documentation (B001-B014) – Software documentation, descriptions, reports, end items, manuals, specifications, and reports shall be provided for all software requirements upon delivery of software or integrated system. Drafts shall be provided 30 days prior.
5.4.14 Test Control Communications Capability – Integrated system, components (including spares), and upgrades shall be delivered, as required, to Det 5 AFOTEC/BTO, 118 E. Jones Road, Bldg. 145, Room 142, Cube 60, Edwards AFB CA 93524.
5.6. Schedule/Period of Performance: Basic effort is 12 months, 1 Feb 12 through 31 Jan 13; Option 1 is 12 months, 1 Feb 13 through 31 Jan 14; Option 2 is 12 months, 1 Feb 14 through 31 Jan 15; Option 3 is 12 months; 1 Feb 15 through 31 Jan 16; Option 4 is 12 months, 1 Feb 16 through 31 Jan 17
6.0 Security
6.1. DD Form 254, Contract Security Classification Specification applies to this task order.
6.1.1 The contractor will require access to classified and Special Access Required source data up to and including Top Secret Special Compartmental Information. Any extracts or use of such data will require the contractor to apply derivative classifications and markings consistent with the source from which the extracts were made IAW DOD 5220.22M, National Industrial Security Manual for Safeguarding Classified Information, and Executive Order 12356.
6.1.2 The contractor will require access to and use of COMSEC materials. The contractor shall maintain COMSEC inventories and control keying material IAW COMSEC guidelines (AFPD 31-1, AFI 33-201 Volumes 1-5 and 9, and DOD 5220.22M). Coordinate with the government COMSEC manager or functional representative on all COMSEC operating instructions, and any required training plans. Maintain any required COMSEC documentation for HQ USAF, AFOTEC, AFFTC, or base level COMSEC inspections.
The contractor process classified visits via the Joint Personnel Adjudication System (JPAS) in support of tasks within the DoD. Classified visits outside of the DoD require Visit Authorization Letters in accordance with the National Industrial Security Program Operating Manual. Direct requests must be approved by AFOTEC with coordination by the COR/test manager prior to travel.
6.2 Safeguarding Information
The contractor shall:
6.2.1 Comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act Program, and AFI 33332, Privacy Act Program requirements. These regulations set policies and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding official material.
6.2.2 Report to an appropriate authority any information or circumstances, of which they are aware, that may pose a threat to the security of DoD personnel, contractor personnel, resources, and/or classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon their initial on-base assignment.
6.2.3 The contractor is prohibited from attaching any computer hardware to the Air Force network, or running any computer software unless it has been certified and accredited according to current USAF Instructions. Any such requests for reconfiguration, upgrade, or addition of computer hardware or software must be approved by the USAF Designated Approval Authority (DAA) Representative via the contractor's submission of a written request to the COR. Contractor use of computer modems, thumb drives, and external hard drives on any machine attached to the Air Force network is prohibited. Use of commercial internet service providers is prohibited.
6.2.4 Contractor personnel using computer assets shall comply with all computer security requirements. In addition, should contractor personnel require access to computer networks or databases, they shall inform the COR or Alternate COR, who will arrange for the contractor personnel to complete the required documentation for a new computer account. The contractor shall notify the COR or Alternate COR within one workday of any contractor personnel who no longer require an open account and shall take action to close the computer account with the appropriate office within that same workday.
6.2.5 All contractor personnel who will be using C4 systems belonging to the federal government to generate, process, store, transfer, or communicate information shall attend mandatory C4 systems security training. The format for the training may be either the Air Force C4 Systems Security Awareness Training program format or an in-house contractor program that meets DOD requirements, subject to agreement by the COR. The training must be completed within the first thirty calendar days of the start of the contract or within the first 10 calendar days for contracts that have duration of 60 days or less. The contractor shall inform the COR when the training has been completed. The notice shall include the contract number and any applicable task order number, names of contractor personnel who attended and dates of training.
6.2.7 The contractor shall immediately notify the COR of any government C4 system problems or issues which come to their attention which may impact the contractor's or the government's ability to access the systems.
6.2.8 No foreign nationals are authorized to work on this effort without prior written notification to the COR and PCO, and until approval is obtained from the PCO in accordance with current government policy and regulations.
6.2.9 All contractor personnel who require access to C4 systems are required to obtain a National Agency Check (NAC) consistent with Public Trust Positions (Standard Form 85P or most current form). The contractor may submit a request to the COR that the government grant contractor employee(s) interim access to the C4 network while awaiting the results of a NAC. Interim access to the C4 network will only be granted after the contractor employees obtain at least a local background files check, and have submitted the appropriate documentation to obtain a NAC. These requests will be processed in accordance with government information security regulations and policy, and must include Security Office and DAA Representative Approval. These requests may be subject to disapproval. In no case will a contractor be given access to the network, including a group account, until a favorable NAC has been completed or interim access granted by the DAA Representative. Any interim accesses that may be granted may be rescinded at any time by the PCO, COR, Directorate Security Office or DAA Representative at the government’s discretion. Any individual who subsequently does not pass the requirements for a full NAC shall not be authorized to work under this effort.
7.0 ATTACHMENTS / MISC. INFO:
7.1 Environmental Controls. The contractor shall comply with all environmental requirements imposed by the Federal Government, the Air Force, and at locations where services are being performed. Such requirements are delineated in AF Policy Directive 32-70, “Environmental Quality”, and other laws and regulations.
7.2 Administrative Dismissal for Safety Reasons. The contractor will provide alternate work sites for personnel during local emergency situations when the Base Commander has declared an emergency and has stated personnel should not report to Base or should leave the Base during a workday. Local emergency conditions include inclement weather (i.e., snow, tornados, earthquakes, hurricanes, etc.).
7.3 Performance of Services during crisis declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander. The performance of these services is not considered to be mission essential during time of crisis. Should a crisis be declared, the PCO or his/her representative will verbally advise the contractor of the revised requirements, followed by written direction.
7.4 Conflict of Interest. In accepting and performing the work required by this task order, and all amendments thereto, the contractor certifies that the requirements of clause AFFARS 5352.209-9000, Organizational Conflict of Interest (OCI) have been or will be adhered to. The contractor must immediately bring any OCI issues to the attention of the PCO for a determination of whether a mitigation plan is required.
7.5 AFOTEC Safety Requirements. It is the contractor’s responsibility to ensure its employees and managers have a comprehensive understanding of and full compliance with OSHA requirements. Detailed information is available on the OSHA website at http://www.osha.gov.
8. WORKLOAD DATA: To be removed upon award.
A total of seven (7) estimated Full-time Equivalents (FTEs) for this task order is provided based on historical data. This information is merely an estimate and is not considered mandatory. This data may not necessarily reflect manpower needed to perform this task order. The offeror shall propose the manpower as they determine appropriate for this task order. An FTE is defined as 40-hour workweek.
File details come from the government source that posted it. Updated .