Conformed_HTC711-13-R-D012_(includes_Amendment_1).pdf
PDF 2 MB Posted
- Attached to
- Single Mobility System (SMS)/Coalition Mobility System (CMS) Federal contract opportunity
- Solicitation number
- HTC711-13-R-D012
About this file
Conformed Copy HTC711-13-R-D012 (includes Amendment 1)
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Conformed_HTC711-13-R-D012_(includes_all_Amendments).pdf | ||
| Atch_10_-_DODAF_SV6_ _AV1_Draft_Documents.pdf | ||
| Atch_4_-_Labor_Rates_-_Price_Proposal_Break_out.xlsx | XLSX spreadsheet | |
| Questions_and_Answers_2_(all_inclusive).pdf | ||
| Amendment_2_-_HTC711-13-R-D012.pdf | ||
| Questions_and_Answers_1.pdf | ||
| Amendment_1_-_HTC711-13-R-D012.pdf | ||
| Atch_4_-_Labor_Rates_-_Price_Proposal_Break_out.xlsx | XLSX spreadsheet | |
| Atch_7_-_PP_Log.doc | DOC document | |
| Atch_9_-_Subcontracting_Plan_Template.doc | DOC document | |
| Atch_5_-_PP_Reference_Sheet.docx | DOCX document | |
| Atch_2_-_SMS-CMS_QASP.pdf | ||
| Atch_3_-_SMS_CMS_CDRLs.pdf | ||
| Atch_1_-_DD254.pdf | ||
| Atch_6_-_PP_Questionnaire.docx | DOCX document | |
| Atch_8_-_PWS_Sections_to_CLIN_Mapping_Table_(For_Info._only).pdf | ||
| HTC711-13-R-D012_-_RFP.pdf | ||
| SMS_CMS_PWS_FY14-18_-_9_May_13_(DRAFT).pdf |
Show all 18
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
HTC711-13-R-D012
CODE
(Hour)
PAGE(S)
until 02:00 PM local time 29 Jul 2013
X
A
X B
X C X D
EX
X
G
F 127 - 140
141 - 149
X H 150 - 155 chastity .hill@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 155
(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
See Instructions to Offerors conditions contained in this solicitation.
10. FOR INFORMATION
CALL:
A. NAME (NO COLLECT CALLS)
CHASTITY R. HILL 618-220-7073
11. TABLE OF CONTENTS
SOLICITATION/ CONTRACT FORM
SUPPLIES OR SERVICES AND PRICES/ COSTS
2 - 32
X I CONTRACT CLAUSES
DESCRIPTION/ SPECS./ WORK STATEMENT X
PACKAGING AND MARKING
33 - 97
J LIST OF ATTACHMENTS
INSPECTION AND ACCEPTANCE
DELIVERIES OR PERFORMANCE
99 - 100
101 - 104 X K
REPRESENTATIONS, CERTIFICATIONS AND
OTHER STATEMENTS OF OFFERORS
CONTRACT ADMINISTRATION DATA 105 - 109 X
SPECIAL CONTRACT REQUIREMENTS
OFFER (Must be fully completed by offeror) 110 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
111 - 125
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
27 Jun 2013
4. TYPE OF SOLICITATION
SEALED BID (IFB)
NEGOTIATED (RFP)
[ X ]
3. SOLICITATION NO.
Section B - Supplies or Services and Prices
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
0001 Months SMS Sustainment
FFP
SMS ONLY Related Tasks in PWS Para’s 1.4.1 (excluding 1.4.1.4), 1.4.2
(excluding 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.1.1.6, 1.4.2.1.1.7, 1.4.2.3.2.a), 1.4.3.3, 1.4.4 (excluding 1.4.4.1.a), 1.4.8, 1.4.9
Period of Performance: 1 October 13 - 30 September 14
FOB: Destination
SIGNAL CODE: A
NET AMT
ITEM NO SUPPLIES/SERVICES ESTIMATED
QUANTITY
UNIT UNIT PRICE AMOUNT
0002 Lot SMS Sustainment
LH
PWS Para: 1.4.1.4.a, 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.3.2.a, 1.4.4.1.a
Period of Performance: 1 October 13 - 30 September 14
TOT ESTIMATED PRICE
CEILING PRICE
QUANTITY
UNIT UNIT PRICE AMOUNT
0003 Lot SMS Web Services
LH
PWS Para: 1.4.2.1.1.6
Period of Performance: 1 October 13 - 30 September 14
0004 Months SMS Functional Support
FFP
PWS Para: 1.4.3.5.1.1, 1.4.3.5.2 (excluding 1.4.3.5.2.e)
Period of Performance: 1 October 13 - 30 September 14
QUANTITY
UNIT UNIT PRICE AMOUNT
0005 Lot SMS Functional Support
LH
PWS Para: 1.4.3.1 – 1.4.3.4 (excluding 1.4.3.3), 1.4.3.5.1.a, 1.4.3.5.2.e
Period of Performance: 1 October 13 - 30 September 14
UNIT UNIT PRICE AMOUNT
0006 Lot SMS AFRC Sustainment
LH
PWS Para: 1.4.5
Period of Performance: 30 September 13 - 29 September 14
QUANTITY
UNIT UNIT PRICE AMOUNT
0007 Lot
SMS - SA&C
LH
PWS Para: 1.4.2.1.1.7
Period of Performance: 1 October 13 - 30 September 15
0008 Months OPTIONAL - Cyber Security
FFP
PWS Para: 1.4.7
Period of Performance: 1 October 13 - 30 September 14
0009 Lot SMS Travel / ODC
COST
PWS Para: 4.2
Period of Performance: 1 October 13 - 30 September 14
Cost: $20,000.00
ESTIMATED COST
0010 Lot SMS AFRC Travel
COST
Period of Performance: 30 September 13 - 29 September 14
Cost: $10,000.00
0011 Months CMS Sustainment
FFP
CMS ONLY related tasks in para’s 1.4.1 (excluding 1.4.1.4), 1.4.2 (excluding
1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c), 1.4.3 (excluding 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e), 1.4.4 (excluding 1.4.4.2.b), 1.4.6, 1.4.8, 1.4.9
Period of Performance: 30 September 13 - 29 September 14
UNIT UNIT PRICE AMOUNT
0012 Lot CMS Sustainment
LH
PWS Para: 1.4.1.4.b, 1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c, 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e, 1.4.4.2.b
Period of Performance: 30 September 13 - 29 September 14
0013 Lot CMS Travel / ODC
COST
Period of Performance: 30 September 13 - 29 September 14
1001 Months OPTION SMS Sustainment
FFP
SMS ONLY Related Tasks in PWS Para’s 1.4.1 (excluding 1.4.1.4), 1.4.2
(excluding 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.1.1.6, 1.4.2.1.1.7, 1.4.2.3.2.a), 1.4.3.3, 1.4.4 (excluding 1.4.4.1.a), 1.4.8, 1.4.9
Period of Performance: 1 October 14 - 30 September 15
QUANTITY
UNIT UNIT PRICE AMOUNT
1002 Lot OPTION SMS Sustainment
LH
PWS Para: 1.4.1.4.a, 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.3.2.a, 1.4.4.1.a
Period of Performance: 1 October 14 - 30 September 15
UNIT UNIT PRICE AMOUNT
1003 Lot OPTION SMS Web Services
LH
PWS Para: 1.4.2.1.1.6
Period of Performance: 1 October 14 - 30 September 15
1004 Months OPTION SMS Functional Support
FFP
PWS Para: 1.4.3.5.1.1, 1.4.3.5.2 (excluding 1.4.3.5.2.e)
Period of Performance: 1 October 14 - 30 September 15
UNIT UNIT PRICE AMOUNT
1005 Lot OPTION SMS Functional Support
LH
PWS Para: 1.4.3.1 – 1.4.3.4 (excluding 1.4.3.3), 1.4.3.5.1.a, 1.4.3.5.2.e
Period of Performance: 1 October 14 - 30 September 15
QUANTITY
UNIT UNIT PRICE AMOUNT
1006 Lot OPTION SMS AFRC Sustainment
LH
PWS Para: 1.4.5
Period of Performance: 30 September 14 - 29 September 15
1008 Months OPTION OPTIONAL - Cyber Security
FFP
PWS Para: 1.4.7
Period of Performance: 1 October 14 - 30 September 15
1009 Lot OPTION SMS Travel / ODC
COST
Period of Performance: 1 October 14 - 30 September 15
1010 Lot OPTION SMS AFRC Travel
COST
Period of Performance: 30 September 14 - 29 September 15
1011 Months OPTION CMS Sustainment
FFP
CMS ONLY related tasks in para’s 1.4.1 (excluding 1.4.1.4), 1.4.2 (excluding
1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c), 1.4.3 (excluding 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e), 1.4.4 (excluding 1.4.4.2.b), 1.4.6, 1.4.8, 1.4.9
Period of Performance: 30 September 14 - 29 September 15
UNIT UNIT PRICE AMOUNT
1012 Lot OPTION CMS Sustainment
LH
PWS Para: 1.4.1.4.b, 1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c, 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e, 1.4.4.2.b
Period of Performance: 30 September 14 - 29 September 15
1013 Lot OPTION CMS Travel / ODC
COST
Period of Performance: 30 September 14 - 29 September 15
2001 Months OPTION SMS Sustainment
FFP
SMS ONLY Related Tasks in PWS Para’s 1.4.1 (excluding 1.4.1.4), 1.4.2
(excluding 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.1.1.6, 1.4.2.1.1.7, 1.4.2.3.2.a), 1.4.3.3, 1.4.4 (excluding 1.4.4.1.a), 1.4.8, 1.4.9
Period of Performance: 1 October 15 - 30 September 16
QUANTITY
UNIT UNIT PRICE AMOUNT
2002 Lot OPTION SMS Sustainment
LH
PWS Para: 1.4.1.4.a, 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.3.2.a, 1.4.4.1.a
Period of Performance: 1 October 15 - 30 September 16
UNIT UNIT PRICE AMOUNT
2003 Lot OPTION SMS Web Services
LH
PWS Para: 1.4.2.1.1.6
Period of Performance: 1 October 15 - 30 September 16
2004 Months OPTION SMS Functional Support
FFP
PWS Para: 1.4.3.5.1.1, 1.4.3.5.2 (excluding 1.4.3.5.2.e)
Period of Performance: 1 October 15 - 30 September 16
UNIT UNIT PRICE AMOUNT
2005 Lot OPTION SMS Functional Support
LH
PWS Para: 1.4.3.1 – 1.4.3.4 (excluding 1.4.3.3), 1.4.3.5.1.a, 1.4.3.5.2.e
Period of Performance: 1 October 15 - 30 September 16
QUANTITY
UNIT UNIT PRICE AMOUNT
2006 Lot OPTION SMS AFRC Sustainment
LH
PWS Para: 1.4.5
Period of Performance: 30 September 15 - 29 September 16
2008 Months OPTION OPTIONAL - Cyber Security
FFP
PWS Para: 1.4.7
Period of Performance: 1 October 15 - 30 September 16
2009 Lot OPTION SMS Travel / ODC
COST
Period of Performance: 1 October 15 - 30 September 16
2010 Lot OPTION SMS AFRC Travel
COST
Period of Performance: 30 September 15 - 29 September 16
2011 Months OPTION CMS Sustainment
FFP
CMS ONLY related tasks in para’s 1.4.1 (excluding 1.4.1.4), 1.4.2 (excluding
1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c), 1.4.3 (excluding 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e), 1.4.4 (excluding 1.4.4.2.b), 1.4.6, 1.4.8, 1.4.9
Period of Performance: 30 September 15 - 29 September 16
UNIT UNIT PRICE AMOUNT
2012 Lot OPTION CMS Sustainment
LH
PWS Para: 1.4.1.4.b, 1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c, 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e, 1.4.4.2.b
Period of Performance: 30 September 15 - 29 September 16
2013 Lot OPTION CMS Travel / ODC
COST
Period of Performance: 30 September 15 - 29 September 16
3001 Months OPTION SMS Sustainment
FFP
SMS ONLY Related Tasks in PWS Para’s 1.4.1 (excluding 1.4.1.4), 1.4.2
(excluding 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.1.1.6, 1.4.2.1.1.7, 1.4.2.3.2.a), 1.4.3.3, 1.4.4 (excluding 1.4.4.1.a), 1.4.8, 1.4.9
Period of Performance: 1 October 16 - 30 September 17
QUANTITY
UNIT UNIT PRICE AMOUNT
3002 Lot OPTION SMS Sustainment
LH
PWS Para: 1.4.1.4.a, 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.3.2.a, 1.4.4.1.a
Period of Performance: 1 October 16 - 30 September 17
UNIT UNIT PRICE AMOUNT
3003 Lot OPTION SMS Web Services
LH
PWS Para: 1.4.2.1.1.6
Period of Performance: 1 October 16 - 30 September 17
3004 Months OPTION SMS Functional Support
FFP
PWS Para: 1.4.3.5.1.1, 1.4.3.5.2 (excluding 1.4.3.5.2.e)
Period of Performance: 1 October 16 - 30 September 17
UNIT UNIT PRICE AMOUNT
3005 Lot OPTION SMS Functional Support
LH
PWS Para: 1.4.3.1 – 1.4.3.4 (excluding 1.4.3.3), 1.4.3.5.1.a, 1.4.3.5.2.e
Period of Performance: 1 October 16 - 30 September 17
QUANTITY
UNIT UNIT PRICE AMOUNT
3006 Lot OPTION SMS AFRC Sustainment
LH
PWS Para: 1.4.5
Period of Performance: 30 September 16 - 29 September 17
3008 Months OPTION OPTIONAL - Cyber Security
FFP
PWS Para: 1.4.7
Period of Performance: 1 October 16 - 30 September 17
3009 Lot OPTION SMS Travel / ODC
COST
Period of Performance: 1 October 16 - 30 September 17
3010 Lot OPTION SMS AFRC Travel
COST
Period of Performance: 30 September 16 - 29 September 17
3011 Months OPTION CMS Sustainment
FFP
CMS ONLY related tasks in para’s 1.4.1 (excluding 1.4.1.4), 1.4.2 (excluding
1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c), 1.4.3 (excluding 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e), 1.4.4 (excluding 1.4.4.2.b), 1.4.6, 1.4.8, 1.4.9
Period of Performance: 30 September 16 - 29 September 17
UNIT UNIT PRICE AMOUNT
3012 Lot OPTION CMS Sustainment
LH
PWS Para: 1.4.1.4.b, 1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c, 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e, 1.4.4.2.b
Period of Performance: 30 September 16 - 29 September 17
3013 Lot OPTION CMS Travel / ODC
COST
Period of Performance: 30 September 16 - 29 September 17
4001 Months OPTION SMS Sustainment
FFP
SMS ONLY Related Tasks in PWS Para’s 1.4.1 (excluding 1.4.1.4), 1.4.2
(excluding 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.1.1.6, 1.4.2.1.1.7, 1.4.2.3.2.a), 1.4.3.3, 1.4.4 (excluding 1.4.4.1.a), 1.4.8, 1.4.9
Period of Performance: 1 October 17 - 30 September 18
QUANTITY
UNIT UNIT PRICE AMOUNT
4002 Lot OPTION SMS Sustainment
LH
PWS Para: 1.4.1.4.a, 1.4.2.1.1.a, 1.4.2.1.1.1, 1.4.2.1.1.2.b, 1.4.2.3.2.a, 1.4.4.1.a
Period of Performance: 1 October 17 - 30 September 18
UNIT UNIT PRICE AMOUNT
4003 Lot OPTION SMS Web Services
LH
PWS Para: 1.4.2.1.1.6
Period of Performance: 1 October 17 - 30 September 18
4004 Months OPTION SMS Functional Support
FFP
PWS Para: 1.4.3.5.1.1, 1.4.3.5.2 (excluding 1.4.3.5.2.e)
Period of Performance: 1 October 17 - 30 September 18
UNIT UNIT PRICE AMOUNT
4005 Lot OPTION SMS Functional Support
LH
PWS Para: 1.4.3.1 – 1.4.3.4 (excluding 1.4.3.3), 1.4.3.5.1.a, 1.4.3.5.2.e
Period of Performance: 1 October 17 - 30 September 18
QUANTITY
UNIT UNIT PRICE AMOUNT
4006 Lot OPTION SMS AFRC Sustainment
LH
PWS Para: 1.4.5
Period of Performance: 30 September 17 - 29 September 18
4008 Months OPTION OPTIONAL - Cyber Security
FFP
PWS Para: 1.4.7
Period of Performance: 1 October 17 - 30 September 18
4009 Lot OPTION SMS Travel / ODC
COST
Period of Performance: 1 October 17 - 30 September 18
4010 Lot OPTION SMS AFRC Travel
COST
Period of Performance: 30 September 17 - 29 September 18
4011 Months OPTION CMS Sustainment
FFP
CMS ONLY related tasks in para’s 1.4.1 (excluding 1.4.1.4), 1.4.2 (excluding
1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c), 1.4.3 (excluding 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e), 1.4.4 (excluding 1.4.4.2.b), 1.4.6, 1.4.8, 1.4.9
Period of Performance: 30 September 17 - 29 September 18
UNIT UNIT PRICE AMOUNT
4012 Lot OPTION CMS Sustainment
LH
PWS Para: 1.4.1.4.b, 1.4.2.2.1.a, 1.4.2.2.1.1, 1.4.2.2.1.2.b, 1.4.2.3.2.c, 1.4.3.6, 1.4.3.7, 1.4.3.9, 1.4.3.10.1, 1.4.3.10.3.e, 1.4.4.2.b
Period of Performance: 30 September 17 - 29 September 18
4013 Lot OPTION CMS Travel / ODC
COST
Period of Performance: 30 September 17 - 29 September 18
Section C - Descriptions and Specifications
PERFORMANCE WORK STATEMENT
PERFORMANCE WORK STATEMENT
FOR
SINGLE MOBILITY SYSTEM (SMS)
and
COALITION MOBILITY SYSTEM (CMS)
Prepared by
USTRANSCOM
PROGRAM MANAGEMENT OFFICE
10 July 2013
Table of Contents
1.0 DESCRIPTION OF SERVICES
1.1 Background
1.2 Scope
1.2.1 SMS
1.2.2 CMS/CTL
1.3 Applicable Documents
1.4 Requirements
1.4.1 Task Area 1: Contract Level and Task Order Management
1.4.2 Task Area 2: Software Development, Sustainment, and Testing
1.4.3 Task Area 3: Operations Support and Training
1.4.4 Task Area 4: SMS/CMS/CTL Help Desk Support
1.4.5 Task Area 5: Sustainment of the Air Force Reserve Command (AFRC) SMS module (Optional Task):
(LH CLIN)
1.4.6 Task Area 6: CMS/CTL Hosting Environment
1.4.7 Task Area 7: SMS Migration to a virtual environment supporting
Infrastructure, Platform, and/or Software as a Service.– OPTIONAL TASK
1.4.8 Task Area 8: Security Engineering and Cyber Security Requirements
1.4.9 Task Area 9: Configuration Management
1.5. Deliverables
1.5.1 Delivery Process
1.5.2 Warranty
1.5.3 Inspection
1.5.4 Final Acceptance
2.0 SERVICE DELIVERY SUMMARY
2.1 SMS Service Delivery Summary
2.2 CMS Service Delivery Summary
3.0 GOVERNMENT-FURNISHED PROPERTY AND SERVICES
3.1 Government Furnished Equipment
3.2 SMS/CMS Government Furnished Information
3.3 Military Network Connectivity
4.0 GENERAL INFORMATION
4.1 Place of Performance
4.2 Travel and Other Direct Costs
4.2.1 Travel
4.2.2 ODC Requirements
../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355955997 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355955998 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355955999 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956000 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956001 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956002 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956003 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956004 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956005 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956006 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956007 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956008 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956008 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956009 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956010 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956011 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956012 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956013 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956014 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956015 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956016 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956017 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956018 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956019 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956020 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956021 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956022 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956023 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956024 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956025 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956026 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956027 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956028 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956029 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956030
4.3 Period of Performance
4.4 Contract Manager
4.5 Contractor Employees
4.6 Quality Assurance
4.7 Requirements Affecting Contractor Personnel Performing Mission Essential Services
4.8 Handling of Non-Public Information
4.9 Acquisition Streamlining
4.10 Standards
5.0 SECURITY (PHYSICAL, PERSONNEL, INFORMATION, ANTITERRORISM / FORCE
PROTECTION AND INDUSTRIAL SECURITY)
5.1 General Security Information
5.2 Personnel Security Requirements
5.3 Facilities Clearance Level
5.4 Personnel and Facilities Clearance Validation
5.5 CAC Issuance Procedures
5.6 Scott Air Force Base/USTRANSCOM Physical Access
5.7 Visits to USTRANSCOM Buildings
5.8 Security Training
5.9 Additional Security Conditions
5.10 Derogatory Information
5.11 Accessing NATO Information
5.12 Security Debriefing
5.13 Cyber Security Requirements
6.0 CONTRACTOR TRANSITION
6.1 Exit Requirements
6.2 Ramp Up Time
APPENDIX A: 5-Year Forecast
APPENDIX B: NONDISCLOSURE AGREEMENT & AGREEMENT TO DISCLOSE POTENTIAL
CONFLICTS OF INTEREST
APPENDIX C: DD FORM 254
APPENDIX D: IAWIP CERTIFICATION REQUIREMENTS
APPENDIX E: CONTRACT DATA REQUIREMENTS LIST
APPENDIX F: ACRONYMS
../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956031 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956032 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956033 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956034 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956035 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956036 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956037 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956038 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956039 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956039 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956040 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956041 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956042 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956043 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956044 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956045 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956046 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956047 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956048 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956049 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956050 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956051 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956052 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956053 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956054 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956055 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956056 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956057 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956057 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956058 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956059 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956060 ../../../../../1.%20RFPs,%20Contracts%20&%20Bailments/2.%20HTC711%20Contracts/SMS%20CMS%20Re-compete/Section%20A/A1%20-%20PWS/SMS_CMS_PWS_FY14-18%20-%2023%20May%2013%20(accepted%20changes).docx#_Toc355956061
1.0 DESCRIPTION OF SERVICES
1.1 Background
The United States Transportation Command (USTRANSCOM) provides global air, land, and sea transportation for the Department of Defense (DoD), both in times of peace and war through its Transportation Component Commands
(TCCs): Air Mobility Command (AMC); Surface Deployment and Distribution Command (SDDC); and Military
Sealift Command (MSC). USTRANSCOM provides synchronized transportation, distribution, and sustainment, which makes possible projecting and maintaining national power where needed with the greatest speed and agility, the highest efficiency and most reliable level of trust and accuracy.
The SMS is the primary system used to view requirements, plan missions, and track execution. It provides the user with information from systems such as: the Air Mobility Command (AMC) Global Decision Support System
(GDSS) and Consolidated Air Mobility Planning System (CAMPS); the Air National Guard (ANG) Management
Utility (ANGMU); the Integrated Data Environment (IDE) / Global Transportation Network (GTN) Convergence
(IGC); the Joint Operations Planning and Execution System (JOPES); and numerous other feeder systems.
USTRANSCOM requires Contractor-provided Information Technology (IT) services and related support to sustain
SMS operations.
The SMS provides USTRANSCOM's C2 capability and augments the multi-system environment currently used for assigning mobility missions. Utilizing its automated C2 system interfaces, SMS significantly reduces the amount of offline interface required between C2 agencies and broadens the range of information available to them as decision makers. SMS improves the flow of mobility mission information from the TCCs to USTRANSCOM, aiding in the decision making process.
USTRANSCOM, United States Pacific Command (USPACOM), and the Office of the Secretary of Defense sponsored and funded the development of CMS as a Joint Capability Technology Demonstration (JCTD). CMS resides inside the Coalition Theater Logistics (CTL) portal and provides for rapid coordination of Coalition movement planning and execution by providing the capability to observe data for aircraft, ship, road and rail movements (military and commercial) in support of coalition operations. One of the recurring lessons learned from
Operation Iraqi Freedom and Operation Enduring Freedom (OIF/OEF) is the persistent need for visibility regarding logistics movements for the Coalition war-fighter. The CTL provides permissions, administrative controls and user access to CMS and the Humanitarian Expeditionary Logistics Program (HELP).
SMS and CMS share data via an interface. SMS sends US data to CMS while also picking up coalition data for display to US SMS users. While CMS only exists in the unclassified environment, the data it sends to SMS is automatically pushed to the high side by SMS.
While CMS is designed to download mobility data from foreign national systems via the transfer of XML files, it currently has no active interfaces with any system other than SMS. CMS does play a role in DOD’s Unclassified
Information Sharing strategic plan and interaction with the All Partners Network (APAN) and other multinational and interagency systems is expected. The number of users is increasing as CMS becomes better known in the international and interagency community.
The primary CMS customer base will be Foreign National (FN) personnel assigned to coalitions supported by the
United States. Other customers include U.S. Government and Non-Government Organization (NGO) personnel within and outside the DOD. The Federal Emergency Management Agency (FEMA), the American Red Cross, and state and local police agencies are examples of targeted CMS users.
1.2 Scope
The purpose of this contract is to provide specialized systems engineering and technical services in support of SMS and CMS/CTL. While this effort is one contract, tasks between SMS and CMS/CTL are funded separately, and therefore work shall be allocated separately towards each program. SMS and CMS/CTL are expected to function as currently designed with only functional and technical enhancements being included in this performance work statement (PWS). The Contractor shall plan for all tasks identified in this PWS and gather all pertinent information.
Contractor estimates and timelines shall be determined based on the deliverable due dates specified in Section 1.5.
The Contractor shall coordinate with the Government to ensure that all activities are well synchronized and integrated with other USTRANSCOM and distribution management efforts. All reports, studies, or policies identified in the PWS shall be prepared and submitted for Government approval or acceptance. All functions and activities shall be task driven and work performed shall be in accordance with (IAW) all applicable regulations and guidelines.
1.2.1 SMS
This effort will include sustainment of the current system and development of Emergent Requirements (EmR). SMS has reached Full Operational Capability (FOC). The program is in sustainment with only limited enhancements to its current capability. In addition, support is necessary to build and maintain user accounts, train customers, and build or modify SMS data filters and reports.
1.2.2 CMS/CTL
CMS/CTL currently resides in a DIACAP certified commercial cloud environment. The Contractor shall manage
CMS/CTL in this environment or propose migration to another cloud environment that is DIACAP certified. This effort will also include support necessary to build and maintain user accounts, train customers, and build or modify
CMS/CTL data filters and reports. The Contractor shall not be responsible for the development or maintenance of other applications within the CTL unless specified in this PWS. Work requires integrating current or future applications and maintaining that integration into the CTL shall be required.
1.3 Applicable Documents
The following documents are applicable to this PWS and are current as of the date of production. The Contractor is responsible for all changes and updates to these references:
CJCSI 6510.01F, INFORMATION ASSURANCE (IA) AND COMPUTER NETWORK DEFENSE
(CND), Feb 9, 2011
DODI 8570.01-M, Change-2, Information Assurance Training, Certification and Workforce Management, Jan 24, 2012
DOD MIL-HDBK-881C, Work Breakdown Structures for Defense Materiel Items, July 30, 2005
DODI 3020.37, Continuation of Essential DOD Contractor Services During Crises, January 26, 1996
DODI 8520.2, Public Key Infrastructure and Public Key Enabling, May 24, 2011
DODI 8551.1, Ports, Protocols, and Services Management, August 13, 2004
DODI 8510.01, DOD Information Assurance Certification and Accreditation Process, November 28, 2007
DODI 8582.01, , Security of Unclassified DOD Information on Non-DOD Information Systems, June 6, 2012, National Institute of Standards and Technology (NIST) Special Publication 800-53, Revision 3, Recommended Security Controls for Federal Information Systems and Organizations, May 1, 2010
Security Regulation Guidance:
DOD:
DODD 2000.12, DOD Antiterrorism Program, March 1, 2012
DODD 8500.01E, Information Assurance, April 23, 2007
DODI 2000.16, December 8, 2006 (DOD Antiterrorism Standards)
DODI 5200.08-R, Change-1, DOD Physical Security Program, May 19, 2010
DODM 5200.01,volumes 1-4, DOD Information Security Program, February 24, 2012
DODD 5200.2, , Personnel Security Program, April 9, 1999
DODI 5220.22, National Industrial Security Program, March 18, 2011
DODI 8500.2, Information Assurance Implementation, February 6, 2003
USTRANSCOM:
USTC 31-2 (Security Classification Guide)
USTC 31-11 (USTRANSCOM Security Program)
Scott Air Force Base (SAFB): SAFB Instruction 31-101 (Installation Security Instruction)
Forms: DD 254, DOD, Contract Security Classification Specification
DOD publications, directives, and instructions listed above are available at:
http://www.dtic.mil/whs/directives/corres/pub1.html
CJCS 6510.01F is available at:
http://www.dtic.mil/cjcs_directives/index.htm
NIST 800-53 is available at:
http://csrc.nist.gov/publications/PubsSPs.html
1.4 Requirements
1.4.1 Task Area 1: Contract Level and Task Order Management
This task consists of the functional activities relating to the administration and management of this effort. The Contractor shall provide program management for all Contractor tasks, personnel resources and costs and ensure all deliverables meet schedule and budget constraints under this
PWS. The Contractor shall designate a principal point of contact for technical/engineering issues.
The Contractor shall provide support in the specific areas outlined below:
a. The Contractor shall provide a centralized program management capability at the Contractor site. This function shall encompass administrative, clerical, documentation, and related functions that provide general support for the program.
b. The Contractor shall provide support by preparing documents such as required briefings, point papers and meeting minutes related to status of the performance of this PWS.
c. The Contractor shall provide support in the specific areas outlined below in this PWS. The Contractor shall work with the SMS and CMS/CTL Program Office, process owners/ stakeholders, Federal and DOD Government representatives, and other Contractors to accomplish required tasks.
d. All decisions regarding Government requirements or Government actions will be made by Government personnel and the Contractor’s representative will submit required evaluations and recommendations to the Contracting
Officer’s Representative (COR) and/or Contracting Officer (CO) for further action.
e. The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for US Transportation Command via a secure data collection site. The contractor is required to completely fill-in all required data fields at http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.
1.4.1.1 SMS and CMS/CTL Task Order Management Plan and Software Development Plan
The Contractor shall prepare an integrated (i.e., Government and Contractor) Task Order Management Plan (TOMP) to include a Work Breakdown Structure (WBS) that defines tasks, resources, and dependencies. Guidance and acceptable formats for the WBS is contained in DOD Handbook MIL-HBK-881C, Chapters 2, 3 and Appendix B.
The TOMP shall also describe the technical approach, organizational resources, and management controls employed to meet the cost, performance, and schedule requirements throughout contract execution. The Contractor shall prepare a Software Development Plan (SDP) that contains the technical details of the development requirements of this PWS as well as the configuration management controls essential to proper software development control. The
Contractor shall deliver the TOMP and the SDP 20 business days after contract award. After the initial submission the Contractor shall provide the updated TOMP and SDP 20 business days after start of each contract period.
Deliverables:
http://www.dtic.mil/whs/directives/corres/pub1.html http://www.ecmra.mil/
1.4.1.1.a SMS TOMP w/ WBS/timelines and risk assessment
1.4.1.1.b SMS SDP
1.4.1.1.c CMS TOMP w/ WBS/timelines and risk assessment
1.4.1.1.d CMS SDP
1.4.1.2 SMS and CMS/CTL Monthly Status Report (MSR)
The Contractor shall provide a Monthly Status Report, which will include information on both SMS and CMS. The
MSR shall outline the status of the task order to date. The MSR shall list, by each active task area, the accomplishments of the reporting period. The report shall list issues, problem areas, and items that require
Government action. The MSR shall also contain a report of the costs incurred to date and whether they comply with the contract delivery schedule and burn plan. The MSR format will be agreed upon by the COR and the Contractor and shall contain, but is not limited to, the following information:
• Activities conducted and results
• Deliverables
• Trip report to include name of traveler, trip location and purpose, estimated and actual travel costs, and dates of travel
• Meetings attended with a summary of relevant items discussed
• Proposed activities
• Risk assessment and mitigation recommendations
• Open issues
• Actual and projected cost expenditures
• Labor hours/costs by task and labor category (for LH CLINS only)
• Key personnel changes
• SMS and CMS system availability and outages
• Security summary analysis and assessment results
• Training statistics and evaluations
• Account management statistics
• Help desk metrics to include the number of trouble calls, fixes, open items, analysis, and trends
The Contractor shall deliver the MSR by the 10 th calendar day of the month.
1.4.1.2.a SMS Monthly Status Report
1.4.1.2.b CMS Monthly Status Report
1.4.1.3 SMS and CMS/CTL Integrated Product Team (IPT) Meetings
The Contractor shall participate in IPT meetings at the Government site or via telephone conference as required by the Government (once a week). Meeting topics include updates on work in progress, requirements management, metrics (monthly), Integrated Master Schedule (IMS) (monthly), upcoming calendar events, help desk issues, and other pertinent issues. The Contractor shall deliver IPT minutes within five (5) business days upon completion of the
IPT. At a minimum, the IPT minutes shall reflect a record of discussion activity, decisions made, date, locations, and attendees.
1.4.1.3.a SMS IPT Attendance & Minutes
1.4.1.3.b CMS IPT Attendance & Minutes
1.4.1.4 SMS and CMS/CTL Technical Interchange Meeting Support
The Contractor shall participate in TIMs and project working groups when called; develop agendas and prepare minutes for each meeting. The Contractor shall develop draft Engineering Change Proposals (ECP) for requirements being considered by the Configuration Control Board (CCB). The ECP shall provide a description of the requirement and proposed technical solution, along with the proposed cost and schedule. TIMs shall be scheduled as needed. At the Government’s discretion, the TIM and IPT may be combined. The Contractor shall deliver TIM minutes within five (5) business days upon completion of the TIM.
Deliverable:
1.4.1.4.a SMS TIM Attendance & Minutes (LH CLIN)
1.4.1.4.b CMS TIM Attendance & Minutes (LH CLIN)
1.4.1.5 SMS and CMS/CTL Trip Reports
The Contractor shall submit a trip report to include the following details: purpose, location and length of trip, travelers, and individuals contacted during trip, synopsis of all discussions, future actions identified, decisions made, or issues of concern arising during trip. This trip report should be an appendix to the MSR. If no travel was conducted during the period, the Contractor shall identify that no travel occurred.
1.4.1.6 Requirements Management
The Contractor shall be responsible for facilitation and administration of the SMS and CMS/CTL requirements management process. The Contractor shall comply with paragraphs a through c below.
a. When available, the Contractor shall utilize the Government’s Requirement Management Tool (RMT) to input, track, trace, and manage requirements and supporting documentation. The Government’s RMTs are composed of
IBM’s Rational RequisitePro, ClearQuest, and ClearCase. The Government shall provide the Contractor access to these tools and the Contractor employees shall be familiar with use of these tools. The Government will not provide
IBM Rational RequisitePro, ClearQuest, and ClearCase training to the Contractor. The Government will maintain and utilize these tools to monitor the requirements management process.
b. In the case where the Government’s RMTs are not available at the beginning of the period of performance, the
Contractor shall follow a Contractor-provided internal requirements management process and use tools that can transition to the Government’s RMTs to input, track, trace, and manage requirements and supporting documentation.
Upon the availability of the Government-provided tools, the Contractor shall have thirty (30) business days to transition to the Government-sponsored environment. The end state will have all open and historical baselines and requirements loaded into the RMTs. The Contractor shall load the current baseline and any open requirements within the first 30-business day transition period. The Contractor shall have one hundred and twenty (120) business days to transition all historical baselines and requirements into the RMTs.
c. The Contractor shall manage the activities necessary to receive, verify, analyze, refine, and confirm requirements provided by the SMS and CMS/CTL Program Manager (PM). The Contractor shall also manage the activities necessary to maintain the SMS and CMS/CTL requirements baseline, track requirements status, maintain requirements versions, maintain requirements attributes, control requirement quality and consistency, perform change impact analysis, and provide reports.
The Contractor shall provide a requirements impact assessment to include an analysis of level of effort, impacts to program costs and program schedule. The Contractor shall deliver the impact assessments five days prior to the
Change Working Group (CWG) or as required for emergent requirements.
1.4.1.6.a SMS Requirements Management and Impact Assessments
1.4.1.6.b CMS Requirements Management and Impact Assessments
1.4.1.7 Project Tracking
The Contractor shall develop a project-tracking plan to include percent complete for each SMS and CMS/CTL project/release identified by the USTRANSCOM program manager. The Contractor shall provide estimated cost and estimated hours for each ticket in the associated release. The Contractor shall work with USTRANSCOM program and Functional Managers to identify milestones that may affect a given project plan. The Contractor shall deliver the project tracking plan 15 business days after identification of the project and/or release.
1.4.1.7.a SMS Project-tracking Plan
1.4.1.7.b CMS Project-tracking Plan
1.4.2 Task Area 2: Software Development, Sustainment, and Testing
1.4.2.1 SMS Software Maintenance
The Contractor shall modify the existing SMS software to fix software errors identified and documented by incident reports. The Contractor shall modify the existing SMS software to implement system enhancements prioritized by the Government as identified…
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 .