HTC711-13-R-D001.pdf

CODE

(Hour)

PAGE(S)

until 04:00 PM local time 22 Jan 2013

X

A X B X C X D

EX

X

G F 103 - 109

110 - 114 X H 115 - 118 deborah.crisp@ustranscom.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

1 118

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

HTC711 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 4 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

DEBORAH K. CRISP 618-220-6731

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 26

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

27 - 72

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

74 - 75 76 - 79

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 80 - 81 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 82 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

83 - 101

PART II - CONTRACT CLAUSES

USTRANSCOM-AQ - HTC711

508 SCOTT DR

SCOTT AFB IL 62225-5357

CONTACT BUYER

CONTACT BUYERFAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

20 Dec 2012

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

HTC711-13-R-D001

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES ESTIMATED

QUANTITY

UNIT UNIT PRICE AMOUNT

0001 1 Lot Labor (CDS Capital SW)

LH

TRDM IT Services, User Interface Development and Web Services

Paragraphs 1.1.2.2, 1.1.2.4.1, 1.1.2.5, 1.1.2.6

CDS Capital Funds

Period of Performance: 1 April 2013 - 30 September 2013

FOB: Destination

SIGNAL CODE: A

TOT ESTIMATED PRICE

CEILING PRICE

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0002 6 Months Labor (CDS Ops)

FFP

TRDM Database Management, System Admin Support

PWS Paragraphs 1.1.1, 1.1.1.3.1, 1.1.1.3.2, 1.1.1.3.3, 1.1.2.1, 1.1.2.3, 1.1.2.4.2, 1.1.2.7, 1.1.2.8 and 1.1.2.9

CDS Operations Funds

Period of Performance: 1 April 2013 - 30 September 2013

NET AMT

0003 6 Months Labor (RDT&E)

FFP

Task 2, DAIS System Design, Configuration Management, Database Management and Web Services

PWS Paragraphs 1.2.2.2, 1.2.2.3.4, 1.2.2.4.3, 1.2.2.4.5, 1.2.2.5, 1.2.2.6.3, 1.2.2.6.4, 1.2.2.7 and 1.2.2.10

OSD RDT&E Funds

Period of Performance: 1 April 2013 - 30 September 2013

0004 6 Months Labor (Ops & Maint) Optional Task 2

FFP

DAIS Test and Evaluation, Operations, Life Cycle Management, Security

Task 2, PWS Paragraphs 1.2.1, 1.2.2.3.4, 1.2.2.4, 1.2.2.4.6, 1.2.2.6.1.1, 1.2.2.6.5,

1.2.2.8 and 1.2.2.9

OSD O&M Funds

Period of Performance: 1 April 2013 - 30 September 2013

UNIT UNIT PRICE AMOUNT

0005 1 Lot Labor (Optional Task One)

TRDM Transition Support

Task One, PWS Paragraphs 1.1.2.10.1 and 1.1.2.10.2

0006 6 Months Labor (Optional Task Three)

FFP

DAIS Transition Support

Task Three, PWS Paragraph 1.2.2.11

OSD RDT&E Funds

Period of Performance: 1 April 2013 - 30 September 2013

0007 Lot FY13 ODCs

COST

FY13 ODCs IAW PWS Paragraphs 4.1.9, 4.1.10 and 4.1.11

Cost: $45,000.00

ESTIMATED COST

0008 Lot FY13 Travel

FY13 Travel IAW PWS Paragraph 4.1.6

Cost: $2,500.00

UNIT UNIT PRICE AMOUNT

1001 1 Lot OPTION Labor (CDS Capital SW)

Period of Performance: 1 October 2013 - 30 September 2014

1002 12 Months OPTION Labor (CDS Ops)

FFP

TRDM Database Management, System Admin Support

PWS Paragraphs 1.1.1, 1.1.1.3.1, 1.1.1.3.2, 1.1.1.3.3, 1.1.2.1, 1.1.2.3, 1.1.2.4.2, 1.1.2.7, 1.1.2.8 and 1.1.2.9

CDS Operations Funds

Period of Performance: 1 October 2013 - 30 September 2014

1003 12 Months OPTION Labor (RDT&E)

FFP

Task 2, DAIS System Design, Configuration Management, Database Management and Web Services

PWS Paragraphs 1.2.2.2, 1.2.2.3.4, 1.2.2.4.3, 1.2.2.4.5, 1.2.2.5, 1.2.2.6.3, 1.2.2.6.4, 1.2.2.7 and 1.2.2.10

OSD RDT&E Funds

Period of Performance: 1 October 2013 - 30 September 2014

1004 12 Months OPTION Labor (Ops & Maint) Optional Task 2

FFP

DAIS Test and Evaluation, Operations, Life Cycle Management, Security

Task 2, PWS Paragraphs 1.2.1, 1.2.2.3.4, 1.2.2.4, 1.2.2.4.6, 1.2.2.6.1.1, 1.2.2.6.5,

1.2.2.8 and 1.2.2.9

OSD O&M Funds

Period of Performance: 1 October 2013 - 30 September 2014

UNIT UNIT PRICE AMOUNT

1005 1 Lot OPTION Labor (Optional Task One)

1006 12 Months OPTION Labor (Optional Task Three)

FFP

DAIS Transition Support

Task Three, PWS Paragraph 1.2.2.11

OSD RDT&E Funds

Period of Performance: 1 October 2013 - 30 September 2014

1007 Lot OPTION FY14 ODCs

FY14 ODCs IAW PWS Paragraphs 4.1.9 and 4.1.10

Cost: $130,000.00

1008 Lot OPTION FY14 Travel

FY14 Travel IAW PWS Paragraph 4.1.6

Cost: $5,000.00

UNIT UNIT PRICE AMOUNT

2001 1 Lot OPTION Labor (CDS Capital SW)

Period of Performance: 1 October 2014 - 30 September 2015

2002 12 Months OPTION Labor (CDS Ops)

FFP

TRDM Database Management, System Admin Support

PWS Paragraphs 1.1.1, 1.1.1.3.1, 1.1.1.3.2, 1.1.1.3.3, 1.1.2.1, 1.1.2.3, 1.1.2.4.2, 1.1.2.7, 1.1.2.8 and 1.1.2.9

CDS Operations Funds

Period of Performance: 1 October 2014 - 30 September 2015

2003 12 Months OPTION Labor (RDT&E)

FFP

Task 2, DAIS System Design, Configuration Management, Database Management and Web Services

PWS Paragraphs 1.2.2.2, 1.2.2.3.4, 1.2.2.4.3, 1.2.2.4.5, 1.2.2.5, 1.2.2.6.3, 1.2.2.6.4, 1.2.2.7 and 1.2.2.10

OSD RDT&E Funds

Period of Performance: 1 October 2014 - 30 September 2015

2004 12 Months OPTION Labor (Ops & Maint) Optional Task 2

FFP

DAIS Test and Evaluation, Operations, Life Cycle Management, Security

Task 2, PWS Paragraphs 1.2.1, 1.2.2.3.4, 1.2.2.4, 1.2.2.4.6, 1.2.2.6.1.1, 1.2.2.6.5,

1.2.2.8 and 1.2.2.9

OSD O&M Funds

Period of Performance: 1 October 2014 - 30 September 2015

UNIT UNIT PRICE AMOUNT

2005 1 Lot OPTION Labor (Optional Task One)

2006 12 Months OPTION Labor (Optional Task Three)

FFP

DAIS Transition Support

Task Three, PWS Paragraph 1.2.2.11

OSD RDT&E Funds

Period of Performance: 1 October 2014 - 30 September 2015

2007 Lot OPTION FY15 ODCs

FY15 ODCs IAW PWS Paragraphs 4.1.9 and 4.1.10

2008 Lot OPTION FY15 Travel

FY15 Travel IAW PWS Paragraph 4.1.6

UNIT UNIT PRICE AMOUNT

3001 1 Lot OPTION Labor (CDS Capital SW)

Period of Performance: 1 October 2015 - 30 September 2016

3002 12 Months OPTION Labor (CDS Ops)

FFP

TRDM Database Management, System Admin Support

PWS Paragraphs 1.1.1, 1.1.1.3.1, 1.1.1.3.2, 1.1.1.3.3, 1.1.2.1, 1.1.2.3, 1.1.2.4.2, 1.1.2.7, 1.1.2.8 and 1.1.2.9

CDS Operations Funds

Period of Performance: 1 October 2015 - 30 September 2016

3003 12 Months OPTION Labor (RDT&E)

FFP

Task 2, DAIS System Design, Configuration Management, Database Management and Web Services

PWS Paragraphs 1.2.2.2, 1.2.2.3.4, 1.2.2.4.3, 1.2.2.4.5, 1.2.2.5, 1.2.2.6.3, 1.2.2.6.4, 1.2.2.7 and 1.2.2.10

OSD RDT&E Funds

Period of Performance: 1 October 2015 - 30 September 2016

3004 12 Months OPTION Labor (Ops & Maint) Optional Task 2

FFP

DAIS Test and Evaluation, Operations, Life Cycle Management, Security

Task 2, PWS Paragraphs 1.2.1, 1.2.2.3.4, 1.2.2.4, 1.2.2.4.6, 1.2.2.6.1.1, 1.2.2.6.5,

1.2.2.8 and 1.2.2.9

OSD O&M Funds

Period of Performance: 1 October 2015 - 30 September 2016

UNIT UNIT PRICE AMOUNT

3005 1 Lot OPTION Labor (Optional Task One)

3006 12 Months OPTION Labor (Optional Task Three)

FFP

DAIS Transition Support

Task Three, PWS Paragraph 1.2.2.11

OSD RDT&E Funds

Period of Performance: 1 October 2015 - 30 September 2016

3007 Lot OPTION FY16 ODCs

FY16 ODCs IAW PWS Paragraphs 4.1.9 and 4.1.10

3008 Lot OPTION FY16 Travel

FY16 Travel IAW PWS Paragraph 4.1.6

UNIT UNIT PRICE AMOUNT

4001 1 Lot OPTION Labor (CDS Capital SW)

Period of Performance: 1 October 2016 - 30 September 2017

4002 12 Months OPTION Labor (CDS Ops)

FFP

TRDM Database Management, System Admin Support

PWS Paragraphs 1.1.1, 1.1.1.3.1, 1.1.1.3.2, 1.1.1.3.3, 1.1.2.1, 1.1.2.3, 1.1.2.4.2, 1.1.2.7, 1.1.2.8 and 1.1.2.9

CDS Operations Funds

Period of Performance: 1 October 2016 - 30 September 2017

4003 12 Months OPTION Labor (RDT&E)

FFP

Task 2, DAIS System Design, Configuration Management, Database Management and Web Services

PWS Paragraphs 1.2.2.2, 1.2.2.3.4, 1.2.2.4.3, 1.2.2.4.5, 1.2.2.5, 1.2.2.6.3, 1.2.2.6.4, 1.2.2.7 and 1.2.2.10

OSD RDT&E Funds

Period of Performance: 1 October 2016 - 30 September 2017

4004 12 Months OPTION Labor (Ops & Maint) Optional Task 2

FFP

DAIS Test and Evaluation, Operations, Life Cycle Management, Security

Task 2, PWS Paragraphs 1.2.1, 1.2.2.3.4, 1.2.2.4, 1.2.2.4.6, 1.2.2.6.1.1, 1.2.2.6.5,

1.2.2.8 and 1.2.2.9

OSD O&M Funds

Period of Performance: 1 October 2016 - 30 September 2017

UNIT UNIT PRICE AMOUNT

4005 1 Lot OPTION Labor (Optional Task One)

4006 12 Months OPTION Labor (Optional Task Three)

FFP

DAIS Transition Support

Task Three, PWS Paragraph 1.2.2.11

OSD RDT&E Funds

Period of Performance: 1 October 2016 - 30 September 2017

4007 Lot OPTION FY17 ODCs

FY17 ODCs IAW PWS Paragraphs 4.1.9 and 4.1.10

4008 Lot OPTION FY17 Travel

FY17 Travel IAW PWS Paragraph 4.1.6

Period of Performance: 1 October 2017 - 30 September 2017

Cost: $7,200.00

UNIT UNIT PRICE AMOUNT

5001 1 Lot OPTION Labor (CDS Capital SW)

Period of Performance: 1 October 2017 - 31 March 2018

5002 6 Months OPTION Labor (CDS Ops)

FFP

TRDM Database Management, System Admin Support

PWS Paragraphs 1.1.1, 1.1.1.3.1, 1.1.1.3.2, 1.1.1.3.3, 1.1.2.1, 1.1.2.3, 1.1.2.4.2, 1.1.2.7, 1.1.2.8 and 1.1.2.9

CDS Operations Funds

Period of Performance: 1 October 2017 - 31 March 2018

5003 6 Months OPTION Labor (RDT&E)

FFP

Task 2, DAIS System Design, Configuration Management, Database Management and Web Services

PWS Paragraphs 1.2.2.2, 1.2.2.3.4, 1.2.2.4.3, 1.2.2.4.5, 1.2.2.5, 1.2.2.6.3, 1.2.2.6.4, 1.2.2.7 and 1.2.2.10

OSD RDT&E Funds

Period of Performance: 1 October 2017 - 31 March 2018

5004 6 Months OPTION Labor (Ops & Maint) Optional Task 2

FFP

DAIS Test and Evaluation, Operations, Life Cycle Management, Security

Task 2, PWS Paragraphs 1.2.1, 1.2.2.3.4, 1.2.2.4, 1.2.2.4.6, 1.2.2.6.1.1, 1.2.2.6.5,

1.2.2.8 and 1.2.2.9

OSD O&M Funds

Period of Performance: 1 October 2017 - 31 March 2018

UNIT UNIT PRICE AMOUNT

5005 1 Lot OPTION Labor (Optional Task One)

5006 6 Months OPTION Labor (Optional Task Three)

FFP

DAIS Transition Support

Task Three, PWS Paragraph 1.2.2.11

OSD RDT&E Funds

Period of Performance: 1 October 2017 - 31 March 2018

5007 Lot OPTION FY18 ODCs

FY18 ODCs IAW PWS Paragraphs 4.1.9 and 4.1.10

Cost: $65,000.00

5008 Lot OPTION FY18 Travel

FY18 Travel IAW PWS Paragraph 4.1.6

Cost: $2,500.00

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

USTRANSCOM REFERENCE DATA MANAGEMENT

and

I&E DATA ANALYTICS AND INTEGRATION SUPPORT PLATFORM

SUPPORT TO

UNITED STATES TRANSPORTATION COMMAND

COMMAND, CONTROL, COMMUNICATIONS AND COMPUTER SYSTEMS DIRECTORATE

PERFORMANCE WORK STATEMENT (PWS)

27 Nov 2012

1. Background

TRDM is the USTRANSCOM tool used to manage enterprise reference data. The tool is managed by the Government and maintained and modernized, as necessary, by the Contractor. TRDM includes data from the former Table Management Distribution System (TMDS), which managed Air Mobility Command (AMC) reference data. The majority of this data has since transitioned to TRDM and remaining tables and interfaces associated with TMDS are being migrated to TRDM. The reference data management process is consistent with the Information Reference Model (IRM) manual as published by USTRANSCOM/J6. The TRDM Program Management Office (PMO) is responsible for providing and interpreting USTRANSCOM policy as it applies to TRDM.

This contract will combine the maintenance of the reference tables, design and implementation of new capabilities, to include the expansion of the Real Property Unique Identifier Registry (RPUIR) capability to become the information management system, dubbed the Data Analytics and Integration Support (DAIS) platform, supporting OSD (I&E) Business Enterprise Integration office Real Property Inventory Reporting (RPIR) and Enterprise Energy Information Management (EEIM) requirements.

In FY2003, the Installations & Environment (I&E) Domain partnered with the Military Services, Defense Agencies, and other Business Management Modernization Program (BMMP) Business Mission Areas (BMAs) to transform or reengineer business processes for the accountability of real property. The goal was, and still is, the availability of reliable, timely, and useful real property asset information to support functional analysis and decision making as well as financial reporting. Inter-Agency and Cross-Service work groups were established to identify the data elements and to analyze and resolve process issues. The results were approved in January 2005 as the RPIR document. The long term goal is to expand the current functions of the RPUIR by incorporating the full Real Property Information Model (RPIM). Real Property Unique Identifiers (RPUIDs) will continue to be implemented for the nearly 1 million global site and real property assets and the DAIS system will continue to act as the centralized data source for RPUIDs both for initial assignment of new RPUIDs and for lookup of existing RPUIDs.

The DUSD (I&E) convened a working group to standardize energy information and business processes utilizing existing enterprise information to the extent possible. The standard data elements that the working group developed became the EEIM model. As incorporated within the DAIS System, EEIM will provide net-centric energy data access services and an energy data warehouse that will provide a consolidated view of timely, reliable energy information for use in measuring, managing and reporting DoD energy consumption, conservation, and renewable energy production information. DoD’s facility energy vision is to use integrated processes and a standard data structure to collect facility energy consumption, renewable energy generation, and energy efficiency project data.

This integrated information structure will facilitate trend analysis, performance comparison, and efficiency improvement across facilities and DoD Components.

The Contractor shall provide continuing on-site support services contributing directly to the management of reference data for USTRANSCOM, its Transportation Component Commands: AMC, Military Sealift Command

(MSC), Military Surface Deployment and Distribution Command (SDDC), and other Department of Defense (DoD) communities. DoD is subject to extensive energy reporting requirements that impose a growing burden on DoD personnel to collect, analyze, package, and transmit energy data. DoD currently does not have standardized enterprise facility energy information, nor does it have enterprise-wide information technology systems to support facility energy management. This lack of standardization requires energy managers and other personnel to manually collect, transform, and reformat data to meet separate data calls. This highly inefficient atmosphere leaves energy managers with little time to manage facility energy consumption, or to focus on ways to improve facility energy efficiency.

1.1. TRDM

The scope of TRDM requires the Contractor to perform specialized systems engineering and technical support of TRDM and distribution of the TRDM-maintained data. TRDM provides a single source of enterprise reference data for enhancing command and control (C2), transportation, logistics, deployment, and financial systems’ reference data management and functional data collection. The Contractor is required to perform requirements analysis, functional data collection, command reference data management to support data validation across system interfaces, reference data distribution implementation, fielding, planning, integrated release scheduling, system interoperability testing (SIT) support, integrated test plan documentation, and reference data distribution.

TRDM consists of approximately 2,500 database tables, with data from over 800 Government and commercial reference data sources. TRDM has a system presence on both the classified and unclassified networks. The data is stored within an Oracle platform. Web users may access data through a custom user interface. There are currently over 2,700 TRDM users and approximately 50 unique system interfaces with an average of 4 new systems interfacing with TRDM yearly. There are approximately 250 requirements for reference data generated annually;

each requirement may include one or more sub-requirements. Requirements include requests to manage new reference data, requests for changes to existing reference data, and requests for new or updated views, filters, or web services to deliver data. In accordance with FAR Part 27.401-1 and DFARS 227-7103, DFARS Part 252.227-7013 and 252.227-7014, the Government acquires unlimited rights in all technical data and computer software developed by the contractor pursuant to this contract. No portion of this PWS should be considered or interpreted as being funded except exclusively by the Government. All systems and component parts shall be delivered to the Government with correspondant “unlimited” data rights.

1.1.1. Contract Management

1.1.1.1. This task consists of functional activities relating to administration and management of this effort. The Contractor shall provide program management of Contractor personnel performing tasks in this order. The Contractor shall designate a principal point of contact for technical issues. A DRAFT contract management plan shall be provided to the Government fifteen (15) business days after the award of the contract with the final version being provided to the Contracting Officer Representative (COR) fifteen (15) business days after Government approval of the DRAFT.

Deliverable: DRAFT Contract Management Plan delivered to COR fifteen (15) business days after contract award with the final version being provided to the Contracting Officer Representative (COR) fifteen (15) business days after Government approval of the DRAFT.

1.1.1.2. The Contractor shall schedule and attend weekly progress reviews with the COR and provide verbal updates on the status of projects being worked.

1.1.1.3. Status Reports.

1.1.1.3.1. Monthly Cost/Status and Resource Utilization Reports.

The Contractor shall provide the COR with a monthly cost/status summary and resource utilization report, separate from In Progress Review (IPR) materials that details the specifics of the work performed. This cost/status summary and resource utilization report should be delivered to the COR no later than the 10th day of the following month for the previous month’s activities. The monthly cost/status report shall summarize costs, status, progress, and recommendations for project areas being undertaken under this contract. Status reports will provide specific labor hours/costs by major project areas.

Deliverable: Monthly Cost/Status and Resource Utilization Report delivered to the COR no later than the 10th day of the following month.

1.1.1.3.2. Weekly Activities Report (WAR).

The Contractor shall provide a WAR detailing significant events to the COR. Significant events may include cost, schedule, or performance impacts in meeting the requirements of the tasks in this PWS. This report will be given to the COR by 1200 every Wednesday in a Word document format via email.

Deliverable: WAR provided to COR by 1200 every Wednesday in a Word document format via email.

1.1.1.3.3. In Progress Review (IPR).

The Contractor shall meet with the Functional manager/COR semi-annually to discuss any problems with current tasks, assignment of future tasks, and to get Government decisions or guidance necessary to facilitate or improve existing processes. The Contractor shall deliver IPR minutes, with a copy of the presentation slides. The slides must also be presented to the COR no later than three (3) business days prior to the IPR. At a minimum, the minutes shall reflect a record of activity, decisions made, date, location, and attendees. IPR minutes will be delivered to the COR within five (5) business days after the IPR.

Deliverable: Semi-annual IPR Slides three (3) business days prior to IPR and meeting minutes five (5) business days after IPR.

1.1.2. TRDM Information Technology (IT) Services.

1.1.2.1. TRDM-Database Management.

1.1.2.1.1. The Contractor shall be responsible for the administration and maintenance of the TRDM database on both the classified and unclassified networks and work with designated USTRANSCOM/J6 support organizations.

The Contractor shall monitor the database performance to proactively identify and resolve performance issues. The Contractor shall ensure appropriate auditing functions are enabled to capture all pertinent information regarding all database transactions. The Contractor shall update and maintain all necessary documentation for the administration and management of the reference data repository.

1.1.2.1.2. The Contractor shall provide and maintain logical and physical database models in support of this effort.

Deliverable: Provide logical and physical database models to the COR at contract award and as requested thereafter.

1.1.2.1.3. The Contractor shall be responsible for the generation of the associated architecture products to support the Information Support Plan (ISP) or Tailored ISP (TISP) and DoD Information Assurance Certification and Accreditation Process (DIACAP) process. These products will require updates throughout the duration of the contract period as system changes occur. The Contractor shall assist with the mapping of reference data to any conceptual business models and enterprise-level logical data models.

Deliverable: Provide and update the ISP and TISP, along with required architecture documentation relating to the DIACAP process.

1.1.2.1.4. The database and operating system shall incorporate appropriate security mechanisms that allow for the assignment of permissions and roles to control database access. The Contractor shall be responsible for the setup and administration of USERIDs, passwords, permissions, and roles (and/or other appropriate security techniques) assigned to users of the repository. The Contractor shall be responsible to ensure the appropriate backup and recovery techniques are in place to protect and secure the reference data. All personnel working on this task shall be Information Assurance Workforce Improvement Program (IAWIP) level IAT-II (or better) compliant.

1.1.2.1.5. In addition, the Contractor shall maintain the database to provide read only capabilities, such as Open Database Connectivity (ODBC), or similar functionality for access to the data.

1.1.2.1.6. The Contractor shall maintain the ability to pull metrics of which customers are using which tables and the frequency of use.

1.1.2.1.7. All data identified for the DoD Metadata Repository (DMR) shall have clearly-defined metadata and shall be Extensible Mark Up Language (XML)-tagged. This data shall be uploaded and maintained in the DoD Metadata and XML Registries to support the DoD Net-Centric Data Strategy for visibility, understanding, and discovery of data. The Contractor shall perform these duties in conjunction with DoD Net-Centric goals (http://metadata.dod.mil/mdr/ns/ces/techguide/net_centric_data_strategy_ncds_goals.html) and the USTRANSCOM Corporate Services Vision (CSV).

1.1.2.2. TRDM – Reference Data Collection and Data Loads

The Contractor shall perform actions necessary to support the expansion of the reference data management program within USTRANSCOM supporting the collection and management of authoritative and derived reference data.

1.1.2.2.1. The Contractor shall work with the functional community and appropriate data vendors to identify and define potential reference data sources that could be consumed by TRDM and redistributed to the enterprise.

1.1.2.2.2. The Contractor shall communicate with organizations and points of contact outside of DoD to obtain essential USTRANSCOM reference data (examples are: DTEB.org and CalPoly.edu).

1.1.2.2.3. The Contractor shall model the table structures for new reference data and provide the model to the Enterprise Data Office (EDO).

1.1.2.2.4. Once coordinated, the Contractor will work with the authoritative source to define the method of obtaining the data within TRDM and design the appropriate interface to consume the data and populate the database.

1.1.2.2.5. The Contractor shall create tables populated with commercial and Government reference data, maintain the data and make updates to the data. Authoritative data shall be managed by the data stewards per agreements made with each authoritative source as to the frequency of updates for reference data.

1.1.2.2.6. The Contractor shall provide technical data stewards to initially acquire and perform any required data analysis in support of reference data updates, to include active participation in the USTRANSCOM data forums as requested by the COR.

1.1.2.2.7. The Contractor shall notify the TCC data offices via email of new data offerings as it becomes available.

1.1.2.2.8. The Contractor shall forward reference table changes to the TCC data offices and the change request submitter via email.

1.1.2.2.9. The Contractor shall support critical exercises (e.g. Terminal Fury, Dragon Reach, etc.) by preparing specific table updates for distribution, while ensuring interface partners and TRDM users are not impacted by these exercises. These exercises occur on a quarterly basis.

1.1.2.3. TRDM – Data Maintenance

1.1.2.3.1. The Contractor shall provide data stewards to maintain correctness and currency of the reference data.

The repository currently contains over 2,500 tables each of which has associated data and meta-data which must be updated as defined by the functional community. The Contractor shall work with data sources to ensure this data is current and accurate. Currently, TRDM has over 800 Government and commercial data sources.

1.1.2.3.2. The Contractor shall track the use of data labeled as limited distribution and ensure that the data is not being distributed to more than the allotted number of users or systems. In the event the data is being distributed to more than the allotted number of users, the Contractor shall notify the COR for further review.

1.1.2.3.3. The Contractor shall migrate the approximately 500 remaining legacy TMDS tables from the legacy database to the current TRDM database. This effort will involve the modeling, creation, and population of these tables within TRDM.

This work under paragraph 1.1.2.3.3 is expected to be completed in FY13 and further maintenance of these tables will fall under duties described in Section 1.1.2.3.1.

1.1.2.3.4. The Contractor shall comply with existing IA procedures to manually move data back and forth between unclassified and classified sources. The Contractor shall ensure that data is maintained, updated, and synchronized in both the classified and unclassified versions of TRDM.

1.1.2.4. TRDM - User Interface Development

1.1.2.4.1. The Contractor shall maintain the web site for the TRDM data using tools that meet DoD requirements.

Deliverable: Source code for the TRDM website on CD/DVD media to be provided annually to the COR NLT 30 September of each year for the life of the contract.

1.1.2.4.1.1. The Contractor shall perform actions necessary to ensure the repository and associated products comply with the USTRANSCOM data policy.

1.1.2.4.1.2. The Contractor shall ensure appropriate DoD security mechanisms are in place to protect the reference data.

1.1.2.4.1.3. The Contractor shall maintain, add, change, and delete necessary views or displays of data on the TRDM web-based interface.

1.1.2.4.1.4. The Contractor shall maintain an inquiry capability for users to pull and filter all reference data via the TRDM web interface. The Contractor shall build additional search capabilities as requested by the customer and discovery of all reference data via the TRDM website along with the ability for the consumer to extract the requested data in a variety of formats. The Contractor shall support the Government in defining terms and conditions that define the extract formats for use by consumers.

1.1.2.4.1.5. The Contractor shall update and build data views and filters to accommodate general customer needs.

1.1.2.4.1.6. The Contractor shall maintain the capability to identify and calculate the total number of users accessing TRDM data via the web interface and any email subscribers to TRDM tables.

1.1.2.4.1.7. The Contractor shall ensure all necessary disclaimer and copyright warnings are appropriately displayed on the TRDM website.

1.1.2.4.1.8. The Contractor shall build and maintain the capability for web users to submit new requirements for data changes, additions, updates, etc. directly on the web interface. Once submitted, the Contractor shall forward these requirements to the Program Manager’s Office where they will flow through the normal Requirements Review Board (RRB) process.

1.1.2.4.2. The Contractor shall create and maintain a user guide for the TRDM web interface detailing basic functionality such us searching, navigating, subscribing, data stewardship, etc. A draft user guide will be delivered to the Government in a PDF format by 30 Sep 2013. Once approved by the Government, this user guide will be updated thereafter as significant changes are made to the web interface.

Deliverable: Draft TRDM Web Interface User’s Guide in PDF format delivered to the Government by 30 Sep 2013 and maintained as necessary thereafter.

1.1.2.5. TRDM – Data Distribution

1.1.2.5.1. The Contractor shall maintain the data distribution application that will be used in conjunction with the user interface application to direct users’ changes to the appropriate systems. Expansion of distribution beyond current distribution may include sending reference data updates, as required, to other systems. The Contractor shall maintain and update a Relational Database Management System (RDBMS) that contains all managed reference tables and information associated with those tables. Reference table data must be viewable and downloadable for DoD and Government users using the security measures currently in place by USTRANSCOM (i.e. Common Access Card (CAC) login, Public Key Infrastructure (PKI) enabled).

1.1.2.5.2. The Contractor shall work with other systems’ Contractor representatives with operational expertise to perform an in-depth requirements analysis. This analysis will lead to a technically achievable interface to present operational and technical alternatives to the COR for discussion and decisions. The Contractor shall assist in defining and documenting the pertinent data elements, data flow, and business and implementation rules necessary to assure a compatible interface between these two systems based on the interface requirements. Upon COR approval of interface solutions, the Contractor shall perform the implementation through the software development, testing, and fielding cycle. Based on individual program requirements, multiple test baselines will require support.

Additionally, as each interface is fielded, new requirements and/or changes to the approved solution will occur.

Changes to these solutions must also be tracked through the fielding and maintenance cycle. Updates to these documents and changes to existing interface structures should be noted in the WAR. Existing interface documentation is reviewed annually or as needed if changes are made throughout the year. There are approximately thirty (30) existing interface agreements in place and the program anticipates a requirement of an additional average of five (5) new interfacing systems each year.

Deliverable: Create or update interface documentation to be delivered to the COR as necessary.

1.1.2.6. TRDM – Web Services.

1.1.2.6.1. The Contractor shall build and maintain web services to distribute reference data. These web services shall be built using tools and methodology that is consistent with the USTRANSCOM Enterprise Architecture as it relates to the implementation of the Corporate Services Vision (CSV). The Contractor shall build and employ mechanisms to ensure the synchronized availability of reference data to all consumers in accordance with (IAW) the Government’s specified terms and conditions for use by all subscribers. The Contractor shall maintain and update the data views and filters to accommodate customer needs. The Contractor shall allow for delivery of the same reference data to a specific system operating in multiple (i.e. primary and alternate) environments from different locations. The Contractor shall build publish and subscribe mechanisms that will provide access to the data to any approved user, who will be able to search for desired information and retrieve it immediately. The Contractor shall deliver data to any approved user who requests it, eliminating the need for pair-wise memorandum of agreement (MOAs) and IRDDs, as all subscribers will agree to the same terms and conditions. Customer requests will be received by the TRDM Contractor via email from the requestor and coordinated with the COR prior to action. All development shall be accomplished to meet all applicable DoD regulations. The Government estimates that their will be requirements for approximately five (5) new web services each year. There are approximately twenty (20) existing services, and these services may require updates at any time as requested by the user community.

Deliverable: Source code for TRDM web services on CD/DVD media to be provided annually to the COR NLT 30 Sep each year for the life of the contract.

1.1.2.6.2. The Contractor shall provide advisory services for web service, portal development, and Business Process Modeling architecture evaluations for reference data requirements to the USTRANSCOM agile development teams working within the Enterprise Integration Lab (EIL).

1.1.2.6.3. The Contractor shall maintain web services to support the receipt and delivery of data to and from systems. Web services shall also be implemented to support reporting and queries against repository data. The Contractor shall also monitor and validate automated queries of the web service to ensure that the web service responds in a timely manner. The Contractor shall maintain the mechanism to ensure positive and routine control of reference data to ensure all data is received by the using system.

1.1.2.6.4. All web services and interfaces will have defined metadata and will be XML-tagged. This data shall be uploaded and maintained in the DoD Metadata and XML registries to support the USTRANSCOM CSV for visibility and discovery of data including interfaces. The DoD Metadata Registry can be found at https://metadata.dod.mil/mdr/homepage.htm.

1.1.2.7. TRDM – Customer Support

The Contractor shall provide customer support five (5) days a week during normal business work hours (0800-1800 CST). Contractor shall respond to customer queries received outside of normal business hours within four (4) hours of start of next business day. For long-term resolution problems (two or more business days), the Contractor shall keep customers informed of call status daily. Contact information shall be provided on the web site and in user documentation. The customer support function shall manage and monitor the web site feedback area and respond to consumer questions and suggestions. Negative feedback or suggestions shall be communicated with the COR. The COR will then review the feedback and may require the Contractor to resolve any system or network-related issues.

1.1.2.8. TRDM – Information Assurance (IA)

The Contractor shall ensure the repository allows access only to .mil and .gov domain users and systems. The repository shall conform to DoD IA policies, including C2 level security and user access by PKI-enabled or CAC access.

1.1.2.8.1. The Contractor shall maintain appropriate tools and permissions in consort with USTRANSCOM network providers to deny access to unauthorized consumers. The Contractor shall ensure the infrastructure supporting TRDM is implemented to support the DoD defense-in-depth strategy, e.g., encryption, authentication, and logging. This task shall be completed only by staff Information Assurance Workforce Improvement Program (IAWIP) level IAT-II (or better) certified.

1.1.2.8.2. The Contractor shall provide the COR as needed with systems diagrams supporting the development of documentation for the DIACAP and work with Government-designated entities to obtain necessary system certifications (i.e. Authority to Operate (ATO), Authority to Connect (ATC)). This task shall be completed only by staff IAWIP level IAT-II (or better) certified.

Deliverable: Systems diagrams supporting creation and updates of documentation for DIACAP as needed.

1.1.2.8.3. The Contractor shall perform the duties of IA log monitoring and analysis on TRDM systems. The Contractor shall address any potential security findings by immediately relaying these findings to the COR and appropriate security entity for further instruction.

1.1.2.8.4. Security Engineering

The Contractor shall support security engineering activities. Security engineering personnel must be certified in accordance with DoDI 8570.01-M, Information Assurance Workforce Improvement Program (IAWIP). Personnel shall be certified at level IAT-II or better.

1.1.2.8.4.1. The Contractor shall attend, provide technical expertise and may be required to take meeting minutes/notes during Technical Information Meetings on a wide range of security engineering topics.

1.1.2.8.4.2. The Contractor shall attend, provide technical expertise and may be required to take meeting minutes/notes in IT program Engineering Milestone Reviews, e.g., System Requirements Review, Design Reviews, Test Readiness Reviews, Operational Readiness Reviews, and Incident Report Working Groups.

1.1.2.8.4.3. The Contractor shall support the USTRANSCOM/DISA Security Office to resolve and address security issues impacting all aspects of the program.

1.1.2.8.4.4. The Contractor shall create and/or review system accreditation documentation. The Contractor shall perform Technical Reviews of deliverables for security impact, e.g., Security Plan, DIACAP, Requirements Specification, Functional Specification, Design Documents, Sustainment Plans, Deployment Plans and Test Plans.

Document and deliver comments to the Government within specified timeframe.

Deliverable: Technical reviews of deliverables for security impact on an as needed basis.

1.1.2.8.4.5. The Contractor shall support operational security activities e.g., system log analysis, firewall implementation, risk mitigation, host security, encryption, intrusion detection, Virtual Private Network (VPN) implementations, and viral detections.

1.1.2.8.4.6. The Contractor shall coordinate overall security strategy with multiple agencies, Designated Approval Authority (DAA) representatives and vendors and other Government organizations/agencies to resolve and/or address a wide range of security engineering issues.

1.1.2.8.4.7. The Contractor shall recommend changes to the COR via email to network and security architecture as potential issues or improvements are identified for the purposes of improving security posture and meeting operational performance requirements.

1.1.2.8.4.8. The Contractor shall execute the program’s Information Assurance Vulnerability Management (IAVM) program in accordance with the DoD IAVM program.

1.1.2.8.5. Security Documentation Requirements

1.1.2.8.5.1. The Contractor shall request, gather and formalize inputs to various DIACAP-required documentation from other organizations (i.e., program management offices, system management offices, system administrators, functional managers, etc.) to fully complete all DIACAP requirements.

1.1.2.8.5.2. The Contractor shall complete the creation of all DIACAP-required documentation prior to submission for an Authorization to Operate (ATO) and an Authorization to Connect (ATC). Currently, TRDM resides on the Air Force Network with the ATO/ATC expiring on both the NIPR and SIPR networks in July 2013. The initial package for this reaccreditation will have been submitted just prior to the start of this contract. As the Information Awareness (IA) team reviews this package, changes may be required in the first 6 months of the contract. The Contractor shall make the appropriate changes as necessary to satisfy DIACAP requirements and ensure reaccreditation prior to the July 2013 expiration date. Eventually, TRDM will migrate to the TRANSCOM network. This will require a submission for a new ATO. It is estimated that the Contractor will be responsible for the development of documentation for two (2) accreditation cycles throughout the life of the contract – FY14 (TRANSCOM Network), FY17 (TRANSCOM Network). This estimate may be impacted depending upon the length of the ATO/ATC granted by the Designated Approving Authorities (DAA). This documentation will be provided to the COR. The Contractor shall also support the Government in the coordination and submission of the DIACAP-related documentation. The Contractor shall monitor the status of the DIACAP package through the ATO/ATC phases and will keep the IAM abreast of current status.

Deliverable: DIACAP-required documentation to the COR prior to the submission for an ATO and ATC. This documentation is estimated to be required two (2) times throughout the life of the contract.

1.1.2.8.5.3. The Contractor shall perform a monthly review of the Plans of Action and Milestones (POA&M) Report for all POA&M items that are due within the next sixty (60) days and update appropriate IA management tools (i.e., eMASS).

1.1.2.8.5.4. The Contractor shall provide the technical and administrative services necessary to support an accreditation decision.

1.1.2.8.5.5. The Contractor shall maintain and update all appropriate existing DIACAP documentation throughout the entire life of the ATO/ATC as necessary.

1.1.2.8.6. Test and Evaluation (T&E)

The Contractor shall provide test and evaluation support for TRDM and IT program-related activities throughout the acquisition lifecycle using the Integrated Defense Acquisition, Technology, & Logistics Life Cycle Management Framework.

1.1.2.8.6.1. The Contractor shall review and build test plans, cases, procedures and reports for Joint Interoperability Test Center (JITC) certification to ensure completeness, consistency and applicability to the requirements in the PMO system specification or applicable document. Findings and recommendations shall be consolidated into a complete analysis report of JITC test findings that the Contractor shall provide to the COR no later than ninety (90) calendar days after the start of the contract.

Deliverable: JITC analysis report of test findings no later than ninety (90) calendar days after the start of the contract and during subsequent re-certifications (FY13, FY16)

1.1.2.8.6.2. The Contractor shall create test and support documentation to include the Test Evaluation Master Plan

(TEMP).

1.1.2.8.6.3. The Contractor shall identify, document, test, and verify Incident Reports (IR) and Software Trouble Reports (STR), and provide system impact analysis feedback to the COR via email or verbal updates.

1.1.2.8.6.4. The Contractor shall plan, coordinate and perform test events, such as Operational Test and Evaluation (OT&E) and NR-KPP certification. The Contractor shall provide a Test Analysis Report (TAR), Joint Interoperability Certification Evaluation Plan (ICEP), and Net Ready Key Performance Parameter (NR-KPP) certification letter using the JITC approval format IAW the current version of Chairman Of The Joint Chief Of Staff Instruction (CJCSI) 6212.01 to the COR for submission to JITC. It is anticipated that this will be required on two

(2) occasions during periods of JITC certification and re-certification throughout the life of the contract. Current JITC certification is expected to be completed in July 2013 and a subsequent re-certification will take place approximately three (3) years later.

Deliverable: The Contractor shall provide a Test Analysis Report (TAR), Joint Interoperability Certification Evaluation Plan (ICEP), and NR-KPP certification letter using the JITC approval format IAW the current version of CJCSI 6212.01 to the COR within FY13 and during subsequent re-certifications. Anticipated to be on two (2) occasions through the life of the contract (FY13, FY16).

1.1.2.8.6.5. The Contractor shall attend, provide technical expertise and may be required to take meeting minutes/notes in the integrated product teams and working groups.

1.1.2.8.6.6. The Contractor shall support the Government in collaboration with external test organizations e.g., Air Force Operational Test and Evaluation Center’s (AFOTEC) and JITC.

1.1.2.9. TRDM - Reference Data Sustainment Support.

1.1.2.9.1. TRDM - Data Sustainment Support.

1.1.2.9.1.1. The Contractor shall document, track, and maintain ongoing support for the reference data repository to include routine, preventive and emergency maintenance, problem and change management, user support, data management, systems engineering support and performance management. In addition, MOAs, service level agreements (SLAs), performance measurement reporting, and quality assurance (QA) shall be provided by the Contractor supporting the TRDM infrastructure.

1.1.2.9.1.2. The Contractor shall maintain and provide the capability for TRDM users to view Baseline Change Requests (BCRs) and enterprise reference data requirements through the system’s web enabled visualization.

1.1.2.9.2. TRDM - System Administration and Sustainment Support.

1.1.2.9.2.1. The Contractor shall provide system sustainment and administrative functions for TRDM operations support, database administration (DBA), applications support and maintenance, systems engineering, configuration management, backup recovery, and audit trail maintenance. A listing of Government Furnished Equipment expected to be maintained is listed in Appendix B. The Contractor shall build additional virtual machines to support system functions and/or initiatives as necessary. This task shall be completed only by staff IAWIP level IAT-II (or better) certified.

1.1.2.9.2.2. The Contractor shall ensure the appropriate security measures (software, patching, firewalls, etc.) are in place to defend the system.

1.1.2.10. TRDM – Transition Support (Optional Task One) The support provided under this task is optional for all follow on years, and shall be executed at the discretion of the Government. If the Government determines support is required, the Government will provide the Contractor with a request for proposal. The Contractor shall provide a price proposal, breaking out the labor categories/rates and number of hours to accomplish the task. Upon acceptance of a valid Contractor proposal, the Government will process a modification to the contract. If the Government deems this support necessary, the Contractor will be given at least 15 days notice before a funding modification is executed.

The Contractor shall provide a project plan detailing the steps necessary to achieve re-engineering and re-hosting milestones within thirty (45) days after the Government requests it.

Deliverable: System re-engineering and re-hosting project plan no later than thirty (45) days after the Government requests it.

1.1.2.10.1. TRDM Reengineering.

The Contractor shall reengineer TRDM so that it is consistent with the USTRANSCOM Enterprise Architecture.

The Contractor shall transform TRDM from the current architecture to the JDDA-E compliant architecture. This will involve a complete redesign from the existing TRDM web-based interface to web-based portlets housed within USTRANSCOM’s CSV portal.

The Contractor shall enable an end state that creates a set of reference data that supports enterprise processes and systems. The Contractor shall work with USTRANSCOM enterprise architects to develop a plan that will be reviewed and approved by the Government.