HTC711-13-R-D003.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 15 Jul 2013

X

A X B X C X D

EX

X

G F 109 - 115

116 - 124 X H 125 - 129 jennifer.knobeloch@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 129

(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 7 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)

JENNIFER M. KNOBELOCH 618-220-7046

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 11

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

12 - 77

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

80 - 81

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 82 - 83 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 84 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

85 - 107

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

12 Jun 2013

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

HTC711-13-R-D003

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 10.50 Months Labor (FFP)

FFP

Ordering Period: 18 December 2013 - 30 September 2014 FOB: Destination

SIGNAL CODE: A

NET AMT

ITEM NO SUPPLIES/SERVICES ESTIMATED

QUANTITY

UNIT UNIT PRICE AMOUNT

0002 1 Lot Labor (LH)

LH

Ordering Period: 18 December 2013 - 30 September 2014

TOT ESTIMATED PRICE

CEILING PRICE

0003 Lot ODCs (cost)

COST

ODCs in accordance with para 4.3.12

Ordering Period: 18 December 2013 - 30 September 2014

ESTIMATED COST

0004 Lot Travel (cost)

Travel in accordance with para 4.3.9

Ordering Period: 18 December 2013 - 30 September 2014

0005 1 Each Guaranteed Minimum

FFP

Ordering Period: 18 December 2013 - 30 September 2014

1001 12 Months OPTION Labor (FFP)

FFP

Ordering Period: 1 October 2014 - 30 September 2015

UNIT UNIT PRICE AMOUNT

1002 1 Lot OPTION Labor (LH)

LH

Ordering Period: 1 October 2014 - 30 September 2015

1003 Lot OPTION ODCs (cost)

Ordering Period: 1 October 2014 - 30 September 2015

1004 Lot OPTION Travel (cost)

Ordering Period: 1 October 2014 - 30 September 2015

2001 12 Months OPTION Labor (FFP)

FFP

Ordering Period: 1 October 2015 - 30 September 2016

UNIT UNIT PRICE AMOUNT

2002 1 Lot OPTION Labor (LH)

LH

Ordering Period: 1 October 2015 - 30 September 2016

2003 Lot OPTION ODCs (cost)

Ordering Period: 1 October 2015 - 30 September 2016

2004 Lot OPTION Travel (cost)

Ordering Period: 1 October 2015 - 30 September 2016

3001 12 Months OPTION Labor (FFP)

FFP

Ordering Period: 1 October 2016 - 30 September 2017

UNIT UNIT PRICE AMOUNT

3002 1 Lot OPTION Labor (LH)

LH

Ordering Period: 1 October 2016 - 30 September 2017

3003 Lot OPTION ODCs (cost)

Ordering Period: 1 October 2016 - 30 September 2017

3004 Lot OPTION Travel (cost)

Ordering Period: 1 October 2016 - 30 September 2017

4001 12 Months OPTION Labor (FFP)

FFP

Ordering Period: 1 October 2017 - 30 September 2018

UNIT UNIT PRICE AMOUNT

4002 1 Lot OPTION Labor (LH)

LH

Ordering Period: 1 October 2017 - 30 September 2018

4003 Lot OPTION ODCs (cost)

Ordering Period: 1 October 2017 - 30 September 2018

4004 Lot OPTION Travel (cost)

Ordering Period: 1 October 2017 - 30 September 2018

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT

FOR

ENTERPRISE ARCHITECTURE, DATA, AND ENGINEERING

Version 3.13, 11 June 2013

Prepared by

UNITED STATES TRANSPORTATION COMMAND

DIRECTORATE OF COMMAND, CONTROL, COMMUNICATIONS & COMPUTER

SYSTEMS

1. DESCRIPTION OF SERVICES

1.1 Background

The mission of the United States Transportation Command (USTRANSCOM) is to develop and direct the Joint Deployment and Distribution Enterprise to globally project strategic national security capabilities;

accurately sense the operating environment; provide end-to-end distribution process visibility; and responsive support of joint, US Government and Secretary of Defense-approved multinational and non- Governmental logistical requirements.

The USTRANSCOM’s Directorate of Command, Control, Communications & Computer Systems (TCJ6) is responsible for long-range planning, policy guidance, direction, technical, control, and program management for projects involving the development and implementation of major transportation management systems Department of Defense (DOD)-wide.

The USTRANSCOM Directorate of Acquisitions (TCAQ) is responsible for partnering with industry and customers to develop and execute innovative acquisition solutions supporting the Command's full-spectrum, deployment and distribution mission. The Distribution Process Owner Division (TCAQ-D) provides responsive, flexible contracting support for USTRANSCOM DPO initiatives and Surface Deployment and Distribution Command National Level Transportation System requirements. Support includes, but is not limited to, commercial and non-commercial software development and related support services; Advisory and Assistance Services, management support services, ancillary support services;

classified and unclassified network support, and Research and Development. Its major programs are:

Agile Transportation for the 21st Century (AT21), Integrated Booking System (IBS), Global Freight Management (GFM), Defense Personal Property System (DPS), Enterprise Support Services (ESS), System Response Call Center, Total Supply Chain Process Improvement, Joint Distribution Process Analysis Center (JDPAC), Program Management Office (PMO) Support, Corporate Services Support (CSS), Integrated Computerized Deployment System (ICODES) and Automatic Identification Technology (AIT) Support.

The mission of the US Air Force Air Mobility Command Directorate of Command, Control, Communications, and Computer Information Systems (AMC/A6) is to provide integrated Command, Control, Communications, and Computer Information (C4I) systems and manage strategic C4I resources in support of AMC's global air mobility mission. AMC/A6CI manages the integration of the communications-computer systems via enterprise-wide planning, systems engineering, architecture development, and interoperability processes. AMC/A6CI ensures technical solutions for AMC C4I systems are in compliance with DOD, USTRANSCOM, US Air Force, and joint architecture and integration goals. AMC/A6CI is responsible for two separate interoperability roles: Air Force (appropriation funded) and Joint (Transportation Working Capital Funds).

The mission of the Military Surface Deployment and Distribution Command Communications Directorate (SDDC G6) is to manage the integration of the communications-computer systems via enterprise-wide planning, systems engineering, architecture development, and interoperability processes. SDDC G6/IMA Enterprise Services Branch provides the enterprise architecture, data integration, and engineering support which drives capability-based technical solutions within the command and ensures SDDC systems comply with DOD, USTRANSCOM, US Army, and joint architecture and integration strategies and objectives.

To achieve greater efficiencies and collaboration, the Government decided to combine the USTRANSCOM Enterprise Architecture (EA) (including data management and architecture tools), and enterprise engineering contracts with the equivalent AMC and SDDC contracts. The EA data currently resides in three independent repositories, managed by three independent tools. With this consolidated contract, the Government expects an integrated architecture tool suite.

1.2 Scope

This Performance Work Statement (PWS) is to acquire EA and information technology engineering services for USTRANSCOM, AMC/A6, and SDDC’s Automated Transport Systems Division (AMSSD- IMA), all located at Scott AFB, IL.

This PWS procures an integrated enterprise architecture from the enterprise level down through the solution level and across solution level architectures. Integration is achieved through the architecture tool suite, the use of standardized templates and guidelines, training, and the architecture review process. The work effort will support analytical services required to support and implement USTRANSCOM, AMC and SDDC operational and system requirements solutions. The Contractor must possess a comprehensive understanding of the DOD Architecture Framework (DODAF), the Federal Enterprise Architecture Framework (FEAF) and the relationships/dependencies between architecture models to support assigned projects. The scope of the architecture and data management services contained in this PWS includes the operational and system perspectives of Command and Control (C2), planning, transportation, logistics, and business support system domains. Using established strategic vision documentation, the Contractor will provide architecture and data management support. This allows Government personnel to conduct impact analysis on the enterprise, systems of systems, and individual system levels. Systems administration of the tools that house the architecture and data artifacts is also required.

1.3 Requirements

1.3.1 Task 1 - Contract Management

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. The Contractor shall provide a centralized program management capability. This function shall encompass administrative, clerical, documentation and related functions that provide general support for the program. The Contractor shall provide support by preparing documents such as briefings, point papers, and meeting minutes related to the status of the performance of this task order. This task will span the entire duration of the contract.

1.3.1.1 Monthly Cost/Status and Resource Utilization Reports

The Contractor shall provide a Monthly Status Report (MSR) to the Government no later than the 10th business day of the following month. The MSR shall list, by each active task/project area, the accomplishments of the reporting period. The MSR should outline a brief synopsis of the efforts completed, deliverables provided, and conferences and trips conducted/attended during the reporting period, and an overall evaluation of the PWS to date. The report shall list for each task any issues, problem areas, and items that require Government action. The final MSR shall be submitted no later than the last business day of the final period of performance. The Contractor shall create an initial architecture documentation plan that will be due within thirty (30) days after contract start date and updated monthly within the Monthly Status reporting.

Deliverable: Monthly Cost/Status and Resource Utilization Report, Architecture Work Break Down Structure

1.3.1.2 Weekly Activities Report (WAR)

The Contractor shall provide (2) separate (EA & Eng) WARs detailing significant events to the Contracting Officer Representative (COR).

The WAR shall be a Microsoft Office soft copy product covering project status, any risks and recommended solutions, status of previously identified issues, and any significant events for the previous week. The Contractor shall provide the WAR to the Government no later than the second business day of the following week.

Deliverable: EA WAR, Enterprise Engineering WAR

1.3.1.3 Work Progress Review Meeting

The Contractor shall brief the COR on the status of ongoing and anticipated future projects weekly. As part of the status, the Contractor shall identify what Contractor personnel are assigned to specific projects and estimated completion dates.

Deliverable: Work progress review meeting

1.3.1.4 In-Progress Review (IPR)

The Contractor shall conduct quarterly IPRs with the Functional Task Leads and COR during the contract meeting or as required by COR. The IPR shall summarize status, progress, recommendations, and concerns in the development of any tasks or documentation described within this PWS. Presentation materials shall be prepared and provided to the COR two (2) business days prior to the IPR. The presenting format shall be determined by the sponsoring (ordering) agencies. The IPR shall cover:

-Current project status and/or development effort under this PWS -Summary of accomplishments to date -Risks and mitigation strategy for each risk -Schedule delays, cause and corrective actions -Current funds expended to date (chart with trend line-burn rate) -Unexecuted funds to date (chart with trend line-burn rate) -Plans for the next three (3) calendar months

Deliverable: IPR and presentation materials

1.3.1.5 Trip Reports

The Contractor shall submit a trip report within five (5) business days of completion of any approved travel. The Contractor shall submit the trip report to include the following details: purpose, location, length of trip, travelers, and actual travel costs, individuals contacted during trip, synopsis of all discussions, future actions identified, decisions made, and issues of concern arising during the trip.

Deliverable: Trip Report

1.3.1.6 Meeting/Conference Minutes

The Contractor shall attend meetings or conferences held at USTRANSCOM or other locations as identified by the Government. When directed by the Government, the Contractor shall provide meeting/conference notes/minutes within two (2) days of attendance meeting/conference minutes that detail the results as well as the impact of the meetings/conferences. We estimate two (2) Chief Architect meeting forums per year. Meetings/Conferences shall generally take place during the normal duty hours but can extend beyond these core hours, e.g., information breach. The Contractor shall attend and participate in Technical Exchange Meetings (TEMs) with the Government as well as various Government and private national forums to demonstrate and present enterprise architecture development challenges, lessons learned and ways-ahead. As required, the Contractor shall create demonstrations, presentations, and information exchange sessions. All materials produced by the Contractor shall be reviewed and pre-approved by the COR. This review includes the proper marking of briefing materials and appropriate disclosure. Workload is estimated at one (1) TEM per month and one (1) conference or forum per quarter.

Deliverable: Presentation materials, meeting minutes

1.3.1.7 Enterprise-wide Contractor Manpower Reporting Application (eCMRA) Reporting

The Contractor shall report ALL direct contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for USTRANSCOM via a secure data collection site. The Contractor is required to completely fill-in all required data fields at http://www.ecmra.mil. The Contractor shall load the eCMRA information under the Department of the Air Force CMRA.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.

1.3.1.8. Annual Program Review

The Contractor shall provide inputs to the COR for the Annual Program Review cycle. The Contractor shall produce inputs for submissions using the templates as defined in the USTRANSCOM Handbook.

The due dates for the inputs will be determined by the COR and are estimated to be a minimum of fifteen

(15) business days.

Deliverable: Program Review inputs

1.3.2. Task 2 - Enterprise Architecture Development and Maintenance

1.3.2.1. Maintain Existing Architecture

1.3.2.1.1. Document Architectures USTRANSCOM

The Contractor shall document enterprise and solution level architectures supporting USTRANSCOM mission. The architectures will include the scope for C2, planning, transportation, logistics, and business systems domains. (e.g., exercise, experiment, and advanced technology demonstrations, and system-focused “as-is” and “to-be” architecture models). The Contractor shall adhere to Government-specified style guides, approved taxonomies, architecture implementation guides and element lists. Within the architecture, the Contractor shall document the design of critical links in DoDAF architecture model formats, to include the linkage between models and related architectures. The Contractor shall reuse existing architecture data/views to minimize development cost and schedule, and maintain configuration control of architectural artifacts and the underlying models. The Contractor shall capture and store USTRANSCOM performers, activities (functions), business process rules, information exchanges, data exchanges, data elements, and Data Dictionaries in the tools identified in Section 0.

Deliverable: Architecture documentation plan

1.3.2.1.2. Research Documentation for Existing Systems USTRANSCOM

The Contractor shall review published guidance identified in Section 3 as the initial source to gain an understanding of processes, systems, organizations, etc. that will influence architectural development efforts. The COR will identify other published guidance relevant to each architecture development effort.

Deliverable: DoDAF architecture views, overview and summary information

1.3.2.1.3. Conduct Interviews for Existing Systems USTRANSCOM

The Contractor shall conduct interviews with subject matter experts, sponsors, and participating organizations prior to and during architecture development. This iterative process requires the Contractor to obtain information from the business operations communities to develop the architecture views.

Deliverable: DoDAF architecture views

1.3.2.1.4. Identify Primitives for Existing Systems USTRANSCOM

The Contractor will review primitives (e.g., performers, systems, system functions, activities, information exchanges) identified while researching documentation (Para 1.3.2.1.1) and conducting interviews (Para 1.3.2.1.2) to determine whether or not these primitives exist within the Government designated enterprise architecture tool environment. If the primitives don’t exist, the Contractor shall propose the primitives to the COR for approval.

Deliverable: DoDAF architecture views, architecture primitives

1.3.2.1.5. Scope and Assemble Primitives into Architecture Views for Existing Systems USTRANSCOM

The Contractor shall collect, organize, correlate, and store the architecture data required for architecture development and document the architectural results in the Government designated enterprise architecture tool environment following Government approved procedures. The Contractor shall support primitive registration, architecture model construction, and architecture markup/coordination, using Government-provided tools in Section 3. This includes using multiple architecture modeling techniques (e.g., Entity Relationship Modeling, Swimlane Process Mapping, Functional Decomposition Tree Modeling, Business Process Modeling Notation (BPMN), Data Flow Modeling, Integrated Definition for Functional 0 (IDEF0) modeling, IDEF1X modeling, Event Trace Modeling, Dependency Analysis Modeling, Semantic Net Modeling, Unified Modeling Language (UML) techniques, etc.), and engineering techniques such as use cases. The Contractor shall mature the architecture views throughout the review and approval process and ensure all architecture artifacts produced comply with DoDAF and Government approved templates and guidelines.

Deliverable: DoDAF architecture views

1.3.2.1.6. Resolve Discrepancies for Existing Systems USTRANSCOM

The Contractor shall identify all architecture discrepancies during architecture model development and review processes. Obtaining Government approvals as necessary, the Contractor shall document the actions taken to resolve and adjudicate the discrepancies and provide a Monthly Discrepancy Report to the COR. The report may be in a format selected by the Contractor. The monthly report due date will be determined by the COR and may vary between one (1) to ten (10) business days.

Deliverable: Discrepancy and Resolution Report

1.3.2.1.7. Maintain Reference Models for Existing Systems USTRANSCOM

The Contractor shall review the existing reference models and suggest modifications to the COR. Upon approval of suggested changes by the COR, the Contractor shall implement changes. As required by the COR, the Contractor shall refine existing, or develop new, reference models which may include the development of ontology’s and taxonomies. New models may include the use of existing published models, such as the Joint Capability Areas (JCAs), Plan-Order-Ship-Track-Pay (POST-P), or the Joint Common System Function List (JCSFL). Requirements for the modification or development of reference models are estimated to be up to 100 times per fiscal year.

Deliverable: Suggested reference model changes

1.3.2.1.8. Document Architectures AMC and SDDC

The Contractor shall document enterprise and solution level architectures supporting AMC, and SDDC missions. The architectures will include the scope for C2, planning, transportation, logistics, and business systems domains. (e.g., exercise, experiment, and advanced technology demonstrations, and system-focused “as-is” and “to-be” architecture models). The Contractor shall adhere to Government-specified style guides, approved taxonomies, architecture implementation guides and element lists. Within the architecture, the Contractor shall document the design of critical links in DoDAF architecture model formats, to include the linkage between models and related architectures. The Contractor shall reuse existing architecture data/views to minimize development cost and schedule, and maintain configuration control of architectural artifacts and the underlying models. The Contractor shall capture and store AMC and SDDC performers, activities (functions), business process rules, information exchanges, data exchanges, data elements, and Data Dictionaries in the tools identified in Section 0.

Deliverable: Architecture documentation plan

1.3.2.1.9. Research Documentation for Existing Systems AMC and SDDC

The Contractor shall review published guidance identified in Section 3 as the initial source to gain an understanding of processes, systems, organizations, etc. that will influence architectural development efforts. The COR will identify other published guidance relevant to each architecture development effort.

Deliverable: DoDAF architecture views, overview and summary information

1.3.2.1.10. Conduct Interviews for Existing Systems AMC and SDDC

The Contractor shall conduct interviews with subject matter experts, sponsors, and participating organizations prior to and during architecture development. This iterative process requires the Contractor to obtain information from the business operations communities to develop the architecture views.

Deliverable: DoDAF architecture views

1.3.2.1.11. Identify Primitives for Existing Systems AMC and SDDC

The Contractor will review primitives (e.g., performers, systems, system functions, activities, information exchanges) identified while researching documentation (Para 1.3.2.1.1) and conducting interviews (Para 1.3.2.1.2) to determine whether or not these primitives exist within the Government designated enterprise architecture tool environment. If the primitives don’t exist, the Contractor shall propose the primitives to the COR for approval.

Deliverable: DoDAF architecture views, architecture primitives

1.3.2.1.12. Scope and Assemble Primitives into Architecture Views for Existing Systems AMC and

SDDC

The Contractor shall collect, organize, correlate, and store the architecture data required for architecture development and document the architectural results in the Government designated enterprise architecture tool environment following Government approved procedures. The Contractor shall support primitive registration, architecture model construction, and architecture markup/coordination, using Government-provided tools in Section 3. This includes using multiple architecture modeling techniques (e.g., Entity Relationship Modeling, Swimlane Process Mapping, Functional Decomposition Tree Modeling, Business Process Modeling Notation (BPMN), Data Flow Modeling, Integrated Definition for Functional 0 (IDEF0) modeling, IDEF1X modeling, Event Trace Modeling, Dependency Analysis Modeling, Semantic Net Modeling, Unified Modeling Language (UML) techniques, etc.), and engineering techniques such as use cases. The Contractor shall mature the architecture views throughout the review and approval process and ensure all architecture artifacts produced comply with DoDAF and Government approved templates and guidelines.

Deliverable: DoDAF architecture views

1.3.2.1.13. Resolve Discrepancies for Existing Systems AMC and SDDC

The Contractor shall identify all architecture discrepancies during architecture model development and review processes. Obtaining Government approvals as necessary, the Contractor shall document the actions taken to resolve and adjudicate the discrepancies and provide a Monthly Discrepancy Report to the COR. The report may be in a format selected by the Contractor. The monthly report due date will be determined by the COR and may vary between one (1) to ten (10) business days.

Deliverable: Discrepancy and Resolution Report

1.3.2.1.14. Maintain Reference Models for Existing Systems AMC and SDDC

The Contractor shall review the existing reference models and suggest modifications to the COR. Upon approval of suggested changes by the COR, the Contractor shall implement changes. As required by the COR, the Contractor shall refine existing, or develop new, reference models which may include the development of ontology’s and taxonomies. New models may include the use of existing published models, such as the Joint Capability Areas (JCAs), Plan-Order-Ship-Track-Pay (POST-P), or the Joint Common System Function List (JCSFL). Requirements for the modification or development of reference models are estimated to be up to 100 times per fiscal year.

Deliverable: Suggested reference model changes

1.3.2.2. Develop New Architectures

1.3.2.2.1. Research Documentation for New Systems USTRANSCOM

The Contractor shall review published guidance identified in Section 3 as the initial source to gain an understanding of processes, systems, organizations, etc. that will influence architectural development efforts. The COR will identify other published guidance relevant to each architecture development effort.

Deliverable: Architecture views, overview and summary information

1.3.2.2.2. Conduct Interviews for New Systems USTRANSCOM

The Contractor shall conduct interviews with subject matter experts, sponsors, and participating organizations prior to and during architecture development. This iterative process requires the Contractor to obtain information from the business operations communities to develop the architecture views.

Deliverable: DoDAF architecture views

1.3.2.2.3. Identify Primitives for New Systems USTRANSCOM

The Contractor will review primitives (e.g., performers, systems, system functions, activities, information exchanges) identified while researching documentation (Para 1.3.2.1.1) and conducting interviews (Para 1.3.2.1.2) to determine whether or not these primitives exist within the Government designated enterprise architecture tool environment. If the primitives don’t exist, the Contractor shall propose the primitives to the COR for approval.

Deliverable: DoDAF architecture views, architecture primitives

1.3.2.2.4. Scope and Assemble Primitives into Architecture Views for New Systems USTRANSCOM

The Contractor shall collect, organize, correlate, and store the architecture data required for architecture development and document the architectural results in the Government designated enterprise architecture tool environment following Government approved procedures. The Contractor shall support primitive registration, architecture model construction, and architecture markup/coordination, using Government-provided tools in Section 3. This includes using multiple architecture modeling techniques (e.g., Entity Relationship Modeling, Swimlane Process Mapping, Functional Decomposition Tree Modeling, Business Process Modeling Notation (BPMN), Data Flow Modeling, Integrated Definition for Functional 0 (IDEF0) modeling, IDEF1X modeling, Event Trace Modeling, Dependency Analysis Modeling, Semantic Net Modeling, Unified Modeling Language (UML) techniques, etc.), and engineering techniques such as use cases. The Contractor shall mature the architecture views throughout the review and approval process and ensure all architecture artifacts produced comply with DODAF and Government approved templates and guidelines.

Deliverable: DoDAF architecture views

1.3.2.2.5. Resolve Discrepancies for New Systems USTRANSCOM

The Contractor shall identify all architecture discrepancies during architecture model development and review processes. Obtaining Government approvals as necessary, the Contractor shall document the actions taken to resolve and adjudicate the discrepancies and provide a Monthly Discrepancy Report to the COR. The report may be in a format selected by the Contractor. The monthly report due date will be determined by the COR and may vary between one (1) to ten (10) business days.

Deliverable: Discrepancy and Resolution Report

1.3.2.2.6. Develop Reference Models for New Architectures USTRANSCOM

The Contractor shall review the existing reference models and suggest modifications to the COR. Upon approval of suggested changes by the COR, the Contractor shall implement changes. As required by the COR, the Contractor shall refine existing, or develop new, reference models which may include the development of ontology’s and taxonomies. Examples of reference models include, but are not limited to the Joint Capability Areas (JCAs), Plan-Order-Ship-Track-Pay (POST-P), Joint Common System Function List (JCSFL), and Supply Chain Operations Reference (SCOR) Model. Reference model modifications may occur as part of the architecture development process.

Deliverable: Suggested reference model changes, new reference models

1.3.2.2.7. Research Documentation for New Systems AMC and SDDC

The Contractor shall review published guidance identified in Section 3 as the initial source to gain an understanding of processes, systems, organizations, etc. that will influence architectural development efforts. The COR will identify other published guidance relevant to each architecture development effort.

Deliverable: Architecture views, overview and summary information

1.3.2.2.8. Conduct Interviews for New Systems AMC and SDDC

The Contractor shall conduct interviews with subject matter experts, sponsors, and participating organizations prior to and during architecture development. This iterative process requires the Contractor to obtain information from the business operations communities to develop the architecture views.

Deliverable: DoDAF architecture views

1.3.2.2.9. Identify Primitives for New Systems AMC and SDDC

The Contractor will review primitives (e.g., performers, systems, system functions, activities, information exchanges) identified while researching documentation (Para 1.3.2.1.1) and conducting interviews (Para 1.3.2.1.2) to determine whether or not these primitives exist within the Government designated enterprise architecture tool environment. If the primitives don’t exist, the Contractor shall propose the primitives to the COR for approval.

Deliverable: DoDAF architecture views, architecture primitives

1.3.2.2.10. Scope and Assemble Primitives into Architecture Views for New Systems AMC and SDDC

The Contractor shall collect, organize, correlate, and store the architecture data required for architecture development and document the architectural results in the Government designated enterprise architecture tool environment following Government approved procedures. The Contractor shall support primitive registration, architecture model construction, and architecture markup/coordination, using Government-provided tools in Section 3. This includes using multiple architecture modeling techniques (e.g., Entity Relationship Modeling, Swimlane Process Mapping, Functional Decomposition Tree Modeling, Business Process Modeling Notation (BPMN), Data Flow Modeling, Integrated Definition for Functional 0 (IDEF0) modeling, IDEF1X modeling, Event Trace Modeling, Dependency Analysis Modeling, Semantic Net Modeling, Unified Modeling Language (UML) techniques, etc.), and engineering techniques such as use cases. The Contractor shall mature the architecture views throughout the review and approval process and ensure all architecture artifacts produced comply with DODAF and Government approved templates and guidelines.

Deliverable: DoDAF architecture views

1.3.2.2.11. Resolve Discrepancies for New Systems AMC and SDDC

The Contractor shall identify all architecture discrepancies during architecture model development and review processes. Obtaining Government approvals as necessary, the Contractor shall document the actions taken to resolve and adjudicate the discrepancies and provide a Monthly Discrepancy Report to the COR. The report may be in a format selected by the Contractor. The monthly report due date will be determined by the COR and may vary between one (1) to ten (10) business days.

Deliverable: Discrepancy and Resolution Report

1.3.2.2.12. Develop Reference Models for New Architectures AMC and SDDC

The Contractor shall review the existing reference models and suggest modifications to the COR. Upon approval of suggested changes by the COR, the Contractor shall implement changes. As required by the COR, the Contractor shall refine existing, or develop new, reference models which may include the development of ontology’s and taxonomies. Examples of reference models include, but are not limited to the Joint Capability Areas (JCAs), Plan-Order-Ship-Track-Pay (POST-P), Joint Common System Function List (JCSFL), and Supply Chain Operations Reference (SCOR) Model. Reference model modifications may occur as part of the architecture development process.

Deliverable: Suggested reference model changes, new reference models

1.3.2.3. Architecture Configuration Management

The Contractor shall provide administrative support to the Government configuration management process. The Contractor shall schedule, arrange and set-up a facility, prepare a draft agenda, and compile presentation materials for the Configuration Control Boards (CCB). The Contractor shall provide draft agendas to the COR for approval no later than (5) business days prior to the CCB. The Contractor shall provide minutes of each CCB to the COR no later than five (5) business days after each meeting.

Meetings shall be held on a quarterly basis or as required by the COR.

Deliverable: CCB agendas, presentation materials, minutes

1.3.2.4. Architecture Liaison

1.3.2.4.1. AMC Architecture Liaison

The Contractor shall review architectures from a process or operations perspective. The Contractor shall facilitate the modification, update, documentation, and coordination of architecture views and artifacts within the operations communities for existing systems. The Contractor shall assist the Government in assessing deployment and distribution challenges, recommending new business rules, and enabling better resource allocation decisions while improving delivery of forces and sustainment to desired points of effect. The Contractor shall provide analyses and recommendation reports by Government directed topic on business process improvement proposals and new business operations requirements documents involving materiel and personnel deployment, distribution, and sustainment operations. The format for analyses and recommendations will be determined by the Government and may include, but is not limited to point papers, white papers, and briefing slides. The Contractor shall also provide operational architecture artifacts to support requirements proposals. The Contractor shall provide analyses and recommendations and operational architecture artifacts quarterly or as required by the COR.

Deliverable: Analyses and recommendation reports, DoDAF architecture artifacts

1.3.2.4.2. USTRANSCOM Architecture Liaisons

The Contractor shall review architectures from a process or operations perspective. The Contractor shall facilitate the modification, update, documentation, and coordination of architecture views and artifacts within the operations communities for new systems and initiatives. The Contractor shall assist the Government in assessing deployment and distribution challenges, recommending new business rules, and enabling better resource allocation decisions while improving delivery of forces and sustainment to desired points of effect. The Contractor shall provide analyses and recommendation reports by Government directed topic on business process improvement proposals and new business operations requirements documents involving materiel and personnel deployment, distribution, and sustainment operations. The format for analyses and recommendations will be determined by the Government and may include, but is not limited to point papers, white papers, and briefing slides. The Contractor shall also provide operational architecture artifacts to support requirements proposals. The Contractor shall provide analyses and recommendations and operational architecture artifacts quarterly or as required by the COR.

Deliverable: Analyses and recommendation reports, DoDAF architecture artifacts

1.3.2.5. Review Architectures

The Contractor shall conduct architecture reviews for externally developed (non- USTRANSCOM/AMC/SDDC) architectures as required by the COR. The Contractor shall record all concerns identified during the architecture review in a comments matrix, in the format provided by the Government, and provide the completed comments matrix to the COR. External architecture reviews are estimated at ten (10) per fiscal year for USTRANSCOM. External architecture reviews are estimated at two (2) each for AMC and SDDC. The due dates for the comments matrices will be determined by the COR and may vary between one (1) to ten (10) business days.

Deliverable: Comments matrice

1.3.2.6. Conduct Architecture Analysis

1.3.2.6.1. Enterprise Impact Analysis

The Contactor shall perform analysis of architecture projects by using graphical, statistical, and document-based techniques. The Contractor shall perform enterprise impact analysis of operational, system, and programmatic changes as required by the COR. The analysis consists of reviewing internally/externally developed architectures for potential linkage and/or integration with DOD, USTRANSCOM, Component, Army, or Air Force architectures. For example, the analysis includes activities such as comparing performers, need lines, resource flows, activities, system interfaces/exchanges, and technical standards in the parent architecture and/or system-focused/program architectures to the architecture being reviewed. Analysis may also include assessments and roadmap/migration planning documentation to provide users with accurate, complete, and concise architecture information. After the conclusion of each analysis project, the Contractor shall provide the enterprise impact analysis to the COR. Assessments and recommendations may be in the format of comment matrix, reports, point papers, talking papers, emails, or presentations. Requests for architecture analysis are estimated at four (4) per fiscal year. The due dates for the analysis documentation will be determined by the COR and may vary between one (1) and ten (10) business days.

Deliverable: Enterprise Architecture impact analysis documentation

1.3.2.6.2. Enterprise Requirements and Review Analysis

The Government will identify enterprise information requirements for review and analysis. The Contractor shall support a team approach which uses the enterprise architecture to evaluate potential requirements for gaps and redundancies. The Contractor shall support this approach by reviewing enterprise information requirements documents to evaluate the linkage to the existing architecture. As the needs are (re-)defined, the Contractor shall use the architecture views as developed in Task 2 (Para 1.3.2.2) to model/illustrate the requirement. Additionally the Contractor shall assist the Government in developing Courses of Action and use cases. Requests for architecture analysis of enterprise information requirements are estimated at twenty (20) per fiscal year. Upon completion of the analysis for each enterprise information requirement, the Contractor shall provide inputs to the COR. The suspense for inputs will be determined by the COR. The due dates will be relayed to the Contractor by the COR and can vary between two (2) and twenty (20) business days depending on the urgency and complexity of the requirement.

Deliverable: Architecture Analysis

1.3.2.6.3. Enterprise Architecture Support for Existing System Business Case Analysis (BCA)

The Contractor shall provide architecture support for USTRANSCOM business case analysis efforts for existing systems. Requests for Government approved BCA support is estimated at three (3) per fiscal year. For each Government approved BCA, the Contractor shall provide a Rough Order of Magnitude (ROM) on manpower resources required prior to perform the architecture analysis. When developing the BCA, the Contractor shall use the existing architecture to perform the analysis. Once complete, the deliverable will be submitted to the COR. The due dates for the analysis will be determined by the COR and can vary between five (5) and fifteen (15) business days.

Deliverable: Architecture analysis

1.3.2.6.4. Enterprise Architecture Support for New System Business Case Analysis (BCA)

The Contractor shall provide architecture support for USTRANSCOM business case analysis efforts for new systems and initiatives. Requests for Government approved BCA support is estimated at three (3) per fiscal year. For each Government approved BCA, the Contractor shall provide a Rough Order of Magnitude (ROM) on manpower resources required prior to perform the architecture analysis. When developing the BCA, the Contractor shall use the existing architecture to perform the analysis. Once complete, the deliverable will be submitted to the COR. The due dates for the analysis will be determined by the COR and can vary between five (5) and fifteen (15) business days.

Deliverable: Architecture analysis

1.3.2.7. Information Resource Catalogue (IRC)

The Contractor shall collect and maintain information about the automated information systems used by USTRANSCOM/AMC/SDDC to conduct their respective missions. The Contractor shall provide monthly status as part of the Monthly Cost/Status and Resource Utilization Report to the COR identifying any updates and/or changes that have been incorporated into the IRC. Contractor shall collect and maintain the information below:

-Application type -Functional area -Security level -Initial operational capability date and full operational capability date, if available -Data system designator and system identifier as applicable -Description -Migration information -Planned upgrades -Technology/platforms -Interfaces with other systems

1.3.3. Task 3 – Data Management

1.3.3.1. USTRANSCOM Enterprise Data Quality (DQ)

The Contractor shall provide data quality support. The Contractor shall identify Enterprise DQ issues that are reported by programs or business operations customers. The Contractor shall assist programs/services to resolve data quality problems with external legacy databases, multiple systems or services. The Contractor shall elevate issues through the COR to the DQ Working Group (DQWG), if needed. The Contractor shall identify proactive DQ issues through the active monitoring and problem resolution of non-compliant data. In the current environment this monitoring will be accomplished using multiple software tools identified in Section 3, Paragraph 1.

1.3.3.1.1. Operational Data Transaction Assessments

The Contractor shall develop for COR approval DQ business rules and procedures ensuring timely and accurate transmission of data using the six characteristics of DQ (Accuracy, Completeness, Consistency, Timeliness, Uniqueness, and Validity). The DQ business rules shall be delivered to the COR and will be stored in a common tool(s), using a methodology consistent with the published USTRANSCOM Data

Strategy. For environments where the Contractor can monitor online transactions, the Contractor shall develop and receive automated alerts via dashboards to the Enterprise DQ Office. The alerts will identify errors during data transmission or errors detected in critical data. The Contractor shall prepare draft Memorandums of Agreement (MOAs) between the DQ Office and the programs that describe their agreement on how to identify and resolve data quality issues. The Contractor shall baseline the data and identify potential business process improvements, system changes, or process workarounds to achieve and improve data quality. The due dates for the draft MOAs will be determined by the COR and can vary between five (5) and fifteen (15) business days. DQ business rules shall be delivered to the COR for approval within 30 days after contract start and updated as required.

Deliverable: DQ Business Rules, Draft MOAs

1.3.3.1.2. Operational Metrics

The Contractor shall interact with the various business operations organizations or systems to identify, capture, and analyze/monitor data to improve data across the USTRANSCOM enterprise. The Contractor shall baseline current data assessment statistics based on the existing architecture, identify any shortfalls, and provide recommended courses of action. The Contractor shall provide suggested metrics using the six DQ characteristics in paragraph 0 to the COR. The DQ metrics and courses of action shall be delivered monthly to the COR.

Deliverable: DQ metrics, courses of action

1.3.3.1.3. Data Quality Working Group (DQWG)

The Contractor shall schedule, arrange and set-up a facility, and assist in leading the monthly DQWG meetings. The Contractor shall prepare draft agendas and presentation materials for the meetings and provide them to the COR for approval within five (5) business days prior to the meeting. Upon the COR’s approval, the Contractor shall provide presentation materials to participants. The Contractor shall prepare minutes and provide them to the COR within five (5) business days after the DQWG meetings and ten (10) business days after the annual DQ Summit. The Contractor shall post the approved minutes and presentation materials on designated USTRANSCOM portals and send an email to the participants informing them that the minutes have been posted. The Contractor shall maintain the DQWG Charter and provide updates as required by the COR.

Deliverable: DQWG presentation materials, minutes, and DQWG Charter

1.3.3.2. AMC Data Quality Support

For AMC only, the Contractor shall monitor, evaluate, and test data integration efforts for new AMC systems (C2, planning, transportation, logistics, and financial system functions) and prototyping initiatives, regardless of data exchange methods, to ensure the data is consistent, certified and reconcilable using criteria such as timeliness, accuracy, completeness, validity, consistency, and uniqueness.