HTC711-09-R-0036.pdf
PDF 637 KB Posted
- Solicitation number
- HTC711-09-R-0036
About this file
Solicitation (SF33) JFAST
View the file
Other files
Show all 22
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CODE
(Hour)
PAGE(S)
until 02:00 PM local time 07 Aug 2009
X
A
X B
X C
D
EX
X
G
F 64 - 68
69 - 74
X H 75 - 79 dominic.curcuru@ustranscom.mil
RATING PAGE OF PAGES
7. ISSUED BY
(Date)
IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.
Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)
Prescribed by GSA
FAR (48 CFR) 53.214(c)
1 78
(If other than Item 7)
15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO
AND
ADDRESS
SIGN OFFER (Type or print)
OF
OFFEROR
AMENDMENT NO. DATE
15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS
IS DIFFERENT FROM ABOVE - ENTER
SUCH ADDRESS IN SCHEDULE.
18. OFFER DATE
1. THIS CONTRACT IS A RATED ORDER
UNDER DPAS (15 CFR 700)
2. CONTRACT NO.
HTC711 8. ADDRESS OFFER TO
See Item 7
9. Sealed offers in original and 3 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in
CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and
TCAQ-S Office, Bldg 1600 conditions contained in this solicitation.
10. FOR INFORMATION
CALL:
A. NAME (NO COLLECT CALLS)
DOMINIC CURCURU 618-229-2513
11. TABLE OF CONTENTS
SOLICITATION/ CONTRACT FORM
SUPPLIES OR SERVICES AND PRICES/ COSTS
1 - 2
3 - 19
X I CONTRACT CLAUSES
DESCRIPTION/ SPECS./ WORK STATEMENT X
PACKAGING AND MARKING
20 - 42 J LIST OF ATTACHMENTS
INSPECTION AND ACCEPTANCE
DELIVERIES OR PERFORMANCE
44 - 45 X K
REPRESENTATIONS, CERTIFICATIONS AND
OTHER STATEMENTS OF OFFERORS
CONTRACT ADMINISTRATION DATA 46 - 48 X
SPECIAL CONTRACT REQUIREMENTS
OFFER (Must be fully completed by offeror) 49 - 51 X M
L INSTRS., CONDS., AND NOTICES TO OFFERORS
EVALUATION FACTORS FOR AWARD
NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.
is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.
13. DISCOUNT FOR PROMPT PAYMENT
(See Section I, Clause No. 52.232-8)
14. ACKNOWLEDGMENT OF AMENDMENTS
(The offeror acknowledges receipt of amendments
AMENDMENT NO. DATE
to the SOLICITATION for offerors and related documents numbered and dated):
FACILITY
12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period
SOLICITATION, OFFER AND AWARD
X
(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)
PART I - THE SCHEDULE
26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE
EMAIL:TEL: (Signature of Contracting Officer)
CODE CODE
B. TELEPHONE (Include area code) C. E-MAIL ADDRESS
AWARD (To be completed by Government)
19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION
22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:
10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)
23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM
24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE
PART IV - REPRESENTATIO NS AND INSTRUCTIO NS
PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS
52 - 62
PART II - CO NTRACT CLAUSES
USTRANSCOM-AQ - HTC711
508 SCOTT DR
SCOTT AFB IL 62225-5357
CONTACT BUYER
CONTACT BUYERFAX:
TEL:
FAX:
TEL:
NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".
SOLICITATION
6. REQUISITION/PURCHASE NO.5. DATE ISSUED
08 Jul 2009
4. TYPE OF SOLICITATION
SEALED BID (IFB)
NEGOTIATED (RFP)
[ X ]
3. SOLICITATION NO.
HTC711-09-R-0036
Section A - Solicitation/Contract Form
ORDERING INFORMATION
In accordance with FAR 52.216-18, the United States Transportation Command, in support of its Program Office for the Joint Flow And Analysis System For Transportation (JFAST), shall be the only Government activity allowed to order off this Schedule.
In accordance with FAR 52.216-22, the quantity of services for this contract is established at $2500.00 minimum and
$30M maximum. The total ceiling value for this contract is $30M.
Section B - Supplies or Services and Prices
ITEM NO SUPPLIES/SERVICES ESTIMATED
QUANTITY
UNIT UNIT PRICE AMOUNT
0001 1 Lot
JFAST
LH
LABOR (TWCF CAP SW)
Base Period
Contractor shall provide services IAW the Government's Performance Work
Statement (PWS) identified in Section C.
Period of performance is 1 Oct 2009 thru 30 Sep 2010
FOB: Destination
SIGNAL CODE: A
TOT ESTIMATED PRICE
CEILING PRICE
UNIT UNIT PRICE AMOUNT
0002 1 Lot
JFAST
LABOR (TWCF OPS)
Period of performance is 1 Oct 2009 thru 30 Sep 2010.
UNIT UNIT PRICE AMOUNT
0003 1 Lot
JFAST DESS
LABOR
Contractor shall provide labor for the following Performance Work Statement
(PWS) Task identified in Section C, paragraph: 1.3.2.
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
0004 1 Lot
JFAST
COST
TRAVEL
All travel in support of PWS tasks shall be reimbursed in accordance with the
Federal Acquisition Regulations (FAR) and Federal Travel Regulations (FTR).
Period of Travel is 1 Oct 2009 thru 30 Sep 2010.
ESTIMATED COST
0005 1 Lot
JFAST
OTHER DIRECT CHARGES
This CLIN is established to allow purchase of support items needed to complete
PWS tasks. All anticipated purchases will be first approved by the COR and billed on an actual cost basis with supporting documentation. Note: General and
Administrative overhead charges will not be accepted or paid for approved ODC purchases.
Period of performance is 1 Oct 2009 thru 30 Sep 2010.
UNIT UNIT PRICE AMOUNT
0006 1 Lot
JFAST WEB BASED CAPABILITY
Optional Task - Phase I
(PWS) Task identified in Section C, Appendix D, 1.3.11.1.
UNIT UNIT PRICE AMOUNT
1001 1 Lot
OPTION JFAST
Option Period 1
Period of performance is 1 Oct 2010 thru 30 Sep 2011
UNIT UNIT PRICE AMOUNT
1002 1 Lot
OPTION JFAST
Period of performance is 1 Oct 2010 thru 30 Sep 2011.
UNIT UNIT PRICE AMOUNT
1003 1 Lot
OPTION JFAST DESS
1004 1 Lot
OPTION JFAST
Period of Travel is 1 Oct 2010 thru 30 Sep 2011.
1005 1 Lot
OPTION JFAST
on an actual cost basis with supporting documentation. Note: General and
Period of performance is 1 Oct 2010 thru 30 Sep 2011.
UNIT UNIT PRICE AMOUNT
1006 1 Lot
JFAST WEB BASED CAPABILITY
Optional Task - Phase II
(PWS) Task identified in Section C, Appendix D, 1.3.11.18.
UNIT UNIT PRICE AMOUNT
2001 1 Lot
OPTION JFAST
Option Period 2
Period of performance is 1 Oct 2011 thru 30 Sep 2012
UNIT UNIT PRICE AMOUNT
2002 1 Lot
OPTION JFAST
Period of performance is 1 Oct 2011 thru 30 Sep 2012.
UNIT UNIT PRICE AMOUNT
2003 1 Lot
OPTION JFAST DESS
Period of performance is 1 Oct 2011 thru 30 Sep 2012
2004 1 Lot
OPTION JFAST
Period of Travel is 1 Oct 2011 thru 30 Sep 2012.
2005 1 Lot
OPTION JFAST
on an actual cost basis with supporting documentation. Note: General and
Period of performance is 1 Oct 2011 thru 30 Sep 2012.
UNIT UNIT PRICE AMOUNT
3001 1 Lot
OPTION JFAST
Option Period 3
Period of performance is 1 Oct 2012 thru 30 Sep 2013
UNIT UNIT PRICE AMOUNT
3002 1 Lot
OPTION JFAST
Period of performance is 1 Oct 2012 thru 30 Sep 2013.
UNIT UNIT PRICE AMOUNT
3003 1 Lot
OPTION JFAST DESS
Period of performance is 1 Oct 2012 thru 30 Sep 2013
3004 1 Lot
OPTION JFAST
Period of Travel is 1 Oct 2012 thru 30 Sep 2013.
3005 1 Lot
OPTION JFAST
on an actual cost basis with supporting documentation. Note: General and
Period of performance is 1 Oct 2012 thru 30 Sep 2013.
Section C - Descriptions and Specifications
Performance Work Statement
Joint Flow and Analysis System for Transportation (JFAST)
22 June 2009
1. DESCRIPTION OF SERVICES
1.1 Background. JFAST is a multi-modal transportation analysis model designed for USTRANSCOM and the
Joint Planning and Execution Community (JPEC). JFAST forecasts transportation requirements, performs course of action analysis, evaluates ―what-if‖ scenarios, and builds delivery profiles of troops and equipment. JFAST assesses the transportation feasibility of contingency, crisis action, and exercise plans. JFAST is a Windows-based transportation-planning tool that provides an ―end-to-end‖ transportation analysis capability to model the movement of forces from origin to the tactical assembly area. JFAST routes trucks, trains, buses, convoys, aircraft, and ships over selected lines of communication to identify transportation network bottlenecks, to determine lift requirements, and to project force closures. JFAST also simultaneously analyzes multiple plans to optimize the use of Defense
Transportation System (DTS) resources.
USTRANSCOM funds the development and support of the JFAST software application. The JPEC, Joint Staff, Combatant Commands, and USTRANSCOM TCCs are primary JFAST users.
1.2 Scope. United States Transportation Command (USTRANSCOM) requires continued development and support of its JFAST software application to comply with the Joint Chiefs of Staff planning doctrine, to implement
USTRANSCOM and Transportation Component Command (TCC) enhancement requests, and to prototype new algorithms to improve the veracity of transportation planning.
The contractor shall plan for all general tasks identified in this PWS required to maintain, support, and enhance
JFAST. The contractor shall coordinate with the JFAST Program Manager (PM) to ensure that all activities are well synchronized and integrated with other USTRANSCOM modeling and simulation (M&S) efforts, and that replicated or overlapping efforts do not occur.
1.3 General Tasks. Each individual TO shall exist within the scope of the following task areas:
Contract Management, Event and Exercise Support, Requirements Definition, Design and Development, Standards, Maintenance, System Administration, Information Assurance, Contingency Operations, Configuration Management and Enhancements (specific tasks specified and performed under individual TOs).
1.3.1 Task Area 1 – Contract Management. This task area shall encompass overall contract management to include administrative, clerical, documentation, and related functions. The contractor shall designate an individual from the contractor‘s resources to be the focal point for all contract management communications with
USTRANSCOM, and to be responsible for ensuring successful accomplishment of PWS tasks. Point of contact
(POC) information, to include name, title, phone number, and email address, are to be provided to the Contracting
Officer at the Post-Award Conference. In support of this task, the contractor may be requested to provide documents such as Task Order Management Plans (TOMP), Monthly Status Reports (MSR), In-Process Reviews (IPR), Integrated Management Schedules (IMS), Contract Summary Reports (CSR), and Variance Reports. The contractor may also be requested to provide demonstration and teleconference support.
1.3.2 Task Area 2 - Event and Exercise Support. Using off-site resources, the contractor shall provide technical support to USTRANSCOM for real-world events and Command Post Exercises (CPXs). Software development support for exercises may be required for approximately 50 days during the period of performance. This includes software troubleshooting and development in support of joint exercises. In addition, the contractor shall update the following DESS documentation to incorporate Spiral 7 requirements: Functional Documentation, System Documentation, Technical Documentation, DESS Architecture, External Interface Identification, External
Software Item Interface Definition, JFAST Operator‘s manual for simulation version, and JFAST - SUSGEN User‘s
Setup Guide. Note, the contractor-developed system shall be capable of operation at the SECRET level and compatible for operations across the SIPRNET.
1.3.3 Task Area 3 - Requirements Definition. The Functional Manager will provide a prioritized list of functional requirements to the PM, who then will provide these requirements to the contractor. The contractor shall coordinate and integrate the technical expertise required to construct the system and associated databases (if applicable), and support field testing in a limited operational environment.
1.3.4 Task Area 4 - Design and Development. The contractor shall design, develop, and test new system capabilities using commercial best practices appropriate to the JFAST functional requirements. For System
Development, the contractor shall:
Design, code, test, document and support full system integration of software and software releases (including software changes), assessments and prototypes supporting application development.
Propose release content and schedules based upon the known Government requirements and priorities.
Provide necessary models and simulations to support the verification and validation.
Provide software size, cost and schedule estimates and include justification and confidence level behind the estimates.
Continue to develop the Logical Data Model (LDM) in full compliance with DOD and USTRANSCOM data standards.
Deliver any developed corporate applications software artifacts to the Government.
1.3.5 Task Area 5 – Standards. JFAST is part of the JDDA-E. The JDDA-E consists of Conceptual, Prescriptive, and Transition Architectures, referred to collectively as the Enterprise Architecture (EA). The JDDA-E embodies the
Distribution Process Owner‘s (USTRANSCOM) Corporate Services Vision (CSV) and Service-Oriented
Architecture (SOA) concepts. Current governance, policy, architecture, standards, and specification documentation can be obtained by coordinating with the JFAST PMO, who, in turn, will contact USTRANSCOM J6-A. Other standards and specifications that are a part of the JDDA-E Prescriptive Architecture are being defined and will be made available after they are delivered. In the mean time, the contractor shall follow existing federal, DOD, and
USTRANSCOM guidelines. The JFAST contractor shall abide by the requirements of the Department of Defense
(DOD) Information Technology Standards Registry (DISR) and the DOD Net-Centric environment as reflected in the JDDA-E. The contractor shall show traceability to the DTS Enterprise Architecture (EA) content to include identifying anticipated standards, new Information Exchange Requirements (IER), and system interfaces. This traceability shall be reflected in DODAF products for which the contractor shall be responsible to develop or update.
DOD is implementing a Service-Oriented Architecture (SOA) environment to enhance net-centricity and data sharing within the Global Information Grid (GIG). As USTRANSCOM is in SOA discovery mode, the contractor shall consider SOA standards and protocols documented in the DISR and the Net-Centric Operations Warfare Reference
Model (NCOW RM) during system development and enhancement. A SOA is a design style for building flexible, adaptable distributed-computing environments for the DOD. Service-oriented design is fundamentally about sharing and reusing functionality across diverse applications. Service-oriented design focuses on the following best practices: Make application and system functionality as accessible and reusable services, Expose service functionality through programmatic interfaces, Maintain an abstraction layer between service interfaces and service implementations, Describe service interfaces using standard metadata, Advertise and discover services using standard service registries, and Communicate with services using standard protocols.
USTRANSCOM's Data Management Strategy is documented in the Information Reference Model Manual which is the governing document for Enterprise Information Management within the Command. This document outlines program responsibility in support of the strategy. It mandates the creation and use of Standard Message Templates and Standard Reference Data (USTRANSCOM Reference Data Management - TRDM). The Enterprise Data Office
(TC/J6-AD) will assist with the creation of the Standard Message Templates once validated through the Enterprise
Requirements Management process. The JFAST Contractor shall ensure JFAST data is submitted and compliant with USTRANSCOM‘s Distribution Process Interface Exchange Data Model (DPIEDM), and that no data business rule from that model is violated in the system, to include the database and interfaces.
1.3.6 Task Area 6 – Maintenance. The Contractor shall provide software, systems, and interface maintenance (e.g.
CFAST) in support of JFAST. In addition, the contractor shall support the installation of required hardware, communication lines, security and system software at the USTRANSCOM site.
1.3.7 Task Area 7 - System Administration (SA). The contractor shall provide on-site support to
USTRANSCOM / SA (s) for JFAST. The contractor SA support will include the following activities:
Plan, schedule and accomplish installation of new or modified hardware and software, to include system and security patches, updates, and enhancements for the system servers. Troubleshoot JFAST installation problems.
Support installation, optimization, operation, backup, recovery, modification, and upgrade of system servers and software and USTRANSCOM Classified Local Area Network (LAN) client workstations. Debug JFAST software and test software releases.
Monitor operational node performance and recommend possible improvements.
Accomplish routine system maintenance functions such as rebooting servers, running backups and coordinating hardware repair/replacement.
Troubleshoot and resolve system performance problems for system servers.
Provide technical support for system reengineering efforts.
Provide ―Help desk‖ support to assist system users troubleshoot and correct JFAST problems.
Distribute JFAST software and documentation to registered users and maintain a database of registered JFAST users.
Work with Government security and networking personnel on system-related issues.
Support the Execution and Effects Review activities and required updates.
Training.
Ad hoc support of TCC requirements.
The contractor shall update the system administration manual to support the system that includes account administration; server installation, configuration, and administration; software installation; obtaining, generating, and updating reference files, shared drives, and web pages; troubleshooting and resolving operating system conflicts;
maintaining logs; and creating reports, as required.
1.3.8 Task Area 8 – Information Assurance (IA). The contractor shall establish an IA Program to implement and sustain appropriate IA management, operational, and technical controls and processes as required to ensure compliance with DOD and Chairman Joint Chiefs of Staff (CJCS) requirements, and Joint Task Force – Global
Network Operations (JTF-GNO) taskings. The contractor shall submit for Government approval an overarching security plan that describes their strategy for implementation of IA and Industrial Security requirements throughout the life of the contract. The contractor shall ensure that information system security engineering (ISSE) is employed to develop or modify any IA component of the system architecture. Such modifications will be made in compliance with all analogous or interfacing IA component(s) of the GIG Architecture and will be designed to make maximum use of the DOD enterprise IA capabilities and services. The contractor shall also support periodic Government inspections and reviews to ensure compliance with DOD IA requirements throughout the contract performance period. Contractor IA Program capabilities shall include but not be limited to processes and procedures for vulnerability management, patch management, incident response, Information Condition (INFOCON), system and application security (to include testing), configuration management, risk management, design and situational awareness.
1.3.9 Task Area 9 - Contingency Operations. The Continuity of Operations Plan (COOP) defines the methodology for providing a back-up capability for system users in the event the primary capability is not available.
The contractor shall provide a Contingency Operations Document (contractor specific) that aligns with the
Government COOP. The contractor‘s Contingency Operations Document shall address SA and data storage support procedures at the recovery site. The hardware and software for the site will be Government furnished to include all maintenance and licenses. Commercial Off-the-Shelf (COTS) software versions will be the same as the versions used in the production environment.
1.3.10 Task Area 10 – Configuration Management. This support is required to meet the DIACAP and
USTRANSCOM technical and security requirements. The CM process facilitates orderly configuration identification, change identification and control, status reporting, and configuration auditing of product information for such beneficial purposes as to revise capability and improve performance, reliability, or maintainability; extend life; reduce cost; reduce risk and liability; or correct defects. CM ensures that changes take place in an identifiable and controlled process and do not adversely affect any properties of the other system or interfaces.
1.3.11 Task Area 11 – Enhancements. All projected changes and improvements to JFAST are identified as Fiscal
Year enhancements within Appendix D, Paragraphs 1.3.11.1 through 1.3.11.47. This work will be specified and completed on an individual task order basis.
1.4 Deliverables. Shall be specified and completed on an individual task order basis.
2.0 SERVICE DELIVERY SUMMARY. Shall be specified on individual task orders.
2.1 Inspection and Acceptance. A deliverable is a specific measurable, tangible, and verifiable activity, outcome, result, item, or product that the contractor may be required to provide and that will require formal Government acceptance and approval. The Government will review, assess and provide comment, as required. Unless otherwise specified under individual task order, final inspection and acceptance of all work performed, reports, or other deliverables shall be performed at the place of delivery. The PM will notify the contractor of deliverable acceptance or provide comments in writing. After receipt of government comments, the contractor, if necessary, shall revise and submit the final deliverable to the PM within the number of business days specified in the deliverable table within the individual task order.
3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES
3.1 Government Furnished Equipment (GFE). Shall be specified on individual task orders.
3.1.1 Mapping and Graphics. The Government will provide mapping and graphics updates, as required, to include: CADRGs covering GNC 1:5M, JNC 1:2M, ONC 1:1M, TPC 1:500K, JOG 1:250K, TLM (1:00K and
1:50K), DTEDs for selected AORs, and DFADs for global coverage of topological lines (highways, rail, waterways and air routes) on CD-ROMs.
3.1.2 Work Space, Material and Equipment. Government will provide controlled working space, computer, phone, fax, and connections to the NIPRNET or SIPRNET, as required, for on-site contractor support at no cost.
3.1.3 Software. The Government will provide a copy of ERwin database software. The Government also will continue to sponsor the FEDLOG subscription for continued manifesting at Level 6 and support of the Distribution
Environment Support System.
3.1.4. Secure Communications. The Government will provide the equipment and leased line to support the
SIPRNET connection in support of the SIPRNET requirement described in Paragraph 4.3.17 of this PWS.
3.1.5. Annual Inventory. The Government will conduct an on-site inventory of all GFE annually. The contractor shall provide a listing of all GFE assigned to this contract and provide a ‗hands on‘ tour of its facility.
4.0 GENERAL INFORMATION
4.1 Continuity of Services. The Contractor recognizes that the services under this contract are vital to the
Government and must be continued without interruption. In the event of a successor contractor and upon contract expiration, a transition period will be required for the continuity of JFAST services. The incumbent contractor agrees to exercise its best efforts and cooperation to affect an orderly and efficient transition with the successor.
4.2 Phase-In / Phase-Out Transition Period. The Contractor shall, upon the Contracting Officer‘s written notification, furnish phase-in / phase-out services for up to 90 days after the contract expires and negotiate in good faith a plan with the successor to ensure the required level of services are retained in operation of the JFAST program. This plan is subject to the Contracting Officer‘s approval and negotiation of reasonable costs.
4.3 Security (Physical, Personnel, Information, Industrial, Anti-terrorism and Force Protection
Requirements).
4.3.1 General Security Information. The overall classification of work associated with this PWS is at the
SECRET level. Contract employees who support this contract and who work in a classified environment or work with or in a work area containing SECRET data shall require SECRET clearance eligibility and access . Personnel requiring security clearances must possess the clearance prior to beginning work on any classified information. The contractor shall not divulge any financial, planning, programming, or budgeting information without the express consent of the Government. The contract work associated with this PWS deals directly with systems supporting current operations and decision making for the DPO.
4.3.2 Contract employees will be required to access classified areas and systems at various locations that require
SECRET eligibility. Contract employees with access to Information Assurance (IA) administrative privileges and/or who will monitor DoD IT systems or software as designated by DoD 8500.1 and 5200.2-R will be rated at ADP/IT-
II level for this contract.
4.3.3 Contract employees assigned at the Non-Critical Sensitive/ADP II rating require an ANACI (or acceptable periodic reinvestigation) favorably adjudicated (a favorable adjudication grants eligibility at the SECRET level as prescribed by DoD 5200.2-R). The contractor shall ensure that individuals assigned have completed the appropriate forms. The required investigation will be completed prior to the assignment of individuals to sensitive duties associated with the positions. The ADP II rating requirement mandates the company awarded the contract have a minimum Facilities Clearance Level (FCL) rated at SECRET, which is outlined in section 4.3.5 of this PWS as directed in DoD 5220.22-M.
4.3.4 Contract employees shall have completed favorably an investigation resulting in SECRET eligibility adjudicated by the Defense Industrial Security Clearance Office (DISCO). The Government will accept an Interim
SECRET clearance provided it was granted by the Defense Industrial Security Clearance Office (DISCO).
4.3.5 The company that is awarded the contract must have a valid Facilities Clearance Level (FCL) at SECRET level. Interim FCL‘s are acceptable provided they are not expired. FCL procedures and security guidelines for adjudicative requirements are outlined in DoD 5220.22-M and DoD 5200.2-R. FCL‘s and Interim FCL‘s must be awarded by the Defense Security Service (DSS) or DISCO. USTRANSCOM will not sponsor the company awarded the contract for an FCL. The company awarded the contract must possess an interim or final FCL before the start of the contract.
4.3.6 Personnel assigned to this PWS who do not require access to classified material but will still work in support of this contract on the deliverables or who will require access to Non-Secure Internet Protocol Router Network
(NIPRNET) applications and/or who will require Common Access Cards (CAC), must successfully complete a
National Agency Check with Inquiries (NACI) or suitable investigation meeting the NACI level or equivalent.
Favorable NACI or equivalent investigation results must be posted in the Joint Personnel Adjudication System
(JPAS). Before a CAC or NIPRNET access is issued the NACI must be opened and fingerprint and name check returned favorably. NACI submissions will be completed on the Standard Form (SF) 85P and submitted with fingerprint cards (FP 258) to USTRANSCOM Force Protection, Security Services Center (SSC).
4.3.7 Upon contract award, the contractor will submit all names of contract employees to the USTRANSCOM
Security Services Center (SSC) for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. This will be completed before the Contract Officer Representative (COR) / Trusted Agent (TA) accesses the DoD Contract Verification System (CVS) and submits requests for issuance of Common Access Cards
(CAC) to the contract employees. If a contract employee does not have the required investigative or security clearance level, the contract employee will be denied the ability to work in support of this PWS, and the employee‘s information will not be loaded into CVS.
4.3.8 Upon notification by the SSC that contract personnel meet the required investigative and clearance level, personnel will be loaded in CVS for an expiration on their CAC for the base year, plus two option years, for a three year total, if the contract is fully funded. If the contract is unfunded or funded on a yearly basis requiring recertification of funding by USTRANSCOM AQ or J8, CAC‘s will only be loaded for the base contract or option year only.
4.3.9 Upon receipt of the CAC, permanently assigned contract employees located at USTRANSCOM at SAFB, IL, may obtain the AF 1199 (Restricted Area Badge) if the employee meets the requirements set forth in the SAFB
Instruction 31-101. Only personnel assigned physically on SAFB at least 4 days a week will be issued the AF 1199 unless an exception to policy is approved by the 375 th
SFS through the USTRANSCOM SSC. In addition, the contractor is required to provide contractor (company) identification badges for its on-site employees. All contractor personnel shall wear these badges while on duty on the Government site. Contractor (company) identification badges are required to identify the individual, company name, and are clearly and distinctly marked as contractor.
The contractor and Government shall mutually agree on badge size, color, style, etc. The Government will provide unrestricted access to facilities, consistent with security clearance and need to know, necessary for the on-site person to perform his or her contractual job. Contractor personnel assigned on-site at USTRANSCOM shall wear and display both the contractor identification badge and Restricted Area Badge at all times.
4.3.10 Any visit(s) by contract employees not permanently assigned to this contract (company presidents, company security managers, contract employees not permanently assigned at SAFB, etc.) will require an electronic visit request be submitted using the Joint Personnel Adjudication Systems (JPAS).
4.3.11 Upon completion of this contract, the employee will surrender all government supplies, materials and equipment to the COR. All contract employees assigned to this contract who possess CAC cards shall return these cards to the COR at SAFB for turn-in to the USTRANSCOM Security Services Center (SSC). Assigned contract employees who possess any security badges shall turn these badges in to the SSC in person during out-processing.
Contract employees shall out-process on the last day of the contract or upon termination or reassignment from duties on this contract.
4.3.12 If the contract employee physically works at USTRANSCOM at SAFB, IL, this employee shall complete a security debriefing statement (Standard Form 312) upon completion of the contract.
4.3.13 Contract employees assigned to USTRANSCOM at SAFB, IL. shall attend and complete Employee Initial
Security Briefing and Annual Security Awareness Training as prescribed by DOD, USTRANSCOM and Air Force
Instructions. All contract employees, regardless of place of assignment, shall complete the annual DoD
Antiterrorism Level 1 training. Contract employees assigned elsewhere shall attend security training established by their respective government security offices and/or installations.
4.3.14 The Government shall ensure the roles/privileges assigned to contract employees on the Government computing platforms are limited to the roles/privileges essential to that individual‘s performance of his/her assignments. The Government may limit or revoke these roles or privileges for any reason.
4.3.15 If the Government notifies the contractor that the employment or the continued employment of any contract employee is prejudicial to the interests or endangers the security of the United States of America, that person shall be removed and barred from the worksite. This includes security deviations/incidents and credible derogatory information on contract members during the course of the contract period. The contractor shall make any changes necessary in the appointment(s).
4.3.16 Responsibility for offsite contractor‘s compliance with internal security for a Command, Control, Communications, and Computer (C ) system site shall be assigned to the contractor. All contractor personnel shall be briefed on site security operating procedures prior to or upon commencement of contract award and shall be debriefed upon termination. The contractor shall be responsible for all continuing security training of the contractor personnel.
4.3.17 Secure Internet Protocol Router Network. It is a requirement of this contract that the contractor use a secure SIPRNET network connection, maintained at the contractor‘s facility in a secure space IAW DoDI 5200.1-R, Appendix 7. The Government will provide the equipment and leased line to support the SIPRNET connection.
Before the SIPRNET is established in the contractor‘s location the contractor must have a physical safeguarding rating at the SECRET level from DSS.
4.3.18 Non-Public Information. In performance of this contract, the contractor may obtain access to sensitive, non-public information. The contractor agrees (a) to use and protect such information from unauthorized disclosure in accordance with the FAR; (b) to use and disclose such information only for the purpose of performing this contract and to not use or disclose such information for any personal or commercial purpose; (c) to obtain permission of the Government PM before disclosing/discussing such information with a third party; (d) to return, upon
Government request, any non-public, sensitive information no longer required for contractor performance; and (e) to advise the Government PM of any unauthorized release of such information. Upon request, the contractor shall have its employees assigned to this contract execute a non-disclosure agreement for delivery to the Government. The
Government will require contractor personnel to sign a non-disclosure statement to protect non-public information of other contractors and/or the Government (see Appendix B, ―Non-Disclosure Agreement‖). This is also covered in the DD 254 for disclosure approvals authorities.
4.3.19 Employment of Foreign Nationals. For purposes of this clause, foreign nationals are all persons not citizens of, not nationals of, or immigrant aliens to the US. A foreign representative is anyone (regardless of nationality) acting as an agent, representative, official, or employee of a foreign government, a foreign-owned or influenced firm, corporation, or person. Nothing in this clause is intended to waive any requirement imposed by any other US Government agency with respect to employment of foreign nationals or export control. Foreign Nationals are not allowed to access classified information, nor are they allowed to fill ADP-I positions as defined in regulation
DOD 5200.2-R, Personnel Security Regulation, Appendix 10.
4.3.20 Security Regulation Compliance. The contractor shall comply with all security regulations and directives as identified herein and other security requirements in this contract specific to site locations of work. Upon contract start of contract employees shall attend security training required by this PWS in section 4.3.13.
Security Regulation Guidance:
Department of Defense (DoD):
2000.16 (DoD Antiterrorism (AT) Standards)
5200.1-R (DoD Information Security Program)
5200.2-R (DoD Personnel Security Program)
5200.08-R (DoD Physical Security Program)
5220.22-M (National Industrial Security Program)
8500.1 (Information Assurance (IA))
2000.12 (DoD Antiterrorism (AT) Program)
8500.2 (Information Assurance (IA) Implementation)
DoD regulations found at:
http://www.dtic.mil/whs/directives/corres/pub1.html
Scott Air Force Base:
SAFB Instruction 31-101 (Installation Security Instruction)
(Restricted publication. Send only to .mil domains when forwarding. Not for public distribution.)
Forms:
DD 254, DoD, Contract Security Classification Specification
DoD forms found at:
http://www.dtic.mil/whs/directives/corres/pub1.html
USTRANSCOM Force Protection (Industrial Security) Points of Contact:
Patrick Collins or Steven Strait
508 Scott Drive
TCJ3-FP
Scott AFB, IL. 62225
Commercial: 618-229-7349/8287 (respectively)
Email at Patrick.Collins@ustranscom.mil or Steven.Strait@ustranscom.mil
4.4 Place of Performance. The primary place of performance may take place either at the Contractor‘s location, in
Government facilities, or as mutually agreed between the Contractor and the Government. The place of performance shall be identified on each individual task order.
4.5 Travel. Task order performance will require contractor travel within and outside the Continental United States
(CONUS/OCONUS)( Appendix C). The Government will reimburse the contractor for travel expenses subject to the
Federal Acquisition Regulation (FAR) and Federal Travel Regulation (FTR). All contractor travel shall be coordinated with and validated by the COR prior to incurring any travel expenses. Travel requests shall be submitted in writing at least five (5) business days in advance from the travel commencement date consisting of:
Title, Purpose/Objective, Expected Outcome, Date, Time (window), Location, Proposed Itinerary, Proposed
Meeting/Activities Agenda, Number of Contractor Participants, Desired Government Participants, Requested
Government Support, and Estimated Costs.
The contractor shall identify personnel who will be traveling in sufficient time to obtain the lowest possible rates for airfare, rental car and lodging. Contractor invoices (along with associated receipts) shall support all travel reimbursement requests. The Government will not reimburse local travel and related expenses to the contractor for daily travel to or from the place of performance stipulated in each individual task order. Contractors shall not use
General Services Administration city pair contracts.
4.6 Hours of Operation. Unless specified within the individual task orders, normal duty hours are between 0730 and 1630, Monday through Friday, with the exception of Federal holidays. If on-site contractor personnel deem it necessary to work outside normal duty hours, it must be coordinated with the COR assigned to the task order. The following will be observed as Federal holidays: New Year's Day, Martin Luther King's Birthday, President's Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veteran's Day, Thanksgiving Day, and Christmas http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html mailto:Patrick.Collins@ustranscom.mil mailto:Steven.Strait@ustranscom.mil
Day. Note: Any of the above holidays falling on a Saturday shall be observed on the preceding Friday. Holidays falling on a Sunday shall be observed on the following Monday.
4.7 Other Direct Costs (ODC). The Government will reimburse other direct costs incurred in performance of the task orders. All ODCs shall be coordinated with and approved by the primary or alternate COR prior to incurring the expense. ODC requests shall be submitted in writing to the COR at least five (5) business days in advance with supporting documentation of the (estimated) cost. The Contractor may be required to submit at least three quotes for high dollar valued items. Contractor invoices (along with associated receipts) shall support all ODC reimbursement requests. Not all tasks may require ODCs. In addition, General and Administrative overhead charges will not be accepted or paid for approved ODC purchases.
4.8 Period of Performance. The period of performance for this contract will consist of a base period with three option year periods: Base Year (1 Oct 2009 - 30 Sep 2010), Option Year I (Oct 2010 - 30 Sep 2011), Option Year
II (1 Oct 2011 – 30 Sep 2012) and Option Year III (1 Oct 2012 – 30 Sep 2013).
4.9 List of Appendices.
APPENDIX TITLE
A List of Acronyms
B Non-Disclosure Agreement
C Travel
D Enhancements
4.10 Section 508 Accessibility Standards. The following Section 508 Accessibility Standard(s) (Technical
Standards and Functional Performance Criteria) are applicable (if box is checked) to this acquisition.
Technical Standards
1194.21 - Software Applications and Operating Systems
1194.22 - Web Based Intranet and Internet Information and Applications
1194.23 - Telecommunications Products
1194.24 - Video and Multimedia Products
1194.25 - Self-Contained, Closed Products
1194.26 - Desktop and Portable Computers
1194.41 - Information, Documentation and Support
The Technical Standards above facilitate the assurance that the maximum technical standards are provided to the
Offerors. Functional Performance Criteria is the minimally acceptable standards to ensure Section 508 compliance.
This block is checked to ensure that the minimally acceptable Electronic and Information Technology (E&IT) products are proposed.
Functional Performance Criteria
1194.31 - Functional Performance Criteria
4.11 Small Business Commitment. If award is made to a large business, verification of subcontracting goals will be accomplished thru eSRS. If award is made to a small business, verification of subcontracting goals will be accomplished via a semi-annual report from contractor to the contracting officer. Report format will be determined at the post-award conference. A small business prime contractor may use their work performance to meet the small business commitment.
APPENDIX A
List of Acronyms
TERM DEFINITION
AAR After Action Review
ADP Automated Data Processing
AIS Automated Information System
AMC Air Mobility Command
APOD Aerial Port of Debarkation
A/R Air Refueling
A/SPOE Aerial/Sea Port of Embarkation
BCR Baseline Change Request
C Command, Control, Communications and Computer
CAA Center for Army Analysis
CD Compact Disk
CDO Corporate Data Office
CCB Configuration Control Board
CFAST Collaborative Force-Building Analysis, Sustainment and Transportation
CLIN Contract Line Item Number
CM Configuration Management
CMB Configuration Management Board
CMP Configuration Management Plan
CND Computer Network Defense
CO Contracting Officer
COR Contracting Officer‘s Representative
COCOM Combatant Command
CONOPS Concept of Operations
CONPLAN Concept Plan
COOP Continuity of Operations Plan
COR Contracting Officer‘s Representative
COTS Commercial Off-the-Shelf
CPX Command Post Exercise
CR Change Request
CRB Configuration Review Board
CSR Contract Summary Report
DCAPES Deliberate and Crisis Action Planning Execution System
DESS Distribution Environment Support System
DEX Data Exchange
DIACAP DOD Information Assurance Certification and Accreditation Process
DIP DIACAP Implementation Plan
DISA Defense Information Systems Agency
DISCO Defense Industrial Security Office
DISR DOD Information Technology Standards Registry
DPIEDM Distribution Process Interface Exchange Data Model
DOD Department of Defense
DODAF DOD Architecture Framework
DODX DOD-owned rail cars
DPO Distribution Process Owner
DSS Defense Security Service
DT&E Developmental Test and Evaluation
DTS Defense Transportation System
DVD Digital Video Disk
E&IT Electronic and Information Technology
EA Enterprise Architecture eMASS Enterprise Mission Assurance Support Service
ETA Estimated Time of Arrival
ETAP Education, Training, and Awareness Program
ETD Estimated Time of Departure
FAR Federal Acquisition Regulation
FIC Force Indicator Code
FIPS Federal Information Processing Standards
FISMA Federal Information Security Management Act
FM Functional Manager
FMID Force Module Identifier
FRB Functional Review Board
FSS Fast Sealift Ship
FTR Federal Travel Regulation
GATES Global Air Transportation Execution System
GDSS Global Decision Support System
GEO Geographic
GEOLOC Geographic Location
GES Global Transportation Network Exercise System
GFE Government-Furnished Equipment
GIG Global Information Grid
GIS Graphical Information System
IA Information Assurance
IA&ISP Information Assurance and Industrial Security Plan
IASAE Information Assurance, Security Architecture and Engineering
ICD Interface Control Document
IER Interface Exchange Requirement
ILOC Intermediate Locations
IMS Integrated Management Schedule
INFOCON Information Condition
IPR In-Process Review
IRDD Interface Requirement Design Document
IRS Interface Requirement Specifications
ISA Interconnection Security Agreement
ISP Information Security Plan
ISR Intelligence/Surveillance/Reconnaissance
ISSE Information system Security Engineering
JCS Joint Chiefs of Staff
JDDA-E Joint Deployment and Distribution Architecture – Enhanced
JDDE Joint Deployment and Distribution Enterprise
JDLM Joint Deployment Logistics Model
JFAST Joint Flow and Analysis System for Transportation
JLAT Joint Logistics Analysis Tool
JPEC Joint Planning and Execution Community
JOPES Joint Operation Planning and Execution System
JTF-GNO Joint Task Force – Global Network Operations
LAN Local Area Network
LDM Logical Data Model
LMSR Large Medium Speed Roll On/Roll Off
M&S Modeling and Simulation
MAC Mission Assurance Category
MOA Memorandums of Agreement
MSC Military Sealift Command
MTON Measurement Ton
MSR Monthly Status Report
NCOW RM Net-Centric Operations Warfare Reference Model
NEO Non-Combatant Evacuation Operations
NIPRNET Non-Secure Internet Protocol Router Network
NISC Naval Intelligence Service Code
NISPOM National Industrial Security Program
NLT No Later Than
NORAD North American Aerospace Defense Command
NSN National Stock Number
OCONUS Outside the Continental United States
ODC Other Direct Costs
OV Operational View
PAX Passengers
PID Plan Identification
PK Public Key
PM Program Manager
POA&M Plan of Action and Milestones
POC Point of Contact
POD Port of Debarkation
POE Port of Embarkation
POL Petroleum, Oil, and Lubricants
POP Period of Performance
PPSM Ports, Protocols, and Services Management
PWS Performance Work Statement
QA Quality Assurance
RLN Requirement Line Number
RO/RO Roll On/Roll Off
SA System Administration
SDDC Surface Deployment and Distribution Command
SDS Service Delivery Schedule
SIP System Identification Profile
SIPRNET Secret Internet Protocol Router Network
SOA Service-Oriented Architecture
SOP Standard Operating Procedure
SPI Systems, Programs and Initiatives
SPOD Sea Port of Debarkation
SPOE Sea Port of Embarkation
SRS Software Requirement Specifications
ST&E Security Test and Evaluation
STIG Security Technical Implementation Guide
SUSGEN Sustainment Generator
SV System View
TCC Transportation Component Command
TIES Transactional Interface to External Systems
TO Task Order
TOMP Task Order Management Plan
TPFDD Time-Phased Force and Deployment Data
TRDM USTRANSCOM Reference Data Management
TTF Tanker Task Force
TTFM Total Transportation Feasibility Module
TUCHA Type Unit Characteristics
TV Technical View
ULN Unit Line Number
UML Universal Modeling Language
UTC Unit Type Code
USJFCOM United States Joint Forces Command
USTRANSCOM United States Transportation Command
VDD Version Description Document
VISA Voluntary Intermodal Sealift Agreement
WFM War Fight Model
WPS Worldwide Port System
XML Extensible Markup Language
APPENDIX B
NON-DISCLOSURE AGREEMENT
FOR CONTRACTOR EMPLOYEES ON USTRANSCOM CONTRACTS
NOTE: This Non-Disclosure Agreement is a standard agreement designed for use by contractor (including subcontractor) employees assigned to work on USTRANSCOM contracts. Its use is designed to protect non-public
Government information from disclosure and prevent violations of federal statutes/regulations. The restrictions contained in this agreement also serve contractors by promoting compliant behavior that keeps contractors eligible to compete for Government contracts. In addition to the potential impact on future business opportunities, failure to abide by this agreement could result in administrative, civil or criminal penalties specified by statute or regulation.
1. I, currently an employee of , hereby agree to the terms and conditions set forth below:
2. I understand that I will have access to confidential business information (as defined by 18 USC 1905), contractor bid or proposal information (as defined by FAR 3.104-3), and/or source selection sensitive information (as defined by FAR 3.104-3) either for contract performance or as a result of working in a USTRANSCOM facility or of working near USTRANSCOM personnel, contractors, visitors, etc. I fully understand that such information is sensitive and must be protected in accordance with 41 U.S. Code Section 423 and 18 U.S. Code Section 1905 and
FAR Part 3. I also certify that I do not have any real or apparent conflicts of interest with respect to the information disclosed. If any potential conflicts of interest, real or otherwise, do present themselves, then I shall immediately disclose the pertinent information that may be a potential conflict to an agency ethics official who shall review the circumstances.
3. In the course of performing under contract/order # or some other contract or subcontract for the USTRANSCOM, I agree to:
a) Use only for Government purpose any and all confidential business information, contractor bid or proposal information, and/or source selection sensitive information to which I am given access. I agree not to disclose ―non-public information‖ by any means (in whole or in part, alone or in combination with other information, directly or indirectly or derivatively) to any person except to a U.S. Government official with a need to know or to a non-
Government person (including, but not limited to, a person in my company, affiliated companies, subcontractors, etc.)…
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 .