TO0001_DRAFT_ORDER.pdf
PDF 228 KB Posted
- Attached to
- FA8604-16-R-7005 RFP Federal contract opportunity
- Solicitation number
- FA860416R7005
About this file
TO0001 DRAFT ORDER
View the file
Other files for this federal contract opportunity
Show all 47
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
DRAFT
ORDER FOR SUPPLIES OR SERVICES
1. CONTRACT/PURCH ORDER/AGREEMENT NO.
FA8604-17-D-2000
2. DELIVERY ORDER/ CALL NO.
FA8604-17-F-2004
3. DATE OF ORDER/CALL
(YYYYMMMDD)
4. REQUISITION/PURCH REQUEST NO.
SEE SCHEDULE
5. PRIORITY
DO-C9
6. ISSUED BY AFLCMC/PZITA CODE FA8604 7. ADMINISTERED BY (If Other than 6) CODE 8. DELIVERY FOB
USAF/AFMC/AFLCMC
AF LIFE CYCLE MANAGEMENT CENTER
2275 D STREET, BLDG 16, RM 128
WRIGHT-PATTERSON AFB OH 45433-7228
JULIE R. HARRIS 9376567455
julie.harris.7@us.af.mil
DESTINATION
X OTHER
(See Schedule if other)
SCD: C PAS: (NONE)
9. CONTRACTOR CODE FACILITY 10. DELIVER TO FOB POINT BY (Date) 11. X IFBUSINESS IS
(YYYYMMMDD) SEE SCHEDULE X SMALL
NAME
AND
12. DISCOUNT ITEMS
SMALL DISAD-
VANTAGED
ADDRESS N
WOMEN-
OWNED
13. MAIL INVOICES TO ADDRESS IN BLOCK
SEE BLOCK 15 (PAYMENT OFFICE)
14. SHIP TO CODE 15. PAYMENT WILL BE MADE BY CODE
SEE SCHEDULE MARK ALL
PACKAGES AND
PAPERS WITH
IDENTIFICATION
NUMBERS IN
BLOCKS 1 AND 2.
EFT:T
16.
DELIVERY/
X
This delivery order/call is issued on another Government agency or in accordance with and subject to terms and conditions of above numbered contract.
TYPE CALL
OF
PURCHASE
Reference your furnish the following on items specified herein.
ORDER ACCEPTANCE. THE CONTRACTOR HEREBY ACCEPTS THE OFFER REPRESENTED BY THE NUMBERED PURCHASE ORDER AS IT MAY PREVIOUSLY HAVE BEEN OR IS NOW MODIFIED, SUBJECT TO ALL OF THE TERMS AND CONDITIONS SET FORTH, AND AGREES TO PERFORM THE SAME.
NAME OF CONTRACTOR SIGNATURE
TYPED NAME AND TITLE DATE SIGNED(YYYYMMMDD)
If this box is marked, supplier must sign Acceptance and return the following number of copies:
17. ACCOUNTING AND APPROPRIATION DATA/LOCAL USE
18. ITEM NO. 19. SCHEDULE OF SUPPLIES/SERVICES 20. QUANTITY
ORDERED/
ACCEPTED*
21.
UNIT
22. UNIT PRICE 23. AMOUNT
*If quantity accepted by the Government is same as quantity ordered, indicate by X. If different, enter actual quantity accepted below quantity ordered and encircle.
24. UNITED STATES OF AMERICA
25. TOTAL
$0.00
29.
DIFFERENCES
STEPHEN L. WHARTON
BY:
CONTRACTING/ORDERING OFFICER
26. QUANTITY IN COLUMN 20 HAS BEEN 27. SHIP NO. 28. D.O. VOUCHER NO. 30. INITIALS
INSPECTED RECEIVED ACCEPTED, AND CONFORMS TO THE
CONTRACT EXCEPT AS NOTED
PARTIAL 32. PAID BY 33. AMOUNT VERIFIED CORRECT FOR
_______ _________________________________________________ FINAL
DATE SIGNATURE AND TITLE OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32. PAYMENT 34. CHECK NUMBER
36. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT. COMPLETE
_______ _________________________________________________ PARTIAL 35. BILL OF LADING
DATE SIGNATURE AND TITLE OF CERTIFYING OFFICER FINAL
37. RECEIVED
AT
38. RECEIVED BY (Print) 39. DATE RECEIVED
(YYYYMMMDD)
40. TOTAL CON-
TAINERS
41. S/R ACCOUNT NO. 42. S/R VOUCHER NO.
DD FORM 1155, JAN 1998 (EG) ConWrite Version 6.15.2 PREVIOUS EDITION MAY BE USED Created 20 Oct 2016 12:35 PM
SCHEDULE
SECTION A - CONTRACT FORM:
1. Pursuant to FAR 16.505 and DFARS 252.216-7006, this order is a new task order against multiple award Indefinite Delivery, Indefinite Quantity (ID/IQ) contract FA8604-17-D-2000 for Information Technology (IT) Support Services for the Air Force Research Laboratory (AFRL), in accordance with the Performance Work Statement (PWS) entitled "TO0001 RQ AFRL IT PWS" dated 13 Oct 2016.
2. The total price of this order is $(TBD) and the total obligation amount is $(TBD).
3. Any clauses, terms, and conditions mutually agreed upon in the basic ID/IQ are hereby incorporated by reference.
4. As a result of paragraphs 1-3 above, the order is created as follows:
SECTION B - SUPPLIES OR SERVICES:
Qty Unit Price ITEM SUPPLIES OR SERVICES Purch Unit Total Item Amount
LABOR
$0.00 Noun: LABOR- AFRL IT SUPPORT SERVICES
PSC: D399
Contract type: J - FIRM FIXED PRICE Start Date: ASREQ Completion Date: ASREQ Descriptive Data:
a. Non-personal services to perform tasks associated with the AFRL IT Support Services in accordance with the Task Order 0001 Performance Work Statement (PWS) "TO0001 RQ AFRL IT PWS," included in Section J, Attachment 1.
b. The total price of this CLIN is $(TBD), and funded in the amount of $(TBD).
c. Performance period will be XX XXX 2017 - XX XXX 2018.
EMERGENCY SUPPORT
EST $0.00
Noun: TRAVEL- AFRL IT SUPPORT SERVICES
PSC: D399
Contract type: S - COST Start Date: ASREQ Completion Date: ASREQ Descriptive Data:
a. All travel must be in direct support of this effort and in accordance with the Joint Travel Regulations (JTR).
b. Travel shall be reimbursed in accordance with FAR 31.205-46, "Travel Costs."
c. All travel shall be approved by the Program Manager prior to commencement of travel.
d. Profit shall not be paid on travel costs.
e. The estimated Not To Exceed (NTE) of this CLIN is $(TBD). In accordance with FAR 52.232-22 Limitation of Funds, this CLIN is incrementally funded in the amount of
$(TBD).
f. Performance period will be XX XXX 2017 - XX XXX 2018.
Qty Unit Price ITEM SUPPLIES OR SERVICES Purch Unit Total Item Amount
EST $0.00
Noun: EQUIPMENT & MATERIAL- AFRL IT SUPPORT SERVICES
PSC: D399
Contract type: S - COST Start Date: ASREQ Completion Date: ASREQ Descriptive Data:
1. a. Non-labor costs associated with the performance of CLIN 0001. (e.g. equipment and materials, conference attendance, equipment transportation, etc.)
b. All ODCs must be in direct support of this effort.
c. Purchases greater than $(TBD) must be approved by the Contracting Officer prior to acquisition.
d. Profit shall not be paid on purchases made under this CLIN.
e. The estimated Not to Exceed (NTE) of this CLIN is $(TBD). In accordance with FAR 52.232-22 Limitation of Funds, this CLIN is incrementally funded in the amount of
$(TBD).
2. The Contractor shall obtain a minimum of three (3) commercial prices on subject equipment or supplies and recommend the lower of the prices or provide rationale for other than lowest price, with said prices to be furnished to the Contracting Officer for Government determination to purchase the equipment or supplies.
3. Performance period will be XX XXX 2017 - XX XXX 2018.
NSP
Noun: DATA
ACRN: U
PSC: D399
Contract type: J - FIRM FIXED PRICE Start Date: ASREQ Completion Date: ASREQ Descriptive Data:
a. Data shall be delivered in accordance with Section J of the basic contract, Exhibit A, DD Form 1423, "Contract Data Requirements List (CDRL)." The required CDRL deliverables and associated Data Item Descriptions (DID) are located in Task Order 0001 Performance Work Statement (PWS) "TO0001 RQ AFRL IT PWS," included in Section J, Attachment 1.
b. This CLIN is NOT SEPARATELY PRICED (NSP). The cost for data is included in CLIN 0001, Labor.
SECTION F - DELIVERIES OR PERFORMANCE:
SECTION G - CONTRACT ADMINISTRATION DATA:
52.232-22 -- Limitation of Funds.
As prescribed in 32.706-2 (b), insert the following clause. The 60-day period may be varied from
30 to 90 days and the 75 percent from 75 to 85 percent. "Task Order" or other appropriate designation may be substituted for "Schedule" wherever that word appears in the clause.
Limitation of Funds (Apr 1984)
(a) The parties estimate that performance of this contract will not cost the Government more than
(1) the estimated cost specified in the Schedule or,
(2) if this is a cost-sharing contract, the Government's share of the estimated cost specified in the Schedule.
The Contractor agrees to use its best efforts to perform the work specified in the Schedule and all obligations under this contract within the estimated cost, which, if this is a cost-sharing contract, includes both the Government's and the Contractor's share of the cost.
(b) The Schedule specifies the amount presently available for payment by the Government and allotted to this contract, the items covered, the Government's share of the cost if this is a cost-sharing contract, and the period of performance it is estimated the allotted amount will cover.
The parties contemplate that the Government will allot additional funds incrementally to the contract up to the full estimated cost to the Government specified in the Schedule, exclusive of any fee. The Contractor agrees to perform, or have performed, work on the contract up to the point at which the total amount paid and payable by the Government under the contract approximates but does not exceed the total amount actually allotted by the Government to the contract.
(c) The Contractor shall notify the Contracting Officer in writing whenever it has reason to believe that the costs it expects to incur under this contract in the next 60 days, when added to all costs previously incurred, will exceed 75 percent of
(1) the total amount so far allotted to the contract by the Government or,
(2) if this is a cost-sharing contract, the amount then allotted to the contract by the
Government plus the Contractor's corresponding share.
The notice shall state the estimated amount of additional funds required to continue performance for the period specified in the Schedule.
(d) Sixty days before the end of the period specified in the Schedule, the Contractor shall notify the Contracting Officer in writing of the estimated amount of additional funds, if any, required to continue timely performance under the contract or for any further period specified in the
Schedule or otherwise agreed upon, and when the funds will be required.
(e) If, after notification, additional funds are not allotted by the end of the period specified in the
Schedule or another agreed-upon date, upon the Contractor's written request the Contracting
Officer will terminate this contract on that date in accordance with the provisions of the
Termination clause of this contract. If the Contractor estimates that the funds available will allow it to continue to discharge its obligations beyond that date, it may specify a later date in its request, and the Contracting Officer may terminate this contract on that later date.
(f) Except as required by other provisions of this contract, specifically citing and stated to be an exception to this clause --
(1) The Government is not obligated to reimburse the Contractor for costs incurred in excess of the total amount allotted by the Government to this contract; and
(2) The Contractor is not obligated to continue performance under this contract (including actions under the Termination clause of this contract) or otherwise incur costs in excess of --
(i) The amount then allotted to the contract by the Government or;
(ii) If this is a cost-sharing contract, the amount then allotted by the Government to the contract plus the Contractor's corresponding share, until the Contracting Officer notifies the Contractor in writing that the amount allotted by the Government has been increased and specifies an increased amount, which shall then constitute the total amount allotted by the Government to this contract.
(g) The estimated cost shall be increased to the extent that
(1) the amount allotted by the Government or,
(2) if this is a cost-sharing contract, the amount then allotted by the Government to the contract plus the Contractor's corresponding share, exceeds the estimated cost specified in the
Schedule.
If this is a cost-sharing contract, the increase shall be allocated in accordance with the formula specified in the Schedule.
(h) No notice, communication, or representation in any form other than that specified in subparagraph (f)(2) above, or from any person other than the Contracting Officer, shall affect the amount allotted by the Government to this contract. In the absence of the specified notice, the
Government is not obligated to reimburse the Contractor for any costs in excess of the total amount allotted by the Government to this contract, whether incurred during the course of the contract or as a result of termination.
(i) When and to the extent that the amount allotted by the Government to the contract is increased, any costs the Contractor incurs before the increase that are in excess of --
(1) The amount previously allotted by the Government or;
(2) If this is a cost-sharing contract, the amount previously allotted by the Government to the contract plus the Contractor's corresponding share, shall be allowable to the same extent as if incurred afterward, unless the Contracting Officer issues a termination or other notice and directs that the increase is solely to cover termination or other specified expenses.
(j) Change orders shall not be considered an authorization to exceed the amount allotted by the
Government specified in the Schedule, unless they contain a statement increasing the amount allotted.
(k) Nothing in this clause shall affect the right of the Government to terminate this contract. If this contract is terminated, the Government and the Contractor shall negotiate an equitable distribution of all property produced or purchased under the contract, based upon the share of costs incurred by each.
(l) If the Government does not allot sufficient funds to allow completion of the work, the
Contractor is entitled to a percentage of the fee specified in the Schedule equaling the percentage of completion of the work contemplated by this contract.
(End of Clause)
252.204-0002 Line Item Specific: Sequential ACRN Order. (SEP 2009)
The payment office shall make payment in sequential ACRN order within the line item, exhausting all funds in the previous ACRN before paying from the next ACRN using the following sequential order: Alpha/Alpha; Alpha/numeric; numeric/alpha; and numeric/numeric.
252.232-7006 Wide Area WorkFlow Payment Instructions. See Basic Contract.
LIST OF ATTACHMENTS
DOCUMENT PGS DATE TITLE
ATTACHMENT 1 35 13 OCT 2016 TO0001 RQ AFRL IT PWS
For Official Use Only – Source Selection Sensitive Do not distribute without permission of AFRL/RXOC
TASK ORDER 0001
PERFORMANCE WORK STATEMENT (PWS)
TO PROVIDE
INFORMATION TECHNOLOGY SERVICES SUPPORT
FOR
AIR FORCE RESEARCH LABORATORY
AEROSPACE SYSTEMS DIRECTORATE (AFRL/RQ)
13 October 2016
TABLE OF CONTENTS
1.0 DESCRIPTION OF SERVICES
1.1. Scope
1.2. Background
1.3. Objective
1.4. Requirements
1.4.1 Computer Support
1.4.2 Application Development and Configuration Management
1.4.3 Planning
1.4.4 Network Implementation
1.4.5 Systems Integration
1.4.6 Systems Support
1.4.7 Computer-Communication Maintenance
1.4.8 Network Multimedia Devices
1.4.9 Asset Management
1.4.10 Computer Aided Design (CAD) Drawing
1.4.11 Video Teleconferencing and Meeting Support
1.4.12 Cybersecurity Management
1.5. Deliverables
1.6. Continuity of Operations (COOP)
1.7. Voluntary Protection Program (VPP)
2.0 Services Summary (SS)
3.0 Base Support/Government Furnished Information
4.0 General Information
4.1. Place of Performance
4.2. Normal Duty Hours
4.3. Extended Hours
4.4. Travel
4.5. Personnel Management and Training Requirements
4.6. Contractor Point of Contact
4.7. Associate Contractor Agreements (ACA)
4.8. Sensitivity of Data
4.9. Security and Identification Procedures
4.10. Quality Control
4.11. Quality Assurance
4.12. Performance of Services During Emergency Conditions Declared by Wright-
Patterson AFB (WPAFB) Authority
4.13. Contractor Manpower Reporting
4.14. Transition
4.15. Non Personal Services
4.16. Combating Trafficking in Persons
APPENDICES
(Provided to demonstrate the size and scope of the initial effort)
APPENDIX 1: CURRENT ENVIRONMENT INFORMATION FOR AFRL/RQ
APPENDIX 2: HISTORICAL MANNING INFORMATION FOR AFRL/RQ
1.0 DESCRIPTION OF SERVICES
1.1 Scope
To provide Information Technology (IT) Services Support for the Air Force Research Laboratory (AFRL). This support includes tasks to ensure an effective Information Management concept and structure that fosters timely deployment and optimal operation of Information Systems to support the research of the AFRL mission. Task orders will be issued to acquire the information technology support services for the AFRL directorates at Wright-Patterson AFB, OH.
The PWS addresses the provision of contractor services when the government is in garrison during Normal (Steady State) Operations, when operating in an emergency mode during the execution of Continuity Of Operations Plans (COOP) or similar plan situations and when returning from those emergency situations to Normal (Steady State) Operations.
During the testing and execution of various Continuity Of Operations Plans or other emergency plans or during the response and resolution of security incidents, every contractor providing services under this PWS may be tasked by AFRL COR personnel, AFRL managers or the AFRL Commander, coordinating with the COR, to provide assistance to other AFRL activities within the local area including providing identification checks, access control or other services within their PWS task areas.
1.2 Background
AFRL plans and executes USAF programs in the areas of basic research, exploratory development, and advanced development.
1.3 Objective
The objective is to acquire a full range of IT services to support the Research and Development and operational missions of AFRL. At a minimum, IT services will consist of the following: Customer Support, Application Development, Configuration Management, Planning, Network Implementation, Systems Integration, Systems Administration, Systems Support, Communication Support, Computer-Communication Maintenance, Network Multimedia Devices, Asset Management, CAD Drawing, Video Teleconference (VTC) and Meeting Support, and Cybersecurity Management.
1.4 Requirements
1.4.1 Computer Support. The contractor shall provide points of contact, referred to as the “Help Desk,” for collecting, controlling, disseminating, documenting, and resolving all user questions and problems. The contractor shall provide an on-site Field Service Team to perform problem analysis and resolution, as well as periodic maintenance. The contractor shall develop and update procedures for the analysis and resolution of IT support requests, including developing standardized schema for characterizing the nature and types of problems being encountered, as well as remedial services being provided. The Help Desk shall fully document trouble tickets, to include problem description, analyses, recommendations, and remedial actions that are taken by the Field Service Team. Contractor Field Service Team personnel shall be trained, qualified, and appropriately certified for the types of IT services required by the Directorate, including DOD 8570.01-M Information Assurance Workforce Improvement Program (May 15, 2008), requirements. The contractor shall ensure Field Service personnel maintain currency with training and certification to competently service technologies deployed within the Directorate. The contractor shall support the operational management of all Directorate IT systems in such a manner as to ensure that non-availability, either collectively or individually, does not exceed 1% of annual, normal operating hours (8,300 hours out of 24x7). The contractor shall conduct ongoing verification of bona fide Directorate users, as well as perform annual (re)certification of users’ licenses for network access. The network access (re)certification process shall be subject to change in order to maintain compliance with Information Assurance and Security directives.
1.4.1.1. Help Desk Field Service Operations shall:
1.4.1.1.1. Man the helpdesk with personnel qualified to provide telephone help desk support.
1.4.1.1.2. Support Directorate IT hardware, including but not limited to various types of personal and workstation computers, as well as servers, micro, mini, and mainframe computers. Hardware support consists of, as a minimum, unpacking, assembling, setting up, testing, operationally sustaining (e.g., diagnosing, repairing, and replacing), and decommissioning all Automated Data Processing Equipment (ADPE).
1.4.1.1.3. Support Directorate software, including but not limited to multiple generations of Microsoft Windows, variants of UNIX, Linux, and other proprietary operating systems, Citrix Metaframe products, VMWare systems, as well as a broad spectrum of commercial off-the-shelf (COTS) and custom application computer programs, including, but not limited to those contained in the task order appendices. Software support consists of, as a minimum: receiving, installing, testing, configuring, debugging, patching, and assisting users in employing product features.
1.4.1.1.4. Support all other IT-related equipment including but not limited to networked and dedicated printers, scanners as well as devices employing serial, parallel, FireWire, USB, and other peripheral device interfaces such as Personal Digital Assistants (PDAs), Tablets, Cellular Phones including I-Phones, and BlackBerry devices; Data Acquisition hardware and software as well as instrument controllers.
1.4.1.1.5. Manage all aspects of materials handling of ADPE, including:
1.4.1.1.5.1. Receiving, documenting (e.g., inventorying), labeling, and deploying
1.4.1.1.5.2. Recovering, disassembling, packing, crating, documenting, shipping
1.4.1.1.5.3. Relocating, reassembling, documenting, and redeploying to new locations.
1.4.1.1.5.4. Inventorying items by capturing, entering and maintaining data in Directorate ADPE databases, where applicable.
1.4.1.1.6. Manage warranty repairs for all ADPE.
1.4.1.1.7. Assist ADPE custodian(s) in accomplishing all aspects of proper management of ADPE.
1.4.1.1.8. Assist Information Assurance personnel in accordance with pertinent regulations and directives.
1.4.1.1.9. Provide immediate response to users by offering assistance over the phone, when feasible, and following up to ensure user satisfaction.
1.4.1.1.10. Utilize an automated Helpdesk call management system to track and document all Field Service activities including the resolution of user inquiries, service requests, and problem reports.
1.4.1.1.11. Maintain the Directorate Helpdesk call management system, including updating the database and adding new functionality.
1.4.1.1.12. Analyze field service reports to identify common problems, developing trends, and recommend corrective actions.
1.4.1.1.13. Operate a customer feedback assessment activity mechanism to obtain and analyze measures of customer satisfaction. Metrics data shall include measures of responsiveness as well as completeness and effectiveness of the service, and be retained for sufficient time (i.e., at least one year) in order to ensure a statistically acceptable sampling that provides perspective in terms of both the current and cumulative quality of performance.
1.4.1.1.14. Manage and maintain a bench stock inventory of ADPE, the quantities and types of which are to be determined using MTBF and other service history data that shall be captured and tracked by the Helpdesk call management system.
1.4.1.2. User Training:
1.4.1.2.1. The contractor shall prepare, manage, and arrange or conduct, IT-related training for Government personnel and supporting contractors.
1.4.1.3. Incident Priorities
1.4.1.3.1. Priority #1 – Significant Directorate impact or SES/GO and/or 2-Letter level request
1.4.1.3.2. Priority#2 – Work stoppage for any user.
1.4.1.3.3. Priority #3 - Normal or routine issues
1.4.1.3.4. Priority #4 – Minor issue resolution
1.4.2. Application Development and Configuration Management. The contractor shall:
1.4.2.1. Support AFRL research in the areas of computational research by assisting research contractors and personnel in the development of applications and models.
1.4.2.2. Support AFRL research in the areas of data acquisition and data analysis.
1.4.2.3. Support AFRL requirements for development of custom software utilities, to include interface modules required for the AFRL Enterprise Business System (EBS), and, when appropriate, coordinate with AFRL leadership, the EBS Program Office, and any other offices necessary to accomplish these tasks.
1.4.2.4. Assist Directorate customers in developing business or productivity applications, including: documenting requirements and specifications, identifying solutions, and acquiring, implementing, documenting, training, testing and validating applications.
1.4.2.5. Develop Windows-based client applications to include connections to Oracle, Microsoft SQL or other database systems employed by the Directorate.
1.4.2.6. Develop Web applications using accredited software and Web development tools.
1.4.2.7. Perform database administration of Directorate database resources.
1.4.2.8. Develop and maintain public web site content in accordance with all required DoD/AF regulations working in coordination with the appropriate Communications Group and Public Affairs.
1.4.2.9. Develop and maintain internal web site content in support of AFRL research.
1.4.2.10. The contractor shall be responsible for the activities related to the configuration management process that identify the functional and physical characteristics of a software item, control changes to those characteristics during its life cycle, and record and report change processing and implementation status. The contractor shall provide configuration management for software, related contract deliverables including contract licensing and warranty documentation. The contractor shall be responsible for adhering to Government prescribed procedures for notification and delivery of periodic releases and upgrades to the Government Configuration Control Manager (CM). The contractor shall be responsible for establishing and maintaining the configuration management-computing environment to include software development configuration management baselines. The contractor shall provide access to an automated configuration management database to allow for the generation of reports. The contractor shall be responsible for providing the Government CM with all items, as defined by the Government (i.e.
software, documentation, help files, etc.) prior to distribution. The contractor shall be responsible for the tracking and delivery of all CDRLs. The contractor shall be responsible for performing migrations across development, test and production environments and maintaining configuration control of each of these environments comprising. This would include but not held solely to IA tracking of network required changed such as TCNOs, MTOs and software inventory including software licensing information for applications, operating systems and related support tools.
1.4.3. Planning. The contractor shall support AFRL organizations in planning the following:
1.4.3.1. Updates to local network infrastructure, including factoring long range network goals into requirements and specifications for all elements that make up the corporate network systems.
1.4.3.2. Configuration and deployment of all corporate software, including operating systems and applications—both client and server-based.
1.4.3.3. Strategic investment in IT assets, to include analysis of purchase versus lease considerations, providing cost-benefit, and trade-off options.
1.4.3.4. Analysis of scalability of software, systems, and networks.
1.4.4. Network Implementation. The contractor shall:
1.4.4.1. Install, test, deploy, manage, update and maintain segments and elements of the Directorate’s local networks, including wireless networks and communications interfaces to external networks as coordinated with local Comm Group. Support shall include, where applicable, gateways to public and private communications networks.
1.4.4.2. Test, deploy, operate, update and maintain network-monitoring devices.
1.4.4.3. Survey and maintain a record of existing wireless, base band, and fiber networks and update configuration documents, as modifications are made.
1.4.4.4. Maintain building and network drawings using Government supplied tools.
1.4.5. Systems Integration. The contractor shall work to facilitate compatibility between systems deployed in AFRL and standard Air Force systems. In order to accommodate a generic interface capability to other DoD systems, the contractor shall maintain the means to utilize: Foreign National or Virtual (Extranet) Networks, internal networks supporting the AFRL mission, the Secret Internet Protocol Router Network (SIPRNet), the Defense Research and Engineering Network (DREN) and the associated Nonsecure Internet Protocol Router Network (NIPRNET), as common carriers for data traffic between systems. User interfaces being maintained shall permit AFRL WRS organization administrators to:
1.4.5.1. Provide the capability for file and print sharing through common mechanisms such as: MS-Windows File Sharing (SMB/CIFS), and Network File System (NFS)
1.4.5.2. Where permitted, enable transmission and reception of electronic mail.
1.4.5.3. Support the operation of remote terminal connections.
1.4.5.4. Where permitted, enable the integration of research systems into the AF network environment.
1.4.5.5. Plan for the transition, perform development, and implement such interfaces. This will include interfaces developed internally and by external organizations.
1.4.5.6. Researching on-going as well as planned technical and development initiatives from within the Government, which impact overall architectural or design methodologies and concepts.
1.4.6. Systems Support. The contractor shall provide systems-level support, encompassing both the software and hardware of all IT systems at covered AFRL Wright-Patterson AFB to include:
1.4.6.1. Software Maintenance: Managing and arranging for or conducting maintenance of all software in use by AFRL organizations.
1.4.6.2. Hardware Maintenance: Managing and arranging for or conducting maintenance on hardware in use by AFRL organizations.
1.4.6.3. System Administration: Handling all aspects of management and support of deployed operating systems (e.g., Microsoft Windows, Unix, and Linux), including performance of: upgrades, security patches, back-ups, account maintenance, and access control maintenance. Where required, patching will be done using Government supplied tools. Data gathered during the course of these activities will be applied in order to maximize the utilization and security of systems.
1.4.6.4. Install, configure, update and provide assistance to users for scientific applications located on the computational resources.
1.4.6.5. Provide support of multi-user platforms and server based applications.
Duties include, but are not limited to: managing and administering directorate web-based services, assisting client users in connecting and using the centralized resources, performing backup and maintenance of the index and content database, clearing and maintenance of the system cache, and optimizing the server functions, creating content workspaces, managing document and folder areas, applying and assigning permissions.
1.4.6.6. Conducting analyses, developing solutions, planning and coordinating tasks, maximizing overall system efficiency, providing for seamless integration or migration, and optimizing usability and effectiveness.
1.4.6.7. Monitoring and reviewing technical activities to ensure compatibility with the objectives, plans, and Concept of Operations (CONOPS) of all AFRL organizations.
1.4.6.8. Investigating hardware, software, and communications compatibility issues. This requirement also encompasses analysis of development, test, and implementation plans, as well as formulating best practices for carrying out technical and developmental activities.
1.4.6.9. Keeping organizational IT managers apprised of state-of-the-art technologies, including state-of-the-art IT concepts, in terms of potential benefits to the R&D or operational missions of the Directorate.
1.4.7. Computer-Communication Maintenance. The contractor shall manage and conduct, or arrange for, hardware and software maintenance services on all corporate-owned computer-communications systems equipment within AFRL organizations. Any applicable corporate commercial discounts that can be passed on to AFRL shall be identified by the contractor and made available to the AFRL organization being serviced.
1.4.8. Network Multimedia Devices. The contractor shall manage Network Multimedia
Devices (NMD), such as a Marconi ViPR, Video Distribution systems and Voice over IP telephone instruments. This will include the connection of the instruments to the unclassified network at the customer desktop. The contractor shall install and configure any software needed on the customer’s equipment. The contractor shall schedule, setup, maintain, and coordinate all NMD activities within the Directorate with customers. The contractor shall coordinate with other locations to assure communications are reliable and consistent for all equipment in the Directorate.
1.4.9. Asset Management. The contractor shall perform all duties related to the tracking and management of IT software, equipment and assets, as designated by the Directorate. This includes, but not limited to: procurement, receiving, storage, inventory, tagging/identifying, moving and turn in. When appointed the contractor shall perform annual validations of software inventories and equipment accounts and support any required Report of Surveys for missing equipment. The processes for asset management shall follow all applicable Directorate, Air Force and DoD instructions, policies and guidelines.
1.4.10. Computer Aided Design (CAD) Drawing. The contractor shall, as directed, create/maintain CAD drawings of IT related equipment, installations, and locations.
Both 2D and 3D drawing/renderings are needed to properly track and display this information, utilizing a visual format. Therefore, expertise in utilizing CAD tools, such as MicroStation, AutoCAD, or other similar tools, as designated by the Directorate, AFRL, Comm Group, AFMC, and Air Force, is a requirement.
Additional effort to employ the full capability of element tagging and database features shall also be considered within the scope of this task.
1.4.11. Video Teleconference (VTC) and Meeting Support. The contractor shall schedule, set-up, maintain, and coordinate all VTC activities. The contractor shall coordinate with other locations, as necessary to ensure communications are reliable and consistent for all equipment. The importance of this function is Directorate-dependent; therefore, the contractor shall be prepared, for each organization, to have full time qualified VTC support personnel thoroughly trained and knowledgeable with the local equipment and back-up personnel equally trained and qualified. The contractor shall:
1.4.11.1. Support VTC connections via both point to point and bridged connections.
1.4.11.2. Support high definition VTC systems.
1.4.11.3. Support VTC connections via both ISDN and IP based connections.
1.4.11.4. Provide support of meetings via the design, install and operation of computer systems, audio systems, video systems, display systems and software.
1.4.12. Cybersecurity Management. The contractor shall manage, track and administer
Information Assurance programs. All activities shall be carried out in full compliance with relevant Federal, DoD, AF, AFMC, Base, and Organizational regulations, instructions, and procedures. The contractor shall be responsible for assessing and adapting operations to comply with changes in official Government policy in these areas. The contractor shall ensure that all members servicing the organization are made aware of their duties, restrictions, procedures and regulations relating to information security. Contractor-provided IA services shall include, but not be limited to:
1.4.12.1. Compiling system accreditation and authorization documentation
1.4.12.2. Oversee and tracking compliance with network security orders
1.4.12.3. Overseeing and following up on regularly scheduled vulnerability scans
1.4.12.4. Tracking and resolving malicious logic incidents
1.4.12.5. Handling account requests
1.4.12.6. Overseeing and handling COMSEC material.
1.4.12.6.1. Resolution of classified spillage incidents
1.5 Deliverables
1.5.1 All deliverables must meet and comply with the requirements set forth in this PWS.
1.5.2 The contractor shall submit the deliverables in accordance with the attached DD Form 1423.
1.6 Continuity of Operations (COOP)
1.6.1 General
The contractor shall support AFRL during Normal (Steady State) Operations (in-garrison operations) at the normal location, as well as during the execution of a Continuity Of Operations Plan (COOP) or similar contingency plan during emergency situations, and during the return from the emergency situation to the Normal (Steady State) Operations posture. The contractor shall always provide services in a safe and secure manner, whether operating in garrison in AFRL’s normal location, in the Emergency Relocation Site or in dispersed operations within the local area. The contractor shall document and implement processes which allow for swiftly and efficiently transitioning from the Normal (Steady State) Operations posture to the emergency plan execution state, reengaging on the various tasks and then returning safely and securely to Normal (Steady State) Operations upon direction from the government.
1.6.2 Preparations before a COOP situation
While in Normal (Steady State) Operations, the contractor shall assist the AFRL staff in COOP and similar plan development as well as the coordination and testing of such plans. These preparations are the foundation from which AFRL will move to the Activation and Relocation Phase which occurs in the first 12 hours of a COOP or other emergency plan’s execution, then on to the Local Area Relocation Phase and, upon cessation of the COOP or other emergency situation, return to Normal (Steady State) Operations. Semi-annually, the contractor shall participate in the testing of at least one of these plans.
As part of COOP and emergency plan preparations, the contractor shall provide and maintain as current over the life of this task a “contractor off-base operations plan”. This plan will address how the contractor will provide services from either a centralized or decentralized off-base posture. The contractor shall consult with the Contracting Officer Representative (COR) before developing this plan in detail so as to obtain copies of the current COOP and other emergency plans involving AFRL as well as to identify what meaningful work can be conducted off-base within each labor category.
The contractor shall be authorized by the government, without resort to a contract modification, to execute the “contractor off-base operations plan” when directed by government personnel or required by approved emergency plans. For billing verification purposes, the contractor shall provide the COR with a weekly informal report documenting all work performed when the “contractor off-base operations plan” is executed.
The contractor shall perform intensified visitor control, external and internal building entrance security control; and security credential inspection during real-world or exercise periods of heightened force protection, security emergencies or other similar situations or when directed by the Government on a case-by-case basis. All personnel on this task, regardless of labor category, shall be used as needed to maintain security.
1.6.3 COOP Notification
While AFRL will normally operate in garrison at Wright-Patterson AFB in the COOP Phase of Normal (Steady State) Operations mode, the organization including its contractors must be ready at all times to execute the COOP or other emergency plans including those related to dispersed operations over an extended period of time such as during pandemics. Upon notification from the Government, that AFRL initiated the execution of the COOP or similar plans, the contractor shall secure all classified material and then safely, efficiently and swiftly shift from Normal (Steady State) Operations mode to the Activation and Relocation Phase (first 12 hours of the plan’s execution) and then to the Local Area Relocation Phase which begins in the 13th hour and lasts up to 180 days.
The contractor shall be prepared to change staff arrival and departure hours or duty location depending on the emergency plan being executed.
Upon notification by the Government of a plan’s execution, the contractor staff shall swiftly and safely secure all classified material and their normal duty locations, and then assist in executing the plan. For planning purposes, AFRL expects this plan execution period will last up to 180 days with daily assessments aimed at determining when to return to normal (steady state) operations.
1.6.4 First 12 Hours
The contractor shall relocate the plan-designated contract staff members and their usual work equipment, as needed, as directed by the plan.
During this phase, the contractor shall assist the government in opening and securing AFRL’s Emergency Relocation Site (ERS) for operational use;
relocating equipment, supplies and related items to or within the ERS to initiate and sustain operations; and make AFRL’s vital records available for the staff’s use.
To prevent inadvertent loss of equipment or data, the contractor shall use any other available contractor staff to perform identification checks or similar access control during this relocation phase.
1.6.5 Hours 13 Through Day 180 of COOP Situation
The contractor shall assist AFRL in ERS operations and, as directed by the Government the ERS facility’s host organization, in the areas of Administration, Facility Management and Visitor Control, Functional Systems Administration, Information Management including the Vital Records Inventory and records management, Knowledge Management, SharePoint and Similar Collaborative Tools Content and Access Maintenance, Security Awareness Training, Security Management and Classified Operations Support and Special Projects. These tasks shall be limited to the scope of the corresponding Normal (Steady State) Operations tasks, but performed in the ERS work areas.
Upon the ERS attaining an operational state, the contractor shall resume the Normal (Steady State) Operations tasks within that location.
As part of securing the ERS or the ERS host facility, the contractor shall perform identification checks or similar access control as directed by the Government
When directed by Government, those contractors who are not needed to sustain the ERS operations shall resume the same Normal (Steady State) Operations tasks except that work shall be performed from an AFRL location in the local area, a contractor facility or from the contractor’s home in compliance with Information and Operation Security guidelines. Some members of the contractor’s staff may not be required to relocate with the AFRL emergency relocation staff, but instead may be tasked by the AFRL Commander to provide assistance to other AFRL activities within the Dayton metropolitan areas including identification checks, access control or other services within their PWS task areas.
Dispersed operations do not apply to that work which is facility-specific and can only be performed at AFRL’s facilities in the Normal (Steady State) Operations mode. In some cases, depending on the equipment or security situation, it may be practical to have the contractor perform those facility-specific tasks in another AFRL activity within the Dayton metropolitan area. The Government will provide guidance as needed in these facility-specific situations.
All work involving information technology equipment shall be performed on government-provided, Common Access Card-enabled computers; not home or contractor-owned computers.
While many of the tasks in this PWS are common to other AFRL areas, the contractor is advised there is no guarantee all of the contractor’s Normal (Steady State) Operations tasks need be performed during the COOP or other emergency plan’s execution. In that event, the government will notify the contractor of those contractor employees whose services are not required during the COOP or emergency plan execution period. Upon receipt of such notification, the contractor shall withdraw those individuals from service and cease all hourly billing for those withdrawn employees until further notice from the government.
1.6.6 Return to Normal Operations
Upon notification from the Government that AFRL initiated a return to the Normal (Steady State) Operations, the contractor shall secure all classified materials and then safely, efficiently and swiftly, within the contractor’s PWS areas, assist the government in returning AFRL to its Normal (Steady State) Operation posture.
1.6.7 COOP Phases
The following illustration depicts the relationships of the various COOP phases as implemented by AFRL.
Return to Normal
Operations Order
Received
Emergency Relocation Site Facility
Dispensed Contractor
Support
Normal (steady state) Operations
(Aka “in-garrison”)
Activation & Relocation Phase (First 12 hours of plan execution)
Local Area Relocation Phase ** (Hour 13 through Day 180)
AFRL/CC –
Directed Support
COOP Phases *
* COOP – Continuity of Operations Plan ** Contractors who cannot be used in one of these situations will be returned to their company and taken off AFRL-related billable work until needed again
COOP
Plan
Execution Order
Received
1.7 Voluntary Protection Program (VPP)
Applicability: This section of the PWS applies to “Applicable Contractors” as defined below.
VPP Definitions:
Applicable contractors. A contractor whose employees worked at least 1000 hours at the site in any calendar quarter within the last 12 months and is NOT directly supervised by the applicant (installation).
Days Away Restricted, and or Transfer Case Incident Rate (DART). Number of recordable injuries and illness cases per 100 full-time employees resulting in days away from work, restricted work activity, and/or job transfer that a site has experienced in a given time frame.
Total Case Incident Rate (TCIR). Total number of recordable injuries and illness cases per 100 full-time employees that a site has experienced in a given time frame.
Voluntary Protection Program: The Voluntary Protection Program (VPP) promotes effective worksite-based safety and health. In the VPP, management, labor, and OSHA establish cooperative relationships at workplaces that have implemented a comprehensive safety and health management system. Approval into VPP is OSHA’s official recognition of the outstanding efforts of employers and employees who have achieved exemplary occupational safety and health.
Requirements:
Wright-Patterson AFB is in the process of pursuing VPP recognition or has already been recognized under the Occupational Safety and Health Act (OSHA) Voluntary Protection Program. VPP impacts all “applicable contractors” operating on Air Force Installations.
It is the contractor’s responsibility to ensure its employees and managers have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. The contractor shall follow the safety and health rules of the installation or VPP site. Detailed information on VPP is available on the OSHA website at http://www/osha.gov/dcsp/vpp/index.html.
1.7.1 Applicable contractors are required to submit their TCIR and DART rates and OSHA Form 300A annually to the contracting officer for consolidation and submission as part of the installation’s annual VPP Safety and Health Management report. TCIR and DART rates are due by the 15th of January each year.
1.7.2 An applicable contractor’s VPP must identify the processes and procedures the contractor will use to track compliance with the Safety and Health Plan, and the process and procedures that will be used to correct violations.
1.7.3 It is the applicable contractor’s sole responsibility for compliance with the OSHA (Public Law 91-596). The contractor must submit a Safety and Health Plan and corresponding site safety checklist to the contracting officer 10 days after contract award.
The contractor’s plan shall include appropriate measures to ensure the contractor reacts promptly to investigate, correct and track alleged safety and health violations and/or uncontrolled hazards in contractor work areas. Additional, installation specific references and policies may be included/attached to the task order. The plan shall:
1.7.3.1 demonstrate a management commitment to employee safety and health;
1.7.3.2 identify the application of the safety and health plan to subcontractors;
1.7.3.3 identify the roles and responsibilities of the following individuals:
1.7.3.3.1 Management;
1.7.3.3.2 Supervisors;
1.7.3.3.3 Employees
1.7.3.3.4 Safety Coordinator;
1.7.3.4 identify applicable safety rules and regulations;
1.7.3.5 include a worksite hazard analysis to include base-line hazard identification and required control measures;
1.7.3.6 include a job site analysis to include hazards to tasks required to control measures;
http://www/osha.gov/dcsp/vpp/index.html
1.7.3.7 identify employee safety and health training requirements and the documentation process;
1.7.3.8 include a workplace inspection frequency, to include identifying the individual conducting the inspections;
1.7.3.9 include employee hazard reporting procedures;
1.7.3.10 identify individual(s) responsible for corrective action hazards;
1.7.3.11 identify first aid/injury procedures;
1.7.3.12 identify procedures for accident investigation and report;
1.7.3.13 identify emergency response procedures; and
1.7.3.14 identify the process for tracking controlled hazards in contractor work areas
1.7.4 An applicable contractor is responsible for establishing these requirements for all subcontractor who qualify as applicable contractors under the resulting contract.
1.7.5. The Contractor shall ensure its employees and subcontractors promptly report pertinent facts regarding mishaps involving reportable damage or injury to the Safety Office for the task order and the COR, and cooperate (IAW AFI 91-204) in any Air Force safety investigation and shall comply with the Contractor’s safety and health plan.
2.0 Services Summary
This Services Summary documents the performance objectives and performance thresholds for the AFRL Information Technology Services Support contract.
The first column, PWS #, serves as a cross reference to a requirement defined in the Performance Work Statement. The Performance Objective column is a brief summary of the PWS task’s performance objective and the performance threshold identifies the acceptable level of performance for the task.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .