PWS - Video System -11 Jun 08.doc
DOC document 143 KB Posted
- Attached to
- Video System Suite Federal contract opportunity
- Solicitation number
- FA4855-08-R-0019
About this file
Attachemnt 1 to Solicitation FA4855-08-R-0019
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| PD2 Solicit Amend Doc.doc | DOC document | |
| Vid Sys Atch 4b Past and Present Performance Questionnaire.xls | XLS spreadsheet | |
| Vid Sys Atch 3 - DD254.docx | DOCX document | |
| Vid Sys Atch 2 - Wage Det.doc | DOC document | |
| Vid Sys Atch 4a Past and Present Performance References.xls | XLS spreadsheet | |
| FA4855-08-R-0019.doc | DOC document |
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
Tracking Number: 17506
Attachment 1
Contract:
11 June 2008
PERFORMANCE WORK STATEMENT
FOR
VIDEO SYSTEM
CANNON AFB NM
11 June 2008
REVIEWED BY:
APPROVED BY:
MAXINE A. GALLEGOS
PATRICIA L. THATCHER
Quality Assurance Program Coordinator Contracting Officer
TABLE OF CONTENTS
DESCRIPTION OF SERVICE
1.1 General Requirements
1.2 Specific Requirements
1.3 Installation
1.4 Testing
1.5 Training
1.6 Warranty Period
1.7 Support
1.8 Deliverables
1.9 Other Reporting Requirements
SERVICES SUMMARY
GOVERNMENT-FURNISHED PROPERTY AND SERVICES
3.1 Government-Furnished Property
3.2 Government-Furnished Services
GENERAL INFORMATION
4.1 Travel
4.2 Hours of Operation
4.3 Personnel
4.4 Security
APPENDIX
A Letter of Identification (LOI) – Official Travel of Government Contractors A-1
PERFORMANCE WORK STATEMENT
FOR
VIDEO SYSTEM
1. DESCRIPTION OF SERVICES. The 3d Special Operations Squadron (3 SOS), Cannon Air Force Base, New Mexico requires a robust media management solution that delivers video with metadata, images, audio, and digital records from various sensor platforms to a Web browser (both streaming and progressive downloads), to multiple users over the network at various bandwidth connections. The video system shall be capable of handling live video and imagery and archiving the data for future searching and retrieval. The system shall provide an interface that is intuitive, portable, and scalable. Distant users must be able to access this system from any worldwide location (with authentication and proper network access). User with a single laptop computer system should be able to utilize a scaled version of this system.
1.1. GENERAL REQUIREMENTS. The contractor shall engineer, furnish, install, and test (EFI&T) and fully implement two video systems to provide the 3 SOS with an eight (8)-feed system on the Secret collateral network and an eight (8)-feed system on the Top Secret/ Sensitive Compartmented Information (TS/SCI) network. The contractor shall provide all hardware and software (including required software licenses) necessary to support this requirement. All contractor-provided equipment shall be new. The contractor shall provide a system with all the latest software/hardware and features/functions commercially available at the time of contractor equipment order to meet the requirements as specified in this Performance Work Statement (PWS). Each system shall be configurable to allow Single Sign-On, Trust Propagation, and Role-Based Access Control at the Web service level.
1.2. SPECIFIC REQUIREMENTS. The video system shall provide:
· Live mission Full Motion Video (FMV) at selectable resolution levels.
· Primary mission Internet Relay Chat (IRC) chat room.
· Near real-time video retrieval capabilities for eight (8) FMV feeds for 60 calendar days on two (2) different networks.
· Map view of any nearby FMV stream(s), searchable by time or annotation.
· On-screen, real time, collaborative annotation (graphic and/or text tagging) of FMV through in mission “white boarding” with other mission players.
· Time-synchronized view of all activities captured during mission and the ability for viewing/saving event playback with or without meta-data viewing.
· Automated storyboarding output for time sensitive reporting.
· FMV meta-data/bookmark capability; inline archived/searchable mission chat.
· Shared live or archive video sessions with other users; synchronized video.
· Service Oriented Architecture (SOA) solution using Web services and standards-based software.
· Compatibility with popular media players and Web browsers.
· Capability to run on any device that supports Java and Web services (Personal Data Assistant (PDA), laptop, or Personal Computer (PC)).
· Input agnostic services (easily integrates with legacy systems, sources, feeds, etc.).
· Ability to input multiple simultaneous feeds from various sources (e.g., Unmanned Aerial System (UAS) cameras, sensors, portable cameras).
· Support for geospatial telemetry, multiple wireless protocols and IPv6 networks.
· Support for existing streaming servers.
· Automatic tags and indexing all content.
· Secure collection and transfer of data.
· Delivery of alerts and messages (via mobile device) to user based on rules-based engine.
· Digital media (e.g., video, imagery, data) to Java-enabled Windows 2000 and later desktops, tablet PCs, set-top boxes, and handheld devices (e.g., PDAs, phones) with wired or wireless Internet Protocol (IP) network connectivity.
· Federated collection of widely distributed service nodes to securely deliver media and telemetry, and quickly alert users to video of specific interest.
· On-demand access, collection, processing, load-balanced storage, dissemination and management of information to users with a specific need-to know.
· Users the ability to quickly discover Intelligence Surveillance & Reconnaissance (ISR) video by geospatial querying: coordinates (using Graphical User Interface (GUI)), date/time, keyword/ phrase, or any combination.
· Services to ensure all information posts and queries occur in a secure, net-centric environment, using Web services through a Web browser.
· End-user access to video streams with a total latent of under one (1) second of capture and server-induced latency.
· Integration with other systems: ArcIMS, ICav, Falconview, Google Earth, Overwatch InterSCOPE, and any other system as required.
1.2.1. Required Equipment.. The required equipment and quantities are identified in the matrix below. The equipment shall meet or exceed the requirements set below.
| EQUIPMENT |
| DESCRIPTION |
| LOCATION |
| Video Systems - 2 each |
| 8-Feed Analog adLib™ Video System Suite, with H.264 hardware video encoders and 36 months unlimited Hardware Warranty |
| Cannon AFB, New Mexico |
| Field Service Representative (FSR) - 1 each |
| On-Site FSR at Cannon Air Force Base (New Mexico) for |
12 months Cannon AFB, New Mexico
| Collaboration Suite Software - 2 each |
| Convene Collaboration Suite software |
| Cannon AFB, New Mexico |
1.2.2. "abLib" and "Convene" Video System Suites (to be installed by contractor). At the core of the design shall be a 19-inch rack-mounted server which is modular and expandable to meet system growth. The capacity of the system should support scalable growth without major investments in new equipment. The system shall support MPEG-2 and H.264 video protocols up to speeds of 8 Mbps. The system shall support direct connection to the Ethernet (classified networks). The equipment shall meet the following requirements:
1.2.2.1. General:
· Capability to join up to 100 concurrent video users.
· Modular and expandable.
· Support bandwidth of 56 Kbps through 8 Mbps based on network availability.
· Provide secure management and lock-down support.
· Provide embedded setup wizard for easy installation.
1.2.2.2. Physical:
· Server shall be mountable in a 19” equipment rack.
· Server shall weigh no more than 25 lbs.
· Server shall support 10/100/1000 BT Ethernet NICs.
1.2.3. Shipping of Equipment. The systems shall be shipped directly to Cannon AFB NM as identified in the shipping instructions document that is included in the solicitation. The contractor shall provide the scheduled delivery date no later than 5 workdays prior to the scheduled delivery date to ensure the base locations are aware of the scheduled delivery.
1.3. INSTALLATION. The contractor is responsible for all installation activities, and shall coordinate with government representatives prior to commencing with installation.
1.4. TESTING. The contractor shall test the system prior to requesting government acceptance of the system. The contractor shall test all items procured under this effort. The government may or may not witness any and all testing. The government requires a minimum of two (2) weeks notice before the contractor performs any testing. The contractor shall provide all test equipment required to perform all testing.
1.5. TRAINING:
1.5.1. Operational and System Training. The contractor shall provide operational training to all users and system training to the network administrators within 30 calendar days of the government's acceptance of the system. The contractor shall provide continual user training, as needed, to ensure users can maximize use of the video system. All training shall consist of one-on-one, on-the-job, and/or telephone support to off-site users, as the situation warrants. The training shall provide the students with the knowledge required to perform Operations, Administration, Maintenance, & Provisioning (OAM&P) duties for the system. Continued training requirements are identified in Paragraph 1.7.2 (On-Site Support). The contractor shall develop and submit, as part of the contractor's proposal, an overview of the training, including a description of the proposed training materials, for government review and acceptance. The contractor is responsible for ensuring all system operations are included in the training.
1.5.2. Training Plan. The contractor shall develop a training plan, to include a training manual, and submit for government review and acceptance within 30 calendar days after government acceptance of the system. At a minimum, the training plan shall include the following information: a detailed description of the training to be provided (for both the formal and informal training) to include content and duration, identification of government-provided resources (i.e., training room with projection capability, access to the live video system) required for the training, a proposed schedule for all training-related task activities, and a training log to record all training-related activities. Upon government acceptance, the contractor shall provide a copy of the training manual for each desktop system to the designated government representative at each system location.
1.5.3. Reference Guide. The contractor shall develop and provide a quick reference guide, which shall contain sufficient information and instructions to enable and facilitate untrained end-users in system utilization. The contractor shall provide a draft guide with the contractor's proposal for the government's review and acceptance.
1.6. WARRANTY PERIOD. The contractor shall provide a 36-month warranty stating that all contractor-provided hardware/software and workmanship are free from defects and are operating in accordance with the manufacturer’s specifications. The 36-month warranty period shall begin at system acceptance (no exceptions – the government shall consider a contractor's proposal nonresponsive if the required warranty period is not proposed as required). The software warranty shall include all manufacturer-developed patches, software upgrades (both major and minor), maintenance upgrades (software specific), and any other software updates generally available for installation for the entire 36-month warranty period.
1.7. SUPPORT:
1.7.1. Off-Site Support. The contractor shall provide necessary off-site support and resources to maintain systems and on-site support efforts. The contractor shall provide off-site support and resources sufficient to provide necessary services to maintain systems and on-site support efforts. All off-site contractor personnel who must access government facilities and systems in the course of these duties shall be United States citizens and shall possess a minimum of a Top Secret security clearance with the ability to obtain SCI access at system acceptance and shall provide all required documentation to the government as needed. The contractor(s) are also required to get Focal Point read-in. The contractor's off-site support activities shall include system integration with other similar systems deployed by the contractor, as well as oversight of on-site support services and system standardization activities.
1.7.2. On-Site Support. After government acceptance of the video system, the contractor shall provide on-site support for a one (1)-year base period (see proposal submission instructions for pricing instructions). The post system installation, on-site support shall not begin until the government has accepted the system. The government shall provide a work area for the individual providing the on-site support. The contractor shall possess a Top Secret security clearance with the ability to obtain SCI access at system acceptance and shall provide all required documentation to the government as needed. The contractor(s) are also required to get Focal Point read-in. The on-site support shall be a firm fixed price, performance-based requirement. The Services Summary (at Paragraph 2) is provided to identify the performance objectives and respective payment percentages based on relative importance to the total task performance. The on-site contractor support tasks shall include, but are not limited to, the tasks listed below.
1.7.2.1. The contractor shall provide general administration, operations, and maintenance support for the video systems.
1.7.2.2. The contractor support shall include system administration of all associated applications.
1.7.2.3. The contractor shall work with government and other contractor representatives to resolve problems and anomalies.
1.7.2.4. The contractor shall ensure resolution of all issues so downtime is minimized to ensure uptime video system service of 98 percent is achieved.
1.7.2.5. The contractor shall respond to problems or outages within 1 hour unless previously coordinated with Quality Assurance Evaluator (QAE). The contractor shall determine the scope of the problem, advise the Network Control Center (NCC), and provide an estimated restoration time.
1.7.2.6. The contractor shall record and resolve all trouble calls and provide sufficient documentation of each incident in a format accepted by the government as required by the QAE.
1.7.2.7. The contractor shall perform maintenance (routine, monthly, and emergency), to include the installation of software (new software, software releases, software updates, software patches and software fixes), and routine functions as identified by manufacturer and government network program manager at the enterprise level.
1.7.2.8. The contractor shall develop a maintenance log for documenting all maintenance-related task activities. The contractor shall submit the log, with the contractor's proposal, for government review and acceptance. The approved log shall be completed and submitted to the QAE on a weekly basis.
1.7.2.9. The contractor shall perform configuration management of the video system. The contractor shall develop and provide a Configuration Management Plan to the government two (2) weeks after government acceptance of the system. The contractor shall include the information contained in the plan in the continuity manual (see Paragraph 1.7.2.11). The configuration management information shall include, but not be limited to, a list of all components installed by system serial number (hardware and if applicable, software/Interface Operating System (IOS)) and the required data to reconfigure the complete system.
1.7.2.10. The contractor shall modify system configuration and associated video equipment to accommodate new features and new customer requirements (add new users) as required.
1.7.2.11. The contractor shall develop a continuity manual, which shall include, at a minimum, the following: complete configuration documentation, documentation of all video system equipment (hardware and software), warranty information for all equipment (hardware and software), and maintenance history. The contractor shall submit the manual for government review and acceptance within 30 calendar days from government acceptance.
1.7.2.12. The contractor shall submit a monthly status report as defined in Paragraph 1.8.
1.8. DELIVERABLES. Contractor deliverables is subject to government acceptance. Deliverables and corresponding due dates are identified in the Deliverable Matrix. The contractor shall submit deliverables with a cover letter, on the contractor’s letterhead, describing the contents. In addition, the contractor shall provide a soft copy (on CD) of all deliverables to the QAE. All deliverables shall be produced using government-recommended and/or specified software tools/versions. All documentation, data generation, data, test materials, documents, notes, records, software tools acquired, and/or software produced by the contractor under this PWS shall become the property of the U.S. Government, who shall have unlimited rights to all materials and determine the scope of publication and distribution. The contractor shall be required to deliver electronic copies of all documents, notes, records, and software to the government upon termination of the contract services or expiration of the contract period. To the fullest extent possible, the contractor shall use processes taking full advantage of electronic storage, distribution, and manipulation of information.
DELIVERABLE MATRIX
| TITLE |
| DELIVERY DATE/DESCRIPTION |
| Technical Proposal |
| Date set in solicitation. |
| Price Proposal |
| Date set in solicitation. |
| Site Survey Report |
| The contractor shall submit a site survey report documenting the entire site survey no later than 7 calendar days after the site survey. The site survey shall be completed no later than 30 calendar days after contract award. |
| System Installation Plan (SIP) |
| The contractor shall provide a SIP as part of the proposal in response to this requirement. The SIP shall include design documentation, drawings, plans and information required to fully install the system. The contractor shall update the SIP based on final proposal content and government questions and directions after contract award. The contractor shall deliver the final SIP no later than 30 calendar days after contract award. The installation plan shall include design documentation, drawings, plans and information required to fully install the system. |
| Test Plan |
| The contractor shall deliver a test plan as part of the proposal in response to this requirement. The contractor shall update the test plan based on final proposal content and government questions and directions after contract award. The contractor shall deliver the draft test plan no later than 30 calendar days after contract award. The test plan shall include industry standard tests and define tests required to ensure that the system meets technical, operational and performance specifications specified by the manufacturer and any associated or required standards. The test plan shall identify the capabilities and functions to be tested, and include detailed instruction for the setup and execution of each test and procedures for evaluation and documentation of the results. The government will review and provide comments to the draft test plan no later than 15 workdays after receipt of the draft test plan. The contractor shall provide a final test plan 10 calendar days after receipt of government comments (if required). |
| Test Reports |
| The contractor shall submit complete test reports 7 calendar days after completion of testing. The test reports shall show the tests performed to verify compliance with the specified performance criteria. Test reports shall include record of the physical parameters verified during testing. The contractor shall correct any system errors or performance deficiencies detected by testing. |
| Warranty Information |
| The contractor shall provide written procedures and required information for warranty services no later than 30 calendar days prior to the scheduled installation completion date. This information shall include, but is not limited to, written confirmation of the warranty period and phone numbers and contact information/procedures for technical support, troubleshooting assistance, and replacement of faulty equipment. |
| Recommended Spares List |
| The contractor shall provide a recommended list of spare parts for maintenance with the proposal. |
| Equipment Manuals and Software |
| The contractor shall provide complete system manuals for all equipment provided. The contractor shall provide licensed copies of all software provided or required for system operation. Manuals and software shall be provided and delivered concurrent with equipment delivery. A desktop system manual shall be provided for each desktop system that is shipped. |
| System Certification |
| The contractor shall provide written certification that the system complies with applicable standards no later than 14 calendar days after completion of testing. If the system does not comply with applicable standards within this 14-day window, the contractor shall notify the contracting officer and provide rationale and fix actions to correct any deficiencies. |
Drawings/Technical Data/ As-Builts The contractor shall submit complete as-built drawings and technical data for the installed system no later than 30 calendar days after installation acceptance. The drawings shall show the location and configuration details of all equipment and shall include an equipment listing with serial/model numbers, and manufacturer specifications. The contractor shall provide any other available technical data used to understand and maintain the system. The contractor shall provide the manufacturer’s equipment operation and maintenance documentation for all equipment provided. All drawings and as-builts shall be provided in Visio format.
| Monthly Status Report (both installation and on-site support tasking) |
| Monthly status reports shall include status of tasks, schedules, deliverables, current and cumulative task funding status (firm fixed price funds and labor hours and reimbursable funds to be reported separately), outstanding issues, and proposed resolution approaches and actions to resolve any outstanding issues. Status of tasks shall include a summary description and schedule of all tasks completed during the reporting period, all tasks currently on-going during the reporting period and all known tasks assigned for future reporting periods. Due the 10th calendar day of the month following the reporting period. |
| Electronic Trouble Ticket Documentation Log (on-site support tasking) |
| Due 30 calendar days after government acceptance of the system. After government acceptance, the trouble ticket log shall be updated within 24 hours of any trouble ticket-related activities to accurately reflect the services performed. The trouble ticket log shall be available for review at the government’s request at all times. The current trouble ticket log shall be included as an attachment to the monthly status report. |
| Electronic Maintenance Log (on-site support tasking) |
| Due 30 calendar days after government acceptance of the system. After government acceptance, the maintenance log shall be updated within 24 hours days of any maintenance-related activities to accurately reflect the maintenance performed. The maintenance log shall be available for review at the government’s request at all times. The current maintenance log shall be included as an attachment to the monthly status report. |
| Continuity Manual (on-site support tasking) |
| Due 30 calendar days after government acceptance of the system. After government acceptance, the continuity manual shall be updated within 14 calendar days of any changes to accurately reflect the changes. The continuity manual shall be available for review at the government’s request at all times. The current continuity manual shall be included as an attachment to the monthly status report. |
| Training Plan/Log (on-site support tasking) |
| Due 30 calendar days after government acceptance of the system. After government acceptance, the training plan shall be updated within 7 calendar days of any changes to accurately reflect the changes and the training log shall be updated within 7 calendar days of any training related activities to accurately reflect the training performed. The training plan shall be available for review at the government’s request at all times. The current training plan and training log shall be included as an attachment to the monthly status report. |
| Quality Control Plan (QCP) |
| The Quality Control Plan shall be submitted concurrently with and separately from the technical and cost proposals and is included in the page limitations of the proposal. The quality control plan shall address all EFI&T and on-site support requirements, services summary (SS) items, and any associated requirements. If requested, a final QCP shall be furnished for acceptance by the Contracting Officer addressing any government comments provided no later than 7 calendar days after contract award. |
1.9. OTHER REPORTING REQUIREMENTS. In addition to the deliverable requirements identified above, the contractor shall bring problems or potential problems affecting performance to the attention of the QAE as soon as possible. Verbal reports shall be followed up with written reports when directed by the QAE.
2. SERVICES SUMMARY (SS): Service requirements are summarized into performance outcomes and thresholds that relate directly to mission-essential items. The thresholds are critical to mission success and acceptable (satisfactory) performance. The SS defines the Performance Thresholds for the listed performance objectives. The contractor shall be accountable to meet the thresholds at all times except for circumstances beyond the contractor's control. Examples of such circumstances include facility power outage, down range communications lines disrupted, weather evacuation, or when redirected by the government (e.g., security lockdown, re-prioritizing due to operational needs, or not permitting system down time for maintenance). The government reserves the right to surveil all services called for in this PWS to determine whether the performance objectives and goals were met.
| SS |
| PERFORMANCE OBJECTIVE |
| PWS REFERENCE |
| PERFORMANCE THRESHOLD |
to Receive Satisfactory Rating
| 1 |
| Provide operational training to all users and system training to the network administrators within 30 calendar days of the government acceptance of the system. The contractor shall provide continual user training, as needed, to ensure users can maximize use of the video system. |
| 1.2 |
1.5.1 100 percent of the 3 SOS mission coordinators and pilots assigned will be trained on viewing live and archived FMV streams, real-time collaboration, viewing/saving event playback, outputting for time sensitive reporting, generating tags, and performing queries. Generate tailored training within 30 calendar days of written notification, from the QAE, of specific functionality desired.
| 2 |
| Ensure resolution of all issues so downtime is minimized to ensure uptime video system service of 98 percent is achieved |
| 1.7.2.4 |
| Performance is acceptable when the 98% performance standard is maintained |
| 3 |
| Respond to problems or outages within 1 hour unless previously coordinated with QAE |
| 1.7.2.5 |
| Response time to problems in less than 1 hour, 95% of the time within a quarter. |
| 4 |
| Record and resolve all trouble calls and provide sufficient documentation of each incident in a format accepted by the government as required by the QAE |
| 1.7.2.6 |
| Documentation shall be error free 95% of the time within a quarter. |
| 5 |
| Perform maintenance (emergency, routine, and monthly), to include the installation of software and routine functions as identified by manufacturer and government network program manager at the enterprise level |
| 1.7.2.7 |
| System components (hardware and software) are managed and maintained (including COTS license and warranty renewals) to support uptime (SS-2) and other performance thresholds identified within this PWS. |
| 6 |
| Submit maintenance log for all maintenance-related task activities to the QAE on a weekly basis. |
| 1.7.2.8 |
| Weekly maintenance log shall be error free 95% of the time. |
| 7 |
| Submit deliverables with a cover letter, on the contractor’s letterhead, describing the contents. In addition, the contractor shall provide a soft copy (on CD) of all deliverables to the QAE. |
| 1.8 |
(inclusive) Complete and professionally-prepared product is provided on or before suspense date set by Senior Leadership 100% of the time.
Product shall have no more than 10 errors 95% of the time within a quarter
3. GOVERNMENT-FURNISHED PROPERTY AND SERVICES. The government shall provide the contractor with the following resources for task performance:
3.1. GOVERNMENT-FURNISHED PROPERTY:
3.1.1. The government shall provide access to work space to include a desktop computer and a telephone for one individual in accordance with the on-site support services.
3.1.2. The government shall provide space on a rack for the video system in Building 780 on Cannon AFB NM.
3.1.3. The government shall provide a beeper for on-call contractor personnel.
3.2. GOVERNMENT-FURNISHED SERVICES:
3.2.1. The government shall provide technical guidance and clarification as required for completion of this contract.
3.2.2. The government shall provide available systems documentation, standards, specifications, or guidelines governing development of deliverables and manuals as requested by the contractor.
4. GENERAL INFORMATION:
4.1. TRAVEL. Travel outside the local area may be required to support the requirements of this PWS. All travel shall be directed and approved in advance by the QAE and CO on a Letter of Identification (LOI) – Official Travel of Government Contractor at Appendix A. Travel expenses shall not exceed the funding under the line item for travel for this requirement. The government shall reimburse travel IAW the Joint Travel Regulation (JTR). Contractor personnel are not authorized to travel on government invitational travel orders.
4.2. HOURS OF OPERATION:
4.2.1. Scheduled Hours. The contractor shall be required to provide 40 hours per week of on-site operational support in accordance with this contract. Military down days, training days, holidays, and weekends are normal workdays for the contractor, who shall be at their place of duty as required to support operations.
4.2.2. Outside Scheduled Hours. The contractor may be required to respond to equipment/ service outages that occur after the contractor's regularly scheduled duty hours (the 40-hour work week). If called, a minimum of one (1) hour shall apply for each trouble call at the hourly rate identified in the proposal. The contractor shall log support times and submit to the QAE for verification prior to submitting the monthly invoice.
4.3. PERSONNEL:
4.3.1 Personnel Retention. The contractor shall identify key personnel, to include off-site development and sustainment staff and on-site support staff requirements, in the technical proposal. The contractor shall submit, with the contractor’s technical proposal, the resumes of all potential key personnel selected to perform under this contract. The contractor shall make every effort to retain personnel in order to ensure continuity until contract completion. If it should become necessary to substitute or replace key personnel, the contractor shall immediately notify the QAE, in writing, of any potential vacancies. After contract award, the contractor shall submit the resumes of all potential key personnel selected to perform under this contract to the QAE for government review and acceptance/rejection. The contractor shall ensure continuity of operations during periods of personnel turnover and long-term absences. Long-term absences are considered those longer than two (2) weeks duration.
4.3.2. Potential Threat. The contractor shall not employ individuals identified to the contractor by the Contracting Officer or QAE as potential threats to the health, safety, security, general well being, or operational mission of the installation and its population.
4.3.3. Contract Employee Appearance. Contractor employees shall present a neat appearance and be easily recognized as contractor employees. All employees shall comply with the requirements of Paragraph 4.4, Security.
4.3.4. Employee Rosters. The contractor shall provide the QAE, upon contract start, a list of all on-site and off-site employees (including the key employees listed in the proposal) working under this contract. The contractor shall keep the roster current at all times and forward changes to the QAE within 10 calendar days of any change. Any changes to key personnel shall comply with the requirements of Paragraph 4.3.1, Personnel Retention.
4.4. SECURITY:
4.4.1. Clearance. All system installation and on-site support personnel assigned to this contract shall be United States citizens and shall possess a minimum of a Top Secret security clearance with the ability to obtain SCI access at system acceptance and shall provide all required documentation to the Government as needed. The contractor(s) are also required to get Focal Point read-in. All contractor personnel shall comply with established security procedures for entering the installation and its facilities, including special security procedures for entry to restricted or controlled areas. The contractor shall obtain the necessary badges, etc., for entry to restricted or controlled areas, if necessary, to meet the requirements of this contract.
4.4.2. Identification of Non-Disclosure Requirements. During the performance of this tasking, contractor personnel may be required to access or come into contact with proprietary government information. Contractor personnel shall not use such information for any purpose other than the performance of this contract. All network topologies in the Air Force are considered both sensitive and proprietary. Due to the sensitive nature of the data and information being worked with on a daily basis, the government shall require contractor employees to complete non-disclosure statements to ensure information that is considered sensitive or proprietary is not compromised.
4.4.3. Badges. The contractor is required to provide identification badges for its employees. All contractor personnel shall wear these badges while on duty on the government site. Badges are required to identify the individual, company name, and be clearly and distinctly marked as contractor. Size, color, style, etc. are to be mutually agreed upon by the contractor and the government. The contractor shall coordinate with the QAE to obtain temporary badges and vehicle registrations.
4.4.4. Privacy Act. Work on this project may require that personnel have access to Privacy Act Information. Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.
4.4.5. Safety. The contractor shall comply with all local safety regulations and procedures in effect at Cannon AFB NM.
File details come from the government source that posted it. Updated .