Get documents about "SE BS IR BMA mendment 0002
Document Sample
DTFAWA-09-R-00055
Amendment No. 0002
B.1. OVERVIEW .......................................................................................................... 1
B.2. CLIN STRUCTURE AND PRICE SCHEDULES ................................................... 1
B.2.1. BASE PERIOD CLIN Structure and Price Schedule ..................................... 1
B.2.2. OPTION YEAR 1 CLIN Structure and Price Schedule .................................. 2
B.2.3. OPTION YEAR 2 CLIN Structure and Price Schedule .................................. 4
B.2.4. OPTION YEAR 3 CLIN Structure and Price Schedule .................................. 5
B.2.5. OPTION YEAR 4 CLIN Structure and Price Schedule .................................. 6
B.2.6. Notes Relating to CLIN Structure and Price Schedules for the Base and
Option Periods ............................................................................................................. 8
B.3. CONTRACT VALUE AND Contract CEILING....................................................... 8
C.1. Introduction ........................................................................................................... 1
C.1.1. Limitation on performing inherently governmental functions.......................... 1
C.1.2. Project Background and Objectives .............................................................. 1
C.1.2.1. Background ............................................................................................................. 1
C.1.2.2. Objectives ............................................................................................................... 2
C.2. Task Description ................................................................................................... 2
C.2.1. Overall Task .................................................................................................. 2
C.2.2. Labor Categories Descriptions ...................................................................... 2
C.3. Scope of Work ...................................................................................................... 2
C.3.1. Administrative and Programmatic Tasks ....................................................... 3
C.3.1.1. Reporting................................................................................................................. 3
C.3.1.2. Document Maintenance .......................................................................................... 3
C.3.2. Meetings ........................................................................................................ 4
C.3.2.1. Action Items and Status Meetings .......................................................................... 4
C.3.2.2. SWIM Management Team (and Team Lead) Meetings ......................................... 4
C.3.2.3. Technical Interchange Meetings ............................................................................. 4
C.3.2.4. Program Management Reviews .............................................................................. 5
C.3.2.5. Program Status Reviews ......................................................................................... 5
C.3.2.6. Meeting Agenda ...................................................................................................... 5
C.3.2.7. Meeting Minutes ..................................................................................................... 5
C.3.2.8. General CDRLs ....................................................................................................... 5
C.3.3. Technical Task Requirement 1 - Systems Engineering Support ................... 5
C.3.3.1. Engineering Processes ............................................................................................ 6
C.3.3.2. Engineering and Analysis ....................................................................................... 6
C.3.3.3. Risk Planning .......................................................................................................... 7
C.3.3.4. Safety ...................................................................................................................... 7
C.3.3.5. Security ................................................................................................................... 7
C.3.3.5.1. Security Policies...................................................................................................... 7
C.3.3.6. Configuration Management .................................................................................... 7
C.3.3.7. Quality Assurance ................................................................................................... 8
C.3.3.8. Systems Engineering Management Plan ................................................................. 8
C.3.3.9. Training Presentations ............................................................................................ 8
C.3.3.10. Technical Advisors ................................................................................................. 8
i
DTFAWA-09-R-00055
Amendment No. 0002
C.3.4. Technical Task Requirement 2 – Requirements/Architecture Documentation
Development ............................................................................................................... 9
C.3.4.1. Systems Requirements Definition and Development ............................................. 9
C.3.4.2. Concept and Requirements ................................................................................... 10
C.3.4.2.1. Core Services ........................................................................................................ 10
C.3.4.2.2. Future SWIM Segments ........................................................................................ 10
C.3.4.3. Architecture Documentation Development. ......................................................... 10
C.3.4.4. Registry/Repository IRD and ICD ........................................................................ 11
C.3.4.5. SWIM XML Gateway Requirements and IRD ..................................................... 11
C.3.4.6. SWIM Policy Server Requirements and IRD ....................................................... 11
C.3.4.7. SWIM Message Oriented Middleware (MOM) Requirements and IRD .............. 11
C.3.4.8. Final Program Requirement Appendix Updates ................................................... 11
C.3.4.9. Service Specification Documentation ................................................................... 12
C.3.4.10. Technical Documentation Review ........................................................................ 12
C.3.4.11. FPR, SvSD, and IRD ............................................................................................ 12
C.3.5. Technical Task Requirement 3 – Governance ............................................ 12
C.3.5.1. Implementation of Governance............................................................................. 13
C.3.5.2. Governance Functional Areas ............................................................................... 14
C.3.5.3. Audit and Document Key Processes ..................................................................... 14
C.3.5.4. Technology Plan ................................................................................................... 14
C.3.6. Technical Task Requirement 4 – Enterprise Information Management ....... 14
C.3.6.1. SWIM Data Architecture Framework ................................................................... 15
C.3.6.1.1. SWIM Taxonomy ................................................................................................. 15
C.3.6.1.2. OV-7 Logical Data Model .................................................................................... 15
C.3.6.1.3. Data Descriptions .................................................................................................. 15
C.3.6.1.4. SV-11 Physical Schema ........................................................................................ 15
C.3.6.1.5. XML Schema(s) .................................................................................................... 15
C.3.6.2. Recommended Procedures .................................................................................... 15
C.3.6.3. SWIM Decision/Information Briefings and Decision Packages .......................... 16
C.3.7. Technical Task Requirement 5 – SWIM Integration Support ....................... 16
C.3.7.1. SWIM Infrastructure Implementation Plan .......................................................... 16
C.3.7.2. Operational Function ............................................................................................ 17
C.3.7.3. Development Function .......................................................................................... 17
C.3.8. Technical Task Requirement 6 – SIPs Oversight ........................................ 18
C.3.8.1. Program Level Agreements (PLAs)...................................................................... 18
C.3.8.2. Earned Value Management System (EVMS) ....................................................... 19
C.3.8.3. Metrics .................................................................................................................. 19
C.3.8.4. Design and Program Reviews ............................................................................... 19
C.3.8.5. Service Level Agreements /Memorandums of Agreement ................................... 19
C.3.8.6. FAA Telecommunications Infrastructure (FTI) Capacity .................................... 19
C.3.8.7. Capability Development ....................................................................................... 20
C.3.8.8. Capability Testing ................................................................................................. 20
C.3.8.9. Capability Deployment ......................................................................................... 20
C.3.8.10. Capability Operations and Maintenance ............................................................... 20
C.3.8.11. SIP Compliance Oversight .................................................................................... 20
C.3.8.12. SWIM Product Development ................................................................................ 20
ii
DTFAWA-09-R-00055
Amendment No. 0002
C.3.8.13. SIP Documents...................................................................................................... 21
C.3.8.14. Post Implementation Review ................................................................................ 21
C.3.8.15. SIP Status Meeting and SIPs Monthly Status Review Meetings .......................... 21
C.3.8.16. Future SWIM Segment Implementation ............................................................... 22
C.3.9. Technical Task Requirement 7 – Program Control...................................... 22
Technical Task Requirement 7 – Program Control .................................................... 22
Risk Management ................................................................................................................. 22
EVMS 23
Performance Metrics ............................................................................................................. 23
Financial Management .......................................................................................................... 24
Investment Analysis for Future Segments ............................................................................ 24
Project Planning .................................................................................................................... 24
C.3.10. Technical Task Requirement 8 – Program Management Support ........... 25
C.3.10.1. SWIM Program Communications......................................................................... 25
C.3.10.2. SWIM Program Plans ........................................................................................... 25
C.3.10.3. Investment Analysis .............................................................................................. 26
C.3.10.4. Conferences and Meetings .................................................................................... 26
C.3.10.5. Program Analysis for SWIM Segment X Acquisitions ........................................ 26
C.4. Travel ................................................................................................................. 26
C.5. Deliverables and Due Dates ............................................................................... 26
C.6. Government Furnished Information (GFI) ........................................................... 26
C.7. Government Furnished PROPTERY (GFP) ....................................................... 27
C.8. Acronym Listing .................................................................................................. 28
D.1. PRESERVATION, PACKING AND PACKAGING .................................................... 1
D.2. MARKING ................................................................................................................ 1
D.3. ELECTRONIC DELIVERY ....................................................................................... 1
E.1. AMS CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE ............. 1
E.2. General .................................................................................................................... 1
E.3. Standards for Acceptance of CDRLs ....................................................................... 1
E.4. medium and method of delivery ............................................................................... 1
F.1. AMS CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE ............. 1
F.2. ACCESS TO GOVERNMENT AND NON-GOVERNMENT FACILITIES ................. 1
F.3. PERFORMANCE OF WORK ON FAA FACILITIES ................................................. 1
F.4. PERIOD OF PERFORMANCE................................................................................. 2
F.5. DELIVERABLES ...................................................................................................... 2
G.1. AMS CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE ............. 1
G.2. FAA CONTACTS FOR CONTRACT ADMINISTRATION ........................................ 1
iii
DTFAWA-09-R-00055
Amendment No. 0002
G.3. CONTRACTOR CONTACTS FOR POST-AWARD ADMINISTRATION ................. 2
G.4. CONTRACTING OFFICER’S AUTHORITY ............................................................. 2
G.5. CORRESPONDENCE PROCEDURES ................................................................... 3
G.6. BILLING INSTRUCTION ......................................................................................... 3
G.7. REIMBURSEMENT OF TRAVEL AND OTHER DIRECT COSTS........................... 3
G.8. INVOICE DELIVERY ............................................................................................... 4
G.9. METHOD OF PAYMENT ......................................................................................... 4
G.10. RELEASE OF GOVERNMENT OBLIGATION....................................................... 5
G.11. RESPONSIBILITY OF PRINCIPAL CONTRACTOR TO MAKE PAYMENTS TO
SUBCONTRACTORS/CONSULTANTS.......................................................................... 6
G.12. ACCOUNTING AND APPROPRIATION DATA ..................................................... 6
H.1. AVAILABILITY OF CONTRACTOR PERSONNEL .................................................. 1
H.2. CONTRACTOR RESPONSIBILITIES...................................................................... 1
H.3. INTERPRETATION OF MODIFICATION ................................................................ 1
H.4. DETERMINATION OF CHANGE ............................................................................. 1
H.5. STANDARD INDUSTRIAL CLASSIFICATION ........................................................ 2
H.6. CONFIDENTIALITY OF DATA AND INFORMATION .............................................. 2
H.7. RELEASE OF INFORMATION ................................................................................ 3
H.8. INCORPORATION OF SECTION K BY REFERENCE ........................................... 3
H.9. TRAVEL AND SUBSISTENCE ................................................................................ 3
H.10. WEATHER-RELATED ABSENCE ......................................................................... 5
H.11. WORK SHIFTS ...................................................................................................... 5
H.12. PERSONAL SERVICES ........................................................................................ 6
H.13. UNCOMPENSATED OVERTIME .......................................................................... 6
H.14. CONTRACTOR PERFORMANCE INFORMATION............................................... 6
H.15. WAIVER PROVISION ............................................................................................ 7
H.16. GOVERNMENT PROPERTY MANAGEMENT ...................................................... 7
H.17. ACCEPTANCE PROCESS FOR DELIVERABLES ............................................. 10
H.18. GOVERNMENT FURNISHED PROPERTY (GFP) .............................................. 10
I.1. CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (DECEMBER
2005) 1
iv
DTFAWA-09-R-00055
Amendment No. 0002
I.2. EXCLUSION FROM FUTURE AGENCY CONTRACTS (3.1.7-1, AUGUST 1997) ... 3
I.3. DISCLOSURE OF CERTAIN EMPLOYEE RELATIONSHIPS (3.1.7-6 OCTOBER
2006) 5
I.4. Indefinite Quantity (3.2.4-20 JULY 1996) .................................................................. 7
I.5. CENTRAL CONTRACTOR REGISTRATION (3.3.1-33 JANUARY 2008) ................ 7
I.6. PAYMENT BY ELECTRONIC FUNDS TRANSFER/CENTRAL CONTRACTOR
REGISTRATION (3.3.1-34 OCTOBER 2005) ................................................................. 9
I.7. Mentor Protégé Program (3.6.1-9 October 2006) .................................................... 11
I.8. SUBSTITUTION OR ADDITION OF PERSONNEL (3.8.2-22 OCTOBER 2006) .... 12
I.9. CONTRACTOR PERSONNEL SUITABILITY REQUIREMENTS (3.14-2 January
2009) 13
I.10. GOVERNMENT-ISSUED KEYS, PERSONAL IDENTITY VERIFICATION (PIV)
CARDS, AND VEHICLE DECALS (3.14-4 JULY 2006) ................................................ 16
I.11. SENSITIVE UNCLASSIFIED INFORMATION (SUI) (3.14-5 JULY 2007) ............. 18
J.1. ATTACHMENT DESCRIPTIONS ............................................................................. 1
J.2. CONTRACT DATA REQUIREMENTS LIST (CDRLS) ............................................. 2
J.3. CONTRACT DATA ITEM DESCRIPTION .............................................................. 11
J.4. PERSONNEL QUALIFICATIONS........................................................................... 17
J.5. COTR DELEGATION ............................................................................................. 28
J.6. TASK ORDER 0001 PERTAINING TO BASE PERIOD ........................................ 38
J.7. APPROVED CONTRACTOR PERSONNEL PER TASK ORDER......................... 40
J.8. TEAM LEADS POINT OF CONTACT LIST ........................................................... 41
K.1. CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (3.1-1
DECEMBER 2005) .......................................................................................................... 1
K.2. TYPE OF BUSINESS ORGANIZATION (3.2.2.3-10 JULY 2004) ............................ 1
K.3. AUTHORIZED NEGOTIATORS (3.2.2.3-15 JULY 2004) ........................................ 1
K.4. PLACE OF PERFORMANCE (3.2.2.3-23 JULY 2004) ............................................ 1
K.5. TAXPAYER IDENTIFICATION (3.2.2.3-70 JULY 2004) .......................................... 2
K.6. CERTIFICATION REGARDING DEBARMENT, SUSPENSION, PROPOSED
DEBARMENT, AND OTHER RESPONSIBILITY MATTERS (3.2.2.7-7 APRIL 1996)..... 3
v
DTFAWA-09-R-00055
Amendment No. 0002
K.7. CERTIFICATION OF REGISTRATION IN CENTRAL CONTRACTOR
REGISTRATION (CCR) (3.3.1-35 APRIL 2006) ............................................................. 4
K.8. PREVIOUS CONTRACTS AND COMPLIANCE REPORTS (3.6.2-6 APRIL 1996) . 4
K.9. AFFIRMATIVE ACTION COMPLIANCE (3.6.2-8 APRIL 1996) ............................... 4
K.10. CLEAN AIR AND WATER CERTIFICATION (3.6.3-1 APRIL 2000) ...................... 4
K.11. CERTIFICATION OF DATA (3.8.2-18 OCTOBER 1996) ....................................... 5
L.1. CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (3.1-1
DECEMBER 2005) .......................................................................................................... 1
L.2. MINIMUM OFFER ACCEPTANCE PERIOD (3.2.2.3-2 JULY 2004) ........................ 1
L.3. REQUIREMENTS FOR COST OR PRICING DATA OR OTHER INFORMATION
ALTERNATE II (3.2.2.3-38/ALT2 JULY 2004) ................................................................ 2
L.4. TYPE OF CONTRACT (3.2.4-1 APRIL 1996) .......................................................... 2
L.5. PROTEST (3.9.1-3 NOVEMBER 2002) ................................................................... 2
L.6. APPROVAL OF CONTRACT (3.13-1 APRIL 1996) ................................................. 3
L.7. MILESTONE SCHEDULE ........................................................................................ 4
L.8. Mailing Address/Delivery Address ............................................................................ 4
L.9. Signed Originals ....................................................................................................... 4
L.10. Proposal Questions, Clarifications and Discrepancies ........................................... 4
L.11. EXPENSES RELATED TO OFFEROR SUBMISSIONS ........................................ 5
L.12. ALTERNATE PROPOSALS ................................................................................... 5
L.13. EXCEPTIONS TO TERMS OR CONDITIONS OF THE SIR .................................. 5
L.14. PROPOSAL PRESENTATION ............................................................................... 6
L.15. PROPOSAL CONTENT ......................................................................................... 7
L.15.1. BINDING AND LABELING........................................................................ 7
L.15.1.1. Original ...................................................................................................... 7
L.15.1.3. Indexing .................................................................................................................. 7
Tab indexing shall be used to identify all proposal sections. Each volume must be
organized such that an extensive search of the proposal is not necessary for its review.
Information not in its appropriate section and not appropriately referenced may be assumed
to have been omitted. .............................................................................................................. 7
L.15.1.4. Page Size, Typing, Spacing, and Numbering ......................................................... 7
L.16. DOWN SELECT PROCESS................................................................................... 7
L.17. VOLUME 1, TECHNCIAL ....................................................................................... 8
L.17.1. FACTOR 1, Technical and business approaches .......................................... 8
vi
DTFAWA-09-R-00055
Amendment No. 0002
L.17.2. VOLUME 1, OFFER AND OTHER DOCUMENTS ........................................ 9
L.18. VOLUME 2, TECHNICAL ....................................................................................... 9
L.18.1. FACTOR 2, SAMPLE TECHNICAL PROBLEM ............................................ 9
L.18.2. FACTOR 3 (EXPERIENCE OF PERSONNEL), FACTOR 4 (MANAGEMENT
APPROACH) AND FACTOR 5 (PAST EXPERIENCE AND PAST PERFORMANCE). 10
L.18.3. Subcontracting Plan .................................................................................... 11
L.19. VOLUME 3, COST .............................................................................................. 12
L.20. Volume 4, task order 0001 proposal..................................................................... 14
L.21. Instructions for Oral Presentation FOR SAMPLE TECHNICAL PROBLEM ......... 15
L.21.1. Background ................................................................................................. 15
L.21.2. Location and Time of Oral Presentations .................................................... 15
L.21.3. Conduct of the Presentations ...................................................................... 15
L.21.4. Oral Presentation Constraints. .................................................................... 15
L.21.5. Form of Presentation. .................................................................................. 15
L.22. Exhibit L-1 Sample Technical Problem................................................................. 16
L.22.1. Problem Statement .................................................................................... 16
L.22.1.1. Introduction .............................................................................................. 16
L.22.1.2. Background.............................................................................................. 16
L.22.2. Using Guidance to Offerors ...................................................................... 17
L.22.2.1. Structure of Response ............................................................................. 17
L.22.2.2. Required Elements of Technical Response ............................................. 17
L.23. Exhibit L-2 Past Performance Questionnaire ....................................................... 19
L.24. Exhibit L-3 Worksheet for Section B ..................................................................... 25
M.1. CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (DECEMBER
2005) 1
M.2. Award Selection ...................................................................................................... 1
M.3. Downselect Decisions ............................................................................................. 1
M.4. Subcontracting Plan ................................................................................................ 2
M.5. Importance of Subcontracting Plan ......................................................................... 2
M.6. Eligibility for Award .................................................................................................. 2
M.7. COMMUNICATIONS AND DISCUSSIONS WITH OFFEROR’S ............................ 2
M.8. Award on Initial Offers ............................................................................................. 2
vii
DTFAWA-09-R-00055
Amendment No. 0002
M.9. EVALUATION PROCESS – Volumes 1, 2, and 3 ................................................... 2
M.10. Volumes: Order of Importance .............................................................................. 3
M.11. Volume 1 Technical Volume – Evaluation Factors ............................................... 4
M.11.1. Factor 1 – Technical and Business Approaches: ............................................ 4
M.9.1.1. Subfactor A (Down Select Subfactor ...................................................................... 4
M.9.1.2. Subfactor B (Down Select Subfactor) ..................................................................... 4
M.9.1.3. Subfactor C (Down Select Subfactor). .................................................................... 5
M.9.1.4. Subfactor D (Down Select Subfactor) ..................................................................... 5
M.9.1.5. Subfactor E (Down Select Subfactor) ..................................................................... 5
M.12. Volume 2 Technical ............................................................................................... 5
M.12.1. Within Volume 2, Factor 2 has no specific weight. An Offeror’s response to
Factors 1 and 2 may be used to corroborate evaluation of the other technical factors
as relevant. With the exception of Factor 2, Factors 3, 4, and 5 are listed in
descending order of importance: ................................................................................. 5
M.12.2. Factor 2. Sample Technical Problem. ............................................................ 5
M.12.3. Factor 3. Experience of Personnel. ................................................................ 6
M.12.4. Factor 4. Management Approach. .................................................................. 6
M.12.5. Factor 5. Past Experience and Past Performance. ........................................ 6
M.12.6. Subcontracting Plan ........................................................................................... 7
M.13. VOLUME 3, COST/PRICE EVALUATION ............................................................. 7
M.14. Volume 4, task order 0001 proposal...................................................................... 8
M.15. Evaluation of Risk .................................................................................................. 8
M.16. rESPONSIBILITY DETERMINATION .................................................................... 9
M.17. Rating of Offers ..................................................................................................... 9
M.17.1. Factors 1, [deleted], 3, AND 4 ............................................................................ 9
M.17.2. Factor 5. Past Experience and Past Performance ........................................... 11
M.18. Final Evaluation/Selection Evaluation ................................................................. 13
viii
DTFAWA-09-R-00055
Amendment No. 0002
PART I - SECTION B
SUPPLIES/SERVICES & PRICE/COST
B.1. OVERVIEW
This is an Indefinite Delivery Indefinite Quantity (ID/IQ) Contract. The Contractor must
provide, as ordered by the Government, the following services with Level Of Effort
(LOE) firm fixed prices for each labor category in a Base Year and four one-year Option
Years. The specific services will be identified via individual Task Orders (TO). FAA has
provided estimated maximum and minimum labor hours for this contract. The
Contractor will be reimbursed for all allowable and allocable costs of Travel and Other
Direct Costs (ODCs).
B.2. CLIN STRUCTURE AND PRICE SCHEDULES
B.2.1. BASE PERIOD CLIN Structure and Price Schedule
BASE PERIOD
(March 1 – September 30, 2010)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
0001AA Program Analyst 568 to 2272 $ $
(Mid-level)
0002AA Systems Engineer 568 to 1704 $ $
(Senior-level)
0002AB Systems Engineer 2556 to 3408 $ $
(Mid-level)
0003AA SOA Architect 568 to 1136 $ $
(Senior-level)
0003AB SOA Architect (Mid- 1136 to 1136 $ $
level)
0003AC SOA Architect (Jr- 1136 to 1136 $ $
level)
0004AA SOA Developer 1704 to 2272 $ $
(Senior-level)
0004AB SOA Developer 1136 to 1136 $ $
(Mid-level)
0005AA Business Analyst 0 to 2272 $ $
(Senior-level)
0005AB Business Analyst 0 to 1136 $ $
(Mid-level)
0005AC Business Analyst 1136 to 1136 $ $
B-1
DTFAWA-09-R-00055
Amendment No. 0002
BASE PERIOD
(March 1 – September 30, 2010)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
(Jr-level)
0005AD Business Analyst 568 to 568 $ $
(Entry-level)
0006AA Enterprise Architect 568 to 2272 $ $
(Mid-level)
SOA Systems 568 to 2272 $ $
0007AA Analyst (Jr-level)
0008 Travel Costs, LOT $48,291.03
including Per Diem
and Local
--
Transportation, and
Administrative
Charge
0009 Other Direct Costs LOT -- $5,000.00
TOTAL AMOUNT for CLINs 0001AA through 0007AA $
Total Amount CLINS 0008 and 0009 (ODCs) $53,291.03
TOTAL Base Period Cost
B.2.2. OPTION YEAR 1 CLIN Structure and Price Schedule
OPTION YEAR 1
(One year from date of Exercising Option)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
1001AA Program Analyst 1840 to 3680 $ $
(Mid-level)
1002AA Systems Engineer 1840 to 3680 $ $
(Senior-level)
1002AB Systems Engineer 7360 to 7360 $ $
(Mid-level)
1003AA SOA Architect 1840 to 3680 $ $
(Senior-level)
1003AB SOA Architect (Mid- 1840 to 1840 $ $
level)
B-2
DTFAWA-09-R-00055
Amendment No. 0002
OPTION YEAR 1
(One year from date of Exercising Option)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
1003AC SOA Architect (Jr- 1840 to 1840 $ $
level)
1004AA SOA Developer 3680 to 3680 $ $
(Senior-level)
1004AB SOA Developer 1840 to 1840 $ $
(Mid-level)
1005AA Business Analyst 5520 to 7360 $ $
(Senior-level)
1005AB Business Analyst 1840 to 5520 $ $
(Mid-level)
1005AC Business Analyst 1840 to 3680 $ $
(Jr-level)
1005AD Business Analyst 1840 to 1840 $ $
(Entry-level)
1006AA Enterprise Architect 920 to 3680 $ $
(Mid-level)
SOA Systems 920 to 3680 $ $
1007AA Analyst (Jr-level)
1008 Travel Costs, LOT $214,986.55
including Per Diem
and Local
--
Transportation, and
Administrative
Charge
1009 Other Direct Costs LOT -- $7,000.00
TOTAL AMOUNT for CLINs 1001AA through 1007AA $
Total Amount CLINS 1008 and 1009 (ODCs) $221,986.55
TOTAL Option 1 Period Cost
B-3
DTFAWA-09-R-00055
Amendment No. 0002
B.2.3. OPTION YEAR 2 CLIN Structure and Price Schedule
OPTION YEAR 2
(One year from date of Exercising Option)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
2001AA Program Analyst 1840 to 1840 $ $
(Mid-level)
2002AA Systems Engineer 1840 to 3680 $ $
(Senior-level)
2002AB Systems Engineer 6440 to 6440 $ $
(Mid-level)
2003AA SOA Architect 1840 to 3680 $ $
(Senior-level)
2003AB SOA Architect (Mid- 1840 to 1840 $ $
level)
2003AC SOA Architect (Jr- 0 to 1840 $ $
level)
2004AA SOA Developer 3680 to 5520 $ $
(Senior-level)
2004AB SOA Developer 1840 to 1840 $ $
(Mid-level)
2005AA Business Analyst 5520 to 7360 $ $
(Senior-level)
2005AB Business Analyst 1840 to 5520 $ $
(Mid-level)
2005AC Business Analyst 1840 to 3680 $ $
(Jr-level)
2005AD Business Analyst 1840 to 1840 $ $
(Entry-level)
2006AA Enterprise Architect 920 to 3680 $ $
(Mid-level)
SOA Systems 920 to 1840 $ $
2007AA Analyst (Jr-level)
2008 Travel Costs, LOT $216,690.33
including Per Diem
and Local
--
Transportation, and
Administrative
Charge
B-4
DTFAWA-09-R-00055
Amendment No. 0002
OPTION YEAR 2
(One year from date of Exercising Option)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
2009 Other Direct Costs LOT -- $ 7,000.00
TOTAL AMOUNT for CLINs 2001AA through 2007AA $
Total Amount CLINS 2008 and 2009 (ODCs) $223,690.33
TOTAL Option 2 Period Cost
B.2.4. OPTION YEAR 3 CLIN Structure and Price Schedule
OPTION YEAR 3
(One year from date of Exercising Option)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
3001AA Program Analyst 1840 to 7360 $ $
(Mid-level)
3002AA Systems Engineer 1840 to 3680 $ $
(Senior-level)
3002AB Systems Engineer 4600 to 4600 $ $
(Mid-level)
3003AA SOA Architect 1840 to 2760 $ $
(Senior-level)
3003AB SOA Architect (Mid- 920 to 1840 $ $
level)
3003AC SOA Architect (Jr- 0 to 1840 $ $
level)
3004AA SOA Developer 1840 to 3680 $ $
(Senior-level)
3004AB 1840 to 1840 $ $
SOA Developer
(Mid-level)
3005AA 5520 to 7360 $ $
Business Analyst
(Senior-level)
OPTION YEAR 3
B-5
DTFAWA-09-R-00055
Amendment No. 0002
(One year from date of Exercising Option)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
3005AB Business Analyst $
1840 to 5520 $
(Mid-level)
3005AC Business Analyst 1840 to 3680 $ $
(Jr-level)
3005AD Business Analyst 920 to 920 $ $
(Entry-level)
3006AA Enterprise Architect 920 to 3680 $ $
(Mid-level)
SOA Systems 920 to 1840 $ $
3007AA Analyst (Jr-level)
3008 Travel Costs, LOT $374,005.73
including Per Diem
and Local
--
Transportation, and
Administrative
Charge
3009 Other Direct Costs LOT -- 7,000.00
TOTAL AMOUNT for CLINs 3001AA through 3007AA $
Total Amount CLINS 3008 and 3009 (ODCs) $381,005.73
TOTAL Option 3 Period Cost
B.2.5. OPTION YEAR 4 CLIN Structure and Price Schedule
OPTION YEAR 4
(One year from date of Exercising Option)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
4001AA Program Analyst 1840 to 8280 $ $
(Mid-level)
4002AA Systems Engineer 1840 to 3680 $ $
(Senior-level)
4002AB Systems Engineer 3680 to 3680 $ $
(Mid-level)
OPTION YEAR 4
B-6
DTFAWA-09-R-00055
Amendment No. 0002
(One year from date of Exercising Option)
CLIN Labor Category Minimum and HOURLY NTE
Maximum RATE TOTAL
Labor Hours AMOUNT
4003AA SOA Architect 1840 to 1840 $ $
(Senior-level)
4003AB SOA Architect (Mid- 0 to 1840 $ $
level)
4003AC SOA Architect (Jr- 0 to 1840 $ $
level)
4004AA SOA Developer 1840 to 1840 $ $
(Senior-level)
4004AB SOA Developer 1840 to 3680 $ $
(Mid-level)
4005AA Business Analyst 5520 to 7360 $ $
(Senior-level)
4005AB Business Analyst 1840 to 5520 $ $
(Mid-level)
4005AC Business Analyst 0 to 3680 $ $
(Jr-level)
4005AD Business Analyst 0 to 0 $ $
(Entry-level)
4006AA Enterprise Architect 920 to 1840 $ $
(Mid-level)
SOA Systems 920 to 1840 $ $
4007AA Analyst (Jr-level)
4008 Travel Costs, LOT $377,818.90
including Per Diem
and Local
--
Transportation, and
Administrative
Charge
4009 Other Direct Costs LOT -- 7,000.00
TOTAL AMOUNT for CLINs 4001AA through 4007AA $
Total Amount CLINS 4008 and 4009 (ODCs) $384,818.90
TOTAL Option 4 Period Cost
B-7
DTFAWA-09-R-00055
Amendment No. 0002
B.2.6. Notes Relating to CLIN Structure and Price Schedules for the Base
and Option Periods
1) All Offerors are instructed to propose the Not-To-Exceed (NTE) amount based on
the maximum labor hours in each labor category.
2) The Travel costs and ODCs are Not-To-Exceed (NTE) costs. The Contractor must
provide all personnel, equipment, facilities and other items incidentals to contract
performance.
3) Under CLINs X001 to X007, each Labor Category Rate is the rate per hour that the
Contractor must charge the FAA for services rendered under the Labor Category,
during the Base Period and any Option Period, respectively. See Section B.2.
4) The Total Estimated Not To Exceed (NTE) Labor Hours are the Program Office’s
estimate of the total volume of work the Contractor will perform under the contract,
as follows:
Base Period Total Estimated NTE Labor 23,856 HOURS
Hours
5) Estimated Labor Hours may be shifted from one Labor Category to another Labor
Category within the same performance period only to accommodate Task needs and
program priorities.
6) The CLINs X008 and X009 reflect the estimates for required travel costs and ODC
for this contract. Travel and Other Direct Costs associated with it will be identified as
required. The FAA will pay reasonable, allowable, and allocable Travel and Other
Direct Costs in accordance with Section H.9. Contractor must not exceed the
estimated cost for Travel or Other Direct Costs.
7) Contractor may add an Administrative Charge to Travel Costs in accordance with
Section H.9 and bill against CLIN X008.
B.3. CONTRACT VALUE AND CONTRACT CEILING
1) The Total Contract Ceiling or Not to Exceed (NTE) Contract Ceiling is the maximum
possible dollar amount of all CLINS, for the Base Period and all Option Periods, as
follows.
Total Contract Ceiling in all Periods
2) The Total Contract Value is the sum of the dollar amount currently obligated to all
CLINS, as follows:
Total Contract Value $(Computed at Award)
B-8
DTFAWA-09-R-00055
Amendment No. 0002
3) Each CLIN has a Ceiling, which is the maximum possible dollar amount for the
CLIN, and a Value, which is the dollar amount currently obligated to the CLIN. The
following table sets forth each CLIN Ceiling, Value and Remaining Ceiling for the
Base Period, as follows:
Base Period (Computed at Award)
CLIN CLIN Ceiling CLIN Value Remaining CLIN
(Funded) Ceiling
0001AA $ $ $
0002AA $ $ $
0002AB $ $ $
0003AA $ $ $
0003AB $ $ $
0003AC $ $ $
0004AA $ $ $
0004AB $ $ $
0005AA $ $ $
0005AB $ $ $
0005AC $ $ $
0005AD $ $ $
0006AA $ $ $
0007AA $ $ $
Totals $ $
FAA AMS clauses 3.3.1-14 Limitation of Funds (April 1996), 3.3.1-12 Limitation of Cost
(April 1996), and 3.3.1-10 Availability of Funds (April 1996) apply to this contract. See
Section I.1.
B-9
DTFAWA-09-R-00055
Amendment No. 0002
PART I - SECTION C
STATEMENT OF WORK (SOW)
SYSTEM WIDE INFORMATION MANAGEMENT SYSTEMS ENGINEERING AND
BUSINESS SUPPORT SERVICES CONTRACT
C.1. INTRODUCTION
This Statement of Work (SOW) provides the Office of ATC Communications (AJW-5)
with the systems engineering (SE), program architecture, requirements, implementation,
and business support services necessary to assist the System Wide Information
Management (SWIM) program. In accordance with Section I.2, the Contractor is
prohibited from competing as a prime or subcontractor for any later contract to acquire
technology or services derived from the requirements developed under this contract.
C.1.1. Limitation on performing inherently governmental functions
Nothing contained in this Contract or this SOW is intended to, nor should it be construed
as, imparting on the Contractor any inherently governmental function. The Contractor is
engaged under this Contract to assist and support the SWIM Program Office (PO) in its
systems engineering, program architecture, requirements, implementation and business
related activities.
C.1.2. Project Background and Objectives
C.1.2.1. Background
SWIM will modernize the National Airspace System (NAS) into a NAS-wide information
system that supports Next Generation Air Transportation System (NextGen) goals. The
transformation to NextGen requires programs and technologies that provide more
efficient operations, including streamlined communications capabilities. SWIM is an
integral part of that transformation.
SWIM was introduced to improve information interoperability and management for
diverse NAS system platforms across multiple operational domains (e.g., Traffic Flow
Management, En Route, Terminal, Surveillance, and Weather). SWIM will provide a
Service Oriented Architecture (SOA) environment for stepwise migration to NextGen.
SWIM obtained a Final Investment Decision in June 2009. The program is currently
developing and refining requirements and architectural designs for the SWIM system.
To advance the program, the SWIM PO requires programmatic and technical support
for engineering activities associated with developing and evaluating operational
concepts; requirements; architectures; strategic planning; value and performance
measurement; and related activities. This support will ensure consistency across
Federal Aviation Administration (FAA) operational domains in the identification,
specification, and development of capabilities that improve NAS interoperability while
furthering SWIM goals (e.g., a managed progression of capabilities toward net-
centricity).
C-1
DTFAWA-09-R-00055
Amendment No. 0002
The SWIM PO is implementing a federated approach for Segment 1. Core services
implementation is delegated to a number of NAS programs. The SWIM PO is in the
process of developing an implementation strategy, acquisition strategy, and an
investment strategy for SWIM Segment 2. The planned Joint Resource Council (JRC)
final investment decision is planned for the summer of 2010. Segment 1 and Segment
2 efforts will be conducted in parallel.
These tasks include direct support to the SWIM PO and other stakeholders, including
Air Traffic Operations-Planning (AJP) Systems Engineering at FAA Washington, D.C.
Headquarters and the William J. Hughes Technical Center (WJHTC) located in Atlantic
City, New Jersey, SWIM Implementing Programs (SIPs), Communities of Interest (COI),
and other FAA Lines of Business.
C.1.2.2. Objectives
This project will be led by the SWIM PO. The objectives of the SWIM PO under this
requirement are to obtain the assistance of a Contractor to provide:
High technical expertise to assist and guide the SWIM PO to execute the program;
High business expertise to assist and guide the SWIM PO to execute the program;
SOA technology and software subject matter expertise to assist and guide the SWIM
PO to execute the program;
Systems engineering information expertise for the SWIM PO that will allow it to
optimize technical decisions and resource utilization as the program is executed;
and
Assistance in creating the formal documentation and processes needed for effective
program management.
C.2. TASK DESCRIPTION
C.2.1. Overall Task
The Contractor must support the SWIM program with the targeted objectives as
identified in Paragraph C.1.2.2 above. The SWIM PO expects its objectives to be met
through the work and deliverables specified in the sections that follow.
C.2.2. Labor Categories Descriptions
The Contractor must support labor categories and functional responsibilities as defined
in Attachment J.4, Personnel Qualifications.
C.3. SCOPE OF WORK
The Contractor must work in collaboration with the following SWIM teams:
Requirements and Governance, Implementation, Program Control, Evolution and
Coordination, and Program Management Support to provide the work described in this
SOW.
C-2
DTFAWA-09-R-00055
Amendment No. 0002
The scope of work is presented in two major task areas to include administrative and
programmatic tasks and technical program tasks. The administrative and programmatic
tasks include document maintenance and support of SWIM meetings.
The work described herein will support all technical tasks associated with all SWIM
segments and requires the Contractor to support the following requirements: Systems
Engineering Support, Requirements/Architecture Documentation Development,
Governance, Enterprise Information Management (EIM), SWIM Integration Support,
SWIM Implementing Programs (SIPs) Oversight, Program Control, and Program
Management.
The Contractor must provide systems engineering (SE) and technical support to the
SWIM PO. The Contractor shall perform specific requirements in accordance with the
SWIM Work Breakdown Structure (WBS) provided to the Contractor as Government
Furnished Information (GFI). The SWIM WBS establishes the SWIM baseline in
support of the Final Investment Decision.
The Contractor must be provided access to the SWIM Knowledge Services Network
(KSN) homepage to facilitate obtaining GFI and the posting of Contract Deliverables
Requirements List (CDRL). The Contractor also has access to the SWIM website at
www.swim.gov.
C.3.1. Administrative and Programmatic Tasks
Administrative and programmatic tasks to be performed by the Contractor include the
following:
C.3.1.1. Reporting
The Contractor will track its performance in accordance with the SWIM WBS and report
it monthly in the Program Status Report (PSR) and must ensure that the requirements
set forth in this SOW are met. Additionally, the Contractor must track earned value
performance metrics by reporting labor hours and submitting a completed WBS
category template for Earned Value Management (EVM) provided as GFI. (CDRL
A001– PSR and CDRL A002 – EVM Reporting).
C.3.1.2. Document Maintenance
The Contractor will be provided access to the SWIM Knowledge Services Network
(KSN) to facilitate document retrieval (including GFI), document reviews and
discussions, and the posting of CDRL. The Contractor also has access to the SWIM
website at www.swim.gov. The Contractor must provide document maintenance, to
include but not limited to, updates reviews, version controls, and posting to the KSN.
The Contractor must review existing documentation, inform the FAA of any
inconsistencies/conflicts, and recommend changes to eliminate inconsistencies/conflicts
among the existing documentation. In some cases, the SWIM Document (preparation)
Template shall be used as a guide, and this template will be issued as GFI.
C-3
DTFAWA-09-R-00055
Amendment No. 0002
C.3.2. Meetings
Meetings shall allow the Contractor the chance to exchange and capture information
and collaborate with stakeholders. The SWIM PO conducts a series of regular internal
meetings and reviews to monitor program performance and discuss the status of action
items, schedule, programmatic, and technical issues. Formal meetings include the
Actions, Issues, and Schedule (AIS) meetings, Management Team meetings, Technical
Interchange Meetings (TIMs), Status meetings, and Program Management Reviews
(PMRs). The SWIM PO may also call ad hoc meetings to discuss specific program
strategies and other issues. SWIM work group also holds meetings to plan and discuss
their work products.
The FAA or designated agent may send electronic mail notification(s), as required, of
planned meeting(s) attendance. The Contractor must support conferences, design
reviews, and other meetings, as identified by the SWIM PO to capture and exchange
technical information. The Contractor shall obtain prior approval before attending. The
Contractor must support SWIM SE and team working meetings. Regular SE and team
working meetings will be excluded from notification and prior approval (unless travel
notification is necessary). The Contractor shall support specific meetings (as directed)
to the SWIM PO and stakeholders in the following tasks:
C.3.2.1. Action Items and Status Meetings
The Contractor must actively attend (unless otherwise specified) weekly meetings to
review actions, issues, schedule status, risk mitigation status, and other items of interest
to the SWIM Teams.
C.3.2.2. SWIM Management Team (and Team Lead) Meetings
The Contractor must actively attend (on an as-needed basis - unless otherwise
specified) weekly meetings at which the team leads discuss accomplishments, issues,
and upcoming activities.
C.3.2.3. Technical Interchange Meetings
The Contractor must actively provide, host, attend, and facilitate (unless otherwise
specified) technical information exchange and Technical Interchange Meetings (TIMs)
to review and discuss systems engineering products, progress, schedules, open action
items, and issues with the SWIM PO, SIPs, WJHTC personnel and other stakeholders,
as directed. The SE TIMs are conducted to be a cross fertilization of all the SE
disciplines (i.e., requirements, architecture, etc.). Information is exchanged and
provided to all participants to enhance product development. The SE TIMs shall be
conducted at a frequency as mutually scheduled at approximately 6-week intervals.
The Contractor must develop and distribute, as required, technical briefings, white
papers, and reports. The Contractor must develop, distribute, and facilitate technical
knowledge exchange. (CDRL A003 – Technical Findings).
C-4
DTFAWA-09-R-00055
Amendment No. 0002
C.3.2.4. Program Management Reviews
The Contractor must be required to report their work status, tasks accomplished and
planned during scheduled PMR held to monitor contractor performance. The
Contractor’s PMR shall be held at least quarterly or as directed by the CO. (CDRL
A004 – Program Briefs)
C.3.2.5. Program Status Reviews
The Contractor must support meetings (as required) at which the PM and the SWIM
Team Leads provide a program status reviews (PSRs), accomplishments, and
upcoming activities to selected audiences interested in SWIM’s program progress.
C.3.2.6. Meeting Agenda
The Contractor must submit a suggested agenda for Government approval four (4)
business days before the date scheduled for designated required meetings such as
TIMs and PMRs (and designated team lead meetings). (CDRL A005 – Agenda)
C.3.2.7. Meeting Minutes
The Contractor must document proceedings from all specified meetings such as TIMs
(and designated team lead meetings such as risk and performance metrics meetings),
PMRs, and PSRs. The Contractor shall develop, distribute, and post all minutes on the
SWIM KSN (or provide as directed). (CDRL A006 – Minutes)
C.3.2.8. General CDRLs
The following CDRLs will be used throughout all requirements:
CDRL A003, Technical Findings
CDRL A004, Program Briefs
CDRL A005, Agenda
CDRL A006, Minutes
CDRL A014, Technical Comments
C.3.3. Technical Task Requirement 1 - Systems Engineering Support
The Contractor must provide standard SE processes and procedures in support of the
SWIM PO. SE efforts shall consider all aspects of the discipline to include, for example,
systems performance modeling and measurement, change impact assessments, life
cycle requirements, quality, safety, security, maintainability, reliability, integrity of
analyses, schedule considerations, requirements analysis, and trade studies, product
assessment, prototyping, test and evaluations. The Contractor must employ their
knowledge of the NAS, their extensive technical background, SOA expertise,
middleware technologies, software programming, and familiarity with software
development standards (e.g., IEEE/EIA 12207) to support SWIM requirements
development and system implementation. The Contractor must develop SWIM
documentation and assess correctness, completeness, and consistency of products.
C-5
DTFAWA-09-R-00055
Amendment No. 0002
Specifically, the Contractor must provide technical expertise to assist the SWIM PO in
the following areas, among others:
Experience and knowledge of one or more of the following FAA domains or
systems: Aeronautical Information Management (AIM), Weather, Traffic Flow
Management (TFM), Surveillance, En Route, and Terminal;
Experience writing technical specifications and other technical documents;
Experience conducting trade studies and knowledge of the FAA System
Engineering Manual (SEM) processes to conduct a trade study;
Knowledge and/or experience with prototyping and the prototyping process;
The Contractor must also provide the following specified tasks:
C.3.3.1. Engineering Processes
The Contractor must design and develop engineering processes to support SWIM
technical activities. The Contractor must assist with the implementation of the SE
engineering processes and procedures outlined in the SWIM Systems Engineering
Management Plan (SEMP) provided as GFI. The Contractor must maintain effective
control over the SE development process including subcontract items and services.
The Contractor must assist in the establishment of engineering processes to monitor,
control, and oversee SWIM engineering activities. The Contractor must support the
implementation, institutionalization, and adoption of engineering processes among
SWIM stakeholders. The Contractor must assess, implement, deploy, and administer
automated tools that facilitate engineering activities (CDRL A003 – Technical Findings).
C.3.3.2. Engineering and Analysis
The Contractor must assist with NAS integration engineering and analysis activities.
The Contractor must provide engineering and analysis activities, to include but not
limited to, service definition and registration; interface definitions and application
integration mechanisms; and, transition issue identification and resolution. The
Contractor must assist with engineering and analysis activities associated with design
and implementation of the core services of the SWIM infrastructure.
The Contractor must develop, manage and support trade studies, and prototype
development plans and procedures for products such as Commercial Off-the-Shelf
(COTS) selections. The Contractor must provide engineering and analysis, to include
but not limited to, the following:
Trade Study and Prototype Support Definitions;
Development of Acquisition Documents;
Acquisition Evaluation Team Participants;
Development of Technical Plans and Reports;
Evaluation of Laboratory Testing;
Execution of Trade Studies;
Execution of Prototype Development;
Provide Software Development and Support;
C-6
DTFAWA-09-R-00055
Amendment No. 0002
Conduct Integration and Interface Testing and Evaluation;
Assist with Setting up Enterprise Licenses; and
Document Process, Progress, Results, and Recommendations.
The Contractor must document findings from the engineering and analysis activities.
The Contractor must develop and distribute, as required, technical briefings, white
papers, and reports. (CDRL A003 – Technical Findings)
C.3.3.3. Risk Planning
The Contactor must review and provide comments on all SWIM risk documentation as it
pertains to requirements and architecture. The Contractor must review and update the
sections of the SWIM SEMP that address risk identification mitigation and/or
management. The Contactor must perform these tasks in accordance with the risk
planning performed in the SOW Section C.3.9 – Program Control. (CDRL A003 –
Technical Findings)
C.3.3.4. Safety
The Contactor must review and provide comments on all SWIM Safety documentation.
Safety documentation will be provided by the SWIM PO on the SWIM KSN to the
Contractor as GFI. The Contractor must review and update the SWIM Safety Plan. The
Contractor must maintain this plan, that outlines a schedule and plan for required safety
reviews, documents and assessments, and an overall schedule for addressing safety
issues, requirements for safety requirements, and interaction with other FAA programs
to resolve/mitigate/manage each safety item or issue. (CDRL A007 – Safety Plan)
C.3.3.5. Security
The Contactor must review and provide comments on all SWIM security documentation.
Security documentation will be provided by the SWIM PO. The Contractor must review
and update the SWIM Security Plan. The Contractor must maintain the SWIM Security
Plan that outlines a schedule and plan for required security reviews, documents and
assessments, and an overall schedule for addressing security issues, requirements for
security, and interaction with other FAA programs to resolve/mitigate/manage each
security item or issue. (CDRL A008 – Security Plan)
C.3.3.5.1. Security Policies
The Contractor must develop application security policies to direct the implementation of
the SWIM Service Oriented Architecture and web services in the NAS (CDRL A009 –
Security Policies)
C.3.3.6. Configuration Management
The SWIM Configuration Review Board (CRB) approves and controls changes to
approved SWIM system baselines and standards in accordance with the SWIM
Configuration Management (CM) Plan maintained on the SWIM KSN Home page. The
CRB also serves as a forum for the disposition of SWIM upgrades/modifications and the
resolution of design, interface, commonality, and schedule issues. The Contractor must
assist in the augmentation of the CM to ensure traceability with SWIM Service
C-7
DTFAWA-09-R-00055
Amendment No. 0002
Specification Documentation/Interface Requirements Documents/Interface Control
Documents (SvSD/IRD/ICD) requirements using the proper change requests (CRs) for
new requirements, enhancement requests, requests for requirements changes, or
defects in accordance with the SWIM Requirements Change Process Standards and
Procedures, CM Plan, and Implementation Plan. CRs may be generated by any SWIM
team member including stakeholders and subject matters experts for new requirements,
enhancement requests, requests for requirements change, or defect in accordance with
the Implementation and CM Plans. The Contractor must assist in the coordination of
activities required before CRs are formally submitted to CM, and initial review for
technical merit and feasibility of proposed requirements changes must be performed
with the CM plan. The Contractor must provide support in defining the procedures in
the SWIM Requirements Change Process Standards and Procedures and the CM Plan.
The Contractor must also review and provide comments of legacy configuration items
that will continue under the CM of the SIPs based on existing plans. (CDRL A010 –
Configuration Management Plan)
C.3.3.7. Quality Assurance
The Contractor must provide support for the maintenance of the Quality Assurance Plan
(QAP). The Contractor must ensure that Quality Assurance (QA) processes and
controls are established and maintained in accordance with the SWIM QAP provided as
GFI. The Contractor shall identify and report QA processes and controls as directed.
The Contractor must identify, document, and report QA issues, problems, and concerns
as required. (CDRL A011 – Quality Assurance Plan)
C.3.3.8. Systems Engineering Management Plan
The Contractor must provide the engineering support for the maintenance of the SWIM
Systems Engineering Management Plan (SEMP) provided on the SWIM KSN to the
Contractor as GFI. The Contractor must review the SWIM SEMP and provide technical
comments generated from their review. (CDRL A012 – Systems Engineering
Management Plan)
C.3.3.9. Training Presentations
The Contractor may conduct training presentations on specific architecture
considerations or software products as required. These presentations will familiarize
team members with the technical content of SWIM. (CDRL A013 – Training
Presentations)
C.3.3.10. Technical Advisors
The Contractor must provide technical expertise to support acquisition associated with
such tasks as COTS procurement (in support of core services development) and
potential SWIM infrastructure acquisitions. The Contractor must leverage knowledge
gained from past COTS acquisition and testing and evaluation to assist with additional
COTS evaluations for future acquisitions. The Contractor must assist with the
preparation of technical and price components of appropriate solicitations and with
responses to FAA solicitations. The Contractor must prepare and assist the
development and update to implementation requirements that may accompany FAA
C-8
DTFAWA-09-R-00055
Amendment No. 0002
solicitations. The Contractor must provide technical advisors to support SWIM
evaluation teams. The Contractor must assist with testing and technical evaluation
activities. The Contractor must capture and report lessons learned at each major task.
The Contractor must assist with the formation of written comments, items for
clarifications, and technical inputs to briefings, reports, and presentations. The
Contractor must handle information provided as source selection sensitive
appropriately. (CDRL A014 – Technical Comments)
C.3.4. Technical Task Requirement 2 – Requirements/Architecture
Documentation Development
The Contractor must provide support to the SWIM PO (in particular the SWIM
Requirements/Architectural Lead) for requirements and architecture documentation
development. The Contractor must provide technical expertise to assist the SWIM PO
in the following areas, among others:
Knowledge of NAS Enterprise Architecture Framework;
Experience with Department of Defense Architecture Framework (DoDAF) and
Unified Modeling Language (UML) experience;
Knowledge of NAS automation architecture and systems integration;
The Contractor must also provide the following specified tasks:
C.3.4.1. Systems Requirements Definition and Development
The Contractor must provide a lead role in development of the SWIM requirements
document, maintenance of existing requirements documents and SIP compliance
oversight. Documentation must include the Final Program Requirements (FPR), FPR
Appendices, SvSD, Component Requirements Documents, Web Service Specification
Documents, Interface Requirements Documents (IRD), and Interface Control
Documents (ICD). The Contractor must work in collaboration with the Requirements
and Governance team, implementation team, SWIM PO, subcontractors, and other
stakeholders to further perform concept exploration and elaboration of SOA services
and information management to refine the definition of SWIM requirements and core
services capabilities including SWIM information exchange requirements. As guidance
material, the Contractor must refer to the SWIM CM Plan, SWIM Requirements
Process, and SWIM Requirements Management Plan (ReqMP) all of which will be
provided as GFI and are located on the SWIM KSN. The Contractor must use the
government provided CM tools (Rational Requisite Pro and Rational Clear Quest) and
processes to identify and capture all requirements changes and assure that
documented requirements changes satisfy quality criteria including completeness,
traceability, verifiability, correctness, consistency, and clarity. The Contractor must
review existing documentation and inform the FAA of any inconsistencies/conflicts, and
recommend changes to eliminate inconsistencies/conflicts among the existing
documentation. The SWIM KSN workspace and Rational Clear Quest CM website shall
be made available to the Contractor for document retrieval, reviews, and discussions.
(CDRL A014 – Technical Comments)
C-9
DTFAWA-09-R-00055
Amendment No. 0002
C.3.4.2. Concept and Requirements
The Contractor must assist with concept and requirements development, validation,
analysis, and documentation, including but not limited to:
C.3.4.2.1. Core Services
The Contractor must provide support for the SWIM PO in the development of SWIM
Core Services/Capabilities concepts and requirements, performance of segment
capability concepts research and development of the following:
Candidate Core Service Use Cases In Accordance With (IAW) Alistair Cockburn’s
book, “Writing Effective Use Cases”; and
Candidate Core Service Concept of Use
(CDRL A014 – Technical Comments)
C.3.4.2.2. Future SWIM Segments
The Contractor must perform functional and system analysis to translate stakeholders’
needs into a traceable set of functional and system requirements. The Contractor must
conduct technical reviews and develop SWIM engineering artifacts for all future SWIM
segments, including but not limited to the following:
SWIM FPR Document;
SWIM FPR Appendices;
SWIM Service Specification Document;
SWIM Interface Control Document;
SWIM Interface Requirement Document; and
Core Services Standards. (CDRL A015 – Core Services Standards)
C.3.4.3. Architecture Documentation Development.
The Contractor must review functional and system requirements and perform physical
architecture, data architecture, and enterprise architecture analysis and develop SWIM
architecture artifacts for all future SWIM segments, to include but not limited to the
following:
Architectural element definition (e.g., conceptual data models, taxonomies, SOA
technologies, and standards), to be delivered as partial content of the following:
- SWIM Architecture Documents
- Core Service Architecture Definitions
- Segment Use Cases development and updates
- Architecture case studies
(CDRL A016 – Architectural Element Definitions);
SWIM NAS Enterprise Architecture Views to be delivered using Rational System
Architect and IAW DoDAF V1.5 include the following:
- TV-1
- OV-1
- OV-2
C-10
DTFAWA-09-R-00055
Amendment No. 0002
- OV-3
- OV-4
- OV-5
- OV-6c
- OV-7
- SV-1
- SV-3
- SV-4a
- SV-4b
- SV-5a
- SV-5c
- SV-6
- SV-7
- SV-10c
- NAS/NextGen Enterprise Architecture impact analysis and studies
- Operational Improvement Roadmap analysis
- Telecommunications Considerations and Requirements Plan
(CDRL A017– Enterprise Architectural Views)
C.3.4.4. Registry/Repository IRD and ICD
The Contractor must update and deliver a revised Registry/Repository IRD. The current
IRD will be provided to the Contractor as GFI. The Contractor must produce and deliver
a Registry/Repository ICD. (CDRL A018 – Registry/Repository IRD and CDRL A019–
Registry/Repository ICD)
C.3.4.5. SWIM XML Gateway Requirements and IRD
The Contractor must update and deliver a revised set of XML gateway requirements.
The current requirements set will be provided to the Contractor as GFI. The Contractor
must produce and deliver an XML Gateway IRD. (CDRL A020- XML Gateway
Requirements and CDRL A021- XML Gateway IRD)
C.3.4.6. SWIM Policy Server Requirements and IRD
The Contractor must update and deliver a revised set of policy server requirements.
The current requirements set will be provided to the Contractor as GFI. The Contractor
must produce and deliver a Policy Server IRD. (CDRL A022 – Policy Server
Requirements and CDRL A023 – Policy Server IRD)
C.3.4.7. SWIM Message Oriented Middleware (MOM) Requirements and
IRD
The Contractor must update and deliver a revised set of Message Oriented Middleware
(MOM) requirements. The current requirements set will be provided to the Contractor
as GFI. The Contractor must produce and deliver a MOM IRD. (CDRL A024 – MOM
Requirements and CDRL A025 – MOM IRD)
C.3.4.8. Final Program Requirement Appendix Updates
C-11
DTFAWA-09-R-00055
Amendment No. 0002
The SWIM Final Program Requirements (FPR) and FPR Appendices are provided on
the SWIM KSN to the Contractor as GFI. The Contractor must provide the engineering
support necessary for the maintenance of the SWIM FPR and FPR Appendices
documents. (CDRL A026 – SWIM FPR Requirements and CDRL A027 – FPR
Appendices)
C.3.4.9. Service Specification Documentation
The Contractor must provide the engineering support for the maintenance of the SWIM
Segment 1 Service Specification Documentation (SvSD) provided on the SWIM KSN
homepage to the Contractor as GFI. The SvSD defines all SWIM service capability
requirements, which are organized by functional capabilities, and decomposes FPR
requirements. The requirements are translated to systems perspective and allocated
requirements from the SWIM Segment 1 SvSD to the SIPs for further elaboration. The
SvSD includes high- level interface requirements. The Contractor must respond to,
capture comments generated after SWIM SvSD reviews, and deliver a product that
maintains the quality criteria presented above. (CDRL A028 – SWIM Service
Specification Document)
C.3.4.10. Technical Documentation Review
To reduce technical risk, the Contractor must conduct a detailed review of all SWIM
system specification documents provided by the SIPs for the nine (9) SWIM
Capabilities. The Contactor shall review all technical documentation provided by the
government, including but not limited, to such documentation as the En Route
Automation Modernization (ERAM) SWIM Release 2 design document and other SIPs
design documentation. (CDRL A014 – Technical Comments)
C.3.4.11. FPR, SvSD, and IRD
To support future SWIM segments (Segment X), the Contractor must, as part of the
system requirements analysis, assist the SWIM Requirements and Governance Team
in the development and execution of the SWIM FPR, SvSD, and IRD in accordance with
the SWIM Requirements Management Plan and Implementation Plan maintained on the
SWIM KSN Home page. The FPR establishes the SWIM Functional Baseline and is the
basis for evaluating the readiness of resultant products and services to become fielded
for use and operation within the FAA. The SvSD decomposes the FPR requirements
and translates them into a service perspective. The IRD defines high-level interface
requirements for SWIM services that are stored in the SWIM registry. The SWIM
SvSD/IRD enables the SWIM program to allocate services to the SIPs. SIPs will
establish and maintain traceability to the SWIM SvSD, and IRD. (CDRL A029 – FPR
(Segment X), CDRL A030 – SvSD (Segment X), CDRL A031 – IRD (Segment X)
C.3.5. Technical Task Requirement 3 – Governance
The Contractor must provide support to the SWIM PO (in particular the SWIM
Governance Lead) as it relates to governance policy, processes, and procedures.
The Contractor must provide technical expertise to assist the SWIM PO in the following
areas, among others:
C-12
DTFAWA-09-R-00055
Amendment No. 0002
Working knowledge of web service (WS) and other information standards and
technologies including WS-Risk Management (RM), WS-Security, WS-
Addressing, and WS-Notification;
Working knowledge of the enterprise management and core services
development such as Interface Management, Messaging, Security, and
Enterprise Service Management (ESM);
Knowledge of information standards and technologies;
Knowledge of WS-Interoperability profiles including WS-I Basic profile, WS-I
Basic Security Profile, and WS-I Reliable Secure Profile;
Working knowledge of SOA security: Extensible Markup Language (XML)
Gateway, Lightweight Directory Access Protocol (LDAP), Security Assertion
Markup Language (SAML), etc.
C.3.5.1. Implementation of Governance
The Contractor must provide technical and management support to review, revise, and
develop plans to define SWIM implementation of governance. The Contractor must
conduct technical assessments and document the results. The Contractor must use the
results of these assessments to recommend SWIM actions and develop implementation
plans based on the approval of recommended action and execution of the plans to
increase the maturity of SWIM governance. The Contractor must analyze existing
policy, develop change recommendations or propose new policy(s), and implement
SWIM policy and guidance including but not limited to:
Description of the SWIM governing bodies or individual roles;
Responsibilities for each governing body or individual role;
Description of the governance lifecycle (i.e., the process by which governance
decisions are made);
Relationships between the SWIM governance process and those for related
governance bodies (e.g., NAS Enterprise Architecture Board, NAS Configuration
Control Board or others);
Roles, responsibilities, and artifact requirements among major stakeholders;
SWIM SOA and Services strategic planning and analysis;
SWIM candidate service selection criteria and value analysis;
SWIM program development and implementation strategy;
SWIM Governance Strategy. This must include consideration of the benefits and
impacts of a federated SWIM approach to address the relationships between the
SWIM and FAA Programs;
The Contractor must develop and coordinate the adoption of Information Technology
(IT) principles. IT principles combined with a commitment to enforce them, helps
drive enterprise-wide change consistently across disparate organizational units and
processes, projects, infrastructure, and the solutions that support them;
The Contractor must assist with the evolution of the COTS product management
plan; and
The Contractor must support the generation refinement and maintenance of the
SWIM Resource Kit for engineering.
C-13
DTFAWA-09-R-00055
Amendment No. 0002
(CDRL A032 – SWIM Governance Policy Document)
C.3.5.2. Governance Functional Areas
The Contractor must perform in the following Governance functional areas:
Maintain/evolve the SWIM Governance Plan provided on the SWIM KSN to the
Contractor as GFI;
Revise and review existing policy, process documentation and procedure
documentation provided on the SWIM KSN to the Contractor as GFI;
Review and revise existing service infrastructure architecture documents provided
on the SWIM KSN to the Contractor as GFI; and
Provide and upon government approval/direction implement recommendations for
remediation of perceived gaps relative to industry conventions and practices.
(CDRL A033 – SWIM Governance Plan)
C.3.5.3. Audit and Document Key Processes
The Contractor must audit and document recommended corrective action to existing
key processes as follows:
Validate a services compliance with governance policy, process, and procedure
requirements;
Validate compliance with and make recommendations for changes to Service
Design Standards;
Validate compliance with and make recommendations for changes to SWIM SOA
Security Policies;
Validate compliance with and make recommendations for change of the SWIM
publishing/discovering standards; and
Make recommendations for the implementation of the run-time enforcement
framework.
(CDRL A003 – Technical Findings)
C.3.5.4. Technology Plan
The Contractor must perform the following services:
Develop and implement a SOA Enabling Technology Plan;
Validate the implementation of SOA Enabling Technology solutions for Web
services;
Revise the core SOA reference architecture model;
Maintain a network drawing depicting the topology of the SOA solution;
Validate remediation of IT Architecture gaps;
Maintain Enterprise Architecture (EA) IT Architecture Documentation; and
Validate strict adherence to and execution of architecture strategy: servers, legacy
systems, web services, utility tools, etc.
(CDRL A034 – Technology Plan)
C.3.6. Technical Task Requirement 4 – Enterprise Information Management
The Contractor must work in collaboration with the SWIM PO (in particular the SWIM
Requirements/Architectural Lead, subcontractors, and other stakeholders to perform
concept exploration and development of Enterprise Information Management (EIM)
C-14
DTFAWA-09-R-00055
Amendment No. 0002
plans, that refine the definition of the SWIM data architecture. A SWIM Data
Architecture Framework was developed as means for collecting information about the
data architecture and support coordination of FAA Programs. Specifically, the
Contractor must provide technical expertise to assist the SWIM PO in the following
areas, among others:
Experience with Data Representation Technology: Extensible Markup Language
(XML) and XML schema design;
C.3.6.1. SWIM Data Architecture Framework
The Contractor must review the government furnished SWIM Data Architecture
Framework. The Contractor must develop and deliver a plan that incorporates the
following elements into an EIM Plan:
C.3.6.1.1. SWIM Taxonomy
The Contractor must review the current SWIM taxonomy and provide suggestions for
improvement. (CDRL A014 – Technical Comments)
C.3.6.1.2. OV-7 Logical Data Model
The Contractor must review the current OV-7 (Logical Data Model) and provide
suggestions for improvement. (CDRL A014 – Technical Comments)
C.3.6.1.3. Data Descriptions
The Contractor must review current descriptions of data items and provide suggestions
for improvement. (CDRL A014 – Technical Comments)
C.3.6.1.4. SV-11 Physical Schema
The Contractor must review government furnished Sequence diagrams and provide
suggestions for improvement. (CDRL A014 – Technical Comments)
C.3.6.1.5. XML Schema(s)
The Contractor must review XML Schema(s) and provide suggestions for improvement.
(CDRL A014 – Technical Comments)
C.3.6.2. Recommended Procedures
The Contractor must provide a recommended sequence of tasks and recommended
personnel (SWIM and FAA program systems engineers and software developers) to
achieve the resolution and acceptance of the recommended products and solutions
envisioned in a Contractor developed and government approved EIM Plan to include
the improvements recommended under paragraph C.3.6.1.1 – C.3.6.1.5. (CDRL A035
– EIM Plan)
C-15
DTFAWA-09-R-00055
Amendment No. 0002
C.3.6.3. SWIM Decision/Information Briefings and Decision Packages
The Contractor must support, as requested by the SWIM PO, the development of
Decision/Information Briefings and Decision Packages. These include but are not
limited to:
Briefs to the FAA Data Governance Board (FDGB) and Service Registry Work
Group (SRWG) to keep them aware of SWIM activities and take full advantage of
the work of the FDGB and SRWG;
Decision packages for existing FAA decision bodies/boards; and
Briefs to the appropriate FAA decision maker for each proposed policy, standard or
governance process/procedure.
(CDRL A036 – Decision Briefings and Packages)
C.3.7. Technical Task Requirement 5 – SWIM Integration Support
The Contractor must work in collaboration with the SWIM PO, subcontractors, and other
stakeholders to perform:
Develop a SWIM Infrastructure Implementation Plan (SIIP) which must capture a
conceptual blueprint for the design of the SWIM Infrastructure, SWIM/FAA business,
organizational and technical objectives;
Maintain and monitor the SWIM infrastructure, which is similar to network or system
management, except that it deals with application-level logic and middleware instead
of lower-level network or server management technical levels; and
Assist developers in each application project team design and build their
connections (adapters) into the SWIM infrastructure, which is similar to data
administration, and includes assembling and maintaining documentation (interface
metadata) for the application interactions.
The Contractor must provide technical expertise to assist the SWIM PO in the following
areas, among others:
Experience with software programming language C++ and JAVA;
Experience with enterprise OS: UNIX, Linux, and AIX;
Demonstrated experience with middleware technologies and systems such as
Java Messaging Service (JMS), Active Message Queuing (MQ), and IBM MQ;
Experience with enterprise application platforms: .NET and Java 2 Platform
Enterprise Edition (J2EE);
Working knowledge of SOA products (i.e., IBM Websphere, Oracle Application
Server, Weblogic and Fusion Middleware, and Fuse (Enterprise Service Bus,
Services Framework, Message Broker, and Mediation Router),
Registry/Repository, Enterprise Service Management (ESM), Policy Server);
Knowledge of SOA platforms and standards: Universal Description Discover
Integration (UDDI) and electronic business (ebXML);
C.3.7.1. SWIM Infrastructure Implementation Plan
C-16
DTFAWA-09-R-00055
Amendment No. 0002
The Contractor must work in collaboration with the SWIM PO (in particular the SWIM
Requirements/Architectural Lead), subcontractors, and other stakeholders to develop a
SWIM Infrastructure Implementation Plan (SIIP) that must include:
The SWIM infrastructure information architecture, specifying communication models
(store-and-forward, publish-and-subscribe or request/reply), schema for
standardized messages, volume and frequency of message exchanges, logical
data/message flows, transformation rules, and logical schemas for files, messages,
and documents. The information architecture should also consider and describe a
proposed system management approach for the SWIM architecture;
A set of governance rules meant to define formally the relationships between the
SWIM integration support team, FAA client application groups and operational
groups. Rules must be established to negotiate service-level agreements (SLAs) for
SWIM integration infrastructure operations (e.g., expected throughput); and
The qualified list of SWIM infrastructure standards, integration middleware and
administration, security, and monitoring tool vendors. (CDRL A037 – SIIP)
C.3.7.2. Operational Function
The Contractor must work in collaboration with the SWIM PO, subcontractors, and other
stakeholders to negotiate SLAs with FAA business units to align response times,
integrity, availability, and message volume expectations.
The SWIM infrastructure will include some combination of communication middleware
(e.g., message-oriented middleware), development tools (e.g., for Simple Object Access
Protocol (SOAP), and Web Service Description Language (WSDL), platform middleware
(e.g., application servers), integration brokers, file transfer utilities, directories and
business process management software.
The Contractor must work in collaboration with the SWIM PO, subcontractors, and other
stakeholders to address operational action items associated with these technologies
including but not limit to:
Installing, configuring and testing middleware;
Modifying and tailoring middleware, occasionally writing some utilities from scratch
rather than buying a tool;
Administering and monitoring the infrastructure (in conjunction with FAA technical
operations personnel, network managers and system administrators);
Tuning and troubleshooting to determine if there are problems in the applications,
network, or integration infrastructure; and
Working with end-user departments to maintain service levels.
(CDRL A014 – Technical Comments)
C.3.7.3. Development Function
The Contractor must work in collaboration with the SWIM PO, subcontractors, and other
stakeholders to assist the teams that develop and maintain FAA/NAS application
systems. This technical support must include, but limited to, the following tasks:
C-17
DTFAWA-09-R-00055
Amendment No. 0002
Specify standard tools for building adapters that connect the applications to the
SWIM infrastructure — for example, adapter development (tool) kits Adapter
Development (tool) Kits (ADKs);
Provide mentors at critical stages of design, coding or acquisition as application
teams build and maintain SWIM infrastructure adapters;
Maintain integration metadata — that is, documentation on the adapters, network
business objects, transformation and routing rules — and business processes.
Integration metadata must include but is not limited to document descriptions, XML
message schema, call signatures (including input and output parameter
descriptions), file formats, screen layouts, and other network business object
definitions;
Maintain the interface repository for Web services (e.g., a WSDL directory using
Universal Description, Discovery and Integration);
Maintain enterprise standards for integration artifacts (e.g., canonical message
definitions and consistent Web services interface definitions); and
Educate FAA managers and project teams regarding integration architecture, best
practices, and tools.
(CDRL A003 – Technical Findings)
C.3.8. Technical Task Requirement 6 – SIPs Oversight
The Contractor must provide support to the SWIM PO (in particular the SWIM
Implementation Lead) as it relates to SIPs oversight as applicable. The SWIM Program
Control Change Request (PCCR) approves and controls changes to approved SWIM
system baseline, the Implementation Team Plan, and standards in accordance with the
CM Plan maintained on the SWIM Home page. It also serves as a forum for the
disposition of SWIM upgrades/modifications and the resolution of design, interface,
commonality, and schedule issues. The SWIM Requirements and Governance Team
approves and controls changes to developmental baselines and work products. This
team will perform system requirements analysis to translate stakeholders’ needs into a
sequenced and traceable functional architecture. The SWIM Implementation Team will
be responsible for reviewing and commenting on all SWIM requirements
documentation, SIP requirements traceability documents, and proposed CRs using the
prescribed SE tools. The Contractor will serve as an Implementation Point of Contact
(POC). A POC is assigned to each SIP. The Contractor must use the Implementation
Team Plan, which will be provided as GFI, in performance of the SIPs oversight
requirement.
C.3.8.1. Program Level Agreements (PLAs)
The Contractor must assist with the SWIM PO in development and updates of the
Program Level Agreements (PLAs) that will be negotiated with each SIP as directed.
The PLAs identify the tasks and activities that the SIPs need to perform in order to
satisfy SWIM PO requirements. The PLAs include JRC approved funding levels,
proposed schedules, required products, and a list of SWIM Government-Furnished
Equipment (GFE). The SWIM Implementation Team will use EVM reporting and TIMs
to track the SIPs progress against the PLAs. One set of PLAs will be prepared for FY11
to FY13, and another set will be prepared for FY14 and FY15. The Contractor must
C-18
DTFAWA-09-R-00055
Amendment No. 0002
designate as the POC in accordance with the Implementation Team Plan. (CDRL A038
– PLAs)
C.3.8.2. Earned Value Management System (EVMS)
The Contractor must support the SIPs in their monthly Earned Value Management
System (EVMS) reporting to the SWIM Implementation Team in accordance with the
SWIM Implementation Plan and as directed.
C.3.8.3. Metrics
The Contractor must assist the SWIM Implementation Team in requesting metric data
from the SIPs and ensuring that this data is reported accurately and in a timely manner.
Also, the Contractor must assist the SIPs in extracting the required metrics from existing
reports or data collection systems.
C.3.8.4. Design and Program Reviews
Throughout the design and development process, the SIPs will conduct Design Reviews
and Program Reviews. The Contractor’s SWIM Implementation Team POC must attend
these reviews in order to monitor the status of the SIPs’ progress, identify any issues
that may impact the SIPs’ ability to facilitate the SWIM capability, and provide technical
assistance. The POC will arrange for, prepare, and conduct SWIM-related
presentations at these reviews upon request. In those instances where issues are
identified, the POC will notify the SWIM Implementation Team Lead as soon as
possible. (CDRL A013 – Technical Presentations)
C.3.8.5. Service Level Agreements /Memorandums of Agreement
During the design and development of SWIM, the Contractor must provide assistance
with the preparation, coordination, and execution of formal agreements that may be
necessary between the SIPs and both FAA NAS consumers and non-FAA consumers
and between SIPs and other SIPs in accordance with the Implementation Plan and as
directed. These optional formal agreements will be documented in writing. Examples,
such as Service Level Agreements (SLAs) for NAS consumer, other transaction
agreements, or required Memorandums of Agreement (MOAs) for non-FAA consumers.
They document the understanding between the SIPs and the consumers as to the level
of the services, priorities of the consumer, responsibilities of both parties, and
guarantees, and will address areas such levels of availability, serviceability,
performance operation, or other attributes. (CDRL A039 – SLAs/MOAs)
C.3.8.6. FAA Telecommunications Infrastructure (FTI) Capacity
In determining the FAA Telecommunications Infrastructure (FTI) service level and the
associated cost to implement the SIPs’ initiative(s), the Contractor must work closely
with the Implementation Team and the SIPs to identify FTI capacity in accordance with
the Implementation Plan and as directed. The following characteristics are identified as
necessary to determine the FTI bandwidth:
Message size;
Average message transmission frequency;
Maximum message transmission frequency;
C-19
DTFAWA-09-R-00055
Amendment No. 0002
Latency requirement;
SWIM, XML, SOAP, and other protocol overheads;
Reliability (high/normal);
Availability; and
Originating program key sites location identifier and the FTI service availability need
date.
(CDRL A040 – FTI Capacity Documentation)
C.3.8.7. Capability Development
Throughout the development process, the Contractor must provide support to the SWIM
PO to review documentation, present at or attend meetings, research technical issues
or options, and coordinate with other stakeholders and SWIM PO entities as directed.
C.3.8.8. Capability Testing
The Contractor must assist the SIPs with the Test Management Plans (TMP) and test
procedures or similar test documentation that includes a description of the plan for
testing the capability as well as a matrix that maps which requirements will be tested in
each phase of testing. The Contractor must provide testing and evaluation (T&E)
support to the SWIM program tests that may be conducted at the WJHTC and SIPs’
Contractor facilities. (CDRL A003, Technical Findings and CDRL A014, Technical
Comments)
C.3.8.9. Capability Deployment
The Contractor must assist the SIPs with the Capability Deployment Plans or similar
document and Transition Plans that contain a description and schedule of the
necessary site surveys, NAS Change Proposals Process (NCPs), and deployment to
sites. (CDRL A003, Technical Findings and CDRL A014, Technical Comments)
C.3.8.10. Capability Operations and Maintenance
The Contractor must assist the SIPs with developing plans for operating and
maintaining the new SWIM capability within the NAS. This plan should include a
description of any required training; identification of staffing resources necessary for
operating and maintaining the system; and, a plan for performing first and second level
engineering maintenance. (CDRL A003, Technical Findings and CDRL A014,
Technical Comments)
C.3.8.11. SIP Compliance Oversight
The Contractor must provide the tasks associated with SWIM requirements document
maintenance, updates, reviews, version controls, posting KSN, and SIPs compliance
oversight.
C.3.8.12. SWIM Product Development
The Contractor must review and provide Technical comments, recommendations, and
enhancements to SWIM documents developed by the SIPs to include Integrated
Terminal Weather System (ITWS), Corridor Integrated Weather System (CIWS), En
Route Automation Modernization (ERAM), Traffic Flow Management (TFM),
C-20
DTFAWA-09-R-00055
Amendment No. 0002
Aeronautical Information Management (AIM), Weather Message Switching Center
Replacement (WMSCR), Terminal Data Distribution System (TDDS), and other
stakeholders (e.g., FTI program requirements). The Contractor must also participate in
designated reviews and meetings. (CDRL A014 – Technical Comments)
C.3.8.13. SIP Documents
The Contractor must assist the SIPs with the creation, development, and revisions of
the all directed SIPs documents. The Contractor must provide review, technical
comments and input to the following:
SIP Capability Management Plan;
SIPs Capability Network Logic Schedule (monthly);
SIPs Status Review Briefing/Report (monthly);
SIPs Cost Performance Report (monthly);
White Papers (as necessary);
SIPs COTS Management Plan;
SIPs Reliability, Maintainability, and Availability (RMA) Plan and Status Reports (if
available and provided);
SIPs Capability Requirements Document, derived from SWIM SvSD;
SIPs Architecture Document;
SIPs Capability High-Level Design Document;
SIPs Capability Prototyping Report and Briefing, if applicable;
SIPs Capability Detailed Design Document;
SIPs Capability IRD/IRD;
SIPs Capability Test Management Plan;
SIPs Capability Test Procedures and Test Reports;
As-built WSDL with all supporting schemas and Role-Based Access Control
(RBAC);
Final FTI Requirements; and
SIPs Capability Deployment Plan.
(CDRL A003 – Technical Findings and CDRL A014 – Technical Comments)
C.3.8.14. Post Implementation Review
The Contractor must support the SIPs to ensure that they plan for and conduct Post
Implementation Reviews (PIRs) for their SWIM services. PIRs assess actual program
results against baseline expectations to determine whether the investment program is
achieving performance and benefit targets; the investment program is meeting the
service needs of customers; and the original business case is still valid. The Contractor
must support the SIPs to ensure that the PIRs assess actual investment costs,
schedules, benefits, performance, and mission outcomes against appropriate measures
of effectiveness. (CDRL A003, Technical Findings and CDRL A014, Technical
Comments)
C.3.8.15. SIP Status Meeting and SIPs Monthly Status Review Meetings
The Contractor must actively provide, host, attend, support, and facilitate (unless
otherwise specified) the SWIM Implementation Team monthly status review (MSR)
C-21
DTFAWA-09-R-00055
Amendment No. 0002
meetings with the participating SIPs. These meetings are the forum for review of SIPs
technical progress, measured against cost and schedule. The SWIM team also
discusses technical risks and outstanding action items with the SIPs at the MSRs.
These meetings are attended by SWIM Program Control personnel, the SWIM Program
Manager, the SWIM Implementation Lead and with other team members being invited
as the meeting topics warrant. (CDRL A005 – Agenda and CDRL A006 – Minutes)
C.3.8.16. Future SWIM Segment Implementation
The Contractor must support future SWIM segments with implementation tasks as
defined by the Implementation lead to include but not limited to the following:
participating in design reviews, conducting testing, evaluation , analyses, performing
site inspections and surveys, assisting , monitoring the integration of software and
hardware products in the NAS, etc. (CDRL A003, Technical Findings and CDRL A014,
Technical Comments)
C.3.9. Technical Task Requirement 7 – Program Control
Technical Task Requirement 7 – Program Control
The Contractor must provide support to the SWIM PO (in particular the Program Control
Lead). The SWIM Program Control Team provides support to the SWIM PO for risk
management, earned value management, performance metrics, financial management,
and investment analysis. Tasks will be conducted for all SWIM segments.
Risk Management
The SWIM Risk Management (RM) process is governed by the SWIM Risk
Management Plan. Risk documentation will be provided by the SWIM PO on the SWIM
KSN to the Contractor as GFI. The Contractor must provide support to the SWIM PO
for the RM process covering SWIM segments that is an organized and systematic
process to reduce risks and improve the likelihood of program success. The Contractor
must provide support for the following RM tasks:
Assist in risk planning, evaluation and mitigation in accordance with SWIM Risk
Management Plan (RMP);
Support, prepare, review, update, and coordinate risk plans and risk reports at
monthly Risk Management Working Group (RMWG) meetings;
Post risk reports (including risk by rank report) on KSN monthly;
Status soon to come due risk mitigation plans at weekly action item meetings;
Maintain risk database;
Support documentation and preparation of guidance for the implementation of SWIM
Best Practices for risk, and respond to Best Practices action items;
Document risk meeting results in minutes and post them to KSN;
Track monthly risk metrics to be included in RMWG minutes;
Periodically update SWIM RMP and post to KSN; and
Periodically update the Risk section of the SEMP.
(CDRL A041 – Risk Documentation)
C-22
DTFAWA-09-R-00055
Amendment No. 0002
EVMS
The Contractor must support the SWIM PO in maintaining the SWIM EVMS in order to
plan and control costs, measure performance, and identify variances in costs and
schedule for all SWIM segments. The Contractor must support the SWIM
PO developing, analyzing, evaluating, and updating earned value management EVM
reports for controlling costs and schedule measures in the approved OMB Exhibit 300
program baseline.
In addition, the Contractor must perform the following EVM tasks:
Develop, update, maintain, distribute, and post to KSN the following Required
Program Artifacts:
Program WBS and Data Dictionary; and.
Responsibility Assignment Matrix (RAM)
CPR format 1 and 5 by control account;
Provide training EVMS process as required;
Provide monthly baseline tracking, control, and analysis, and provide monthly EVMS
reports to AJA, Control Account Managers (CAMs), and Program Manager and post
results to KSN;
Coordinate with CAMs to identity understand and resolve variance;
Support Program Management Reviews and Integrated Baseline Reviews (IBRs);
Provide inputs to OMB Exhibit 300;
Provide inputs to Resource Planning Data (RPD); and
Maintain change control log and post to KSN.
(CDRL A042 – EVM Documentation)
Performance Metrics
The Contractor must support the SWIM PO for all SWIM Segments in developing,
tracking, updating, modeling, and reporting on performance metrics in order to support
the investment decision to determine measurement achievements against the
established metric baseline in accordance with the SWIM Measurement and Analysis
(M&A) Plan, OMB Exhibit 300 guidance, and as otherwise directed. The Contractor
must perform the following tasks:
Identify/ tailor performance measurements in OMB Exhibit 300;
Maintain status of performance metrics and post to KSN;
Periodically update SWIM M&A Plan and post to KSN;
Support documentation and preparation of guidance for the implementation of SWIM
Best Practices for measurement and analysis, and respond to Best Practices action
items;
Support, preparation, review, update and coordination of performance metrics at
Quarterly MMWG meetings;
Document metrics meeting results in minutes and post to KSN.
(CDRL A043 – Performance Metric Documentation)
C-23
DTFAWA-09-R-00055
Amendment No. 0002
Financial Management
The Contractor must assist the SWIM PO in the following Financial Management tasks:
Assist in the financial planning, budget formulation, presentation and execution;
Provide financial baseline management support;
Prepare Procurement Requests for FAA funds;
Monitor financial status for obligations, commitments, and expenditures and report to
the program control lead; and
Compile, analyze and prepare financial, contractual and procurement reports using
data from FAA systems (i.e., Delphi, PRISM, FMS).
Envelop, distribute, and post to the KSN, updates to the current spend plan provided
as GFI, commitments and obligations report.
(CDRL A044 – Financial Documentation)
Investment Analysis for Future Segments
The Contractor must support the SWIM PO in the following tasks:
Provide investment planning and analysis support to include development,
documentation, presentation and delivery of high quality, substantiated cost
estimates that identify the cost and schedule base of estimate (BOE), methodologies
employed by WBS element, and time-phase in both base year and then year (i.e.,
inflated) dollars;
Support the analysis of various technical and acquisition alternatives. Evaluate
solutions by compiling and analyzing life cycle cost, cost-benefits, risk, technical
performance, schedule, human factors, safety assessment, environmental impact,
spectrum support and operational suitability;
Facilitate the affordability assessment;
Support the development of the OMB Exhibit-300, Business Case Analysis Report
(BCAR), and Cost and Benefit Bases of Estimates in accordance with the program
schedule;
Maintain current interim documents on KSN;
Support the development of program spend plans and Resource Planning
Documents (RPD);
Provide Joint Resource Council (JRC) process guidance and coordination;
Perform economic analysis and develop economic measures such as net present
value, benefit to cost ratio, and payback period; and
Perform budget analyses to relate planned budgets and potential changes to the
budgets to attainment of project milestones.
(CDRL A045 – Investment Analysis Documentation)
Project Planning
The Contractor must support the SWIM PO in the following tasks:
Maintain an updated integrated program schedule for Segment 1. Collaborate with
project team members to capture milestone, event, and activity changes to provide
C-24
DTFAWA-09-R-00055
Amendment No. 0002
program schedule information. Updated schedule should be posted to the KSN
within one day of the change;
Maintain an updated integrated program schedule for Segment 2. Collaborate with
project team members to capture milestone, event, and activity changes to provide
program schedule information. Updated schedule should be posted to the KSN
within one day of the change;
Provide reports on the progress of the implementation of SWIM programs providing
mid and end of month schedule status to SWIM CAMs for all SWIM segments;
Coordinate with CAMs on proposed schedule changes;
Maintain supplemental information to include activity dictionary, cost loading,
resource loading and percent complete activities;
Provide and review critical path schedule networks, Program Evaluation and Review
Technique (PERT) and Gantt charts;
Provide input to program briefings and information papers;
Maintain change control log and post to KSN.
Provide schedule reports as requested by the PM or CAM;
(CDRL A046 – Project Planning Documentation)
C.3.10. Technical Task Requirement 8 – Program Management Support
The Contractor must provide support to the SWIM PO and in particular the Program
Manager for support activities and functions, such as program communications,
program plans, investment analysis, conference and meeting, and acquisition support.
C.3.10.1. SWIM Program Communications
The Contractor must provide and manage the content for program communications with
governmental bodies, stakeholders, media, and other entities as directed including:
U.S.A. Congress;
OMB;
Government Accounting Office;
Joint Planning and Development Office (JPDO);
Department of Transportation’s Office of the Inspector General (OIG);
AJW management;
Air Traffic Operations (ATO) service units;
Industry;
SWIM program website (www.swim.gov);
KSN website; and
SWIM program newsletter.
(CDRL A047 – Program Communications)
C.3.10.2. SWIM Program Plans
The Contractor must update and maintain the SWIM program plans to include the
Communications Plan, Website Plan and Outreach Plan. (CDRL A048 –
C-25
DTFAWA-09-R-00055
Amendment No. 0002
Communications Plan, CDRL A049 – SWIM Website Plan and CDRL A50– SWIM
Outreach Plan)
C.3.10.3. Investment Analysis
The Contractor must review and provide inputs to OMB-300, RPD documents,
executive-level briefings for the JRC and Executive Committee. (CDRL A045 –
Investment Analysis Documentation)
C.3.10.4. Conferences and Meetings
When requested, the Contractor must accompany and participate with FAA SWIM PO
personnel at related conferences and meetings.
C.3.10.5. Program Analysis for SWIM Segment X Acquisitions
The Contractor must support and conduct detail analysis to support SWIM Segment X
acquisitions. (CDRL A003 – Technical Findings and CDRL A014 – Technical
Comments).
C.4. TRAVEL
Travel may include trips to various vendor locations (such as Boston, Massachusetts),
training facilities, WJTHC located in Atlantic City, New Jersey, NAS facilities and
conference locations as appropriate. The Contractor must obtain prior approval for
travel from the CO. Travel will be reimbursed on a cost basis, if allowable and
allocable, in accordance with Acquisition Management System (AMS) policies and
guidelines.
C.5. DELIVERABLES AND DUE DATES
The Deliverables and Due Dates under this contract are set forth in Section J.2.
C.6. GOVERNMENT FURNISHED INFORMATION (GFI)
The FAA KSN website workspace must be made available to the Contractor for
document retrieval, reviews, and discussions. Additionally, the Contractor is
encouraged to obtain information from the SWIM website at www.swim.gov. The
Contractor must be granted access to the SWIM Wiki as required and approved. The
FAA will purchase the required software licenses for COTS software, if required, for use
by FAA and Contractor personnel. The Contractor may view the GFI on the SWIM
website at www.swim.gov to assist in the preparation and development of their tasks.
As guidance material and to establish program baseline, the Contractor must have and
refer to the SWIM GFI which will be located on the SWIM KSN site or the SWIM website
(unless otherwise noted below), and includes, but is not limited to, the following:
SWIM Decision Memorandum – What is SWIM?
C-26
DTFAWA-09-R-00055
Amendment No. 0002
SWIM Fact Sheets – Segments Capabilities
SWIM Work Breakdown Structure (WBS)
SWIM Final Program Requirements
SWIM Program Schedule
SWIM Document Template
SWIM WBS Category Template for EVM
SWIM Requirements Management Plan
SWIM Systems Engineering Management Plan
SWIM Implementation Plan
SWIM Laboratories Plan
SWIM Configuration Management Plan
SWIM Risk Management Plan
SWIM Risk Reports
SWIM Measurement and Analysis Plan
SWIM WBS and Data Dictionary
SWIM Responsibility Assignment Matrix
SWIM OMB Exhibit 300
SWIM Resource Planning Data (RPD)
SWIM Change Log Report
SWIM Business Case Analysis Report
SWIM Network Logic Schedule
NAS Enterprise Architecture Documentation (as it becomes available)
System Engineering Management Plan (SEMP)
SWIM Requirements Process
SWIM Governance Documents
Other GFI as identified will be made available as it is required and/or upon request.
C.7. GOVERNMENT FURNISHED PROPTERY (GFP)
The FAA will provide Government Furnished Property (GFP) to the Contractor for FTI
Remote Access Capabilities (FRAC) accounts for each approved Contractor personnel
for access to the FAA Local Area Network (LAN) account, as required for performance
of their duties.
C-27
DTFAWA-09-R-00055
Amendment No. 0002
C.8. ACRONYM LISTING
Acronym Definition
ADKs Adapter Development (tool) Kits
AIM Aeronautical Information Management
AMS Acquisition Management System
AIS Action Issues, and Schedule
ARO After Receipt of Order
ATC Air Traffic Control
ATO Air Traffic Operations
BCAR Business Case Analysis Report
BCR Baseline Change Request
BOE Basis of Estimates
CAMs Control Account Managers
CDRL Contract Deliverable Requirements List
CIWS Corridor Integrated Weather Service
CM Configuration Management
CM Plan Configuration Management (CM) Plan
COTR Contracting Officer’s Technical Representative
CO Contracting Officer
COIs Communities of Interest
COTS Commercial Off-the-Shelf
CPR Cost Performance Report
CR Change Request
DAF Data Architecture Framework
DOD Department of Defense
DoDAF Department of Defense Architecture Framework
EA Enterprise Architecture
EbXML Electronic Business Extensible Markup Language
EIM Enterprise Information Management
ERAM En Route Automation Modernization
ESM Enterprise Service Management
EVM Earned Value Management
EVMS Earned Value Management Systems
FAA Federal Aviation Administration
FEA Federal Enterprise Architecture
FID Final Investment Decision
FIPS Federal Information Processing Standard
FISMA Federal Information Security Management Act
FPR Final Program Requirements
FDGB FAA Data Governance Board
FTI FAA Telecommunications Infrastructure
GFE Government Furnished Equipment
C-28
DTFAWA-09-R-00055
Amendment No. 0002
GFI Government Furnished Information
GCNSS Global Communications Navigation and Surveillance Systems
IAW In Accordance With
IBRs Integrated Baseline Reviews
ICAO International Civil Aviation Organization
ICD Interface Control Document
IRD Interface Requirements Documents
IT Information Technology
ITWS Integrated Terminal Weather Service
JRC Joint Resource Council
JMS Java Messaging Service
KSN Knowledge Services Network
M&A Measurement and Analysis Plan
MMWG Metrics Management Working Group
MOA Memorandum of Agreement
MQ Message Queuing
MSR Monthly Status Review
NAS National Airspace System
NextGen Next Generation Air Transportation System
NCP NAS Change Proposal Process
NLS Network Logic Schedule
OCI Organizational Conflict of Interest
OMB Office of Management and Budget
PERT Program Evaluation and Review Technique
PIR Post Implementation Review
PLA Program Level Agreement
PM Program Manager
PMR Program Management Review
PO SWIM Program Office
POC Point of Contract
PSR Program Status Review
QA Quality Assurance
QAP Quality Assurance Plan
RAM Responsibility Assignment Matrix
RBAC Role-Base Access Control
ReqMP Requirements Management Plan
RM Risk Management
RMA Reliability, Maintainability, Availability
RMP Risk Management Plan
RMWG Risk Management Working Group
ROC Resolution of Comments
RPD Resource Planning Data
RUP Rational Unified Process
SE System Engineering
SEM Systems Engineering Manual
C-29
DTFAWA-09-R-00055
Amendment No. 0002
SEMP System Engineering Management Plan
SIIP SWIM Infrastructure Implementation Plan
SIPs SWIM Implementing Programs
SLA Service Level Agreement
SOA Service Oriented Architecture
SOAP Simple Object Access Protocol
SOW Statement of Work
SRWG Systems Requirements Working Group
SV System Version
SvSD Service Specification Documentation
SWIM System Wide Information Management
TBD To be determined
TDDS Terminal Data Distribution System
TFM Traffic Flow Management
TIM Technical Interchange Meetings
TMP Test Management Plan
UDDI Universal Description, Discover, and Integration
UML Unified Modeling Language
WBS Work Breakdown Structure
WJHTC William J. Hughes Technical Center
WMSCR Weather Message Switching Center Replacement
WS Web Service
WSDL Web Services Description Language
XML Extensible Markup Language
C-30
DTFAWA-09-R-00055
Amendment No. 0002
PART I - SECTION D
PACKAGING AND MARKING
D.1. PRESERVATION, PACKING AND PACKAGING
The Contractor shall ensure all deliverables (e.g., reports, materials, hardware, and
software, etc.) applicable to this contract are prepared for shipment in accordance with
the contractor’s best commercial practice to protect delivery to the Government from
damage, contamination, and deterioration during shipping and handling.
D.2. MARKING
a.) The Contractor shall mark each package, report, or other deliverable with the
following:
(1) Name and address of the Contractor;
(2) FAA Contract number under which the item is being delivered;
(3) Deliverable item number;
(4) Notice of partial or final delivery; and
(5) Name and routing symbol of person to whom deliverable is being sent.
b.) Each package, report, or other deliverable shall be accompanied by a transmittal
letter, with a copy to the Contracting Officer and Contracting Officer Technical
Representative.
D.3. ELECTRONIC DELIVERY
All deliverables shall be released in electronic format, unless the Contractor is directed
to do otherwise in writing by the Contracting Officer. Acceptable delivery methods
include electronic mail.
However, the contractor shall not send by unencrypted electronic mail any information
that:
a.) Is classified (at the “For Government Use Only” level or higher);
b.) The Contracting Officer’s Technical Representative (COTR) or Contracting Officer
(CO) has informed the contractor is inappropriate for transfer by unencrypted e-mail;
or,
c.) Is “Sensitive Security Information.”
D-1
DTFAWA-09-R-00055
Amendment No. 0002
PART I - SECTION E
INSPECTION AND ACCEPTANCE
E.1. AMS CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE
This screening information request (SIR) or contract, as applicable, incorporates by
reference the provisions or clauses listed below with the same force and effect as if they
were given in full text. Upon request, the Contracting Officer will make the full text
available, or Offerors and contractors may obtain the full text via Internet at:
http://www.asu.faa.gov/conwrite/ (on this web page, select "Search and View Clauses").
Inspection of Services - Both Fixed-Price & Cost Reimbursement (April
3.10.4-4 1996)
E.2. GENERAL
The Contractor must deliver all CDRLs developed in support of specific requirements to
the respective Program Leads, the CO, and the COTRs for review of acceptance. The
Program Leads will inspect the CDRLs and provide feedback to the Contractor. The
CO and COTRs will track and monitor CDRL deliverables for acceptance. Final
acceptance of CDRL deliverables performed will be made by the in writing. Any
rejection will be made by the CO in writing.
E.3. STANDARDS FOR ACCEPTANCE OF CDRLS
The Contractor must ensure that all CDRL deliverables accomplish general quality
measures as set forth below under this contract and any resulting Task Orders:
Accuracy – All CDRLs must be accurate in presentation, technical content, and
adherence to CO and COTR accepted elements of style.
Clarity – All CDRLs must be clear and concise; engineering terms must be used as
appropriate. All diagrams must be easy to understand and relevant to the
supporting narrative.
Requirements Validation – All CDRLs must satisfy the requirement of the
Government as specified herein, and as specified in individual TOs.
File Editing – All CDRLs with text or diagrammatic files or both must be editable by
the Government.
Timeliness – All CDRLs must be submitted in accordance with J.2.
E.4. MEDIUM AND METHOD OF DELIVERY
The Contractor must post their deliverables to the appropriate SWIM KSN website
space. Upon the posting of their deliverables, the Contractor must submit an email
notification to the respective Program Leads, CO, and COTRs within 1 business day
from posting.
E-1
DTFAWA-09-R-00055
Amendment No. 0002
PART I - SECTION F
DELIVERIES OR PERFORMANCE
F.1. AMS CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE
This screening information request (SIR) or contract, as applicable, incorporates by
reference the provisions or clauses listed below with the same force and effect as if they
were given in full text. Upon request, the Contracting Officer will make the full text
available, or Offerors and contractors may obtain the full text via Internet at:
http://www.asu.faa.gov/conwrite/ (on this web page, select "Search and View Clauses").
3.10.1-9 Stop-Work Order (October 1996)
3.10.1-11 Government Delay of Work (April 1996)
3.10.1-24 Notice of Delay (November 1997)
F.2. ACCESS TO GOVERNMENT AND NON-GOVERNMENT FACILITIES
Part of the effort to be performed under this contract may be at facilities operated by the
FAA. The Contractor will be granted ingress and egress at the specific site where the
effort is to be accomplished. Access to the site shall be coordinated with the COTR.
While Contractor personnel are at FAA facilities, they are required to comply with all
rules and regulations of the site, particularly in the areas of health and safety. The
facilities to which the Contractor has access at all times will be in the custody of the
Federal Government and will not be considered “Government Property” furnished to the
Contractor.
The scheduling of access to FAA facilities shall be under the control of the FAA facility
and availability will be scheduled to permit timely performance of contract requirements.
However, Contractor personnel shall be prepared to work outside normal day shift if
conditions at the facility so require.
The Contractor must require that all Contractor personnel who perform work at FAA
facilities wear identification badges that clearly identify individuals as Contractor
employees.
F.3. PERFORMANCE OF WORK ON FAA FACILITIES
Any of the work under this contract, which is performed by the Contractor, or any of its
subcontractors on premises under FAA control is subject to all provisions of this
contract governing such work and the following:
a.) All Contractor personnel shall, at all times conspicuously display a distinctive badge
provided by DOT/FAA or the Contractor, identifying such personnel as employees of
the Contractor, and shall observe such security regulations as are in effect for the
particular premises involved.
b.) The Contractor agrees that this is a non-personal services contract; that, for all the
purposes of the contract, the Contractor is not, nor shall it hold itself out be, an agent
or partner of, or joint venture with the FAA; and that it shall neither supervise nor
accept supervision from FAA employees.
F-1
DTFAWA-09-R-00055
Amendment No. 0002
c.) The Contractor Contacts identified in Section G shall be available via telephone
Monday through Friday, from 8:00 am until 4:00 pm Eastern Time (Standard or
Daylight Savings as applicable) to receive directions and inquiries regarding the work
in progress and task orders.
d.) Performance of work on FAA premises shall be confined to the area(s) specified by
the Contracting Officer.
e.) When work is performed at Government provided facilities, parking is not provided.
f.) When work is performed at Government provided facilities, basic work facilities such
as workspace and its associated operating supplies (i.e., phones, desks, utilities,
consumable and general-purpose office supplies) will be provided.
F.4. PERIOD OF PERFORMANCE
The periods of performance for this contract are stated as follows:
BASE YEAR: March 1, 2010 to September 30, 2010.
OPTION YEAR 1: October 1, 2010 to September 30, 2011.
OPTION YEAR 2: October 1, 2011 to September 30, 2012
OPTION YEAR 3: October 1, 2012 to September 30, 2013.
OPTION YEAR 4: October 1, 2013 to September 30, 2014
F.5. DELIVERABLES
The Contractor must prepare and submit all deliverable items specified in Section J.
Attachment J.2 and by the task orders issued by the FAA pursuant to this Contract, in
accordance with Part I, Section D.3, to the CO and COTR at the places specified in Part
I, Section G. All deliverables shall be signed and certified by the Contractor.
The transmittal of any deliverable by the Contractor shall include reference to the CDRL
number and set forth the title of the deliverable, if any.
With respect to the delivery date of any deliverables required by this contract, any
reference to “days” shall mean calendar days, unless otherwise specified in writing by
the CO.
When responding to requests for information from the Government, the Contractor shall
provide the information in the Government-specified format and within the timeframe
specified in the Government’s request for the information.
F-2
DTFAWA-09-R-00055
Amendment No. 0002
PART I - SECTION G
CONTRACT ADMINISTRATION DATA
G.1. AMS CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE
This screening information request (SIR) or contract, as applicable, incorporates by
reference the provisions or clauses listed below with the same force and effect as if they
were given in full text. Upon request, the Contracting Officer will make the full text
available, or Offerors and contractors may obtain the full text via Internet at:
http://www.asu.faa.gov/conwrite/ (on this web page, select "Search and View Clauses").
3.10.1-22 Contracting Officer’s Technical Representative (January 2008)
G.2. FAA CONTACTS FOR CONTRACT ADMINISTRATION
For matters pertaining to this contract, the Contractor shall use the applicable FAA Point
of Contact, as follows:
a.) The Contracting Officer (CO) is:
Ms. Dixie Harper, AJA-47
Federal Aviation Administration
800 Independence Avenue, SW
Room 508
Washington, DC 20591
Telephone: (202) 493-5942
Fax: (202) 493-5057
Email: dixie.harper@faa.gov
b.) The Contracting Officer (CO) for administration of this contract is Dennis L. Scanlon.
All references to the CO for contract administration in this contract are to be referred
Dennis L. Scanlon:
Mr. Dennis L. Scanlon, AJA-472
Federal Aviation Administration
800 Independence Avenue, SW
Room 506
Washington, DC 20024
Telephone: (202) 267-9422
Fax: (202) 493-5057
Email: dennis.scanlon@faa.gov
c.) The Contracting Officer’s Technical Representative (COTR) is:
Ms. Rhonda Thomas
Federal Aviation Administration
Office of ATC Communications Technical Operations
Services
800 Independence Avenue, S.W.
Room 508
G-1
DTFAWA-09-R-00055
Amendment No. 0002
Washington, DC 20591
Telephone: 202-493-4671
Email: rhonda.thomas@faa.gov
d.) The Alternate Contracting Officer’s Technical Representative (COTR) is:
Mr. Jim Robb
Federal Aviation Administration
Office of ATC Communications Technical Operations
Services
800 Independence Avenue, S.W.
Room 508
Washington, DC 20591
Telephone: 202-267-8357
Email: jim.robb@faa.gov
G.3. CONTRACTOR CONTACTS FOR POST-AWARD ADMINISTRATION
a.) Contractor’s Contract Manager: The name, address, telephone and fax numbers,
and e-mail address of the Contractor’s Contract Manager are as follows:
Name:
Address:
Telephone:
Fax:
E-mail:
b.) Program Manager: The name, address, telephone and fax numbers, and e-mail
address of the Contractor’s Program Manager are as follows:
Name:
Address:
Telephone:
Fax:
E-mail:
G.4. CONTRACTING OFFICER’S AUTHORITY
The Contracting Officer assigned to this contract has responsibility for ensuring the
performance of all necessary actions for effective contracting; ensuring compliance with
the terms of the contract and safeguarding the interests of the United States in its
contractual relationships. In this regard, the Contracting Officer is the only individual
who has the authority to enter into, administer, or terminate this contract. In addition,
the Contracting Officer is the only person authorized to approve changes to any of the
requirements under this contract, and notwithstanding any provision contained
elsewhere in this contract, the said authority remains solely with the Contracting Officer.
G-2
DTFAWA-09-R-00055
Amendment No. 0002
The Contractor shall immediately notify the Contracting Officer for clarification when a
question arises regarding the authority of any person to act for the Contracting Officer
under the contract in select areas, or when the Contractor receives direction that
appears outside contract scope.
G.5. CORRESPONDENCE PROCEDURES
To promote timely and effective administration, correspondence shall be addressed to
the CS with an information copy of the correspondence to the COTR.
G.6. BILLING INSTRUCTION
a.) The Contractor shall submit invoices once monthly. The Contractor shall submit all
invoices for payment under this contract with the following information:
(1) The Contract Number
(2) The Invoice Number and Date prepared
(3) The Contractor’s name, mailing address, and telephone number
(4) Identify the billing period covered by month, day and year
(5) Dollar amount for the current billing period and cumulative identified by Task
Order, name of billable employee, labor category, billable hours, CLIN, and
labor rate
(6) Details of the work performed sufficient to allow the CO and COTR to
determine the dates, personnel, type of tasks and level of effort expended on
each task for which the Contractor is submitting its invoice. The CO may
request additional detail about an invoice before approving payment.
(7) Detail for all travel, by person, with vouchers and receipts included as backup
(8) Certification and signature of an appropriate management official as follows:
“I certify that this invoice is correct and in accordance with
the terms of the contract. I further certify that the costs
included herein have been incurred, represent payments
made by the Contractor, and properly reflect the work
performed.”
Signature of Official
Date of Signature
Signer's name typed or printed
Signer's Title
(9) Name and telephone number of the Contractor’s contact for resolution of
questions.
(10) Invoices cannot exceed the total fixed amount of the referenced task order.
If so, the invoice amount will be lowered.
b.) Prior to travel or material costs being incurred, the Contractor must receive approval
from the CO.
G.7. REIMBURSEMENT OF TRAVEL AND OTHER DIRECT COSTS
For performance of this Contract, the contractor may be reimbursed for direct and
indirect travel and other direct costs incurred that are determined by the Contracting
G-3
DTFAWA-09-R-00055
Amendment No. 0002
Officer to be allowable in accordance with the Clause entitled “Allowable Cost and
Payment” (3.2.4-5) and the following provisions:
a.) Limitation. Reimbursement of costs shall not exceed the amounts of funding set
forth in Section B and are subject to the Clause entitled “Limitation of Cost” (3.3.1-12)
b.) Requirement for Prior Approvals. The following shall require prior written approval of
the Contracting Officer:
(1) Proposed subcontracts, in accordance with the Clause entitled “Subcontracts
(Fixed Price Contracts - 3.10.2-1 April 1996)
(2) Employment of subcontractors and consultants, or either, for work under the
contract.
(3) Approval for contractor travel, except for local travel that does not require
airfare and overnight stay, or either. The contractor shall submit requests for
travel sufficiently in advance of the travel dates to allow for program office
review and Contracting Officer approval and, for international travel,
sufficiently in advance of the planned travel dates to allow processing of all
required notifications to the U.S. State Department.
c.) Travel and Per Diem. Travel and Per Diem will be reimbursed in accordance with
Section H.13, “Travel and Subsistence.”
G.8. INVOICE DELIVERY
The contractor shall deliver its invoices to the following individuals with copies as
indicated:
a.) AFM-220 - Accounting original and one copy with backup:
FAA AC ACCTG Office
DOT/FAA AMZ-110
6500 S. MacArthur Blvd.
Oklahoma City, OK 73169
b.) Contract Specialist: one copy with back-up.
c.) Contracting Officer’s Technical Representative: one copy with back-up:
The CO will authorize payments in amounts determined to be allowable in accordance
with the FAA "Contract Cost Principles" at AMS 3.3.2-1.
G.9. METHOD OF PAYMENT
a.) Payments under this contract will be made either by check or by wire transfer
through the Treasury Financial Communications System at the option of the FAA.
b.) The Contractor shall forward the following information in writing to the Federal
Aviation Administration, Accounting Office, DOT/FAA AMZ-110, PO Box 25710,
Oklahoma City, OK 73125, not later than seven days after receipt of notice of award:
(1) full name (where practicable), title, phone number, and complete mailing
address of responsible official(s):
(2) to whom check payments are to be sent, and
(3) who may be contacted concerning the bank account information requested
below;
(4) the following bank account information is required to accomplish wire
transfers:
G-4
DTFAWA-09-R-00055
Amendment No. 0002
i) name, address, and telegraphic abbreviation of the receiving financial
institution;
ii) receiving financial institution's 9-digit American Bankers Association (ABA)
identifying number for routing transfer of funds (provide the number only if
the receiving financial institution has access to the Federal Reserve
Communications System);
iii) recipient's name and account number at the receiving financial institution
to be credited with the funds;
iv) if the receiving financial institution does not have access to the Federal
Reserve Communications System, provide the name of the
correspondent financial institution through which the receiving financial
institution receives electronic funds transfer messages. If a
correspondent financial institution is specified, also provide:
(a) address and telegraphic abbreviation of the correspondent financial
institution;
(b) the correspondent financial institution's 9-digit ABA identifying
number for routing transfer of funds.
Any changes to the information furnished under paragraph (b) of this clause shall be
furnished in writing to the Federal Aviation Administration, Accounts Payable Branch,
AFM-220, 800 Independence Avenue, SW, Washington, DC 20591 at least thirty (30)
days before the effective date of the change. It is the Contractor's responsibility to
furnish the changes promptly to avoid payment to erroneous addresses or bank
accounts.
The document furnishing the information required in paragraphs (b) and (c) must be
dated and contain the signature, title, and telephone number of the Contractor official
authorized to provide it as well as the Contractor's name and contract number.
G.10. RELEASE OF GOVERNMENT OBLIGATION
The Contractor, and each assignee under an assignment entered into under this
contract and in effect at the time of final payment under this contract, shall execute and
deliver, at the time as a condition precedent to final payment under this contract, a
release discharging the Government, its officers, agents, and employees of and from all
liabilities, obligations, and claims arising out of or under this contract, subject only to the
following exceptions:
a.) Specified claims in stated amounts, or in estimated amounts if the amounts are not
susceptible of exact statement, by the contractor.
b.) Claims, together with reasonable incidental expenses, based upon the liabilities of
the contractor to third parties arising out of performing this contract, that are not
known to the contractor on the date of the execution of the release, and of which the
contractor gives notice in writing to the Contracting Officer not more than one (1) year
after the date of the release or the date of any notice to the contractor that the FAA is
prepared to make final payment, whichever is earlier.
G-5
DTFAWA-09-R-00055
Amendment No. 0002
G.11. RESPONSIBILITY OF PRINCIPAL CONTRACTOR TO MAKE PAYMENTS TO
SUBCONTRACTORS/CONSULTANTS
The principal Contractor shall be responsible for making flow down payments due to
subcontractors or consultants in a timely manner consistent with Government payment
to the principal Contractor. The principal Contractor should not infer that payments
made to subcontractors or consultants are predicated on payments made by the
Government to the principal Contractor.
G.12. ORDERING (3.2.4-16 OCTOBER 1996)
a.) Any supplies and services to be furnished under this contract shall be ordered by
issuance of delivery orders or task orders by the individuals or activities designated in
the Schedule.
b.) All delivery orders or task orders are subject to the terms and conditions of this
contract. In the event of conflict between a delivery order or task order and this contract,
the contract shall control.
c.) If mailed, a delivery order or task order is considered "issued" when the Government
deposits the order in the mail. Orders may be issued orally, by facsimile, or by electronic
commerce methods only if authorized in the Schedule.
G.12. ACCOUNTING AND APPROPRIATION DATA
(Supplied at award)
H- 6
DTFAWA-09-R-00055
Amendment No. 0002
PART I - SECTION H
SPECIAL CONTRACT REQUIREMENTS
H.1. AVAILABILITY OF CONTRACTOR PERSONNEL
The Contractor personnel who are assigned to perform work under the labor categories
of this contract must be available for frequent face to face meetings with FAA personnel.
In order to facilitate efficient use of working time, Contractor personnel assigned to work
under this contract must be based in the Washington, DC commuting region and be
able to appear for meetings at FAA Headquarters, or nearby, upon two (2) hours notice.
H.2. CONTRACTOR RESPONSIBILITIES
The Contractor shall proceed promptly with the performance of technical directions duly
issued by the COTR.
If, in the opinion of the Contractor, any instruction or direction by the COTR falls outside
the scope of work set forth in Section C, the Contractor shall not proceed but shall notify
the CO in writing within five (5) working days after receipt of any such instruction or
direction from the COTR and the Contractor shall request the CO to modify the contract
accordingly. Upon receipt of notification from the Contractor, the CO will: (a) advise the
Contractor in writing, within thirty (30) calendar days after receipt of the Contractor's
letter, that:
a.) the technical direction is within the scope of the contract effort and does not
constitute a change to the contract; or
b.) advise the Contractor, within a reasonable length of time, that the instruction or
direction is not within the scope of work but that the Government will modify the
contract to provide for the change; or
c.) advise the Contractor, within a reasonable length of time, that the instruction or
direction is not within the scope of work and that the Government will not modify the
contract and that the instruction or direction is rescinded.
H.3. INTERPRETATION OF MODIFICATION
No oral statement and no written statement by anyone other than the CO, or his
authorized representative acting within the scope of his authority, shall be interpreted as
modifying or otherwise affecting the terms of this resulting contract. All requests for
interpretation or modification shall be made in writing to the CO.
H.4. DETERMINATION OF CHANGE
If, in the opinion of the Contractor, any instruction or direction by the COTR falls outside
the categories defined in the COTR’s Delegation Letter, a copy of which is appended
hereto as Attachment J-5, the Contractor shall not proceed but shall notify the CO in
writing within five (5) working days after receipt of any such instruction or direction from
the COTR and the Contractor shall request the CO to modify the contract accordingly.
Upon receipt of the notification from the Contractor, the CO shall: (a) advise the
Contractor in writing, within thirty (30) calendar days after receipt of the Contractor's
letter, that the technical direction is within the scope of the contract effort and does not
constitute a change to the contract; (b) advise the Contractor, within a reasonable
length of time, that the instruction or direction is not within the scope of work but that the
H- 1
DTFAWA-09-R-00055
Amendment No. 0002
Government will modify the contract to provide for the change; or (c) advise the
Contractor, within a reasonable length of time, that the instruction or direction is not
within the scope of work and that the Government will not modify the contract, in which
case the Contractor is not to perform the work requested by the COTR.
H.5. STANDARD INDUSTRIAL CLASSIFICATION
The North American Industry Classification System (NAICS) code for this acquisition is
Engineering Support Services (541330) (Aerospace exception). Information on the
calculation of average annual receipts can be found in 13 CFR 121.104.
H.6. CONFIDENTIALITY OF DATA AND INFORMATION
a.) The Contractor and any of its subcontractors in performance of this contract, may
have need for access to and use of various types of data and information in the
possession of the Government which the Government obtained under conditions
which restrict the Government's right to use and disclose the data and information, or
which may be of a nature that its dissemination or use other than in the performance
of this contract, would be adverse to the interests of the Government or other parties.
Therefore, the Contractor and its subcontractors agree to abide by any restrictive use
conditions on such data and not to:
(1) knowingly disclose such data and information to others without written
authorization from the Contacting Officer, unless the Government has made
the data and information available to the public; and
(2) use for any purpose other than the performance of this contract any data that
bears a restrictive marking or legend.
b.) In the event the work required to be performed under this contract requires access to
proprietary data of other companies, the Contractor shall obtain agreement from such
other companies for such use unless such data is provided or made available to the
Contractor by the Government. Two copies of such company-to-company
agreements shall be furnished promptly to the Contracting Officer for information
only. These agreements shall prescribe the scope of authorized use of disclosure,
and other terms and conditions to be agreed upon between the parties thereto. It is
agreed by the Contractor that any such data, whether obtained by the Contractor
pursuant to the aforesaid agreement or from the Government, shall be protected from
unauthorized use or disclosure to any individual, corporation, or organization so long
as it remains proprietary.
c.) The Contractor agrees to conduct formal training to make employees aware of the
requirement to maintain confidentiality of data and information, as required above, to
the end that they will be disciplined in the necessity to refrain from divulging either the
proprietary data of other companies or data that is obtained from the Government to
anyone except as authorized. The Contractor shall obtain from each employee,
engaged in any effort connected with this contract, an agreement, in writing, which
shall in substance provide that such employee will not, during his/her employment by
the Contractor, or thereafter, disclose to others or use for his/her own benefit or the
future benefit of any individual any trade secrets, confidential information, or
proprietary/restricted data (to include Government "For Official Use Only") received in
connection with the work under this contract.
H- 2
DTFAWA-09-R-00055
Amendment No. 0002
d.) The Contractor agrees to hold the Government harmless and indemnify the
Government as to any cost/loss resulting from the unauthorized use or disclosure of
third party data or software by the Contractor, its employees, subcontractors, or
agents.
e.) The Contractor agrees to include the substance of this provision in all subcontracts
awarded under this contract. The Contracting Officer will consider case-by-case
exceptions from this requirement for individual subcontracts in the event that: (1) the
Contractor considers the application of the prohibition of this provisions to be
inappropriate and unnecessary in the case of a particular subcontract; (2) the
subcontractor provides a written statement affirming absolute unwillingness to
perform absent some relief from the substance of this prohibition; (3) use of an
alternate subcontract source would unreasonably detract from the quality of effort;
and (4) the Contractor provides the Contracting Officer timely written advance notice
of these and any other extenuating circumstances.
f.) Except as the Contracting Officer specifically authorizes in writing, upon completion
of all work under the contract, the Contractor shall return all such data and
information obtained from the Government, including all copies, modifications,
adaptations, or combinations thereof, to the Contracting Officer. Data obtained from
another company shall be disposed of in accordance with the Contractor's agreement
with that company. If such data or information cannot reasonably be returned to the
Contracting Officer (or to a company), the Contractor shall certify in writing to the
Contracting Officer that all copies, modifications, adaptations, or combinations of the
data or information have been deleted from the Contractor's (and any
subcontractor's) records and destroyed.
g.) The restrictions stated herein do not limit the Contractor's (or subcontractor's) right to
use and disclose any data and information obtained from another source without
restriction.
H.7. RELEASE OF INFORMATION
The Contractor (including individual employees thereof) shall not release or
communicate, except as required by law or regulations, information, including any news
release, public announcement, or advertising material concerned with this contract,
whether orally or in writing, unless authorized by the Contracting Officer. News
releases pertaining to this contract shall not be made without prior approval of the CO.
A minimum of 36 hours advanced notice is required for approval.
H.8. INCORPORATION OF SECTION K BY REFERENCE
Part II, Section K, Representations, Certifications and Notices to Offerors of Proposals,
is hereby incorporated by reference into this contract.
H.9. TRAVEL AND SUBSISTENCE
This clause applies to Cost Reimbursable CLINs for travel and other direct costs
reimbursement where the Contractor proposes and the Government agrees that such
expenses are allowable. This clause does not apply to Fixed Price CLINs.
a.) The Contractor shall be reimbursed for allocable, allowable and reasonable travel
expenses. Except as otherwise provided herein, the Contractor shall be reimbursed
H- 3
DTFAWA-09-R-00055
Amendment No. 0002
for travel on the basis of actual expenses incurred in accordance with the Federal
Travel Regulation (FTR) and subject to the following:
(1) All travel, whether it is within the continental United States or outside the
continental United States, shall be accomplished by commercial carrier, rail,
privately-owned automobile or auto rental and the cost paid by the
Contractor. The Government will reimburse the Contractor in accordance
with the “Federal Travel Regulation” for domestic transportation on the basis
of actual cost if by commercial or Government carrier, and at the current rate
per mile, plus road and bridge tolls.
(2) The travel reimbursement herein includes only that travel (commercial
carrier, or private automobile or auto rental) performed from the Contractor’s
plant to the site of work, between the site of work, and from the site of work
to the Contractor’s plant. Travel within a Government installation where
Government transportation is available, and travel performed for personal
convenience, including daily travel to and from work, will not be reimbursed.
(3) Relocation costs and travel costs incidental to relocation are not allowable as
a direct charge to the contract and will not be reimbursed as a direct charge.
(4) The Contractor shall use alternate airports where available and within a
reasonable commuting distance, if it will result in lower costs.
(5) The Contractor shall conduct a cost analysis prior to the start of travel to
determine the overall most cost effective means.
b.) Per Diem: The Contractor will be reimbursed for the expense of meals, lodging,
transportation between places of lodging or business and places where meals are
taken and any other miscellaneous travel and living expenses incurred in the
performance of this contract at the per diem rate as set forth in accordance with the
GSA “Federal Travel Regulation.” Per Diem shall be payable only when the
Contractor’s employee is in an authorized travel status. The per diem rate shall be
established in accordance with the “Department of Transportation Travel
Regulations” or a set rate agreed upon by the parties, however, such a set rate shall
not exceed the maximum amount permitted by the GSA “Federal Travel
Regulations.”
c.) Contractor Use of Government Discount Rates:
(1) To the maximum extent practicable and consistent with travel requirements,
the Contractor agrees to use the reduced air transportation rates and
reduced hotel accommodation rates provided through available Government
discount rates. These discount rates are for bona fide employee travel that
are otherwise reimbursable as a direct cost pursuant to the contract when
use of such rates results in the lowest overall cost.
(2) Upon receipt of a list of eligible Contractor employees, the Contracting
Officer will provide the Contractor with an agency letter of identification for
presentation to participating airlines and hotels.
(3) The Federal Travel Directory, which GSA publishes monthly, identifies
current contract airlines and hotels. The symbol in the Federal Travel
Directory for discount hotel rates is CRC.
d.) Contractor will synopsize the travel (where and when) and list the total price for the
travel on the invoice that will be sent in accordance with the instructions in Section G.
H- 4
DTFAWA-09-R-00055
Amendment No. 0002
A copy of the Contractor’s travel expense report accompanied by a delineation of the
travel will be sent to the FAA’s CO at the same time the invoice is submitted for
payment.
e.) Travel may be burdened with an administrative charge reflecting the effort necessary
to book and administer travel costs, which must be a percentage of the total travel
costs allowed. The maximum charge for the base year period and each option year
period must be the administrative charge not to exceed the following:
Base Period Option 1 Option 2 Option 3 Option 4
f.) Except for local travel that does not require airfare and overnight stay, or either, no
travel may be taken without the specific approval of the FAA CO. The contractor
shall submit requests for travel sufficiently in advance of the travel dates to allow for
program office review and Contracting Officer approval. In addition, for international
travel, contractor shall submit requests sufficiently in advance of the planned travel
dates to allow processing of all required notifications to the U.S. State Department.
H.10. WEATHER-RELATED ABSENCE
As a matter of policy, contractors may only invoice the FAA for the hours actually
worked, and contractor employees should not assume their absence will be excused
when FAA employees have been granted leave.
Individual contractor offices may allow their employees to arrive late or be dismissed
early, when warranted due to adverse weather conditions, without a commensurate
reduction in the hours charged to the FAA for those employees working that day when
all of the following conditions are met:
a.) Documentation exists that those individuals worked at least the equivalent number of
hours during that same pay period;
b.) The Contractor grants or refuses leave to its employees in a manner that is
consistent both within that company and with the policy for FAA employees; and
c.) The Contractor allows for weather-related leave only in coordination with the ATO or
the SWIM Program Office. It is anticipated that contractor employees would not be
excused from absence when the coordinating FAA offices are not granting a similar
type of leave.
No contractor is required or presumed to grant their employees weather-related
absence; it is at the discretion of each company organization; in consideration of the
above conditions and in coordination with each applicable FAA office. When the FAA
offices close, Contractor employees may work in their local offices, from their homes, or
be granted access to Government buildings as agreed between the appropriate offices.
H.11. WORK SHIFTS
Each Contractor employee will, under normal circumstances, work up to an eight-hour
shift daily depending upon the hours authorized for the labor category. The time of the
shift will normally be within the office hours of 6:00 a.m. to 6:00 p.m., Monday through
Friday, the exact hours of work will be set so that the contractor personnel will work
concurrently along side their Government counterparts and those times and may vary
H- 5
DTFAWA-09-R-00055
Amendment No. 0002
over the course of performance. Exceptions to this include excused absences and
observed holidays.
Many FAA facilities utilize an alternate work schedule (AWS). The Contractor may
request approval, in writing, from the COTR and CO, for Contractor personnel to
concurrently work an AWS along side their Government counterparts.
H.12. PERSONAL SERVICES
No personal services shall be performed under this Contract. No Contractor employee
will be directly supervised by the Government. All individual Contractor employee
assignments, and daily work direction, shall be given by the applicable Contractor
supervisor. If the Contractor believes that any Government action or communication
has been given that would create a personal services relationship between the
Government and any Contractor employee, the Contractor shall promptly notify the
Contracting Officer of this communication or action.
The Contractor shall not perform any inherently Governmental actions under this
Contract. No Contractor employee shall hold him or herself out to be a Government
employee, agent or representative. No Contractor employee shall state orally or in
writing at any time that he or she is acting on behalf of the Government. In all
communications with third parties in connection with this Contract, Contractor
employees shall identify themselves as Contractor employees and specify the name of
the company for which they work. In all communications with other Government
contractors in connection with this Contract, the Contractor employee shall state that
they have no authority to in any way change the Contract and that if the other contractor
believes this communication to be a direction to change their contract, they should notify
the Contracting Officer for that contract and not carry out the direction until a clarification
has been issued by the Contracting Officer.
The Contractor shall insure that all of its employees working on this Contract are
informed of the substance of this clause. Nothing in this clause shall limit the
Government's rights in any way under any other provision of the Contract, including
those related to the Government's right to inspect and accept the services to be
performed under this Contract. The substance of this clause shall be included in all
subcontracts at any tier.
H.13. UNCOMPENSATED OVERTIME
The use of uncompensated overtime is not authorized. Uncompensated overtime
means the hours worked without additional compensation in excess of an average of 40
hours per week by direct charge employees who are exempt from the Fair Labor
Standards Act. Compensated personal absences such as holidays, vacations, and sick
leave shall be included in the normal work week for purposes of computing
uncompensated overtime hours.
H.14. CONTRACTOR PERFORMANCE INFORMATION
In conformance with the Government’s need to record and maintain information on
contractor performance during the life of this contract, the Government will periodically
H- 6
DTFAWA-09-R-00055
Amendment No. 0002
evaluate the manner in which the contractor performed in accordance with contract
requirements such as: quality of service; cost efficiencies; timeliness; business
relations; history of reasonable and cooperative behavior; commitment to customer
satisfaction; and key personnel. Performance assessments will be shared with the
Contractor and an opportunity to comment will be provided prior to inclusion in the FAA
past performance database. Information obtained as a result of the evaluation(s) may
be shared with Government agencies for their use in support of future award decisions.
H.15. WAIVER PROVISION
The Contractor may petition the Contracting Officer, anytime after award, and request a
waiver for any of the minimum requirements for an individual to be qualified for a
specific labor category included in the contract. The waiver shall provide the name of
the individual and his/her work location, the proposed labor category for which the
waiver is requested, and the proposed effective date of the request. It should also
contain a full justification as to why the minimum requirements should be waived, and
the benefit to the FAA as a result of waiver approval. The contractor shall propose a
discount to the direct labor rate for all requested waivers. If the waiver is not approved,
the request shall indicate whether the individual will work in another labor category on
the contract to which they qualify. Normally waivers will be processed within 15 days of
submission. Requests for approval of waivers must be approved by the COTR and
contracting officer.
H.16. GOVERNMENT PROPERTY MANAGEMENT
a.) The Contractor shall be accountable for all Government property that was provided
either to the Contractor or to its subcontractors as Government Furnished
Equipment/Government Furnished Property (GFE/GFP) or contract acquired property
(CAP). The Contractor shall not accept any GFP without FAA Form 4650-12,
Materiel Requisition/Issue/Receipt, to transfer custodianship to the Contractor. When
property is returned to the Government, FAA Form 4650-12 shall be used.
b.) The Contractor shall be responsible for interfacing with TSM Property Administrator.
The Contracting Officer (CO) will designate a TSM Property Administrator who will be
the primary point of contact relating to GFE, GFP or CAP. A copy of all
correspondence sent to the TSM Property Administrator shall also be sent to the CO
and COTR.
c.) The Contractor shall develop and maintain a property control system that will
adequately control, preserve, protect, and maintain all Government property in
accordance with Government property clauses. The Contractor may utilize the TSM
Property Inventory Management System (TPIMS) to manage and control GFP/CAP.
The Contractor shall:
(1) Submit a property control system plan to the COTR for review and approval
within 60 calendar days after Contract award. The Contractor shall correct
any deficiencies identified in the system by the Government within 30 days
after notification of the deficiencies.
(2) Designate a property management point of contact for the contract.
(3) Maintain required property management records.
H- 7
DTFAWA-09-R-00055
Amendment No. 0002
(4) Report, within ten (10) working days all losses, damage, or destruction of
property to the Property Administrator.
(5) Submit a final inventory of all accountable GFE, GFP or CAP properly
certified by an authorized representative of the Contractor, to the TSM
Property Administrator upon completion or termination of the Contract.
d.) The Government has the right to inspect and perform compliance reviews of the
Contractor's property control system, including all records.
e.) The FAA MUST specifically authorize each Order in which GFE, GFP, or CAP will be
acquired. The authorization request shall be submitted to the COTR or CO and shall
include the following information:
(1) Contract Number
(2) Date of Request
(3) Description
(4) Model
(5) Type: hardware or software
(6) Vendor
(7) Quantity
(8) Unit Price
(9) Extended Price
(10) Tax
(11) Shipping and Handling
(12) Total Cost
(13) Explanation of why the property is needed. Once approved by the CO or
COTR, a copy will be provided to the TSM Property Administrator.
f.) For GFE/GFP/CAP to be installed within the Contractor’s facility, the Contractor shall
use FAA Form 4640-12, Material Requisition/Issue/Receipt, to transfer accountability
from the FAA. For GFE/GFP, the FAA Form 4650-12, which originally provided the
property to the Contractor, shall be attached to the return document.
g.) At the completion or termination of the contract or when the property becomes
excess to the needs of the contract, the Contractor shall report the property
regardless of value, to the appropriate Property Administrator. The Contractor shall
identify excess inventory on an excess inventory report. The excess inventory report
shall contain the following information:
(1) Excess Date: DD/MM/YY
(2) Pick-up Date: DD/MM/YY
(3) Item Description: Type or category such as printer, CPU, laptop, etc.
(4) Model: Type or number such as Pentium III, 17’’ display, etc.
(5) Serial Number: A unique number assigned to each piece of equipment by
vendor.
(6) DOT Bar Code: A unique number assigned to GFP, GFE and CAP by the
TSM Property Administrator.
(7) Condition: Equipment condition such as damaged, does not meet
requirements, missing battery, etc.
(8) Location: The current location where the equipment is stored for pick up.
(9) Property Type: GFP, GFE or CAP.
H- 8
DTFAWA-09-R-00055
Amendment No. 0002
h.) A Report of Survey, FAA Form 4630-8, shall be submitted by the Contractor to the
Contracting Officer (for forwarding to the Property Administrator) for all cases of
missing, stolen, or damaged accountable Government property when the facts
become known. This includes property under the control of a subcontractor. The
Contracting Officer and Property Administrator shall review the Report of Survey to
determine the Contractor's liability (see FAA Order 4650.3, Survey of Lost, Damaged,
or Destroyed Government Personal Property). The report shall include the following
information:
(1) The Contractor's name and the contract number.
(2) Description of items missing, stolen, damaged, or unreasonably consumed to
include where appropriate, the FAA bar code number, manufacturer's name,
model, and serial numbers, last known condition, acquisition date, and cost.
Cost of repairs in instances of damaged items. Date, time, and cause of
origin of the loss, damage, destruction, or consumption. Insurance, if any,
covering the Government property and whether a replacement item was
purchased.
(3) Actions taken by the Contractor to prevent further loss, damage, destruction,
or unreasonable consumption and to prevent recurrence of similar incidents;
and other facts or circumstances relevant to the determination of liability and
responsibility for repair or replacement. Copies of the law enforcement
agency reports providing circumstances surrounding the incident shall also
be submitted, if any.
i.) The Contractor shall conduct a physical inventory at the beginning of the contract,
every year in September during the term of the contract, and at the end of contract.
The Contractor shall prepare and submit to the Contracting Officer and Property
Administrator the results of the physical inventory on an SF 1428. The report shall
include, but is not limited to, GFP, GFE, or CAP that was procured under the contract
as an Other Direct Charge (ODC). In addition to the required information on the SF
1428, the following information shall be provided:
(1) Vendor: Manufacturer Name
(2) Item Description: Type or category such as printer, CPU, laptop, etc.
(3) Model: Type or number such as Pentium III, 17’’ display, etc.
(4) Serial Number: A unique number assigned to each piece of equipment by
vendor.
(5) DOT Bar Code: A unique number assigned to GFP, GFE and CAP by the
TSM Property Administrator.
(6) Location: Where the GFP, GFE or CAP is being deployed and used.
(7) Property Type: Each item shall be designated as GFP, GFE, or CAP.
(8) Value: It can be the purchased price for CAP, resale price for GFE and GFP.
(9) Date: This date reflects when the item was acquired. It is provided in the
format of MM/DD/YY.
(10) Status: This field provides an indication of the property’s condition. It can
be in-use, excess, loss, damaged, or destroyed.
H- 9
DTFAWA-09-R-00055
Amendment No. 0002
H.17. ACCEPTANCE PROCESS FOR DELIVERABLES
Notice of Delivery of Deliverables shall be made to the Contracting Officer and the
COTR via e-mail with the Deliverable being sent to the Team Lead responsible for it and
as identified in this Section. Upon receipt, the respective Team Lead shall review it for
conformance to the requirements of the CDRL, Data Item Description (DID), and TO, as
applicable. Within five (5) business days after transmittal, the Team Lead shall advise
the Contracting Officer of any objections to the Deliverable. If no objections are taken
by the Team Lead within that time, the Deliverable will be accepted as presented.
H.18. GOVERNMENT FURNISHED PROPERTY (GFP)
The FAA will provide Government Furnished Property (GFP) to the Contractor for FTI
Remote Access Capabilities (FRAC) accounts for each approved Contractor personnel
for access to the FAA Local Area Network (LAN) account, as required for performance
of their duties.
H- 10
DTFAWA-09-R-00055
Amendment No. 0002
PART II - SECTION I
CONTRACT CLAUSES
I.1. CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (DECEMBER
2005)
This screening information request (SIR) or contract, as applicable, incorporates by
reference the provisions or clauses listed below with the same force and effect as if they
were given in full text. Upon request, the Contracting Officer will make the full text
available, or Offerors and contractors may obtain the full text via Internet at:
http://conwrite.faa.gov (on this web page, select "Search and View Clauses").
3.1.7-5 Disclosure of Conflicts of Interest (February 2009)
Cancellation, Rescission and Recovery of Funds for Illegal or Improper
3.1.8-1 Activity (September 2000)
3.1.8-2 Price or Fee Adjustment for Illegal or Improper Activity (September 2000)
3.2.2.3-29 Integrity of Unit Prices (July 2004)
3.2.2.3-33 Order of Precedence (February 2009)
Protecting the Government’s Interest when Subcontracting with Contractors
3.2.2.7-6 Debarred, Suspended, or Proposed for Debarment (February 2009)
3.2.2.7-8 Disclosure of Team Arrangements (April 2008)
3.2.2.8-1 Material Requirements (October 2007)
3.2.4-5 Allowable Cost and Payment (April 2001)
3.2.4-34 Option to Extend Services (April 1996)
3.2.5-1 Officials Not to Benefit (April 1996)
3.2.5-3 Gratuities or Gifts (January 1999)
3.2.5-4 Contingent Fees (October 1996)
3.2.5-5 Anti-Kickback Procedures (October 1996)
3.2.5-6 Restrictions on Subcontractor Sales to the FAA (April 1996)
Disclosure Regarding Payments to Influence Certain Federal Transactions
3.2.5-7 (June 1999)
3.2.5-8 Whistleblower Protection for Contractor Employees (April 1996)
3.2.513 Contractor Code of Business Ethics and Conduct (July 2008)
3.3.1-1 Payments (April 1996)
3.3.1-8 Extras (April 1996)
3.3.1-9 Interest (January 2008)
3.3.1-10 Availability of Funds (April 1996)
3.3.1-14 Limitation of Funds (April 1996)
3.3.1-15 Assignment of Claims (April 1996)
3.3.1-17 Prompt Payment (January 2008)
Payment by Electronic Funds Transfer - Central Contractor Registration
3.3.1-34 (February 2009)
3.3.2-1 FAA Cost Principles (October 1996)
3.4.1-10 Insurance—Work on a Government Installation (July 1996)
3.4.1-11 Insurance--Liability to Third Persons (October 1996)
3.4.1-13 Errors and Omissions (July 1996)
I-1
DTFAWA-09-R-00055
Amendment No. 0002
3.4.2-8 Federal, State, and Local Taxes--Fixed Price Contract (April 1996)
3.5-1 Authorization and Consent (January 2009)
Notice and Assistance Regarding Patent and Copyright Infringement
3.5-2 (January 2009)
3.5-13 Rights in Data--General (January 2009)
3.5-13 alt 4 Rights in Data--General Alternate IV (October 1996)
Representation of Limited Rights Data and Restricted Computer Software
3.5-14 (October 1996)
3.5-15 Additional Data Requirements (April 1996)
Utilization of Small, Small Disadvantaged and Women-Owned, and Service-
3.6.1-3 Disabled Veteran Owned Small Business Concerns (September 2001)
Small, Small Disadvantaged and Women-Owned and Service-Disabled
3.6.1-4 Veteran Owned Small Business Subcontracting Plan (April 2007)
3.6.1-6 Liquidated Damages--Subcontracting Plan (September 2001)
3.6.1-9 Mentor Protégé Program (October 2006)
3.6.2-2 Convict Labor (April 1996)
3.6.2-9 Equal Opportunity (August 1998)
3.6.2-10 Equal Opportunity Preaward Clearance of Subcontracts (November 1997)
Affirmative Action for Special Disabled and Vietnam Era Veterans (April
3.6.2-12 2007)
3.6.2-13 Affirmative Action for Workers With Disabilities (April 2000)
Employment Reports on Special Disabled Veterans and Veterans of Vietnam
3.6.2-14 Era (April 2007)
3.6.2-16 Notice to the Government of Labor Disputes (April 1996)
3.6.2-35 Prevention of Sexual Harassment (August 1998)
Notification of Employees Rights Concerning Payment of Union Dues or
3.6.2-37 Fees (April 2007)
3.6.2-39 Trafficking in Persons (January 2008)
3.6.3-2 Clean Air and Clean Water (April 1996)
3.6.3-16 Drug Free Workplace (January 2004)
3.6.4-10 Restrictions on Certain Foreign Purchases (April 1996)
Utilization of Indian Organizations and Indian Owned Economic Enterprises
3.6.5-1 (February 2009)
3.8.2-9 Site Visit (April 1996)
Protection of Government Buildings, Equipment, and Vegetation (April
3.8.2-10 1996)
3.8.2-11 Continuity of Services (October 2008)
3.9.1-1 Contract Disputes (November 2002)
3.9.1-2 Protest After Award (August 1997)
3.10.1-3 Penalties for Unallowable Costs (October 1996)
3.10.1-7 Bankruptcy (April 1996)
3.10.1-12 Changes--Fixed-Price (April 1996)
3.10.1-12 Alternate I (April 1996)
3.10.1-25 Novation and Change-Of-Name Agreements (October 2007)
3.10.2-1 Subcontracts (Fixed-Price Contracts) (April 1996)
3.10.2-5 Competition in Contracting (January 1998)
3.10.3-1 Definitions (April 2004)
I-2
DTFAWA-09-R-00055
Amendment No. 0002
3.10.5-1 Product Improvement/ Technology Enhancement (April 1996)
Termination for Convenience of the Government (Fixed Price) (October
3.10.6-1 1996)
3.10.6-4 Default (Fixed-Price Supply and Service) (October 1996)
3.10.6-7 Excusable Delays (October 1996)
3.11-61 Preference for U.S. Flag Carriers (April 1999)
3.13-3 Printing/Copying Double-sided on Recycled Paper (July 2008)
3.13-5 Seat Belt Use by Contractor Employees (January 1999)
3.13-10 Contractor Attendance at FAA Sponsored Training (January 2003)
3.13-11 Plain Language (July 2006)
3.14-5 Sensitive Unclassified Information (SUI) (July 2008)
I.2. EXCLUSION FROM FUTURE AGENCY CONTRACTS (3.1.7-1, AUGUST 1997)
(a) Work under this contract may create a future organizational conflict of interest (OCI)
that could prohibit the Contractor from competing for, or being awarded future
Government contracts.
The following examples illustrate situations in which questions concerning
organizational conflicts of interest may arise. They are not all-inclusive, but are
intended to help the Contracting Officer apply general guidance to individual contract
situations:
(1) Unequal access to information. Access to "nonpublic information" as part of the
performance of an FAA contract could provide the contractor a competitive advantage in
a later competition for another FAA contract. Such an advantage could easily be
perceived as unfair by a competing vendor who is not given similar access to the
relevant information. If the requirements of the FAA procurement anticipate the
successful vendor may have access to nonpublic information, the successful vendor
should be required to submit and negotiate an acceptable mitigation plan. Alternatively,
the "nonpublic information" may be provided to all vendors.
(2) Biased ground rules. A contractor in the course of performance of an FAA contract,
has in some fashion established important "ground rules" for another FAA contract,
where the same contractor may be a competitor. For example, a contractor may have
drafted the statement of work, specifications, or evaluation criteria of a future FAA
procurement. The primary concern of the FAA in this case is that a contractor so
situated could slant key aspects of a procurement in its own favor, to the unfair
disadvantage of competing vendors. If the requirements of the FAA procurement
anticipate the contractor may have been in a position to establish important ground
rules, including but not limited to those described herein, the contractor should be
required to submit and negotiate an acceptable mitigation plan.
(3) Impaired objectivity. A contractor in the course of performance of an FAA contract,
is placed in a situation of providing assessment and evaluation findings over itself, or
another business division, or subsidiary of the same corporation, or other entity with
which it has a significant financial relationship. The concern in this case is that the
I-3
DTFAWA-09-R-00055
Amendment No. 0002
contractor's ability to render impartial advice to the FAA could appear to be undermined
by the contractor's financial or other business relationship to the entity whose work
product is being assessed or evaluated. In these situations, a "walling off" of lines of
communication may well be insufficient to remove the perception that the objectivity of
the contractor has been tainted. If the requirements of the FAA procurement indicate
that the successful vendor may be in a position to provide evaluations and assessments
of itself or corporate siblings, or other entity with which it has a significant financial
relationship, the affected contractor should provide a mitigation plan that includes
recusal by the vendor from the affected contract work. Such recusal might include
divestiture of the work to a third party vendor.
(b) In order to prevent a future OCI resulting from potential bias, unfair competitive
advantage, or impaired objectivity, the Contractor shall be subject to the following
restrictions:
(1) The Contractor shall be excluded from competition for, or award of any government
contracts as to which, in the course of performance of this contract, the Contractor has
received advance procurement information before such information has been made
generally available to other persons or firms.
(2) The Contractor shall be excluded from competition for, or award of any FAA
contract for which the contractor actually assists in the development of the screening
information request (SIR), specifications or statements of work.
(3) The Contractor shall be excluded from competition for or award of any government
contract which calls for the evaluation of system requirements, system definitions, or
other products developed by the Contractor under this contract.
(4) The Contractor shall be excluded from competition for, or award of any government
contract which calls for the construction or fabrication of any system, equipment,
hardware, and/or software for which the Contractor participated in the development of
requirements or definitions pursuant to this contract.
(c) This clause shall not exclude the Contractor from performing work under any
amendment or modification to this contract or from competing for award for any future
contract for work that is the same or similar to work performed under this contract.
(d) The term "contractor" as used in this clause, includes any person, firm or
corporation which has a majority or controlling interest in the contractor or in any parent
corporation thereof, any person, firm , or corporation in or as to which the contractor (or
any parent or subsidiary corporation thereof) has a majority or controlling interest. The
term also includes the corporate officers of the contractor, those of any corporation
which has a majority or controlling interest in the contractor, and those of any
corporation in which the contractor (or any parent or subsidiary corporation thereof) has
a majority or controlling interest.
I-4
DTFAWA-09-R-00055
Amendment No. 0002
(e) The agency may in its sole discretion, waive any provisions of this clause if deemed
in the best interest of the Government. The exclusions contained in this clause shall
apply for the duration of this contract and for three (3) years after completion and
acceptance of all work performed hereunder.
(f) If any provision of this clause excludes the Contractor from competition for, or award
of any contract, the Contractor shall not be permitted to serve as a subcontractor, at any
tier, on such contract. This clause shall be incorporated into any subcontracts or
consultant agreements awarded under this contract unless the Contracting Officer
determines otherwise.
I.3. DISCLOSURE OF CERTAIN EMPLOYEE RELATIONSHIPS (3.1.7-6 OCTOBER
2006)
a.) The policy of the FAA is to avoid doing business with contractors, subcontractors,
and consultants who have a conflict of interest or an appearance of a conflict of
interest. The purpose of this policy is to maintain the highest level of integrity within
its workforce and to ensure that the award of procurement contracts is based upon
fairness and merit.
b.) The contractor must provide to the Contracting Officer the following information with
its proposal and must provide an information update within 30 days of the award of a
contract, any subcontract, or any consultant agreement, or within 30 days of the
retention of a Subject Individual or former FAA employee subject to this clause:
(1) The names of all Subject Individuals who:
i) participated in preparation of proposals for award; or
ii) are planned to be used during performance; or
iii) are used during performance; and
(2) The names of all former FAA employees, retained by the contractor who
were employed by FAA during the two year period immediately prior to the
date of:
i) the award; or
ii) their retention by the contractor; and
(3) The date on which the initial expression of interest in a future financial
arrangement was discussed with the contractor by any former FAA employee
whose name is required to be provided by the contractor pursuant to
subparagraph (2); and
(4) The location where any Subject Individual or former FAA employee whose
name is required to be provided by the contractor pursuant to subparagraphs
(1) and (2) are expected to be assigned.
c.) "Subject Individual" means a current FAA employee's father, mother, son, daughter,
brother, sister, uncle, aunt, first cousin, nephew, niece, husband, wife, father-in-law,
mother-in-law, son-in-law, daughter-in-law, brother-in-law, sister-in-law, stepfather,
stepmother, stepson, stepdaughter, stepbrother, stepsister, half brother, half sister,
spouse of an in-law, or a member of his/her household.
d.) The contractor must incorporate this clause into all subcontracts or consultant
agreements awarded under this contract and must further require that each such
subcontractor or consultant incorporate this clause into all subcontracts or consultant
I-5
DTFAWA-09-R-00055
Amendment No. 0002
agreements at any tier awarded under this contract unless the Contracting Officer
determines otherwise.
e.) The information as it is submitted must be certified as being true and correct. If
there is no such information, the certification must so state.
f.) Remedies for nondisclosure: The following are possible remedies available to the
FAA should a contractor misrepresent or refuse to disclose or misrepresent any
information required by this clause:
(1) Termination of the contract.
(2) Exclusion from subsequent FAA contracts.
(3) Other remedial action as may be permitted or provided by law or regulation
or policy or by the terms of the contract.
g.) Annual Certification. The contractor must provide annually, based on the
anniversary date of contract award, the following certification in writing to the
Contracting Officer:
ANNUAL CERTIFICATION OF DISCLOSURE OF CERTAIN
EMPLOYEE RELATIONSHIPS
The contractor represents and certifies that to the best of its
knowledge and belief that during the prior 12 month period:
[ ] A former FAA employee(s) or Subject Individual(s) has
been retained to work under the contract or subcontract or
consultant agreement and complete disclosure has been
made in accordance with subparagraph (b) of AMS Clause
3.1.7-6.
[ ] No former FAA employee(s) or Subject Individual(s) has
been retained to work under the contract or subcontract or
consultant agreement, and disclosure required by AMS
Clause 3.1.7-6 is not applicable.
Authorized Representative
Company Name:
Date:
I-6
DTFAWA-09-R-00055
Amendment No. 0002
I.4. INDEFINITE QUANTITY (3.2.4-20 JULY 1996)
a.) This is an indefinite-quantity contract for the services specified in Section C and
effective for the period stated in Section B. The guarantee minimum labor hours for this
contract are stated in the Base Year period in Section B. These minimum labor hours
are consideration for all CLINs, whether the CLINs state a zero (i.e., “0”) minimum
quantity or greater. The maximum quantities specified in Section B are estimates only
and may not purchased by this contract.
b.) The Contractor’s performance will be made only as authorized by orders issued in
accordance with the "Ordering" clause in Section H. The Contractor must provide to the
Government, when and if ordered, the services and associated deliverables as specified
in Sections B and J.2, respectively, up to and including the quantity designated in
Section B as the maximum. The Government will order at least the minimum quantity
designated in Section B.
c.) Except for any limitations on quantities in the "Order Limitations" clause or in the
Section B, there is no limit on the number of orders that may be issued. The
Government may issue orders requiring performance at multiple locations.
d.) Any order issued during the effective period of this contract and not completed within
that period must be completed by the Contractor within the time specified in the order.
The contract must govern the Contractor's and Government's rights and obligations with
respect to that order to the same extent as if the order were completed during the
contract's effective period; provided, that the Contractor must not be required to make
any deliveries under this contract after beyond ninety (90) days after the contract’s
effective period.
I.5. CENTRAL CONTRACTOR REGISTRATION (3.3.1-33 JANUARY 2008)
a.) Definitions. As used in this clause
“Central Contractor Registration (CCR) database” means the
primary Government repository for Contractor information
required for the conduct of business with the Government.
“Data Universal Numbering System (DUNS) number” means
the 9-digit number assigned by Dun and Bradstreet, Inc.
(D&B) to identify unique business entities.
“Data Universal Numbering System +4 (DUNS+4) number”
means the DUNS number assigned by D&B plus a 4-
character suffix that may be assigned by a business
concern. (D&B has no affiliation with this 4-character suffix.)
This 4-character suffix may be assigned at the discretion of
the business concern to establish additional CCR records for
identifying alternative Electronic Funds Transfer (EFT)
accounts for the same parent concern.
“Registered in the CCR database” means that the Contractor
has entered all mandatory information, including the DUNS
number or the DUNS+4 number, into the CCR database.
I-7
DTFAWA-09-R-00055
Amendment No. 0002
b.)
(1) By submission of an offer, the Offeror acknowledges the requirement that a
prospective awardee shall be registered in the CCR database prior to award,
during performance, and through final payment of any contract, basic
agreement, basic ordering agreement, or blanket purchasing agreement
resulting from this solicitation.
(2) The Offeror shall enter, in Representations, Certifications and Other
Statements of Offerors Section of the solicitation, the DUNS or DUNS +4
number that identifies the Offeror’s name and address exactly as stated in
the offer. The DUNS number will be used by the Contracting Officer to verify
that the Offeror is registered in the CCR database.
c.) If the Offeror does not have a DUNS number, it should contact Dun and Bradstreet
directly to obtain one.
(1) An Offeror may obtain a DUNS number
i) If located within the United States, by calling Dun and Bradstreet at 1-866-
705-5711 or via the Internet at http://fedgov.dnb.com/webform; or
ii) If located outside the United States, by contacting the local Dun and
Bradstreet office.
(2) The Offeror should be prepared to provide the following information:
i) Company legal business.
ii) Tradestyle, doing business, or other name by which your entity is
commonly recognized.
iii) Company Physical Street Address, City, State, and ZIP Code.
iv) Company Mailing Address, City, State and ZIP Code (if different from
physical street address).
v) Company Telephone Number.
vi) Date the company was started.
vii) Number of employees at your location.
viii) Chief executive officer/key manager.
ix) Line of business (industry).
x) Company Headquarters name and address (reporting relationship within
your entity).
d.) If the Offeror does not become registered in the CCR database in the time
prescribed by the Contracting Officer, the Contracting Officer may proceed to award
to the next otherwise successful registered Offeror.
e.) Processing time, which normally takes 48 hours, should be taken into consideration
when registering. Offerors who are not registered should consider applying for
registration immediately upon receipt of this solicitation.
f.) The Contractor is responsible for the accuracy and completeness of the data within
the CCR database, and for any liability resulting from the Government’s reliance on
inaccurate or incomplete data. To remain registered in the CCR database after the
initial registration, the Contractor is required to review and update on an annual basis
from the date of initial registration or subsequent updates its information in the CCR
database to ensure it is current, accurate and complete. Updating information in the
CCR does not alter the terms and conditions of this contract and is not a substitute
for a properly executed contractual document.
I-8
DTFAWA-09-R-00055
Amendment No. 0002
g.)
(1)
i) If a Contractor has legally changed its business name, “doing business as”
name, or division name (whichever is shown on the contract), or has
transferred the assets used in performing the contract, but has not
completed the necessary requirements regarding novation and change-
of-name agreements in AMS Procurement Guidance T3.10.1.A-8, the
Contractor shall provide the responsible Contracting Officer a minimum of
one business day’s written notification of its intention to:
(a) change the name in the CCR database;
(b) comply with the requirements of T3.10.1.A-8; and
(c) agree in writing to the timeline and procedures specified by the
responsible Contracting Officer. The Contractor must provide
the Contracting Officer with the notification, sufficient
documentation to support the legally changed name.
ii) If the Contractor fails to comply with the requirements of paragraph
(g)(1)(i) of this clause, or fails to perform the agreement at paragraph
(g)(1)(i) of this clause, and, in the absence of a properly executed
novation or change-of-name agreement, the CCR information that shows
the Contractor to be other than the Contractor indicated in the contract
will be considered to be incorrect information within the meaning of the
“Suspension of Payment” paragraph of the electronic funds transfer (EFT)
clause of this contract.
(2) The Contractor shall not change the name or address for EFT payments or
manual payments, as appropriate, in the CCR record to reflect an assignee
for the purpose of assignment of claims. Assignees shall be separately
registered in the CCR database. Information provided to the Contractor’s
CCR record that indicates payments, including those made by EFT, to an
ultimate recipient other than that Contractor will be considered to be incorrect
information within the meaning of the “Suspension of payment” paragraph of
the EFT clause of this contract.
h.) Offerors and Contractors may obtain information on registration and annual
confirmation requirements via the internet at http://www.ccr.gov/ or by calling 1-888-
227-2423, or 269-961-5757.
I.6. PAYMENT BY ELECTRONIC FUNDS TRANSFER/CENTRAL CONTRACTOR
REGISTRATION (3.3.1-34 OCTOBER 2005)
a.) Method of payment.
(1) All payments by the Government under this contract shall be made by
electronic funds transfer (EFT), except as provided in paragraph (a)(2) of this
clause. As used in this clause, the term “EFT” refers to the funds transfer and
may also include the payment information transfer.
(2) In the event the Government is unable to release one or more payments by
EFT, the Contractor agrees to either:
i) Accept payment by check or some other mutually agreeable method of
payment; or
I-9
DTFAWA-09-R-00055
Amendment No. 0002
ii) Request the Government to extend the payment due date until such time
as the Government can make payment by EFT (but see paragraph (d) of
this clause).
b.) Contractor’s EFT information. The Government shall make payment to the
Contractor using the EFT information contained in the Central Contractor Registration
(CCR) database. In the event that the EFT information changes, the Contractor shall
be responsible for providing the updated information to the CCR database.
c.) Mechanisms for EFT payment. The Government may make payment by EFT through
either the Automated Clearing House (ACH) network, subject to the rules of the
National Automated Clearing House Association, or the Fedwire Transfer System.
The rules governing Federal payments through the ACH are contained in 31 CFR
Part 210.
d.) Suspension of payment. If the Contractor’s EFT information in the CCR database is
incorrect, then the Government need not make payment to the Contractor under this
contract until correct EFT information is entered into the CCR database; and any
invoice or contract financing request shall be deemed not to be a proper invoice for
the purpose of prompt payment under this contract. The prompt payment terms of the
contract regarding notice of an improper invoice and delays in accrual of interest
penalties apply.
e.) Liability for uncompleted or erroneous transfers.
(1) If an uncompleted or erroneous transfer occurs because the Government
used the Contractor’s EFT information incorrectly, the Government remains
responsible for?
i) Making a correct payment;
ii) Paying any prompt payment penalty due; and
iii) Recovering any erroneously directed funds.
(2) If an uncompleted or erroneous transfer occurs because the Contractor’s
EFT information was incorrect, or was revised within 30 days of Government
release of the EFT payment transaction instruction to the Federal Reserve
System, and?
i) If the funds are no longer under the control of the payment office, the
Government is deemed to have made payment and the Contractor is
responsible for recovery of any erroneously directed funds; or
ii) If the funds remain under the control of the payment office, the
Government shall not make payment, and the provisions of paragraph (d)
of this clause shall apply.
f.) EFT and prompt payment. A payment shall be deemed to have been made in a
timely manner in accordance with the prompt payment terms of this contract if, in the
EFT payment transaction instruction released to the Federal Reserve System, the
date specified for settlement of the payment is on or before the prompt payment due
date, provided the specified payment date is a valid date under the rules of the
Federal Reserve System.
g.) EFT and assignment of claims. If the Contractor assigns the proceeds of this
contract as provided for in the assignment of claims terms of this contract, the
Contractor shall require as a condition of any such assignment, that the assignee
shall register separately in the CCR database and shall be paid by EFT in
I-10
DTFAWA-09-R-00055
Amendment No. 0002
accordance with the terms of this clause. Notwithstanding any other requirement of
this contract, payment to an ultimate recipient other than the Contractor, or a financial
institution properly recognized under an assignment of claims, is not permitted. In all
respects, the requirements of this clause shall apply to the assignee as if it were the
Contractor. EFT information that shows the ultimate recipient of the transfer to be
other than the Contractor, in the absence of a proper assignment of claims
acceptable to the Government, is incorrect EFT information within the meaning of
paragraph (d) of this clause.
h.) Liability for change of EFT information by financial agent. The Government is not
liable for errors resulting from changes to EFT information made by the Contractor’s
financial agent.
i.) Payment information. The payment or disbursing office shall forward to the
Contractor available payment information that is suitable for transmission as of the
date of release of the EFT instruction to the Federal Reserve System. The
Government may request the Contractor to designate a desired format and
method(s) for delivery of payment information from a list of formats and methods the
payment office is capable of executing. However, the Government does not
guarantee that any particular format or method of delivery is available at any
particular payment office and retains the latitude to use the format and delivery
method most convenient to the Government. If the Government makes payment by
check in accordance with paragraph (a) of this clause, the Government shall mail the
payment information to the remittance address contained in the CCR database.
I.7. MENTOR PROTÉGÉ PROGRAM (3.6.1-9 OCTOBER 2006)
a.) Large and small businesses are encouraged to participate in the FAA pilot Mentor-
Protégé program for the purpose of providing developmental assistance to eligible
protégé entities to enhance their capabilities and increase their participation in FAA
contracts.
b.) The pilot program consists of:
(1) Mentor firms, which are large prime contractors or eligible small
businesses capable of providing developmental assistance;
(2) Protégé firms, which include socially and economically disadvantaged
businesses, service-disabled veteran-owned small businesses, historically
black colleges and universities, minority educational institutions, and
woman-owned small businesses; and
(3) Mentor-Protégé agreements, approved by the Contracting Officer and
the Small Business Development Office (SBO);
c.) Mentor participation in the program means providing technical, managerial, and
financing assistance to aid protégés in developing requisite high-tech expertise and
business systems to compete for and successfully perform FAA contracts and
subcontracts.
d.) Contractors interested in participating in the pilot program are encouraged to contact
the SBO, (202) 267-8881 or (202) 267-7454, for further information.
I-11
DTFAWA-09-R-00055
Amendment No. 0002
I.8. SUBSTITUTION OR ADDITION OF PERSONNEL (3.8.2-22 OCTOBER 2006)
a.) The Contractor must assign only those individuals whose resumes, personnel data,
or personnel qualification statements have been submitted and determined by the
Contracting Officer to meet the minimum requirements of the contract. The
Contractor must not substitute or add personnel except in accordance with this
clause. The list of personnel who are approved by the Contracting Officer to perform
work on this requirement and the Labor Category under which they may perform
services is set forth in Attachment J.7.
b.) Substitution of Personnel.
(1) For the term of the contract performance, the Contractor must not substitute
personnel for the individuals whose resumes or other personal qualification
were submitted with its offer and that were determined by the Contracting
Officer to be acceptable at the time of contract award, unless such
substitutions are because of an individual’s sudden illness, death, or
termination of employment. In any of these events, the Contractor must
promptly notify the Contracting Officer and propose substitute personnel as
required by paragraph d.) below.
(2) If an individual becomes, for whatever reason, unavailable for work under the
contract for a continuous period exceeding fourteen (14) working days, or is
expected to devote substantially less effort to the planned work, the
Contractor must propose a substitute personnel as required by paragraph d.)
below.
c.) Addition of Personnel. If an FAA requirement will increase the specified level of effort
for a designated labor category, but not the overall level of effort of the contract, then
the Contractor must notify the Contracting Officer to add personnel to the designated
labor category. The Contractor must request added personnel as required by
paragraph d.) below.
d.) Request and Review. The Contractor must submit the request for substitute or
added personnel in writing to the Contracting Officer at least ten (10) working days (if
a security clearance must be obtained, at least fifteen (15) working days) before the
proposed date of substitution or addition. The Contractor’s request must provide a
detailed explanation of the circumstances causing the proposed substitution or
addition, a complete resume for the proposed substitute or added personnel, and any
additional information required by the Contracting Officer. Proposed substitutes and
added personnel must have qualifications equal to or higher than those stated in the
contract for the labor category. The Contracting Officer will evaluate the Contractor’s
request and promptly notify the Contractor of the decision to accept or reject the
qualifications of the substitute or added personnel.
e.) (Paragraph Deleted)
I-12
DTFAWA-09-R-00055
Amendment No. 0002
I.9. CONTRACTOR PERSONNEL SUITABILITY REQUIREMENTS (3.14-2 JANUARY
2009)
(a) This clause applies to the extent that this contract requires contractor employees,
subcontractors, or consultants to have unescorted access to FAA:
(1) Facilities;
(2) Sensitive information; and/or;
(3) Resources regardless of the location where such access occurs, and none of the
exceptions of FAA Order 1600.72A, Contractor and Industrial Security Program,
Chapter 5, paragraphs 4, 6, 7 and 8 pertains.
Definitions of applicable terminology are contained in the corresponding guidance and
FAA Order 1600.72A, appendix A.
(b) Consistent with FAA Order 1600.72A, the FAA Servicing Security Element (SSE)
has approved designated risk levels for the positions under the contract. Those
designated risk levels are:
Program Analyst (Mid-level) TBD
TBD
Systems Engineer (Senior-level)
TBD
Systems Engineer (Mid-level)
SOA Architect (Senior-level) TBD
SOA Architect (Mid-level) TBD
SOA Architect (Jr-level) TBD
TBD
SOA Developer (Senior-level)
TBD
SOA Developer (Mid-level)
TBD
Business Analyst (Senior-level)
TBD
Business Analyst (Mid-level)
TBD
Business Analyst (Jr-level)
TBD
Business Analyst (Entry-level)
TBD
Enterprise Architect (Mid-level)
I-13
DTFAWA-09-R-00055
Amendment No. 0002
TBD
SOA Systems Analyst (Jr-level)
(c) If a National Agency Check with Inquiries (NACI) or other investigation is
required under paragraph (b) for a given position, the contractor will submit to the
Contracting Officer (CO) a point of contact (POC) that will enter applicant data
into the Vendor Applicant Process (VAP) system (vap.faa.gov). VAP is a FAA
system used to process and manage security information for FAA contractor
personnel. Each contract may have up to 5 POCs. Once designated, a VAP
administrator will provide each POC a Web ID and password.
The type of investigation conducted will be determined by the position risk level
designation for all duties, functions, and/or tasks performed and will serve as the
basis for granting a favorable employment suitability authorization as described
in FAA Order 1600.72A. If an employee has had a previous U. S. Government
conducted background investigation which meets the requirements of Chapter 5
of FAA Order 1600.72A and Homeland Security Presidential Directive 12 (HSPD-
12), it will be accepted by the FAA. However, the FAA reserves the right to
conduct further investigations, if necessary. The contract may include positions
that are temporary, seasonal, or under escort only. In such cases, a FAA Form
1600-77 for each specific position will be established as the investigative
requirements may differ from the NACI.
The following information must be entered into VAP by the POC for each
applicant requiring an investigation:
- Name;
- Date and place of birth (city and state);
- Social Security Number (SSN);
- Position and office location;
- Contract number;
- Current e-mail address and telephone number (personal or work); and
- Any known information regarding current security clearance or previous
investigations (e.g. the name of the investigating entity, type of background
investigation conducted, contract number, labor category (Position), and
approximate date the previous background investigation was completed).
If a prior investigation exists and there has not been a 2 year break in service by
the applicant, the SSE will notify the contractor that no investigation is required
and that final suitability is approved.
If no previous investigation exists, the SSE will send the applicant an e-mail (this
step may be delegated to VAP POC):
- Stating that no previous investigation exists and the applicant must complete a
form through the Electronic Questionnaires for Investigations Processing (eQIP)
system;
- Instructing the applicant how to enter and complete the eQIP form;
- Providing where to send/fax signature and release pages and other applicable
I-14
DTFAWA-09-R-00055
Amendment No. 0002
forms; and
- Providing instructions regarding fingerprinting.
The applicant must complete the eQIP form and submit other required material
within 15 days of receiving the e-mail from the SSE.
For items to be submitted outside eQIP, the contractor must submit the required
information with a transmittal letter referencing the contract number to:
Headquarters Contracts:
Manager, Personnel Security Division, AIN-400
800 Independence Avenue, S.W., Room 315
Washington, D.C. 20591
Regional and Center Contracts:
[TBD]
The transmittal letter must also include a list of all of the names of contractor
employees and their positions for which completed forms will be submitted to the
SSE pursuant to this Clause.
(d) The contractor must submit the information required by paragraph (c) of this
Clause for any new employee not listed in the Contractor's initial submission who
is hired into any position identified in paragraph (b) of this Clause.
(e) The CO will provide notice to the contractor when any contractor employee is
found to be unsuitable or otherwise objectionable, or whose conduct appears
contrary to the public interest, or inconsistent with the best interest of national
security. The contractor must take appropriate action, including the removal of
such employee from working on this FAA contract, at their own expense. Once
action has been taken, the contractor will report the action to the CO and SSE.
(f) No contractor employee will work in a high, moderate, or low risk position
unless the SSE has received all forms necessary to conduct any required
investigation and has authorized the contractor employee to begin work.
(g) The contractor must notify the CO within one (1) business day after any
employee identified pursuant to paragraph (c) of this Clause is terminated from
performance on the contract. This notification must be done utilizing the Removal
Entry Screen of VAP. If FAA issued the terminated employee and identification
card, the contractor must collect the card and submit it to the SSE.
(h) The CO may also, after coordination with the SSE and other security
specialists, require contractor employees to submit any other security information
(including additional fingerprinting) deemed reasonably necessary to protect the
interests of the FAA. In this event, the contractor must provide, or cause each of
its employees to provide, such security information to the SSE, and the same
transmittal letter requirements of paragraph (c) of this Clause applies.
(i) The contractor and/or subcontractor(s) must contact the Servicing Security
Elements (Regional and/or Center Security Divisions) or AIN-400 at
I-15
DTFAWA-09-R-00055
Amendment No. 0002
Headquarters within one (1) business day in the event an employee is arrested
(detained by law enforcement for any offenses, other than minor traffic offenses)
or is involved in theft of government property or the contractor becomes aware of
any information that may raise a question about the suitability of a contractor
employee.
(j) Failure to submit information required by this clause within the time required
may be determined by the CO a material breach of the contract.
(k) If subsequent to the effective date of this contract, the security classification
or security requirements under this contract are changed by the Government and
if the changes cause an increase or decrease in direct contract costs or
otherwise affect any other term or condition of this contract, the contract will be
subject to an equitable adjustment.
(l) The contractor agrees to insert terms that conform substantially to the
language of this clause, including paragraph (k) but excluding any reference to
the Changes clause of this contract, in all subcontracts under this contract that
involve access and where the exceptions under Chapter 5, FAA Order 1600.72A
do not apply.
(m) Contractor employees who have not undergone a background investigation
must be escorted at all times. In some instances, a contractor employee may be
required to serve as an escort. To serve as an escort, a contractor employee
must have a favorably adjudicated fingerprint check and initiated a NACI with
FAA.
I.10. GOVERNMENT-ISSUED KEYS, PERSONAL IDENTITY VERIFICATION (PIV)
CARDS, AND VEHICLE DECALS (3.14-4 JULY 2006)
a.) It may become necessary for the Government to issue keys, PIV cards, vehicle
decals, and/or access control cards to contractor employees. Prior to or upon
completion or termination of the work required hereunder, the contractor must return
all such Government-issued items to the issuing office with notification to the
Contracting Officer's Technical Representative (COTR). When contractor employees
who have been issued such items are terminated or no longer required to perform the
work, the Government-issued items must be returned to the Government within three
(3) business days or upon termination of the contract or the employee. Improper use,
possession or alteration of FAA issued keys, PIV Cards and/or vehicle decals is
subject to penalties under Title 18, USC 499, 506, and 701.
b.) In the event such keys, PIV Cards, or vehicle decals are not returned, the contractor
understands and agrees that the Government may, in addition to any other
withholding provision of the contract, withhold [CO to enter appropriate amount] for
each key PIV Card, and vehicle decal not returned. If the keys, PIV Cards, or vehicle
decals are not returned within 30 calendar days from the date the withholding action
was initiated, any amount so withheld must be forfeited by the contractor.
c.) Access to aircraft ramp/hangar areas is authorized only to those persons displaying
a flight line identification card and for vehicles, a current ramp permit issued pursuant
to Title 49, Part 1542, Code of Federal Regulations.
I-16
DTFAWA-09-R-00055
Amendment No. 0002
d.) The Government retains the right to inspect inventory, or audit PIV Cards, keys,
vehicle decals, and access control cards issued to the contractor in connection with
the contract at the convenience of the Government. Any items not accounted for, to
the satisfaction of the Government will be assumed to be lost and the provisions of
section (b) apply.
e.) Keys must be obtained from the COTR who will require the contractor to sign a
receipt for each key obtained. Lost keys, PIV Cards, vehicle decals, and access
control cards must immediately be reported concurrently to the Contracting Officer
(CO), COTR, and [CO to insert name of local security division or staff and facility
management office]. Electronic keying cards are handled in the same manner as
metal keys.
f.) Each contract employee, during all times of on-site performance at the [CO to insert
location] must prominently display his/her current and valid PIV card on the front
portion of his/her body between the neck and waist. Each PIV card holder must not
affix pins, stickers, or other decorations to the PIV.
(1) Prior to any contractor employee obtaining a PIV Card or vehicle decals, the
contract employee is required to report in person to the SSE Registrar or an
FAA designated trusted agent for fingerprinting, photographing, and to
submit their required investigation forms as described in AMS clause 3.14-2,
Contractor Personnel Suitability Requirements. The investigative forms must
be submitted to [CO to insert name and location of security division or staff]
by the contractor in a sealed envelope either hand carried by the contractor
or sent via U.S. mail to: [CO to insert mailing address]. The SSE will review
the forms and approve interim suitability prior to the contract employee
beginning work. When an interim is granted by the SSE, the individual may
begin work under escort until their OPM fingerprint check has been returned
and successfully adjudicated at such time they can then be badge. If the
contract employee requires a PIV Card, the fingerprint check must be
completed and favorably adjudicated by the SSE prior to approval or
issuance of the PIV card.
(2) To obtain the PIV Card, contractor employee must submit an identification
Card/Credential Application (DOT 1681) signed by the contractor employee
and by the authorized trusted agent (when applicable) and also by the
authorized sponsor to the CO or to the COTR. The DOT 1681 must contain,
as a minimum, under the "Credential Justification" heading, the name of the
contractor/company, the contract number or the appropriate acquisition
identification number, the expiration date of the contract or the task
(whichever is sooner), and the required signatures. The contractor will be
notified when the DOT 1681 has been approved and is ready for processing
by the [CO to insert name and location of the person who will process the
document]. Arrangements for processing the identification cards, including
photographs and lamination can be made by the contacting [CO to insert
point of contact with phone number].
(3) The contractor must contact the SSE to obtain the procedures that the
contractor's employees must utilize to obtain their PIV Card.
I-17
DTFAWA-09-R-00055
Amendment No. 0002
g.) The contractor is responsible for ensuring final out-processing is accomplished for all
departing contractor employees. Final out-processing must be accomplished by close
of business the final workday of the contractor employee or the next day under
special conditions. The SSE must be notified in writing and ensure that all FAA
medial, including the PIV card are returned to the SSE.
I.11. SENSITIVE UNCLASSIFIED INFORMATION (SUI) (3.14-5 JULY 2007)
a.) Sensitive information must be restricted to specific contractors who:
(1) Have a need "to know" to perform contract tasks;
(2) Are authorized to receive the SUI;
(3) Meet personnel suitability security requirements to access sensitive
information; and
(4) Successfully complete a Document Security Notice and SUI Request Form.
b.) The contractor must develop and implement procedures to ensure that sensitive
information is handled in accordance with FAA requirements and at a minimum, must
address:
(1) Procedures for distributing, receiving, and retaining signed Document
Security Notice and SUI Request Forms from each subsequent recipient of
the SUI (to include subcontractors, suppliers, etc.);
(2) Steps to minimize risk of access by unauthorized persons during business
and non-business hours to include storage capability;
(3) Procedures for safeguarding during electronic transmission (voice, data, fax)
mailing or hand carrying;
(4) Procedures for protecting against co-mingling of information with general
contractor data system/files;
(5) Procedures for marking documents with both the protective marking and the
distribution limitation statement as needed;
(6) Procedures for the reproduction of subject material;
(7) Procedures for reporting unauthorized access; and
(8) Procedures for the destruction and/or sanitization of such material.
c.) Federal Technical Data Solutions (FedTeDS): Except for those items noted by the
CO, SUI will be made available to Offerors through FedTeDS. FedTeDS provides a
secure environment for the distribution of SUI information to vendors.
(1) FedTeDS can be found at www.fedteds.gov.
(2) Vendors will utilize FedTeDS to download SUI information (to include plans,
specifications, equipment specifications, etc.), or the vendor will utilize the
site to download a request form to send to the CO for SUI information
unavailable in electronic formats.
(3) Before receiving access to the SUI information or forms, the Offeror is
required to certify electronically to SUI policy and standards in FedTeDS.
(4) As FedTeDS uses the Central Contractor Registration (CCR) for a portion of
the vendor authentication process, Offerors must be successfully registered
in CCR (www.ccr.gov) prior to seeking access to SUI through FedTeDS.
(5) Instructions and guides on usage of FedTeDS can be found at
www.fedteds.gov.
I-18
DTFAWA-09-R-00055
Amendment No. 0002
PART III - SECTION J
LIST OF ATTACHMENTS
J.1. ATTACHMENT DESCRIPTIONS
J.2 Contract Data Requirements List (CDRLs)
J.3 Data Item Descriptions (DIDs)
J.4 Personnel Qualifications
J.5 COTR Delegation and Alternate Delegation COTR Letters
J.6 Task Order No. 0001
J.7 Approved Contractor Personnel
J.8 Technical Lead Points of Contact List
J-1
DTFAWA-09-R-00055
Amendment No. 0002
J.2. CONTRACT DATA REQUIREMENTS LIST (CDRLS)
The Contractor must deliver the following CDRLs in accordance with the SOW and Section F.5:
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
Monthly -
Program Status Report occurrence 2
(PSR) months ARO and
General CDRLs A001 (Ref. C.3.1.1) 10th of each month N/A N/A
Monthly -
1st occurrence 7
EVM Reporting weeks ARO or 15th
A002 (Ref. C.3.1.1) of each month N/A N/A
As required or IAW
Technical Findings SWIM Network
A003 (Ref. C.3.2.3) Logic Schedule As required As required
As required or IAW
Program Briefs SWIM Network
A004 (Ref C.3.2.4) Logic Schedule As required As required
As required or IAW 4 business days
SWIM Network prior to the
A005 Agenda (Ref. C.3.2.6) Logic Schedule As required designated meeting
As required or IAW 5 business days
SWIM Network after the
A006 Minutes (Ref. C.3.2.7) Logic Schedule As required designated meeting
Requirements 1 – As required or IAW 2 weeks after ROC
Systems Engineer Technical Findings SWIM Network
Support A003 (Ref C.3.3.1) Logic Schedule As required
One time and 2 weeks after ROC
A003 annual review or
Technical Findings IAW SWIM Network
(Ref C.3.3.2) Logic Schedule 2 months ARO
Technical Findings Monthly or IAW Close of Business
(Ref C.3.3.3) SWIM Network NA Monday prior to
J-2
DTFAWA-09-R-00055
Amendment No. 0002
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
Logic Schedule second Tuesday of
A003 each month
One time and 2 weeks after ROC
annual review or
Safety Plan IAW SWIM Network
A007 (Ref C.3.3.4) Logic Schedule 1 month ARO
One time and 2 weeks after ROC
annual review or
Security Plan IAW SWIM Network
A008 (Ref C.3.3.5) Logic Schedule 1 month ARO
One time and 2 weeks after ROC
annual review or
Security Policies IAW SWIM Network
A009 (Ref C.3.3.5.1) Logic Schedule 1 month ARO
One time and 2 weeks after ROC
Configuration annual review or
Management Plan (CMP) IAW SWIM Network
A010 (Ref C.3.3.6) Logic Schedule 2 month ARO
One time and 2 weeks after ROC
Quality Assurance Plan annual review or
(QAP) IAW SWIM Network
A011 (Ref C.3.3.7) Logic Schedule 2 month ARO
System Engineering One time and
Management Plan annual review or
(SEMP) IAW SWIM Network
A012 (Ref C.3.3.8) Logic Schedule 1 month ARO 1 week after ROC
As required or IAW
Training Presentations SWIM Network
A013 (Ref C.3.3.9) Logic Schedule As required As required
One time and
A014 annual review or
Technical Comments IAW SWIM Network
(Ref C.3.3.10) Logic Schedule 1 month ARO 1 week after ROC
J-3
DTFAWA-09-R-00055
Amendment No. 0002
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
Requirement 2 –
Requirement
Architecture/ One time and
Documentation A014 Technical Comments annual review or
Development (Ref C.3.4.1, C.3.4.2.1, IAW SWIM Network
and C.3.4.10) Logic Schedule 1 month ARO 1 week after ROC
One time and
annual review or
Core Services Standards IAW SWIM Network
A015 (Ref C.3.4.2.1) Logic Schedule 1 month ARO 1 week after ROC
One time and
Architectural Element annual review or
Definitions IAW SWIM Network
A016 (Ref C.3.4.3) Logic Schedule 2 month ARO 1 week after ROC
One time and
Enterprise Architectural annual review or
Views IAW SWIM Network
A017 (Ref C.3.4.3) Logic Schedule 2 month ARO 1 week after ROC
One time and
annual review or
Registry/Repository IRD IAW SWIM Network
A018 (Ref C.3.4.4) Logic Schedule 3 month ARO 1 week after ROC
One time and
annual review or
Registry/Repository ICD IAW SWIM Network
A019 (Ref C.3.4.4) Logic Schedule 4 month ARO 1 week after ROC
XML Gateway One time and
Requirements annual review or
A020 (Ref C.3.4.5) IAW SWIM Network 3 month ARO
J-4
DTFAWA-09-R-00055
Amendment No. 0002
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
Logic Schedule
1 week after ROC
1 week after ROC
One time and
annual review or
XML Gateway IRD IAW SWIM Network
A021 (Ref C.3.4.5) Logic Schedule 4 month ARO
One time and 1 week after ROC
Policy Server annual review or
Requirements IAW SWIM Network
A022 (Ref C.3.4.6) Logic Schedule 3 month ARO
One time and 1 week after ROC
annual review or
Policy Server IRD IAW SWIM Network
A023 (Ref C.3.5.6) Logic Schedule 3 month ARO
Message Oriented One time and 1 week after ROC
Middleware (MOM) annual review or
Requirements IAW SWIM Network
A024 (Ref C.3.4.7) Logic Schedule 4 month ARO
One time and 1 week after ROC
annual review or
MOM IRD IAW SWIM Network
A025 (Ref C.3.4.7) Logic Schedule 3 month ARO
One time and 1 week after ROC
SWIM Final Program annual review or
Requirements (FPR) IAW SWIM Network
A026 (Ref C.3.4.8) Logic Schedule 1 month ARO
One time and 1 week after ROC
annual review or
SWIM FPR Appendices IAW SWIM Network
A027 (Ref C.3.4.8) Logic Schedule 1 month ARO
A028 SWIM Service One time and 1 month ARO 1 week after ROC
J-5
DTFAWA-09-R-00055
Amendment No. 0002
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
Specification Document annual review or
(SvSD) (Ref C.3.4.9) IAW SWIM Network
Logic Schedule
One time and 1 week after ROC
annual review or
FPR Segment X IAW SWIM Network
A029 (Ref C.3.4.11) Logic Schedule TBD
One time and 1 week after ROC
annual review or
SvSD Segment X IAW SWIM Network
A030 (Ref C.3.4.11) Logic Schedule TBD
One time and 1 week after ROC
annual review or
IRD Segment X IAW SWIM Network
A031 (Ref C.3.4.11) Logic Schedule TBD
Requirement 3 - One time and 1 week after ROC
Governance SWIM Governance annual review or
Policy Document IAW SWIM Network
A032 (Ref C.3.5.1) Logic Schedule 1 month ARO
One time and 1 week after ROC
annual review or
SWIM Governance Plan IAW SWIM Network
A033 (Ref C.3.5.2) Logic Schedule 1 month ARO
As required or IAW As required As required
Technical Findings SWIM Network
A003 (Ref C.3.5.3) Logic Schedule
One time and
annual review or
Technology Plan IAW SWIM Network
A034 (Ref C.3.5.4) Logic Schedule 1 month ARO 1 week after ROC
J-6
DTFAWA-09-R-00055
Amendment No. 0002
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
Requirement 4 – Technical Comments As required or IAW As required As required
Enterprise Information (Ref C.3.6.1.1, C.3.6.1.2, SWIM Network
Management C.3.6.1.3, C.3.6.1.4, and Logic Schedule
A014 C.3.6.1.5)
One time and
annual review or
EIM Plan IAW SWIM Network
A035 (Ref. C.3.6.2) Logic Schedule 1 month ARO 1 week after ROC
Decision Briefings and As required or IAW As required As required
Packages SWIM Network
A036 (C.3.6.3) Logic Schedule
One time and
Requirement 5 – SWIM annual review or
Integration Support IAW SWIM Network
A037 SIIP (Ref. C.3.7.1) Logic Schedule 1 month ARO
As required or IAW As required As required
Technical Comments SWIM Network
A014 (Ref. C.3.7.2) Logic Schedule
As required or IAW As required As required
Technical Findings SWIM Network
A003 (Ref. C.3.7.3) Logic Schedule
Requirement 6 – SIPs
Oversight Periodic Updates,
as required or IAW
PLAs SWIM Network
A038 (Ref. C.3.8.1) Logic Schedule As required As required
A013 Training Presentations Monthly and As required As required
J-7
DTFAWA-09-R-00055
Amendment No. 0002
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
(Ref. C.3.8.4) Updates, as
required or IAW
SWIM Network
Logic Schedule
Periodic Updates,
as required or IAW
SLAs/MOAs SWIM Network
A039 (Ref. C.3.8.5) Logic Schedule As required As required
Periodic Updates,
FTI Capacity as required or IAW
Documentation SWIM Network
A040 (Ref. C.3.8.6) Logic Schedule As required As required
Technical Comments
(Ref. C.3.8.8, C.3.8.9, As required or IAW As required As required
C.3.8.10, C.3.8.12, SWIM Network
C.3.8.13, C.3.8.14 and Logic Schedule
A014 C.3.8.16)
Technical Findings
(Ref. C.3.8.8, C.3.8.9, As required or IAW As required As required
C.3.8.10, C.3.8.12, SWIM Network
C.3.8.13, C.3.8.14 and Logic Schedule
A003 C.3.8.16)
As required or IAW 4 business days
SWIM Network prior to the
A005 Agenda (Ref. C.3.8.15) Logic Schedule As required designated meeting
As required or IAW 3 business days
SWIM Network after the
A006 Minutes (Ref. C3.8.15) Logic Schedule As required designated meeting
Requirement 7 – Monthly Updates,
Program Control as required or IAW
Risk Documentation SWIM Network
A041 (Ref. C.3.9.1) Logic Schedule As required As required
J-8
DTFAWA-09-R-00055
Amendment No. 0002
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
Monthly and
Updates, as
required or IAW
SWIM Network
EVM Documentation Logic Schedule
A042 (Ref. C.3.9.2) As required As required
Performance Metric As required or IAW
Documentation SWIM Network
A043 (Ref. C.3.9.3) Logic Schedule As required As required
As required or IAW
Financial Documentation SWIM Network
A044 (Ref. C.3.9.4) Logic Schedule As required As required
Investment Analysis
Documentation As required or IAW
(Ref. C.3.9.5) SWIM Network
A045 Logic Schedule As required As required
Project Planning As required or IAW
Documentation SWIM Network
A046 (Ref C.3.9.6) Logic Schedule As required As required
Requirement 8 –
Program Management Program Periodic Updates,
Support Communications as required or IAW
Documentation SWIM Network
A047 (Ref. C.3.10.1) Logic Schedule As required As required
Annual and
Updates, as
required or IAW
Communications Plan SWIM Network
A048 (Ref. C.3.10.2) Logic Schedule As required As required
Annual and
SWIM Website Plan Updates, as
A049 (Ref. C.3.10.2) required or IAW As required As required
J-9
DTFAWA-09-R-00055
Amendment No. 0002
Requirement CDRL TITLE/SOW Frequency Draft Final
No./Management No. Reference *ARO – After ROC – *Resolution
Team Lead *Receipt of Order of Comments
SWIM Network
Logic Schedule
Annual and
Updates, as
required or IAW
SWIM Outreach Plan SWIM Network
(Ref. C.3.10.2) Logic Schedule
A050 As required As required
Annual and
Updates, as
Investment Analysis required or IAW
Documentation SWIM Network
A045 (Ref. C.3.10.3) Logic Schedule As required As required
Technical Findings
(Ref. C.3.10.5) As required or IAW As required As required
SWIM Network
Logic Schedule
A003
As required or IAW As required As required
Technical Comments SWIM Network
A014 (Ref. C.3.10.5) Logic Schedule
J - 10
DTFAWA-09-R-00055
Amendment No. 0002
J.3. CONTRACT DATA ITEM DESCRIPTION
All documents delivered shall maintain the following quality criteria: completeness,
traceability, verifiability, correctness, consistency and clarity.
A001 Program Status Report. The report shall, at a minimum, contain a list of each task
worked upon, the level of completion for each task, a statement of whether you are on
schedule to complete the individual tasks contained therein, and if not , an explanation of why
you are not on schedule. It shall also contain the numbers and description of hours
expended, specific CDRL delivered. Any work problems encountered, pending issues, and
an outline of the work planned.
A002 Earned Value Management Report /WBS. SWIM WBS EVM template provided GFI.
Total work hours expended within each applicable cost account.
A003 Technical Findings. Based on technical activities, and research such as evaluations,
etc. Provide results of system engineering task in the form of technical briefings, white
papers, or reports in the level of detail necessary to facilitate technical information sharing
and decision making.
A004 Program Briefs. Two program briefs in PowerPoint: First brief detailing SWIM
baseline program earned value status to include schedule, cost, variance analysis, updated
estimate to complete, risks and issues to support a Program Management Review (PMR).
Second brief detailing the Contractor’s internal work status, technical issues, and tasks
accomplished during quarter and planned.
A005 Agenda. Submit agenda for meetings such as TIMs, PMR, etc. The agenda, at a
minimum, shall include specific topics to be discussed and requested attendees.
A006 Minutes. Capture major decisions, actions, outcomes, findings, task assignment etc
for all meetings such as TIMs, PMRs, etc.
A007 Safety Plan. The SWIM Safety Plan shall be provided GFI. The CDRL shall contain
continuous updates of the Safety Plan that outline a schedule and plan for required safety
reviews, documents and assessments, a schedule for addressing safety issues and
requirements for safety.
A008 Security Plan. The security documentation will be provided GFI. The CDRL shall
contain written comments on SWIM security documentation to include, but not limited to,
schedule, requirements and planned security reviews.
A009 Security Policies. The security policy document shall contain application security
policies for implementation of Federal standards.
A010 Configuration Management Plan. The Configuration Management (CM) Plan shall
ensure the traceability with SWIM Service Specification Documentation/Interface
Requirements Documents/Interface Control Documents requirements. The Plan should
J - 11
DTFAWA-09-R-00055
Amendment No. 0002
include the process for Change Requests and the Configuration Review board procedures
and policies.
A011 Quality Assurance Plan (QAP). Identify and report QA processes and controls,
document and report QA issues and maintain the Quality Assurance Plan that is provided as
GFI. .
A012 System Engineering Management Plan (SEMP). The CDRL shall be maintained and
technical comments generated. The SEMP will be provided as GFI.
A013 Training Presentations. Develop and present training presentation(s) on specific
architecture considerations or software products, etc., at a level that increases team
understanding and knowledge base.
A014 Technical Comments. Provided technical comments after review of all technical
documents provided by the SWIM PO and/or its stakeholders. Comments may be submitted
(as requested) using SWIM comment form (provided GFI). In other instances, comments
may be in Microsoft Word. Provide technical comments for all documents SIPs and SWIM
DAF IAW FAA approved comment form (provided GFI).
A015 Core Services Standards. Conduct technical reviews and develop SWIM engineering
artifacts for all future SWIM segments.
A016 Architectural Element Definitions. The CDRL shall provide written technical inputs,
updates, and comments to SWIM Core Service Architecture Definition, SWIM Architecture
Documents, Segment Use Cases, and architecture case studies. In some instances, a GFI
template will be provided and shall be utilized.
A017 Enterprise Architectural Views. The CDRL shall provide written technical
documentation to generate the following views: TV-1, OV-1, OV-2, OV-3, OV-4, OV-5, OV-6c,
OV-7, SV-1, SV-3, SV-4a, SV-4b, SV-5a, SV-5c, SV-6, SV-7, SV-10c, using Rational
Software Modeler tools (provided GFI) and IAW the format of DoDAF V2.
A018 Registry/Repository IRD. The CDRL shall contain an updated and revised
Registry/Repository IRD. The current Registry/Repository IRD will be provided as GFI.
A019 Registry/Repository ICD. The CDRL shall contain the description of the interfaces
between the system under development or modification and external system(s) to a level that
the ICD can serve as a configuration control document. It shall provide all mechanical,
electrical, logical, and procedural information needed to enable system implementation. The
ICDs shall be prepared IAW FAA Standard 025F.
A020 XLM Gateway Requirements. The CRL shall contain updated and revised gateway
requirements. The current version will be provided as GFI. The requirements will serve as
an overarching control document.
A021 XML Gateway IRD. The CDRL shall contain updated and revised XML gateway
requirements. The current version will be provided as GFI. The IRD shall describe the
J - 12
DTFAWA-09-R-00055
Amendment No. 0002
interfaces required between the system under development or modification and external
system(s) to a level that the IRD can serve as a configuration control document. The IRDs
shall be prepared IAW FAA Standard 025F.
A022 Policy Server IRD. The CDRL shall contain an updated and revised set of SWIM
policy server requirements. The current version will be provided as GFI. The IRD shall
describe the IRD shall describe the interfaces required between the system under
development or modification and external system(s) to a level that the IRD can serve as a
configuration control document. The IRDs shall be prepared IAW FAA Standard 025F.
A023 Policy Server Requirements. The CDRL shall contain the requirements for the SWIM
Policy Server. The Requirements should serve as an overarching control document. The
Requirements shall be prepared IAW FAA Standard 025F.
A024 Message Oriented Middleware (MOM) IRD. The CDRL shall contain interface updates
and revisions to SWIM MOM interface requirements. The current version provided GFI. The
IRD shall describe the interfaces requirements between the system under development or
modification and external system(s) to a level that the IRD can serve as a configuration
control document. The IRDs shall be prepared IAW FAA Standard 025F.
A025 Message Oriented Middleware (MOM) Requirements. The CDRL shall contain the
requirements for the SWIM MOM. The Requirements should serve as an overarching
control document. The Requirements shall be prepared IAW FAA Standard 025F.
A026 SWIM Final Program Requirements (FPR) Document. The CDRL shall contain the
final program requirements for the SMIM Program. The current version will be provided as
GFI. This document should be the control document. The requirements shall be prepared
IAW FAA Standard 025F.
A027 SWIM FPR Appendices. The CDRL should include the additional final Program
Requirements information as appendices of the FPR. The current version will be provided
as GFI. The appendices shall be prepared IAW FAA Standard 025F.
A028 SWIM Service Specification Document. The CDRL defines and should contain all
SWIM service capability requirements and high-level interface requirements. The document
should detail all SWIM system specification documents provided by the SIPs for the nine
capabilities. The current version will be provided as GFI. Respond to and capture comments
generated after SWIM SvSD reviews.
A029 Segment X FPR. The CDRL shall define exact operational concept and requirements
to be achieved. Respond to and capture comments generated after FPR Appendices’
reviews.
A030 Segment X SvSD. The SvSD shall define logical service requirements addressing
functional and performance needs for implementation that are derived from analysis based
on text use cases and NAS EAF artifacts.
J - 13
DTFAWA-09-R-00055
Amendment No. 0002
A031 Segment X IRD (SWIM Services). The CDRL shall capture all comments after review;
describe the interfaces required between the system under development or modification and
external system(s) to a level that the IRD can serve as a configuration control document IAW
FAA standard O25F.
A032 SWIM Governance Policy Document. The CDRL shall contain policy, processes and
procedures, service infrastructure architecture, and roles and responsibilities of the PMO and
SWIM governing bodies. This document shall serve as a control document.
A033 SWIM Governance Plan. The plan shall contain governance, descriptions, roles,
responsibilities, strategies, technical assessments, recommendations and implementation,
etc. The current version will be provided as GFI.
A034 Technology Plan. The plan shall contain SOA Enabling Technology solutions for Web
services, descriptions and procedures which include SOA reference architecture model,
network drawing depicting the topology of the SOA solution, EA IT architecture
documentation and IT architecture gaps IAW the architecture strategy.
A035 EIM Plan. The plan shall include improvements and recommendations suggested
from the review of the SWIM Taxonomy, OV-7 Logical Data model, Data Descriptions, SV-11
Physical Schema and XLM Schema(s).
A036 Decision Briefings and Packages. The briefs shall contain technical decision and/or
information resulting from proposed governance policy standards, processes and/or
procedures.
A037 SWIM Infrastructure Implementation Plan (SIIP). The plan shall contain SWIM
infrastructure information, proposed system management approach for the SWIM
architecture, and governance rules to Service-Level Agreement (SLAs). The plan shall
contain a qualified list of SWIM infrastructure standards, integration middleware and
administration, security and monitoring tool vendors.
A038 Program Level Agreements (PLAs). The PLA’s identify the tasks and activities that the
SIPS need to perform in order to satisfy SWIM PMO requirements. The agreements shall
contain technical input and include the tasks and activities required of each SIP. Prior PLAs
may be provided as GFI for format purposes.
A039 Service Level Agreements/Memorandums of Agreements. These agreements shall
contain the levels of service, priorities of each consumer, responsibilities of parties,
guarantees and will address areas such as levels of availability, service ability, performance
operation or other attributes.
A040 FTI Capacity Documentation. This Documentation shall contain the
telecommunications infrastructure service level and the associated cost to implement the
SIP’s initiative(s). The FTI capacity documentation should be IAW the Implementation Plan
(Implementation Plan provided as GFI).
J - 14
DTFAWA-09-R-00055
Amendment No. 0002
A041 Risk Documentation. Risk Documentation includes coordination of risk plans and risk
reports. Risk planning, evaluation and mitigation IAW the SWIM Risk Management Plan
(RMP) (Risk Management Plan provided as GFI). Maintaining Risk Database, meeting
results, tracking of monthly risk metrics and updating the RMP and risk section of the SEMP.
A042 EVM Documentation. EVM documentation shall include EVM reports, program WBS,
data dictionary, RAM, training and change control logs. Maintain inputs to PMRs, IBRs, OMB
Exhibit 300 and RPDs. The CDRL shall document all EVM decisions, outcomes and activities
etc.
A043 Performance Metric Documentation. The CDRL shall provide to the SWIM PO
documentation and maintaining of the performance metrics database IAW Measurement and
Analysis Plan, OMB guidance, and or otherwise directed. Documentation shall capture the
decisions, actions, outcomes, findings, tasks, assignments, etc.
A044 Financial Documentation. The CDRL shall assist the SWIM PO with financial
management tasks IAW FAA systems (i.e. Delphi, PRISM, and FMS) by developing and
providing updates to the current spend plan (provided GFI). Documentation shall capture the
decisions, actions, outcomes, findings, tasks, assignments, etc.
A045 Investment Analysis Documentation. The CDRL shall contain analysis documentation
that details and supports high quality substantiated cost and benefits estimates for BOE,
methodologies, time-phased dollars; analysis of various technical and acquisition
alternatives, to include but not limited to, cost-benefits, risk, technical performance and
human factors, etc; affordability; OMB Exhibit 300 development and BCAR, etc.
Documentation shall capture the decisions, actions, outcomes, findings, tasks, assignments,
etc.
A046 Project Planning Documentation. The documentation shall include items such as a
NLS for all SWIM segments that captures milestones, events, activity changes to program
schedule; reports the progress on implementation; includes supplemental information such as
activity dictionary, cost loading, resource loading, etc; and an updated change log report after
the approval of the baseline change request. Documentation shall capture the decisions,
actions, outcomes, findings, tasks, assignments, etc.
A047 Program Communications. Assist the SWIM PO in the development and presentation
of program communications documentation for the SWIM newsletter, OMB 300 exhibits and
GAO briefings, Congressional inquiries, SWIM program and KSN websites, white papers,
and requests from other governmental bodies, stakeholders, other entities, and responses to
requests from media. Documentation shall capture the decisions, actions, outcomes,
findings, statuses, issues, tasks, etc. Documentation shall contain formal and informal
briefings, reports, white papers, etc. in the level of detail necessary to effectively
communicate information sharing and to increase the understanding and knowledge base.
A048 Communications Plan. The SWIM Communications Plan shall be provided as GFI.
Continuous updates and revisions shall be made to the Communications Plan as required.
These updates shall include processes, policies, procedures, guidelines, descriptions, roles,
J - 15
DTFAWA-09-R-00055
Amendment No. 0002
responsibilities, strategies, implementation, and recommendations for actual and perceived
gaps that address communication strengths, weaknesses, breakdowns, vulnerabilities, etc.
A049 Website Plan. The SWIM Website Plan shall be provided GFI. Continuous updates
and revisions shall be made to the Website Plan as required. These updates shall include
processes, policies, procedures, guidelines, descriptions, roles, responsibilities, strategies,
implementation, and recommendations for actual and perceived gaps which address
strengths, weaknesses, etc.
A050 Outreach Plan. The SWIM Plan shall be provided as GFI. Continuous updates and
revisions shall be made to the Outreach Plan as required. These updates shall include
processes, policies, procedures, guidelines, descriptions, roles, responsibilities, strategies,
implementation, and recommendations for actual and perceived gaps which address
outreach strengths, weaknesses, etc.
J - 16
DTFAWA-09-R-00055
Amendment No. 0002
J.4. PERSONNEL QUALIFICATIONS
The table below represents a general selection of labor categories, functional responsibilities, and minimum
qualifications are depicted and reflective of what is being currently considered and will be finalized in the
individual task orders: Note: RELEVANT EXPERIENCE is representative not all inclusive for each
labor category.
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
Program A Bachelor Minimum Qualification: 6 years Provide and manage content for
Analyst degree in experience required program communications in the areas
Business or of requests for program information
(Mid-level)
other related In analyzing complex business or from Congress, OMB, GAO, JPDO, The
degree. programmatic problems for resolution Department of Transportation’s Office
using systematic methodologies. of the Inspector General (OIG), AJW
Or management, other ATO service units,
and industry; SWIM program website
A minimum of (www.swim.gov) and Knowledge-
10 years of Service Network (KSN) site; and, SWIM
experience program newsletter.
without degree Update and maintain the SWIM
program plans to include the
Communications Plan, Website Plan,
and Outreach Plan. Review and provide
inputs to OMB-300, Resource Planning
Data (RPD) documents, executive-level
briefings for the Joint Resource Council
(JRC), and Executive Council (EC).
Accompany and participate with FAA
SWIM program office personnel at
related conferences and meetings.
Support SWIM acquisition analyses for
Segments X.
Systems A Master of Minimum Qualification: 15 years IT The System Engineer (SE) resolves
Engineer Science degree experience with basic technical engineering development problems by
in Engineering, certifications. the application of (a) the physical and
(Senior-
Business, engineering sciences and mathematics,
level) Experience with software
Computer (b) system development and
programming language C++ and
Science, or integration, and (c) the principal
JAVA.
other related techniques and practices of
degree. Experience with enterprise OS: UNIX, engineering. Work pertains primarily to
Linux and AIX. assessing and demonstrating the
Demonstrated experience with effectiveness of new concepts and
Or
Middleware technologies and systems
ideas for equipment in achieving
J - 17
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
A minimum of such as Java Messaging Service particular mission goals; formulating
21 years of (JMS), Active MQ and IBM Message overall design concepts and criteria,
experience Queuing (MQ). which establish the baseline for
without a advancement of state-of-the-art
degree. Experience with enterprise application engineering developments; and, review,
platforms: .NET and Java 2 Platform monitor, implement, deploy and assess
Enterprise Edition (J2EE). overall progress in the development
effort.
Experience with SOA products [i.e.,
IBM Websphere, Oracle Application
The SE shall develop, manage, and
Server, Weblogic and Fusion
support trade studies and prototype
Middleware and Fuse (Enterprise
development plans and procedures for
Service Bus, Services Framework,
associated products.
Message Broker and Mediation
Router), Registry/Repository, ESM,
Policy Server].
Experience with SOA platforms,
standards, and products such as:
Universal Description Discover
Integration (UDDI), and eBXML, Data
Representation Technology: XML and
XML schema design.
Experience and knowledge of one or
more of the following FAA domains or
systems: Aeronautical Information
Management (AIM), Weather, Traffic
Flow Management, Surveillance, En
Route, and Terminal.
Ability to supervise and direct the work
of lower level personnel.
Experience in Web Service (WS) and
other information standards and
technologies including WS-RM, WS-
Security, WS-Addressing, and WS-
Notification.
Experience with the enterprise
management and core services
development such as Interface
Management, Messaging, Security,
and Enterprise Service Management.
Experienced in information standards
and technologies.
Experience with OMB-required
architecture views,
J - 18
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
DoDAF and Unified Modeling
Language (UML) experience.
Experience with Rational Unified
Process System Engineering (RUP
SE) with the DoDAF Modeling
Framework.
Experience with NAS automation
architecture and systems integration.
Experience writing technical
specifications and other technical
documents.
Experience conducting trade studies
and knowledge of the FAA System
Engineering Manual (SEM) processes
to conduct a trade study.
Knowledge and experience with
prototyping and the prototyping
process.
Experience with WS and other
information standards and
technologies including WS-Risk
Management (RM), WS-Security, WS-
Addressing, and WS-Notification.
Experience with SOA security: XML
Gateway, Lightweight Directory
Access Protocol (LDAP), Security
Assertion Markup Language (SAML),
etc.
Systems A Bachelor of Minimum Qualification: 7 years IT The System Engineer (SE) supports the
Engineer Science degree experience with basic technical resolution of engineering development
in Engineering, certifications. problems by the application of (a) the
(Mid-level)
Business, physical and engineering sciences and
Experience with software
Computer mathematics, (b) system development
programming language C++ and
Science, or and integration, and (c) the principal
JAVA.
other related techniques and practices of
degree. Experience with enterprise OS: UNIX, engineering. Work pertains primarily to
Linux and AIX. assessing and demonstrating the
Or Demonstrated experience with effectiveness of new concepts and
middleware technologies and systems ideas for equipment in achieving
A minimum of such as Java Messaging Service particular mission goals; formulating
11 years of (JMS), Active MQ and IBM Message overall design concepts and criteria,
experience Queuing (MQ). which establish the baseline for
without a Experience with enterprise application advancement of state-of-the-art
degree. platforms: .NET and J2EE. engineering developments; and, review,
monitor, implement, deploy and assess
J - 19
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
overall progress in the development
Working knowledge of SOA products
effort.
[i.e., IBM Websphere, Oracle
Application Server, Weblogic and
The SE shall support the development
Fusion Middleware and Fuse
and management of trade studies, and
(Enterprise Service Bus, Services
support prototype development plans
Framework, Message Broker and
and procedures for associated
Mediation Router),
products.
Registry/Repository, ESM, Policy
Server].
Knowledge of SOA platforms and
standards: Universal Description
Discover Integration (UDDI), and
eBXML, Data Representation
Technology: XML and XML schema
design.
Experience and knowledge of one or
more of the following FAA domains or
systems: Aeronautical Information
Management (AIM), Weather, Traffic
Flow Management, Surveillance, En
Route, and Terminal.
Working knowledge of web service
and other information standards and
technologies including WS-RM, WS-
Security, WS-Addressing, and WS-
Notification.
Working knowledge of the enterprise
management and core services
development such as Interface
Management, Messaging, Security,
and Enterprise Service Management.
Knowledge of information standards
and technologies.
Knowledge of OMB-required
architecture views
DoDAF and Unified Modeling
Language (UML) experience.
Experience with Rational Unified
Process System Engineering (RUP
SE) with the DoDAF Modeling
Framework.
Knowledge of NAS automation
architecture and systems integration.
J - 20
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
Experience writing technical
specifications and other technical
documents.
Experience conducting trade studies
and knowledge of the FAA System
Engineering Manual (SEM) processes
to conduct a trade study.
Knowledge and experience with
prototyping and the prototyping
process.
Knowledge of Web service (WS) and
other information standards and
technologies including WS-Risk
Management (RM), WS-Security, WS-
Addressing, and WS-Notification.
Working knowledge of SOA security:
XML Gateway, Lightweight Directory
Access Protocol (LDAP), Security
Assertion Markup Language (SAML),
etc.
SOA A Master of Minimum Qualification: 10 years of IT The SOA Architect shall be responsible
Architect Science degree experience required for analyzing, designing, and
in Software implementing SOA architectural
(Senior-
Engineering, Ability to supervise and direct the work requirements into service-based
level)
Computer of lower level personnel. solutions. The SOA Architect will work
Science, or within various IT environments,
other related Must be well versed in Enterprise including client/server and N-tier
degree. Architecture, SOA, J2EE, and/or Net architectures, and modify those
Full Cycle implementation experience systems to accommodate a service-
Or including requirements, design, based approach.
implementation, and integration and
A minimum of testing. The SOA Architect shall also be
14 years of responsible for identifying SOA based
experience Experience and working knowledge non-functional system requirements
without a with SOA platforms and standards: such as security, transactional integrity,
degree. Universal Description Discover reliability, availability, and agility.
Integration (UDDI) and electronic
business (exam). This individual will work with IT and
business organizations to facilitate
Must be well versed and have detailed organizational commitment for all
working experience and knowledge of systems and software plans, as well as
SOA products, such as IBM evaluate and select all technologies
Websphere, Oracle Application required in completing those plans. In
J - 21
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
Server, Weblogic and Fusion addition, the SOA Architect must
Middleware and Fuse (Enterprise provide technical leadership in a
Service Bus, Services Framework, consultative capacity across the client
Message Broker and Mediation organization—from strategic decision
Router), Registry/Repository, ESM, making down to the project planning
Policy Server. level.
Experienced with messaging systems.
Ability to present professionally and
persuasively to C-level executives.
Excellent communication skills both
written and verbal.
Experienced with Web service and
other information standards and
technologies including WS-Risk
Management (RM), WS-Security, WS-
Addressing, and WS-Notification.
SOA A Bachelor of Minimum Qualification: 7 years IT The SOA Architect shall be responsible
Architect Science degree experience required for reviewing SOA architectural
in Engineering, requirements. The SOA Architect will
(Mid-level)
Business, Must be knowledgeable in Enterprise work within various IT environments,
Computer Architecture, SOA, J2EE, and/or Net including client/server and N-tier
Science, or Full Cycle implementation experience architectures, and modify those
other related including requirements, design, systems to accommodate a service-
degree. implementation, and integration and based approach.
testing.
Or The SOA Architect shall provide
Knowledgeable of SOA products [i.e., support in identifying SOA based non-
A minimum of IBM Websphere, Oracle Application functional system requirements such as
11 years of Server, Weblogic and Fusion security, transactional integrity,
experience Middleware and Fuse (Enterprise reliability, availability, and agility.
without a degree Service Bus, Services Framework,
Message Broker and Mediation This individual will work with IT and
Router), Registry/Repository, ESM, business organizations to facilitate
Policy Server]. organizational commitment for all
systems and software plans, as well as
Knowledgeable in distributed evaluate and select all technologies
computing background. required in completing those plans.
Communication, analytical, and
problem solving skills.
Implementation familiarity including
J - 22
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
requirements, design, implementation
integration, and testing.
Knowledge with messaging systems.
Knowledge of Web service and other
information standards and
technologies including WS-Risk
Management (RM), WS-Security, WS-
Addressing, and WS-Notification.
SOA A Bachelor of Minimum Qualification: 3 years IT The SOA Architect shall be responsible
Architect Science degree experience required for supporting higher-level architects
in Engineering, with SOA architectural requirements.
(Junior-
Business, Familiarity with SOA products [i.e., The SOA Architect will support work
level)
Computer IBM Websphere, Oracle Application within various IT environments,
Science, or Server, Weblogic and Fusion including client/server and N-tier
other related Middleware and Fuse (Enterprise architectures, and support modification
degree. Service Bus, Services Framework, of those systems to accommodate a
Message Broker and Mediation service-based approach.
Or Router), Registry/Repository, ESM,
Policy Server]. This individual will provide support of IT
A minimum of 7 and business organizations to facilitate
years of Familiarity with SOA platforms and organizational commitment for all
experience standards: Universal Description systems and software plans, as well as
without a Discover Integration (UDDI), and support all technologies requirements in
degree. eBXML. completing those plans.
Competence with enterprise
architecture, SOA, J2EE, and/or Net
Full Cycle implementation.
Competence in the computing
background.
Competence with messaging systems.
Knowledge of Web service and other
information standards and
technologies including WS-Risk
Management (RM), WS-Security, WS-
Addressing, and WS-Notification.
Minimum Qualification: 15 years IT
SOA A Master of experience required. The SOA Developer’s role shall be to
Developer Science degree define, develop, test, analyze, and
Experience with a variety of relevant
in Computer maintain new software and service
(Senior- standards, practices, and procedures.
Science, applications in support of achieving
level) Relies on extensive experience and
J - 23
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
Software judgment to plan and accomplish SOA requirements. This will include
Engineering, or goals. writing, coding, testing, and analyzing
other related software programs, services and
Experience in the field of software
degree. applications. The SOA Developer will
development, including requirements-
also research, design, document, and
Or gathering, design, development,
modify software specifications
integration, and data migration.
throughout the production life cycle.
A minimum of
Leads and direct the work of others.
19 years of
Must exhibit fluency in first generation The Contractor shall use Government
experience
provided configuration management
without a degree web services standards, technologies,
and tools. tools (Rational Requisite Pro and
Rational Clear Quest) and processes to
Knowledge of Web service and other identify and capture all requirements
information standards and changes and assure that documented
technologies including WS-Risk requirements changes satisfy quality
Management (RM), WS-Security, WS- criteria including completeness,
Addressing, and WS-Notification. traceability, verifiability, correctness,
consistency and clarity.
Working knowledge of SOA products,
such as IBM Websphere, Oracle
Application Server, Weblogic and
Fusion Middleware and Fuse
(Enterprise Service Bus, Services
Framework, Message Broker and
Mediation Router),
Registry/Repository, ESM, Policy
Server.
SOA A Bachelor of Minimum Qualification: 7 years IT The SOA Developer will support senior
Developer Science degree experience required level to define, develop, test, analyze,
in Engineering, and maintain new software and service
(Mid-level) Knowledgeable with a variety of
Business, applications in support of achieving
relevant standards, practices, and
Computer SOA requirements. This will include
procedures.
Science, or support with writing, coding, testing,
other related and analyzing software programs,
Relies on extensive experience and
degree. services and applications. The SOA
judgment to plan and accomplish
Developer will provide support in
Or goals.
research and review design, document,
and software specifications throughout
A minimum of Knowledgeable in first generation web
the production life cycle.
11 years of services standards, technologies, and
experience tools including XML, SOAP, WSDL,
without a UDDI and BPEL.
degree.
Knowledgeable in the field of software
development.
J - 24
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
Business A Master degree Minimum Qualification: 15 years The Business Analyst shall be capable
Analyst in Business or experience required of assuming full responsibility to advise
other related on and perform cost estimating, cost
(Senior- Leads and direct the work of others.
degree. analysis, budgeting, scheduling,
level)
Experience in performance performance measurement, EVM,
Or
measurement, problem solving, and/or cost research. Possesses an in-
organizational/program assessment depth knowledge of the techniques,
A minimum of
and analysis, and preparing draft and uses and content of cost analysis, to
19 years of
final reports for dissemination. accomplish the most complex of
experience
estimating or research efforts.
without a degree
Experience in finance, budgeting, Experience in cost & financial
accounting, business, or business management, business practices,
management. technical, cost and schedule, and
business re-engineering issues. This
Prior FAA experience desired. encompasses a basic knowledge of
statistical techniques, scheduling,
Proficient in Microsoft Excel. network analysis, applied mathematics,
economics, and the engineering
disciplines. Defend/solve cost/risk
issues, collect and perform analysis of
cost and technical data.
Business A Bachelor Minimum Qualification: 7 years The Business Analyst shall advise on
Analyst degree in experience required and perform cost estimating, cost
Business or analysis, budgeting, scheduling,
(Mid-level)
other related Knowledgeable in performance performance measurement, EVM,
degree. measurement, problem solving, and/or cost research. Possesses an in-
organizational/program depth knowledge of the techniques,
Or
assessment, analysis, benchmarking, uses and content of cost analysis to
and preparing draft and final reports accomplish the most complex of
A minimum of
for dissemination. estimating or research efforts.
11 years of
Experience in cost & financial
experience Knowledgeable in finance, budgeting,
management, business practices,
without a degree accounting, business, or business
technical, cost and schedule, and
management.
business re-engineering issues. This
Prior FAA experience desired. encompasses a basic knowledge of
Proficient in Microsoft Excel. statistical techniques, scheduling,
network analysis, applied mathematics,
economics, and the engineering
disciplines. Defend/solve cost/risk
issues, collect and perform analysis of
cost and technical data.
Business A Bachelor Minimum Qualification: 3 years The Business Analyst shall advise on
Analyst degree in experience required and perform cost estimating, cost
J - 25
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
Business or analysis, budgeting, scheduling,
(Junior-
other related Competence in finance, budgeting, performance measurement, EVM,
level)
degree. accounting, business, or business and/or cost research. Possesses an in-
management. depth knowledge of the techniques,
Or uses and content of cost analysis to
Prior FAA experience desired. accomplish the most complex of
A minimum of 7 estimating or research efforts.
years of Working knowledge of Microsoft Experience in cost & financial
experience Excel. management, business practices,
without a technical, cost and schedule, and
degree. business re-engineering issues. This
encompasses a basic knowledge of
statistical techniques, scheduling,
network analysis, applied mathematics,
economics, and the engineering
disciplines. Defend/solve cost/risk
issues, collect and perform analysis of
cost and technical data.
Business An Associate Minimum Qualification: Entry level with The Business Analyst provides financial
Analyst Degree in at least 1 year of experience. baseline management support. Support
Business or on financial status for obligations,
(Entry-level)
other related Communication, analytical, and commitments, and expenditures, and
degree. problem solving skills. report to the program control lead.
Or
Support with financial, contractual, and
procurement reports.
A minimum of 2
years of
experience
without a
degree.
Enterprise A Bachelor of Minimum Qualification: 7 years IT The Enterprise Architect conceives
Architect Science degree experience required. designs, provides functional guidance,
in Engineering, technical support, and oversees the
(Mid-Level)
Business, Knowledge and experience with implementation of a company’s systems
Computer enterprise application platforms: .NET development. An Enterprise Architect is
Science, or and J2EE. responsible for designing IT architect
other related for an organization on an enterprise
degree. Formal training in best practice level. They define system and
process business process modeling application architect, provide vision,
Or
and/or Enterprise Resource Planning anticipate problems, and bring
A minimum of (ERP) systems. experience in solving processes and IT
15 years of related issues to an organization.
experience Ability to interface effectively with Produces best practice business
without a client technical and management models.
degree. personnel.
J - 26
DTFAWA-09-R-00055
Amendment No. 0002
Labor Minimum Relevant Experience Functional Responsibility
Categories Education
Requirements
or Experience
Strong oral and written
communications skills.
SOA A Bachelor of Minimum Qualification: 3 years IT The SOA Analyst’s role is to devise and
Systems Science degree experience required. design business process requirements
Analyst in Engineering, for all IT-related business, financial, and
Business, Familiarity with: operations systems critical to core
(Junior-
Computer Service definition, design, or organizational functions. This includes
level)
Science, or implementation using WSDL and/or researching and analyzing data in
other related SOAP Implementing Business support of business and agency
degree. Process Orchestration using BPEL or functions, process knowledge and
an equivalent. systems requirements. The individual is
Or Communication, analytical, and also responsible for proactively
problem solving skills generating and compiling reports based
A minimum of 7 on his or her findings, complete with
years of Knowledge of SOA products, recommended improvements to or new
experience platforms and standards. requirements for business processes
without a and operational procedures. This
degree. individual will apply communication,
analytical, and problem-solving skills to
help maximize the benefit of IT system
investments and to assist in
implementing new computer systems.
Driving and reviewing technology
diagnosis and assessment activities.
Identifying opportunities for technology-
related improvement based on
benchmark data and doing high-level
cost benefit analysis. Support the
development of a high-level design,
which supports robust technology
solutions—taking into account the
user’s requirements and technology.
Review design components. Support in
the development design and transition
approaches. Driving technology to
build, test, and deployment activities.
Troubleshooting, diagnosing, and
supporting application development.
J - 27
DTFAWA-09-R-00055
Amendment No. 0002
J.5. COTR DELEGATION
Federal Aviation
Administration
Memorandum
Date: September 4, 2009
To: Rhonda Thomas
Federal Aviation Administration
From: Dennis L. Scanlon, Contract Specialist, AJA-47
Subject: Delegation of authority to act as COTR under
Contract No. DTFAWA-09-C-000xx
You are hereby delegated authority to act as the Contracting Officer’s Technical
Representative (COTR) for the above referenced contract. A copy of the contract is
attached. As such, your duties are to assist the Contracting Officer in the administration
of the contract through performance and closeout. This delegation may be changed only
by the Contracting officer in writing. As the COTR, you shall represent the Contracting
Officer within the scope of the following authority, responsibilities, and limitations:
AUTHORITY:
As COTR, you have the authority to:
1. Perform surveillance of the contract work and conduct inspections that are necessary
to assure compliance with the contract terms and conditions. Resolve day-to-day
matters within the scope of your authority.
2. Make recommendations to the Contracting Officer when it appears that there is a
need for a change in scope or terms of contract in the event the contractor has
submitted a request for waiver to address non-conformances, Engineering Change
Proposals (ECPs) or Value Engineering Change Proposals (VECPs).
3. Perform, or cause to be performed, inspection(s) necessary for the acceptance of
deliverables (including contract line item numbers (CLINs) and Contract Data
Requirements Lists (CDRLs)) as stated in the contract and to require the contractor to
correct any deficiencies. Periodically, on-site surveillance visits may be required.
4. Assist the contractor in interpreting the contract specifications or technical
requirements provided that any interpretation or clarification that the COTR provides is
within the limitations prescribed later in this delegation.
J - 28
DTFAWA-09-R-00055
Amendment No. 0002
5. Certify invoices to the Contracting Officer for payment. Evaluates progress payment
requests based on costs incurred and actual work accomplished.
6. Obtain and maintain a listing of employees who will be working at the site. The list is
to be kept current by assuring that new employees are added and employees who are
terminated are deleted from the list. This is important to the security of the facility and
your list may be used as a basis for background checks by the security office in the
relevant location. A copy of this list shall be provided to the security office at least
quarterly, and at any time, a contractor employee is added or deleted from the list.
RESPONSIBILITIES:
As COTR, you have the responsibility to:
1. Be familiar with and understand contract requirements (SOW, specification, CLINs
and work-break-down structure and implications of contractor performance in relation to
the contract requirements.
2. Attend adequate initial COTR training within two months of appointment and obtain
adequate refresher training annually.
3. Establish a technical performance review program for evaluation of the contractor’s
work.
4. Coordinate with Contracting Officer whether support contractors have signed
nondisclosure forms and liaison agreement.
5. Review the Contractor’s performance of the technical requirements of the contract in
accordance with the contract terms, funding, conditions, and specifications. Notify the
Contracting Officer, in writing, of any indication that the terms of the contract are not
being met.
6. Monitor the contractor’s compliance with safety and security requirements. Ensure
contractor's performance of requirements is in agreement with provisions contained in
security clauses 3.14-1 through 5, which are prescribed for use with all FAA contracts.
7. Report any observed fraud, waste, or inefficiencies to the Contracting Officer.
8. Maintain liaison and direct communications with the Contractor and the Contracting
Officer. Meet with the Contractor or his designated representative at the beginning of
the contract to discuss working methods and scheduling and as otherwise needed.
Also, serve as the contact through which the contractor can relay questions and
problems of a technical nature to the Contracting Officer.
9. Draft technical portions of Contracting Officer letters to the contractor.
10. Ensure appropriate confidentiality of contractor submissions bearing proprietary
markings.
11. Review and evaluate the technical aspects of contractor proposals and furnish
evaluation comments and recommendations to the Contracting Officer.
12. Assist the Contracting Officer in negotiating supplemental agreements.
13. Advise the Contracting Officer on contractual matters of a technical nature.
14. Recommend needed change orders to the Contracting Officer when in the best
interest of the Government.
15. Inform the Contracting Officer as to the status and progress of performance under
the contract.
16. Alert the Contracting Officer to any potential or existing problems.
J - 29
DTFAWA-09-R-00055
Amendment No. 0002
17. Submit reports the Contracting Officer requires to perform his/her duties.
18. Provide the Contracting Officer a copy of all technical correspondence with the
contractor.
19. In the absence of need for or presence of Quality Reliability Officer (QRO), inspect
contract deliverables for conformance to the contract specifications and accept or reject
them.
20. Furnish the Contracting Officer requests for waivers (whether generated by
Government or contractor personnel) along with supporting paperwork.
21. Furnish copies of written communication between you and the contractor to the
Contracting Officer.
22. Furnish information on contractor performance as input to the past performance
data base or as otherwise requested by the Contracting Officer.
23. Report any discrepancies in payment vouchers to the Contracting Officer. Provide
documentation to support the representation.
24. Maintain a file of all correspondence (or data) initiated or received by you in
connection with subject contract.
25. Maintain an arms-length relationship with the contractor.
26. Practice claims avoidance, halting unspecified accelerated production and/or
directions of other Government employees.
27. Review all contractor-furnished reports.
28. Conduct business with industry in a manner that is above reproach.
29. Date stamp the receipt time of all vouchers or invoices.
30. Evaluate progress payment requests against the contractor’s efforts including
schedule, quality, performance, and the general progress of the acquisition.
31. Return improper vouchers or invoices to the Contractor within 7 days of receipt.
32. Seek guidance from the Contracting Officer for specific situations not covered in this
delegation.
33. Assist in the analyses of engineering change proposals (ECPs) and value
engineering change proposals (VECPs), validating and calculating estimated savings
and the contractor’s share for VECPs.
34. Ensure administration of government furnished property.
a. Advise the Contracting Officer to delegate a Property Administrator to administer
government property contract requirements.
b. Notify Property Administrator of scheduled pre-award and post-award meetings.
c. Provide the Contracting Officer with a listing of government furnished property
(including quantity and value) for inclusion into contract.
d. Notify the Property Administrator of scheduled program reviews.
e. Prepare documentation to track the movement and accountability of government
furnished property which shall include the following information:
(1) Technical Officer signature.
(2) Contracting Officer signature.
(3) Points of contacts with phone numbers for the Consignee and Consignor location.
(4) Line item property description, acquisition date, serial number, model/type, quantity,
unit cost and total cost.
(5) Transportation service requirements (when applicable):
(a) Recommended shipment method.
J - 30
DTFAWA-09-R-00055
Amendment No. 0002
(b) Weights and dimensions.
(c) Special shipping/delivery instructions (when applicable).
(d) Accounting classification for transportation costs.
f. Provide the Property Administrator with the completed document for processing.
g. Provide the Property Administrator with invoice to authorize the acquisition of contract
acquired property (this refers to non-expendable property only).
(1) Invoices shall include vendor and contractor name, address, phone number, and
point of contact.
(2) Invoices shall include line item property description, acquisition date, serial number,
model/type, quantity, unit cost and total cost.
h. Notify the Property Administrator of administrative changes to the contractor (i.e.
Company name, address, point of contact, etc.).
i. Assist the Property Administrator with the disposal of excess government furnished
property and/or contractor acquired property as required.
(1) Screen excess government furnished property and/or contractor acquired property
for potential internal program office use.
(a) Prepare documentation to transfer excess government furnished property and/or
contractor acquired property to internal programs.
(b) Prepare documentation to return government furnished property to program office.
(2) Notify the Property Administrator if there is no-use for excess government furnished
property and/or contractor acquired property.
j. Initiate the Report of Survey for Lost, Damage, and Destroyed (LDD) government
furnished property and/or contractor acquired property as required.
(1) Assist the Property Administrator with the valuation of lost, damaged and destroyed
government furnished property and/or contractor acquired property.
(2) Advise the Property Administrator of recommendations for contractor liability for
accountable lost, damaged and destroyed government furnished property and/or
contractor acquired property.
(3) Provide replacement government property for lost, damaged or destroyed
government furnished property or contractor acquired property.
(a) Prepare documentation for the issuing of government furnished property.
(b) Advise the Contracting Officer to authorize the acquisition of contractor-acquired
property.
k. Advise the Property Administrator on property related matters of a technical nature.
l. Alert the Property Administrator to any potential or existing property issues.
m. Notify the Property Administrator of contract termination/cancellation.
35. Report through normal administrative channels to the DOT Inspector General (IG)
and to the CO any evidence of prime or subcontractor kickback, attempt to bribe, or
other fraudulent behavior.
LIMITATIONS:
As COTR, you shall not:
1. Make or give the appearance of being able to make contractual commitments outside
the scope of the contract or execute or agree to modifications or take actions that would
J - 31
DTFAWA-09-R-00055
Amendment No. 0002
commit the Government to a change in contract price, quality, quantity, or delivery
schedule.
2. Sign any changes or modifications to contracts and/or delivery order(s).
3. Make determinations regarding issues of contractor liability that may arise during
contract performance. Such issues should be referred to the Contracting Officer.
4. Take part in a labor controversy or dispute involving the contractor or its employees.
5. Direct the contractor on how to perform the work.
6. Issue stop-work orders.
7. Supervise contractor employees implicitly or explicitly which could constitute personal
services.
8. Engage in conduct prejudicial to the Government.
9. Use public office for gain.
10. Impede Government efficiency or economy.
11. Lose independence or impartiality.
12. Make a Government decision outside official channels.
13. Affect adversely the public’s confidence in the Government.
The duties and responsibilities set forth herein are not intended to be all-inclusive. As
COTR, you are required to consult with the Contracting Officer when there are
questions about your authority. This delegation will remain in effect for the duration of
the contract unless revoked, in writing, by the Contracting Officer. You are not
authorized to redelegate your authority. If you have any questions concerning your role
as COTR, please contact me at 202-267-9422.
Attachment: Copy of executed contract.
________________________ Dated: _______________________
Rhonda Thomas
COTR
_______________________ Dated: _______________________
Dennis Scanlon, AJA-47
Administrative Contracting Officer
J - 32
DTFAWA-09-R-00055
Amendment No. 0002
Federal Aviation
Administration
Memorandum
Date: September 4, 2009
To: Jim Robb
Federal Aviation Administration
From: Dennis L. Scanlon, Contracting Officer, AJA-47
Subject: Delegation of authority to act as Alternate COTR under
Contract No. DTFAWA-09-R-000xx
You are hereby delegated authority to act as the Alternate Contracting Officer’s
Technical Representative (COTR) for the above referenced contract. A copy of the
contract is attached. As such, your duties are to assist the Contracting Officer in the
administration of the contract through performance and closeout. This delegation may
be changed only by the Contracting officer in writing. As the Alternate COTR, you shall
represent the Contracting Officer within the scope of the following authority,
responsibilities, and limitations:
AUTHORITY:
As Alternate COTR, you have the authority to:
1. Perform surveillance of the contract work and conduct inspections that are necessary
to assure compliance with the contract terms and conditions. Resolve day-to-day
matters within the scope of your authority.
2. Make recommendations to the Contracting Officer when it appears that there is a
need for a change in scope or terms of contract in the event the contractor has
submitted a request for waiver to address non-conformances, Engineering Change
Proposals (ECPs) or Value Engineering Change Proposals (VECPs).
3. Perform, or cause to be performed, inspection(s) necessary for the acceptance of
deliverables (including contract line item numbers (CLINs) and Contract Data
Requirements Lists (CDRLs)) as stated in the contract and to require the contractor to
correct any deficiencies. Periodically, on-site surveillance visits may be required.
4. Assist the contractor in interpreting the contract specifications or technical
requirements provided that any interpretation or clarification that the COTR provides is
within the limitations prescribed later in this delegation.
5. Certify invoices to the Contracting Officer for payment. Evaluates progress payment
requests based on costs incurred and actual work accomplished.
J - 33
DTFAWA-09-R-00055
Amendment No. 0002
6. Obtain and maintain a listing of employees who will be working at the site. The list is
to be kept current by assuring that new employees are added and employees who are
terminated are deleted from the list. This is important to the security of the facility and
your list may be used as a basis for background checks by the security office in the
relevant location. A copy of this list shall be provided to the security office at least
quarterly, and at any time, a contractor employee is added or deleted from the list.
RESPONSIBILITIES:
As Alternate COTR, you have the responsibility to:
1. Be familiar with and understand contract requirements (SOW, specification, CLINs
and work-break-down structure and implications of contractor performance in relation to
the contract requirements.
2. Attend adequate initial COTR training within two months of appointment and obtain
adequate refresher training annually.
3. Establish a technical performance review program for evaluation of the contractor’s
work.
4. Coordinate with Contracting Officer whether support contractors have signed
nondisclosure forms and liaison agreement.
5. Review the Contractor’s performance of the technical requirements of the contract in
accordance with the contract terms, funding, conditions, and specifications. Notify the
Contracting Officer, in writing, of any indication that the terms of the contract are not
being met.
6. Monitor the contractor’s compliance with safety and security requirements. Ensure
contractor's performance of requirements is in agreement with provisions contained in
security clauses 3.14-1 through 5, which are prescribed for use with all FAA contracts.
7. Report any observed fraud, waste, or inefficiencies to the Contracting Officer.
8. Maintain liaison and direct communications with the Contractor and the Contracting
Officer. Meet with the Contractor or his designated representative at the beginning of
the contract to discuss working methods and scheduling and as otherwise needed.
Also, serve as the contact through which the contractor can relay questions and
problems of a technical nature to the Contracting Officer.
9. Draft technical portions of Contracting Officer letters to the contractor.
10. Ensure appropriate confidentiality of contractor submissions bearing proprietary
markings.
11. Review and evaluate the technical aspects of contractor proposals and furnish
evaluation comments and recommendations to the Contracting Officer.
12. Assist the Contracting Officer in negotiating supplemental agreements.
13. Advise the Contracting Officer on contractual matters of a technical nature.
14. Recommend needed change orders to the Contracting Officer when in the best
interest of the Government.
15. Inform the Contracting Officer as to the status and progress of performance under
the contract.
16. Alert the Contracting Officer to any potential or existing problems.
17. Submit reports the Contracting Officer requires to perform his/her duties.
J - 34
DTFAWA-09-R-00055
Amendment No. 0002
18. Provide the Contracting Officer a copy of all technical correspondence with the
contractor.
19. In the absence of need for or presence of Quality Reliability Officer (QRO), inspect
contract deliverables for conformance to the contract specifications and accept or reject
them.
20. Furnish the Contracting Officer requests for waivers (whether generated by
Government or contractor personnel) along with supporting paperwork.
21. Furnish copies of written communication between you and the contractor to the
Contracting Officer.
22. Furnish information on contractor performance as input to the past performance
data base or as otherwise requested by the Contracting Officer.
23. Report any discrepancies in payment vouchers to the Contracting Officer. Provide
documentation to support the representation.
24. Maintain a file of all correspondence (or data) initiated or received by you in
connection with subject contract.
25. Maintain an arms-length relationship with the contractor.
26. Practice claims avoidance, halting unspecified accelerated production and/or
directions of other Government employees.
27. Review all contractor-furnished reports.
28. Conduct business with industry in a manner that is above reproach.
29. Date stamp the receipt time of all vouchers or invoices.
30. Evaluate progress payment requests against the contractor’s efforts including
schedule, quality, performance, and the general progress of the acquisition.
31. Return improper vouchers or invoices to the Contractor within 7 days of receipt.
32. Seek guidance from the Contracting Officer for specific situations not covered in this
delegation.
33. Assist in the analyses of engineering change proposals (ECPs) and value
engineering change proposals (VECPs), validating and calculating estimated savings
and the contractor’s share for VECPs.
34. Ensure administration of government furnished property.
a. Advise the Contracting Officer to delegate a Property Administrator to administer
government property contract requirements.
b. Notify Property Administrator of scheduled pre-award and post-award meetings.
c. Provide the Contracting Officer with a listing of government furnished property
(including quantity and value) for inclusion into contract.
d. Notify the Property Administrator of scheduled program reviews.
e. Prepare documentation to track the movement and accountability of government
furnished property which shall include the following information:
(1) Technical Officer signature.
(2) Contracting Officer signature.
(3) Points of contacts with phone numbers for the Consignee and Consignor location.
(4) Line item property description, acquisition date, serial number, model/type, quantity,
unit cost and total cost.
(5) Transportation service requirements (when applicable):
(a) Recommended shipment method.
(b) Weights and dimensions.
J - 35
DTFAWA-09-R-00055
Amendment No. 0002
(c) Special shipping/delivery instructions (when applicable).
(d) Accounting classification for transportation costs.
f. Provide the Property Administrator with the completed document for processing.
g. Provide the Property Administrator with invoice to authorize the acquisition of contract
acquired property (this refers to non-expendable property only).
(1) Invoices shall include vendor and contractor name, address, phone number, and
point of contact.
(2) Invoices shall include line item property description, acquisition date, serial number,
model/type, quantity, unit cost and total cost.
h. Notify the Property Administrator of administrative changes to the contractor (i.e.
Company name, address, point of contact, etc.).
i. Assist the Property Administrator with the disposal of excess government furnished
property and/or contractor acquired property as required.
(1) Screen excess government furnished property and/or contractor acquired property
for potential internal program office use.
(a) Prepare documentation to transfer excess government furnished property and/or
contractor acquired property to internal programs.
(b) Prepare documentation to return government furnished property to program office.
(2) Notify the Property Administrator if there is no-use for excess government furnished
property and/or contractor acquired property.
j. Initiate the Report of Survey for Lost, Damage, and Destroyed (LDD) government
furnished property and/or contractor acquired property as required.
(1) Assist the Property Administrator with the valuation of lost, damaged and destroyed
government furnished property and/or contractor acquired property.
(2) Advise the Property Administrator of recommendations for contractor liability for
accountable lost, damaged and destroyed government furnished property and/or
contractor acquired property.
(3) Provide replacement government property for lost, damaged or destroyed
government furnished property or contractor acquired property.
(a) Prepare documentation for the issuing of government furnished property.
(b) Advise the Contracting Officer to authorize the acquisition of contractor-acquired
property.
k. Advise the Property Administrator on property related matters of a technical nature.
l. Alert the Property Administrator to any potential or existing property issues.
m. Notify the Property Administrator of contract termination/cancellation.
35. Report through normal administrative channels to the DOT Inspector General (IG)
and to the CO any evidence of prime or subcontractor kickback, attempt to bribe, or
other fraudulent behavior.
LIMITATIONS:
As Alternate COTR, you shall not:
1. Make or give the appearance of being able to make contractual commitments outside
the scope of the contract or execute or agree to modifications or take actions that would
commit the Government to a change in contract price, quality, quantity, or delivery
schedule.
J - 36
DTFAWA-09-R-00055
Amendment No. 0002
2. Sign any changes or modifications to contracts and/or delivery order(s).
3. Make determinations regarding issues of contractor liability that may arise during
contract performance. Such issues should be referred to the Contracting Officer.
4. Take part in a labor controversy or dispute involving the contractor or its employees.
5. Direct the contractor on how to perform the work.
6. Issue stop-work orders.
7. Supervise contractor employees implicitly or explicitly which could constitute personal
services.
8. Engage in conduct prejudicial to the Government.
9. Use public office for gain.
10. Impede Government efficiency or economy.
11. Lose independence or impartiality.
12. Make a Government decision outside official channels.
13. Affect adversely the public’s confidence in the Government.
The duties and responsibilities set forth herein are not intended to be all-inclusive. As
Alternate COTR, you are required to consult with the Contracting Officer when there are
questions about your authority. This delegation will remain in effect for the duration of
the contract unless revoked, in writing, by the Contracting Officer. You are not
authorized to redelegate your authority. If you have any questions concerning your role
as Alternate COTR, please contact me at 202-267-9422.
Attachment: Copy of executed contract.
________________________ Dated: _______________________
Jim Robb
Alternate COTR
_______________________ Dated: _______________________
Dennis Scanlon, AJA-47
Administrative Contracting Officer
J - 37
DTFAWA-09-R-00055
Amendment No. 0002
J.6. TASK ORDER 0001 PERTAINING TO BASE PERIOD
Estimated
Requirement No. / LOE for
Management Team Task TASK CDRLs
Lead Order No.
0001
1767 Provide standard systems engineering support, to A003, A007,
include evaluation, analyses and documentation of A008, A009,
standard engineering processes and procedures A010, A011,
and risk planning. Serve as technical advisors on A012, A014
Requirement 1 - Systems COTs acquisitions, security policies, T&E and
Engineer Support / SWIM various plans: safety, security, CM, QA, SEMP, and
Program Office QA plans. Provide program status and EVM reports.
Conduct technical meetings and facilitate the
sharing of technical knowledge. Provide agendas
and minutes to support designated meetings.
3787 Review, develop, validate, analyze, and document A014, A015,
existing technical concepts and requirements (FRP, A016, A017,
SVSD, etc.) including core services; future A018, A019,
Requirement 2 - segments; architectural documentation A020, A021,
Requirement Architecture/ development, to include Architectural element A022, A023,
Documentation definition; registry/repository requirements, IRD, and A024, A025,
Development / SWIM ICD; Gateway XML Gateway Requirements and A026, A027,
Requirements/Architectur IRD; and Policy Server Requirements and IRD; A028
al Lead MOM Requirements and IRD; FRP Appendix
Updates, SvSD, and technical reviews and
comments.
757 Conduct analysis to help determine SWIM A032, A033,
Governance implementation polices and A034
procedures. Document findings and present in
reports. Review existing governance
documentation and provide comments and
Requirement 3 -
recommendations. Develop, implement, validate,
Governance / SWIM
maintain/update a SOA Enabling Technology Plan.
Governance Lead
Revise, validate, maintain/update, and document
core SOA reference architecture model, network
topology of SOA solution, IT architecture gaps, etc.
against strict adherence to architecture strategy.
Requirement 4 - 252 A035
Enterprise Information
Work in collaboration with the SWIM team to
Management (EIM) /
perform concept exploration and development of
SWIM Program Office ,
EIM plans which define the definition of the SWIM
Subcontractors, and
data architecture.
Stakeholders
Requirement 5 - SWIM 252 A037
Integration Support / Develop a SWIM Infrastructure Implementation Plan
SWIM Program Office, (SIIP) to capture conceptual blueprint for the design
Subcontractors, and of the SWIM Infrastructure.
Stakeholders
J - 38
DTFAWA-09-R-00055
Amendment No. 0002
Estimated
Requirement No. / LOE for
Management Team Task TASK CDRLs
Lead Order No.
0001
4544 Designated to serve as a SWIM implementation A003, A005,
POC and will attend all design and program review A006, A013,
Requirement 6 - SWIM
Provide program status and EVM reports. Provide A038, A039,
Implementing Programs
technical support to the SIPs: review technical A040
(SIPS) Oversight / SWIM
documentation and provide technical comments,
Implementation Lead
assistance and recommendations. Provide
assistance with the preparation of PLA/SLA/MOAs.
284 Assist the SWIM PO in financial management tasks. A043, A044
Develop, track, update, model, and report
Requirement 7 - Program
performance metrics to support investment decision
Control / SWIM Program
IAW OMB Exhibit 300, M&A Plan, Best Practices,
Control Team
quarterly MMWG, and as otherwise directed.
Maintain performance metrics database.
568 Provide program management support for program A045, A047
Requirement 8 - Program communications, to include responses to A001, A002,
Management Support/ Congressional inquiries, other governmental bodies, A003, A014
SWIM Program Manager media, etc., and maintain program plans, to include
communications, website and outreach plans.
Note:
This Task Order and all subsequent Task Orders (as applicable) will be finalized after
Contract Award.
J - 39
DTFAWA-09-R-00055
Amendment No. 0002
J.7. APPROVED CONTRACTOR PERSONNEL PER TASK ORDER
Approved Personnel Name
[To Be Completed by the
Labor Category
Contractor]
1. Program Analyst (Mid-level)
2. Systems Engineer (Senior-level)
3. Systems Engineer (Mid-level)
SOA Architect (Senior-level)
4.
SOA Architect (Mid-level)
5.
SOA Architect (Jr-level)
6.
7. SOA Developer (Senior-level)
8. SOA Developer (Mid-level)
9. Business Analyst (Senior-level)
10. Business Analyst (Mid-level)
11. Business Analyst (Jr-level)
12. Business Analyst (Entry-level)
13. Enterprise Architect (Mid-level)
14. SOA Systems Analyst (Jr-level)
See Paragraph I.8
J - 40
DTFAWA-09-R-00055
Amendment No. 0002
J.8. TEAM LEADS POINT OF CONTACT LIST
Requirements Team Leads Contact Information
1. Requirement 1 JIM ROBB 202-267-8357
Systems Engineer Support Jim.robb@faa.gov
Requirement 2 202-267-8357
JIM ROBB
2. Requirement Architecture/ Jim.robb@faa.gov
Documentation Development
Requirement 3 JIM ROBB 202-267-8357
3. Governance Jim.robb@faa.gov
4. Requirement 4 JIM ROBB 202-267-8357
Enterprise Information Management Jim.robb@faa.gov
5. Requirement 5 JIM ROBB 202-267-8357
SWIM Integration Support Jim.robb@faa.gov
Requirement 6
6.
SWIM Implementing Programs
JEFF HOBBS 202-267-9772
(SIPS) Oversight
Jeffrey.hobbs@faa.gov
Requirement 7
7. 202-267-8003
Program Control DEBORAH YOUNG
Deborah.young@faa.gov
8. 202-267-3391
Ahmad.usmani@faa.gov
AHMAD USMANI
Requirement 8
Program Management Support
202-493-4671
RHONDA THOMAS Rhonda.thomas@faa.gov
J - 41
DTFAWA-09-R-00055
Amendment No. 0002
K.1. CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (3.1-1
DECEMBER 2005)
This screening information request (SIR) or contract, as applicable, incorporates by
reference the provisions or clauses listed below with the same force and effect as if they
were given in full text. Upon request, the Contracting Officer will make the full text
available, or Offerors and contractors may obtain the full text via Internet at:
http://conwrite.faa.gov (on this web page, select "Search and View Clauses").
3.2.2.3-3 Affiliated Offerors (April 2009)
3.1.7-2 Organizational Conflicts of Interest (August 1997)
3.6.2-5 Certification of Non-segregated Facilities (April 1996)
3.6.3-1 Clean Air and Water Certification (April 2000)
K.2. TYPE OF BUSINESS ORGANIZATION (3.2.2.3-10 JULY 2004)
By checking the applicable box, the Offeror (you) represents that--
a.) You operate as [ ] a corporation incorporated under the laws of the State of
____________________ , [ ] an individual, [ ] a partnership, [ ] a nonprofit
organization, [ ] a joint venture or [ ] other ____________[specify what type of
organization]
b.) If you are a foreign entity, you operate as [ ] an individual, [ ] a partnership, [ ] a
nonprofit organization, [ ] a joint venture, or [ ] a corporation, registered for business
in _____________________________________(country).
K.3. AUTHORIZED NEGOTIATORS (3.2.2.3-15 JULY 2004)
The Offeror states that the following persons are authorized to negotiate on your behalf
with the FAA in connection with this offer:
Name:_______________________
Title:_________________________
Phone number:_________________
K.4. PLACE OF PERFORMANCE (3.2.2.3-23 JULY 2004)
a.) The Offeror (you), in fulfilling any contract resulting from this SIR, [ ] intends, [ ] does
not intend (check applicable block) to use one or more plants or facilities located at a
different address from your address as stated in this offer.
b.) If you check 'intends' in paragraph (a) above, insert the following information:
Place of Performance Street:
City:
State:
Zip Code:
Name of owner and operator, if other than the owner
K-1
DTFAWA-09-R-00055
Amendment No. 0002
K.5. TAXPAYER IDENTIFICATION (3.2.2.3-70 JULY 2004)
a.) Definitions.
(1) "Common parent," as used in this clause, means a corporate entity that owns
or controls an affiliated group of corporations that files an Offeror's (you,
your) Federal income tax returns on a consolidated basis, and of which you
are a member.
(2) "Corporate status," as used in this clause, means a designation as to
whether you are a corporate entity, an unincorporated entity (for example,
sole proprietorship or partnership), or a corporation providing medical and
health care services.
(3) "Taxpayer Identification Number (TIN)," as used in this clause, means the
number the Internal Revenue Service (IRS) requires you use in reporting
income tax and other returns.
b.) All Offerors must submit the information required in paragraphs (c) through (e) of this
provision to comply with reporting requirements of 26 U.S.C. 6041, 6041A, and
6050M and implementing regulations issued by IRS. The FAA will use this
information to collect and report on any delinquent amounts arising out of your
relation with the Federal Government, under Public Law 104 -134, the Debt
Collection Improvement Act of 1996, Section 31001(I)(3). If the resulting contract is
subject to the reporting requirements and you refuse or fail to provide the information,
the Contracting Officer (CO) may reduce your payments 31 percent under the
contract.
c.) Taxpayer Identification Number (TIN).
[ ] TIN: ______________________________
[ ] TIN has been applied for.
[ ] TIN is not required because:
[ ] Offeror is a nonresident alien, foreign corporation, or
foreign partnership that does not leave income effectively
connected with the conduct of a trade or business in the U.S.
and does not have an office or place of business or a fiscal
paying agent in the U.S.;
[ ] Offeror is an agency or instrumentality of a foreign
government;
[ ] Offeror is an agency or instrumentality of a Federal, state,
or local government;
[ ] Other--State basis. _________________________.
d.) Corporate Status.
[ ] Corporation providing medical and health care services, or
engaged in the billing and collecting of payments for such
services;
[ ] Other corporate entity
[ ] Not a corporate entity
[ ] Sole proprietorship
[ ] Partnership
[ ] Hospital or extended care facility described in 26 CFR
501(c)(3) that is exempt from taxation under 26 CFR 501(a).
K-2
DTFAWA-09-R-00055
Amendment No. 0002
e.) Common Parent.
[ ] A common parent does not own or control the Offeror as
defined in paragraph (a).
[ ] Name and TIN of common parent:
Name _____________________________________
TIN _______________________________________
K.6. CERTIFICATION REGARDING DEBARMENT, SUSPENSION, PROPOSED
DEBARMENT, AND OTHER RESPONSIBILITY MATTERS (3.2.2.7-7 APRIL
1996)
a.) The Offeror certifies, to the best of its knowledge and belief, that--
(1) The Offeror and/or any of its Principals--
i) Are [ ] are not [ ] presently debarred, suspended, proposed for debarment,
or declared ineligible for the award of contracts by any Federal agency;
ii) Have [ ] have not [ ] within a three-year period preceding this offer, been
convicted of or had a civil judgment rendered against them for:
commission of fraud or a criminal offense in connection with obtaining,
attempting to obtain, or performing a public (Federal, state, or local)
contract or subcontract; violation of Federal or state antitrust statutes
relating to the submission of offers: or commission of embezzlement,
theft, forgery, bribery, falsification or destruction of records, making false
statements, or receiving stolen property; and
iii) Are [ ] are not [ ] presently indicted for, or otherwise criminally or civilly
charged by a governmental entity with, commission of any of the offenses
enumerated in subdivision (a)(1)(i)(B) of this provision.
(2) The Offeror has [ ] has not [ ] within a three-year period preceding this offer,
had one or more contracts terminated for default by any Federal agency.
'Principals,' for the purposes of this certification, means officers; directors; owners;
partners; and, persons having primary management or supervisory responsibilities
within a business entity (e.g., general manager; plant manager; head of a subsidiary,
division, or business segment, and similar positions). THIS CERTIFICATION
CONCERNS A MATTER WITHIN THE JURISDICTION OF AN AGENCY OF THE
UNITED STATES AND THE MAKING OF A FALSE, FICTITIOUS, OR FRAUDULENT
CERTIFICATION MAY RENDER THE MAKER SUBJECT TO PROSECUTION UNDER
SECTION 1001, TITLE 18, UNITED STATES CODE.
b.) The Offeror shall provide immediate written notice to the Contracting Officer if, at any
time prior to contract award, the Offeror learns that its certification was erroneous
when submitted or has become erroneous by reason of changed circumstances.
c.) A certification that any of the items in paragraph (a) of this provision exists will not
necessarily result in withholding of an award under this SIR. However, the
certification will be considered in connection with a determination of the Offeror's
responsibility. Failure of the Offeror to furnish a certification or provide such
additional information as requested by the Contracting Officer may render the Offeror
non-responsible.
K-3
DTFAWA-09-R-00055
Amendment No. 0002
d.) Nothing contained in the foregoing shall be construed to require establishment of a
system of records in order to render, in good faith, the certification required by
paragraph (a) of this provision. The knowledge and information of an Offeror is not
required to exceed that which is normally possessed by a prudent person in the
ordinary course of business dealings.
e.) The certification in paragraph (a) of this provision is a material representation of fact
upon which reliance was placed when making award. If it is later determined that the
Offeror knowingly rendered an erroneous certification, in addition to other remedies
available to the Government, the Contracting Officer may terminate the contract
resulting from this SIR for default.
K.7. CERTIFICATION OF REGISTRATION IN CENTRAL CONTRACTOR
REGISTRATION (CCR) (3.3.1-35 APRIL 2006)
In accordance with paragraph I.6, Central Contractor Registration, Offeror certifies that
they are registered in the CCR Database and have entered all mandatory information
including the DUNS or DUNS+4 Number.
Name: ______________________________
Title: _______________________________
Phone Number: _______________________
K.8. PREVIOUS CONTRACTS AND COMPLIANCE REPORTS (3.6.2-6 APRIL 1996)
The Offeror represents that—
a.) It [ ] has, [ ] has not, participated in a previous contract or subcontract subject either
to the "Equal Opportunity" clause of this solicitation, the clause originally contained in
Section 310 of Executive Order No. 10925, or the clause contained in Section 201 of
Executive Order No. 11114;
b.) It [ ] has, [ ] has not, filed all required compliance reports; and
c.) Representations indicating submission of required compliance reports, signed by
proposed subcontractors, will be obtained before subcontract awards.
K.9. AFFIRMATIVE ACTION COMPLIANCE (3.6.2-8 APRIL 1996)
The Offeror represents that
a.) it [ ] has developed and has on file, [ ] has not developed and does not have on file,
at each establishment, affirmative action programs required by the rules and
regulations of the Secretary of Labor (41 CFR 60-1 and 60-2), or
b.) it [ ] has not previously had contracts subject to the written affirmative action
programs requirement of the rules and regulations of the Secretary of Labor.
K.10. CLEAN AIR AND WATER CERTIFICATION (3.6.3-1 APRIL 2000)
The Offerors signature on this contract constitutes an affirmative attestation that:
a.) Any facility to be used in the performance of this contract is not listed on the
Environmental Protection Agency (EPA) List of Violating Facilities;
K-4
DTFAWA-09-R-00055
Amendment No. 0002
b.) The Offeror will immediately notify the Contracting Officer, of the receipt of any
communication from the Administrator, or a designee, of the EPA, indicating that any
facility that the Offeror uses for the performance of the contract is under
consideration to be listed on the EPA List of Violating Facilities; and
c.) The Offeror will include a certification substantially the same as this certification,
including this paragraph, in every nonexempt subcontract.
K.11. CERTIFICATION OF DATA (3.8.2-18 OCTOBER 1996)
a.) The Offeror represents and certifies that to the best of its knowledge and belief, the
information and/or data (e.g., company profile, qualifications, background statements,
brochures) submitted with its offer is current, accurate, and complete as of the date of
its offer.
b.) The Offeror understands that any inaccurate data provided to the Department of
Transportation may subject the Offeror, its employees, or its representatives to: (1)
prosecution for false statements pursuant to 18 U.S.C. 1001 and/or; (2) enforcement
action for false claims or statements pursuant to the Program Fraud Civil Remedies
Act of 1986, 31 U.S.C. 3801-3812 and 49 CFR Part 31 and/or; (3) termination for
default under any contract resulting from its offer and/or; (4) debarment or
suspension.
c.) The Offeror agrees to obtain a similar certification from its subcontractors.
Signature: _____________________________
Date: _________________________________
Typed Name and Title: ___________________
Company Name: ________________________
This certification concerns a matter within the jurisdiction of an agency of the United
States and the making of a false, fictitious, or fraudulent certification may render the
maker subject to prosecution under Title 18, United States Code, Section 1001.
K-5
DTFAWA-09-R-00055
Amendment No. 0002
PART IV - SECTION L
INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS
L.1. CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (3.1-1
DECEMBER 2005)
This screening information request (SIR) or contract, as applicable, incorporates by
reference the provisions or clauses listed below with the same force and effect as if they
were given in full text. Upon request, the Contracting Officer will make the full text
available, or Offerors and contractors may obtain the full text via Internet at:
http://conwrite.faa.gov (on this web page, select "Search and View Clauses").
3.1.7 -4 Organizational Conflict of Interest SIR Provision (February 2009)
3.1.7-5 Disclosure of Conflicts of Interest (February 2009)
3.2.2.3-1 False Statements in Offers (July 2004)
3.2.2.3-11 Unnecessarily Elaborate Submittals (July 2004)
3.2.2.3-12 Amendments to Screening Information Requests (July 2004)
3.2.2.3-13 Submission of Information/Documentation/Offers (July 2004)
3.2.2.3-14 Late Submissions, Modifications, and Withdrawals of Submittals (July
2004)
3.2.2.3-16 Restriction on Disclosure and Use of Data (July 2004)
3.2.2.3-17 Preparation of Offers (July 2004)
3.2.2.3-19 Contract Award (July 2004)
3.6.2-7 Preaward On-Site Equal Opportunity Compliance Review (November
1997)
3.13-4 Contractor Identification Number – Data Universal Numbering System
(DUNS) Number (April 2006)
L.2. MINIMUM OFFER ACCEPTANCE PERIOD (3.2.2.3-2 JULY 2004)
a.) “Acceptance period”, as used in this provision, means the number of calendar days
the FAA has to award a contract from the date the SIR specifies for receiving offers.
b.) This provision supersedes any language about the acceptance period appearing
elsewhere in this SIR.
c.) The FAA requires a minimum acceptance period of One Hundred Twenty (120)
calendar days from receipt of Volumes 2, 3, and 4 Proposals.
d.) The Offeror (you) may specify a longer acceptance period than the period shown in
paragraph (c). To specify a longer period, fill in the blank: The Offeror allows the
following acceptance period: _____ calendar days.
e.) We may reject an offer allowing less than the FAA's minimum acceptance period.
f.) You agree to fulfill your offer completely if the FAA accepts your offer in writing within:
(1) The acceptance period stated in paragraph (c) of this provision; or
(2) Any longer acceptance period stated in paragraph (d) of this provision.
g.) The completion and submission to the FAA of a proposal will constitute an offer and
will indicate the Offeror’s unconditional assent to the terms and conditions in this SIR,
and in any attachments hereto, for the minimum offer acceptance period identified in
Section L.2.c upon the receipt of Volumes 2, 3 and 4.
L-1
DTFAWA-09-R-00055
Amendment No. 0002
L.3. REQUIREMENTS FOR COST OR PRICING DATA OR OTHER INFORMATION
ALTERNATE II (3.2.2.3-38/ALT2 JULY 2004)
a.) The FAA does not require certified cost or pricing data.
b.) The Offeror must provide the following information, if available:
(1) An explanation of [deleted]your rates, including labor cost, overhead, G&A,
and profit;
(2) Any recent DCAA audits and contact information;
(3) If you are on the GSA Schedule, state the schedule, your rates thereunder,
and whether the proposed rates hereunder are at or below the schedule
rates; and
(4) Identify any other government contracts for equivalent services and state the
contract number, your rates thereunder, and whether the proposed rates
hereunder are at or below those rates.
L.4. TYPE OF CONTRACT (3.2.4-1 APRIL 1996)
The FAA contemplates award of an Indefinite Delivery Indefinite Quantity (ID/IQ)
Contract with LOE firm fixed labor rates resulting from this Screening Information
Request. Travel Costs, associated Administrative Costs, and Other Direct Costs, if
authorized, will be reimbursed on a cost basis as set forth in this Request for Proposal.
L.5. PROTEST (3.9.1-3 NOVEMBER 2002)
AS A CONDITION OF SUBMITTING AN OFFER OR RESPONSE TO THIS SIR (OR
OTHER SOLICITATION, IF APPROPRIATE), THE OFFEROR OR POTENTIAL
OFFEROR AGREES TO BE BOUND BY THE FOLLOWING PROVISIONS RELATING
TO PROTESTS:
a.) Protests concerning Federal Aviation Administration Screening Information Requests
(SIRs) or awards of contracts shall be resolved through the Federal Aviation
Administration (FAA) dispute resolution system at the Office of Dispute Resolution for
Acquisition (ODRA) and shall be governed by the procedures set forth in 14 C.F.R.
Parts 14 and 17, which are hereby incorporated by reference. Judicial review, where
available, will be in accordance with 49 U.S.C. 46110 and shall apply only to final
agency decisions. A protestor may seek review of a final FAA decision only after its
administrative remedies have been exhausted.
b.) Offerors initially should attempt to resolve any issues concerning potential protests
with the Contracting Officer. The Contracting Officer should make reasonable efforts
to answer questions promptly and completely, and, where possible, to resolve
concerns or controversies. The protest time limitations, however, will not be extended
by attempts to resolve a potential protest with the Contracting Officer.
c.) The filing of a protest with the ODRA may be accomplished by mail, overnight
delivery, hand delivery, or by facsimile. A protest is considered to be filed on the date
it is received by the ODRA.
d.) Only an interested party may file a protest. An interested party is one whose direct
economic interest has been or would be affected by the award or failure to award an
L-2
DTFAWA-09-R-00055
Amendment No. 0002
FAA contract. Proposed subcontractors are not "interested parties" within this
definition.
e.) A written protest must be filed with the ODRA within the times set forth below, or the
protest shall be dismissed as untimely:
(1) Protests based upon alleged improprieties in a solicitation or a SIR that are
apparent prior to bid opening or the time set for receipt of initial proposals
shall be filed prior to bid opening or the time set for the receipt of initial
proposals.
(2) In procurements where proposals are requested, alleged improprieties that
do not exist in the initial solicitation, but which are subsequently incorporated
into the solicitation, must be protested not later than the next closing time for
receipt of proposals following the incorporation.
(3) For protests other than those related to alleged solicitation improprieties, the
protest must be filed on the later of the following two dates:
i) Not later than seven (7) business days after the date the protester knew or
should have known of the grounds for the protest; or
ii) If the protester has requested a post-award debriefing from the FAA
Product Team, not later than five (5) business days after the date on
which the Product Team holds that debriefing.
f.) Protests shall be filed at:
(1) Office of Dispute Resolution for Acquisition, AGC-70,
Federal Aviation Administration,
800 Independence Ave., S.W.,
Room 323,
Washington, DC 20591,
Telephone: (202) 267-3290,
Facsimile: (202) 267-3720; or
(2) other address as specified in 14 CFR Part 17.
g.) At the same time as filing the protest with the ODRA, the protester shall serve a copy
of the protest on the Contracting Officer and any other official designated in the SIR
for receipt of protests by means reasonably calculated to be received by the
Contracting Officer on the same day as it is to be received by the ODRA. The protest
shall include a signed statement from the protester, certifying to the ODRA the
manner of service, date, and time when a copy of the protest was served on the
Contracting Officer and other designated official(s).
h.) Additional information and guidance about the ODRA dispute resolution process for
protests can be found on the ODRA Website at http://www.faa.gov.
L.6. APPROVAL OF CONTRACT (3.13-1 APRIL 1996)
This contract is subject to the written approval of the Contracting Officer and shall not
be binding until so approved.
L-3
DTFAWA-09-R-00055
Amendment No. 0002
L.7. MILESTONE SCHEDULE
The following represents the projected procurement milestone schedule as of the release date
of the SIR.
Activity Date
Release SIR September 22, 2009
Deadline for Offerors’ Proposal questions October 6, 2009
Deadline: Proposal for Volume I Technical, Factor 1 October 30, 2009
Notification of Down Selected Offerors December 4, 2009
AND
Downselected Offerors Notice to Submit Volumes 2,
3, and 4
Deadline Proposal Volumes 2, 3, and 4 January 6, 2010
Oral Presentations –Sample Problem January 6- February 1,
2010
Award Contract and Task Order 0001 March 1, 2010
L.8. MAILING ADDRESS/DELIVERY ADDRESS
Offerors must submit proposals in hard copy as follows; an original, two (2) hard copies, and
one (1) electronic media copy, in Microsoft Office 2003 or 2007 format. IN the event of a
discrepancy between the hard copy and the electronic copy, the hard copy takes precedence.
Offerors that choose to submit proposals should utilize a means of delivery that ensures the
FAA receives the Proposal by 2:00 PM Eastern Time (Standard or Daylight Savings as
applicable on the due date) on the deadline date specified in paragraph L.7.0. The address for
delivery of Proposals is:
Federal Aviation Administration
C/O YWCA Building
624 9th Street, NW, Suite 500
Washington DC 20001
Telephone: 202-233-0172
Someone will be present on the day proposals are due to receive Volume 1. The Offerors must
notify Dennis L. Scanlon via e-mail (dennis.scanlon@faa.gov) after delivery is made to the
above address.
L.9. SIGNED ORIGINALS
The original proposal must include the signed original of all documents requiring signature by
the Offeror, to include a confirmation of modifications to the SIR.
L.10. PROPOSAL QUESTIONS, CLARIFICATIONS AND DISCREPANCIES
If an Offeror believes that these instructions contain an error, omission, or are otherwise
unsound, the Offeror shall immediately notify the Contracting Officer in writing with supporting
rationale. If discrepancies are not noted prior to Proposal submission, it shall be deemed that
there are no discrepancies.
Any Offeror questions or clarifications regarding any section of the SIR, if any, shall be prepared
in writing and submitted to the Contracting Officer. Offerors must identify
L-4
DTFAWA-09-R-00055
Amendment No. 0002
questions or clarifications by topic, and must refer to the applicable SIR section or
paragraph, (e.g., Section H, Provision H-3, subparagraph (a)). The Government will
post questions or clarifications and responses thereto on the FAA Contract
Opportunities website. The source of the questions or clarifications will not be
identified.
All questions or clarifications must be received by the Contracting Officer by the
deadline set forth in Section L.7. The Offeror shall be responsible for ensuring that the
Government Contracting Officer has actually received the questions or clarifications.
Offerors are encouraged to use e-mail for all communications pursuant to this
paragraph. E-mail must be submitted to Dennis Scanlon, at dennis.scanlon@faa.gov.
L.11. EXPENSES RELATED TO OFFEROR SUBMISSIONS
The FAA will not pay for the information solicited, nor reimburse the Offeror for any
costs incurred in the preparation or submission of any response to requests for
proposals or in making necessary studies or designs for the preparation thereof,
including attendance at any pre-proposal conferences.
Furthermore, no pre-contract costs will be allowed on this contract. Pre-contract cost is
defined as any cost incurred at the Offeror’s risk in anticipation that any such cost may
later be charged to any resulting contract or task assignments, and to the extent that
they would have been allowable if incurred after the date of the contract or task
assignment execution and to the extent authorized by the Contracting Officer.
L.12. ALTERNATE PROPOSALS
Alternate proposals are NOTauthorized to be submitted in response to this SIR.
L.13. EXCEPTIONS TO TERMS OR CONDITIONS OF THE SIR
Offerors must submit proposed exceptions in writing and referencing the SIR section
number. Submission of exceptions does not bind the FAA to accept them and
submission of the proposal constitutes an unconditional offer to perform the contract
according to the original terms of the SIR. Offerors are cautioned to consult with the
Contracting Officer before submitting any offer that takes exception to any term or
condition of this SIR.
L-5
DTFAWA-09-R-00055
Amendment No. 0002
L.14. PROPOSAL PRESENTATION
The Offeror’s proposal submission must consist of four volumes: Volume I Technical
Proposal (Factor 1 and Subfactors Only) and Offer and Other Documents; Volume 2
Technical Proposal (Factors 2, 3, 4, and 5 and Subfactors); and Volume 3 Cost
Proposal, and Volume 4 Task Order 0001 Proposal. The Offeror’s proposals shall be
organized as follows:
VOLUME DESCRIPTION PAGE LIMITS
VOL. 1 TECHNICAL
Table of Contents Not Restricted
Introductory Statement 2 Pages
Factor 1, Technical and Business 40 Pages
Approaches (DOWN SELECT)
SIR SECTION A, SF#33, Solicitation, Offer Restricted to SF 33,
and Award- Signed and acknowledgement and Modifications
of SIR modifications
SIR SECTION K, Representation, Restricted to Section
Certifications and Other Statement of K, as provided herein.
Offerors – Signed
VOL. 2 TECHNICAL
Factor 2 – Sample Technical Problem Not Restricted
Factor 3 – Experience of Personnel; 2 Pages per person
Factor 4 - Management Approach; and 6 pages
Factor 5 - Past Experience and Past 6 pages
Performance
SIR SECTION I.3, Disclosure of Certain Restricted to Section
Employee Relationships (3.1.7-6 October I.3, as provided herein.
2006)
Subcontracting Plan Not Restricted
VOL. 3 COST
SIR SECTION B, Supplies or Services And Section B
Prices/Cost – Completed Spreadsheet
Cost Proposal as instructed in Section L Not Restricted
VOL. 4 TASK ORDER 0001
Task Order Technical Proposal Not Restricted
Task Order Cost Proposal Not Restricted
L-6
DTFAWA-09-R-00055
Amendment No. 0002
L.15. PROPOSAL CONTENT
L.15.1. BINDING AND LABELING
L.15.1.1. Original
The original shall be placed in a binder and each volume shall be separately bound.
L.15.1.2. Copies
The Offeror shall submit one (1) original and two (2) copies of all loose leaf binder
proposal materials. A binder cover sheet shall be affixed to each volume that clearly
identifies each volume, volume number, copy number (i.e., copy 2 of 4), solicitation
number and the Offeror’s identification. Copy number shall appear at the bottom cover
of each binder to allow for rapid accountability. If material for a volume requires more
than one book, then that volume shall be labeled with the name and number of the
volume and book number, if any, (e.g., Technical Proposal, Volume1, Book 1 of 2).
L.15.1.3. Indexing
Tab indexing shall be used to identify all proposal sections. Each volume must be
organized such that an extensive search of the proposal is not necessary for its review.
Information not in its appropriate section and not appropriately referenced may be
assumed to have been omitted.
L.15.1.4. Page Size, Typing, Spacing, and Numbering
Offerors must use Microsoft Office 2003 or 2007 software applications. Page size shall
be 8-1/2 by 11 inches. The proposal pages may be printed on both sides of plain white
bond paper with each side enumerated for the page count. The type size shall be
“Arial” font and not less than 12-point with a single spacing, and a one-inch page margin
on all sides, except for legends and text associated with figures and tables as long as
the information portrayed remains easily readable. Foldouts (11 by 17 inch paper) will
only be acceptable for graphics, tables, and diagrams as long as they fold to 8-1/2 by
11inch size and will be counted as one page, however if both sides are used it will count
as two pages. Each section within a proposal volume shall be consecutively numbered.
The FAA will not evaluate or read any information beyond page limits as specified in
Section L.
L.16. DOWN SELECT PROCESS
The evaluation process will have three (3) phases: Review of Proposal Submittals,
Down Selection, and Final Evaluation as follows:
In the Review of Submittals Phase, the FAA will review each Offeror’s proposal
submittals for their completeness in addressing all SIR requirements. The FAA will also
review the proposal submittals to ensure that the information provided is sufficient to
award without the need to obtain further information from an Offeror and that the
submittals is sufficient for complete analysis and evaluation. The Offeror’s failure to
L-7
DTFAWA-09-R-00055
Amendment No. 0002
complete all required sections of the SIR may result in disqualification of the Offeror
from further consideration.
The Down Selection Phase will evaluate all remaining offers submitted to determine
those Offerors most likely to receive an award based on their responses to Volume 1,
Factor 1 (Down Select Criteria). In this phase, Offerors must submit only responses to
Volume I, Factor 1. Once the FAA makes its Down Select, the FAA will notify the
Offerors to submit responses to Volumes 2, 3, and 4. Only down selected Offeror(s) will
be required to submit Volumes 2, 3, and 4.
The Final Evaluation Phase will evaluate responses to Volume 2, Factors 3, 4 and 5,
and Volume 3. Also, the Offerors may be afforded the opportunity to make an Oral
Presentation of the Sample Technical Problem.
L.17. VOLUME 1, TECHNCIAL
Volume 1, Technical, is to be completed by all Offerors for consideration of down
selection as discussed above. Volume 1 consists of Factor 1(Technical and Business
Approaches) and Offer and Other Documents section.
L.17.1. FACTOR 1, TECHNICAL AND BUSINESS APPROACHES
As stated above in Section L.14, Offeror’s response to Factor 1, Technical and
Business Approaches, must be submitted by the due date set forth in Section L.7.
Factor 1 and its Subfactors must include the following:
a.) Subfactor A. (Down Select Subfactor). Technical Approach for SOW Requirement 1.
The Offeror’s proposal must describe their understanding of the work and
demonstrate that they have the ability and knowledge to fulfill the system engineering
SOW requirements, including the knowledge of salient operational procedures,
inherent problems, ideas for solutions, and the capability to perform system
engineering processes, such as knowledge standard systems engineering processes
and procedures to include, systems performance modeling and measurement,
change impact assessments, life cycle requirements, quality, safety, security,
maintainability, reliability, integrity of analyses, schedule considerations,
requirements analysis, and trade studies, product assessment, prototyping and test
and evaluations.
b.) Subfactor B (Down Select Subfactor). Technical Approach for SOW Requirements 2
through 5. The Offeror’s proposal must describe their understanding of the work and
demonstrate that they have the ability and knowledge to fulfill these technical SOW
requirements, including the knowledge of salient operational procedures, inherent
problems, ideas for solutions, and the capability to perform the technical
requirements, such as requirements architecture documentation development,
governance, EIM and SWIM Integration.
c.) Subfactor C (Down Select Subfactor). Technical Approach for SOW Requirement 6.
The Offeror’s proposal must describe their understanding of the work and
demonstrate that they have the ability and knowledge to fulfill the SIP oversight SOW
requirements, including the knowledge of salient operational procedures, inherent
L-8
DTFAWA-09-R-00055
Amendment No. 0002
problems, ideas for solutions, and the capability to perform the technical
requirements, such as PLAs, EVM, metrics, design and program reviews, SLAs, FTI
capacity and capacity development, testing, deployment, operations and
maintenance.
d.) Subfactor D (Down Select Subfactor). Business Approach for SOW Requirement 7.
The Offeror’s proposal must describe their understanding of the work and
demonstrate that they have the ability and knowledge to fulfill the program control
SOW requirements, including the knowledge of salient operational procedures,
inherent problems, ideas for solutions, and the capability to perform business related
requirements, such as knowledge of risk management, EVM documentation,
performance metrics, financial management and investment analysis.
e.) Subfactor E (Down Select Subfactor). Program Approach for SOW Requirement 8.
The Offeror’s proposal must describe their understanding of the work and
demonstrate that they have the ability and knowledge to fulfill the program
management support SOW requirements, including the knowledge of salient
operational procedures, inherent problems, ideas for solutions, and the capability to
perform overall program management support requirements, such as knowledge
program communications with various governmental entities and non-governmental
stakeholders, program plans, investment analysis and support program manager at
various meetings and conferences.
The offeror may view the GFI on the SWIM website at www.swim.gov to assist in the
preparation of their offer.
L.17.2. VOLUME 1, OFFER AND OTHER DOCUMENTS
The Offeror’s response must be submitted by the due date set forth in Section L.7 and
must include the following as stated in Section L.14:
a.) Table of Contents - Each Offeror must provide within this volume a table of contents
depicting what is contained in each of the volumes submitted in the Offeror’s
proposal, as well as a listing of all acronyms used and a glossary of terms.
b.) Solicitation/Contract Form – AMS Form SF-33, "SOLICITATION, OFFER AND
AWARD,” with blocks 13 through 18 completed by the Offeror. The representative
who signs this form must be authorized to contractually bind the company providing
the offer.
c.) SIR Section K, Representations, Certifications and Other Statements of Offerors -
The Offeror shall complete all Representations, Certifications, and Other Statements
included in Section K of the model contract.
L.18. VOLUME 2, TECHNICAL
Volume 2 consists of Factor 2 (Sample Technical Problem), Factor 3 (Experience of
Personnel), Factor 4 (Management Approach), and Factor 5 (Past Experience and Past
Performance) as discussed below.
L.18.1. FACTOR 2, SAMPLE TECHNICAL PROBLEM
Factor 2, Sample Technical Problem. The Offeror’s proposal must describe their
answer to the Sample Technical Problem (Exhibit L-1). The Offeror’s proposal must
L-9
DTFAWA-09-R-00055
Amendment No. 0002
demonstrate a clear understanding of the scope and complexity of all of the
requirements described in the SOW as well as identification of any technical
performance risks or contingent events that could endanger satisfactory performance.
The Offeror’s proposal must demonstrate their level of SOA expertise; how system
engineering processes were used to achieve the results of their examples; what
methodologies were used to meet and manage their requirements; what problem(s)
were encountered; and how did risk come into consideration of for those problem(s);
what was done to mitigate risks; and to what extent the mitigation was effective.
Factor 2 must also include the following: the Offeror’s Technical Presentation Plan for
their presentation of the Sample Technical Problem. The Offeror’s Plan must include
the following: an outline of the presentation; Offeror’s approach to the Sample Technical
Problem; and any related visual aids and material. The Technical Problem is attached
hereto as Exhibit L-1. Offerors will have up to two (2) hours to make the presentation
and must allow up to one additional hour for FAA questions relating to the presentation.
L.18.2. FACTOR 3 (EXPERIENCE OF PERSONNEL), FACTOR 4
(MANAGEMENT APPROACH) AND FACTOR 5 (PAST
EXPERIENCE AND PAST PERFORMANCE).
a) Factor 3. Experience of Personnel must describe how the Offeror’s proposed
resumes meet the Education and Experience requirements and describe how the
education and experience set forth is relevant to the Functional Responsibility
requirements for the respective Labor Category as describe in Attachment J.4. The
Offerors may use their discretion in the number of resumes submitted, keeping in mind
the evaluation criteria in section M.12.3 and M.12.4. Offerors are are encouraged to
submit the resumes of those personnel who they intend to submit for approval under
paragraph I.8 after award.
b) Factor 4. Management Approach must describe the Offeror’s managerial approach
for accomplishing the work set forth in the SOW, such as describing how the Offeror
proposes to recruit and retain personnel over the Period of Performance and how the
Offeror will establish and maintain a good business relationship with the FAA,
stakeholders, and supporting contractors.
c) Factor 5. Past Experience and Past Performance must describe the Offeror’s Past
Experience on government contracts of similar scope and size and describe the
Offeror’s Past Performance by describing three references, preferably government
agencies, for which you have provided contract services within the past three years,
including:
(1) The Point of Contact (preferably the Contracting Officer),
(2) Contract Number,
(3) Period of Performance,
(4) A summary of the work performed,
(5) Whether you were the prime or subcontractor, and
(6) State: The contract type, labor categories, and fully burdened labor rates
charged.
L - 10
DTFAWA-09-R-00055
Amendment No. 0002
The Offeror may view the GFI on the SWIM website at www.swim.gov to assist in the
preparation of their offer.
L.18.3. SUBCONTRACTING PLAN
This solicitation is unrestricted and contains no set-aside provisions for small
businesses. However, the proposed solicitation incorporates the "Small Business and
Small Disadvantaged Business Subcontracting Plan" clause prescribed by Public Law
95-507. Each Offeror, if a large business, shall be required by the clause to negotiate
and establish percentage goals for the utilization of small business concerns, owned
and controlled by socially and economically disadvantaged individuals, as
subcontractors. The negotiated Plan will be incorporated into the prime contract.
The FAA is committed to assuring that maximum practicable opportunity is provided to
small, small disadvantaged and women-owned business concerns to participate in the
performance of this contract, consistent with efficient performance. A SB/SDB Plan is
required from all Offeror’s other than small businesses. The SB/SDB Plan will be
negotiated concurrently with price and other Proposals. The FAA expects that an
Offeror’s SB/SDB Plan shall reflect a commitment to assuring that small, small
disadvantaged and women-owned small business concerns are provided the maximum
practicable opportunity to participate as subcontractors in the performance of this
contract. The FAA has established the following minimum subcontracting goals for the
SWIM program:
At least 45% of total planned subcontract dollars to small businesses including:
At least 10% of total subcontract dollars to Small Disadvantaged Businesses
(SDBs)
At least 5% of total subcontract dollars to Women Owned Businesses (WOBs).
At least 3% of total subcontract dollars to Service Disabled Veterans Owned
Businesses.
In addition, the FAA encourages participation in the FAA Mentor-Protégé Program. See
specific clauses in SIR Section I. These clauses encourage firms to mentor SDBs and
WOBs during contract performance.
The Offeror shall submit a SB/SDB Plan, which includes:
A description of the Offeror’s subcontracting strategy.
How the above goals will be met.
A description of the Offeror’s approach, if elected, to participate in the FAA Mentor-
Protégé Program.
A description of the Offeror’s subcontracting strategies used in any previous similar
contracts, significant achievements, and how this Plan will build upon those earlier
a achievements.
Offerors may submit SWIM unique subcontracting plan or may make use of their
corporate or other Government approved commercial subcontracting plan. If an existing
L - 11
DTFAWA-09-R-00055
Amendment No. 0002
plan is submitted, it must meet the FAA minimum goals stated herein. The four bullets
above must be explicitly addressed in any corporate or other Government approved
commercial subcontracting plan that the Offeror may propose.
Failure to submit an acceptable subcontracting plan and/or correct deficiencies within
the time specified by the Contracting Officer shall make the Offeror ineligible for award.
L.19. VOLUME 3, COST
If the FAA notifies an Offeror that it is one of the down selected Offerors, Offerors must
submit their Volume 3 proposal by the due date set forth in Section L.7.
Volume 3 must contain:
a.) With reference to the SIR on the government provided excel worksheet:
(1) Completed Section B.2 Hourly Rate, by inserting Offeror’s proposed fully
burdened hourly rate for each Labor Category in the Base and each Option
Period table,
(2) Computed and completed Section B.2 Total Amount, by inserting the product
of the Labor Hours times the Hourly Rate for each Labor Category in the
Base and each Option Period table,
(3) Computed and completed Section B.2 TOTAL AMOUNT for CLINs, by
inserting the sum of the Total Amounts in the Base and each Option Period
table.
(4) Computed and completed Section B.3 part 1, Total Contract Ceiling or Not to
Exceed Contract Ceiling (NTE), by inserting the sum of the TOTAL AMOUNT
for CLINs for the Base and all Option Periods.
(5) Totals on Exhibit L-3 are cumulative and will change when the Excel
worksheets are completed.
b.) Compensation for Professional Employees:
The Government is concerned with the quality and stability of the work force Offeror will
employ on this contract. Professional compensation that is unrealistically low or not in
reasonable relationship to the Labor Categories may impair the Contractor's ability to
attract and retain competent professional employees. In addition, professional
compensation that is unrealistically low or not in reasonable relationship to the Labor
Categories may be viewed as evidence of failure to comprehend the complexity of the
contract requirements. In some instances, competition for service contracts may result
in lowering the compensation (salaries and fringe benefits) paid or furnished to
professional employees. This lowering can be detrimental to obtaining the quality of
professional services needed for adequate contract performance. Therefore, it is in the
Government's best interest that professional employees, as defined in 29 CFR 541,
receive proper and fair compensation.
(1) A Total Compensation Plan setting forth the salaries and fringe benefits it
intends to pay the professional employees who will work under the contract.
The Total Compensation Plan must describe how Offeror will ensure their
ability to provide uninterrupted high-quality work taking into account the work
to be performed, the differences in skills required, the complexity of various
disciplines, and the degree of professional job difficulty.
L - 12
DTFAWA-09-R-00055
Amendment No. 0002
(2) Information describing how Offerors reached their conclusions in the Total
Compensation Plan describing how the rates are realistic, fair, and
reasonable, pursuant to AMS Policy and Guidance 3.2.3.To that end, Offerors
are instructed to provide at least the following information:
i) A list of all subcontractors the Offeror anticipates using to perform any
part of this contract and description of the labor categories and work the
subcontractor will provide.
ii) Detailed price data for each labor category for the prime contractor
and each proposed subcontractor. The Offeror may choose to apply the
same rate to the subcontractors as for the prime Contractor. If not, then
the Offeror must provide this data for the prime contractor and for each
proposed subcontractor. Keep in mind that the contract will reflect only
one fully burdened labor rate for each labor category and the
government will allow the contractor to bill only that labor rate whether it
provides a prime contractor resource or a subcontractor resource for that
labor category. In all regards, the Offeror must include sufficient detail to
reflect the price reasonableness of the individual items that make up
your fully burdened labor rate.
iii) Any DCAA rate audit and the name of the DCAA contact regarding
that audit.
iv) If you are on a GSA Schedule, identify the Schedule then provide a
copy of your Labor Categories with fully burdened rates, Personnel
Qualifications by Category, and map the GSA categories to the Offer
categories.
v) As part of the data submitted, the Offeror shall provide a single fixed
fully burdened labor rate for each Labor Category included in Section B
showing the total sum (including salary, fringe benefits, overhead, G&A,
and profit) that the FAA will pay per hour for each Labor Category.
(3) Failure to comply with this provision may constitute sufficient cause to justify
rejection of a Proposal at any time in the evaluation.
c.) Travel may be burdened with an administrative charge reflecting the effort necessary
to book and administer travel costs, which must be a percentage of the total travel
costs allowed. The maximum charge for the base year period and each option year
period must be the administrative charge not to exceed the following:
Base Period Option 1 Option 2 Option 3 Option 4
d.) Financial Capability.
(1) Notwithstanding the evaluation methodology outlined in this SIR, the contracting
Officer must make a determination that an Offeror is a responsible Offeror. In
reaching this determination, the Contracting Officer will consider whether a
prospective contractor has:
i) Adequate financial resources to perform the contract, or the ability to obtain
those resources;
L - 13
DTFAWA-09-R-00055
Amendment No. 0002
ii) Ability to provide the level of effort contemplated by the contract, taking
into consideration all other business commitments;
iii) A satisfactory record of integrity and business ethics;
iv) A satisfactory performance record;
v) The necessary organization, experience, accounting and operational
controls; and
vi) Is otherwise qualified and eligible to receive an award under applicable
laws and regulations.
(2) To facilitate the Contracting Officer’s responsibility determination, the Offerors
must submit at least the following information in Volume II:
i) A description of the Offeror’s financial capability to fund and perform a
contract of this size and duration.
ii) Information that describes the book value of Offeror’s company and that of
your team members.
iii) A description of all legal actions involving Offeror or Subcontractors under
Federal Government contracts within the past 3 years and a description of
any impending legal actions involving Federal Government Contracts. The
descriptions must include, but is not limited to: Requests for Equitable
Adjustments (formal or informal), pending claims, ongoing claims (formal or
informal) in excess of $5M, pending cure notices, ongoing cure notices,
Terminations for Convenience, and Terminations for Default.
L.20. VOLUME 4, TASK ORDER 0001 PROPOSAL
If the FAA notifies an Offeror that it is one of the down selected Offeror(s), the Offeror(s)
must submit their Volume 4 proposal by the due date set forth in Section L.7.
VOLUME 4 is not part of the award evaluation process. The Government intends on
awarding the first Task Order at the time of the contract award and expects the
Contractor to be to be ready, willing, and able to commence work on the date of award.
Volume 4 must contain:
Part 1: The Resume’s of personnel proposed to work on the Task Order and an
explanation of the Task Order Labor Mix. Proposed personnel must meet the
qualifications set forth in Section J.4. Any contractor personnel approved to work on
this Task Order will be listed in Attachment J.7.
Part 2: The SWIM PO’s level of effort estimates for each requirement is set forth
in Attachment J.6. The Offeror must provide a price proposal for the Base Period Task
Order. The Task Order proposal must include a schedule with Labor Categories and
Labor Rates and totals. For task planning, assume that the maximum amounts
available under CLINs 0008 and 0009 are applicable.
The Offeror’s TO proposal will be reviewed for appropriateness of the proposed
effort. The SWIM PO may revise the Base Period Task Order prior to its issuance or
after discussions with the potential contract awardee.
L - 14
DTFAWA-09-R-00055
Amendment No. 0002
The Offeror may view the GFI on the SWIM website at www.swim.gov to assist in the
preparation of their offer.
[Relocated Subcontracting Plan to 18.3]
L.21. INSTRUCTIONS FOR ORAL PRESENTATION FOR SAMPLE TECHNICAL
PROBLEM
L.21.1. BACKGROUND
The purpose of the oral presentation is to assess the Offeror’s understanding and
technical approach to the Sample Technical Problem. Exhibit L–1. Offerors shall make
a detailed presentation addressing the technical criteria listed in the Sample Technical
Problem and consistent with the applicable requirements of this SIR. Presentations
shall include a discussion of Offeror’s approach to scheduling the tasks to accomplish
them in a timely and efficient manner.
L.21.2. LOCATION AND TIME OF ORAL PRESENTATIONS
The FAA will hold the Technical Presentations at FAA Headquarters, 800 Independence
Ave. S.W., Washington, DC 20591 or some other Washington DC area location
designated by the CO. Individual Offerors will be advised of the exact location, as
applicable. Times to be announced.
L.21.3. CONDUCT OF THE PRESENTATIONS
Offerors will have up to two (2) hours to make the presentation and must allow up to
one (1) additional hour for FAA questions relating to the oral presentation. Offeror’s
may arrive up to ½ hour early to set up for their presentation and are reminded that it is
their responsibility to bring any equipment necessary to support the oral presentation.
L.21.4. ORAL PRESENTATION CONSTRAINTS.
Offerors are instructed that only substantive responses to the Sample Technical
Problem will be considered. Offerors are reminded of AMS Provision 3.2.2.3-11,
Unnecessarily Elaborate Submittals (July 2004).
Presentation of new material or material outside of the Technical Presentation Plan will
not be evaluated or considered.
Offerors shall not discuss cost or price during the presentation or in the question and
answer period.
L.21.5. FORM OF PRESENTATION.
Offerors may use visual aids, such as, Power Point, for the presentation and shall
provide any equipment necessary. Offerors must advise the FAA of any plans in this
regard to ensure that the location can support their presentation.
The Government reserves the right to video tape or record the sessions.
L - 15
DTFAWA-09-R-00055
Amendment No. 0002
L.22. EXHIBIT L-1 SAMPLE TECHNICAL PROBLEM
SWIM – Systems Engineering and Business Services Support
L.22.1. PROBLEM STATEMENT
Using the scenario presented in Sections L.22.1(Introduction) and L.22.2 (Background),
Offerors must address all of the areas in Section L.22.2 (Guidance to Offerors) including
all subsections and subparts thereunder (i.e., subsections L.22.2.1and L.22.2.2 and
subparts L.22.2.2.a through h).
L.22.1.1. Introduction
SWIM provides policies and standards to support data management, along with the
mechanisms (i.e., commercial software) for the core services needed to publish data to
the network, retrieve it, secure its integrity, and control its access and use. The basic
mechanisms provided by SWIM that enable integration are referred to as core services.
The SWIM core services are interface management, messaging, enterprise service
management and security.
The SWIM Program promotes the application of service-oriented architecture (SOA)
and information exchange technologies to improve the speed, efficiency, and quality of
distributed decision making. The SWIM Program is an integral part of the NAS
Enterprise Architecture roadmap. It enables safe and secure interaction with other
members of the decision-making community including other agencies, air navigation
service providers, and airspace users.
Systems engineers support the SWIM Program through the development of concept
documents, functional and service-level requirements, architecture documents, policies,
and standards. These same engineers conduct training, perform coaching, examine
artifacts, attend reviews, and witness test and/or demonstration events to determine
proper implementation of concepts and compliance with requirements, architectural
constraints, policies, and standards.
In future segments, it is anticipated that the SWIM Program will provide infrastructure
functionality with no business services included in the investment analysis business
case. As part of the investment analysis for these future segments, the SWIM Program
must validate that the investment will be cost beneficial based solely on providing
infrastructure functionality to the NAS.
L.22.1.2. Background
In this sample problem, a business unit has proposed the adding to the NAS enterprise
a service supporting a NAS mission. Concurrent with this business unit activity the
SWIM program is developing the documentation for SWIM Segment N.
L - 16
DTFAWA-09-R-00055
Amendment No. 0002
L.22.2. USING GUIDANCE TO OFFERORS
The Offeror shall describe its technical and management approach to providing the
service described in Sections L.22.1(Introduction) and L.22.2 (Background) above. The
Offeror’s response shall supplement and apply the written proposal. It is not necessary
to repeat material from the written proposal; Offerors may emphasize or reference that
material as needed. The Offeror’s response shall provide a description of the
capabilities the Offeror can provide (i.e., systems engineering support), articulate the
Offeror’s knowledge and experience in systems engineering, and describe how the
Offeror executes its knowledge and experience. The Offeror shall clearly articulate all
assumptions and constraints influencing major elements of its response to this sample
problem.
L.22.2.1. Structure of Response
The Offeror shall structure its response consistent with the instructions in Section L.
L.22.2.2. Required Elements of Technical Response
The Offeror’s response shall discuss methodologies used by their team, problem
resolution strategy, risk identification, and mitigation processes to address the following
technical elements:
a) Operational Concept - Describe your process and provide an example
where you identified or assessed the scope and impact of a proposed SOA
service on existing business or operational functions and core services.
b) Functional Requirements and Components - Describe your process and
provide an example where you transformed an operational concept into service-
level requirements (e.g., functional, interface, performance) and subsequently
into requirements sufficient to support service design activities.
c) Architectural Analysis and Development – Describe your process and
provide an example where you performed an analysis of system requirements
and developed the applicable physical, data, and enterprise architectural
elements of the Department of Defense Architecture Framework.
d) SOA Infrastructure – Describe your process and provide an example
where you implemented or participated in the implementation of SOA Core
Services.
e) Governance – Describe your process and provide an example where you
implemented or participated in the implementation of IT and SOA governance.
L - 17
DTFAWA-09-R-00055
Amendment No. 0002
f) Enterprise Information Management (EIM) – Describe your process and
provide an example where you implemented or participated in the
implementation of EIM.
g) Infrastructure Support – Describe your process and provide an example
where you implemented or participated in the implementation of SOA
infrastructure support.
h) Development Support – Describe your process and provide an example
where you implemented or participated in the implementation of SOA
development support.
i) Investment Analysis – Describe your process for determining benefits
related to a SOA implementation.
L - 18
DTFAWA-09-R-00055
Amendment No. 0002
L.23. EXHIBIT L-2 PAST PERFORMANCE QUESTIONNAIRE
SWIM – Systems Engineering and Business Services Support
PART 1 – TO BE COMPLETED BY OFFEROR
Instructions to the Offeror: The Offeror shall cite, and briefly describe at least three
(3) contracts (Government or non-Government) they have performed within the past 3
years that are of similar size, complexity, and scope as the SWIM effort. The Offeror
will then transmit the completed Part 1 and a blank Part 2 to the Offeror’s client
organization’s Contracting Officer or Contacting Officer’s Technical Representative.
The Offeror will request its client organization to complete Part 2 and return the
completed Parts 1 and 2 by mail or facsimile directly to:
Federal Aviation Administration
Dennis L. Scanlon, Contracting Officer
AJA-472, Room 506
800 Independence Ave.
Washington, DC 20591
Telephone (202) 267-9422
Fax (202) 493-5057
1. Contract Number:____________________
2. Contractor (Name, Address and Zip Code):
3. Type of Contract: Negotiated ___; Sealed Bid ___; Fixed Price ___; Cost
Reimbursement___;
Other (Specify): ______________________
4. Complexity of Work: Difficult ___ Routine ___
5. Brief Description and Location of Work:
6. Contract Amount: _______________ Status: Active: ___ Complete: ___
7. Date of Award: ________ Contract Completion Date (Including Extensions):
_____________
8. Type and Extent of Subcontracting:
9. Name, Address and Telephone Number of the Contracting Officer or Contracting
Officer’s Technical Representative (COTR) of the client organization:
L - 19
DTFAWA-09-R-00055
Amendment No. 0002
PART 2 – TO BE COMPLETED BY OFFEROR’S CLIENT ORGANIZATION
Instructions to the receiving Contracting Officer or Contracting Officer’s
Technical Representative: The organization (the “Offeror”) forwarding this Past
Performance Questionnaire is competing for a contract award with the Federal Aviation
Administration (FAA) – specifically, providing support to the FAA’s System Wide
Information Management Program (SWIM). A separate record must be completed for
all contracts awarded to the competing Offeror within the past three (3) years. It is
requested that the Offeror’s client organization review the information in Part 1, make
corrections if appropriate, and then answer the questions in Part 2. The questions are
written in such a way that only brief responses are required. However, the FAA would
appreciate additional comments where Offeror’s client feels that a check-off grade does
not adequately address the circumstances of contract performance. Please transmit the
completed questionnaire directly to the address below (not back to the Offeror) at the
earliest convenience:
Federal Aviation Administration
Dennis L. Scanlon, Contracting Officer
AJA-472, Room 506
800 Independence Ave.
Washington, DC 20591
Telephone (202) 267-9422
Fax (202) 493-5057
1. Corrections, additions, deletions to the information provided in Part 1. (Annotate in
Part 1 or attach additional pages if required.)
2. To what extent did the Contractor adhere to contract delivery schedules?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
L - 20
DTFAWA-09-R-00055
Amendment No. 0002
3. To what extent did the Contractor submit required reports and documentation in a
timely manner?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
4. To what extent were the Contractor’s reports and documentation accurate and
complete?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
5. To what extent was the Contractor able to solve contract performance problems
without extensive guidance from customer counterparts?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
6. To what extent did the Contractor display initiative in meeting requirements?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
7. Did the Contractor commit adequate resources in timely fashion to the contract to
meet the requirement and successfully solve problems?
L - 21
DTFAWA-09-R-00055
Amendment No. 0002
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
8. To what extent did the Contractor submit change orders and other required
Proposals in a timely manner?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
9. To what extent did the Contractor respond positively and promptly to technical
directions, contract change orders, etc.?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
10. To what extent was the Contractor’s document maintenance and problem
tracking/reporting documentation timely, accurate, and of appropriate content?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
11. To what extent was the Contractor effective in interfacing with the customer’s staff?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
L - 22
DTFAWA-09-R-00055
Amendment No. 0002
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
12. Has this contract been partially or completely terminated for default or
convenience?
{ } Yes { } Default { } Convenience
{ } No
If yes, explain (e.g., inability to meet cost, performance, or delivery schedules).
13. Are there any pending terminations?
{ } Yes { } No
If yes, explain and indicate the status.
14. How effective has the Contractor been in identifying user and system
shortcomings?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
15. To what extent was the maintenance and problem reporting/tracking documentation
produced by the Contractor’s efforts satisfactory to the users?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
L - 23
DTFAWA-09-R-00055
Amendment No. 0002
16. To what extent did the Contractor provide timely technical assistance when
responding to problems encountered?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
17. To what extend did the Contractor meet the proposed cost estimates?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
18. To what extend did the system delivered by the Contractor meet your operational
requirements?
{ } Considerably surpassed minimum requirements
{ } Exceeded minimum requirements
{ } Met minimum requirements
{ } Less than minimum requirements
Comment:
19. NARRATIVE SUMMARY - Use this section to for additional information not already
provided.
L - 24
DTFAWA-09-R-00055
Amendment No. 0002
L.24. EXHIBIT L-3 WORKSHEET FOR SECTION B
SWIM – Systems Engineering and Business Services Support
NOTE: Totals on Exhibit L-3 are cumulative and will change when the Excel
worksheets are completed.
**SEE EXCEL WORKSHEET ATTACHED TO SIR**
L - 25
DTFAWA-09-R-00055
Amendment No. 0002
PART IV - SECTION M
EVALUATION FACTORS FOR AWARD
M.1. CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE
(DECEMBER 2005)
This screening information request (SIR) or contract, as applicable, incorporates
by reference the provisions or clauses listed below with the same force and effect
as if they were given in full text. Upon request, the Contracting Officer will make
the full text available, or Offerors and contractors may obtain the full text via
Internet at: http://conwrite.faa.gov (on this web page, select "Search and View
Clauses").source selection process.
3.2.4-31 Evaluation of Options (April 1996)
M.2. AWARD SELECTION
This is a Best Value source selection conducted in accordance with the FAA
Acquisition Management System (AMS). The FAA will make Award to the
Offeror whose proposal is evaluated to represent the Best Value to the FAA.
Best Value means a solution that is the most advantageous to the FAA, based on
the evaluation of Technical and Cost/Price Factors specified by the FAA. This
approach provides the opportunity for trade-offs between Technical and
Cost/Price factors, and does not require the FAA to make an award to an Offeror
submitting the highest rated technical solution or to an Offeror submitting the
lowest Cost/Price, although award may be to either of those Offerors. Offerors
will receive an adjectival rating for Technical Factors derived from evaluation of
the following Subfactors: Technical and Business, Experience of Personnel,
Management Approach, and Past Experience and Past Performance. For the
Cost/Price evaluation, the FAA will consider the total Cost/Price, Total
Compensation Plan, and reasonableness, completeness, realism and
consistency/traceability of each Offeror’s Cost/Price.
The Source Selection Official (SSO) will consider the Source Selection
Evaluation Board’s recommendation and use his or her best judgment to arrive at
a Best Value determination. The FAA intends to select one contractor for the
award.
M.3. DOWNSELECT DECISIONS
If more than five offers are received, the FAA intends to make a Down Select
decision prior to making a contract award decision. The FAA will base its down
select decision upon evaluation of Volume 1, Factor 1 (Down Select Criteria), by
choosing the proposals for final evaluation for award. The rated proposals will
represent the FAA’s determination of which Offerors are most likely to receive the
award. There are no maximum number of proposals that the FAA will down
select.
If at any point during the evaluation process, the FAA determines that a particular
Offeror does not have a reasonable chance of receiving this award, the FAA may
M-1
DTFAWA-09-R-00055
Amendment No. 0002
eliminate that particular Offeror from further consideration. The Contracting
Officer will notify the Offeror officially in writing that the Offeror has been
eliminated from further consideration.
M.4. SUBCONTRACTING PLAN
The Subcontracting Plan will be evaluated based on the Offeror’s demonstrated
commitment to assuring that small, small disadvantaged, women-owned small
business, and service disabled veterans owned concerns are provided the
maximum practicable opportunity to participate in the SWIM program (AMS
Clauses 3.6.1-3, 3.6.1-4, 3.6.1-9, and 3.6.1-10) . The evaluation will consider the
plausibility of the subcontracting goals.
M.5. IMPORTANCE OF SUBCONTRACTING PLAN
The Subcontracting Plan will be evaluated on a pass or fail basis. Failure to
submit an acceptable subcontracting plan or to correct deficiencies within a time
specified by the Contracting Officer shall make an Offeror ineligible for award.
M.6. ELIGIBILITY FOR AWARD
The Offeror must be determined responsible by the Contracting Officer in
accordance with AMS. (See paragraph L.16) To be eligible for award, the
Offeror’s team must also be technically and financially capable of performing the
magnitude and scope of the work.
M.7. COMMUNICATIONS AND DISCUSSIONS WITH OFFEROR’S
In evaluating the proposals, the FAA may conduct written or oral communications
with any or all Offerors. Additionally, the FAA reserves the right to conduct
discussions and negotiations with any or all Offerors, and to request proposal
updates, as the situation warrants. Discussions with one or more Offerors do not
require discussions with all Offerors.
M.8. AWARD ON INITIAL OFFERS
Once Down Select has been made and the proposals are received, the FAA
reserves the right to award a contract immediately following the conclusion of the
evaluations, without discussions or negotiations with any Offeror. Therefore, it is
critical that each proposal be fully responsive to this SIR and its provisions.
M.9. EVALUATION PROCESS – VOLUMES 1, 2, AND 3
The evaluation process will occur in three phases; Review of Submittals, Down
Selection, and Final Evaluation.
Upon receipt of proposals, the FAA will review each submittal for completeness
in addressing all SIR requirements, including review to ensure that the
information provided is sufficient to allow award without the need to obtain further
information from an Offeror and that the submittal is sufficient for complete
M-2
DTFAWA-09-R-00055
Amendment No. 0002
evaluation. Failure to submit a complete proposal may result in disqualification of
the Offeror from further consideration.
The Down Selection phase will evaluate the remaining offers submitted to
determine the Offerors most likely to receive award based on their responses to
the Down Select Criteria in accordance with Section M.9. No limit is set upon the
number of Offerors who may be down selected.
The FAA will evaluate the Down Select Criteria for indications that they
demonstrate Offeror’s approach and understanding of the requirements. All
Down Select subCriteria relate the technical requirements of the SOW and
evaluation thereof is expected to provide the Evaluators with a clear picture of
the Offerors most likely to receive award. The FAA will not consider Cost/Price
during the Down Selection phase. As soon as practical after Down Select
unsuccessful Offerors will be notified and offered the opportunity to debrief.
The Final Evaluation Phase will consist of evaluating submittals of Volumes 2
and 3, in accordance with Sections M.9 and M.10.
Based on individual evaluation of each offer, evaluators will derive an adjectival
rating for each of the Factors as set forth herein. From that adjectival rating, each
Offer will receive an overall adjectival rating, based on the results of the Factor
evaluations. Evaluators will apply independent judgment during the evaluation to
derive each overall adjectival rating.
The FAA reminds Offerors that all information provided in the proposals and
gathered during this acquisition clarifications, and any discussions serves as the
basis for the evaluation. Offerors should consider the evaluation factors in this
Section very carefully when preparing responses.
M.10. VOLUMES: ORDER OF IMPORTANCE
Factor 1 is the most important factor. Factor 2 and Oral Presentation will not be
evaluated separately from Factor 1, but will be used by the evaluators as
additional information whenever relevant to the other Factors. Factor 1 is more
important than Factors 3, 4 and 5 combined. The Factors and Subfactors will be
evaluated according to the criteria set forth in Section M. The weight attributed to
each subfactor is described in the section pertaining to each factor.
a.) Volume I contains Factor 1 Technical and Business Approach.
b.) Volume 2 contains Factors 2, 3, 4, and 5 as follows:
(1) Factor 2 – Sample Technical Problem
(2) Factor 3 – Experience of Personnel;
(3) Factor 4 - Management Approach; and
M-3
DTFAWA-09-R-00055
Amendment No. 0002
(4) Factor 5 - Past Experience and Past Performance.
c.) Volume 3 contains the Cost/Price Proposal.
The FAA does not assign a weight to Volume 3 (Cost/Price). As the relative
technical evaluations of the Offeror’s approach equivalency or are equivalent,
Volume 3 will become more important in the determination of Best Value.
Volume 3 will be considered in performing award selection, as set forth in section
M.2.
d.) Volume 4 contains the Task Order 0001.Volume 4 is not part of the award
evaluation process. The Government intends on awarding the first Task Order
at the time of the contract award and expects the Contractor to be ready,
willing, and able to commence work on the date of award.
M.11. VOLUME 1 TECHNICAL VOLUME – EVALUATION FACTORS
M.11.1. Factor 1 – Technical and Business Approaches:
Within Volume 1, the subfactors for Factor 1 are listed below in
descending order of importance:
M.9.1.1. Subfactor A (Down Select Subfactor). Technical
Approach for SOW Requirement 1. Degree to which the Offeror’s
proposal demonstrates their understanding of the work and has the
ability and knowledge to fulfill the system engineering SOW
requirements, including the knowledge of salient operational
procedures, inherent problems, ideas for solutions, and the
capability to perform system engineering processes, such as
knowledge standard systems engineering processes and
procedures to include, systems performance modeling and
measurement, change impact assessments, life cycle
requirements, quality, safety, security, maintainability, reliability,
integrity of analyses, schedule considerations, requirements
analysis, and trade studies, product assessment, prototyping and
test and evaluations.
M.9.1.2. Subfactor B (Down Select Subfactor). Technical
Approach for SOW Requirements 2 through 5. Degree to which the
Offeror’s proposal demonstrates their understanding of the work
and has the ability and knowledge to fulfill these technical SOW
requirements, including the knowledge of salient operational
procedures, inherent problems, ideas for solutions, and the
capability to perform the technical requirements, such as
requirements architecture documentation development,
governance, EIM and SWIM Integration.
M-4
DTFAWA-09-R-00055
Amendment No. 0002
M.9.1.3. Subfactor C (Down Select Subfactor). Technical
Approach for SOW Requirement 6. Degree to which the Offeror’s
proposal demonstrates their understanding of the work and has the
ability and knowledge to fulfill the SIP oversight SOW requirements,
including the knowledge of salient operational procedures, inherent
problems, ideas for solutions, and the capability to perform the
technical requirements, such as PLAs, EVM, metrics, design and
program reviews, SLAs, FTI capacity and capacity development,
testing, deployment, operations and maintenance.
M.9.1.4. Subfactor D (Down Select Subfactor). Business
Approach for SOW Requirement 7. Degree to which the Offeror’s
proposal demonstrates their understanding of the work and has the
ability and knowledge to fulfill the program control SOW
requirements, including the knowledge of salient operational
procedures, inherent problems, ideas for solutions, and the
capability to perform business related requirements, such as
knowledge of risk management, EVM documentation, performance
metrics, financial management and investment analysis.
M.9.1.5. Subfactor E (Down Select Subfactor). Program
Approach for SOW Requirement 8. Degree to which the Offeror’s
proposal demonstrates their understanding of the work and has the
ability and knowledge to fulfill the program management support
SOW requirements, including the knowledge of salient operational
procedures, inherent problems, ideas for solutions, and the
capability to perform overall program management support
requirements, such as knowledge program communications with
various governmental entities and non-governmental stakeholders,
program plans, investment analysis and support program manager
at various meetings and conferences.
M.12. VOLUME 2 TECHNICAL
M.12.1. Within Volume 2, Factor 2 has no specific weight. An Offeror’s
response to Factors 1 and 2 may be used to corroborate evaluation of
the other technical factors as relevant. With the exception of Factor 2,
Factors 3, 4, and 5 are listed in descending order of importance:
M.12.2. Factor 2. Sample Technical Problem.
Degree to which the Offeror’s answer to the Sample Technical Problem
(Exhibit L-1) and demonstrates a clear understanding of the scope and
complexity of all of the requirements described in the SOW as well as
identification of any technical performance risks or contingent events that
could endanger satisfactory performance. Degree to which the Offeror’s
proposal demonstrates the level of SOA expertise; how system
engineering processes were used to achieve the results of their examples;
M-5
DTFAWA-09-R-00055
Amendment No. 0002
what methodologies were used to meet and manage their requirements;
what problem(s) were encountered; and how did risk come into
consideration of for those problem(s); what was done to mitigate risks; and
to what extent the mitigation was effective.
M.12.3. Factor 3. Experience of Personnel.
Degree to which the proposed resumes demonstrate that the proposed
personnel meet the education and experience requirements in J.4
Personnel Qualifications and demonstrates that the education and
experience is relevant to the Functional Responsibility requirements for
each specified labor category.
M.12.4. Factor 4. Management Approach.
Degree to which the Offeror’s proposal demonstrates an integrated and
effective managerial approach to ensure Offeror’s employee performance
with a feedback mechanism for input by the FAA. Degree to which the
proposal demonstrates an integrated and effective managerial approach
for successfully accomplishing the work to be performed under this SIR.
Examples, without limitation, are demonstrating how the Offeror proposes
to manage fluctuations in work levels due to rapid changes in staffing
requirements, recruiting and retaining qualified personnel so as to
maintain staffing levels throughout the contract performance period, and
establishing and maintaining appropriate and good business relationships
with FAA, all stakeholders, and supporting contractors
M.12.5. Factor 5. Past Experience and Past Performance.
Within Factor 5, the two subfactors are equal in importance.
M.12.5.1. Subfactor A. Past Experience.
The Offeror’s proposal must describe their past experience on government
contracts is similar scope, size, (i.e., type of labor categories and
magnitude of level of effort) and complexity to the SOW requirements of
the SIR using three references, preferably government agencies, for
which contract services were provided within the past three years,
including:
1. The Point of Contact (preferably the Contracting Officer),
2. Contract Number,
3. Period of Performance,
4. A summary of the work performed,
5. Whether you were the prime or subcontractor, and
6. State: The contract type, labor categories, and fully burdened
labor rates charged.
M-6
DTFAWA-09-R-00055
Amendment No. 0002
M.12.5.2. Subfactor B. Past Performance. The degree to which the
Offeror’s past performance, reflected in the FAA review of
previous work via the past performance questionnaire, reflects
quality of performance and quality of personnel.
M.12.6. SUBCONTRACTING PLAN
The FAA will evaluate the responsibility of the offerors’ proposed subcontracting
plans in accordance with the standards listed in AMS clause 3.6.1-4. If the
apparently successful offeror fails to propose the required subcontracting goals
and, prior to award, is unable to remedy any deficiencies in their plan regarding
these goals or is unable to provide to FAA sufficient and acceptable reasoning as
to their inability to achieve the goals, the offeror shall be ineligible for award.
The subcontracting plan will receive an adjectival rating of pass or fail. This
evaluation factor is not applicable to small businesses.
Proposed goals meet or exceed FAA established subcontracting
PASS
goals
Offeror fails to propose goals; proposed goals do not meet FAA
FAIL
established subcontracting goals
M.13. VOLUME 3, COST/PRICE EVALUATION
The Government will evaluate the Cost/Price submitted in Offers to determine if
they are realistic, fair, and reasonable, pursuant to AMS Policy and Guidance.
The FAA may use cost/price analysis to evaluate the cost estimates or prices,
not only to determine whether, or not, they are reasonable, but also to determine
if the Offeror understands the work and has the ability to perform the contract.
The FAA will evaluate the Base and Option periods, including the Administrative
Fee applicable to Travel, together to establish an Offeror’s Cost/Price; however,
doing so does not bind the FAA to exercise any Option.
Also, Offerors’ total costs will be evaluated against the FAA’s Independent
Government Costs Estimate (IGCE) based on the maximum labor hours possible
in each labor category as stated in Section B of this SIR.
The evaluators will evaluate Cost/Price for:
1.) Reasonableness – A cost is reasonable if, in its nature and amount, it does
not exceed that would be incurred by a prudent person conducting competitive
business.
2.) Completeness – Responsiveness in addressing all SIR requirements--review
of the proposal to ensure that the information provided is sufficient to allow a
M-7
DTFAWA-09-R-00055
Amendment No. 0002
complete analysis and evaluation of the costs or prices delineated in Section B
and includes all information and exhibits required by Section L.
3.) Realism – How well the Offeror’s proposed costs are realistic for the work
performed; reflect a clear understanding of the requirements; and are
consistent with the various elements in the Offeror’s technical proposal.
4.) Consistency/Traceability – How well the Offeror’s proposed costs and prices
match the labor categories proposed, the method of accomplishing the work
described in the technical capabilities proposal, and the Offeror’s past
experience for similar work.
M.14. VOLUME 4, TASK ORDER 0001 PROPOSAL
VOLUME 4 IS NOT PART OF THE EVALUATION TO DETERMINE BEST
VALUE FOR AWARD.
Volume 4 will be evaluated after the award decision for reasonableness and
appropriateness of the proposed Labor Category Mix and Personnel. The Task
Order must be in line with the awardee’s contract. It is the Government’s
intention to award Task Order 0001 at the same time as the IDIQ award, and the
contractor must be prepared to commence work on the date of award.
M.15. EVALUATION OF RISK
Implicit in the evaluation of all proposal volumes is an assessment of risks
inherent in the proposal. Risk is defined as the cumulative effect of the
weaknesses identified during the evaluation. Risk evaluation will assess the
likelihood that the Offeror's proposed solutions will successfully meet the FAA’s
requirements.
The Degree of Risk assigned will be Low, Moderate or High as set forth below:
Risk Description
Low Proposal meets requirements with only minor changes
required.
Moderate Proposal is suitable with some modifications.
High Proposal requires significant modifications to be suitable.
a.) Risks identified within any aspect of an Offeror's proposal, and within any of
the evaluation factors, will be analyzed as to their potential impact on the
program.
b.) Risks identified due to inconsistencies and discrepancies within the Offeror's
proposal will be considered, as will risks that pertain to unsubstantiated
statements made by the Offeror in their proposal.
c.) The FAA will evaluate the Total Compensation Plan and assign a Degree of
Risk to it to assure that it reflects a sound management approach and
understanding of the contract requirements.
(1) Evaluation of the Total Compensation Plan will consider whether the
Offeror has demonstrated:
M-8
DTFAWA-09-R-00055
Amendment No. 0002
i) The capability of the proposed compensation structure to obtain and
keep suitably qualified personnel to meet mission objectives.
ii) The ability to provide uninterrupted high-quality work in terms of the
impact of compensation upon recruiting and retention.
iii) The ability of the Offeror to maintain program continuity,
uninterrupted high-quality work, and availability of required
competent professional service employees.
(2) Unusually low compensation for the professional work required may
indicate lack of sound management judgment or lack of understanding of
the requirement and may result in assignment of a higher Degree of Risk
or serve as grounds for rejection of an Offer.
M.16. RESPONSIBILITY DETERMINATION
a.) The Contracting Officer must make a determination whether an Offeror is a
responsible Offeror. Failure of an Offeror to demonstrate financial
responsibility may result in assignment of a higher Degree of Risk or serve as
grounds for rejection of an Offer. In reaching this determination, the
Contracting Officer will consider whether a prospective contractor has:
(1) Adequate financial resources to perform the contract, or the ability to
obtain those resources;
(2) Ability to provide the level of effort contemplated by the contract,
taking into consideration all other business commitments;
(3) A satisfactory record of integrity and business ethics;
(4) A satisfactory performance record;
(5) The necessary organization, experience, accounting and operational
controls; and
(6) Is otherwise qualified and eligible to receive an award under
applicable laws and regulations.
M.17. RATING OF OFFERS
M.17.1. FACTORS 1, [DELETED], 3, AND 4
Factor 1 (Technical and Business Approach); Factor 3 (Experience of
Personnel); and Factor 4 (Management Approach), including the Subfactors, will
be assigned an adjectival rating, as follows:
M-9
DTFAWA-09-R-00055
Amendment No. 0002
Adjectival Rating
The Offeror’s response to the topics is comprehensive
and demonstrates a thorough knowledge and
understanding of the full range of requirements and
work efforts, to include but not limited to, SOA and
related systems engineering disciplines; FAA and best
practice management methodologies and techniques;
Excellent FAA systems and related systems; formal education
and/or experience of proposed personnel; and a
systematic approach to the full life cycle for IT
investments to maximize the value and assess the
acquisition’s risks. Few, if any, areas for improvement
can be cited. The combined impact of the strengths far
outweighs the combined impact of the weaknesses.
The Offeror’s response to the topics is fully acceptable
and demonstrates a strong knowledge and
understanding of the full range of requirements and
work, to include but not limited to, SOA and related
systems engineering disciplines; FAA and best practice
management methodologies and techniques; FAA
Good systems and related systems; formal education and/or
experience of proposed personnel; and a systematic
approach to the full life cycle for IT investments to
maximize the value and assess the acquisition’s risks.
A few minor weaknesses are noted. The combined
impact of the strengths outweighs the combined impact
of the weaknesses.
The Offeror’s response to the topics is acceptable and
demonstrates an adequate knowledge and
understanding of the full range of requirements and
work efforts, to include but not limited to, SOA and
related systems engineering disciplines; FAA and best
practice management methodologies and techniques;
Satisfactory FAA systems and related systems; formal education
and/or experience of proposed personnel; and a
systematic approach to the full life cycle for IT
investments to maximize the value and assess the
acquisition’s risks. Although there may be some
weaknesses and areas in need of improvement, these
are offset by strengths in other areas.
M - 10
DTFAWA-09-R-00055
Amendment No. 0002
Adjectival Rating
The Offeror’s response does not respond adequately to
the full range of requirements and work efforts, to
include but not limited to, SOA and related systems
engineering disciplines; FAA and best practice
management methodologies and techniques; FAA
systems and related systems; formal education and/or
Marginal experience of proposed personnel; and a systematic
approach to the full life cycle for IT investments to
maximize the value and assess the acquisition’s risks.
Offeror’s response is deficient in several areas with no
corresponding offset in other areas. The combined
impact of the weaknesses outweighs the combined
impact of the strengths.
The Offeror’s response to the topic fails to demonstrate
a satisfactory understanding of the requirements and
work efforts, to include but not limited to, SOA and
related systems engineering disciplines; FAA and best
practice management methodologies and techniques;
FAA systems and related systems; formal education
and/or experience of proposed personnel; and a
systematic approach to the full life cycle for IT
investments to maximize the value and assess the
acquisition’s risks. The proposal does not demonstrate
the capability to support the FAA’s needs. The
Unsatisfactory combined impact of the weaknesses far outweighs the
combined impact of the strengths.
M.17.2. FACTOR 5. PAST EXPERIENCE AND PAST PERFORMANCE
Factor 5, including the Subfactors will be assigned an adjectival rating, as
follows:
M - 11
DTFAWA-09-R-00055
Amendment No. 0002
Adjectival
Rating
Outstanding The Offeror’s records of past experience and past
performance have specific and direct relevancy to the
Section C, SOW, requirements, especially the Offeror’s
extensive relevant experience in SOA technology and
thorough knowledge of FAA systems, and that
outstanding performance was achieved. The Offeror’s
past performance/past experience records suggests a
superior quality performance will be delivered.
Very Good The Offeror’s records of past experience and past
performance have specific and direct relevancy to the
Section C, SOW, requirements, especially the Offeror’s
strong relevant experience in SOA technology and sound
knowledge of FAA systems, and that highly successful
performance was achieved. The Offeror’s past
performance/past experience records suggest a high
quality performance will be delivered.
Satisfactory The Offeror’s records of past experience and past
performance have specific and direct relevancy to the
Section C, SOW, requirements, especially the Offeror’s
relevant experience in SOA technology and familiar
knowledge of FAA systems, and that satisfactory
performance was achieved. The Offeror’s past
performance/past experience records suggests
satisfactory quality performance will be delivered.
Poor The Offeror’s records of past experience and past
performance have limited relevancy to the Section C,
SOW, requirements, especially the Offeror’s limited
relevant experience in SOA technology and limited
knowledge of FAA systems. The Offeror is not likely to
meet the program performance requirements.
Unsatisfactory The Offeror’s records of past experience and past
performance have minimal or no relevancy to the Section
C, SOW, requirements, especially the Offeror’s lack of
relevant experience in SOA technology and limited or no
knowledge of FAA systems. The Offeror’s past
performance achieved was satisfactory or below. The
Offeror is not highly unlikely to meet the program
performance requirements.
M - 12
DTFAWA-09-R-00055
Amendment No. 0002
M.18. FINAL EVALUATION/SELECTION EVALUATION
Once the evaluations are complete, the respective Technical and Cost
Evaluation Team Leads will prepare a report for the Source Selection Evaluation
Board (SSEB). The SSEB will then prepare a Source Selection Report and
Recommendation for the Source Selection Official (SSO). The SSEB will then
present its’ Report and Recommendation to the SSO who will make the Best
Value Decision and select an Offeror for Award. Thereafter, the selected
contractor will be notified of the award. Unsuccessful Offerors will be notified of
the decision and provided the opportunity to debrief.
M - 13
Related docs
Other docs by HC120209091751
In most chelicerates the pedipalps are relatively small and are used as sensors
Views: 7 | Downloads: 0
