SOW FA4600-06-F-8001.doc

Integrated Tactical Warning/Attack Assessment Architecture Support (ITW/AA)

STATEMENT OF WORK

31 May 06

Revision 1

1.0

DESCRIPTION OF SERVICES

1.1. Scope: Support the documentation, alignment, maintenance, and analysis of an integrated, end-to-end Integrated Tactical Warning/Attack Assessment (ITW/AA) Mission Architecture to serve as a defendable analytical reference for operations personnel (supporting day-to-day operations and system integration). The ITW/AA Mission Architecture identifies warfighter relationships, activities and information needs (Operational Views), relates system functions and characteristics to warfighter requirements (System Views), and prescribes conventions and standards to ensure interoperable implementation across the information technology enterprise (Technical Views). The ITW/AA Mission Architecture should leverage, and be traceable to, existing ITW/AA sub-architectures and United States Strategic Command (USSTRATCOM) Enterprise Architectures. Additionally, project management and technical support to the USSTRATCOM Enterprise Management Branch consisting of specific and general tasks will be provided through operational and technical data architecture support through modeling, data collection, process analysis, economic analysis, briefing and meeting support and plan development.

1.2. Background: USSTRATCOM is responsible for developing desired characteristics and capabilities, advocating, planning and conducting nuclear deterrence, space, global strike, integrated missile defense, and information operations. This responsibility includes, but is not limited to, supporting other combatant commanders by providing warning and assessment of space and missile attack and advocating desired missile warning characteristics and capabilities of all combatant commanders, including the battle management, command and control, communications, and intelligence system and architecture. The Enterprise Management Branch (HQ USSTRATCOM/J823) is responsible for documenting, developing, aligning, and maintaining integrated (operational, system, and technical) architecture artifacts depicting the people, processes, and standards for all USSTRATCOM assigned mission areas. The architectural artifacts provide descriptions of current, transitional, and long-term requirements, capabilities, duplications, and deficiencies for development and modernization plans along with the technical standards required to integrate missions. This effort supports the process of properly preparing and providing architectural artifacts for use by operations personnel.

1.3. Objective: Utilize contractor expertise to build upon and maintain an ITW/AA Mission Architecture, using the Department of Defense Architecture Framework (DoDAF), for use by operations personnel. The ITW/AA Mission Architecture requires an integrated (people, processes, systems, and standards), end-to-end (sensor-to-assessor) view to effectively sustain the ability to provide warning and assessment of air, space and missile attack. Contractor support is sought to accurately capture, document, uphold, align, and provide architecture artifacts for analytical examination in support of the ITW/AA Change Control process. The overall tasking involves the development, alignment, and maintenance of a mission architecture, along with a systems engineering and change management process to efficiently link requirements, resources, master schedules and dependencies to the architecture to maximize the capital expenditure of resources to meet USSTRATCOM requirements. It also involves highly skilled, specialized technical contracted support to assist the Government with defining, improving, and supporting the development and integration of mission architectures into the USSTRATCOM Enterprise Architecture.

1.4. Place of Performance: USSTRATCOM, Building 500, Offutt AFB NE and Building 1470, Peterson AFB CO.

1.5. Tasks:

1.5.1. Document, develop, align, analyze and maintain/update an ITW/AA Mission Architecture.

1.5.1.1. The Contractor shall provide support for documenting, developing, aligning, analyzing, and maintaining/updating an ITW/AA Mission Architecture consisting of All Views, Operational Views, System Views, and Technical Views, in accordance with the most current version of the DoDAF, using Command-approved architecture tools, methodology, and standards. This task entails incorporation of the guidance of higher-level direction, such as the DoD Architecture Framework and the DISR. Architecture information shall be documented and maintained in the following documents/databases: Telelogic System Architect and DoD Architecture Registry System (DARS). Product deliverables will maximize the use of architectural graphics and tables to enhance document clarity and succinctness. (CDRL A003, A005)

1.5.1.2. The Contractor shall establish and maintain a current "As-Is" (within Future Years Defense Plan (FYPD)) baseline accurately reflecting the ITW/AA Mission and System connectivity. This includes leveraging and encouraging reuse of architectural artifacts, along with supporting the automatic distribution of artifacts, among ITW/AA sub-architectures, USSTRATCOM Enterprise Architecture, NORAD Enterprise Architecture, and mission partner architectures. (CDRL A003)

1.5.1.3. The Contractor shall attend technical interchange meetings (TIMs) to gather subject matter expert (SME) information and data required for development, alignment, and analysis of architectures, and to report architectural progress to the Quality Assessment Personnel (QAP). (CDRL A002)

1.5.1.4. The Contractor shall coordinate proposed architecture changes throughout the command (including components) and with mission partners to ensure concurrence. This may require a TIM to resolve comments. (CDRL A002) The Contractor shall deliver an annual Architecture Support Plan (ASP) documenting architecture deliverables and milestones for the coming year NLT 1 September of the previous year (to coincide with end of fiscal year). The purpose of the ASP is to document architecture requirements to support the ITW/AA Change Control Process and to clarify roles and responsibilities of stakeholders and supporting organizations. The goal is for the ASP to serve as an informal contract between architects and customers to document annual architectural goals and milestones to ensure architecture efforts accurately support customer requirements. The content of the ASP follows that of the All View (AV)-1, Overview and Summary. Format for the ASP should be in Microsoft Word and follow previous version formats.

1.5.1.5. The Contractor shall support USSTRATCOM initiatives to integrate ITW/AA operations with supported/supporting COCOMs, Services, and Components. This includes supporting alignment of ITW/AA sub-architectures with the ITW/AA Mission Architecture and other USSTRATCOM Mission Architectures, the USSTRATCOM Enterprise Architecture, and mission partner architectures. This may require a TIM. (CDRL A002)

1.5.1.6. The Contractor shall develop and provide architectural artifact/product presentations accurately reflecting data maintained within command architecture repositories. (CDRL A005) As a minimum, Telelogic (formerly Popkin) System Architect data should be exported into formats that may be accessible and viewable to geographically dispersed locations that may not have Telelogic System architect (formats may include, but are not limited to, Java, Adobe, .html, etc.). Commercially available formats/products should be used – proprietary formats/products may be considered by the government when commercial formats/products limit the display of data.

1.5.1.7. The Contractor shall perform technical analysis, review, and comment on selected architectures, programs and documents to determine accuracy, applicability, and ensure conformance with, the commands' architectural direction. This involves a review of documents dealing with interoperability, architectural policy, direction, guidance and integration compliance with the ITW/AA Mission Architecture and related architectures. (CDRL A003)

1.5.1.8. The Contractor shall review selected documents for information update and correction. This effort includes reviewing, updating and maintaining command-specific and mission partner documentation. USSTRATCOM and ITW/AA-specific standards are generally based on commercial and military standards. As the commercial or military standards evolve, USSTRATCOM and/or ITW/AA standards must be reviewed and updated accordingly, and impacts to existing infrastructure must be evaluated and documented. (CDRL A003)

1.5.1.9. The Contractor shall develop and publish weekly architecture status reports. The government will provide formats for the weekly reports. (CDRL A001)

1.5.2. Support standardization of architecture development processes, improving architecture presentations, and aligning .

1.5.2.1. The Contractor shall support efforts to establish tactics, techniques, and procedures (TTP) for architectural training and operations support. This includes participating in architecture collaboration groups and contributing ideas for improving the architect’s process/procedure and architectural artifact presentation to architecture customers. (CDRL A005)

1.5.2.2. The Contractor shall develop an architect guide that describes process and procedures for developing, aligning, and maintaining the ITW/AA Mission Architecture. The intent of this architect guide is to provide information to component and mission partner architects supporting the development and maintenance of ITW/AA-related architecture efforts. This includes, but is not limited to, TTP for developing and maintaining the mission architecture, procedures for importing and exporting architectural data to command architecture tools, an overview of the architecture change management process, etc. The guide should also include procedures/templates for creating, organizing, and distributing architectural artifacts into attractive and useful products for use by operations personnel and command advocates. This includes maintaining a capability to import and export information into architecture databases and selected websites, as well as recommending improvements to the packaging, presentation, and easy retrieval of architectural artifacts from the Telelogic database. The architect guide shall be published as directed by the Government. The Government estimates that four (4) publications will be required throughout the year. (CDRL A003)

1.5.3. Support ITW/AA Communications and Architecture Panel (CAP) activities.

1.5.3.1. The Architecture Review Panel is a standing panel responsible to the ITW/AA Operations Approval Board for operational communications integrity and architectural compliance of the ITW/AA System. The Contractor shall provide support as the CAP Secretariat. Specific tasks include maintenance of the CAP web page, organizing and setup of CAP meetings, recommending agenda items, preparing briefings, documenting discussions and preparing minutes, and tracking action items of the CAP. (CDRL A002, A005)

1.5.3.2. The Contractor shall analyze and provide an architectural assessment of USSTRATCOM’s capability to satisfy ITW/AA mission requirements. This includes providing technical support to the CAP and its sub-working groups, identifying deficiencies, recommending courses of action to mitigate the deficiencies, and institute a formal structured process to support the ITW/AA change management activities necessary to execute the reflected course(s) of action captured in transition plans. (CDRL A003)

1.5.3.3. The Contractor shall maintain liaison between CAP efforts and the ITW/AA System Integrity Board. This involves ensuring accuracy and currency of the ITW/AA Mission Architecture as it may be used to support ITW/AA system certification and testing activities. This includes developing and integrating software tools to enhance the analysis of architectures and programs in terms of technical merit, standards compliance and integration.

1.5.3.4. The Contractor shall identify, analyze, research and recommend solutions for integration and interoperability shortfalls and concerns to support the CAP. The Contractor shall review, evaluate, recommend, and comment on Standard Change Form (SCF) requests and Architecture Validation Packages requiring CAP consideration. (CDRL A004)

1.5.3.5. The Contractor shall review USSTRATCOM, NORAD, and Component-generated documents to ensure DoD and Joint-directed interoperability and architectural policy is adequately addressed. Examples of documents to be reviewed include Joint Capabilities Integration and Development System (JCIDS) documentation, miscellaneous requirements documents, and staffed packages.

1.5.4. Develop and maintain architectural analysis tool to support ITW/AA change control Process decision-making.

1.5.4.1. The Contractor shall develop and maintain an architectural analysis tool that enhances and improves accessibility to architecture data as maintained in Telelogic (formerly Popkin) System Architect. The goal is to decrease change control decision timelines by improving accessibility, manipulation, and analysis of architecture data through use of advanced search engines, filters, customized queries, etc.. The tool should not duplicate deliverables under subtask 1.5.1 of this task order ("Document, develop, align, analyze and maintain/update an ITW/AA Mission Architecture") nor should it be considered as a replacement to the Command's architecture repository (Telelogic System Architect). Rather, it should build upon capabilities inherent in Telelogic System Architect (as a data repository) to enhance the Command's architecture-based analytical capabilities. The analysis tool should be accessible via a web-based environment and not require software or hardware modification at client workstations.

1.5.4.2. The Contractor shall document the development and maintenance of the analysis tool in accordance with architect guide deliverable referenced in existing subtask 1.5.2 of this task order.

1.5.5. Support selected activities and interests to include providing quick reaction support, attending meetings and training, and traveling.

1.5.5.1. USSTRATCOM/J823 is the Command’s focal point for architecture support and representatives for various DoD and Joint architecture working groups and conferences. USSTRATCOM/J82 representation and technical expertise at these meetings is required to ensure Command interests are adequately addressed within the Joint community. The Contractor shall attend selected meetings to provide technical expertise and supporting documentation that will ensure Command interests are adequately considered. (CDRL A002)

1.5.5.2. The Joint architecture community is working on a number of initiatives to capitalize on architectures, and institutionalize and standardize architecture metrics, integration, alignment, and analysis. The Contractor shall attend selected training to establish USSTRATCOM in-house expertise. The Contractor shall perform follow-on training for the USSTRATCOM community, as required. (CDRL A005)

1.5.5.3. Quick reaction support is required by the Government to work short-notice requirements related to USSTRATCOM concerns. This subtask allows the Government to task the Contractor to analyze problems and identify issues, attend short-notice meetings, and provide technical input to briefings. Upon receipt of a “quick response” tasking, the Contractor shall proceed with the task unless assumption of the task will cause the Contractor to exceed the total hours on this task order. The Contractor shall simultaneously provide written notification (not to exceed one [1] page) to the Quality Assurance Personnel (QAP) and the Program Manager on the nature of the tasking, the date received, required deliverables, and estimated number of staff-hours required to complete the task.

1.5.5.4. The Contractor shall develop technical presentations and meeting support documentation to address USSTRATCOM interests, as required. (CDRL A002, A005)

1.6. Deliverables.

1.6.1. Progress Reports/ Program Progress Reports and Quarterly Management Reviews. These reports are required to summarize past and future architecture-related activities. The format for these reports will be provided by the Government. Possible formats include, but are not limited to, Microsoft Word documents or electronic mail. Progress reports will be required weekly. (CDRL A001)

1.6.2. Conference Minutes/Meeting Minutes and Trip Reports. These reports are required to document the results of meetings, trips, studies, and analyses as tasked by the requiring office. The Government estimates that twelve (12) CAP meetings, twenty (20) technical interchange meetings (TIMs), and twelve (12) trip reports will be required. The TIMS consist of architecture boards, less formal architecture planning and guidance sessions, and coordination/comment resolution of staff packages. Minutes of meetings and trip reports shall be delivered in soft copy (Microsoft Word). Estimate one copy for each meeting. Minutes and reports shall be provided within five (5) working days after completion of meeting. (CDRL A002)

1.6.3. Service Engineering Reports /Technical Reports. Service Engineering/Technical Reports are required to document the results of review and analysis activities, as well as summarizing updates to architecture artifacts and associated databases (i.e. Telelogic) The format for these reports will be determined by the Government at the time of tasking. Possible formats include, but are not limited to, one or a combination of the following: point papers, position papers, word documents, excel spreadsheets, powerpoint slides, etc. The due date for reports summarizing updates to architecture artifacts within databases is the last working day of each month. All reports shall be delivered in soft copy. (CDRL A003)

1.6.4. Standard Change Forms (SCF). Review and evaluate design, integration, and test documents for the proposed system and subsystem upgrades to ensure architectural compliance and integration with applicable standards. Write SCFs wherever subsystem deficiencies are identified which adversely impact system integrity or system performance. (CDRL A004)

1.6.5. Presentation Material/ Briefing Material. Presentation materials include, but are not limited to, graphics and verbiage accurately reflecting the architecture data resident in command architecture repositories, as well as information and issues relevant to the ITW/AA Architecture Review Panel. Presentation materials shall be developed as directed by the Government. Presentation materials will be delivered in soft copy and hard copy at timeframes mutually agreed upon by the QAP and the Contractor. The number of hard copies required will vary, but will not exceed 50. (CDRL A005)

1.6.6. USAMS Socio-Economic Report. The Socio-Economic report is due annually to the 55th Contracting Officer and according to the Government schedule. (CDRL A008)

1.6.7. Funds and Man-Hour Expenditure Report. A monthly status report is required to document activities accomplished, agreements reached, and resources (man-hours and funds) utilized. Submit a quarterly progress report that summarizes the results of all work performed, the type and amount of effort (man-hours), expenses incurred, deliverables completed, work in process, percentage of annual effort expended by effort, problems encountered, recommended solutions and work planned during the next reporting period. (CDRL A009)

2.0

SERVICE DELIVERY/TASK SUMMARY

PERFORMANCE

OBJECTIVE

SOW

PARAGRAPH

REFERENCE

PERFORMANCE

THRESHOLD

1.5.1.2 As required by the Government schedule with 100% accuracy and no customer complaints for redelivery

1.5.5.3 As required by the Government schedule with 100% on time and accurate

3.0

WORKING SPACE/MATERIAL/EQUIPMENT

3.1 The Government will provide access to relevant government organizations, information, and documentation, manuals, text briefs, and associated materials as required and available. Access will be granted to classified networks as directed by the designated security authority. The Government will provide the Contractor access to the C2AS Web Server , the C2AS LAN, and access to the staff to accomplish taskings. The Government will sponsor the Contractor’s access to government websites and databases as required to include the Telecommunications Certification Office Support System (TCOSS) database. The Contractor shall request other required items in writing to USSTRATCOM/J823 through the Contracting Officer.

3.2.

The Government will provide limited working space (no more than two spaces each) in USSTRATCOM spaces including Building 1470 (Peterson AFB CO) and Building 500 (Offutt AFB NE). The space will include computers, telephones, e-mail and LAN connectivity, as required to perform tasks identified in the SOW. The government will provide access to supported equipment and systems, as required for funded field contractor personnel.

3.3.

The Government will provide access to facilities, office space, supplies and services, to include workstations, computers and phones. Access will be granted to classified and unclassified military local area network (LAN) services, LAN support, telephones, and reproduction facilities. If the contractor determines additional equipment is required, the contractor shall notify the government, in writing, of the applicable information/equipment required to accomplish the required task(s).

4.0 GENERAL INFORMATION

4.1. Personnel Qualifications. The contractor shall possess the necessary training, qualifications, and clearances to accomplish all tasks identified in this SOW. Resumes may be provided to demonstrate individual skill sets.

4.1.1. The Contractor shall demonstrate a full understanding of the Department of Defense Architecture Framework (DoDAF) and associated architecture repository systems. Personnel assigned to this task must have at least 3 years experience and/or education in DoD architecture policies, framework, and CADM compliance; program management, strategic planning, and business process re-engineering; structured, object-oriented, and activity-based methodologies; IDEF modeling; and the following case tools and software products: Telelogic System Architect, Rational Rose, Microsoft Visio, NetViz, and standard Microsoft Office Products.

4.1.2. The contractor shall have experience in the operation and maintenance of communication systems, servers and networks is highly desired.

4.1.3. Appropriate fields of experience include strategic and non-strategic command, control, communications, computer, intelligence, surveillance, and reconnaissance (C4ISR) systems; automated data processing; satellite systems; and data management systems, including data collection and analysis techniques.

4.1.4. The Contractor shall be capable of discussing C4ISR issues with appropriate subject matter experts for all assigned mission areas. The Contractors have a good understanding of complex, multi-platform information technology (IT) infrastructure operations, processes, and tools and should be capable of deploying and documenting enterprise management solutions for complex heterogeneous IT and mission environments.

4.1.5. The Contractor shall have the capability of having senior level personnel with extensive backgrounds in C4 related fields. A minimum of two FTE positions must have a minimum of 3 years experience with Telelogic.

4.1.6. The Contractor shall have at least 3 years experience with early warning operations or systems.

4.2. Travel. The contractor shall be required to attend meetings, briefings, or perform other related travel. Temporary Duty (TDY) will be performed as required by the tasking, approved and authorized by the QAP. All travel will be performed on a reimbursable basis. A trip/test report will be provided to the QAP within five (5) workdays after completion of the trip.

The contractor shall be responsible for making arrangements for all airfare, car rental, lodging, and subsistence required for approximately 12 trips a year consisting of 2-3 days duration. The contractor shall be responsible for tracking travel expenditures and reporting usage rates in the Performance and Cost Report. The Joint Travel Regulations (JTR) (Current Volume) shall be used for guidance.

4.3 Period of Performance. The period of performance for this task order is from contract award for a period of 12 consecutive calendar months, with two (2) option years. Please price out the base year and two option years separately.

4.4. Security. Contractor personnel shall possess a Top Secret security clearance at time of Task Order award. Contractor personnel may be required to be eligible for Sensitive Compartmented Information (SCI) access at a later date in order to perform their assigned duties.. Contractor personnel shall follow and meet the security requirements as given in the DD Form 254. The contractor shall not divulge and information about files, data, processing activities or functions, user ID’s, passwords or other knowledge that may be gained to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all USSTRATCOM rules, procedures and standards of conduct. Unescorted and unsupervised access to government facilities, during all hours, is required. (Does not apply to SCIFs.) Ongoing clearance requirements during the period of performance will be coordinated with the Government’s technical point of contact and his security staff. Access will be required to cleared facilities including, but not limited to, the STRATCOM Command Center, NORAD-NORTHCOM Command Centers, and Cheyenne Mountain Operations Center.

4.5. Quality Control. The contractor shall develop and maintain a quality program to ensure services are performed in accordance with commonly accepted commercial practices. At a minimum, the contractor shall develop quality control procedures that address the areas identified in paragraph 2, Service Delivery Summary. A copy of the quality program shall be provided to the government within 30 days of contract award.

4.6. Quality Assurance. The government will evaluate the contractor’s performance by appointing a representative(s) to monitor performance to ensure services are received. The government representative will evaluate the contractor’s performance through intermittent inspections of the contractor’s quality control program and receipt of complaints from USSTRATCOM personnel. The government may inspect each task as completed or increase the number of quality control inspections, if deemed appropriate, because of repeated failures discovered during quality control inspections or because of repeated customer complaints. Likewise, the government may decrease the number of quality control inspections if merited by performance. The contractor shall be responsible for initially validating customer complaints. The government will investigate the complaints received from various customers. The government representative shall make final determination of the validity of customer complaint(s), in cases of disagreement with customer(s). The government has unlimited rights to all deliverables under this Task Order. The government shall retain custody of all records associated with contractor deliverables and shall have exclusive control in the distribution of all written deliverables.