J - Attch 1 - PWS.docx

FA4452-12-R-0001

Section J - Attachment 1 Performance Work Statement Air Mobility Command Directorate of Communications (AMC/A6IS) Global Air Transportation Execution System (GATES) Application & System Support 03 April 2012

1. DESCRIPTION OF SERVICES

1.1. Background. GATES is developed and maintained by the United States Air Force (USAF) Headquarters (HQ) Air Mobility Command (AMC). GATES originally replaced legacy systems supporting the AMC transportation mission with a modernized, fully integrated and significantly enhanced global transportation system using an open systems infrastructure and a shared relational database. In January 2006, United States Transportation Command (USTRANSCOM) directed GATES to integrate the Defense Courier Service (DCS) functionality into the program. In April 2006, USTRANSCOM directed the integration of the United States Army’s Surface Deployment and Distribution Command’s Worldwide Port System (WPS) into GATES. GATES is now a joint port management system supporting Defense Transportation System (DTS) and Distribution Process Owner (DPO) migration strategies. GATES development includes, but is not limited to, meeting DTS architecture.

1.2. Scope of Work. The contractor shall comply with the appropriate Department of Defense (DOD), Services, USTRANSCOM, and AMC architectures, programs, policies, standards and guidelines (e.g. Security Technical Implementation Guide (STIG), Net-Centric Enterprise Services (NCES), Defense and Information Systems Network (DISN)). The contractor shall provide GATES system upgrade releases that address architectural tuning; functional community (DCS, aerial port, and water port users) enhancements; and operations and maintenance on the GATES software and specialized equipment. The facilities supporting GATES will permit functional community transactions and data flows into and out of locations where communications can support the traffic using a variety of communications methods.

1.2.1. GATES is designed around a client-server environment composed of web applications, server processes, Commercial Off the Shelf (COTS) relational database management system, database schema, and supporting utility scripts. The COTS supporting the current design include Sybase, UNIX, Oracle, and Microsoft products. This environment runs on host infrastructures maintained by the Services (Air Force, Army, Navy, Marines) and/or major commands. The architecture also includes wireless and Automated Information Technology (AIT) capabilities to include unique specialized equipment. Current GATES specialized equipment is the Flight Information Display Systems (FIDS), mobile work stations, label printers, baggage tag printers, boarding pass printers, Radio Frequency Identification (RFID) tag burning stations, identification card readers, kiosks, and handheld terminals. The GATES architecture utilizes Virtual Private Networks (VPN), AIT servers, Remote GATES (RGATES), a Windows platform on a server/workstation; and Deployed GATES (DGATES), Windows platform on a laptop, to support certain locations. The AIT server, RGATES, and DGATES are also considered specialized equipment.

General network operations and maintenance (O&M) is handled by the government, to include local network updates/patches as part of their security policies. GATES runs on various networks and configurations maintained by the government through numerous Services and commands. Due to the GATES architecture and specialized equipment, the contractor responsibilities go beyond just engineering the capability and include integrating GATES unique capabilities into the variety of networks and configurations. For example, the GATES application resides on a common computer that the government can push to the Federal Desktop Core Configuration (FDCC). If the government pushes an FDCC patch and the computer stops working, the government would troubleshoot why the computer is not working. The contractor shall get involved if the computer is working properly and the troubleshooting is related to the GATES application or associated GATES peripheral equipment. Although the contractor focus is on GATES functionality/interoperability, this is a collaborative effort (i.e. Java update). This contractor support includes, but is not limited to, specialized printers, hand-held terminals, kiosks, and FIDS. The contractor’s effort also involves the support of the RGATES and DGATES application on government managed equipment. Support will include assistance in establishing connectivity with GATES and managing their GATES accounts. The majority of this work is done remotely.

1.3. Specific Support Services.

Task 1 – Enterprise IT Policy and Planning Task 2 – Integrated Solutions Management Task 3 – Market Research and Prototyping Task 4 – Custom Application Development Task 5 – Product Integration Task 6 – Asset Management Task 7 – Security Engineering Certification and Accreditation Task 8 – Operations Support Task 9 – Other Direct Costs

The contractor shall be responsible for its own overall responsiveness, cost control, adherence to schedules, responsible and cooperative behavior, technical quality of work, management of contractor team’s efforts (including level of understanding of the AMC, SDDC, USTRANSCOM DCS, and USTRANSCOM overall missions), and commitment to customer satisfaction. Except for those items specifically stated as government-furnished, the contractor shall furnish everything needed to perform this contract. In the absence of specific contract requirements, the contractor shall use the software development industry standards and industry best practices for providing the products and services required by the contract.

1.3.1. Task 1 – Enterprise IT Policy and Planning. In providing plans, reports and technical assistance, the contractor shall accomplish the following:

1.3.1.1. Subtask 1 – Documents. The contractor shall prepare, submit, and maintain the following documents:

1.3.1.1.1. Plans and Agreements

· Technical & Management Work Plan (Contract Data Requirements List (CDRL) A001)

1.3.1.1.2. Reports

1.3.1.1.3. Procedures & descriptions-

1.3.1.1.4. Other

1.3.1.2. Subtask 2 – Attend Meetings. This subtask addresses CDRLs A001, A004, A005, and B017. The contractor shall attend the following meetings:

1.3.1.2.1. Contract and Program Status Review (monthly) for which the contractor in concert with the PMO prepare the agenda and provide written minutes. (CDRL A004). The purpose of this meeting is to review and update the contractor’s Technical & Management Work Plan (CDRL A001), brief the progress of each assigned task (CDRL B017), address schedule tracking concerns/impacts to the master schedule (CDRL A005), and solicit input from the Program Management Office (PMO) to obtain concurrence of work performed by the contractor.

1.3.1.2.2. Task Management Review (unofficially weekly)

1.3.1.2.3. Program Management Review (monthly)

1.3.1.2.4. CIO Program Review Process Preparation (bi-annually)

1.3.1.2.5. Support Ad Hoc Teams (historically bi-weekly)

1.3.1.2.6. Accreditation and Security Support (historically weekly for accreditation and daily for security)

1.3.1.2.7. Information Support Plan (ISP) Support (as architecture changes or software releases dictate)

1.3.1.2.8. Technical Working Group (TWG) Support (historically weekly)

1.3.1.2.9. Process Improvement Management Meetings (bi-weekly)

1.3.1.2.10. USTRANSCOM and AMC Sponsored Meetings (historically bi-weekly)

1.3.1.3. Subtask 3 – Task Progress. This subtask addresses CDRLs A001, A002, A005, A007 and B017. The contractor shall provide visibility/monitoring of task progress by accomplishing the following:

1.3.1.3.1. Maintain and annotate a project schedule of all developer activities associated with the efforts described in tasks 1 through 5 utilizing the tools identified by the government. (CDRL A005)

1.3.1.3.2. Populate each schedule with sufficient task activities to ensure visibility of management and tracking for each milestone. (CDRL A005)

1.3.1.3.3. Identify, within the schedule, the resources required to accomplish all task activities. Contractor may use generic resource identification. (CDRLs A001, A007)

1.3.1.3.4. Determine and annotate appropriate milestones needed to ensure/monitor progress. (CDRL A005)

1.3.1.3.5. Baseline all schedules with concurrence by the government. (CDRLs A002, A005)

1.31.3.6. Update schedule progress on a weekly basis using government-provided tools. (CDRL B017)

1.3.1.3.7. Provide schedule status, risks, issues and progress. (CDRLs A002, B017)

1.3.1.3.8. Provide Contract Performance Report. (CDRL A002)

1.3.1.4. Subtask 4 – Meeting and Conference Support. This subtask addresses CDRL A004.

1.3.1.4.1. The contractor shall generate presentation materials in order to aid in the discussion of technical issues and shall support conferences, meetings, demonstrations, and Technical Interchange Meetings/Reviews. The contractor shall also provide agendas, meeting minutes, and track action items associated with the aforementioned meetings/reviews. (CDRL A004)

1.3.2. Task 2 – Integrated Solutions Management. This task addresses CDRLs B001, B002, B011, B014, B020, B021, and B026.

1.3.2.1. The contractor shall integrate software/firmware/hardware solutions supporting GATES AIT and other special equipment requirements. This includes established efforts to migrate the current AIT software to an updated platform chosen by the government. Efforts consist of a Radio Frequency (RF) and a non-RF version of the software to support locations without any approved frequency. The contractor shall assist the government by testing government chosen products and making recommendations. (CDRLs B001, B002) The contractor shall develop, update, and maintain installation plans and guides, (CDRLs B020, B021) including the GATES Handheld Terminal Handbook (CDRL B026) that provides instructions on the use of the GATES equipment and application.

1.3.2.2. Using the software release process described in para 1.3.4.5., the contractor shall develop solutions supporting (CDRLs B011, B014) the integration of water port functionality into the GATES application.

1.3.2.3. Future negotiated tasks: The GATES PMO foresees tasks associated with integrating RFID, both active and passive, Enterprise Integration Lab (EIL), Common Computing Environment (CCE), and services within a Services Oriented Architecture (SOA). Future negotiated tasks may also be associated with integrating new solutions into the GATES application design and supporting architecture.

1.3.3. Task 3 – Market Research and Prototyping. This task addresses CDRL A008.

1.3.3.1. The contractor shall evaluate commercial-off-the-shelf (COTS) and other solutions to support GATES applications, AIT, and other special equipment requirements. This includes established efforts to migrate the current AIT software to an updated platform chosen by the government. Efforts consist of a RF and a non-RF versions of the software to support locations without any approved frequency. The contractor shall assist the government by testing government chosen products and making recommendations. (CDRL A008)

1.3.3.2. Future negotiated tasks: The GATES PMO foresees tasks associated with RFID, both active and passive, Electronic Data Interchange (EDI), and services within a SOA implementation. Future negotiated tasks may also be associated with the GATES application design and supporting architecture, such as database and replication process improvements.

1.3.4. Task 4 – Custom Application Development

1.3.4.1. Subtask 1 – Configuration Management (CM). This subtask addresses CDRLs A005, A007, A008, B012, B013, B014, B016, B018, and B019. The contractor shall provide a software configuration management process that incorporates the following:

1.3.4.1.1. Using MIL HDBK 61A, ISO 12207, and EIA 649 guidance, the contractor shall institute and maintain a configuration management process to ensure engineering and administrative disciplines (which include configuration identification, configuration control, status accounting, and auditing) are implemented for all development activities. The contractor shall identify the configuration of all work products (to mean baselines as well as other supporting work products), systematically control changes, and maintain the integrity and traceability of all work products throughout their lifecycle. The contractor shall ensure configuration is identified, reliable, traceable, and repeatable, and that all relationships among work products, versions of work products, as well as auditing and reporting on the changes that are made are implemented throughout the development process. (CDRL B016)

1.3.4.1.2. In addition to the general requirements described above, the contractor shall accomplish the following:

1.3.4.1.2.1. Establish and employ internal configuration management of processes and procedures for all development work products.

1.3.4.1.2.2. Identify the configuration items (including COTS software), components, and related work products, to include baseline documentation, and place these items under configuration control. (CDRLs A008 and B014)

1.3.4.1.2.3. Establish and maintain a configuration management and change control system for controlling configuration items, components, and work products. (CDRLs B012, B013, B016, B018, B019)

1.3.4.1.2.4. Establish version control to ensure integrity and tracking of all work products.

1.3.4.1.2.5. Identify, track, and control change requests (including those changes intended to resolve identified problems) for the configuration items. (CDRLs A005, B012, B013, B016, B018, B019)

1.3.4.1.2.6. Establish configuration control of all supporting documentation, changes to the documentation, and version control of all documentation supporting work products, and ensure product documentation reflects all changes to a work product. (CDRLs B012, B013, B016, B018, B019)

1.3.4.1.2.7. Provide backup controls to ensure work products are not lost or damaged due to resource, equipment, or power failures.

1.3.4.1.2.8. Establish and employ product CM processes and procedures to ensure the integrity of all delivered baselines and work products. (CDRL B016)

1.3.4.1.2.9. Establish and maintain records describing configuration items. (CDRLs B012, B013, B016, B018, B019)

1.3.4.1.2.10. Ensure internal controls are in place supporting all baselines and work products.

1.3.4.1.2.11. Ensure configuration audits are available supporting the integrity of the configuration.

1.3.4.1.2.12. Ensure the internal configuration status accounting system records the tracking of baselines and work products and their modification history throughout the life cycle. (CDRL A007)

1.3.4.1.1.2.13. Perform, along with a government representative, a configuration Functional Configuration Audit/Physical Configuration Audit (FCA/PCA) prior to delivery of any baseline or work product to ensure accuracy and completeness of the deliverable.

1.3.4.1.2.14. Record and present to the government the results of the configuration audit (CDRL A008), to include action taken by the contractor to correct deficiencies noted during the audit. The contractor shall correct all deficiencies noted during the audit prior to presenting the deliverable for government acceptance.

1.3.4.1.2.15. Coordinate closely with government Configuration Manager to ensure continuity of configuration management processes and practices are maintained and controlled.

1.3.4.1.2.16. Ensure development CM processes and procedures complement the government’s Configuration Management Plan (CMP). (CDRL B016)

1.3.4.1.2.17. Provide traceability of all Change Requests (CRs) throughout the system lifecycle via a requirement traceability tracking tool. (CDRLs B012, B013, B016, B018, B019)

1.3.4.2. Subtask 2 – Quality Assurance. This subtask addresses CDRL B015. Provide a quality assurance program that incorporates the following:

1.3.4.2.1. The contractor shall establish and maintain a Quality Assurance Program in accordance with ISO IEC 26514:2008 and Software Engineering Institute (SEI) Capability Maturity Model - Integrated (CMMI) Level 3-Defined requirements or equivalent processes approved in writing by the Contracting Officer’s Representative (COR). In establishing and maintaining a Quality Assurance Program, the contractor shall plan, develop, and implement procedures and practices to ensure that all requirements of the contract are complied with fully. The government representative shall audit all processes and products as outlined in the Quality Program Plan (CDRL B015). The Quality Program Plan shall also include a non-compliance reporting and tracking process.

1.3.4.2.2. The contractor shall support government reviews and audits of all services and support provided under this contract. The government reserves the right to authorize an independent verification and validation of the contractors procedures, methods, data, equipment, and other services provided at any time during the performance of this contract. At government’s discretion, registered ANSI/ANSQ Q9000 series suppliers may not be subjected to audit/assessment by government if they provide the government with a copy of their registration certification issued by an approved ISO registrar.

1.3.4.3. Subtask 3 – Work Break Down Structure & Performance-Based Management. This subtask addresses CDRLs A002, A005, and B017.

1.3.4.3.1. The contractor shall establish, integrate, and report the program-wide Work Breakdown Structure (WBS) to lower level WBS, as depicted in Figure 1, below. The contractor shall maintain sufficient detail within the WBS to support the Program’s migration to Performance-Based Management and shall support the Program’s efforts in tracking and maintaining the Integrated Master Schedule within Project Server. The WBS shall align with the tasks described in this PWS and as described in MIL-HDBK-881, Department of Defense Handbook Work Breakdown Structure, which may be further defined or modified by the Program. (CDRLs A002, A005, and B017)

1.0 GATES

1.1 Enterprise IT Policy and Planning

1.1.1 Documents

1.1.2 Meeting and Conference Support

1.1.3 Management Reviews

1.2 Integrated Solutions Management

1.3 Market Research and Prototyping

1.4 Custom Application Development

1.4.1 Configuration Management

1.4.2 Quality Assurance

1.4.3 Work Break Down Structure & Performance-Based Management

1.4.4 Interoperability and architecture support

1.4.5 Software Release Process

1.4.5.1 Analysis

1.4.5.2 Design

1.4.5.3 Develop

1.4.5.4 Test

1.4.5 System Integration

1.5 Product Integration

1.6 Asset Management

1.7 Security Engineering Certification and Accreditation

1.7.1 Certification and Accreditation Support

1.7.2 Vulnerability Management

1.7.3 GATES Security and Documentation Support

1.8 Operations Support

1.8.1 Fielding Support

1.8.2 Technical Support

1.8.3 Functional Help Desk

1.8.4 Location Support & Training Support

1.9 Hardware

Figure 1 Work Breakdown Structure

1.3.4.4. Subtask 4 – Interoperability and Architecture Support. This subtask addresses CDRLs A008, B003, B004, B006, and B011. The contractor shall provide interoperability and architecture support by accomplishing the following tasks:

1.3.4.4.1. Ensure that the technical designs and system elements comply with the Defense Information Technology Standard Registry (DISR). (CDRLs A008, B003, B004, B006, B011)

1.3.4.4.2. Design technical solutions to operate within the GATES framework, and interoperate with other systems with which GATES interfaces. (CDRL A008)

1.3.4.4.3. Ensure technical design and solutions are compatible with DOD infrastructure, e.g., Standard Desktop Configuration, and the operational environment. (CDRLs A008, B003, B004, B006, B011)

1.3.4.4.4. Participate in developing and validating Department of Defense Architecture Framework (DoDAF) products. The contractor shall use AMC Architecture Tool (AMCAT) for the source of all DoDAF compliant architectures.

1.3.4.4.5. Participate in supporting Air Force, Joint, and Federal agencies certifications.

1.3.4.4.6. Develop prototypes as proof of concepts. (CDRL A008)

1.3.4.5. Subtask 5 – Software Release Process. This subtask addresses CDRL B003.

1.3.4.5.1. The contractor shall provide the support necessary to maintain the GATES software via the government’s approval process. For subsequent releases beginning with version 6.0, the contractor shall provide and follow its Software Development Plan (CDRL B003) that includes the contractor’s approach to analyze, design, develop (code), and test the software release process as illustrated in Figure 2 and described in the following subtasks. Current releases will be delivered as directed by the GATES PMO. GATES produces a Version Release List (VRL) through its configuration control boards and Joint Functional Review Board creation of a prioritized requirements listing. The details for the individual requirements are maintained in a Clear Quest database. (Figure 2 depicts the software milestone review process. The details are addressed in the PWS paragraphs.)

Figure 2 Software Milestone Reviews

1.3.4.6. Subtask 6 – Analyze. This subtask addresses CDRLs A008, B004, B009, B018, B019, B024, and B025. The contractor shall provide analysis support by accomplishing the following tasks:

1.3.4.6.1. Propose (when necessary) refinements and analysis to (but not limited to) use cases, Baseline Change Requests, and Software Problem Reports in accordance with business practices, processes, procedures, systems, and performance measures. (CDRLs A008, B004, B009, B018, B019, B024, B025)

1.3.4.6.2. Prepare use cases/user stories. (CDRL B024)

1.3.4.6.3. Conduct Joint Application Development (JAD) sessions for software requirements.

1.3.4.6.4. As a result of JAD sessions, propose changes to business practices, processes, procedures, systems, and performance measures. (CDRL A008)

1.3.4.6.5. Analyze and, if appropriate, provide recommended changes to version requirements documents/lists. (CDRL A008)

1.3.4.6.6. Analyze and, if appropriate, provide recommended changes to the requirements list test pass/fail criteria. (CDRL A008)

1.3.4.7. Subtask 7 – Design. This subtask addresses CDRLs B006, B007, B008, B011, and B024. The contractor shall design software to meet requirements by completing the following tasks:

1.3.4.7.1. Meet the plans, specifications, and descriptions accepted by the government under Task 1 and the government approved analysis conducted by the contractor under Subtask 1.3.4.1.

1.3.4.7.2. Design and document software architecture, including incorporating business rules.

1.3.4.7.3. Prepare software design products to support technical review and approval of software direction and decisions. (CDRLs B006, B007, B008, B011, B024)

1.3.4.7.4. Conduct design reviews.

1.3.4.7.5. Provide sustainment and configuration management of the system-centric Physical Data Model and Data Dictionary.

1.3.4.7.6. Use government reference data source, currently provided by USTRANSCOM Reference Data Management (TRDM) System, as the authoritative source of system reference data.

1.3.4.7.7. Participate in the Architecture Data Integration Group (ADIG) to assist the government with the sustainment and configuration management of the government-provided enterprise-level Logical Data Model (LDM) and the Data Dictionary.

1.3.4.7.8. Assist the government in the sustainment and configuration management of the system-centric LDM and mapping of the PDM to the government-provided Enterprise LDM.

1.3.4.7.9. Submit proposed Service Definition schemas for government approval prior to establishing a system/service or interface. (CDRL B006)

1.3.4.7.10. Participate in the Systems/Services Development Working Group to assist the government in the sustainment and configuration management of the government-provided enterprise-level and system centric Interface Design Documents (CDRL B006) and Services Definition Framework.

1.3.4.7.11. Assist the government in the identification, creation, update and/or deletion, and documentation of reference data, e.g., port names.

1.3.4.8. Subtask 8 – Develop. This subtask addresses CDRLs A005, A008, B013, B014, B021, and B024.

1.3.4.8.1. The contractor shall develop software to maintain the GATES capabilities described in existing system or software documentation and to implement downward-directed, mission-essential requirements. The scope/size of each release is based upon the government requirements process that prioritizes the requirements before the developer estimates how many requirements can be included in the release based upon constraints such as time and funding. The program manager then formalizes what requirements are officially included in the release. It should be understood that all requirements are not equal in level of effort required to implement and cost to implement.

1.3.4.8.2. The contractor shall maintain the development environment to the most current operational environment configuration:

· Validate the intended release environment configuration prior to commencing development of a software release.

· Coordinate immediately with the government designated representatives when deviations to the intended environment configurations are necessary to support development and delivery of the software release. (CDRL B013)

1.3.4.8.3. The contractor shall develop, test, document, and deliver software solutions, including implementation of business rules such that it performs satisfactorily on government-provided equipment. (CDRLs A005, A008, B014, B021, B024)

1.3.4.8.4. The contractor shall ensure that developed software does not interfere with currently fielded hardware or government-accepted software.

1.3.4.8.5. The contractor shall conduct unit code and database reviews to ensure developed software meets design specifications and is ready for developer testing.

1.3.4.8.6. The contractor shall ensure a schedule is maintained to encompass all long lead items approved for development and associates each long lead item to a target release schedule. Manage development of each long lead item to ensure each item is ready to incorporate into its intended release. (CDRL A005)

1.3.4.8.7. The contractor shall confirm vendor software patch compatibility with existing GATES code.

1.3.4.8.8. The contractor shall analyze and upgrade the database management system.

1.3.4.9. Subtask 9 – Test. This subtask addresses CDRLs A008, B001, B002, and B023. The contractor shall conduct testing and complete the following tasks:

1.3.4.9.1. Produce and maintain test cases and software test descriptions:

· To verify that the software meets the SRS.

· To verify that the software does not interfere with currently fielded hardware or government accepted software.

· To verify that software meets test pass/fail criteria for each requirement contained in an SRS. (CDRLs B001, B002, B023)

1.3.4.9.2. Perform internal testing (e.g. unit, system, regression, security, performance).

1.3.4.9.3. Conduct and participate with government representative in integrated testing, to include regression testing, to ensure the developed capability is suitable for delivery to the government as the test baseline (as defined in the Defense Acquisition Guidebook).

1.3.4.9.4. Participate and document with the government to complete any DOD, Joint, Air Force or other governing body certification or accreditation testing for all security classification domains. (CDRLs A008, B001)

1.3.4.9.5. Participate with government representatives in validating a software release prior to delivering the release to the government. (CDRL B023)

1.3.4.9.6. Provide to the government all testing artifacts (e.g. test results, Software Test Descriptions, Test Readiness Review Report) required to complete all government acceptance testing. (CDRLs A008, B001, B002, B023)

1.3.4.10. Subtask 10 – System Integration. This subtask addresses CDRLs B010, B014, B020, B021, B022, B026, and C001. The contractor shall support full system integration by ensuring that the software does not adversely affect the intended operational system, and by accomplishing the following tasks:

1.3.4.10.1. Prepare and deliver the configuration items of the intended operational system. (CDRLs B010, B014, B020, B021, B022, B026, C001)

1.3.4.10.2. Ensure and demonstrate that the software is integrated into the intended system configuration.

1.3.4.10.3. Provide software application training for key technical personnel, functional help desk personnel, trainers, testers, government personnel, and contractors designated by the government for each release. (CDRL C001)

1.3.4.10.4. Support the government in the installation and fielding of the delivered system.

1.3.4.10.5. Prepare and deliver software releases and test results, including all required components and documentation. (CDRLs B010, B014, B20, B021, B022, B026, C001)

1.3.4.10.6. Develop the installation procedures, sequencing, and schedule inputs associated with the version release or hardware installation. In consultation with the PMO, coordinate preparation and installation activities with sites. Provide the status daily to the PMO during the releases or installations.

1.3.4.11. Subtask 11 – Provide the What’s New Document. This subtask addresses CDRL B022.

1.3.4.11.1. The contractor shall provide a “What’s New Document” (CDRL B022) describing the changes made for the applicable release. This document shall be written in language understandable to the functional community.

1.3.4.12. Subtask 12 – Future Negotiated

1.3.4.12.1. The GATES PMO foresees tasks associated with transportation tracking numbers, database query expansion, Enterprise Integration Lab (EIL), Common Computing Environment (CCE), services for an SOA design, and interfaces such as Mobility Enterprise Information Services environment.

1.3.4.13 Subtask 13 – Transportation Tracking Number (TTN) Data Element Capability

1.3.4.13.1. The contractor shall create GATES TTN capability. TTN will provide a unique data element that maintains referential data integrity across all unit movement systems in the Joint Deployment and Distribution Enterprise (JDDE). TTN will provide the ability to link unclassified transportation information to classified force requirements in support of Joint operations while preserving Operations Security (OPSEC). TTN will generate a unique unclassified identifier in the classified force planning systems which can be used by the unclassified Service and Joint transportation domains to achieve end-to end visibility and planned versus actual comparison of unit movements.

1.3.4.13.2. TTN will provide an accurate data set that can be used to create a view of what was planned, compared to what is actually moving (or not moving). TTN will enable views of planned requirements fully matched for movement in execution so that the supported Combatant Commander (COCOM) can make informed employment decisions based on current state of unit equipment capabilities; i.e., what percent of a unit is in theater and what is the location of the remainder of the equipment.

1.3.5. Task 5 – Product Integration

1.3.5.1. The contractor shall integrate emerging port functionality into the software/firmware/hardware solutions supporting GATES.

1.3.6. Task 6 – Asset Management . This task addresses CDRL A007. The contractor shall provide asset management by accomplishing the following per DOD guidance:

1.3.6.1. Maintain equipment, ship and receive equipment, and maintain shipping, receiving, and accounting documentation.

1.3.6.2. Provide inventory tracking, planning, maintenance coordination.

1.3.6.3. Maintain current database of all GATES equipment worldwide and active Points of Contact (POCs) for each site. (CDRL A007)

1.3.6.4. Function as a single POC for any GATES equipment issue.

1.3.6.5. Track maintenance and warranty status of all GATES equipment.

1.3.6.6. Maintain government equipment accounts, Automated Data Processing Equipment (ADPE), in the Assets Inventory Management (AIM) in accordance with AFI 23-111 and AFMAN 23-220. (CDRL A007)

1.3.6.7. Coordinate and maintain storage facilities for GATES equipment.

1.3.6.8. Provide Central Site equipment management control.

1.3.6.9. Function as the contractor AFWay Purchasing Agent.

1.3.6.10. Conduct government property inventory annually or as requested by the government.

1.3.6.11. Track and account for all government equipment through the Air Force AIM system. (CDRL A007)

1.3.6.12. Maintain familiarity with the Information Technology Asset Management (ITAM) Handbook.

1.3.6.13. Implement Asset Inventory methods to assist the government in maintaining asset tracking and compliance with policy.

1.3.7. Task 7 – Security Engineering Certification and Accreditation. The contractor shall provide security engineering certification and accreditation by accomplishing the following tasks:

1.3.7.1. Subtask 1 – Certification and Accreditation Support. The contractor shall provide security certification and accreditation support to GATES PMO by providing the following services:

1.3.7.1.1. Support the GATES Authority to Operate (AtO), Authorization to Connect (AtC), Certificate of Networthiness (CON), and DoD Information Assurance Certification and Accreditation Process (DIACAP) processes.

1.3.7.1.2. Prepare and monitor security documentation necessary to operate GATES throughout the world. This includes AtO documentation with USTRANSCOM, AtC documentation with Air Force Network Integration Center (AFNIC), AtO and CON documentation with each additional military Service (Army, USMC, and Navy), and if necessary the Project Support Agreement (PSA) with the specific base. AtO documentation includes the release notification, Enterprise Information Technology Data Repository (EITDR) registration, USTRANSCOM and other Service required checklists, and the coordination of other documentation for submission to USTRANSCOM or other Services prepared by other entities.

1.3.7.1.3. Provide weekly status updates on AtOs, AtCs and CONs to GATES PMO for incorporation into the program schedule.

1.3.7.1.4. Schedule and monitor the Network Risk Assessments required by USTRANSCOM and other services.

1.3.7.1.5. Provide, when instructed by the COR, notification and information to each major command, military Service, and base.

1.3.7.1.6. Prepare notification for Navy Marine Corps Infrastructure program (NMCI) and Overseas Navy Enterprise Network (ONE-NET), USMC and US Army Signals Command for each release and prepare the necessary release documentation.

1.3.7.1.7. Coordinate with USTRANSCOM and other military Services as well as other DOD authorities to ensure that the GATES system is approved to operate on various networks around the world.

1.3.7.1.8. Coordinate with GATES program to ensure applicable security documents are posted and available to users.

1.3.7.1.9. Advise and consult with the Program Manager on matters of information and system security.

1.3.7.1.10. Notify the government within one hour after the contractor is aware that GATES is not in compliance with DIACAP. There shall be no incidence of late notification to the PMO.

1.3.7.1.11 Provide a quick-fix recommendation within 24 hours after the DIACAP non-compliance became apparent to the contractor.

1.3.7.1.12 Provide within 10 working days a recommendation to the government to correct DIACAP non-compliances.

1.3.7.2. Subtask 2 – Vulnerability Management

1.3.7.2.1. As it relates to GATES, the contractor shall manage the United States Cyber Command (USCYBERCOM) Information Assurance Vulnerability Alert (IAVA) process; coordinate the response to USCYBERCOM, and keep abreast of Air Force Network Operations (AFNETOPS) Network Tasking Orders (NTO), and Notices to Airmen (NOTAM).

1.3.7.2.2. The contractor shall serve as liaison between developers, testers, system administrators, and Network Operations and Security Centers throughout DOD for problem resolution and/or clarification on such notices/alerts/advisories/bulletins/messages.

1.3.7.2.3. The contractor shall support the development and maintenance of the GATES Ports, Protocols and Services (PPS) Matrix and ensure proper registration with the Department of Defense and AFNETOPS.

1.3.7.3. Subtask 3 – GATES Security and Documentation Support. This subtask addresses CDRL A008.

1.3.7.3.1. The contractor shall provide reviews and reports on proposed changes to system hardware, software, or environment for impacts to the GATES security posture and ensure changes do not violate the criteria for system accreditation. (CDRL A008)

1.3.8. Task 8 – Operations Support

1.3.8.1. Subtask 1 – Fielding Support. This task addresses CDRL B005. The contractor shall provide the following (some of these subtasks must be accomplished in advance of fielding):

1.3.8.1.1. Equipment documentation, special approvals Radio Frequency, and Declaration of Conformity.

1.3.8.1.2. RF documentation, creation of DD1492 Application for Equipment Frequency Allocation, supporting documentation for Military Communications Electronics Board (MCEB), SFAF messages for temporary RF approvals, coordination of Host Nation Approvals, coordination with all levels of Spectrum management.

1.3.8.1.3. Research for new equipment specifications for upgrade efforts.

1.3.8.1.4. Inputs related to the GATES installed sites and coordination of logistical support for existing and new sites.

1.3.8.1.5. Updates and maintenance of the GATES Integrated Logistics Support Plan (ILSP) (CDRL B005)

1.3.8.1.6. Direct installation support, to include troubleshooting, patches, and installations.

1.3.8.2. Subtask 2 – Technical Support. This subtask addresses CDRLs A008, B013, B019, and B021. Unless otherwise stated in the succeeding subparagraphs, the contractor shall provide the following to the PMO or requesting activity:

· An initial response to queries within 60 minutes after receipt of verbal or written request.

· Verbal notices reported to the PMO within one hour after the problem or the potential problem becomes apparent to the contractor.

· Proposal/recommendations for non-emergency situations within 24 hours upon request from the PMO.

· When there is a situations requiring the contractor to implement long-term corrective action, the contractor shall institute, within 10 working days from implementing immediate corrective action, long term corrective action, as presented to the PMO.

1.3.8.2.1. The contractor shall provide 24/7 technical assistance with the GATES application and associated specialized equipment. The contractor shall provide Help Desk, advanced system administration, and advanced database administration support for the GATES functional and technical requirements involving RGATES, DGATES, and AIT as well as specialized equipment such as hand-held terminals, kiosks, and printers. This includes in-depth troubleshooting and fault isolation, providing technical expertise on all systems, repair and maintenance on preinstalled hardware/software/peripherals, and performing user account maintenance.

1.3.8.2.2. The contractor shall provide technical support for GATES application and systems, to include RGATES, DGATES, AIT, and specialized equipment support, by accomplishing the following tasks:

1.3.8.2.2.1. Provide continuous on call engineering support.

1.3.8.2.2.2. Assist in fault/defect isolation analysis and resolution.

1.3.8.2.2.3. Document issues with the fielded system utilizing the government-identified trouble reporting systems/methods.

1.3.8.2.2.4. Coordinate all program system problem/outage resolutions with appropriate agencies and/or activities.

1.3.8.2.2.5. Provide assistance to resolve/fix problems.

1.3.8.2.2.6. Update the government-provided problem reporting system.

1.3.8.2.2.7. Upon an inability to resolve a problem determined to be programmatic, generate SPRs (CDRL B019) for appropriate support actions.

1.3.8.2.2.8. Provide Technical Reports (white papers) (CDRL A008) to address proposed approach and technological changes.

1.3.8.2.2.9. Install and maintain software/firmware/hardware solutions supporting GATES AIT requirements. This includes established efforts to migrate the current AIT software to an updated platform chosen by the government. Efforts consist of a Radio Frequency (RF) and a non-RF version of the software to support locations without any approved frequency. The contractor shall assist the government by testing government chosen products and making recommendations. The contractor shall provide skilled/knowledgeable personnel to install the chosen AIT platform and configure the system to run the GATES software for the functional community. Also, the contractor shall provide onsite assistance and training during the implementation phase.

1.3.8.2.2.10. Provide 24/7 system administration and troubleshooting assistance for all GATES systems, including test bed systems. Troubleshooting shall include assistance related to Microsoft servers, wireless Access Points (AP), Virtual Private Network (VPN), and Intruder Alert software, including but not limited to, user account maintenance, hardware installation and configuration, software installation and configuration, user request support and problem tracking, hardware and software upgrade recommendations, system performance monitoring, file system configuration and maintenance, documentation of system configuration and information, and assistance to other administrators.

1.3.8.2.2.11. Provide advanced database administration support for troubleshooting assistance.

1.3.8.2.2.12. Provide 24/7 Help Desk support for RGATES and DGATES by providing the following:

· System monitoring

· Problem identification

· Troubleshooting

· System resets

· System backups

· Liaison support between customer and applicable Control Centers after the problem has been referred by the government C2 Call Center or applicable “first line” troubleshooting process

· On-call/duty POC list for all areas of responsibility covered by this PWS maintained to currency

· Troubleshooting services to determine the problem’s cause, fix, and/or recommendation of the office responsible; updates to the government provided problem reporting system

· Deployment assistance, including troubleshooting during and while deployed for hardware, software, connectivity, site installs, system monitoring, security, account, and data issues

· Installation of all application related firmware/software systems patches and upgrades

· Development and installation of hardware, firmware, and software setup for replacement and new sites before shipping

1.3.8.2.2.13. Retrieve GATES historical data that common users cannot obtain through normal means. Verify that the applicable GATES functional manager has approved any users/requestors of the Historical Data, to ensure proper identification of these individuals.

1.3.8.2.2.14. For RGATES and DGATES, coordinate, manage, and install each release. Provide and maintain an RGATES Installation Plan (CDRL B021) supporting this activity.

1.3.8.2.3 Develop, establish, and maintain the development environment matching the operational baseline (hardware & software). Any Requests For Deviation are to be submitted per the instructions provided in CDRL B013.

1.3.8.3. Subtask 3 – Functional Help Desk. The contractor shall provide functional Help Desk support. This requires the contractor to perform system security requirements and support GATES access management. In accomplishing this task, the contractor shall:

1.3.8.3.1. Manage the Workstation Area Security Officer (WASO) appointment program.

1.3.8.3.2. Provide account creation and maintenance support to deployed account managers, Brio account managers, and user accounts; revalidate accounts annually.

1.3.8.3.3. Reset forgotten or expired passwords and lock or unlock user accounts when no WASO is available and access is deemed mission critical.

1.3.8.3.4. Maintain and enforce group and roles membership.

1.3.8.3.5. Develop and maintain security documentation training for users and the WASOs. Post Security Services application training aids, security-related forms, and WASO informational documents to the GATES website's security page.

1.3.8.3.6. Correct and validate defective or missing database entries in security-related tables, when specified in open trouble tickets.

1.3.8.3.7. Provide testing support for the Security Services functionality during Formal Software Testing (FST) and Customer Acceptance Testing (CAT).

1.3.8.3.8. Provide functional area expert advice.

1.3.8.4. Subtask 4 – Location Support & Training Support. This subtask addresses CDRL C001. The contractor shall provide location and training support by accomplishing the following:

1.3.8.4.1. The contractor shall provide GATES software and hardware platform installation and troubleshooting support. Currently, five formal school locations are supported (Lackland AFB, TX; March ARB, CA; AMWC, Ft. Dix, NJ; Westover ARB, MA; Dobbins AFB, GA). There is a possibility for Army schools to be added. (CDRL C001)

1.3.9. Task 9 – Other Direct Costs

1.3.9.1. The government may request the contractor purchase AIT and GATES specialized equipment hardware as Other Direct Costs (ODCs), including but not limited to, wireless mini carts, hand-held terminals, and kiosks for new initiatives. After the requirements for hardware are determined, the government will request the contractor submit a proposed equipment list to include respective equipment quantities, delivery dates, and unit price of each item listed. The contracting officer will confirm the availability of funds. If there are any changes to the original proposal, the contractor shall make a recommendation to the PMO, and receive PMO approval before purchasing any alternate. The contractor shall inspect and test the equipment prior to delivery to government. If the equipment is damaged or does not operate according to its performance description, the contractor shall attempt to return the nonconforming equipment for replacement or refund. ODCs will be reimbursed on a cost-reimbursable basis utilizing the ODC CLIN established. The contractor shall comply with Defense Transportation Regulations, especially as they relate to the transport and delivery of IT equipment to foreign destination. The regulations are at the following URL: http://www.transcom.mil/j5/pt/dtr.cfm as well as in federal statutes.

1.4. General Information.

1.4.1. Place of Performance

1.4.1.1. The services described in Task 1.3.6, Task 1.3.7, and Subtask 1.3.8.3 shall be provided on-site at Scott AFB, IL. All other tasks shall be performed at the contractor’s site and from time-to-time at locations designated by the government as needed to work with GATES hardware platforms and attend meetings, conferences, and other government directed activities.

1.4.2. Duty Hours. Maintenance of GATES consists of two different types of duty hours.

1.4.2.1. Technical support availability, except the Functional Help Desk, shall be 24/7.

1.4.2.2. Contractor shall be available to correspond and attend meetings with the government during normal duty hours. Government duty hours are 0700 -1700 hours Monday through Friday, except for Federal holidays. Other services/tasks shall be based on the delivery schedules of due-ins/deliverables, meeting schedules.

1.4.2.3. Functional Help Desk shall operate during normal duty hours, unless the PMO directs a change to accommodate events such as installation support.

1.4.3. Travel.

1.4.3.1. Travel by contractor personnel may be required in support of this contract. The contractor must obtain approval by the government prior to travel commencement. Reimbursement for travel outside the local area is authorized. Travel will be reimbursed at cost in IAW with FAR 31.205-46 and Federal Travel Regulations (FTR) guidance.

1.4.3.2. The contractor shall submit a travel itinerary and estimated cost for approval by the COR not later than five workdays prior to travel. The contracting officer will confirm the availability of funds. Per Diem and travel rates shall not exceed the amount authorized in the Joint Travel Regulation (JTR). Airfare shall be the prevailing rates for commercial airlines at coach class. The contractor should make all efforts to schedule travel far enough in advance to take advantage of reduced airfares. When required, the most reasonable means of ground transportation (i.e. taxi, bus, rental car) shall also be used.